Builds for android for python

Hello, tell me how to assemble, or maybe use ready? libtdjson.so works great on linux, but does not work on android ""/home/kivy/4/.buildozer/android/platform/python-for-android/build/python-install/lib/python2.7/ctypes/init.py", line 356, in init
OSError: dlopen failed: "/data/data/org.bte.bte/files/lib/libtdjson.so" is 64-bit instead of 32-bit"
libtdjni.so error "" /home/kivy/4/.buildozer/android/platform/python-for-android/build/python-install/lib/python2.7/ctypes/init.py ", line 374, in getitem
AttributeError: undefined symbol: td_json_client_create "
Well, it's understandable, these functions are not there, And written for java.
Or should libtdjson.so be built for Android?
I want to use in the project on Kivy.
And there is ready assembled libtdjson.so for Android?

libtdjson.so should be built using Android NDK to be used on Android. Prebuilt Android library provides only JNI interface, so if you want JSON to use JSON interface, you need to build it manually. It is definitely possible, but you will likely need to write a small CMakeLists.txt file for Android Studio like described in https://developer.android.com/studio/projects/configure-cmake. You will also need to first build OpenSSL for Android.

Thank.
JNI interface, did not find a description of the methods?
createNativeClient
Client_createNativeClient
in the example that are missing in the assembled library.
"AttributeError: undefined symbol:"
Or am I looking there?

This is already understood, thank you.
So I will try to collect JSON.
Although not sure what happens.
Thank you

For iOS, there is an example of an assembly, maybe for Android, post an example of an assembly libtdjson?

We may add such example in a future along with example of building Java interface for Android, but given existence of prebuilt Android Java binaries, it is not a priority.

This is already understood, thank you.
So I will try to collect JSON.
Although not sure if I can do it.
Thank you

I'm trying to build for android, using JSON c++ interface, but still can not build through Cmake. If you can build for android, please give me some instruction, thank you very much!

Now you can use the Android example to build TDLib with JSON interface for Android.


Github actions mypy build check fails when python 3.9 typing is used

Describe the bug
When the inbuilt type notation introduced in python 3.9 (e.g. list[str]) is used, the<EMAIL_ADDRESS>fails the mypy build check. This is despite it passing the pre-commit hook locally.
To Reproduce
Steps to reproduce the behavior:

Add a type hint which indexes a collection type (e.g. list[str] or tuple[int]) to existing code
Commit this code
If it passes the pre-commit hooks push the code
The GitHub actions build check should fail with a message similar to error: "list" is not subscriptable, use "typing.List" instead

Expected behavior
The mypy build check should pass as we have set our supported python to be >=3.9.
Desktop (please complete the following information):

OS: macOS
Version 12.5.1

I think we just need to add a python-version section to the qa job

Yeah - the ubuntu-latest is Ubuntu 20.04, which includes Python 3.8, so that is what is being used:
https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#:~:text=In 20.04 LTS%2C the python,base system is Python 3.8.

OK, so I think we'll just need to add an extra step:
    - uses: actions/setup-python@v4
      with:
        python-version: "3.9"

I think it makes sense to just use the lowest version we want to support.


Documentation Issue

I am  a beginner in react framework so that makes me new to JavaScript. I am trying to use an accordion menu for my hospital project and I was excited to find your component but there is an issue of documentation for me. I need to know how to create main menu and submenu and also I could not get any look and feel so if I can a component tree like what you have on this page. I know you mite not understand what I am saying but if  you can give me as a beginner exposure to you library. I found this site https://ivp-dev.github.io/react-bootstrap-sidebar-menu/ but still could not understand any thing. If you can, give little time and give me an exposure.

This module is broken so better not use it for now , and to make it work you need to drilldown into demo source code. not recommended for beginners.


Add required headers and parameter checks

For example media types requirements
The easiest way to meet the spec is to replicate the trait

i think to use the middleware instead of trait method because this repository is special to jsonapi.

It requires the app sending raw objects rather than Responses. Would it be natural to phalcon users?

Does the library send PHP object?
i thought it sends raw JSON

Middleware is something between the app and the user. The following image shows them as yellow circles

If data conversion is placed in middleware it will require the app to send objects/arrays/iterators and the middleware will convert them to Responses with json. Are you planning to make such middleware?

The phalcon it self returning raw Phalcon\Http\Response object see the docs and my latest code [line#44](https://github.com/sumeko/phalcon-jsonapi/blob/master/routes.php #L44).
anyway, is there any better way?

@sumeko If you plan to implement this approach
return $app->encoder->encode(Comment::find());

it might be design issue. Users actually send desired format with Accept header and it could be like this
text/plain; q=0.5, text/html, text/x-dvi; q=0.8, text/x-c

When you return just text (json, xml, html) and then in middleware add headers you can't know actual data type.
Headers needs to be analyzed and when you convert data you need to know the requested type.
Also have a look at Location header requirement. With this approach it can't be implemented as you loose this info after returning json text.

shortly it's better to return Response with correct body, code and headers and it should have requested format

Oh i see,
Phalcon has before middleware event to analyze the request headers, so i think it still ok to use middleware.
but i will implement the trait method also

IMHO it could be trait or controller or some helper class. Choose what is natural for phalcon community.
My most concern is filling correct Response.

@neomerx
How to just return array instead of json with the lib?

inherit/extend Encoder and override encodeToJson method

how is it going? is anything to look at?

I'm on vacation this week.. see ya later

Super. Have a good time :wink:


Support for external chaincode builders

Add support to be able to run external builders.
This is following the model of https://github.com/hyperledgendary/fabric-builders/blob/master/builders/external/README.md
To run in this manner:
Start microfab as normal, but ensure that it is attached to a known docker network
Create a connection.json file and package in a tgz as per normal chaincodes (see the notes above)
Install the tgz
Start the docker container with the chaincode as per the connection.json (on the same network)
Approve and Commit the chaincode as normal.

Think this is done 👍


Searched for and proposed relation property candidates miss their labels

When a property is proposed or search for its label is not displayed in the candidates list.

@KataBoku @JanVana As even the server struggles to provide the labels for relation during the initial run, this might be postponed to the 5th iteration.


Full Monero public address not displaying on Ledger.

First of all thank you for all of your efforts. I am glad XMR can be protected on a hardware device now.
I have two Monero wallets on the ledger. One with pass phrase and one without.
The Monero wallet attached to pin with 24 seed, no pass phrase does not display the ENTIRE public address on the ledger.
It displays and scrolls about 60 percent of it and then scrolls back.
The second wallet with pass phrase however displays the entire public address.
Bug seems entirely cosmetic as everything appears functional when interacting with blockchain.
The address displayed is correct it just doesn’t display ALL of it.
I hope this can help please let me know if I can clarify any details.

Confirmed.
It will be fixed shortly after the release 1.0.0 of the app

I have the same issue (on v1.0.0 of the app), but for me it doesn't even scroll past the first 11 characters.
(The 11th character shows a pixel stretch effect before it returns scrolling back again).
And it's also not on the wallet attached to the 24 seed, but attached to a 24 + passphrase seed.
I tried other 24 + passphrase seeds and it scrolls all the way for them, as well as for the 24 seed only.
It just happens to not scroll all the way on the 24 + passphrase seed that I actually use.
Just my luck.^^

It will be fixed shortly

Skeleton waiting.

I know time is relative but I'd really like to be able to see my entire address on the ledger display. A status update would be nice...thanks a bunch for the work on the ledger app!

Hey @cslashm
My Ledger Nano S is updated to firmware v1.5.5 and Monero app v1.1.2
Unfortunately I still have the problem (like the OP originally mentioned) that my public address is not scrolling through completely. It appears to stop scrolling after some characters.
This only happens with a specific passphrase.
If I only use the seed or use another passphrase then the address scrolls through without any problems.
I guess it only seems to affect certain addresses or seed+passphrase combinations?
I'm happy to provide you with any logs or settings, just tell me what you need and I'll oblige. :)

Just wanted to report that with the Monero app v1.1.3 I (obviously) don't have the scrolling problem anymore. :)

@Mansarde  1.1.2 and 1.1.3 are only available on 1.5.5 firmware
no more scroll! Press both button on your pub address to show the full address.

Oh, I saw the abbreviated address, but didn't know about the double-press for showing the whole address.
Just tried it and it works without problems, yay!
Many thanks! :D


Database deployment (dotnet publish) failes - An error occurred during deployment plan generation. Deployment cannot continue.  error MSB3073. Exit code -1.

I have a very simple SSDT project (contains one table) created in VS 2019 (16.4.4) and .NET standard Class Library project using MSBuild.Sdk.SqlProj.
<Project Sdk="MSBuild.Sdk.SqlProj/1.6.0">
  <PropertyGroup>
    <TargetFramework>netstandard2.0</TargetFramework>
  </PropertyGroup>
  <ItemGroup>
    <Content Include="..\MyPlayground\dbo\**\*.sql" />
  </ItemGroup>
</Project>

dotnet build is executed successfully but dotnet publish (publishing on SQL Server 14) fails with the following error:
EXEC : error : Deployment of database 'MyPlayground' failed: An error occurred during deployment plan generation. Deployment cannot continue. [C:\Users\XXX\workspace\Node\sb3-rest-api\sql\SSDT\Playground.Build\Playground.Build.csproj]
C:\Users\XXX\.nuget\packages\msbuild.sdk.sqlproj\1.6.0\Sdk\Sdk.targets(191,5): error MSB3073: The command "dotnet "C:\Users\XXX\.nuget\packages\msbuild.sdk.sqlproj\1.6.0\Sdk\../tools/netcoreapp3.1/DacpacTool.dll" deploy -i "C:\Users\XXX\workspace\Node\sb3-rest-api\sql\SSDT\Playground.Build\bin\Debug\netstandard2.0\/Playground.Build.dacpac" -tsn "localhost\SQLSERVER" -tdn "MyPlayground" -tu "user" -tp "password" -p IncludeCompositeObjects=true " exited with code -1. [C:\Users\XXX\workspace\Node\sb3-rest-api\sql\SSDT\Playground.Build\Playground.Build.csproj]

Please could you help me how can I publish my project?

Solved - database version was required: <SqlServerVersion>Sql140</SqlServerVersion>

@Fenix-Z Glad you found the issue. I would recommend updating to a newer version (1.11.4 is the latest right now) which has some improved diagnostics that should make it easier to diagnose issues.


Add tests for invalid schema

