how to reload Reids acl?

Environment

VerneMQ Version:
OS:Linux
Erlang/OTP version (if building from source):

Expected behavior
Now I authorization using the Reids, but there is a problem：We define one publish_acl [{"pattern":"client/device/json/0"}], we can pusblish the "client/device/json/0" topic，now we change the publish_acl to [{"pattern":"client/device/json/2"}] , If you don't reconnect the MQTT-Server(VerneMQ), we
still can pusblish the "client/device/json/0" topic。
Actual behaviour
we cannot pusblish the "client/device/json/0" topic.
Is there a way to make the publish_acl work right now?

Hi @mao2080 thanks for asking, I guess this intended behaviour though with Redis? Any publish will check the ACLs live.

@ioolkos thanks for answer，but now it doesn't work. If the client reconnect the MQTT-Server(VerneMQ) the ACLs worked well.
Is there a problem with the vernemq.conf?

The vernemq.conf description is:
set the acl reload interval in seconds, the value 0 disables
the automatic reloading of the acl file.

Default: 10

Acceptable values:
- an integer
vmq_acl.acl_reload_interval = 10
It looks like only use the vmq_acl.acl_file？How abort the redis acl reload？

Hi - is this still an issue?
If so could you provide a bit more information? It seems you're using both the vmq_acl plugin but you also mention redis which is available via the vmq_diversity plugin. Note that the vmq_acl plugin and the vmq_acl.acl_reload_interval has nothing to do with the behaviour of the vmq_diversity redis functionality.

Also note this quote from https://vernemq.com/docs/configuration/db-auth.html
Note: the database integrations will cache the ACLs when the client connects avoiding expensive database lookups for each publish or subscribe message. The cache entries are evicted when the client disconnects.

So this means ACLs are fetched from Redis when a client connects and are not refreshed until the client reconnects. If you need a different behaviour you'd need a custom plugin.

@larshesel ok,thanks


Fix of transaction size check during consensus

Signed-off-by: i1i1<EMAIL_ADDRESS>

Description of the Change
We already have ddos protection, but forgot to put it in consensus.
Benefits
We disable attack vector of flooding during consensus
Possible Drawbacks
Runtime instruction length check.
Jira Issue
https://jira.hyperledger.org/browse/IR-1038

I think the transaction byte size in not checked. @i1i1 are you planning to add it?

@eadventurous it is hard to check against it, as we have whole block there. We can parse it at first and then check whether number_of_tx_in_block * max_bytes_per_tx >= block_size, but that has downsides of parsing block.

We definitely need to check it, it can be simply done by iterating over tx the same as with instruction len

Block is always parsed at that moment in code, so I don't see the downside


DT-903: Change export button to link directly to terra-ui import page

Addresses
https://broadworkbench.atlassian.net/browse/DT-903
Instead of performing a two-step operation in the duos UI, use the new TDR import link to have terra-ui perform the TDR export step. The same APIs are called in both cases, so other than the UX differences there is no difference in behavior.
Summary
Video clip showing behavior, note that this is trying to export an azure dataset so the final step is blocked, but everything else is working correctly.
https://github.com/user-attachments/assets/859bb8dd-171e-4b4e-91ca-51961eded4b3

I am seeing the export link twice when there are multiple snapshots, so we still need to address that at some point:

At a minimum we probably want a bit of spacing between the links.

I can add spacing between the links, but there's not much room for multiple Exports, unless I make this column wrap across lines.


[BUG] Syntax of command arg with token and multiple (e.g. CLIENT LIST)

This is about command arguments specified in the JSON file with these properties:

a "token" property,
a "type" that is not "pure-token" and
"multiple": true
("optional": true in the examples below, but otherwise, it just affects the use of [ ] vs < >)

For arguments like this, the token is displayed as to be repeated for each argument.
Example: The CLIENT LIST has this argument in the JSON file:
        {
            "name": "client-id",
            "token": "ID",
            "type": "integer",
            "optional": true,
            "multiple": true,
            "since": "6.2.0"
        }

It is presented on the command web page like this:
CLIENT LIST [ TYPE normal | master | replica | pubsub ] [ ID client-id ] [ [ ID client-id ] ... ]

Expected behaviour
The expected behaviour is that ID only appears once, e.g.
CLIENT LIST [TYPE <NORMAL | MASTER | REPLICA | PUBSUB>] [ID client-id [client-id...]]

Additional
There's an exception: If the argument has "multiple_token": true, then the token should actually be repeated. An example is the SORT command, which is already rendered correctly on the website, with GET get-pattern repeated as a whole:
SORT key [ BY by-pattern ] [ LIMIT offset count ] [ GET get-pattern ] [ [ GET get-pattern ] ... ] [ asc | desc ] [ sorting ] [ STORE destination ]

Okay. I took some time on this. I think there are two distinct issues here. I'll all them "non-pure token multiples" and "< > in optional" for this issue.
non-pure token multiples
Given the criteria in the issue, I found seven commands that would be affected. With my changes, I get:

CLIENT LIST [ TYPE normal | master | replica | pubsub ] [ ID client-id [client-id ... ] ]
MIGRATE host port 〈 key | empty-string 〉 destination-db timeout [ copy ][ replace ][ AUTH auth | AUTH2 username password ] [ KEYS keys [keys ... ] ]
ZINTER numkeys key [ key ... ] [ WEIGHTS weight [weight ... ] ][ AGGREGATE sum | min | max ][ withscores ]
ZINTERSTORE destination numkeys key [ key ... ] [ WEIGHTS weight [weight ... ] ][ AGGREGATE sum | min | max ]
ZUNION numkeys key [ key ... ] [ WEIGHTS weight [weight ... ] ][ AGGREGATE sum | min | max ][ withscores ]
ZUNIONSTORE destination numkeys key [ key ... ] [ WEIGHTS weight [weight ... ] ][ AGGREGATE sum | min | max ]

The above 6 all compare closely to valkey-cli HELP <command>, the 7th doesn't look right:
MODULE LOADEX path [ CONFIG name value ][ [ CONFIG name value ] ... ] [ ARGS args [args ... ] ]
I need to look into MODULE LOADEX since it meets the criteria in this issue but CONFIG arguments aren't rendering as I expect, so there is something else. I personally don't find that as wrong as the repeating token in the other 6.
< > in optional
I have questions here. While these are in the website parser, I did notice that valkey-cli doesn't use < >. For example,
$ valkey-cli help client list

  CLIENT LIST [TYPE NORMAL|MASTER|REPLICA|PUBSUB] [ID client-id [client-id ...]]
  summary: Lists open connections.
  since: 2.4.0
  group: connection

This matches my parsers output, save for a bit of (irrelevant) spacing differences. I'm guessing the man pages do have [TYPE < NORMAL|MASTER|REPLICA|PUBSUB >].
IMHO, we should probably break this bit out into a new issue and harmonize the use < > across CLI, man pages, and website.
Side quest: debugging across all the commands
As part of the fix for this, I implemented a 'cheatsheet' page that has the syntax for all commands in alphabetical order on one single page. I was using this to compare changes as I made alterations to the parser and to avoid unintended consequences. Honestly, it's pretty handy for both this type of debugging and as a quick reference; I may break this out into a seperate PR.


Add Configuration.DotenvSpec Configuration.Dotenv.ParseSpec to other modules

The Configuration.DotenvSpec and Configuration.Dotenv.ParseSpec are not part of the other modules field in the test suite, so there are no tests in the Cabal package.

@CristhianMotoche would you be able to take a look at this one? Seems like something we should fix.

We could mark this as solved, since #9.

@CristhianMotoche Thanks.


Possible candidate derivation paths

Source: https://walletsrecovery.org

BIP 44: "m/44'/0'/0'/0" and "m/44'/0'/0'/1"
Coldcard: "m/48'/0'/0'/0" and "m/48'/0'/0'/1"
BIP 49: "m/49'/0'/0'/0" and "m/49'/0'/0'/1"
BIP 84: "m/84'/0'/0'/0" and "m/84'/0'/0'/1"
Samourai Whirlpool Deposit: "m/47'/0'/0'/0" and "m/47'/0'/0'/1"
Samourai Whirlpool Bad Bank: "m/84'/0'/2147483644'/0" and "m/84'/0'/2147483644'/1"
Samourai Whirlpool Pre-mix: "m/84'/0'/2147483645'/0" and "m/84'/0'/2147483645'/1"
Samourai Whirlpool Post-mix: "m/84'/0'/2147483646'/0" and "m/84'/0'/2147483646'/1"
Samourai Whirlpool Ricochet: "m/44'/0'/2147483646'/0",  "m/44'/0'/2147483646'/1", "m/49'/0'/2147483646'/0", "m/49'/0'/2147483646'/1", "m/84'/0'/2147483646'/0" and "m/84'/0'/2147483646'/1"
Sparrow: "m/86'/0'/0'/0" and "m/86'/0'/0'/1"

Implemented in #16.


persistent peripherals between calls to .startScanning() on mavericks

periphal objects stored in _peripherals are no longer overwritten when repeated picked up while scanning

@andySigler thanks! This address #85 on OS X 10.9


How to send Zencash from Transparent Wallet

How can I send Zencash from my ZENCash wallet? I get the message: "There are no addresses with a positive balance to send cash from!".
The "Transparent balance" shows balance, the 'Private (z) balace is zero.
Should I transfer from "Transparent" to 'Private"? How?
Thank you

If the ZENCash Desktop GUI Wallet shows transparent balance (in the Overview UI TAB) but the "Send cash" UI TAB shows no addresses with a positive balance to send cash from, maybe the balance (incoming transactions) are not confirmed. What does the "Own addresses" UI TAB show? Is the balance of addresses confirmed there?

@zennermac should be able to close this one. Sounds like unconfirmed transaction.


Using Test.py

Hi, I have two questions about the test.py file.

I'm trying to use test.py in the same way that I got image_demo.py working. I've noticed that test.py doesn't have an image directory argument similar to the 'img' argument in image_demo.py. How should I tell test.py what data to test?

!CUDA_VISIBLE_DEVICES=0 python test.py \   /content/ViT-Adapter/segmentation/configs/cityscapes/mask2former_beit_adapter_large_896_80k_cityscapes_ms.py  \   /content/ViT-Adapter/segmentation/release/mask2former_beit_adapter_large_896_80k_cityscapes.pth.tar  \   /content/drive/MyDrive/ColabNotebooks/ViT-AdapterContent/dataA/dataA/CameraRGB \
The 3rd argument is the directory where my data is.

Also I noticed that in the image_demo.py file, there is a --palette argument to choose the segmentation palette, but there isn't in the test.py file. If I added that to test.py, would I easily be able to add custom palettes, specific to the dataset of testing interest?

Hi, the test.py is a copy of https://github.com/open-mmlab/mmsegmentation/blob/master/tools/test.py.
You can see the document provided by segmentation for help.


fix: console log correct admin URL for tests

Description
Before:

After:

[X] I have read and understand the CONTRIBUTING.md document in this repository

