Kinect_bridge gets slower after some hours of use.

I'm using Kinect_bridge in a i5 without any GPU.  With the "depth_method" parameter set to default, it runs opengldetphregistration (it should not be opencl?)
When I fresh install libfreenect and this package and run Kinect_Bridge i can get in qhd 50 fps. But after some hours of use it easily gets 6fps to qhd and 15 to sd.
Other interesting thing is that i get more fps with less threads working

It is only OpenCL if you compiled libfreenect2 with OpenCL support.
The Kinect2 is only able to deliver 30 fps, so 50 fps cannot be true. Maybe you are referring to the calculated maximum frame rate, that your system could handle.
What CPU are you using? What is the exact name?
The best performance should be achieved, when the number of threads is <= number of CPU cores.
That the frame rate gets lower over time might be a heat issue. Could it be, that the CPU is heating up and therefore lower the clocks? Please check if the temperatures could be the source.

Ok, I could had read wrong the initial frame_rate but it was visually quite faster.
The CPU is i5-4460.
And I can only turn the system faster again after format the disc. So it's not related with CPU temperature.
Can it be related to compiling other ROS packages and some shared compilation flags?

I don't know. Maybe something with your system is wrong.

any update on this?

Not really. It seems like when CPU temperature increases the performance of iai_kinect bridge, mainly when subscribing to qhd/depth topics decreases a lot.


重构 /upyun

Coverage increased (+0.06%) to 88.954% when pulling bdafe8b703c3b54e27f9d8771a322b0c4f395c67 on develop into 9e2afa208d9d4044d5d8c30fd035887558943558 on master.


[Feature]: Chat Completion with Parallel Function Calling

Your current environment
vLLM 0.5.5 openai 1.43.0

Detailed Environments
```text
PyTorch version: 2.4.0+cu121
Is debug build: False
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A
OS: Ubuntu 20.04.3 LTS (x86_64)
GCC version: (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Clang version: Could not collect
CMake version: version 3.28.6
Libc version: glibc-2.31
Python version: 3.10.14 (main, May  6 2024, 19:42:50) [GCC 11.2.0] (64-bit runtime)
Python platform: Linux-5.4.0-189-generic-x86_64-with-glibc2.31
Is CUDA available: True
CUDA runtime version: 12.1.66
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration:
GPU 0: NVIDIA RTX A5000
GPU 1: NVIDIA RTX A4000
GPU 2: NVIDIA RTX A5000
Nvidia driver version: 530.30.02
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True
CPU:
Architecture:                       x86_64
CPU op-mode(s):                     32-bit, 64-bit
Byte Order:                         Little Endian
Address sizes:                      46 bits physical, 48 bits virtual
CPU(s):                             80
On-line CPU(s) list:                0-79
Thread(s) per core:                 2
Core(s) per socket:                 20
Socket(s):                          2
NUMA node(s):                       2
Vendor ID:                          GenuineIntel
CPU family:                         6
Model:                              85
Model name:                         Intel(R) Xeon(R) Gold 5218R CPU @ 2.10GHz
Stepping:                           7
CPU MHz:                            800.033
CPU max MHz:                        4000.0000
CPU min MHz:                        800.0000
BogoMIPS:                           4200.00
Virtualization:                     VT-x
L1d cache:                          1.3 MiB
L1i cache:                          1.3 MiB
L2 cache:                           40 MiB
L3 cache:                           55 MiB
NUMA node0 CPU(s):                  0-19,40-59
NUMA node1 CPU(s):                  20-39,60-79
Vulnerability Gather data sampling: Mitigation; Microcode
Vulnerability Itlb multihit:        KVM: Mitigation: Split huge pages
Vulnerability L1tf:                 Not affected
Vulnerability Mds:                  Not affected
Vulnerability Meltdown:             Not affected
Vulnerability Mmio stale data:      Mitigation; Clear CPU buffers; SMT vulnerable
Vulnerability Retbleed:             Mitigation; Enhanced IBRS
Vulnerability Spec store bypass:    Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:           Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:           Mitigation; Enhanced / Automatic IBRS; IBPB conditional; RSB filling; PBRSB-eIBRS SW sequence; BHI Vulnerable, KVM SW loop
Vulnerability Srbds:                Not affected
Vulnerability Tsx async abort:      Mitigation; TSX disabled
Flags:                              fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cdp_l3 invpcid_single intel_ppin ssbd mba ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm mpx rdt_a avx512f avx512dq rdseed adx smap clflushopt clwb intel_pt avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts hwp hwp_act_window hwp_epp hwp_pkg_req pku ospke avx512_vnni md_clear flush_l1d arch_capabilities
Versions of relevant libraries:
[pip3] mypy-extensions==1.0.0
[pip3] numpy==1.26.4
[pip3] nvidia-cublas-cu12==<IP_ADDRESS>
[pip3] nvidia-cuda-cupti-cu12==12.1.105
[pip3] nvidia-cuda-nvrtc-cu12==12.1.105
[pip3] nvidia-cuda-runtime-cu12==12.1.105
[pip3] nvidia-cudnn-cu12==<IP_ADDRESS>
[pip3] nvidia-cufft-cu12==<IP_ADDRESS>
[pip3] nvidia-curand-cu12==<IP_ADDRESS>
[pip3] nvidia-cusolver-cu12==<IP_ADDRESS>
[pip3] nvidia-cusparse-cu12==<IP_ADDRESS>
[pip3] nvidia-ml-py==12.535.161
[pip3] nvidia-nccl-cu12==2.20.5
[pip3] nvidia-nvjitlink-cu12==12.6.68
[pip3] nvidia-nvtx-cu12==12.1.105
[pip3] onnxruntime==1.19.0
[pip3] pyzmq==25.1.2
[pip3] torch==2.4.0
[pip3] torchvision==0.19.0
[pip3] transformers==4.44.2
[pip3] triton==3.0.0
[conda] numpy                     1.26.4                   pypi_0    pypi
[conda] nvidia-cublas-cu12        <IP_ADDRESS>                 pypi_0    pypi
[conda] nvidia-cuda-cupti-cu12    12.1.105                 pypi_0    pypi
[conda] nvidia-cuda-nvrtc-cu12    12.1.105                 pypi_0    pypi
[conda] nvidia-cuda-runtime-cu12  12.1.105                 pypi_0    pypi
[conda] nvidia-cudnn-cu12         <IP_ADDRESS>                 pypi_0    pypi
[conda] nvidia-cufft-cu12         <IP_ADDRESS>                pypi_0    pypi
[conda] nvidia-curand-cu12        <IP_ADDRESS>               pypi_0    pypi
[conda] nvidia-cusolver-cu12      <IP_ADDRESS>               pypi_0    pypi
[conda] nvidia-cusparse-cu12      <IP_ADDRESS>               pypi_0    pypi
[conda] nvidia-ml-py              12.535.161               pypi_0    pypi
[conda] nvidia-nccl-cu12          2.20.5                   pypi_0    pypi
[conda] nvidia-nvjitlink-cu12     12.6.68                  pypi_0    pypi
[conda] nvidia-nvtx-cu12          12.1.105                 pypi_0    pypi
[conda] pyzmq                     25.1.2          py310h6a678d5_0
[conda] torch                     2.4.0                    pypi_0    pypi
[conda] torchvision               0.19.0                   pypi_0    pypi
[conda] transformers              4.44.2                   pypi_0    pypi
[conda] triton                    3.0.0                    pypi_0    pypi
ROCM Version: Could not collect
Neuron SDK Version: N/A
vLLM Version: 0.5.5@09c7792610ada9f88bbf87d32b472dd44bf23cc2
vLLM Build Flags:
CUDA Archs: Not Set; ROCm: Disabled; Neuron: Disabled
GPU Topology:
GPU0    GPU1    GPU2    CPU Affinity    NUMA Affinity
GPU0     X      NODE    SYS     0-19,40-59      0
GPU1    NODE     X      SYS     0-19,40-59      0
GPU2    SYS     SYS      X      20-39,60-79     1
Legend:
X    = Self
SYS  = Connection traversing PCIe as well as the SMP interconnect between NUMA nodes (e.g., QPI/UPI)
NODE = Connection traversing PCIe as well as the interconnect between PCIe Host Bridges within a NUMA node
PHB  = Connection traversing PCIe as well as a PCIe Host Bridge (typically the CPU)
PXB  = Connection traversing multiple PCIe bridges (without traversing the PCIe Host Bridge)
PIX  = Connection traversing at most a single PCIe bridge
NV#  = Connection traversing a bonded set of # NVLinks```

🐛 Describe the bug
First, launch an OpenAI compatible server: vllm serve meta-llama/Meta-Llama-3.1-8B-Instruct --dtype auto --max_model_len 20480.
Then try to request this server with the following payload for function calling
{
    "messages": [
        {
            "content": "\\nYou are a grader assessing whether an LLM generation is grounded in / supported by a set of retrieved facts.\\nGive a binary score \'yes\' or \'no\', where \'yes\' means that the answer is grounded in / supported by the set of facts.\\n\\nIF the generation includes code examples, make sure those examples are FULLY present in the set of facts, otherwise always return score \'no\'.\\n",
            "role": "system"
        },
        {
            "content": "Set of facts: Provided Documents.",
            "role": "user"
        }
    ],
    "model": "meta-llama/Meta-Llama-3.1-8B-Instruct",
    "stream": false,
    "n": 1,
    "temperature": 0,
    "max_tokens": 2048,
    "tools": [
        {
            "type": "function",
            "function": {
                "name": "GradeHallucinations",
                "description": "Binary score for hallucination present in generation answer.",
                "parameters": {
                    "type": "object",
                    "properties": {
                        "binary_score": {
                            "description": "Answer is grounded in the facts, \'yes\' or \'no\'",
                            "type": "string"
                        }
                    },
                    "required": [
                        "binary_score"
                    ]
                }
            }
        }
    ],
    "parallel_tool_calls": false,
    "tool_choice": {
        "type": "function",
        "function": {
            "name": "GradeHallucinations"
        }
    }
}

The server gives me the error, indicating the wrong parameter parallel_tool_calls.
BadRequestError: Error code: 400 - {'object': 'error', 'message': "[{'type': 'extra_forbidden', 'loc': ('body', 'parallel_tool_calls'), 'msg': 'Extra inputs are not permitted', 'input': False}]", 'type': 'BadRequestError', 'param': None, 'code': 400}

The parameter parallel_tool_calls is declared in OpenAI API references https://platform.openai.com/docs/api-reference/chat/create, should this parameter be added into the ChatCompletionRequest class in vLLM?
Before submitting a new issue...

[X] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

#5649  Tool Calling PR


force requeue after fixing status fields and adding finalizer

UHC reporting long delays between creating clusterdeployment and having the install job launched.
logs indicated delays from when we clear the empty clusterversion in status and adding the finalizer. for these two paths, force a requeue.
add test cases to check for results from Reconcile()

/test e2e


Refactor/visit methods

