Unable to control devices over BLE - Failed to perform the action light/turn_on. 'NoneType' object has no attribute 'write_gatt_char'

Version of the integration
0.1.1
Device setup
H617C, H618A
Describe the bug
Device cannot be controlled via integration, outputs "AttributeError: 'NoneType' object has no attribute 'write_gatt_char'". Device is detected by HA and able to be added, but errors when a command is given.
Debug log

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 245, in handle_call_service
    response = await hass.services.async_call(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2802, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2845, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1007, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
        hass, entity, func, data, call.context
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1079, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/light/__init__.py", line 628, in async_handle_light_on_service
    await light.async_turn_on(**filter_turn_on_params(light, params))
  File "/config/custom_components/govee-ble-lights/light.py", line 277, in async_turn_on
    await client.write_gatt_char(UUID_CONTROL_CHARACTERISTIC, command, False)
          ^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'write_gatt_char'

Rombond's H617A BLE fork seems to have fixed this and reliably controls the H617C.
https://github.com/Rombond/h617a_govee_ble_lights


improve integration of cell / line magics

autocompletion
making sure they don't interfere with existing magics

Fixed the issue with cell numbers for %safety magic; probably won't add autocompletion b/c there's not a cookie-cutter way to do this for magics.


Fix OneDeploy --clean option for type zip

Fixing issue where --clean option would not work for type=zip.

@jvano


Issue on page /msa/progressive.html

Chapter 11.1.1
Second sentence: "priciples" instead of "principles".
Chapter 13.2.3
First paragraph, second sentence: "staes" instead of "states". Same sentence "dont" instead of "don't" or "do not".
Second paragraph, fourth sentence: "Uneavenly" instead of "Unevenly".
Chapter 14
First paragraph, second sentence: "soi" instead of "so".

Thanks! Corrected in 8a27be2


Add Maven Central badge

Using maven-badges. Unfortunately,

the style doesn't currently match GitHub's build status badge 😞
we don't currently have an umbrella artifact for all dependencies, i.e. locations-android, routes-ui-android, etc

Yeah, I was wondering too 🙂 I think either or works. Why not both? 😄


Does the order of search terms matter to the YouTube API?

e.g. if I can do:
"The Beatles Hey Jude"
vs
"Hey Jude The Beatles"
what should I be searching for?

They probably do, but I've been getting along just fine without knowing so why invent a problem.


Will it be possible to change accent colour in the theme based on the PC's accent colour?

By default, for accented buttons and other stuff, this theme uses the default windows 11 blue accent colour. This looks good for most cases, but when the background is not particularly blue in colour, it kinda looks weird. So will it be possible to implement accent colours that change based on the user's accent colour, for more consistency?

There's already #12 and #55 about this, but unfortunately it isn't easy to add accent color support.
Since this theme is based on PNG images, we would have to programmatically edit them to change their colors. You can find some hacking in #55, but that's still not perfect, and I don't really have time to work on it :((

Oh alright. Sorry I didn't really look into the other issues as much. Thanks for your reply!


Functional Requirements

How should I set this place so that he directly displays the total number of entries instead of 100+, I don't want to click once to display the total number of entries, this is too troublesome.

Hello @lzb-libra,
Thank you for your request, but we want to keep the current behavior the same.
Let me explain: DBeaver executes a separate query for counting the number of rows in the result set. Because of that:

It can result in performance degradation if always performed without the user's intention.
It can result in side effects if the source query contains invocations of non-pure procedures or functions
It can result in side effects if the source query is DML


FourInARow incorrectly returns null from Board.Copy(NSZone), which causes GKMinMaxStrategist to fail

In FourInARow, Board.Copy(NSZone) cannot return null.
If it returns null, the GKMinMaxStrategist does not properly evaluate potential moves.
To reproduce: add a static counter to Board.ScoreForPlayer and you will see that it is only called a single time.
If you rewrite Board.Copy(NSZone) to return a clone, it will be called dozens of times, similarly as to how it is called in Apple's version.
Partial solution: Board.Copy(NSZone) should return a clone of this, similar to Apple's :+1:

(__nonnull id)copyWithZone:(nullable NSZone *)zone {
AAPLBoard *copy = [[[self class] allocWithZone:zone] init];
[copy setGameModel:self];
return copy;
}

Problem: When I did this, it appears that several AI moves are executed simultaneously.

Thanks for filling this issue @lobrien! Bug fixed in this commit d092559389b5eaf3f9a9d4a62b837d0d62dd40bc


Add SDK documentation for Microsoft.Testing.Platform

Internal previews

📄 File
🔗 Preview link

docs/core/testing/unit-testing-platform-sdk.md
Testing framework and extensions developers guide

@IEvangelist this is good to go
cc: @Evangelink

We can't have an article that is a single sentence with a link elsewhere. Instead, just add a TOC entry that links to the desired location.

Done @IEvangelist .


feat(listing): Owners Access Control Check #204

In Reference to #204
Please Review
@skhtet
@rkenyon1969
@akonsowski

:+1:

:+1:


Updating issue?

If I update my ServiceWorker script the new version will be installed in the background. My new precache items will end up in shed-/-1, but this is the same version the current version is using. Introducing a cache update before a ServiceWorker update may break stuff.
A work around would be to put the version number in indexedDB and bump it by one each time the install event gets called.

I think this is fixed now.


[fix] Replace deprecated CONST with valid version.

Replace CONST.DOCUMENT_PERMISSION_LEVELS.OBSERVER (deprecated in Foundry V10 and removed in V12) with CONST.DOCUMENT_OWNERSHIP_LEVELS.OBSERVER;

Thanks for the fix. I haven't had time to do a maintenance update on this module for v12 yet.


Update documentation for R.call and R.pair

Fixes #1550.

Also, maybe tests should be added for examples in the documentation? The R.call example slipped through the cracks, yet it could have been caught with a test.

:herb: Thank you.


The results of the experiment could not be reproduced

Thank you for your excellent work, I can't achieve the effect in your paper in the process of reproducing the compression of the swin-transformer model, in detail, I use the swin model you defined to train the teacher model on my own dataset, but the accuracy has not been up, in addition, I also use my own teacher model to distill directly, the accuracy can not go up, what is going on? Thank you very much!

Do you use your own teacher model for distillation? or do you have to use the swin-transformer base model generated by your code to train on the dataset and then distill it as a teacher model?Thank you very much!


v3.0 Roadmap

If there are proposed changes that you would like to see introduced in xmake v3.0, you can submit them here.
It will be adopted if the vote result >= 80%.
we can use set_policy("compatibility.version", "3.0") or xmake f --policies=compatibility.version:3.0 to attempt v3.0
Roadmap (Adopted)

[x] Use MD/MDd runtimes for msvc by default

Poll: https://github.com/xmake-io/xmake/discussions/5526

[x] Use ninja generator for cmake package by default

Poll: https://github.com/xmake-io/xmake/discussions/5545

[x] Simplifying add_requires with configs

https://github.com/xmake-io/xmake/issues/5727#issuecomment-2421040107

Roadmap (Draft)

[ ] Remove support for built-in variables in script scope, support it only in the description

Poll: https://github.com/xmake-io/xmake/discussions/5529

[ ] Rename buildir to builddir

Poll: https://github.com/xmake-io/xmake/discussions/5533
https://github.com/xmake-io/xmake/issues/5596

[ ] Improve custom toolchain to support unknown compiler/linker.

https://github.com/xmake-io/xmake/issues/5554

[ ] Support project namespace

https://github.com/xmake-io/xmake/issues/3380

[ ] Autobuild when calling xmake run

Poll: https://github.com/xmake-io/xmake/discussions/5624

[ ] ...

Support dynamical script load, so we can distribute some xmake scripts by packages. This would be useful when sharing some scripts between projects.

A better way for xmake packages to pull off info from their build xmake.lua, to avoid having to duplicate defines and such

I think it is very important to improve the documentation, now the documentation of a few more serious problems
1  Even if I select Chinese in xmake.io, the search still comes up with English results
2  Some methods are not found in the documentation

支持对apt，pkg-config等系统库指定使用动态库或静态库

I think it is very important to improve the documentation, now the documentation of a few more serious problems 1 Even if I select Chinese in xmake.io, the search still comes up with English results 2 Some methods are not found in the documentation

new document, https://docs.xmake.io/en-us/index.html
But I don't have a lot of time alone to update and perfect it.

Maybe we can use document generators like LDoc and embed the document into annotations.

A way to reuse rules already included in a project that uses xmake, but in a package definition.
https://github.com/shad0wshayd3-FO4/CommonLibF4/blob/master/CommonLibF4/xmake.lua#L133

Rename buildir to builddir

Rename buildir to builddir

https://github.com/xmake-io/xmake/discussions/5533

For my project xmake-rs, I wanted xmake to send the resolved list of a target's links to the rust part. This way the user wouldn't need to link anything in the build.rs.
To do this, I had to copy a large part of the xmake source code, my idea would be to add a target:orderlinks() function which would return a resolved list of links on a binary target.
I thought about using target:linkcmd(), but the flags are different for different compilers and you'd have to parse them.

Use ninja generator for cmake package by default.

Use ninja generator for cmake package by default.

Poll: https://github.com/xmake-io/xmake/discussions/5545

Add a way to really clean everything. Sometimes, I need to delete .xmake directories (and/or build directory) in order to fix a build that should work. A nice command like xmake mrproper would be nice to delete everything, as if it was a fresh installation of xmake (like on a CI).

Add a way to really clean everything. Sometimes, I need to delete .xmake directories (and/or build directory) in order to fix a build that should work. A nice command like xmake mrproper would be nice to delete everything, as if it was a fresh installation of xmake (like on a CI).

xmake f -c will ignore all configuration cache.

A way to change config without having to respecify all config, maybe separate some configs such as mode from other configs. It's quite painful to work with a lot of config because of that.

希望option域里面 能够支持 add_rules 接口

希望定义option时可以直接指定default值，而不用这样再包一层 https://github.com/xmake-io/xmake-repo/blob/dev/packages/a/angle/port/6288/xmake.lua

希望定义option时可以直接指定default值，而不用这样再包一层 https://github.com/xmake-io/xmake-repo/blob/dev/packages/a/angle/port/6288/xmake.lua

原本就可以直接指定，这里的问题是你用了 is_plat ，想要在 option 里用，只能在脚本域。这个是本身机制决定的，没法在描述域实现

跑测试的时候，是否有必要把所有的config也测试到呢？
比如下面的pr，其实是测试不到新添加的config的
https://github.com/xmake-io/xmake-repo/pull/5115

跑测试的时候，是否有必要把所有的config也测试到呢？ 比如下面的pr，其实是测试不到新添加的config的 xmake-io/xmake-repo#5115
或者说写包描述的时候可以给config添加一个字段指定是否对这个config进行自动测试

这个不太现实，新增一个config ，排列组合下，ci 的测试 job 是数量级暴增的，没这么多资源，不仅耗时，耗ci资源，跑出问题，也没这么多人力修。

vote for Rename buildir to builddir #5533 and Improve custom toolchain to support unknown compiler/linker #5554

是否考虑增加has_option/get_option相关针对option的独立api。把option和config的获取分开
现在其实是用一个has_config/get_config来获取option包括config的值，很容易有歧义，下意识去搜索option相关的api也找不到
群友也有遇到同样问题

是否考虑增加has_option/get_option相关针对option的独立api。把option和config的获取分开 现在其实是用一个has_config/get_config来获取option包括config的值，很容易有歧义，下意识去搜索option相关的api也找不到 群友也有遇到同样问题

option 就是为 config 服务的，改不了。

c51和sdcc工具链的默认plat不要设为当前系统，建议为裸机（没有系统的单片机，自立实现）添加名为bare或者standalone的目标平台plat属性值。c51工具链的默认架构arch建议也弄成mcs51，不然下面的日志太难绷：
> xmake config --clean
checking for platform ... windows
checking for architecture ... x64
checking for Microsoft Visual Studio (x64) version ... 2022
checking for Microsoft C/C++ Compiler (x64) version ... 19.40.33811
> xmake build --rebuild
[ 50%]: cache compiling.release src\main.c
[ 75%]: linking.release hello
[ 75%]: generating.release build\windows\x64\release\hello.hex
[100%]: build ok, spent 0.125s

c51和sdcc工具链的默认plat不要设为当前系统，建议为裸机（没有系统的单片机，自立实现）添加名为bare或者standalone的目标平台plat属性值。c51工具链的默认架构arch建议也弄成mcs51，不然下面的日志太难绷：
> xmake config --clean
checking for platform ... windows
checking for architecture ... x64
checking for Microsoft Visual Studio (x64) version ... 2022
checking for Microsoft C/C++ Compiler (x64) version ... 19.40.33811
> xmake build --rebuild
[ 50%]: cache compiling.release src\main.c
[ 75%]: linking.release hello
[ 75%]: generating.release build\windows\x64\release\hello.hex
[100%]: build ok, spent 0.125s

c51和sdcc工具链的默认plat不要设为当前系统，建议为裸机（没有系统的单片机，自立实现）添加名为bare或者standalone的目标平台plat属性值。c51工具链的默认架构arch建议也弄成mcs51，不然下面的日志太难绷：
> xmake config --clean
checking for platform ... windows
checking for architecture ... x64
checking for Microsoft Visual Studio (x64) version ... 2022
checking for Microsoft C/C++ Compiler (x64) version ... 19.40.33811
> xmake build --rebuild
[ 50%]: cache compiling.release src\main.c
[ 75%]: linking.release hello
[ 75%]: generating.release build\windows\x64\release\hello.hex
[100%]: build ok, spent 0.125s

这个无解，每个 target 可以绑定多个不同 toolchain 的，而全局平台 toolchain 只有一个，跟他们独立。
你走 set_toolchain 设置，仅仅只影响 target toolchain ，不会影响 platform toolchain ，也不应该去影响它。

而全局平台 toolchain 只有一个，跟他们独立。
你走 set_toolchain 设置，仅仅只影响 target toolchain ，不会影响 platform toolchain ，也不应该去影响它。

为什么全局的 toolchain 会和目标平台绑定？这个全局 toolchain 和 host 绑定可能更好吧

之前用xmake构建的时候老是通不过，最后发现是因为xmake会从PATH环境变量找到我添加的工具链，混用就出错了。
为了用xmake我都是把PATH环境里面的工具链去掉，这也导致命令行连个g++都没有，有时候想写点小东西，也必须xmake创建一个项目，就很繁琐。
是否可以给全局设置里面添加一个功能让xmake忽略指定路径下的工具链，即使他在PATH环境变量里。

而全局平台 toolchain 只有一个，跟他们独立。
你走 set_toolchain 设置，仅仅只影响 target toolchain ，不会影响 platform toolchain ，也不应该去影响它。

为什么全局的 toolchain 会和_目标平台_绑定？这个全局 toolchain 和 host 绑定可能更好吧

如果这样， xmake f -p mingw 也会用 msvc 编译

之前用xmake构建的时候老是通不过，最后发现是因为xmake会从PATH环境变量找到我添加的工具链，混用就出错了。 为了用xmake我都是把PATH环境里面的工具链去掉，这也导致命令行连个g++都没有，有时候想写点小东西，也必须xmake创建一个项目，就很繁琐。 是否可以给全局设置里面添加一个功能让xmake忽略指定路径下的工具链，即使他在PATH环境变量里。

不从 path 里找，从哪找。而且也不是所有 toolchain 都从 PATH 找，如果有问题，可以提 issues

之前用xmake构建的时候老是通不过，最后发现是因为xmake会从PATH环境变量找到我添加的工具链，混用就出错了。 为了用xmake我都是把PATH环境里面的工具链去掉，这也导致命令行连个g++都没有，有时候想写点小东西，也必须xmake创建一个项目，就很繁琐。 是否可以给全局设置里面添加一个功能让xmake忽略指定路径下的工具链，即使他在PATH环境变量里。

不从 path 里找，从哪找。而且也不是所有 toolchain 都从 PATH 找，如果有问题，可以提 issues

可以从PATH里找，但是希望能有个exclude列表可以排除掉指定的目录

可以从PATH里找，但是希望能有个exclude列表可以排除掉指定的目录，xmake分析PATH的时候遇到这个目录就跳过 之前提过issue，是因为我把msys2的bin加到windows的PATH环境里面。最后是去掉解决的（用下来，只对xmake有影响，没有其他问题，而且有些情况最好得加，有几个大型程序是在msys2里面编译出来的，我单独拿出来用，如果不加msys2的bin到环境变量里面跑不起来，除非把所有依赖单独再复制一份出来）
还有就是想在win命令行下用msys2下的工具，但是加了bin，又会影响xmake编译程序

这种情况推荐是用虚拟环境 https://github.com/xmake-io/xmake/issues/5580 跑xmake的时候开虚拟环境把自己的toolchain放在系统gcc前面

可以从PATH里找，但是希望能有个exclude列表可以排除掉指定的目录，xmake分析PATH的时候遇到这个目录就跳过 之前提过issue，是因为我把msys2的bin加到windows的PATH环境里面。最后是去掉解决的（用下来，只对xmake有影响，没有其他问题，而且有些情况最好得加，有几个大型程序是在msys2里面编译出来的，我单独拿出来用，如果不加msys2的bin到环境变量里面跑不起来，除非把所有依赖单独再复制一份出来）
还有就是想在win命令行下用msys2下的工具，但是加了bin，又会影响xmake编译程序

这种情况推荐是用虚拟环境 #5580 跑xmake的时候开虚拟环境把自己的toolchain放在系统gcc前面

可以解决，不过这样的话，每个项目都得设置一遍环境变量，略繁琐，本身我是明确了不需要xmake使用特定路径下的工具链

可以解决，不过这样的话，每个项目都得设置一遍环境变量，略繁琐，本身我是明确了不需要xmake使用特定路径下的工具链

每个项目都用不同的toolchain吗？一般有一两个全局虚拟环境就可以了吧

可以解决，不过这样的话，每个项目都得设置一遍环境变量，略繁琐，本身我是明确了不需要xmake使用特定路径下的工具链

每个项目都用不同的toolchain吗？一般有一两个全局虚拟环境就可以了吧

现在是这样，
1 PATH里面只有msys2中bin的环境变量
2 如果用xmake使用msvc去编译项目，他会混合使用到msys2中的库(好像是这种情况，反正是混合了不同工具链的库，之前issue提过，但是找不到了，最后就是去掉msys2的库才正常)
我现在是希望xmake不管我在环境变量中加的这个msys2中的库

可以解决，不过这样的话，每个项目都得设置一遍环境变量，略繁琐，本身我是明确了不需要xmake使用特定路径下的工具链

每个项目都用不同的toolchain吗？一般有一两个全局虚拟环境就可以了吧

现在是这样， 1 PATH里面只有msys2中bin的环境变量 2 如果用xmake使用msvc去编译项目，他会混合使用到msys2中的库(好像是这种情况，反正是混合了不同工具链的库，之前issue提过，但是找不到了，最后就是去掉msys2的库才正常)
我现在是希望xmake不管我在环境变量中加的这个msys2中的库

这个很奇怪啊，msys2的库名字是xxx.dll.a，msvc是.lib，格式都不一样不应该链接上的，除非用了msys2 gfortran之类工具；这种情况把自己的flang/intel fortran放gfortran前面也能解决问题。感觉根本问题不在环境变量，在xmake找系统toolchain/library的机制

可以解决，不过这样的话，每个项目都得设置一遍环境变量，略繁琐，本身我是明确了不需要xmake使用特定路径下的工具链

每个项目都用不同的toolchain吗？一般有一两个全局虚拟环境就可以了吧

现在是这样， 1 PATH里面只有msys2中bin的环境变量 2 如果用xmake使用msvc去编译项目，他会混合使用到msys2中的库(好像是这种情况，反正是混合了不同工具链的库，之前issue提过，但是找不到了，最后就是去掉msys2的库才正常)
我现在是希望xmake不管我在环境变量中加的这个msys2中的库

这个很奇怪啊，msys2的库名字是xxx.dll.a，msvc是.lib，格式都不一样不应该链接上的，除非用了msys2 gfortran之类工具；这种情况把自己的flang/intel fortran放gfortran前面也能解决问题。感觉根本问题不在环境变量，在xmake找系统toolchain/library的机制

找到了，是这个issue
https://github.com/xmake-io/xmake/issues/4479

Found it, it’s this issue #4479

但 xmake 无法通过 pkg-config 去判断返回的库是 gnulib 还是 mslib 格式，只能假定都可使用。

这个是可以判断的，parse完linkdir之后 https://github.com/xmake-io/xmake/blob/dev/xmake/modules/package/manager/pkgconfig/find_package.lua#L88-L89 这里区分一下后缀名.a/.lib就行了。尽管这里msys2的zlib msvc也能用，但混用mingw格式包的这种行为还是默认禁用为好，实在要用可以加一个policy 控制 是否对msvc启用mingw格式的包

可以新开一个issue

https://github.com/xmake-io/xmake/issues/5609

#5609

支持，现在的musl.cc工具链只能从linux上跨平台/架构编译。这个工具链能大大扩展交叉编译的能力

We can use set_policy("compatibility.version", "3.0") or xmake f --policies=compatibility.version:3.0 to attempt v3.0
https://github.com/xmake-io/xmake/commit/f9196dfa7073e3c3511230072d606c89f28a075d

New Poll: Autobuild when calling xmake run
https://github.com/xmake-io/xmake/discussions/5624

Now we can use set_policy("compatibility.version", "3.0") to switch vs runtime to MD/Md
https://github.com/xmake-io/xmake/pull/5625

我需要一个接口来遍历我的项目依赖的三方库的列表，我需要将三方库的二进制打包到我的安装包中。
我现在的做法是在脚本域中使用以下代码来获取三方库的二进制的：
        import("core.project.project")
        cprint("${yellow}Export Shared libs")
        for pkg_name, info in pairs(project:required_packages()) do
            local libfiles = info:get("libfiles")
        end

但是这只能获取到三方库的库文件，对于一些拥有插件或者工具的三方库，例如gstreamer、ffmpeg、qt，我需要用到他们的工具和插件，并将其打包到安装包中。目前我没有办法做到直接从xmake的脚本域中找到它们
能否提供一个函数例如project:all_packages(),target:all_packages()来获取到他们的manifest信息？
又或者为package的包管理中添加一个on_export_runtime()，可以用于一键导出三方库的运行时？

我需要一个接口来遍历我的项目依赖的三方库的列表，我需要将三方库的二进制打包到我的安装包中。 我现在的做法是在脚本域中使用以下代码来获取三方库的二进制的：
        import("core.project.project")
        cprint("${yellow}Export Shared libs")
        for pkg_name, info in pairs(project:required_packages()) do
            local libfiles = info:get("libfiles")
        end

但是这只能获取到三方库的库文件，对于一些拥有插件或者工具的三方库，例如gstreamer、ffmpeg、qt，我需要用到他们的工具和插件，并将其打包到安装包中。目前我没有办法做到直接从xmake的脚本域中找到它们 能否提供一个函数例如project:all_packages(),target:all_packages()来获取到他们的manifest信息？
又或者为package的包管理中添加一个on_export_runtime()，可以用于一键导出三方库的运行时？

这种问题，没必要在这里问，可以到 discussion 里提，target:pkgs() ，pkg:installdir()  原本就能取到。

A way to change config without having to respecify all config, maybe separate some configs such as mode from other configs. It's quite painful to work with a lot of config because of that.

I also want it, something like a file xmake.lua.user, and xmake build will check it if change, auto config with it.

c51和sdcc工具链的默认plat不要设为当前系统，建议为裸机（没有系统的单片机，自立实现）添加名为bare或者standalone的目标平台plat属性值。c51工具链的默认架构arch建议也弄成mcs51，不然下面的日志太难绷：
> xmake config --clean
checking for platform ... windows
checking for architecture ... x64
checking for Microsoft Visual Studio (x64) version ... 2022
checking for Microsoft C/C++ Compiler (x64) version ... 19.40.33811
> xmake build --rebuild
[ 50%]: cache compiling.release src\main.c
[ 75%]: linking.release hello
[ 75%]: generating.release build\windows\x64\release\hello.hex
[100%]: build ok, spent 0.125s

这个无解，每个 target 可以绑定多个不同 toolchain 的，而全局平台 toolchain 只有一个，跟他们独立。

那xmake-repo里的包，如何适配c51或者sdcc工具链，同时不影响默认工具链的编译？

c51和sdcc工具链的默认plat不要设为当前系统，建议为裸机（没有系统的单片机，自立实现）添加名为bare或者standalone的目标平台plat属性值。c51工具链的默认架构arch建议也弄成mcs51，不然下面的日志太难绷：
> xmake config --clean
checking for platform ... windows
checking for architecture ... x64
checking for Microsoft Visual Studio (x64) version ... 2022
checking for Microsoft C/C++ Compiler (x64) version ... 19.40.33811
> xmake build --rebuild
[ 50%]: cache compiling.release src\main.c
[ 75%]: linking.release hello
[ 75%]: generating.release build\windows\x64\release\hello.hex
[100%]: build ok, spent 0.125s

这个无解，每个 target 可以绑定多个不同 toolchain 的，而全局平台 toolchain 只有一个，跟他们独立。

那xmake-repo里的包，如何适配c51或者sdcc工具链，同时不影响默认工具链的编译？

add_requires("xxx", {configs = {toolchains = ""}}) 也是可以设置 toolchain 的

How would you feel about having add_requires("xx", { configs = { foo = "bar" } }) automatically add add_requireconfs("**.xx", { configs = { foo = "bar" }})? Also add_requires("libsdl 2.30") => add_requireconfs("**.libsdl", { version = "2.30" }}).
This way, package config and versions would automatically replicate to their dependencies as well, because currently:
add_requires("libsdl 2.28", "libsdl_ttf")

