Intellisense not work with Remote-Extention

when vscode link to remote server by Remote-SSH, the kubernetes Intellisense don't work on .yaml file.
I waited for a long enough time to load the kubernetes extenion for the vscode, but kubernetes Intellisense never appears.

Could you try downgrading to 1.0.2 and see if it works better there?  In 1.0.2 we used a bundled schema to provide intellisense; in 1.0.3 and above we try to download one from the cluster, which puts kubectl and API proxying in play, which might not work right in remote contexts.  (Though it should still fall back to the bundled schema.)  Thanks!  (You can downgrade by choosing Extensions: Install Specific Version of Extension from the command palette.)

Could you try downgrading to 1.0.2 and see if it works better there? In 1.0.2 we used a bundled schema to provide intellisense; in 1.0.3 and above we try to download one from the cluster, which puts kubectl and API proxying in play, which might not work right in remote contexts. (Though it should still fall back to the bundled schema.) Thanks! (You can downgrade by choosing Extensions: Install Specific Version of Extension from the command palette.)

I have downgrading to 1.0.2 and intellisense still not work.

I also encountered a UI problem(not critical) when i tracking problem. detail in here

I am seeing this as well. However, it is possible to see suggestions with "ctrl+space" after typing characters.
However, when multiple pods are in one file (seperated by "---" for instance), no intellisense is available at all.


Add fastClicksExclude param to exclude nodes as fastclick targets

Fastclick implementation causes the Google's Places API place_changed event to not fire when clicking on an auto-completed place.  To overcome this, and still use fastclicks in your app, users needed to listen for the 'DOMNodeInserted' event and add .no-fastclick classes to all child nodes of .pac-container which causes performance issues.
This PR implements a CSS Selector param instead to exclude nodes from being a fastclick target and so the items returned by the Places API can be excluded like the example below.
var myApp = new Framework7({
    fastClicksExclude: '.pac-item, .pac-item span', // CSS Selector
    // ... other parameters
});

Stackoverflow:
http://stackoverflow.com/questions/9972080/cant-tap-on-item-in-google-autocomplete-list-on-mobile#34628921
http://stackoverflow.com/questions/17160220/google-places-autocomplete-with-jquery-mobile-not-working-on-mobile-touch-device/17176350#20056569
Bugs:
https://github.com/nolimits4web/Framework7/issues/888
https://github.com/nolimits4web/Framework7/issues/95

Merged, thanks


Reduce duplication in indentation cops

Introduce ArrayHashIndentation to be used by Style/IndentArray and
Style/IndentHash. This should bring these up from the CodeClimate's
F-class.

:+1:

:+1:


Enable code coverage

added coveralls configuration
updated travis configuration (to run tests with coverage and test over PHP 7.1)
removed redundant .php_cs
added .gitattributes
changed squizlabs/php_codesniffer to zendframework/zend-coding-standard ~1.0.0
updated badges to use SVG images and master branch

Please enable coveralls for the package

Changes Unknown when pulling 626249eab082f0c85e81a7fbeb0a063ea0f229a1 on webimpress:feature/coverage into ** on zfcampus:develop**.


GCP Deployment broken due to update in Kubernetes provider

Describe the bug
GCP deployment is broken due to the update in Kubernetes provider. It seems there are more changes.
How can we help?
Help us help you.

What are you trying to achieve?
Deploy QHub on GCP

How can we reproduce the problem?
Deploy QHub on GCP via latest master

What is the expected behaviour?
Deploy successfully

And what is currently happening?
Deployment fails

Any error messages?

Error: Unsupported block type

  on .terraform/modules/kubernetes/modules/gcp/kubernetes/nvidia_installer.tf line 77, in resource "kubernetes_daemonset" "nvidia_installer":
  77:             requests ***

Blocks of type "requests" are not expected here. Did you mean to define
argument "requests"? If so, use the equals sign to assign it a value.

Error: Terraform exited with code 1.
Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.8.6/x64/bin/qhub", line 8, in <module>
    sys.exit(main())
  File "/opt/hostedtoolcache/Python/3.8.6/x64/lib/python3.8/site-packages/qhub/__main__.py", line 7, in main
    cli(sys.argv[1:])
  File "/opt/hostedtoolcache/Python/3.8.6/x64/lib/python3.8/site-packages/qhub/cli/__init__.py", line 40, in cli
    args.func(args)
  File "/opt/hostedtoolcache/Python/3.8.6/x64/lib/python3.8/site-packages/qhub/cli/deploy.py", line 44, in handle_deploy
    deploy_configuration(
  File "/opt/hostedtoolcache/Python/3.8.6/x64/lib/python3.8/site-packages/qhub/deploy.py", line 21, in deploy_configuration
    guided_install(config, dns_provider, dns_auto_provision, disable_prompt)
  File "/opt/hostedtoolcache/Python/3.8.6/x64/lib/python3.8/site-packages/qhub/deploy.py", line 65, in guided_install
    raise ValueError(f"IP Address not found in: ***cmd_output***")
r: IP Address not found in: b'[command]/home/runner/work/_temp/5e923156-ffe1-41f9-afc5-95e78a099e60/terraform-bin output --json\n***\n::debug::Terraform exited with code 0.\n::debug::stdout: ***%0A\n::debug::stderr: \n::debug::exitcode: 0\n::set-output name=stdout::***%0A\n::set-output name=stderr::\n::set-output name=exitcode::0\n'

Your environment
Describe the environment in which you are experiencing the bug.

Include your conda version (use conda --version), k8s and any other relevant details.

The problem is due to this update:
https://registry.terraform.io/providers/hashicorp/kubernetes/latest/docs/guides/v2-upgrade-guide#changes-to-the-limits-and-requests-attributes-on-all-resources-that-support-a-podspec

The limits and requests attributes on all resources that include a PodSpec, are now a map. This means that limits {} must be changed to limits = {}, and the same for requests. This change impacts the following resources: kubernetes_deployment, kubernetes_daemonset, kubernetes_stateful_set, kubernetes_pod, kubernetes_job, kubernetes_cron_job.

The problem is due to this update:
https://registry.terraform.io/providers/hashicorp/kubernetes/latest/docs/guides/v2-upgrade-guide#changes-to-the-limits-and-requests-attributes-on-all-resources-that-support-a-podspec

The limits and requests attributes on all resources that include a PodSpec, are now a map. This means that limits {} must be changed to limits = {}, and the same for requests. This change impacts the following resources: kubernetes_deployment, kubernetes_daemonset, kubernetes_stateful_set, kubernetes_pod, kubernetes_job, kubernetes_cron_job.


Problems viewMode table doesn't take effect

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
OS Version:
@lszomoru

Steps to Reproduce:

Set Problems: Default View Mode to table in Insiders (W11)
Reload vscode
Problems still appear in tree view mode.
Clicking the View as Table option does work.

By the way, if the default view mode is set to table, shouldn't the View as Table option be toggled to tree and vice versa?
Version: 1.68.0-insider (user setup)
Commit: 528ee1ae3daabe30c1307cf9dcd6e77eb96094bc
Date: 2022-05-26T05:16:43.433Z
Electron: 17.4.4
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.25120

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.67.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

@ArturoDent, the setting controls the mode in which the problems will be displayed by default for a workspace that is being opened for the very first time. After a workspace has been opened the view mode used in the problems view is being save.

@lszomoru I removed the bug label since you also added the as-designed label here, please add the bug label back if necessary.


sieve of eratosthenes | python

i have only added sieve of eratosthenes in this pr, ignore the commits will add trie data structure in the other pr


Wait for another image download shows up when there's no other download

This occurs for all downloads, whether its waiting or not. Problem is, there's no way to differentiate.
Closing for now since I don't think there's anything we can do about this.

What is the solution or workaround for this problem?
After incorrect shutdown of notebook (due to battery) I can't download any new box using kitematic.

This is happening to me and there are no solutions! It's stuck like that for life....


Use expression post aggs and havingspec

The final cut of new  Prototype.
Now we support Expression with Filters Aggs PostAggs and Having specs filters.

@nishantmonu51 sent this new one since the branch is not mergeable https://github.com/b-slim/calcite/pull/4


[FLOC 3189] Updates to the Flocker Node install docs

Fixes 3189
This PR rewrites the Flocker Node services install steps, following a run through between myself, @alicesowerby and @Stephenitis
The content under "full installation" has been split out into smaller documents, and the steps to Flocker Node services have been rewritten to be easier to follow.
I've run through the instructions and they work on my laptop.

Thanks everyone involved with this! It's great to have our install docs simplified :smile:
@davidoliverSP2 please address the comments and resubmit. Most comments are not strictly necessary so I guess use your judgement and let me know if there are any you'd rather not address.

Thanks @adamtheturtle
Changes have been incorporated, although all suggestions related to install/setup-aws.rst have been recorded in FLOC 3279, as this content hasn't changed in this PR, just moved.

Apologies for not using reviewable. Oh well, I made my bed...

Looks good to me, and thanks for writing up FLOC-3279.


Custom Multiple Output ports are not working

Hey there, I've been trying to make a branching structure like a dialogue system. So, I've been trying to convert CustomPortsNode from multiple inputs to mulitple outputs. But whenever I do that, I can connect a single port to another node, though if I try to connect a second one, it throws a NullRefException as follows:

NullReferenceException: Object reference not set to an instance of an object
GraphProcessor.SerializableEdge.CreateNewEdge (GraphProcessor.BaseGraph graph, GraphProcessor.NodePort inputPort, GraphProcessor.NodePort outputPort) (at Assets/com.alelievr.NodeGraphProcessor/Utils/SerializableEdge.cs:53)

And in line 53, we have this:

I've tried to debug, in second port connection attempt, outputPort and owner is null.
Behaviour Example: (Doesn't connect 2nd one and throws the exception at above)

This is the node that I've used, basically it is the same node as CustomPortDataNode, I just flipped input and outputs.
using System.Collections;
using System.Collections.Generic;
using UnityEngine;
using GraphProcessor;
using System.Linq;

[System.Serializable, NodeMenuItem("Custom/MultiPorts")]
public class CustomPortsNode : BaseNode
{
    [Input]
	public List< float >       	inputs;

	[Output]
	public List< float >		outputs; // TODO: custom function for this one

	List< object >				values;

	public override string		name => "CustomPorts";

    public override string      layoutStyle => "TestType";

    // We keep the max port count so it doesn't cause binding issues
    [SerializeField, HideInInspector]
	int							portCount = 1;

	protected override void Process()
	{
		// do things with values
	}

	[CustomPortBehavior(nameof(outputs))]
	IEnumerable< PortData > ListPortBehavior(List< SerializableEdge > edges)
	{
		portCount = Mathf.Max(portCount, edges.Count + 1);

		for (int i = 0; i < portCount; i++)
		{
			yield return new PortData {
				displayName = "In " + i,
				displayType = typeof(float),
				identifier = i.ToString(), // Must be unique
			};
		}
	}

	[CustomPortOutput(nameof(outputs), typeof(float))]
	void PullInputs(List< SerializableEdge > inputEdges)
	{
		//values = inputEdges.Select(e => e.passThroughBuffer).ToList();
	}

	[CustomPortInput(nameof(inputs), typeof(float))]
	void PushOutputs(List< SerializableEdge > connectedEdges)
	{
		// Values length is supposed to match connected edges length
		//for (int i = 0; i < connectedEdges.Count; i++)
		//	connectedEdges[i].passThroughBuffer = values[i];
	}
}

Update: I believe I might have a solution, I've debugged further and found that in BaseGraphView.cs:
if (serializeToGraph)
{
				NodePort inputPort = inputNodeView.nodeTarget.inputPorts.FirstOrDefault(o => o.portData.identifier == inputPortView.portData.identifier);
				NodePort outputPort = outputNodeView.nodeTarget.outputPorts.FirstOrDefault(o => o.portData== outputPortView.portData);

				e.userData = graph.Connect(inputPort, outputPort);
}

This line is
NodePort outputPort = outputNodeView.nodeTarget.outputPorts.FirstOrDefault(o => o.portData== outputPortView.portData); causing that issue. So I've changed it to o.portData.identifier== outputPortView.portData.identifier. And now it seems to be working for output ports.
Do you see any setbacks or side effects that it will cause ? If not, I'll send a PR.

Hi, indeed there is an error in the code that finds the output port, it must use the identifier to find the port. I did a fixed in master for this: https://github.com/alelievr/NodeGraphProcessor/commit/33901bf3b040f844182b305fe2242773c0812dcb where i use GetPort instead of iterating over all ports manually.
Thanks for reporting the issue and taking the time to investigate :)

Thank you for your interest as well :) Good solution, I'll pull and see how it goes. For know I am closing the issue, if something like that occurs I'll open it back up. Cheers!