Hi @hjkcai , thanks for merging the previous PR and publish a new version. When I test that on my repo, it still panics with RuntimeError: unreachable or RuntimeError: out of bounds memory access. Unfortunately, the compiled wasm plugin was hard to debug and I'm trying my best here. I'm hoping the bast that if index < stmts.len() { should fix this issue.
I also did some refactoring to use the native visit_ methods so that it seems more natural way to do.

Thanks a lot! I have made you the collaborator of this repo. Feel free to directly modify something 😄
By the way could you please help me investigate #2 (swc-project/swc#7952)?

I have published v0.2.2 including this patch


[Bug]: Website isn't loading

What happened?
The website isn't loading. Here is a screenshot of it:

I had previously opened calculator.
To reproduce the behavior?
Go to https://win11.blueedge.me
What browser are you seeing the problem on?
Chrome

@Pixel556 looks like the css is not loading (weird)
are u using some extensions if so try disabling it and then loading the site

It was one of the extensions that was causing it. Thanks for your help @yashash1511


Add more basic commands

Hi,
I think that all the options that are available in Zazu icon context menu should be available as commands.

It can be very useful to add an about command, that will open the Zazu about (and you can also add the os and git version, so it would be super easy to get those details for issues for example).
Same for update plugins, check for updates and reload config

Zazu: 0.5.2  ;  OS: win10  ;  GIT: 2.12.2

I love this idea!


Chore/jkastner/2.4.0 cherrypick

Cherry pick two of my PRs onto 2.4.x

can we put the PR numbers in the description of this PR?


load gif image not aspect fit

hi, can you help?
here is my code:

            imageView.contentMode = .scaleAspectFit
            imageView.loadImage(temp.placeHolderUrl?.absoluteString ?? DEFAULT_LOGO_URL)

the image 1,2,5 is not fit the cell ( 120x120)

sorry, i set contentmode in wrong image


Fix Quantum Jobs Readme issues

Fix issue https://github.com/Azure/azure-sdk-for-net/issues/20213
@scottaddie , @AlexGhiondea , @vxfield and @jongio for notification.

@jongio Who should we ping to review this PR?

@vxfield - Please help us merge this PR.

Hi @v-xuto, since this PR touches other service SDKs, I'm not comfortable in merging this PR before the other service owners approving it.
Ideally you should create one PR per service and them they can be reviewed/approved/merged on a per service basis.
I can only approve/merge for the quantum service...

@vxfield I've finished modifying it. Now there's only quantum service, can you help us merge this PR?

Great. Thank you!


AttributeError: 'dict' object has no attribute 'iteritems'

I ran your code, but got this issue in make_tfrecords.py line 92:
error: AttributeError: 'dict' object has no attribute 'iteritems'
Thank you for sharing the code.

To answer my question, python3 does not support iteritems, :+1:


Redo structure of CSS

Currently:

The "master" input CSS lies in Shared, referencing its css bundle in obj
Client and Server have their own npm scripts, outputting directly to their wwwroot

Goal phase 1:

[ ] "master" site.css lives at root directory, referencing Shared.css and others as need be.
[ ] Shared.css will @import the bundled CSS from obj and little else.
[ ] One set of npm scripts, outputting to Shared's wwwroot folder, the html link href being wwwroot/_content/Shared/Shared.css
[ ] If Client or Server create their own CSS one of two things happens:

Vanilla CSS: link it directly in index.html/_Host.cshtml
PostCSS: @import it in site.css and note that it will end up in Shared.css.  Hacky and weird but it works.  All UI should be in Shared though.

Goal phase 2 - maybe:
Currently, we're relying on not just Blazor's CSS Isolation but the bundling as well.  A minor side effect of this is unneeded bundles are copied to wwwroot.  Also, a full rebundle happens even if only one component is changed.  (OK there's only one component in this project but you get it...)  A newish option "Disable Automatic Bundling" exists, leaving it up to us to do the bundling.  Faster incremental rebuilds i'd imagine, and no stray files in wwwroot.  Downside being either manual referencing of individual components's isolated CSS in Shared.css or adding a dependency on node-glob and doing something like this

[ ] apply <DisableScopedCssBundling>true</DisableScopedCssBundling> to Shared
[ ] Change Shared.css to reference individual components' bundled CSS - just obj\scopedcss\Components\PersonCard\PersonCard.razor.rz.scp.css for now.

Currently, if the components' CSS hasn't been generated and a CSS build is requested - as is the current "first run" experience outside of VS Code - there is a hard error: File Not Found.
Using node-glob & resolve as linked could mean no hard errors on first build.  This approach would allow removal of the runOn task for VS Code, but the behavior for Visual Studio / dotnet CLI would still be undesirable: No CSS built by Tailwind as it hadn't been generated yet.  Really really need to figure out how to kick off a non-blocking, single-instance tailwindcss --watch via csproj/msbuild.


🐛 [firebase_auth] authStateChanges.listen sometimes doesn't works on the web

Bug report
Describe the bug
authStateChanges().listen sometimes not triggered when signed in or out.
Steps to reproduce
Steps to reproduce the behavior:

add firebase_auth to pubspec.yaml
listen authStateChanges and catch user.
Run
signInWithEmailAndPassword
authStateChanges not triggered.

Expected behavior
authStateChanges must be triggered just like on mobile.

Additional context
This only happens on the web.
Sometimes we need to hot restart manually to make it works.

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
ekasetiawans@MacBook-Pro ~ % flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel dev, 1.25.0-4.0.pre, on macOS 11.0.1 20B29 darwin-x64,
    locale en-ID)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 12.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.1)
[✓] VS Code (version 1.51.1)
[✓] Connected device (4 available)
    ! Error: iPhone 7 is busy: Processing cache files from device. Xcode will
      continue when iPhone 7 is finished. (code -10)

• No issues found!
ekasetiawans@MacBook-Pro ~ %

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
ekasetiawans@MacBook-Pro retgoo_account_flutter % flutter pub deps -- --style=compact
Dart SDK 2.12.0-76.0.dev
Flutter SDK 1.25.0-4.0.pre
account_retgoo 1.0.0+1

dependencies:
- cloud_firestore 0.14.4 [flutter meta quiver firebase_core firebase_core_platform_interface cloud_firestore_platform_interface cloud_firestore_web]
- cupertino_icons 1.0.1+1
- firebase_auth 0.18.4+1 [meta firebase_core firebase_core_platform_interface firebase_auth_platform_interface firebase_auth_web flutter]
- firebase_core 0.5.3 [firebase_core_platform_interface flutter quiver meta firebase_core_web]
- flutter 0.0.0 [characters collection meta typed_data vector_math sky_engine]
- google_sign_in 4.5.6 [google_sign_in_platform_interface flutter meta google_sign_in_web]
- intl 0.16.1 [path]
- provider 4.3.2+2 [flutter nested collection]

dev dependencies:
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters charcode collection matcher meta source_span stream_channel string_scanner term_glyph typed_data]

transitive dependencies:
- async 2.5.0-nullsafety.3 [collection]
- boolean_selector 2.1.0-nullsafety.3 [source_span string_scanner]
- characters 1.1.0-nullsafety.5
- charcode 1.2.0-nullsafety.3
- clock 1.1.0-nullsafety.3
- cloud_firestore_platform_interface 2.2.1 [flutter meta collection firebase_core plugin_platform_interface]
- cloud_firestore_web 0.2.1+2 [flutter flutter_web_plugins http_parser meta firebase_core firebase_core_web cloud_firestore_platform_interface js]
- collection 1.15.0-nullsafety.5
- fake_async 1.2.0-nullsafety.3 [clock collection]
- firebase_auth_platform_interface 2.1.4 [flutter meta firebase_core plugin_platform_interface]
- firebase_auth_web 0.3.2+3 [flutter flutter_web_plugins meta http_parser intl firebase_core firebase_core_web firebase_auth_platform_interface js]
- firebase_core_platform_interface 2.1.0 [flutter meta plugin_platform_interface quiver]
- firebase_core_web 0.2.1+1 [firebase_core_platform_interface flutter flutter_web_plugins meta js]
- flutter_web_plugins 0.0.0 [flutter js characters collection meta typed_data vector_math]
- google_sign_in_platform_interface 1.1.2 [flutter meta quiver]
- google_sign_in_web 0.9.1+1 [google_sign_in_platform_interface flutter flutter_web_plugins meta js]
- http_parser 3.1.4 [charcode collection source_span string_scanner typed_data]
- js 0.6.3-nullsafety.3
- matcher 0.12.10-nullsafety.3 [stack_trace]
- meta 1.3.0-nullsafety.6
- nested 0.0.4 [flutter]
- path 1.8.0-nullsafety.3
- plugin_platform_interface 1.0.2 [meta]
- quiver 2.1.3 [matcher meta]
- sky_engine 0.0.99
- source_span 1.8.0-nullsafety.4 [charcode collection path term_glyph]
- stack_trace 1.10.0-nullsafety.6 [path]
- stream_channel 2.1.0-nullsafety.3 [async]
- string_scanner 1.1.0-nullsafety.3 [charcode source_span]
- term_glyph 1.2.0-nullsafety.3
- test_api 0.2.19-nullsafety.6 [async boolean_selector collection meta path source_span stack_trace stream_channel string_scanner term_glyph matcher]
- typed_data 1.3.0-nullsafety.5 [collection]
- vector_math 2.1.0-nullsafety.5
ekasetiawans@MacBook-Pro retgoo_account_flutter %

I'm seeing this as well on the latest master 1.25.0-5.0.pre.108 with
  firebase_auth: ^0.18.4+1
  firebase_core: ^0.5.3

  <script src="https://www.gstatic.com/firebasejs/7.20.0/firebase-app.js"></script>
  <script src="https://www.gstatic.com/firebasejs/7.20.0/firebase-auth.js"></script>

flutter doctor -v

```
[√] Flutter (Channel master, 1.25.0-5.0.pre.108, on Microsoft Windows [Version 10.0.19041.630], locale et-EE)
    • Flutter version 1.25.0-5.0.pre.108 at C:\Development\flutter_master
    • Framework revision 995aa138cd (10 hours ago), 2020-12-08 09:18:02 +0530
    • Engine revision b0d31ae166
    • Dart version 2.12.0 (build 2.12.0-125.0.dev)
[√] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
• Android SDK at C:\Users\marku\AppData\Local\Android\sdk
• Platform android-30, build-tools 30.0.2
• Java binary at: C:\Users\marku\AppData\Local\JetBrains\Toolbox\apps\AndroidStudio\ch-0\201.6953283\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
• All Android licenses accepted.
[√] Chrome - develop for the web
• Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe
[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.7.7)
• Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Community
• Visual Studio Community 2019 version 16.7.30621.155
• Windows 10 SDK version 10.0.18362.0
[√] Android Studio (version 4.1.0)
• Android Studio at C:\Users\marku\AppData\Local\JetBrains\Toolbox\apps\AndroidStudio\ch-0\201.6953283
• Flutter plugin can be installed from:
https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
[√] IntelliJ IDEA Ultimate Edition (version 2020.3)
• IntelliJ at C:\Users\marku\AppData\Local\JetBrains\Toolbox\apps\IDEA-U\ch-0\203.5981.155
• Flutter plugin can be installed from:
https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
https://plugins.jetbrains.com/plugin/6351-dart
[√] Connected device (4 available)
• SM G950F (mobile) • ce12171c51cc001c03 • android-arm64  • Android 9 (API 28)
• Windows (desktop) • windows            • windows-x64    • Microsoft Windows [Version 10.0.19041.630]
• Chrome (web)      • chrome             • web-javascript • Google Chrome 87.0.4280.88
• Edge (web)        • edge               • web-javascript • Microsoft Edge 87.0.664.55
• No issues found!
</details>
<details>
 <summary>Modified official code sample</summary>

```dart
import 'package:firebase_core/firebase_core.dart';
import 'package:firebase_auth/firebase_auth.dart';
import 'package:flutter/foundation.dart' show kIsWeb;
import 'package:flutter/material.dart';
import 'package:flutter_signin_button/flutter_signin_button.dart';
import 'package:google_sign_in/google_sign_in.dart';