Add tests to verify ANCM handles invalid schema gracefully (e.g. https://github.com/aspnet/IISIntegration/pull/989).  May be easiest to test with containers.

Not completely invalid, just old versions of it.


Improve some tests

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (63aaf6f) to head (a06fedb).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #414   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          119       119
  Lines         3499      3499
  Branches       281       281
=========================================
  Hits          3499      3499

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests


ignore: merge a real commit into a separate test branch for dispatch testing

By merging into dispatch-to-brim, I can test whether a new workflow on dispatch-to-brim will see the merge event and send the PR metadata to Brim.


Update regexes.pod

I found a small typo: staring -> starting

Thanks!

You're welcome.
It's my first contribution to a project on GitHub, so I hope I did everything as I'm supposed to.

Perfectly ... :-)
Am 14. Februar 2016 17:38:25 MEZ, schrieb Eric de Hont<EMAIL_ADDRESS>
You're welcome.
It's my first contribution to a project on GitHub, so I hope I did
everything as I'm supposed to.

Reply to this email directly or view it on GitHub:
https://github.com/perl6/doc/pull/395#issuecomment-183918257

--
Fritz Zaucker
Oetiker+Partner AG
Aarweg 15
CH-4600 Olten
+41 62 775 9903

In that case, expect more pull requests ;-)

@edehont or accept the invitation I just sent you, and push directly :-)

Nice, thanks!
I have accepted, of course.
Eric de Hont
Op 15-02-16 om 13:27 schreef Moritz Lenz:

@edehont https://github.com/edehont or accept the invitation I just
sent you, and push directly :-)
—
Reply to this email directly or view it on GitHub
https://github.com/perl6/doc/pull/395#issuecomment-184186351.


added bower install instruction to installation

Needed to run the 'bower install' to install breakpoint-sass

thanks!


Cannot start uploading process

Describe the bug
I cannot click button "upload and run workflow"
To Reproduce

Expected behavior
click the button and start workflow.
Please complete the following information about the solution:

[ ] Version: v2.1.2

(SO0164) Content Localization on AWS v2.1.2

[ ] Region: [e.g. ap-northeast-2]

[ ] Was the solution modified from the version published on this repository? No

[ ] If the answer to the previous question was yes, are the changes available on GitHub?

[ ] Have you checked your service quotas for the sevices this solution uses? Yes

[ ] Were there any errors in the CloudWatch Logs? Cannot find out

Screenshots
If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).
Additional context
I suspect this issue is related to browser security setting.
My browser is chrome version 118.0.5993.117 (arm64).

@fromcloud Can you please double check your workflow configuration and make sure you have selected a "target language" if you have Translate enabled? If you don't need translations you can disable Translate. Let me know if that fixes your issue while trying to upload content and run the workflow. Thanks

I missed the workflow configuration as @raulmlamzn said. thanks.


DBZ-474: Fix failure when COLLATE comes after NOT NULL

COLLATE can come after NOT NULL. Currently the MySQL connector fails on such DDL statements.

Excellent, thanks, @medvekoma! Merged to master.


Add release checklist items for querying individual task health checks

When service instances come online as part of a deploy, there is a desire to be able to hit individual service instance health check endpoints. Add items to the release checklist that show how to use curl from the bastion such that it hits the service instance private IP.
If there are issues with firewall rules or port mappings, fix them as part of resolving this issue.

Closing because failing health checks already report their status in the logs.


Big performance improvement

I've done these changes to improve the time to flash firmware.
I removed some small sleeps from the physical.py, and used the UPDI RSD flag to remove the need to receive acknowledgement bytes for every word of data written.
I also added a reset command.
I use a usb-serial adaptor; it all works for me at 115200 baud on the attiny1614 - but I haven't tried any other combination of serial port or device. I have only tested it under Linux.
It would be really useful to test this on other serial interfaces and devices, perhaps there is some reason why these changes will fail on different devices.
I am not an expert on UPDI or attiny microcontrollers, I just read the documentation :)

For me, the time taken to program my device was decreased from 72 seconds, to 12 seconds.

Looks good, @MarkR42! I will give it a run when i have time (hopefully soon).
The byte-by-byte write (with echo on each) was initially a workaround for a bug caused by having one stop-bit (which was of course fixed ages ago)
Turning ACK off is a more "advanced" change, but I think it should be safe at this speed.

Works for me using tiny416 with medbg's cdc on both mac and windows.
Programming time reduced from about 14s to about 4s - nice :)

Also tested good on windows on the m4809 using its own CDC, where the gain is even more significant - I suspect due to the nedbg's CDC being optimised for data frames (not bytes).  This is about where my test coverage ends :/


More powerful options for repeating a part of the previous slide.

Sometimes I want to make slides that are "hierarchical":

One element that changes every ~9 slides. E.g. the left sidebar showing the current chapter.
One element that changes every ~3 slides. E.g. the current headline.
One element that changes on every slide.

I don't have enough experience to say whether this is a good idea or whether I am going to continue to work this way in the future. But it seems like a legitimate goal someone might have.
So how can this be the most DRY?
I personally ended up doing some PHP preprocessing before the markdown kicks in. Kinda worked, but it was ugly.
The -- repeater can do some of this, but it can only go so far.
So what about the following:
--3
Chapter headline 1
--2
Slidegroup headline 1.1
--1
Slide content 1.1.1
--1
Slide content 1.1.2
--2
Slidegroup headline 1.2
--1
Slide content 1.2.1
--3
Chapter headline 2
--2
Slidegroup headline 2.1
--1
Slide content 2.1.1

etc.
The chapter headline and slidegroup headline would be repeated on every slide.
Maybe with html containers for easier styling.
I am totally not suggesting this exact same syntax. In fact I find it horrible :) I am just trying to communicate the idea. Maybe we can get somewhere from this.

If you want a "clean" approach using only mechanism already provided you can use remark's page template feature:
layout: true
name: 1

Chapter headline 1
---
layout: true
template: 1
name: 1-1

Slidegroup headline 1.1
---

Slide content 1.1.1
---

Slide content 1.1.2
---
layout: true
template: 1
name: 1-2

Slidegroup headline 1.2
---

Slide content 1.2.1

---
layout: true
name: 2

Chapter headline 2
---
layout: true
template: 2
name: 2-1

Slidegroup headline 2.1
---

Slide content 2.1.1
---

Slide content 2.1.2

I made the above as complete as possible so you can copy&paste it to try out, but the general principle may not be clear.
So let me break it down in some detail:
...
layout: true <---- tell remark this is NOT a page to display
template: xxx <--- id of chapter (embedding this section)
name: xxx-yyy  <-- this is
      ||| ^^^----- section `yyy` (= the nested level)
      ^^^ -------- of chapter `xxx` (= the embedding level)

... template layout - {{content}} may be used to embed content of actual page ...
---

... actual page will use the closest template preceding it ...
---

... subsequent pages will too ...
---
layout true: <--- (starts next template, i.e. chapter-section or chapter only )
...

This (may or) may not be as DRY as you like, but what makes it verbose is mostly "copy & paste", especially if you do not use numbers for the chapters but short mnemonic for the template names, making it easier.
The "non-dry" part of this approach is the necessity in template pages to repeat the name of the embedding element (xxx in the example above).

Maybe you are also interested to read #384 I opened recently.


Verified

My instagram account please Verified Sir
@jsonproperty
My username @deepusingh08096

PLEASE VERIFIED MY INSTAGRAM ACCOUNT ( @PEDAIWI )


Support for id Properties

I'd like to use plank for generating models for use inside an app i.e. no JSON parsing, and it'd be great to be able to specify @property id myThing and @property UIColor *myColor.
Is anyone else interesting in this capability?

I think there is value in having other concrete types like UIColor but I'd want to avoid having id as a type since we lose pretty much any safety or usage guarantees for that property.

For example, I would like to use plank to generate objects for use in Texture, and sometimes these objects have a userInfo field that stores a plain id so that the user can attach arbitrary context info to something like a an image request. That would be one great use case for this.

@Adlai-Holler - currently we offer things like serialization, copying support for all properties, how do you propose handling this in the case of id?

Also what would the type be for this?

@Adlai-Holler @rahul-malik I think we'd likely make use of this in our composer rewrite

For serialization, I think we could start with not serializing it. I don't know what the extensibility rules for JSON schema are, but maybe we could offer a hatch like, throwing this out there, "type": "$objc(id)"
The bigger question is whether plank is/should be suitable for generating non-serialized plain-old-NS-objects for use inside the app, or if it should be specialized for talking with a server.
Texture, for example, could make great use of a solid ObjC code generator.

The main question for me is does it make sense to create types with properties of unknown types. I think id ends up reducing type-safety and could introduce more issues than it solves.
The only thing that is JSON / Server specific currently is the assumption that dictionaries always use NSString as the key type.
That said, I think there is probably value in having a way to having users declare type extensions outside of the ones listed in JSONSchema and it would be up to them to declare what the corresponding type is for each supported language they wish to generate.

What about treat those cases similar to how Plank deals with NSDate?
The JSON value could be "any" string and with format you would define what kind of class it should be.
This way the responsibility would be up to each developer and not to Plank itself.

@Adlai-Holler - working on a proposal to allow custom type extensions making plank a whole lot more flexible. I’ll forward when I have something to review


[6.0][Concurrency] Reference dispatch_async_swift_job directly when the header is available.

Cherry-pick https://github.com/apple/swift/pull/73945 to release/6.0.
Only use dlsym when we don't have the header, since it's an unnecessary performance hit.
rdar://118465481

@swift-ci please test

@swift-ci please test

@swift-ci please test


Integration with Protocol Buffers plugin

Checklist

[x] I have filed an issue about this change and discussed potential changes with the maintainers.
[x] I have received the approval from the maintainers to make this change.
[x] This is not a stylistic, refactoring, or cleanup change.

Please note that the maintainers will not be reviewing this change until all checkboxes are ticked. See
the Contributions section in the README for more
details.
Discussion thread for this change
Issue number: #3214
Description of this change
Integrate with Protocol Buffers plugin to provide resolution of external *.proto files.

This PR is still missing tests that I will add if overall the change looks OK. @alice-ks PTAL

