Google Login in Laravel Admin | Custom UserProvider | Not Working

Laravel Version: 7.15.0
PHP Version: PHP/7.3.19
Laravel-admin: 1.8.1

Description:
Task: I want to add the google login functionality

i have added Socialite done the config and created a route and callback
Callback Code:
$existingUser = Administrator::where('email', $user->email)->first();
if($existingUser){
// log them in
Auth::loginUsingId($existingUser->id);
//auth()->login($existingUser, true);
}

Custom User Provider added as per documentaion -> CustomUserProvider implements UserProvider

public function retrieveById($identifier)
{
$user = Administrator::where('id','=',$identifier)->first();
return isset($user)?$user:null;
}

Email field added to admin_users table

But Still redirecting me to Login Page -> /admin/auth/login
Steps To Reproduce:

Laravel Version: 7.15.0
PHP Version: PHP/7.3.19
Laravel-admin: 1.8.1

Description:
Task: I want to add the google login functionality

i have added Socialite done the config and created a route and callback
Callback Code:
$existingUser = Administrator::where('email', $user->email)->first();
if($existingUser){
// log them in
Auth::loginUsingId($existingUser->id);
//auth()->login($existingUser, true);
}
Custom User Provider added as per documentaion -> CustomUserProvider implements UserProvider

public function retrieveById($identifier)
{
$user = Administrator::where('id','=',$identifier)->first();
return isset($user)?$user:null;
}

Email field added to admin_users table

But Still redirecting me to Login Page -> /admin/auth/login
Steps To Reproduce:

Have you tried to log in using guard admin?
i.e.
auth('admin')->login($user, true)


Breaking change in version 1.2.1

This is more an FYI for anyone who is upgrading from 1.2.0 or lower to 1.2.1. This might need to be called out in the changelog as I did not see this anywhere.
Summary
The luarocks version changed in the docker image.
kong:1.2.0 => luarocks version 2.4.3
kong:1.2.1 => luarocks version 3.1.3
If you have a custom plugin where you use the luarocks feature that builds your rock_spec from all the files in your lua directory, instead of specifying all the files in the rockspec file. This upgrade will cause the rock_spec file for your plugins to be missing all the file references.
Steps To Reproduce

Create a plugin and put the handler in a sub folder called lua.

/lua/kong/plugins/my/plugin/handler.lua
/my-plugin-1.0.0-1.rockspec
my-plugin-1.0.0-1.rockspec:
package = "my-plugin"
version = "1.0.0-1"

description = {
  summary = "Test Kong plugin",
  license = "Apache 2.0"
}

dependencies = {
  "lua >= 5.1"
}

build = {
  type = "builtin",
  modules = {}
}

Buld and install on docker image kong:1.2.1
Enable my-plugin when running the kong docker image.
Kong will error saying it cannot find plugin my-plugin. If built on kong:1.2.0 image it works fine.
If you interogate the rock_spec file in the docker image, it will look something like this:

kong:1.2.1
rock_manifest = {
   ["my-plugin-1.0.0-1.rockspec"] = "<some file hash>"
}

kong:1.2.0
rock_manifest = {
   ["my-plugin-1.0.0-1.rockspec"] = "<some file hash>",
   lua = {
      kong = {
         plugins = {
            my = {
               plugin = {
                  ["handler.lua"] = "<some file hash>",
                  ["schema.lua"] = "<some file hash>"
               }
            }
         }
      }
   }
}

Additional Details & Logs
To fix this you can just update your rockspec format to version 3 'rockspec_format = "3.0"' and delete the build directive:
package = "my-plugin"
version = "1.0.0-1"
rockspec_format = "3.0"

description = {
  summary = "Test Kong plugin",
  license = "Apache 2.0"
}

dependencies = {
  "lua >= 5.1"
}

Kong version 1.2.1 docker image
Operating system: Docker for windows

@jvandervelden This was not an intentional change. If this is happening, it's most definitely a LuaRocks bug. I'll look into that. Thanks for reporting!

No problem, I just figured you might want to call it out in your 1.2.1 changelog, since it will break some people's plugins.

I could not reproduce this in LuaRocks as of the latest master (latest Kong includes LuaRocks 3.3.1), but I added a test just in case:
https://github.com/luarocks/luarocks/commit/6a11f673d02145ffe03aea173817ea9ab566f784


(new feature) Adding a way for template to generate combination results

I love this plugin so far, and I think it can grow better.
I was thinking something like:
in template file:

tablename: "table"
combination: "{{adjective}} {{noun}}"  or "{{adjective}} and {{adjective}}"
adjective: big, large, small, tiny
nouns: house, sword, thing

And so on for adverbs, verbs…
And if it was possible to add weights to terms to alter probabilities (e.g., small::0.5) it would be awesome.

That's a great suggestion, thank you so much!
I've added a template feature in 0.2.8, usage described here: https://github.com/alexkurowski/solo-toolkit?tab=readme-ov-file#custom-table-templates
I'm not sure how to add weight in the way that would be intuitive though. I'd like the user to have full control of the output formatting.
For now you can duplicate the heavier words to make them appear more often. I know it's not ideal, especially for something like 2d6 tables.
I'll see if I can come up with something better.

Thank you, this awesome ! Duplication of words instead of weight is still a very good way to achieve the same goal !


[feat] Regular Expression Analysis

It's not possible to confirm that arbitrary string is matching to regular expression in predictable time.
However it's possible to limit this question with constraints.
And it's possible to decide if regular expression can be finished inside limited decision frame.
It should be possible to mark chosen regular expression as predicates.

Duplicate of https://github.com/facebook/flow/issues/4654
/cc @vkurchatkin

Hi, this is not really a duplicate bud instead badly written from my side, sorry :smiling_imp:
The point is that some regular expressions show that they can be used as attack vector — ReDoS
I believe that some analysis can be done and flow can issue a warning when linting is configured


Docker Integration

Added a Docker file and linked repository to DockerHub so that we can have automated Docker Images produced on every repository commit.
These Docker images can be used to execute the code instead of compiling it for each specific system varient (and any problems that entails). They give a unified distribution OS with dependancies to give consistent running on any system irrespective of the machine type used.

The commit history for this pull request is strange, with very old commits being included. Since this docker file is separate, could you just check out the current develop branch, add in the docker file, and redo this pull request?

Also, if I wanted to try out this docker implementation, what would I do? This is just a file that allows docker to build this on an external website, right? Could you give some further instructions so people can try this out?

If made a new pull with a cleaned up commit history and also added
instructions to the readme
On 1 December 2017 at 10:01, eosullivan<EMAIL_ADDRESS>wrote:

Also, if I wanted to try out this docker implementation, what would I do?
This is just a file that allows docker to build this on an external
website, right? Could you give some further instructions so people can try
this out?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/WCSim/WCSim/pull/224#issuecomment-348453638, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ANcOQfcpdSAFENyhwKkFFQHsGb2JiY_Dks5s786XgaJpZM4QYwOT
.


Please add two error check

I received memory exception of:

NullPointerException (@ThemeableBrowser$ThemeableBrowserClient:onPageStarted:1176) {main}
NullPointerException (@ThemeableBrowser$6$6:onPageFinished:703) {main}

Fixed with version 0.2.7.

New NullPointerException:
NullPointerException (@ThemeableBrowser:goForward:476) {main}
NullPointerException (@ThemeableBrowser:goBack:467) {main}
NullPointerException (@ThemeableBrowser$4:run:307) {main}
NullPointerException (@ThemeableBrowser$6$5:onItemSelected:658) {main}
ThemeableBrowser version 0.2.6

Could you please elaborate on reproduction steps?

Sorry, I can't.  These exceptions received from GA crash report.
And only these information, GA report exception not with callstack....

Fixed in version 0.2.9. Please note that due to Cordova's migration to npm, plugin ID has been updated to cordova-plugin-themeablebrowser.


Contemplating about integrate recognition into a surveillance system...

Hi there, great work.
I am developing a surveillance system that using face recognition service on smart edge devices that directly send back the captured face images.
There are about 4 smart IPC working at the same time(even more than 16 in the future),capture average 4000 face image per day(about 1000 image per camera per day), consume about 137GB storage per day.
The recognition algorithm I am using cost about 1.7min to execute the search.
Are there any other viable product that using this framework could provide me some advises. thx

Hi
Is 1.7 minutes performance of CompreFace or your current system?
How many images are stored right now?

Hi
Is 1.7 minutes performance of CompreFace or your current system?
How many images are stored right now?

My current system is using DAHUA integrated device whose CPU is kinda low.
There are about 10k images stored right now. Not yet deploy CompreFace to test.

We have a CompreFace in production now that stores 50k images, and it takes less than 300ms for a request.
The hardware - CPU only, four cores, 16Gb RAM.
Have you tried to make several requests? The first request loads embeddings into the memory, so it may take time on slow machines. It takes about 5 seconds on our hardware...


Backup my Preferences !

Hi,
Will you be able to add an option to Export / Import the preferences of the addon?
Just in case if we have to reinstall Firefox for example.
Sincerely,
Machou
=====
Salut,
Pourrai-tu ajouter une option pour Exporter / Importer les préferences de l'addon ?
Au cas où si on doit reinstaller Firefox par exemple.
Cordialement,
Machou

Hello!
Adding an export function is quite straightforward. The import one is a bit more complicating as the provided settings must be checked to ensure they are valid.
If someone reinstall Firefox, as long as the bookmarks are restored (via the Firefox backup/restore feature, not via an HTML file) before, there should be no problem. Otherwise, if a folder is missing, the associated option can be reset to its default and an information message can be displayed to the user.
I am adding this to the roadmap. 🙂


How RegistriesRandomizerProvider works?

