horizontal layout wrap doesn't work on safari

I have tried this a couple of times but children of a parent div with horizontal layout wrap don't wrap in safari. It works in Chrome (using v41) and firefox (using v.35.0.1). Using Polymer v0.5.4

It seems to work for me on Safari 8: http://jsbin.com/sosimetude/1/edit

@frankiefu  Thanks for the jsbin. I modified your sample code to conform to my use case to reproduce the issue here: http://jsbin.com/gixixevujo/2/edit. When you adjust the width of the window, you can tell its doesn't wrap in safari but it does in chrome and firefox. This seems to occur when the children element have percentage width, with a min-width.

@frankiefu Want to check if this bug is planned for a release. I have an app out which relies on this layout. I'm hoping to tell my users till will be fixed soon.

Closing this issue due to age and the release of version 1 of Polymer - please feel free to re-open if this is incorrect.


How do I configure Viya 3.5

How do I configure Viya 3.5 clientID, secret code, access token etc?
I went by https://blogs.sas.com/content/sgf/2021/09/24/authentication-to-sas-viya/
Couldn't get it working.  step 5 fails, syntax error.  Is there a step by step somewhere in this channel for configuring Viya to accept connections from VSCode users?   struggling ..

Hi @bmorse61. From the blog post you linked, you should use the access token generated in Step 4. Put the contents of the access token in a file and use the "Token File" value, in your profile in the settings.json file, to point to the file location.
Profile creation is outlined in the Profiles section of the GitHub documentation.

With v0.1.1, now you only need step 1 and 2 in the blog post to generate a client ID/secret for Viya 3.5. Please refer to the latest README.

No user feedback for a while. Closing.


libkbfs: add a journaling-specific dirty block cache

This will prevent journaled writes from messing up the buffer counts and backpressure for synchronous writes.
Most of the line changes are due to adding a new TlfID parameter to the DirtyBlockCache methods, so we can direct calls to the appropriate DirtyBlockCache.
We also need to prevent journal enabling/disabling while there is, or might be, dirty data coming in to the dirty block cache.  For now, if there are any outstanding operations that might dirty data on ANY TLF, or if there is any dirty data already, don't allow any TLF to switch its journaling status, because it will mess up the state of the DirtyBlockCache.
Issue: KBFS-1266

lgtm after rebase and comments


Added linter

Added .editorconfig
Create linter.yml
Fixed all code style issues

It is very cool commit.
Can you please separate linter setup and all fixes in 2 PRs?
There are some pending PRs now and it would be difficult to merge it.

Of course

Removed the formatting fixes in the files.
Left the minimum configuration, so you can configure it to the needs of the project.


add utility module

Need a module with all the utility functions

i think you should use pytest instead of unittest:

pytest is more literate - you just add test_stuff.py with test functions and pytest automatically registers this as tests, no class stuff that early programmers may not understand.
pytest magically deconstructs asserts so errors report the LHS and RHS of an assertion.  I think this works through partial disassembly of the test code but it is extremely helpful when asserts fail. assert

the "hello" container uses continuous testing with pytest not unittest.  I don't know if pytest notices unittest tests.

pytest finds and runs unittest framework. It gives the same level of details results when LHS and RHS assertion fails unless I'm missing something. I force student to use unittest in the upper division courses and use basic assert statement in lower.


[FP]: commons-validator being identified as Apache James

Package URl
<EMAIL_ADDRESS>CPE
cpe:2.3:a:apache:james:1.7:*:*:*:*:*:*:*
CVE
CVE-2021-38542
ODC Integration
{"label"=>"Gradle Plugin"}
ODC Version
7.0.0
Description
No response

Fix in current snapshot by #4148

Thanks, I've copied the suppression from the head of master into my local suppression file & it is working as expected


Agent refactoring - Moving IoT Hub related code into IoTHubClientModule extension

This is the first part of changes that enable DU Agent to support different communication channels.

Adding new Agent Module interface.
Moving IoT Hub related codes in to /extensions/agent_modules/cloud_communciation/iothub_client

Please ensure windows build succeeds--seems to be failing currently: https://dev.azure.com/azure-device-update/adu-linux-client/_build/results?buildId=13400&view=results
CMake Error at src/extensions/agent_modules/cloud_communication/iothub_client/module/CMakeLists.txt:23 (target_link_libraries):
  Target "iothub_client_module" links to:
-- Generating done (2.0s)

    aduc::command_helper

  but the target was not found.  Possible reasons include:

    * There is a typo in the target name.
    * A find_package call is missing for an IMPORTED target.
    * An ALIAS target is missing.

Please ensure windows build succeeds--seems to be failing currently: dev.azure.com/azure-device-update/adu-linux-client/_build/results?buildId=13400&view=results
CMake Error at src/extensions/agent_modules/cloud_communication/iothub_client/module/CMakeLists.txt:23 (target_link_libraries):
  Target "iothub_client_module" links to:
-- Generating done (2.0s)

    aduc::command_helper

  but the target was not found.  Possible reasons include:

    * There is a typo in the target name.
    * A find_package call is missing for an IMPORTED target.
    * An ALIAS target is missing.

Fixed

Getting this error now--likely fix is to #include <aducpal/unistd.h>:
https://dev.azure.com/azure-device-update/adu-linux-client/_build/results?buildId=13407&view=logs&j=66c25936-86b6-5530-73fe-1980d9bce5f6&t=c9298a61-188d-5631-1d08-e0c0d4457cdc&l=763

ERROR: Build failed (Error 1)

Compiler errors:
* src\utils\parson_json_utils\src\parson_json_utils.c (18,10): Cannot open include file: 'unistd.h': No such file or directory [parson_json_utils.vcxproj]


Cannot open telegram link after switch account

Describe the bug
I'm trying to build mini app where user can access interesting channel, group ...
For the first time user start telegram, they click on the button "Open" contain telegram link. It will open perfectly. But when user switch to another account and start mini app, click open button, it not go to channel/chat
If user want to open link inside mini app, they have to quit telegram and then start telegram again
Code i'm using to open telegram link
import WebApp from "@twa-dev/sdk";

