Deprecation warnings in 4.1.0

Environment
How do you use Sentry?
self-hosted
Which SDK and version?
sentry-symfony 4.1.0
symfony 5.2.6
Steps to Reproduce
Symfony reports a couple of deprecation warnings
1x: The "Sentry\SentryBundle\Tracing\Doctrine\DBAL\TracingDriver" class implements "Doctrine\DBAL\Driver\ExceptionConverterDriver" that is deprecated.

  1x: The "Sentry\State\HubAdapter::captureMessage()" method will require a new "EventHint|null $hint" argument in the next major version of its interface "Sentry\State\HubInterface", not defining it is deprecated.

  1x: The "Sentry\State\HubAdapter::captureException()" method will require a new "EventHint|null $hint" argument in the next major version of its interface "Sentry\State\HubInterface", not defining it is deprecated.

  1x: The "Sentry\State\HubAdapter::captureLastError()" method will require a new "EventHint|null $hint" argument in the next major version of its interface "Sentry\State\HubInterface", not defining it is deprecated.

Expected Result
no warnings
Actual Result

The last three deprecations are fixed in https://github.com/getsentry/sentry-php/pull/1206, and will be released in the next patch version of sentry/sentry.
The first one instead is tricky, and I'm not sure we can overcome it... DBAL is pretty entangled now.

bin/console doctrine:migrations:list -q
2021-09-20T21:12:46+03:00 [info] User Deprecated: The "Sentry\SentryBundle\Tracing\Doctrine\DBAL\TracingDriver" class implements "Doctrine\DBAL\Driver\ExceptionConverterDriver" that is deprecated.

How to suppress this error message?

We're trying something more with #553, but it's possible that those deprecations will never go away since we have to support both DBAL v2 & v3 at the same time.

But how can i suppress this message from output, when i call bin/console doctrine:migrations:list?
Is there any way to hide it from output?

That's due to Symfony, not us, you need to check their docs.

I don't deeply understand how errors are handled, but i think that it's an error(notice) inside error handler, and that is why it is not handled by other error handlers and go to STD_ERR in console.
monolog:
    handlers:
        sentry:
            type: sentry
            level: !php/const Monolog\Logger::ERROR
            hub_id: Sentry\State\HubInterface
        php_info_filter:
            type: filter
            handler: php_info
            accepted_levels: ["info"]
            channels: ["php"]
            bubble: false
        php_info:
            type: stream
            path: "%kernel.logs_dir%/%kernel.environment%.php_info.log"
        main:
            type: stream
            path: "%kernel.logs_dir%/%kernel.environment%.log"
            level: debug
            channels: ["!event"]
        # uncomment to get logging in your browser
        # you may have to allow bigger header sizes in your Web server configuration
        #firephp:
        #    type: firephp
        #    level: info
        #chromephp:
        #    type: chromephp
        #    level: info
        console:
            type: console
            process_psr_3_messages: false
            channels: ["!event", "!doctrine", "!console"]

I bet it won't, but can you please try updating to 4.2.3 and see if it solves the problem?

I don't deeply understand how errors are handled, but i think that it's an error(notice) inside error handler, and that is why it is not handled by other error handlers and go to STD_ERR in console.

It's a deprecation, so it's handled like that. Since Symfony 5.1+, there's a dedicated channel: https://github.com/symfony/recipes/blob/master/symfony/monolog-bundle/3.7/config/packages/prod/deprecations.yaml

I bet it won't, but can you please try updating to 4.2.3 and see if it solves the problem?

Hi @ste93cry. Upgrading to 4.2.3 has removed the deprecation warning. I was on 4.2.2 previously.

I think that the deprecation gone because you also upgraded the doctrine/dbal package to 3.x, otherwise it doesn't make sense because we're still implementing the old interface

IIUC, the warnings should be gone in the latest 4.2.3 release, right? If yes, can we close the issue?

I just checked some projects I work on and I definitely still see the deprecation about the ExceptionConverterDriver interface. Unfortunately, the issue is not that easy to solve because we have to implement all interfaces to avoid failures with instanceof checks 😞

Still seing deprecations in 4.2.3
2022-02-02T18:39:03+00:00 [info] User Deprecated: Class "Sentry\SentryBundle\Tracing\Doctrine\DBAL\TracingDriverConnection" should implement method "Doctrine\DBAL\Driver\Connection::getNativeConnection(): resource|object".
2022-02-02T18:39:03+00:00 [info] User Deprecated: Class "Sentry\SentryBundle\Tracing\Doctrine\DBAL\TracingServerInfoAwareDriverConnection" should implement method "Doctrine\DBAL\Driver\Connection::getNativeConnection(): resource|object".
2022-02-02T18:39:03+00:00 [info] User Deprecated: The "Sentry\SentryBundle\Tracing\Doctrine\DBAL\TracingServerInfoAwareDriverConnection" class implements "Doctrine\DBAL\Driver\ServerInfoAwareConnection" that is deprecated The methods defined in this interface will be made part of the {@see Driver} interface in the next major release.
2022-02-02T18:39:03+00:00 [info] User Deprecated: Class "Sentry\SentryBundle\Tracing\Doctrine\DBAL\TracingServerInfoAwareDriverConnection" should implement method "Doctrine\DBAL\Driver\Connection::getNativeConnection(): resource|object".

hi ~ I also encounter the deprecation messages on the console. What I found out was that when I enabled Sentry as a logger DebugHandlersListener of SF was called after Sentry ErrorHandler was initialized. Therefore the following code
$handler = set_exception_handler('var_dump');
$this->earlyHandler = \is_array($handler) ? $handler[0] : null;
restore_exception_handler();

sees the Sentry ErrorHandler instead of the Symfony ErrorHandler, what then results in the Logger not properly being setup for the ErrorHandler (which is normally done in DebugHandlersListener ::configure), which then results in the default BufferingLogger to be used for the deprecation message which are outputted at the end.
As a fix for this I used Sentry logger using the old behaviour using monolog.type=service instead of sentry and the lazy loaded that services. This way DebugHandlersListener __constructor is caller before Sentry changes the error_handler.
monolog:
  handlers:
    sentry:
      type: service
      id: App\Sentry\MonologHandler

see: https://symfony.com/doc/current/service_container/lazy_services.html
  App\Sentry\MonologHandler:
    lazy: true
    public: true
    arguments:
      $hub: '@Sentry\State\HubInterface'
      $level: !php/const Monolog\Logger::ERROR

I hope this helps

Thanks @wimwinterberg but unfortunately this is a known issue; see #337.

I'm having the same issue @Tofandel is having, also on symfony 5.4.2 / php8.1

The deprecation warnings make it almost impossible to see real errors.
Odd, since this is Sentry's entire reason for being.
No idea how to solve it, alas, so I'm just part of the chorus hoping it
happens.
On Wed, Mar 16, 2022 at 8:07 PM github-actions[bot] <
@.***> wrote:

This issue has gone three weeks without activity. In another week, I will
close it.
But! If you comment or otherwise update it, I will reset the clock, and if
you label it Status: Backlog or Status: In Progress, I will leave it
alone ... forever!
"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀
—
Reply to this email directly, view it on GitHub
https://github.com/getsentry/sentry-symfony/issues/483#issuecomment-1069761826,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEXIQP4JIO2U2NEWIMO3ODVAJZUPANCNFSM43FXRKGA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

The deprecation warnings make it almost impossible to see real errors.

I don't think that this is a fair statement. Just one deprecation remains, which is the one related to the DBAL, and it would have been fixed already if it was so easy to do it. The reality is a bit different unfortunately: that class is deprecated, but we have to implement it because otherwise our decorator would break the applications that expect the connection to be an instance of ExceptionConverterDriver

To be fair, I think that Symfony makes it too hard to hide
deprecation errors.   And monolog is very confusing to someone who just
wants to capture errors.
  It's an oft-discussed issue.
On Wed, Mar 16, 2022 at 8:39 PM Stefano Arlandini @.***>
wrote:

The deprecation warnings make it almost impossible to see real errors.
I don't think that this is a fair statement. Just one deprecation remains,
which is the one related to the DBAL, and it would have been fixed already
if it was so easy to do it. The reality is a bit different unfortunately:
that class is deprecated, but we have to implement it because otherwise our
decorator would break the applications that expect the connection to be an
instance of ExceptionConverterDriver
—
Reply to this email directly, view it on GitHub
https://github.com/getsentry/sentry-symfony/issues/483#issuecomment-1069780814,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEXIQILZ5ECNZ3VUOTOA63VAJ5NJANCNFSM43FXRKGA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

For me, it's not just the deprecations (from #596) but my app effectively and suddenly (with Sentry v3.4?) stopped working.

Please open a separate issue and post more details. An image of an error message is not enough to understand what's happening

Hey!
Facing same issue with deprecation error. Muting it in phpunit config does not work, using SYMFONY_DEPRECATIONS_HELPER=weak works fine, but that would result with any other deprecation slipping in our codebase and that's not wanted.
Can we fix this error? Some check on what version is used and determining correct class?
php -c [./php/conf.d/php.ini](https://bitbucket.org/usertech/fllite-be/src/02000d2c15d4d34752e214ed372108c260809179/php/conf.d/php.ini) vendor/bin/phpunit --configuration [./phpunit.xml](https://bitbucket.org/usertech/fllite-be/src/02000d2c15d4d34752e214ed372108c260809179/phpunit.xml) --testsuite unit
PHPUnit 9.5.20 #StandWithUkraine
Testing
..............................                                    30 / 30 (100%)
Time: 00:00.032, Memory: 14.07 MB
OK (30 tests, 66 assertions)
Remaining indirect deprecation notices (2)
  2x: The "Sentry\SentryBundle\Tracing\Doctrine\DBAL\TracingDriverForV3" class implements "Doctrine\DBAL\VersionAwarePlatformDriver" that is deprecated All drivers will have to be aware of the server version in the next major release.
    2x in AirportCodeNormalizerTest::testNormalizeCustom from App\Tests\unit\Application\Airport
make: *** [test-unit] Error 1

Running following versions:
"doctrine/annotations": "^1.0",
"doctrine/doctrine-bundle": "^2.5",
"doctrine/doctrine-fixtures-bundle": "^3.4",
"doctrine/doctrine-migrations-bundle": "^3.2",
"doctrine/orm": "^2.11"

"sentry/sentry-symfony": "^4.2",

... symfony packages 5.4.* ...

I would love to, but I don't think it's feasible without the proof that the majority of people upgraded from DBAL 2.x. When we're talking about the userbase to support, the Sentry team is unwilling to leave a sizable chunk of users behind in most if not all of the cases, no matter the reason. @cleptric is now to the go-to person for this kind of decisions through

Looking at https://packagist.org/packages/doctrine/dbal/stats#major/all, I do see a 50/50 split between v2 and v3. So I don't see us of removing dbal v2 support anytime soon.


EWF issuer has the tag Ed25519Signature2020 but is issuing a VC with proof type "Ed25519Signature2018"

https://github.com/w3c-ccg/vc-api-test-suite-implementations/blob/main/implementations/EWF.json#L4-L7

Closing, The issue has been moved to the w3c test suite implementations repo.


modified arrays.md  file and added a new file rev_array

In rev_array, I have written code to reverse elements by two ways

Hi, Please read the Important Announcement.
PR can only be made after the issue is assigned to you.


Needed to add /lib/security/libpam_rssh.so

This project works great, except that I had the error
PAM unable to dlopen(libpam_rssh.so): /lib/security/libpam_rssh.so: cannot open shared object file: No such file or directory

I was able to fix this by copying libpam_rssh.so to /lib/security/limpam_rssh.so.
I didn't find a mention of that in the README, so I am opening an issue.
If you need me to do some more tests, I am happy to do that.

The location of pam libraries depends on Linux distrubutions. On Debian for example, they are in the /lib/x86_64-linux-gnu/security/. So in the README, I use absolute path for sample configuration file.

That makes sense. Maybe a mention in the README would be good. Is it fine if I open a PR

Additional information in document would be nice. PR is always welcomed.


Update sites.json - Added bet365

Added instructions for bet365

Hello @alavaros ,
This repo is not being maintained anymore, but we've kept it alive and updated on a detached fork. If still applicable, would you kindly submit your PR there and close this one here? :)

Hello @alavaros ,
This repo is not being maintained anymore, but we've kept it alive and updated on a detached fork. If still applicable, would you kindly submit your PR there and close this one here? :)

In fact, I think I already have. Update sites.json - Added bet365


can we use mithril as js lib instaed of jq

http://lhorie.github.io/mithril/
Mithril is a client-side MVC framework - a tool to organize code in a way that is easy to think about and to maintain.
Light-weight
Only 5kb gzipped, no dependencies
Small API, small learning curve
Robust
Safe-by-default templates
Hierarchical MVC via components
Fast
Virtual DOM diffing and compilable templates
Intelligent auto-redrawing system

bennifit are:
light-weight fit for mobile
fastest than jq
ui compenents

This is an MVC framework, I don't see how it is meant as a replacement for JQuery. In any case we have no plans to switch.


Fix Email Issues

The email has a bug: SMTP Server Requires a secure connection.
Fix that.

Closed with a commit referencing it


RSA key generation exponent

CreatePrimary/Create parameter
RSA key generation length=2048
Key Generation will fail
(rc=0x8d, value was out of allowed range)
if I set inPublic.t.publicArea.parameters.rsa.exponent other than 0.
Any information?

Do you have example code you're working from that we can use as reference. I've been ramping up on the serialization / marshaling logic and policy session mechanisms. I haven't got familiar with the key creation logic yet but this may be as good a time as any to do so. Still, getting some example code to help repo your issue will speed things up significantly.

Got no response to ask for more information, closing issue. If you want to fill in the details feel free to open this one back up.


[BUG] Inconsistent device search results after compute reboot or long time idle.

Hi Luxonis: I recently got some inconsistent results when bringing up multiple (4) usb oak-d (1st gen) camera devices in parallel (using ros nodelets) after rebooting the compute or leave cameras in idle state for a while.
The inconsistency happens in the device search stage: sometimes all my camera devices can be found successfully by providing mxids and the returned deviceInfo for each device is correct (as shown in Fig 1),

while some times one or more devices couldn't be found or the device info it contains belongs to some other devices (as shown in Fig 2).

After having some discussions with EriK, he provided these suggestions to help me address the stability issue:

XLink protocol isn't very thread safe, and you shouldn't connect to multiple cameras at the same time, but should wait eg. 500ms between connections
after connection is closed, cameras need a few seconds to be discoverable again. USB OAKs about 3sec, while POE OAKs about 10sec

And I changed my camera driver to follow these ideas:

Sequentially launch the driver nodelet per camera.
Add delays before restarting camera driver nodelets.

With these changes, my driver node becomes more stable now. However, I still can get this bring up stability issue and I found this problem is very easy to occur under the scenario described below:

Reboot the compute
Query connected camera devices using an script like this: https://github.com/luxonis/depthai-core/blob/main/examples/host_side/device_information.cpp

And if I found any warning messages in the console print, the bringup issue will happen:

If I don't launch the camera driver node but run the query script again right after the first one, I will see less devices threw warning messages:

And if I run the query script the 3rd time, every device will be in normal state:

After this health check, I can always launch my multiple camera driver nodes successfully.

@developer-mayuan
We are yet to add some helper functions on this note, but in a nutshell, a device transitions between states when starting & stopping. In this state, a device isn't connectable & should be waited upon more, till its in a good state again.

Thanks for the quick reply! I'm wondering if there's currently a more official way to check if an OAK camera is in a good state before using it (besides querying devices like what I have done)? And I'm also curious why the camera is often if not always not in a good state after reboot the compute?

I'm wondering if there's currently a more official way to check if an OAK camera is in a good state before using it

At the moment devices have to be queried (which you can also specify to not skip invalid devices, but filter those out yourself)

And I'm also curious why the camera is often if not always not in a good state after reboot the compute?

This is a thing we haven't explored much yet, but heard it a couple of times. I don't have any good answers on this topic at the moment unfortunatelly:/


Specify carthage directory path

If the Xcodeproj isn't in the root directory (as well as the carthage directory), the generated framework search path will be invalid. I didn't find a way to set a custom carthage path from the docs, would be a great option!

In the end, I'm using search_paths directly like this:
carthage_path = "${SRCROOT}/../Carthage/Build"
platforms = [
    macos("10.11", search_paths = "#{carthage_path}/Mac/"),
    ios("9.0", search_paths = "#{carthage_path}/iOS/"),
    tvos("9.0"),
    watchos("2.0")
]

It's working as expected, so closing this, my bad to miss that feature!

No problem. Do you think the documentation is lacking in this section?

Personal my, I miss it just because I didn't the usage in ruby, so it was more due to my missing knowledge than the documentation itself.
It may be harder to get everything for new ruby users, but I don't think it's an issue


Added sliding evaluation for pspnet

works best for cityscapes, there may remain some tiling bugs for the other two.
Increases the amount of detail in segmentation tremendously.

Wow! The resolution is really good. Too bad you lose the context for many of the tiles in ADE.

Yeah, even if we increase the overlap the context is not enough in some areas.

Maybe with multi-scale evaluation.

Should I merge this pull request and we can deal with the tiling context issue later?

Yeah, I'm pretty sure this is as good as it gets without multi-scaled evaluation. The coverage of the tiles is not really regular but it's pretty much how the original paper evaluates them and probably trained them too. If someone has a pipeline for validating VOC and ADE20k that would be nice.

Multi-scale doesn't help much for ADE20K with the default scales.  When evaluating at lower scales only the results seem to better as the network has a larger field of view.


ingress: add support for networking.k8s.io/v1

Add support for networking.k8s.io/v1 for ingress. v1beta1 API is deprecated and has been removed in kube 1.22. This change is backward compatible but if the kubernetes version is at least 1.19 the new API will be used and thus this can break installations. That's why I bumped the version to 2.0.0

Is there a way with the current CI to have different values files depending of the kubernetes version tested ?


why does it say a manga is missing chapters when theyre not

Steps to reproduce
when I went to add jjk to my library I noticed it said by one it's missing 100 chapters and by the other 1771 chapters? why is that
Expected behavior
expecting this to be fixed ngl
Actual behavior
it should js add the chapters of if it's wrong not show up
Crash logs
No response
Mihon version
0.16.0
Android version
android 14
Device
Samsung galaxy s23
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an official extension, I should be opening an issue in the extensions repository.
[X] I have gone through the FAQ and troubleshooting guide.
[X] I have updated the app to version 0.16.0.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

Any chapters not visible in your current filter setting (like showing only unread chapters) will trigger this message and say that amount of chapters is missing.
There are some edge cases where the system gets tricked by a chapter being named something like "Extra - 2023 Christmas Illustration" and then believe the entry has 2023 chapters total.
While source support is out of scope for Mihon, if wherever you're getting JJK from doesn't have all chapters in the first place, those would obviously also show as missing. Some will also inevitably be incomplete for various reasons.

all 4 of my extentions have the same amount of chapters and they're the latest it js gives that message

Have you filtered the list in any way? Like set it to unread only or similar?

nope not that I know of

Could you provide a screenshot of the chapter list with the warning visible? Is there a warning between two chapters saying it's missing chapters between them?

Okay, for the one with over 1k missing, can you scroll through the list to see if you can find anywhere there is a warning between two chapters in the list? Would look something like this

lol wth

Ah effectively what I figured. That Jump Festa special probably has the year number in its title doesn't it 😅
That'll have caused the massive discrepancy.
As for the other one, I believe it's the name not having a number at all that's confusing the system.
Pretty sure this is on the numbering recognition system, so we'll see if someone can fix that/make it less gullible.

ah okay and one other question
is it normal the extentions need to ve "trusted" first before being used or am I js bein dumb

Yes that's normal as they're not code Mihon can express any guarantees for as its not provided by Mihon. To make users realise they're taking a risk, this trusting mechanic exists.

ah so there's no danger?

they're js the old tachi extentions  like repod
u want the link? or is that gonna get me banned

Don't post any links, but it's hard to say whether extensions can be trusted or not, and this is probably not the place to do it. Now that extensions have gone unofficial, the people providing you extensions can make any changes they wish to them, and it is your own responsibility to ensure that they only do what they say they do.

any way to check the extentions are safe? before they gobble my shi up

As far as I understand, extension have to be open source by design, so you can always read through the code to make sure, but that's the same mindset you should have with everything you download off of the internet.

can I say the of the place i got them from? like no links js the name

I don't know but I wouldn't take any chances. The closer Mihon gets affiliated with extensions, the more likely it is to suffer the same fate as Tachi. Extensions are your own responsibility, if anything you should be talking to the people that gave them to you.

No, it's your personal responsibility and Mihon doesn't provide help with 3rd party extensions

it was on github I js seached how the extention shi worked and I js put it in


loads/common directory structure doesn't work with cds-dk 2.0.7 for csv files

I talk about this yt video https://www.youtube.com/watch?v=EJrKRQyULsw (got no account to comment directly below...)
I try to copy your structur for csv files, db/loads/common,
but notice that my table keep empty.
in next stept i checked the cds build output:
[cds] - determining build tasks for project [/home/user/projects/cap].
   {
     "build": {
       "target": ".",
       "tasks": [
         {"for":"hana", "src":"db", "options":{"model":["db","srv"]}},
         {"for":"node-cf", "src":"srv", "options":{"model":["db","srv"]}}
       ]
     }
   }

[cds] - building project [/home/user/projects/cap], clean [true]
[cds] - cds [4.1.5], compiler [1.35.0], home [/home/user/.node_modules_global/lib/node_modules/@sap/cds-dk/node_modules/@sap/cds]

[cds] - done > wrote output to:
  db/src/gen/.hdiconfig
  db/src/gen/.hdinamespace
  db/src/gen/Base.hdbtable
  db/src/gen/iso_countries_regions.hdbview
  db/src/gen/iso_us_states.hdbview
  db/src/gen/iso_us_states_and_territories.hdbview
  db/src/gen/localized.iso_countries_regions.hdbview
  db/src/gen/localized.sap.common.Countries.hdbview
  db/src/gen/localized.sap.common.Currencies.hdbview
  db/src/gen/localized.sap.common_countries.Regions.hdbview
  db/src/gen/sap.common.Countries.hdbtable
  db/src/gen/sap.common.Countries_texts.hdbtable
  db/src/gen/sap.common.Currencies.hdbtable
  db/src/gen/sap.common.Currencies_texts.hdbtable
  db/src/gen/sap.common_countries.Regions.hdbtable
  srv/gen/_i18n/i18n.json
  srv/gen/csn.json

[cds] - build completed in: 612.308ms

no csv files mention,
than i move one csv file to the loads directory, no change.
renamed loads to csv  with the result:
[cds] - determining build tasks for project [/home/user/projects/cap].
   {
     "build": {
       "target": ".",
       "tasks": [
         {"for":"hana", "src":"db", "options":{"model":["db","srv"]}},
         {"for":"node-cf", "src":"srv", "options":{"model":["db","srv"]}}
       ]
     }
   }

[cds] - building project [/home/user/projects/cap], clean [true]
[cds] - cds [4.1.5], compiler [1.35.0], home [/home/user/.node_modules_global/lib/node_modules/@sap/cds-dk/node_modules/@sap/cds]

[cds] - done > wrote output to:
  db/src/gen/.hdiconfig
  db/src/gen/.hdinamespace
  db/src/gen/Base.hdbtable
  db/src/gen/csv/sap.common-Currencies.csv
  db/src/gen/csv/sap.common-Currencies.hdbtabledata
  db/src/gen/iso_countries_regions.hdbview
  db/src/gen/iso_us_states.hdbview
  db/src/gen/iso_us_states_and_territories.hdbview
  db/src/gen/localized.iso_countries_regions.hdbview
  db/src/gen/localized.sap.common.Countries.hdbview
  db/src/gen/localized.sap.common.Currencies.hdbview
  db/src/gen/localized.sap.common_countries.Regions.hdbview
  db/src/gen/sap.common.Countries.hdbtable
  db/src/gen/sap.common.Countries_texts.hdbtable
  db/src/gen/sap.common.Currencies.hdbtable
  db/src/gen/sap.common.Currencies_texts.hdbtable
  db/src/gen/sap.common_countries.Regions.hdbtable
  srv/gen/_i18n/i18n.json
  srv/gen/csn.json

[cds] - build completed in: 591.683ms

so the "root" csv file got picked up, but the others ones how are in db/csv/common not,
in the manuel https://cap.cloud.sap/docs/ i didn't found any hints in the change log if this behavior got changed and
see no config parameter to enforce this behavior.
or the source of the issue is me, for this case i attached my project file:
cap.zip

Yes this was a change in the recent release of CAP CDS (which happened after the video was recorded).  However I've already change the project here in the code sample to remove the sub-folders from the csv folder 9 days ago. https://github.com/SAP-samples/hana-opensap-cloud-2020/commit/ab37b310f1b9ce4fe322c6b363b21ea1d7f526df
https://github.com/SAP-samples/hana-opensap-cloud-2020/tree/master/db/csv


Kubenab loses container when handling multi-container pod

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT

Version of Helm and Kubernetes:
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.2", GitCommit:"f6278300bebbb750328ac16ee6dd3aa7d3549568", GitTreeState:"clean", BuildDate:"2019-08-05T09:23:26Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.2", GitCommit:"f6278300bebbb750328ac16ee6dd3aa7d3549568", GitTreeState:"clean", BuildDate:"2019-08-05T09:15:22Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}

What happened:
When  use kubenab to deploy a multi-container pod, the front container will disappear.
What you expected to happen:
Kubenab can properly handle multi-container pods.
How to reproduce it (as minimally and precisely as possible):

deploy kubenab
write a deployment yaml file containing multiple containers, eg:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: dp-busybox
  namespace: allkinds
spec:
  replicas: 1
  selector:
    matchLabels:
      app: allkinds-dp
  template:
    metadata:
      labels:
        app: allkinds-dp
    spec:
      containers:
      - image: busybox
        name: busybox-011111111111111
        imagePullPolicy: Always
        command:
          - "/bin/sh"
        args:
          - "-c"
          - "mkdir -p /mnt && touch /mnt/SUCCESS && sleep 36000 || exit 1"
      - image: busybox
        name: busybox-0222222222222
        imagePullPolicy: Always
        command:
          - "/bin/sh"
        args:
          - "-c"
          - "mkdir -p /mnt && touch /mnt/SUCCESS && sleep 36000 || exit 1"

kubectl create -f xxx.yaml
kubectl get pod --all-namespaces

[root@node1]# kubectl get pod --all-namespaces
NAMESPACE     NAME                                      READY   STATUS    RESTARTS   AGE
allkinds      dp-busybox-6c777bfbd5-6q879               1/1     Running   0          36m

get kubenab logs:

2019/10/09 21:50:43 Serving request: /mutate
2019/10/09 21:50:43 {"kind":"AdmissionReview","apiVersion":"admission.k8s.io/v1beta1","request":{"uid":"5c2cd2c8-4705-4d81-95b6-a33bbae27fcb","kind":{"group":"","ver  sion":"v1","kind":"Pod"},"resource":{"group":"","version":"v1","resource":"pods"},"requestKind":{"group":"","version":"v1","kind":"Pod"},"requestResource":{"group":"  ","version":"v1","resource":"pods"},"namespace":"allkinds","operation":"CREATE","userInfo":{"username":"system:serviceaccount:kube-system:replicaset-controller","uid  ":"d38e0c38-6662-4dc2-8533-fdfdb6e751b7","groups":["system:serviceaccounts","system:serviceaccounts:kube-system","system:authenticated"]},"object":{"kind":"Pod","api  Version":"v1","metadata":{"generateName":"dp-busybox-6c777bfbd5-","creationTimestamp":null,"labels":{"app":"allkinds-dp","pod-template-hash":"6c777bfbd5"},"ownerRefe  rences":[{"apiVersion":"apps/v1","kind":"ReplicaSet","name":"dp-busybox-6c777bfbd5","uid":"53c58e1f-b658-484d-a85c-0efbad21296d","controller":true,"blockOwnerDeletio  n":true}]},"spec":{"volumes":[{"name":"default-token-hvfcx","secret":{"secretName":"default-token-hvfcx"}}],"containers":[{"name":"busybox-011111111111111","image":"  busybox:latest","command":["/bin/sh"],"args":["-c","mkdir -p /mnt \u0026\u0026 touch /mnt/SUCCESS \u0026\u0026 sleep 36000 || exit 1"],"resources":{},"volum  eMounts":[{"name":"default-token-hvfcx","readOnly":true,"mountPath":"/var/run/secrets/kubernetes.io/serviceaccount"}],"terminationMessagePath":"/dev/termination-log"  ,"terminationMessagePolicy":"File","imagePullPolicy":"Always"},{"name":"busybox-0222222222222","image":"busybox:latest","command":["/bin/sh"],"args":["-c","  mkdir -p /mnt \u0026\u0026 touch /mnt/SUCCESS \u0026\u0026 sleep 36000 || exit 1"],"resources":{},"volumeMounts":[{"name":"default-token-hvfcx","readOnly":true,"moun  tPath":"/var/run/secrets/kubernetes.io/serviceaccount"}],"terminationMessagePath":"/dev/termination-log","terminationMessagePolicy":"File","imagePullPolicy":"Always"  }],"restartPolicy":"Always","terminationGracePeriodSeconds":30,"dnsPolicy":"ClusterFirst","serviceAccountName":"default","service  Account":"default","securityContext":{},"schedulerName":"default-scheduler","tolerations":[{"key":"node.kubernetes.io/not-ready","operator":"Exists","effect":"NoExec  ute","tolerationSeconds":300},{"key":"node.kubernetes.io/unreachable","operator":"Exists","effect":"NoExecute","tolerationSeconds":300}],"priority":0,"enableServiceL  inks":true},"status":{}},"oldObject":null,"dryRun":false,"options":{"kind":"CreateOptions","apiVersion":"meta.k8s.io/v1"}}}

2019/10/09 21:50:43 AdmissionReview Namespace is: allkinds
2019/10/09 21:50:43 Container Image is busybox:latest
2019/10/09 21:50:43 Image is not being pulled from Private Registry: busybox:latest
2019/10/09 21:50:43 Changing image registry to: <IP_ADDRESS>:8088/busybox:latest
2019/10/09 21:50:43 Container Image is busybox:latest
2019/10/09 21:50:43 Image is not being pulled from Private Registry: busybox:latest
2019/10/09 21:50:43 Changing image registry to: <IP_ADDRESS>:8088/busybox:latest
2019/10/09 21:50:43 Serving request: /validate
2019/10/09 21:50:43 {"kind":"AdmissionReview","apiVersion":"admission.k8s.io/v1beta1","request":{"uid":"91d9b321-1e9c-449d-9298-25f2715c9924","kind":{"group":"","ver  sion":"v1","kind":"Pod"},"resource":{"group":"","version":"v1","resource":"pods"},"requestKind":{"group":"","version":"v1","kind":"Pod"},"requestResource":{"group":"  ","version":"v1","resource":"pods"},"namespace":"allkinds","operation":"CREATE","userInfo":{"username":"system:serviceaccount:kube-system:replicaset-controller","uid  ":"d38e0c38-6662-4dc2-8533-fdfdb6e751b7","groups":["system:serviceaccounts","system:serviceaccounts:kube-system","system:authenticated"]},"object":{"kind":"Pod","api  Version":"v1","metadata":{"name":"dp-busybox-6c777bfbd5-6q879","generateName":"dp-busybox-6c777bfbd5-","namespace":"allkinds","uid":"bf3ce444-2a0b-49bd-8446-050db630  c77e","creationTimestamp":"2019-10-09T21:50:43Z","labels":{"app":"allkinds-dp","pod-template-hash":"6c777bfbd5"},"ownerReferences":[{"apiVersion":"apps/v1","kind":"R  eplicaSet","name":"dp-busybox-6c777bfbd5","uid":"53c58e1f-b658-484d-a85c-0efbad21296d","controller":true,"blockOwnerDeletion":true}]},"spec":{"volumes":[{"name":"def  ault-token-hvfcx","secret":{"secretName":"default-token-hvfcx","defaultMode":420}}],"containers":[{"name":"busybox-0222222222222","image":"<IP_ADDRESS>:8088/busybox:latest","command":["/bin/sh"],"args":["-c","mkdir -p /mnt \u0026\u0026 touch /mnt/SUCCESS \u0026\u0026 sleep 36000 || exit 1"],"resources":{},"volumeMounts":  [{"name":"default-token-hvfcx","readOnly":true,"mountPath":"/var/run/secrets/kubernetes.io/serviceaccount"}],"terminationMessagePath":"/dev/termination-log","termina  tionMessagePolicy":"File","imagePullPolicy":"Always"}],"restartPolicy":"Always","terminationGracePeriodSeconds":30,"dnsPolicy":"ClusterFirst","serviceAccountName":"default","serviceAccount":"default","securityContext":{},"imagePullSecrets":[{"name":"regsecret"}],"schedulerName":"default-schedu  ler","tolerations":[{"key":"node.kubernetes.io/not-ready","operator":"Exists","effect":"NoExecute","tolerationSeconds":300},{"key":"node.kubernetes.io/unreachable","  operator":"Exists","effect":"NoExecute","tolerationSeconds":300}],"priority":0,"enableServiceLinks":true},"status":{"phase":"Pending","qosClass":"BestEffort"}},"oldO  bject":null,"dryRun":false,"options":{"kind":"CreateOptions","apiVersion":"meta.k8s.io/v1"}}}