Hi,
Im trying to implement custom RandomizerRegistry with low priority(e.g -100) in order to check if class contains builder() method.
If so construct relevant Builder class(generated by Immutable project), then populate fields within Buider class with internal EasyRandom and finally call his build() method to return original requested class to be randomized.
Everything is implemented via java reflection and it seems that works but what I found is that RegistriesRandomizerProvider goes accross all registries to check if any randomizer exists. And then returns first one.
My problem is that my registry class is always checked also when for instance String field is incoming and it could cause performance issues.
My question is why following method always evaluate all registries and not stop when first one if found?
private Randomizer<?> getRandomizer(final Provider provider) {
        return registries.stream()//it should be already sorted by priority
                .map(provider::getRandomizer)//it always goes for each registered registry, why not to stop loop when first one is found?
                .filter(Objects::nonNull)
                .sorted(priorityComparator) //what does it mean, we sort all found randomizers
                .findFirst().orElse(null);
    }

thanks

@metalpalo The reason the registries are all evaluated because sorted operation, you may need to process all list items just to apply the sorted.
Your point is totally valid, because the registries already sorted when added new one.

@trinhnx  thanks for response,
I good understand, evaluation all registries are necessary right?. If so then we need to define priority on Randomizer classes too?
I put my custom user registry into parameters before EasyRandom construction, so everyting should be sorted within constructor.
I dont see option that user registry can be added later through parameters and change is automatically taken into account.
Another question:
As mentioned I implemented custom registry to check if class, interface contains builder() method(comming from Immutables) framework, if given method exists I call it to construct Builder class then I want to populate fields via EasyRandom instance.
So I create singleton instance if EasyRandom again and call nextObject. I dont have access to doPolulate method(package private). I would like to prefer it due to go in identical RandomizerContext but when looking at RegistriesRandomizerProvider context are not used. But my randomizer could implement ContextAwareRandomizer right? What can I do in order to call doPopulate method instead doNext() one. I need to create subclass in identical package?
thanks


node.js build fail

Hi all,
I am new to flynn, this is my first experience with it. My sample node.js application build failed with error no 7. Debug info attached bellow, please help me to fix this issue.
https://gist.github.com/anonymous/855b43cd2eaccede7095

@sukitha do you have any firewall rules blocking outbound traffic?

I checked with infastructure team and they said there are no any blocking rule applied

@sukitha ok so it looks like the build is stuck trying to run the following command:
curl --silent --get --data-urlencode range=0.10.x https://semver.herokuapp.com/node/resolve

Can you try running that from the command line on the host running Flynn? It should output a version number like 0.10.37.

i installed flynn in digital-ocean its working fine. may be our network issue as you say


Need to create a Travis CI job for the library

This should run the testes, should report test coverage, and should make sure that it builds.
I wonder if also we need to have a reference implementation of the project in a example folder?

I wonder if also we need to have a reference implementation of the project in a example folder?

I would really like to see this. I have a horrible project for working with these libs in practice. I'll spare my disparaging go comments.

closed by #28


Wasm runtime contains a runtime_apis custom section but no runtime_version section

Is there an existing issue?

[X] I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

[X] This is not a support question.

Description of bug
The Rococo v2.2 genesis runtime contains a runtime_apis custom section but no runtime_version section.
I've also noticed the problem with the Nodle genesis runtime.
This problem does not exist with the Westend, Kusama or Polkadot runtimes.
I've uploaded the decompressed Rococo v2.2 genesis runtime converted to ASCII here: https://gist.github.com/tomaka/52dfe5fd4588eecdf57b4418dce48483
According to the Wasm spec, a custom section contains: a 0 byte (indicating a custom section), then the length of the section, then the length of the name of the section, then the name, then the rest of the section.
See https://www.w3.org/TR/2022/WD-wasm-core-2-20220419/binary/modules.html#custom-section
If I grep 12, 114, 117, 110, 116, 105, 109, 101, 95, 97, 112, 105, 115 (12 bytes followed with runtime_apis) in the Rococo runtime uploaded above, there's one result.
But if I grep 15, 114, 117, 110, 116, 105, 109, 101, 95, 118, 101, 114, 115, 105, 111, 110 (15 bytes followed with runtime_version), there's no result.
Steps to reproduce
No response

The rococo v2_2 chain spec was probably generated without this commit: https://github.com/paritytech/polkadot/commit/2da9a7e6bb185b5268afe24ba63b7506953bf4f3
The commit adding the v2_2 chain spec was added one day later, probably not including the commit above: https://github.com/paritytech/polkadot/commit/cc080f052b558db37c560b7a0367e37e46418601


Add check null for glueUDB

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/10502/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/10504/
Test FAILed.

Jenkins, test this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/10505/
Test FAILed.

Jenkins, test this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/10506/
Test FAILed.

Jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/10510/
Test PASSed.

alluxio-bot, merge this please

alluxio-bot, cherry-pick this to branch-2.3 please


Change background images to Brent's illustrations

Brent took our image sizes and is providing new illustrations
He expects them to be plug 'n play, little work on our part except replacing image files

Received email from Brent that he will not have the time to make his illustrations up to his standards. We will release with our current graphics


Models won't render in OpenGL

Hello I'm new here. I'm just started moding 3 months ago and I stumbled upon your program and i get interested. The thing here is I'm using an average laptop and my GPU won't work in OpenGL. Is there a way to force render models in Dx9? plss reply and thank you. (sorry if my english is a bit off :P )

No, there isn't.


Formatting docstrings

Formatting docstrings according to PEP 257

Codecov Report

Merging #48 (589d2ac) into main (b1743a7) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #48   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           12        12
  Lines          364       364
=========================================
  Hits           364       364

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 b1743a7...589d2ac. Read the comment docs.


Automated cherry pick of #3010: lbagents: 禁止在公有云、托管物理机上部署

Cherry pick of #3010 on release/2.11.
#3010: lbagents: 禁止在公有云、托管物理机上部署

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.11@dae1b62). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff               @@
##             release/2.11   #3015   +/-   ##
==============================================
  Coverage                ?   7.16%
==============================================
  Files                   ?     476
  Lines                   ?   76663
  Branches                ?       0
==============================================
  Hits                    ?    5494
  Misses                  ?   70706
  Partials                ?     463

Flag
Coverage Δ

#aFlag
7.16% <0%> (?)

Impacted Files
Coverage Δ

pkg/compute/models/loadbalanceragents_deploy.go
0.34% <0%> (ø)

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 dae1b62...b3deab9. Read the comment docs.

/lgtm

/approve


chore(#682): update circleci node image

Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[ ] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

Update CircleCI Node image
Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[ ] All new and existing tests are passing.

Screenshots/Media:

Summary by CodeRabbit

Chores

Updated the Docker image used in our continuous integration process, which includes newer versions of Node.js and its dependencies.

Review Status
Actionable comments generated: 0
Configuration used: CodeRabbit UI
Commits
Files selected for processing (1)
Files skipped from review due to trivial changes (1)

Re-run the review

@coderabbitai review


Can you bump the version?

For those who install, the latest version is still 0.7.1 from two years ago, which misses fixes such as https://github.com/nielstron/pyfronius/pull/7. It would be great to get a new release on pypi.
Thanks!

Should be fixed in 19f5cfc


fix(ZMS-3436): multiple clicks on appointments lead to multiple reservations

Description
Short description or comments
Reference
Issues #XXX

@coderabbitai full review


How to build?

can you write the readme?

parallels@ubuntu-linux-20-04-desktop:~/ws$ cd src/mocap4ros2_optitrack/
parallels@ubuntu-linux-20-04-desktop:~/ws/src/mocap4ros2_optitrack$ vcs import ~/ws/src < dependency_repos.repos
..
=== /home/parallels/ws/src/mocap (git) ===
Cloning into '.'...
=== /home/parallels/ws/src/mocap_msgs (git) ===
Cloning into '.'...
parallels@ubuntu-linux-20-04-desktop:~/ws/src/mocap4ros2_optitrack$ cd ../..
parallels@ubuntu-linux-20-04-desktop:~/ws$ colcon build
Starting >>> mocap_msgs
Starting >>> mocap_control_msgs
Starting >>> mocap_marker_viz_srvs
Starting >>> mocap_robot_gt_msgs
Finished <<< mocap_robot_gt_msgs [4.46s]
Finished <<< mocap_control_msgs [4.59s]
Starting >>> mocap_control
Finished <<< mocap_marker_viz_srvs [4.60s]
Finished <<< mocap_msgs [4.90s]
Starting >>> mocap_marker_publisher
Starting >>> mocap_marker_viz
Starting >>> mocap_robot_gt
Finished <<< mocap_marker_publisher [3.69s]
--- stderr: mocap_robot_gt
/home/parallels/ws/src/mocap/mocap_robot_gt/mocap_robot_gt/src/mocap_robot_gt/gt_component.cpp:18:10: fatal error: tf2_geometry_msgs/tf2_geometry_msgs.hpp: No such file or directory
   18 | #include <tf2_geometry_msgs/tf2_geometry_msgs.hpp>
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/gt_component.dir/build.make:63: CMakeFiles/gt_component.dir/src/mocap_robot_gt/gt_component.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:84: CMakeFiles/gt_component.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:141: all] Error 2
---
Failed   <<< mocap_robot_gt [3.89s, exited with code 2]
Aborted  <<< mocap_marker_viz [6.13s]
Aborted  <<< mocap_control [8.63s]

Summary: 5 packages finished [13.4s]
  1 package failed: mocap_robot_gt
  2 packages aborted: mocap_control mocap_marker_viz
  1 package had stderr output: mocap_robot_gt
  2 packages not processed
parallels@ubuntu-linux-20-04-desktop:~/ws$ colcon build
Starting >>> mocap_msgs
Starting >>> mocap_control_msgs
Starting >>> mocap_marker_viz_srvs
Starting >>> mocap_robot_gt_msgs
Finished <<< mocap_robot_gt_msgs [0.47s]
Finished <<< mocap_marker_viz_srvs [0.51s]
Finished <<< mocap_control_msgs [0.54s]
Starting >>> mocap_control
Finished <<< mocap_msgs [0.60s]
Starting >>> mocap_marker_publisher
Starting >>> mocap_marker_viz
Starting >>> mocap_robot_gt
Finished <<< mocap_control [0.22s]
Starting >>> mocap_optitrack_driver
Starting >>> rqt_mocap_control
Finished <<< mocap_marker_publisher [0.20s]
Finished <<< mocap_marker_viz [0.24s]
--- stderr: mocap_robot_gt
/home/parallels/ws/src/mocap/mocap_robot_gt/mocap_robot_gt/src/mocap_robot_gt/gt_component.cpp:18:10: fatal error: tf2_geometry_msgs/tf2_geometry_msgs.hpp: No such file or directory
   18 | #include <tf2_geometry_msgs/tf2_geometry_msgs.hpp>
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/gt_component.dir/build.make:63: CMakeFiles/gt_component.dir/src/mocap_robot_gt/gt_component.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:84: CMakeFiles/gt_component.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:141: all] Error 2
---
Failed   <<< mocap_robot_gt [1.32s, exited with code 2]
Aborted  <<< rqt_mocap_control [1.45s]
Aborted  <<< mocap_optitrack_driver [9.11s]

