Bugfix for #209 Diff powershell files will crash VS

Normally, opening a powershell file will create a TextBuffer with ContentType "PowerShell". However, when diffing a powershell, the TextBuffer ContentType is a combination of two TextBuffers, both of which have ContentType as "PowerShell". But the combination TextBuffer's ContentType is with name "projection". We don't put anything into this TextBuffer, meaning we can get nothing from it, neither. Then we don't, we create it one ourselves here.
@AndreSayreMSFT @EricMSFT @Microsoft/poshtools

Looks good!  Does the combination textBuffer support all of our expected editor operations?

Fixes adamdriscoll#209

We got all the colorization but not editing. The combination textBuffer doesn't support editing for some reason. Though we know you should be able to edit the local file. I suggest fixing the crashing bug first then opening an issue for editing in diff mode, thoughts? @AndreSayreMSFT

@HuanhuanSunMSFT Agreed!  Please open up another issue, as it's something we definitely need to be able to handle!


Jsx being rendered as a component

A button is being rendered in the chat upon entering jsx of a button.
Steps to reproduce:

Open a new chat window by pressing Ctrl + Shift + h
Enter the following code:

export default Button({text}) {
 return(
 <button>{text}</button>
 );
}

Screenshot:

OS: Windows
Browser: Chrome
Extension Version: Don't know :/

It is generally recommended to wrap your submitted code in a code block.

I'll make sure to do that in the future. I raised this issue because I thought it might be a security risk. Thanks for letting me know.


Release 1.1.0

Coverage increased (+3.0%) to 71.3% when pulling f72b5cb5af59df21e117646e5cf804415c630cbe on release/1.1.0 into 510c0d534946d2d0f0efd09f4d3ee4083731baa3 on master.

Coverage increased (+3.0%) to 71.3% when pulling 643146dd445c3cc35f29efd4429cac206031ce99 on release/1.1.0 into 510c0d534946d2d0f0efd09f4d3ee4083731baa3 on master.

Coverage increased (+3.0%) to 71.3% when pulling 643146dd445c3cc35f29efd4429cac206031ce99 on release/1.1.0 into 510c0d534946d2d0f0efd09f4d3ee4083731baa3 on master.

Coverage increased (+3.0%) to 71.3% when pulling 3d8b09052fedd42ec9b39d2ba7d3284960d7baf9 on release/1.1.0 into 510c0d534946d2d0f0efd09f4d3ee4083731baa3 on master.

Coverage increased (+3.0%) to 71.3% when pulling 1c97ff9d9e97a8b3ab54de2d58d61ac28d1b7213 on release/1.1.0 into 510c0d534946d2d0f0efd09f4d3ee4083731baa3 on master.

Coverage increased (+3.0%) to 71.3% when pulling 6b2a2084202093257d0740422b95832687ad9b94 on release/1.1.0 into 510c0d534946d2d0f0efd09f4d3ee4083731baa3 on master.

Coverage increased (+3.0%) to 71.3% when pulling bf1130cd46eb5d740e2431c30107eae2e8c74e1e on release/1.1.0 into 510c0d534946d2d0f0efd09f4d3ee4083731baa3 on master.

Coverage increased (+3.0%) to 71.3% when pulling 6dab849bc53c2e5c5a8ad05790927eb6521a89d5 on release/1.1.0 into 510c0d534946d2d0f0efd09f4d3ee4083731baa3 on master.

Coverage increased (+3.0%) to 71.3% when pulling 67509c61a56fe7e7a970ca50a6144295be7d3dd0 on release/1.1.0 into 510c0d534946d2d0f0efd09f4d3ee4083731baa3 on master.

Coverage increased (+3.0%) to 71.3% when pulling 5e6468e9ee7b7b0519e53faa0bf41f2ad761bc26 on release/1.1.0 into 510c0d534946d2d0f0efd09f4d3ee4083731baa3 on master.

Coverage increased (+3.0%) to 71.3% when pulling ec1d58cf9cc15433340ae828b30e9288099cc31f on release/1.1.0 into 510c0d534946d2d0f0efd09f4d3ee4083731baa3 on master.

Coverage increased (+3.0%) to 71.3% when pulling 3bbc705e98869a54dc23da89966e644fe9d646f0 on release/1.1.0 into 510c0d534946d2d0f0efd09f4d3ee4083731baa3 on master.

Coverage increased (+3.0%) to 71.3% when pulling d7ebb982889e39bd89ba4f055fa7437a5e22ae00 on release/1.1.0 into 510c0d534946d2d0f0efd09f4d3ee4083731baa3 on master.

Coverage increased (+3.0%) to 71.3% when pulling 3cbe955485503ac595d087d2a5c11646c36f699d on release/1.1.0 into 510c0d534946d2d0f0efd09f4d3ee4083731baa3 on master.

Coverage increased (+3.0%) to 71.3% when pulling 4baecff71bb7bafef194be3d769a9fd9f261ee0c on release/1.1.0 into 510c0d534946d2d0f0efd09f4d3ee4083731baa3 on master.

Coverage increased (+3.0%) to 71.3% when pulling f303a51573e0d3207391361c99c57343bafb3fef on release/1.1.0 into 510c0d534946d2d0f0efd09f4d3ee4083731baa3 on master.

Coverage increased (+3.0%) to 71.3% when pulling 0d086dc35f4072c23cafabd502ccd1d92093e968 on release/1.1.0 into 510c0d534946d2d0f0efd09f4d3ee4083731baa3 on master.

Coverage increased (+3.0%) to 71.3% when pulling 4b71a992bd91dce05e7dacddd3e189c7d3d85177 on release/1.1.0 into 510c0d534946d2d0f0efd09f4d3ee4083731baa3 on master.

Coverage increased (+2.9%) to 71.245% when pulling 9b71da273bb6993ea1a267eaacbc44959642aabe on release/1.1.0 into 510c0d534946d2d0f0efd09f4d3ee4083731baa3 on master.

Coverage increased (+2.9%) to 71.193% when pulling 9dfe48af3241d309c2c362f0d63b1c2cdd5c62ab on release/1.1.0 into 510c0d534946d2d0f0efd09f4d3ee4083731baa3 on master.

Coverage increased (+2.8%) to 71.074% when pulling 9fdc218b7506b82eaed97c56bec72a85717b9a63 on release/1.1.0 into 510c0d534946d2d0f0efd09f4d3ee4083731baa3 on master.

Coverage increased (+2.6%) to 70.954% when pulling 0d0bba8ccbf275c084f093f81b24684b13bcb0ec on release/1.1.0 into 510c0d534946d2d0f0efd09f4d3ee4083731baa3 on master.

Coverage increased (+1.6%) to 69.963% when pulling 144426df0ee0f4d6bea1cd42e94c3f690905595d on release/1.1.0 into 510c0d534946d2d0f0efd09f4d3ee4083731baa3 on master.

Coverage increased (+0.8%) to 69.079% when pulling 712ab87fbbdfd97cda2a7f4de685c747aafa5b3e on release/1.1.0 into 510c0d534946d2d0f0efd09f4d3ee4083731baa3 on master.

Coverage increased (+0.8%) to 69.079% when pulling 1ba09ee53cbff6051d362a9ace336b7cc68964dd on release/1.1.0 into 510c0d534946d2d0f0efd09f4d3ee4083731baa3 on master.

Coverage increased (+2.5%) to 72.982% when pulling d08a01b4e01cf1f8f9efdd184d5e9fd9d1951fa5 on release/1.1.0 into 1c25d77dc915478b746cdf2fa1039fd35fb2d12e on master.

Coverage increased (+7.7%) to 78.201% when pulling 5314f0b5139f4f6b4b5875ae3876ce70fc3f7547 on release/1.1.0 into 1c25d77dc915478b746cdf2fa1039fd35fb2d12e on master.

Coverage increased (+5.7%) to 76.174% when pulling 905a4dbb78366536d9d4a05deac2ecd6eedb7be8 on release/1.1.0 into 1c25d77dc915478b746cdf2fa1039fd35fb2d12e on master.

Coverage increased (+5.7%) to 76.174% when pulling f6b42fc05f5305f2e8b19708791959beae20518c on release/1.1.0 into 1c25d77dc915478b746cdf2fa1039fd35fb2d12e on master.

Coverage increased (+5.7%) to 76.174% when pulling 53c094df8fc8d325c42b44567dee0cac3ea32700 on release/1.1.0 into 1c25d77dc915478b746cdf2fa1039fd35fb2d12e on master.

Coverage increased (+5.7%) to 76.174% when pulling 6a30ce367f5e716b3fba16698b6a75d03f5b31e1 on release/1.1.0 into 1c25d77dc915478b746cdf2fa1039fd35fb2d12e on master.

Coverage increased (+5.7%) to 76.174% when pulling 708457f6ccdafa831551fa739b8eb9cae7a1b66a on release/1.1.0 into 1c25d77dc915478b746cdf2fa1039fd35fb2d12e on master.

Coverage increased (+5.7%) to 76.174% when pulling a8232ea92f53b9b4b095d43cba341df111c0d900 on release/1.1.0 into 1c25d77dc915478b746cdf2fa1039fd35fb2d12e on master.

Coverage increased (+5.7%) to 76.174% when pulling d566c847064cb20f0b8e7acd0c23865bdd58eb0d on release/1.1.0 into 1c25d77dc915478b746cdf2fa1039fd35fb2d12e on master.

Coverage increased (+5.7%) to 76.174% when pulling 7d31a6f34819e8082e6fe83a1c61a1a98dcbae87 on release/1.1.0 into 1c25d77dc915478b746cdf2fa1039fd35fb2d12e on master.

Coverage increased (+5.7%) to 76.174% when pulling 7d31a6f34819e8082e6fe83a1c61a1a98dcbae87 on release/1.1.0 into 1c25d77dc915478b746cdf2fa1039fd35fb2d12e on master.

Coverage increased (+5.7%) to 76.174% when pulling 8d68e7b28f2ddf6ac5b1c8f4d49d7c5fd083033b on release/1.1.0 into 1c25d77dc915478b746cdf2fa1039fd35fb2d12e on master.

Coverage increased (+5.7%) to 76.174% when pulling 67e20211c3b0a6d07d379de5947395fe7d6c5c9f on release/1.1.0 into 1c25d77dc915478b746cdf2fa1039fd35fb2d12e on master.

Coverage increased (+5.7%) to 76.174% when pulling 05936abd349b10b24c46f65c384d9b22d2b2380c on release/1.1.0 into 1c25d77dc915478b746cdf2fa1039fd35fb2d12e on master.

Coverage increased (+5.7%) to 76.174% when pulling fd0caa07debfbc42e14d554fd489c189ba8c0e26 on release/1.1.0 into 1c25d77dc915478b746cdf2fa1039fd35fb2d12e on master.

Coverage increased (+5.7%) to 76.174% when pulling 73055f5344ba0ebba841e6d6742f25c0780acd9d on release/1.1.0 into 1c25d77dc915478b746cdf2fa1039fd35fb2d12e on master.

Coverage increased (+5.7%) to 76.174% when pulling ef6444f1aee09d167f28c5da4e3a21e9501bf277 on release/1.1.0 into 1c25d77dc915478b746cdf2fa1039fd35fb2d12e on master.

Coverage increased (+5.7%) to 76.174% when pulling a0a39b7128b78beabc2754a2eaf905c005e63a83 on release/1.1.0 into 1c25d77dc915478b746cdf2fa1039fd35fb2d12e on master.


Fix issue-2294

This PR fixes issue #2294.
TODO

[x] @mewim should remove marked API from all language bindings.

I have removed the deprecated functions from C, Java, Node.js, and Python bindings. I do not know Rust, so @benjaminwinger should take over and remove the APIs from Rust as well.


responsive component inside of responsive component doesn't work

I have the case that I built a component which needs to be resizable on its own, but must use another component which is also resizable:
let InnerResizable = componentQueries(queryInner)(InnerDumb)

let OuterResizableDumb = ({fromQuery, otherProp}) => {
  return

            {fromQuery &&
            only visible when size fits}
            <InnerResizable>see my prop {otherProp}</InnerResizable>

}

let OuterResizable = componentQueries(queryOuter)(OuterResizableDumb)

On first render both components call their queries and resize right. On browser window resize the only component which updates (and calls their query) is the inner one. The outer one doesn't call their query and because of that it never changes its query result and isn't responsive.
By the time I developed the outer component, the inner one was not resizable. That way I know the outer version works fine without the inner one. As soon as I made the inner one also responsive the outer one stopped working.
For react-sizeme and react-component-queries I'm on the latest version. element-resize-detector is version 1.1.12 as dependency from another third party component. React is version 15.4.2.

Woah, very strange case!
Would you mind putting together an example via http://codesandbox.io/ and then I would be happy to review it for you.

@ctrlplusb here is the example https://codesandbox.io/s/NkP3qy3rL
Sometimes the query of Outer calculates a new value one time after the resizing the window, sometimes it just works on first render as I described in my first post. Nevertheless it doesn't work beyond one change after the initial render. In index.js you can replace the import of Outer to get a "working" version. As a workaround I added a div around Inner.
For the record:
My first example looked more than the version above https://codesandbox.io/s/Bp4D74gx
which has more nodes in Outer to add some text to show which is the outer and which the inner component. It took me a good amount of the day to check that is really just the issue that the inner container gets returned without any wrapping element. In my real app Outer transforms some data into children for Inner so I can't combine Outer and Inner into one component.

Super helpful sandbox @hoschi! Thanks for putting this together.
I haven't looked into it yet, but my initial guess may be that the pure behaviour is causing an issue here.  I'll need to investigate further.


Polygon mainnet not connecting for Synpress with Playwright on Chrome

Describe the bug
I am using  Synpress with Playwright in isolated state on Chrome as mentined in Example  https://github.com/drptbl/synpress-examples/tree/master/playwright/isolated-state. I am able to connect with Ethereum mainnet but not able to connect to Polygon mainnet.
However able to connect to Polygon mainent manually on Metamask Wallet chrome extension.
To Reproduce
Steps to reproduce the behavior:

Use  Synpress with Playwright to run on Chrome
In fixtures.ts  pass network as polygon in initialSetup() method
Polygon mainnet gets added, but while changing network, it goes in forever spinning state

Related repository
Expected behavior
Polygon mainnet should be connected
Screenshots

Desktop (please complete the following information):

OS: macOS
Browser: chrome
Synpress version: 3.5.1

Additional context
fixtures.ts file :
import { test as base, chromium, type BrowserContext } from "@playwright/test";
import { initialSetup } from "@synthetixio/synpress/commands/metamask";
import { prepareMetamask } from "@synthetixio/synpress/helpers";
export const test = base.extend<{
context: BrowserContext;
}>({
context: async ({}, use) => {
// required for synpress
global.expect = expect;

// download metamask
const metamaskPath = await prepareMetamask(
  process.env.METAMASK_VERSION || "10.25.0"
);

// prepare browser args
const browserArgs = [
  `--disable-extensions-except=${metamaskPath}`,
  `--load-extension=${metamaskPath}`,
  "--remote-debugging-port=9222",
];
if (process.env.CI) {
  browserArgs.push("--disable-gpu");
}
if (process.env.HEADLESS_MODE) {
  browserArgs.push("--headless=new");
}

// launch browser
const context = await chromium.launchPersistentContext("", {
  headless: false,
  args: browserArgs,
});

// wait for metamask
await context.pages()[0].waitForTimeout(3000);

// setup metamask
await initialSetup(chromium, {
  secretWordsOrPrivateKey:
    "aim friend vast bird glimpse body mountain tide solar badge office nut",
  network: "polygon",
  password: "mymetamaskwallet1",
  enableAdvancedSettings: true,
});

await use(context);
await context.close();

},
});
export const expect = test.expect;

Just a note: I've seen such behavior some weeks ago inside ordinary Metamask, without Synpress, haven't figured what was that; later it was gone by itself.

So after more debugging i realised, that Polygon is now available under Popular Custom Networks, So it doesn't allow adding Manually. And adding from Popular Custom Networks is not handled in initialSetup() method.
I was able to handle and test this successfully on my local. Will raise a PR for same.

@prem-kumar-fox could you clarify what does "doesn't allow adding Manually" mean?
For me, this seems to work with Polygon Mainnet:
## .env
# the name is presumably just for human interaction; the ID and URL matter
NETWORK_NAME='Polygon Mainnet'
CHAIN_ID=137
RPC_URL='https://polygon-rpc.com'
SYMBOL="MATIC"

And this seems to work with Polygon Mumbai testnet:
## .env
# the name is presumably just for human interaction; the ID and URL matter
NETWORK_NAME='Mumbai'
CHAIN_ID=80001
RPC_URL='https://matic-mumbai.chainstacklabs.com'
SYMBOL="MATIC"

(I'm applying this config by using env-cmd cypress run --browser chrome --headed; my Synpress version is 3.7.1 though; I'm currently running tests locally)
Do you mean that while configuring with env variables works, setting these params via initialSetup fails?

PS Also, you should check 3.7.1 anyway, as it has a fix for custom networks:

problem: https://github.com/Synthetixio/synpress/issues/764#issuecomment-1569644206
fix delcaration: https://github.com/Synthetixio/synpress/issues/764#issuecomment-1579383770

Thanks @YakovL , Its working with 3.7.1. Closing the issue.


Add side menu

Add a button in the app bar which opens a menu with the items from the design: https://www.figma.com/file/0qkRp3TrKBRnpEnmQeA5m4/Covid-Watch---App-v1.6?node-id=36%3A394
It's OK for the items to not work for now.
This should happen in MainActivity so the menu is present on every screen. Use navigation drawer from Material Design. In our design the menu is on the right but in Material Design it's on the left so it's OK to be there until we discuss it with the designer.

@imshentastic I think your work may be duplicated by what @madim has done. Can you please check his PR: https://github.com/covid19risk/covidwatch-android/pull/65

done in https://github.com/covid19risk/covidwatch-android/pull/65


Daemonising on debian?

I'm new to ruby (huginn is my first reason to even have it installed on my system) and am unfamiliar with how to run huginn in the background.
Unfortunately the only mention I found in the wiki involved upstart, and that seamed like an unnecessarily complicated way to get huginn running in the background.

Hey @dugite-code, welcome!
Are you going to run this on a remote computer (like a VPS), or locally?

Locally, on my home server currently installed in a virtual Debian environment witch I setup and control with webvirtmgr.

foreman can export for inittab and systemd too.  Also, @dsander has a guide underway: https://github.com/cantino/huginn/pull/872

Thank you for the help

Unfortunately the export to systemd in foreman doesn't appear to work straight off the bat and I haven't found a way to make it work or any guides that don't focus on upstart.
I looked at the installation guide linked but installing upstart stopped my system booting up altogether so I had to reload from a snapshot.

If it's easy, you might consider using Docker.  There's also #872.

hummm... I'm still not seeing anything other than using upstart in #872 and for some reason that frags my system.
In any case I guess I'll have to try to get docker working again

@dugite-code I also tried to use systemd on debian for #872 with no luck, the export worked but the services did not start. Which debian version are you using? I tested the upstart installation with debian 6 and 7 images on vagrant and digital ocean and had no problems.

I'm using 7 wheezy. It's an install with a whole bunch of tinkering done so I'm not surprised something broke badly. Defiantly looks like docker is the best way to go for me


add "unbone ghost" option

Related to Dunk's request to remove ghosts from NT, however instead of removing them entirely, it instead replaces them with the polymorph version of the player ghost which uses a random wand (Tier 3 wand, if I understood the code correctly). Also affects the Kivi player ghosts.
The way it's coded is a little jank, since I check if an entity was actually generated and then replace it rather than doing the check myself, but since the source code for spawning apparitions isn't in Lua I didn't want to make my life harder than it needed to be (assuming this approach doesn't have other issues I'm not aware of)
I can change it to remove them entirely if that's preferred, since that change would be even simpler, I just figured it would be a shame to remove them entirely.

