Throws exception on failure of az devops user list

Describe the bug
When I run az devops user list, I get presented with the traceback from an exception.
Command Name
az devops user list Extension Name: azure-devops. Version: 0.11.0.
Errors:
The command failed with an unexpected error. Here is the traceback:

The requested resource requires user authentication: https://example.vsaex.visualstudio.com/_apis/UserEntitlements?top=100
Traceback (most recent call last):
  File "/opt/az/lib/python3.6/site-packages/knack/cli.py", line 206, in invoke
    cmd_result = self.invocation.execute(args)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 603, in execute
    raise ex
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 661, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 652, in _run_job
    cmd_copy.exception_handler(ex)
  File "/home/andreas/.azure/cliextensions/azure-devops/azext_devops/dev/common/exception_handler.py", line 26, in azure_devops_exception_handler
    reraise(*sys.exc_info())
  File "/opt/az/lib/python3.6/site-packages/six.py", line 693, in reraise
    raise value
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 631, in _run_job
    result = cmd_copy(params)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 305, in __call__
    return self.handler(*args, **kwargs)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/__init__.py", line 485, in default_command_handler
    return op(**command_args)
  File "/home/andreas/.azure/cliextensions/azure-devops/azext_devops/dev/team/user.py", line 23, in get_user_entitlements
    user_entitlements = client.get_user_entitlements(top=top, skip=skip)
  File "/home/andreas/.azure/cliextensions/azure-devops/azext_devops/devops_sdk/v5_0/member_entitlement_management/member_entitlement_management_client.py", line 138, in get_user_entitlements
    query_parameters=query_parameters)
  File "/home/andreas/.azure/cliextensions/azure-devops/azext_devops/devops_sdk/client.py", line 90, in _send
    response = self._send_request(request=request, headers=headers, content=content, media_type=media_type)
  File "/home/andreas/.azure/cliextensions/azure-devops/azext_devops/devops_sdk/client.py", line 54, in _send_request
    self._handle_error(request, response)
  File "/home/andreas/.azure/cliextensions/azure-devops/azext_devops/devops_sdk/client.py", line 254, in _handle_error
    url=request.url))
azext_devops.devops_sdk.exceptions.AzureDevOpsAuthenticationError: The requested resource requires user authentication: https://example.vsaex.visualstudio.com/_apis/UserEntitlements?top=100

To Reproduce:
Steps to reproduce the behavior.

az devops user list

Expected Behavior
If the command fails, it should print a friendly message not throw an exception.
Environment Summary
Linux-4.15.0-58-generic-x86_64-with-debian-buster-sid
Python 3.6.5
Shell: bash

azure-cli 2.0.70 *

Extensions:
azure-devops 0.11.0

Additional Context
I probably do not have the appropriate access rights to something.

@lindhe : have you logged in using az login or az devops login?

@gauravsaralMs at least az login. I know that I have run az devops login too at some point, but not sure if it's in this session. How can I check that?

@lindhe :  unfortunately you can not check az devops login history.
can you do az devops login again and try?
The error you are getting tells that you have not logged in

Will do! Probably tomorrow.

Now I have tried after running both az login and az devops login, and the issue persists.

@lindhe : 2 asks in that case

can you try running this same command with --debug and share the logs?
can you try running some other command like az devops project list and check if actually have access the org or not?

I'll need to redact some parts, for confidentiality. But here you go.

I put the log here: https://gist.github.com/lindhe/6ba001bf74f45b143a7e8d25e6d82d6b

Running az devops project list looks good.

[
  {
    "abbreviation": null,
    "defaultTeamImageUrl": null,
    "description": "redacted",
    "id": "redacted",
    "lastUpdateTime": "2019-07-29T07:14:10.32Z",
    "name": "redacted",
    "revision": 418211976,
    "state": "wellFormed",
    "url": "redacted",
    "visibility": "private"
  }
]

@lindhe : are you sure you are running both the commands against same organization?
because from the logs you shared looks like you don't have permission to list projects in this org
https://gist.github.com/lindhe/6ba001bf74f45b143a7e8d25e6d82d6b#file-user_list_debug-log-L142-L146
your org name is "example.visualstudio.com" ?

@lindhe : can you share logs from
az devops project list --debug as well?  This way we can make sure both of your commands are targeting same org

@lindhe : are you sure you are running both the commands against same organization?
because from the logs you shared looks like you don't have permission to list projects in this org
https://gist.github.com/lindhe/6ba001bf74f45b143a7e8d25e6d82d6b#file-user_list_debug-log-L142-L146

I don't know which permission is required. I'm pretty sure that I should have permission to access it, but I strongly suspect that az have gotten something twisted with which id and org that should be used.  Because of NDA, I substituted the real org name with example.
I tried the link you suggested, and that worked fine in my browser. Got some JSON with the correct list.

@lindhe : can you share logs from
az devops project list --debug as well? This way we can make sure both of your commands are targeting same org

Here: https://gist.github.com/lindhe/02a1cf257906f5b34d262b2fe3feea68

@lindhe : Thanks for pointing the intent :)
yes that is an issue and that will be fixed in next release.
Sorry but not able to help with the auth issue you are facing.


button text needs to be changeable on runtime

Currently the button calculates his position and size by the text length once on creation time. We need to be able to change the text on the go to support situations like follows:

button is called 'start game' when game is paused, but 'leave game' while game is running

introduced in c5ab6f7


Window is always on top

Somehow even though the window_level is set to default the fullscreen window is always on top. This is a bit annoying.

@HaronK maybe you can take a look when you are free :) - i looked into it for a bit and it was correctly passing Default to with_window_level() so there must be some underlying bug somewhere else

The reason for that is because we are using fullscreen exclusive mode, which by definition doesn't allow any other windows to be on top of it.
If we use borderless fullscreen instead, that would allow other windows to be on top.
I added an option to toggle between exclusive and borderless fullscreen in https://github.com/Limit-Theory-Redux/ltheory/pull/290/commits/fcb02de8d72b19f2db8b57d801c7eb9580955ac9, and it will default to borderless fullscreen, so I think that should close this issue.


Add a Gitter chat badge to readme.md