Summary: 7 packages finished [10.0s]
  1 package failed: mocap_robot_gt
  2 packages aborted: mocap_optitrack_driver rqt_mocap_control
  1 package had stderr output: mocap_robot_gt
parallels@ubuntu-linux-20-04-desktop:~/ws$

Have you tried looking in some of the other repos on this page?

by https://github.com/neobotix/neo_localization2/issues/1#issuecomment-1078695979 change
#include <tf2_geometry_msgs/tf2_geometry_msgs.hpp>

to
#include <tf2_geometry_msgs/tf2_geometry_msgs.h>

but have new problem:

@ripdk12 I can't find the way to solve  the new problem

Hi!! It sounds like the NatNet library is not for your system. Maybe something related to 64/32 bits, not intel, ... you should probably manually replace it with the one appropriate for your system.
What are your system characteristics?

@fmrico m1 mac

Ok. That explains the problem. Look for the NatNet library for your architecture.
Good luck!!!

natnet sdk does not exist for mac. There are only 3 options windows, ubuntu and fedora.Check here
Plus I believe this project more focused on linux based system rather than windows or mac for now. I suggest to use VM with bridge adapter to the network card that you use to connect to the optitrack pc.


{dataprotection} HTML tags are rendering as empty parameter values in reference

Describe the bug
Problem to solve:
HTML tags in source code are causing build warnings in MicrosoftDocs/azure-docs-cli. More importantly, customer-facing reference docs are not instantiating properly -- parameter values formatted with `<>` are missing. Here's an example:

Requested solution:
These values should be escaped with a backtick. Here's an example from az webpubsub.

Published reference guidelines
Guidelines for Parameters used in examples
Related GitHub issues:
This is the same issue as these GitHub issues.
List of HTML tag instances that need update:

File name
Build error

latest/docs-ref-autogen/dataprotection/backup-policy.yml
HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/dataprotection/backup-policy.yml
HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/dataprotection/backup-vault.yml
HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/dataprotection/backup-vault.yml
HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/dataprotection/resource-guard.yml
HTML tag 'indexToRemove' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

latest/docs-ref-autogen/dataprotection/resource-guard.yml
HTML tag 'value' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

Related command
az dataprotection
Errors
n/a
Issue script & Debug output
n/a
Expected behavior
n/a
Environment Summary
Azure CLI 2.62.0
Additional context
No response

Thank you for opening this issue, we will look into it.


UMB item not appearing in bank

🐛 Bug Report
Write a description of the bug here, give all the information you can about what it is, how it happened.
I opened a UMB, got

a bloody mourner shirt, it is not in my bank though.

resolved


In the Explorer filetree, near the top, please include a filename filter box

In the Explorer UI, when looking at a filetree, near the top, please include a filename filter box. In a way, it'd be sort of a search box but limited in scope only to filenames (which are likely cached in memory anyway), so it should be ultra-snappy.

Are you aware that you can already search / filter the Explorer tree by typing characters when focused on it?

I think it's duplicate of #70646

I see, I wasn't aware. I agree this is more or less a duplicate of #70646.


Fixed "isClonedFrom" bug

Removed a duplicate property "isClonedFrom".
This bugfix may be merged before or after creating a branch for 2.0.

the pull request should be reissued for the dev branch. Therefore I delete the branch.


Add a basic installation description

What the title says
conda install tk

Basic description has been provided. Closing but we will need to keep this in mind later.


failed constructing descriptor for chaincodes

Hello all,
Versions

Peers / orderers: 2.5.9
Fabric CA: 1.5.12

I have the following hyperledger fabric setup:

2 Orgs, 1 peer each
4 Orderer nodes in etcraft fashion
2 NodeJS clietns for Org 1 with load balancer in front of them
7 Java chaincodes installed using chaincode as a service deployment fashion

I can use the client using APIs that I implemented to submit transaction and evaluate transaction on all the chaincodes.
I can submit transactions for all chaincodes except for chaincode with the following name "DigitalRegistryContracts"
I get this error from the client when I try to call any API that uses the "DigitalRegistryContracts" contract to communicate with the chaincode
{
"error": "DiscoveryService: DigitalRegistryContracts error: failed constructing descriptor for chaincodes:{name:"DigitalRegistryContracts"}",
"stack": "Error: DiscoveryService: DigitalRegistryContracts error: failed constructing descriptor for chaincodes:{name:"DigitalRegistryContracts"}\n at DiscoveryResultsProcessor.parseDiscoveryResults (/usr/src/app/node_modules/fabric-common/lib/DiscoveryResultsProcessor.js:31:11)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async DiscoveryService.send (/usr/src/app/node_modules/fabric-common/lib/DiscoveryService.js:341:19)\n at async ContractImpl.newDiscoveryService (/usr/src/app/node_modules/fabric-network/lib/contract.js:281:9)\n at async ContractImpl.getDiscoveryHandler (/usr/src/app/node_modules/fabric-network/lib/contract.js:258:25)\n at async Transaction.submit (/usr/src/app/node_modules/fabric-network/lib/transaction.js:236:43)\n at async /usr/src/app/app.js:425:18"
}
Can anyone help me please.
Thanks,

I think that this client-side error can occur if an incorrect discovery interest is configured with the legacy Node SDK. See the tutorial on using the discovery service for details. I don't know if this is the cause in your case.
While it should work with Fabric 2.5, the legacy Node SDK is no longer supported. You really should be using the Fabric Gateway client API instead. In most cases the newer client API automatically handles endorsement using collections and chaincode-to-chaincode calls correctly.

Hi bestbeforetoday,
Thank you for your response, I have applied the changes you suggested and used the Fabric Gateway client API. But when I started the client I got the below issue from the client docker container.
Logs:
******** FAILED to run the application: EndorseError: 10 ABORTED: failed to endorse transaction, see attached details for more info
As you can see no attached details to the logs.
Note that my blockchain network is running using docker swarm.
Thanks,

Have a look at the asset-transfer-basic/application-gateway-go sample in the fabric-samples repository for an example of accessing the associated error details. The (Gateway) peer logs should also contain information on the error.

Hi @bestbeforetoday
I fixed the issue above but now I still get an error when trying to communicate with the "DigitalRegistryContracts" chaincode.
{
"error": "9 FAILED_PRECONDITION: no combination of peers can be derived which satisfy the endorsement policy: No metadata was found for chaincode DigitalRegistryContracts in channel contractschannel",
"stack": "EndorseError: 9 FAILED_PRECONDITION: no combination of peers can be derived which satisfy the endorsement policy: No metadata was found for chaincode DigitalRegistryContracts in channel contractschannel\n at /usr/src/app/node_modules/@hyperledger/fabric-gateway/dist/client.js:37:253\n at Object.callback (/usr/src/app/node_modules/@hyperledger/fabric-gateway/dist/client.js:102:20)\n at Object.onReceiveStatus (/usr/src/app/node_modules/@grpc/grpc-js/build/src/client.js:193:36)\n at Object.onReceiveStatus (/usr/src/app/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:360:141)\n at Object.onReceiveStatus (/usr/src/app/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:323:181)\n at /usr/src/app/node_modules/@grpc/grpc-js/build/src/resolving-call.js:129:78\n at process.processTicksAndRejections (node:internal/process/task_queues:85:11)"
}
Thanks,

This message typically occurs when the requested chaincode is not successfully committed and running on the channel.


Adding my personal file - Drumminherbie

This is my bio page.

Edited the README

Looking at your code.

3d printing for the win!

How do you feel about U2 in Vegas without Larry Mullen Jr?

I'm enjoy their music, but not a huge follower of them. But hey, can't drum forever unfortunately....
Good for this guy taking a break for taking care of his health. Hopefully he can get back to it.


Realtime Log or Status?

I'm using the auto disc ripper feature however noticed this disabled the GUI from showing me the status. The only other method I know of is to manually refresh the log in my OMV GUI or wait for the disc to magically eject.
Is there another way to view the status?

Currently the container's log is the only way.  The automatic disc ripper is using the CLI version of MakeMKV and custom script to automatically rip the discs.  The GUI version doesn't have any feature that allows to perform this.
However, maybe It could be useful to show a pop-up window in the GUI while the automatic disc ripper is working.  This window could show the progress while informing the user to not attempt to rip the disc through the GUI at the same time...

@goofmyan23 see https://github.com/jlesage/docker-makemkv/issues/67

With version 1.19.0, the progress of a disc ripped by the automatic disc ripper can be seen in the UI.

With version 1.19.0, the progress of a disc ripped by the automatic disc ripper can be seen in the UI.


Fix typos in README

Thanks for your awesome package.

Thanks for liking it!
Not sure I understand the intended change. I think I like having the decoder below the type, to make it as similar as possible to the corresponding Typescript type declaration.

Intended change should be more clear now. I've reverted the order.

Ah now I see! Brilliant, thanks!


Rubocop support

I added some rubocop support to have a cleaner and better readable code.
But there is a bug in the customization_plugin function so rubocop still found two offenses.
lib/chef/knife/vsphere_vm_clone.rb:465:23: W: Lint/AssignmentInCondition: Assignment in condition - you probably meant to use ==.
      if cplugin_path = get_config(:customization_plugin)
                      ^
lib/chef/knife/vsphere_vm_clone.rb:474:27: W: Lint/AssignmentInCondition: Assignment in condition - you probably meant to use ==.
          if cplugin_data = get_config(:customization_plugin_data)
                          ^

