MapInitializer is not initialized

Description
Running react-native-hms-map example project doesn't render the Map. Android logs show:
E/HmsMapKit_MapView_15: MapsInitializer is not initialized.
Expected behavior
React native example project should show map.
Current behavior
Map is not showing. Error is logged in Android studio.
Environment

Platform: React Native
Kit: Map Kit (@hmscore/react-native-hms-map)
Kit Version 6.11.0-304
OS Version EMUI 12.0.0
Android Studio version Android Studio Electric Eel | 2022.1.1 Patch 2

Other
I created a project in AppGallery Connect, enabled Location and Map APIs, created and configured fingerprint, downloaded agconnect-services.json and added in project/android/app folder.
I used the React native example code from the repo to display the MapView, but it shows empty.
On a side node, I cloned the Kotlin example project also, configured agconnect-services.json and keystore-file in the same way as with React native project and the Map loads and is displayed, so I don't think it's a problem with AppGallery configurations.
For the React native project I am using these dependencies:
"dependencies": {
"@hmscore/react-native-hms-location": "^6.11.0-301",
"@hmscore/react-native-hms-map": "^6.11.0-304",
"react": "18.2.0",
"react-native": "0.71.7"
},

Same issue with me. Did you find a solution for that ? @ottohyyrynendigia

@rozeridilar @isamert @ozcanozgur  @canerkocer

Unfortunately no. I downgraded to version 5 which seems to be working.

Hi, Have you tried to set the API key using "initializer" method? this is a reference from the official document
https://developer.huawei.com/consumer/en/doc/development/HMS-Plugin-References/mapview-0000001051150160-V1#section17562133322720

Hi, Have you tried to set the API key using "initializer" method? this is a reference from the official document https://developer.huawei.com/consumer/en/doc/development/HMS-Plugin-References/mapview-0000001051150160-V1#section17562133322720

Please follow the documentation for the latest updates.


If anyone know how to set device specific cover image

Checklist

[x] I have read the newlest tutorials and know the correct effect of the functional design.
[x] There is no similar question on existing issues (including closed ones).
[x] I have tried to find the answer on Jekyll Forum and StackOverflow.
[x] My question is based on the latest code of the master branch.

Description
If anyone know how to set device specific cover image. Mean that under specific device width the cover thumbnail image dont show. It good for Reduce the Lcp score in mobile devices.
If anyone know the trick let me know. I need the solution please.

Hi @Nexus-Gits
You are looking for CSS @media Rule.
It maybe looks like:
@media screen and (max-width: 1200px) {
  img.dev-spec {
    display: none;
  }
}


Create Responsive Error Page

I want to work on this issue under JWOC

@codervivek5
I would like to work on this under JWOC


Drop Python 2

Just to help out open source folks (or internal folks) coming to this page, would be good to include just a bit of description about what you think should happen here + possibly apply a good first issue label to it!

Done in https://github.com/counsyl/capone/pull/15.


Mountpoint path problem in Mac OS X

Hi,
I've just started using your module, which is truly fantastic, but I encoutered one problem while plugging in one of my pendrives. It is called EXTRNL #2 and of course it is mounted in Mac OS X with path /Volumes/EXTRNL #2, but after running drivelist it shows the path trimmed after space (/Volumes/EXTRNL). When using name without space or without hash sign it works as expected.
OS report
EXTRNL #2:
  Capacity:	32,01 GB (32 009 879 552 bytes)
  Available:	31,62 GB (31 617 187 840 bytes)
  Writable:	Yes
  File System:	MS-DOS FAT32
  BSD Name:	disk2s1
  Mount Point:	/Volumes/EXTRNL #2
  Content:	Windows_FAT_32

Module
{
  "device": "/dev/disk2",
  "description": "Cruzer Blade",
  "size":<PHONE_NUMBER>8,
  "mountpoints": [
    {
      "path": "/Volumes/EXTRNL"
    }
  ],
  "raw": "/dev/rdisk2",
  "protected": false,
  "system": false
}

Yup, same thing affects Linux too. Fix should be easy...

I released v5.0.18 to npm. Let me know how it goes!


Register new CRDs & Autogenerate CRD Clients

This PRs introduces the required Go code to register the new CRDS, based on which we generate the following https://github.com/Azure/application-gateway-kubernetes-ingress/pull/282
This is a small chunk from https://github.com/Azure/application-gateway-kubernetes-ingress/pull/267

@akshaysngupta  I struggled to find a decent way to make informers.HasSynced() == true in the WaitForCacheSync section for the CRDs during unit tests here: .  So for the time being I added a bool to bypass that while testing: https://github.com/Azure/application-gateway-kubernetes-ingress/pull/283/files#diff-f0d560b01cfd4dd3863dff1cb96b71edR256
I'm going to spend some time fixing this as soon as we ship this feature first.
PTAL


Update version to 1.1.16-0 on staging

Update version to 1.1.16-0

🚀 Deployed to staging by @OSBotify in version: 1.1.16-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
failure ❌

🍎 iOS 🍎
success ✅

🕸 web 🕸
failure ❌

🚀 Deployed to production by @roryabraham in version: 1.1.16-10 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Refactor NewRelic::Cli::Install

Refactor codes based on tell-dont-ask style
Minor refactor on Install CLI options

Hi @joneslee85 - thanks for sending this our way! There's a lot in here, so I'm wondering if you could contextualize these changes a bit by describing what your overall goal was in making them. Thanks!

@benweint description updated


What type of update are you requesting?
A new version of an existing package
Current Package Identifier
SillyKoalaHugs.TheFreezingKoala
Package Version
1.0+
Please describe the changes you would like to see

Reference: https://github.com/microsoft/winget-pkgs/pull/164497

See https://github.com/microsoft/winget-pkgs/pull/164496#issuecomment-2250993912


typo fix in HISTORY.md

Coverage remained the same at 100.0% when pulling 01fcdaa4275c59d50549666464f775916c60916b on Guria:patch-1 into a4fa4facc0b43cdb933859d5374f081d18f40320 on nodeca:master.


WFLY-436 Inline JGroups subsystem references to threads subsystem

Jira:
https://issues.jboss.org/browse/WFLY-436

Linux with security manager Build 720 is now running using a merge of 738077e9bce07a1e015e33f315baddfa5ea2c5df

Windows Build 844 is now running using a merge of 738077e9bce07a1e015e33f315baddfa5ea2c5df

Linux Build 5733 is now running using a merge of 738077e9bce07a1e015e33f315baddfa5ea2c5df

Linux with security manager Build 720 outcome was SUCCESS using a merge of 738077e9bce07a1e015e33f315baddfa5ea2c5df
Summary: Tests passed: 788, ignored: 369 Build time: 0:05:13

Windows Build 844 outcome was SUCCESS using a merge of 738077e9bce07a1e015e33f315baddfa5ea2c5df
Summary: Tests passed: 2906, ignored: 364 Build time: 0:51:14

Linux Build 5733 outcome was SUCCESS using a merge of 738077e9bce07a1e015e33f315baddfa5ea2c5df
Summary: Tests passed: 2906, ignored: 364 Build time: 0:53:25

Rebased again after clustering module split, also reworked that defaults from the model are the defaults actually used.

Linux Build 5752 is now running using a merge of e6d129d9de06c401e7aefd1bfbd05dcd968eda71

Linux with security manager Build 739 is now running using a merge of e6d129d9de06c401e7aefd1bfbd05dcd968eda71

Windows Build 863 is now running using a merge of e6d129d9de06c401e7aefd1bfbd05dcd968eda71

Linux with security manager Build 739 outcome was SUCCESS using a merge of e6d129d9de06c401e7aefd1bfbd05dcd968eda71
Summary: Tests passed: 788, ignored: 369 Build time: 0:06:03

Windows Build 863 outcome was SUCCESS using a merge of e6d129d9de06c401e7aefd1bfbd05dcd968eda71
Summary: Tests passed: 2906, ignored: 364 Build time: 0:50:10

Linux Build 5752 outcome was SUCCESS using a merge of e6d129d9de06c401e7aefd1bfbd05dcd968eda71
Summary: Tests passed: 2906, ignored: 364 Build time: 0:51:34

Needed  a rebase again... done.

Linux Build 5780 is now running using a merge of 679a352c0f6af32de8ed52d248bfaecd798d9fd9

Windows Build 890 is now running using a merge of 679a352c0f6af32de8ed52d248bfaecd798d9fd9

Linux with security manager Build 766 is now running using a merge of 679a352c0f6af32de8ed52d248bfaecd798d9fd9

Linux with security manager Build 766 outcome was SUCCESS using a merge of 679a352c0f6af32de8ed52d248bfaecd798d9fd9
Summary: Tests passed: 795, ignored: 371 Build time: 0:05:16

Windows Build 890 outcome was SUCCESS using a merge of 679a352c0f6af32de8ed52d248bfaecd798d9fd9
Summary: Tests passed: 2915, ignored: 366 Build time: 0:50:39

Linux Build 5780 outcome was SUCCESS using a merge of 679a352c0f6af32de8ed52d248bfaecd798d9fd9
Summary: Tests passed: 2915, ignored: 366 Build time: 0:53:07

Linux with security manager Build 793 is now running using a merge of 02174480fcb5d5076e1919d1f435ddd860cb5e8f

Linux Build 5807 is now running using a merge of 02174480fcb5d5076e1919d1f435ddd860cb5e8f

Windows Build 917 is now running using a merge of 02174480fcb5d5076e1919d1f435ddd860cb5e8f

Linux with security manager Build 793 outcome was SUCCESS using a merge of 02174480fcb5d5076e1919d1f435ddd860cb5e8f
Summary: Tests passed: 851, ignored: 316 Build time: 0:05:28

Windows Build 917 outcome was FAILURE using a merge of 02174480fcb5d5076e1919d1f435ddd860cb5e8f
Summary: Tests failed: 1 (1 new), passed: 2933, ignored: 311 Build time: 0:50:00
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.ejb.stateful.passivation.PassivationTestCase.testPassivationMaxSize: javax.ejb.EJBException: java.lang.IllegalStateException: WFLYCLEJBINF0008: Stateful session bean {[-31, 6, 88, -88, -71, 65, 73, -45, -79, -30, -11, -82, 36, -31, -23, 26]} refers to an invalid bean group a7b4cbef-b41f-4d04-9c79-5f68c029e4ed
	at org.wildfly.clustering.ejb.infinispan.bean.InfinispanBeanFactory.createBean(InfinispanBeanFactory.java:76)
	at org.wildfly.clustering.ejb.infinispan.InfinispanBeanManager.findBean(InfinispanBeanManager.java:266)