will make xmake install this:
$ xmake f --check
checking for Microsoft Visual Studio (x64) version ... 2022
note: install or modify (m) these packages (pass -y to skip confirm)?
in xmake-repo:
  -> libsdl 2.28.5 [runtimes:"MD"]
  -> libsdl#1 2.30.8 [runtimes:"MD", from:libsdl_ttf]
  -> libsdl_ttf 2.22.0 [runtimes:"MD"]
please input: y (y/n/m)

same goes for
add_requires("libsdl", { configs = {sdlmain = false}})
add_requires("libsdl_ttf")

=>
in xmake-repo:
  -> libsdl 2.30.8 [runtimes:"MT", sdlmain:n]
  -> libsdl#1 2.30.8 [runtimes:"MT", from:libsdl_ttf]
  -> libsdl_ttf 2.22.0 [runtimes:"MD"]
please input: y (y/n/m)

it's been a long time I've been thinking about making a feature request for a policy for this, and I think it would be a great default to have that in xmake 3.0.
what do you think?
(also thinking about it, package.librarydeps.strict_compatibility would be great to enable by default in that case, to avoid subtles bugs when you change your mind about a package config also used as a dependency)

How would you feel about having add_requires("xx", { configs = { foo = "bar" } }) automatically add add_requireconfs("**.xx", { configs = { foo = "bar" }})? Also add_requires("libsdl 2.30") => add_requireconfs("**.libsdl", { version = "2.30" }}).
This way, package config and versions would automatically replicate to their dependencies as well, because currently:
add_requires("libsdl 2.28", "libsdl_ttf")

