fix: use prefix for last auth

Related Issues
fixes https://github.com/descope/etc/issues/7423
Related PRs
https://github.com/descope/console-app/pull/3365
Description

add storage prefix to last auth

Must

[x] Tests
[ ] Documentation (if applicable)

Maybe we should prefix all local storage keys with the project id?
In this way we will avoid such issues in the future, we won't need to add additional attributes to the web-component, and we will be more consistent
WDYT?

@nirgur we don't add any new attributes, we use the existing local storage prefix attribute which already prefix the session and refresh token so it should be more consistent that way. prefixing based on the project id is a great way but to make it consistent we need a broader change and some break on compatibility for all localstorage keys to make it ready. currently local storage prefix is not really used anywhere

@nirgur we don't add any new attributes, we use the existing local storage prefix attribute which already prefix the session and refresh token so it should be more consistent that way. prefixing based on the project id is a great way but to make it consistent we need a broader change and some break on compatibility for all localstorage keys to make it ready. currently local storage prefix is not really used anywhere

We added this attribute to the web-component and the web-js-sdk
Should this attribute be exposed to descopers? Do we expect them to set its value, or is it only for internal use?
If we agree that a better solution is to use the project-id, let’s consider how we can go with this approach and avoid increasing technical debt by using this attribute in more places

@nirgur this suppose to be internal property. Keep in mind that using project-id as a prefix will break backward compatibility and thus makes this solution much harder.. It's much easier to replace it all with project id and break compatibility all together.

@nirgur this suppose to be internal property. Keep in mind that using project-id as a prefix will break backward compatibility and thus makes this solution much harder.. It's much easier to replace it all with project id and break compatibility all together.

Let's talk about it when you have time


[New chain]: Unit Zero Stagenet

Chain Name
Unit Zero Stagenet
RPC URL
https://rpc-stagenet.unit0.dev
The chain must be added to https://chainlist.org/

[X] I confirm that the chain is added to chainlist

After creating the issue, a bot will estimate the required pre-fund and post it in the comments. Please check this checkbox after you send the pre-fund.

[x] I sent the pre-fund in accordance with Github Action's comment

Relevant information
explorer https://explorer-stagenet.unit0.dev/
chainlist https://chainlist.org/chain/88819

https://explorer-stagenet.unit0.dev/tx/0x615b9a670d9541264defc32cfed162fec7cef025b88588ac673ac153b03e6834


DRAFT: Dev Guide improvements

Updates to content and formatting of DevSetupGuide.md
Updates to other .md files to make them valid and/or more readable Markdown.

See comments below for meta-level issues.

Updating the dev set up guide
Things I didn't get to but need to be done
In VLCS

Indicate how long the manual step takes (0-3 days).

It is not clear where the UMLS API Key goes once you get it.
is the answer: .env the key/value pair VSAC_API_KEY = ChangeMe ?

The step for requested membership access to CMS-DRLS author group should be made...more durable? rather than emailing one individual on the team.

In "installing VSCode"
The "install recommended extensions" step failed to get us some important extensions.
Necessary extensions:

Extension
Author
Notes

Debugger for Java
Microsoft
To run debug-all target

ESLint
Microsoft
Find/fix lint errors in editor

Prettier - Code formatter
Prettier
Find/fix style errors in editor

Recommended:

Extension
Author
Notes

Clinical Quality Language (CQL)
Clinical Quality Framework

Code Spell Checker
Street Side Software
Find/fix tpyos in your cdoe

Extension Pack for Java
Microsoft
Installs 4 other extensions

FHIR tools
Yannick Lagger

GitLens - Git supercharged

Git better

IntelliCode
Microsoft

IntelliCode API Usage Examples
Microsoft

Language Support for Java(TM) by Red Hat
Red Hat

Maven for Java
Microsoft

MongoDB for VS Code
MongoDB

Playwright Test for VSCode
Microsoft
For writing e2e tests

Ruby
Pen Lv

VSCode Ruby
Stafford Brunk

Alex also recommends:

Extension
Author
Notes

Abracadabra, refactor this!
Nicolas Carlo
code faster

change-case
wmaurer
code faster

DotENV
mikestead
.env file syntax

Git Graph
mhutchie
Git better

indent-rainbow
oderwat
see better

Markdown All in One
Yu Zhang
write better .md

Markdown Table
Takumi Ishii
write better .md

markdownlint
David Anson
write better .md

Output Colorizer
IBM
see better

Rainbow CSV
mechatroner
see better

Sapling
team-sapling
for React devs

shell-format
foxundermoon
for shell devs

Text Power Tools
Daniel Tar
code faster

Todo Tree
Gruntfuggly
See your // TODOs

Transformer
dakara
code faster

Web Accessibility
Max van der Schee
Be a GUI a11y

In debug-all

You need to install Java. What version? Otherwise things won't work.
Does MongoDB need to be installed and running? if not...?

Misc
Missing a few npm install commands in various places. These are mentioned in the subsidiary directory READMEs but it would be helpful to reiterate it here as it can be hard to debug.
Refactoring advice for the project

Remove the significant number of large dependencies in the project:

Ruby is only used for one utility (docker-sync), and that utility may not be necessary any more.
Java appears to be used for one test server?

Fix some minor issues:

In package.json, file extensions for linter/etc. should also include tsx
Provide example pre-commit and pre-push hooks which enforce team best practices (e.g.: lint and Prettier must pass)

There are stale references to e.g. create-react-app, which I would strongly recommend migrating away from.

Recommend picking your own port to run things on, rather than standard dev ports like :3000 -- this helps devs who
might have multiple projects running on their machine


This page needs updating as it does not describe the possible usage of the File Transform task

The file transform task (https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/file-transform) has the ability to transform entire arrays in JSON files. Which makes it no longer necessary to use DBAccess.Users.0 = NewUser but you can use DBAccess.Users = ["NewUser1","NewUser2","EvenAddMoreUsersThanBeforeDemoUser"]

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

ID: 315ff823-9992-9f9b-62a1-42ce622ed41c
Version Independent ID: 72ec3ffc-1dc9-b2dc-e3d4-4f14deae3720
Content: File transforms and variable substitution - Azure Pipelines
Content Source: docs/pipelines/tasks/transforms-variable-substitution.md
Product: devops
Technology: devops-cicd
GitHub Login: @RoopeshNair
Microsoft Alias: ronai

Sure, Thanks for calling out. We'll have the documentation updated.

I confirm that this document needs to be updated.  In particular, this bullet point - "Only String substitution is supported for JSON variable substitution" needs to be changed. Replacing content of an entire json array works in the File Transform task and not in the App Service Deploy task.  Note: this is about replacing the value of the entire array and not replacing value each element via the index position. E.g., replacing "ids": [1,2] from the build pipeline with "ids": [1,2,3,4,5] in the release pipeline.

The latest change has been reported as ineffective with the syntax still requiring DBAccess.Users.0 instead of DBAccess.Users.
Please refer to issues https://github.com/MicrosoftDocs/azure-devops-docs/issues/9129 and https://github.com/MicrosoftDocs/azure-devops-docs/issues/9173.


chore: sync v11 branch with main

This PR syncs the latest changes on main with the v11 branch and runs the format command to clean up unformatted files
Also fixes a change in #2299 that was breaking the auto build
Confirm the following PRs are ok to merge from main to v11

#2288
#2299
#2336
#2338
#2347
#2343
#2351

