text:
Data race on submission URL

I have a unit test that calls WithSubmissionUrl to set a new target, but a previous unit test has already called Start, and there's no way to terminate that goroutine. So, I'm writing over the string at the same time trapCall is reading it.
WARNING: DATA RACE
Write by goroutine 23:
  github.com/go-kit/kit/metrics/circonus.TestGauge()
      /home/travis/gopath/src/github.com/go-kit/kit/metrics/circonus/circonus_test.go:106 +0x295
  testing.tRunner()
      /tmp/workdir/go/src/testing/testing.go:456 +0xdc

Previous read by goroutine 10:
  github.com/circonus-labs/circonus-gometrics.trapCall()
      /home/travis/gopath/src/github.com/circonus-labs/circonus-gometrics/circonus-gometrics.go:340 +0x14a
  github.com/circonus-labs/circonus-gometrics.submit()
      /home/travis/gopath/src/github.com/circonus-labs/circonus-gometrics/circonus-gometrics.go:230 +0x93
  github.com/circonus-labs/circonus-gometrics.Start.func1()
      /home/travis/gopath/src/github.com/circonus-labs/circonus-gometrics/circonus-gometrics.go:396 +0x974

The fastest fix is to wrap all access of package globals with mutexes. The better fix is to stop using package globals :)

no more package globals being used. i think we're good on this one.

authors: maier peterbourgon

repo: circonus-labs/circonus-gometrics


text:
ORION-2525: fsoc solution zap + deprecate include-tags flag for fsoc ks commands

Description
We are adding a new solution command: fsoc solution zap.  This will upload an empty version of a solution, removing all types and objects that are present in the solution.  This will only work for non-stable tagged solutions.  W
We have also marked the include-tags flag as hidden as this field is not in our public open api spec at this point of time so we should not expose it to our users yet.
Type of Change

[X] Bug Fix
[X] New Feature
[ ] Breaking Change
[ ] Refactor
[ ] Documentation
[ ] Other (please describe)

Checklist

[X] I have read the contributing guidelines
[X] Existing issues have been referenced (where applicable)
[X] I have verified this change is not present in other open pull requests
[X] Functionality is documented
[X] All code style checks pass
[X] New code contribution is covered by automated tests
[X] All new and existing tests pass

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

Comparison is base (ba840f9) 26.88% compared to head (79617c1) 26.88%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #275   +/-   ##
=======================================
  Coverage   26.88%   26.88%
=======================================
  Files          44       44
  Lines        4564     4564
=======================================
  Hits         1227     1227
  Misses       3242     3242
  Partials       95       95

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

source: gharchive/pull-request

repo: cisco-open/fsoc

license_type: permissive

license_source: github-api


text:
Fixed gse include path for use with FetchContent

Moving CMakeLists.txt up to the src/gse directory helps minimize the number of .. used in paths.

@glhewett Nice work, but I think we need the same change to src/common for this to work

fixed.

authors: RichLogan glhewett

repo: cisco/gse


text:
Add iOS/mobile device support

Is your feature request related to a problem? Please describe.
Papermerge is quite unusable since it does not support touch input. When using iPad or another device that does not support a right click in web interfaces, it results in poor user experience.
Describe the solution you'd like
A mobile/touch friendly interface would make Papermerge much more usable.
Describe alternatives you've considered
N/A
Additional context
N/A

@cevatkerim, thanks for opening this issue!

This may not be directly related with the above bug, but it's also related to mobile:
When using mobile (tested with Firefox 90.1.3 on Android) a lot of stuff is "hidden".
E.g. when I want to create a user, the whole box containing the two buttons to "Create" or "Cancel" isn't visible.
Or when opening a file it only shows the file itself, the metadata "box" isn't displayed, etc.

source: gharchive/issue

authors: Melkor333 cevatkerim ciur

repo: ciur/papermerge


text:
🛑 AppCheck is down

In bea9387, AppCheck (https://www09.8f7.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: AppCheck is back up in 6b9b52d after 36 minutes.

repo: civcicd/uptime-monitor

license: MIT


text:
Projects not showing up under individual org page for index contributors

Overview
For orgs that are tagged as index contributors in the Civic Tech Organizations page, when you click on some of them, no projects show up under the individual org page.  As index contributors, they should have projects tagged with "civictechindex"
Action Items

[ ] Investigate where the disconnect is between orgs flagged as contributors and their tagged projects
[ ] Implement fix in front end if needed or notify PM where to update org data

Just some info from a quick search on github.com.

Code for Buffalo is the index contributor that returns no projects
http://civictechindex.org/organization/code-for-buffalo
Code For Buffalo does have a project with the "civictechindex" tag
https://github.com/search?p=4&q=topic%3Acivictechindex&type=Repositories
Code For Buffalo uses the tag "buffalo" in projects, rather than some variations like "hack-for-la" or "code-for-kc"

Here are the queries we're using to retrieve the organization's projects with "civictechindex". Notice we don't use "buffalo".

Here's a query that does return the correct result, but it uses the CodeForBuffalo github user (it works without the org:CodeForBuffalo that's also in this query)
https://github.com/search?q=org%3ACodeForBuffalo+topic%3Acivictechindex+user%3ACodeForBuffalo
There's a "github_user" field in the backend organization model that's available to use for this case. Or maybe just use the github_user instead of the organization tag variations. But I don't know if there are cases that require those.

We do want to encourage the proper use of affiliation tags.  So we have the following rules

We don't list someone under their org in the contributors section unless they use one of the various of the tags that we accept.  For example, we would not accept Buffalo because other orgs might use that.  We will accept code-for-buffalo, codeforbuffalo, code4buffalo.

@cnk please see Bonnie's clarification of current affiliation tag issues above.  Let me know if we need to discuss how to tackle them.  Thanks

I think we need to clarify that "they need to use an affiliation tag" means "The organization needs their repositories tagged with a topic (that is GH's word for our 'tags') that is one of our recognized variations on their name".
I suspect several of our current 'contributors' will need to update their tagging - but it's hard to say if we don't have good data for the org tags. Before I modify our 'update_contributors' script with this new restriction, let's get the data import from #1036 done. Then the issues are likely to be useful / valid.

This should be split into new issues

[frontend] This sounds like a frontend change. We only store the orgs in the backend and not their repos. The frontend is what queries and displays the repos. This kind of negates point 2 below. This hidden repo behavior was what triggered the current issue to be created.

[frontend] We can query the repo's organization to see whether it belongs to codeforbuffalo or codeforamerica. This is what the linked pull request is doing. If the user clicks to see Code For Buffalo's repos, it does a query for topic:civictechindex and org:CodeForBuffalo. I think this solution addresses the current issue correctly.

[backend] This is what cnk is addressing above

[frontend] This is a frontend thing since it involves the tag generator. Run the queries in the frontend to display what's appropriate.

Here's the expected behavior discussed at the 1/27 meeting:
The backend script should NOT mark an affiliated org as index contributor unless it has a repo that contains BOTH 'civictechindex' and a proper org affiliation topic tag.
So, in the case of Code for Buffalo, rather than having it show up as index contributor and have an empty page, we would not want to show the organization at all if the index contributor filter is on. This means the backend should not check the index contributor flag.
Question/clarification: For non-affiliated orgs, we require only that the 'civictechindex' topic tag be present for the org to be an index contributor?

Progress - not much progress on front end since last update
Blockers - need to make instructions more clear for orgs to set their affiliation tags in their projects.  Also awaiting data migration in #1036 and other back end logic updates for flagging orgs as contributors
Availability - 2 days this week
ETA - pending blockers

authors: ExperimentsInHonesty bruceplai cnk fyliu

repo: civictechindex/CTI-website-frontend


text:
Enable applicants to download and print completed applications

Is your feature request related to a problem? Please describe.
A group of Trusted Intermediaries mentioned that it's helpful to print the completed program application for a resident/client to take with them. Residents often want the physical form to take with them. They mentioned it can be helpful if the residents seeks services from multiple CBOs, they can take their application to the next TI.
Describe the solution you'd like
An option on the application confirmation page that allows the applicant (TI or resident) to download then print the completed application.
Additional context
It would be helpful if it included all completed questions as well as a printout of any uploaded documents. There may be data privacy concerns with the email option, would want to check with Privacy on this.
Done when
Resident or TI can completed application.

@swatkat1 is considering this feature as a good project for summer intern.

This was a feature requested during listening sessions with community-based orgs (digital navigators) on April 25th.

Possibly change to just download as PDF.  Adobe can print from there and possibly open users email application.

For responsiveness, I recommend laying out the information side by side, so on mobile buttons can stack. Here's a mockup!

authors: elisekalstad msprenke sijiayam

repo: civiform/civiform


text:
Difference between existing packages?

Hi, I just notice this package and I'm wondering about what's the difference between this package and those existing packages like Pickle.jl and NPZ.jl? And maybe it's worth directly depending on them?

This is unregistered and very experimental!
Partly I don't particularly like the API of NPZ.jl and partly putting them in the same place allows some useful behaviour, like you can reuse the Python parser to implement reading npy files, and the pickle parser allows parsing a wider range of npy files, e.g. ones containing strings.

authors: chengchingwen cjdoris


text:
State of the library and future plans

Hi,
I came across your library after asking about open source LoRaWan stack implementartions here.
We want to develop sensor nodes in a factory environment, we're planning to use STM32Lx devices, communicating over LoRaWan with a gateway. We're using Atollic TrueStudio (configuration code generated with STM32CubeMX) and I would like to include your library to the project, I tried to do so with lorawan-mac I i wasn't able to do so.
After searching LoRaWan stacks I think yours is the most sane one, but i would like to know what is your roadmap, maybe if you accept contributions, plans to implement Class B and C, etc.

Hello
Thanks, I started this project to learn the protocol and also because I felt the other implementations looked crazy.
This project is active but I am (probably) the only person using it. It would be great to get some more users and contributors that appreciate the style of this implementation over the alternatives. Before accepting contributions I think it would be necessary to lay down some guidelines so that no effort is wasted.
There is no roadmap, there could be one if there was serious interest. The reason I haven't done class B and C is because I have no need for these modes. The biggest challenge with implementing these modes (or indeed any new features) is verifying that they work correctly. Class B needs a lot more tooling than class A.
I would describe the quality as experimental. I don't think you should use it for anything serious at the moment. This could change if more people use it. I think it would also be good to run it through the LoRaWAN conformance test at some point.
I'm planning to release 0.1.7 in the next week or two. I'll see if I can also produce a list of what works well and what needs to be improved.

Hi,

I would describe the quality as experimental. I don't think you should use it for anything serious at the moment. This could change if more people use it. I think it would also be good to run it through the LoRaWAN conformance test at some point.

