Add more K-S tests

Merge #1677 first.
ref. #1300

Jenkins, test this please.

Jenkins CI test (for commit 48e7aa25398aef312f64bea0ac22671065a9ea8f, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Jenkins, test this please.

Jenkins CI test (for commit b54695456620d78406f67f256cf427182c61249a, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Jenkins, test this please.

Jenkins CI test (for commit 81b53873a4aae194391daee4cb3199d172fd458e, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

The Jenkins failure (tests.chainer_tests.links_tests.normalization_tests.test_batch_renormalization.BatchRenormalizationTest_param_13.test_forward_multi_gpu) is unrelated to the PR.


Can't select multiple lines in the documentation window

Godot version:
master 321ce4d4c
OS/device including version:
Windows 10 Pro
Issue description:
We can't select multiple lines in the documentation window. Instead, the window just scrolls on dragging with left click.
Steps to reproduce:

Open any documentation in the editor.
Try to drag more than one line to copy some text or example code.

Closing in favor of #38665 as it better describes the issue at hand.


add ios dev scout as partners

would like to add iOS Dev Scout as Geekcamp's partner

@vinamelody please provide logo thanks!


Actions on workshop items do not work

Describe the bug
Voting, subscribing, adding to fav, (...), workshop items does not work. I know it's not a problem with your specific package (this also happens in the original project), but maybe you know an alternative solution.
To Reproduce
Steps to reproduce the behavior:

Create or download an item from the workshop.
Call item.Vote.
The result.Value is always 'Failure'.

Calling Code
                // 'item' is a Steamworks.Ugc.Item object
                var result = await item.Vote(true);
                if(!result.HasValue || result.Value != Steamworks.Result.OK)
                {
                    ShowMessage("Error", "An error occurred while submitting your request", 3);
                    return;
                }

Expected behavior
The vote should be published in the workshop item, but it is not.
Desktop (please complete the following information):

OS: Win64
WinUI3 C#.

Additional context
The rest of the functionalities work correctly (publish/download/update items, consult their information, etc.). It simply does not allow you to modify the information of the items in the workshop.

Nevermind, it was a mistake in my code. Sorry abt that.


Added redirection from herokuapp site

Not sure what the best routing path to put in app.get(), so feedback on that would be nice.
Aside from that, this seems to work on my localhost:3000. Took me a while to figure this out because chrome browser caches 301 redirects, so I spent a lot of time figuring out why my redirects were going to some change in the code that I had put in previously and not my current redirected site.
Anyway, hope this works. Please let me know where I can improve the code; I'm relatively new to this.
Thanks!

I'll check this out @vvayne. Can you add your name to userlist.js to become a member as well?

Note: this closes https://github.com/larvalabs/pullup/issues/235.

@vvayne, this is a good start, but you should change the app.get to app.use.
When you use app.get('*', ...), you create a HTTP GET handler function for every route. That's okay, but that's what middleware is for. Middleware functions are called before the handlers. To register a middleware function in Express, you use app.use() as in:
app.use(function(req, res, next) {
    if ( req.header("host") == "pullup.herokuapp.com") {
        res.redirect(301,'https://pullup.io');
    }
    next();  // Very important
});

Notice the next argument that's passed in and called at the end. You have to be sure to call this when your middleware function is done because it is essentially what says "ok, this is done proceed with the next middleware function or call the handlers". If you don't call next then the app will just hang waiting for your function to say it's done.
Note that this is essentially the entirety of the express-force-domain package, which you call with app.use as well (see docs here). If you want to learn more about Express middleware and app.use see this stackoverflow question.
Can you update to app.use like the sample above?

@vvayne I took care of making that change for you. See https://github.com/larvalabs/pullup/commit/f61af0dda555d0c00cb0d8a5ac8a33c971f87121.
Thanks!


Add note timestamp

Self-explanatory. Adding a timestamp (last modified) to notes.

In latest commit. Will be in next release.


Add LICENSE for cloneable_seekable_reader.rs from ripunzip

Summary

If I’ve correctly analyzed the file crates/uv-extract/src/vendor/cloneable_seekable_reader.rs as vendored and forked from https://github.com/google/ripunzip/blob/v0.4.0/src/unzip/cloneable_seekable_reader.rs, then this PR adds the corresponding license text from https://github.com/google/ripunzip/blob/v0.4.0/LICENSE.
This would therefore fix https://github.com/astral-sh/uv/issues/5584.
Test Plan

N/A; inspect for appropriate contents.

Thanks, I thought adding the header was sufficient but this seems correct.


CI initial setup

run tests for PRs, pushes to develop, main

feature branches?
make test results visible

Completed with 47447af0d9406ff987844ccdf36a4bb72ed61384 and 272c683b54fa13bc4f56de18c155f31eb9e4b634


New sharepoint token loaded on every page refresh

A new sharepoint token is loaded on every refresh of a page containing a sharepoint, regardless of if the previous sharepoint token has been consumed or not - this needs investigating.

This is the correct behaviour.


Allow building with base-compat-batteries-0.13.*

Very strangely, GitHub's UI appears to prevent me from merging this PR:

Any idea what is going on here?

Some further investigation reveals that the scotty repo has enabled the "Lock branch" option for the master branch, which prevents users from pushing to the branch at all (by pull request or otherwise). For the life of me, I can't imagine why this option would ever be useful for the master branch. There is a separate "Require pull request reviews before merging" option that is also enabled for master, which I believe more closely matches what was actually intended here.
I've opted to disable the "Lock branch" option and keep the "Require pull request reviews before merging" option. If this isn't what you want, please speak up. (And I apologize for disrupting your workflow if that is the case!)


"--wrap=auto | preserve| none" doesn't make any difference (HTML to OPML)

thank you for your great application.
I tried to convert my HTML to OPML.
I want --wrap=preserve. but, "auto" option is forcibly turned on.

Similar problem here, but for converting docx to markdown.
from pathlib import Path
import pypandoc

filepath = "./file.docx"
with Path(filepath).open("rb") as f:
    content = f.read()

print(pypandoc.convert_text(
    content,
    "markdown",
    format="docx",
    extra_args=["-s",  "--wrap=none"]
))

The output will be wrapped, ignore the --wrap=none argument.
But it does work when I use the equivalent pandoc command in the command line:
pandoc file.docx -t markdown -s --wrap=none

I'm using pypandoc v1.13 and pandoc <IP_ADDRESS>

@akuma73  I cannot reproduce this


Batch mark/unmark files as viewed

Context
Previously, when marking/unmarking a folder as viewed, a request was sent for every single file. This PR ensures that only one request is sent when marking/unmarking a folder as viewed.
Fixes #4520
Before
https://user-images.githubusercontent.com/7654793/229513098-670ad525-4e05-44ff-bd3e-10cab4781113.mp4
After
https://user-images.githubusercontent.com/7654793/229513184-fab21149-52b2-4b16-b23b-4f4a3b483383.mp4

I'm not a fan of this inlining. Is it possible to do without the inlining and instead have a new query in queries.gql

I spent a bit of time investigating this before raising this PR, but I couldn't find a way to do it. That said, I've never used graphql before outside of this project so I'm sure I'm missing something. I'll take another look this evening!

Thanks for the updates! In the future, it would make reviewing PRs much easier/faster for me if you don't force push your branch. It's hard to tell which files have changed since my last review after a force push.
I tested this out and it doesn't seem to work. I get this error:
stack trace: GraphQLError: Syntax Error: Cannot parse the unexpected character ".".
    at syntaxError (d:\repos\Microsoft\vscode-pull-request-github-2\dist\webpack:\vscode-pull-request-github\node_modules\graphql\error\syntaxError.js:15:1)
    at readToken (d:\repos\Microsoft\vscode-pull-request-github-2\dist\webpack:\vscode-pull-request-github\node_modules\graphql\language\lexer.js:360:1)
    at Lexer.lookahead (d:\repos\Microsoft\vscode-pull-request-github-2\dist\webpack:\vscode-pull-request-github\node_modules\graphql\language\lexer.js:75:1)
    at Lexer.advance (d:\repos\Microsoft\vscode-pull-request-github-2\dist\webpack:\vscode-pull-request-github\node_modules\graphql\language\lexer.js:58:1)
    at Parser.expectToken (d:\repos\Microsoft\vscode-pull-request-github-2\dist\webpack:\vscode-pull-request-github\node_modules\graphql\language\parser.js:1408:1)
    at Parser.parseName (d:\repos\Microsoft\vscode-pull-request-github-2\dist\webpack:\vscode-pull-request-github\node_modules\graphql\language\parser.js:98:1)
    at Parser.parseField (d:\repos\Microsoft\vscode-pull-request-github-2\dist\webpack:\vscode-pull-request-github\node_modules\graphql\language\parser.js:295:1)
    at Parser.parseSelection (d:\repos\Microsoft\vscode-pull-request-github-2\dist\webpack:\vscode-pull-request-github\node_modules\graphql\language\parser.js:284:1)
    at Parser.many (d:\repos\Microsoft\vscode-pull-request-github-2\dist\webpack:\vscode-pull-request-github\node_modules\graphql\language\parser.js:1523:1)
    at Parser.parseSelectionSet (d:\repos\Microsoft\vscode-pull-request-github-2\dist\webpack:\vscode-pull-request-github\node_modules\graphql\language\parser.js:271:1)
    at Parser.parseOperationDefinition (d:\repos\Microsoft\vscode-pull-request-github-2\dist\webpack:\vscode-pull-request-github\node_modules\graphql\language\parser.js:199:1)
    at Parser.parseDefinition (d:\repos\Microsoft\vscode-pull-request-github-2\dist\webpack:\vscode-pull-request-github\node_modules\graphql\language\parser.js:137:1)
    at Parser.many (d:\repos\Microsoft\vscode-pull-request-github-2\dist\webpack:\vscode-pull-request-github\node_modules\graphql\language\parser.js:1523:1)
    at Parser.parseDocument (d:\repos\Microsoft\vscode-pull-request-github-2\dist\webpack:\vscode-pull-request-github\node_modules\graphql\language\parser.js:115:1)
    at parse (d:\repos\Microsoft\vscode-pull-request-github-2\dist\webpack:\vscode-pull-request-github\node_modules\graphql\language\parser.js:31:1)
    at parseDocument (d:\repos\Microsoft\vscode-pull-request-github-2\dist\webpack:\vscode-pull-request-github\node_modules\graphql-tag\src\index.js:129:1)
    at gql (d:\repos\Microsoft\vscode-pull-request-github-2\dist\webpack:\vscode-pull-request-github\node_modules\graphql-tag\src\index.js:170:1)
    at _PullRequestModel.markFilesAsViewed (d:\repos\Microsoft\vscode-pull-request-github-2\dist\webpack:\vscode-pull-request-github\src\github\pullRequestModel.ts:1629:23)
extensionHostProcess.js:105
unhandledRejection {"message":"Syntax Error: Cannot parse the unexpected character \".\".","locations":[{"line":2,"column":25}]}
extensionHostProcess.js:105
rejected promise not handled within 1 second: Syntax Error: Cannot parse the unexpected character ".".

Huh okay. I'll see if I can reproduce that locally. I'll push up a fix if I can.

This completely dropped off my radar. I'll fix it up and send it back for review soon.
Given how long it's been, I rebased my branch rather than have a massive merge commit. This required a force push, sorry. I won't force push for any further changes.

@joshuaobrien very good timing, thanks for reviving the change! We are doing issue/pr clean up in December and your PR is at the top of my list of my list.


How to start more than one processes for a single task?

Is it possible to start multiple process for a single task? Start multiple client would be not so convenient

Hey @BrandonDotLin, we're working on some improvements for that, it will probably fix your goal by #130 merge.
In the meantime, there is a documentation on how to achieve multiple workers.
Long short story - just append as many workers as needed. Each one will work as a independent process, regardless of the task name.

This solved my problem. Thanks for your useful information.


#issue 3353:- Tindog sign up button border design

issue 3353 was to add sign u p button border design in Tindog

You should link your issue as
Closes #3353


Feature: pre-commit hooks

Closes #25. This adds a basic pre-commit set up that incorporates both pylint and black.
The first invocation of pre-commit generates the following output. I also highly suggest immediate action for this branch in order to propagate its effects to other branches. I'll also add more pre-commit hooks and write documentation the development setup.
$ pipenv run pre-commit install
$ pipenv run pre-commit run --all-files
Trim Trailing Whitespace.................................................Failed
- hook id: trailing-whitespace
- exit code: 1
- files were modified by this hook

Fixing README.md
Fixing docker-compose.yml
Fixing bot/cogs/admin.py

Mixed line ending........................................................Passed
pylint...................................................................Failed
- hook id: pylint
- exit code: 30

************* Module bot.cogs.admin
bot/cogs/admin.py:30:0: C0301: Line too long (104/100) (line-too-long)
bot/cogs/admin.py:66:0: C0304: Final newline missing (missing-final-newline)
bot/cogs/admin.py:1:0: C0114: Missing module docstring (missing-module-docstring)
bot/cogs/admin.py:4:0: E0401: Unable to import 'discord.ext.commands' (import-error)
bot/cogs/admin.py:22:4: W0622: Redefining built-in 'id' (redefined-builtin)
bot/cogs/admin.py:22:4: C0103: Variable name "id" doesn't conform to snake_case naming style (invalid-name)
bot/cogs/admin.py:23:4: R1705: Unnecessary "else" after "return" (no-else-return)
bot/cogs/admin.py:37:4: C0116: Missing function or method docstring (missing-function-docstring)
bot/cogs/admin.py:38:14: W1309: Using an f-string that does not have any interpolated variables (f-string-without-interpolation)
bot/cogs/admin.py:4:0: C0411: third party import "from discord.ext.commands import Bot, Cog, command, check" should be placed before "from bot.settings import BASE_DIR" (wrong-import-order)
************* Module bot.cogs.memes
bot/cogs/memes.py:1:0: C0114: Missing module docstring (missing-module-docstring)
bot/cogs/memes.py:1:0: E0401: Unable to import 'discord.ext.commands' (import-error)
bot/cogs/memes.py:5:0: R0903: Too few public methods (1/2) (too-few-public-methods)
************* Module bot.__main__
bot/__main__.py:1:0: C0114: Missing module docstring (missing-module-docstring)
bot/__main__.py:10:4: C0116: Missing function or method docstring (missing-function-docstring)
bot/__main__.py:3:0: C0411: first party import "from bot.meme_api import memegen" should be placed before "from . import settings" (wrong-import-order)
************* Module bot.cogs.utilities
bot/cogs/utilities.py:108:0: C0301: Line too long (103/100) (line-too-long)
bot/cogs/utilities.py:1:0: C0114: Missing module docstring (missing-module-docstring)
bot/cogs/utilities.py:2:0: E0401: Unable to import 'discord.ext' (import-error)
bot/cogs/utilities.py:3:0: E0401: Unable to import 'discord.ext.commands' (import-error)
bot/cogs/utilities.py:34:4: R0913: Too many arguments (7/5) (too-many-arguments)
bot/cogs/utilities.py:53:8: W0612: Unused variable 'after_create_reminder' (unused-variable)
bot/cogs/utilities.py:78:4: C0116: Missing function or method docstring (missing-function-docstring)
bot/cogs/utilities.py:136:4: C0116: Missing function or method docstring (missing-function-docstring)
************* Module bot.meme_api.memegen
bot/meme_api/memegen.py:38:0: C0301: Line too long (103/100) (line-too-long)
bot/meme_api/memegen.py:69:0: C0301: Line too long (105/100) (line-too-long)
bot/meme_api/memegen.py:1:0: C0114: Missing module docstring (missing-module-docstring)
bot/meme_api/memegen.py:1:0: E0401: Unable to import 'requests' (import-error)
bot/meme_api/memegen.py:7:0: C0115: Missing class docstring (missing-class-docstring)
bot/meme_api/memegen.py:19:41: C0103: Variable name "m" doesn't conform to snake_case naming style (invalid-name)
bot/meme_api/memegen.py:25:4: C0116: Missing function or method docstring (missing-function-docstring)
bot/meme_api/memegen.py:40:8: C0103: Variable name "r" doesn't conform to snake_case naming style (invalid-name)
bot/meme_api/memegen.py:42:8: R1705: Unnecessary "else" after "return" (no-else-return)
bot/meme_api/memegen.py:47:4: C0116: Missing function or method docstring (missing-function-docstring)
bot/meme_api/memegen.py:48:8: C0103: Variable name "r" doesn't conform to snake_case naming style (invalid-name)
bot/meme_api/memegen.py:49:8: C0103: Variable name "r" doesn't conform to snake_case naming style (invalid-name)
bot/meme_api/memegen.py:54:46: C0103: Variable name "f" doesn't conform to snake_case naming style (invalid-name)
bot/meme_api/memegen.py:59:4: C0116: Missing function or method docstring (missing-function-docstring)
bot/meme_api/memegen.py:62:12: C0103: Variable name "x" doesn't conform to snake_case naming style (invalid-name)
bot/meme_api/memegen.py:68:8: R1705: Unnecessary "else" after "return" (no-else-return)
bot/meme_api/memegen.py:69:81: C0201: Consider iterating the dictionary directly instead of calling .keys() (consider-iterating-dictionary)
bot/meme_api/memegen.py:3:0: W0611: Unused import os (unused-import)
bot/meme_api/memegen.py:2:0: C0411: standard import "import json" should be placed before "import requests" (wrong-import-order)
bot/meme_api/memegen.py:3:0: C0411: standard import "import os" should be placed before "import requests" (wrong-import-order)
************* Module bot.bot
bot/bot.py:1:0: C0114: Missing module docstring (missing-module-docstring)
bot/bot.py:1:0: E0401: Unable to import 'discord' (import-error)
bot/bot.py:2:0: E0401: Unable to import 'discord.ext' (import-error)
bot/bot.py:5:0: C0115: Missing class docstring (missing-class-docstring)
bot/bot.py:8:4: W0235: Useless super delegation in method '__init__' (useless-super-delegation)
bot/bot.py:5:0: R0903: Too few public methods (1/2) (too-few-public-methods)
bot/bot.py:1:0: W0611: Unused import discord (unused-import)
************* Module bot.cogs.greetings
bot/cogs/greetings.py:1:0: C0114: Missing module docstring (missing-module-docstring)
bot/cogs/greetings.py:1:0: E0401: Unable to import 'discord.ext.commands' (import-error)
bot/cogs/greetings.py:11:4: C0116: Missing function or method docstring (missing-function-docstring)
bot/cogs/greetings.py:4:0: R0903: Too few public methods (1/2) (too-few-public-methods)
************* Module bot.settings
bot/settings.py:1:0: C0114: Missing module docstring (missing-module-docstring)
************* Module bot.cogs.source
bot/cogs/source.py:7:0: C0301: Line too long (106/100) (line-too-long)
bot/cogs/source.py:51:0: C0301: Line too long (127/100) (line-too-long)
bot/cogs/source.py:52:0: C0301: Line too long (104/100) (line-too-long)
bot/cogs/source.py:1:0: C0114: Missing module docstring (missing-module-docstring)
bot/cogs/source.py:1:0: E0401: Unable to import 'discord' (import-error)
bot/cogs/source.py:2:0: E0401: Unable to import 'discord.ext' (import-error)
bot/cogs/source.py:31:33: W0212: Access to a protected member _cache of a client class (protected-access)
bot/cogs/source.py:10:0: R0903: Too few public methods (1/2) (too-few-public-methods)
bot/cogs/source.py:46:4: C0116: Missing function or method docstring (missing-function-docstring)
bot/cogs/source.py:39:0: R0903: Too few public methods (1/2) (too-few-public-methods)
bot/cogs/source.py:3:0: C0411: standard import "from typing import Union" should be placed before "from discord import Embed, Colour" (wrong-import-order)

------------------------------------------------------------------
Your code has been rated at 6.07/10 (previous run: 6.25/10, -0.18)

black....................................................................Failed
- hook id: black
- files were modified by this hook

reformatted Friendo_Bot/bot/__main__.py
reformatted Friendo_Bot/bot/cogs/admin.py
reformatted Friendo_Bot/bot/cogs/source.py
reformatted Friendo_Bot/bot/meme_api/memegen.py
All done! ✨ 🍰 ✨
4 files reformatted, 8 files left unchanged.

This PR should be ready for merging into develop; I had a bit of trouble setting up the pylint hook since I've only really worked with flake8. I suggest rigid testing and configuration in order to properly set this up @fisher60.

Looks great, no conflicts, linter worked. Awesome job!


Generate Synapse AccessControl LLC

Generation of the Synapse AccessControl library protocol methods.
See corresponding APIView here: https://apiview.dev/Assemblies/Review/89bac638188c43dc99cc2f82779ef006
Remaining work:

[ ] Add models to test grow-up story
[ ] Update Tests to use new API
[ ] Update Samples to use new API
[ ] Update Snippets

API changes have been detected in this PR. You can review API changes here

API changes have been detected in this PR. You can review API changes here

API changes have been detected in this PR. You can review API changes here

Returning to draft state to add tests.  CreateRoleAssignment test currently fails with 403.


Decide on approach for NuGet and Chocolatey Pack

Currently, the strategy that is used for creating NuGet and Chocolatey Packages is to store the nuspec file in source control.  Then, within build.cake, the NuGetPack and ChocolateyPack commands are used, to provide additional information, like version, releasenotes, files, etc.
However, the nuspec file is not actually required, as NuGetPack and ChocolateyPack can both create temp files, which are then used to do the actual creation of the nupkg's.
The first approach means some duplication of properties, like Copyright, Owners, etc, which could be made into consts within the build.cake file.
We need to make a decision about how to move forward with this.

I prefer to use nuspecs, but if we move this to code then I think we at least should put it in another .cake file to reduce clutter.

This can now be closed.  We have settled on the approach, i.e. use a nuspec so that things are consistent.


[BEAM-4733] Pass pipeline options from Python portable runner to job server.

The Python portable runner client doesn't pass the pipeline options to the job service. Backport of  change from prototype from @lukecwik fixes this. Is a similar change needed for Go @herohde ?
Added extra commit to fix Flink runner executable stage streaming translation.

There was some discussion about what to do here that wasn't formalized or completely figured out about PipelineOptions and the job server API. For know I believe the intention was to have the job server configured explicitly from the command line when being launched and not to take PipelineOptions per job.
For know, we should stick with passing Python PipelineOptions through as an opaque blob and not worry about the internal representation or having a runner/job server look at them.
CC: @angoenka @jkff

A runner can look at whether any of the PCollections are unbounded instead of relying on --streaming. The SDK should pass options through but for now we are attempting to prevent the runner from inspecting them until someone has time to think of a good story around how runners and PipelineOptions interact.

I used --streaming as a non-exclusive example for pipeline options that the runner needs to understand (we discussed it a while ago and it was implemented accordingly)
Please take a look at FlinkPipelineOptions - there are several other options like parallelism and checkpointing interval that a user needs to be able to set.
I think a basic story will be better than no story. Since you have authored the approach that is adopted here, are there any issues following it until someone has time to come up with something better (I suspect that we have many more important things to tackle till then).

Your right, we'll have to do something temporary till something better comes along.

Run Flink ValidatesRunner


Fix: Modal and screen closing with single esacpe keypress

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/5769
Tests | QA Steps

Navigate to Workspace settings on the web.
Navigate to members
Check one from the list of members and click on the remove button.
Once the remove modal appears, press the esc button.
Only Confirm modal should close.
Press Esc again.
Now the Settings Modal should close.

Tested On

[x] Web
[ ] Mobile Web [No Escape key]
[x] Desktop
[ ] iOS [No Escape key]
[ ] Android [No Escape key]

Screenshots

Web | Desktop

https://user-images.githubusercontent.com/24370807/137516779-ce4417d9-6607-47a6-9382-b9481e6bb942.mp4
Mobile Web

Desktop

iOS

Android

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by @Julesssss in version: 1.1.8-10 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

This PR could have prevented this bug https://github.com/Expensify/App/issues/18558. The willAlertModalBecomeVisible call is only made on componentDidUpdate. We should have made this call on componentDidMount as well to cover the cases where the modal is initially rendered visible.


enable contextcheck linter

Signed-off-by: Matthieu MOREL<EMAIL_ADDRESS>

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 54.839%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4250

Relevant Lines:
7750

💛  - Coveralls


image is showing in outer div box in cart page

Bug report
Title
image is showing out of div box in cart page
Issue Description
image is showing out of div box in cart page
Preconditions
1. framework Version- master

Steps to reproduce
1. step1- add a product image with max-height
2. step2- now add to cart the product and go to the cart page

Expected result
the image should not out from the div box
Actual result

Hello @vaishaliwebkul  Can you assign me this ticket ?

Fixed in master.

https://prnt.sc/v9yccs fixed


Is it possible to send push notifications to all subscribers without database at all?

Once the user has subscribed, we need to pass their subscription ID to our server so that it can be saved securely in the database. Our server receives this request and saves the data to a database for use later on.
Is it possible to send push notifications to all app subscribers without saving subscription IDs into database at all?
Looks like it's possible to add all subscription IDs to a one topic (https://firebase.google.com/docs/cloud-messaging/js/send-multiple#subscribe_the_client_app_to_a_topic) using XHR/fetch POST request during user subscription process on client side and later send push notifications to this topic instead of send to each subscription ID from database.
But according to https://developers.google.com/instance-id/reference/server#create_relationship_maps_for_app_instances, adding to topic requires use Authorization: key=YOUR_API_KEY parameter in request.
Is YOUR_API_KEY a secret key that should never be included in any client code?

@gauntface, cc.

Yes the API key should be kept secret.
While you won't need a database to store subscriptions, you will need some server to perform the subscribing to a topic (Not just because of the API secret, but also because I believe CORs isn't enabled for the API).

CORs isn't enabled for the API
What API you mean? Google Instance ID API?

Unfortunately, Firebase Notifications is not available for Web.
Does Firebase Notifications for Android and iOS requires saving subscription IDs into database to send push notifications to all app subscribers?

The main idea of Firebase is use it instead of own back-end.
I can use Firebase Database for storing subscription IDs, but in this case, I still need some admin panel to extract subscription IDs from Firebase Database and trigger push messages to them.
This admin panel can be front-end app (e.g. Polymer web app with PolymerFire) that extracts subscription IDs from Firebase Database and send POST requests for each ID. But I think it's not a good idea, because if I close the app in the browser during sending POST requests process, push notifications will be sent to not all subscribers. What you think?
The admin panel can be back-end app (e.g. Node.js app like https://github.com/gauntface/web-push-book/tree/master/src/demos/node-server), but in this case, I need some Node.js hosting for real production use. Do you know good free Node.js hosting? It kills the idea of using Firebase only instead of own back-end.
It's possible to send push notifications without own admin panel using Notifications tab of the Firebase console, but it available only for Android and iOS, not Web.

You can have a local node script that will get the subscriptions and post messages (i.e. it doesn't need to be hosted anywhere.
Regarding CORS: I'm referring the the endpoint reference in: https://firebase.google.com/docs/cloud-messaging/js/send-multiple#subscribe_the_client_app_to_a_topic

@gauntface

I believe CORs isn't enabled for the API

Looks like you are wrong.
Just checked to run the following code
var key = 'YOUR-SERVER-KEY';
var token = 'YOUR-IID-TOKEN';
var topic = 'YOUR-TOPIC';

fetch('https://iid.googleapis.com/iid/v1/' + token + '/rel/topics/' + topic, {
  'method': 'POST',
  'headers': {
    'Authorization': 'key=' + key,
    'Content-Type': 'application/json'
  }
}).then(function(response) {
  console.log(response);
}).catch(function(error) {
  console.error(error);
})

on HTTPS served page, and all works like a charm!

Awesome :)

@gauntface Could you please answer to my question

Does Firebase Notifications for Android and iOS requires saving subscription IDs into database to send push notifications to all app subscribers?

BTW, any info when Firebase Notifications will come to Web to send push notifications from Firebase console?

Android and iOS SDK's are very similar to web, the only difference is there is a provided API on the SDK's to subscribe an FCM token to a topic (As you've done in the previous step).
Sorry, I don't know the plan for the Firebase console.

Hi I have a question
What is YOUR-IID-TOKEN?
is it a ID token that get with auth().currentUser.getIdToken(true) or
is it a API Key of some google APIs (OAuth 2, API Key..) or
is it some of Firebase Project ?
I have tried several times
Thanks

I believe it's the token for the user (i.e. the messaging token).

Where to get the "IID TOKEN"?

Is it possible to get the IID TOKEN (while subscibing) withotu using firebase libraries (using just a fetch or a get or whatever the firebase library does)

Unfortunately, Firebase Notifications is not available for Web.
Does Firebase Notifications for Android and iOS requires saving subscription IDs into database to send push notifications to all app subscribers?

Scammer!!!


AttributeError: 'Collection' object has no attribute 'model_fields'

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
def create_selector():
    try:
        vectorstore = Chroma()
        vectorstore.delete_collection()
        selector = SemanticSimilarityExampleSelector.from_examples(
            examples,
            llm_embeddings,
            vectorstore,
            k=1,
            input_keys=["input"],
        )
        return selector
    except Exception as e:
        logger.error(e)
        return None

Error Message and Stack Trace (if applicable)
'Collection' object has no attribute 'model_fields'
Description
I'm trying to use Chroma vectorstore in Langchain, and receive the error above. Error appeared when calling Chroma() function.
System Info
OS: Ubuntu
OS Version: Ubuntu 22.04
Python Version: 3.10.12
Packages
langchain==0.2.5
langchain-chroma==0.1.2
langchain_community==0.2.5
langchain-openai==0.1.8

I am on Mac and having the same issue.

Downgrading to chromadb==0.5.3 worked for me. The 0.5.4 version was released yesterday.

Downgrading to chromadb==0.5.3 worked for me. The 0.5.4 version was released yesterday.

Thanks @mbastian for the solution, it worked for me also.

If this is a bug in chromadb 0.5.4 should it remain open?

Downgrading to chromadb==0.5.3 worked for me. The 0.5.4 version was released yesterday.

It finally worked for me too. Thanks!

same problem with 0.5.4 in windows

worked for me too. Thanks Buddy :)

Downgrading to chromadb==0.5.3 worked for me. The 0.5.4 version was released yesterday.

I'm still facing the same issue with 0.5.3 version as well

Downgrading to chromadb==0.5.3 worked for me. The 0.5.4 version was released yesterday.

I'm still facing the same issue with 0.5.3 version as well

Same error for chromadb 0.5.3 , I'm using MAC M3

Same issue even when downgrading, and I am working on Databricks.

Downgrading to chromadb==0.5.3 worked for me. The 0.5.4 version was released yesterday.

Thanks @mbastian for the solution, it worked for me also.

Hi, could you reopen the issue ? This should be fixed by the langchain team as it is a bug :)

This is a bug with chromadb it seems... versions 0.5.5 and 0.5.4 both don't work and throw this error when starting a new collection, but version 0.5.3 does. I am using llama-index, not langchain, so I don't think this is a bug with langchain.

same problem with 0.5.5 in windows
version 0.5.3 does

I encountered this issue with LlamaIndex and the downgrade also worked for me. Thanks for the fix!

Downgrading to chromadb==0.5.3 worked for me. The 0.5.4 version was released yesterday.

I'm still facing the same issue with 0.5.3 version as well

I was also facing the issue, then restarting the kernel and then running all the cells in my ipynb file worked for me, after downgrading chromadb to 0.5.3 version

it works on me too. thanks!

same problem with 0.5.5 in windows
i tired chroma==0.5.4 ,0.5.3,0.5.1, stopped kernel and reran jupyter,,,have no idea......

Downgrading to chromadb==0.5.3 worked for me. The 0.5.4 version was released yesterday.

Thanks man

Downgrading to chromadb==0.5.3 worked for me. The 0.5.4 version was released yesterday.

Worked for me too.. Please fix it asap

It seems that this is the error version of the chromadb .I saw you guys can work with the chromadb==0.5.3,but I also can't work with the langchain.
this is my code:
from langchain_chroma import Chroma
vectorstore = Chroma.from_documents(
documents,
embedding=OpenAIEmbeddings(),
)
and it will cause the same error like this:
AttributeError: 'Collection' object has no attribute 'model_fields'
how should I do can resolve this problem?thx.

@cc17 This worked for me using chromadb==0.5.3

@cc17 This worked for me using chromadb==0.5.3

it works,thx.

same issue when using chromadb on Sagemaker - had to downgrade

downgrade work for me also on mac

Downgrade to 0.5.1 works for me on Windows.


Add support for plain text request body

Is your feature request related to a problem? Please describe.
It should be possible to have endpoint with a full plain text request body like
  /dummy:
    post:
      requestBody:
        description: (to be documented)
        content:
          text/plain:
            schema:
              type: string
        required: true

Today it is completely ignored
Describe the solution you'd like
In openapi._add_body() we should have a additional line
        text_body, schemas = Endpoint.parse_request_text_body(
            body=data.requestBody, schemas=schemas, parent_name=endpoint.name, config=config
        )

And
    @staticmethod
    def parse_request_text_body(
        *, body: oai.RequestBody, schemas: Schemas, parent_name: str, config: Config
    ) -> Tuple[Union[Property, PropertyError, None], Schemas]:
        """Return text_body"""
        body_content = body.content
        text_body = body_content.get("text/plain")
        if text_body is not None and text_body.media_type_schema is not None:
            return property_from_data(
                name="text_body",
                required=True,
                data=text_body.media_type_schema,
                schemas=schemas,
                parent_name=parent_name,
                config=config,
            )
        return None, schemas

Describe alternatives you've considered
Additional context

I can probably provide a PR

I am facing the same issue for response. text/plain does not seems to be supported


Replace template ND values by 1D values.

It appears that we haven't been using the optimized kernels for the FaceQuadratureInterpolator due to the instantiation of the kernels with ND template values instead of 1D template values.

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#2301
@YohannDudouit
@tzanio
@artv3 + @camierjs
06/07/21
06/08/21
06/09/21

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

It looks like @YohannDudouit posted "done" two time but there were no corresponding commits -- @YohannDudouit, did you forget to push?


Fails when getting "b1" account

JsonReaderException: Could not convert string to integer:<PHONE_NUMBER>50. Path 'net_weight', line 1, position 271.
Will probably also fail on cpu_weight. Should be something larger than Int32.

This https://github.com/GetScatter/eos-sharp/commit/fcae0cc7eea786956ab835286e110f345e4c6b6b fixs it. Give it a try


Adding php imap and calander extension support.

I checked that install-php-extensions supports imap and calender php 7.0 -> 8.2


Do not register /nick short command on servers even if enabled in config

The command only really makes sense when using the client at the moment anyways.

Actually, no, never mind. The server should just disable them. There's really no reason to have it enabled on servers. So instead, check the default value of this option.


About training speed

Hi, This is awesome work！I love lt！
But, I have some problem....
I found the taining speed may not as faster as i expected
here is my use analyze_logs.py:
slowest epoch 49, average time is 1.1886
fastest epoch 11, average time is 0.9775
time std over epochs is 0.0323
average iter time: 1.0163 s/iter
this means for one epoch it's need about 4 hours....
the same net on darknet only need about 1 hours for one epoch
Is there any good suggestion here?

Please provide more training details, such as cfg, log, envs, etc.


Remove unnecessary config.json file from the project

Describe the bug
There is an unused config.json file for configuring algolia search. Since it is implemented using a workaround we don't need the file anymore.
Reproduction
https://github.com/arclix/arclix-docs
Steps to reproduce
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Arclix issue and not a React specific issue.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion.
[X] Please follow minimal reproducible example of the bug.

[ Triaged ] Good to start development


Enable IO and UpdateTest types

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

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

Enables types in Library/Homebrew/extend/io.rb and Library/Homebrew/dev-cmd/update-test.rb
Note that this is a bit clumsy in one case, where we mark an lvar as untyped. This is because Utils.popen_read resists a straightforward sig (The return type is the return type of the block given to it, or a String otherwise. Sorbet allows multiple sigs in the Ruby core and std libraries in order to express this, but doesn't allow it otherwise.)

Note that this is a bit clumsy in one case, where we mark an lvar as untyped. This is because Utils.popen_read resists a straightforward sig (The return type is the return type of the block given to it, or a String otherwise. Sorbet allows multiple sigs in the Ruby core and std libraries in order to express this, but doesn't allow it otherwise.)

Very interesting!

Thanks again @dduugg! Happy to chat more post-merge.


Add support for 1.3.0. contracts on web v1

What is this feature about? (1 sentence)
This adds support for Safe contracts 1.3.0 on L2.
Implementation details
New safes created on L2 should target contract 1.3.0.
New safes on mainnet/rinkeby should still target 1.1.1.
Both new and old safes, both 1.3.0 and 1.1.1 should work with the Safe app.
The contract API is almost the same between 1.3 and 1.1. The only difference is that we need to pass the chain id when doing off-chain signatures.
This method receives a new chainId param in 1.3: https://github.com/gnosis/safe-react/blob/42291e12088f5a53b3b2ea680d2185deb47b276c/src/logic/safe/store/actions/transactions/utils/transactionHelpers.ts#L35
So to support both 1.1 and 1.3 in the frontend code, we’ll need to check which version of the Safe this is and add or not add an extra chain id param to the tx type.
What needs to be updated in the code

Mastercopy address needs to be configurable for L1 and L2 based on the env (i.e. domain)
Even between L2s, the address needs to be configurable since it can differ.
Update the proxy factory
Fallback manager (on creation)
A conditional in the transactionHelpers to add chainId for off-chain signatures on 1.3.0

@dasanra , @katspaugh and @francovenica , as it was discussed during the retro I suggest to check test cases prepared for the big feature to make sure that all important cases are covered
There is the link on the test cases - https://gno.testrail.io/index.php?/suites/view/851&group_by=cases:section_id&group_id=3486&group_order=asc&display_deleted_cases=0
Some questions have been added to the suite description


string index out of range

while using auth/users/create/ .... i am getting string index out of range at the time of sending confirmation and activation email...
email backend and setting are all aright and i have not override any function

Hi @xzibiit
It's most probably connected to https://github.com/sunscrapers/django-templated-mail/issues/4 - I'll release a new version of this dependency today.
I'm very sorry for the trouble it has brought.

I've released a new version of the dependency, which should resolve the problem. To update you can simply issue pip install -U djoser or pipenv install if you are a pipenv user. In case it doesn't fix it, please let me know.

Thanks for support ...Its working fine


Hotswap Keyword Additions

In the tools current state, a user must restart the service if they would like to add a new keyword. This is not much of a problem if running manually, but assuming a user wants to script the addition of keywords, it becomes sightly annoying.
Potential Solutions:

Daemonize the service to make restarting a natural behavior
Create an observer that polls for new keywords

Perhaps another two solutions:

listen on stdin for new keywords
add-in zeromq and use that for multi-way IPC (unix socket, tcp/ip ...)

As for the observer option: inotify could be a solution

Right now we take in keywords through a file. Do you agree that more logic should exist on this function so that it can be extended to handle the above cases as well as keywords being stored in the database?

Pretty much so but prior to doing that, I'd like to create some sort of config parsing so that a user won't have to edit gather.py by hand.
Then, finish the sql table layout and finally, adding keyword selection by db is simple enough through an additional column keyword_enabled BOOL for the sql ones. add in a signal handler for, say, SIGUSR1, and one can trigger a reload.

a quick heads up. I'm working on finishing the config file format(s).
So far I've got a usable raw python config format but I'm also working on something ini-base (stdlib ConfigParser)
Python example:
https://gist.github.com/1745091
Ini example:
https://gist.github.com/1745137

This is so cool. It's reached a point where I am reluctant to commit, because there is so much you have thought out and planned for (not necessarily a bad thing).

It's reached a point where I am reluctant to commit

That's what branches and issue trackers are for; that way, one can keep in touch/sync

This is so cool.

Well thank you :)

because there is so much you have thought out and planned for

There's still plenty that I haven't planned, it's just hard to find those ;)

Finished the implementation for the config system, but I believe it needs a bit more testing before it can be merged.
branch config on my forked repo contains an install guide (INSTALL) and two config examples (in directory examples).
gather, harvest and snatch have been replaced with install-time scripts pastycake, -harvest, -snatch.


Fix occasionally failing API authorization

If you have a long running process doing the SMS stuff, you will end up with occasional "TurboSMS::SendingSMSError: Вы не авторизированы" happening from time to time, because the cookie got expired, or the server deleted the session associated with it. Creating new session on every call may be a bit slower (I'm not sure it is), but at least your messages will be delivered.
Maybe there's a better way, but I got that going for me, which is nice.
Also my editor couldn't resist fixing whitespaces in the file, sorry for that. The only important part is line 29.

Did you recognize the expiration timeout for cookies?

No, and I think it's not the cookies' fault. My guess is that TurboSMS server deletes sessions deliberately on its side, I don't know if by some timeout, or completely randomly. Maybe the session gets deleted if you don't call the API for some time, and if you're using API often enough, it's never deleted.
I was getting the error constantly something like once in 1-3 days. With this fix, there wasn't even one in 3 months.
If you are using this gem, are you sure you're not getting the errors?. Try grepping logs for the error message, or hook up a monitoring tool something like Rollbar or NewRelic.

I saw this error few times but I'm sending sms in background, so the job will retry after failing. I suggest you to send sms (mail, etc) in same way.

I'll try to contact with TurboSMS support team and to get a real cause of this issue.

@hnatt as TurboSMS support team said to me cookie session has 1 day expiration timeout. I will invalidate cookies in 12 hours after authorization. So feel free to use updated version (0.1.3) of this gem.

@vitalikdanchenko thanks!


DataFusion weekly project plan (Andrew Lamb) - Dec 18, 2023

Follow on to Dec 11 2023:
Boilerplate Overview
The idea of this ticket is make my plans for DataFusion visible, largely for my own personal organizational needs, but also to:

Try some different ways to communicate / coordinate in the community
Help provide an interesting summary of what is happening in DataFusion this week

It would be great if anyone else who has plans like this for DataFusion could try to make them visible somehow as well
My (personal) plans for this week

[ ] Shepherd next PRs through for https://github.com/apache/arrow-datafusion/issues/8376
[ ]  https://github.com/apache/arrow-datafusion/issues/8491
[ ] Reproduce other bugs / limitations we have hit while upgrading DataFusion in InfluxDB IOx

Project Queue (list of future projects)

[ ] https://github.com/apache/arrow-datafusion/issues/8227 (specifically, https://github.com/apache/arrow-datafusion/issues/8229 as a step towards https://github.com/apache/arrow-datafusion/issues/8078)

Projects I hope to help review and coordinate

[ ] https://github.com/apache/arrow-datafusion/issues/8130, in support of memory explosion in HashJoin outputs: https://github.com/apache/arrow-datafusion/issues/7848
[ ] Next steps towards function packages more modular (make all BuiltInScalarFunctions ScalarUDFs): https://github.com/apache/arrow-datafusion/issues/8045 with @2010YOUY01 and @edmondop . This week I hope to help get https://github.com/apache/arrow-datafusion/issues/8157 complete, and move on to https://github.com/apache/arrow-datafusion/pull/8046
[ ] Review any new ticket / bug reports

Algorithm for (my) prioritizing PR reviews
Note there are many committers who can and review and merge PRs, so this is not the priorities of the project as a whole, just the approximate algorithm I am using
Priority:

Bug fixes (where something is just incorrect), especially regressions (where it used to work and now does not)
Improvements directly related to features needed for InfluxDB (my employer)
Documentation and test improvements (I view these as very strategically important)
PRs that I think are strategically important
Other new features / additions to functionality

The current strategically important projects in my head are:

Making function packages modular and easier to mix/match: https://github.com/apache/arrow-datafusion/issues/8045
Improving performance of high cardinality aggregation (I have dreams of working on this over Christmas break)

Thus, if you are interested in contributing to DataFusion and are interested in a fast turn around time I would recommend looking into bug fixes / test improvements / documentation / etc.
If you propose adding new functionality, the review cycle will likely be longer. You can make it a shorter cycle by looking at the comments on other recent PRs and following the same model (e.g. ensure there are tests in sqllogictest for example, the CI passes, includes documentation, etc)

Review queue
Datafusion

[ ]  https://github.com/apache/arrow-datafusion/pull/8558
[ ] https://github.com/apache/arrow-datafusion/pull/8317
[ ] https://github.com/apache/arrow-datafusion/pull/7942
[ ] https://github.com/apache/arrow-datafusion/pull/8562
[ ] https://github.com/apache/arrow-datafusion/pull/8565
[ ] https://github.com/apache/arrow-datafusion/pull/8560
[ ] https://github.com/apache/arrow-datafusion/pull/8363

Arrow

[ ] https://github.com/apache/arrow-rs/pull/5186
[ ] https://github.com/apache/arrow-rs/pull/5217

sqlparser-rs:

[ ] https://github.com/sqlparser-rs/sqlparser-rs/pull/1063
[ ] https://github.com/sqlparser-rs/sqlparser-rs/pull/1062

Review queue
Datafusion

[ ] https://github.com/apache/arrow-datafusion/pull/8580
[ ] https://github.com/apache/arrow-datafusion/pull/8570
[ ] https://github.com/apache/arrow-datafusion/pull/7942
[ ] https://github.com/apache/arrow-datafusion/pull/8562
[ ] https://github.com/apache/arrow-datafusion/pull/8565

Arrow

[ ] https://github.com/apache/arrow-rs/pull/5186

sqlparser-rs:

[ ] https://github.com/sqlparser-rs/sqlparser-rs/pull/1063
[ ] https://github.com/sqlparser-rs/sqlparser-rs/pull/1062

sqlparser-rs

[ ] https://github.com/sqlparser-rs/sqlparser-rs/pull/1061

@alamb any chance that you'll get around to reviewing this soon-ish? https://github.com/apache/arrow-datafusion/pull/7581. Really appreciate it!

DataFusion:

[ ] https://github.com/apache/arrow-datafusion/pull/8558
[ ] https://github.com/apache/arrow-datafusion/pull/7581

DataFusion

[ ] https://github.com/apache/arrow-datafusion/pull/8595#pullrequestreview-1794424409
[ ] https://github.com/apache/arrow-datafusion/pull/8608
[ ] https://github.com/apache/arrow-datafusion/pull/8558
[ ] https://github.com/apache/arrow-datafusion/pull/7581


[crypto] Use nextgen-crypto signing across Libra

Motivation
Removing the remaining usages of the legacy crypto signing API from the code base, most notably the functions in tests generating keypairs based on the old random generation.
Have you read the Contributing Guidelines on pull requests?
YES
Test Plan
existing

@huitseeker, rebased to resolve conflicts after your merge, will need a new stamp.


Fixed secure cookie option.

backport

Released: https://github.com/plone/volto/releases/tag/15.8.1


hasMany goods update

When I update goods in cart 1, all goods in athers cart update same id.
https://carts.rzk.com.ua/

Link to access firebase data https://jsfiddle.net/7L20cboj/5/

Solution create unique ID cart_id+goods_id

can you show me how you defined the model in models/cart.js? I think you have an object prototype issue where each instance of a cart has a single shared goods object in the prototype.

Closing this due to no response. Please reopen with example of how you're defining the models an assigning the goods property.

// models/cart.js
export default DS.Model.extend({
    timestamp: DS.attr('number'),
    summ: DS.attr('string'),
    ordered: DS.attr('boolean', {defaultValue: false}),
    goods: DS.hasMany('good', {async: false})
});

// model/good.js
export default DS.Model.extend({
  timestamp: DS.attr('number'),
  goods_id: DS.attr('string'),
  name: DS.attr('string'),
  price: DS.attr('number'),
  qty: DS.attr('number'),
  unit: DS.attr('string'),
  summ: Ember.computed('price', 'qty', function() {
    return Math.round(this.get('price') * this.get('qty') * 100) / 100;
  });
});

I see you have set async:false, have you also created a file serializers/cart.js? See the instructions for embedded records.

This should be your serializer:
// app/serializers/cart.js
import FirebaseSerializer from 'emberfire/serializers/firebase';
export default FirebaseSerializer.extend({
  attrs: {
    goods: { embedded: 'always' },
  }
});

If that still doesn't work. try setting inverse null:
goods: DS.hasMany('good', {async: false, inverse: null}),

@tstirrat this dont help
https://carts.rzk.com.ua/

can you show me the code where you create the goods and assign them to a cart?

Data saved correct,
// Firebase rest api

    	$firebase = new \Firebase\FirebaseLib('https://rzk-com-ua.firebaseio.com');

    	$cart = array(
		    "summ" => $cart->subtotal(2, '.', ' '),
		    "timestamp" => time() * 1000,
		    "ordered" => false
		);

	    //$request->session()->forget('firebase_cart_id');
		$firebase_cart_id = $request->session()->get('firebase_cart_id');

		$goods = [
            "goods_id" => $request->id,
			"name" => $request->name,
			"price" => $request->price,
			"qty" => $request->qty,
			"unit" => $request->unit,
			"timestamp" => time() * 1000
        ];

        if ( $firebase_cart_id ) {

          $firebase->update("carts/$firebase_cart_id", $cart);

          if (!$request->qty) {
            $firebase->delete("carts/$firebase_cart_id/goods/$request->id");
          } else {
            $firebase->update("carts/$firebase_cart_id/goods/$request->id", $goods);
          }

        } else {

          $firebase_cart_id = $firebase->push('carts/', $cart);
          $array_fireid = json_decode($firebase_cart_id);
          $request->session()->put('firebase_cart_id', $array_fireid->name);
          $firebase->update("carts/$array_fireid->name/goods/$request->id", $goods);

        }

        // Firebase rest api

I think I see what's happening. If you give a good the same id as another good, it will overwrite that record in Ember Data, this is not an problem specific to EmberFire, its just how the Ember Data store works. So yes, it looks like you might be assigning duplicate ids.
You might want a new model. You have Cart and Good. If a cart needs to have different quantity and sum for each good, you should be storing that in a separate record. e.g. CartItem
// models/cart.js
export default DS.model({
  sum: DS.attr('number'),
  items: DS.hasMany('cartItem', {async: false, inverse: null}), // embedded
});

// serializers/cart.js
export default FirebaseSerializer.extend({
  attrs: {
    items: { embedded: 'always' },
  }
});

// models/cart-item.js
export default DS.model({
  qty: DS.attr('number'),
  good: DS.belongsTo('good', {async: true, inverse: null}),
  sum: DS.attr('number'),
});

// models/good.js
export default DS.model({
  name: DS.attr('string'),
  price: DS.attr('number'),
});

In your back end use push to get a new unique id for each new CartItem object before saving.
$entry = [
    "good" => $request->id, // no need for *_id suffix here
    "sum" => $request->price,
    "qty" => $request->qty,
    "unit" => $request->unit,
    "timestamp" => time() * 1000
];

if ( $firebase_cart_id ) {

  $firebase->update("carts/$firebase_cart_id", $cart);

  if (!$request->qty) {
    $firebase->delete("carts/$firebase_cart_id/items/$request->id");
  } else {
    $firebase->push("carts/$firebase_cart_id/items", $entry); // push here to get auto id
  }

}

I think, best way:
Solution create unique ID cart_id+goods_id

I don't know much about your app, so it is hard to know what qty means.
cart_id+goods_id will work.

Going to close this issue. Please continue the discussion as needed.

Thanks @tstirrat! I keep you advised
Now I have more analysts, Total sales as orders made particular product.
TOP 100 Goods
// models/good.js
export default DS.model({
  name: DS.attr('string'),
  price: DS.attr('number'),
  unit: DS.attr('string'),
  qty: DS.attr('number'),
  orders: DS.attr('number'),
  timestamp: DS.attr('number')
});

/routes/goods.js
export default Ember.Route.extend({
  model() {
    return this.get('store').query('good', {
      orderBy: 'qty',
      limitToLast: 100
    });
  },
  titleToken: 'Goods'
});


about intl versions

I use intl and flutter_flavourizr simultaneously in my application as follows.

intl: ^0.18.1(or ^0.19.0)
flutter_flavorizr: ^2.2.3

flutter pub get requires intl:0.18.1 as shown below

:flutter pub get --no-example
Resolving dependencies...
Note: intl is pinned to version 0.18.1 by flutter_localizations from the flutter SDK.
See https://dart.dev/go/sdk-version-pinning for details.

Because my_app depends on flutter_localizations from sdk which depends on intl 0.18.1, intl 0.18.1 is required.
So, because my_app depends on intl ^0.19.0, version solving failed.

You can try the following suggestion to make the pubspec resolve:

Consider downgrading your constraint on intl: flutter pub add intl:^0.18.1
exit code 1

flutter build ipa requires intl:0.19.0 as follows

:flutter build ipa  and :flutter build appbundle --flavor production
Resolving dependencies...
Note: intl is pinned to version 0.19.0 by flutter_localizations from the flutter SDK.
See https://dart.dev/go/sdk-version-pinning for details.

Because my_app depends on flutter_localizations from sdk which depends on intl 0.19.0, intl 0.19.0 is required.
So, because my_app depends on intl ^0.18.1, version solving failed.

You can try the following suggestion to make the pubspec resolve:

Try upgrading your constraint on intl: flutter pub add intl:^0.19.0

flutter clean is performed.
It started happening after I changed the Flutter version to 3.22.1.
You can also run flutter build ipa by setting intl:0.19.0.
Why are there different versions required?

:flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.22.1, on macOS 14.5 23F79 darwin-arm64, locale ja-JP)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 15.4)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.2)
[✓] VS Code (version 1.89.1)
[✓] Connected device (5 available)
[✓] Network resources

I changed Flutter version to 3.22.2.
flutter build ipa and flutter pub get both work fine.
I'm sorry for troubling you.
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.22.2, on macOS 14.5 23F79 darwin-arm64, locale ja-JP)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 15.4)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.2)
[✓] VS Code (version 1.90.1)
[✓] Connected device (4 available)
[✓] Network resources