final FirebaseAuth _auth = FirebaseAuth.instance;

Future<void> main() async {
  WidgetsFlutterBinding.ensureInitialized();
  await Firebase.initializeApp();
  runApp(AuthExampleApp());
}

/// The entry point of the application.
///
/// Returns a [MaterialApp].
class AuthExampleApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(title: 'Firebase Example App', theme: ThemeData.dark(), home: SignInPage());
  }
}

/// Entrypoint example for various sign-in flows with Firebase.
class SignInPage extends StatefulWidget {
  /// The page title.
  final String title = 'Anonymous number link test';

  @override
  State<StatefulWidget> createState() => _SignInPageState();
}

class _SignInPageState extends State<SignInPage> {
  String uid = "";

  @override
  void initState() {
    changeUidText(_auth.currentUser);
    _auth.userChanges().listen(changeUidText);
    super.initState();
  }

  void changeUidText(User user) {
    setState(() {
      if (user == null) {
        uid = "Signed out";
        return;
      }
      uid = user.uid;
      if (user.email != null) {
        uid += " " + user.email;
      }
    });
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
        actions: <Widget>[
          Builder(builder: (BuildContext context) {
            return FlatButton(
              child: const Text('Sign out'),
              textColor: Theme.of(context).buttonColor,
              onPressed: () async {
                final User user = await _auth.currentUser;
                if (user == null) {
                  Scaffold.of(context).showSnackBar(const SnackBar(
                    content: Text('No one has signed in.'),
                  ));
                  return;
                }
                _signOut();
                final String uid = user.uid;
                Scaffold.of(context).showSnackBar(SnackBar(
                  content: Text(uid + ' has successfully signed out.'),
                ));
              },
            );
          })
        ],
      ),
      body: Builder(builder: (BuildContext context) {
        return ListView(
          padding: EdgeInsets.all(8),
          scrollDirection: Axis.vertical,
          children: <Widget>[
            Text(uid),
            RaisedButton(
              child: const Text("Print currentUser info"),
              onPressed: () => print(_auth.currentUser.toString()),
            ),
            _EmailPasswordForm(),
          ],
        );
      }),
    );
  }

  // Example code for sign out.
  void _signOut() async {
    await _auth.signOut();
  }
}

class _EmailPasswordForm extends StatefulWidget {
  @override
  State<StatefulWidget> createState() => _EmailPasswordFormState();
}

class _EmailPasswordFormState extends State<_EmailPasswordForm> {
  final GlobalKey<FormState> _formKey = GlobalKey<FormState>();
  final TextEditingController _emailController = TextEditingController();
  final TextEditingController _passwordController = TextEditingController();

  @override
  Widget build(BuildContext context) {
    return Form(
        key: _formKey,
        child: Card(
          child: Padding(
            padding: const EdgeInsets.all(16.0),
            child: Column(
              crossAxisAlignment: CrossAxisAlignment.start,
              children: <Widget>[
                Container(
                  child: const Text(
                    'Sign in with email and password',
                    style: TextStyle(fontWeight: FontWeight.bold),
                  ),
                  alignment: Alignment.center,
                ),
                TextFormField(
                  controller: _emailController,
                  decoration: const InputDecoration(labelText: 'Email'),
                  validator: (String value) {
                    if (value.isEmpty) return 'Please enter some text';
                    return null;
                  },
                ),
                TextFormField(
                  controller: _passwordController,
                  decoration: const InputDecoration(labelText: 'Password'),
                  validator: (String value) {
                    if (value.isEmpty) return 'Please enter some text';
                    return null;
                  },
                  obscureText: true,
                ),
                Container(
                  padding: const EdgeInsets.only(top: 16.0),
                  alignment: Alignment.center,
                  child: SignInButton(
                    Buttons.Email,
                    text: "Sign In",
                    onPressed: () async {
                      if (_formKey.currentState.validate()) {
                        _signInWithEmailAndPassword();
                      }
                    },
                  ),
                ),
              ],
            ),
          ),
        ));
  }

  @override
  void dispose() {
    _emailController.dispose();
    _passwordController.dispose();
    super.dispose();
  }

  // Example code of how to sign in with email and password.
  void _signInWithEmailAndPassword() async {
    try {
      final User user = (await _auth.signInWithEmailAndPassword(
        email: _emailController.text,
        password: _passwordController.text,
      ))
          .user;

      Scaffold.of(context).showSnackBar(SnackBar(
        content: Text("${user.email} signed in"),
      ));
    } catch (e) {
      Scaffold.of(context).showSnackBar(SnackBar(
        content: Text("Failed to sign in with Email & Password"),
      ));
    }
  }
}

In my case it only happens after a browser refresh. Before a refresh, sign in with a 'authStateChanges()' listener works fine.

an additional case, if the website has been published, you have to reload many times until it can capture data in authstatechanges.

Additional info I can add is that it seems that the demo project, which doesn't explicitly use the published package firebase_auth: ^0.18.4+1 and instead uses the github version with
firebase_auth:
    path: ../

authStateChanges are fired correctly and as expected.
In my case this is a definite regression as user persistance was working fine until lately users started noticing they have to login every time.

I've looked more into this, mainly as this deeply impacts user experience, and I've found two configurations which work:
pubspec.yaml
-------------------
firebase_auth: 0.18.3
firebase_core: 0.5.2

index.html
-----------------
<script src="https://www.gstatic.com/firebasejs/7.20.0/firebase-app.js"></script>
<script src="https://www.gstatic.com/firebasejs/7.20.0/firebase-auth.js"></script>

OR
pubspec.yaml
-------------------
firebase_auth: 0.18.4+1
firebase_core: 0.5.3

index.html
-----------------
<script src="https://www.gstatic.com/firebasejs/7.5.0/firebase-app.js"></script>
<script src="https://www.gstatic.com/firebasejs/7.5.0/firebase-auth.js"></script>

So until this is fixed you can choose which functionality you rather sacrifice.

I want to note we've experience this issue in production as well.

Probably same issue here. Need to clear the browser's cache and data every time, else it won't log-in.

In terms of priority, I would like to see this issue categorized as high priority.
Because a user auth status listener is the ONLY reliable way Firebase Auth supports for fetching the authentication status of a user, without this working, everything auth related breaks.
I can provide a reproducible sample if that would help

For me using auth.userChanges() was the (temporary) solution:
From firebase_auth.dart
  /// Notifies about changes to any user updates.
  ///
  /// This is a superset of both [authStateChanges] and [idTokenChanges]. It
  /// provides events on all user changes, such as when credentials are linked,
  /// unlinked and when updates to the user profile are made. The purpose of
  /// this Stream is to for listening to realtime updates to the user without
  /// manually having to call [reload] and then rehydrating changes to your
  /// application.
  Stream<User> userChanges() => _pipeStreamChanges(_delegate.userChanges());

Any updates on this issue, I am also having the same problem. This is definitely a priority issue to fix.
Thanks.

Any updates on this issue, I am also having the same problem. This is definitely a priority issue to fix.
Thanks.

I'm experiencing the same issue. Would love some clarity on if this is going to be fixed / if there's any workarounds for the time being, as it's affecting my users

For anyone struggling - I fixed it for myself like that:
FirebaseAuth.instance         .authStateChanges()         .startWith(FirebaseAuth.instance.currentUser)

This should be fixed in the latest version. Web & Native platforms have undergone a bit of a rework to keep them consistent with each other.

Hey folks, is anyone still experiencing this issue after upgrading to the latest version?

I just tried with version 2, my app still gets stuck on my splash screen waiting for an auth event.. for the time being I've worked around the issue by having the splash screen check if a user exists:
    WidgetsBinding.instance!.addPostFrameCallback((_) {
      final user = context.read<AuthenticationRepository>().currentUser;
      if (user == User.empty) {
        print('No user found on SpashPage');
      } else {
        Navigator.pushReplacementNamed(context, HomePage.id);
      }
    });

The good news is that this issue seems to be resolved in production.
Unfortunately, hot reload still has this issue where #6192 is not resolved.

@searchy2 That's an issue with the Dart SDK, been fixed on 2.14.0-276.0.dev - see https://github.com/dart-lang/sdk/commit/460887d8149748d3feaad857f1b13721faadeffa for more info.

This issue, and the hot reload issue has now been resolved I believe.

@searchy2 That's an issue with the Dart SDK, been fixed on 2.14.0-276.0.dev - see dart-lang/sdk@460887d for more info.

No.
When I turn on All exception - still appears...


[misc] Support ss for locale/en-li

In src/locale/en-li.js, ss is not under relativeTime.
So '%d seconds' has not been supported yet.

Coverage decreased (-0.07%) to 88.336% when pulling 9efacdf762da65eb658d59eeb72754d7277b02a2 on HyunSangHan:en-li/ss into 13a61b285c095bda7ea8e33156090ea5ccfeaef1 on moment:develop.

Coverage decreased (-0.07%) to 88.336% when pulling 9efacdf762da65eb658d59eeb72754d7277b02a2 on HyunSangHan:en-li/ss into 13a61b285c095bda7ea8e33156090ea5ccfeaef1 on moment:develop.

I could not help decreasing the coverage, because the thresholds of s and ss are below:
var thresholds = {
    ss: 44,         // a few seconds to seconds
    s : 45,         // seconds to minute
    m : 45,         // minutes to hour
    h : 22,         // hours to day
    d : 26,         // days to month
    M : 11          // months to year
};


Roll engine c9bbd0e680d9..de420a0fc49a (4 commits)

