Make GUI and deployment scripts use compiling service

This PR change the GUI, backend, and shell scripts under core/scripts to incorporate with the TexeraWorkflowCompilingService introduced in #2796
How to test this PR
To test with the user-sys enabled, set the user-sys.jwt.256-bit-secret to be a 256-bit string in application.conf.
For backend, launch 3 services

TexeraWebApplication
TexeraRunWorker
TexeraWorkflowCompilingService (runs at 8082)

For frontend, launch the GUI normally.
Core changes
1. GUI
WorkflowCompilingService is added
Workflow Compiling Service provides mainly 3 functionalities:

autocomplete attribute property of operators (previously done by the SchemaPropagationService)
receive static errors (previously done by sending EditingTimeCompilationRequest and saving in the ExecutionStateInfo)
manage PhysicalPlan

/core/gui/src/app/common/type/proto protoc-generated ts files are added
These files are generated and added based on proto files in /core/amber/src/main/protobuf. The main purpose is to correctly de-serialize the PhysicalPlan given by the WorkflowCompilingService
This service will talk to the TexeraWorkflowCompilingService in a certain debounce time when:

operator add, delete, property changed, disabled
link add, delete

SchemaPropagationService is removed.
Schema propagation feature now relies on the WorkflowCompilingService's endpoint to accomplish
EditingTimeCompilationRequest and OperatorReuseCacheStatusService are removed
The main purpose of EditingTimeCompilationRequest and OperatorReuseCacheStatusService is to report the static errors Now this relies on the WorkflowCompilingService to accomplish.
2. Backend
Some bugs in WorkflowCompilationResource are fixed
These bugs are found when frontend is actually using it. This PR fixes those issues.
EditingTimeCompilationRequest and its handler are removed
Now the compilation is done by TexeraWorkflowCompilingService.
SchemaPropagationResource is removed
Now the schema propagation is done by the TexeraWorkflowCompilingService.
3. scripts
workflow-compiling-service.sh is added
This script is mainly used to launch the TexeraWorkflowCompilingService.
Related build and deploy shell scripts are updated
These scripts are updated to include the launching and terminating of TexeraWorkflowCompilingService

close as we do need it any more


Server crash when connecting a pipe with extractor attachment to Create Mod Portable Storage

Describe the bug
When connecting a pipe it acts as expected, as soon as I place the extractor attachment on a pipe which is attached to a create mod portable storage block (on the stationary non moving side of the contraption) a server crash is caused. I have attached the crash report for you to consider.
Thanks
archive-2022-02-14T213459-0600.tar.gz
,
How can we reproduce this bug or crash?

place create mod portable storage block.
Place pipe
Place extractor attachment on pipe
SERVER CRASHED!

What Minecraft version is this happening on?
Minecraft 1.16.5
What Forge version is this happening on?
forge-1.16.5-36.2.22
What Refined Pipes version is this happening on?
Refined-Pipes-0.5.1
Relevant log output
Please see bug report attachment for server crash log

Can you link me just the crash report, preferably on Pastebin etc.
I don't feel comfortable opening random archives


Memcached: Cannot assign requested address

Hi,
I am getting this bug on my CentOS. I tries 1.5.0 to 1.5.3 but nothing solved. Its like memcached server going down for sometime on every X min. Please help me
Thank you
Apurba

I somehow missed this; you should try the mailing list for support help. this issue tracker is for software bugs.


fix: prevent infinite loop when a node's parent is the node itself

This also fixes issue #150

I can confirm this PR fixed this issue for me. For me, neovim was completely freezing when performing commands like cw or ci on certain keywords.


Auto derivation fails for base trait with no generic parameter

This compiles:
  import io.circe.syntax._
  import io.circe.generic.auto._

  sealed trait A[T]
  case class B[T](b: T) extends A[T]

  val b = B(1.0)
  println(b.asJson.noSpaces)
  val a: A[Double] = b
  println(a.asJson.noSpaces)

This fails:
  import io.circe.syntax._
  import io.circe.generic.auto._

  sealed trait A
  case class B[T](b: T) extends A

  val b = B(1.0)
  println(b.asJson.noSpaces)
  val a: A = b
  println(a.asJson.noSpaces) // does not compile

Why?

The issue is that you need to know at compile-time that all of the members of the case class can be encoded, so the following must not compile:
trait Nonsense
val a: A = B(new Nonsense {})
val encoded = a.asJson

But that A is exactly the same as the A in your second example.
It's worth noting that Shapeless doesn't provide a LabelledGeneric (or Generic) instance for your second A, either. Also, to be honest I'm a little surprised that your first example works (and in fact it doesn't seem to on 2.11). It's clearly fine, but I wouldn't expect the compiler / these macros to be able to figure that out.


[KOGITO-5449] Fix JandexProtoGenerator StackOverflow and ProtoGenerator refactor

https://issues.redhat.com/browse/KOGITO-5449
This PR fix a StackOverflowException in case of recursive types and also includes multiple refactoring/improvements to ProtoGenerator in general

Create a common test suite for both JandexProtoGenerator and ReflectionProtoGenerator
Fix enum different behaviour introduced by https://github.com/kiegroup/kogito-runtimes/pull/654
Fix different behaviour introduced by https://github.com/kiegroup/kogito-runtimes/pull/1468
Fix bug in package handling: top level types were using proto package instead of their own real packages
Unified proto generation to have a single common path: all public methods reach internalGenerate that is the only entry point
Moved to AbstractProtoGenerator some common logic (to be honest ~all the code in ReflectionProtoGeneratorandJandexProtoGeneratoris a duplication from a functional perspective but going deeper with common methods requires to "replace" all interaction withClass<?>andClassInfo` to common abstraction)

Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[ ] You have read the contributors guide
[ ] Your code is properly formatted according to this configuration
[ ] Pull Request title is properly formatted: KOGITO-XYZ Subject
[ ] Pull Request title contains the target branch if not targeting main: [0.9.x] KOGITO-XYZ Subject
[ ] Pull Request contains link to the JIRA issue
[ ] Pull Request contains link to any dependent or related Pull Request
[ ] Pull Request contains description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket

How to retest this PR or trigger a specific build:

Run all builds
Please add comment: Jenkins retest this

Run (or rerun) specific test(s)
Please add comment: Jenkins (re)run [runtimes|optaplanner|apps|examples] tests

Quarkus LTS checks
Please add comment: Jenkins run LTS

Run (or rerun) LTS specific test(s)
Please add comment: Jenkins (re)run [runtimes|optaplanner|apps|examples] LTS

Native checks
Please add comment: Jenkins run native

Run (or rerun) native specific test(s)
Please add comment: Jenkins (re)run [runtimes|optaplanner|apps|examples] native

Full Kogito testing (with cloud images and operator BDD testing)
Please add comment: Jenkins run BDD
This check should be used only if a big change is done as it takes time to run, need resources and one full BDD tests check can be done at a time ...

The (build) Examples check has failed. Please check the logs.

The (build) Apps check has failed. Please check the logs.

jenkins rerun apps
jenkins rerun examples

Jenkins rerun apps tests
Jenkins rerun examples tests

The (build) Apps check has failed. Please check the logs.

The (build) Examples check has failed. Please check the logs.

The (build) Examples check has failed. Please check the logs.

Jenkins rerun examples tests

The (build) Examples check has failed. Please check the logs.

Jenkins rerun examples tests

The (build) Examples check has failed. Please check the logs.

Jenkins rerun examples tests

jenkins please retest this


fix: image compiling

RM-10691

🧰 Changes
Fixes compiling images.
The problem was our naive transformer that could not handle non string attributes. For instance, using a false value would crash the compiler:
<Image border={false} />

This updates the toAttributes method to create the valid AST.
🧬 QA & Testing
Do the tests pass?
You could test it locally like:
npm i && npm run build
node
> const rmdx = require('./')
> rmdx.mdx(rmdx.mdast('<Image border={false} />'))

But that's roughly the same as the tests?

Broken on production.
Working in this PR app.

This PR was released!
🚀 Changes included in v7.4.2


[VS Code] Support custom LSP extensions for guests

I've been using cquery and it works quite well with live-share. cquery has a number of LSP extensions which would be handy to use as well (ie, call hierarchy, semantic highlighting, among others). Is it possible/planned to support arbitrary LSP protocol extensions?
Off topic: I'm also curious - are there any publicly accessible documents for how live-share integrates into vscode? Thanks for the great work!

This is definitely something we'd love to be able to support. Right now, Live Share "hooks" into the guest's language services by registering providers for the vsls scheme (which is what all documents use on the guest-side in a Live Share session. Unfortunately, I'm not aware of a way for us to register handlers for arbitrary custom LSP requests.

Thanks! I suspect the cquery extension can detect if it is in the vsls client by checking the document schema.
If you're willing to provide a mechanism for the cquery extension to run an arbitrary command against the language server for a given document, I'd be happy to make the relevant changes cquery-side.

let doc = vscode.window.activeTextEditor.document.uri;

// Request
let requestData = JSON.stringify({}); // arbitrary payload
let response = JSON.parse(await vscode.commands.executeCommand(
    'vsls.languageServerRequest', doc, requestData));

// Notification
let notificationData = JSON.stringify({}); // arbitrary payload
await vscode.commands.executeCommand(
    'vsls.languageServerNotification', doc, notificationData);

Then I can make the custom cquery client-side handlers understand vsls and make the right calls as needed.
Another option may be to build support directly into the languageserver package so this all happens transparently, but that may be a much trickier problem to solve.

@jacobdufault I spoke with @srivatsn about this, and we actually came to the exact same conclusions as you 😄
Modifying the vscode-languageserver-node package directly isn't completely ideal, since Live Share is (at least currently) still an extension. However, it's definitely our goal to make extensions "light up" as transparently as possible, so that's a compelling solution long-term.
Regarding your other proposal, we'd also need a way to route the custom LSP message back to the extension, on the the host-side, and then send the response back to the respective guest. Right now, we call VS Code commands on the host-side in order to query language data on behalf of the requesting guest. We'd need something similar for extensions. Maybe we could have a convention where the extension exposes an internal command (<EXTENSION_NAME>.customLspRequest), that we can attempt to call when receiving a custom LSP request.
We'll need to think about it a bit more, but I definitely think there's something there we could do here.

we'd also need a way to route the custom LSP message back to the extension, on the the host-side, and then send the response back to the respective guest.

One (simple) option here is to specify the name of the command in the request command, ie,
let uri = vscode.window.activeTextEditor.document.uri;
let notificationData = JSON.stringify({}); // arbitrary payload
vscode.commands.registerCommand('handlerId', (response: string) => {});
vscode.commands.executeCommand(
    'vsls.languageServerNotification', 'handlerId', uri, '$cquery/callTree', notificationData);

@jacobdufault Yeah, that could potentially work! I love that idea 😄

I'm going to close this for now since we haven't heard significant customer feedback for this. If this is something that folks would like to see us prioritize, please let us know by re-opening/commenting on this bug. Thanks!

I'm going to close this for now since we haven't heard significant customer feedback for this. If this is something that folks would like to see us prioritize, please let us know by re-opening/commenting on this bug. Thanks!

Hey, Several users of my VS Code language extension are actively asking for the live share support. The extension is built on top of an LSP server (https://github.com/OmniSharp/csharp-language-server-protocol). Some features work with live share (eg, tooltips), but others don't (eg, semantic highlighting). Do I understand correctly, that this issue is covering cases like that? If it does, I'd really like it if not prioritized, but at least remain  on the to-do list.

@Elringus , semantic highlighting is supported by the textDocument/references LSP request, right? If so, that should be supported by Live Share today.

@daytonellwanger I think it's textDocument/semanticTokens (https://microsoft.github.io/language-server-protocol/specifications/specification-3-16/#textDocument_semanticTokens)

@Elringus ah, I see. Does VS Code support that request? I know other IDEs do, but I thought VS Code operated exclusively off of language grammars for colorizaton.

It seems they do 😊. Thanks for letting me know!

VS Code doesn't currently support us querying semantic token providers (here's a list of what they currently support). We'd have to work with them to add that to the API before we could remote them over Live Share. @smvanderweide could you look into this?

@Elringus could you open a new issue to track this request? It's a little different than what this thread was asking for.

@daytonellwanger Done: https://github.com/MicrosoftDocs/live-share/issues/4024 Thanks for looking into this!

@Elringus thanks!


[Swap] Add identifier for ASGARDEX to swap memo

ASGDX ID: 999
Memo: SWAP:{ASSET}:{DESTADDR}:12341999 (slightly adjust limit to id 999)
Depends on #1105

Does it make sense to make this cahnge the part of asgardex-util package?

getSwapMemo has already all data we need to pass: { asset: Asset; address?: string; limit?: BaseAmount }. The identifier 999 will be the last three digits of limit. However, before we can add a slip limit to the memo, we do need to implement a slip limit protection #1105 (we don't have such protection in ASGDX right now)

july 16,2021
is there an issue with your swapping - since the calulations are way off .
did a swap in Asgardex from btc to rune / rune to btc  DID HAVE $3881.57 but after swapping around i now left with $226.40 .. see transaction below ( missing 3655.17 )
CHAOSNET
POOLS
WALLET
$ USD
ASSETS  SHARES  BONDS  HISTORY
DETAIL	DATE	DETAIL
SWAP
INᚱ 7.01576684⚡ 83,337OUT
07/14/2021 19:34
SWAP
INᚱ<PHONE_NUMBER>4₿ 0.12373175OUT
07/14/2021 19:16
SWAP
IN₿ 0.12543178ᚱ<PHONE_NUMBER>9OUT
07/14/2021 18:53
SWAP
INᚱ 6.67812181⚡ 108,871OUT
07/14/2021 16:48
SWAP
INᚱ<PHONE_NUMBER>9₿ 0.05892867OUT
07/14/2021 16:45
SWAP
IN₿ 0.08257076ᚱ<PHONE_NUMBER>OUT
06/15/2021 22:02
paddress
bc1q528rrkmhdhpdhqh0c4ll0nl3rjtx8txgjfa3kd
thor1lfe48vgxxmmmawrsuqe4hpak2qfaetvvsua9su
0x9c02679cca11ad94044083f9b9a161571acf5468
please contact me @ pantheons @ gmail.com

Why did you close this issue, when it’s not resolved yet !!
I still have not got my crypto amount corrected via $4847.868
In eth which you show only .605 crypto !
Please reply
Thxs
Rob
On Thu, Aug 5, 2021 at 9:07 AM veado @.***> wrote:

Closed #1615 https://github.com/thorchain/asgardex-electron/issues/1615
via #1650 https://github.com/thorchain/asgardex-electron/pull/1650.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/thorchain/asgardex-electron/issues/1615#event-5117381044,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUNORVGG6TYVJMGVEATWM53T3KEJDANCNFSM47637GXQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

Why did you close this issue, when it’s not resolved yet !! I still have not got my crypto amount corrected via $4847.868 In eth which you show only .605 crypto ! Please reply Thxs Rob

Pls note: This issue here (#1615) has nothing to do with #1636, which is still open. You got an info about closing this issue here just because you have added a duplicated message ^ before.

O ok, thxs
On Sat, Aug 7, 2021 at 10:44 AM veado @.***> wrote:

Why did you close this issue, when it’s not resolved yet !! I still have
not got my crypto amount corrected via $4847.868 In eth which you show only
.605 crypto ! Please reply Thxs Rob
Pls note: This issue here (#1615
https://github.com/thorchain/asgardex-electron/issues/1615) has nothing
to do with #1636
https://github.com/thorchain/asgardex-electron/issues/1636, which is
still open. You got an info about closing this issue here just because you
have added a duplicated message ^
https://github.com/thorchain/asgardex-electron/issues/1615#issuecomment-881363939
before.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/thorchain/asgardex-electron/issues/1615#issuecomment-894663609,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUNORVAVPHJNXPQCJZEP56TT3VBGDANCNFSM47637GXQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

Any update on this issue, notice no change after upgrade?
Thxs
Rob
On Sat, Aug 7, 2021 at 4:57 PM RH @.***> wrote:

O ok, thxs
On Sat, Aug 7, 2021 at 10:44 AM veado @.***> wrote:

Why did you close this issue, when it’s not resolved yet !! I still have
not got my crypto amount corrected via $4847.868 In eth which you show only
.605 crypto ! Please reply Thxs Rob
Pls note: This issue here (#1615
https://github.com/thorchain/asgardex-electron/issues/1615) has
nothing to do with #1636
https://github.com/thorchain/asgardex-electron/issues/1636, which is
still open. You got an info about closing this issue here just because you
have added a duplicated message ^
https://github.com/thorchain/asgardex-electron/issues/1615#issuecomment-881363939
before.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/thorchain/asgardex-electron/issues/1615#issuecomment-894663609,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUNORVAVPHJNXPQCJZEP56TT3VBGDANCNFSM47637GXQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.


cvss{2,3}_score fix

Currently, vmaas-sync syncs the empty cvss{2,3}_score as 0.0 (in contrast with vulnerability, where it keeps as NULL value).

Add constraint to not allow NULL value, to keep it consistent
Manager fix to respect this 0.0 value

This could be done other way arround (empty score as NULL, vmaas-sync inserts nil), opinions?
Secure Coding Practices Checklist GitHub Link

https://github.com/RedHatInsights/secure-coding-checklist

Secure Coding Checklist

[x] Input Validation
[x] Output Encoding
[x] Authentication and Password Management
[x] Session Management
[x] Access Control
[x] Cryptographic Practices
[x] Error Handling and Logging
[x] Data Protection
[x] Communication Security
[x] System Configuration
[x] Database Security
[x] File Management
[x] Memory Management
[x] General Coding Practices

Codecov Report

Merging #80 (700cbbc) into master (b216dee) will increase coverage by 0.25%.
The diff coverage is n/a.

:exclamation: Current head 700cbbc differs from pull request most recent head 33ea6b3. Consider uploading reports for the commit 33ea6b3 to get more accurate results

@@            Coverage Diff             @@
##           master      #80      +/-   ##
==========================================
+ Coverage   40.21%   40.47%   +0.25%
==========================================
  Files          13       13
  Lines         639      635       -4
==========================================
  Hits          257      257
+ Misses        363      359       -4
  Partials       19       19

Flag
Coverage Δ

unittests
40.47% <ø> (+0.25%)
:arrow_up:

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

Impacted Files
Coverage Δ

digestwriter/consumer.go
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


log unexpected errors in the server console by default

Describe the bug
When an error thrown from context function, no error logs are shown in standard output/error.
Implementation:
createServer({
  // ... ,
  context: () => { throw new Error('foo') },
  // ...,
})

Then I open the GraphiQL page, the response is
{
  "data": null,
  "errors": [
    {
      "message": "Unexpected error."
    }
  ]
}

but no error logs are shown up, so it's hard to find the cause.
I tried useLogger() and useErrorHandler() plugins but both didn't catch that error.
Your Example Website or App
https://codesandbox.io/s/summer-brook-tvigl0?file=/src/main.ts
Steps to Reproduce the Bug or Issue

Create a minimal app with graphql-yoga, and set context value as a function that throws an error
Open http://localhost:4000/graphql in your browser, or just send a introspection query

Expected behavior
As a developer, I expected the error messages are shown.
Screenshots or Videos
No response
Platform

OS: macOS
NodeJS: 16.10.0
@graphql-yoga/* version(s): 2.5.0, 2.13.6

Additional context
Sorry, I haven't investigate whether this problem is related graphql-yoga or envelop.

Hey @qsona, thank you for using GraphQL Yoga!
Currently, errors are not logged to the console.
The original error SHOULD be included within the errors extension.originalError field within the execution result sent from the server, when you set the maskedErrors.isDev to true (or automatically when process.env.NODE_ENV is set to 'development' (See the error masking documentation).
HOWEVER, there is currently a bug within envelop that causes the error message to be swallowed. I am working on a fix of that here:

https://github.com/n1ru4l/envelop/pull/1471

Once this fix is released within Yoga, I will ping you here again.

We are currently working on GraphQL Yoga v3 (see our roadmap https://github.com/dotansimha/graphql-yoga/issues/1358). We want to make sure that Yoga v3 has the best developer experience. Logging unexpected errors to the console seems like something we should probably do.
In which kind of format would you expect these logs?

@n1ru4l Sorry my report was a bit inaccurate.
On my original app, I'm specifying NODE_ENV=development and using the useErrorHandler plugin. The error thrown by context function isn't handled by both, so I created this issue.
The workaround you showed ( onPluginInit(ctx) { ctx.registerContextErrorHandler // ... ) perfectly worked on my app. Thank you very much!

In which kind of format would you expect these logs?

I don't have a strong opinion about log format, but I'm basically satisfied with current way, I mean maskedErrors option and
useErrorHandler plugin. I'm thinking that the error thrown by creating context can be regarded as expected, so it just seems better if useErrorHandler catches it. (It's just an innocent opinion, of course I know it's not easy)

I have a similar problem, where e.g. errors thrown in any callback supplied to plugins loses their stack traces and can be very tedious to track down.
This is the line that seems responsible for losing the error stack https://github.com/dotansimha/graphql-yoga/blob/master/packages/common/src/GraphQLYogaError.ts#L36
A typical unhelpful error that gets returned could be:
{
  data: null,
  errors: [
    {
      message: "Cannot read properties of undefined (reading 'somewhere_in_my_code')"
    }
  ]
}

It would be great if such errors somehow could be logged, maybe using the debug library.

Hey @qsona, thank you for using GraphQL Yoga!
Currently, errors are not logged to the console.
The original error SHOULD be included within the errors extension.originalError field within the execution result sent from the server, when you set the maskedErrors.isDev to true (or automatically when process.env.NODE_ENV is set to 'development' (See the error masking documentation).
HOWEVER, there is currently a bug within envelop that causes the error message to be swallowed. I am working on a fix of that here:

fix: include the original context error in extensions in dev mode for error thrown during context creation n1ru4l/envelop#1471

Let's track this here instead and keep this issue as a general logging issue: #1585
For now, you can use the following workaround, by specifying your own logger plugin: https://codesandbox.io/s/yoga-log-unexpected-errors-to-the-console-vhir52
We are currently working on GraphQL Yoga v3 (see our roadmap #1358). We want to make sure that Yoga v3 has the best developer experience. Logging unexpected errors to the console seems like something we should probably do.
In which kind of format would you expect these logs?

I am currently having issues writing error handling with yoga v3.
In v2, I could just got the original error from the result, and handle it as I pleased.
In v3 the errors that I throw seems lost.
I have been trying to figgure out when the my error is converted to a GraphQLErorr and the original error lost.
I understand that "maskError" happens after useErrorHandler, I am just trying to figgure out where I can access my errors.
Within "maskError" the error has already been converted to a GraphQLerror
    maskedErrors: {
      maskError: (error) => {
        console.log(error.name, 'Its a GraphQLError')
        // And no properties of the original error exists
        console.log(error.originalError.name, 'This is also a GraphQLError...')
        console.log(error.originalError.httpErrorMessage, 'Custom error property is gone')

        return error as Error
      },
    },
`
``

Using the `useErrorHandler` package has the same result.
There are properties left of the original error that was thrown.

I am using
`"graphql-yoga" : "3.0.0-next.8"`
`"@envelop/core": "^3.0.3"`

I am sure the answer is simple, but I think it should be documented how one should catch custom rrror thrown in resolvers.


fix: move prompt templates to modules which use them

I think refactor: commit type would be better choice here rather than fix:


Video

Hey guys! Thanks for submitting to the gitcoin hackathon. Were you able to submit a video?

Wasn’t sure how to submit the video. I’ll add a link to the video on the
README shortly.
On Thu, Jul 30, 2020 at 6:44 PM Patrick Collins<EMAIL_ADDRESS>wrote:

Hey guys! Thanks for submitting to the gitcoin hackathon. Were you able to
submit a video?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/littlezigy/crypto-cards/issues/3, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAYCRYCZLJ2QNQIY3KO3ANDR6HZTBANCNFSM4PO2KUOA
.

--
Derrick Wilson - Duncan
Temple University, B.S. Computer Science
<EMAIL_ADDRESS>www.linkedin.com/in/derrick-wilson-duncan-5ab07053
https://github.com/coderrick
https://github.com/coderrick

Looks like the video is for another project?

Looks like the video is for another project?

No it's for this. I've updated the video.


Add CloudWatch logs entrypoint documentation

Fixes

Fixes #2298 by @sarayourfriend
Description

Adds a new documentation page describing the basic knowledge for using CloudWatch to query logs, both via Log groups (where to find logs, etc) and Logs Insights, along with some example insights queries.
I also added the sphinx-reredirects plugin so that I could move the Cloudflare traffic documentation into a common "monitoring" directory without causing 404s.
Testing Instructions

Read the new documentation. Test the redirects by visiting /meta/traffic/index.html and confirming it redirects you to /meta/monitoring/traffic/index.html.
Checklist

[x] My pull request has a descriptive title (not a vague title likeUpdate index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[N/A] I added or updated tests for the changes I made (if applicable).
[x] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no visible errors.
[N/A] I ran the DAG documentation generator (if applicable).

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

Replacing Franciso's review request with @dhruvkb as you expressed to me recently feeling like you weren't sure how to start querying for logs and, therefore, you are exactly the audience for this new document :slightly_smiling_face:


[Cleanup] Default to pre-norm throughput: 10.3/N

This PR removes *normalize_before flags and defaults to pre-norm logic throughout.
Part of https://github.com/facebookresearch/metaseq/issues/368 efforts.

bold

At some point we can add flags in again... just not before we figure out how to clean up our configuration setup 😅


cmake: 3.27.8 -> 3.28.1

Changelog: https://cmake.org/cmake/help/v3.28/release/3.28.html
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Duplicate of #275284?

Closing as duplicate - and especially because the patches weren't "rebased", which causes the Darwin issue.


unlink error on fork

The below sample program fails through Lind and shouldn't, it seems due to an error in unlink.
#include <stdio.h>
#include <string.h>
#include <unistd.h>
#include <fcntl.h>
#include <errno.h>
int main(){
  int fd = open("test.txt", O_RDWR | O_CREAT, 0777);
  char buf[] = "This is a test of the wonderful fork call in lind.";
  write(fd, buf, sizeof(buf));
  close(fd);
  fd = open("test.txt", O_RDWR);
  switch(fork()){
    case -1:
      puts("fork failed");
      break;
    case 0:
      close(fd);
      break;
    default:
      sleep(1);
      char newbuf[100];
      int numread = read(fd, newbuf, 100);
      printf("%s\n",newbuf);
      printf("read %d chars\n",numread);
      unlink("test.txt");
      close(fd);
      break;
  }
  return 0;
}

This was fixed with this PR.


Unable to delete tenant if there is enterprise application for DevOps

If the tenant has DevOps app registration then you won't be able to delete the enterprise application and hence tenant can't be deleted.

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

ID: ea77d5a9-6619-0f31-9567-6085b7a4b5a2
Version Independent ID: f4cf720d-60dd-f086-3ace-1ff17e427757
Content: Delete an Azure AD tenant - Azure Active Directory
Content Source: articles/active-directory/enterprise-users/directory-delete-howto.md
Service: active-directory
Sub-service: enterprise-users
GitHub Login: @curtand
Microsoft Alias: curtand

@ramuvr
Thank you for your feedback!
Microsoft first party applications shouldn't prevent you from deleting your Azure AD Tenant. Have you tried following the section Enterprise apps with no way to delete section?
We also had another customer run into this same issue: Delete tenant - Enterprise Applications

On your windows desktop search, Open PowerShell ISE as Administrator
Install the needed module, type at promt: Install-Module MSOnline
Then type at prompt: Connect-msolservice
Input a global admin’s credentials for your azure tenant. (eg. User<EMAIL_ADDRESS>+ password)
If we have any output please run the following command at the prompt: Get-msolserviceprincipal | remove-msolserviceprincipal (Note you will see a lot of red output on this command, these are applications that cannot be deleted from the tenant, but will not stop you from doing so.)
Log in back to the Azure tenant, and try one more time to delete it.

If you have any other questions, please let me know.
Thank you for your time and patience throughout this issue.

Thank you, that worked.
I got confused as it didn't deleted it yesterday with a message
"Remove-AzADServicePrincipal: Specified App Principal ID is Microsoft Internal."
Probably related to some other service registration.
All good.

@ramuvr
Thank you for following up on this and I'm glad that I was able to help resolve your issue!
I'll go ahead and close this out.
Thank you for your time and patience throughout this issue.

Hello,
I have the same issue:
Unable to delete tenant
Unable to delete tenant Florent Appointaire. Known issues exist where some enterprise applications are not capable to delete within the portal.  Click the notification title for more information and manual troubleshooting steps.
I tried commands that are before, and retry to delete, without success.
Any idea?
Florent


Replace gcc's download_prerequisites with Ubuntu packages

Travis CI has problems downloading from GNU's FTP servers,
so use the appropriate Ubuntu packages to not cause timeouts.

Closing in favour of #206


Bacon::Error: nil.kind_of?(UIBarButtonItem) failed

Hi,
I have installed ProMotion 2.2.1. When I run "rake spec" there were some issues in a console. I did not add any code. The new created app works on iOS Simulator though.
My iOS SDK version is 8.2, RubyMotion 3.6
Stacktrace for "rake spec":
HomeScreen

has a navigationController
has a right nav bar button [FAILED - nil.kind_of?(UIBarButtonItem) failed]
opens the help screen when tapping Help [FAILED - #HomeScreen:0x10bd90e40.kind_of?(HelpScreen) failed]

Bacon::Error: nil.kind_of?(UIBarButtonItem) failed
spec.rb:745:in satisfy:': HomeScreen - has a right nav bar button 	spec.rb:759:in method_missing:'
spec.rb:316:in block in run_spec_block' 	spec.rb:459:in execute_block'
spec.rb:316:in run_spec_block' 	spec.rb:331:in run'
Bacon::Error: #HomeScreen:0x10bd90e40.kind_of?(HelpScreen) failed
spec.rb:745:in satisfy:': HomeScreen - opens the help screen when tapping Help 	spec.rb:759:in method_missing:'
spec.rb:316:in block in run_spec_block' 	spec.rb:459:in execute_block'
spec.rb:316:in run_spec_block' 	spec.rb:331:in run'
4 specifications (4 requirements), 2 failures, 0 errors
I tried to deploy the app to my iPad and there were an error:
: assertion failed: 12B466: libxpc.dylib + 51955 [...]: 0x7d
Are there any solutions how to solve it?

Hi @bolatkazybayev ! Sorry about that, I've known that there's some issues with the template for a while. Haven't had time to fix them yet.
The main issue right now is that tap(<UIView>) doesn't appear to work anymore. I think it could be a bug with UIAutomation, but it's hard to tell. You're going to have to find a different way to simulate taps, unfortunately.


Update README.md

I tryed to use your workspace example but in order to use it you need to first add the git rule to your workspace.
I think this should be added to your README so that a user could just copy and past it to its workspace.
If they have the git repo rules already this would not break them;)
Additionaly i want to thank your for this project since it makes using the arm-toolchain as easy as possible

I'm glad you found this project helpful, and that you gave it a star! Thanks for updating the readme


Upgrade to Kubernetes 1.17.0

K8s 1.17.0 is out. Update k3s to use it.
As part of this, we will be changing the versioning of k3s to be inline with kubernetes, as mentioned in this issue: https://github.com/rancher/k3s/issues/1088

QA testing has been completed (rc1 thru rc4). Conformance tests are also passing.


Horizontal line/Spacer renders before image

![](https://placehold.co/200x100/EEE/31343C)

<hr>

Renders in Inlyne (4.2):

GitHub:

(edit): This does not occur when align center or right is used, so the problem lies somewhere in how we handle image rows because https://github.com/Inlyne-Project/inlyne/blob/32619fff5ab60e1217d12be43b91e679042eb0f2/src/interpreter/mod.rs#L341C9-L352C10

Yeah the code for handling inline images has been notoriously buggy. I'll work on adding some more tests on how that part of the code should behave over time since there are a lot of different variations that people use for their README's headers


Doesn't work if it can't get to the internet

This seems to be a chronic issue with all docker base projects, but... scope tries to download containers from the registry, which is an issue when trying to start it up on a hosts in a restricted network
[root@docker-as-4p tmp]# ./scope launch
Unable to find image 'gliderlabs/alpine:latest' locally
Pulling repository docker.io/gliderlabs/alpine
Network timed out while trying to connect to https://index.docker.io/v1/repositories/gliderlabs/alpine/images. You may want to check your internet connection or if you are behind a proxy.
Unable to find image 'weaveworks/scope:0.6.0' locally
Pulling repository docker.io/weaveworks/scope
Network timed out while trying to connect to https://index.docker.io/v1/repositories/weaveworks/scope/images. You may want to check your internet connection or if you are behind a proxy.
[root@docker-as-4p tmp]#

The scope script you're running, like the weave script it was roughly based on, is a bootstrapping shim that eventually just calls out to a Docker daemon. As you've noticed, if a Docker daemon doesn't have the requisite container images locally, it will attempt to download them.
You can use Docker on an internet-connected host to fetch the images, and then move them to your restricted network however you see fit. Then, Docker (via the scope script) won't need to reach out to the internet.
On the internet-connected host,
$ docker pull weaveworks/scope:0.6.0
$ docker save -o scope-0.6.0.tar weaveworks/scope:0.6.0

Copy the file to the restricted host using your provisioning system, and then
$ docker load -i scope-0.6.0.tar
$ ./scope launch

Please let me know if that solves your problem!

As I did with weave I went the long way around, pulled the images to our internal registry and then modified the scope script to point to the internal images. I still feel that this is an issue affecting most of docker base projects. Having to hack scripts of move images around is a blocker for a wider adoption of the projects.

The scope script is meant as a bootstrapping tool, and isn't intended to cover all use cases, especially in infrastructures with constraints like restricted network access. I'm glad you were able to get it working. If you have suggestions for how we might better package and distribute our software, we'd be happy to hear them!


Security Issue.

Patient3 cannot able to see other patient name.
Patien3 can only able to book an appointment to a doctor only for himself/herself.

Solved it bro


CMake best practices with ComputeLibrary

Hello there,
Let's say I have successfully built ARM-CL, and it is in ~/tools/arm/ComputeLibrary/build.
Now, I have a project in some other directory.  It uses the CMake build system.  I want to be able to leverage ARM-CL, use the the tools provided by it etc.
Using CMake, as we need to link our code to the library, and include the ARM-CL headers.  Our project structure is thus:
.
├── _build
├── CMakeLists.txt
└── src
    ├── CMakeLists.txt
    └── gemm_armcl.cpp

CMake folk: how would you link ARM-CL?

Download and build ARM-CL in the project directory.
Use some sort of FindARMCL.cmake script
Globally install ARM-CL by adding symbolic links in some common location?

This StackOverflow post seems like a way to do it, though when it comes to ARM-CL I'm not entirely sure what and where to link.

Have been working away with the ComputeLibrary, and did eventually get an okay workflow going with it.  Has been a good learning experience.
I have made a minimum working example from my project, which you can find in this Github repo.  Hopefully this will be useful for other people starting out like me.
Any suggestions for improvements would be appreciated, since right now I have the library built from source, and the path to the build directory as an environment variable (see MWE).

Thanks for sharing your example, closing this issue for now.


Move initialising prop definitions from the constructor to the prototype

See https://github.com/skatejs/skatejs/blob/master/src/api/component.js#L57
This is breaking as it removes support for Safari < 10.

So original iPad and iPhone 4/4S. Sad, but I think that reflects the common consensus for mainstream sites.

Yeah, I thought about that. There's so many problems with Safari <= 9, though and I think that's why so many have said they just support "latest".  If you have any further thoughts on this, I'm happy to discuss.

I think the direction of turning most things into mixins is the best, it allows making legacy browser variants that don't hold back new functionality. Of course it is more work and likely to atrophy without a larger number of maintainers. So in this case I would lean towards moving forward.

I would be cautious about moving everything to mixins as it creates long prototypal chains, which may hit performance ( maybe, have no numbers yet )...

I'm also concerned about perf here. Every upgrade has to walk all the way from your top chain to HTMLElement. This should be optimised by the browser if using native, but ES5 transpiled code uses setPrototypeOf. Maybe a non-issue in the future.

To be clear, mixins are great, and whatever can be modularised probably should be. I still prefer the idea of having a pre-built base class for an all-in approach for the simplest use case. For example, I use most features in most components, so it makes sense to not have to piece everything together every time for that.

Done in #1098.


License info

On npm.org the license is set to 'none'. Can it be, or do you have plans to also update it to MIT? We would like to leverage your package, but are unable unless the package is explicitly marked MIT on the npm.org site.
Thanks in advance

Done in 11.0.3


Using Dropbox Refresh Token

@arjunprakash027 Can we use Dropbox Refresh Token for our Airlift?
https://stackoverflow.com/questions/70641660/how-do-you-get-and-use-a-refresh-token-for-the-dropbox-api-python-3-x
https://www.codemzy.com/blog/dropbox-long-lived-access-refresh-token
https://www.dropbox.com/developers/documentation/http/documentation#authorization

token_access_type String? If this parameter is set to offline, then the access token payload returned by a successful /oauth2/token call will contain a short-lived access_token and a long-lived refresh_token that can be used to request a new short-lived access token as long as a user's approval remains valid. If set to online then only a short-lived access_token will be returned. If omitted, this parameter defaults to online.

We can build in a function to get long-lived dropbox refresh Token?
--dropbox-get-refresh-token "App key" "App secret"
Tool would Launch the URL in Browser to Authorise. Once Authorise, User can input their Access Code?
And the Tool would generate the "Refresh Token"?
Not sure if this could be possible.

From : https://stackoverflow.com/questions/70641660/how-do-you-get-and-use-a-refresh-token-for-the-dropbox-api-python-3-x
Find the APP key and App secret from the App Console.
Run the following snippet (replace APP_KEY with the value obtained from last step) and complete the process in the browser to obtain Access Code Generated.
import webbrowser

APP_KEY = '<APP_KEY>'
url = f'https://www.dropbox.com/oauth2/authorize?client_id={APP_KEY}&' \
      f'response_type=code&token_access_type=offline'

webbrowser.open(url)

Replace all APP_KEY, APP_SECRET, and ACCESS_CODE_GENERATED with the actual values in the following snippet. Run the snippet.
import base64
import requests
import json

APP_KEY = '<APP_KEY>'
APP_SECRET = '<APP_SECRET>'
ACCESS_CODE_GENERATED = '<ACCESS_CODE_GENERATED>'

BASIC_AUTH = base64.b64encode(f'{APP_KEY}:{APP_SECRET}'.encode())

headers = {
    'Authorization': f"Basic {BASIC_AUTH}",
    'Content-Type': 'application/x-www-form-urlencoded',
}

data = f'code={ACCESS_CODE_GENERATED}&grant_type=authorization_code'

response = requests.post('https://api.dropboxapi.com/oauth2/token',
                         data=data,
                         auth=(APP_KEY, APP_SECRET))
print(json.dumps(json.loads(response.text), indent=2))

Added Dropbox Refresh Token!


Bug 1504250 - Keep listening for deprovision messages

Describe what this PR does and why we need it:
We want the subscriber to keep listening for deprovision messages even if a previous deprovision fails.
See https://bugzilla.redhat.com/show_bug.cgi?id=1504250 for recreation steps.
Before this change 'deprovision complete msg' would be sent to the channel but there would not be a corresponding 'processed deprovision message from buffer'.
After this change (from broker logs):
...
[2017-10-19T20:07:53.008Z] [DEBUG] sending deprovision complete msg to channel
[2017-10-19T20:07:53.008Z] [DEBUG] Processed deprovision message from buffer

OR chain the if statements so they only do one of them at a time and no need for continue or return. See the provision subscriber. Either way is acceptable.

$ make build
go build -i -ldflags="-s -w" ./cmd/broker

$ make check
ok      github.com/openshift/ansible-service-broker/pkg/apb     0.190s
ok      github.com/openshift/ansible-service-broker/pkg/app     0.236s
ok      github.com/openshift/ansible-service-broker/pkg/auth    0.016s
ok      github.com/openshift/ansible-service-broker/pkg/broker  0.207s
?       github.com/openshift/ansible-service-broker/pkg/clients [no test files]
?       github.com/openshift/ansible-service-broker/pkg/dao     [no test files]
?       github.com/openshift/ansible-service-broker/pkg/fusortest       [no test files]
ok      github.com/openshift/ansible-service-broker/pkg/handler 0.309s
?       github.com/openshift/ansible-service-broker/pkg/metrics [no test files]
?       github.com/openshift/ansible-service-broker/pkg/origin/copy/authorization       [no test files]
ok      github.com/openshift/ansible-service-broker/pkg/origin/copy/authorization/validation    0.086s
?       github.com/openshift/ansible-service-broker/pkg/origin/copy/user        [no test files]
ok      github.com/openshift/ansible-service-broker/pkg/origin/copy/user/validation     0.081s
ok      github.com/openshift/ansible-service-broker/pkg/registries      0.079s
ok      github.com/openshift/ansible-service-broker/pkg/registries/adapters     0.102s
?       github.com/openshift/ansible-service-broker/pkg/runtime [no test files]
?       github.com/openshift/ansible-service-broker/pkg/version [no test files]


shortcut key to execute query causing context menu to be displayed

Description
When I execute a query using the shortcut control-enter the query executes fine but the query context menu is displayed (as if I had mouse clicked on the query to get the execute / file / format etc context menu).
I can press escape to make this disappear but then the script tab context menu is displayed (which I can also make disappear by esc again)
DBeaver Version
Version <IP_ADDRESS>409221725
Operating System
macOS Sequoia 15.0
Database and driver
No response
Steps to reproduce
No response
Additional context
No response

Thank you for report. It's a duplicate of #35109
Please follow this steps to fix it on your mac https://github.com/dbeaver/dbeaver/issues/35109#issuecomment-2306254608


Allow doctrine/persistence ^3.0

Closes #2419

Would it be possible to have a release with this support ?

We'll make one once we wrap up #2412


build with tensorflow_cc with cmake.

I found https://github.com/FloopCZ/tensorflow_cc/
as a good solution.
should somebody add it to official repository

That sounds wonderful and I hope the community finds it useful.
From what I understand, bazel is used to build libtensorflow_cc.so, and what's there packages that up with a set of header files.
Eventually, we would like to distribute the shared library and header files in a tarball that can be used by any build system, instead of having to maintain support for different build systems. We'd also like to tighten the API a bit, to reduce the number of internal header files that need to be exposed.
If anyone is interested in contributing to that, I'd suggest following along on #2412.
Thanks!
(FYI @skye)

@asimshankar Yes, that is exactly what is done in there. However, it should be noted that if https://github.com/FloopCZ/tensorflow_cc/issues/8 is resolved (add support for CPack), you will be able to easily build a tarball, installers and even deb/rpm packages independent of the build system (FYI @skye).

@FloopCZ Where should I place the example folder or its contents. From which location should I run those last commands(3rd point under Usage) in your repository ?

Lets continue at https://github.com/FloopCZ/tensorflow_cc/issues/112#issuecomment-461413277.


You can implement it better!

https://github.com/zongyi-li/fourier_neural_operator/blob/90bbd4c9ffa84b91ec2daa86660148861989adec/fourier_3d.py#L53
What you can do is using FFTshift:
def roll_n(X, axis, n):
    f_idx = tuple(slice(None, None, None) if i != axis else slice(0, n, None)
                  for i in range(X.dim()))
    b_idx = tuple(slice(None, None, None) if i != axis else slice(n, None, None)
                  for i in range(X.dim()))
    front = X[f_idx]
    back = X[b_idx]
    return torch.cat([back, front], axis)

def fftshift(data):
    for dim in range(len(data.size()) - 3, len(data.size()) - 1):
        data = roll_n(data, axis=dim, n=data.size(dim) // 2)
    return data

and then slice just the middle of the tensor (instead of four different corners)

That's a very good point! Thanks for bringing this up!

I created a pull request: https://github.com/zongyi-li/fourier_neural_operator/pull/12

@hfarazi @zongyi-li pytorch has a built-in fftshift function these days, for what it's worth

Is there any advantage in doing it that way?
I had also tried to roll the coefficients but there was no speedup.

Closing as inactive.


suppressing "I" log messages in tensorflow

I am using TF 0.6.0 with python 2.7.10 on both ubuntu linux and osx 10.9.5.  TF base functionality is working fine.  The issue is logging - I want to suppress the following messages that are emitted whenever I construct the first tensorflow Session:
I tensorflow/core/common_runtime/local_device.cc:40] Local device intra op parallelism threads: 2
I tensorflow/core/common_runtime/direct_session.cc:58] Direct session inter op parallelism threads: 2
They do not appear to be transmitted through the normal python logging mechanism.  Any ideas?  Did I just miss something?
I don't want to turn off all log messages, I just want TF to stop generating these two specific messages - and perhaps if you can tell me how to turn off all INFO messages from this particular (seemingly non-pythonic) source, that would be fine too.

Hi @davefairtex ,
I am on latest tensor, python 2.7, and osx.On a quick look, these are logged using Google logging(logging.h) in local_device.cc/direct_session.cc from common_runtime module, and these logs can be required by some users.
While invoking your application you could use flags like below to suppress as needed?
./your_application —minloglevel=1 (such that INFO msgs are not logged; 0/1/2/3 acceptable values defaults to 0)
./your_application —logtostderr=0 (such that log msgs are suppressed in stderr; 0/1 acceptable values)

Logging levels for INFO, WARNING, ERROR, and FATAL are 0, 1, 2, and 3 respectively.
Thanks!

Rekha-
Thanks much for your comment; now I at least have a clue where I should be looking.
I don't have gflags installed.  I tried using an environment variable (which has been alleged to work in comments elsewhere), but it sadly did not work for me:
ub1%  GLOG_minloglevel=3 python
Python 2.7.10 (v2.7.10:15c95b7d81dc, May 23 2015, 09:33:12)
[GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

import tensorflow
tensorflow.Session()
I tensorflow/core/common_runtime/local_device.cc:40] Local device intra op parallelism threads: 4
I tensorflow/core/common_runtime/direct_session.cc:58] Direct session inter op parallelism threads: 4
<tensorflow.python.client.session.Session object at 0x10693fb50>
import os
os.environ['GLOG_minloglevel']
'3'

Any thoughts?  I also tried setting os.environ['GLOG_minloglevel'] = '3' within python directly prior to importing tensorflow, also no luck there.

Hi @davefairtex ,
From the logging referred to in tensorflow*, I observe the parameter re2::FLAGS_minloglevel that needs to be overridden. Set to 1 or greater to suppress info logs. I am not 100% sure it works as new checkins on re2 package, but Ideally it needs to be possible for user to override this parameter via command line. As a workaround, if you are stuck, you can pipeline current output to sed to remove unneeded log lines and get exact output you need.thanks.

https://github.com/google/re2/blob/master/util/logging.h
https://github.com/google/re2/blob/master/util/flags.h

rekha- thanks for the update.  With your help I found the re2::FLAGS_minloglevel variable in the shared object, but I have no way of setting it directly from python.  (If I were using C++ I could totally do it - but I'm not).   I tried setting it using the python gflags interface:
import tensorflow
import gflags
gflags.ADOPT_module_key_flags(tensorflow)
gflags.FLAGS(['-minloglevel', '3'])
tensorflow.Session()
but that still gives me the log messages.  Is this the correct way to set the tensorflow gflags?  (Is this actually a tensorflow module gflag?  It does show up in "nm _pywrap_tensorflow.so")
It would be awesome if the code had only one logging mechanism, controllable via python.
I know I can use sed; it just seemed so disagreeable to do that.  I was hoping there was a three-line "real" way to fix the problem.

Thanks @davefairtex  I agree its painful for its a simple act of suppressing and silencing logs.Was providing quick suggestions hoping simplest logical way works with flags :-) However looking more though there are various flavors of logging, this one just hits the tensorflow/core/platform/default/logging.h.For this case used verbose logging.thanks.

https://github.com/tensorflow/tensorflow/pull/619

"And there was great rejoicing" ...  thanks for the fix, look forward to the new version.  Its really nice to see that you guys are responsive about even minor things like this.

@davefairtex What is the actual fix? Does your glfags python code from above now work for suppressing the "I" messages?

import tensorflow
import gflags
gflags.ADOPT_module_key_flags(tensorflow)
gflags.FLAGS(['-minloglevel', '3'])
tensorflow.Session()

hi @fiannaca please refer https://github.com/tensorflow/tensorflow/pull/619 for this log issue.thanks!

@rekhajoshm I should be more clear. I saw that pull request already. I'm just not sure what that means for how I can actually go about suppressing the "I" messages from TF. What are the actual steps now for suppressing log messages?

Hi @fiannaca As stated in the #619 , logging has a different flow here and cannot be overridden by gflags/re2 atm. You can apply the patch for the #619 for your setup to avoid the logs. Another quick pull here https://github.com/tensorflow/tensorflow/pull/1229 to have conditional logging., in some time.thanks.

I'm also confused about the status of this. Is this possible to achieve now with a released version, or is it yet to appear?

There's a related issue here: https://github.com/tensorflow/tensorflow/issues/1258
That issue is still open, so I suspects there's no way to change logging settings other than modifying the code and recompiling. For instance, here are instructions on how to change verbose logging level here -- http://stackoverflow.com/a/36505898/419116

@vrv, @rekhajoshm: What's the status of this after #619?

#619 just removed some unnecessary logging, our logging library still doesn't have the ability to control verbosity.  Still a contributions welcome at this point.

It has been 11 months since my initial request: a way to stifle the flood of "ALL IS STILL WELL AND OPERATING NORMALLY" info messages that appear each every time tf starts up.
Since a more general mechanism can't seem to make it onto anyone's list, can someone please just raise the default debugging level to WARN?  I don't care about INFO messages.  I suspect there is a vast silent majority that agrees with me.  Once our dev environments are configured properly, 99.9% of the problems we users face are in our own code, and the flood of (useless, to us) INFO messages proclaiming (yet again) that the normal initialization sequence worked properly just gets in the way of us trying to sort out the actual errors in our own stuff.
Thanks for listening to my rant.
Here's an example of all the stuff I have to wade through every time I run tf (0.10.0):
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcublas.so locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcudnn.so locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcufft.so locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcuda.so.1 locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcurand.so locally
I tensorflow/core/common_runtime/gpu/gpu_init.cc:102] Found device 0 with properties:
name: GeForce GTX 970
major: 5 minor: 2 memoryClockRate (GHz) 1.253
pciBusID 0000:01:00.0
Total memory: 3.94GiB
Free memory: 3.88GiB
I tensorflow/core/common_runtime/gpu/gpu_init.cc:126] DMA: 0
I tensorflow/core/common_runtime/gpu/gpu_init.cc:136] 0:   Y
I tensorflow/core/common_runtime/gpu/gpu_device.cc:838] Creating TensorFlow device (/gpu:0) -> (device: 0, name: GeForce GTX 970, pci bus id: 0000:01:00.0)

I am in the same boat as @davefairtex . So far I've been using a workaround: a bash script wrapping the call to my python script, filtering out the unwanted messages. Let me share it here, in case it helps someone:
#!/bin/bash
python $* 3>&1 1>&2 2>&3 3>&- | grep -v ^I\ | grep -v ^pciBusID | grep -v ^major: | grep -v ^name: |grep -v ^Total\ memory:|grep -v ^Free\ memory:

I called the script tf.sh and simpy preface python script calls with it. e.g. tf.sh my_script.py.
A bit non-trivial as the naive approach using |& and then grep -v ends up buffering STDOUT, at least on my system.

The more general tracking issue is https://github.com/tensorflow/tensorflow/issues/1258
I like @rekhajoshm proposal to specify logging options as part of tf.ConfigProto given to Session

Closing as duplicate of https://github.com/tensorflow/tensorflow/issues/1258, see comments there.

Adding this just because I get redirected here way too often and still do not find the flag.
Terminal: export TF_CPP_MIN_LOG_LEVEL = 2
Python: tf.logging.set_verbosity(tf.logging.ERROR)


catalystproject-latam: decommission old filestore

fixes #4338

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  - destroy

Terraform will perform the following actions:

  # google_filestore_instance.homedirs["filestore"] will be destroyed
  # (because key ["filestore"] is not in for_each map)
  - resource "google_filestore_instance" "homedirs" {
      - create_time = "2023-07-07T07:18:58.726882564Z" -> null
      - id          = "projects/catalystproject-392106/locations/southamerica-east1-c/instances/latam-homedirs" -> null
      - labels      = {} -> null
      - location    = "southamerica-east1-c" -> null
      - name        = "latam-homedirs" -> null
      - project     = "catalystproject-392106" -> null
      - tier        = "BASIC_HDD" -> null

      - file_shares {
          - capacity_gb = 6144 -> null
          - name        = "homes" -> null
        }

      - networks {
          - connect_mode      = "DIRECT_PEERING" -> null
          - ip_addresses      = [
              - "<IP_ADDRESS>",
            ] -> null
          - modes             = [
              - "MODE_IPV4",
            ] -> null
          - network           = "default" -> null
          - reserved_ip_range = "<IP_ADDRESS>/29" -> null
        }
    }

Plan: 0 to add, 0 to change, 1 to destroy.


What event is thrown if customer disconnect the call within flow.

I need to do an insert operation in database with lambda after a call is disconnected by the customer in IVR (Contact Flows). I don't know where to call lambda function after call is disconnected

Take a look at Amazon Connect Events using the event busOn 23 Dec 2022, at 09:14, Nithishsubramaiyan @.***> wrote:
I need to do an insert operation in database with lambda after a call is disconnected by the customer in IVR (Contact Flows). I don't know where that session travels once call is disconnected
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

I have checked the amazon connect event bus , as per the docs DISCONNECTED event is thrown only if the call is disconnected by the agent or flow action but need to know weather event is thrown if the customer disconnects the call.

I believe it is when the contact is disconnected irrespective of who
disconnect otherwise it is pretty useless
I will test it and let you know the outcome
On Fri, 23 Dec 2022 at 09:52, Nithishsubramaiyan @.***>
wrote:

I have checked the amazon connect event bus , as per the docs DISCONNECTED
event is thrown only if the call is disconnected by the agent or flow
action but need to know weather event is thrown if the customer disconnects
the call.
—
Reply to this email directly, view it on GitHub
https://github.com/amazon-connect/amazon-connect-streams/issues/623#issuecomment-1363798387,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMLCER6XIRVEI5FGKMZ6MOTWOVY47ANCNFSM6AAAAAATHROHJQ
.
You are receiving this because you commented.Message ID:
@.***>

That is as useful as a chocolate teapot. I will raise it with AWS
On Fri, 23 Dec 2022 at 09:52, Nithishsubramaiyan @.***>
wrote:

I have checked the amazon connect event bus , as per the docs DISCONNECTED
event is thrown only if the call is disconnected by the agent or flow
action but need to know weather event is thrown if the customer disconnects
the call.
—
Reply to this email directly, view it on GitHub
https://github.com/amazon-connect/amazon-connect-streams/issues/623#issuecomment-1363798387,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMLCER6XIRVEI5FGKMZ6MOTWOVY47ANCNFSM6AAAAAATHROHJQ
.
You are receiving this because you commented.Message ID:
@.***>

I need to do a database insert operation for all types of disconnect operation, irrespective of disconnected  by flow, agent, or customer.
Is there any workaround for this, or should I use only bus events?

Hi, I have just tested this functionality, and I get a disconnect event
when I hang up in the contact flow.
I created a small lambda to show the event type i received, so i called my
number and it played an announcement for me and i hung up and in the
cloudwatch logs the lambda was invoked on a disconnect.
On Fri, 23 Dec 2022 at 11:19, Nithishsubramaiyan @.***>
wrote:

I need to do a database insert operation for all types of disconnect
operation, irrespective of disconnected by flow, agent, or customer.
Is there any workaround for this, or should I use only bus events?
—
Reply to this email directly, view it on GitHub
https://github.com/amazon-connect/amazon-connect-streams/issues/623#issuecomment-1363865668,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMLCERYAHEJAN4ATMKM227LWOWDC3ANCNFSM6AAAAAATHROHJQ
.
You are receiving this because you commented.Message ID:
@.***>

Hi, I have just tested this functionality, and I get a disconnect event when I hang up in the contact flow. I created a small lambda to show the event type i received, so i called my number and it played an announcement for me and i hung up and in the cloudwatch logs the lambda was invoked on a disconnect.
…
On Fri, 23 Dec 2022 at 11:19, Nithishsubramaiyan @.> wrote: I need to do a database insert operation for all types of disconnect operation, irrespective of disconnected by flow, agent, or customer. Is there any workaround for this, or should I use only bus events? — Reply to this email directly, view it on GitHub <#623 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMLCERYAHEJAN4ATMKM227LWOWDC3ANCNFSM6AAAAAATHROHJQ . You are receiving this because you commented.Message ID: @.>

Can you please show how you did it? I mean can you share your code how did you call lambda function on disconnect event. I am facing similar issue and want to understand how you did it. Thank you.

I am looking forward to your answer because i am unable to handle call disconnect event.. a little help is appreciated.
How you did this ?
I created a small lambda to show the event type i received, so i called my
number and it played an announcement for me and i hung up and in the
cloudwatch logs the lambda was invoked on a disconnect.
…

Would love an answer on this one too.
Based on https://docs.aws.amazon.com/connect/latest/adminguide/contact-events.html, it looks like there is no contact flow event for customer disconnected, which is wild. Seems like a huge miss.


More features for group wall / improve conversations

Starting with conversations & feedback for finished pickups, it'd make sense to implement a wall from now on. This would be a mixture of history, chat, and pickup-feedback.
Items I would include:

wallPost (chat messages)
wallJoined people who joined the group
wallPickup when you did a pickup (with a button to give feedback, if not done so already)
wallFeedback feedback for pickups

I think this could be a nice way of having all relevant information in one single place.
Design Ideas

...please don't mind my drawing skills :wink:

Yup, great idea to combine them into a feed. I was just looking at a pull request conversation tab, and that has all the useful things on it. Although those are top -> bottom, instead of bottom -> top (like a wall normally is).
A few questions it opens up too:

what should do the combining of items:

frontend
backend
insert messages into the conversation for each thing that should be shown - this approach is my initial inclination, so it keeps the frontend/api simple (also the conversations is the only model that has the concept of updates being pushed over the websocket - although we can push more updates in the future)

