Feature/235 formats api structure

Many changes, including:

New export API under thoth-export-api (closes #235 and closes #101 )

with swagger schema autogeneration using paperclip
relational schema as Format -> Specification <- Platform
Each specification can be output for both a single Work or all of a Publisher's works

Restructure of thoth-client

It now needs to be instantiated instead of calling the static methods
Both queries are now using a graphql fragment to unify the Work output, making WorkQuery::Work the canonical one

Update yew to newest version
Update actix-web to newest version
Use a custom instance of graphiql

Left to do:

export caching
Implementation of the export API in the APP (dynamically querying the available specifications and list them in the catalogue)

Additional changes all look fine - if you want to merge now and improve the handling of works with no PDF URL as a separate issue, I'd be happy with that.

I had something working already, so I've pushed https://github.com/thoth-pub/thoth/pull/251/commits/2bcf9df1c7f2813d05b3692e2eea13f3ce15da26


Nearest neighbor upsampling stretching image

Images are being stretched when resized with sharp.kernel.nearest, however the stretching only happens when the resolution is not an exact scale like 8 (1), 16 (2), or 24 (3).
Exact scale (x32) with kernel nearest:

Non exact scale with kernel nearest:

Non exact scale with default kernel:

Hello, please can you share the input image and (standalone) code sample.

Here's the original image:

And here's the code:
const imageBuffer = /* ... */;
const size = 250; // causes stretching

const avatar = await sharp(imageBuffer).extract({
  left: 8,
  top: 8,
  width: 8,
  height: 8
}).resize({
  width: size,
  height: size,
  kernel: sharp.kernel.nearest
}).png().toBuffer();

Hello, should be fixed in git master, thanks for the report! It was to do with the way centre vs. corner sampling is implemented.
With this 3x3 pixel PNG:

If I run:
$ vips resize 3x3.png 3x3-nearest.png 83.33333333333 --kernel nearest
$ vips resize 3x3.png 3x3-cubic.png 83.33333333333

I now see:

Thanks @jcupitt !

sharp v0.23.0 / libvips v8.8.1 is now available. Thanks for reporting this @edwjusti.


update Compatibility matrix

The Compatibility matrix is incomplete and includes an incorrect statement. This PR fix this.
It didn't mention RTRlib (https://github.com/rtrlib/rtrlib/), which is a C library implementing the RTR protocol. Part of the software package is the rtrclient, which dumps valid ROA payloads, similar to RTRdump.
RPKI support in FRRouting and BIRD is based on RTRlib. Currently, SSH transport in the RTRlib only allows for key-based authentication. As such, FRRouting does not support password-based SSH but key-based SSH.
Password-based SSH authentication will be available soon, see https://github.com/rtrlib/rtrlib/issues/250.

Thank you @waehlisch :)
I quickly capitalized the "no" but apart from that, it's good.


Wrap images in links

Same as #322 but Im using api push to dynamically generate galleries. Is there a way to use data-href and data-link as that author originally asked or some other solution?

I think this solution should be in the official documentation :)

Hey guys... testing in Windows Phone Internet Explorer it doesn't work. Any help?

@artpolikarpov Can someone please add the fix to the documentation?  I spent a long time trying to resolve this issue, either way nice work on the slider.


docs(Algebra/MonoidAlgebra/Basic): fix order of arguments in docs

The arguments to AddMonoidAlgebra were reversed with respect to normal use in the module docs.  They also used α instead of R.  For reference, these are the actual definitions:
-- Data/MvPolynomial/Basic
def MvPolynomial (σ : Type*) (R : Type*) [CommSemiring R] :=
  AddMonoidAlgebra R (σ →₀ ℕ)

-- Data/Polynomial/Basic
structure Polynomial (R : Type*) [Semiring R] where ofFinsupp ::
  toFinsupp : AddMonoidAlgebra R ℕ

Thanks!
bors merge


  Also re-enabled the tab that allows users to see sub-organizations.
Breadcrumbs are updated to be the parent of the current organization allowing the user to traverse back through the organizations no matter how deep they may be.
💭 Motivation and context
This allows the user to access the sub-organization tab and allows users to navigate from the organization page to the parent via a breadcrumb link
🧪 Testing
Manual testing:

Login to Crossfeed
Navigate to My Organizations under the user icon
There should be a Sub-Organizations tab at the top.
Click the Sub-Organization tab to go to the Sub-organization screen that show all the organization's children shown

📷 Screenshots (if appropriate)

## ✅ Pre-approval checklist ##

[X] This PR has an informative and human-readable title.
[X] Changes are limited to a single goal - eschew scope creep!
[X] All future TODOs are captured in issues, which are referenced
in code comments.
[X] All relevant type-of-change labels have been added.
[X] I have read the CONTRIBUTING document.
[X] These code changes follow cisagov code standards.
[X] All relevant repo and/or project documentation has been updated
to reflect the changes in this PR.

✅ Pre-merge checklist

[ ] Revert dependencies to default branches.
[ ] Finalize version.

✅ Post-merge checklist

[ ] Create a release.

Can we rename "Sub-Organization" to "Suborganization"?

@lfilip-ivaal can you also include screenshots of the breadcrumbs?

The second screen shot shows what the bread crumbs look like at the top. The parent is clickable and will navigate the user to the parent organization.

@lfilip-ivaal can you also include screenshots of the breadcrumbs?

The second screen shot shows what the bread crumbs look like at the top. The parent is clickable and will navigate the user to the parent organization.

Thanks. Two things:

I don't see in this PR where the breadcrumbs is implemented, can you point me to the code point? or is there some code you need to push?
We should ensure that the breadcrumb is not clickable for users who don't have access to a particular organization. (or maybe for now we just make it not clickable for people who are not global view / global admins). Otherwise, regular Crossfeed users may click on the breadcrumb to try to navigate (for example, they may click "Federal" / "FCEB") and just get an error message and get confused.

Hi @lfilip-ivaal , should we get this PR in soon?


I can not install ta with pip help plss

Hey this is the error I get, would be really happy if someone can help me, thankss
Collecting ta
Using cached https://files.pythonhosted.org/packages/ba/09/149cb10cbd6b98cbcbaa6f74169b4f1f2ce6df144335bea0df0eaa9e1b01/ta-0.4.2.tar.gz
Complete output from command python setup.py egg_info:
Traceback (most recent call last):
File "", line 1, in
File "/private/var/folders/hc/b2dnskds513b2dxjnv8m3g_40000gn/T/pip-install-ceehcvvi/ta/setup.py", line 14, in
install_requires=open('requirements.txt').readlines(),
FileNotFoundError: [Errno 2] No such file or directory: 'requirements.txt'

Fixed on 0.4.3 version.
Try again, please.


[Go Live][3 Feb]

Pushing RSC and manifest 1.12 to live

Docs Build status updates of commit b286135:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/apps-in-teams-meetings/API-references.md
:white_check_mark:Succeeded
View

msteams-platform/apps-in-teams-meetings/create-apps-for-teams-meetings.md
:white_check_mark:Succeeded
View

msteams-platform/apps-in-teams-meetings/design/designing-apps-in-meetings.md
:white_check_mark:Succeeded
View

msteams-platform/apps-in-teams-meetings/enable-and-configure-your-app-for-teams-meetings.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/rsc/resource-specific-consent.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/rsc/test-resource-specific-consent.md
:white_check_mark:Succeeded
View

msteams-platform/resources/schema/manifest-schema-dev-preview.md
:white_check_mark:Succeeded
View

msteams-platform/resources/schema/manifest-schema.md
:white_check_mark:Succeeded
View

msteams-platform/whats-new.md
:white_check_mark:Succeeded
View

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


AnimateCommand detail added

Docs for Toolkit PR #1180
PR: https://github.com/xamarin/XamarinCommunityToolkit/pull/1180
Feature: https://github.com/xamarin/XamarinCommunityToolkit/issues/1175
What changes to the docs does this PR provide?

Added in detail about the new AnimateCommand property on the AnimationBehavior class.
PR Checklist
Please check if your PR fulfills the following requirements:

[ ] For new pages, used the provided template.
[ ] For new features, added an entry in the Table of Contents.
[x] Ran against a spell and grammar checker.
[x] Contains NO breaking changes.

Other information

Docs Build status updates of commit 67f7f71:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/behaviors/animationbehavior.md
:white_check_mark:Succeeded
View

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


Adding instruction to set auth token

Its a bit problematic as instructions to set the auth token is missing from the doc. It would be helpful if instructions are provided in the same tutorial

LGTM, thanks!


Safeguard private keys

In your latest video, around 22:30, you talk about private keys being stored in plain text. Is there any safe and ethical way for this mod to safeguard those, if Mojang will not fix it for 1.19.1 release?

Really, that simple? How would the client sign the messages for servers that require it then?

It will just get keypair from authentication services on every startup. It already does that when keypair is not yet cached, the only difference caching makes is that client doesn't have to communicate with authentication services to obtain those keys every time it loads.

This is no longer necessary as key caching was removed in pre-release 6.


Missing pre-req pygame?

Hi there,
I have the hardware, and I would like to build the USB part of this, but I can't find this any more: http://bitbucket.org/pygame/pygame do you have a copy of it you could host?

hey, have you tried pip install pygame? the code is now some years old, maybe the pygame issue has been fixed now.


Fix relative path docker db script

Without this, docker complained:
docker: Error response from daemon: create ./postgres-data: "./postgres-data" includes invalid characters for a local volume name, only "[a-zA-Z0-9][a-zA-Z0-9_.-]" are allowed. If you intended to pass a host directory, use absolute path.

Followed recommendation from https://stackoverflow.com/questions/46526165/docker-invalid-characters-for-volume-when-using-relative-paths

Thanks for the PR @araffin!


Feature/location info (#9)

Show comma-separated city, state and country in infobox and in gallery mode. All of the values that are non-empty will be shown.

Before:

After:

A matter of taste perhaps. I thought with the nice searchable data, it might also be displayed. Especially in places like the USA where the state is rather important info. For example: Beverly Hills exist in 5 different states, not only the one in California :)

Thanks!


Empty tasks

It's possible to create empty tasks by not typing anything in when creating tasks. Can't be deleted without deleting cookie.

Hey, nice catch. I'll release a set of bug fixes and few changes in couple of hours, thanks for raising this issue. Totally missed out on the validations part.

Patched for now, will get some validation in the place soon. Closing for now!
Thanks :)


An error occurred during the push operation: Could not find a schema at /home/user/projectName/amplify/backend/api/appSyncApiName/schema.graphql

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?
No response
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
7.6.14
What operating system are you using?
Mac, Windows and Ubuntu
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No
Amplify Categories
api, hosting
Amplify Commands
publish, push
Describe the bug
The project has no backend or schema definition of its own, it uses manual hosting. The types are generated using amplify codegen of types from another appsync API using amplify codegen (script used as codegen unfortunetly does not have headless support ):
#!/usr/bin/expect -f

set timeout -1
spawn amplify add codegen --apiId "$env(API_ID)"
expect "target"
send "\033\[B"
send "\r"
expect "ts)"
send "\r"
expect "(Y/n)"
send "n\r"
expect "(src/API.ts)"
send "\r"
expect "(Y/n)"
send "\r"
expect eof