Please see my feedback on the tracking issue (https://github.com/bazelbuild/intellij/issues/3214#issuecomment-1032989870).

@alice-ks will you be OK merging changes to intellij_info_impl.bzl. This way I will be able to extract the rest in a separate plugin. Still not convenient but better then having a full fork of the plugin.
Having this generic_ide_info for each target is not a problem since there is no one huge aspect file for all the targets. There are just bunch of small aspect files which won't be significantly larger because of generic_ide_info.

Hello @mai93, Could you please have a look on this PR and @fkorotkov comments. Thanks!


React: equivalent solid apis

what are the equivalent apis of React.cloneElement, React.Children   in solid?

Short answer is since we aren't dealing with a Virtual DOM those APIs meant for dealing with VDOM nodes don't make sense.
Of course the real question is what sort of scenarios you were picture using those methods with Solid? And we can see how we'd approach it reactively and identify any gaps.

i am porting react code to solid. what is the best way to do this? part of my code is
render(){
  const {cls, className, clsActive, clsButton} = this.props;
  const {buttons} = this.state;

  return (
    <div className={`button-group ${cls} ${className}`}>
      {
        React.Children.map(this.props.children, (button, index) => {
          const correctIndex = index + 1;
          const isActive = buttons.includes(correctIndex);
          // here each children get new props
          return (
            React.cloneElement(button, {
              cls: button.props.cls + ' ' + clsButton + ' ' + (isActive ? clsActive === '' ? ' active ' : clsActive : ''),
              index: correctIndex,
              onClick: this.buttonClick.bind(this, correctIndex)
            })
          )
        })
      }
    </div>
  )
}

Right so wrapper Component applies click handler and sets active prop on children passed in rather than the parent. Hmm.. I've never actually used these APIs and always opted for a render prop which would work here. The problem is the children are rendered the second you access them which means unless you want to bind to the DOM nodes some more, which is doable although it bypasses the child's state management, you want to defer rendering until you have all reactive vars present. This probably means mapping the buttons to an array of functions that pass the active state in on the outside. But I will give this a shot tonight to see what it could look like.

I've made a Code Sandbox.  https://codesandbox.io/s/boring-bash-n72yd. I found 3 bugs in Solid through working on this example so I have a couple of things not perfect.
This example uses functions to inject the state from the wrapping component. This prop object uses  JS getters to wrap reactive expressions so they can be spread and maintain reactivity.
I'm still not convinced this is a good pattern. There might just be other ways to achieve this through other patterns. I'm not sure there are any additional helpers to generalize this either. All the tools are there I'm just not sure it's obvious.

solid i believe takes on the functional aspect of react and since the example is given in a class based react component, let's look at how we would rewrite the example as a functional component in react.
https://codesandbox.io/s/quizzical-clarke-o411h
if we then do a solid take, here's what you might have
https://codesandbox.io/s/quirky-mccarthy-s8w8l

This pattern is pretty useful in React and I think it generally is a fairly reusable there if the child components have an agreed upon interface. Classically things like routers have used this pattern to push route params down. The newer approach is to use Context + Hooks for routers. Kudos to the people who figured out this could be a thing and used it to slim-down some more challenging "slotting" scenarios with React.
It does suffer through from abstraction smell, in that it works by interacting directly with VDOM nodes, something we aren't supposed to be aware of. It's why they have special functions to hide the inner details there. That is why there is no real equivalent here as Solid has a similar abstraction but completely different implementation. If React ever moved away from a Virtual DOM (say some compiled solution) they could keep 90% of their abstraction but stuff like this would have to change.
I still see the problem though. It is insufficient to do the rendering of the children inside your own wrapper as that isn't reusable. We need to tell the ButtonGroup how to render each button. Personally if I were to do this example I would have the wrapper component (ButtonGroup) take following props:

classes for the button group and buttons etc..
The array of buttons it wants to draw, text, icon.. etc.. whatever information you need
a render prop (or use children as a function) of the form ({ button, className, clickHandler }) => ..... where based on that info you could template the buttons however you want.. using conditionals to choose the right component etc.. In fact this function call could just be a Component definition. ie const Button =  ({ button, className, clickHandler }) => ..... And then your wrapper could be used like <ButtonGroup buttons={buttons} render={Button} />

The shape of the buttons data is whatever you want to pass to yourself to later render the button so it can be pretty much anything. And this way the wrapper can pass its information through and you have a generic factory for generating the right child components based on the data being passed in. I'm pretty sure that's the pattern I'm going to recommend here unless it is missing a particular case.

Agree. I did however wanted to mimic the intent of the example. Passing a
shell to fill it with details from on the wrapper component which then hold
the states of rendered components.
On Wed, Mar 11, 2020, 2:58 PM Ryan Carniato<EMAIL_ADDRESS>wrote:

This pattern is pretty useful in React and I think it generally is a
fairly reusable there if the child components have an agreed upon
interface. Classically things like routers have used this pattern to push
route params down. The newer approach is to use Context + Hooks for
routers. Kudos to the people who figured out this could be a thing and used
it to slim-down some more challenging "slotting" scenarios with React.
It does suffer through from abstraction smell, in that it works by
interacting directly with VDOM nodes, something we aren't supposed to be
aware of. It's why they have special functions to hide the inner details
there. That is why there is no real equivalent here as Solid has a similar
abstraction but completely different implementation. If React ever moved
away from a Virtual DOM (say some compiled solution) they could keep 90% of
their abstraction but stuff like this would have to change.
I still see the problem though. It is insufficient to do the rendering of
the children inside your own wrapper as that isn't reusable. We need to
tell the ButtonGroup how to render each button. Personally if I were to
do this example I would have the wrapper component (ButtonGroup) take
following props:

classes for the button group and buttons etc..
The array of buttons it wants to draw, text, icon.. etc.. whatever
information you need
a render prop (or use children as a function) of the form ({ button,
className, clickHandler }) => ..... where based on that info you could
template the buttons however you want.. using conditionals to choose the
right component etc.. In fact this function call could just be a Component
definition. ie const Button = ({ button, className, clickHandler }) =>
..... And then your wrapper could be used like

The shape of the buttons data is whatever you want to pass to yourself to
later render the button so it can be pretty much anything. And this way the
wrapper can pass its information through and you have a generic factory for
generating the right child components based on the data being passed in.
I'm pretty sure that's the pattern I'm going to recommend here unless it is
missing a particular case.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ryansolid/solid/issues/126#issuecomment-597810845,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSKP637W2ZUQ3JADEJ7HIDRG7NO3ANCNFSM4LDQGXTA
.

Thread seems inactive. Closing.


WinError 123 (Windows) when installing via Jupyter Notebook

When installing package through Jupyter Notebook on Windows OS, receiving error  ERROR: Could not install packages due to an OSError: [WinError 123] The filename, directory name, or volume label syntax is incorrect: 'C:\\Users\\Username\\...\\{{"{{\'.github\' if use_github_action}}"}}'

Hi, thanks for reporting this.
Can you share how you installed solutions-builder on jupyter? Did you run !pip install solutions?


cropped_aicity folder order???

I am confused how to provide  cropped_aicity folder.
Should I make cropped images folder structure as we do with test_data?
my test_data structure is: test_data/gallery/im_test and test_data/query/im_query
When I run fast_submit_baidu.py I am getting the following error:
RuntimeError: CUDA out of memory. Tried to allocate 1.39 GiB (GPU 0; 7.80 GiB total capacity; 5.19 GiB already allocated; 174.31 MiB free; 5.59 GiB reserved in total by PyTorch)
@layumi  Could you please give me some guidance about how to prepare test_dir and crop_dir to run fast_submit_baidu.py?
Thanks again for your great job.

Hi @martianvenusian
I think you are right.
The error is due to the memory limitation of your GPU. You may use small batchsize during inference.

Hi @martianvenusian
I think you are right.
The error is due to the memory limitation of your GPU. You may use small batchsize during inference.

@layumi Thank you for fast response.
I am using two 8GB GPUs. I have tried with batchsize 1 the same error occurring.
I am trying to understand your code. But I don't understand why I am still getting CUDA out of memory error


halve silently fails on zip collections

The current implementation of halve(zip(xs...)) essentially amounts to zip(map(halve, xs)...). This causes a problem when halve splits collections differently. Each half is then a zip of different-length collections, and since zip stops iterating at the end of the shortest collection, some elements are silently left out.

@perrutquist Can you check which version you're using? This is what I see currently:
julia> using SplittablesBase: halve

julia> halve(zip([1,2], [1,2,3]))
ERROR: ArgumentError: `halve(zip(...))` requires collections with identical `size`
Stacktrace:
 [1] shape
   @ ~/.julia/packages/SplittablesBase/FeYNd/src/implementations.jl:264 [inlined]
 [2] checkshape
   @ ~/.julia/packages/SplittablesBase/FeYNd/src/implementations.jl:258 [inlined]
 [3] halve(xs::Base.Iterators.Zip{Tuple{Vector{Int64}, Vector{Int64}}})
   @ SplittablesBase.Implementations ~/.julia/packages/SplittablesBase/FeYNd/src/implementations.jl:270
 [4] top-level scope
   @ REPL[5]:1

and it seems this was fixed back in 2020 by this PR: https://github.com/JuliaFolds/SplittablesBase.jl/pull/28/files
If you have an example on a recent version of SplittablesBase.jl where this still fails though, please let me know so we can think up a fix.

Here's an example of what I mean. Let Vector{Float64} be a stand-in for a user type, for which I define halve method that cuts it "roughly in half".
(@v1.8) pkg> status SplittablesBase
Status `~/.julia/environments/v1.8/Project.toml`
  [171d559e] SplittablesBase v0.1.15

julia> import SplittablesBase: halve

julia> function halve(xs::Vector{Float64})
           mid = ceil(Int, length(xs)/2)
           left = @view xs[firstindex(xs):firstindex(xs)-1+mid]
           right = @view xs[firstindex(xs)+mid:end]
           return (left, right)
       end
halve (generic function with 20 methods)

julia> a = collect(1:5); b = float.(a);

julia> halve(zip(a,b))
(zip([1, 2], [1.0, 2.0, 3.0]), zip([3, 4, 5], [4.0, 5.0]))

julia> collect.(ans)
([(1, 1.0), (2, 2.0)], [(3, 4.0), (4, 5.0)])


pdksync - Use abs instead of vmpooler to provision test resources

Use abs instead of vmpooler to provision test resources
pdk version: 1.17.0

Codecov Report

Merging #85 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master     #85   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files           1       1
  Lines          14      14
======================================
  Misses         14      14

Continue to review full report at Codecov.

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


Add Philips Hue white ambiance suspension Amaze

Hello,
I open this ticket to request support for this device, I look at the list it is not yet in there thank you
https://www.zigbee2mqtt.io/devices/4023330P7.html

Done, could you please update plugin and check

Hello @stas-demydiuk
Thank you for the speed of the support I am traveling this weekend I confirm you the good work Monday of the device

Hello @stas-demydiuk
I just tried it everything works perfectly I close the ticket


brace expansion in values file paths

For more context, please see the relevant discussion in our official slack channel  https://sweetops.slack.com/archives/CE5NGCB9Q/p1554569444071500
This feature would allow you to dramatically reduce repetitions in your helmfile.yaml.
Consider the use-case that you want load values.yaml files matching dynamic patterns:
releases:
- missingFileHandler: warn # prevent the install to stop if some files are not
  values:
  - "../values/{{`{{.Release.Name}}`}}.yaml"
  - "../values/{{`{{.Release.Name}}`}}.yaml.gotmpl"
  - "values/{{`{{.Release.Name}}`}}.yaml"
  - "values/{{`{{.Release.Name}}`}}.yaml.gotmpl"
  - "{{ env "TALEND_LOCAL_PATH" }}/platform-services/helmfile/hybrid-remote/values/{{`{{.Release.Name}}`}}.yaml"
  - "{{ env "TALEND_LOCAL_PATH" }}/platform-services/helmfile/hybrid-remote/values/{{`{{.Release.Name}}`}}.yaml.gotmpl"

With this feature, you can rewrite it to:
releases:
  values:
  - {../,,{{ env "TALEND_LOCAL_PATH" }}}values/{{`{{.Release.Name}}`}}.yaml{,.gotmpl}

Note that you can even omit missingFileHandler assuming you want at least one matching values file to exist.

I would do this as long as https://github.com/thomasheller/braceexpansion works 😄


Webmock breaks HTTP::Client.get(“https…”) with Closed stream (IO::Error)

Webmock breaks
    require "webmock"
    WebMock.allow_net_connect = true
    response = HTTP::Client.get("https://api.exchangeratesapi.io/latest?base=EUR")
    p response

I got exception
Closed stream (IO::Error)
         from /usr/share/crystal/src/io.cr:128:5 in 'check_open'
         from /usr/share/crystal/src/io/buffered.cr:99:5 in 'peek'
         from /usr/share/crystal/src/io.cr:632:37 in 'gets'
         from /usr/share/crystal/src/io.cr:591:5 in 'gets'
         from /usr/share/crystal/src/io.cr:814:5 in 'read_line:chomp'
         from /usr/share/crystal/src/http/content.cr:205:7 in 'read_chunk_size'
         from /usr/share/crystal/src/http/content.cr:187:26 in 'next_chunk'
         from /usr/share/crystal/src/http/content.cr:120:7 in 'read'
         from /usr/share/crystal/src/io.cr:554:29 in 'gets_to_end'
         from /usr/share/crystal/src/http/client/response.cr:81:15 in 'consume_body_io'
         from lib/webmock/src/webmock/core_ext.cr:12:7 in 'exec_internal'
         from /usr/share/crystal/src/http/client.cr:576:5 in 'exec'
         from /usr/share/crystal/src/http/client.cr:698:5 in 'exec'
         from /usr/share/crystal/src/http/client.cr:730:7 in 'exec'
         from /usr/share/crystal/src/http/client.cr:402:3 in ‚get

Without webmock all works as expected.
P.S. Original question https://stackoverflow.com/questions/60847886/closed-stream-ioerror-with-httpclient-gethttps

I just ran in to this as well. Any Lucky app using this shard, and LuckyFlow will hit this because LuckyFlow reaches out to Google to fetch chromedriver.

As a general advice, I'd recomend against intrusive mocking mechanisms like webmock. If you can avoid it, don't use it. It's not always easy, of course.
But often it's simply possible to make a HTTP::Client instance configurable, so you can hook it up directly to a mock backend.


Issue #000 fix: Course Certificate Generation Fix

Codecov Report

Merging #628 into post-publish-processor will not change coverage.
The diff coverage is n/a.

@@                    Coverage Diff                    @@
##             post-publish-processor     #628   +/-   ##
=========================================================
  Coverage                     32.66%   32.66%
  Complexity                     1232     1232
=========================================================
  Files                           170      170
  Lines                         14981    14981
  Branches                       2371     2371
=========================================================
  Hits                           4893     4893
  Misses                         9363     9363
  Partials                        725      725

Continue to review full report at Codecov.

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


Final GUNW 3.0 Packaging Updates

This represents the final packaging updates requested by @dbekaert and ACCESS team. Note: the python files I modified were reformatted by ruff (via VS code) and so there appears to be more changes than what is done. Below, I have highlight important changes and spell-out important questions that can be answered before merging.
Here is a sample GUNW run by this branch: link. The command to generate the above product is:
OMP_NUM_THREADS=4
isce2_topsapp --secondary-scenes S1A_IW_SLC__1SDV_20220131T222803_20220131T222830_041711_04F690_8F5F \
                                 S1A_IW_SLC__1SDV_20220131T222828_20220131T222855_041711_04F690_28D7  \
              --reference-scenes S1A_IW_SLC__1SDV_20220212T222803_20220212T222830_041886_04FCA3_2B3E \
                                 S1A_IW_SLC__1SDV_20220212T222828_20220212T222855_041886_04FCA3_A3E2  \
              --frame-id 25502 \
              > topsapp_img.out 2> topsapp_img.err\

Here is the browse imagery:

Note: ionosphere and SET corrections are now default so the correction arguments are not needed in the above command.
Ionosphere
@mgovorcin @dbekaert:
Please review this modification to the staging of the water mask for the ionosphere here. Below are screenshots of the ionosphere layers (ionosphereBurstRamps and ionosphere, respectively) in the product (which can also be seen directly in the GUNW linked above):

I can provide additional ISCE files or you can check the folder on our shared server leffe in /mnt/leffe-data2/cmarshak/Jan2024-topsapp-revision.
Global attributes for relevant mean values
@sssangha @mgovorcin @dbekaert
In an email from David last week, we agree to have global attributes of the following:

Mean (filtered) coherence masked with water
Mean (filtered) coherence
Mean perpendicular baseline*
Mean parallel baseline*
Mean incidence angle
Mean azimuth angle (with ARIA convention) i.e. adding 90 degrees to ISCE2 raster

They are now as global attributes (copied from the panoply netcdf viewer):
:mean_filtered_coherence_without_water_mask = 0.3126283f; // float
:mean_filtered_coherence_with_water_mask = 0.32342613f; // float
:mean_incidence_angle = 28.281992f; // float
:mean_azimuth_angle = -99.18769836425781; // double
:mean_parallel_baseline = 79.44112223102859; // double
:mean_perpendicular_baseline = -130.66025246650725; // double

All the values except for the baselines can be obtained by averaging a band from the ISCE2 raster. The relevant paths (in the merged folder) and the band are captured here. For taking the mean of geocoded ISCE2 rasters, the code is here. I created a simple integration test by staging the merged directory in s3 and using those rasters to generate the means provided. If there are corrections or changes or concerns, please make specific use of this staged data so we can all be on the same page.
For extracting baseline data, you can see this code here that extracts the baselines from the relevant topsProc.xml file and computes an average for perpendicular and parallel baseline values (there are 6 total for each value). An integration test of the extraction process is here in which the baselines are extracted from this sample topsProc.xml.
Water Mask
The water mask used in all the workflows is the ESA Land Cover 2021 map (via tile-mate).
For the ionosphere, as noted above, the code is here. For the browse imagery, it is captured here. For the mean value of the masked coherence, it reuses the browse masking and the relevant lines of code are found here.
To see some improvement of the browse imagery from this PR compare it to the browse image generated the current dev branch:

@mgovorcin - the water mask is obtained through ESA world cover 2021.
I wrote a package (similar to dem-stitcher) that merges the tiles. The permanent water class is what I am using.
Here is a basic example in the demo: https://github.com/OPERA-Cal-Val/tile-mate/blob/dev/notebooks/Basic_Demo.ipynb
And here is how it is used in the code: https://github.com/ACCESS-Cloud-Based-InSAR/DockerizedTopsApp/blob/final_packaging_updates/isce2_topsapp/localize_mask.py#L27-L40

@mgovorcin Please review impact in the ionospheric area.
@cmarshak we should document the limitations of our ancillaries somewhere. i.e. DEM, water mask (max latitude bounds etc). Did we also confirm there are no gaps on the water masks etc. We had some issues with the DEM and patched it earlier too,.

I all this looks fine to me please do some testing to confirm this is all as expected.
Look at GUNW created from ASC,DESC and also for the north and southern hemisphere.

@mgovorcin Please open these global variables and ensure this is meeting your expectations.

@dbekaert asked for the following:

to check whether the GUNW cubes (for angles) and comparable rasters (coherence) had similar means to those computed from the ISCE2 geocoded rasters as done for the global variable. This has been checked using the GUNW above and is now included as an integration test, comparing the respective means from the GUNW with those from the geocoded rasters output from ICSE2 and ensuring they are within acceptable range for the particular example. For coherence, the mean values are within .01. For angles, the means are within 1 degree.
Include mean_unfiltered_coherence_with/without_water_mask as global variables. These too are apart of the integration test from 1.

For larger scale studies, let's use hyp3 after this has been merged.

Also, the water_mask attribute now looks like:
:water_mask = "water_mask_derived_from_esa_world_cover_2021_10m.geo";


Go to general registry 🤞

[x] TagBot
[x] Install app
[ ] Comment this issue following this

@JuliaRegistrator register()

Error while trying to register: Error in (Julia)Project.toml: Package 'CTBase' with UUID: 54762871-cc72-4466-b8e8-f6c8b58076cd not found in registry or stdlib

Checkout @PierreMartinon @jbcaillau

Error while trying to register: Error in (Julia)Project.toml: Package 'CTBase' with UUID: 54762871-cc72-4466-b8e8-f6c8b58076cd not found in registry or stdlib

Registration pull request created: JuliaRegistries/General/110817
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.9.4 -m "<description of version>" 7687e0760c05bf2bade9dc83adfb048d348c2285
git push origin v0.9.4

Also, note the warning: This looks like a new registration that registers version 0.9.4.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

Registration pull request updated: JuliaRegistries/General/110817
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.9.4 -m "<description of version>" 740c8120b8d0ec9478335053ed59cfbb77fc79df
git push origin v0.9.4

Also, note the warning: This looks like a new registration that registers version 0.9.4.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.


Fix document RDFa extractor to get subject attributes

Overview
Currently causes RB to crash when attempting to save new regulatory statement templates as they have properties but no subject.
connected issues and PRs:
N/A
Setup
I tested linked to RB.
How to test/reproduce
Create a new blank regulatory statement template in RB and then save it. It should save and not crash.
Challenges/uncertainties
N/A
Checks PR readiness

[ ] UI: works on smaller screen sizes
[ ] UI: feedback for any loading/error states
[ ] Check cancel/go-back flows
[ ] Check database state correct when deleting/updating (especially regarding relationships)
[x] changelog
[x] npm lint
[x] no new deprecations

This makes sense, but shouldn't we do the node.dataset['subject'] check seperate from the node.dataset['outgoingProps']. This way we also support nodes with a subject but without outgoing props. Similar to the original getRdfaAwareAttrs. Wouldn't it also be possible to check on the node.dataset['rdfaNodeType'] attribute, similar to getRdfaAwareAttrs?

You're right about making the subject check separate. I've changed that now. For the rdfaNodeType, I don't think we currently set a node type for documents, so I don't think this works here. Did you have something else in mind?

yeah we dont set the rdfaNodeType for documents
I tried to set that always to resource, but it caused other issues
so the doc node is being special cased in all the parsing logic atm


Corrected syntax error

Removed the second unneeded -Identity from lines 24 and 30.

@veharshv can you review these changes and approve the merge request. Thank you.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-pnp/Publish-PnPApp.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[Flake] Pubsub endurance benchmark times out

Raw: https://storage.googleapis.com/cloud-cpp-community-publiclogs/logs/google-cloud-cpp/main/614b71877d7508178f2451bd9fdd74250d3ffb57/fedora-34-tsan/log-153e30f3-36b1-4f8a-bdce-108adcf478e8.txt
//google/cloud/pubsub/benchmarks:endurance                              TIMEOUT in 900.1s

Benchmark output:
# Running Cloud Pub/Sub experiment
# Start time: 2021-08-21T19:42:01.754177376Z
# Configured topic:
# Actual topic: cloud-cpp-2021-08-21-jazjlxpzkptzvbdvzjlnlaycljinbcag
# Flow Control LWM: 8000
# Flow Control HWM: 10000
# Publisher Count: 1
# Subscription Count: 1
# Session Count: 1
# Minimum Samples: 1
# Maximum Samples: 10
# Minimum Runtime: 0s
# Maximum Runtime: 2s
Timestamp,RunningCount,Count,Min,Max,Average(us)
2021-08-21T19:42:11.933890131Z,2017,2017,467981,1975135,1365548
-- Test timed out at 2021-08-21 19:57:01 UTC --

It might have the same root cause as #6793. I remember when testing our library on ARM (in July), I saw both tests flake (building with both bazel and cmake).

I think this was fixed by @coryan in #7313


MegaEvolve not making any sound

Description
When mega-evolving a Pokémon in battle, it doesn't play any sound, even after following the resource pack steps, even though the message displays correctly.
How to reproduce
Steps to reproduce the behavior:

Enter a battle
MegaEvolve a Pokemon
No make any sound

Context
Pixelmon Version: 9.1.7
PixelTweaks Version: 1.7.1
Server or Single Player: Singleplayer
Additional Context: -

Could you send me a version of the resource pack you're using so I can do some testing with it?

Cannot replicate. Your resource pack just didn't have the Mega Evolve thing setup right. The JSON file was a txt file


[RFC] SLH-DSA Updates for Earl Grey

Description
This document proposes updates to the SLH-DSA (Sphincs+) implementation used in secure boot to provide configuration options that will simplify integration with offline and cloud based code signing infrastructure, while providing additional performance improvements in secure boot.

Here's some context that might be helpful:

SPHINCS+ supports parameter sets with either SHAKE or SHA-2 as the underlying hash function.
The current implementation uses SHAKE, although the reasons for that are not super strong. They include:

for signing or keygen in the future we'd want to use SHAKE, since it has SCA protection
NIST was previously considering dropping the SHA-2 parameter sets, but has since decided to keep them, so this no longer really matters
the algorithm instantiation is a little more ergonomic for SHAKE than SHA2; while the SHAKE version just uses SHAKE for everything, the SHA2 version needs HMAC and MFG1 as well.

Now, there are some reasons emerging why we may want to use SHA-2 instead, or at least make it possible:

signing infrastructure might support SHA-2 faster than it supports SHAKE
SHA-2 is slightly faster than SHAKE on OpenTitan because the implementation is not masked (10.5ms vs 12.5ms based on some quick ballpark benchmarks)

In addition to the SHAKE vs SHA-2 question, there's a separate but related question: should we allow a "pre-hashed" option (via an OTP setting or similar) in which the message we sign with SPHINCS+ is the hash of the ROM_EXT image, rather than the image directly? If we did this and used SHA-2, it would reduce boot time for large images because ECDSA and SPHINCS+ could use the same digest (although arguably it would also have an effect on the fault attack difficulty -- see the doc for some discussion).
I'm a little ambivalent on these options myself to be honest; I think there aren't a lot of terrible choices here, and the balance to strike is keeping ROM code as simple as possible while also retaining flexibility as much as we can. Either way, though, if we want to make it for ROM freeze we need to decide on this one pretty quickly. It's a not huge but also not trivial amount of implementation effort.

removing Hotlist label since approved by TC

Can this be closed now?

Yes! I thought that "Resolves" would link it in this comment but I guess it didn't: https://github.com/lowRISC/opentitan/pull/23765#issuecomment-2189313053


Store address information that comes from Stripe

When using Stripe frontend tools, such as Express checkout, we don't always get the complete address information sent back. This can cause a problem for Lunar as we're potentially storing a small subset of what is actually on the payment intent.
This PR looks to add a new action which updates the billing and shipping addresses on Lunar during placement, using the payment intent as the source of truth.
This is enabled/disabled via a new config option
// config/lunar/stripe.php

<?php

return [
    // ...
    'sync_addresses' => true,
];

@alecritson should this have a test?

@alecritson should this have a test?

Test has been added


account-service: Always return handle with suffix

As a user, I expect the POST accounts/siwf to return the display handle.suffix for all login flows.
Current behavior:

Some endpoints return the handle without the suffix.

Expected behavior:

All returns should include the suffix.

closed in another issue.


bug:    errr on setup

Did you check docs and existing issues?

[X] I have read all the which-key.nvim docs
[X] I have searched the existing issues of which-key.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.9.1
Operating system/version
windows
Describe the bug
I do the following setup:
wk=require('which-key')
wk.setup()
wk.register({
    prefix = "<leader>",
    mode = "v",
})

I get the following on startup
--E5108: Error executing lua ...\.vim\plugged\which-key.nvim/lua/which-key/util.lua:128: errr
--stack traceback:
    --[C]: in function 'error'
    --...\.vim\plugged\which-key.nvim/lua/which-key/util.lua:128: in function 'parse_keys'
    --...\.vim\plugged\which-key.nvim/lua/which-key/keys.lua:425: in function 'update_keymaps'
    --...\.vim\plugged\which-key.nvim/lua/which-key/keys.lua:333: in function 'update'
    --...\.vim\plugged\which-key.nvim/lua/which-key/init.lua:96: in function 'load'

where line 128 is  :
  if #notation ~= #internal then
    error('errr')
  end

Steps To Reproduce
As mentioned
Expected Behavior
Worked
Repro
Minimal configuration worked. It might be something in my mapping.

This isn't a bug. Look at the examples in the README. register takes a table of prefixes to mappings.


usFrameWorksExamplesDriver hangs when quitting after stopping system bundle

Steps to repro
λ usFrameworkExamplesDriver.exe
> u 0
> q

It hangs here and I have to press [Ctrl-C] to exit out of the driver program. (Tested on Win 10)
Under any other scenario "q" exits gracefully and returns us back to the shell.

uninstalling the system bundle should throw an exception. Its not allowed, per the OSGi spec.

@jeffdiclemente  suggested to try the following snippet just before exiting the driver program to see if this is a similar bug he is working on
  framework.Stop();
  framework.WaitForStop(std::chrono::seconds::zero())

However, it still hangs in WaitForStop() method.

As @jeffdiclemente said, uninstalling the system bundle should throw an exception acc. to the OSGi spec.
My tentative idea of a fix is to

implement Framework::Uninstall() and throw an exception if this is called per spec
Check if GetBundleId() == 0 in Bundle::Uninstall() and throw the same exception
(Of course, I maybe wrong about the fix :-) )