Improve .chunk method

size arg should go first
improve tests

https://github.com/lambdamusic/dimcli/tree/v_0.5


New container with latests WRF

https://github.com/bakamotokatas/WRF-Install-Script/blob/master/WRF4.5_Install.bash

We will need to add MET as part of our process and methodology https://github.com/NCAR/container-dtc-nwp

Include some of the utilities from here https://github.com/wrfchem-leeds/python-scripts

And this tool for the execution of WRF https://github.com/elpahlevi/pyWRF-automation


Start container as non-root user

First of all, thanks for the image. Following best practices I learned that it's best to not start containers as a root user.
When I switch to the node user though, I get "permission denied" error:
Error: EACCES: permission denied, open '/usr/local/lib/node_modules/pm2/node_modules/array-unique/index.js'
    at Object.fs.openSync (fs.js:651:18)
    at Object.fs.readFileSync (fs.js:553:33)
    at Object.Module._extensions..js (module.js:579:20)
    at Module.load (module.js:503:32)
    at tryModuleLoad (module.js:466:12)
    at Function.Module._load (module.js:458:3)
    at Module.require (module.js:513:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/usr/local/lib/node_modules/pm2/node_modules/micromatch/lib/utils.js:13:16)
    at Module._compile (module.js:569:30)

Is there a way to start this container as non-root user, i.e. assuming user "node". When doing so, for what files and directories do I need to change ownership to that new user?