(DCO assistant is failing due to an unsigned agreement in https://github.com/carbon-design-system/carbon-website/pull/2351)


reserved identifier violation

I would like to point out that identifiers like “_EFLAGS” and “_CPU_VENDOR” do not fit to the expected naming convention of the C language standard.
Would you like to adjust your selection for unique names?

It's unlikely that I'll change the code to be fully compatible with C standard. I doubt it can cause any real conflicts and compiler will give warning if anything goes wrong.

How do you think about to avoid that this software depends on undefined behaviour?

It doesn't depend on it. It may have undefined behavior because of reserved identifier conflict, but it's the smallest issue here.


Sample Rate not working

Hi,
Firstly, thank you very much for your fine work.
I am trying to use your repo to read in wav files.
The python code is (so I am using the default sampling rate of 22050):
sound_clip, sr = librosa.load(audioFilePath)

and I got:
[0.00557333 0.00983567 0.00837638 ... 0.01534646 0.01109151 0.00635755]

With your repo, I use:
val buffer = librosa.loadAndReadAcrossChannels(audioFilePath, 22050, -1);

And I got:
[0.007446516312143315 0.00848414563432722 0.009186071352275156 0.009369182409131139...0.005554368724631489 0.00445570238349559 0.0036011841181676687]

I guess the sampling rate is not working because if I use the sampling rate from the wave file(48000), the results are the same.
...or am I missing anything?
I look forward to hearing from you.
Thank you very much.

Hi Yeyicheng,
There are some issues with the sampling rate and I will have it addressed in the next version. I hope the library works fine with the default sampling rate and the issue comes only with the custom sampling rate. Am I right?
Thanks!

Yes. I cannot solve it by myself, so I am looking forward to your update. XD
On Tue, Nov 3, 2020 at 11:22 PM VVasanth<EMAIL_ADDRESS>wrote:

Hi Yeyicheng,
There are some issues with the sampling rate and I will have it addressed
in the next version. I hope the library works fine with the default
sampling rate and the issue comes only with the custom sampling rate. Am I
right?
Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Subtitle-Synchronizer/jlibrosa/issues/3#issuecomment-721503707,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIGUQIVAWYMM7K55VBCUDLSODJHNANCNFSM4TGZITBA
.

--
Best regards,
Yicheng Ye


Fix two error log related exceptions

Fixed exceptions raised when logging errors from two places:

DebugPort when scanning APs.
Kinetis target class when MDM-AP IDR match fails.

@mbed-bot: TEST


Chromedriver error

I am attempting to scrape and continue to get this error. Any ideas?
Message: session not created: Chrome version must be between 70 and 73
(Driver info: chromedriver=73.0.3683.86,platform=Linux 4.18.0-18-generic x86_64)

Hmm, perhaps you can try installing an older version of chromedriver.


Invalid Search Improvement

On searching something invalid, we can still see the download button. I think it would be more comprehensive to not let the user search the wrong thing in the first place i.e. when they click on the search button there should be a small popup to alert the user that it is invalid, and clear the search input. Please let me work on this issue

You can start working on this issue.

Since someone already added this feature before I could I'm just going to fix this :

and make this area more readable:


Error : Outdated FPS Pattern

Just started appearing after the new 4.3 patch dropped. It limits the game back to 60fps. Requesting to resolve this issue please.

duplicate

duplicate

ok, but how to solve?

duplicate

ok, but how to solve?

download the new version yourself?


how to run qp_spile_path_optimizer during em_planner execution?

Hello.
In the reviewing em_planner.cc, there are many tasks in the RegisterTasks().
But, this function did not take qp_spline_path_optimizer.
where is it? and how could run this QpSplinePathOptimizer in running time?
After path decider module execution,  this path decision data send to qp_spline_path_optimizer
(Ignore/stop/nudge). but qp_spline_path_optimizer is missing in the run time.
please support this question.
thanks.
void EMPlanner::RegisterTasks() {   task_factory_.Register(DP_POLY_PATH_OPTIMIZER,                          []() -> Task* { return new DpPolyPathOptimizer(); });   task_factory_.Register(PATH_DECIDER,                          []() -> Task* { return new PathDecider(); });   task_factory_.Register(DP_ST_SPEED_OPTIMIZER,                          []() -> Task* { return new DpStSpeedOptimizer(); });   task_factory_.Register(SPEED_DECIDER,                          []() -> Task* { return new SpeedDecider(); });   task_factory_.Register(QP_SPLINE_ST_SPEED_OPTIMIZER, []() -> Task* {     return new QpSplineStSpeedOptimizer();   });   task_factory_.Register(POLY_ST_SPEED_OPTIMIZER,                          []() -> Task* { return new PolyStSpeedOptimizer(); }); }

It seems we only implement QpSplinePathOptimizer, but not invoke in running time for less elapsed time.  If I'm not right ,please correct me @jiangtao and liangliang

@jiangtao
Hello.
In the reviewing em_planner.cc, there are many tasks in the RegisterTasks().
But, this function did not take qp_spline_path_optimizer.
where is it? and how could run this QpSplinePathOptimizer in running time?
After path decider module execution, this path decision data send to qp_spline_path_optimizer
(Ignore/stop/nudge). but qp_spline_path_optimizer is missing in the run time.
please support this question.
thanks.
void EMPlanner::RegisterTasks() { task_factory_.Register(DP_POLY_PATH_OPTIMIZER,  -> Task* { return new DpPolyPathOptimizer(); }); task_factory_.Register(PATH_DECIDER,  -> Task* { return new PathDecider(); }); task_factory_.Register(DP_ST_SPEED_OPTIMIZER,  -> Task* { return new DpStSpeedOptimizer(); }); task_factory_.Register(SPEED_DECIDER,  -> Task* { return new SpeedDecider(); }); task_factory_.Register(QP_SPLINE_ST_SPEED_OPTIMIZER,  -> Task* { return new QpSplineStSpeedOptimizer(); }); task_factory_.Register(POLY_ST_SPEED_OPTIMIZER,  -> Task* { return new PolyStSpeedOptimizer(); }); }

Currently we are not using qp_spline_path_optimizer so that you don't see it in the config file.

Closing the issue due to no communication. Feel free to re-open the issue if there is follow up questions.


Let user be able to customize cfg for hoverpopup

when hover popup showed up:

set a 'b:lsphoverpopupid' var as popupid to hover popup
set a 'b:lsphovermarkupkind' var as hover markup kind

user can customize setup according to those if needed if so.

to allow or let user have a interface to setup customized option or highlight etc..
// so far, the hover popup looks a bit poor... :-)
what do you think?

set hover popup ft as 'lsphover'
// force pushed a new commit.

to be uniformed if so, and then user can dev he/she preferred syntax/options if so if needed,
or/and would not impact anything if just keep the default (kept current hover as it looked like).
// i think this would be better, pls review/refine, or withdraw/ignore if not-like... :-)

and to fix - hoverReply: type mismatch #6

Thanks for the patch. It will be useful if the plugin, by default, highlights the items in the hover popup. This is not currently implemented. Can you add some help text to describe how a user can use the filetype to highlight the hover popup?

description added. a35dff8

solved code/commit conflict with your last commit, now should be clear and direct to merge if ok. thx.


Backend: Login Step 2

@SalamanderHP @sagara11 pls review my pr, especially the second commit

@SalamanderHP @sagara11 pls review my pr, especially the second commit

@kkinggmann just merge them into one for simpler total review

@SalamanderHP done


Tidy cleanup

This change copies the .clang-tidy file from https://github.com/googleapis/google-cloud-cpp-spanner/blob/master/.clang-tidy
The only difference is that for this project we disable the google-runtime-int check, which suggests avoiding types like long and long long in favor of explicitly sized types like std::int64_t. However, it appears that the curl library requires that are specifically long or long long, so keeping this warning would require lots of NOLINT, which simply doesn't seem worth it.
FWIW, I've always found this particular warning to be of dubious value anyway, so I don't mind turning it off.

This change is

PTAL. I disabled the google-runtime-int check, and reverted all those changes.


Revert "[JENKINS-47510] RemoteLauncher.isUnix() is not overridden - always returns master OS"

Reverts jenkinsci/ssh-slaves-plugin#168

Why was it removed? Not released so far tho

the code runs on the Master so the OS detection is not good :(


Use babel-register in readme

babel-core/register is deprecated (and other samples in the readme uses babel-register)

Changes Unknown when pulling c624a4db2bedfdb48b8137b4fc9967d87deca53b on SimenB:patch-1 into ** on istanbuljs:master**.


Inference issue

I encounter this while predicting.

Hi @Va6lue,
I have made some updates to dataset.py. Please let me know if the issue still exists.

I can see the progress bar begins at 0%.

However, I find out that my 32GB RAM explodes just in a few seconds, so I terminate the process.

Typically, predict.py won't consume 32GB of memory unless it is dealing with large video inputs. Based on your description, I require more information to assist you effectively. Specifically, I need additional details about any error messages, your input video, and your environment setup. Providing this information will help me better understand your issue and offer accurate assistance.

My input video file is 1920x1080, 25fps and only 7 seconds. This kind of memory explosion occurs on my two systems. Unfortunately, there is no any error message coming out. The process gradually consumes all the system memory in a few seconds, and causes system stutters.
System 1 (i5-11400, 16GB RAM, RTX 3060 12GB):
Windows 11 (latest version)
Python 3.11.7 64bit
PyTorch 2.1.2+cu121
:::spoiler
Package                   Version

absl-py                   2.1.0
addict                    2.4.0
albumentations            1.4.0
anyio                     4.2.0
argon2-cffi               23.1.0
argon2-cffi-bindings      21.2.0
arrow                     1.3.0
asttokens                 2.4.1
async-lru                 2.0.4
attrs                     23.2.0
Babel                     2.14.0
beautifulsoup4            4.12.3
bleach                    6.1.0
cachetools                5.3.2
certifi                   2022.12.7
cffi                      1.16.0
charset-normalizer        2.1.1
colorama                  0.4.6
comm                      0.2.1
contourpy                 1.2.0
cycler                    0.12.1
debugpy                   1.8.0
decorator                 4.4.2
defusedxml                0.7.1
et-xmlfile                1.1.0
executing                 2.0.1
fastjsonschema            2.19.1
filelock                  3.9.0
fonttools                 4.49.0
fqdn                      1.5.1
fsspec                    2023.4.0
gitdb                     4.0.11
GitPython                 3.1.42
google-auth               2.27.0
google-auth-oauthlib      1.2.0
grpcio                    1.60.0
idna                      3.4
imageio                   2.34.0
imageio-ffmpeg            0.4.9
ipykernel                 6.29.0
ipython                   8.20.0
ipywidgets                8.1.1
isoduration               20.11.0
jedi                      0.19.1
Jinja2                    3.1.2
joblib                    1.3.2
json5                     0.9.14
jsonpointer               2.4
jsonschema                4.21.1
jsonschema-specifications 2023.12.1
jupyter                   1.0.0
jupyter_client            8.6.0
jupyter-console           6.6.3
jupyter_core              5.7.1
jupyter-events            0.9.0
jupyter-lsp               2.2.2
jupyter_server            2.12.5
jupyter_server_terminals  0.5.2
jupyterlab                4.0.11
jupyterlab_pygments       0.3.0
jupyterlab_server         2.25.2
jupyterlab-widgets        3.0.9
kiwisolver                1.4.5
lazy_loader               0.3
Markdown                  3.5.2
MarkupSafe                2.1.3
matplotlib                3.8.3
matplotlib-inline         0.1.6
mistune                   3.0.2
moviepy                   1.0.3
mpmath                    1.3.0
nbclient                  0.9.0
nbconvert                 7.14.2
nbformat                  5.9.2
nest-asyncio              1.6.0
networkx                  3.0
notebook                  7.0.7
notebook_shim             0.2.3
numpy                     1.26.3
oauthlib                  3.2.2
opencv-python             <IP_ADDRESS>
opencv-python-headless    <IP_ADDRESS>
openpyxl                  3.1.2
overrides                 7.6.0
packaging                 23.2
pandas                    2.2.1
pandocfilters             1.5.1
parse                     1.20.1
parso                     0.8.3
Pillow                    9.3.0
pip                       24.0
platformdirs              4.1.0
proglog                   0.1.10
prometheus-client         0.19.0
prompt-toolkit            3.0.43
protobuf                  4.23.4
psutil                    5.9.8
pure-eval                 0.2.2
pyarrow                   15.0.0
pyasn1                    0.5.1
pyasn1-modules            0.3.0
pycocotools               2.0.7
pycparser                 2.21
Pygments                  2.17.2
pyparsing                 3.1.1
python-dateutil           2.8.2
python-json-logger        2.0.7
pytz                      2023.3.post1
pywin32                   306
pywinpty                  2.0.12
PyYAML                    6.0.1
pyzmq                     25.1.2
qqdm                      0.0.7
qtconsole                 5.5.1
QtPy                      2.4.1
qudida                    0.0.4
referencing               0.32.1
requests                  2.31.0
requests-oauthlib         1.3.1
rfc3339-validator         0.1.4
rfc3986-validator         0.1.1
rpds-py                   0.17.1
rsa                       4.9
scikit-image              0.22.0
scikit-learn              1.4.1.post1
scipy                     1.12.0
seaborn                   0.13.2
Send2Trash                1.8.2
setuptools                65.5.0
six                       1.16.0
smmap                     5.0.1
sniffio                   1.3.0
soupsieve                 2.5
stack-data                0.6.3
sympy                     1.12
tensorboard               2.15.1
tensorboard-data-server   0.7.2
terminado                 0.18.0
thop                      0.1.1.post2209072238
threadpoolctl             3.3.0
tifffile                  2024.2.12
tinycss2                  1.2.1
torch                     2.1.2+cu121
torchaudio                2.1.2+cu121
torchvision               0.16.2+cu121
tornado                   6.4
tqdm                      4.66.1
traitlets                 5.14.1
types-python-dateutil     <IP_ADDRESS>40106
typing_extensions         4.4.0
tzdata                    2023.4
uri-template              1.3.0
urllib3                   1.26.13
wcwidth                   0.2.13
webcolors                 1.13
webencodings              0.5.1
websocket-client          1.7.0
Werkzeug                  3.0.1
widgetsnbextension        4.0.9
:::
System 2 (R7-7700, 32GB RAM, RTX 4090 24GB):
Windows 11 (latest version)
PyTorch 2.X+cu121 (I forgot, maybe 2.2.1)

In predict or test has a code "frame_list, fps, (w, h) = generate_frames(args.video_file)", and this will get all frames from video, which is saved in a cache list, may get the RAM out of memory.

In predict or test has a code frame_list, fps, (w, h) = generate_frames(args.video_file), and this will get all frames from video, which is saved in a cache list, may get the RAM out of memory.

We have the same issue when using Tracknetv3 with a full 50 minutes badminton match video. The line frame_list, fps, (w, h) = generate_frames(args.video_file) eats up to 400G of RAM (on the server) before crashing (ie. not enough RAM remaining to charge all the frames). We're trying to make a sliding windows, to charge chunks of videos instead of the whole video and feed generate_frames(args.video_file) with these chunks.

Hi @Geoffroy-Berthelot,
Sorry for the late response. I've added an IterableDataset to address the OOM issue during large video inference.
You can find more details here.
If you have any further questions, please let me know.

Now using --large_video can infer successfully, but the inference speed is slow.
However, there is another problem in the inference result. I find out that the "Visibility" is always 1, even though there is no shuttlecock in the specific frame or even the frames in a period of time.

Hi @Va6lue,
About the inference speed, I am still searching a better implementation. If you have any advice, it would be greatly appreciated.
For "Visibility," in our implementation, it will be 1 when either the "X" or "Y" coordinate of the shuttlecock is greater than 0. Do you mean that you have results where "Visibility" is 1 while both "X" and "Y" are 0? Or are you suggesting that the model mistakenly detects another object as the shuttlecock? I may need some examples to better understand the problem.

Yeah, there are X and Y coordinate values both greater than 0 when the "Visibility" is 1.
The scenario is that when the inference frames don't have any shuttlecocks (we can easily determine where the shuttlecocks should be or even shouldn't be there), the model still predicted them for example in my case (X, Y) = (609, 178). Moreover, I found out that these faulse predictions (X, Y) are usually stuck at (609, 178) on my 720p video, but the other version of "TrackNetV3" with a different model architecture also based on TrackNetV2 infering the same 720p video can give a correct "Visibility"=0 in some cases that there isn't any shuttlecock actually there.
Although this isn't a big problem.


Improve TorByDefault

Most basics for TorByDefault #2056 got covered with the realease of v1.7 .. for v1.7.1 there are some special cases to look into again and to improve:

[ ] https://github.com/rootzoll/raspiblitz/issues/1341
[ ] https://github.com/rootzoll/raspiblitz/issues/2013
[ ] https://github.com/rootzoll/raspiblitz/issues/2054
[ ] use a pihole/wireshark to analyse where we still have clearnet leakage when using apps & features
[ ] check if the Tor Install during recover/update can now be removed (because its done already by build-script) to save on time

Would also like to see an option to enable ipv4/ipv6 in addition to tor instead of it just being a binary tor-only option. I'd like the option to have my node be as available as possible.

@maxgoldberg basically that makes sense to have that option, but because of time i dont think we will be focus on this already for the v1.7.1. and the v1.8 also has mainly focus on UI/UX - so I created this as an issue for v1.8.1 - see: #2259
But of course you can already manually config your LND under SYSTEM > LNDCONF .. please share your experiences in adding more networks manually in this new issue: #2259

@rootzoll and would be great to give the option to connect to a mobile wallet using IPv6  (public IP) or TOR by choice if both options are activated

On the tor branch 2669tor where I merged now the tor changes with the changes on dev I was able to build a new sd card and setup a fresh LND node with it - but LND in the end is not able to start (wallet unlock, shutdown, repeat).
The error in the logs is: unable to initialize tor controller: unable to connect to Tor server: dial tcp <IP_ADDRESS>:9051: connect: connection refused
While sudo systemctl status tor@default is showing a long running and 100% bootstraped tor service.
@nyxnor @openoms any quick hint what to check?

check the torrc
the tor cookie needa to be group readable
and
add the bitcoin user to the debian-tor group

Thanks was a good hint ... I had a typor that didnt triggered the tor enable part and so missed to edit the torrc.

OK Tor seems now working for LND in branch 2388redis-tor-dev-merge
@nyxnor but looking into the /etc/tor/torrc after enable I see the line that looks a bit like a broken path, is that correct that way?
%include /mnt/hdd/app-data/tor//torrc.d

it is wrong, it should have no trailing '/ or tor_conf_dir
https://github.com/rootzoll/raspiblitz/blob/42593a94f06180992b8253ba639f6a225b63aa9f/home.admin/config.scripts/tor.install.sh#L26
correct:
tor_conf_dir="${hdd_path}/app-data/tor"

OK looks better now %include /mnt/hdd/app-data/tor/torrc.d


Release 1.0.1-rc2 as 1.0.1

Hey, would it possible to publish 1.0.1-rc2 as 1.0.1? Currently, if you use the rc-2 version and use dependabot, it tries to update this version to the latest nightly alpha versions (because you use a rc version). This results into weekly PRs for each repository promoting a nightly version.
You want to use this RC version (1.0.1-rc2), because it supports Kotlin 1.6.10.

We are going to release 1.0.1 very soon(few days), unless some critical issues are found in 1.0.1-rc2

Done

@akurasov Is there deliberately no changelog for the version or was it forgotten?

@felixdivo thank you, nice point. There are no major changes besides switching to a new Kotlin. But anyway I added it to CL.

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


fix: apply filters to alerts cache correctly

The alerts cache was missing a step that's present in the V3 API which meant that filters were not being applied to the list of all alerts correctly producing the wrong results.
This change adds a test suite to verify that filters work as expected and adds the additional step of expanding built matchers so partial matches are considered a match.

the old tests for build_matchers seem like they're testing an implementation detail — are they still providing some value above and beyond the filter_by tests?

@digitalcora You're totally right. build_matchers was a private function a while back. I've made it private again and removed those test cases. They were helpful while I wrote that code but isn't really behavior we need to test anymore.


Replace create-test-git-repo.sh with Rust so tests run on Windows

With some luck this will also pass in Windows CI 🤞 (I wrote this code on a Mac)

quick shoutout to https://docs.rs/xshell/0.2.2/xshell/ and the xtask solution

Thanks for the tips! I've heard loosely about them before, but I try to stay as vanilla as possible for as long as possible, since I like things to be as simple as possible. Not least because it lower the barrier for new contributors.
But when things start to get out of hands, those are definitely things to consider.
In this case I think the Rust version doesn't look too bad (and now CI passes also on Windows for many more tests 🎉 )

if we gate diff_public_items_with_dirty_tree_fails so it's only ran on linux, we can enable macos too now for the tests
I think that was the only reason I didn't include macos in cargo test

Hmm the test passes on my Mac though. Let's first see what happens if we simply just add mac.

Hmm the test passes on my Mac though. Let's first see what happens if we simply just add mac.

Yes mine too :3

The mac failure seems to have been caused by a different git version or config that printed a shorter error message to stdout. I changed the assert (to something that I think is also ok) and now the test pass also in Mac CI and still on my local Mac.


Bug - webhook for transaction_created throws a type error if transaction includes return label

it still marks the first transaction as shipped, but if there is a return label, a second request comes in and that throws
we are not really doing anything with that transaction so this is more of a annoyance...

re-opening, this is still happening at random


refactor: reposition Expect() to below errors, in providers_test.go

If an unexpected error occurs, got will be nil and the Expect(got).To... will fail, halting the test execution.
That means that the Expect(err != nil) won't be executed, resulting in confusing errors (error will fail for unmatched got instead than unexpected error).

Thanks @ziccardi for the explanation


A RenderFlex overflowed by 99911 pixels on the bottom.

I am creating an E_commerce app and Whenever I click on the "Add to Cart" button it shows me, 'RenderFlex overflowed by 99911 pixels on the bottom' I have tried to wrap it in Expanded but it doesn't work for me, please any help...

.

Please ask support questions on StackOverflow. Closing from here.


Eager Loading with it

Hey, can you give me a advice, how make Eager Loading on my model with it?

What do you want to eager load?

On my model Article, Course and User. Because i want to show user, how many viewers they have on all courses.

Whoops... I answered this yesterday, but it looks like that I forgot to click on comment.
Eager loading the views relationship will only make it slower, because the counting is done with SQL's aggregrate methods.

Hm.. what do you recommend me? I have above 100 request on view. I want to collect unique views for user articles, courses and author page.

Caching the views count value for a while can make the application faster, that's why I added caching functionality to v2.0.0, but this version will isn't released yet. I have planned it on May 28, 2018.
How long does it take to the load the page at the moment?

above 1 sec and still rise

Is it a really important requirement to make the page load faster at the moment? Because I can release a betá version of v2 so you can use it. You will need to upgrade the application of course.
If you have the time, you could test version 2 and check if it fixes the speed problem for you.
I think just changing the version number to dev-2.0.0  in composer.json would do the job. I suggest you to create a new branch, so you can rollback the changes.
https://github.com/cyrildewit/laravel-page-view-counter/tree/2.0
https://github.com/cyrildewit/laravel-page-view-counter/blob/2.0/UPGRADING.md


installation of sphinx=3.0.3 failed

The Sphinx-dft installation failed. For now, I changed the version to 2.7.0. The error is as below:
package sphinxdft-3.0.3-h62cddd8_0 requires mkl >=2021.2.0,<2022.0a0, but none of the providers can be installed

Is this still the case?

Yes, I wanted to contact Christoph about it. But I need to dig deeper to see what exactly the error is first.

Maybe this is related to https://github.com/pyiron/pyiron_atomistics/issues/311


Change URL to site in GitHub

Currently, it reads blogpoole.herokuapp.com. Change to jekyll.pizza

updated to http://jekyll.pizza


linux: 4.4.23 -> 4.4.24

Motivation for this change
Update kernel
Things done

[X] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] OS X
[ ] Linux