Wow, thanks for doing this. I ran rubocop on this earlier and was overwhelmed.
Assignment in conditions aren't necessarily bugs, but I'd call it a smell. Let's leave that in there for now and we can rewrite them to be more clear in a separate PR.
And with this we can get it into Travis :heart:
Will review today and merge.

I should have expanded on the assignment in condition thing.
if foo = bar
  baz
end

is the same as
foo = bar
if foo
  baz
end

First off, wow. Thanks for doing this. Already the code looks nicer. A few small queries inline.
Is there anyone that is willing to give this a second review?

I updated my branch and add some more stuff.

I'm :+1: on this. Anyone else want to take a look before this gets merged?

Merged! With my sincere gratitude.

It was my pleasure. :blush:


Add ritual help messages

Print more detailed help messages in chat if the player is only missing a few blocks for a pentacle or a few items for a ritual. I did not test this too extensively so it might be a good idea if you do some sanity testing to make sure that I have not broken anything 🙂

I'll have to try and expedite this one. That'll be a super welcome feature, thank you so much!


Help requested

Hi - thank you for posting this (and for answering some of my questions a while ago on the ogx360 project).
I've made the modifications to TinyUSB as suggested. I'm not sure where the xinput_host.c and xinput_host.h need to be included. Do they need to be placed in the TinyUSB tree somewhere and included in one or more of the files there or should they be included in my project.
Thanks.

the repo has all been updated for the latest upsteam tinyUSB.
Hopefully these problems should be alleviated


regex Windows panic MustCompile/MatchString

What version of Go are you using (go version)?

go version go1.11.2 windows/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\sys\AppData\Local\go-build
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\Sys\User\Go
set GOPROXY=
set GORACE=
set GOROOT=C:\Go
set GOTMPDIR=
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=C:\Users\sys\AppData\Local\Temp\2\go-build287238718=/tmp/go-build -gno-record-gcc-switches

What did you do?
package main

import "fmt"
import "regexp"

var IsLetter = regexp.MustCompile(`^[a-zA-Z]+$`).MatchString

func main() {

    b := IsLetter("abc")
    fmt.Println(b)
}

What did you expect to see?
Works on playground:
true

What did you see instead?
On Windows:
panic: runtime error: slice bounds out of range

goroutine 1 [running]:
main.main()
      .../main.go:7 +0xbc

In the file you posted, line 7 is an empty line. The program also seems to run fine on Linux.

I must be going crazy.
I'm pretty sure I double-checked before issuing bug report.
But now I copied and pasted code and it ran successfully.
A possible explanation for original panic:
The original test code was pasted from the web and modified
It's possible there were some unruly characters lingering in the file.
This might explain the "empty line 7" which @mvdan spotted.
Anyway, all is good now.
Sincere apologies for inconveniencing you and thanks for assistance


Custom filter: undefined custom function in filters configuration property

I'm triying to filter by date field. For that, I'm using the custom filters functionality:
In the template:
<input type="date" class="form-control col-5" v-model="filters.birthday.value.min"
                                           :max="filters.birthday.value.max"/>
                                    -
                                    <input type="date" class="form-control col-5" v-model="filters.birthday.value.max"
                                           :min="filters.birthday.value.min">

<v-table :data="data" :filters="filters" ... >
In the filters object:
birthday: {
                   value: { min: '', max: '' },
                    custom: this.birthdayFilter
                 }

In the created hook:
birthdayFilter (filterValue, row) {
                return row.birthday >= filterValue.min && row.birthday <= filterValue.max
            }

When the page is rendered, it throws errors:

Error in data(): "TypeError: Cannot read property 'birthdayFilter' of undefined"
Property or method "filters" is not defined on the instance but referenced during render. Make sure that this property is reactive, either in the data option, or for class-based components, by initializing the property

The basic filters work fine in the page, custom filters don't. I have followed the official documentation (https://tochoromero.github.io/vuejs-smart-table/filtering/#custom-filters) and my Vue version is 2.6.12
Thanks.

did you get this working?


Eliminate -Wconversion-null warnings

Fix two warnings of the form:
  cmod_csp_common_eqns.h:16:113: warning: passing NULL to non-pointer argument 1 of
  ‘util::matrix_t<T>::matrix_t(size_t) [with T = double; size_t = long unsigned int]’ [-Wconversion-null]

C++ guarantees that a reference always refers to a valid object.

It looks like this pull request has a merge conflict. Can you please merge develop into this branch and update the pull request?

Thanks Ben.


Remove nginx conf files for PSC DEV

Note: with this migration and conf changes, the docker/ingest-api/nginx.conf handles the forwarding.
Will handle this PR once the TEST and PROD migrate to the NEW VM and Puppet service in place to handle the deployment.
TEST/PROD:

TEST will use the latest docker image tag
PROD will use an explicit version tag.
Sometimes the code changes will require corresponding app.cfg updates (mainly adding new items), I'll commit to the Gitlab repo
For PROD, you will have to add a file, DEPLOY_INGEST_API, to the /opt/repository/{hostname}-{env} directory so that Puppet knows to actually deploy things.
Puppet service will pull the docker image and the Gitlab changes, and should redeploy the containers. The new config will be placed in the appropriate places, by Puppet, prior to the redeployment.

Will go hand in hand when merge https://github.com/hubmapconsortium/gateway/pull/252

The gateway PR had been merged first.

Migrated to the new PSC TEST VM today. Will be removing the test nginx conf files and the docker-compose test deployment yaml file as well.

Will be merging this PR and test the main branch on vm002 and vm004 (sudo access pending)


Support of multiple file upload. As requested in #595

As requested in #595:

Allowing multiple file upload by default. Using the original 'file' type

saving original filename in json in the DB for better outlook of the download link

removing files once the entity is deleted

@lampdev, Just an FYI for future pull requests.  You can safely ignore StyleCI and CodeClimate failures unless we explicitly request that you change them.

@lampdev has this been completed yet. I'm trying to test out a multiple file upload, but it's only letting me upload one image. When I try and view the data in the database for a file upload it just gives me an empty array:
[]

Let me know if there's anything I can do to help with testing this further before confirming the Merge Request :)
Thanks.

@lampdev actually sorry, I didn't switch to your multiple-files branch. But after doing so, I went to test out a multiple file upload. I switched the pages image to be mutiple-images and after doing so I tried creating a new page with 2 images and got the following message:

Any thoughts? Let me know 👍
Thanks.

@tnylea Hi and thanks for testing this! I haven't done anything with multiple_images field type, only modified the file type

@lampdev aha, ok. Thanks for clarifying.
I'll be testing again tomorrow. BTW, just merged in the coords functionality and that will be available when we release 1.0 👍


Fix4K: Fix bad positioning when changing active wheel

This pull should better fit your workflow, I hope.

I'll add you as an author now, so you can participate directly on the project.  Just don't touch master, add any version tags, or commit the FLAs at all.  The rest I can fix if anything goes wrong :)


Add kubectl log as an alias for kubectl logs

What would you like to be added?
It will be great if kubectl log could be added as an alias for kubectl logs.
Why is this needed?

Most kubectl commands work as singular and plural for the resource name. It always confuses me which is the correct one for logs. I understand logs is the verb part.

I also use git which has commands like git log --oneline. I can never never when to use log and when to use logs.

you can also get the opinion on kubernetes.slack.com slack , on the channel #sig-cli

I think this will be helpful as well. will recommend to join sig meeting today if you want to discuss this . please go through the community page for more information.

this can easily be managed via aliases and I doubt about the usefulness of this feature if we add it in kubectl. I'd prefer closing this issue.

/close


Package changes for Adoptium Temurin binaries (add temurinjre8) 🧪

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Related to #28737
Microsoft Reviewers: Open in CodeFlow

https://github.com/microsoft/winget-pkgs/pull/28744#issuecomment-927313703


sbt scala-cli cs installed by coursier does not work on windows

When I try to run the above command, it says
This version of C:\Users\HarryXi\AppData\Local\Coursier\data\bin\.sbt.aux.exe is not compatible with the version of Windows you are running. Please check your computer's system information and then contact the software publisher.

Might be that the version of windows is too old? What version are you using?

Might be that the version of windows is too old? What version are you using?

I'm using Windows 11 23H2 (22613.3296)
I apologize for forgetting to provide this information in the first place

According to https://answers.microsoft.com/en-us/windows/forum/all/this-verison-of-this-file-is-not-compatible-with/0c6a4c8e-1416-47a5-b6b4-6d10a82942da it might mean that you have 32bit system and the apps are create for 64 or the other way around. I think the native apps are released for 64 bit systems

According to https://answers.microsoft.com/en-us/windows/forum/all/this-verison-of-this-file-is-not-compatible-with/0c6a4c8e-1416-47a5-b6b4-6d10a82942da it might mean that you have 32bit system and the apps are create for 64 or the other way around. I think the native apps are released for 64 bit systems

You should know that win11 doesn't have a 32 bit version

Hmm... Ok then a pity the error doesn't give us more information. You could try installing Scala CLI via winget, we can confirm whether the error is coursier specific.
https://scala-cli.virtuslab.org/install <- there should be some minimal instruction there

It's working fine.
In fact the binary version cs downloaded from coursier's release and the sbt binary downloaded from the official sbt repository's release both work fine!
The problem only occurs with the version installed by coursier.

Not sure them :thinking: does anyone else have this problem? If it's more widespread we might need to take a closer look soon.

This version of C:\Users\HarryXi\AppData\Local\Coursier\data\bin.sbt.aux.exe ...

So when Coursier says it's installing sbt, is it still installing some shim of sbt instead of the genuine sbt?

So when Coursier says it's installing sbt, is it still installing some shim of sbt instead of the genuine sbt?

Honestly, I didn't understand your statement very well.
I was just installing scala and its tools using a binary version of coursier on a computer that didn't have scala (and any of its associated tools) installed.
During this process, I didn't notice any different log output when installing sbt than when installing other tools.