@Lasiace not sure what went wrong here as I cannot find a crash dump or logs, but it crashed on me when it spawned the player ghosts when unbone was on :(

Might be related to a recent update, I haven't run this since I made the PR. I'll look into it.


Fbx to GLB import drops UV1 channel

see more on the forum: https://forum.playcanvas.com/t/glb-drops-uv1-from-3ds-max-fbx-export/15415

I also made a ticket in Editor repo previously. I think it is the same issue:
https://github.com/playcanvas/editor/issues/220#issue-742755253

duplicate of https://github.com/playcanvas/editor/issues/220


fix SLES repo URL for logstash >= 1.5

Minimal fix for the SLES repository. The "centos5" repository doesn't seem to exist for logstash>=1.5, but "centos" works. For logstash <=1.4 "centos5" is still used.

Jenkins standing by to test this. If you aren't a maintainer, you can ignore this comment. Someone with commit access, please review this and clear it for Jenkins to run; then  say 'jenkins, test it'.

Can one of the admins verify this patch?

It seems Logstash itself does not support installing from RPM packages on SLES, only from tar archives.
Given that, I think forcing this module to try doing it could put people in a bad situation.


refactor(protocol-designer): ot-2 slot map is now a normal size

closes RAUT-1005
Overview
See the ticket. no idea when this error was introduced - apparently after i did the migration to react-hook-form?? Weird. But anyway, I fixed it here and also cleaned up the SlotMap components, getting rid of the no longer needed ConnectSlotMap
Bonus: also there was a small bug with the well selection field where it was defaulting the value to 0 which is different from PD in prod. So i fixed that up really quick too.
Test Plan
Create an Ot-2 protocol and edit the modules. See that the slot map is no longer way too big.
Changelog

clean up the SlotMap component and associated components
fix test
fix bug with well selection field where it was defaulting the value to 0 if the length of well array was 0.

Review requests
see test plan
Risk assessment
low

Looks good! IMO, I wouldn't be opposed to naming SlotMap to something like OT2SlotMap or leaving a docstring explaining that this is an OT-2 specific component, since we have an analogous FlexSlotMap.

@mjhuff good call! thank you! SlotMap used to be used for both robot types so I forgot that I made a FlexSlotMap later. I'll rename it to OT2SlotMap


Docs: Add entry for CPX adapter in Meshery Docs

Current State:
The CPX adapter is not currently listed.
Desired State:
The CPX adapter should have an entry in the list of adapters and should now be a "beta" adapter.
See https://meshery.layer5.io/docs/installation/adapters

Contributor Resources

Meshery documentation site
Meshery documentation source
Instructions for contributing to documentation

The CPX adapter is already in the docs. I updated it with some new information but this issue can be closed.

Very good. Thank you, @schillingjerrid


Move isEqual under Collections in index.html

Since isEqual operates on arrays as well as on objects, it belongs under Collections. The language has been changed accordingly.

I agree with @megawac. This could maybe be a utilitys method, but it's much more an object (not necessarily Object) method.


New release

Hi,
We're experimenting with this at the moment, and noticed that the latest released version is someway behind HEAD. any chance you could create a new release?
Thanks.

Will do. If you're testing/experimenting you should definitely be using HEAD.


allow an .env file to be passed as an recipe parameter to change the dotenv-path setting

In my projects, I have .env files for different contexts, like dev, prod, local, etc. I'd like to be able to specify which .env file to use based on a named parameter to the specific recipe.
I'm working around this now by embedding a shell script and calling out to shdotenv in the middle of it, but it's hacky.
some_recipe env="dev.env":
	#!/usr/bin/env sh
	set -euo pipefail
	export $(shdotenv -e {{env}} env)
	... do something with an environment variable loaded from env

it would be neat if we could change the dotenv-path setting like passing an parameter. I don't know what the syntax would look like, maybe it would be...
some_recipe dotenv-path="dev.env":
	... do something with an environment variable loaded from env

I could always go, shdotenv -e dev.env just recipe, but that is awkward, too.

Why not using just -E dev.env recipe?

Wow. Thank you. I've looked at the documentation a ton (I've been writing justfiles for over a year) and I never saw that.
I think the documentation should mention that in the relevant place, https://just.systems/man/en/chapter_27.html#dotenv-settings. Maybe I'll write up a PR tomorrow.

Nice, glad that works for you. There are way too many options for .env handling, so I'm sure the docs could use some work. PRs welcome!


Redis inside docker

Is redis running inside docker? If not, can we have it and have it as default in docker setup for production?

Dockerfile is only for the web container. Each service (web, celery, database, cache) runs in an isolated container.

So, if I follow this documentation
https://docs.getsaleor.com/en/latest/deployment/docker.html
Does it mean that the container actually runs web,celery, database and cache and I can just use the ENV variables to tell it to use REDIS as cache?
Or how does it work?

These instructions assume that you have PostgreSQL, Redis etc. already running somewhere (which is often the case with AWS RDS, AWS ElastiCache and similar services). If you want to deploy everything then I suggest you use docker-compose instead.
I would welcome a change to the documentation to clarify that.

I'll be happy to contribute to the documentation, but I need to understand how this works first 😅
The documentation states that docker-compose is for development only, to what extent is that correct?
Also, how easily is it to maintain different docker containers that interact with each other, wouldn't be super easier to just bring everything under the same container?

The config we distribute (docker-compose.yml) is meant for local development as it uses python manage.py runserver to start Django. There is a pull request however that begins to change that.
If you remove the command: ... line from the web container you should be able to use the config to build a production environment. Make sure to edit the common.env file to disable DEBUG and make sure other variables are set to correct values (and use a safe SECRET_KEY).
As for running everything under one container it has several problems:

Docker is meant to oversee a single process in each container, you could add a supervisor process inside the container to orchestrate a number of other dependencies but if one of those experiences a failure, your Docker server will not know about it (from its point of view, your container is there to run the supervisor which probably still runs as a process)
The resulting image would have to be manually assembled and would need to be large to satisfy the the requirements of all the services running inside
It would be impossible to scale: you'd normally scale services by spawning more containers but spawning a second container would mean you would now have two (five, a hundred) separate database servers and two (five, a hundred) separate caches with no way to synchronize state between them


Capitalized first letter in each line of the list

Why:
Closes: https://github.com/github/docs/issues/35455
What's being changed:
Capitalized the first letter in each line of the list in doc page https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork  to maintain consistency with other docs. Screenshot below showcases the changes made:

Check off the following:

[x] A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require a SME review from GitHub staff.
[x] The changes in this PR meet the docs fundamentals that are required for all content.
[x] All CI checks are passing.

@VictorDoyle Thanks so much for opening a PR with this fix! I'll update the branch and get this merged once tests are passing 🍏


Fancy queries

Codecov Report

Merging #738 (3255aac) into master (af5198b) will increase coverage by 0.23%.
The diff coverage is 92.07%.

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

@@            Coverage Diff             @@
##           master     #738      +/-   ##
==========================================
+ Coverage   81.85%   82.09%   +0.23%
==========================================
  Files          86       89       +3
  Lines        3142     3217      +75
  Branches      462      472      +10
==========================================
+ Hits         2572     2641      +69
- Misses        483      486       +3
- Partials       87       90       +3

Impacted Files
Coverage Δ

CreeDictionary/CreeDictionary/urls.py
100.00% <ø> (ø)

CreeDictionary/CreeDictionary/views.py
92.18% <ø> (ø)

CreeDictionary/API/search/presentation.py
87.65% <60.00%> (-2.09%)
:arrow_down:

CreeDictionary/API/search/types.py
91.66% <83.33%> (-2.39%)
:arrow_down:

CreeDictionary/API/search/util.py
84.61% <84.61%> (ø)

CreeDictionary/API/search/query.py
96.29% <96.29%> (ø)

CreeDictionary/API/search/affix.py
96.77% <100.00%> (+0.05%)
:arrow_up:

CreeDictionary/API/search/core.py
86.84% <100.00%> (-2.75%)
:arrow_down:

CreeDictionary/API/search/lookup.py
85.00% <100.00%> (ø)

CreeDictionary/API/search/query_test.py
100.00% <100.00%> (ø)

... and 4 more

Continue to review full report at Codecov.

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


memcached does not handling all passed arguments, even invalid ones

Simple example.
Incorrect
Connected to <IP_ADDRESS>
`watch` fetchers afsfds dsf sdf s df sd
OK

Incorrect
Connected to <IP_ADDRESS>
`stats` items afsfds dsf sdf s df sd
OK

Correct
Connected to <IP_ADDRESS>
`stats` fetchersafsfds dsf sdf s df sd
ERROR

However, if you simply pass it as indicated in the documentation with |(OR) and *(AND), then everything works. Maybe validation was not intended? This is mistake?

The parser ignores data in some instances. Some commands have a fixed number of tokens and it will error if you give it the wrong count, but stats and some commands have no technical limit on the amount of tokens the user can supply. It will ignore ones it doesn't end up using.
watch should probably error with unknown tokens, though.

watch fetchers afsfds dsf sdf s df sd
ERROR

I have no idea what you did here but watch does validate the input tokens and will throw an error.


Clean frontend