https://github.com/flutter/engine/compare/c9bbd0e680d9...de420a0fc49a
git log c9bbd0e680d9aa57fad27d8c67128633210a586e..de420a0fc49ac5d8d84e3dd446af800d672eff02 --no-merges --oneline
de420a0fc Roll src/third_party/dart 97f91fecdb..7ecd81b0b8 (5 commits) (flutter/engine#9268)
8812781d9 Roll src/third_party/skia bba5aa761cd5..a716809d5ad3 (1 commits) (flutter/engine#9269)
b470913fb Roll src/third_party/skia 77cb2ca3c9aa..bba5aa761cd5 (3 commits) (flutter/engine#9267)
48ecbca8a Roll src/third_party/skia bb74990a11d9..77cb2ca3c9aa (1 commits) (flutter/engine#9265)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (liyuqian@google.com), and stop
the roller if necessary.

Auto-roller completed checks. About to merge.


Replaced fetch with Ocktokit in GitHubEvents

Removed fetch and used Ocktokit to retrieve data from API in GitHubEvents.tsx file.
fix: #346

@rithviknishad I have tried to replace fetch ocktokit is it right?

@rithviknishad I made the changes have a look

@rithviknishad removed any in previous commit

@rithviknishad I removed any in previous commit


[BUG] Integration tests for dashboards failing with the image/latest we are currently using

Is your feature request related to a problem? Please describe
Integtests dashboards jenkins workflow uses the docker image latest (v4 == v4.3 at the time of writing this)
This is failing for a few of the dashboard plugins with the following error
Sending interrupt signal to process
script returned exit code 143.
Sample build
Plugins failed:
opensearch-dashboards
alertingDashboards
anomalyDetectionDashboards
customImportMapDashboards
indexManagementDashboards
observabilityDashboards
securityAnalyticsDashboards
securityDashboards

The issue is seen with the new image which has been recently uploaded, but the the previous versions of the docker image are working fine. (previous version == 4.2)
Describe the solution you'd like
Debug the reason for the failing tests or revert the image latest to use the previous version for integ-testing
Describe alternatives you've considered
No response
Additional context
No response

Will take a look on whether the changes of the user and home cause this issue.

Using OSD tar on 2.12 7163 build on x64 as an example.
Using 4.2 image will pass everything successfully.
Using 4.3 image will keep stucking on this step of without-security test for dashboards-maps:

  Running:  plugins/custom-import-map-dashboards/documentsLayer.spec.js                     (2 of 4)

  Documents layer

In 4.2 it passes with this:

  Running:  plugins/custom-import-map-dashboards/documentsLayer.spec.js                     (2 of 4)

  Documents layer
    ✓ Add new documents layer with configuration (110069ms)
    ✓ Open saved map with documents layer

  2 passing (2m)

Seems like issues with the chromium browser, or compatibility between Cypress 9.5.4 and Chromium version over 114:
% docker exec -it osd-rockylinux-4.2 chromium-browser --version
Chromium 114.0.5735.198 Fedora Project

% docker exec -it osd-rockylinux-4.3 chromium-browser --version
Chromium 118.0.5993.117 Fedora Project

The cypress test will stuck on the Chromium version > 114.
I even use the very old dockerfile that build 4.2 to build a new image here: https://github.com/opensearch-project/opensearch-build/blob/35048a49164337843efcf128a2b4245dc1559b8c/docker/ci/dockerfiles/current/test.rockylinux8.opensearch-dashboards.x64.arm64.dockerfile
And it still stuck with the same issue, version is:
% docker exec -it osd-rockylinux-4.2-rebuild chromium-browser --version
Chromium 120.0.6099.199 Fedora Project

The 4.2 Rebuild Logs are here:
opensearch_dashboards.log
opensearch.log
cypress.log

I switch back to electron and the test passes.

$ env TZ=America/Los_Angeles NO_COLOR=1 cypress run --headless --env SECURITY_ENABLED=false --browser electron --spec 'cypress/integration/plugins/custom-import-map-dashboards/*'

====================================================================================================

  (Run Starting)

  ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ Cypress:        9.5.4                                                                          │
  │ Browser:        Electron 94 (headless)                                                         │
  │ Node Version:   v18.16.0 (/usr/share/opensearch/.nvm/versions/node/v18.16.0/bin/node)          │
  │ Specs:          4 found (plugins/custom-import-map-dashboards/add_saved_object.spec.js, plugin │
  │                 s/custom-import-map-dashboards/documentsLayer.spec.js, plugins/custom-import-m │
  │                 ap-dashboards/import_vector_map_tab.spec.js, plugins/custom-import-map-dashboa │
  │                 rds/opensearchMapLayer...)                                                     │
  │ Searched:       cypress/integration/plugins/custom-import-map-dashboards/*                     │
  └────────────────────────────────────────────────────────────────────────────────────────────────┘

────────────────────────────────────────────────────────────────────────────────────────────────────

  Running:  plugins/custom-import-map-dashboards/add_saved_object.spec.js                   (1 of 4)

  Add flights dataset saved object
    ✓ check if maps saved object of flights dataset can be found and open (76695ms)

  1 passing (1m)

  (Results)

  ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ Tests:        1                                                                                │
  │ Passing:      1                                                                                │
  │ Failing:      0                                                                                │
  │ Pending:      0                                                                                │
  │ Skipped:      0                                                                                │
  │ Screenshots:  0                                                                                │
  │ Video:        true                                                                             │
  │ Duration:     1 minute, 20 seconds                                                             │
  │ Spec Ran:     plugins/custom-import-map-dashboards/add_saved_object.spec.js                    │
  └────────────────────────────────────────────────────────────────────────────────────────────────┘

  (Video)

  -  Started processing:  Compressing to 32 CRF
  -  Finished processing: /tmp/tmpjmuih98k/customImportMapDashboards/cypress/videos/p    (8 seconds)
                          lugins/custom-import-map-dashboards/add_saved_object.spec.j
                          s.mp4

────────────────────────────────────────────────────────────────────────────────────────────────────

  Running:  plugins/custom-import-map-dashboards/documentsLayer.spec.js                     (2 of 4)

  Documents layer
    ✓ Add new documents layer with configuration (114497ms)
    ✓ Open saved map with documents layer (5851ms)

  2 passing (2m)

There is no way to install chromium 114 now as the latest available on fedora project repo is already 120.
The 120 chromium will also cause this issue on security enabled test:

  Running:  plugins/custom-import-map-dashboards/documentsLayer.spec.js                     (2 of 4)

  0 passing (2ms)

Warning: We failed processing this video.

This error will not alter the exit code.

TimeoutError: operation timed out
    at afterTimeout (/usr/share/opensearch/.cache/Cypress/9.5.4/Cypress/resources/app/packages/server/node_modules/bluebird/js/release/timers.js:46:19)
    at Timeout.timeoutTimeout [as _onTimeout] (/usr/share/opensearch/.cache/Cypress/9.5.4/Cypress/resources/app/packages/server/node_modules/bluebird/js/release/timers.js:76:13)
    at listOnTimeout (node:internal/timers:557:17)
    at processTimers (node:internal/timers:500:7)

Firefox issues:

yarn run v1.22.21
$ env TZ=America/Los_Angeles NO_COLOR=1 cypress run --headless --env SECURITY_ENABLED=false --browser firefox --spec 'cypress/integration/plugins/custom-import-map-dashboards/*'

====================================================================================================

  (Run Starting)

  ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ Cypress:        9.5.4                                                                          │
  │ Browser:        Firefox 115 (headless)                                                         │
  │ Node Version:   v18.16.0 (/usr/share/opensearch/.nvm/versions/node/v18.16.0/bin/node)          │
  │ Specs:          4 found (plugins/custom-import-map-dashboards/add_saved_object.spec.js, plugin │
  │                 s/custom-import-map-dashboards/documentsLayer.spec.js, plugins/custom-import-m │
  │                 ap-dashboards/import_vector_map_tab.spec.js, plugins/custom-import-map-dashboa │
  │                 rds/opensearchMapLayer...)                                                     │
  │ Searched:       cypress/integration/plugins/custom-import-map-dashboards/*                     │
  └────────────────────────────────────────────────────────────────────────────────────────────────┘

────────────────────────────────────────────────────────────────────────────────────────────────────

  Running:  plugins/custom-import-map-dashboards/add_saved_object.spec.js                   (1 of 4)

  Add flights dataset saved object
Still waiting to connect to Firefox, retrying in 1 second (attempt 18/62)

Cypress failed to make a connection to Firefox.

This usually indicates there was a problem opening the Firefox browser.

Error: could not find CRI target
    at lazyAssLogic (/usr/share/opensearch/.cache/Cypress/9.5.4/Cypress/resources/app/node_modules/lazy-ass/index.js:110:14)
    at lazyAss (/usr/share/opensearch/.cache/Cypress/9.5.4/Cypress/resources/app/node_modules/lazy-ass/index.js:115:28)
    at findStartPage (/usr/share/opensearch/.cache/Cypress/9.5.4/Cypress/resources/app/packages/server/lib/browsers/protocol.js:56:28)
    at runMicrotasks (<anonymous>:null:null)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
~

Chrome 121 show the same issue as chromium120.

Approaches:

Upgrade Cypress from 9.5.4 to latest version (Long Term)

Pros:

Resolve the issue from the root cause
Update to latest Cypress for more features and functions

Cons:

Significant amount of work on both the core changes and all plugins to support it, already tried by Craig and Security Team contractor for several times, both stale: https://github.com/opensearch-project/opensearch-dashboards-functional-test/issues/408
Will not be done for 2.12.0 release

Change FTrepo to use Electron instead of Chromium

Pros:

Quick Fix
Proves working

Cons:

Directly change FTrepo which cause all users of FTrepo force to change from Chromium to Electron
Have issues with Electron not showing all the issues that Chromium shows

(Recommended) Change opensearch-build to define BROWSER_PATH=electron env vars to override FTrepo settings

Pros:

Quick Fix
Proves working
Will not change FTrepo and only change opensearch-build related workflows

Cons:

Have issues with Electron not showing all the issues that Chromium shows

@kavilla @joshuarrrr @ashwin-pc @seraphjiang  @AMoo-Miki  We are thinking if using electron for 2.12.0 instead of Chromium due to the issues mentioned above. Can you provide your inputs?


Warning message for incompatibility of topology and market model should be more verbose

Right now it just tells me that some stakeholders are not compatible:

It would really help if the user gets a list of those that are in the Market Model but not in the topology (and vice versa).

For example, I'm using the default topology:
---
name: HV Network
stakeholder: producer
children:
- name: HV-MV Trafo
  capacity: 16000
  technical_lifetime: 30
  investment_cost: 150000
  stakeholder: system operator
  children:
  - name: 'MV-LV Trafo #1'
    capacity: 2000
    technical_lifetime: 30
    investment_cost: 50000
    stakeholder: system operator
    children:
    - name: Households 1
      capacity: 17.25
      units: 33
      stakeholder: customer
  - name: 'MV-LV Trafo #2'
    capacity: 2000
    technical_lifetime: 30
    investment_cost: 50000
    stakeholder: system operator
    children:
    - name: Households 2
      capacity: 17.25
      units: 33
      stakeholder: customer
  - name: 'MV-LV Trafo #3'
    capacity: 2000
    technical_lifetime: 30
    investment_cost: 50000
    stakeholder: system operator
    children:
    - name: Households 3
      capacity: 17.25
      units: 33
      stakeholder: cooperation

which includes, producer, customer, system operator and cooperation.
My market model includes all of these stakeholders except the system operator:

but still I get the warning for incompatibility!


chore(docs): Adds automated sphinx builds to tox and travis

This PR adds tox and travis jobs for building documentation with sphinx.
It also modified CONTRIBUTING.md to show how to build it. :-)
Comments/suggestions welcome!

lgtm, but it needs to be rebased.

Looks good, thanks!


UI components repeated on titlebar when NewUI is enabled, on 2022.3 EAP

Description of the bug:
Please refer to the attached screenshot.
Tried on

Non-Bazel project on 2022.3 EAP NewUI enabled
Bazel project on 2022.3 EAP NewUI disabled
Bazel project on 2022.2 NewUI enabled

They are all good.
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
No response
Which Intellij IDE are you using? Please provide the specific version.
IntelliJ IDEA 2022.3 Beta (Ultimate Edition) Build #IU-223.7571.4
What programming languages and tools are you using? Please provide specific versions.
No response
What Bazel plugin version are you using?
2<IP_ADDRESS>.1-api-version-223
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?

Hello @jameslan, Can you provide complete steps to reproduce the above issue. Thanks!

@sgowroji this issue is for Intellij with 2022.3+ update which includes the new ui. I've got the same issue.

Enable the new ui on intellij 2022.3
Load bazel project


Workaround for possible bug in API for color detection

Fixed required for #27
The Wink API states the following.
color_model|(string)|one of: "xy", "hsb", "color_temperature", or "rgb"
Based on the response from the Osram bulb you would think that it supports setting color via rgb or hsb. I don't see any documentation on how to set via rgb, and I don't see rgb color listed in the response form the Osram bulb.
So having said that this would be an additional fix for color detection. If a bulb indicates that it supports both rgb and hsb, default to hsb. I will see about reaching out to Wink to have this corrected, or clarified.
Additional changes to Home-Assistant will still be required for the Osram bulb to work in full color mode. I have it working locally, and will be able to open the Home-Assistant pull request once this is pushed to pypi.

Coverage decreased (-0.07%) to 87.059% when pulling efb1641cdf1bb74cf81beb4c3ab252b046338a60 on w1ll1am23:fix_bulb_color_detection into 7a2f0ddb594ae15b95c82a8857aa68591b041003 on python-wink:master.

Coverage decreased (-0.07%) to 87.059% when pulling 9fee1d10e1c91b7a9f20ab173c62eb4e29363864 on w1ll1am23:fix_bulb_color_detection into 7a2f0ddb594ae15b95c82a8857aa68591b041003 on python-wink:master.

Could this code change implemented in the HA code instead?
I'd like python-wink to be a true representation of what is coming back from the API, regardless of whether or not that response makes logical sense.

That's a good point, don't see why not. I'll try doing that.
On Sep 5, 2016 12:05 AM, "Brad Johnson"<EMAIL_ADDRESS>wrote:

Could this code change implemented in the HA code instead?
I'd like python-wink to be a true representation of what is coming back
from the API, regardless of whether or not that response makes logical
sense.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/python-wink/python-wink/pull/49#issuecomment-244655002,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGIoAq1PcJMBzpXBtdIVbSo265zS6jSWks5qm5UAgaJpZM4J0tH0
.


Automated cherry pick of #3027: fix: 避免监听未设置manager_id

Cherry pick of #3027 on release/2.11.
#3027: fix: 避免监听未设置manager_id

Codecov Report

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

@@              Coverage Diff               @@
##             release/2.11   #3029   +/-   ##
==============================================
  Coverage                ?   7.15%
==============================================
  Files                   ?     476
  Lines                   ?   76665
  Branches                ?       0
==============================================
  Hits                    ?    5486
  Misses                  ?   70718
  Partials                ?     461

Flag
Coverage Δ

#aFlag
7.15% <0%> (?)

Impacted Files
Coverage Δ

pkg/compute/models/loadbalancerlisteners.go
1.67% <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 7bc624a...b9dd1d7. Read the comment docs.

/lgtm


#autobalance does not update Game Settings screen

[http://www.freeallegiance.org/forums/index.php?showtopic=45071 Relevant topic]

Start a game.
The GC uses #autobalance.
Game Settings retains the old value.
Game ends.
Next game starts with old value.

I don't know if the bug is clientside or serverside, to be honest.
Imported from trac ticket #4,  created by badp on 01-05-2010 at 09:04, last modified: 07-06-2010 at 07:10

'''Imago'''
This bug can be fixed by sending an updated MISSIONPARAMS fedmsg after
receiving the #autobalance setting chat.
Trac comment by fuzzylunkin1 on 01-05-2010 at 09:05

r672
Trac comment by Imago on 07-06-2010 at 07:10


[ogre]: FindPackage(OGRE...) set release OGRE_PLUGIN_DIR and OGRE_CONFIG_DIR for Debug

Describe the bug
In a foreign project, using Ogre package with CMake and display the OGRE_PLUGIN_DIR  like:
find_package(OGRE REQUIRED COMPONENTS Overlay)
target_link_libraries(MyTarget PUBLIC OgreOverlay)

message(OGRE_PLUGIN_DIR='${OGRE_PLUGIN_DIR}')

displays the same string, in debug and in release: vcpkg/installed/x64-windows/bin. The debug plugins are in vcpkg/installed/x64-windows/debug/bin
Environment

OS: Windows 10
Compiler: Microsoft (R) C/C++ Optimizing Compiler Version 19.28.29335 for x64

To Reproduce
Steps to reproduce the behavior:

./vcpkg install ogre
In a CMake project in Debug (CMAKE_BUILD_TYPE=Debug):

find_package(OGRE REQUIRED COMPONENTS Overlay)
target_link_libraries(MyTarget PUBLIC OgreOverlay)

message(OGRE_PLUGIN_DIR='${OGRE_PLUGIN_DIR}')

Expected behavior
OGRE_PLUGIN_DIR and OGRE_CONFIG_DIR  should match the build type, as the debug plugin are not in the same directory as release one.
Additional context
Maybe other variable should be checked in the generated OGREConfig.cmake. The problem may be somewhere in OGREConfig.cmake.in. I begin to think it is really ambitious to mix debug and release build, sharing cmake files, includes, config..

In OGREConfig.cmake:
set(OGRE_STATIC OFF)
set(OGRE_MEDIA_DIR "${PACKAGE_PREFIX_DIR}/Media")
set(OGRE_PLUGIN_DIR "${PACKAGE_PREFIX_DIR}/bin")
set(OGRE_CONFIG_DIR "${PACKAGE_PREFIX_DIR}/bin")

set(OGRE_PREFIX_DIR "${PACKAGE_PREFIX_DIR}")
get_filename_component(OGRE_LIBRARY_DIRS "${OGRE_PREFIX_DIR}/lib" ABSOLUTE)
get_filename_component(OGRE_INCLUDE_DIRS "${OGRE_PREFIX_DIR}/include/OGRE" ABSOLUTE)
set(OGRE_LIBRARIES)

This is because ogre's cmake configuration files are installed together in vcpkg.
If according to the upstream design, the configuration of debug and release are separated, then OGRE_*_DIR will be pointed to the corresponding folder. But in vcpkg, we merged release/share/ogre/OGREConfig.cmake and debug/share/ogre/OGREConfig.cmake, which caused this issue.
I think we can only choose where to point to by adding a judgment CMAKE_BUILD_TYPE where these paths are set in OGREConfig.cmake.

This issue was fixed in PR 32853.


Cannot save project...

Describe the bug
failed to save project...
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-bzvhkd
Steps to reproduce
modifying code, but not saving!
Expected behavior
Save project!
Screen Recording / Screenshot
No response
Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 130
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 95355908,
  "usedJSHeapSize": 83236088,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = Ndeavr
Chat ID = e0a134070635

Additional context
No response

Hi @Ndeavr,
Are you able to find your project by going to stackblitz.com, logging in (same credentials as Bolt), clicking Collections on the left-hand side of the page, and then opening Bolt Collection?

yes it works. But I need Bolt.new to work as I am not a programmer.
But something's not right, I spent millions of tokens trying to reconnect,
to debug... I guess you can see that!
On Sat, Nov 16, 2024 at 9:39 AM Brian @.***> wrote:

Hi @Ndeavr https://github.com/Ndeavr,
Are you able to find your project by going to stackblitz.com, logging in
(same credentials as Bolt), clicking Collections on the left-hand side of
the page, and then opening Bolt Collection?
—
Reply to this email directly, view it on GitHub
https://github.com/stackblitz/bolt.new/issues/2514#issuecomment-2480599328,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3UB6Y32JV25MOJMJLKUGAT2A5KL5AVCNFSM6AAAAABR4VYYQ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBQGU4TSMZSHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

This page here contains a number of insights on using Bolt most effectively while maximizing token efficiency. At times, if Bolt is unable to auto-fix the issue manual intervention is required to prevent excessive token usage. Hope this helps!


fix: Avoid registering mappers for unselected streams

Closes #1942

:books: Documentation preview :books:: https://meltano-sdk--1944.org.readthedocs.build/en/1944/

Sunk too much time trying to fix the failing SQLite test. Leaving it for now...


Lowercase GH org name in .gitmodules

The Microsoft org has been renamed to microsoft. While casing isn't an issue with GitHub, just correcting it in case some implementations are case-sensitive.

I don't see why not. :smile:

Funny enough, i chose capital-T Terminal when I renamed it because when I last looked it was capital-M Microsoft :(

@DHowett-MSFT that’s fine, this is the THE Terminal, with capital T 😉


add serialization and deserialization

Thanks @nlangellier, as notebooks are hard to review in json format I'm happy to just merge. We will improve the material incrementally in the coming days / few weeks anyway.


[BUG] Popup missing dll when running the .exe

When running the .exe there is a problem with GetDaylightFlag.dll missing in ucrtbase.dll
Expected Behavior
No DLL are missing
Current Behavior
At least one DLL is missing.
Possible Solution

-r RESOURCE, --resource RESOURCE
Add or update a resource to a Windows executable. The RESOURCE is one to four items,
FILE[,TYPE[,NAME[,LANGUAGE]]]. FILE can be a data file or an exe/dll. For data files, at least TYPE and
NAME must be specified. LANGUAGE defaults to 0 or may be specified as wildcard * to update all resources
of the given TYPE and NAME. For exe/dll files, all resources from FILE will be added/updated to the final
executable if TYPE, NAME and LANGUAGE are omitted or specified as wildcard *.This option can be used
multiple times.

Install the Windows Software Development Kit (SDK) for Windows 10 and expand the .spec-file to include the
required DLLs, see “Distributing Software that uses the Universal CRT“ in the above-mentioned link, number 6
https://readthedocs.org/projects/pyinstaller/downloads/pdf/stable/

Steps to Reproduce

Download the .exe
Run the .exe

Context (Environment)
OS: Windows 11

No support for Windows planned anymore.


The size of license icons should be 30px

In the single result page, the license icons should be 30px
Current implementation

can I be assigned to fix this issue?

We are no longer doing assignments; anyone is free to submit a PR for issues marked "help wanted". Please read our contribution guidelines.

Thanks. Good to know that.


It's possible for a wire to break signal

I think this bug occurs if you place a wire line, break a block in the middle, then replace the wire. The signal doesn't connect up properly. I'll do some testing in the meantime.

It seems that if you have multiple wires in the same block space, the signal gets confused

Another anomaly

Hey man, ty for the report. The complicated fixes that had to be made with the new update order has apparently introduced a regression that slipped the checks ;; That's gonna be a "Vanilla Redstone one" - aka a horrible one to fix ;). I presume the neighbour updates of the track networks interfere now.

... It is likely that late 1.20.x (neo:forge + fabric) may be affected as well, this was a vanilla change.

Yeah. Easy to work around for now, just less compact wiring

For 1.21 fabric I just pushed a beta for testing. It was a regression issue when working around changed redstone handling in vanilla and mods. Could you risk a glimpse at that? I was not able to test it in depth (like what happens to Dropper triggering from various sides, or e.g. Alternate Current and similar mods go along with it) - so "maybe fxed" ;).
Download link is: https://modrinth.com/mod/redstonepen/version/1.11.36

Oky the actual fix is out. There is still the visual glitch when placing, I could not track that - the debug info show that the block knows the correct values, so this looks as having something to do with the network synchronization - which is very strange.
For the next while we'll have to live with it, I have to defer the task for timing reasons.

Fixes are up on the distribution platforms. The visual glitch is considered in a separate thread/issue.


Rez test improvements (dev mode, interactive flag)

Some rez test improvements

added the ability to run rez test in "developer mode" using rez test . from the root folder of the package.
Automatically build the package if the package is not found in  the REZ_LOCAL_PACKAGES_PATH
Update the built package.py if the tests section changed
added --interactive option, to resolve an interactive environment to run the tests. ie. (rez test --interactive TESTNAME). In case the package has multiple variants, you can also specify the variant using --variant
By default change to a build/rez_test_result directory to run the test and store the test artifacts (this way we can pick those results from tools like sonar, that expect the nose and coverage reports in a known place). If they need to be run on the root of the packages  run_in_root can be set in the tests field of the package.py.
added --clean to clean the test artifacts created from a previous test run.
Tests added along with the mock module under vendor

related to https://github.com/nerdvegas/rez/issues/665

Update: Hoping to be working on this soon, we need the same functionality at Method. Stay tuned.

So I'm freed up to work on this next week for Method. I think it would make sense to use this PR and https://github.com/nerdvegas/rez/pull/758 as a basis for that work, rather than updating these PRs though.
Reasons are:

I need to make immediate use of the time I'm getting from Method (rez dev time doesn't happen often!)
We need to make these changes with https://github.com/nerdvegas/rez/issues/665 in mind, so there will probably be some significant differences to these PRs.

Fede I wanted to let you know in case you thought I'm throwing this work away! Rest assured a chunk of the work is already done here and I'll be incorporating it into the upcoming PRs. Expect to see more next week.

Note that some of this PR has been superseded by https://github.com/nerdvegas/rez/pull/807. However, I'm still open to adding the dev mode functionality shown here, as long as there's consensus. It's not clear to me how this should work exactly - as mentioned above, the way the package is automatically re-installed if the tests definition changes, feels inconsistent.
Wrt --interactive, it definitely makes sense to do this, and I'm aiming to make this available in a separate PR which mimics the behaviour in this PR.

@nerdvegas @fnaum The way I see the dev mode is just to avoid some typing. So instead of doing rez-build -ci && rez-test packageA==x.x.x, you could just do rez-build -ci && rez-test .. It would make things simpler to use IMO. So it's just a "shorthand".

Yeah I don't mind that functionality, but in
https://github.com/nerdvegas/rez/pull/759 'dev mode' is not quite that
simple, as it does things like automatically re-install the package if its
tests change. I am not so sure about that, because it feels a bit arbitrary
as to whether a package is reinstalled (ie yes if tests change, no if
anything else changes).
In #759, test byproducts are also written to a specific directory when in
dev mode. So the question is also whether this should happen and if so,
what that path should be.
A
On Wed, Dec 4, 2019 at 2:58 PM Jean-Christophe Morin <
<EMAIL_ADDRESS>wrote:

@nerdvegas https://github.com/nerdvegas @fnaum
https://github.com/fnaum The way I see the dev mode is just to avoid
some typing. So instead of doing rez-build -ci && rez-test packageA==x.x.x,
you could just do rez-build -ci && rez-test .. It would make things
simpler to use IMO. So it's just a "shorthand".
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nerdvegas/rez/pull/759?email_source=notifications&email_token=AAMOUSVZUO6SGH3FUDLYKZ3QW4TIHA5CNFSM4I6XOR42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF3UWJA#issuecomment-561466148,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMOUSSJGRR7JWFQNGQ3RE3QW4TIHANCNFSM4I6XOR4Q
.

in #759 'dev mode' is not quite that
simple, as it does things like automatically re-install the package if its
tests change.

Yeah, I wouldn't go with the auto-install. Hence why I was giving rez-build -ci && rez-test . as an example. I'd almost prefer if the user was manually building (as he probably knows more what he needs to do for his tests to run then us).

In #759, test byproducts are also written to a specific directory when in
dev mode. So the question is also whether this should happen and if so,
what that path should be.

I still haven't made my mind on this. To be frank, the first time I reviewed this PR I didn't like the idea that rez would know where my tests artifacts are. And as of today I have the same feeling. You could have 5 different test target that each run different tools that will all generate tests artifacts in a different way (and sometimes if would even be impossible to choose where to put them). That means each test would have to define it's artifact directory. Though a possible case, it might not be a super common one. It would be easy to implement though. I think the hardest part will be to agree on how to handle that...


Add zombie types (Spitters, Vaulter, ...)

More concepts:

Hugger: runs towards the player while dropping bombs
Screamer: as long as it lives, it will cause all zombies to be in CHASE mode
Sprinter: fast, but deals little damage (causes chaos)


Fluency builder not supported

Time is not being added when we add a time value there in fluency builder !
Please fix it ! I already commented about that in the last issue !

What didn't you get in my last answer ?
If you can't use the provided bug template and precisely describe what your bug is, I won't even try to help you.
As I said, it works on my machine, so if it doesn't work on yours, I'm not gonna fix something if I don't know what it is.
I will keep closing your issue till you precisely and respectfully describe what your problem is using the provided template.
Remember that I am not the one affected by the issue, therefore, I don't really care whether you validate your due time or not.

yep you cant add time to fluency blender i tried with multiple accounts and with 2 devices and the problem is the same from a1 . a2 time getting added b1 b2 c1 c2 nope no time getting added

The developer fixed it ! Try again ! Maybe you didn't load the extension correctly.

yep you cant add time to fluency blender i tried with multiple accounts and with 2 devices and the problem is the same from a1 . a2 time getting added b1 b2 c1 c2 nope no time getting added

The developer fixed it ! Try again ! Maybe you didn't load the extension correctly.

it was working perfectly but i dont think it work anymore for more than b1


Bulkdata download from sunlight foundation error

I get the below error when trying to download bulkdata from the table on https://github.com/unitedstates/congress/wiki.

It seems ProPublica only has the XML available for bulk download. Is there another source for bulk JSON download or a way to use the existing sunlight foundation links?

The Sunlight Foundation is unfortunately long gone (the organization doesn't exist anymore). @dwillis would know if there is alternative ProPublica data.

Can you share more about this information you wish to download?
The Government Publishing Office has some of this data published in bulk:
https://www.govinfo.gov/developers
On Thu, Jun 13, 2024 at 11:20 AM Joshua Tauberer @.***>
wrote:

The Sunlight Foundation is unfortunately long gone (the organization
doesn't exist anymore). @dwillis https://github.com/dwillis would know
if there is alternative ProPublica data.
—
Reply to this email directly, view it on GitHub
https://github.com/unitedstates/congress/issues/306#issuecomment-2165987989,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWRVUEGPM3YP3XXOARMFO3ZHG2EJAVCNFSM6AAAAABJINIXPSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRVHE4DOOJYHE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hey @DanielSchuman sorry for the delayed reply.
I was hoping for JSON formatted bulk data but can do the xml to json conversion locally as well.


Can't create a new theme

Hello, I have a problem with creating a new theme :
$ hugo new theme sometext
Error: Unable to locate Config file. Perhaps you need to create a new site.
       Run `hugo help new` for details. (Unsupported Config Type "")

I'm using the latest version (0.17), installed using Homebrew on macOS. I tried to create a new theme using hugo installed from source but I got the same problem.
I attach a screenshot in case...

How you can see I am able to create a new site but not a new theme.

hugo new site someOtherText
cd someOtherText
hugo new theme someText

@cafe4it Thank you it works, I'm feel so dumb


Circular dependencies

In v0.8.0 it seems that django-simple-deploy depends on the 3 dsd- plugins but the 3 dsd- plugin also depends on django-simple-deploy. Seems like this is circular, and that django-simple-deploy should only optionally depend on the 3 dsd- plugins.

With this circular dependency we would indeed not be able to distribute either django-simple-deploy 0.8.0 nor any of the dsd plugins. The reason being 0.8.0 depends on the 3 (new) dsd plugins, which we would have to bring on board to conda forge first, but we will not be able to do so because they depend on django-simple-deploy 0.8.0, which depends on the 3 dsd plugins... and so forth.

Broadly speaking, it seems to be if the 3 dsd- plugins is never intended to be installed without django-simple-deploy, and also that the newest version of django-simple-deploy should always be installed with the 3 dsd- plugins, then they should be bundled in the same library.

In my experience, in other python libraries the pattern would be to make the plugins as optional dependencies, and raise an exception with hint text when the user tries to access parts of django-simple-deploy that requires the plugins to install them if they haven't already. An example of this would be pandas, which a very popular data science package, which has an optional dependency on xlrd, which allows it to interact with MS Excel files. It is an optional dependency not installed in the base installation. If the user try to use pandas to open an excel file, an exception is raised with the error text telling the user to install xlrd.

Thanks, that's helpful. The plugins really need to be separate from the main package, because they need to be maintained on a separate timeline from the main package.
I may make them optional, and report to the user if the required one is not installed. But I really prefer making the project work in the default way just from installing django-simple-deploy.
One other approach I'm considering is to require these three plugins, but remove the django-simple-deploy requirement for each of the plugins. Non-default plugins would be free to require django-simple-deploy.
Do you think that would resolve packaging issues on your end? Also, do you have any sense of how often people are using conda to install Django? I have used condo occasionally, but not for quite some time.

Thanks, either option should work. According to the conda-forge repo, so far django-simple-deploy had a little under 35k downloads: https://anaconda.org/conda-forge/django-simple-deploy

Thanks, that's really helpful to know. I'm considering one other approach, and that's distinguishing requirements from dependencies. I think I'm going to try to set up conda forge locally and see if it builds locally before pushing an update.

Hi again. I think this should work with 0.8.1. The core package no longer requires plugins.
I also set up a VM to re-render, so if there are still issues I should be more helpful in troubleshooting. I wasn't able to setup feedstocks for the plugins, but once they're set up I think I can rerender those locally to troubleshoot as needed.
Thanks for bringing this to my attention, and I'll let you close the issue when it's resolved.

Thanks @ehmatthes; 0.8.1 is now available on Conda. https://anaconda.org/conda-forge/django-simple-deploy
I will work to distribute the 3 plugins there as well.

This should be resolved now.

Thanks so much @ehmatthes !


Search Suggest API endpoint does not return user. Returns ElasticSearch search_phase_execution_exception

Affected module
API, UI
Describe the bug
When I try to conduct a suggest search via the API using /api/v1/search/suggest?q=admin&index=user_search_index, I am getting:
{
	"responseMessage": "An exception with message [Elasticsearch exception [type=search_phase_execution_exception, reason=all shards failed]] was thrown while processing request."
}

If I add team_search_index to the request /api/v1/search/suggest?q=admin&index=user_search_index,team_search_index, then I get:
{
	"suggest": {
		"metadata-suggest": [
			{
				"text": "admin",
				"offset": 0,
				"length": 5,
				"options": [
				]
			}
		]
	}
}

There are no results. I would expect there to be 1 result for the admin user that I see in the UI.
To Reproduce
Try an API call to /api/v1/search/suggest?q=admin&index=user_search_index
Try an API call to /api/v1/search/suggest?q=admin&index=user_search_index,team_search_index
Expected behavior
Admin user is returned by the API call.
Version:

OS: OS X
Python version:
OpenMetadata version: 0.12.2
OpenMetadata Ingestion package version: [e.g. openmetadata-ingestion[docker]==XYZ]

Additional context

Issue is fixed in 0.13.0


Wallet field is missing from button edit.

Also:

Change Addresses to Addresses* to match the Name* field label. Maybe do this for Wallet too even though it forces you to enter something w/ the dropdown.

Change "Wallet" to "Wallet*" on create & edit button form.

We didn't put this up yet because addresses are the one that belong to a wallet, not buttons. So changing the wallet of a button would more be like changing the wallet of each one of its addresses (which could also be done separately) and current is managed on the Wallet page
So, the possible behaviors I see are:

Drop down on the edit button form:
This would change the wallet of all of the buttons addresses, even if they also belong to other paybuttons, which can
be counterintuitive to users and it's less granular than we in fact allow

Separate menu to edit each address' wallet:
This would allow for the granularity, but it requires some other interface as e.g. a pencil next to each address on the Button Detail view


Links to GO are not formatted well

The GO: prefix is missing in the identifiers, this also causes the links to be incorrect, e.g. https://bioregistry.io/0001732.

there are some spaces missing in the text here


Upgrade Cassandra version to 2.1.10

Update Cassandra version from 2.0.16 to 2.1.10
Update Cassandra package installation (due to 404 trying to download archive.apache.org).
Update parser in cassandra_stress benchmark. The metric name is also changed.
Update config files. (cassandra.yaml, cassandra-env.sh)

Could you fix the lint error?

PTAL, @cmccoy

LGTM. Thanks.


Lpg work

Coverage increased (+7.0%) to 56.522% when pulling b12862d07a307c631d4d4b39a68cb60d00e5e69b on lpg_work into 9261cc466d115f65e7e10a840912705ba4b89380 on master.


Timing scaden train on cpu vs gpu

I am running scaden train on a cluster node with a Tesla V100 GPU, but (on casual observation) I don't see a time difference in the training when the GPU is enabled or disabled.
I do get the following message when the GPU is disabled, so it looks like scaden can "see" the GPU ? I have tensorflow-gpu installed.

INFO     Training M256 Model ...                                                                          train.py:54
2021-07-02 15:14:22.035782: E tensorflow/stream_executor/cuda/cuda_driver.cc:328] failed call to cuInit: CUDA_ERROR_NO_DEVICE: no CUDA-capable device is detected

Is there a way to check if the GPU is being used by scaden ? And at a practical level, is it just simpler to let scaden train run on a 40 core CPU than getting the GPU part to work ?

Hi @nagendraKU ,
it looks like there is some issue with the CUDA installation and it somehow can't connect to it. That can happen for various reasons - hard to tell from here!
But from a practical aspect, yes you're right :) I think you'll be just fine with your 40 core CPU, training should not take too long anyway. So in that case it might not be worth the effort to get the GPU running. It's not a huge model!
Cheers,
Kevin

Thanks for the input Kevin !


Material 3 Slider goes out of draggable state prematurely in some cases

Describe the bug
In some cases (see example below) I have the following slider behavior:

I press on slider track and start dragging
slider calls onValueChange 1-3 times
slider calls onValueChangeFinished (when mouse button is still pressed)
slider becomes unresponsible until I release a mouse button

Affected platforms

Desktop

Versions

Kotlin version: 1.9.22
Compose Multiplatform version: 1.6.0-rc03
OS version: Windows 11 Pro 23H2 22631.3155
OS architecture: x86
JDK: corretto-17.0.9

To Reproduce
import androidx.compose.material3.Slider
import androidx.compose.runtime.collectAsState
import androidx.compose.runtime.getValue
import androidx.compose.ui.window.Window
import androidx.compose.ui.window.application
import kotlinx.coroutines.flow.MutableStateFlow

class Store(
    val value: MutableStateFlow<Float> = MutableStateFlow(0.5f)
) {
    fun progress(it: Float) {
        value.tryEmit(it)
        println(it)
    }
    fun finished() = println("finished")
}

fun main() {
    val store = Store()
    application {
        Window(::exitApplication) {
            val value by store.value.collectAsState()
            Slider(
                value = value,
                onValueChange = { store.progress(it) },
                onValueChangeFinished = { store.finished() }
            )
        }
    }
}

Run this and try to drag the slider.
Expected behavior
Slider should moves and doesn't go out of draggable state before I release the mouse button.
Additional context
Issue doesn't reproduce in Compose 1.5.12.
Looks like the issue was introduced in this commit - https://github.com/JetBrains/compose-multiplatform-core/commit/f88a09b71aefd631588dbfc7302bbdf66e4d6f4e#diff-407454b5953648c917a33db1d037c1f5f8279ec22e572db656dbd9479f6b129a, maybe because before this commit gestureEndAction was remembered in rememberUpdatedState {}.
I don't know exactly what is the problem, but if I inline the class all works fine:
val value: MutableStateFlow<Float> = MutableStateFlow(0.5f)
fun progress(it: Float) {
    value.tryEmit(it)
    println(it)
}
fun finished() = println("finished")

fun main() {
    application {
        Window(::exitApplication) {
            val value by value.collectAsState()
            Slider(
                value = value,
                onValueChange = { progress(it) },
                onValueChangeFinished = { finished() }
            )
        }
    }
}

Also remembering of onValueChangeFinished value resolves the problem as a workaround:
fun main() {
    val store = Store()
    application {
        Window(::exitApplication) {
            val value by store.value.collectAsState()
            val finished by remember { mutableStateOf(store::finished) }
            Slider(
                value = value,
                onValueChange = { store.progress(it) },
                onValueChangeFinished = finished
            )
        }
    }
}

Thanks! Yes this bug appears also on MacOS in Compose for Desktop 1.6.0-rc03.
With version 1.5.12 Slider works well.

It is reproducible on Android as well:
import android.os.Bundle
import androidx.activity.ComponentActivity
import androidx.activity.compose.setContent
import androidx.compose.material3.Slider
import androidx.compose.runtime.Composable
import androidx.compose.runtime.collectAsState
import androidx.compose.runtime.getValue
import kotlinx.coroutines.flow.MutableStateFlow

val store = Store()

class MainActivity : ComponentActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)

        setContent {
            Screen(store)
        }
    }
}

class Store(
    val value: MutableStateFlow<Float> = MutableStateFlow(0.5f)
) {
    fun progress(it: Float) {
        value.tryEmit(it)
        println(it)
    }
    fun finished() = println("finished")
}

@Composable
fun Screen(store: Store) {
    val value by store.value.collectAsState()
    Slider(
        value = value,
        onValueChange = { store.progress(it) },
        onValueChangeFinished = { store.finished() }
    )
}

A temporary workaround until we make a stable release - remember store:
    val currentStore by rememberUpdatedState(store)
    val value by store.value.collectAsState()
    Slider(
        value = value,
        onValueChange = { currentStore.progress(it) },
        onValueChangeFinished = { currentStore.finished() }
    )

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


Add json for multiple prior released packages from AFRL/Quantum groups

Thanks for submitting a pull request! Below are a few things you can do to help us more quickly review your changes.
Checklist
I have…

[ X] run the application locally (./scripts/serve) and verified that my changes behave as expected.
[ X] run the build process locally (./scripts/build) and make sure it builds correctly.
[X ] run the test suite (./scripts/test) and verified that all tests pass.
[X ] summarized below my changes and noted which issues (if any) this pull request fixes or addresses.
[ X] thoroughly outlined below the steps necessary to test my changes.
[ -] attached screenshots illustrating relevant behavior before and after my changes.
[ X] read, understand, and agree to the terms described in CONTRIBUTING.md.
[ -] added my name, email address, and copyright date to CONTRIBUTORS.md.

Summary of Changes
This pull request adds several json blocks for previously released/open-sourced code that was posted at @afrl-quantum.
Testing
To verify the changes proposed in this pull request, I used the ./scripts/serve script to ensure that the blocks were properly inserted into the aggregate code.json file.

Greetings, apologies for the delay in pulling these changes into code.mil. I reviewed these changesets and the only changes that need to be made to conform with version 2.0.0 of the code.gov code inventory schema is to add a usageType. In earlier versions of the spec these were boolean values which is how they are specified in these changesets. Please see https://github.com/GSA/code-gov-data/blob/master/schemas/schema-2.0.0.json
      "usageType": {
                "type": "string",
                "description": "A list of enumerated values which describes the usage permissions for the release: (1) openSource: Open source; (2) governmentWideReuse: Government-wide reuse; (3) exemptByLaw: The sharing of the source code is restricted by law or regulation, including—but not limited to—patent or intellectual property law, the Export Asset Regulations, the International Traffic in Arms Regulation, and the Federal laws and regulations governing classified information; (4) exemptByNationalSecurity: The sharing of the source code would create an identifiable risk to the detriment of national security, confidentiality of Government information, or individual privacy; (5) exemptByAgencySystem: The sharing of the source code would create an identifiable risk to the stability, security, or integrity of the agency’s systems or personnel, (6) exemptByAgencyMission: The sharing of the source code would create an identifiable risk to agency mission, programs, or operations; (7) exemptByCIO: The CIO believes it is in the national interest to exempt sharing the source code; (8) exemptByPolicyDate: The release was created prior to the M-16-21 policy (August 8, 2016)",
                "enum": [
                  "openSource",
                  "governmentWideReuse",
                  "exemptByLaw",
                  "exemptByNationalSecurity",
                  "exemptByAgencySystem",
                  "exemptByAgencyMission",
                  "exemptByCIO",
                  "exemptByPolicyDate"
                ],
                "additionalProperties": false
              },

It should be a relatively small change. I'll pull this in once completed.


Error installing Torch on Ubuntu 16.04

followed the instructions on the page and getting the following errors -
vatsal@vatsal-Inspiron-7559:~/torch$ ./install.sh
Prefix set to /home/vatsal/torch/install
Installing Lua version: LUAJIT21
/home/vatsal/anaconda2/lib/libreadline.so: undefined reference to tputs' /home/vatsal/anaconda2/lib/libreadline.so: undefined reference totgoto'
/home/vatsal/anaconda2/lib/libreadline.so: undefined reference to tgetflag' /home/vatsal/anaconda2/lib/libreadline.so: undefined reference toUP'
/home/vatsal/anaconda2/lib/libreadline.so: undefined reference to tgetent' /home/vatsal/anaconda2/lib/libreadline.so: undefined reference totgetnum'
/home/vatsal/anaconda2/lib/libreadline.so: undefined reference to PC' /home/vatsal/anaconda2/lib/libreadline.so: undefined reference totgetstr'
/home/vatsal/anaconda2/lib/libreadline.so: undefined reference to `BC'
collect2: error: ld returned 1 exit status
make[2]: *** [exe/luajit-rocks/luajit-2.1/luajit] Error 1
make[1]: *** [exe/luajit-rocks/luajit-2.1/CMakeFiles/luajit.dir/all] Error 2
make: *** [all] Error 2
./install.sh: line 82: /home/vatsal/torch/install/bin/luarocks: No such file or directory
Installing common Lua packages
./install.sh: line 86: /home/vatsal/torch/install/bin/luarocks: No such file or directory
I am running Ubuntu 16.04 with anaconda2. Please help!

I have exactly the same issue, with same specs...

I'd suggest changing this line: https://github.com/torch/distro/blob/master/install.sh#L35 from anaconda to anaconda2

I think that is not the problem because the error is not changed, @soumith

It seems like a problem with gcc-5.x. A possible hack is to add this into your CMakeLists.txt.
SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -D_FORCE_INLINES")

Taken from: https://groups.google.com/d/msg/torch7/aj6cIPABUOA/QW0aSr2YAwAJ

no, the problem in this case is that they have anaconda2's readline that is conflicting with torch.
To fix this, remove anaconda from $PATH and $LD_LIBRARY_PATH, install torch, then add it back.

I am facing a similar issue,tried changing anaconda to anaconda3 in install.sh and also tried by removing anaconda from $PATH and $LD_LIBRARY_PATH .nothing seems to work ,still getting the same error ,after googling for some time i found it can be fixed by linking readline.so to libncurses or libterinfo but i have no idea how to do it in this case.

though it works with sudo but here "http://torch.ch/docs/getting-started.html" its mentioned not to use sudo . luarocks does not work after installing with sudo

I was able to resolve this issue my temporarily removing libreadline.so.  Try this:
mv ~/anaconda2/lib/libreadline.so ~/libreadline.so
make clean
./clean.sh
./install.sh
mv ~/libreadline.so ~/anaconda2/lib/libreadline.so

Cleaning the build directory is the important part.  I believe if you modify the install.sh to replace anaconda with anaconda2 that will work too if you clean the build directory before attempting to install again.

Changing anaconda to anaconda2 in install.sh and cleaning the build directory did work. But now the installation gets stuck after the line  - MAGMA not found. Compiling without MAGMA support
Found Torch7 in /home/vatsal/torch/install
Looking for pthread.h
Looking for pthread.h - found
Looking for pthread_create
Looking for pthread_create - not found
Looking for pthread_create in pthreads
Looking for pthread_create in pthreads - not found
Looking for pthread_create in pthread
Looking for pthread_create in pthread - found
Found Threads: TRUE
Found CUDA: /usr/local/cuda (found suitable version "7.5", minimum required is "6.5")
Found gcc >=5 and CUDA <=7.5, adding workaround C++ flags
MAGMA not found. Compiling without MAGMA support
hangs

Any updates?

this is now fixed via commit https://github.com/torch/distro/commit/c0e51b98acbb54e6655343a57152b6e711ffdc2b

I amend this error with removing conda from $PATH and move the conda libreadline.so


add Indonesian language

I added some Indonesian language in the Readme file

Fix project images links in README.md

hi, the links to the lessons need to be fixed (the ones in the table) - add '../' as necessary to avoid 404s


vue question

I tested the vue example code at https://github.com/jerosoler/Drawflow/issues/34.
When dragging the output, there is a line to the far right.
How do I fix it?
Originally posted by @namjals in https://github.com/jerosoler/Drawflow/issues/34#issuecomment-779687583

https://github.com/jerosoler/Drawflow/issues/37


my map dosent work ?!

cant see claims and map not show <IP_ADDRESS>:8881
{
"EnableTileGeneration": true,
"EnableGameGeneration": true,
"EnableTopTribes": true,
"Host": "",
"Port": 8881,
"AlternativeURL": "",
"WWWDir": "./www",
"FetchRateInSeconds": 15,
"DatabaseConnections": [
{
"Name": "Default",
"URL": "localhost",
"Port": 6379,
"Password": "foobared"
},
{
"Name": "TerritoryDB",
"URL": "localhost",
"Port": 6379,
"Password": "foobared"
}
],
"GridSize": 1400000.0,
"ServersX": 3,
"ServersY": 3,
"GameSize": 4096,
"TileSize": 256,
"MaxZoom": 7,
"LandRadiusUE": 10000,
"WaterRadiusUE": 21000,
"CircleAlpha": 128,
"AtlasS3URL": "",
"AtlasS3Region": "",
"AtlasS3AccessID": "",
"AtlasS3SecretKey": "",
"AtlasS3BucketName": "",
"AtlasS3KeyPrefix": ""
}

You aren't supposed to if you aren't running the tool that inserts them!
On Fri, Mar 8, 2019 at 2:24 AM Anuls<EMAIL_ADDRESS>wrote:

cant see claims and map not show <IP_ADDRESS>:8881
{
"EnableTileGeneration": true,
"EnableGameGeneration": true,
"EnableTopTribes": true,
"Host": "",
"Port": 8881,
"AlternativeURL": "",
"WWWDir": "./www",
"FetchRateInSeconds": 15,
"DatabaseConnections": [
{
"Name": "Default",
"URL": "localhost",
"Port": 6379,
"Password": "foobared"
},
{
"Name": "TerritoryDB",
"URL": "localhost",
"Port": 6379,
"Password": "foobared"
}
],
"GridSize": 1400000.0,
"ServersX": 3,
"ServersY": 3,
"GameSize": 4096,
"TileSize": 256,
"MaxZoom": 7,
"LandRadiusUE": 10000,
"WaterRadiusUE": 21000,
"CircleAlpha": 128,
"AtlasS3URL": "",
"AtlasS3Region": "",
"AtlasS3AccessID": "",
"AtlasS3SecretKey": "",
"AtlasS3BucketName": "",
"AtlasS3KeyPrefix": ""
}
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/GrapeshotGames/AtlasTerritoryMap/issues/13#issuecomment-470846236,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ah5OQ5Qy911hmD-paFMspl8-vZQI4ta8ks5vUh5OgaJpZM4bk4Q8
.

ahh okeey but it dosent show up only top compernys

it looks like this http://<IP_ADDRESS>:8880/

ships also mis placed :(

Start over and follow instructions
On Sat, Mar 9, 2019 at 2:04 AM Anuls<EMAIL_ADDRESS>wrote:

ships also mis placed :(
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GrapeshotGames/AtlasTerritoryMap/issues/13#issuecomment-471156357,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ah5OQ4KfmLI-a-Op1vK3MEYP9xwIGpPEks5vU2sDgaJpZM4bk4Q8
.


Adding additional Elasticsearch Config options

This should give you access to more configuration options for the elastic search datasource. I think its possible that some things are still broken I will need to test some more. There will be no breaking changes to existsing elasticHosts config.
Things that still need to happen:

docs need to be updated
syntax hlighting needs to be updated
annotations endpoint needs to have similar config options

This is still a WIP there are still some things that need testing and additional work that needs to be done before this can land. I wanted to just get someone to check the direction on this and make sure it looks alright.
To make this work with annotations im thinking about adding a new function to https://github.com/bosun-monitor/annotate/blob/master/backend/backend.go that would have the following signature:
func NewCustomElastic(urls []elastic.ClientOptionFuncs, index string) (*Elastic, error) {

That would leave the existing api in place but also allow us to do something similar to what I stated above for the elastic configs. Additionally there wouldn't be any shared data structures outside the stuff in the elastic package.

Needs to be updated to match new system config format (toml)

@kylebrandt, just a heads up we need this feature urgently, so i will work on the 'toml' config format changes.


Initialize part of the process of creating a virtual control plane

What type of PR is this?
/kind feature

What does this PR do?
Initialize part of the process of creating a virtual control plane

Which issue(s) does this PR fix?

Fixes #421
Special notes for your reviewer:

Does this PR introduce a user-facing change?

/cc @duanmengkk @GreatLazyMan please help review

@cc @duanmengkk @GreatLazyMan

/lgtm
/approve


fix: enable torchembedding deepcopy

Goals:
This PR is related to #1131

After the modification
import torch
from docarray import BaseDocument
from docarray.typing.tensor.embedding.torch import TorchEmbedding

class Meow(BaseDocument):
    embedding : TorchEmbedding

a = Meow(embedding=torch.randn(42))
print(id(a.embedding), id(a.copy(deep=True).embedding))

output has no error
140248435632272<PHONE_NUMBER>36032

Can u add to test to check that it is actual deep copied and not shallow copy ?

Can you explain this fix briefly? It is not obvious to me why this is fixing it

Can you explain this fix briefly? It is not obvious to me why this is fixing it

The deepcopy error is thrown from here https://github.com/pytorch/pytorch/blob/master/torch/_tensor.py#L170, and line above is
new_tensor = self.new_empty([])
if type(new_tensor) is not type(self):

where type(new_tensor) is  <class 'torch.Tensor'> and
type(self) is <class 'docarray.typing.tensor.embedding.torch.TorchEmbedding'>.
So according to the error msg, I should implement new_empty() for the subclass, which means the new_tensor should also be a TorchEmbedding.

Can you explain this fix briefly? It is not obvious to me why this is fixing it

The deepcopy error is thrown from here https://github.com/pytorch/pytorch/blob/master/torch/_tensor.py#L170, and lines above are
new_tensor = self.new_empty([])
if type(new_tensor) is not type(self):

where type(new_tensor) is <class 'torch.Tensor'> and type(self) is <class 'docarray.typing.tensor.embedding.torch.TorchEmbedding'>.
So according to the error msg, I should implement new_empty() for the subclass, which means the new_tensor should also be a TorchEmbedding.

@AnneYang720  can u add this to the docstring of new_empty in your PR so that ppl who will read the code will understand the same ?