Update version overwriting in tool check

Closes #531
Signed-off-by: Yankee Maharjan<EMAIL_ADDRESS>
Description

Fixes version overwriting on tool check that causes errors while downloading tools with pinned versions.

[ ] Yes
[x] No

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Documentation

[ ] I have updated the list of tools in README.md if (required) with ./arkade get -o markdown
[ ] I have updated the list of apps in README.md if (required) with ./arkade install --help

Checklist:

[ ] I have updated the documentation accordingly.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[x] I've read the CONTRIBUTION guide
[x] I have signed-off my commits with git commit -s
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

@alexellis added test on the new commit.

@alexellis  it's good!


JobExecutionContext: Replace LinkedHashMap with a ArrayList

Requires less memory.

Current coverage is 81.54% (diff: 91.30%)

Merging #4756 into master will decrease coverage by 0.07%

@@             master      #4756   diff @@
==========================================
  Files          1313       1313
  Lines         45057      45060     +3
  Methods           0          0
  Messages          0          0
  Branches       7059       7060     +1
==========================================
- Hits          36772      36742    -30
- Misses         5613       5636    +23
- Partials       2672       2682    +10

Powered by Codecov. Last update 1167217...bc31da5


Add an env-example file

Creating an env-example file will help the new contributors easily recognize and have an idea about the environment setup variable.
Can you please assign this issue to me under the GSSOC label?
Thanks

@gunner26735 You should check the README file, it contains the environment variables.

Yes correct but similar to an env-sample which is given in client I thought there should be a sample for server as well.
Because NODE_ENV value and MongoDB sample URI are not mention anywhere that's why I created this issue.

Please add a .env.sample file, also update README.md accordingly and also provide a link for the .env.sample file. In the .env.sample file add a comment for NODE_ENV that it's expected value is production.

@gunner26735 Please add a .env.sample file, also update README.md accordingly and also provide a link for the .env.sample file. In the .env.sample file add a comment for NODE_ENV that its expected value is production.

In the README.md file write .env.sample in place of .env sample
Change the name pf file from .env-sample to .env.sample
Follow the client side .env.sample file for writing the values of variables
Comment the value of MONGODB_URI given by you after the giving the variable value
Change the comment for production variable as just "Expected value 'production'"

@gunner26735 Please do the following changes

In the README.md file write .env.sample in place of .env sample
Change the name pf file from .env-sample to .env.sample
Follow the client side .env.sample file for writing the values of variables
Comment the value of MONGODB_URI given by you after the giving the variable value
Change the comment for production variable as just Expected value "production"

@sethshivam11 can you please assign the gssoc label?


Colons get replaced with blank blocks (TypeScript Angular)

Faced to the same issue. I looked deeper, it's precisely this css rule : https://github.com/jesseweed/seti-syntax/blob/157d1fe59a86ccb038b7d047b62c6e4a0e234a38/styles/syntax.less#L236
color & background-color are set on the same gray. I would suggest removing the background-color line and it seems to work but I don't know if it could create a regression.


Question about deprecated fields in Incoming Webhook payload class

com.slack.api.webhook.Payload
The "channel" field is deprecated, is it mean that it is not going to work if I send the message with webhook through the Incoming Webhook app ?

Hi @guy1699, thanks for asking the question! This SDK should have mentioned the reason behind the deprecation a bit more clearly in javadoc (I will do this later).
Before providing a specific answer to your channel parameter question, let me explain the current situation around Incoming Webhooks first. From historical reasons, there are two ways to use Incoming Webhooks in a Slack workspace (I know this is a bit confusing).

:one: Create your own Slack App (recommended way)

Create a Slack app here
Features > Incoming Webhooks Enable Incoming Webhook feature for the created app
Settings > Install App Install the app into your development workspace
(Slack OAuth confirmation page) Select a channel and click Allow button
Grab the issued Webhook URL and use it for sending messages

:two: Use the custom integration "Incoming Webhooks" in App Directory

Access the App Directory page
Click Add to Slack button
Select a channel and click the button
Grab the issued Webhook URL and use it for sending messages

Our current recommendation is :one: for consistent user experience and better app management. With this way, all the deprecated fields already do not work for you.
On the other hand, if you use the legacy integration 2⃣ , those deprecated fields are still available. Even though you are asked to decide one channel to post messages when creating a new one, the legacy integration allows you to post messages in any public channels by passing channel parameter.
Unfortunately, there is no equivalent to the channel parameter in the current Incoming Webhooks (:one:). Our current recommendation is to utilize chat.postMessage API method with channel parameter if your app wants to post to various channels. As for other deprecated parameters like username and icon_url, chat.postMessage API method with additional chat:write.customize permission is the right way to do the same.
Thanks again for asking this! This thread should be helpful for others too. If everything is clear now, would you mind closing this issue?

Sorry, I forgot to mention this: Probably, you're using 2⃣ the Incoming Webhook app in App Directory. As long as the legacy integration is available in the platform, you can expect the channel parameter (and any others that are deprecated in this Java SDK) should work for you.

Thanks


Transclution behaves incorrectly with table elements

Full detailed explanation on this StackOverflow thread:
http://stackoverflow.com/questions/18156930/transclude-in-angular-directive-putting-elements-inside-a-single-span/18157128?noredirect=1#comment26611579_18157128
I am using angular 1.0.7 and bootstrap 2.3.2 for in that example

Old issue, but yeah. This is a won't fix. The browser will discard the ´etc. elements, because they don't have aparent. This is unfortunately how HTML works, see https://github.com/angular/angular.js/issues/1459#issuecomment-67235182. As a workaround, use the directive like this: ...`


running the lib in nextJS middleware

Describe the bug
I am getting:
error - (middleware)\node_modules\mongodb-data-api\dist\mongodb-data-api.esm.js (106:0) @ eval
error - error.toJSON is not a function
Reproduction
-> mongodbDataApi.ts
`
import { createMongoDBDataAPI } from 'mongodb-data-api'
const connectToMongoAPI = (collection: string) => {
if (
!process.env.MONGODB_API_URL ||
!process.env.MONGODB_API_KEY ||
!process.env.MONGODB_CLUSTER ||
!process.env.MONGODB_DB_NAME
)
return undefined
return createMongoDBDataAPI({
apiKey: process.env.MONGODB_API_KEY,
urlEndpoint: process.env.MONGODB_API_URL,
})
.$cluster(process.env.MONGODB_CLUSTER)
.$database(process.env.MONGODB_DB_NAME)
.$collection(collection)
}
export default connectToMongoAPI
`
-> middleware.ts
`
import { NextResponse } from 'next/server'
import type { NextRequest } from 'next/server'
import { getToken } from 'next-auth/jwt'
import connectToMongoAPI from 'lib/mongodbDataApi'
export const middleware = async (req: NextRequest) => {
const session = await getToken({ req, secret: process.env.SECRET })
/// auth Layer
if (
!session &&
!(
req.nextUrl.pathname.startsWith('/auth/login') ||
req.nextUrl.pathname.startsWith('/api/auth')
)
)
return NextResponse.redirect(new URL('/auth/login', req.url))
/// role layer
const res = await connectToMongoAPI('Pages')?.find({ filter: {} })
console.log(res)
}
export const config = {
matcher: ['/((?!_next|favicon.ico).*)'],
}
`
System Info
System:
    OS: Windows 10 10.0.19044
    CPU: (16) x64 Intel(R) Core(TM) i7-10870H CPU @ 2.20GHz
    Memory: 4.26 GB / 15.79 GB
  Binaries:
    Node: 16.16.0 - C:\Program Files\nodejs\node.EXE
    npm: 8.17.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (105.0.1343.50)
    Internet Explorer: 11.0.19041.1566
  npmPackages:
    @babel/core: ^7.18.10 => 7.18.10
    @commitlint/cli: ^17.0.3 => 17.0.3
    @commitlint/config-conventional: ^17.0.3 => 17.0.3
    @emotion/react: ^11.10.4 => 11.10.4
    @emotion/styled: ^11.10.4 => 11.10.4
    @mui/icons-material: ^5.10.3 => 5.10.3
    @mui/lab: ^5.0.0-alpha.99 => 5.0.0-alpha.99
    @mui/material: ^5.10.5 => 5.10.5
    @next-auth/mongodb-adapter: ^1.0.4 => 1.0.4
    @reduxjs/toolkit: ^1.8.4 => 1.8.4
    @storybook/addon-a11y: ^6.5.10 => 6.5.10
    @storybook/addon-actions: ^6.5.10 => 6.5.10
    @storybook/addon-essentials: ^6.5.10 => 6.5.10
    @storybook/addon-interactions: ^6.5.10 => 6.5.10
    @storybook/addon-links: ^6.5.10 => 6.5.10
    @storybook/builder-webpack5: ^6.5.10 => 6.5.10
    @storybook/manager-webpack5: ^6.5.10 => 6.5.10
    @storybook/react: ^6.5.10 => 6.5.10
    @storybook/testing-library: ^0.0.13 => 0.0.13
    @types/bcrypt: ^5.0.0 => 5.0.0
    @types/node: 18.7.1 => 18.7.1
    @types/react: 18.0.17 => 18.0.17
    @types/react-dom: 18.0.6 => 18.0.6
    @typescript-eslint/eslint-plugin: ^5.33.0 => 5.33.0
    @typescript-eslint/parser: ^5.33.0 => 5.33.0
    babel-loader: ^8.2.5 => 8.2.5
    babel-preset-next: ^1.4.0 => 1.4.0
    bcrypt: ^5.0.1 => 5.0.1
    cross-env: ^7.0.3 => 7.0.3
    eslint: ^8.21.0 => 8.21.0
    eslint-config-next: 12.2.4 => 12.2.4
    eslint-plugin-check-file: ^1.2.2 => 1.2.2
    eslint-plugin-prefer-arrow: ^1.2.3 => 1.2.3
    eslint-plugin-storybook: ^0.6.4 => 0.6.4
    husky: ^8.0.0 => 8.0.1
    lint-staged: ^13.0.3 => 13.0.3
    mongodb: ^4.8.1 => 4.8.1
    mongodb-data-api: ^0.2.0 => 0.2.0
    mongoose: ^6.5.2 => 6.5.2
    next: ^12.3.1 => 12.3.1
    next-auth: ^4.10.3 => 4.10.3
    next-redux-wrapper: ^8.0.0 => 8.0.0
    prettier: ^2.7.1 => 2.7.1
    react: 18.2.0 => 18.2.0
    react-dom: 18.2.0 => 18.2.0
    react-hook-form: ^7.34.2 => 7.34.2
    react-redux: ^8.0.2 => 8.0.2
    typescript: ^4.7.4 => 4.7.4
    validate-branch-name: ^1.3.0 => 1.3.0