Since we upgraded to this amplify version, the amplify publish commands (and amplify push) give the following error:
(base) user@DESKTOP-EI7Q1CL:~/projectName$ amplify publish --yes
✖ There was an error pulling the backend environment dev.
🛑 An error occurred during the push operation: Could not find a schema at /home/user/projectName/amplify/backend/api/appSyncApiName/schema.graphql`

If we generate an empty file manually then the command succeeds.
mkdir -p amplify/backend/api/appSyncApiName && touch amplify/backend/api/appSyncApiName/schema.graphql
(base) user@DESKTOP-EI7Q1CL:~/projectName$ amplify publish --yes
✔ Successfully pulled backend environment dev from the cloud.

    Current Environment: dev

┌──────────┬────────────────┬───────────┬───────────────────┐
│ Category │ Resource name  │ Operation │ Provider plugin   │
├──────────┼────────────────┼───────────┼───────────────────┤
│ Api      │  projectName   │ Create    │                   │
├──────────┼────────────────┼───────────┼───────────────────┤
│ Hosting  │ amplifyhosting │ No Change │ awscloudformation │
└──────────┴────────────────┴───────────┴───────────────────┘
✔ All resources are updated in the cloud

GraphQL transformer version: 1

Publish started for amplifyhosting

><EMAIL_ADDRESS>build
> craco build

Creating an optimized production build...
Compiled successfully.

File sizes after gzip:

  1.62 MB    build/static/js/2.ca3ea0ff.chunk.js
  300.26 KB  build/static/js/main.b8facb9b.chunk.js
  4.94 KB    build/static/css/2.b53d0174.chunk.css
  772 B      build/static/js/runtime-main.776c1e0d.js
  323 B      build/static/css/main.b1bc96b3.chunk.css

The bundle size is significantly larger than recommended.
Consider reducing it with code splitting: https://goo.gl/9VhYWB
You can also analyze the project dependencies: https://goo.gl/LeUzfb

The project was built assuming it is hosted at /.
You can control this with the homepage field in your package.json.

The build folder is ready to be deployed.
You may serve it with a static server:

  npm install -g serve
  serve -s build

Find out more about deployment here:

  https://cra.link/deployment

✔ Zipping artifacts completed.
✔ Deployment complete!
https://dev.xxx.amplifyapp.com

Trying with 7.6.7 was also working.
Expected behavior
The amplify publish --yes commands runs normally with no errors
Reproduction steps
use amplify publish on a minimal project with types generated from another API.
GraphQL schema(s)

# Put schemas below this line

Log output

# Put your logs below this line

Additional information
Environment information
Bug appears on Windows and Mac with same Amplify version

  System:
    OS: Linux 4.19 Ubuntu 20.04.3 LTS (Focal Fossa)
    CPU: (24) x64 AMD Ryzen 9 3900X 12-Core Processor
    Memory: 21.17 GB / 25.00 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 16.13.1 - ~/.nvm/versions/node/v16.13.1/bin/node
    Yarn: 1.22.5 - /mnt/c/Program Files (x86)/Yarn/bin/yarn
    npm: 8.1.2 - ~/.nvm/versions/node/v16.13.1/bin/npm
  npmPackages:
    @apideck/file-picker: https://github.com/Conova-ai/file-picker/tarball/master => 0.6.0
    @auth0/auth0-spa-js: ^1.14.0 => 1.19.3
    @aws-amplify/analytics: ^4.0.17 => 4.0.22
    @aws-amplify/api: ^3.2.29 => 3.3.3
    @aws-amplify/auth: ^3.4.29 => 3.4.34 (3.4.21)
    @aws-amplify/core: ^3.8.21 => 3.8.24 (3.8.13)
    @aws-amplify/interactions: ^3.3.29 => 3.3.34 (3.3.21)
    @aws-amplify/storage: ^3.3.29 => 3.4.4 (3.3.21)
    @aws-amplify/ui-react: ^0.2.38 => 0.2.38
    @aws-amplify/xr: ^2.2.29 => 2.2.34 (2.2.21)
    @aws-sdk/client-s3: ^3.49.0 => 3.49.0 (3.6.1, 1.0.0-rc.4)
    @conova/coach-ui-library: ^1.45.1 => 1.45.1
    @craco/craco: 6.2.0 => 6.2.0
    @graphql-tools/graphql-file-loader: ^7.1.0 => 7.3.3
    @graphql-tools/load: ^7.3.2 => 7.5.1
    @material-ui/core: ^4.11.0 => 4.12.3
    @material-ui/icons: ^4.11.2 => 4.11.2
    @material-ui/lab: ^4.0.0-alpha.56 => 4.0.0-alpha.60
    @microsoft/file-browser: ^1.0.0-preview.0 => 1.0.0-preview.0
    @microsoft/microsoft-graph-client: ^3.0.0 => 3.0.1
    @stripe/stripe-js: ^1.15.0 => 1.22.0
    @testing-library/dom: ^7.30.2 => 7.31.2 (6.16.0)
    @testing-library/jest-dom: ^4.2.4 => 4.2.4
    @testing-library/react: ^9.3.2 => 9.5.0
    @testing-library/user-event: ^7.1.2 => 7.2.1
    @types/chrome: 0.0.133 => 0.0.133
    @types/dompurify: ^2.2.2 => 2.3.2
    @types/dotenv: ^8.2.0 => 8.2.0
    @types/google.picker: 0.0.39 => 0.0.39
    @types/jest: ^24.9.1 => 24.9.1
    @types/lodash: ^4.14.165 => 4.14.178
    @types/material-ui: ^0.21.8 => 0.21.12
    @types/node: ^12.20.7 => 12.20.41
    @types/react: ^16.14.5 => 16.14.21
    @types/react-dom: ^16.9.12 => 16.9.14
    @types/react-helmet: ^6.1.0 => 6.1.5
    @types/react-phone-number-input: ^3.0.6 => 3.0.13
    @types/react-router-dom: ^5.1.5 => 5.3.2
    @types/segment-analytics: 0.0.33 => 0.0.33
    aws-amplify: ^3.3.26 => 3.4.3
    aws-amplify-react: ^4.2.30 => 4.2.35
    aws-appsync: ^4.0.3 => 4.1.4
    axios: ^0.21.1 => 0.21.4 (0.24.0, 0.21.1)
    chai: ^4.3.4 => 4.3.4
    cross-var: ^1.1.0 => 1.1.0
    dompurify: ^2.2.9 => 2.3.4
    dotenv: ^8.2.0 => 8.6.0 (8.2.0)
    dotenv-cli: ^4.0.0 => 4.1.1
    email-validator: ^2.0.4 => 2.0.4
    example:  1.0.0
    file-type: ^16.5.3 => 16.5.3
    form-data: ^4.0.0 => 4.0.0 (3.0.1)
    gapi-script: ^1.2.0 => 1.2.0
    graphql: ^15.6.0 => 15.8.0 (14.0.0)
    graphql-tag: ^2.11.0 => 2.12.6
    graphql-tools: ^8.2.0 => 8.2.0
    graphql-tools/es5:  8.2.0
    husky: ^4.3.8 => 4.3.8
    i18next: ^19.9.2 => 19.9.2
    i18next-browser-languagedetector: ^6.1.0 => 6.1.2
    i18next-http-backend: ^1.2.1 => 1.3.1
    jwt-decode: ^3.1.2 => 3.1.2
    lint-staged: ^10.5.4 => 10.5.4
    lodash: ^4.17.21 => 4.17.21
    mocha: ^9.1.2 => 9.1.3
    moment: ^2.29.1 => 2.29.1
    prettier: ^2.2.1 => 2.5.1
    query-string: ^6.14.1 => 6.14.1 (4.3.4)
    react: ^16.14.0 => 16.14.0
    react-dom: ^16.14.0 => 16.14.0
    react-dropzone: ^11.4.2 => 11.4.2
    react-google-drive-picker: ^1.1.4 => 1.1.4
    react-helmet: ^6.1.0 => 6.1.0
    react-i18next: ^11.8.12 => 11.15.3
    react-infinite-scroll-component: ^5.1.0 => 5.1.0
    react-intersection-observer: ^8.32.0 => 8.33.1
    react-moment: ^1.1.1 => 1.1.1
    react-onedrive-filepicker: ^0.1.3 => 0.1.3
    react-phone-number-input: ^3.1.22 => 3.1.45
    react-phone-number-input-core:  1.0.0
    react-phone-number-input-flags:  1.0.0
    react-phone-number-input-input-core:  1.0.0
    react-phone-number-input-input-max:  1.0.0
    react-phone-number-input-input-min:  1.0.0
    react-phone-number-input-input-mobile:  1.0.0
    react-phone-number-input-max:  1.0.0
    react-phone-number-input-min:  1.0.0
    react-phone-number-input-mobile:  1.0.0
    react-phone-number-input/react-hook-form:  1.0.0
    react-phone-number-input/react-hook-form-core:  1.0.0
    react-phone-number-input/react-hook-form-input:  1.0.0
    react-phone-number-input/react-hook-form-input-core:  1.0.0
    react-phone-number-input/react-native-input:  1.0.0
    react-router-dom: ^5.2.0 => 5.3.0
    react-schemaorg: ^1.2.0 => 1.3.3
    react-scripts: 4.0.3 => 4.0.3
    sass: ^1.44.0 => 1.46.0
    schema-dts: ^0.7.1 => 0.7.4
    typescript: ^3.8.0 => 3.9.10
  npmGlobalPackages:
    @aws-amplify/cli: 7.6.14
    corepack: 0.10.0
    npm: 8.1.2

@charlesdarkwind Thanks for the issue, does a file called .graphqlconfig.yml get generated and can you share its contents?
I am unable to reproduce with 7.6.15

@ammarkarachi sure, here is the file
projects:
  projectName-env:
    schemaPath: src/graphql/schema.json
    includes:
      - src/graphql/**/*.ts
    excludes:
      - ./amplify/**
    extensions:
      amplify:
        codeGenTarget: typescript
        generatedFileName: src/API.ts
        docsFilePath: src/graphql
        region: ca-central-1
        apiId: AppSyncApiID

@charlesdarkwind Thanks for the prompt reply. The issue stems from the absence of this flag. If you add this to your amplify/cli.json
{
  "features": {
    "graphqltransformer": {
      "addmissingownerfields": true,
      "improvepluralization": false,
      "validatetypenamereservedwords": true,
      "useexperimentalpipelinedtransformer": true,
      "enableiterativegsiupdates": true,
      "secondarykeyasgsi": true,
      "skipoverridemutationinputtypes": true,
      "transformerversion": 2,
      "suppressschemamigrationprompt": true,
--->"securityenhancementnotification": false
    },
...
}

Should unblock you in the mean time we work on fixing this bug.

@ammarkarachi Thanks, I confirm that this flag fixes the problem.

I tried to add this flag but it didn't fix the issue for me

@charlesdarkwind Thanks for the prompt reply. The issue stems from the absence of this flag. If you add this to your amplify/cli.json
{
  "features": {
    "graphqltransformer": {
      "addmissingownerfields": true,
      "improvepluralization": false,
      "validatetypenamereservedwords": true,
      "useexperimentalpipelinedtransformer": true,
      "enableiterativegsiupdates": true,
      "secondarykeyasgsi": true,
      "skipoverridemutationinputtypes": true,
      "transformerversion": 2,
      "suppressschemamigrationprompt": true,
--->"securityenhancementnotification": false
    },
...
}

Should unblock you in the mean time we work on fixing this bug.

For me, the following flag was the one that workaround the problem
"showfieldauthnotification": false
"features": {
    "graphqltransformer": {
    "addmissingownerfields": true,
    "improvepluralization": false,
    "validatetypenamereservedwords": true,
    "useexperimentalpipelinedtransformer": true,
    "enableiterativegsiupdates": true,
    "secondarykeyasgsi": true,
    "skipoverridemutationinputtypes": true,
    "transformerversion": 2,
    "suppressschemamigrationprompt": true,
    "securityenhancementnotification": false,
--->"showfieldauthnotification": false
},

How long does the fix take to be merged into the amplify-cli after it's complete? I updated to 7.6.22 but still seeing the error.


Ability to fetch processed data correctly RecruitmentUsersWithoutInterviewGangPage

The information in the right most column ("Processed") is not updating.
It should be updated when recruiters set the priority of the application to anything
else than "Not set". Remember this is for the whole recruitment!
There is very similar functionality which works here: "http://localhost:3000/control-panel/recruitment/1/gang/10"

https://github.com/Samfundet/Samfundet4/pull/1592


editBox.SendKeys(TextValue) in localolized OS (FRA) send US keys

Hello,
I have tried on my FRA system the notepad sample, and the sent text in the edit is incorrect.
As you can see hereafter, the text is displayed in "Bloc-notes" as This is qn quto,qted test on Clqssic Windozs Applicqtion!09:25 28/12/2016

Regards.

The device where the tested app is running needs to be set to US keyboard layout per the json wire protocol spec:
https://github.com/SeleniumHQ/selenium/wiki/JsonWireProtocol#sessionsessionidelementidvalue


Update check_pip_licenses

Still trying to figure out why pathable is having an issue with the license, since it uses apache 2, and this License type is allowed.
Nevertheless, I think we are save to ignore it for now.

❤ 🚀


TypeScript doesn't recognize esm exports of this package

Describe the bug A clear and concise description of what the bug is.
I am using "module": "Node16" in my tsconfig.json which also implies "moduleResolution": "Node16". The "Node16" module resolution needs to identify this package as an ESM compatible module to be able to handle the exports type correctly.
However, because this package doesn't have a "module": "..." field the "Node16" module resolution recognizes this package as a CommonJS module, which causes all exports to be named, including the default exports.
So in my case, this happens:
import EntryShakingPlugin from 'vite-plugin-entry-shaking';

// This expression is not callable.
//  Type 'typeof import(".../node_modules/vite-plugin-entry-shaking/dist/index")' has no call signatures.
await EntryShakingPlugin(...);

// Type-checking succeeds, runtime does not.
await EntryShakingPlugin.default(...),

// I get the same when doing:
import { default as EntryShakingPlugin } from 'vite-plugin-entry-shaking';
await EntryShakingPlugin(...);

// And:
import EntryShakingPlugin from 'vite-plugin-entry-shaking';
await EntryShakingPlugin.default(...);

To Reproduce Steps to reproduce the behavior:

Create a tsconfig.json with "module": "Node16".
Try importing the default export.

Expected behavior A clear and concise description of what you expected to happen.
The package should include a "module": "..." field in order for TypeScript to recognize the package as an ESM module.
Alternatively, or additionally, export EntryShakingPlugin as a named export in addition to the default export. This also improves other aspects too. See https://basarat.gitbook.io/typescript/main-1/defaultisbad.
Additional context Add any other context about the problem here.
I am happy to contribute with a pull request, if requested.

I accidentally posted the issue when it was incomplete. I edited the issue after posting it. If you are reading from email, it might not be up to date. Sorry for any incontinence.

As I mentioned in #21, I went down the wrong rabbit hole.  I am closing this issue but leaving #22 open if it is wanted.


feat: #36 upgrade dependencies

Currently I'm waiting for Chrome 79 support through protractor and webdriver-manager.

Part of #40


Improve error management when scanning chunks

Is your feature request related to a problem? Please describe.
Following issue #391 : I realized that the error message was not perfectly accurate.
GGshield displays a network error occurred. This is kind of true as this happens while interacting with the API, but on the other hand, the user might think of a lower level network error.
Describe the solution you'd like
When sending a filename that is too long to the API, we get a status_code 400 with a code max_length. We could adapt the output of ggshield for this case, and perhaps for other ones ?
Additional context
Also, I am a bit puzzled by why the status_code is None at that point.

Revisiting this issue: ggshield used to rely on the filename to match a scan with its result, but it's no longer the case since #435, so we should be able to only set a filename in this field, as initially intended.


Funny scrollbar behavior

The vertical scrollbar moves up and down by itself.
The horizontal scrollbar appears and disappears.
I've only seen this behavior happen in Firefox 80.0.1 (64-bit)

Good catch, thanks! It was the infinite load spinner animation causing that :)

Good catch, thanks! It was the infinite load spinner animation causing that :)


Operator should be lte and gte

Here the operators are defined as le and ge.
The spec defines these as lte and gte.

Fixed in pgstac backend via #185; sqlalchemy backend still needs this fix.


toString() does not work as expected on a mock object

This one is not a "bug" exactly but just annoying when trying to figure out what is going on.
While trying to figure out what was going on with #191 I added some print statements to my code (and eventually the ts-mockito code). Yes, I solved both this one and #191 with print statements. Old-school for the win?
Some of the print statements I added with like this:
  const mocked = mock(Foo)
  const foo = instance(mocked)
  console.log(`Got a foo: ${foo}`)

Imagine my surprise when I got this:
  Got a foo: null

When I saw this I figured I had put the wrong thing in the expression, so I checked but it was right. I was in the middle of trying to figure out why #191 was not working so I actually had the thought "wow, they figured out how to attach a mock to a null value. That's kinda cool" and then I went on.
At some point I realized that you couldn't have added methods to null (this was on day 2, I was tired and distracted by the other problem) so I started adding print statements to Mock.js and found that there was an actual object but by the time it got to my code it was null. It wasn't my main problem, so I ignored it again.
Eventually, I added a print statement to Mock.js/ts that displayed the name of the property being retrieved from the mock Proxy and I saw this:
  name = 'Symbol(Symbol.toPrimitive)'

I thought that was strange so I looked it up and...Doh!...there it was. Of course, the object I got wasn't null, we were retrieving the Symbol.toPrimitive value from the mock, which was mocked, so we got a weird answer back (in this case null).
So I added Symbol(Symbol.toPrimitive) to the list of names I had for #191 and suddenly my print statements were displaying [object Object] like they should, Huzzah!
So I propose that Symbol(Symbol.toPrimitive) be in the defaulted list in #192 (assuming that #192 is accepted) so that anyone following won't get the same weird null value when printing a mock for a debug statement. It's not really important, but it did slow me down in debugging #191.

Hey, with this code:
  const mocked = mock(Foo)
  const foo = instance(mocked)
  console.log(`Got a foo: ${foo}`)

I get:
function () {
                var args = [];
...
...
...

Not the null

You know, I wrote this wrong. Doh!
This only happens when it's an interface so the first line of the example should have been:
const mocked = mock<Foo>()

Sorry about that. I was trying to do two things at the same time.


Great cogs

Nice cogs but the lolz cog + the slots in the economy cog = no slot images
Maybe make the lolz cog ignore slots?

could make it ignore :emojis:

Sounds cool

b915713

lolz also is available in PM now
for you creepy people that like talking to my bot in PM.
I see you >.>


Refactor getFormat pattern and ordering for speed

Even though 31c6a32 added caching to make this method less of a
hotspot, there's no reason to use a pattern which is an order of
magnitude slower (https://jsperf.com/pokemon-showdown-getEffect).
Also, rearranges Format to get checked first as pkmn.cc/optimize
finds it to be the most frequently accessed.

I find it weird that V8 doesn't optimize this pattern, seems like a simple optimization, but I guess that's what you get with peephole optimization. The movement of formats to be the first makes sense, considering most formats have clauses, and they are always present.

!!!!
We use hasOwnProperty because keys like constructor would crash the code!

>> Dex.data.Formats['constructor']
  << function Object() { [native code] }
>> Dex.data.Formats.hasOwnProperty('constructor')
  << false


GraphicsPath.AddString is wrongly positioned on linux?

I am currently writing a .NET Core 2.0 App to run cross-platform. Part of this is App is Drawing a Text and overlay onto a Bitmap.
So I added the latest System.Drawing.Common and finally ended up with a working Code(On Windows) like this:
public static Bitmap WriteText(Bitmap bmp, string txt)
{
    RectangleF rectf = new RectangleF(0, 0, bmp.Width, bmp.Height);

    // Create graphic object that will draw onto the bitmap
    using (Graphics g = Graphics.FromImage(bmp))
    {
        g.SmoothingMode = SmoothingMode.AntiAlias;
        g.InterpolationMode = InterpolationMode.HighQualityBicubic;
        g.PixelOffsetMode = PixelOffsetMode.HighQuality;
        g.TextRenderingHint = TextRenderingHint.AntiAliasGridFit;
        StringFormat format = new StringFormat()
        {
            Alignment = StringAlignment.Center,
            LineAlignment = StringAlignment.Center
        };
        // dampening
        using (Brush brush = new SolidBrush(Color.FromArgb(69, Color.Black)))
            g.FillRectangle(brush, rectf);

        var fSize = 26;
        var fFam = Fonts.GetDefaultFontName();
        // Draw the path
        GraphicsPath p = new GraphicsPath();
        p.AddString(txt, fFam, (int)FontStyle.Regular, g.DpiX * fSize / 72.2f, rectf, format);
        g.DrawPath(new Pen(Color.FromArgb(180, Color.Black), 8), p);
        // Draw the text
        g.DrawString(txt, new Font(fFam, fSize), Brushes.White, rectf, format);
        // Flush all graphics changes to the bitmap
        g.Flush();
    }
    // Now save or use the bitmap
    return bmp;
}

On Windows 10 Outputs are generated correctly or as expected like this for Example:
https://i.stack.imgur.com/nHBl7.png
But when run on my Ubuntu 18.04 server, the GraphicsPath/Shadow would generate like this:
Notice the top left corner (it's a bit hard to see on dark background)
https://i.stack.imgur.com/onO2e.png
My first thought was an Error in the DPI-calculation since my Server doesn't have an X-Server installed but apparently the GraphicsPath is drawn correct; just the positioning is wrong?
Since the "Formatting" apparently works on the usual DrawString this behaviour seems weird to me, maybe the lack of the Emoji-Icon in the Font could be the cause of this?
Otherwise this looks like a platform-specific bug in the System.Drawing package to me... perhaps .Net Standard 2.0 is also affected by this...
Thanks in advance.

closing in favor of https://github.com/dotnet/runtime/issues/31979


Pagination with hits_per_page to limit per page but got error

I am trying to limit the pagination using hits_per_page with Kaminari:
Candidate.search("", page: 1, hits_per_page: 5, sort: ["name:asc"])

But was given this error:
MeiliSearch::ApiError: 400 Bad Request - Json deserialize error: unknown field `hitsPerPage`, expected one of `q`, `offset`, `limit`, `attributesToRetrieve`, `attributesToCrop`, `cropLength`, `attributesToHighlight`, `showMatchesPosition`, `filter`, `sort`, `facets`, `highlightPreTag`, `highlightPostTag`, `cropMarker` at line 1 column 21. See https://docs.meilisearch.com/errors#bad_request.

Removing the hits_per_page and I got back the first 20 records of the first page.
I even replace it with limit, but no luck:
# Replacing to limit don't work also
Candidate.search("", page: 1, limit: 5, sort: ["name:asc"])

Is there any special options we are not aware of? Or is pagination not working and need to wait for v0.29

OS: macOS 12.5
Meilisearch server version: v0.28.1
meilisearch-rails version: v0.7.1
Rails version: v<IP_ADDRESS>

Hi @mech I found what happened, I'll provide a fix soon!

@mech I created a branch with the fix, I need to have my PR approved to release a new version.
So while I wait for the approval, you have some options:

You can reference this branch directly in your Gemfile
You can change from hits_per_page to hitsPerPage

Thanks for using Meilisearch ❤

Wow tks, hitsPerPage does work. I will use this temporarily.

It will be released soon as 0.7.2!

I am puzzle, when I do a search, it appear it is querying all 200 records no matter which page I am on.
Doing Candidate.ms_search("", page: 2, hitsPerPage: 3) will result in such SQL:
SELECT * FROM "candidates" WHERE id IN ($1, $2, ...... $200)

Is this normal?

Yes, it is normal because Meilisearch does not provide a way to know the total hits yet.
@curquiza explained this here: https://github.com/meilisearch/meilisearch-rails/issues/138#issuecomment-1144747998
It is something we plan to improve in the future, in fact, we already have a prototype for this https://github.com/meilisearch/meilisearch/discussions/2635

Tks for clarification, will play with the new prototype 👍


What ovn packages need to be installed when I install openstack in a common way？

The ovn openstack tutorial on the ovn website installs OpenStack by installing DevStack. Now I install OpenStack in a normal way. What ovn packages do I need to install? My system is centos 8 and the installed OpenStack is Ussuri.

@ExploreScience please direct the question to a more appropriate venue. Depending on the installation method you use, it may be either RDO mailing list or openstack-discuss mailing list.
This github repo maintains OVN core components, not OpenStack or any of its installation mechanisms.

Thans for your reply, I will look to openstack-discuss mailing list for answers.


Image loading gets slower for more images

After loading 8 images (224x224x208), the last 7 images were loading very slowly. (niivue-compare)

fixed, was a bug using Signals and drawScene() too often


Unable to set attribute: autocapitalize on a searchbar

Ionic version:  (check one with "x")
[ ] 1.x (For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[x] 3.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
Currently, setting autocapitalize has no effect on controlling how input is typed into a searchbar and is effectively ignored.
<ion-searchbar autocapitalize="none"></ion-searchbar>

This has no effect.
Expected behavior:
When setting the autocapitalize feature, for it to be set on the native input.
See documentation:
MDN:
https://developer.mozilla.org/en/docs/Web/HTML/Element/input#attr-autocapitalize
Apple:
https://developer.apple.com/library/content/documentation/AppleApplications/Reference/SafariHTMLRef/Articles/Attributes.html#//apple_ref/doc/uid/TP40008058-autocapitalize
Steps to reproduce:
N/A
Related code:
<ion-searchbar autocapitalize="none"></ion-searchbar>

Other information:
I am opening this issue as part of a pull request I have made to implement said behaviour.
Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
cli packages:

    @ionic/cli-plugin-ionic-angular : 1.4.0 (/Users/kelvindart/src/searchbar/node_modules/@ionic/cli-plugin-ionic-angular)
    @ionic/cli-utils                : 1.6.0 (/Users/kelvindart/src/searchbar/node_modules/@ionic/cli-utils)
    ionic (Ionic CLI)               : 3.6.0 (/Users/kelvindart/src/searchbar/node_modules/ionic)

local packages:

    @ionic/app-scripts : 2.1.3
    Ionic Framework    : ionic-angular 3.6.0

System:

    Android SDK Tools : 26.0.2
    Node              : v8.2.1
    OS                : macOS Sierra
    Xcode             : Xcode 8.2.1 Build version 8C1002
    ios-deploy        : 1.9.1
    ios-sim           : 5.0.13
    npm               : 5.3.0

Hello, thanks for opening an issue with us and thanks for the PR (: We will take a look into this.


How to validate booleans?

I'd like to validate an object of booleans. I want to prevent my users from sending custom requests to the server containing any other type than booleans.
I haven't found a suitable validator. Does validate.js lack of that capability or is there a way to achieve this?

I already found out: http://validatejs.org/#custom-validator
Sorry so much for posting nonsense!

This is definitely not nonsense :)
A ticket has been opened (#66 based on #65) to support this.
Until that has been fixed you can use the inclusion validator:
var constraints = {
  checkbox: {
    presence: {
      message: "^You need to check the checkbox"
    },
    inclusion: {
      within: [true],
      message: "^You need to check the checkbox"
    }
  }
};

validate({checkbox: false}, constraints)
// => {"checkbox": ["You need to check the checkbox"]}

validate({checkbox: true}, constraints)
// => undefined

@ansman Thanks :)


Bevy dependency version less strict

Following a discord discussion:
https://discord.com/channels/691052431525675048/1029089408734990346
bevy did has a patch for 0.8.1, as bevy_rapier should be compatible with all 0.8.* bevy version, making this change would fix incompatibility versions.

Hi! Setting version = "0.8.0" and version = "0.8" are equivalent, they both mean version >= 0.8.0.
Quoting the cargo doc:
1.2.3  :=  >=1.2.3, <2.0.0
1.2    :=  >=1.2.0, <2.0.0
1      :=  >=1.0.0, <2.0.0
0.2.3  :=  >=0.2.3, <0.3.0   <-- this one
0.2    :=  >=0.2.0, <0.3.0   <-- and this one
0.0.3  :=  >=0.0.3, <0.0.4
0.0    :=  >=0.0.0, <0.1.0
0      :=  >=0.0.0, <1.0.0

Please reopen if I’m misinterpreting that documentation.


New Sticky Navbar (#25)

Thank you for your contribution 🤩🤩

Please mention the following in order to get PR merged  🙌🏻🙌🏻

Kind of change this PR introduce : Made a new navbar for all the pages
Issue it resolves : #25
Screenshots & GitHub Page Link : https://sushantpatial.github.io/Blood-Buddy/

Poor visibility, not good design. @SushantPatial

Check now @2024-SANDHYA
https://sushantpatial.github.io/Blood-Buddy/

Check now @2024-SANDHYA https://sushantpatial.github.io/Blood-Buddy/

It is not looking good at all !! Not going with the design too !!  @SushantPatial


merging of qualifications results into wrong data

As the new vaccination recommendation is here, it is no longer possible to get the status of BioNTech (L920), Moderna (L921) and AstraZeneca (L922) separately.
The new vaccine list merges the three together:
[{
    "qualification": "L920",
    "name": "Comirnaty (BioNTech)",
     "interval": 21,
    "age": "16-17"
 },{
    "qualification": "L921",
    "name": "mRNA-1273 (Moderna)",
    "tssname": "Moderna, BioNTech, AstraZeneca",
    "interval": 28,
    "age": "18+"
}]

The /rest/suche/termincheck?plz=XXXXX&leistungsmerkmale=LXXX API is returning for L921/L922 now coupled values.
They introduced the vaccination change today (07.03.2021) at around 14:40 and coupled the values today at 19:40.

Thanks for alerting me to this! Impfterminmonitor will be updated in a while. I think this repo doesn't need any changes, so I'll close the issue for now. Please feel free to reopen if otherwise.


SetSelectedTime() doesn't work in onCreate()

For some reason, calling setSelectedTime() on the TimeSpinner in the activity's onCreate() method doesn't do anything. Could possibly also affect setSelectedDate() in the DateSpinner, need more time to test.

This is now fixed, will close it when the next version is uploaded to maven central.

Fixed in release 1.1.3 (3e73e247).


Examples work in rawgit, please link!

https://rawgit.com/XXIIVV/Riven/master/example.conditional.html
https://rawgit.com/XXIIVV/Riven/master/example.math.html

What is rawgit?

From first result of https://www.google.com/search?q=rawgit:

RawGit serves raw files directly from GitHub with proper Content-Type headers.

Does this make sense? Do you have any other questions?

It does but what do you mean by please link?

From the README?

From the README?

I would recommend it.

ah! Absolutely :)
We're working on a couple of new examples, when they're done I will add them in the README.
Thanks!


mat-expansion-panel not working first-time

I have these 3 components:
grandparent:
<app-route-group *ngFor="let list of routes" [ves]="r" [list]="list">
</app-route-group>

parent:
<mat-card>
  <mat-card-content>

    <app-route *ngFor="let r of list" [ves]="r"></app-route>

  </mat-card-content>
</mat-card>

and grandchild:
<mat-expansion-panel>
  <mat-expansion-panel-header>
    <mat-panel-title>
      This is the expansion title
    </mat-panel-title>
    <mat-panel-description>
      Mat Panel Description
    </mat-panel-description>
  </mat-expansion-panel-header>

( This is the primary content of the panel)

</mat-expansion-panel>

the problem is that on first render - the expansion panels are really slow to respond, 1 or 2 second delay to expand upon a click.
If I re-render, then the expansion panels are much more responsive, back to normal. Has anyone experienced this problem before? I don't see how my code could be a problem perse, it works, just daaaaamn slow the first time.
My only other hypothesis is a loop (feedback loop) in the code, that's not quite infinite, but sucks up some time until it breaks out. But I am not seeing such a loop in my code with logging statements.

Closing this issue as it does not follow the issue template. Please file a new issue that follows the template, which gives the team the information needed to investigate


Disable babel cache when developing

https://github.com/zeit/next.js/issues/3164
This might be needed for the babel-plugin-inline-import-graphql-ast dependency to work properly. Passing BABEL_DISABLE_CACHE doesn’t work with Next.js.

Just realized the server isn’t restarted either when modifying .graphql files.

Done with https://github.com/ZolaApp/zola-app/pull/77.


Import prompts, Modelfiles button is inactive

Bug Report
Description
Bug Summary:
Hi, when I click on Import prompts or Modelfiles button nothing happens (seems that they are inactive). Download buttons work correctly.
Steps to Reproduce:
Navigate to either Prompts or Modelfiles section and click on "Import Prompts" or " Import Modelfiles" button.
Expected Behavior:
Open file browser to select JSON file.
Actual Behavior:
Nothing happens, button is inactive.
Environment

Operating System: [Ubuntu 20.04]

Reproduction Details
Confirmation:

[x] I have read and followed all the instructions provided in the README.md.
[x] I am on the latest version of both Open WebUI and Ollama.

Installation Method
Docker

I suspect I know the cause, pinging @tjbck: Is this another issue from the attempt to get rid of vanilla JS?

Yes, seems to be a common theme in the PR: https://github.com/open-webui/open-webui/pull/1025/files#diff-69f3d6656db6b16bcf7427c8e7cc16c94e5a276b10fdac64e2f7a51cbfba6c70R112 Working on a fix right now.

Confirmed, issue is resolved !


Update ansible-dk to 1.2.0-3

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if updating a cask:

[ ] If the sha256 changed but the version didn’t,
provide public confirmation by the developer: {{link}}

Thank you for the contribution. It was merged directly as 318d670a67f8b1cfab50167c35fe3cbfbc40cc4d. Your contribution is still credited to you.


update llama_index to 0.8.55

Updating llama_index dependency to latest version 0.8.55
Addresses #62
Mainly just needed to fix an issue with PGVector initialization + add some of the new callback event types to an DB enum type column.

@sourabhdesai -- I'm running into this error (attached) when deploying on Render, wondering if it's due to this update?
Render Startup Failure due to punkt or nltk.txt

@sourabhdesai -- I'm running into this error (attached) when deploying on Render, wondering if it's due to this update?
Render Startup Failure due to punkt or nltk.txt

@joshsabol46  thanks for raising this. I took a look at the error log and it seems like it should be a fairly benign error that just needs to be caught in a try/catch. I'll make a PR adding that right now.


Notifications are not silent in chrome

Hi I am trying to use the silent option of Push.js but it is still making noise in Chrome, when I receive notifications. I am running this on a server with the files stored under the public directory.
My code is:
Push.create('Message',{
timeout:5000,
onClick: function(){
window.focus();
this.close;
},
silent:true
}
Help me please.
Thank you.

Does push.js even shows notification in chrome if you are using localhost,i.e , http connection..In my case it is working well in edge but i cant see any notification in chrome ? So, I infer that chrome is blocking notification on sites with insecure http connection as it blocks Notifications from Notification API.

Notification API should work fine in localhost. Please check that you have not denied push permission.

No , I have allowed notifications and popups . The promise is being fulfilled, it is just that notification is not showing up.

Please specify the OS and Browser versions. Thanks

OS -Windows
Chrome Version - 84

Returning to the principal issue,  @theLufenk , @kg-kartik , @vlazar & @Calinou  do you know why silent notifications are not working? I have made sure to the pass in the silent: true parameter and my notifications are coming through - just not silently.
I am using localhost for dev and heroku for live versions. Does not work on Chrome or Firefox (both run on Windows).
Sample code:
                        Push.create('Sit',{
                            tag: 'Warning',
                            body:"Hi ",
                            timeout:5000, //in ms
                            onClick: function(){
                                window.focus();
                                this.close;
                                },
                            silent:true
                            }
                        )

@NamanSharma5
silent is only supported on Mobile Chrome in the latest version.
Would be simple enough to add support for it here I believe.
A Pull Request is always welcome :)

@kg-kartik Could you please open a separate issue for your question. Thanks.

@theLufenk Why not just use all of the fields found under Notification API Instance properties?
As of now, only body, icon, tag, and requireInteraction are actually used, out of the 15 that are provided in the API.

@theLufenk Why not just use all of the fields found under Notification API Instance properties?
As of now, only body, icon, tag, and requireInteraction are actually used, out of the 15 that are provided in the API.

Any resolution for this ? otherwise this should be removed from the documentation


imageTransformOutputQuality does not work on iOS

Hello!
once the image resized the compression ratio is equal to 95 from an iOS mobile, not 85

    	imagePreviewMaxHeight: 170,
    	allowImageResize: true,
    	imageResizeTargetWidth: 682,
    	imageResizeUpscale: true,
    	maxParallelUploads: 1,
    	imageTransformOutputQuality: 85,

FilePond.registerPlugin(
		FilePondPluginFileRename,
		FilePondPluginFileValidateType,
		FilePondPluginFileValidateSize,
		FilePondPluginFileEncode,
		FilePondPluginImageResize,
		FilePondPluginImagePreview,
		FilePondPluginImageExifOrientation,
		FilePondPluginImageTransform
	);

...

Environment
Version

OS
iOS

Device
iPad  / ...

Browser
Safari  / Chrome / ...

How did you measure that?

sorry : on iOS 12.1.13

with this link https://www.imgonline.com.ua/eng/determine-jpeg-quality.php and also by the file weight between MacOS and iOS

The compression ratio is simply passed to the toBlob method, how much compression is applied is handled by the browser. There's not much we can do about that. Can you see the compression being applied when it's set to a low value like 40?

ok!
I just tested at 40, the file weight is well diminished, and the compression ratio shows 64, why such a difference in rate?

I don't know to be honest. It's browser specific, some will apply different compression techniques than other perhaps? For instance favouring speed over compression?

On Chrome MacOS the rate is 40

could we apply specific setting only for iOS ?

You could detect the browser/device and then pass a different compression value to FilePond

would you have an example to send the variable dynamically to FilePond.create?

I don’t, but it’s basic navigator agent sniffing and then setting the result to the settings object that is passed to FilePond.
Will close because this is not related to FilePond

yes, thank you so much !


g_oss is causing incorrect stringification results

Edit: I have now published a possible fix at #569!
I'm currently working on a stringification utility for STL classes, and I've discovered an obscure bug that manifests in two slightly different ways:
1.
When an argument to a MessageBuilder is stringified via being written to an ostream (operator<<) the result of that stringification is accidentally prepended to the result of the MessageBuilder.
Example:
struct A { }; struct B { };
static std::ostream& operator<<(std::ostream& o, const A&) { o << "A"; return o; }
template<> struct doctest::StringMaker<B> {
	static String convert(const B&) { return toString(A()) + "B"; }
};
TEST_CASE("") { FAIL(B()); }

Expected result: AB
Actual result: AAB
This can be avoided by first writing the String into an object like so:
doctest::String s = doctest::toString(B());
FAIL(s);

2.
When an operator<< utilizes toString which in turn executes its function via writing to a stream.
Arguably this is a bit contrived, since you usually wouldn't use toString in an operator<< overload, but it still shows a weakness in design, which demonstrates that simply giving MessageBuilderss their own thread local osstream won't solve this problem entirely.
There might be a less contrived instance of this bug lurking somewhere!
Example:
struct A { }; struct B { };
static std::ostream& operator<<(std::ostream& o, const A&) { o << "A"; return o; }
static std::ostream& operator<<(std::ostream& o, const B&) { o << "C" << "B" + doctest::toString(A()); return o; }
TEST_CASE("") { String s = toString(B()); FAIL(s); /* Failure is not due to MessageBuilder! */ }

Expected result: CBA
Actual result: ACA
The stream that is used to stringify B needs to be used again to stringify A, this messes things up.
I'm honestly not entirely sure on how to solve this, I think the idea of having a single string buffer will need to be abandoned.
My first approach was simply moving the logic of resetting the buffer into the result function, this solves 1. but modifies 2.'s result to be BCA, which is still incorrect!
My current progress can be found on https://github.com/Saalvage/doctest/tree/tlss
Some input would be appreciated!
Extra information

doctest version: a384864 (dev head at the time of posting)
Operating System: Windows 10 Pro 19043
Compiler+version: MSVC 22 17.0.2

So I fixed the 2015 builds and the obvious bugs in dev, but your AB vs AAB issue persisted. So I made a fix for it in another branch - take a look: https://github.com/doctest/doctest/commit/4f3591f61acf670f63bbad425f4a2934e710eda4
Basically I changed it so that whenever getTlsOssResult gets called the stream gets cleaned (hopefully after done with all the appending), and there's no cleaning going on in getTlsOss. Now your first example returns AB properly.
However the second example still behaves weirdly, but if I change "B" + doctest::toString(A()) to "B" << doctest::toString(A()) it starts behaving properly - so there's something going on with that operator+ for the String class - haven't looked too much into it yet.

Making getTlsOssResult clean the stream was my first approach, however, it doesn't solve the issue when a stringification calls another stringification that depends on it, when the inner stringification is finished the whole stream is cleared.
This is why I built the stack-like solution in #569, is there anything wrong with it?

merged the PR #569


How to change HTML and CSS for sign-up/in/out

Hi, just wondering if it's possible to change the html and css of pages for sign-in, sign-out, sign-up.  I don't know where are this pages located.

I know this is old, but for anyone interested, I found cloning this repo to my project's packages directory worked, as described in this SO post. HTH.


IsGesture on IOS devices

Summary
I saw in version 1.0.0 the issue of onRegionChangeComplete props (which has a property named isGesture, unavailable on ios ) was resolved..im  using version "1.3.2" .. and this method returns me undefined on ios devices
Reproducible sample code
const regionChanging = (values: any, details) => {
        console.log("details", details) => on android works, on ios returns only undefined
        if (details.isGesture === true) {
            onRegionChangeComplete(values)
            return
        }

    }

<MapView onRegionChangeComplete={(region, details) => regionChanging(region, details)} />

Steps to reproduce
nothing special :D
Expected result
to return true or false
Actual result
undefined
React Native Maps Version
1.3.2
What platforms are you seeing the problem on?
iOS (Apple Maps)
React Native Version
0.68.5
What version of Expo are you using?
Not using Expo
Device(s)
iphone 8
Additional information
No response

This is an ongoing request: https://github.com/react-native-maps/react-native-maps/discussions/4440
The current solution is to use Google Maps on iOS.

Still relevant

Still relevant

still relevant, however i found a workaround if anyone is looking for a fix this is my MapView ->  `
<MapView
provider={Platform.OS == "android" ? "google" : undefined}
style={styles.map}
customMapStyle={customMapTheme}
ref={mapRef}
onPress={handleMapPress}
region={region}
onPanDrag={() => {
if (!showSearchAreaButton && Platform.OS == "ios") setShowSearchAreaButton(true);
}}
onRegionChangeComplete={(region, isGesture) => {
      if (isGesture?.isGesture || Platform.OS == "ios") {
        if (!showSearchAreaButton && Platform.OS == "android") setShowSearchAreaButton(true);

        const newBoundingBox = [
          region.latitude - region.latitudeDelta / 2,
          region.latitude + region.latitudeDelta / 2,
          region.longitude - region.longitudeDelta / 2,
          region.longitude + region.longitudeDelta / 2,
        ];
        setRegion(region);
        setBoundingBox(newBoundingBox);
      }
    }}
  >`


Changing message and submessage does nothing...

It's staying in English.

Using the options like this works:
`
`


Changes according codestyle. Add flake8 to travis

Coverage remained the same at 52.857% when pulling dbe43a845d8743d0737d8ccb2096a3c2b05a4bea on oleksiyVeretiuk:up_maintainability into 35e0dfe367e70a2add78133393ac07b01fd50ef2 on openprocurement:master.


Tooltip Truncated Under Callout Title

Expected Behavior
The tooltip that appears when hovering over a task should show above callout title bars.
Current Behavior
The tooltip appears layer wise under the callout title bar. The callout content area in a narrow callout also forms a horizontal scroll bar.

Steps to Reproduce

Insert a few tasks into a callout.  The tasks needs to have a multi-lined tooltip (ie. is recurring, scheduled and any other thing to lengthen the tooltip).
Set the task codeblock to be in short mode
Hover mouse over top/first task listed.

The callout and tasks codeblock I used in the sandbox vault is:
>[!note]
> ```tasks
> short mode
> ```

Context (Environment)

Obsidian version: 0.14.6
Tasks version: 1.5.1
[X] I have tried it with all other plugins disabled and the error still occurs. I tested this out in the Obsidian sandbox with only Tasks installed (Second image is a screenshot of the Sandbox).

Possible Solution
I have tried setting some personal css snippet code to see if changing the z-index will fix the issue. So far this has not been successful.
.callout,
.callout-title {
    z-index: 0;
}
.tooltip {
    z-index: 99999;
}

Thank you for the detailed report @Azurewren!

Thanks!
Looking at the history, that was done for https://github.com/obsidian-tasks-group/obsidian-tasks/issues/371 - where the > is after the [ ].
The callout issue is tasks that look like this > - [ ] are not even detected as tasks in the first place.
However, see the example in that issue, it will provide a useful test scenario for this one, to make sure we don't break that behaviour.

For anybody who might find it useful, I found a (partial) workaround for this - but only in the context of reading mode.
This is the css snippet that makes the behavior serviceable:
.callout, .callout-content{
	overflow:visible;
}

However, I couldn't get short-mode pop-ups to work nicely in Live Preview Editing mode. Even outside of callouts, i.e. just in a simple tasks-query-codeblock, they are restricted to the area of the codeblock.

Thanks very much @oldakos.

Found working solution, may break something another with codeblocks because I'm not sure about purpose of 'contain', but at first glance - everything ok
.cm-editor .cm-contentContainer .cm-preview-code-block.cm-embed-block.markdown-rendered{
overflow: visible;
contain: none !important;
}

Thanks.

For anybody who might find it useful, I found a (partial) workaround for this - but only in the context of reading mode.
This is the css snippet that makes the behavior serviceable:
.callout, .callout-content{
	overflow:visible;
}

However, I couldn't get short-mode pop-ups to work nicely in Live Preview Editing mode. Even outside of callouts, i.e. just in a simple tasks-query-codeblock, they are restricted to the area of the codeblock.

This fixed it for me is both reading and live modes. I think this fixed should be merged into master since it is very trivial and the issue is very annoying. I currently use this fix as an Obsidian CSS snippet:
/* Fix tooltip clipping when overflowing a callout */
.callout, .callout-content{
    overflow: visible;
}

@synalice thanks!
@ilandikov The above might be up your street. I've pushed a couple of changes (see just above) to make it easier to test this.
And I've tried out the suggested fix above - the patch is:
Index: src/Renderer/Renderer.scss
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
diff --git a/src/Renderer/Renderer.scss b/src/Renderer/Renderer.scss
--- a/src/Renderer/Renderer.scss	(revision f0c37dca4a429106e84f511d5552d53f714de615)
+++ b/src/Renderer/Renderer.scss	(date<PHONE_NUMBER>595)
@@ -113,6 +113,12 @@
     white-space: nowrap;
 }

+/* Fix tooltip clipping when overflowing a callout:
+   see https://github.com/obsidian-tasks-group/obsidian-tasks/issues/650 */
+.callout, .callout-content {
+    overflow: visible;
+}
+
 .task-list-item-checkbox {
     cursor: pointer;
 }

It does work for vertical height. It doesn't prevent the right-side truncation of the heading name on the long heading lines.
I was a bit nervous about retaining the fix as it isn't specific to Tasks query blocks - so would affect all callouts for users that have Tasks enabled...
I've spend more time on this than I have right now - so am just saving here what I've done....

@claremacrae I think the solution by @synalice is as good as it can be (for now). If you are worried about affecting all the callouts which is reasonable, maybe we can include the solution as a standalone CSS snippet like tasks-callout-tooltip-fix that users can enable/disable at will and add a small explanation in the docs and reference it here?
Otherwise, this seems to me like something related to Obsidian, I would think even to open a bug or inquire about this with Obsidian team, it may be a feature, not a bug =)

Mostly I'm concerned with making sure that users can see their data.
So yes, truncating under the title is a problem.
But so is the truncating of text at the fixed-size width, meaning that backlinks in the tooltip are often useless.

meaning that backlinks in the tooltip are often useless

I mean... not necessarily. You can still see most of it (45 characters to be exact). Usually that's more that enough to understand, what file we are talking about.

meaning that backlinks in the tooltip are often useless

I mean... not necessarily. You can still see most of it (45 characters to be exact). Usually that's more that enough to understand, what file we are talking about.

Not in mu vault - filename plus heading is often more than 45 characters long.


corrected typo in mode section

'Microsoft.Resources/subscriptions/resourceGroup' - added trailing s

@Danrawlings-msft : Thanks for your contribution! The author, @DCtheGeek, has been notified to review your proposed change.

Thanks @Danrawlings-msft !  This fixes Issue #25029.
@MicrosoftDocs/azure-cxp-triage #sign-off


⚠ Bofrost.de has degraded performance

In 669de3f, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1495 ms

Resolved: Bofrost.de performance has improved in b1f91ff after 308 days, 9 hours, 13 minutes.


Persistent blacklist of known bad keys

We should consider having a persistent blacklist of keys that were found to be provably misbehaving (e.g. nodes that were double signing things they shouldn't be).
Those keys should be stored in the consensus layer and be prevented from registering and/or participating in the system.

While this isn't a bad idea in theory, with key generation being dirt cheap, I'm not sure if this solves much beyond the "all of our nodes have all this free storage space" problem.


Xcode 8 support

Starting with Xcode 8, plugins will no longer be supported. I will make an attempt to work around this by making the Build Time Analyzer a standalone app. I believe this can be done by simply scanning the log files during the app launch (and perhaps with a refresh button or similar).
The most recent log file / files will be the ones to work with.

@RobertGummesson or we can add a new run script build phase, and trigger the standalone app from there

@onmyway133 - Yep, that's an option too. ...or perhaps both.

I have a build log parser here: https://github.com/orta/Snapshots-app/blob/master/Snapshots/DeveloperDirWatcher.swift
Been wanting to convert all of this stuff into an XcodeSDK mixed with the new AppleScript API, but haven't made the time yet.

@orta Good stuff

Is there any progress on Xcode 8 support? I'd love to use this!

Yes, but it's been slow (other priorities). I'm still on it though so bare with me. :)

Update:  #45 contains the implementation for the standalone app. I will be testing it throughout the day and merge it to master if nothing catches on fire.
A standalone app is obviously a bit more limited than a plug-in. Basically, the app now monitors the derived data folder rather than subscribing to Xcode notifications. Here are a couple of limitations:

The app doesn't indicate when a build process has started (but it knows when it ends)
Jumping to line upon selection no longer works, instead it just opens up the appropriate Swift file.

I have also made some smaller improvements. One is the ability to choose existing projects to analyze, i.e existing builds.


project.lastUpdated field

When status changes.
Use for the autoCloseout job instead of the history

Once this runs a little on prod, update the autoCloseout to use this value instead.


⚠ Bofrost.de has degraded performance

In 3df923c, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 753 ms

Resolved: Bofrost.de performance has improved in 0f380c0.


Node.js Mentorship team Meeting 2019-04-19

Time
UTC Fri 19-Apr-2019 16:00 (04:00 PM):

Timezone
Date/Time

US / Pacific
Fri 19-Apr-2019 09:00 (09:00 AM)

US / Mountain
Fri 19-Apr-2019 10:00 (10:00 AM)

US / Central
Fri 19-Apr-2019 11:00 (11:00 AM)

US / Eastern
Fri 19-Apr-2019 12:00 (12:00 PM)

London
Fri 19-Apr-2019 17:00 (05:00 PM)

Amsterdam
Fri 19-Apr-2019 18:00 (06:00 PM)

Moscow
Fri 19-Apr-2019 19:00 (07:00 PM)

Chennai
Fri 19-Apr-2019 21:30 (09:30 PM)

Hangzhou
Sat 20-Apr-2019 00:00 (12:00 AM)

Tokyo
Sat 20-Apr-2019 01:00 (01:00 AM)

Sydney
Sat 20-Apr-2019 02:00 (02:00 AM)

Or in your local time:

http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Community Committee+Meeting+2019-04-19&iso=20190419T16
or http://www.wolframalpha.com/input/?i=04PM+UTC%2C+Apr+19%2C+2019+in+local+time

Agenda
Extracted from mentorship-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
Invited

Mentorship Members: @nodejs/mentorship

Observers/Guests
Feel free to follow along on the YouTube live stream, or attend meeting as a guest
by calling in to Zoom, using the links below. If you will be attending as a guest,
please comment on this issue to let us know you'll be joining.
Notes
The agenda comes from issues labelled with mentorship-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.
Joining the meeting

Link for participants: < will be updated >
For those who just want to watch: https://www.youtube.com/channel/UCQPYJluYC_sn_Qz_XE-YbTQ

I'm puzzled by why things in the table say Fri 18-Apr-2019 and Sat 19-Apr-2019. April 18 2019 is a Thursday, not a Friday. April 19 2019 is a Friday, not a Saturday. ????? Bug in the tooling? Or a manual edit / copy-paste error of some kind? Or am I confused and need better calendar-reading skills?

@Trott We dont have the tooling setup :( I copy-pasted it and forgot to update the table.


Add a SQLite implementation of the jeff.Storage interface

Thanks for the notes! I've been sick this week, so I'm a little behind, but I'll hopefully have time to follow up this weekend or next.

In addition to the inline comments, could you also add a test to this file?

Sure, I added tests in 7d09c7a.

Perhaps also an example for the documentation?

I'm not seeing where this would go, as it doesn't look like the README has examples for any of the stores. Is there a place you have in mind?

Finally, do you think it's possible to use standard SQL as much as possible and make this work for any *sql.DB object passed in, or is that unrealistic?

I don't think this would be practical. MySQL/MSSQL/Postgres all have different semantics for prepared statements, so I don't think the syntax for SQLite would abstract away to the other DB types.

@abraithwaite - Is this PR still under consideration?


Add a batch_key option to HVG function to reduce the batch effects

I added a new batch_key option to HVG function. If specified, it runs the HVG selection in every batch separately and then merges the list in order to reduce the batch effects by avoiding the selection of batch-specific genes. This doesn't fully correct the batch effect but reduces it.
Running the function for each batch is trivial but merging is trickier than I thought. How I do it now is as follows:

hvg is run on each batch and resulting hvg lists are first concatenated into a single dataframe.
The data frame is grouped by genes. mean, dispersion and normalized dispersion values are aggregated via np.nanmin np.nanmean. Another column which counts "in how many batches a gene is detected as hvg" is also created. I'm not 100% certain about nanmin, but I think it works better than mean or max, because it forces the process to pick genes with high dispersion even in the "worst" batches.
if n_top_genes is given, combined hvg lists are sorted by 1) in how many batches a gene is detected as hvg 2) normalized dispersion. normalized dispersion is used to break the ties. Then top n genes are selected as the final hvg list.
if n_top_genes is not given, same mean and dispersion thresholds are applied to the combined hvg list.

Here is the code to see the improvement of this approach:
import scanpy as sc
import numpy as np
import pandas as pd

ad = sc.read("pancreas.h5ad", backup_url="https://goo.gl/V29FNk") # adapted from scGen repo
ad.obs["cell_type"] = ad.obs["celltype"].tolist()

ad = sc.AnnData(ad.raw.X, var=ad.raw.var, obs=ad.obs)
sc.pp.normalize_per_cell(ad)
sc.pp.log1p(ad)

sc.pp.highly_variable_genes(ad, batch_key='batch')
sc.pp.pca(ad)
sc.pp.neighbors(ad)
sc.tl.umap(ad)
sc.pl.umap(ad, color=["batch", "cell_type"])

sc.pp.highly_variable_genes(ad)
sc.pp.pca(ad)
sc.pp.neighbors(ad)
sc.tl.umap(ad)
sc.pl.umap(ad, color=["batch", "cell_type"])

sc.pp.highly_variable_genes(ad, batch_key='batch', n_top_genes=1000)
sc.pp.pca(ad)
sc.pp.neighbors(ad)
sc.tl.umap(ad)
sc.pl.umap(ad, color=["batch", "cell_type"])

sc.pp.highly_variable_genes(ad, n_top_genes=1000)
sc.pp.pca(ad)
sc.pp.neighbors(ad)
sc.tl.umap(ad)
sc.pl.umap(ad, color=["batch", "cell_type"])

Plase review thoroughly :) Tests are missing, I'll add them soon.

I just found out that raw was already log transformed. Now I fixed it and nanmin seems a bit too conservative, any ideas?

Hey! I think it's a great idea to put HVG calculation within batches as a pull request. This is also an important pre-processing step for sce.mnn_correct, which I usually run on the intersection of HVGs from each batch. Do you think you could output the intersection as well? Or would it just be a matter of subsetting HVGs that are detected in all batches from the resulting dataframe?

Hey. I also thought about the intersection but didn't implement it as the default output for two reasons.

it can be too harsh, especially if there is some biological variation between batches. When we sort the genes based on in how many batches they're detected as HVG and on mean normalized dispersion, there is still a chance for the user to catch such "biological" genes with a high n_top_genes value.

Output of highly_variable_genes should be consistent regardless of batch_key option. So n_top_genes and mean/dispersion cutoff flavors should still work the same way. I feel like using the intersection directly as the output violates that.

However, making 'highly_variable': np.nansum part available in adata.var is a good idea. Then users can manually make the selection more stringent by selecting genes where this value == nbatches.

I agree that using the intersection is too harsh if the only data integration/batch correction you do is this HVG filtering, but for mnn_correct for example you only use these HVGs to calculate the technical batch vector. In that case you ideally don't want to capture the biological variation between batch samples. For that I reckon having an option of getting the intersection would be good.
And for point 2... definitely agreed... but again, a different use case for me. The same approach (intersection of HVGs) is suggested for the new CCA in Seurat v3 btw.

@LuckyMD Can you maybe check if the new highly_variable_nbatches variable in adata.var is useful for finding the intersections?
adata.var['highly_variable'] = adata.var['highly_variable_nbatches'] == len(adata.obs.batch.cat.categories)

I'm sure it will be... Just having network issues atm, so server storage is too slow to do anything. Can't really test this atm I'm afraid :/.

Sorry my master branch is messed up, I'll send another PR.


Version fix on README.md

Version 4.0 is not released for a while, it's better to keep it 0.3.1 which is the latest stable release

It's even better to migrate to https://github.com/cberner/fuser, which is a maintained fork of this crate ;)


Detect cycles

fixes vanished arrows on HierarchyWidget
introduces cycle detection in hierarchy trees. cyclic branches are not expanded anymore, preventing unlimited recursion. a warning is printed on console to inform about the cyclic branch, which could be a mistake in the terminology service
other minor issues were addressed

:tada: This PR is included in version 2.7.0 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


add flutter version manager

with the flutter version manager (fvm) it's easy to change the flutter versions and make sure that we are all working with the same one.
I think at the moment it's not important, but since i had a different version installed than all of you what lead to the problems with my last PR i installed it so that this does not happen again. (for more information see https://fvm.app/).
@fynsta thanks for finding fvm.

just fyi the link in the description is wrong


Mark ol.format.filter.Spatial as abstract class

fixes #7217 and add missing @abstract tag

Yes, it make sense to remove the @api annotation but will it require a new major release (5.0.0) ?

Hm. Well, you cannot add a @deprecated annotation, because you will get a compiler warning. But you could mention that those are deprecated in their docs. And we can remove the @api annotation later, i.e. before we release 5.0.

@ahocevar I've added the deprecation warning in the doc

Thanks for the review


RHIDP 4573 Discover- Verify existing content is removed from the getting started guide

IMPORTANT: Do Not Merge - To be merged by Docs Team Only
Version(s): 1.3, 1.4
Issue: https://issues.redhat.com/browse/RHIDP-4573
Link to docs preview:

Reviews:

[ ] SME: @ mention assignee
[ ] QE: @ mention assignee
[ ] Docs review: @ mention assignee
[ ] Additional review: @mention assignee (by writer)

Additional information:

@jmagak Please resolve the conflict to make the PR mergeable.

@themr0c I have resolved all conflicts; PR is ready for merging.


Bump node-fetch version and update travis file

Bump node-fetch version and update travis file to make it runs with correct version of nodejs.
fetch-node doesn't seem working with node 9, so node 7 and 8

@normanzb it's just nock that's broken in node 9. node-fetch works fine. https://github.com/matthew-andrews/isomorphic-fetch/pull/163


Can not create Kusto Database Principal

$ pulumi version
v2.1.1

$ pulumi plugin ls
NAME        KIND      VERSION  SIZE    INSTALLED  LAST USED
azure       resource  3.4.0    177 MB  n/a        1 week ago
azuread     resource  2.1.1    41 MB   n/a        1 day ago
azuread     resource  2.1.0    41 MB   n/a        1 week ago
kubernetes  resource  2.0.0    52 MB   n/a        1 week ago

TOTAL plugin cache size: 312 MB

Using slightly modified code from example
import pulumi
import pulumi_azure as azure

tags = {"Owner"<EMAIL_ADDRESS>
current = azure.core.get_client_config()
rg = azure.core.ResourceGroup("rg", location="East US", tags=tags)
cluster = azure.kusto.Cluster("cluster",
    location=rg.location,
    resource_group_name=rg.name,
    sku={
        "name": "Standard_D13_v2",
        "capacity": 2,
    })
database = azure.kusto.Database("database",
    resource_group_name=rg.name,
    location=rg.location,
    cluster_name=cluster.name,
    hot_cache_period="P7D",
    soft_delete_period="P31D")
principal = azure.kusto.DatabasePrincipal("principal",
    resource_group_name=rg.name,
    cluster_name=cluster.name,
    database_name=database.name,
    role="Viewer",
    type="User",
    client_id=current.tenant_id,
    object_id=current.client_id)

Added tags and changed
database_name=azurerm_kusto_database["test"]["name"] -> database_name=database.name

Kusto cluster and Database are created, but DatabasePrincipal returned an error:
Diagnostics:
  azure:kusto:DatabasePrincipal (principal):
    error: Error creating Kusto Database Principal (Resource Group "rg-kusto-testdcc32db9", Cluster "cluster9c203712"): kusto.DatabasesClient#AddPrincipals: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="BadRequest" Message="The request is invalid."

I think this depends on your current authentication mechanism that you use with Pulumi. I'm logged in as a user with az login and the following snippet worked for me (note a different object_id):
principal = azure.kusto.DatabasePrincipal("principal",
    resource_group_name=rg.name,
    cluster_name=cluster.name,
    database_name=database.name,
    role="Viewer",
    type="User",
    client_id=current.tenant_id,
    object_id=current.object_id)

Here is my new principal in the portal:

In case of a doubt, you should export all the properties from current and double-check whether the IDs that you are passing are actually valid. I suspect that the original example is intended to be used with a SP.
I hope this helps.

Hi
object_id did the trick. Next I created SP and used the code:
`
kusto_application = Application("kusto-app")
kusto_service_principal = ServicePrincipal("kustoServicePrincipal",
application_id=kusto_application.application_id)
kusto_service_principal_password = ServicePrincipalPassword("kustoServicePrincipalPassword",
end_date="2099-01-01T01:02:03Z",
service_principal_id=kusto_service_principal.id,
value=config.require("service_principal_password")
)
resource_group = ResourceGroup(
'kusto-rg',
tags=tags)
kusto_cluster = Cluster(
"kusto-cluster",
name=config.require("kusto_cluster_name"),
tags=tags,
resource_group_name=resource_group.name,
sku={
"name": "Standard_D11_v2",
"capacity": 2
}
)
kusto_database = Database(
"kusto-database",
cluster_name=kusto_cluster.name,
name="pulumidb",
resource_group_name=resource_group.name
)
kusto_database_principal = DatabasePrincipal(
"kusto-database-principal",
client_id=subscription.tenant_id,
cluster_name=kusto_cluster.name,
database_name=kusto_database.name,
object_id=kusto_service_principal.object_id,
resource_group_name=resource_group.name,
role="Admin",
type="App"
)
`
I got an error:
Diagnostics:   azure:kusto:DatabasePrincipal (kusto-database-principal):     error: expected non-nil error with nil state during Create of urn:pulumi:dev-kusto::kusto::azure:kusto/databasePrincipal:DatabasePrincipal::kusto-database-principal
Meanwhile SP was added to Database Permissions

This issue is three years old and hasn't got any recent comments. I'll assume it's been fixed in https://github.com/pulumi/pulumi-terraform-bridge/issues/114


fix: missing stacktrace during error reporting

:tada: This PR is included in version 1.2.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


CASMTRIAGE-5999

Summary and Scope

upgrade csm-node-heartbeat version

Issues and Related PRs

https://jira-pro.it.hpe.com:8443/browse/CASMTRIAGE-5999
https://github.com/Cray-HPE/csm-node-heartbeat/pull/5

Testing
Tested on:

local system
Baldar

Test description:
csm-node-heartbeat=2.3-1 was installed. It properly removed cray-heartbeat in the process.
Risks and Mitigations
None known.
Pull Request Checklist

[x] Version number(s) incremented, if applicable
[x] Copyrights updated
[x] License file intact
[x] Target branch correct
[x] CHANGELOG.md updated
[x] Testing is appropriate and complete, if applicable

backport release/1.5

/backport release/1.5


Peering Request

Full Name
Xin Bingxian
ASN
199310
PeeringDB Integration

[X] My PeeringDB Entries are current
[ ] Peer at ALL EXCHANGES (and skip the Peer Address(es) field below)

Peer Address(es)
2a0e:97c0:220::1
Multihop

[X] Multihop Peering Request

Thank you for contacting RouteViews. We are happy to set up an EBGP multihop session with you.
Our collector details are:
IPv6: 2001:468:d01:33::80df:3370
ASN: 6447
FQDN: route-views6.routeviews.org

I've set up the sessions now:
Neighbor              V         AS   MsgRcvd   MsgSent   TblVer  InQ OutQ  Up/Down State/PfxRcd   PfxSnt Desc
2a0e:97c0:220::1      4     199310         0         1        0    0    0    never       Active        0 WolfXun Network

Please let us know if you need help setting up the BGP sessions.

Hello, I would like to open another IPv4 Session
Peer Address is <IP_ADDRESS>

Thanks for getting in touch again! Okay, we can do that. The collector we had you connected to is designed only for IPv6 connections, not dual stack. For dual stack connections we have to move you to our route-views7 collector. Here are its details:
IPv4: <IP_ADDRESS>
IPv6: 2001:468:d01:33::113
ASN:  6447
FQDN: route-views7.routeviews.org

I've set up the peerings there now:
Neighbor           V         AS   MsgRcvd   MsgSent   TblVer  InQ OutQ  Up/Down State/PfxRcd   PfxSnt Desc
<IP_ADDRESS>     4     199310         0         2        0    0    0    never       Active        0 WolfXun Network
2a0e:97c0:220::1   4     199310         0         2        0    0    0    never       Active        0 WolfXun Network

I've also removed the configuration we had for your IPv6-only peering from our route-views6 collector. If you would please configure both multi-hop peerings with the collector above.
Many thanks!

I noted you closed this as completed. It's not.
<IP_ADDRESS>  4     199310    291968<PHONE_NUMBER>5    0    0 07:17:27            0        0 WolfXun Network
2a0e:97c0:220::1            4     199310         0       125        0    0    0    never      Connect        0 WolfXun Network

Zero prefixes received on IPv4, and the IPv6 peering is down. Please resolve.

Due to the restructuring arrangement, our network is now undergoing an architectural upgrade, so we can't feed normally, we will re-feed as soon as the upgrade is completed.


fix(textfield): text-align inherits from parent

Fix #5509

Centered Text

    <md-outlined-text-field value="This text should be at the start"></md-outlined-text-field>
    <md-filled-text-field value="This text should be at the start"></md-filled-text-field>
    <input value="This text should be at the start" />

    <md-outlined-text-field class="text-center" value="This text is manually centered"></md-outlined-text-field>
    <md-filled-text-field class="text-center" value="This text is manually centered"></md-filled-text-field>
    <input class="text-center" value="This text is manually centered" />

Oops, I didn't see this PR when reading your issue. I made https://github.com/material-components/material-web/pull/5523 to fix it, so I'll close this PR and track the fix there since its tests are already in progress.


Heroku doesn't read DATABASE environment variable

Heroku deployment error:
File "/app/contributr/contributr/settings/production.py", line 9, in <module>
NameError: name 'DATABASES' is not defined

This definitely happened after #79 got merged in.

I'm working on it, I think i know what causes it. Testing with heroku now

Fixed with PR #86


Molarity 1.4.0-rc.1 RC test

@ariel-phet, Molarity 1.4.0-rc.1 is ready for RC testing.
Link to sim _en.html
Link to sim _all.html
Link to sim iframe
Link to sim XHTML
Link to phet-io standalone
Link to phet-io studio
Normal RC Test Matrix
phet io RC Test Matrix
Issues to Verify
(all should be marked "status:fixed-pending-testing")
Please test the following issues and check them off after addressing. If they are resolved, close them.  If not, they should be updated.

Mainly test the XHTML like the iframe, to ensure that it still works appropriately

Please also verify

[x] stringTest=double (all strings doubled)
[x] stringTest=long (exceptionally long strings)
[x] stringTest=X (short strings)
[x] stringTest=rtl (right-to-left)
[x] stringTest=xss (test passes if sim does not redirect, OK if sim crashes or fails to fully start)
[x] showPointerAreas (touchArea=red, mouseArea=blue)
[x] Full screen test
[x] Screenshot test
[x] Does AR need to be notified for any LOL updates?

If any new issues are found, please note them in https://github.com/phetsims/molarity/issues and reference this issue.
@ariel-phet please assign and prioritize

@samreid and @zepumph would you like us to test all of the phet-io wrappers for this test, or just add these two wrappers to the regular rc?

PhET-iO testing for a sim should include testing all of the wrappers linked from the landing page:
https://phet-dev.colorado.edu/html/molarity/1.4.0-rc.1/phet-io/
@jonathanolson is there a template you used to create this issue that I should update?

Also, @KatieWoe a reminder to reassign issues when asking a question, to make sure the intended recipients don't miss it.

I modified the main RC template in the QA repo.

@samreid so just to be clear, this a phet-io test, and not a normal rc, or is it both?

It is testing both the phet and phet-io brands, so it is essentially both.

We are striving to get to a point where RC's normally test PhET brand and PhET-iO brand at the same time.  I don't recall 100% of the conversation around Molarity but it seems we want to publish it for PhET and PhET-iO.

QA is done.  Note: testing for phet-io was done on Mac OS 10.12 as is indicated on the testing matrix, not on the newest OS 10.13.  Let me know if testing should be changed to test 10.13 instead.

Unassigning myself. (No issues found, so nothing for me to fix.)

Closing. @samreid and @zepumph will let @pixelzoom know when to publish the next RC, and whether to grab new SHAs for the release branch. Thanks for the testing!

Summary:
No sim-specific issues were found.  PhET-iO issues need to be addressed before proceeding with next RC.  Next RC test will be done in https://github.com/phetsims/QA/issues/166.


Update CSS on product list view icons

Update CSS properties on view icons on the product list page to be better looking

PR: GH-2600

QA:
Quick and small hotfix. Tested it using dev17 and will be moving it to Done to keep Server QA column clear for the release. I'll ask Brian to double check it again tomorrow to make sure.


Multi-files: prefetch resource

When dispatching multiple resources (#83), the browser prevents opening them all in new tabs.
The user will have to click on thumbnails.
Before she clicks, it would be nice to get the (not-displayed-yet) resources.

It is possible to initiate resource fetching, but this may slow down the display instead of speeding it up.
When pictures A, B, C are downloading in background, and I click on one thumbnail, the browser waits for this resource to be completely downloaded before displaying it.
When so prefetching is performed, the browser begins displaying streamed picture data as soon as I click the thumbnail.

https://github.com/Deleplace/cool-maze/tree/issues/127-prefetch-multiple-resources

Obsolete: all resources are E2EE now, which means they are already fully downloaded when shown in the web client.
Clicking does not open a remote URL in a new tab anymore. It displays the already-downloaded-and-decrypted picture, in a fullscreen lightbox.


Flow type definitions

I'm working on a flow type definition to submit to flow-typed. I have a few uncertainties, so I'm reaching out to ask for some help in typing redux-orm.
Here's the gist of what I'm working on: https://gist.github.com/B-Reif/772bdb132dc9597f1a014d15707167ba
Some questions/thoughts:

How should we type the Model's ref attribute? Should it be left up to the user & their inheriting classes?
How should we type createSelector? I have an existing definition in this gist, but it's not a sufficient description. I imagine it should be quite similar to reselect's type definition. (It's a little scary-looking but AFAIK the only way to type this kind of function signature.)
@keenondrums recently contributed a TypeScript definition. It has a few unsafe types under TODOs, but some of what's there can be used as a basis for flow typing.

Great!  You may also want to compare with this Flow types gist from @ahutchings : https://gist.github.com/ahutchings/357001da662addb30e45e15fe87206e2 .
Not sure on answers to your questions, though.

I've definitely considered that gist. It's a reasonable skeleton, but it has many unsafely typed fields.

Unless someone is willing to keep Flow types up-to-date I think we cannot support this officially. Would probably cause more harm than good to have outdated metadata in shipped code.


Card payment - invalid checksum

We have the following issue with the latest code (commit: 656b670ad09b16022fc6ca863b5beb00553e7da6).
Maybe something has changed on server side? @piotrjozwiak
Omnipay\Tpay\_class_tpay\Utilities\TException
0 : Card payment - invalid checksum. in file /webapps/vendor/omnipay/tpay/src/_class_tpay/PaymentCard.php line: 110

The above error points to the following lines:
        $hash = hash($this->cardHashAlg, $sale . $testMode . $saleAuth . $this->orderID . $this->clientAuthCode .
            $card . $this->currency . $this->amount . $saleDate . $status . $reason . $this->cardVerificationCode);
        if ($sign !== $hash) {
            throw new TException('Card payment - invalid checksum.');
        }

Here are the request details in case you would like to find at your system:

param
value

amount
1

card
****9891

currency
985

date
2021-10-07 14:33:35

order_id
835

sale_auth
[Filtered]

sign
de2eff1ba3fbbd6d28ca39611b16151d1b0675e522dcc7a321ad1070bb6e7dbf004bd816c335b9a2ce45eead664b54f330037975f333e4fc61efc9dc5c1e33d7

status
correct

type
sale

Please verify if there is need for update.

Hi @pszalko
We have just resolved the mentioned issue https://github.com/tpay-com/omnipay-tpay/pull/13


os.homedir() is only supported in node >= 4

@Tyriar please fix, I pushed a workaround here: https://github.com/Microsoft/vscode/commit/faffb7df995482275996535681d141e5a71560b8
I think we should still allow to build on older node.js versions unless there is a major reason otherwise.

@joaomoreno how exactly was the windows build breaking in 3a3c9e15? Doesn't the process.env['HOME'] only get evaluated if the task is called in to? It feels weird to do process.env[(process.platform == 'win32') ? 'USERPROFILE' : 'HOME'] here when it should never be run on Windows.

@joaomoreno oh I think I got it; because we create the gulp task by calling prepareRpmPackage, I'll fix it up.

:-1: 0.12 is not even LTS now. We should stop supporting it.


Make suntContent adapter an alias of seedingAlliance

https://github.com/prebid/prebid-server/pull/2420
PBS-Go implemented a copy of the seedingAlliance adapter, but they state in the PR that there will be divergent changes in the future.
Still for PBS-Java, we should just making sunt an alias of seedingAlliance until divergence is required.

Already in master


Move idempotency key architecture docs into main docs site

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@bb86b90). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Current head d6373e3 differs from pull request most recent head c10dbc3. Consider uploading reports for the commit c10dbc3 to get more accurate results

@@           Coverage Diff            @@
##             main     #1334   +/-   ##
========================================
  Coverage        ?   100.00%
========================================
  Files           ?       314
  Lines           ?     21447
  Branches        ?         0
========================================
  Hits            ?     21447
  Misses          ?         0
  Partials        ?         0


AssertionError "rev is None" in fuzzy_find_documents() after feat/rfc deployment

Describe the issue
After deploying v12.0.0, a call to document_pdfized() led to a failed assertion in fuzzy_find_documents()
The offending parameters were {'name': 'rfc4231', 'rev': '02'}
Traceback in a screenshot here because I don't have a better way to copy/paste at the moment

Code of Conduct

[X] I agree to follow the IETF's Code of Conduct

also seeing:
{'name': 'rfcdraft-ietf-httpbis-cookie-alone', 'rev': '01'}

I think the log.assertion was a mistake - this code deals with strings provided directly in urls which may be nonsense, and it should just not find anything matching the nonsense.


g_inner_map_mng.inner_map support persist in restart

What type of PR is this?
/kind enhancement

What this PR does / why we need it:
Since map_fd cannot be used universally in different processes,
map_fd needs to be converted into map_id and stored, and then
converted into map_fd in the corresponding process when the
configuration is restored.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

/lgtm
/approve