Unable to specify version for custom plugin.

I'm developing a custom plugin and can't get pybuilder to pull new versions when they're available. How do I specify min and/or locked version for a plugin pulled from a pypi repository?

IIRC there is no mechanism built in to do this (yet). @mriehl to confirm

I'm not sure I understand what you're asking, but here are some thing that might help :)
https://github.com/pybuilder/pybuilder/blob/master/src/main/python/pybuilder/core.py#L210
https://github.com/pybuilder/pybuilder/blob/master/src/main/python/pybuilder/pluginloader.py#L156
https://github.com/pybuilder/pybuilder/blob/master/src/unittest/python/pluginloader_tests.py#L214
https://github.com/pybuilder/pybuilder/blob/master/src/unittest/python/pluginloader_tests.py#L226

@arcivanov I'd like pybuilder to validate the plugin version each time it runs to determine if a newer version of the plugin is available (according to the version spec) and, if so, download the updated version. For -dev versions, I want it to check timestamps and/or dev[N] numbers in the repo to make sure it has the latest version.  Basically, emulate maven's behavior for SNAPSHOT and release dependencies.
It doesn't seem to do any of that and I've resorted to running an rm ${venv}/lib/python2.7/site-packages/my_plugin* each time I update my plugin. This is not a scalable solution once this gets pushed out to our CI server and the rest of my dev team.
Am I missing something in my plugin definition that configures the version so pybuilder can check it? I saw the code in pluginloader._check_plugin_version, but I don't think that's getting hit. I can change my version spec in the use_plugin call to a later version than what's installed and everything continues to run without downloading the new plugin.

@mrburrito
https://github.com/pybuilder/pybuilder/blob/master/src/unittest/python/pluginloader_tests.py#L214
If you use use_plugin with version specification and set version according to https://www.python.org/dev/peps/pep-0440/#handling-of-pre-releases then pip will both pull and update prereleases for you. You can also use the VCS URL in which case plugin will always be reinstalled.
So either
use_plugin("pypi:your-plugin", "~=1.2.3.dev0")
or
use_plugin("vcs:http://github.com/...", plugin_module_name="plugin.module.name")
Please let me know if this works for you. You might have to play with the version spec a little to get exactly what you want, so please do read through PEP-0440 carefully.

None of that is working.
The plugin I'm working on is currently at version 0.3.1, with a dev version of 0.4.0.dev. When I publish/upload via the pybuilder distutils plugin, it appended the date to the end of the dev version rather than a number, so I deployed 0.4.0.dev20160310151716 to our internal PyPi repository (Artifactory).
My original include was use_plugin('pypi:my-plugin', '>=0.3.0') which, correctly, did not grab the dev dependency.
I updated it to use_plugin('pypi:my-plugin', '~=0.4.0.dev') and '~=0.4.0.dev0', neither of which worked.
I published my dev version as a release, 0.4.0 and tried again, using ~=0.3, >=0.3 and >=0.3.0 as version specs and pybuilder did not pull either my new 0.4.0 release or the 0.4.0.dev artifact from the repository.
I'm still faced with a situation where the only way I can get it to pull an updated version is by removing the cached plugin from the virtual environment.
Any ideas?

Oh, the commands I'm running to attempt to get pybuilder to download the plugin are:

pyb -t
pyb my_plugin_task
pyb install_dependencies

IIRC the "check-for-latest-version-of-plugin-and-install" never actually worked, but that was some weeks ago.

Um, weird, I'll debug and get back to you.

I just looked at the code and judging from this:
https://github.com/pybuilder/pybuilder/blob/master/src/main/python/pybuilder/pluginloader.py#L120
it would appear that it will upgrade if a version identifier is present.

Yeah, I can confirm that neither specifying the plugin with version or without will automatically upgrade it with a pyb install_dependencies.

So, the ThirdPartyPluginLoader https://github.com/pybuilder/pybuilder/blob/master/src/main/python/pybuilder/pluginloader.py#L64 triggers if the plugin has already been downloaded and then simply continues without checking for updates.

One would probably have to refactor the way in which the plugins are loaded.
You could try chaning the order in:
https://github.com/pybuilder/pybuilder/blob/master/src/main/python/pybuilder/reactor.py#L63
And put the downloading_thirdparty_plugin_loader first.

I'll try that now locally and get back.

So, reversing the order of the plugin loaders AND specifying the version will update the plugin.

Not sure what kind of stuff breaks when doing this, all unittests pass though.

I don't think it's a problem. Running pybuilder will always cause network I/O though.
I think we could roll with this but we really need to settle on an update strategy (either requested by user as a task, so that the user can choose how to handle it with default tasks for instance, or as a clever automatism or even on a per-plugin basis).

On 10 Mar 2016, at 17:21, Valentin Haenel<EMAIL_ADDRESS>wrote:
Not sure what kind of stuff breaks when doing this, all unittests pass though.
—
Reply to this email directly or view it on GitHub.

My vote would be to automatically check for, and update outdated plugins if a fuzzy version specifier is provided. If you have a locked version, no need to check once it's installed. I think general user expectation (granted, this is from my specific viewpoint) would be that plugin updates are transparent to them once they've specified they want ~=, >=, <=, >, or < some version.

Yeah that sounds like intuitive behaviour. But when the automatic upgrade fails, is it an error? I don't think it should be transparent. Perhaps a warning about the failed upgrade?

On 10 Mar 2016, at 17:45, Gordon Shankman<EMAIL_ADDRESS>wrote:
My vote would be to automatically check for, and update outdated plugins if a fuzzy version specifier is provided. If you have a locked version, no need to check once it's installed. I think general user expectation (granted, this is from my specific viewpoint) would be that plugin updates are transparent to them once they've specified they want ~=, >=, <=, >, or < some version.
—
Reply to this email directly or view it on GitHub.

That's a tough one. On the one hand, you might be expecting the updated version; particularly if you're doing active development on a plugin. On the other, you may not need the new version and don't want your builds failing if it can't be retrieved.
I think I lean towards failing by default with a command line option to treat those failures as a warning and continue the build. If I'm not locking down the version, I should be expecting updates when they become available.

+1 on expecting a new version when available, it's the way we handle dependency updates too

Ok peeps.
ThirdpartyPluginLoader is merged with a Downloading one. The logic is now as follows:
If a plugin is "vcs:..." then force reinstall. If a plugin is "pypi:..." and version is specified and version specifier set contains at least one operator that is not "==" or "===" then update the plugin.
Try loading plugin module.
If plugin module is not loaded (which may be the case if it's a built-in third-party or PYPI plugin with no version specifier or with an exact version that has not been installed yet) then install plugin.
Try loading plugin module for the final time.
@mrburrito please try out https://github.com/pybuilder/pybuilder/pull/342.
You can do this by running pip install git+git://github.com/arcivanov/pybuilder#issue_340
@mriehl @esc please review and comment.

Hmm, don't we want to update if no version is present at all?

Still not working. I installed that patch version and I'm using the build.py file below to test. The first time I run pyb, it downloads the most recent dev build of my_plugin and executes the lver task correctly, outputting the version string of my plugin.
If I then modify that version string and upload a new dev version to my pypi repository, it fails to grab the new version and still outputs the old version string. I confirmed that a pip install --upgrade --pre my_plugin grabs the new version. The pyb upload task in my_plugin is appending the timestamp for the dev versions, so I end up with 0.4.0.dev20160316175310 and so on.
build.py
from pybuilder.core import init, use_plugin

use_plugin('python.core')
use_plugin('python.install_dependencies')
use_plugin('pypi:my_plugin', '>=0.4.0.dev')

default_task = 'lver'

I'll second @mriehl; I think you should auto-update to the latest version of a plugin unless the version is explicitly locked.

@mrburrito could you provide a debug log of your build please? It's pretty hard to know what exactly isn't working based on "doesn't work" :)

@mriehl @mrburrito here's the problem:
My thinking is if you specify "no version at all" it means you don't care about the version and if you have SOME version then you are already good.
If I implement this update for no version at all it means that EVERY build will go through network IO and PyPi. Do you really want that?

Also, due to how plugin loading is implemented, it's not going to be "collect all external plugin references and install/update plugins once", it's going to be "for every plugin encountered, install/update independently", i.e number of trips is literally unbounded.

good point. I guess from the perspective of other build tools, they typically require a version specification, which makes that check much more efficient.

Well, we could you pkg_resource entry-point discovery, but that will require ditching the current plugin loading system destroying backward compatibility.

to clarify my earlier point -- I've changed my opinion on behavior if no version is specified; not suggesting a version should be required. If there is no version, assume that any installed version is acceptable

@mrburrito cool!
Could you also provide me with pyb -X -v debug log for the build that isn't updating the plugin the way you want?

@mrburrito did you have a chance to get the debug log?

I got stuck putting out some fires at work today. I'll get the log for you
first thing tomorrow.
On Thu, Mar 17, 2016 at 6:28 PM, Arcadiy Ivanov<EMAIL_ADDRESS>wrote:

@mrburrito https://github.com/mrburrito did you have a chance to get
the debug log?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/pybuilder/pybuilder/issues/340#issuecomment-198108944

Here's the log file, along with my build.py and the relevant @task from the plugin.
pybuilder_aws_lambda_plugin excerpt
VERSION = (0, 4, 0, 'dev')
__version__ = VERSION
__versionstr__ = '.'.join(map(str, VERSION))

@task
def lver(logger):
    logger.info("VERSION: {}".format(__versionstr__))

build.py
from pybuilder.core import use_plugin

use_plugin('python.core')
use_plugin('python.install_dependencies')
use_plugin('pypi:pybuilder_aws_plugin')
use_plugin('pypi:pybuilder_aws_lambda_plugin', '>=0.4.0.dev')

name = 'pyb_test'
version = '0.1.1'
default_task = 'lver'

Version of pybuilder_aws_lambda_plugin in virtualenv site-packages: 0.4.0.dev20160316175310
Versions of pybuilder_aws_lambda_plugin in pypi repository:

0.4.0.dev20160310151716
0.4.0.dev20160316174500
0.4.0.dev20160316175220
0.4.0.dev20160316175310
0.4.0.dev20160316175433
0.4.0.dev20160316180346
0.4.0.dev20160318125108

pyb_debug.txt

@mrburrito
You have an old version of the PyB it seems.
Here's what you're supposed to be getting in relevant parts:
[DEBUG] Found task 'list_dependencies' with dependencies []
[DEBUG] Registering task 'list_dependencies'
[DEBUG] Loading plugin 'pypi:pybuilder_aws_lambda_plugin' version >=0.4.0.dev
[INFO]  Downloading or updating plugin pypi:pybuilder_aws_lambda_plugin version >=0.4.0.dev
[DEBUG] Invoking pip: ['/Users/arcivanov/.pyenv/versions/3.5.1/envs/karellen-venv/bin/python3.5', '-m', 'pip.__main__', 'install', '--upgrade', 'pybuilder_aws_lambda_plugin>=0.4.0.dev']
[ERROR] The following pip error was encountered:
  Could not find a version that satisfies the requirement pybuilder-aws-lambda-plugin>=0.4.0.dev (from versions: )
No matching distribution found for pybuilder-aws-lambda-plugin>=0.4.0.dev

[ERROR] Could not install or upgrade plugin pypi:pybuilder_aws_lambda_plugin version >=0.4.0.dev: Missing plugin 'pypi:pybuilder_aws_lambda_plugin': Failed to install plugin from pybuilder_aws_lambda_plugin>=0.4.0.dev.

The build branch would not call built-in loader if there are : in the name of the plugin. Yet your log indicates this:
[DEBUG] Trying to load builtin plugin 'pypi:pybuilder_aws_lambda_plugin'
[DEBUG] Trying to load third party plugin 'pybuilder_aws_lambda_plugin'
[DEBUG] Found third party plugin 'pybuilder_aws_lambda_plugin'

UPD: I know what the problem is - I gave you an update pip command with wrong syntax. Sorry!
pip install --upgrade git+git://github.com/arcivanov/pybuilder@issue_340
Branch is separated with an @ and not # :sob:

That worked! It updates correctly now, at least for the dev versions. Thanks!

I'll merge as soon as @mriehl reviews

Done. Already reviewed a few days ago, but was waiting to see if it solves the issue author's problem ;)

On 21 Mar 2016, at 17:58, Arcadiy Ivanov<EMAIL_ADDRESS>wrote:
I'll merge as soon as @mriehl reviews
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

Thanks for all the hard work.

@mrburrito released with 0.11.8.


No collection after creating first user

I can't see any collection after creating the first user for cms. Also there is no collection creation option.

Hi Nisan!
Can you check in PocketBase the API rules for the collection you wish to modify from PocketCMS?

If the view rule is set to admins only, the user logged into PocketCMS won't be able to see it since they aren't an admin of PocketBase. In addition, a user in PocketCMS can't create a new collection, that is something that should be done from within PocketBase.
There is some more work to be done on permissions in the future so that you don't have to completely open up the API rules to anyone in order for PocketCMS to work. The ticket is in the project dashboard if anyone is interested in picking it up!

Thanks, that solve the issue now I can see the collections.
I have another question. Every user can see same data on the collection. Can we have multitenancy?

Thanks, that solved the issue, now I can see the collections. I have another question. Every user can see same data on the collection. Can we have multitenancy?

That would be a great feature. I’ll add it to the list of ideas and try to tackle it in the near future!
Any other questions feel free to send them here or to<EMAIL_ADDRESS>Thanks for checking out the project :)


Import-LocalizedData must NEVER error if culture not found

The steps to reproduce is difficult but we have wasted multiple man days chasing issues with Import-Module/Import-LocalizedData with servers running En-GB culture. We've seen it with smbshare and powershell.archive. An example of the issue is captured in https://github.com/PowerShell/PowerShell/issues/4180. While that bug was closed and the user told to file a bug in the Archive specific location the ultimate issue is with Import-LocalizedData or Import-Module. If a language specific localization is not found it MUST NOT fail to load the module.

The problem is that import-module doesn’t know why the psm1 script failed, only that an error was thrown.  The issue is in the module.  I’ll submit a PR to fix Archive module

We've also seen this in the SmbShare. I'm sure we saw it with another module but it was a while ago and I'm having trouble finding. This has moved from an anomaly to a recurring problem. How is this not a Import-LocalizedData bug? Why is it throwing instead of warning?

Another way to put this. Adding a work around to the Archive module is fixing the symptom not the disease.

I've updated the title to focus on Import-LocalizedData.  I'm open to discussing having some fallback capability to Import-LocalizedData.

As I see it, the problem is two things:

Import-LocalizedData writes an error when it can't find a localization
Even benign errors break module dependency