This implements many ideas from #88, except for fiddling with the header.
One thing that I'm not sure about is that when there is only one piece of 'more information', like only a unifier, the 'more information' link could be removed and the unifier could be put instead (i.e., only put the link when there is more than one piece of information / when it is a list of instances or derivations). However, removing the more information link in some cases may work confusing.
Another option is to only hide instances and derivations behind the more link (but both behind one link would have my preference, so that you don't need to click twice).

It's a lot more compact which is good. However, the more information fields are not very informing. In the case of class instances it says so but for type constructors and/or class it belongs to it doesn't.
I'm fine with merging it to master for now and we'll have to think about a nice shorthand for the more information cases.

ps.
For class function such as other we can just don't print more information and just write the full text (which is always exactly one line anyways).

Yes, so let's not hide any extra information except the derivations and the instances (which are hidden behind one shared link). Merging the filename / module / library lines and removing the horizontal rules already gave a lot of space. I'll merge this now, because it allows me to create the next PR for the library browser, but wait with deploying until this is changed.


Revert "Add ASB operator deployment manifest assets."

Reverts openshift/ansible-service-broker#1151
With https://github.com/fusor/catbrokers4 I don't think these are needed as they are just duplicates and catbrokers should be our source of truth for now.

Coverage remained the same at 40.97% when pulling e1e2d0f5385ffc70e77edab0ffa3d92843a4ed4c on revert-1151-add-manifests-dir into b54997cce43d410f9b8a226a27f0893b7a770909 on master.


Change minimum PHP version to 7.2.

As per https://github.com/whikloj/BagItTools/issues/7

Resolved with 978810f11620c0eead22876e338f87bba77fcacc.


In a typescript file, cancelling IncRename results in an error

I'm pressing escape to try to abort renaming in a typescript file. All the same info as here: https://github.com/smjonas/inc-rename.nvim/issues/1 -- might be related.
Works as expected in lua files

Can you check if the latest commit fixes this issue as well?

it works! thanks!


Oculus CV1 IMU latency problem

On the Oculus Rift CV1, I have some heavy "input lag"-like latency issues with the IMU.
On OpenHMD master branch (3DOF CV1 support), I only see that while turning my head in the hmd, the whole thing turns late, and seems to be choppy.
On Thaytan's branches with 6DOF CV1 support I see the following message being spammed when I open one of the demos:
[WW] Exposure timestamp<PHONE_NUMBER> was more than 1.5 IMU samples earlier than IMU ts<PHONE_NUMBER> by 10228 µS
It seems like the difference increases until it reaches around 19000 µS then it jumps down and climbs up again.
Am I the only one experiencing this? It is not a performance issue as it happens with the simple example too (no 3d rendering), and the cpu can easily handle it (i5-12400f)

That kind of message ([WW] Exposure timestamp<PHONE_NUMBER> was more than 1.5 IMU samples earlier than IMU ts<PHONE_NUMBER> by 10228 µS) implies that OpenHMD didn't get scheduled in time and missed USB traffic. Make sure you're building in release mode (cd build; meson -Dbuildtype=release) to get compiler optimisations and see if that helps?
In general I don't see the lag or choppiness.
It seems like the difference increases until it reaches around 19000 µS then it jumps down and climbs up again.

I did build in release. but I noticed now that after unplugging the HMD from USB and plugging it back in, the latency got much better. It's been plugged in for a long time (probably months), since I don't really unplug it and on Windows it worked fine.

That's.. interesting. I can't think of any reason why that would happen. If it happens again it might be interesting to record a USB trace with wireshark

VDavid003, hello guys, I just signed up to find out if you guys did finally find a way to make the oculus rift works under linux again, was it a matter of waiting for the kernel to be fixed drivers from nvidia ? mesa again ?? I am still trying to make this wonderfull glasses to start working again under linux, ubuntu Centos Arc Linux. but I am kind of lost if I still need to go back to the kernel and drivers...doesn´t make any sense, didn´t Nvidia fixed it ? Thankss it will be a pleasure to try my best as well to grow and learn in here so may be someday I can help others as well. Cheers and God Bless...


Propose to rename the lineBroadening into Apodization

Since it is not integrated in the FiltersToolBar, yet, I propose that you rename the lineBroadening function into "apodization". In this way, we will not only do exp multiplicaiton (line broadening) with it but also apply other window functions. You could add options (sin, sin2... in the menus similar to the  one for zero filling) to select the one we wish. It would be nice that if the data come from (say) Bruker data, the default apodization is the one used on the spectrometer.

Currently we have one tool bar in which we plan to put apodization and also zerofilling. What do you think ?

Yes, I think that it is OK to have all window function, zero filling and (ev. lin pred...?) as a single tool bar.
One could us it as a single filter. But your design allows (and it is nice) if we can also apply multiple window function in sequence. It is not always necessary making sense, but it may be a good way to completely control the order of the application of the operations. I suppose that a pull-down menu could be used to select the window function and (according to the choice), the parameter for the processing would be proposed (using the value from the Bruker file as default) accordingly. We can inspiration from Bruker "edp" window, the Mnova parameter window and the NMR pipe choices. For the code or the operations, I don't know if NMR pipe code is open, but it may be a way to get the window functions from. Alternative (I have not checked if they are relevant - but these are the possible source of code/inspiration) GNAT (https://www.nmr.chemistry.manchester.ac.uk/?q=node/430) , ccpm (https://www.ccpn.ac.uk/v2-software/software) - maybe you also did something?


Example doesn't work

Trying to get this to run with my Cloudflare Pages + Remix + Emotion + Chakra-UI app. After following the README.md guide, I'm encountering the following error:
$ npm run dev
Building Remix app in development mode...
Error: Error loading Remix config in /Users/.../remix.config.js
    at Object.readConfig (/Users/.../node_modules/@remix-run/dev/config.js:67:11)
    at Object.build (/Users/.../node_modules/@remix-run/dev/cli/commands.js:151:31)
    at Object.run (/Users/.../node_modules/@remix-run/dev/cli/run.js:351:22)
    at Object.<anonymous> (/Users/.../node_modules/@remix-run/dev/cli.js:16:11)

First I thought this was a misconfiguration problem (or possibly an incompatibility with CF Pages), but it turns out that your /example runs into the same problem. I see that this package was just freshly upgraded 5 hours ago, so I'll downgrade to v1 for now. Thank you for investing your time in maintaining this publically, can't wait to have this fixed! 💯

@3x071c Thanks for actually using this library.
I am wondering why I am getting errors like the one you presented, since I have verified that /example is running correctly, as shown in the image below.

I would like to know in order to streamline my investigation.

What is the version of Node in your environment?
Downgrade remix-esbuild-override to v1 in your repository and get the same error?

I can confirm same error;
node -v
v17.8.0
npm -v
8.5.0
Both
"remix-esbuild-override": "^1.0.0",
"remix-esbuild-override": "^2.0.0",
fail with same error, so only diff is yarn vs npm?
Cheers!

@gnimmelf Thanks for the detailed information. This will help me in my investigation.
I promise to address and resolve the issue as soon as possible.

@aiji42 Thanks for investigating. Perhaps this is an npm-specific issue?

@3x071c I have not yet been able to determine the cause of the problem, but I believe it is likely.

The remix-esbuild-override intercepts the esbuild call from remix by rewriting the path to esbuild under node_modules using the file system.
I suspect that the error is caused by a slight difference in the configuration of the directory under node_modules during module installation between yarn and npm.

@3x071c @gnimmelf
Can you try to delete node_modules/@remix-run/dev/node_modules/esbuild and run the development command to see if it starts?
rm -rf node_modules/@remix-run/dev/node_modules/esbuild
npm run dev

I would like to know in order to streamline my investigation.

What is the version of Node in your environment?

I'm using the latest Node.js version (17.8.0), with npm

Downgrade remix-esbuild-override to v1 in your repository and get the same error?

Downgrading and reconfiguring remix-esbuild-override to 1.2.2 works with Remix 1.3.x. Confusingly, it doesn't with Remix 1.2.x.

node_modules/@remix-run/dev/node_modules/esbuild

Weird, that doesn't work for me.

@marcus-sa Thanks for letting me know.
Is the error you observed the same as the error @3x071c presented at the beginning of the Issue?

@aiji42 this is the error I'm currently getting
Cannot find module 'esbuild-org'
at Object.<anonymous> (/home/marcus-sa/Git/marcus-sa/onlyfans-clone/node_modules/remix-esbuild-override/dist/index.js:18:14)

@aiji42 Works great for me! Thank you. 👍

I am making this release and closing the issue. Thank you all for your help in reporting and debugging.
I am hopeful that the errors you have reported have been resolved, but if they recur, please re-open the issue.


Avoid fetching null paths

Missing paths were generated by the recent change to paths with null/undefined/empty key sets. This resulted in unnecessary network requests.

Coverage decreased (-0.1%) to 92.715% when pulling f6880984eaa039fb296ccc1aad85a2bc2fa35acb on avoid_fetch_null_path into bccaa349c79433d47e804aa06e7a402dd7761426 on master.


CLA whitelist: do not require bots to sign CLA

URL to the linked Repo/Org: https://github.com/gramework/gramework
Steps to reproduce the problem:

Create repo
Connect any bot (e.g. FOSSA)
See the PR created

What is the expected result?
Bot should not sign CLA to pass the check
What happens instead?
Bot should sign CLA

ah, sorry, didn't noticed it in the dashboard


Update GO panel display on summary page

Keep the table setup but only display the last five by date for each row. These should be separated by lines rather than commas.

https://github.com/dictyBase/Migration/issues/111
https://github.com/dictyBase/Migration/issues/110

Example of gene with multiple extensions, including multiple for one term:
https://betafunc.dictybase.org/genes/DDB_G0280531/goas

here is one with many CHEBI extensions to a process term: DDB_G0272004
the gene with SO extension: DDB_G0278741

maybe also linking the RNA annotation issue here
https://github.com/dictyBase/Migration/issues/109

The summary display has been updated in version 2.0.0 which will be deployed very soon.


Purpose of the index.js file?

Why do we need this file?
export MasterPage from './MasterPage'
export IndexPage from './IndexPage'
export LoginPage from './LoginPage'
export RegisterPage from './RegisterPage'
export ResetPasswordPage from './ResetPasswordPage'
export VerifyEmailPage from './VerifyEmailPage'
export ProfilePage from './ProfilePage'
export ChangePasswordPage from './ChangePasswordPage'

When each of the, say for example IndexPage has its own
export default class IndexPage extends React.Component { ....
}

Did you figure this out?  I don't understand what this file does, but without it things fail.

@micahstartnow @scheung38 without it, you would have to import each Component as such:
import MasterPage from './MasterPage'
import IndexPage from './IndexPage'
import LoginPage from './LoginPage'
import RegisterPage from './RegisterPage'
import ResetPasswordPage from './ResetPasswordPage'
import VerifyEmailPage from './VerifyEmailPage'
import ProfilePage from './ProfilePage'
import ChangePasswordPage from './ChangePasswordPage'

You're exposing each component by adding export default class before the class declaration but the index.js functions as an entry point that groups all of these similar components so you can organize them and export them more neatly. It's really just a preference.


x/image/font/sfnt: not all tables begin with four byte boundries

What version of Go are you using (go version)?

$ go version
go version go1.15.3 linux/amd64

Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/zhou/.cache/go-build"
GOENV="/home/zhou/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/zhou/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/zhou/go"
GOPRIVATE=""
GOPROXY="https://goproxy.cn,direct"
GOROOT="/usr/lib64/go/1.15"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib64/go/1.15/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/zhou/test/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build508378831=/tmp/go-build -gno-record-gcc-switches"

What did you do?

https://play.golang.org/p/0_ESQiUzpHy
/usr/share/fonts/truetype/wqy-zenhei.ttc is "WenQuanYi Zen Hei", the primary Simplified Chinese font for many Linux distributions for many years before Noto Sans CJK. nowadays many distributions still provide it, and some of them still don't have Noto Sans CJK fonts and didn't switch their default SC font yet. BTW, fontconfig project set it as the default SC font for programs relying on it without tweak.
In one word, if you want to print something Chinese with golang/x/image/font infrastructure, "wqy-zenhei.ttc" may come to your mind definitely.
What did you expect to see?
nil error
What did you see instead?
sfnt: invalid table offset
I print the tag with:
func tag2string(u uint32) string {
  s := strconv.FormatUint(uint64(u), 16)
  decoded, _ := hex.DecodeString(s)
  return string(decoded)
}

And find a weird tag "BDF" and "FFTM" , after some research I found they are fontforge specific tables, and are non-standard extension for opentype specification.
https://fontforge.org/docs/techref/non-standard.html#non-standard-bdf
the offset for previous BDF tag is 956, the length is 845.
the offset for FFTM tag is 8659, the length is 28.
if o&3 != 0 || n&3 != 0 {
  fmt.Println(u32string(tag))
  fmt.Println(o)
  fmt.Println(n)
}
// We ignore the checksums, but "all tables must begin on four byte
// boundries [sic]".
/*if o&3 != 0 {
  return nil, 0, false, errInvalidTableOffset
}*/

tag: BDF
offset: 956
length: 845
tag: cmap
offset: 1801
length: 6854
tag: cvt
offset: 8655
length: 4
tag: FFTM
offset: 8659
length: 28
tag: gasp
offset: 8687
length: 16
tag: GDEF
offset: 8703
length: 32
tag: glyf
offset: 8735
length: 12302984
tag: GPOS
offset: 12311719
length: 32
tag: GSUB
offset: 12311751
length: 248
tag: head
offset: 12311999
length: 54
tag: hhea
offset: 12312053
length: 36
tag: hmtx
offset: 12312089
length: 179544
tag: loca
offset: 12491633
length: 180092
tag: maxp
offset: 12671725
length: 32
tag: name
offset: 12671757
length: 2467
tag: OS/2
offset: 12674224
length: 86
tag: post
offset: 12674310
length: 451503
tag: vhea
offset: 13125813
length: 36
tag: vmtx
offset: 13125849
length: 179326

because BDF table contains a string table, which is raw ASCII bytes. so it is hard to controll the 4 byte boundaries.
but seems fontforge do the byte alignment by itself as a whole.
so, I think, as many old "bimap embedded"  trutype fonts exist, can we skip this boundary check? simple comment it out saves wqy-zenhei.ttc

cc @nigeltao

If anybody likes I can help implementing the parseBDF and parseFFTM functions, but I think they’re useless for truetype rendering and no one cares them...so it’s enough if we unlimit the table boundary check

I don't think we need parseBDF or parseFFTM functions, but https://docs.microsoft.com/en-us/typography/opentype/spec/otff clearly says "All tables must begin on four-byte boundaries".
Two questions:

Do you know if wqy-zenhei.ttc is usable on Microsoft Windows?
Do you know where in the C freetype code they enforce (or don't enforce) four-byte boundaries?

@nigeltao

Sure wqy-zenhei supports Windows...but due to the popularity of simsum.ttc( which I doubt has the same problem since it’s also a bimap embedded truetype), it’s hard to see it installed
These C codes do the table identification job in freetype2:

https://github.com/aseprite/freetype2/blob/master/src/sfnt/sfobjs.c#L451-L469


Minor fix to have --re-parse-existing pass XML content into Parse() i…

…nstead of the filename.
Re-tested same (simple) scenarios; works OK and the appcast.xml verifies as well.

Thank you!! ✨


how to set serverTimezone for MySQL8

Describe the bug

my project:04_oversell
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Busy with work these days, I'll look into the issue when free, thanks for your feedback

Busy with work these days, I'll look into the issue when free, thanks for your feedback

After I set the db parameters as in the figure below, the problem no longer occurs.

Busy with work these days, I'll look into the issue when free, thanks for your feedback

After I set the db parameters as in the figure below, the problem no longer occurs.

Good


[Bug][Table] 官网 Table 固定列的表格固定两列 有问题

tdesign-vue-next
You will open a bug issue at tdesign-vue-next。
Describe Environment
browser version: Chrome
tdesign-vue-next version:
Describe the bug
A clear and concise description of what the bug is.
codesandbox online demo:

Additional context
Add any other context about the problem here.

0.9.0 已修复


Add tests

Set up the testing environment and added first tests for the Avatar component.
I wasn't sure how to test the styled-components / styled-system styles properly. As you can see we are now checking for 3em but it would be better to do this based on a variable set in the test itself.
Should we also be testing for if the component is capable of passing the url and name props?

Hi Sander,
Sorry, for my late reply. Let's find a better workflow together. Maybe chat soon to discuss. The tests look good.
A couple of small remarks:

put package-lock.json in .gitignore. normally it should be under source control, but given the fact that this is a monorepo managed by lerna, only the toplevel one is pushed to git.

what are the 'size is 3em' and 'contains img' tests testing exactly? It's not determined by the props, is it? I'd probably leave it out, especially since the snapshot already covers these two props.

In general, only tests inputs and output (in other words: given a set of inputs (props), this should be the output).

Taken the previous point in consideration, I'd argue that for this component a snapshot test is probably enough.

Okay, that's my feedback for now. The tests will probably become a lot more interesting, once the components are a bit more challenging.
Let's chat soon and discuss a better workflow (and again apologies for my tardiness)
JH

I've revised the previous tests and added tests for Bar and Button components.
I found that a common case people tend to test components on, is if they are capable of passing/setting props. But props are not always used 1 on 1 in the component, e.g. you might use the prop to calculate a different value and render that in the component. Also, you can't always pass all props that the component is capable of setting at once.
This last scenario happens in the Button component, where you wouldn't pass both an onClick and a href. In the test I've now used a few props to test if the component is capable of setting props:
const props = {
    variant: "primary",
    children: formatTitle("click me!"),
    type: "button",
  };

  it('passes props', () => {
    const tree = shallow(<Button {...props} />);

    expect(tree.props()).toMatchObject(props);
  });

I'm unsure wether with testing the capability of setting props, we're really just testing if the component can set any prop, or if we're supposed to test the capability of setting each individual prop.


PdfHighlighter enhancements

auto color differentiation per class (currently need to specify each color)
add small writing of what label each highlight it is above the actual label (like annotated PDF sample)

Done


KAFKA-4931: stop script fails due 4096 ps output limit

This also fixes KAFKA-4389 and KAFKA-4297, which were exactly the same
issue but for kafka-server-stop.sh.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/5563/
Test PASSed (JDK 7 and Scala 2.11).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/5549/
Test PASSed (JDK 8 and Scala 2.12).

AFAIK, jps tool is not available on IBM Java.

I pushed a change so we use jps if it's available and fallback to using ps when it's not

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/5588/
Test PASSed (JDK 7 and Scala 2.11).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/5574/
Test PASSed (JDK 8 and Scala 2.12).

LGTM

If multiple Kafka brokers are running in the same machine, which one will it stop ?
Existing script using ps command have the same problem, but now it does nothing.

@Kamal15 it will kill all of them. Wdym "now it does nothing"?

No, it won't kill any server. Since the grep output is empty.

@Kamal15 which grep output (the jps or ps one?) and if the jps one what jre/jdk are you using?

@tombentley
Assume that multiple brokers are running in different ports in a machine. Earlier, on invoking sh kafka-server-stop.sh due to 4096 ps output limit, we will get "No kafka server to run".
Now with your changes, jps command will definitely return a PID which may or mayn't be the intended broker to stop. I'm using oracle jdk 1.8.0_121

@Kamal15 but in environments where the 4096 limit was not hit the original script would have killed all the servers. So in that respect this patch doesn't change anything: The stop script still kills all the applicable server processes. There's a separate JIRA about this https://issues.apache.org/jira/browse/KAFKA-4110

@tombentley
Ok then. I'm un-aware of the Jira.


Add files via upload

This is the almost finished windows installer minus the CI

I added a readme after a further code review


shallow merges the existing machine context and the passed in context…

… from the parent.
not sure what sort of effect this change will have, since it appears that when it was created it was intentionally not merging the contexts. But all the tests pass. :D
Fixes #993

As innocuous as this seems, this might be a breaking change... but might not be. What do you think @Andarist ?

Yeah I agree that it has the potential to be a breaking change. I’i have workaround I can use until it’s released, so it doesn’t bother me if you merge it into the 5x branch

Though thinking about it, because the parent context is merged second it should always win. So what would happen is that you just have additional properties on the context object that weren’t there before... hypothetically not a breaking change right?

Though thinking about it, because the parent context is merged second it should always win. So what would happen is that you just have additional properties on the context object that weren’t there before... hypothetically not a breaking change right?

Yeah this was my thinking too. Would be good to get a second opinion too.

Seems additive to me, and thus not technically breaking.

Sounds good to me - I myself have wished that it shallow merged, and my original thinking in the API design was that the context could be anything, but in V5 we will enforce that it is an object.
Can you add a changeset? cd into the root directory and run yarn changeset - this would be a minor change to xstate.

This technically is a breaking change, but I don't think we need to worry about it that much as pragmatically it probably wouldn't break anyone or just a super small fraction of users.
There is a possibility of TContext having an optional property that is filled in and which gets removed currently, but would be preserved with your change merged in. So if somebody would rely on it somehow it could break them.
I believe this is a change that is already merged into v5 branch, so maybe it would be better to hold off this PR and just release v5-alpha version sometime in the near future, so you could install it to get this feature sooner than others.

If you think this change is already in v5, would it be preferable that I check that branch out and add the test there just in case?
Or what would you like me to do at this point?

@frehner It's already in the next branch 👍

Ok. I'll close this PR then - and leave the issue open until there's a 5x release?


sbt resolves dependencies differently with/without coursier

Hi,
Since sbt switched to Coursier I've faced with the issue described in https://github.com/sbt/sbt/issues/5389. It looks like the root cause of the issue is a different classpath we get using Ivy and Coursier.
So, here is a problem repo https://github.com/rusexpertiza-llc/yupana. The subproject is hbase. Here is the diff between Ivy dependencies and Coursier:
- guava-12.0.1.jar
+ guava-16.0.1.jar
+ hadoop-mapreduce-client-core-2.5.1.jar
+ hadoop-yarn-api-2.5.1.jar
+ hadoop-yarn-common-2.5.1.jar
+ jline-0.9.94.jar
+ netty-3.7.0.Final.jar
- protobuf-java-2.6.1.jar
+ protobuf-java-3.8.0.jar
+servlet-api-2.5-20081211.jar

One of the problems I see here is that forced version for protobuf-java is ignored.

I've noticed major differences between the coursier and ivy classpaths as well...
for example my project depends on com.microsoft.azure:msal4j:1.8.0
that lib depends on com.nimbusds:oauth2-oidc-sdk:7.4 which depends on com.nimbusds:nimbus-jose-jwt:8.14.1
coursier doesn't even download either of those two jars nor add them to the classpath....
I had to disable coursier to get my project to function.
ThisBuild / useCoursier := false
seems odd to rewrite dependency management when maven/ivy are tried and trued...

I wonder if this issue is related:
https://github.com/coursier/coursier/issues/1954

It's interesting that the dependency resolution differences seem to be around Hadoop related things.
For example, if you look at cs resolve org.apache.hadoop:hadoop-common:2.9.2 -t, you'd see the libraries that are mentioned here like netty-3.7.0.Final and nimbus-jose-jw.
It would be good to compare not just Ivy vs Coursier, but also the resolution result of Maven as well because some of the differences could be coming from the fact that Coursier is doing a better job emulating Maven, especially when it comes to traversing the parent POMs.
Hadoop depends on Apache Curator Framework.
https://repo1.maven.org/maven2/org/apache/curator/curator-framework/2.7.1/curator-framework-2.7.1.pom
At a glance it doesn't look like it doesn't depend on much:
<dependencies>
  <dependency>
    <groupId>org.apache.curator</groupId>
    <artifactId>curator-client</artifactId>
  </dependency>
  <dependency>
    <groupId>org.apache.curator</groupId>
    <artifactId>curator-test</artifactId>
    <scope>test</scope>
  </dependency>
</dependencies>

but wait there's more...
<parent>
  <groupId>org.apache.curator</groupId>
  <artifactId>apache-curator</artifactId>
  <version>2.7.1</version>
</parent>

Here's the parent POM - https://repo1.maven.org/maven2/org/apache/curator/apache-curator/2.7.1/apache-curator-2.7.1.pom
<dependencies>
  <dependency>
    <groupId>org.apache.zookeeper</groupId>
    <artifactId>zookeeper</artifactId>
  </dependency>
  <dependency>
    <groupId>com.google.guava</groupId>
    <artifactId>guava</artifactId>
  </dependency>
  <dependency>
    <groupId>org.testng</groupId>
    <artifactId>testng</artifactId>
    <scope>test</scope>
  </dependency>
  <dependency>
    <groupId>org.slf4j</groupId>
    <artifactId>slf4j-log4j12</artifactId>
    <scope>test</scope>
  </dependency>
</dependencies>

That's Guava 16 and Zookeeper 3.4.6. Hadoop also depends on Zookeeper but with excludes. Curator doesn't have those excludes.
What does Zookeeper 3.4.6 depend on? https://repo1.maven.org/maven2/org/apache/zookeeper/zookeeper/3.4.6/zookeeper-3.4.6.pom
<dependency>
  <groupId>jline</groupId>
  <artifactId>jline</artifactId>
  <version>0.9.94</version>
  <scope>compile</scope>
</dependency>
<dependency>
  <groupId>io.netty</groupId>
  <artifactId>netty</artifactId>
  <version>3.7.0.Final</version>
  <scope>compile</scope>
</dependency>

That's right JLine 0.9.94 and Netty 3.7.0.Final.
I mean you probably don't need those (and that's why Hadoop excludes them), but when I see extra JLine or Netty, I usually assume that Coursier is being correct.

@bpossolo About com.microsoft.azure:msal4j:1.8.0, it seems coursier does download com.nimbusds:oauth2-oidc-sdk:7.4 and com.nimbusds:nimbus-jose-jwt:8.14.1:
$ cs resolve com.microsoft.azure:msal4j:1.8.0
...
com.nimbusds:nimbus-jose-jwt:8.14.1:default
com.nimbusds:oauth2-oidc-sdk:7.4:default
...

(and cs fetch com.microsoft.azure:msal4j:1.8.0 downloads their JARs).

If that's the case, then the problem I experienced is probably due to sbt-eclipse.
Seems like it's producing an incorrect .classpath file.


Support for aws-auth in terraform enterprise

I'm submitting a...

[ ] bug report
[ ] feature request
[ x] support request
[ ] kudos, thank you, warm fuzzy

I'd like to have terraform enterprise automatically apply the aws-auth ConfigMap after provisioning an eks cluster. Currently it's required to add the aws-iam-authenticator to your PATH and have kubectl available. The enterprise version of terraform doesn't allow me the flexibility to install binaries or touch the folders in the $PATH environment variable. I'd like to know if there are any plans to add support for this or if there is a recommended workaround.

You can also just change your KUBECONFIG to a path of your choosing, right?
e.g.
...
users:
- name: my-cluster
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1alpha1
      command: /my/path/to/aws-iam-authenticator
      args:
        - "token"
        - "-i"
        - "my-cluster"

Trying the same here..
@max-rocket-internet The problem is the kubectl invocation here: https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/aws_auth.tf#L17
I'm currently trying to use a local-exec to install kubectl to /usr/bin/. That seems to success (eg the provisionber succeeeds without error output) but for some reason it still can't find it. I'll update this issues if I find a solution.

Okay, I spent most of my day trying to somehow get a single terraform apply run to first install kubectl locally and then run the aws-eks module. I don't think that's possible..
I've tried various hacks like running the install in data.external, but that seems to get execute in a different environment. I also tried running with null_(data_)resource which again isn't working since I can only capture the null_resources 'id' which is available before it finishs... So I conclude we need support for that in here, e.g something that passes through a reference to the null resource executing kubectl. I'll look into that tomorrow.

Okay, I finally managed to solve that even without changing this module. Instead of trying to install kubectl etc prior to the module being executed (1), I set manage_aws_auth = false and uses the rendered config map module output and applied that after cluster creation in a null_resource/local-exec.

At this point I say is impossible since there is no way to make a module depend on a null resource, even with hacks since the null resource has no outputs or attributes that would be only available after it finished

Here's what I use:
resource "null_resource" "apply_configs" {
  triggers {
    config_map_aws_auth = "${sha256(module.eks.config_map_aws_auth)}"
    kubeconfig          = "${sha256(module.eks.kubeconfig)}"
  }

  provisioner "local-exec" {
    environment = {
      AWS_CONFIG_MAP_RENDERED = "${module.eks.config_map_aws_auth}"
      KUBE_CONFIG_MAP_RENDERED = "${module.eks.kubeconfig}"
    }
    command = <<EOH
mkdir bin
curl -s -o bin/aws-iam-authenticator https://amazon-eks.s3-us-west-2.amazonaws.com/1.12.7/2019-03-27/bin/linux/amd64/aws-iam-authenticator
curl -s -L -o bin/kubectl https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/linux/amd64/kubectl
chmod 755 bin/*
export PATH=$(readlink -f bin):$PATH
echo "$AWS_CONFIG_MAP_RENDERED" > aws_auth_configmap.yaml
echo "$KUBE_CONFIG_MAP_RENDERED" > kube_config.yaml
for i in `seq 1 10`; do
  kubectl apply -f aws_auth_configmap.yaml --kubeconfig kube_config.yaml && break || sleep 10;
done;
EOH
  }
}

It has the advantage of only running when configs change.

Closing with @eytanhanig idea as a work around. If someone has a nice and elegant solution then feel free to make a PR 🙂


in canvas cards, triple-backtick text is drawn in a proportional font, not mono

On this canvas card, I expected the cyan words to be in a monospace font, like they are in a non-canvas note.
Here's a non-canvas note:

I think you are in the wrong repo with this one.
This is what a canvas card looks like in the official Dracula theme, where this issue is posted:

This is with the unofficial Dracula theme by jarodise:

So while your issue strictly speaking has nothing to do with this repo, cards in the official theme DO look wrong in their own way by using the wrong colors and not using correct background colors.

I have updated the theme to not override the background color so it allows setting the card color via the canvas color chooser. I also added the Dracula colors to said color chooser.
So while you are talking about a different theme entirely, you helped me identify issues with this new cards feature that I wasn't aware of. Thank you!

I understand now- I never even noticed there were two draculas.

"Two draculas looking at obsidian"

That picture is gold.
But yeah, it is quite confusing that the theme with more downloads is the unofficial one, and that there are even two separate themes to begin with.


Let's build better tools together 🧰

I found my people, maybe, hopefully: let's build better tools 🛠🧰🚀
I am limited by my tools. I need more big brains to help implement my ideas 🚀🧠 together 🛤🚀
@TechBroTino

Hi @taylor1477, it sounds interesting to build tools using these principles for the LLM prompting, and we are open to collaborating on this.

Overstimulated my brain so currently recovering but I’m writing a framework attempting to tie the many parts together: I will reach back out in a couple days, hopefully we can build better tools for the future! @techbrotino on X if you want to see some my note in ‘ beautiful minds’ mode that led to the burnout lol there just musing I had while writing tho so don’t be scared by the unhinged nature 😅


[RHOAIENG-5489] Home page: projects w/ tiles

Closes: RHOAIENG-5489
Closes: RHOAIENG-5490
Closes: RHOAIENG-4860
Description
Add project tiles to the home page projects section.
How Has This Been Tested?
Locally tested while turning the home page feature floag on
Test Impact
Added e2e tests
Screen shots
Full tiles w/ self-provisioning access

Full tiles w/o self-provisioning access

Less tiles w/ self-provisioning access

Less tiles w/o self-provisioning access

Request review criteria:

[x] The developer has manually tested the changes and verified that the changes work
[x] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)
[x] Included any necessary screenshots or gifs if it was a UI change.
[x] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

/cc @jgiardino

Oh no! I just posted a comment and saw that this PR was merged. 😬
I was also going to say that these updates look really good. That one comment was the only thing I saw. But it's also really minor.

@jgiardino if you get to it late you get to it late. @jeff-phillips-18 should still react to your feedback and he can sneak small things into future work or craft a new issue if it's larger. We don't usually wait on UX reviews as there will be more reviews later once the work is more complete.


Waku Socket (better name pending)

From the p2p WebRTC exploration, a requirement has emerged to design a protocol that enables two peers to communicate over Waku using their peer id as identifier.
In a first phase, the protocol does not need to be encrypted (signal server sees all content in clear). However, it may be interested to add a layer of encryption using https://rfc.vac.dev/spec/35/ at some point.
The usage of peer ids as identifier is to enable this protocol to be used as libp2p transport. Which in turns, enables it to be used for WebRTC handshakes.
Note that the usage of peer id is likely to leak out privacy information, enabling anyone observing the network to know who is doing a webrtc handshake with whom.
As we get a first "unsecure" PoC working, we can then iterate and add needed privacy features.
Notes
In terms of technical design, it would make sense to implement an API similar to https://socket.io/ with emit/on/once:
socket.on(event: string, listener: (data: any) => void)

Which means that for each message we have:

An event string: Tag that describe the event
A data payload: The type would depend on the event.

socket.io provides a very advanced typing system. We do need to go down this path at first.
Regarding libp2p transport, see the considerations outlined in https://github.com/status-im/js-waku/issues/20#issuecomment-1090973059 especially around multiaddr.
DoD

[ ] A PoC that enables two parties to exchange payload with each other, only knowing each other peer id.
[ ] Implement a libp2p transport using this PoC

Using noise-session directly might be useful here.

https://discord.com/channels/864066763682218004/1019621534769352904/1019871950132219964

May be fixed with https://github.com/waku-org/js-waku-examples/pull/177

The initial use case stemed from Web RTC which is now blocked on libp2p improvement. Ice boxing this.

WebRTC specific work is tracked in #1181
Regarding this issue, the essence of it is encompassed in:

A PoC that enables two parties to exchange payload with each other, only knowing each other peer id.

Enable two parties that know something of each other (ie, a public key) to communicate in an e2ee manner to each other but using something better than ECIES.
How is noise better than ECIES would be good to define so the added value is clear.
Do note similar question asked here: https://github.com/waku-org/js-waku/issues/1181#issuecomment-1434084548 pending input.


Skip  completely

Can you please add an option to skip the addition of < base > completely?
I want to add anchor links and don't need the < base > element.
I tried it with null but it doesn't skip generating the line and still makes anchor links impossible.
    'htmlhead/base' => function ($kirby, $site, $page) {
      return ['href' => 'null'];
    },

ah. its merged. sorry...
https://github.com/bnomei/kirby3-htmlhead/blob/a6f112129451dd381dc1f3c951c4ab940b94d78f/classes/HTMLHead.php#L16

return ['href' => 'null'];
or
return [];
should work now.


Modal on mithril app doesn't show

Hello, has anyone experienced using materialize on mithrilJs app here?
I'm facing an issue where I can't get the jQ modal trigger to work, here is my code (in livescript)
m.render document.body,
  m \.modal#modal1, m \.modal-content,
    m \h4, 'Modal Content'
    m \p, 'A bunch of text'

And I tried to activate the modal from browser console with
$('.modal').modal()

or
M.Modal.init document.querySelector \.modal

nor with
m \button.btn.modal-trigger, 'data-target': \modal, \Modal

Neither of them seems to work. Here is the link to my repo to see the complete case

I have found the right way to do it. Just do modal open after modal initialization
$('.modal').modal('open')


Use pattern matching at the namespace level

This follows #46. Each node will now listen to only three channels:

socket.io#<namespace>#*: used when broadcasting
socket.io-request#<namespace>#: used for requesting information (ex: get every room in the cluster)
socket.io-response#<namespace>#: used for responding to requests

We keep the benefits of #46 since:

messages from other namespaces are ignored
when emitting to a single room, the message is sent to
socket.io#<namespace>#<my-room>, so listeners can check whether they
have the room before unpacking the message (which is CPU consuming).

But there is no need to subscribe / unsubscribe every time a socket
joins or leaves a room (which is also CPU consuming when there are
thousands of subscriptions).

So, as a consequence of this change (not subscribing to specific rooms, but instead to generic namespaces).  The result will be that EVERY client will get EVERY message correct?  While, I see that you're checking before you unpack the message, there is no way to horizontally scale this at some point.  The overhead of receiving/checking every message from every client on the entire system seems to be a big problem for apps with high workloads.


Replace org.json with com.github.openjson in com.ibm.mq.jakarta.client

The original library is licensed under a standard BSD license with an additional line that requires the use of the software only for "non-evil" purposes. Since this is ill-defined, many downstream consumers of this software find this license condition unacceptable. The moral is don't put jokes into legal documents. More background information is collected by the Debian team members at https://wiki.debian.org/qa.debian.org/jsonevil
https://github.com/openjson/openjson

This is not something that can be handled through this repository. If you've got a suggested change to the underlying MQ client libraries, then you can open an Idea at https://integration-development.ideas.ibm.com

This is not something that can be handled through this repository. If you've got a suggested change to the underlying MQ client libraries, then you can open an Idea at https://integration-development.ideas.ibm.com

Alright - thank you for pointing me in the right direction!


Patch md styling

Description of the change:
Reason for the change:
Link to original source:

Closes #

Hello @justinwhall,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX


add resource, fix steps

@flaviuvadan  btw there might be something weird with your DCO, your commits are authored using
Flaviu Vadan<EMAIL_ADDRESS>
but signed off using
# Notice the different name
flaviuvadan<EMAIL_ADDRESS>
which causes DCO to fail


Prepare release Batch 5 RPs (3)

Azure.ResourceManager.LabServices
Azure.ResourceManager.Marketplace
Azure.ResourceManager.MixedReality
Azure.ResourceManager.NetApp
Azure.ResourceManager.Peering
Azure.ResourceManager.Purview

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.NetApp


Tons of smaller quality improvements

This PR addresses a lot of compiler warnings WRT tidbits like extraneous semicola, missing return statements or unreachable statements.

CircleCI is reporting that the tests are failing because of a bad include order, but IIRC I didn't touch any includes.
/hpx/hpx/config.hpp:14:2: error: Boost.Config was included before the hpx config header. This might lead to subtile failures and compile errors. Please include <hpx/config.hpp> before any other boost header
#error Boost.Config was included before the hpx config header. This might lead to subtile failures and compile errors. Please include <hpx/config.hpp> before any other boost header

@gentryx don't worry about this, it's not your problem but was caused by a bad master branch at the point you branched off.
The changes LGTM.

std::numeric_limits lives in <limits>, every single header that uses it shall include it.

@K-ballo Fixed, thanks!

If the purpose of -1 is to serve as a magic number, then why not define a constant of that value with an appropriate name? Anyhow, I've changed all initializations to use explicit casts.

I'm fine with having a static std::size_t const any_thread = std::size_t(-1); and use this as the sentinel.


Startup ~100ms slower with Electron 6

The perf bot shows that builds running Electron 6 are starting roughly 100ms slower (1835ms vs 1723ms). We should understand why and we should try to get that time back. Seems to only happen with windows.

Pending verification once https://github.com/electron/electron/pull/20709 gets into the next electron version bump.

VS Code keeps increasing the startup time. Meanwhile, Sublime Text is just freaking amazing and starts faster than the time of realizing you launched it.
Launching Sublime Text is so seamless and fast that it becomes muscle memory.
When I launch VS Code, I have the time to realize I am launching a text editor, to realize "if I launched Sublime Text it would be much faster and this editing would be done already", and I also have the time to become frustrated and annoyed. When launching VS Code, I have the time to realize I launched a text editor.
This issue indicates that startup time will not be getting any better with VS Code, if anything, it will just be getting worse. 😞

Looking at telemetry it seems that getting the workbench ready takes longer now. Since day 284 it dropped by a lot which might hint towards the code mitigation change

Build a release config with that flag turned off to verify the difference, will post updates shortly.

@deepak1556 With electron fiddle and this gist https://gist.github.com/3d4909b7a1fc1664b962fb108de2d150 and I can also see how electron 6 is somewhat slower

I assume nothing will happen for the October timeframe... 😭

@bpasero I tried that, there was no difference that was consistent enough to point it as the cause. I am now tracking down the regression on electron side.

Makes sense.

I guess we won't do anything except for hoping that this is getting better with the next version of electron.


Update deploy-to-futurenet to use public rpc

Preview is available here:http://soroban-docs-pr372.previews.kube001.services.stellar-ops.com/

Preview is available here:http://soroban-docs-pr372.previews.kube001.services.stellar-ops.com/

Preview is available here:http://soroban-docs-pr372.previews.kube001.services.stellar-ops.com/

Preview is available here:http://soroban-docs-pr372.previews.kube001.services.stellar-ops.com/


Use projects in config instead of custom script

Summary
As requested in #5052, this simplifies running examples even more by making them first-class part of the normal test suite.
I would highly prefer not deleting the README, but this resolve call removes trailing /, so I cannot just match directories in the glob:
https://github.com/facebook/jest/blob/e44de3f0b6c957ea5c38f85e3e559e2c665a830c/packages/jest-config/src/utils.js#L58
Normally a trailing slash is enough, as per https://github.com/isaacs/node-glob/blob/8fa8d561e08c9eed1d286c6a35be2cd8123b2fb7/README.md#options

Test plan
Green CI

Codecov Report

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

@@           Coverage Diff           @@
##           master    #5053   +/-   ##
=======================================
  Coverage   60.72%   60.72%
=======================================
  Files         198      198
  Lines        6605     6605
  Branches        3        4    +1
=======================================
  Hits         4011     4011
  Misses       2594     2594

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 e44de3f...79468a4. Read the comment docs.

Lovely!


register new sensor

Hello,
am trying to add a new radar sensor (https://github.com/uos/rmagine_gazebo_plugins)
I've followed all the instruction on the new sensor documentation, and it works with examples.
When I tried to implement it with mir_250, it dosen't works, because one step is necessary: "register a new sensor in gzserver", will you please advice me where should i register this sensor?
the command is:
<node name="gazebo" pkg="gazebo_ros" type="gzserver" args="-s librmagine_embree_sensors_gzregister.so" output="screen" /> -->
  <!-- <node name="gazebo_gui" pkg="gazebo_ros" type="gzclient" output="screen" if="$(arg gui)" />

thanks in advance.

Sounds like a you should open this issue in rmagine_gazebo_plugins), not here.
@aock: Any ideas?

Closing this issue. Please reopen at one of @aock's repositories.


Use overmind to run Procfiles, if available

Overmind is a process manager (like foreman) for Procfile-based applications. The advantage is that it allows to use debuggers like pry or binding.irb without installing extra gems.

This PR is very simple, as I'm waiting for feedback on whether the maintainers like this idea. I can add tests and a CHANGELOG entry after that. I'll also open a PR on cssbundling-rails if this one is accepted.

@dhh thoughts?

I don't think it's worth carrying this specialization. You can just tweak it yourself after it's setup.

Is there any reason to prefer Foreman vs Overmind?

@semaperepelitsa I believe foreman is prefered because it's a pury-ruby solution. You can just gem install it without worrying about OSes and other packages.

Foreman has this annoying issue, its fork overman addresses that. Would you accept a PR for that @dhh?


Callout: Replace title with attributes

The title attribute in the callout component was used as an aria-label for its container.
This is being changed because:

The callout container is a non-interactive element and aria-label is intended for use on interactive elements only (as described in the MDN web docs)
Allowing only one attribute to be passed for a specific option in the container element is quite restrictive

The following changes have been made:

A deprecation warning has now been added to the use of title in the callout component
attributes is now an optional attribute that passes a hash of options to the callout component element

It was also discovered while making these changes, that ActiveSupport::Deprecation.warn is being deprecated but is used in a handful of places in the codebase


How do I launch the webapp?

I have successfully deployed the webapp frontend and infrastructure using 'npm run deployAll' but I don't see the UI. How do I start the UI? There is nothing in the README that I saw. Is the UI supposed to come up after deploy?
Thanks!

You can see the uri after deployment like this or CloudFront page. You can access to the web app.
Also I will add it to the README.
Outputs:
xxx-dev-omics-app-frontendStack.cloudfrontdomain = xxxx.net

Add the output example to README by #44


#version of GLSL in older platform

I am trying to ensure compatibility with older machines.
When using slang::IGlobalSession->findProfile("glsl_330"), it returns a non-zero value.
However, we receive a GLSL code that starts with "#version 450".
Even "slangc.exe" has the same problem.
Is there any way to set a lower version of GLSL?

Another related question is, is there any way to obtain the code for the GLES version "#version XX es"?

GLES isn't an officially supported target at the moment. The current GLSL backend is for Vulkan flavored GLSL only.
I don't think we have profiled defined for anything older than glsl_430, so frontend capability checks for gles platforms isn't possible right now.

A confusing issue is that when we use findProfile() with "glsl_430" or "glsl_440", we always get "#version 450", but versions 450 and 460 seem to work well.

The -profile option to the compiler mostly specifies what intrinsics the code is allowed to use, and does not necessarily translate to the output glsl version. Because our GLSL backend only support the Vulkan flavored GLSL output, we have not implemented anything specific for generate outputs on older GLSL versions.
This isn't a supported feature and we are unlikely to have resource allocated on the GLSL backend as our focus is to get as many users move on to the direct-spirv backend. However we will welcome contributions for a fix to get GLSL backend working in more situations.

Closing as won't fix now.

Thank you for the explanation, after some trial and error, I seem to have found a viable solution.
First, use Slang to generate SPIR-V, then use spirv-cross to generate a lower version of GL or GLES code.


[fix-commission-petition] fix commission test utility function

fix reject handling and commissioner id comparing

No need to merge now since this part of code is undergoing a full rewrite.


Popover and Tooltip demos don't seem to display or function correctly in docs site

See display issues below. Additionally, javascript doesn't appear to be working.
Tooltips
Tooltips in Bootstrap 4 alpha 6 docs (https://v4-alpha.getbootstrap.com/components/tooltips/):

Tooltips in Daemonite's Material UI docs (https://daemonite.github.io/material/gh-pages/components/tooltips/index.html):

Popovers
Popovers in Bootstrap 4 alpha 6 docs (https://v4-alpha.getbootstrap.com/components/popovers/):

Popovers in Daemonite's Material UI docs (https://daemonite.github.io/material/gh-pages/components/popovers/index.html):

This is because popover and tooltip are not initialised on these pages, because Bootstrap popover and tooltip are opt-in for performance reasons.
This has been fixed by https://github.com/Daemonite/material/commit/bc8c31e6491565e8888bf28c51ad07607fdc26d9 in backfilling-bootstrap-v4.0.0-beta


Change Windows to OpenSSL fetched

And update to OpenSSL 1.1.1n
Signed-off-by: Adam Brousseau<EMAIL_ADDRESS>

@vsebe I'm merging this now so the nightly build will pick it up but please review when you get a chance.

Should be --with-openssl=fetched


Use confluent-kafka-python library for Kafka Consumer check

What does this PR do?

Motivation

Additional Notes

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached
[ ] If the PR doesn't need to be tested during QA, please add a qa/skip-qa label.

Current dependencies on/for this PR:

master

PR #13894   👈

This comment was auto-generated by Graphite.

whoops not sure why this PR closed.


div > pre > code not so good

I am using the following code for my code snippets:
div > pre > code

The result is that an extra-wide box appears, which is suboptimal.

Is there a section wrapping that div? From the demo/usage document:

Organize your document with an article element inside your body tag. Inside that, use section tags around each logical grouping of text and headings.

It would be helpful to share a minimal example as text, so the issue can be easily reproduced.

Minimal example:
https://jsbin.com/varukulesi

This appears to be a function of third-party code highlighting the pre rather than the code.

@fulldecent Any further findings on this?

Yes, the highlighter was styling the div.
I did this workaround for Rogue.
.highlight {
  background: none
}

But that is out of scope for this project so I'll call this an incompatibility of Rogue with tufte.css's wide block approach.


VSCode is "unable to resolve resource"

This happens when I click on an error/warning.
I tried using a blank folder, and the "SM Create Project" option, all of them return the same error in the bottom right.

This has been solved over Discord:
TL;DR make sure your paths are correct in your settings.json file

Also VSCode seems to require a restart for the changes to take effect, if anyone still has the issue after modifying the settings.

ss://YWVzLTI1Ni1jZmI6dTFyUldUc3NOdjBw@<IP_ADDRESS>:8388
ss://YWVzLTI1Ni1jZmI6dTFyUldUc3NOdjBw@<IP_ADDRESS>:8388


feat: move arbiturm Faq to a dropdown

Before
After

Hey @saihaj, looks like we did some conflicting work. 😬 I worked directly in Michael's branch, which was merged. Sorry about that!
I went with a shorter URL segment (arbitrum instead of scaling-with-arbitrum), but I didn't add a redirect like you did. Maybe we can repurpose this PR to just add the redirect?


Spyder cannot launch: Access denied

Issue Report Checklist

[x] Searched the issues page for similar reports
[ ] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[ ] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[ ] Tried basic troubleshooting (if a bug/error)

[ ] Restarted Spyder
[ ] Reset preferences with spyder --reset
[ ] Reinstalled the latest version of Anaconda
[ ] Tried the other applicable steps from the Troubleshooting Guide

[ ] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
Not able to launch Spyder4 in Windows10.
Error: Access denied
Python is working well. I ran upgrade on Spyder and it also fine.
What steps reproduce the problem?

Run Spyder4.exe from the folder

What is the expected output? What do you see instead?
I see access denied message. Spyder has been running properly since installed and no changes to my Windows 10 until recently.
Paste Traceback/Error Below (if applicable)

No Traceback. Only Access denied.
PASTE TRACEBACK HERE

Versions

Spyder version: 4.1.3
Python version: 3.8
Qt version: QtPy 1.9.0
PyQt version: PyQt 5.12.3
Operating System name/version: Windows 10

Dependencies

PASTE DEPENDENCIES HERE

Hi @ashura1, thanks for the report. How did you install Spyder?

Hi,I used Pip and there are no failed messages. I had been using it for quite sometimes but it suddenly stopped working with access denied message. This is what annoyed me. I still can launch Python directly with no issue so I can say Python and folders access are fine. I have local admin rights on my laptop too.Sent from my Samsung Galaxy smartphone.
-------- Original message --------From: Gonzalo Peña-Castellanos<EMAIL_ADDRESS>Date: 14/7/20  23:10  (GMT+10:00) To: spyder-ide/spyder<EMAIL_ADDRESS>Cc: ashura1<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [spyder-ide/spyder] Spyder cannot launch: Access denied (#13270)
Hi @ashura1, thanks for the report. How did you install Spyder?
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/spyder-ide/spyder/issues/13270#issuecomment-658169639",
"url": "https://github.com/spyder-ide/spyder/issues/13270#issuecomment-658169639",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]

@ashura1 did you install with admin priviledges?

Closing due to lack of response.


修复JavaBeanDeserializer不能反序列化深层内部类的问题

JavaBeanDeserializer在遇到深层的内部类时抛出JSONException，更改后可以通过src/test/java/com/alibaba/json/test/InnerInnerTest.java

 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.

[Current coverage][cc-pull] is 92.71%

Merging [#658][cc-pull] into [master][cc-base-branch] will decrease coverage by 0.12%

@@             master       #658   diff @@
==========================================
  Files           108        108
  Lines         15812      15848    +36
  Methods           0          0
  Messages          0          0
  Branches       3661       3666     +5
==========================================
+ Hits          14684      14692     +8
- Misses          491        517    +26
- Partials        637        639     +2

Powered by Codecov. Last updated by [036253d...0d8b086][cc-compare]
[cc-base-branch]: https://codecov.io/gh/alibaba/fastjson/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/alibaba/fastjson/compare/036253dc786f2e91623d80de89cac1f7627c4560...0d8b086449e48a303bef16a203f696c16efe131a
[cc-pull]: https://codecov.io/gh/alibaba/fastjson/pull/658?src=pr


Cannot change the way links to files are generated for PHPSTORM (Windows)

Before creating a new bug report
I was not able to find any information on this topic
Describe the bug
It is not possible to open a file in PHPSTORM by clicking the file link in the Ray Windows app.
phpstorm://open?file=[path/to/file] is not working for me even after the steps suggested in the documentation (reg edit and stuff).
That being said, I have another way to open files via link.
I can open files using the built-in server of PHPSTORM by accessing a url like this: http://localhost:63342/api/file/[path/to/file]. (Configuration for this is in Additional Context.)
I am looking for a way to instruct Ray to replace phpstorm://open?file= with http://localhost:63342/api/file/ so I don't have to wait for JetBrains to fix the protocol.
Is there a way to change how the file link is generated?
Versions

PHPSTORM: 2021.3 Build #PS-213.5744.279
Ray Windows app version: <IP_ADDRESS>
spatie/backtrace: 1.2.1
spatie/macroable: 1.0.1
spatie/ray: 1.32.2

To Reproduce
Steps to reproduce the behavior:

Generate a message for the Ray Windows app by calling ray(...args) in a PHP file.

Execute the file and receive the message in the Windows app.

Click the link that is supposed to open the file in the configured code editor

Observe the error

Expected behavior
Be able to open files in PHPSTORM on Windows 10 successfully.
Desktop (please complete the following information):

OS: Windows (build 19042.1415)
Version: 20H2

Additional context
This is my config for the built-in server:

I've created an issue for this in our internal issue tracker. I'll probably add a "custom" option to the selectinput, which allows you to enter your own string that accepts {FILE} and {LINE} placeholders that will be replaced when clicking on a file link.

The above change will be included in the next release (in a few weeks).

@AdrianMrn thanks! I'm looking forward to the next version. Take care!


WIP: Add --package-version-tag flag to apko publish

When this flag is set to a particular package, e.g. --package-version-tag=go, apko will immediately take the version of that package (e.g. 1.18) and tag all images it was going to publish with that version tag.
It does this by grabbing the version for the package from the /lib/apk/db/installed file. If there's a better way to do this I'm happy to update, this was just the only way I could find.
This should make it easy for us to start tagging all images with version numbers.
This will be smaller once https://github.com/chainguard-dev/apko/pull/305 merges first

Nice!


Error on renewing _masterKey when keys are on blob

I sometimes see this 500 error on a POST /admin/host/keys/_master
{
  "id": "66ff4784-59b6-4d20-a2a6-bdcd0940aab5",
  "requestId": "1f4c472a-086e-4a6f-98c8-3236077fa747",
  "statusCode": 500,
  "errorCode": 0,
  "messsage": "The remote server returned an error: (400) Bad Request. -> The remote server returned an error: (400) Bad Request."
}

@krolson Could this be a bad request coming from Azure storage? can you investigate?

@ahmelsayed was this around while there were instances of the UI open (i.e. when you were noticing this behavio: https://github.com/projectkudu/AzureFunctionsPortal/issues/1296?) or can you share any other information on this, like region or if you noticed it specifically for this master key POST or if that was the only key POST you were trying?
@fabiocav is there special handling in the keymanagement for _master key that comes to mind? The blob storage repository treatment is essentially the same for master vs any other key, so this would be a more broad issue if it's storage related.

The master key is not handled in a special way (not any different than other keys in the host secrets file). @ahmelsayed ran into this a while ago, but if we can repro and look at the actual storage exception details leading to the bad request, it might be easier to identify what is going on here.

I tried doing dozens of /admin/host/keys/_master POSTs on my function test site, even alternating between UI and direct requests, but they are all working. Since I haven't been able to get a repro, I was hoping to try to look at logs from when @ahmelsayed hit the issue, but didn't find anything in my limited check without a specific time, site name, or region.

@ahmelsayed I know this was a while back, but do you have storage (or application) logs for this?

@krolson I tried to do the same now, but couldn't get a repro either. I'll close this as no repro, and will open it again if I see the error again.


Infinite loop in TCPTransport.swift : readLoop()

Scenario:

Simple WebSocket server running locally
Launch SimpleTest.xcodeproj to connect to ws://localhost:8080
Close the NWConnection on the server

Result:
On this line :
data = nil
error = nil

thread com.vluxe.starscream.networkstream (serial) enters infinite loop eating up CPU. looking for one more frame even though context.isFinal = true

facing same problem as you

Replacing line 144 with:
if data != nil || context?.isFinal == false {
    s.readLoop()
}

works for me. Is this a possible solution?

Figured it out:
Close socket when your heartbeat not get response

But you will still have the infinite loop (and high CPU usage) till the heartbeat timeout, right?

I think this can be marked as fixed right @sdidla?

✅


[GUI NX - v-guinx-19-05-22] When accessing the Dashboard tosts are being displayed on the screen.

I'm submitting a ...

[x] bug report
[ ] feature request
[ ] support request

When accessing the Dashboard Toast are being displayed on the screen.

Please tell us about your environment:

Version: v-guinx-19-05-22
Environment: [docker-compose]
Operating system: [Ubuntu 20.04]

NX GUI Tested Version: Version: DEV-220816 (OK)


Mob Spawning

I want to disable Mobs but when i do it i cant use eggs. ? can i do it that the mob-spawning is off but i can create mobs ? and only the self createt mobs are alive the others dont spawn automated ?

I fixed eggs a few builds ago. They're fixed in the latest.


Inability to use let / struct

Currently, because of the way ObjectMappers <- operator functions, there is no way to use let properties, and the Mapper class itself requires AnyObject, so where we'd often like to have immutable structs, we have mutable class instances.
Would be real nice if we could fix this limitation.

If you just don't want the properties to be public mutable, I guess you can make it private(set) like this
public private(set) var propertyName: TypeName

ObjectMapper does in fact support let type variables, however it requires some extra code to accomplish. There is an example which you can check out in ObjectMapperTests.swift:
https://github.com/Hearst-DD/ObjectMapper/blob/master/ObjectMapperTests/ObjectMapperTests.swift#L685
Otherwise there are other libraries that tackle this requirement more directly for example:
Himotoki