will make xmake install this:
$ xmake f --check
checking for Microsoft Visual Studio (x64) version ... 2022
note: install or modify (m) these packages (pass -y to skip confirm)?
in xmake-repo:
  -> libsdl 2.28.5 [runtimes:"MD"]
  -> libsdl#1 2.30.8 [runtimes:"MD", from:libsdl_ttf]
  -> libsdl_ttf 2.22.0 [runtimes:"MD"]
please input: y (y/n/m)

same goes for
add_requires("libsdl", { configs = {sdlmain = false}})
add_requires("libsdl_ttf")

=>
in xmake-repo:
  -> libsdl 2.30.8 [runtimes:"MD", sdlmain:n]
  -> libsdl#1 2.30.8 [runtimes:"MD", from:libsdl_ttf]
  -> libsdl_ttf 2.22.0 [runtimes:"MD"]
please input: y (y/n/m)

it's been a long time I've been thinking about making a feature request for a policy for this, and I think it would be a great default to have that in xmake 3.0.
what do you think?
(also thinking about it, package.librarydeps.strict_compatibility would be great to enable by default in that case, to avoid subtles bugs when you change your mind about a package config also used as a dependency)

The add_requires at the user's top level are completely independent. They should not affect the dependency configurations of other packages, as this can lead to many hidden problems.

The add_requires at the user's top level are completely independent. They should not affect the dependency configurations of other packages, as this can lead to many hidden problems.

But in the examples I'm showing this is already causing many issues, if you decide to use libsdl as a shared library, libsdl_ttf will use it as a static library causing bugs (libsdl uses global variables which would not be the same between libsdl and libsdl_ttf in that case).
Having that behavior as an opt-out seems safer to me

The add_requires at the user's top level are completely independent. They should not affect the dependency configurations of other packages, as this can lead to many hidden problems.

But in the examples I'm showing this is already causing many issues, if you decide to use libsdl as a shared library, libsdl_ttf will use it as a static library causing bugs (libsdl uses global variables which would not be the same between libsdl and libsdl_ttf in that case).

so we should use add_requireconfs

Another example would be openssl, if you use package locking for example and you're locking your openssl package version, it won't lock it as a dependency (and openssl is used by many packages).

This is just another issue about requires-lock. We can improve requires-lock instead of add_requires.

Your app cannot have two differents versions of openssl and it will error out on init.

However, two completely independent targets can be bound to different versions of OpenSSL. If their dependency behaviors are globally modified through add_requires, these unrelated targets will all be affected.

Having that behavior as an opt-out seems safer to me

In the future, I will try to improve and solve this problem, but not by modifying the default behavior of add_requires. Modifying it would lead to even more problems than now.

I understand even though I don't agree on the current behavior being safer than what I suggest (especially because it causes subtle bugs one can fix only with advanced xmake usage and knowing how libs depends on each other, my students fall in this trap every year).
(About package lock, the issue arise simply when you set a package version through add_requires, at best it duplicates symbols and at worst it causes weird bugs in your app)
How about having this behavior as an opt-in policy? Because even though we can already do this using add_requireconfs, it means duplicating every add_requires with a add_requireconfs which is redundant and more error-prone.

I haven't figured out how to improve and solve it yet. You can open an issue first.

A way to change config without having to respecify all config, maybe separate some configs such as mode from other configs. It's quite painful to work with a lot of config because of that.

这个+1，甚至希望xmake config的默认行为就是只修改而不要清除之前的config，类似于git config。并且如果真的需要覆盖已有config的话也可以先跑xmake config --clean再修改

Assuming target A depends on target B, the build.fence policy will cause the object files of target A to wait until target B is fully linked before compiling, resulting in no-full-usage of the CPU.
On the other hand, build.target_across_parallel leads to even lower CPU utilization. Will xmake 3.0.0 consider optimizing CPU utilization for codegen/proto targets? We have a log of codegen / proto tasks in our repo, so we're quite interested in this feature.