Yea, sorry about that. That was more of an observation (I'm a maintainer of sbt) that Coursier does that. bin.sbt.aux.exe isn't something that we (sbt project) ship.

Yea, sorry about that. That was more of an observation (I'm a maintainer of sbt) that Coursier does that. bin.sbt.aux.exe isn't something that we (sbt project) ship.

I did some investigation on a fresh coursier sbt install on Windows and the situation has apparently improved. It now simply installs a thin sbt.bat file that redirects to genuine sbt.bat file.
PS D:\Repos> where.exe sbt
C:\Users\Jerry Tan\AppData\Local\Coursier\data\bin\sbt.bat

Content of C:\Users\Jerry Tan\AppData\Local\Coursier\data\bin\sbt.bat
@echo off

@REM set %HOME% to equivalent of $HOME
if "%HOME%" == "" (set HOME=%HOMEDRIVE%%HOMEPATH%)

set ERROR_CODE=0

@REM set local scope for the variables with windows NT shell
if "%OS%"=="Windows_NT" @setlocal

@REM Decide how to startup depending on the version of windows

@REM -- Win98ME
if NOT "%OS%"=="Windows_NT" goto Win9xArg

@REM -- 4NT shell
if "%@eval[2+2]" == "4" goto 4NTArgs

@REM -- Regular WinNT shell
set CMD_LINE_ARGS=%*
goto endInit

@REM The 4NT Shell from jp software
:4NTArgs
set CMD_LINE_ARGS=%$
goto endInit

:Win9xArg
@REM Slurp the command line arguments.  This loop allows for an unlimited number
@REM of arguments (up to the command line limit, anyway).
set CMD_LINE_ARGS=
:Win9xApp
if %1a==a goto endInit
set CMD_LINE_ARGS=%CMD_LINE_ARGS% %1
shift
goto Win9xApp

@REM Reaching here means variables are defined and arguments have been captured
:endInit

@REM Start program
:runm2
SET CMDLINE="C:\Users\Jerry Tan\AppData\Local\Coursier\cache\arc\https\github.com\sbt\sbt\releases\download\v1.10.4\sbt-1.10.4.zip\sbt\bin\sbt.bat" %CMD_LINE_ARGS%
%CMDLINE%
if ERRORLEVEL 1 goto error
goto end

:error
if "%OS%"=="Windows_NT" @endlocal
set ERROR_CODE=1

:end
@REM set local scope for the variables with windows NT shell
if "%OS%"=="Windows_NT" goto endNT

@REM For old DOS remove the set variables from ENV - we assume they were not set
@REM before we started - at least we don't leave any baggage around
set CMD_LINE_ARGS=
set CMDLINE=
goto postExec

:endNT
@endlocal

:postExec
exit /B %ERROR_CODE%

Never mind coursier doesn't always just install a thin shim...
https://github.com/coursier/coursier/blob/24ae7456d45c3597613f35076ed967c287597bb2/modules/install/src/main/scala/coursier/install/InstallDir.scala#L251-L259
Apparently it looks up for "prebuilt" exe launchers somewhere, and then fallback to thin bat shim...

Is there any way to circumvent this problem? It still ship cs.aux and other shim files.

Use scoop on Windows? - https://www.scala-sbt.org/download

If prebuilt sbt binary is broken, can we just disable prebuilt lookup when installing sbt (or if prebuilt are hosted in some remote server, delete these broken prebuilt).
Like on my machine the installation of sbt via coursier was fine. It just worked.

Use scoop on Windows? - https://www.scala-sbt.org/download

I use coursier installed by scoop, and coursier setup will prompt:

Checking if the standard Scala applications are installed
Found ammonite
Found cs
Found coursier
No prebuilt binary available at https://github.com/scala/scala3/releases/download/3.6.1/scala3-3.6.1-x86_64-pc-win32.zip, https://github.com/scala/scala3/releases/download/3.6.1/scala3-3.6.1-x86_64-pc-win32.zip...

Use scoop on Windows? - https://www.scala-sbt.org/download

I use coursier installed by scoop( actually the jar version, cs still can't use ), and coursier setup will prompt:

Checking if the standard Scala applications are installed

Found ammonite

Found cs

Found coursier

No prebuilt binary available at https://github.com/scala/scala3/releases/download/3.6.1/scala3-3.6.1-x86_64-pc-win32.zip, https://github.com/scala/scala3/releases/download/3.6.1/scala3-3.6.1-x86_64-pc-win32.zip...

I think Eugene is probably referring to using scoop to install sbt directly, instead of using scoop to install coursier.

I think Eugene is probably referring to using scoop to install sbt directly, rather then using scoop to install coursier.

But I can't install the whole toolchain, not only sbt.

I think Eugene is probably referring to using scoop to install sbt directly, rather then using scoop to install coursier.

But I can't install the whole toolchain, not only sbt. Are there other ways?

I think Eugene is probably referring to using scoop to install sbt directly, rather then using scoop to install coursier.

But I can't install the whole toolchain, not only sbt. Are there other ways?

How about scoop install scala-cli (and vice versa to install other parts of the toolchain).
 I also use Windows (I have a Windows 11 ARM virtual machine on my MacBook and a physical x64 Windows 10 Machine), and on neither of these can I reproduce the issue. If I can reproduce it somehow, I might be able to look into it further.

How about scoop install scala-cli (and vice versa to install other parts of the toolchain).
 I also use Windows (I have a Windows 11 ARM virtual machine on my MacBook and a physical x64 Windows 10 Machine), and on neither of these can I reproduce the issue. If I can reproduce it somehow, I might be able to look into it further.

I currently use intellij now to circumvent this. : (

Now sbt 1.10.7 is released, I just tried cs update sbt on Windows. Still cannot reproduce the issue...

Now sbt 1.10.7 is released, I just tried cs update sbt on Windows. Still cannot reproduce the issue...

I'm just stuck at cs installation. I try to use coursier setup but it will panic:

Checking if the standard Scala applications are installed
Found ammonite
Found cs
Found coursier
No prebuilt binary available at https://github.com/scala/scala3/releases/download/3.6.2/scala3-3.6.2-x86_64-pc-win32.zip...

Now sbt 1.10.7 is released, I just tried cs update sbt on Windows. Still cannot reproduce the issue...

I'm just stuck at cs installation. I try to use coursier setup but it will panic:

Checking if the standard Scala applications are installed
Found ammonite
Found cs
Found coursier
No prebuilt binary available at https://github.com/scala/scala3/releases/download/3.6.2/scala3-3.6.2-x86_64-pc-win32.zip...

So, currently, I can't even install sbt during the process.

I wonder if there's a flag that enables "prebuilt binary" mode. The mode is broken and should not be turned on.

https://github.com/coursier/coursier/blob/5ea4aa43a58e7aaa2fec4da86d592ffb94c30fcb/modules/install/src/main/scala/coursier/install/InstallDir.scala#L323-L328
Exception is thrown right there.

https://github.com/coursier/coursier/blob/5ea4aa43a58e7aaa2fec4da86d592ffb94c30fcb/modules/install/src/main/scala/coursier/install/InstallDir.scala#L323-L328
Exception is thrown right there.

I hope that will fix it, at least I can use coursier.


Publish updates to NPM?

npm's latest copy of angular-bootstrap is 0.12.2. It would be helpful if versions can be published to npm when tagged here.
Thanks

https://github.com/angular-ui/bootstrap#install-with-npm

The linked documentation doesn't address my request.


Implement Dataset from JSON Lines

Implement Dataset.from_jsonl.

Thanks @lhoestq. I was trying to follow @thomwolf suggestion about integrating that script but as from_json method...

Note that I don't think this is necessary a breaking change, we can still keep the old scripts around

Do you think there is a better way of doing it?
I was trying to implement more or less the same logic as in the script, but I confess I assumed the target was in-memory only...

Basically, I was trying to reimplement Json(datasets.ArrowBasedBuilder)._generate_tables, and no writing to arrow file (I assumed only in-memory usage). I started with the first "else" clause...

merging master into this branch should fix the CI issue :)

Good job ! I think we can merge after the last changes regarding the error message and the docstring above :)

@lhoestq Done! And I have also added some tests for the field parameter.

Let me add some more tests for dict of lists JSON file, please.

@lhoestq done! ;)

We can merge. Additional work will be done in another PR. ;)


[Feature] BoundingFrustum Support

Hello, I saw you Model (Mesh) Type does not support BoundingFrustum like the Default Mesh Types in MonoGame, Can you pls support them?

Added SkinnedMesh.BoundingSphere in 1.0.3

thxx!


Keyboard shortcut for "Import Icon from Owning Library..." action

As a LabVIEW user, I would appreciate being able to more quickly execute the "Import Icon from Owning Library..." action.

I would be happy with any key combination chosen for this action.
Side-note: It would be great if, when moving a VI or CTL from one owner to another, the LabVIEW IDE would be able to automatically update the "banner" of the VI with that of the new owning lvclass or lvlib. This feature would remove 90% of the instances where I need to use the "Import Icon from Owning Library..." action. But I know that this is not the place to ask for this feature.
Thanks!

If going the dialog on load, also enable a checkbox to "Always Apply".

For the purpose of closing this PR, i will develop the keyboard shortcut on the icon editor and will open a new issue that explores the route of automatically applies the banner from the parent library as described on this issue's comments

Thanks for looking into this. It's much appreciated.
Kind regards,
Petru Tarabuta, Robusto Systems Ltd, UK


sap.m.ListBase: selectAll-behavior when growing is activated

OpenUI5 version: 1.52
Browser/version (+device/version): Google Chrome 64.0.3282.186, Windows 10
URL (minimal example if possible):
https://plnkr.co/dGgvUz4iPxDzZgqHkug4
Steps to reproduce the problem:

Open the plunker
Click on 'SelectAll'-Checkbox in the header
Scroll until growingThreshold is reached

What is the expected result?
the new items should be selected when growing is finished and the 'SelectAll'-Checkbox is checked
What happens instead?

the new items are not selected
you have to select the Checkbox again

Any other information? (attach screenshot if possible)

Hello @sassito ,
Thank you for sharing this finding. I've created an internal incident<PHONE_NUMBER>. The status of the issue will be updated here in GitHub.
Regards,
Gery

