Closure #1 in closure #1 in Thenable.done(on:flags:_:) Crash

PromiseKit 6.9
CocoaPods 'PromiseKit/Alamofire'
I've services that calls for example :
    static func getOffices() -> Promise<Offices?> {

        let request = OfficesRequest.getOffices

        return Promise {seal in  APIService.shared.execute(model: request, decodedTo: Offices.self).done { (model) in
            seal.fulfill(model)
        }.catch { (error) in
            seal.reject(error)
        }}

    }

i would call it in view controller:
        firstly{
            OfficesService.getOffices()
        }.done { (offices) in
            guard let offices = offices else {return}
            self.offices = offices
        }.catch { (error) in

        }.finally {

        }

The crash is received through Crashlytics with below details:
Thenable.swift line 151
closure #1 in closure #1 in Thenable.done(on:flags:_:)

Crashed: com.apple.main-thread
0  AppName                         0x100932674 (Missing)
1  AppName                         0x100935eb8 (Missing)
2  AppName                         0x100935f20 (Missing)
3  PromiseKit                     0x1018a9774 closure #1 in closure #1 in Thenable.done(on:flags:_:) + 151 (Thenable.swift:151)
4  PromiseKit                     0x1018855a8 thunk for @escaping @callee_guaranteed () -> () + 4588 (<compiler-generated>:4588)
5  libdispatch.dylib              0x1a8afe610 _dispatch_call_block_and_release + 24
6  libdispatch.dylib              0x1a8aff184 _dispatch_client_callout + 16
7  libdispatch.dylib              0x1a8ab1190 _dispatch_main_queue_callback_4CF$VARIANT$mp + 1044
8  CoreFoundation                 0x1a8db05e4 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 12
9  CoreFoundation                 0x1a8dab5d8 __CFRunLoopRun + 2004
10 CoreFoundation                 0x1a8daaadc CFRunLoopRunSpecific + 464
11 GraphicsServices               0x1b2d30328 GSEventRunModal + 104
12 UIKitCore                      0x1acea5ae0 UIApplicationMain + 1936
13 AppName                         0x100813884 (Missing)
14 libdyld.dylib                  0x1a8c34360 start + 4

It's crashing in your code in the handler, PromiseKit is not crashing.

I am in the same situation


Regenerate Event Grid .NET SDK for 2020-04-01-preview to include new properties changes

Regenerate Event Grid .NET SDK for 2020-04-01-preview to include new properties changes

Link to Swagger PR: https://github.com/Azure/azure-rest-api-specs/pull/9402
Link to Swagger file: https://github.com/Azure/azure-rest-api-specs/blob/master/specification/eventgrid/resource-manager/Microsoft.EventGrid/preview/2020-04-01-preview/EventGrid.json

Hello @isra-fel @erich-wang ... Can you please help reviewing this change?
Also, it seem check-enforcer is stuck in running state since yesterday. Is this infra issue?
thanks

Hello, I just merged a PR to skip that test: https://github.com/Azure/azure-sdk-for-net/pull/12097
Could you rebase latest master?

Hello @isra-fel  .. Thanks for merging the test fix.. I rebased and resubmitted. All checks passe snow. Kindly merge the change.
thanks

/azp run net - eventgrid - ci


More test and improvements - fix issues with icons in maya dock.

Hey @huntfx,
I've recently released my project (only the framework for now) but I've been working on the UI as well and I have some changes to propose for your package. Feel free to discuss them :)

Replace pymel with maya.cmds: Even if I understand the qualities for pymel, it's not something most people want to work with, it's slow to import and not native, I never worked anywhere where it was used or even tolerated. So to improve the accessibility for vfxwindow I think we can safely replace it with the default maya.cmds, I kept the namespace mc you were already using. I've been testing this almost since my last PR and it seems to work the same, except it's faster to launch.
Minor change on MayaWindow, I've added support last time for the icon on the floating window and it was working well when the windows start as docked. Unfortunately, if the windows is dockable but not docked, it was displayed with no icon. This is now fixed.
Replace the numerous dcc names attributes on the AbstractWindow with an "abstract" property to be implemented on subclass to get the name of the software. It's a "nice name" by default but can be tested using self.software.lower() == 'maya' to prevent false positive. The best solution is still to do:

from vfxwindow import software

if software.isMaya():
    ...

Let me know what you think,
Greg.

Hey again, It was so long ago that I'd honestly forgotten it was using pymel, but yes I'd be very happy phasing it out lol. I'll have a check of its source code to make sure it's not doing anything extra in regards to docking. One thing I see you removed was the qtObj = pm.uitypes.toQtObject(windowID) part, which was something to do with attaching Maya UIs to a Qt window. Not very important at all, but I should ideally figure that bit out again, and if anything I'll just do a lazy import if it's pymel only.
The software attributes were actually part of the plan to redo when doing a 2.0 version, I'd not decided how best to handle it but I like your idea. I'm definitely up using that going forward, but for the sake of compatibility while it's on 1.x would you be able to restore the attributes back?
Cheers again :)

About the pm.uitypes.toQtObject(windowID) I remember doing test to wrap a maya widget (Node Editor, Attribute Editor) and it was working also without this part of the code, it looks like the find control handle it well, at least in Maya 2023 (I'll double check that to be sure 👍)
Oh cool for the attributes, to be honest I was not a fan having all those attributes where most of them shouldn't be on the class so that's the reason for the change, I was also thinking about building classes to represent each software, where we could also be able to get the versions and other things like that but that could've requested way more development and the need is not there yet so that's probably overthinking. I wanted to keep it simple but still clean to use.
But actually you're right, I will bring them back and mark them as deprecated so you know you can remove them on the next major release. (If you want too).

@huntfx It should be better now, we have all attributes for backward compatibility, marked as deprecated since this release name (1.9.0).
It should be compatible to show in sphinx if someday you want to generate a documentation. :)

The attributes are back from when there was only Maya and Nuke support, and I just needed a way of determining which one for the purpose of adding callbacks. It obviously got a lot less "nice" as more software was added lol, but I'd already pushed it to pypi so didn't want to break anything.

I was also thinking about building classes to represent each software, where we could also be able to get the versions and other things like that but that could've requested way more development and the need is not there yet so that's probably overthinking

I like the sound of that to be honest - just brainstorming here with the basics, but I'm thinking of doing something like this:
# software.py
class NukeSoftware: ...
Nuke = NukeSoftware()  # I'm aware it would be more pythonic as NUKE but I find it looks a bit ugly with Qt

# init.py
from vfxwindow import software
if software.Nuke:  # Using bool will determine if it's the current software
    from .nuke import NukeWindow as VFXWindow

# nuke.py
>>> from vfxwindow.software import Nuke
>>> self.software = Nuke
>>> self.software
'Nuke'
>>> self.software == 'nuke'  # case insensitive check
True
>>> self.software.batch  # hide away the batch mode attribute
False
>>> self.software.version  # gets the full version as a string
'14.0v5'
>>> int(self.software.version)  # gets the major version
14
>>> float(self.software.version)  # gets the major and minor version
14.0

Also thanks, I've never quite known how to properly deprecate stuff. Since I'm using 2.0 as an excuse to do a major code cleanup, I'm planning on expanding the documentation a lot more then as I do that :)
(also don't worry about testing the Maya widget wrapping, I'll get round to doing it at some point)

The attributes are back from when there was only Maya and Nuke support, and I just needed a way of determining which one for the purpose of adding callbacks. It obviously got a lot less "nice" as more software was added lol, but I'd already pushed it to pypi so didn't want to break anything.

I was also thinking about building classes to represent each software, where we could also be able to get the versions and other things like that but that could've requested way more development and the need is not there yet so that's probably overthinking

I like the sound of that to be honest - just brainstorming here with the basics, but I'm thinking of doing something like this:
# software.py
class NukeSoftware: ...
Nuke = NukeSoftware()  # I'm aware it would be more pythonic as NUKE but I find it looks a bit ugly with Qt

# init.py
from vfxwindow import software
if software.Nuke:  # Using bool will determine if it's the current software
    from .nuke import NukeWindow as VFXWindow

# nuke.py
>>> from vfxwindow.software import Nuke
>>> self.software = Nuke
>>> self.software
'Nuke'
>>> self.software == 'nuke'  # case insensitive check
True
>>> self.software.batch  # hide away the batch mode attribute
False
>>> self.software.version  # gets the full version as a string
'14.0v5'
>>> int(self.software.version)  # gets the major version
14
>>> float(self.software.version)  # gets the major and minor version
14.0

Also thanks, I've never quite known how to properly deprecate stuff. Since I'm using 2.0 as an excuse to do a major code cleanup, I'm planning on expanding the documentation a lot more then as I do that :)
(also don't worry about testing the Maya widget wrapping, I'll get round to doing it at some point)

So for now you're ok with that solution ? Keeping the legacy attributes and maybe replace them in the future (On a major update)
I also like the idea of software objects, they could be dataclasses actually, that would make sense for what they will be used for. But I think this may request some work, it could make sense for a future update.
I'm happy to help, actually this way of deprecating is really "documentation oriented". There's other way, like subclassing Warning or implementing special decorators with loggers. Nothing 100% formal tho. For a single attribute I think there's not real good way other than documentation.
So, what do you think about the PR, maybe you prefer if I remove every changes and leave this for a future update where you implement software classes ? (And I keep only the maya widget icon fix in this PR)

So for now you're ok with that solution ? Keeping the legacy attributes and maybe replace them in the future (On a major update)

Yeah absolutely, those attributes will 100% be nuked for 2.0, I'd mainly just not decided on self.application or self.software and you made the choice for me :)   And while I like the idea of dataclasses, I'm aiming to keep this compatible with py2 for a lot longer, so a custom one will work fine.
I'm happy with the PR as it stands anyway, will do what I did last time and get it slowly tested :)