However, even if this is implemented, the reason behind the aforementioned hang is still unknown.

Implementing the exception in Bundle::Uninstall() locally led me to this finding that we don't "uninstall" the bundle when we do "u 0" in the driver program. According to the help
> h
h               This help text
l <id | name>   Start the bundle with id <id> or name <name>
u <id>          Stop the bundle with id <id>
s               Print status info

So we are simply stopping it. I erroneously associated the letter 'u' with 'uninstall'.
I have changed the title to reflect this.

Now, I check if the bundle id is 0 and if so, I do the WaitForStop() like Jeff suggested i.e.
        try
        {
          bundle.Stop();
		  if (id == 0)
		  {
		    framework.WaitForStop(std::chrono::seconds::zero());
		  }
        }

And this doesn't hang!
λ usFrameworkExamplesDriver.exe
> u 0
> q

(returns to shell gracefully)

It turns out a framework.WaitForStop() immediately after bundle.Stop() (refer to the previous update) works as desired but a framework.WaitForStop() down below (just before the return), hangs. Jeff surmised it maybe due to a race condition.

I believe the issues you found have been fixed in #130 . For the hangs, I couldn't reproduce them. But I am not sure I fully understand what combinations you tries. If you added a WaitForStop() call before returning from main but without actually calling framework.Stop(), then this would hang for sure.
Feel free to re-open this issue if you think there is still something to fix here.

Just to close the loop, you are right @saschazelzer. The issue seems to have been fixed with your changes and I no longer encounter the hang.


Fix/issue5 remove child

#5

Coverage decreased (-0.8%) to 91.914% when pulling 926fe59bf7ea410edccf917acf584f92ab058030 on fix/issue5-remove-child into e0f4bad024f6a499c8e878851c9f2bfb69b89566 on master.


1823825 | Message fixes | Address validation issues | 36

This PR is for user story 1823825.
Fixed an issue with missing table headers.
If these changes are not appropriate, please let me know. I'm only trying to clean up validation issues in this repo. So I can easily close this PR or modify it in whatever way is best for the content.

Docs Build status updates of commit cc6678a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

his/install-and-config-guides/system-requirements-2020.md
:bulb:Suggestion
View
Details

his/install-and-config-guides/system-requirements.md
:bulb:Suggestion
View
Details

his/install-and-config-guides/tn3270-emulator2.md
:bulb:Suggestion
View
Details

his/install-and-config-guides/trace-viewer2.md
:bulb:Suggestion
View
Details

his/core/transaction-errors.md
:white_check_mark:Succeeded
View

his/db2oledbv/data-provider-error-codes.md
:white_check_mark:Succeeded
View

his/db2oledbv/data-source-wizard.md
:white_check_mark:Succeeded
View

his/db2oledbv/installing-data-provider-version-6-0.md
:white_check_mark:Succeeded
View

his/esso/issomapper2-members.md
:white_check_mark:Succeeded
View

his/install-and-config-guides/host-file-transfer-utility.md
:white_check_mark:Succeeded
View

his/install-and-config-guides/host-integration-designer.md
:white_check_mark:Succeeded
View

his/install-and-config-guides/system-requirements-2020.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: System Requirements' is duplicated in 'install-and-config-guides/system-requirements-2020.md(2,14)', 'install-and-config-guides/system-requirements.md(2,14)'.

his/install-and-config-guides/system-requirements.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: System Requirements' is duplicated in 'install-and-config-guides/system-requirements-2020.md(2,14)', 'install-and-config-guides/system-requirements.md(2,14)'.

his/install-and-config-guides/tn3270-emulator2.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: TN3270 Emulator' is duplicated in 'core/tn3270-emulator1.md(2,14)', 'install-and-config-guides/tn3270-emulator2.md(2,14)'.
Line 22, Column 1: [Suggestion-table-syntax-invalid] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.

his/install-and-config-guides/trace-viewer2.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: Trace Viewer' is duplicated in 'core/trace-viewer1.md(2,14)', 'install-and-config-guides/trace-viewer2.md(2,14)'.

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

Docs Build status updates of commit 43a4f05:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

his/install-and-config-guides/tn3270-emulator2.md
:bulb:Suggestion
View
Details

his/install-and-config-guides/trace-viewer2.md
:bulb:Suggestion
View
Details

his/core/transaction-errors.md
:white_check_mark:Succeeded
View

his/db2oledbv/data-provider-error-codes.md
:white_check_mark:Succeeded
View

his/db2oledbv/data-source-wizard.md
:white_check_mark:Succeeded
View

his/db2oledbv/installing-data-provider-version-6-0.md
:white_check_mark:Succeeded
View

his/esso/issomapper2-members.md
:white_check_mark:Succeeded
View

his/install-and-config-guides/host-file-transfer-utility.md
:white_check_mark:Succeeded
View

his/install-and-config-guides/host-integration-designer.md
:white_check_mark:Succeeded
View

his/install-and-config-guides/system-requirements-2020.md
:white_check_mark:Succeeded
View

his/install-and-config-guides/system-requirements.md
:white_check_mark:Succeeded
View

his/install-and-config-guides/tn3270-emulator2.md

Line 22, Column 1: [Suggestion-table-syntax-invalid] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.

his/install-and-config-guides/trace-viewer2.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: Trace Viewer' is duplicated in 'core/trace-viewer1.md(2,14)', 'install-and-config-guides/trace-viewer2.md(2,14)'.

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

Docs Build status updates of commit ff19952:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

his/core/transaction-errors.md
:white_check_mark:Succeeded
View

his/db2oledbv/data-provider-error-codes.md
:white_check_mark:Succeeded
View

his/db2oledbv/data-source-wizard.md
:white_check_mark:Succeeded
View

his/db2oledbv/installing-data-provider-version-6-0.md
:white_check_mark:Succeeded
View

his/esso/issomapper2-members.md
:white_check_mark:Succeeded
View

his/install-and-config-guides/host-file-transfer-utility.md
:white_check_mark:Succeeded
View

his/install-and-config-guides/host-integration-designer.md
:white_check_mark:Succeeded
View

his/install-and-config-guides/system-requirements-2020.md
:white_check_mark:Succeeded
View

his/install-and-config-guides/system-requirements.md
:white_check_mark:Succeeded
View

his/install-and-config-guides/tn3270-emulator2.md
:white_check_mark:Succeeded
View

his/install-and-config-guides/trace-viewer2.md
:white_check_mark:Succeeded
View

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

@MandiOhlinger This PR is ready for merge.


Support for a Pre-Loaded GroundRuleStore in Weight Learning

Right now, the weight learning base class (WeightLearningApplication) will check for latent variables and then run grounding.
After that it will call into the learning code that children are to implement.
However some special cases, specifically structure learning, we will need to run weight learning multiple times on similar models.
In this case, we want to be able to pass a pre-grounded GroundRuleStore (GRS) into weight learning.
This requires two main pieces:

Passing a GroundRuleStore into weight learning constructors.
Updating a GroundRuleStore with a new model.

Number 1 is pretty simple. It would be nice if we could move out some older/less used WL applications out to PSL Experimental.
Number 2 is not very hard. We will need to update the Grounding class to have some method like: update(Model, GroundRuleStore).
We could then look for any rules that are in the model, but not the GRS and ground them out. Then look for rules not in the model, but in the GRS and remove them.
This is also pretty interesting since we can leave the GroundAtom values at what they currently are after the last WL run as a hot start.

Complete in 0c2eafd4329741e28facf92c52821da191617855.


Add guest login option

Issue Number
Add a Demo/Guest Login #300
Describe the changes you've made

Added a Guest Login button
Created a guest() function that bypasses the username and password requirements with an appropriate message

Describe if there is any unusual behaviour of your code(Write NA if there isn't)

Text shown:
'); mywindow.document.close(); // necessary for IE >= 10 myDelay = setInterval(checkReadyState, 10); function checkReadyState() { if (mywindow.document.readyState == "complete") { clearInterval(myDelay); mywindow.focus(); // necessary for IE >= 10 mywindow.print(); mywindow.close(); } } return true; }

I'm not sure why this happened, but I'm looking into it.
Additional context (OPTIONAL)

Current appearance
Test plan (OPTIONAL)
A good test plan should give instructions that someone else can easily follow.
How someone can test your code?
Checklist

[x] I have mentioned the related issue number in the PR description.
[x] I have added screenshots and related demo links of my changes.
[x] The title of my pull request is a short description of the requested changes.
[ ] I have added my name to the contributors list at the end of the README.md file.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] Open Source Program names: LGM SoC

Looks fine to me, change the status of your PR from draft so I can merge it.

Done! Please let me know if there are further changes to be made...


open-policy-agent: move to go modules

Motivation for this change
Move to buildGoModule, use an array for buildFlagsArray, and add a longDescription
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 103741 1

1 package built:

open-policy-agent

@GrahamcOfBorg build open-policy-agent

Tried this locally (osx), works great 🎉 Thank you!

Thanks everyone!


[cmake] Install libraries in standard directories

Previously, libraries were installed under lib/swift/${os}/. They should be installed in the default library directory for the relevant target system.
In addition, swiftmodules were installed in the older layout format on non-Darwin platforms. This changes to use the standard modern layout format for swiftmodules.
Checklist

[x] I've added at least one test that validates that my change is working, if appropriate
[x] I've followed the code style of the rest of the project
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary

@compnerd Before I get started on other libraries, is this what you had in mind?

@swift-ci please test

This is going to require a cross-repository test to ensure that the toolchain builds don't break.


User feedback July 2024

Feedback on the changes implemented in 0.9.0. Some of these I know you are aware of, just mentioning here for documentation/completeness. Thank you so much, it's looking GREAT!
Batch Uploader
Looks good, no real comments or changes except that it would be nice to be able to view/review what has been uploaded, which will probably be part of the global directory interaction request (already registered elsewhere). We will test the speed once we have more images to upload.
User Feedback

As you know, currently changes we make to adjust bounding boxes, confirm correct names, or correct wrong names don't make any visible difference; these are my suggestions for how I would like the solution to look but are not absolute.

Interaction box should disappear/minimize when you click "submit;" bounding boxes should disappear or grey out when you select "no seed"
When confirming a correct name, it would be nice if some kind of confirmation badge was visible, either a green checkmark that remains visible on the picture or (my preference) some change to the name in the Results box where it gets a green checkmark or green highlight there.

Similarly, when correcting an incorrect name, it would be nice if the name in the Results box changed, was crossed out, or otherwise indicated it has been corrected (red highlight? red x beside it?).
Currently when you adjust the bounding box, the changes disappear. Not sure if this is because they are not recorded or just that you have to hit "cancel" to make the interactions box disappear

Bounding Box Workflow tweak
I would suggest a small change to the workflow. Currently, when you first mouse over an identified seed, you have two options: green checkmark, red X.

I would suggest adding the blue arrows for adjusting the bounding box to this first stage, if possible, as you might want to adjust the box even though the ID is correct. Also this way you don't have to move the interactions pane out of the way to see the bounding box to adjust it.

Also right now I can only adjust the right and bottom sides of the box, I can't seem to move the box as a whole either.