Type of change

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[ ] I have added tests that prove my fix is effective or that my feature works
[ ] Existing test suite passes locally with my changes
[ ] I have made corresponding changes to the documentation

Thanks for the update @AlessioGr!


[BUG] Keep landing on the same planet.

[Please fill out the form below and delete the sections in square brackets after reading them]
Version of Advanced Rocketry

1.6.0 186

Have you verified this is an issue in the latest unstable build

[x] Y

Version of LibVulpes

0.4.2 68

Version of Minecraft

1.12.2

Does this occur without other mods installed

[x] Y

Description of the problem

Warp to a planet in a space station, land on it, warp to another one, land on it, same planet.

Fixed, but now I get the black skybox glitch again.


[AutoPR devtestlabs/resource-manager] Add devtestlabs/resource-manager/readme.typescript.md

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/4181

(message created by the CI based on PR content)


Cannot receive metadata without playing

In my use cases I need to process the metadata before considering the player "usable".
So, I do the following, with autoplay=false:
player.core.on(Clappr.Events.CORE_CONTAINERS_CREATED, () => {
  const playback = player.core.getCurrentPlayback();
  playback.on(
    Clappr.Events.PLAYBACK_LOADEDMETADATA,
    (em) => {
      player.pause();
    }
  );
});
player.load(source);
player.play();

But then the browser shows an exception:
Uncaught (in promise) DOMException: The play() request was interrupted by a call to pause().

And further investigating this error shows everytime one does:
player.pause();
player.seek(targetTime);
player.play();

Then how should the proper handling be done, with proper event handling ?
playback.once(Clappr.Events.PLAYBACK_PAUSE, () => {
  player.once(Clappr.Events.PLAYER_SEEK, () => {
    if (wasPlaying) {
      console.debug('must play - seek done');
      player.play();
    }
  });
  player.seek(targetTime);
});
player.pause();

But it manifests with the same error:
Uncaught (in promise) DOMException: The play() request was interrupted by a call to pause().

How can I do it correctly ?
I want to have the metadata received, but without autoplay

@iongion this error ...The play() request was interrupted by a call to pause(). is related to chrome >= 50 but this exception usually doesn't stop the playback.

I want to have the metadata received, but without autoplay.

We rely on video tag loadedmetadata event. I don't know if I clearly understood you but you could:
var playerElement = document.getElementById("player-wrapper");

var player = new Clappr.Player({
  source: 'http://www.streambox.fr/playlists/x36xhzz/x36xhzz.m3u8',
  baseUrl: '/latest',
  poster: 'http://clappr.io/poster.png',
  mute: true,
  height: 360,
  width: 640
});

player.attachTo(playerElement);

player.core.getCurrentPlayback().on(Clappr.Events.PLAYBACK_LOADEDMETADATA, function(e) {
  console.log('here', e)
})

player.on(Clappr.Events.PLAYER_PLAY, function() {player.pause()})

Yes, you are right, it was an m3u8, hence no metadata due to how hls.js works


firefox-esr-91-unwrapped: 91.7.0esr -> 91.7.1esr

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for firefox-esr-91-unwrapped is: "A web browser built from Firefox Extended Support Release source tree"
meta.homepage for firefox-esr-91-unwrapped is: "http://www.mozilla.com/en-US/firefox/"
meta.changelog for firefox-esr-91-unwrapped is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/azbrcfyma6vfqfvq86dcs2k267d2aq8z-firefox-esr-unwrapped-91.7.1esr/bin/firefox had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/azbrcfyma6vfqfvq86dcs2k267d2aq8z-firefox-esr-unwrapped-91.7.1esr/bin/.firefox-wrapped had a zero exit code or showed the expected version
0 of 2 passed binary check by having a zero exit code.
0 of 2 passed binary check by having the new version present in output.
found 91.7.1esr with grep in /nix/store/azbrcfyma6vfqfvq86dcs2k267d2aq8z-firefox-esr-unwrapped-91.7.1esr
found 91.7.1esr in filename of file in /nix/store/azbrcfyma6vfqfvq86dcs2k267d2aq8z-firefox-esr-unwrapped-91.7.1esr

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

6 total rebuild path(s)

3 package rebuild(s)

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

First fifty rebuilds by attrpath
firefox-esr-91-unwrapped
firefox-esr-unwrapped
firefoxPackages.firefox-esr-91

Instructions to test this update (click to expand)

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

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/azbrcfyma6vfqfvq86dcs2k267d2aq8z-firefox-esr-unwrapped-91.7.1esr
ls -la /nix/store/azbrcfyma6vfqfvq86dcs2k267d2aq8z-firefox-esr-unwrapped-91.7.1esr/bin

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

3 packages built:

firefox-esr
firefox-esr-91-unwrapped
firefox-esr-wayland

Maintainer pings
cc @mweinelt for testing.

No release notes or advisories yet.

They were 404 a couple hours ago.

98.0.1 over in #164126.


[rhoai-2.8 ] Cherry-picks - CVE fixes and crashloop fix

What this PR does / why we need it:
Cherry-pick of:

https://github.com/opendatahub-io/kserve/pull/260
https://github.com/opendatahub-io/kserve/pull/265

/lgtm


Breaks superforms internal sate restore on soft-reload, and on hard-reload with snapshots enabled

Describe the bug
Superforms internal state is not being restored when using snapshots, and also not restored on soft refresh.

Superforms state not restored when soft refreshing.

This behaviour is with and without snapshots

Superforms state not restored when soft or hard refreshing.

This is behaviour is with snapshots

Existing behaviour:
clone https://github.com/ciscoheat/superforms-examples/tree/tutorial-valibot (currently at 2414332)

Add <SuperDebug data={$formData} /> to the bottom of the page

pnpm upgrade (or whatever package manager)

Run the project

Enter something in the email field

Soft refresh with cmd+r

Data is restored in superforms state

Hard refresh (cmd+shift+r)

State is (correctly) reset

Enable snapshots
export const snapshot = { capture, restore };
Do the same with hard refresh, state is restored.
Reproduction
Install formsnap
pnpm upgrade or whatever to get version numbers in line with my environment below

