Coderay css error

My asciidocs use coderay as source code highlighter. It has its own css. Untill recently this did not affect the preview, but now the preview fails showing error message:

Any way to tell the preview where to find the css or bypass this issue? We would be happy if the rest of the text would preview.

Hi, thanks for reporting the problem, can you please provide a zip file with a sample .adoc and the css structure ?
Thanks

Attached is a .zip with an example. In the styles catalog you will find the coderay css. In the bin catalog you can see an example of the finished build using asciidoctor and coderay gems.
As you can see I use a setup file in the beginning. This adoc I reuse across all documents and it is always included in the beginning of my documents. As I mentioned earlyer, the main issue is that nothing previews. If you can make the syntax highlighter work in preview - great, but if the source blocks just renders genericly thats no problem.
adoc-previewWithCoderayProblem.zip

Simply removing this line
:source-highlighter: coderay
from the setup.adoc resolves the problem for preview but breakes my butiful codeblocks in the end result.
Perhaps it is possible to just ignore this attribute before rendering?

@SandMann1, in a recent version of the extension the default asciidoc renger engine was changed from Asciidoctor (Ruby) to Asciidoctor(.JS), there are multiple source highlighters, but they only work on specific engines, you can find the list at:
https://asciidoctor.org/docs/user-manual/#enabling-source-highlighting
You have the following options:

Change setup.adoc, to use "highlightjs" instead of "coderay"
Change the vscode asciidoc settings to use asciidoctor (ruby):

    "AsciiDoc.asciidoctor_command": "asciidoctor -r asciidoctor-diagram -o-",
    "AsciiDoc.use_asciidoctor_js": false,

@SandMann1  not sure if you need the diagram extension. You can remove the-r asciidoctor-diagram.

Thank you for excellent and quick response. - SandMan


fix: Bridge access for Rust opaques

Changes
Fix code generated for Rust opaques when --no-use-bridge-in-method is active (referencing a non-existent bridge)
Checklist

[ ] An issue to be fixed by this PR is listed above.
[ ] New tests are added to ensure new features are working. End-to-end tests are usually in the ./frb_example/pure_dart example, more specifically, rust/src/api.rs and dart/lib/main.dart.
[x] The code generator is run and the code is formatted (via just precommit).
[ ] If this PR adds/changes features, documentations (in the ./book folder) are updated.
[ ] CI is passing.

Remark for PR creator

Justfile is a task runner for the command line interface that allows you to run shell commands from a file named justfile in your project directory. You can use Justfile after installing it. Note that commands written in justfile of this repository are expected to be run in bash, not cmd or powershell. Running just ... commands in cmd or powershell will produce errors as the syntax is not compatible. On Windows, you can use git bash if you have Git installed.
If fzyzcjy does not reply for a few days, maybe he just did not see it, so please ping him.

Good job! Quite busy now so may check as soon as possible :)

(will merge after CI goes green)


data-theorem-mobile-secure 1.2.0

This PR updates the Data Theorem Mobile Secure step to version 1.2.0, which adds an optional sourcemap parameter which can be used to submit mapping files for android builds.
What to do if the build fails?
At the moment contributors do not have access to the CI workflow triggered by StepLib PRs. In case of a failed build, we ask for your patience. Maintainers of Bitrise Steplib will sort it out for you or inform you if any further action is needed.
New Pull Request Checklist
Please mark the points which you did / accept.

[ ] I will not move an already shared step version's tag to another commit
[ ] I read the Step Development Guideline
[ ] I have a test for my Step, which can be run with bitrise run test (in the step's repository)
[ ] I did run bitrise run audit-this-step (in the step's repository - note, if you don't have this workflow in your bitrise.yml, you can copy it from the step template.)
[ ] I read and accept the Abandoned Step policy

It appears that my username has unexpecetdly made it into the git repo URL. I will close this and submit a new PR after fixing that.


fix: take out parallel running in unit tests to avoid timing issue

Signed-off-by: Jim Wang<EMAIL_ADDRESS>

If your build fails  due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[x] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I am not introducing a new dependency (add notes below if you are)
[x] I have added unit tests for the new feature or bug fix (if not, why?)
[x] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[ ] I have opened a PR for the related docs change (if not, why?)

Testing Instructions

New Dependency Instructions (If applicable)

recheck

recheck

recheck

for i in {1..5}; do recheck; done ; :->

Codecov Report

Merging #4349 (f556cac) into main (15a983a) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main    #4349   +/-   ##
=======================================
  Coverage   43.54%   43.54%
=======================================
  Files         116      116
  Lines       10732    10732
=======================================
  Hits         4673     4673
  Misses       5640     5640
  Partials      419      419

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Unclear how to add logo

In the ccs, there are mentions of the email-masthead-logo, but no directions on how to add the logo to the masthead. Is that supported with these templates? I don't see it in any of the demos/screenshots that you've published.
Great templates, can't wait to play with them more!

Hey @jrgifford, this is possible! Here's an example to get you started:

To support this further I made a small change to .email-masthead_logo, so you'll want to pull the latest. https://github.com/wildbit/postmark-templates/commit/3507d12df4ba702c6f887b78543bf2a71a957696
Let me know if this helps and I'll be sure to document this in the README.

Looks good! Thanks!

The style change never seemed to make it through to your live version on Postmark. Is that a bug? :) I just copied it through but thought you'd want to know :)

Thanks for the heads up @brendon. Looks like this was removed by accident a couple years ago when we switched over to MailMason for our builds.

Roger :) I think also you could add in a commented out image tag for the masthead_logo just to give people a bit of a hint as to what to do :) Not sure if the actual border, width, and height attributes on the img tag are needed though as in your original example.

Nodemailer doesn't support css in the header . so can i get inline version of the templates?


Add trust check to persistence performance test

Description
Our script to check that skops persistence is not too slow compared to pickle used trusted=True so far. However, this is not the recommended way of using skops -- ideally the check for trusted types should be performed, which theoretically could slow down persistence. This PR adds the check for trusted types to the script.
Results
Testing locally, there is only a small difference. For instance, for the slowest couple of tests, the added time was only 0.05 sec or less. On average across all estimators, the difference was 0.004 sec. or 30% slower. This relatively small increase means that the check for trusted types is fast compared to constructing the objects.

@skops-dev/maintainers ready for review


Dummy API endpoint

We need a dummy API that takes the request from the SDKs in order to test them and mock some responses.
Why

The actual sandbox should be used just for learning purposes and not for testing the code.
Several services providers (no mentions) have a client that you can run locally.
This can be helpful also for a CI when you run your tests.

How

using all the structs from the go model of the mangopay SDK with a git module.
genrerating some fake data with a local fuzzer and sotring the all in maps.
we can add features with params like network latencies, no responses of services and so on.

Hi @ritoon,
I understand your feedback, however, I would recommend using the sandbox account to do any testing, our sandbox is always identical to the prod environment and great place to develop SDK functionality.
We have certain test envs, but these are protected for security reasons.
Regards,
Max


Sync eng/common directory with azure-sdk-tools for PR 2219

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/2219  See eng/common workflow

Failure not related to this PR. merging.

/check-enforcer override


Ionimg can't display normally with local pictures

Ionimg can't display normally with local pictures
Ionic version:
    "@ionic/pwa-elements": "^1.5.2",
    "@ionic/react": "^5.0.7",
    "@ionic/react-hooks": "0.0.6",
    "@ionic/react-router": "^5.0.7",
    "@testing-library/jest-dom": "^4.2.4",

Current behavior:
            <IonImg
              onIonError={(event) => ionError(event)}
              src={'./logo.png'}
            />

The first thing that can't be displayed normally is the local use, and what can be displayed normally is the network picture.

Expected behavior:

Expected normal display.
Ionic info:
Ionic:

   Ionic CLI       : 6.6.0 (/Users/jkwu/.nvm/versions/node/v10.20.0/lib/node_modules/@ionic/cli)
   Ionic Framework : @ionic/react 5.0.7

Capacitor:

   Capacitor CLI   : 2.0.1
   @capacitor/core : 2.0.1

insert the output from ionic info here