comment threads - it puts more need to have comments on conversation mesages (aka threads...) as you don't normally reply to a wall post with another wall post... (especially if there are other message types in there - although having said that, it's exactly what you do on a github pull request conversation thread, it's just a simple linear thing)
how does this fit with the ideas in the other thread re chat vs wall style display (sorry, don't have it to hand, and have to turn off computer now!)

i don't understand this issue , -most information referenced can be found in the history tab view .

@nicksellen

Although those are top -> bottom, instead of bottom -> top (like a wall normally is).
..the messages are already ordered the other way round in the current chat UI proposal #597 (if that's what you meant)

I like the idea of adding messages in the conversation. Maybe we could have a "message-type" var for each message? So that they can still look differently in our frontend and stay translatable? Or we add an option to the history endpoint to also return the messages of the group-conversation and pickup-feedback (shouldn't pickup feedback be a history entry anyways?)

comment threads

Comments would of course be even better, but I think for now it'd also make sense with what we have already (conversation + joins + feedback + your pickups)

how does this fit with the ideas in the other thread re chat vs wall style display

From what I read in #583, it seems to go along with the idea of a wall quite well.
@Sliverriver
My intention is to combine all relevant information in one place. Pickup-feedback doesn't have a spot yet where you could read through the feedback other people gave (except for group/xxx/give-feedback, but thats not really a good place in my opinion), and the conversations also need somewhere to go.
And since the history endpoint is so overloaded with people joining and leaving pickups and doing other things, I'd like to make it more prominent when new people arrived in a group.
I think the 4 points mentioned above (+ joining future pickups, which is hard to add to a chronological wall) are really the most important status-aspects of our tool. On the other hand, history seems more like a protocoll to me and should in my opinion be used more like an admin-tool in the future.

On history vs wall
I agree with Lars, I like to think of the "history" as a complete log of everything that happened. It needs complex filters in order to be useful.
The "wall" is the information that users are mostly interested in, a selection of the history. It should have no filter parameters. Additionally, it has actions: you can create posts on the wall, probably edit them, comment on them.
Wall as conversation
I think adding a message type to conversations is a good idea. Then we push all relevant information into conversations and "wall" shows the group conversation. We can extend the concept to stores as well.
The question is: what is relevant information? The "wall" content is the same for all users, so we can't make it user-specific.
Group wall content:

users joining the group
stores being added
people posting on the wall
upcoming pick-up where nobody has signed up so far (with join action)

Store wall content:

feedback to pick-ups
new pick-up dates
people posting on the wall
upcoming pick-up where nobody has signed up so far (with join action)

Thoughts about sharing messages between conversations
The content "upcoming pick-up where nobody has signed up so far" could make sense in the store wall too, but it doesn't seem to make much sense to send it twice. Can we already introduce the concept of sharing messages? e.g. group wall would contain a reference to the store wall post.
Comment threads
Comparing it with Github issues: it has short-lived, top-to-bottom style conversations where comments are simply appended.
Group and store walls are long-lived and thus the most recent message first style seems better. But it needs comments pretty soon.
Slack threads are an interesting model. Thread messages are normal messages, but they have a "thread_id" field. The client takes care of the proper displaying them.
Wow, a lot of words...

Can we already introduce the concept of sharing messages? e.g. group wall would contain a reference to the store wall post.

I would not. Will get complicated very quickly. I think some duplication of content is fine here.
The facebook model seems much more like posts are independent things that get pulled into various feeds in various sort orders depending on magic algorithm - but our conversations are more like strict chronological things tied to a specific thing, which makes more sense to me for a working tool like ours compared to a casual social tool like facebook.
I think the challenge for us is to get a clear concept of what a conversation entry is compared to an activity entry. Could be, something happens, then:

we add an entry to the conversation AND to the history/activity independently
writing an activity/history entry triggers a conversation entry to be made
history/activity entries can be directly referenced in the conversation

Slightly separately the slack attachments approach seems quite nice, which includes types for links, buttons, etc...

We currently have WallPosts, the rest should be discussed further and added at a later time.

Probably things that could be done here:

[ ] add "type" (or similar) to conversation message entries (default is text, others might be markdown..., history/activity or something)
[ ] render them in the frontend different
[ ] add reactions!
[ ] add comments (ooh er, gets complicated, I think they need to be their own conversation so we can track read/notifications correctly)

I feel like we should plan the wall concept better. There was an idea to extend the wall in #741 with a list of all pickups that have open slots.
These "upcoming pickup alarms" are quite different from the other features proposed in the wall. The alarms stay until they are done (e.g. pickup done, all slots full, at least one slot filled), while the proposed wall features are mostly historic events (e.g. messages, who joined/left the group)
I think we should call the historic events the "feed" (in contrast to history, which shows all events), then we should have some "alarms" that consist of upcoming events of interest to the user (empty pickups, joined pickups).

I enabled markdown for wall messages (also retroactively), but didn't introduce other messages types yet.

Currently the wall conversation shows only people's messages. The upcoming pickups, as well as feedback to give, is displayed above. If we want the wall to become more like a news feed / dash board kind of thing we need to figure out how to go about it:

How to treat the data; are all wall posts conversation items?
How to display the different categories?
Probably much more...^^

The group wall seems to be the main location for notifications and group conversation, so we should be careful to keep it relevant to users.
If there's more information to display, it would be better to split them into separate categories, to be shown on different pages:

notifications: system-generated text, events that should have high priority to the user, need to be marked as read
activity: system-generated text and user messages, all latest events to scroll through, limited to most 30 most recent entries
conversation messages: only written by humans

If we separate notifications and conversation into different pages, then we don't have a dashboard, or is activity meant to be the dashboard? Could also be okay to not have one though, I'm mainly pointing it out...
Just to get more clarity on what you mean exactly with the three categories you mentioned, @tiltec, is it somewhat like this?:

conversation: the group wall
notifications: e.g. upcoming pickups I have signed up for, upcoming empty pickups
activity: pickups done, feedbacks given, stores created, but user messages as well? Isn't this a weird, partly duplication of content from the conversation? I'm doubtful about the usefulness of this page actually. Or did I get it wrong?


Update index.md

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@21728ef). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #2   +/-   ##
=========================================
  Coverage          ?   72.15%
  Complexity        ?      399
=========================================
  Files             ?       70
  Lines             ?     1232
  Branches          ?      125
=========================================
  Hits              ?      889
  Misses            ?      311
  Partials          ?       32

Continue to review full report at Codecov.

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


Adds invoice API and routes

Ready to rock and roll

This should be good to go now. The routes should be correct.


gogo/protobuf v1.3.1 vulnerability

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?
Hello, we have scanned the docker image with Aquasecurity Trivy vulnerability scanner.
Command:
# docker run --rm -v /var/run/docker.sock:/var/run/docker.sock -it aquasec/trivy:latest image --severity HIGH,CRITICAL traefik:v2.5.0-rc2
# docker run --rm -v /var/run/docker.sock:/var/run/docker.sock -it aquasec/trivy:latest image --severity HIGH,CRITICAL traefik:v2.4.11
# docker run --rm -v /var/run/docker.sock:/var/run/docker.sock -it aquasec/trivy:latest image --severity HIGH,CRITICAL traefik:v2.3.7

This has turned up the gogo/protobuf vulnerability from gogo/protobuf v1.3.1.
Can you please help to patch the issue in the docker image?
What did you see instead?
usr/local/bin/traefik (gobinary)
================================
Total: 1 (HIGH: 1, CRITICAL: 0)

+--------------------------+------------------+----------+-------------------+---------------+--------------------------------------+
|         LIBRARY          | VULNERABILITY ID | SEVERITY | INSTALLED VERSION | FIXED VERSION |                TITLE                 |
+--------------------------+------------------+----------+-------------------+---------------+--------------------------------------+
| github.com/gogo/protobuf | CVE-2021-3121    | HIGH     | v1.3.1            | v1.3.2        | gogo/protobuf:                       |
|                          |                  |          |                   |               | plugin/unmarshal/unmarshal.go        |
|                          |                  |          |                   |               | lacks certain index validation       |
|                          |                  |          |                   |               | -->avd.aquasec.com/nvd/cve-2021-3121 |
+--------------------------+------------------+----------+-------------------+---------------+--------------------------------------+

What version of Traefik are you using?
2.5.0-rc2, 2.4.11, 2.3.7
What is your environment & configuration?
N/A
If applicable, please paste the log output in DEBUG level
N/A

Hello,
github.com/gogo/protobuf is a transitive dependency for Traefik (we don't depend directly on it)
$ go mod why -m github.com/gogo/protobuf
# github.com/gogo/protobuf
github.com/traefik/traefik/v2/pkg/config/dynamic
k8s.io/apimachinery/pkg/runtime
github.com/gogo/protobuf/proto

We use k8s.io/apimachinery/pkg/runtime only for DeepCopy functions, and not in the context of protobuf.
Then, from the point of view, it's not an issue.

Hi @ldez,
This is happening when scanning the Traefik docker image from our CI/CD Pipeline, so I believe it is not a transitive dependency but one which is included (albeit indirectly).
I found that running go get -u github.com/gogo/protobuf adds a new entry to go.mod with the right version in the v2.5 branch and makes a few updates to go.sum as well in v2.4 branch.
This should solve the problem.

I request you to please try it for yourself. Scan your docker image with the scanner using the commands I provided in this issue and confirm the bug. Then I will submit another PR.

It's a transitive dependency:
$ go mod why -m github.com/gogo/protobuf
# github.com/gogo/protobuf
github.com/traefik/traefik/v2/pkg/config/dynamic
k8s.io/apimachinery/pkg/runtime
github.com/gogo/protobuf/proto

It's a false positive of your vulnerability scan because we don't use this lib.

The issue is even if you are not using it, the vulnerability is coming up in the traefik binary inside Docker.
We cannot complete our deployment using your docker image as we were able to do previous to this vulnerability finding.
Therefore we are stuck on an old release v2.3.0 which is itself vulnerable to this.
Our only option then would be to fork your repo for the purposes of fixing this bug until the runtime module updates this on their side.

Once again it's a false positive, you have to add an exclusion in your scanner.
There is no vulnerability.
FYI, the lib has been updated in v2.5.0-rc3

Thank you for updating it in 2.5.0-rc3.
I was about to point out that apimachinery updated it in the runtime module already :)
We will upgrade to this release to avoid the issue as we try to avoid whitelisting whenever possible.

I'd like to point out that I am also seeing this vulnerability when I scan the traefik binary itself which is extracted from the v2.4.11 tarball release. Is there any way you can please consider that as a valid vulnerability?
I don't understand how a statically linked compiled binary which is downloaded from your repo can possibly be flagged for a vulnerability that is in a transitive library. I could understand if this was compiled as dynamic linked binary then this could be transitive, because the external library can be ignored, but traefik is statically linked and so this vulnerable code must be present somewhere in the binary. If this was a transitive library then this vulnerability would not appear in the output from scanning your binary.
Please advise?

$ go mod why -m github.com/gogo/protobuf
# github.com/gogo/protobuf
github.com/traefik/traefik/v2/pkg/config/dynamic
k8s.io/apimachinery/pkg/runtime
github.com/gogo/protobuf/proto

The package k8s.io/apimachinery/pkg/runtime is used the DeepCopyInto of one element in the configuration in the package github.com/traefik/traefik/v2/pkg/config/dynamic.
https://github.com/traefik/traefik/blob/36ffdf548dc197e10ad53f87797dbc5e11792e72/pkg/config/dynamic/plugins.go#L15
The package github.com/gogo/protobuf/proto is used by the package k8s.io/apimachinery/pkg/runtime.
The package k8s.io/apimachinery/pkg/runtime contains several files with several functions.
The vulnerability of the package github.com/gogo/protobuf/proto is related to the file plugin/unmarshal/unmarshal.go, the vulnerabilities occur only when you unmarshal from protobuf.
We use the package k8s.io/apimachinery/pkg/runtime but we don't use the file pkg/runtime/serializer/protobuf/protobuf.go and the file plugin/unmarshal/unmarshal.go because we don't unmarshal from protobuf because we only use the JSON features.
So we are not affected by this vulnerability because we don't use the specific part that has a vulnerability.
Your scanner is just analyzing the dependency without evaluating where is the vulnerability.


Module not found: Can't resolve 'react-google-maps'

Hi there
I get this message and I don't know why:
Module not found: Can't resolve 'react-google-maps' in '/usr/src/app/src/components'
I tried to delete node_modules folder, tried various versions of your library but it didn't help. Curently I use React 16.4.0 and react-google-maps 9.4.5. I don't use typescript as the other users with the same problem.

could you post your code,  especially how you imported 'react-google-maps' in your code

Same problem here. Its from the youtube turorial of le wagon about react.
Here is my code:
import React, { Component } from 'react';
// import logo from './logo.svg';
import './App.css';
import Flat from "./components/flat";
import GoogleMapReact from 'google-map-react';

class App extends Component {
  constructor(props){
    super(props);
    this.state = {
      flats: []
    };
  }

  componentDidMount() {
    const url = "https://raw.githubusercontent.com/lewagon/flats-boilerplate/master/flats.json";
    fetch(url) //AJAX
      .then(response => response.json())
      .then((data) => {
        this.setState({
          flats: data
        });
      });
  }

  render() {

    const center = {
      lat: 52.520008 ,
      lng: 13.404954
    };

    return (

            {this.state.flats.map((flat) => {
              return <Flat flat={flat} />
            })}

        <GoogleMapReact
          // bootstrapURLKeys={{ key: /* YOUR KEY HERE */ }}
          defaultCenter={center}
          defaultZoom={11}
        >
          {/* <AnyReactComponent
            lat={59.955413}
            lng={30.337844}
            text="My Marker"
          /> */}
        </GoogleMapReact>

    );
  }
}

export default App;

Module not found: Can't resolve 'google-map-react' in ...

Same here :
`
import React from 'react';
import GoogleMapReact from 'google-map-react';
import data from '../../food_trucks.json';
const AnyReactComponent = ({ text }) => {text};
class Map extends React.Component {
constructor(props) {
super(props);
this.state = {
places: data,
};
this.props = {
center: {
lat: 59.95,
lng: 30.33
},
zoom: 11
};
this.props.center.lat = this.state.places.coordonnees_wgs84.lat;
this.props.center.lat = this.state.places.coordonnees_wgs84.lon;
}
render() {
    return (

            <GoogleMapReact
            bootstrapURLKeys={{ key: '' }}
            defaultCenter={this.props.center}
            defaultZoom={this.props.zoom}
            >
            <AnyReactComponent
                lat={59.955413}
                lng={30.337844}
                text="My Marker"
            />
            </GoogleMapReact>

    );
}

}
export default Map;
`
And my package.json :
{
"name": "react-lab",
"version": "0.1.0",
"private": true,
"dependencies": {
"@material-ui/core": "^4.5.0",
"@material-ui/icons": "^4.4.3",
"google-maps-react": "^2.0.2",
"react": "^16.10.2",
"react-dom": "^16.10.2",
"react-redux": "^7.1.1",
"react-scripts": "3.2.0",
"recharts": "^1.7.1",
"redux": "^4.0.4"
},
"scripts": {
"start": "react-scripts start",
"build": "react-scripts build",
"test": "react-scripts test",
"eject": "react-scripts eject"
},
"eslintConfig": {
"extends": "react-app"
},
"browserslist": {
"production": [
">0.2%",
"not dead",
"not op_mini all"
],
"development": [
"last 1 chrome version",
"last 1 firefox version",
"last 1 safari version"
]
}
}

@banibanc
The repo of this project is unmaintained more than a year, and we had build new version https://www.npmjs.com/package/@react-google-maps/api
We had rewrite it to TypeScript, and updating it frequently: https://github.com/JustFly1984/react-google-maps-api/tree/master/packages/react-google-maps-api
You can enjoy autocomplete.
You can see our docs: https://react-google-maps-api-docs.netlify.com/
Also a lot of examples: https://react-google-maps-api-gatsby-demo.netlify.com/ https://github.com/JustFly1984/react-google-maps-api/tree/master/packages/react-google-maps-api-gatsby-example/src/examples
The bundle size is much smaller: https://bundlephobia.com/result?p=<EMAIL_ADDRESS>Enjoy!

Thanks !

@banibanc
The repo of this project is unmaintained more than a year, and we had build new version https://www.npmjs.com/package/@react-google-maps/api
We had rewrite it to TypeScript, and updating it frequently: https://github.com/JustFly1984/react-google-maps-api/tree/master/packages/react-google-maps-api
You can enjoy autocomplete.
You can see our docs: https://react-google-maps-api-docs.netlify.com/
Also a lot of examples: https://react-google-maps-api-gatsby-demo.netlify.com/ https://github.com/JustFly1984/react-google-maps-api/tree/master/packages/react-google-maps-api-gatsby-example/src/examples
The bundle size is much smaller: https://bundlephobia.com/result?p=<EMAIL_ADDRESS>Enjoy!

Hello there,
I cannot load the map, with error msg Module not found: Can't resolve<EMAIL_ADDRESS>in
I installed via yarn add @react-google-maps/api
This is on a newly created react project app. React v: 16.10.2

npm i react-google-maps --force


How to correctly use a generic? View blank and onViewCreated() not called in Fragment nor Base

I have an app with lots of fragments. It does not use view models. I have been using BaseFragment() : Fragment() as I need onCreateView() and onViewCreated() to do all of the same stuff in every view (set entry animations and add an animation delay for the transitions).
Following issue tracked previously here
I attempt to setup a new BaseVBFragment as such
abstract class BaseVBFragment<VB : ViewBinding>(viewBindingClass: Class<VB>) : Fragment() {

    protected val binding: VB by viewBinding(viewBindingClass)

    override fun onCreateView(inflater: LayoutInflater, container: ViewGroup?, savedInstanceState: Bundle?): View? {
        Timber.d("-> onCreateView()")
        setHasOptionsMenu(true)
        setEntryAnimations()
        return super.onCreateView(inflater, container, savedInstanceState)
    }

    override fun onViewCreated(view: View, savedInstanceState: Bundle?) {
        Timber.d("-> onViewCreated()")
        super.onViewCreated(view, savedInstanceState)
        delayAnimation(view)
    }

    override fun onResume() {
        logFragmentAnalytics()
        super.onResume()
    }
}

I setup my Fragment as such
class MyFragment : BaseVBFragment<MyFragmentBinding>(MyFragmentBinding::class.java) {

    override fun onViewCreated(view: View, savedInstanceState: Bundle?) {
        Timber.d("-> onViewCreated()")
        super.onViewCreated(view, savedInstanceState)
    }

    override fun onResume() {
        Timber.d("-> onResume()")
        super.onResume()

        // Can't access the Fragment View's LifecycleOwner for MyFragment{f4db0e9} when getView() is null i.e., before onCreateView() or after onDestroyView()
        observable.observe(viewLifecycleOwner) { /* do something on event */ }
    }

}

So with the error of not being able to access viewLifecycleOwner in onResume(), I moved that to MyFragment.onViewCreated()
This resolved the hard error but the view is completely blank. Looking at logs, MyFragment nor BaseVBFragment runs onViewCreated().
ActivityExtensionsKt                      D  -> hideSoftKeyboard()
BaseVBFragment                            D  -> onCreateView()
UpdateEmai...ssFragment                   D  -> onResume()
FragmentExtensionsKt                      D  -> logFragmentAnalytics()
FrameEvents                               E  updateAcquireFence: Did not find frame.
FrameEvents                               E  updateAcquireFence: Did not find frame.
FrameEvents                               E  updateAcquireFence: Did not find frame.
...

Hi. I didn't find where you access ViewBinding instance in your code. The most common mistake is accessing it in callback of async calls. Before that you need to check that you view is still exists:
class AnyFragment : Fragment {

    fun anyFuncation() {
         // Start operation or subscribe on Flow/LiveData/Observable
         // that call callback async
         source.doOnResult {
<EMAIL_ADDRESS>!= null) {
                 //do operations using ViewBinding instance
             }
         }
    }
}


[CAMEL-15262] Fix argument order in new ExponentialBackoffRetry call in ZooKeeperCuratorHelper

Fix reversed order of arguments maxRetries and maxSleepMs in constructor
call of ExponentialBackoffRetry in ZooKeeperCuratorHelper.createCurator
[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] If you're unsure, you can format the pull request title like [CAMEL-XXX] Fixes bug in camel-file component, where you replace CAMEL-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run mvn clean install -Psourcecheck in your module with source check enabled to make sure basic checks pass and there are no checkstyle violations. A more thorough check will be performed on your pull request automatically.
Below are the contribution guidelines:
https://github.com/apache/camel/blob/master/CONTRIBUTING.md

Can you create the same Pr for camel-3.4.x branch? Thanks.


Replace the ENV vars of the Dashboard with a YAML file

Regarding to the review of  https://github.com/SeaCloudsEU/SeaCloudsPlatform/pull/47 we found an interesting way to replace enviroment variables that wires the entire project with the Dashboard.  Maybe as we are using Dropwizard.io to deploy the dashboard, we can use the configuration YAML to setup all the necessary parameters.

Closed by #60