Used Package Manager
npm
Validations

[X] Read the the documentation in detail.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Also running into this issue. @surmon-china any ideas how to fix?

error.toJSON() It is likely that the error is caused by the internal error handling logic, can you provide a more detailed error stack? It is better to reflect the data type of the error itself.

@surmon-china webpack-internal:/(sc_server)/node_modules/mongodb-data-api/dist/mongodb-data-api.esm.js (117:31).
Here is the code:
import { createMongoDBDataAPI } from 'mongodb-data-api'

const config = {
  apiKey: process.env.MONGODB_API_KEY as string,
  urlEndpoint: process.env.MONGODB_APP_URL as string
}

const mongo = createMongoDBDataAPI(config)

const res = await mongo.$cluster(process.env.MONGODB_CLUSTER).$database(process.env.MONGODB_DB).$collection('posts').find()

Hi! @Ezall2001 @fbjork
I think this issue has been fixed in v0.3.0 (please note there are some breaking change)

@surmon-china I just tried it, but now I get a new error:
Error: Cannot read properties of undefined (reading 'headers')
Call Stack
eval

webpack-internal:/(sc_server)/node_modules/mongodb-data-api/dist/mongodb-data-api.esm.js (109:30)

@surmon-china I just tried it, but now I get a new error:
Error: Cannot read properties of undefined (reading 'headers')
Call Stack
eval

webpack-internal:/(sc_server)/node_modules/mongodb-data-api/dist/mongodb-data-api.esm.js (109:30)

Try v0.4.0 (API key desensitization is no longer processed when an error occurs.)

@surmon-china now I'm getting this error:
  message: 'Adapter http is not supported by the environment',
  name: 'AxiosError',
  description: undefined,
  number: undefined,
  fileName: undefined,
  lineNumber: undefined,
  columnNumber: undefined,
  stack: 'AxiosError: Adapter http is not supported by the environment\n    at Object.getAdapter (webpack-internal:///(sc_server)/./node_modules/axios/dist/node/axios.cjs:2598:23)\n    at Axios.dispatchRequest (webpack-internal:///(sc_server)/./node_modules/axios/dist/node/axios.cjs:2641:30)\n    at Axios.request (webpack-internal:///(sc_server)/./node_modules/axios/dist/node/axios.cjs:2933:39)\n    at MongoDBDataAPI.wrap (webpack-internal:///(sc_server)/./node_modules/axios/dist/node/axios.cjs:28:19)\n    at MongoDBDataAPI.$$action (webpack-internal:///(sc_server)/./node_modules/mongodb-data-api/dist/mongodb-data-api.esm.js:93:69)\n    at MongoDBDataAPI.find (webpack-internal:///(sc_server)/./node_modules/mongodb-data-api/dist/mongodb-data-api.esm.js:119:17)\n    at Page (webpack-internal:///(sc_server)/./app/mongodb/page.tsx:15:71)\n    at preloadComponent (webpack-internal:///(sc_client)/./node_modules/next/dist/esm/server/app-render.js:62:22)\n    at eval (webpack-internal:///(sc_client)/./node_modules/next/dist/esm/server/app-render.js:801:24)\n    at async createComponentTree (webpack-internal:///(sc_client)/./node_modules/next/dist/esm/server/app-render.js:800:25)',
  config: undefined,
  code: 'ERR_NOT_SUPPORT',
  status: null
}```

@surmon-china now I'm getting this error:
  message: 'Adapter http is not supported by the environment',
  name: 'AxiosError',
  description: undefined,
  number: undefined,
  fileName: undefined,
  lineNumber: undefined,
  columnNumber: undefined,
  stack: 'AxiosError: Adapter http is not supported by the environment\n    at Object.getAdapter (webpack-internal:///(sc_server)/./node_modules/axios/dist/node/axios.cjs:2598:23)\n    at Axios.dispatchRequest (webpack-internal:///(sc_server)/./node_modules/axios/dist/node/axios.cjs:2641:30)\n    at Axios.request (webpack-internal:///(sc_server)/./node_modules/axios/dist/node/axios.cjs:2933:39)\n    at MongoDBDataAPI.wrap (webpack-internal:///(sc_server)/./node_modules/axios/dist/node/axios.cjs:28:19)\n    at MongoDBDataAPI.$$action (webpack-internal:///(sc_server)/./node_modules/mongodb-data-api/dist/mongodb-data-api.esm.js:93:69)\n    at MongoDBDataAPI.find (webpack-internal:///(sc_server)/./node_modules/mongodb-data-api/dist/mongodb-data-api.esm.js:119:17)\n    at Page (webpack-internal:///(sc_server)/./app/mongodb/page.tsx:15:71)\n    at preloadComponent (webpack-internal:///(sc_client)/./node_modules/next/dist/esm/server/app-render.js:62:22)\n    at eval (webpack-internal:///(sc_client)/./node_modules/next/dist/esm/server/app-render.js:801:24)\n    at async createComponentTree (webpack-internal:///(sc_client)/./node_modules/next/dist/esm/server/app-render.js:800:25)',
  config: undefined,
  code: 'ERR_NOT_SUPPORT',
  status: null
}```

This looks like an axios request error caused by the runtime environment, can you provide your system info? (npx envinfo --system --npmPackages --binaries --browsers)

@surmon-china here goes. Also note that I'm using the edge runtime with my Next.js project.
  System:
    OS: macOS 13.0.1
    CPU: (6) x64 Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz
    Memory: 844.29 MB / 32.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 16.15.0 - ~/.nvm/versions/node/v16.15.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v16.15.0/bin/yarn
    npm: 8.14.0 - ~/.nvm/versions/node/v16.15.0/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 107.0.5304.110
    Safari: 16.1
  npmPackages:
    @graphql-codegen/cli: 2.13.12 => 2.13.12
    @graphql-codegen/client-preset: 1.1.5 => 1.1.5
    @planetscale/database: ^1.4.0 => 1.4.0
    @tailwindcss/typography: 0.5.8 => 0.5.8
    @types/node: 18.11.9 => 18.11.9
    @types/react: 18.0.25 => 18.0.25
    @types/react-dom: 18.0.9 => 18.0.9
    @xata.io/client: ^0.21.2 => 0.21.2
    autoprefixer: 10.4.13 => 10.4.13
    graphql: 16.6.0 => 16.6.0
    graphql-request: 5.0.0 => 5.0.0
    mongodb-data-api: 0.4.0 => 0.4.0
    next: 13.0.5 => 13.0.5
    postcss: 8.4.19 => 8.4.19
    react: 18.2.0 => 18.2.0
    react-dom: 18.2.0 => 18.2.0
    tailwindcss: 3.2.4 => 3.2.4
    typescript: 4.9.3 => 4.9.3

@surmon-china anything else I can share to help fix this?


feat(): use default website layout if no app layout is present

Addresses: #491
https://user-images.githubusercontent.com/73725297/226471380-5f6b07d9-8c8c-40ea-a2af-18d42a9f57a3.mp4

@Ayon95 you can open PR's directly on this repo. you have write access. For now I have created the branch for you


refactor: improve repartition buffering

Which issue does this PR close?
Closes #4865.
Rationale for this change
The repartition operation had an unbounded buffer. This is not required in all cases and is even counterproductive since it will drive the input nodes to completion while potentially starving the output nodes and while filling up the buffers up to the memory limit (at which point it will just bail out).
What changes are included in this PR?
A somewhat more sophisticated channel construct (distribution channels) that are only unbounded as long as at least one channel is empty. In practice (= for any reasonable repartition config) this will NOT lead to unbounded memory usage since virtually all partitions should eventually receive some data.
Are these changes tested?

all existing tests pass
extensive tests for the distribution construct

Are there any user-facing changes?
Improved scheduling for the repartition operation.

In practice (= for any reasonable repartition config) this will NOT lead to unbounded memory usage since virtually all partitions should eventually receive some data.

I'm sure this doesn't hold in certain cases. Mainly for hash repartition, when cardinality is low, for example lower than the number of target partitions, part of them will not receive any data.

Another "problematic" case is when some column/expression part of a hash repartition has low cardinality and data is sorted or semi-sorted (i.e. the value is repeated many times before moving to a next one), in this case the buffer will fill up until a next value is consumed.
It is still better than the current situation though for other situations.

I agree w/ @Dandandan's assessment.

I plan to review this tomorrow if I can find the time; If not I will certainly do so on Thursday

Looks like this PR has introduced uncontrolled memory consumption 🤔
Which can cause OOM, see my comments here: https://github.com/apache/arrow-datafusion/issues/5108#issuecomment-1412879293

I will look into this report later today -- thank you

@alamb thank you! I've created a new issue (https://github.com/apache/arrow-datafusion/issues/5162), because the initial one could be not related at all. But there are some comments there that could be useful

Looks like this PR has introduced uncontrolled memory consumption 🤔

My measurements appear to show that DataFusion 17.0.0 is actually better than DataFusion 16.0.0 about memory consumption https://github.com/apache/arrow-datafusion/issues/5108#issuecomment-1414320116


swarm-cli  feed upload -T

oot@pixel:/home/ansible/backup-solution-for-nc/swarm-up# swarm-cli  feed upload -T ramesh_nc backup_pixel_nextcloud_2023-11-30_10-17-14.tar.gz-part-012-of-100 --verbose
? Please select a stamp for this action
cad20fadbfed3e825f2598f21b02e841a3a4565699d8027906dd38f39d6cd086 127.76 GB expires in
Upload size is approximately 8.43 MB
Data has been sent to the Bee node successfully!
Swarm hash: 726efcbb86c2b2d59edb98a23c9493aebbcf8083640f801b855608bda4db4e7d
Waiting for file chunks to be synced on Swarm network...
Uploading was successful!
URL: http://localhost:1633/bzz/726efcbb86c2b2d59edb98a23c9493aebbcf8083640f801b855608bda4db4e7d/
ERROR Bad Request

running bee dev

I believe SOCs are no longer supported in bee dev mode, please see https://github.com/ethersphere/bee/issues/4652
Do you have this issue on testnet or mainnet?

Please reopen if this issue happens outside of dev mode.


Data transfer hub solution to work with Azure Blob storage

Customer requesting to migrate data from Azure Blob storage to S3 using automated methods. Data transfer hub works with other cloud storage providers but doesn't currently support Azure Blob storage.

Sorry for the late reply, this feature already supported by AWS DataSync.


Subject Line not showing typed characters

The subject line not showing stuff that is typed.
See below.

Unable to enter text in the subject line as well!


App warns when Foreflight sending is paused due to incomplete data.

Currently the app does not send to ForeFlight if all flight data is not populated.  It does not, however, have any visible indication as such other than the data boxes showing dashes.  Add a warning to the window if ForeFlight sending is paused.

implemented in 1.0.1, https://github.com/eklynx/SimForeflightLink/pull/14


reject attributes that do not have dataset when qualifying

Fixes #288
@solnic @flash-gordon hope this helps with the issue.
Any comments I'll be happy to address them.

@solnic Thank you so much for the comments, as always great advice ❤

Please rebase/squash + merge. We should also cherry-pick this into release-2.x branch and push a new bug fix release. I can deal with that.


Betterhash

Dramatically simplify method hashing.
Use FNV-1  instead of sha1 which is much faster
Remove redundant caches
KISS

Codecov Report

Merging #83 into master will increase coverage by 0.37%.
The diff coverage is 50%.

@@            Coverage Diff            @@
##           master     #83      +/-   ##
=========================================
+ Coverage    2.73%   3.11%   +0.37%
=========================================
  Files          45      44       -1
  Lines        6220    6171      -49
  Branches     1211    1200      -11
=========================================
+ Hits          170     192      +22
+ Misses       6032    5961      -71
  Partials       18      18