@Unitech any thought on this?

I ran into this problem as well.
As a Linux n00b I discovered several issues with this:

npm has been installed by the root user in the original node:alpine image
installing pm2 therefor is only possible using the root user as well
executing pm2 as a different user is not possible because it has been installed as root, so it gives you "permission denied"

To run NPM and PM2 using a different user I've created my own image with the following tweaks:
RUN chown -R USER:GROUP $(npm config get prefix)/lib/node_modules
RUN chown -R USER:GROUP /usr/local/bin/pm2

@Unitech maybe we can add the @jvduf workaround to the readme. What do you think about?

I've been experimenting some more...
This might be a cleaner option and is also suggested solution as per https://docs.npmjs.com/getting-started/fixing-npm-permissions
RUN mkdir /home/USERNAME/.npm-global \
    && npm config set prefix '/home/USERNAME/.npm-global' \
    && export PATH=/home/USERNAME/.npm-global/bin:$PATH \
    && npm install -g pm2

This is part of my Dockerfile:
RUN addgroup -g 9999 app && adduser -u 9999 -G app -D app -s /bin/bash \
    && apk upgrade --update \
    && apk add --no-cache \
       bash bash-completion \
       git

#    && npm install -g pm2
# RUN chown -R app:app $(npm config get prefix)/lib/node_modules
# RUN chown -R app:app $(which pm2)