export const openTelegramLink = (link: string) => {
try {
if (typeof window !== "undefined") {
WebApp.openTelegramLink(link)
}
} catch (error) {
console. log (error);

Telegram link sample: https://t.me/tapps_bot
Steps to reproduce
Step 1: Create simple mini app, add button "Open" open telegram link when click. Sample: https://t.me/tapps_bot, link of Telegram Apps Center bot
Step 2: Start Telegram with Account A, open mini app and click button "Open", it will redirect to chat with Telegram Apps Center
Step 3: Close mini app, switch to Account B, open mini app, click button "Open", it still good
Step 4: Close mini app, switch to Account A, open mini app, click button "Open", now nothing happen, some time miniapp has disappear
Step 5: Quit telegram, start again so it will be open link perfectly from step 1
Expected behavior
I expected user still go to chat with Telegram Apps Center, still can open link after switch account many times
How often does this bug happen?
Always when following these steps
Platform
OS: MacOS Monterey 12.7.6
Chrome: Version 130.0.6723.117 (Official Build) (x86_64)
NextJs: 14.2.13
Package Version
@twa-dev/sdk": "^8.0.1"
"typescript":"^5"
"nextjs":14.2.13
"react":"^18"

Sound big issue, i see this issue is still on Blum or some famous miniapp. Need fix soon


Setup a github action (or similar) to apply the "needs triage" label to every new external github issue

This helps us tracking which issue still needs the first pass.
Checking online it seems there is no way to apply a label by default to every template, and it seems the way to go is to add a github action?
Ideally, the label would not be applied if one of the current maintainers is opening it. But that's not so important...

@reyammer I'd be interested in picking up this issue if you're accepting contributions

Assigned to you, thanks!

There are two ways to determine if an issue creator is a maintainer:

Use the GitHub API to check if the user is a collaborator on the repo.
Use a CODEOWNERS file to maintain a list of project maintainers. More info here.

Of course, we would be using GitHub actions in both cases.


Add components already compatible with Cardano-Node v9.0/9.1

Hi, can someone please review this PR?
@olgahryniuk @NeilBurgess42 @fstoqnov-iohk

The build fails after 3seconds, missing a parameter value.

@FerralBunny Same issue. It seems that the Vercel token is missing:
Error: Input required and not supplied: vercel-token
Could this be a permission-related issue? My pull requests have never been able to deploy to preview in this repository.

@FerralBunny Is there anything I can do to help resolve this?


Write Arrow footer

The resulting Arrow IPC file is invalid because it's missing the footer. Calling finish after writing all the batches fixes this.

Thank you! Can you also fix json2arrow?


added request parameters to all pages in pagination of request list

Issue Reference
This PR addresses the Issue : Fixes #331
Summarize
Please, describe what the PR does, the changes you have made.

Also, mention the key points if any to look into while code reviews

Tested this on the /requests page and it works well. Does that cover everything?

Test /find_people too.

There doesn't seem to be any data on /find_people online, nor in the db dump. Could you tell me how one can populate it?

It seems that there is no data in the server also.

Deploying, test in production


fix(api): don't log db conn failures on db create/update

SUMMARY
Avoid logging a DB connections failure since it's a user error
TEST PLAN
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

Codecov Report

Merging #11503 into master will decrease coverage by 3.98%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #11503      +/-   ##
==========================================
- Coverage   66.55%   62.57%   -3.99%
==========================================
  Files         869      451     -418
  Lines       41587    15506   -26081
  Branches     3797     3797
==========================================
- Hits        27680     9703   -17977
+ Misses      13805     5624    -8181
- Partials      102      179      +77

Flag
Coverage Δ

#cypress
?

#javascript
62.57% <ø> (ø)

#python
?

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

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


Improve documentation for how to run and debug tests locally

VSCode Local Development.
There should either be information on what tests failed once dotnet test is completed, as it currently just output something like below example:
Failed!  - Failed:     3, Passed:    60, Skipped:     0, Total:    63, Duration: 11 m 18 s - /Users/vasubhog/GitProjects/azure-functions-sql-extension/test/bin/Debug/net6/Microsoft.Azure.WebJobs.Extensions.Sql.Tests.dll (net6.0)
This is not informative about what tests failed and you may not be able to scroll up if the terminal does not allow it since we run many tests.
Possible Solution:
Have the tests that failed to be saved to a list so that at the end they be outputted in order to quickly understand which tests fail and then focus on.

The test failure information is in the logs already - although when looking at pipeline failures you should typically be using the tests tab for this since it also directly attaches the stdout for the test that failed as well. Is there something else you think we need here?

And if you really just want to run from the command line then you can just use dotnet test --logger:html and that will output an HTML file with all the test failure details
https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-test has all the details on that (and more options)

It has a test explorer as well which should provide a similar experience for seeing test failures and their results. Running dotnet test directly is not something I would expect most people to be doing when working on tests locally.

I only use VS Code for local development. Are you talking about this test explorer extension? https://marketplace.visualstudio.com/items?itemName=formulahendry.dotnet-test-explorer.
It would be great to include some of this information in the Integration Test ReadMe specifically running tests since that is not stated.

Something like that - I've never tried using that myself since VS is just a much better experience IMO. Feel free to add any documentation you think is necessary.

Updated test docs here so that there are multiple ways to debug.


feat: Finite maximality/minimality

This PR slightly tidies the proof of Set.Finite.exists_maximal_wrt, and adds a minimality version.
It also adds primed versions of both that alter the finiteness hypothesis to a weaker hypothesis where only the image is finite.

bors merge

I don't understand the issue that CI is having here. Do I need to do something?

Just a network error
bors merge


Doesn't work for some groups (Comment, Type, etc)

Thanks for the great work, this is very nice!
Most of the groups work and are highlighted correctly, however some of them (Comment, Type, Statement, others) are not. There's nothing overriding them, so it must be something from neovim.
Sample:
local theme = lush(function()
	return {
		Comment {fg = lush.hsl(20, 20, 20)},
	}
end)

All groups are highlighted just fine when calling :Lushify.
Can anyone replicate?
NVIM v0.5.0-897-gd80f262f8

it works fine, I didn't RTFM on setting g:colors_name


Variable Operator Precedence Parsing Issue

General Summary
The design of Enso's syntax uses whitespace to control operator precedence (e.g. 2 * 1+1 is equal to 2 * (1 + 1), and hence evaluates to 4). However, there are a few cases where this doesn't seem to work, instead producing an AST that doesn't make sense. One of these occurs in the interaction between = and ->.
This should also fix the fact that a, b should parse the same as a , b, without the precedence rule applying.
Steps to Reproduce

Parse the following code into an AST.

x -> y=x -> x + y

Expected Result
It should be parsed as if it were implicitly the following:
x -> (y = x) -> x + y

Actual Result
It is parsed as if it is implicitly:
x -> (y = x -> x + y)

Enso Version
Enso Compiler and Runtime
Version:    0.0.1
Built with: scala-2.13.2 for GraalVM 20.0.0
Built from: master @ 50e307e6ee34c5f536343189d8d55eff30fde026
Running on: Java HotSpot(TM) 64-Bit Server VM GraalVM EE 20.0.0, JDK 1.8.0_241-b07
            Mac OS X 10.15.3 (x86_64)

This will be accounted for in designing the new operator resolution and macro resolution phases.


build error on windows

Trying to build on windows with yarn build_windows.
Any idea what might be causing this error and/or how to fix it?
ERROR in src/rapidoc.js 830:85
Module parse failed: Unexpected token (830:85)
File was processed with these loaders:
 * node_modules/babel-loader/lib/index.js
 * node_modules/eslint-loader/dist/cjs.js
You may need an additional loader to handle the result of these loaders.
|     }
|
>     if (this.showInfo === 'true' && !window.location.hash && (this.resolvedSpec.info?.description || this.resolvedSpec.info?.title)) {
|       this.selectedContentId = 'overview';
|     } else if (window.location.hash) {
 @ src/index.js 2:0-32 5:2-9

here was my yarn install output, if it helps:
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
info<EMAIL_ADDRESS>The platform "win32" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "win32" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "win32" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[4/5] Linking dependencies...
warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency "eslint-plugin-react-hooks@^4 || ^3 || ^2.3.0 || ^1.7.0".
[5/5] Building fresh packages...
Done in 35.15s.```

i am unable to recreate this issue for windows build
the environment i test is
OS Name:                   Microsoft Windows 10 Enterprise
OS Version:                10.0.19042 N/A Build 19042

node -v
//  v15.3.0

yarn -v
// 1.22.5

I use powershell to build on windows

I tracked down the issue. A few things need to be installed manually/globally for it to work.
Here's steps from fresh:

Download node.js from https://nodejs.org/en/ (last tested with 14.15.1)
Install that (you can skip the extra node-gyp installation)
Run the following global installs:
a. npm i -g yarn
b. npm i -g webpack
c. npm i -g webpack-cli
d. npm i -g eslint-plugin-react-hooks
e. npm i -g eslint
f. npm i -g eslint-plugin-react
g. npm i -g eslint-plugin-jsx-a11y
(in steps c/d/f/g you can ignore the warning that you need the peer dependency -- you are installing it)
Download RapiDoc
In that folder, do yarn install
(you can ignore the fsevents infos -- you don't need them)
(you can also ignore the three warnings for eslint-config-airbnb peer dependencies -- you installed them above)
In that folder, do yarn build_windows

@mrin9 perhaps it is worth adding these to a windows build instructions somewhere?


update protos to latest from google/protobuf repo

Includes extension range options in descriptor.proto, added in protoc 3.4.

Can anyone recommend a good person to at-tag for a change like this? I know @cybrcodr and @dsnet have reviewed my most recent PRs.
This one is super simple. I just pulled latest from google/protobuf and then ran make regenerate and cd ptypes && ./regen.sh.

@cybrcodr, done

Good catch. Fixed to precisely match v3.4.1.


Do not show live view if BlElement is already added to another element

The live view attached to a BlElement does not work if the element is opened already in a space.

If there is no solution to make it work, would be bette to remove if in this case.

I was more thinking of a button that snatches the element from its scene and brings it in the inspector. What do you think?

I remember keeping the Live view in this use case in order to understand why the Live tab is not present. There should be a message informing about it, not a debug button.
It used to be confusing not to see the Live tab, not knowing why it happens.

A common use case is to navigate the children structure of an element already opened in a space. In that case the user will always need to do an action: click the button or explicitly switch to the Preview tab to see the element.
One more simple solution could be to have the message + the button to brink the element here on a line + the actual preview below. That way no action is needed to see the element.
A second solution is to have the live view as above and to select the Preview tab by default in case an element is already displayed in a space. The user can then switch to the Live view and bring the element there if she wishes to interact with it.

Maybe we can the Live tab and the Preview tab can indicate that it is attached somewhere else.
On other hand, the "children structure" scenario, I think that if you click on a Preview tab once, then it opens the Preview tab in all other children (if they have it). We can maybe just change Live tab priority number to make Preview first when the Live tab cannot really display a Bloc element.

I think the change I did works fine in the  "children" scenario. I am not sure we need "the button to brink the element here".

The button to bring the element inside the inspector could be interested for debugging situations. For example, when the element has certain actions attached, like a button element, of something with hover animations. Without having the live element in the inspector, we need to find the element in the UI and do the action there. Instead we could brink the element in the inspector, interact with it, and then maybe have another action to send it back to the user interface.
Of course depending on the user interface, it might not always work, but would be interesting to experiment with this.

On other hand, the "children structure" scenario, I think that if you click on a Preview tab once, then it opens the Preview tab in all other children (if they have it). We can maybe just change Live tab priority number to make Preview first when the Live tab cannot really display a Bloc element.

Yes this works ok. Might be interesting later to introduce some notion of default presentation in the inspector, instead of always selecting the first one.

We now have the preview form embedded in the Live view when the element has a parent.


Return to binding FastAPI from all addresses

Describe what the PR does:
In #359, I attempted to restrict binding to the FastAPI port, but that turns out to restrict every connection except from localhost – not what we want. This PR fixes the bug.
Does this fix a specific issue?
N/A
Checklist:

[ ] Confirm that one or more new tests are written for the new functionality.
[x] Run tests and ensure everything passes (with 100% test coverage).
[ ] Update README.md with any new documentation.
[ ] Add yourself to AUTHORS.md.

that's why 2022.10.2 wasn't working for me. :)


Semantic elements in getting started

In https://oneuiweb.dev/#/getting-started/quickstart
the markup is:

I think probably think
 should maybe be a
 or a  and
 should be a
 or an

Agree, planning to follow this: https://www.w3.org/TR/wai-aria-practices/examples/landmarks/HTML5.html
so it would look something like this:

       ...

        This is the header
        This is the nav
        And here is main

PR are welcome 🤗


Axlsx::name_to_indices fix

In Axlsx::name_to_indices accept row numbers containing, but not starting with, 0.

@joekain AWESOME!
Serious apologies for such an obvious bug! I'll knock out some specs and merge this today.
Thank you so much for taking the time to find and fix this bug.

No problem, thanks for merging this.


Hybrid query and nested type fields

Description
Nested fields have few problems that we're addressing in this PR:

query is wrapped into the Bool query inside the core code (ref), that happening behind the scenes and depends only on presents of the field in the index mapping. This case should work.

wrapping up hybrid search query into another query in general. That is not how hybrid query were designed, it must be a top level query. We need to track and block such queries.

We're mainly addressing case 1, and trying our best for case 2.
Below is snippet of example from original github issue to illustrate case 1. Without this PR search query returns wrong scores:
index mapping
PUT /index-test
{
    "settings": {
        "index.knn": true,
        "number_of_shards": 2,
        "default_pipeline": "pipeline-test"
    },
    "mappings": {
        "properties": {
            "id": {
                "type": "text"
            },
            "passage_embedding": {
                "type": "knn_vector",
                "dimension": 768,
                "method": {
                    "name": "hnsw",
                    "space_type": "cosinesimil",
                    "engine": "lucene",
                    "parameters": {
                        "ef_construction": 512,
                        "m": 8
                    }
                }
            },
            "name": {
                "type": "text"
            },
            "passage_text": {
                "type": "text"
            },
            "test": {
                "type": "text"
            },
            "user": {
                "type": "nested"
            }
        }
    }
}

add doc to index
POST /index-test/_doc/1
{
    "name": "A West Virginia university women 's basketball team , officials , and a small gathering of fans are in a West Virginia arena .",
    "id": "4319130149.jpg"
}

search request
GET /index-test/_search?search_pipeline=nlp-search-pipeline

{
    "_source": {
        "exclude": [
            "passage_embedding"
        ]
    },
    "query": {
        "hybrid": {
            "queries": [
                {
                    "match": {
                        "name": {
                            "query": "wild west"
                        }
                    }
                },
                {
                    "neural": {
                        "passage_embedding": {
                            "query_text": "wild west",
                            "model_id": "{{model_id}}",
                            "k": 20
                        }
                    }
                }
            ]
        }
    }
}

Issues Resolved
https://github.com/opensearch-project/neural-search/issues/466
Check List

[x] New functionality includes testing.

[x] All tests pass

[x] Commits are signed as per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@martin-gaievski Please add the index mapping and query that you tested via curl or postman in the issue description so that we understand how this was tested.

@martin-gaievski Please add the index mapping and query that you tested via curl or postman in the issue description so that we understand how this was tested.

updated

@martin-gaievski Please add the index mapping and query that you tested via curl or postman in the issue description so that we understand how this was tested.

added requested info to the PR description

@martin-gaievski Please add the index mapping and query that you tested via curl or postman in the issue description so that we understand how this was tested.

added requested info to the PR description

I cannot see the nested field or query in the description

@martin-gaievski Please add the index mapping and query that you tested via curl or postman in the issue description so that we understand how this was tested.

added requested info to the PR description

I cannot see the nested field or query in the description

please check mapping query:
"user": {
                "type": "nested"
            }

just having such field is enough, that triggers the logic of wrapping query into Bool in core code https://github.com/opensearch-project/OpenSearch/blob/main/server/src/main/java/org/opensearch/search/DefaultSearchContext.java#L367-L370

nested

can we index in the user field in your example and the paste the response.

nested

can we index in the user field in your example and the paste the response.

yes, these are additional requests/responses
add doc to index
{
    "name": "A rodeo cowboy , wearing a cowboy hat , is being thrown off of a wild white horse .",
    "id": "2691147709.jpg",
    "user":
        {
            "name": "bill",
            "lastname": "mardock"
        }

}

and additional search requests where nested query is part of the hybrid query
{
    "_source": {
        "exclude": [
            "passage_embedding"
        ]
    },
    "query": {
        "hybrid": {
            "queries": [
                {
                    "nested": {
                        "path": "user",
                        "query": {
                            "match": {
                                "user.name": "john"
                            }
                        }
                    }
                },
                {
                    "neural": {
                        "passage_embedding": {
                            "query_text": "wild west",
                            "model_id": "{{model_id}}",
                            "k": 20
                        }
                    }
                }
            ]
        }
    }
}

sample response from system without the fix:
{
    "took": 129,
    "timed_out": false,
    "_shards": {
        "total": 2,
        "successful": 2,
        "skipped": 0,
        "failed": 0
    },
    "hits": {
        "total": {
            "value": 7,
            "relation": "eq"
        },
        "max_score": 1.475126,
        "hits": [
            {
                "_index": "index-test",
                "_id": "7",
                "_score": 1.475126,
                "_source": {
                    "name": "Open letter immediately",
                    "id": "345345.jpg",
                    "user": {
                        "name": "john",
                        "lastname": "waine"
                    }
                }
            },
            {
                "_index": "index-test",
                "_id": "4",
                "_score": 0.8722888,
                "_source": {
                    "name": "A man who is riding a wild horse in the rodeo is very near to falling off .",
                    "id": "4427058951.jpg"
                }
            },
            {
                "_index": "index-test",
                "_id": "2",
                "_score": 0.871683,
                "_source": {
                    "name": "A wild animal races across an uncut field with a minimal amount of trees .",
                    "id": "1775029934.jpg"
                }
            },
            {
                "_index": "index-test",
                "_id": "5",
                "_score": 0.866345,
                "_source": {
                    "name": "A rodeo cowboy , wearing a cowboy hat , is being thrown off of a wild white horse .",
                    "id": "2691147709.jpg"
                }
            },
            {
                "_index": "index-test",
                "_id": "6",
                "_score": 0.866345,
                "_source": {
                    "name": "A rodeo cowboy , wearing a cowboy hat , is being thrown off of a wild white horse .",
                    "id": "2691147709.jpg",
                    "user": {
                        "name": "bill",
                        "lastname": "mardock"
                    }
                }
            },
            {
                "_index": "index-test",
                "_id": "1",
                "_score": 0.84706104,
                "_source": {
                    "name": "A West Virginia university women 's basketball team , officials , and a small gathering of fans are in a West Virginia arena .",
                    "id": "4319130149.jpg"
                }
            },
            {
                "_index": "index-test",
                "_id": "3",
                "_score": 0.82945794,
                "_source": {
                    "name": "People line the stands which advertise Freemont 's orthopedics , a cowboy rides a light brown bucking bronco .",
                    "id": "2664027527.jpg"
                }
            }
        ]
    }
}

here is sample response with the fix:
{
    "took": 604,
    "timed_out": false,
    "_shards": {
        "total": 2,
        "successful": 2,
        "skipped": 0,
        "failed": 0
    },
    "hits": {
        "total": {
            "value": 7,
            "relation": "eq"
        },
        "max_score": 0.7003,
        "hits": [
            {
                "_index": "index-test",
                "_id": "7",
                "_score": 0.7003,
                "_source": {
                    "name": "Open letter immediately",
                    "id": "345345.jpg",
                    "user": {
                        "name": "john",
                        "lastname": "waine"
                    }
                }
            },
            {
                "_index": "index-test",
                "_id": "4",
                "_score": 0.3,
                "_source": {
                    "name": "A man who is riding a wild horse in the rodeo is very near to falling off .",
                    "id": "4427058951.jpg"
                }
            },
            {
                "_index": "index-test",
                "_id": "2",
                "_score": 0.29798752,
                "_source": {
                    "name": "A wild animal races across an uncut field with a minimal amount of trees .",
                    "id": "1775029934.jpg"
                }
            },
            {
                "_index": "index-test",
                "_id": "5",
                "_score": 0.28025523,
                "_source": {
                    "name": "A rodeo cowboy , wearing a cowboy hat , is being thrown off of a wild white horse .",
                    "id": "2691147709.jpg"
                }
            },
            {
                "_index": "index-test",
                "_id": "6",
                "_score": 0.28025523,
                "_source": {
                    "name": "A rodeo cowboy , wearing a cowboy hat , is being thrown off of a wild white horse .",
                    "id": "2691147709.jpg",
                    "user": {
                        "name": "bill",
                        "lastname": "mardock"
                    }
                }
            },
            {
                "_index": "index-test",
                "_id": "1",
                "_score": 0.21619603,
                "_source": {
                    "name": "A West Virginia university women 's basketball team , officials , and a small gathering of fans are in a West Virginia arena .",
                    "id": "4319130149.jpg"
                }
            },
            {
                "_index": "index-test",
                "_id": "3",
                "_score": 0.15772042,
                "_source": {
                    "name": "People line the stands which advertise Freemont 's orthopedics , a cowboy rides a light brown bucking bronco .",
                    "id": "2664027527.jpg"
                }
            }
        ]
    }
}

@martin-gaievski fix the title of the PR it doesn't provide info around what this PR is about.
Other than that code look good to me

@martin-gaievski fix the title of the PR it doesn't provide info around what this PR is about.
Other than that code look good to me

fixed the title @navneet1v


Does this support react-native?

Not yet? https://github.com/gaearon/redux-devtools/blob/a30043f54ef0d434174d80e36c963d80ce7d1b3d/src/react/native/index.js

Ok, I see.

@jlumpe Any chance I could get you to port the internal prototype you did to this stable code version? Shouldn't require many changes I think..

Yeah I'll try and take a look asap :)

@gaearon I have used the redux in a react-native app---noder, But I have some problems:

Is there can be two connectors in a redux app?

I put the Navigator in the connector, is this a  good way?

Is there any react-native Example code for use redux, I mean I know how to use, but I don't know this is the best way.

Look into my noder , component nest component, and the state is passed through many component, I think this will result in some Performance issues especially in react-native. Can you give me  some advice?

@soliury
This is a repository for Redux DevTools, not for Redux. Can you please ask these questions in the main Redux repo?
https://github.com/gaearon/redux

ok, I see.

Any updates on this one? @johanneslumpe anything you're stuck with that may need help?

Yes, this would help out tremendously!
:+1:

Anybody working on this? If not, we might take a look into it as we are going to release new este/native with Redux, cc: @steida

If you need any help let me know!

Good, we kinda need it for WebExpo conference this weekend, so will keep you updated :)

Yeah, we should help.

Note: changes in #132 will make it harder to make an RN version until React 0.14 comes out and React Native releases a compatible update. 0.14 is coming soon, so I'd expect #132 to land about the same time it's ready. In the meantime feel free to experiment with the current (2.x) version which should be easier to get running with RN.

Learning RN and Redux looks amazing.  I'm eager to test this!

any news on this?

No news but feel free to work on this.
I personally don't have the time right now.

As a heads up to all on this thread.  I'm a long time dev, but new to React.  If someone thinks they can get me pointed in the right direction with minimum screenshare training, I'll put the time in to try to get this going.  :beers:

I think the most promising way to support this would be to try to make the Redux DevTools Chrome extension to play with React Native.
Unfortunately DevTools currently uses React Redux 4.x which is incompatible with React Native as it still has its own fork of React. I can't give much more advice than that. I'm sure you'll figure something out if you give it some time :-)

so we should accelerate react native's transition to using the regular react package instead of a fork? that's what's blocking this?

There's actually nothing to accelerate since that's ongoing issue and it's going to land super soon. (Afaik)

Implemented in remote-redux-devtools.

@zalmoxisus's solution works great. It would be ideal to merge his changes into the base redux-devtools though.

@corbt, actually I didn't make any changes in redux-devtools, I use the original redux-devtools/lib/instrument there.
The remote monitoring is meant to be used for React Native, hybrid, desktop and server side apps. For web apps it's easier and way faster to use the classic solution or Chrome extension (in v1.0 we'll have there remote monitoring, but as an option).

@zalmoxisus ok, I guess as long as any changes/enhancements to the instrumentation are available to the redux-remote-devtools as well it isn't a big deal if we have to use a separate package in RN vs webapps.

A quick update for those wondering/got here by Google:
The Chrome extension seems to be working with React Native now. Requires npm install --save-dev remote-redux-devtools and pressing the toolbar button and using "Open Remote DevTools".
It's not bug-free (it looses the connection when the app is reloaded) but it works for now. One annoying issue is that you need to reload the DevTools when the app reloads (it loses connection).

@scarlac, that issue should be fixed. Thanks for the report.
BTW, apart from the extension there's a great ecosystem around this. You can have Redux DevTools right on React Native Debugger. Or there's a React Native Debugger, which includes both Redux DevTools and React DevTools.

I use React Native Debugger with the following code and it works perfectly with react-native 0.40.0 (even on Windows), no need to install anything else:
    if (__DEV__) {
        // Development mode with Redux DevTools support enabled.
        const composeEnhancers = window.__REDUX_DEVTOOLS_EXTENSION_COMPOSE__ ? window.__REDUX_DEVTOOLS_EXTENSION_COMPOSE__({
                // Prevents Redux DevTools from re-dispatching all previous actions.
                shouldHotReload: false
            }) : compose;
        // Create the redux store.
        store = createStore(rootReducer, composeEnhancers(...enhancers));
    } else {
        // Production mode.
        store = createStore(rootReducer, compose(...enhancers));
    }

just a heads up, we've been using this forever in React Native.  If you're a fan of dev tools for redux, this is my fav.
https://github.com/infinitered/reactotron

ok great sounds like we can use redux-devtools with RN, this issue can be closed


Does the official website support multiple languages?

Is the official considering adding a language prefix to support multi-language switching on the basis of this project, rather than creating a new repository to support other languages?

Considering: Yes. Execution Plan: None
NextJS does support localization to a certain degree, but I didn't have time to think about a proper strategy / plan on how to introduce localization and how to organize translation work around it.


Fix incorrect mutation of argument list (#7802)

Pull request opened by the merge tool on behalf of #7802

Merged into branches iso7 in 9beada0106f2e1c22d64d61e1dd1106b5bc9bce7


segmentation fault when loading

Hi @alexhultman,
Sorry to post as an issue but I was hoping you have some idea where this is coming from.
I have compiled libuWS with flag UWS_THREADSAFE, also this doesn't happen on every start, which is the weirdest thing. I thought the order of loading modules could be the problem, but that should be consistent with every load.
Linux c007 3.13.0-123-generic #172-Ubuntu SMP Mon Jun 26 18:04:35 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
GDB shows this (full backtrace):

Core was generated by `nginx: worker process                                   '.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  check_match (sym=0x1e60) at dl-lookup.c:132
132	dl-lookup.c: No such file or directory.
(gdb) backtrace
#0  check_match (sym=0x1e60) at dl-lookup.c:132
#1  0x00007f03a96f89b6 in do_lookup_x (new_hash=new_hash@entry=1876617623, old_hash=old_hash@entry=0x7f039dffe5c0, result=result@entry=0x7f039dffe5d0,
scope=, i=, i@entry=0, flags=flags@entry=5, skip=skip@entry=0x0, undef_map=undef_map@entry=0x7f03a99121c8)
at dl-lookup.c:249
#2  0x00007f03a96f8b31 in _dl_lookup_symbol_x (undef_name=0x40a70e "_ZN2uS4NodeC2Eiiib", undef_map=0x7f03a99121c8, ref=ref@entry=0x7f039dffe688,
symbol_scope=0x7f03a9912520, version=0x0, type_class=type_class@entry=1, flags=5, skip_map=skip_map@entry=0x0) at dl-lookup.c:737
#3  0x00007f03a96fd6f7 in _dl_fixup (l=, reloc_arg=) at ../elf/dl-runtime.c:111
#4  0x00007f03a97046a5 in _dl_runtime_resolve () at ../sysdeps/x86_64/dl-trampoline.S:45
#5  0x0000000000503274 in uWS::Hub::Hub (this=0x7f039dffe840, extensionOptions=0, useDefaultLoop=false, maxPayload=16777216) at /usr/include/uWS/Hub.h:47
#6  0x0000000000501e24 in startWebsocketServer (port=4343, cycle=0xd0c430)
at /usr/local/src/di-collection-42b504564a65ffb282c0187ea91ba3b43afa99c8/src/ngx_http_di_collection_websockets.cpp:112
#7  0x00000000004f9346 in startWebsocketThread (param=0xd0c430)
at /usr/local/src/di-collection-42b504564a65ffb282c0187ea91ba3b43afa99c8/src/ngx_http_di_collection.c:225
#8  0x00007f03a7989184 in start_thread (arg=0x7f039dfff700) at pthread_create.c:312
#9  0x00007f03a76b5ffd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

