[Optimize] Use compact mode to send query plan thrift data structure.

Proposed changes
In some cases, the query plan thrift structure of a query may be very large
(for example, when there are many columns in SQL), resulting in a large number
of "send fragment timeout" errors.
This PR adds an FE config  use_compact_thrift_rpc to control whether to transmit
the query plan in a compressed format.
Using compressed format transmission can reduce the size by ~50%. But it may reduce
the concurrency by ~10%. Therefore, in the high concurrency small query scenario,
you can choose to turn off compaction.
Types of changes
What types of changes does your code introduce to Doris?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)
[ ] Code refactor (Modify the code structure, format the code, etc...)
[ ] Optimization. Including functional usability improvements and performance improvements.
[ ] Dependency. Such as changes related to third-party components.
[ ] Other.

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[ ] I have created an issue on (Fix #ISSUE) and described the bug/feature there in detail
[ ] Compiling and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If these changes need document changes, I have updated the document
[ ] Any dependent changes have been merged

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

should we turn off or turn on use_compact_thrift_rpc  by adaptive mode， so we can get both query concurrent performance and avoid send fragment timeout

should we turn off or turn on use_compact_thrift_rpc by adaptive mode， so we can get both query concurrent performance and avoid send fragment timeout

That may be a good choice. But I have no idea how to make it adaptive to the runtime situation...

according to the request size？

according to the request size？

The key point is how to determine the threshold of the size...

according to the request size？

The key point is how to determine the threshold of the size...

I think that it is better to use  threshold of the size than to use use_compact_thrift_rpc as a config.

according to the request size？

The key point is how to determine the threshold of the size...

I think that it is better to use threshold of the size than to use use_compact_thrift_rpc as a config.

You mean use size as config and using a big or small value as default?

according to the request size？

The key point is how to determine the threshold of the size...

I think that it is better to use threshold of the size than to use use_compact_thrift_rpc as a config.

You mean use size as config and using a big or small value as default?

yeah, because the request size is different with each other,  it is not flexible for users to just simply turn on or turn off the use_compact_thrift_rpc config


Stop exposing some props in IConnectionDetails, use new interface IConnectionDetailsInternal

Description
Adding new interface IConnectionDetailsInternal for props we can expose internally.
Removing existing completely from IConnectionDetails
removed InitialClients and version from IConnectionDetails, added in IConnectionDetailsInternal
In IDeltaManagerInternalEvents, we will use IConnectionDetailsInternal

@chensixx , it would be great to reference in this PR (and resulting commit) a PR/ commit for main changes that deprecates first these properties.

deprecate PR in main: https://github.com/microsoft/FluidFramework/pull/13705


⚠ ClamAV has degraded performance

In 4344550, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 67 ms

Resolved: ClamAV performance has improved in 2ed9bcf.


input._selected_rows() does not work (at least on Shinylive)

I had supposed this might have to do with the recent update, and that I was struggling to integrate it. This may still be the case, but examples of code, for example, here: https://shiny.posit.co/py/api/core/render.DataGrid.html. The example given therein works on the webpage fine. But when I try copying the code into a fresh shinylive.io application, it does not. Clicking the rows does not give the expected results.
I hope this was clear enough!
Many thanks

Hi @Assad-AC, we just released Shiny 0.9.0, and this should be fixed now.


Feature Request: Add back button support

It would be cool if I could use the back button on my mouse/keyboard (WM_BACK) to go back to the previous page.
That way I could experiment with controls more quickly form the home screen...

The XAML navigation control has this built in. The gallery app is built using the cross-platform react navigation module. @chiaramooney does that support hooking to a back navigation stack? And if so, how do apps enable those to be driven with keyboard?

There is some hooking for back navigation in RNW itself here. IS that relevant?


Network Speed at Taskbar

Description of the new feature / enhancement
showing internet or network speed at Taskbar
Scenario when this would be used?
it will be help us to monitor the internet speed that we used
Supporting information
No response

+1

Taskbar extensions wouldn't work on Windows 11 since the IDeskband2 interface was removed in Windows 11.

/dup https://github.com/microsoft/PowerToys/issues/828


Good Start

This is a good start to the first local repositories and I hope you have a chance to enter the Arctic Code Vault this year

Thanks for the encouragement! I really appreciate it


Improve OSPool AP installation doc

Mostly language changes but some reorganization as well. Also tell people to use OSG 23 if possible. (SOFTWARE-5777)

I would also like to move the 'upgrading from 3.5' section to the end of the document (or remove it entirely) but I will do that separately to keep the diffs small.

or remove it entirely

Yeah, let's do that


final / dots dead

The Persistent Purge of Pesky Punctuation!!
On Tue, Apr 12, 2016 at 8:38 PM Kate Rabinowitz<EMAIL_ADDRESS>wrote:

Merged #69 https://github.com/codefordc/school-modernization/pull/69.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/codefordc/school-modernization/pull/69#event-625017574


FIX: Re-add cohort identifier to template name

Fixes #415
We have been stripping out the cohort identifier in split_desc, and as a result losing the information when saving out transforms. This re-enables the output transforms to include the cohort information, i.e. ...from-MNIPediatricAsym+3_to-T1w_mode-image_xfm.h5.
However, this change exposes another problem: collect_derivatives cannot collect these transformations, as the current BIDSLayout configurations do not account for the + character during parsing. Since BIDS derivatives conventions are still a bit murky, I figured we want to just create a modified fmriprep-derivatives config to catch this convention when parsing.

Looks good in general. Perhaps relying on the + semantic is too risky. Since the proposal was done also including - as allowed (and I believe also underscore), it will not fly anytime soon. And would honestly not will to try to get only + accepted.
What do you think about from-MNIPediatricAsymCohort3 or, alternatively and potentially generating conflicts down the line, from-MNIPediatricAsym_to-T1w_desc-cohort3_xfm.h5?

TBH I don't love either option - at first I figured we could just add the cohort- entity directly, but that will clobber cases of inter-cohort xfms. IMO the + seems to be the cleanest / least ambiguous...

@effigies if you have a minute, would appreciate a review

TBH I don't love either option - at first I figured we could just add the cohort- entity directly, but that will clobber cases of inter-cohort xfms. IMO the + seems to be the cleanest / least ambiguous...

In that case, I believe space- could be used: space-MNIPediatricAsym_from-cohort1_to-cohort2_xfm.h5, but this honestly feels like a templateflow's issue, not a plausible output of sMRIPrep

Is this considered a bugfix or a feature?

I consider it more of a bug fix to get cohort processing / --derivatives working, as the changes will really only affect those cases. But this will invalidate the cache starting from the fit.registration workflow so maybe worth a minor bump?

Given that we're almost in Q2 of 2024 let's cut 24.0


[New game]: Endless Runner Game

🎮 Game Request
Game logic and basic description
An Endless Runner Game is a type of game where the player controls a character that runs continuously, and the objective is to avoid obstacles that come in the character's way. The game gets progressively harder as the player goes further, hence the name "endless."
Point down the features
Game points
Here are some features of an Endless Runner Game implemented in Python or JavaScript:
The player controls a character that runs automatically.
The player can make the character jump or slide to avoid obstacles.
The game generates new obstacles at regular intervals.
The obstacles can take various forms, such as gaps in the ground, moving objects, or enemies.
The player's score increases as they go further in the game.
The game gets progressively faster and more challenging as the player's score increases.
The game can have various themes, such as running through a city, a forest, or a fantasy world.
The game can have power-ups that give the player temporary abilities, such as invincibility or a speed boost.
Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @Damini2004 , You can't have another issue before completing the previous one 😀
you already have the following 1 open issues 👀 ! :
#3510

Hey @Damini2004 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇

Hey @Damini2004 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Hey @Damini2004!
We are already having a similar game request in #3331 👀
Make sure you come up with a cool unique idea 😀
Waiting for your new game idea 💗.


Change link to redirect on correct page

Change link to redirect on correct page
Category

[x] Content fix

Related issues:

fixes #5285

Change link to redirect on correct page

Thanks for your submission, but this is outdated and had issues. Please see how this was fixed in #5290. For internal links, must use relative links.
We can't include the locale in the URL (let the system determine that automatically based on the user request) & we don't use absolute links to content within the same repo.

Hi @andrewconnell Thank you for pointing out. Will add relative links from next time.


script hangs after printing the gravity db to update

I'm using a Pi 3 Model B with debian version 10.4, pihole5-list-tool version 0.4.5, python 3.7, not using docker.
when I start the script with 'sudo pihole5-list-tool' it gives the following output, and hangs for 10+ minutes. cpu and memory use are .1% and 2.2% respectively, which doesn't seem out of the ordinary to me.
┌──────────────────────────────────────────┐
│       π-hole 5 list tool  v0.4.5                                                              │ └──────────────────────────────────────────┘
https://github.com/jessedp/pihole5-list-tool
Do not hit ENTER or Y if a step seems to hang!
Use CTRL+C if you're sure it's hung and report it.

docker pihole image not found running, continuing...
? Gravity Db to Update:  /etc/pihole/gravity.db

I am only asking this because nothing different from that happens next... did you hit enter there?

that "fixed" it... I took the warning too literally, and it wasn't clear from the demonstration video that input was needed at that step


Password Generator - jpaddeo

🔒 Password Generator
This is my version of the hackathon proposed by @midudev . It's is quite simple as UI/UX but 100% functionally.
📷  Screenshot

💻 Technologies

Astro
React
TailwindCss

📁 Files
Pages
src/pages/entry/jpaddeo/index.astro

Components
src/components/jpaddeo/hooks/usePasswordGenerator.jsx
src/components/jpaddeo/icons/CheckCircle.jsx
src/components/jpaddeo/icons/Clipboard.jsx
src/components/jpaddeo/icons/Lock.jsx
src/components/jpaddeo/icons/Refresh.jsx
src/components/jpaddeo/partials/Actions.jsx
src/components/jpaddeo/partials/CharOptions.jsx
src/components/jpaddeo/partials/PasswordCard.jsx
src/components/jpaddeo/partials/Slider.jsx
src/components/jpaddeo/Generator.jsx
src/components/jpaddeo/GeneratorOptions.jsx

🚀🚀🚀⭐


Reordered MM4M365 TOC

Category

[x] Content fix
[ ] New article

Alpha sort in the TOC

Docs Build status updates of commit 5a77b3e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Community/TOC.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 9fc3dc7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Community/index_mm4m365.yml
:white_check_mark:Succeeded
View

Community/TOC.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 6b601f7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Community/index_mm4m365.yml
:white_check_mark:Succeeded
View

Community/microsoft365-maturity-model--run-workshop.md
:white_check_mark:Succeeded
View

Community/TOC.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Some facebook user dont have email address

Some facebook user dont have email address so added facebook identifier email address instead

@sushrest I don' think we can trust users without email being verified. Also, this PR has conflicts.

@SocalNick Some users are registered with only mobile numbers in facebook in that case the emailVerified and email field is blank. I personally prefer to allow those users to my app as well. Or is there any ways I can override this function with my own namespace? would appreciate your help.


Branch-related bugfixes

Fixes both ruby-git#599 and ruby-git#600
Also fixes argument name of update_ref.  I'm assuming it's supposed to be analogous to the command line git update-ref, which doesn't directly use a branch name.
Signed-off-by: Matt Blythe<EMAIL_ADDRESS>Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.

[x] Ensure all commits include DCO sign-off.
[x] Ensure that your contributions pass unit testing.
[N/A] Ensure that your contributions contain documentation if applicable.

Description
Fixes for #599 and #600

The fix for #599 seems good but I'd like to see the following test added to test/units/test_branch.rb. This is a slightly simplified version of the problem you mentioned in #599.
  def test_branch_update_ref
    in_temp_dir do |path|
      git = Git.init
      File.write('foo','rev 1')
      git.add('foo')
      git.commit('rev 1')
      git.branch('testing').create
      File.write('foo','rev 2')
      git.add('foo')
      git.commit('rev 2')
      git.branch('testing').update_ref(git.revparse('HEAD'))

      # Expect the call to Branch#update_ref to pass the full ref name for the
      # of the testing branch to Lib#update_ref
      assert_equal(git.revparse('HEAD'), git.revparse('refs/heads/testing'))
    end
  end

I think that the fix for #600 in Git::Branch#parse_name is something that I'd like to discuss further.
First off, #600 fails to note the externally visible issue caused by the insufficient implementation of this private method. Having a failing test would be very helpful in discussing this problem.
parse_name is only used by Git::Branch#initialize.
Git::Branch.new is only called from:

Git::Branches#initialize: the branch name is taken from git branch -a. e.g. master for a local branch or remotes/{remote-name}/{branch-name} for a remote branch
Git::Remote#branch: the branch name is given as {remote-name}/{branch-name}
Git::Base#branch: the branch name is only a name i.e. a local branch

The problem you ran into is easily duplicated for other cases that your fix does not solve.  For example, what happens when you create a (perfectly valid) local branch named refs/remotes/origin/master?
I am thinking that Git::Branch#initialize should probably be changed to have this signature: def initialize(base, remote_name, branch_name) to avoid this ambiguity. We would have to figure out how this impacts Git::Base#branch which is the only of these methods that should be used externally. Maybe document that it should only be used to create local branches (vs. remote) and have it add the "refs/heads/" prefix to the branch name before calling Git::Branch.new.

@mblythe86 I have added your change plus the test I suggested in #626.


Travis CI fails to compile OpenBLAS

Possible answers:

use sudo in Travis CI
use another CI service (e.g. Circle CI, wercher) to use docker

resolved by #2


Add Mute Command

Add the ability to ZeroTsu to give and remove a mute role to users and log it as a punishment

Added.


Updated wording

Updated variable names to be more explicit of who is friends with who and to correct mistakenly called variables.

thanks!


Refactor makeRequestsPropertyAssignment to use loop over HTTP methods

Refactor: Simplify makeRequestsPropertyAssignment Function
This PR refactors the makeRequestsPropertyAssignment function to use a loop over HTTP methods, reducing repetitive if statements and improving code maintainability. The functionality remains unchanged, ensuring backward compatibility. Unit tests have been checked to confirm they pass with the refactor.

Hi @moetazbrayek1, thanks for the PR. it seems the build fails with typescript types errors. Please take a look:

okay let me double check the tests

Just to clarify, it is not the tests failing, it is the build/compilation of typescript failing because of type mismatches

Fixed the typing issue. Could you check now?

@rametta  you can check now


The custom filter values provided in loadData([filter]) does not reflect in the searchboxes in the grid

When doing this custom search action:
    // loadData with custom filter
    $("#grid").jsGrid("loadData", { Name: "John" }).done(function() {
       //
    });

The loaddata is executed correctly, but the search box for the Name column is not updated with the value "John".
How to get this working ?

Now it's not supported. We mentioning this functionality here https://github.com/tabalinas/jsgrid/issues/81


Readme clarity for --xhyve-experimental-nfs-share

--xhyve-experimental-nfs-share does not seem to take a path. It only supports --xhyve-experimental-nfs-share=true.

Ok... Using homebrew's installed version, I cannot get this to work:
docker-machine create --driver xhyve --xhyve-experimental-nfs-share /Network/NFS --xhyve-cpu-count "4" --xhyve-memory-size "16384" default

However, when I install the formula using github's master branch, it's working and =true doesn't work. I'm guessing brew is just out of date.


feat(packages/core): Allow static web page forms of Kui to set a CSP …

…page header
part of #7330

Description of what you did:

My PR is a:

[ ] 💥 Breaking change
[ ] 🐛 Bug fix
[x] 💅 Enhancement
[ ] 🚀 New feature

Please confirm that your PR fulfills these requirements

[x] Multiple commits are squashed into one commit.
[x] The commit message follows Conventional Commits, which allows us to autogenerate release notes; e.g. fix(plugins/plugin-k8s): fixed annoying bugs
[x] All npm dependencies are pinned.

/lgtm


Python language server from Pylance is crashing

Environment data

Language Server version: 2021.6.0
OS and version: Windows 10 x64 10.0.19043
Python version (& distribution if applicable, e.g. Anaconda): 3.6.12, Anaconda

Expected behaviour
Intellisense, code completion/highlighting and ctrl+click should work.
Actual behaviour
None of the smart features of Pylance are working correctly. I keep getting the following notification:
The Python Tools server crashed 5 times in the last 3 minutes. The server will not be restarted.

I have tried following the steps in https://github.com/microsoft/vscode-python/issues/12286 and https://github.com/microsoft/python-language-server/issues/909 but unable to fix this. Probably because I am using Pylance [ref].
Logs

[Info  - 1:36:54 PM] Pylance language server 2021.6.0 (pyright 209c8040) starting
[Info  - 1:36:54 PM] Server root directory: c:\Users\usr\.vscode\extensions\ms-python.vscode-pylance-2021.6.0\dist
[Info  - 1:36:54 PM] Background analysis(1) root directory: c:\Users\usr\.vscode\extensions\ms-python.vscode-pylance-2021.6.0\dist
[Info  - 1:36:54 PM] Background analysis(1) started
[Info  - 1:36:55 PM] No configuration file found.
[Info  - 1:36:55 PM] No pyproject.toml file found.
[Info  - 1:36:55 PM] Setting pythonPath for service "GANDLF": "C:\Projects\GENERIC\venv\python.exe"
[Warn  - 1:36:55 PM] stubPath c:\Projects\GENERIC\typings is not a valid directory.
[Info  - 1:36:55 PM] Assuming Python version 3.6
[Info  - 1:36:55 PM] Assuming Python platform Windows
Search paths for c:\Projects\GENERIC
  c:\Users\usr\.vscode\extensions\ms-python.vscode-pylance-2021.6.0\dist\typeshed-fallback\stdlib
  c:\Projects\GENERIC
  c:\Projects\GENERIC\typings
  c:\Users\usr\.vscode\extensions\ms-python.vscode-pylance-2021.6.0\dist\typeshed-fallback\stubs\...
  c:\Users\usr\.vscode\extensions\ms-python.vscode-pylance-2021.6.0\dist\bundled\stubs
  c:\projects\generic\venv\python36.zip
  c:\projects\generic\venv\dlls
  c:\projects\generic\venv\lib
  c:\projects\generic\venv
  c:\Users\usr\appdata\roaming\python\python36\site-packages
  c:\projects\generic\venv\lib\site-packages
  c:\projects\generic
[Info  - 1:36:55 PM] Searching for source files
Background analysis message: setConfigOptions
Background analysis message: ensurePartialStubPackages
Loading ONNX runtime...
Loaded ONNX runtime. Creating IntelliCode session...
Created IntelliCode session.

Code Snippet / Additional information

Not applicable

I'm confused; normally if we crash there would be an exception. Is this the entire set of logs?

That's a known bug that'll be fixed in today's release. #1397
After that is closed, we can retry and see if your original issue goes away.

We've just released 2021.6.1; can you retry and see if your issue is fixed?

I can confirm it is fixed. I was having the same issue.

We've just released 2021.6.1; can you retry and see if your issue is fixed?

YES, this fixed it! Thank you so much!!!

Still facing the same issue with version of 6.1.
[Info  - 10:53:33 AM] Pylance language server 2021.6.1 (pyright e3f7cccc) starting
[Info  - 10:53:33 AM] Server root directory: /~/.vscode-server/extensions/ms-python.vscode-pylance-2021.6.1/dist
Libzip Error: Not a zip archive
    at makeLibzipError (/~/.vscode-server/extensions/ms-python.vscode-pylance-2021.6.1/dist/pyright-internal/node_modules/@yarnpkg/fslib/lib/ZipFS.js:149:29)
    at new m (/~/.vscode-server/extensions/ms-python.vscode-pylance-2021.6.1/dist/pyright-internal/node_modules/@yarnpkg/fslib/lib/ZipFS.js:121:28)
    at b.getZipSync (/~/.vscode-server/extensions/ms-python.vscode-pylance-2021.6.1/dist/pyright-internal/node_modules/@yarnpkg/fslib/lib/ZipOpenFS.js:784:28)
    at b.makeCallSync (/~/.vscode-server/extensions/ms-python.vscode-pylance-2021.6.1/dist/pyright-internal/node_modules/@yarnpkg/fslib/lib/ZipOpenFS.js:665:21)
    at b.readdirSync (/~/.vscode-server/extensions/ms-python.vscode-pylance-2021.6.1/dist/pyright-internal/node_modules/@yarnpkg/fslib/lib/ZipOpenFS.js:582:21)
    at c.readdirSync (/~/.vscode-server/extensions/ms-python.vscode-pylance-2021.6.1/dist/pyright-internal/node_modules/@yarnpkg/fslib/lib/ProxiedFS.js:191:28)
    at C.readdirSync (/~/.vscode-server/extensions/ms-python.vscode-pylance-2021.6.1/dist/pyright-internal/node_modules/@yarnpkg/fslib/lib/ProxiedFS.js:191:28)
    at I.readdirEntriesSync (/~/.vscode-server/extensions/ms-python.vscode-pylance-2021.6.1/dist/pyright-internal/src/common/fileSystem.ts:293:23)
    at t.PyrightFileSystem.processPartialStubPackages (/~/.vscode-server/extensions/ms-python.vscode-pylance-2021.6.1/dist/pyright-internal/src/pyrightFileSystem.ts:182:46)
    at _0x305a7e.ensurePartialStubPackages (/~/.vscode-server/extensions/ms-python.vscode-pylance-2021.6.1/dist/pyright-internal/src/analyzer/importResolver.ts:589:25)


Type binding mismatch: javax.security.Subject instead of my x.y.z.Subject

I have a schema which declare a type:
type Subject {
  uri:String!
}

and a class
public class Subject {
   private String uri;

   // Getters and setters
}

At startup, instead of picking up my Subject class, I get the following error:
Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [graphql.kickstart.tools.SchemaParser]: Factory method 'schemaParser' threw exception; nested exception is graphql.kickstart.tools.resolver.FieldResolverError: No method or field found as defined in schema <unknown>:338 with any of the following signatures (with or without one of [interface graphql.schema.DataFetchingEnvironment] as the last argument), in priority order:
  javax.security.auth.Subject.uri()
  javax.security.auth.Subject.getUri()
  javax.security.auth.Subject.uri

I'm struggling, trying to find a way to indicate my class instead of that coming from javax.security. Apart asking where I can set that mapping, I think it would be better to have a configuration or something like that, which would allow me to indicate a package where the bindings can be found. I mean, it's absolutely great to rely on this automatic binding, but in these cases there should be an easy way to solve the ambiguity.

The binding is handled by graphql-java-tools by starting the scan of the root Query and Mutation types and following all defined queries and mutations to bind all types and inputs to the corresponding classes. The above snippet above doesn't show that crucial part.
This Subject type is used in one of your queries or mutations? And in the Java class implementing that query or mutation you are using your own Subject class? Because in that case it should map it correctly.


References not converted to latex when template extends report.tplx

If one uses bookbook.latex with a template that starts with
((*- extends 'report.tplx' -*))

then cross references are not properly converted to latex; they are simply formatted as hyperlinks with \href{}.  This seems to be caused by the following section of nbconvert/templates/latex/report.tplx:
((* block markdowncell scoped *))
((( cell.source | citation2latex | strip_files_prefix | convert_pandoc('markdown', 'latex', extra_args=["--chapters"]) )))
((* endblock markdowncell *))

As a hacky workaround, I've copied filter_links.py to my book directory and set
((( cell.source | citation2latex | strip_files_prefix | convert_pandoc('markdown', 'latex', extra_args=["--chapters",'--filter', './filter_links.py']) )))

in my template.

Aha, I hadn't noticed that report.tplx overrides the markdowncell definition. That probably means there's a bug in nbconvert as well.

This should work with the development version of nbconvert, or 5.2 when we release it.


Databricks SSH into driver node not working when using containers

Page describing how to enable SSH-access into Databricks (Apache Spark) driver node isn't accurate.
First problem is, when running Databricks on Microsoft hosted VNet SSH-option isn't available at all. Altough this is accurate functionality, this documentation doesn't reflect any of this.
Second problem, when doing VNet Injection (https://docs.microsoft.com/en-us/azure/databricks/administration-guide/cloud-configurations/azure/vnet-inject) SSH-option is available, a public key can be set into cluster. However, when running on containers SSH doesn't work. Reason is simple: container host (Databricks) needs to forward the port into the container running Apache Spark Driver. My research indicates this isn't enabled and no SSH-access can be made. When running on virtual machines, my experience is SSH works. Documentation doesn't reflect any of this either.

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

ID: 8b52652f-0207-5ee5-b916-faad7e5995d4
Version Independent ID: d5fe8fb3-36f3-2a1f-12a7-2e96810f6038
Content: SSH to the cluster driver node - Azure Databricks
Content Source: databricks/kb/clusters/azure-ssh-cluster-driver-node.md
Service: azure-databricks
GitHub Login: @xwang30
Microsoft Alias: saperla

@Cap-JaTu Thank you for sharing feedback. We are actively validating it. We will share updates soon.

@xwang30 / @leifbro ,
Requesting to validate customer feedback and update the document accordingly as appropriate. Thankyou

#please-close


Functional Test Gaps for CLI

Our CLI functional test coverage is currently inconsistent, with several commands lacking any tests, including env show, list, app switch, among others. Although we introduced helper functions (removed in this PR) within the test framework for these commands, they were never utilized to implement actual tests. This issue aims to perform a review of our CLI functional test coverage and identify commands that are missing tests.
Next steps:

[ ] Review the overall test coverage of our CLI commands.
[ ] Identify commands that lack sufficient test coverage.
[ ] Implement tests for commands lacking coverage.

AB#11714

Due to integration test coverage of the CLI most all of the code paths are covered, particularly in complex areas. Going forward we will take a leave it better than we found it approach and add functional tests if we modify functionality or move the CLI to its own repo.


Update Button styles

I don't think that @primer/primitives has either hoverText or hoverShadow defined in its primary button color schemes.
btn.danger and btn.outline do so, and they're currently the same. We can check that here.
// btn.outline.hoverText, btn.danger.hoverText
get('scale.white')
// prints → #ffffff

// btn.outline.hoverText, btn.danger.hoverText
(theme: any) => `0 1px 0 ${alpha(get('scale.black'), 0.1)(theme)}`
// prints → '0 1px 0 rgba(27,31,36,0.1)'

Perhaps we should update @primer/primitives then update it here? We could also remove it altogether as it's probably not rendering anything.
I'm guessing that, if they're supposed to be the same, they could go up one level (btn.hoverText, btn.hoverShadow) and be shared across all buttons.
PS: Just found another "missing" style in <ButtonDanger />. Apparently there's no btn.danger.disabledBorder defined.
border-color: ${get('colors.btn.danger.disabledBorder')};

Let me know your thoughts. Happy to make any adjustments needed, either way.

[x] No tests were affected
[ ] Added/updated documentation

No worries! Glad to help.


additional stuff in deal_with_errors

and checked run_with_gcm and area _length_filter

I am not sure if I understood it right in deal_with_errors ...

Thanks a lot! That's very useful!!!


Cost explorer

Description
This adds a tab called "Cost" which summarizes Cluster cost by pulling in data from cost-explorer and graphing it by instance type. Also, this includes a button to activate cost allocation tags, which is a necessary pre-requisite for cost explorer.
Changes

Included new Cost.tsx file
Added route /manager/graph_data?cluster_name=Cluster&Start=Start&End=End/
Added route /manager/activate_tags/
Added route /manager/check_tag_status/

How Has This Been Tested?

Tested locally using created clusters

https://user-images.githubusercontent.com/68314782/180088672-fad78396-854a-425f-92c8-7c8152289d64.mov
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Closing in favor of #162


Get-VirusReport to specific hash returns String instead of JSON

Hi
Doing a query against hash 44676ad570f565608ddd6759532c3ae7b1e1a97d returns a String instead a JSON
The issue can be reproduced with a call like:
(Get-VirusReport -ApiKey $VTApi -Hash 44676ad570f565608ddd6759532c3ae7b1e1a97d).gettype()

It should be fixed. Hoping they don't create more then one, if they do we will have to add more sophisticated approach.


Host Server (<IP_ADDRESS>) Down

it seems <IP_ADDRESS>/useragents/?format=json is down, is there plan to bring this backup?

It seems that the maintainer have moved on...
I could host the server if the initial database and code to keep it up to date were provided.

@lobstrio Should we consider this package deprecated or will there be any efforts to get the server up and running?
Would much appreciate a reply, it does seem like there are people willing to take over maintenance if required.


Update ITAdmin-readiness.md

Removed old video for call quality overview, as the deck just got refreshed.

Learn Build status updates of commit 9ad6e0b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Teams/ITAdmin-readiness.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Relative trigger paths

Are trigger paths relative to the yml file (when in a subdirectory) or relative to the repository root?

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

ID: f5673ec1-c7d1-e0ac-043a-8fc3d5b226a9
Version Independent ID: b4872831-51c0-6cf8-1c56-de20beb38a80
Content: Build pipeline triggers - Azure Pipelines
Content Source: docs/pipelines/build/triggers.md
Product: devops
Technology: devops-cicd
GitHub Login: @steved0x
Microsoft Alias: sdanie

@cadull  Thank you for the question.
Trigger paths are relative the repository root.
Assigning this to the author for review.

Thanks for calling this out. We are making an update to the doc to clarify this.


Upgrade meilisearch-php to version 0.21

It is required to have meilisearch-php 0.21 installed to work with Meilisearch 0.25.

I've started updated the versioning system to match that of MeiliSearch as they're going through a lot of breaking changes while the software continues to mature. To work with v0.24 you can now install the latest release:
"elvenstar/statamic-meilisearch": "^0.24"

This week I'm testing out compatibility with v0.25, which you can try out early by installing the v25 branch:
"elvenstar/statamic-meilisearch": "v25.x-dev"

I'm testing it out with my own project but you can also let me know if you run into any bugs too.

That's fantastic. Version 0.24 works fine. I will test the v25-dev branch. Thanks a lot.


deprecate cwd and rename it to pwd

Rename cwd -> pwd so that it is more consistent w/ bash and less confusing with wd

merged: https://github.com/lihaoyi/Ammonite/pull/456


Proxy crashes when clicking "Authorize Account"

I'm using windows 10 and the proxy detects the authorization request and as soon as I click Authorize account I get this error. I tried with 2 different clients but get the same error.
2022-07-14 15:36:20: SMTP (localhost:2465; <IP_ADDRESS>:62030->smtp.gmail.com:465)     --> b'AUTH XOAUTH2\r\n'
2022-07-14 15:36:20: SMTP (localhost:2465; <IP_ADDRESS>:62030->smtp.gmail.com:465)     <-- b'334 \r\n'
2022-07-14 15:36:20: Authorisation request received for<EMAIL_ADDRESS>(interactive mode)
Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
at System.Windows.Forms.Control.get_CacheTextInternal()
at System.Windows.Forms.Control.get_Text()
at System.Windows.Forms.Control.set_Text(String value)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Python.Runtime.PythonException.ThrowLastAsClrException()
at Python.Runtime.Dispatcher.TrueDispatch(Object[] args)
at Python.Runtime.Dispatcher.Dispatch(Object[] args)
at __System_Threading_ThreadStartDispatcher.Invoke()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

just a follow-up. I tried the telnet method using IMAP but got the exact same error.

This is not a bug in the proxy, but an issue with pywebview on Windows. The resolution is to install a different version of that module's dependency pythonnet (e.g., see here for a similar discussion). You can check your pywebview installation without using the proxy by using the starter code found in the pywebview usage guide.
If you are not able to resolve the pywebview issue easily, then the proxy's --local-server-auth option is another solution, as it does not use pywebview.


improve: support combining multiple grouping expressions

Which issue does this PR close?

Closes #5361 .
Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

I plan to review this PR tomorrow. Thank you @yukkit

This looks good to me -- thank you @yukkit
the only thing I think is needed is an error condition check (as in try to pass in 100 columns in a grouping set). If this is unreasonable (or will take too long) I think it should generate a runtime error to protect DataFusion

@alamb FWIW. DataFusion is a fundamental query engine designed for inheritance by other products. I believe that the responsibility for implementing any necessary restrictions should lie with those who integrate it, as they have a better understanding of the customers and application scenarios. Therefore, we can afford to set a relatively high security threshold, as long as the process remains stable. I noticed that in Doris, the maximum number of distinct sets in the grouping sets clause is 64, while in PostgreSQL, it is 4096, and in DuckDB, it is 65535. Additionally, the maximum number of group expressions in the grouping_set clause is 65535 in DuckDB. I would appreciate your feedback on this.

cc @ozankabak

This PR also seems to have accumulated a merge conflict -- @yukkit  could you please resolve it?

This PR also seems to have accumulated a merge conflict -- @yukkit could you please resolve it?

@alamb  Okay, I've resolved the conflict

This PR also seems to have accumulated a merge conflict -- @yukkit could you please resolve it?

@alamb  Okay, I've resolved the conflict

LGTM. I think this PR is ready to  merge.

This PR had somehow accumulated another conflict, so I took the liberty of merging / resolving it again and pushing to your branch
While there are additional improvements, such as described by @mingmwang  on https://github.com/apache/arrow-datafusion/pull/5559#discussion_r1142950230, I think this PR is better than what is on main and thus I plan to merge it when the CI has passed

This PR had somehow accumulated another conflict, so I took the liberty of merging / resolving it again and pushing to your branch
While there are additional improvements, such as described by @mingmwang on #5559 (comment), I think this PR is better than what is on main and thus I plan to merge it when the CI has passed

I am working on the following improvement now.

I plan to move the enumeration logic to the new Analyzer  and keep the constructor logic in the Aggregate simple
and make the constructors(try_new(), try_new_with_schema()) be consistent.
There are some other grouping expressions related open tickets and I will also address them in the following PR.
https://github.com/apache/arrow-datafusion/issues/5647
https://github.com/apache/arrow-datafusion/issues/5672

i agree with your proposal

I plan to move the enumeration logic to the new Analyzer and keep the constructor logic in the Aggregate simple and make the constructors(try_new(), try_new_with_schema()) be consistent.
There are some other grouping expressions related open tickets and I will also address them in the following PR.
#5647 #5672

i agree with your proposal


:bug:Fix play game dev view edit level button

Was missing course and course instance id query params.

Coverage decreased (-0.2%) to 56.604% when pulling a2682fc179700ef210057855f06aa2f39ebc764d on fix-edit-level into 1308c23aa7dec28ef3331f55341d2b9e62ea88ed on master.

Coverage decreased (-0.2%) to 56.604% when pulling d6d88e87682fffbbd8d61fd107297d90833b7c3f on fix-edit-level into 1308c23aa7dec28ef3331f55341d2b9e62ea88ed on master.


Adding package meta-data to distribution.yaml?

Greetings,
I'm supporting an effort to update ROS on arch. The distribution.yaml is quite helpful, but I noticed a few things when trying to parse it for our package builds:

inconsistent data: some packages only have a release url, some have source, sometimes when both are missing, the doc url still points to git (which implies there is a source url)
sub-packages don't have xml entries: we link to the ROS wiki as the upstream URL in PKGBUILDs; because sub-packages (like tf2_eigen) don't have entries in the release_package_xmls, I'm not able to know their wiki directly. Currently I'm using a script which sees if https://wiki.ros.org/pkg_name exists
empty data: I'm using ET to find the wiki if it does exist:

wiki = ET.fromstring(xmls[pkg]).findall('url[@type="website"]')

Sometimes this returns a hit, but it turns out the tag is empty. The ff package is an example, and there is a ros wiki page for it...
<?xml version="1.0" ?><package><name>ff</name><version>2.1.12</version><description>ff: pddl planner. see http://www.loria.fr/~hoffmanj/ff.html</description><maintainer<EMAIL_ADDRESS>Okada</maintainer><license>GPL</license><url type="website"/><author>J.Hoffmann</author><buildtool_depend>catkin</buildtool_depend><build_depend>mk</build_depend><build_depend>flex</build_depend><build_depend>bison</build_depend><build_depend>unzip</build_depend><build_depend>mk</build_depend><build_depend>rosbuild</build_depend><build_depend>rosbash</build_depend><build_depend>rospack</build_depend><build_depend>roslib</build_depend><build_depend>ca-certificates</build_depend><build_depend>openssl</build_depend><export/></package>

Maybe my use-case is kind of fringe, but in principle it would seem to advantageous to have this complete. Any guidance on filling in blanks, standardizing? Interest in tracking sub-packages (e.g. what the package parent is and the wiki page, if it exists)?

* inconsistent data: some packages only have a release url, some have source, sometimes when both are missing, the doc url still points to git (which implies there is a source url)

This is a feature; sometimes our contributors only want to do one part of the "release" process.  There are separate uses for the documentation, source, and release (binary), and some packages only want parts of it.  So I don't think that we really want to change the flexibility this gives the contributors.

* sub-packages don't have xml entries: we link to the ROS wiki as the upstream URL in PKGBUILDs; because sub-packages (like `tf2_eigen`) don't have entries in the `release_package_xmls`, I'm not able to know their wiki directly. Currently I'm using a script which sees if `https://wiki.ros.org/pkg_name` exists

Sorry, can you point more directly where you are fetching the release_package_xmls from?

* empty data: I'm using ET to find the wiki if it does exist:

Sometimes this returns a hit, but it turns out the tag is empty. The ff package is an example, and there is a ros wiki page for it...

Oh, I see.  This is a case of the contributor not adding in a <url> tag to their package.xml.  In principle, I agree that all packages should have this, but I also don't think we should really enforce it at the rosdistro level.  My suggestion for these packages is to submit a PR to their upstream repository adding the <url> tag.

Interest in tracking sub-packages (e.g. what the package parent is and the wiki page, if it exists)?

Tracking the sub-packages back to the parent is a nice thing.  I would think it would be possible, since our buildfarm/infrastructure code has to do this.  @nuclearsandwich might have some tips on how to achieve this.

Thanks for the reply.

This is a feature; sometimes our contributors only want to do one part of the "release" process.

I might now know what all these get used for, but it seems kind of arbitrary? Take bagger as an example. What benefit is there in not listing source, or more particularly listing that page for at least the doc url? I think the wiki might rely on some of this, so you get ghost pages as a result. This isn't helpful, in my opinion.

can you point more directly where you are fetching the release_package_xmls from?

Whoops! I actually go that from here: http://repositories.ros.org/rosdistro_cache/ (I pulled melodic), which looks to contain distribution.yaml, but indeed has what looks like extracted package.xml data.

I also don't think we should really enforce it at the rosdistro level.

Good point... I assumed this was maintained, but stupidly should have read contributing.md... now I see the community generates this. Since my script is trying various ways to get the url (is it in the wiki page in the xml data? is there a doc site? does the wiki exist?), I could compile the list of packages that are missing.

Tracking the sub-packages back to the parent is a nice thing.

I'd be happy to help with that as well. My solutions is certainly low-tech. Do you mean you already have a master index of wiki pages or similar? That's where I ran into trouble. Even with some time.sleep() delays, I ran into surge protection checking for package pages...
Thanks for the dialog!

Followup: I now have the list of wiki pages for sub-packages, assuming the pkg_name matched up directly with wiki.ros.org/pck_name. This was manually scraped and takes some time to not overload the wiki. If there is a better way to get this data, or you have existing code and would like help implementing a more granular listing, I'm game to help!
In addition, I can create a list of missing data for reference and suggest to upstream folks that they add this info to their listings.

In general there should be a wiki page for each package name. The wiki pages are not autogenerated but require the maintainer to create them so we don't end up spamming the wiki.
You'll find that our new site https://index.ros.org does automatically create content for anything indexed. eg search for ff
You're right that it's much more helpful for maintainers to submit doc and source entries. But there are cases when it's not appropriate. Doc is not useful if the repository cannot be crawled by our documentation engine. And sometimes the source is not hosted in a format that we support indexing. So we cannot require them. If there are packages which you'd like to see have more content listed please file a ticket with the upstream package to get the attention of the maintainer.

Tracking the sub-packages back to the parent is a nice thing.

I'd be happy to help with that as well. My solutions is certainly low-tech. Do you mean you already have a master index of wiki pages or similar? That's where I ran into trouble. Even with some time.sleep() delays, I ran into surge protection checking for package pages...

Assuming you're referrring to packages and repositories, (instead of subpackages and packages) index.ros.org already has the associations between those documented.
If a website url is not declared the wiki page is what we use as the default. It's ok to create a link to it even if it doesn't exist. If someone creates it and there is a documentation job when it's created the header will be populated.

You'll find that our new site https://index.ros.org does automatically create content for anything indexed. eg search for ff

I have seen that and assumed it was based on distribution.yaml, risdistro cache, or similar, or that both distribution.yam, and index.ros.org are based on the same thing.

wiki pages are still missing for some (like ff even thought it exists)
index.ros.org indeed tracks parent/child (or repo/packages), but so does distribution.yaml, but it doesn't seem to track child wiki pages, e.g. tf2_eigen.

This was initially just a neurotic inquiry as I'm helping update the ROS packages for arch linux. We list a url per package in our PKGBUILD (example), and while we were migrating to ROS sources (vs. ros-gbp), I figured I'd update them. That's when I found there appears to be no master list, and many packages listing links.
I think part of the problem is that from an outsider view, I can't tell the difference between accidentally missing (like ff having an empty website tag in the distro_cache) and any of the cases you mention above where some link doesn't make sense.
I don't know what other uses having such an index has, but given that I've now built it, it would seem there is no downside in adding that data where possible? Again, happy to help, and I would think it's in everyone's best interest to have these wiki pages listed in various places if they exist...
What if I use the github api to post an issue suggesting a review of the distribution.yaml entry for any packages who had errors? This wouldn't seem to correct the pacakges issue (e.g. tf2_eigen), would it? That would seem to require a new structure and intentionally adding those wiki pages somewhere to the index.

index.ros.org indeed tracks parent/child (or repo/packages), but so does distribution.yaml, but it doesn't seem to track child wiki pages, e.g. tf2_eigen.

I don't understand this there's a link at the right to the wiki page.

What if I use the github api to post an issue suggesting a review of the distribution.yaml entry for any packages who had errors?

Can you explain this a little more? Opening a mass of tickets is not going to be helpful. Opening PRs that fix things could be.

This wouldn't seem to correct the pacakges issue (e.g. tf2_eigen), would it? That would seem to require a new structure and intentionally adding those wiki pages somewhere to the index.

What do you consider wrong with tf2_eigen that needs fixing and could be ticketed? Actually to that matter, what do you want to fix with ff. I see the wiki page has been there since 2015: http://wiki.ros.org/action/info/ff?action=info but you said it's missing above.

I don't understand this there's a link at the right to the wiki page.

Hmm. Consider me losing my mind. I swear I looked upon the last reply and saw no website link. Now I do. What originally got me on ff specifically was the package xml in the distro cache (posted above):
<?xml version="1.0" ?><package><name>ff</name><version>2.1.12</version>
...
<url type="website"/>

Opening a mass of tickets is not going to be helpful. Opening PRs that fix things could be.

Agreed.

What do you consider wrong with tf2_eigen that needs fixing and could be ticketed?

I actually did not see the wiki link on any packages until you pointed it out, and I thought links to a website, wiki, sources, etc. would live in the main info section.

Taking a step back, let me restate how we got here:

I'm trying to help maintain ROS packages for arch linux
to do this, we're updating our build files
to do that, I need to know all the packages, their sources, and their repos
I found this repo, which I believed would contain that
in parsing the file and the rosdistro_cache, I found things I believed to be missing
I'm here asking how I can help

I feel friction in asking to do this, so perhaps we should just keep it simple:

what data source is ros index based on? (if that's the gold standard, I could use that for my aim)
same question for distribution.yaml and rosdistro_cache
are all those data sources in agreement with each other? (I believe at least the cache and index do not, based on the missing ff url tag)
if not, do you care?
if so, would you like any help aligning them?

With some slight generalizations this is how the indexing works.
Everything starts with the rosdistro. The distribution.yaml lists all the indexed repositories. To find all the packages you go to those repositories and browse for package.xml files. All data for any given package is pulled from the package.xml. It's expensive to do this walk, so to save most people the cost there's a caching mechanism the rosdistro cache where we store the results of the walk.
This information feeds the wiki, this information feeds the rosindex etc.
In general there's no duplication of the data except for several layers of caching which can cause temporary inconsistencies, but that's not what you're seeing. You mention that it doesn't seem that all the "sources" are in agreement. However they all are derived from the same source and appear to be in agreement, accurately reproducing the invalid url.
I definitely do care about the data being correct, but I'm mostly resisting your suggestions about adding or extending the data in the rosdistro which will make things more complicated and cause data redundancy that then could then become inconsistent. In general we rely on the maintainers to keep their package.xml up to date. Looking closer at ff itself, I now see that it's not a missing tag, but an empty tag in ff.  And that's an obvious bug with the package and should be ticketed as such on the upstream repository. Once that's updated there it will propagate to all the different places you're seeing like the rosdistro cache, and then the wiki and index.
I'm generally glossing over a lot of details about the exact mechanisms and different paths for different build types, and different paths for different versions. But the main point is that the primary source for all of this information is from the upstream repositories. If there's data that's missing or inaccurate tickets should be opened on the upstream repositories for the attention of the maintainers. If you'd like to suggest better ways to render or display things that are collected by the rosdistro indexing I can point you to the relevant repositories to make suggestions. (Such as the wiki or rosindex )
You mention that you don't know if the omissions are purposeful or intentional, and I don't either for any given package. It's a federated community and we delegate that judgement to the package maintainers.
You are right that the rosdistro is your source as the authority for finding the list of packages. I think you'll find that basically everything you need for generating every ROS package is available from the rosdistro library and the rosdep database(also in the rosdistro repo). We generate debian packages, ubuntu packages, fedora packages automatically with bloom and have support for Gentoo and OpenEmbedded using superflore. With those tools you should be able to extend the functionality to generate Arch packages fully automatically as well.
These are also the tools that use the wiki page by default unless the optional website url is set as the package "Homepage" in the debian parlance. in the future we will likely switch that over to use rosindex as the default. The packages that have explicitly declared the default website url will likely need to all be touched. And if you look around you can find ones that are still using our deprecated wiki urls like bond core and they're already out of date. This is why we like to use default values and not type it out every time in all the packages. But if the maintainer wants they can declare a non-standard website like frame_editor and we add that in parallel since as this example shows the wiki link is still more useful.

With those tools you should be able to extend the functionality to generate Arch packages fully automatically as well.

Work has also been done in the past to support adding an Archlinux generator to Bloom and work is ongoing to reduce the friction and maintenance burden of supporting additional generators with the hope that Superflore's separate generators are someday merged into Bloom so that Superflore uses Bloom under the hood.

@tfoote Thanks for the in-depth explanation! Forgive the delay. I had some vacation, house work, and also just ran out of time to work on this for a bit. I appreciate the understanding of package details as well as the mention of bloom and superflore, which are definitely of interest re. building arch binaries.
I asked that they add a website to ff (which will likely point to the ROS wiki from looking at their other package.xml files).
Re. bloom and superflore, I'll have to look into these more and they seem above my head at the moment. Bloom tells me how to add a package (which presumably builds for supported ROS distros), but I think what we need is that existing packages be build for arch, specifically.
superflore looks like the equivalent of an AUR package manager, namely "grab all the required source files for packages x, y, and z, then build and install them on my system." If so, I think that's basically what arch users already do. I think we're hung up on finding a build farm to do this (and then creating the infrastructure/config required for arch). I'm just helping out the lead of this effort who sounds to have more experience on that front.
Thanks again!


Update how users download the db file for scanning

do you want to include the screenshots that we've been sending through? or do you think it's unnecessary?
maybe just the last screenshot?

Yup, screenshots make it easy to scan the content and find what you need without wasting time. Can you include on @sarahpark ?

@joaofnfernandes just added screenshots in another commit


ebiten: a new version of Game.Update function to have arguments

Operating System

[ ] Windows
[ ] macOS
[ ] Linux
[ ] FreeBSD
[ ] OpenBSD
[ ] Android
[ ] iOS
[ ] Nintendo Switch
[ ] Xbox
[ ] Web Browsers

What feature would you like to be added?
Now Game's Update doesn't take anything. If Update takes something valuable, this might be nice. For example:

A screen size: Draw takes the screen size, but this information should be useful even in Update
A window manager (now there are global functions for this)
An input manager (now there are global functions for this)
A device scale factor (now there is a global function for this)

Of course we cannot change Update in v2 for backward compatibility, but we can have a new version of Update like Update2 or UpdateWithArguments? In v3, we can merge them.
Related issues:

#1704
#1852

Why is this needed?
This reduces global functions in the future and cleans up APIs.

Is there a reason to reduce global functions?

I don't think there is a point in giving Update some of the things it might be interested in, if we don't also give it all the things it might be interested in, as otherwise we would have to decide which things Update is more interested in over other things, and that would just make API less consistent with itself.
In case of giving it all the things, it could be done with an interface that has them all.
func (g *Game) Update(t TheThings) error {
	if t.Inputs().IsKeyPressed(...) { ... }
	ww, wh := t.Window().Size()
	// and so on
}

If TheThings is a bit of an overkill, there is an idea of checking all the things Update takes when calling it for the first time via reflection, so that Update(), Update(input ebiten.Input), Update(window ebiten.Window), Update(td ebiten.TimeDelta) and Update(td ebiten.TimeDelta, input ebiten.Input) etc. are all valid, but I can see why this is not so good of an idea. First of all, not very compile-time type safe and second I didn't even consider possible overhead of reflection, since I don't know how exactly it works in such case, and possibly ten other things I didn't think of.
Ideas akin to those discussed in #1704 make a lot more sense to me. There would be no need for Update to take in inputs if they were dedicated to HandleInputs. If HandleInputs happens right before each Update, isn't it almost like giving inputs to Update, handling them ASAP, and then forgetting about them? And if no inputs were made, HandleInputs could be skipped. If it is not implemented at all, there is no need to even track inputs.

If we want to lead users down the path of a "managed", "easy to use" model with Update() and Draw(), then we have to control the access to the "low-level functionality blocks" of input and window. That's because the managed model needs to set some restrictions (e.g. input consistency), and if input, window and others are exposed globally, the user can "break" the system, violate the restrictions.
That's Hajime's logic, I think... and if we accept the premise, the reasoning makes perfect sense: the cleanest way to enforce proper usage of window and input managers is to pass them directly to update[^1]. But I disagree with this model.
[^1]: We could also just control this internally and panic if Input() is used outside Update() though. Ugly, but works.
My main argument against this is that I would prefer input, window and game loop management to be truly universal, orthogonal, low-level functionality blocks. Right now they almost are, but not completely... and this model moves us away from unlocking a ton more of potential for Ebitengine.
Let's jump for a second into an alternate reality where we have global access to func DefaultInput() Input, func MainWindow() Window, and then explicit Input.Update() and Window.SwapBuffers() methods. Now we can manage input and game loops as we please. Many of the problems we have been discussing are not problems anymore:

Input state consistency is on the user (just call Input.Update() appropriately).
Update() can receive whatever the user needs, but since functions would be global, nothing new would be really needed.
Fitting other input models (e.g. async) can be done much more naturally.
Different game loop types for general purpose apps and high refresh rate games become possible without having to agonize over everything we discussed on 2338.

I think this is the right way to go instead of supressing globals (though I'm a big fan of organizing globals in a more structured way (DefaultInput() and MainWindow() and so on 👍)).
Instead of conditioning the design of input and window functionality to a concrete type of game loop (fixed timestep loop), we should just give users the power to do all this by themselves as they want, and only then suggest a recommended, simple, managed way to do things. Provide that as utility functionality instead.

Like #1852, I think this should be done in the last 2.x after v3.0.0-alpha is tagged. Or, the API would be unnecessarily complex.


update packages

:white_check_mark: Build TheIdServer 7.1.3-fix-dependencies1-0006 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/875d8cf121 by @)


Add edge support with updated doc and minified version

@luis-carvalho could you please review this and merge
In this commit I update docs, versions and js minified version

Hey @romanlex
Thank you for submitting.
We'll give a round up to your changes and we'll give back to you asap.

Please, merge it <3


Fixing memorystatus project to work with VS2017

@rachitb777,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


WorkloadEntry healthcheck condition miss

When healthcheck is enabled for wle, pilot-agent will probe the health status of the vm workload, and send healthcheck result to istiod only:

when the status changed(e.g. unhealthy->healthy or healthy->unhealthy).
And pilot-agent will send the health status when it recreate a ads stream(this can happen when reconnect).

In the istiod side, it will process the health info and update the workloadentry, however this can fail, if it fails the eds config could be wrong.
And it has no chance to recover unless reconnect, which is not acceptable.

One option is to simpley do backoff retry,
And the other one is to refactor the current health check workflow:
istio-agent should send healthcheck info--> wait for the healthcheck ack/nack, and resend the healthcheck when nacked.

Option one may introduce race problems when proxy reconnects, i would personally like the 2nd option.
The race problem is very hard to solve, we have done a lot of work to fix wle reg/unreg.
@stevenctl @howardjohn @ramaraochavali  WDYT?


git@github.com:layerhq/maven-private.git: ERROR: Repository not found

I'm getting the following error:
Cause: git@github.com:layerhq/maven-private.git: ERROR: Repository not found.
Below is my Module build.gradle file: (I want to pull my private repo into my module.)
apply plugin: 'com.android.library'
android {
compileSdkVersion 24
buildToolsVersion "23.0.1"
defaultConfig {
    minSdkVersion 19
    targetSdkVersion 23
    versionCode 1
    versionName "1.0"
    testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"

}
buildTypes {
    release {
        minifyEnabled false
        proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
    }
}

}
dependencies {
androidTestCompile 'com.android.support:support-annotations:24.1.1'
androidTestCompile 'com.android.support.test:runner:0.4'
androidTestCompile 'org.hamcrest:hamcrest-library:1.3'
compile 'org.jetbrains:annotations-java5:15.0'
}
apply plugin: 'git-repo'
buildscript {
repositories {
mavenCentral()
}
dependencies {
// get from layer
classpath group: 'com.layer', name: 'gradle-git-repo-plugin', version: '2.0.2'
}
}
repositories {
github("layerhq", "maven-private", "master", "releases")
git("some_git_url", "some.random.name", "master", "folder_dir/folder")
}

@kaylaavalos It looks like the content of your repositories block is wrong.
It should be:
repositories {
      github("my-github-username", "my-repo-project", "master", "releases")
}

Refer to the comment on this issue for an example.

@iRuth Thank you.
As for "releases" do I need to create a folder for "releases"?
What is ""arbitrary.unique.name" supposed to be? What is it used for?

@kaylaavalos in my project, I basically use:
repositories {
      github("my-github-username", "my-repo-project")
}

and it works fine.
I don't see "arbitrary.unique.name" anywhere. What are you referring to?

@iRuth When asking about "arbitrary.unique.name", I'm referring to the example in the README.md under "Depending on git repos"

@kaylaavalos oh okay. I haven't used that one, so I can't say. You can play around with it to find out what works and what doesn't.
Quoting from the README, you don't need to include both the git and github variants.

Add either alongside other repositories and you're good to go. The github variant is just a special case of git, they both do the same thing.


storage tiering fails in CI with a false red

[x] 4-2-stable
[x] master

I've now seen green - closing...


Issue with the snap interaction & how to automatically select/modify a feature on drawend?

In the following example, when drawing, the snap interaction works only for the first drawn polygon. Or if you first select and modify one of the two polygons and then start drawing a polygon, the snap interaction doesn't work.
-However the snap interactions works on the modify interaction.

I am having a hard time figuring out how to automatically select / modify a polygon when I finish drawing it on the drawend event.
Adding the following to the drawend function doesn't quite work and I don't think I am doing it the right way.

selectedFeatures.value = event.feature
modifyEnabled.value = true

https://codesandbox.io/s/vue3-openlayers-forked-qqrqx?file=/src/App.vue

i did not reproduce the issue

you should add this line to drawend function
selectedFeatures.value.push(event.feature)
and bind selectedFeatures to features props of select
example with 0.1.28:  https://codesandbox.io/s/vue3-openlayers-forked-lbvtf?file=/src/App.vue

i fixed this error with 0.1.29 :)


Loading any chart results in a duplicate execution

Doesn't matter if it is an example chart or a random one:
$ go run cmd/gobarchar/main.go
2024/06/25 22:22:14 listening on: 8080
2024/06/25 22:22:20 completed in: 150.333µs
2024/06/25 22:22:20 completed in: 74.625µs

I've not touched the project in a long time, so perhaps this is something I knew the reason for, but right now my memory escapes me.

Also the case for the deployed version:
2024-06-25T19:57:09.608 app[17816477f21648] ams [info] 2024/06/25 19:57:09 listening on: 8080
2024-06-25T19:58:06.407 app[17816477f21648] ams [info] 2024/06/25 19:58:06 completed in: 70.57µs
2024-06-25T19:58:06.536 app[17816477f21648] ams [info] 2024/06/25 19:58:06 completed in: 74.404µs

However, the issue is not the case when curl is used.

After adding a bit of code to dump the request:
diff --git a/chart.go b/chart.go
index da3caed..6ddf909 100644
--- a/chart.go
+++ b/chart.go
@@ -4,6 +4,7 @@ import (
        "fmt"
        "math/rand"
        "net/http"
+       "net/http/httputil"
        "sort"
        "strconv"
        "strings"
@@ -69,6 +70,9 @@ func (a chartData) Less(i, j int) bool { return a[i].Value < a[j].Value }

 func PresentBarChart(examples string) http.HandlerFunc {
        return func(w http.ResponseWriter, r *http.Request) {
+               reqDump, _ := httputil.DumpRequest(r, true)
+               fmt.Printf("REQUEST:\n%s", string(reqDump))
                // Check if there are any query parameters; if not, add random key-value pairs
                if len(r.URL.Query()) == 0 {
                        encodeRandomQuery(r)

The problem became obvious:
$ go run cmd/gobarchar/main.go
2024/06/26 14:09:15 listening on: 8080
REQUEST:
GET /?February=14.71&March=22.83&April=28.57&May=22.58&June=23.29&July=20.29&August=9.30&September=9.52 HTTP/1.1
Host: localhost:8080
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7
Accept-Encoding: gzip, deflate, br, zstd
Accept-Language: en-GB,en-US;q=0.9,en;q=0.8
Connection: keep-alive
Dnt: 1
If-None-Match: 357e2e5ea931c096a299ed3e617d32837c98368d
Referer: http://localhost:8080/?February=14.71&March=22.83&April=28.57&May=22.58&June=23.29&July=20.29&August=9.30&September=9.52
Sec-Ch-Ua: "Not/A)Brand";v="8", "Chromium";v="126"
Sec-Ch-Ua-Mobile: ?0
Sec-Ch-Ua-Platform: "macOS"
Sec-Fetch-Dest: document
Sec-Fetch-Mode: navigate
Sec-Fetch-Site: same-origin
Sec-Fetch-User: ?1
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36

2024/06/26 14:09:20 completed in: 180µs
REQUEST:
GET /favicon.ico HTTP/1.1
Host: localhost:8080
Accept: image/avif,image/webp,image/apng,image/svg+xml,image/*,*/*;q=0.8
Accept-Encoding: gzip, deflate, br, zstd
Accept-Language: en-GB,en-US;q=0.9,en;q=0.8
Connection: keep-alive
Dnt: 1
If-None-Match: de2fdae5bbaf89a5f22f91aa4d7dd19d23e8c073
Referer: http://localhost:8080/?February=14.71&March=22.83&April=28.57&May=22.58&June=23.29&July=20.29&August=9.30&September=9.52
Sec-Ch-Ua: "Not/A)Brand";v="8", "Chromium";v="126"
Sec-Ch-Ua-Mobile: ?0
Sec-Ch-Ua-Platform: "macOS"
Sec-Fetch-Dest: image
Sec-Fetch-Mode: no-cors
Sec-Fetch-Site: same-origin
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36

2024/06/26 14:09:20 completed in: 140µs

Definitely do not need the additional request for the favicon.

Released with version v1.5.1.


Added RHEL5 support which also entails supporting .PEM file extensions.

Changed file names so that they can either be .CRT or .PEM extensions based on the OS Release.  ie:  RHEL5 = PEM, all others = CRT.

I've pulled this back in as a rhel5 branch (distributed source control is nice). Unfortunately I don't have the time right now to manually merge this with a year's worth of changes though.
Other than all of the merge conflicts, do you know about what issues need to be fixed before this can be merged?

RHEL5 support has ended, so can this be dropped now?

I'll go ahead and close it since it's end of production support, but I'm not opposed to re-opening if someone has the time to work on it (extended support runs through 2020).


Filter sentry issues - part 1

Do Sentry logs triage to filter the issues that are still relevant in 0.4.1, identify the origin and create the corresponding issues in the repository, with priority to data pipeline errors.
Acceptance criteria:
1 - All app-related logs in the Sentry dashboard are marked as reviewed with the corresponding issue link or ignored.


lib: libc: newlib: fix compile warning for retargetable lock

These APIs are only valid when enable _RETARGETABLE_LOCKING in toolchain, When _RETARGETABLE_LOCKING is enabled, "_LOCK_T" is "__lock" pointer type, otherwise "_LOCK_T" is "int" type, so without this modification, there will be the following compile warnings when toolchain doesn't enable _RETARGETABLE_LOCKING:
zephyr/lib/libc/newlib/libc-hooks.c:416:13: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
416 |  k_sem_take((struct k_sem *)lock, K_FOREVER);
|             ^
zephyr/lib/libc/newlib/libc-hooks.c: In function '__retarget_lock_acquire_recursive':
zephyr/lib/libc/newlib/libc-hooks.c:423:15: warning: cast to pointer from
integer of different size [-Wint-to-pointer-cast]
423 |  k_mutex_lock((struct k_mutex *)lock, K_FOREVER);
|               ^
...
Signed-off-by: Jiafei Pan<EMAIL_ADDRESS>

What toolchain are you using that does not have a newlib built with retargetable locking enabled?

I am using the following toolchain:
https://developer.arm.com/-/media/Files/downloads/gnu-a/10.2-2020.11/binrel/gcc-arm-10.2-2020.11-x86_64-aarch64-none-elf.tar.xz?revision=79f65c42-1a1b-43f2-acb7-a795c8427085&rev=79f65c421a1b43f2acb7a795c8427085&hash=6020C2E8860C105980B250C80334F5A6F753C504

Should Zephyr support newlib without retargetable locks? Without that option, there is no locking at all, so any function operating on shared global state (stdio) will cause problems.

I am using the following toolchain:

Interesting ... GNU Arm Embedded (arm-none-eabi) builds with retargetable locking enabled, but GNU Toolchain for Cortex-A (aarch64-none-elf) does not.
I would say it is a bug that GNU Toolchain for Cortex-A does not build with retargetable locking because, in that case, you cannot ensure the thread safety of the newlib functions.
My suggestion would be to use the AArch64 toolchain from Zephyr SDK since this would ensure that the C library functions are thread safe.
As for this patch, -1 because we should not support newlib without retargetable locking for the aforementioned reason; if any, it should be a build assert saying retargetable locking must be always enabled.

Done, please review again, thanks.

Assuming you've tested to make sure this triggers in the right case, this looks like the right plan.

Yes, I have tested on ARM64 platform.


Updated Node install to use /usr/local/bin/nvm as install path

Ping: @chef-cookbooks/delivery-migration-team @schisamo

This PR has passed 'Verify' and is ready for review and approval!
Use: '@delivery approve' when code review is complete.

This PR has passed 'Verify' and is ready for review and approval!
Use: '@delivery approve' when code review is complete.

@delivery approve

Change: dc353d7b-29fc-43a1-8eff-34fc79ade0f2 approved by: @elliott-davis

This PR has passed 'Acceptance' and is ready to be delivered!
Use: '@delivery deliver' when validated in acceptance.


V2 - Project Console - Permissions issues with few endpoints

Test Data Used in endpoints

community-program-manager having access to project with project scope. User is not able to access below endpoints but should be able to
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/updateProjectGithubOrganizationConfig
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/getSignatureSignedDocument
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/downloadProjectSignatureICLA
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/downloadProjectSignatureCorporateCLA
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/downloadProjectSignatureEmployeeAsCSV

project-manager having access to project with project scope. User is not able to access below endpoints but should be able to
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/updateProjectGithubOrganizationConfig
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/downloadProjectSignatureICLA
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/downloadProjectSignatureCorporateCLA
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/downloadProjectSignatureEmployeeAsCSV

lf-program-manager having access to project with project scope. User is not able to access below endpoints but should be able to
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/updateProjectGithubOrganizationConfig
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/getSignatureSignedDocument
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/downloadProjectSignatureICLA
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/downloadProjectSignatureCorporateCLA
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/downloadProjectSignatureEmployeeAsCSV

cla-manager having access to project with project/Organization scope. User is able to access below endpoints. If it is  used in Corporate Console the user has to have access, if not user should not be able to access
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/getProjectSignatures
cla-manager having access with Organization scope. User is able to access below endpoints. If it is  used in Corporate Console the user has to have access, if not user should not be able to acces
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/getProjectSignatures
community-program-manager having access with community scope. User is able to access below endpoints but should not be able to access
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/updateClaGroup
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/deleteClaGroup
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/enrollProjects
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/unenrollProjects
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/getTemplates
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/validateClaGroup
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/getCLATemplatePreview
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/getProjectSignatures
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/addGerrit
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/deleteGerrit

community-program-manager having access with Organization scope. User is able to access below endpoints but should not be able to access
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/updateClaGroup
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/deleteClaGroup
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/enrollProjects
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/unenrollProjects
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/getTemplates
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/validateClaGroup
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/getCLATemplatePreview
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/getProjectSignatures
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/addGerrit
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/deleteGerrit

lf-program-manager having access with aggregate scope. User is able to access below endpoints but should not be able to access
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/updateClaGroup
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/deleteClaGroup
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/enrollProjects
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/unenrollProjects
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/getTemplates
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/validateClaGroup
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/getCLATemplatePreview
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/getProjectSignatures
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/addGerrit
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/deleteGerrit

lf-program-manager having access with organization scope. User is able to access below endpoints but should not be able to access
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/updateClaGroup
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/deleteClaGroup
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/enrollProjects
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/unenrollProjects
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/getTemplates
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/validateClaGroup
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/getCLATemplatePreview
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/getProjectSignatures
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/addGerrit
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/deleteGerrit
project-manager having access to project with project|organization scope. User is able to access below endpoints but should not be able to access
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/updateClaGroup
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/deleteClaGroup
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/enrollProjects
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/unenrollProjects
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/getTemplates
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/validateClaGroup
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/getCLATemplatePreview
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/getProjectSignatures
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/listClaGroupCorporateContributors
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/addGerrit
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/deleteGerrit

@manishv09 please check the latest permissions on the APIs listed above.

As discussed over 16-Dec standup, it was decided to unflag it from release as permissions have been tested so far well with the overall/e2e testing done. So, no need to test each and every api for now - can be done later.


support for etcd3

Does the latest version support etcd3? I always got "key not found".

No, it doesn't support etcdv3 at the moment. The support should be merged in the coming months. Feel free to follow #468 to be updated on the PR status.

thanks! i got a fork that supported it. waiting the update...

The 0.13.0 release of confd has support for etcdv3, as well as other fixes and improvements. You can download it here: https://github.com/kelseyhightower/confd/releases/tag/v0.13.0


IPV6_RECVPKTINFO is the correct option to receive IPV6_PKTINFO

Haven't tested, try this though.

it works great, I've left the defaults unchanged but updated setPktInfo() to use the socket options so users (and tests) can get / set these options easily
https://github.com/swhitty/FlyingFox/pull/133

very nice!


Warning on type errors

I think it needs warning instead of throwing errors by option.
https://github.com/codemix/babel-plugin-typecheck/blob/master/src/index.js#L94
just use console.warn

Yes this would definitely be possible. I would like to include this in v4

Hi, sorry for taking so long to respond to this, this project is now deprecated in favour of https://codemix.github.io/flow-runtime which aims for full compatibility with Flow.
Tracking this issue here - https://github.com/codemix/flow-runtime/issues/10