[USD] update to 22.08

What does your PR fix?
Fixes https://github.com/microsoft/vcpkg/issues/26920
No feature need to be tested.

USD version 22.11 has landed. It should be ready to update into vcpkg. Please let me know if there's any questions.

Closing this PR since it seems that no progress is being made. Please ping us to reopen if work is still being done.

The work at our end (Pixar) is finished. USD version 23.02 has been released since my last update.

What is the current state of this issue: https://github.com/PixarAnimationStudios/USD/issues/1600 ?

The migration is planned for Vfxplatform CY2024 (https://vfxplatform.com). Vfxplatform cy2024 will begin formalization in August, so I would look for motion on https://github.com/PixarAnimationStudios/USD/issues/1600 in support of that time frame.
I'm not a vcpkg maintainer, so I am unfamiliar with vcpkg's support for tbb vs Onetbb. It is possible to build tbb with a custom namespace for USD, and link it to a program that uses OneTBB, but I do not know if that is a viable path for vcpkg in the mean time.
I am fine with closing this request and perhaps revisiting it when the OneTbb migration is finished. My main motivation for pursuing this topic is to help move this issue forward: https://github.com/PixarAnimationStudios/USD/pull/2041 ~ it will be great to be able to promote vcpkg as a way for end users to obtain usd, when they are able to obtain the current release version.


cmd/audit: only flush formulary cache when needed

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

The cache here needs to be cleared when we are auditing multiple os/arch combinations but not when we are running the audit only for the current os/arch combination. This gives a 2x speed boost to brew audit --skip-style --except-version --tap=homebrew/core locally.
In theory we could clear the cache less often by running all audits for one os/arch combination at a time when auditing multiple os/arch combinations. This would make the output a bit harder to follow and we don't seem to run those checks on CI so I'm skipping that for now.
Note: This is on an old mac so we'll see how much faster it looks in CI.
 I'll see if there's any noticeable performance boost there.


Introduce Azure Traffic Manager 2018-04-01 API version with new features

This is a copy of https://github.com/Azure/azure-rest-api-specs/pull/3162/files with fixes to that PR (no auth to update original PR).
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] The spec follows the guidelines described in the Swagger checklist document.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-sdk-for-python

Automation for azure-sdk-for-node

Automation for azure-sdk-for-java

Automation for azure-sdk-for-go

Blocking on ARM review to be completed here https://github.com/Azure/azure-rest-api-specs/pull/3162/files

Talked to @allencal offline and looks like he is porting changes from https://github.com/Azure/azure-rest-api-specs/pull/3162 here along with some of his additional changes.
He will address @ravbhatnagar 's comments posted there and update this PR
@ravbhatnagar could you please finish the ARM review here

Assigning this to @sergey-shandar since he has more context here

Looks good!

@dsgouda are you ok with the changes? Please, approved the PR. Otherwise I can't merge.

LGTM

