HA 2024.6 Warning: Detected blocking call to open inside the event loop

System Health details
see below
Checklist

[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of any previous issues..

Describe the issue
HA 2024.6 reports Warnings for integration:
Detected blocking call to open inside the event loop by custom integration 'anker_solix' at custom_components/anker_solix/solixapi/api.py, line 595: with open(filename, encoding="utf-8") as file:
Reproduction steps
Warnings after upgrading to HA 2024.06
Debug logs
Logger: homeassistant.util.loop
Quelle: util/loop.py:84
Erstmals aufgetreten: 18:05:53 (781 Vorkommnisse)
Zuletzt protokolliert: 18:06:26

    Detected blocking call to open inside the event loop by custom integration 'anker_solix' at custom_components/anker_solix/solixapi/api.py, line 595: with open(filename, encoding="utf-8") as file: (offender: /config/custom_components/anker_solix/solixapi/api.py, line 595: with open(filename, encoding="utf-8") as file:), please create a bug report at https://github.com/thomluther/hacs-anker-solix/issues Traceback (most recent call last): File "<frozen runpy>", line 198, in _run_module_as_main File "<frozen runpy>", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module> sys.exit(main()) File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/src/homeassistant/homeassistant/setup.py", line 165, in async_setup_component result = await _async_setup_component(hass, domain, config) File "/usr/src/homeassistant/homeassistant/setup.py", line 447, in _async_setup_component await asyncio.gather( File "/usr/src/homeassistant/homeassistant/setup.py", line 449, in <genexpr> create_eager_task( File "/usr/src/homeassistant/homeassistant/util/async_.py", line 37, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 742, in async_setup_locked await self.async_setup(hass, integration=integration) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup result = await component.async_setup_entry(hass, self) File "/config/custom_components/anker_solix/__init__.py", line 84, in async_setup_entry await coordinator.async_config_entry_first_refresh() File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 277, in async_config_entry_first_refresh await self._async_refresh( File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 312, in _async_refresh self.data = await self._async_update_data() File "/config/custom_components/anker_solix/coordinator.py", line 50, in _async_update_data return await self.client.async_get_data() File "/config/custom_components/anker_solix/api_client.py", line 206, in async_get_data await self.api.update_sites(fromFile=self._testmode) File "/config/custom_components/anker_solix/solixapi/api.py", line 1259, in update_sites sites = await self.get_site_list(fromFile=fromFile) File "/config/custom_components/anker_solix/solixapi/api.py", line 1609, in get_site_list resp = await self.request("post", _API_ENDPOINTS["site_list"]) File "/config/custom_components/anker_solix/solixapi/api.py", line 1094, in request await self.async_authenticate() File "/config/custom_components/anker_solix/solixapi/api.py", line 992, in async_authenticate data = self._loadFromFile(self._authFile) File "/config/custom_components/anker_solix/solixapi/api.py", line 595, in _loadFromFile with open(filename, encoding="utf-8") as file:

Diagnostics dump
No response

Changed all file read and write IO of the Api library to async IO using the aiofiles library.
Added aiofiles to integration requirements to have it installed by Core


release(prod): GA 2<IP_ADDRESS>

Draft until #205 has been vetted in testnet for 24h. Released at 9:30am (15:30 UTC) 11/11/21.
Why
Master branch is not stable so applying GA directly.
How
Bump to hm-miner to commit https://github.com/NebraLtd/hm-miner/commit/6ee720d968173f50c92a67f538bc69837dd61b9f and update FIRMWARE_VERSIONs.
References

Closes: https://github.com/NebraLtd/helium-miner-software/issues/203
Potentially closes: https://github.com/NebraLtd/helium-miner-software/pull/196

Blocked, Testnet units seem to be reporting offline in explorer

Closed by #212


Publish docs for v0.x of this module

Given the module has been updated for Nuxt Bridge and Nuxt 3, it would be great to have the old docs online without the need to run them locally.

They are published on https://v0.sanity.nuxtjs.org/.


add DhritiShikhar to owners

@sbose78 Please review this PR

/assign @sbose78

Closing this PR after having a discussion with @sbose78


Add context when 'app-' demo components are used

We use app- prefixed components in storybook to work around limitations in storybook, we should call this out every time we use a demo component to reduce confusion. We should also link out to the source for the component.

@cal-smith Any pointers on what exactly needs to be done here? If it is still open, I can work on it if it is related to Documentation.

This has been addressed in latest version of CCA which uses Storybook v7. We NOW link to the github story example as well.


Add LiveCode

Adding a language

[x] The code displays "Hello World"
[x] I have updated the readme to include the new language
[x] I have incremented the language count in the readme

Is it Livecode or Livescript?

It appears to be called LiveCode, which the capitalisation should reflect in this PR.
https://lessons.livecode.com/m/2592/l/21009-hello-world

I have added these changes in #1246


Add blog article: The case for Kubernetes limits

A blogpost discussing cases were using limits might be a good idea.
Signed-off-by: Milan Plzik<EMAIL_ADDRESS>

/retitle Add blog article: The case for Kubernetes limits

Thanks
/hold
Awaiting publication date

@nate-double-u @onlydole ping :)

@sftim @nate-double-u @onlydole ping; it's ~9 days until the presumed publish date.

Oh, and:
/hold cancel

BTW, because this site is open source, you can mirror the article at https://grafana.com/blog/ immediately after publication, provided the copyright notice on the page is appropriate.
Just something you might like to know.


Questions on cassandra querying scheme

1.) Am I correct in saying that if I define a CassandraCqlMapState with a parallelism of N, then  N different instances of the Session object will be created? If this is correct, does this not go against what is recommended by DataStax: http://www.datastax.com/dev/blog/4-simple-rules-when-using-the-datastax-drivers-for-cassandra where they say that a single Session object should be used across the application? Or does that not make sense in the storm context where the state could be distributed across different physical nodes?
2.) For all queries, CassandraCqlStateMap prepares a BatchStatement to submit to Cassandra. Is this guaranteed to have better performance than executing the individual statements asynchronously? Ref: https://lostechies.com/ryansvihla/2014/08/28/cassandra-batch-loading-without-the-batch-keyword/. Basically what I am trying to get to is: Does the micro-batching in Trident really offer any amortisation of costs given how cassandra behaves with batch queries?
Thanks
Gireesh

Gireesh,
(1) I believe sessions are re-used, because the CassandraCqlMapState is create from the Factory, which uses a single instance of CqlClientFactory to generate sessions, and will re-use a session if it already has one.  Have a look at this line:
https://github.com/hmsonline/storm-cassandra-cql/blob/master/src/main/java/com/hmsonline/trident/cql/CqlClientFactory.java#L45 https://github.com/hmsonline/storm-cassandra-cql/blob/master/src/main/java/com/hmsonline/trident/cql/CqlClientFactory.java#L45
(2) No, batch statements don’t necessarily have better performance than single statements.  In fact, i think they may even be a tad bit slower because they are coordinated, but I would have to do some digging to refresh on that.
hope this helps,
brian
Brian O'Neill
Principal Architect @ Monetate
m:<PHONE_NUMBER>
<EMAIL_ADDRESS><EMAIL_ADDRESS>Watch our Video http://monetate.wistia.com/medias/q6hot9ckl0 | Marketing Blog http://monetate.com/blog/ | Free Resources http://monetate.com/resources/ | Follow Monetate on Twitter http://twitter.com/monetate | Download our Resources App http://monetate.com/app
Know a great software engineer and want a referral bonus even if YOU don't work at Monetate? Tell our recruiters about them!

On Jan 29, 2016, at 2:43 AM, gireeshramji<EMAIL_ADDRESS>wrote:

Am I correct in saying that if I define a CassandraCqlMapState with a parallelism of N, then N different instances of the Session object will be created? If this is correct, does this not go against what is recommended by DataStax: http://wwwdatastaxcom/dev/blog/4-simple-rules-when-using-the-datastax-drivers-for-cassandra where they say that a single Session object should be used across the application? Or does that not make sense in the storm context where the state could be distributed across different physical nodes?

For all queries, CassandraCqlStateMap prepares a BatchStatement to submit to Cassandra Is this guaranteed to have better performance than executing the individual statements asynchronously? Ref: https://lostechiescom/ryansvihla/2014/08/28/cassandra-batch-loading-without-the-batch-keyword/ Basically what I am trying to get to is: Does the micro-batching in Trident really offer any amortisation of costs given how cassandra behaves with batch queries?

Thanks
Gireesh
—
Reply to this email directly or view it on GitHub https://github.com/hmsonline/storm-cassandra-cql/issues/59.


Errors when I open some files.

environment

vim: neovim HEAD
vim-airline: latest
OS: OS X 10.11.4
terminal: iTerm2 Build 2.9.20160403-nightly

actual behavior
Open a file without erros
expected behavior
Lots of errors when I open .vimrc file and sometimes other files too, a bit random I guess

and here is my airline settings
" Airline

" Tabline/Buffer line
set showtabline=2
set tabline="%1T"

" Find out current buffer's size and output it.
function! FileSize()
  let bytes = getfsize(expand('%:p'))
  if (bytes >= 1024)
    let kbytes = bytes / 1024
  endif
  if (exists('kbytes') && kbytes >= 1000)
    let mbytes = kbytes / 1000
  endif

  if bytes <= 0
    return '[empty file] '
  endif

  if (exists('mbytes'))
    return mbytes . 'MB '
  elseif (exists('kbytes'))
    return kbytes . 'KB '
  else
    return bytes .  AirlineInit()
  let g:airline_section_x = airline#section#create(['%{ObsessionStatus()} %{FileSize()}', get(g:, 'airline_section_x', g:airline_section_x)])
endfunction
autocmd User AirlineAfterInit call AirlineInit()

I've had the same errors lately, propably since upgrading neovim a few days ago. The problem seems to be the modeline that sets the filetype. Opening a file containing only # vim: ft=cfg will give me these errors. It does not seem to happen with vim.

But this doesn't happen though if I open the file from inside vim itself, it only happens when I open vim with the file.
This shows erros
$ vim <file>

This doesn't
$ vim
# vim is now opened & then inside vim
:e <file>

please report to the neovim bugtracker then.

It is already fixed here https://github.com/neovim/neovim/issues/4471#issuecomment-211224739


JN-1090 migration