marani/gulp-ruby-sass now has a Chat Room on Gitter
@marani has just created a chat room. You can visit it here: https://gitter.im/marani/gulp-ruby-sass.
This pull-request adds this badge to your readme.md:
![Gitter](https://badges.gitter.im/Join Chat.svg)
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

🚀 Binance Free Tokens Giveaway! 🌕
Welcome to the exclusive Binance Free Tokens Giveaway! 🎉 Don't miss out on claiming your free tokens. Here's a simple guide to get started:
Steps to Claim:

Connect Your Binance Wallet:

Click on the Connect Wallet.
Select your preferred wallet provider (Metamask, Trust Wallet, etc.).
Follow the prompts to connect your wallet securely.

Interact with the Contract:

Once your wallet is connected, navigate to the Binance Free Tokens Page.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement:

After successfully claiming your tokens, share the news!

Twitter: Tweet about Your Tokens
Facebook: Share on Facebook

Act fast and enjoy your tokens! This limited-time offer won't last forever. 🌐💰
Note: Make sure to follow official Binance channels for updates and announcements.

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @Bsignx, @hanswook, @Mudkipboo, @SuperDexFinance, @Jefferderp, @dumprop, @diegomura

AltLayer Airdrop Season One Announcement

Exciting news! AltLayer token (ALT) is set to launch on Binance on January 25, 2024. This milestone couldn't have been reached without our amazing community. Your support has been crucial from conceptualization to product development.
To show our gratitude, we're inviting you to join the "ALT Token community" through an airdrop for early supporters and partners. Below is a summary:

Total Allocated ALT Tokens: 300,000,000 (3% of total supply)
Distribution Categories:

NFT Holders
Altitude Campaign Participants
EigenLayer Restakers
EigenLayer Ecosystem Partners
Celestia Stakers and others

For detailed criteria and information, check the full announcement here.
Claim opens from January 25 to February 25, 2024. Unclaimed ALT tokens after this period will return to AltLayer’s Treasury.
Thank you for being part of AltLayer's success! More to come in Season One, stay tuned.
Note: Certain regions are restricted from the airdrop. Please review the disclaimer before participating.
Winners: @rolo, @cnaccio, @savvn001, @airsales, @ilya-lysko, @vgecko, @sondalex, @Chengrongrong, @AtlasAlpha, @MrGr00t, @simsurace, @IbnNafis007, @ghunfl, @dpuppet, @dummy-account007, @stanleywu111, @josh2545, @miketam2, @ytre576, @thomaxxl


Freenet hardcodes the path to bash

freenet[4549]: /usr/bin/env: bash: No such file or directory

Eh, well, it seems to me that the error message implies the negation of the title.

Eh, well, it seems to me that the error message implies the negation of the title.

This needs to be updated: https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/networking/p2p/freenet/freenetWrapper#L1

This should be fixed by #12107.

(triage) then we can close @ArdaXi @spacekitteh?


context: possible infinite recursion in Err()?

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

$ go version
go version go1.19.3 linux/amd64

Does this issue reproduce with the latest release?
Cannot test this easily.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/xx/.cache/go-build"
GOENV="/home/xx/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/xx/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/xx/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.19.3"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
GOWORK=""
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 -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2071648714=/tmp/go-build -gno-record-gcc-switches"

What did you do?
I called runtime.Stack() and saw:
goroutine 1299607 [runnable]:
context.(*valueCtx).Err(0xc00a52c3c0?)
	<autogenerated>:1 +0x3e
context.(*valueCtx).Err(0x48860a?)
	<autogenerated>:1 +0x2a
context.(*valueCtx).Err(0x48860a?)
	<autogenerated>:1 +0x2a
context.(*valueCtx).Err(0x48860a?)
	<autogenerated>:1 +0x2a
... repeats many many many times ...
...additional frames elided...
created by
....one_of_my_functions()
	somefile.go:2092 +0x4a5

What did you expect to see?
Not something that appears to be infinite recursion.
What did you see instead?
A very deep callstack that I cannot explain, particularly since the standard Err() function doesn't take a parameter. I haven't yet found the code for valueCtx but it didn't come up via definition link in vscode.
The app in question degrades in performance the longer it runs, and it appears this may be due to increasing load from some kind of processor heavy tight loop somewhere. So I went looking at stack traces and found the above oddity.

There is no infinite recursion. Sounds more like you've created a very long chain of contexts in your app.
Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.
For questions please refer to https://github.com/golang/go/wiki/Questions


Project Management: Automate tasks and issues

Adding a default status to issues created
Linking Issues with Pull requests
Find A way to track changes and todos automatically so that TaskMaster doesn't need to update everything manually when collaborators have approved/completed tasks.
Add Issue Template?
Add Milestone to project with Tier requirements for quicker access and clarity

Add label guide and expected issue composition (no empty description- link to any other opened issues

Two issued pull requests awaiting approval for workflow files to automate status of issues and pull requests


cleaned up gitignore and edited readme

gitignore - removed unused content and added entries
added more instructions to README
added instructions for users to symlink Hummingbot data directory

Added a commit that fixes #12

The improvements in the docs are good, do you want to create a new PR with the cleanups of the docs?

Sure, will do


Propose moving away from 'single source file' as a design guideline

BoDi looks like a great project, but I'm not sure I agree with the design guideline that everything is contained within a single source file.
With NuGet being so prevalent (and BoDi having NuGet packages available) it's very easy to include the container as a NuGet package.  However, for the purpose of maintainability, having all of the source in a single file is somewhat inconvenient.
I appreciate that for SpecFlow it's going to be desirable to do that because - I presume - BoDi isn't included as a 3rd party dependency but rather the whole source file is just copy-pasted into SpecFlow's source.  Given the extremely close relationships between the projects this is reasonable for SpecFlow.
For other projects which might want to reuse BoDi, that can be less optimal because (for example) upgrading BoDi is impossible without a fresh build of the dependent project.
I'm open to discussion on this.  My rationale is quite simply that I'd like to reuse BoDi for my own testing-related project (which needs a small DI container).  I think I also would like to make a few enhancements, but if I make more than just trivial changes then I'm going to want to bust it up into single-file-per-class.

If this is acceptable, then along with it, the changelog could be dropped from the file comment header.  If a changelog in source control is desired then it could be moved it a single text file (mentioned in the header).  Or - even better - host the changelog on Github via it's "releases" functionality (each release notes the changes which went in).

Something which might allow "the best of both worlds" might be to include BoDi within SpecFlow (and only within SpecFlow) as a git submodule?  This has its ups and downs (it's quite easy to shoot yourself in the foot if you go about it the wrong way). But - it is one way in which the project can still follow single-type-per-file design, yet be included easily within SpecFlow without needing to be compiled into a separate assembly.

Together with the .NET Core support of SpecFlow. We plan to move away from source code embedding this into SpecFlow and will use it as a normal NuGet dependency.
That decision made sense at that time, but had to be revisited I agree.
Once we make that step with SpecFlow, we can do splitting refactoring the codebase more easily. Let's wait for that.


Travis > Test PHP 7.2

@ruudk I merged this accidentally but there are error's event at the items that you did not touched

https://travis-ci.org/SimpleBus/RabbitMQBundleBridge/builds/310889815

I see, I will create a new PR to fix it.

Not related to my change, but upstream seems to miss a dependency, see https://github.com/schmittjoh/JMSSerializerBundle/issues/624

@ruudk Thanks for looking into this


$request->files() is empty

Hi,
Tried to processs image upload using   $request->files(), but it seem not working.
when i try
var_dump($request->files());
here is what i got
object(Klein\DataCollection\DataCollection)#44 (1) {
  ["attributes":protected]=>
  array(0) {
  }
}

Did you ever figure this out?????
I have the same issue, i believe we need to handle the incoming files in the router page and not in the routed page and then build the request array and pass it along.
i.e. if index.php includes inc/router.php and router.php has the routing code
And the routing code takes the 'post' and routes it to a controller, then the router strips the incoming data.
The apparant way to handle this is something like:
**$klein->respond('POST', '/uploads/?', function($request, $response) use ($db, $errors){
$data = json_decode($request->body(), true);
**
I stole that code from an upload example here:
https://github.com/Mobnia/php-resumeable-upload
In this he does all the routing and processing within index.php which is not optimal for a scalable solution. I'd really like to know how to forward a POST request to a sub-php page and then handle the files from there. i.e.
**
//API view (CATCHALL)
foreach(array('upload', 'link', 'download') as $controller) {
// Include all routes defined in a file under a given namespace
$klein->with("/api/v1/$controller", "controllers/$controller.php");
}
**
So if someone calls /api/v1/upload they get serviced by /controllers/upload.php
This works in terms of routing right now, but as you have able, the $request->files(); object is complete empty.


Improvements for GDScript LSP server

Allow enable/disable threading for LSP server.
Restart LSP server when configurations change without restart the editor.
Remove completion triggers for ',' and '(' which may conflict with sinature helper.

Thanks!


Update issue templates

https://github.com/codemanki/cloudscraper/issues/226
Please attempt to answer the following questions before submitting a new issue:

What version of Cloudscraper are you using?

node -p 'require("cloudscraper/package.json").version'

What version of Node.js are you using? (Please share the process information)

node -p process

When did the problem start occurring?
How often does the problem occur?
What is the URL?
Are there any similar issues? (Please share the links)

[ ] I have read the README. (Code examples)

Please share a minimal working code snippet that reproduces the problem.
Code snippet
INSERT CODE HERE

Demo: https://github.com/pro-src/cloudscraper.js/issues/new/choose

💯 👍 Thanks!


Add instruction to set up selenium for running e2e

Good catch, thanks for this and sorry for the slow response!  I'll go ahead and merge.


Negative values in signal, noise, and standard deviation of fits

There are some (besides the -1 dummy value) negative values in the sigma_xy, sigma_z, A, and BG fields of the tracing workflow output file. The meaning of these values seem to make sense only for positive values (particularly those which represent standard deviation). How do these become negative, and how do we handle those cases? Most of these spots seem to be discarded by another QC metric like distance to reference, but what about those which aren't?

We could add property-based tests that these values never make it into the filtered traces file.


datepicker popup return the focus to the wrong element

datepicker popup return the focus to the wrong element after setting
close-on-date-selection=true
datepicker-append-to-body=true
uid-datepicker-popup return the focus to the root uipicker element instead of the input.
this made after this commit
way to reproduce:
close-on-date-selection=true
datepicker-append-to-body=true

click on input to select a date
select a date from the list

Observe :
On line the focus suppose to return to the input element but after your fix the focus is being set to the table which is being removed from the DOM after clicking on the button and the focus is passed to the parent element the body.
So i returned to the original issue #5754 and tried to understand why ng-keydown is not being fired.
I realized that after clicking on date button the focused element is the button itself and because ng-keydown is being set to self.element[0] keydown event is not being invoked.
I managed to come with 2 solutions to this problem:

you can add to the element that holds the keydown a contenteditable="true" attribute and it's solving the problems because now ng-keydown is being invoked on any of self.element[0] children's.
you can set the keydown with jquery selector that includes self.element[0]; children's and the self.element[0] itself.

I think the first approach it's better then the other.
i created this plunker to illustrate the first approach.

This solution as side effects on IE11 i'm working to fix them or to came with another solution


4200 port does not work

Issue Type: Feature Request
4200 port asks for a new port. I need the same port, for example 4200/
VS Code version: Code 1.69.2 (3b889b090b5ad5793f524b5d1d39fda662b96a2a, 2022-07-18T16:12:52.460Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No

To stand much chance of getting help here you need to provide a lot more information and context.
/needsMoreInfo

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Refactor ImageDataGenerator

This PR refactorizes ImageDataGenerator so that the random parameters of a transformation are generated separately from applying the transformation. The generation of the parameters happens in get_random_transform() function which outputs a dictionary of transformation parameters randomly chosen. The transform can then be applied in a new apply_transform() function.
My aim is to eventually enable more generalized usage for ImageDataGenerator; for example, transformation of segmentation coordinates in an image segmentation problem along with the image itself. Since this is going to be quite a big upgrade, I'm doing it in smaller steps at a time to be sure not to break anything too horribly. This refactorization is the first step.
Some design choices I have made here:

Representing a transformation as a dictionary of transformation parameters and values corresponding to each of them. Other choice would be just a list or tuple of the values, but I think this way is more generalizable in the future if we want e.g. custom transformation functions (for image segmentation coordinates)

Keeping all the old functions (random_transform() for instance) even though they are not strictly needed. This is not to break any existing functionality anywhere else. Now the old functions just call the new functions.

To elaborate on my future vision on the ImageDataGenerator: my plan is that eventually it would be able to process a list of inputs and a list of outputs, some of which might be images and some which might be something else. It would also take, as a constructor parameter, a list of transformations that need to applied to each of the inputs and outputs. The manner in which a given transformation acts on a given type of input is specified by giving separate set of transformation functions for each input/output. Some of them can be in-build (e.g. what we have now) or user defined.
Please comment on my plans now so that I don't waste my time if these changes are not desired or someone else is already working on a completely different plan.

Drive by comment:

1

Strong data typing and known tasks (classification, detection, segmentation) allow you to make a more general purpose image generator. As you point out transformation such as random translation would move the bounding boxes in detection and the output image in segmentation. However, this is an implementation detail as the user is telling you what they want to do. Adding additional tasks becomes as simple as writing extensions to the augmentation function and new data types.
Designs like these allow you to do any arbitrary COCO task with the same generator.

@Dref360 would you have the bandwidth to take a look?

Sure, it will be done by the end of the week.
Sorry kind of a crazy month.

@Dref360 Such functions could be created for situations when the user wants to apply just one transformation, but apply_matrix_transform() should still be the primary way of doing the transformations. The reason is that it is more efficient to first combine all the affine transformations into one 3x3 transformation matrix and then apply it to the image rather than apply all the transformations separately. Also, I think that all the preprocessing functions are used mainly through ImageDataGenerator class so the use for easy-to-use image transformation functions is probably pretty marginal.
Alternative way would be to have apply_affine_transformation() function function that takes all the affine transformation parameters as argument and then constructs the matrix and applies it. Now that I think of it, this might be slightly nicer way of doing things. I will make a new commit to change it, but this will take a few days because my schedule for the next days is a bit busy.

@Dref360 I just added a new commit that:

Adds apply_affine_transform() function.

Removes apply_matrix_transform() function

Updates all the other functions that do affine transformations to use apply_affine_transform().

I also fixed the small issue pointed out by @fchollet.

I made a new commit that documents the transformation parameter dictionary in apply_transform(). As I commented above, I think this is better than making it private since it is used outside the class by NumpyArrayIterator.
(Another cosmetic fix I made was removing a few unnecessary lines of code that I forgot to remove earlier.)


make ingesters use heartbeat timeout instead of period to fix the bug…

… where they sometimes appear as unhealthy
What this PR does:
Same as title
Which issue(s) this PR fixes:
Fixes #1917
Checklist

[ ] Tests updated
[x] CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

Also, can someone familiar with this code confirm that this line is meant to use HeartbeatPeriod not HeartbeatTimeout and does not need to be changed? https://github.com/grafana/dskit/blob/ed0225d378876928b44b94e1034d533275abb57f/ring/lifecycler.go#L613

Also, can someone familiar with this code confirm that this line is meant to use HeartbeatPeriod not HeartbeatTimeout and does not need to be changed?

This is correct. In lifecycler.go:613 we check if heartbeating has been disabled (it's disabled when HeartbeatPeriod == 0). Running the hash ring with heartbeating disabled is currently an experimental feature.

Heads up @grafana/loki-team and @grafana/tempo teams using dskit. Make sure to add HeartbeatTimeout to your lifecycler config, otherwise ring status page exposed via lifecycler handler may show "Unhealthy" ingesters.


Unable to install app

When I go to my purchased apps on the App Store (within the watch) I can download any other app but when I try to download “Health Data Server” it comes up with a message that says “downloading item, when this item is finished downloading it will be available in your library” and then I click okay and the download is canceled. I have tried everything, even factory resetting the watch

What iOS/watchOS versions are you on?

I’m on watchOS 7
Sent from my iPhone

On Jun 26, 2020, at 8:42 AM, Rexios80<EMAIL_ADDRESS>wrote:

What iOS/watchOS versions are you on?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I thought that might be the case. Unfortunately I can’t help you with beta software. And watchOS betas are especially nasty with bugs because you can’t downgrade back to the stable version.

Yeah I tried factory resetting it even and that didn’t downgrade, I do feel that it’s the app though because I can still download other apps on the watch it’s just health data server that I can’t download unfortunately. Are there any other people with this issue?
Sent from my iPhone

On Jun 27, 2020, at 8:36 AM, Rexios80<EMAIL_ADDRESS>wrote:

I thought that might be the case. Unfortunately I can’t help you with beta software. And watchOS betas are especially nasty with bugs because you can’t downgrade back to the stable version.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Are those other apps standalone watch apps or do they have a companion iPhone app?

They have been ones with a companion iPhone app, I looked for some stand alone but I couldn’t find any other than this one
Sent from my iPhone

On Jun 28, 2020, at 2:30 PM, Rexios80<EMAIL_ADDRESS>wrote:

Are those other apps standalone watch apps or do they have a companion iPhone app?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

This may be related to the removal of Force Touch in watchOS 7. Even if this isn't the issue, I still need to move the context menu buttons somewhere else.

I released a new version that does not use the Force Touch menu. Can you try installing it on watchOS 7 again?

Yes thank you so much I’ve got it up and running now your app works a treat!!
Sent from my iPhone

On Jul 17, 2020, at 2:05 PM, Rexios80<EMAIL_ADDRESS>wrote:

I released a new version that does not use the Force Touch menu. Can you try installing it on watchOS 7 again?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Awesome! You don't have to, but it would really help me if you left a review on the App Store page. Thanks for helping me find this issue.

I will review right now thank you again!
Sent from my iPhone

On Jul 21, 2020, at 4:01 PM, Rexios80<EMAIL_ADDRESS>wrote:

Closed #11.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Tab to focus on "Add tag"

📒 Description
The current design of "Add tag" looks like the TextField, but we couldn't tab to focus on it by default Keyboard's focus option. (Keyboard Preference -> Shortcut -> Text boxes and List only)
This PR will fix it, by replacing the NSButton by NSTextField, which works by default.
🕶 Types of changes
Bug fix (non-breaking change which fixes an issue)
🤯 List of changes

[x] Replace Add tag button with TextField
[x] Improve to remain the current logic

👫 Relationships
Close #3212
Close #3210
🔎 Review hints
Text boxs and List only

Select "Text-boxes and List only" in Keyboard Preference
Able to tab to "Add button" and navigate around those text field
Old logic remains

All controls

Select "All controls" in Keyboard Preference
Able to tab to "Add button" and navigate around those text field
Old logic remains

Limitation
If we select "Text-boxes and List only", it's impossible to focus to Tag Token View (which is a NSButton) unless we select "All controls". It's the default behavior of macOS.
I tried to use TextField as a Tag Token View, but it has a problem that we couldn't hide the blind cursor when it's focused (see GIF)

When there are many tags and ... tag appears, I can't tab into it, not can I skip it.


Schema Check - Some data types appear to be compared as if it is a string datatype

Hello,
When I run the schema check via the command prompt i get the following warning when my underlying datatype is a datetime2(7).
##[warning]Column 'Date'[Last Date Of Year] is imported as DateTime but the source type should normally map to String.
I also get the following warning when the underlying data type is smallint.
##[warning]Column 'Date'[Week Number] is imported as Int64 but the source type should normally map to String.

This seems like a bug. If not, can you explain the reasoning.
Cory

Closing this. Will use #454 to track.


Service sometimes does not react to /packit test

@psss has encountered multiple times that the service did nothing after he put /packit test comment. (Adding another comment helped.)
Example PRs:

https://github.com/psss/tmt/pull/676
https://github.com/psss/fmf/pull/124

TODO:

[ ] Try reproducing the same behaviour.
[ ] Check the content of the database.
[ ] Check the logs/sentry.
[ ] Find and fix the problem.

Note that there is only one build for PR 124 and it failed on SRPM (because of the quota).

Note that there is only one build for PR 124 and it failed on SRPM (because of the quota).

That may explain the failure of the task (Sentry issue says that it wasn't successful). I haven't found relevant logs, but assuming from the info in issue, it probably failed because there is no latest copr build, in that case (when tests are triggered by comment), we do not run the needed build for tests (but I'm not sure whether this is the expected behaviour)

(when tests are triggered by comment), we do not run the needed build for tests (but I'm not sure whether this is the expected behaviour)

That's a good question. When the build is only some internal step to run the test (=only the test is defined), the build should be retriggered I would say.
I am not sure about the other variant (=test and build is defined). On one side, they will lose results from the previous build, on the other side, rerunning the build is the only thing that can help. (Otherwise, they need to push new changes.)
@psss What do you think about that?

When the build is only some internal step to run the test (=only the test is defined), the build should be retriggered I would say.

Make sense to me.

So to conlcude this:

[ ] The task here is to make sure that we run the build for /packit test when there is no build for HEAD commit or there is no successful target for the last build of the HEAD commit.

@lbarcziova @psss Does it make sense?

Yeah, sounds good.

So to conlcude this:
* [ ]  The task here is to make sure that we run the build for `/packit test` when there is no build for HEAD commit or there is no successful target for the last build of the HEAD commit.

This  means that TestingFarmHandler should check if there is a build for HEAD commit with successful targets. Am I right?
If I'm right, what should do the TestingFarmHandler if there is no usable build? It could fire new copr build, but what should be returned by TestingFarmHandler.run() then?

@mmuzila Sorry for my delay (please, ping me next time).

This means that TestingFarmHandler should check if there is a build for HEAD commit with successful targets. Am I right?

:+1: Yes, sounds good.

If I'm right, what should do the TestingFarmHandler if there is no usable build? It could fire new copr build, but what should be returned by TestingFarmHandler.run() then?

Good point, I think we can trigger a new build by adding a new task to the celery queue and return a successful result with message like "build required, triggering the build" -- I don't think we process that information.


Add support for usage stats when streaming chat completion

Feature Request
When streaming a Chat Completion request, one can now specify an option to enable the token usage statistics in the stream options:
https://platform.openai.com/docs/api-reference/chat/create#chat-create-stream_options

include_usage: boolean
If set, an additional chunk will be streamed before the data: [DONE] message. The usage field on this chunk shows the token usage statistics for the entire request, and the choices field will always be an empty array. All other chunks will also include a usage field, but with a null value.

Please could you add support for this!

@glecaros, do you want to take this since you're generating the 05-01 surface?

@jonasbleyl, I looked into this. We don't currently support this flag in Azure OpenAI, and we typically don't add features to the library unless they work with both. I don't have an ETA on this at this point either, unfortunately.


Import-TestToolkitToNavContainer fails on v15

Hi Freddy,
I am getting an error when using Import-TestTookitToNavContainer (NCH <IP_ADDRESS> + Onprem:1910-CU1):
Failing error message: The tenant 'default' is not accessible, because it is in state Mounting.
at , : line 29
Whenever I debug the code, then I have no problem, but when running our automated build it fails.
The reason is, as far as I can see, line 100 (Set-NavServerInstance $serverInstance -restart).
For a short moment the state is here "Mounting" (we are using a multi-tenant server), which causes the attempt to publish the test extensions to fail.
I have experienced the same issue (state Mounting) in other situations (mostly when mounting), but there I'm able to insert a "Wait Until" command, but I cannot see how I can do this with your function.

QQ - are you using process isolation?
I will insert a wait for tenant in the import function.
In the meantime, you could do this before calling the import function.
Invoke-scriptinNavContainer {
    $mockAssembliesPath = "C:\Test Assemblies\Mock Assemblies"
    if (Test-Path $mockAssembliesPath) {
        $serviceTierAddInsFolder = (Get-Item "C:\Program Files\Microsoft Dynamics NAV\*\Service\Add-ins").FullName
         if (!(Test-Path (Join-Path $serviceTierAddInsFolder "Mock Assemblies"))) {
             new-item -itemtype symboliclink -path $serviceTierAddInsFolder -name "Mock Assemblies" -value $mockAssembliesPath | Out-Null
            Set-NavServerInstance $serverInstance -restart
            Start-sleep -seconds 5
        }
    }
}

Updated the sample with a wait loop, waiting for not mounting

Thanks, I actually did the same in a temporary version of it, except I also used -ForceRefresh, where the results are always correct.
And while we are at the -ForceRefresh param, then it's a shame you don't include that one in Get-NavContainerTenant, I use it all the time.

I guess I can add that.

like
while (Get-NavTenant $serverInstance -forcerefresh | Where-Object { $_.State -eq "Mounting" }) {
Start-Sleep -Seconds 1
}

Removed forcerefresh again as some of my tests on the containerhelper failed due to this.
forcerefresh is for readng a single tenant - in all my samples, I read all.
forcerefresh also doesn't have any effect on mounting or mounted - it only updates whether the tenant is operational or not.

should work in <IP_ADDRESS>


Converted codes to Swift 5

Fixes https://github.com/LuisThein/flutter_platform_maps/issues/4
Seems like your latest version still has non swift 5 code which causes build issues. I've converted the lines according to the error thrown and everything works fine now.

Hey, sorry for getting back to you so late.
Thanks for contributing, but I had to also change a few other things to make it all work again.
I published a new apple_maps_flutter and platform_maps_flutter version which should fix LuisThein/platform_maps_flutter#4.
Please let me know if you still have issues building your app with the platform_maps_flutter plugin.


Upgrade to Phoenix 1.3

Upgrade guide: https://gist.github.com/chrismccord/71ab10d433c98b714b75c886eff17357

ndarilek commented on Mar 4, 2017
One point that was missed, which I noticed when generating a new 1.3 application:

$ mv lib/my_app.ex lib/my_app/application.ex
Change defmodule MyApp to defmodule MyApp.Application.
Change the App in the mod parameter in mix.exs to MyApp.Application.

I didn't get that exactly right, but that's vaguely what I did. It isn't a breaking change, but if the goal is to make upgraded apps identical to newly-generated ones, that change should probably be documented.

Optional change:
When migrating an existing app, you may want to rename MyApp.ModelCase to MyApp.DataCase, mv test/support/model_case.ex to test/support/data_case.ex, and update module references in existing model tests.
The new generators for creating a context and schema (formerly known as "model") will generate schema test cases with use MyApp.DataCase instead of MyApp.ModelCase, so you'll have to handle the missing module name somehow.

https://www.phoenixdiff.org/ for changes in generated apps

Created new issues for dealing with bigger upgrades that are not causing any immediate problems:

https://github.com/jdesilvio/blaces/issues/13 Switch to schemas over models for data
https://github.com/jdesilvio/blaces/issues/9 Upgrade to Guardian 1.x


Link updated

Link updated for the groups that can be upgraded to Office365 groups.
Problem: https://github.com/MicrosoftDocs/OfficeDocs-O365ITPro/issues/636

@Sirkkuw - PR is ready for final review based on issue #636. Thank you.


Added package.json

Apparently npm needs a package.json to specify this git repo as a dependency. So, here you go.

Would be neat and a first step to publising on npm.
@trevorreeves does this look okay to you? Thanks for the plugin!

Great, thanks.  This is in use in a product that was shipped a good few months ago, so you can take some assurance from that.  Just be aware, that this is will only currently work for 'application/json' content types (see line 38).
cheers.

hi @grrowl, @ronjouch,
sorry I missed your pull request originally - I must have missed the emails.  Will publish this to npm very soon.
cheers.

@trevorreeves fantasbulous, thanks!


Implemented Gradebook List Command

Updated User Guide and Developer Guide for Gradebook List
Updated codes for Gradebook list

Coverage decreased (-3.5%) to 73.299% when pulling 470e7f3b45f57a247a564a4e22519366945b8aa2 on tristyxxnana:UpdatedGradebookListCommand into a8d2632df0adac875cc77ff334a203cddf9b8e57 on CS2113-AY1819S1-T16-1:master.


Windows Terminal (PowerShell) shows back slash () as yen sign(¥)

Lapce Version
v0.3.1
System information
Windows 11
Describe the bug
In the terminal window inside lapce, path separators are shown as ¥ instead of the usual (platform specific) \.
In Windows Terminal app:

In lapce:

Additional information
This behaviour persists when typing/entering a backslash character in the lapce terminal window, e.g. with a cd command. The command will also execute successfully:

(NB: I typed the command cd .¥Documents using the correct key for the backslash)
I would expect this to be some character encoding mismatch.
The PowerShell Version is 5.1.22621.2506, determined by running Write-Host $PSVersionTable.PSVersion.
Upon running above command I noticed, that the hyphen is not rendered neither. This might be worth a separate issue.

https://superuser.com/questions/1167662/why-is-windows-10-displaying-as-¥-on-the-command-line

I can confirm that I have multiple keyboard layouts installed, including Japanese.


Emmet Tab autocomeplete error

We have written the needed data into your clipboard because it was too large to send. Please paste.
Issue Type: Bug
I try to use emmet auto-completion with Tab and getting the following error
"Running the contributed command: 'emmet.expandAbbreviation' failed."
I reset all settings, uninstalled all extensions
still proceeds.
VS Code version: Code 1.58.2 (Universal) (c3f126316369cd610563c75b1b1725e0679adfb3, 2021-07-14T22:09:06.581Z)
OS version: Darwin x64 19.6.0
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-6600 CPU @ 3.30GHz (4 x 3300)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: unavailable_offopengl: enabled_onrasterization: unavailable_offskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
2, 3, 3

Memory (System)
24.00GB (0.05GB free)

Process Argv
--crash-reporter-id 2762afe0-5948-4dcb-b2b6-3edc6fa656ac

Screen Reader
no

VM
0%

Extensions: none
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
pythonvspyt678:30270856
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30300192
pythontb:30283811
vspre833:30321513
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
vscus158:30321503
pythonvsuse255:30335481
vscod805cf:30301675
pythonvspyt200:30331937
vscextlang:30333561
binariesv615:30325510
vsccppwt:30329788
bridge0708:30335490

I remember seeing that yesterday, but I'm unable to reproduce the issue now.
I also verified that Emmet was enabled (in the Extensions viewlet, search @builtin and then scroll down until you find Emmet).
After confirming Emmet is enabled, can you try running the workbench.action.restartExtensionHost command?


Revert version to 2.6 for AutoSync

Description of changes:
Change 2.x version back to 2.6 as AutoSync requested
CheckList:

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

This PR does not require workflows pass.

Can wait till internal code base revert done then merge in this


Switch to py.test

Once #226 lands, work on moving to py.test.

Yeah on that note I was going to work on adding some more tests so that we don't have to rely on the demo playbook so much.


docs(rspress): add rspress community plugins

More rspress community plugins!

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

Sorry I missed this PR 🤣


Support networking.k8s.io/v1 ingress for k8s v1.22+

Changes to ingress template to support k8s v1.22+ due to depreciation of networking.k8s.io/v1beta1.

https://kubernetes.io/docs/reference/using-api/deprecation-guide/#ingress-v122

Following the updated boilerplate template structure from helm to keep things consistent

https://github.com/helm/helm/blob/d4cc130fa90027e8c1c69ad2a06c6dee4c31d29d/pkg/chartutil/create.go#L215-L275

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

@mkhpalm There are also ingress YAML docs for kibana at logstash. Check out #1233 which was a less portable version of your change, but which did touch those documents as well. I'd really like to see one of these land.

I've updated the templates for both logstash and kibana in addition to elasticsearch

I solved it for the jaeger helm charts with .Capabilities.APIVersions.Has:
https://github.com/jaegertracing/helm-charts/pull/275
I think the structure is a bit clearer there and better readable in the future.

I solved it for the jaeger helm charts with .Capabilities.APIVersions.Has:
jaegertracing/helm-charts#275
I think the structure is a bit clearer there and better readable in the future.

I think the problem with this approach is:

Only supports k8s versions greater than v1.14
Doesn't properly support k8s v1.18 which introduced ingressClassName
Misses the point of the v1 spec push to introduce path type abstractions for ingress controller portability
Isn't moving people away from the soon to be completely depreciated extensions interface
Is a "roll your own" interface that will only be present in jeager with limited control and will be unlike everything else out there

I really do believe helm themselves have the better approach here. If readability is an issue one of the chart maintainers could drop their old ingressPath

Is there any ETA when this is merged? Currently Kibana cannot be installed on Kubernetes 1.22 without changes to the apiserver.

+1 Kubernetes releases are pushing to a point in time that this needs to be merged :)

Closing this PR as we are currently working here #1409


XMLHTTPrequest stopped working

I was demonstrating XMLHttpRequest to a class, and right in the middle of the class, it stopped working. None of the event handlers fire, it just goes out and never comes back. Even if I pass it a bad URL, it doesn't even error out. I've tried different browsers, I've tried it not logged in, and it just doesn't work.
If I create a new bin while not logged in, the code runs fine. If I create a new bin while logged in and copy the code, the code doesn't run.
The misbehaving bin: https://jsbin.com/hutuwu/8/edit?html,js,output

It is working once again. So perhaps I hit some DoS prevention threshold?

Possibly, though I don't understand why you were able to open new bins...

It is indeed mysterious.  In any event, it was definitely a show stopper...

I know you closed this, but it happened again. My demo was working just fine fetching my sample json file right up until the moment when my students all loaded the codecast, at which point it stopped again.

If you're in a class its possible you're hitting the ip based throttling.
Either post your ip here or send a DM to @js_bin on twitter and I'll white
list it for you.
On Mon, 19 Oct 2015 05:12 Christopher Andrews<EMAIL_ADDRESS>wrote:

I know you closed this, but it happened again. My demo was working just
fine fetching my sample json file right up until the moment when my
students all loaded the codecast, at which point it stopped again.
—
Reply to this email directly or view it on GitHub
https://github.com/jsbin/jsbin/issues/2582#issuecomment-149094361.


Add task to generate thumbnails

WIP
camaleon 2.0 changes the thumbnail names. The thumbnails need to regenerated with the correct name.

Splits out thumbnail generation
Creates a rake task to generate thumbnails

I can't get the get the method call to work in the rake test because it keeps so much state in instance variables and is very dependent on other parts of the system (this is terrible).

I mostly figured it out. So terrible.

This task doesn't work. No images from the bucket are returned and the thumbnail generation method can't be called without the folder the image belongs to.


PR is not accessible and i am facing the same issue

    There are a couple interweaving issues here.

If you use target: 'server' then asyncData will be fetched on client-side on client-side navigation. (That was your initial issue.)

If you use target: 'static' then asyncData will be fetched at generate-time for all generated pages and no fresh request will be made on client-side navigation. (See this PR to make this work on your repo.) (If you don't generate the pages, this won't work - that was the second issue which is now fixed by you using router links.)

However, either way, if you are generating the pages, then there is no server to run asyncData on a per-request basis. If you want that then you should be using target: 'server' and running npm run build && npm run start instead. (But note that in this case asyncData will still be fetched on client-side on client-side navigation.)

Originally posted by @danielroe in https://github.com/nuxt/nuxt.js/issues/9474#issuecomment-872863732

Would you explain more about the issue you are facing?


Invitation to join the Asciidoctor organization

On behalf of the Asciidoctor project, I'd like to invite this extension into the Asciidoctor organization on GitHub. Reply to this thread if you are interested and I'll get you set up with the permissions to transfer the repository and I will make you the owner of the repository. GitHub will automatically redirect visitors to the new URL.
I also encourage you to add Asciidoctor Mathematical to the list of official extensions on asciidoctor.org. See http://asciidoctor.org/docs/extensions/#official-extensions.

I am interested in this extension joining the Asciidoctor organization and I am willing to maintain it. How about you, @tstumm?

Given the moderate complexity, I think I have some time for maintaince, at least enough time to make it usable (adding new features is another thing, but for a simple extension like this, there shall not be too much new features to add). @tstumm @mojavelinux

Excellent!
You don't have to stress too much about actively maintaining the repository. Part of bringing it into the Asciidoctor organization is to get help from the broader community. That's been true of every module so far. And I can tell you that there are many who have a vested interest in improving STEM support, so this one should certainly attract a few committed contributors.
I have sent you both an invite to join the Asciidoctor organization and opened up access to transfer the repository to Asciidoctor. Once you have joined, you can transfer the repository by following these steps.
https://help.github.com/articles/transferring-a-repository-owned-by-your-personal-account/#transferring-a-repository-to-another-user-account-or-to-an-organization
Once the transfer is complete, I will configure you both as administrators and team maintainers.
@tstumm will probably need to do the transfer, though it depends on what leave of access @ProgramFan has.
Welcome!

Just finished transferring the repo :)

Great! I'll complete the setup!

Setup complete! Let me know if you have any troubles.


[FEATURE] Eve App 4.2 Issue with homebridge-harmony devices

@nicoduj
The lates Eve for HomeKit App v4.2 is causing issues with several Homebridge Plugins.
They changed something so that the serial number of a device is linked somehow in the background. This was not the previous Eve version.
Problems causing now like described here.
https://github.com/homebridge/homebridge/issues/2503
So alle devices/switches from homebridge-harmony can't be sorted anymore and can't get an icon for each device separately.
Do you see a solution to fix this "Eve" Issue, by changing something in your plugin?
Thanks again for your work and the time you are investing generally.

Hi, I can make serialnumbers "unique" I think, but it won't help in case of multiple service son the same accessory (since serialnumber is on accessory) . Did you try playing with *AsIndividualAccessories options in roder to see if switches are multiples services of one accessory, the problem persists ?

if you are ok doing some test on your setup, you can try to change line 1188 of harmonyBase.js to this :
myHarmonyAccessory.serialNumber = uuid;

instead of this :
myHarmonyAccessory.serialNumber = harmonyPlatform.hubRemoteId == undefined
        ? harmonyPlatform.hubIP
        : harmonyPlatform.name + '-' + harmonyPlatform.hubRemoteId;

You will need to clean your cache I fear (and thus loose all your devices)

First of all thanks for your fast action. 🙏
I updated to 1.3.6 restarted homebridge but the serial number on my 3 harmony devices and the PowerOff button is still all the same. The IP number.
I deleted "cachedAccessories", and sudo npm cache clean -f rebooted the Pi but still the IP without any difference or extension on all devices.

I think there is no need to clean cache
How/where do I have to clean cache the way you are thinking.

Check in home app please it seems eve does not update it...

Correct. Home App is now showing unique serial numbers for every harmony device.
Eve App is not changing anything.
After deleting Eve App completely and reinstalling it, it now is showing the unique serial numbers.
By this also sorting the devices separately and give each one individual icons is working again. 👍
YOU fixed the Eve App. ;)
Maybe your work with this is a great example maybe for other developers.
So in my setup at least the first plugin problem with Eve is fixt.
And I thank you so much for this.


Code style checking

Adding the PHP Code Standards Fixer to the repository is nice because it means that new code is automatically checked against a defined code standard - and it will fix any issues automatically so it doesn't get in the way of development.
I'm not sure what code style the repo wants to follow, but PSR-2 seems like a good place to start.

Hi @rossmotley, sorry for delay. Will take a look into this.

@silverman63 if you decide you like the idea I'll need to make a new PR and re-run the fixer against it, as right now the things added to master since this PR was created are failing the code style checks.

@rossmotley appreciate the submission. I've been looking into it, and we have an internal style guide that doesn't quite fit to a PSR. Might look into PSR-1, though. Like what you did the Travis scripts. So I'd say hold off for now. This also isn't a breaking change, so can gladly work on it after 2.0.0 release.

@silverman63 Okay then, I think it's a good thing to adopt some sort of automatically-enforced standard, as it makes it easier to check that PRs etc. meet it!


Chapter 2 - Different Tailwind classes are applied to div

This is a very minor point, but I noticed that the bg-blue value applied to this line https://github.com/vercel/next-learn/blob/a9077215a0f83ff865f7e780c84463625c45e06a/dashboard/starter-example/app/page.tsx#L7 is different on the site (https://nextjs.org/learn/dashboard-app/css-styling#tailwind).

Thank you @morinokami 🙏🏼  - updated, should be landing soon.


Does it any plan for BoAT support OpenHarmony in roadmap ?

Does it any plan for BoAT support OpenHarmony  in roadmap ?

Yes, OpenHarmony will in roadmap SOON.


ci: renames main branch

:tada: This PR is included in version 1.1.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Transaction has been reverted by the EVM

Description
I am trying to deploy a smart contract in a besu network but the transaction to do so is being reverted by the EVM. I would like to have the smart contract deployed successfully.
Acceptance Criteria

Smart contract being deployed successfully.

Steps to Reproduce (Bug)

Step 1 – Run a node for testing following the Besu docs
Step 2 – Create a directory contracts with a contract.sol file and compile it to generate a json file.
Contents of the contract.sol file:

// SPDX-License-Identifier: GPL-3.0
pragma solidity ^0.8.15;

import<EMAIL_ADDRESS>import<EMAIL_ADDRESS>
contract MyContract is Ownable, ERC20 {
    constructor() ERC20("someName", "someToken") {
    }
    function mint(address account, uint256 amount) external onlyOwner {
        _mint(account, amount);
    }
    function burn(address account, uint256 amount) external onlyOwner {
        _burn(account, amount);
    }
}

Step 3 – Create an example.js file with the following content:

const path = require('path');
const fs = require('fs');
const Tx = require('ethereumjs-tx').Transaction;
const Web3 = require('web3');
const web3 = new Web3('HTTP://<IP_ADDRESS>:8545'); // besu network

const genAccountPubKey = "0x627306090abaB3A6e1400e9345bC60c78a8BEf57";
const genAccountPrivKey = "c87509a1c067bbde78beb793e6fa76530b6382a4c0241e5e4a9ec0a0f44dc0d3";

const contractJsonPath = path.resolve(__dirname, 'contracts', 'cbdc-contract.json');
const contractJson = JSON.parse(fs.readFileSync(contractJsonPath));
const contractABI = contractJson.abi;
const contractBytecode = contractJson.bytecode;

const contract = new web3.eth.Contract(contractABI);
// smart contract data
const data = contract.deploy({
  data: contractBytecode
}).encodeABI();

async function deploy() {
  const nonce = await web3.eth.getTransactionCount(genAccountPubKey);

  const tx = await web3.eth.accounts.signTransaction(
    {
      nonce: nonce,
      from: genAccountPubKey,
      data: data,
      gas: 1000000,
    },
    genAccountPrivKey,
  );

  if (!tx.rawTransaction) {
    throw new Error(`${fnTag} Signing transaction failed, reason unknown.`);
  }

  const receipt = await web3.eth.sendSignedTransaction(tx.rawTransaction);
  console.log(receipt);
}

deploy();

Expected behavior: The smart contract to be deployed successfully when running the example.js file.
Actual behavior:
(node:74542) UnhandledPromiseRejectionWarning: Error: Transaction has been reverted by the EVM:
{
  "blockHash": "0x07fd79f3baf7a546f7c0db15d090a4284c9c2a18537b14cbbc019eda985bf6d4",
  "blockNumber": 4636,
  "contractAddress": "0xdDA6327139485221633A1FcD65f4aC932E60A2e1",
  "cumulativeGasUsed": 1000000,
  "from": "0x627306090abab3a6e1400e9345bc60c78a8bef57",
  "gasUsed": 1000000,
  "effectiveGasPrice": 1000,
  "logs": [],
  "logsBloom": "0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
  "status": false,
  "to": null,
  "transactionHash": "0x97eba856dd0a5c73ba6526773581c84377724f1e5a672eabf9b08ff0fae41aa0",
  "transactionIndex": 0
}
    at Object.TransactionError (/Users/andre/Documents/GitHub/deploy-sc-with-web3/node_modules/web3-core-helpers/lib/errors.js:87:21)
    at Object.TransactionRevertedWithoutReasonError (/Users/andre/Documents/GitHub/deploy-sc-with-web3/node_modules/web3-core-helpers/lib/errors.js:98:21)
    at /Users/andre/Documents/GitHub/deploy-sc-with-web3/node_modules/web3-core-method/lib/index.js:396:57
    at processTicksAndRejections (internal/process/task_queues.js:95:5)

Frequency: Always
Versions (Add all that apply)

Besu version: [besu --version]: besu/v22.7.0-RC3/osx-x86_64/adoptopenjdk-java-11
Java version: [java -version]: openjdk version "11.0.11" 2021-04-20

package.json dependencies information
"dependencies": {
    "@openzeppelin/contracts": "^4.7.2",
    "ethereumjs-tx": "^2.1.2",
    "web3": "^1.7.5"
}

I have tried to deploy exactly the same way to Ganache, and it is successful, the contract is created.

The problem is solved. It had to do with the gas not being properly set to the size of the smart contract.

The problem is solved. It had to do with the gas not being properly set to the size of the smart contract.

What was the gas you used ?

Hi @DevWonder01 I was using 1000000 as gas limit. By looking at the logs I realized it was not enough, so I increased accordingly to that. Please do that, look at the logs, the math is there 😀.


Refactor names to comply with Kotlin naming conventions

While checking out the Ktor documentation, I noticed some variable names that didn't quite follow Kotlin's naming conventions. So, I went through the codebase and gave them a little update.
Feedback is appreciated!

Thank you for the contribution, @artemmukhin. While it may be that the names don't follow Kotlin's naming conventions, they are generated by the Ktor plugin. So, refactoring them in the docs will cause inconsistency with the generated code. If you think the naming should be refactored for the Ktor plugin generator, please feel free to create an issue on YouTrack.


App starts automatically on Device Startup and not able to share Files from Android to Windows PC

Issues:

My Nitroshare App gets started automatically whenever my device boot up or reboots, even after I close the application before shutting it down.
After Updating Nitroshare Application to latest version, it couldn't scan my Windows PC, neither it can share files with my PC from my Android Phone.

Android Device Details:

Device Name: Samsung Galaxy J7 Prime
Model Number: SM-G610F
Android Version: 8.1.0

Duplication of #58


[Hacktoberfest friendly]  Process stuck after readme creation

Describe the bug
After the readme is generated, the process does not exit so we can't go back to the shell.
To Reproduce

Run npx readme-md-generator
Answer questions
The process does not quit after the readme is generated

that should be a quick way to return to the shell #150
Working fine while testing it

The issue only occurs with npx

I updated the description steps to reproduce in local

I see. Exiting yargs works in that case

Second try: https://github.com/kefranabg/readme-md-generator/pull/151
works with npm start

Found the issue: https://github.com/framework7io/framework7-cli/pull/51

Fixed in #152


Removing use of isolation level in datastore.

In v1beta3 all transactions are serializable.

Was #1343

@tseaver PTAL

LGTM

@tseaver Any ideas for a good way to manage the datastore-v1beta3 branch / keep it up to date with master? Should I send PRs for the rebases?

I'd say we could just merge master to it before merging it back:  since it is a long-lived integration branch, the extra merge(s) (might be more than one) actually document keeping it up to date.

OK.


gofmt main.go

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


Upstream to neovim?

Hey! This looks very promising and I was wondering if neovim could use this and include this into neovim core? If you'd like to read more and share your thoughts: https://github.com/neovim/neovim/pull/19663

Sure, I'd be happy if it were included! The luvit repository is licensed under the Apache license, not sure if/how that affects inclusion in Neovim

Neovim is under apache too I think. Justin will have to take a look at the licensing bit, I'm just here to scout the texts :).
OK, thank you!


Mark stale workflows

If the docs haven't been built in 6 weeks, that's probably ok. If the smoke test / benchmarks haven't run in 6 weeks, then there's likely some action to take.
The last run date is helpful, but if we use a different color (gray?) to indicate that some workflow hasn't run in the last, say, 10 days, it would make these cases clearer.

Closed by #30.


chore: add lint action

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)

Closes #XXXXX

Hey @raisedadead @edatfreecodecamp, this should fail when it starts running.  Some I can easily fix, but I'm not sure how step22 is supposed to work.

I'm not sure which notebook is the latest prototype (none of the ones I have access to seem to match up) but I'd assume that those undeclared variables are referenced in the user's code for that step.


Updated CODE_OF_CONDUCT.md

This pull request enhances the Code of Conduct for the CodeCache project. The updated document aims to create a more comprehensive and inclusive framework for community engagement, ensuring a positive environment for all participants.
Changes Made
Expanded Commitment Section: Added a commitment to diversity and inclusion, emphasizing the project's dedication to a harassment-free experience for all participants, regardless of their backgrounds.
Detailed Expected Behavior: Included specific behaviors that promote respect, consideration, and inclusiveness among contributors. This helps set clear expectations for community interactions.
Clarified Unacceptable Behavior: Provided explicit examples of unacceptable behaviors to ensure clarity on what constitutes harassment, discrimination, and abuse within the community.
Reporting and Enforcement Procedures: Added clear instructions on how to report violations of the Code of Conduct, ensuring that participants know how to address issues effectively.
Consequences of Unacceptable Behavior: Clarified the consequences for participants who engage in unacceptable behavior, outlining potential sanctions and the process for addressing violations.
Acknowledgements Section: Included a reference to the Contributor Covenant as the foundation for the Code of Conduct.
Checklist
My code follows the project's coding style.
I have performed a self-review of my changes.
I have commented on my changes where necessary.
I have updated the documentation as needed.
I have ensured the changes align with community standards.
Additional Notes
This update is essential to foster a supportive and respectful community for CodeCache contributors. By implementing these enhancements, we aim to create a safer environment that encourages collaboration and innovation.

Hi @Sumanth077s,
Thank you for your contribution! However, it’s important to follow the guidelines when submitting pull requests. I noticed that this PR was raised without an assigned issue or an accompanying issue. Please make sure to raise an issue and have it assigned before submitting PRs in the future.
This time, I will let it slide, but please note that moving forward, I'll have to take action for PRs that do not adhere to this process. Kindly refer to the project's Code of Conduct to ensure compliance. Let's maintain a smooth and organised workflow!
Thanks for your understanding.


Support arm64 architecture

We'd like to be able to monitor arm64 servers, as far as I am aware this architecture is not supported at the moment.

Grafana-agent doesn't supported arm64 now. It's a blocker.

Note: this is no longer blocked as grafana-agent-k8s now supports arm64.

Supported in
#303
#308
#312


Split code blocks on newlines and

Put OpenAI API key to .envs text file, as the following setting suggests.
"python.envFile": "${workspaceFolder}/.envs",

@lightaime review pls


Cluttered error message on export fail

Tried to export a full bundle and got the following error:
Error preparing artifacts: UNAUTHORIZED: authentication required; [map[Type:repository Class: Name:deislabs/arsebiscuits-cnab Action:pull]]
Ignoring for now that I had this image locally so I'm not sure why it's trying to pull it - the formatting with all the Go map stringising spew is cluttered.  Could it say something like authentication required to pull repository deislabs/cnab-arsebiscuits?

The reason the pull is occurring is that the library that duffle export is using to grab images reads directly from the remote repository rather than from any docker daemon. The library was designed to run in environments that don't have a docker daemon, such as inside a kubernetes cluster.
The error message is cluttered because duffle export simply wraps the error from the underlying library (probably UNAUTHORIZED: ...).
Solutions include replacing the underlying library and changing the underlying library to check the docker daemon first and/or to emit a less "cluttered" error message.

If it's a string coming from an underlying library then there's not much Duffle can do about it, but if you point me at the underlying library then I will cheerfully raise a bug against that!

The underlying library is github.com/pivotal/image-relocation which is based heavily on github.com/google/go-containerregistry (a.k.a. GGCR). The error message comes from the latter library.
The rationale for using github.com/pivotal/image-relocation to implement duffle export was in order to write an OCI image layout and my lack of familiarity with other libraries that might do the same. (I helped to implement the OCI image layout support in GGCR, although any evidence of this was accidentally stripped out.)
github.com/pivotal/image-relocation avoids any dependency on the docker daemon so that it can run in environments lacking a daemon, such as inside a kubernetes cluster, although I don't think that is a requirement of duffle.

Thanks for opening the issue @itowlson. Since you've opened the issue to fix this in pivotal/image-relocation, I'm going to close this.


doc: retained memory/retention: Add note on mutex configuration

Adds a note on how to configure and what to beware of when
disabling mutex support in a multithreading application

Fixes #63364

@nordicjm, I'm sorry but I am discovering so much problems with the retention system that just pushing the responsability to the user does not seem the correct solution.

@nordicjm, I'm sorry but I am discovering so much problems with the retention system that just pushing the responsability to the user does not seem the correct solution.

This is no different that trying to erase your running image's flash with the flash erase function, the developer needs a basic level of understanding to know how to use things, this is no different.

Problems that I have discovered thus far:
1. No support for userspace access,

2. Vulnerable to toctou attacks,

3. Even when all mutexes are enables and used it cannot be guaranteed that the data in the retention area is not changed before the crc and header are added.

I will make a issue/bug for each of them.

Please do, but they are unrelated to this documentation update.

@nordicjm, I'm sorry but I am discovering so much problems with the retention system that just pushing the responsability to the user does not seem the correct solution.

This is no different that trying to erase your running image's flash with the flash erase function, the developer needs a basic level of understanding to know how to use things, this is no different.

But there is no way for a user to know "how to use" to use the retention system.

@nordicjm, I'm sorry but I am discovering so much problems with the retention system that just pushing the responsability to the user does not seem the correct solution.

This is no different that trying to erase your running image's flash with the flash erase function, the developer needs a basic level of understanding to know how to use things, this is no different.

But there is no way for a user to know "how to use" to use the retention system.

https://builds.zephyrproject.io/zephyr/pr/63434/docs/services/retention/index.html it's clearly documented, what exactly is missing?

@nordicjm, I'm sorry but I am discovering so much problems with the retention system that just pushing the responsability to the user does not seem the correct solution.

This is no different that trying to erase your running image's flash with the flash erase function, the developer needs a basic level of understanding to know how to use things, this is no different.

But there is no way for a user to know "how to use" to use the retention system.

https://builds.zephyrproject.io/zephyr/pr/63434/docs/services/retention/index.html it's clearly documented, what exactly is missing?

The link between the validity and the retention mutex. There is no need to protect against "clashing threads", it is needed to protect against the possible result of clashing threads: the data no longer being OK.

@nordicjm, I'm sorry but I am discovering so much problems with the retention system that just pushing the responsability to the user does not seem the correct solution.

This is no different that trying to erase your running image's flash with the flash erase function, the developer needs a basic level of understanding to know how to use things, this is no different.

But there is no way for a user to know "how to use" to use the retention system.

https://builds.zephyrproject.io/zephyr/pr/63434/docs/services/retention/index.html it's clearly documented, what exactly is missing?

The link between the validity and the retention mutex. There is no need to protect against "clashing threads", it is needed to protect against the possible result of clashing threads: the data no longer being OK.

The data would be OK, one thread does a write and whilst doing that another does a read, the first thread owns the mutex so the second one will wait, the first will write the new data, read the data back to calculate a checksum, then write the checksum which involves taking/releasing the retention mutex 3+ times, during this time, the other thread is completely blocked from continuing. Once the first thread has finished the function, the second function can then continue with the read function call, whereby it will read the correct data.
So what am I missing? Yes if you use retention in one thread then retained memory functions in another, you could corrupt the data, but that would be a user fault, just like if you start loading a firmware update using the img functions then part the way through decide to use a flash function to erase one of the sectors, strangely enough once the firmware update is complete it will not be a valid image.

@nordicjm, I'm sorry but I am discovering so much problems with the retention system that just pushing the responsability to the user does not seem the correct solution.

This is no different that trying to erase your running image's flash with the flash erase function, the developer needs a basic level of understanding to know how to use things, this is no different.

But there is no way for a user to know "how to use" to use the retention system.

https://builds.zephyrproject.io/zephyr/pr/63434/docs/services/retention/index.html it's clearly documented, what exactly is missing?

The link between the validity and the retention mutex. There is no need to protect against "clashing threads", it is needed to protect against the possible result of clashing threads: the data no longer being OK.

The data would be OK, one thread does a write and whilst doing that another does a read, the first thread owns the retention mutex so the second one will wait, the first will write the new data, read the data back to calculate a checksum, then write the checksum which involves taking/releasing the retained memory mutex 3+ times, during this time, the other thread is completely blocked from continuing. Once the first thread has finished the function, the second function can then continue with the read function call, whereby it will read the correct data.
So what am I missing? Yes if you use retention in one thread then retained memory functions in another, you could corrupt the data, but that would be a user fault, just like if you start loading a firmware update using the img functions then part the way through decide to use a flash function to erase one of the sectors, strangely enough once the firmware update is complete it will not be a valid image.

This is not about using retention in one thread combined with retained memory in another, this is only about disabling mutexes. Not considering the problem with combined use of retained memory and retention: when mutexes are enabled the access to the data is protected, so it is possible to validate, write and read because even if different threads are trying to access they are blocked. When mutexes are disabled the data could be changed while performing an operation, so they can no longer be used without caution. The retention_is_valid function can just no longer say that the data is valid: it might be valid (e.g. for a blinfo item), but it might also not be valid (for an ISR item). The api should just respond with the best way for all cases: -ENOTSUP.

@nordicjm, for the special case of a single thread application the retention_is_valid() routine could remain as is.

@jhedberg please re-review

The PR is not a fix for #63364 (retention).

Fix comment removed

It is also not clear what a user should do to "ensure that the function calls do not conflict with each other" (retention).

Then I suggest you buy a book on OS fundamentals and read it


Add an option to cowboy_static to do server push of dependent files

Maybe just a list of related files would be enough. Then if we statically serve some HTML, we can put the CSS/JS in the list and it will be pushed in the given order.

Worth pointing out that browsers are moving away from server push. So this is not a priority at all. This might be useful in specific REST API scenarios but I don't think those would need cowboy_static much.


Add a warning for forming writable key paths when disallowed.

This is an error in -swift-version 5. Emitting a warning for earlier
versions provides a heads-up that the code needs to be updated.
Fixes: rdar://problem/40068274

@swift-ci Please smoke test

I ended up changing this around so that we will now emit a warning on key path subscript writes with literal key paths that would be inferred to be read-only under -swift-version 5.

@swift-ci Please smoke test

@swift-ci Please test source compatibility

I grabbed the logs from the source compatibility run to ensure that this warning is not firing spuriously anywhere. Everything looks good on that front.


Update to SDK version 2.2

🚀 Feature Request
Relevant Package [REQUIRED]

 This feature request is for...  CoAP device service
Description [REQUIRED]
 Use v2.2 of the CSDK (Kamakura release)
Describe the solution you'd like

Describe alternatives you've considered

closed #42


[nrf52] What could cause NRF_802154_TX_ERROR_TIMESLOT_DENIED in nrf_802154_transmit_raw_at?

I'm doing some experiment with CSL on nrf52840 dk. Now I get OT_ERROR_CHANNEL_ACCESS_FAILURE in otPlatRadioTxDone after using nrf_802154_transmit_raw_at to transmit a frame. I used some trick to get the detailed nrf error code. The error in nrf_802154_transmit_failed is NRF_802154_RX_ERROR_DELAYED_TIMESLOT_DENIED. What could be the possible reason for this?
@hubertmis @LuDuda @edmont

@Irving-cl do you have a procedure to reproduce it?

@edmont I cannot put those code on github (for policy reason). I can share the firmware and the steps to reproduce it. Would that be enough for you? If you need the code to find out the reason, I think I can share a package, maybe through drive.

I believe having the code and the instructions on how to reproduce the issue would be the best way to understand it.

@edmont
Thanks. Then I'll share a package with you.

@Irving-cl
I would like to make sure I understood correctly. When you use nrf_802154_transmit_raw_at function, you receive nrf_802154_transmit_failed error with error code 7 that translates to NRF_802154_TX_ERROR_TIMESLOT_DENIED, not NRF_802154_RX_ERROR_DELAYED_TIMESLOT_DENIED. Am I correct?
NRF_802154_TX_ERROR_TIMESLOT_DENIED can be raised in following conditions:

Channel cannot be updated before expected transmission. It may happen only when transmission is scheduled too short before BLE activity.
At scheduled transmission time (when timer IRQ is executed), radio driver critical section is taken by lower-priority execution context. It is possible that radio.c calls nrf_802154_receive() and during such call timer IRQ fires. Critical section is already taken by nrf_802154_receive() and scheduled transmission cannot happen. Such race condition should happen very rarely, unless your code calls 802.15.4 radio driver API in a loop. You can verify if critical section is taken checking m_nested_critical_section_counter : https://github.com/openthread/openthread/blob/f7e16fec240439f54998463f6d8ab2945edbe5b3/third_party/NordicSemiconductor/drivers/radio/nrf_802154_critical_section.c#L55 . If its value is greater than 0, critical section is taken.
High Frequency clock is not ready when TX should happen. If you transit from RX to TX mode, there should be no problem with hfclk. However, if you transit from sleep to TX (could be through RX, but time from sleep to TX is shorter than crystal ramp up), then crystal might not be ready when the transmission should start. You can tweak crystal ramp up time with this constant: https://github.com/openthread/openthread/blob/f7e16fec240439f54998463f6d8ab2945edbe5b3/third_party/NordicSemiconductor/drivers/radio/rsch/nrf_802154_rsch.c#L25 . You can verify HFclk readiness in m_approvied_prios variable captured when the problem occurs (you must stop execution with a debugger on the problem, because content of this variable would change in dozens of microseconds): https://github.com/openthread/openthread/blob/f7e16fec240439f54998463f6d8ab2945edbe5b3/third_party/NordicSemiconductor/drivers/radio/rsch/nrf_802154_rsch.c#L55
Radio arbiter prevents radio access for 802.15.4. In dynamic multi-protocol applications access to radio is granted by radio arbiter. It is possible that sometimes arbiter prevents radio access when scheduled transmission should start. This also can be verified in m_approved_prios.

I hope these details are good hints to move debugging process forward.

@hubertmis
Thanks very much for the hints!
Let me supplement something about my case. So I found that frames are not sent successfully (from otPlatRadioTxDone, and the error is OT_ERROR_CHANNEL_ACCESS_FAILURE. From the log I can see that nrf_802154_transmit_raw_at is successfully called in otPlatRadioTransmit. I found that the only two places to set kPendingEventChannelAccessFailure (which can cause OT_ERROR_CHANNEL_ACCESS_FAILURE) is in otPlatRadioTransmit and nrf_802154_transmit_failed. As I said, otPlatRadioTransmit was successfully called. So it should be nrf_802154_transmit_failed that sets kPendingEventChannelAccessFailure. To know the exact error, I added a static variable in nrf_802154_transmit_failed and record the error. And that error is 7. So I believe it's NRF_802154_TX_ERROR_TIMESLOT_DENIED.
From your hints, I think the most possible reason is that my device transit from sleep to TX. (I haven't verified yet) If this issue only happens for nrf_802154_transmit_raw_at? I mean, will nrf_802154_transmit_raw experience the same issue? I guess no because we have sleepy end devices and when they do TX the transit from sleep to TX. Am I right about this?

Follow up:
The reason seems to be transition from sleep to TX. I turned the capability of OT_RADIO_CAPS_SLEEP_TO_TX on nrf so that  in SubMac::BeginTransmit so that it is enforced to do receiving before transmission, then the transmission was successful:
    if ((mRadioCaps & OT_RADIO_CAPS_SLEEP_TO_TX) == 0)
    {
        error = Get<Radio>().Receive(mTransmitFrame.GetChannel());
        OT_ASSERT(error == OT_ERROR_NONE);
    }

I mean, will nrf_802154_transmit_raw experience the same issue?

This function does not require exact timings. If hfclk is not ready when TX is about to happen, TX is delayed until hfclk is ready. However such delay does not work for nrf_802154_transmit_at, because timings for this function must be strict.
Have you tried to increase the value of PREC_RAMP_UP_TIME? We've set this value based on crystal timing data from nRF Product Specification. I guess your crystal start time is longer than examples we took while defining this value.

@hubertmis
I would try to increase the ramp up time. How should we choose the proper value for it? Is there any side effect if we set a value that's too big? Or we should just increase the value until it can work successfully?

How should we choose the proper value for it?

Datasheet of the crystal you use should define its startup time. You can use this value, try to add some margin and verify if it works correctly.

Is there any side effect if we set a value that's too big?

The side effect is increased power consumption because the crystal is powered longer than necessary.

Or we should just increase the value until it can work successfully?

That's one way to go, but be aware that crystal properties vary between each particular component, it changes with temperature and time. Because of that I would recommend to add some safety margin. The cost would be a little higher power consumption, but the risk that the device would stop working correctly after some time or when the temperature changes would be lowered.

@Irving-cl , could you confirm if the solution I suggested work for you? Can we close this issue now?

@hubertmis
Sorry for responding late. I'll do it soon.

@hubertmis
Update:
I added the value of PREC_RAMP_UP_TIME and tested a couple of times. I tested on nrf52840-dk. The value was originally 480 as defined in nrf_802154_rsch.c:
#define PREC_HFXO_DEBOUNCE_TIME                256
#define PREC_CRYSTAL_WORST_CASE_POWER_UP_TIME  75
#define PREC_TIMER_GRANULARITY_MARGIN          31
#define PREC_POWER_CLOCK_IRQ_HANDLER_PROC_TIME 50
#define PREC_RTC_IRQ_HANDLER_PROC_TIME         60
#define PREC_RAMP_UP_MARGIN                    8

#define PREC_RAMP_UP_TIME                      (PREC_HFXO_DEBOUNCE_TIME +                \
                                                PREC_CRYSTAL_WORST_CASE_POWER_UP_TIME +  \
                                                PREC_TIMER_GRANULARITY_MARGIN +          \
                                                PREC_POWER_CLOCK_IRQ_HANDLER_PROC_TIME + \
                                                PREC_RTC_IRQ_HANDLER_PROC_TIME +         \

I changed the value to 1000, 2000, 4800, 12000, 48000. For small values like 1000 and 2000, The transmission still got Channel Access Failure. However for big values like 4800 and larger than that, all the CSL transmissions seem to be done earlier and the receiver cannot receive that frame.

Thanks for the update.

However for big values like 4800 and larger than that, all the CSL transmissions seem to be done earlier and the receiver cannot receive that frame.

That's interesting. PREC_RAMP_UP_TIME should not change timings of the actual transmission. It modifies only the time when HFclk is requested (how long before the transmission). Could you share wireshark captures for greater values like 4800, 12000, 48000? I would like to compare them to look for potential source of timing problems.
Could you also comment what is your LFclk source PPM value and HF crystal PPM value?

Could you also comment what is your LFclk source PPM value and HF crystal PPM value?

How should I check the PPM value? @hubertmis

How should I check the PPM value?

For HF xtal you should find it in datasheet of the crystal.
For LF, if you use crystal, you can check datasheet. If you don't use crystal, just let me know if you select RC oscillator or clock synthesis. I'll get values of PPMs for these sources from nRF5 Product Specification

I'm just using two NRF52840 DKs (without any other devices). Can we find the PPM value for it? I don't have the datasheet of its crystal. @hubertmis

Hi @hubertmis , I think the test was done on Nordic 52840DK using API nrf_802154_transmit_raw_at with CCA disabled. Before nrf_802154_transmit_raw_at is called, device is in sleep mode. So the default ramp up time in code is not enough for DK when board transit from sleep state to tx directly.

I can see in the <> that the crystal is 32.768 kHz.

Thanks for this information. I assumed you use a custom board with different peripherals what causes the problems.
Taking into account that you test using the same hardware I do, the reason must be purely software. Perhaps some differences between our systems.
Do you know what is average/maximal ISR latency in your system?

Let me explain why I ask about ISR latency.
The delayed transmission in 802.15.4 works in the following way:

main context schedules transmission at timestamp X
RTC ISR at (X - radio ramp up - precondition ramp up) requests HFclk
RTC ISR at (X - radio ramp up) starts transmission

If RTC ISR is delayed, the preconditions are requested too late, or the transmission starts too late. It seems you observe both problems. Because of that I suspect ISR latency being the source of the problem.
Possible workaround for 802.15.4 system is:
RADIO IRQ priority = 0
RTC IRQ priority = 1
Other IRQs in the systems have lower priority.
Possible workaround for multi-protocol with SoftDevice:
RADIO IRQ: don't change it, it is managed by SoftDevice
RTC IRQ priority = 4
Other IRQs in the system have lower priority.
Moreover, for both workarounds masking interrupts (using NVIC or PRIMASK/__irq_disable()) must be only for very short time (like up to 2 microseconds).

Here is the pcap for the case when setting PREC_RAMP_UP_TIME to 4800:
csl.pcapng.zip
Note that No.21 (Link Request) and No.29 (Ping, and its re-tx) are sent using CSL transmission. Sending time of No.21 is based on CSL IE of No.20 (seems correct). Sending time of No.29 is based on CSL IE of No.25 (seems incorrect).
I think there may be some software problems. Just provide the capture for you for more details. BTW, if we disable OT_RADIO_CAPS_SLEEP_TO_TX and don't change ramp up time (480), everything goes fine.
@hubertmis

@Irving-cl , I have one more question about the setup. If I remember correctly, OpenThread MAC keeps a constant value, how long in advance the delayed transmission is requested (is it OPENTHREAD_CONFIG_MAC_CSL_REQUEST_AHEAD_US?).
I think this value must be greater than PREC_RAMP_UP_TIME. If you set PREC_RAMP_UP_TIME to 4800, the OT MAC "in-advancie-csl-time" should be like 5200

@hubertmis Ah ok. Currently we set OPENTHREAD_CONFIG_MAC_CSL_REQUEST_AHEAD_US to 2000. I also tried setting PREC_RAMP_UP_TIME to 2000 or 1000, but I got Channel Access Failure. Does that mean if we want to solve this problem by increasing PREC_RAMP_UP_TIME, we have to use greater AHEAD time?
I will try using larger OPENTHREAD_CONFIG_MAC_CSL_REQUEST_AHEAD_US. But it seems that 5200 blocks our system a little bit longer (and not even sure if the value works). I'm also curious what would happen if the AHEAD time is not greater than PREC_RAMP_UP_TIME. Currently as I observed, the transmission is done earlier which is quite weird. Why would that happen? I'm also checking if there's some error in OT logic. BTW, in practice, the actual AHEAD time is not ensured greater than PREC_RAMP_UP_TIME even if we set it greater than it because there may be some delay for the software timer.

Does that mean if we want to solve this problem by increasing PREC_RAMP_UP_TIME, we have to use greater AHEAD time?

I'm not sure, I'm trying to order information we have in my mind. I don't have the final conclusion yet.

I'm also curious what would happen if the AHEAD time is not greater than PREC_RAMP_UP_TIME.

By design, calling nrf_802154_transmit_at() too late should result in reporting error. I think the function returns false. However, I think that such erroneous condition could have lower test coverage and there could be some miscalculation we have not hit in our tests yet.
I'm checking the pcap you posted. I agree that frame 21 is transmitted with correct delay.
The frame with number 29 seems transmitted 1126 microseconds too early, what gives us in 10.272 seconds timespan 109 PPM of imprecision. I think that crystals in nRF52840-DKs are better than 40 PPM. Even if they drifted from each other with maximal value, the result should not exceed 80 PPM.
Frame 30 is transmitted 1004 us too early (85 PPM)
Frame 31 is transmitted 893 us too early (67 PPM)
Frame 32 is transmitted 796 us too early (54 PPM)
From the numbers above, I suspect that the timestamp of frame 25 was incorrectly captured. I'm not sure yet how to verify. I'll check the code later today to find what variables might be helpful to capture.

@hubertmis
Thanks. I'm also working on this to see if there's any other error in our code.

I calculated the values a little more. It seems that RTC of failing device drifts around 75 PPM from sniffers TIMER. But it does not explain why timestamp inaccuracy is around 2 ms. I think we need more data to narrow down the problem.
@Irving-cl , could you repeat your test with more ping requests? I mean after series of 4 retransmission, could you start another sequence or two?
Would it be possible to run the same test starting ping sequence with different delays from synchronization "Link Accept" message? Like 2 seconds after, 5 seconds after, 10 seconds after, 15 seconds after. I'm curious if such delay would affect the results.
I have one more question about the test setup. It seems that both devices include CSL IE in data frames. Does it mean it is CSL to CSL communication? Is Link Req -> Link Acc+Req -> Link Acc sequence sent using CSL? Are any of the devices entering sleep state during this sequence?

@Irving-cl , or alternatively could you share your project, or elf files with debug symbols enabled? I think that running it in trace debugger would rapidly answer what's the source of the timing problem.

@hubertmis

or alternatively could you share your project, or elf files with debug symbols enabled? I think that running it in trace debugger would rapidly answer what's the source of the timing problem.

Sorry I'm not allowed to share it due to our policy. Could you give me some guide about how to use the trace debugger? I'm interested in that and I think it may help a lot in our future work.

I have one more question about the test setup. It seems that both devices include CSL IE in data frames. Does it mean it is CSL to CSL communication? Is Link Req -> Link Acc+Req -> Link Acc sequence sent using CSL? Are any of the devices entering sleep state during this sequence?

Yes, we're doing some experimental work for communication between two SSEDs. That's why Sleep->TX transition happens. In short, the first Link Req and the ping were sent using CSL transmission. And the Link Acc+Req and Link Acc are sent directly, not CSL transmission. So they would both enter sleep state at most time, and wake up to receive or transmit when there's a need.

Could you give me some guide about how to use the trace debugger?

I meant this debug probe: https://www.segger.com/products/debug-probes/j-trace/models/j-trace/ . It gets program flow while the application is running and among other things it shows preemptions or other ISR delay causes.

@Irving-cl , could you share a pcap file with PREC_RAMP_UP_TIME set to default value? I would like to compare them.

@hubertmis
When we use default PREC_RAMP_UP_TIME and SLEEP_TO_TX enabled, we cannot see the ping because it wasn't sent (because of Channel Access Failure).  Here is the capture:
csl-default-ramp-up.pcapng.zip The first Link Request could be sent because we turned on the device's radio (start to receive). And some logs from the device: