No simulation showing on first start after changing graphics card on Mac OS High Sierra with Radeon RX 560

Describe the Bug
Middle part of screen stays gray / empty on first start of Webots taking guided tour.
Steps to Reproduce

Download -rw-r--r--@ 1 wf  staff<PHONE_NUMBER> Aug  4 10:24 webots-R2019b.dmg
Install
Start Webots with old graphics card ATI Radeon 5770 1 GB VRAM
Get a complaint that card has not enough ram
Stop computer
Install Radeon RX 560 4 GB VRAM
Restart computer
Restart Webots
Start guided tour
Middle part stays gray while controls seem to run simulation

Expected behavior
Should show simulation.
Screenshots
N/A since on second start of application simulation works.
System

Operating System: [Mac OS 10.13.6 High Sierra]
Graphics Card: [Radeon RX 560]

Additional context
Mac Pro Mid 2010, 12 core, 64 GB RAM

Thank you for your bug report.
If I understand well, you can now start Webots smoothly. Only the first startup leads to a crash.

If it's the case, a new GPU installation may have trick the Webots startup settings causing a crash. We won't investigate this issue further as this is an uncommon case.

If this is not the case, could you try:

To run Webots in safe mode. This will set the GPU settings at minimum, and open Webots on an empty world:
 export WEBOTS_SAFE_MODE=true
 cd /Applications/Webots
 ./webots

To determine if Webots detects successfully your freshly installed GPU by running the Webots sysinfo:
 cd /Applications/Webots
 ./webots --sysinfo

To determine if other applications using OpenGL are working.

@fabienrohrer  - thx for the swift reply.
The software did not crash. It simply didn't show anything in the middle of the screen. Another Open GL app might haven been EPIC Games launcher which I am going to deactivate for future tests.

./webots --sysinfo
System: Darwin 17.7.0 x86_64
Processor: Intel(R) Xeon(R) CPU           X5690  @ 3.47GHz
Number of cores: 24
OpenGL vendor: ATI Technologies Inc.
OpenGL renderer: AMD Radeon RX 560 OpenGL Engine
OpenGL version: 2.1 ATI-1.68.22

Ok, I seems worth to test the safe mode mentioned above:
export WEBOTS_SAFE_MODE=true
cd /Applications/Webots
./webots

I'll try it for #784

see #784

I explain this bug by the GPU switch. Reinstalling cleanly the OS is certainly the solution.


1655 Fix Search input suggestions and search history

Thank you for your contribution to the KodaDot NFT gallery.
👇  _ Do a quick check before the merge.
PR type

[x] Bugfix
[ ] Feature
[ ] Refactoring

Before submitting Pull Request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main-nuxt and I've no conflicts
[x] I've tried respect high code quality standards
[x] I've didn't break any original functionality
[ ] I've posted screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </rmrk/collection/26902bc2f7c20c546a-1FVG7>
[ ] I've tested PR on mobile and everything seems works
[ ] I found edge cases

What's new?

[x] PR closes #1715
[x] Added client option in apollo manual query.

Had issue bounty label ?

[x] Fill up your KSM address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot

[x] My fix has changed something on UI, a screenshot is best to understand changes for others.

Works when I search

But doesn't work when I'm coming from previous search

and it opens me wrong results on different string

Try yourself https://deploy-preview-1715--koda-nuxt.netlify.app/rmrk/gallery?search=kusama

@yangwao I have fixed the history issue also, can you check once again. If have also tested if from my side. If there is still any issue, can you please send me small video so that I can reproduce it on my side easily.

@yangwao I have fixed the history issue also, can you check once again. If have also tested if from my side. If there is still any issue, can you please send me small video so that I can reproduce it on my side easily.

Please update PR template and all needed stuff to proceed

@yangwao I have fixed the history issue also, can you check once again. If have also tested if from my side. If there is still any issue, can you please send me small video so that I can reproduce it on my side easily.

Please update PR template and all needed stuff to proceed

sure @yangwao

Perfect, I’ve sent the payout https://kusama.subscan.io/extrinsic/0x1c9ffac9f4eb4caf128eb246b33ddd6b81ac909aff8ece44e2b383c60f4dbe88
Let’s grab another issue and get rewarded!
https://github.com/kodadot/nft-gallery/issues/


Fix regressions in lcow.CreateScratch

@jstarks - This isn't complete. I can't understand it yet but I always get a -1 error response from the invocation of hcsoci.Cmd.Run for the lcowUVM. But these are at least some of the fixes

Hmm, OK. Do we not have tests for this path? I was relying on our automated testing...

LGTM

Figured this out. Was a regression on OpenGCS. Will link once fixed.


Make Browse Great Again ★★★

Middleware browse has been refactored for better maintainability and extendability. As a result features that had been in one format are carried over to all other.
The outstanding cause for much grief—datetimes shown to visitors in the "wrong" format ('wrong' being a mismatch between expected format and what Caddy delivers)—has been addressed by delegating its formatting to the visitor's browser.
Standardizing the timezone of all returned datetime instances on UTC, and not depending on filesystem implementation details when sorting any directories, yields a well-defined user experience no matter where and on what system Caddy is actually deployed.

It's easier to review every commit one by one instead of all in one go.

I do kind of miss seeing the modified times in local time. They seem to be UTC now. Is there a way to make it local time?

The JS ought do the translating and show it in your timezone.

I would have thought so too, but unfortunately it's not. I just made a file to test it out, and it's 7:10 PM right now. The time shows up as 1:10 AM...

I don't know a way to accomplish that right now. But with the old version, if you were to upload that file to a server that runs under UTC (which is a industry best practice) the date would have been off, too. So it's ceteris paribus the same. <time> contains that datetime with timezone.

What's the result of your:
var d = new Date('2006-01-02 15:04:05-0700');
d.toString();

Intl.DateTimeFormat().resolvedOptions();

Hmm, it's definitely MST:
var d = new Date('2006-01-02 15:04:05-0700');
d.toString() // "Mon Jan 02 2006 15:04:05 GMT-0700 (MST)"
Intl.DateTimeFormat().resolvedOptions();
Object
calendar: "gregory"
day: "numeric"
locale: "en-US"
month: "numeric"
numberingSystem: "latn"
timeZone: "America/Denver"
year: "numeric"

I have an idea, moment.

Bingo! That did it. :+1:

Gotta love them all attributes, all of them. And timezones.

Thanks @wmark! This is fantastic.

Pleasure is mine, @mholt. It's always amazing how much time and expertise you spend on this for the benefit of others.


"Azd auth login" failed with cloud shell.

Describe the issue:
Failed to azd auth login with cloud shell in portal because executable file not found in $PATH.
The error message as follows:

Repro steps:

Log in to the portal and open cloud shell.
Clean out auth and other settings using "rm -rf ~/.azd"
Set environment variables: export AZD_IN_CLOUDSHELL=1, export NODE_ENV=dev
Installation: to install run “mkdir -p ~/bin && curl -fsSL https://aka.ms/install-azd.sh | bash -s -- --install-folder ~/bin”
Execute azd auth login and you will see this error.

Environment:

OS: Windows desktop, Linux desktop, macOS
Template: All templates
Azd version: 0.8.0-beta.2 (commit 429b6ccf9a9d1616efa8988f2f8561deeb464c71)

Expected behavior:
Use the command azd auth login to log in normally.
@rajeshkamal5050, @danieljurek for notification.

@zedy-wj, I'm not able to reproduce this result. Does your environment have AZD_IN_CLOUDSHELL=1 set? To find out run echo $AZD_IN_CLOUDSHELL

Environment variables must be set in each terminal session so if you opened a new tab or have closed and re-opened the terminal session that environment variable won't persist.
When we release azd in CloudShell, the CloudShell environment will set this environment variable for the user. Until then we'll need to set it manually.

@vhvb1989 mentioned this during stand-up. @danieljurek is it recommended to be using the managed identity assigned to the cloudshell instance?

Closed as not reproduce, thanks all.

@weikanglim -- Yes, by default we should be using the identity provided. It's possible to override but azd auth login behavior should probably be modified to indicate that the user is already logged in if running in CloudShell.


As a Content Editor, I want a visual indicator when I'm viewing a page that is not yet published so that I can distinguish between published and unpublished content.

this is a stopgap measure until we get wagtail implemented. see asana task:
https://app.asana.com/0/1134940917892680/419540733516951/f
note that this doesn't cover draft/unpublished custom content types (posts, events, etc).
we need to:

[x] check that mezzanine adds some kind of class to unpublished pages
[x] add a css watermark to those pages (see asana task for examples)

got the draft indicator to show up in qa on this page. it looks a little weird overlapping with the test banner, but i think that's probably fine.


Reapply "Provide more powerful isResultValid API"

This reverts commit a3ef0f7909ffd023a390dc1f677cf2cbdffbb166 (https://github.com/swiftlang/swift-llbuild/pull/928) and essentially reapplies 437dac184b64dff1a2ca49ff9c6fd09417473bda (https://github.com/swiftlang/swift-llbuild/pull/926). The downstream failure was not related to this change.
Note that compared to the original commit, this one also initializes the newly introduced function pointer to nil in BuildSystemBindings.swift.

@swift-ci please smoke test


Consider renaming the project to "bashmoji"

There is another more populate software project named "bemoji" , that fills up most of the search results of the first couple pages when searching exactly for the name:
https://www.google.com/search?hl=en&q=bemoji
Also consider adding some Github tags to make it easier to find, as the dmenu-emoji project did.  This project generally works great, but is a little hard to find.

An interesting idea. For now I think I am honestly not too bothered by the discoverability (also shows up 8th spot on the google search for me, just after some android and instagram stuff). Do you think there are large negatives aside from initial discoverability for the little project?
The tags are probably a good idea however, I'll take a minute to fix it.
Also, your google search link showed me that the project is now also packaged as an Arch-AUR package, so thanks for that! :)

Nonetheless thank for the ideas, perhaps in the future as it gains more traction we can reconsider.

I suggest reconsidering the current project name "bemoji" as it may give the impression that it is exclusively for the "bemenu" program launcher, when in fact it is designed to work with multiple program launchers.


Abort existing transactions

Hi.
I have a search bar that everytime the user adds a letter, it triggers a DB query.
I need to abort existing DB transactions, to make sure only one (the more recent one) returns results.
Do you have any recommendation/best practice to do that?

I tried all day to load a bundled DB on assets directory, on www directory, on db directory, with createFromLocation: 1, with createFromLocation: 'string', with different names, to no avail. I just can't find the assets folder in the apk. Is the code still working ?

yes...I suspect that your Android project is not configured properly to include assets directory from the project structure (assuming you followed directions and created one)...Google changes Gradle all the time... cannot keep up with it...

Closing as non-issue and lock of followup.


Riot Android requires having power (level 50?) for adding local aliases

This requirement isn't in Riot Desktop and would be helpful with the issue where rooms show no aliases (I am not sure if there is an issue for it at Synapse at the moment).
I am on Google Play Store version 0.6.8 (8f1140d).