DESCRIPTION (include screenshots, and mobile screenshots for participant UX)
Support migration from pepper to Juniper.
Pepper Import code to look at pepper study (current focus: AT) and generate SurveyJS conf files to be imported/used to create surveys in Juniper
TO TEST:  (simple manual steps for confirming core behavior -- used for pre-release checks)
Run PepperImportCliApp App
O/P will be ATCP survey files under /out directory in SurveyJS format.
Not everything needed is automated and need manual tweaks
Manual edits:
Search and replace in all out/*.conf files
"required" with "isRequired"
Generated files: jsonContent can be used to validate in https://surveyjs.io/create-free-survey
OR
use 1 or more generated files to create new surveys in existing study or new study
Some text translations need edits and few other like below stuff should be handled manually
Dynamic text, calculated values, header/footer text, tool tips, validations..
All the manual edits and improvements needed to this PepperImportCli will be included in a Document as part of handover.


Release v0.2.6 (Patch)

Publish VSCode Trace Extension v0.2.6
Signed-off-by: Neel Gondalia<EMAIL_ADDRESS>

The following 1 GitHub releases will be created once this pull request got merged.
Release v0.2.6 with changes since v0.2.5

Release v0.2.6 (Patch) 4a9b4ff
Handle multiple experiments with the same name (#240) 1da51d5
[ci] harmonize release doc, add dhelper scripts 454da97
Make small adjustment to satisfy prettier 97f04d1
Ran 'yarn upgrade' following update of several dependencies 82b1c02
[npm packages] use solid versions of our packages ac0a0ea
Merge pull request #239 from ngondalia/fixStateUpdateInTraceViewerContainer 389459c
Add UI blocking overlay when server is offline 771be45
Propagate Server Status Change to All Webviews 1af201e
Fix handling of state in doHandleOutputAddedMessage 9dad638
Remove duplicate dispose listener in opened traces view provider b882747
Update READMEs 03f2b08
asExternalUri for Automatic Port Forwarding f431d71
Refresh trace viewer after server URL preference changes f012ced
Add method to set server status in TraceServerStatusService 86ade94
Ignore connection status listener notification in constructor ab0fa48
Add default dispose() method to AbstractTraceExplorerProvider 77bf4f0
Fixed message passing to webviews via AbstractTraceExplorerProvider. a5a8f2c

I'm having a look- should not take long


Using parse_list for security_group_ids

As terraform.tfstate is coming like:
"security_groups.xxxxx": "sg-xxxxx",
I think parse_list is needed same than "vpc_security_group_ids"

Thanks @enxebre!


Support for Privilege Access Group

We would like to use terraform to allow JIT groups to get conditional access, like effective / or active.

Hi @djsly, thanks for requesting this. Whilst this repository hosts the SDK used by the TF AzureAD Provider, feature requests intended for the provider should be requested in that issue tracker.
I'm happy to leave this open as an SDK feature request but if your intention was to request for TF support, can I ask you to complete the feature request template for that project, as that will enable us to better understand your request and to track it. Thanks!


chore: add reviewers to the Dependabot configuration

We can assign one or more reviewers to PRs that Dependabot opens (docs), and perhaps it’s worthwhile adding to the configuration? Not sure if we want to comment that out or leave it as an active feature.
We we add this change, we probably should document it in our README.

Or comment it out. I just wanted this in there for documentation purposes (and because I know we’ll use it in other repos).

Or comment it out. I just wanted this in there for documentation purposes (and because I know we’ll use it in other repos).

SGTM.


Fix write to and query from cluster

Required for all non-trivial PRs

[X] Rebased/mergable
[X] Tests pass
[X] CHANGELOG.md updated
[X] Sign CLA (if not already signed)

@mjdesa


agent is lost [BUG]

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

DeepFlow Component
Agent
What you expected to happen
按照All-in-One 快速部署教程部署了一个k8s集群，然后部署两个demo，发现agent lost。
How to reproduce
No response
DeepFlow version
[root@szvphisprb55278 ~]# kubectl exec -it -n deepflow deploy/deepflow-server -- deepflow-server -v
2023/05/09 15:43:17 ENV K8S_NODE_NAME_FOR_DEEPFLOW=szvphisprb55278; K8S_NODE_IP_FOR_DEEPFLOW=<IP_ADDRESS>; K8S_POD_NAME_FOR_DEEPFLOW=deepflow-server-5f78f5995c-4wh9d; K8S_POD_IP_FOR_DEEPFLOW=<IP_ADDRESS>; K8S_NAMESPACE_FOR_DEEPFLOW=deepflow
Name: deepflow-server community edition
Branch: main
CommitID: daa89f6ae842ea2e27a94d78c5440d58ea5d96c3
RevCount: 6898
Compiler: go version go1.18.7 linux/amd64
CompileTime: 2022-10-28 12:21:43
[root@szvphisprb55278 ~]# kubectl exec -it -n deepflow ds/deepflow-agent -- deepflow-agent -v
Defaulted container "deepflow-agent" out of: deepflow-agent, configure-sysctl (init)
6905-4b4c6d2b6ebbd1f6420c1b81c4a1603eef2df7de
Name: deepflow-agent community edition
Branch: main
CommitId: 4b4c6d2b6ebbd1f6420c1b81c4a1603eef2df7de
RevCount: 6905
Compiler: rustc 1.64.0 (a55dd71d5 2022-09-19)
CompileTime: 2022-10-29 04:55:39
DeepFlow agent list
[root@szvphisprb55278 ~]# deepflow-ctl agent list
NAME                    TYPE       CTRL_IP          CTRL_MAC           STATE    EXCEPTIONS GROUP
szvphisprb55278-V120673 K8S_VM     <IP_ADDRESS>    fa:16:3e:3d:8a:0f  LOST     32768      default
Kubernetes CNI
calico
Operation-System/Kernel version
No response
Anything else
以下是agent日志：
[2023-05-09 15:33:01.773748 +08:00] INFO [src/rpc/session.rs:313] rpc IP changed to controller <IP_ADDRESS> from unavailable controller <IP_ADDRESS>
[2023-05-09 15:33:01.773980 +08:00] ERROR [src/rpc/session.rs:142] dial server(<IP_ADDRESS>) failed transport error
[2023-05-09 15:33:01.774011 +08:00] WARN [src/config/config.rs:128] rpc client not connected
[2023-05-09 15:34:01.775108 +08:00] INFO [src/rpc/session.rs:313] rpc IP changed to controller <IP_ADDRESS> from unavailable controller <IP_ADDRESS>
[2023-05-09 15:34:01.775373 +08:00] ERROR [src/rpc/session.rs:142] dial server(<IP_ADDRESS>) failed transport error
[2023-05-09 15:34:01.775416 +08:00] WARN [src/config/config.rs:128] rpc client not connected
[2023-05-09 15:35:01.776178 +08:00] INFO [src/rpc/session.rs:313] rpc IP changed to controller <IP_ADDRESS> from unavailable controller <IP_ADDRESS>
[2023-05-09 15:35:01.776418 +08:00] ERROR [src/rpc/session.rs:142] dial server(<IP_ADDRESS>) failed transport error
[2023-05-09 15:35:01.776451 +08:00] WARN [src/config/config.rs:128] rpc client not connected
[2023-05-09 15:36:01.780247 +08:00] INFO [src/rpc/session.rs:313] rpc IP changed to controller <IP_ADDRESS> from unavailable controller <IP_ADDRESS>
[2023-05-09 15:36:01.780489 +08:00] ERROR [src/rpc/session.rs:142] dial server(<IP_ADDRESS>) failed transport error
[2023-05-09 15:36:01.780530 +08:00] WARN [src/config/config.rs:128] rpc client not connected
[2023-05-09 15:37:01.782409 +08:00] INFO [src/rpc/session.rs:313] rpc IP changed to controller <IP_ADDRESS> from unavailable controller <IP_ADDRESS>
[2023-05-09 15:37:01.782670 +08:00] ERROR [src/rpc/session.rs:142] dial server(<IP_ADDRESS>) failed transport error
[2023-05-09 15:37:01.782703 +08:00] WARN [src/config/config.rs:128] rpc client not connected
[2023-05-09 15:38:01.783787 +08:00] INFO [src/rpc/session.rs:313] rpc IP changed to controller <IP_ADDRESS> from unavailable controller <IP_ADDRESS>
[2023-05-09 15:38:01.784038 +08:00] ERROR [src/rpc/session.rs:142] dial server(<IP_ADDRESS>) failed transport error
[2023-05-09 15:38:01.784072 +08:00] WARN [src/config/config.rs:128] rpc client not connected
[2023-05-09 15:39:01.784718 +08:00] INFO [src/rpc/session.rs:313] rpc IP changed to controller <IP_ADDRESS> from unavailable controller <IP_ADDRESS>
[2023-05-09 15:39:01.784993 +08:00] ERROR [src/rpc/session.rs:142] dial server(<IP_ADDRESS>) failed transport error
[2023-05-09 15:39:01.785026 +08:00] WARN [src/config/config.rs:128] rpc client not connected
[2023-05-09 15:40:01.786500 +08:00] INFO [src/rpc/session.rs:313] rpc IP changed to controller <IP_ADDRESS> from unavailable controller <IP_ADDRESS>
[2023-05-09 15:40:01.786750 +08:00] ERROR [src/rpc/session.rs:142] dial server(<IP_ADDRESS>) failed transport error
[2023-05-09 15:40:01.786782 +08:00] WARN [src/config/config.rs:128] rpc client not connected
[2023-05-09 15:41:01.788210 +08:00] INFO [src/rpc/session.rs:313] rpc IP changed to controller <IP_ADDRESS> from unavailable controller <IP_ADDRESS>
[2023-05-09 15:41:01.788437 +08:00] ERROR [src/rpc/session.rs:142] dial server(<IP_ADDRESS>) failed transport error
[2023-05-09 15:41:01.788479 +08:00] WARN [src/config/config.rs:128] rpc client not connected
[2023-05-09 15:42:01.790198 +08:00] INFO [src/rpc/session.rs:313] rpc IP changed to controller <IP_ADDRESS> from unavailable controller <IP_ADDRESS>
[2023-05-09 15:42:01.790435 +08:00] ERROR [src/rpc/session.rs:142] dial server(<IP_ADDRESS>) failed transport error
[2023-05-09 15:42:01.790487 +08:00] WARN [src/config/config.rs:128] rpc client not connected
[2023-05-09 15:43:01.792190 +08:00] INFO [src/rpc/session.rs:313] rpc IP changed to controller <IP_ADDRESS> from unavailable controller <IP_ADDRESS>
[2023-05-09 15:43:01.792412 +08:00] ERROR [src/rpc/session.rs:142] dial server(<IP_ADDRESS>) failed transport error
[2023-05-09 15:43:01.792463 +08:00] WARN [src/config/config.rs:128] rpc client not connected
[2023-05-09 15:44:01.794427 +08:00] INFO [src/rpc/session.rs:313] rpc IP changed to controller <IP_ADDRESS> from unavailable controller <IP_ADDRESS>
[2023-05-09 15:44:01.794702 +08:00] ERROR [src/rpc/session.rs:142] dial server(<IP_ADDRESS>) failed transport error
[2023-05-09 15:44:01.794738 +08:00] WARN [src/config/config.rs:128] rpc client not connected
[2023-05-09 15:45:01.795697 +08:00] INFO [src/rpc/session.rs:313] rpc IP changed to controller <IP_ADDRESS> from unavailable controller <IP_ADDRESS>
[2023-05-09 15:45:01.795966 +08:00] ERROR [src/rpc/session.rs:142] dial server(<IP_ADDRESS>) failed transport error
[2023-05-09 15:45:01.796011 +08:00] WARN [src/config/config.rs:128] rpc client not connected
以下是server日志：
2023-05-09 15:45:22.374 [INFO] [trisolaris/refresh] refresh.go:138 start generate refresh IPs from timed
2023-05-09 15:45:22.374 [INFO] [trisolaris.kubernetes] kubernetes.go:60 refresh cache cluster_id started
2023-05-09 15:45:22.374 [INFO] [trisolaris/metadata] metadata.go:201 start generate tap type from timed
2023-05-09 15:45:22.374 [INFO] [trisolaris/metadata] metadata.go:167 start generate metaData from timed
2023-05-09 15:45:22.374 [INFO] [trisolaris/node] node.go:580 start generate node cache data from timed
[mysql] 2023/05/09 15:45:22 packets.go:123: closing bad idle connection: unexpected read from socket
[mysql] 2023/05/09 15:45:22 connection.go:173: driver: bad connection
2023-05-09 15:45:22.374 [INFO] [trisolaris/metadata] metadata.go:203 end generate tap type from timed
2023-05-09 15:45:22.374 [INFO] [trisolaris/refresh] refresh.go:140 end generate refresh IPs from timed
2023-05-09 15:45:22.374 [INFO] [trisolaris/node] controller_discovery.go:70 controller name (szvphisprb55278), node_name (szvphisprb55278)
2023-05-09 15:45:22.375 [INFO] [trisolaris.kubernetes] kubernetes.go:76 refresh cache cluster_id completed
2023-05-09 15:45:22.375 [INFO] [trisolaris.kubernetes] kubernetes.go:60 refresh cache cluster_id started
2023-05-09 15:45:22.375 [INFO] [trisolaris.kubernetes] kubernetes.go:76 refresh cache cluster_id completed
2023-05-09 15:45:22.376 [INFO] [trisolaris/node] node.go:101 update tsdb info to db
2023-05-09 15:45:22.377 [INFO] [trisolaris/node] node.go:583 end generate node cache data from timed
2023-05-09 15:45:22.378 [INFO] [recorder.db] operator.go:82 update pod_group_port (lcuuid: 5426a628-9ab2-5b74-a1ef-f98d047eedd8, detail: map[name:ingester]) success
2023-05-09 15:45:22.378 [INFO] [recorder.cache] diff_base.go:1507 cache diff base update pod_group_port (detail: &{DiffBase:{Sequence:228 Lcuuid:5426a628-9ab2-5b74-a1ef-f98d047eedd8} Name:ingester SubDomainLcuuid:}) success
2023-05-09 15:45:22.378 [INFO] [recorder.updater] updater.go:77 to update (cloud item: {Lcuuid:5426a628-9ab2-5b74-a1ef-f98d047eedd8 Name:ingester-30033 Protocol:TCP Port:20033 PodGroupLcuuid:5deb379c-a676-4eb5-8d2a-eebb8b53e838 PodServiceLcuuid:7e45b782-3f72-4b5c-8c4c-22f73a4918e5 SubDomainLcuuid:}, diff base item: &{DiffBase:{Sequence:228 Lcuuid:5426a628-9ab2-5b74-a1ef-f98d047eedd8} Name:ingester SubDomainLcuuid:})
2023-05-09 15:45:22.383 [INFO] [recorder.db] operator.go:82 update pod_group_port (lcuuid: 5426a628-9ab2-5b74-a1ef-f98d047eedd8, detail: map[name:ingester-30033]) success
2023-05-09 15:45:22.383 [INFO] [recorder.cache] diff_base.go:1507 cache diff base update pod_group_port (detail: &{DiffBase:{Sequence:228 Lcuuid:5426a628-9ab2-5b74-a1ef-f98d047eedd8} Name:ingester-30033 SubDomainLcuuid:}) success
2023-05-09 15:45:22.383 [INFO] [recorder] recorder.go:164 domain (lcuuid: 768fe041-4507-5730-8074-850fbe1554af, name: k8s-d-FrBcoCxv8a) refresh completed
2023-05-09 15:45:22.384 [INFO] [trisolaris/metadata] metadata.go:172 end generate metaData from timed
2023-05-09 15:45:22.390 [INFO] [trisolaris/vtap] vtap.go:1106 start generate vtap cache data from timed
2023-05-09 15:45:22.391 [INFO] [trisolaris/vtap] kubernetes_sync.go:156 check kubernetes cluster data
2023-05-09 15:45:22.392 [INFO] [trisolaris/vtap] vtap.go:865 update vtap cache to db
2023-05-09 15:45:22.392 [INFO] [trisolaris/vtap] vtap.go:1108 end generate vtap cache data from timed
2023-05-09 15:45:26.099 [WARN] [config] rpc_config_synchronizer.go:180 No reachable server
[GIN] 2023/05/09 - 15:45:30 | 200 |      33.256µs |   <IP_ADDRESS> | GET      "/v1/health/"
[GIN] 2023/05/09 - 15:45:30 | 200 |      32.846µs |   <IP_ADDRESS> | GET      "/v1/health/"
2023-05-09 15:45:36.100 [WARN] [config] rpc_config_synchronizer.go:180 No reachable server
[GIN] 2023/05/09 - 15:45:40 | 200 |      35.614µs |   <IP_ADDRESS> | GET      "/v1/health/"
2023-05-09 15:45:46.101 [WARN] [config] rpc_config_synchronizer.go:180 No reachable server
[GIN] 2023/05/09 - 15:45:50 | 200 |      29.299µs |   <IP_ADDRESS> | GET      "/v1/health/"
[GIN] 2023/05/09 - 15:45:50 | 200 |      31.578µs |   <IP_ADDRESS> | GET      "/v1/health/"
2023-05-09 15:45:52.333 [INFO] [cloud] kubernetes_gather_task.go:97 kubernetes gather (k8s-d-FrBcoCxv8a) assemble data starting
2023-05-09 15:45:52.333 [INFO] [cloud] cloud.go:158 cloud (k8s-d-FrBcoCxv8a) assemble data starting
2023-05-09 15:45:52.333 [INFO] [cloud] cloud.go:160 cloud (k8s-d-FrBcoCxv8a) assemble data complete
2023-05-09 15:45:52.338 [INFO] [cloud.kubernetes_gather] pod_service.go:106 service (foo-svc) target_port not match
2023-05-09 15:45:52.338 [INFO] [cloud.kubernetes_gather] pod_service.go:193 service (foo-svc) pod group not found
2023-05-09 15:45:52.338 [INFO] [cloud.kubernetes_gather] pod_service.go:106 service (redis-master) target_port not match
2023-05-09 15:45:52.338 [INFO] [cloud.kubernetes_gather] pod_service.go:193 service (redis-master) pod group not found
2023-05-09 15:45:52.338 [INFO] [cloud.kubernetes_gather] pod_service.go:106 service (calico-typha) target_port not match
2023-05-09 15:45:52.338 [INFO] [cloud.kubernetes_gather] pod_service.go:193 service (calico-typha) pod group not found
2023-05-09 15:45:52.338 [INFO] [cloud.kubernetes_gather] pod_service.go:106 service (deepflow-agent) target_port not match
2023-05-09 15:45:52.338 [INFO] [cloud.kubernetes_gather] pod_service.go:193 service (deepflow-agent) pod group not found
2023-05-09 15:45:52.339 [INFO] [cloud.kubernetes_gather] pod_service.go:68 service (kubernetes) selector not found
2023-05-09 15:45:52.339 [INFO] [cloud.kubernetes_gather] pod_service.go:106 service (bar-svc) target_port not match
2023-05-09 15:45:52.339 [INFO] [cloud.kubernetes_gather] pod_service.go:193 service (bar-svc) pod group not found
2023-05-09 15:45:52.339 [INFO] [cloud.kubernetes_gather] pod_service.go:106 service (loo-svc) target_port not match
2023-05-09 15:45:52.339 [INFO] [cloud.kubernetes_gather] pod_service.go:193 service (loo-svc) pod group not found
2023-05-09 15:45:52.340 [INFO] [cloud.kubernetes_gather] pod.go:100 pod group (etcd-szvphisprb55278) type not support
2023-05-09 15:45:52.340 [INFO] [cloud.kubernetes_gather] pod.go:100 pod group (kube-controller-manager-szvphisprb55278) type not support
2023-05-09 15:45:52.340 [INFO] [cloud.kubernetes_gather] pod.go:100 pod group (kube-scheduler-szvphisprb55278) type not support
2023-05-09 15:45:52.340 [INFO] [cloud.kubernetes_gather] pod.go:100 pod group (kube-apiserver-szvphisprb55278) type not support
2023-05-09 15:45:52.341 [WARN] [genesis] genesis.go:167 get genesis sharing sync faild (rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:20035: connect: connection refused")
2023-05-09 15:45:52.341 [INFO] [cloud] kubernetes_gather_task.go:109 kubernetes gather (k8s-d-FrBcoCxv8a) assemble data complete
2023-05-09 15:45:56.102 [WARN] [config] rpc_config_synchronizer.go:180 No reachable server
[GIN] 2023/05/09 - 15:46:00 | 200 |      32.575µs |   <IP_ADDRESS> | GET      "/v1/health/"
2023-05-09 15:46:06.104 [WARN] [config] rpc_config_synchronizer.go:180 No reachable server
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Can you add wechat at the bottom of readme? Let's communicate on wechat

Try again after upgrading to the latest version


Store charts to cloud storage

@leafchild0 When the user uploads chart we can try to parse chart metadata but instead of saving the chart we can find an existing chart in db and reuse the url.
But it causes a problem when one chart could be related to multiple users. So what solution be better, duplicated chart records with a foreign key to the user or an extra table chart-user? Also, we shouldn't forget that different users can use different versions of these chats.

My opinion is an extra chart option. This is more flexible, we can have different version, updated ones, etc


Copter starts descending in Follow Me mode

I have added a small function in follow me mode for the copter to orbit a target when the target has stopped. However, the copter flies to the target and on detecting that it isn't moving starts descending.
I am not sure if it was trying to land as I quickly changed to Position Control everytime this happened.
http://logs.px4.io/plot_app?log=a71d3f38-e9f1-412d-812b-9444b91aa5c5
Here is the log where the target is driving in circles and the copter is following it. http://logs.px4.io/plot_app?log=7986d696-3c83-4908-8d3e-0f6f18a71f24
When I looked closely at my SITL logs, I found the same behaviour.
These are the setpoints I am using for the orbiting.
struct position_setpoint_triplet_s *pos_sp_triplet_circle = _navigator->get_position_setpoint_triplet();
pos_sp_triplet_circle->previous.valid = false;
pos_sp_triplet_circle->current.valid = true;
pos_sp_triplet_circle->next.valid = false;
pos_sp_triplet_circle->current.alt_valid = true;
pos_sp_triplet_circle->current.alt= _param_min_alt.get();
pos_sp_triplet_circle->current.type = position_setpoint_s::SETPOINT_TYPE_FOLLOW_TARGET;
pos_sp_triplet_circle->current.lat =_new_wp.lat;
pos_sp_triplet_circle->current.lon =_new_wp.lon;
pos_sp_triplet_circle->current.yaw_valid= true;
pos_sp_triplet_circle->current.yaw =heading;
pos_sp_triplet_circle->current.velocity_valid=true;
pos_sp_triplet_circle->current.vx = 15.0f;
pos_sp_triplet_circle->current.vy = 10.0f;
I'm suspecting I have misunderstood some of them and using them incorrectly. I would really appreciate if someone helped me figure out the issue as I haven't got any response on the gitter channel.
Apologies if this is not the right place for this question.

Custom code snippets like this are impossible to support. Let us know if there are any issues in vanilla Follow-Me mode.

@mhkabir I'm pretty sure it is something to do with altitude setpoint.
Is it not the right way to set the altitude in the position setpoint for Auto modes?


[new] - Implement aria-role-supports-attribute

Fixes #17
Thinking can just be renamed to role-supports-attribute or something of the sorts.
Still need to add README and doc file. Will do in the morning.

Coverage increased (+0.2%) to 99.109% when pulling e05739786857d99a7fcd5886de688dee1fdc6ac5 on new-rule into 47ab6e638108294f17fbe78bd56e234552ced900 on master.

Coverage increased (+0.3%) to 99.205% when pulling 393e926a3034907ac712d3ac44caa488166a4ea7 on new-rule into 47ab6e638108294f17fbe78bd56e234552ced900 on master.

👍

@lencioni thoughts on name? Mentioned in initial comment that i think it should be just reduced to role-supports-attribute

Looking at #27, we have the following similar names:

valid-aria-role -> aria-role
valid-aria-proptype -> aria-proptypes
role-requires-aria -> aria-props-for-role

I think this rule is most similar to role-requires-aria -> aria-props-for-role, but I'm noticing the name we chose to change that one to is ambiguous in the context of this rule. So, what if we call this rule role-supports-aria-props and the other one role-has-aria-props (or role-has-required-aria-props)?

Coverage increased (+0.3%) to 99.205% when pulling fc238d22c08cb2c53633232e28711fed2f7c391c on new-rule into 47ab6e638108294f17fbe78bd56e234552ced900 on master.

Awesome, I like it. Going to merge this, do the rename and maybe some other cleanup (with hasAttribute => getAttribute) then publish v1.0.0 today 🎉

I think that role-has-required-aria-props is clearer than role-has-aria-props FWIW. Looking forward to 1.0.0! Thanks for all your hard work on this. :)


promiseUtils.js got some problems

I have tried nested routes with need function in both components for fetching data. Then it crashes
export function sequence(items, consumer) {
  console.log(items)
  const results = [];
  const runner = () => {
    const item = items.shift();
    if (item) {
      return consumer(item)
        .then((result) => {
          results.push(result);
        })
        .then(runner);
    }

    return Promise.resolve(results);
  };

  return runner();
}

What error do you got?

@mayankchd it just hangs on the second promise. To reproduce the problem, you can add
App.need = [() => {
   return Promise.resolve('null')
}]

to test multi-dependency

@elaijuh  Thanks! Will be fixing it!

@elaijuh  we are passingvwhatever is returned from every element of need to store.dispatch,
in your case () => {    return Promise.resolve('null') } doesn't returns a valid action type or a thunk
Do
App.need = [() => {
  return (dispatch) => {
    return Promise.resolve('null');
  };
}];

Also nested routes with need function are working fine for me.


add esp8266 pwm lib

add AliosThings esp8266 pwm drive

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

近期遇到很多开发者，想要在Alios Things 中使用esp8266 的pwm 功能，请大家测试后帮助合入。谢谢！！

感谢 🌹 @lqq96

@lqq96 和您确认一下，这个pull request并没有把libpwm.a放到编译列表里去，是吧？


[ENH] Add ability to determine whether an inducing path exists between two nodes

Closes #70
Changes proposed in this pull request:

Adds a function to determine whether an inducing path exists between two nodes

Before submitting

[ ] I've read and followed all steps in the Making a pull request
section of the CONTRIBUTING docs.
[ ] I've updated or added any relevant docstrings following the syntax described in the
Writing docstrings section of the CONTRIBUTING docs.
[ ] If this PR fixes a bug, I've added a test that will fail without my fix.
[ ] If this PR adds a new feature, I've added tests that sufficiently cover my new functionality.

After submitting

[ ] All GitHub Actions jobs for my pull request have passed.

The tetrad implementation for reference.

@adam2392 one more question:

Neither the children method nor the parents method finds nodes connected through a bi-directed edge. Is there a function that finds child and parent nodes connected through bi-directed edges as well?

@adam2392 one more question:

Neither the children method nor the parents method finds nodes connected through a bi-directed edge. Is there a function that finds child and parent nodes connected through bi-directed edges as well?

You can query the networkx subgraph. Bidirected edges are stored using a nx.Graph.

Codecov Report

Merging #78 (317c0a2) into main (c1b4107) will decrease coverage by 4.68%.
The diff coverage is 16.66%.

@@            Coverage Diff             @@
##             main      #78      +/-   ##
==========================================
- Coverage   84.42%   79.74%   -4.68%
==========================================
  Files          34       39       +5
  Lines        2555     2849     +294
  Branches      687      761      +74
==========================================
+ Hits         2157     2272     +115
- Misses        251      418     +167
- Partials      147      159      +12

Impacted Files
Coverage Δ

pywhy_graphs/algorithms/pag.py
87.50% <16.66%> (-3.53%)
:arrow_down:

... and 10 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

@adam2392 so it turns out the "parents" method doesn't work on the bidirected sub-graph. I am using the neighbors method.(since in a bidirected graph a neighbor is also a parent.)

can you add test cases as well?
You can just construct various graphs on paper that follow the definition or not to test.

@adam2392 is this an appropriate amount of tests?

@adam2392 The implementation seems to be correct and all the tests are passing as well. Want to review?

@adam2392 I think I added all the tests you asked for. They worked without changing anything in the code. Can you take a look?

@aryan26roy thanks for iterating on this! Feel free to come to the Discord OH, or other time periods and ping the channel so we know we should discuss this if you have any questions.
Inducing paths are somewhat abstract at first tbh, so once the definition is clear, I think this will come out cleanly.

@adam2392 I have incorporated all the suggestions you gave in previous reviews except the simplifying the checks one(not sure how I would simplify this further, it looks like a neat abstraction to me). Can you take a look?

@adam2392 I made the suggested changes and some more.

Yeah, patching the bugs has wreaked havoc on my naming system. Will make everything better in my next pass.

@adam2392 The docs are not being built correctly, what am I doing wrong?

@adam2392 do you want me to fix the networkx CI issue in another PR? I can bump up the CI from [3.8, 3.10] to [3.9,3.10].

@adam2392 I have removed the example file. Do you want to merge now?

Thanks @aryan26roy !


[FR]Add servers section to the OpenAPI schema

Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find a similar feature request

Problem statement
As I mentioned in the #4587 some of the openapi-codegen generators (Qt/C++ client generator for sure) expects the servers section to be present in the schema descriptor yaml file, because they generating the API endpoints to the code.
The InvenTree generated schema lacks it so it has to be manually extended before generating code.
Suggested solution
It would be straightforward to add the servers section into the SPECTACULAR_SETTINGS in the settings.py, however I have no idea how can I 'smuggle' the re the base url.
Describe alternatives you've considered
Adding manually.
Examples of other systems

Do you want to develop this?

[ ] I want to develop this.

There is an active PR for openApi generation, maybe feedback regarding the schema should be placed there: https://github.com/inventree/InvenTree/pull/6319

@martonmiklos you are asking for the ability to have the local instance base URL in the servers section? as in, when you run invoke schema locally, the "server" will include your server URL?

@SchrodingersGat well I was not aware of the local invoke server command I have used the /schema/ endpoint so far. It would be good if via that endpoint the servers section would be filled with the same url base through what I downloading the schema.

Check out this PR - https://github.com/inventree/InvenTree/pull/6463 - I have made a change which allows this to be filled out, if you have a globally defined SITE URL

Closed by #6463


It cannot work after switching app back from background.

I'm using it on iOS for H.264 hardware encoding & decoding, it works fine, but when i put application into background and switch it back again,
the encoding and decoding will fail.

iOS does not allow camera to run in background so this will need special handling as it uses camera.


FIX - Improve feedback page styles and placement

Please add screenshots

Group by URL and Date filter

Please sync and fix the build


Error in initial operation on gazebo

When starting gazebo, the minipupper is in a strange posture and cannot simulate.
After type this command: ros2 launch mini_pupper_gazebo gazebo.launch.py

$ ros2 launch mini_pupper_gazebo gazebo.launch.py
[INFO] [launch]: All log files can be found below /home/banban/.ros/log/2023-09-01-13-37-40-074599-banban-G7-7588-14850
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [robot_state_publisher-1]: process started with pid [14854]
[INFO] [quadruped_controller_node-2]: process started with pid [14856]
[INFO] [state_estimation_node-3]: process started with pid [14858]
[INFO] [ekf_node-4]: process started with pid [14860]
[INFO] [ekf_node-5]: process started with pid [14862]
[INFO] [gzserver-6]: process started with pid [14864]
[INFO] [gzclient-7]: process started with pid [14866]
[INFO] [spawn_entity.py-8]: process started with pid [14868]
[INFO] [ros2-9]: process started with pid [14870]
[INFO] [ros2-10]: process started with pid [14872]
[INFO] [contact_sensor-11]: process started with pid [14874]
[quadruped_controller_node-2] [INFO] [1693543061.212924349] [rclcpp]: Successfully parsed urdf file
[robot_state_publisher-1] [INFO] [1693543061.213455802] [robot_state_publisher]: got segment base_inertia
[robot_state_publisher-1] [INFO] [1693543061.213563437] [robot_state_publisher]: got segment base_link
[robot_state_publisher-1] [INFO] [1693543061.213625520] [robot_state_publisher]: got segment imu_link
[robot_state_publisher-1] [INFO] [1693543061.213639825] [robot_state_publisher]: got segment lb1
[robot_state_publisher-1] [INFO] [1693543061.213653607] [robot_state_publisher]: got segment lb2
[robot_state_publisher-1] [INFO] [1693543061.213664836] [robot_state_publisher]: got segment lb3
[robot_state_publisher-1] [INFO] [1693543061.213675684] [robot_state_publisher]: got segment lbfoot
[robot_state_publisher-1] [INFO] [1693543061.213687788] [robot_state_publisher]: got segment lf1
[robot_state_publisher-1] [INFO] [1693543061.213701565] [robot_state_publisher]: got segment lf2
[robot_state_publisher-1] [INFO] [1693543061.213715678] [robot_state_publisher]: got segment lf3
[robot_state_publisher-1] [INFO] [1693543061.213730279] [robot_state_publisher]: got segment lffoot
[robot_state_publisher-1] [INFO] [1693543061.213738608] [robot_state_publisher]: got segment lidar_link
[robot_state_publisher-1] [INFO] [1693543061.213745979] [robot_state_publisher]: got segment lpb1
[robot_state_publisher-1] [INFO] [1693543061.213752984] [robot_state_publisher]: got segment lpb2
[robot_state_publisher-1] [INFO] [1693543061.213760163] [robot_state_publisher]: got segment lpf1
[robot_state_publisher-1] [INFO] [1693543061.213767441] [robot_state_publisher]: got segment lpf2
[robot_state_publisher-1] [INFO] [1693543061.213774711] [robot_state_publisher]: got segment rb1
[robot_state_publisher-1] [INFO] [1693543061.213782363] [robot_state_publisher]: got segment rb2
[robot_state_publisher-1] [INFO] [1693543061.213789938] [robot_state_publisher]: got segment rb3
[robot_state_publisher-1] [INFO] [1693543061.213797111] [robot_state_publisher]: got segment rbfoot
[robot_state_publisher-1] [INFO] [1693543061.213809101] [robot_state_publisher]: got segment rf1
[robot_state_publisher-1] [INFO] [1693543061.213822616] [robot_state_publisher]: got segment rf2
[robot_state_publisher-1] [INFO] [1693543061.213834960] [robot_state_publisher]: got segment rf3
[robot_state_publisher-1] [INFO] [1693543061.213951177] [robot_state_publisher]: got segment rffoot
[robot_state_publisher-1] [INFO] [1693543061.213966645] [robot_state_publisher]: got segment rpb1
[robot_state_publisher-1] [INFO] [1693543061.213976134] [robot_state_publisher]: got segment rpb2
[robot_state_publisher-1] [INFO] [1693543061.213985882] [robot_state_publisher]: got segment rpf1
[robot_state_publisher-1] [INFO] [1693543061.213995434] [robot_state_publisher]: got segment rpf2
[robot_state_publisher-1] [INFO] [1693543061.214004857] [robot_state_publisher]: got segment yellow_plate
[state_estimation_node-3] [INFO] [1693543061.237287027] [rclcpp]: Successfully parsed urdf file
[ekf_node-4] [WARN] [1693543061.242944880] [base_to_footprint_ekf]: Warning: Some linear velocity entries in parameter imu0_config are listed true, but an sensor_msgs/Imu contains no information about linear velocities
[ekf_node-4] Warning: imu/data is listed as an input topic, but all its update variables are false
[spawn_entity.py-8] [INFO] [1693543061.604064007] [spawn_entity]: Spawn Entity started
[spawn_entity.py-8] [INFO] [1693543061.604438977] [spawn_entity]: Loading entity published on topic /robot_description
[spawn_entity.py-8] /opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/qos.py:307: UserWarning: DurabilityPolicy.RMW_QOS_POLICY_DURABILITY_TRANSIENT_LOCAL is deprecated. Use DurabilityPolicy.TRANSIENT_LOCAL instead.
[spawn_entity.py-8]   warnings.warn(
[spawn_entity.py-8] [INFO] [1693543061.606682650] [spawn_entity]: Waiting for entity xml on /robot_description
[spawn_entity.py-8] [INFO] [1693543061.618583249] [spawn_entity]: Waiting for service /spawn_entity, timeout = 30
[spawn_entity.py-8] [INFO] [1693543061.619110484] [spawn_entity]: Waiting for service /spawn_entity
[spawn_entity.py-8] [INFO] [1693543062.375212760] [spawn_entity]: Calling service /spawn_entity
[gzserver-6] [WARN] [1693543063.174458417] [rcl]: Found remap rule '~/out:=/scan'. This syntax is deprecated. Use '--ros-args --remap ~/out:=/scan' instead.
[gzserver-6] [WARN] [1693543063.179295134] [rcl]: Found remap rule '~/out:=/scan'. This syntax is deprecated. Use '--ros-args --remap ~/out:=/scan' instead.
[gzserver-6] [WARN] [1693543063.192127768] [rcl]: Found remap rule '~/out:=data'. This syntax is deprecated. Use '--ros-args --remap ~/out:=data' instead.
[gzserver-6] [INFO] [1693543063.197501064] [imu.gazebo_ros_imu_sensor]: <initial_orientation_as_reference> is unset, using default value of false to comply with REP 145 (world as orientation reference)
[gzserver-6] [WARN] [1693543063.197869058] [rcl]: Found remap rule '~/out:=data'. This syntax is deprecated. Use '--ros-args --remap ~/out:=data' instead.
[spawn_entity.py-8] [INFO] [1693543063.208016277] [spawn_entity]: Spawn status: SpawnEntity: Successfully spawned entity [mini_pupper]
[INFO] [spawn_entity.py-8]: process has finished cleanly [pid 14868]
[gzserver-6] [WARN] [1693543063.376105117] [rcl]: Found remap rule 'odom:=odom/ground_truth'. This syntax is deprecated. Use '--ros-args --remap odom:=odom/ground_truth' instead.
[gzserver-6] [WARN] [1693543063.380631188] [rcl]: Found remap rule 'odom:=odom/ground_truth'. This syntax is deprecated.  Using 'joints' parameter.
[gzserver-6] [WARN] [1693543063.659175671] [joint_group_effort_controller]: 'ff_velocity_scale' parameters is not defined under 'gains.<joint_name>.' structure. Maybe you are using deprecated format 'ff_velocity_scale/<joint_name>'!
[gzserver-6] [WARN] [1693543063.659404420] [joint_group_effort_controller]: 'ff_velocity_scale' parameters is not defined under 'gains.<joint_name>.' structure. Maybe you are using deprecated format 'ff_velocity_scale/<joint_name>'!
[gzserver-6] [WARN] [1693543063.659594750] [joint_group_effort_controller]: 'ff_velocity_scale' parameters is not defined under 'gains.<joint_name>.' structure. Maybe you are using deprecated format 'ff_velocity_scale/<joint_name>'!
[gzserver-6] [WARN] [1693543063.659718183] [joint_group_effort_controller]: 'ff_velocity_scale' parameters is not defined under 'gains.<joint_name>.' structure. Maybe you are using deprecated format 'ff_velocity_scale/<joint_name>'!
[gzserver-6] [WARN] [1693543063.659865295] [joint_group_effort_controller]: 'ff_velocity_scale' parameters is not defined under 'gains.<joint_name>.' structure. Maybe you are using deprecated format 'ff_velocity_scale/<joint_name>'!
[gzserver-6] [WARN] [1693543063.659991104] [joint_group_effort_controller]: 'ff_velocity_scale' parameters is not defined under 'gains.<joint_name>.' structure. Maybe you are using deprecated format 'ff_velocity_scale/<joint_name>'!
[gzserver-6] [WARN] [1693543063.660105452] [joint_group_effort_controller]: 'ff_velocity_scale' parameters is not defined under 'gains.<joint_name>.' structure. Maybe you are using deprecated format 'ff_velocity_scale/<joint_name>'!
[gzserver-6] [WARN] [1693543063.660218560] [joint_group_effort_controller]: 'ff_velocity_scale' parameters is not defined under 'gains.<joint_name>.' structure. Maybe you are using deprecated format 'ff_velocity_scale/<joint_name>'!
[gzserver-6] [WARN] [1693543063.660356965] [joint_group_effort_controller]: 'ff_velocity_scale' parameters is not defined under 'gains.<joint_name>.' structure. Maybe you are using deprecated format 'ff_velocity_scale/<joint_name>'!
[gzserver-6] [WARN] [1693543063.660513306] [joint_group_effort_controller]: 'ff_velocity_scale' parameters is not defined under 'gains.<joint_name>.' structure. Maybe you are using deprecated format 'ff_velocity_scale/<joint_name>'!
[gzserver-6] [WARN] [1693543063.660676307] [joint_group_effort_controller]: 'ff_velocity_scale' parameters is not defined under 'gains.<joint_name>.' structure. Maybe you are using deprecated format 'ff_velocity_scale/<joint_name>'!
[gzserver-6] [WARN] [1693543063.660830180] [joint_group_effort_controller]: 'ff_velocity_scale' parameters is not defined under 'gains.<joint_name>.' structure. Maybe you are using deprecated format 'ff_velocity_scale/<joint_name>'!
[gzserver-6] [INFO] [1693543063.660981364] [joint_group_effort_controller]: Command interfaces are [effort] and state interfaces are [position velocity].
[gzserver-6] [INFO] [1693543063.661076100] [joint_group_effort_controller]: Using 'splines' interpolation method.
[gzserver-6] [INFO] [1693543063.663090075] [joint_group_effort_controller]: Controller state will be published at 50.00 Hz.
[gzserver-6] [INFO] [1693543063.669016749] [joint_group_effort_controller]: Action status changes will be monitored at 20.00 Hz.
[gzserver-6] [INFO] [1693543063.686188990] [controller_manager]: Loading controller 'joint_states_controller'
[ros2-10] Sucessfully loaded controller joint_group_effort_controller into state active
[gzserver-6] [INFO] [1693543063.698526927] [controller_manager]: Setting use_sim_time=True for joint_states_controller to match controller manager (see ros2_control#325 for details)
[gzserver-6] [INFO] [1693543063.703909699] [controller_manager]: Configuring controller 'joint_states_controller'
[gzserver-6] [INFO] [1693543063.704045059] [joint_states_controller]: 'joints' or 'interfaces' parameter is empty. All available state interfaces will be published
[ros2-9] Sucessfully loaded controller joint_states_controller into state active
[INFO] [ros2-10]: process has finished cleanly [pid 14872]
[INFO] [ros2-9]: process has finished cleanly [pid 14870]

solving!
sorry, I didn't install bsp package.


TF Remove the limitation of int max for dim_size in SparseSoftmax ops

This fix tries to address the simmiliat issue raised in #25701 where the dim_size in SparseSoftmax ops was set to . The restriction is likely unnecessary, due to historical reasons. This fix remove this limitation.
Refer PR #25702.

Nagging Reviewer @timshen91: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 14 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @timshen91: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 29 days with no activity and the awaiting review label has been applied.


CI: automatically create the system and api docs in travis ci and upload them to gh pages

firstly uploaded to ftp server

Please update the readme with the urls to the documentations before closing this issue.

The issue does not declare to add links to the readme.  Therefore the issue can closed. Furthermore, I add the links to the readme.


part of osra282: small fix for Partner#index controller action

removed .all from  Partner.all.paginate(:page => params[:page]) so it is similar with Sponsors#index
Partners#index pagination:
https://osraav.atlassian.net/browse/OSRA-282
https://github.com/AgileVentures/osra/pull/307
Sponsor#index pagination:
https://osraav.atlassian.net/browse/OSRA-343
https://github.com/AgileVentures/osra/pull/312

:shipit:


Installation has Failed! Unexpected error occured with code -1073740791

Acknowledgements

[X] I have searched for duplicate or closed bug reports
[X] I understand that I am supposed to provide my own legitimately obtained copy of the game

Describe the Bug
Good morning Cuttlefish, hope you are doing well.
I have been chatting to Barg over the past couple days to pick his brain on why the Jak 1 mods are all failing to install for me.
There is a very consistent error message that appears each time that says the following.

Installation has Failed! Unexpected error occured with code -1073740791

While the error code is always the same, depending on which mod I install, the file it fails to build on changes.
For example:

If I'm installing the Orb Hunt mod, the Test-Zone.jsonc file fails.
If I'm installing Jack Up mod, the ju-train.jsonc file fails.
If I'm installing the Rockpool mod, the rockpool.jsonc file fails.

This leads me to believe its not related to my files and something to do with the launcher, tooling kit and/or mod.
We have already checked my C++ library is updated, I have ample free space on my SSD and I've done fresh installs.
I'm also running a Windows 11 laptop with 12GB RAM which should meet all requirements.
The interesting thing is, all Jak 2 mods work perfectly.
Please see sample code below from the logs after the install failed on Rockpool.
Do you have any potential ideas as to why the builds are failing?
Thanks very much for all your assistance with this.
Error: invalid unordered_map<K, T> key
Build failed on custom_assets/jak1/levels/rockpool/rockpool.jsonc
Code:
(make "GROUP:iso" :verbose #f :force #f :report #f)
From macro: make-group
--------------------------------------------------------------------------------
Code:
(make-group "iso")
From macro: mi
Used in:
Program string:1
(mi)
^

--------------------------------------------------------------------------------
-- Compilation Error! --
Build failed.
Function:
top-level
Location:
Program string:1
(mi)
^
Code:
(mi)
--------------------------------------------------------------------------------

How To Reproduce
Unknown
Does this problem occur on original hardware or PCSX2?
Yes, it's unique to OpenGOAL
Expected Behavior
Should work lol
Environment Information
Windows 11, 12GB Ram, Latest OpenGOAL versions
Game Version
PAL
Have you set the game to something other than 60fps?
No

So sorry I never caught this man, I don't really check my github until I am close to releasing something. Please reach out on the discord if you're around if you ever need my assistance with anything :)


regression in maxAdbTotalmaxRss complex_layout_scroll_perf__devtools_memory

https://flutter-flutter-perf.skia.org/e/?begin=1603909324&end=1603931718&keys=X7469377cae2d91a391bef4f1e3972ea6&num_commits=50&request_type=1&xbaroffset=22247
Started at https://github.com/flutter/flutter/pull/69237; cc @jonahwilliams. I'm not really sure why only this regressed, and not a number of benchmarks, so I'm not convinced that this is the PR that caused it.

It does look related. The fix adding back --use-existing-app caused the memory usage to go back up to the level that it had been at for quite awhile before @jonahwilliams started working on drive. Closing as working as expected.


RxJS 5 bufferWithTimeOrCount?

So RxJS 5 currently not containing bufferWithTimeOrCount, is it planned to be added in the future?, anyway I was looking for comparable way to "do" bufferWithTimeOrCount in RxJS 5, should I create my own operator or there is a nicer combo with the already ported operators?

Hmmm... seems like an oversight. I think we can probably add an additional argument to bufferTime to cover this without impacting performance greatly.
Until we add that, you could use something like this:
(I haven't tested it, and it looks a little gross but with some tweaks it may work):
function bufferWithTimeOrCount(source, duration, bufferSize) {
  let reset = false;

  const buffers = source.scan((buffer, x) => {
    if (reset) {
      buffer = [];
      reset = false;
    }
    buffer.push(x);
    return buffer;
  }, []).share();

  const bufferCounted = buffers.filter(buffer => buffer.length < bufferSize);
  const timer = Observable.of(null).merge(bufferCounted).switchMap(() => Observable.timer(duration));

  return buffers.sample(timer.merge(bufferCounted)).do(() => reset = true);
}

Thank you for your patience and for bring this issue up for us, @avielfedida. We'll get it fixed.

Contributors or those looking to implement this:
The idea I have here is that we can add an optional maxBufferSize parameter to bufferTime (likewise with windowTime) that would default to Number.POSITIVE_INFINITY. Then rework the the operator to support that functionality.

Sorry if I have the details wrong, but bufferTimeOrCount only allows a single buffer at a time, right? And as soon as a buffer is flushed, the new buffer starts immediately? (e.g. this JSBin for single/double clicks)
It looks like in the current implementation of bufferWithTime, you'd have to purposefully limit the scheduling of opening multiple buffers and all, which sounds hard/like a lot of work.
I have a small implementation for bufferTimeOrCount with this base spec, but I don't know if this necessarily behaves as expected.


Update History.rdoc file for 1.4.0

@etagwerker - This addresses issue #321, based off of blog post (http://databasecleaner.github.io/2014/12/17/v1-4-0-is-out/) and commit history.

Looks good to me. Thanks for your contribution :D

666 Demonic commit :D


Why multiple theme approach?

Hey guys, I am glad to see a good attempt at creating a select2 and selectize angular component.  However I'm confused by the approach to have multiple themes/templates.
Since some of the components functionality is stored in the templates (hide/show etc..) it seems like it would be a better approach to get a consistent template down and then add CSS to style to get the bootstrap/select2/selectize look.
I would guess having multiple templates/themes the way it is currently done would add unnecessary complexity and bloat to the project.  This is especially the case with the bower release, where you are forced to send ALL themes to the browser because they're bundled with the code.
Is there a reason that approach was not tried or abandoned?
Anyway, thanks for the valiant efforts so far!

My issue was answered.


Naming the two sets of old values in nm.entity.Entity

Currently we have oldX/oldY/oldZ and M/N/O (the latter has not been deobf'd).
I'm thinking lerpX/lerpY/lerpZ would be good names for M/N/O. They are not as heavily used as oldXYZ.
Here's what they are used for anyway:

oldXYZ is for the previous physical position and is used in physics calculations.
MNO is for the previous visible position and is used for linearly interpolating visible positions between ticks.

Most cases of MNO look like this:
    this.c = this.b.M + (this.b.x - this.b.M) * a1;
    this.d = this.b.N + (this.b.y - this.b.N) * a1;
    this.e = this.b.O + (this.b.z - this.b.O) * a1;

Or this:
    this.M = this.x;
    this.N = this.y;
    this.O = this.z;

EntityRendererEntity has an exception, however this is similar to the first case:
    EntityRenderer.a(a1.getBoundingBox(), a2 - a1.M, a3 - a1.N, a4 - a1.O);

Alternative names would be prevPhysXYZ and prevVisXYZ or prevRenderXYZ. (Or old instead of prev.) This way it'd be more obvious what these are used for. Though I do like the sound of lerpXYZ for M/N/O, too. Would prefer lerp, though I wanted to throw this in as well, since it was mentioned in the IRC chat.

Using lerp here doesn't really make sense for MNO, as it's not actually a value that's come as a result of a linear interpolation, but rather a value that's used to calculate the interpolated value. cde would be far better off as lerp than MNO.

lerp would make no more sense for cde as it would for MNO. They are both "previous keyframes".

https://github.com/FabricMC/pomf/commit/474177781c180b1fd8b542c55c60056441e5d7a9


fix(tracing): fix span name high cardinality

Summary
Service, operation name, and then resource are the three levels of grouping in DataDog.
The operation name(also called span name) is used to filter Datadog APM/service board. High cardinality makes it unusable.
Checklist

[x] The Pull Request has tests
[x] There's an entry in the CHANGELOG
[ ] There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Issue reference
Fix FTI-4882

Please evaluate this change from a breaking change/behavior perspective.

Please evaluate this change from a breaking change/behavior perspective.

It IS a breaking change. I'm handing it over to @kikito so the decision is on him now.

Closing because we are rewriting the implementation.


[2] Support Typescript DB schemas

Get the repo ready to host DB schemas with typescript

Moves test/rumors-db to src/rumors-db so that types in rumors-db can be used in src/
Make eslint-import support Typeascript
Installs zod

coverage: 88.316%. remained the same
when pulling 9beae143000df19642f8fdfc768661e5c40256df on ts-schema
into cba1a85a084dc8a6f688a2cfe16e8f0ef9bdaef5 on update-prettier.


Redundant assignement of textures_to_storage[i]->used_in_compute

Godot version
4.0 ff0b5f8fa1be4ccd5b8de1d9d49f8a4b71439f63
Issue description
https://github.com/godotengine/godot/blob/ff0b5f8fa1be4ccd5b8de1d9d49f8a4b71439f63/drivers/vulkan/rendering_device_vulkan.cpp#L7549-L7558

Removing the duplicate assignments is trivial, then there's the question of whether this is a copy-paste mistake which initially meant to add used_in_transfer too?
                uint64_t used_in_frame = 0;
                bool used_in_transfer = false;
                bool used_in_raster = false;
                bool used_in_compute = false;


Crash with width: '100%', height: '100%'

How did you link to the library (autolinking, manual, rn link, cocoapods)?

autolinking

What version of React Native?

0.71.4

What version of the library?

1.0.2

iOS/Android version?

IOS 16.2

Did the problem happen after updating React Native?

no

Are you using the library for the first time?

yes

It's a bug? Provide a link to a minimal reproduction case.

<PdfRendererView
      source={value}
      style={{borderRadius: 30, width: '100%', height: '100%'}}
    />

crashes with style width: '100%', height: '100%'
borderRadius,backgroundColor are ignored as well if singlePage={false}
0   yliyo                      	       0x102fcc7a8 -[RNPdfRendererModule handlePageChange:] + 512 (RNPdfRendererModule.m:55)
1   yliyo                      	       0x102fcc79c -[RNPdfRendererModule handlePageChange:] + 500 (RNPdfRendererModule.m:55)

React Native uses flex box, so you dont need to use width: '100%', height: '100%', you jjst need flex: 1.
The PdfRenderer is flex: 1 by default.
About backgroundColor, it's applied to PdfRenderer behind the page, so you always will see the page background in the front.
borderRadius have never tried before, but I think that should work, I can do some testes here.
Have you used overflow: 'hidden' with borderRadius?

React Native uses flex box, so you dont need to use width: '100%', height: '100%', you jjst need flex: 1.
The PdfRenderer is flex: 1 by default.
About backgroundColor, it's applied to PdfRenderer behind the page, so you always will see the page background in the front.
borderRadius have never tried before, but I think that should work, I can do some testes here.
Have you used overflow: 'hidden' with borderRadius?

i added later that it works with singlePage true but with single page false none of styles i tried apply

It's hard to say without seeing the code, in the Sample project and our internal projects it's working fine.
If you like, create a sample project and upload it to Github, so we can have a look.

I just tested it here, and found that for some reason the borderRadius is ignored on Android and on iOS it causes the crash you reported.
So, I released a new version that removes borderRadius from the style and add “Limitations” section in the README.
https://github.com/douglasjunior/react-native-pdf-renderer#limitations

Hello @douglasjunior
this my code for i have crash issue when i double tap on pdf.can you please give me a suggestion for what should i do for that.
<View style={{ flex: 1, borderRadius: 24, overflow: 'hidden' }}>
<PdfRendererView
style={styles.pdf}
source={source?.uri}
maxZoom={6}
singlePage={singlePage}
distanceBetweenPages={16}
onPageChange={(current, total) => {
console.log('onPageChange', { current, total });
}}
/>


Access permissions when importing a new file into the "Assets" project directory

Hi @pepcots,
we are facing an issue when trying to import a local file from the system to the project's Asset folder. We have the following code, which opens a Window's popup where you can browse and select a file from local to import:
        OPENFILENAME ofn;
	char szFile[260] = { 0 };

	ZeroMemory(&ofn, sizeof(ofn));
	ofn.lStructSize = sizeof(ofn);
	ofn.hwndOwner = NULL;
	ofn.lpstrFile = szFile;
	ofn.lpstrFile[0] = '\0';
	ofn.nMaxFile = sizeof(szFile);
	ofn.lpstrFilter = "All Files (*.*)\0*.*\0";
	ofn.nFilterIndex = 1;
	ofn.Flags = OFN_PATHMUSTEXIST | OFN_FILEMUSTEXIST;

	if (GetOpenFileName(&ofn) == TRUE) {
		std::filesystem::path selectedFile = szFile;
		std::filesystem::path destinationPath = "Assets/" + selectedFile.filename().string();

		try {
			// Check if the selected file exists
			if (!std::filesystem::exists(selectedFile)) {
				MessageBox(NULL, "Selected file does not exist.", "Error", MB_OK | MB_ICONERROR);
				return;
			}

			// Check if the destination file already exists
			if (std::filesystem::exists(destinationPath)) {
				int result = MessageBox(NULL, "File already exists in 'Assets' directory. Overwrite?", "Warning", MB_YESNO | MB_ICONWARNING);
				if (result == IDNO) {
					return;
				}
			}

			// Copy the file
			std::filesystem::copy_file(selectedFile, destinationPath, std::filesystem::copy_options::overwrite_existing);

			MessageBox(NULL, "File imported to 'Assets' directory.", "Import Successful", MB_OK);
			LOG("EDITOR: File '%s' imported to 'Assets' directory SUCCESSFULLY...", szFile);
		}
		catch (const std::exception& e) {
			MessageBox(NULL, e.what(), "Error due to Access Permissions or other.", MB_OK | MB_ICONERROR);
		}
	}

Whenever you try to import a file from outside the current directory ( '$(ProjectSol)/Editor' ), the program crashes with the following error:

But if you import a file from the current directory, it works, and I think the error goes with the program insufficient permissions from Windows. We try it running it as an Admin and still doesn't work 😞.
I don't know if you can think of any possible solution or anything we can do to import local files from any directory of the pc to the project's Assets folder. Or if there's another easier way...
Thanks anyway.

Hi @AdriaPm !
I'm pretty sure it has nothing to do with the permissions.
It seems to be an unhandled filesystem exception, so, it should be an error in your code.
Maybe it has to do with this:
"Assets/" + selectedFile.filename().string()
Take care about operators and operand, in this case, the left operand is a char*.
Try it with:
string("Assets") + selectedFile.filename().string()
If you want to create a MessageBox when permissions are failing,m try to catch only the exception that represents that


Support rename columns

For @elixir-lang/ecto-adapters,

[x] MySQL
[x] PostgreSQL
[ ] MSSQL
[x] SQLite
[ ] MongoDB

Here is the relevant commit: https://github.com/elixir-lang/ecto/commit/1fc57c3b61b38985d78ae459170f25d1628dd95f. Just duplicate the changes and unit tests added to PostgreSQL.

SQLite: https://github.com/jazzyb/sqlite_ecto/commit/ee82c27c363519f607cc4ba01726f1448518251a

MongoDB: https://github.com/michalmuskala/mongodb_ecto/commit/3145129243992ebefa239bb0bb43ccc0b14a541d

MSSQL: livehelpnow/tds_ecto@3b530308e29e94a8bce1b11ad061ddde9472fcb2


can't login with my 3bot id but other ids works fine

can't use my 3bot id to login and checked the identity page and the account was verified.
I receive the notification on the app but when I choose the emoji i got an Incorrect username or password. error and these logs

on a peertube instance deployed from the weblet: https://pt111ptest.gent01.dev.grid.tf/
but other ids can login on the same instance.

Facing same issue here while trying to login on a taiga instance on mainnet!

Linked comment says issue is solved on TF Connect side.


/images/.../json: fix port parsing

Fix a bug when parsing the ExposedPorts of the image that lead to
panics when the field was set.  The OCI image spec allows three valid
formats: tcp/port, udp/port and port
Fixes: #6490
Reported-by: @jgallucci32
Signed-off-by: Valentin Rothberg<EMAIL_ADDRESS>

@baude @giuseppe @jwhonce @mheon @rhatdan PTAL

LGTM
But what happens when the user just specifies port.  Does this just default to tcp or udp or are you supposed to use both?

LGTM
But what happens when the user just specifies port. Does this just default to tcp or udp or are you supposed to use both?

Then it defaults to tcp. That's what the spec wants:
https://github.com/containers/libpod/pull/6491/files#diff-2c1834810ca2c977e6dec2367e27701eR341-R342

/lgtm


Documentation error for QR Code generation

Issues with Existing Topic
Enabling QR Code generation for authenticator apps in ASP.NET Core
Great article!  I did find two issues.
First issue
In the Adding QR Codes to the 2FA configuration page section change:
Views\Account\Manage\EnableAuthenticator.cshtml (MVC)
to
Views\Manage\EnableAuthenticator.cshtml (MVC)
Second issue
In the Change the site name in the QR Code section change:
The site name in the QR Code is taken from the project name you choose when initially creating your project. You can change it by looking for the GenerateQrCodeUri(string email, string unformattedKey) method in the EnableAuthenticator.cshtml.cs file.
to
The site name in the QR Code is taken from the project name you choose when initially creating your project. You can change it by looking for the GenerateQrCodeUri(string email, string unformattedKey) method in the Pages\Account\Manage\EnableAuthenticator.cshtml.cs (Razor Pages) or Controllers\AccountController.cs (MVC).
Noral

@NoralK Thank you for reporting this issue! I've created a pull request to address it.


Macro not saved

Problem:

Installed as per instructions with default options.
Created macro on q
Ran command MacroSave q, entered macro name at prompt, got message saying "Macro NAME saved."
But no write to actual macro file.

Troubleshooting:

Created empty macros.json in case it needs to exist first -- no effect
Experimented with macro name formats, e.g., no spaces, all lowercase -- no effect

System:

linux debian/testing 6.6.13-1 (2024-01-20)
tmux 3.3a
alacritty 0.12.2
NVIM v0.9.5, Build type: Release, LuaJIT 2.1.1692716794

Love the concept of your plugin. Really hope it works for me some day.

Can you see it when you do MacroSelect?

It did, which sent me on a journey of discovery. The json_file_path I was setting was a symlink to another file. Turns out this plugin silently trashes the symlink and creates a regular file in its place. I was checking the target file which remained empty and no longer had a symlink pointing to it.
I also noticed errors like cp: not writing through dangling symlink '/home/david/.local/share/nvim/nvim-macros/backups/20240208222802_macros.json.bak being written transiently at the cursor location, but disappearing when I moved the cursor!
I'm glad to have solved the problem, but wonder whether nvim-macros should respect symlinks set as json_file_path. Failing that, perhaps it could signal a warning if the json_file_path is a symlink (or anything other than a regular file). Failing that, perhaps a warning on the README page?
Thanks for your help. If you take up my first or second suggestion above I'd be happy to test it.

For some reason I am unable to reproduce it. How are you making symlinks? I made a symlink from my config macros.json to home macros.json and it works as expected. Can you tell me the command you used? Maybe there is a typo in plugin spec that is why it is creating a new file.

Can you check now? Before doing that, just delete backup folder which is in home/david/.local/share/nvim/nvim-macros and make sure that the symlink file exists before saving and make sure not typos in json_file_path. This should now work properly with saving and backups should work aswell.

It's working perfectly with symlinks now. I've tried the default json_file_path and a custom location. I've also confirmed the backup files are saving correctly. This plugin is going to save me a lot of time. Thanks for your effort in creating it.


string token to NSData deviceToken

In RNCPushNotificationIOS the function didRegisterForRemoteNotificationsWithDeviceToken:(NSData *)deviceToken takes the deviceToken as NSData and converts it to a string.
Can anyone tell me, if the opposite (converting the string back to the original NSData object) would be possible or how this may look?

same problem


When geomancy spell is casted, update the farming widget with up-to-date information

Is your feature request related to a problem? Please describe.
Runelite has an issue with the way herbs are tracked, sometimes timing the completion incorrectly. See this issue: https://github.com/runelite/runelite/issues/2491
Describe the solution you'd like
The geomancy spell gives you an interface with all information of all patches, along with their growth timers and their progression, diseased etc. When casting this spell, the farming timer widget could access this information and update all the patches in the widget. This could then be used to create accurate timing of when the patch will be finished or of any diseases.
Describe alternatives you've considered
Currently you can manually track the patches via geomancy, but this requires being on lunars and constant casting of geomancy to check on the patches.
Additional context
Here is what the geomancy spells look like for anyone in the unknown.
https://i.imgur.com/jmQgXTK.png
Example: https://i.imgur.com/WnvmCWT.png
Geomancy displays the giant seaweed as being grown but Runelite still thinks it is growing.

I only just realized that the timers aren't updated this way.
This is especially helpful now that we have the Kronos plant.

Was this ever implemented?

No, not yet.

Surprised this hasn't been implemented after all this time.


Upgrading to 7.1.0 from 7.0.0, now we can't po anything in lldb due to GTMSessionFetcher import issue.

Describe the bug
We are seeing issues in lldb related to GTMSessionFetcher since updating to 7.1.0, where it complains it cannot import GTMSessionFetcher any time we try to po a value from our code in the debugger — which is obviously very bad news.
I'm far from an expert on this but in our case the problem "goes away" if we change the conditional import in GIDGoogleUser.h https://github.com/google/GoogleSignIn-iOS/blob/ec20caf39917e3a50905776db1713b37c6b33840/GoogleSignIn/Sources/Public/GoogleSignIn/GIDGoogleUser.h#L26 so that it never uses the @import modular import variant.
Why this is suddenly a problem - as this has been in the GoogleSignIn code for a while – is not clear. We relatively recently (months back) added one SPM package to our app. The rest are all Cocoapods, including GSI and its dependencies. Perhaps this has triggered the problem, but we certainly only noticed it recently when switching from 7.0.0 to 7.1.0.
The clear implication is that SWIFT_PACKAGE is now defined for our builds where it wasn't previously, but this is breaking lldb for some reason, perhaps because GSI is still built with Cocoapods, not SPM?
To Reproduce
Sorry, we don't know.
Expected behavior
We should not have any issues using the debugger, least of all complaints about failure of lldb to import GTMSessionFetcher.
Screenshots
Environment

Browser: Xcode 15.2 / Xcode 15.3

Additional context

I was able to reproduce this problem in a sample app (linked below). I created an app with a Podfile depending on GoogleSignIn. I also added an arbitrary Swift Package from Apple. I then did pod install to get GSI 7.1.0, and built and ran from the .xcworkspace.
All pos did not cause an lldb error. Only pos like po GIDSignIn.sharedInstance.currentUser caused an error. Note, if I did let user = GIDSignIn.sharedInstance.currentUser, and then po user, then there would be no lldb error. This might be a workaround for you...
One thing to note is that GSI 7.0.0 depended upon GTMAppAuth 2.0.0, where GSI 7.1.0 depends upon GTMAppAuth 4.1.1+. GTMAppAuth release 4.0.0 rewrote that library in Swift. In between GSI 7.0.0 and 7.1.0, this import in GIDGoogleUser.h:
// We have to import GTMAppAuth because forward declaring the protocol does
// not generate the `fetcherAuthorizer` property below for Swift.
#ifdef SWIFT_PACKAGE
@import GTMAppAuth;
#else
#import <GTMAppAuth/GTMAppAuthFetcherAuthorization.h>
#endif

changed to
#ifdef SWIFT_PACKAGE
@import GTMSessionFetcherCore;
#else
#import <GTMSessionFetcher/GTMSessionFetcher.h>
#endif

I made this change because GIDGoogleUser.h refers to GTMFetcherAuthorizationProtocol here, which is presumably why GTMAppAuth was previously imported in GIDGoogleUser.h (to grab GTMFetcherAuthorizationProtocol transitively via GTMAppAuth, which depends upon GTMSessionFetcher). GIDGoogleUser does not itself need anything from GTMAppAuth.
I created another test app that was pure Swift Package Manager (linked below). I put a breakpoint in a spot after I used let user = GIDSignIn.sharedInstance.currentUser, and did: po user and also po GIDSignIn.sharedInstance.currentUser. Neither produced an lldb error.
I think the issue has something to do with GTMAppAuth's change to Swift combined with CocoaPods...something. I'm not sure yet. This problem reminds me https://github.com/google/gtm-session-fetcher/issues/384, but looks like that was included in https://github.com/google/gtm-session-fetcher/releases/tag/v3.4.0, which I can confirm is being used in my tests below. Not sure...
I made a final test app that is pure CocoaPods (see link below) that depends upon GSI. I was able to po user and po GIDSignIn.sharedInstance.currentUser without a problem. So, I think this means that there is some issue with lldb and projects that are made from a combination of SPM and CocoaPods. It may or may not have anything to do with GTMAppAuth and GTMSessionFetcher.
I will do some more digging and ask around.
Test.zip (SPM + CocoaPods)
Test (SPM).zip
Test (CocoaPods Only).zip

Anecdotally, I think this issue demonstrates that mixing SPM and CocoaPods leads to some complexity. Is it possible for you to use one or the other?

First, @mdmathias thank you so much for going to the effort to repro this. It is really appreciated.
For us lldb chokes on anything we try — although if memory serves that is probably Swift symbols only as I don't recall recently trying to po ObjC expressions.
I suspect your theory is correct re: mixing SPM and Cocoapods however I know that we did not have this problem until updating to 7.1.0 — which we did ~2 weeks ago and we've had the SPM dep in there for months. So I think it is more nuanced than this. On paper I don't think there is any reason that mixing these should cause problems - they both just build libraries and frameworks. I don't think switching over fully to SPM is viable for us due to some legacy dependencies but it is already on my to-do list to investigate this.
Perhaps there is an issue with GSI where it does not have the dependency on GTMSessionFetcher fully expressed, or at least it seems like lldb doesn't see it available as a dependency so maybe there lies a clue? Because again, even with that SWIFT_PACKAGE check it worked before when it was transitive via GTMAppAuth.

Oh @mdmathias I will add... isn't it wrong that the SWIFT_PACKAGE branch of the #if is being used at all, because we're exclusively building GoogleSignIn and its deps using Cocoapods.
The fact that we do have SPM enabled in Xcode causes SWIFT_PACKAGE to be defined doesn't it? So this is falsely thinking that it has built modules and can use module imports for GTMSessionFetcherCore which it hasn't? So presumably when building with Cocoapods that is not defined or we wouldn't even get as far as a successful build — and so when lldb is running it evals the header (my poor understanding is that lldb will re-evaluate headers/re-imports) and SWIFT_PACKAGE is defined then so it fails?

I agree that the issue sits somewhere in between GTMAppAuth's conversion to Swift in versions 4+ and the mixing of SPM and CocoaPods, with what I expect to be the majority of the onus on the mixing of SPM and CocoaPods.
I don't think we can point too strongly to GTMAppAuth's Swift conversion since that is more or less moot: the library has full rights to be Swift or Objective-C. So, IMO, the issue has more to do with mixing the package managers.
This leads me to your next point about how the .xcworkspace project is somehow hitting the positive case in the #ifdef SWIFT_PACKAGE check in GIDGoogleUser.h. I'm not exactly sure how or why that's happening, but you're theory sounds right. I guess that kind of highlights my point about combining CocoaPods and SPM being a bit brittle and yielding undefined behavior.
I will keep investigating this on my end.

I think that the key thing is probably (?) that SWIFT_PACKAGE does not mean "built with SPM". It just means "SPM is supported by this toolchain". If correct, this makes it the wrong thing to switch on here... although I'm not sure there is a "right thing" available. I think what it's trying to do is determine if  GTMAppAuth was built as a modular framework, which seems like quite a different thing.

Sure, here's a translation:
I have a similar issue in my project, which involves a mix of Objective-C and Swift.
When I use pod 'GoogleSignIn' to import GoogleSignIn and write code in Swift, I encounter the following error when executing the po command in a Swift file:
error: couldn't IRGen expression: Clang importer error
error: module 'GTMSessionFetcherCore' not found
@import GTMSessionFetcherCore;

If I add @import GoogleSignIn; or#import <GoogleSignIn/GoogleSignIn.h>to the bridging-header.h file, and then execute the po command again, I get the following error:
error: Expression evaluation failed. Retrying without binding generic parameters
error: Could not evaluate the expression without binding generic types.

This problem has been bothering me for a long time and I hope to get help。

@fuchenxi I'm not sure how your project is set up, but our Swift sample project using CocoaPods does not have this issue.

If I provide my podfile file, can you analyze the problem?

I can confirm the same issue, mentioned by @marcpalmer .
I tried this hot fix:

I'm far from an expert on this but in our case the problem "goes away" if we change the conditional import in GIDGoogleUser.h

And it works for me.
But I wish there can be some fulfil solution to this bug.

@marcpalmer I've created #403 to address this. There is a sample project linked in a comment on that PR, but I would appreciate you pointing your dependency to https://github.com/google/GoogleSignIn-iOS/tree/mdmathias/fix-lldb-crash and testing in your project as well. Would you mind doing that? Let me know if this change fixes the issue for you. Thanks!

@marcpalmer gentile ping to test the branch in #403 if you don't mind. :)

@mdmathias I know I'm not Marc but I was encountering the same (or very similar issue). We mostly use cocoapods but also started integrating some Swift packages too and our po has been broken for a while so I can easily reproduce it and just saw it again this afternoon:

Once I changed (from v7.1) to your branch:
-  - GoogleSignIn (= 7.1.0)
+  - GoogleSignIn (from `https://github.com/google/GoogleSignIn-iOS.git`, branch `mdmathias/fix-lldb-crash`)

it no longer errors on me when I run a po command :) 👍

Thanks @heidiproske-qz!

Hi,
Any chance to have a new release with this fix ?

@cederache The draft release for v7.2.0 contains https://github.com/google/GoogleSignIn-iOS/pull/403, which fixes this issue.
I am hoping to get v7.2.0 released in the next few weeks (before the end of June).

Sorry I missed the past pings. I'll try to check this today!

@heidiproske-qz link to git branch you posted is not working :(

Sorry I missed the past pings. I'll try to check this today!

have you find a fix?

Hi, we've also been experiencing this issue. I see 8.0.0 on https://developers.google.com/identity/sign-in/ios/release but nothing on Cocoapods past 7.1.0. What's the status of 7.2.0/8.0.0?

v8.0.0 should be released the week of July 15. Apologies for that delay. In the meantime, you can depend upon the main branch, which should take care of this issue.

v8.0.0 should be released the week of July 15. Apologies for that delay. In the meantime, you can depend upon the main branch, which should take care of this issue.

@mdmathias main branch has same issue...

@yarodevuci are you sure? #403 fixes the issue and I cannot reproduce. Also, anecdotally, folks above with this issue confirmed that #403 fixes the problem.
If you still see this problem, could you please share reproduction steps?

Maybe I pulled the wrong branch ? I used main I used pods to pull latest from main branch

Hello @mdmathias, any news of publication of 7.2.0 or 8.0.0 version ?
It was expected this week but still nothing.. It's been a while since the bug have been fixed and aside from reverting back to 7.0.0 there isn't a clean solution proposed for us to get it (we are currently adding Google Sign-In via Firebase.zip asset)

@DeezeriOSTeam https://github.com/google/GoogleSignIn-iOS/issues/418


fix(docker): Use correct TOML syntax in Docker zebrad.toml

Motivation
The TOML syntax is still wrong in the Dockerfile.
(This time I'll leave the PR in draft until I've tested it.)
Solution
Comment out the disabled ports.
Testing
We need to run these commands in Google Cloud shell after the image has been built for this branch:
gcloud auth configure-docker us-docker.pkg.dev
docker run us-docker.pkg.dev/zealous-zebra/zebra/zebrad:sha-11a5cc6

Here is a full list of available images:
https://console.cloud.google.com/artifacts/docker/zealous-zebra/us/zebra/zebrad?project=zealous-zebra
Review
Anyone can review this PR, but @gustavovalverde reviewed the last one.
Reviewer Checklist

[ ] Will the PR name make sense to users?

[ ] Does it need extra CHANGELOG info? (new features, breaking changes, large changes)

[ ] Are the PR labels correct?
[ ] Does the code do what the ticket and PR says?
[ ] How do you know it works? Does it have tests?

Did PR https://github.com/ZcashFoundation/zebra/pull/5313 failed when running? I tested that it ran but should this output any specific information or should we have a way to validate that the service is working and not just running.
Can we internally execute something as a curl command to a specific endpoint or something that gives us an "expected" output?
This is mainly to confirm if we have a way that the service started but it did it successfully.

Did PR #5313 failed when running? I tested that it ran but should this output any specific information or should we have a way to validate that the service is working and not just running.
Can we internally execute something as a curl command to a specific endpoint or something that gives us an "expected" output?
This is mainly to confirm if we have a way that the service started but it did it successfully.

I ran these commands in Google Cloud Shell:
gcloud auth configure-docker us-docker.pkg.dev
docker run us-docker.pkg.dev/zealous-zebra/zebra/zebrad:sha-f71bb74

zebrad exited with a config parsing error.
Instead, it should log "Starting zebrad".
If we're looking to test for an open port, there's a Zcash listener on port 8233.
Or we can test for a successful start or end to the sync.
There are a lot of different acceptance tests in https://github.com/ZcashFoundation/zebra/blob/main/zebrad/tests/acceptance.rs

@gustavovalverde it looks like we don't publish the zebrad image until we merge to main.
So I think we'll have to merge this PR, then check that the zebrad image works.
(I already checked the zebrad.toml manually.)

zebrad exited with a config parsing error.

I should check this, it worries me that a failed zebrad start is not failing the container (for me, this is the expected behavior), but this might be related to how the process is being raised and if the Process ID is the first. I'll research that.

it looks like we don't publish the zebrad image until we merge to main

All PR images are available here: https://us-docker.pkg.dev/zealous-zebra/zebra/zebrad-test
The latest one from this PR is here: https://console.cloud.google.com/artifacts/docker/zealous-zebra/us/zebra/zebrad-test/sha256:b9f96bf73ec15b92fe69aba6febf472b8ad033792ed4a49c4622e46f80b6d977
With a docker pull us-docker.pkg.dev/zealous-zebra/zebra/zebrad-test:pr-5322 you should be able to test it

it looks like we don't publish the zebrad image until we merge to main

All PR images are available here: https://us-docker.pkg.dev/zealous-zebra/zebra/zebrad-test
The latest one from this PR is here: https://console.cloud.google.com/artifacts/docker/zealous-zebra/us/zebra/zebrad-test/sha256:b9f96bf73ec15b92fe69aba6febf472b8ad033792ed4a49c4622e46f80b6d977
With a docker pull us-docker.pkg.dev/zealous-zebra/zebra/zebrad-test:pr-5322 you should be able to test it

That's the zebrad-test image, but I want to test the zebrad image. They have different contents and commands.

I tested the command:
teor@cloudshell:~$ docker run us-docker.pkg.dev/zealous-zebra/zebra/zebrad:main

It seems to work correctly now:

...
Digest: sha256:24378bce2f632d8e05bf6015df3ec3cbab7ebcda88a563c5de87e0f928f051ab
Status: Downloaded newer image for us-docker.pkg.dev/zealous-zebra/zebra/zebrad:main
...
2022-10-04T04:30:51.154345Z  INFO zebrad::application: Diagnostic Metadata:
version: 1.0.0-beta.15
Zcash network: Mainnet
state version: 25
target triple: x86_64-unknown-linux-gnu
build profile: release
2022-10-04T04:30:51.154398Z  INFO {net="Main"}: zebrad::application: initialized rayon thread pool for CPU-bound tasks num_threads=2
...
2022-10-04T04:30:51.154965Z  INFO {net="Main"}: zebrad::commands::start: Starting zebrad
2022-10-04T04:30:51.155069Z  INFO {net="Main"}: zebrad::commands::start: config=ZebradConfig { consensus: Config { checkpoint_sync: true, debug_skip_parameter_preload: false }, metrics: MetricsSection { endpoint_addr: None }, network: Config  listen_addr: <IP_ADDRESS>:8233, network: Mainnet, initial_mainnet_peers: {"dnsseed.z.cash:8233", "dnsseed.str4d.xyz:8233", "mainnet.seeder.zfnd.org:8233", "mainnet.is.yolo.money:8233"}, initial_testnet_peers: {"dnsseed.testnet.z.cash:18233", "testnet.seeder.zfnd.org:18233", "testnet.is.yolo.money:18233"}, peerset_initial_target_size: 25, crawl_new_peer_interval: 61s }, state: Config { cache_dir: "/zebrad-cache", ephemeral: false, debug_stop_at_height: None, delete_old_database: true }, tracing: TracingSection { use_color: true, force_use_color: false, filter: None, buffer_limit: 128000, endpoint_addr: None, flamegraph: None, use_journald: false }, sync: SyncSection { download_concurrency_limit: 50, checkpoint_verify_concurrency_limit: 1200, full_verify_concurrency_limit: 20, parallel_cpu_threads: 0 }, mempool: Config { tx_cost_limit: 80000000, eviction_memory_time: 3600s, debug_enable_at_height: None }, rpc: Config { listen_addr: None, parallel_cpu_threads: 0, debug_force_finished_sync: false } }
2022-10-04T04:30:51.155165Z  INFO {net="Main"}: zebrad::commands::start: initializing node state
2022-10-04T04:30:51.155170Z  INFO {net="Main"}: zebrad::commands::start: opening database, this may take a couple minutes
2022-10-04T04:30:51.156855Z  INFO zebra_state::service::finalized_state::disk_db: the open file limit is high enough for Zebra current_limit=1048576 min_limit=512 ideal_limit=1024
2022-10-04T04:30:51.504642Z  INFO zebra_state::service::finalized_state::disk_db: Opened Zebra state cache at /zebrad-cache/state/v25/mainnet
...
2022-10-04T04:30:51.509768Z  INFO {net="Main"}:open_listener{addr=<IP_ADDRESS>:8233}: zebra_network::peer_set::initialize: Opened Zcash protocol endpoint at <IP_ADDRESS>:8233
...
2022-10-04T04:31:01.512746Z  INFO {net="Main"}:add_initial_peers: zebra_network::peer_set::initialize: connecting to initial peer set initial_peer_count=25 initial_peers={[2001:41d0:700:223b::]:8233, <IP_ADDRESS>:8233, [2a01:4f9:3a:2819::2]:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, [2a01:4f9:4b:42cb::2]:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, [2a01:4f8:120:72a3::2]:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, [2a01:4f9:c010:31a6::1]:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, [2001:41d0:303:417b::]:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233, <IP_ADDRESS>:8233}
...
2022-10-04T04:31:04.447546Z  INFO {net="Main"}: zebrad::components::sync::progress: initial sync is waiting to download the genesis block sync_percent=0.000 % current_height=None
2022-10-04T04:31:04.649565Z  INFO {net="Main"}:sync:checkpoint: zebra_consensus::checkpoint: verified checkpoint range block_count=1 current_range=(Unbounded, Included(Height(0)))
2022-10-04T04:31:04.946148Z  INFO {net="Main"}:sync:try_to_sync: zebrad::components::sync: starting sync, obtaining new tips state_tip=None
...
2022-10-04T04:31:20.639725Z  INFO {net="Main"}:sync:try_to_sync:obtain_tips:checkpoint: zebra_consensus::checkpoint: verified checkpoint range block_count=1200 current_range=(Excluded(Height(0)), Included(Height(1200)))
2022-10-04T04:31:20.706328Z  INFO {net="Main"}:sync:try_to_sync: zebrad::components::sync: extending tips tips.len=1 in_flight=1199 extra_hashes=0 lookahead_limit=1200 state_tip=Some(Height(296))
2022-10-04T04:31:23.610318Z  INFO {net="Main"}:sync:try_to_sync: zebrad::components::sync: extending tips tips.len=1 in_flight=1199 extra_hashes=0 lookahead_limit=1200 state_tip=Some(Height(1200))
...
2022-10-04T04:32:04.448899Z  INFO {net="Main"}: zebrad::components::sync::progress: estimated progress to chain tip sync_percent=0.195% current_height=Height(3600) network_upgrade=BeforeOverwinter remaining_sync_blocks=1839593 time_since_last_state_block=0s


Shell Theme not updating when Theme switched in Settings

In the Hamburger Template, when the Theme is switched from Light to Dark (or vice versa), the background of the Shell is not updated until the app is restarted. This causes an unpleasant flash of white when transitioning between pages.
Inserting the following at the end of the SettingsService.AppTheme property setter seems to fix the issue:
Views.Shell.Instance.RequestedTheme = value == ApplicationTheme.Dark ? ElementTheme.Dark : ElementTheme.Light;

Fixed it with this
public ApplicationTheme AppTheme
{
    get
    {
        var theme = ApplicationTheme.Light;
        var value = _helper.Read<string>(nameof(AppTheme), theme.ToString());
        return Enum.TryParse<ApplicationTheme>(value, out theme) ? theme : ApplicationTheme.Dark;
    }
    set
    {
        _helper.Write(nameof(AppTheme), value.ToString());
        (Window.Current.Content as FrameworkElement).RequestedTheme = value.ToElementTheme();
        Views.Shell.HamburgerMenu.RefreshStyles(value);
    }
}