Thanks for the quick reply, to be honest I just been told that the plan A is to use modules commanded via AT commands, so I'm no longer in a hurry, at least not for work projects.
I'm still interested in using this library as a learning exercise and in personal projects, seems like I will be using LoRaWan for a while and, as you did when you started this project, I would use it to learn the protocol.

I'm planning to release 0.1.7 in the next week or two. I'll see if I can also produce a list of what works well and what needs to be improved.

I would like to propose the following, let me know if you agree. I can get more familiar with LoRaWan and maybe other implementations of it, then if you feel like it I can help with small and easy tasks of the to be implemented list.

So far I have been able to include LDL to my project and initialize boath Board and Radio, just noticed I must implement all the weak functions in lora_system, am I right? Maybe a porting guide would be nice for us who aren't familiar with LDL.
Regards

I think an AT command module is wise for proof of concept. You don't want to get bogged down in technical details before you know if the technology is right for the application.
Yes I agree a todo list is a good idea.
Yes I agree a porting guide would be helpful.
Some of the system interfaces will work just fine with the weak implementations, while others are show stoppers. Looking at the API documentation it occurs to me not all of the mandatory interfaces are marked as mandatory.
The arduino wrapper is a good reference for what is mandatory.

I should also mention that since I am in the UK I only ever use the setting for the EU_863_870 region. I have in the past emulated some of the other regions but not for some time.

I'm located in Mexico, will test the US_902_928 region.

Some of the system interfaces will work just fine with the weak implementations, while others are show stoppers. Looking at the API documentation it occurs to me not all of the mandatory interfaces are marked as mandatory.

I didn't took a deep look, but I assume the mandatory interfaces are those marked with @warning this function must be implemented on target for correct operation.

The arduino wrapper is a good reference for what is mandatory.

I will take a look at it, so far i haven't seen any timer being setup, while in loramac-node, they use the microcontroller RTC, is this only neccesary on Class B or C nodes?

I didn't took a deep look, but I assume the mandatory interfaces are those marked with @warning this function must be implemented on target for correct operation.

Yeah more or less.

I'm at master, should i also check the development branch?

Master is best. Development might not work properly.

so far i haven't seen any timer being setup

LDL has a bunch of internal timers that depend on the platform providing a free-running 32bit counter.

LDL_System_time() returns the counter value at any time
LDL_System_tps() returns the rate at which the counter increments (ticks per second)
LDL_System_eps() returns the error in ticks (error per second)

So on Arduino for example:

LDL_System_time() wraps micros()
LDL_System_tps() returns 1000000
LDL_System_eps() returns 5000 to account for a ceramic resonator

LDL has a bunch of internal timers that depend on the platform providing a free-running 32bit counter.
LDL_System_time() returns the counter value at any time
LDL_System_tps() returns the rate at which the counter increments (ticks per second)
LDL_System_eps() returns the error in ticks (error per second)
So on Arduino for example:
LDL_System_time() wraps micros()
LDL_System_tps() returns 1000000
LDL_System_eps() returns 5000 to account for a ceramic resonator

Haven't been on my work station, I'm using STM32 devices, I guess the HAL_GetTicks() function for LDL_System_time() should work, it should return the same value in LDL_System_tps() and I will calculate the value for LDL_System_eps()

Looking good.
I see the problem, you need to connect the radio "DIO" control lines. That part is missing from the example you are based on, it's not very clear.
You need to detect the DIO line(s) rising edge and then call LDL_MAC_interrupt(&mac, n, LDL_System_time()) where n is the index of the line (e.g. DIO0 is n == 0). You only need DIO0, DIO1, DIO2, and DIO3.
This is how the arduino wrapper does it. That function is called by an ISR for a particular control line. There is implementation specific logic but the important part is that I call LDL_MAC_interrupt().
If you use an interrupt, make sure to define LORA_SYSTEM_ENTER_CRITICAL and _LEAVE_CRITICAL. This should work:
#define LORA_SYSTEM_ENTER_CRITICAL(APP) volatile uint32_t primask = __get_PRIMASK();__disable_irq();
#define LORA_SYSTEM_ENTER_CRITICAL(APP) __set_PRIMASK(primask);
I recommend to put this in a header file, then define LORA_TARGET_INCLUDE to be the name of that file (e.g. -DLORA_TARGET_INCLUDE='"your_header.h"'). All the other LDL build options can go there.
You will need to also define:

LORA_ENABLE_SX1276
LORA_ENABLE_US_902_928
LORA_DISABLE_FULL_CODEC

I assume you've already done this somewhere I can't see. I mean, you can do it all from the makefile if you prefer.
Once you get that sorted you will probably find that the example sends too frequently since the US doesn't have a duty cycle limit. To slow it down you can either add a delay in your app, or set LDL_MAC_setAggregatedDutyCycle() to impose a global duty cycle limit. A setting of 2 will give you a 1% duty cycle limit.

Hi,
Thanks for taking a look at the project, just noticed i uploaded the keys of it, so i had to make the repo private :/, let me know if you want me to give you access to it.

I see the problem, you need to connect the radio "DIO" control lines. That part is missing from the example you are based on, it's not very clear.
You need to detect the DIO line(s) rising edge and then call LDL_MAC_interrupt(&mac, n, LDL_System_time()) where n is the index of the line (e.g. DIO0 is n == 0). You only need DIO0, DIO1, DIO2, and DIO3.
This is how the arduino wrapper does it. That function is called by an ISR for a particular control line. There is implementation specific logic but the important part is that I call LDL_MAC_interrupt().

Here's how i implemented it:
void HAL_GPIO_EXTI_Callback(uint16_t GPIO_Pin)
{
	switch (GPIO_Pin) {
	case DIO0_Pin:
		LDL_MAC_interrupt(&mac, 0, LDL_System_time());
		break;
	case DIO1_Pin:
		LDL_MAC_interrupt(&mac, 1, LDL_System_time());
		break;
	case DIO2_Pin:
		LDL_MAC_interrupt(&mac, 2, LDL_System_time());
		break;
	case DIO3_Pin:
		LDL_MAC_interrupt(&mac, 3, LDL_System_time());;
		break;
	default:
		break;
	}
}

If you use an interrupt, make sure to define LORA_SYSTEM_ENTER_CRITICAL and _LEAVE_CRITICAL. This should work:
#define LORA_SYSTEM_ENTER_CRITICAL(APP) volatile uint32_t primask = __get_PRIMASK();__disable_irq();
#define LORA_SYSTEM_LEAVE_CRITICAL(APP) __set_PRIMASK(primask);
I recommend to put this in a header file, then define LORA_TARGET_INCLUDE to be the name of that file (e.g. -DLORA_TARGET_INCLUDE='"your_header.h"'). All the other LDL build options can go there.

My custom header file is named LDL_options.h and goes as follows:
#ifndef LDL_OPTIONS_H_
#define LDL_OPTIONS_H_

#include "cmsis_gcc.h"

// http://stm32f4-discovery.net/2015/06/how-to-properly-enabledisable-interrupts-in-arm-cortex-m/

static volatile uint32_t primask = 0;

#define LORA_SYSTEM_ENTER_CRITICAL(APP) do { primask = __get_PRIMASK(); __disable_irq(); } while (0);
#define LORA_SYSTEM_LEAVE_CRITICAL(APP) __set_PRIMASK(primask);

#endif /* LDL_OPTIONS_H_ */

You will need to also define:
LORA_ENABLE_SX1276
LORA_ENABLE_US_902_928
LORA_DISABLE_FULL_CODEC
I assume you've already done this somewhere I can't see. I mean, you can do it all from the makefile if you prefer.

Yep, I define those symbols on the IDE, but now i think it's better to have them on the LDL_options.h file so others doesn't need to load the project into the IDE just to see the configuration. So the LDL_options.h file ends up like this:
#ifndef LDL_OPTIONS_H_
#define LDL_OPTIONS_H_

#include "cmsis_gcc.h"

// http://stm32f4-discovery.net/2015/06/how-to-properly-enabledisable-interrupts-in-arm-cortex-m/

#define LORA_ENABLE_SX1276
#define LORA_ENABLE_US_902_928
#define LORA_DISABLE_FULL_CODEC

// #define LORA_TARGET_INCLUDE	 /* See lora_platform */

static volatile uint32_t primask = 0;

#define LORA_SYSTEM_ENTER_CRITICAL(APP) do { primask = __get_PRIMASK(); __disable_irq(); } while (0);
#define LORA_SYSTEM_LEAVE_CRITICAL(APP) __set_PRIMASK(primask);

#endif /* LDL_OPTIONS_H_ */

Once you get that sorted you will probably find that the example sends too frequently since the US doesn't have a duty cycle limit. To slow it down you can either add a delay in your app, or set LDL_MAC_setAggregatedDutyCycle() to impose a global duty cycle limit. A setting of 7 will give you a ~1% duty cycle limit.
edit: made mistake on global duty cycle

Will edit the comment once i get some results later today.
Thanks for the help and patience.

10km is probably too far for initial debug. Too close (i.e. sitting right next to the gateway) can also be an issue.
It's often useful to print time (i.e. LDL_System_time()) with each event for double checking timing.

Hi,
Thanks for the tips. I had to modify the logging macros (replacing PRIu32 for %d) because of my underlying functions. Everything else seems to be working as expected. Will report back when I get a gateway.

license: mit

license_source: bigquery


text:
Docs for 1.0-alpha?

Are these available somewhere convenient?

Are these available anywhere at all ?

authors: mafrosis thicklord

repo: cjlucas/rtorrent-python


text:
always destroy instances

Expected Behavior
an GCP and DO cloud providers always destroy instances:
2021-07-30 15:59:33.646 | INFO     | uvicorn.protocols.http.h11_impl:send:461 - 127.0.0.1:60922 - "GET /destroy HTTP/1.1" 200
2021-07-30 15:59:36.640 | INFO     | uvicorn.protocols.http.h11_impl:send:461 - 127.0.0.1:60922 - "GET /destroy HTTP/1.1" 200
2021-07-30 15:59:30.937 | INFO     | uvicorn.protocols.http.h11_impl:send:461 - 127.0.0.1:60924 - "GET /destroy HTTP/1.1" 200

The UI regularly calls the /destroy endpoint to get a list of all the proxy instances pending deletion. This get request you are seeing is just that and it's not actually deleting the proxies.
If you start Cloudproxy and don't open the UI, then you'll notice those requests aren't there.

repo: claffin/cloudproxy


text:
image preprocessing for training

For the first batches of training, we plan to use video frames extracted from AAPB videos. However, there's concerns around how to "normalize" different image size and aspect ratios from videos from different decades. This thread is to discuss how we implement the normalizing strategies.