ISTR that Synapse was changed so that any user can add local aliases to a room. The webclient has been updated with this new behaviour, but the Android client so far has not.
Should be an easy fix (remove the permission check).

Is this a P2 or a P3 issue?

Ok, fixed


Preflight 1.8.0 checking disconnected annotations for operators

check workload preflight-green

check workload preflight-green

check workload preflight-green

check workload preflight-green

@ylamgarchal or @thekad could you please approve the PR from the DCI team?

check workload preflight-green

This is triggered automatically when detecting changes in preflight :smile_cat:
https://github.com/dci-labs/dallas-pipelines/blob/7eab7e9646222b06a1e637d85054225038df7439/bin/github-stream#L174-L177

check workload preflight-green

This is triggered automatically when detecting changes in preflight 😸
https://github.com/dci-labs/dallas-pipelines/blob/7eab7e9646222b06a1e637d85054225038df7439/bin/github-stream#L174-L177

I think, "$repo" = openshift-preflight will only work when we have preflight code in the deps (as in the last test here). Just changing the preflight role is currently not enough to trigger the preflight job.

recheck


Building for Node 18 needs libssl-dev and libkrb5-dev to allow building libgit2 from source

System information

node version: v16.18.1
npm or yarn version: npm 8.19.2
OS/version/architecture: Ubuntu: <IP_ADDRESS>-microsoft-standard-WSL2 #1 SMP Fri Jan 27 02:56:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Applicable nodegit version: v0.28.0-alpha.21

I successfully installed v0.28.0-alpha.21 for Node 18.
To the base OS, I had to add:
sudo apt install libssl-dev libkrb5-dev
The install needs to actually build the libgit2 libraries for this work, so it is slower.
Any chance that the 0.28.0 release will be finalized and binary packages created for general use?

Also, install with 0.28.0-alpha.23 does not work with Node v18.19.1.  It does work with Node v18.16.1.
My system is Ubuntu on WSL2 on Win10 x64.
I every install scenario installs or build Win32 nodegit.node libraries.
Trying to debug with --update-binary and --build-from-source does not work either.
I did not try git clone and building from there.
I understand the download binary idea, but with Node shouldn't the v18.16.1 stuff work with v18.19.1 stuff?

FYI: I worked around the npm install problem,  I think there was something that the install was inheriting from my shell or prior install that was triggering the Win32 path.  Somehow I managed to reset it and it builds correctly now.  So, nevermind.


Configure Travis to build treating warnings as errors

This PR addresses #53.
#113 should be merged before this PR. (Edit: merged)

This change is

Coverage decreased (-0.07%) to 86.225% when pulling e07f06ab918ca222714cad41e5286b1f9a83c343 on werror into b658c173eb3470aa67b959b488dd747642742f97 on master.

@mkoval Do we need to add -DTREAT_WARNINGS_AS_ERRORS=ON to here as well?

@mkoval Do we need to add -DTREAT_WARNINGS_AS_ERRORS=ON to here as well?

I don't have a strong opinion either way. If the unit tests currently build without warnings (or it is trivial to make them do so), then I would go ahead and add the flag. Otherwise, it doesn't seem worth the effort.

I'm not familiar with the build process with catkin. My preference is enabling the option for every build for sure hoping that it doesn't require to change the build script a lot. What is the most effective way to do so?

Coverage decreased (-0.07%) to 86.225% when pulling 98e2ad371f6b51fe1379798643efe3ab97c4cd34 on werror into b658c173eb3470aa67b959b488dd747642742f97 on master.

Coverage decreased (-0.07%) to 86.225% when pulling 98e2ad371f6b51fe1379798643efe3ab97c4cd34 on werror into b658c173eb3470aa67b959b488dd747642742f97 on master.

The internal-build.sh script uses the CATKIN_CONFIG_OPTIONS environment variable to populate the default build flags. You could add this to the .travis.yml file:
env:
  global:
  - "CATKIN_CONFIG_OPTIONS=-DCMAKE_BUILD_TYPE=Release -DTREAT_WARNINGS_AS_ERRORS=ON"

I added -DCMAKE_BUILD_TYPE=Release because that is the default if no other flags are specified. This should be overridden (as expected) when we run tests:
./scripts/internal-run.sh catkin build --no-status --no-deps -p 1 -i --cmake-args -DCMAKE_BUILD_TYPE=Debug -DCOVERALLS=ON -- --make-args all tests -- aikido

All the compiler requirements are to ensure that C++ is supported by them. I'll add the comment.

Do you mean C++11? If so, can we put this into a separate that just sets the flags necessary to enable C++11 support?

Hm, this PR has become to have several changes:
(1) Compiler version checking
(2) Adding a compiler flag for enabling C++11
(3) Passing the compiler flag for enabling C++11 to the consumer libraries using target_compiler_options()
(4) Adding a compiler flag for treating warnings as errors

Do you mean C++11? If so, can we put this into a separate that just sets the flags necessary to enable C++11 support?

I think we need both of (1) and (2) because old compilers wouldn't be able to enable C++11 even though we set a flag (e.g., -std=c++11) for it.

You could add this to the .travis.yml file

I'll do this.

This should be overridden (as expected) when we build the tests for Coveralls support:

Are the whole default options are overridden or just options that are specified in both places?

Coverage decreased (-0.07%) to 86.225% when pulling 5823055ba85961c4bb51c9e7949bcf8fbc052a1e on werror into b658c173eb3470aa67b959b488dd747642742f97 on master.

Are the whole default options are overridden or just options that are specified in both places?
View changes

Overriden. The options are merged into one list of command-line arguments that are passed to cmake. If you set -DOPTION=1 using catkin config (i.e. through the CATKIN_CONFIG_OPTIONS environment variable) and pass -DOPTION=2 to catkin build, then cmake is invoked with -DOPTION=1 -DOPTION=2.  CMake uses the last value, so the end result should be equivalent to passing -DOPTION=2.

I think we need both of (1) and (2) because old compilers wouldn't be able to enable C++11 even though we set the flag (e.g., -std=c++11) for it.

I understand that. I am advocating for encapsulating the "check if the compiler supports C++11 and, if so, enable it" logic into a standalone .cmake file that we can easily remove later. Note that CMake 3.1, which we can hopefully switch to soon, adds native support for C++11 by setting:
set(CMAKE_CXX_STANDARD 11)
set(CMAKE_CXX_STANDARD_REQUIRED ON)

Coverage remained the same at 86.225% when pulling 5f2038f6011d34c8181b2d3c8c91c2e0fb4ec7d5 on werror into d5a3730a008ed69897f379b1f64372473d80e445 on master.

Coverage remained the same at 86.225% when pulling 3d91db6c80c10e9989d66a027a4219f93f30fe3a on werror into 941782e68c9c460c50f5a24d0574ae02da84b320 on master.

I'd like to get this merged, but I am concerned that we are adding the flags to each target with PUBLIC visibility.
First, my understanding is that PUBLIC flags will be attached to the EXPORTed targets that are included in the auto-generated aikidoConfig.cmake file. This is troubling because it means that users who link against a version of Aikido that was built with -DTREAT_WARNINGS_AS_ERRORS=ON will inadvertently enable enable -Werror on their own targets.
Second, it adds a lot of boilerplate to Aikido's [already quite verbose] CMakeLists.txt files.
What is the advantage of this over setting CMAKE_CXX_FLAGS inside Aikido's top-level CMakeLists.txt file?

Coverage remained the same at 86.288% when pulling 3acf0c2f403103f766a3abc8f7cdd8678e014eb1 on werror into 67747e1f3cf40791c63ec98a7899160a47ab1608 on master.

The first concern would be fine because this PR doesn't add -DTREAT_WARNINGS_AS_ERRORS=ON but the flag to the Aikido targets that enables building with C++11 (depending on the compilers) so that the consumer project inherently enable C++11.
For the second point, as mentioned above, it passes the compiler options to the consumer projects so that the consumer project doesn't need to figure out what are the required flags such as this.

Coverage remained the same at 86.288% when pulling 3327066ef03cd23c3ecb23eca0e8a35d1ce98841 on werror into 3942ff77f03a48767091fda60afe6386f20b62b2 on master.

Coverage remained the same at 85.391% when pulling e4b49a407b64156909b0bc9d637e1cf9b81fabdd on werror into 963a5d739f9365e107c4ed5fd51b341b66fe4058 on master.

The first concern would be fine because this PR doesn't add -DTREAT_WARNINGS_AS_ERRORS=ON but the flag to the Aikido targets that enables building with C++11 (depending on the compilers) so that the consumer project inherently enable C++11.

It looks like this pull request does add the TREAT_WARNINGS_AS_ERRORS CMake option to Aikido. What am I missing here?
In any case, I am fine with having that option. I am only concerned that the -Werror flag is set as a PUBLIC property on Aikido's targets.

For the second point, as mentioned above, it passes the compiler options to the consumer projects so that the consumer project doesn't need to figure out what are the required flags such as this.

This makes sense for flags that are required for a library to work as expected, e.g. --std=c++11 or -frounding-math. I think it's a bad idea modify compiler warnings and errors for dependent projects, unless doing so is absolutely necessary to #include Aikido's headers. Adding -Werror to a dependency project could break that project's build!

We're adding two flags -Werror and -std=c++11 to Aikido, but only -std=c++11 is added to dependency projects. Please note that -Werror is added using **add**_compile_options() while -std=c++11 is added using **target**_compile_options().

Coverage remained the same at 85.391% when pulling 7b55f33ba744a27785dad49c69e512c45160edf4 on werror into 4cd2795dcf7b90e6b295aaae5e83e244161ab10e on master.

No worries. Thanks!


fix: ensure reserved keywords can never be rendered for TS output

Description
This PR ensures that reserved keywords cannot be rendered for specific parts of class and interface output. It might seem a bit weird, but apparently, not all syntax keywords are reserved. Only parts of it.
Related issue(s)
related to #176

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

11 of 11 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.09%) to 93.68%

Totals

Change from base Build<PHONE_NUMBER>:
0.09%

Covered Lines:
1502

Relevant Lines:
1532

💛  - Coveralls


weechat: 4.3.6 -> 4.4.0

Description of changes
https://github.com/weechat/weechat/releases/tag/v4.4.0
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg eval

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

10 packages built:

weechat
weechat-unwrapped
weechat-unwrapped.guile
weechat-unwrapped.lua
weechat-unwrapped.man
weechat-unwrapped.perl
weechat-unwrapped.php
weechat-unwrapped.python
weechat-unwrapped.ruby
weechat-unwrapped.tcl


Document the memray tests and add a script for automation

Fixes #112

Codecov Report

Merging #113 (dbf596d) into main (3c14500) will increase coverage by 3.44%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #113      +/-   ##
==========================================
+ Coverage   85.38%   88.83%   +3.44%
==========================================
  Files          11       11
  Lines        2156     2069      -87
==========================================
- Hits         1841     1838       -3
+ Misses        315      231      -84

Impacted Files
Coverage Δ

src/picologging/handler.cxx
92.55% <0.00%> (+0.33%)
:arrow_up:

src/picologging/streamhandler.cxx
94.80% <0.00%> (+0.60%)
:arrow_up:

src/picologging/handlers.py
94.02% <0.00%> (+1.83%)
:arrow_up:

src/picologging/config.py
84.83% <0.00%> (+2.45%)
:arrow_up:

src/picologging/logger.cxx
85.67% <0.00%> (+3.33%)
:arrow_up:

src/picologging/filterer.cxx
95.23% <0.00%> (+16.66%)
:arrow_up:

src/picologging/_picologging.cxx
100.00% <0.00%> (+41.46%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Fast muter not working with Lora Stack

In example above it works only if the first lora stacker is enabled. Enabling any other or any combination of multiple stackers are not working (or only applying first one if enabled).
In fact when any stacker other than first is enabled the output is no longer lora_stack as shown by apply lora stack node throwing a warning

Ah, the Fast Muter node only mutes / bypasses the connected nodes; it is not a switch itself. The OPT_CONNECTION output is for connecting to other nodes, like the Fast Action Button, etc.
However, you can still use Fast Muter with the Any Switch to correctly mute nodes (so they don't do work) and choose then first non-muted value.
Would be something like this:


Addition of Resnet18 Model in Application

If you open a GitHub issue, here is our policy:
It must be a bug, a feature request, or a significant problem with the documentation (for small docs fixes please send a PR instead).
The form below must be filled out.
Here's why we have that policy:.
Keras developers respond to issues. We want to focus on work that benefits the whole community, e.g., fixing bugs and adding features. Support only helps individuals. GitHub also notifies thousands of people when issues are filed. We want them to see you communicating an interesting problem, rather than being redirected to Stack Overflow.
System information.
TensorFlow version (you are using): 2.6.0
Are you willing to contribute it (Yes/No): Yes
Describe the feature and the current behavior/state. Addition of a new pre-trained model: Resnet18 in the application section.
Describe the feature clearly here. Be sure to convey here why the requested feature is needed. Any brief description of the use-case would help.
Will this change the current API? How? Yes. Addition of a new Resnet18 pre-trained model in the application section.
Who will benefit from this feature? Researchers as well as individuals who want to fine-tune or train Resnet18 in Tensorflow without switching to PyTorch
Contributing

Do you want to contribute a PR? (yes/no): Yes
If yes, please read this page for instructions
Briefly describe your candidate solution(if contributing):
Addition of following code to the api:

tf.keras.applications.ResNet18( include_top=True, weights='imagenet', input_tensor=None, input_shape=None, pooling=None, classes=1000, classifier_activation='softmax', **kwargs )
Use Case: This would allow individuals to fine-tune the ResNet18 model pre-trained on the imagenet dataset to be fine-tuned on their custom dataset. As the implementation of ResNet18 is already available in PyTorch and not in Tensorflow, sometimes it becomes difficult for developers with knowledge of Tensorflow and no prior knowledge of Pytorch to implement the following. Hopefully, this will allow better transfer learning for developers and reduce time in writing the ResNet18 model from scratch, then training it on the imagenet dataset and then fine-tuning it on their custom dataset. Let me know if this resolves the doubt or I need to provide more explanation.
Paper for ResNet18 introduction and architecture

@MrinalTyagi
It's already been asked, here

@jvishnuvardhan
Sorry, it's not clear to me the above comment. Is there any model application in tf-addons? I think it's well used and worthy to add under tf.keras.applicaitons.

Duplicate of ##15269
Is it possible for you and @innat to add this to tf-addons. Based on usage, this may be moved under tf.keras.applications. Thanks!

yes I can surely try that but would require some more information on how to submit the required pr for that.

Duplicate of #https://github.com/keras-team/keras/issues/15269
Is it possible for you and @innat to add this to tf-addons. Based on usage, this may be moved under tf.keras.applications. Thanks!

any update on this?

any update guys?

i can implement breadbreads implementation into the codebase, within a week or so

+1

@MrinalTyagi This issue is a duplicate of the issue #15269 and there is an active PR for this issue here. Please close the issue as it has already been tracked using #15269. Thanks!


[file-extension-in-import] Does not work with node version 16.0.0 - 16.16.0

Environment
Node version: 16.16.0
eslint-plugin-n version: 16.3.0
With the following config:
"n/file-extension-in-import": ["error", "always"]

I see the error,
isBuiltin is not a function

isBuiltin was added to node in version v16.17.0
What rule do you want to report?
n/file-extension-in-import
Proposal:
Docs can be updated to reflect the requirement for node version
Participation

[ ] I am willing to submit a pull request for this issue.

Additional comments
No response

Sorry about this, I will get on it this afternoon!

yes, it should be fixed - node.js v16 is still supported.

@scagood  This problem has appeared again. Does this library not support node 16.0.*?

As of version 17, we have dropped support for node 16, yes.
The current minimum version is 18.18.0
https://github.com/eslint-community/eslint-plugin-n/commit/41ceed7ad17e42f3074e664081f69639d0fb4322


Feature/fixed navbar jumps

Reference to the following issue: 4635
Now it's possible to prevent this issue with the option hideScrollBar. The default value of this option is true. To prevent these jumps you have to set the value to false.
Default behaviour: https://codepen.io/anon/pen/GmEmgQ
Behaviour without jumps: https://codepen.io/anon/pen/XRYZMp

Are you running on windows?

On work. Why do you ask?

Cuz I wasn't able to reproduce it on a mac in chrome,safari or firefox. Was just confused

Yes, that's a windows exclusive bug :)

Added an option in sidenav and modal in a9a87f4f9cec5e7412a097a132c64cb8ff671663


Generate documentation for blueprint archetypes & components

Blueprint uses a scope that's currently filtered.
Need to decide how this works, where it goes, etc.

@jleibs are we done here?

Though maybe we could use a comment somewhere that the blueprint-scoped components and data types don't get explicit documentation. Only views.


⚠ ClamAV has degraded performance

In 294dadc, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 192 ms

Resolved: ClamAV performance has improved in e617361.


Support for array, table types

With other implementations of EmmyLua i've seen, it is possible to use types such as "string[]" or "table<string, string>". As of right now, it seems that arrays/tables aren't supported.

^ Without using the for loop, the language server assumes the type of "names" to be any. Ideally, I would like it to recognize that each (key, value) ipair/pair of names is (number, string).

It should be fixed.

https://gfycat.com/goodnaturedrashbluefish
It seems to almost work fully


Relationship query filter to get specific data

Version information

Laravel: v6.10.0
Voyager: v1.3.1
PHP: 7.3
Database: [MariaDB] [10.4]

Description

I got an option get specific type users through relationship. For example create a relationship products bread with users table. When I try to create a product the relationship get all users. But I want to get only users that has specific role.
Additional context
Add any other context about the problem here.

Questions about how to implement something should be asked in slack, not here.  This is mentioned in the issue template.
Please check the docs (both Laravel and Voyager) for query scopes


Refactor/validation text component

still not sure about the memoization and if it is needed in this
case
https://github.com/see: https://dmitripavlutin.com/use-react-memo-wisely/
https://github.com/see: https://react.dev/reference/react/useMemo
Lael directory based on components which are labeling input (helper
text, validation text, label itself)
https://github.com/see: https://github.com/adobe/react-spectrum/tree/main/packages/%40react-spectrum/label
also https://blog.bitsrc.io/new-react-design-pattern-return-component-from-hooks-79215c3eac00

[ ] Add tests
[ ] Rename directory to Field
[ ] export in anyway
[ ] add README


TypeError: init() got an unexpected keyword argument 'max_iters' in PoisoningAttackSVM.ipynb

Describe the bug
TypeError: init() got an unexpected keyword argument 'max_iters' in PoisoningAttackSVM
To Reproduce
Steps to reproduce the behavior:

Go to Notebooks '
Run provenance_defence Notebook .
While executing below line of code
svm_attack = PoisoningAttackSVM(classifier=no_defense, x_train=x_train, y_train=y_train,
step=0.1, eps=1.0, x_val=valid_data, y_val=valid_labels, max_iters=200)
See error

System information (please complete the following information):

OS : Windows 10
Python version : 3.7
ART version or commit number : 1.5.0

@sohanlal1234 thanks for catching this! This is a issue with the notebook. I will change the notebook to use the correct argument max_iter.
Thanks for using ART!


cbr is a hash, so we need the merge

Yeah, okay, I broke it yesterday.
Thanks @lpichler.
@miq-bot add_label bug, ivanchuck/yes

@miq-bot assign @bdunne
break all the things?

@miq-bot add_label ivanchuk/yes

Ivanchuk backport details:
$ git log -1
commit 2fda0fd166d4e4c04470884e0a5a5c5162c2c2a2
Author: Nick Carboni<EMAIL_ADDRESS>Date:   Wed Jul 24 09:09:22 2019 -0400

    Merge pull request #19047 from d-m-u/fixing_chargeback_rate_detail_seed

    cbr is a hash, so we need the merge

    (cherry picked from commit a37cc5d89b42f5b53133f32f9caa402a2764313d)


Remote Submissions now hanging clients after RuneLite release

Hi - I've been running this for a clan to track achievements - since this morning, my code has been hanging users posting in clan chats. I've looked at my own code and it's in line with typical network posts - I had been responding 200/201 and writing back carriage return/newlines until now. Just hangs the user now.
Is there an updated response format expected since yesterday with underlying remote requests for runelite? Thanks!
runelite build: RuneLite/1.10.36-a2b6305

Thanks for reporting this, I'll look into it today


6 GB VRAM?

Hello,
is it possible to run the 117M GPT-2 model with 6 GB VRAM using FP16?

If you mean "train it" then nope.


Can't find c compiler on windows even when present

A few times recently where people complain they have gcc installed and can find it in their path but the setup app doesn't find it.
Skimming through the code, it has to do with using which to find the compiler, which doesn't exist on windows that uses where instead.

This is now fixed, thanks so much - a new build is up at https://geoffrey-artefacts.fynelabs.com/github/andydotxyz/fyne-io/setup/419/index.html


matching updater's version checking

Fixes "not installing the latest version" issue.
Also added missing scriptlogs.
Tested working ;)
Need to pull on development branche once this is merged.

Last commit fixes also https://github.com/dgibbs64/linuxgsm/issues/744


Allow hyphens to be used in property names in theme

Allow hyphens to be used instead of underscores in property names in the theme file.
Example:
base:
  font-family: NotoSerif

This makes the theme more comfortable for CSS designers. Internally, all hyphens will be mapped to underscores to make it convenient to reference the keys as properties in Ruby (e.g., @theme.base_font_family).

I think we'll still require underscores for the categories (e.g., definition_list).


Updating version of NVM v0.34.0 -> v0.35.2

v0.35.2 available, see https://github.com/nvm-sh/nvm#install--update-script

@rsmb : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thanks @rsmb!  Merging your update. : )


audit and serialization updates

Sample viewer logic audit and update to metadata serialization

Ok all those comments either changed in code or addressed in the comment! Ready for re-review. Thanks @shubham7109!


Group layer elements

Closes #42

Elements from a single layer are grouped in <g>
Change layer-to-xml functions to return elements rather than lists