COPY ./bash/.bash* /home/app/

USER app
ENV HOME=/home/app/
WORKDIR $HOME

RUN mkdir /home/app/.npm-global \
    && npm config set prefix '/home/app/.npm-global' \
    && export PATH=/home/app/.npm-global/bin:$PATH \
    && npm install -g pm2


Restrict interface type. Disallow additional properties or strictly check type.

Bug Report / Feature Request / ?
🔎 Search Terms
interface, restrict, disallow, additional properties, etc. In various combinations. Hard to find better words at this moment. Thinking in progress... (ETA: pending) 🤤
🕗 Version & Regression Information
Tested with 4.3.5 and 4.6.2 and the nightly 4.7.0-dev20220302.
⏯ Playground Link
💻 Code
interface Apple {
  id?: string;
  /** [cm] */
  value: number;
}

interface Pear {
  name: string;
  /** [grams] */
  value: number;
}

class Test {
  public write(obj: Apple): void {
    console.log(obj);
  }
}

const test = new Test();

const pear: Pear = {
  name: 'WTF',
  value: 2
}

// No error. You can pass a pear as apple.
// It's not really a bug. But not expected / wanted here.
// How to allow only apples here? No pears!
test.write(pear);

🙁 Actual behavior
You can pass pears as apples. Pass interface with another meaning. It's perhabs no bug. But keep reading the expected behavior...
🙂 Expected behavior
I expect an error here. Don't pass pear as apple. Strictly allow Apple interface only.
The interface Pear has additional property name which is not allowed in interface Apple. I would except it if I use this:
interface Apple {
  id?: string;
  value: number;
  [additionalProp: string]: unknown;
}

