Update template source documentation

Fixes https://github.com/Azure/azure-dev/issues/4603

Update the template source example snippet to follow the proper format for user-configured sources
Include brief description of each JSON property
Add link to a full example, which we recommended in Azure Developer CLI (azd) – September 2023 Release
Other minor fixes, such as correcting --displayName to --name

Hi @JeffreyCA - internal contributors should submit pull requests against the internal/private version of the repo - azure-dev-docs-pr - so that we can get full build validation and preview builds. Could you please close this PR and reopen it in azure-dev-docs-pr? If you're using the web-based editor, that's fine, just be aware that it defaults to the public repo, so you need to update the repo name in the address bar before you proceed. Thanks!

Hi @JeffreyCA - internal contributors should submit pull requests against the internal/private version of the repo - azure-dev-docs-pr - so that we can get full build validation and preview builds. Could you please close this PR and reopen it in azure-dev-docs-pr? If you're using the web-based editor, that's fine, just be aware that it defaults to the public repo, so you need to update the repo name in the address bar before you proceed. Thanks!

My bad! Created it here: https://github.com/MicrosoftDocs/azure-dev-docs/pull/1420


Trying to delete a federated graph raises an error

Component(s)
cli
Component version
latest
wgc version
latest
controlplane version
latest
router version
latest
What happened?
Description
When trying to delete a federated graph, an error occurs. Other federated commands works. API KEY and API URL are correctly set
Steps to Reproduce
npx wgc federated-graph delete GRAPH-NAME
Expected Result
Should delete the federated
Actual Result
An error is raised
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Package Manager: pnpm, npm, yarn, etc
Compiler(if manually compiled): (e.g., "go 14.2")
Router configuration
No response
Router execution config
No response
Log output
{"type":"S3ServiceException","message":"The Access Key Id you provided does not exist in our records.","stack":"InvalidAccessKeyId: The Access Key Id you provided does not exist in our records.\n    at throwDefaultError (/app/node_modules/.pnpm/@smithy+smithy-client@2.4.2/node_modules/@smithy/smithy-client/dist-cjs/index.js:838:20)\n    at /app/node_modules/.pnpm/@smithy+smithy-client@2.4.2/node_modules/@smithy/smithy-client/dist-cjs/index.js:847:5\n    at de_CommandError (/app/node_modules/.pnpm/@aws-sdk+client-s3@3.529.1/node_modules/@aws-sdk/client-s3/dist-cjs/index.js:4756:14)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async /app/node_modules/.pnpm/@smithy+middleware-serde@2.1.3/node_modules/@smithy/middleware-serde/dist-cjs/index.js:35:20\n    at async /app/node_modules/.pnpm/@aws-sdk+middleware-signing@3.523.0/node_modules/@aws-sdk/middleware-signing/dist-cjs/index.js:192:18\n    at async /app/node_modules/.pnpm/@smithy+middleware-retry@2.1.4/node_modules/@smithy/middleware-retry/dist-cjs/index.js:320:38\n    at async /app/node_modules/.pnpm/@aws-sdk+middleware-sdk-s3@3.525.0/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:97:20\n    at async /app/node_modules/.pnpm/@aws-sdk+middleware-sdk-s3@3.525.0/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:120:14\n    at async /app/node_modules/.pnpm/@aws-sdk+middleware-logger@3.523.0/node_modules/@aws-sdk/middleware-logger/dist-cjs/index.js:33:22","name":"InvalidAccessKeyId","$fault":"client","$metadata":{"httpStatusCode":403,"requestId":"17DC90321B4617BE","attempts":1,"totalRetryDelay":0},"Code":"InvalidAccessKeyId","BucketName":"cosmo","Resource":"/cosmo/","RequestId":"17DC90321B4617BE","HostId":"1767b1a2-81d3-44e4-a99d-5178d69bfd55"},"msg":"The Access Key Id you provided does not exist in our records."}

Additional context
No response

Nevermind, this is due to the user access permission within minio, not the apiKey.


Update llama_index imports