Hey, I've not forgotten about this, just been on holiday so not had a good chance to fully test yet :)
In regards to pm.uitypes.toQtObject(), behind the scenes its just calling wrapinstance(maya.OpenMayaUI.MQtUtil.findControl(), QtCore.QObject) (with some extra stuff to get the correct widget type), so it should be totally fine leaving this removed.
I've also started doing a bit on the application data class in a separate branch, with all the same behaviour as my previous example. I decided on using "application" rather than "software" after having a chat with some coworkers, though my branch is still far off merging so I'll just do a quick update on this PR to update that.
I also just went down all the other changes in a bit more detail - I'll test your edits to _parentOverride, will think about if the change of pm.uitypes.toQtControl to getMainWindow should just directly call the underlying function, and fix where pm.uitypes.toQtObject(form) was changed to mc.uitypes.toQtObject.

With the parent override part where added the part saying If the window has no parent, it was probably forgotten by user so we can assume it should be the maya main window., were you able to cause this to happen at one point or you just spotted a potential issue with the code flow?
If I recreate it by doing this (the only way I could figure out how), then the main Maya window is moved when it should just be the widget itself.
from vfxwindow.debug import TestWindow
TestWindow.WindowDockable = True
win = TestWindow.show()
win.setParent(None)
win.move(50, 50)

What works is changing getMainWindow() to super(MayaWindow, self)._parentOverride(), but I'd like to run it by you first in case you spotted something I didn't.
if base is None:
    self.__parentTemp = super(MayaWindow, self)._parentOverride()

With the parent override part where added the part saying If the window has no parent, it was probably forgotten by user so we can assume it should be the maya main window., were you able to cause this to happen at one point or you just spotted a potential issue with the code flow?
If I recreate it by doing this (the only way I could figure out how), then the main Maya window is moved when it should just be the widget itself.
from vfxwindow.debug import TestWindow
TestWindow.WindowDockable = True
win = TestWindow.show()
win.setParent(None)
win.move(50, 50)

What works is changing getMainWindow() to super(MayaWindow, self)._parentOverride(), but I'd like to run it by you first in case you spotted something I didn't.
if base is None:
    self.__parentTemp = super(MayaWindow, self)._parentOverride()

Hey, I think during my tests I had a weird issue where the full maya window moved. Unfortunately now it's not that fresh in my mind.
It may also have been about the icon thing, when it's docked and undocked the behavior is a bit weird and if the widget is created with no parent and is in a floating mode at first show, I think there was something weird.

I went digging into that dock/floating issue and opened a can of worms. Good news is it's improved a lot, though I found one or two edge cases I had to add comments for as I wasn't able to fix.
Anyway, I'll get this merged into the main branch now as your PR is stable and I shouldn't be doing edits lol, thanks again for the help. I'll get my application class branch merged in for 1.9 too as it'll let me fix a few messier bits of code.


The same allele, not reported

https://www.pombase.org/genotype/nda3-KM311-unknown-unknown
nda3-311, nda3-311cs
but
https://www.pombase.org/genotype/nda3-311-unknown-unknown-expression-not_assayed
but does not appear here
https://curation.pombase.org/dumps/latest_build/logs/log.2021-11-24-04-28-54.chado_checks

So the synonym matches?  I don't think there are any checks for synonyms yet.

Hmm, here a primary name of one gene is the synonym of another gene which would not cause an alert unless the description are the same. But here the descriptions are the same "unknown".
If we have   2 tye "unknown" with a shared name (primary, or synonym), for the SAME GENE that should be looked into, because they are almost certainly going to be the same allele.... Can we report these?

If a specific gene has more than 1 alleles of type "unknown", with a shared allele name or synonym, report.

We need to standardize the background use too.
It seems that we have settled on nda3-KM311. I will fix the genotypes.

I meant to say could you access the usage of nda3-311 in backgrounds so that I can fix this too.

If a specific gene has more than 1 alleles of type "unknown", with a shared allele name or synonym, report.

I've had a go at this.  It didn't make it into the current load but it should be there on Wednesday morning.  Here's an example output:  unknown_allele_name_synonym_matches.tsv.txt
The first column is the allele name.  The third column is the name or synonym that is duplicated.  The if it was a synonym that was duplicated the fourth column will contain "synonym".  The synonym will occur in or more of canto sessions listed.  Sorry, it's not the clearest.

I will try to parse that when I look at the logfile ;)

t didn't make it into the current load but it should be there on Wednesday morning.

https://curation.pombase.org/dumps/builds/pombase-build-2021-12-07/logs/log.2021-12-07-22-23-18.chado_checks.unknown_allele_name_synonym_matches


Implement EntryLog and cache

Maybe simply use RocksDB as the index engine.

Write cache, write journal;
Checkpoint write cache to entry log and roll up journal;
Read from cache, from entry log.

Checkpoint and cache can be optimization also.
The basic classes of a EntryLog storage are:

EntryLogger
Entry
EntryLocation (ledgerId(?), logId, position)
LedgerStorage (manage indices and entry log files)

Ledgers layout:

LedgerDirsManager
EntryLogIds
EntryLoggerAllocator
EntryLogger
EntryLogManagerBase

We should first define a Ledger abstraction and delegate its file creation, entries read and write to a shared class. Embedded the position index lookup and pluggable for further implementation.

Close as particially done in #20. Caches should be added later - currently, all writes should be flushed to be readable.


Yaml files needs to be updated for the PMID:38448586 (submission ID: 6564aefc53c4ef0001094614)

The traits in the UI are correct, but the yaml files still have old traits and need to be updated.
Total 233 studies.

Accession IDs: 90301941--90302173

@eks-ebi to test this once completed (Santhi will be on leave next week)

Looks good except for this one: http://ftp.ebi.ac.uk/pub/databases/gwas/summary_statistics/GCST90301001-GCST90302000/GCST90301942/

There was something wrong with the one above due to caching I believe. Now all looks good to me.

@eks-ebi to verify

@karatugo Thanks I can confirm that the trait is now correct in the YAML for this study: http://ftp.ebi.ac.uk/pub/databases/gwas/summary_statistics/GCST90301001-GCST90302000/GCST90301942/

@Santhi1901 there is one problem remaining in the traits in the UI, which was spotted by user Martijn Zoodsma on gwas-info. I've looked into it and I'm pretty sure that there is just one study with an incorrect Reported trait and EFOs:
GCST90301976 currently has Reported trait Cholesteryl esters to total lipids ratio in IDL, should be Total cholesterol to total lipids ratio in IDL. And the EFOs are currently cholesteryl esters:total lipids ratio and intermediate density lipoprotein measurement, should be cholesterol:total lipids ratio and intermediate density lipoprotein measurement.
I haven't made the change myself because I'm not 100% sure that I understand how you did the reannotation, and I could have made a mistake. Could you please have a look when you get back and make sure this is the correct way to fix the issue?

corrected the trait+EFO for GCST90301976 and republished

Hi @Santhi1901 could you please confirm if this ticket can be closed ? Thanks

it can be closed


item #121 fixed windows scripts

Signed-off-by: Christopher Morgan<EMAIL_ADDRESS>

Chris, did you merge this change already? I thought we were using a high-trust process in which any maintainer can commit and push to the main branch. If you're satisfied that you've tested the change sufficiently, you can go ahead with it.

Hi Dave,
That commit was pushed at whatever date item #121 was originally closed
(late march). I had the fork from before I had access to make my own
commits. I just deleted the fork and closed the pull request so all should
be well now. I've been working using the main repository since.
Thanks

http://www.mercurial-solutions.com
Christopher Morgan
Managing Member
Mercurial Solutions LLC http://www.mercurial-solutions.com
@.***
On Tue, Jun 15, 2021 at 11:44 AM Dave Nicolette @.***>
wrote:

Chris, did you merge this change already? I thought we were using a
high-trust process in which any maintainer can commit and push to the main
branch. If you're satisfied that you've tested the change sufficiently, you
can go ahead with it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/openmainframeproject/cobol-check/pull/123#issuecomment-861611303,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AR63GY6XY4ELN3I4FCIPDDDTS5YNFANCNFSM4ZGTIL5A
.


ContainerProperties.Name does not contain the name?

In our testing, schema1.ContainerProperties.Name does not contain the container name as reported by Docker, but instead the container id. Is this intentional? Is there another way to get the name as Docker sees it?

@swernli - Can you confirm? It was my understanding that Name was always the User Defined Name and Id was the generated Id. Right?

I think @carlpett is referring to the docker friendly name, as in "infallible_ramanujan" or the like.  This is a purely docker concept, and does not make it's way into the HCS schemas at all.  The schema1.ContainerProperties.Name was not intended to be a supported field (due to this confusion between ID and friendly name), and as such it is no longer present in schema2.

@jterry75 what about the name of the image the container was ran from? An example use-case here is a docker swarm cluster where we need useful information about which container is which across a bunch of hosts, rather than a guid and some file system path.

@Drewster727 The name of the image is not something that is passed to HCS, so it doesn’t have that information to return on query. Like the container friendly name, the image name is only a concept in docker. From the platform perspective, a layer is just a file path and a GUID identifier. If you need docker specific information, it has to be queried from docker, not from the HCS.

Ok, thanks.


Crash when running entire test suite. 11 Pro iOS 15.4 simulator Raw

Seems to be crashing randomly in Combine code.
https://gist.github.com/hboon/b5f761c17c091b8f0a77d9b77e72bdc1

Lets wait for https://github.com/AlphaWallet/alpha-wallet-ios/pull/5047 first, looks like it fixes this issue. Need to double check it.


Extra large device max-width breaking decorations

Description:
When applying certain decorations (e.g. background color) to an element that contains a Bootstrap class, an invalid media query wraps the style added causing browsers to ignore the style.
How to reproduce issue:

Start with empty canvas
Click on Body
Go to Style Manager tab
Add Bootstrap class (e.g. jumbotron)
Try changing background color under Decorations

Result:
@media (max-width: 100%){
  .jumbotron{
    background-color:#d02121;
  }
}

The default device (Extra Large) shouldn't have @media queries for its styles and is causing browsers to ignore everything underneath it.
The max-width parameter should be omitted when initializing a list of devices in devices.js. I'll be submitting quick a PR for that.

Hey! Sorry for the late response. I merged this PR, thanks for the help!


Implement Automatic Issue Closure Comments