I not sure, but it's probably not a bug. The pear object is compatible to interface Apple because it has the property value. And id is optional. We could argue about the name. Because the Apple has no property name. But even if we have to interfaces with just one property value. How to restrict the interface to only that interface what is specified?
It's ok if I pass a literal object. But in this case I branded an object explicitly to an interface type. The object has explicitly the type Pears and is passed to Apples. TypeScript know it. But only checks the property. I think this is intended. Using classes may fix it. But is there no way to work with interfaces here? - So, sorry I can't mark that issue clearly as bug, feature request or docs/question.

What you're asking for is Exact Types (#12936).

Also see the FAQ: https://github.com/microsoft/TypeScript/wiki/FAQ#what-is-structural-typing

Ok thanks for info. I close this as duplicate of the referred issue. I'll post a comment to it (with a workaround I found).


Rename the audio FFT_Size enum to FFTSize for consistency

Follow-up to https://github.com/godotengine/godot/pull/37700.
I noticed this while working on https://github.com/godotengine/godot/pull/48681.

Thanks!


Fix langserver tests

Purpose

Fix langserver tests

Check List

[ ] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[x] Checked Tooling Support (#)
[ ] Added necessary tests

[x] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

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

@@           Coverage Diff           @@
##           master   #18726   +/-   ##
=======================================
  Coverage   15.57%   15.57%
=======================================
  Files          47       47
  Lines        1220     1220
  Branches      184      184
=======================================
  Hits          190      190
  Misses       1016     1016
  Partials       14       14

Continue to review full report at Codecov.

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


Upgrading to storybook 4.0.0

Also handles the bug noted in #10

Is this change backward compatible? I haven't had the chance to test with storybook < 4, but it doesn't look like it is compatible. If it is not, then it should be changed to be backward compatible. I think it would be backward compatible if the render function is  (opts) => <StatePanel channel={channel} api={api} active={!opts || opts.active} />. I don't know if storybook < 4 passes any parameter to the render function, so this might not work.
An alternative would be a major version change. That would also be a good time to switch to storybook 4 decorator parameters and get rid of the legacy function formats.

Hi @dump247. IMO, it's better to bump the major version because it's not backward compatible. Shall we merge this pr and bump the major version first? thus, we can do more optimization upon the new version.

What is the consensus? v2.0.0 bump?

Any chance to go ahead and merge this with a major bump? This is a blocker for most of us to update to v4.


Upcoming matches

Hello! How can I get upcoming matches? Is it possible? There's only matches history(

Unfortunately there are no Valve APIs for upcoming matches that I know about.  Several sites maintain their own calendars, but they're not official.

@howardchung thanks a lot!

@howardchung What do you think about this method from Stream Api? "Matches" GET method with parameters ("from" - Integer, Minimum timestamp) and ("to" - Integer, Max timestamp).

I don't think it will return matches in the future


Python syntax error in dynamically generated 'build/gyp-mac-tool' file when python3 on the PATH is < 3.6

Node Version:  Latest 10, 12, 14 and 15 (10.24.0, 12.21.0, 14.16.0, 15.12.0)
Platform:  macOS "Catalina" 10.15.7
Compiler:  Apple clang version 12.0.0 (clang-1<IP_ADDRESS>)
Module:  git-utils, leveldown, superstring

Verbose output (from node-gyp rebuild --verbose):
% /Users/[user]/node-gyp/bin/node-gyp.js rebuild --verbose
gyp info it worked if it ends with ok
gyp verb cli [
gyp verb cli   '/Users/[user]/n-prefix/bin/node',
gyp verb cli   '/Users/[user]/node-gyp/bin/node-gyp.js',
gyp verb cli   'rebuild',
gyp verb cli   '--verbose'
gyp verb cli ]
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| darwin | x64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb find Python Python is not set from command line or npm configuration
gyp verb find Python Python is not set from environment variable PYTHON
gyp verb find Python checking if "python3" can be used
gyp verb find Python - executing "python3" to get executable path
gyp verb find Python - executable path is "/Library/Frameworks/Python.framework/Versions/3.10/bin/python3"
gyp verb find Python - executing "/Library/Frameworks/Python.framework/Versions/3.10/bin/python3" to get version
gyp verb find Python - version is "3.10.0"
gyp info find Python using Python version 3.10.0 found at "/Library/Frameworks/Python.framework/Versions/3.10/bin/python3"
gyp verb get node dir no --target version specified, falling back to host node version: 15.12.0
gyp verb command install [ '15.12.0' ]
gyp verb install input version string "15.12.0"
gyp verb install installing version: 15.12.0
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version is already installed, need to check "installVersion"
gyp verb got "installVersion" 9
gyp verb needs "installVersion" 9
gyp verb install version is good
gyp verb get node dir target node version installed: 15.12.0
gyp verb build dir attempting to create "build" dir: /Users/[user]/github/node_modules/superstring/build
gyp verb build dir "build" dir needed to be created?  System Darwin 19.6.0
gyp ERR! command "/Users/[user]/n-prefix/bin/node" "/Users/[user]/node-gyp/bin/node-gyp.js" "rebuild" "--verbose"
gyp ERR! cwd /Users/[user]/github/node_modules/superstring
gyp ERR! node -v v15.12.0
gyp ERR! node-gyp -v v7.1.2
gyp ERR! not ok

More info:
Only node-gyp from git master is affected; The latest release to the npm package registry 7.1.2 is unaffected.
The error looks like this:
  File "./gyp-mac-tool", line 252
    fp.write(f"{package_type}{signature_code}")
                                             ^
SyntaxError: invalid syntax
make: *** [Release/superstring_core.a] Error 1

When this error occurs, it's always the same syntax error at line 252 of gyp-mac-tool. Some (most?) packages appear to be unaffected, but I've found a few packages which are affected:  git-utils, leveldown, and superstring.
  Given that we plan to drop those versions, I do not see the problem.

It occurs with stable Python 3 as well. Such as Python 3.8.2 currently shipped with command line tools for Xcode.

https://github.com/nodejs/node-gyp/blob/e81602ef55023cc8ffeebc5509a9a8649d60434d/gyp/pylib/gyp/mac_tool.py#L1 has a #!/usr/bin/env python header so maybe it's not using the version of Python you're expecting it to.

I always use #!/usr/bin/env python3 now that Py2 is dead.

@richardlau that seems to have been the problem.
The problem goes away if that shebang line is changed to #!/usr/bin/env python3, or if I make python on my PATH point to Python 3 (Python 3.8.2 in my case).

Modifying all shebang lines to add the 3 seems like the safest approach.

I humbly suggest updating to use gyp-next 0.8.1, where the shebang lines have already been updated.
I think ./update-gyp v0.8.1 does it? I can submit a Pull Request for that if desired...

I have a tentative fix for this. (https://github.com/DeeDeeG/node-gyp/commit/8250dec748790152d829e2c2c7ab248b7237b47d)
Implementation notes:
I changed gyp/pylib/gyp/generator/make.py so that the generated Makefile includes the absolute PATH to Python that lib/find-python.js found. I recorded this as a Makefile variable CONFIG_PYTHON. But I also made the logic check if that Python executable still exists on disk; if not, I had it fall back to the Python specified in the shebang line of gyp-mac-tool. (CONFIG_PYTHON is an empty string if the Python executable no-longer exists on the disk.)
So in the end we have: $(CONFIG_PYTHON) ./gyp-mac-tool rather than simply ./gyp-mac-tool.
The reason I didn't just hard-code a Python path found by find-python.js is, I realized that the Makefile is generated during node-gyp configure, and any arbitrary amount of time could pass before running node-gyp build. In the time that passes between these commands, someone could uninstall a version of Python in order to upgrade to a new Python, they could reinstall their OS but preserve the built package in their home directory, or they copy-pasting their repository to a new machine... So to avoid regressing on that and introducing a new common failure mode, I made sure to fall back to the shebang Python if the Python find-python.js found once upon a time is no-longer on the disk.

Caveat: This relies on reading the PYTHON env var that is set during node-gyp configure, based on the result of find-python.js.
This fix is only relevant to node-gyp where we can rely on the PYTHON env var being set to a helpful value by lib/find-python.js. And in fact, other projects might be using the PYTHON env var for a different purpose, so this change might be disruptive for other projects in general. So I'm not sure exactly where to land this fix. Landing it in gyp-next's main branch seems a bit questionable. Some options:

Land this in the main branch of gyp-next, despite it not being relevant to everyone and potentially being disruptive.

I'd prefer not to do this on gyp-next's main branch, since I don't think other projects would need this outside of node-gyp, but maybe the implementation could be less disruptive by using a more specific and unlikely to overlap env var like GYP_MAC_CONFIG_PYTHON or NODE_GYP_FOUND_PYTHON?

Land this in an alternative branch at the gyp-next repository for node-gyp specific tweaks, and have the gyp-next maintainers tag new node-gyp-specific variants of each release of gyp-next for node-gyp to consume.
I could set up ./update-python in this project to automatically cherry-pick this fix after every sync with the gyp-next repo. A very basic system for curating and automatically applying patches to gyp for the node-gyp project.

I did a little research on how the nodejs/node repository handles this.
They actually do their own Python detection, looking for python3.9 ... python3.6 or python2.7... And whichever they find first, they symlink to ./out/tools/bin/python. They have a Makefile for the overall node repo that puts this on the PATH, sets an env var (if not yet defined) PYTHON=python (which means the symlinked Python is used if the user doesn't specify a PYTHON env var before running make).
If we could set up a similar Python symlink in the build dir for packages we're building, during node-gyp configure, and have that respected during node-gyp build, that would be great.

In general, I think we need to either:

Write a full Python path to a file, or
Make a Python symlink

And commit that to disk during node-gyp configure, so that said path or symlink can be used during node-gyp build.
Any advice on an implementation approach would be much appreciated. If I don't get any advice, I suppose I'll keep improvising and see what I can come up with.
I think patching gyp is an easy-to-author but less-easy-to-maintain option, so I'm continuing to look to alternatives that don't involve patching gyp. If folks here are comfortable maintaining patches to gyp specifically for node-gyp, please do let me know, as I have a solution in the form of patching node-gyp that's ready to go. I even figured out a system to float the patches and automatically land them. Any interest/input/advice from maintainers would help me pick a specific direction to pursue here. I'd really like to fix this bug. Thanks.

Awesome detective work @DeeDeeG Thanks much for digging into the details.
It would be great if Node.js and gyp shared a common method for finding the right Python to use.  Unless others have objections, I believe that creating a symlink at a well known path is the best approach.  That would be easiest to reason about and easiest to test.

Re: @cclauss

It would be great if Node.js and gyp shared a common method for finding the right Python to use.

If you mean full code deduplication across these two projects, some of the duplicate code in either repository could be moved into gyp itself. Although I am not so versed in Python to be able to fluently code this feature in Python, my Makefile generator patch is an example of at least recording an absolute Python path within the gyp codebase. Somehow the "find the right Python to use" part seems odd to me to include in gyp directly, but it should still be possible if that's what you meant.
If you meant we should use a similar algorithm or perform the same checks to find a usable Python binary/decide which Python is the right Python to use, even if technically the code is still duplicated, then I don't see why not. At least we should "compare notes". For example, their idea of checking python3.9 ... python3.6 is neat, and we could use that as the fallback check on Unix, similar to the default install paths we currently check on Windows...
nodejs/node's checks are here: https://github.com/nodejs/node/blob/master/configure

Now that the shebangs in gyp are python3 I updated the issue title.
This issue now affects anyone with python3 older than 3.6 first on their PATH... who were able to supply the path to a working, newer Python version earlier in node-gyp's run. Such as with the PYTHON env var, or the npm config item npm_config_python.


Marketo - Streaming

Any update on this one?

Please to review @wilg ?

Yup. http://developers.marketo.com/rest-api/bulk-import/
Best,
-d
On Jun 8, 2018, 4:39 PM -0400, Wil Gieseler<EMAIL_ADDRESS>wrote:

@wilg commented on this pull request.
In src/actions/marketo/marketo.ts:

let response

await request.streamJsonDetail({

 onFields: (fields) => {

   fieldset = Hub.allFields(fields)

   let hasTagMap

   for (const field of fieldset) {

     hasTagMap = field.tags.map((tag: string) => {if (tag.startsWith("marketo:")) {

       return tag.split("marketo:")[1]

     }})

     fieldMap[field.name] = hasTagMap.find((tag: string | undefined) => tag !== undefined)

   }

 },

 onRow: async (row) => {

Does marketo support a batch API?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

implemented in a different way


chore: fix license auto update

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Include PLUMgrid plugin to DriverLog

Add PLUMgrid Fuel plugin to DriverLog

Thank you for contributing to openstack/driverlog!
openstack/driverlog uses Gerrit for code review.
If you have never contributed to OpenStack before make sure you have read the
getting started documentation:
http://docs.openstack.org/infra/manual/developers.html#getting-started
Otherwise please visit
http://docs.openstack.org/infra/manual/developers.html#development-workflow
and follow the instructions there to upload your change to Gerrit.


Floating IP documentation

We need to have documentation for the floating IP, I would suggest keeping the documentation in the current repo in Wiki section.

https://github.com/majidkarimizadeh/leaseweb-go-sdk/wiki/Floating-Ip


Hi @rahulbhalley , sorry for the delay. Could you try to build a toolchain against the latest HEAD of the tensorflow branch? https://github.com/apple/swift/pull/25967 fixed the major issue and it could resolve your OOM problem. We'll release another 0.4 release candidate later today.

Hi @rahulbhalley , sorry for the delay. Could you try to build a toolchain against the latest HEAD of the tensorflow branch? https://github.com/apple/swift/pull/25967 fixed the major issue and it could resolve your OOM problem. We'll release another 0.4 release candidate later today.
Originally posted by @rxwei in https://github.com/Ayush517/S4TF-Tutorials/issues/8#issuecomment-509236841

Hey @rxwei I tried to build Swift for TensorFlow from source as you suggested but I keep on getting an error during the build process. The steps I followed are as following:
Installed CMake, Ninja and Bazel (downloaded and installed with bazel-0.25.2-installer-darwin-x86_64.sh script from Bazel website).
brew install cmake ninja
brew cask install java

Bazel I have installed is v0.25.2
(py27) Rahuls-MacBook-Pro:swift-source rahulbhalley$ bazel version
WARNING: --batch mode is deprecated. Please instead explicitly shut down your Bazel server using the command "bazel shutdown".
Build label: 0.25.2
Build target: bazel-out/darwin-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Fri May 10 20:50:40 2019<PHONE_NUMBER>)
Build timestamp:<PHONE_NUMBER>
Build timestamp as int:<PHONE_NUMBER>

I created directory for Swift source code and then cloned Swift with tensorflow branch.
mkdir swift-source
cd swift-source
git clone https://github.com/apple/swift.git -b tensorflow
./swift/utils/update-checkout --clone --scheme tensorflow

Now when I started to build Swift for TensorFlow the error occurred at about 60% process completion:
/opt/local/include/unicode/ucnv.h:52:10: fatal error: 'unicode/ucnv_err.h' file not found
#include "unicode/ucnv_err.h"
         ^~~~~~~~~~~~~~~~~~~~
1 error generated.
[2056/3406][ 60%][2029.143s] Linking CXX static library lib/libclangDaemon.a
ninja: build stopped: subcommand failed.
swift/utils/build-script: fatal error: command terminated with a non-zero exit status 1, aborting

Any idea what's going wrong? Should I use tensorflow-0.4 branch instead?


Bugfix: Guest Image

这个 PR 实现什么功能/修复什么问题:

guest image 支持 generate_name 创建
解决一个bug：使用主机镜像创建主机时，所有盘的类型都会变成系统盘
子镜像只允许改备注
修复主机做完主机镜像后不能自动启动
修复主机镜像的项目不对
添加主机镜像更新的状态，防止主机镜像更新完子镜像还没有更新完就被前端拉取展示了

是否需要 backport 到之前的 release 分支:

release/2.12

Codecov Report

Merging #3472 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #3472      +/-   ##
=========================================
- Coverage    6.98%   6.98%   -0.01%
=========================================
  Files         496     496
  Lines       82855   82856       +1
=========================================
- Hits         5788    5786       -2
- Misses      76577   76579       +2
- Partials      490     491       +1

Flag
Coverage Δ

#aFlag
6.98% <0%> (-0.01%)
:arrow_down:

Impacted Files
Coverage Δ

pkg/mcclient/options/servers.go
0% <ø> (ø)
:arrow_up:

pkg/compute/guestdrivers/virtualization.go
0% <0%> (ø)
:arrow_up:

pkg/compute/models/guest_actions.go
0% <0%> (ø)
:arrow_up:

pkg/compute/models/disks.go
0.63% <0%> (ø)
:arrow_up:

pkg/appsrv/response.go
66.15% <0%> (-3.08%)
:arrow_down:

Continue to review full report at Codecov.

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

/area region glance

/cc @wanyaoqi

/area image

/lgtm

/needs-backport

/need backport

/lgtm
/approve


Reordered task instructions in Elyses Enchantments exercise

The exercise "Elyses Enchantments" had instructions that did not match the order in which they appeared in the online editor.
I switched the position of the instructions based on the order they had in the code. I also reordered the hints for each task so that they matched the new order.

LGTM. Thanks for the update @nasch92

@nasch92 Good catch!


[cxx-interop] Add test for lifetimebound annotation in ctor

It looks like everything worked out of the box, no code changes required. Added a test to avoid regressions.

@swift-ci please smoke test linux


Fix command info

1. Why is this change necessary?
Almost got a heartattack when seeing the info message. Wrong text for the migration
2. What does this change do, exactly?
exchange redis with sql
3. Describe each step to reproduce the issue or behaviour.

4. Please link to the relevant issues (if any).

5. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/NEXT-22156
Please use this issue to track the state of your pull request.


Just a suggestion

Thle line "This library will ONLY work with XLSX files" should be at the very most top of the Readme file & page

Done!


Fix diff tree height and adjust target file style

Extract from https://github.com/go-gitea/gitea/pull/23553, just the parts that fix the diff tree height and the change to the file :target style.
Fixes: https://github.com/go-gitea/gitea/issues/23593

🎺 🤖


Build fails on Android 30 due to blue-pair-secret.properties  file is missing

Hi Aurasphere,
Could you please share this file, as I'm not sure about the parameters I should be setting in this file
2021-09-06T13:02:01.460+0530 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] A problem occurred evaluating project ':app'.
2021-09-06T13:02:01.461+0530 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] > /home/android/AndroidTestApp/blue-pair/blue-pair-secret.properties (No such file or directory)
Thanks,
Divya

Duplicate issue


Error 401: UNAUTHENTICATED

Hello,
I've been struggling with this for hours now, if not days and can't seem to fix it.
My Requests to Cloud Functions are being denied with error code: 401: UNAUTHENTICATED.
My Code is as follow:
    putenv('GOOGLE_APPLICATION_CREDENTIALS=' . FIREBASE_SERIVCE_PATH);

    $client = new Google_Client();
    $client->useApplicationDefaultCredentials();
    $client->addScope(Google_Service_CloudFunctions::CLOUD_PLATFORM);
    $httpClient = $client->authorize();

    $promise = $httpClient->requestAsync("POST", "<MyCloudFunctionExecutionUri>", ['json' => ['data' => []]]);
    $promise->then(
        function (ResponseInterface $res) {
            echo "<pre>";
            print_r($res->getStatusCode());
            echo "</pre>";

        },
        function (RequestException $e) {
            echo $e->getMessage() . "\n";
            echo $e->getRequest()->getMethod();
        }
    );
    $promise->wait();

I'm currently executing this from localhost as I'm still in development phase.
My FIREBASE_SERIVCE_PATH constant links to my service_account js
My Cloud Function index.js:
const functions = require('firebase-functions');
const admin = require('firebase-admin');
admin.initializeApp();

// CORS Express middleware to enable CORS Requests.
const cors = require('cors')({
  origin: true,
});

exports.testFunction = functions.https.onCall((data, context) => {
    return new Promise((resolve, reject) => {
        resolve("Ok:)");
    });
  });
  // [END all]

My Cloud Function Logs:
Function execution took 459 ms, finished with status code: 401
What am I doing wrong so I get Unauthenticated?
PS: My testFunction works perfectly when invoked from my Flutter mobile app who uses: https://pub.dartlang.org/packages/cloud_functions
Update:
I have followed this guide: https://developers.google.com/api-client-library/php/auth/service-accounts but in the "Delegating domain-wide authority to the service account" section, it only states If my application runs in a Google Apps domain, however I wont using Google Apps domain, and plus I'm on localhost.

If this issue is relevant to you, please see here for an answer: https://stackoverflow.com/questions/54818119/google-php-api-client-i-keep-getting-error-401-unauthenticated.


gnome-builder is not packaged

According to https://areweideyet.com/#gnome-builder gnome-builder is quite good at supporting Rust, but there's no way of testing it on NixOS today.
Maybe someone experienced with gnome packages could do this in little time, otherwise I'll dig into it in the mid-term future.

Geary is a reasonably packaged example of GNOME app. Feel free to ping me here or on IRC if you need any help.

Added in #44217.