{#if $message}
{$message}
{/if}

<form method="POST" use:enhance>
	<Field {form} name="name">
		<Control>
			{#snippet children({ props })}
				Name
				<input {...props} type="test" bind:value={$formData.name} />
			{/snippet}
		</Control>
		<Description>Use your company email if you have one.</Description>
		<FieldErrors />
	</Field>

	<Field {form} name="email">
		<Control>
			{#snippet children({ props })}
				Email
				<input {...props} type="test" bind:value={$formData.email} />
			{/snippet}
		</Control>
		<Description>Use your company email if you have one.</Description>
		<FieldErrors />
	</Field>

<button>Submit</button>

</form>

	💥 Created with Superforms for SvelteKit 💥

<SuperDebug data={$formData} />

Run the project

Enter something in the email field

Soft refresh with cmd+r

Data is not restored in superforms state <---- problem

Hard refresh (cmd+shift+r)

State is (correctly) reset

un-comment out snapshot

hard refresh

state is not restored <---- major problem

Logs
No response
System Info
System:
    OS: Linux 6.6 Debian GNU/Linux 11 (bullseye) 11 (bullseye)
    CPU: (10) arm64 unknown
    Memory: 2.13 GB / 7.66 GB
    Container: Yes
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 22.12.0 - ~/.local/share/pnpm/node
    npm: 10.9.0 - ~/.local/share/pnpm/npm
    pnpm: 9.15.0 - ~/.local/share/pnpm/pnpm
  npmPackages:
    @sveltejs/kit: ^2.11.1 => 2.11.1
    formsnap: ^2.0.0 => 2.0.0
    svelte: ^5.13.0 => 5.13.0
    sveltekit-superforms: ^2.21.1 => 2.21.1

npm notice
npm notice New patch version of npm available! 10.9.0 -> 10.9.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.9.2
npm notice To update run: npm install -g<EMAIL_ADDRESS>npm notice

Severity
blocking all usage of Formsnap

let formState: ReturnType<typeof capture> | null = null;

function do_capture() {
  formState = capture();
}

function do_restore() {
  if (formState != null) {
    restore(formState);
  }
}

<button onclick={do_capture}>capture</button>
<button onclick={do_restore}>restore</button>

This works, so I guess it is on initial initialisation

Would you mind pushing your code to GitHub and dropping a repo link so I can debug?

https://github.com/Mardoxx/formsnap-issue/

Initial

On restore

SuperForm internal state seems wrong.

It seems that it is the html input component that is messing things up if I put in
<Field {form} name="email">
	<Control>
		{#snippet children({ props })}
			Name
			<input {...props} type="text" bind:value={$formData.email} />
		{/snippet}
	</Control>
	<Description>Use your company email if you have one.</Description>
	<FieldErrors />
</Field>

above the form, it breaks things, if I remove the input, it doesnt't exhibit the bad behaviour

<button onclick={() => console.log($formData)}>dump</button>
When SuperDebug reports that the form is in an invalid state, dumping it shows the data to be correct.
This might suggest an issue with SuperDebug component, although I think it is still worth investigating why this behavior has changed. This library is a wrapper around superforms which should cause no side effects on its functionality, this discrepancy is unexpected.
It’s also possible that this issue could lead to bugs in more advanced use cases involving superforms. Investigating it now might help prevent potential problems down the line.

I wonder if it has something to do with this? https://svelte.dev/docs/svelte/bind#input-bind:value
Can you reproduce it without using formsnap at all? If so then this is an issue for sveltekit-superforms rather than formsnap.

Without formsnap it works correctly. It is when the input element is
wrapped with formsnap components that this behaviour breaks.
On Sun, 15 Dec 2024 at 16:35, Hunter Johnston @.***>
wrote:

I wonder if it has something to do with this?
https://svelte.dev/docs/svelte/bind#input-bind:value
Can you reproduce it without using formsnap at all? If so then this is an
issue for sveltekit-superforms rather than formsnap.
—
Reply to this email directly, view it on GitHub
https://github.com/svecosystem/formsnap/issues/205#issuecomment-2543940190,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAB2QMLRB3FKLCRGIBFODVT2FWVWTAVCNFSM6AAAAABTTYNKQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBTHE2DAMJZGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

https://github.com/user-attachments/assets/d22ba849-700a-4728-8d6c-a7da2cec976e
I apologize, I'm having a difficult time following what is and isn't working as expected. This is the behavior I get when putting the component in runes mode (replace export let data with let { data } = $props()).
Is this not the expected behavior?

Interesting.. strange, this is after putting it in rune modes
https://www.loom.com/share/d2a924f426a14caca659df3a8e70660c

Ah.. it's a firefox bug.

Here it is without formsnap (still in firefox), and it works correctly
https://www.loom.com/share/2e7f6cdf4aae41e6a3600f6b772f3fc8

{#if $message}
{$message}
{/if}

<form method="POST" use:enhance>
	<input type="text" bind:value={$formData.name} />
	<input type="text" bind:value={$formData.email} />

<button>Submit</button>

</form>

	💥 Created with Superforms for SvelteKit 💥

<SuperDebug data={$formData} />

Interesting... I'll take a closer look at this with firefox as soon as I get the chance!


Fix OCP-UPI issue #68

I was just looking around , hope you don't mind me making comments :)

I was just looking around , hope you don't mind me making comments :)

Of course not:) Thanks for your comments, it helps us a lot!

Thanks for this PR, good job!


Revise dev-oriented onboarding instructions

#16 is about user-facing instructions. I'm using this issue to centralize developer-facing onboarding documentation.
Suggestions from the retreat (list will be edited continuously):

[ ] rail/docs/source/overview.rst should include an introduction to stages and pipelines (also remove outdated content there and to check that the descriptions of creation/estimation/evaluation are accurate)
[ ] mamba not conda so it's simpler
[ ] rail --help, rail-nb --help [path] (suggest running on some notebooks to confirm it works)
[ ] explain why the instructions are what they are (pip vs. conda)
[ ] explain the command-line tool (purpose, what this gives you) rather than just jumping into the commands
[ ] change pip install to pip install -e .
[ ] instructions to get around NERSC ceci path issue
[ ] install local kernel to notebook server instructions to introduce rail-nb command (insert this link)
[ ] add a link to NERSC-specific instructions
[ ] add a link to a git cheat sheet

Some notes I took for running rail pipeline on NERSC
Install rail:

module load python
git clone https://github.com/LSSTDESC/rail.git
cd rail
mamba env create -f environment.yml -n [env]  # or mamba env create, which is much faster
conda activate [env]
pip install .
rail clone-source --package-file rail_packages.yml
rail install --package-file rail_packages.yml --from-source

add the rail kernel to jupyter:

conda activate [env]           # . ./cenv/bin/activate in case of virtualenv
([env])$ conda install ipykernel
([env])$ ipython kernel install --user --name=<any_name_for_kernel>
([env])$ conda deactivate

If you run into issue with ceci or pipeline.run() in jupyterlab, it is a path issue with the jupyter.
you need to ssh into ssh<EMAIL_ADDRESS>, and run

module load python
conda activate [env]
Open your your_rail_pipeline.yml, add “name: local” under the site section. Then run
ceci your_rail_pipeline.yml

Additional changes we may want to make:
[ ] separate mac-specific instructions
[ ] mention mamba is preferable over conda (mentioned in Rail Retreat)
[ ] Add an additional “check that the installation worked” section (as this is applicable after following any of the installation instruction sections) about running the two lines (wrote this in the RR - what are the two lines?)
[ ] Add line: struggling to figure out what repo some code is from? these ides will let you command + click to jump around repos: (list IDEs)
More abstract:
[ ] Something explaining the philosophy of rail, eg, “the usual way you pass things around in rail is handles, not the data itself” with a little explanation that yeah, you might be using toy data in notebooks, but this is built to handle zuntz level pipelines as well.

I've created a PR that addresses all but two of the requests in the first comment. If I could get some help from someone about what to include for the two NERSC-related requests, I would really appreciate it. I'm not familiar with what they are referring to.


add builtin jobs command

show the following job information

job id
command name
command argument
pid

currently Job dose not maintain command name and arguments,
so get these information via procfs (Linux only)

related to #295

in interactive mode, capture command line as string and set to job table


Add option to copy ASCII

Kinda messy workaround but it's supposed to work

Works for me! I'm going to

Works for me! I'm going to implement this as an option along with txt download, so users can pick whichever they prefer.


Fixed mistake in last example layout

[x ] I have read freeCodeCamp's contribution guidelines.
[x ] My pull request has a descriptive title (not a vague title like Update index.md)
[x ] My pull request targets the master branch of freeCodeCamp.
[x ] None of my changes are plagiarized from another source without proper attribution.
[x ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@rosiline Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


CARDS-2177: In the Heracles S3 exporter, the "Failed to perform the nightly export" message should be logged for all types of failures that occur during the data export task

The goal of this Pull Request is to ensure that the error Failed to perform the nightly export is logged if any exception is thrown during S3 data export. Before this, the Failed to perform the nightly export error would only be logged if a com.amazonaws.AmazonServiceException was thrown inside the output method. This missed many failure cases - for example, if a network error prevented a connection from being made between CARDS and the S3 bucket, a com.amazonaws.SdkClientException and not a com.amazonaws.AmazonServiceException would be thrown and thus the Failed to perform the nightly export error would not be logged.
Testing Instructions

Build this (CARDS-2177) branch, including a Docker image, with mvn clean install -Pdocker
cd compose-cluster
python3 generate_compose_yaml.py --dev_docker_image --composum --cards_project cards4heracles --s3_test_container --oak_filesystem
docker-compose build && docker-compose up -d
Visit http://localhost:8080 and login as admin:admin
Create a new Demographics Form and an associated Patient
Visit http://localhost:8080/Subjects.s3push
Run docker-compose logs cardsinitial - the Failed to perform the nightly export error should be logged because the specified uhn bucket does not exist in the MinIO container.
Stop the MinIO container with docker-compose stop s3_test_container
Visit http://localhost:8080/Subjects.s3push once again
Run docker-compose logs cardsinitial - the Failed to perform the nightly export error should be logged because the cardsinitial container could not send a HTTP request to the minio host.
Stop and clean up with docker-compose down && docker-compose rm && docker volume prune -f && ./cleanup.sh
To verify that Failed to perform the nightly export is logged if an exception is thrown in the getChangedSubjects method, run instructions 2-7 on a build of the CARDS-2177_getChangedSubjects_fail branch.
To verify that Failed to perform the nightly export is logged if an exception is thrown in the getSubjectContents method, run instructions 2-7 on a build of the CARDS-2177_getSubjectContents_fail method.

Step 8:

Step 11:


[ch6929] add support for bulk queryAll opperation

yeah, this is much needed

Hey, sorry this didn't get reviewed in time, we aren't doing feature work on master and this is already supported in jsforce v3


Specialization Info is not complete for Enchanting goods

CraftSim Specialization Info window always shows the same 3 entries and warning "SpecInfo Work in Progress". Please fix this.

This is because its just not implemented for enchanting yet, and no bug!


add automatic deploy support

add automatic deploy support
update sphinx version to solve docs generation error

Current coverage is 84.29% (diff: 100%)

No coverage report found for master at 41b57b6.

Powered by Codecov. Last update 41b57b6...6a1aff3


Updated the top.css for a larger font

I have created a pull request for medium font....https://github.com/privly/privly-applications/pull/337
But if you consider it to be small , then i have created this pull request keeping in mind the font-size to be a little larger.
However if the community wants to keep the font-size to be somewhat smaller than this....please let me know and please review this....:)
#317

Closed for duplicate #337.

So should i reference this commit to the original pull request....

You commented on a pull request, not a commit. I don't understand the question.


Inline values passed to http:Caller->respond() method get compilation failed due to type ambiguity

Description:
type Person record {|
    int id;
    string name;
|};

type RetEmployee record {|
    readonly int id;
    string name;
|};

type PersonTable table<RetEmployee> key(id);
type PersonTableArr PersonTable[];

resource function get callerInfo17(@http:CallerInfo {respondType: Person}http:Caller abc) returns error? {
    error? a = abc->respond({id:123, name:"hele"}); // type is considered as map<json>
}

resource function get callerInfo32(int xyz, @http:CallerInfo {respondType: PersonTableArr} http:Caller abc) {
    PersonTable tbPerson = table [
        {id: 1, name: "John"},
        {id: 2, name: "Bella"}
    ];
    checkpanic abc->respond( [tbPerson, tbPerson]); // type is considered as table<map<json>>[]
}

http:Caller->respond() method param type is
public type ResponseMessage Response|string|xml|json|byte[]|int|float|decimal|boolean|map<json>|table<map<json>>|
                            (map<json>|table<map<json>>)[]|mime:Entity[]|stream<byte[], io:Error?>|();

Describe your task(s)
This works fine when you pass a particular type to the method
Person p = {id:123, name:"hele"};
error? a = abc->respond(p);

I think the issue here is that if a type is not explicitly specified, it'll infer the type to be the type it's compatible with in the param's type. In this case, map<json>. So I think this behaviour is correct. If you need to be explicit about the type inferred for the inline value, a cast can be used. @hasithaa @MaryamZi please verify.

I think the issue here is that if a type is not explicitly specified, it'll infer the type to be the type it's compatible with in the param's type. In this case, map<json>. So I think this behaviour is correct. If you need to be explicit about the type inferred for the inline value, a cast can be used. @hasithaa @MaryamZi please verify.

Yeah, this is the expected behaviour. The compiler does not know of/make use of any additional restrictions the library has.
If you really want to allow this maybe the specific validation can do some additional checks for constructor expressions (mappings, lists, tables) before logging the incompatible respond method argument type error.

I'm not sure I had the sufficient additional details to figure out the exact type when the values is passed inline to improve the error message. As mentioned in the description, the record which passed inline was considered as type map<json>. Also, matching the record structure with the param values could cause a significant delay when the number of fields are higher.
I think it makes sense to either cast the value or pass a typed value.

@chamil321, since this is the expected behaviour, shall we close this issue?

@chamil321, since this is the expected behaviour, shall we close this issue?

+1


Support & unit test for parsing effective POMs with multiple projects

Merging anyway, integration testing has an unrelated issue, may require updates to git handling or ci caching to fix. Will do that separately.

Filed https://jira.gibeling.com/browse/G2-1570 to fix the CI tests.


Max number of docs is arbitrarily limited to 20

We should either provide a 'load more' option or let the user configure how many docs they want to retrieve

Moved to new cosmosdb extension
https://github.com/Microsoft/vscode-cosmosdb/issues/4


When a package is pushed, make the "edit" less obvious

When a package is pushed, make the "edit" less obvious on the verification step. We want to encourage people to use a proper NuSpec instead of editing in the UI.

Edit feature was removed.


Server: completePurchase inconsistency with other drivers

Currently, in order to genuinely complete the purchase of a SagePay Server transaction, the calling code needs to call not only $gateway->completePurchase() but also $response->confirm(). This is slightly annoying, as it means the behaviour and usage is different to other drivers, and the beauty of OmniPay is having drop in replacement drivers, as far as possible.
As far as I can see, there wouldn't be any major downsides to ServerGateway handling the confirm process, thereby negating the need for extra calling code. Does anyone have any thoughts on this (I'd be happy to provide a PR for the changes)?

My suggestion - so that it doesn't break any existing usage - is that if a returnUrl parameter is passed to $gateway->completePurhase(), it calls $response->confirm() automatically.
Eg:
$params = [
    'transactionId' => $ourId,
    'transactionReference' => $gatewayId,
    'returnUrl' => $customerReturnUrl
];
$response = $gateway->completePurchase($params)->send();
// because 'returnUrl' was set, completePurchase called confirm itself

Hi @coatesap, do you have any examples showing how you would like the callback process to work?
As it stands now, $response->confirm() is an end-point - it responds to SagePay and exits. That should only be done if the callback handler is happy with the result it gets from $gateway->completePurchase(), and has had an opportunity to log the details it gets from that into storage and possibly queued up for handling by the merchant application. I'm not sure how those two steps can be merged, given that the merchant site callback handler needs to process the result and make a decision on what is returned to SagePay (confirm, invalid, or error)

You may also want to call $response->invalid() with a return URL. This would be the case if the security token (the signature) does not validate, or the amount being expected does not match the amount being authorised. This can arguably be done within $gateway->completePurchase() , so long as there is a way to log this in the application; the application needs to know what was sent back to SagePay, so it knows whether the transaction notification was valid or not.
Perhaps if the confirm/invalid/error methods did not exit the script, leaving that up to the application after it has done all its logging, that would work. And if those methods keep a flag when a result has been "sent" (i.e. echoded) so calling those methods a second time does not output a second time, would help in migration.

So the problem is possibly that $response->confirm() and friends exit the script to make sure no further output is generated. $gateway->completePurchase() should probably generate the result (i.e. return the three lines of text to SagePay), BUT we don't want that exiting the script because the result needs to be logged by the application.
I think that could work, by removing confirm/invalid/error (or changing them to they do nothing more than just exit, for backwards compatibility) and generate (i.e. echo) the real return code in $gateway->completePurchase(). What do you think?

I think this would also help with Issue #16 in which an invalid signature results in an exception being raised and some clumsy code being needed to handle it. Instead of raising an exception, it could just echo the "error" return text and return an error status (not an exception) for logging. I think you may be on to a winner here :-)

@judgej - thanks for those thoughts and suggestions. I have realised now that whichever way this is done, it's not ideal. If we remove the exits, then this comes with it's own non-standardness in that the calling code needs to know whether to output something or redirect the customer's browser (if it's a callback from a gateway where the customer redirect is one and the same thing)...
I'll give this a little more thought!

In this particular case, there is never a redirect. The notification callback must always return something: OK (confirm), INVALID or ERROR, plus an optional message. These are just echoed out as a couple of lines of text. The only thing that the callback should then do is to exit, after it has done its logging etc. but no other headers, redirects or content should be sent/returned.
How this compares to other gateway callbacks, I'm not sure. So far as I know, all the callbacks just return text and exit. Some may modify the HTTP response code though. They will all have their own formats: SagePay needs three (or two) lines of text, Authorise.Net SIM needs a HTML page with an embedded redirect returned, Helcim wants multiple lines of name:value pairs. They are all different, just to mess with our heads, but the underlying action is: return text, exit, done.

just came across the discussion here that is loosely relevant:
https://github.com/thephpleague/omnipay/pull/215
It argues that complete*() should not be used in the callbacks at all, which is something I've always felt too, just because it feels unintuitive to me. Both this issue and that PR concern making the callback handling more consistent between the drivers, and more intuitive across the board.

Good find - I think that's exactly it. Gateway callbacks/notifications need a bit more thought at the generic omnipay level, so that regardless of their style of operation, they can be handled in a consistent fashion.
With SagePay Server, because of the need to exit with a response to SagePay, we're always left with a need for it to be a two-stage operation. I'm not now so keen on my original proposal, as this would really just create the need for another method - something like ->exitIfRequired() (which would again be non-standard unless it was implemented in the common layer).
Regarding the redirects following a callback - I should have been clearer - these take place in my own controller. This is completely generic callback handling code that currently serves a number of different gateways. It is how I've implemented it in our project, but I imagine anyone else interested in doing the same thing would probably implement it in a similar fashion.
Pseudo-code for speed:
// callback received from gateway
// (might be behind-the-scenes paypal ipn style,
// or customer browser redirect, eg. barclays epdq)

// try to identify the transaction to which this relates
// (either from the URL or the session)
$params = ['stuff'];

// let the driver do its thing
$response = $gateway->completePurchase($params)->send();

// update our database with the results, etc
$this->handlePaymentResult($response, $params);

// our current non-standard bit for SagePay
if (method_exists($response, 'confirm')) {
    $response->confirm($customerReturnUrl);
}

// now, the majority of gateways won't care what happens now,
// so assuming this might be a customer browser redirect style callback,
// send them off to a suitable completion url
$this->redirectToCompletionPage($customerReturnUrl)

I think actually, just standardising at the omnipay common level what that final method is called would probably be sufficient.

I see - one handler for returns from the gateway, whether in-session or an out-of-session callback.
I tend to treat these as two separate things, since the callback does not share a session, so there are steps involved in pulling the transaction data from storage, which is is not (necessarily) needed when it is a simple gateway return. I can see the value in either approach.

Just to expand this a little, when a callback is used (SagePay Server, Authorize.Net SIM et all) then the first thing the callback handler needs is the ID that it will use to identify the partially-complete transaction record that it has stored. None of the drivers help you do this at present - they leave you to look in the $POST or $REQUEST super-globals and to have the knowledge of what the ID is for each particular gateway.
So a helper method to get the ID, I believe would be useful. You still need to know which gateway driver to load, and maybe a parameter on the callback URL would indicate that (unless there is scope for some kind of auto-detect, based on what has been posted), but then getting the ID would be a consistent $gateway->getStorageId() or something like that.
SagePay will always send the vendor transaction ID with the callback, but Authorize.Net does not, and you need to create your own custom field to do that (or do as the current driver does and squeeze it into the invoiceId, which I don't like, but I suspect that choice has been inherited from the SDK - still wrong though IMO - an invoice and a payment are two different things). Anyway, there are perhaps some decisions to be made on which fields to use and which custom fields to be "owned" by OmniPay.

I think your approach of defining separate URLs for gateway callbacks and customer returns is a good idea, and allows the controller code to treat the request appropriately.
In that case... we probably could remove the exit from confirm() and allow completePurchase() to call confirm() itself. However, that would break all existing integrations!

Yes, it would be a BC breaking change. But for OmniPay V3 it would be acceptable, with some documentation on how the behaviour differs and what kind of changes are needed for it to work. Maybe we need a "V3" label for these issues, or perhaps a V3 milestone? Each major version gives us a chance to refactor some of these design decisions, so we should make the most of it.

BC Breaks can be allowed fro V3, and I would assume there will be a few of them. I'll be writing up an upgrade guide to go with the release of V3, though, so it shouldn't be an issue there.

Excited :-)

After much discussion, I think essentially we're saying that SagePay Server's implementation is not quite right, and it should be using notifyUrl rather than returnUrl.
This would mean in this line: https://github.com/thephpleague/omnipay-sagepay/blob/e7d287e42ad0e4adddd1d1419af5b086f6a3897d/src/Message/ServerAuthorizeRequest.php#L25
in v3 we would change it to $data['NotificationURL'] = $this->getNotifyUrl(); and make sure the notifyUrl value was always validated.
In completeAuthorize we would then call the current confirm code, and let the calling code handle the exit;. @judgej - does that sound like a fair summary?

On the notifyUrl vs returnUrl, I added a change to AuthorizeNet to make the same change. It works for either at the moment, so is BC, and returnUrl can be removed for v3.00. That allows for some incremental changes. So yes to that.
The other one is a little more complicated. Here is an example notify handler for SagePay Server. Notice towards the end that once we know whether the authorisation was successful or not, we still need to be able to perform some action for the merchant site to register the result in the transaction storage. This happens between send() and confirm(), so we can't have send() exiting the script without the handler being able to do something with that result.

Regarding notifyUrl vs returnUrl - glad I'm not the only one who's spotted that in a few different drivers and thought it needed changing!
Regarding how the notify handlers work - my initial thought was that if we said that all OmniPay notification handlers followed the same pattern of calling completeWhatever(), storing the result, then exiting, this would allow the completeWhatever() method to potentially write some kind of response to the buffer, which would then get output when the handler exited. I'm not sure if this is too prescriptive though.

Yes, I can see how the HTTP message can be pushed out, then your notify handler can record the results/approve the invoice/push to a queue for processing etc. and then simply exit without outputting anything else.
For SagePay, you may want to choose the return URL depending on the result, but we can handle that with multiple (and optional) return URLs there - one for success, one for failure, and one for error. That would also get rid of this dirty hack since we won't need to recreate the response object to fire out the error response - it could do that itself, then raise the exception, then the notify handler could log it and exit.
I like that idea.

What do you think about the notify handler in Authorize.Net?
https://github.com/thephpleague/omnipay-authorizenet/issues/22#issuecomment-119265616
This handler does not expect data like some gateways, but a full HTML page that it then displays to the user from its own domain. That page can be the final "thank you" page with a link back to the merchant site, or can contain a HTML (meta, JS) redirect back to the site. If using DPM, then you must have a redirect if you want to catch form errors and give the user another chance to re-submit the payment form.
Anyway, there is a $response->redirect() helper method in the completeResponse to do a simple redirect for you, or you can provide your own HTML page from your application. It could do a $response->redirect() automatically, as described above, but if you want to provide your own HTML page, then that has to be something that can be switched off (or mess around with output buffers to catch the default redirect page and throw it away - I guess that might be okay for people who want something special, and the built-in redirect as the default).

Fixed in PR #69 - use the acceptNotification handler, pointed to by the notifyUrl when creating the initial transaction.

Hi @judgej, sorry to return to this after so long. I noticed in PR #69 that you've marked completePurchase() as deprecated. Is this meant just for the SagePay driver, or are you saying that it should be deprecated across all drivers/gateways?

Hi @coatesap - it was just for this driver. It will remain for OmniPay 2.x but won't be needed in 3.x. I'll explain.
The very early OmniPay drivers used a completePurchase() to process parameters POSTed (or GET parameters) with a user return from an external gateway. So the user goes off to the external gateway, and they come back with some data that indicates the result of the transaction. It would normally be encrypted or hashed to make sure it does not get manipulated by the user, and the completePurchase() function would do the decrypting or check that hash.
Later there came gateway drivers with a back-channel. The results went direct from gateway to merchant site. To capture those results, the completePurchase() function was utilised because it seemed like the best fit. This is what the Sage Pay Server driver does. However, it was not an ideal fit, since completePurchase() was designed with a browser request in mind.
So later OmniPay introduced acceptNotification() which is solely for back-end server-to-server notification requests. I introduced that function to Sage Pay Server to use instead of completePurchase() for the Sage Pay Server driver. It also fixes a few flaws in the original completePurchase() (e.g. it could not response to an error condition if the hash failed because it threw an exception instead of returning the message to response with). I didn't want to change that functionality of completePurchase() as it would be a BC break. So the idea was to move to the acceptNotification() and let completePurchase() fade away.
Now completePurchase() still has its place where designed. For example, it can be used to catch 3D Secure codes POSTed back to the merchant site with the end user on return from the remote bank (or in same cases, on return from the payment gateway that wraps 3D Secure its own iframe-based page - e.g. PAYONE).
So personally I think it should be deprecated across all drivers where it is used as a back-channel POST/GET parser, but it does still have its place where used as a front-end POST/GET parser. However, there is no official policy on changing this across the board on any kind of time frame.
Does that make sense?

Just a note on the difference between the back-end and front end handlers: on the back end, the notification handler normally has full control of the server request - it parses what comes in and returns the result. It is the kind of thing that would go into HTTP middleware, and would return its own HTTP response message. It could go into a controller, but not on a path any user would interact with.
The front-end handler on the other hand still accepts the incoming HTTP request, but does not control the response in any way. It just provides some data for whatever calls it. It may also be put into middleware, but it is probably better suited to going into a controller where the controller decides what to do and where to send the user to next.

Thanks @judgej, that's useful, and makes perfect sense based on what we previously discussed. My only concern is that aside from us, other driver developers may not be aware of what the intention is (or even the existence) of acceptNotification(). Would it be possible to add a condensed version of your previous comment to the docs, and mention it as an optional method in the interface?
The application that I work on relies on being able to easily switch between different payment drivers, and so I'm very keen to see as much consistency between them as possible!

Okay, on my list for when I get half an hour idle after Christmas.

@coatesap Does this note cover this enough:
https://github.com/thephpleague/omnipay/pull/417
The overall descriptions of the difference between the complete* messages and the acceptNotification handler, I think, is great already. This note just acknowledges that that there is some cross-over still for historical reasons, but that is being addressed.


Add DataV

Vue large screen data display component library.
https://github.com/jiaming743/DataV

@jiaming743 Please create a PR if this is still relevant


Cherrypick 3640 for release 1.27

Summary
Cherrypick for 3640 into 1.27 due to automatic cherrypick failure

Was this a manual cherry-pick?

Was this a manual cherry-pick?

Yes


Fix a bug that unable to intercept requests using plugins

See issue #326

Current coverage is 84.63%

Merging #328 into master will decrease coverage by -0.21% as of 0e743ca

@@            master    #328   diff @@
======================================
  Files           13      13
  Stmts          640     651    +11
  Branches         0       0
  Methods          0
======================================
+ Hit            543     551     +8
  Partial          0       0
- Missed          97     100     +3

Review entire Coverage Diff as of 0e743ca

Uncovered Suggestions

+2.46% via Source/Result.swift#53...68
+1.69% via Source/Result.swift#38...48
+1.23% via ...ource/Response.swift#75...82
See 7 more...

Powered by Codecov. Updated on successful CI builds.

Btw, I suppose if you can create the PR based on another branch instead of master, that would be great. :tada:

Close this PR,  create a new branch in my local repo and then create a PR?

It seems that I forget to make the conformance to RequestType of NSURLRequest public.

@wangshengjia I've used my local repo in a new project and everything works fine.

Ah... my bad.. I didn't see it. It should compile without any error then.
On the other hand.. it seems to that you can not just fake methods without implementing the details. It turns out this solution will likely break the implementation of willSendRequest in CredentialsPlugin
Why not just set startRequestsImmediately to false by default and call resume() manually.

Really cool PR, thanks! I don't mind it coming from master at all, personally. Could you add an entry to the changelog when you get a chance?
Thanks again! 🎉

@wangshengjia Credential is the missing part~

@mrahmiao Great, thx

@ashfurrow Alter the changelog and make a PR?

You can update the changelog, commit, and push to this branch and github will add it to this pr ⭐

It seems that separating two kinds of plugins (ordinary plugins and plugins used to change requests) is a much more appropriate way to solve this bug since almost no related point is exposed by Alamofire.


Simulation engine

Hi! I've just discovered your project. I'll watch your videos. I share with you a portage of their simulation engine https://github.com/Lecrapouille/OpenGlassBox I hope that can help you or give you ideas.

Very interesting! Thanks for sharing.


fix: using ...attributes without passing attrs fails

Example:
A component template with:
<div ...attributes></div>

and this invocation:
<MyComponent />

fails with:
Uncaught TypeError: Cannot convert undefined or null to object
    at Function.keys (<anonymous>)
    at Object.create (runtime-polyfill.js:99)

This invocation succeeds:
<MyComponent class="foo" />

Done!

Thank you!


Fixed issues with docs , particularly extending OpenAPI schema

The example in the docs do not work because the defualt prefix is not specified. It may confuse a lot of begginers and thats why I modified both the en docs as well as the python code for the same.

Thanks for your contribution! This was updated/improved in https://github.com/tiangolo/fastapi/pull/1596 , and the openapi_prefix parameter is no longer needed :tada:
The new docs are here: https://fastapi.tiangolo.com/advanced/extending-openapi/
And the updated docs about root_path, that previously required the openapi_prefix parameter, are here: https://fastapi.tiangolo.com/advanced/behind-a-proxy/
This is available in FastAPI version 0.59.0 :tada:
So I'll close this now, but thanks for your effort! :coffee:


Increase primary key field lenght not allowed for Appsource

AL Extension Version: All

Server Version: All.

If I Increase the field length of a primary key when I publish in Appsource in first validation I get this error message:
"Error AS0080: Field 'Item No.' has changed from 'Code[10]' to 'Code[20]' in table or table extension 'TIP SILICIE Item Pack. Type'. Decreasing the length of a field is not allowed. For fields used in the primary key, the field length cannot change.."
Notice that the text says "Decrease" but we are Increasing the length.
Already reported in ##4933. But nobody has answered it since 2019. No problem if you leave only one issue, and delete the mine one, but please answer us or tell us where we must post this issue, for getting some answers.
Thank in advance.

Even microsoft had to introduce a new table to increase the primary key fields of cross-references (now they are called item references). So I don't think you can do that as customer.

Even microsoft had to introduce a new table to increase the primary key fields of cross-references (now they are called item references). So I don't think you can do that as customer.

Thank you @dannoe .
You are right. I thought about that and closed the issue before your answer. The problem was the lack of answer in the previous issue #4933 .
Best regards, thank you again for your fast answer.


odo push recreates the pod if scaled to 0

What type of PR is this?
/kind bug
What does this PR do / why we need it:
Refer issue being fixed
Which issue(s) this PR fixes:
Fixes #5041
PR acceptance criteria:

[ ] Unit test

[x] Integration test

[ ] Documentation

[ ] I have read the test guidelines

How to test changes / Special notes to the reviewer:
Refer issue description of original issue for steps to test changes.

/lgtm
/approve

/cherrypick v2

/cherrypick v2


Add keyboard shortcut while reviewing

Three keyboard shortcuts are implemented. While reviewing, users can strike "r"/"R" to label "relevant", "i"/"I" to label "irrelevant", and "u"/"U" to undo labeling. This feature can be toggled on/off in the settings dialog.

Can you add some documentation on this feature? Somewhere in the ReadTheDocs will do. (maybe we have to make a new section "Keyboard shortcuts")

Is there any documentation on other features in the settings dialog in the ReadTheDocs? Shall we have a new section "Customize settings" at the end of the quick tour in the ReadTheDocs?

I'm more thinking about a small article on keyboard shortcuts only. There is nothing for the other options at the moment.
Maybe we should work on something like this:

Features

Keyboard shortcuts
Undo
Change text size

But let's start with the keyboard shortcuts.

So nice!!!
I agree we carefully need to think about the text in the settings menu, maybe involve Martijn?
For the rtd I like the suggestion of the Feature structure, also the other options need to be explained and we will probably develop more of such features shortly.

I agree we carefully need to think about the text in the settings menu, maybe involve Martijn?

https://material.io/design/platform-guidance/android-settings.html#label-and-secondary-text
@MartijnUX can you have a look on this one?
@terrymyc Let's skip this for this PR and focus on the docs and hooks folder.

To overcome "Feature creep" we could already consider to user to implement a menu for the preferences/settings. This way we help the user make a selection of what to change. "The four-item rule applies to (short-term) memory retrieval". If we want to help the user choosing, we should try to keep it as minimal as possible. So, my advise would be to make the panel a bit bigger.

Makes sense. I think we can make this work on small screens as well. This requires some custom made components. I think we can reuse this is step 3 (overview relevant/irrelevant items) as well.

We could also use a Tab component. https://material-ui.com/components/tabs/#vertical-tabs

I agree with such menu's or tabs, since more features are comming and we will violate the '4 rule' sooner than later


Missing  Letter 's' !!

Hello Thanks for the awesome website FREECODECAMP
I noticed that there are missing 's' letter in this lesson
https://learn.freecodecamp.org/front-end-libraries/react/pass-props-to-a-stateless-functional-component
in the challenge description
"There is a Calendar and CurrentDate component(s) in the code editor."
I'm not native speaker but I think it is missing.
Thanks from EGYPT !

@MoatazAbdAlmageed since this has been fixed, please close the issue

Fixed #17657

Fixed #17657


Specify method to ab

It is useful to be able to benchmark applications that implement "DELETE" methods, and other non standard methods, ApacheBench is a very useful tool to do POST/PUT/GET requests, this change will allow one to specify any method with either POST or PUT bindings.
romans-air:httpd winfinit$ support/ab -h
Usage: support/ab [options] [http[s]://]hostname[:port]/path
Options are:
    -n requests     Number of requests to perform
    -c concurrency  Number of multiple requests to make at a time
    -t timelimit    Seconds to max. to spend on benchmarking
                    This implies -n 50000
    -s timeout      Seconds to max. wait for each response
                    Default is 30 seconds
    -b windowsize   Size of TCP send/receive buffer, in bytes
    -B address      Address to bind to when making outgoing connections
    -p postfile     File containing data to POST. Remember also to set -T
    -u putfile      File containing data to PUT. Remember also to set -T
    -T content-type Content-type header to use for POST/PUT data, eg.
                    'application/x-www-form-urlencoded'
                    Default is 'text/plain'
    -v verbosity    How much troubleshooting info to print
    -w              Print out results in HTML tables
    -i              Use HEAD instead of GET
    -x attributes   String to insert as table attributes
    -y attributes   String to insert as tr attributes
    -z attributes   String to insert as td or th attributes
    -C attribute    Add cookie, eg. 'Apache=1234'. (repeatable)
    -H attribute    Add Arbitrary header line, eg. 'Accept-Encoding: gzip'
                    Inserted after all normal header lines. (repeatable)
    -A attribute    Add Basic WWW Authentication, the attributes
                    are a colon separated username and password.
    -P attribute    Add Basic Proxy Authentication, the attributes
                    are a colon separated username and password.
    -X proxy:port   Proxyserver and port number to use
    -V              Print version number and exit
    -k              Use HTTP KeepAlive feature
    -d              Do not show percentiles served table.
    -S              Do not show confidence estimators and warnings.
    -q              Do not show progress when doing more than 150 requests
    -l              Accept variable document length (use this for dynamic pages)
    -g filename     Output collected data to gnuplot format file.
    -e filename     Output CSV file with percentages served
    -r              Don't exit on socket receive errors.
    -m method       Method name.
    -h              Display usage information (this message)
    -Z ciphersuite  Specify SSL/TLS cipher suite (See openssl ciphers)
    -f protocol     Specify SSL/TLS protocol
                    (SSL2, SSL3, TLS1 or ALL)

sample command and output:
romans-air:httpd winfinit$ support/ab -m PING -n 1 -v 9 http://<IP_ADDRESS>:6666/
This is ApacheBench, Version 2.3 <$Revision$>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking <IP_ADDRESS> (be patient)...INFO: PING header ==
---
PING / HTTP/1.0
Host: <IP_ADDRESS>:6666
User-Agent: ApacheBench/2.3
Accept: */*

---
LOG: header received:
HTTP/1.1 200 OK
Date: Fri, 06 Jun 2014 18:37:54 GMT
Server: Apache/2.2.26 (Unix) mod_ssl/2.2.26 OpenSSL/0.9.8y mod_cluster/1.3.1.dev DAV/2
Connection: close
Content-Type: text/plain

Type=PING-RSP&State=OK&id=-322559617

LOG: Response code = 200
..done

Server Software:        Apache/2.2.26
Server Hostname:        <IP_ADDRESS>
Server Port:            6666

Document Path:          /
Document Length:        37 bytes

Concurrency Level:      1
Time taken for tests:   0.001 seconds
Complete requests:      1
Failed requests:        0
Total transferred:      226 bytes
HTML transferred:       37 bytes
Requests per second:    1572.33 [#/sec] (mean)
Time per request:       0.636 [ms] (mean)
Time per request:       0.636 [ms] (mean, across all concurrent requests)
Transfer rate:          347.02 [Kbytes/sec] received

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

this was merged already


(WIP) update readme.md

Problem:
Our readme was a bit hard to follow, and required you to read it sequentially.
Fix:
I've tried to make it more readable and focused the top section on the casual first-time installer - separating the "make your life easier" parts from "just get something running". I think it's a better direction, but wanted to get your thoughts on it before continuing.

looks good to me. the prerequisites are more readable with the reduced clutter.


issue:tutorial_android

Added tutorial for modelling users in the application database
Branch: branch_tutorial_android

This has been merged. https://docs.hasura.io/0.13/tutorials/modeling-users-in-the-application-database.html


Updates to elcord to make it a minor mode, add Windows support, et al.

An overview of all changes:

elcord is now a minor mode, rather than connecting automatically on startup
elcord now works on Windows, by use of a PowerShell script to serve as proxy between Emacs and Discord
Exported customization options via defcustom: - asdasd

Client ID if the user wants to use their own Discord Application
Extensible mappings for major modes to strings
Extensible mappings for major modes to icons
Hide buffer name and line if the user wishes to do so.

elcord now displays Emacs as the main icon on Discord, with a small icon for the currently active Major Mode
elcord now only updates Rich Presence every 15 seconds as requested by the spec, rather than every keystroke.
elcord gracefully handles starting up without Discord running, or if the Discord application exits, by attempting periodically to reconnect.
I've updated the README accordingly, adding documentation on the features and installation instructions.

Cool. Is this going to get merged, then? I'd love to close https://github.com/melpa/melpa/pull/5132 by pointing the MELPA recipe at this repo.


Moving to s3-deploy-action

This works, and it deploys much faster.
Demo link here:
https://collaborative-learning.concord.org/branch/s3-deploy-action/?demo
However it will have problems when we go to deploy a production version. The way that works requires some changes to webpack build and in the case of CLUE will require changes to the code.
We should be able see this problem in this branch if you add the branch name to the github actions config topBranches like:
    topBranches: >
      [ "master", "183571651-s3-deploy-action" ]

More details here: https://github.com/concord-consortium/s3-deploy-action#top-branches
The first thing that will break is the expectation of there being an index-top.html file in the dist folder.

I've merged master into this branch, and also temporarily updated ci.yml to build this PR's branch as a topBranch. This will make it possible to test if the resources load correctly when the html page is in different location from the resources.

This has now deployed the temporary top branch and can be tested here:
https://collaborative-learning.concord.org/index-s3-deploy-action.html?demo
You should notice that it is downloading its assets from https://collaborative-learning.concord.org/branch/s3-deploy-action/

The readme refers to two manual workflows which aren't available yet release-staging.yml and release.yml. release-staging.yml is part of this PR but GitHub won't show it until it has been merged to master. I'll add release.yml after this PR is merged and we try out release-staging.yml. I didn't want to make it possible to blow away the current index.html until we've tested this more.


Add --disable-check flag to upgrade command

The upgrade command performs the same validation checks as the install command, so add --disable-check flag to the upgrade command as well.
Fixes: a5598ec8ed0e ("Add --disable-check flag back")

✅ tested manually ✨
% ./cilium install --disable-check=minimum-version --version 1.15.1
🔮 Auto-detected Kubernetes kind: kind
✨ Running "kind" validation checks
⏭   Skipping disabled validation test "minimum-version"
ℹ   Using Cilium version 1.15.1
🔮 Auto-detected cluster name: kind-chart-testing
🔮 Auto-detected kube-proxy has been installed

% ./cilium upgrade --disable-check=minimum-version --version 1.15.2
🔮 Auto-detected Kubernetes kind: kind
✨ Running "kind" validation checks
⏭   Skipping disabled validation test "minimum-version"
ℹ   Using Cilium version 1.15.2
🔮 Auto-detected cluster name: kind-chart-testing
🔮 Auto-detected kube-proxy has been installed

gotta love that this was already factored out :rocket:


1.3.3 install broken, ModuleNotFoundError: No module named 'pkgconfig'

During installation i'm getting:
ModuleNotFoundError: No module named 'pkgconfig'
But as can be seen at the stack trace:
Installing pkgconfig-1.5.1-py2.py3-none-any.whl to /opt/atlassian/pipelines/agent/build/.eggs Installed /opt/atlassian/pipelines/agent/build/.eggs/pkgconfig-1.5.1-py3.6.egg
both packages are in my requirements file
xmlsec==1.3.3             # via python3-saml pkgconfig==1.5.1          # via xmlsec
python3.6 setup.py test --addopts "-m unit_test"
running pytest
Searching for zipp==0.3.3
Reading https://pypi.org/simple/zipp/
Downloading https://files.pythonhosted.org/packages/00/42/10a1f8d29eaf9c7f2b555a5d1d602b9261f2a0cbec08f8f23d9056f5915d/zipp-0.3.3-py2.py3-none-any.whl#sha256=682b3e1c62b7026afe24eadf6be579fb45fec54c07ea218bded8092af07a68c4
Best match: zipp 0.3.3
Processing zipp-0.3.3-py2.py3-none-any.whl
Installing zipp-0.3.3-py2.py3-none-any.whl to /opt/atlassian/pipelines/agent/build/.eggs
writing requirements to /opt/atlassian/pipelines/agent/build/.eggs/zipp-0.3.3-py3.6.egg/EGG-INFO/requires.txt
Installed /opt/atlassian/pipelines/agent/build/.eggs/zipp-0.3.3-py3.6.egg
Searching for pkgconfig==1.5.1
Reading https://pypi.org/simple/pkgconfig/
Downloading https://files.pythonhosted.org/packages/b4/2c/bf434cb5a6590417e1d4468050ec317ea17fd6231c2a256df4646c11e588/pkgconfig-1.5.1-py2.py3-none-any.whl#sha256=cddf2d7ecadb272178a942eb852a9dee46bda2adcc36c3416b0fef47a4ed9f38
Best match: pkgconfig 1.5.1
Processing pkgconfig-1.5.1-py2.py3-none-any.whl
Installing pkgconfig-1.5.1-py2.py3-none-any.whl to /opt/atlassian/pipelines/agent/build/.eggs
Installed /opt/atlassian/pipelines/agent/build/.eggs/pkgconfig-1.5.1-py3.6.egg
Searching for xunitparser==1.3.3
Reading https://pypi.org/simple/xunitparser/
Downloading https://files.pythonhosted.org/packages/57/04/15064f68aea845109382e966ea059497bcbf006b2ef0dee0e602065e09ce/xunitparser-1.3.3.tar.gz#sha256=f6e9262bbaeb9be8fccd52f1fd18a3f9b09aa95933df18137abd82197db25515
Best match: xunitparser 1.3.3
Processing xunitparser-1.3.3.tar.gz
Writing /tmp/easy_install-9jgca8r8/xunitparser-1.3.3/setup.cfg
Running xunitparser-1.3.3/setup.py -q bdist_egg --dist-dir /tmp/easy_install-9jgca8r8/xunitparser-1.3.3/egg-dist-tmp-k3cs_bhd
zip_safe flag not set; analyzing archive contents...
Moving xunitparser-1.3.3-py3.6.egg to /opt/atlassian/pipelines/agent/build/.eggs
Installed /opt/atlassian/pipelines/agent/build/.eggs/xunitparser-1.3.3-py3.6.egg
Searching for xmlsec==1.3.3
Reading https://pypi.org/simple/xmlsec/
Downloading https://files.pythonhosted.org/packages/35/42/d7cd323c91d4706f3cc32ffe7d5f851ab8ef9898ccb350f6ba593dd8b89a/xmlsec-1.3.3.tar.gz#sha256=e573c0172174973223d874ffd158ecd4e0faa761015474385289a6468dd29ed6
Best match: xmlsec 1.3.3
Processing xmlsec-1.3.3.tar.gz
Writing /tmp/easy_install-3psrchsy/xmlsec-1.3.3/setup.cfg
Running xmlsec-1.3.3/setup.py -q bdist_egg --dist-dir /tmp/easy_install-3psrchsy/xmlsec-1.3.3/egg-dist-tmp-iyhjizxz
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/setuptools/sandbox.py", line 154, in save_modules
    yield saved
  File "/usr/local/lib/python3.6/site-packages/setuptools/sandbox.py", line 195, in setup_context
    yield
  File "/usr/local/lib/python3.6/site-packages/setuptools/sandbox.py", line 250, in run_setup
    _execfile(setup_script, ns)
  File "/usr/local/lib/python3.6/site-packages/setuptools/sandbox.py", line 45, in _execfile
    exec(code, globals, locals)
  File "/tmp/easy_install-3psrchsy/xmlsec-1.3.3/setup.py", line 60, in <module>
  File "/usr/local/lib/python3.6/site-packages/setuptools/__init__.py", line 129, in setup
    return distutils.core.setup(**attrs)
  File "/usr/local/lib/python3.6/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/usr/local/lib/python3.6/distutils/dist.py", line 955, in run_commands
    self.run_command(cmd)
  File "/usr/local/lib/python3.6/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/usr/local/lib/python3.6/site-packages/setuptools/command/bdist_egg.py", line 172, in run
    cmd = self.call_command('install_lib', warn_dir=0)
  File "/usr/local/lib/python3.6/site-packages/setuptools/command/bdist_egg.py", line 158, in call_command
    self.run_command(cmdname)
  File "/usr/local/lib/python3.6/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/usr/local/lib/python3.6/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/usr/local/lib/python3.6/site-packages/setuptools/command/install_lib.py", line 11, in run
    self.build()
  File "/usr/local/lib/python3.6/distutils/command/install_lib.py", line 107, in build
    self.run_command('build_ext')
  File "/usr/local/lib/python3.6/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/usr/local/lib/python3.6/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/tmp/easy_install-3psrchsy/xmlsec-1.3.3/setup.py", line 11, in run
    author='orcarmi',
  File "/tmp/easy_install-3psrchsy/xmlsec-1.3.3/setup.py", line 16, in patch_options
    )
  File "/tmp/easy_install-3psrchsy/xmlsec-1.3.3/xmlsec_setupinfo.py", line 48, in define_macros
  File "/tmp/easy_install-3psrchsy/xmlsec-1.3.3/xmlsec_setupinfo.py", line 111, in xmlsec_config
  File "/tmp/easy_install-3psrchsy/xmlsec-1.3.3/xmlsec_setupinfo.py", line 164, in load_xmlsec1_config
  File "/tmp/easy_install-3psrchsy/xmlsec-1.3.3/.eggs/pkgconfig-1.5.1-py3.6.egg/pkgconfig/pkgconfig.py", line 248, in parse
  File "/tmp/easy_install-3psrchsy/xmlsec-1.3.3/.eggs/pkgconfig-1.5.1-py3.6.egg/pkgconfig/pkgconfig.py", line 103, in _raise_if_not_exists
pkgconfig.pkgconfig.PackageNotFoundError: xmlsec1 not found
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "setup.py", line 15, in <module>
    tests_require=Path('requirements.txt').read_text(),
  File "/usr/local/lib/python3.6/site-packages/setuptools/__init__.py", line 129, in setup
    return distutils.core.setup(**attrs)
  File "/usr/local/lib/python3.6/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/usr/local/lib/python3.6/distutils/dist.py", line 955, in run_commands
    self.run_command(cmd)
  File "/usr/local/lib/python3.6/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/opt/atlassian/pipelines/agent/build/.eggs/pytest_runner-4.4-py3.6.egg/ptr.py", line 183, in run
    installed_dists = self.install_dists(dist)
  File "/opt/atlassian/pipelines/agent/build/.eggs/pytest_runner-4.4-py3.6.egg/ptr.py", line 131, in install_dists
    orig.test.install_dists(dist),
  File "/usr/local/lib/python3.6/site-packages/setuptools/command/test.py", line 206, in install_dists
    tr_d = dist.fetch_build_eggs(dist.tests_require or [])
  File "/usr/local/lib/python3.6/site-packages/setuptools/dist.py", line 514, in fetch_build_eggs
    replace_conflicting=True,
  File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 770, in resolve
    replace_conflicting=replace_conflicting
  File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 1053, in best_match
    return self.obtain(req, installer)
  File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 1065, in obtain
    return installer(requirement)
  File "/opt/atlassian/pipelines/agent/build/.eggs/pytest_runner-4.4-py3.6.egg/ptr.py", line 72, in fetch_build_egg
    return cmd.easy_install(req)
  File "/usr/local/lib/python3.6/site-packages/setuptools/command/easy_install.py", line 673, in easy_install
    return self.install_item(spec, dist.location, tmpdir, deps)
  File "/usr/local/lib/python3.6/site-packages/setuptools/command/easy_install.py", line 699, in install_item
    dists = self.install_eggs(spec, download, tmpdir)
  File "/usr/local/lib/python3.6/site-packages/setuptools/command/easy_install.py", line 884, in install_eggs
    return self.build_and_install(setup_script, setup_base)
  File "/usr/local/lib/python3.6/site-packages/setuptools/command/easy_install.py", line 1152, in build_and_install
    self.run_setup(setup_script, setup_base, args)
  File "/usr/local/lib/python3.6/site-packages/setuptools/command/easy_install.py", line 1138, in run_setup
    run_setup(setup_script, args)
  File "/usr/local/lib/python3.6/site-packages/setuptools/sandbox.py", line 253, in run_setup
    raise
  File "/usr/local/lib/python3.6/contextlib.py", line 99, in __exit__
    self.gen.throw(type, value, traceback)
  File "/usr/local/lib/python3.6/site-packages/setuptools/sandbox.py", line 195, in setup_context
    yield
  File "/usr/local/lib/python3.6/contextlib.py", line 99, in __exit__
    self.gen.throw(type, value, traceback)
  File "/usr/local/lib/python3.6/site-packages/setuptools/sandbox.py", line 166, in save_modules
    saved_exc.resume()
  File "/usr/local/lib/python3.6/site-packages/setuptools/sandbox.py", line 140, in resume
    type, exc = map(pickle.loads, self._saved)
ModuleNotFoundError: No module named 'pkgconfig'

Did you try yum install pkgconfig?
If you did, you probably need to configure PKG_CONFIG_PATH as well.

@gs202 this was caused by pkgconfig not been declared as build dependency. This is now fixed in the latest 1.3.8 version; can you please confirm the issue is resolved?

Closed as cannot reproduce this. Feel free to ping me if the issue should be reopened, though.


Crashing while using the trim tool

Hello. Fine tool you have here. I consistently crash when using the trim tool to playback certain parts to get the right clip. Windows 10 64 bit.

It happens often with the latest version 3.22.0?

can confirm it's happening a lot for me too since recent updates.

Memory management is improved. The program is 32 bits for dependency of some libraries, so the amount of memory is limited compared to 64 bits.


Feedback on Chromium Patch Issue and Requirement for Flatpak Version

After installing the widevine-installer patch, Chromium can play Spotify without any issues (Firefox is also fixed). However, the Chromium installed through Flatpak (flatpak install flathub org.chromium.Chromium) still has problems. Could it be that this patch didn't consider this version? As for why I have to use the Flatpak version, it's because this Chromium version can resolve Google sync issues by using flatpak override --user --env.
jack@jack-macbookpro:/var/lib/flatpak/app/org.chromium.Chromium$ ls
aarch64  current

Flatpak Chromium is isolated in the sense that it has its own libraries and doesn't use system libs. This patch adds Widevine to the system libraries and has no effect on Flatpak.


[Preview-Do not merge] Request for comments on Elasticsearch performance tests

Not to be merged: work in progress.
New performance tests for the Elasticsearch module. Their purpose is to give us an idea of how our code performs in the real world, so I tried to use scenarios involving multiple work types, and most importantly multiple works in each transaction.
With these tests, we should be able to compare different implementations of the Elasticsearch work processor (https://hibernate.atlassian.net/browse/HSEARCH-2764).
@Sanne This is largely based on your work on the engine tests, but my additions may overlook some micro-benchmarking pitfalls. Does anything seem incorrect to you?

Looks like a great start!
One pitfall might be the usage of randoms.
Two different angles:

it's good to have a randomized source but make sure that when running the same benchmark multiple times, the same sequence is generated. You want to be able to compare them, and reproduce them when investigating issues.
do not generate random numbers during the test run, try to create all data you need upfront. The reason is that the host running the test has only a limited amount of entropy: let's say it contains enough data to feed 5,000 iterations of your test, and your test consumes about 5,000. You'll run the benchmark twice and the second time it will be significantly slower. Entropy builds up over time but this process can be surprisingly slow, especially on VMs and headless servers. Servers also consume a lot of it for all the secure connections (assuming they have no dedicated hardware to boost it).

Closing to avoid CI builds while I'm working on this branch.


Consider Migrating Jenkins CI to Github Actions if Travis runs out of Credit

[ ] Ensure Same Functionality
[ ] Ensure PRs cant be merged unless succeeds
[ ] Check all Travis Variables e.g. for Test Exclusions etc


Offering the option to use flat badges

Fixes #1258
In the awesome manifesto, two badges are available for awesome lists and mentioned-in-awesome repos.

I made my own versions of the awesome badges, with a flat style.
I haven't added a single thing, only removed the gradient, the shadows and the round corners.
They were passed through svgomg as asked

N.B: You may want to host these svg on awesome.re, the URLs would look a lot better ✨

N.B: You may want to host these svg on awesome.re, the URLs would look a lot better ✨

You can add them there yourself, just do another PR to https://github.com/sindresorhus/awesome/tree/gh-pages ;)

Ooh, I didn't realize that the source of awesome.re was Github Pages.
Pull request created and links updated. I added the badges to the /media folder too.

Great! Thank you :)


feat: remove primary to secondary mapper (handled automatically)

@metacosm I would actually put this into 3.0 since, although its quite last minute, but simplifies usafe. PrimaryToSecondaryMapper was not easy to understand for someone who started with dependent resources and ti basically was needed in all cases when the names of the primary and secondary did not match.


Cont rkt tip aug 1st

Squashed commits into two commits based on the owner.
Softlink /persist/rkt to /var/lib/rkt
Use Add rkt data directory global option --dir=<> for all rkt commands
And rebased the patches on Top of master

@spatchineelam @kalyan-nidumolu as part of this review you both should start going over Yetus feedback https://1561-182198941-gh.circle-artifacts.com/0/tmp/yetus-out/diff-patch-revive.txt
I'll provide more details later today

One last thing @spatchineelam and @kalyan-nidumolu -- please make sure to rebase on the latest EVE master before taking care of feedback @zedvijay and I provided. You'll need to be based off of https://github.com/lf-edge/eve/pull/170/files at least

I have squashed the whole lot of commits into 4 total commits, and applied Roman's CircleCI tweak on top.


what deos "WARNING: XVIZ Protobuf files are unstable, do not use" mean?

First, awesome project! I'm trying to use it in our project.
At the beginning of every .proto file, there is such a warning. Why it's unstable? I refer to the doc, and it says "the Prototuf schema for XVIZ is under active development.". So, can I use it or not? If not, how to incorporate XVIZ in my C++ project?
Thanks!

@JianXinyu yes, documentation doesn't update at the same speed as development practices :p. The protobuf's are completely fine to use and preferred in nearly all cases.  our glTF will be deprecated at some point as protobuf is across the board easier to integrate with.


Implement new FilterHeader type to differentiate from FilterHash

These two types represent different hashes:
Filter hash is the sha256d hash of the bytes of the filter
Filter header is the sha256d hash of the filter hash concatenated with the previous filter header
filter_id() is replaced with filter_header() to better describe what it returns
Calculating the filter header is moved to the filter hash type because you need to calculate the filter header from a filter hash when you do not have access to the full filter.

Though not a functional change per se a nice clarification to the hash types used in CFHeader and BlockFilter to more closely matches BIP-157 nomenclature where "filter header" is used but not "filter id".

Concept ACK, though I think some things are missing. In the network/message_filter.rs file, some uses of FilterHash need to be replaced with FilterHeader.

I can only see one instance of filter hash and that's for cfheaders. The bip says "the response includes one filter header and a sequence of filter hashes" so that's correct

I've renamed previous_filter to previous_filter_header in cfheaders to better describe what it is

Seems to need a rebase. Ping me if you need a re-ack in #rust-bitcoin.


[BUG] with addChannelCheck and setPlayerRadio on server side

Describe the bug
Working on resticted channels via addChannelCheck export and it not working

from client side: not checking access on channel join -> can join to restricted channel
from server side: adding player to channel and nui not update

To Reproduce
minimal script for checking:
server.lua
RegisterCommand("svradio", function (source, args, rawCommand)
	if args[1] then
		exports["pma-voice"]:setPlayerRadio(source, tonumber(args[1]))
	end
	local Player = Player(source).state
	print(source, tonumber(args[1]), Player.radioChannel)
end, false)

Citizen.CreateThread(function ()
	exports["pma-voice"]:addChannelCheck(100, function(source)
		local Player = Player(source).state -- update from esx
		print(job, Player.job)
		if Player.job == job then
			print("true")
			return true
		end
		print("false")
		return false
	end)
--[[
srv log:
offgym	police
false
--]]
end)

then:

type svradio 100
will print player added to channel
player adding into radio channel, but nui not updated
if try join to resticted channel, still add to radio channel

Expected behavior
When join to restriced channel, cancel it.
Server Info:

Server Version: 5181
Client Version: beta
Client Build: b2545
Game: fivem

Picture and some info

server side: update statebag before check canjoin: radio module line:108
server side: trigger client update before check canjoin: radio module line:106
client side: no trigger for nui update in syncRadio function: radio module line 186

They get added but removed instantly after
See:
https://github.com/AvarianKnight/pma-voice/blob/2eb25b4a40a5f64e77e63a2fedba87c4bee6bcc9/server/module/radio.lua#L52-L55
The radio channel the person gets stuck in is their previous radio channel if they joined one prior


Structured logging hides contents of interface objects

Describe the bug
Some (quite many) go objects in Meridio are really interfaces. When used for output in structured logging the contents is empty {}. Example;
https://github.com/Nordix/Meridio/blob/c19b1d2e8c5dec12639ee0570773724bc3859cea/pkg/loadbalancer/stream/loadbalancer.go#L190
To Reproduce
Check the load-balancer logs:
# kubectl logs -n red -c stateless-lb meridio-load-balancer-7549d49c9f-f28xz | jq
...
{
  "severity": "info",
  "timestamp": "2023-02-06T09:29:37.965+00:00",
  "service_id": "Meridio-LB",
  "message": "AddTarget",
  "version": "1.0.0",
  "extra_data": {
    "class": "LoadBalancer",
    "instance": "stream1",
    "target": {}
  }
}

Expected behavior
Useful logging

Interface classes may be needed, but they should not be over-used since they basically trashes structured logging.
An overhaul is needed to log specific getters in interface objects rather than the objects themselves. This goes somewhat against the idea of structured logging.


Maybe some more detail required

Using an exe built with vs2008 - i needed to copy the debug dlls and manifests from the non redist folder (i guess that matches method 2), but got a sxs error.
I ran sxstrace - the version number in the manifest didn't match what the exe wanted. Putting in the older version of the dlls had an incorrect entry point. I had to edit the manifest file to change the version (also removed the sha details) whilst using the new dlls. No idea where these version numbers reside in the vcproj!

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ce3ac071-f6e9-da5a-6fa5-577da31bd308
Version Independent ID: 92854ad2-954f-e12f-7f7f-f9cec8924548
Content: Preparing a Test Machine To Run a Debug Executable
Content Source: docs/windows/preparing-a-test-machine-to-run-a-debug-executable.md
Product: visual-cpp
Technology: cpp-windows
GitHub Login: @corob-msft
Microsoft Alias: corob

@heuanhomos
My understanding is that debug DLL version matching information doesn't come from the project file. It's either recorded in the PDB file, or for SxS assemblies, in the manifest. The linker records this version info when it generates the PDBs and manifests. If you're doing new builds with the 2008 toolset, it should pick up whatever libraries you use for your build. If it's an old binary, locating the PDB and debug DLLs you need is up to you; it's a good idea to archive these whenever you create a binary for precisely this purpose. Doing as you've done, trying to make a slightly different version of some library work instead, is sometimes possible, but it's not recommended. I don't expect we'll explain how to do something we don't recommend.
I'm currently closing the issue as out of scope, but it's entirely possible that I've misunderstood what detail you're asking for, and something should be clarified in the docs. If you can explain what you're looking for in this article, and it's in scope for the article, I'm happy to reconsider, and reopen the issue.


Question: Multiple hubs on 1 server

Hi,
I plan on mapping two hubs to two different routes on my server.  For example:

app.UseSignalR(routes =>
{
      routes.MapHub<ReaderHub>("/ReadHub");
      routes.MapHub<WriterHub>("/WriterHub");
});

Is this ideal and are there any drawbacks to this method? I plan on allowing a page to connect to only 1 hub at a time.
The only documentation I could find was for the ASP.NET version
https://docs.microsoft.com/en-us/aspnet/signalr/overview/guide-to-the-api/hubs-api-guide-server#multiplehubs
Thank you.

ASP.NET Core SignalR definitely supports multiple hubs per server, but unlike ASP.NET SignalR these hubs do not share connections. This means that if you do connect to multiple hubs on the same page, the client will be using multiple connections. There's no inherent problem with that, it just means it takes two separate TCP connections.
In your case, since you only plan to connect to 1 hub at a time, there's absolutely no problem with having multiple hubs. Are you seeing an error or problem?

That's great to hear. As of now, I'm not experiencing any errors related to multiple hubs. Just wanted to ensure I'm aware of any drawbacks.


vttv stream

I can't connect any vttv stream.
I'm a japanese. so i can't use English well.

the links is down.


Updated Vm Start/Stop/Suspend actions to leverage optional class_name

Updated action method to have class_method as optional.
Simplified and updated start, stop and suspend VM actions accordingly.

:+1:

If I merge this, will it mess up all of your other PRs?  Do you want them merged in any particular order?

this PR can be merged. only touches what's already merged so it shouldn't mess up the Vm delete PR, remaining PRs after delete do need rebasing.


getting job Artifacts added also added gitter and storyboard/sprintboard

just need to replace gitter and waffle.io links with current repo

Could you describe me why buildUrl is modified?  I didn't execute your branch, but this change seems breaking one for other methods.

And the changes in README.rst (adding gitter and stroyboard/sprintboard) are not necessary for me.  Please revert these, or close the PR and create new PR with only changes to add getting job artifacts once again.

For getting artifacts url is http://example.jenkins.com/job/job_name/api/json?tree=artifacts[*]
so when I am trying to pass tree as key and value as artifacts[*] as value,encode method escaping [*]
so rest request was failing in that case,so I modified buildURL method to work with this scenario.

For example, (*Jenkins).GetQueue needs to request to http://example.jenkins.com/queue/api/json, but in your branch, the URL modified to http://example.jenkins.com/job/queue/api/json and that endpoint not exists.

I can revert change back,but sometimes we need to provide parameters as http://example.jenkins.com/job/job_name/api/json?tree=artifacts[*],but url.Encode(), replacing [*] so what do you think what is the best idea to work with such cases.

I am appending /job/ to url path,so will remove that also

@akashshinde can you please rebase your pull request?
I wish this could be merged. very useful

I wish this could be merged. very useful

I re-implemented it in a more simple way here:
https://github.com/yosida95/golang-jenkins/pull/19/files
@yosida95 is that better?

Close this PR because artifacts feature is now supported in #19.
Thank you @akashshinde, @bclermont !


errors

Uncaught ReferenceError: audience_wrapper is not defined
at controller.js:223
When you press the hall help.
Do not lose answers when choosing 50/50
Prohibit re-pressing the call when it was used

Hi @susl16c ! This is because the audience option functionality has not been implemented yet. You can feel free to contribute to this. Thanks!

The errors has been fixed. Thank you!


'application_id' on GCMDeviceSerializer

https://github.com/jleclanche/django-push-notifications/commit/78586d383816261a940227516244c5f750a07bb6 addresses this issue and has been merged into master (https://github.com/jleclanche/django-push-notifications/pull/401).  When will this be built and included in the latest pip package?

Also, it does not look like this will be available in https://github.com/jleclanche/django-push-notifications/releases/tag/1.5.0

I'm about to be unavailable for 3 weeks but I can make a new release when I get back.


ModuleNotFoundError: No module named 'search_setup'

Describe the bug
A clear and concise description of what the bug is.
Cannot run the example code, missing module "search_setup"
To Reproduce
Steps to reproduce the behavior:

Cloned most recent version of the source code.
Imported into PyCharm
Ran code, got the error ModuleNotFoundError: No module named 'search_setup'

Expected behavior
Be able to find all modules in latest version of all referenced libraries, such as praw.
Desktop (please complete the following information):

Python 3.6
OS: macOS High Sierra 10.13.4

I'm working on a fix!

I fixed the problem! It seems that I accidentally forgot to include the search_setup python script into the repository. Thanks for bringing this to my attention.
Here is a link to the latest hotfix release:
https://github.com/DuckBoss/RedditMediaScanner-Python3/releases/latest


posterr will not show now playing when access plex remotely

Plex app is hosted at my home, posterr server is hosted home on the same network on a virtual machine.
If I play from my account locally from my 192.168.x.x network posterr will display now playing movie.
If I access my plex server remotely posterr will not display now playing move.
Is this possible? if so what do I need to adjust?
Thanks.
-MZ

Have you tried enabling the remote networks option?

closing as no response


Plg installs old version

Hi! I was trying today to figure out how to pass a USB webcam through UNRAID to the go2rtc docker container and figured out I somehow needed video2linux and ALSA installed on UNRAID itself. Your DVB driver worked for video2linux and this worked for ALSA.
When I used the plg to install, however, I noticed it installed 2022.07.21 rather than the latest version 2024.09.23. I should note I am on UNRAID 7.0.0-beta.3.
I also think it would be great if you added this to community applications. Thanks so much for putting both of these together!

When I used the plg to install, however, I noticed it installed 2022.07.21 rather than the latest version 2024.09.23.

I don't understand, you mean the sound driver plugin?
The latest version from the sound driver plugin is version 2022.07.21, there is no newer version available.
From where do you get 2024.09.23?

I also think it would be great if you added this to community applications. Thanks so much for putting both of these together!

Sorry but I won't add this plugin to the CA App since I don't have time to improve it further nor to give support because this plugin is only meant for USB devices and most people will most likely ask why it won't work for their onboard sound cards, which I explained here.

I saw this release and was assuming it was the newest one.

The plugin version is not bound to the package version.
The plugin installs the appropriate package for your running Unraid version on boot or installation from the plugin.
If you do:
ls -1 /var/log/packages | grep sound
from a Unraid terminal you will see which package got installed.
The packages in the release section are the pre compiled drivers which the plugin automatically determines to be compatible with your running Unraid version and downloads them as explained above.
Hope that makes sense.

That makes sense. Thank you!