@allencal @dsgouda @sergey-shandar
This swagger spec is causing rendering issues in docs for User Metrics Keys and HeatMap.
https://review.docs.microsoft.com/en-us/rest/api/trafficmanager/trafficmanagerusermetricskeys?branch=trafficmanager
Specifically, the "Try It" feature renders for the REST operations (it shouldn't) but not for the examples themselves. There are also issues with the Definitions for UserMetricsModel in multiple places.
Can you take a look and fix? When you merge the fix you should be able to return to this docs link above and see if it is fixed.
thanks.


Changed package contents to nested lists and implemented caching

I didn't want to push directly to KnightOS since I added a column to the packages table. Not sure if anything has to be done to update the db.

Should work fine.


Fix return type for RKObjectMapping.inverseMapping

[RKEntityMapping inverseMapping] will return an RKObjectMapping so let's make that clear.

👍🏻


missing test for method

Description
A specific method is having issues in dockstore-support, was not previously tested (but is often used).
Added a test in the main repo to narrow things down, may as well make a PR out of it.
Review Instructions
n/a
tests pass
Issue
n/a
Security
None
Please make sure that you've checked the following before submitting your pull request. Thanks!

[x] Check that you pass the basic style checks and unit tests by running mvn clean install
[x] Ensure that the PR targets the correct branch. Check the milestone or fix version of the ticket.
[x] Follow the existing JPA patterns for queries, using named parameters, to avoid SQL injection
[x] If you are changing dependencies, check the Snyk status check or the dashboard to ensure you are not introducing new high/critical vulnerabilities
[x] Assume that inputs to the API can be malicious, and sanitize and/or check for Denial of Service type values, e.g., massive sizes
[x] Do not serve user-uploaded binary images through the Dockstore API
[x] Ensure that endpoints that only allow privileged access enforce that with the @RolesAllowed annotation
[x] Do not create cookies, although this may change in the future
[x] If this PR is for a user-facing feature, create and link a documentation ticket for this feature (usually in the same milestone as the linked issue). Style points if you create a documentation PR directly and link that instead.

Will need to revisit as part of larger investigation


Update drivers for multiple time sources

Port this over: https://github.com/ouster-lidar/ouster_example/pull/97

Hey @SteveMacenski if this work has not yet started, I'm happy to do it (you can "assign" me) as it is relevant to what I am currently working on. I also have an OS1-16 to test with in my quarantined WFH setup. LMK.

That would be great! Thanks.
Are you also generally interested in being a maintainer on this?
You clearly understand what's going on here and a prime user. I'd be more than happy to have you - just add your name to the package.xml in the next PR and I'll work on getting you admin.

Sure. Thanks Steve. Happy to join on as a maintainer/admin.
I'll get a PR together for this issue in the coming days. I'm currently deep on a few other things that I do not want to context switch out of, but this is squarely on my radar (per my earlier comment).

Sounds good. This also resolves one of the bullets in #16 to allow for local, ROS, and synced time.


How to deal with mesos master leader changes when you use storm < 1.0.0

I came across a situation whereby if the mesos master leader is not the same as the node on which the storm nimbus is setup on, the storm ui/setup is borked.
Basically with storm < 1.0.0 cannot cope with multiple mesos masters and mesos master leader changes.
has anyone experienced this ?
cc @erikdw
Thanks

@salimane : can you tell me more about your setup & what exactly the storm ui being borked means?  We haven't had any problems like this, but we don't run the storm ui nor storm nimbus within the mesos cluster itself.  Only the supervisors & workers are run in our mesos cluster.

@erikdw sorry I was my mistake. there was a typo in the zookeepers url. closing this

@salimane: ahh, thanks for clearing that up, and no worries.


New example-c docs work to "Test the BMI" but breaks with pymt.models

@mcflugen & @mdpiper,
Thank you for merging this PR!

#97

I was able to successfully (on a Mac) follow the Example: Wrapping a C model down to the Test the BMI section, but after that I got numerous errors, all related to pymt.
To make it work, I had to create a conda environment that built babelizer from the head of your develop branch, using this: https://github.com/LimnoTech/babelizer-examples/blob/main/environment.yml.
Given that pymt hasn't been updated since 2021, it might make sense to just put a big warning above that section of the docs, saying that pymt functionality is not currently compatible with the babelizer toolchain. That seems like a quick way to help folks avoid headaches.
@Volk3rJ & @ptomasula, can you try this workflow on Windows, down to Test the BMI](https://babelizer.readthedocs.io/en/latest/example-c.html#test-the-bmi)? Please do it from my modified environment.yml in https://github.com/LimnoTech/babelizer-examples

We just need to update pymt; it's 1) not built for Python 3.12, and 2) incompatible with recent changes to gimli.units.

Moving conversation to:

https://github.com/csdms/pymt/issues/167#issuecomment-2061707187

and closing here, as the example-c works well (on Mac) up to that point.


GWAS plugin test (continued)

This draft PR is a continuation of #43, now that the identified prerequisites have been integrated into the main branch.
I have cherry-picked the commits that seemed most relevant, and replaced the former placeholder track by a manually-added one (using addTrack: false).

Thanks for this! Added 7f1fd55 for the sake of posterity, should we ever need to revisit the log from this PR. It irons out some bugs from test data.
I took a somewhat lazy approach to get the gwas_testing_ground dummy data to display. Since the dummy has a .txt extension and as such will not be parsed by the makefile, I renamed the extension to .bed via fileName in config.yml. I was amused to see that it worked 😏 It's a fun hack for testing purposes, but is probably a practice that we should avoid for real data.
I have also figured out the cause for the behavior reported in the note in #43. It was the the sparsity of the data (100kbp windows) that made it look like it was not loaded properly when defaultSession was configured to higher zoom levels. Increasing bpPerPx solved this.
Looks good to me!

I will then delete the old gwas-test-data branch. Is this PR intended to be included in the first release ? If you intend to keep it as an experiment I think we can close the PR (but keep the branch if you want to use it as a starting point for further tests)

I renamed the extension to .bed via fileName

Nice! The Makefile takes all the downloaded files as a starting point for further processing, and fileName tells how local copy should be named. So it works as expected (although fileName was first intended to be used with opaque URLs)

Sounds good! I am happy about the findings of this experiment for now and I think we can merge this and include it in the first release.


Help

Subject of the issue
Describe your issue here.
sent money from one wallet to another ,but they didn't get to
fe0822372e04daf31aff0b98d9a86dc85b2c8b07126649fe29041c3227880c8e
u19ywpcvzae2zkwzkg36rxeh648t8sd5cvn3r5372den8kej0rpgssr9gzx3feqamg92fzjv98s05q9n7erspajasecy447w6s9v30h0w2
should have come here
u1edf7vxxfaxzdsu8qt5rdcmc7hqx88kw34jh9qdzmrpfugnsvrs446j4s8wzgejfz9gsuf0zwnsxpruc8ymjphf889ze3xnc9j97tlsq9v3fyl4k5apvfvu97hy3a2llxfl47uupjwy052s4auelw0dsrzacdcsvnmrael07zkwgv2e2ks4mvkxs3rqe6ehrae7qus5vt8wlmvmcw63f

Your environment

version of YWallet
platform and version. Ex: Android 11, Windows 10, etc.
if you were upgrading, the previous version you had

Steps to reproduce
Tell us how to reproduce this issue. Please provide a minimal reproducible scenario.
If possible, do a screen recording
Expected behaviour
Tell us what should happen
Actual behaviour
Tell us what happens instead

This is not ywallet. You are using zecwallet.


My key is slightly off

I am using the recommended formula for generating a key:
package main

import (
    "crypto/hmac"
    "crypto/sha256"
    "encoding/base64"
    "fmt"
)

func main() {
    mac := hmac.New(sha256.New, []byte("secret key"))
        mac.Write([]byte("https://octodex.github.com/images/codercat.jpg"))
        want := mac.Sum(nil)
        fmt.Println("result: ",base64.URLEncoding.EncodeToString(want)) // expect "sXyMwWKIC5JPCtlYOQ2f4yMBTqpjtUsfI67Sp7huXIYY="
}

This results in "XyMwWKIC5JPCtlYOQ2f4yMBTqpjtUsfI67Sp7huXIYY=" vs the key provided in your example "http://localhost:8080/500,sXyMwWKIC5JPCtlYOQ2f4yMBTqpjtUsfI67Sp7huXIYY=/https://octodex.github.com/images/codercat.jpg".  Notice the missing "s" at the front of my key.
My key doesn't work but yours does. Why am I missing an "s"?

The leading "s" isn't actually part of the signature itself, it's the name of the option, indicating that the remaining string is the actual signature value.  See more at https://godoc.org/willnorris.com/go/imageproxy#hdr-Signature

that's just weird. even having the key there is weird. should be a query arg.

Not using query strings was an intentional design decision for imageproxy, since it can having caching implications with various proxies.


Document all the gotchas I found

 "homepage": ".",

If this isn't in the package.json file then the production build of the React server won't load any of the compiled pages.
Document how the Dockerfile creates the react server.

Add react leaflet stuff:

How to add the geolocation and centering buttons
How to add the custom logout buttton

Stupid line endings issue for why the docker-entrypoint.sh file wouldn't run.


NEED WizardLM-2-8*22B Q6

NEED WizardLM-2-8*22B Q6

I cant download it
ollama pull wizardlm
pulling manifest
Error: pull model manifest: file does not exist


 System Windows_NT 10.0.17134
gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd D:\AI\SI\Agent\agentServer\node_modules\epoll
gyp ERR! node -v v10.15.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      C:\Users\KH2554\AppData\Roaming\npm-cache_logs\2020-05-28T09_33_02_183Z-debug.log

npm i onoff working on Windows:
c:\src\onoff>node -v
v10.15.3

c:\src\onoff>npm i onoff

><EMAIL_ADDRESS>install c:\src\onoff\node_modules\epoll
> node-gyp rebuild

c:\src\onoff\node_modules\epoll>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\node_modu
les\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "C:\Program Files\nodejs\
node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
  win_delay_load_hook.cc
  Generating code
  All 1 functions were compiled because no usable IPDB/IOBJ from previous compilation was found.
  Finished generating code
  epoll.vcxproj -> c:\src\onoff\node_modules\epoll\build\Release\\epoll.node
  epoll.vcxproj -> c:\src\onoff\node_modules\epoll\build\Release\epoll.pdb (Full PDB)
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.

+<EMAIL_ADDRESS>added 6 packages from 12 contributors and audited 6 packages in 4.525s
found 0 vulnerabilities

c:\src\onoff>

npm i<EMAIL_ADDRESS>working on Windows:
c:\src\onoff>npm i<EMAIL_ADDRESS>
><EMAIL_ADDRESS>install c:\src\onoff\node_modules\epoll
> node-gyp rebuild

c:\src\onoff\node_modules\epoll>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\node_modu
les\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "C:\Program Files\nodejs\
node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
  win_delay_load_hook.cc
  Generating code
  All 1 functions were compiled because no usable IPDB/IOBJ from previous compilation was found.
  Finished generating code
  epoll.vcxproj -> c:\src\onoff\node_modules\epoll\build\Release\\epoll.node
  epoll.vcxproj -> c:\src\onoff\node_modules\epoll\build\Release\epoll.pdb (Full PDB)
npm WARN saveError ENOENT: no such file or directory, open 'c:\src\onoff\package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open 'c:\src\onoff\package.json'
npm WARN onoff No description
npm WARN onoff No repository field.
npm WARN onoff No README data
npm WARN onoff No license field.

+<EMAIL_ADDRESS>added 4 packages from 9 contributors and audited 4 packages in 4.979s
found 0 vulnerabilities

c:\src\onoff>

It looks like something isn't setup correctly on your system.

Perhaps it's the version of Python being used. I'm using Python v2.7.16.

Do we need any python version installed? why?

I install python 2.7.18 (it sees node-gyp is not supported in python 3). But the install still failed with the following tracelog.
` npm i onoff

<EMAIL_ADDRESS>install D:\AI\SI\Agent\agentServer\node_modules\epoll
node-gyp rebuild

D:\AI\SI\Agent\agentServer\node_modules\epoll>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\....\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
Warning: unrecognized setting VCCLCompilerTool/MultiProcessorCompilation
Warning: unrecognized setting VCCLCompilerTool/MultiProcessorCompilation
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
MSBUILD : error MSB4132: The tools version "2.0" is unrecognized.  System Windows_NT 10.0.17134
gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd D:\AI\SI\Agent\agentServer\node_modules\epoll
gyp ERR! node -v v10.15.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      C:\Users\KH2554\AppData\Roaming\npm-cache_logs\2020-05-28T15_20_20_363Z-debug.log`

Do we need any python version installed?

Yes

why?

Because onoff depends on epoll and epoll is a native module that is implemented in C++. When native modules are installed they are built by node-gyp which in turn requires Python.
A Visual C++ compiler is also needed.
A potential alternative to avoid these issues is to add onoff to the optional dependencies in package.json. Then error messages will be displayed but the installation process will continue. onoff will not be of any usage on a Windows machine.

Thanks, It helped. :)


Allow to log errors in file

Allow to log errors in app_data\sites{tenant}\logs for this kind of problem.
It should be enabled by default, or at least with a configuration.

See #300 for logging support.


Update ATAppUpdater.m

Logic is added to force cache clearing every time a request is made to Apple.

Thanks! Will update repo/cocoapods later. 😊


web: docs and guides

[x] Set up documentation section of the website
[x] Set up docs layout template
[x] Set up outline
[ ] Write the docs

Jeff will do an outline and we can discuss/work together

removing myself and creating a separate ticket for me for the "using the interface" docs #58

Focus on essential sections for now and we will finish the rest later.


move remaining csharp loadgen code from examples repo to some internal repo (ask ellery where would be a good place to put it, maybe with his python one)

Moved to internal repo "demos".


git.openFile keyboard shortcut does not work from a GitLens Compare view

GitLens Version: 8.3.3
VSCode Version: 1.23.1
OS Version: 10.13.5

Steps to Reproduce:

"Compare File with Previous Revision"
Attempt to execute "git.openFile" with a keyboard shortcut - nothing happens.
Attempt to execute "git.openFile" via "Show All Commands" fuzzy search - nothing happens.
Attempt to execute "git.openFile" via the button in tab bar located to the left of "Open Working File" - success.

Other Notes / Things I have tried:

I tried changing keyboard shortcut.
Note that my keyboard shortcut does appear correctly in the tooltip for the button and in the fuzzy search - yet the button works and keyboard shortcut and fuzzy search does not.

Workflow I am seeking:
Frequently, I want to copy text from a previous revision. The only way I have discovered to do this is with "Open File". If there is a better way, I would be happy to know it. Regardless, it is strange that keyboard shortcuts/fuzzy find does not work, only the UI button.
Thank you for your work and the amazing extension!