Class vs. Taxon
Very minorly, would it be possible to change the dropdown box in the interactions pane to say "Taxon" or "Scientific name" instead of "Class"? Class has a very specific meaning in biology (it's the level between Phylum and Family) and that's not the level we're entering here. Taxon or Scientific name are more general terms for what we're wanting.

Dropdown Class List duplication
There is a duplication in the dropdown list of species names, where each name occurs twice, the second time with a number in front of it. Can we fix/merge these?

White box sometimes left behind
A while box has been added that sits behind the identifying numbers above each seed to make it easier to read them. However, in situations where the bounding box is close to the top of the image, the number gets switched to the bottom, and now the white box is getting left behind. Very minor.

That basically covers my thoughts for now. I am very excited about all your hard work, it is really coming together! Please go ahead and divide this list up however it makes the most sense for you, and if I can clarify anything let me know!

I did have a thought about the batch uploader:
We have created it to function primarily for uploading training images to you guys for use on the back end. However, once the directory-interaction function is in place, users might want to use it for images they would like to classify, for example if I take images of impurities from several samples over the course of a day, I might choose to upload them all at once and then classify. This wouldn't really work with the uploader as is because you have to define the taxon you are uploading as well as the scale, so you can't upload mixed images or images taken at different maginifications. If we could change the "class" (and maybe scale?) dropdowns from required to optional, it might increase the flexibility/functionality of this feature for users. Not a high priority but something to maybe think about for the future.


RPI 3 model b and JK BMS not working

Trying to connect my JK BMS via BT to RPI3 model B using embedded BT module but no way to connect
kindly ask for support
some notes
BT module seems correctly installed and detected by HA on hci0 adatper on my RPI

I have tried connection both with and without PIN "1234"
I have executed almost all the suggestinons (except power cycle JK bms since can't switch off the battery bank) in the troubleshooting section
-install_newer_bleak done
-bt_power_cycle on done
JK BMS is visible via BLE scanner and I have updated the address in the settings

this is my device configuration

address: C8:47:8C:E8:F2:62
type: jk
alias: LiFePo4 160Ah
debug: true

Notice that I have RPI 3 connected via wifi ... I can't do differently since where battery is located no LAN cable :-(
these are the info from BMS

BEGIN
await scanner.start()
File "/usr/lib/python3.11/site-packages/bleak/backends/bluezdbus/scanner.py", line 145, in start
assert_reply(reply)
File "/usr/lib/python3.11/site-packages/bleak/backends/bluezdbus/utils.py", line 23, in assert_reply
raise BleakDBusError(reply.error_name, reply.body)
bleak.exc.BleakDBusError: [org.bluez.Error.NotReady] Resource Not Ready
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/app/main.py", line 43, in fetch_loop
if await fn():
^^^^^^^^^^
File "/app/main.py", line 357, in fn
raise exceptions[0]
File "/app/main.py", line 352, in fn
await t()
File "/app/bmslib/sampling.py", line 153, in call
except bleak.exc.BleakDeviceNotFoundError:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: module 'bleak.exc' has no attribute 'BleakDeviceNotFoundError'
17:35:04 INFO [sampling] connecting bms JKBt(C8:47:8C:E8:F2:62,LiFePo4 160Ah)
17:35:04 INFO [bt] connecting LiFePo4 160Ah (C8:47:8C:E8:F2:62) adapter=default timeout=6
17:35:04 DEBUG [client] Connecting to device @ C8:47:8C:E8:F2:62 with hci0
17:35:04 DEBUG [scanner] cached devices: {}
17:35:04 INFO [jikong] normal connect failed (module 'bleak.exc' has no attribute 'BleakDeviceNotFoundError'), connecting with scanner
17:35:04 DEBUG [bt] starting scan
17:35:04 DEBUG [scanner] cached devices: {}
17:35:04 ERROR [main] 1 exceptions occurred fetching BMSs
17:35:04 ERROR [main] Error (num 4, max 200) reading BMS: module 'bleak.exc' has no attribute 'BleakDeviceNotFoundError'
17:35:04 ERROR [main] Stack: Traceback (most recent call last):
File "/app/bmslib/bt.py", line 184, in _connect_client
await asyncio.wait_for(self.client.connect(timeout=timeout), timeout=timeout + 1)
File "/usr/lib/python3.11/asyncio/tasks.py", line 489, in wait_for
return fut.result()
^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/bleak/backends/bluezdbus/client.py", line 190, in connect
device = await BleakScannerBlueZDBus.find_device_by_address(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/bleak/backends/scanner.py", line 205, in find_device_by_address
return await cls.find_device_by_filter(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/bleak/backends/scanner.py", line 234, in find_device_by_filter
async with cls(detection_callback=apply_filter, **kwargs):
File "/usr/lib/python3.11/site-packages/bleak/backends/scanner.py", line 79, in aenter
await self.start()
File "/usr/lib/python3.11/site-packages/bleak/backends/bluezdbus/scanner.py", line 145, in start
assert_reply(reply)
File "/usr/lib/python3.11/site-packages/bleak/backends/bluezdbus/utils.py", line 23, in assert_reply
raise BleakDBusError(reply.error_name, reply.body)
bleak.exc.BleakDBusError: [org.bluez.Error.NotReady] Resource Not Ready
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/app/bmslib/models/jikong.py", line 125, in connect
await super().connect(timeout=6)
File "/app/bmslib/bt.py", line 235, in connect
await self._connect_client(timeout=timeout)
File "/app/bmslib/bt.py", line 185, in _connect_client
except bleak.exc.BleakDeviceNotFoundError as exc:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: module 'bleak.exc' has no attribute 'BleakDeviceNotFoundError'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/app/bmslib/sampling.py", line 149, in call
s = await self._sample_inner()
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/bmslib/sampling.py", line 212, in _sample_inner
async with bms:
File "/app/bmslib/bt.py", line 343, in aenter
await self.connect()
File "/app/bmslib/models/jikong.py", line 128, in connect
await self._connect_with_scanner(timeout=timeout)
File "/app/bmslib/bt.py", line 259, in _connect_with_scanner
await scanner.start()
File "/usr/lib/python3.11/site-packages/bleak/backends/bluezdbus/scanner.py", line 145, in start
assert_reply(reply)
File "/usr/lib/python3.11/site-packages/bleak/backends/bluezdbus/utils.py", line 23, in assert_reply
raise BleakDBusError(reply.error_name, reply.body)
bleak.exc.BleakDBusError: [org.bluez.Error.NotReady] Resource Not Ready
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/app/main.py", line 43, in fetch_loop
if await fn():
^^^^^^^^^^
File "/app/main.py", line 357, in fn
raise exceptions[0]
File "/app/main.py", line 352, in fn
await t()
File "/app/bmslib/sampling.py", line 153, in call
except bleak.exc.BleakDeviceNotFoundError:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: module 'bleak.exc' has no attribute 'BleakDeviceNotFoundError'
END

update to latest version and try again

Connection OK and stable with last version
Just one minor issue to highlight
Missing some entities in my JK bms device
in particular the "balance" entity

any idea how to fix it ?
br
Davide


Debugger stops working right after debugging any .NET Core application on Manjaro

Environment data
dotnet --info output:
[perret@perret-pc ~]$ dotnet --info
.NET Core SDK (reflecting any global.json):
 Version:   2.2.102
 Commit:    96ff75a873

Runtime Environment:
 OS Name:     manjaro
 OS Version:
 OS Platform: Linux
 RID:         arch-x64
 Base Path:   /opt/dotnet/sdk/2.2.102/

Host (useful for support):
  Version: 2.2.1
  Commit:  878dd11e62

.NET Core SDKs installed:
  2.2.102 [/opt/dotnet/sdk]

.NET Core runtimes installed:
  Microsoft.NETCore.App 2.2.1 [/opt/dotnet/shared/Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

VS Code version:
[perret@perret-pc ~]$ code --version
1.30.2
61122f88f0bf01e2ac16bdb9e1bc4571755f5bd8
x64

C# Extension version: 1.17.1
Omnisharp version 1.32.8
Omnisharp when opening Visual Studio Code with my project in the working directory:
Starting OmniSharp server at 2/3/2019, 11:36:15 AM
    Target: /home/perret/Desktop/Playground/CSharpmusement/Meow

OmniSharp server started with Mono 5.16.0.
    Path: /home/perret/.vscode-oss/extensions/ms-vscode.csharp-1.17.1/.omnisharp/1.32.8/omnisharp/OmniSharp.exe
    PID: 23375

[info]: OmniSharp.Stdio.Host
        Starting OmniSharp on manjaro 0.0 (x64)
[info]: OmniSharp.Services.DotNetCliService
        DotNetPath set to dotnet
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Located 2 MSBuild instance(s)
            1: Mono 15.0 - "/usr/lib/mono/msbuild/15.0/bin"
            2: StandAlone 15.0 - "/home/perret/.vscode-oss/extensions/ms-vscode.csharp-1.17.1/.omnisharp/1.32.8/omnisharp/msbuild/15.0/Bin"
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Registered MSBuild instance: Mono 15.0 - "/usr/lib/mono/msbuild/15.0/bin"
            CscToolPath = /home/perret/.vscode-oss/extensions/ms-vscode.csharp-1.17.1/.omnisharp/1.32.8/omnisharp/msbuild/15.0/Bin/Roslyn
            CscToolExe = csc.exe
[info]: OmniSharp.Cake.CakeProjectSystem
        Detecting Cake files in '/home/perret/Desktop/Playground/CSharpmusement/Meow'.
[info]: OmniSharp.Cake.CakeProjectSystem
        Could not find any Cake files
[info]: OmniSharp.WorkspaceInitializer
        Project system 'OmniSharp.DotNet.DotNetProjectSystem' is disabled in the configuration.
[info]: OmniSharp.MSBuild.ProjectSystem
        No solution files found in '/home/perret/Desktop/Playground/CSharpmusement/Meow'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/home/perret/Desktop/Playground/CSharpmusement/Meow/Meow.csproj'
[info]: OmniSharp.Script.ScriptProjectSystem
        Detecting CSX files in '/home/perret/Desktop/Playground/CSharpmusement/Meow'.
[info]: OmniSharp.Script.ScriptProjectSystem
        Could not find any CSX files
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpWorkspaceOptionsProvider
[info]: OmniSharp.WorkspaceInitializer
        Configuration finished.
[info]: OmniSharp.Stdio.Host
        Omnisharp server running using Stdio at location '/home/perret/Desktop/Playground/CSharpmusement/Meow' on host 23259.
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: /home/perret/Desktop/Playground/CSharpmusement/Meow/Meow.csproj
[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file '/home/perret/Desktop/Playground/CSharpmusement/Meow/Meow.csproj'.
[info]: OmniSharp.MSBuild.ProjectManager
        Adding project '/home/perret/Desktop/Playground/CSharpmusement/Meow/Meow.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Update project: Meow

Steps to reproduce
If needed, Install Arch / Manjaro and yay in order to easily install packages from AUR.
pacman -Sy yay
yay -S dotnet-sdk --noconfirm
yay -S mono --noconfirm
yay -S msbuild-stable --noconfirm
yay -S code --noconfirm

Then creating the default mvc or (console) solution and opening up Visual Studio Code, installing the C# extension, adding the default assets.
mkdir Meow
cd Meow
dotnet new mvc
code .

Install the C# extension
CTRL + SHIFT + P
ext install ms-vscode.csharp
[Restart if needed]
Download the .NET Code Debugger for the C# extension (if needed / not already done the first time)
CTRL + SHIFT + P
Debug: Download .NET Core Debugger
Generate the launch.json and tasks.json files (if not already answered yes to the popup shows: "Would you like to add the required assets to build and debug your project?")
CTRL + SHIFT + P
.NET: Generate Assets for Build and Debug
Debugging (.NET Core Launch (web))
CTRL + SHIFT + D
F5
Expected  behavior
The debugging bar should remain active, the application should be running and open the web browser to the related address:port.
Actual behavior
The debugging bar shows up for 0.1 sec and then disappear, the application is not running (not action equivalent to a dotnet run) and no web browser is actually open.

@gregg-miskelly exactly no error shows in either VS Code or in the debug console.
About the log, here it is:
-> (C) {"command":"initialize","arguments":{"clientID":"vscode","clientName":"Code - OSS","adapterID":"coreclr","pathFormat":"path","linesStartAt1":true,"columnsStartAt1":true,"supportsVariableType":true,"supportsVariablePaging":true,"supportsRunInTerminalRequest":true,"locale":"en-us"},"type":"request","seq":1}
-> (C) {"command":"launch","arguments":{"name":".NET Core Launch (web)","type":"coreclr","request":"launch","preLaunchTask":"build","program":"/home/perret/Desktop/Playground/CSharpmusement/Meow/bin/Debug/netcoreapp2.2/Meow.dll","args":[],"cwd":"/home/perret/Desktop/Playground/CSharpmusement/Meow","stopAtEntry":false,"internalConsoleOptions":"openOnSessionStart","launchBrowser":{"enabled":true,"args":"${auto-detect-url}","windows":{"command":"cmd.exe","args":"/C start ${auto-detect-url}"},"osx":{"command":"open"},"linux":{"command":"xdg-open"}},"env":{"ASPNETCORE_ENVIRONMENT":"Development","ASPNETCORE_URLS":"https://localhost:5001;http://localhost:5000"},"sourceFileMap":{"/Views":"/home/perret/Desktop/Playground/CSharpmusement/Meow/Views"},"logging":{"engineLogging":false},"__sessionId":"c7232537-28cb-4375-b2aa-d4d1bebac69f"},"type":"request","seq":2}
<- (E) {"seq":3,"type":"event","event":"output","body":{"category":"console","output":"-------------------------------------------------------------------\nYou may only use the Microsoft .NET Core Debugger (vsdbg) with\nVisual Studio Code, Visual Studio or Visual Studio for Mac software\nto help you develop and test your applications.\n-------------------------------------------------------------------\n"}}
-------------------------------------------------------------------
You may only use the Microsoft .NET Core Debugger (vsdbg) with
Visual Studio Code, Visual Studio or Visual Studio for Mac software
to help you develop and test your applications.
-------------------------------------------------------------------
<- (R) {"seq":4,"type":"response","request_seq":2,"success":true,"command":"launch"}
<- (E) {"seq":5,"type":"event","event":"initialized","body":{}}
<- (E) {"seq":6,"type":"event","event":"output","body":{"category":"telemetry","output":"VS/Diagnostics/Debugger/vsdbg/CommandFailed","data":{"VS.Diagnostics.Debugger.vsdbg.AdapterId":"coreclr","VS.Diagnostics.Debugger.vsdbg.ErrorCode":-1989017584,"VS.Diagnostics.Debugger.vsdbg.Distribution.Name":"d241e93b","VS.Diagnostics.Debugger.vsdbg.Command":"handshake","VS.Diagnostics.Debugger.vsdbg.OSFamily":"Linux","VS.Diagnostics.Debugger.vsdbg.Version":"16.0.11026.1 commit:87122b596f240c8c819a194d8f57eb6c749483b9"}}}
<- (R) {"seq":7,"type":"response","request_seq":3,"success":false,"command":"handshake","message":"Error processing 'handshake' request. Unknown Error: 0x89720010"}
-> (C) {"command":"setExceptionBreakpoints","arguments":{"filters":["user-unhandled"]},"type":"request","seq":4}
<- (R) {"seq":8,"type":"response","request_seq":4,"success":true,"command":"setExceptionBreakpoints"}
-> (C) {"command":"configurationDone","type":"request","seq":5}
<- (E) {"seq":9,"type":"event","event":"output","body":{"category":"telemetry","output":"VS/Diagnostics/Debugger/vsdbg/CommandFailed","data":{"VS.Diagnostics.Debugger.vsdbg.AdapterId":"coreclr","VS.Diagnostics.Debugger.vsdbg.ErrorCode":17001,"VS.Diagnostics.Debugger.vsdbg.Distribution.Name":"d241e93b","VS.Diagnostics.Debugger.vsdbg.Command":"handshake","VS.Diagnostics.Debugger.vsdbg.OSFamily":"Linux","VS.Diagnostics.Debugger.vsdbg.Version":"16.0.11026.1 commit:87122b596f240c8c819a194d8f57eb6c749483b9"}}}
<- (E) {"seq":10,"type":"event","event":"output","body":{"category":"telemetry","output":"VS/Diagnostics/Debugger/vsdbg/DebugCompleted","data":{"VS.Diagnostics.Debugger.vsdbg.AdapterId":"coreclr","VS.Diagnostics.Debugger.vsdbg.DebugCompleted.BreakCounter":0,"VS.Diagnostics.Debugger.vsdbg.Distribution.Name":"d241e93b","VS.Diagnostics.Debugger.vsdbg.OSFamily":"Linux","VS.Diagnostics.Debugger.vsdbg.Version":"16.0.11026.1 commit:87122b596f240c8c819a194d8f57eb6c749483b9"}}}
<- (R) {"seq":11,"type":"response","request_seq":5,"success":false,"command":"configurationDone","message":"Error processing 'configurationDone' request. Unknown Error: 0x89720010"}
-> (C) {"command":"disconnect","arguments":{"restart":false},"type":"request","seq":6}
-> (C) {"command":"threads","type":"request","seq":7}
<- (E) {"seq":12,"type":"event","event":"output","body":{"category":"telemetry","output":"VS/Diagnostics/Debugger/vsdbg/DebugCompleted","data":{"VS.Diagnostics.Debugger.vsdbg.AdapterId":"coreclr","VS.Diagnostics.Debugger.vsdbg.DebugCompleted.BreakCounter":0,"VS.Diagnostics.Debugger.vsdbg.Distribution.Name":"d241e93b","VS.Diagnostics.Debugger.vsdbg.OSFamily":"Linux","VS.Diagnostics.Debugger.vsdbg.Version":"16.0.11026.1 commit:87122b596f240c8c819a194d8f57eb6c749483b9"}}}
<- (R) {"seq":13,"type":"response","request_seq":6,"success":true,"command":"disconnect"}

I don't think those below are expected, right?
<- (E) {"seq":6,"type":"event","event":"output","body":{"category":"telemetry","output":"VS/Diagnostics/Debugger/vsdbg/CommandFailed","data":{"VS.Diagnostics.Debugger.vsdbg.AdapterId":"coreclr","VS.Diagnostics.Debugger.vsdbg.ErrorCode":-1989017584,"VS.Diagnostics.Debugger.vsdbg.Distribution.Name":"d241e93b","VS.Diagnostics.Debugger.vsdbg.Command":"handshake","VS.Diagnostics.Debugger.vsdbg.OSFamily":"Linux","VS.Diagnostics.Debugger.vsdbg.Version":"16.0.11026.1 commit:87122b596f240c8c819a194d8f57eb6c749483b9"}}}
<- (R) {"seq":7,"type":"response","request_seq":3,"success":false,"command":"handshake","message":"Error processing 'handshake' request. Unknown Error: 0x89720010"}

<- (E) {"seq":9,"type":"event","event":"output","body":{"category":"telemetry","output":"VS/Diagnostics/Debugger/vsdbg/CommandFailed","data":{"VS.Diagnostics.Debugger.vsdbg.AdapterId":"coreclr","VS.Diagnostics.Debugger.vsdbg.ErrorCode":17001,"VS.Diagnostics.Debugger.vsdbg.Distribution.Name":"d241e93b","VS.Diagnostics.Debugger.vsdbg.Command":"handshake","VS.Diagnostics.Debugger.vsdbg.OSFamily":"Linux","VS.Diagnostics.Debugger.vsdbg.Version":"16.0.11026.1 commit:87122b596f240c8c819a194d8f57eb6c749483b9"}}}
<- (E) {"seq":10,"type":"event","event":"output","body":{"category":"telemetry","output":"VS/Diagnostics/Debugger/vsdbg/DebugCompleted","data":{"VS.Diagnostics.Debugger.vsdbg.AdapterId":"coreclr","VS.Diagnostics.Debugger.vsdbg.DebugCompleted.BreakCounter":0,"VS.Diagnostics.Debugger.vsdbg.Distribution.Name":"d241e93b","VS.Diagnostics.Debugger.vsdbg.OSFamily":"Linux","VS.Diagnostics.Debugger.vsdbg.Version":"16.0.11026.1 commit:87122b596f240c8c819a194d8f57eb6c749483b9"}}}
<- (R) {"seq":11,"type":"response","request_seq":5,"success":false,"command":"configurationDone","message":"Error processing 'configurationDone' request. Unknown Error: 0x89720010"}

Correct. Do you have an official version of VS Code installed? Only official versions support .NET Debugging.
I am not sure why you aren't getting an error message for this. Sounds like the VS Code team may have broken something with their error handling.

As far as the word "official" goes: https://aur.archlinux.org/packages/visual-studio-code-bin
I don't have that issue when I am running the same thing against Ubuntu, so might come from a wide variety of factors.

@ehouarn-perret Thanks! You need to install the Official Microsoft copy from https://code.visualstudio.com/

@gregg-miskelly good news: managed to make it work with... the code insiders version!
Still kinda a voodoo answer to me but at least it works now!


error creating Service Account "app-manager-rbac-sa-non-prod": 409 Conflict: Service name is already in use.

What
A user reported the following in https://github.com/confluentinc/terraform-provider-confluent/issues/27:

That's expected since we didn't want to include too much logic in our TF Provider but let me check what other TF providers do.

@bluedog13 we looked at other TF Provider and figured most of them explicitly return a similar error instead of trying to check whether existing remote object matches the one a user wants to create so we'll likely continue to return an error too:

409 Conflict: Service name is already in use.