https://github.com/xmake-io/xmake/issues/4878
Hopefully 3.0 will support menu like menuconfig

Hopefully 3.0 will support menu like menuconfig

It's already supported with xmake config --menu

Hopefully 3.0 will support menu like menuconfig

It's already supported with xmake config --menu

no , see this https://github.com/xmake-io/xmake/issues/4878

Hopefully 3.0 will support menu like menuconfig

It's already supported with xmake config --menu

no , see this #4878

You didn't explain it clearly. It's a dependency issue of option, not menuconfig.

as version 3 come with breaking changes, isn't it an opportunity to remove experimental support for modules (-fmodules-ts for gcc and clang and /experimental:modules for cl) and only support compilers with official support ? (-fmodules for gcc, -std=c++20 for clang and /std:c++latest or /std:c++20 for cl)

as version 3 come with breaking changes, isn't it an opportunity to remove experimental support for modules (-fmodules-ts for gcc and clang and /experimental:modules for cl) and only support compilers with official support ? (-fmodules for gcc, -std=c++20 for clang and /std:c++latest or /std:c++20 for cl) old compilers experimental support is very broken, nobody will use them seriously in a project
or at least disable them by default when compatibility policy for 3.x is set ?

you can use compatibility.version policy to remove it.

Opinions on this?
https://github.com/xmake-io/xmake/discussions/5904

Talking about renaming things, how about renaming iphoneos platform to ios and macosx to macos?


Python: 1.9 Use cases of python

Description 📜
Added a Video link on different  uses of python in real world
Fixes #223

Type of change 📝

[x] Video (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)

Domain of Contribution 📊

[x] Python

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

/assign


Can't filter by taxon after redoing search in map area

Describe the bug
In Android, you cannot filter by taxon after redoing search in map area
To Reproduce
Steps to reproduce the behavior:

Go to Explore, observations view, map layout
Zoom into an area with some observations and redo search in map area; note that the number of observations changes
Filter by taxon (using the header or filters menu); try something high-level that will have some observations in the search area
Nothing happens; particularly note that the obs count doesn't change

Expected behavior
You should be able to apply any filter on top of another, especially taxon on top of bounding box, which is a pretty common use of Explore
Context (please complete the following information):

Device: Pixel 8
OS: Android 14
App version: 0.44.0

I do not see this issue in v0.57.0 (132). Maybe the recent fixes for Explore in Android have taken care of this.


fix: test api user arguments

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[x] N
[ ] Y

fix: test api user arguments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>3
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

16 of 18 (88.89%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.006%) to 70.533%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

kclvm/tools/src/testing/tests.rs
14
16
87.5%

Totals

Change from base Build<PHONE_NUMBER>6:
0.006%

Covered Lines:
50442

Relevant Lines:
71515

💛  - Coveralls


Encrypted zip not handled correctly

Exception in milter if a encrypted zip is send:
2018-01-15 14:59:30,754 -    DEBUG: [1574] Exeption code: [!! Traceback (most recent call last):
!!   File "/usr/bin/macromilter", line 282, in checkforVBA
    zipvba = self.getZipFiles(attachment, filename)
!!   File "/usr/bin/macromilter", line 334, in getZipFiles
    for zip_name, zip_data in files_in_zip:
!!   File "/usr/bin/macromilter", line 376, in zipwalk
    data = z.read(fname)
!!   File "/usr/lib64/python2.7/zipfile.py", line 931, in read
    return self.open(name, "r", pwd).read()
!!   File "/usr/lib64/python2.7/zipfile.py", line 986, in open
    "password required for extraction" % name
!! RuntimeError: File YUMI-<IP_ADDRESS>.exe is encrypted, password required for extraction
]

Possible solution:
for zinfo in zf.infolist():
    is_encrypted = zinfo.flag_bits & 0x1

P.S.: Typo >> Exeption = Exception

tested


CI: controller bpf-map-sync-cilium_lb_affinity_match is failing

Test Endpoint can still connect while Cilium is not running failed on test-gke:
11:54:38  18:54:37 STEP: Cilium is not ready yet: controllers are failing: cilium-agent 'cilium-d884n': controller bpf-map-sync-cilium_lb_affinity_match is failing: Exitcode: 0
11:54:38  Stdout:
11:54:38   	 KVStore:                Ok   Disabled
11:54:38  	 Kubernetes:             Ok   1.14+ (v1.14.10-gke.36) [linux/amd64]
11:54:38  	 Kubernetes APIs:        ["CustomResourceDefinition", "cilium/v2::CiliumClusterwideNetworkPolicy", "cilium/v2::CiliumEndpoint", "cilium/v2::CiliumNetworkPolicy", "cilium/v2::CiliumNode", "core/v1::Endpoint", "core/v1::Namespace", "core/v1::Node", "core/v1::Pods", "core/v1::Service", "networking.k8s.io/v1::NetworkPolicy"]
11:54:38  	 KubeProxyReplacement:   Probe   []   [SessionAffinity]
11:54:38  	 Cilium:                 Ok      OK
11:54:38  	 NodeMonitor:            Listening for events on 4 CPUs with 64x4096 of shared memory
11:54:38  	 Cilium health daemon:   Ok
11:54:38  	 IPAM:                   IPv4: 2/255 allocated from <IP_ADDRESS>/24,
11:54:38  	 Masquerading:           IPTables
11:54:38  	 Controller Status:      17/18 healthy
11:54:38  	   Name                                    Last success   Last error   Count   Message
11:54:38  	   bpf-map-sync-cilium_lb_affinity_match   never          15s ago      23      4 map sync errors
11:54:38  	   cilium-health-ep                        26s ago        never        0       no error
11:54:38  	   dns-garbage-collector-job               27s ago        never        0       no error
11:54:38  	   endpoint-1949-regeneration-recovery     never          never        0       no error
11:54:38  	   endpoint-827-regeneration-recovery      never          never        0       no error
11:54:38  	   k8s-heartbeat                           31s ago        never        0       no error
11:54:38  	   mark-k8s-node-as-available              4m27s ago      never        0       no error
11:54:38  	   metricsmap-bpf-prom-sync                6s ago         never        0       no error
11:54:38  	   resolve-identity-1949                   4m26s ago      never        0       no error
11:54:38  	   resolve-identity-827                    4m27s ago      never        0       no error
11:54:38  	   sync-endpoints-and-host-ips             27s ago        never        0       no error
11:54:38  	   sync-lb-maps-with-k8s-services          4m27s ago      never        0       no error
11:54:38  	   sync-policymap-1949                     25s ago        never        0       no error
11:54:38  	   sync-policymap-827                      26s ago        never        0       no error
11:54:38  	   sync-to-k8s-ciliumendpoint (1949)       6s ago         never        0       no error
11:54:38  	   sync-to-k8s-ciliumendpoint (827)        7s ago         never        0       no error
11:54:38  	   template-dir-watcher                    never          never        0       no error
11:54:38  	   update-k8s-node-annotations             4m28s ago      never        0       no error
11:54:38  	 Proxy Status:     OK, ip <IP_ADDRESS>, 0 redirects active on ports 10000-20000
11:54:38  	 Hubble:           Ok              Current/Max Flows: 336/4096 (8.20%), Flows/s: 1.27   Metrics: Disabled
11:54:38  	 Cluster health:   2/2 reachable   (2020-06-16T18:54:29Z)

Same failure on both Cilium nodes:
11:55:27  ⚠  Cilium agent 'cilium-d884n': Status: Ok  Health: Ok Nodes "" ContinerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 18 Failed 1
11:55:27  Failed controllers:
11:55:27   controller bpf-map-sync-cilium_lb_affinity_match failure '4 map sync errors'
11:55:27  ⚠  Cilium agent 'cilium-nxwnv': Status: Ok  Health: Ok Nodes "" ContinerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 18 Failed 1
11:55:27  Failed controllers:
11:55:27   controller bpf-map-sync-cilium_lb_affinity_match failure '4 map sync errors'

@brb As of now the job is still running: https://jenkins.cilium.io/job/Cilium-PR-K8s-GKE/1687/execution/node/118/log/

uname -a from one of the Cilium PODs:
Linux gke-jarno-cluster-2-default-pool-e9824c89-z065 4.14.138+ #1 SMP Tue Sep 3 02:58:08 PDT 2019 x86_64 x86_64 x86_64 GNU/Linux

Build results for the above: https://jenkins.cilium.io/job/Cilium-PR-K8s-GKE/1687/

2ccca833_K8sChaosTest_Connectivity_demo_application_Endpoint_can_still_connect_while_Cilium_is_not_running.zip

Seems that the affinity match map has not been created:
2020-06-16T18:50:08.71975432Z level=warning msg="Unable to add entry to affinity match map" backendID=5 error="Unable to get object /sys/fs/bpf/tc/globals/cilium_lb_affinity_match: no such file or directory" serviceID=11 subsys=service

OK, this is a bug - initMaps() is called before initKubeProxyReplacementOptions(). In your case, the latter enabled the session affinity, but the related maps can be created by initMaps(). Therefore, the affinity maps were not created, and thus the controller failure.


Variables are not correctly hoisted in Qwik's lexical scope

Qwik Version
0.11.1
Which component is affected?
Qwik Optimizer (rust) (I think)
Expected Behaviour
In javascripts variables get hoisted, so in my components I would expect to be able to access variables in any part of the code as long as they belong to the same scope, see this simple react example.
There the decreaseCounter function can access the counter (and also the setCounter) variable because it is being hoisted.
Actual Behaviour
It seems like Qwik doesn't apply such hoisting causing runtime errors, for example see this analogous qwik example
Here the decreaseCounter function fails to recognize the state reference causing a runtime error:

Additional Information
I am not sure if this is a bug or a feature request, sorry if I picked the wrong option for the issue
Anyways I think that javascript developers are very used and familiar with the hoisting of variables and that if possible Qwik should provide the same sort of behaviour.
This also generates contraints/hinderances to the developers which are forced to order their code in a particular way in order to have it correctly working.

The code you passes it is using the variable before it's declared

Hi @manucorporat , the variable is being referenced before it's declaration/initialization, but it is not being used right away (so it's not in the temporal dead zone) so I would expect it to being hoisted in the same way standard javascript does.
Please check out the react example to see what I mean, there the counter variable is also being referenced before it's declaration, but there everything works totally fine.
And I find this a to be a valuable behaviour which allows me to order my code in any logical way I want instead of having to carefully move code around so that the order follows the various code dependencies.

I see, that's too bad 😢
Thank you very much for the explanation 🙂
Let me know if we should just close this issue, keep it for reference or also add something regarding this in the docs.

yeah, i will keep it open, i think it's good to document this

@manucorporat - one option would be to move the dependency array into a function that is called later.
I.e. instead of:
const increaseCounter = qrlDEV(
  () => import('./app_component_increasecounter_ho3zdspwjzs.js'),
  "App_component_increaseCounter_Ho3zDspwJzs",
  {...},
  [ state ]
);```

it could be

```ts
const increaseCounter = qrlDEV(
  () => import('./app_component_increasecounter_ho3zdspwjzs.js'),
  "App_component_increaseCounter_Ho3zDspwJzs",
  {...},
  () => [ state ]
);

Note the last parameter.

we will

@manucorporat - was this closed as resolved or not planned?


Support for SwiftPM

Are there any plans to support SwiftPM?

Duplicate with https://github.com/mischa-hildebrand/AlignedCollectionViewFlowLayout/issues/27.
Branch master have Package.swift but latest version 1.1.2 not included Package file. 🤔


Fix icon folder-thumbnail

1. Why is this change necessary?
Tried to read all SVGs to create svg-sprite.
I'm getting error while reading the folder-thumbnail.svg because it seems to have no valid content.
Warning: DOMDocument::load(): Namespace prefix xlink for href on use is not defined in /var/www/html/sw6/platform/src/Storefront/Resources/app/storefront/dist/assets/icon/default/folder-thumbnail.svg, line: 6
2. What does this change do, exactly?
make the svg valid
3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
5. Checklist

[x] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[x] I have created a changelog file with all necessary information about my changes
[x] I have written or adjusted the documentation according to my changes
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/NEXT-14261
Please use this issue to track the state of your pull request.

Hey @tinect, your PR was merged : )


Setting the last_enqueue_time for a job can be ambiguous in format

Sidekiq::Cron::Job#save_last_enqueue_time just passes the @last_enqueue_time to hset for the redis connection, which is calling to_s on the Time object.
If you're using a non-standard default string format for Time objects, then parsing the last_enqueue_time will raise with the following error:
ArgumentError: Ambiguous parse format

Edit: Actually looks like this was fixed in the master branch..but not updated in any of the release versions. Any updates?

@alecjacobs5401 this is fixed in v1.0.4

please close it if it is resolved

@ondrejbartas
Thanks!


Update minimal version requirements for dependencies

This was tested using cargo generate-lockfile -Zminimal-versions.
The following indirect dependencies also have minimal version
dependencies. For at least num, rustc-serialize and rand this is
necessary to compile on rustc versions that are not older than 1.0.

num = "0.1.27"
rustc-serialize = "0.3.20"
termcolor = "1.0.4"
libudev-sys = "0.1.1"
rand = "0.3.14"
ab_glyph = "0.2.7

Based on https://github.com/bevyengine/bevy/pull/2455

for easy change comparison: https://github.com/bjorn3/bevy/compare/remove_unused_deps...bjorn3:minimal_versions
why do you want to add minimal patch versions?

To ensure that adding or updating bevy without a full cargo update will always work without problems. Currently if you already have say anyhow 1.0.0 in your Cargo.lock you will get a compilation error when adding bevy as new dependency. In the future it could happen that a fresh Cargo.lock generated at the time of the release of a certain bevy version will cause compilation to fail when bevy is updated to a new version in the future if the minimal version requirements in bevy are not updated to match reality.

Oh they broke backward compatibility between patch version... though that's a hard guarantee to make

Anyhow only uses patch releases it seems. The current version is 1.0.42.

Rebased

bors r+


chore(main): release 0.2.4

:robot: I have created a release beep boop
0.2.4 (2024-07-10)
Bug Fixes

bumping version to 0.2.4 (21bc095)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.2.4
:sunflower:


Deploy a minimum application to test network connectivity between openshift network and amazon

As part of our effort to find out why we have a flakey connection between Amazon and Openshift, the best bet would be to run a minimum application that simply attempts some actions using the AWS SDK.

[ ] Deploy a bare-bones version of the app (in dev) with only a request to AWS (S3 in this case would be the most useful)
[ ] Log the time it takes to start and end the request
[ ] Attempt requests to different hosts, to determine whether this is specifically a communication problem between AWS and Openshift or Openshift and any other host
[ ] Compare this to a (manual) ping on the same host, this will provide additional context that this is happening on the TCP layer and can help isolate the search if handing off to Platform Services is required.

Related to #1110

Blocked while waiting for metrics to come in that this is in fact a network layer issue, so this is on hold until the Sentry metrics come back showing slow execution/hanging when connecting to AWS.

So there is some hanging every once in a while, while testing I had ping running consistently (without any slowdowns or any dropped packets).
The results at 9PM EST (so ~1 hour after west-coast business hours) is that out of 4,438 uploads, only 7 had experienced a retry with an upload size of 10MB.
Come tomorrow I'd like to try again with a smaller filesize, and then once more during business hours

Results at 10AM EST: out of 3,995 uploads, 15 had experienced a retry with an upload size of 4MB

I believe I've found the issue, one (or more) of the IP addresses for AWS S3 are being blocked as it seems? A ping on s3-r-w.ca-central-1.amazonaws.com (<IP_ADDRESS>) results in 100% packet drop, and the tracepath has it ending at an IP address that I'd assume is internal to the BC Gov Network.
I believe the issue may be that, every so often when the DNS resolves the IP of our bucket we're given <IP_ADDRESS> wherein that connection hangs as it attempts to connect until it retries and gets a different IP.


New FILA Report Layout + Generation by date range

Fix #251
Fix #252

Coverage increased (+0.2%) to 47.287% when pulling d5c9375da53d52edb5c750376558542f03914a6f on edrisse:master into fe4553c30debb835dac775bd1e3cec072711b2f2 on esaude:master.

 Bug: FILA report must be according to layout and must be generated by date range.

Coverage increased (+0.2%) to 47.287% when pulling 97eef1a36382554891fb2d98a0af0f164d27f7c7 on edrisse:master into fe4553c30debb835dac775bd1e3cec072711b2f2 on esaude:master.

Coverage increased (+0.2%) to 47.3% when pulling 79af7ea041f882fb199ac2000d524f2bf212c38f on edrisse:master into fe4553c30debb835dac775bd1e3cec072711b2f2 on esaude:master.

Coverage increased (+0.2%) to 47.3% when pulling bf6059dc50d90071d3bd4ea7223a67f63128aaa7 on edrisse:master into fe4553c30debb835dac775bd1e3cec072711b2f2 on esaude:master.

Coverage increased (+0.2%) to 47.336% when pulling d8b96dfbcb1896d5f9eb28b343c5cc005e446f48 on edrisse:master into fe4553c30debb835dac775bd1e3cec072711b2f2 on esaude:master.

Coverage increased (+0.2%) to 47.336% when pulling 8d8f59618ad7ebe4b7e19cecd283423b2c2c41df on edrisse:master into fe4553c30debb835dac775bd1e3cec072711b2f2 on esaude:master.


Update govuk-frontent-toolkit name to match npm package naming

What problem does the pull request solve?
When using the guidance for 'packages/govuk-elements-sass', the README.md file (changed in this pull request) directs to use 'npm install govuk-frontend-toolkit' command however the correct name for the npm package is 'govuk_frontend_toolkit' (just changing hyphens for underscores).
How has this been tested?
Single change to README.md file therefore no tests executed.
What type of change is it?

Bug fix (non-breaking change which fixes an issue)

Has the documentation been updated?

I have updated the documentation accordingly.
I have read the CONTRIBUTING document. - Apologies though, wasn't sure if this actually needed a new version given that it's a minor, non-functional change.

Thanks for this! In theory that package is installed as a dependency of govuk-elements-sass anyway so not sure how important that line currently is anyway, but making it correct is a step in the right direction!


[5.4] Make comment more readable

This comment was a little awkward, so tweaked a little bit, ensuring we keep the cascading line endings :+1:

It's fine as is.


Card hover effect added

Pull Request
issue no #257
Title
Add scale effects on What we offer to developers Cards
Description
Added style in tailwind css
Related Issues
Fixes #257
Changes Made
Just added tailwind css for get hover effects.
Checklist

[x] I have tested the changes locally
[x] Documentation has been updated (if necessary)
[x] Changes are backward-compatible

@VaibhavArora314 Please check it and merge !


First release

Release the beta branch for the first time

:tada: This PR is included in version 1.0.0-beta.1 :tada:
The release is available on:

v1.0.0-beta.1
GitHub release

Your semantic-release bot :package::rocket:


v0.17.0-pre

There's a few things we need to sort here with migrations for keep-core being disabled on the keep-dev workflow.  Going ahead and opening this while we sort it out.

I think we can close #436 with this change. We need to resolve conflicts and make sure lock is in sync - build is complaining about it.

This is what we need to talk about - I can't update the lock because we disabled NPM publishing in the keep-dev workflow on keep-core.

We need to either reenable NPM  publishing even though we aren't migrating in keep-dev anymore, to keep this versioning dance going, or come up with something else.

We are at 1.0 now so this one is no longer applicable.


fix AttributeError: 'FileAdmin' object has no attribute 'queryset',

close #528

Coverage decreased (-0.04%) to 68.79% when pulling 2f3a38d4e09433093318cf18e1d5299dbaf1b27c on bashu:patch-1 into 04b4473cbb563470b077aadc8ff55a99c9ddbfd1 on stefanfoulis:develop.

I'd rather change the occurrencies of self.queryset to self.get_queryset whenever needed than aliasing get_queryset to queryset

I will fix that too

done =)

Coverage decreased (-0.05%) to 68.78% when pulling 0d89f68294190cd7e861776b3a7fb98a4e9a79db on bashu:patch-1 into 04b4473cbb563470b077aadc8ff55a99c9ddbfd1 on stefanfoulis:develop.

A self.queryset change for https://github.com/stefanfoulis/django-filer/pull/529/files#diff-d3544abce35931d328cca703f8101d48R108 is missing and I'd use the DJANGO_1_5 variable (at https://github.com/stefanfoulis/django-filer/blob/develop/filer/utils/compatibility.py#L20) for the version check, so it will be easier to go through the code when removing support for older Django versions

Coverage decreased (-0.04%) to 68.79% when pulling dd2201d846bf9127a451efd9bffb716067f24318 on bashu:patch-1 into 04b4473cbb563470b077aadc8ff55a99c9ddbfd1 on stefanfoulis:develop.

Coverage decreased (-0.04%) to 68.79% when pulling dd2201d846bf9127a451efd9bffb716067f24318 on bashu:patch-1 into 04b4473cbb563470b077aadc8ff55a99c9ddbfd1 on stefanfoulis:develop.


Syncer won't connect to KCP when KCP is running in a pod

Describe the bug
We are deploying KCP in a pod and then exposing it using an OpenShift Route. We can access the KCP instance using the kubectl and kcp plugin (although we need to use the --insecure-skip-tls-verify).
When we try to add a WorkloadCluster, it fails to start because the certificate is not valid for the external hostname that we configured in KCP. This is the log we see:
E0523 16:05:54.520348       1 run.go:74] "command failed" err="Get \"https://kcp-kcp.apps.kni1.cloud.lab.eng.bos.redhat.com:443/clusters/root:telcops:team-a/apis/workload.kcp.dev/v1alpha1/workloadclusters/hypershift\": x509: certificate is valid for localhost, not kcp-kcp.apps.kni1.cloud.lab.eng.bos.redhat.com"

To Reproduce
Steps to reproduce the behavior:

Deploy KCP on OCP and expose it using an OpenShift Passthrough Route.
Create a WorkloadCluster and apply the syncer yaml in the destination cluster
Check the logs
See error

Expected behavior
Syncer should be able to skip certificate verifications.
Additional context
This may be related to #1096
cc: @e-minguez

@mvazquezc are you using kubectl kcp workload sync to set up the WorkloadCluster & then taking the yaml it outputs and passing that to kubectl apply in the destination cluster?

@ncdc correct. This is the command we used:
kcp workload sync hypershift --syncer-image ghcr.io/kcp-dev/kcp/syncer:main --resources virtualmachineinstances.kubevirt.io --resources virtualmachines.kubevirt.io > syncer-hypershift.yaml
Then applied the manifest to the pcluster:
oc --kubeconfig=hosted0.kubeconfig apply -f syncer-hypershift.yaml
If it helps, we can provide access to the cluster.

This is different than #1096 because you aren't going through that path (where you create the deployment in kcp, kcp mutates it and sends to to the pcluster)

As a workaround try terminating TLS at the route (could re-encrypt to the backend) and removing any CA data from the generated workload cluster yaml.

I chatted with @mvazquezc and it sounds like this is something specific to how they deployed kcp. Would it be ok to close this (and reopen if needed)?


[SPARK-47148][SQL] Avoid to materialize AQE ExchangeQueryStageExec on the cancellation

What changes were proposed in this pull request?
AQE can materialize both ShuffleQueryStage and BroadcastQueryStage on the cancellation. This causes unnecessary stage materialization by submitting Shuffle Job and Broadcast Job. Under normal circumstances, if the stage is already non-materialized (a.k.a ShuffleQueryStage.shuffleFuture or BroadcastQueryStage.broadcastFuture is not initialized yet), it should just be skipped without materializing it.
Problematic Stacktrace:
at org.apache.spark.sql.execution.exchange.ShuffleExchangeExec.submitShuffleJob(ShuffleExchangeExec.scala:104)
at org.apache.spark.sql.execution.adaptive.ShuffleQueryStageExec.shuffleFuture$lzycompute(QueryStageExec.scala:210)
at org.apache.spark.sql.execution.adaptive.ShuffleQueryStageExec.shuffleFuture(QueryStageExec.scala:210)
at org.apache.spark.sql.execution.adaptive.ShuffleQueryStageExec.cancel(QueryStageExec.scala:223)
at org.apache.spark.sql.execution.adaptive.AdaptiveSparkPlanExec.$anonfun$cleanUpAndThrowException$1(AdaptiveSparkPlanExec.scala:905)

Please find sample use-case:
1- Stage Materialization Steps:
When stage materialization is failed:
1.1- ShuffleQueryStage1 - is materialized successfully,
1.2- ShuffleQueryStage2 - materialization is failed,
1.3- ShuffleQueryStage3 - Not materialized yet so ShuffleQueryStage3.shuffleFuture is not initialized yet

2- Stage Cancellation Steps:
2.1- ShuffleQueryStage1 - is canceled due to already materialized,
2.2- ShuffleQueryStage2 - is earlyFailedStage so currently, it is skipped as default by AQE because it could not be materialized,
2.3- ShuffleQueryStage3 - Problem is here: This stage is not materialized yet but currently, it is also tried to cancel and this stage requires to be materialized first.

Reproduce Steps:
https://github.com/apache/spark/pull/45234/files#diff-f89f2fe78b324c6bc7190bef84220181f3616efc156ea99b3f15d375a22d7f88R900
Why are the changes needed?
Current logic introduces unnecessary Shuffle Job / Broadcast Job to be able to cancel ShuffleQueryStage / BroadcastQueryStage.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Added new Unit Tests
Was this patch authored or co-authored using generative AI tooling?
No

Should we also backport this patch to v3.4.x and v3.5.x?

cc @cloud-fan @maryannxue as well

Thanks @cloud-fan and @ulysses-you for the reviews and approval.
I have just rebased to get green build.

Build is green now so PR is ready to be merged. Thanks in advance.

thanks, merging to master!


Selector needs to be 'lightbox' for swipe to work

If you use any other selector than 'lightbox' the swiping on touch devices does not work.

Hi :) I found your plugin today and was happy to use it in my project. I made a small improvement what may add a good usability advantage with only a few lines.
I added "afterConstructLightbox" as a new hook, what gives me the ability to make changes to the created topbox html ("templating features", add more html, change buttons etc...)
init...
      afterConstructLightbox: function() {},
after...
      e.preventDefault();
      this.options.beforeShowLightbox.call(this);
      var lightbox = this.constructLightbox();
just this line:
      this.options.afterConstructLightbox.call(this);
Thanks for your work,
Alex

@AlexanderKoe Brilliant work, many thanks! I'll look at getting this added soon. Still trying to chase a few YouTube bugs currently, due to new attributes they are adding on links. Thank you for your time and code suggestion. Much appreciated.

happy to help :)
sorry I just noticed I putted this comment into an existing issue...
This is a short example how to use it.
Important: remove the overlay before open a new Lightbox.
[...]
	beforeShowLightbox: function () {
		$('.topbox_overlay').remove(); // need this to reinitialise the changes
	},
	afterConstructLightbox: function () {
		changeTemplate();
	},

[...]

	function changeTemplate() {
		$('.topbox_title_wrap').addClass('text-white text-left');
		$('.topbox_nav').append('');
		$('.topbox_close').append('');
	}


filter 'skip-ami-snapshots'  is not valid under any of the given schemas

Hi
With this simple policy below :
policies:
  - name: delete-stale-snapshots
    resource: ebs-snapshots
    filters:
      - type: age
        days: 28
        op: ge
      - skip-ami-snapshots: true

from http://www.capitalone.io/cloud-custodian/docs/_modules/c7n/resources/ebs.html
i get this error :

Traceback (most recent call last):
  File "./cloud-custodian/bin/custodian", line 11, in <module>
    load_entry_point('c7n', 'console_scripts', 'custodian')()
  File "/Users/damien/Documents/d2si/renault-digital/custodian/cloud-custodian/c7n/cli.py", line 369, in main
    command(options)
  File "/Users/damien/Documents/d2si/renault-digital/custodian/cloud-custodian/c7n/commands.py", line 55, in _load_policies
    collection = policy_load(options, fp, vars=vars)
  File "/Users/damien/Documents/d2si/renault-digital/custodian/cloud-custodian/c7n/policy.py", line 63, in load
    raise Exception("Failed to validate on policy %s \n %s" % (errors[1], errors[0]))
Exception: Failed to validate on policy delete-stale-snapshots
 {'resource': 'ebs-snapshots', 'name': 'delete-stale-snapshots', 'filters': [{'type': 'age', 'days': 28, 'op': 'ge'}, {'skip-ami-snapshots': True}]} is not valid under any of the given schemas