[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

We should port this into 16.09 as well as this is the default kernel

All stable kernel bumps should go into 16.09


Pod install | static linking issue | RCT Folly | Turbo modules

Description
We were notified of a customer facing issues when trying to pod install in the iOS directory of their react native project. The issue read -
[!] The following Swift pods cannot yet be integrated as static libraries:

The Swift pod `klaviyo-react-native-sdk` depends upon `RCT-Folly.common`, which does not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set `use_modular_headers!` globally in your Podfile, or specify `:modular_headers => true` for particular dependencies.

Although, we were unable to reproduce this error in our test app even after updating our podfile to match the customers, we tried to dig into the issue and it turns out that RCT-Folly. is an objective c library that was getting pulled in as one of our dependency because we were trying to get turbo modules to work.
As a solution,

since we are not currently using turbo modules, I've updated our podspec to not include that as a dependency
Further, just as a safely check I've added a line to our podspec that would allow swift and objective c interoperability if in the future we ended up pulling in objective c libraries.

Check List

[ ] Are you changing anything with the public API?
[ ] Are your changes backwards compatible with previous SDK Versions?

Changelog / Code Overview

Test Plan
Once I get this PR in I'll use the npm install with a commit and test it locally and make sure our internal test app is able to pull in dependencies with cocoapods and works as expected. I will test it with a few version of react native to be sure that this works on all versions.
 Better to do the formal testing before merging so that I can fix any issue right here.

Testing on the below RN versions and posting the results of pod install. Please note that this doesn't indicate that we support all of these versions at the moment but mostly indicating that pod install works on these versions.

React native version
pod install Result

0.68.7
✅

0.69.12
✅

0.70.15
✅

0.71.15
✅

0.72.10
✅

0.73.3
✅

I tried running the example RN project in this repo from the master branch and hit a bunch of different errors with running yarn ios (yarn android was fine). Pulling down the changes from this branch resolved all the pod issues, nice work! 🎊
Let me know if you want me to run anything from my end to try hunting down what's driving the breakage in master.

Thanks for chiming in @lightstrike, if you wouldn't mind sharing your npx react-native info and any of the error messages you hit that may help us understand more going forward. In our environments, the example app builds on master, so we've been having trouble reproducing. But we are glad to hear that this branch fixed it for you! We'll keep you posted when this gets into an official release.

Sure thing @evan-masseau, here's the output of npx react-native info when running the example on the master branch:
System:
  OS: macOS 14.2.1
  CPU: (10) arm64 Apple M1 Max
  Memory: 85.81 MB / 32.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 18.4.0
    path: ~/.nvm/versions/node/v18.4.0/bin/node
  Yarn:
    version: 3.6.1
    path: ~/.nvm/versions/node/v18.4.0/bin/yarn
  npm:
    version: 8.12.1
    path: ~/.nvm/versions/node/v18.4.0/bin/npm
  Watchman: Not Found
Managers:
  CocoaPods:
    version: 1.14.3
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.2
      - iOS 17.2
      - macOS 14.2
      - tvOS 17.2
      - watchOS 10.2
  Android SDK: Not Found
IDEs:
  Android Studio: 2023.1 AI-231.9392.1.2311.11255304
  Xcode:
    version: 15.1/15C65
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.9
    path: /opt/homebrew/opt/openjdk@17/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.73.1
    wanted: 0.73.1
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false

info React Native v0.73.3 is now available (your project is running on v0.73.1).
info Changelog: https://github.com/facebook/react-native/releases/tag/v0.73.3
info Diff: https://react-native-community.github.io/upgrade-helper/?from=0.73.3
info For more info, check out "https://reactnative.dev/docs/upgrading?os=macos".

Here's the current error thrown by yarn ios (linked as it's a lot, hopefully helpful!). Let me know if you want me to check anything else.