Note: tests are expected to fail until #44 is fixed. Will check that out next.

If someone merges #46, please merge main into this one also. 😊


Update dependencies to latest versions

Updated with npx npm-check-updates.
 @crowdstrike/foundry-js                    0.9.0  →    0.15.0
 @shoelace-style/shoelace                   2.5.2  →    2.16.0
 @testing-library/jest-dom                 ^6.1.3  →    ^6.5.0
 @testing-library/react                   ^14.0.0  →   ^16.0.1
 @types/react                            ^18.2.14  →   ^18.3.5
 @types/react-dom                         ^18.2.6  →   ^18.3.0
 @typescript-eslint/eslint-plugin         ^5.61.0  →    ^8.5.0
 @typescript-eslint/parser                ^5.61.0  →    ^8.5.0
 @vitejs/plugin-react                      ^4.0.1  →    ^4.3.1
 autoprefixer                            ^10.4.14  →  ^10.4.20
 eslint                                   ^8.44.0  →   ^9.10.0
 eslint-plugin-no-relative-import-paths    ^1.5.2  →    ^1.5.5
 eslint-plugin-prettier                    ^5.0.0  →    ^5.2.1
 eslint-plugin-react                      ^7.33.1  →   ^7.36.1
 eslint-plugin-react-hooks                 ^4.6.0  →    ^4.6.2
 eslint-plugin-react-refresh               ^0.4.1  →   ^0.4.11
 framer-motion                           ^10.13.1  →   ^11.5.4
 jsdom                                    ^22.1.0  →   ^25.0.0
 postcss                                  ^8.4.26  →   ^8.4.45
 prettier                                   3.0.0  →     3.3.3
 react                                    ^18.2.0  →   ^18.3.1
 react-dom                                ^18.2.0  →   ^18.3.1
 react-hook-form                          ^7.45.2  →   ^7.53.0
 react-router-dom                          6.14.1  →    6.26.2
 react-select                              ^5.7.4  →    ^5.8.0
 rollup-plugin-visualizer                  ^5.9.2  →   ^5.12.0
 tailwindcss                               ^3.3.3  →   ^3.4.11
 temporal-polyfill                         ^0.1.1  →    ^0.2.5
 typescript                                ^5.0.2  →    ^5.6.2
 vite                                      ^4.4.0  →    ^5.4.4
 vitest                                   ^0.34.5  →    ^2.1.0
 zod                                      ^3.21.4  →   ^3.23.8

yarn install seems to work after upgrading these libraries, but there are warnings:
➤ YN0000: · Yarn 4.3.1
➤ YN0000: ┌ Resolution step
➤ YN0085: │ + @crowdstrike/foundry-js@npm:0.15.0, @shoelace-style/shoelace@npm:2.16.0, and 242 more.
➤ YN0085: │ - @adobe/css-tools@npm:4.3.1, @babel/compat-data@npm:7.23.2, @babel/core@npm:7.23.2, and 236 more.
➤ YN0000: └ Completed in 4s 999ms
➤ YN0000: ┌ Post-resolution validation
➤ YN0060: │ eslint is listed by your project with version 9.10.0 (pbabda), which doesn't satisfy what @typescript-eslint/eslint-plugin and other dependencies request (^8.57.0).
➤ YN0002: │ scalable-rtr-react@workspace:. doesn't provide @testing-library/dom (p02ebd), requested by @testing-library/react.
➤ YN0086: │ Some peer dependencies are incorrectly met by your project; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code.
➤ YN0086: │ Some peer dependencies are incorrectly met by dependencies; run yarn explain peer-requirements for details.
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0066: │ typescript@patch:typescript@npm%3A5.6.2#optional!builtin<compat/typescript>::version=5.6.2&hash=379a07: Cannot apply hunk #11
➤ YN0013: │ 113 packages were added to the project (+ 113.45 MiB).
➤ YN0000: └ Completed in 3s 257ms
➤ YN0000: ┌ Link step
➤ YN0007: │ esbuild@npm:0.21.5 must be built because it never has been before or the last one failed
➤ YN0000: └ Completed in 5s 181ms
➤ YN0000: · Done with warnings in 13s 482ms

If I try to run yarn test, it fails:
 DEV  v2.1.0 /Users/mraible/dev/foundry-sample-scalable-rtr/ui/pages/scalable-rtr-react

 ❯ src/components/ZonedDateTime.test.tsx (0)
 ❯ src/lib/utils/cron-parser.test.ts (0)
 ❯ src/lib/utils/datetime.test.ts (0)
 ❯ src/lib/utils/truncate-text.test.ts (0)

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Suites 4 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

 FAIL  src/components/ZonedDateTime.test.tsx [ src/components/ZonedDateTime.test.tsx ]
 FAIL  src/lib/utils/cron-parser.test.ts [ src/lib/utils/cron-parser.test.ts ]
 FAIL  src/lib/utils/datetime.test.ts [ src/lib/utils/datetime.test.ts ]
 FAIL  src/lib/utils/truncate-text.test.ts [ src/lib/utils/truncate-text.test.ts ]
Error: Cannot find module '@testing-library/dom'
Require stack:
-<EMAIL_ADDRESS> ❯ Object.<anonymous> node_modules/@testing-library/react/dist/pure.js:46:12

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/4]⎯

 Test Files  4 failed (4)
      Tests  no tests
   Start at  11:51:10
   Duration  595ms (transform 17ms, setup 0ms, collect 0ms, tests 0ms, environment 1.22s, prepare 474ms)

To fix this, I ran yarn add -D @testing-library/dom. Now some three tests fail:
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Tests 3 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

 FAIL  src/lib/utils/datetime.test.ts > toZoned method > Bad inputs > Malformed timestamp
AssertionError: expected error to have message: Cannot parse dateTime 'asdf[UTC]'

Expected: "Cannot parse dateTime 'asdf[UTC]'"
Received: "Cannot parse: asdf[UTC]"

 ❯ src/lib/utils/datetime.test.ts:61:10
     59|       expect(() => {
     60|         toZoned({ timestamp: "asdf" });
     61|       }).toThrow(new RangeError("Cannot parse dateTime 'asdf[UTC]'"));
       |          ^
     62|     });
     63|

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/3]⎯

 FAIL  src/lib/utils/datetime.test.ts > toZoned method > Bad inputs > Invalid date
AssertionError: expected error to have message: Invalid overflowed value 13

Expected: "Invalid overflowed value 13"
Received: "Invalid isoMonth: 13; must be between 1-12"

 ❯ src/lib/utils/datetime.test.ts:67:10
     65|       expect(() => {
     66|         toZoned({ timestamp: "2023-13-32T25:61" });
     67|       }).toThrow(new RangeError("Invalid overflowed value 13"));
       |          ^
     68|     });
     69|

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[2/3]⎯

 FAIL  src/lib/utils/datetime.test.ts > toZoned method > Bad inputs > Invalid timezone
AssertionError: expected error to have message: Invalid time zone specified: Moon/Sea_Of_Tranquility

Expected: "Invalid time zone specified: Moon/Sea_Of_Tranquility"
Received: "Invalid time zone specified: MOON/SEA_OF_TRANQUILITY"

 ❯ src/lib/utils/datetime.test.ts:73:10
     71|       expect(() => {
     72|         toZoned({ timestamp: summerDate, timezone: "Moon/Sea_Of_Tranquility" });
     73|       }).toThrow(
       |          ^
     74|         new RangeError("Invalid time zone specified: Moon/Sea_Of_Tranquility"),
     75|       );

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[3/3]⎯

 Test Files  1 failed | 3 passed (4)
      Tests  3 failed | 37 passed (40)


Mr cragy

Problems with functionality and acessing wallet registration, a long way off to be a functional product

Please explain the issue,


Create CallingCard.lua

Contains the code for the Calling Card joker