Linux Build 5807 outcome was FAILURE using a merge of 02174480fcb5d5076e1919d1f435ddd860cb5e8f
Summary: Tests failed: 1 (1 new), passed: 2933, ignored: 311 Build time: 0:51:41
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.smoke.webservices.WSTestCase.testManagementDescriptionMetrics: java.lang.AssertionError: null
	at org.junit.Assert.fail(Assert.java:86)
	at org.junit.Assert.assertTrue(Assert.java:41)

Retest this please.

Windows Build 919 is now running using a merge of 02174480fcb5d5076e1919d1f435ddd860cb5e8f

Linux with security manager Build 795 is now running using a merge of 02174480fcb5d5076e1919d1f435ddd860cb5e8f

Linux Build 5809 is now running using a merge of 02174480fcb5d5076e1919d1f435ddd860cb5e8f

Linux with security manager Build 795 outcome was SUCCESS using a merge of 02174480fcb5d5076e1919d1f435ddd860cb5e8f
Summary: Tests passed: 851, ignored: 316 Build time: 0:06:18

Windows Build 919 outcome was SUCCESS using a merge of 02174480fcb5d5076e1919d1f435ddd860cb5e8f
Summary: Tests passed: 2934, ignored: 311 Build time: 0:49:21

Linux Build 5809 outcome was SUCCESS using a merge of 02174480fcb5d5076e1919d1f435ddd860cb5e8f
Summary: Tests passed: 2933, ignored: 311, muted: 1 Build time: 0:52:00

This all looks good, except it introduces a third way of representing keep-alive time. There's the ee concurrency stuff way, where it's a single attribute of type long, and the threads subsystem way (used by jca) where it's a complex attribute.
Please pick one of those two.

(BTW, I vote for a single attribute of type long. The convenience of being able to use a random time unit isn't worth the complexity of having a complex attribute.)

Linux with security manager Build 928 is now running using a merge of 7d553e6e0544a8227b6893212a7ab0fb07dc390b

Linux Build 5949 is now running using a merge of 7d553e6e0544a8227b6893212a7ab0fb07dc390b

Windows Build 1059 is now running using a merge of 7d553e6e0544a8227b6893212a7ab0fb07dc390b

I have reimplemented with the "ee subsystem way" (including the spelling mistake; keep alive are either hyphenated or 2 words in English language).

Linux with security manager Build 928 outcome was SUCCESS using a merge of 7d553e6e0544a8227b6893212a7ab0fb07dc390b
Summary: Tests passed: 840, ignored: 319 Build time: 0:06:22

Windows Build 1059 outcome was SUCCESS using a merge of 7d553e6e0544a8227b6893212a7ab0fb07dc390b
Summary: Tests passed: 2927, ignored: 313 Build time: 0:47:00

Linux Build 5949 outcome was FAILURE using a merge of 7d553e6e0544a8227b6893212a7ab0fb07dc390b
Summary: Tests failed: 1 (1 new), passed: 2925, ignored: 313, muted: 1 Build time: 0:48:18
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.ejb.stateful.passivation.PassivationTestCase.testPassivationMaxSize: javax.ejb.EJBException: java.lang.IllegalStateException: WFLYCLEJBINF0008: Stateful session bean {[-4, -15, -63, -33, 31, -90, 79, -39, -108, -72, 120, 21, -75, -11, -25, 85]} refers to an invalid bean group 875789e6-8920-44b0-b9cb-4d5163fac9b3
	at org.wildfly.clustering.ejb.infinispan.bean.InfinispanBeanFactory.createBean(InfinispanBeanFactory.java:76)
	at org.wildfly.clustering.ejb.infinispan.InfinispanBeanManager.findBean(InfinispanBeanManager.java:266)

Linux with security manager Build 932 is now running using a merge of f0df3257b5e172cc1ee5e20d140fc56b18cc505f

Linux Build 5953 is now running using a merge of f0df3257b5e172cc1ee5e20d140fc56b18cc505f

Windows Build 1063 is now running using a merge of f0df3257b5e172cc1ee5e20d140fc56b18cc505f

Linux with security manager Build 932 outcome was SUCCESS using a merge of f0df3257b5e172cc1ee5e20d140fc56b18cc505f
Summary: Tests passed: 840, ignored: 319 Build time: 0:05:02

Linux Build 5953 outcome was SUCCESS using a merge of f0df3257b5e172cc1ee5e20d140fc56b18cc505f
Summary: Tests passed: 2927, ignored: 313, muted: 1 Build time: 0:46:35

Windows Build 1063 outcome was FAILURE using a merge of f0df3257b5e172cc1ee5e20d140fc56b18cc505f
Summary: Tests failed: 1 (1 new), passed: 2927, ignored: 313 Build time: 0:47:10
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.clustering.cluster.web.GranularWebFailoverTestCase(SYNC-tcp).testGracefulUndeployFailover: java.lang.AssertionError: expected:<200> but was:<500>
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failNotEquals(Assert.java:743)

Retest this please.

Windows Build 1066 is now running using a merge of f0df3257b5e172cc1ee5e20d140fc56b18cc505f

Linux with security manager Build 935 is now running using a merge of f0df3257b5e172cc1ee5e20d140fc56b18cc505f

Linux Build 5956 is now running using a merge of f0df3257b5e172cc1ee5e20d140fc56b18cc505f

Linux with security manager Build 935 outcome was SUCCESS using a merge of f0df3257b5e172cc1ee5e20d140fc56b18cc505f
Summary: Tests passed: 840, ignored: 319 Build time: 0:06:29

Windows Build 1066 outcome was SUCCESS using a merge of f0df3257b5e172cc1ee5e20d140fc56b18cc505f
Summary: Tests passed: 2928, ignored: 313 Build time: 0:46:32

Linux Build 5956 outcome was SUCCESS using a merge of f0df3257b5e172cc1ee5e20d140fc56b18cc505f
Summary: Tests passed: 2928, ignored: 313 Build time: 0:47:09

Linux with security manager Build 936 is now running using a merge of 0168c48d87018d42fc07ca942656c9f5bb4a3d8c

Linux Build 5957 is now running using a merge of 0168c48d87018d42fc07ca942656c9f5bb4a3d8c

Windows Build 1067 is now running using a merge of 0168c48d87018d42fc07ca942656c9f5bb4a3d8c

Linux with security manager Build 936 outcome was SUCCESS using a merge of 0168c48d87018d42fc07ca942656c9f5bb4a3d8c
Summary: Tests passed: 840, ignored: 319 Build time: 0:05:23

Windows Build 1067 outcome was SUCCESS using a merge of 0168c48d87018d42fc07ca942656c9f5bb4a3d8c
Summary: Tests passed: 2928, ignored: 313 Build time: 0:46:52

Linux Build 5957 outcome was SUCCESS using a merge of 0168c48d87018d42fc07ca942656c9f5bb4a3d8c
Summary: Tests passed: 2928, ignored: 313 Build time: 0:47:24

woohoo! now we can "remove" threads subsystem :)

@ctomc Sorry, not so fast...! still working on the last Infinispan part.


Tests failing on pull requests

Full problem here: http://stackoverflow.com/questions/39530802/tox-running-command-based-on-env-variable

Kinda fixed by calling python setup.py testcov which calls a new class in setup.py, which has subprocess.calls and os.getenv - I don't like this solution however - so I'm leaving this issue open

No better solution found


Migrate build to sbt1.0

Hi, this PR attempts to migrate your library to use sbt 1.0.2. I tried to keep it as minimal as possible.
If you have wishes regarding this PR feel free to tell me or change it directly as you wish.
Regards, Felix

@alexarchambault
look like we got this covered: https://github.com/lihaoyi/acyclic/blob/master/project/build.properties


Key Management Interface

We need to define our Key Management interface.
The interface needs to be able to be initialized with in-memory or hardware keys. We can start with the in-memory implementation.
Once initialized, this interface should include expose:

Transaction signing
Message signing

These methods do not need to be implemented as part of this work

#10


[Employees] When granting permission to the "Employees" page, the navigator can't create, edit, deactivate an employee card and edit an employee's authority

Environment: all
Reproducible: always
**Build found:**31/07/2023
Preconditions

User shoud be on the position navigator.
Super admin has to set employee permisions for navigator on seeing the main page "Employee", creating a new employee card, editing an employee card, deactivating an employee, editing an employee's authority.
User shoud be logged.
Go to https://www.greencity.social/#/ubs-admin/employee/1

Steps to reproduce

On the main page "Employee" click on the button "Add employee" and fill all fields in pop-up "Add employee"
Choose an employee card, click on 3 dots and and click on "Edit employee data". Do some changes in "Edit employee data" pop-up window. Save changes.
Choose an employee card, click on 3 dots and click on "Delete employee"
Choose an employee card, click on 3 dots and click on "Set employee permissions ". Set some employee permissions to employee. (e.x. to edit order card)

Actual result

There is no "Add employee" button on the page.
There are no 3 dots near employee card.
There are no "Set permissions" and "Edit" buttons at the bottom of the employee card.

Expected result
Navigator can create, edit, deactivate an employee card and edit an employee's authority.
User story and test case links
E.g.: https://github.com/ita-social-projects/GreenCity/issues/5538

Bug is fixed


Bad header line in Caskroom/cask/osxfuse

osxfuse fails with this error when I try to install it:
$ brew install Caskroom/cask/osxfuse
==> brew cask install Caskroom/cask/osxfuse
Error: Cask 'osxfuse' definition is invalid: Bad header line: parse failed

As far as I can tell, my Homebrew and its definitions are up-to-date:
$ brew --version
Homebrew 0.9.5 (git revision 6fd6; last commit 2016-02-09)

$ brew update
Already up-to-date.

That was caused by an update to how homebrew-cask works. Details can be found here.
To fix the issue, please run:
brew uninstall --force brew-cask; brew update

If you are still having problems, open an issue with the appropriate template

@vitorgalvao Cool. Thanks for the quick response.


overview of project

I will add the code of this project after the merger of this project.
Thank you,

please approve

Do both things together


Update ssr.md

I came across these two SSR frameworks recently and thought they would be good alternatives to Nuxt.js for developers who want to have more of a pure Vue.js development experience.

Am I supposed to do something on my end before this PR gets merged and pushed to production or do I need to wait until someone handles that? I want to make sure that I didn't miss something.
Thank you!

@SamuelEarl this branch has conflicts now. Can you fix them and remerge?


LocalCluster(processes=True) broken?