Thanks @lightstrike, ultimately the error seems to be from RCTThirdPartyFabricComponentsProvider.mm which I think is part of what Ajay is taking out in this PR. It does appear to be related to the issue that prompted us to draft this PR in the first place.
Unfortunately I still can't reproduce it myself despite the fact that according to the output from our npx react-native info being basically identical. Here are the steps I took with a clean clone of the repository:

clean clone of the repo
yarn install in project roo
cd example/ios
pod install

Note, using yarn pod-install created an erroneous xcode.env.local file with a bad path to node binary, so I opt for using pod install.

Also note that this pod install modified the pod lockfile to bump to v 0.1.1 of the Klaviyo SDK, something we should update in version control

yarn ios -- takes a while to build project, but succeeds.

We certainly aren't giving up on understanding the issue, but I think this PR will have to be our first step. We're just doing a little more testing before we merge and release this.
Thanks again for your active help. If there were any differences in how you installed and tested the example, let me know. There are often several ways to do the same things with RN, so a minor difference might give us a clue!

The discovery about yarn pod-install generating an erroneous local xcode config file has finally allowed me to fix our Github Action that compiles the example app on iOS, see #75. That will be a nice sanity check going forward that in a clean environment our example app does in fact compile and launch on both platforms.

Fixed conflicts


[bug] Unable to mark dead node as failed node to remove it

Before submitting a bug please read: https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/bug_report
Version
Build/Run method

[X] Docker
[ ] PKG
[ ] Manually built (git clone - npm install - npm run build )

docker image: zwavejs/zwavejs2mqtt:dev  (0c5cfa16d4a2)
zwavejs2mqtt version:  1.0.0-rc.1
zwavejs version: 6.0.0
Describe the bug
When trying to remove a dead not, marking it as failed and then removing the failed node, I get the following error:
Node 45 is not in the list of failed nodes removeFailedNode

To Reproduce
Steps to reproduce the behavior:

Click on the dead node
Select "Is Failed Node" from the drop-down menu and click Send
Observe successful API call with info notice
Click on the node again and select "Remove failed node" and click Send
Observe failed API call with error notice

Expected behavior
The failed node should be removed.
Additional context
2021-01-22 10:44:42.737 INFO APP: Zwave api call: isFailedNode [ 45, [length]: 1 ]
2021-01-22 10:44:42.748 INFO ZWAVE: Success zwave api call isFailedNode
2021-01-22 10:44:54.021 INFO APP: Zwave api call: removeFailedNode [ 45, [length]: 1 ]
2021-01-22 10:44:55.243 INFO ZWAVE: The node removal process could not be started due to the following reasons:
· Node 45 is not in the list of failed nodes removeFailedNode

@larstobi I think that if you try to use zwavejs 6.0.1 it should work. It has been released yesterday and I forgot to bump it! It has added a ping to automatically detect a node as failed when calling replace/remove failed. Could you try?

@larstobi I think that if you try to use zwavejs 6.0.1 it should work. It has been released yesterday and I forgot to bump it! It has added a ping to automatically detect a node as failed when calling replace/remove failed. Could you try?

Yes, trying now, will report back in an hour or two.

Yes, trying now, will report back in an hour or two.

@robertsLando I have now tried again with 6.0.1, but it still doesn't get removed, although it behaves differently.
In the log:
2021-01-22 15:26:00.268 INFO APP: Zwave api call: isFailedNode [ 45, [length]: 1 ]
2021-01-22 15:26:16.154 INFO APP: Zwave api call: removeFailedNode [ 45, [length]: 1 ]

And I get no notice in the WebUI if the command failed or succeeded.
The node is still there, marked as Dead instead of Removed.

@robertsLando I have now tried again with 6.0.1, but it still doesn't get removed, although it behaves differently.
In the log:
2021-01-22 15:26:00.268 INFO APP: Zwave api call: isFailedNode [ 45, [length]: 1 ]
2021-01-22 15:26:16.154 INFO APP: Zwave api call: removeFailedNode [ 45, [length]: 1 ]

And I get no notice in the WebUI if the command failed or succeeded.
The node is still there, marked as Dead instead of Removed.

@larstobi I suggest to also attach the zwavejs log so we can see what's going on.
cc @AlCalzone

@larstobi I suggest to also attach the zwavejs log so we can see what's going on.
cc @AlCalzone

As always, if something that communicates with the device or controller is not working I need logs.

As always, if something that communicates with the device or controller is not working I need logs.

zwavejs_1.log
zwavejs2mqtt.log.gz

zwavejs_1.log
zwavejs2mqtt.log.gz

@AlCalzone @robertsLando Is this sufficient?

@AlCalzone @robertsLando Is this sufficient?

Can check when I'm back on the computer

Can check when I'm back on the computer