hi @sassito this has been discussed several times but the current behavior is actually the one that UX would like to have.  If you want to change it then I think you can listen updateFinished event(reason parameter "Growing") and call List#selectAll again.

HI @aborjinik,
1:
But first you have to check if the 'selectAll'-Checkbox is selected.
In the updateFinished event it is already unselected.
Therefore, you have to listen to the updateStarted event (here it is still selected) and save the selected-property.
2:
If a user doesn´t know this behaviour and selects the Checkbox without loading all Items, only the loaded items will be selected.
→ But the user doesn't notice anything.
Not the best user experience!
In my opinion, the selectAll-Checkbox should be disabled when growing is active.

@sassito as I said before this is exactly what UX wants, only the loaded items should be selected when select all is checked or ctrl + A is pressed.
I would suggest to listen selectionChange event and use selectAll parameter instead of updateStarted event.


Refactor lookupNetwork unit tests

Description
The network controller lookupNetwork unit tests have been refactored to be more similar to the extension unit tests.
Changes
None
References
This relates to #1200
Checklist

[x] I've updated the test suite for new or updated code as appropriate
[x] I've updated documentation for new or updated code as appropriate (note: this will usually be JSDoc)
[x] I've highlighted breaking changes using the "BREAKING" category above as appropriate

This was originally part of #1264. I broke this out because the number of changes was too large.


Fix standalone tests module.

This PR makes the standalone tests folder an executable module by adding the missing __init__.py.
Now one can copy tests where the arrayfire module was built and run python -m tests to execute the testsuite. This is particularly useful for CI. The remaining fixes makes the standalone execution compatible with Python 3 (only absolute imports are allowed).

@ghisvail that was creating a problem in our ci. I moved the tests module into the arrayfire module.
You can now run tests using python -m arrayfire.tests after installing arrayfire. This guarantees that the tests being run correspond to the installed version of arrayfire. No need to copy the test directory.

I moved the tests module into the arrayfire module.

Works too. That was potentially more invasive a change that's why I did not do it this way.

No need to copy the test directory.

Even better from my perspective.
Are you planning a release soon which would incorporate these changes?

Hopefully sometime next week.


MAINT: Replace xrange with range

Reference issue

What does this implement/fix?
Python 2 code cleanup.
Additional information

@sethtroisi
Please specify the reference issue and link it to this PR.

Looks good, not sure why you closed this.
All these changes are in cython code, and I suspect cython compiles xrange and range in the same way. Regardless, the cleanup is good.

One can specify whether cyrhon treats it as python 2 or 3 by using a language directive.

I closed this till I have time to open a sufficient "Python2 Cleanup" issue

https://github.com/cython/cython/wiki/FAQ#what-python-versions-does-cython-support


Create reuchlin-gymnasium.txt

Institution/School Name
Reuchlin-Gymnasium Pforzheim
Instiution/School Website
reuchlin-gymnasium.de
Email Users
Please place an x between the square brackets if yes

[x] Students
[x] Academic/Teaching Staff
[ ] Other/Support Staff
[ ] Alumni

Education Levels
Please place an x between the square brackets if yes

[ ] Post-graduate research
[ ] Graduate School
[ ] College (University) or Undergraduate School or equivalent
[ ] Community College or equivalent
[x] High School or equivalent
[ ] Elementary School or equivalent

@InformatikBildschirm Pull request merged. Thank you!


target: zephyr: Fix build when USE_CCACHE=1

Currently if USE_CCACHE=1 is set to one than the Zephyr build system
will include ccache in the CC variable. ccache cannot be passed to
cmake using EXTERNAL_CMAKE_C_COMPILER (even if we fix the quoting)
because it fails a PATH reachability test within cmake. For that
reasons we solve the build failure simply by removing ccahce from CC
before we pass it into cmake.
The problem described about is a regression due to commit ac1bf19c90d6
("build: Adopt outputexports") and the fix contained in this patch
restores the original behaviour (zephyr exploits ccache, jerryscript
library build does not).
JerryScript-DCO-1.0-Signed-off-by: Daniel Thompson<EMAIL_ADDRESS>

LGTM

LGTM


Very cool ... should there be any Javadoc?

My preference is to actually NOT have Javadoc in the generated class.
That sounds a bit weird I know, my thinking is that the builder pattern is SOOO predictable that the Javadoc does not actually add anything or help the person reading the code.  In the "less is more" thinking it is actually better to not have the Javadoc at all.

You know, this, I know this, but the maven javadoc plugin doesn't know this.


Add is_empty SCEL expression for string/array fields

Hello,
This adds a new SCEL expression to check if a string or an array is empty.
You could already do that with the length or equals operators, but I think having a dedicated operator for this expression will improve readability. (I have several use cases with complex expressions so this would be quite useful for us)
Best regards,
Lucas

Hi @lucas-dclrcq, thank you very much for your contribution, could you please remove the unused imports from the IsEmpty class. Also, could you replace the wildcard import  in the ExpressionFunctionExecutorsclass.
The build has failed with the following checkstyle errors :
Error:  src/main/java/io/streamthoughts/kafka/connect/filepulse/expression/function/strings/IsEmpty.java:[23,8] (imports) UnusedImports: Unused import - io.streamthoughts.kafka.connect.filepulse.expression.Expression.
Error:  src/main/java/io/streamthoughts/kafka/connect/filepulse/expression/function/strings/IsEmpty.java:[25,8] (imports) UnusedImports: Unused import - io.streamthoughts.kafka.connect.filepulse.expression.ValueExpression.
Error:  src/main/java/io/streamthoughts/kafka/connect/filepulse/expression/function/strings/IsEmpty.java:[26] (imports) AvoidStarImport: Using the '.*' form of import should be avoided - io.streamthoughts.kafka.connect.filepulse.expression.function.*.
Error:  src/main/java/io/streamthoughts/kafka/connect/filepulse/expression/function/strings/IsEmpty.java:[28,8] (imports) UnusedImports: Unused import - java.util.Objects.
Error:  src/main/java/io/streamthoughts/kafka/connect/filepulse/expression/function/strings/IsEmpty.java:[29,8] (imports) UnusedImports: Unused import - java.util.regex.Pattern.
Error:  src/main/java/io/streamthoughts/kafka/connect/filepulse/expression/function/ExpressionFunctionExecutors.java:[38] (imports) AvoidStarImport: Using the '.*' form of import should be avoided - io.streamthoughts.kafka.connect.filepulse.expression.function.strings.*.

Hi,
Yes I will do that !


bitmask-vpn: fix calyx build

This fixes: #347620
In the last upgrade of bitmask-vpn #344549 the upgrade of callPackage to qt6 for calyx-vpn was missed. This is the immediate cause of the build error reported in #347620.
Beyond this initial build error, there were further errors with calyx-vpn because a new make vendor step has been added to the build documentation for bitmask-vpn in the past few months. Riseup-vpn seems to work fine without running this step but calyx-vpn does not. The remaining changes to the default.nix here were required to complete the build when it includes make vendor.
Calyx-vpn now builds and runs, but still cannot actually complete a VPN connection because of certificate errors. It is unclear whether the underlying cause of this bug is from the calyx servers, the bitmask-vpn upstream, or with the nixpkgs build. Building calyx-vpn on a different linux system could determine whether or not it is a nixpkgs build problem. I will leave it to someone else to open an issue about this if necessary.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] 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
[X] 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

[X] Fits CONTRIBUTING.md.

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

@RoGreat and @vigneshpai2003 I couldn't request you as reviewers, but if you're able to do a review you might be able to add yourselves.

@ju1m and @Aleksanaa I think if you redo your reviews of this PR then it will appear ready to merge.


Switch to fork with content length redirect

This will switch us to my fork of camo (at least until my PR is merged or we replace it, whichever comes first), which allows us to set a redirect to a custom image when the user's image size exceeds the content length limit.
This will allow us to show a real image w/ some information in the README instead of just having a broken image with 404 Not Found and no other information.
Also brings us up to the latest version, which doesn't really seem to have any functional changes and works fine in dev.

cc @dstufft, since it seems like you're not actually watching this repo.

e670ab3


GitHub actions: Create a proper release if a tag is pushed

When we push a tag, GitHub actions will now create a proper release from the tag

This worked wonders for the openxr plugin.
Ben I'm going to merge this but I would like to ask you to rewrite the part that puts the zip file together. I'll raise an issue for this.


[question ]Regarding the GPT-4 API

I saw in the README.md file that it mentions using the GPT-4 API, but I don't have access to the official OpenAI GPT-4 API. I'm wondering if I can use a third-party service that offers OpenAI GPT-4 API, like this website: https://docs.aiproxy.io/guide/quick-start. If it's possible, how should I set it up?

To get an OpenAI API key that has GPT-4 access follow these instructions: https://help.openai.com/en/articles/7102672-how-can-i-access-gpt-4
Quite a few people have been commenting on the Discord about their issues with getting working keys, so maybe hop on the Discord and search for "api key" to see if anyone else has the same issues.


Fix diagnostics in multi file projects

Description
Closes https://github.com/FuelLabs/sway/issues/5027
Now instead of caching the Diagnostics object, we cache a mapping of file path -> Diagnostics
When we publish diagnostics, we only publishing the diagnostics for the given URI, not for the entire project. I added a test where there are no diagnostics in the main.sw file, but a bunch of diagnostics in the other files in the project.
Checklist

[x] I have linked to any relevant issues.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have updated the documentation where relevant (API docs, the reference, and the Sway book).
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have added (or requested a maintainer to add) the necessary Breaking* or New Feature labels where relevant.
[ ] I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
[ ] I have requested a review from the relevant team or maintainers.

Just tested this locally, wow I can't believe how bad it was! We need to get this in the beta-4 release for sure! Thanks for spotting this error! So much nicer now.


RDKTV-14246: CEC enable/disable inconsistencies fix

Reason for change:1) Prevent Initiate ARC & system audio
on message process form audio device when TV CEC is disabled.
2) Increase timeout for critical arc messages so that TV
can retry sending in case of any cec message write failures
Test Procedure: Verify cec enable/disable
Risks: Low
Signed-off-by: Deekshit Devadas<EMAIL_ADDRESS>