This feature aims to automate the process of commenting on closed issues within the project repository. Upon the closure of an issue, an automated comment will be generated, expressing gratitude to the contributor for their input and providing any relevant follow-up information or next steps. By implementing this feature, we can enhance the project's workflow by promptly acknowledging contributors when their reported issues are resolved, standardizing communication to ensure all contributors are informed about issue resolution status, and improving transparency in the resolution process. This automation will streamline collaboration and contribute to a more efficient and user-friendly experience for all project contributors.

@sethshivam11 Could you assign and add label of gssoc and level.


New Package(gh-121099): FireDaemon.OpenSSL 3.1.3

Resolve https://github.com/microsoft/winget-pkgs/issues/121099 .

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Have you tested your manifest in Windows Sandbox with Tools/SandboxTest.ps1 -Manifest <path>?
[x] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Weird, the changes shouldn't have caused an unattended failure, since the silent and custom switches would be applied to all runs

The previous Silent switch was copied from the User Guide. Can't figure out what was wrong...


[CHEC-827] - create chec-file-uploader, using dropzone

also creates primitive component file-row for chec-file-uploader component to use

How's this going @john-raymon? Just want to make sure you saw my comment about the missed A/C?

@ScopeyNZ Yes, wrapping this up was separating the chec-loading work to it's own PR https://github.com/chec/ui-library/pull/271

@john-raymon if you can add doc-blocks to props and events, and remove yourself as an assignee when you've finished working on this, I'll re-review. I think that'll help keep things cleaner rather than littering it with reviews while it's WIP.
Let me know if you want any help working on this.

@ScopeyNZ Added the doc-block comments and some other necessary changes such as the error file-row state and more. All ready to review :)

Oh also the FileRow story wasn't working for me.


Windows Subsystem for Linux: $ bin/grav new-project fails

Environment:

Running Windows 10, using Windows Subsystem For Linux (Ubuntu distro)
Websites are installed on Windows file system, not inside WSL.
Commands are run from bash shell in WSL.

Used two version of Grav installations, Zip (fails) and git clone (success).
Using Zip GRAV CORE + ADMIN PLUGIN 1.5.1
Steps:

Extracted zip
Browsing to 'localhost/grav-admin'
Required to add user
Updated Quark as requested
Website 'localhost/grav-admin' is running fine
$ bin/grav new-project ../site-x
Error

Pages Initializing
    /mnt/c/path/to/www/grav-admin/user/pages -> Created
    mappings: /.gitignore does not exist!

install should be run with --symlink|--s to symlink first

$ touch .gitignore
$ bin/grav new-project ../site-xx
Error:

Pages Initializing
    /mnt/c/path/to/www/grav-admin/user/pages -> Created

File Initializing
PHP Warning:  copy(/mnt/c/path/to/www/grav-admin/.dependencies): failed to open stream: No such file or directory in /mnt/c/path/to/www/grav-admin/system/src/Grav/Console/Cli/SandboxCommand.php on line 222
PHP Stack trace:
PHP   1. {main}() /mnt/c/path/to/www/grav-admin/bin/grav:0
PHP   2. Symfony\Component\Console\Application->run() /mnt/c/path/to/www/grav-admin/bin/grav:45
PHP   3. Symfony\Component\Console\Application->doRun() /mnt/c/path/to/www/grav-admin/vendor/symfony/console/Application.php:148
PHP   4. Symfony\Component\Console\Application->doRunCommand() /mnt/c/path/to/www/grav-admin/vendor/symfony/console/Application.php:248
PHP   5. Grav\Console\Cli\NewProjectCommand->run() /mnt/c/path/to/www/grav-admin/vendor/symfony/console/Application.php:946
PHP   6. Grav\Console\Cli\NewProjectCommand->execute() /mnt/c/path/to/www/grav-admin/vendor/symfony/console/Command/Command.php:251
PHP   7. Grav\Console\Cli\NewProjectCommand->serve() /mnt/c/path/to/www/grav-admin/system/src/Grav/Console/ConsoleCommand.php:29
PHP   8. Grav\Console\Cli\SandboxCommand->run() /mnt/c/path/to/www/grav-admin/system/src/Grav/Console/Cli/NewProjectCommand.php:61
PHP   9. Grav\Console\Cli\SandboxCommand->execute() /mnt/c/path/to/www/grav-admin/vendor/symfony/console/Command/Command.php:251
PHP  10. Grav\Console\Cli\SandboxCommand->serve() /mnt/c/path/to/www/grav-admin/system/src/Grav/Console/ConsoleCommand.php:29
PHP  11. Grav\Console\Cli\SandboxCommand->initFiles() /mnt/c/path/to/www/grav-admin/system/src/Grav/Console/Cli/SandboxCommand.php:120
PHP  12. copy() /mnt/c/path/to/www/grav-admin/system/src/Grav/Console/Cli/SandboxCommand.php:222
    /.dependencies -> Created
    /.htaccess -> Created
    /user/config/site.yaml -> Created
    /user/config/system.yaml -> Created

Permissions Initializing
    bin/composer.phar permissions reset to 755
    bin/gpm permissions reset to 755
    bin/grav permissions reset to 755
    bin/plugin permissions reset to 755

ERROR Missing .dependencies file in user/ folder
HINT Are you trying to install a plugin or a theme? Make sure you use bin/gpm install <something>, not bin/grav install. This command is only used to install Grav skeletons.

No plugins installed, no themes installed.
Using git clone
Steps:

$ git clone -b master https://github.com/getgrav/grav.git
$ composer install --no-dev -o
$ bin/grav install
$ bin/gpm install quark
Website 'localhost/grav-master' is running fine
$ bin/grav new-project ../site-xxx
Website 'localhost/site-xxx' is running fine
Quark and plugins have been installed

Copy .gitignore + .dependencies from repo solved the issue.
Note: I guess both .gitignore and .dependencies should not be required.
Using Zip GRAV CORE + ADMIN PLUGIN 1.5.1
Steps:

Extracted zip
Browsing to 'localhost/grav-admin'
Required to add user
Updated Quark as requested
Website 'localhost/grav-admin' is running fine
$ bin/grav new-project ../site-x                                                       -> fails
$ bin/grav sandbox -s ../site-xx                                                       -> fails
Copy .gitignore + .dependencies from repo
$ bin/grav new-project ../site-y                                                       -> success
$ bin/grav sandbox -s ../site-yy                                                       -> success


Refactor to use require_relative instead of require

I found some issues with Puppet::Util::AtFork and Puppet::Util::Posix, and fixed up the commits in a new PR #8595


Issue4392 resolution - No new line after operation

For issue #4392 resolution - not adding new line after operation ('==', etc.).
Also test cases file is added.
An issue in the code changes is that "transmute" is used. Hopefully there is better way to implement.

OK, Thanks. I now see that the root issue may be related to the issues discussed in the other thread, so this issue should be retested after the other issues are solved.
Regarding the repeated changes this was unintentional and I will try to make sure that doesn't happen (unless the same change is part of solving different issues).


Document how to update/contribute to docs

Docs are held in docs/ folder in maverick repo and use docsify.  Document how to run docsify server for development, and how to update docs to google hosting.

Actually super simple -docs are served by maverick webserver, eg:
http://maverick-raspberry.local/web/docs/maverick
Any updates to the markdown files are immediately reflected on load, as there is no compilation stage.

Users contributing to maverick docs a little tricky as ~/software/maverick shouldn't really be altered because it's so integral to the running of the system.  Should probably fork and clone into ~/code.  Document how to do this.


Request for Input on Porting Bangs-For-Google Extension to Manifest V3

I am currently working on porting your version of Bangs-For-Google to the "new" manifest V3 (because version 2 will be / is already deprecated). That comes with its own complications. I really enjoyed using your extension. Because I am using your work as a base, I wanted to ask, how you would like me to proceed.
Facts about the almost-finished port:
Will support manifest V3 (necessary to be used now / in the future)
Will probably not be specific to Google (will generally only check omnibox and not redirect requests to Google, because of limitations from manifest V3, at least that's my current understanding of V3)
Therefore, I have at least two possible ways to proceed and wanted to ask for your approval for one because of your underlying work.
Way 1: I could fork your repository and open a pull request. (Don't know if this would be in your interest, because the name of the extension is "Bangs-For-Google" and exactly that Google part would be gone after that.)
Way 2: Still fork your repository, give all potential credits and link to your repository / your GH account, but release this extension under a new name, because the Google part isn't really a thing anymore.
I would greatly appreciate your input on this matter! Thanks again for creating this extension!

Thanks for your interest in this, I'd be happy to merge your updated version with MW3 so existing users will also be migrated over.
As for the name, I'd be happy to rename it to something like "Universal Omnibox Bangs" so it isn't bound to Google.

Alright, so the plan is as follows:
Get updated version ready for a pull request so that as soon as possible other users can use the extension again.
This will probably not block google requests to make it faster, as this is either a hassle with the new manifest v3 or not even possible, might have to look into that a little more if I got time..
After some testing the "missing" blocking function does not seem to decrease performance all that much.
I feel like the name could stay the same, you could think about updating the description of the repo / chrome extension store to inform people that it would actually work with other search engines too, because it doesn't really depend on a search engine..

One thing that would be nice for users, while already updating the extension: Update the information in the stores that the extension is not collecting any data whatsoever (I only know that chrome ext. store offers information about that)


Dusk v6 release

Is is possible to prepare a Dusk 6 release branch, for Laravel 8? So we can start testing Laravel 8 packages before the release?
Thanks!

Sure, but dev-master or "orchestra/testbench-dusk": "^6.0" right now should allow tests against Laravel 8.

Hmm, I tried that in https://github.com/barryvdh/laravel-debugbar/pull/1097 but it fails (eg. in https://github.com/barryvdh/laravel-debugbar/pull/1097/checks?check_run_id=1040482927 )
Not really sure what is conflicting then

Just make on push to use laravel/nova ^6.5 instead of dev-master. Should work now.

Thanks, it works now :)

Welcome, thanks for letting me know about this.
Proper branch should be available soon.


Support Postgresql sslrootcert option

Proposed functionality
Add the value externalDatabase.sslRootCert, and put it in the configuration.py:
apiVersion: v1
kind: ConfigMap
metadata:
  name: {{ include "common.names.fullname" . }}
  namespace: {{ include "common.names.namespace" . | quote }}
  # [ ... ]
data:
  configuration.py: |-
    {{ .Files.Get "files/configuration.py" | nindent 4 }}

  netbox.yaml: |-
    # [ ... ]

    DATABASE:
      # [ ... ]
      OPTIONS:
        sslmode: {{ .Values.externalDatabase.sslMode | quote }}

        # add the options here
        sslrootcert: {{ .Values.externalDatabase.sslRootCert | quote }}

      # [ ... ]

Maybe the externalDatabase.sslRootCert value could be set to system by default, but it could be a breaking change because by default my container tries to get the CA cert from //.postgresql/root.crt
Use case
When setting the value externalDatabase.sslMode to verify-full, it should be possible to configure the path of the CA bundle (or set it to system to use the system CA bundle)

Thanks for filing this issue, @joachimBurket.
This suggestion seems all right to me.
Would you like to open a pull request?

Maybe the externalDatabase.sslRootCert value could be set to system by default

Let's keep it empty/null for now, and let's NetBox manage its default on its own.

Yes I can give it a try :)