git.openFile isn't a command from GitLens, it is provided by the vscode git extension itself and since it doesn't know about GitLens files (uris) it doesn't work. I'm assuming you are trying to open the working version of that file? If so use the gitlens.openWorkingFile command instead.
Hope that helps.

@eamodio thank you for your response.
Perhaps I am going about it the wrong way, but my aim is this:

to browse one-by-one back in file revision history using "Compare to Previous" keyboard shortcut - which sometimes seems to work and other times does not go back more than one revision.
Then, when I reach a certain revision, I want to be able to copy and paste the red highlighted code and paste it in current code.

Do you have any suggestion for how to do this most efficiently?
Thank you!

I should note that Compare with Previous seems to always work using the button, but the keyboard shortcut only can go back one revision - why is this?

@eamodio I think my issue is, in fact, primarily about keybindings, but it does not seem limited to chorded keymap. I have tried all keymaps, settling on user-defined, and several keyboard shortcuts do not work when going back in history.
For example:  Previous Change and Next Change navigation.

I have keyboard shortcuts assigned to these, but they do not work in file history views.
The buttons do work.
the Keyboard shortcuts do work in the regular diff viewer triggered from Source Control view.

Thanks for your help!

@mliq I just release GitLens 8.3.4 which should hopefully fix the keyboarding issues. Please re-open this issue if not. Thanks!

Hi @eamodio - still not fixed. I don't think I am able to re-open the issue though, thank you.

Can you provide more details as to what isn't working? Because I can't reproduce any issues with the shortcut keys with the latest release.

Here is an example:

Define keyboard shortcut for workbench.action.compareEditor.nextChange.
Execute "Compare File With Previous Revision" until multiple changes are present.
Attempt to execute workbench.action.compareEditor.nextChange via keyboard shortcut - nothing happens.
Attempt to execute workbench.action.compareEditor.nextChange via the UI button - it works.

UI Button in question:

Hrm, I cannot reproduce this. What version of vscode are you using? I've tried 1.24 and 1.25-insiders. I am on Windows though (and don't have access to a Mac currently).

I am on 1.24.1 and also had this on 1.23 and 1.24.0. Perhaps it is a Mac issue then...

@mliq Is this still an issue? If so, what are you using to setup the keybinding?
Here is mine -- and it works fine for me on Windows
    {
        "key": "alt+n",
        "command": "workbench.action.compareEditor.nextChange",
        "when": "editorTextFocus && isInDiffEditor"
    },

@eamodio Yes, still an issue. I copied your keybinding setup above and no improvement.

@mliq Can you try again with GitLens 9?

I'm going to close this as I can't reproduce it, nor do I have access to a Mac at this point. And also the commands in question are built-in vscode commands, so if there is some underlying issue it is likely to be with vscode itself. So I would recommend filing an issue against that repository. Sorry.


Blocked scraper: opinions.united_states.state.ky

Scraper works slowly on my machine, but have been timing out in production for months now.  I'm suspicious that the court may be blocking our production IP.
Need to call the court.
********!! CRAWLER DOWN !!***********
*****scrape_court method failed!*****
********!! ACTION NEEDED !!**********
Traceback (most recent call last):
File "/var/www/courtlistener/cl/scrapers/management/commands/cl_scrape_opinions.py", line 324, in handle
self.parse_and_scrape_site(mod, options['full_crawl'])
File "/var/www/courtlistener/cl/scrapers/management/commands/cl_scrape_opinions.py", line 289, in parse_and_scrape_site
site = mod.Site().parse()
File "/var/www/.virtualenvs/courtlistener/local/lib/python2.7/site-packages/juriscraper/AbstractSite.py", line 112, in parse
self.html = self._download()
File "/var/www/.virtualenvs/courtlistener/local/lib/python2.7/site-packages/juriscraper/opinions/united_states/state/ky.py", line 105, in _download
html = super(Site, self)._download(request_dict)
File "/var/www/.virtualenvs/courtlistener/local/lib/python2.7/site-packages/juriscraper/AbstractSite.py", line 300, in _download
self._request_url_post(self.url)
File "/var/www/.virtualenvs/courtlistener/local/lib/python2.7/site-packages/juriscraper/AbstractSite.py", line 345, in _request_url_post
**self.request['parameters']
File "/var/www/.virtualenvs/courtlistener/local/lib/python2.7/site-packages/requests/sessions.py", line 572, in post
return self.request('POST', url, data=data, json=json, **kwargs)
File "/var/www/.virtualenvs/courtlistener/local/lib/python2.7/site-packages/requests/sessions.py", line 524, in request
resp = self.send(prep, **send_kwargs)
File "/var/www/.virtualenvs/courtlistener/local/lib/python2.7/site-packages/requests/sessions.py", line 637, in send
r = adapter.send(request, **kwargs)
File "/var/www/.virtualenvs/courtlistener/local/lib/python2.7/site-packages/requests/adapters.py", line 504, in send
raise ConnectTimeout(e, request=request)
ConnectTimeout: HTTPConnectionPool(host='<IP_ADDRESS>', port=80): Max retries exceeded with url: /dtSearch/dtisapi6.dll (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7f288e317ad0>, 'Connection to <IP_ADDRESS> timed out. (connect timeout=60)'))

You asked for the url to test against via curl.  It's too complicated for me to comment here.  Its a big post request.  See this: https://github.com/freelawproject/juriscraper/blob/master/juriscraper/opinions/united_states/state/ky.py#L74-L100

UPDATE: This scraper is now failing in dev during _fetch_case_name().  The sub-request is triggering a 500 error here.
The sub-requests is a POST to http://<IP_ADDRESS>/dockets/SearchCaseDetail.asp.
The web interface for this search is http://<IP_ADDRESS>/dockets/SearchbyCaseNumber.htm
I have no idea if this is a production service (it doesn't look like it, but that doesn't necessarily mean anything).  I have no idea if it is linked to from anywhere else on the KY court site(s), and I have no idea how we actually found out about this widget (before my time).  But, it appears to be broken now.  I will contact the court to solicit assistance, but they've historically been unhelpful/non-responsive to past requests.

Thanks @arderyp. I appreciate you following up on this one. Looking at the comment here: https://github.com/freelawproject/juriscraper/blob/master/juriscraper/opinions/united_states/state/ky.py#L75-L79, it seems like it's fairly easy to get a handle on the new URL. Right now it's set to:
http://<IP_ADDRESS>/dtSearch/dtisapi6.dll
Tried that?

That url isn't the problem.  Our initial post to that url works just fine.  The problem is with the sub-query post we have to make to fetch case names, as explained in my comment above.

@mlissner that url you mentioned is not the problem. Our initial post to that url works just fine. The problem is with the sub-query post we have to make to fetch case names, as explained in my comment above.

@mlissner I should clarify.  The url you mentioned is not the (new) problem in dev.  However, the logs suggest that the url you mentioned may be blocking our prod instance, which is what this issue was originally about.

OK, I'm striking out over on #262, but I think for this one, the missing URL is here:
https://appellate.kycourts.net/SC/SCDockets/
That shows the form that you can use to look up the case name and other metadata for a given case.

hmmm, maybe they moved it.  I will look into that later.

@mlissner the latest commit fixes the scraper so it now runs in dev.  But the PROD log still indicates that we are likely being blocked:

********!! CRAWLER DOWN !!***********
*****scrape_court method failed!*****
********!! ACTION NEEDED !!**********
Traceback (most recent call last):
File "/var/www/courtlistener/cl/scrapers/management/commands/cl_scrape_opinions.py", line 324, in handle
self.parse_and_scrape_site(mod, options['full_crawl'])
File "/var/www/courtlistener/cl/scrapers/management/commands/cl_scrape_opinions.py", line 289, in parse_and_scrape_site
site = mod.Site().parse()
File "/var/www/.virtualenvs/courtlistener/local/lib/python2.7/site-packages/juriscraper/AbstractSite.py", line 112, in parse
self.html = self._download()
File "/var/www/.virtualenvs/courtlistener/local/lib/python2.7/site-packages/juriscraper/opinions/united_states/state/ky.py", line 105, in _download
html = super(Site, self)._download(request_dict)
File "/var/www/.virtualenvs/courtlistener/local/lib/python2.7/site-packages/juriscraper/AbstractSite.py", line 300, in _download
self._request_url_post(self.url)
File "/var/www/.virtualenvs/courtlistener/local/lib/python2.7/site-packages/juriscraper/AbstractSite.py", line 345, in _request_url_post
**self.request['parameters']
File "/var/www/.virtualenvs/courtlistener/local/lib/python2.7/site-packages/requests/sessions.py", line 572, in post
return self.request('POST', url, data=data, json=json, **kwargs)
File "/var/www/.virtualenvs/courtlistener/local/lib/python2.7/site-packages/requests/sessions.py", line 524, in request
resp = self.send(prep, **send_kwargs)
File "/var/www/.virtualenvs/courtlistener/local/lib/python2.7/site-packages/requests/sessions.py", line 637, in send
r = adapter.send(request, **kwargs)
File "/var/www/.virtualenvs/courtlistener/local/lib/python2.7/site-packages/requests/adapters.py", line 504, in send
raise ConnectTimeout(e, request=request)
ConnectTimeout: HTTPConnectionPool(host='<IP_ADDRESS>', port=80): Max retries exceeded with url: /dtSearch/dtisapi6.dll (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7f441c378d90>, 'Connection to <IP_ADDRESS> timed out. (connect timeout=60)'))