![image](https://user-images.githubusercontent.com/20339760/79707541-66b2a600-82ef-11ea-9359-e412d080bc48.png)

I solved this problem by adding require ().
so:
     <IonImg
              onIonError={(event) => ionError(event)}
              src={require('./logo.png')}
            />


Unidentified trackers from Barnes & Noble

I sent some emails from Barnes & Noble with an unidentified tracker, using 0.7.1.
B&N emails before July 23 are still identified as Validity + 2 more.

Good data points, thanks! Captured these ones. Looks like there's 4 trackers in each


Cannot install from a local wheel

I have a project where I want to install a package (cassiopeia) that depends on pycurl. I'm on Windows, and pycurl currently does not provide a binary wheel for Python 3.6, nor does it build without a prebuilt libcurl being available. I can however get a wheel from Christoph Gohlke's website.
I'd like to hold the pycurl wheel in my project directory, under wheels/pycurl*.whl. I could then supply --find-links to pip and install pycurl from there.
Specifying an environment variable PIP_FIND_LINKS sort of works, but I can't find any way to record the fact that I want to include the wheels directory in the search path permanently, so that I don't have to (remember to) set an environment variable every time I rebuild the environmnent.
I found https://github.com/pypa/pipfile which gives examples of more complex ways of specifying things in a pipfile, but I can't make this work.
Describe you environment

Windows
Python version: python 3.6.2
Pipenv version: pipenv, version 8.2.6

Expected result
To be able to configure "find-links = ./wheels" somewhere, probably in the Pipenv file, and have it pick up wheels from that location. (I'd expect to be able to use a relative path, to mean "relative to the project directory", or an absolute path for wheels I store globally).
Actual result
I need to manually set PIP_FIND_LINKS before installing via pipenv, and then unset it afterwards, so that it doesn't affect other invocations of pip.
Steps to replicate
pipenv install. Pipfile is
[[source]]
url = "https://pypi.python.org/simple"
verify_ssl = true
name = "pypi"

[packages]
cassiopeia = "*"
pycurl = {file = "./wheels/pycurl-7.43.0-cp36-cp36m-win_amd64.whl"}

[dev-packages]

Output is:
>pipenv install
Creating a virtualenv for this project…
Using real prefix 'C:\\Users\\pfmoore\\AppData\\Local\\Programs\\Python\\Python36'
New python executable in C:\Users\pfmoore\.virtualenvs\riot_data-4b7hkvZN\Scripts\python.exe
Installing setuptools, pip, wheel...done.

Virtualenv location: C:\Users\pfmoore\.virtualenvs\riot_data-4b7hkvZN
Pipfile.lock not found, creating…
Locking [dev-packages] dependencies…
Locking [packages] dependencies…
Updated Pipfile.lock (17f190)!
Installing dependencies from Pipfile.lock (17f190)…
An error occurred while installing pycurl==7.43.0! Will try again.
  ================================ 8/8 - 00:00:17
Installing initially–failed dependencies…
Collecting pycurl==7.43.0 ----------- 0/1 - 00:00:00

THESE PACKAGES DO NOT MATCH THE HASHES FROM Pipfile.lock!. If you have updated the package versions, please update the hashes. Othe
rwise, examine the package contents carefully; someone may have tampered with them.
    pycurl==7.43.0 from file:///C:/Work/Projects/riot_data/wheels/pycurl-7.43.0-cp36-cp36m-win_amd64.whl (from -r C:\Users\pfmoore\AppData\Local\Temp\pipenv-y27xl4s1-requirement.txt (line 1)):
        Expected sha256 de2980f2839029ffa2917fcc1eb84b2dc736f0a30a5413645e514a2b61df04ed
        Expected     or d6cb0917ce564c9edc377ae436bc0963ee72be8873c90bcce7470f1670c3baef
        Expected     or 1ba222eafcb740805d5c9fe778a47d2704bf764abe9a2546de90f159e4c3a116
        Expected     or f614c93422f31761764a002297b56a0c7f0aeaee7badb0fb43764bda13467697
        Expected     or b0af8badfda56b175e190cf0fb1a18d2bd600a677d3b5d9f7a579823eec74fa4
        Expected     or 9db493308f092b87d8113cea322886f07c2f1b64f9839dffd4a65c300f91244b
        Expected     or 26dcfb05ecbaa27ffaa71a4a3add217ec9e1cee2998b727e1b9e6eff7264d5f8
        Expected     or 413b82b25795dcd0656e2d254892a16f531d88eccabc3a97c9c9451781caf5e8
        Expected     or 89758f2375fe44b139fcc11e305a060c75a4a89178b5066a3894055fe069a80e
        Expected     or 991d221a59c5546370e618241ec05e7d85efd7c5126fb33387de0a12c2cfe8e4
        Expected     or 39a7399e7da031f4648bd6ea273b02c0cf203471b63fe3629d19ebfd13e5701f
        Expected     or 9997e9994860cc99f2622de4133e0dd1756797852645dc6942b58142014f2e59
        Expected     or aa975c19b79b6aa6c0518c0cc2ae33528900478f0b500531dbcdbf05beec584c
        Expected     or 7d1ffc138132a7dcb322d41b1f7d5ed7e2f9bb0dea3103ae5ca25fae2a1f689b
        Expected     or 074a565bc33cfc484fa87339136876f1d8176bd30bb214235e11382b363beef9
        Expected     or d6ac0f902cb82cab13bc9488fb5240cf86325bd24800dc5ab677f8044993f6fc
        Expected     or 61d4b1a2dc1ecdb3b6d4188d63ab884e8768cfc85f37f48c481935b784920137
        Expected     or 1339972f6faf9e7feb54e0d62b018dcea6c99fb5ca46fef4a8d20c2a810d1f2d
        Expected     or 30983ec2f88ee0d26d290f276563c26bc1d302f1f6fc447092368bce7a93f0ea
        Expected     or 9075d35c8bafb96a836a7558b37fe697ec04646f76239254b06e87eb360097c7
        Expected     or 36c3a2d6b4ca31f39ac84fe9b7616d338191f956710c7912c546ffef18600f2f
        Expected     or 024fba378134633694b7a64ec7cb8ef9a98e3ce6b5635247b51b7282b96f33de
        Expected     or 826866c43ef532b7633e24332b7f4bc6b309e72b33631c2b06258fdb284dd55b
        Expected     or 59f637ffe21a90b6155df34b9fdf3030b6453859110db8700bf17f569c6449d6
        Expected     or 614687bdc73246ce85f73b7199d533a222efdda954e84a6bd692fef25fa3b6ac
             Got        7b9443007238914a6cc7fb6c3442aa00f06868b141837097f249adf54add11b6

     ================================ 0/1 - 00:00:01

>pipenv run pip list
Package       Version
------------- -------
cassiopeia    3.0.13
datapipelines 1.0.2
decorator     4.1.2
merakicommons 1.0.2
networkx      2.0
olefile       0.44
Pillow        4.3.0
pip           9.0.1
setuptools    36.6.0
wheel         0.30.0

Note that pycurl is missing from the output of pip list.

Hey @pfmoore!  Thanks for the report.  This is a rough niche situation not having the prebuilt wheel.  Being that it is a niche situation I'm gonna mark it as a future enhancement!  This will probably need a change to the pipfile spec, which @kennethreitz can weigh in on

closing and referencing #909 for all further talk about dep resolution

Hmm, I'm not sure it's that niche. Needing to use prebuilt wheels is fairly common on Windows, and Christoph Gohlke maintains an extensive and well-known archive of such wheels, particularly for the scientific stack (although it is true that more and more projects now host wheels on PyPI). So while I'm OK with the idea that it's an enhancement, I think it's a fairly important use case.
Also, even if it's not supported directly by pipenv yet, documentation on ways of working round the limitation would be useful (I assume that hosting the wheel in a local index like devpi would work, for example).

Actually, #909 doesn't seem that related. What I'm specifically looking for is a way to specify that a directory within the project holds artifacts (probably wheels, but potentially sdists as well) that should be considered as a source. Something like
[[source]]
bundled_artifacts = "relative_path_within_repo"
name = "bundled"

which could then be referenced like any other source.
By limiting it to relative paths within the project, it avoids the possibility of depending on context that's only available on the local system.
See the discussion on https://github.com/pypa/python-packaging-user-guide/issues/373 for more context.

You can specify local paths in your pipfile already and you can specify project environment variables in a .env file per the documentation.

On Oct 18, 2017, at 8:58 AM, Paul Moore<EMAIL_ADDRESS>wrote:
Actually, #909 doesn't seem that related. What I'm specifically looking for is a way to specify that a directory within the project holds artifacts (probably wheels, but potentially sdists as well) that should be considered as a source. Something like
[[source]]
bundled_artifacts = "relative_path_within_repo"
name = "bundled"
which could then be referenced like any other source.
By limiting it to relative paths within the project, it avoids the possibility of depending on context that's only available on the local system.
See the discussion on pypa/python-packaging-user-guide#373 for more context.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

This may be best reformulated as a docs RFE then, as neither @pfmoore nor I realised sources[n].url could already be a relative path within the repo - we thought it needed to be a network accessible URL.
If we're wrong about that, then that's a very useful discovery, and worth investigating further to see how we might have got that mistaken impression.

I should be clear. Pipenv allows you to specify local paths to wheels for specific packages already. It also allows you to define persistent environment variables in a .env file. It is not a replacement for pip; it uses pip. I’m fairly confident that since this functionality exists and can be dropped into the environment, it is probably out of scope for pipenv.

On Oct 18, 2017, at 9:17 AM, Nick Coghlan<EMAIL_ADDRESS>wrote:
This may be best reformulated as a docs RFE then, as neither @pfmoore nor I realised sources[n].url could already be a relative path within the repo - we thought it needed to be a network accessible URL.
If we're wrong about that, then that's a very useful discovery, and worth investigating further to see how we might have got that mistaken impression.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

The aim of this RFE would be for folks to be able to do:
git clone <repo_url>
cd the_project
pipenv install --dev
pipenv shell

And have that resulting shell be fully functional for development purposes, even if some of the dependencies are only available as bundled wheel files within the repo.
Right now, that "clone, install & run" outcome can be achieved only if all the artifacts to be installed are available somewhere online (i.e. you're not bundling anything directly inside the repo).
The RFE is thus for there to be a way to tell pipenv to look inside the repo for bundled deps, and for it to remember that fact, and hence rely on it automatically when the repo is cloned in the future.
Setting PIP_FIND_LINKS in a .env file unfortunately isn't sufficient, as that only gets read by pipenv shell and pipenv run (not pipenv install), and the docs explicitly advise against checking .env files in anyway (since the primary intended use case is for credential management): https://docs.pipenv.org/advanced.html#automatic-loading-of-env

@pfmoore or @ncoghlan do you have an example repo that has a wheel in it I can test with?  Submit a failing test maybe?

Only a local one at the moment, but I can put it on github. It's nothing more than a directory with a subdirectory "wheels" and in there a wheel downloaded from http://www.lfd.uci.edu/~gohlke/pythonlibs/
There's no Pipfile precisely because I don't know how to specify what I'm trying to achieve. Or I caould add the one from above:
[[source]]
url = "https://pypi.python.org/simple"
verify_ssl = true
name = "pypi"

[packages]
cassiopeia = "*"
pycurl = {file = "./wheels/pycurl-7.43.0-cp36-cp36m-win_amd64.whl"}

[dev-packages]

but that doesn't do what I want, so I'm not sure how useful that would be to you?

The file specification requires real file URIs. Pipfiles ca man use path instead for relative locations

On Oct 19, 2017, at 3:44 AM, Paul Moore<EMAIL_ADDRESS>wrote:
Only a local one at the moment, but I can put it on github. It's nothing more than a directory with a subdirectory "wheels" and in there a wheel downloaded from http://www.lfd.uci.edu/~gohlke/pythonlibs/
There's no Pipfile precisely because I don't know how to specify what I'm trying to achieve. Or I caould add the one from above:
[[source]]
url = "https://pypi.python.org/simple"
verify_ssl = true
name = "pypi"
[packages]
cassiopeia = "*"
pycurl = {file = "./wheels/pycurl-7.43.0-cp36-cp36m-win_amd64.whl"}
[dev-packages]
but that doesn't do what I want, so I'm not sure how useful that would be to you?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Sorry, I'm confused. As I understand it, it's not possible to have file URLs for relative paths (and if it is, the rules for constructing them in a cross-platform manner seem obscure at best).
Can you explain the syntax I'd use to say "the file pycurl-7.43.0-cp36-cp36m-win_amd64.whl stored in the wheels directory that exists alongside the Pipfile file"?
I'm confused as to what's being said here. Is this an existing, supported, capability in pipenv? @erinxocon seemed to be saying in https://github.com/kennethreitz/pipenv/issues/914#issuecomment-337439874 that it was a future enhancement...?

I don't think pipenv handles local wheels well.  I haven't really had a chance to test though.  Been real busy with work!

@erinxocon No problem. I completely understand.
My main question isn't so much whether things work well/badly, or even if there's a bug. My real question is whether this scenario is currently supported or not. If it's not supported, that's fine - I can raise a new feature request explaining my requirement and asking if it could be supported. If it is supported, then the docs don't explain it very well. If someone can clarify how to set things up, I'm happy to try to write a doc PR to improve things. (There may also be bugs in the implementation, if it's not a well-used feature - I'm happy to be a guinea pig in that case, and report any problems I hit).
My impression is that actually, this simply isn't something anyone has thought through, so it might work, but more as a side-effect of how other features work than as a fully fleshed out use case. If that's true, I'd be inclined to just treat it as a feature request, rather than struggle to try to make the existing features handle an unexpected corner case.

@pfmoore no I actually think this should work, the pipfile spec allows local paths using {path = "../path/thing.whl"} but it is currently broken (apparently) and I'm not sure why yet.  So there is 100% a bug here.

@techalchemy OK, but you're saying I should explicitly specify the path to the precise wheel, rather than specifying a directory and a requirement? If I were doing this with a requirements file, I'd use the latter, because I'd potentially want to store multiple wheels for different architectures.
But I'm fine with the idea that an explicit filename is the supported approach now, and "define a source that's a local directory of wheels" is an enhancement request. If that's the case, I'm happy to help with testing/fixing the existing bug first, and then lookingat raising the enhancement request.

But I'm fine with the idea that an explicit filename is the supported approach now, and "define a source that's a local directory of wheels" is an enhancement request

This is precisely the situation.  Currently installing anything as a local path in a project subdirectory fails horribly with no explanation and I haven't had a chance to untangle the exact reason.  this is obviously a huge problem, and can be replicated as follows:
$ mkdir /tmp/test
$ cd /tmp/test
$ mkdir dls
$ wget -O dls/requests.zip https://github.com/requests/requests/archive/master.zip
$ pipenv install dls/requests.zip

This also fails with pipenv install ./dls/requests.zip, but works fine if you do the following:
$ cp dls/requests.zip ./
$ pipenv install requests.zip

I suspect it would work similarly well if you copied a wheel into the project root.

OK. I'll put together a test using a wheel, and maybe see if I can come up with any ideas for what's happening.

Sure thing. I’ve been encouraging some discussion on the irc channel #pipenv on freenode. I’m popping in and out but you can find me as hawkerz.  The broader discussion about local paths, files, and (potentially) environment variables should happen in the issue I referenced

On Oct 19, 2017, at 2:20 PM, Paul Moore<EMAIL_ADDRESS>wrote:
OK. I'll put together a test using a wheel, and maybe see if I can come up with any ideas for what's happening.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I was posting via email before but the issue I was talking about is #939 which is meant for a discussion about how to approach local files in general.  I haven't spent a ton of time troubleshooting this yet but the ideal approach in my mind would be to check if a provided input is a path or file, and, if so, see if we can install it somehow / do dependency resolution

Hmm. That seems to be about local files on the command line (pipenv install foo) where I can see that there's a need to address the confusion between a package name and a local directory. My issue here is about manually editing Pipfile to explicitly state my intention.
To be frank, I think I've got a badly skewed mental model of how pipenv works, and that means I can't see the connection you're suggesting. My main priority should likely be to understand the correct approach to using pipenv before I try to work on solutions. But I'm not quite sure how to do that.
The way I got to where I now am is as follows - the docs start by showing how to use pipenv install foo in a new project directory to start setting up the working environment for your project. From there, "Basic Usage" shows what Pipfile looks like, but it still mostly talks in terms of a model where I use pipenv install to add packages, and don't manually edit Pipfile.
My use case (where installing from PyPI fails due to a lack of a binary wheel) clearly dumps me into "Advanced Usage" territory. Here, "Specifying Package Indexes" sounds like exactly what I'd want, but it's only for PyPI style URLs, not for local directories of packages. That's where my suggestion of adding syntax to [[source]] came from.
There's nothing else in the pipenv docs that looked relevant to me, but the example in https://github.com/pypa/pipfile includes a "file=" option for a package, but that uses a URL, not a path (and file: URLs are basically hopeless to use for relative files, or absolute Windows paths).
That's the point I came here.

The pipenv documentation implies I should be writing a [[source]] section, but doesn't tell me how to do that for a local directory (it implies it's more like --index-url than --find-links in pip terms).
The pipfile documentation provides file= but it implies that only URLs are supported, and it doesn't support having a set of wheels in a directory, with the correct one chosen based on compatibility with the platform.

The discussion here leads me to think that (1) is an enhancement request. And (2) in principle works but has bugs (and has the limitations I note above). But #939 doesn't seem to relate to Pipfile syntax at all, but rather to command line usage, and I'm reluctant to add my confusion to that issue as well as to this one...
For my current project, I've (at least for now) abandoned pipenv, and reverted to pew plus a requirements file. I'm happy to help get pipenv to a point where it handles what I'm doing, but I'm struggling to understand how I can contribute usefully. Maybe I'm better, now that I've explained my use case, to step back and leave the experts here to consider it.

To answer your question:

Pipfiles support local filesystem paths the way I described above.  I don't control the documentation, I can only tell you how the implementation works because I pushed for it and am partly responsible for its inclusion in the spec.
I already understand that you would like an enhancement whereby you can specify a --find-links parameter in your install, this is not part of pipenv right now but probably isn't that difficult and could also be handled as a passthrough environment parameter to pip or pip-tools, I would assume
The remaining issue is that the only option that should currently work for your case is to put the {path = "wheels/package.whl"} entries directly into your Pipfile or to run pipenv install wheels/package.whl from your project directory, however this does not work currently because of a bug nobody has had time to examine

Thanks for clarifying. I'll see if I can dig into the bug from point (3), as that seems the most productive.
It seems that much of my frustration stems from how the documentation is structured. I appreciate that's not something you can influence, which is fine. But I would like to flag that issue somehow. Maybe it needs me to raise a new issue and start afresh. I'll try to see if I can work out how to explain the problem I had with the docs clearly enough to do that.

@pfmoore, please feel free to open an issue for the issues you have with the documentation. It's evolved fairy haphazardly and seen some significant revisions recently so I'm not surprised there are gaps.
Once we have those cataloged we can start rallying time to get the docs fixed. If you feel like putting together a PR, that's great too :)

As for the wheel issue, we should be able to support installing local packages that are inside the project, but pipenv historically hasn't really been intended to install arbitrary packages on the file system. The lockfile becomes machine specific at that point and defeats the point of having a reusable setup.

@nateprewitt there were a bunch of issues similar to this one where users were bundling relative paths, enough so that Kenneth was willing to update the pipfile spec for it.  The original use case was for a path outside of the project directory, but at the very least relative paths inside of the project directory should be in scope (I can't remember how we decided to hash them but I feel that may be causing our recent bugs)

@nateprewitt "But reproducibility..." was my initial reaction as well, but then @pfmoore pointed out that the idea behind using a relative path is that it means you can easily bundle the relevant wheel files with the affected source project, similar to the way CPython handles bundling pip and setuptools for the sake of ensurepip.
That then actually ends up improving environmental reproducibility, since you get the otherwise-tricky-to-obtain dependencies right along with the source code.

@ncoghlan to clarify, I'm completely for relative paths to packages in the project. I stated that in other comments this evening, sorry it didn't make it into this one.
What we have previously been against is allowing people to specify arbitrary paths to, for example, something the have in their downloads folder or desktop. These are the kinds of things I'd prefer we avoid and I think historically we have.

@nateprewitt Aye, I think it would be reasonable for paths outside the project to be at least actively discouraged (with a warning), if not outright prohibited.
Even --site-packages can be problematic on the reproducibility front, but at least in that case, the host environment itself is often amenable to automated management.

@nateprewitt until #540 (which traverses up one directory outside the project root) we only supported file:// URIs in the pipfile spec.  The resolution for that issue added the path keyword and operated in what I think is the way you are describing as being concerned about.  I don't think it's wrong to be concerned about it -- I was concerned about the use case at the time, and suggested that any relative paths outside the project directory should be converted to absolute file:// URIs.
I still sort of think this is how we should approach it, although I think Kenneth was  adamant that developers who wanted to screw with their pipfiles in such a way should be allowed to have this kind of configuration, and perhaps the lockfile should pin down the path? Not sure what makes sense there.

@ncoghlan the thing is pipenv already has built in support for file:// URIs which are, by nature, not portable.  Support for this pre-dated support for relative paths, which are substantially more portable, for the most part.  I see no reason why we would want to stop people from installing things just because those things might not exist somewhere else, the point of pipenv is to help manage dependencies, not to prevent people from doing things that would work fine with their normal tools.
IMO the questions we should be asking don't revolve around what we should allow users to install, but how we should be representing that information internally both in the pipfile and the lockfile.

It may also be worth noting here that personally, I have little or no interest in total reproducibility. I am interested in getting a usable environment, but it doesn't bother me in the slightest if (for example) I get a new version of a dependency if I rebuild my environment.
If that makes me an unusual corner case for pipenv, that's fine - but I got here via the Python packaging user guide, and neither that nor my reading of the docs gave me any impression that pipenv valued reproducibility more than I did. The pipenv docs say that it enables reproducible builds, rather than (for example) promoting them, and mention them under "Pipfile security features", but don't really explain why I should want them (or what I should expect if I don't - for me, machine-dependent absolute paths are fine for most of my projects, so being told I shouldn't use them and the tool deliberately doesn't support them is a clash of goals).
I'm not saying that I mind environments being reproducible - just flagging that as things stand, if the PUG starts recommending pipenv as per its current draft tutorial, you could start getting users arriving here confused as to why their requirements don't match with your priorities, much like I did.

Local file installation is resolved in #958

I'm curious as to how exactly this is supposed to be used. I'm confused as to what exactly I need to put in the Pipfile and or the Pipfile.lock file in order to install a specific whl package into the pipenv.
If I wanted to install the cryptography package where the relative location from where my pipenv is being executed from is "./install/cryptography-2.1.4-cp27-cp27m-win_amd64.whl", where and how do I put that in the pipenv files? I've tried a number of combinations and nothing seems to work. It just wants to install the version that's already on my local environment which is lower than the version that I want installed in the pipenv. Does the whl have to be in a gz or zip? I don't have a requirements.txt file, but should I?
Here's my Pipfile:
[[source]]
url = "https://pypi.python.org/simple"
verify_ssl = true
name = "pypi"
[dev-packages]
[packages]
cryptography = "*"
[requires]
python_version = "2.7"
Here's my Pipfile.lock:
{
"_meta": {
"hash": {
"sha256": "60e72c1b289a3648291f0eef58dcc4be3b7ecc10dbb128893baa616e5bd4bb26"
},
"pipfile-spec": 6,
"requires": {
"python_version": "2.7"
},
"sources": [
{
"name": "pypi",
"url": "https://pypi.python.org/simple",
"verify_ssl": true
}
]
},
"default": {
"cryptography": {
"hashes": [
"sha256:0d39a93cf25edeae1f796bbc5960e587f34513a852564f6345ea4491a86c5997",
... (removed middle to shorten post)
"sha256:fc2208d95d9ecc8032f5e38330d5ace2e3b0b998e42b08c30c35b2ab3a4a3bc8"
],
"version": "==2.1.4"
}
},
"develop": {}
}

Don’t put anything in either file manually. pipenv install ./file.whl

Most especially never ever put anything in your lockfile manually.

I tried that, but it still doesn't want to install. I get an error stating that cryptography needs to be >= 2.1.4. Is this a requirement for pipenv to work? Even executing "pipenv shell" gives me this error.
Traceback (most recent call last):
File "C:\Python27\Scripts\pipenv-script.py", line 6, in
from pkg_resources import load_entry_point
File "c:\python27\lib\site-packages\pkg_resources_init_.py", line 3142, in
@call_aside
File "c:\python27\lib\site-packages\pkg_resources_init.py", line 3126, in call_aside
f(*args, **kwargs)
File "c:\python27\lib\site-packages\pkg_resources_init.py", line 3155, in _initialize_master_working_set
working_set = WorkingSet.build_master()
File "c:\python27\lib\site-packages\pkg_resources_init.py", line 666, in _build_master
return cls.build_from_requirements(requires)
File "c:\python27\lib\site-packages\pkg_resources_init.py", line 679, in build_from_requirements
dists = ws.resolve(reqs, Environment())
File "c:\python27\lib\site-packages\pkg_resources_init.py", line 872, in resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (cryptography 2.1.1 (c:\python27\lib\site-packages), Requirement.parse('cryptog
raphy>=2.1.4'), set(['pyOpenSSL']))

@purEnergy please file a separate issue where we can troubleshoot your error, instead of using this one

Got it. I filed a new issue. I thought this might be related and have been a quick one to solve, but apparently not. Thanks for the help here.


Only include public members of components

Currently the documentation includes ALL members (properties, attributes, states, etc) of the web components. For the time being, the documentation is only intended for end users of the components so what members are included in the documentation should be limited to only public members.

Done in commit 4ca345cb826d3832c9f3d98521b22b8f83e9af05.


fix: escape quotes and percentage in date to string for duckDB

Also

fix the tests (the output was in the snapshot so the expected was useless and it was more confusing than anything)
remove %-M which is not for all dialects and not super common
force UTC as timezone for the date to string repr

While writing the doc I saw that I forgot to support %%. Now it's done :)


Show exact time of each annotations at SpanPanel

For investigation purpose, we often want to know not only duration but also the exact time of each spans. This patch shows their local date time at Span Panel. This is useful to investigate the cause of  irregularly long span by collating its time with server log file.

@eirslett you cool with this?

+1

okie dokie.. on the way!

Thanks for the help @synk! bcac2a322e0305c1fb43a75ebac8007337fdbd01


Streamline selection of descriptor-type and workflow path

When changing the descriptor-type and workflow-path, some changes could be streamlined.
a) When toggling the descriptor-type, the workflow path should be automatically changed to match the new extension (e.g. choosing WDL should cause /Dockstore.cwl to change to /Dockstore.wdl)
b) When editing the workflow path, the change should cascade down to the versions of the workflow as well (this can be done either in the GUI or in the web service)

Notes:
a). Users are allowed to put in anything in the workflow path when editing. However, should add warning if the extension is not cwl,wdl,yaml,yml. If the extension in workflos path is neither cwl/wdl, then dont change the descriptor type dropdown.
b). Changing the workflow path in 'Info' tab(default) should change the workflow path in 'Version' tab, but not the other way around. Changing path in 'Version' tab should not change the path in 'Info' tab(default)


Add counter_cache to track number of follows for each article

In general this is easy to do to count associations.  However, th epolymorphic nature of this particular retlationship makes it less typical.  I think  can find an example using Posts and Comments,, but I am timeboxed for now.
this may help: http://stackoverflow.com/questions/18166997/sort-posts-by-their-comment-counts-then-created-at-date-in-rails

on production.


GPII-3715: Move Audit Logging Config to  native Terraform

This is required as part of migration to new v2.0.0 version of Terraform Google Provider, as the google_project_iam_policy resource became strictly authoritative on the complete policy_data object (see https://www.terraform.io/docs/providers/google/version_2_upgrade.html#resource google_project_iam_policy for details). Since TF supports managing Audit Logging config natively now, it only makes sense to use TF to do this.
Also, instead of having to list individually all the services, GCP Resource Manager API supports special value allServices (see `https://cloud.google.com/resource manager/reference/rest/Shared.Types/AuditConfig for details). This has an additional benefit as it will automatically stay up-to-date as Google releases support for Audit Logs for additional services (see https://cloud.google.com/logging/docs/audit/#services for details).
This has been tested and should go together with https://github.com/gpii-ops/exekube/pull/43

LGTM

LGTM
auditConfigs clean-up looks nice :). Do we have anything to test after that change to make sure we're still getting all the audit logs we want?

I did verify manually on the test org, will do same for prod. Command to get actual policy is: gcloud projects get-iam-policy <project_id>.
Also reading actual data access logs (those are interesting as those are optional compared to admin access) can be done with:
gcloud logging read \                                                                                (move-to-istio|✚10…) 0
    'logName="projects/gpii-gcp-prd/logs/cloudaudit.googleapis.com%2Fdata_access"' \
    --limit 5 \
    --freshness 1d --project gpii-gcp-prd --format="table(timestamp, resource.labels)"
TIMESTAMP                       LABELS
2019-02-20T11:21:13.203708976Z  {u'project_id': u'gpii-gcp-prd', u'method': u'google.monitoring.v3.MetricService.ListMetricDescriptors', u'service': u'monitoring.googleapis.com'}
2019-02-20T11:21:11.913614764Z  {u'cluster_name': u'k8s-cluster', u'nodepool_name': u'', u'project_id': u'gpii-gcp-prd', u'location': u'us-central1'}
2019-02-20T11:21:09.941037Z     {u'cluster_name': u'k8s-cluster', u'project_id': u'gpii-gcp-prd', u'location': u'us-central1'}
2019-02-20T11:21:09.795038Z     {u'cluster_name': u'k8s-cluster', u'project_id': u'gpii-gcp-prd', u'location': u'us-central1'}
2019-02-20T11:21:09.222622Z     {u'cluster_name': u'k8s-cluster', u'project_id': u'gpii-gcp-prd', u'location': u'us-central1'}

Command above shows output for prod before merge -> logs are comming. I'll update this ticket after this changes is deployed to confirm.

After deploy:
$ gcloud projects get-iam-policy gpii-gcp-prd

...
auditConfigs:
- auditLogConfigs:
  - logType: DATA_WRITE
  - logType: DATA_READ
  - logType: ADMIN_READ
  service: allServices
...

^ This looks as expected, Audit logs enabled for all svcs.
$ gcloud logging read \
    'logName="projects/gpii-gcp-prd/logs/cloudaudit.googleapis.com%2Fdata_access"' \
    --limit 5 \
    --freshness 1d --project gpii-gcp-prd --format="table(timestamp, resource.labels)"
TIMESTAMP                    LABELS
2019-02-20T14:25:25.791Z     {u'instance_id': u'', u'project_id': u'gpii-gcp-prd', u'zone': u'us-central1-b'}
2019-02-20T14:25:25.739483Z  {u'cluster_name': u'k8s-cluster', u'project_id': u'gpii-gcp-prd', u'location': u'us-central1'}
2019-02-20T14:25:25.672401Z  {u'cluster_name': u'k8s-cluster', u'project_id': u'gpii-gcp-prd', u'location': u'us-central1'}
2019-02-20T14:25:25.647419Z  {u'cluster_name': u'k8s-cluster', u'project_id': u'gpii-gcp-prd', u'location': u'us-central1'}
2019-02-20T14:25:25.645Z     {u'instance_id': u'', u'project_id': u'gpii-gcp-prd', u'zone': u'us-central1-f'}

$ date
Wed 20 Feb 2019 15:25:41 CET

$ gcloud logging read \
    'logName="projects/gpii-gcp-prd/logs/cloudaudit.googleapis.com%2Fdata_access"' \
    --limit 5 \
    --freshness 1d --project gpii-gcp-prd --format="table(timestamp, resource.labels)"
TIMESTAMP                    LABELS
2019-02-20T14:25:47.879Z     {u'project_id': u'gpii-gcp-prd', u'location': u'global', u'backend_service_id': u''}
2019-02-20T14:25:43.827275Z  {u'cluster_name': u'k8s-cluster', u'project_id': u'gpii-gcp-prd', u'location': u'us-central1'}
2019-02-20T14:25:43.824331Z  {u'cluster_name': u'k8s-cluster', u'project_id': u'gpii-gcp-prd', u'location': u'us-central1'}
2019-02-20T14:25:43.792330Z  {u'cluster_name': u'k8s-cluster', u'project_id': u'gpii-gcp-prd', u'location': u'us-central1'}
2019-02-20T14:25:43.784025Z  {u'cluster_name': u'k8s-cluster', u'project_id': u'gpii-gcp-prd', u'location': u'us-central1'}

^ Data access Aufit logs are arriving (note date is in CET -> 1h off).


Authentication switch from SSO to DB

What is currently missing?
When switching from SSO ad AuthN all passwords are removed from internal database when there is outage in IDP and you switch back from ad to db authN this creates two issues

logs are flooded with error messages that users cannot be initialized because password is missing
Users cannot log in even when they previously had the password set. This combined with the password reset issue is a problem

How could this be improved?

Improved logging
fix pwd reset issues

Is this a feature you would work on yourself?

[ ] I plan to open a pull request for this feature

This needs to be reviewed, I agree logging needs to be improved to not flood the logs, however I am not keen on keeping potentially stale passwords in the DB especially as we now have a working and improved password reset.


Fixing equality operators in common docs

In the new TS version you can't compare two different numbers directly because they are considered different literal types (i.e. instead of "number" and "number" the types would be "0" and "42"). This doesn't have much of a practical effect because those expressions will always evaluate the same way anyways.

@riknoll is there a way to disable this check in TypeScript? I have a feeling this is one type too many for kids.

Sadly, no. We could maybe filter out the errors though


Array out of bound Bug in regex_syntax::hir::LookSet::read_repr

What version of regex are you using?
regex-syntax = "=0.7.2"

Describe the bug at a high level.
When calling regex_syntax::hir::LookSet::read_repr, if the length of the slice is less than 2, the program crashes. It is necessary to add an array bounds check to prevent this issue.
What are the steps to reproduce the behavior?
source code:
fn main() {
    //println!("_param1 = {:?}", _param1);
    let _local1 = regex_syntax::hir::LookSet::read_repr(&[0]);
}

What is the actual behavior?
it crashed.
thread 'main' panicked at 'range end index 2 out of range for slice of length 1', /home/yxz/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/regex-syntax-0.7.2/src/hir/mod.rs:2748:39

This is behaving as documented: https://docs.rs/regex-syntax/latest/regex_syntax/hir/struct.LookSet.html#panics


SCORM import - repeater fields missing

There is a problem with SCORM zip file uploads and repeater fields.
Problem:
when uploading SCORM files containing repeating values, these repeated values are not imported into openEQUELLA.
We have raised this issue with Edalex previously, please see ticket number 101337 for more details and example package to replicate (SCORM package, metadata schema, collection export)

Hi @NextEdServices, is it possible for you to attach a screen recording demonstrating the issue?
Or some more detailed steps to reproduce?

Hi, screenrecording, SCORM file and collection by request (cannot upload here)
Steps:

contribute / upload SCORM zip file containing repeating metadata values into collection that has referring repeater fields marked as mandatory
some of the mandatory repeater fields are not imported correctly
remove mandatory setting in the wizard, contribute / upload same SCORM course - and the SCORM metadata values are imported.

Wizard setting with mandatory fields:

After Uploading SCORM Course no Rol entry:

Wizard setting without mandatory fields:

After Uploading SCORM Course ok:

(Further: Please note there is different behaviour when uploading SCORM courses with the contribution upload link or with clicking in the file upload field. The latter seem not to import repeater values either.)

@mrblippy I have emailed you a direct link as I had difficulties uploading (sensitive) material. Let me know if you have any issues or questions.

We currently have this on our list to look at, so re-opening.

@NextEdServices I was attempting to diagnose and fix this problem in-code, and I discovered that it is not actually a bug, rather a collection configuration issue.
So in the your collection you have the repeater in question set up like this:

You also have IMS metadata mapping set up for these fields, so openEQUELLA should create repeater instances for each element that matches this xpath, but it doesn’t.
Now, the problem itself is a little unintuitive - the field labelled "Minimum number of repeats" is set to 1. For some reason this disables metadata mapping to repeaters - it seems to be that the minimum count is for manually inputting data into repeaters fields rather than mapping them from metadata.
If you set that field to 0, and save the collection, data should map properly. I have tested this with your collection and SCORM package locally on my machine. I also during testing edited the imslrm.xml to contain multiple different values of lom/lifeCycle/contribute, to make sure that openEQUELLA would add and map repeaters for each one.
testing video clip
I have attached a short clip of me doing the following testing steps in order:

In the Administration Console, open the Buenas prácticas collection in the editor and find the Contribuciones repeater. Set the minimum number of repeats to 0 and hit Save.

Open a contribution using the Buenas prácticas collection and add the SCORM package, as it is without changes.

Go to the Obligatorios page and scroll down to the Contribuciones repeater.

Note that the Rol field is populated in one repeater.

Repeat step 2 and 3, this time using a modified version of the client’s SCORM package that contains another two instances of lom/lifeCycle/contribute in the imslrm.xml to prove that it is mapping properly. In each additional lom/lifeCycle/contribute node, the Rol and the Nombre values are edited.

Note that the Rol field is populated for 3 repeaters.


MySQLSyntaxErrorException: Table 'wherehows.log_dataset_instance_load_status' doesn't exist

frontend is throwing an error - table log_dataset_instance_load_status does not exist. I didn't find any references to that table in sql scripts. Anyone having similar issue?
https://github.com/linkedin/WhereHows/blob/0cd9d682580d8004ab6ed23d0c1db257043770b2/wherehows-frontend/app/dao/DatasetsDAO.java#L350

#1054 should fix this


Incorrect data is fetched from graphite intermittently.

I am facing an issue such that the data returned from graphite is totally different and unexpected, sometimes. This leads to false alarms, and what not.
Later when I check the data again for the same query it is correct, this is happening intermittently.
Cluster Info
We are running graphite as a cluster of 5 nodes.

Node [A] does not store any data locally, it replicates [replication factor = 2] it into two different nodes [B, C]. It's webapp fetches data from Node [D] and [E]. We send and retrieve the data from this node.

Node [A] also runs statsd, which pushes data to node [A]'s relay.

Node [B] runs relay, cache and stores all the data it gets locally and serves this via the webapp, this is our backup server.

Node [C] runs relay, and doesn't store any data locally and forwards the data it gets (consitent-hashing), to two nodes [D, E].

Node [D, E] are nodes who run relay and cache, and store the data they get, and serve them via the webapp.

We have recently moved to this new clustered architecture, earlier we only had the single node [B].
Versions

whisper : 0.9.10
carbon : 0.9.12
webapp : 0.9.12

Any help will be greatly appreciated. Thanks.

First, you should never run mismatched versions of Graphite components. Second, there have been a lot of fixes for this type of behavior in the 0.9.x branch leading up to our next release. You should try the 0.9.x branch and please let us know if that doesn't fix your issues.

I have upgraded my cluster to  0.9.x and the issue has disappeared.
Thanks @obfuscurity!

Facing this issue again. I have seen two false alerts (got empty data from graphite for both).
Later when I queried for the same time period, it gives me non-empty data.


creating custom directives

when creating a custom directive is it possible to know if it is rendering in a creation/edition view or show view? built-in fields can be defined once, inserted in all views and they can correctly render as, e.g., input fields or span depending on the view. I wonder if it is possible to do the same with a custom directive, as I've found nothing in the scope.
thanks in advance!

Not now, but I proposed a refactoring to make this possible. See #294.


ActionController::Parameters#require signature needs adjustment

See https://github.com/Shopify/rbi-central/pull/224#pullrequestreview-1917467194

@aprescott Do you know what the full possible set of returnable types is?
It should be T.any(String, Integer, T::Array[T.any(String, Integer)) at a minimum, but do you know of any other possible cases?
Whatever that type is, that's what should be used as the return value of not just #require, but also #[], which still returns T.untyped

although interestingly it doesn't always fire runtime errors, as in cases like a T::Array[X] vs. T::Array[Y].

That's a performance concession, Sorbet's runtime type-checking doesn't do deep recursive type-checks on Enumerables. The runtime type-checking calls #valid?, not #recursively_valid?

Do you know what the full possible set of returnable types is?

I'm not sure! It would be good to match whatever Parameters can possibly support. String or Integer or Array containers of those certainly sounds reasonable. Perhaps Rails source would help confirm. I don't really know much about the rbi-central project's approach here, but perhaps T.anything is an option if the full set of output types isn't clear? The true correct typing would of course beat T.anything.

Sorbet's runtime type-checking doesn't do deep recursive type-checks on Enumerables

Found the docs explaining this right after my comment, realized my confusion!

String or Integer or Array containers of those certainly sounds reasonable.

Agreed, let's start there, and adjust it if people find that other values were possible.
@aprescott Would you be interested in opening your first RBI Central PR to contribute this Sig? :)

I don't really know much about the rbi-central project's approach here, but perhaps T.anything is an option if the full set of output types isn't clear?

I like using T.anything in my own code, but it's not a good fit for RBI central, because:

It gets in peoples' way. Personally I find that to be a good thing, to make me think about the types and act accordingly. But others see it as an intrusive hassle. Ruby developers are already used to dealing with unknown types, anyway.
It's kicking the can down the road. RBI Central is supposed to do the homework to provide the types, and T.anything largely indicates "🤷 we don't even know, either"


Add Sanitize for query input sanitization

Useful when passing through search queries from search form that's available to an end user.
Referenced this node implementation:
https://github.com/lanetix/node-elasticsearch-sanitize

Thanks for putting up the PR. I think this is a good idea but this is a pretty complex set of regular expressions. This needs a better set of tests before this could be merged.


Add support for viewing resources on multiple pages (backwards compatible)

After wanting to have better support for multiple pages, I rewrote parts of the layout.erb and added a second example resource to better show the changes. There are a few known issues that I plan to work on, but for individuals that want the basis of having multiple pages, this works well enough. I elected not to edit the javascript this time around to preserve backwards compatibility. I have done some work on Rspec_Api_Documentation to support this branch. It can be found here. That branch is still wip, so read over the changes here and there to use RAD with slate paged.
Changes:

You can list your resources on all pages, as well as the requests for that resource
The new changes only go into affect if multiple_pages: true is included in the index.html.md yaml.
This makes all these additions completely backwards compatible.
updated the ruby and bundler (Only because bundler wasn't working when I forked it straight up)

Known Issues:

The toc does not include the "includes." it's weird as the search does sometimes.
The toc drop down does not work. This is because I did not edit any of the _toc.js
Search is a bit weird. I did not edit it yet.

Hi @E1337Kat! Sorry for the slow feedback on this one. Thanks for spending the time to work on this! This has the general ideas of a feature we'd want, but I think we'd probably want the following attributes:

Listing all the headers manually is pretty laborious — it'd be nice to list all the files (and not ToC entries) in a single place, and maybe repurpose the toc_data.rb code to scrape them and figure out which ToC information needs to be inserted? Perhaps the other pages could list a 'root page' that includes the list of files, and could look up the list directly from there instead of duplicating the list.
Optimally, search would work across all pages at once. This is really tricky, and could require doing server-side indexing and swapping out our search implementation?
We'd definitely want any feature to not mess up the ToC's ability to drop down

I think starting with something more like Read The Doc's version selector would probably be much easier, since there wouldn't be the expectation that search would work across all pages. If you're still interested in working on this feature (2 months after you submitted — again, sorry!) glad to chat about how this feature could be designed if you open an issue?

for sure! thanks for the feedback! I had continued working on this to try and improve upon the submitted design. I'll def open an issue and see what we can do :)
(Sorry for the lack of response as well! Work has been pretty hectic)


Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:
https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/forelleblau/ioBroker.luxtronik1

[ ] [E201] Bluefox was not found in the collaborators on NPM!. Please execute in adapter directory: "npm owner add bluefox iobroker.luxtronik1"

Thanks,
your automatic adapter checker.
P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

Thanks, that all bugs have been fixed.


Eval of Double backqoute and unquote

Found this SO question Using two backquotes and commas, Common Lisp

the syntax is like this:
(eval ``(a ,,(+ 1 2) ,(+ 3 4)))

biwascheme throw an errror, maybe eval have problems with macros because if you execute just
``(a ,,(+ 1 2) ,(+ 3 4))

the output is correct.

Tried with BiwaScheme 0.6.8:
biwascheme> ``(a ,,(+ 1 2) ,(+ 3 4))
(#<Syntax quasiquote> (a (unquote 3) (unquote (+ 3 4))))

This should be
(quasiquote (a (unquote 3) (unquote (+ 3 4))))

This is not only for eval it will probably not work in macros defining macros as with #100

Looks like fixed now (may be by c5a69177095999a4f70c0cecadb8987f57060946 .)
biwascheme> ``(a ,,(+ 1 2) ,(+ 3 4))
(quasiquote (a (unquote 3) (unquote (+ 3 4))))
biwascheme> (eval ``(a ,,(+ 1 2) ,(+ 3 4)))
(a 3 7)


sort check list in layer and service page and set check date in service page to US/Estern zone

issue#281 and issue#282
The check date stored in database is UTC. If TIME_ZONE sets 'UTC', the pages will show UTC time.

@zhangmingda let's use the default attribute order for this, no need to create a specific method.
You can get this working using the ordering option in meta model options:
https://docs.djangoproject.com/en/1.11/ref/models/options/#ordering
Note: the build is failing. I don't think this is because of your commit. @tomkralidis any idea?

Thanks for the document link @capooti

Committed another PR.


parquet reader in Kùzu 0.0.9 shows different behaviour than earlier versions

I think this is a bug/regression in version 0.0.9 with the parquet reader that depends on pyarrow.
Python version: 3.11.2
OS: MacOS Ventura 13.5.2
Platform: M2 (arm64)
Polars version: 0.19.8
Pyarrow version: 13.0.0
Kùzu versions: 0.0.8 and 0.0.9
Issue
The code snippet below works for Kùzu 0.0.8, while it fails for version 0.0.9. The issue seems to be related to how the pyarrow reader decompresses and parses columns in the new version.
$ python test.py
shape: (3, 3)
┌─────┬───────┬─────┐
│ id  ┆ name  ┆ age │
│ --- ┆ ---   ┆ --- │
│ i64 ┆ str   ┆ i64 │
╞═════╪═══════╪═════╡
│ 1   ┆ Jack  ┆ 33  │
│ 2   ┆ Jill  ┆ 22  │
│ 3   ┆ Wendy ┆ 25  │
└─────┴───────┴─────┘
Traceback (most recent call last):
  File "/code/test.py", line 23, in <module>
    conn.execute(f"COPY Person FROM 'test.parquet';")
  File "/code/.venv/lib/python3.11/site-packages/kuzu/connection.py", line 90, in execute
    self._connection.execute(
RuntimeError: ColumnReader::decompressInternal

MRE
In the following code, I'm exporting a Polars DataFrame to parquet format. Note that I specify compression="zstd" (best compression performance), and also use_pyarrow=True to ensure that it uses the C++ implementation of pyarrow under the  hood -- this is what I'll be using downstream to ingest the parquet into Kùzu.
import os
import shutil

import polars as pl
import kuzu

df = pl.DataFrame({"id": [1, 2, 3], "name": ["Jack", "Jill", "Wendy"], "age": [33, 22, 25]})
print(df)

df.write_parquet("test.parquet", compression="zstd", use_pyarrow=True)

DB_NAME = "test_db"
# Delete directory each time till we have MERGE FROM available in kuzu
if os.path.exists(DB_NAME):
    shutil.rmtree(DB_NAME)

# Create database
db = kuzu.Database(f"./{DB_NAME}")
conn = kuzu.Connection(db)

conn.execute("CREATE NODE TABLE Person(id INT64, name STRING, age INT64, PRIMARY KEY (id))")

conn.execute(f"COPY Person FROM 'test.parquet';")

Workaround
I can use compression="snappy" to get the code above to work with Kùzu 0.0.9.
However, the default write_parquet method in Polars and use_pyarrow=True will prefer to use zstd compression, rather than snappy, which the Polars docs says is older and not as efficient with its compression.
Why is it that the code that used to work before, doesn't work now in newer versions of kuzu and pyarrow?

Hi Prashanth,
We recently switched from the arrow parquet reader to our own parquet reader. The new parquet reader currently only supports SNAPPY compression, and we are planning to support more compression and encodings in the next release.

Okay, will plan on documenting that I should only use snappy compression upstream!

Hi @prrao87
We have supported reading zstd and gzip compresssed parquet file in #2329 .


Deprecated things (PropTypes) and crashes

When added map to my application, suddenly I've got these errors:

Warning: Accessing PropTypes via the main React package is deprecated. Use the prop-types package from npm instead.

Warning: GoogleMap: React.createClass is deprecated and will be removed in version 16. Use plain JavaScript classes instead. If you're not yet ready to migrate, create-react-class is available on npm as a drop-in replacement.

ALSO.... when v6.3.0 is working, v7.0.0 is crashing on React ^15.5.4.

+1

This should all be fixed in v8.0.0
https://tomchentw.github.io/react-google-maps/


Create input parameters to designate unique ID fields for the input origins and destinations

Suggestion from a user: It would be useful if users could specify the origin and destination fields to use as identifiers.
This user got tripped up matching the output lines to their original input data since the OriginOID and DestinationOID values refer to the values in the output Origins and Destinations tables instead of the input.
Resolving this would involve adding more joins on the output but would not be horrendously difficult.

I believe this has been resolved by the improvements we made in the ArcGIS Pro 3.1 release to the solver object output fields.


Circuit ID should be returned in the response to a Dial request

It would be beneficial for the circuit ID to be returned in a Dial request response so that endpoint/SDK logs could be 1:1 correlated with fabric events, logs, and utilization records.

Either that or add the dial options to the entry stored in the elastic, so we can add a correlation ID and see the forwarded host in the entry. (the target of the original request)


core: expose engine via weak_ptr

Signed-off-by: Mike Schore<EMAIL_ADDRESS>

@junr03 So I’m kinda going back on what we talked about Friday - I do think leaking forever would fix our problems for now, but I still think a weak pointer is probably just necessary long-term. Because the engine’s lifecycle will(?) ultimately be tied to the platform wrapper’s lifecycle, we need to be very careful about the timing of incoming calls coming from other (arbitrary) threads. I think we will always want to manage the engine’s state via an exposed weak_ptr that we use to capture shared_ptrs for the duration of calls - to prevent destruction starting while any thread might be touching Engine in its stack.
To make this non-singleton, we convert the internal shard_ptr to one the platform wrapper holds (and eventually resets).

Thanks for the review :)


UI todo catch-all

Use this issue as a list of todos under the umbrella of UI for a 7.14 release.
the currently plan is to create a new button linking to the exploratory view from the standard apm view.
I'd really like to see some pre-defined exploratory-view settings, but it sounds like that might not be an options. We may need to write some docs on how to build exploratory views for recommended charts.

bug & other ui issues have been broken down into other tickets


Updated mixer config to bring in latest changes

Updated to get to 31948644cc53bb8569e4073486d7796540909adc from istio/istio
master branch.

@nrjpoddar: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_installer
e46c8f2d61d5723cac32429c8d1cc776be691db8
link
/test gencheck_installer

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nrjpoddar: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_installer
b8da4539ae434c86d2b2e11862964f0aa1925a70
link
/test gencheck_installer

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

I am not confident of the second commit that I added after running make gen.

@nrjpoddar: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_installer
7753e07a73d9078b608e3eb469e5410a1eda1b56
link
/test gencheck_installer

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

I am not confident of the second commit that I added after running make gen.

Scratch that, after regenerating them with BUILD_WITH_CONTAINER=1, change set looks more sane.

In response to a cherrypick label: #537 failed to apply on top of branch "release-1.3":
error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	istio-telemetry/mixer-telemetry/templates/config.yaml
Falling back to patching base and 3-way merge...
Auto-merging istio-telemetry/mixer-telemetry/templates/config.yaml
CONFLICT (content): Merge conflict in istio-telemetry/mixer-telemetry/templates/config.yaml
Patch failed at 0001 Updated mixer config to bring in latest changes

In response to a cherrypick label: new pull request created: #538

This does not need a 1.3 backport here, this was super experimental in 1.3 and has tons of bugs already

Thanks!


The whole code is not visible due to the bar below

The whole code is not visible due to the bar below

Duplicate of #1657


add Container.replace()

Presently there is parent_container.replace_child().
Should add Contaner.replace() to hide parent logic inside Container.
usage here, but should work regardless if a Container has a parent (is a root) or not:
https://github.com/ioxu/boxer/blob/9d16528a92268d7a1a3d71ae1c3dd886549bbb14/boxer/containers.py#L710
.replace_child() implemented here:
https://github.com/ioxu/boxer/blob/9d16528a92268d7a1a3d71ae1c3dd886549bbb14/boxer/containers.py#L184

change_container() is messy. This should help generalise.

.. cannot replace the root Container of course.

added .replace_by()
It's mostly to make utilising code shorter.
use
if container.parent is None:
    container.set_child( new_container, 0 )
else:
    container = container.replace_by( new_container )```

which is all very smelly.


martamap: fix config bools

@InTheDaylight14 Noticed some config fields weren't handled correctly when preparing to publish. Calling config.get() will give you a string value, so these won't be type bool by default.

Oh that's my bad. Thanks for the fix!


Theme selector with previous dark theme colors

Description
On staging, I noticed that after changing from system (default) to dark, the component kept showing the previous color scheme (dark pink shade).
Reproduction
https://github.com/user-attachments/assets/23888d27-182f-4c84-888c-a151be1e6251

Go to staging.openverse.org
On homepage's footer, click on the theme select
Select "Dark"
Click out of the component to unfocus
See the color mismatch

This is specific to Safari so I have reduced the priority to low.

@dhruvkb, why doesn't Safari store cookies? That would be a big problem for rendering, wouldn't it?

One more problem I can see in Safari: the select becomes white inside on the light mode.

I've also noticed it being pink in the dark (or system, I'm not sure now) mode in Arc, but I couldn't reliably reproduce it.

I have not observed this problem at all in Arc or Firefox but it does occur in Safari. That's because Safari does not handle click events on <select>. I've pushed a fix for Safari in PR #5216 to use focus event instead of click, which also works on other browsers.
As for the cookies, after debugging this for an entire day, all I could tell is that Safari is very finicky about cookies (in the name of privacy) and does not store any cookies for Openverse.org at all. It's receiving the cookies in the response, parsing them too but then discarding them instead of storing. I need to try this again without extensions to be certain it's not one my extensions that's responsible for this behaviour.


obesity classification

@khusheekapoor
i would like to work on this issue
this will classify obesity into different categories
the dataset i am gonna use is :- https://www.kaggle.com/datasets/sujithmandala/obesity-classification-dataset?select=Obesity+Classification.csv

@khusheekapoor
i would like to work on this issue
this will classify obesity into different categories
the dataset i am gonna use is :- https://www.kaggle.com/datasets/sujithmandala/obesity-classification-dataset?select=Obesity+Classification.csv
@khusheekapoor

Hello @khusheekapoor
I would like to work on this issue.
I will implement SVM, KNN and other classification algorithms to test the accuracy, and will select the one which is more accurate, and is good at generalization.

Hi, I would like to contribute o this issue. I'm eager to enhance MindWave with an obesity classification model using Python and ML.
Kindly consider assigning me this task. Looking forward to collaborate.

Hi, I'm super excited to be a part of the obesity classification project and contribute using ML models like SVM, Random Forest, and Neural Networks. With my experience in data science and ML, I'm confident in creating accurate models.
I'd be grateful if you could assign me this task so we can collaborate and make an impact on obesity classification.

@lcs2022026   - you can go ahead! We are assigning you 21 days for this project, after which it will be assigned to someone else if not completed. All the best!
Name the file as: algorithm_dataset.ipynb and link it in the readme of the labeled directory as algorithm - dataset.
@Saiesh-Agre @tushtithakur  - since we are following the first-come-first-serve policy, we will not be able to assign you this issue. However, you can create another issue on the similar lines.

@lcs2022026   - which algorithms will you be using?
SVM , logistic, Random Forest and I would pick the best one out of it

@khusheekapoor
I had completed my issue assigned to me - obesity classification
What I have to do next

@lcs2022026 - you can go ahead! We are assigning you 21 days for this project, after which it will be assigned to someone else if not completed. All the best!
Name the file as: algorithm_dataset.ipynb and link it in the readme of the labeled directory as algorithm - dataset.

@khusheekapoor
I had made a pull request
kindly have a look at it
and then merge it to main branch


It should be possible to set and monitor the authentication mode of SQL server with DSC

It is my understanding that the SQLsetup resource only sets stuff up but does not monitor them per #37. Among those settings there is the authentication mode which is a setting that appears in most database configuration standards
Right now, there doesn't seem to be a resource to set and monitor the setting after the database is configured for the first time

A suggestion is that we name this new resource either 'SqlServerSecurity', so it will be used to set everything on the Server Properties Security tab, or we name it 'SqlServerProperty' and used to set most single value properties on the Server Properties tabs.
Proposing how a start of a schema could look like, if a property is not assigned a value, the resource should not change that property. This schema is up for discussion.
[ClassVersion("<IP_ADDRESS>"), FriendlyName("SqlServerProperty")]
class MSFT_SqlServerProperty : OMI_BaseResource
{
    [Key, Description("Specifies the resource is a single instance, the value must be 'Yes'."), ValueMap{"Yes"}, Values{"Yes"}] String IsSingleInstance;
    [Write, Description("The SQL Server authentication mode."), ValueMap{"Windows Authentication", "SQL Server and Windows Authentication"}, Values{"Windows Authentication", "SQL Server and Windows Authentication"}] String AuthenticationMode;
    [Write, Description("The SQL Server login auditing."), ValueMap{"None", "Failed logins only", "Successful logins only", "Both failed and successful logins"}, Values{"None", "Failed logins only", "Successful logins only", "Both failed and successful logins"}] string LoginAuditing;
    [Write, Description("If server proxy account should be enabled or disabled. If this is set to $true then the property ServerProxyCredential must also be assigned the credentials to use.")] Boolean EnableServerProxyAccount;
    [Write, Description("The server proxy account to use. Only used if EnableServerProxyAccount is set to $true."), EmbeddedInstance("MSFT_Credential")] String ServerProxyCredential;
}

And seems these values are updated using
USE [master]
CREATE CREDENTIAL [##xp_cmdshell_proxy_account##] WITH IDENTITY = N'MyAccount', SECRET = N''
GO
EXEC xp_instance_regwrite N'HKEY_LOCAL_MACHINE', N'Software\Microsoft\MSSQLServer\MSSQLServer', N'LoginMode', REG_DWORD, 2
GO
EXEC xp_instance_regwrite N'HKEY_LOCAL_MACHINE', N'Software\Microsoft\MSSQLServer\MSSQLServer', N'AuditLevel', REG_DWORD, 1
GO

Labeling this as help wanted so that anyone in the community can run with this.

Sounds very similar to what SqlServerConfiguration already does and here I might be exposing how clueless i am about SQL server. Extending that module is out of the question?

You right, they are very similar. I think since SqlServerConfiguration is meant to change values set by sp_configure, and extending it with properties like credential parameters could be non-intuitive. But if we found a good way of extending SqlServerConfiguration I'm open for that.

The correct location for this registry entry is the following.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL13.SQL2016\MSSQLServer]
--
"LoginMode"=dword:00000002
"LoginMode"=dword:00000001

But can be set through
PS > $sql = New-Object -TypeName Microsoft.SqlServer.Management.Smo.Server -ArgumentList 'SQLTEST\SQLEXPRESS'
PS > $sql.Settings

AuditLevel            : Failure
BackupDirectory       : C:\Program Files\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQL\Backup
DefaultFile           : C:\Program Files\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQL\DATA\
DefaultLog            : C:\Program Files\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQL\DATA\
LoginMode             : Integrated
MailProfile           :
NumberOfLogFiles      : -1
PerfMonMode           : None
TapeLoadWaitTime      : -1
Parent                : [SQLTEST\SQLEXPRESS]
OleDbProviderSettings : {ADsDSOObject, MSDAOSP, MSDASQL, SQLNCLI11...}
Urn                   : Server[@Name='SQLTEST\SQLEXPRESS']/Setting
Properties            : {Name=AuditLevel/Type=Microsoft.SqlServer.Management.Smo.AuditLevel/Writable=True/Value=Failure
                        , Name=BackupDirectory/Type=System.String/Writable=True/Value=C:\Program Files\Microsoft SQL Se
                        rver\MSSQL14.SQLEXPRESS\MSSQL\Backup, Name=DefaultFile/Type=System.String/Writable=True/Value=C
                        :\Program Files\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQL\DATA\, Name=DefaultLog/Type=Syste
                        m.String/Writable=True/Value=C:\Program Files\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQL\DAT
                        A\...}
DatabaseEngineType    : Standalone
DatabaseEngineEdition : Express
ExecutionManager      : Microsoft.SqlServer.Management.Smo.ExecutionManager
UserData              :
State                 : Existing

PS > $s.Settings.LoginMode = [Microsoft.SqlServer.Management.SMO.ServerLoginMode]::Mixed
PS > $s.Settings.LoginMode = [Microsoft.SqlServer.Management.SMO.ServerLoginMode]::Integrated

Explaination of the login modes: ServerLoginMode

You are indeed correct. It is actually what I ended up testing the database with once i realized it was easier to just use the sqlserver powershell module for everything. Sorry, I should have updated this but now i am doing more important things such as looking for a new job
In your requirement list for this module, you do not specify that you need such powershell module installed in the database server however. You should do it because we love powershell and everything but it's not the default

Uf, the sqlserver powershell module is rather large. how will this behave when testing a lot of newly created databases?

@imarambiocatan I'm not following you now.


Make aggregations work for Logstash

Logstash puts the unanalyzed value for string fields in .raw , so to do aggregations on string fields we need to access the .raw property of the field instead of the field itself. Unfortunately, it doesn't do the same for numeric fields, so we have to access the field name itself to do aggregations on numeric fields. Until we design and implement some sort of schemas v5, the adapter will have no idea what fields are numbers and what are strings.
So, to make the situation better in the short term, let's guess that any group bys are on string fields, any min, max, sum, or avgs are on numeric fields, and any count_unique or count with an argument are on string fields. If you group by numeric_field, count_unique(numeric_field), or count(numeric_field), we'll return some unexpected output as ES will use 0 for all values of numeric_field on all your documents. I don't see a way to work around this or even detect it, since the values could really all be 0. This seems like enough of an edge case that we can document and live with it to get group by string_field working for Logstash.
@demmer @VladVega @dmehra @rlgomes @go-oleg

After some research into the behavior of Kibana, we've decided not to do magic like this. If you want to reduced by unanalyzed field values, you'll have to refer to .raw yourself, as Kibana requires. We'll add a read elastic -fields true option that will list the valid fields to reduce by, to make it easier to detect situations like this.


Export-DbaInstance Integration Test

Type of Change

[ ] Bug fix (non-breaking change, fixes #)
[ ] New feature (non-breaking change, adds functionality)
[ ] Breaking change (effects multiple commands or functionality)
[ ] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[x] Pester test is included
[ ] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

Purpose

Creating Integration Test for Export-DbaInstance.
Approach

Run Export-DbaInstance with a few parameters. Delete files after creating.
Commands to test

Invoke-Pester .\tests\Export-DbaInstance

on fire! 🔥 🚒  thank you so much!

Absolutely! Finally have some free time to write some test.


Change height of tabs

Hello,
Can anybody help me with this?
How cam i change the height of tabs?
Is it possible?
Thanks

Hi,
You can use your own style for every inner view of StepperLayout. You can checkout the sample app where a custom theme is used: https://github.com/stepstone-tech/android-material-stepper/blob/master/sample/src/main/res/values/styles.xml https://github.com/stepstone-tech/android-material-stepper/blob/master/README.md#stepperlayout-style-attributes
Alternatively, you can simply overwrite the default with the following dimen in your app:
<dimen name="ms_step_tab_height">72dp</dimen>

thanks very much, i solved

Hello zawadz88! I have found the answer. Thanks alot


Use double quotes for json in config docs

Summary

The configuration page of the docs is amazing, but I think there are some minor inconsistencies with how code is styled...
Code blocks
For the default values some of them are using rendering the value as code and some as plain text
Example of current state:

Double quotes
Most of the examples for config are using single quotes, but I guess that it is more common to have the Jest config in the package.json than in a separate js config file, right (I might be wrong)? Using double quotes makes it easier to just paste into a the package.json
Example of current state:

Test plan
The Markdown seems to render correctly, but I was not able to figure out how to build the docs and website to fully test it.

wow this is great! Thank you.


[iOS / Mac] The uicollectionviewcell is not being resized if the content resized

I have the expander as item of the list. when user taps on it it expands, but ios collectionview cell not and it cuts off the expander's content. you can reproduce it just for example setting visibility to the content of virtual viewcell

I have a branch started here but still playing with getting properly notified when the cell content actually changes size which is a bit illusive at the moment.

This one is harder to do on iOS than it seems.  I think what's happening is that the UICollectionView is trying to optimize by short circuiting layout changes the cell.  The way the MAUI interop between virtual and native views works for example is that changing the visibility on an item would cause the handler to set the visibility on the native control, which would then cause a layout invalidation on the native control, and that in turn causes the measure on the virtual view.  For this reason, the invalidation isn't happening when you make a change, and there's no simple way to infer when some MAUI view in the tree of the cell needs a layout pass, so we can't easily (automatically) wire up the invalidation of the particular cell that has changed.
I have a branch started that adds support on the adapter for invalidating specific item positions, which does provide a way to manually do this.  It's not obviously ideal, it would be lovely if it 'just worked' but I haven't found a reasonable way to wire that up yet.
In my branch there's an example where clicking a button is wired up to an event handler on the parent page of the VirtualListView and adds the ItemPosition as the Button.CommandParameter (from the VirtualViewCell's resource dictionary which gets that object assigned when the binding context changes if you nest your cell's view inside it) so you can call the adapter's UpdateItems(..) method passing that item position.
It's a bit clunky, but for now the reality seems to be if you are manipulating the views within a cell that is already displayed, after the binding context has already been set and the initial layout of the cell has happened, you will need to manually invalidate the item after doing so.

The same issue in maui's collectionview. But it worked well in xam forms.
Btw, maybe you saw the virtualizelistview implemented by my without native code using scrollview and absolute layout. So there item size change works as expected. You can find it in maui's github issue about performance of CV


Not a webpack bundle unhandled rejection on every chunk

Multi entry webpack 4 (latest) configuration on Node 14.
It does this for every chunk
errored out during transformation  Error: /Users/claudio/Projects/loom/js/404-3594367e1117c0d15bb5.js: Not a webpack bundle
    at mod (/Users/claudio/Projects/loom/node_modules/optimize-plugin/dist/worker.js:203:15)
    at /Users/claudio/Projects/loom/node_modules/optimize-plugin/dist/worker.js:211:9
    at Array.forEach (<anonymous>)
    at getWebpackModules (/Users/claudio/Projects/loom/node_modules/optimize-plugin/dist/worker.js:207:10)
    at getWebpackBootstrap (/Users/claudio/Projects/loom/node_modules/optimize-plugin/dist/worker.js:85:25)
    at /Users/claudio/Projects/loom/node_modules/optimize-plugin/dist/worker.js:256:29
    at Array.forEach (<anonymous>)
    at PluginPass.Program (/Users/claudio/Projects/loom/node_modules/optimize-plugin/dist/worker.js:255:26)
    at newFn (/Users/claudio/Projects/loom/node_modules/optimize-plugin/node_modules/@babel/traverse/lib/visitors.js:175:21)
    at NodePath._call (/Users/claudio/Projects/loom/node_modules/optimize-plugin/node_modules/@babel/traverse/lib/path/context.js:55:20) {
  type: 'Error',
  code: 'BABEL_TRANSFORM_ERROR'
}

Any pointers? 🙏

Hiya - this seems the same as the second issue mentioned in #7.
Are you able to share your Webpack configuration - in particular the mode, target and output options?

Awesome, thanks for this. I will try to set up a test case. I likely missed some bundle parsing cases for multi-entry since I avoid using multi-entry whenever possible for performance reasons.

Oh that's very interesting. I can intuitively understand why would it be a performance drain, do you have any links where I can learn more (multi entry webpack)? 🙏
I'll do some digging of my own in the meanwhile :)

@keepitterron it's a little buried in the docs, but there now:
https://webpack.js.org/plugins/module-concatenation-plugin/#optimization-bailouts

We bundle multiple separate 'apps' so we definitely need multiple entries, not something we can avoid unfortunately.

For those hitting this issue, you can disable automatic modernization via new OptimizePlugin({ modernize: false }). This improves performance, but will use the unmodified ES5 source of most npm modules since they do not publish modern code.


support mix_mode in dt_workload

What problem does this PR solve?
Issue Number: ref #3594
Problem Summary: Need support mix_mode in dt workload.
What is changed and how it works?
Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/merge

/run-unit-tests

/run-unit-test

/merge


[Bug]: asset processing broken in production with unicode private area codes

System Info
System: Windows
rspack 1.1.0
It's a doozy.
Here's a repro: https://github.com/Narretz/rspack-sass-asset-bug
run npm run build:rspack.
Go to localhost:8085
You can see that in the scss div, there are not background images, because
the url is still url(../assets/leading.svg) (the asset was not processed).
In the css div, it works.
If you run npm run build:webpack, it works in both.
Details
the problem is this css:
body {
  content: var(--some-var, "\f101");
}

The private use area unicode breaks the asset processing.

if you set the unicode as value of content, it works (bug is in variabel parsing somewhere?)
If you move the block after the asset, it works
if you use other unicode values, like emojis, it also works
if the rspack mode is "development" it also works
works in webpack

These private unicode areas are widely used in ag-grid:
https://github.com/ag-grid/ag-grid/blob/3930d31b4e0f7db83a9a427b151ecb0a52da210d/packages/ag-grid-community/styles/_icon-font-codes.scss#L5
Reproduce link
https://github.com/Narretz/rspack-sass-asset-bug
Reproduce Steps
run npm run build:rspack.
Go to localhost:8085
You can see that in the scss div, there are not background images, because
the url is still url(../assets/leading.svg) (the asset was not processed).
In the css div, it works.

Thank you for the detailed description of the issue. After looking into it, I found that the problem is not related to Sass; it can be reproduced with this line of CSS: body{content: "\f101";background-image:url(./img.png)}. This might be related to the lexer.

Thanks for the quick response!

it can be reproduced with this line of CSS: body{content: "\f101";background-image:url(./img.png)}.

Interesting!

Founded something like that issue with @atomaro/icons package.
In Windows only. Correctly works in MacOS
  × Module not found: Can't resolve './Сookie' in
     ╭─[552:15]
 550 │   }
 551 │ });
 552 │ var _ookie_1 = require("./\u0421ookie");
     ·                ────────────────────────
 553 │ Object.defineProperty(exports, "\u0421ookie", {
 554 │   enumerable: true,
     ╰────

script route is not normalized, but something normalizes that

Not related, @kentets4 please submit a new issue and provide reproduction


Add upload snapshot to cloud feature for ceph driver

What this PR does / why we need it:
Add upload snapshot to cloud feature for ceph driver
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:

Coverage remained the same at 28.363% when pulling cd5d732125a9ff4b6ac1b441d159a3dbc43c46aa on xxwjj:upload_snapshot into e89d884504493ab0216e16fdc151150ea8211566 on opensds:development.


Task 29

@SunkireddyRagini
Task -29
Code verified.
Task -30
Code verified.
Task -31
Code verified.
Task -32
Code verified.
Task -33
Code verified.


Add designs for public catalogue

Signed-off-by: ashish<EMAIL_ADDRESS>Description
This PR fixes #
Notes for Reviewers
Signed commits

[ ] Yes, I signed my commits.

🚀 Preview for commit ac0f085963a0245bbe6699a1d0b5096de61fdc33 at: https://631883b336cc9c29bff528c7--service-mesh-patterns.netlify.app