Impacted Files
Coverage Δ

MLAPI/MonoBehaviours/Core/NetworkingManager.cs
0% <ø> (ø)
:arrow_up:

MLAPI/MonoBehaviours/Core/NetworkedBehaviour.cs
0% <0%> (ø)
:arrow_up:

...rComponents/Core/InternalMessageHandler.Receive.cs
0% <0%> (ø)
:arrow_up:

MLAPI/Data/StringExtension.cs
100% <100%> (ø)

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 4b476e6...bb618d3. Read the comment docs.


Consider switching Arc to an opaque type

This issue is mostly a placeholder for a discussion leading up to 0.2.
Currently, Arc is used to pass around the unpark handle. This API has a hard requirement on Arc which means that an allocation is required even if it isn't strictly necessary.
I propose switching that to an opaque struct, something like UnparkHandle which would allow the internal representation to change in the future.
There could be a conversion from Arc as I think we would need to maintain that indefinetly.
Relates to #430

I'd be surprised if we could do this, but I'd be willing to try!

Done in #436!


Auto merge auto-update-weights-for-dev-5587d0df66fc923b09c265ceb6494aeaa973dbfd to dev

Codecov Report

Merging #818 (452ee01) into dev (cb8f15c) will not change coverage.
The diff coverage is 93.54%.

@@           Coverage Diff           @@
##              dev     #818   +/-   ##
=======================================
  Coverage   78.24%   78.24%
=======================================
  Files          51       51
  Lines       10317    10317
=======================================
  Hits         8073     8073
  Misses       2244     2244

Impacted Files
Coverage Δ

pallets/creditcoin/src/weights.rs
92.18% <92.59%> (ø)

pallets/difficulty/src/weights.rs
100.00% <100.00%> (ø)

pallets/rewards/src/weights.rs
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Broken documentation link for "new object macro"

Hi,
https://docs.rs/juniper/0.13.0/juniper/macro.graphql_object.html has a notice at the top that says:

The graphql_object! macro is deprecated and will be removed soon. Use the newobject macro instead.

The hyperlink under "object" points at https://docs.rs/juniper/latest/juniper/macro.object.html which doesn't seem to exist. Searching the docs for a macro named "object" doesn't seem to yield anything either.

Thanks for pointing that out, fixed the link.
FYI https://graphql-rust.github.io/juniper/current/types/objects/complex_fields.html also provides more information on the new macro.


Update troubleshooting docs