We decided to go only with 4:3 videos (before HD broadcasting era, circa early 2000s) in the early rounds of annotation.

Note that as long as we are using the pre-trained backbone weights, those weights in torch-vision package come with their own preprocessing code. That is, we can add some additional preprocessing based on some domain knowledge before the torch-shipped preprocessing. However, as of now we don't see a lot of needs for doing so.

repo: clamsproject/app-swt-detection


text:
clangd "--query-driver" option doesn't follow symlinks

When I run clangd with the --query-driver option set to a path containing a symlink, the argument has no effect and I still have missing system headers. In the following case, <iostream> can't be found.
#include <iostream>

int main(int argc, char* argv[])
{
    std::cout << "hi\n";
    return 0;
}

I can work around this issue by using the complete path without any symlinks.
Within the logs, the oe-workdir path item is a symlink to another location.
Logs
Please attach the clangd stderr log if you can. (Usually available from the editor)
If possible, run with --log=verbose - note that the logs will include the contents of open files!
If this is a crash, try to put llvm-symbolizer on your PATH per the troubleshooting instructions.
[START][2024-03-16 12:09:47] LSP logging initiated
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	'I[12:09:47.584] clangd version 17.0.6\nI[12:09:47.584] Features: linux\nI[12:09:47.584] PID: 102869\nI[12:09:47.584] Working directory: /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight\nI[12:09:47.584] argv[0]: /usr/bin/clangd\nI[12:09:47.584] argv[1]: --log=verbose\nI[12:09:47.584] argv[2]: --query-driver=/home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/oe-workdir/recipe-sysroot-native/usr/bin/aarch64-poky-linux/aarch64-poky-linux-g++\nV[12:09:47.584] User config file is /home/jasonc/.config/clangd/config.yaml\nI[12:09:47.584] Starting LSP over stdin/stdout\nV[12:09:47.584] <<< {"id":1,"jsonrpc":"2.0","method":"initialize","params":{"capabilities":{"offsetEncoding":["utf-8","utf-16"],"textDocument":{"callHierarchy":{"dynamicRegistration":false},"codeAction":{"codeActionLiteralSupport":{"codeActionKind":{"valueSet":["","quickfix","refactor","refactor.extract","refactor.inline","refactor.rewrite","source","source.organizeImports"]}},"dataSupport":true,"dynamicRegistration":false,"isPreferredSupport":true,"resolveSupport":{"properties":["edit"]}},"completion":{"completionItem":{"commitCharactersSupport":true,"deprecatedSupport":true,"documentationFormat":["markdown","plaintext"],"insertReplaceSupport":true,"insertTextModeSupport":{"valueSet":[1,2]},"labelDetailsSupport":true,"preselectSupport":true,"resolveSupport":{"properties":["documentation","detail","additionalTextEdits","sortText","filterText","insertText","textEdit","insertTextFormat","insertTextMode"]},"snippetSupport":true,"tagSupport":{"valueSet":[1]}},"completionItemKind":{"valueSet":[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25]},"completionList":{"itemDefaults":["commitCharacters","editRange","insertTextFormat","insertTextMode","data"]},"contextSupport":true,"dynamicRegistration":false,"editsNearCursor":true,"insertTextMode":1},"declaration":{"linkSupport":true},"definition":{"linkSupport":true},"documentHighlight":{"dynamicRegistration":false},"documentSymbol":{"dynamicRegistration":false,"hierarchicalDocumentSymbolSupport":true,"symbolKind":{"valueSet":[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26]}},"hover":{"contentFormat":["markdown","plaintext"],"dynamicRegistration":false},"implementation":{"linkSupport":true},"publishDiagnostics":{"relatedInformation":true,"tagSupport":{"valueSet":[1,2]}},"references":{"dynamicRegistration":false},"rename":{"dynamicRegistration":false,"prepareSupport":true},"semanticTokens":{"augmentsSyntaxTokens":true,"dynamicRegistration":false,"formats":["relative"],"multilineTokenSupport":false,"overlappingTokenSupport":true,"requests":{"full":{"delta":true},"range":false},"serverCancelSupport":false,"tokenModifiers":["declaration","definition","readonly","static","deprecated","abstract","async","modification","documentation","defaultLibrary"],"tokenTypes":["namespace","type","class","enum","interface","struct","typeParameter","parameter","variable","property","enumMember","event","function","method","macro","keyword","modifier","comment","string","number","regexp","operator","decorator"]},"signatureHelp":{"dynamicRegistration":false,"signatureInformation":{"activeParameterSupport":true,"documentationFormat":["markdown","plaintext"],"parameterInformation":{"labelOffsetSupport":true}}},"synchronization":{"didSave":true,"dynamicRegistration":false,"willSave":true,"willSaveWaitUntil":true},"typeDefinition":{"linkSupport":true}},"window":{"showDocument":{"support":true},"showMessage":{"messageActionItem":{"additionalPropertiesSupport":false}},"workDoneProgress":true},"workspace":{"applyEdit":true,"configuration":true,"didChangeWatchedFiles":{"dynamicRegistration":false,"relativePatternSupport":true},"semanticTokens":{"refreshSupport":true},"symbol":{"dynamicRegistration":false,"hierarchicalWorkspaceSymbolSupport":true,"symbolKind":{"valueSet":[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26]}},"workspaceEdit":{"resourceOperations":["rename","create","delete"]},"workspaceFolders":true}},"clientInfo":{"name":"Neovim","version":"0.9.5"},"initializationOptions":{},"processId":102865,"rootPath":"/home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight","rootUri":"file:///home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight","trace":"off","workspaceFolders":[{"name":"/home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight","uri":"file:///home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight"}]}}\n\nI[12:09:47.584] <-- initialize(1)\nI[12:09:47.585] --> reply:initialize(1) 0 ms\nV[12:09:47.585] >>> {"id":1,"jsonrpc":"2.0","result":{"capabilities":{"astProvider":true,"callHierarchyProvider":true,"clangdInlayHintsProvider":true,"codeActionProvider":{"codeActionKinds":["quickfix","refactor","info"]},"compilationDatabase":{"automaticReload":true},"completionProvider":{"resolveProvider":false,"triggerCharacters":[".","<",">",":","\\"","/","*"]},"declarationProvider":true,"definitionProvider":true,"documentFormattingProvider":true,"documentHighlightProvider":true,"documentLinkProvider":{"resolveProvider":false},"documentOnTypeFormattingProvider":{"firstTriggerCharacter":"\\n","moreTriggerCharacter":[]},"documentRangeFormattingProvider":true,"documentSymbolProvider":true,"executeCommandProvider":{"commands":["clangd.applyFix","clangd.applyTweak"]},"foldingRangeProvider":true,"hoverProvider":true,"implementationProvider":true,"inactiveRegionsProvider":true,"inlayHintProvider":true,"memoryUsageProvider":true,"referencesProvider":true,"renameProvider":{"prepareProvider":true},"selectionRangeProvider":true,"semanticTokensProvider":{"full":{"delta":true},"legend":{"tokenModifiers":["declaration","definition","deprecated","deduced","readonly","static","abstract","virtual","dependentName","defaultLibrary","usedAsMutableReference","usedAsMutablePointer","constructorOrDestructor","userDefined","functionScope","classScope","fileScope","globalScope"],"tokenTypes":["variable","variable","parameter","function","method","function","property","variable","class","interface","enum","enumMember","type","type","unknown","namespace","typeParameter","concept","type","macro","modifier","operator","bracket","label","comment"]},"range":false},"signatureHelpProvider":{"triggerCharacters":["(",")","{","}","<",">",","]},"standardTypeHierarchyProvider":true,"textDocumentSync":{"change":2,"openClose":true,"save":true},"typeDefinitionProvider":true,"typeHierarchyProvider":true,"workspaceSymbolProvider":true},"offsetEncoding":"utf-8","serverInfo":{"name":"clangd","version":"clangd version 17.0.6 linux x86_64-pc-linux-gnu"}}}\n\n'
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"V[12:09:47.699] <<< {\"jsonrpc\":\"2.0\",\"method\":\"initialized\",\"params\":{}}\n\nI[12:09:47.699] <-- initialized\nV[12:09:47.699] <<< {\"jsonrpc\":\"2.0\",\"method\":\"textDocument/didOpen\",\"params\":{\"textDocument\":{\"languageId\":\"cpp\",\"text\":\"/*\\n * SPDX-License-Identifier: GPL-3.0-or-later\\n *\\n * Copyright (C) 2023 Jason Carrete\\n *\\n * This file is part of Flight Controller.\\n *\\n * Flight Controller is free software: you can redistribute it and/or modify\\n * it under the terms of the GNU General Public License as published by\\n * the Free Software Foundation, either version 3 of the License, or\\n * (at your option) any later version.\\n *\\n * This program is distributed in the hope that it will be useful,\\n * but WITHOUT ANY WARRANTY; without even the implied warranty of\\n * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the\\n * GNU General Public License for more details.\\n *\\n * You should have received a copy of the GNU General Public License\\n * along with this program.  If not, see <https://www.gnu.org/licenses/>.\\n */\\n\\n#include \\\"appinfo.h\\\"\\n#include \\\"version.h\\\"\\n\\n#include <iostream>\\n\\nnamespace ffd = freeflight_daemon;\\n\\nint main(int argc, char* argv[])\\n{\\n    std::cout << ffd::get_app_name() << ' ' << freeflight::get_version() << ' '\\n              << freeflight::get_name() << '\\\\n';\\n    return 0;\\n}\\n\",\"uri\":\"file:///home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/flightd/main.cpp\",\"version\":0}}}\n\nI[12:09:47.699] <-- textDocument/didOpen\nV[12:09:47.699] System include extraction: driver clang expanded to /usr/bin/clang\nV[12:09:47.699] System include extraction: not allowed driver /usr/bin/clang\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	'V[12:09:47.700] <<< {"id":2,"jsonrpc":"2.0","method":"textDocument/semanticTokens/full","params":{"textDocument":{"uri":"file:///home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/flightd/main.cpp"}}}\n\n'
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"I[12:09:47.700] <-- textDocument/semanticTokens/full(2)\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"V[12:09:47.700] config note at /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/.clangd:1:0: Parsing config fragment\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"V[12:09:47.700] config note at /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/.clangd:1:0: Parsed 1 fragments from file\nV[12:09:47.700] Config fragment: compiling /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/.clangd:1 -> 0x0000724F50003730 (trusted=false)\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"I[12:09:47.701] --> textDocument/publishDiagnostics\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	'V[12:09:47.701] >>> {"jsonrpc":"2.0","method":"textDocument/publishDiagnostics","params":{"diagnostics":[],"uri":"file:///home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/.clangd"}}\n\n'
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"I[12:09:47.701] Loaded compilation database from /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/compile_commands.json\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"V[12:09:47.701] Broadcasting compilation database from /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"V[12:09:47.701] System include extraction: not allowed driver /home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/recipe-sysroot-native/usr/bin/aarch64-poky-linux/aarch64-poky-linux-g++\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"I[12:09:47.701] ASTWorker building file /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/flightd/main.cpp version 0 with command \n[/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/freeflight-1.0+git]\n/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/recipe-sysroot-native/usr/bin/aarch64-poky-linux/aarch64-poky-linux-g++ --target=aarch64-poky-linux --driver-mode=g++ --sysroot=/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/recipe-sysroot -I/home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/flightd -I/home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/freeflight/public -mcpu=cortex-a57 -march=armv8-a+crc -mbranch-protection=standard -fstack-protector-strong -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/recipe-sysroot -O2 -pipe -g -feliminate-unused-debug-types -fmacro-prefix-map=/home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight=/usr/src/debug/freeflight/1.0+git-r0 -fdebug-prefix-map=/home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight=/usr/src/debug/freeflight/1.0+git-r0 -fmacro-prefix-map=/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/freeflight-1.0+git=/usr/src/debug/freeflight/1.0+git-r0 -fdebug-prefix-map=/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/freeflight-1.0+git=/usr/src/debug/freeflight/1.0+git-r0 -fdebug-prefix-map=/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/recipe-sysroot= -fmacro-prefix-map=/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/recipe-sysroot= -fdebug-prefix-map=/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/recipe-sysroot-native= -fvisibility-inlines-hidden -O2 -g -DNDEBUG -std=gnu++20 -o src/flightd/CMakeFiles/flightd.dir/main.cpp.o -c -resource-dir=/usr/lib/clang/17 -- /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/flightd/main.cpp\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"I[12:09:47.702] Loaded compilation database from /home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/freeflight-1.0+git/compile_commands.json\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"I[12:09:47.702] --> window/workDoneProgress/create(0)\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	'V[12:09:47.702] >>> {"id":0,"jsonrpc":"2.0","method":"window/workDoneProgress/create","params":{"token":"backgroundIndexProgress"}}\n\n'
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"I[12:09:47.702] Enqueueing 1 commands for indexing\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"V[12:09:47.702] Driver produced command: cc1 -cc1 -triple aarch64-poky-linux -fsyntax-only -disable-free -clear-ast-before-backend -disable-llvm-verifier -discard-value-names -main-file-name main.cpp -mrelocation-model pic -pic-level 2 -pic-is-pie -mframe-pointer=non-leaf -fmath-errno -ffp-contract=on -fno-rounding-math -mconstructor-aliases -funwind-tables=2 -target-cpu cortex-a57 -target-feature +neon -target-feature +v8a -target-feature +crc -target-abi aapcs -msign-return-address=non-leaf -msign-return-address-key=a_key -mbranch-target-enforce -debug-info-kind=constructor -dwarf-version=5 -debugger-tuning=gdb -fcoverage-compilation-dir=/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/freeflight-1.0+git -resource-dir /usr/lib/clang/17 -I /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/flightd -I /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/freeflight/public -D _FORTIFY_SOURCE=2 -D NDEBUG -isysroot /home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/recipe-sysroot -internal-isystem /usr/lib/clang/17/include -internal-isystem /home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/recipe-sysroot/usr/local/include -internal-externc-isystem /home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/recipe-sysroot/include -internal-externc-isystem /home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/recipe-sysroot/usr/include -fmacro-prefix-map=/home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight=/usr/src/debug/freeflight/1.0+git-r0 -fmacro-prefix-map=/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/freeflight-1.0+git=/usr/src/debug/freeflight/1.0+git-r0 -fmacro-prefix-map=/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/recipe-sysroot= -O2 -Wformat -Wformat-security -Werror=format-security -std=gnu++20 -fdeprecated-macro -fdebug-compilation-dir=/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/freeflight-1.0+git -fdebug-prefix-map=/home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight=/usr/src/debug/freeflight/1.0+git-r0 -fdebug-prefix-map=/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/freeflight-1.0+git=/usr/src/debug/freeflight/1.0+git-r0 -fdebug-prefix-map=/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/recipe-sysroot= -fdebug-prefix-map=/home/jasonc/projects/quadcopter/albatros/build/tmp/work/cortexa57-poky-linux/freeflight/1.0+git/recipe-sysroot-native= -ferror-limit 19 -fvisibility-inlines-hidden -stack-protector 2 -fno-signed-char -fgnuc-version=4.2.1 -fno-implicit-modules -fcxx-exceptions -fexceptions -vectorize-loops -vectorize-slp -no-round-trip-args -target-feature -fmv -faddrsig -D__GCC_HAVE_DWARF2_CFI_ASM=1 -x c++ /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/flightd/main.cpp\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	'V[12:09:47.702] Building first preamble for /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/flightd/main.cpp version 0\nV[12:09:47.702] BackgroundIndex: building version 1 after loading index from disk\nV[12:09:47.702] <<< {"id":0,"jsonrpc":"2.0","result":null}\n\nI[12:09:47.702] <-- reply(0)\nI[12:09:47.702] --> $/progress\nV[12:09:47.702] >>> {"jsonrpc":"2.0","method":"$/progress","params":{"token":"backgroundIndexProgress","value":{"kind":"begin","percentage":0,"title":"indexing"}}}\n\n'
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	'V[12:09:47.702] BackgroundIndex: serving version 1 (50980 bytes)\nI[12:09:47.702] --> $/progress\nV[12:09:47.703] >>> {"jsonrpc":"2.0","method":"$/progress","params":{"token":"backgroundIndexProgress","value":{"kind":"report","message":"0/1","percentage":0}}}\n\nI[12:09:47.703] --> $/progress\n'
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	'V[12:09:47.703] >>> {"jsonrpc":"2.0","method":"$/progress","params":{"token":"backgroundIndexProgress","value":{"kind":"report","message":"0/1","percentage":0}}}\n\nI[12:09:47.703] --> $/progress\n'
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	'V[12:09:47.703] >>> {"jsonrpc":"2.0","method":"$/progress","params":{"token":"backgroundIndexProgress","value":{"kind":"end"}}}\n\n'
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"I[12:09:47.716] Built preamble of size 529320 for file /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/flightd/main.cpp version 0 in 0.01 seconds\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	'I[12:09:47.717] --> workspace/semanticTokens/refresh(1)\nV[12:09:47.717] >>> {"id":1,"jsonrpc":"2.0","method":"workspace/semanticTokens/refresh","params":null}\n\n'
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	'V[12:09:47.717] <<< {"jsonrpc":"2.0","method":"$/cancelRequest","params":{"id":2}}\n\nI[12:09:47.717] <-- $/cancelRequest\nV[12:09:47.717] indexed preamble AST for /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/flightd/main.cpp version 0:\n  symbol slab: 5 symbols, 5376 bytes\n  ref slab: 0 symbols, 0 refs, 128 bytes\n  relations slab: 0 relations, 24 bytes\nV[12:09:47.717] <<< {"id":3,"jsonrpc":"2.0","method":"textDocument/semanticTokens/full","params":{"textDocument":{"uri":"file:///home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/flightd/main.cpp"}}}\n\nI[12:09:47.717] <-- textDocument/semanticTokens/full(3)\n'
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	'V[12:09:47.717] <<< {"id":1,"jsonrpc":"2.0","result":null}\n\nI[12:09:47.717] <-- reply(1)\nV[12:09:47.717] Build dynamic index for header symbols with estimated memory usage of 22004 bytes\n'
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	'V[12:09:47.724] Trying to fix unresolved name "cout" in scopes: [std::]\n'
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"V[12:09:47.724] Dex query tree: false\nV[12:09:47.724] Dex query tree: false\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"E[12:09:47.725] IncludeCleaner: Failed to get an entry for resolved path : No such file or directory\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"V[12:09:47.726] indexed file AST for /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/flightd/main.cpp version 0:\n  symbol slab: 2 symbols, 4680 bytes\n  ref slab: 2 symbols, 2 refs, 4272 bytes\n  relations slab: 0 relations, 24 bytes\nV[12:09:47.726] Build dynamic index for main-file symbols with estimated memory usage of 12040 bytes\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"I[12:09:47.726] --> textDocument/publishDiagnostics\n"
[ERROR][2024-03-16 12:09:47] .../vim/lsp/rpc.lua:734	"rpc"	"/usr/bin/clangd"	"stderr"	"V[12:09:47.726] >>> {\"jsonrpc\":\"2.0\",\"method\":\"textDocument/publishDiagnostics\",\"params\":{\"diagnostics\":[{\"code\":\"pp_file_not_found\",\"message\":\"'iostream' file not found\",\"range\":{\"end\":{\"character\":19,\"line\":24},\"start\":{\"character\":9,\"line\":24}},\"relatedInformation\":[],\"severity\":1,\"source\":\"clang\"},{\"code\":\"undeclared_var_use\",\"message\":\"Use of undeclared identifier 'std'\",\"range\":{\"end\":{\"character\":7,\"line\":30},\"start\":{\"character\":4,\"line\":30}},\"relatedInformation\":[],\"severity\":1,\"source\":\"clang\"},{\"code\":\"misc-unused-alias-decls\",\"codeDescription\":{\"href\":\"https://clang.llvm.org/extra/clang-tidy/checks/misc/unused-alias-decls.html\"},\"message\":\"Namespace alias decl 'ffd' is unused (fix available)\",\"range\":{\"end\":{\"character\":0,\"line\":27},\"start\":{\"character\":0,\"line\":26}},\"relatedInformation\":[],\"severity\":2,\"source\":\"clang-tidy\",\"tags\":[1]}],\"uri\":\"file:///home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/flightd/main.cpp\",\"version\":0}}\n\nI[12:09:47.726] --> reply:textDocument/semanticTokens/full(2) 26 ms, error: Task was cancelled.\nV[12:09:47.726] >>> {\"error\":{\"code\":-32800,\"message\":\"Request cancelled\"},\"id\":2,\"jsonrpc\":\"2.0\"}\n\nV[12:09:47.726] ASTWorker running SemanticHighlights on version 0 of /home/jasonc/projects/quadcopter/albatros/build/workspace/sources/freeflight/src/flightd/main.cpp\nI[12:09:47.726] --> reply:textDocument/semanticTokens/full(3) 8 ms\nV[12:09:47.726] >>> {\"id\":3,\"jsonrpc\":\"2.0\",\"result\":{\"data\":[26,10,3,15,65537,0,6,17,15,131072,2,4,4,3,131075,0,9,4,2,16387,0,12,4,2,16387],\"resultId\":\"1\"}}\n\n"