2019/10/09 21:50:43 AdmissionReview Namespace is: allkinds
2019/10/09 21:50:43 Container Image is <IP_ADDRESS>:8088/busybox:latest
2019/10/09 21:50:43 Image is being pulled from Private Registry: <IP_ADDRESS>:8088/busybox:latest

Anything else we need to know:

I could re-produce the Bug.
I will start fixing it today.
@rimusz can you please assign me to this Issue and add the bug label?

@lyyao09 Which kubenab-version do you use?

@lyyao09 Which kubenab-version do you use? And can you please provide the Output of kubectl desribe pod <POD>

kubenab vesion: 0.3.2（I am a bit confused about image name in https://github.com/jfrog/kubenab/blob/master/deployment/kubenab-deployment.yaml
[root@node2 home]# kubectl describe pod -n kube-system kubenab-deployment-5b8d8f85dd-57gp6
Name:                 kubenab-deployment-5b8d8f85dd-57gp6
Namespace:            kube-system
Priority:<PHONE_NUMBER>
Priority Class Name:  system-cluster-critical
Node:                 node2/<IP_ADDRESS>
Start Time:           Fri, 11 Oct 2019 06:07:47 +0800
Labels:               app=kubenab
                      pod-template-hash=5b8d8f85dd
Annotations:          <none>
Status:               Running
IP:                   <IP_ADDRESS>
Controlled By:        ReplicaSet/kubenab-deployment-5b8d8f85dd
Containers:
  kubenab:
    Container ID:   docker://9b404291fd3e1562e379238b7d01f1a0b184ef3d8d07f55f537b9e22d4a36a5f
    Image:          kubenab:0.3.2
    Image ID:       docker://sha256:d46a28aa4cfb05dde0086cb789113d3dcd738ca2ef8c371831eb12bac6c77d4d
    Port:           443/TCP
    Host Port:      0/TCP
    State:          Running
      Started:      Fri, 11 Oct 2019 06:07:54 +0800
    Ready:          True
    Restart Count:  0
    Environment:
      DOCKER_REGISTRY_URL:   <IP_ADDRESS>:8088
      REGISTRY_SECRET_NAME:  regsecret
      WHITELIST_NAMESPACES:  kube-system,default
      WHITELIST_REGISTRIES:  <IP_ADDRESS>:8088
      REPLACE_REGISTRY_URL:  false
    Mounts:
      /etc/admission-controller/tls from tls (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-495xx (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True
Volumes:
  tls:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  kubenab-certs
    Optional:    false
  default-token-495xx:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-495xx
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  role=master
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:          <none>

@lyyao09 thanks but I meant the describe Output of your busybox pod

@lyyao09 docker image tag is kubenab version :)
chart has a separate versioning

@lyyao09 thanks but I meant the describe Output of your busybox pod

ok, updated.

I could re-produce the Bug.
It seems like that kubenab removes all the previous Containers and only returns the latest.

kubenab does return a correct patch:
[
  {
    "op": "add",
    "path": "/spec/containers",
    "value": [
      {
        "name": "busybox-1",
        "image": "docker.artifact.fab/busybox:1.29.3",
        "command": [
          "/bin/sh"
        ],
        "args": [
          "-c",
          "mkdir -p /mnt && touch /mnt/SUCCESS && sleep 36000 || exit 1"
        ],
        "resources": {},
        "volumeMounts": [
          {
            "name": "default-token-2s9hf",
            "readOnly": true,
            "mountPath": "/var/run/secrets/kubernetes.io/serviceaccount"
          }
        ],
        "terminationMessagePath": "/dev/termination-log",
        "terminationMessagePolicy": "File",
        "imagePullPolicy": "Always"
      }
    ]
  },
  {
    "op": "add",
    "path": "/spec/containers",
    "value": [
      {
        "name": "busybox-2",
        "image": "docker.artifact.fab/busybox:latest",
        "command": [
          "/bin/sh"
        ],
        "args": [
          "-c",
          "mkdir -p /mnt && touch /mnt/SUCCESS && sleep 36000 || exit 1"
        ],
        "resources": {},
        "volumeMounts": [
          {
            "name": "default-token-2s9hf",
            "readOnly": true,
            "mountPath": "/var/run/secrets/kubernetes.io/serviceaccount"
          }
        ],
        "terminationMessagePath": "/dev/termination-log",
        "terminationMessagePolicy": "File",
        "imagePullPolicy": "Always"
      }
    ]
  },
  {
    "op": "add",
    "path": "/spec/imagePullSecrets",
    "value": [
      {}
    ]
  }
]

Fixed

Fixed

yes, I tested this issue has been solved.


Add U2F dependency

https://github.com/Yubico/libu2f-host#building
Notes:

The binary can be built for macOS without the macosx.mk file.
Even when building from a release tarball, gengetopt and help2man are required.

@UserNotFound @robertfairhead before I go much further, am I handling/adding dependencies correctly? I've not used omnibus before and have to add quite a few dependencies to get U2F to work.

I'm not sure, I have zero experience here. This might be a good chance to do something like a lunch-and-learn if we need to build up some internal knowledge to make an effective review here.

I've never used omnibus-toolbelt before either, so I don't have enough experience to say offhand.

I'm investigating including libu2f-host as a non-embedded dependency. It looks like this might be possible on debian with a source package control file.

Should be able to use homebrew-cask's depends_on formula: to include the dependency for libu2f-host to our aptible cask. https://github.com/Homebrew/homebrew-cask/blob/master/doc/cask_language_reference/stanzas/depends_on.md#depends_on-formula
Unsure if we can include the dependency directly in our .pkg.

Adding dependencies to a RH/CentOS package: http://ftp.rpm.org/api/<IP_ADDRESS>/dependencies.html

It's unfortunate that it took this long to find that omnibus does support runtime_dependencies but this does what my script did for the .deb and .rpm packages. Now I just need to figure out how to only add the dependency to supported OS versions. We also need to determine how we want to handle adding the dependency to Debian packages.
Debian: u2f-host is not available until 9+ (stretch) but we only build packages for 7 and 8. I was able to install the debian-8 package on 9 without trouble and it can still be installed on 7 or 8 it will just say it has unsatisfied dependencies.
Ubuntu: Available 16.04+ (xenial)
CentOS: Available in 7 but not 8

Found the gem responsible for the platform checks we use (e.g. ubuntu?): chef/sugar

I decided to leave the dependency off the Debian packages for now so we don't get a bunch of support requests about the unmet dependency. We should probably add support for newer versions and it will be added to those.


znap pull - unknown option `quiet'

I just did znap pull this morning and got the following error message:
error: unknown option `quiet'
usage: git maintenance start [--scheduler=<scheduler>]

    --scheduler <scheduler>
                          scheduler to trigger git maintenance run

I'm using git version 2.34.0

Are you on WSL?

Are you on WSL?

No I'm on macOS.

Looks like starting with Git 2.34.0, git maintenance no longer knows any other option than --scheduler.


Return the time from a percentile call on an integer

percentile() is supposed to be a selector and return the time of the
point, but that only got changed when the input was a float. Updating
the integer processor to also return the time of the point rather than
the beginning of the interval.
Fixes #7634.

Can you add a test for this?

Added a test for this.


Parameter "callback" needs to be of type "function" but type "undefined" has been passed

Describe the bug
The log shows:
error: tado.0 (404940) Error in data refresh at step DoDevices: Error: Parameter "callback" needs to be of type "function" but type "undefined" has been passed

Versions:

Adapter version: 0.4.6-alpha.1
JS-Controller version: 5.0.1-alpha.0-20230330-e0b409fe
Node version: v19.8.1
Operating system: Debian 12 'Bookworm'

Additional context
I'm totally aware that these versions are bleeding edge. Just pointing out upcoming situations.

Thanks for raising!
Will investigate after eastern

I tried a quick fix (best guess) without installing js-controller v5
Would be cool if you can check this fix:
DrozmotiX/ioBroker.tado#247a30d1dfef57dfb0c1cc7636b6cd7d6fd51ef3

Having installed this version the log still shows these messages, roughly every 30 minutes.

ok, thanks, then I have to install the version on my own.
What is the best way to install it in that early stag? Is there a how to available?

Very easy. Just follow the instructions in this Thread:
https://forum.iobroker.net/topic/64273/alpha-test-js-controller-5-0

Not every 30 minutes but every 60 minutes (Polling is set to 60 seconds):
2023-03-31 09:41:26.508  - info: host.chet instance system.adapter.tado.0 started with pid 461834
2023-03-31 09:41:29.782  - info: tado.0 (461834) starting. Version 0.4.6-alpha.1 (non-npm: DrozmotiX/ioBroker.tado#575913f32f7e1e9120e7640dfdb4279becab7322) in /opt/iobroker/node_modules/iobroker.tado, node: v19.8.1, js-controller: 5.0.1-alpha.0-20230330-e0b409fe
2023-03-31 09:41:29.827  - info: tado.0 (461834) Started with JSON-Explorer version 0.1.11-alpha.1
2023-03-31 09:41:30.853  - info: tado.0 (461834) Connected to Tado cloud, initialyzing...
2023-03-31 09:41:31.346  - error: tado.0 (461834) Error in data refresh at step DoDevices: Error: Parameter "callback" needs to be of type "function" but type "undefined" has been passed
2023-03-31 09:41:31.675  - error: tado.0 (461834) Disconnected from Tado cloud service ..., retry in 30 seconds !
2023-03-31 09:42:02.662  - info: tado.0 (461834) Connected to Tado cloud, initialyzing...
2023-03-31 09:42:07.900  - info: tado.0 (461834) Initialisation finished, connected to Tado cloud service refreshing every 60 seconds
2023-03-31 10:41:32.330  - error: tado.0 (461834) Error in data refresh at step DoDevices: Error: Parameter "callback" needs to be of type "function" but type "undefined" has been passed
2023-03-31 10:41:32.350  - error: tado.0 (461834) Disconnected from Tado cloud service ..., retry in 30 seconds !
2023-03-31 10:42:03.999  - info: tado.0 (461834) Connected to Tado cloud, initialyzing...
2023-03-31 10:42:08.045  - info: tado.0 (461834) Initialisation finished, connected to Tado cloud service refreshing every 60 seconds
2023-03-31 11:41:33.205  - error: tado.0 (461834) Error in data refresh at step DoDevices: Error: Parameter "callback" needs to be of type "function" but type "undefined" has been passed
2023-03-31 11:41:33.225  - error: tado.0 (461834) Disconnected from Tado cloud service ..., retry in 30 seconds !
2023-03-31 11:42:04.072  - info: tado.0 (461834) Connected to Tado cloud, initialyzing...
2023-03-31 11:42:08.115  - info: tado.0 (461834) Initialisation finished, connected to Tado cloud service refreshing every 60 seconds
2023-03-31 12:42:36.991  - error: tado.0 (461834) Error in data refresh at step DoDevices: Error: Parameter "callback" needs to be of type "function" but type "undefined" has been passed
2023-03-31 12:42:37.040  - error: tado.0 (461834) Disconnected from Tado cloud service ..., retry in 30 seconds !
2023-03-31 12:43:07.984  - info: tado.0 (461834) Connected to Tado cloud, initialyzing...
2023-03-31 12:43:12.111  - info: tado.0 (461834) Initialisation finished, connected to Tado cloud service refreshing every 60 seconds
2023-03-31 13:42:37.361  - error: tado.0 (461834) Error in data refresh at step DoDevices: Error: Parameter "callback" needs to be of type "function" but type "undefined" has been passed
2023-03-31 13:42:37.398  - error: tado.0 (461834) Disconnected from Tado cloud service ..., retry in 30 seconds !
2023-03-31 13:43:08.382  - info: tado.0 (461834) Connected to Tado cloud, initialyzing...
2023-03-31 13:43:12.492  - info: tado.0 (461834) Initialisation finished, connected to Tado cloud service refreshing every 60 seconds
2023-03-31 14:43:38.435  - error: tado.0 (461834) Error in data refresh at step DoDevices: Error: Parameter "callback" needs to be of type "function" but type "undefined" has been passed
2023-03-31 14:43:38.458  - error: tado.0 (461834) Disconnected from Tado cloud service ..., retry in 30 seconds !
2023-03-31 14:44:09.367  - info: tado.0 (461834) Connected to Tado cloud, initialyzing...
2023-03-31 14:44:13.489  - info: tado.0 (461834) Initialisation finished, connected to Tado cloud service refreshing every 60 seconds
2023-03-31 15:43:39.436  - error: tado.0 (461834) Error in data refresh at step DoDevices: Error: Parameter "callback" needs to be of type "function" but type "undefined" has been passed
2023-03-31 15:43:39.460  - error: tado.0 (461834) Disconnected from Tado cloud service ..., retry in 30 seconds !
2023-03-31 15:44:09.877  - info: tado.0 (461834) Connected to Tado cloud, initialyzing...
2023-03-31 15:44:13.933  - info: tado.0 (461834) Initialisation finished, connected to Tado cloud service refreshing every 60 seconds
2023-03-31 16:44:35.834  - error: tado.0 (461834) Error in data refresh at step DoDevices: Error: Parameter "callback" needs to be of type "function" but type "undefined" has been passed
2023-03-31 16:44:35.852  - error: tado.0 (461834) Disconnected from Tado cloud service ..., retry in 30 seconds !
2023-03-31 16:45:06.771  - info: tado.0 (461834) Connected to Tado cloud, initialyzing...
2023-03-31 16:45:11.137  - info: tado.0 (461834) Initialisation finished, connected to Tado cloud service refreshing every 60 seconds
2023-03-31 17:44:41.038  - error: tado.0 (461834) Error in data refresh at step DoDevices: Error: Parameter "callback" needs to be of type "function" but type "undefined" has been passed
2023-03-31 17:44:41.057  - error: tado.0 (461834) Disconnected from Tado cloud service ..., retry in 30 seconds !
2023-03-31 17:45:11.419  - info: tado.0 (461834) Connected to Tado cloud, initialyzing...
2023-03-31 17:45:15.593  - info: tado.0 (461834) Initialisation finished, connected to Tado cloud service refreshing every 60 seconds
2023-03-31 18:45:44.541  - error: tado.0 (461834) Error in data refresh at step DoDevices: Error: Parameter "callback" needs to be of type "function" but type "undefined" has been passed
2023-03-31 18:45:44.563  - error: tado.0 (461834) Disconnected from Tado cloud service ..., retry in 30 seconds !
2023-03-31 18:46:14.928  - info: tado.0 (461834) Connected to Tado cloud, initialyzing...
2023-03-31 18:46:18.940  - info: tado.0 (461834) Initialisation finished, connected to Tado cloud service refreshing every 60 seconds

Same error with nodejs@18:
echad@chet:~ $ iobroker logs | grep 493588
2023-03-31 19:30:20.060  - info: host.chet instance system.adapter.tado.0 started with pid 493588
2023-03-31 19:30:34.377  - info: tado.0 (493588) starting. Version 0.4.6-alpha.1 (non-npm: DrozmotiX/ioBroker.tado#575913f32f7e1e9120e7640dfdb4279becab7322) in /opt/iobroker/node_modules/iobroker.tado, node: v18.15.0, js-controller: 5.0.1-alpha.0-20230330-e0b409fe
2023-03-31 19:30:34.587  - info: tado.0 (493588) Started with JSON-Explorer version 0.1.11-alpha.1
2023-03-31 19:30:36.363  - info: tado.0 (493588) Connected to Tado cloud, initialyzing...
2023-03-31 19:30:37.406  - error: tado.0 (493588) Error in data refresh at step DoDevices: Error: Parameter "callback" needs to be of type "function" but type "undefined" has been passed
2023-03-31 19:30:38.519  - error: tado.0 (493588) Disconnected from Tado cloud service ..., retry in 30 seconds !
2023-03-31 19:31:09.035  - info: tado.0 (493588) Connected to Tado cloud, initialyzing...
2023-03-31 19:31:16.990  - info: tado.0 (493588) Initialisation finished, connected to Tado cloud service refreshing every 60 seconds

based on your log you are using version based on commit
tado#575913f32f7e1e9120e7640dfdb4279becab7322
I used/refered to commit
tado#247a30d1dfef57dfb0c1cc7636b6cd7d6fd51ef3+
Can you please retry to install the version
DrozmotiX/ioBroker.tado#247a30d1dfef57dfb0c1cc7636b6cd7d6fd51ef3

Thanks!

Excuse me, I failed to install the patched version.
No errors now.

no worries! Glad to hear that it works with the fix!


[automated] Update Lotus version in API tests

Changes

Updates Lotus version in the JSON-RPC API tests to the latest release.

The Lotus images were not uploaded for these tags. I'll ping Lotus team. https://hub.docker.com/r/filecoin/lotus-all-in-one/tags

Blocked by https://github.com/filecoin-project/lotus/issues/12188

Let's queue #4480 together with this one.

@hanabi1224 Shall we cherry-pick ddc1d3b to your branch and close this PR?

Shall we cherry-pick ddc1d3b to your branch and close this PR?

@LesnyRumcajs Done.


Forms do not handle form method GET properly

Right now the Form component adds a hidden input for the method passed to Form. This is a necessary workaround since most browsers only support POST and GET and allows Rails routing to work properly for DELETE, PATCH, and PUT.
That said -- it breaks for GET since it does not follow the expected behavior (putting the variables into the URL etc).
Given that this is an expected way to use a form, we should update the Form component to properly handle GET as a method.

Resolved by https://github.com/user-interviews/ui-design-system/pull/507


more hierarchies for strict mode

currently, we only have one strict mode that disables all classical function calls, it will be more convenient to have:

[x] qasm compatible mode (allow a small set of classical functions)
[x] strict mode

now it's :pure and :qasm


-o option doesn't seem to work

it seems to try to treat my -o 0.7.6 input as the config.plist argument
`
% ./octool -o 0.7.6
Did not find config at "/Users/bkmartin/opencore/octool/-o"
Using tool_config_files/OpenCorePkg/Docs/Sample.plist
`

are you using the latest release version? - currently 0.3.5
unlike my older program, OC-tool, this version does not update itself automatically since it is a compiled binary so users will have to keep downloading the latest version for now
I did have a release in there called "latest_dev_build", but I haven't been good about keeping it up to date

that was the problem.  i saw it doing it's git downloads and assumed it was updating the app as well.  thanks for the great tool


Updated CONTRIBUTE.md

Removed reference to isort fromCONTRIBUTE.md as per related issue.

Thanks for all the updates @yyyaaaccc! If you want one more I have the same thing here https://github.com/sanders41/meilisearch-python-async/issues/434. No pressure to do it, just wanted to put it out there if you want it.


Build error: command '/usr/local/cuda-10.1/bin/nvcc' failed with exit code 1

zzg@zzg-Strix-GL504GW-S5CW:~/CARLA/PythonAPI/carla/lanedet$ python setup.py build develop
/home/zzg/.local/lib/python3.8/site-packages/pkg_resources/init.py:123: PkgResourcesDeprecationWarning: 0.18ubuntu<IP_ADDRESS> is an invalid version and will not be supported in a future release
warnings.warn(
/home/zzg/.local/lib/python3.8/site-packages/setuptools/installer.py:27: SetuptoolsDeprecationWarning: setuptools.installer is deprecated. Requirements should be satisfied by a PEP 517 installer.
warnings.warn(
running build
running build_py
running egg_info
writing lanedet.egg-info/PKG-INFO
writing dependency_links to lanedet.egg-info/dependency_links.txt
writing requirements to lanedet.egg-info/requires.txt
writing top-level names to lanedet.egg-info/top_level.txt
/home/zzg/.local/lib/python3.8/site-packages/torch/utils/cpp_extension.py:369: UserWarning: Attempted to use ninja as the BuildExtension backend but we could not find ninja.. Falling back to using the slow distutils backend.
warnings.warn(msg.format('we could not find ninja.'))
reading manifest file 'lanedet.egg-info/SOURCES.txt'
adding license file 'LICENSE'
writing manifest file 'lanedet.egg-info/SOURCES.txt'
running build_ext
building 'lanedet.ops.nms_impl' extension
x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -fPIC -I/home/zzg/.local/lib/python3.8/site-packages/torch/include -I/home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include -I/home/zzg/.local/lib/python3.8/site-packages/torch/include/TH -I/home/zzg/.local/lib/python3.8/site-packages/torch/include/THC -I/usr/local/cuda-10.1/include -I/usr/include/python3.8 -c ./lanedet/ops/csrc/nms.cpp -o build/temp.linux-x86_64-cpython-38/./lanedet/ops/csrc/nms.o -DTORCH_API_INCLUDE_EXTENSION_H -DPYBIND11_COMPILER_TYPE="_gcc" -DPYBIND11_STDLIB="_libstdcpp" -DPYBIND11_BUILD_ABI="_cxxabi1011" -DTORCH_EXTENSION_NAME=nms_impl -D_GLIBCXX_USE_CXX11_ABI=0 -std=c++14
In file included from /home/zzg/.local/lib/python3.8/site-packages/torch/include/ATen/Parallel.h:140:0,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/utils.h:3,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/nn/cloneable.h:5,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/nn.h:3,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/all.h:13,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/extension.h:4,
from ./lanedet/ops/csrc/nms.cpp:30:
/home/zzg/.local/lib/python3.8/site-packages/torch/include/ATen/ParallelOpenMP.h:83:0: warning: ignoring #pragma omp parallel [-Wunknown-pragmas]
#pragma omp parallel for if ((end - begin) >= grain_size)
In file included from /home/zzg/.local/lib/python3.8/site-packages/torch/include/c10/core/Device.h:5:0,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/c10/core/Allocator.h:6,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/ATen/ATen.h:7,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/types.h:3,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader_options.h:4,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader/base.h:3,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader/stateful.h:3,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader.h:3,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data.h:3,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/all.h:8,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/extension.h:4,
from ./lanedet/ops/csrc/nms.cpp:30:
./lanedet/ops/csrc/nms.cpp: In function ‘std::vectorat::Tensor nms_forward(at::Tensor, at::Tensor, float, long unsigned int)’:
./lanedet/ops/csrc/nms.cpp:40:41: warning: ‘at::DeprecatedTypeProperties& at::Tensor::type() const’ is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
#define CHECK_CUDA(x) AT_ASSERTM(x.type().is_cuda(), #x " must be a CUDA tensor")
^
/home/zzg/.local/lib/python3.8/site-packages/torch/include/c10/util/Exception.h:225:39: note: in definition of macro ‘C10_EXPAND_MSVC_WORKAROUND’
#define C10_EXPAND_MSVC_WORKAROUND(x) x
^
/home/zzg/.local/lib/python3.8/site-packages/torch/include/c10/util/Exception.h:244:34: note: in expansion of macro ‘C10_UNLIKELY’
#define C10_UNLIKELY_OR_CONST(e) C10_UNLIKELY(e)
^~~~~~~~~~~~
/home/zzg/.local/lib/python3.8/site-packages/torch/include/c10/util/Exception.h:291:7: note: in expansion of macro ‘C10_UNLIKELY_OR_CONST’
if (C10_UNLIKELY_OR_CONST(!(cond))) {
^~~~~~~~~~~~~~~~~~~~~
/home/zzg/.local/lib/python3.8/site-packages/torch/include/c10/util/Exception.h:484:32: note: in expansion of macro ‘TORCH_INTERNAL_ASSERT’
C10_EXPAND_MSVC_WORKAROUND(TORCH_INTERNAL_ASSERT(cond, VA_ARGS));
^~~~~~~~~~~~~~~~~~~~~
./lanedet/ops/csrc/nms.cpp:40:23: note: in expansion of macro ‘AT_ASSERTM’
#define CHECK_CUDA(x) AT_ASSERTM(x.type().is_cuda(), #x " must be a CUDA tensor")
^~~~~~~~~~
./lanedet/ops/csrc/nms.cpp:42:24: note: in expansion of macro ‘CHECK_CUDA’
#define CHECK_INPUT(x) CHECK_CUDA(x); CHECK_CONTIGUOUS(x)
^~~~~~~~~~
./lanedet/ops/csrc/nms.cpp:53:5: note: in expansion of macro ‘CHECK_INPUT’
CHECK_INPUT(boxes);
^
In file included from /home/zzg/.local/lib/python3.8/site-packages/torch/include/ATen/Tensor.h:3:0,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/ATen/Context.h:4,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/ATen/ATen.h:9,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/types.h:3,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader_options.h:4,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader/base.h:3,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader/stateful.h:3,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader.h:3,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data.h:3,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/all.h:8,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/extension.h:4,
from ./lanedet/ops/csrc/nms.cpp:30:
/home/zzg/.local/lib/python3.8/site-packages/torch/include/ATen/core/TensorBody.h:303:30: note: declared here
DeprecatedTypeProperties & type() const {
^~~~
In file included from /home/zzg/.local/lib/python3.8/site-packages/torch/include/c10/core/Device.h:5:0,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/c10/core/Allocator.h:6,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/ATen/ATen.h:7,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/types.h:3,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader_options.h:4,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader/base.h:3,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader/stateful.h:3,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader.h:3,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data.h:3,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/all.h:8,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/extension.h:4,
from ./lanedet/ops/csrc/nms.cpp:30:
./lanedet/ops/csrc/nms.cpp:40:41: warning: ‘at::DeprecatedTypeProperties& at::Tensor::type() const’ is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
#define CHECK_CUDA(x) AT_ASSERTM(x.type().is_cuda(), #x " must be a CUDA tensor")
^
/home/zzg/.local/lib/python3.8/site-packages/torch/include/c10/util/Exception.h:225:39: note: in definition of macro ‘C10_EXPAND_MSVC_WORKAROUND’
#define C10_EXPAND_MSVC_WORKAROUND(x) x
^
/home/zzg/.local/lib/python3.8/site-packages/torch/include/c10/util/Exception.h:244:34: note: in expansion of macro ‘C10_UNLIKELY’
#define C10_UNLIKELY_OR_CONST(e) C10_UNLIKELY(e)
^~~~~~~~~~~~
/home/zzg/.local/lib/python3.8/site-packages/torch/include/c10/util/Exception.h:291:7: note: in expansion of macro ‘C10_UNLIKELY_OR_CONST’
if (C10_UNLIKELY_OR_CONST(!(cond))) {
^~~~~~~~~~~~~~~~~~~~~
/home/zzg/.local/lib/python3.8/site-packages/torch/include/c10/util/Exception.h:484:32: note: in expansion of macro ‘TORCH_INTERNAL_ASSERT’
C10_EXPAND_MSVC_WORKAROUND(TORCH_INTERNAL_ASSERT(cond, VA_ARGS));
^~~~~~~~~~~~~~~~~~~~~
./lanedet/ops/csrc/nms.cpp:40:23: note: in expansion of macro ‘AT_ASSERTM’
#define CHECK_CUDA(x) AT_ASSERTM(x.type().is_cuda(), #x " must be a CUDA tensor")
^~~~~~~~~~
./lanedet/ops/csrc/nms.cpp:42:24: note: in expansion of macro ‘CHECK_CUDA’
#define CHECK_INPUT(x) CHECK_CUDA(x); CHECK_CONTIGUOUS(x)
^~~~~~~~~~
./lanedet/ops/csrc/nms.cpp:54:5: note: in expansion of macro ‘CHECK_INPUT’
CHECK_INPUT(idx);
^
In file included from /home/zzg/.local/lib/python3.8/site-packages/torch/include/ATen/Tensor.h:3:0,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/ATen/Context.h:4,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/ATen/ATen.h:9,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/types.h:3,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader_options.h:4,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader/base.h:3,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader/stateful.h:3,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data/dataloader.h:3,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/data.h:3,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include/torch/all.h:8,
from /home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/extension.h:4,
from ./lanedet/ops/csrc/nms.cpp:30:
/home/zzg/.local/lib/python3.8/site-packages/torch/include/ATen/core/TensorBody.h:303:30: note: declared here
DeprecatedTypeProperties & type() const {
^~~~
/usr/local/cuda-10.1/bin/nvcc -I/home/zzg/.local/lib/python3.8/site-packages/torch/include -I/home/zzg/.local/lib/python3.8/site-packages/torch/include/torch/csrc/api/include -I/home/zzg/.local/lib/python3.8/site-packages/torch/include/TH -I/home/zzg/.local/lib/python3.8/site-packages/torch/include/THC -I/usr/local/cuda-10.1/include -I/usr/include/python3.8 -c ./lanedet/ops/csrc/nms_kernel.cu -o build/temp.linux-x86_64-cpython-38/./lanedet/ops/csrc/nms_kernel.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr --compiler-options '-fPIC' -DTORCH_API_INCLUDE_EXTENSION_H -DPYBIND11_COMPILER_TYPE="_gcc" -DPYBIND11_STDLIB="_libstdcpp" -DPYBIND11_BUILD_ABI="_cxxabi1011" -DTORCH_EXTENSION_NAME=nms_impl -D_GLIBCXX_USE_CXX11_ABI=0 -gencode=arch=compute_70,code=compute_70 -gencode=arch=compute_70,code=sm_70 -std=c++14
./lanedet/ops/csrc/nms_kernel.cu: In lambda function:
./lanedet/ops/csrc/nms_kernel.cu:171:43: warning: ‘at::DeprecatedTypeProperties& at::Tensor::type() const’ is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
AT_DISPATCH_FLOATING_TYPES(boxes.type(), "nms_cuda_forward", ([&] {
^
/home/zzg/.local/lib/python3.8/site-packages/torch/include/ATen/core/TensorBody.h:303:1: note: declared here
DeprecatedTypeProperties & type() const {
^ ~~
./lanedet/ops/csrc/nms_kernel.cu:171:98: warning: ‘c10::ScalarType detail::scalar_type(const at::DeprecatedTypeProperties&)’ is deprecated: passing at::DeprecatedTypeProperties to an AT_DISPATCH macro is deprecated, pass an at::ScalarType instead [-Wdeprecated-declarations]
AT_DISPATCH_FLOATING_TYPES(boxes.type(), "nms_cuda_forward", ([&] {
^
/home/zzg/.local/lib/python3.8/site-packages/torch/include/ATen/Dispatch.h:109:1: note: declared here
inline at::ScalarType scalar_type(const at::DeprecatedTypeProperties& t) {
^~~~~~~~~~~
./lanedet/ops/csrc/nms_kernel.cu: In lambda function:
./lanedet/ops/csrc/nms_kernel.cu:171:857: warning: ‘T* at::Tensor::data() const [with T = double]’ is deprecated: Tensor.data() is deprecated. Please use Tensor.data_ptr() instead. [-Wdeprecated-declarations]
AT_DISPATCH_FLOATING_TYPES(boxes.type(), "nms_cuda_forward", ([&] {
^
/home/zzg/.local/lib/python3.8/site-packages/torch/include/ATen/core/TensorBody.h:395:1: note: declared here
T * data() const {
^ ~~
./lanedet/ops/csrc/nms_kernel.cu:171:886: warning: ‘T* at::Tensor::data() const [with T = long int]’ is deprecated: Tensor.data() is deprecated. Please use Tensor.data_ptr() instead. [-Wdeprecated-declarations]
AT_DISPATCH_FLOATING_TYPES(boxes.type(), "nms_cuda_forward", ([&] {
^
/home/zzg/.local/lib/python3.8/site-packages/torch/include/ATen/core/TensorBody.h:395:1: note: declared here
T * data() const {
^ ~~
./lanedet/ops/csrc/nms_kernel.cu:171:916: warning: ‘T* at::Tensor::data() const [with T = long int]’ is deprecated: Tensor.data() is deprecated. Please use Tensor.data_ptr() instead. [-Wdeprecated-declarations]
AT_DISPATCH_FLOATING_TYPES(boxes.type(), "nms_cuda_forward", ([&] {
^
/home/zzg/.local/lib/python3.8/site-packages/torch/include/ATen/core/TensorBody.h:395:1: note: declared here
T * data() const {
^ ~~
./lanedet/ops/csrc/nms_kernel.cu: In lambda function:
./lanedet/ops/csrc/nms_kernel.cu:171:1664: warning: ‘T* at::Tensor::data() const [with T = float]’ is deprecated: Tensor.data() is deprecated. Please use Tensor.data_ptr() instead. [-Wdeprecated-declarations]
AT_DISPATCH_FLOATING_TYPES(boxes.type(), "nms_cuda_forward", ([&] {
^
/home/zzg/.local/lib/python3.8/site-packages/torch/include/ATen/core/TensorBody.h:395:1: note: declared here
T * data() const {
^ ~~
./lanedet/ops/csrc/nms_kernel.cu:171:1693: warning: ‘T* at::Tensor::data() const [with T = long int]’ is deprecated: Tensor.data() is deprecated. Please use Tensor.data_ptr() instead. [-Wdeprecated-declarations]
AT_DISPATCH_FLOATING_TYPES(boxes.type(), "nms_cuda_forward", ([&] {
^
/home/zzg/.local/lib/python3.8/site-packages/torch/include/ATen/core/TensorBody.h:395:1: note: declared here
T * data() const {
^ ~~
./lanedet/ops/csrc/nms_kernel.cu:171:1723: warning: ‘T* at::Tensor::data() const [with T = long int]’ is deprecated: Tensor.data() is deprecated. Please use Tensor.data_ptr() instead. [-Wdeprecated-declarations]
AT_DISPATCH_FLOATING_TYPES(boxes.type(), "nms_cuda_forward", ([&] {
^
/home/zzg/.local/lib/python3.8/site-packages/torch/include/ATen/core/TensorBody.h:395:1: note: declared here
T * data() const {
^ ~~
./lanedet/ops/csrc/nms_kernel.cu: In function ‘std::vectorat::Tensor nms_cuda_forward(at::Tensor, at::Tensor, float, long unsigned int)’:
./lanedet/ops/csrc/nms_kernel.cu:183:115: warning: ‘T* at::Tensor::data() const [with T = long int]’ is deprecated: Tensor.data() is deprecated. Please use Tensor.data_ptr() instead. [-Wdeprecated-declarations]
nms_collect<<<1, 1>>>(boxes_num, col_blocks, top_k,
^
/home/zzg/.local/lib/python3.8/site-packages/torch/include/ATen/core/TensorBody.h:395:1: note: declared here
T * data() const {
^ ~~
./lanedet/ops/csrc/nms_kernel.cu:183:143: warning: ‘T* at::Tensor::data() const [with T = long int]’ is deprecated: Tensor.data() is deprecated. Please use Tensor.data_ptr() instead. [-Wdeprecated-declarations]
nms_collect<<<1, 1>>>(boxes_num, col_blocks, top_k,
^
/home/zzg/.local/lib/python3.8/site-packages/torch/include/ATen/core/TensorBody.h:395:1: note: declared here
T * data() const {
^ ~~
./lanedet/ops/csrc/nms_kernel.cu:183:171: warning: ‘T* at::Tensor::data() const [with T = long int]’ is deprecated: Tensor.data() is deprecated. Please use Tensor.data_ptr() instead. [-Wdeprecated-declarations]
nms_collect<<<1, 1>>>(boxes_num, col_blocks, top_k,
^
/home/zzg/.local/lib/python3.8/site-packages/torch/include/ATen/core/TensorBody.h:395:1: note: declared here
T * data() const {
^ ~~
./lanedet/ops/csrc/nms_kernel.cu:183:214: warning: ‘T* at::Tensor::data() const [with T = long int]’ is deprecated: Tensor.data() is deprecated. Please use Tensor.data_ptr() instead. [-Wdeprecated-declarations]
nms_collect<<<1, 1>>>(boxes_num, col_blocks, top_k,
^
/home/zzg/.local/lib/python3.8/site-packages/torch/include/ATen/core/TensorBody.h:395:1: note: declared here
T * data() const {
^ ~~
./lanedet/ops/csrc/nms_kernel.cu:183:249: warning: ‘T* at::Tensor::data() const [with T = long int]’ is deprecated: Tensor.data() is deprecated. Please use Tensor.data_ptr() instead. [-Wdeprecated-declarations]
nms_collect<<<1, 1>>>(boxes_num, col_blocks, top_k,
^
/home/zzg/.local/lib/python3.8/site-packages/torch/include/ATen/core/TensorBody.h:395:1: note: declared here
T * data() const {
^ ~~
/usr/include/c++/7/bits/basic_string.tcc: In instantiation of ‘static std::basic_string<_CharT, _Traits, _Alloc>::_Rep* std::basic_string<_CharT, _Traits, _Alloc>::_Rep::_S_create(std::basic_string<_CharT, _Traits, _Alloc>::size_type, std::basic_string<_CharT, _Traits, _Alloc>::size_type, const _Alloc&) [with _CharT = char16_t; _Traits = std::char_traits<char16_t>; _Alloc = std::allocator<char16_t>; std::basic_string<_CharT, _Traits, _Alloc>::size_type = long unsigned int]’:
/usr/include/c++/7/bits/basic_string.tcc:578:28:   required from ‘static _CharT* std::basic_string<_CharT, _Traits, _Alloc>::_S_construct(_InIterator, _InIterator, const _Alloc&, std::forward_iterator_tag) [with _FwdIterator = const char16_t*; _CharT = char16_t; _Traits = std::char_traits<char16_t>; _Alloc = std::allocator<char16_t>]’
/usr/include/c++/7/bits/basic_string.h:5042:20:   required from ‘static _CharT* std::basic_string<_CharT, _Traits, _Alloc>::_S_construct_aux(_InIterator, _InIterator, const _Alloc&, std::__false_type) [with _InIterator = const char16_t*; _CharT = char16_t; _Traits = std::char_traits<char16_t>; _Alloc = std::allocator<char16_t>]’
/usr/include/c++/7/bits/basic_string.h:5063:24:   required from ‘static _CharT* std::basic_string<_CharT, _Traits, _Alloc>::_S_construct(_InIterator, _InIterator, const _Alloc&) [with _InIterator = const char16_t*; _CharT = char16_t; _Traits = std::char_traits<char16_t>; _Alloc = std::allocator<char16_t>]’
/usr/include/c++/7/bits/basic_string.tcc:656:134:   required from ‘std::basic_string<_CharT, _Traits, _Alloc>::basic_string(const _CharT*, std::basic_string<_CharT, _Traits, _Alloc>::size_type, const _Alloc&) [with _CharT = char16_t; _Traits = std::char_traits<char16_t>; _Alloc = std::allocator<char16_t>; std::basic_string<_CharT, _Traits, _Alloc>::size_type = long unsigned int]’
/usr/include/c++/7/bits/basic_string.h:6688:95:   required from here
/usr/include/c++/7/bits/basic_string.tcc:1067:16: error: cannot call member function ‘void std::basic_string<_CharT, _Traits, _Alloc>::_Rep::_M_set_sharable() [with _CharT = char16_t; _Traits = std::char_traits<char16_t>; _Alloc = std::allocator<char16_t>]’ without object
__p->_M_set_sharable();
~~~~~~~~~^~
/usr/include/c++/7/bits/basic_string.tcc: In instantiation of ‘static std::basic_string<_CharT, _Traits, _Alloc>::_Rep* std::basic_string<_CharT, _Traits, _Alloc>::_Rep::_S_create(std::basic_string<_CharT, _Traits, _Alloc>::size_type, std::basic_string<_CharT, _Traits, _Alloc>::size_type, const _Alloc&) [with _CharT = char32_t; _Traits = std::char_traits<char32_t>; _Alloc = std::allocator<char32_t>; std::basic_string<_CharT, _Traits, _Alloc>::size_type = long unsigned int]’:
/usr/include/c++/7/bits/basic_string.tcc:578:28:   required from ‘static _CharT* std::basic_string<_CharT, _Traits, _Alloc>::_S_construct(_InIterator, _InIterator, const _Alloc&, std::forward_iterator_tag) [with _FwdIterator = const char32_t*; _CharT = char32_t; _Traits = std::char_traits<char32_t>; _Alloc = std::allocator<char32_t>]’
/usr/include/c++/7/bits/basic_string.h:5042:20:   required from ‘static _CharT* std::basic_string<_CharT, _Traits, _Alloc>::_S_construct_aux(_InIterator, _InIterator, const _Alloc&, std::__false_type) [with _InIterator = const char32_t*; _CharT = char32_t; _Traits = std::char_traits<char32_t>; _Alloc = std::allocator<char32_t>]’
/usr/include/c++/7/bits/basic_string.h:5063:24:   required from ‘static _CharT* std::basic_string<_CharT, _Traits, _Alloc>::_S_construct(_InIterator, _InIterator, const _Alloc&) [with _InIterator = const char32_t*; _CharT = char32_t; _Traits = std::char_traits<char32_t>; _Alloc = std::allocator<char32_t>]’
/usr/include/c++/7/bits/basic_string.tcc:656:134:   required from ‘std::basic_string<_CharT, _Traits, _Alloc>::basic_string(const _CharT*, std::basic_string<_CharT, _Traits, _Alloc>::size_type, const _Alloc&) [with _CharT = char32_t; _Traits = std::char_traits<char32_t>; _Alloc = std::allocator<char32_t>; std::basic_string<_CharT, _Traits, _Alloc>::size_type = long unsigned int]’
/usr/include/c++/7/bits/basic_string.h:6693:95:   required from here
/usr/include/c++/7/bits/basic_string.tcc:1067:16: error: cannot call member function ‘void std::basic_string<_CharT, _Traits, _Alloc>::_Rep::_M_set_sharable() [with _CharT = char32_t; _Traits = std::char_traits<char32_t>; _Alloc = std::allocator<char32_t>]’ without object
error: command '/usr/local/cuda-10.1/bin/nvcc' failed with exit code 1

export CUDA_HOME=/usr/local/cuda


Add to the retrieve-codeowners tool support for returning owners for all paths matching given glob path.

This PR implements for the retrieve-codeowners tool the ability to return not only owners for a single path, but a list of all owners for all paths resolved when matching a glob path given as input.
As such, this PR contributes to:

#5135

This work is necessary to be able to compare and diff the owners of all files in repository before and after the regex matcher is turned on, per this comment:

https://github.com/Azure/azure-sdk-tools/pull/5088#pullrequestreview-1241376684

In other words, this PR contributes to unblocking this PR:

#5088

And as such, also contributes to:

#2770

This PR will require some upstream changes, which are captured by:

#5103

Additional changes

Removed logger from CodeOwnersParser; replaced with Console.Out and Console.Error. This addresses the following comment:

https://github.com/Azure/azure-sdk-tools/pull/5063#discussion_r1066019443

Prevented the new regex matcher from matching paths that have * in them - such paths are malformed anyway (at least on Windows).
A lot of assorted changes to surrounding production & test code - please see the file diff for details.

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow


WARNING in ./node_modules/moment/src/lib/locale/locales.js

when running npm start, warning errors throws and application is not running.
i have tried following steps to resolve this issue, but still it is not yet fixed.

I have changed the path and checked, Still not working. Screenshot below

Locales.js path:

imported DLL - import * as moment from "moment/moment.js". Still not working

installed yarn upgrade, npm install moment. Still not working.

Kindly help us to fix this issue.
Below is the error while running npm start

Below is error while running my application:

my package.json file

2.25.2 should fix this. You might need to exclude moment locales from auto-bundling with moment via webpack configuration.

Running 2.25.2 and get this


fix(build): replace 'docs' with 'dgeni' in build task

First, I tried npm install angular-new-router in a new project, but I wasn't successful in using it because router.es5.js had a reference to $traceurRuntime.
Then I tried building it from scratch, and the build failed because gulp couldn't find the docs task. It looks like it just needs to be replaced by the new dgeni task.
This commit just fixes the build and includes a newly built router.es5.js

Thanks! I addressed this differently in cbe0f137b55236da4d0aad861e29a73fbc7a1aa9.
Also for future reference, the dist should only be checked in on build.


Unable to open Reroll window on dev

Hello,
I've noticed a few weeks ago that opening the Reroll window would cause a crash of GWToolbox and the game. I first thought that was coming from my own devs, but after rebuilding from the up to date dev branch today, I am also reproducing this error, anytime I click on "Reroll" in the main window, toolbox+the game crash.
Crash dump file => https://we.tl/t-zHBYKtmXed

Fixed on dev


Hangman Game

I want to create an interactive hangman game using HTML, CSS and JS for hacktoberfest

go ahead 🚀


implement the summary buffer fix without insantiating new BaseMessage…

Description: Despite this class intending to summarize just enough messages to fit within a set context size, the product of this class always contains ALL messages PLUS a summary system message at the front, ultimately making token count longer rather than shorter. This commit addresses the issue by fixing the single bug where the buffer is constantly reset to the internal message store even after messages are summarized and removed.

The error does not occur with in-memory History buffers, but instead fails when trying to access and modify an immutable database (such as a Postgres DB)
My organization's project repo contains the code that triggered this error to be discovered, as well as output Verbose=True files for the current langchain master, my initial fix, and this revised solution that doesn't replicate any extra Lists.

Issues: Couldn't find one, misread the issue I thought was similar with my last pull request.
@efriis
Reason for changes in diff order:

An index is stored with the moving summary buffer to represent up to which messages it represents
The buffer property only returns memory outside of the summary buffer, without a duplicate List this time
This satisfy's the need for the required member type for any BaseMessage constructor
Update the prune index
Clear index when clearing other members

Hey @Jyumpp ! This is the third time you've opened this PR, and I understand your frustration with the class. Would you be willing to try out the more up to date method of memory that I mentioned in #13481 ? https://python.langchain.com/docs/expression_language/how_to/message_history#adding-message-history
On this older memory object (ConversationSummaryBufferMemory):
In your PR description, you repeatedly reference the memory not functioning like you expect, but when I use the recommended interface documented in the docs, I don't see the behavior you see. As mentioned in #13481, I would guess this has to do with your code manually attaching a postgres-backed chat message history.
This code is unfortunately not mergeable because it would be a breaking change for people using it in the documented way (public attributes change type, return types of functions are different).
I'll leave this open to hear if you're ok to use the new one, but I'll probably close this afterwards!

Thanks for your time! I'll take a look at this new method, but that guide seems to indicate that it functions only on histories and not memories, which I think is more likely to bury the problem than solve it. I do feel that the ability to attach a reconstructed History object is important to many scenarios should they ever extend to prod tools rather than demo toys. To overcome this, would it be better to A) include a private member as the index rather than using the tuple method B) create a new summary buffer memory type exclusively for these immutable cases or C) suffice to just use patched code in projects that happen to run into this issue.


Create workbench.action.terminal.copyLastCommand to match Shell Integrations Tooltip Menu

The options available in the Shell Integrations tooltip menu are not consistent with those available within VScode Settings. This discrepancy is bothersome because you can not use keybinds on the options available in the Shell Integrations tooltip menu (but you can use them with any of the workbench.action's in VScode).

Specifically, there is no option available in VScode settings  to simply "Copy Last Command", which would take the last command you ran and put it in your clipboard. This option is available in the tooltip menu though. I believe the shell integrations tooltip options are defined within the _getCommandActions function on line 346 within this file ( link: https://github.com/microsoft/vscode/blob/main/src/vs/workbench/contrib/terminal/browser/xterm/decorationAddon.ts ).
There already exists an option for copying the output of the last command workbench.action.terminal.copyLastCommandOutput and an equivalent option exists in the tooltip menu, so I do not know why there isn't an equivalent option built into VScode called workbench.action.terminal.copyLastCommand. I think this feature would be a nice addition.
Furthermore, I also think it would be nice to see a combination of workbench.action.terminal.copyLastCommandOutput and workbench.action.terminal.copyLastCommand (perhaps called workbench.action.terminal.copyLastCommandBlock that would copy the last command you ran as the first line and then the output of said command in the subsequent lines that are stored in your clipboard. This would enable you to bind this to a keybind and copy a whole command and its output for use elsewhere (helpful when writing documentation for example).

Any update on this? Does what I described make sense? I can try and provide more information if necessary.

Reaching out again regarding an update on this issue.

Following up on this issue. Would love an update. Thank you.

@0x303 #197098 might duplicate this.

/duplicate https://github.com/microsoft/vscode/issues/197098


Generalise type signature

Hello. This is one of the most useful FFT libraries I've seen - it doesn't call out to any C libraries, and is unencumbered with license restrictions. I'd like to help make it more useful.
I propose generalising the type signatures from Complex Double to Floating a => Complex a. This makes it efficient on 32 bit architectures. I'm happy to help if you'd accept the patch once the work is done.

@oliverbunting I'd be more than happy to accept PRs for this sort of thing!  Please go ahead.


Move Add menu to root

This PR:

Moves the Add menu to the root, sorts the menu
Updates SlicingPlane
Fixes a bug in SwingMainWindow

@skalarproduktraum there have been changes to the addVolume API since the original refactor. I am not claiming this is the best API, my adjustments were about making this build because there ended up being a clash with the Java function signatures of addVolume's nullable arguments.


Show recommendation on projector

Shows the recommendation on the motion slide projector again

Only had the sidebox covered.


pre-commit autoupdate and related changes

This PR includes the results of a pre-commit autoupdate propagated to the affected files.
In more detail:

Black in the release 22.1.0 made a style change that removes spaces around the ** operator in some cases https://github.com/psf/black/pull/2726
This is reflected in both nbqa-black and black-jupyter after the autoupdate.
This change temporarily resulted in a race condition, reproducibility issue and pre-commit failures in some PRs, e.g. in https://github.com/GoogleCloudPlatform/asl-ml-immersion/pull/161 (link to pre-commit.ci failure)

the reason for this is that while black-jupyter respects the pinned Black version number in https://github.com/GoogleCloudPlatform/asl-ml-immersion/blob/17f55063036c621c85dc594b802d9e7be061897c/.pre-commit-config.yaml#L41 , on the other hand nbqa-black uses the black installed in the local environment, and in case of the pre-commit.ci environment this was the latest 22.1.0, as opposed to the pinned 21.12b0.
in theory there would be a 'solution' to this reproducibility issue, in the pre-commit-config.yaml file in the nbqa-black section one could add something like additional_dependencies : ['black:21.12b0'] (see also the same advice in the nbQA doc), but probably this would add an unnecessary layer of manual maintenance burden (e.g. having to manually bump this version and sync with black's), hence this PR only autoupdate's and accepts the repercussions.

Finally, all this means that on your local environment you need to pip install --upgrade black, especially if you experience similar issues.

Thanks Daniel! This is great! LGTM


EKS, GKE and AKS going into Updating state for a few seconds after a rancher upgrade

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):

Deploy AKS/GKE/EKS clusters in 2.3.6
Upgrade rancher to 2.4.3-rc2
The clusters go into "Updating" state for a few seconds ~ < 5 seconds
EKS cluster shows error while updating:

Expected Result:
The cluster should not go into Updating state
Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): 2.3.6 to 2.4.3-rc2
Installation option (single install/HA): HA/Single

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): hosted

This is similar to the behavior seen for RKE clusters getting into "updating" state for a short time which is tracked in https://github.com/rancher/rancher/issues/26471

@sangeethah @soumyalj @sowmyav27 can we have debug logs enabled during upgrade testing next time? Since the state change is for such short time, checking UI is not useful and INFO logs don't tell much either

@mrajashree : Reproduced the issue again with debug logs enabled and provided you the setup.

UI shows "Updating" state when ClusterConditionUpdated is Unknown.
On rancher-server upgrade, cluster sync happens, during which the provisioner controller calls ClusterConditionUpdated.Do(), to check whether the cluster needs an upgrade. This method in norman sets the Updated condition to Unknown first, while checking if the cluster spec has changed. Since the cluster spec doesn't change on Rancher upgrade, the provisioner controller doesn't trigger a cluster upgrade, but because the condition "Updated" was set to "Unknown", for that duration the state is "Updating" in UI. I still think this would have happened for earlier rancher versions too

The above comment explains the "Updating" state, and from discussion with @dramich this would have been the behavior for older versions too, but since 2.4 uses one management controller, it's more visible in 2.3 -> 2.4 upgrade. So @maggieliu @deniseschannon this is not a bug


Switch to using feature for RequestServices

Why? Bug #?

@Tratcher Performance. Making this lazy. The only problem is the fact that IServiceProviders feature is pretty hidden.

Added a test to verify we no-op if there's an existing ISPsFeature.  Removed IServiceScope from ctors and just GetRequiredService when needed

Small change then :shipit: once CI is green

49520a2a73251a9f718743df4a43d26514021767


Spec enhancements -  stubbing in factories

Context
Enables stubbing in factories, as discussed in last week's dev retro, and updates ucas_match spec to utilise stubbed factory where data retrieval is not required.
Changes proposed in this pull request

Update rspec configuration to enable stubs in factories
Use new stubeed factory in UCASMatch spec

Things to check

[x] This code does not rely on migrations in the same Pull Request
[x] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[x] API release notes have been updated if necessary
[x] New environment variables have been added to the Azure config

I did consider using a more descriptive name for the factory to make it more obvious that this is a stub, which may be a pattern worth adopting if we move forward with this.
At the moment we seem to be moving away from testing everything thoroughly because of the complexity and time it takes to setup data, so I think it can help us aim for better test coverage.

I did consider using a more descriptive name for the factory to make it more obvious that this is a stub, which may be a pattern worth adopting if we move forward with this.
At the moment we seem to be moving away from testing everything thoroughly because of the complexity and time it takes to setup data, so I think it can help us aim for better test coverage.

I think this approach works well for :dual_application_ucas_match but I'd be interested to see how/if it works for application forms and choices, which have greater dependencies on associations between themselves and other models. Yes, our current default of creating applications leads to tests that are slower to run but these are faster to write (because in most cases we just reference a trait and overwrite one or two values, if any). There is, of course, the cost of maintaining these traits, but I think maintaining traits and aligning them with business rules, process states etc. is a good thing™. But this is an aside.
The other thing to consider is our general approach to testing. We tend to favour service-level tests because a) they immediately correspond to business value and processes and b) they allow us to refactor without constant revising of tests. I don't think using stubbed models would be appropriate for such tests, but perhaps many presentation layer scenaria (e.g. component specs, previews) could benefit from a more stubbed approach. But even then, some components fetch data from multiple associations etc. so we'd need to do a fair amount of stubbing.
To summarise, I'm happy with this specific PR but I'm not convinced we could take the same approach across the board, with the aim of speeding up the test suite. Is it worth trying this approach for different types of spec involving application choices in different states next time?

I agree with @tijmenb's comment. I think we should make that change, merge this, and stick to that (stub factories should be in the spec file) as our practice in the short term, then review in due course? Wdyt @despo?

@tijmenb @duncanjbrown  Happy to move this out of the factories, however I am not a fan of noisy specs (having to scroll to line 62 to find the actual tests as in the example provided by @tijmenb) and would rather to have a well named helper module that is included in the specs, which should also make visibility of this functionality easier across the project as it won't rely on other team members having to specifically open the ucas_match_spec in order to see this implementation. E.g. UCASMatchStubbedFactory in /spec/support/stub_factories/

@mnacos
The intention is not to use these across all specs, but to instead replace some of the already stubbed factories generated using build_stubbed and overcome some of FactoryBot's limitations, such as being able to access the course of a stubbed application choice. I think the example demonstrated in this PR is unfortunately not the best one but due to the necessary identified refactoring to the application choice factories (to improve trait usage) I didnt want to rush and create any stub factories for ApplicationChoice just yet!


ip-check-prefix.py: prefix with is_pool

If parent prefix is a pool, allow contained address to be /32 (v4) or /128 (v6)
(Commit rebased on top of #20)

@candlerb would you mind updating this to support the constants refactor in 2.7?

Could you merge #20 first please?  That has some 2.7 updates and this patch sits on top of it.

I have now rebased this onto master and it's ready to merge.
(The changes for 2.7 constants were part of #20 / c4153d2a)