Can one of the admins verify this patch?

@mhughesacn - Please help with the license/cla check. Is there any open issue with this check since multiple PRs are getting delayed on this check.

H Anand: CLA signature checking is done outside of rdkcentral.  It seems to be very slow today (and yesterday).  As the CLA is signed by you, I marked it as a success.


Automatic pause on scene change when generating the script

Current solution with asking the user to press 'q' when the scene changes is suboptimal.
Main source of pain during automatic funscripting is if you miss the scene change, then the tracking algorithm would detect some random position in a new scene, which would mess up the range of the previous points.
It would be great if the automatic tracking UI had a pause/unpause functionality and then on each detected scene change the user could either press 'q' and set up the range or press 'space' and continue the tracking on a false-positive scene change detection.

It might be easier to have automatic tracking pause when it hits an existing point. That way, you could "pre-cue" the scene changes by going through the video and dropping in points at the "correct" values.

Do you have a suggestion how i can automatically detect such a scene change? I have no idea how to automatically detect this without too much computational effort. You can of course apply a 3d pose estimation with deep learning but this would probably slow down the tracking 100-1000 times.
Currently there is one new function that allow to specify a area where you expect the tracking prediction and if the prediction is outside this specified area the tracking stops (see this commit) - This feature will be available in the next release.

I think the "define start and end points" feature should do the job nicely.

I meant "scene change" as in video codec context. If the current frame differs from the previous too much - there's a high chance that the tracked region is invalid now. I don't know what facilities OpenCV has for that, but it sure should have something. If the big chunk of the frame doesn't have any valid motion vectors, or simply too many pixels have changed - that should trigger a pause. Maybe some threshold values should be exposed in config.
An easy hack would be to pause when the tracked region has jumped suddenly (too big of a change from the previous frame, or position outside of the usual range - e.g. what was during the first 5 seconds of the processed video chunk). It's not an ideal solution, but it would remove the main issue, caused by the change - the misidentified region messing with the range selection at the end of tracking.

Some googling returned this: https://github.com/Breakthrough/PySceneDetect
So, it's possible to detect scene changes with openCV. Maybe it's feasible to use the same openCV API here to automatically detect pause locations.
Or, you could invoke this packet to find the pause locations.
Or implement a list of predetermined pause locations, which the users could generate themselves using e.g. the packet above.

Thanks for the link. I will have a look at the python module in the next days.

The Feature is now available in the new release v0.1.1. With default setting the application read the csv from PySceneDetect in the same directory where the video is located. If such a csv file not exist this feature get automatically disabled. You can also use an build in online scene change algorithm by change this config entry. The config files for MTFG with Install Option 1 are located in %appdata%/OFS_data/extensions/Funscript Generator Windows/funscript-editor/funscript_editor/config
It would be helpful if you could try out the implemented online methods and give feedback if they work reliably and detect few false positive scene changes. Then we could set one of the built-in methods as default value in a future release.

Thank you very much!


Bug: Discovery packet for each sensor is resent every 30 seconds

Describe the bug
My Homeassistant log is overwhelmed with MQTT discovery messages saying its getting discovery for already discovered component. This comes in every 30 seconds, for each HASS.Agent sensor I have configured.
2023-03-17 07:31:17.052 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor TIM-PC tim-pc_loggeduser, sending update
2023-03-17 07:31:47.428 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor TIM-PC tim-pc_loggeduser, sending update
2023-03-17 07:32:17.824 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor TIM-PC tim-pc_loggeduser, sending update

Looking in MQTT-Explorer, I confirm a new config packet comes every 30 seconds.
Why is this happening so often?
To Reproduce
Steps to reproduce the behavior:

Create a HASS.Agent sensor
???
Get MQTT spam

Expected behavior
I would only expect to see one config packet per sensor, at first connection, or when something significant changes that requires a new config packet.
Screenshots

Misc info (please complete the following information):

Windows build (ideally screenshot/info of winver.exe output):

Windows' UI language:
English
HASS.Agent version:
2022.14.0

Please check what's applicable (multiple answers possible):

[x] Installed via installer
[ ] Installed manually
[x] Problem occurs in HASS.Agent
[ ] Problem occurs in Satellite Service

Additional context
Add any other context about the problem here.
Logs
If possible, please provide the logs of HASS.Agent and - if applicable - the Satellite Service. You can find HASS.Agent's logs by going to the main window, then Configuration -> Logging -> open logs folder. The Satellite Service's logs are in the same window, but the Satellite Service tab -> open service logs folder. If you want, you can mail them to<EMAIL_ADDRESS>

I too am seeing this but mine is every 10 seconds, which is the frequency of the lastactive sensor updates.
2023-03-24 01:20:34.212 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor WINDOWS-11 WINDOWS-11_lastactive, sending update
2023-03-24 01:20:34.213 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor WINDOWS-11 WINDOWS-11_sessionstate, sending update
2023-03-24 01:20:34.214 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor WINDOWS-11 WINDOWS-11_monitorpowerstate, sending update
2023-03-24 01:20:35.432 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: button WINDOWS-11 WINDOWS-11_monitorsleep, sending update
2023-03-24 01:20:35.437 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: button WINDOWS-11 WINDOWS-11_monitorwake, sending update
2023-03-24 01:20:35.438 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: button WINDOWS-11 WINDOWS-11_restart, sending update
2023-03-24 01:21:04.705 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor WINDOWS-11 WINDOWS-11_lastactive, sending update
2023-03-24 01:21:04.708 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor WINDOWS-11 WINDOWS-11_sessionstate, sending update
2023-03-24 01:21:04.709 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor WINDOWS-11 WINDOWS-11_monitorpowerstate, sending update
2023-03-24 01:21:05.437 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: button WINDOWS-11 WINDOWS-11_monitorsleep, sending update
2023-03-24 01:21:05.442 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: button WINDOWS-11 WINDOWS-11_monitorwake, sending update
2023-03-24 01:21:05.446 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: button WINDOWS-11 WINDOWS-11_restart, sending update
2023-03-24 01:21:35.162 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor WINDOWS-11 WINDOWS-11_lastactive, sending update
2023-03-24 01:21:35.166 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor WINDOWS-11 WINDOWS-11_sessionstate, sending update
2023-03-24 01:21:35.169 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor WINDOWS-11 WINDOWS-11_monitorpowerstate, sending update
2023-03-24 01:21:35.444 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: button WINDOWS-11 WINDOWS-11_monitorsleep, sending update
2023-03-24 01:21:35.447 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: button WINDOWS-11 WINDOWS-11_monitorwake, sending update
2023-03-24 01:21:35.449 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: button WINDOWS-11 WINDOWS-11_restart, sending update

I too get this a lot, why is the component "rediscovered" again?
2023-06-09 20:46:40.848 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **__ConnectionType, sending update
2023-06-09 20:46:40.857 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **__UserNotificationStateSensor, sending update
2023-06-09 20:46:40.857 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **__CPU, sending update
2023-06-09 20:46:40.858 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **__Geolocation, sending update
2023-06-09 20:46:40.859 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **__LastBoot, sending update
2023-06-09 20:46:40.860 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **__Memory, sending update
2023-06-09 20:46:40.860 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **__LastActive, sending update
2023-06-09 20:46:40.861 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **__BT_LE_Devices, sending update
2023-06-09 20:46:40.863 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **__Microphone_Process, sending update
2023-06-09 20:46:40.863 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: binary_sensor ** **__Microphone_Active, sending update
2023-06-09 20:46:40.864 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: binary_sensor ** **__Webcam_Active, sending update
2023-06-09 20:46:40.865 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **__Webcam_Process, sending update
2023-06-09 20:46:40.881 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **_WindowsUpdates_driver_updates_pending, sending update
2023-06-09 20:46:40.881 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **_WindowsUpdates_software_updates_pending, sending update
2023-06-09 20:46:40.882 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **_WindowsUpdates_driver_updates, sending update
2023-06-09 20:46:40.882 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **_WindowsUpdates_software_updates, sending update
2023-06-09 20:46:40.883 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **_Battery_charge_status, sending update
2023-06-09 20:46:40.883 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **_Battery_full_charge_lifetime, sending update
2023-06-09 20:46:40.884 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **_Battery_charge_remaining_percentage, sending update
2023-06-09 20:46:40.884 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **_Battery_charge_remaining, sending update
2023-06-09 20:46:40.885 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **_Battery_powerline_status, sending update
2023-06-09 20:46:40.885 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **_Audio_default_device, sending update
2023-06-09 20:46:40.886 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **_Audio_default_device_state, sending update
2023-06-09 20:46:40.893 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **_Audio_default_device_volume, sending update
2023-06-09 20:46:40.893 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **_Audio_default_device_muted, sending update
2023-06-09 20:46:40.903 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **_Audio_peak_volume, sending update
2023-06-09 20:46:40.904 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **_Audio_audio_sessions, sending update
2023-06-09 20:46:40.915 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **_Audio_default_input_device, sending update
2023-06-09 20:46:40.916 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **_Audio_default_input_device_state, sending update
2023-06-09 20:46:40.916 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **_Audio_default_input_device_muted, sending update
2023-06-09 20:46:40.917 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **_Audio_default_input_device_volume, sending update
2023-06-09 20:46:40.917 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **_de18243da5874db0881fc1bebe29d316, sending update
2023-06-09 20:46:40.919 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **_total_network_card_count, sending update
2023-06-09 20:46:40.920 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **_8e00941088334e0298c083ab6efa053e, sending update
2023-06-09 20:46:40.920 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **_total_network_card_count, sending update
2023-06-09 20:46:40.921 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **_37926b4c49c549b19d4030f20538a5d6, sending update
2023-06-09 20:46:40.932 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor ** **_total_network_card_count, sending update