Describe the issue: Launching a LocalCluster(processes=True) appears to be broken, with the cluster failing the launch and RuntimeError thrown from mutlipocessing/spawn.py. Based on the output below, I suspect a race condition in the subprocess setup.
Minimal Complete Verifiable Example:
# -*- coding: utf-8 -*-

from dask.distributed import Client, LocalCluster

cluster = LocalCluster(n_workers=8, processes=True)
client = Client(cluster)

def test():
    return "hello"

print(client.run(test))

Anything else we need to know?:
Here is a sample of the long traceback (although I am not exactly sure where each processes traceback begins):
The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/Users/jfirst/opt/miniconda3/envs/dask/lib/python3.10/asyncio/tasks.py", line 650, in _wrap_awaitable
    return (yield from awaitable.__await__())
  File "/Users/jfirst/opt/miniconda3/envs/dask/lib/python3.10/site-packages/distributed/core.py", line 488, in start
    raise RuntimeError(f"{type(self).__name__} failed to start.") from exc
RuntimeError: Nanny failed to start.
Task exception was never retrieved
future: <Task finished name='Task-27' coro=<_wrap_awaitable() done, defined at /Users/jfirst/opt/miniconda3/envs/dask/lib/python3.10/asyncio/tasks.py:643> exception=RuntimeError('Nanny failed to start.')>
Traceback (most recent call last):
  File "/Users/jfirst/opt/miniconda3/envs/dask/lib/python3.10/site-packages/distributed/core.py", line 480, in start
    await asyncio.wait_for(self.start_unsafe(), timeout=timeout)
  File "/Users/jfirst/opt/miniconda3/envs/dask/lib/python3.10/asyncio/tasks.py", line 408, in wait_for
    return await fut
  File "/Users/jfirst/opt/miniconda3/envs/dask/lib/python3.10/site-packages/distributed/nanny.py", line 363, in start_unsafe
    response = await self.instantiate()
  File "/Users/jfirst/opt/miniconda3/envs/dask/lib/python3.10/site-packages/distributed/nanny.py", line 436, in instantiate
    result = await self.process.start()
  File "/Users/jfirst/opt/miniconda3/envs/dask/lib/python3.10/site-packages/distributed/nanny.py", line 679, in start
    await self.process.start()
  File "/Users/jfirst/opt/miniconda3/envs/dask/lib/python3.10/site-packages/distributed/process.py", line 38, in _call_and_set_future
    res = func(*args, **kwargs)
  File "/Users/jfirst/opt/miniconda3/envs/dask/lib/python3.10/site-packages/distributed/process.py", line 199, in _start
    process.start()
  File "/Users/jfirst/opt/miniconda3/envs/dask/lib/python3.10/multiprocessing/process.py", line 121, in start
    self._popen = self._Popen(self)
  File "/Users/jfirst/opt/miniconda3/envs/dask/lib/python3.10/multiprocessing/context.py", line 284, in _Popen
    return Popen(process_obj)
  File "/Users/jfirst/opt/miniconda3/envs/dask/lib/python3.10/multiprocessing/popen_spawn_posix.py", line 32, in __init__
    super().__init__(process_obj)
  File "/Users/jfirst/opt/miniconda3/envs/dask/lib/python3.10/multiprocessing/popen_fork.py", line 19, in __init__
    self._launch(process_obj)
  File "/Users/jfirst/opt/miniconda3/envs/dask/lib/python3.10/multiprocessing/popen_spawn_posix.py", line 42, in _launch
    prep_data = spawn.get_preparation_data(process_obj._name)
  File "/Users/jfirst/opt/miniconda3/envs/dask/lib/python3.10/multiprocessing/spawn.py", line 154, in get_preparation_data
    _check_not_importing_main()
  File "/Users/jfirst/opt/miniconda3/envs/dask/lib/python3.10/multiprocessing/spawn.py", line 134, in _check_not_importing_main
    raise RuntimeError('''
RuntimeError:
        An attempt has been made to start a new process before the
        current process has finished its bootstrapping phase.

        This probably means that you are not using fork to start your
        child processes and you have forgotten to use the proper idiom
        in the main module:

            if __name__ == '__main__':
                freeze_support()
                ...

        The "freeze_support()" line can be omitted if the program
        is not going to be frozen to produce an executable.

The above exception was the direct cause of the following exception:

It's worth noting that this bug does not appear from within ipython. If I load the interactive shell and execute the commands above, I get the expected behavior. However, running ipython -i test.py on the source code above results in the issue.
Environment:

Dask version: 2022.7.0
Python version: Python 3.10.4
Operating System: macOS 12.0.1, also observed on CentOS Linux release 7.7.1908 (Core)
Install method (conda, pip, source):

conda create -n dask
conda install dask ipython

Thanks for raising an issue @jeremyfirst22! You need include a if __name__ == "__main__": block to when creating a LocalCluster. See https://docs.dask.org/en/stable/scheduling.html#standalone-python-scripts for more details.


Insight into error awswrangler.exceptions.QueryFailed: Iceberg cannot access the requested resource

Hi. I received the following error when trying to use athena_to_iceberg. I was wondering if anyone had any insights into what the root cause might be - or at least how to get more information about the error?
I suspect that there might be some permissions issues - I am trying to use AccesAnalyzer to look at what might be needed. With that in mind, Iceberg is the thing that does not have permissions - not me?
Any insight would be appreciated.
This:
lab_data_wrangler_session = boto3.Session(profile_name='COMPANY-lab-data-wrangler',region_name='us-west-2')
lab_data_wrangler_s3 = lab_data_wrangler_session.client('s3')

wr.athena.to_iceberg(
    # df=total_panda,
    df=pd.DataFrame({'col': [1, 2, 3]}),
    database='COMPANY_lab_data_lake_staging',
    table='junk_table',
    table_location='s3://COMPANY-lab-data-lake/temp/iceberg/',
    temp_path='s3://COMPANY-lab-data-lake/temp/iceberg-temp/',
    boto3_session=lab_data_wrangler_session,
    s3_output='s3://COMPANY-lab-a2p-commons-metabase-output/NAMEs-directory/'
)

gives:
Traceback (most recent call last):
  File "/Users/NAME/coding_projects/COMPANY/a2p-commons/src/python/commons/tools/gsheet_to_lake.py", line 165, in <module>
    dataframe_to_iceberg(
  File "/Users/NAME/coding_projects/COMPANY/a2p-commons/src/python/commons/tools/gsheet_to_lake.py", line 69, in dataframe_to_iceberg
    wr.athena.to_iceberg(
  File "/Users/NAME/Library/Caches/pypoetry/virtualenvs/COMPANY-data-commons-mOl3hlmm-py3.11/lib/python3.11/site-packages/awswrangler/_config.py", line 715, in wrapper
    return function(**args)
           ^^^^^^^^^^^^^^^^
  File "/Users/NAME/Library/Caches/pypoetry/virtualenvs/COMPANY-data-commons-mOl3hlmm-py3.11/lib/python3.11/site-packages/awswrangler/_utils.py", line 178, in inner
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/Users/NAME/Library/Caches/pypoetry/virtualenvs/COMPANY-data-commons-mOl3hlmm-py3.11/lib/python3.11/site-packages/awswrangler/athena/_write_iceberg.py", line 391, in to_iceberg
    _create_iceberg_table(
  File "/Users/NAME/Library/Caches/pypoetry/virtualenvs/COMPANY-data-commons-mOl3hlmm-py3.11/lib/python3.11/site-packages/awswrangler/athena/_write_iceberg.py", line 82, in _create_iceberg_table
    wait_query(query_execution_id=query_execution_id, boto3_session=boto3_session)
  File "/Users/NAME/Library/Caches/pypoetry/virtualenvs/COMPANY-data-commons-mOl3hlmm-py3.11/lib/python3.11/site-packages/awswrangler/_config.py", line 715, in wrapper
    return function(**args)
           ^^^^^^^^^^^^^^^^
  File "/Users/NAME/Library/Caches/pypoetry/virtualenvs/COMPANY-data-commons-mOl3hlmm-py3.11/lib/python3.11/site-packages/awswrangler/athena/_executions.py", line 237, in wait_query
    raise exceptions.QueryFailed(response["Status"].get("StateChangeReason"))
awswrangler.exceptions.QueryFailed: Iceberg cannot access the requested resource

Hi @plbremer does this consistently reproduce? Does your role have S3 permissions to both COMPANY-lab-data-lake and COMPANY-lab-a2p-commons-metabase-output  buckets, as well as KMS, and Glue permissions? Have you tried running it as Admin?
The error is coming from the Athena service and unfortunately lacking information that would help to debug. You might be able to find more error details in CloudTrail, otherwise I suggest to raise AWS support request and include query id that would help service team with RCA.

@kukushking thanks for taking the time to respond
for all those curious, I am not sure which permissions exactly did the trick, but I can say that adding

"athena:StartQueryExecution",
"athena:StopQueryExecution"
"glue:Create*"

resolved this issue


Spell check the compositional ontology

I wasn't sure what to do with doctors office or physicians assistant which usually have apostrophes.  I left them.


Spiffe validator doesn't respect require_client_cert configuration

Title: Spiffe validator doesn't respect require_client_cert configuration
Description:
When Spiffe Validator is in use it require you to provide client certificate independently of what value of require_client_certificate is set.
Repro steps:
Configure envoy SDS with spire-agent as upstream like:
{
   ...
    "transport_socket": {
        "name": "envoy.transport_sockets.tls",
        "typed_config": {
            "@type": "type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.DownstreamTlsContext",
            "common_tls_context": {
                "tls_params": {
                    "tls_minimum_protocol_version": "TLSv1_2"
                },
                "alpn_protocols": [
                    "h2"
                ],
                "tls_certificate_sds_secret_configs": [
                    {
                        "name": "spiffe://some.trust.domain/service-name",
                        "sds_config": {
                            "api_config_source": {
                                "api_type": "GRPC",
                                "grpc_services": [
                                    {
                                        "envoy_grpc": {
                                            "cluster_name": "spire_sds_cluster"
                                        }
                                    }
                                ],
                                "transport_api_version": "V3"
                            },
                            "resource_api_version": "V3"
                        }
                    }
                ],
                "validation_context_sds_secret_config": {
                    "name": "spiffe://some.trust.domain",
                    "sds_config": {
                        "api_config_source": {
                            "api_type": "GRPC",
                            "grpc_services": [
                                {
                                    "envoy_grpc": {
                                        "cluster_name": "spire_sds_cluster"
                                    }
                                }
                            ],
                            "transport_api_version": "V3"
                        },
                        "resource_api_version": "V3"
                    }
                }
            }
        }
    }
}

Try to curl your service and get
curl: (56) OpenSSL SSL_read: error:1409445C:SSL routines:ssl3_read_bytes:tlsv13 alert certificate required, errno 0
command terminated with exit code 56

Verbose output:
*   Trying <IP_ADDRESS>:10110...
* TCP_NODELAY set
* Connected to some-service (<IP_ADDRESS>) port 10110 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Request CERT (13):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Certificate (11):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: ---
*  start date: Mar 28 17:11:56 2023 GMT
*  expire date: Mar 28 19:12:06 2023 GMT
*  issuer: ---
*  SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x561b85108320)
> GET /api/headers HTTP/2
> Host: some-service
> user-agent: curl/7.68.0
> accept: */*
>
* TLSv1.3 (IN), TLS alert, unknown (628):
* OpenSSL SSL_read: error:1409445C:SSL routines:ssl3_read_bytes:tlsv13 alert certificate required, errno 0
* Failed receiving HTTP2 data
* OpenSSL SSL_write: SSL_ERROR_ZERO_RETURN, errno 0
* Failed sending HTTP2 data
* Connection #0 to host some-service left intact
curl: (56) OpenSSL SSL_read: error:1409445C:SSL routines:ssl3_read_bytes:tlsv13 alert certificate required, errno 0
command terminated with exit code 56

Looks like it's deliberate:
https://github.com/envoyproxy/envoy/blob/3ddd5cd8a2080308c5da21860e939a8d0971b839/source/extensions/transport_sockets/tls/cert_validator/spiffe/spiffe_validator.cc#L143

Yep, I’ve seen it. But is there any reasons to enforce clients certificate requirement unconditionally?

Well, could say the same for any mTLS vs TLS. There are still plenty of situations when we don’t want mutual TLS to be enforced but still have spiffe validator in place, especially when you’re in some kind of transition mode

The concept of SPIFFE is to mutually authenticate workloads hence how this is implemented. If your client doesn't adopt SPIFFE, how do you validate the server's SPIFFE SVID?


Async update for vineyard llm cache

Have a dedicated thread for performing update operations.
Vineyard is designed to drop updates whose prefix chunks are not already present in the cache, which imposes an ordering requirement on updates: we must perform updates in the issued order for each sequence. For simplicity, we use a single thread to process all updates sequentially.
Internally, we use an object pool to reuse the pinned tensors and restrict the number of inflight tasks. if an update operation cannot get a tensor from the pool, meaning we already have max_inflight_tasks tasks issued, it then simply skips the update. A completed task will return the used tensor back to the pool. The memory utilization of the object pool is configurable via env variable VINEYARD_CACHE_ASYNC_UPDATE_CPU_MEM_UTIL, whose value ranges from 0 to 1, and, e.g., 0.2 means 20% of VINEYARD_CACHE_CPU_MEM_LIMIT_GB (configured cpu memory limit for vineyard) will be used by the object pool.
FILL IN THE PR DESCRIPTION HERE
FIX #xxxx (link existing issues this PR will resolve)
BEFORE SUBMITTING, PLEASE READ THE CHECKLIST BELOW AND FILL IN THE DESCRIPTION ABOVE

 PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

[Bugfix] for bug fixes.
[CI/Build] for build or continuous integration improvements.
[Doc] for documentation fixes and improvements.
[Model] for adding a new model or improving an existing model. Model name should appear in the title.
[Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
[Kernel] for changes affecting CUDA kernels or other compute kernels.
[Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
[Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
[Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:

We adhere to Google Python style guide and Google C++ style guide.
Pass all linter checks. Please use format.sh to format your code.
The code need to be well-documented to ensure future contributors can easily understand the code.
Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Adding or changing kernels
Each custom kernel needs a schema and one or more implementations to be registered with PyTorch.

Make sure custom ops are registered following PyTorch guidelines: Custom C++ and CUDA Operators and The Custom Operators Manual
Custom operations that return Tensors require meta-functions. Meta-functions should be implemented and registered in python so that dynamic dims can be handled automatically. See above documents for a description of meta-functions.
Use torch.libary.opcheck() to test the function registration and meta-function for any registered ops.  See tests/kernels for examples.
When changing the C++ signature of an existing op, the schema must be updated to reflect the changes.
If a new custom type is needed, see the following document: Custom Class Support in PT2.

Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.
What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

 After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
 After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
 After the review, the reviewer will put an  action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
 Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You
 Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

All my comments are addressed. /lgtm


Web Share and Share Target are shipped on desktop

On the Fugu tracker it looks like Web Share and Web Share target are only shipped on Android. They've been shipped to some desktop platforms as well.
https://chromestatus.com/feature/4777349178458112?context=myfeatures
https://chromestatus.com/feature/6124071381106688?context=myfeatures
https://chromestatus.com/feature/5662315307335680?context=myfeatures
https://chromestatus.com/feature/5668769141620736?context=myfeatures
Chrome OS has full support while Windows only has Share API, no Share Target.

cc: @ewilligers

Fixing ChromeStatus should fix the tracker. Once you have changed the info there, give the tracker a day to redeploy. After confirming it worked, please close this issue. Thank you!

The ChromeStatus entries say they've shipped on desktop in M89, is there a specific field that needs updating for Fugu Tracker to pick up on?

If you search for "web share" in the Fugu Tracker, you will find several entries, since it has shipped separately for Mac, Windows, "desktop", etc. The same goes for "web share target", but the bugs are still not fixed (https://bugs.chromium.org/p/chromium/issues/list?q=summary%3A"web share target"&can=2). I think the reason it doesn't show up is this change, where @ewilligers has removed the other OS labels. You can try adding them again (this could also work for Web Share).

Oh interesting, I didn't know the tracker looked at bug statuses, thanks!


Pressing tab will undo a backspace when no autocomplete is available.

Not a feature flaw.

This happens because the ordering which the keypress events occur for certain keys are different.


Set ttl via this.cacheManager.set is not working when ttl is set in CacheModule.registerAsync as global

Is there an existing issue for this?

[x] I have searched the existing issues

Current behavior
Set ttl via this.cacheManager.set is not working when ttl is set in CacheModule.registerAsync as global. ttl is always set as the global value.
Minimum reproduction code
https://github.com/nestjs/cache-manager
Steps to reproduce

ttl set to 100 in CacheModule.registerAsync as global:

import { redisStore } from 'cache-manager-redis-store';

CacheModule.registerAsync<RedisClientOptions>({
  isGlobal: true,
  inject: [ConfigService],
  useFactory: async (configService: ConfigService) => ({
    store: redisStore,
    url: configService.get('REDIS_URL'),
    password: configService.get('REDIS_PASS'),
    ttl: 100,
  }),
}),

ttl set to 200 in xx.service.ts:

this.cacheManager.set(
  'key',
  'value',
  200,
)

Expected behavior
Check in redis client tool, TTL is 200
Package version
1.0.0
NestJS version
9.0.0
Node.js version
16.17.0
In which operating systems have you tested?

[X] macOS
[ ] Windows
[ ] Linux

Other
No response

cacheManager is just a wrapper around cacheManager.caching() instance. I'd suggest reporting this issue here https://github.com/node-cache-manager/node-cache-manager instead


Protocol README and size recommendation

Add a README to the vocabulary-draft folder.
Add links from the main README to the vacabulary, sdk and poc folders.
Add notes about lightweight events, as agreed in https://github.com/cdfoundation/sig-events/discussions/47
Signed-off-by: Andrea Frittoli<EMAIL_ADDRESS>

/lgtm


shaperpan resizable with aspect ratio

hi, i want to resize my shaperpans with 1/3 ratio and i did it changich mouseDragged event. but it stop edge of ratio. for example if i reach max width for 1/3 ratio it stops, the same thing exist for height. i want like resize as  https://jqueryui.com/resources/demos/resizable/aspect-ratio.html. how can i do it non stop resizeble at zebra.

Well, not very graceful solution but find below an example of code that sizes component with preserving 3/2 ratio:
zebkit.require("ui","layout","draw", "ui.design", function(ui, layout, draw, design) {
	var zc = new ui.zCanvas();
	//zc.setSizeFull(true);
	zc.root.add(new design.ShaperPan(new ui.Button("Test"), [
		function pointerDragged(e){
		    if (this.$state !== null) {
		       	var s= this.$state;
		       	if ((s.top + s.right + s.bottom + s.left) === 0) {
		       		this.$super(e);
		       	} else {
		       		var dy = (e.absY - this.py),
		       		    dx = (e.absX - this.px),
		       		    nh = this.height - dy * s.top  + dy * s.bottom;

		       		if (nh >= this.minHeight && dy !== 0) {
		       		    this.px = e.absX;
		       		    this.py = e.absY;
		       		    var nw = Math.floor(nh * 3) / 2;
		       		    this.setBounds(this.x + dx * s.left, this.y + dy * s.top, nw, nh);
		       		}
		       	}
		    }
		}
	])).setBounds(10, 10, Math.floor((50 * 3) / 2), 50);
});

thanks


[4pt]  - Display number of likes for each item on the Homepage - Abbas

When the page loads, the webapp the Involvement API to show the item likes and combines them with the data from the base API.
Remember that your page should make only 2 requests:

one to the base API
and one to the Involvement API.

This task does not include displaying the likes button (heart icon on the wireframe) for each item.

https://github.com/Log-benjamin/Microverse-Javascript-Capstone/pull/50


Refactor how to record feast metrics.

Which issue(s) this PR fixes:

Fixes not able to log NULL feature status if user didn't specify default value.
Checklist

[ ] Added unit test, integration, and/or e2e tests
[ ] Tested locally
[ ] Updated documentation
[ ] Update Swagger spec if the PR introduce API changes
[ ] Regenerated Golang and Python client if the PR introduce API changes

@ariefrahmansyah Are you going to continue this PR?


Apply registration to new image does not work using the warp_slide function.

My problem is related to closed issue, i.e, issue 63,49(Apply registration to new image), and 41(H&E deconvolution pre-processing)
I have two consecutive slides one was stained by HE(filename :211175HE) and the other was stained by H+DAB(filename: 211175CD8). The slide 211175HE and slide 211175CD8 were split into 211175HE_h,211175HE_e and 211175CD8_h and 211175CD8_d using color deconvolution, respectively.
The 211175HE_h was considered as the reference image, and 211175CD8_h registered to it beautifully. I want to use the same transformation parameters to register slide 211175CD8_d.
code file 1：
slide_src_dir = f"/data/wsi_registration/my_data1/src/211175"
results_dst_dir = f"/data/wsi_registration/my_data1/dest1_results/211175"
registered_slide_dst_dir = f"/data/wsi_registration/my_data1/dest1_slides/211175"
img_list = ['/data/wsi_registration/my_data1/src/211175/211175HE_h.tiff', '/data/wsi_registration/my_data1/src/211175/211175CD8_h.tiff']
reference_slide = f"/data/wsi_registration/my_data1/src/211175/211175HE_h.tiff"
#Create a Valis object and use it to register the slides in slide_src_dir
registrar = registration.Valis(slide_src_dir, results_dst_dir, img_list = img_list, reference_img_f=reference_slide, align_to_reference=True,
max_processed_image_dim_px=8502, max_non_rigid_registration_dim_px=8502)
rigid_registrar, non_rigid_registrar, error_df = registrar.register()
#Save all registered slides as ome.tiff
registrar.warp_and_save_slides(registered_slide_dst_dir, compression="jpeg", Q=80, crop="all") # overlap, reference, all
code file 2:
src_reg   = '/data/wsi_registration/my_data1/dest1_results/211175/211175/data/211175_registrar.pickle'
src_slide = '/data/wsi_registration/my_data1/src/211175/211175HE_h.tiff'
dst_slide = '/data/wsi_registration/my_data1/src/211175/211175CD8.tiff'
dst_dir   = '/data/wsi_registration/my_data1/dest2_slides/211175/211175CD8.ome.tiff'
#read in the registrar
registrar = pickle.load(open(src_reg,'rb'))
#pull out the previously registered slide
slide_obj = registrar.get_slide(src_slide)
warped_slide = slide_obj.warp_slide(level=0, non_rigid=True, crop="reference", src_f=dst_slide)
slide_io.save_ome_tiff(img=warped_slide, dst_f=dst_dir, compression="jpeg", Q=80)
My code file1 ran just as expected, however the slide was not registered by code file2 at all.
The paper "Virtual alignment of pathology image series for multi-gigapixel whole slide images" is great, I will cite it in my research paper. Please help me. Thanks in advance.

I have found the reason.  slide_obj = registrar.get_slide(src_slide).  The src_slide parameter in function get_slide should be the 211175CD8_h.tiff rather than the reference slide. This issue can be closed.


chore(deps): Upgrade the version of semver package from v1 to v3

Reason for the upgrade
I attempted to use the semver update strategy with the x-0 constraint.

x-0 signifies any tags that adhere to semantic versioning,  whether or not they have prerelease tags.

However, the constraint wasn't considering tags with prerelease versions as valid tags.
There was a fix^1 in Masterminds/semver package, which argocd-image-updater uses for semver checks. This fix was included in the v3.2.0 release^2 of Masterminds/semver and the lastest release is v3.2.1.
Therefore I have upgraded the version of Masterminds/semver package from v1 .5.0to v3.2.1.
Testing
I have verified that the x-0 constraint correctly handles prerelease tags by the following test code.
The test code includes multiple test cases to cover various scenarios.
Details

package tag

import (
	"fmt"
	"github.com/Masterminds/semver/v3"
	"github.com/stretchr/testify/assert"
	"strconv"
	"testing"
	"time"
)

func Test_Semver(t *testing.T) {
	for i, tt := range []struct {
		imageList  []string
		expected   string
		constraint string
	}{
		{
			imageList: []string{"v1.2.3", "v1.2.3-rc1"},
			expected:  "v1.2.3",
		},
		{
			imageList: []string{"v1.2", "v1.2.3"},
			expected:  "v1.2.3",
		},
		{
			imageList: []string{"v1.2.3-rc1", "v1.2.3"},
			expected:  "v1.2.3",
		},
		{
			imageList: []string{"v1.2.3-rc1", "v1.2.3-rc2"},
			expected:  "v1.2.3-rc2",
		},
		{
			imageList: []string{"v1.2.3-rc2", "v1.2.3-rc12"},
			// This is because if prelease tags are string,
			// they are sorted by the order of strings.
			expected: "v1.2.3-rc2",
		},
		{
			imageList:  []string{"v1.2.3-1", "v1.2.3"},
			expected:   "v1.2.3",
			constraint: "x-0",
		},
		{
			imageList:  []string{"v1.2.3-rc1", "v1.2.3-1"},
			expected:   "v1.2.3-rc1",
			constraint: "x-0",
		},
		{
			imageList:  []string{"v1.2.3-1", "v1.2.3-rc1"},
			expected:   "v1.2.3-rc1",
			constraint: "x-0",
		},
	} {
		t.Run("tt "+strconv.Itoa(i), func(t *testing.T) {
			var (
				v   *semver.Constraints
				err error
			)
			if tt.constraint != "" {
				v, err = semver.NewConstraint(tt.constraint)
				assert.NoError(t, err)
			}

			il := NewImageTagList()
			for _, tag := range tt.imageList {
				version, err := semver.NewVersion(tag)
				assert.NoError(t, err)
				if v != nil && !v.Check(version) {
					t.Logf("Constraint failed. constraint=%s, version=%s", tt.constraint, tag)
					continue
				}
				t.Logf("Constraint qualified. constraint=%s, version=%s", tt.constraint, tag)
				il.Add(NewImageTag(tag, time.Now(), ""))
			}
			sorted := il.SortBySemVer()
			answer := sorted[len(sorted)-1].TagName
			assert.Equal(t, tt.expected, answer, fmt.Sprintf("expected %s, but %s returned. sorted version: %+v", tt.expected, answer, sorted))
		})
	}
}

Codecov Report

Merging #625 (0d18b16) into master (d5a8f94) will decrease coverage by 0.29%.
Report is 4 commits behind head on master.
The diff coverage is 75.00%.

:exclamation: Current head 0d18b16 differs from pull request most recent head 22954c8. Consider uploading reports for the commit 22954c8 to get more accurate results

@@            Coverage Diff             @@
##           master     #625      +/-   ##
==========================================
- Coverage   65.63%   65.35%   -0.29%
==========================================
  Files          22       22
  Lines        2069     2084      +15
==========================================
+ Hits         1358     1362       +4
- Misses        577      588      +11
  Partials      134      134

Files Changed
Coverage Δ

pkg/argocd/git.go
66.82% <0.00%> (ø)

pkg/image/version.go
40.69% <ø> (ø)

pkg/tag/semver.go
100.00% <ø> (ø)

pkg/tag/tag.go
82.53% <ø> (ø)

pkg/argocd/gitcreds.go
76.19% <83.33%> (ø)

pkg/argocd/update.go
66.54% <83.33%> (+0.49%)
:arrow_up:

pkg/registry/client.go
12.75% <100.00%> (-0.76%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Add LinkCustomizationName to CreateLinkTokenRequest

Add LinkCustomizationName to CreateLinkTokenRequest
https://plaid.com/docs/api/tokens/#link-token-create-request-link-customization-name

Could you also add the android_package_name field? Thanks!

Could you also add the android_package_name field? Thanks!

6916cba3bd11fb01e22f3d4cc3c22e9c962be5f0

Thanks!

Released via v2.6.0


Any plans on supporting polymorphic db table relations?

For one to many relations. That would be quite handy.

This is not really necessary


Godot server fails to load gdnative libraries in C ++

Godot version:
3.1.1
OS/device including version:
x11.64 Debian 9
Issue description:
When I try to run the project with godot server I get the following error:

Fails to load the libtest.so (gdnative C++) library.
Using godot with gui instead, the project runs correctly and the libtest.so library is loaded.
Steps to reproduce:
Add any library (gdnative c ++) to the project and run one of these console commands

./server --path project.godot
./server --main-pack server.pck

For server build you should use additional "Server" platform line in the .gdnlib file:
X11.x86_64="res://bin/linux.x86_64/libtest.so" <-- for X11
Server.x86_64="res://bin/linux.x86_64/libtest.so" <-- for Server

For server build you should use additional "Server" platform line in the .gdnlib file:
X11.x86_64="res://bin/linux.x86_64/libtest.so" <-- for X11
Server.x86_64="res://bin/linux.x86_64/libtest.so" <-- for Server

ok, it worked and I thank you and I hope it can serve others.
Running it on Centos he pointed out the error:
ERROR: open_dynamic_library: Method / Function Failed, returning: ERR_CANT_OPEN

I tried to add the text below but it didn't work:
env.Append (LINKFLAGS = [
     '-Wl, -rpath ' $$ ORIGIN \ '/ lib'
])

I tried to add LD_LIBRARY_PATH but it didn't work:
export LD_LIBRARY_PATH = $ (pwd) /: $ (pwd) / lib /

I tried to compile the library in the same path as the executable but it didn't work.

Finally I tried to replace:
         env.Append (CCFLAGS = ['-fPIC', '-g', '- O3', '-std = c ++ 17'])
     IN
        env.Append (CCFLAGS = ['-fPIC', '-g', '- O3', '-std = c ++ 11'])
and the latter solved the problem.

In practice with the transition to C ++ 11, it allowed the executable to find the right path to the library.
Are there performance differences using C ++ 11 instead of C ++ 17?
Excuse me for not perfect English.

Are there performance differences using C ++ 11 instead of C ++ 17?

With the same compiler version and the same code as input, it's unlikely to show any performance differences. However, recent compilers often perform better than older compilers.
Still, if you wish to distribute portable binaries/libraries, these should be built on the oldest distribution you wish to support, which naturally limits the compiler (and C++ language) versions you can use.

Thanks for the info.

How about documenting this case and making it accessible through Editor UI?
I spent like 2 hours of my life trying to realize why godot-headless didn't work with my .so lib!

@mintyleaf I think the Server platform should just attempt to load the library defined for X11 or macOS (Server can run on macOS too since 3.2). This way, users don't need to define the library path twice.

FYI here is the PR related to the Server / Headless GDNative library issue: https://github.com/godotengine/godot/pull/38898


Set installation paths for lc so that clang can search for headers

Done. :-)

This doesn't work on CI because of some path issues with clang. I am trying to reproduce it locally.

So the clang from conda-forge is broken. However the clang provided in compilers package works fine. However that environment installs some version of LLVM which cannot be compiled on Linux (a separate issue). To start work on std::span I am just testing it on macOS for now which works on CI as well.
Will merge this PR once it passes.


Adjusted WLAN_HOSTED_NETWORK_DATA_PEER_STATE_CHANGE members layout

Placed PeerStateChangeReason description where it belongs

@alexbereznikov : Thanks for your contribution! The author(s) have been notified to review your proposed change.


[FLINK-15360][e2e] Fix the parameter issue in retry_times

What is the purpose of the change
This PR fix the parameter issue in retry_times function of common.sh.
Brief change log
Fix the parameter issue in retry_times function of common.sh.
Verifying this change
Trigger container relevant e2e tests.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

cc: @wangyang0918 @tillrohrmann
Since it's a blocker issue for e2e test, I open this PR without being assigned first.

After https://github.com/apache/flink/commit/bdd432a09a776fec88f465771101893a8151dc1d , the retry_times function could not accept commands with multiple parts split by whitespace. This PR fix that problem.

Travis give green light to relevant tests https://travis-ci.org/KarmaGYZ/flink/builds/628343573

This is really a magic code. However, i think it could work. Because when we define a new local shell variable and then pass it to the function retry_times_with_backoff_and_cleanup, it will be treated as one argument. If we directly pass ${@:3} to the function, since it a shell array, they will be treated as multiple arguments in retry_times_with_backoff_and_cleanup.

@flinkbot run travis

Thanks for the fix @KarmaGYZ . After the travis pass, you can ping me then i would merge it.

In addition, it is better to copy some descriptions from jira ticket to the commit content. Then it would be helpful to further understand the motivation and changes of this commit. You can also submit a pr for the release-1.10 branch.

@flinkbot run azure

Travis passed.
cc @zhijiangW .

Quick question, isn't the problem that we pass the command in https://github.com/apache/flink/commit/cce1cef50d993aba5060ea5ac597174525ae895e as multiple strings instead of wrapping the command in "" before we pass it to retry_times? If I look at retry_times_with_backoff_and_cleanup then one also needs to pass the command and cleanup_command as a single string (meaning one needs to wrap it into ""). The fix seems to underline this as we are joining ${@:3} into a single string.

Quick question, isn't the problem that we pass the command in cce1cef as multiple strings instead of wrapping the command in "" before we pass it to retry_times? If I look at retry_times_with_backoff_and_cleanup then one also needs to pass the command and cleanup_command as a single string (meaning one needs to wrap it into ""). The fix seems to underline this as we are joining ${@:3} into a single string.
The problem now is that retry_times and retry_times_with_backoff_and_cleanup behave differently wrt their parameters.

Before bdd432, retry_times will joining ${@:3} into a single string. So, I think that commit changes the contract of retry_times, not as excepted. This PR fix that problem.
Regarding to the inconsistent parameter, I agreed it's better to align the behavior of two functions. We could work on it in future work. WDYT?


Publish 0.5.2

Diff : https://github.com/tomaka/vulkano/compare/609056d0b0c2db6b0a64c84dfbd34f11a1f6bac5...b63b49d204c53088ff48f1b613cd2b02395d50c7
Major changes: #613 #603 #615 #616 #618 #619

I also want to slip in #622


mne.viz _plot_topo ylim

I couldn't set the ylim in some cases because they were being turned into something like [(-50,),(,100)] and abs() doesn't work on tuples. I added:
import numpy as np
ylim_ = np.squeeze(ylim_).tolist();
to _plot_topo and it seems to work now.

Closing, I'm assuming this one has been resolved. Feel free to re-open if not.


Keras documentation of multi_gpu_model: example 2 can be misleading

In the Keras documentation for multi_gpu_model, it is stated:

To save the multi-gpu model, use .save(fname) or .save_weights(fname) with the template model (the argument you passed to multi_gpu_model), rather than the model returned by multi_gpu_model.

However in example 2 the template model is overwritten by the multi-gpu model:
         ..
         # Not needed to change the device scope for model definition:
         model = Xception(weights=None, ..)
         try:
             model = multi_gpu_model(model, cpu_relocation=True)
             print("Training using multiple GPUs..")
         except:
             print("Training using single GPU or CPU..")
         model.compile(..)
         ..

This means that in this example it would not be possible to save the weights of the template model. I suggest rewritting to something like:
         ..
         # Not needed to change the device scope for model definition:
         model = Xception(weights=None, ..)
         try:
             parallel_model = multi_gpu_model(model, cpu_relocation=True)
             print("Training using multiple GPUs..")
         except ValueError:
             parallel_model = model
             print("Training using single GPU or CPU..")
         parallel_model.compile(..)
         ..

(I take this opportunity to except only a specific error)

You are totally right. Thanks!


Update benchmark and control tags for compatibility with dashboard page

Checklist

[ ] Issue(s) linked

@misraved pls associate the images in PR, check OCI/AWS for reference


/staff

/staff always displays that no staff are online.

I will look into it, but am informing everyone

I will look into it, but am informing everyone

I cannot fix this issue, I am handing it over to whoever wants it.

I'll look into this.


SARibbon in QT Designer

Hi,
Can I install SARibbon in QTDesigner? Where can I find the instructions to compile plugin?

At present, there is no well-established Qt Designer solution. I have developed plugins before, but I am unable to implement the solution of dragging actions to the ribbon pannel and setting action properties. Therefore, the development plan for plugins has been temporarily put on hold.
Mainwindow can be built using Designer and completed with code during the menu (ribbon) construction process


Issue with "Cortex Data Lake" in @site/docs/reference/integrations/cortex-data-lake.md

Describe the problem
Backticks in example command syntax for !cdl-query-logs get rendered as markdown styling elements when viewed in the browser and do not come through when copying/pasting text to another window.  This causes the requirement of backticks in the query to be unclear in the documentation.

Screenshots

Environment

OS: [e.g. Windows]
Browser: [e.g. chrome, safari, firefox..]
Browser Version:

Suggested fix
Escape the backticks in the example SQL syntax for the cdl-query-logs command so they are visible in the browser.

@mikejrizzo thanks for reporting this
not sure I understand the issue, this is how i see it:

which seems fine to me
also, i can copy and paste it as expected
can you please clarify whats wrong here?

@mikejrizzo thanks for reporting this, we will fix it


Fix/retrieve historical candles

Before submitting this PR, please make sure:

[x] Your code builds clean without any errors or warnings
[x] You are using approved title ("feat/", "fix/", "docs/", "refactor/")

A description of the changes proposed in the pull request:
As continuation of https://github.com/hummingbot/hummingbot/pull/7142,

Keep previous features added by @jbekker
Fix Binance Spot Candles implementation
Fix kraken "since" param
Isolate missing records from fetch candles logic to access it either from fill_historical_candles or get_historical_candles

Tests performed by the developer:

Create a jupyter notebook at hummingbot's root level and run this code, try to download all historical candles through get_historical_candles method and plot them with:

import plotly.graph_objects as go
import pandas as pd
import datetime
import time

from hummingbot.data_feed.candles_feed.ascend_ex_spot_candles.ascend_ex_spot_candles import AscendExSpotCandles
from hummingbot.data_feed.candles_feed.binance_perpetual_candles import BinancePerpetualCandles
from hummingbot.data_feed.candles_feed.binance_spot_candles import BinanceSpotCandles
from hummingbot.data_feed.candles_feed.bybit_perpetual_candles.bybit_perpetual_candles import BybitPerpetualCandles
from hummingbot.data_feed.candles_feed.bybit_spot_candles.bybit_spot_candles import BybitSpotCandles
from hummingbot.data_feed.candles_feed.gate_io_perpetual_candles import GateioPerpetualCandles
from hummingbot.data_feed.candles_feed.gate_io_spot_candles import GateioSpotCandles
from hummingbot.data_feed.candles_feed.hyperliquid_perpetual_candles.hyperliquid_perpetual_candles import (
    HyperliquidPerpetualCandles,
)
from hummingbot.data_feed.candles_feed.kraken_spot_candles.kraken_spot_candles import KrakenSpotCandles
from hummingbot.data_feed.candles_feed.kucoin_perpetual_candles.kucoin_perpetual_candles import KucoinPerpetualCandles
from hummingbot.data_feed.candles_feed.kucoin_spot_candles.kucoin_spot_candles import KucoinSpotCandles
from hummingbot.data_feed.candles_feed.mexc_perpetual_candles.mexc_perpetual_candles import MexcPerpetualCandles
from hummingbot.data_feed.candles_feed.mexc_spot_candles.mexc_spot_candles import MexcSpotCandles
from hummingbot.data_feed.candles_feed.okx_perpetual_candles.okx_perpetual_candles import OKXPerpetualCandles
from hummingbot.data_feed.candles_feed.okx_spot_candles.okx_spot_candles import OKXSpotCandles

from hummingbot.data_feed.candles_feed.data_types import HistoricalCandlesConfig

classes = [
    AscendExSpotCandles,
    BinancePerpetualCandles,
    BinanceSpotCandles,
    BybitPerpetualCandles,
    BybitSpotCandles,
    GateioPerpetualCandles,
    GateioSpotCandles,
    HyperliquidPerpetualCandles,
    KrakenSpotCandles,
    KucoinPerpetualCandles,
    KucoinSpotCandles,
    MexcPerpetualCandles,
    MexcSpotCandles,
    OKXPerpetualCandles,
    OKXSpotCandles
]

def date_to_seconds(year, month, day):
    date = datetime.datetime(year, month, day)
    timestamp = time.mktime(date.timetuple())
    return int(timestamp)

trading_pair = "BTC-USDT"
interval = "1h"
start_time_secs = date_to_seconds(2024, 8, 3)
end_time_secs = date_to_seconds(2024, 8, 6)

df = pd.DataFrame()
for i in range (0, len(classes)):
    print(classes[i].__name__)
    candles = classes[i](trading_pair, interval)
    config = HistoricalCandlesConfig(connector_name="",
                                     trading_pair=trading_pair,
                                     interval=interval,
                                     start_time=start_time_secs,
                                     end_time=end_time_secs,)

    candles_df = await candles.get_historical_candles(config)
    candles_df['connector_name'] = classes[i].__name__
    candles_df['step'] = ','.join(map(str, [step for step in candles_df.timestamp.diff()[1:].unique().tolist()]))
    candles_df['timestamp'] = pd.to_datetime(candles_df['timestamp'], unit="s")
    df = pd.concat([df, candles_df])
    print(f"Timestamp diff unique: {candles_df.timestamp.diff().unique()}")

    fig = go.Figure(data=[go.Candlestick(x=candles_df['timestamp'],
                    open=candles_df['open'],
                    high=candles_df['high'],
                    low=candles_df['low'],
                    close=candles_df['close'])])
    fig.update_layout(xaxis_rangeslider_visible=False)
    fig.show()

After running previous cell, check for candles consistency in a summarized table with:

df.groupby(["connector_name", "step"]).agg({"timestamp": ["first", "last"],
                                  "open": "first",
                                  "high": "first",
                                  "low": "first",
                                  "close": "first"})

For live candles, use the following script and run status --live to compare with exchange

from typing import Dict

import pandas as pd
import pandas_ta as ta  # noqa: F401

from hummingbot.connector.connector_base import ConnectorBase
from hummingbot.data_feed.candles_feed.candles_factory import CandlesConfig, CandlesFactory
from hummingbot.strategy.script_strategy_base import ScriptStrategyBase

class StreamCandles(ScriptStrategyBase):
    """
    This script is a simple example of how to use the Candles Factory to create a candlestick and start it.
    """
    # Available intervals: |1s|1m|3m|5m|15m|30m|1h|2h|4h|6h|8h|12h|1d|3d|1w|1M|
    # Is possible to use the Candles Factory to create the candlestick that you want, and then you have to start it.
    # Also, you can use the class directly like BinancePerpetualsCandles(trading_pair, interval, max_records), but
    # this approach is better if you want to initialize multiple candles with a list or dict of configurations.
    candles = CandlesFactory.get_candle(CandlesConfig(connector="hyperliquid",
                                                      trading_pair="PURR-USDT",
                                                      interval="1m",
                                                      max_records=200))

    # The markets are the connectors that you can use to execute all the methods of the scripts strategy base
    # The candlesticks are just a component that provides the information of the candlesticks
    markets = {"binance_paper_trade": {"SOL-USDT"}}

    def __init__(self, connectors: Dict[str, ConnectorBase]):
        # Is necessary to start the Candles Feed.
        super().__init__(connectors)
        self.candles.start()

    def on_tick(self):
        pass

    def on_stop(self):
        """
        Without this functionality, the network iterator will continue running forever after stopping the strategy
        That's why is necessary to introduce this new feature to make a custom stop with the strategy.
        :return:
        """
        self.candles.stop()

    def format_status(self) -> str:
        """
        Displays the three candlesticks involved in the script with RSI, BBANDS and EMA.
        """
        if not self.ready_to_trade:
            return "Market connectors are not ready."
        lines = []
        lines.extend(["\n############################################ Market Data ############################################\n"])
        candles_df = self.candles.candles_df
        # Let's add some technical indicators
        candles_df.ta.ema(length=14, offset=None, append=True)
        candles_df["timestamp"] = pd.to_datetime(candles_df["timestamp"], unit="s")
        lines.extend([f"Candles: {self.candles.name} | Interval: {self.candles.interval}"])
        lines.extend(["    " + line for line in candles_df.tail().to_string(index=False).split("\n")])
        lines.extend(["\n-----------------------------------------------------------------------------------------------------------\n"])

        return "\n".join(lines)

Tips for QA testing:

All get_historical_candles results must:

start and end at the same time (in my case, 3:00am because i'm located at UTC-3)
appear only one time, if there are more steps than 3600 for 1h interval is because there are gaps that need to be filled
match ohlc values with exchange
for hyperliquid spot candles, should import correspondent candle feed and check which markets are available in the exchange, i.e. PURR-USDC

@nikspz @rapcmia @cardosofede ready for review!

Test in progress

PR update using commit ef4f299245ff517c4b2fbb26b99abdc11165ae00

Ran tests on local using macOs(m1)
Create jupyter notebook

Got an error when running the notebook
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x105c66da0>
AscendExSpotCandles
Error fetching historical candles: Cannot connect to host ascendex.com:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1007)')]
Traceback (most recent call last):
      File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/aiohttp/connector.py", line 1025, in _wrap_create_connection
    return await self._loop.create_connection(*args, **kwargs)
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/asyncio/base_events.py", line 1103, in create_connection
    transport, protocol = await self._create_connection_transport(
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/asyncio/base_events.py", line 1133, in _create_connection_transport
    await waiter
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/asyncio/sslproto.py", line 534, in data_received
    ssldata, appdata = self._sslpipe.feed_ssldata(data)
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/asyncio/sslproto.py", line 188, in feed_ssldata
    self._sslobj.do_handshake()
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/ssl.py", line 975, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1007)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/Users/rapcomia/github/hummingbot/7160/hummingbot/data_feed/candles_feed/candles_base.py", line 171, in get_historical_candles
    fetched_candles = await self.fetch_candles(end_time=current_end_time, missing_records=missing_records)
  File "/Users/rapcomia/github/hummingbot/7160/hummingbot/data_feed/candles_feed/candles_base.py", line 229, in fetch_candles
    candles = await rest_assistant.execute_request(url=self.candles_url,
  File "/Users/rapcomia/github/hummingbot/7160/hummingbot/core/web_assistant/rest_assistant.py", line 47, in execute_request
    response = await self.execute_request_and_get_response(
  File "/Users/rapcomia/github/hummingbot/7160/hummingbot/core/web_assistant/rest_assistant.py", line 94, in execute_request_and_get_response
    response = await self.call(request=request, timeout=timeout)
  File "/Users/rapcomia/github/hummingbot/7160/hummingbot/core/web_assistant/rest_assistant.py", line 108, in call
    resp = await wait_for(self._connection.call(request), timeout)
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/asyncio/tasks.py", line 408, in wait_for
    return await fut
  File "/Users/rapcomia/github/hummingbot/7160/hummingbot/core/web_assistant/connections/rest_connection.py", line 10, in call
    aiohttp_resp = await self._client_session.request(
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/aiohttp/client.py", line 581, in _request
    conn = await self._connector.connect(
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/aiohttp/connector.py", line 544, in connect
    proto = await self._create_connection(req, traces, timeout)
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/aiohttp/connector.py", line 944, in _create_connection
    _, proto = await self._create_direct_connection(req, traces, timeout)
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/aiohttp/connector.py", line 1257, in _create_direct_connection
    raise last_exc
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/aiohttp/connector.py", line 1226, in _create_direct_connection
    transp, proto = await self._wrap_create_connection(
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/aiohttp/connector.py", line 1027, in _wrap_create_connection
    raise ClientConnectorCertificateError(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorCertificateError: Cannot connect to host ascendex.com:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1007)')]
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
Cell In[3], line 66
     59 config = HistoricalCandlesConfig(connector_name="",
     60                                  trading_pair=trading_pair,
     61                                  interval=interval,
     62                                  start_time=start_time_secs,
     63                                  end_time=end_time_secs,)
     65 candles_df = await candles.get_historical_candles(config)
---> 66 candles_df['connector_name'] = classes[i].__name__
     67 candles_df['step'] = ','.join(map(str, [step for step in candles_df.timestamp.diff()[1:].unique().tolist()]))
     68 candles_df['timestamp'] = pd.to_datetime(candles_df['timestamp'], unit="s")

TypeError: 'NoneType' object does not support item assignment

Same error occurred on other connectors
Compared wth @nikspz running on local Windows and seem to work on his end

Steps to reproduce:

Conda activate hummingbot and run jupyter notebook on hummingbot root folder
Create notebook and select kernel python 3 (ipykernel)
Run the notebook

Run script provided by dev then compare OHLC data from hummingbot and exchanges while on status --live

Run tests 5m and 15ms with candles data of 200, 300 and 1000
Compare candles data between hummingbot and exchange each interval is completed (3/3)
Run candles data that exceeds 1000 and observe
Connectors tested:

Kraken - ok but can only cater max of 720
Ascendex - ok
Kucoin spot and perpetual - ok
Mexc spot and perpetual not started
OKX spot and perpetual not started

@rapcmia hmm.. That problem is related to python itself. There might be some steps to troubleshoot that error:

check your jupyter notebook is properly setup with hummingbot environment, even being started after conda activate hummingbot
verify that your hbot environment is up to date, try removing and installing again conda environment

otherwise, i'm afraid that since i'm using a linux machine i can't help :(

PR update:

Thanks @tomasgaudino for the help, yep ill have a look tonight about the jupyter notebook
Re-run tests on kucoin perpetual

Rerun tests on kucoin connector and found this behavior on perpetual
Compare these behaviors on development, not able to reproduce
Screen recording here https://www.loom.com/share/31d239b97a7a404aa35b90f23004dca8

Run candles script on okx

For spot, run test on 5m interval 200 records, 15m for 500 records

Both scripts running on 1 and 2 markets return same behavior

Observed than when I change the record from 200 → 1000, this behavior occurred.
Also observed when running 1 market script candles data getting ..candles are not sorted by timestamp in ascending order.
Compare the results on development branch not able to reproduce this behavior

For perpetual, Run test on 5m interval 200 records, 15m for 500 records

Im not getting the behavior from spot but these are not happening as well on development branch when crosschecked using same scripts
On single market candles script, we only use records of max_records of 200 and 500

Run candles script on mexc

For spot and perpetual,

Compare OHLC data between hummingbot and exchange all matched
Observed quote_asset_volume are present and matched as well
However comparing this PR with development branch observed:

This PR has the most activity of error The websocket connection was closed (The WS connection was closed unexpectedly. Close code = 1006 msg data: 0)

Steps to reproduce: see attached for the scripts

Use single and multi market pair
Observed behavior when using max_records 200, 500 and values more than 1000
Compare OHLC data between hummingbot and exchange when running status --live

08082024.zip

Jupyter notebook: ok, reviewed showed candles for connectors
@tomasgaudino
Candles script for dif connectors:

binance: ok

binance_perpetual: ok

bybit spot

OHLC matched with exchange ✅
no quote asset volume for ETH-USDT ❌

bybit perpetual:

OHLC not matched with exchange ❌
no quote asset volume for ETH-USDT ❌

gate_io spot:

OHLC matched with exchange ✅
volume shows USDT (not base ETH) for ETH-USDT ❌

gate_io perpetual:

OHLC not matched with exchange ❌
no quote asset volume for ETH-USDT ❌

hyperliquid spot/perpetual:
Hyperliquid spot no quote asset volume for PURR-USDC ❌

Hyperliquid perpetual no quote asset volume for BTC-USD ❌

Thanks for the feedback @nikspz ,

As discussed with @cardosofede we will not be including quote volume if the exchange API doesn't offer it. I've checked again the exchange docs mentioned and the param is missing
Fixed Gate IO spot base/quote volume inversion in websocket
For mismatched candles, I've checked again and they are working properly

@rapcmia after some checks:

For kucoin perpetual candles i've disabled start time param leading to a correct behaviour

For OKX i've reproduced every combination you provided and worked fine for me. After reading your logs, the error that you're getting is because apparently the execution exceeded the candles endpoint rate limit. I've checked definition and it's ok since it's the same for spot or perp. Is it possible that you've been running tests in separated instances of hummingbot? It's the only error source that I can imagine for now

About MEXC the websocket connection might be disconnecting because of the ausence of trades and ping/pong handling, a feature previously discussed with @cardosofede and present in backlog for next PR -this one is time-sensitive due to the release of the next version next week-

PR update:

Thanks @tomasgaudino for the help, yep ill have a look tonight about the jupyter notebook

Re-run tests on kucoin perpetual

Rerun tests on kucoin connector and found this behavior on perpetual
Compare these behaviors on development, not able to reproduce
Screen recording here https://www.loom.com/share/31d239b97a7a404aa35b90f23004dca8

Run candles script on okx

For spot, run test on 5m interval 200 records, 15m for 500 records

Both scripts running on 1 and 2 markets return same behavior

Observed than when I change the record from 200 → 1000, this behavior occurred.
Also observed when running 1 market script candles data getting ..candles are not sorted by timestamp in ascending order.
Compare the results on development branch not able to reproduce this behavior

For perpetual, Run test on 5m interval 200 records, 15m for 500 records

Im not getting the behavior from spot but these are not happening as well on development branch when crosschecked using same scripts
On single market candles script, we only use records of max_records of 200 and 500

Run candles script on mexc

For spot and perpetual,

Compare OHLC data between hummingbot and exchange all matched

Observed quote_asset_volume are present and matched as well

However comparing this PR with development branch observed:

This PR has the most activity of error The websocket connection was closed (The WS connection was closed unexpectedly. Close code = 1006 msg data: 0)

Steps to reproduce: see attached for the scripts

Use single and multi market pair
Observed behavior when using max_records 200, 500 and values more than 1000
Compare OHLC data between hummingbot and exchange when running status --live

08082024.zip
Todo:

Run this PR with ongoing tests on quants-lab not started

789a433
Candles script for dif connectors:

binance: ok

OHLC matched with exchange :white_check_mark:
volume is correct  :white_check_mark:

binance_perpetual: ok

OHLC matched with exchange :white_check_mark:
volume is correct  :white_check_mark:

bybit spot

OHLC matched with exchange :white_check_mark:
no quote asset volume for ETH-USDT, base volume is correct :white_check_mark:

bybit perpetual:

OHLC matched with exchange
no quote asset volume for ETH-USDT, base volume is correct :white_check_mark:

gate_io spot:

OHLC matched with exchange :white_check_mark:
volume is correct  :white_check_mark:

gate_io perpetual:

OHLC matched with exchange :white_check_mark:
no quote asset volume for ETH-USDT, base volume is correct :white_check_mark:

hyperliquid spot:

OHLC matched with exchange :white_check_mark:
Hyperliquid spot no quote asset volume for PURR-USDC, base volume is correct :white_check_mark:

hyperliquid perpetual:

OHLC matched with exchange :white_check_mark:
Hyperliquid perpetual no quote asset volume for BTC-USD, base volume is correct :white_check_mark:


Temporarily disable PATs until next release

This might be a bit contentious, but I think we should try to limit the impact of deprecating scoped PATs with the rewrite proposed here we're working on for v1.20: https://github.com/go-gitea/gitea/issues/24501
We should have a PR opened shortly to re-scope the routes.

So, I can see two options after this PR:

The replacement PR is merged in time.
The replacement PR is not merged in time, and this PR will be reverted.

Another thing to note is that handling the already existing scoped PATs will be absolutely horrifying.

So, I can see two options after this PR:

The replacement PR is merged in time.
The replacement PR is not merged in time, and this PR will be reverted.

Another thing to note is that handling the already existing scoped PATs will be absolutely horrifying.

Well, we have a few options:

Migrate existing scoped PATs to new ones (kind of annoying)
Backport this to 1.19.3 and announce a breaking change, then reject all of the old scope tokens in 1.20 (so that users have to regenerate them)

Backport this to 1.19.3 and announce a breaking change, then reject all of the old scope tokens in 1.20 (so that users have to regenerate them)

I don't see this as a viable option.
That is a huge violation of semver, for an outcome that is not yet known.

Migrate existing scoped PATs to new ones (kind of annoying)

I know, but I see that as the only viable option here.

Throwing a breaking label on this PR so it gets reviewed again when writing the next blog post in case the proposed solution above doesn't come about in time.

Looks like we'll be able to get the new design merged, hence removing the breaking label.


add option to propagate binaries without access to internet

its allow to download binary from own store

Please fix issues reported by Travis CI: https://travis-ci.com/cloudalchemy/ansible-node-exporter/jobs/258266272#L280-L288 and add molecule tests. Everything can be found in https://github.com/cloudalchemy/ansible-prometheus/pull/239

Styling errors are fixed

Great job on fixing errors.
This still needs molecule tests before it is merged.

is this molecule check
https://travis-ci.com/cloudalchemy/ansible-node-exporter/builds/137379386

This is our CI output of molecule tests. You can run those locally by following https://github.com/cloudalchemy/ansible-node-exporter#local-testing.
What we need is to extend those to cover feature included in this PR, same way as it is happening in cloudalchemy/ansible-prometheus#239

moleculetest-ansible-node-exporter.txt

Sorry, but I don't know what I have to do with this file.
I was saying about adding molecule tests in code to this PR. Things like this:

https://github.com/cloudalchemy/ansible-prometheus/blob/dc277d8db3c8d0682f4b2a9fc98df0cba7993938/molecule/alternative/prepare.yml
https://github.com/cloudalchemy/ansible-prometheus/blob/dc277d8db3c8d0682f4b2a9fc98df0cba7993938/molecule/alternative/playbook.yml

Additionally. I just noticed that this PR is adding new variable to defaults/main.yml. This needs to be reflected in README.md file in Role Variables section.

Closing as this was already done in #126


No audio support

How to add audio support to rtp-stream-fix.js? I am not getting any audio but can see the video. Is it the same for you?
Originally posted by @Raj123456788 in https://github.com/eduardomota/ffmpeg-stream/issues/2#issuecomment-747138718

I'm not sure about the audio part, that may be due to flaws on the lib itself, i would need to dive in, this is basically on the same level as the filtergraph issue maybe a little less. If you're able to figure this out you may post it here.


SOL_ALL_SAFETIES_ON in sol³ doesn't handle nil arguments or mismatched types

System: Linux desktop 5.3.1-arch1-1-ARCH #1 SMP PREEMPT Sat Sep 21 11:33:49 UTC 2019 x86_64 GNU/Linux
Compiler: g++ (GCC) 9.1.0
Sol version: b2c22ea
I'm running into two issues related to the SOL_ALL_SAFETIES_ON flag seeming to fail on me:

Providing a nil argument to a bound usertype triggers a SEGV
Providing the wrong type of argument (A Vec3 instead of a Material) silently fails, causing undefined behavior later in my program.

Reproducible gist here: https://gist.github.com/Samulus/27d6db0aebe0f3c51e4c8dc52fec306a

No repro on silent failure: handler gets called.

Repro on SEGV on all platforms.

Hmm, I have a problem with SOL_ALL_SAFETIES_ON, where it throws on mismatched types (expected = boolean) and (actual = sol::nil). It throws in error_handler.hpp somewhere on line 96.

@xzores That sounds exactly expected.

but can't I say something like never throw?

I call safe_script in a try catch

safe_script(the_script, ..., sol::script_pass_on_error);, or pass in your own handler. See the tutorials and examples for more information: https://github.com/ThePhD/sol2/blob/develop/examples/source/tutorials/quick_n_dirty/running_lua_code_safely.cpp#L28

This is fixed now, pull from latest.

:+1: Thanks for fixing this. The silent failure you couldn't reproduce now fails as expected on my machine. SEGV is gone too.


Fixing up the notification is not being sent for the user that has been added from the filamentphp dashboard

 //fixing up creation token not created and the notification not sended
protected function mutateFormDataBeforeCreate(array $data): array     {
$data['type'] = "db";         return parent::mutateFormDataBeforeCreate($data);     }

Please create a pull request with this fix.

I installed Helper on Firday (12 July 2024) on my local machine. Everything looks to be fine except for sending a notifaction when I create new user. What must I do to get this working?

I installed Helper on Firday (12 July 2024) on my local machine. Everything looks to be fine except for sending a notifaction when I create new user. What must I do to get this working?

I had to make few changes to get this working. I am not sorted.

Can you make a PR with the changes that you did, so we can fix the problem?

Can you make a PR with the changes that you did, so we can fix the problem?

My fix is almost similar to what AbbasovMakrov did. If he hasn't created a pull request, I can create one.

where do i need to put this fix? thx in advance


ci: Expand PR test triggers

I found that the auto-release PRs don't trigger tests for some reason.
This makes it so that we don't get the required "validate PR title"
run, and we also don't get automated test passes against release
candidates.
This replaces the PR triggers for both workflows with a set that
includes "edited" and "ready_for_review".  Now any PR that doesn't get
properly tested can have tests triggered by either editing the body or
taking it in and out of draft mode.

I tested the "build and test" part of this on a branch, and it's working.  The "validate title" workflow can only be run on the master branch, but I assume the same set of triggers will work.


Add doc to use GET with allow_redirects=False

It was not easy to find who to get  allow_redirects to work.
I finally found how to use it in this PR
https://github.com/bulkan/robotframework-requests/pull/43/files
Use: =${false}
Get Request Without Redirection
    [Tags]  get
    Create Session  httpbin  http://httpbin.org

    ${resp}=  Get  httpbin  /redirect/1  allow_redirects=${false}
    ${status}=  Convert To String  ${resp.status_code}
    Should Start With  ${status}  30

Having an example is the doc could be helpfull

@kenden i will update here http://bulkan.github.io/robotframework-requests/

Sounds good, thanks!


make-redux-sudoku using react

Sudoku is a fun puzzle game  and a classic game. Has Undo and problem solver.

Hey @Shreyaar12 Can you assign this to me i want to make it

Please assign this issue to me @Shreyaar12

Hey Shreya , I want to contribute in this issue , I'll also add option like level of game i.e. easy , medium , hard . Please assign me this issue @Shreyaar12 , I'm a member of Gssoc`23 .


Add support for OSM vector tiles

Although OSM vector tiles are not ideal, they are used frequently. This pull request adds support for them, by implementing vector tile feature reprojection in a generic way.
Inspired by https://github.com/openlayers/ol3/issues/4516#issue-120399895.

I'll make the suggested example changes. Thanks for the review so far.

I addressed all your comments @bartvde, and added more tests.

LGTM please merge

Done @tsauerwein.

Did you want to take another look @tsauerwein?

Thanks, this looks good to me.