If a module calls Import-LocalizedData without suppressing the inevitable error, that doesn't techincally stop the module from being imported and used. As a result, of TWENTY THREE modules in $PSHome\Modules which use Import-LocalizedData (on my Windows 10, PS5.1 system) only two use -ErrorAction to suppress the errors.  I don't know how many of these modules are actually localized, but if there's a betting pool, I'm taking ZERO.
This is a problem because if another module or script specifies a dependency on any of these modules (e.g. via RequiredModules in the manifest or via #requires -module or just by calling Import-Module -ErrorAction Stop ... then those modules or scripts break whenever they are used in a locale that isn't explicitly localized.
The only reason I can think of that this hasn't come up before is that module authors basically never document their dependency on "in the box" modules, and nobody but Microsoft bothers to localize at all...
If I just use a cmdlet from a module with a localization problem, you'll see the localization error from the autoloading, but the cmdlet will run and produce results with no problems. It's only when I put the module in my RequiredModules or use a #requires that it causes a terminating error.

My suggestion is that if it does not find a specific culture folder it throws a warning and does not terminate.

I should note that many of these modules (e.g.  Appx, BitLocker, etc) don't even have the fallback data section in the file -- @sdecker has been lucky so far, Archive and SmbShare module do have default values in a data section, so this localization error isn't fatal to the module except when the module import happens when ErrorActionPreference is set to Stop.  For these other modules like Appx and Bitlocker, the Import-LocalizedData failure will result in further errors whenever anything tries to access that LocalizedData.
Clearly Microsoft isn't setting a good example for how to localize modules, so there should be no surprise that nobody else is doing it.
From my perspective, the most immediate change that would help would be for the help to be changed to highlight the fact that when the localization files are missing it will produce an error, and that the caller really must decide how to handle that and do something.
A single useful example should show the right way to do it, combining the default data in Example 5 and error handling! Perhaps the example could turn the error into a warning that English messages will be used instead...

If you want my 2c on a better long-term design for Import-LocalizedData:
Make a Import-LocalizedStringData which:

Doesn't have a SupportedCommand parameter
Expects the file to have just the content that ConvertFrom-StringData supports
Guarantees the output is a [dictionary[string,string]] rather than a hashtable

String dictionaries are clearly the main use case for localization, the other features of Import-LocalizedData aren't generally used for translation, and they make it more complicated to use for it's primary purpose: almost every use of Import-LocalizedData has an internal ConvertFrom-StringData which would be unnecessary with Import-LocalizedStringData.

Requires a DefaultData string dictionary parameter
Guarantees that the output will have a value for every string in the DefaultData parameter

This would ensure that the command never needs to produce an error -- it can fall back to the DefaultData -- it would also allow partial localizations to use the default strings for untranslated content.

Has a fallback folder for localizations that is user-editable (e.g. in AppData or ~.config)
Respects a PreferenceVariable for whether or not to generate a language file in the user location is no localized data is found for the current culture

This would allow knowledgeable users to easily produce translations for themselves, without waiting for Microsoft to get around to supporting UK English 😉

Totally agree. This has been awkward for a long time and caused plenty of issues so far. Great write-up for a solution.

@Jaykul I like your proposal and something we can look into for 6.1.0.  If we go that route, then we wouldn't make any changes to Import-LocalizedData.

Agreed @SteveL-MSFT, given the varied uses of Import-LocalizedData like mine for non-localization, and my count of the modules in $PSHome that wouldn't work even if you made it warn instead of error -- I'd be reluctant to change it much -- especially to suppress an error which can already be suppressed with -ErrorAction
Focus on improving the documentation, and on fixing whatever testing process is allowing you to release "localized" modules that crash on anything other than en-US -- and of course, on fixing the actual modules.  For now, I'm at the point where it's clearly problematic for us to add a dependency on any module that's localized.
We currently work around the Archive module bug like this:
function DoNothing {}
Set-Alias Import-LocalizedData DoNothing
Import-Module Microsoft.PowerShell.Archive
Remove-Alias Import-LocalizedData
Remove-Item function:DoNothing

Although we could, arguably, use $PSDefaultParameterValues to force en-US instead (which might work for some of these other modules) ...


For development, create a response caching option.

The external service failed and it this moment is hard anythig develop.

We can reuse the "file" logger? How would you like to use it / set it?


Fix leaking goroutines when using Google KMS keys

The KeyManagementClients needs to be closed to avoid leaking goroutines;

in keys/google/google.go; Generate and Signer functions

Currently tests fail when using Google KMS keys (FLOW_WALLET_DEFAULT_KEY_TYPE=google_kms)

This would allow closing the client manually; https://github.com/onflow/flow-go-sdk/pull/204


Support for loading frames using WADO-RS (octet-stream)

Example of a WADO-RS (frame) request:
curl http://localhost:8042/dicom-web/studies/2.16.840.1.113669.632.20.1211.10000315526/series/<IP_ADDRESS>.1<IP_ADDRESS>.54693.30000006100507010800000005268/instances/<IP_ADDRESS>.1<IP_ADDRESS>.54693.30000006100507010800000005466/frames/1 -H 'accept: multipart/related; type=application/octet-stream'
Documentation
http://book.orthanc-server.com/plugins/dicomweb.html

I removed 2 commits from this PR and created a new PR with a JPEG Baseline (8bits) fix.
https://github.com/chafey/cornerstoneWADOImageLoader/pull/68


callbacks example

please provide a custom callback example. e.g. take ATAC counts and do LSI (standard preprocessing for ATAC data)


Variable names shown in scalar variable lists are improperly sorted.

I was investigating 3035 and noticed that the variable list for the pseudocolor plot was incorrectly sorted. I checked with 2.13.3 and it was properly sorted there, but starting with 3.0.1 (possibly 3.0.0, but I don't have that installed anymore), the list wasn't sorted properly.
Here is an image of the menu:

This image is from Windows and for some reason many of the variables were greyed out. This wasn't the case on Linux (quartz).
Here is the file that demonstrates the bug.
3035_pointexample.tar.bz2.zip

I can't tell for sure from the picture but its conceivable that sorting is performed only among valid variables...which when there are no non-valid variables would go unnoticed. But, when there are many, it would stand out as a problem. The logic to handle this I think is in src/winutil/VariableMenuPopulator.C

I am unable to replicated the greyed out variables on Windows.
I did a comparison between the variable menus on 3.0.0 and current 3.1RC.
All are the same except these:
from 3.0.0, (sorting is case-sensitive) Highlighted entry, it matches first entry in submenu

from 3.1.3, (sorting is case-insensitive), Higlighted entry, by its name, is in the wrong location.  However it also doesn't match the first entry in the submenu.
I think the group name is the problem here, if it matched the first var, then its position in the top-level menu would be correct.

@markcmiller86 Since you made the changes to the VariableMenuPopulator to do the case-insensitive sort order, would you be able to figure out why this one-particular grouping name is wrong?

I just figured out why I got the greyed out variables on Windows. When I unpacked the zip file I only extracted the top level silo file and not the directory. When I also extracted the directory, then the variables show up properly.
Sorry about the rabbit hole Kathleen!
I think the entries in the expanded subentry were correct based on the old case sensitive sorting, but the XSPH... variables shouldn't be in that list based on a case insensitive sorting. My guess is that the lists for the top level menu and all the sub menus were done with a case sensitive sorting and then those lists were resorted case insensitive. There should have been a global case insensitive sorting done and then that list should have been broken down into sub lists.

@markcmiller86 Since you made the changes to the VariableMenuPopulator to do the case-insensitive sort order, would you be able to figure out why this one-particular grouping name is wrong?

It looks the relevant commit is #3550. I believe the grouping names (as you are calling them) (e.g. the intermediary menu names between the Plot object's entries and the leaves) should simply by the top-entry in each group. Its concievable #3550 was syntactically compatible but functionally incompatible with logic in `VariableMenuPopulator::IsGroupingRequired" here, https://github.com/visit-dav/visit/blob/cf721827e71da0523552ea2824079d04c44e95a1/src/winutil/VariableMenuPopulator.C#L1958
But, my attention is currently on other tasks.

Thanks @markcmiller86

@markcmiller86 do you remember why you decided to use tolower instead of something like strcasecmp here:
https://github.com/visit-dav/visit/blob/1ebf4aaab5adb748c24c9559fb0d4b1f1fbef0f6/src/winutil/VariableMenuPopulator.h#L134-L142

@markcmiller86 do you remember why you decided to use tolower instead of something like strcasecmp here:

I think because this is C++ code (std::string) and strcasecmp is C lib (char *) string library.

Oh, wait, you mean why didn't I just implement as...
return strcasecmp(s1.c_str(), s2.c_str()) <= 0;

Hmmm...good question. I may have been wanting to understand how to do it with C++ and so just used it as an opportunity to do that.

You don't think the extra string copy's add unnecessary overhead? That said with the caveat that I don't know how strcasecmp (or stricmp on Windows) performs in comparison.

You don't think the extra string copy's add unnecessary overhead?

Oh, good catch! Yes, they do for sure. And, its happening every time we iterate variable menus and compare strings. So thats really bad.
strcasecmp would be way better now that you've pointed this out.
I'm just stunned that same ops in C++ aren't possible? Or, maybe I just didn't know enough about how to do equiv. in C++ to get it performant.

Or, maybe I just didn't know enough about how to do equiv. in C++ to get it performant.

Yeah, its the latter...I didn't know enough when I wrote this, nor apparently think or care about performance here. There are some nice C++ ways of doing it


include enumeration of missing permissions in error log

put extra info in log to help diagnose #1008

The travis-ci failure is because com.android.billingclient:billing has been updated.
> Lint found errors in the project; aborting build.

  Fix the issues identified by lint, or add the following to your build script to proceed with errors:
  ...
  android {
      lintOptions {
          abortOnError false
      }
  }
  ...

  Errors found:

  /home/travis/build/jberkel/sms-backup-plus/app/build.gradle:58: Error:
 A newer version of com.android.billingclient:billing than 2.0.3 is available: 2.1.0 [GradleDependency]
      implementation 'com.android.billingclient:billing:2.0.3'
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

@jberkel I'm loath to push any patch where the CI fails, even though that appears to be unrelated to the patch. Your advice would be much appreciated.


Overhaul the tutorials, improve directory structure visibility, add new content, link headers

Targeted at issue #268, and discussion therein.

Codecov Report

Merging #360 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #360   +/-   ##
=======================================
  Coverage   91.27%   91.27%
=======================================
  Files          26       26
  Lines        4023     4023
=======================================
  Hits         3672     3672
  Misses        351      351

Continue to review full report at Codecov.

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

Based on some recent discussions, I'm going to push forward with removing the numbering system of the tutorials.  I'm also going to move the tutorials to the main landing page on GitHub repo, with modified Makefile for the docs.  I propose the docs get re-rendered with dpi=300 or higher to suit high resolution (e.g. Retina) displays.  I also added a README that will render on GitHub with clickable links.  I will also add headers that can be clicked on in the documentation pages.

OK, I've renamed the tutorials with a compromise: the topical themes are grouped by number, and notebooks are left unsorted within theme, when navigating locally.  The README.md file and doc Table of Contents remain sorted within the theme based on our prescribed ordering.
$ ls -1
01-lightcurve-files.ipynb
01-target-pixel-files.ipynb
01-using-the-periodogram-class.ipynb
01-what-are-lightcurves.ipynb
02-how-to-make-a-supernova-lightcurve.ipynb
02-how-to-recover-the-first-tess-candidate.ipynb
02-how-to-use-lightkurve-for-asteroseismology.ipynb
02-recover-a-planet.ipynb
03-appending-lightcurves.ipynb
03-cutting-out-tpfs-from-tess-ffis.ipynb
03-how-to-use-prf-photometry.ipynb
03-making-custom-apertures.ipynb
03-making-fits-files.ipynb
04-how-to-detrend.ipynb
04-identify-rolling-band.ipynb
04-interact-with-lightcurves-and-tpf.ipynb
04-removing-cbvs.ipynb
04-replicate-vanderburg-2014-k2sff.ipynb
04-replicate-vanderburg-2014-lightkurve.ipynb
README.md

The 02-how-to-use-lightkurve-for-asteroseismology tutorial takes a really long time to run, since it's doing multiple SFF corrections on a short cadence lightcurve.  I kept getting timeout warnings while running the notebook, and finally resolved it by updating the conf.py file in docs/source

In the "how to recover a planet" tutorial, I updated the dependence on transit_periodogram in favor of the astropy 3.1 implementation of BoxLeastSquares.
The "make a tpf from FFI" tutorial breaks on make notebooks because it expects a data directory with fits files in it.  I propose we use packaged or fetched files to demo the from_fits method.  I also propose extending this tutorial to include how to get TPFs from TESS-CUT produced tpfs.

Thanks for all these improvements @gully!  I think the solution to the "make a tpf from FFI" tutorial breaking is to include a !wget something cell.  We wouldn't want to package large FFI's.

Thanks for this PR @gully!  Your changes to conf.py look good and I like the new README.md and the renaming of files.
It looks like we have a merge conflict with three tutorials.  I think we applied bug fixes to those since the first commit in this PR (e.g. we recently renamed phase into transit_midpoint as an argument of lc.fold()).  I'm not sure that rebasing will work in this case because the notebooks have been re-executed?
Once you fix the merge conflict I'm happy to glance over the notebook changes (because I need to learn how BoxLeastSquares works myself =)) and merge this!


[FLINK-4733] Port WebInterface to metric system

This PR relies on #2613, #2614 and #2615. Thus, the first 5 commits should not be reviewed here.
This PR ports the remaining parts of the WebInterface to rely on the metric system.
TaskManager metrics
In a7011e8305d7c828fabc4245358c2d21568fd561 the TaskManagersHandler is modified to use the metric system. In addition, the garbage collector section in the WebInterface was enhanced to no longer rely on hard-coded GC names, but instead be dynamic. The recently introduced network metrics have been added as well.
cbff6d6aab80bc423a09aa6b62c80a2f409d796a then removes the remnants of the old metrics that are now unused. This affects the TaskManager(no longer gathers these metrics) and Heartbeat messages (no longer includes a metrics report). As a result the DropWizard dependency was removed. The transitive jackson dependency is now explicitly set for both flink-runtime and flink-runtime-web.
Task metrics
The Webinterface shows how many records/bytes each task has received or sent. Until now these were gathered with system specific accumulators.
cab25496ff5991de60e757f68c5d5139c86f34ba these accumulators were removed.
Under the new system, bytes In/Out is measured per task (since it doesn't make sense within chained operators), while records In/Out is measured per operator. In order to display the records metrics for each task it was thus necessary to "reuse" some operator counters for the task.
This is implemented in<PHONE_NUMBER>8a61bec0418adb833508dcaf276170 by re-registering the numRecordsIn counter of the first operator in the chain and the the numRecordsOut counter of the last operator on the task level
This re-use could (sadly) not be done automatically within the metric system. Instead 2 helper methods were added to the OperatorIOMetricGroup, which are called for example within BatchTask#invoke(), which forward the counters to the TaskIOMetricGroup where they are stored and re-registered.
With these metrics being re-registered they can be accessed easily via the MetricQueryService from the WebInterface handlers. The downside is that this service provides no guarantee that the most up-to-date metrics for a finished task will be transferred. It was thus necessary to store a snapshot of these IOMetrics within the ExecutionGraph, similar to the system accumulators, which the handlers could access as well.
The handlers were finally adjusted in 8be5145a9406dc8d6d661299c9ee98aa09233df4. For running tasks they access metrics via the MetricQueryService, whereas for finished tasks they rely on the metrics stored in the ExecutionGraph.

Will rebase now, this will also fix the test failure.

@rmetzger Rebased version is up.

Note that 2 new methods were introduced into the StreamConfig: setChainStart() / isChainStart() to better determine which output counter should be used for the task. Previously this used the same logic as the operator name extraction, which was bugged for multi-chains.

Thank you for rebasing.
This run:
had the following error: https://s3.amazonaws.com/archive.travis-ci.org/jobs/170428661/log.txt
Failed tests:
  CoordinatorShutdownTest.testCoordinatorShutsDownOnFailure:94 org.apache.flink.runtime.executiongraph.ArchivedExecutionGraph cannot be cast to org.apache.flink.runtime.executiongraph.ExecutionGraph

I suspect we need to change the cast there to AccessExecutionGraph.

I tested the change locally, it works. +1 to merge.

I just found another bug related to forked-chains. Right now only the output of a single operator is used as the task output counter, where as we should actually use both of them. Will fix it while merging.

The CoordinatorShutdownTest can't be fixed with a cast. This test assumes that the actual ExecutionGraph is still available when a job is finished since it tries to access the CheckpointCoordinator within. This however no longer works; finished jobs are immediately archived, and the archived version does not contain the CheckpointCoordinator.
A possible fix is to not let the job fail immediately but block him, ask for the ExecutionGraph while being blocked (which, since the job is still running actually returns the runtime ExecutionGraph) and store the reference, and then let the job fail.

Both issues should be fixed now, but I'll let travis take another stab at it.

The CoordinatorShutdownTest fixes look reasonable.


remove print config list

Why are these changes needed?
remove print statement for config list in test.
Related issue number

Checks

[ ] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
[ ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
[ ] I've made sure all auto checks have passed.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (899b250) 37.79% compared to head (86729fe) 12.92%.

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1637       +/-   ##
===========================================
- Coverage   37.79%   12.92%   -24.88%
===========================================
  Files          50       50
  Lines        5704     5704
  Branches     1295     1404      +109
===========================================
- Hits         2156      737     -1419
- Misses       3377     4951     +1574
+ Partials      171       16      -155

Flag
Coverage Δ

unittests
12.92% <100.00%> (-24.88%)
:arrow_down:

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

The test failure is likely due to GPT-3.5 (?)'s undeterminstic response. Try re-running it again.


Couldn't install distrobox container first time at phase 4

setup.log
No idea what went wrong here. The log doesn't seem to point to anything just exit 1 and no further elaboration
POP_OS 2.04 with an Nvidia RTX 4090 Driver ver 550

setup.log
Same. I assume you also were trying to use nightly?
env.sh -> IS_NIGHTLY=1
Looking into where it died, the wget for the ALVR-nightly Appimage failed.
$> wget --show-progress 'https://github.com/alvr-org/ALVR-nightly/releases/latest/download/ALVR-x86_64.AppImage'
--2024-07-04 12:31:21--  https://github.com/alvr-org/ALVR-nightly/releases/latest/download/ALVR-x86_64.AppImage
Resolving github.com (github.com)... <IP_ADDRESS>
Connecting to github.com (github.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://github.com/alvr-org/ALVR-nightly/releases/download/v21.0.0-dev01+nightly.2024.07.03/ALVR-x86_64.AppImage [following]
--2024-07-04 12:31:22--  https://github.com/alvr-org/ALVR-nightly/releases/download/v21.0.0-dev01+nightly.2024.07.03/ALVR-x86_64.AppImage
Reusing existing connection to github.com:443.
HTTP request sent, awaiting response... 404 Not Found
2024-07-04 12:31:22 ERROR 404: Not Found.

And so we go deeper and learn that ALVR-nightly is no longer maintaining an Appimage!
So ALVR-Distrobox-Linux-Guide needs to be updated to use the tarball in the case of IS_NIGHTLY=1, it seems.

To be completely honest, distrobox installation method could soon be deprecated/archived in favor of better explanation of how to do it on alvr side (already partially done, hybrid GPU just needs better explanation) + alvr flatpak getting nvidia support as well, which should work everywhere, also launcher is getting close to release

To be completely honest, distrobox installation method could soon be deprecated/archived in favor of better explanation of how to do it on alvr side (already partially done, hybrid GPU just needs better explanation) + alvr flatpak getting nvidia support as well, which should work everywhere, also launcher is getting close to release

Rough ETA on Nvidia flatpak support? Because that would solve pretty much all of my issues


Add rm funcionality

Address #53

Hello @Lucas-C could you review my PR?

Thank you for your contribution @ebotiab 👍
I merged this MR

This has been released in version 0.4.0: https://pypi.org/project/pdfly/#history


Routing buckets export

I am looking to use the exports['pma-voice']:updateRoutingBucket export, but it doesn't seem to exist/work anymore.
When trying to use this I get the following console error. Was the export removed for some reason? Thanks.
SCRIPT ERROR: @safezones/server/main.lua:20: No such export updateRoutingBucket in resource pma-voice

They're no longer needed, as voices are proximity based


[CodeCamp #1535] Add SAD

Motivation
Add MattingSAD of MMEditing to MMEval and complete the adaptation.
Modification
Add MattingSAD of MMEditing to MMEval
The PR link using mmeval.SAD in mmediting：https://github.com/open-mmlab/mmediting/pull/1592#issue-1525897921

LGTM 🚀


Adding rule to disable insecure APIM ciphers support

PR Summary
Adding to the APIM rules a new rule to check if deprecated ciphers are in use. This is related to issue 1128.
I have broken out the existing APIM Cipher And Protocol rule into different rules.
PR Checklist

[x] PR has a meaningful title
[x] Summarized changes
[x] Change is not breaking
[x] This PR is ready to merge and is not Work in Progress
Rule changes

[x] Unit tests created/ updated
[x] Rule documentation created/ updated
[x] Link to a filed issue
[x] Change log has been updated with change under unreleased section

Other code changes

[x] Unit tests created/ updated
[x] Link to a filed issue
[x] Change log has been updated with change under unreleased section

@ms-sambell Thanks Sam.
The build issues mostly seem to fail around the help. If you check under docs/en/rules/ you will find documentation for each rule. I'd suggest copying and updating one that is similar such as Azure.APIM.Protocols since it is related. Just add your help content to a new .md file with the same name as the rule. Alternatively you can use the snippet in an empty .md file by typing rule.
Also if you adding a unit test under tests/PSRule.Rules.Azure.Tests/Azure.APIM.Tests.ps1 would be helpful. To do that:

Duplicate and update the Azure.APIM.Protocols block.
Update at least one API Management instance in tests/PSRule.Rules.Azure.Tests/Resources.APIM.json that would pass/ fail.

Tip: You can mention the issue by Fixes #1128 to automatically link the issue for automatic closing.

@BernieWhite Updated as per the feedback.

Tests:

Instance A with a False value.
Instance B without setting the ciphers to False.

I also added a sentence to the doco explaining the default value is True.


allocation and promotion rates look wrong on jdk9

When running on jdk9 the allocation rate looks way lower than expected and the promotion rate seems to be missing.

Live/max data size also seem to be broken on jdk9.


Map keys to mouse1/mouse2?

Hi.
Thanks for this awesome app.
Im a very old gamer (pre-2000) and I've always used mouse1=forward, mouse2=back. Nowadays people use WASD but im not used to it.
Is there any way to do it? The layout configurator wont allow me
Thanks.

Mouse button binding is not yet flexible.  (In code, TranslateMouse has MouseButtonsInput hard-coded to turn mouse button state into left/right triggers.)  This is a good idea though.

I'm using your software for a game bot neural network which runs in the background but I cannot use my mouse for normal PC use because it affects my data xD

@Committing Have you considered writing direct simulation code with https://github.com/DavidRieman/SimWinInput#simulate-gamepad?  I think the Xbox app still requires to be in focus to receive the controller input (whether simulated or real) so you still won't be able to use the PC very much at the same time.

@Committing Have you considered writing direct simulation code with SimWinGamePad? I think the Xbox app still requires to be in focus to receive the controller input (whether simulated or real) no matter what approach you take with it. So you might still not be able to use the PC for very much at the same time. XboxKeyboardMouse is great for its designed purpose, but you might be adopting an extra layer unnecessary for such automation intents.

Thanks for the link - I'll check it out right now! I am using Python at the moment for this.
When using a keyboard/mouse this particular game requires focus but doesn't require focus when tabbed out if coming from a controller virtual or otherwise.
I agree it is another layer of seemingly unnecessary complexity but there have been many specific issues that have lead me down the path to using your software. It has however been very handy/convenient for me, great work! I'm going to set up the bot on a spare PC so my clicks won't affect it anymore while I continue to work on it. Thanks!

@Committing, I'm interested to seeing your NN if you decide to open source it.

@Committing Have you considered writing direct simulation code with SimWinGamePad? I think the Xbox app still requires to be in focus to receive the controller input (whether simulated or real) no matter what approach you take with it. So you might still not be able to use the PC for very much at the same time. XboxKeyboardMouse is great for its designed purpose, but you might be adopting an extra layer unnecessary for such automation intents.

My mouse doesn't work. I can't use any games. I don't understand why. I'm Chinese. English is not very good. What's the dead zone


V1.1 test

Pull request checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[x] Build (yarn build) was run locally and any changes were pushed
[x] Lint (yarn lint --check) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

add synchronizer.test.ts, userState.test.ts
merge v1.0.1

Does this introduce a breaking change?

[ ] Yes
[ ] No

Other information

This pr brings in some changes from the v1 branch (most notably #140 and #145). The v1 and v1.1 branches have diverged enough that I think it's better to just redo those changes manually.

Since I already merged v1.0.1 in this PR
I think we don't have to do it manually again

The problem is this pr has a lot of diffs and a super unclear commit history. I intended the v1 and v1.1 branches to have separate histories. In v1 we just fix any bugs that might appear, then we do active development on v1.1 (main). Can you break this pr into smaller pieces?

it is okay to keep v1 and v1.1 in different branches but we should include the changes in v1.1
yeah I think when v1.1-graffiti and v1.0.1 are merged it will be more clear


Expires notify log sooner when possible

It seems useless to keep the notifications in the nflog for longer than
twice the repeat interval. This should help reduce memory usage of
clustered alertmanagers.

[x] needs tests

Signed-off-by: Julien Pivotto<EMAIL_ADDRESS>

Attempt to fix #2961

@gotjosh We have ran this and noticed a 30% memory decrease with alertmanager with low repeat interval. Any chances to get this merged?

This would be change of behaviour, let's merge this while we think on the further change


MODE sends to OSWRCH, OSBYTE 0 returns L=ZX Spectrum, INKEY(neg) returns, INKEY-256 returns machine

MODE sends to OSWRCH, OSBYTE 0 returns L=ZX Spectrum, INKEY(neg) returns, INKEY-256 returns machine. (Carry correct this time).

Hi, thanks for the pull request (and your interest in this project). I'd already started implementing OSCALL in order to get a subset of the page &FF calls working. Unfortunately the changes you've suggested won't merge easily with mine. The project's not very geared up for collaboration at the moment; it's going to be all over the place for at least the next couple of months whilst I juggle stuff around to fit into 2 ROM banks. I'll be releasing the new code over the weekend.


Add srv record-based DNS discovery.

We use the same keys used by
confd (https://github.com/kelseyhightower/confd) to allow service
discovery via DNS.
@jplana @fasaxc I think this is very useful for whoever uses confd as well, and in general. It introduces a dependency on dnspython, but it's well packaged in all distros. What do you think?

@lavagetto Nice! But we need to add it to the buildout the get travis working with it.

right, I'll do it.
On Sat, Jun 20, 2015 at 2:13 PM, Jose Plana<EMAIL_ADDRESS>wrote:

@lavagetto https://github.com/lavagetto Nice! But we need to add it to
the buildout the get travis working with it.
—
Reply to this email directly or view it on GitHub
https://github.com/jplana/python-etcd/pull/112#issuecomment-113755523.

For some reason the python3 travis build fails, even if I inject the correct dependency on package dnspython3 instead than dnspython.
@jplana any idea about how to fix that?
Apart from it this works well, and I'd really like to push it through.

@lavagetto I fixed the issue at bcb706f0aed53dcc3a37a04986073805433d38a1, now the build complains about python 3.5, I guess.

@jplana yes, thanks. In fact python-etcd was mostly unusable on python 3.4 too - I'll fix this and reorg the mess that this PR has become.

Sounds like a good feature to me.

Closed as I merged an enhanced version of this mess.


Optimize instruction dispatch

Currently, the VM uses a simple dispatch loop, which boils down to:
match next_opcode() {
  op::LoadReg => vm.op_load_reg(decode_args::<LoadReg>()),
  op::StoreReg => vm.op_store_reg(decode_args::<StoreReg>()),
  // ... etc.
}

It could be replaced by a less portable direct-threaded dispatch written in architecture-specific assembly for a few platforms (most likely only x86_64 and arm64), similar to this one (note that this code is heavily outdated, as it used the super unstable LLVM assembly macro, and asm has since been stabilised). The concept boils down to:
// create a jump table where `jump_table[opcode]` is the label address of the dispatch handler for that opcode
let jump_table = [label_addr!("dispatch_load_reg"), label_addr!("dispatch_store_reg"), ...];

// setup `pc` and `op` registers, jump to the first instruction
trampoline!(vm, pc, op, jump_table);

// all opcodes would be defined similar to this:
dispatch_handler!(load_reg, (vm, pc, op, jump_table) {
  // call VM's opcode handler
  vm.op_load_reg(decode_args::<LoadReg>());
  // load + dispatch next instruction
  dispatch!(vm, pc, op, jump_table);
})

This is unfortunately not better than a switch in most cases https://github.com/jprochazk/vm-perf


feat: Supporting management policies beta feature

Description of your changes
This PR enables the Beta feature management policies, following the same approach as the AWS provider.
I have:

[x] Run make reviewable to ensure this PR is ready for review.

How has this code been tested
The tests were done manually, applying the following scenarios:

Applying Workspace without management policies (management policy feature disabled)
Applying Workspace management policy [Observe] only (management policy feature disabled)
Applying Workspace management policy [Observe] only (management policy feature enabled)

 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.

/test-examples="examples/workspace-inline-aws.yaml"

@ytsarev you are very welcome 🤝


Continuous integration and delivery on Azure Databricks using Azure DevOps - Error in line 62 of installWhlLibrary.py

Error in the conditional "if" of line 62, there is one more parenthesis
if (getLibStatus(shard, token, clusterid, dbfslib) is not None:
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 56b86f59-7a22-90c6-9aa6-652b85975612
Version Independent ID: b333ab7b-847b-7129-9b62-4b9b934747d7
Content: Continuous integration and delivery on Azure Databricks using Azure DevOps - Azure Databricks
Content Source: databricks/dev-tools/ci-cd/ci-cd-azure-devops.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

On the other hand, the pipeline for the library installation ends well but when I go to the Cluster the installation has an error and the status is FAILED.
java.lang.RuntimeException: ManagedLibraryInstallFailed: java.util.concurrent.ExecutionException: java.io.FileNotFoundException: dbfs:/dbfs/libs/funcadd-0.0.1-py3-none-any.whl for library:PythonWhlId(dbfs:/dbfs/libs/funcadd-0.0.1-py3-none-any.whl,,NONE),isSharedLibrary=false
Any clue as to what may be happening?

Thanks for the feedback! We have assigned the issue to the content author to further review this and update the document as appropriate.
@leifbro, @mssaperla - Could you please review this feedback and update the doc as needed. Thank you

Thanks for your dedication to our documentation. Unfortunately, we have been unable to review your issue and apologize for the delayed response. The requested updates have not yet been made. The timeline for resolution varies based on resourcing. We've created an internal work item (DOC-7026) to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary.
#please-close

#please-close


Buffering settings to reduce latency

There is a latency in the delivery of messages which seems to be from some buffering which flushes the messages only every few seconds. Is there a configuration where this latency can be reduced and the messages processed as soon as they come in?
Moquette MQTT version
1.12.1
JVM version (e.g. java -version)
8
OS version (e.g. uname -a)
Windows 10 / Ubuntu 16.04

Probably a duplicate of, or related to #515


Added gulp autoprefixer task

This closes #43

Thanks, this just works like charm! :boom:

Cool!!


[docs] Remove npm 2 recommendation

npm 3 is working fine especially if you use shrinkwrap at the end. we've been using it for a month+ and the dependency deduping works well.

Both the Travis and Circle CI tests use npm 3 so there's coverage for this as well. I'm going to ship this, ping me if it should be reverted.

@facebook-github-bot shipit


Better MDX support

We could allow users to provide pages as .mdx files. This would be handy for documentation websites.
We could also automatically add ids to headings. See:

https://github.com/mdx-js/mdx/issues/810
https://mdxjs.com/docs/extending-mdx/
https://github.com/rehypejs/rehype-slug

You can also add components into .mdx pages (using the standard import Component from 'component.jsx' syntax), so you could even build simple form flows in MDX

Markdown (and MDX) pages are now supported.


refCnt after retainedSlice and slice

Expected behavior
AbstractByteBuf has the following implementation

public ByteBuf retainedSlice() {
return this.slice().retain();
}

refCnt of parent ByteBuf and the sliced one should keep consistency with ByteBuf.slice().retain()
Actual behavior
They are inconsistent.
Steps to reproduce
See the re-preroducer code
Minimal yet complete reproducer code (or URL to code)
@Test
public void testRetainedSlice() {
    ByteBuf buf1 = PooledByteBufAllocator.DEFAULT.directBuffer();
    buf1.writeInt(1);

    ByteBuf slice1 = buf1.slice();
    slice1.retain();
    Assert.assertEquals(2, buf1.refCnt());
    Assert.assertEquals(2, slice1.refCnt());

    ByteBuf buf2 = PooledByteBufAllocator.DEFAULT.directBuffer();
    buf2.writeInt(1);

    ByteBuf slice2 = buf2.retainedSlice();
    Assert.assertEquals(2, buf2.refCnt());
    Assert.assertEquals(1, slice2.refCnt());
}

Netty version
     <dependency>
            <groupId>io.netty</groupId>
            <artifactId>netty-all</artifactId>
            <version>4.1.58.Final</version>
        </dependency>

JVM version (e.g. java -version)
openjdk version "1.8.0_272"
OpenJDK Runtime Environment (build 1.8.0_272-b10)
OpenJDK 64-Bit Server VM GraalVM CE 20.3.0 (build 25.272-b10-jvmci-20.3-b06, mixed mode)
OS version (e.g. uname -a)
Darwin ali-186590d602cd.local 20.2.0 Darwin Kernel Version 20.2.0: Wed Dec  2 20:39:59 PST 2020; root:xnu-7195.60.75~1/RELEASE_X86_64 x86_64

The javadocs do not say that they must have the same reference counts, so this behaviour is within spec. As long as you pair up retains and releases, they will behave the same.

The javadocs do not say that they must have the same reference counts, so this behaviour is within spec. As long as you pair up retains and releases, they will behave the same.

Duplicate of #10713

Duplicate of #10713


Certificate issued date is almost invisible...

...but only if i use direct link.
Bad: https://www.freecodecamp.org/certification/alexortizzz/javascript-algorithms-and-data-structures
Good: click certificate in portfolio (https://www.freecodecamp.org/alexortizzz)
Windows 10, Chrome 78 / Firefox 70

Thanks for the report!  However, there is already an issue, https://github.com/freeCodeCamp/freeCodeCamp/issues/37378, that's tracking this, so I'm closing this one as a duplicate.


Support Laravel 9

Laravel 9 RC1 coming next Tuesday, I would like to be able to integrate spatie/laravel-ray on Testbench 7 right away (we will also release RC alongside Laravel).

Thanks!


Tensorflow.LookupError : No gradient defined for operation 'Add_3/y' (op type: Cast)

After updating from, version 0.4 to 0.6, I have this error:
Tensorflow.LookupError : No gradient defined for operation 'Add_3/y' (op type: Cast)

fixed for v0.60.1. will release soon.


Recursively include submodules

In app/js/controllers/index.js, our code as below:
const controllers = bulk(__dirname, ['./**/!(*index|*.spec).js']);

Object.keys(controllers).forEach((key) => {
  let item = controllers[key];

  controllersModule.controller(item.name, item.fn);
});

If we have a file structure looks like below:
-- controllers
  -- example.js
  -- folder
    -- another.js

We got a controllers object after bulked:
{
  "example": {
    "fn": "ExampleCtrl()",
    "name": "ExampleCtrl"
  },
  "folder": {
    "another": {
      "fn": "AnotherCtrl()",
      "name": "AnotherCtrl"
    }
  }
}

Unfortunately, AnotherCtrl did not declare as a controller because it's lying under a folder. services/filters/directives have the same problem, so I create this PR to solve it.

This looks good, thanks for the PR!


chore(docker): docker-compose mongo service local dev

add example of making an api call to the server from the client

Note: don't use the fetch api but something like react-query in the future

add example of init script to seed mongodb with data
enable cors on server
add mongo-express to visually browse the database from a browser

Task linked: CU-k0uuva Dockerfiles and docker-compose

Task linked: CU-k0uuva Dockerfiles and docker-compose


[Feature] Embed rollout in an application

Is your feature request related to a problem? Please describe.
Support embedded rollout settings in an application. In this way, any changes to the
application will naturally roll out in a controlled manner instead of a sudden replace.
Describe the solution you'd like
IMO we can split the solution to 2 pr
1.refactor rollout Reconcile func to let it could be called by application. Guarantee  logic work well  and pass all tests
2.write application side logic and add tests.
Describe alternatives you've considered
If the solution of refactor rollout reconcile cannot work well. Consider create a AppRollout object in application control loop.

If the solution of refactor rollout reconcile cannot work well. Consider create a AppRollout object in application control loop.

There might be a few problems with this approach

appRollout has finalizer logics that won't apply when it's not the entire object
appRollout reconciler has defer functions that might not apply when it's not the entire object

Let me clarify the design:
apiVersion: core.oam.dev/v1beta1
kind: ScopeDefinition
metadata:
  name: rollout
spec:
  definitionRef:
    name: approllouts.core.oam.dev
    version: v1beta1

Then:
apiVersion: core.oam.dev/v1beta1
kind: Application
metadata:
  name: example-app
spec:
  components:
    - name: testsvc
      type: webservice
      properties:
        addRevisionLabel: true
        image: crccheck/hello-world
        port: 8000
  scopes:
    - type: rollout
      properties:
        sourceAppRevisionName: test-rolling-v1
        targetAppRevisionName: test-rolling-v2
        componentList:
          - metrics-provider
        rolloutPlan:
          targetSize: 5
          rolloutBatches:
            - replicas: 1
            - replicas: 3

Then we will create the rollout object, the name of the rollout is automatically generated:
apiVersion: core.oam.dev/v1beta1
kind: AppRollout
metadata:
  name: example-app-rollout-1
spec:
    sourceAppRevisionName: test-rolling-v1
    targetAppRevisionName: test-rolling-v2
    componentList:
      - metrics-provider
    rolloutPlan:
      targetSize: 5
      rolloutBatches:
        - replicas: 1
        - replicas: 3

@wonderflow The whole point of having component + trait model is we should be able to attach capabilities to a component and then get a self-contained app deployment entity, CUE and Helm are the glue that make this happen, Application is the UI to assemble these capabilities and declare user parameters.
If there's an app mgmt capability that can't fit in this model, we need to revisit why. Note that this dosen't mean we will change how Rollout works. On the contrary,  we may check the implementation of abstraction layer (app controller) itself.
As a user, I will be happy to see if I have a Helm chart, and your system can attach a rollout capability to it w/o breaking my chart, and it's even better if I can bring/define my own capability.
We can leave Rollout as is and make Flagger and Istio trait happen. Rollout can be left as an independent feature such as "manual upgrade app in batches".


Do not use line defaults in legend

Resolves #7648

Not sure, I changed from the line defaults. The default line borderWidth is 3, but that seemed too large for the legend.

Ok. Makes sense that it should have its own defaults, so let's merge as is


Do this project support nn.ConvTranspose2d layer?

Hi, @starimeL .
Do this project support nn.ConvTranspose2d layer?

Yes, the converter support ConvTranspose layer. Just make sure to use the pytorch 0.2.0 to do the conversion.


errorsbp: Add BatchSize

This is helpful in unit tests to verify that a function returned the
exact number of errors in a batch as expected.
Also add Batch.Len() helper function.

cc @JessicaGreben


Detect AWS region from instance metadata

When starting discovery, receive the following error:
operation error Kafka: ListClusters, failed to resolve service endpoint, an AWS region is required, but was not found

This can be resolved by setting the AWS_REGION environmental variable but this can also be determined from the instance metadata so it would not be necessary to configure anything (as long as the MSK clusters in the same region).

Hey Mike,
Thanks for this! I'm guessing this was running the binary directly on an EC2 instance? It's not something that was caught since we generally only use it in the Docker image on an EKS cluster which tends to set the required environment variables.
It looks like an easy fix so let me just test it some more and I'll push the new version.

I am running it in a pod within our Kops built Kubernetes cluster.
It was just the sidecar container of the Prometheus Helm chart. Nothing special at all.

Got it, thanks!
When you get a chance, can you try the Docker image: statsbomb/prometheus-msk-discovery:ec2region and let me know if it works as expected.

I just encountered the same issue, and statsbomb/prometheus-msk-discovery:ec2region solved it for me.
As a suggestion - maybe add an option to explicitly set it via CLI (although I assume the standard AWS env var will also work?).
Another one, more important, is to allow passing a list of regions, to scan them all.

@imriz Thanks for confirming! I'll create a proper release with the fix today.
As for the list of regions I've created a dedicated feature request for it (#10) but I suspect it'd require a bit of rewrite to implement so I can't promise it'll be done any time soon.
Allowing specifying a single region as a parameter shouldn't be too difficult (#11) but in the meantime I'd imagine you could just set the AWS_REGION environment variable to the desired region and things should work.

@mikelorant @imriz The image statsbomb/prometheus-msk-discovery:0.3.0 now contains the EC2 IMDS fallback as well as the ability to specify a region with the -region flag.
Let me know if you have any problems!


redisCommand not blocking when expected

I have a thread (thread owns its own redisContext*, can't use event libs because reasons) and that thread is in a while loop with a redisCommand calling BLPOP.
 It pops one value then context->errstr complains about a "bad file descriptor".
So I'm guessing somehow the context has lost the fd at some point while blocking but I can't figure out if this is a bug with hiredis or something I'm missing. I've looked at pretty much every example available. Does the context need a keepalive mechanism or something along those lines? I had a quick look at #168 but my connected_clients doesn't appear to be going down so it seems my threaded context is still connected...
Here's the wait loop (please excuse the lack of a null check for reply! it's in my working dir) https://github.com/Southclaws/samp-redis/blob/master/src/impl.cpp#L432-L451

Did you try with enabling keepalive? It might very well that the server closes the connection.
You should also check the server's log and the server's tcp-keepalive setting.

It's the default tcp-keepalive 300 I should add that this problem I'm having happens within seconds of connecting (during unit tests). The redisCommand call blocks at first, pops the first element and then on the next iteration, returns a NULL reply.

That sounds weird indeed. I don't have time this week to look into it, but I put it on my list for the following week

Alright, thanks! I'm going to do some investigation too - I'm going to implement an auto-reconnect anyway so with some more logging and pushing it onto my test server I should have some more information on why this is happening. Strangely I can't reproduce it consistently either, which is annoying...

Hi,
I haven't done any real C++ work in years, but this is almost certainly a memory corruption bug due to threading.  I wrote a very simple C program to run BLPOP in a worker thread and hiredis is just fine with it:
https://gist.github.com/michael-grunder/edb0a438a6e923c3cf375038be73c7c9
If you place a continue statement above this line here, does the bug go away?:
https://github.com/Southclaws/samp-redis/blob/master/src/impl.cpp#L460
The fact that it works sometimes, and other times fails makes me almost certain that this is a threading issue.
Cheers!
Mike

While I am always the first one pointing out issues in multi-threaded programs, I don't see a problem with the current usage.
The context is created and used in a single function and thus not across threads. processMessages iterates over the returned elements, processMessage copies out the string.
None of the hiredis values is moved across thread boundaries as far as I can see.
It might still be possible for further memory corruption, but a closed socket would probably cause similar problems.

Just in case you were still thinking about this issue, I've solved it now. You'll be pleased to know that Hiredis is fine! It was some memory corruption on the host app caused by some dodgy SQLite library (the main reason for my implementing Hiredis was to get the SQL code out of the host and into a Go app to do it concurrently anyway).
Thanks for the replies on the topic anyway, apologies for wasting an issue :)

:) Thanks for reporting back.


Do not unstake, withdrawal due to number conversion

Description the bug
Do not unstake, withdrawal due to number conversion

Do not reproduce this issue on the new UI version


Feat:fixed integration page

Description
This PR fixes #1181
Notes for Reviewers
Fixed the invisible text and extra space in the header.
You may wonder why there is so much space in between, The purpose is to manage the overlap of 3-D grids with the main buttons as well as the text bar.
https://github.com/meshery/meshery.io/assets/59855919/d25a49ec-cc5d-46b9-85de-ed49ed55b4de
Signed commits

[x] Yes, I signed my commits.

Thanks for this, please make sure the changes are consistent for all screen sizes.

yes thanks for the review , currently working for the same

@thisiskaransgit actually im confused , my current layout is responsive as per the size standards.
https://github.com/meshery/meshery.io/assets/59855919/fa274bf3-d2cf-477d-9d67-b5242ca9cab1

closing this as it has been completed by #1209


Remove action item codes for Assessments v1

Related Issues

Links https://transcend.height.app/T-34487

Security Implications
[none]
System Availability
[none]

@iamtheluckyest it dismisses stale review whenever new commits are pushed!

@anotherminh oh, really? I had no idea. Is that specific to this repo?


Update OnboardingRequest contract

Rename Country to CountryRegion
Rename State to StateProvince

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

I was having trouble getting the auto-generation tool set up and running on my machine, so I ended up editing it manually since it was such a small change. Is that OK? I can try to redo it through the tool if necessary.
Yes, these changes are for sprint 68.

We should avoid manual edits, but this should be ok so long as we've confirmed that the changes are included in the new swagger file.

@davidkwoods we also should note this could be breaking for existing apps

@brendankowitz @davidkwoods  Yup, these changes are in Swagger, and @jhutchings1 and @rouellam are good with communicating the breaking changes.


Package setup

Hello there,
I'm pretty new in react native programming and I just can't get the iOS setup for this package right. Maybe these are quite dumb questions, but I hope someone can help me.
I found the ReactNativeCameraKit.xcodeproj file, but where do I have to drag it? Open projectname.xcodeproject and drag into the project?
And what does this mean 'Add libReactNativeCameraKit.a to all your target Linked Frameworks and Libraries (prone to be forgotten)'? What are these linked Frameworks and Libraries and where do I find them?
Thanks alot

Exactly same question here

Finally I got it right. To set this module up, just follow the description in the React Native Docs for Linking Libraries ( You can find it here )

It's better to put these instructions or the link into the doc, sincerely.


Export-DbaInstance exports password in clean text

Environmental information
#### PowerShell version:

Name                           Value
----                           -----
PSVersion                      5.1.17134.765
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17134.765
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

#### dbatools Module version:

Name    : dbatools
Path    : C:\Program Files\WindowsPowerShell\Modules\dbatools\1.0.0\dbatools.psd1
Version : 1.0.0

Name    : dbatools
Path    : C:\Program Files\WindowsPowerShell\Modules\dbatools\0.9.803\dbatools.psd1
Version : 0.9.803

Name    : dbatools
Path    : C:\Program Files\WindowsPowerShell\Modules\dbatools\0.9.512\dbatools.psd1
Version : 0.9.512

SQL Server:

Microsoft SQL Server 2017 (RTM) - 14.0.1000.169 (X64)
        Aug 22 2017 17:04:49
        Copyright (C) 2017 Microsoft Corporation
        Developer Edition (64-bit) on Windows Server 2016 Standard Evaluation 10.0 <X64> (Build 14393: )

Report
Running Export-DBAInstance is exporting the password of the linked server credentials in clean text.
Host used

[x ] powershell.exe
[ ] ISE
[ ] VS Code
[ ] Other (please specify)

Errors Received
There is no error
Steps to Reproduce
Run: Export-DbaInstance
Expected Behavior
Linked Server credentials and SQL login credentials are hashed or at least not in clean text.
Actual Behavior
SQL logins password are hashed but linked server password is exported in clean text.

I see two options here

introduce a parameter -ExcludePasswords to Export-DbaInstance to parameterize either you want to have passwords exported in clean text or not.
Just add -ExcludePassword when calling Export-DbaLinkedServer from Export-DbaInstance function

If you don't export the password for a given object then creation of that object cannot be accomplished. What purpose is there in not including the password?

Re-reading, the note on hashed passwords will only work for logins. There is no mechanism in SQL Server to create a hash for the linked server object and have that hash converted in order to create the linked server.

My purpose of that function is to aumatcally export an instance and put in source control. And I do not won't to have passwords in my repository. I can work around that by doing a search and replace after the export. But in my opinion passwords should not be exposed as a default behaviour.

hey @codeunitone - claudio told me about your idea and i think it's fab. It would be:

Export-DbaLogin (-ExcludePasswordHash)
Export-DbaLinkedServer (-ExcludePassword)
Export-DbaCredential (-ExcludePassword)
Export-DbaInstance - (-ExcludePassword) (covers both)

I understand your position about the default, and it's true regarding Export-DbaLinkedServer and Credential, but those are breaking changes, so we'll add the exclude. Please also add some Examples as well 👍

@potatoqualitee why not just make it a configuration item instead of adding on a parameter/testing? Just say either configuration called IncludePasswordExports and we set it to true by default.

We can do that in addition to parameters 👍  I don't expect most ppl will use our config systems and would prefer to use them as a backup and not primary source.

Also looking at using Export-DbaInstance and throwing in source control. Added param -ExcludePassword to both Export-DbaLogin and Export-DbaInstance.
Realise now I didn't follow your naming... let me know if I should change it.
PR #5833 is open for it

@potatoqualitee, @wsmelton - can this be closed? ExcludePassword param is now available on both Export-DbaLogin and Export-DbaInstance

yes ty 🙇


Add external versioning for documents being stored in elasticsearch

We recently had the use case where we needed to provide an external version for documents being stored in documents. Currently I dont see the option to do this in benthos. I wanted to ask, if there are thoughts about it and if it would be useful to have. Thank you.

Hey @jann, my elasticsearch knowledge is a little lacking but it sounds like something that's easy to add.

@jann Could you elaborate your case a bit, please.
Is it a _version of a stored document in Elasticsearch itself you're after, or do you just need some  incrementing mechanism as your documents come through benthos?


not prettyprinting using file transport?

I was hoping to get the JSON written to the file to be pretty printed, but it doesn;t appear to be. Am I doing something wrong?
new winston.transports.File({
      filename: file,
      level: 'info',
      prettyPrint: true,
      // eol: 'rn', // for Windows, or `eol: ‘n’,` for *NIX OSs
      timestamp: true
    })

Hi @ScottChapman,
By default, on file transform the flag json is true. That means that JSON output is not prettyPrinted. Here in the docs you can see that prettyPrint is only for the meta part of the message to log. Since the transport is in json: true mode the meta object is merged with the rest, so it works as expected.
Hope that helps and feel free to re-open if I have misunderstood your question, thanks!


python310Packages.cvxpy: 1.3.0 -> 1.3.1

Changelog: https://github.com/cvxgrp/cvxpy/releases/tag/v1.3.1
Description of changes
ZHF: #230712

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

https://github.com/cvxpy/cvxpy/releases/tag/v1.3.1 is the right changelog

I don't know why do we refer to a fork

Result of nixpkgs-review pr 231842 run on x86_64-linux 1

36 packages failed to build:

python310Packages.bambi
python310Packages.bambi.dist
python310Packages.blackjax
python310Packages.blackjax.dist
python310Packages.jaxopt
python310Packages.jaxopt.dist
python310Packages.qiskit
python310Packages.qiskit-aer
python310Packages.qiskit-aer.dist
python310Packages.qiskit-finance
python310Packages.qiskit-finance.dist
python310Packages.qiskit-ibmq-provider
python310Packages.qiskit-ibmq-provider.dist
python310Packages.qiskit-ignis
python310Packages.qiskit-ignis.dist
python310Packages.qiskit-nature
python310Packages.qiskit-nature.dist
python310Packages.qiskit-optimization
python310Packages.qiskit-optimization.dist
python310Packages.qiskit.dist
python311Packages.blackjax
python311Packages.blackjax.dist
python311Packages.jaxopt
python311Packages.jaxopt.dist
python311Packages.qiskit-aer
python311Packages.qiskit-aer.dist
python311Packages.qiskit-finance
python311Packages.qiskit-finance.dist
python311Packages.qiskit-ibmq-provider
python311Packages.qiskit-ibmq-provider.dist
python311Packages.qiskit-ignis
python311Packages.qiskit-ignis.dist
python311Packages.qiskit-nature
python311Packages.qiskit-nature.dist
python311Packages.qiskit-optimization
python311Packages.qiskit-optimization.dist

16 packages built:

python310Packages.cvxpy
python310Packages.cvxpy.dist
python310Packages.ecos
python310Packages.ecos.dist
python310Packages.qutip
python310Packages.qutip.dist
python310Packages.scikit-survival
python310Packages.scikit-survival.dist
python311Packages.cvxpy
python311Packages.cvxpy.dist
python311Packages.ecos
python311Packages.ecos.dist
python311Packages.qutip
python311Packages.qutip.dist
python311Packages.scikit-survival
python311Packages.scikit-survival.dist

qiskit is already very much broken anyway due to NumPy.

blackjax, jaxopt and bambi are broken as well.


Fixes #389 Window layouting breaks when resizing.

Fixed #389 horizontal resizing issue. Vertical resizing was fine. Posting a complete code to verify these two situations.
Application.Init ();

var top = Application.Top;
var files = new Window ("Files") {
	X = 0,
	Y = 0,
	Width = Dim.Percent (70),
	Height = Dim.Percent (80)
};
top.Add (files);
var sourcesWindow = new Window ("Sources") {
	X = Pos.Right (files),
	Y = 0,
	Width = Dim.Fill (),
	Height = Dim.Percent (90)
};
top.Add (sourcesWindow);
var filesDetails = new Window ("Files Details") {
	X = 0,
	Y = Pos.Bottom (files),
	Width = Dim.Percent (70),
	Height = Dim.Fill ()
};
top.Add (filesDetails);
var sourcesWindowDetails = new Window ("Sources Details") {
	X = Pos.Right (files),
	Y = Pos.Bottom (sourcesWindow),
	Width = Dim.Fill (),
	Height = Dim.Fill ()
};
top.Add (sourcesWindowDetails);

Application.Run ();


Portal experience does not match current page step by step instructions.

The Portal experience does not match the current page step by step instructions.
This page states that after filling in the project details you should click "Review + Create" and create the private end link separately.
(section https://docs.microsoft.com/en-us/azure/azure-arc/servers/private-link-security#create-a-private-link-scope)
The Portal currently has the end link as part of the Azure Arc Private Link Scope creation. Could you adjust the new screenshots and integrated. steps?
Cheers!

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

ID: 2fa8defc-fa38-dfc2-a0bc-18a2051eb3f6
Version Independent ID: 933382fc-a6c7-d0e3-da99-0759750cef64
Content: Use Azure Private Link to securely connect servers to Azure Arc - Azure Arc
Content Source: articles/azure-arc/servers/private-link-security.md
Service: azure-arc
Sub-service: azure-arc-servers
GitHub Login: @johnmarco
Microsoft Alias: johnmarc

@pierreroman Thanks for the feedback.
Assigning to @johnmarco for visibility, review and document enhancement consideration as appropriate.

@pierreroman, investigating necessary updates.

@pierreroman thank you for bringing this to our attention. I've made some changes to the procedure so that it reflects the actual onscreen experience. The new version should be live soon. I will now close this issue.
#please-close


Move configuration out of extremal-python-dependencies

This modifies the extremal-python-dependencies script so that it is configured on the command line.  This is one step toward making it a standard script.  Configuration is now provided by command line flags in the CI workflows.

Waiting on #230

This modifies the extremal-python-dependencies script so that it is configured on the command line. This is one step toward making it a standard script. Configuration is now provided by command line flags in the CI workflows.

Nice, is the idea that we include this in tools as something we can run outside the context of CI?

Nice, is the idea that we include this in tools as something we can run outside the context of CI?

That is a nice benefit of this, but actually, my immediate goal is to make this script more generic, so that we aren't configuring it within itself.  This way, we can standardize this script among all the repositories that use it, or, better yet, spin it out into its own repository with tests and brief documentation.  From there, we could pip install it in the workflows that need it and maintain it only in one place.
Currently, forks of this code exist at

https://github.com/qiskit-community/prototype-zne/blob/main/tools/extremal_dependency_versions.py
https://github.com/Qiskit-Extensions/staged-primitives/blob/main/tools/extremal_dependency_versions.py
and a few other places internally, not to mention packages that did it the old, setup.py way (quantum-prototype-template, qrao, and quantum kernel training)


[RFC] Talk and an Organization

Trying to wrap my head around what it'd take to implement Talk resources with an Organization.
It appears Talk resources have a section: project-#{project.id}.

Talk-Api/app/models/concerns/sectioned.rb

I think when creating something, like a new Board, which requires section to be defined, it checks Panoptes that the section (let's say project-1234) has a valid project ID, though I'm not entirely sure how this is happening.
So Talk would have to be refactored to accept 'project-1234' OR 'organization-5678'.

The section component would be the something like the project specific one (note there is a global zooniverse one too). E.g. section =  "organization-#{org.id}" and if you keep that consistent then i'm pretty sure everything will work out of the box API side. You'll have to wire up the views to use those section contexts though.

closing for now - feel free to reopen if needed.


HDDS-11132. Revert client version bump done as part of HDDS-10983

Change-Id: Ib8b9fb743492eacde1f11436eb3116e6a221ac9b
What changes were proposed in this pull request?
Currently backward client version compatability of Ozone RequestFeatureValidator in OM is broken, after a client version bump done as part of HDDS-10983. https://github.com/apache/ozone/pull/6932 fixes the issue on the RequestFeatureValidator side.
This patch is a stop gap arrangement done in the interim which reverts the client version bump done in HDDS-10983.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-11132
How was this patch tested?
Existing IT & unit tests

Thanks @swamirishi for the patch.  Verified that FSO bucket can be created and used in new cluster with clients 1.3.0 and 1.4.0.

Thanks @swamirishi for the patch, @sodonnel for the review.


Adding Additional Constraint To Nuspec. https://github.com/IdentitySe…

This pull request adds an additional nuget package constraint to the IdentityServer3.AccessTokenValidation nuspec.
Highlighted in this issue.
https://github.com/IdentityServer/IdentityServer3.AccessTokenValidation/issues/134
Additional Points:
This the simplest possible change, the only thing is, am i being too strict on System.IdentityModel.Tokens.Jwt version="<IP_ADDRESS>221351"
In VS nuget is prompting me that its safe to update to version 5.1.2 but i'm not really sure that's a good idea.
For now this certainly change will at least get the dependencies inline.

Hi @mickdelaney, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

thanks - but please do that against the dev branch!

sorry :-)


Notepad++ does not open when this dll is added to plugin folder

Here is the error message:

Here is my NPP version:

Sourceforge has only 32-bit dll. That's why I got the error. Now I used the 64-bit version and it is working fine.


Scroll with touchpad is Excessively responsive.

OS:
Windows 10 Single Language
pc: Lenovo Ideapad 300
Issue Descriptions:
Double-finger touchpad scroll is too fast; changes with touchpad software are not effective; regular mouse scrollwheel works fine.
Steps to Reproduce:
Use two fingers to scroll the UI. UI scrolls uncontrollably fast.
DISCLAIMER: new to GitHub, please be kind.

This sounds like a hardware thing, if your scroll wheel works fine but your trackpad scrolls to fast.  Just adjust the scroll speed on your track pad?
Regardless if it works for one and not the other no matter what i do it will never be the same for both :+1:

Thanks for the feedback. As an additional info, the issue happens with spotify too!

UPDATE
Found some fix in the Spotify forum. Documenting it here for people who may have the same problem:
Open regedit.exe using run
Go to HKEY_CURRENT_USER -> SOFTWARE -> Elantech -> Smartpad
Change ScrollControl_Mode from 0 to 1
Open the elan software and click apply just to make sure the settings get applied
Source:
https://www.reddit.com/r/techsupport/comments/3lhmhq/win10_elan_touchpad_scrolling_issues/
Source:
https://community.spotify.com/t5/Ongoing-Issues/Touchpad-scrolling-too-fast/idi-p/1301995#comment-on-this

@lorenzofollador Thank you so much!!!! Fixed for me for lenovo ideapad 330.


[BUG] - When Copying an existing tunnel, Amnetzia properties are not copied.

Describe the bug
Amnezia Properties are not copied when using the copy button to duplicate a tunnel.
Smartphone (please complete the following information):

Device: Samsung Galaxy S10e
Android Version: Android 12
App Version 3.5.2
Backend: Userspace

To Reproduce

Configure a tunnel with custom "Amnezia Properties"
From the tunnel screen, long press the tunnel and click the Copy button.
Edit the newly created tunnel. Wait for the interface properties to populate.
Click "Show Amnezia Properties".
Notice all of the Amnezia properites are all blank (set to default) while the standard Wireguard options were all copied to the new tunnel.

Expected behavior
All everything that was configured in the original tunnel should be copied to the new tunnel.

This was fixed in 3.5.4, along with automatically showing the Amnezia properties if they exist.

Confirmed fixed.


Trainning Stage

[x] Update Config.YAML
[x] research or analysis
[x] Update Entity
[x] Update Configuration Manager in src Config
[x] Update Component
[x] Update the Pipeline

Created and pushed


Un-Encrypted vxlan tunnel between clusters

What would you like to be added:
Un-Encrypted vxlan tunnel between clusters
Why is this needed:
All current cable drivers involve encrypting content, which is great for privacy but involves some overhead. On private connections, it would be useful to enable unencrypted connections, using VxLAN.

bump


Misnumbered Sections In Contributing.md

Currently the steps are listed in the following order:

Clone the repository:
Install dependencies:
Firebase Configuration Setup
Steps to Set Firebase Environment Variables
Run the project:
Access the project locally at http://localhost:3000.

Suggest changing the first listed '5' to be '4'.

Kindly make a PR for the same


Request: add askdev.ru to the filter

Please block askdev.ru
Evidence: https://askdev.ru/q/raznica-mezhdu-zram-i-zswap-zakryto-138035/
Original: https://stackoverflow.com/questions/18437205/difference-between-zram-and-zswap

Thanks a lot!


utils/github: use tap.full_name

[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.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

This fixes issue search in the Linux core tap, which no longer uses homebrew-.
cc: @imichka @sjackman

sorry for the noise. that's the second time I've edited a file on my fork through the web interface and then accidentally targeted the pull request at my fork instead of upstream
smh


hssi 10g: disable options related to eth ifc

Remove the notion of specifying or querying the ethernet interface
from the 10G flow. Remove the associated calls to enable/disable
loopback for the interface as well as the call to display eth
statistics.
Signed-off-by: Tim Whisonant<EMAIL_ADDRESS>

Coverage increased (+0.01%) to 65.96% when pulling e547fd83c2e2efb612eeb9d47ead8bf152bc2e2e on tswhison/hssi into 1d68a32a7334ae04743762ecefed84e0cd06387d on master.


Add an example for docker containers

It's not clear what version selectors will work with docker containers in Dockerfiles. Therefore this hard won example demonstrates how to ignore a version range in a Dockerfile.

Why:
Closes ISSUE #23340

What's being changed (if available, include any code snippets, screenshots, or gifs):

Adding the following example to the ignore example:

Check off the following:

[x] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

@dannystaple Thank you for opening a PR and linking it to your issue! ✨
I'll get this triaged for review! :zap:

hi @dannystaple, thank you for opening this PR! We're reviewing internally and I hope to be able to update you on this soon 💛

hi @dannystaple,
We agree that adding some clarity on this for docker would make sense! Since we'll need some input from engineering, I've opened an issue internally, so I'll close this out one.
Thank you for raising this! 💛


Add folder-git icon

What about something like this ?

@jguddas: we should use the existing folder shape, so maybe something like this:

@jguddas: we should use the existing folder shape, so maybe something like this:

Oh, that looks nice, mine looked a bit like a telephone :smile:

What about something like this?

I did already have this, which looks nice, but unfortunately is off-center relative to the other folder icons…

What do you mean with off center, I feel like it fit's in quite well.

What do you mean with off center, I feel like it fit's in quite well.

I meant the first one in my post…

What do we think of these? @karsa-mistmere @ericfennis @jguddas
I’m looking for some kind of folder-root (git repo or otherwise) icon, for the file explorer/tree in my VS Code extension…