Going through the tutorial I found that llama_index was restructured recently (in the last month?) so these imports had to be changed to work correctly

Thanks buddy @sestinj this is helpful :)


favicons

The Matrix Movies Website could use favicons.
Please choose a drawing or photo that could represent this website and will look good when it's small.
Here's a handy tool:   https://favicon.io/favicon-converter/ will generate all the favicons if you give it an image.
Please put all the favicons into /img/favicons/  instead of the root, so that the root doesn't get crowded with too many files.
Then add code like this to all of the html files:   Make sure to update the file paths below.
<link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png">
<link rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="/favicon-16x16.png">
<link rel="manifest" href="/site.webmanifest">

Hi @roannav , assign to me, please!

@ivanetra Thanks!  You're assigned.

@ivanetra Thanks! You're assigned.

Thanks @roannav !


Juniper and Thebelab

Juniper and Thebelab seem to tackle the same problem, with -- if I understood correctly -- similar approaches. Is there an intrinsic reason preventing the two project to converge? E.g. by merging Juniper's cool additional goodies (e.g. CodeMirror cells, ...) into Thebelab?
Cheers,
Nicolas

@nthiery @Miniland1333 Sorry for only getting to this now. To give you some background:

Is there an intrinsic reason preventing the two project to converge? E.g. by merging Juniper's cool additional goodies (e.g. CodeMirror cells, ...) into Thebelab?

I started off by using Thebelab and later a custom build of it, but I ended up rewriting it pretty much from scratch in a way that makes it easier for me to maintain, especially for use in the spaCy site. At that point, I thought it was fairest to maintain my own fork instead of trying to push all my changes upstream.
For example, I would never go and open a PR on someone else's project like "Replace jQuery because I personally dislike it" – I think that's unfair to fellow OSS maintainers. If I want to rewrite code like this, I need to accept the maintenance burden and fork it.
But of course, everything I changed and did is open-source and published as MIT, so it can be reused by others or adopted again.


Style Guide (Discussion)

Let's leave this as a running dialog about stylistic choices so that we discuss our preferences and what the best practices are that we should follow on future projects.

Just curious about the underscore for class methods.  I've been following this pattern since picking up the code, but am just wondering if there is a reason for it?
Here is what the AirBnb style-guide says, not that we always need to follow it.

The styling follows grommet core's styling which essentially adds underscores to a component's methods. In my personal JS projects outside of React, I like the pattern of using underscores for private methods but that doesn't make much sense once you're in the React eco-system.
I lean towards AirBnB's setup for most styling however it'd be a pain to remove the underscores at this point.

Yeah, I agree with that!!  No sense in making drastic changes this late in the game, We can bookmark these decisions for future projects.


Per-config LSP tests