@larstobi not enough, sorry :(
Two problems:

The loglevel isn't high enough (should be silly)
Looks like your stick does something weird:

12:21:24.560 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:22:50.688 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:23:22.439 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:25:48.691 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:25:51.107 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:26:51.346 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:27:04.498 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:27:08.963 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:27:13.533 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:27:24.633 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:27:40.820 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:28:20.977 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:29:51.256 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:31:02.196 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:32:30.988 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.

@larstobi not enough, sorry :(
Two problems:

The loglevel isn't high enough (should be silly)
Looks like your stick does something weird:

12:21:24.560 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:22:50.688 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:23:22.439 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:25:48.691 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:25:51.107 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:26:51.346 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:27:04.498 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:27:08.963 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:27:13.533 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:27:24.633 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:27:40.820 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:28:20.977 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:29:51.256 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:31:02.196 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
12:32:30.988 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.

I have since enabled debug logs. Will upload those soon, and then enable silly.

I have since enabled debug logs. Will upload those soon, and then enable silly.

Debug might be enough I think.

Debug might be enough I think.

@AlCalzone Here you go! Let me know if debug wasn't enough. :-)
zwavejs2mqtt.log.gz
zwavejs_1.log.gz

@AlCalzone Here you go! Let me know if debug wasn't enough. :-)
zwavejs2mqtt.log.gz
zwavejs_1.log.gz

I tried to mark failed and remove failed nodes 45 and 92, just prior to the timestamps "20:11:40".

I tried to mark failed and remove failed nodes 45 and 92, just prior to the timestamps "20:11:40".

I'm not seeing that tbh.
Remove failed first pings the node (I'm not seeing that message go out), and if that comes back negative (because otherwise the node cannot be removed), sends a RemoveFailedNodeRequest to the controller. The only instance of RemoveFailed is in the controller's list of supported commands.

I'm not seeing that tbh.
Remove failed first pings the node (I'm not seeing that message go out), and if that comes back negative (because otherwise the node cannot be removed), sends a RemoveFailedNodeRequest to the controller. The only instance of RemoveFailed is in the controller's list of supported commands.

Hmm, that is weird. So, basically the node ping doesn't go out.
Would a new silly log help?

Hmm, that is weird. So, basically the node ping doesn't go out.
Would a new silly log help?

Wait.... Now, when I refreshed the page of zwavejs2mqtt both Node 45 and Node 92 are in status Removed.

Wait.... Now, when I refreshed the page of zwavejs2mqtt both Node 45 and Node 92 are in status Removed.

@robertsLando Can you make any sense of this?
zwave-js does not have a status "removed"

@robertsLando Can you make any sense of this?
zwave-js does not have a status "removed"

Removed is the state I use for nodes that doesn't exists, them are hidden by default, you need to enable the flag "show hidden nodes" in order to see them

Removed is the state I use for nodes that doesn't exists, them are hidden by default, you need to enable the flag "show hidden nodes" in order to see them

I didn't do anything further. So, something must have worked.
This is the last log line from Node 045 before it was never heard from again:
20:12:41.120 CNTRLR   [Node 045] [Configuration] 8: metadata updated                    [Endpoint 0]

In the zj2m log it says:
grep "Node 45" zwavejs2mqtt.log
2021-01-22 18:06:54.472 DEBUG ZWAVE: Node 45 has been added to nodes array
2021-01-22 18:09:21.781 INFO ZWAVE: Node 45 is dead
2021-01-22 20:12:41.049 INFO ZWAVE: Node 45: value removed: 49-0-Air temperature
2021-01-22 20:12:41.051 INFO ZWAVE: Node 45: value removed: 113-0-Power Management-Battery maintenance status
[...]
2021-01-22 20:12:41.080 INFO ZWAVE: Node 45: value removed: 113-0-System-Hardware status
2021-01-22 20:12:41.082 INFO ZWAVE: Node 45: value removed: 112-0-1
[...]
2021-01-22 20:12:41.092 INFO ZWAVE: Node 45: value removed: 112-0-8
2021-01-22 20:12:41.094 INFO ZWAVE: Node 45: metadata updated: 49-0-Air temperature
[...]
2021-01-22 20:12:41.104 INFO ZWAVE: Node 45: metadata updated: 113-0-Power Management-Battery maintenance status
2021-01-22 20:12:41.106 INFO ZWAVE: Node 45: metadata updated: 113-0-System-Hardware status
2021-01-22 20:12:41.108 INFO ZWAVE: Node 45: metadata updated: 112-0-1
[...]
2021-01-22 20:12:41.121 INFO ZWAVE: Node 45: metadata updated: 112-0-8
2021-01-22 20:12:41.241 INFO ZWAVE: Node 45: removed

So, maybe it wasn't so dead afterall, but still managed to get removed.
Node 92 is 100% dead, I have physically verified it. It got removed a good while after I tried to remove it, like 49 minutes after:
2021-01-22 18:06:54.559 DEBUG ZWAVE: Node 92 has been added to nodes array
2021-01-22 18:19:42.248 INFO ZWAVE: Node 92 is asleep
2021-01-22 21:04:46.705 INFO ZWAVE: Node 92: removed

I didn't do anything further. So, something must have worked.
This is the last log line from Node 045 before it was never heard from again:
20:12:41.120 CNTRLR   [Node 045] [Configuration] 8: metadata updated                    [Endpoint 0]

In the zj2m log it says:
grep "Node 45" zwavejs2mqtt.log
2021-01-22 18:06:54.472 DEBUG ZWAVE: Node 45 has been added to nodes array
2021-01-22 18:09:21.781 INFO ZWAVE: Node 45 is dead
2021-01-22 20:12:41.049 INFO ZWAVE: Node 45: value removed: 49-0-Air temperature
2021-01-22 20:12:41.051 INFO ZWAVE: Node 45: value removed: 113-0-Power Management-Battery maintenance status
[...]
2021-01-22 20:12:41.080 INFO ZWAVE: Node 45: value removed: 113-0-System-Hardware status
2021-01-22 20:12:41.082 INFO ZWAVE: Node 45: value removed: 112-0-1
[...]
2021-01-22 20:12:41.092 INFO ZWAVE: Node 45: value removed: 112-0-8
2021-01-22 20:12:41.094 INFO ZWAVE: Node 45: metadata updated: 49-0-Air temperature
[...]
2021-01-22 20:12:41.104 INFO ZWAVE: Node 45: metadata updated: 113-0-Power Management-Battery maintenance status
2021-01-22 20:12:41.106 INFO ZWAVE: Node 45: metadata updated: 113-0-System-Hardware status
2021-01-22 20:12:41.108 INFO ZWAVE: Node 45: metadata updated: 112-0-1
[...]
2021-01-22 20:12:41.121 INFO ZWAVE: Node 45: metadata updated: 112-0-8
2021-01-22 20:12:41.241 INFO ZWAVE: Node 45: removed

So, maybe it wasn't so dead afterall, but still managed to get removed.
Node 92 is 100% dead, I have physically verified it. It got removed a good while after I tried to remove it, like 49 minutes after:
2021-01-22 18:06:54.559 DEBUG ZWAVE: Node 92 has been added to nodes array
2021-01-22 18:19:42.248 INFO ZWAVE: Node 92 is asleep
2021-01-22 21:04:46.705 INFO ZWAVE: Node 92: removed

Hm there's definitely something funky going on. The whole removal process should be a matter of seconds.

Hm there's definitely something funky going on. The whole removal process should be a matter of seconds.

@AlCalzone suggestions about how to debug this or about the root cause? Is it something on my side?

@AlCalzone suggestions about how to debug this or about the root cause? Is it something on my side?

No idea. Doesn't seem like the zwave-js api gets called

No idea. Doesn't seem like the zwave-js api gets called

I'm afraid I have no further way to debug this since both nodes have been removed in the end. At least not until next time I get a dead node or two.

I'm afraid I have no further way to debug this since both nodes have been removed in the end. At least not until next time I get a dead node or two.

I'd say we close this for now. Feel free to reopen when you have the problem again.

I'd say we close this for now. Feel free to reopen when you have the problem again.


Feature/airports

This should be merged after https://github.com/UKHomeOffice/dq-tf-apps/pull/123 and https://github.com/UKHomeOffice/dq-tf-infra/pull/81
This adds the airports pipeline and tests. Note this is separate from the airports-input pipeline and this PR assumes the airports input pipeline has been done first.

Closing due to conflict.


feat: use Ubuntu 22.04

Zephyr toolchain v0.14.1 does not work with Ubuntu 22.04

Thanks for the fix @erikkallen!


release-21.1: changefeedccl: Apply avro schema prefix as a namespace

PR: https://github.com/cockroachdb/cockroach/pull/61734
From release notes:

The WITH avro_schema_prefix option for Avro changefeeds now sets schema.namespace [#61734][#61734] {% comment %}doc{% endcomment %}

@lnhsingh for triage.

Covered by https://github.com/cockroachdb/docs/pull/10292 - closing this issue


upgraded master to latest jboss-ip-bom 6.0.0.CR30

+1 to merge once the build succeeds.

I did test on my local with executing tests and it worked???

I don't think those test failures are related to the ip-bom upgrade. Running the build locally myself to see if it fails.

I wasn't able to reproduce it locally. Will take a look at the Jenkins job and try to fix it.

@dgutierr could you please take a look and merge this one? Test failures are not related to the changes in this PR (I am still investigating the root cause of those failures)

Merged on master


guile-lib: 0.2.8 -> <IP_ADDRESS>

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/guile-lib/versions.
meta.description for guile-lib is: A collection of useful Guile Scheme modules
meta.homepage for guile-lib is: https://www.nongnu.org/guile-lib/
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found <IP_ADDRESS> with grep in /nix/store/ihmdyz9kq9j402djysijlyhsy7g9fgfw-guile-lib-<IP_ADDRESS>
found <IP_ADDRESS> in filename of file in /nix/store/ihmdyz9kq9j402djysijlyhsy7g9fgfw-guile-lib-<IP_ADDRESS>

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

7 total rebuild path(s)

7 package rebuild(s)

First fifty rebuilds by attrpath

guile-lib
guile-reader
guix
gwrap
haunt
skribilo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ihmdyz9kq9j402djysijlyhsy7g9fgfw-guile-lib-<IP_ADDRESS> \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/869e3fb51a864e4780fc0531614edbdd0a404204#guile-lib

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ihmdyz9kq9j402djysijlyhsy7g9fgfw-guile-lib-<IP_ADDRESS>
ls -la /nix/store/ihmdyz9kq9j402djysijlyhsy7g9fgfw-guile-lib-<IP_ADDRESS>/bin

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

6 packages built:

guile-lib
guile-reader
guix
gwrap
haunt
skribilo

Maintainer pings
cc @vyp @foo-dogsquared for testing.

@ofborg test guix


Extension Reload?

Hi isnt the point of hot module reload to not just re complile on changes but to also reload the extension, without the need to reload it on the extension page?
How do I get this working, or do I need to install something like browser-sync?

Duplicatw for #41

Like @rvasilev pointed, duplicated. So, closing.


nft enumeration & measure storage

In case of panic when TokenMetadata Extension and Approval Extension are not implemented

tagging related issues to connect (I missed the connection)
#842 #844

@BenKurrek do you mind having another quick look to make sure things are correct? Need to make sure this is correct when translating to JS SDK.
cc @ailisp was there anything you think should be changed to be in sync with the JS NFT impl?

@austinabell I don't have any so far, this specific PR looks good

going to wait for another approval since I was the last to make a change


Update H1 HTML tags

Background and context
We want to make sure all of the pages on the awesome-azd website have an
 tag for the top header.
Pages to update:

[ ] /awesome-azd/
[ ] /awesome-azd/about/

Currently, the header on both pages is set to  for the gradient style in "Template Library". Would prefer that it's enclosed in and
 tag for SEO. For example:
…

Must-fix for build.


Tensorboard is installed, prompted to install repeatedly

Type: Bug
When I run 'Python: Launch Tensorboard' from the command palette, I am prompted with 'The package TensorBoard is required to launch a TensorBoard session. Would you like to install it?'
The package will install into the conda environment 'tf'.
I then run the command palette again, I am prompted to install TensorBoard again. This time, conda states: "# All requested packages already installed."
I have tried the workaround:
Set python.conda to "/home/spawn/miniconda3/bin/conda" - issue persists.
I have removed/reinstalled tensorboard manually with conda and removed/reinstalled manually with pip. - issue persists.
Notes: This is in a conda environment, and may be related to microsoft/vscode-python#10462 or microsoft/vscode-python#21749
microsoft/vscode-python#10462 discussion indicated we should file a new bug to report this.

Test:
Close all active .ipynb files.
Close and reopen VSCode
Disable Jupyter extension. Use 'Reload Required' button
Command Palette > Python: Launch Tensorboard - issue repeats.

This sounds similar to the issue I reported #12420
I am back here because I got stuck with a Tensorboard launch error again, I think I know why, and the root of the cause is the same.
The error I get now is
We failed to start a TensorBoard session due to the following error: Command failed: conda run -n comodgan --no-capture-output python /home/jsaito/.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/get_output_via_markers.py /home/jsaito/.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/printEnvVariables.py EnvironmentLocationNotFound: Not a conda environment: /opt/conda/envs/myenv

This happens when there is a system-installed conda, but I use a separate Mamba install under my home. Specifically, in my case, the correct location of myenv is /home/jsaito/mambaforge/envs/myenv, not /opt/conda/envs/myenv. This is interesting because VSCode Python extension has no problem finding myenv under /home/jsaito/mambaforge. It seems that the Tensorboard integration is not reusing the same logic as the Python extension to find the correct environment location.
I hope this helps to finally fix this bug.

I also have problem starting tensorboard from vs code. When I try Python: Loanch Tensorbaord I get a message: The package TensorBoard is required to launch a TensorBoard session. Would you like to install it? and then when I press Yes I get Could not install tensorboard. If pip is not available, please use the package manager of your choice to manually install this library into your Python environment.. This is strange because both my default base environment has tensorboard               2.4.1  and the one I would like to actually tensorboard               2.6.0  .

@georgemilosh
Please can you share the logs from the python extension
What version of Python are you using, what OS and what version of VS Code and Python extension as well.

I am running VS code on a remote linux machine with ssh.
VS code version:
Version: 1.83.1 (Universal)
Commit: f1b07bd25dfad64b0167beb15359ae573aecd2cc
Date: 2023-10-10T23:46:55.789Z
Electron: 25.8.4
ElectronBuildId: 24154031
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 23.0.0

The version of the operating system:
NAME="Ubuntu"
VERSION="20.04.5 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.5 LTS"
VERSION_ID="20.04"

the version of python extension v2023.18.0 along with other related extensions like Jupyter v2023.9.1102792234 , Pylance v2023.10.30 etc.
my .bashrc indicates I am running python with miniconda3

Yeah it something with the python version:
2023-10-19 14:50:15.639 [debug] Cached data exists KeyPrefix=Cache_Method_Output_b._selectIfLaunchedViaActivatedEnv-Args=true
2023-10-19 14:50:15.639 [debug] Clearing context for python dependencies not installed: /net/nfs/ssd2/gmiloshe/tests/tests.ipynb
2023-10-19 14:50:15.639 [debug] Starting new TensorBoard session...
2023-10-19 14:50:15.639 [debug] Ensuring TensorBoard package is installed into active interpreter
2023-10-19 14:50:15.639 [debug] Cached data exists KeyPrefix=Cache_Method_Output_b._selectIfLaunchedViaActivatedEnv-Args=true
2023-10-19 14:50:15.640 [debug] Found cached env for /usr/bin/python3
2023-10-19 14:50:15.640 [debug] Found cached env for /usr/bin/python3
2023-10-19 14:50:15.640 [debug] Resolved /usr/bin/python3 from cache: {"name":"","location":"","kind":"global-other","executable":{"filename":"/usr/bin/python3","sysPrefix":"/usr","ctime":1646236337304,"mtime":1584102020000},"display":"Python 3.8.10 64-bit","version":{"major":3,"minor":8,"micro":10,"release":{"level":"final","serial":0},"sysVersion":"3.8.10 (default, May 26 2023, 14:05:08) \n[GCC 9.4.0]"},"arch":3,"distro":{"org":""},"source":["path env var"],"id":"/usr/bin/python3","detailedDisplayName":"Python 3.8.10 64-bit"}
2023-10-19 14:50:15.642 [debug] Resolved /usr/bin/python3 from cache: {"name":"","location":"","kind":"global-other","executable":{"filename":"/usr/bin/python3","sysPrefix":"/usr","ctime":1646236337304,"mtime":1584102020000},"display":"Python 3.8.10 64-bit","version":{"major":3,"minor":8,"micro":10,"release":{"level":"final","serial":0},"sysVersion":"3.8.10 (default, May 26 2023, 14:05:08) \n[GCC 9.4.0]"},"arch":3,"distro":{"org":""},"source":["path env var"],"id":"/usr/bin/python3","detailedDisplayName":"Python 3.8.10 64-bit"}
2023-10-19 14:50:15.644 [debug] Cached data exists KeyPrefix=Cache_Method_Output_E.ensureEnvironmentContainsPython-Args="/usr/bin/python3"-Arg-Separator-undefined
2023-10-19 14:50:15.704 [debug] Activation Commands received undefined for shell bash
2023-10-19 14:50:15.712 [debug] Activation Commands received undefined for shell bash
2023-10-19 14:50:15.752 [info] > /usr/bin/python3 -c "import tensorboard; print(tensorboard.__version__)"
2023-10-19 14:50:15.783 [info] > /usr/bin/python3 -c "import torch_tb_profiler; print(torch_tb_profiler.__version__)"
2023-10-19 14:50:15.892 [debug] Error when getting version of module tensorboard n [Error]: Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'tensorboard'

    at ChildProcess.<anonymous> (/home/gmiloshe/.vscode-server/extensions/ms-python.python-2023.18.0/out/client/extension.js:2:238843)
    at Object.onceWrapper (node:events:628:26)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1091:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)
2023-10-19 14:50:15.919 [debug] Error when getting version of module torch_tb_profiler n [Error]: Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'torch_tb_profiler'

    at ChildProcess.<anonymous> (/home/gmiloshe/.vscode-server/extensions/ms-python.python-2023.18.0/out/client/extension.js:2:238843)
    at Object.onceWrapper (node:events:628:26)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1091:16)
    at Socket.<anonymous> (node:internal/child_process:449:11)
    at Socket.emit (node:events:513:28)
    at Pipe.<anonymous> (node:net:322:12)
2023-10-19 14:50:25.483 [info] > /usr/bin/python3 -c "import pip"
2023-10-19 14:50:25.613 [debug] Error when checking if module is installed pip n [Error]: Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'pip'

    at ChildProcess.<anonymous> (/home/gmiloshe/.vscode-server/extensions/ms-python.python-2023.18.0/out/client/extension.js:2:238843)
    at Object.onceWrapper (node:events:628:26)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1091:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)
2023-10-19 14:50:25.683 [debug] Activation Commands received undefined for shell bash
2023-10-19 14:50:25.690 [debug] Activation Commands received undefined for shell bash
2023-10-19 14:50:25.727 [info] > /usr/bin/python3 -c "import tensorboard; print(tensorboard.__version__)"
2023-10-19 14:50:25.757 [info] > /usr/bin/python3 -c "import torch_tb_profiler; print(torch_tb_profiler.__version__)"
2023-10-19 14:50:25.864 [debug] Error when getting version of module tensorboard n [Error]: Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'tensorboard'

    at ChildProcess.<anonymous> (/home/gmiloshe/.vscode-server/extensions/ms-python.python-2023.18.0/out/client/extension.js:2:238843)
    at Object.onceWrapper (node:events:628:26)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1091:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)
2023-10-19 14:50:25.893 [debug] Error when getting version of module torch_tb_profiler n [Error]: Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'torch_tb_profiler'

    at ChildProcess.<anonymous> (/home/gmiloshe/.vscode-server/extensions/ms-python.python-2023.18.0/out/client/extension.js:2:238843)
    at Object.onceWrapper (node:events:628:26)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1091:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)