You can experiment with posting via cURL on the command line to see if maybe they are restricting by our User-Agent.  If it works from your machine with and without our UA, you will probably need to jump onto the PROD server and do some cURL test there.

OK, yes, you've been right all along, thank you. It works fine locally when I do these commands:
curl <IP_ADDRESS>
curl https://appellate.kycourts.net/SC/SCDockets/ --insecure

(Though it requires --insecure because their SSL is screwy.)
But when I do the same on the server, it just sits there stalled. I'll try to give them a call.

Left a voicemail for their information officer. She's reachable via the AO:<PHONE_NUMBER>.

@mlissner goooooooood luck!
The only time they have ever responded to any contact I've made (maybe 1 our of 8 attempts), they were rather combative about the issue.  Not only do they not want to help us, but they view us as a nuisance (hence the blocking).  Did you try on PROD both with/without our UA?  In other words, are you sure they are blocking the actual IP?

if she ever responds, it might be worth adding her name and phone number to to scraper file

I tried with the same UA on my laptop and on prod. I'll definitely add her name to a file if I can get through to her.

ooof, of course the UA isn't the issue if it works on my machine with that UA... lol, long morning, sorry.

Heard back from Jamie Neal. She's going to forward an email on my behalf. We'll see.

Appears unblocked after fixes


need to create the build dir

Hi,
Thanks for the tool. Not sure about other systems, but here (fedora) the build dir has to be created beforehand, or else,
$ make
gcc -g -c src/xmutil.c -o build/xmutil.o -Wall -Werror
Assembler messages:
Fatal error: can't create build/xmutil.o: No such file or directory
make: *** [build/xmutil.o] Error 1
Fix should be trivial..

Fixed in 7af456692061cb3246e9bbc47c59314b178721fe
Sorry about the delay. :P


More testing with extensions

Apparently the changes in the area of working with font extensions has had unintended consequences:

\setmainfont[UprightFont=arial.ttf]{arial.ttf} worked in TL15 but not in TL16

Something to look into in more detail…

I just tried this in 2018 and it worked...


emacs not display properly with -nw option

This was fixed awhile ago (by changing window size I think) but recently I started seeing again, maybe after #39 and/or #41.

This has been observed only on serval so far, for which #45 is a fix.


chore: remove nonterminal simp

Removes nonterminal simps on lines looking like simp [...]

[ ] depends on: https://github.com/leanprover/lean4/issues/2131

Lean 4 issue 2131 seems like it would make this easier, since I am currently trying to fix these by hand.

LGTM!  I am sorry to have caused so much pain, but I think that this is a strong improvement!
I agree with the comment that ideally the linter should be implemented in lean directly, but currently, this is what is available!
Thanks!

LGTM! I am sorry to have caused so much pain, but I think that this is a strong improvement!
I agree with the comment that ideally the linter should be implemented in lean directly, but currently, this is what is available!
Thanks!

Thanks!
bors merge


index.html file cache

Seems that create react app has cache busting for its asset files (js, css, etc) but when deploying an update, the browser is still caching the html file itself, which would use the old assets.

Github pages sets a cache-control header max age to 600, so this isn't actually a problem, users will see the updated html after 10m.


runners: openocd: don't throw when no config is provided

In some cases the config is already provided for us e.g. when setting OPENOCD_NRF5_SUBFAMILY. Also it looks like config was always supposed to be optional (there are checks for it in do_run()).

Thanks for the patch. Looks good, please fix the issues reported by zephyrbot.

please fix the issues reported by zephyrbot.

@rhssk ping?

@mbolivar sorry for the late response. Linter errors are fixed.

@mbolivar sorry for the late response. Linter errors are fixed.

Thank you for the update! I'm closing and reopening this to restart CI, since it timed out.


Allow slide number to be set as bold

Handle bold from TextBaseProps by setting b="1" in the XML. Move up align definition before the field as it was no longer working when combined with bold.
Add actual slide number in the XML so that LibreOffice displays the slide number too (actually solves #339).

Thanks @mathbruyen !


Use another toolset of msvc in cuda job

This PR uses -T version=14.25 to use another one toolset in github action.
Also, pass the toolset selection into other cmake command if it exists.
It avoid the error from the latest compiler from 16.10 with cuda 11. ref
Github action install the toolset 14.25 from this issue
Another workaround is to use standard 17 not 14.

rebase!


why not set the php function foreach continue the addColumn orderBy

the issue url
https://github.com/yajra/laravel-datatables/issues/154

When using Collection as data source, added column via addColumn method is possible to be search and arranged. This will vary on your use case. But generally, you should set false on added columns because it's not part of the query.

you are right ，but the Developer should solve any bug for use 。isn‘t it ?
addColumn for search("foreach ($this->request->searchableColumnIndex() as $index)") and order("foreach ($this->request->orderableColumns() as $orderable)")  $index should be litte the database sql select column.

Yes, and the right way to fix this on my opinion is by properly setting the correct options set by the api. For your case, the proper way to fix it is by setting the option searchable and orderable to false to tell the package not to search and sort by it. If you have a better idea on how we can magically fix it then I am willing to accept a pull request ^_^.

how to  request a pull request. like this ?

Let's continue the discussion on https://github.com/yajra/laravel-datatables/pull/158


Add get_sites and get_sysinfo helpers

I've added these two helpers to retrieve sites and sysinfo.
get_sites helpers have already been proposed as a PR but was a little to intrusive in every functions.
I've just reused existing code from @uJIu4 : https://github.com/calmh/unifi-api/pull/39#issuecomment-231037978
get_sysinfo is usefull to retrieve Unifi controller name/FQDN and Unifi controller version, etc.
Many usefull API functions from php class UniFi-API-browser could be backported to python

Thank you for the contribution.  I will review it in the coming days.

I've made the changes, will you be able to merge changes ?
How can I safely contribute to the project ?
Do I have to make a PR for each function I wish to add ?

@agauvrit-tis Yes, that is the best approach.  Just do a PR and I will then merge once reviewed.
Thank you for the contribution!


Time Lock Upgradability

Currently tests failing due to bytecode size. Waiting on Brian's Module PR so the CoreMock tests will pass

Pull Request Test Coverage Report for Build 2846

16 of 16 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 2834:
0.0%

Covered Lines:
606

Relevant Lines:
606

💛  - Coveralls


there is no example project in given link

https://github.com/NathanaelA/nativescript-sqlite-example this gives 404 error

The demo is now included in this repo in the demo folder...   Where are you seeing this link to the old -example repo.

I could have sworn I updated the readme...  It has been updated...

Here in this repo's readme file


Any plan for translation?

Do you have any plan to translate templates in near future? Would be great to have a possibility to add more languages to this project, I can collaborate with English, Spanish and Basque.

We will add multiple lang support in next version.

Actually the current theme system is OK for multiple languages

@mikaoras I am agree, sadly I know nothing about Chinese, any chance to bring us English templates?

I can add Russian


Make ignstrtok private to Util.cc

Otherwise we might get ODR issue with ign-msgs/src/Utility.cc.

Windows failures also unrelated here.


RFC: Change Sensor Attribute SENSOR_ATTR_BATCH_DURATION from Ticks to a standardized metric

Problem description
At the Sensors WG meeting on 240729, it was brought by @bperseghetti @jgoppert that users working with the sensor attribute SENSOR_ATTR_BATCH_DURATION need to provide the configuration setting in Sensor Ticks. This is problematic because this may change between sensors and therefore breaks the abstraction of keeping the API sensor-agnostic.
https://github.com/zephyrproject-rtos/zephyr/blob/93c9da66944c7c7f79d5c554ca9a640b422d39b3/include/zephyr/drivers/sensor.h#L344-L345
Proposed change (Detailed)
Change the unit of SENSOR_ATTR_BATCH_DURATION from ticks to a more standardized metric (e.g: micro-seconds, nano-seconds, Hertz). Users would provide this value and the sensors would map that internally depending on their settings and constraints intristic to the sensor itself.
Impact/Dependencies
Currently, the only driver implementing this attribute is the ICM42688. So the impact of this change, even though not null, is limited.
https://github.com/zephyrproject-rtos/zephyr/blob/93c9da66944c7c7f79d5c554ca9a640b422d39b3/drivers/sensor/tdk/icm42688/icm42688.c#L160-L169
Alternatives
Not making this change and keeping the attribute in ticks.
CC: @teburd @MaureenHelm @yperess

I agree with choosing a standard unit of measurement. I would like to say, given the continued usage of struct sensor_value, the unit should be val1 being whole milliseconds, val2 being nanoseconds (1/1000000 of a millisecond). But I don't have a strong inclination in the slightest about what this number actually is, so long as its consistent across devices and parts. Ticks is not consistent.

@teburd why not seconds instead of milliseconds? This feels more logical/natural to me

@teburd why not seconds instead of milliseconds? This feels more logical/natural to me

ADCs can be very fast, and I'd love to support voltage sensing as yet-another-sensor would be my argument for supporting very small time units.

@teburd why not seconds instead of milliseconds? This feels more logical/natural to me

ADCs can be very fast, and I'd love to support voltage sensing as yet-another-sensor would be my argument for supporting very small time units.

Oh yeah totally, but isn't that the point of the nanoseconds part already to provide this level of precision? I.e the actual duration is "val1.val2 seconds" which is what I meant by more natural (with the added benefit of allowing for much longer durations without rolling over but not sure 3-month long batches are a thing :))

Not sure if I misunderstood, @kartben are you suggesting:

val1 -> seconds, and
val2 -> nanoseconds?

If that's the case, wouldn't we be breaking the units described by struct sensor value?
https://github.com/zephyrproject-rtos/zephyr/blob/ebd31d3916abf87791ba69e6831ea187e6b20e8f/include/zephyr/drivers/sensor.h#L51-L56
That's what Tom was alluding to here:

the unit should be val1 being whole milliseconds, val2 being nanoseconds (1/1000000 of a millisecond).

Not sure if I misunderstood, @kartben are you suggesting:
* val1 -> seconds, and

* val2 -> nanoseconds?

If that's the case, wouldn't we be breaking the units described by struct sensor value?
https://github.com/zephyrproject-rtos/zephyr/blob/ebd31d3916abf87791ba69e6831ea187e6b20e8f/include/zephyr/drivers/sensor.h#L51-L56
That's what Tom was alluding to here:

the unit should be val1 being whole milliseconds, val2 being nanoseconds (1/1000000 of a millisecond).

Indeed that's where my mind was. Though in further reflection I'm thinking perhaps picoseconds would be more appropriate for the smaller unit.
TI/ADI/etc make multi-gigasample per second parts, would be a shame to inadvertently cause those parts to be out of range, though they are in all likelihood tied to a specialized part (FPGA or DSP) rather than a general purpose MCU.

@ubieda I knew I was missing something :) I get what you both mean now, and it makes sense. It actually never occurred to me that val1 and val2 had an overall consistent definition :) Sorry for the noise :)