Some initial discussion at #1059.
Currently the plan is to create a new repo under nvim-lua that will be a place to put per-config tests to test basic LSP integration of that language, at least as far as implemented by its lua/lspconfig/*.lua file.
@mjlbach WIP prototype at rish987/nvim-lspconfig-test. At the moment, what the workflow does is, for each language server in the tests/ directory:

runs the test.sh file
if:
-- error and no existing issue, automatically creates one titled for that specific language server
-- error and existing issue, does nothing
-- no error and existing issue, automatically closes it
-- no error and no existing issue, does nothing

Will make a few more improvements add ACTUAL tests for leanls/lean3ls soon (likely tommorrow, in fact)!

(CC: @Julian)

Alright it should be ready for a detailed review at this point! @ rish987/nvim-lspconfig-test. I've added you both as collaborators, feel free to make any changes as you see fit. Also feel free to test the automatic issue creation out by causing errors (e.g. rish987/nvim-lspconfig-test@7646a40).

I've really been wanting to get this done for https://github.com/williamboman/nvim-lsp-installer. I think we should join forces on this, where nvim-lsp-installer could fill in the gap and shoulder the responsibility of server installation/management.

The issue is tests might be extremely annoying to maintain,as if we checked for specific responses from the language server this would be heavily tied to the version of the server itself. We could pin the version of the language servers to mitigate this but that semi-defeats the point. I guess I would recommend a pinned + non-pinned tests so we know if the regression is from lspconfig or from the server.

Ah that's good to know, I'm not very familiar with those details. I was actually thinking testing further out in the stack, like user acceptance testing. The interfaces that would be involved would exclusively be core neovim APIs (like buffer contents, cursor position, etc.). I think if combined with a BDD-approach, it could be a pretty low maintenance effort (mostly a one-time cost initially).
Feature: tsserver

  Scenario: Go to a buffer-local definition
    Given a file "index.ts" with the contents
        """
const my_number = 5

console.log(my_number)
        """
    And a cursor position of "3:13"
    When I go to definition
    Then cursor position should be "1:7"

The above could be further parameterized to avoid having to individually write these for each server. Maybe the resolved capabilities could govern which features should be tested. Also, maybe treesitter could be used to construct ASTs that then  are translated into a given source language, to be used as fixture files in tests.
I think a good start would be to just keep it simple and expand from that. I vaguely know there's the concept of "initializing a server" that is part of the spec - maybe that could be the first target to test, that each server successfully initialize?

I don't understand how that is different than the extensive testing we already do of the built in client in core.

Well yes and no. I'm not too familiar with what those tests do, but I imagine they're primarily testing the client implementation and spec compliance? What I'm after is testing and verifying that each of the server configurations provided by lspconfig actually work in an acceptable manner, and as a precursor to that that the installation in nvim-lsp-installer is correct.

I'd say that depends on what you're inspecting and asserting on. If you take the perspective of an end-user, you have (rightfully) no idea what the server is responding to the neovim client in the background, or even that there even is an LSP server running. All you know is whether go to definition, rename, find references, etc. is working. Those are all user actions that have a pretty clear motive and an expected result. Building out a test scenario that performs those user actions and observes that expected behavior takes place could prove pretty useful I think, for many reasons.

Hi there, thanks for your interest! I've just recently started to get back into testing. In the experimental repo rish987/nvim-lspconfig-test I have the requirement to "formalize" the install steps of nvim-lspconfig for each server in the form of a BASH script, but your plugin seems to be much more in the right spirit of neovim. So we can start by replacing that layer with nvim-lsp-installer.

I think what would be even better is acceptance tests that would run in a neovim instance end-to-end, and make sure that servers actually start properly and are responding reliably to client requests.

I've already added these for Lean 3 and 4 servers in that repo, see for example https://github.com/rish987/nvim-lspconfig-test/blob/master/tests/leanls/tests/lsp_spec.lua. It tests that hover and definition requests and client creation work as they should on Lean files in the different kind of project structures we're supposed to support.

The issue is tests might be extremely annoying to maintain,as if we checked for specific responses from the language server this would be heavily tied to the version of the server itself.

This problem could be minimized if we're careful about how much we're testing. For example it that test file above I just check for a small portion of the hover response that I would expect never to change between versions.

I guess I would recommend a pinned + non-pinned tests so we know if the regression is from lspconfig or from the server.

Yes I think this is something that will be necessary as well. When a PR comes in for new tests for a server we could also require that they provide an nvim-lsp-installer script for a fixed version, and test both in CI.

Maybe the resolved client capabilities could govern which features should be tested (have to bear in mind dynamic capability registration though).

We could separate tests by file (e.g. definition, hover, etc.) and have a helper that errors if the capability corresponding to that file isn't supported by the server. But to start I think we should keep it simple and assume fixed capabilities across server versions.

Also, maybe treesitter could be used to construct ASTs that then are translated into a given source language, to be used as fixture files in tests.

This sounds very interesting and ambitious -- has it been done before? I'd imagine we'd need to unify parts of treesitter grammars between languages to make this happen. And to do so we'd probably initially need to have some protocol/standard that everyone can agree on. (I don't know enough about treesitter yet to know whether this has already been done...) But I think we'll have to start out by just writing tests manually.

I'd probably rather just write a dockerfile per server than rely on nvim-lsp-installer as we can pin the system packages as well (and we need to set up system dependencies anyways). I kinda started this in https://github.com/nvim-lsp/try.nvim. We could share the rest of the testing infrastructure though.

This sounds very interesting and ambitious -- has it been done before? I'd imagine we'd need to unify parts of treesitter grammars between languages to make this happen. And to do so we'd probably initially need to have some protocol/standard that everyone can agree on. (I don't know enough about treesitter yet to know whether this has already been done...) But I think we'll have to start out by just writing tests manually.

This was just a vague idea I came up with with not much forethought to be honest. There probably could be benefits of taking such an approach, but the complexity would skyrocket. Starting small and iterating fast is the way to go for sure :+1:

I'd probably rather just write a dockerfile per server than rely on nvim-lsp-installer as we can pin the system packages as well (and we need to set up system dependencies anyways). I kinda started this in https://github.com/nvim-lsp/try.nvim. We could share the rest of the testing infrastructure though.

With the risk of me just talking about vague, unmaterialized, ideas - I've had the idea of further decoupling the different components in nvim-lsp-installer, going from having installers represented as composed Lua functions that spawn processes (or other system operations) on the host system to instead providing static descriptions of system requirements and the install steps. That'd allow for a number of different use cases, like translating it to platform-specific jobs that run on the host system, compiling to a different format such as a Dockerfile. Having access to these static descriptors would also improve the quality and maintainability of certain plugin-specific GUI features (and probably a nicer interop with plugins like distant.nvim).
I'll see if I can contribute anything to what you've gotten started with @rish987. I might also just start by targeting some of the problems I'd like to solve for nvim-lsp-installer first, and then we can circle back at a later time and re-evaluate

See https://github.com/rish987/nvim-lspconfig-test/pull/57 for a working POC.

Seems like https://github.com/williamboman/mason.nvim owns this.
Definitely out of scope for this repo, which is just a collection of data, not a project that intends to support every random lsp server.


Fix functionality of Go To Definition for properties set/get

Closes #67927
Adds new case statement for GDScriptParser::Completion_Property_Method which allows using ctrl + Left click to go to function definition

Just realized it's your first contribution! Congratulations! :tada:

Thanks! And congrats for your first merged Godot contribution :tada:


Feature request: Query time shift / specify time interval

In our old data visualization system (a bunch of JS and HighCharts) we split the time series into multiple ones by their year, so we could plot a year-over-year chart

Like this
I'm thinking how I could replicate a similar thing in Grafana and the built-in timeshift feature was implemented by the datasource. I would probably try stacking multiple -1y, -2y, -3y etc queries. It would be manual, but it would work.
Outputting multiple time series directly by a specified time interval would be best but I don't know if that would be outside scope of this plugin.
(The new Grafana time series transformations could have something like this but as far I can see, they don't in their current featureset. In fact, they seem to be made with the opposite idea: merging series. )

Splitting query results into multiple series is something that's been requested for my other data source as well. This will definitely happen as soon as I figure out the UX for it. Ideally I'd like for the data sources to work for any data—not only time series.
When it comes to time shifts, I believe this is a generic feature to all data sources which means there's a chance we'll see improved support in Grafana itself. While I recognize that it would be a useful feature, I probably will be prioritizing feature that are more specific to this plugin. I might reconsider if this turns out to be frequented requested.


Store app id and app secret

Proposed Changes

(Describe the changes and rationale behind them)

Related Issues

(Github link to related issues or pull requests)

Codecov Report

Merging #55 (6abf6e5) into main (b8aadd6) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #55   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            6         6
  Lines          307       309    +2
  Branches        38        38
=========================================
+ Hits           307       309    +2

Impacted Files
Coverage Δ

src/youtubeaio/youtube.py
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


~~FrEe!! Robux hOw tO GeT Free robux iN RoBlOx 100% WoRkInG In 2024 WiThOuT SuRvEy & vErIfIcAtIoN

Getting free Roblox free robux gift card codes through legitimate means usually involves participating in online surveys, reward websites, and promotional events. Here are some effective methods to earn free Roblox gift codes:
🔴💎👉👉CLICK HERE TO GET FREE NOW
🔴💎👉👉 CLICK HERE TO GET FREE NOW
While there is no way to get free Robux without some effort, there are a few legitimate methods that can help you earn Robux for free. We condemn and don’t recommend the use of any illegal tools such as Robux generators or gambling websites. With that being said, let us discuss the best ways to get free Robux in Roblox.
You can earn free Robux using Microsoft Rewards, and it is the best. You just have to do some odd jobs on Bing and perform some specific searches to earn reward points. Then, you can redeem these Microsoft Reward points to get free Roblox with ease. However, the Robux gift card comes and goes in the Microsoft Reward section. Currently, you can earn 800-1000 Robux from Microsoft Rewards.
You need to go to the Microsoft Rewards option to see your points first. Once there, find the Redeem option and you will see the Roblox Digital Card option. You can buy it if you have enough points and redeem the code later on the Roblox website.
Using a free Robux generator without human verification will typically involve the following steps:
Give the Roblox user name.
Verify the profile.
Input the amount of Robux you want to generate.
Click on the generate button.
Wait and enjoy the game.
If you are using free Robux generator 2021, then There are a number of contests run on the web every month where the winner will either go home with some genuine Robux or cash.

NO.

@jhkennedy let's delete instead of close? Maybe it would be better to email GitHub support than go through them all manually? :grimacing:


Kapacitor 0.13.0: Simple task creation example in documentation isn't correct

Page: https://github.com/influxdata/kapacitor/blob/master/client/API.md#tasks
Documentation example says you can do:
POST /kapacitor/v1/tasks/
{
    "id" : "TASK_ID",
    "type" : "stream",
    "dbrps": [{"db": "DATABASE_NAME", "rp" : "RP_NAME"}],
    "script": "stream\n    |from()\n        .measurement('cpu')\n"
}

However, doing so results in an error. You can make this work if you do:
POST /kapacitor/v1/tasks/
{
    "id" : "TASK_ID",
    "type" : "stream",
    "dbrps": [{"db": "DATABASE_NAME", "rp" : "RP_NAME"}],
    "script": "stream\n    |from()\n        .measurement('cpu')\n",
    "status": "enabled"
}

@mglazer Thanks for filing these issues. I'll make sure we get a fix out today on these. Sorry for the hassle.


Added new TypeScript description file.

Here is the definition file we created. If you like great, if not that's okay too. However, if you see any issues with please let us know. Thanks.

That looks great, thanks for your work! I never worked with TypeScript, so a silly question: Does the implementation work with ReadOnlyBitSet and the current BitSet.js implementation?

And does the def file not need an entry in the package.json file?

In TS the 'shape' is what is important not the inheritance structure. Therefore, the ReadOnlyBitSet should have the right 'shape' as the BitSet. However, we haven't tested it since I just added the interface a few days ago. If you could create a set of unit tests for it that would be great!


fix "excess flood" issue on Freenode IRC

issue: https://developer.pidgin.im/ticket/11089
patch: https://gist.github.com/imcleod/77f38d11af11b2413ada

Updated AUR package


Separate actions for report issue and request API key dialog and move them to the epics

Verified on Prod successfully

@Alexander-Kezik We need to create and apply a patch to 0.10 version

Verified with 0.10.3 patch successfully


Spring Reverb 1.0.1 Polyphony?

Hi Martin, on 1.0.1 Spring Reverb is polyphonic in but not out - is this the expected behaviour?
Thanks.

Yes, I did not see the point in a polyphonic reverb, as it would usually be used as effect. The input then has the standard behaviour of mixing the channels. Do you think a polyphonic reverb would make sense?


Unable to package spring boot with cloud config jar

Hi,
I am trying to assemble spring boot with cloud config client jar but it not assembling properly due to wrong spring.factories file.
No existing merge strategy properly merge spring.factories files

I am facing the same issue. can anyone help?

@jackyin5918 by using https://www.scala-sbt.org/sbt-native-packager/gettingstarted.html
I resolve this.
I created jar file of my project without dependency and exported all project dependency jars in different folder using sbt native packaging and run the project jar with added dependency in class path.

@AjitTK Thank you for sharing.
I just saw your comment. and I was trying this https://github.com/xerial/sbt-pack, looks like the same approach to solve this issue.

just:
assemblyMergeStrategy in assembly := {
case PathList("META-INF", ps @ _) if ps.contains("MANIFEST.MF")    => MergeStrategy.discard
case PathList("META-INF", ps @ _) if ps.contains("spring.factories") || ps.contains("spring.handlers") || ps.contains("spring.schemas")
=> MergeStrategy.concat
}

just:
assemblyMergeStrategy in assembly := {
case PathList("META-INF", ps @ _) if ps.contains("MANIFEST.MF")    => MergeStrategy.discard
case PathList("META-INF", ps @ _) if ps.contains("spring.factories") || ps.contains("spring.handlers") || ps.contains("spring.schemas")
=> MergeStrategy.concat
}

@KhankaLake this strategy is not working. multiple entries of same loader class give you error. Validate this by implementation.

@KhankaLake this strategy is not working. multiple entries of same loader class give you error. Validate this by implementation.

This works for me:
  case PathList("META-INF", "spring.factories") => new MergeStrategy {
    import java.io.ByteArrayInputStream
    import java.nio.charset.StandardCharsets
    import java.util.Properties
    import scala.jdk.CollectionConverters.*

    override val name: String = "merge-spring.factories"
    override def apply(tempDir: File, path: String, files: Seq[File]): Either[String, Seq[(File, String)]] = {
      val allFactories = files.foldLeft(Map.empty[String, List[String]]) { (acc, file) =>
        val props = new Properties()
        IO.load(props, file)
        val factories = props.asScala.map { case (name, classes) => name.trim -> classes.split(',').map(_.trim).toList }
        acc ++ factories.map { case (name, classes) => name -> (classes ++ acc.getOrElse(name, List.empty)) }
      }

      // use custom properties formatting because 'Properties.store' appends date to result
      // (we hope that nobody will use non-ASCII characters in class names)
      val file = MergeStrategy.createMergeTarget(tempDir, path)
      val lines = "# merged spring.factories\n\n" + allFactories.map {
        case (name, classes) => s"$name=${classes.mkString("\\\n", ",\\\n", "\n")}"
      }.mkString("\n")
      IO.write(file, lines.getBytes(StandardCharsets.ISO_8859_1))

      Right(Seq(file -> path))
    }
  }

A few notes:

it uses unix newlines to generate the same results on Windows
Properties.store is not used because it

always adds comment with current date (making build non-repeatable)
escapes newlines, making results less readable

I'm using old API


[SPARK-50493][BUILD] Migrate kubernetes-client to 7.0.0

What changes were proposed in this pull request?
The pr aims to migrate kubernetes-client from 6.13.2 to 7.0.0, includes:

upgrade kubernetes-client from 6.13.2 to 7.0.0.
switch default HttpClient implementation from OkHttp to Vert.x.

Why are the changes needed?

The full release notes: https://github.com/fabric8io/kubernetes-client/releases/tag/v7.0.0
Vert.x as default HttpClient implementation

Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass GA.
Was this patch authored or co-authored using generative AI tooling?
No.

After more than a week of investigation and research, when we upgraded Kubernetes client from 6.x to 7.0 and switched default HttpClient implementation from OkHttp to Vert.x, the issue of Kubernetes Integration test failure has been resolved.
The root cause is that some thread attributes daemon of Vert.x are set to false, so that after using ProcessBuilder to start the spark application on K8S (based on spark-submit), the main thread has already ended, but the above threads will not end, resulting in the overall process based on spark-submit not ending either.

cc @dongjoon-hyun @pan3793 @Yikun @LuciferYang

Please restore okio version to 1.17.6 explicitly.
It's because the downgrade is not supposed to be happen.
- okio/1.17.6//okio-1.17.6.jar
+ okio/1.17.2//okio-1.17.2.jar

Okay.

FYI, okio 1.7.16 was CVE-related updated, @panbingkun .

https://github.com/apache/spark/pull/47758

cc @roczei , @yaooqinn from #47758

+1 if that's the only one.

+1 if that's the only one.

Yea, I use following command to analy it. Currently, that's the only one.
./build/mvn dependency:tree -Phadoop-3 -Phadoop-cloud -Phive-thriftserver -Pkinesis-asl -Pspark-ganglia-lgpl -Pkubernetes -Pvolcano -Pyarn -Pdocker-integration-tests -Pconnect -Phive -Pyarn -Pjvm-profiler > dependency/20241216.txt

I think this PR can wait a little longer, because after https://github.com/fabric8io/kubernetes-client/pull/6726 is fixed, this PR can be simpler, see the following discussion: https://github.com/fabric8io/kubernetes-client/issues/6709#issuecomment-2545071491

Thank you for the info, @panbingkun . Yes, let's wait.

The version 7.0.1 has been released, and this PR has also been updated synchronously.
It now looks much simpler.

Thank you for syncing with 7.0.1, @panbingkun .

Okay, I'll update it.

The LICENSE of the newly added 4 jars are as follows:

Jar
LICENSE
URL

io.vertx:vertx-auth-common
Apache License Version 2.0
https://github.com/eclipse-vertx/vertx-auth/blob/master/LICENSE.txt

io.vertx:vertx-core
Eclipse Public License 2.0 or Apache Software License 2.0
https://github.com/eclipse-vertx/vert.x/blob/master/LICENSE.md

io.vertx:vertx-web-client
Apache License Version 2.0
https://github.com/vert-x3/vertx-web/blob/master/LICENSE.txt

io.vertx:vertx-web-common
Apache License Version 2.0
https://github.com/vert-x3/vertx-web/blob/master/LICENSE.txt

+1 for the above comment about LICENSE .
In addition, to be safe, please keep the original okhttp version by overriding the transitive dependency, @panbingkun . We had better handle okhttp upgrade independently, too.
- okhttp/3.12.12//okhttp-3.12.12.jar
+ okhttp/3.14.2//okhttp-3.14.2.jar

Done.
But I'm not sure if the LICENSE I added for these 4 newly added jars is correct.
I have added the original LICENSE of the 4 newly added jars in the comments for everyone to review.
@pan3793 @dongjoon-hyun Can you help me take a look at it?

BTW, sorry for the late response, @pan3793 .


How do u customise the table of contents for the scrollspy

i would like to change the line color from red to my accent color for the scroll spy and i would also like it to work on a horizontal view with my nav bar instead of the vertical view. I cannot seem to find any instructions on your page how to achieve this. and ideas on what i should do to achieve it

Closed due inactivity, feel free to reopen it if it is still necessary.


Feature/capture js console output

Problem Statement
There is no visibility into web console out that may contain errors
Solution
Add a listener to output these messages

@bogeylnj thank you. I'll test this and merge it later tonight. I'm hoping to have a release with your SRI workaround out by Monday.

FYI: There are still some nested SRI calls (or something) that are failing
(for us), but the interfere with our authn flow.
Our code base also DEBUG logs these so Users don't see them but we could
troubleshoot, if necessary. If you would like those code stmts/config added
as well, let me know
On Fri, Feb 22, 2019 at 4:35 PM AlainODea<EMAIL_ADDRESS>wrote:

@bogeylnj https://github.com/bogeylnj thank you. I'll test this and
merge it later tonight. I'm hoping to have a release with your SRI
workaround out by Monday.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/oktadeveloper/okta-aws-cli-assume-role/pull/273#issuecomment-466572297,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Akp5dQ_5cRQdWQDRZDzkKw0irtcr6X9Uks5vQHCpgaJpZM4bLRk7
.


workaround MSVC codegen bug

In some cases MSVC generates bad code here. This change seems to fix the issue

Good point, I will make a note.