2023-10-19 14:51:34.088 [debug] Cached data exists KeyPrefix=Cache_Method_Output_b._selectIfLaunchedViaActivatedEnv-Args=true
2023-10-19 14:51:34.088 [debug] Clearing context for python dependencies not installed: ms-python.python.Python
2023-10-19 14:51:34.089 [debug] Found cached env for /usr/bin/python3
2023-10-19 14:51:34.089 [debug] Resolved /usr/bin/python3 from cache: {"name":"","location":"","kind":"global-other","executable":{"filename":"/usr/bin/python3","sysPrefix":"/usr","ctime":1646236337304,"mtime":1584102020000},"display":"Python 3.8.10 64-bit","version":{"major":3,"minor":8,"micro":10,"release":{"level":"final","serial":0},"sysVersion":"3.8.10 (default, May 26 2023, 14:05:08) \n[GCC 9.4.0]"},"arch":3,"distro":{"org":""},"source":["path env var"],"id":"/usr/bin/python3","detailedDisplayName":"Python 3.8.10 64-bit"}
2023-10-19 14:51:34.090 [debug] Cached data exists KeyPrefix=Cache_Method_Output_E.ensureEnvironmentContainsPython-Args="/usr/bin/python3"-Arg-Separator-undefined

I would rather it use my miniconda3 environments which have tensorboard

It works

As the originator, is there anything you need me to try?

So sorry,
if anyone else is running into this,
please can you share your python logs as well
See instructions here https://github.com/microsoft/vscode-jupyter/issues/14206#issuecomment-1770911061

@TommyJW
Thank you very much for the logs
Looking at the logs, there seems tobe some errors in the installation of some of the packages
[debug] Error when getting version of module torch_tb_profiler [n [Error]: /usr/bin/bash: /home/spawn/miniconda3/envs/tf/lib/libtinfo.so.6: no version information available (required by /usr/bin/bash)

	at ChildProcess.<anonymous> (/home/spawn/.vscode-server/extensions/ms-python.python-2023.18.0/out/client/extension.js:2:238843)
	at Object.onceWrapper (node:events:628:26)
	at ChildProcess.emit (node:events:513:28)

Q 1. Please can you confirm that tensorboard works property in the same tf conda env.

Please can you try this once again and share the logs from the Python extension
There might be some errors earlier on in the logs indicating the fact that Python extension failed to activate the tf conda environment

Q 1. Please can you confirm that tensorboard works property in the same tf conda env.
I can launch Tensorboard in Simple Browser:

Launch VSCode, which opens the default terminal in (base) environment
Terminal -> "conda activate tf"
Observe Terminal now activated the (tf) environment
Terminal -> "tensorboard --logdir loggingHW4"
Tensorboard begins the process in that terminal.
Navigate to the Ports view, select <IP_ADDRESS>:6006 which is running in /home/spawn/miniconda3/envs/tf/bin/python3.9 /home/spawn/miniconda3/envs/tf/bin/tensorboard --logdir loggingHW4 (6847)
Right click on that line and select Open in Browser.
Tensorboard browser window opens.

Q2 Could you elaborate on what you need? I followed the steps in
https://github.com/microsoft/vscode-jupyter/issues/14206#issuecomment-1770911061
The 4th step is to clear the output. So if you want something earlier in that log, I'll need new steps that detail where to start from.

i have same issue.
log python:
2023-11-12 11:57:00.458 [debug] Ensuring TensorBoard package is installed into active interpreter
2023-11-12 11:57:00.458 [debug] Cached data exists KeyPrefix=Cache_Method_Output_b._selectIfLaunchedViaActivatedEnv-Args=true
2023-11-12 11:57:00.459 [debug] Found cached env for /home/hamze/mambaforge/envs/TensorFlow_pypi/bin/python
2023-11-12 11:57:00.460 [debug] Resolved /home/hamze/mambaforge/envs/TensorFlow_pypi/bin/python from cache: {"name":"TensorFlow_pypi","location":"/home/hamze/mambaforge/envs/TensorFlow_pypi","kind":"virt-conda","executable":{"filename":"/home/hamze/mambaforge/envs/TensorFlow_pypi/bin/python","sysPrefix":"/home/hamze/mambaforge/envs/TensorFlow_pypi","ctime":1699253134407,"mtime":1699253134407},"display":"Python 3.10.13 ('TensorFlow_pypi')","version":{"major":3,"minor":10,"micro":13,"release":{"level":"final","serial":0},"sysVersion":"3.10.13 | packaged by conda-forge | (main, Oct 26 2023, 18:07:37) [GCC 12.3.0]"},"arch":3,"distro":{"org":"Anaconda, Inc."},"source":[],"type":"Conda","id":"/home/hamze/mambaforge/envs/TensorFlow_pypi/bin/python","detailedDisplayName":"Python 3.10.13 ('TensorFlow_pypi': conda)"}
2023-11-12 11:57:00.467 [debug] Found cached env for /home/hamze/mambaforge/envs/TensorFlow_pypi/bin/python
2023-11-12 11:57:00.467 [debug] Resolved /home/hamze/mambaforge/envs/TensorFlow_pypi/bin/python from cache: {"name":"TensorFlow_pypi","location":"/home/hamze/mambaforge/envs/TensorFlow_pypi","kind":"virt-conda","executable":{"filename":"/home/hamze/mambaforge/envs/TensorFlow_pypi/bin/python","sysPrefix":"/home/hamze/mambaforge/envs/TensorFlow_pypi","ctime":1699253134407,"mtime":1699253134407},"display":"Python 3.10.13 ('TensorFlow_pypi')","version":{"major":3,"minor":10,"micro":13,"release":{"level":"final","serial":0},"sysVersion":"3.10.13 | packaged by conda-forge | (main, Oct 26 2023, 18:07:37) [GCC 12.3.0]"},"arch":3,"distro":{"org":"Anaconda, Inc."},"source":[],"type":"Conda","id":"/home/hamze/mambaforge/envs/TensorFlow_pypi/bin/python","detailedDisplayName":"Python 3.10.13 ('TensorFlow_pypi': conda)"}
2023-11-12 11:57:00.468 [debug] Cached data exists KeyPrefix=Cache_Method_Output__.getCondaVersion-Args=
2023-11-12 11:57:00.469 [debug] Found cached env for /home/hamze/mambaforge/envs/TensorFlow_pypi/bin/python
2023-11-12 11:57:00.469 [debug] Resolved /home/hamze/mambaforge/envs/TensorFlow_pypi/bin/python from cache: {"name":"TensorFlow_pypi","location":"/home/hamze/mambaforge/envs/TensorFlow_pypi","kind":"virt-conda","executable":{"filename":"/home/hamze/mambaforge/envs/TensorFlow_pypi/bin/python","sysPrefix":"/home/hamze/mambaforge/envs/TensorFlow_pypi","ctime":1699253134407,"mtime":1699253134407},"display":"Python 3.10.13 ('TensorFlow_pypi')","version":{"major":3,"minor":10,"micro":13,"release":{"level":"final","serial":0},"sysVersion":"3.10.13 | packaged by conda-forge | (main, Oct 26 2023, 18:07:37) [GCC 12.3.0]"},"arch":3,"distro":{"org":"Anaconda, Inc."},"source":[],"type":"Conda","id":"/home/hamze/mambaforge/envs/TensorFlow_pypi/bin/python","detailedDisplayName":"Python 3.10.13 ('TensorFlow_pypi': conda)"}
2023-11-12 11:57:00.470 [debug] Cached data exists KeyPrefix=Cache_Method_Output__.getCondaVersion-Args=
2023-11-12 11:57:00.470 [debug] Found executable within conda env {"name":"TensorFlow_pypi","prefix":"/home/hamze/mambaforge/envs/TensorFlow_pypi"}
2023-11-12 11:57:00.532 [info] > conda run -n TensorFlow_pypi --no-capture-output python ~/.vscode-server/extensions/ms-python.python-2023.21.13141007/pythonFiles/get_output_via_markers.py -c "import tensorboard; print(tensorboard.__version__)"
2023-11-12 11:57:00.533 [debug] Found executable within conda env {"name":"TensorFlow_pypi","prefix":"/home/hamze/mambaforge/envs/TensorFlow_pypi"}
2023-11-12 11:57:00.582 [info] > conda run -n TensorFlow_pypi --no-capture-output python ~/.vscode-server/extensions/ms-python.python-2023.21.13141007/pythonFiles/get_output_via_markers.py -c "import torch_tb_profiler; print(torch_tb_profiler.__version__)"
2023-11-12 11:57:01.224 [debug] Error when getting version of module tensorboard [n [Error]:
EnvironmentLocationNotFound: Not a conda environment: /home/hamze/mambaforge/envs/TensorFlow_pypi/envs/TensorFlow_pypi

	at ChildProcess.<anonymous> (/home/hamze/.vscode-server/extensions/ms-python.python-2023.21.13141007/out/client/extension.js:2:229511)
	at Object.onceWrapper (node:events:628:26)
	at ChildProcess.emit (node:events:513:28)
	at ChildProcess.emit (node:domain:489:12)
	at maybeClose (node:internal/child_process:1091:16)
	at ChildProcess._handle.onexit (node:internal/child_process:302:5)]
2023-11-12 11:57:01.249 [debug] Error when getting version of module torch_tb_profiler [n [Error]:
EnvironmentLocationNotFound: Not a conda environment: /home/hamze/mambaforge/envs/TensorFlow_pypi/envs/TensorFlow_pypi

	at ChildProcess.<anonymous> (/home/hamze/.vscode-server/extensions/ms-python.python-2023.21.13141007/out/client/extension.js:2:229511)
	at Object.onceWrapper (node:events:628:26)
	at ChildProcess.emit (node:events:513:28)
	at ChildProcess.emit (node:domain:489:12)
	at maybeClose (node:internal/child_process:1091:16)
	at Socket.<anonymous> (node:internal/child_process:449:11)
	at Socket.emit (node:events:513:28)
	at Socket.emit (node:domain:489:12)
	at Pipe.<anonymous> (node:net:322:12)]

I guess this problem is due to considering the wrong env location
2023-11-12 11:57:01.224 [debug] Error when getting version of module tensorboard [n [Error]:
EnvironmentLocationNotFound: Not a conda environment: /home/hamze/mambaforge/envs/TensorFlow_pypi/envs/TensorFlow_pypi

I manually entered the conda path in the Python Extension settings, but it had no effect
vscode version:
Version: 1.84.2 (system setup)
Commit: 1a5daa3a0231a0fbba4f14db7ec463cf99d7768e
Date: 2023-11-09T10:51:52.184Z
Electron: 25.9.2
ElectronBuildId: 24603566
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.25992

wsl version:
Distributor ID: Ubuntu
Description:    Ubuntu 23.04
Release:        23.04
Codename:       lunar
kernel:        <IP_ADDRESS>-microsoft-standard-WSL2

Extension version:
ms-python.python=v2023.21.13141007-Pre-Release
ms-toolsai.tensorboard=v2023.10.1002992421-Preview

@TommyJW @Earendilism Please can you install the new Tensorboard extension and very you are still running into this issue?

downgrading python extension fixed it for me

downgrading python extension fixed it for me

@karthiknadig @luabud /cc

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!

Extension 'ms-toolsai.tensorboard' CANNOT use API proposal: portsAttributes. Its package.json#enabledApiProposals-property declares: but NOT portsAttributes. The missing proposal MUST be added and you must start in extension development mode or use the following command line switch: --enable-proposed-api ms-toolsai.tensorboard

Extension 'ms-toolsai.tensorboard' CANNOT use API proposal: portsAttributes. Its package.json#enabledApiProposals-property declares: but NOT portsAttributes. The missing proposal MUST be added and you must start in extension development mode or use the following command line switch: --enable-proposed-api ms-toolsai.tensorboard

same problem.
Extension 'ms-toolsai.tensorboard' CANNOT use API proposal: portsAttributes. Its package.json#enabledApiProposals-property declares: but NOT portsAttributes. The missing proposal MUST be added and you must start in extension development mode or use the following command line switch: --enable-proposed-api ms-toolsai.tensorboard

Extension 'ms-toolsai.tensorboard' CANNOT use API proposal: portsAttributes. Its package.json#enabledApiProposals-property declares: but NOT portsAttributes. The missing proposal MUST be added and you must start in extension development mode or use the following command line switch: --enable-proposed-api ms-toolsai.tensorboard

Same problem. Maybe try to restart the VSCode, which works for me.

Please could you enable logging as follows:

Open settings & go into Jupyter->Logging
Change the value to trace
Reload VS Code,
Attempt to repro the issue & then copy the output from the Jupyter output panel (use the command Jupyter: Show Output to get to the logs).


Corrupted Content Error on localhost:8080/

Good morning,
I just started taking the Developing Progressive Web Apps training course; On runnng the command http-server -p 8080 -a localhost -c 0 inside the responsive-design-lab/app/  I got this error: Corrupted Content Error: The site at http://localhost:8080/ has experienced a network protocol violation that cannot be repaired.. I've cleared the site data  and unregistered all serivce workers buit the error still persist.
Please advise on a forward in resolving it.
Thank you.

Hi iensteins2k, I've not seen that issue before. Often  when I see really strange issues like this it ends up being cause by a browser extension. Could you try disabling your Chrome extensions? (you might be able to do this using Incognito mode, or even try another browser without extensions)
If that doesn't work, I would try resetting as much as possible, consider

checking that you have the specified node version (node --v)
removing and reinstalling your dependencies (rm -rf node_modules && npm install)
try using a different port, in case something else is running on that one (http-server -p 8089 -a localhost -c 0 and visiting http://localhost:8089/

Let me know if none of those fix the issue!

Hi David, I've tried all your recommendations but the issue still persist. Please advise on a way forward.
Thank you.

This is a common problem with Firefox and is often the result of a corrupted cache. Please try the troubleshooting steps suggested by Mozilla support.

See this Stack Overflow question - you can downgrade http-server to 0.9 to fix it - https://stackoverflow.com/questions/56364464/http-server-with-localhost3000-gives-err-invalid-redirect/57536943#57536943

Going to close this issue for now, LMK if its still a problem!


Feature/remove provider

The moved blocks should make upgrading from a previous version of the terraform module pretty smooth.
However one big stumbling block is the removal of the provider block, I was only able to fix this by manually editing state during upgrades, replacing
"provider": "module.meshplatform.provider[\"[registry.terraform.io/hashicorp/azurerm](http://registry.terraform.io/hashicorp/azurerm)"]",
with
"provider": "provider[\"[registry.terraform.io/hashicorp/azurerm](http://registry.terraform.io/hashicorp/azurerm)\"]",
terraform state replace-provider command was not helpful

yup, think that makes sense to add it to them

One thing to do additionally is to execute ./generate_tf_docs.sh to recursively adapt TF docs according to the changes. This will later be replaced by pre-commit config. Otherwise looks good!


Cannot add AES to the Accessibility list of Apps in macOS 14.4.

Describe the bug
I cannot add AES to the Accessibility list of Apps in macOS 14.4.
To Reproduce
Steps to reproduce the behaviour:

Startup AES
Get the following warning...

Go to System Settings -> Privacy and Security -> Accessibility
Note that LES is not listed, and press the + button to add an app.
Navigate to /Applications/Live Enhancement Suite, select it and press OK.

Expected behaviour
I expected LES to be added to the list of apps in the Accessibility list.
Actual behaviour
LES was not added to the Accessibility list which meant that it could not be enabled, thus preventing further installation.
Desktop (please complete the following information):

macOS 14.4 Sonoma
Mac Mini M1 - 16GB

Additional context
Add any other context about the problem here.

for me it appears in the accessibility tab right away but when i launch it it says:
Live Enhancement Suite is only validated to run between macOS 11 and macOS 13 and is currently being run on macOS 14.4.
The program may behave in an undefined manner and may cause disruption but will continue running until prompted to exit.
If you believe this is in error or that the program must be updated to support a newer release of macOS, please file an issue at https://github.com/LiveEnhancementSuite/LESforMacOS/issues.
then hammerspoon opens and gives me the following error:
*** ERROR: ...ite.app/Contents/Resources/extensions/hs/les/LESmain.lua:258: attempt to concatenate a nil value (local 'subfoldername')
stack traceback:
...ite.app/Contents/Resources/extensions/hs/les/LESmain.lua:258: in function 'buildPluginMenu'
...ite.app/Contents/Resources/extensions/hs/les/LESmain.lua:632: in function 'reloadLES'
...ite.app/Contents/Resources/extensions/hs/les/LESmain.lua:664: in main chunk
[C]: in function 'dofile'
/Users/xxx/.les/init.lua:16: in main chunk
[C]: in function 'xpcall'
...uite.app/Contents/Resources/extensions/hs/_coresetup.lua:698: in function 'hs._coresetup.setup'
(...tail calls...)
LES doesnt show up in the control centre and does not work in ableton. i am also on macOS 14.4 Sonoma, macbook air m1

i just got it to work! first of all, delete the current LES and empty your bin. then open Finder - Go to Folder - type ~/.les, hit enter and delete all files in that folder. Restart your mac. Now download v1.3.4.beta.3 and install. Right click - open and it should work.


projects can be named the same

Description
when creating an issue project, there is nothing to restrict the name of the board and thus the same name can be used multiple times
https://try.gitea.io/eeyrjmr/test_issues/projects
Gitea Version
1.17.0+dev-558-g3da9dafc6
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots

Git Version
N/A
Operating System
N/A
How are you running Gitea?
Try.gitea.com
Database
No response

this is a classic question: feature or bug? - we need to decide

It's not name, it's a title at least Gitea think so. So I don't think it's a bug.


⚠ Bofrost.at has degraded performance

In 4922dec, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1265 ms

Resolved: Bofrost.at performance has improved in 1b1fe32.


Allow istioctl version to work w/o --kube=false

The istioctl version currently fails to print the remote apiserver version.  It prints the local version, then "Error: the server could not find the requested resource".  This fixes that bug.

Jenkins job manager/presubmit passed

Jenkins job manager/e2e-smoketest passed


Drop cluster map, refine the filters

Let's stick with a single map view that displays just points (not clusters) and allows filtering based on some some sensible time ranges or windows.
For example:

Last 7 days
Last 30 days
Last 90 days
Current year
Two years
Three years
ALL

created a custom option using flatpickr


Yup resolver problem with test function

Describe the bug
When we use yup schema validation with the test function, the react-hook-form errors object does not return the name of the failed test as key.
  const SignupSchema = yup
    .object()
    .shape({
      firstName: yup.string().required("required")
    })
    .test('test', "test error message", (val) => {
      return val.firstName === "test";
    });

  const { register handleSubmit, formState: { errors } } = useForm({
    resolver: yupResolver(SignupSchema)
  });

  console.log(errors);

Console log results (as you can see, the key is an empty string):
{
    "": {
        "message": "test error message",
        "type": "test"
    }
}

Codesandbox link (Required)
https://codesandbox.io/s/react-hook-form-validationschema-v7-2ik00
Expected behavior
Errors object must be returned with the name of the failed test as key:
{
    "test": {
        "message": "test error message",
        "type": "test"
    }
}

Thanks for you fast reply @jorisre!
So, we cannot have a form level validation management?

Currently no, there is a RFC for your needs https://github.com/react-hook-form/react-hook-form/discussions/6472

Thanks for your replies. I understand that this is an expected behavior of react-hook-form so I close the issue here.


[WIP] EHN/TST advance TTR

TODO:

[ ] More tests
[ ] Documentation

cool. So you don't want to do a PR to master and finish it off?


Missing possibility for error...

I believe that this sentence in the article is incomplete: "This error usually reflects an authentication failure in AD or that the NPS server is unable to receive responses from Azure AD. "
I believe you can also get this error message if the Radius server does not get a response to a secondary authentication prompt from the VPN appliance, e.g., when the authentication message is an SMS one that needs to display a UI in the user's VPN client to enter the requested Azure MFA SMS challenge numbers. The articles explaining how Azure MFA NPS works with VPN solutions fails to note that in some cases, a secondary authentication request may involve the following:

Sending the secondary authentication request to Azure AD
Sending the secondary authentication challenge to the users and sending user data from Azure AD to the Radius server's NPS extension
Sending information to the VPN appliance that will solicit and get the response for the secondary authentication challenge
Receiving the secondary authentication response from the user through the VPN appliance
Sending the response back to Azure AD
Receiving a valid or invalid response back from Azure AD
Sending a valid VPN response back to the VPN appliance if the secondary authentication response is correct
VPN appliance completes the VPN connection.

If I'm correct the articles should cover this scenario and note that when / if the user's VPN client application doesn't support entering data for a secondary authentication challenge (like SMS) then the VPN connection will fail.

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

ID: 5bb8312c-c6d2-d435-15e0-f759234e5a30
Version Independent ID: 4df70af1-b4d6-735d-215a-011a18712529
Content: Troubleshooting Azure AD MFA NPS extension - Azure Active Directory
Content Source: articles/active-directory/authentication/howto-mfa-nps-extension-errors.md
Service: active-directory
Sub-service: authentication
GitHub Login: @Justinha
Microsoft Alias: justinha

@wcneumann219 Thank you for the feedback. I have assigned the issue to the author of the document to review and update.

@wcneumann219 Thanks so much for the clear explanation! Would you kindly submit this as a pull request to the topic?

@wcneumann219 no worries, I will add it. Many readers like to contribute to topics directly by clicking the pencil icon in the upper right corner of the topic. The contribution is saved and submitted as pull request in GitHub and the Reader is listed as a contributor after the pull request is merged. We encourage those direct contributions so just wanted to offer.


Option to import directives in UI resolver?

Related to #152, I'm working on adding a few missing items to the PrimeVue resolver and I would love the ability to add a few directives that it uses.    I like that it can already import the CSS, it'd be great to have it handle the remaining directives for PrimeVue.
I can do a PR for the easier part of updating the resolver, but I'm not sure whether you even want any ability to add directives and if so, how to do that :)
app.directive('tooltip', Tooltip)
app.directive('badge', BadgeDirective)
app.directive('ripple', Ripple)

Thank you for your idea


More convenient "update cargo-dist" workflow

Because cargo-dist-version is baked into your Cargo.toml, you need to remember to update that field to actually get the CI to use a new version. Installing the new version locally on your machine is insufficent. I keep messing this up and forgetting the field!

oh this was implemented in #227


Instant harvest when crop becomes mature

Describe the feature you'd like to have added
Right now using the shadowpulse soil for example, when a crop reaches mature level, it takes some time before it's harvested. Would like a feature where it's instant, something like the harvester pylon
Additional information
No response

I came up with a way to do this which isn't awful :) so yea why not!


Speed up conformance runs with parallelism

This introduces two new flags to the connectconformance runner:

max-servers: the number of concurrent server processes to start. Test cases for all of them will be written to the client's stdin in parallel (thread-safe, but interleaving test cases for various servers). Defaults to 4.
parallel: the number of RPCs to issue in parallel when --mode is server (so this only controls the reference client). In --mode of client, it's up to the client-under-test to implement parallelism. Defaults to 4 * GOMAXPROC (and GOMAXPROC defaults to the number of CPU cores detected).

This speeds up conformance runs on my MBP from about 3 minutes down to less than 15 seconds,.

@smaye81, ping

Nice! Tested this on my machine too and it was much faster.