text:
[FEATURE] Configure ports used by go-langserver

I am using the latest version of:

[x] Atom
[x] ide-go
[x] atom-ide-ui
[x] go-langserver

Operating System: MacOS 10.13.3
Problem
The port :6060 is used by go-langserver for pprof, and :4389 is used for the language service.
As a developer it's possible for one of these ports to be used by other software on my machine.  In my case, :6060 is being used by something else.
Request
Add the -pprof and -addr options for go-langserver to the package settings, so they can be changed by the user.

I added an option to configure the pprof port. It is actually a misleading setting, the docs make it seem like it pprof should be disabled by default but its actually running on :6060 by default and there is no way to disable it. I hope this option is the workaround you needed!
I didn't add an option for -addr because that's only used in tcp mode and this plugin uses stdio. No tcp server is started so it should never cause a conflict on :4389

authors: ckaznocha sbward

repo: ckaznocha/ide-go


text:
Example running on GPUs not CPU

Hi again all,
I've managed to get the README example for SGEMM working through my Ruby FFI into clBLAS but for some reason it will only run on my GPUs, not the CPU. A collaborator of mine is using identical code and it's running just fine on his CPU, so I don't suspect the code.
The exact issue is that I'm getting an INVALID_EVENT error from openCL. So it seems that for some reason the kernel isn't getting enqueued on my CPU and the event isn't getting created.
Is there any relevant system information I could give that would be helpful?
Me and my collaborator are both using Intel CPUs. I'm on openCL 1.1.
I don't really expect anyone to dig into the Ruby FFI for me (though that would be awesome) but perhaps you can give me a direction to bug hunt?

@KCErb which OS are you on ?

Yup that's a good place to start :blush:
I'm on OS X 10.10.1

@KCErb This is a known issue. The CPU implementation of OpenCL on OSX is a little bit funky. While it does not break the OpenCL spec, their implementation makes it harder to write a general purpose library. For example, the maximum workgroup size supported for some kernels changes to "1" which makes the code inherently serial at that point.
The CPU implementations work on other operating systems because they are implemented by the hardware manufacturers instead of Apple.
The bottom line is that it is very hard to support CPUs on OSX.

Oh, OK then. That's the sorta answer I like to hear!
Thanks @pavanky
(In case my tone could be misinterpreted I'm not being sarcastic. I really do like straightforward known answers. Sort of a bummer that OS X makes it hard, but it's not a big deal in the long run.)

source: gharchive/issue

authors: KCErb pavanky

repo: clMathLibraries/clBLAS

license_type: permissive

license_source: github-api


text:
Unable to deduce variadic templates in the llvm-project/mlir

In any usage of the create function within the mlir::OpBuilder class, clangd fails to provide argument suggestions even after passing in the correct mlir::Op to the template. My compile_commands.json was generated by default cmake config. No problem with the whole project compile.
Here's the code from mlir/include/mlir/IR/Builders.h
  template <typename OpTy, typename... Args>
  OpTy create(Location location, Args &&...args) {
      OperationState state(location,getCheckRegisteredInfo<OpTy>(location.getContext()));
      OpTy::build(*this, state, std::forward<Args>(args)...);
      auto *op = create(state);
      auto result = dyn_cast<OpTy>(op);
      assert(result && "builder didn't return the right type");
      return result;
  }

Clangd can normally deduce the parameter what mlir::OpTy::build  need, such as scf::IfOp::build and vector::MaskedStoreOp, but any mlir::OpBuilder.create builder.create<scf::IfOp> in llvm-project is unable to deduce.

OpTy::build can normally deduce the parameter, such as scf::IfOp::build or vector::MaskedStoreOp, but any builder.create<scf::IfOp> in llvm-project is unable to deduce

I don't understand what you mean by "OpTy::build can normally deduce the parameter".
MaskedStoreOp::build() is not a variadic template. It has three overloads which look like this:
void MaskedStoreOp::build(::mlir::OpBuilder &odsBuilder, ::mlir::OperationState &odsState, ::mlir::Value base, ::mlir::ValueRange indices, ::mlir::Value mask, ::mlir::Value valueToStore) { ... }
void MaskedStoreOp::build(::mlir::OpBuilder &odsBuilder, ::mlir::OperationState &odsState, ::mlir::TypeRange resultTypes, ::mlir::Value base, ::mlir::ValueRange indices, ::mlir::Value mask, ::mlir::Value valueToStore) { ... }
void MaskedStoreOp::build(::mlir::OpBuilder &, ::mlir::OperationState &odsState, ::mlir::TypeRange resultTypes, ::mlir::ValueRange operands, ::llvm::ArrayRef<::mlir::NamedAttribute> attributes) { ... }

and clangd's signature help is showing you these parameters as written in the declaration.
OpBuilder::create() is a variadic template, and clangd's signature help is showing you its parameters as written in the declaration.

I have edited my issue, I'm sorry for my poor English. The variadic template pass to OpBuilder::create() will finally pass to OpTy::build, once passing the Op type such as scf::IfOP to the OpTy template, OpTy::build(*this, state, std::forward<Args>(args)...); make the type constraints clear, the Args &&...args passing to the create function should same as the std::forward<Args>(args)... args. If I edit the original OpTy::build(*this, state, std::forward<Args>(args)...); to scf::IfOp::build(*this, state); the clangd will deduce which parameter should I pass. Can clangd deduce the mlir::OpBuilder::create  parameters like that? Thank you for your answer!

Ok, I believe I understand: you would like clangd to use the information that OpBuilder::create() passes its parameter pack args... to OpTy::build(), combined with the knowledge that OpTy is known to be a specific type (such as scf::IfOp) for a call written as builder.create<scf::IfOp>(...), to replace the Args &&args... in the signature hint with the concrete parameters of scf::IfOp::build().
This is not currently implemented in clangd.
I definitely see the value in this as a user. However, I can think of a couple of implementation challenges:

Clangd skips parsing of function bodies in included headers for performance reasons. So, when editing a .cpp file, the AST clangd uses does not contain the function body of OpBuilder::create(), only its declaration. As such, clangd cannot see how OpBuilder::create() uses its args... parameter.
Even if we had access to the function body, when you're in the middle of the writing the call, the function body is not yet instantiated (unlike in the case of inlay hints, where we use the instantiation to handle forwarded parameter packs specially). Indeed, we don't even have a complete list of template arguments to instantiate it with, only a partial list (the explicitly provided ones). It's not clear that substituting the partial list of known template arguments into the function body is something we can do "on the fly" during code completion (though this is something that could be explored).

We have #447 on file for a similar request about make_unique<T>(...), and a WIP patch for that issue. That patch sidesteps the above problems by hard-coding knowledge of the function body into clangd: clangd knows that make_unique<T>(...) will call the constructor of T, so it doesn't need to look at the function body of make_unique to determine that. It's not clear how this could approach could generalize to cases like OpBuilder::create<T>(...) calling T::build().

repo: clangd/clangd


text:
11.0.0-rc1 crashing with OmniSharp client

Just for context
I am trying to integrate clangd into my own editor using the OmniSharp LSP Client available here. Clangd 10 works fine but the 11.0.0-rc1 crashes on initializing.
I am not completely sure if this is a issue with clangd or with the OmniSharp client, but since all other LSP Servers (I tested a lot) or clangd 10.0 work with the OmniSharp Client I decided to open the issue here.
It simply fails to initialize because it can't parse allCommitCharacters from completionProvider.
Logs
I don't have a full log right now but I think this might show what's going on:
[Error]: Initializing clangd.exe failed! Error converting value " 	()[]{}<>:;,+-/*%^&#?.="'|" to type 'OmniSharp.Extensions.LanguageServer.Protocol.Models.Container`1[System.String]'. Path 'result.capabilities.completionProvider.allCommitCharacters', line 1, position 197.

System information
Output of clangd --version: 11.0.0-rc1 (from releases tab)
Editor/LSP plugin: OmniSharp c# LSP client
Operating system: Tested with windows and ubuntu 18.04

You might have a problem with the escaping of quotes in your editor/plugin communication. the text in the error doesn't have a backslash before the " (it also has lots of whitespaces at the front).
Normally this is the relevant field advertised by clangd during initialization (note the backslash before the double quote, 3rd element from the end):
"allCommitCharacters":[" ","\t","(",")","[","]","{","}","<",">",":",";",",","+","-","/","*","%","^","&","#","?",".","=","\"","'","|"]

And that's how LSP specifies the field: https://microsoft.github.io/language-server-protocol/specification#textDocument_completion (search for allCommitCharacters), i.e. as a string array.
We also have lots of internal users testing clangd trunk on a variety of editors and I can't say we've received such a complaint yet. So I would rather check the concatenation logic producing the string you've mentioned in the error. If it seems valid, please provide clangd logs so that we can take a more detailed look.

The logic for that is included in the OmniSharp Librarys, not on my side. As I said, it might be a bug with the OmniSharp libraries. I was just wondering why clangd 10 (or every other LSP I tested so far) is working without problems.

oh sorry, i forgot to provide an explanation for that part. It is because
advertising of "allCommitCharacters" wasn't there before clangd-11. I can't
talk about other language servers tho, it might be the case that they just
don't advertise it at all.
On Thu, Sep 10, 2020 at 8:33 PM Hendrik Mennen notifications@github.com
wrote:

The logic for that is included in the OmniSharp Librarys, not on my side.
As I said, it might be a bug with the OmniSharp libraries. I was just
wondering why clangd 10 (or every other LSP I tested so far) is working
without problems.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/clangd/clangd/issues/522#issuecomment-690605831, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAG3EE5N5RTXUMGSXGOQLULSFELVZANCNFSM4RFRA4UA
.

Yes I found that out too. My other language servers don't provide allCommitCharacters aswell so they have no problem (Python, VHDL, Verilog and few others). I am convinced this is a bug with OmniSharp Client. Thank you

Normally this is the relevant field advertised by clangd during initialization (note the backslash before the double quote, 3rd element from the end):
"allCommitCharacters":[" ","\t","(",")","[","]","{","}","<",">",":",";",",","+","-","/","*","%","^","&","#","?",".","=","\"","'","|"]

This is the retrieved initialisation message from reading stderr with --log=verbose:
{"id":1,"jsonrpc":"2.0","result":{"capabilities":{"codeActionProvider":{"codeActionKinds":["quickfix","refactor","info"]},"completionProvider":{"allCommitCharacters":" \t()[]{}<>:;,+-/*%^&#?.=\"'|","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"]},"hoverProvider":true,"referencesProvider":true,"renameProvider":true,"selectionRangeProvider":true,"semanticTokensProvider":{"full":{"delta":true},"legend":{"tokenModifiers":[],"tokenTypes":["variable","variable","parameter","function","member","function","member","variable","class","enum","enumConstant","type","dependent","dependent","namespace","typeParameter","concept","type","macro","comment"]},"range":false},"signatureHelpProvider":{"triggerCharacters":["(",","]},"textDocumentSync":{"change":2,"openClose":true,"save":true},"typeHierarchyProvider":true,"workspaceSymbolProvider":true},"serverInfo":{"name":"clangd","version":"clangd version 11.0.0 (https://github.com/llvm/llvm-project d6875948aaade1cd39e5d9b373d02749dd1e58f2)"}}}

This is the field that causes trouble: "allCommitCharacters":" \t()[]{}<>:;,+-/*%^&#?.=\"'|"
According to https://microsoft.github.io/language-server-protocol/specification#textDocument_completion this should be an array, but it isnt't send as an array from clangd.
I think it should be send like the other field: "triggerCharacters":[".","<",">",":","\"","/"]}

Looks like this was fixed recently at https://github.com/llvm/llvm-project/commit/9d11e6789c477ce6104e29745ca70e13c9fafeb0.
Filed https://bugs.llvm.org/show_bug.cgi?id=47526 for cherry-pickign the fix into 11.0 release. Thanks for bringing this to our attention (and sorry for missing it at the first look).
In the meantime, you can build a clangd from trunk, will close this issue once fix is cherry-picked into release branch.

Thank you!

This has been merged to the 11 branch.

authors: HendrikMennen kadircet sam-mccall


text:
HLSJS now initialised immediately

So that PLAYER_READY can fired before the users requests to play the content.

This seems messy: https://github.com/clappr/clappr/pull/747/files#diff-c2aedd093e03237d4e53308106db71a2R68
Why should the poster automatically disappear for a playback anyway without the user playing?

@tjenkinson I don't think this is the best solution, since hls.js starts preloading the video, as if playback has been started. We avoided initializing the hls object immediately to avoid unnecessary requests. Unless preloading the video is an options and the user chooses this, I wouldn't do it this way.
About the poster disappearing in the first bufferfull event, it's because the bufferfull event should only be triggered when loading the video, not when preloading. I would let this change on the poster plugin to a later time, since we want to avoid the poster to manage it's own state, but instead being controlled by the container.
Perhaps the right approach is to consider the playback ready after rendering, or if preload is enabled, after preloading. The buffering event shouldn't be triggered on preload, unless autoPlay is enabled.

@towerz ok I see I was wondering why it might have been like that.
Just looked at the hlsjs options and there's a autoStartLoad, which when false seems to prevent the requests starting. It also doesn't work when clicking play either but guess there's some other that needs calling in a play() override, I haven't figured it out yet.
So then instead this method could be used (depending on whether the user has chosen to preload or not).
Sound ok?

Sounds ok for me. Perhaps we could tranlslate the preload option that we use on the html5_video playback to autoStartLoad, or add to as an exposed HLS option. By default, there should be no preload, so this proposed solution should work ok.

@towerz I've updated this now to just call ready() as soon as the class has loaded. It means the BUFFERFULL event is also fired though and I'm not sure if this makes sense.
I tried the other way, having hlsjs load but with autoStartLoad as false but it causes issues because the video element fires the stalled event which causes the loading indicator to appear. It's for the same reason that it's not possible to load hlsjs immediately if options.preload === "auto"

Ignore this at the moment I had to merge master and it isn't working now

It's because the playback events can fire before the listeners are added :/
We could have another check in here like other places to check if the isReady is true, but that only handles this one case. What about any other playback events that end up firing before the listeners are registered, for example? In the code it looks like there is already the possibility for ready() to be called in the render() method which I think at the moment wouldn't work.
Maybe there should be a separate init() method in playback() or something which would be called after bindEvents()?

@tjenkinson why don't we trigger the ready state only after render instead of in the constructor? As far as I know, the listeners are always added before rendering, so there's no risk of the event being triggered without listeners. Actually this would be more accurate, because a video element should only be ready after it's added to the DOM.

@towerz yes never thought of that it makes a lot more sense!

@towerz this works but the poster disappears incorrectly, which I think #749 will fix.

Actually no the event is still firing before the listeners are added :/

Stupid mistake should be fine now.

Thanks @tjenkinson

source: gharchive/pull-request

authors: leandromoreira tjenkinson towerz

repo: clappr/clappr

license_source: bigquery


text:
🛑 Main is down

In 325822c, Main (https://www.nsercresnet.ca) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Main is back up in beed21a after 8 minutes.

repo: clarkwrks/resnet-status

license: MIT


text:
Attend on public events

A user should be able to create a "attendee" membership for public events.
There should be generic invitation link for an event (event_token).

logged in users are able to add membership directly for public events, now

now not logged in users can also attend by sending an invitation to themself --> so they get an invitation link and we do not have to think about a new workflow of creating users/memberships.
Already logged in users can attend directly or invite other people to the event

repo: classlab/classlab

license: mit


text:
Add quotes around the values

Adding quotes around the dynamically loaded values prevents possible security risks when weird or malicious values are be used.

@claudenm just a small tweak to make sure the dynamically loaded values cannot cause any security issues.

repo: claudenm/aws-okta


text:
is it possible to get overId and activeId on dndcontext modifiers ?

hey, awesome library! really smooth transitions
is it possible to get the overId and activeId on a custom modifier context ? I would like to apply custom restrictions based on the type of the element i'm dragging rather than its position.
thanks

Hey, not currently, but this would be a fairly straightforward change. If you'd like to and have time to do so, PRs are welcome 🙏

Hey, not currently, but this would be a fairly straightforward change. If you'd like to and have time to do so, PRs are welcome 🙏

This would be cool to have!

Added in this PR #207

authors: clauderic idhard leon-marzahn

repo: clauderic/dnd-kit


text:
feat: add disableAnimation prop

Hi,
In one of our projects we had to disable elements "animation" (switching places) until onSortEnd. We added new prop disableAnimation that does just that.
We use onSortOver to mark the position where the element will be dropped.
This allows us to achieve something like this:

Same with animations enables:

We also need this, and while react-dnd is good, we really prefeer using the simpler and leaner react-sortable-hoc

Update the code to latest and Created a new PR implementing the same functionality as this PR with the latest code, in case you change your mind about how useful it could be :)
https://github.com/clauderic/react-sortable-hoc/pull/749

authors: krzaczek yuri-scarbaci-lenio

repo: clauderic/react-sortable-hoc


text:
No image being output when using toScreen()

It does not give any errors. Although I turned on all error warnings.
What is the problem?
http://prntscr.com/o4fxfc
http://prntscr.com/o4g0dc

Need working code to test. Does this happens with images on other domains, or is it limited to the one you're targeting? It could be the target host is rejecting the request based on user agent, IP address, etc.
Or it could be that you don't have fopen wrappers enabled. (Try removing the @ from line 117 to test if you want).

Unfortunately, there was no change when I removed the code on the line you specified.
I can get the image data in a healthy way, but I can't show it on the screen. It is the same for all pictures, but there are no rope problems.
`try {
$image = new SimpleImage();
$image
->fromFile('https://helpx.adobe.com/content/dam/help/en/stock/how-to/visual-reverse-image-search/jcr_content/main-pars/image/visual-reverse-image-search-v2_intro.jpg')
->autoOrient()
->bestFit(720, 1280)
->toScreen();
} catch(Exception $err) {
echo $err->getMessage();
}`

Works for me. Check your error logs. Make sure PHP has enough memory to work with.

http://prntscr.com/o4h74m
So what are your server settings?

Just using the local version of PHP on macOS.

http://prntscr.com/o4h9zq
I can get picture data. But when I add a header, I can't get a result. I do not receive any error log.
http://prntscr.com/o4hb7i

Closing due to inactivity. If this is still an issue, please post more info and we'll try to help.

authors: Ecancan claviska

repo: claviska/SimpleImage


text:
feat: add datadog_trace 0.92.2 release

update datadog_trace with release 0.92.2

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

repo: claylo/pecl-info


text:
Starting point for AST transformation

Are there any starter kit or something to play with the generated AST? I'd thought that passing AST JSON through JMESPath will help in quicker code conversion. But, it looks complex than than.
IOW, are there any best practices for the AST transformation or modification?

The best practice would be to use 🐊Putout code transformer for any purpose of programming changing the code, it has plugins, guide and online editor :)!

@coderaiser Thank for sharing this. Looks interesting for many cases. But, beyond the predefined cases, it seems to be difficult. Anyway, will closely check that for https://github.com/rrjanbiah/react2solid

@rrjanbiah just create an issue in 🐊Putout repository with transform you need (before -> after), and I’ll try to help :)

@coderaiser Will closely check and will do. Thanks for being generous!

Hey, sorry for the late response. I have an example in the following place. Hopefully I can create more examples soon. I want to create an example of React class component, React functional component and express endpoint. The main use case for this project is to create compostable code generators for common repetitive patterns.
https://github.com/clayrisser/react-ast/blob/master/example/index.tsx

@clayrisser, that's definitely better then JSON, but how it's better then @babel/template?
import template from "@babel/template";
import generate from "@babel/generator";

const buildRequire = template.ast(`
    class Hello {
        add(a, b) {
            return a + b;
        }
    }
`);

console.log(generate(ast).code);

@coderaiser it's better because it supports composablity. In other words, you could build multiple templates with this, and then use them together.
For example, you could create a <ClassReactComponent \> template that generates code for a class based react component. You could then use this component in a larger generator. Then, perhaps in the future, you want to switch your generator to use function components. Instead of rebuilding the entire template, you would just swap out  <ClassReactComponent \> with <FunctionReactComponent \>.
In other words, you can componentize and abstract the generation of code into tiny parts and use those pieces together in a composable way.
Generating a react component with template.ast() might solve a code generation problem, but it probably can't be reused for other similar problems.
Hope this makes sense. I need to improve the docs to clearly explain this use case. I think it's really powerful.

authors: clayrisser coderaiser rrjanbiah

repo: clayrisser/react-ast


text:
🛑 livevault is down

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

HTTP code: 0
Response time: 0 ms

Resolved: livevault is back up in fefb1b0.

repo: claytonplong/backup-uptime


text:
🛑 livevault is down

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

HTTP code: 0
Response time: 0 ms

Resolved: livevault is back up in 92d2138.


text:
[GlobalTime] Cannot toggle lights

[Reported against r13 running on beta 0.9 emulator]

Pressing L to toggle the lights display doesn't work.

Cause is the following code in the GlobalTime.onKeyDown method:

        // If we're not in alphabetical entry mode, convert letters
        // to their digit equivalents
        if (!mAlphaKeySet) {
            char numChar = event.getNumber();
            if (numChar >= '0' && numChar <= '9') {
                keyCode = KeyEvent.KEYCODE_0 + (numChar - '0');
            }
        }

After this code has executed, KEYCODE_L has been remapped to KEYCODE_5.

Note that event.getNumber() returns '5' for 'L' because the JKL key on the
touch pad bears the numeral 5.

KEYCODE_W and most other alpha keys are also broken by this code.

Original issue reported on code.google.com by joe.bowb...@gmail.com on 29 Aug 2008 at 12:04

Original comment by morri...@gmail.com on 13 Nov 2008 at 10:11

Changed title: [GlobalTime] Cannot toggle lights

Original comment by morri...@gmail.com on 13 Nov 2008 at 10:17

Added labels: Application-AndroidGlobalTime

repo: clc/apps-for-android


text:
DepthConcat problem in FaceNet model

Hi, clcarwin,
Have you tried convert FaceNet's model?
It is used in OpenFace project, and you can download the model here
It requires dpnn package to load the model in lua.
Since it's a bit of old, I load and save it with the newest lua torch.
When I convert this model to PyTorch, this error occurs:
File "/home/xiaolush/.pyenv/python3.5/lib/python3.5/site-packages/torch/utils/serialization/read_lua_file.py", line 357, in storage_to_size
value = getattr(obj, attr)
AttributeError: 'DepthConcat' object has no attribute 'outputSize'
Do you have a hint where could be the problem?
Thanks!

This is a bug in read_lua_file.py. Re-saving the model with this lua script can pass the error.
m = torch.load('nn4.small2.v1.t7')
m:replace(function(mm)
	if torch.typename(mm)=='nn.DepthConcat' then
		mm.outputSize=torch.LongStorage()
	end
	return mm
end)
torch.save('nn4.small2.v1.t7',m)

However convert_torch.py can not support dpnn package. The openface model still can not be converted.
Not Implement nn.SpatialConvolutionMM
Not Implement nn.SpatialConvolutionMM
Not Implement nn.SpatialConvolutionMM
Not Implement nn.Inception
Not Implement nn.Inception
Not Implement nn.Inception
Not Implement nn.Inception
Not Implement nn.Inception
Not Implement nn.Inception

@clcarwin Hi!
Has dpnn support been included yet or is it in the pipeline?
Would save me a lot of boilerplate code if your repo could convert the openface model to pytorch.'
Thanks

authors: TwoBranchDracaena clcarwin pkmandke


text:
Support and Test Firefox

Firefox tests removed after failing with Mocha.
        {
          "browserName": "firefox",
          "platform": "Windows 10",
          "version": ""
        },
        {
          "browserName": "firefox",
          "platform": "OS X 10.11",
          "version": ""
        }

Possible error due to Firefox 48, using version 47.  See Polymer/web-component-tester#365

Possible error due to Firefox 48, using version 47.  See Polymer/web-component-tester#365

repo: cleantile/cleantile


text:
Make the shim wait for the process to be started before forwarding stdin and signals

A somewhat long-winded PR that should remove the need to start the shim as stopped. We finish the work to started to synchronise runtime, shim and the process inside the VM without queuing data. It can be a bit fiddly so the code is somewhat heavily documented and tested.

Coverage increased (+1.3%) to 71.872% when pulling af0fec40487e31158604450f8c29d17f731a78c9 on dlespiau:20170504-sync-stdin-newcontainer-execcmd into 70866bae885913e407c6e23194da008dd13b5e1b on clearcontainers:master.

Coverage increased (+1.3%) to 71.872% when pulling af0fec40487e31158604450f8c29d17f731a78c9 on dlespiau:20170504-sync-stdin-newcontainer-execcmd into 70866bae885913e407c6e23194da008dd13b5e1b on clearcontainers:master.

Coverage increased (+1.7%) to 72.292% when pulling af0fec40487e31158604450f8c29d17f731a78c9 on dlespiau:20170504-sync-stdin-newcontainer-execcmd into 70866bae885913e407c6e23194da008dd13b5e1b on clearcontainers:master.

One comment about function comment not in sync with the function name, but other than that LGTM.

Coverage increased (+1.3%) to 71.872% when pulling 5eb191d3f5994b0891cd6e5a731925fbd952fb48 on dlespiau:20170504-sync-stdin-newcontainer-execcmd into 70866bae885913e407c6e23194da008dd13b5e1b on clearcontainers:master.

argh, I can't merge it because the LGTM isn't at the start of the line. Grmbl.

PR updated:

Renamed waitForExecTimeout to waitForProcessTimeout.

Coverage increased (+1.2%) to 72.292% when pulling 1124a6f8709a4789744ded27f494e5b97cedad4b on dlespiau:20170504-sync-stdin-newcontainer-execcmd into 4db5a150d393869b5c3200544418f2931afe3fd6 on clearcontainers:master.

PR updated:

Renamed RelocateHyperCommand to relocateHyperCommand in comment.

Coverage increased (+1.7%) to 72.241% when pulling b9948be24eac8bde090769207ee89d60bfa74860 on dlespiau:20170504-sync-stdin-newcontainer-execcmd into 800cc89e68c488d7c994c1139973ed06d05ff66f on clearcontainers:master.

Coverage increased (+1.3%) to 71.823% when pulling ba3b9b575e0273af5113e0ff95e3e5cbf63698bc on dlespiau:20170504-sync-stdin-newcontainer-execcmd into 800cc89e68c488d7c994c1139973ed06d05ff66f on clearcontainers:master.

This needs to be rebased on top of the logrus port before merging.

And now rebased on top of the logrus changes.

Coverage increased (+1.6%) to 72.904% when pulling 70af5ecaf892c6020cec2f260d1707af9fa5ee77 on dlespiau:20170504-sync-stdin-newcontainer-execcmd into 2925d0a65a3a80503918cf5718becf66cb998e95 on clearcontainers:master.

@amshinde mind having another look at this one?

lgtm

authors: amshinde coveralls dlespiau sboeuf

repo: clearcontainers/proxy


text:
How to send raiblocks without syncing

How can I export the private keys and send raiblocks (that was deposited in a wallet) without syncing that wallet ?
I ask because it is definitely not going to sync after so many hours (still havent sync 5%). I think there are some serious scalability issues with raiblock since it takes days to sync and its still very new (imagine if we have 100x more accounts), that would become impossible.
Now my raiblocks are stuck in a unsyncable wallet and I would like to know how to send that (just like it is possible to do with ether, bitcoin, litecoin. They can be sent by importing the private key into a light wallet then sending it. But i dont find how to do that for raiblocks. Thanks.

@marc477 I had the same problem. The workaround is take your local wallet seed and import it to their online wallet. Your balance would be available right away. Yes I agree they need to fix the local wallet sync problems ASAP.

repo: clemahieu/raiblocks


text:
chore(*): Sync main-v4 with main

Description
Until we begin to start the Clerk@v5 Release Process the main-v4 branch should be in sync with main. Sync we enforced the same rules in main-v4 as main we cannot force push the changes, so this PR will rebase main into main-v4 when we proceed with Clerk@v5.
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:

Packages affected

[ ] @clerk/clerk-js
[ ] @clerk/clerk-react
[ ] @clerk/nextjs
[ ] @clerk/remix
[ ] @clerk/types
[ ] @clerk/themes
[ ] @clerk/localizations
[ ] @clerk/clerk-expo
[ ] @clerk/backend
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/fastify
[ ] @clerk/chrome-extension
[ ] gatsby-plugin-clerk
[x] build/tooling/chore

This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

authors: clerk-cookie dimkl

repo: clerk/javascript


text:
fix(clerk-js): Fix Phone input styling

Description

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:

Packages affected

[ ] @clerk/backend
[ ] @clerk/chrome-extension
[ ] @clerk/clerk-js
[ ] @clerk/clerk-expo
[ ] @clerk/fastify
[ ] gatsby-plugin-clerk
[ ] @clerk/localizations
[ ] @clerk/nextjs
[ ] @clerk/clerk-react
[ ] @clerk/remix
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/themes
[ ] @clerk/types
[ ] build/tooling/chore

!preview

Hey @octoper, your preview is currently deploying and should be available shortly.

Status
Preview
Updated (UTC)

:cook: Deploying...
Inspect
Dec 20, 2023 07:05 PM

authors: clerk-cookie octoper


text:
feat(clerk-js,nextjs,clerk-react,types): Introduce <Waitlist /> component

Description
Show Join waitlist promt from <SignIn /> component when mode is waitlist
Change the text in RestrictedAccess component when mode is waitlist
Introduce <Waitlist /> component to allow users to join in the waitlist via email
Introduce joinWaitlist method in clerk class
Introduce redirectToWaitlist function in clerk class to allow user to redirect to waitlist page

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
[x] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

<SignIn /> Component with sign_up.mode = waitlist

<SignUp /> Component with sign_up.mode = waitlist

<Waitlist /> Component

<Waitlist /> Component success screen

<Waitlist /> Component success screen with redirectUrl presented

!snapshot

Hey @nikospapcom - the snapshot version command generated the following package versions:

Package
Version

@clerk/astro
1.4.3-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c

@clerk/backend
1.15.3-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c

@clerk/chrome-extension
1.3.25-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c

@clerk/clerk-js
5.31.0-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c

@clerk/elements
0.18.1-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c

@clerk/clerk-expo
2.2.31-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c

@clerk/expo-passkeys
1.0.0-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c

@clerk/express
1.3.5-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c

@clerk/fastify
2.0.7-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c

@clerk/localizations
3.5.0-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c

@clerk/nextjs
6.2.0-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c

@clerk/clerk-react
5.15.0-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c

@clerk/remix
4.2.43-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c

@clerk/clerk-sdk-node
5.0.56-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c

@clerk/shared
2.11.1-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c

@clerk/tanstack-start
0.4.19-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c

@clerk/testing
1.3.17-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c

@clerk/themes
2.1.41-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c

@clerk/types
4.30.0-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c

@clerk/ui
0.1.12-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c

Tip: Use the snippet copy button below to quickly install the required packages.
@clerk/astro
npm i @clerk/astro@1.4.3-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c --save-exact

@clerk/backend
npm i @clerk/backend@1.15.3-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c --save-exact

@clerk/chrome-extension
npm i @clerk/chrome-extension@1.3.25-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c --save-exact

@clerk/clerk-js
npm i @clerk/clerk-js@5.31.0-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c --save-exact

@clerk/elements
npm i @clerk/elements@0.18.1-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c --save-exact

@clerk/clerk-expo
npm i @clerk/clerk-expo@2.2.31-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c --save-exact

@clerk/expo-passkeys
npm i @clerk/expo-passkeys@1.0.0-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c --save-exact

@clerk/express
npm i @clerk/express@1.3.5-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c --save-exact

@clerk/fastify
npm i @clerk/fastify@2.0.7-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c --save-exact

@clerk/localizations
npm i @clerk/localizations@3.5.0-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c --save-exact

@clerk/nextjs
npm i @clerk/nextjs@6.2.0-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c --save-exact

@clerk/clerk-react
npm i @clerk/clerk-react@5.15.0-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c --save-exact

@clerk/remix
npm i @clerk/remix@4.2.43-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c --save-exact

@clerk/clerk-sdk-node
npm i @clerk/clerk-sdk-node@5.0.56-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c --save-exact

@clerk/shared
npm i @clerk/shared@2.11.1-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c --save-exact

@clerk/tanstack-start
npm i @clerk/tanstack-start@0.4.19-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c --save-exact

@clerk/testing
npm i @clerk/testing@1.3.17-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c --save-exact

@clerk/themes
npm i @clerk/themes@2.1.41-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c --save-exact

@clerk/types
npm i @clerk/types@4.30.0-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c --save-exact

@clerk/ui
npm i @clerk/ui@0.1.12-snapshot.ve498412ac8617eb535cbbeb78d27ded11ad8f45c --save-exact

One thing I just noticed about Astro: there's now a waitlistUrl in the Astro integration config and the SignUp and SignIn components. However, you can't really use this new feature when you've disabled the account portal because the Waitlist component is missing. I guess Astro support will be shipped later?

One thing I just noticed about Astro: there's now a waitlistUrl in the Astro integration config and the SignUp and SignIn components. However, you can't really use this new feature when you've disabled the account portal because the Waitlist component is missing. I guess Astro support will be shipped later?

Hey @mlafeldt
We're working on it and I'll have an update this week

One thing I just noticed about Astro: there's now a waitlistUrl in the Astro integration config and the SignUp and SignIn components. However, you can't really use this new feature when you've disabled the account portal because the Waitlist component is missing. I guess Astro support will be shipped later?

Hey @mlafeldt
We released the support of <Waitlist /> component for astro. You should install version @clerk/astro@1.5.0 :)
Feel free to reach out us if you running any issue
Thanks

@nikospapcom Added a waitlist to my Astro app without a hitch. 💥 Left some feedback here.

authors: clerk-cookie mlafeldt nikospapcom


text:
Fix a cookies call that was not await-ed

Description
This PR fixes a dangling cookies() call that was not awaited causing errors when using Next.js 15. With @clerk/nextjs v6.0.0 I noticed that performing certain actions such as clicking a <SignOutButton> would error with that particular callsite.
Since this function was already marked as async there shouldn't be any other required changes.

Checklist

[X] npm test runs as expected.
[X] 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

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

Thank you so much! We missed this one.
Closing in favor of https://github.com/clerk/javascript/pull/4396 as we also need to not return the result of the call.

authors: BRKalow ChristianIvicevic


text:
Not able to import qs to run examples

I've tried both the OneJS (https://github.com/clkao/plv8x/tree/master) and the
Browserify (https://github.com/clkao/plv8x/tree/browserify) branches.
The OneJS branch results in:
postgres=# SELECT ~>'require("qs").parse("foo=bar&baz=1")';
WARNING:  failed to load module qs: Error: Cannot find module "qs" @[module: lib/index package: plv8x]
ERROR:  TypeError: Cannot call method 'parse' of undefined
DETAIL:  undefined() LINE 1:   return require("qs").parse("foo=bar&baz=1");

The Browserify branch results in:
postgres=# SELECT ~>'require("qs").parse("foo=bar&baz=1")';
WARNING:  failed to load module LiveScript:
ERROR:  TypeError: Cannot call method 'compile' of undefined
DETAIL:  boot() LINE 82:   return require('LiveScript').compile(expression, {

Yet the install appears to have succeeded:
postgres=# SELECT name FROM plv8x.code;
 name
-------
 qs
 plv8x

postgres@...:~$ plv8x -d /var/run/postgresql -l
qs: 12615 bytes
plv8x: 899907 bytes

This on a default install of Postgres 9.3 on Ubuntu 14.04 with Node v0.10.29
and NPM 1.4.14 (both of which were install via packages).

Hm, the ~> operator requires LiveScript. try this:
#postgres=# SELECT |> 'require("qs").parse("foo=bar&baz=1")';

Okay, how do I run a web server inside Postgres?

authors: clkao solidsnack


text:
Update ESXi Provider to josenk/esxi

Update ESXi provider to josenk from hashicorp/esxi
DetectionLab/ESXi terraform init && terraform apply

Initializing the backend...

Initializing provider plugins...
- Finding latest version of hashicorp/esxi...

Error: Failed to install provider

Error while installing hashicorp/esxi: provider registry registry.terraform.io
does not have a provider named registry.terraform.io/hashicorp/esxi

△ DetectionLab/ESXi terraform init && terraform apply                                                                                master :: 25d :: ⬡

Initializing the backend...

Initializing provider plugins...
- Finding josenk/esxi versions matching "1.8.0"...
- Installing josenk/esxi v1.8.0...
- Installed josenk/esxi v1.8.0 (self-signed, key ID A3C2BB2C490C3920)

Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/plugins/signing.html

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Looks good, thanks @aancw !

authors: aancw clong

repo: clong/DetectionLab


text:
npm start :compiled with warnings

OS Ubuntu 18.04

Nevermind the warnings in the terminal. Those functions can be used as props for ObjectDetectionVideo and therefore replacing the original render function.
What errors are you receiving in your web console?

On localhost and else PC's web console is different, and what causes a blank screen?

Googling the error message, seems to be a permissions issue maybe? Does your device have a webcam?

This site seems to have some useful info on debugging the issue: https://blog.addpipe.com/common-getusermedia-errors/

Googling the error message, seems to be a permissions issue maybe? Does your device have a webcam?

Okay, I connect my webcam and allow .
It's blank screen, too.

Hmm no more webcam issue, not sure where to go from here...

I would recommend to make sure that Firefox is up to date and that your vm is set up correctly.
A work around is to install ngrok and tunnel the dev server to a https endpoint. https is required for enabling camera permissions on the web, that's why it wont work on the host


text:
[Alibaba:VM] Incorrect Zone-based control for VM

Zone-based Control 시험에서

참고: https://docs.google.com/spreadsheets/d/1U_xZA9MkV6zrLyPDSw2WlbJ03jFcvGNp5zPrJ_hkSoc/edit?gid=0#gid=0

 Zone 기본 시험: Pass
 Default Zone 시험: Pass
 Target Zone 시험: Fail

[증상]

Connection : cn-beijing / cn-beijing-f  zone
Subnet 생성을 Target Zone(cn-beijing-e zone) 설정으로 생성: Pass

VM 생성을 cn-beijing-e Zone에 생성한 subnet 설정으로 생성: Issue(점검 필요)

VM 생성 실패
CB-SPIDER].[ERROR]: 2024-08-23 23:09:18 VMManager.go:509, github.com/cloud-barista/cb-spider/api-runtime/common-runtime.StartVM() - SDK.ServerError
ErrorCode: InvalidVSwitchId.NotFound
Recommend: https://api.alibabacloud.com/troubleshoot?intl_lang=EN_US&q=InvalidVSwitchId.NotFound&product=Ecs&requestId=E61B967C-844C-5D88-9AEE-CB86B06900A5
RequestId: E61B967C-844C-5D88-9AEE-CB86B06900A5
Message: vsw cn-beijing-e
RespHeaders: map[Access-Control-Allow-Origin:[*] Access-Control-Expose-Headers:[*] Connection:[keep-alive] Content-Length:[314] Content-Type:[application/json;charset=utf-8] Date:[Fri, 23 Aug 2024 14:09:18 GMT] Keep-Alive:[timeout=25] X-Acs-Request-Id:[E61B967C-844C-5D88-9AEE-CB86B06900A5] X-Acs-Trace-Id:[8fd4aa1b2edd03a73dcabc0f79fb6f3f]]

참고: 요청 정보

Fixed in https://github.com/cloud-barista/cb-spider/pull/1313

repo: cloud-barista/cb-spider


text:
Load latest BOM in Ascent tool

Make sure latest automation-solutions BOMs are in Ascent

we have not automated that flow just yet

Loaded BOMS as of 23th June 11am contents


text:
Integrate Z/OS automation as a Techzone environment

Integrate Z/OS automation as a Techzone environment
automation: https://github.com/cloud-native-toolkit/software-everywhere/issues/328
Details on Techzone:
https://ibm.ent.box.com/notes/977212608527?s=0hqyk884m6a03p0ivodup1y9mhkgyupz
General flow:

create automation to deploy resources
update automation to work with techzone framework (either wrap, or direct updates)
PR with automation into https://github.ibm.com/dte2-0/ccp-gitops-patterns/
work with Techzone team to get PR merged, then will be provisionable within Techzone environments

Related Techzone story: https://github.com/cloud-native-toolkit/software-everywhere/issues/330


text:
Initial revision

knative serving instance, required for cp4s dependencies

Merging.  The failure in the validation action is b/c of a known issue for the destroy operation, not a problem in the module.


text:
FAILED: parsing YAML file

I got the same syntax error with the existing issue "failed to parsing YAML File #129"
when running the playbook.
TASK [cloudalchemy.prometheus : configure prometheus] *************************************************************************************************************
Wednesday 20 March 2019  19:29:06 +0000 (0:00:00.061)       0:00:25.019 *******
fatal: [monitor.example.com]: FAILED! => {"changed": false, "checksum": "083e5057d0bf958f87ce817aab84c86579897d4e", "exit_status": 1, "msg": "failed to validate", "stderr": "  FAILED: parsing YAML file /home/ben.le/.ansible/tmp/ansible-tmp-1553110147.04-172617959679310/source: yaml: unmarshal errors:\n  line 23: cannot unmarshal !!str labs-al... into struct { Targets []string "yaml:\"targets\""; Labels model.LabelSet "yaml:\"labels\"" }\n", "stderr_lines": ["  FAILED: parsing YAML file /home/ben.le/.ansible/tmp/ansible-tmp-1553110147.04-172617959679310/source: yaml: unmarshal errors:", "  line 23: cannot unmarshal !!str labs-al... into struct { Targets []string "yaml:\"targets\""; Labels model.LabelSet "yaml:\"labels\"" }"], "stdout": "Checking /home/ben.le/.ansible/tmp/ansible-tmp-1553110147.04-172617959679310/source\n\n", "stdout_lines": ["Checking /home/ben.le/.ansible/tmp/ansible-tmp-1553110147.04-172617959679310/source", ""]}
It was complaining the line "23" in the prometheus.yml
Here's the Prometheus file:
global:
evaluation_interval: 15s
scrape_interval: 15s
scrape_timeout: 10s
external_labels:
{}
rule_files:

/etc/prometheus/rules/*.rules

alerting:
alertmanagers:

scheme: https
static_configs:

targets:

alertmanager.example.com

scrape_configs:

job_name: prometheus
metrics_path: /metrics
static_configs:

targets:

monitor.example.com:9090

file_sd_configs:

files:

/etc/prometheus/file_sd/node.yml
job_name: node
relabel_configs:

regex: (.*):9100
replacement: ${1}
source_labels:

address
target_label: instance
scrape_interval: 20s

Please format your message with markdown (link to a nice guide) otherwise I don't know what is the indentation in your config.

@paulfantom, please review the prometheus.txt file to see the correct indentation.
prometheus.txt

Could you also attach prometheus_scrape_configs values?

FWIW cannot unmarshal !!str labs-al... into struct { Targets []string  is a typical Go unmarshal error (i.e not Python/Ansible related)

I agree it is not python/ansible related. It is specific to this role, I think there is some misconfiguration in prometheus_scrape_config and promtool cannot handle new config. This in turn causes failure to run a role (expected behavior).

Please review the attached file
prometheus.yml.txt

I need your ansible variables, not prometheus.yml file.

monitor.txt

Attached is the ansible variables for my monitor.
monitor.txt

Sadly I don't see what is wrong. You can try running ansible playbook debugger to get prometheus.yml file created by this role and then running that file through promtool to check what is wrong.
Other solution would be to run this role with prometheus config validation removed (https://github.com/cloudalchemy/ansible-prometheus/blob/de31ec64e4bf789793528849b36b554687538302/tasks/configure.yml#L36) and manually checking what is wrong.

authors: JordanP ben-le paulfantom

repo: cloudalchemy/ansible-prometheus


text:
Large messages causes channel to shut down

We've got a production setup running where we've encountered an issue where the responses causes the server to shut down with the following error:
connection closed by server 505 UNEXPECTED_FRAME - expected content body, got non content body frame instead 60 40
amqp-client connection closed connection closed: UNEXPECTED_FRAME - expected content body, got non content body frame instead (505)
ERROR AMQPError: connection closed: UNEXPECTED_FRAME - expected content body, got non content body frame instead (505)

I've made a repo that replicates this issue consistently, under my profile: https://github.com/2joocy/cloudamqp-frame-issue
The repo contains a very minimal example of sending a message from the same channel a couple times, causing the server to crash. You can edit the connection string to rabbitmq in app.ts. The only requirement is that you've run npm i and then run npm start with the correct connection string.
We've used an older library before and didn't have issues, I've set the same test up with https://www.npmjs.com/package/amqplib and the data passes through.
Is this an issue from the library side or should we handle messages differently? Or are there parameters to circumvent this?

Try adding the await operator for the publish statement in your code.  That will prevent javascript from trying to send the next message before the first message's body is fully written to the socket.  E.g.,
for (let index = 0; index < 3; index++) {       await q.publish(data).catch(console.error);  }

Try adding the await operator for the publish statement in your code. That will prevent javascript from trying to send the next message before the first message's body is fully written to the socket. E.g., for (let index = 0; index < 3; index++) { await q.publish(data).catch(console.error); }

That's done on purpose to provoke the error. This error only happens when we load test the whole system, and the code I presented is just a simplification to provoke the same thing. With the await it works, however I tried to not include async sending from multiple clients to simulate the load testing that we do, just to keep the example project small. The data is also just mock data to fill around the same as the production data that is logged during the crash. Just as a note, in the production code we are awaiting the sends
                                const encrypted = encrypt(data);
				const buffer = Buffer.from(encrypted);
				await channel.basicPublish("", message?.properties.replyTo ?? "", buffer, publishOptions);

I'll just note that I can still reproduce with amqp-client.js v3.0.0 (on both RabbitMQ 3.9.16 used in the example here and RabbitMQ 3.12.1).

We observed the same issue in prod where we were writing around 140 messages/second. The ingress rate at exchange was around 70 messages/second before we observed the crashes.
Currently we are planning to use multiple channels (say n) for writes, and a channel for each consumer.
While writing a message to the exchange, we plan to use a semaphore1 and round robin the channel and do the basicPublish.
We observed that with n channels, n+1 messages without await are sufficient to bring this error message up. In production, although we use await on a single channel, I'm not sure why this behaviour is happening. Maybe it is due to concurrency introduced by the promises at the scale?

A publish involves sending multiple different frames, the BasicPublish method frame, the Headers frame and then 0 or more body frames. These frames all have to be sent together or else RabbitMQ will freak out (kind of defeats the purpose of multiplexing but anyway). We await sending each frame in Channel#basicPublish, being good citizens, but if the user isn't using await everywhere they can inject frames from other channels between the basicPublish frames.
One way I guess, if user's won't or can't await is that this library won't either, or just await the last sent frame. NodeJS will continue to buffer data internally until the socket is drained (increasing memory usage, until the application crashes): https://nodejs.org/api/stream.html#writablewritechunk-encoding-callback

Hi @carlhoerberg
If I understand the clarification of the original issue, the problem occurs during a load test with multiple clients. I imagine the poster means multiple HTTP clients were hitting their application during the test, which in turn published messages to RabbitMQ. The application under test correctly used await but still encountered the problem. The demo application deliberately missed await for the purpose of demonstrating this issue.

Right, I think the PR #123 should solve for that.

Thank you Carl for the quick turnaround! Will test the PR and let you know!

authors: 2joocy carlhoerberg chadknutson cressie176 dentarg vinayakakv


text:
Changed CookieInterceptor to use CookieManager

What
Changed CookieInterceptor to use java.net.CookieManager
How
The previous CookieInterceptor code failed to account for the possibility of multiple Set-Cookie headers being present in a response. It also failed to account for the possibility of multiple cookie values within a single header. Finally and most obviously from #287 it failed to check that the string parsing it was doing was safe. To avoid having to write code for all these scenarios it seemed preferable to use the java.net.CookieManager instead, which should be spec compliant.

Removed our existing cookie/header parsing and used an instance of java.net.CookieManager instead.
Refactored methods and error handling to work with CookieManager changes.
Made the shouldAttemptCookieRequest atomic as it is potentially accessed by multiple HttpConnection instances.

Testing
Added tests:

HttpTest#badCredsDisablesCookie - to check that a 401 when requesting a
cookie stops any further attempts.
HttpTest#cookieAppliedToDifferentURL - to validate that the cookie is
successfully applied to a different request URL.

Updated the OK_COOKIE to better match CouchDB.
Fixed assertions impacted by cookie change (optional " not present in a CookieManager handled cookie).
Issues
Fixes #287

Reviewers can hold off on this for a little while I investigate the CI hang on Java 1.7.

@rhyshort @tomblench the tests are passing on this now, but as well as changing the tests I added some more logging so might be worth another look

+1

+1

authors: rhyshort ricellis tomblench

repo: cloudant/java-cloudant


text:
Add updateOneFieldIndexMultithreaded test

What: Check that a non-trivial number of threads (currently 20) can concurrently create documents and update the query index for those documents
Why: Previous threading implementations of our database access layer were prone to error or deadlock when accessed by non-trivial numbers of threads
Testing: Add new updateOneFieldIndexMultithreaded test to check the above

reviewers: @ricellis @brynh
FB ticket 34396

+1

Just an observation - this PR mentions 20 threads, but the code uses 8. However, that doesn't appear to materially affect the test.

+1

authors: brynh ricellis tomblench

repo: cloudant/sync-android


text:
🛑 cbn.id is down

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

HTTP code: 0
Response time: 0 ms

Resolved: cbn.id is back up in 87ca76a.

repo: cloudbip/upptime


text:
🛑 citrahost.com is down

In efd161a, citrahost.com (https://citrahost.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: citrahost.com is back up in da6117b.


text:
🛑 cbn.id is down

In 34cdd12, cbn.id (https://cbn.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cbn.id is back up in a9754fa.


text:
🛑 my.domainesia.com is down

In 1ea1fce, my.domainesia.com (https://my.domainesia.com) was down:

HTTP code: 403
Response time: 84 ms

Resolved: my.domainesia.com is back up in 6e8d450 after 24 minutes.


text:
🛑 member.jagoanhosting.com is down

In 1d2db2e, member.jagoanhosting.com (https://member.jagoanhosting.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: member.jagoanhosting.com is back up in b46b961.


text:
🛑 rumahweb.com is down

In 2f3e61c, rumahweb.com (https://rumahweb.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: rumahweb.com is back up in 1fb5f74.


text:
🛑 hostinger.co.id is down

In ab59f70, hostinger.co.id (https://hostinger.co.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: hostinger.co.id is back up in cb82668.


text:
Exclude jackson-databind from shaded jar

Exclude jackson-databind from shaded .jar as it clashes with Spark's version in Cloudera Runtime 7.1.x. Looking at the dependency tree Spark includes jackson-databind:2.6.5 whereas Envelope 0.7.2 is including jackson-databind:2.3.1 as part of a kitesdk dependency.

Spark throws this exception when both versions of the jar are on the classpath:
Caused by: java.lang.NoSuchMethodError: com.fasterxml.jackson.databind.ObjectMapper.readerFor(Ljava/lang/Class;)Lcom/fasterxml/jackson/databind/ObjectReader;
	at org.apache.hadoop.hive.common.StatsSetupConst$ColumnStatsAccurate.<clinit>(StatsSetupConst.java:176)
	at org.apache.hadoop.hive.common.StatsSetupConst.parseStatsAcc(StatsSetupConst.java:353)
	at org.apache.hadoop.hive.common.StatsSetupConst.setBasicStatsState(StatsSetupConst.java:241)
	at org.apache.hadoop.hive.common.StatsSetupConst.setStatsStateForCreateTable(StatsSetupConst.java:345)
	at org.apache.hadoop.hive.ql.metadata.Hive.loadPartitionInternal(Hive.java:2443)
	at org.apache.hadoop.hive.ql.metadata.Hive.lambda$loadDynamicPartitions$4(Hive.java:2909)
	... 4 more

repo: cloudera-labs/envelope


text:
Cannot install Magento 2.1.4 with plugin enabled

With the cloudflare magento plugin required, a fresh installation of Magento 2.1.4 fails.
Error message: (vagrant/puppet encoded)
==> default: Notice: /Stage[main]/Magento/Exec[Install Magento]/returns: Running schema recurring...PHP Fatal error:  Uncaught Error: Cannot instantiate interface CF\Integration\IntegrationInterface in /var/www/Magento/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php:73
==> default: Notice: /Stage[main]/Magento/Exec[Install Magento]/returns: Stack trace:
==> default: Notice: /Stage[main]/Magento/Exec[Install Magento]/returns: #0 /var/www/Magento/vendor/magento/framework/ObjectManager/ObjectManager.php(71): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create('CF\\Integration\\...')
==> default: Notice: /Stage[main]/Magento/Exec[Install Magento]/returns: #1 /var/www/Magento/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php(126): Magento\Framework\ObjectManager\ObjectManager->get('CF\\Integration\\...')
==> default: Notice: /Stage[main]/Magento/Exec[Install Magento]/returns: #2 /var/www/Magento/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php(53): Magento\Framework\ObjectManager\Factory\AbstractFactory->resolveArgument(Array, 'CF\\Integration\\...', NULL, 'integration', 'CloudFlare\\Plug...')
==> default: Notice: /Stage[main]/Magento/Exec[Install Magento]/returns: #3 /var/www/Magento/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php(82): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->_resolveArguments('CloudFlare\\Plug...', Array, Array)
==> default: Notice: /Stage[main]/Magento/Exec[Install Magento]/returns: #4 /var/www/Magento/vendor/magento/framework/Obj in /var/www/Magento/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php on line 73

Hi,
Are you in development or production mode?
What bin/magento commands did you run beforehand?

So this is happening as part of our deployment process.  So no Magento commands have been run, there's no var files, etc.
The error occurs during a setup:install.
MariaDB 10, PHP 5.6
It was also occurring during a setup:upgrade on the server, but that's harder to get a good reproducible case for.

I think this is a dupe or at least related to https://github.com/cloudflare/Cloudflare-Magento/issues/34
I'm looking into these issues next week.  I'll leave this open and update when I know more.
I'm able to reproduce though.

I'm having this same issue as well. I can't get cloudflare to work with magento 2.1.4

Fixed in https://github.com/cloudflare/Cloudflare-Magento/pull/47
Can you upgrade to 1.1.1 and let me know if this is resolved please?

authors: jwineman navarr ooples

repo: cloudflare/Cloudflare-Magento


text:
1abbdbeff610417b46f4a7b47c477adfb451a

Expected Behavior
Link to the documentation or explain the expected outcome of following the documentation.
Actual Behavior
Explain what actually happens when you follow the documentation.
Section that requires update
Provide a link to the page that needs an update and be specific about which section requires the update.
Additional information
Any other details or screenshots you think are relevant.

1abbdbeff610417b46f4a7b47c477adfb451a

repo: cloudflare/cloudflare-docs


text:
workers: add Module Worker mention/snippets to FetchEvent

Merges the FetchEvent Lifecycle page with the FetchEvent API page. The content was hugely duplicative and IMO there was no point in having them separate, especially now with two Worker formats to document.
Sibling to #1790
Separately, I think both these Runtime API pages need to be renamed/relocated. With the addition of Module Worker syntax, we're no longer (consistently) talking about/dealing with FetchEvents and ScheduledEvents. We should discuss

Closes #1564

@signalnerve We'll need a lilredirector entry for the lifecycle page to the new section. Not sure how to do that

This is ready to merge now pending @signalnerve for a lilredirector entry & for synchronization with #1790


text:
New detection and announcing 2 new detection

New detection and announcing 2 new detection

FYI: I will soon re-format all these HTML code blocks using prettier... There's an almost-ready PR with these changes:
https://github.com/cloudflare/cloudflare-docs/pull/3734

authors: pedrosousa unknownhad


text:
taskprov: Ensure the task ID matches the advertised config

Closes #710.
Add a unit test that ensures
TaskprovAdvertisement::parse_taskprov_advertisement() fails if the task ID doesn't match the advertised task config. Along the way, adjust some variable names to make the code easier to read.

Took Mendes' suggestion, rebased, and squashed.

repo: cloudflare/daphne


text:
Add missing docs for admin override

Add missing schema examples for disable_for_time admin override feature for WARP clients.
Strangely, previously merged docs for this feature do not appear in the Terraform Registry. Wondering if this is possibly due the field not being present in the schema example?

i suspect this was caught up in the rename of the ZT resources. worth calling out here, this won't change the examples for cloudflare_teams_account given you're only modifying the newer resource.

i suspect this was caught up in the rename of the ZT resources. worth calling out here, this won't change the examples for cloudflare_teams_account given you're only modifying the newer resource.

What do I need to do to get the cloudflare_teams_account example updated?

it will go in https://github.com/cloudflare/terraform-provider-cloudflare/blob/master/examples/resources/cloudflare_teams_account/resource.tf however, it looks like that already has the key. perhaps the confusion here was new vs old resource?

authors: da-cf jacobbednarz


text:
C3: next templates refactoring

This PR aligns the Next.js template code with the rest of the C3 templates by removing its templates.ts file and
including template files directly in the next template directory
In order to properly implement the above also it was needed to extend the C3 config logic to support custom template variants (not only js and ts) and also allow the possibility to specify a custom destination directory for the template files to copy

for posterity: there are existing tests that cover this code that did not need modification because this is only refactoring 👍

authors: dario-piotrowicz lrapoport-cf

repo: cloudflare/workers-sdk


text:
clean up manifest generation, and a couple other things

This mostly introduces the following changes to manifest-generation

the bottom part of config-from-cf-internal.yml is only responsible for pulling data from the CF manifest, and defaults to nil if and only if it's possible for that data is not provided in the CF manifest.
the top part of config-from-cf-internal.yml transforms the extracted data into data diego's manifest needs
config-from-cf.yml is now only for masking off unneeded values from config-from-cf-internal
diego.yml now only directly consumes values from the result of config-from-cf.yml, and does do any more transformation, with the sole exception of the deployment name being the CF name plus "-diego".

Additionally, this:

deletes the unused etcd.machines property
adds the consul.datacenter property
removes stubs-for-cf-release/enable_consul_with_cf.yml which has long been redundant

I tried to validate this by generating a BOSH-Lite diego manifest before and after the changes, the only difference was the addition of the consul.datacenter: null value, as expected.  I didn't try it against other environments (ketchup, A1, etc.) but that would be easy enough to do.
NB: This builds on cloudfoundry-incubator/diego-release#97, please make sure @cholick gets credit for the idea via the git committer/author should you decide to merge this PR.

Merged as of fc7b3ac0bcb515e38982d0046fae35bf2efb0cd4.

repo: cloudfoundry-incubator/diego-release


text:
fix: chart: _config.tpl: fix comments

Description
We accidentally made the templates emit things instead of commenting things out (because we broke the helm templating markers).  This has no actual effect, as the helper outputs are discarded.
Motivation and Context
Encountered while doing #629
How Has This Been Tested?
Rendered helm chart, and diffed before & after outputs.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My code has security implications.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

This is duplicating https://github.com/cloudfoundry-incubator/kubecf/pull/1258/commits/f75c7dcaedb42d0a643b6a7ce5c74ecc43c67106
I would prefer to close the extra PR instead of spending a full CI cycle on basically comment changes, but will let you decide...

Closing PR because, no, I don't really need it here; I just happened to be in the area and made a commit locally, and didn't realize it was already being fixed elsewhere.
(Was rebasing my local branch into a bunch of topic-specific PRs for ease of review.)

authors: jandubois mook-as

repo: cloudfoundry-incubator/kubecf


text:
New routes can sometimes fail to show in routes table

We request new routes after a route has been created. The response can sometimes be missing the new route. Need to wait for success... or work around failure of sync call

Noticed something funny, could be related. Looks like delete by row is different to delete by multie select (row missed recursive and async params in call)

Need to look at this once #1811 is resolved

Can not reproduce

authors: nwmac richard-cox

repo: cloudfoundry-incubator/stratos


text:
openstack cpi should wait for the server to be deleted

In the patch, we added the following things:

wait_resource call when destroying the vm instance
log error messages during deleting the vm instance
one new unit test for the code changes

[#95584442]
Signed-off-by: Zhang Hua zhuadl@cn.ibm.com

updated the PR based on @cppforlife 's comments

@xingzhou we merged PR with small refactor here: https://github.com/cloudfoundry/bosh/commit/e0e1e05e780021affbcc115c73a6bfdcaa65455d
Please note, when doing PRs they need to be done against develop branch, not master.
Thanks.

authors: mariash xingzhou

repo: cloudfoundry/bosh


text:
[Bug]: CFApp finalizer will never be removed if a related domain is deleted

What happened?
When replacing deletion of subnamespace anchors with a call to the delete org API endpoint, we noticed that some test code was causing the org namespaces to never be deleted. This turned out to be due to the finalizer on CFApp.
The code was as follows:
AfterEach(func() {
    deleteOrg(orgGUID)
    deleteDomain(domainGUID)
})

The test had created a CFApp, and it was including in the destinations for a CFRoute pointing to a domain with the domainGUID above.
Since the API call to delete an org is async (relying on polling a job afterwards for completion which is not implemented), the delete domain code might run before all contents of the org's spaces have been removed. The org deletion eventually cascades to the space's namespace deletion. K8s attempts to remove all namespace resources which triggers the CFApp deletion. Finally, that triggers the CFApp finalizer code which attempts to update related routes by removing the app from the route's destination list. But the route's validation webhook fails because the domain cannot be looked up. So the finalizer can never be removed from the CFApp, and this blocks the namespace deletion.
Note that this code only alerted us to this issue. Making deleteOrg() synchronous here would only fix the test not the underlying problem.
What you expected to happen
Either the CFRoute validation webhook should deal gracefully with CFDomain deletion, or the CFApp finalizer should be able to cope with such a permanent error. Or maybe both.
Acceptance Criteria
GIVEN a CFDomain
AND a CFRoute associated with that domain
AND a CFApp with a destination on that route
WHEN I delete the domain and then delete the app
THEN I see the app is successfully deleted
How to reproduce it (as minimally and precisely as possible)
# deploy CF locally on kind
cd ~/workspace/cf-k8s-controllers
./scripts/deploy-on-kind.sh -l -d cf-env
./scripts/create-new-user.sh cf-admin

# create a domain
cat <<EOF | kubectl apply -f-
apiVersion: networking.cloudfoundry.org/v1alpha1
kind: CFDomain
metadata:
  name: bd67e962-0ded-4ba6-beb3-e5d6e3ed490f
  namespace: cf
spec:
  name: example.com
EOF

# login using the CF CLI
cf api https://localhost --skip-ssl-validation
cf login # and select the cf-admin entry from the list

# create and target and org and space
cf create-org org1
cf create-space -o org1 space1
cf target -o org1

# create a route
cf create-route example.com --hostname foo

# create an app and add it to the route's destinations
cf create-app app1
cf map-route app1 example.com --hostname foo

# delete the domain
kubectl delete -n cf cfdomain bd67e962-0ded-4ba6-beb3-e5d6e3ed490f

# attempt to delete the app
cf delete app1

Use k9s or kubectl to see the app is not deleted. There will be a log entry in the controllers pod saying 'failed to patch cfRoute to remove a destination'.
You can also try cf delete-org org1. This will leave the org and space namespaces in the terminating state as the app cannot be deleted from the space.
Anything else we need to know?
No response
Environment
Revision of codebase: main branch: fdbd22206cfa6ac7108565fb9a3ad60c231545dd
Kubernetes version (use kubectl version):
Cloud provider or hardware configuration:
Others:

⚠ We have decided to solve this by masking the CFApp finalizer more tolerant for now. Once we implement domain deletion, we will take care of deleting related routes and that should make it impossible for this to occur.

We thought we could do this by setting an owner ref on the CFRoute to the CFDomain. However, since the domain is generally in the root CF namespace, and the route is not, the rule that owner refs cannot be across namespace breaks this idea.
It looks like we will have to delete routes in the domain finalizer instead.

authors: gcapizzi kieron-dev


text:
Assert trusted-certs property value is a string

Supplying a different type, such as an array of strings, causes job-template rendering to fail at the start of the deploy, before updating any BOSH VM instances.
Also, improve setup job spec with property description and example.

Thanks @dgodd !


text:
As a Korifi API user I want to be able to apply admin service plan visibility

As a Korifi API user I want to be able to apply admin service plan visibility
GIVEN I have enabled the experimental managed services flag in the helm values
WHEN I have created service brokers
WHEN I POST /v3/service_plans/:guid/visibility with parameters type=admin
THEN I get a 200 OK response containing the updated service plan visibility with type set to admin
WHEN I get the updated service plan visibility
THEN I see the visibility has been updated to admin and organizations cleared
Dev notes:

Managed services proposal
Apply service plan visibility docs

It seems we have already implemented this with one of the previous visibility stories. Closing

repo: cloudfoundry/korifi


text:
log-cache-cf-auth-proxy crashing frequently due to concurrent map writes

On Log Cache 2.1.10, log-cache-cf-auth-proxy is frequently crashing with the following error:
fatal error: concurrent map writes
goroutine 177475 [running]:
runtime.throw(0xa674cf, 0x15)
	/var/vcap/data/packages/golang1.13.1/93e1c490dc284ac05cfb026cb706a074fa4a46f3/src/runtime/panic.go:774 +0x72 fp=0xc000281600 sp=0xc0002815d0 pc=0x430bd2
runtime.mapassign_faststr(0x996b60, 0xc00008da10, 0xc000305100, 0x645, 0x8)
	/var/vcap/data/packages/golang1.13.1/93e1c490dc284ac05cfb026cb706a074fa4a46f3/src/runtime/map_faststr.go:291 +0x3fe fp=0xc000281668 sp=0xc000281600 pc=0x414cde
code.cloudfoundry.org/log-cache/internal/auth.(*UAAClient).Read(0xc00009e460, 0xc000305100, 0x645, 0xc000305100, 0x0, 0x0, 0x0, 0x0)
	/var/vcap/packages/log-cache-cf-auth-proxy/src/code.cloudfoundry.org/log-cache/internal/auth/uaa_client.go:107 +0x911 fp=0xc0002819a0 sp=0xc000281668 pc=0x8fd841
code.cloudfoundry.org/log-cache/internal/auth.CFAuthMiddlewareProvider.Middleware.func1(0xb2c9a0, 0xc0001f40e0, 0xc0001b4300)
	/var/vcap/packages/log-cache-cf-auth-proxy/src/code.cloudfoundry.org/log-cache/internal/auth/cf_auth_middleware.go:88 +0xf0 fp=0xc000281a28 sp=0xc0002819a0 pc=0x8fe380
net/http.HandlerFunc.ServeHTTP(0xc00000f8a0, 0xb2c9a0, 0xc0001f40e0, 0xc0001b4300)
	/var/vcap/data/packages/golang1.13.1/93e1c490dc284ac05cfb026cb706a074fa4a46f3/src/net/http/server.go:2007 +0x44 fp=0xc000281a50 sp=0xc000281a28 pc=0x6e8094
github.com/gorilla/mux.(*Router).ServeHTTP(0xc0001d40e0, 0xb2c9a0, 0xc0001f40e0, 0xc0001b4300)
	/var/vcap/packages/log-cache-cf-auth-proxy/src/github.com/gorilla/mux/mux.go:159 +0x104 fp=0xc000281bb8 sp=0xc000281a50 pc=0x86e5c4
code.cloudfoundry.org/log-cache/internal/auth.(*AccessHandler).ServeHTTP(0xc000068680, 0xb2c9a0, 0xc0001f40e0, 0xc000216300)
	/var/vcap/packages/log-cache-cf-auth-proxy/src/code.cloudfoundry.org/log-cache/internal/auth/access_middleware.go:48 +0xf6 fp=0xc000281c18 sp=0xc000281bb8 pc=0x8fa0a6
net/http.serverHandler.ServeHTTP(0xc0001d61c0, 0xb2c9a0, 0xc0001f40e0, 0xc000216300)
	/var/vcap/data/packages/golang1.13.1/93e1c490dc284ac05cfb026cb706a074fa4a46f3/src/net/http/server.go:2802 +0xa4 fp=0xc000281c48 sp=0xc000281c18 pc=0x6eb4e4
net/http.(*conn).serve(0xc0002c8320, 0xb2e120, 0xc000104700)
	/var/vcap/data/packages/golang1.13.1/93e1c490dc284ac05cfb026cb706a074fa4a46f3/src/net/http/server.go:1890 +0x875 fp=0xc000281fc8 sp=0xc000281c48 pc=0x6e6e85
runtime.goexit()
	/var/vcap/data/packages/golang1.13.1/93e1c490dc284ac05cfb026cb706a074fa4a46f3/src/runtime/asm_amd64.s:1357 +0x1 fp=0xc000281fd0 sp=0xc000281fc8 pc=0x45faf1
created by net/http.(*Server).Serve
	/var/vcap/data/packages/golang1.13.1/93e1c490dc284ac05cfb026cb706a074fa4a46f3/src/net/http/server.go:2927 +0x38e

For context, @mma-pivotal 's loggr-forwarder-agent crash is https://github.com/cloudfoundry/loggregator-agent-release/issues/26 .
This issue should be fixed in https://github.com/cloudfoundry/log-cache-release/commit/c3339a997eeceb14ffc1cb3dd2080010b74f8137 , released in log-cache v2.1.13.

repo: cloudfoundry/log-cache-release


text:
Startup scripts silently fail if DB password include a '$'

If you include a password containing a '$' under databases.roles, the postgres job will report as running but the DB won't have a password set. In /var/vcap/sys/log/postgres/postgres_ctl.err.log I see:
[2017-08-18 20:46:02+0000] + echo 'Setting password for role cloud_controller...'
[2017-08-18 20:46:02+0000] /var/vcap/jobs/postgres/bin/postgres_start.sh: line 81: $6: unbound variable

My cloud_controller DB password does have a '...$6...' in the middle. Looks like this line is not doing any escaping so special characters get expanded. On CAPI we usually use Ruby's Shellwords.shellescape in our ERB templates around passwords.
Also a big +1 on this comment around failing the job if setting the roles fails: https://github.com/cloudfoundry/postgres-release/blob/865224b83361d58e8a5bbef77ccee48429feae45/jobs/postgres/templates/postgres_ctl.erb#L31-L37. Would have been much easier to debug if the postgres job failing immediately rather than silently erroring.

@ljfranklin
Thanks for reporting this issue. We have opened a separate story to have the postgres job to fail when a query fails.
For the empty password issue, we have fixed it as suggested and you will find the fix in the next release.

The empty password issue has been fixed in v21.

authors: ljfranklin valeriap

repo: cloudfoundry/postgres-release


text:
CldUploadButton:onUpload={(result: any) => onChange(result.info.secure_url)} Error

it not working in the latest package of "next-cloudinary": "~6.11.0"

can any body help me

@princekumarg is it actually not working or are you referring to the line? it's a deprecated method but it should still work as of now
id recommend the onSuccess callback instead

Now it's working on using onSuccess

fantastic!

authors: colbyfayock princekumarg

repo: cloudinary-community/next-cloudinary


text:
chore: align the annotation reconcilePodSpec support function

This patch make the reconcilePodSpec supports both both
cluster and pooler, and update doc accordingly.
Closes: #5068

LGTM

/test d=push tl=4

authors: gabriele-wolfox litaocdl mnencia

repo: cloudnative-pg/cloudnative-pg


text:
fix(roles): properly quote inRoles in SQL statements

This patch fixes an issue where the inRoles parameter was not properly quoted in SQL statements, which could cause syntax errors if the role name contains special characters.
Closes #6337
Release notes
Properly quote inRoles in SQL statements to prevent potential syntax errors in the generated SQL.

@mnencia @gabriele-wolfox this is only for 1.24 right? 1.22 and 1.23 shouldn't be having this PR ?

Declarative role management has been introduced in 1.20, so it needs to be backported to all the branches.

I started a few E2e runs on this:
STATUS  TITLE              WORKFLOW           BRANCH        EVENT              ID           ELAPSED   AGE
*       continuous-del...  continuous-del...  dev/cnp-5756  workflow_dispatch  12410155110  7s        less than a mi...
*       continuous-del...  continuous-del...  dev/cnp-5756  workflow_dispatch  12410154776  8s        less than a mi...
*       continuous-del...  continuous-del...  dev/cnp-5756  workflow_dispatch  12410154394  10s       less than a mi...
* ```
*

https://github.com/EnterpriseDB/cloudnative-pg/actions/runs/12415238247
https://github.com/EnterpriseDB/cloudnative-pg/actions/runs/12415243728

/ok-to-merge green E2E

authors: gabriele-wolfox leonardoce mnencia


text:
feat: instancetype implement UpdateInstanceTypes and UpdateInstanceTypeOfferings

What type of PR is this?

/kind feature
What this PR does / why we need it:
instancetype implement UpdateInstanceTypes and UpdateInstanceTypeOfferings
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?

cc @daimaxiaxie @IrisIris
Please take a look

How to think about unit testing. AWS has implemented fake API(interface), but it seems difficult for Ali to do so.

How to think about unit testing. AWS has implemented fake API(interface), but it seems difficult for Ali to do so.

For now, our main focus is to finish building the minimum usable version.
We'll come back to the fakeapi implementation later, but that doesn't mean unit testing isn't important, it is. Can you create an issue tracker for this?

For now, our main focus is to finish building the minimum usable version.

I agree with this suggestion.

/lgtm

authors: daimaxiaxie helen-frank jwcesign


text:
[Feature Request]: Implementation for FileUpload component

Description
Docs describe a file upload component but it appears this component is not directly available in the library. File upload is non-trivial to implement and the documented example for multiple file upload does not appear to be replicable externally since TokenGroup does not allow for components within Tokens.
Since file uploaders are a common need and consumers currently require additional effort to implement them, I think it would be great if we could have a FileUpload implementation directly available in the library that follows the specification described in the docs.
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate requests

Hey Jason,
thank you for reaching out. That's correct! The systems describes the user experience on the website, but it does not provide an implementation as part of the library. We are aware of this feature request, but we don't currently have short-term plans to work on it. For now, you can get around by creating your own adjacent component using a button and a custom file list implementation.
We will use this issue to track interest in having a FileUpload implementation.
Thank you,
Florian

Given the commonality of this feature, its absence could be a blocker for adoption for us. Love the ease-of-use of the existing components though!

Agreed, was really excited to see how clean the file upload example was only to find out it wasn't actually part of the components. In the short term, if the image in the example was generated and not just a mock, would it be possible to paste the source code here?

@FlorianDr Any updates on this request?  My team was really excited to use this.

Hello!
There are no particular plans for this request. It stays here for visibility, but not prioritised in any way
P.S. Best is not to ping individual people, because they may change their projects. Just leave a comment and our team will be notified regardless.

FWIW, I've been working on a file uploader implementation if anyone is interested: https://github.com/jasmaa/cloudscape-file-uploader

Hello!
Cloudscape team is working on implementing the file upload component, please bear with us!

authors: FlorianDr XTEKiyZRLr8UsiQN jasmaa jeffshep jjdirvin just-boris pan-kot

repo: cloudscape-design/components


text:
chore: Use focus-visible from component-toolkit

Description
Use the newly-added focus-visible hook and styling from component-toolkit package
Related links, issue #, if available: n/a
How has this been tested?
Tested in dev pipelines

Review checklist
The following items are to be evaluated by the author(s) and the reviewer(s).
Correctness

Changes include appropriate documentation updates.
Changes are backward-compatible if not indicated, see CONTRIBUTING.md.
Changes do not include unsupported browser features, see CONTRIBUTING.md.
Changes were manually tested for accessibility, see accessibility guidelines.

Security

If the code handles URLs: all URLs are validated through the checkSafeUrl function.

Testing

Changes are covered with new/existing unit tests?
Changes are covered with new/existing integration tests?

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

fwiw - upgrading to 3.0.685 started causing issues in my build/test due to the resolved version being @cloudscape-design/component-toolkit@npm:1.0.0-beta.51, which if I had to guess doesn't contain the useFocusVisible hook yet.
the fix for me was to make sure I was pointing to the latest @cloudscape-design/component-toolkit
e.g.
yarn set resolution @cloudscape-design/component-toolkit@npm:^1.0.0-beta npm:1.0.0-beta.58

authors: gethinwebster virtuoushub


text:
UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v4.19.195",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=50316635e644a0b9e62d3263fb4e8be2104605b6"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "50316635e644a0b9e62d3263fb4e8be2104605b6",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "wq: handle VM suspension in stall detection\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v4.19.195 by commit 50316635e644a0b9e62d3263fb4e8be2104605b6. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1000870

repo: cloudsecurityalliance/security-database


text:
removed unique from column def

Fixes #105
Removed the unique attribute from columns and kept it as a constraint everywhere

[x] Tests pass
[x] Appropriate changes to README are included in PR

@agasheesh @nevinheintze - please review

repo: cloudspannerecosystem/harbourbridge


text:
Implement Tests to Restart Servers During Balance and RawTransactions Reads to Verify Raft Request Distribution

Why
Testing the system’s behavior during server restarts is crucial to ensure that requests are properly distributed and handled by the Raft consensus algorithm. This helps in verifying the system’s fault tolerance and robustness.
How

Read Balance and RawTransactions Test:

Implement tests to read account balances and raw transactions while the system is under load.

Server Restart Scenario:

Implement a test that restarts one or more servers during the read operations.
Ensure that the Raft consensus algorithm properly distributes the requests to other available servers.

Verify Request Handling:

Verify that the restarted servers correctly rejoin the Raft cluster and resume handling requests without data loss or corruption.

Test Suite Integration:

Integrate these tests into the existing test suite to run automatically.
Ensure the tests cover various scenarios, including partial and full cluster restarts.

We've shelved raft for now, closing.

authors: carneiro-cw renancloudwalk

repo: cloudwalk/stratus


text:
[QUESTION] - How to set different Read Timeout for http handlers and websocket handler

Describe the Question
By default hertz has 3 minutes of Read timeout which is fine. But I wanted to disable ReadTimeout for Websocket handler. Currently the websocket connection auto close with error Error connection read timeout.
Is it possible to disable or increase the Read Timeout for websocket handler.

https://www.cloudwego.io/zh/docs/hertz/tutorials/basic-feature/protocol/websocket/#setreadtimeoutsetwritetimeout

authors: li-jin-gou sujit-baniya

repo: cloudwego/hertz


text:
支持自定义 annotations

Feature Request
Crates
pilota-build

Motivation
支持自定义 annotations 来支持在插件里通过不同的 annotations 来生成不同的代码

Proposal

Alternatives

目前 annotations 在 resolve 阶段只会保留 pilota-build 里指定的注解信息，要支持自定义 annotations 只需要把未指定的信息也保留下来即可，有兴趣提个 PR 直接实现一下吗？

authors: Millione boringplay

repo: cloudwego/pilota


text:
241-error-on-delete-metadata fixed.

I noticed that an error was thrown when deleting metadata. Metadata_In didn't have fields for extractor or extractor_info, adding those has fixed the error. Metadata can be deleted from dataset or file

@tcnichol I am reviewing this. Do I need to add any specific metadata for this to be tested?

No. The error came up on any metadata deletion, so any metadata would be fine.


text:
Adding better word cleaning for definitions and removing unnecessary log statements

We can squash these two commits into a single commit before merging.
The squash option can be enabled in repo settings: https://help.github.com/articles/configuring-pull-request-merge-squashing/

Thanks, @suheb--both of those are enabled on the repo.  Looks great!

authors: lukehollis suheb


text:
Rename this resource to “bloblang-keyval-resource”

Hi @cludden!
I'm the maintainer of the plain-content, file-based “keyval-resource” and as such , when I've seen your “keyval” resource recently in the Concourse Resource Types I've was very interested.
Turns out, your resource is very different from plain key-values, with the support for Bloblang documents.
Also, the key-values can only be created through params of the put: keyval steps. The original key-value resource aims at providing a file-based interface in artefact directories exposed to or filled from tasks executions.
In order to avoid any confusion in the Concourse community, would you accept renaming your resource bloblang-keyval-resource? This would help understand at first glance how it distinguishes from the “classical” keyval resources.
I'm available on Cloud Foundry Slack with my full name, if you need to reach out.
Always keen on chatting with other Concourse fans, hope to hear from you soon, thanks!

We could also reword a bit in there: resource-types/cludden-keyval-resource.yml if you' up to 🙂

repo: cludden/concourse-keyval-resource


text:
Add some tests to CI

These tests are using inputs largely based on CAT-23-001.

To get this merged without issues, I could remove the MarkovChainMC test for now.


text:
Implement parser edge case

This PR intents to fix issue #680 that peloton would crash with statements like "SELECT *" and "SELECT;"
The reason is that the Postgres parser does not think the statements mentioned above as wrong statements and the binder and optimizer would continue to execute the wrong parse tree and eventually crash.
The solution is to explicitly check that

The target list is not null, which can overcome "SELECT;"
The from clause list is not null when the target contains any variables 'like * or item column', this would overcome "SELECT *;"

A unit test case is added in parser_test to check "SELECT *" and "SELECT;".
There may still be other edge cases in 2 since right now only constant, bool expression and expression type are checked.

Coverage decreased (-0.004%) to 72.395% when pulling c14be277dc7ac8d1c780d052ccce136665990365 on ChTimTsubasa:parser into 7faab8dc6938f16861be3031965e2ccaa03fc669 on cmu-db:master.

Coverage increased (+0.005%) to 72.404% when pulling dcea176da6c1ed584df788673b551b1e8473df4b on ChTimTsubasa:parser into 7faab8dc6938f16861be3031965e2ccaa03fc669 on cmu-db:master.

Coverage increased (+0.01%) to 72.409% when pulling 9dae3e7c74215c9408a7217e0189c7c8c6f1590e on ChTimTsubasa:parser into 7faab8dc6938f16861be3031965e2ccaa03fc669 on cmu-db:master.

One of the four travis jobs is failed.
The test failed when running the script ../script/testing/psql/psql_test.sh. The line of error causing code is
at
peloton: /home/travis/build/cmu-db/peloton/src/index/bwtree_index.cpp:106: bool peloton::index::BWTreeIndex<KeyType, ValueType, KeyComparator, KeyEqualityChecker, KeyHashFunc, ValueEqualityChecker, ValueHashFunc>::CondInsertEntry(const peloton::storage::Tuple*, peloton::ItemPointer*, std::function<bool(const void*)>) [with KeyType = peloton::index::CompactIntsKey<1ul>; ValueType = peloton::ItemPointer*; KeyComparator = peloton::index::CompactIntsComparator<1ul>; KeyEqualityChecker = peloton::index::CompactIntsEqualityChecker<1ul>; KeyHashFunc = peloton::index::CompactIntsHasher<1ul>; ValueEqualityChecker = peloton::ItemPointerComparator; ValueHashFunc = peloton::ItemPointerHashFunc]: Assertion ret == true' failed.`
The full log is as following:
travis_time:start:0c6582f0
$ bash ../script/testing/psql/psql_test.sh
Exception Type :: Catalog
Message :: Table foo is not found
peloton: /home/travis/build/cmu-db/peloton/src/index/bwtree_index.cpp:106: bool peloton::index::BWTreeIndex<KeyType, ValueType, KeyComparator, KeyEqualityChecker, KeyHashFunc, ValueEqualityChecker, ValueHashFunc>::CondInsertEntry(const peloton::storage::Tuple*, peloton::ItemPointer*, std::function<bool(const void*)>) [with KeyType = peloton::index::CompactIntsKey<1ul>; ValueType = peloton::ItemPointer*; KeyComparator = peloton::index::CompactIntsComparator<1ul>; KeyEqualityChecker = peloton::index::CompactIntsEqualityChecker<1ul>; KeyHashFunc = peloton::index::CompactIntsHasher<1ul>; ValueEqualityChecker = peloton::ItemPointerComparator; ValueHashFunc = peloton::ItemPointerHashFunc]: Assertion `ret == true' failed.
../script/testing/psql/psql_test.sh: line 59: 15717 Aborted                 (core dumped) bin/peloton -port $PELOTON_PORT > /dev/null
***FAIL***

@apavlo
The line in the tests causing error was in an insert statement:
https://github.com/cmu-db/peloton/blob/master/script/testing/dml/basic2.sql#L48
Which caused peloton not passing the insertion:
https://github.com/cmu-db/peloton/blob/master/src/index/bwtree_index.cpp#L106
I tested again using the current master and it still failed on my computer. I am afaid this error is not related to this PR.

Coverage increased (+0.03%) to 72.346% when pulling 3bdc57feab6a65715d1c8dd5ae3793a2d06b9d67 on ChTimTsubasa:parser into 5891ee94fff561e07c38626702d8d5fa172ab0b3 on cmu-db:master.

Coverage increased (+0.01%) to 72.324% when pulling f0901cb25e7cd9aefc6e62f484895e1c474daafa on ChTimTsubasa:parser into c30cb3137b4aca4539d7681cec824f60a0789c55 on cmu-db:master.

@apavlo
Although this time the PR has passed, all I did was only rebase on top of current master. There are still bugs in BW tree, as mentioned in #730. Other PRs could still possibly fail due to the same problem.
I have tested manually with the basic1.sql.
Peloton still crashed when inserted the new tuples at
https://github.com/cmu-db/peloton/blob/master/script/testing/dml/basic1.sql#L51
This happens both for this PR and current master.
I

Coverage increased (+0.03%) to 72.354% when pulling 52a7e6b4797503487d4032450720e81f9ac2d11b on ChTimTsubasa:parser into 320226b0d1fad5088abec252049b763a676b1f86 on cmu-db:master.

authors: ChTimTsubasa coveralls

repo: cmu-db/peloton