Xcode successfully builds .xcworkspace but throws error: dyld`__abort_with_payload:

Hi folks, I'm a noob when it comes to opening issues, so please bear with me.
I followed the steps outlined in the README to integrate react-native-proximity within my react native project application. The application builds successfully but gets stuck at the launcscreen.xib image when the app starts on my phone (which Im using as the simulator) and doesn't progres forward to the classic red screen or 'downloading javascript bundle' phase. Simultaneously, in Xcode, it shows the following error:

Here's my Podfile:

And here's my package.json:

And yes, my iPhone developer certificates in KeyChain Access are using system defaults under 'Trust' as opposed to always trust.
Again, I definitely followed all the steps, and cross-referenced them against the basic iOS setup really need to get my react native project working with my estimote proximity beacons as I have a deadline. So any help whatsoever would be greatly appreciated.

Thanks for such a detailed bug report! ❤
Xcode 10 shipped last week with Swift 4.2, which required us to release an updated version of the iOS Proximity SDK built for Swift 4.2. (There are binary-interface incompatible changes between Swift 4.1 and Swift 4.2.)
So, you probably just need to run pod update in your ios directory to update to the latest version of the native SDK, 1.2.0. Let us know if that helps.

YESSS, it worked.

 The delay in reply was because xcode 10 broke my react native project, so I had to manually fix it by going through some terminal stuff to build the application each time. But yes, pod update  did the trick. Side question, and your company's docs probably answer this, but can one check when two proximity beacons are super close to each other as opposed to just checking when my phone is close to N number of beacons. That is, can we check if, say, 2 beacons are in/not in each other's proximity and then let the phone know?

Glad to heart that! ❤

can we check if, say, 2 beacons are in/not in each other's proximity and then let the phone know?

The Proximity Beacons only broadcast, and don't listen/scan, so they wouldn't know on their own when they're close to each other.
Our new/upcoming LTE Beacon is programmable via JavaScript, and can be programmed to scan for other Bluetooth devices, so 2 LTE Beacons could technically know when they're close to each other, and broadcast that information over Bluetooth to the smartphone. (Caveat: continuous Bluetooth scanning will drain the battery much faster, so the LTE Beacon would need to be recharged often, it has a rechargeable battery and a USB-C port for that.)


Installation at MS VS for MAC

How can I install the extension an MicroSoft Visual Studio for Mac?

It is not compatible with Visual Studio for Mac, because Visual Studio for Mac is a separate product from Visual Studio for Windows with completely different extensibility mechanisms.


Fix/zrs capability

Adding support for ZRS option (https://docs.microsoft.com/en-us/azure/storage/common/storage-redundancy-zrs) while creating snapshots in Azure.

In the regions where ZRS is currently not supported(https://docs.microsoft.com/en-us/azure/storage/common/storage-redundancy-zrs#support-coverage-and-regional-availability), snapshots will be created with normal LRS option.

Bumped the versions of azure-mgmt-compute and azure-common (https://github.com/Azure/azure-sdk-for-python/commit/b362f7fa3a6b17175a6ca50603bc02e1792f4b24).

Verified in the Azure console that snapshots are getting created with Zone-redundant account type. It can be verified for snapshot "sf-snapshot-45560-20180717145222" in dev-1 resource group.

Pull Request Test Coverage Report for Build 60

0 of 7 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 35.286%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/clients/AzureClient.py
0
7
0.0%

Totals

Change from base Build 57:
-0.1%

Covered Lines:
652

Relevant Lines:
1792

💛  - Coveralls

@jayeshjk : restore also works fine right ?

@kamath-prasad: Yes. Tested positively for both backup and restore operation with blueprint service.


jq invocation on Windows CMD failing

Hello @Gimi!
Based on https://github.com/Gimi/fluent-plugin-jq/blob/master/lib/fluent/plugin/jq_mixin.rb#L34, it seems like jq is invoked with the filter surrounded by single quotes.  This seems to be problematic when invoking on CMD.
For example:
C:\>jq -n --unbuffered -c '.record.source = "C:/var/log" + .record.source | .record.sourcetype = (.tag | ltrimstr("file.")) | .record' 2>&1
'.record.sourcetype' is not recognized as an internal or external command,
operable program or batch file.

Two potential ways to support CMD:

Would it be possible to change the single quotes into double quotes?  Changing to double quotes seems to fix the issue for CMD, while not breaking it for bash.  Top example is from CMD and bottom is from bash:

C:\>jq -n --unbuffered -c ".record.source = \"C:/var/log\" + .record.source | .record.sourcetype = (.tag | ltrimstr(\"file.\")) | .record" 2>&1
{"source":"C:/var/log","sourcetype":null}

$ jq -n --unbuffered -c ".record.source = \"C:/var/log\" + .record.source | .record.sourcetype = (.tag | ltrimstr(\"file.\")) | .record" 2>&1
{"source":"C:/var/log","sourcetype":null}

Downside of this is that all double quotes would need to be escaped before invoking IO.popen

Create a new build for Windows that uses double quotes.

Let me know if either of these two options look reasonable.  I can submit a PR if you want.
Thanks!

After investigating this more, it doesn't seem like Windows support is going to be as easy as changing the quote character.  Would be really cool if this plugin could support Windows!  The work around for Windows was to just use record_transformer.


Add basis for future automated functional/regression tests of project-clone container

What does this PR do?
In verifying PR https://github.com/devfile/devworkspace-operator/pull/1115, I worked on a semi-automatic regression test for project-clone functionality to ensure the PR wasn't breaking existing behavior. I figured it's worth adding this to the repository so that it's not lost to time.
This PR adds sample DevWorkspaces to project-clone/test/ that tests project clone functionality at a basic level: they verify that projects can be cloned, and that branches, tags, and revisions can be correctly checked out from both the origin and a fork of the repository. If any project is not set up as expected, the workspace enters a failed state (potentially after a few restarts), indicating that there is a problem. If the "test" "succeeds", the workspace enters and stays in a running state. Logs for a successful test look like
Defaulted container "test-project-clone" out of: test-project-clone, project-clone (init)
Testing default project set up
Project is on main, tracking main-origin/main, with remotes configured
Testing branch checkout project set up
Project is on 0.21.x, tracking origin/0.21.x, with remotes configured
Testing tag checkout project set up
Project is on tag v0.21.0, with remotes configured
Testing hash checkout project set up
Project is on commit 79ed3e1ef80da390f7793777c658ecbd13260adc, with remotes configured
[SUCCESS] Test succeeded. Sleeping indefinitely

The workspace makes use of devfile variables to enable configuration of the key elements being tested (main repo, fork repo, branch, tag, revision) so that it can more easily be adapted in the future (though it is harder to read as a result)
The project-clone-test-basic.devworkspace.yaml file is a simpler, more basic test of the functionality above -- it just verifies that we can successfully clone a project from a repository. It was useful for testing that https://github.com/devfile/devworkspace-operator/issues/1114 was resolved (where the self-signed certificates repo I used to test did not have a fork, branches, tags, etc.)
What issues does this PR fix or reference?
N/A
Is it tested? How?
Tests can be run by applying these DevWorkspaces to any cluster where DWO is installed.
PR Checklist

[ ] E2E tests pass (when PR is ready, comment /test v8-devworkspace-operator-e2e, v8-che-happy-path to trigger)

[ ] v8-devworkspace-operator-e2e: DevWorkspace e2e test
[ ] v8-che-happy-path: Happy path for verification integration with Che

/retest

Accidentally forgot to push the project-clone-test-basic.devworkspace.yaml file... pushed now.


Remove link to beta service

Remove link to beta service as it is being discontinued. See Zendesk ticket ref #1391138

👍

@rubenarakelyan note that because Alan's PR comes from a fork, the tests haven't run (they would've failed because of https://github.com/alphagov/business-support-finder/pull/116). I'll turn on branch protection which should prevent this from happening again.

Related; https://github.com/alphagov/business-support-finder/pull/114

@tijmenb: Ah, I wasn't aware that bypassed the tests.


Make the nslog shim optional

Makes the nslog.py logging bootstrap script optional
Add a warning during startup if there's no logging configuration
Enables parallel command line builds. This was showing up as a warning during the briefcase builds, potentially confusing users.

PR Checklist:

[x] All new features have been tested
[x] All new features have been documented
[x] I have read the CONTRIBUTING.md file
[x] I will abide by the code of conduct

With this modification, Briefcase will display the following on an app that doesn't have the std-nslog dependency:
[newtest] Following system log output (type CTRL-C to stop log)...
===========================================================================
Filtering the log data using "senderImagePath == "/Users/rkm/projects/beeware/briefcase/local/newtest/macOS/Xcode/NewTest/build/Release/NewTest.app/Contents/MacOS/NewTest" OR (processImagePath == "/Users/rkm/projects/beeware/briefcase/local/newtest/macOS/Xcode/NewTest/build/Release/NewTest.app/Contents/MacOS/NewTest" AND senderImagePath == "/usr/lib/libffi.dylib")"
Timestamp               Ty Process[PID:TID]
2022-03-01 10:15:31.895 Df NewTest[21820:86372] PythonHome is: /Users/rkm/projects/beeware/briefcase/local/newtest/macOS/Xcode/NewTest/build/Release/NewTest.app/Contents/Resources/Support/Python/Resources
2022-03-01 10:15:31.895 Df NewTest[21820:86372] PYTHONPATH is: PYTHONPATH=/Users/rkm/projects/beeware/briefcase/local/newtest/macOS/Xcode/NewTest/build/Release/NewTest.app/Contents/Resources/app:/Users/rkm/projects/beeware/briefcase/local/newtest/macOS/Xcode/NewTest/build/Release/NewTest.app/Contents/Resources/app_packages
2022-03-01 10:15:31.896 Df NewTest[21820:86372] Initializing Python runtime...
2022-03-01 10:15:31.946 Df NewTest[21820:86372] Unable to locate NSLog bootstrap script.
2022-03-01 10:15:31.946 Df NewTest[21820:86372] No logging configuration bootstrap found. stdout/err will not be captured.
2022-03-01 10:15:31.946 Df NewTest[21820:86372] To capture stdout/error, add 'std-nslog' to your app dependencies.
2022-03-01 10:15:31.946 Df NewTest[21820:86372] Running app module: newtest


question: why does the http server still handle request in ServeHTTP after server.Close or server.Shutdown

What version of Go are you using (go version)?

1.10.3

Does this issue reproduce with the latest release?

YES. It happens when we build using go1.12.2.

What operating system and processor architecture are you using (go env)?
go env Output
GOARCH="amd64"
GOBIN=""
GOCACHE=""
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH=""
GOPROXY=""
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build956601935=/tmp/go-build -gno-record-gcc-switches"

What did you do?

I put some code snippets on here.
What did you expect to see?
The http server will not call "(w *WebSvrImpl) ServeHTTP" after we call "(w *WebSvrImpl) Close()". And the http server should return some special error code. e.g. 404?
What did you see instead?
The http server still returns response with http status code 200 and empty body.
We had known the response with empty body is caused by "(w *WebSvrImpl) ServeHTTP" which will not process  when "w.closed.Get()" is true.
But why the net/http framework still call ServeHTTP() when we had called the Close() or Shutdown()?

Thanks for your reply!

I put some code snippets on here.

Please summarize the relevant properties of those snippets — they don't compile, and it's not obvious what the elided code does or how that interacts with the call to Close.
Note per https://golang.org/pkg/net/http/#Server.Close:

Close does not attempt to close (and does not even know about) any hijacked connections, such as WebSockets.

Also note that closing a connection does not terminate any associated goroutine running ServeHTTP: those goroutines will continue to run until they decide to return (perhaps as a result of noticing a failed write to the response). In particular, it is possible for the ServeHTTP goroutine to start, then the Close call to execute, and finally the ServerHTTP goroutine to become scheduled and run.
So the details of what those nested servers are actually doing are very important, as are the details about when exactly you expect ServeHTTP to no longer be called.

Thanks for your reply.

Please summarize the relevant properties of those snippets — they don't compile, and it's not obvious what the elided code does or how that interacts with the call to Close.

First we create an object of type WebSvrImpl, then call ListenAndServe, now we can recv the http request from client.
Those requests are used for loading some business data from DB.
After serving all the http requests we call Close on such object and stop the whole application.
Then we expect the server will not recv the request from any client.
As you say

Also note that closing a connection does not terminate any associated goroutine running ServeHTTP

we expect that the http.Server should return some error code to indicate it had been stoped during the time we call Close and the end moment of server.
But we still got http request which was handled by ServeHTTP.

Thanks.

we expect that the http.Server should return some error code to indicate it had been stoped during the time we call Close and the end moment of server.

Close literally closes the connection. There is no opportunity to return any error code at that point.
If you want the server to shut down gracefully, you can use the Shutdown method. With that approach, you'd need to communicate the start of shutdown to the handlers by whatever mechanism you like (such as canceling a context.Context), and they can report an appropriate error explicitly.

@pingworld did this adequately answer your question?

Thanks, we have no other questions! We have solved this problem!
All requests have been processed after waiting for several seconds when close the whole app.


Submission to Avalanche Tutorial Contest - Asset Bridge Security

This tutorial is currently a work-in-progress. However, I do hope that it provides an adequate demonstration of the potential for educating and growing the Subnet community.
Following the guidelines expressed to other participants, special attention has been made to:

Verify that the tutorial is building correctly.
All mentions of Subnet are capitalized
Good use of Markdown features (ie. tables, annotations, links, images, etc)

Greatly appreciate this opportunity to contribute to the Avalanche (Subnet) ecosystem.
Cheers!
Shomari

Unfortunately, new entries were only accepted in Round 1, which had a deadline of July 6th. Watch out for new contests coming up.


Place gitbash in place of power shell on Windows

Hey. Is it possible to replace power shell with git bash so it shown in editor, but not in separate window?

You would have to find the shell executable for git bash rather than the launcher that opens a new window. Another user said these settings worked for him:
Shell Override: C:\Program Files\Git\bin\sh.exe
Shell Arguments: --login

Note: See issue #117 for more details.

Thanks, that worked for me

@jeremyramin Is that possible to do it with Cmder ?

@pvorona do you suffer from the same backspace bug as others? don't know if you're system is the same as theirs though.
I don't use Windows often, but when I need to, I find it quite awkward that I can't get this plugin working. I'll do some diagnostics of this problem if I can, hopefully find a solution of some sort, even if it is moving over to ssh based solution. ie. boot a putty cmd or something and connect to a local ssh server.


Performance issue in /libs/models/backbones/efficientnet (by P3)

Hello! I've found a performance issue in /utils.py: dataset.batch(self.batch_size,drop_remainder=batch_drop_remainder)(here) should be called before dataset.map(_parse_function)(here), which could make your program more efficient.
Here is the tensorflow document to support it.
Besides, you need to check the function _parse_function called in dataset.map(_parse_function) whether to be affected or not to make the changed code work properly. For example, if _parse_function needs data with shape (x, y, z) as its input before fix, it would require data with shape (batch_size, x, y, z) after fix.
Looking forward to your reply. Btw, I am very glad to create a PR to fix it if you are too busy.

Hello, I'm looking forward to your reply~


forge snapshot: don't execute fuzz tests at all

Component
Forge
Describe the feature you would like
due to PR https://github.com/gakonst/foundry/pull/1134 fuzz tests are no longer included in the .gas-snapshot output of forge snapshot at all by default
for a significant performance boost we could simply not execute them when running forge snapshot (vs just hiding them from the output)
Additional context
No response

would be happy to try implementing but need some guidance on how to approach this 😅

maybe a custom runner that filters out tests where func.inputs.is_empty() == false?
https://github.com/gakonst/foundry/blob/9ed6b8878c7c2daeb0a6b17ec3b9ff04e7752131/forge/src/runner.rs#L299


Scroll up button and Portfolio page conflict

(Quoted directly from 51836d16560acca4577cd6e472ec081ee438e16d)

Work around a weird bug affecting only the Portfolio page where the button does not reappear when the page is scrolled to visibility then reloaded.

Eventually track down this bug and find out to to prevent calling toggleScrollUp() twice.

This is actually a non-issue, as $(window).scroll(); is only called, well, when the page is scrolled, not on page load. Thus toggleScrollUp() needs to be called twice: once on page load, and when the page is scrolled. Closing.


Add table of contents to readme

Add a table of contents to the top of the readme for easier navigation

Add links to headings/subheadings
Something like this would probably work

Hey, thank you so much for not only checking out Kobweb but also taking the time to leave feedback. I really appreciate it!
I want you to know I absolutely agree with the spirit of this issue -- while the README is better than nothing, it's currently quite long and yet also not detailed enough in some ways. It's easy to feel lost.
This is something I'm taking active steps to fix.
So that said, I'm going to close this issue for the following reasons (but I don't want you to feel like that should end the discussion if you think I'm missing something):

Github already supports TOC for every README, with a TOC button, although it's possible most people aren't aware of it.

Check out this screenshot from the link you shared:

You can check out issue #133 (which I just happened to open earlier today!).

This bug is essentially about moving most of the README over to my website. This will have many advantages, one of which is including a super convenient nav area that's always visible to the left of the content you are reading.
I'm hoping this will start taking place in the next two weeks, as opposed to one of those "coming soon (TM)" bugs.


Close bot spam

Just wanted to say that in the past few days I've been spammed by the close bot emails. It's probably too late now but would probably have been good to find a way to only do it for commits going forward and not retroactively apply it for everything.
This is one of the many series of emails I've received.

yeah, sorry about that. I've been hitting "archive all matching search" a lot in the last few days myself.
It's now done luckily, so as you say not much to be done about it now. Looking back, locking without a comment for anything untouched for, say, a year or something would probably have been a better approach


optimization for donator info in !user command

can u pls just name things what they actually are, it just ruins the log of commits/requests - treat git commit names, comments, pr names as logs

i won't really like squash merging commits but i do it in these cases to keep the log clean

i'm glad you're helping out - i don't mean to set the wrong tone but i try my best to keep it clean :^)

sure sure I just got kinda lazy because it was such a small change


Add type loader support for building ByRef types

The CoreRT compiler and runtime have been able to handle this for a
while. The only thing missing (that required us to throw from a place)
was the type loader support.
This adds support for building ByRef types at runtime. I'm not
introducing a native layout representation though, so things like T&
won't compile still.

@davidwrighton @fadimounir @AtsushiKan Please take a look
This is tested from https://github.com/dotnet/coreclr/blob/master/tests/src/reflection/ldtoken/byrefs.il that I checked in a couple months ago. The LDTOKEN path cannot be tested on Project N because none of the toolchain pieces support it (IL2IL crashes, NUTC would likely fail, and so would the binder because this needs new CTL). I'll check in a separate tests that at least tests roundtripping through a type handle, but the value of such test is dubious.

Aside from blank line nit, lgtm.


Readme, docs: update Meshery logo

Current Behavior
The Meshery logo with tagline is antiquated.
Implementation
Swap out all instances of the tagline logo with a version sans tagline.

Contributor Guides and Handbook

🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation

Meshery documentation site and source

🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

Hey I would like to work on it

Can you please assign it to me?

@tinniaru3005

Anywhere that you see Layer5 logos with the “The Service Mesh Company” tagline, please take a note and let’s see that is replace with a logo without the tagline.
Anywhere that you see a Meshery logo with the “Multi-Mesh Manager” tagline, please take  a note and let’s see that is replace with a logo without the tagline.
Find copies of logos in the Community Drive under the Assets folder or on layer5.io/brand

Hey @leecalcote Do I need to change the logo here also?

Yes, please


Benchmarking / Profiling Recommendations

Any recommendation for running microbenchmarks in the enclave? I cannot naively use libtest bench or criterion as normal. I'm simply looking for general guidance or examples of good benchmarks.

Benchmarking might be complicated here as many use cases should use constant-time algorithms to avoid side channel information leakage. Are you looking for benchmarks of individual operations? I'd be interested in how that could work here as well.

I'm interested in benchmarking critical operations (microbenchmarking), like a unit tests as benchmarks. In untrusted land, the libtest bencher has a harness for this.

hi @LeibnizCapital ,
we have some benchmark results in our CCS'19 paper: https://dingelish.com/ccs19.pdf . section 7
testing code is at https://github.com/mesalock-linux/rust-sgx-benchmark

This is helpful @dingelish Since you've wrote these benchmarks, I'll cut to the chase... Do you have recommendations for large key/value store? I see the hugemem example and some kv crates in third-party. I'm both afraid of abusing encrypted memory and making too many external calls. I'd like to better understand what the tradeoffs are to select the best approach.


Is there a way to prevent "spam" notifications?

This never previously happened, so I'm not sure if this has been a new thing, but when I started coding today I noticed while coding these really annoying popups started showing.

Is there a way I can disable these since they are pretty annoying. I don't mind having them popup for major stuff like ESLint config errors and such (Like they used to), but having them popup instantly as soon as I delete even a single line of code is pretty frustrating.

This happens in the ESLint library I use and swallowing them might not be good either. Can you share a GitHub repository that reproduces this. Then I can see if this is a deeper problem in ESLint or a runtime engine problem (e.g. you need to start the server using a different version of node).

This happens in the ESLint library I use and swallowing them might not be good either. Can you share a GitHub repository that reproduces this. Then I can see if this is a deeper problem in ESLint or a runtime engine problem (e.g. you need to start the server using a different version of node).

Hey @dbaeumer
I'm just using a default Vue CLI 3 project. Not sure entirely if it's to do with the project though since this never happened previously, and only started happening maybe a day or two before I initially posted this issue, which is also the time this extension received an update.
🤔

Heya folks, I think this is due to eslint-plugin-prettier not handling the SyntaxError that prettier throws when it is given code it can't parse - in this case malformed HTML in a vue template like <template><div></template> (note the lack of a closing </div>). As the eslint plugin lints on typing by default you'll have invalid HTML pretty often - as you won't have finished writing the correct closing tags just yet!
I've put up a PR to fix this in https://github.com/prettier/eslint-plugin-prettier/pull/141 and hopefully I intend to merge it tomorrow. By reporting the SyntaxError as an ESLint error you'll get a red squiggly line somewhere in your file, rather than an "problem" notification because eslint crashed.

Great thank you very much @BPScott I can confirm that it is working as intended in eslint-plugin-prettier 3.0.1!


Fix incorrect type in some boolean operations on Domain

The type_ attribute of Domain, which tracks whether the domain is of boundary elements or bulk elements, was not being set for domains created from Boolean operations. The type should have passed from the operands to the created Domain (and the operator should check that both operands have matching type).
This PR does the following:

adds tests that detect the bug
removes the default value for the type_ attribute in the constructor, forcing each of the factory functions to explicitly set it
fixes the bug, and puts in the missing type_ check.

Fixes #1281

/style


chore: bump contract builder to version 1.60

1.60 is needed to be able to build the nearcore crates used for unit testing after #820 as can be seen from this failed buildkite https://buildkite.com/nearprotocol/near-sdk-rs/builds/4076#090f7030-7abe-48bf-80a0-95fbce8f323f
This adds more value to https://github.com/near/near-ops/issues/839 since using latest and bumping people's images based on this for updates like this isn't a good pattern. cc @anshal-savla
Also noting that changes like this would break old CI runs on this repo since the toolchain is different and would produce different binaries -- there should be a way to specify the Rust toolchain version on the image tag

Any reason not to use Rust 1.61 that came out today? Regardless, LGTM

Nope, didn't notice it had been released. Will update to that


@material-table/core version 4.3.45 depends on MUI version 5

I'm just raising this as I'm not sure whether this is intentional or not, seeing as you appear to have branches explicitly for mui versions >=5.
As a project still running on mui v4, we now have to explicitly specify material-table/core version 4.3.44 in order to get it to build.

Try the experimental branch v5 with many changes and fixes. Will be the the stable branch soon.


ensure 'left' value is the original css value

https://github.com/d-oliveros/ngSticky/issues/152

@d-oliveros I'm having the same issues.

Thanks @rDr4g0n!


Feature/details page

I like how this is evolving! couple feedback points:

having both the while border around the inner card and a drop shadow is a bit much
the title is pushed too much to the left border
the details box can be more condensed and/or split up into multiple boxes, for example how CrunchBase does this: https://www.crunchbase.com/organization/squadrun
for the URL I would prefer using a slug derived from the dapp name instead of exposing the MongoId; so /dapp/ethereum-games when the Dapp name is 'Ethereum Games'.

yey
On Thu, Apr 27, 2017 at 2:04 AM, Joris Bontje<EMAIL_ADDRESS>wrote:

Merged #40 https://github.com/EtherCasts/state-of-the-dapps/pull/40.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/EtherCasts/state-of-the-dapps/pull/40#event-1059107019,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKrFrwwth0VUqSm_EFz44uQl4_GkYqoUks5rz4dKgaJpZM4Maktx
.

--
Kind Regards
Jr Reyes / Senior Full Stack Software<EMAIL_ADDRESS>/
09179416271


Link broken to trigger template

I get a 404 page when trying to download the trigger JSON template.

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

ID: c24a54d4-aac6-6a24-e07b-548139201f30
Version Independent ID: 13921320-fcc2-cd0c-d021-4739bfa2cda1
Content: How to use Azure Image Builder triggers to set up an automatic image build - Azure Virtual Machines
Content Source: articles/virtual-machines/image-builder-triggers-how-to.md
Service: virtual-machines
Sub-service: image-builder
GitHub Login: @kof-f
Microsoft Alias: kofiforson

@aheusdens
Thanks for your feedback! We will investigate and update as appropriate.

@kof-f
Could you please review add comments on this, update as appropriate.

@aheusdens
Thank you for bringing this to our attention.
I've delegated this to content author @kof-f, who will review it and offer their insightful opinions.

I just checked the link for the trigger template and it opens. It should be downloadable. Please submit a ticket to our team to investigate further here if you're still experiencing this issue.

@aheusdens, Thank you for your feedback. As reviewed by the author, I request you to try reproducing the issue just to make sure it's not your environment specific. Should it occur again, please file an ICM ticket for our team to review and help.
#please-close.


Trailing double under-scores produces Anonymous hyperlink mismatch warning

This issue is mostly seen with macros (such as RCPPUTILS_THREAD_ANNOTATION_ATTRIBUTE__), since they tend to have trailing double under-scores. The warning reads:
line : Error: Anonymous hyperlink mismatch: 1 references but 0 targets.
See "backrefs" attribute for IDs.

The problem here is that exhale takes identifiers verbatim and throws them into their respective .rst files, and double under-scores is used for anonymous hyperlinking in the restructured text format.
The immediate solution is to exclude these identifiers in Doxygen, but I'm opening this issue to track progress on a real fix.

We should rename RCPPUTILS_THREAD_ANNOTATION_ATTRIBUTE__ to something like RCPPUTILS_THREAD_ANNOTATION_ATTRIBUTE_IMPL.  That is standards compliant, and also fixes this particular issue.  Then we can also get rid of the @cond that we are currently using.

Okay, since symbols with double underscores are not standards compliant anyway, I believe this is not a cause for concern anymore.
Feel free to close this issue.

We should rename RCPPUTILS_THREAD_ANNOTATION_ATTRIBUTE__ to something like RCPPUTILS_THREAD_ANNOTATION_ATTRIBUTE_IMPL. That is standards compliant, and also fixes this particular issue. Then we can also get rid of the @cond that we are currently using.

Should I transfer this issue to rcpputils?

Should I open an issue in rcpputils? I don't think you can transfer across orgs.

Yeah, I think that makes sense.  I'll close this one and let you open a new one in rcpputils.


update fund amount (+10)

Update the size of the fund following the 10BTC Nervos donation.

Actually this amount is not regularly updated but right now it's<PHONE_NUMBER>6 BTC https://blockstream.info/address/bc1qecw954uappnwhle6tmafqskn6vxmpr6lmmuwfwldphfxplcshgnssy9kmx

Actually this amount is not regularly updated but right now it's<PHONE_NUMBER>6 BTC https://blockstream.info/address/bc1qecw954uappnwhle6tmafqskn6vxmpr6lmmuwfwldphfxplcshgnssy9kmx

Alright.
And while I'm at it, is the grin balance displayed somewhere so it can be updated without calculating from the txs log?

No unfortunately the grin node is maintained by @yeastplume and I don't think there is a way to do it automatically. Maybe some wizardry is possible.

Thanks for the PR @Paouky.
I've opted to only update the balance once per quarter based on the financial transparency reports (which is why they are linked, as proofs). Prior to this, we were updating on an ad-hoc basis which was error prone and inefficient to manage correctly.
I have an action to produce a new report and update it for Q2. The Nervos donation would appear in Q3.
Keeping the amount automatically up to date is something we've yet to support, but is interesting to explore.

@lehnberg Got it. I'm producing useless PRs but at least I'm learning!

No worries! We've all been there 👍


VM password fails

I ran a script to update VM local admin passwords. This works fine running on my own PC using my account, but I get the error below when running it on a Hybrid Worker using a Managed Identity. The authentication step works and I have given the Managed Identity the same RBAC role as my own account. Any ideas?
This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az vm user update
Errors:
'VirtualMachineExtensionsOperations' object has no attribute 'create_or_update'
Traceback (most recent call last):
Local\Temp\pip-unpacked-wheel-pwfpui04\knack\cli.py, ln 233, in invoke
azure\cli\core\commands\__init__.py, ln 659, in execute
azure\cli\core\commands\__init__.py, ln 722, in _run_jobs_serially
azure\cli\core\commands\__init__.py, ln 715, in _run_job
AppData\Local\Temp\pip-unpacked-wheel-s5x_2dzp\six.py, ln 703, in reraise
azure\cli\core\commands\__init__.py, ln 693, in _run_job
azure\cli\core\commands\__init__.py, ln 330, in __call__
pip-unpacked-wheel-c2pcumlb\azure\cli\core\__init__.py, ln 786, in default_command_handler
azure\cli\command_modules\vm\custom.py, ln 2224, in set_user
azure\cli\command_modules\vm\custom.py, ln 2211, in _reset_windows_admin
AttributeError: 'VirtualMachineExtensionsOperations' object has no attribute 'create_or_update'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az vm user update --name {} --resource-group {} --username {} --password {}

Expected Behavior
Environment Summary
Windows-10-10.0.17763-SP0
Python 3.6.8
Installer: MSI

azure-cli 2.18.0

Additional Context

hi @qwordy could you pls help to confirm?

hi @qwordy could you pls help to confirm?

Similar issue https://github.com/Azure/azure-cli/issues/16392

Thanks for this, but I don’t think the suggested solution is relevant as the Hybrid Worker VM is already running Azure CLI 2.18.0.
From: Feiyue Yu<EMAIL_ADDRESS>Sent: 02 February 2021 07:57
To: Azure/azure-cli<EMAIL_ADDRESS>Cc: Simon Wright<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Azure/azure-cli] VM password fails (#16712)
Similar issue #16392https://github.com/Azure/azure-cli/issues/16392
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-cli/issues/16712#issuecomment-771444089, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASUJC7IDVPFCNT27VGGFXODS46V6RANCNFSM4WXDXRLA.
Visit us online www.thameswater.co.uk , follow us on twitter www.twitter.com/thameswater or find us on www.facebook.com/thameswater. We’re happy to help you 24/7.
Thames Water Limited (company number 2366623) and Thames Water Utilities Limited (company number 2366661) are companies registered in England and Wales, both are registered at Clearwater Court, Vastern Road, Reading, Berkshire RG1 8DB. This email is confidential and is intended only for the use of the person it was sent to. Any views or opinions in this email are those of the author and don’t necessarily represent those of Thames Water Limited or its subsidiaries. If you aren’t the intended recipient of this email, please don’t copy, use, forward or disclose its contents to any other person – please destroy and delete the message and any attachments from your system.


Create a Postgres instance and db for RUCIO

Request a new CERN DBOD Postgres instance for all future databases in this project.

A database with the name vre was created and modified as follows:
psql -h <ip-alias> -p <port> -U admin -c '\password'
CREATE USER rucio WITH PASSWORD '';
CREATE DATABASE rucio;
GRANT ALL PRIVILEGES ON DATABASE rucio TO rucio;

The passwords for both users are stored in tbag.
Further, the line host rucio rucio <IP_ADDRESS>/0 md5 had to be added to thepg_hba.conf file in order to allow connections with that user. Changes are tracked in the DBOD WebUI.

[ ] Create a db secret for rucio according to: https://rucio.cern.ch/documentation/database/

A new database instance called vre has been created.
Passwords have been stored in tbag:

dbod_vre_user_admin
dbod_vre_user_rucio

and dbconnect string is stored as a secret in the cluster, so it can be accessed by terraform for example:
set {
    name = "config.database.default"
    value = data.kubernetes_secret_v1.rucio_db_secret.data.dbconnectstring
  }
}


Backports 0.18 pr17

Linter (python dead code) is unhappy

@Munkybooty pls avoid resolving my comments, I'll do it myself when I'm happy with corresponding fixes :)

Oh sorry, I do that to keep track of changes I've done. I just realized I can just minimize them by clicking the window and achieve the desired effect so I'll stick to that. My bad

For all PRs I mentioned as "A requires B" pls re-implement them in the right order "merge A" -> "merge B", not "merge B" -> "merge A" cause doing it the latter way creates a mess. Simply changing the order of existing commits won't work. For example, 14236 (should) drop code in feature_block.py which was added in 14180. You could drop it in 14180 now to fix it but it would make it very hard to review PRs (too many things to keep in mind, too easy to miss smth).

I ended up dropping the 6 prs that were mentioned and redid them in the correct order to make things less confusing. I'm hoping I didn't accidentally miss something while doing so but it should be better now.

I'm assuming #14381 is needed to not fail deadcode linter

So currently a majority of tests fail due to the same error,
AttributeError: '[Insert name of test]Test' object has no attribute 'skip_if_no_wallet'
I don't know if i should handle this in the way that #14236 handles it by deleting it or if there is a different approach to take, because its about 60 tests that have this issue and all of them were included in #14180

pls see https://github.com/UdjinM6/dash/commit/518e93bf10ff5c5962563dc4337660321e52db99 and https://github.com/UdjinM6/dash/commit/365260b9ef8e446dead8efbd453d1d86a72254f5


Work on separator

add a separator option
indent dependency only if separator contains a linefeed

The idea is to be able to customize the output, in my case using umd template,  from :
  if (typeof define === 'function' && define.amd) {
    define(["marionette",
      "underscore"], function (Marionette, _) {
      return (root['State'] = factory(Marionette, _));
    });
  } else if (typeof exports === 'object') {
    // Node. Does not work with strict CommonJS, but
    // only CommonJS-like enviroments that support module.exports,
    // like Node.
    module.exports = factory(require("marionette"),
      require("underscore"));
  } else {
    root['State'] = factory(Marionette,
      _);
  }

to :
  if (typeof define === 'function' && define.amd) {
    define(["marionette",
      "underscore"], function (Marionette, _) {
      return (root['State'] = factory(Marionette, _));
    });
  } else if (typeof exports === 'object') {
    // Node. Does not work with strict CommonJS, but
    // only CommonJS-like enviroments that support module.exports,
    // like Node.
    module.exports = factory(require("marionette"), require("underscore"));
  } else {
    root['State'] = factory(Marionette, _);
  }

I think it's an ok idea. It got me thinking, though. Does formatting actually belong to libumd? What if we used something like js-beautify as a separate pass at tooling (ie. grunt-umd)? This would make libumd smaller and push the formatting aspect to the right place. What do you think?

I think it's an ok idea. It got me thinking, though. Does formatting actually belong to libumd? What if we used something like js-beautify as a separate pass at tooling (ie. grunt-umd)? This would make libumd smaller and push the formatting aspect to the right place. What do you think?

@bebraw I haven't heard about js-beautify before. I agree it will be much better as libumd would only does one thing.
Closing this issue in favor of a js-beautify move.

@stephanebachelier Do you think we should drop indent option while at it? Deferring formatting to js-beautify would allow this. We would not give any guarantees about formatting of libumd after that but instead point out this option.

@stephanebachelier I ended up dropping indent. Just need to make Saucelabs widget work, perhaps test a bit more and a new release should be good to go.


Does not work within CodePipeline

This aspect will not currently work when you are using the CodePipeline for doing synthesizing, either directly of via the pipelines/CodePipeline construct.
The root cause is because CodePipeline's source actions transfer the code assets to CodeBuild and does not carry the .git metadata directory with it.
If you try to use this construct, it will throw an error during the synth steps:
Error: No .git folder found

There are a few ways I think this could be handled:

Do not throw the error, produce a warning instead. I don't love this because it likely will result in confusion, like "why isn't my stuff tagged" and it won't be immediately clear that you have to go to the CodeBuild logs to see why.
Treat the request the same way imports work, and use a local cache (like context, but not cause context isn't easily accessible) to store the value so it's not re-read during CICD builds.

There is a workaround that helps, but is not perfect. Add the option to the input connection object, codeBuildCloneOutput: true.
    const pipeline = new CodePipeline(this, 'Pipeline', {
      synth: new ShellStep('Synth', {
        input: CodePipelineSource.connection('Defiance-Digital/cdk-aspects-tester', 'main', {
          connectionArn: 'arn:aws:codestar-connections:us-east-1:00001111222:connection/6437fe74-41e3-4ad3-8fb5-fcfb867b66da',
          codeBuildCloneOutput: true,
        }),
        commands: [
          'yarn install --frozen-lockfile',
          'yarn build',
          'npx cdk synth',
        ],
      }),
    });

Internally we have repo's that use cdk pipelines to synth and deploy stacks via codepipeline. The way we tag all resources on stacks that are deployed via codepipeline stages are done like so:
import { Stack, Aspects, TagManager, IResource } from 'aws-cdk-lib';
import { Construct } from 'constructs';

/**
 * Tag all supported resources within an application.
 *
 * CDK will propagate tags too all resources that support it.
 */
export function tagResources(scope: Construct, tags: (stack: Stack) => Record<string, string>): void {
  Aspects.of(scope).add({
    visit(construct: IResource) {
      if (TagManager.isTaggable(construct)) {
        // We pick the last stack in chain to support stages where
        // there are multiple stacks.
        const allStacks = construct.node.scopes.filter((it): it is Stack => Stack.isStack(it));

        const stack = allStacks.length > 0 ? allStacks[allStacks.length - 1] : undefined;
        if (stack != null) {
          for (const [key, value] of Object.entries(tags(stack))) {
            construct.tags.setTag(key, value, 100, true);
          }
        }
      }
    },
  });
}

for a new cdk pipeline stage:
      // Tags all the resources in the target account
      tagResources(awsAccount, (stack) => ({
        customer: 'customer-name',
        stage: awsAccount.stageName,
      }));


change dict loading mechanism from internal static to server extension

Changing the loading strategy from internal webpack loading to a free customisable  server extension solution.
Closes #69.
Closes #66.

Sorry that it took me a while to get back. I improved this approach in https://github.com/jupyterlab-contrib/spellchecker/pull/74. I will merge this PR now and let's review the changes proposed in #74 next.


pip install tensorrt_llm --extra-index-url https://pypi.nvidia.com --extra-index-url https://download.pytorch.org/whl/cu121

PS C:\ai\TensorLLM> pip install tensorrt_llm --extra-index-url https://pypi.nvidia.com --extra-index-url https://download.pytorch.org/whl/cu121
pip : DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\addict-2.4.0-py3.11.egg is deprecated. pip 24.3 will enforce
this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
At line:1 char:1

pip install tensorrt_llm --extra-index-url https://pypi.nvidia.com -- ...

  + CategoryInfo          : NotSpecified: (DEPRECATION: Lo...ip/issues/12330:String) [], RemoteException
  + FullyQualifiedErrorId : NativeCommandError

DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\aiofiles-23.2.1-py3.11.egg is deprecated. pip 24.3 will enforce this
behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\ffmpy-0.3.1-py3.11.egg is deprecated. pip 24.3 will enforce this
behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\gevent-23.7.0-py3.11-win-amd64.egg is deprecated. pip 24.3 will
enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\geventhttpclient-2.0.2-py3.11-win-amd64.egg is deprecated. pip 24.3
will enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\gradio-3.40.1-py3.11.egg is deprecated. pip 24.3 will enforce this
behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\gradio_client-0.4.0-py3.11.egg is deprecated. pip 24.3 will enforce
this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\grpcio-1.57.0-py3.11-win-amd64.egg is deprecated. pip 24.3 will
enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\httpx-1.0.0b0-py3.11.egg is deprecated. pip 24.3 will enforce this
behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\importlib_metadata-6.8.0-py3.11.egg is deprecated. pip 24.3 will
enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\importlib_resources-6.0.1-py3.11.egg is deprecated. pip 24.3 will
enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\mdit_py_plugins-0.3.3-py3.11.egg is deprecated. pip 24.3 will
enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\mmengine-0.8.4-py3.11.egg is deprecated. pip 24.3 will enforce this
behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\opencv_python-<IP_ADDRESS>-py3.11-win-amd64.egg is deprecated. pip 24.3
will enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\orjson-3.9.5-py3.11-win-amd64.egg is deprecated. pip 24.3 will
enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\platformdirs-3.10.0-py3.11.egg is deprecated. pip 24.3 will enforce
this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\pybind11-2.11.1-py3.11.egg is deprecated. pip 24.3 will enforce this
behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\pydub-0.25.1-py3.11.egg is deprecated. pip 24.3 will enforce this
behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\pygments-2.16.1-py3.11.egg is deprecated. pip 24.3 will enforce this
behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\python_multipart-0.0.6-py3.11.egg is deprecated. pip 24.3 will
enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\python_rapidjson-1.10-py3.11-win-amd64.egg is deprecated. pip 24.3
will enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\quant_cuda-0.0.0-py3.11-win-amd64.egg is deprecated. pip 24.3 will
enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\rich-13.5.2-py3.11.egg is deprecated. pip 24.3 will enforce this
behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\semantic_version-2.10.0-py3.11.egg is deprecated. pip 24.3 will
enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\tiktoken-0.4.0-py3.11-win-amd64.egg is deprecated. pip 24.3 will
enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\tomli-2.0.1-py3.11.egg is deprecated. pip 24.3 will enforce this
behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\tritonclient-2.36.0-py3.11.egg is deprecated. pip 24.3 will enforce
this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\websockets-11.0.3-py3.11-win-amd64.egg is deprecated. pip 24.3 will
enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at c:\users\real\appdata\local\programs\python\python311\lib\site-packages\yapf-0.40.1-py3.11.egg is deprecated. pip 24.3 will enforce this
behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
Looking in indexes: https://pypi.org/simple, https://pypi.nvidia.com, https://download.pytorch.org/whl/cu121
Collecting tensorrt_llm
Using cached tensorrt-llm-0.7.1.tar.gz (6.9 kB)
Preparing metadata (setup.py): started
Preparing metadata (setup.py): finished with status 'error'
error: subprocess-exited-with-error
python setup.py egg_info did not run successfully.
exit code: 1
[6 lines of output]
Traceback (most recent call last):
File "", line 2, in
File "", line 34, in
File "C:\Users\Real\AppData\Local\Temp\pip-install-u3y4yvyp\tensorrt-llm_88a6dbc662754cf0a41c985e2110d1ec\setup.py", line 90, in
raise RuntimeError("Bad params")
RuntimeError: Bad params
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
Encountered error while generating package metadata.
See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
PS C:\ai\TensorLLM>

@realhaik Do you still have the question? If not, we will close it soon.


Fix AttributeError: 'Namespace' object has no attribute 'verbose'

Proposed changes:

python -m rasa_core.server -d models/dialogue -u models/nlu/current is broken and gives an error: AttributeError: 'Namespace' object has no attribute 'verbose'

Status (please check what you already did):

[x] made PR ready for code review
[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog

Very good point, thanks

Just did another small fix, should be fixed on master now :+1:


OrderMap 1.0 Roadmap

Must have

[ ] Full consistency check list should be complete and remaining discrepancies should be fixable backwards compatibly or marked as not important (#19)
[x] Mutable keys #7 #39
[x] Settle crate name #14 Settle removal semantics #15  (and split crate for full insertion order #12)
[x] Move map stuff to map:: submodule (like set::) #60

Nice to have
(can be added backwards compatibly)

[ ] Full consistency (#19). Being drop in is good, but some of the details don't matter much, you can be effectively drop in without being 100% type by type compatible.
[x] OrderSet #8
[x] Order preserving retain #56
[ ] Every public item has documentation

At Release

Blog post about the name change and explain the properties of the data structure

Crate name question is decided, IndexMap from #14


Type merge error in Databricks source

The following error occurs when trying to upload a file to databricks:

It is probably due to the object type in the DataFrame. This type allows the rows of a column to contain mixed values, which can cause this error.

Closed by #701


If the uri attribute in the app.xml doesn't end with '/', things blow up.

It's a little thing but it would be nice if the slash was added if not there.

Thanks for reporting this, it has actually bothered me as well, just didn't get around to fixing it. I will take care of this on monday :)


Add exec command

When embedding standalone static binaries in a docker container, it feels nice to use the empty "scratch" docker image as a starting point. However, this fails when also wanting secretary support, since the current workflow requires a shell.
This PR adds the support for secretary exec -- cmd [args..] which will decrypt all environment variables and all command line arguments without requiring an embedding shell to do the work.

Codecov Report

Merging #19 into master will decrease coverage by 3.72%.
The diff coverage is 20.87%.

@@            Coverage Diff             @@
##           master      #19      +/-   ##
==========================================
- Coverage   51.48%   47.75%   -3.73%
==========================================
  Files           8        8
  Lines         606      691      +85
==========================================
+ Hits          312      330      +18
- Misses        254      317      +63
- Partials       40       44       +4

Impacted Files
Coverage Δ

main.go
0% <0%> (ø)
:arrow_up:

box.go
61.01% <50%> (-1.49%)
:arrow_down:

commands.go
78.68% <75%> (-1.32%)
:arrow_down:

marathon.go
83.67% <0%> (-0.33%)
:arrow_down:

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 ca56ce1...feaa061. Read the comment docs.

@dezmodue or other @meltwater/foundation members. Can we merge this and release a new version of secretary? It would enable us to more easily use non-meltwater base images that don't necessarily have a shell.


Big endian platform not detected by farmhash

We are building TensorFlow on big endian system and farmhash is being downloaded as external dependency.
Few tests are failing on our system ( s390x platform) as it's not getting detected as big endian by farmhash. We tried setting the macro FARMHASH_BIG_ENDIAN for s390x in farmhash.cc file  and with this change the tests are passing .
The farmhash/README mentions a known issue for big endian that
to make FarmHash work properly on big-endian platforms you may need to modify the wrapper .h file.
Is farmhash.cc  right place to add a macro for our platform?
(We have seen macros used in config.h for big endian but doesn't seem to work for s390x )

In general, the tests are extremely unlikely to pass due to luck, so if you have a change that makes the tests pass then it should be safe to use.
If you don't want to modify the code, you might try compiling with WORDS_BIGENDIAN defined (e.g., g++ -DWORDS_BIGENDIAN). Or FARMHASH_BIG_ENDIAN.

Is the WORDS_BIGENDIAN workaround robust enough for distribution? I'm about to fix the farmhash build failure for Debian. As reported here: https://github.com/google/farmhash/issues/12

How about this patch?
diff --git a/src/farmhash.h b/src/farmhash.h
index d041488..52be397 100644
--- a/src/farmhash.h
+++ b/src/farmhash.h
@@ -292,4 +292,27 @@ inline uint128_t Fingerprint128(const Str& s) {

 }  // namespace NAMESPACE_FOR_HASH_FUNCTIONS

+// Detect big-endian architectures and inject FARMHASH_BIG_ENDIAN flag.
+#if defined (__mips__)
+  #if defined (__MIPSEB__)
+    #define FARMHASH_BIG_ENDIAN
+  #elif defined (__MIPSEL__)
+  #else
+    #error MIPS no endian specified
+  #endif
+#elif defined (__s390__) || defined (__s390x__)
+  #define FARMHASH_BIG_ENDIAN
+#elif defined (__powerpc__) || defined(__powerpc64__)
+  #if defined (__LITTLE_ENDIAN__)
+  #else
+    #define FARMHASH_BIG_ENDIAN
+  #endif
+#elif defined (__hppa__)
+  #define FARMHASH_BIG_ENDIAN
+#elif defined (__sparc__)
+  #define FARMHASH_BIG_ENDIAN
+#elif defined (__alpha__)
+  #define FARMHASH_BIG_ENDIAN
+#endif // end detect big-endian archs
+
 #endif  // FARM_HASH_H_

@geoffpike @Nayana-ibm

@CDLuminate The patch looks good to me.
Tests are passing on s390x platform with above code changes.
Also, we had tried executing tests with --copt=-DWORDS_BIGENDIAN and it works too.

@Nayana-ibm Thank you very much for the confirmation.

@CDLuminate Any idea by when this will be merged?

@Nayana-ibm I'm currently asking several Debian Developers for review. If it looks good to them, I'll update the Debian package with this patch and create a PR.

This patch should be better for linux:
diff --git a/src/farmhash.h b/src/farmhash.h
index d041488..1bfcc46 100644
--- a/src/farmhash.h
+++ b/src/farmhash.h
@@ -292,4 +292,24 @@ inline uint128_t Fingerprint128(const Str& s) {

 }  // namespace NAMESPACE_FOR_HASH_FUNCTIONS

+/* gently define FARMHASH_BIG_ENDIAN when detected big-endian machine */
+#if defined(__BIG_ENDIAN__)
+  #if !defined(FARMHASH_BIG_ENDIAN)
+    #define FARMHASH_BIG_ENDIAN
+  #endif
+#elif defined(__LITTLE_ENDIAN)
+  // nothing for little-endian
+#else
+  #include <endian.h> // libc6-dev, GLIBC
+  #if defined(__BYTE_ORDER) && (__BYTE_ORDER == __BIG_ENDIAN)
+    #if !defined(FARMHASH_BIG_ENDIAN)
+      #define FARMHASH_BIG_ENDIAN
+    #endif
+  #elif defined(__BYTE_ORDER) && (__BYTE_ORDER == __LITTLE_ENDIAN)
+    // nothing for little-endian
+  #else
+    #error "Unable to determine endianness!"
+  #endif /* __BYTE_ORDER__ */
+#endif /* __BIG_ENDIAN__ */
+
 #endif  // FARM_HASH_H_

The above patch doesn't consider the case of BSD.
This link is useful: http://esr.ibiblio.org/?p=5095

@CDLuminate  Is this patch is reviewed? Any idea by when this will be merged?

@Nayana-ibm The patch is already used in the Debian package[1], but it failed on s390x.
Actually that patch fixed only the powerpc and ppc64 build. see [2].
[1] https://tracker.debian.org/pkg/farmhash
[2] https://buildd.debian.org/status/logs.php?pkg=farmhash&suite=experimental


"Nx Generate (Ui)" doesn't show workspace-scematics

I have created several workspace generators that I can run in CLI like so:
nx workspace-generator app bla

But I don't see it in the context menu of "Nx Generate (Ui)":

Hello,
can you provide a sample repo with your custom generator?
I  will take a look.
Thanks.

Thanks, there you go:
https://github.com/vitalybe/nx-test

The plugin does not look in tools/generators support only tools/schematics.
As a workaround rename the directory generators to schematics and restart your IDE.

I will fix that on the next version.

It did help somewhat - It does appear now. However, trying to run the generator like that results in:
/Users/vitalyb/.volta/bin/node<EMAIL_ADDRESS>generate workspace-schematic:lib --name=bla
Unable to resolve workspace-schematic:lib.
Cannot find module 'workspace-schematic/package.json'
Require stack:
-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>Done

The command could not be run as nx workspace-schematic lib --name=test --no-interactive  ?
It's not working too with Nx console vscode or in terminal.

That's right, I use it like that:
nx g lib --name=bla
[image: image.png]
On Sun, Jul 18, 2021 at 4:21 PM iguissouma @.***> wrote:

The command could not be run as nx workspace-schematic lib --name=test
--no-interactive ?
It's not working too with Nx console vscode or in terminal.
[image: Screenshot 2021-07-18 at 13 42 53]
https://user-images.githubusercontent.com/9085108/126065740-5b3262d6-ddde-479b-b688-b154470fbffa.png
[image: Screenshot 2021-07-18 at 13 44 37]
https://user-images.githubusercontent.com/9085108/126065750-a90d4393-ca41-41ef-acfc-cb200c24f37a.png
[image: Screenshot 2021-07-18 at 13 44 37]
https://user-images.githubusercontent.com/9085108/126065996-e097a64d-b868-48a6-ab6b-023b5896aa02.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/iguissouma/nx-console-idea-plugin/issues/28#issuecomment-882055459,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAOYDOBCXERJR2NKRKPSUITTYLIOLANCNFSM5ANAW74Q
.

--

Vitaly

I don't know if generators on generators/tools directory should be called with workspace-generators!

From NX documentation it seems that schematics/generators can be used interchangeably and mean the same thing. I think schematics was the older terminology and they are transitioning now to use generators.
I use it like so:
nx g app --name=bla

nx g workspace-schematic app --name=bla => ok
nx g workspace-schematic:app --name=bla => ko
I'm using the second one for all schematics/generators from node modules or generators/tools

nx g workspace-schematic app --name=bla => ok

Something is off. This works for me too, but it doesn't use my generator at all, in fact this works too:

nx g workspace-schematic sjkgfhsdfjkgh --name=bla

For both it just generates a new generator template:

Sorry, I'm not very familiar with schematics/generators.
I got it working fine in vscode so I'll be able to do same thing on jetbrains IDE side.

It should be fixed on the new version.
Please test and confirm.

Seems to be working great now, thanks!


Does hub pull-request support ssh now?

Wonder to know whether hub pull-request support ssh in latest release?

Hub commands like hub issue and hub pull-request all make HTTPS requests to the GitHub API, and our API is only accessible over HTTPS. Therefore, SSH is not supported in any of these commands. SSH is only supported in git protocol when cloning/pushing/pulling, but this is all regular git functionality that is completely separate from hub.
More information here: https://github.com/github/hub/issues/1644#issuecomment-359002547

Ok, thank you very much.


DB upgrades can result in race condition

In the SugarApp class the onCreate() method looks like this:
@Override
public void onCreate() {
    super.onCreate();
    SugarContext.init(this);
}

Since super.onCreate() is being called first, it means that the launcher activity starts, then SugarContext.init(this) is called. This is creating problems in my app because my Activity is able to hit its onCreate() and onStart() methods before the upgrade is even started. This has been crashing my app and I wonder if this has occurred for anyone else and if you have a solution that you can suggest.
Would calling SugarContext.init(this) before super.onCreate() guarantee that upgrades would occur before Activity code is run?

@hoda0013,
you can create a class extending SugarApp and override onCreate method as you wish.
Don't forget to declare this class in your Android Manifest.

I currently am extending SugarApp with a class called MyApplication.
One thought I had was to call SugarContext.init(this) in the onCreate() method of MyApplication and then call super.onCreate(). It looks like that would take care of the upgrade before any of my Activities start.
However, I'm having trouble getting a reference to SugarContext from MyApplication. Which is weird because it looks like SugarContext is a public class and I can get a reference to several of the other public classes in the com.orm package.

Disregard my last comment. I cloned the most recent branch instead of v1.3. v1.3 looks to be a bit different (SugarContext isn't even a class).

Is this still an issue for you or does the beta jar resolve this? Moving forward, what's in the beta jar will what 1.4.0 has.

I wasn't able to get database migrations to work for me using v1.3. It seemed that when the app would startup that the onCreate() of the application class would kick off the migration, but that it would happen 'in parallel' with the activity and fragment life cycles. What I was seeing was that the migration wouldn't have started until after one of my activities had completed a networking operation and would be trying to persist data and eventually result in a crash with the message 'table not found'.
This may just be user error, but I was not able to figure out how to do a migration because of this.

@hoda0013 try to use the master version


[Bug] Stack errors involving WorldEdit

Information
Full output of /abook about:

Server log (upload logs/latest.log to Gist):
https://gist.github.com/pkhodadi/2be95c7bb2a7ebdbca1c83918a2d2d18#:~:text=[09%3A28%3A49,Thread.java%3A833)%20~%5B%3F%3A%3F%5D
AstralBooks config (upload plugins/AstralBooks/config.yml to Gist):
https://gist.github.com/pkhodadi/6c0be1ab38a3ae41ec2b1f6aa3a263c9
Details
Using commands with FastAsyncWorldEdit sends stack errors.

Thank you for your report. It's gonna be fixed in the next release.


Add an alert component

Whenever there's an error, like entering an invalid or existing username, a native alert is called from the browser.
It would be better if there were a reusable component that displays an alert with matching UI style with the rest of the website. The alert could be called with a custom message.

Like a Toast Message right?


change homebrew url

note that I made a new prelibgit2 branch for this and made it the default on github.
master (also saved as libgit2dev, currently equivalent) has libgit2 work on it
which doesn't totally work yet so shouldn't be tagged. this may not be able to do
migrations of existing installs properly, but I think those are hosed right now anyway

Changes Unknown when pulling 909a316294422fa8175bcd3885ff11534c5f10f1 on tk/url into ** on prelibgit2**.

I'm going to merge and tag this. It would be great if someone who actually used a mac could help out with maintenance here.


[DOCS] Add header image to README.md

Is your feature request related to a problem? Please describe.
No, it's just an improvement to README.md. Add header image to the top of the readme file. Which makes the README.md file look attractive.
Describe the solution you'd like
I used a tool called GitHub Socialify to generate the following header images :point_down:.

Customize This :point_up:

Customize This :point_up:

Describe alternatives you've considered
if you don't want to use tool generated image. You can create it from scratch :slightly_smiling_face:.
Additional context
No additional context.

The first one with dark theme looks great 👍

Done :+1:


experiment: alpha/beta types in a single package with export paths

wip
The scenario
We want to roll out some new APIs slowly over time. We intend to use the TSDoc @alpha and @beta tags to enable us to produce different types files that have some APIs trimmed out (this process is called "dts trimming").
However, there's only one types field in package.json, so we're stuck shipping different packages for different API types - e.g. an alpha-types package and a beta-types package, in addition to the standard package. While the user experience for customers isn't that bad, shipping different packages that differ only in superficial ways seems wasteful at best, and it also requires us to change packages in the CI pipeline far more than we do today. It would be far better if the package.json in the repo was almost exactly what we ship to npm.
The concept
The idea is to use the exports field in package.json to output different paths that point to the same code, but different types. When importing from the package using a path like import { API } from "@scope/package/beta"; the result would be the beta API, while the default path would omit those APIs.
The exports field
Using this idea, the exports field for a CJS-and-ESM package would look something like this:
"exports": {
  ".": {
    "import": {
      "types": "./lib/tree2-untrimmed.d.ts",
      "default": "./lib/index.js"
    },
    "require": {
      "types": "./dist/tree2-untrimmed.d.ts",
      "default": "./dist/index.js"
    }
  },
  "./alpha": {
    "import": {
      "types": "./lib/tree2-alpha.d.ts",
      "default": "./lib/index.js"
    },
    "require": {
      "types": "./dist/tree2-alpha.d.ts",
      "default": "./dist/index.js"
    }
  },
  "./beta": {
    "import": {
      "types": "./lib/tree2-beta.d.ts",
      "default": "./lib/index.js"
    },
    "require": {
      "types": "./dist/tree2-beta.d.ts",
      "default": "./dist/index.js"
    }
  }
},

Once this change is implemented, we won't need the setPackageTypesField flub command, right?

Superseded by other PRs.


System.ArgumentOutOfRangeException: ''

What can we do for you?
When I'm using GetDirectoryListing for the second time, it shows me an empty exception. What's wrong?

Please use this template if you find a bug.
Or please tell us which version of nuget package and dotnet platform you used.

is this a bug or i'm doing something wrong??

It's a bug. But I don't know how to fix it. You can renew the class and it will functional...

try to call service.Open(), like this
SyncService service = new SyncService(client, device);
var a = service.GetDirectoryListing("/");
service.Open();
var b = service.GetDirectoryListing("/sdcard");

Sorry, it's not functional 🤣


DB2 for i 7.3 support?

Hi There,
I'm helping an organization plan an upgrade to i 7.3 from i7.1, and would like to know if the db2 connector will continue to be supported for the new version. Can you confirm?
Thanks!
Michael

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

ID: 2e62611c-d499-c2ab-c2f5-663cd6911757
Version Independent ID: ad3a4be7-c0dc-7857-798f-1c7206cc1176
Content: Copy data from DB2 using Azure Data Factory
Content Source: articles/data-factory/connector-db2.md
Service: data-factory
GitHub Login: @linda33wj
Microsoft Alias: jingwang

@MichaelHallak
Thanks for the feedback! We are currently investigating and will update you shortly.

@linda33wj is this something that can be added to the documentation yet?

Thanks folks; I'm looking forward to hearing what you come up with.

@jason-j-MSFT - any word?

@jason-j-MSFT @linda33wj I'm also interested in ADF support for DB2 7.3. Please let us know!

Thank you for your interest in ADF!  We are going to update documentation and explicitly mentioned that IBM DB2 for i 7.3 is supported.
#please-close

Only Microsoft employees can manage issues via commenting in this repo.

Thanks all for your feedback on DB2 connector! We have updated the doc to cover DB2 for i7.3 support.
#please-close


Adjust image loading strategy

Checklist
Use fetchpriority for LCP images:

[x] fetchpriority="high" for

first slide of announcement;
first N feed items;

[x] fetchpriority="low" for:

GIF avatars;
rest of the slides of announcement;
rest of the feed items;

Progressive loading:

For GIF image:

load status format (?anim=false) first
load GIF format once other prioritized resources are loaded

Refs

https://www.notion.so/matterslab/matters-news-4c3fe7c774ed4c939c38f49c2632891f?pvs=4#ce468d7fe17045f1b8b4ace58df2f249
https://vaihe.com/quick-seo-tips/using-fetchpriority-with-images/
https://github.com/thematters/developer-resource/issues/253

closed in #3995


Valet's helper overrides Laravel's helper

Laravel Version: 5.5.0
PHP Version: 7.1
Database Driver & Version: MySQL 5.7

Description:
The tap method of Laravel 5.5 cannot be called from unit test, it will use the method that in Valet's helpers.
The problem only exists when Laravel Valet is installed.
But It works well when I call tap from tinker.
Steps To Reproduce:

Create a fresh Laravel 5.5 project.
Install Laravel Valet.
Call the tap method from unit tests with no parameters.
Get the following exceptions that says 2 parameters expected.

PHPUnit 6.3.0 by Sebastian Bergmann and contributors.

.E                                                                  2 / 2 (100%)

Time: 90 ms, Memory: 10.00MB

There was 1 error:

1) Tests\Unit\ExampleTest::testBasicTest
ArgumentCountError: Too few arguments to function tap(), 0 passed in /Users/rway7/Projects/laravel55/tests/Unit/ExampleTest.php on line 17 and exactly 2 expected

/Users/rway7/.composer/vendor/laravel/valet/cli/includes/helpers.php:143
/Users/rway7/Projects/laravel55/tests/Unit/ExampleTest.php:17
/Users/rway7/.composer/vendor/phpunit/phpunit/src/TextUI/Command.php:212
/Users/rway7/.composer/vendor/phpunit/phpunit/src/TextUI/Command.php:141

ERRORS!
Tests: 2, Assertions: 1, Errors: 1.

I'd suggest that you don't use a global PHPUnit binary, use the one per project since different phpunit versions might be required for each app.
Maybe add an alias in your .bashrc file like so:
phpunit=vendor/bin/phpunit


devcontainer exec overwrites characters in the terminal when there are wrapped output lines

I've tried this with both bash and zsh. They are both broken, but in slightly different ways; I think the breakage in bash is worse, but they both are not pretty.
Steps to reproduce and demonstrate what I mean:

Create a bash/zsh process in a devcontainer attached to a tty.
Press enter repeatedly so that you are at the bottom of the tty in your terminal emulator.
Type in a long command that overflows the line length of your terminal emulator.
Run that command.
Next step depends on the shell being used:

For bash, press the up arrow, and observe how the overflowing command does not appear fully, and how another line of text in the terminal disappears. If you now repeatedly press the down and up arrows to recall a command from history and clear it, you will see that for each of the pairs of arrow key presses, one line of text that was previously in the terminal vanishes.
For zsh, press the up arrow, then the down arrow. You will see that the cursor is two cells further into the line than it should be; if you go up twice and then down, two characters from a previous command will appear in those two cells, and will not change until you force a new line to be sent to the terminal.

I believe that this is related to this problem, though the linked original talks specifically about non-printable characters, and the arrow is definitely printable. Nevertheless, with it being a multi-byte character, it appears to me that using the solution normally used for the non-printable characters, i.e. wrapping it with \[\] in PS1, fixes the issue for bash. I am unsure if this is a viable solution to this problem, which is why I'm filing this as an issue and not with a specific patch. I assume that the zsh method of escaping the characters in PROMPT would similarly work, but I have not verified this.

@chrmarti can you take a look at this?

I can also reproduce with docker exec. Does this indicate that the PS1 value needs additional wrapping?

I can also reproduce with docker exec. Does this indicate that the PS1 value needs additional wrapping?

I checked all of the escapes in https://github.com/devcontainers/features/blob/main/src/common-utils/scripts/bash_theme_snippet.sh is they look correct to me. All of the non-printable sequences are wrapped in square brackets.
I was not able to reproduce in pure ssh connections (using the sshd feature and forwarding the ssh port as described here) or in VS Code integrated terminals which makes me think it's not an issue in the shell profile. Perhaps it's a bug in docker exec, which would explain why it also shows up in devcontainer exec which wraps docker exec.

Here's a more minimal repro:
docker run --rm -it mcr.microsoft.com/devcontainers/base:ubuntu
echo ➜

Then hit the up and down arrow back and forth and notice one character is overwritten at a time.
https://github.com/devcontainers/cli/assets/746020/d4e508ce-ef23-4677-b901-885723bb7bbe
If you clear out the profile and set it to a minimal profile config before doing the echo, the same thing happens:
docker run --rm -it mcr.microsoft.com/devcontainers/base:ubuntu
export PS1="\s-\v\$"
echo ➜

https://github.com/devcontainers/cli/assets/746020/45c50678-c2ca-4d59-87b9-b2f6caedaa57
Similarly, spawning the initial bash shell with --norc also still reproduces the issue.
docker run --rm -it mcr.microsoft.com/devcontainers/base:ubuntu /bin/bash --norc
echo ➜

The UTF-8 character in the output seems to be messing up width calculation somehow. If you try with the ubuntu:latest image, it doesn't reproduce, but it also doesn't accept unescaped UTF-8 characters as input on the terminal without installing additional locales, so I wonder if that's related.
docker run --rm -it ubuntu:latest
apt update && apt install locales
dpkg-reconfigure locales
<enter 160 and then 3 on the options>
export LC_ALL=en_US.UTF-8
export LANG=en_US.UTF-8
export LANGUAGE=en_US.UTF-8
bash
echo ➜

I did notice that changing the locale configured in mcr.microsoft.com/devcontainers/base:ubuntu from POSIX to en_US.utf8 seems to fix the issue, but it's not entirely clear why when the ubuntu:latest image also comes configured out of the box with the POSIX locale which works fine.
docker run --rm -it mcr.microsoft.com/devcontainers/base:ubuntu
export LC_ALL=en_US.utf8
bash
echo ➜

I don't know enough about how locales are configured to explain this difference, and it's still not clear to me why this only reproduces in docker exec and devcontainer exec rather than in shells spawned through other tools.

The line length is definitely wrong in the base devcontainers image when no locale is explicitly set.
bash-5.1# echo ➜ | wc --max-line-length
0
bash-5.1# export LC_ALL=en_US.utf8
bash-5.1# echo ➜ | wc --max-line-length
1

Compared to ubuntu:latest which shows the correct value without setting the locale explicitly:
bash-5.1# echo ➜ | wc --max-line-length
1

Knowing that it's a locale issue also helps explain why it works in VS Code interactive terminals and SSH shells. In VS Code and SSH, LANG=en_US.UTF-8 is being applied which also fixes the issue.
At this point, it's definitely not a CLI bug. It's either in the image or the common-utils feature, although it's tied to the locales rather than the PS1 escaping. Transferring back to the features repo for now.


[Feed] Show if post is part of community

Need to show on the homepage when a post is a part of a specific community

One problem is a post can have multiple labels that belong to multiple communities. We don't have a mechanism to limit that. If it's fine to allow and show a post belong to several communities, then this is not a big deal and I estimate it to be one day.


Slowness in receiving "data" event

Hi,
My environment is:
OS: Ubuntu 16.04.01
Kernel: 4.4.0-75-generic
Node: 4.2.3
Redis Server: 3.2.5
rsmq: 0.8.2
rsmq-worker: 0.5.2

I have not made any changes to the library source. The queuing performs consistently satisfactorily:
[ RSMQ ] Time Taken:  28
[ RSMQ ] Time Taken:  3
[ SQS ] Time Taken:  303
[ SQS ] Time Taken:  214
[ RSMQ ] Time Taken:  3
[ RSMQ ] Time Taken:  3
[ RSMQ ] Time Taken:  3
[ SQS ] Time Taken:  628
[ SQS ] Time Taken:  455
[ SQS ] Time Taken:  207
[ RSMQ ] Time Taken:  4
[ SQS ] Time Taken:  214
[ RSMQ ] Time Taken:  4
[ SQS ] Time Taken:  192
[ RSMQ ] Time Taken:  6
[ SQS ] Time Taken:  244
[ RSMQ ] Time Taken:  5
[ SQS ] Time Taken:  198
[ RSMQ ] Time Taken:  4
[ SQS ] Time Taken:  184

However, the event takes too long to reach the worker.
Though the Redis server is local, rsmq-worker takes an awfully long time to receive the "data" event and process it.
var RSMQWorker = require( "rsmq-worker" );
var options =
{
  invisibletime: 900,                    // hide received message for 900 sec
  maxReceiveCount: 1,              // only receive a message once until delete
  autostart: true,                         // start worker on init
  customExceedCheck: exdCheckFn
};
var worker = new RSMQWorker( "testqueue", options);
worker.on( "data", function( msg ){
 // do stuff
});

For a set of 10 messages that were set in SQS and redis at the same time:
[ SQS ] Total Time taken for processing at site 13
[ SQS ] Total Time taken for processing at site 14
[ SQS ] Total Time taken for processing at site 38
[ SQS ] Total Time taken for processing at site 27
[ SQS ] Total Time taken for processing at site 139
[ SQS ] Total Time taken for processing at site 20
[ SQS ] Total Time taken for processing at site 455
[ SQS ] Total Time taken for processing at site 416
[ SQS ] Total Time taken for processing at site 1375
[ SQS ] Total Time taken for processing at site 125
[ RSMQ ] Total Time taken for processing at site 3428
[ RSMQ ] Total Time taken for processing at site 6190
[ RSMQ ] Total Time taken for processing at site 8980
[ RSMQ ] Total Time taken for processing at site 11767
[ RSMQ ] Total Time taken for processing at site 14532
[ RSMQ ] Total Time taken for processing at site 17331
[ RSMQ ] Total Time taken for processing at site 20097
[ RSMQ ] Total Time taken for processing at site 22852
[ RSMQ ] Total Time taken for processing at site 25590
[ RSMQ ] Total Time taken for processing at site 28347

As you can see even AWS SQS is outperforming it. Are there any obvious settings that I am misconfiguring?

I was waiting for the timeout which is 3 seconds.

I was waiting for the timeout which is 3 seconds.


In the generated RDF, articles year ends with ".0"

Looks like the year is interpreted as a float instead of a int. Results in something like:
"2019.0"^^http://www.w3.org/2001/XMLSchema#gYear

This was caused by one null value in the metadata.  Fixed by filling n/a values of the year column in the matadada tsv file.

Another way to ensure the types of the columns imported into MongoDB would be to alter the header of the  metadata TSV file with included types into the header of the file. For example, for the column year it should be year.int32().  And include --columnsHaveTypes option into mongoimport command.
Reference for the types can be found [here](https://www.mongodb.com/docs/database-tools/mongoimport/#std-label-example-csv-import-types. Examples can be found here
Given that each column header has to be annotated with the type and prior fix of filling the null values to the only integer column, we forgo this step in the Agrovoc use case.


rofi being tiled

Running rofi -modi drun -show results it in being tiled. I'm using the default config for both Hyprland, i.e. from the examples directory, and rofi, i.e. no file on disk.
This is undesired behavior. I expected a floating window on top of all other windows similar to wofi, which is being used by the default config.
Unfortunately, wofi is no longer being maintained thus my preference for rofi. Maybe I am missing an important config? Pretty new to WMs in general.

You can also use windowrule=float,rofi in your hyprland.conf if you're attached to the x11 verision for some reason.

Thank you for the information and the project!

You can also use windowrule=float,rofi in your hyprland.conf if you're attached to the x11 version for some reason.
I used to do this too but it doesn't work anymore though

because rule parsing changed a bit.
open rofi, use hyprctl clients, find the rofi entry and note it's class name. (the first name, it should be "window at xxxxx -> classname:" iirc)
then, adjust your windowrule to look like this:
windowrule=float,^(classname)$

or
windowrule=float,classname


No support for docusaurus v3

Thanks for your work and the addon!
Unfortunately currently the addon doesn't work with docusaurus v3, it would be nice to have such support
NPM won't let you install, because of the peerDeps:
"peerDependencies": {
    "@docusaurus/core": "^2.3.1"
}

Also, it would be nice if this worked with the latest storybooks version (v8).
Perhaps it's the only issue now and updating peerDeps would be enough to make it work.
UPD: tried monkey-patching this package to check if it can be easily adopted for v3, it doesn't seem like this is the case.

@shadowusr  I've forked the repo and patched an update to run with docusaurus 3.2. (the server upgrade that broke this).
You can find it at storybook-n-docusaurus. Note I only fixed the /framework part of this package.
@jodyheavener If you're open to it, I'd love clean this up and PR this back into your branch.    If you don't have time and want to share the load, I'd be open to helping manage this repo.

Awesome.  Great to hear @jodyheavener ! Will do. I'll try to get that out this week.


handleCardAction thows on fail instead of returning error

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
if (paymentStatus === PaymentIntents.Status.RequiresAction) {
  try {
    const {
     error
    } = await this._stripe.handleCardAction(clientSecret)
   console.log(error)
  } catch (e) {
    console.error(e)
  }
}

1/ trigger a 3D Secure using test card
2/ Fail the authorization
3/ returned error is undefined and the error is thrown
Expected behavior
Return the error as the other functions

weird, it seems that it's sometimes returned and sometimes thrown...
i had to wrap it all in a try / catch and throw error in it when it's returned to cover any cases

How are you importing the library? How are you setting this._stripe?
I think you might be importing NativeStripeSDK rather than the top level functions.

there is some legacy code in our app, so i actually inject useStripe return in the class constructor while waiting for a rework on this code.
We just migrated from tipsi so we had to make some withdrawals to do it fast.

Okay, sounds like this is an issue with your specific integration, not the library per se. As you can see, the function does never throw but always return: https://github.com/stripe/stripe-react-native/blob/master/src/functions.ts#L228-L248


asgoel/fix inline instances

Description
I noticed a bug (I think) where the handle action function does not pass through the parent object into the get_inline_instances function. Sometimes, a ModelAdmin will display or not display an inline(s) based on some property of the object itself. So, this function was error'ing out with a unbound model_admin instance since get_inline_instances was coming up with an empty list.
Fixes #(issue)
Checklist

[X] Tests covering the new functionality have been added
[X] Code builds clean without any errors or warnings
[X] Documentation has been updated
[x] Changes have been added to the CHANGELOG.md
[X] You added yourself to the CONTRIBUTORS.md

@escaped let me know if this makes sense

@escaped just following up on this?


Adding support for managed identity for ActionGroups resource type

ARM (Control Plane) API Specification Update Pull Request

[!TIP]
Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!

[ ] New resource provider.
[x] New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix OpenAPI spec quality issues in S360.
[ ] Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

Next Steps to Merge
Next steps that must be taken to merge this PR:

❌ This PR is in purview of the ARM review (label: ARMReview). This PR must get ARMSignedOff label from an ARM reviewer.This PR is awaiting ARM reviewer feedback (label: WaitForARMFeedback).To learn when this PR will get reviewed, see ARM review queue at aka.ms/azsdk/pr-arm-reviewFor details of the ARM review, see aka.ms/azsdk/pr-arm-review
❌ The required check named Swagger LintDiff has failed. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guide

Hi @rkmanda - Since you initially reviewed this same change in the PR branch, could you help review this please? Thanks!
BTW, the Swagger LintDiff failures are not introduced by this change. Thanks!

Thank you, @raosuhas, for reviewing and signing off on the changes. How do I get this merge? Do I need another reviewer to approve? Thank you!
@rkmanda , @akshitgoyal , @avjerafi - could you please help to review this PR? Thank you so much.

Thank you, @raosuhas, for reviewing and signing off on the changes. How do I get this merge? Do I need another reviewer to approve? Thank you!
@rkmanda , @akshitgoyal , @avjerafi - could you please help to review this PR? Thank you so much.

@raosuhas , could you advise me what else do I need to have this merge? The "Swagger LintDiff" failures are not introduced by my changes?
Thank you!

/azp run

Approving suppressions since they are not related to the current PR at all.

Thank you, @raosuhas, for reviewing and signing off on the changes. How do I get this merge? Do I need another reviewer to approve? Thank you!
@rkmanda , @akshitgoyal , @avjerafi - could you please help to review this PR? Thank you so much.

@raosuhas , could you advise me what else do I need to have this merge? The "Swagger LintDiff" failures are not introduced by my changes?
Thank you!

Please follow the instructions here to complete the merge : https://eng.ms/docs/products/azure-developer-experience/design/api-specs-pr/api-specs-pr#get-your-pr-merged

approved


chore: keeps clean method private.

Transaction.Clean is more like an implementation detail on how we build/bootstrap a new transaction and we shouldn't expose such methods, otherwise there is not any use case where one needs to clean a transaction.

Thank you for contributing to Coraza WAF, your effort is greatly appreciated
Before submitting check if what you want to add to coraza list meets quality standards before sending pull request. Thanks!

Make sure that you've checked the boxes below before you submit PR:

[ ] My code includes positive and negative tests.
[ ] I have an appropriate description with correct grammar.
[ ] I have read Contribution guidelines, maintainers note and Quality standard.
[ ] My code is properly linted and passes pre-commit tests.

Thanks for your contribution :heart:

Codecov Report
Base: 73.13% // Head: 73.13% // No change to project coverage :thumbsup:

Coverage data is based on head (3877853) compared to base (008a3f3).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@           Coverage Diff           @@
##           v3/dev     #454   +/-   ##
=======================================
  Coverage   73.13%   73.13%
=======================================
  Files         143      143
  Lines        6592     6592
=======================================
  Hits         4821     4821
  Misses       1494     1494
  Partials      277      277

Flag
Coverage Δ

no-tinygo
73.18% <100.00%> (ø)

overall
73.13% <100.00%> (ø)

tinygo
72.06% <100.00%> (+0.03%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

internal/corazawaf/transaction.go
65.34% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.