Also having the same issues with the discovery message every 30 seconds. Very similar error in the extended log too
2023-06-25 11:34:19.829 +01:00 [INF] [MAIN] HASS.Agent version: 2022.14.0
2023-06-25 11:34:19.831 +01:00 [INF] [MAIN] Extended logging enabled
2023-06-25 11:34:19.834 +01:00 [INF] [SETTINGS] Config storage path: C:\Users\me\AppData\Roaming\LAB02 Research\HASS.Agent\config
2023-06-25 11:34:19.927 +01:00 [INF] [SETTINGS] Configuration loaded
2023-06-25 11:34:19.930 +01:00 [INF] [LOCALIZATION] Selected UI culture: [en] English
2023-06-25 11:34:20.119 +01:00 [INF] [SETTINGS_QUICKACTIONS] Config not found, no entities loaded
2023-06-25 11:34:20.138 +01:00 [INF] [SETTINGS_COMMANDS] Loaded 2 entities
2023-06-25 11:34:25.101 +01:00 [INF] [SETTINGS_SENSORS] Loaded 4 entities
2023-06-25 11:34:25.108 +01:00 [INF] [MQTT] Identifying as device: SPEEDY2
2023-06-25 11:34:25.108 +01:00 [INF] [LOCALAPI] Disabled
2023-06-25 11:34:25.111 +01:00 [INF] [SERVICE] Local install path: C:\Program Files (x86)\LAB02 Research\HASS.Agent Satellite Service\
2023-06-25 11:34:25.116 +01:00 [INF] [MQTT] Connecting ..
2023-06-25 11:34:25.119 +01:00 [INF] [HOTKEY] Completed bind for global quickaction hotkey
2023-06-25 11:34:25.140 +01:00 [INF] [MEDIA] Disabled
2023-06-25 11:34:25.214 +01:00 [INF] [NOTIFIER] Ready
2023-06-25 11:34:25.234 +01:00 [INF] [HASS_API] Home Assistant version: 2023.6.2
2023-06-25 11:34:25.317 +01:00 [INF] [MQTT] Connected
2023-06-25 11:34:25.358 +01:00 [INF] [HASS_API] System connected with https://homeassistant.local:8123
2023-06-25 11:34:27.139 +01:00 [INF] [MQTT] Initial registration completed
2023-06-25 11:36:40.202 +01:00 [FTL] [PROGRAM] FirstChanceException: Unable to read data from the transport connection: The I/O operation has been aborted because of either a thread exit or an application request..
System.IO.IOException: Unable to read data from the transport connection: The I/O operation has been aborted because of either a thread exit or an application request..
 ---> System.Net.Sockets.SocketException (995): The I/O operation has been aborted because of either a thread exit or an application request.
   --- End of inner exception stack trace ---
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token)
   at System.Net.Security.SslStream.ReadAsyncInternal[TIOAdapter](TIOAdapter adapter, Memory`1 buffer)

OS Info
Edition	Windows 10 Pro
Version	22H2
OS build	19045.3086
Experience	Windows Feature Experience Pack 1000.19041.1000.0

Latest HASS.agent and HomeAssistant using mosquitto for MQTT installed on a separate Pi
Always had this error since the first use of HASA.Agent so I've avoided using it up to now.

I have the same problem. Any updates on this one?
Thank you ;)


Get datas from Navisworks without Clash Detection

Hi all!
I have a Navis federated model that collects some files inside and I have to get a spreadsheet of all the elements and some selected properties out of it.
Any idea on how to do it?
Best solution would be accessing the Files in the project in order to be able to dispatch the names and just use the files that I know I need but in case I also have Navis Selection Sets with all the needed objects.
Thank you guys for the help :wink:

http://stuffandbims.blogspot.com.au/2014/10/dynaworks-is-here-navisworks-library.html


Operators Samples

For file names with multiple words, could you please eliminate the space between them (i.e. Arithmetic Operators.qs -> ArithmeticOperators.qs)?


Missing metrics (exported but not stored by Prometheus)

What did you do?
Attempt to use Prometheus to view node_exporter metrics
What did you expect to see?
Metrics existing in Prometheus
What did you see instead? Under which circumstances?
Missing metrics (node_network*,  to be specific)
Environment

System information:

Linux 4.9.20-10.30.amzn1.x86_64 x86_64

Prometheus version:

prometheus, version 2.0.0 (branch: release-2.0, revision: b3ddaf5ae9113a31be7f364c3dfee2e412e72df3)
build user:       kitchen@6e402e1ef1af
build date:       20171113-10:50:17
go version:       go1.8.3

Alertmanager version:

N/A

Prometheus configuration file:

N/A

Alertmanager configuration file:

N/A

Logs:

There appear to be no relevant logs pertaining to this issue.

We have a number of instances in AWS which are running node_exporter. I've connected to the metric endpoint manually and verified that they are exposing the network statistics, which they indeed are. I've also performed a curl from the Prometheus server, and this also returns said network statistics, so I'm at a loss as to why the metrics aren't making themselves into the database. As you can see from the screenshot above, surely there should be at least the same amount of node_network* metrics as there are instances. I realise that some instances may have more than one network interface, but that would result in the count being higher, not lower than the memory metric.
I've tried enabling debug logging but that just spits out unrelated errors (instances discovered via the ec2 config but those which are not yet running node_exporter).
Any ideas?

It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.

I did see the comment about usage questions, but I thought it was worth logging it here as it would appear to be a bug, given the metrics are all being exported but not consumed by Prometheus.

There's insufficient information here to indicate a bug, and usually these issues turn out to be usage issues, so the default presumption is that it's an issue outside of Prometheus. As we get quite a few of these, we direct users to the mailing list to keep the bug tracker tidy.


your website is not working

Thank you so much @yash3056  🙂
I just fixed the error. I was due the package name changes from llama-index.


Update consumables in cancer modules

This brings some refactoring of the consumables of the cancer modules. It is an antecedent of #1298.

Look good - thanks Tim!!

Thanks Joe.
For the 'todos' in cancer_consuambles.py -- is there anything we can do with these now, or do we solve them in the #1298?

I would go with the latter in the interest of getting this PR in?

Look good - thanks Tim!!

Thanks Joe.
For the 'todos' in cancer_consuambles.py -- is there anything we can do with these now, or do we solve them in the #1298?

Thanks Tim. I agree with Joe, I would leave it for #1298, but if you like to solve any, I think you may be able to resolve the # TODO: replace with cystoscope if you merge in also the commit from Sakshi Add cystoscope, endoscope and prostate specific antigen test to consumable list and do the corresponding changes in the code.

Look good - thanks Tim!!

Thanks Joe.
For the 'todos' in cancer_consuambles.py -- is there anything we can do with these now, or do we solve them in the #1298?

Thanks Tim. I agree with Joe, I would leave it for #1298, but if you like to solve any, I think you may be able to resolve the # TODO: replace with cystoscope (I think multiple of such across the cancer modules) and # TODO: replace with PSA test when added to cons list if you merge in also the commit from Sakshi Add cystoscope, endoscope and prostate specific antigen test to consumable list and do the corresponding changes in the code.

OK, I'll flag those those to-dos will be done on #1298.
(Eva - not sure I know where that commit you refer to is....?)

It looks good, except for a few equipment leftovers:

Thanks very much for those spots and suggested changes!! Don't know how those slipped in! All gone now, hopefully.

Look good - thanks Tim!!

Thanks Joe.
For the 'todos' in cancer_consuambles.py -- is there anything we can do with these now, or do we solve them in the #1298?

Thanks Tim. I agree with Joe, I would leave it for #1298, but if you like to solve any, I think you may be able to resolve the # TODO: replace with cystoscope (I think multiple of such across the cancer modules) and # TODO: replace with PSA test when added to cons list if you merge in also the commit from Sakshi Add cystoscope, endoscope and prostate specific antigen test to consumable list and do the corresponding changes in the code.

OK, I'll flag those those to-dos will be done on #1298. (Eva - not sure I know where that commit you refer to is....?)

it's in #1298

Look good - thanks Tim!!

Thanks Joe.
For the 'todos' in cancer_consuambles.py -- is there anything we can do with these now, or do we solve them in the #1298?

Thanks Tim. I agree with Joe, I would leave it for #1298, but if you like to solve any, I think you may be able to resolve the # TODO: replace with cystoscope (I think multiple of such across the cancer modules) and # TODO: replace with PSA test when added to cons list if you merge in also the commit from Sakshi Add cystoscope, endoscope and prostate specific antigen test to consumable list and do the corresponding changes in the code.

OK, I'll flag those those to-dos will be done on #1298. (Eva - not sure I know where that commit you refer to is....?)

it's in #1298, there are two commits from Sakshi: 4d8712f & ff4d072

Apologies, wrong number, it is in #1341.


Error: "This browser or app may not be secure" asks to use different browser!!

I recently moved from firefox to beaker browser and have been in the process of making it my daily browser but this really makes things hard for me.

Please do fix this:)

Yeah this is a known issue and we're not sure how to get around it.
On Fri, Feb 26, 2021 at 1:21 PM Archit<EMAIL_ADDRESS>wrote:

I recently moved from firefox to beaker browser and have been in the
process of making it my daily browser but this really makes things hard for
me.
[image: Screen Shot 2021-02-26 at 2 19 28 PM]
https://user-images.githubusercontent.com/71905307/109345270-deb9f880-783d-11eb-95ba-736f3998d829.png
Please do fix this:)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/beakerbrowser/beaker/issues/1912, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJWCU4JRR42WNPOC477ZH3TA7YEDANCNFSM4YI7FWLA
.

Yeah this is a known issue and we're not sure how to get around it.
…

But google services is widely used and it is very important, users will need this to work properly to use the browser, what User Agent are you guys using? Maybe using Firefox, or chrome's user agent will work out?

In 2019 Google caused the same problem for most independent browsers, and the Firefox user agent specific worked.

Has this issue been resolved ?

Quick Solution
app.userAgentFallback = "Chrome";
app.on("ready", ()=>{
    session.defaultSession.setUserAgent("Chrome");
}

Source
But
Google restricts Sign In's from non standard browsers for a couple of reasons!  A browser running on electron could for example simply have a keylogger installed. That's why google warns developers not to modify their browser's user-agent.

The browser must identify itself clearly in the User-Agent when connecting to accounts.google.com. The browser must not use another browser's User-Agent string, such as Chrome or Firefox on that host.

Source