The symbol "_ZN2uS4NodeC2Eiiib" is actually "uS::Node::Node(int, int, int, bool)"
Any idea will be appreciated!
Cheers

I changed the order of library linking from:
-pthread -lmysqlclient -lstdc++ -luWS -lz -lssl
To:
-lmysqlclient -luWS -lstdc++ -lz -lssl -pthread
All 47 servers are happy now. Do you think the order of loading was the issue?


id.sonyentertainmentnetwork.com

need it if you want to sign in to sony network
Match found in list.34.hosts.ubuntu101.co.za.domains:
id.sonyentertainmentnetwork.com

Note: I was unable to reach it from Germany.
Note: I will keep this on hold as it needs much more time to check.


ninja generator: support for CLI-specified tools

Before:
xmake f --cxx=g++-8 && xmake project -k ninja && ninja

create ok!
ninja: error: build.ninja:68: unknown build rule 'cxx'
build build/.objs/hello/linux/x86_64/release/src/main.cpp.o: cxx src/mai...
                                                             ^ near here

cxx rule is missing when --cxx=... is used. Same with ld and --ld=..., etc

Thanks!


[RFC] Scalability improvement for large amount of indexes

This is a request for comment to improve the startup time of most CLI commands.
Background
Currently restic interleaves tree information with their data blobs in packs. File operations do a treewalk to get to the next level of directories. Access to those blobs (any blobs for that matter) is sped up by using an index which maps blob hashes to pack file/offsets. Each backup creates a new indexes which are kept around until either one of  rebuild_indexes or prune cli commands is used.
Issue
At the end of each backup, a new index is created which contains the set of all previous indexes plus the new blobs written for this backup. This new index has a field, telling which other indexes it supersedes. Mainly this is done so that if 2 backups run at the roughly same time, each can write it's own index without interfering with the other backup. As a consequence one ends up with a large amount of superseded indexes, which, during startup of a cli cmd, ALL need to be read and determined for applicability.
Idea
Somewhere after reading of the available indexes, we remove indexes who are marked superseded. This removal should be non-fatal as 2 backups started at the same time, after reading all the indexes, might start removing the same indexes. Also, when reading all indexes and then failing to open them (aka, a race condition with another ReadIndexes() instance who deleted it), should be ignored, as long as in the end ReadIndexes() finds at least one non superseded index to work with.
This would not need an update of the locking strategy, a backup already has a non exclusive lock and since we are sure that the superseded indexes do not play a role in the resulting index , we do not need to upgrade our backup lock, even though it is a mutating operation.
Rationale
These superseded indexes are no longer needed as their mapping are by definition already contained any one the indexes marked as superseding them. (Note I'm only arguing to remove indexes where their superseding index is already committed to disk).
Some senseless ascii art.
A -> B(A) -> D(B,C) -> F(D,C)         -> H(F,G)
  -> C(A) ->       E(B,C)* -> G(D,E)  -|
Note that backup E took a long time, overlapping with the start of backup F. When E finishes, F has not finished so G does not see F's index.

You got a tiny detail wrong: At the end of a backup, restic writes a new index containing all new blobs added for that backup run, with an empty supersedes field. So we can neither just remove the previous indexes, nor the new index, the intersection of the blobs/pack files in the indexes is empty. In addition, no destructive modification of the repository should be done without an exclusive lock in place, at least that's what restic does at the moment. The backup operation doesn't need an exclusive lock because it just adds new data, never deletes or modifies old data.
The supersedes field is only set when a new index is built by rebuild-index or prune.
Thoughts?

FYI: In https://github.com/restic/restic/pull/842 I'm working on refactoring the Repository object. I've added some kind of Session data structure which tracks new data added, and I'm thinking about saving tree objects in separate pack files (so e.g. caching becomes easier).

Ah. right. I see now.
Ok, then I do not get it. When I run rebuild-index or prune, rebuildIndex() builds a new, combined index and removes ALL indexes mentioned in the supersedes field. Based on what you said, there is no need to persist that field at all, right? It will by definition point to removed indexes. (And since both  rebuild-index or prune are running with an exclusive lock, I don't expect race conditions with other backups which want to store new indexes.)
However, I'm not sure that invalidates my idea, right? The LoadIndex() used in cmd_backup() and others can be made a little smarter and build a "supersedes" on the fly (as it knows which indexes it loads) which idx.Save() can later on persist.

Re 842, Ah, you stole my thunder, I was about to write a RFC for putting the treedata into the snapshot object as they have the same lifecycle and having a single (albeit slightly large json file) is way better than having to seek through the repository a million times :)

Ok, then I do not get it. When I run rebuild-index or prune, rebuildIndex() builds a new, combined index and removes ALL indexes mentioned in the supersedes field.

Correct.

Based on what you said, there is no need to persist that field at all, right? It will by definition point to removed indexes. (And since both rebuild-index or prune are running with an exclusive lock, I don't expect race conditions with other backups which want to store new indexes.)

Also correct. My idea was that restic keeps a list of old index IDs around so that it can detect when an old index is present in the repo. Otherwise attackers with access to the backend could keep index files around, wait for content being removed and afterwards and move the index files back to the backend. The next time restic runs a backup it will think that old (=removed) content is still present in the repo because the index file says so. I'm not sure how relevant this is any more.

Re #842, Ah, you stole my thunder, I was about to write a RFC for putting the treedata into the snapshot object as they have the same lifecycle and having a single (albeit slightly large json file) is way better than having to seek through the repository a million times :)

That's a neat idea, but I don't think that this scales. Decoding large JSON objects in Go is very memory-intensive, that'll also become a problem for the index files soon.

PS. #842 is becoming very hard to read, it looks like a refactor to me, not seeing that Session object just now.

I know, I'm sorry. I still haven't figured out the right size for a PR yet. The object is not yet called Session but ContentManager: https://github.com/restic/restic/pull/842/commits/a68613fabfe76fe3c03dc514c13ea9b16f5b03f1

That's a neat idea, but I don't think that this scales. Decoding large JSON objects in Go is very memory-intensive, that'll also become a problem for the index files soon.

/me grins and points to #838, (I actually implemented this and it seems that even gobing the same structure results in a big speed improvement. None the less, let me address your concern more realistically.)
I don't think a single - one time - json decode even comes close to the memory fragmentation resulting from loading say 30k blobs and 30k smaller json decodes just to list or find a file in a snapshot. Not to mention speed. Loading a single full filesystem tree decodes in ~5s on my machine, a restic find takes about 3m.
Re #842
So, now I'm curious as to how the content manager helps here. I see it maintains a set of pack files, which it uploads when full or finishes. But it still looks there will be an index file per backup. Which means if the user does not run restic rebuild-index often enough, the cli will bog down again.
I probably missed something in the code though which makes it all better. :(

Ah, I thought I already added the code which uses separate pack files for tree objects, but it seems I haven't done that yet. I apologize :)

There are two problems about many index files:

all files need to be loaded which may take some time for high-latency backends
index operations even slow  down once the index is loaded, as they are ATM stored in memory like saved in the repository.

The first point is by design and yes, this can be only curated by regularly running rebuild-index or prune (I would suggest prune after #2718 is merged).
The second point is addressed by #2818.


Overlapping interface/text on prev page

I suggest to move the BFR label to the bottom left of the graph


[BZ: 2076468]Added extra rook configs for provider clusters

For a provider storage cluster extra rook ceph configs are required to solve a performance problem.
[global]
osd_pool_default_pg_autoscale_mode = off
osd_pool_default_pg_num = 128
osd_pool_default_pgp_num = 128

Added Unit tests

Signed-off-by: Kaustav Majumder<EMAIL_ADDRESS>

The correct key for the autoscale mode was osd_pool_default_pg_autoscale_mode. changed it in the new commit

/lgtm

/cherry-pick release-4.10


new version of the Ocellus/Zenodeo

Hello everyone,
I am very happy to have pushed a new version of the Ocellus/Zenodeo apps. They are both live at
https://ocellus.info/
https://test.zenodeo.org/
I am in the process of writing some explanatory release notes on their respective Github repos, but here is a quick summary:

Zenodeo supports a slew of extended querying capabilities. The full details are documented on the Zenodeo website under each resource that can be fetched from the database. For example,

fields with dates (publicationDate, checkinTime) can be queried like so

publicationDate=since(2010-12-21)
publicationDate=until(2000-01-01)
checkinTime=between(2012-01-17 and 2013-12-12)
checkinTime=eq(2013-12-03)

geolocation can be queried like so

geolocation=within({radius:100, units: ‘kilometers’, lat: -43.05, lng: -121.223})
geolocation=containedIn({lowerLeft:{lat: 5, lng: 7}, upperRight:{lat: 22, lng: 13}})

For the most part, one would construct these queries programmatically instead of by hand. Already, every field extracted from the XMLs is queryable, but I hope to expand this extended query capability much further. Your feedback would be very welcome.

As an image explorer, Ocellus is made possible by Zenodeo, and the new version leverages the new querying capabilities. You can, of course, search for images as usual, by just typing some text and letting Ocellus do a full-text search on both images on Zenodo (that is, images that may have nothing to do with treatments) as well as images connected to treatments. Ocellus combines the two results, weeds out the duplicates and presents the images in a unified view.

But, you can also use the extended queries on Ocellus (currently only possible against treatments, but hopefully, eventually expanded to include all of Zenodo images).
You will notice the same, minimalistic Ocellus interface but with two new features — a switch that selects the source of images (this switch automatically selects treatments as a source if it detects extended queries), and a link to example searches that reveals examples of extended queries. Clicking on an example fills the form correctly. You just have to press [go] to retrieve the images.
Whatever source you choose, the images connected to treatments are marked with a [T] on the upper right corner which reveals the treatmentId when you click on it. These images also have a link to the respective record on TreatmentBank.
Ocellus has been rewritten using the new ES6 module syntax, and as a result, the code is much cleaner, smaller, and hopefully more bug-free. (I want the only bugs to be the ones you are viewing on the screen.)
Speed and clarity are the prime-objective in making Ocellus, and I happy to say, it excels at those. I tested Ocellus against pagespeed.web.dev and it comes up at 100/100 on desktop and 97/100 on mobile. The entire application is around 350 KB and works great on phones.
Please use, test, and report any issues you may experience on the issue-trackers of the respective applications.
A lot more to come,
Puneet

hello everyone,
I have now added a cache-busting mechanism to Ocellus so it is no longer necessary (or, I might say, it should not be necessary) to refresh/empty your browser cache to get the latest version of the ocellus javascript and css. Every time I make any change, a new version with a unique name is generated so the browser will always cache only the latest version.
@millerjeremy @myrmoteras


wprecon: 1.6.3a -> 2.4.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/blackbinn/wprecon/releases.

WARNING: Package has meta.broken=true; Please manually test this package update and remove the broken attribute.

meta.description for wprecon is: "WordPress vulnerability recognition tool"
meta.homepage for wprecon is: "https://github.com/blackbinn/wprecon"
meta.changelog for wprecon is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/qqkwcb8q4clr9kjcbg5w5xhdyz6jmipj-wprecon-2.4.4/bin/cli had a zero exit code or showed the expected version
0 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 2.4.4 with grep in /nix/store/qqkwcb8q4clr9kjcbg5w5xhdyz6jmipj-wprecon-2.4.4
found 2.4.4 in filename of file in /nix/store/qqkwcb8q4clr9kjcbg5w5xhdyz6jmipj-wprecon-2.4.4

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
wprecon

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qqkwcb8q4clr9kjcbg5w5xhdyz6jmipj-wprecon-2.4.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A wprecon https://github.com/r-ryantm/nixpkgs/archive/d029a4cc3c6c63e39a9e4a308dfdf8ec95c61f9b.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qqkwcb8q4clr9kjcbg5w5xhdyz6jmipj-wprecon-2.4.4
ls -la /nix/store/qqkwcb8q4clr9kjcbg5w5xhdyz6jmipj-wprecon-2.4.4/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package marked as broken and skipped:

wprecon

Maintainer pings
cc @fabaff @kalbasit for testing.

Upstream has 2.4.5 available


make use of runInNewContext: false

This PR contains changes necessary to make use of the new runInNewContext: false option introduced in 2.3.
The changes are implemented and tested on top of https://github.com/nuxt/nuxt.js/pull/633 and should be merged after it. (This is probably why CI is broken, this is mainly submitted to show the diffs, I can re-submit after #633 is merged as well)
This introduces breaking changes. Most notably the user will have to avoid global singletons in their code as explained here. Also, in store.js we have to add a few warnings to require user store and modules to use functions for state.
It's possible to maintain backwards compat by making this whole thing behind a config option, but I think this really should be the new default.
Perf comparison for an out-of-the-box Nuxt app using vue init nuxt/starter with ab -n 1000:
Before
Concurrency Level:      1
Time taken for tests:   10.904 seconds
Complete requests:      1000
Failed requests:        0
Total transferred:      4531000 bytes
HTML transferred:       4371000 bytes
Requests per second:    91.71 [#/sec] (mean)
Time per request:       10.904 [ms] (mean)
Time per request:       10.904 [ms] (mean, across all concurrent requests)
Transfer rate:          405.81 [Kbytes/sec] received

Connection Times (ms)
              min  mean[+/-sd] median   max
Connect:        0    0   0.1      0       1
Processing:     6   11   6.5      9      92
Waiting:        6   11   6.4      9      91
Total:          6   11   6.5      9      92

Percentage of the requests served within a certain time (ms)
  50%      9
  66%     10
  75%     10
  80%     11
  90%     13
  95%     23
  98%     32
  99%     35
 100%     92 (longest request)

After
Concurrency Level:      1
Time taken for tests:   2.126 seconds
Complete requests:      1000
Failed requests:        0
Total transferred:      4531000 bytes
HTML transferred:       4371000 bytes
Requests per second:    470.41 [#/sec] (mean)
Time per request:       2.126 [ms] (mean)
Time per request:       2.126 [ms] (mean, across all concurrent requests)
Transfer rate:          2081.49 [Kbytes/sec] received

Connection Times (ms)
              min  mean[+/-sd] median   max
Connect:        0    0   0.1      0       1
Processing:     1    2   1.8      1      17
Waiting:        1    2   1.8      1      17
Total:          1    2   1.8      1      17

Percentage of the requests served within a certain time (ms)
  50%      1
  66%      2
  75%      2
  80%      2
  90%      3
  95%      5
  98%      9
  99%     13
 100%     17 (longest request)

I've successfully cherry-picked commits into #633 and CI is now passing tests :)  @yyx990803

Cool! Closing this one then.


Fixed read() and write_read() specs

read() and write_read() actually return data() not {data()}.

Wow - that's been in there awhile. I've lost my write access to be able to merge pull requests, but hopefully someone else is watching who can do it.

Thanks fhunleth.  Not a significant change, but the PR does clean up my dialyzer output.


[Doc] Need to link to EI product download page in Configuring WSO2 EI Entitlement Mediator with Identity Server

Doc link : https://docs.wso2.com/display/IS540/Configuring+WSO2+EI+Entitlement+Mediator+with+Identity+Server
Suggested Labels
Improvement

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.


auto fix include-what-you-use output

the latest rexpy version already does this.
use mapping files, macros, style, .. to customise it for rex engine and rex standard
https://github.com/include-what-you-use/include-what-you-use/blob/master/docs/IWYUMappings.md

PR has been made
https://github.com/New-Creta/Rex/pull/130


Cursor position in test plan changes jmx file

Expected behavior
If you save a JMeter plan with no changes in the test plan then outputed jmx file is still same no matter where you had the cursor while saving the test plan.
Actual behavior
Outputed jmx file is different based on the cursor position while saving the test plan. It is hard to track changes of jmx file because of this.
Steps to reproduce the problem
Open the attached sample test plan then select Thread Group and save the plan (or you can just try to close JMeter application and you will be notified that there are some changes in the test plan) and compare the outputed file with the original one, you will see the differences. Different position of the cursor in the test plan produces different output.
sample.zip
JMeter Version
5.6.3
Java Version
No response
OS Version
No response

The diff is that enabled=true appears only for the currently selected element
--- sample2.jmx	2024-01-09 14:04:16
+++ sample3.jmx	2024-01-09 14:03:44
@@ -27,7 +27,7 @@
         </collectionProp>
       </Arguments>
       <hashTree/>
-      <ThreadGroup guiclass="ThreadGroupGui" testclass="ThreadGroup" testname="Thread Group">
+      <ThreadGroup guiclass="ThreadGroupGui" testclass="ThreadGroup" testname="Thread Group" enabled="true">
         <intProp name="ThreadGroup.num_threads">1</intProp>
         <intProp name="ThreadGroup.ramp_time">1</intProp>
         <boolProp name="ThreadGroup.same_user_on_next_iteration">true</boolProp>
@@ -38,7 +38,7 @@
         </elementProp>
       </ThreadGroup>
       <hashTree>
-        <HTTPSamplerProxy guiclass="HttpTestSampleGui" testclass="HTTPSamplerProxy" testname="HTTP Request">
+        <HTTPSamplerProxy guiclass="HttpTestSampleGui" testclass="HTTPSamplerProxy" testname="HTTP Request" enabled="true">
           <boolProp name="HTTPSampler.follow_redirects">true</boolProp>
           <stringProp name="HTTPSampler.method">GET</stringProp>
           <boolProp name="HTTPSampler.use_keepalive">true</boolProp>

I see the opposite. When you open "sample.jmx" and then immediately save the file you will see something what you can see on the screenshot (every single element has enabled=true, probably all elements have their default values saved, see what was saved for the test plan).

enabled=true disappears only for the elements that were selected, i.e. when you open a test plan, select some elements and save, then the elements you selected were saved without enabled=true the other were saved with enabled=true.
This is complication for the development because you see the changes you haven’t done upon the commit.
Every time the test plan is loaded then a default value is appended to all elements.


[Tag] Add disabled prop

The disabled state of the tag has not been included in the component revision and is still missing

Fig. - Tag component states
Tag documentation in 4.2.0 - Color specifications

@aweell
Since we are waiting for a decision regarding this component, let's keep this one on hold.


[UPDATE] Suggestion to improve instruction clarity in bonus-unit1

In Create the Huggy config file cell from bonus-unit1.ipynb, for first time users of notebooks and colab, it is not obvious how to create a file or how to "Go to /content/ml-agents/config/ppo".
I suggest adding "Click file icon on left sidebar of notebook."
@simoninithomas

Good Idea I'm updating the notebook 🤗

Merged thanks again 🤗


The meanning of the lastest float number in the scene00xx_0x.txt within the pred_instance file

Thanks for your amazing work!
Can you explain the meanning of the lastest float number in, for example, the scene0011_01.txt within the pred_instance file?
"predicted_masks/scene0011_01_000.txt 3 0.4161"

It is the confidencescore.
predicted_masks/scene0011_01_000.txt -> path to mask pred
3 -> Predicted label
0.4161 -> confidence score

thanks for your reply.There is a new question,Does softGroup have NMS before output instance_pred.


CLI

🚀 Feature Request
etna-ts should have CLI interface
Motivation
It will make integration of etna-ts in production easier
Proposal
etna should be able to run prediction from CLI.
Parameters may be stored in json/yml files.
Input and outputs are csv files.
Test cases
No response
Alternatives
https://github.com/fursovia/allenai-common
https://github.com/catalyst-team/hydra-slayer
https://github.com/facebookresearch/hydra
Additional context
No response
Checklist

[X] Added feature request
[X] Added motivation
[X] Added proposal

@martins0n can we close this issue?


Audit Hyrax <-> D5 use of dc terms vs. dc11 properties

Descriptive summary
We have noticed in documentation and Hyrax's basic_metadata code some differences between Hyrax and D5 in the properties/namespaces for Dublin Core (dc vs. dc11).
Note: to avoid confusion, since the syntax of the code is based on rdf.rb, the prefix dc: always refers to DC Terms, while dc11: obviously refers to the 1.1 Elements namespace.
A example of where Hyrax and D5 differ are Hyrax using dc:rights vs. D5 using dc11:rights. Should we find and reconcile the rest?
Rationale
Although we are obviously forking/extending the existing basic Hyrax metadata, if there is an opportunity for us to align with the Hydra/Hyrax community on shared properties/namespaces and still meet our local needs, it would be worth pursuing.

@remerjohnson Attached is the Excel file with the difference in red for the terms and predicates used in Hyrax basic metadata and D5. It seems like some mapping are not clear enough (see my comments in the Notes):
hyrax-d5_predicates.xlsx

@lsitu I put your sheet as a new sheet in the 4.2 data dictionary to discuss with DOMM.
@GregReser then took the alignment and updated the properties in the main sheets and template. The changed properties are highlighted in yellow in the Google Sheet.
Two outstanding issues:

Since Hyrax is reserving dc:created for system dates of object creation, we can either "collapse" our idea of resource date creation into just dc:date, OR simply use a different predicate, such as bf:originDate (link). @ucsdlib/domm Thoughts? I'm trying to get more info about how Hyrax will likely handle descriptive metadata for dates, but haven't found anything.
Related resouce. Hyrax is using rdfs:seeAlso, but only expecting a simple URL. Can this be mapped to our current plan for the schema:url property within our class? See #58

@remerjohnson For dc:created, I think we can still use predicate dc:created but just use another property name, such as created_date as currently used in horton. This could avoid the conflicting of the time valve that Hyrax used by default for system dates and the TimeSpan class that we are using.

@lsitu We could do that, but then it would raise the question of when would we ever use just dc11:date? Is there a way we can assert on the ontology level that all of our date types are sameAs dc11:date?

@remerjohnson Good question! Are you going to use dc11:date for all date types?

@lsitu So I asked Mike Giarlo about this dc:created situation, and he said that he believes date_created is descriptive metadata, and not reserved for Hyrax system uses.
He believes those system dates come from the core_metadata file.
So it seems we have no conflict. Our date:created seems to now map cleanly to Hyrax

That sounds good and we can use dc:created. Thanks @remerjohnson. However, I do see some unexpected result in the past when I use it and I noticed that property name date_created is referenced every where over hydra/hyrax. For example, https://github.com/projecthydra/hydra-works/blob/master/lib/hydra/works/characterization/schema/base_schema.rb#L7 .

@lsitu True, I've seen that before. I'm assuming that's the PCDM:File class?
I think this is heading into unsettled territory, and hoping the metadata folks in the community can maybe help out here. We could change our property name to avoid conflicts. At least in the example you have, it points to ebucore and not dc. But yes, still sub-optimal.

@remerjohnson Yes, I think it's used in the PCDM:File, and hyrax expected date_created to be a 'date string', which is conflicting with our TimeSpan as well. For example, https://github.com/projecthydra-labs/hyrax/blob/master/app/helpers/hyrax/citations_behaviors/publication_behavior.rb#L6-L11.

@lsitu I see. Our dates here will be strings, we just wanted the range to be our TimeSpan class, so it would start with a string in the prefLabel. Is it that the code just won't parse it?

@remerjohnson I think when referenced by object, it'll be a TimeSpan. When using the values in solr, then it depends on how we index those values. But both label and the hash/json value should be there.

@remerjohnson Good news is that Hyrax is trying to separate the basic metadata that could be used/referenced internally with the descriptive metadata from the object/collection models. I see the BasicMetadataIndexer class is extracted that can added to or removed from the object/collection model, which making it a good step toward it.
I think the conflicting issue with the property name like date_created for TimeSpan could be fully resolved once we upgrade to the latest Hyrax 2.0.alpha on github.

@lsitu Yes, that's good. It seems both devs and metadata people are moving along, so this a fluid situation.
I now see there is no references to just dc:date anywhere for Hyrax. Should we still support it for description at all?

Yes. we can support it in any way you want. I think we can ignore those basic descriptive metadata defined in Hyrax and build our own data model.

@remerjohnson We just talked about the ticket during our sprint wrap up meeting. Is there anything else you want me to do? Otherwise I think we can close the ticket.


Fixing JavaScript

I noticed variables are declared as var instead of using let or const someone should change all of them to their respected type. If no ones willing to do this I'm alright with working on this.

let has been around long enough and the overwhelming percentage of browsers that support it means that let could and probably should replace var. Only old versions of IE wouldn't support it effectively, and with 7 now EOL, those old versions of IE will soon also fade away. I do think that let needs to replace var to comply with proper JavaScript notation standards.

Yes, you might be right. In that case by all means make a start on modernising the JS.
I do think the codebase could do with a drastic overhaul anyway, and my intention once some of the outstanding issues are resolved is to majorly restructure the code with modern browsers in mind. But for the time being, these kinds of fixes are 100% worthwhile.

I’m very grateful to join the GITHUB.

You can write modern JavaScript syntax and have them transpile to multiple format ie. es5 and es6 and ship them separately for both old and newer browsers. You can utilise bundle tools such as webpack, rollup and transpile tool like babel.

That's not really an option for github pages hosting unfortunately, and without changing the domain it requires some more drastic codebase restructuring.
I do want to attempt some of those larger-scale changes in v2, but for now we can just update to the more widely-supported features like let and const.

Hi I'd like to help out with modernizing this repo. Has this been taken up by someone or do I just start?

Not that I know of; if you want to start moving to let and const, just make a fork and give it a go!

I was working on this today and found 3 variables repeated in all HTML files but never used anywhere.
var sc_project=11325211;
var sc_invisible=1;
var sc_security="fd9f0659";

What is the use of them?

I was working on this today and found 3 variables repeated in all HTML files but never used anywhere.
var sc_project=11325211;
var sc_invisible=1;
var sc_security="fd9f0659";

What is the use of them?

As far as I can see, there isn't any purpose to them. I think @Genora51 would need to confirm if they would be safe to remove and/or their purpose.

So, looking back over that code I'm pretty sure that stuff was some basic analytics @TristanBomb  put in way back at the start of the project - I would encourage a pull request to take out all of that code (google analytics, statcounter), otherwise I'll do it myself in a couple weeks when I have some time.


Update bash script to add grader extensions based on notebook type

Update the enable_extensions.sh script to install the grader extensions based on theGrader role.

Done.


add GPU support for pytorch torchbench benchmarking

Description

Add vm_api.gpu_api to mimic tpu_api. gpu_api supports resource creation and remote execution using fabric.
Fix the torchbench TPU run config to support nightly torch/torchaudio/torchvision build.
Add the torchbench GPU run for nightly test.

Currently the gpu_api doesn't contain resource release. A temporal solution is to set --max-run-duration of the resource in one hour when creating the vm.
Known issue:

xla PJRT will fail for GPU at this time (xla inductor works fine). This will be fixed after https://github.com/pytorch/xla/pull/5960 is checked into torch_xla.

Tests
airflow test link here.
Please wait for the test to complete.
Checklist
Before submitting this PR, please make sure (put X in square brackets):

[x] I have performed a self-review of my code.
[x] I have necessary comments in my code, particularly in hard-to-understand areas.
[x] I have run one-shot tests and provided workload links above if applicable.
[x] I have made or will make corresponding changes to the doc if needed.

The workers seem dead when I launch 10 runs in parallel. Is there a resource limitation?

Could you attach your latest GPU test link? Thanks!

Here is the link. Currently the run models failed to run all the model due to the benchmarking coding issue, which is not associated with the DAG setup.

Here is the run with TPU and GPU: https://08398f98ca104983a06a424b851a390d-dot-us-central1.composer.googleusercontent.com/dags/pytorchxla-torchbench/grid?dag_run_id=manual__2024-01-19T23%3A29%3A55.062940%2B00%3A00&tab=graph

Check in this for now since we are working on the following pending features. Please let me know if there is future improvement feedbacks. Thanks


Extract logic to new Connection API

What is wrong?
https://github.com/ethereum/trinity/blob/ce1f5ae3bfc28a45dc872c8e6f5fa068ee75094d/trinity/protocol/common/handlers.py#L48-L67
This logic from the BaseExchangeHandler probably belongs in the Connection or Multiplexer object.
How can it be fixed
I'm inclined to put it on the Connection as get_protocol_for_command_type
This API should be able to be reasonably easily tested against the various code paths.

@pipermerriam Can I work on this?

@Patil2099 :+1: all yours


fix: parse the process name to get the process type instead of using port count

ref: https://github.com/longhorn/longhorn/issues/7393
Get the process type by parsing the name instead of using port count.

Need to wait until IM PR merged, so I can update the vendor here.

Wait for https://github.com/longhorn/go-common-libs/pull/25

@ChanYiLin any updates?

@innobead
wait for https://github.com/longhorn/longhorn-instance-manager/pull/407

This pull request is now in conflict. Could you fix it @ChanYiLin? 🙏

fixed.

@ChanYiLin any updates?

Waiting for https://github.com/longhorn/longhorn-instance-manager/pull/407
So we can update the vendor in manager


Cannot find module './types' or its corresponding type declarations.

Hey,
I installed and tried to use this package on Angular.
I get this error on build.
Please advice,
Thanks

Error: node_modules/@nfteyez/sol-rayz/dist/config/metaplex.d.ts:1:33 - error TS2307: Cannot find module '../types' or its corresponding type declarations.

1 import { StringPublicKey } from "../types";
                                  ~~~~~~~~~~

Error: node_modules/@nfteyez/sol-rayz/dist/getParsedAccountByMint.d.ts:2:33 - error TS2307: Cannot find module './types' or its corresponding type declarations.

2 import { StringPublicKey } from "./types";
                                  ~~~~~~~~~

Error: node_modules/@nfteyez/sol-rayz/dist/getParsedNftAccountsByOwner.d.ts:2:33 - error TS2307: Cannot find module './types' or its corresponding type declarations.

2 import { StringPublicKey } from "./types";
                                  ~~~~~~~~~

Error: node_modules/@nfteyez/sol-rayz/dist/resolveToWalletAddress.d.ts:2:33 - error TS2307: Cannot find module './types' or its corresponding type declarations.

2 import { StringPublicKey } from "./types";
                                  ~~~~~~~~~

✖ Failed to compile.

hey @naamapps !
I think it is not related to Angular. it should be agnostic to the js framework.
it might be related to your js bundler, like Webpack or whatever you use. and how things are transpiled/compiled in your project.
I've created Angular codesandbox. It seems to work well. check it here:
https://codesandbox.io/s/heuristic-fermi-b1vi6?file=/src/app/app.component.ts

Hi, im having some problems in the deployment. I just add all the files in my src folder. And show me this error. How i have to call the function useWalletNfts?? You have any code example please!!
Thanks for this!
Could not load source file "../src/index.ts" in source map of<EMAIL_ADDRESS>

hey @marcsabate7
I've updated README with proper example:
https://github.com/NftEyez/sol-rayz/blob/main/packages/sol-rayz-react/README.md
1st of all these are React Hooks and can't be used with classes only with functional components. Google the difference. e.g.
https://dev.to/mehmehmehlol/class-components-vs-functional-components-in-react-4hd3
Also, here is more detailed example:
https://github.com/thuglabs/create-dapp-solana-nextjs/blob/main/src/views/GalleryView/index.tsx

I'm also running into this issue.
The error comes from typescript when setting skipLibCheck to false. The issue is that the referenced file ../types does not exist in the bundle.


Fixes memory leak loading certs

This leak was introduced by f729c9dc41ff1635132f4bdc6331ce826f3bc2fe

This will need to follow #6483

Cherry-picked to v9.0.x branch.


ng set apps.0.serviceworker=true not working

i tried using "ng set app.0.serviceworker=true" for the generation of the ngsw etc, but all i am getting is "can't add property  serviceworker, object is not extensible", please help me

If you're experiencing an issue with Angular's ngsw tool, then https://github.com/angular/mobile-toolkit is the correct project to file it against. It's not related to sw-precache.


How to get current query string inside a  resolver function

Hi,
I want to get current query string inside a resolver function.
If there are multiple queries in this request, I want to get the current resolving query string, not the whole query string. Is it possible? Can I get it from ResolveInfo object ?
The reason for this is because I want to save this query string to somewhere and later use this query string to rerun this query.
Thank you!

The reason for get query string is because I want to save this query string in somewhere, and later run this query again .

I created a function to get current query string from ResolveInfo object:
  public function getCurrentQueryString($pathName, ResolveInfo $info) {
    $wholeQueryString = $info->operation->loc->source->body;

    /**
     * @var \GraphQL\Language\AST\NodeList $nodeList
     */
    $nodeList = $info->operation->selectionSet->selections;
    $count = $nodeList->count();

    for ($i = 0; $i < $count; $i++) {
      /**
       * @var \GraphQL\Language\AST\FieldNode $fieldNode
       */
      $fieldNode = $nodeList->offsetGet($i);

      if ($fieldNode->alias == NULL) {
        $name = $fieldNode->name->value;
      }
      else {
        $name = $fieldNode->alias->value;
      }

      if ($name == $pathName) {
        $start = $fieldNode->loc->start;
        $end = $fieldNode->loc->end;
        $subString = substr($wholeQueryString, $start, $end - $start);
        $currentQueryString = '{ ' . $subString . ' }';

        return $currentQueryString;
      }
    }

    return NULL;
  }

When call this function , pass two variables : $info->path[0] and $info , like this:
  getCurrentQueryString($info->path[0], $info);
This is a temporary solution, I think there should be more better way to do this.

I am probably missing something. Query string term usually refers to the whole query string passed into GraphQL::executeQuery() as a 2nd argument.
But looks like you are trying to get something else. Can you provide an example of the whole query string and the part you want to retrieve? That would help.

Hi @vladar ,
Here is an example, the whole query string is like:
query {
  featured_books {
    bookTitle
    bookAuthor
    bookPrice
  }
  best_seller_books {
    bookTitle
    bookAuthor
    bookPrice
  }
}

I want to get featured_books sub query string and best_seller_books sub query string, inside each resolver function.

First, I don't think it is a good idea. GraphQL also has fragments, variables and include/skip directives so a client may send something like this:
query ($includePrice: Bool) {
  featured_books {
    ...FeaturedBook
  }
  best_seller_books {
    bookTitle
    bookAuthor
    bookPrice @include(if: $includePrice)
  }
}

fragment FeaturedBook on Book {
    bookTitle
    bookAuthor
    bookPrice @include(if: $includePrice)
}

Different clients may send different fragment names, so if you rely on a string - you'll get a bunch of cache duplicates. Variables may also come into play, especially when fields have their own arguments.
Managing caching this way may become quite complicated. Usually, they fetch all the "small" fields in the resolver and cache them by entity id. "Heavy" fields (like nested objects or big texts/blobs) are always resolved separately.
But if you still want to go this route - try using $info->getFieldSelection(). It won't provide you a string but will return a list of all the requested sub-fields  for a given depth so that you could construct a cache key.
Alternatively, you could access the AST of the current field via $info->fieldNodes and re-construct the query.
See description of the ResolveInfo class in docs.


IndexOptimize: Heap (de)fragmentation

Feature request - adding the ability to identify and "fix" heap fragmentation.
I know a heap is usually a bad idea and that heap maintenance is a pain, but there are some valid use cases for heaps.

This would be a very welcome addition

This makes complete sense. There are some situations in which is needed to rebuild a heap (a new datafile was added, for example). If we could have a @RebuildHEAP option in the solution, it would be great !

+1.  I'm managing a vendor DB with 1400+ heap tables. An option to rebuild heaps would be quite welcome. :)

Guys, as we wait for this new feature, I share the code I use in a job to accomplish this task. As it is, it only creates and shows the syntax needed. Uncomment the EXEC line to put it to work. I think you already have written something like this, but this can be helpful to someone.

--> BEGIN SCRIPT
DECLARE @Tablename SYSNAME;
DECLARE @Sintaxis VARCHAR( 500 )
DECLARE Cursor_Heaps CURSOR LOCAL STATIC READ_ONLY FORWARD_ONLY FOR
SELECT SCH.name + '.' + TBL.name
    FROM sys.tables AS TBL
    INNER JOIN sys.schemas AS SCH
    ON TBL.schema_id = SCH.schema_id
    INNER JOIN sys.indexes AS IDX
    ON TBL.object_id = IDX.object_id
    AND IDX.type = 0;
OPEN Cursor_Heaps;
FETCH NEXT FROM Cursor_Heaps INTO @Tablename;
WHILE @@fetch_status = 0
BEGIN

SET @Sintaxis = 'ALTER TABLE ' + @Tablename + ' REBUILD';
PRINT @Sintaxis
--EXEC( @Sintaxis )
FETCH NEXT FROM Cursor_Heaps INTO @Tablename;
END;
CLOSE Cursor_Heaps;
DEALLOCATE Cursor_Heaps;
--> END SCRIPT

Thanks, @EmilioBoucau .  I have also been working on a sproc to help rebuild heaps.  It only rebuilds ones that have user scans in the last x # of days and non-zero forward fetch counts.  My first public repo:
https://github.com/iampeterdaniels/sp_rebuild_heaps

+1 on this request

See https://www.brentozar.com/archive/2016/07/fix-forwarded-records/ on advice to modify IndexOptimize for this situation.
I work with a lot of vendor applications.  Getting vendor approval for clustered indexes meets a ton of resistance even after doing writeups with facts.  Rebuilding heaps using an existing solution is the way to go.


Implements QuizPreview and QuestionWrapper factory

This PR is doing 2 things:

create a QuizPreview component to display a quiz description and general information (see #32)
implement a factory pattern to use the right component depending on the QuestionKind.

Usage
To add a new Question, update schemas/interface.ts, then implement the corresponding component in frontend/scr/components/questions, and then register your component in frontend/scr/components/questions/QuestionWrapper.vue
What's next

[ ] Implements each question component
[ ] The current usage can be tedious since we have an additional step (registering the question component). As a nice to have, we can do this dynamically by loading automatically every files in frontend/scr/components/questions except QuestionWrapper in the factory.

Current dependencies on/for this PR:

main

PR #39   👈

This comment was auto-generated by Graphite.


[ISSUE #4419] Upgrade maven-checkstyle-plugin to 3.1.2

What is the purpose of the change
Fix incorrect indentation issue
Brief changelog
Upgrade maven-checkstyle-plugin to 3.1.2

Codecov Report

Merging #4420 (98ea86c) into develop (b1c5fef) will decrease coverage by 0.12%.
The diff coverage is 100.00%.

@@              Coverage Diff              @@
##             develop    #4420      +/-   ##
=============================================
- Coverage      48.12%   48.00%   -0.13%
+ Complexity      5099     5082      -17
=============================================
  Files            646      646
  Lines          42885    42885
  Branches        5607     5607
=============================================
- Hits           20640    20588      -52
- Misses         19740    19781      +41
- Partials        2505     2516      +11

Impacted Files
Coverage Δ

...ocketmq/broker/processor/SendMessageProcessor.java
40.05% <100.00%> (ø)

...org/apache/rocketmq/store/DefaultMessageStore.java
55.56% <100.00%> (ø)

...in/java/org/apache/rocketmq/test/util/MQAdmin.java
38.88% <0.00%> (-5.56%)
:arrow_down:

...org/apache/rocketmq/store/ha/WaitNotifyObject.java
66.07% <0.00%> (-5.36%)
:arrow_down:

...apache/rocketmq/remoting/netty/ResponseFuture.java
85.00% <0.00%> (-5.00%)
:arrow_down:

...ache/rocketmq/common/stats/MomentStatsItemSet.java
39.13% <0.00%> (-4.35%)
:arrow_down:

...rocketmq/remoting/netty/NettyRemotingAbstract.java
47.08% <0.00%> (-4.02%)
:arrow_down:

...org/apache/rocketmq/common/stats/StatsItemSet.java
41.79% <0.00%> (-2.99%)
:arrow_down:

...rocketmq/common/message/MessageClientIDSetter.java
71.42% <0.00%> (-2.39%)
:arrow_down:

...va/org/apache/rocketmq/logging/inner/Appender.java
34.83% <0.00%> (-2.25%)
:arrow_down:

... and 11 more

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 b1c5fef...98ea86c. Read the comment docs.

Coverage decreased (-0.09%) to 52.062% when pulling 98ea86c9742c156369f061fdc1a218a5ef6e6674 on drpmma:develop-1 into b1c5fefecf08f802935249e9a05bfd3bb1700fdb on apache:develop.


feat(FormValues): adding form type

Overview
In Author, we have quite a few type errors associated with ConnectedForm due to passing something like this into the form:
project: {
        id: "123456",
        title: "Wow this is a real project"
        projectInformation: {
                   taskGroups: [ {tasks: [{id: '1234567', hint: "A task hint",
                                                          title: "Do this task", __typename: 'Task'}]
}
}

Sometimes we need to manipulate these values in our onSubmit that we pass into the form, and typescript is yelling at that because it expects only boolean | string | Pick<FileList, 'item'>; right now.
Values that we expect to be arrays don't currently have .map on them and in the example above, projectInformation that we expect to be of type ProjectInformation (thanks to CSV4 and codegen) also gets cast to something else so we can't manipulate the values of tasks on the tasksGroups.

PR Checklist

[ ] Related to designs:
[ ] Related to JIRA ticket: ABC-123
[ ] I have run this code to verify it works
[ ] This PR includes unit tests for the code change

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.79-alpha.3a5b8a.0@codecademy/gamut-labs@30.2.5-alpha.3a5b8a.0@codecademy/gamut@45.1.4-alpha.3a5b8a.0@codecademy/monaco@0.6.25-alpha.3a5b8a.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://622f4e2b83981914ebd8bffb--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.79-alpha.8e8950.0@codecademy/gamut-labs@30.2.5-alpha.8e8950.0@codecademy/gamut@45.1.4-alpha.8e8950.0@codecademy/monaco@0.6.25-alpha.8e8950.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://622f739f964fa629d5cc36bf--gamut-preview.netlify.appDeploy Logs

here you go: https://github.com/codecademy-engineering/Codecademy/pull/29914!


Update v3-0-reference.md

Translator service added regional support for regions Switzerland North and Switzerland West.

@krishna-doss-mohan : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @krishna-doss-mohan - This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. Would you make this content update in the private repo instead? Thank you! We'll close this PR.


publish gatsby newrelic plugin next to latest on NPM

relates to https://github.com/newrelic/gatsby-plugin-newrelic/issues/44
Acceptance Criteria

[x] confirm with @tristandenyer /  @herecydev  the next branch is available on NPM
[ ] Once confirm this is working for a few users we can publish the next version to latest by merging next into main branch.

@jpvajda we ticked the NR package up to latest 2.1.1, and made a PR. My team will test in BETA and let you know how things go. Thx!

@tristandenyer thank you! We appreciate that. Once we confirm this version is working we can the bump it to the latest release and merge this next branch into main.

@jpvajda looks all good from where we are 👍

@herecydev Thank you!


Performance somehow drops on local installation

I've been playing around with your chroma-key script and all seems to work excellent. However, after about half a minute performance starts dropping in every browser I use. While your online example has no problem whatsoever. It remains fast. I tried stripping everything so only the essentials are left and tried to use your online source, however without success.
Do you have any idea what the problem might be? My video is just 320px < 0.5MB and has a very bright / good background without noice since it's rendered and not recorded.
Also, I am ashamed to ask, but where does the noise in the background of the video on your site come from? I am pretty new with Canvas, but just don't see where the black and red are created / attached. I am obviously looking for a canvas without background so the rendered video is  lying on top of my site.
Thanks!

Did you modify the script at all? If so post it and I'll take a look. If not, it may be how you encoded the video, I can take a look at the video itself as well. I used Premiere to compress the video as much as possible.
The red/black noise code can be seen in this block:
 if (dEScore < 70) {
            data32[y * canvasWidth + x] =
                (255 << 24) |
                (0 << 16) |
                (0 << 8) |
                Math.floor(Math.random() * (255 - 1 + 1) + 1);
            continue;
        }

This is a Uint8ClampedArray:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Uint8ClampedArray
The bitwise OR (|) and shift registers (<<) creates a full byte of data (eg:<PHONE_NUMBER>1111111111111011000101 )
In this case, the data shifts between 0 and whatever RGB code for that red is, because the last line (with Math.floor) is acting as a switch.
This is probably mostly confusing because you're likely asking "Why do this just to oscillate between two colors, surely there are easier ways?" Before publishing that code I had the pixels do rainbow colors, deemed it obnoxious, and removed the bits that made rainbow colors.
We still need the clamped array for performance, though, so removing the code completely won't work. You still need to create a full byte there.

Thank you for your reply, very mutch appreciated!
The video's I've been using (for testing purposes) I've downloaded from iStock. This is one https://media.istockphoto.com/videos/retro-flying-saucer-video-id869298120
I tried edditting the script, but eventually after half a day I came to the conclusion it became slower and slower. I thought this had to do with my changes, so eventually reverted everything. It now still is as you've posted it on your website.
For now I changed all 255's to 0's which makes the video transparent e.g. data32[y * canvasWidth + x] =  (0 << 24) I don't know if this is the best method though. The edges look pretty choppy, but that might be the video.
Thanks again!

Hi Zachary,
Did you perhaps already had the time to see if you experience the same issue? Thanks in advance!
Regards,

Closing due to inactivity. Reopen if needed :-)


Reset form should include Recaptcha

The password reset form is an abuse vector, so it should include Recaptcha.

The add email and phone forms also send communications to unverified destinations and therefore need Recaptcha protection.


⚠ Bofrost.de has degraded performance

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

HTTP code: 200
Response time: 1619 ms

Resolved: Bofrost.de performance has improved in 8c74d1f after 1 hour, 33 minutes.