Failed validating 'anyOf' in schema['properties']['policies']['items']:
    {'anyOf': [{'$ref': '#/definitions/resources/datapipeline/policy'},
               {'$ref': '#/definitions/resources/firehose/policy'},
               {'$ref': '#/definitions/resources/rds-cluster-snapshot/policy'},
               {'$ref': '#/definitions/resources/event-rule/policy'},
               {'$ref': '#/definitions/resources/elb/policy'},
               {'$ref': '#/definitions/resources/redshift-snapshot/policy'},
               {'$ref': '#/definitions/resources/rds-subnet-group/policy'},
               {'$ref': '#/definitions/resources/route-table/policy'},
               {'$ref': '#/definitions/resources/internet-gateway/policy'},
               {'$ref': '#/definitions/resources/ami/policy'},
               {'$ref': '#/definitions/resources/cache-cluster/policy'},
               {'$ref': '#/definitions/resources/kinesis/policy'},
               {'$ref': '#/definitions/resources/network-acl/policy'},
               {'$ref': '#/definitions/resources/snowball/policy'},
               {'$ref': '#/definitions/resources/support-case/policy'},
               {'$ref': '#/definitions/resources/ml-model/policy'},
               {'$ref': '#/definitions/resources/network-addr/policy'},
               {'$ref': '#/definitions/resources/asg/policy'},
               {'$ref': '#/definitions/resources/emr/policy'},
               {'$ref': '#/definitions/resources/kinesis-analytics/policy'},
               {'$ref': '#/definitions/resources/iam-user/policy'},
               {'$ref': '#/definitions/resources/cfn/policy'},
               {'$ref': '#/definitions/resources/vpn-gateway/policy'},
               {'$ref': '#/definitions/resources/dynamodb-stream/policy'},
               {'$ref': '#/definitions/resources/app-elb/policy'},
               {'$ref': '#/definitions/resources/ec2/policy'},
               {'$ref': '#/definitions/resources/ebs/policy'},
               {'$ref': '#/definitions/resources/storage-gateway/policy'},
               {'$ref': '#/definitions/resources/rds-cluster/policy'},
               {'$ref': '#/definitions/resources/hsm-client/policy'},
               {'$ref': '#/definitions/resources/opswork-stack/policy'},
               {'$ref': '#/definitions/resources/kms/policy'},
               {'$ref': '#/definitions/resources/log-group/policy'},
               {'$ref': '#/definitions/resources/hostedzone/policy'},
               {'$ref': '#/definitions/resources/rds-subscription/policy'},
               {'$ref': '#/definitions/resources/hsm/policy'},
               {'$ref': '#/definitions/resources/identity-pool/policy'},
               {'$ref': '#/definitions/resources/ecr/policy'},
               {'$ref': '#/definitions/resources/codebuild/policy'},
               {'$ref': '#/definitions/resources/directconnect/policy'},
               {'$ref': '#/definitions/resources/distribution/policy'},
               {'$ref': '#/definitions/resources/rds/policy'},
               {'$ref': '#/definitions/resources/key-pair/policy'},
               {'$ref': '#/definitions/resources/app-elb-target-group/policy'},
               {'$ref': '#/definitions/resources/elasticsearch/policy'},
               {'$ref': '#/definitions/resources/ecs/policy'},
               {'$ref': '#/definitions/resources/iam-group/policy'},
               {'$ref': '#/definitions/resources/batch-compute/policy'},
               {'$ref': '#/definitions/resources/redshift/policy'},
               {'$ref': '#/definitions/resources/vpn-connection/policy'},
               {'$ref': '#/definitions/resources/iam-role/policy'},
               {'$ref': '#/definitions/resources/batch-definition/policy'},
               {'$ref': '#/definitions/resources/dynamodb-table/policy'},
               {'$ref': '#/definitions/resources/hsm-hapg/policy'},
               {'$ref': '#/definitions/resources/waf/policy'},
               {'$ref': '#/definitions/resources/shield-protection/policy'},
               {'$ref': '#/definitions/resources/cache-subnet-group/policy'},
               {'$ref': '#/definitions/resources/snowball-cluster/policy'},
               {'$ref': '#/definitions/resources/iam-profile/policy'},
               {'$ref': '#/definitions/resources/vpc/policy'},
               {'$ref': '#/definitions/resources/codepipeline/policy'},
               {'$ref': '#/definitions/resources/step-machine/policy'},
               {'$ref': '#/definitions/resources/account/policy'},
               {'$ref': '#/definitions/resources/security-group/policy'},
               {'$ref': '#/definitions/resources/rest-api/policy'},
               {'$ref': '#/definitions/resources/acm-certificate/policy'},
               {'$ref': '#/definitions/resources/customer-gateway/policy'},
               {'$ref': '#/definitions/resources/codecommit/policy'},
               {'$ref': '#/definitions/resources/gamelift-fleet/policy'},
               {'$ref': '#/definitions/resources/opswork-cm/policy'},
               {'$ref': '#/definitions/resources/simpledb/policy'},
               {'$ref': '#/definitions/resources/waf-regional/policy'},
               {'$ref': '#/definitions/resources/cloudtrail/policy'},
               {'$ref': '#/definitions/resources/cache-snapshot/policy'},
               {'$ref': '#/definitions/resources/cloudsearch/policy'},
               {'$ref': '#/definitions/resources/rrset/policy'},
               {'$ref': '#/definitions/resources/peering-connection/policy'},
               {'$ref': '#/definitions/resources/streaming-distribution/policy'},
               {'$ref': '#/definitions/resources/s3/policy'},
               {'$ref': '#/definitions/resources/eni/policy'},
               {'$ref': '#/definitions/resources/efs/policy'},
               {'$ref': '#/definitions/resources/redshift-subnet-group/policy'},
               {'$ref': '#/definitions/resources/iam-certificate/policy'},
               {'$ref': '#/definitions/resources/gamelift-build/policy'},
               {'$ref': '#/definitions/resources/user-pool/policy'},
               {'$ref': '#/definitions/resources/rds-snapshot/policy'},
               {'$ref': '#/definitions/resources/shield-attack/policy'},
               {'$ref': '#/definitions/resources/launch-config/policy'},
               {'$ref': '#/definitions/resources/subnet/policy'},
               {'$ref': '#/definitions/resources/sqs/policy'},
               {'$ref': '#/definitions/resources/healthcheck/policy'},
               {'$ref': '#/definitions/resources/kms-key/policy'},
               {'$ref': '#/definitions/resources/sns/policy'},
               {'$ref': '#/definitions/resources/iam-policy/policy'},
               {'$ref': '#/definitions/resources/ebs-snapshot/policy'},
               {'$ref': '#/definitions/resources/health-event/policy'},
               {'$ref': '#/definitions/resources/alarm/policy'},
               {'$ref': '#/definitions/resources/r53domain/policy'},
               {'$ref': '#/definitions/resources/glacier/policy'},
               {'$ref': '#/definitions/resources/directory/policy'},
               {'$ref': '#/definitions/resources/lambda/policy'}]}

On instance['policies'][0]:
    {'filters': [{'days': 28, 'op': 'ge', 'type': 'age'},
                 {'skip-ami-snapshots': True}],
     'name': 'delete-stale-snapshots',
     'resource': 'ebs-snapshots'}

bad doc example it looks like on the doc string, the shorthand syntax of k: v is reserved for value type filters on the resource attributes. other filter types need to be explicitly declared or implicit if done with no parameters.
ie.
policies:
  - name: delete-stale-snapshots
    resource: ebs-snapshots
    filters
       - type: age
          days: 28
          op: ge
       - skip-ami-snapshots

or explicit
policies:
  - name: delete-stale-snapshots
    resource: ebs-snapshots
    filters
       - type: age
          days: 28
          op: ge
       - type: skip-ami-snapshots
          value: false

Thank you


Uncaught class binding parsing error

I was struggling with this for some time:
      a($b="class:{active: isActiveInSteps(5,6)") 5

I went debugging my isActiveInSteps function.
Turn out the closing } was missing but VM gives no warning. Thus the binding always failed silently.

Pick up 4.0.14


Support for SchemaUpdate

Using the JsonType.class for database technology agnostic configuration fails when using SchemaUpdate, with error "No Dialect mapping for JDBC type: 1111", at least for SQL Server Dialects, but I suppose it will fail for all Dialects.
For what I've looked at, there is no information available for Hibernate to create the DDL script.
The stack trace is (using hibernate-types-52 2.14.0 and hibernate 5.4.31.Final):
 Caused by: org.hibernate.MappingException: No Dialect mapping for JDBC type: 1111
	at org.hibernate.dialect.TypeNames.get(TypeNames.java:71)
	at org.hibernate.dialect.TypeNames.get(TypeNames.java:103)
	at org.hibernate.dialect.Dialect.getTypeName(Dialect.java:403)
	at org.hibernate.mapping.Column.getSqlType(Column.java:238)
	at org.hibernate.tool.schema.internal.StandardTableExporter.getSqlCreateStrings(StandardTableExporter.java:96)
	at org.hibernate.tool.schema.internal.StandardTableExporter.getSqlCreateStrings(StandardTableExporter.java:30)
	at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.createTable(AbstractSchemaMigrator.java:279)
	at
 org.hibernate.tool.schema.internal.GroupedSchemaMigratorImpl.performTablesMigration(GroupedSchemaMigratorImpl.java:71)
	at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.performMigration(AbstractSchemaMigrator.java:207)
	at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.doMigration(AbstractSchemaMigrator.java:114)
	at org.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:93)
	at org.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:62)
        ...

One approach could be enhancing SQLServerDialect with the new type, however, type 1111 is "OTHER", and that doesn't feel like the correct approach.

The Hibernate Types library is just a plugin. A plugin does not control the Hibernate ORM core. The feature you need can only be implemented in the Hibernate framework, and you can do it too since Hibernate is OSS.
Since I'm no longer working for Red Hat, I will never have the time to do it myself unless your company wants to hire me to investigate it and find a solution.


Optionally auto-register commands to Application

Right now this extension expects commands autodiscovery as contributte/console does it. Providing way to optionally auto-register commands like zenify/doctrine-migrations would bring support even for kdyby/console.
Something like:
console:
    loadCommands: true # default false

I guess you can use decorator for this case.
decorator:
        Symfony\Component\Console\Command\Command:
                tags: [kdyby.console.command]

Great, thank you! Didn't know about that extension. Would you mention it somewhere in the docs? I expect that interop with kdyby/console is a common scenario.

We'll mention it ;-) Thanks @fmasa for the issue for that.

https://github.com/nettrine/migrations/blob/master/.docs/README.md#kdybydoctrine


Add supabase/postgrest-rs client library

Hey there, I made a little thingy 🦀. Just adding another one to the list!

Looks cool! Thank you!


Program type already present: com.google.firebase.messaging.MessageForwardingService

Please fill in the following fields:
Unity editor version: 2018.3.12f1
Firebase Unity SDK version: 6.0.0
Firebase plugins in use (Auth, Database, etc.): FCM
Additional SDKs you are using (Facebook, AdMob, etc.):
Admob, Facebook, voxelbuster, googlesignin,
Platform you are using the Unity editor on (Mac, Windows, or Linux): WIndows
Platform you are targeting (iOS, Android, and/or desktop): Android
sorry for my engilsh.
using build, gradle. multidex.
i cant build project after add fcm.
https://scans.gradle.com/s/hh6ksy4nmgdd2

Hi @kshioring - sorry you're having trouble with the Firebase Unity SDK!
Are you able to reproduce this issue in our cloud messaging quickstart, using only the Firebase plugin?  If you're able to reproduce the issue in the quickstart and provide us with the steps you took to get there, that would greatly help us try to figure out what might be going wrong.

We had the same problem. Using multidex.
After doing force resolve, commenting out the following line in the gradle template file seems to be working for us. We have the resolve on build and editor toggles disabled.

implementation 'com.google.firebase:firebase-messaging-unity:6.1.1' // Assets/Firebase/Editor/MessagingDependencies.xml:22

I found a solution which is basically very similar with the above solution.
Cause
If you build using custom gradle template,