[x] Section about "name export" build issues (#1070)
[x] Section about shadow DOM (#1029 #1068)
[ ] Waiting on solution for #1067 to another a section about it

Patch file for #1067
react-tooltip-1067.patch


Tweaks to play nice with jlab

Just wondering, are these changes compatible with vanilla Jupyter notebooks?

Yes, this should not get into the way of running "regular" notebooks. These are to make the flexx embeddable in Jlab as a tool to make plugins. A next step would be be to allow running Flexx inside notebooks in jlab, which would require multiple Flexx "sessions" on the same page.


Use one line statement instead of the for of

You're confusing iterables and iterators.
It could have been:
module.exports = iterable => Boolean(iterable[Symbol.iterator]().next().done);

But I think the current is clearer.

That's not the same. A one liner would be:
return iterable[Symbol.iterator]().next().done;

See the specs or MDN for details.

@schnittstabil Lol.

Hey @sindresorhus,
!Array.from(iterable).length will make a needless conversion. so you avoid it, right?

Yes


add robustness to generated loop code

Certain expressions—integers (with or without a preceding +/-), null,
and void—when used as sources of for loops resulted in illegal
JavaScript being generated. While (42).length is a silly but legal thing
to do, 42.length is an actual SyntaxError in JS. This commit adds checks
to wrap potentially problematic expressions in parentheses.

(For why-the-heck-does-he-want-this background: I was working on #831 and kept getting very annoying-to-diagnose errors from the test suite. I had to binary search the files with comments, because of course the JavaScript SyntaxErrors didn't give me a line number. Not fun. I'm just trying to help out the next guy who goes experimenting with loop, slice, or spread syntax.)


cargo fails to download git package

Problem
I was trying to build Meilisearch with AI support and ran into this error. The URL resolves, so not sure what the issue might be.
cargo build --release --features cuda
    Updating crates.io index
error: failed to download `candle-kernels v0.3.1 (https://github.com/huggingface/candle.git#f4fcf609)`

Caused by:
  unable to get packages from source

Caused by:
  failed to find candle-kernels v0.3.1 (https://github.com/huggingface/candle.git#f4fcf609) in path source
note: this is an unexpected cargo internal error
note: we would appreciate a bug report: https://github.com/rust-lang/cargo/issues/
note: cargo 1.76.0 (c84b36747 2024-01-18)

Steps
Download Meilisearch and follow build instructions (which are really simple).
Possible Solution(s)
If I was to guess, I wonder if the hashtag is causing the issue?
Notes
No response
Version
cargo 1.76.0 (c84b36747 2024-01-18)
release: 1.76.0
commit-hash: c84b367471a2db61d2c2c6aab605b14130b8a31b
commit-date: 2024-01-18
host: x86_64-unknown-linux-gnu
libgit2: 1.7.1 (sys:0.18.1 vendored)
libcurl: 8.5.0-DEV (sys:0.4.70+curl-8.5.0 vendored ssl:OpenSSL/1.1.1w)
ssl: OpenSSL 1.1.1w  11 Sep 2023
os: Pop!_OS 22.04 (jammy) [64-bit]

Thanks for the report. The hashtag is how Cargo represents and records a precise commit. It is not related to how GitHub handles URLS, so might not be related.
Haven't dug deeper, but it might be the package.exclude containing candle-kernels led to the issue.


Added copy_if on device test case

Added copy_if on device test case

The same failures are seen on https://github.com/ROCmSoftwarePlatform/rocThrust/pull/145.  Unclear which changeset is causing the fails.

The same failures are seen on #145. Unclear which changeset is causing the fails.

We can build on our side. Can you send the build error?

I am trying to figure out what it is. We didn't use ninja for the builds. I do not think that should impact this but I can add that.

Could someone restart the CI run? It should pass now, with the latest rocPRIM develop branch.


Update akka-actor, akka-persistence, ... to 2.6.11

Updates

com.typesafe.akka:akka-actor
com.typesafe.akka:akka-persistence
com.typesafe.akka:akka-slf4j
com.typesafe.akka:akka-stream-testkit
com.typesafe.akka:akka-testkit

from 2.6.7 to 2.6.11.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.typesafe.akka" } ]

labels: library-update, semver-patch

Superseded by #580.

Superseded by #580.


Angular 12.1.0 big rebuild time

🐞 Bug report
Command (mark with an x)

[ ] new
[ ] build
[x] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[ ] extract-i18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Is this a regression?
It was much faster for rebuilds with ng11.1.2 + NG_BUILD_IVY_LEGACY=1 (see the table below).
Description
Rebuild time for AppComponent changes (adding console.logs) increase drastically with the amount of code.
We have relatively big application. Here are some measures for starting server and rebuilding on changes in AppComponent for different cases.

server
AppComponent

default
180s
65s

default, --aot=false
105s
3.5s

12 of 24 lazy routes disabled
125s
45s

18 of 24 lazy routes disabled
100s
8.5s

all lazy routes disabled
52s
2.2s

ng11 default
350s
14s

(ng11 - 11.1.2 version with NG_BUILD_IVY_LEGACY=1)
(all changes are adding console.log() statements to AppComponent, median of 3-4 passes excluding first on)
🔬 Minimal Reproduction
Don't have a public reproduction. Attaching rebuild performance profiling for 18 of 24 lazy routes disabled case.
CPU-20210707T141946.cpuprofile
https://drive.google.com/file/d/1LQzweIGTErNLmjcLhDjnGOSWiVbol-gR/view?usp=sharing

Cant profile the default case with all routes enabled - chrome crashes trying to dump all this stuff :(
🔥 Exception or Error
🌍 Your Environment

Angular CLI: 12.1.0
Node: 12.18.1
Package Manager: yarn 2.4.2
OS: win32 x64

Angular: 12.1.0
... animations, cdk, cli, common, compiler, compiler-cli, core
... elements, forms, language-service, localize, material
... material-moment-adapter, platform-browser
... platform-browser-dynamic, platform-server, router
... youtube-player

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1201.0
@angular-devkit/build-angular   12.1.0
@angular-devkit/core            12.1.0
@angular-devkit/schematics      12.1.0
@angular/flex-layout            12.0.0-beta.34
@ngtools/webpack                12.1.0
@nguniversal/builders           12.1.0
@nguniversal/express-engine     10.1.0
@schematics/angular             12.1.0
rxjs                            6.6.7
typescript                      4.3.4
webpack                         5.40.0

Anything else relevant?
This issue affects several of our projects relatively same size.  Most of our code is inside libs/ subfolders and is imported directly by sources (nrwl/nx like monorepo).
Can debug something else, share screen or provide TeamViewer access to our codebase to check anything (discord drow#4335)

I wonder if this the same as https://github.com/angular/angular-cli/issues/21116 which was determined to be an issue in the TypeScript compiler.
Can you check if you get similar results running TSC directly.
tsc --watch --project <path-to-app-tsconfig>/tsconfig.app.json

> packages\student-cabinet> yarn tsc --watch --project tsconfig.app.json

[19:10:56] Starting compilation in watch mode...
[19:11:47] Found 0 errors. Watching for file changes.

[19:13:21] File change detected. Starting incremental compilation...
[19:13:22] Found 0 errors. Watching for file changes.

[19:13:34] File change detected. Starting incremental compilation...
[19:13:35] Found 0 errors. Watching for file changes.

Same changes in AppComponent, nothing commented out (default case from above), ~50s starting and ~1s rebuilding.
Also you can see low results for the default, --aot=false case in first post. So only aot mode is affected by this regression.

Could you please also run 11 without NG_BUILD_IVY_LEGACY=1; that environment variable makes for an unfair comparison as NG_BUILD_IVY_LEGACY=1 moves type-checking off to a different process, not blocking JS emit.
The Ivy build pipeline is doing incremental type-checking, instead of offloading it to a different worker. From your profile however I notice that type-checking of templates have to be redone. This might be due to a path normalization issue on Windows, where the cached template diagnostics are missed and therefore recomputed.
Additionally, what is strange is that the profile is showing that program structure could not be reused. Was this perhaps the first rebuild? That would explain why no program reuse was available and also why template type-checking had to be redone.

Was this perhaps the first rebuild

There are 3-4 rebuilds starting with the second one for each case before getting average value. First rebuild in ng12 is roughly the same as the following ones, first one in ng11.1.2 with NG_BUILD_IVY_LEGACY=1 is 4-5 times slower (100s vs 14s following)

This might be due to a path normalization issue on Windows

same issue has my colleague with MacOS for the same project (asked him to recheck tomorrow and to record cpu profile for the 18 of 24 lazy routes disabled case)

run 11 without NG_BUILD_IVY_LEGACY=1;

ng 11.1.2, default case, NG_BUILD_IVY_LEGACY=0

server start 400s
first rebuild 337s
second rebuild 325s

also noticed a huge memory consumption ~6.2gb for first rebuild and ~7.1gb for the second (looks like all free memory). Same for ng12 rebuilds - uses up to all available memory (started with node --max-old-space-size=8192)

It seems very similar to #21228 , is possible that you have<EMAIL_ADDRESS>in your project?

nope, regular scss styling

cpu profile of 4th rebuild, 18 of 24 lazy routes disabled case, MacOS
https://drive.google.com/file/d/1PO2CBRNoeERlidPY3NMnOdK845R-4ceA/view?usp=sharing

Could you set "angularCompilerOptions": { "tracePerformance" : "/path/to/log.json" } in a tsconfig.json file? That should write additional performance statistics to the specified file. That property is not documented/supported and the generated output format is unstable, but it might provide some insights into what is going on.

node --max-old-space-size=8000<EMAIL_ADDRESS>-p tsconfig.app.json --watch

Server started
{
  "events": {
    "InputDtsFile": 1759,
    "InputTsFile": 10517,
    "AnalyzeComponent": 1682,
    "AnalyzeDirective": 77,
    "AnalyzeInjectable": 687,
    "AnalyzeNgModule": 559,
    "AnalyzePipe": 47,
    "TraitAnalyze": 3052,
    "GenerateTcb": 1682,
    "UpdateTypeCheckProgram": 1,
    "EmitSourceFile": 5374
  },
  "phases": {
    "Unaccounted": 2149638,
    "Setup": 1452,
    "TypeScriptProgramCreate": 14520731,
    "TypeScriptDiagnostics": 16945268,
    "Analysis": 6057360,
    "Resolve": 1093654,
    "CycleDetection": 135902,
    "TcbGeneration": 3850441,
    "TcbUpdateProgram": 3214251,
    "TypeScriptEmit": 15904762,
    "Compile": 4737047,
    "TtcDiagnostics": 8363886
  },
  "memory": {
    "Initial": 71360216,
    "TypeScriptProgramCreate": 577769256,
    "Analysis":<PHONE_NUMBER>,
    "Resolve":<PHONE_NUMBER>,
    "TtcUpdateProgram":<PHONE_NUMBER>,
    "PreEmit":<PHONE_NUMBER>,
    "Emit":<PHONE_NUMBER>
  }
}

First rebuild
{
  "events": {
    "InputDtsFile": 1759,
    "InputTsFile": 10517,
    "AnalyzeComponent": 1682,
    "AnalyzeDirective": 77,
    "AnalyzeInjectable": 687,
    "AnalyzeNgModule": 559,
    "AnalyzePipe": 47,
    "TraitAnalyze": 3052,
    "GenerateTcb": 1682,
    "UpdateTypeCheckProgram": 1,
    "EmitSourceFile": 5374
  },
  "phases": {
    "Unaccounted": 73803,
    "Setup": 115024,
    "TypeScriptProgramCreate": 7789981,
    "Reconciliation": 17248,
    "TypeScriptDiagnostics": 16368127,
    "Analysis": 5063386,
    "Resolve": 1461536,
    "CycleDetection": 252679,
    "TcbGeneration": 4182421,
    "TcbUpdateProgram": 2983010,
    "TypeScriptEmit": 13762470,
    "Compile": 4761262,
    "TtcDiagnostics": 8074679
  },
  "memory": {
    "Initial":<PHONE_NUMBER>,
    "TypeScriptProgramCreate":<PHONE_NUMBER>,
    "Analysis":<PHONE_NUMBER>,
    "Resolve":<PHONE_NUMBER>,
    "TtcUpdateProgram":<PHONE_NUMBER>,
    "PreEmit":<PHONE_NUMBER>,
    "Emit":<PHONE_NUMBER>
  }
}

Second rebuild
{
  "events": {
    "InputDtsFile": 1759,
    "InputTsFile": 10517,
    "AnalyzeComponent": 1682,
    "AnalyzeDirective": 77,
    "AnalyzeInjectable": 687,
    "AnalyzeNgModule": 559,
    "AnalyzePipe": 47,
    "TraitAnalyze": 3052,
    "GenerateTcb": 1682,
    "UpdateTypeCheckProgram": 1,
    "EmitSourceFile": 5374
  },
  "phases": {
    "Unaccounted": 87090,
    "Setup": 20138,
    "TypeScriptProgramCreate": 7773523,
    "Reconciliation": 24136,
    "TypeScriptDiagnostics": 15853157,
    "Analysis": 4532055,
    "Resolve": 975659,
    "CycleDetection": 141955,
    "TcbGeneration": 3536365,
    "TcbUpdateProgram": 2478772,
    "TypeScriptEmit": 12085801,
    "Compile": 3330321,
    "TtcDiagnostics": 7736459
  },
  "memory": {
    "Initial":<PHONE_NUMBER>,
    "TypeScriptProgramCreate":<PHONE_NUMBER>,
    "Analysis":<PHONE_NUMBER>,
    "Resolve":<PHONE_NUMBER>,
    "TtcUpdateProgram":<PHONE_NUMBER>,
    "PreEmit":<PHONE_NUMBER>,
    "Emit":<PHONE_NUMBER>
  }
}

Third rebuild
{
  "events": {
    "InputDtsFile": 1759,
    "InputTsFile": 10517,
    "AnalyzeComponent": 1682,
    "AnalyzeDirective": 77,
    "AnalyzeInjectable": 687,
    "AnalyzeNgModule": 559,
    "AnalyzePipe": 47,
    "TraitAnalyze": 3052,
    "GenerateTcb": 1682,
    "UpdateTypeCheckProgram": 1,
    "EmitSourceFile": 5374
  },
  "phases": {
    "Unaccounted": 80811,
    "Setup": 17180,
    "TypeScriptProgramCreate": 7958840,
    "Reconciliation": 10814,
    "TypeScriptDiagnostics": 14910830,
    "Analysis": 4866759,
    "Resolve": 1037635,
    "CycleDetection": 127137,
    "TcbGeneration": 3612529,
    "TcbUpdateProgram": 2565787,
    "TypeScriptEmit": 12319332,
    "Compile": 3264253,
    "TtcDiagnostics": 7595661
  },
  "memory": {
    "Initial":<PHONE_NUMBER>,
    "TypeScriptProgramCreate":<PHONE_NUMBER>,
    "Analysis":<PHONE_NUMBER>,
    "Resolve":<PHONE_NUMBER>,
    "TtcUpdateProgram":<PHONE_NUMBER>,
    "PreEmit":<PHONE_NUMBER>,
    "Emit":<PHONE_NUMBER>
  }
}

The main issue is fixed by this PR https://github.com/angular/angular/pull/42759. Recompile time droped to this (default case)
- first rebuild 41735ms
- second 15193ms
- third 18841ms
- fourth 16084ms

still investigating why it's 16-18s for two files recompiling (AppComponent + root module, or for main.ts changes)


[Fix] Faster R-CNN fix in ONNX Runtime

Motivation
In the current version of mmdetection, the quality of the Faster R-CNN model in ONNX Runtime has dropped.
This PR will fix it and return the quality as in the table.
To get the results I used tools/deployment/test.py configs/faster_rcnn/faster_rcnn_r50_fpn_1x_coco.py --eval bbox:

master
fix_faster_rcnn

Average Precision  (AP) @[ IoU=0.50:0.95 , area=   all , maxDets=100 ]
0.370
0.374

Average Precision  (AP) @[ IoU=0.75      , area=   all , maxDets=1000 ]
0.575
0.582

Average Precision  (AP) @[ IoU=0.50:0.95 , area= small , maxDets=1000 ]
0.402
0.406

Average Precision  (AP) @[ IoU=0.50      , area=   all , maxDets=1000 ]
0.207
0.212

Average Precision  (AP) @[ IoU=0.50:0.95 , area=medium , maxDets=1000 ]
0.404
0.409

Average Precision  (AP) @[ IoU=0.50:0.95 , area= large , maxDets=1000 ]
0.481
0.481

Average Recall     (AR) @[ IoU=0.50:0.95 , area=   all , maxDets=100 ]
0.502
0.517

Average Recall     (AR) @[ IoU=0.50:0.95 , area=   all , maxDets=300 ]
0.502
0.517

Average Recall     (AR) @[ IoU=0.50:0.95 , area=   all , maxDets=1000 ]
0.502
0.517

Average Recall     (AR) @[ IoU=0.50:0.95 , area= small , maxDets=1000 ]
0.306
0.325

Average Recall     (AR) @[ IoU=0.50:0.95 , area=medium , maxDets=1000 ]
0.540
0.557

Average Recall     (AR) @[ IoU=0.50:0.95 , area= large , maxDets=1000 ]
0.641
0.648

Modification

mmdet/models/dense_heads/rpn_head.py: Removed re-filtering with nms_pre before nms.
tools/deployment/pytorch2onnx.py: Moved the input name into a variable, since it is used twice.

@RunningLeon
Hello, could you take a look?

@SemyonBevzuk Sure. BTW, thanks for the contribution.


ADMIN: Fix spurious complexity in setup.py

Don't need to unpack a list literal--just pass directly as separate arguments.
Closes #22.

Codecov Report

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

@@          Coverage Diff          @@
##           master    #23   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           3      3
  Lines          42     42
=====================================
  Hits           42     42

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 a2b7143...577e718. Read the comment docs.


Update 1.10 release notes to reflect container name change

As discussed in standup on 28/11!

/test pull-cert-manager-website-verify

/lgtm

Is this Helm only?
/hold

Is this Helm only? /hold

@inteon : The changes in https://github.com/cert-manager/cert-manager/pull/5410 seemed to be Helm only to me - were there other changes beyond that?

Have also updated the release notes on GitHub.

/unhold

@inteon I think it would require another LGTM too unfortunately!

/lgtm


Trajectory with motor

-Added motor controls to "PreditionEdgeTPU.py"
-Removed auto list loading in the constructor of Prediction class in "prediction.py" so that this should work in real time.

No testing done yet, I don't think we can merge this into main


[1.26 hotfix] limit fetch commit response size and increase request & response limit

Description
Describe the changes or additions included in this PR.
Test plan
How did you test the new or updated feature?

Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.

[ ] Protocol:
[ ] Nodes (Validators and Full nodes):
[ ] Indexer:
[ ] JSON-RPC:
[ ] GraphQL:
[ ] CLI:
[ ] Rust SDK:

Picked directly by @ebmifa.


test: verify tailwind example with playwright tests

This runs the Playwright tests for the tailwind example as part of the verify-examples task flow, via the web-test task.
Verification:
From the examples/tailwind directory...

Run cargo make setup
Run cargo make web-test

Nice, thanks!


Add support of CI procedure for web pyjokes implementation

The general idea of this PR is to (revive cool project as last commits were about 3 years ago!) implement CI procedure that contains following options:

Add flake integration
Add pylint integration
Add mypy integration
Add black integration
Add unittests integration
Run static code assessment in CI

Additionally, some enhancements were also added such as updated wiki (README.md file) and internal code structure.
Thanks for having pyjokes, it is really awesome stuff!

@oiertwo Hey, If you don't mind I just created a PR, please review it once you have time for, thanks :)

I made this fr a maker fair stand, it was something simple and fast. Now its also cool and has unittes, CI... !! Thanks!!!


ES5 Compatiblitiy

ES5 Compatibility changes for IE, fixes #439.  I just converted arrow functions to regular functions and other small changes to get the library running on IE.
I currently use Azure, so I'm unable to test any AWS specific code.

This seems like a really good and simple fix @oh-yeah - I'll try and take a look over the next few nights and get it merged in and released.

Hi @rowanwins!
First of all thank you so much for having created this component, it is very useful for a project I am working on at the moment!
Also wanted to say that I am very much looking forward to seeing this PR released, as we need to have our project compatible with Internet Explorer. Thanks again for your efforts!

@rowanwins Any luck implementing this fix?

+1

Hi you can fork @oh-yeah work and build and replace in your package.json  "vue2-dropzone": "git+https://github.com//vue-dropzone.git",
Actually i use this tips.

Actually this PR is broken. I just ran some tests. vue-dropzone.vue comes back saying processFile doesn't exist, and urlsigner.js errors with object type conversion. I was able to fix on my own, but I'm not sure I did it in the best way.
https://github.com/XGhozt/vue-dropzone/commit/5882341af420fab84d2b074d0578c0a468aa0786

Changing
data() { ... }

to
data: function() { ... }

breaks scoping and shouldn't be required in the first place.
The easier solution would be to handle transpiling with a build step.

  Use Babel to transpile the code to ES5 or whatever you need.  Make sure it's not in your exclusion list if you use Webpack (node_modules usually is).
Worst-case, the package should be modified to use Babel in its build step to generate ES5 dist files.  The source code should not be modified.

I agree with @hackel. project requirements might change so instead of shipping code for IE11 , we can simply expose src directory and allow user build config to take over. only drawback is for users , who is using vue-dropzone from cdn(direct script tag).I think most of the projects which needs ie supports uses some sort of build setup or cli.In any case, I think we should expose src dir in pkg.json file.
I have created pull request:- please review.
https://github.com/rowanwins/vue-dropzone/pull/534
For people who want IE11 ASAP. look into patch-package(https://www.npmjs.com/package/patch-package)


[vscode extension] update README

Summary
Update README.md in vscode-extension.
How was it tested?

thanks!


Modification in nms_wrapper.py for CPU use

Modification in nms_wrapper.py fixes the error in proposal_layer.py
/

tf-faster-rcnn/tools/../lib/layer_utils/proposal_layer.py", line 46, in proposal_layer
keep = keep[:post_nms_topN]

Sample code:

def nms(dets, thresh, force_cpu=False):
   #Dispatch to either CPU or GPU NMS implementations.

    if dets.shape[0] == 0:
        return []
    if cfg.USE_GPU_NMS and not force_cpu:
        #return gpu_nms(dets, thresh, device_id=cfg.GPU_ID)
        return cpu_nms(dets, thresh)
    else:
        return cpu_nms(dets, thresh)

You need to rebase your code

Sorry, I am new to GitHub and I am not sure what I have to do. Could you please explain me?

https://help.github.com/articles/about-git-rebase/


Literate Programming

While reading some ASP code today I realized that the authors had quite lengthy documentation blocks as comments above predicate definitions or smaller chunks of code. I thought that Literate Programming would be the preferred layout to write code like this, and we might want to support it.
For example, Clique in Literate Answer Set Programming (with disjunction):
# The *3-Clique Problem*

The *3-Clique Problem* is a decision problem. Given a *graph*, consisting of *vertices*
and *edges* that connect two vertices each, can we find 3 vertices, such that they are
all pairwise connected?

## Instance

We will be looking at four nodes

    vertex(1..4).

that are connected as follows:

    edge(1,2).
    edge(1,3).
    edge(1,4).
    edge(2,3).

To ensure undirectedness of edges, we add the following rule to establish symmetry:

    edge(U,V) :- edge(V,U).

## Guess

We will use the `clique` predicate to mark those vertices that are in the clique.
For any vertex, it might or might not be in the clique.

    clique(V) v -clique(V) :- vertex(V).

## Check

At least k vertices must be in the clique.

    :- #count{V : clique(V)} < 3.

Every two vertices that are in the clique must be connected through an edge.

    :- clique(U), clique(V), U != V, not edge(U,V), not edge(V,U).

That is a big-step enhancement and quite far ahead of all the other issues. I did not recall Literate Programming but I've had related ideas a long time ago (and with no connection to ASP). This can be some very nice addition to the system. I need some more time to fully understand its implication, however.
For example, you changed the parser to ignore all errors and continue with the rest, right? So if I write a comment like This is the code about bovines (cows). For whatever reasons... then the answer sets will contain bovines(cows) because that looks like a fact? This seems to be dangerous.
On the other hand, I like the idea that your example above is the actual input!

No, I wrote a small pre-processing routine Util.literate which operates on a stream of lines Stream<String>. It comments out everything that is not indented by at least four spaces and removes those spaces in case they are there.
So what the parser would see in case of the above example is the following:
% # The *3-Clique Problem*
%
% The *3-Clique Problem* is a decision problem. Given a *graph*, consisting of *vertices*
% and *edges* that connect two vertices each, can we find 3 vertices, such that they are
% all pairwise connected?
%
% ## Instance
%
% We will be looking at four nodes
%
vertex(1..4).
%
% that are connected as follows:
%
edge(1,2).
edge(1,3).
edge(1,4).
edge(2,3).
%
% To ensure undirectedness of edges, we add the following rule to establish symmetry:
%
edge(U,V) :- edge(V,U).
%
% ## Guess
%
% We will use the `clique` predicate to mark those vertices that are in the clique.
% For any vertex, it might or might not be in the clique.
%
clique(V) v -clique(V) :- vertex(V).
%
% ## Check
%
% At least k vertices must be in the clique.
%
:- #count{V : clique(V)} < 3.
%
% Every two vertices that are in the clique must be connected through an edge.
%
:- clique(U), clique(V), U != V, not edge(U,V), not edge(V,U).

Note that this preserves line numbers.
There might be more sophisticated implementation using Lexer Modes with ANTLR, but I did not get that to work.

Interesting idea! It reminds me of Achievements in Answer Set Programming, which seems to be a related concept.

I think that Literate Programming and Achievements in Answer Set Programming can be combined, and this does not look too bad.
IMO Achievements is the postfix version of what I did naturally in my example (i.e., instead of first explaining the rule and then introducing it, achievements record the effect of the rule after stating it). I slightly adopted Fig. 4 from your reference and got the following:
# NQueens

input: positive integer n (size of the board).

## Instance

A square is represented as a pair, column number and row number,
both from the set `{1,..,n}`.

    row(1..n).

*achieved*: `row/1 = {1,...,n}`.

    col(1..n).

*achieved*: `col/1 = {1,...,n}`.

## Guess

    n { queen(I,J) : col(I), row(J) } n.

*achieved*: Set `queen/2` consists of n squares.

## Check

    :- queen(I,J), queen(I,JJ), J != JJ.

*achieved*: Each column includes at most one square from `queen/2`.

    :- queen(I,J), queen(II,J), I != II.

*achieved*: Each row includes at most one square from `queen/2`.

    :- queen(I,J), queen(II,JJ), (I,J) != (II,JJ), |I-II|=|J-JJ|.

*achieved*: Each diagonal includes at most one square from `queen/2`.


Pytest skel

Type of change

[ ] Refactor
[X] New feature
[ ] Bug fix
[ ] Optimization
[ ] Documentation Update

Description
Implements the basics of pytest testing.
Related Tickets & Documents
N/A
Checklist before requesting a review

[X] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.

Testing
make test!!! 🥳

/retest

/lgtm

/retest

https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_lightspeed-service/26/pull-ci-openshift-lightspeed-service-main-unit/1729607918023610368
failed because our "root" image is actually golang based.
need to fix up the unit test job like https://github.com/openshift/release/pull/45980 does
i'll submit a PR and rehearse it.

/hold
need to fix the makefile targets

@thoraxe well we've fixed your pip problem, but there's still a failure in the job you'll need to look at:
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_lightspeed-service/26/pull-ci-openshift-lightspeed-service-main-unit/1729616953988878336
ImportError while importing test module '/home/prow/go/src/github.com/openshift/lightspeed-service/test_ols.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib64/python3.11/importlib/__init__.py:126: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
test_ols.py:1: in <module>
    from fastapi.testclient import TestClient
E   ModuleNotFoundError: No module named 'fastapi'

guessing you need to pip install requirements.txt and requirements-test.txt

/retest

/retest

/refresh

/hold cancel

/lgtm

@vishnuchalla 100% agree. Once your refactor lands I will refactor the tests appropriately.


Fixes

Add ConstEq typeclass in IO to make integrating credentials/MACs into bigger data types easier (ref https://github.com/ambiata/zodiac/pull/23) (#45).
Fix hardcoded pointer size I forgot to deal with last PR (#46).
Render hex encoding of MACs so we don't have to do it in client libraries.

@markhibberd
/cc @erikd-ambiata @thumphries @charleso

🍯

:+1:


Added a license

MIT is mentioned in the README, but an explicit file is not present in the repository.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


CORS Preflight request: return supported headers

Summary
When bee-js is used in the browser it can sometimes trigger CORS Preflight request, where the browser sends OPTIONS request to Bee to verify that it will comply with Bee's CORS policy.
One reason when the Preflight check is triggered is when a "non-standard" header is attached to the request. Then the response to the Preflight request must also contain all headers that the server deems valid (in the Access-Control-Allow-Headers header).
This is not happening currently and it restricts the feature set available to browser users. For example for the /dirs endpoint, you support Swarm-Index-Document, Swarm-Error-Document and many others which are not returned in the Access-Control-Allow-Headers response headers.

Actual behavior
Returned headers:
HTTP/1.1 200 OK
Access-Control-Allow-Headers: Origin, Accept, Authorization, Content-Type, X-Requested-With, Access-Control-Request-Headers, Access-Control-Request-Method
...

To demonstrate this issue I have created a simple page for it.
https://gateway.ethswarm.org/bzz/7bafc00de4423a335c7e6ac577211e7055258538a73d41aea6c1107ebdd91cf4/
If not present in Bee network, you can also view it here: https://htmlpreview.github.io/?https://github.com/ethersphere/examples-js/blob/feat/cors-preflight/cors-preflight/index.html

@Eknir please have a look. ^^^


⚠ GitHub has degraded performance

In fe066bf, GitHub (https://www.githubstatus.com/api/v2/status.json) experienced degraded performance:

HTTP code: 200
Response time: 4187 ms

Resolved: GitHub performance has improved in 22a5b45.


validation errortemplates popup always shown on top with opened flyout

nasty issue, don't know how to solve this for now... it happens with opened flyout, if user selects the control with the validation...

I’m closing this issue because IMO this can only be fixed by using a different validation implementation. The current one uses a Popup to show the validation error text. That's the reason why it shows over the Flyout, because Popup uses internally a window to show their content.
Thank you! 🙏


feat: add navigating away confirmation when in the integration editor

This adds a reusable component WithLeaveConfirmation that can be used to protect a page/section from navigating away.
In the integration editor, it's used by setting the shouldDisplayDialog property to a function that checks if the following URL is outside the "mountpoint" of the editor.
Demo

PR Storybook available here

Awesome!  I think from the add step page we could skip the confirmation if the integration hasn't been modified, but we could save that for a future PR too, like one for fixing an issue I need to raise still about showing some kind of dirty/modified state with the save/publish buttons :smile:

Yeah this was more a quick win than anything, since the way it’s wired child pages can’t really control the logic.


Data source

Hi all,
I had installed this Script on my phone where I am using outlook as a data source. As you described, when using showAll parameter the script have to work anyway. Nope, unfortunately not.
The Error is on line 110:45: ReferenceError: Can’t find variable: getFixedDate
Regards, Eric

Hi,
how did you install the script? By hand (marking everything, copying and pasting it in Scriptable) oder using Scriptdu.de ?
My hot guess is you did it by hand and missed the the part at the very bottom of the file https://raw.githubusercontent.com/lwitzani/daysUntilBirthday/main/daysUntilBirthdayWidget.js
The last function at the bottom is the function called getFixedDate. Do you have that function in your script? If yes, then i have no idea what the problem could be since "Can’t find variable: getFixedDate" exactly states that it can't find getFixedDate ...

Also i am not sure how this script behaves, if the contacts are in/from outlook. The contacts should be available in the iphone app "Contacts". If i remember right, then all contact container are checked. So as long as your contacts are also in the ios Contacts app, it should work using ;) showAllContacts = true

Were you able to fix your problem and get it running ?

Hey, sorry missed to give you an update. It was a layer 8 issue. I just missed a couple rows at the end of the script. This happend because of copy paste on iPad didn't catch the whole script. Sorry


Display issue.

Hi,
When launching Runelite I get such weird display issue. Please find attached screenshot. I am running Archlinux with OpenJDK 10. Other OSRS clients are working fine such as Konduit, therefore I think that this issue is not related to my hardware / setup.
Launcher logs: launcher.log
Applicaiton logs: application.log

https://github.com/runelite/runelite/wiki/Disable-Hardware-Acceleration

@TzZek Thanks, issue is now fixed. Any ideas why this is happening? Is there something from my side that I can do to run Runelite with HardwareAcceleration?

Yeah, most likely update/install graphics drivers.

@Puz3 What fixed this issue for you in the end?


What model is the LLM used in Figure 3？

hello, What model is the LLM used in Figure 3 of the paper to determine whether the conversation is safe, and does it require retraining or fine-tuning?

在当时使用的是InstructGPT，但放到今天来看这个选择显然不是最优了。


a error of webpage index

Uncaught TypeError: Cannot read property 'slice' of undefined
at HTMLButtonElement.$.on ((index):1777)
$('.modal-types button').on('click', () => {   //because of arrow function the this value is window
var type = $(this).attr('class').slice(5)
swal(type + '!', '', type)
})

Fixed, thanks a lot for reporting @zhangenming!


Recently Completed view is not loading

The recently completed view is not loading. (it hasn't been working for quite a while)
There are many requests in the background:

Sometimes so much, that ADO will limit the API access:

Looks like it could be connected to https://github.com/hanneswidrig/azure-devops-pull-request-center/issues/23
The other views (Active, Draft) work without any problems.
Console output
root/restoreSettings/fulfilled: completed successfully [store.ts:187:14](https://hannes-widrig.gallerycdn.vsassets.io/extensions/hannes-widrig/pull-request-center/2.2.3/1642443965956/build/static/js/state/store.ts)
root/getPullRequests/fulfilled: completed successfully [store.ts:106:14](https://hannes-widrig.gallerycdn.vsassets.io/extensions/hannes-widrig/pull-request-center/2.2.3/1642443965956/build/static/js/state/store.ts)

Hi!
Yes I can confirm, we are still having this issue.

What's the date range for PRs that you're requesting, is it all time?

Same here, view is not loading - I believe its running into some sort of loop

Maybe you can fix #26 as well 😉 That way we can update the extension and get the benefit of both in one go.

any updates on a PR since the last visit (bold title + blue line on the left side)

This one is definitely possible, and would be time-consuming.

any tags on the PR

If tags are easily available, this would be possible and hopefully not too much work.

@nhuethmayr The infinite loop should be fixed now. Please let me know if you're still experiencing issues.


Support Windows guests

Assemble the correct commands to boot Windows guests.

Possibly uses #11

UEFI support and framebuffer support has been added. This should be sufficient for Windows support.


Update Lavender.Five_Nodes.toml

Previous commit from this account https://github.com/anoma/namada-testnets/commit/e318e502673afd9e184691690f9beb9f4e02e243
Description
All previous genesis validators should name their PRs "Update {validator_alias}.toml for tesntet-15" and provide links to previous PRs merged.
If this is an UPDATE for a previous genesis validator
Checks are made against your net_address. If this has changed since the previous testnet, make sure you provide links of previous prs merged from your previous git username.
Thanks in advance!
Checklist before merging

[ ] Only one toml is added in this PR
[ ] The file being added is indeed a .toml file
[ ] The toml being added is to the correct folder, and only to the correct folder
[ ] The eth_hot_key and eth_cold_key are present
[ ] The email, discord, elements telegram, and twitter fields are present and valid

Successfully validated transactions.toml file for commit hash 1d33da9


Issue #11395 feat: Local Cache Implementation for framework

This Implementation is not required. So closing this pull request.


[WIP] Proposal for changing default behavior of workflow reports.

This PR is a proposal/strawman for starting a discussion on how to address #16, which has become a blocker in our workflows. It changes the default behavior of the DataFrame.report to generate a schema-only report, and introduces a new DOperation called DataFrameReport which provides the option to generate the original report format (along with the simplified report format).
While this proposal is likely unsatisfactory for all use cases, we wanted to submit it as a starting point for discussions on how a more comprehensive solution might be designed and implemented.

Thanks for the PR. I'll try to review next week. I would prefer that existing operations work as earlier and introduce new operation schema only report. Then we wouldn't have to migrate old workflows.

I understand that. Our problem with a "schema only report" is that when you do, Split or Join or Read DataFrame, or any of the other built-in operations, full statistics are always computed. If your data is too big for that to be tenable, you have not recourse other than to Create your own parallel set of operations that perform the same task but handle reports differently. Does this make sense?
I see two other options that aren't breaking.

Have a per-operation switch to turn off auto full report generation on a case-by-base basis.

Option 2 would be my preference. What is your thinking on this?

Withdrawn in favor of #72


CQN Minor Fix for TypeError

Minor fix to remove list access from np.randint & np.argmax in the getAction function (TypeError: Unable to iterate over the following elements: 0). Most likely unnoticed due to the documentation part of CQL not having a call to the getAction function as a test. My first pull request :D

Hey, congrats and thanks for the PR! Can you provide some more details on the issue? The list access is there because it was made with non-vectorised environments in mind, because with offline we don't train in the environment. Could you implement this in a way that works for both vectorised and non-vectorised envs?

Yeah, I see now why that is there, with the replay buffer using two separate functions to save memory. I'll see if I can implement this to adapt to both online and offline training. Also, I think there are also some extra changes that would also be beneficial so I will commit them as well to my branch for you to review later.

Upon reflection, it still makes sense to use vector envs, even with offline/only wanting to use one env.
Thanks a lot for all the improvements, nice work!


It has problem in showing some ranges

Hi, good work for this cool library but I found a problem in showing data on pins.
for Example if you set setTickStart=10,000 and setTickEnd=500,000 with setTickInterval=10,000 , range changes from 1000 to 5000 and think this part need some revisions.
with regards

@mahdit83 I just faced same issue for one of my project. So as I checked the library text is trimming from below code.
private PinTextFormatter mPinTextFormatter = new PinTextFormatter() {
	@Override
	public String getText(String value) {
		if (value.length() > 4) {
			return value.substring(0, 4);
		} else {
			return value;
		}
	}
};

So you can tackle this issue from below method.
mRangeBarPrice.setFormatter(new IRangeBarFormatter() {
	@Override
	public String format(String value) {
		int price = Integer.parseInt(value);

		Log.d(TAG, "price-in", value);
		Log.d(TAG, "price-out", String.valueOf((float) price/1000));

		return String.format("%sK", (float) price/1000);
	}
});

thanks @pasaneramusugoda

it makes the start from 0?

@pasaneramusugoda Your solution doesn't work with for example:
min: 100000, max:<PHONE_NUMBER>
It gives:
getPinValue - tickIndex: 999900032

The correct answer is: shubham192's solution


[$250] [HIGH] [API] OpenPaymentsPage is called whenever SettlementButton is rendered breaking 1:1:1

Coming from here
Problem
When user is expected to pay an expense report, in the Report preview or in the expense report header we render the SettlementButton. This calls OpenPaymentsPage  API in the useEffect to determine if user can use Wallet.
This breaks 1:1:1 though as we should return this information in the OpenReport call or somewhere else.
Solution
I believe the necessary data should be returned from the OpenApp. Let's remove this API call and see if there are any regressions in the payment flow
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0150686ef5eeacf118
Upwork Job ID:<PHONE_NUMBER>802320896
Last Price Increase: 2024-05-29

Issue OwnerCurrent Issue Owner: @fedirjh

Proposal
Please re-state the problem that we are trying to solve in this issue.
OpenPaymentsPage is called whenever SettlementButton is rendered breaking 1:1:1
What is the root cause of that problem?
we need to remove the OpenPaymentsPage as its now redundant because the data are already returned in theopenAPI request:

What changes do you think we should make in order to solve the problem?
Remove the followinguseEffect call
https://github.com/Expensify/App/blob/2a7d5d497ebec61171c7033ff85cdd0731d710c5/src/components/SettlementButton.tsx#L146-L148

@mountiny  I have verified whether removing the openWalletPage causes any regressions, and as you suggested, the OpenAPI already returns the same data. Therefore, this useEffect is indeed redundant.

Updated this comment

Proposal
Please re-state the problem that we are trying to solve in this issue.

OpenPaymentsPage is called whenever SettlementButton is rendered breaking 1:1:1
This also happens in WalletPage when we go online, it will also call OpenPaymentsPage along with OpenApp/ReconnectApp which breaks 1:1:1

What is the root cause of that problem?

The app's calling OpenPaymentsPage here whenever SettlementButton renders
The app's calling openWalletPage here whenever we go from offline to online in WalletPage

What changes do you think we should make in order to solve the problem?

1st, we need to make sure OpenApp returns all the data that's supposed to be returned via OpenPaymentsPage, the OpenApp is missing the fundList which should be added.
Then, both above OpenPaymentsPage calls are not necessary because all the data should've been returned in OpenApp.
So we can remove the useEffect here.
And also remove the useEffect here.
It looks like we can remove this useEffect too, although we don't really need to because it will not break 1:1:1, it's the only call made when going to wallet page.
We also need to ensure to send back payments page data update via Pusher whenever we add a card/add bank account, ... that can change payments page data. If this is not done, when the user updates the card/bank account in another device, it will not show up in the main device which is a regression, because right now if we do that, when rendering SettlementButton, it will always call OpenPaymentsPage that will get the latest payment page data.
What alternative solutions did you explore? (Optional)
NA

I think we should keep the API call in the WalletPage so we can get up to date data just in case. This does not break 1:1:1
@abzokhattab Thank you, your analysis is looking the most helpful, can you confirm that we use the fundList somewhere down the line from SettlementButton so we need to fetch it there? Is it needed there? I think it might be mainly needed on the wallet page

@Nodebrute I am not sure if there are some available cards for testing, this might be internal in staging. Asking around

I will go ahead with @abzokhattab. Their comments were the most helpful, and the solution here is the same for all proposals: remove the API call from SettlementButton.
I will work on adding the fundList to the OpenApp and then this should be ready to implement in App

I think we should keep the API call in the WalletPage so we can get up to date data just in case. This does not break 1:1:1

@mountiny When coming online, the wallet page will call both ReconnectApp and also OpenPaymentsPage. I think that will break 1:1:1 right?

@truph01 how is this handled on other pages that have a similar read as OpenPaymentsPage? This feels like its ok for the ReconnectApp case unless we have some solution already in place for other cases

Just the BZ checklist to go?

Payment Summary:

Contributor: @abzokhattab $250 paid via upwork
Reviewer: @fedirjh

@fedirjh can you accept the offer for this one and complete the checklist? Thanks!

$250 approved for @fedirjh

All set here.


pcatools error

this error follows below：
Enter one or more numbers, or an empty line to skip updates:
── R CMD build ──────────────────────────────────────────────────────────────────────────────────────────
✔  checking for file 'C:\Users\Administrator\AppData\Local\Temp\Rtmpo5M9OS\remotes46cc71e138f0\kevinblighe-PCAtools-50f240b/DESCRIPTION' ...
─  preparing 'PCAtools':
✔  checking DESCRIPTION meta-information ...
─  cleaning src
─  checking for LF line-endings in source and make files and shell scripts
─  checking for empty or unneeded directories
─  building 'PCAtools_2.5.15.tar.gz'

installing source package 'PCAtools' ...
** using staged installation
** libs
using C++ compiler: 'G__~1.EXE (GCC) 12.2.0'
using C++17
g++  -std=gnu++17 -I"C:/PROGRA~1/R/R-43~1.1/include" -DNDEBUG  -I'C:/Program Files/R/R-4.3.1/library/Rcpp/include' -I'C:/Program Files/R/R-4.3.1/library/beachmat/include' -I'C:/Program Files/R/R-4.3.1/library/BH/include' -I'C:/Program Files/R/R-4.3.1/library/dqrng/include'   -I"C:/RBuildTools/4.3/x86_64-w64-mingw32.static.posix/include"     -O2 -Wall  -mfpmath=sse -msse2 -mstackrealign  -c RcppExports.cpp -o RcppExports.o
g++  -std=gnu++17 -I"C:/PROGRA~1/R/R-43~1.1/include" -DNDEBUG  -I'C:/Program Files/R/R-4.3.1/library/Rcpp/include' -I'C:/Program Files/R/R-4.3.1/library/beachmat/include' -I'C:/Program Files/R/R-4.3.1/library/BH/include' -I'C:/Program Files/R/R-4.3.1/library/dqrng/include'   -I"C:/RBuildTools/4.3/x86_64-w64-mingw32.static.posix/include"     -O2 -Wall  -mfpmath=sse -msse2 -mstackrealign  -c shuffle_matrix.cpp -o shuffle_matrix.o
shuffle_matrix.cpp:1:10: fatal error: Rtatami.h: No such file or directory
1 | #include "Rtatami.h"
|          ^~~~~~~~~~~
compilation terminated.
make: *** [C:/PROGRA~1/R/R-43~1.1/etc/x64/Makeconf:272: shuffle_matrix.o] Error 1
ERROR: compilation failed for package 'PCAtools'
removing 'C:/Program Files/R/R-4.3.1/library/PCAtools'

It seems there are some issue when compile PCAtools packages，You may first install Rtools43. Then try to install PCAtools again.
If it is still not work, you can install PCAtools via Bioconductor:
## use westlake Bioc mirror souce
options(BioC_mirror="https://mirrors.westlake.edu.cn/bioconductor")
## install PCAtools
if (!require("BiocManager", quietly = TRUE))
    install.packages("BiocManager")

BiocManager::install("PCAtools")

ok，thanks


Gradle Tooling API with Gradle Daemon contains memory leak

On our huge multi-module Gradle project, the 2nd run of IntelliJ's "Refresh all Gradle projects" runs always OOM.
Expected Behavior
The 2nd refresh of Intellij's "Refresh all Gradle projects" will be faster as the Gradle Daemon is already running and some of the data is already cached in the memory.
Current Behavior
2nd refresh of all Gradle projects is much slower (48s vs. 6m) and eventually gets OOM. The GC is spending ~12% of CPU time.
From the jvisualvm view it is obvious that there is memory leakage:
1st run executes in ~48s, GC activity max ~ 1% of CPU, consumed memory ~500MB.
2nd run dies after ~ 6M, GC activity ~ 12% of CPU, consumed memory ~800MB.
Context
This is not allowing us to refresh the IntelliJ's Gradle project for the 2nd time and Gradle daemon always has to be stopped.
Steps to Reproduce (for bugs)
IntelliJ version: 2018.3.2
Gradle version: 4.5-20180102235856+0000
Gradle JVM: 1.8.0_144 (Oracle Corporation 25.144-b01)
See attached
Your Environment

Build scan URL:

The problem is in the JET plugin, which uses instance-level metaclasses. These are held in memory by Groovy even after the instance is no longer used. They are only released after several minutes (soft references). This is a bug in Groovy of course, but I'm pointing out the JET plugin, because plugins shouldn't use metaclass magic at all. They should use plain old Java objects and Gradle's Extension mechanism, so that the DSL also works in Kotlin.


Cannot run cargo tarpaulin --doc without rustup

Describe the bug
When attempting to run cargo tarpaulin --doc without rustup installed, it fails because it passes +nightly to cargo.
To Reproduce
# install a nightly rust toolchain without rustup, e.g. through `nix`
> cargo tarpaulin --doc
Feb 08 17:23:14.191  INFO cargo_tarpaulin::config: Creating config
Feb 08 17:23:14.259  INFO cargo_tarpaulin: Running Tarpaulin
Feb 08 17:23:14.259  INFO cargo_tarpaulin: Building project
Feb 08 17:23:14.259  INFO cargo_tarpaulin::cargo: Cleaning project
error: no such command: `+nightly`

        Cargo does not handle `+toolchain` directives.
        Did you mean to invoke `cargo` through `rustup` instead?
Feb 08 17:23:14.410 ERROR cargo_tarpaulin::cargo: Building doctests failed
Feb 08 17:23:14.410 ERROR cargo_tarpaulin: Cargo failed to run! Error: Building doctest failed
Error: "Cargo failed to run! Error: Building doctest failed"

Expected behavior
It to work, since I'm already using a nightly toolchain.

It's been a while since an assumption has come back to bite me like this! I've pushed a potential fix to the branch issue/1472 if you have some time to test it let me know (I'll also open a PR for it right now)

Yep, that works (at least, it starts the build and hits some ICE caused by -Zbuild-std that I'm still diagnosing).

Cool I'll merge it in then, I'll also try and see if there's any other fixes I can fit in quickly and cut a release today or tomorrow


Fixes A&A Sorting.

@DanielJMaher @FBRTMaka @birdage Please review

Hold merging this please

Okay, ready if you guys are.

:+1:


Align hashes code interface to user guide

The user guide says to do benchit script.py::hash1,hash2 to filter for hashes. The code has you do benchit script.py:hash1,hash2. Fix the code.

Wait until #50


Invalid argument passed to canTransform argument source_frame in tf2 frame_ids cannot be empty

Can you provide additional information? What happened? What were you trying to do?

The long corridor problem makes it really difficult to get the correct pose without using odometry ,  slam think the robot is not moving when laser scan datas are almost the same at long corridor, thus i think using odometry might sloves the problem.  However, I have met the same issue when i set
tracking_frame = "base_link",
published_frame = "base_link",
odom_frame = "odom",
provide_odom_frame = true,
use_odometry = false,

The sensor messages you are passing to Cartographer probably have an empty frame id, which is invalid.


Unable to load json2typescript into Lit-Element based project.

Hi,
I installed json2typescript via npm and want to use it in my typescript of my page as described in the docs:
import { JsonConvert, OperationMode, ValueCheckingMode } from "json2typescript"
it compiles and looks good until I want to run the page in the browser. I get this error then:
Uncaught SyntaxError: The requested module '../node_modules/json2typescript/index.js' does not provide an export named 'JsonConvert'
Is this due to the fact this is supposed to run with angular so that json2typescript exports its API somehow different than usual node modules?
I tried to change the index.js to export its interface as other modules do but without success. Any ideas what this could be?

I downloaded the repository and put it into my project. It workes now, My target is set to esnext which compiles it to the import clauses other modules work with. Sorry for the confusion.


SandboxGeneral Blog 6.4 KB for consideration to the club

https://www.sandboxgeneral.xyz
https://gtmetrix.com/reports/sandboxgeneral.xyz/ovFnIp7Z/
6.4 KB

Done

Done


An errant pixel lights up on selected toolbar icons (XUbuntu 20.04)

I am on XUbuntu 20.04, Lagrange 1.6.5 locally compiled.
When mousing over the top toolbar over any icon (back-arrow, outline of a personl, home, etc (but not the URL bar), an errant pixel lights up, same color as the frame surrounding the icon.  The pixel is located upper-leftish.

Could you attach a screenshot, please?
The frames are drawn as lines, and I have noticed various minor line drawing glitches on older versions of SDL. Ubuntu 20.04 has SDL 2.0.8 IIRC.
Due to lines being unreliable, I'll likely switch to some other method of drawing them in the future.

I've been trying to figure out how to take a screenshot, as the tool needs to be selected which deselects the screen grabbing app, even with a screen-grab-delay set...

OK, here it is.

Also, note the noisy background!  I was planning to report this separately, but could not catch it as it is intermittent.

Thanks! I do recall seeing this "corner dot" issue before, but not with recent SDL versions.
The random noise has been reported before, and appears to be some glitch in the hardware accelerated SDL textures. In #271 it was noted that forcing software rendering in Lagrange will make the issue disappear, but no real fix was found because I've been unable to reproduce the issue on my systems.
Using software rendering may help with the errant dots, as well.

I did not see an option to select software rendering in Lagrange settings - is it a compile-time option?
Here are my SDL library versions, in case it is useful:
$ dpkg -l | grep sdl
ii  libsdl-gfx1.2-5:amd64                    2.0.25-11                                  amd64        drawing and graphical effects extension for SDL
ii  libsdl-gfx1.2-dev:amd64                  2.0.25-11                                  amd64        development files for SDL_gfx
ii  libsdl-image1.2:amd64                    1.2.12-12                                  amd64        Image loading library for Simple DirectMedia Layer 1.2, libraries
ii  libsdl-mixer1.2:amd64                    1.2.12-16build1                            amd64        Mixer library for Simple DirectMedia Layer 1.2, libraries
ii  libsdl-mixer1.2-dev:amd64                1.2.12-16build1                            amd64        Mixer library for Simple DirectMedia Layer 1.2, development files
ii  libsdl1.2-dev                            1.2.15+dfsg2-5                             amd64        Simple DirectMedia Layer development files
ii  libsdl1.2debian:amd64                    1.2.15+dfsg2-5                             amd64        Simple DirectMedia Layer
ii  libsdl2-2.0-0:amd64                      2.0.10+dfsg1-3                             amd64        Simple DirectMedia Layer
ii  libsdl2-dev:amd64                        2.0.10+dfsg1-3                             amd64        Simple DirectMedia Layer development files
ii  libsdl2-image-2.0-0:amd64                2.0.5+dfsg1-2                              amd64        Image loading library for Simple DirectMedia Layer 2, libraries
ii  libsdl2-image-dev:amd64                  2.0.5+dfsg1-2                              amd64        Image loading library for Simple DirectMedia Layer 2, development files
ii  libsdl2-mixer-2.0-0:amd64                2.0.4+dfsg1-2build1                        amd64        Mixer library for Simple DirectMedia Layer 2, libraries

Let me know if I can help in some other way

Try launching the app with the --sw command line option, no recompilation needed.

--sw seems to eliminate the dot, and probably the noise (although the noise was hard to catch...)

I'm closing this because I don't believe there is much to be done here. The underlying issue is most likely caused by a bug in an obsolete version of SDL.

I had the same issue on Ubuntu 20.04 locally compiled, including the glitchy background on the URL bar. The --sw workaround did the trick. Thank you!

I still see glitches (weird pieces of bitmaps) in the background of the URL bar...  LaGrange 1.10.2, on xubuntu 20.04.3 LTS

@stacksmith You mean like #271 ?

I think so... I am so used to it I hardly notice it - it is only on the URL bar.

As far as I can tell, that glitch is either a bug in the version of SDL in Ubuntu 20.04, or some video driver issue. There are no reports of it with newer SDL releases.


Total Watchtime

It would be good if you add an option to extract WatchTime of any video through plyr. It should show exactly correct watchtime (it means it should exclude all skipped part, rewind, forward parts).
For example: if a video is having length of 1:00
And i start playing from 0:00 to 00:10 and then i pause and forward to 00:20 to 1:00 then watchtime should be 50 seconds
I am trying to integrate on my side, by adding some JS between different events, still it would be good if there is a feature something like this in future.

I managed to achieve this, just get total video duration and under timeupdate event you can calculate watch time using current video length and total video length

can you share your code with us. i dont find timeupdate event.


Workload identity

Task name:
Description:
Documentation changes required: (Y/N)
Added unit tests: (Y/N)
Attached related issue: (Y/N)
Checklist:

[ ] Task version was bumped - please check instruction how to do it
[ ] Checked that applied changes work as expected

Tagging @silviuandrica as there may be a better option to Auth soon

/azp run