2 things to throw in here. We will soon begin working on a sensor_clock.h API which should standardize time. Additionally, I don't think we need to worry about nanoseconds here. The whole point of batching is to read less frequently. You can't really batch in the order of nanoseconds.

Development on the sensor_clock.h will start soon via #63651


Ja review download top page

I translated it a little freely. Plz check 🙏
Changes:
/ja/download/ page
Notes:
Please feel free to let me know and I will modify the PR to merely change the wording!

Thanks for update!


Investigate performance of MySqlConnector

MySqlConnector is an ADO.NET provider for MySQL that is not based on the "official" MySQL provider. It has a few notable characteristics:

It includes proper async support
It targets .NET Standard 2.0
It is the ADO.NET provider layer for the Pomelo EF Core provider for MySQL.
@bgrainger has volunteered to focus on performance for it

Code and issue tracking lives at https://github.com/mysql-net/MySqlConnector.
NuGet package is at https://www.nuget.org/packages/MySqlConnector.

@bgrainger thanks for volunteering!
@sebastienros I am wondering how to best help @bgrainger get started. I think if we document the steps as we go, it can become a useful template for subsequent providers. This what I believe we will need:

Define performance baseline for MySQL, i.e. a identify a repeatable set of tests that anyone can use to estimate the maximum throughput on any given client and server configuration (this test can use any tech, i.e. it does not need to use .NET).
Provide any post-cloning instructions for setting up the tests
Provide tips and links to useful tools to use for profiling and diagnosing
Summarize learnings from improvements applied so that other providers can leverage them (it would be great if @roji and @damageboy could do this for the Npgsql improvements applied so far in https://github.com/aspnet/DataAccessPerformance/issues/3)

Based on these blog posts, it seems like the standard benchmarking software for MySQL is sysbench. However, it currently excludes Windows (“As of sysbench 1.0 support for native Windows builds was dropped.”), so it can't work for “any given client and server configuration”.

Thanks, that's useful information and we can get the baseline from a Linux machine it's not an issue. I will run it, then give you the numbers of the benchmark with the latest MySQL connector version.

Just found about this comment. Will run it right away.
@bgrainger can you ping me on skype (sebastienros) so we can make faster progress? Latency matters ;)

I was curious to know how close MySqlConnector was to maximum throughput, so I learnt the Registered I/O Networking Extensions for Winsock ("how hard could it be?") and wrote a (Windows-only) client that queries a MySQL Server as quickly as possible using native code and registered I/O.
Compile the code from: https://github.com/bgrainger/MySqlBench
Or download a precompiled binary: https://github.com/bgrainger/MySqlBench/releases


Network (2020-05-01): Error removing/updating load balancer rules

When using 2020-05-01 network API, when I want to remove a load balancer rule that the load balancer is attached to VMSS, the request will fail.
The complete flow is as below:

GET https://management.azure.com/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/loadBalancers/hbtest1?api-version=2020-05-01 HTTP/2.0

{
  "name": "hbtest1",
  "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/loadBalancers/hbtest1",
  "etag": "W/\"1867ac9a-5eca-431f-831c-939768a65794\"",
  "type": "Microsoft.Network/loadBalancers",
  "location": "eastus2",
  "tags": {},
  "properties": {
    "provisioningState": "Succeeded",
    "resourceGuid": "bf36d61a-728d-4255-8292-4397720a279d",
    "frontendIPConfigurations": [
      {
        "name": "hbtest1",
        "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/loadBalancers/hbtest1/frontendIPConfigurations/hbtest1",
        "etag": "W/\"1867ac9a-5eca-431f-831c-939768a65794\"",
        "type": "Microsoft.Network/loadBalancers/frontendIPConfigurations",
        "properties": {
          "provisioningState": "Succeeded",
          "privateIPAddress": "<IP_ADDRESS>",
          "privateIPAllocationMethod": "Dynamic",
          "subnet": {
            "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/virtualNetworks/acceptanceTestVirtualNetwork1/subnets/testsubnet"
          },
          "loadBalancingRules": [
            {
              "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/loadBalancers/hbtest1/loadBalancingRules/rule1"
            }
          ],
          "privateIPAddressVersion": "IPv4"
        }
      }
    ],
    "backendAddressPools": [
      {
        "name": "hbtest1",
        "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/loadBalancers/hbtest1/backendAddressPools/hbtest1",
        "etag": "W/\"1867ac9a-5eca-431f-831c-939768a65794\"",
        "properties": {
          "provisioningState": "Succeeded",
          "loadBalancerBackendAddresses": [
            {
              "name": "test-hbtest_hbtest1_virtualMachines_1_networkInterfaces_primaryprimary",
              "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/loadBalancers/hbtest1/backendAddressPools/hbtest1/loadBalancerBackendAddresses/test-hbtest_hbtest1_virtualMachines_1_networkInterfaces_primaryprimary",
              "etag": "W/\"1867ac9a-5eca-431f-831c-939768a65794\"",
              "properties": {
                "provisioningState": "Succeeded",
                "networkInterfaceIPConfiguration": {
                  "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Compute/virtualMachineScaleSets/hbtest1/virtualMachines/1/networkInterfaces/primary/ipConfigurations/primary"
                }
              },
              "type": "Microsoft.Network/loadBalancers/backendAddressPools/loadBalancerBackendAddresses"
            },
            {
              "name": "test-hbtest_hbtest1_virtualMachines_2_networkInterfaces_primaryprimary",
              "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/loadBalancers/hbtest1/backendAddressPools/hbtest1/loadBalancerBackendAddresses/test-hbtest_hbtest1_virtualMachines_2_networkInterfaces_primaryprimary",
              "etag": "W/\"1867ac9a-5eca-431f-831c-939768a65794\"",
              "properties": {
                "provisioningState": "Succeeded",
                "networkInterfaceIPConfiguration": {
                  "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Compute/virtualMachineScaleSets/hbtest1/virtualMachines/2/networkInterfaces/primary/ipConfigurations/primary"
                }
              },
              "type": "Microsoft.Network/loadBalancers/backendAddressPools/loadBalancerBackendAddresses"
            },
            {
              "name": "test-hbtest_hbtest1_virtualMachines_0_networkInterfaces_primaryprimary",
              "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/loadBalancers/hbtest1/backendAddressPools/hbtest1/loadBalancerBackendAddresses/test-hbtest_hbtest1_virtualMachines_0_networkInterfaces_primaryprimary",
              "etag": "W/\"1867ac9a-5eca-431f-831c-939768a65794\"",
              "properties": {
                "provisioningState": "Succeeded",
                "networkInterfaceIPConfiguration": {
                  "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Compute/virtualMachineScaleSets/hbtest1/virtualMachines/0/networkInterfaces/primary/ipConfigurations/primary"
                }
              },
              "type": "Microsoft.Network/loadBalancers/backendAddressPools/loadBalancerBackendAddresses"
            }
          ],
          "backendIPConfigurations": [
            {
              "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Compute/virtualMachineScaleSets/hbtest1/virtualMachines/1/networkInterfaces/primary/ipConfigurations/primary"
            },
            {
              "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Compute/virtualMachineScaleSets/hbtest1/virtualMachines/2/networkInterfaces/primary/ipConfigurations/primary"
            },
            {
              "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Compute/virtualMachineScaleSets/hbtest1/virtualMachines/0/networkInterfaces/primary/ipConfigurations/primary"
            }
          ],
          "loadBalancingRules": [
            {
              "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/loadBalancers/hbtest1/loadBalancingRules/rule1"
            }
          ]
        },
        "type": "Microsoft.Network/loadBalancers/backendAddressPools"
      }
    ],
    "loadBalancingRules": [
      {
        "name": "rule1",
        "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/loadBalancers/hbtest1/loadBalancingRules/rule1",
        "etag": "W/\"1867ac9a-5eca-431f-831c-939768a65794\"",
        "type": "Microsoft.Network/loadBalancers/loadBalancingRules",
        "properties": {
          "provisioningState": "Succeeded",
          "frontendIPConfiguration": {
            "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/loadBalancers/hbtest1/frontendIPConfigurations/hbtest1"
          },
          "frontendPort": 5000,
          "backendPort": 5000,
          "enableFloatingIP": false,
          "idleTimeoutInMinutes": 10,
          "protocol": "Tcp",
          "enableDestinationServiceEndpoint": false,
          "enableTcpReset": false,
          "allowBackendPortConflict": false,
          "loadDistribution": "Default",
          "disableOutboundSnat": true,
          "backendAddressPool": {
            "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/loadBalancers/hbtest1/backendAddressPools/hbtest1"
          },
          "probe": {
            "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/loadBalancers/hbtest1/probes/rule1"
          }
        }
      }
    ],
    "probes": [
      {
        "name": "rule1",
        "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/loadBalancers/hbtest1/probes/rule1",
        "etag": "W/\"1867ac9a-5eca-431f-831c-939768a65794\"",
        "properties": {
          "provisioningState": "Succeeded",
          "protocol": "Tcp",
          "port": 5000,
          "intervalInSeconds": 15,
          "numberOfProbes": 2,
          "loadBalancingRules": [
            {
              "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/loadBalancers/hbtest1/loadBalancingRules/rule1"
            }
          ]
        },
        "type": "Microsoft.Network/loadBalancers/probes"
      }
    ],
    "inboundNatRules": [],
    "outboundRules": [],
    "inboundNatPools": []
  },
  "sku": {
    "name": "Standard"
  }
}