Unity Jar Resolver will write out the dependencies into the gradle script. so Gradle will include some dependencies in the build process.
At the same time, Unity will copy the aar files in the project into the temporary libs folder which is also used in the build process.
Firebase Plugin has some aar files in Assets/Firebase/m2repository/com/google/... that is used by both of gradle and unity (yeah, it's causing the conflict)

Solution
Exclude all Firebase aar files from the Unity's build process by unchecking "Android" from "Include Platforms" like the below picture:

Folks this was fixed in the Play Services Resolver 1.2.117 though you'll probably want to pull the latest release.  We'll update this bug when the issue the latest Play Services Resolver is redistributed with the Firebase Unity SDK.

This should be fixed as of the latest release, 6.2.0


Export data as GLTF (GLB)

Starting to take shape.
What is missing is:

optionally rotating the geometry so that +Z in the rvm files align with the up-vector of gltf files (+Y)
plumbing the options controlling the export out to the command line argument parsing instead of having them hard-coded.


[Doc Improvement][Tools and SDKs-TTK-Revise Integrate with Developer Portal]

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/Integrate-with-developer-portal.md
95
2
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 73476a8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/toolkit/Integrate-with-developer-portal.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/Integrate-with-developer-portal.md
83
9
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 2f5766c:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/toolkit/Integrate-with-developer-portal.md
:warning:Warning
View
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/Select_Import_app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/Select_Publish_to_org.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/Integrate-with-developer-portal.md

Line 21, Column 5: [Warning: file-not-found - See documentation] Invalid file link: '../assets/images/teams-toolkit-v2/teams toolkit fundamentals/dev-portal-ttk_1.png'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/Integrate-with-developer-portal.md
99
1
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 991c146:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/dev-portal-ttk_1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/Select_Import_app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/Select_Publish_to_org.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/Integrate-with-developer-portal.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/Integrate-with-developer-portal.md
99
1
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit dbbacf9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/dev-portal-ttk_1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/Select_Import_app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/Select_Publish_to_org.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/Integrate-with-developer-portal.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/Integrate-with-developer-portal.md
99
1
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit c3430d8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/dev-portal-ttk_1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/Select_Import_app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/Select_Publish_to_org.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/Integrate-with-developer-portal.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/Integrate-with-developer-portal.md
99
1
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit e798a0e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/dev-portal-ttk_1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/Select_Import_app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/Select_Publish_to_org.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/Integrate-with-developer-portal.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Delete work "Now" in step 1 for to Publish app using Developer Portal.
Remove Dev Portal link in step 2 as already mentioned in See also.
Step 3 its better to write upload your app instead of import your app as its repeating.
To many times the Dev Portal link is given. Remove from all the places except see also.
Please place the first mention in the right place.

*Add an image of Dev Portal dashboard basic information. Just sign in with your v-id and you can do that.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/Integrate-with-developer-portal.md
99
1
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit c31e94e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/dev-portal-ttk_1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/Select_Import_app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/Select_Publish_to_org.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/Integrate-with-developer-portal.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/mstdd-landing.yml
100
0
link
:white_check_mark:

msteams-platform/toolkit/Integrate-with-developer-portal.md
99
1
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit b81f053:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/dev-portal-ttk_1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/Select_Import_app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/Select_Publish_to_org.png
:white_check_mark:Succeeded
View

msteams-platform/mstdd-landing.yml
:white_check_mark:Succeeded
View

msteams-platform/toolkit/Integrate-with-developer-portal.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/Integrate-with-developer-portal.md
99
1
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 540d7e2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/dev-portal-ttk_1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/Select_Import_app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/Select_Publish_to_org.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/Integrate-with-developer-portal.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Add support for rotating around custom point

WPILIB's toSwerveStates method allows you to specify a point with Translation2d to rotate around, it would be super useful to have this implemented to YAGSL

Thank you so much! you're an absolute life-saver


Not returning GM, GDS independently from the lookup table however returns GM_GDS

gds  = nmos.look_up('GDS',  GM_ID=gm_id, L=L VGS=VGS_nmos, VDS=VDS,VSB=VSB)
gm  = nmos.look_up('GM',  GM_ID=gm_id, L=L VGS=VGS_nmos, VDS=VDS,VSB=VSB)
returns []
whereas
gm_gds = nmos.look_up('GM_GDS',  GM_ID=gm_id, L=L VGS=VGS_nmos, VDS=VDS,VSB=VSB)
returns a value, Ex: 160.
Is there anything missing in the function or the way it's used?

Hi avlsi,
Your usage is incorrect. You can't directly lookup GDS or GM from the lookup function against gm/ID .
Usually we find an Ibias from our GBW specification.
Then you can lookup:
GDS = Ibias * nmos.look_up('GDS_ID', GM_ID=gm_id, ........)
GM =  Ibias * gm_id

You can email me for a common source design example
Cian

I did try GDS_W and its working. Thanks for the feedback.
gds1 = nmos.look_up('GDS_W',VGS=VGS1,VDS=VDS1,L=L)
VEA1 = JD1/gds1


{ragg} build didn't happen

The ragg spec was updated in https://github.com/cran4linux/cran2copr/commit/33ecc4a379258b8a947422ee8099e445b90f53af but this doesn't seem to have triggered a build in copr. Normally I'd assume a lag but today's sync seems to have already triggered builds (e.g. R-CRAN-MEDseq).
Hope this makes sense.

And several more... Triggered now, thanks!


Virtual fields are dropped in changeset params

See mailing list topic: https://groups.google.com/forum/#!topic/elixir-ecto/SlFSfkfB03k

Can you provide your User.changeset code? Did you forget to add temp to required or optional params?
Because there's a test for this case, I move the temp to optional params, it still works. But the field will be dropped if I remove temp

:+1: my mistake, you're right. Thats exactly what I was doing wrong, thanks!


Create Java Project broken

Install extension
Try to invoke "Java: Create Project" to create a project.

Expected:
A prompt to add a new project
Actually:
Nothing happened

@Vigilans could you have a look at this issue?

Sure, I'll have a look.

This issue cannot be reproduced in Linux, Mac & Windows machine with openjdk 11, so I'll close it for now.

Seems like some users are still experiencing this error. Could you follow up with the user?
redhat-developer/vscode-java#1141

I see.
This issue and the linked issue's behavior seems not the same, and I'll have a look into the mechanism of how the command gets called.

Close for inactive. If anyone still has the problem, feel free to leave a comment,
Thanks

I think i Solved it, I was Facing this Problem too.
On Clicking create data project nothing happend for 2 sec and then a error poped up saying - 'java.project.create' not found.
Solution - (At least worked for me😅)
YOU HAVE TO ADD JAVA TO PATH.
Here are the steps to do that -

Find Java Folder in you C drive and then inside JDK folder, copy the path of bin folder (it will look like this - C:\Program Files\Java\jdk-15.0.1\bin)
Search Environment Variables in settings.
A system Properties tab will open.
click on environment variables button.
Inside System variables Group search for the varible named 'Path'.

Can you provide some images


fixed typo and removed the pitch section in the Feature request template

Fixes #318

Coverage remained the same at 88.907% when pulling<PHONE_NUMBER>76aec431af3770c7c53a3b747da83e on INM-6:fix/issue_template into 7cb8d087c0364a87447d5c4b59019a894d3fb88c on NeuralEnsemble:master.


Zombified slimes can turn into unzombified Geras

Description
Was playing on Salamander and got infected. Turns out, you can abuse this to sneak up on people and and pop up as a zombie next to them.
Reproduction
Be a slime. Get infected and turn into a zombie. Morph into Geras, you will not have the zombie tag and your speech is normal.

Duplicate. My fault, OG's.


document local minikube. Fixes https://github.com/tilt-dev/tilt/issues/3193

Hello @maiamcc,
Please review the following commits I made in branch nicks/minikube:
f637541df50d13c64549d9262e52efaf7409c291 (2020-09-21 18:04:23 -0400)
document local minikube. Fixes https://github.com/tilt-dev/tilt/issues/3193
Code review reminders, by giving a LGTM you attest that:

Commits are adequately tested
Code is easy to understand and conforms to style guides
Incomplete code is marked with TODOs
Code is suitably instrumented with logging and metrics

a ton of this is just copied and pasted from the work we did on kind-local
https://github.com/tilt-dev/kind-local
i found that the minikube instructions recommended a bad approach, and the setup was very manual

unforuntately, had to back out the circleci test due to a minikube bug

there's some discussion here https://github.com/kubernetes/minikube/issues/7420, there might be a workaround, but going to do it on a separate pr

...whoops I made a buncha comments straight on this commit, transferring them over to this PR :-/


test: allow dispatcher test cases running on ipv6 only env

Commit Message:
Replaced hard coded "<IP_ADDRESS>" by getLoopbackAddressUrlString
Signed-off-by: Yuchen Dai<EMAIL_ADDRESS>Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/assign yanavlasov

Thank you!


Improve find command keyword-matching

Codecov Report
Base: 66.19% // Head: 66.19% // Decreases project coverage by -0.00% :warning:

Coverage data is based on head (e52e60b) compared to base (1f54f31).
Patch coverage: 73.07% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##             master     #250      +/-   ##
============================================
- Coverage     66.19%   66.19%   -0.01%
- Complexity      629      648      +19
============================================
  Files           121      127       +6
  Lines          2204     2254      +50
  Branches        240      250      +10
============================================
+ Hits           1459     1492      +33
- Misses          673      684      +11
- Partials         72       78       +6

Impacted Files
Coverage Δ

...se/model/person/NameContainsKeywordsPredicate.java
100.00% <ø> (ø)

.../model/person/PersonContainsKeywordsPredicate.java
66.66% <66.66%> (ø)

...model/person/AddressContainsKeywordsPredicate.java
71.42% <71.42%> (ø)

...e/model/person/EmailContainsKeywordsPredicate.java
71.42% <71.42%> (ø)

...e/model/person/PhoneContainsKeywordsPredicate.java
71.42% <71.42%> (ø)

...inurse/model/tag/TagContainsKeywordsPredicate.java
71.42% <71.42%> (ø)

...model/person/PatientContainsKeywordsPredicate.java
85.71% <85.71%> (ø)

...ava/seedu/uninurse/logic/commands/FindCommand.java
90.00% <100.00%> (-10.00%)
:arrow_down:

...seedu/uninurse/logic/parser/FindCommandParser.java
100.00% <100.00%> (ø)

... and 1 more

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Added source maps

It might be easier if developers see the code they wrote when debugging not the code generated.

@rossross Can you sign our CLA? https://docs.google.com/forms/d/1Npd68d32UDUKUYuCDDrW0VN5Lv8p-a6Ziaa2JFKp6Cg/viewform?c=0&w=1

Signed

This got merged in, but I had to amend the commit message. Have a read through the contributing guide for the future:  https://github.com/durandalproject/about/blob/master/CONTRIBUTING.md
Thanks! I agree, this is much nicer.

Sorry about that, I'll make sure to follow the guidelines next time.


add tests

Closes #13

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@af99b7b). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #15   +/-   ##
=======================================
  Coverage        ?   79.09%
=======================================
  Files           ?        7
  Lines           ?      110
  Branches        ?        8
=======================================
  Hits            ?       87
  Misses          ?       20
  Partials        ?        3

Flag
Coverage Δ

unittests
79.09% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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