System information
Output of clangd --version:
clangd version 17.0.6
Features: linux
Platform: x86_64-pc-linux-gnu
Editor/LSP plugin:
Neovim/nvim-lspconfig
Operating system:
Arch Linux
Kernel version: 6.7.9

Duplicate of #1605

repo: clangd/clangd


text:
Include completion fails at the end of file

clangd version:  clangd version 11.0.0 (https://github.com/llvm/llvm-project.git 3badd17b6989621b5aa2732800f697dabbda034d)
OS: Windows 10

I think this issue still exists. @HighCommander4

Originally posted by @lh123 in https://github.com/clangd/clangd/issues/38#issuecomment-643115928

You're right, I see the same issue (global completion instead of include completions).
I think what happened when I was testing #38, is that I typed in #include "llvm/Sup manually. When I type the " character, my editor auto-inserts a matching closing quote, so the actual test case I was testing was:
#include "llvm/Sup^"

(not the presence of the closing quote), which works fine.

I can't seem to reproduce this, neither on LLVM or a dummy project.
Could you please share clangd logs ?

It reproduces if the file has no code in and the include brackets are unbalanced and followed by eof

It reproduces if the file has no code in and the include brackets are unbalanced and followed by eof

Interesting I thought I had fixed this one... Well good thing is, this means at least I know the fix :D
Sent out https://reviews.llvm.org/D95419

Interesting I thought I had fixed this one... Well good thing is, this means at least I know the fix :D
Sent out https://reviews.llvm.org/D95419

Works like a charm now on my end, thanks.

Works like a charm now on my end, thanks.


text:
Clangd formatting issue?

Hi:
I notice that clang has formatting feature, but I don't know how to set it up. Is there any docs for this?
best regards
Peiyun Jin

clangd is using clang-format to do formatting, https://clangd.llvm.org/features.html#formatting , you can set .clang-format for style options.

Hi I have installed coc-clangd,  have .clang-format file in the project folder, and set
"coc.preferences.formatOnSaveFiletypes": ["cpp"],
"coc.preferences.formatOnSave": true,
But neither :Format nor format on save worked.
Could you tell me how can fix this?
Best

I think the problem is caused by this line  "clangd.arguments": ["-Wall", "-Werror", "-std=c++17"]  in above in my coc-settings.json. After adding this line into my coc-settings.json. The language server stops working for some reason.
{
    "coc.preferences.formatOnSaveFiletypes": ["cpp"],
    "coc.preferences.formatOnSave": true,
    "clangd.arguments": ["-Wall", "-Werror", "-std=c++17"],
    "languageserver": {
        "python": {
            "command": "python",
            "args": [
                "-mpyls",
                "-vv",
                "--log-file",
                "/tmp/lsp_python.log"
            ],
            "trace.server": "verbose",
            "filetypes": [
                "python"
            ],
            "settings": {
                "pyls": {
                    "enable": true,
                    "trace": {
                        "server": "verbose"
                    },
                    "commandPath": "",
                    "configurationSources": [
                        "pycodestyle"
                    ],
                    "plugins": {
                        "jedi_completion": {
                            "enabled": true
                        },
                        "jedi_hover": {
                            "enabled": true
                        },
                        "jedi_references": {
                            "enabled": true
                        },
                        "jedi_signature_help": {
                            "enabled": true
                        },
                        "jedi_symbols": {
                            "enabled": true,
                            "all_scopes": true
                        },
                        "mccabe": {
                            "enabled": true,
                            "threshold": 15
                        },
                        "preload": {
                            "enabled": true
                        },
                        "pycodestyle": {
                            "enabled": true
                        },
                        "pydocstyle": {
                            "enabled": false,
                            "match": "(?!test_).*\\.py",
                            "matchDir": "[^\\.].*"
                        },
                        "pyflakes": {
                            "enabled": true
                        },
                        "rope_completion": {
                            "enabled": true
                        },
                        "yapf": {
                            "enabled": true
                        }
                    }
                }
            }
        }
    }
}```

Look like it's caused by server, @sam-mccall can you look into this?

I think the problem is caused by this line "clangd.arguments": ["-Wall", "-Werror", "-std=c++17"] in above in my coc-settings.json. After adding this line into my coc-settings.json. The language server stops working for some reason.

The reason is clangd.arguments is extra flags to pass to clangd, and those are not valid clangd arguments:
$ clangd -Wall -Werror -std=c++17
clangd: Unknown command line argument '-Wall'.  Try: 'clangd --help'
clangd: Did you mean '--help'?
clangd: Unknown command line argument '-Werror'.  Try: 'clangd --help'
clangd: Did you mean '--color'?
clangd: Unknown command line argument '-std=c++17'.  Try: 'clangd --help'
clangd: Did you mean '--log=c++17'?

If you want to set the flags for parsing your code, this is configured using compile_commands.json or compile_flags.txt: https://clangd.llvm.org/installation.html#project-setup

@sam-mccall Hi Sam, Is there a way to enable clang-tidy and -j inside coc-settings.json? Or how can I enable them with vim?
best regards

Sure: "clangd.arguments": ["-j=3", "-clang-tidy-checks=bugprone-*"] - those really are clangd flags.
Similar to clang-format, for finer-grained clang-tidy config you should use the standard .clang-tidy config file in your source tree, clangd should respect it.

@sam-mccall Do I need to enable clang-tide first, "clangd.arguments": ["-j=3", "-clang-tide=true","-clang-tidy-checks=bugprone-*"]?

What's clangd --version?
It's on by default as of clangd 9.
It may barely work in clangd 8, it was experiencing and off by default.

I'm using fedora 32 beta. Clangd is version 10.

With clangd 10 you shouldn't have to explicitly enable clang tidy.
On Sat, Mar 28, 2020, 7:30 PM Stokhos notifications@github.com wrote:

I'm using fedora 32 beta. Clangd is version 10.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/clangd/coc-clangd/issues/25#issuecomment-605500662,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEGBAMIBI3LZ3LECRB7SNTRJY65TANCNFSM4LRQVAMQ
.

Sorry to add to this but it seems related. I am very confused about what this plugin can do. Should I be able to do formatting? Issuing a coc :Format command doesn't do anything for me. Would then clang-format be used or clang-tidy with the --fix option (or both)?

authors: chmanie fannheyward sam-mccall stokhos

repo: clangd/coc-clangd


text:
Ogg Opus Files Dont Show

On macOS Mojave, installed via homebrew. MP3 files show fine, but the majority of my library which is in ogg opus just doesnt show in the library viewer.

Oh, I see, tag parsing failed? That's possible, I don't have tons of Opus files. Is there any way you can share a file with tags that don't seem to be working?

sure, try this one
01 Tree Village.ogg.zip

Ah! So... taglib (our tag parsing library) sees the .ogg extension and assumes it's a vorbis file, then fails when it's not. When this happens, we should probably detect the error and then check to see if it's an opus file.
Are there any other file formats that commonly have an .ogg extension that may not be vorbis? :thinking:

Got it. I modified the taglib parser reader plugin so it can detect opus files in an ogg container -- your example file seems to parse fine now! I also made it such that as soon as I can get examples of other formats in ogg containers it should be trivial to add support to them as well.

seems to be fixed after re-adding the library on latest head, thanks!

Thanks for confirming the fix!

authors: clangen ibrokemypie

repo: clangen/musikcube


text:
Browser starts to lag after playing 3-5 videos when using  player.configure to update the source url

Browser:
Firefox 88.0.1
OS:
Pop OS  20.04 LTS
Clappr Version:
latest from http://cdn.clappr.io/latest/clappr.min.js
Steps to reproduce:
play 3-5 video one after another.

I was expecting to have a smooth playback but instead it started lagging(my browser)

Did you try to reproduce this issue at http://cdn.clappr.io/
No
I'm trying to update the video source using the following code:
// [...]
player.configure({
  source: 'another-url',
  // ...
});

which updates the video but after playing around 3-5 videos one after another the browser starts to lag.
I also tried to reproduce this issue on multiple devices, the same issue occurred.
NOTE : source URL is an HLS video encrypted with AES-128

Did you try to reproduce this issue at http://cdn.clappr.io/
No

Can't you reproduce the reported behavior or just haven't tried?

I also tried to reproduce this issue on multiple devices, the same issue occurred.

Yes I have but not on http://cdn.clappr.io/

Yes, I understand that you have tested it on other devices. The recommendation to test on http://cdn.clappr.io/ (specifically on http://cdn.clappr.io/demo) is that it becomes a common point that we can also validate on our side.
I was unable to reproduce this issue. Can you generate any evidence of this? (CPU / Memory consumption of the tab that is running Clappr, some video showing the problem visually)

Hi @unique1o1, is the problem still happening? Can you generate any evidence of this? (CPU / Memory consumption of the tab that is running Clappr, some video showing the problem visually)

I'm closing this issue due to inactivity. If needed, please feel free to reopen it.

authors: joaopaulovieira leticiafernandes pedrochamberlain unique1o1

repo: clappr/clappr


text:
no video on galaxy s5

There is no video on Galaxy s5 when a live video or a replay is playing. But the video is diaplayed after you click the progress bar.

only the audio.

are you still facing this issue @polaris-zx ? also, did you test with different stream sources? is it only with hls ?

authors: leandromoreira polaris-zx


text:
Reintroduce differentiation between application environments

Instead of only relying on one environment, this commit changes run
wrapper and the docker-compose stack to differentiate between
development/production and being able to run them both in parallel.
In other words: Reintroduce the significance of $APPLICATION_ENV

This commit fixes:

#36 - Jenkins image build takes twice the build time
#33 - Reintroduce distinction between development and production environment
#32 - Documentation is gone
#31 - Jenkins jobs constantly throwing errors

repo: claranet/spryker-demoshop


text:
jpb/220-enable-some-pylint-error-checking-in-ci

Adding pylint error checking into the ci part of the precommits. The .pre-commit-config.yaml now has two entries for pylint: one which runs errors only which is compatible with ci, and one that runs as 'repo: local' and uses the .pylintrc which will pick on all the usual style warnings etc, but which is skipped over by the ci.
I have also run pylint with the errors-only flag over the full repo and fixed all issues that were picked up - or added pylint ignore against the ones that appeared to be false-positives.
Ruff: I have also added 'ruff' to the precommit hooks. 'ruff' is a rust-based linter that is super fast (but doesn't yet have quite as many rules as pylint). I fixed a number of issues that the ruff checked picked up on. Ruff might eventually be able to replace pylint but for now we can just keep it in as an extra linter because it takes very little time to run.

@groadabike  - there is nothing significant in this PR - mostly just fixing line-too-long type errors and issues that pylint considers 'errors' i.e Exxx codes. Could you please give it a quick review (I don't want to get in the habit of overriding the need for reviews :-).  Once this is integrated pylint will pass with the '-E'  i.e. errors only flag which can then be included safely in the precommit ci path.

Going to merge this PR if

repo: claritychallenge/clarity


text:
Understanding IQ data generated by Raw data package with Clarius L7HD052110A0780

Hi, clarius dev team,
Based on the indications of your support team, I forward you this issue from my support request to Clarius.
I am currently acquiring IQ data with the Raw data package of Clarius L7HD052110A0780.
From here, I am trying to go back in synthesizing RF data, basically modulating performing modulation to RF frequencies.
Since it is not clear to me how IQ is calculated in the first place, I am having difficulties to synthesize RF.
Could you let me know about the algorithmic steps, which are followed, to go from RF to IQ?
My main question is how to choose the right carrier frequency "fc". Is this equivalent to the transmit frequency in the .yml file?
I attach my current script in Python, in case this can be valuable for this github project:
                      `  ## from here we resynthesize rf data
                        UPSAMPLING = 4
                        fs_rf = fs*UPSAMPLING
                        #interpolation
                        rf_line_int = np.zeros(len(iq_line)*UPSAMPLING, dtype=complex)
                        rf_line_int[0::UPSAMPLING] = UPSAMPLING*iq_line[:]
                        tcoords_rf = (np.arange(rf_line_int.shape[0]) + toff*UPSAMPLING)/fs_rf
                        SHIFT_FREQ = 3E6 # To filter data without distortion
                        rf_line_int_ = rf_line_int * np.exp(2*np.pi*SHIFT_FREQ*1j*tcoords_rf)

                        #filtering
                        b, a = butter(8, 1/UPSAMPLING)  #filter interpolation replica
                        rf_line_filt = filtfilt(b, a, rf_line_int_)
                        #carrier modulation

                        rf_line_analytic = rf_line_filt * np.exp(2*np.pi*(-SHIFT_FREQ + fs/2+ fc)*1j*tcoords_rf)
                        rf_line = np.real(rf_line_analytic)

                        rf_line_fft = fft(rf_line)
                        rf_line_freq = fftfreq(len(rf_line), 1/fs_rf)`

Attached also  an example of the spectrum of my current IQ lines and the corresponding RF synthesized with the code above.
The bandwidth of the probe after modulation (4-13 MHz) is apparently correct.

Thank you and best wishes,
Sergio Sanabria

a few tips:

you'll want to look at the sampling rate in the yaml file to determine any downsampling from 60MHz
demodulation is a sliding frequency as a function of depth, see shallowfreq, deepfreq, and filterdepth, these are the parameters used applied linearly

Hi, @clariusk, thanks for the quick answer.
I have looked into the demodulation parameters you mention.
It seems deepfreq is always 7.5 MHz, and shallowfreq: 11 MHz, with a single filterdepth of 59.6999 mm
My understanding is that at 0 mm the depth carrier is 11 MHz, linearly decreasing down to 7.5 MHz at 59.6999 mm
and staying constant at 7.5 MHz for larger depths. Is this correct? .yml extract below.
Sergio
receive:
  - {shallowfreq: 11 MHz, deepfreq: 7.5 MHz, filterdepth: 59.699999999999996 mm}
  - {shallowfreq: 11 MHz, deepfreq: 7.5 MHz, filterdepth: 59.699999999999996 mm}
  - {shallowfreq: 11 MHz, deepfreq: 7.5 MHz, filterdepth: 59.699999999999996 mm}
  - {shallowfreq: 11 MHz, deepfreq: 7.5 MHz, filterdepth: 59.699999999999996 mm}
  - {shallowfreq: 11 MHz, deepfreq: 7.5 MHz, filterdepth: 59.699999999999996 mm}
  - {shallowfreq: 11 MHz, deepfreq: 7.5 MHz, filterdepth: 59.699999999999996 mm}
  - {shallowfreq: 11 MHz, deepfreq: 7.5 MHz, filterdepth: 59.699999999999996 mm}
  - {shallowfreq: 11 MHz, deepfreq: 7.5 MHz, filterdepth: 59.699999999999996 mm}

yes, that's exactly correct

authors: clariusk sergiojsanabria

repo: clariusdev/raw


text:
Add CNCF Conformance 1.26 1.27 1.28

close #356

@prometherion should we merge before related PRs are merged in k8s-conformance? All required tests have passed!

repo: clastix/kamaji


text:
Improve auto-scrolling for small containers / large drag sources

Currently if you have a small scroll container and a large drag source, it's nearly impossible to get fine controlled auto-scrolling working properly given the existing auto-scrolling logic.
The getScrollDirectionAndSpeed will need to be updated to take into account the relative size of the item being dragged compared to the scroll container's actual size

Hey, first of all, thank you for your job!
This issue is related to this behaviour, right? Is there any way to improve this?

Hey, first of all, thank you for your job!
This issue is related to this behaviour, right? Is there any way to improve this?

@horprogs that's one of the manifestations of the issue, indeed.
On how this could be improved: Generally I think it's a bit tricky to find a one-size-fits-all strategy for auto-scrolling. I think in the future this should be a bit more extensible, and have either a pointer coordinates based strategy or a strategy that is based on the bounding rect of the dragged element

@clauderic Looking the grid example, I wonder if the auto-scrolling is too aggressive. Right now it seems that the page auto-scrolls when the element is brought down past the halfway point of the page. A simple solution might be to only scroll if the element that is being dragged is nearing the edge of the viewport. Any thoughts?

Having similar issues but with on drag instantly scrolling to the top in a scrollable container.
Any workarounds?

I don't know if this is related to this issue but when you try to scroll with dragged element without DragOverlay element position won't be updated for the scroll duration. You can see it here: https://5fc05e08a4a65d0021ae0bf2-vfebfgjygq.chromatic.com/?path=/docs/presets-sortable-grid--without-drag-overlay
Drag element and try to scroll the page with it. Result: mouse position and element position are different

I'm running into this issue as well - has anyone found an interim workaround?

I'm working on a fix to these issues here: #140

I am using dnd-Kit and sortable, context with an array. In my case auto scrolling is not working in a list while item being dragged.

authors: AlfainCoder Simba14 Sorgrum clauderic horprogs ohayojp willadamskeane

repo: clauderic/dnd-kit


text:
Unexpected token when import css

I followed the guideline from the readme page and added the following line in my js file (It's a react component)
import "react-infinite-calendar/styles.css";
But I encounter this error when running gulp:
events.js:160
throw er; // Unhandled 'error' event
^
SyntaxError: Unexpected token
Does anyone know to fix it? Because I'm quite new to React

You need to use the appropriate loader.
Assuming you're using webpack, check out https://github.com/webpack-contrib/css-loader

repo: clauderic/react-infinite-calendar


text:
Masteries and Runes possible bug

I seem to have a problem retrieving the masteries and runes after the last update.
I tried all the "LolApi.Summoner..." functions and for some reason getMasteries() and getRunes() does not work for me. They return undefined as result and null as error.
Im using the 'eune' server.

I'll check it out!

fixed it in the latest version :)

Appreciate it! Thank you

authors: claudiowilson dukevomv

repo: claudiowilson/LeagueJS


text:
Optimized ssr

Reduces file size of SSR build file. Fixes bug where sometimes hot reload server would be blank. Improves speed. Combines both package.json files. Fixes lazy loading of navigation without throwing hydration errors. Now not all modules will be loaded at once.
What kind of change does this PR introduce? (check at least one)

[x] Bugfix
[x] Feature
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[x] Yes
[ ] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[x] It's submitted to the dev branch and not the master branch
[ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
[ ] It's been tested with all Quasar themes
[ ] It's been tested on a Cordova (iOS, Android) app
[ ] It's been tested on a Electron app
[ ] Any necessary documentation has been added or updated in the docs (for faster update click on "Suggest an edit on GitHub" at bottom of page) or explained in the PR's description.

If adding a new feature, the PR's description includes:

[x] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

This branch has the same issue as my latest pull request from hot-reload-ssr. The issue of mocking the window object and vue router history mode. Please see the other pull request for details.

repo: claustres/quasar-templates


text:
🛑 livevault is down

In 934816d, livevault (https://livevault.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: livevault is back up in 0eb1320.

repo: claytonplong/backup-uptime


text:
🛑 livevault is down

In b3fb421, livevault (https://livevault.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: livevault is back up in c724e4d.


text:
🛑 livevault is down

In d5e28c4, livevault (https://livevault.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: livevault is back up in 84f7cd3.


text:
🛑 livevault is down

In 651792d, livevault (https://livevault.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: livevault is back up in dc0ba81.


text:
change abort() to AuthError

Use AuthError instead of abort() for Invalid API keys to reduce the alert noise from wrong keys

Can you fix CI and format before merging

repo: cleanlab/cleanlab-studio


text:
proxy: Restrict the socket and parent directory modes

We don't need those sockets to be read/writable to the whole world. Only
root is enough.
Signed-off-by: Damien Lespiau damien.lespiau@intel.com

Coverage remained the same at 69.828% when pulling 8c67a3135a1b42d0241a681c6c9fd88a70d7e214 on dlespiau:20170411-socket-perms into 653860d1e034d12963f2abf06e1f3289f7ed1348 on clearcontainers:master.

lgtm

authors: coveralls dlespiau jodh-intel

repo: clearcontainers/proxy


text:
oop 0.0.3

Type: Missing
Summary:
oop 0.0.3
Details:
NPM license field indicates NONE
No project link
Way Back Machine had no record
Resolution:
NONE
Affected definitions:

oop 0.0.3

@capfei - I think this might be the repo/license - https://github.com/felixge/node-oop/blob/master/LICENSE.  Thoughts on updating this from NONE to MIT?

@ariel11 Did you find that link somewhere in the package? I didn't see it.

@capfei - I dont see the repo link in the package specifically, however both are by "felixge" and there's this issue where someone asked about a license and "felixge" confirmed MIT. I think we can take that as evidence this package is MIT.  Thoughts?

authors: LandOfBliss ariel11 capfei

repo: clearlydefined/curated-data


text:
Changing User-Agent

At first: Really nice project!
I have tried to change the User-Agent via:

Map<String, String> params = new HashMap<>();
		params.put("User-Agent", "Mozilla/5.0 (Windows NT 6.0; rv:2.0.1) Gecko/20100101 Firefox/4.0.1");
System.out.println(net.dongliu.requests.Requests.get("http://localhost:2343/init.aspx").headers(params).send().readToText());

But it doesn't seem to work: The User-Agent is Requests/4.0, Java 1.8.0
So is it possible to change the agent?

This code do change user-agent for me. Which version you are using?
Or you can try
Requests.get(url).userAgent("Mozilla/5.0 (Windows NT 6.0; rv:2.0.1) Gecko/20100101 Firefox/4.0.1")

Thanks for replying!
I am using the latest version from the central maven repo. --> 4.7.1
I have tried your solution, but it doesn't seem to work! ( I have used www.whoishostingthis.com for getting the user-agent)
System.out.println(net.dongliu.requests.Requests.get("http://www.whoishostingthis.com/tools/user-agent").userAgent("Mozilla/5.0 (Windows NT 6.0; rv:2.0.1) Gecko/20100101 Firefox/4.0.1").send().readToText());
Does this work for you ?

The site redirect http://www.whoishostingthis.com/tools/user-agent to http://www.whoishostingthis.com/tools/user-agent/, seems Requests does not use the specified user-agent when send the redirected http request. I will fix this later.
For now, using Requests.get("http://www.whoishostingthis.com/tools/user-agent/") you can get the expected result.

Hey thanks, I will test it when the maven repo is up-to-date!

Now you can try version 4.7.2, set user agent by .userAgent("Mozilla/5.0 (Windows NT 6.0; rv:2.0.1) Gecko/20100101 Firefox/4.0.1")

repo: clearthesky/requests


text:
fix(clerk-js): Use a fixed border radius value for OrganizationAvatar

Description
OrganizationAvatar should maintain the border-radius, even if the user passes a value in borderRadius variable.

Checklist

[ ] npm test runs as expected.
[ ] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

!preview

@desiprisg yes, i'm sure!

repo: clerk/javascript


text:
Fix string_keys to work when it's the only option specified

If string_keys was set without any other options, it wouldn't work since "name" variable is initially a symbol.
Fix #24.

Thank you

authors: fernandomm stepozer

repo: cloocher/xmlhasher


text:
Use parseMarkdownFile instead of parseMarkdownString

Fixes #276

Can you resolve the conflicts?

Can you resolve the conflicts?

Done! I hadn't branched from the latest main, sorry :grimacing:

Thanks!

repo: cloud-annotations/docusaurus-openapi


text:
conversion failed

After training is finished. I got conversion failed.

I got the same problem,

I still got this error, after upgrading to the latest version.

repo: cloud-annotations/training


text:
Return info of the KeyPair Create/List/Get API are not clear

Issue: KeyPair Create/List/Get API 호출시 반환 정보가 일괄성이 없음

ex) driver별로 public key를 제공하거나 제공하지 않거나

cf) KeyPairInfo Spec
type KeyPairInfo struct {
        IId   IID       // {NameId, SystemId}
        Fingerprint string
        PublicKey   string
        PrivateKey  string
        VMUserID      string

        KeyValueList []KeyValue
}

cf) Example of the KeyPair List/Get return info(AWS drvier)
{
   "keypair" : [
      {
         "IId" : {
            "NameId" : "keypair-01",
            "SystemId" : "keypair-0-c7nqod2ba5o2et11hlm0"
         },
         "Fingerprint" : "3f:79:34:28:87:09:44:ee:b0:41:e4:e4:6d:e7:5f:62:b9:d5:87:67",
         "PublicKey" : "",
         "PrivateKey" : "",
         "VMUserID" : "",

         "KeyValueList" : []
      }
   ]
}

[Driver 별 List API 제공 졍보 현황]

empty: 시험을 안해본 드라이버

|   | IId | PublicKey | PriavateKey | Fingerprint | VMUserID | KeyValueList
-- | -- | -- | -- | -- | -- | -- | --
1 | AWS | O | X | X | O | X | X
2 | Azure | O | O | X | X | X | X
3 | GCP | O | O | O | X | X | X
4 | Alibaba | O | X | X | O | X | CreationTime
5 | Tencent | O | X | X | X | X | KeyId
6 | IBM |   |   |   |   |   |
7 | OpenStack | O | O | X | O | X | X
8 | Cloudit | O | O | O | X | X | X
9 | NCP |   |   |   |   |   |
10 | KT |   |   |   |   |   |
11 | NHN |   |   |   |   |   |

[현황 및 계획]

현황: 초기 API 설계와 달리, 현재까지 실제 사용되는 정보는 key 생성 시점에 private key 외에는 없어 보임
질문: Fingerprint는 언제 사용되는가?
계획: 최소 정보 제공으로 적용 후 일정 기간 운영, 그 후 KeyPairInfo struct 변경을 고려
계획: 일부 driver에서는 private key 등을 자체 활용하므로 Spider 서버 단에서 API별 제공 정보 일관성을 일괄 반영

[API별 제공 정보 제안]

Create API 반환시 제공 정보 제안

Iid
PublicKey
PriavateKey
Fingerprint
VMUserID
KeyValueList

O
X
O
X
cb-user
자율

List/Get API 반환시 제공 정보 제안

Iid
PublicKey
PriavateKey
Fingerprint
VMUserID
KeyValueList

O
X
X
X
cb-user
자율

현재 KeyPairInfo struct 구조는 한동안 현행 유지

@hyokyungk @inno-cloudbarista  @dev4unet @innodreamer @seokho-son @jihoon-seo @sykim-etri
위 이슈의 [현황 및 계획], [API별 제공 정보 제안]
부분을 검토하시어 추가 고려 사항이나 의견 있으시면 의견 달아 주시면 감사하겠습니다. ( ~ 1/28.금 정도까지)

Fingerprint는 어디다 쓰는지? 사용될 여지가 있는지?
FW별로 저 정도의 최소 정보 제공이면 족한 것인지?
등등

[Fingerprint]

https://docs.bmc.com/docs/display/itda27/About+the+SSH+host+key+fingerprint
https://superuser.com/questions/421997/what-is-a-ssh-key-fingerprint-and-how-is-it-generated
https://superuser.com/questions/1377132/get-the-fingerprint-of-an-existing-ssh-public-key
https://arsviator.blogspot.com/2015/04/ssh-ssh-key.html
https://blueyikim.tistory.com/1792

The fingerprint is based on the host's public key, usually based on the /etc/ssh/ssh_host_rsa_key.pub file.  Generally it's for easy identification/verification of the host you are connecting to.
If the fingerprint changes, the machine you are connecting to has changed their public key. This may not be a bad thing (happens from re-installing ssh), but it could also indicate that you are connecting to a different machine at the same domain/IP (happens when you are connecting through something like a load balancer) or that you are being targeted with a man-in-the-middle attack, where the attacker is somehow intercepting/rerouting your ssh connection to connect to a different host which could be snooping your username/password.
Bottom line: if you get warned of a changed fingerprint, be cautious and double check that you're actually connecting to the correct host over a secure connection. Though most of the time this is harmless, it can be an indication of a potential issue.

CB 개발/시험용으로 쓸 때에는 Fingerprint는 신경쓰지 않을 수도 있겠습니다.
prod 도 고려한다면, 추후 Rogue VM 등에 대한 대비책이 필요할 수도 있으므로,
Fingerprint를 일단 저장이라도 해 놓는 편이 좋을 것 같습니다.

말씀해주신 API별 제공 정보 제안에서
Azure, Ibm-vpc, openstack는 CSP에서 SSH키 기능을 제공하기에 적용가능한 사항입니다.
Cloudit은 저번 이슈사항(#548)을 해결한 후에 적용가능합니다.

@inno-cloudbarista

넵, 알겠습니다.

AWS / Alibaba에서 핑거프린트는 콘솔에서 키페어 목록 노출용으로 사용되고 있으며
자체 키 관리 등을 할 경우 ID나 키 검증 등에 활용될 수는 있지만 현재 cb-spider에서 사용되는 곳은 없습니다.
PublicKey / PriavateKey의 경우 CSP의 조회 API에서는 리턴되는 정보가 없으며
기존에 VM생성 시 cb-user 생성을 위해 PublicKey가 사용되었지만 공개키를 이용하지 않는 방식으로 변경되어서
현재는 자체 키를 관리하는 GCP의 경우에만 VM 생성 시 PublicKey를 사용하고 있습니다.

@dev4unet

넵, 감사합니다.
반영하여 정리해보도록 하겠습니다.

authors: dev4unet inno-cloudbarista jihoon-seo powerkimhub

repo: cloud-barista/cb-spider


text:
Adding BOM Catalog

BOM Categories

Create New Cluster
Use Existing Cluster

Bom Catalog UI
Implemented MVP1

Displays the contents category wise
With in the categories, grouping is done according to the cloud provider.

/lgtm

authors: csantanapr phemankita

repo: cloud-native-toolkit/automation-modules


text:
Readme variable prometheus_binaries_local_dir

What did you do?
I run command playbook with this role  with variable "prometheus_binaries_local_dir" but it seems playbook could not complete. This need to be done since my environment is located on air gapped network.
Did you expect to see some different?
I expect the playbook complete to install prometheus to the remote host
Environment

Role version:
Insert release version/galaxy tag or Git SHA here

Ansible version information:
ansible 2.9.2 config file = /etc/ansible/ansible.cfg configured module search path = [u'/home/deploy/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules'] ansible python module location = /usr/lib/python2.7/site-packages/ansible executable location = /usr/bin/ansible python version = 2.7.5 (default, Aug  2 2016, 04:20:16) [GCC 4.8.5 20150623 (Red Hat 4.8.5-4)]

Variables:

---
- name : Deploy prometheus
  hosts: ams
  roles:
  - cloudalchemy.prometheus
  vars:
    prometheus_version: 2.17.0
    prometheus_binary_local_dir: /data/monitoring/prometheus/
    prometheus_db_dir: /apps/prometheus/database
    prometheus_targets:
      node:
      - targets:
        - localhost:9100
        labels:
          env: ams

Ansible playbook execution Logs:

PLAY [Deploy prometheus] **********************************************************************************

TASK [Gathering Facts] ************************************************************************************
ok: [camelia-ams]

TASK [cloudalchemy.prometheus : Gather variables for each operating system] *******************************
ok: [camelia-ams] => (item=/etc/ansible/roles/cloudalchemy.prometheus/vars/redhat.yml)

TASK [cloudalchemy.prometheus : Assert usage of systemd as an init system] ********************************
ok: [camelia-ams] => {
    "changed": false,
    "msg": "All assertions passed"
}

TASK [cloudalchemy.prometheus : Get systemd version] ******************************************************
ok: [camelia-ams]

TASK [cloudalchemy.prometheus : Set systemd version fact] *************************************************
ok: [camelia-ams]

TASK [cloudalchemy.prometheus : Assert no duplicate config flags] *****************************************
ok: [camelia-ams] => {
    "changed": false,
    "msg": "All assertions passed"
}

TASK [cloudalchemy.prometheus : Assert external_labels aren't configured twice] ***************************
ok: [camelia-ams] => {
    "changed": false,
    "msg": "All assertions passed"
}

TASK [cloudalchemy.prometheus : Set prometheus external metrics path] *************************************
ok: [camelia-ams]

TASK [cloudalchemy.prometheus : Fail when prometheus_config_flags_extra duplicates parameters set by other variables] ***
skipping: [camelia-ams] => (item=storage.tsdb.retention)
skipping: [camelia-ams] => (item=storage.tsdb.path)
skipping: [camelia-ams] => (item=storage.local.retention)
skipping: [camelia-ams] => (item=storage.local.path)
skipping: [camelia-ams] => (item=config.file)
skipping: [camelia-ams] => (item=web.listen-address)
skipping: [camelia-ams] => (item=web.external-url)

TASK [cloudalchemy.prometheus : Get all file_sd files from scrape_configs] ********************************
ok: [camelia-ams]

TASK [cloudalchemy.prometheus : Fail when file_sd targets are not defined in scrape_configs] **************
skipping: [camelia-ams] => (item={'value': [{u'labels': {u'env': u'ams'}, u'targets': [u'localhost:9100']}], 'key': u'node'})

TASK [cloudalchemy.prometheus : Alert when prometheus_alertmanager_config is empty, but prometheus_alert_rules is specified] ***
ok: [camelia-ams] => {
    "msg": "No alertmanager configuration was specified. If you want your alerts to be sent make sure to specify a prometheus_alertmanager_config in defaults/main.yml.\n"
}

TASK [cloudalchemy.prometheus : Get latest release] *******************************************************
skipping: [camelia-ams]

TASK [cloudalchemy.prometheus : Set prometheus version to {{ _latest_release.json.tag_name[1:] }}] ********
skipping: [camelia-ams]

TASK [cloudalchemy.prometheus : Get checksum list] ********************************************************
fatal: [camelia-ams]: FAILED! => {"msg": "An unhandled exception occurred while running the lookup plugin 'url'. Error was a <class 'ansible.errors.AnsibleError'>, original message: Failed lookup url for https://github.com/prometheus/prometheus/releases/download/v2.17.0/sha256sums.txt : <urlopen error timed out>"}

NO MORE HOSTS LEFT ****************************************************************************************

Anything else we need to know?:
I realized that in Readme File, you put the variable as "prometheus_binaries_local_dir" while in defaults/main.yml, the correct value is prometheus_binary_local_dir. Once I update my playbook file variable accordingly, it successfully complete. Does the Readme need update?

Yes, readme needs an update, the correct variable name is in defaults/main.yml

Fixed with #280

authors: asatblurbs paulfantom

repo: cloudalchemy/ansible-prometheus


text:
Uniform log sources

WHAT is this pull request doing?
Create all Log instances from LavinMQ::Log. This will make all log sources prefixed with "lmq" which in turn makes it easy to see if a log comes from a lib (e.g. amqp-client) or from lavinmq itself.
HOW can this pull request be tested?
Run lavin with --debug and look at log output.

Should probably require "./lavinmq/logger" in each file that needs it, rather on a top level. If we want to compile any part independently. Pretty sure vim will complain otherwise, as it won't be able to compile it to check formatting, linting etc.

authors: carlhoerberg spuun

repo: cloudamqp/lavinmq


text:
Add ability to have multiple PeriodicReplicationServices

This PR fixes the following issues:

The abstract class PeriodicReplicationService currently stores information in SharedPreferences under fixed key names. This means that if an app implements multiple concrete PeriodicReplicationServices they will interfere with each other. To fix this, we now store the values in SharedPreferences using keys prefixed with the name of the concrete class implementing the PeriodicReplicationService.
After a reboot, the elapsed time since boot at which the next should occur isn't always updated to reflect the fact the device rebooted. This could lead to replications not being invoked at the expected times.
Rather than storing the time at which the next replication should be triggered, we now store the time at which the last replication occurred. This feels more logical and means we don't have to recalculate the value stored in SharedPreferences after bind/unbind and the only time the value will need adjusting is after a reboot.

Testing
The existing tests have been updated in accordance with these changes. They now verify that the keys used in SharedPreferences are prefixed with the name of the concrete implementation of PeriodicReplicationService and verify that the elapsed time since boot is always updated after the service has been notified of a reboot.

@tomblench I've tried to address your comments in 8bfe34e. Hopefully it makes the tests more easily readable.

repo: cloudant/sync-android


text:
🛑 idwebhost.com is down

In f150083, idwebhost.com (https://idwebhost.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: idwebhost.com is back up in 2827b7a after 8 minutes.

repo: cloudbip/upptime


text:
🛑 ach.id is down

In f512354, ach.id (https://ach.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ach.id is back up in 29f009d.


text:
🛑 my.dewabiz.com is down

In b177400, my.dewabiz.com (https://my.dewabiz.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: my.dewabiz.com is back up in 7bde932.


text:
🛑 cbn.id is down

In 8d5874a, cbn.id (https://cbn.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cbn.id is back up in 9e402e6.


text:
🛑 hsp.net.id is down

In c1b8df9, hsp.net.id (https://hsp.net.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: hsp.net.id is back up in 1e3bfaa.


text:
Laravel 5.7 support - fresh app install

Hello
When installing on a fresh Laravel 5.7 app instance, I had to change the following in the RouteServiceProvider:

Otherwise I got 404 errors.
Best regards,
Ciaro

Thank you for your reply! I must have overlooked that section.

repo: cloudcreativity/laravel-json-api


text:
Corrected an error spelling

Corrected an error spelling in doc

Nice!
Would you mind rebasing the PR so that we only have the change in 'docs/manual.txt' showing up?

repo: cloudera/hue


text:
Can't Detect Wordpress

My station's site is built on wordpress, the cloudflare plugin is enabled, I've connected it to the API key. This morning I decided to go ahead and upgrade to $20 / month as we're getting a tone of traffic and the site is getting incredibly slow in the mornings. When I go to enable APO - it tells me that it's not a Wordpress website...

Hi @trevordbc  please try following the steps: "What if my Cloudflare dashboard says it can't detect the WordPress plugin?".
If it won't help please raise the support ticket and post the number here (I will have a look).

please install the latest version of the plugin and navigate to APO card in the plugin, it should fix automatically your APO settings.

authors: sejoker trevordbc

repo: cloudflare/Cloudflare-WordPress


text:
Add support for configuration via environment vars

Having a the ability to configure credentials via environment vars would be quite appreciated by advanced users.

Storing credentials in a database can be insecure if data is exported to other environments, eg: dev.
Reusing credentials is not flexible if dev environments are running on different domain(s).

awesome stuff! after battling YAML, i managed to test this out and it works great! thank you ❤

Sure thing! Glad to help.

authors: jacobbednarz joeles


text:
Adding Firebase App Check workers template to docs

I've been using CF workers along with Firebase App Check for a while now in production. This is sort of equivalent to a captcha, and is useful for preventing easy/excessive access to resources without first passing the check (an invisible captcha on the web, or Android/iOS attestation).
I thought it might be useful to share the code in the form of a template, available here https://github.com/chocolatkey/worker-appcheck-template , inspired by the current quickstart examples. Is it worth adding this as one?

Hey @chocolatkey - thanks for the idea! Would you mind opening a PR and adding the template to this page: https://developers.cloudflare.com/workers/get-started/quickstarts#example-projects
File in source is here: https://github.com/cloudflare/cloudflare-docs/blob/production/products/workers/src/content/get-started/quickstarts.md

@codewithkristian Done, here: https://github.com/cloudflare/cloudflare-docs/pull/3365

authors: chocolatkey codewithkristian

repo: cloudflare/cloudflare-docs


text:
[⚡ Feature]: Supporting Next.js runtime Node.js

Description
I see Cloudflare supporting more and more Node.js modules.
Additional Information
No response
Would you like to help?

[ ] Would you like to help implement this feature?

Hi @lcswillems 👋
Thanks for the issue 🙂, unfortunately I think that supporting the Node.js runtime is quite out of the question, mainly for two reasons:

This adapter works by generating a worker using the Vercel CLI build command (vercel build) output, such output comprises of edge functions and (AWS) lambda functions, the adapter collects the code from the former to build the worker and discards the latter (when discarding the code doesn't generate a loss of functionality, if it does then the adapter's build process fails). The latter is code very AWS lambda specific and not something we can really use (unless we were to deploy it to AWS).
The Cloudflare runtime does support more Node.js modules but not all of them (fs, path, os, etc...), I am not sure if and how we on next-on-pages could support those? should they be no-op? surely that would break in many many use case no?  (PS: I have no idea if/how/when they could be included in the runtime either)

The only practical solution I can think that would address both issues above would be to, actually make @cloudflare/next-on-pages work with both runtimes, and for node runtimes have the lambda(s) deployed to AWS, although that would introduce many issues:

we want the code only to run in a worker as that is what provides the best and fastest user experience, mixing this with lambdas, which often could be required to run before the worker code, could quite defeat the purpose here
we'd have to find a way to connect the worker we produce with the AWS lambda(s) we get, making the whole application more complex and with more failure points. This would likely be quite awkward/cumbersome locally.
we'd have to find a way to "version"/"keep in sync" the worker and the AWS lambda(s), which might be very tricky since the two would reside on different platforms.

Additionally (likely a personal opinion)... this project is called next-on-pages as it aims to allow running a Next.js applications on the Cloudflare Pages platform, so having it more generic and include AWS (or whatever else platform) seems out of scope to me and not something that this project was designed to do/created for.
Please let me know what you think of the above 🙂
If you have any potential solutions/ideas please also feel free to throw them my way 😄

Hi @dario-piotrowicz , what about just transforming the AWS lambda into workers? Doesn't seem too hard? And it would fail only if I use node modules not supported by Cloudflare.

@lcswillems as I mentioned above:
This adapter works by generating a worker using the Vercel CLI build command
(vercel build) output, such output comprises of edge functions and (AWS) lambda
functions, the adapter collects the code from the former to build the worker and
discards the latter (when discarding the code doesn't generate a loss of functionality,
if it does then the adapter's build process fails). The latter is code very AWS lambda
specific and not something we can really use (unless we were to deploy it to AWS).

The Vercel build generates complex lambdas which usually contain multiple routes bundled and grouped in an optimized way so that they grow as big as they can without reaching the AWS lambdas max side (50MB).  So besides other things here, opposite to what we have with edge functions, there isn't even a 1-to-1 relationship between lambdas and routes.
It is as I said an AWS specific build, so pretty useless for us. I did look into it in depth a while back (looked wether we could infer any useful information/extract any useful code from the lambdas output I mean) which gives me confidence in saying that there, in my opinion, isn't really anything valuable from the lambdas that we could reuse 😕

authors: dario-piotrowicz lcswillems

repo: cloudflare/next-on-pages