About restful relation data return limit

class Album {
    ......
    public function getPhotos($limit) {
        return (new query())->from('photos')->limit($limit)->all()
    }
}

How to transmit 'limit' param in url?
http://api.example.com/albums/123

you may add limit in query url like  http://api.example.com/albums/123?limit=10

If i will get 10 albums and 5 photos per album. I use http://api.example.com/albums?limit=10&photoLimit=5?
Is not pretty.

Construct custom URL rule like:
    'urlManager' => [
        'enablePrettyUrl' => true,
        'showScriptName' => false,
        'rules' => [
            [
                'pattern' => 'album/<id:\d+>/<photoLimit:\d+>',
                'route' => 'site/album'',
                'defaults' => [
                    'photoLimit' => 5
                ]
            ]
        ]
    ],

currently you can only limit the model used by the ActiveDataProvider,
first of all i would suggest that you do this in the controller level, basically altering what the prepareDataProvider and findModel params of the index action and the view action does.
....
$query->with(['photos' => function ($q) {$q->limit(Yii::$app->request->getQueryParam('photoLimit'))} ])
...

however if i had a choice i would do it like facebook graph API:
GET /albums?expand=photos[limit=5]

@SilverFire Tks
@fernandezekiel Tks, Like facebook graph API
GET /albums?expand=photos[limit=5]

is good O(∩_∩)O

@cebe Can support it
GET /albums?expand=photos[limit=5]

?expand=photos[limit=5] would result in $_GET['expand'] to be ="photos[limit=5]" which you can parse to get what you want.


feat: add math/base/special/minf

Description

What is the purpose of this pull request?

This pull request:

adds math/base/special/minf, which would be the single-precision variant for math/base/special/min.

float stdlib_base_minf( const float x, const float y );

Related Issues

Does this pull request have any related issues?

This pull request:

resolves a part of #649.

Questions

Any questions for reviewers of this pull request?

No.
Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.
Checklist

Please ensure the following tasks are completed before submitting this pull request.

[x] Read, understood, and followed the contributing guidelines.

@stdlib-js/reviewers

Thanks for clarifying this @kgryte! I'll be following these conventions from now on, and will update other open PRs accordingly.


std.math.trigonometry: fix tan asm x86 implementation for ldc compiler

Somehow, separating asm blocks in small pieces produces additional
movs and other instructions on LDC that breaks the tanAsm logic and
therefore returns wrong values.
Signed-off-by: Luís Ferreira<EMAIL_ADDRESS>
CC: @kinke
I'm pretty sure this is not being tested on LDC. I would love to see some coverage reporting for LDC builds. A comparison of DMD and LDC coverage is desired to seek some problems on LDC code generation.
Here's the problem isolated: https://godbolt.org/z/bEhGa1d9P
Here is the asm diff of this change for more context:
--- t1  2021-08-19 19:21:19.595248484 +0100
+++ t2  2021-08-19 19:20:58.704874438 +0100
@@ -5,8 +5,9 @@
         mov     rbp, rsp
         fld     tbyte ptr [rbp + 16]
         fstp    tbyte ptr [rbp - 16]
+        fld     dword ptr [rip + .LCPI0_0]
+        fstp    tbyte ptr [rbp - 32]
         fld     tbyte ptr [rbp - 16]
-        mov     dword ptr [rbp - 20], 0
         fxam
         wait
         fnstsw  ax
@@ -32,41 +33,12 @@
         test    ah, 4
         je      .Lpure nothrow @nogc @trusted real example.tanAsm(real)_Lret
         fstp    st(0)
-
-        jmp     .Lpure nothrow @nogc @trusted real example.tanAsm(real)__llvm_asm_end1
+        fld     tbyte ptr [rbp - 32]
 .Lpure nothrow @nogc @trusted real example.tanAsm(real)_Clear1:
-        mov     dword ptr [rbp - 20], 1
-
-        jmp     .Lpure nothrow @nogc @trusted real example.tanAsm(real)__llvm_asm_end1
+        fstp    st(0)
 .Lpure nothrow @nogc @trusted real example.tanAsm(real)_Lret:
-        mov     dword ptr [rbp - 20], 2
-
-        jmp     .Lpure nothrow @nogc @trusted real example.tanAsm(real)__llvm_asm_end1
-.Lpure nothrow @nogc @trusted real example.tanAsm(real)__llvm_asm_end1:
-
-        mov     eax, dword ptr [rbp - 20]
-        mov     ecx, eax
-        sub     ecx, 1
-        mov     dword ptr [rbp - 24], eax
-        je      .LBB0_1
-        jmp     .LBB0_6
-.LBB0_6:
-        mov     eax, dword ptr [rbp - 24]
-        sub     eax, 2
-        je      .LBB0_2
-        jmp     .LBB0_3
-.LBB0_1:
-        jmp     .LBB0_4
-.LBB0_2:
-        jmp     .LBB0_5
-.LBB0_3:
-        fld     dword ptr [rip + .LCPI0_0]
-        pop     rbp
-        ret
-.LBB0_4:
+        fld     st(0)
         fstp    st(0)
-.LBB0_5:
-        fldz
         pop     rbp
         ret

@@ -180,7 +152,7 @@
 .LBB1_8:
         lea     rsi, [rip + .L.str.4]
         mov     edi, 14
-        mov     edx, 120
+        mov     edx, 117
         call    _d_assert@PLT

 @safe void std.stdio.writeln!(immutable(char)[], real).writeln(immutable(char)[], real):

@kinke meanwhile I found out that declaring rnan as an enum makes the compiler abort abnormally with the following stack trace.
 #0 0x00007fb59b59b793 (/usr/lib/libLLVM-12.so+0xb49793)
 #1 0x00007fb59b598e96 (/usr/lib/libLLVM-12.so+0xb46e96)
 #2 0x00007fb59aa3d870 __restore_rt (/usr/lib/libpthread.so.0+0x13870)
 #3 0x0000562b67d80b47 getIrValue(VarDeclaration*) (/usr/bin/ldc2+0x74bb47)
 #4 0x0000562b67d02509 makeVarDValue(Type*, VarDeclaration*, llvm::Value*) (/usr/bin/ldc2+0x6cd509)
 #5 0x0000562b67d029fd DtoSymbolAddress(Loc const&, Type*, Declaration*) (/usr/bin/ldc2+0x6cd9fd)
 #6 0x0000562b67d5b11a (/usr/bin/ldc2+0x72611a)
 #7 0x0000562b67d51448 toElem(Expression*) (/usr/bin/ldc2+0x71c448)
 #8 0x0000562b67d5b2d0 (/usr/bin/ldc2+0x7262d0)
 #9 0x0000562b67d51448 toElem(Expression*) (/usr/bin/ldc2+0x71c448)
#10 0x0000562b67cd1ab8 AsmStatement_toIR(InlineAsmStatement*, IRState*) (/usr/bin/ldc2+0x69cab8)
#11 0x0000562b67d39dfb Statement_toIR(Statement*, IRState*) (/usr/bin/ldc2+0x704dfb)
#12 0x0000562b67cd33a3 CompoundAsmStatement_toIR(CompoundAsmStatement*, IRState*) (/usr/bin/ldc2+0x69e3a3)
#13 0x0000562b67d3a4e9 (/usr/bin/ldc2+0x7054e9)
#14 0x0000562b67d3a4e9 (/usr/bin/ldc2+0x7054e9)
#15 0x0000562b67d39dfb Statement_toIR(Statement*, IRState*) (/usr/bin/ldc2+0x704dfb)
#16 0x0000562b67cf2584 DtoDefineFunction(FuncDeclaration*, bool) (/usr/bin/ldc2+0x6bd584)
#17 0x0000562b67dc0de0 (/usr/bin/ldc2+0x78bde0)
#18 0x0000562b67dc0de0 (/usr/bin/ldc2+0x78bde0)
#19 0x0000562b67dc0d32 Declaration_codegen(Dsymbol*) (/usr/bin/ldc2+0x78bd32)
#20 0x0000562b67d09772 codegenModule(IRState*, Module*) (/usr/bin/ldc2+0x6d4772)
#21 0x0000562b67dd2f98 ldc::CodeGenerator::emit(Module*) (/usr/bin/ldc2+0x79df98)
#22 0x0000562b67da74d9 codegenModules(Array<Module*>&) (/usr/bin/ldc2+0x7724d9)
#23 0x0000562b67b75d18 mars_mainBody(Param&, Array<char const*>&, Array<char const*>&) (/usr/bin/ldc2+0x540d18)
#24 0x0000562b67da5a02 cppmain() (/usr/bin/ldc2+0x770a02)
#25 0x0000562b67f3be28 _D2rt6dmain212_d_run_main2UAAamPUQgZiZ6runAllMFZv (/usr/bin/ldc2+0x906e28)
#26 0x0000562b67f3bc45 _d_run_main2 (/usr/bin/ldc2+0x906c45)
#27 0x0000562b67f3ba9e _d_run_main (/usr/bin/ldc2+0x906a9e)
#28 0x0000562b67a7784e main (/usr/bin/ldc2+0x44284e)
#29 0x00007fb59a50eb25 __libc_start_main (/usr/lib/libc.so.6+0x27b25)
#30 0x0000562b67a7958e _start (/usr/bin/ldc2+0x44458e)

Needs a test case, i.e. What wrong value? Would also be good to make sure that there is coverage for exactly this implementation rather than just the top level tan

This behaviour is already being tested and the assembly version is being covered, but unfortunately, coverage reporting doesn't work with asm blocks. The unittests fail when the proper environment is set.
AFAIK phobos doesn't run LDC test cases at all so the problem needs to be fixed on the LDC test suite, that's why I tagged @kinke to be aware of this problem.

Needs a test case, i.e. What wrong value? Would also be good to make sure that there is coverage for exactly this implementation rather than just the top level tan

This behaviour is already being tested and the assembly version is being covered, but unfortunately, coverage reporting doesn't work with asm blocks. The unittests fail when the proper environment is set.
AFAIK phobos doesn't run LDC test cases at all so the problem needs to be fixed on the LDC test suite, that's why I tagged @kinke to be aware of this problem.

OK, but what does "fail" mean, does the moon fall out of the sky or does it return wrong values? Nan values?
This would also benefit from a comment in the code noting the change

OK, but what does "fail" mean, does the moon fall out of the sky or does it return wrong values? Nan values?

It returns wrong values on LDC. More precisely, 0 when not fed with infinity.
The point is: this is already being tested. I don't see the point of creating more test cases. The failing point here is not compiling the tests with x87 floating point precision on the LDC test suite. The DMD and official Phobos test suite are fine and cover this but not the LDC ones.

This would also benefit from a comment in the code noting the change

Can you suggest something? I wrote a brief description on the commit body in case someone does a git blame.

I'm pretty sure this is not being tested on LDC.

You're right, what is being tested is LDC's fork of Phobos, which already includes a workaround for this: https://github.com/ldc-developers/phobos/blob/e5258ae22258cf839790d267a281c1237453b3c0/std/math/trigonometry.d#L214-L315

You're right, what is being tested is LDC's fork of Phobos, which already includes a workaround for this<EMAIL_ADDRESS>
Why not upstream these changes?

This is just one of a bunch of std.math adaptations for LDC, see e.g. https://github.com/ldc-developers/phobos/commit/b3efcea59dfa11d752f5df6ba2d6871748dbefc7. This one is a particularly ugly workaround for LDC limitations wrt. DMD-style inline asm; others don't make much too much sense upstream IMO, just uglifying Phobos with LDC specifics (and further if the GDC-specifica would be upstreamed too).

This is just one of a bunch of std.math adaptations for LDC, see e.g. ldc-developers@b3efcea. This one is a particularly ugly workaround for LDC limitations wrt. DMD-style inline asm; others don't make much too much sense upstream IMO, just uglifying Phobos with LDC specifics (and further if the GDC-specifica would be upstreamed too).

There are some things I already fixed here in the upstream, like relying on the runtime function when possible. fabs, log, log10, ... are seen as builtins by the compiler and fallback to the runtime implementation. Other stuff is nasty workarounds that impact the overall coverage of the code.
I'm not totally sure, but those patches seem to lack code review because there are better options to go with. E.g. https://github.com/ldc-developers/phobos/commit/b3efcea59dfa11d752f5df6ba2d6871748dbefc7#diff-b7811717fbf1cc1b4465a9a51fdd2bf5e1ee6cdfe51f3d77deb3943ce0f941daR3394-R3396 this decreases binary compatibility and does not actually follow Phobos. It may compile fine, but not portable when switching binaries at runtime. Another stuff that clearly isn't good is disabling unittests.
These are the type of things that makes LDC adoption more breakable in a production-ready environment, and we all know that everyone uses LDC for release code.
I don't see the problem of including some LDC and GDC specifics in the standard library if they are sane changes. Maintaining three different repositories are not productive in a long run.

I'm not totally sure, but those patches seem to lack code review because there are better options to go with. E.g. ldc-developers@b3efcea#diff-b7811717fbf1cc1b4465a9a51fdd2bf5e1ee6cdfe51f3d77deb3943ce0f941daR3394-R3396 this decreases binary compatibility and does not actually follow Phobos.

Decreases binary compatibility in what way? The signature is identical, are you talking about the pragma(inline) to prevent the costly Phobos trampoline? Unlike DMD, the other compilers have to deal with real likely not being X87 (incl. Windows targets and all non-x86 targets). There are other DMD beauties like https://github.com/ldc-developers/phobos/blob/b3efcea59dfa11d752f5df6ba2d6871748dbefc7/std/math/exponential.d#L3123, implying less precision than most other x87 implementations.
Feel free to try to improve the existing implementations; but note that testing them is a PITA for non-LDC devs like you, as our Phobos fork doesn't have CI, and needs to be tested by opening an LDC PR and advancing the Phobos submodule accordingly.

Decreases binary compatibility in what way? The signature is identical, (...)

https://run.dlang.io/is/CCcCT2
I just realized that those overloads are not part of the official standard library. This should be fixed. This is pretty much enforcing people using real precision when inferred. And this got optimized because either it is a compiler builtin or this code is inlined and end up being optimized.
People that do auto lf = log2(f); think that lf is a float, but it isn't. To enforce this when using type inference the users need to do their own functions.
https://godbolt.org/z/T1h3Y9oqc

(...) are you talking about the pragma(inline) to prevent the costly Phobos trampoline? Unlike DMD, the other compilers have to deal with real likely not being X87 (incl. Windows targets and all non-x86 targets). There are other DMD beauties like<EMAIL_ADDRESS>implying less precision than most other x87 implementations.
Feel free to try to improve the existing implementations; but note that testing them is a PITA for non-LDC devs like you, as our Phobos fork doesn't have CI, and needs to be tested by opening an LDC PR and advancing the Phobos submodule accordingly.

Can we do better? I would love to see more integration with other compilers in the official Phobos test suite, at least for LDC. Most people use LDC for releases and I've seen code breakage for LDC only when compiling with release mode. I think this will not only increase stability but also make D more production-ready, although I understand that the official team doesn't want to mix those implementations, which is unfortunate.

I just realized that those overloads are not part of the official standard library. This should be fixed.

Ah that's what you meant - yes, this is exactly why they are commented out, just waiting for upstream to finally get them. There are multiple issues about this, e.g., https://issues.dlang.org/show_bug.cgi?id=18559 and https://issues.dlang.org/show_bug.cgi?id=19346. I've had a go at a bunch of them a while back (especially those for which there's no LLVM intrinsic), but there sadly hasn't been much movement on that front since then: https://github.com/dlang/phobos/pull/6272

I just realized that those overloads are not part of the official standard library. This should be fixed.

Ah that's what you meant - yes, this is exactly why they are commented out, just waiting for upstream to finally get them. There are multiple issues about this, e.g., issues.dlang.org/show_bug.cgi?id=18559 and issues.dlang.org/show_bug.cgi?id=19346. I've had a go at a bunch of them a while back (especially those for which there's no LLVM intrinsic), but there sadly hasn't been much movement on that front since then: #6272

I can write some overrides for these situations then, but this may introduce a breaking change if there are people relying on the previous overloads.

Anyway, is this good to go? @maxhaton If yes, can you elaborate on the comment suggestion?

I can write some overrides for these situations then,

That'd be great.

but this may introduce a breaking change if there are people relying on the previous overloads.

Breaking changes for a new compiler/druntime/Phobos wouldn't be something new, and good ones like these are warmly welcome, especially if the old behavior can be restored via an explicit cast to real.

I can write some overrides for these situations then,

That'd be great.

but this may introduce a breaking change if there are people relying on the previous overloads.

Breaking changes for a new compiler/druntime/Phobos version wouldn't be something new, and good ones like these are warmly welcome, especially if the old behavior can be restored via an explicit cast to real.

Sure, I'll add this on a separate PR as it is unrelated.

@maxhaton I added a comment describing why I added the additional immutable variable. Is this good to go now? Let me know if anything is still missing.


Error when used inside

So I have this code:
<script lang="ts" setup>
  import { useProfileListQuery } from "@/hooks/useProfiles"

  const { isLoading, data } = useProfileListQuery()

  /* ... */
</script>

And i get the error:
vue-query hooks can only be used inside setup() function

But, I am in a sort-of setup function, aren't I?

Oh it's my mistake, I was already calling a hook on the import, even before useProfileListQuery() was called.


Add an explicit NDK version to RNTester and ReactAndroid

Summary
When I try to run RNTester with Gradle the RNTester Required me to use NDK 20.0.5594570. I can't seem to find an explicit NDK version anywhere in ReactAndroid and RNTester. This PR Aims to add an explicit NDK version to RNTester and ReactAndroid.

Changelog
[Android] [Added] - Add an explicit NDK version to RNTester and ReactAndroid.
Test Plan
Build manually from RNTester

cc @dulmandakh @safaiyeh
@fkgozali what is the NDK version does FB use internally on the RNTester buckconfig?  I used the same version specified on the Gradle template file PR that @safaiyeh worked on.

Actually I have a question about this explicit version specification: https://github.com/facebook/react-native/pull/29403#issuecomment-695362361

what is the NDK version does FB use internally on the RNTester buckconfig?

FB uses a different internal version of the NDK, so it will conflict with the version you specify here, hence my question linked above

Based on https://github.com/facebook/react-native/pull/29403#issuecomment-695821870, I wonder if we can make https://github.com/facebook/react-native/blob/master/ReactAndroid/build.gradle#L249-L271 a little smarter by detecting the version you specify here. If that's possible, that would reduce confusion a lot.
Side note: is there a way to put all these "blessed versions" in one place so that we minimize repetition? E.g. perhaps we could put it in the root project config?

@fkgozali Kindly check I just updated the findNdkBuildFullPath() to only use the explicitly specified NDK. But this means that we will be dropping support for users that install the Android NDK outside of the SDK Manager.
For me, I think this is the best approach, considering that support for ANDROID_NDK_HOME is deprecated and will be removed in the future.

Thanks for the PR @gedeagas! I think in general we should keep this aligned with whatever the currently used version the Android Gradle plugin defaults to, unless there is a specific reason to use a different version.
For AGP versions 3.5 and later, this page states:

(Recommended) Use the ndkVersion property to set the NDK version.

Since React Native is currently using 3.6.4, we would set it to ndkVersion to 20.1.5948944, and update it together with the Android Gradle plugin (#29013). Would that work?

Also, I don't think it should be inside defaultConfig, only directly inside android. Or did you have any issues?

Also (in case I missed it somewhere in the long discussion) - The point of ndkVersion is to not automatically select whatever NDK is installed locally, but to ensure that a specific state of the repository is always built with the same exact tools.

Yes, @friederbluemle, you are correct this pr is to ensure we all use the same version of NDK. And prevent people from using the different NDK version than we already specified on the React NativeGradle template file
We should use the same version of NDK on Gradle or Buck to ensure that a specific state of the repository is always built with the same exact tools.

Hmm looks like this broke the test_android CI? Can you take a look?
https://app.circleci.com/pipelines/github/facebook/react-native/6463/workflows/0393edd6-4185-490b-a1e1-d7366a43fe83/jobs/169076
FAILURE: Build failed with an exception.

* Where:
Build file '/root/react-native/ReactAndroid/build.gradle' line: 251

* What went wrong:
Could not determine the dependencies of task ':ReactAndroid:packageReactNdkLibs'.
> Could not create task ':ReactAndroid:buildReactNdkLib'.
   > NDK is not installed

@fkgozali we probably need to wait for this one https://github.com/facebook/react-native/pull/29050. The Android dockerfile is already being migrated to use Side by Side NDK.
Compile Native Libs is successful
https://app.circleci.com/pipelines/github/facebook/react-native/6480/workflows/d71dd86d-5783-4d2c-b826-26b202a252af/jobs/169292

@gedeagas, @ShikaSD will merge this, but we need to adjust the config slightly to support FB CI.


[Bug] Non-proficient with shields not being triggered

Shields should have the same disadvantages as armor when it comes to non-proficiency.

Armor Proficiency. Anyone can put on a suit of armor or strap a shield to an arm. Only those proficient in the armor's use know how to wear it effectively, however. Your class gives you proficiency with certain types of armor. If you wear armor that you lack proficiency with, you have disadvantage on any ability check, saving throw, or attack roll that involves Strength or Dexterity, and you can't cast spells.

Tested with different shields, and armor.  All armor worked as intended, no shields cause the disadvantage.
Shield Proficiency is obtained from Class Features, or the Moderately Armored feat.
Foundry - 11.315
DnD5e - 3.1.2

Good point. I haven't added Shields in the mix to be honest, cause I didn't think about it.
I will put it in the next release.
Thanks for that.


Admin Area ?

Is there an Admin dashboard that could be used to block or delete accounts that are trolling ?
Thanks

Would that be a democracy?


Improve and modernize the launch/debug/update loop for .NET projects

Summary
The launch, debug, and EnC (Edit and continue) features that exist today, offer developers a way to run their application during the inner-loop along with potentially debugging and even changing their code and have those changes applied to their running application. There are a number of potential opportunities to improve this set of experiences to further their ability to become a more integral part of the inner-loop story.
User Stories & Issues

[x] Support Dev inner loop improvements in .NET Core https://github.com/dotnet/runtime/issues/45629
[ ] EnC: Improving the experience https://github.com/dotnet/roslyn/issues/49001

Closing this out as it pertains to work done in .NET 6.0


Add few global shortcuts for player

https://github.com/atom/electron/blob/master/docs/api/accelerator.md
In electorn, there are some accelerators that we can use to make this player more easy to use. At the first stage, we should support VolumeUp, VolumeDown, VolumeMute, MediaNextTrack, MediaPreviousTrack, MediaStop and MediaPlayPause.

After doing some tests, it would be nice that we don't capture VolumeUp, VolumeDown and VolumeMute directly because this will make users unable to control their global volumes when pressing these keys.


Complete various TODOs in team layout

Problem solved
Short description of the bug fixed or feature added

PR-Codex overview
This PR primarily focuses on enhancing the handling of team images across various components in the dashboard. It updates the src attributes for GradientAvatar and ProjectAvatar components to use the appropriate team images, while also improving the InviteSection button functionality.
Detailed summary

Updated src for GradientAvatar in TeamSelectionUI.tsx to use team.image.
Modified className for Img in ProjectAvatar.tsx to include an additional border-border class.
Changed src for titleAvatarIcon in TeamSettingsSidebar.tsx to use props.team.image.
Updated the Upgrade button in InviteSection.tsx to be a link to billing settings.
Set src for GradientAvatar in TeamHeaderUI.tsx and TeamHeaderMobileUI.tsx to use currentTeam.image.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

#4959  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @MananTank and the rest of your teammates on  Graphite


Extension Manager doesn't update after side-loading VSIX

Azure Data Studio Version: master

Steps to Reproduce:

Side-load a VSIX file using "Install extension from VSIX" command in Extension Manager
Wait for installation to complete

Expected: "Enabled" section of the Extension Manager is update to include newly installed extension
Actual: No updates after "install completed" notification

This is working correctly on the current build.


Improve README.md adding new badges, and link to CFSSL

CI is expected to fail until #1 is merged

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Dario Freddi seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Coverage remained the same at 61.765% when pulling c62e182960476fd51fc3c6d29270368ad2a2df30 on drf:improve-readme into 19f502f9b7f83f42951af9d4a4b62ef64d894de9 on ispirata:master.

@rbino there you go


Adapted the code to Asphalt 5

coverage: 99.026% (-0.2%) from 99.242%
when pulling e745b28ef067f464fabeaec157fb9b23f60b1eb6 on davidbrochart:asphalt5
into 73363d3e5b00cdc892df6fb8ee12122085f26ef7 on asphalt-framework:master.


Adds student research applications charts

Includes:

Doughnut chart for applications count by filing status for semesters and schools
Doughnut chart for applications count viewed and not viewed for semesters and schools
Bar chart for applications count by semester and school
Bar chart for applications count by semester, school and filing status

Completed last corrections and suggestions for the first iteration. Ready for review.


ignore-versions doesn't work

I'm trying to set this action to remove certain packages but I want to keep all semver-correct versions. For instance 1.8.0-develop-312 should be deleted but 1.8.0 should persist.
My action setup is as follows:
package-name: xxx-xxx-xxx
package-type: npm
ignore-versions: '^(0|[1-9]\d*)\.\d+\.\d+(-.+)?$'
min-versions-to-keep: 10

but it keeps deleting all packages.
What am I doing wrong?

same for me, this action is not usable in it's current state

same issue - specific versions that were to be ignored got deleted

I'm getting the same issue as well. This is my job:
      - uses: actions/delete-package-versions@v4
        with:
          ignore-versions: '.*main-ci.*'
          min-versions-to-keep: 5
          package-name: ${{ github.event.repository.name }}
          package-type: container

I've tried '.*main-ci.*' as shown, I've tried 'main-ci', '^main-ci$', etc... it continues to delete that package. It's very frustrating.


Bug: Path bar isn't updating to tabs current path

Description
When changing the tab the pervious tab path will be shown on all of them. There also the tab previews braking which im not sure if there related

Steps To Reproduce

Open some tabs
Go to different paths
Switch between other tabs
See the last loaded tabs path on all tabs

Requirements

Update paths to current tabs directory

Files Version
<IP_ADDRESS>
Windows Version
10.0.22621.2506
Log File
debug.log

@0x5bfa

@0x5bfa I reverted the changes for now, but this should be addressed so that we can merge them back into main.


Run the database migration in same rake task as the deployment to Heroku

It feels more convenient for a developer not to have to run the
database migration each time he needs to do a deployment.
For this reason, I am including the migration task within the deployment
task.
As a side note, I had to add the Bundler.with_clean_env to run the
migrations because Heroku was picking up the wrong version of ruby.
See suggested solution in StackOverflow1 and explanation in:

How do heroku database migrations work if you (I mean me) run the app in the Development VM, but deploy to heroku from my base mac?
Do I need to do anything extra? Would it be better if I installed the heroku client in my VM?

The migration process runs in Heroku, so the quick answer is that it is not relevant from where you are running the command.

@chao-xian I have updated the link. Thank you 👍
I am force-pushing now in preparation for merging.


For MNIST, NormLayer is giving incorrect results

I'm tying to implement MNIST Network using ARM ComputeLibrary. Layers in MNIST are in folllowing order.
InputLayer
ConvLayer
MaxpoolingLayer
ConvLayer
MaxpoolingLayer
FCLayer
ReLULayer
NormLayer
FCLayer
SoftmaxLayer
OutputLayer
The NormLayer takes input from the ReLU layer. But the NormLayer output mismatches with the expected result.  I've attached the stand alone  test setup for NormLayer , NormLayer Input, NormLayer output,  NormLayer expected output.
normExpected.txt
normInput.txt
normOutput.txt
normTestsetup.txt
Could you take a look into this and let us know if you face the same error or are we missing anything here?
Note: We have used the latest armcompute library.
Thanks in advance.

Is there any update on this ?

Hello @nhkrishna,
I added your shapes as a test case in our internal testing and we didn't see any failures.
First looking at your code you don't need two src tensors.
Use a single one and pass it to configure. Then allocate src and use copy_n or memcpy to copy 500 elements only to you src tensor from your relu buffer. The starting position to copy inside your src tensor should be:
src->info()->buffer() + src->info()->offset_first_element_in_bytes
Hope this helps.
If it still fails post the update code here as a comment

Hello @GeorgeARM,
We have changed the wrapper as per your suggestion and we are still seeing the same issue . We 've attached the wrapper for your reference.
We are running this setup on rpi 3. Could you let us know on which platform did you run and share us your test setup or make commands. Could you let us know whether the norm outputs that you have got are matching with the values in normExpected.txt.
normTestsetup.txt
Thanks,

Hi @nhkrishna
I've reproduced your example using the value you provided and I got the same results, so you should not be doing anything wrong.
Could you please tell us where you got these "expected" result values from, in order to understand whether this is actually a bug or not?!
Thanks

When I say expected results, I mean the results that I have obtained for MNIST using CuDNN library on Nvidia GPU. These results also match with Intel MKL-DNN  library on a desktop and both are working fine for MNIST Network. But, with ARM ComputeLibrary I am getting mismatch in results at NormLayer output as compared to these libraries.

Hello @nhkrishna,
I think that the problem is in the model you have defined or a mismatch of how we interpret the FullyConnectedLayer.
If in your example change the shape to TensorShape(1U, 1U, 500U) you will get the correct result.
What you are doing now is performing cross map LRN is a row vector which from the expected results isn't what you want.

Hello @GeorgeARM ,
I've changed the shapes of both src and dest tensors to TensorShape(1U, 1U, 500U)  in my test file. But still i'm seeing the wrong result. I've attached the modified testfile and its output for your reference.
normTestSetup.txt
normOutput_io.txt
If you got the correct result,  Let me know the test file that you have written .
Thanks

@nhkrishna you cannot use memcpy anymore to fill your tensor, thus use a window loop instead.
Now the NormLayer function will add padding spatially as it process 4 elements across width each time and your width is 1, thus it should add a padding of 3.

Hello @GeorgeARM ,
Finally i got the correct results. But, after configure sizes of src and dst tensor are increased to 8000 and 2000 respectively. We know that embedded devices have some  memory constraints. So, if sizes are increasing in this way embedded application will consumes lot of memory.
Is there any idea to retain the sizes of  src and dst tensors after configure.
Thanks

Hello @nhkrishna,
Yes it will increase your size. What you could do probably is to think it the other way around.
Meaning you could leave your shape as TensorShape(500U) and do an IN_MAP normalization with the same parameters. This shouldn't add much padding. Give it a try.

Closing this issue. Reopen if needed.


Add support for multi-gpu rendering

What type of PR is this? (check all applicable)

[ ] Refactor
[X] Feature
[ ] Bug Fix
[ ] Optimization
[ ] Documentation Update
[ ] Community Node Submission

Have you discussed this change with the InvokeAI team?

[X] Yes - a long time ago
[ ] No, because:

Have you updated all relevant documentation?

[ ] Yes
[X] No

Description
This PR adds speculative support for parallel rendering across multiple GPUs.

The model loader has been enhanced to keep track of all the CUDA GPUs available. When the loader is asked to load a model into VRAM, the first unused CUDA device is selected. If all CUDA devices are available, the loader will block until a timeout is reached. There is no support for multiple CPU or MPS devices right now.
The model manager now has an attribute called gpu_count which provides the number of GPU devices potentially available.
In invokeai/app/services/invocation_processor/invocation_processor_default.py, I upped the __thread_limit semaphore to the number of GPUs known to the model manager. I think this will cause up to gpu_count processing threads to be started.

The intended effect is to speed up batch image generation by allowing up to N workflows execute in parallel, where N is the number of GPUs on the user's system. There will be no effect on the speed of individual image renders, but an overall increase when you are running a batch of them.
The code is untested at the current time, and I imagine that some new locking code must be placed in DefaultInvocationProcessor in order to make it thread safe.
Related Tickets & Documents

Related Issue #4745
Closes #

QA Instructions, Screenshots, Recordings
This needs a multi-GPU system to test. I'm in the process of gaining access to one.

Merge Plan
This PR is in draft state. Do not merge.

Added/updated tests?

[ ] Yes
[ ] No : please replace this line with details on why tests
have not been included

[optional] Are there any post deployment tasks we need to perform?

We might find that more folks are in need of batch size support over needing multi-gpu orchestration. This would add a fair bit of complexity into the session processing logic and UX would it not?

We might find that more folks are in need of batch size support over needing multi-gpu orchestration. This would add a fair bit of complexity into the session processing logic and UX would it not?

I think batching requires a pretty fundamental reorganization of how the denoise latents node works. It would have an arbitrary number of conditioned/unconditioned prompt inputs, passes a list of latents to the vae decoder, and then the vae would produce an arbitrary number of images for further processing.

Seems reasonable for the intended functionality.
Comment copied from #5737:

I am thinking about how to implement multi-GPU support for parallel rendering. The current idea is to do this at the ModelManager level, where the manager provides a semaphore that tracks the number of GPUs that are currently free. The model locker would be modified so that when the caller requests that a model be moved into the rendering device (e.g. CUDA) it picks an unused GPU and/or blocks until one is released and available.
Under this scenario, you would want to acquire the semaphore and keep dequeue and executing sessions until the semaphore blocks. Would it be better to start multiple _process() threads here, or put that logic in the body of _process()?
Another issue is that not all sessions will need access to the GPU. So maybe there is a way of distinguishing those that do from those that don't?

If nodes could report if they need GPU or only CPU, we could parallelize both CPU and GPU at the node or workflow level. I think it's safe to assume the vast majority of workflows will require GPU, so parallelizing at the node level might be more impactful.
We could allocate 1 GPU per workflow, but in the processor, we can a parallelize CPU-only nodes. That said, CPU-only tasks are mostly not a performance bottleneck. For example, executing 20 add integer nodes in synchronously may be much faster than distributing that work across however many threads. The overhead of creating a thread might dwarf the boost from parallel node processing.
This is definitely outside my comfort zone - just thinking out loud.

superseded


OCM-ify Sockshop

Description
Sock Shop is a polyglot micro-services application created by Wevaeworks for demonstration purposes.
For reInvent we should model it using OCM. Sock Shop should be modelled by creating a single root descriptor which contains references to dedicated descriptors for each micro-service.
The Component Descriptor for each micro-service should contain the following resources at a minimum:

the manifests / Helm charts required to deploy the service
the images required to deploy the service
a ConfigData manifest (see below) that can be used to configure and localize the service

ConfigData
apiVersion: config.ocm.software/v1alpha1
kind: ConfigData
metadata:
  name: ocm-config
  labels:
    env: test
configuration:
- target:
      name: manifests # the resource to target  defaults:
    color: red
    message: Hello, world!
  schema:
    type: object
    additionalProperties: false
    properties:
      namespace:
        type: string
      color:
        type: string
      message:
        type: string
  rules:
  - value: (( color ))
    file: configmap.yaml
    path: data.PODINFO_UI_COLOR
  - value: (( message ))
    file: configmap.yaml
    path: data.PODINFO_UI_MESSAGE
localization:
- target:
      name: manifests # the resource to target
  rules:
  - resource:
      name: podinfo
    file: deploy.yaml
    image: spec.template.spec.containers[0].image

note: There is some prior art here: https://github.com/gardener/landscaper-examples/tree/master/sock-shop/many-components.

Add configuration parameters for customize front-end

^ This subtask is done thanks to MVPs @AlinaGoaga & @foot! 💟
The background colour of sockshop's FE can be changed to any colour by setting an env var e.g. COLOUR=ff0000 to make it red:

Next step is to figure out where to push the image & how to access the UI for the demo


Removed eventhub and service bus migration guide from toc

Docs Build status updates of commit 4483fbc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/azps-8.2.0/toc.yml
:white_check_mark:Succeeded
View (azps-8.2.0)

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


ajax page search

when i loading a small amount of data  first page, and the scroll bar does not appear.  and then second page data not load.

Duplicate of https://github.com/select2/select2/issues/3088.


Q&M: Fix broken links identified by the Broken links report - 3

Per task: https://dev.azure.com/msft-skilling/Content/_workitems/edit/335393/?view=edit.
I've fixed some broken links.

@dotnet-policy-service agree company="Microsoft"

@cmastr, @Rick-Anderson, @wadepickett, @tdykstra, I've fixed some broken links, please verify. Thanks.


There is a problem in the agent configuration of tomcat 8 in quick start document.

linux 环境下，tomcat 7和tomcat8的探针配置应该是一样的，文档中tomcat8的配置应该是windows系统的配置
路径：incubator-skywalking/docs/en/Deploy-skywalking-agent.md

You can fix these things for the community. We are always welcome your contributions.


what's the best practice to write a parser for speech recognition results ?

i want to create a smiple parser for speech recognition results ,the grammar going to be complex that's why i want some advices about how to deal with complex grammar .
i have this simple example below using speech recognition api and lark parser    :
from lark import Lark,Token, Transformer, v_args
from helpers.file_process import FileProcess
import numpy as np

speech_grammar = """
start              : KEY TYPE FNAME PATH?
KEY                : "create" | "delete" | "open" | "read" | "make"
TYPE               : "file" | "folder"
FNAME              : (/[a-z]/)+
PATH               : (/[a-zA-Z]/)+":"(/[\\/]/)+DIRNAME
DIRNAME            : ((/[a-zA-Z0-9]/)+(/[\\/]/)?)*

%ignore (" ")+
"""

speech_parser = Lark(speech_grammar)

def run(input):
    try:
        speech = speech_parser.parse(input)
        instr=np.array(speech.children)
        return FileProcess(instr).request_process()
    except Exception as err :
        return err

def main(input):
    return run(input)

def test():
    print(run("make file test d:/test"))
    print(run("delete file test"))

i will add more terminals (Vt) in the grammar part , any suggestions or advices  would be much appreciated ?

Can you give us an idea of speech recognition results?

for a word or phrase that has been positively recognized by speech recognition api and this has been communicated back to the app as a set of words  , when i say  " create file test" the api will return :
{ token : KEY , value : create , token : type , value : file, token : fname, value : tes t}

It's not going to be nested, right? If not, that's not too hard!
Try to play around with the grammar until you can get it to parse. The documentation for making a JSON parser can probably help.

yes that's right but if you look at the PATH (Vn) in the grammar! , imagine when you say " CREATE FILE TEST" plus the path where the file will be created , how to make api understood file path then i can use it for lark parsing?

I'm kind of confused... can show you me what happens when you tried that? (We can only parse what the API gives)

the grammar describe how users interact with speech api , we can't use "create file test d:/myfolder" like that because the api doesn't understand the path and it doesn't have the concatenation between each path item, is there any way to make it easier to understand and use for speech api?

It sounds like you're asking about the lingual interface, rather than parsing.
Maybe if you provide some examples of the output you're getting (or hoping to get) from the voice API, we can tell you how to parse it.
I would suggest considering a "DSL" for the paths that's more natural for speaking, like "drive d folder myfolder"

path_dsl that's what i'm looking for , thank you so much @erezsh @ThatXliner


[FEATURE REQ] Support uploading gzip for ingestion

Currently, a list of logs is supported which is later gzipped.
It's not ideal that if the user has a gzipped file, they'd have to unzip it , upload it as a list and the we re-zip it again.

This can be done with the existing code today. Here is a quickly wriiten sample method which does this
private void uploadGzippedLogs(String ruleId, String streamName, InputStream gZipContent) {
        //Get gZip content
        final byte[] content;
        try {
             content = gZipContent.readAllBytes();
        } catch (IOException e) {
            // Handle IO exception
            throw new RuntimeException("Reading gzip content failed.", e);
        }

        RequestOptions requestOptions = new RequestOptions();
        requestOptions.setHeader("Content-Encoding", "gzip");
        requestOptions.setBody(BinaryData.fromBytes(content));
        byte[] dummyBuffer = new byte[0];

        Response<Void> response = uploadWithResponse(ruleId, streamName, BinaryData.fromBytes(dummyBuffer), requestOptions).block();
        assert 200 == Objects.requireNonNull(response).getStatusCode();
    }


Cannot negate boolean queries with False

I would like to construct a query with negations, such as finding messages which are NOT starred.
construct_query takes in a dictionary that supports various boolean labels, but setting them to False does not add the negation operator (-).
Actual:
>>> construct_query({"starred": True})
'is:starred'

>>> construct_query({"starred": False})
'is:starred'

>>> construct_query({
    "starred": False,
    "snoozed": False,
    "unread": False,
    "important": False,
    "attachment": False,
    "drive": False,
    "docs": False,
    "sheets": False,
    "slides": False
})
'(is:starred is:snoozed is:unread is:important has:attachment has:drive has:document has:spreadsheet has:presentation)'

Expected:
>>> construct_query({"starred": True})
'is:starred'

>>> construct_query({"starred": False})
'-is:starred'

>>> construct_query({
    "starred": False,
    "snoozed": False,
    "unread": False,
    "important": False,
    "attachment": False,
    "drive": False,
    "docs": False,
    "sheets": False,
    "slides": False
})
'(-is:starred -is:snoozed -is:unread -is:important -has:attachment -has:drive -has:document -has:spreadsheet -has:presentation)'

As a workaround for now, you can compose these queries manually, ie
construct_query({"exact_phrase": "-is:starred"})
This does add quotes to the query string ("-is:starred" vs -is:starred) but Gmail doesn't seem to mind.


add TRIVY_JAVA_DB_REPOSITORY to trivy configmap

Description
Related issues

Close #2271

Remove this section if you don't have related PRs.
Checklist

[x] I've read the guidelines for contributing to this repository.
[ ] I've added tests that prove my fix is effective or that my feature works.
[ ] I've updated the documentation with the relevant information (if needed).
[ ] I've added usage information (if the PR introduces new options)
[ ] I've included a "before" and "after" example to the description (if the PR is a user interface change).

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.dlouzado seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


can't connect real robot(RS007l)

hello.
I try to connect rs007l and F60 controller to ros
So, referring to the ConnectingRealRobot.md file, I connected the Ethernet cable to the pc and controller.
And I ran roslaunch khi_robot_bringup rs013n_bringup.launch ip:=<IP_ADDRESS>
But I got this error message
auxapi_login error ret=-8200
asapi_connect error ret=-4099
[ERROR] [1712824106.423495507]: [KhiRobotKrnxDriver] krnx_Open returned -0x1003
[ INFO] [1712824106.423616006]: [KhiRobotKrnxDriver] State 0: CONNECTING -> INIT
[ERROR] [1712824106.423767172]: Failed to open KHI robot
[ INFO] [1712824106.423895855]: [KhiRobotKrnxDriver] State 0: INIT -> DISCONNECTING
[ERROR] [1712824106.424007162]: [KhiRobotKrnxDriver] krnx_Close returned -0x2000
[ INFO] [1712824106.424089355]: [KhiRobotKrnxDriver] destructor
[ERROR] [1712824106.424166824]: [KhiRobotKrnxDriver] krnx_Close returned -0x2000
[ INFO] [1712824106.424244112]: [KhiRobotKrnxDriver] destructor
[khi_robot_control-2] process has died [pid 9677, exit code -11

and i try ping <IP_ADDRESS>
It works correctly
Can you please help me solve this problem?
[ROBOT and PC version]
os: ubuntu20.04
ros: noetic
robot name: rs007l-A001
controller: F60
AS version: ASF_01000001A (Is this version higher than ASF_01000000W??)
thank you.

Hi @elripunt,

And I ran roslaunch khi_robot_bringup rs013n_bringup.launch ip:=<IP_ADDRESS>

When you want to connect to rs007l, plsease run rs007l_bringup.launch. (Not  rs013n_bringup.launch)
If the error still occurs, could you check for connectivity by ping?

sorry i try roslaunch khi_robot_bringup rs007l_bringup.launch ip:=<IP_ADDRESS>  not rs013n
and i try again  rs007l_bringup.launch but it's the same error message
so I checked with this command ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data. 64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=0.065 ms 64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=64 time=0.060 ms 64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=64 time=0.074 ms 64 bytes from <IP_ADDRESS>: icmp_seq=4 ttl=64 time=0.063 ms 64 bytes from <IP_ADDRESS>: icmp_seq=5 ttl=64 time=0.064 ms 64 bytes from <IP_ADDRESS>: icmp_seq=6 ttl=64 time=0.062 ms 64 bytes from <IP_ADDRESS>: icmp_seq=7 ttl=64 time=0.080 ms 64 bytes from <IP_ADDRESS>: icmp_seq=8 ttl=64 time=0.063 ms 64 bytes from <IP_ADDRESS>: icmp_seq=9 ttl=64 time=0.064 ms 64 bytes from <IP_ADDRESS>: icmp_seq=10 ttl=64 time=0.055 ms 64 bytes from <IP_ADDRESS>: icmp_seq=11 ttl=64 time=0.080 ms 64 bytes from <IP_ADDRESS>: icmp_seq=12 ttl=64 time=0.066 ms 64 bytes from <IP_ADDRESS>: icmp_seq=13 ttl=64 time=0.064 ms 64 bytes from <IP_ADDRESS>: icmp_seq=14 ttl=64 time=0.069 ms

pc and the controller's ip should not be set the same
It's my mistake
Thank you!


Drain connections + graceful shutdown

Type of PR

[ ] Documentation changes
[x] Code changes
[ ] Test changes
[ ] CI-CD changes
[ ] GitHub Template changes

Purpose of PR
When the app is terminated, ensure that the existing connections will be processed by the server (up to 20s) and any new connections will be dropped (graceful shutdown).
Validation

[ ] Unit tests updated and ran successfully
[x] Update documentation or issue referenced above

Issues Closed or Referenced

References https://github.com/retaildevcrews/helium/issues/383

Going to block this PR for the time being since it'll be better if https://github.com/retaildevcrews/helium-java/pull/298 gets merged in first.

Going to block this PR for the time being since it'll be better if #298 gets merged in first.

We're good to unblock, just merged referenced PR :)


Refactor things into separate files

Splitting things out inside separate files. Seems like encode + decode is around 2*100 + a bit. Not too bad :)
Also did a tiny var => const refactor while I was at it.
I have tested this doing full queries on an empty database and performance is the same as before.

I have been working on cleaning up BIPF to make it easier for other people to implement as its now used in [buttwoo]. The easiest way to review this is by commit. I tried to not change very much other than splitting things up and minor cleanups (const, let, consistent naming).

Much appreciated the commit-by-commit approach. Great refactor!


json:1: unexpected symbol near '{'

I try to use itorch in MSYS2 on Win7 64bits.
$ /e/prg/py/Anaconda3_64/Scripts/ipython notebook   --MappingKernelManager.default_kernel_name="itorch"
...

e:/prg/lua/torch/bin/itorch_launcher: ...runtime\kernel-79533033-f912-4fc5-9407-6a0b6cc11775.json:1: unexpected symbol near '{'

but I can't find any bug in the json file. So what is the problem? Thanks
{
  "iopub_port": 8346,
  "ip": "<IP_ADDRESS>",
  "stdin_port": 8347,
  "signature_scheme": "hmac-sha256",
  "shell_port": 8345,
  "hb_port": 8349,
  "control_port": 8348,
  "key": "c4ca1303-8387-4cdd-9a24-942b8a5c4518",
  "kernel_name": "itorch",
  "transport": "tcp"
}

well, it seems that itorch is abandoned


Docker container up locking + Unix/Ubuntu support fixed

corresponding PR in multi
https://github.com/Cognifide/gradle-aem-multi/pull/101/files
TODO maybe it is possible to determine that IP automatically

progress loggers related with locking to be hidden... but merging to develop as it will be base for 9.1.0 / @mierzwid please continue work by merging it via merging develop to your branch(es) to warm up this feature


Use Azure Key Vault secrets in Azure Pipelines page doesn't show how to reference secrets

The example pipeline has a step called "CmdLine" that echos the secret to a file, but that step is never defined on the page. The pipeline creation instructions only include the key vault step but after saving, two more steps called CmdLine and PublishPipelineArtifact have appeared out of nowhere.
After reading this page I still don't know how to reference secrets in the pipeline after the key vault step. I can only assume they are converted to variables, and maybe environment variables too. Do I have to also add output variables to the key vault job or does it add everything matching the "Secrets filter"? Is the CmdLine step running echo $(mysecretpassword) > secret.txt or something else?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f5346b3b-4c62-c343-4b02-92cd891395d8
Version Independent ID: 8ff89836-ebf2-7a58-542e-c5d91ff38df6
Content: Use Azure Key Vault secrets in Azure Pipelines - Azure Pipelines
Content Source: docs/pipelines/release/azure-key-vault.md
Product: devops
Technology: devops-cicd-release
GitHub Login: @ramiMSFT
Microsoft Alias: rabououn

This is the same issue as #10610 and #10372


Return Error::Finished in recv() on graceful close.

This PR depends on #350.
This allows applications to distinguish whether the remote end has
gracefully closed the connection with a FIN (in which case it has
received all the data intact), or the connection has failed due to e.g. a
RST or a timeout (in which case the received data may be truncated).
Fixes #349

Added documentation and rebased.