PUT https://management.azure.com/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/loadBalancers/hbtest1?api-version=2020-05-01 HTTP/2.0

{
    "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/loadBalancers/hbtest1",
    "location": "eastus2",
    "properties": {
        "frontendIPConfigurations": [
            {
                "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/loadBalancers/hbtest1/frontendIPConfigurations/hbtest1",
                "name": "hbtest1",
                "properties": {
                    "loadBalancingRules": [
                        {
                            "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/loadBalancers/hbtest1/loadBalancingRules/rule1"
                        }
                    ],
                    "privateIPAddress": "<IP_ADDRESS>",
                    "privateIPAllocationMethod": "Dynamic",
                    "privateIPAddressVersion": "IPv4",
                    "subnet": {
                        "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/virtualNetworks/acceptanceTestVirtualNetwork1/subnets/testsubnet"
                    },
                    "provisioningState": "Succeeded"
                }
            }
        ],
        "backendAddressPools": [
            {
                "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/loadBalancers/hbtest1/backendAddressPools/hbtest1",
                "name": "hbtest1",
                "properties": {
                    "backendIPConfigurations": [
                        {
                            "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Compute/virtualMachineScaleSets/hbtest1/virtualMachines/1/networkInterfaces/primary/ipConfigurations/primary"
                        },
                        {
                            "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Compute/virtualMachineScaleSets/hbtest1/virtualMachines/2/networkInterfaces/primary/ipConfigurations/primary"
                        },
                        {
                            "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Compute/virtualMachineScaleSets/hbtest1/virtualMachines/0/networkInterfaces/primary/ipConfigurations/primary"
                        }
                    ],
                    "loadBalancerBackendAddresses": [
                        {
                            "name": "test-hbtest_hbtest1_virtualMachines_1_networkInterfaces_primaryprimary",
                            "properties": {
                                "networkInterfaceIPConfiguration": {
                                    "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Compute/virtualMachineScaleSets/hbtest1/virtualMachines/1/networkInterfaces/primary/ipConfigurations/primary"
                                }
                            }
                        },
                        {
                            "name": "test-hbtest_hbtest1_virtualMachines_2_networkInterfaces_primaryprimary",
                            "properties": {
                                "networkInterfaceIPConfiguration": {
                                    "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Compute/virtualMachineScaleSets/hbtest1/virtualMachines/2/networkInterfaces/primary/ipConfigurations/primary"
                                }
                            }
                        },
                        {
                            "name": "test-hbtest_hbtest1_virtualMachines_0_networkInterfaces_primaryprimary",
                            "properties": {
                                "networkInterfaceIPConfiguration": {
                                    "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Compute/virtualMachineScaleSets/hbtest1/virtualMachines/0/networkInterfaces/primary/ipConfigurations/primary"
                                }
                            }
                        }
                    ],
                    "loadBalancingRules": [
                        {
                            "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/loadBalancers/hbtest1/loadBalancingRules/rule1"
                        }
                    ],
                    "provisioningState": "Succeeded"
                }
            }
        ],
        "loadBalancingRules": [],
        "probes": [
            {
                "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/loadBalancers/hbtest1/probes/rule1",
                "name": "rule1",
                "properties": {
                    "loadBalancingRules": [
                        {
                            "id": "/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/loadBalancers/hbtest1/loadBalancingRules/rule1"
                        }
                    ],
                    "protocol": "Tcp",
                    "port": 5000,
                    "intervalInSeconds": 15,
                    "numberOfProbes": 2,
                    "provisioningState": "Succeeded"
                }
            }
        ],
        "inboundNatRules": [],
        "inboundNatPools": [],
        "outboundRules": [],
        "resourceGuid": "bf36d61a-728d-4255-8292-4397720a279d",
        "provisioningState": "Succeeded"
    },
    "sku": {
        "name": "Standard"
    },
    "tags": {}
}

Response:
{
    "error": {
        "code": "InvalidRequestFormat",
        "details": [
            {
                "code": "DuplicateIpConfigurationReferenceOnBackendAddressPool",
                "message": "Found duplicate ipConfiguration reference /subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/networkInterfaces/|providers|Microsoft.Compute|virtualMachineScaleSets|hbtest1|virtualMachines|1|networkInterfaces|primary/ipConfigurations/primary on backend pool addresses /subscriptions//resourceGroups//providers/Microsoft.Network/loadBalancers//backendAddressPools//loadBalancerBackendAddresses/ and /subscriptions//resourceGroups//providers/Microsoft.Network/loadBalancers//backendAddressPools/hbtest1/loadBalancerBackendAddresses/70f3bd40-2344-4c29-8177-768d4c3ca926."
            },
            {
                "code": "DuplicateIpConfigurationReferenceOnBackendAddressPool",
                "message": "Found duplicate ipConfiguration reference /subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/networkInterfaces/|providers|Microsoft.Compute|virtualMachineScaleSets|hbtest1|virtualMachines|2|networkInterfaces|primary/ipConfigurations/primary on backend pool addresses /subscriptions//resourceGroups//providers/Microsoft.Network/loadBalancers//backendAddressPools//loadBalancerBackendAddresses/ and /subscriptions//resourceGroups//providers/Microsoft.Network/loadBalancers//backendAddressPools/hbtest1/loadBalancerBackendAddresses/46147dc8-81bf-42be-8372-7815357a3f3f."
            },
            {
                "code": "DuplicateIpConfigurationReferenceOnBackendAddressPool",
                "message": "Found duplicate ipConfiguration reference /subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/networkInterfaces/|providers|Microsoft.Compute|virtualMachineScaleSets|hbtest1|virtualMachines|0|networkInterfaces|primary/ipConfigurations/primary on backend pool addresses /subscriptions//resourceGroups//providers/Microsoft.Network/loadBalancers//backendAddressPools//loadBalancerBackendAddresses/ and /subscriptions//resourceGroups//providers/Microsoft.Network/loadBalancers//backendAddressPools/hbtest1/loadBalancerBackendAddresses/a34f230b-359e-42a3-bb2e-921085c852b8."
            }
        ],
        "message": "Cannot parse the request."
    }
}