The addition to the config in the main paperback.lua file is missing (it won't be initialized otherwise)

I was having issues getting this joker to load in its current state. I enabled it in the config but it kept giving me an error saying that the end_calculate_context field was null. I did some research and asked on the Discord and they said to change it to if context.joker_main and add card in as a function parameter to calculate. Here is the working code if you want to take a look:
SMODS.Atlas {
    key = 'callingcardimg',
    px = 71,
    py = 95,
    path = 'CallingCard.png'
}

SMODS.Joker {
    key = 'callingcard',
    loc_txt = {
        name = "Calling Card",                                --name used by the joker
        text = {
            "Whenever you defeat a {C:attention}Boss Blind{} or activate its {C:attention}effect{}, this Joker gains {X:red,C:white}0.25X{}",             --description text.
            "{C:inactive}(currently gives {}{X:red,C:white}#2#X{}{C:inactive} Mult){}"                       --more than 5 lines look odd
        }
    },
    config = { extra = { mult = 0, x_mult = 1 } }, --variables used for abilities and effects.
    rarity = 2,                                         --rarity 1=common, 2=uncommen, 3=rare, 4=legendary
    pos = { x = 0, y = 0 },                             --pos in spirtesheet 0,0 for single sprites or the first sprite in the spritesheet
    atlas = 'callingcardimg',                                        --defines the atlas that you want to use for the sprite sheet. atlas=nil if you want to use single sprites
    cost = 6,                                           --cost to buy the joker in shops
    unlocked = true,                                    --joker is unlocked by default
    discovered = true,                                  --joker is discovered by default
    blueprint_compat = true,                            --does joker work with blueprint
    eternal_compat = true,                              --can joker be eternal
    soul_pos = nil,                            --pos of a soul sprite.

    calculate = function(self, card, context)                 --define calculate functions here
        if G.GAME.blind.triggered and not context.blueprint then
            card.ability.extra.x_mult = card.ability.extra.x_mult + 0.25
        end
        if context.end_of_round and not context.individual and not context.repetition and not context.blueprint and G.GAME.blind.boss and not self.gone then
            card.ability.extra.x_mult = card.ability.extra.x_mult + 0.25
        end
        if context.joker_main then
            return {
                Xmult_mod = card.ability.extra.x_mult,
                card = card,
                message = localize { type = 'variable', key = 'a_xmult', vars = { card.ability.extra.x_mult } }
            }
        end
    end,

    loc_vars = function(self, info_queue, center) --defines variables to use in the UI. you can use #1# for example to show the mult variable, and #2# for x_mult
        return { vars = {center.ability.extra.mult, center.ability.extra.x_mult} }
    end,
}

Also, pull main and merge, since we removed the individual sprites and replaced it with one sprite sheet

Also consider changing the filename to calling_card.lua, since basically everything else is snake_case.

Moving to branch add-calling-card to merge with refactoring


chore(blockifier_reexecution): refactor cli to reduce code duplication

This change is

crates/blockifier_reexecution/src/main.rs line 51 at r2 (raw file):
Previously, dorimedini-starkware wrote…
why do you need an output dir in the rpc test (without dump)?

I don't - there are 3 args and 3 commands: the 1st requires the first two args, the second all three, and the last the second two. How do you want me to organize the args?

crates/blockifier_reexecution/src/main.rs line 62 at r2 (raw file):
Previously, dorimedini-starkware wrote…
you don't need the node url here, right?

Right

crates/blockifier_reexecution/src/main.rs line 51 at r2 (raw file):
Previously, dorimedini-starkware wrote…
if there is no subset of args that is common to all - just be explicit in each command... unless you have some idea to share code.
but don't require unecessary args for commands that don't need them

There's a natural default, so they don't strictly require them. Being explicit here is simply much more code - what's the disadvantage to using this struct?

crates/blockifier_reexecution/src/main.rs line 62 at r2 (raw file):
Previously, dorimedini-starkware wrote…
then please don't require it

Done. Is it better this way?

crates/blockifier_reexecution/src/state_reader/utils.rs line 193 at r6 (raw file):
Previously, dorimedini-starkware wrote…
where is pre_process_block?
please ask for review from @AvivYossef-starkware

That change is already in this PR: https://reviewable.io/reviews/starkware-libs/sequencer/1764

crates/blockifier_reexecution/src/state_reader/test_state_reader.rs line 79 at r12 (raw file):
Previously, AvivYossef-starkware wrote…
Please add documentation or change the location of old_block_hash, as it is confusing since the old block hash does not correspond to the hash of the previous block.

I don't see it, I guess it's already done.


Broken with Compiled Exe (Node Single Executable Application SEA)

Hi,
I was recently trying out UWS and loved the performance gains, but wanted to make sure it worked with .exe.
(https://nodejs.org/api/single-executable-applications.html#single-executable-applications)
First, I tried using it with npx webpack. Works great!
Then, I tried using it by injecting the blob into my executable. This works for other .node files perfectly, but with
the same uws_win32_x64_120.node we used for our bundle.js that worked- we see it crash our exe with no error.
I've managed to strip away everything and get it down to the one function causing the error, so other than require()
or createRequire(), the real problem is dlopen(). For whatever reason, even with the same system, seconds after running
the working dlopen on a bundled JS file, the same method fails when run inside an executable. I've debugged to making
sure the node file exists and is found properly, but can't go much further without C code, as NodeJS exe refuses to catch
the error, crashing instead, making me think some kind of segfault or otherwise is happening on UWS's side.
I've created a working minimal example below.
To run it, just do:
node server.js
which should work and show:
node server.js

Starting server... before UWS
__dirname: C:\Users\slee\Downloads\minimal
UWS path: C:\Users\slee\Downloads\minimal\uws_win32_x64_120.node
Attempting to load UWS native addon...
UWS loaded successfully
module.exports keys: [
'App',
'SSLApp',
'H3App',
...
'DEDICATED_DECOMPRESSOR_1KB',
'DEDICATED_DECOMPRESSOR_512B',
'LIBUS_LISTEN_EXCLUSIVE_PORT'
]
Starting server... after UWS
App instance created successfully
Server started on port 3000

Then you can do npx webpack and node bundle.js and see the same output, indicating packing works fine.
However, if we compiled the executable by doing:
node -e "require('fs').copyFileSync(process.execPath, 'test.exe')"
npm run sea
npm run postject
then running test.exe shows:

C:\Users\slee\Downloads\minimal>test.exe
Starting server... before UWS
__dirname: C:\Users\slee\Downloads\minimal
UWS path: C:\Users\slee\Downloads\minimal\uws_win32_x64_120.node
Attempting to load UWS native addon...
C:\Users\slee\Downloads\minimal>

Just crashing, despite our try/catch, indicating the dlopen or C code is faulting.
Attached are the files you need to reproduce this.
minimalbrokenexe.zip

You don't want to be on Windows when debugging things like these. If you swap to Linux (or even just WSL2) you have tons more and better tools to see what is wrong.
But at the same time - never heard of SEA and I know there are many bundlers that don't work with uWS. They often neglect native addons.

Btw, nobody is going to run an .exe attached to your post. I removed it. Please do not attach .exe files here.

Sorry!! Updated for just code, along with Windows and Linux commands. I went ahead and did WSL2 with Linux binary via SEA, and surprisingly- it worked.
./test
Starting server... before UWS
__dirname: /mnt/c/users/slee/downloads/minimal/linux
UWS path: /mnt/c/users/slee/downloads/minimal/linux/uws_linux_x64_120.node
Attempting to load UWS native addon...
UWS loaded successfully
module.exports keys: [
  'App',
  ...
  'DEDICATED_DECOMPRESSOR_512B',
  'LIBUS_LISTEN_EXCLUSIVE_PORT'
]
Starting server... after UWS
App instance created successfully
Server started on port 3000

So that narrows down the issue to just Windows, but it doesn't make debugging any easier- because now I really have to figure out how to debug on Windows instead (since exe is my target platform) and running the compiled exe doesn't show any logs despite all our attempts to catch the segfault. I also checked w/ Dependency Walker (Some other issue raised mentioned needing MSVC140), but the Walker and MSVC installers claimed I had everything installed.
Since it works on Linux, I imagine it's some kind of dependency issue on Windows. I've used other native addons that work just fine with SEA, so just need to debug UWS.node loading on Windows exe to see what crashes it- any ideas? Any custom development .node that just spits out info before it crashes, maybe?
Ty for the quick reply!


Fork getting ready development environment

Hello,
We have made a fork from your branch, we want to introduce a vertical slide to the library but we are unable to start the development environment.
After the clone we do "npm i" and we try the next build, but it gives an error:
npm run build.log
Also we tried the npm run dev but in the screen we only see "internal server error".
Finally in the npm run start it also gives and error but i think is because the build failed:
npm run start.log
If you could help us understand what we are missing we will would be grateful.
Attentively
Angelbe

Could you realise vertical slide?


It looks like factories.py is not used, am i right?

Is use_factory function deprecated by UserFactory class? I want to confirm this. Tests are passed if I delete this file.

You're right, I forgot to delete the file. Thanks for reporting I'll delete it from repository

closing


Add jdbc connector e2e test

Purpose of this pull request

Check list

[ ] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/incubator-seatunnel/tree/dev/docs

#2255 . License it's ok.  I will take a look when my free.

At present, only batch tests are covered, Streaming Mode and Exactly-Once Streaming Mode are not covered。Can you add these two test scenarios? And abstract public methods for use by mysql, pgsql, and dmsql . . .


IGNITE-14070 Protecting a snapshot from unauthorized changes.

Thank you for submitting the pull request to the Apache Ignite.
In order to streamline the review of the contribution
we ask you to ensure the following steps have been taken:
The Contribution Checklist

[ ] There is a single JIRA ticket related to the pull request.
[ ] The web-link to the pull request is attached to the JIRA ticket.
[ ] The JIRA ticket has the Patch Available state.
[ ] The pull request body describes changes that have been made.
The description explains WHAT and WHY was made instead of HOW.
[ ] The pull request title is treated as the final commit message.
The following pattern must be used: IGNITE-XXXX Change summary where XXXX - number of JIRA issue.
[ ] A reviewer has been mentioned through the JIRA comments
(see the Maintainers list)
[ ] The pull request has been checked by the Teamcity Bot and
the green visa attached to the JIRA ticket (see TC.Bot: Check PR)

Notes

How to Contribute
Coding abbreviation rules
Coding Guidelines
Apache Ignite Teamcity Bot

If you need any help, please email<EMAIL_ADDRESS>or ask anу advice on http://asf.slack.com #ignite channel.

PR is related to resolved ticket https://issues.apache.org/jira/browse/IGNITE-14070, closing it.
Feel free to reopen if it is needed


Revisit data access exceptions in RandomAccessData, Bytes, BufferedData, and other classes

Here is one of the methods in RandomAccessData interface:
    /**
     * Gets the signed byte at the given {@code offset}.
     *
     * @param offset The offset into data to get a byte from.
     * @return The signed byte at given {@code offset}
     * @throws BufferUnderflowException if the buffer is empty
     * @throws IndexOutOfBoundsException If the given {@code offset} is negative or not less than {@link #length()}
     */
    byte getByte(final long offset);

Method semantics is "get a byte at the given offset", which is identical to byte arrays. IOOBE is consistent with what exceptions are used by arrays, but BufferUnderflowException looks alien here. These BufferXYZExceptions are used by buffers on sequential access, when there is no more data to read / write. On random access, java.nio buffer classes throw IOOBE, too.
This ticket is to iterate over PBJ classes and interfaces and make sure exceptions used to indicate illegal access are consistent across code.

Please speak with @rbair23 before changing the strategy for exceptions.


💡[Feature]: Smiling Detection

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
This feature enables the detection of smiles in facial images using a neural network. It processes the dataset by resizing and normalizing images, then trains the model on labeled data to distinguish between smiling and non-smiling faces. The system includes model evaluation, saving, and loading capabilities for accurate and efficient smile detection
Use Case
Add this feature to apps like photo albums, social media sites, and marketing tools to automatically find and tag pictures of people smiling. This makes the user experience better and helps deliver more personalized content.
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@TAHIR0110 sir can you please assign this issue to me.

@UppuluriKalyani assigned!


Performance variables must be numbers

I tried putting the output of "git commit" into a perf_var so that I could link changes in performance history to changes in the system configuration, but I get this error:
FAILURE INFO for ...
<snip>
  * Failing phase: performance
<snip>
Reason: sanity error: the value extracted for performance variable 'alaska:roce-openmpi4-ucx:git_ref' is not a number: a2cccdd-dirty

There's nothing in the docs I can see that state performance variables need to be numbers.
Is there a way around this, or a better way of achieving the same thing?

Hi @sjpb, this behaviour is expected and it has been reported in #1146 (where ReFrame was just crashing instead of giving a message). The comment here describes what happens and why we expect a number: https://github.com/eth-cscs/reframe/issues/1146#issuecomment-580682324
What do you want to achieve exactly? How your references look like for this "performance variable?"

Ok - so then this is really just a documentation issue. I'd assumed that with a reference which looked like this 'git_ref': (None, None, None, 'n/a'),, i.e. no reference, a non-numeric perf var would be ok.
What I was trying to achieve (and this obviously isn't the right way) was to get a git commit into the performance log, linked to a test run, so I can link changes in performance to changes in configuration. Still interested in a way of doing that!

I'd assumed that with a reference which looked like this 'git_ref': (None, None, None, 'n/a'),, i.e. no reference, a non-numeric perf var would be ok.

This is something we could implement easily, since it seems that people want to use the performance variables to log non-performance information. I will open a feature request for that.

What I was trying to achieve (and this obviously isn't the right way) was to get a git commit into the performance log, linked to a test run, so I can link changes in performance to changes in configuration. Still interested in a way of doing that!

Makes sense. One way you could possibly do that currently, is to try to pass the git hash as a "unit", the last element of the tuple, and make sure that what you extract as a value for this variable from the output is a number (anything). Then the git hash will be logged as the unit of that variable. I know it's hacky, but it should work.

FYI my eventual solution for this was to push the info into the tag instead. It isn't really a performance variable, and actually logically it makes more sense to have this available on each line of the performance log (like the reframe version) rather than generating a new line (="observation") for it. So maybe the current perf var functionality shouldn't be changed, although using tags is a bit hacky too. I considered using the info field but that seemed less appropriate.

I agree. This one needs more thinking. How did you make it log the tags? Did you add another log format specifier for tags?

I just added %(check_tags)s to the log format - then (outside of reframe) I have code which parses the perflogs.

I see. There is also #1068 that requests other check fields to be logged as well and I'm thinking to make this more generic, so that you could easily select any test field to log, even custom ones. How that sounds?

Yes that would work. Tags actually work fine to be honest though - as reframe nicely formats them as a comma-separated string in the log they're pretty easy to handle. I guess conceptually "tags" and "things I want to log" are different though.

I'm closing this, too. It'll be addressed by #1068.


iron-ajax doesn't work when it is used in a custom element

Hi, I tried to use iron-ajax inside a custom element using the polymer-starter-kit. The ajax request cannot be made with "auto" or the generateRequest() method. However, it works when I import the iron-ajax.html AGAIN in the main index.html.
Here is my code if it helps

UPDATE:
It works by changing the import code to  <link rel="import" href="...."  rather than <link import="..."

Great, you've got the correct syntax now.  Closing.


could you please build images regularly?

Description of the feature

I see you have a github action to trigger a build and publish to docker hub. I would like to see this action triggered by a cron ( maybe once a week or so ) - the last publish seems to have been ~ 3 months ago. this would make it easier for the end user to use images and dont have to patch them on their own.
Benftits of feature

overall reduce attack surface for users by regularly patching issues.
Additional context

https://gist.github.com/loeken/5a6568b7507818629700273377eab9ed <- current trivy report for your image

repo seems dead will close my request


update client-c to disable grpc client keepalive (#4655)

cherry-pick https://github.com/pingcap/tiflash/pull/4655 to release-5.4 branch
close https://github.com/pingcap/tiflash/issues/4192, close https://github.com/pingcap/tiflash/issues/4662
What problem does this PR solve?
Issue Number: close #xxx
Problem Summary:
What is changed and how it works?
Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

Fix bug that TiFlash query will meet keepalive timeout error randomly.

/merge

/run-integration-test


[release-2.11] Update to Go v1.22

ref: https://issues.redhat.com/browse/ACM-14251

/override "security/snyk (Red Hat Advanced Cluster Management for Kubernetes)"

/override "security/snyk (Red Hat Advanced Cluster Management for Kubernetes)"


It appears that users1_address_line_two is not being recognized as a built-in field but it should be

Fixed in #520


Canceled Hosting Adoption, but server was provisioned and dashboard doesn't allow edit DNS record automagically

After PR registration was merged, I've double checked manage.is-a.dev. It allows domain changes (probably will do an PR automagically again), but also offered to create hosting... after click on create host, a confirmation about DNS changes  was made, but 've decided to not use hosting wright now, so canceled confirmation. An error was thrown about no DNS changes made, but dashboard now only offers options to manage files (net2ftp browsing - which is working after setting password on hosting settings) and hosting settings.
I've believe that code is not prepared for a not so decided user like I was...

To avoid hosting registrations that will not be used, this confirmation
https://github.com/is-a-dev/register.is-a.dev/blob/f5fd2d80e510161fc62bf060181d0a5465104209/src/routes/domains/[domain]/%2Bpage.svelte#L107
Should be done before domain registration on host.is-a.dev

is-a.dev Hosting was shut down.


fix: project detail logo deleted actually removes it

What does this PR do and why?
Provide a description of what this PR does. Link to any relevant GitHub issues, Notion tasks or Discord discussions.
Screenshots or screen recordings
If applicable, provide screenshots or screen recordings to demonstrate the changes.
Acceptance checklist

[ ] I have evaluated the Approval Guidelines for this PR.
[ ] (if relevant) I have tested this PR in all supported browsers.
[ ] (if relevant) I have tested this PR in dark mode and light mode (if applicable).

Current dependencies on/for this PR:

main

PR #3572   👈

This comment was auto-generated by Graphite.


[Hub Generated] Review request for Microsoft.ImportExport to add version stable/2020-08-01

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of “no breaking changes
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Please follow the link to find more details on PR review process.

Hi @nivats, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review.
Action: To initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
If you think it is false positive breaking change, please provide the reasons in the PR comment, report to Swagger Tooling Team via https://aka.ma/swaggerfeedback.

@nivats You could tell the Breaking Change reviewer about it. I'm not the reviewer for breaking change.
Since most of the SDK may default resolve int as int32, it would be breaking change when re-generating. (Maybe it would be safe for using int32 rather then int64, @jianyexi Is it fine for int32 as non breaking change?)

Hi @nivats, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review.
Action: To initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
If you think it is false positive breaking change, please provide the reasons in the PR comment, report to Swagger Tooling Team via https://aka.ma/swaggerfeedback.

@nivats You could tell the Breaking Change reviewer about it. I'm not the reviewer for breaking change.
Since most of the SDK may default resolve int as int32, it would be breaking change when re-generating. (Maybe it would be safe for using int32 rather then int64, @jianyexi Is it fine for int32 as non breaking change?)

Right , for csharp , java , go , the default format is "int32" .


Error Status 402 - Not reading characteristic

Hi , I connected the Device but not reading the characteristic . AnyBody can help me pls. Thanks you

await peripheral
.discoverAllServicesAndCharacteristics()
.then((_) => peripheral.services())
.then((services) {
log('PRINTING SERVICES for ${peripheral.name}');
return services.first;
}).then((service) async {
log('PRINTING CHARACTERISTICS FOR SERVICE \n${service.uuid}');
List characteristics = await service.characteristics();
log('PRINTING CHARACTERISTICS FROM \nPERIPHERAL for the same service');
return peripheral.characteristics(service.uuid);
}).then((characteristics) {
peripheral.requestMtu(185);
for (Characteristic characteristic in characteristics) {
log('Found characteristic \n ${characteristic.uuid}');
characteristic.isReadable = true;
characteristic.isWritableWithResponse = true;
characteristic.isWritableWithoutResponse = true;
if (characteristic == null) {
print("Characteristic not found");
} else {
print(
"Characteristic:\n"
"uuid: ${characteristic.uuid}\n"
"isReadable: ${characteristic.isReadable}\n"
"isWritableWithoutResponse: ${characteristic.isWritableWithoutResponse}\n"
"isWritableWithResponse: ${characteristic.isWritableWithResponse}\n"
"isIndicatable: ${characteristic.isIndicatable}\n"
"isNotifiable: ${characteristic.isNotifiable}\n",
);
}
Stream characteristicUpdates =
peripheral.monitorCharacteristic(
'000018f0-0000-1000-8000-00805f9b34fb',
'00002af0-0000-1000-8000-00805f9b34fb');
characteristicUpdates.listen((event) {
print('##################');
print('$event');
readCharacteristic();
}, onError: (error) {
print('##################');
print('$error');
}).resume();
if (characteristic.uuid.toString().contains(writeCharacteristicUUID)) {
Future.delayed(const Duration(milliseconds: 500), () async {
// characteristic.is
try {
print(Uint8List.fromList(utf8.encode('ATZ\n')));
// await characteristic.write(
//     Uint8List.fromList(utf8.encode('ATZ\n')), false);
await peripheral.writeCharacteristic(
'000018f0-0000-1000-8000-00805f9b34fb',
'00002af1-0000-1000-8000-00805f9b34fb',
Uint8List.fromList(utf8.encode('ATZ\n')),
false);
} catch (e) {
print(e.toString());
}
});
}
}
});

this is my console:
flutter: Characteristic{service: Service{peripheralId: F2CCD470-E0F6-2D73-9495-09D446F6DC08, uuid: 000018f0-0000-1000-8000-00805f9b34fb}, _manager: Instance of 'InternalBleManager', uuid: 00002af0-0000-1000-8000-00805f9b34fb, isReadable: false, isWritableWithResponse: false, isWritableWithoutResponse: false, isNotifiable: true, isIndicatable: true} CharacteristicWithValue{value = [65, 84, 90, 10] CharacteristicWithValueAndTransactionId{transactionId: 3}
flutter: Reading temperature config
flutter: ##################
flutter: Characteristic{service: Service{peripheralId: F2CCD470-E0F6-2D73-9495-09D446F6DC08, uuid: 000018f0-0000-1000-8000-00805f9b34fb}, _manager: Instance of 'InternalBleManager', uuid: 00002af0-0000-1000-8000-00805f9b34fb, isReadable: false, isWritableWithResponse: false, isWritableWithoutResponse: false, isNotifiable: true, isIndicatable: true} CharacteristicWithValue{value = [65, 84, 90, 10] CharacteristicWithValueAndTransactionId{transactionId: 4}
flutter: Reading temperature config
flutter: ##################
flutter: BleError (Error code: 402, ATT error code: 2, iOS error code: null, Android error code: null, reason: Reading is not permitted., internal message: null, device ID: F2CCD470-E0F6-2D73-9495-09D446F6DC08, service UUID: 000018f0-0000-1000-8000-00805f9b34fb, characteristic UUID: 00002af0-0000-1000-8000-00805f9b34fb, descriptor UUID: null)
flutter: ##################
flutter: BleError (Error code: 402, ATT error code: 2, iOS error code: null, Android error code: null, reason: Reading is not permitted., internal message: null, device ID: F2CCD470-E0F6-2D73-9495-09D446F6DC08, service UUID: 000018f0-0000-1000-8000-00805f9b34fb, characteristic UUID: 00002af0-0000-1000-8000-00805f9b34fb, descriptor UUID: null)

The characteristic you're trying to read does not support reading, only notifications. Use .monitor()  and listen to the stream.

Hi @mikolak
I used monitor and check status characterstic but not read it

uuid: 00002af0-0000-1000-8000-00805f9b34fb
isReadable: true
isWritableWithoutResponse: false
isWritableWithResponse: false
isIndicatable: true
isNotifiable: true
flutter: Characteristic:
uuid: 00002af1-0000-1000-8000-00805f9b34fb
isReadable: true
isWritableWithoutResponse: true
isWritableWithResponse: true
isIndicatable: false
isNotifiable: false
[log] Found characteristic
00002af1-0000-1000-8000-00805f9b34fb
flutter: [65, 84, 90, 10]
flutter: ##################
flutter: [65, 84, 90, 10]
[log] BleError (Error code: 402, ATT error code: 2, iOS error code: null, Android error code: null, reason: Reading is not permitted., internal message: null, device ID: F2CCD470-E0F6-2D73-9495-09D446F6DC08, service UUID: 000018f0-0000-1000-8000-00805f9b34fb, characteristic UUID: 00002af0-0000-1000-8000-00805f9b34fb, descriptor UUID: null)

for (Characteristic characteristic in characteristics) {
log('Found characteristic \n ${characteristic.uuid}');
// characteristic.isNotifiable = true;
characteristic.isReadable = true;
// characteristic.isWritableWithResponse = true;
// // characteristic.isWritableWithoutResponse = true;
if (characteristic == null) {
print("Characteristic not found");
} else {
print(
"Characteristic:\n"
"uuid: ${characteristic.uuid}\n"
"isReadable: ${characteristic.isReadable}\n"
"isWritableWithoutResponse: ${characteristic.isWritableWithoutResponse}\n"
"isWritableWithResponse: ${characteristic.isWritableWithResponse}\n"
"isIndicatable: ${characteristic.isIndicatable}\n"
"isNotifiable: ${characteristic.isNotifiable}\n",
);
}
if (characteristic.uuid.toString().contains(nofityCharacteristicUUID)) {
var monStream = characteristic.monitor();
      monStream.listen((event) {
        print('##################');
        print('$event');
        characteristic.read();
        // readCharacteristic();
      }).onError((error) {
        log(error.toString());
      });
    }
    if (characteristic.uuid.toString().contains(writeCharacteristicUUID)) {
      Future<void>.delayed(const Duration(milliseconds: 500), () async {
        print(Uint8List.fromList(utf8.encode('ATZ\n')));
        // characteristic.is
        try {
          await characteristic.write(
              Uint8List.fromList(utf8.encode('ATZ\n')), false);
        } catch (e) {
          print(e.toString());
        }
      });
    }
  }

Whether a characteristic is readable or not is controlled by the peripheral. You cannot change the permission on it, you'd have to change the peripheral's firmware.

Ok, thank you @mikolak


SparseList Follow Protocol Speedup

The existing implementation always binary searches over the entire index vector. However, we should always be doing lookups in increasing order, so we can actually "consume" the index vector instead by moving up the lower search bound each time. This also lets us use the expsearch function instead because we now have reason to believe that the lower bound is close to the true value.
Before Change:
┌ Info: experiment
└   sp = 0.01
[ Info: merge
  78.459 μs (2 allocations: 96 bytes)
[ Info: hash (search)
  290.835 μs (2 allocations: 96 bytes)
[ Info: gallop
  89.306 μs (2 allocations: 96 bytes)
[ Info: hash construction
  787.695 μs (63 allocations: 1.62 MiB)
[ Info: hash (hashtable)
  170.373 μs (2 allocations: 128 bytes)
┌ Info: experiment
└   sp = 0.005
[ Info: merge
  51.509 μs (2 allocations: 96 bytes)
[ Info: hash (search)
  161.717 μs (2 allocations: 96 bytes)
[ Info: gallop
  62.533 μs (2 allocations: 96 bytes)
[ Info: hash construction
  782.748 μs (63 allocations: 1.62 MiB)
[ Info: hash (hashtable)
  82.390 μs (2 allocations: 128 bytes)
┌ Info: experiment
└   sp = 0.001
[ Info: merge
  15.879 μs (2 allocations: 96 bytes)
[ Info: hash (search)
  37.581 μs (2 allocations: 96 bytes)
[ Info: gallop
  13.650 μs (2 allocations: 96 bytes)
[ Info: hash construction
  785.824 μs (63 allocations: 1.61 MiB)
[ Info: hash (hashtable)
  9.868 μs (2 allocations: 128 bytes)
┌ Info: experiment
└   sp = 0.0005
[ Info: merge
  13.307 μs (2 allocations: 96 bytes)
[ Info: hash (search)
  19.855 μs (2 allocations: 96 bytes)
[ Info: gallop
  6.050 μs (2 allocations: 96 bytes)
[ Info: hash construction
  785.667 μs (63 allocations: 1.62 MiB)
[ Info: hash (hashtable)
  4.053 μs (2 allocations: 128 bytes)
┌ Info: experiment
└   sp = 0.0001
[ Info: merge
  9.198 μs (2 allocations: 96 bytes)
[ Info: hash (search)
  3.912 μs (2 allocations: 96 bytes)
[ Info: gallop
  1.063 μs (2 allocations: 96 bytes)
[ Info: hash construction
  783.611 μs (63 allocations: 1.61 MiB)
[ Info: hash (hashtable)
  816.976 ns (2 allocations: 128 bytes)

After change:
┌ Info: experiment
└   sp = 0.01
[ Info: merge
  93.398 μs (2 allocations: 96 bytes)
[ Info: hash (search)
  88.104 μs (2 allocations: 96 bytes)
[ Info: gallop
  92.542 μs (2 allocations: 96 bytes)
[ Info: hash construction
  777.537 μs (63 allocations: 1.61 MiB)
[ Info: hash (hashtable)
  174.599 μs (2 allocations: 128 bytes)
┌ Info: experiment
└   sp = 0.005
[ Info: merge
  58.945 μs (2 allocations: 96 bytes)
[ Info: hash (search)
  54.867 μs (2 allocations: 96 bytes)
[ Info: gallop
  60.835 μs (2 allocations: 96 bytes)
[ Info: hash construction
  787.040 μs (63 allocations: 1.62 MiB)
[ Info: hash (hashtable)
  86.802 μs (2 allocations: 128 bytes)
┌ Info: experiment
└   sp = 0.001
[ Info: merge
  21.538 μs (2 allocations: 96 bytes)
[ Info: hash (search)
  12.863 μs (2 allocations: 96 bytes)
[ Info: gallop
  14.054 μs (2 allocations: 96 bytes)
[ Info: hash construction
  757.483 μs (63 allocations: 1.61 MiB)
[ Info: hash (hashtable)
  8.999 μs (2 allocations: 128 bytes)
┌ Info: experiment
└   sp = 0.0005
[ Info: merge
  18.049 μs (2 allocations: 96 bytes)
[ Info: hash (search)
  6.152 μs (2 allocations: 96 bytes)
[ Info: gallop
  6.423 μs (2 allocations: 96 bytes)
[ Info: hash construction
  790.806 μs (63 allocations: 1.61 MiB)
[ Info: hash (hashtable)
  3.876 μs (2 allocations: 128 bytes)
┌ Info: experiment
└   sp = 0.0001
[ Info: merge
  14.527 μs (2 allocations: 96 bytes)
[ Info: hash (search)
  929.694 ns (2 allocations: 96 bytes)
[ Info: gallop
  1.065 μs (2 allocations: 96 bytes)
[ Info: hash construction
  792.627 μs (63 allocations: 1.62 MiB)
[ Info: hash (hashtable)
  810.836 ns (2 allocations: 128 bytes)

Could use a close look though, I'm not 100% sure how the lowering works with 'thunk'

@willow-ahrens  Just wanted to bump this because I'd forgotten about it. It doesn't seem like the python test failure is related to the PR, but I'm not sure.

This took a while to merge as I needed to fix python ci


fix length check for too short packets

Depends on #1698.
A too short packet would lead to an out-of-bounds slice access (which panics).

Codecov Report

Merging #1699 into master will decrease coverage by 0.12%.
The diff coverage is 83.87%.

@@            Coverage Diff             @@
##           master    #1699      +/-   ##
==========================================
- Coverage   87.39%   87.27%   -0.12%
==========================================
  Files          96       96
  Lines        6263     6298      +35
==========================================
+ Hits         5473     5496      +23
- Misses        558      566       +8
- Partials      232      236       +4

Impacted Files
Coverage Δ

packet_unpacker.go
91.18% <ø> (-0.49%)
:arrow_down:

session.go
72.97% <37.5%> (-0.78%)
:arrow_down:

packet_handler_map.go
91.49% <90.74%> (-2.15%)
:arrow_down:

Continue to review full report at Codecov.

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


Origin regex fails depending on query param

Hello,
I use the following value for the origin option:
origin: [/^https?:\/\/([^\/]+\.)?welt\.de/, /localhost/, /<IP_ADDRESS>/]

It works, usually. But this is weird: I am on the website
http://local.welt.de:9000/testgpr/Funkotron/article156909079/XHTML-oEmbed-Migration-Testartikel.html
From that same page, I XHR the 2 urls

https://beta.welt.de/oembed?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DDLzxrzFCyOs

https://beta.welt.de/oembed?url=https%3A%2F%2Fbeta.welt.de%2Foembed%3Ftype%3Diframe%26width%3D480%26height%3D340%26url%3Dhttp%3A%2F%2Fdutyfarm.welt.de%2Fsudoku_daily.html

https://beta.welt.de/oembed is where my cors enabled node server is running. The first request works fine, the second request however fails for not providing Access-Control-Allow-Origin headers. I really don't get it, the only difference is the query param url.

Ok I am sorry, it seems it has been a nasty cache invalidation issue that has solved itself over the weekend.

"There are only two hard problems in Computer Science:
cache invalidation and naming things."


Design an animated flow/network diagram that shows traffic between building blocks and their internal databases

Blocked on https://github.com/GovStackWorkingGroup/IM_Demo_InstallingScripts/issues/9


Easy step by step directions to utilize TotalSegmentator

First and foremost forgive my novice. I'm an MD with a small computer programing background interested in utilizing TotalSegmentator as part of a separate research project.  Goal is to incorporate it as part of a separate process. Is there somewhere with easy step by step instructions on how to segment a folder containing a set of DICOM files through the program?

Unfortunately there is no step by step instructions for this.
Basically you first have to convert the DICOM to nifti using e.g. the dcm2niix library.
Then you have to run TotalSegmentator.
To do this automatically for all subjects in the directory it would make sense to use a scripting language like Bash or Python.

We created a 3D Slicer extension to make TotalSegmentator easily usable for clinicians. It requires only a few button clicks to install and run it on any DICOM image. See step-by-step instructions here: https://github.com/lassoan/SlicerTotalSegmentator#totalsegmentator

Big fan of 3D slicer! but I was looking for more of a way to run it though the command line. Maybe I am not being descriptive enough (or you are maybe giving me too much credit), but when you say "Then you have to run TotalSegmentator", what is a step by step instructions on how to do that?

I undestand @EnioMDMPH issue, not everyone will know how to create a Virtual Environment.
And for me although I have created a Environment with a Python 3.7, with NumPy and the Pytorch (for CUDA 11.7, the same version that I know that works in my PC, using conda) and after that pip installing TotalSegmentator, I don't know how to properly use the following command: TotalSegmentator -i ct.nii.gz -o segmentations
As @wasserth  said I converted a  "DICOM to nifti using e.g. the dcm2niix library" (I also try using the example_ct.nii.gz from this reference_files and renaming to ct.nii.gz) but when I execute this line in my Windows PowerShell: TotalSegmentator -i ct.nii.gz -o segmentations the result are the same as I just use this TotalSegmentator it shows me a list of Softwares and if I select anyone it will load the file TotalSegmentator from my virtual environment Script folder.

not everyone will know how to create a Virtual Environment

If someone wants to use TotalSegmentator engine directly then we can require very basic knowledge, such as how to create a virtual Python environment. Those who do not want to know about virtual Python environments can use TotalSegmentator in higher-level frameworks, such as 3D Slicer.

And for me although I have created a Environment with a Python 3.7

Python 3.7 is very old. The last bugfix release was 3 years ago. I would recommend to use at least Python 3.9, otherwise you may run into issues.

when I execute this line TotalSegmentator -i ct.nii.gz -o segmentations in my Windows PowerShell (that I run as an administrator) the result are the same as I just use this TotalSegmentator it shows me a software list

On Windows, shebang (#!/usr/bin/env python line at the beginning of a file) is not a thing. Instead, you need to run the script using the appropriate interpreter - in this case Python - like this:
path/to/python.exe path/to/TotalSegmentator -i ...

I was able to create a virtual environment, but when I went to "pip install totalsegmentator" I receive this error:
ERROR: Cannot install totalsegmentator==1.2, totalsegmentator==1.3 and totalsegmentator==1.4.0 because these package versions have conflicting dependencies.
The conflict is caused by:
totalsegmentator 1.4.0 depends on SimpleITK==2.0.2
totalsegmentator 1.3 depends on SimpleITK==2.0.2
totalsegmentator 1.2 depends on SimpleITK==2.0.2
I subquently tried to "pip install totalsegmentator==1.5.0" and got this error:
ERROR: Ignored the following versions that require a different python version: 1.21.2 Requires-Python >=3.7,<3.11; 1.21.3 Requires-Python >=3.7,<3.11; 1.21.4 Requires-Python >=3.7,<3.11; 1.21.5 Requires-Python >=3.7,<3.11; 1.21.6 Requires-Python >=3.7,<3.11; 1.6.2 Requires-Python >=3.7,<3.10; 1.6.3 Requires-Python >=3.7,<3.10; 1.7.0 Requires-Python >=3.7,<3.10; 1.7.0rc1 Requires-Python >=3.7,<3.10; 1.7.0rc2 Requires-Python >=3.7,<3.10; 1.7.1 Requires-Python >=3.7,<3.10; 1.7.2 Requires-Python >=3.7,<3.11; 1.7.3 Requires-Python >=3.7,<3.11; 1.8.0 Requires-Python >=3.8,<3.11; 1.8.0rc1 Requires-Python >=3.8,<3.11; 1.8.0rc2 Requires-Python >=3.8,<3.11; 1.8.0rc3 Requires-Python >=3.8,<3.11; 1.8.0rc4 Requires-Python >=3.8,<3.11; 1.8.1 Requires-Python >=3.8,<3.11; 2.5.2 Requires-Python !=3.0.,!=3.1.,!=3.2.,!=3.3.,<3.9dev,>=2.7
ERROR: Could not find a version that satisfies the requirement torch>=1.6.0a (from nnunet-customized) (from versions: none)
ERROR: No matching distribution found for torch>=1.6.0a
Currently running Python 3.11.2
Any suggestions? Also wondering if I should have started a new "problems installing thread"


Lab 7 Minor Grammatical Correction

From the "Visualising shift-reduce parsing" section, don't believe "And" should start a sentence, instead potentially using a comma instead of a full stop, and continuing the sentence on.
i.e "...as lists of tokens with their indices, and the list of edges..."

Yep, we can fix that. I'm definitely not aiming for perfect grammatical and formal language in the labs. But still nice to fix little things. 1 points for this.


Mail accounts admin

I have successfully installed the mail server with yours and Sven Kaubers instructions - thanks!
I'd like to have an admin portal for managing user accounts, etc and was wondering if you have any suggestions. There are lots of postfixadmin docker containers out there, I just don't want to pick the wrong path if you know of or have successfully used a package that works well with your docker-mailserver

In case that somebody lands here we've just created a docker image merging dovecot-mysql branch with current tomav/docker-mailserver, here the code.
Cheers.


fix to zephyr: Add direct-xip mode to Zephyr configuration

Made swap mode selection always explicitly.
Signed-off-by: Andrzej Puzdrowski<EMAIL_ADDRESS>

@davidvincze You can squash it to kconfig commit if you want.


Deploying to Humanitec

WIP
Motivation

Approach

Alternate Designs

Possible Drawbacks or Risks

TODOs and Open Questions

Learning

Screenshots

📣 NOTIFICATION
You are receiving this message because we did not publish any packages.
Generated by @thefrontside/actions


US127139: Edit Fullscreen dialog to have a margin to preserve context

Made the following changes to the existing d2l-dialog-fullscreen component, consistent with the design at https://xd.adobe.com/view/84fce6d7-52ec-427b-a259-693a98d6bca9-d1af/screen/e7dd9b0a-3d5f-452a-b200-65579f8a68d5?fullscreen.

Here are some gifs I recorded. They look way smoother on my machine so I guess the screencap lowered the quality significantly.
d2l-dialog-fullscreen on an LMS page:

Responsive behaviour:

Regular fullscreen dialog:

Async dialog:

On mobile:


How to configure CRA to point to dev ASP.NET Core server for API calls?

I realize this is a React/JavaScript question more than an ASP.NET Core question, but it would be nice if in the "Run the CRA server independently" section there was a note about how to point your API calls to the appropriate localhost/port for development. Else, the weather forecast page will attempt to fetch from localhost:3000/... and fail.

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

ID: 261c9875-3db6-4d30-f9d6-922a9334ecb2
Version Independent ID: b8f8f7c4-9c90-869d-9fd7-a887bc28f262
Content: Use the React project template with ASP.NET Core
Content Source: aspnetcore/client-side/spa/react.md
Product: aspnet-core
GitHub Login: @SteveSandersonMS
Microsoft Alias: scaddie

@VirtuaBoza  thanks for the feedback. We'll try to address this in the next doc sweep.


Fix brute force partitioning out of bounds reads/writes

If the block/grid size generated is not an exact match to the population
or rather is larger than the maximum buffer size,
then out of bounds global reads/writes could occur for agent functions which iterate non-partitioned messaging.
This is prevented by thread bounds checking on global reads / writes, but as the agent function will still execute default values are loaded.
Agent array variables then presented possible issues, so null pointers are passed to the relevant functions which trigger special cases. This was the simplest change which does not require changing of function prototypes (and therfore functions.c).
Closes #189

This has been tested on Linux and it appears to resolve the boids brute force issues without harming behaviour, but should still be tested on Windows before merge.

Good find


No video from SV3C camera in HA

Hi! I've got 3 cameras from SV3C (https://sv3c.aliexpress.com/store/5720035) and before installing them I checked RTSP stream and I could play it via ffplay without any issue (the URL is like rtsp://192.168.1.x/0 or rtsp://user:pass@192.168.1.x/0).
One camera shows well in HA via simple card:
type: custom:webrtc-camera
url: rtsp://cam6.domain/0

while 2 other cameras show nothing:

Again, I tested those cameras with ffplay (and VLC) and RTSP stream is OK. Moreover, all those 3 cameras are captured by kerberos.io agents (on another host, DVR). HA is running on RPi 3 in core mode (PVE + service).
In addition I tried to setup go2rtc on DVR host via docker:
  go2rtc:
    image: alexxit/go2rtc:latest
    container_name: go2rtc
    restart: always
    privileged: true
    ports:
      - "1984:1984"
      - "8554:8554"  # RTSP port (optional, if you need RTSP access)
      - "8555:8555"  # WebRTC
#      - "8888:8888"
#    network_mode: host
    environment:
      - TZ=${AGENT_TIMEZONE}
    volumes:
      - "/usr/local/src/kerberos.io/go2rtc:/config"

with go2rtc/go2rtc.yaml as:
streams:
  cam7:
    - rtsp://cam7.domain/0
  cam8:
    -<EMAIL_ADDRESS>
and none of the links that I can see at http://dvr:1984 works, the same black screen.
Can you please help me how to debug this and dig more info to figure out what's wrong?
I don't see any logs in HA log file or syslog, and see nothing in container as well:
go2rtc           | 13:52:19.296 INF go2rtc platform=linux/amd64 revision=a4885c2 version=1.9.4
go2rtc           | 13:52:19.304 INF config path=/config/go2rtc.yaml
go2rtc           | 13:52:19.306 INF [api] listen addr=:1984
go2rtc           | 13:52:19.306 INF [rtsp] listen addr=:8554
go2rtc           | 13:52:19.307 INF [webrtc] listen addr=:8555/tcp

Most likely your camera is using the H265 codec. And your browser (including the RTC technology) does not support it.
https://github.com/AlexxIT/go2rtc?tab=readme-ov-file#codecs-madness
You can find out the codec by looking at the stream information in the go2rtc WebUI.

Oh! Thank you very much for the update!
Looks like the camera is really h265, the probe link has this in the json output:
      "medias": [
        "video, recvonly, H265",
        "audio, recvonly, PCMU/8000"
      ],

Can you please help me if I couldn't reconfigure camera to h264 on a weekend, as I can see in the docs I can use go2rtc to transcode into mjpeg via ffmpeg, right?
And in this case the config should be like this:
streams:
  camera1:
    - ffmpeg:rts://cam7.domain/0#video=mjpeg

I'm asking this because I lost in the docs (https://github.com/AlexxIT/go2rtc?tab=readme-ov-file#module-mjpeg).
Thanks in advance!


Issues getting populate hint typechecking to work

Describe the bug
I'm not getting type error when I would expect when writing functions with that take Loaded types with nested populate hints. I'm guessing this is because of the nature of string unions? Minimal reproduction repo attached below, but a quick and dirty example here:
NOTE I am using Typescript version 5.4.3
Assume we have entities A, B, C. A is M:M B, B is M:1 C.
function takesNested(a: Loaded<A, 'b' | 'b.c'>) {}

// This returns a Loaded<A, 'b'>
const loadedAB = await em.findOneOrFail(A, 1, { populate: ['b'] })

takesNested(loadedAB); // This does not cause a compile error

Note that this also doesn't fail with a function that just takes the nested populate hint requirement. This one I am less certain on the root cause of. Surely 'b' and 'b.c' should cause a type mismatch?
function takesNested(a: Loaded<A, 'b.c'>) {}

// This returns a Loaded<A, 'b'>
const loadedAB = await em.findOneOrFail(A, 1, { populate: ['b'] })

takesNested(loadedAB); // This does not cause a compile error

Both of these examples are in the reproduction repo
Reproduction
https://github.com/chrisbenincasa/reproduction-populate-hint
What driver are you using?
@mikro-orm/better-sqlite
MikroORM version
6.1.12
Node.js version
20.11.1
Operating system
Ubuntu 23.10
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Slack.
[X] The provided reproduction is a minimal reproducible example of the bug.

FWIW, this feels like the opposite problem of https://github.com/mikro-orm/mikro-orm/discussions/5374.

That is probably not related, reverting it does not fix this one. The reason why I added the branded types had nothing to do with this, and #5374 was a side effect of that change.

I suspect that this has something to do with type variance. In TypeScript 4.7, two generic type modifiers in and out are added to allow explicitly specify whether a generic type is covariant or contravariant:
<in Arguments, out Return>

See https://devblogs.microsoft.com/typescript/announcing-typescript-4-7/#optional-variance-annotations-for-type-parameters for details


fix: generate random password the first time

What
When a customer has a guest account, if the customer tries to log in with an external provider it is currently throwing cause no password has been provided and a guest account exists. Now, when calling the create, we provide a randomly generated password that the user can reset later if he wants to use the default login flow.
wdyt @tsvetann ?

LGTM thanks mate

I am a bit busy at the moment guys, I ll merge this one probably next week 💪