I am also facing the same issue, please fix

I just ran into this issue as well. I am pretty sure I didn't experience this until after implementing Scale Sets. But could be wrong.
Error: Error Creating/Updating Load Balancer "lbi.example.example-poc.development.services" (Resource Group "rg.example.example-poc.development.services"): network.LoadBalancersClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="InvalidRequestFormat" Message="Cannot parse the request." Details=[{"code":"DuplicateIpConfigurationReferenceOnBackendAddressPool","message":"Found duplicate ipConfiguration reference /subscriptions/134b3809-76mf-4891-bf25-edfaf8d5fc6f/resourceGroups/rg.example.example-poc.development.services/providers/Microsoft.Network/networkInterfaces/nic-wpapp01.example.example-poc.development.services/ipConfigurations/ip-wpapp01.example.example-poc.development.services on backend pool addresses /subscriptions//resourceGroups//providers/Microsoft.Network/loadBalancers//backendAddressPools//loadBalancerBackendAddresses/ and /subscriptions//resourceGroups//providers/Microsoft.Network/loadBalancers//backendAddressPools/lbi-wpapp.example.example-poc.development.services/loadBalancerBackendAddresses/0af31b77-ec08-4910-a328-66fe0662a851."},{"code":"DuplicateIpConfigurationReferenceOnBackendAddressPool","message":"Found duplicate ipConfiguration reference /subscriptions/134b3809-76mf-4891-bf25-edfaf8d5fc6f/resourceGroups/rg.example.example-poc.development.services/providers/Microsoft.Network/networkInterfaces/nic-wpapp02.example.example-poc.development.services/ipConfigurations/ip-wpapp02.example.example-poc.development.services on backend pool addresses /subscriptions//resourceGroups//providers/Microsoft.Network/loadBalancers//backendAddressPools//loadBalancerBackendAddresses/ and /subscriptions//resourceGroups//providers/Microsoft.Network/loadBalancers//backendAddressPools/lbi-wpapp.example.example-poc.development.services/loadBalancerBackendAddresses/e7c37c29-a3ac-403d-b234-a74009841b8a."}]

We have the same problem, please fix

This also affects any regular VMs in a Standard LB's backend pool
Error: Error Creating/Updating Load Balancer "LB-TEST01" (Resource Group "RGP-TESTAZURERMv2"):
network.LoadBalancersClient#CreateOrUpdate: Failure sending request: StatusCode=400 --
Original Error:
Code="InvalidRequestFormat"
Message="Cannot parse the request."
Details=[{
"code":"DuplicateIpConfigurationReferenceOnBackendAddressPool",
"message":"Found duplicate ipConfiguration reference /subscriptions/xxxxxx-xxxx-xxxx-xxxx-xxxxxx/resourceGroups/RGP-TESTAZURERMv2/providers/Microsoft.Network/networkInterfaces/vmtest01_nic-eth0/ipConfigurations/vmtest01-SubnetIPConfig on backend pool addresses /subscriptions//resourceGroups//providers/Microsoft.Network/loadBalancers//backendAddressPools//loadBalancerBackendAddresses/ and /subscriptions//resourceGroups//providers/Microsoft.Network/loadBalancers//backendAddressPools/LB-TEST01-backend_pool/loadBalancerBackendAddresses/xxxxxx-xxxx-xxxx-xxxx-xxxxxx."},
{"code":"DuplicateIpConfigurationReferenceOnBackendAddressPool",
"message":"Found duplicate ipConfiguration reference /subscriptions/xxxxxx-xxxx-xxxx-xxxx-xxxxxx/resourceGroups/RGP-TESTAZURERMv2/providers/Microsoft.Network/networkInterfaces/vmtest02_nic-eth0/ipConfigurations/vmtest02-SubnetIPConfig on backend pool addresses /subscriptions//resourceGroups//providers/Microsoft.Network/loadBalancers//backendAddressPools//loadBalancerBackendAddresses/ and /subscriptions//resourceGroups//providers/Microsoft.Network/loadBalancers//backendAddressPools/LB-TEST01-backend_pool/loadBalancerBackendAddresses/xxxxxx-xxxx-xxxx-xxxx-xxxxxx."
}]

You can temporarily lock down the azurerm module to version 2.17.0, it is still using the older Azure API and does not have this problem.

So this is interesting, I am using 2.15.0 and seeing this issue quite regularly.
provider "azurerm" {
  client_id       = var.azurerm_client_id
  client_secret   = var.azurerm_client_secret
  subscription_id = var.azurerm_subscription_id
  tenant_id       = var.azurerm_tenant_id
  version         = "~> 2.15"
  features {}
}

According to https://www.terraform.io/docs/configuration/modules.html#module-versions with "~> 2.15" you are allowing any version up to (excluding) 3.0.0. So, most likely you are using right now 2.19, which is the highest available one < 3.0.0

That is actually true. Thanks for catching that!

Btw, just in case it matters for some one, the same issue exist with managing LB health checks - same exact issue, and same (temporary) fix.

Saw this there as well. I am about to kick off a pipeline build to see if this solves the issues I've experienced as well. Just to clarify, I have pinned the provider to 2.17
provider "azurerm" {
  client_id       = var.azurerm_client_id
  client_secret   = var.azurerm_client_secret
  subscription_id = var.azurerm_subscription_id
  tenant_id       = var.azurerm_tenant_id
  version         = "= 2.17"
  features {}
}

Hi @zikalino or @qianwens Could you please take a look at this?
BTW, does Azure/azure-rest-api-specs#10131 fixes this?

Just as an FYI. I have gone through pipeline several times now with success using 2.17. That is about 173 resources spinning up, tearing down, and spinning up again. This also includes removing the depends_on that I mentioned earlier. I will be testing quite a bit more as well.

This one is still active and present :(
but it does work with the 2.17 version of the azurerm provider!
Test case - deploy Azure Loadbalancer

1x frontend
1x backend pool (add X VMs to it)
X health checks and ACL rules added to that backend pool

-> now create another backend pool or even a separate frontend and the same setup on the existing one
-> it fails to create a backend or even remove the existing one which is in no way connected to the backend that has VMs added to!
Error output:
[
  {
    "code":"DuplicateIpConfigurationReferenceOnBackendAddressPool",
    "message":"Found duplicate ipConfiguration reference /subscriptions/<SUBSCRIPTION_ID>/resourceGroups/<RG_NAME>/providers/Microsoft.Network/networkInterfaces/<VM-1>/ipConfigurations/primary on backend pool addresses /subscriptions//resourceGroups//providers/Microsoft.Network/loadBalancers//backendAddressPools//loadBalancerBackendAddresses/ and /subscriptions//resourceGroups//providers/Microsoft.Network/loadBalancers//backendAddressPools/backend-internal-dns/loadBalancerBackendAddresses/XXXXXX."
  },
  {
    "code":"DuplicateIpConfigurationReferenceOnBackendAddressPool",
    "message":"Found duplicate ipConfiguration reference /subscriptions/<SUBSCRIPTION_ID>/resourceGroups/<RG_NAME>/providers/Microsoft.Network/networkInterfaces/<VM-2>/ipConfigurations/primary on backend pool addresses /subscriptions//resourceGroups//providers/Microsoft.Network/loadBalancers//backendAddressPools//loadBalancerBackendAddresses/ and /subscriptions//resourceGroups//providers/Microsoft.Network/loadBalancers//backendAddressPools/backend-internal-dns/loadBalancerBackendAddresses/XXXXXX."
  }
]

@ArcturusZhang can we get the "Service Attention" and "Load Balancer" labels on this one so the service team can look at this API bug?

@ArcturusZhang Additionally, please check whether #10131 has already addressed that.

any updates regarding this fix in new provider version/upstream API?

Hi @gek0 this issue should have been fixed. I am going to close this issue. Please feel free to reopen this or comment if you see this issue again.

Reopen per request

#10131 doesn't actually fix this issue, this should be fixed on service side.

👋 any update here?

👋 any update here?

@tombuildsstuff Confirmed with service team, this has been fixed. I've created a PR terraform-providers/terraform-provider-azurerm#10263 for the linked TF issue.

@tombuildsstuff Confirmed with service team, this has been fixed. I've created a PR terraform-providers/terraform-provider-azurerm#10263 for the linked TF issue.


Xzyaoi/feat/inspector

This change is

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


FTSOv2 and Randomv2 examples

Purpose: This PR adds examples for FTSOv2 and RandomInterfacev2

Hi, please make sure that all checks pass before opening a PR for review, otherwise mark it as draft.
  [cause]: Error: Can't process doc metadata for doc at path path=/home/runner/work/developer-hub/developer-hub/docs/ftso/guides/randomnumber-v2-examples.mdx in version name=current

Additional changes that need to be made:

Full code snippets should not be defined in a .mdx file, they should be loaded using the raw loader from the developer-hub/examples folder, see other guides on how this is done:  https://github.com/flare-foundation/developer-hub/blob/f0ffe328b5256500378c88eda572bac10fb2fc1f/docs/ftso/guides/change-quote-feed.mdx?plain=1#L21
When a full Solidity code snippet is presented, it should include a "Open in Remix" button that loads the file from this path: https://github.com/flare-foundation/developer-hub/blob/f0ffe328b5256500378c88eda572bac10fb2fc1f/docs/ftso/guides/change-quote-feed.mdx?plain=1#L31
RandomNumberV2 examples should be added to the Use secure random onchain section of the Secure Random guide: https://github.com/flare-foundation/developer-hub/blob/f0ffe328b5256500378c88eda572bac10fb2fc1f/docs/network/guides/secure-random-numbers.mdx?plain=1#L86
The examples for FTSOv2 are good, but it likely does not belong under guides. Leave it as is for now, once the PR is ready I will rearrange this

@dineshpinto  Made the changes but not sure what the problem is with RandomNumberV2 reference error not building on the PR when it is locally.

@AmadiaFlare you are using RandomNumberV2 without importing it:
https://github.com/flare-foundation/developer-hub/blob/832f55a46d33337a9809041756031df060e1cedf/docs/ftso/guides/ftsov2-examples.mdx?plain=1#L47

@AmadiaFlare, is this ready for review?

Yes - this is ready for review.

@AmadiaFlare thanks, looks good. I have moved the code examples into the solidity reference for FtsoV2Interface. One thing, I see it's missing a code example for getFeedIndex i.e. converting from feed ID to feed index.


add ipsec_psk and vpn_pass variables

Secrets like ipsec_psk and vpn_pass should be configurable in advance, avoiding the random generator.
In order to filter these secrets from the integration test output, these values must be known and masked.
This can look something like:
- run: assets/generate-secret.sh ipsec_psk
          # SECRET=$(openssl rand -base64 32)
          # echo "::add-mask::$SECRET"
          # echo "ipsec_psk=$SECRET" >> $GITHUB_ENV
- run: assets/generate-secret.sh vpn_pass

l2tp_vpn.sh could perhaps take a -q argument (or otherwise remove the echo'ing of the credentials). These are already known to Terraform and terraform outputs, so we don't need the l2tp_vpn output.

These concerns are largely addressed by https://github.com/equinix/terraform-metal-vsphere/pull/19/commits/87be8e0c254ea50e0422a39f6789f67db16a8d45
The variables are not configurable in advance, but the secrets are not displayed during provision (especially e2e).
This commit may not have covered all cases, so I'm leaving the issue open for now. We should examine a successful E2E build log and look for any exposure of the VPN related secrets before closing this.

Closing this because the secrets are no longer emitted in build logs.
It may still be useful for these secrets to be predefined, to do so:
terraform import random_password.sso_password securepassword
terraform import random_password.vpn_pass securepassword
terraform import random_password.ipsec_psk securepassword
terraform import random_password.vcenter_password securepassword


Design: Maintaining retention window asynchronously in the DB

There is no db reingest equivalent in Soroban RPC. We should discuss the extent to which we want to support managing gaps in the database due to downtime or other inconsistencies. Options include:

trimming the database of everything that is not continuous on startup
erroring/forcing reingestion of any gaps in the retention window
allowing users to reingest arbitrary spans of history and/or to find/fill gaps in existing history like Horizon
doing nothing and just forcing users to wait for the retention window to fill before they get continuous history
others?

Each of these will result in a different level of work so we should decide first.

Objective is to write a one-pager outlining design choices and implementation details to maintain db retention window. Implementing the work is out of scope.

Closing as a dup of https://github.com/stellar/soroban-rpc/issues/196


Update state when receiving new props

I'm creating a component that uses createContainer for fetching data from a store. The fetch is dependent on the props I pass in (e.g. date). This change will make sure that prop-dependent fetches will re-execute when props change.

Hey, thanks for the PR. Happy to submit however linting is failing due to nextProps not being used. Can you remove it please?

Done :)

:+1: thanks


Window width can become less than 0, which causes a crash.

Hyprland Version
OS: archlinux
Hyprland ver: latest update (installed with hyprdots)
Bug or Regression?
Bug
Description
When you have 3 or more windows on 1 monitor horizontally tiled and 1 of them has the minimal width you can increase width of any other window until width of other window becomes less than 0, which causes a crash.
How to reproduce

Have 3 windows horizontally tiled.
Make 1 window have minimal possible width.
Increase width of any other window
Get crashed to swaylock

Crash reports, logs, images, videos
No response

Same behaviour with vertical tiling

fixed in git. Plus, "latest update" is not a version.


Newsletters: add 327 (2024-11-01)

[x] Lede, releases/RCs, topic entries @harding
[x] New topics: duplex channels and DLEQ @harding
[x] Illustration for SuperScalar item @harding
[x] Notable merges @Gustavojfe

Rebased on master to pull in the deep dive podcast for a link to it.  Made edits (thanks @vostrnad @LarryRuane @jonatack @bitschmidty !), added lede, added topic text*, added topic entries, removed image fixme (decided not to add one), and updated releases/RCs.  Reviewed @Gustavojfe section (thanks!).
* There's quite a bit of last-minute text for the DLEQ/PODLE entry.  Sorry.  If anyone leaves a review here post-merge, I'll prioritize addressing that feedback Friday.


Qt: typo fix and extra empty lines removal

Reasons for making this change:
5052629072d15dd6ecb789279184b248681bd62c: To keep consistency with other files in the repository, which all appear to have a single empty line at the end of them.
1bee1a16dcfa60097115eac1dfce82b22fbd0645: The name of the program is Qt Creator.

I would also remove these empty lines:
https://github.com/github/gitignore/blob/f9a44f6c36d9fdd66a1aa9610f1331fdabf5e32c/Qt.gitignore#L2
https://github.com/github/gitignore/blob/f9a44f6c36d9fdd66a1aa9610f1331fdabf5e32c/Qt.gitignore#L14
https://github.com/github/gitignore/blob/f9a44f6c36d9fdd66a1aa9610f1331fdabf5e32c/Qt.gitignore#L38

I would also remove these empty lines:

@davidebeatrici go for it

@shiftkey Done.

@davidebeatrici thanks!

@shiftkey You're welcome!

????
On 12 Feb 2018 1:30 pm, "Davide Beatrici"<EMAIL_ADDRESS>wrote:

Reasons for making this change:
5052629
https://github.com/github/gitignore/commit/5052629072d15dd6ecb789279184b248681bd62c:
To keep consistency with other files in the repository, which all appear to
have a single empty line at the end of them.
1bee1a1
https://github.com/github/gitignore/commit/1bee1a16dcfa60097115eac1dfce82b22fbd0645:
The name of the program is Qt Creator.
You can view, comment on, or merge this pull request online at:
https://github.com/github/gitignore/pull/2601
Commit Summary

Qt: Remove extra line at the end of file
Qt: Correct typo "QtCtreator" to "QtCreator"

File Changes

M Qt.gitignore
https://github.com/github/gitignore/pull/2601/files#diff-0 (5)

Patch Links:

https://github.com/github/gitignore/pull/2601.patch
https://github.com/github/gitignore/pull/2601.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/github/gitignore/pull/2601, or mute the thread
https://github.com/notifications/unsubscribe-auth/Ah6Zp_nXgWTSmjjfIR3XduIIw9hY6EZzks5tT6JYgaJpZM4SBoT7
.


Support configuration "chaining", or adding one configuration to another

Required to support aspnet/Hosting#448
Add support for adding one IConfiguration to another, e.g.:
public Startup(IHostingEnvironment hosting)
{
    var builder = new ConfigurationBuilder()
        .AddJsonFile("appsettings.json")
        .AddEnvironmentVariables()
        .AddConfiguration(hosting.Configuration);

    Configuration = builder.Build();
}

Should have two extension method overloads:
public static IConfigurationBuilder AddConfiguration(this IConfigurationBuilder builder, IConfiguration configuration);
public static IConfigurationBuilder AddConfiguration(this IConfigurationBuilder builder, string prefix, IConfiguration configuration);

/cc @divega

Cool. A ConfigurationConfigurationProvider :smirk: Is this needed in RC2?

Yes

@divega can you assign please?

Figuring out with @Eilon who will work on this.

Assigning to @haok. Hopefully he can start in a few days.

2909753f6c2aca8936a4a63c902eb9647e14f709

Hi everybody. I can't find this provider in v2.0, where did it go?


HDDS-11238. Converge redundant getBucket calls for FileSystem client delete

What changes were proposed in this pull request?
A few internal calls as part of FileSystem client delete involve repeated computation of getBucket(). Instead, we may precompute the OzoneBucket object and then pass it onto other dependent calls as they again compute the same object internally.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-11238
How was this patch tested?
Existing unit and integration tests should cover the changes

Thanks @adoroszlai and @ArafatKhan2198 for reviewing the patch.