Validate header claims

I'd like to be able to validate header claims with my claim spec as well -- this could look like:
local claimSpec = {
  header = {
    alg = validators.equals('HS256'),
    kid = validators.equals('MyKeyID'),
    custom = validators.equals('other')
  },
  payload = {
    exp = validators.required(validators.opt_is_not_expired()),
  }
}

Good idea! I definitely will do this!

Awesome! By the way, I think it's considered best practice to pin the signing algorithm when verifying a JWT. Otherwise:

An attacker can change alg: none in the header, and a insecure JWT library would validate the JWT
An attacker can use the public key of an asymmetric JWT, and sign a JWT using alg: HS256 or something symmetric and an insecure JWT library would validate the JWT

Not sure how it would look like in this library, but something to look into alongside this improvement.

We didn't implement the none algorithm.
You can use set_alg_whitelist function to pin one or some signing algorithms.

Awesome, didn't realize that. Thanks!

How would you go about validating the sub claim in the JWT access token.

Is it possible to validate the sub in the payload of the JWT ?


Linter proposal: Explicitly set each value for margin / padding

With:
margin: 10px 0 0;

I prefer it as:
margin-top: 10px;
margin-right: 0;
margin-bottom: 0;
margin-left: 0;

Is it possible to check for this please?

Have you tried the Shorthand option?

If you don't want to allow all possible shorthands, you can limit them by setting the allowed_shorthands array option to a subset of [1, 2, 3].

So setting allowed_shorthands as [] should supposedly forbid using any shorthands.

@monoblaine thanks, I just tried that, but it didn't work unfortunately.


Breaking while loop crashes tab

My Specs
Bug reproduced on MacOS 10.14.3, Chrome 72.0.3626.12, Latest Safari
Latest<EMAIL_ADDRESS>
Expected Behaviour
Making endless animation when using while loop shouldn't crash the browser tab.
Works perfectly in CodeSandbox.

What happened instead?
Following this example I tried implementing animation that is playing non-stop when while loop is set to true. I discovered that breaking that while loop crashes browser tabs (Safari, Chrome) both in dev environment and with minified build (Terser). Here is repro repository with the same component as  in CodeSandbox.
Also, I found that leaving react-spring docs open for an extended amount of time also crashes the tab, but I can't reproduce it reliably.

Possible leads

The fact that it works in CodeSandbox makes me think that it is could be related to build tools, but I can't imagine how.

I think that there is a possibility that I should somehow cancel an animation with the second cancel argument in async "to", but there are no examples in the docs. If the problem lies in me misunderstanding how async "to" works, maybe we could add this use case to the docs.

Also, using set and stop functions with custom loop using setInterval might help, but I couldn't get them to work as of now, I'm going to try and update later.

Heavy inline SVG animation crashes Chrome tab sometimes. This is, I think, mostly not applicable in our case because the same crash happens even if you animate divs. However, people could repro the same behaviour with SVG relatively recently.

I have the same issue. This code crashes the browser (chrome and safari):
useSpring({
	from: { transform: 'rotate(0deg)' },
	to: async next => {
		while (1) {
			await next({ transform: 'rotate(720deg)' });
			await next({ transform: 'rotate(0deg)' });
		}
	},
});

It completes the first iteration of the while loop normally, and then hangs the browser.
I could also not replicate this in a CodeSandbox. So maybe two different instances of react-spring in one build might be the issue ...?

@subhero24 I'm glad to know I'm not only one who has the problem.
I am not entirely sure what you mean by "two different instances", but in my repro repo there is only one useSpring in the whole app, so that shouldn't be the case

@MM263 I'm using a dependency that also has a react-spring dependency. So I think the build would contain two versions of react-spring. I'm not convinced this is the issue, but I mentioned it just in case.
As you pointed to build tools, I am using parcel for the build.

@subhero24 Got it, thanks for clarification!
I'm using webpack by the way, so maybe we ruled out build tools :)

Cannot reproduce with https://codesandbox.io/s/v6o7666onl
LMK if you can break that 👍

I wanted to dig deeper into the issue just now. But I can not reproduce the issue anymore. Sadly, I have no idea what fixed it ...

I was finally able to reproduce the bug! Here is a codesandbox that reproduces the issue: https://codesandbox.io/s/l4wqoyox5l
A one-time setState causes react-spring to go into an infinite loop. If you disable the line setState (index.js:24) inside useEffect, the tab crashes.
I disabled the sandbox "Infinite Loop Protection" in sandbox.config.json to show the issue of the infinite loop.

This seems to be fixed in #632 👍

You can use v9 like this now: yarn add react-spring@next
Let us know how it goes: #642

Tried the 9.0.0 beta today, and it fixes the issue for me. Thank you!

Just ran into this issue. v9.0.0 fixed it for me as well. Thanks! :tada:


feat(connector): [BOA/Cybersource] Pass commerce indicator using card network for apple pay

Type of Change

[ ] Bugfix
[x] New feature
[ ] Enhancement
[ ] Refactoring
[ ] Dependency updates
[ ] Documentation
[ ] CI/CD

Description

Apple pay transactions via BOA and Cybersource require a specific field commerce_indicator which is based on the card network type used during apple pay transactions.
https://docs.cybersource.com/content/dam/documentation/en/apple-pay/fdiglobal/so/applepay-so-fdiglobal.pdf
This data is now being passed using the card network data being shared from SDK during apple pay payments.
Additional Changes

[ ] This PR modifies the API contract
[ ] This PR modifies the database schema
[ ] This PR modifies application configuration/environment variables

Motivation and Context

https://github.com/juspay/hyperswitch/issues/3783
How did you test it?

Apple pay payments need to be tested using simplified and manual flow for connectors BOA and Cybersource
Checklist

[x] I formatted the code cargo +nightly fmt --all
[x] I addressed lints thrown by cargo clippy
[x] I reviewed the submitted code
[ ] I added unit tests for my changes where possible
[ ] I added a CHANGELOG entry if applicable

This changes are handled in https://github.com/juspay/hyperswitch/pull/3795


Improve the comment of tfmigrate plan

Make the comment easy to understand.
https://suzuki-shunsuke.github.io/tfaction/docs/feature/tfmigrate
https://github.com/minamijoyo/tfmigrate

multi_state - working directory
force
unexpected diff
command failure
migration files

no unapplied migrations
2023/04/27 22:50:42 [INFO] [runner] no unapplied migrations

migration files
2023/04/27 22:53:18 [INFO] [runner] unapplied migration files: [20230427225226_test.hcl]
2023/04/27 22:53:18 [INFO] [runner] load migration file: tfmigrate/20230427225226_test.hcl

unexpected diff
2023/04/27 22:55:19 [ERROR]<EMAIL_ADDRESS>unexpected diffs

terraform plan command returns unexpected diffs: failed to run command (exited 2): terraform plan -state=/var/folders/lk/bw_hsbdd72l9ckd0tz61xz2m0000gn/T/tmp1879517692 -out=/var/folders/lk/bw_hsbdd72l9ckd0tz61xz2m0000gn/T/tfplan4277955471 -input=false -no-color -detailed-exitcode

Note: Objects have changed outside of Terraform

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create
  - destroy

Terraform will perform the following actions:

Plan: 1 to add, 0 to change, 1 to destroy.


Give administrator privileges to tab

Description of the new feature/enhancement

A possibility to change certain tabs to administrator rights.
Useful when you have to deal with package managers and similar.
Proposed technical implementation details (optional)

An entry for that functionality in the CTL+SHIFT+P menu, which changes the current tab to administrator, or if that's not possible, creates a new one with administrator privileges.

This is something you can kinda already do today, but maybe not that conveniently. As of 1.13, you can mark a profile as requiring elevation (admin rights), with elevate:true. You can also use that in a newTab action to open that profile elevated. So you could add something like:
        { "icon": "\uEA18", "command": { "action": "newTab", "elevate": true, "profile": "foo" } },

to open your foo profile as admin. Or just Ctrl+Click on the entry in the dropdown.
However, what you really want is "duplicate the current tab, with admin permission", and that's not tracked right now, I don't think. #10232 is sorta like it, but not exactly what I'm looking for. splitPane has splitMode: duplicate, maybe we need a flag like that for newTab (or just let duplicateTab accept the rest of a NewTerminalArgs

If you put elevate:true in the settings.json file for a new tab definition, then that will cause a new Windows Terminal window to launch.  However, if you instead use sudo from the gsudo package, then you just get a new tab as expected.
           {                 "commandline": "sudo %SystemRoot%\\System32\\cmd.exe",                 "guid": "{0caa0dad-35ce-5f56-a8ff-afceeeaa6101}",                 "hidden": false,                 "name": "CMD Admin"             },
The above will cause a new tab, with CMD elevated.
While this:
           {                 "commandline": "%SystemRoot%\\System32\\cmd.exe",                 "guid": "{0caa0dad-35ce-5f56-a8ff-afceeeaa6101}",                 "hidden": false,                 "elevate":true,                 "name": "CMD Admin"             },
will instead launch a new Windows Terminal window, with an elevated command prompt.  Not an additional tab.  Neither method is wrong, just a matter of preference.  I like a new tab, not a new window, but YMMV.

obliged to add: as awesome as gsudo is, there is a fairly trivial escalation of privilege attack that's possible with it, so use with caution. I'm gonna collapse both these as off topic to keep focused on the implementation of the original ask here. Thanks ☺

Would it be possible to add a Terminal-specific command "sudo" so the user could type that, which would instruct Terminal to duplicate the tab as admin?

You know, I might just close this as /dup https://github.com/microsoft/sudo. Honestly, that's just the easiest user experience over all.
(we'll work on shipping that out-of-band from the OS: https://github.com/microsoft/sudo/issues/57)


Vulnerability issues with dependencies in dropwizard 2.1.6

After running the OWASP Dependency check against our components, reporting vulnerabilities :
[ERROR] guava-31.1-jre.jar: CVE-2020-8908(6.2)

Low severity, there's no fixed version, and the method in question isn't even used in Dropwizard.


register IntegrityService correctly

Fixes a missing service factory registration for IIntegrityService.
See: https://python-software-foundation.sentry.io/share/issue/70ec7e99e7524584acc2ebf9a238f832/

Closing in favor of revert in #16542. I'll cherry-pick this onto the recreated PR along with a full backstop test.

Merging this instead of having to revert the migration, @woodruffw will follow up with an additional test in a separate PR!


Google object detect: misleading success message

With an invalid image url processed by Google Vision, the tool reports 'success'.
Successfully processed image: http://datable.be/files/image_analysis_test/samples4/XXzac_posen_ss13_0965.jpg
{'data': [], 'error': [{'error': {'code': 3, 'message': 'The URL does not appear to be accessible by us. Please double check or download the content and pass it in.'}}], 'request_id': 'http://datable.be/files/image_analysis_test/samples4/XXzac_posen_ss13_0965.jpg'}

Can you specify how to reproduce this exactly? I mean, when I POST a request with an invalid image URL to the tool, I get this JSON response:
{
    "data": [],
    "error": [
        {
            "error": {
                "code": 3,
                "message": "The URL does not appear to be accessible by us. Please double check or download the content and pass it in."
            }
        }
    ],
    "request_id": "http://example.com/images/123"
}

I can't see where the part Successfully processed image is coming from...

sorry, error in my script


Add CMI-SHMEM Module

Adds fast IPC delivery to any machine layer.
Adds the build options --enable-shmem (to use PXSHM) or --enable-xpmem (to use XPMEM).
Adds the command line options ++ipcpoolsize and ++ipccutoff.
TODOs:

Refine cmake additions? Discover XPMEM automatically? Enable passing XPMEM basedir? (Long term!)
Should we add tests for this module? (Add to autobuild as a machine layer test.)
Should we keep throwing bad alloc or just return nullptr? What's the performance impact of it? (Please offer thoughts.)

Testing this on Summit

Ah, keep me posted if you get a chance to test it elsewhere -- I'd be interested in the results!

Would it be possible to add support to buildold and configure.ac?

Would it be possible to add support to buildold and configure.ac?

I would prefer deferring that to a follow-up PR if that's acceptable (Add support for building SHMEM with buildold). Adapting all the buildold-related scripts to ensure a successful outcome will take some time, and this PR is quite large already.

Seems to work fine on Summit, with changes in CMakeLists.txt from ${CMK_SYSLIBS} to $CMK_SYSLIBS (see #3538)

Excellent! That confirms that address-free atomics work on ARM, PowerPC, and x86_64. Corrected this in the latest update :)


Add CONTRIBUTING.md

Mentioned in https://github.com/PostgREST/postgrest-docs/pull/244. Definitely necessary to add this.

Refer to https://github.com/PostgREST/postgrest/blob/master/.github/CONTRIBUTING.md


added 3 govermental Websites

Changes have been made you can review it
On Mon, Oct 2, 2023 at 8:53 AM Nishant Sapkota @.***>
wrote:

@.**** requested changes on this pull request.
In data/websites.json
https://github.com/Know-Nepal/government-websites/pull/27#discussion_r1342251102
:

 }

]
-}
+}
Could you add a new line at the end of the file please.
—
Reply to this email directly, view it on GitHub
https://github.com/Know-Nepal/government-websites/pull/27#pullrequestreview-1652058031,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASJWU3JGKJXBGX4SYCKUAPDX5IVZPANCNFSM6AAAAAA5OYXXBA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thank you for your contribution @prajjwallive :heart:

Awesome, thank you so much!
On Mon, Oct 2, 2023 at 9:02 AM Nishant Sapkota @.***>
wrote:

@.**** approved this pull request.
—
Reply to this email directly, view it on GitHub
https://github.com/Know-Nepal/government-websites/pull/27#pullrequestreview-1652061553,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASJWU3MAE7MSWPS7YCVGKSLX5IW5XANCNFSM6AAAAAA5OYXXBA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Add new fields to user

Feature

add new fields to user
add new fields surname, social security number, nationality, date of birth, place of work and positio

Type:  New implementation |
Depends on the issue: Hacksbr/<PROJECT_SLUG>#<ISSUE_ID>

Status: (Partially | Fully)

Checklist:

[x] Implement feature;
[x] Add tests;
[x] Update docstring;
[x] Update documentation.

"nacionalidade": "string",
"data_nascimento": "2023-10-05",
"local_trabalho": "string",
"cargo": "string"


webView.postMessage hangs iOS 10.3(14E8301) simulator

Is this a bug report?
postMessage to WebView hangs simulator
Have you read the Contributing Guidelines?
yes
Environment
Environment:
OS: macOS Sierra 10.12.1
Node: 7.2.1
Yarn: Not Found
npm: 5.4.2
Watchman: 4.8.0
Xcode: Xcode 8.3.3 Build version 8E3004b
Android Studio: Not Found
Packages: (wanted => installed)
react: 16.0.0-alpha.12 => 16.0.0-alpha.12
react-native: 0.48.4 => 0.48.4
Target Platform: iOS (10.3)
Steps to Reproduce
Steps to reproduce:

Create html with script

<script>
 document.addEventListener("message", function(data) {
	var temp = data.data.split("::");

	if (temp[0] === "token") {
	    token = temp[1];
	    alert("token " + temp[1]);
	else {
	    alert("unexpected data: " + data.data);
	}
});
</script>

Create component as

import React, { Component } from 'react';
import {
    View, TouchableHighlight, Text, WebView
} from 'react-native'
import TimerMixin from 'react-timer-mixin'

var htmlFile = require('../../assets/temp.html');

const SEPARATOR = "::";

export default class MapScreen extends Component<{}> {
    constructor(props) {
        super(props);

        this.state = {
            id: this.props.id || "null",
            token: this.props.token || "TOKEN",
        };
    }

    render() {
        return (
            <View style={{height: '100%', width: '100%'}}>
                <WebView
                    ref={ webview => { this.webview = webview; }}
                    source={htmlFile}
                    style={{backgroundColor: '#000000'}}
                    // onLoadEnd={()=>this._helloWebView()}
                />
            </View>
        )
    }

    componentDidMount() {
        this._helloWebView();
    }

    componentWillUnmount() {
        TimerMixin.clearTimeout(this.timer);
    }

    _helloWebView() {
        console.log("_helloWebView called");
        this.sendData("token::" + (this.state.token || "null"), 5000);
    }

    sendData(data, timeout) {
        console.warn("sendData called [" + data + "][" + (timeout || 0) + "]");

        TimerMixin.setTimeout(() => {
            console.log("postMessage executed [" + data + "][" + timeout + "]");
            this.webview.postMessage(data);
        }, timeout || 0);
    }

}

Expected Behavior
Alert is shown with provided token with no hang
(Write what you thought would happen.)
Actual Behavior
Simulator does not responding and the process needs to be killed via ActivityMonitor

Reproducible Demo
https://snack.expo.io/H1P4m802b

yes-template

Thanks for editing your post to make sure it uses the template as required by the contribution guidelines. Your issue is now open again.


It works on MAC?

Just wanna know if it's work on MAC

Nope. Windows only.
On Thu, 17 Dec 2015, 08:40 RuisuSato<EMAIL_ADDRESS>wrote:

Just wanna know if it's work on MAC
—
Reply to this email directly or view it on GitHub
https://github.com/networkMe/missinghud2/issues/50.

I would like to see this mod working on Linux !
Any Change to get that ?

The method MissingHUD hooks into the game is Windows specific (DLL
Injection).
A decent chunk of the codebase would have to be completely rewritten to
support Linux.
So no, it's still Windows only.
On Fri, 25 Dec 2015, 21:54 Thomas Worofsky<EMAIL_ADDRESS>wrote:

I would like to see this mod working on Linux !
Any Change to get that ?
—
Reply to this email directly or view it on GitHub
https://github.com/networkMe/missinghud2/issues/50#issuecomment-167222133
.


ALLOWED_ORIGINS

Currently, ALLOWED_ORIGINS is a startup config parameter that controls the allowed origins for the did method.
In a multi-domain orb network, and when a new orb domain is onboarded to the network, this requires updating and restarting all existing orb domain instances, which affects the availability of the overall network unjustifiably (confirmed with the orb team).
The proposal is to have an endpoint where this can be done for each orb domain at run-time, without requiring a restart of the orb instances.

[x] #1377
[x] #1378
[x] #1379

Done


Prevent Error when JSXSpreadAttribute is passed to isSemanticRoleElement

This was an error I ran into when running v6.2.0 on the FB codebase. It took me a while to get the test case, but now that I have it, I put up the fix.

Coverage increased (+0.09%) to 99.548% when pulling 610eef7770cffbf8d92bbfad80e75a63dd089cb7 on fix--isSemanticRoleElement into 33a7d6911023bef46bcdb890bf2abbc566d78b9e on master.

Coverage increased (+0.09%) to 99.548% when pulling 610eef7770cffbf8d92bbfad80e75a63dd089cb7 on fix--isSemanticRoleElement into 33a7d6911023bef46bcdb890bf2abbc566d78b9e on master.

Coverage increased (+0.09%) to 99.548% when pulling 610eef7770cffbf8d92bbfad80e75a63dd089cb7 on fix--isSemanticRoleElement into 33a7d6911023bef46bcdb890bf2abbc566d78b9e on master.

Coverage increased (+0.09%) to 99.548% when pulling 610eef7770cffbf8d92bbfad80e75a63dd089cb7 on fix--isSemanticRoleElement into 33a7d6911023bef46bcdb890bf2abbc566d78b9e on master.

Coverage increased (+0.09%) to 99.548% when pulling 610eef7770cffbf8d92bbfad80e75a63dd089cb7 on fix--isSemanticRoleElement into 33a7d6911023bef46bcdb890bf2abbc566d78b9e on master.

Coverage increased (+0.09%) to 99.548% when pulling 610eef7770cffbf8d92bbfad80e75a63dd089cb7 on fix--isSemanticRoleElement into 33a7d6911023bef46bcdb890bf2abbc566d78b9e on master.

Coverage increased (+0.09%) to 99.548% when pulling 610eef7770cffbf8d92bbfad80e75a63dd089cb7 on fix--isSemanticRoleElement into 33a7d6911023bef46bcdb890bf2abbc566d78b9e on master.

Coverage increased (+0.09%) to 99.548% when pulling 610eef7770cffbf8d92bbfad80e75a63dd089cb7 on fix--isSemanticRoleElement into 33a7d6911023bef46bcdb890bf2abbc566d78b9e on master.


Actions.md: swapped the order of flux and redux examples. Redux first.

As a casual reader the flux example might be confusing.
This is a Redux document, why not jump to the best part first?

Because it is a narrative. If not reviewing Flux first then it might be worth moving the Flux-specific notes to an Appendix. I'd argue it's fine as is though.

On Apr 14, 2016, at 1:35 PM, Laszlo Megyer<EMAIL_ADDRESS>wrote:
As a casual reader the flux example might be confusing.
This is a Redux document, why not jump to the best part first?
You can view, comment on, or merge this pull request online at:
https://github.com/reactjs/redux/pull/1615
Commit Summary
Actions.md: swapped the order of flux and redux examples. Redux comes first.
File Changes
M docs/basics/Actions.md (18)
Patch Links:
https://github.com/reactjs/redux/pull/1615.patch
https://github.com/reactjs/redux/pull/1615.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub

its fine by me, it just happened to trick me :)

Nah, let’s do it. I left a few nits but I agree we should start de-emphasizing Flux.
This was written before Redux was popular and we needed to cater to Flux users.
Today the situation is often the opposite.

Thanks. I added my changes in 24ab45f2acb8434119998e77464237041571d758

great, thanks!


Add support for User Provided Service Instances

https://docs.cloudfoundry.org/devguide/services/user-provided.html

This CF feature is really important for connecting apps to existing databases. We should have a User Provided (or Connection Info, or Existing Credentials) option in the Create Service Instance > Select Service list.

Any update on this and why it was removed from the v2-next roadmap? Would love to see this feature.

Hi @cwb124! We previously had this feature in v1 of Stratos and would have liked it to hit v2 soon after that release. It's however been bumped out a bit due to current priorities. I don't think we have any current plans to look at this within the next few months. I'll bring it up again with @troytop and @nwmac and see if there's any change.

Any update on this feature request? Doesn't seem to be scheduled and would be really useful.

My users are clamoring for this.  The PCF apps manager has this feature and as we try to create feature parity between PCF and OSCF in our enterprise, the lack of user provided services is the glaring delta between our GUI offerings.

@mymasse @cwb124 Sorry for the slow response. We've taken a look at this today and have a path forward. It might not make it into the next release but we're hoping to have something implemented by the following one.

Really appreciate you considering it for the roadmap and working towards it. I think it will be a very welcomed feature.

@cwb124 Just wanted to confirm with you that we've completed all of the known user provided service tasks and the feature will be in the next release (planned for end of this month). With it you should be able to create, edit and delete user provided service instances and view them in the main Services list as well as the new space user provided service instance list.

Awesome news. I just saw some of the new Stratos hotness from Troy at the CF summit.  Cool cool stuff coming, especially with container endpoints.  Appreciate all the work.  Hoping we can get some traction on Comcast's open source fellowship program to start putting resources to improving Stratos.


🐛 [Dataset] Cannot download wmt14, wmt15 and wmt17

I try downloading wmt14, wmt15, wmt17, wmt19 with the following code:

nlp.load_dataset('wmt14','de-en')
nlp.load_dataset('wmt15','de-en')
nlp.load_dataset('wmt17','de-en')
nlp.load_dataset('wmt19','de-en')

The code runs but the download speed is extremely slow, the same behaviour is not observed on wmt16 and wmt18

When trying to download wmt17 zh-en, I got the following error:

ConnectionError: Couldn't reach https://storage.googleapis.com/tfdataset-data/downloadataset/uncorpus/UNv1.0.en-zh.tar.gz

similar slow download speed here.
Downloading: 100%|██████████████████████████████████████████████████████████| 658M/658M [1:00:42<00:00, 181kB/s] Downloading: 100%|██████████████████████████████████████████████████████████| 918M/918M [1:39:38<00:00, 154kB/s] Downloading:   2%|▉                                                       | 40.9M/2.37G [04:48<5:03:06, 128kB/s]

The code runs but the download speed is extremely slow, the same behaviour is not observed on wmt16 and wmt18

The original source for the files may provide slow download speeds.
We can probably host these files ourselves.

When trying to download wmt17 zh-en, I got the following error:
ConnectionError: Couldn't reach https://storage.googleapis.com/tfdataset-data/downloadataset/uncorpus/UNv1.0.en-zh.tar.gz

Looks like the fileUNv1.0.en-zh.tar.gz is missing, or the url changed. We need to fix that

Could we just download a specific subdataset in 'wmt14', such as 'newstest14'?

Right now I don't think it's possible. Maybe @patrickvonplaten knows more about it

Yeah, the download speed is sadly always extremely slow :-/.
I will try to check out the wmt17 zh-en bug :-)

Maybe this can be used - https://stuncorpusprod.blob.core.windows.net/corpusfiles/UNv1.0.en-zh.tar.gz.00

These issues seem to be fixed now.


ldirichlet(d) and evaluate(d,d.a) behave differently

Is there a reason why these shouldn't be identical operators
julia> evaluate(d,d.a)
Evaluation{UltrasphericalSpace{0},Float64,Float64}(UltrasphericalSpace{0}(Interval{Float64}(0.0,50.0)),0.0,0)

julia> ldirichlet(d)
Evaluation{UltrasphericalSpace{0},Bool,Float64}(UltrasphericalSpace{0}(Interval{Float64}(0.0,50.0)),false,0)

for any d, in this case d=Interval(0.,50.)
At least they should behave the same, but something is up here
d = Interval(0.,50.)
D = diff(d)
t = Fun(identity,d)

F = D^2 +.5D + 1
BC_test1 = [evaluate(d,0.), evaluate(d,0.)*D]
BC_test2 = [ldirichlet(d), lneumann(d)]
BC0 = [1.0, 0.0]

x1 = [BC_test1, F]\[BC0, 0.0]
x2 = [BC_test2, F]\[BC0, 0.0]

julia> norm(x1-x2)
0.9875181589473826

ldirichlet(d) and evaluate(d,d.a) behave differently and/or  lneumann(d) and evaluate(d,d.a) * D

I'm curious why there is an approximate check (though maybe I'm misunderstanding). Aren't these boundary conditions numerically identical?

Hmm, it looks like the actual bug was already fixed.
I’ll leave the approximate check since otherwise Evaluation(d,0.,1) is not implemented yet.

On 22 Apr 2015, at 7:03 am, Gustavo Goretkin<EMAIL_ADDRESS>wrote:
I'm curious why there is an approximate check (though maybe I'm misunderstanding). Aren't these boundary conditions numerically identical?
—
Reply to this email directly or view it on GitHub https://github.com/ApproxFun/ApproxFun.jl/issues/79#issuecomment-94943100.


Fixed #28710 -- Fixed the Basque DATE_FORMAT string

Thanks Eneko Illarramendi for the report and initial patch.

Please add with self.subTest(locale=locale): after the for loop (except on stable/1.11.x where Python 2 support is needed).

Don't you mind combining the with conditions?
with self.subTest(locale=locale), translation.override(locale):

I tried that locally but it didn't seem to work.

Weird, it works fine on my system (Python 3.5). What error do you get?

I guess I had made a mistake earlier, seems to work now.


[Website] Java, Scala, C++, R, Clojure, and Julia API References redirect to 404

Description
Java issue: trying to access the MXNet Java API reference from this page leads to a 404. This issue also extends to all of the other language docs mentioned in the title.
Error Message
404 page
To Reproduce
Navigate to the MXNet Java homepage or Docs & Tutorials on the MXNet website and try to access the MXNet Java API reference.

@mxnet-label-bot add [Website]

Should this have been caught by the automatic link checker?

@leezu I'm not personally familiar with the automatic link checker, but I would assume so.

This is happening on the latest build, probably these 2 PR import the bug #18598 #18578

Thanks @ys2843. Found what I believe to be the root cause in #18598 - merge for this PR should be reverted ASAP.

Updated issue as it is worse than initial assessment - docs for Java, Scala, C++, R, Clojure, and Julia are not being built and are no longer available on the website.

That's correct, the PR removes the language bindings that use the old graph executor APIs. For now we need to remove them from the master version of the website until they are available in mxnet 2.0. Users can access these language binding docs in mxnet 1.6 website version. Let's work together to remove them, instead of reverting the PR.

Was there community consensus on this change? @eric-haibin-lin

I think this issue is duplicate of https://github.com/apache/incubator-mxnet/issues/18429 and can be closed?

@sandeep-krishnamurthy The project for merging beta website need to be rediscussed due to this change.

This issue can be closed, all language bindings are removed from master website.


feat(keybinds): keyboard shortcuts

What this PR does 📖
Record custom keybinds:

Keybind settings:

Find shortcut by kebind:

There are a few things left to fix before this is ready for review:

[ ] When recording a keybind, if you attempt to record a keybind that already exists the focus will shift to the the highlight functionality and break recording the duplicate keybind.
[ ] I've added the code to warn of duplicate keybinds but it is un-tested because of the aforementioned item.
[ ] Create a TooltipWrapper component in UIKit to enable adding common tooltips to any given children on the component.
[ ] We should include a button somewhere on the page to "reset to defaults".

Example of the highlight bug when trying to record duplicate keybinds:

We are going to leave this feature on experimental until we can add some more keybindings and squash a few more bugs, but this is ready for general testing and we can open further bugs for any bugs that do not cause regressions on existing features.


"w.WriteMany undefined (type seekable.Writer has no field or method WriteMany)"

Hi @SaveTheRbtz ,
I'm exploring zstd compressed SQLite. I've tried compressing my SQlite DB with zstd, and then use jtarchie's sqlitezstd library over top. I will be the first to acknowledge that I could be making multiple mistakes in my explorations.
I thought I would use your code to compress my DB, in case there's a difference. However, I get this error, and I haven't been able to diagnose why.
$ go run github.com/SaveTheRbtz/zstd-seekable-format-go/cmd/zstdseek -f db/src.sqlite -o src.sqlite.zst
# github.com/SaveTheRbtz/zstd-seekable-format-go/cmd/zstdseek
../../../go/pkg/mod/github.com/!save!the!rbtz/zstd-seekable-format-go/cmd/zstdseek@v0.0.0-20241001193558-df49df43ff57/main.go:174:10: w.WriteMany undefined (type seekable.Writer has no field or method WriteMany)
../../../go/pkg/mod/github.com/!save!the!rbtz/zstd-seekable-format-go/cmd/zstdseek@v0.0.0-20241001193558-df49df43ff57/main.go:174:47: undefined: seekable.WithWriteCallback

I was using go 1.23, and rolled back to 1.22.8. I still got the same error. Ubuntu 22.04.
I'll update this issue thread if I discover my error, or anything that seems to be the cause.

Nevermind.
My best guess: I had imported both psanford/sqlite3vfs and sqlite3vfshttp, because I was experimenting with something else earlier.
I can't explain why it caused the error it did, but reducing the number of VFS libraries I had in my code made a difference. Closing. Apologies for the noise.


Unable to add static library to lp core program (IDFGH-13696)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
v5.3
Operating System used.
Linux
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
None
What is the expected behavior?
It should simply link the symbol and that's it
What is the actual behavior?
It complains it can't find it, undefined reference
Steps to reproduce.
I have built by library (with rust esp-lp-hal) the symbol is there, the architecture is also the same, a normal static library, then I added on top of my ulp program extern void rust_test();. I tried many things, calling link_libraries, also modifying the __setup_ulp_project function, by trying to call add_prebuilt_library, the regular cmake ways of adding a library too, in various places, the main cmake file, the one in the main dir etc. I see no reason for it to not work, it should regularly grab the symbol and built with it.
Also as to why, this would enable me to use rust memory safety and trait magic to drive the lp core and esp idf would manage the features that aren't implemented there for rust yet
Build or installation Logs.
/opt/esp/tools/riscv32-esp-elf/esp-13.2.0_20240530/riscv32-esp-elf/bin/../lib/gcc/riscv32-esp-elf/13.2.0/../../../../riscv32-esp-elf/bin/ld: CMakeFiles/ulp_main.dir/workspaces/yatchy-lp-program/lp-core-esp-idf/main/ulp/main.c.obj: in function `main':
/workspaces/yatchy-lp-program/lp-core-esp-idf/main/ulp/main.c:19:(.text.startup.main+0x4): undefined reference to `rust_test'
collect2: error: ld returned 1 exit status

More Information.
It's for the esp32c6 lp core

Hi @Szybet, We have recently added the support for adding custom libraries to the ULP project. You can see the example here. This change is on the master branch only.

Wow, this is awesome, I will try it later. I hope it will work without specifying source files as I don't have them, but this shouldn't be an issue

Worked like a charm, huge thanks


Fix teardown of menus to prevent widget test leaks

Description

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

References

Fixes #3431
How has this been tested?

[x] example: the test suite for my feature covers cases x, y, and z
[x] example: all tests pass with my change

Final checklist:

[x] My PR is the minimum possible work for the desired functionality
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] If I included new strings, I have used trans. to make them localizable.
For more information see our translations guide.

@Czaki could you test this PR?
Thanks!

@Czaki could you test this PR?
Thanks!

Works for me.

There seem to be some segfaults on windows, but I do not think they are related to the PR as I have seem them on other PRs, but need to check.

you may check if adding qtbot.wait(50) like in #3427 will help.

Thanks @Czaki, trying now

from my observation, In the most common cases, failure is caused by some test that was already marked as completed.


[Mod matrix] Missing icons for permission actions and suggested sort actions

This is actually a reddit problem, more than a toolbox problem. We link to whatever icon reddit uses in the regular modlog...


[3/N][torch.compile] consolidate custom op logging

previously the custom op logging is too verbose.
after https://github.com/vllm-project/vllm/pull/10383 , we now have global control and aggregation of the custom op statistics.

the logging looks better now:

DEBUG 11-16 18:23:29 init.py:95] enabled custom ops: Counter({'rms_norm': 65, 'silu_and_mul': 32, 'rotary_embedding': 1})
DEBUG 11-16 18:23:29 init.py:97] disabled custom ops: Counter()


Fix - Size of logos on companies page

Fixed the size of companies logos on the companies page so now it looks nice!

Should I still add the borders around images? @TimKardol

Add the borders, I'll check how it looks.

Add the borders, I'll check how it looks.

Yeah well I did it, but it looks much worse imo..

Agreed, get rid of the borders and rounded edges. I think this fixes the issues we have been having. Can you also check the other issue about the sizes of the png/jpgs/etc? I think that is also a factor to consider.


Relationship between User.gm_at, restaurant.gm_id, and Restaurant.gm needs to be fixed

SAWarning: relationship 'User.gm_at' will copy column user.id to column restaurant.gm_id, which conflicts with relationship(s): 'Restaurant.gm' (copies user.id to restaurant.gm_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="gm"' to the 'User.gm_at' relationship. (Background on this error at: https://sqlalche.me/e/14/qzyx)

Added , viewonly=True when User.gm_at


Gateway on hub

Feature/Enhancement moved to ADO board for tracking

This Feature/Enhancement completed for Terraform.


Add support for Postgres UUID arrays using JDBC

We now use Postgres' JDBC drivers TypeInfoCache to register and determine array types, including support for UUID.
Closes #1567

LGTM!

Thanks, that's merged.


rclone serve restic processes left behind

I have noticed that after playing with rustic I always have rclone serve restic processes left behind and running, e.g.:
$ ps -ef | grep rclone
  501 25941     1   0 Fri05PM ??         0:13.96 rclone serve restic onedrive:restic-VM --addr localhost:0
  501  5407     1   0 Thu09PM ttys003    2:34.60 rclone serve restic OD01-ENC:restic-test --addr localhost:0
  501 12210     1   0 Fri07AM ttys003    0:15.61 rclone serve restic OD01-ENC:restic-test --addr localhost:0

It would mean that sometimes when rustic is terminated it does not stop rclone instance it is using.
I have not identified yet reproducible conditions but I see it daily so it is not something exceptional.

duplicate of https://github.com/rustic-rs/rustic_core/issues/22
Actually I cannot yet explain why this is happening. But I can confirm that I also had left-over rclone instances. But it seem I'm not having them for my regular scheduled backups. So my theory is that either backup is not affected or that systemd-scheduled runs are not affected...

Actually, I thought that when the rclone backend is dropped, it will always call a kill on the created subprocess. Technically the Child process is wrapped in an Arc and kill is called just before the containing Child is dropped. For panicking rustic runs, this could cause left-over child processes.  But it seems, we also have this for normally terminating runs...Maybe the Arc gets never dropped? In this case, https://github.com/rustic-rs/rustic_core/pull/73 might help as with this PR, a backend no longer needs to be Copy and we can remove the Arc.
About systemd runs. IIRC, systemd would take care about subprocesses and also kill them - this would explain why this is not observable with systemd.

I did some other tests and can say that I can reproduce the behavior when I manually run rustic check.
Now I'll try if #73 fixed that...

Unfortunately, #73 didn't fix it.. I'll have to take a deeper look into where things could go wrong...

I think I found the reason, see https://github.com/rustic-rs/rustic_core/issues/22

closed via https://github.com/rustic-rs/rustic_core/pull/139


Test coverage

Purpose

...

Does this introduce a breaking change?

[ ] Yes
[ ] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Test the code

What to Check
Verify that the following are valid

...

Other Information

Thank you for the PR. I'll move the pipeline files to their own folder.

Is this PR missing any files?

Closing for now. Feel free to reopen with more information.


Bug/update axios base

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fuzzing emptyish rooms

Rooms with less than a certain threshold (5 people or a percentage) should fuzz activity to always contain active machines of that threshold
The idea here is to make it impossible for people to be "targeted" if a room is shown to be have only one occupant

has this been a problem in the past?


Explore using Bloom filter for id field index to optimize read performance

Opensearch uses FST data structure to store document ids and then searches for it as a term query. Document id queries are generally "does_exist" for most use-cases. Bloom filter is known to perform better for such queries. We will explore this data structure to store document ids and then measure read performance for various usecases:

Mostly appends
Upserts, but no updates. Equal number of appends and upserts
Both updates and appends

This is a spin off from a discussion captured here

While analysing updates, I found FST lookups to be taking time as well, and started exploring bloom filter based postings for id field, and worked on a POC for the same: https://github.com/mgodwan/OpenSearch/compare/d76614cb4f071989da04d0976c1227b8943e5b61..02a344004413d39b08d882cc2b04321808682909
Upon running the same for NYC Taxis dataset with 25% conflict probability, we see gains in indexing throughput of the order of ~30%
Following are the results of the benchmarks for the same (7 runs for each code):

Following is a differential flame graph for the CPU usage analysis:

Based on the above results, I think we should look into exposing this as an opt-in feature to start with while working to optimize the usage of bloom filters internally, and potentially exposing this as a data structure for other fields.
In parallel, we can continue to investigate on the optimizations on the impact this introduces on JVM, Storage, and get/search paths(if any) to promote this towards a default feature for indices.
@shwetathareja @backslasht @dblock @itiyama
Looking forward to your thoughts on this.

@mgodwan - Thanks for the experiments. With approx. 2% increase in disk size, 20%+ decrease in latency is great.
We should definitely consider to bring it as opt-in feature. Are you thinking of exposing conflict probability as an option as well?

@mgodwan This are great results. Any reason for choosing this as an opt-in instead of default? I am aware that some users piggyback on term features on the id field, but I am thinking that going forward we should disable term features and just use id as a mechanism for does_exist or get kind of queries so that the optimizations can be more tailored towards these type of queries.

The nos. look great.  +1 @mgodwan to offer this as opt in/ experimental features with setting to configure the false positive %. @itiyama , it is pending full scale testing to evaluate the impact impact on JVM/ CPU with different workloads. And, also how it impacts merging before marking it production ready.
@mgodwan, Lets try to make it to 2.10 release as opt-in feature.

From a feature perspective, we can explore the following as well:
Thanks folks for the comments.

We should definitely consider to bring it as opt-in feature. Are you thinking of exposing conflict probability as an option as well?

@backslasht Yes, we can expose the false positive probability as an argument as it provides trade-offs between jvm/storage usage and the throughput improvement we observe for update use cases.

Any reason for choosing this as an opt-in instead of default?
@itiyama For append-only use cases with auto-generated ids, this may not help and add additional compute/memory/storage overhead. Also, we are still profiling the overall resource utilization the new data structure results in to take more informed decision.

I am thinking that going forward we should disable term features and just use id as a mechanism for does_exist

I agree that it will help optimize on the majority of use cases where FST may be an overhead. I think we can track a separate issue for evaluating the underlying deterministic structure.

Thanks folks for the comments.

We should definitely consider to bring it as opt-in feature. Are you thinking of exposing conflict probability as an option as well?

@backslasht Yes, we can expose the false positive probability as an argument as it provides trade-offs between jvm/storage usage and the throughput improvement we observe for update use cases.

Any reason for choosing this as an opt-in instead of default?

@itiyama For append-only use cases with auto-generated ids, this may not help and add additional compute/memory/storage overhead. Also, we are still profiling the overall resource utilization the new data structure results in to take more informed decision.

I am thinking that going forward we should disable term features and just use id as a mechanism for does_exist

@itiyama I agree that it will help optimize on the majority of use cases where FST may be an overhead. I think we can track a separate issue for evaluating the underlying deterministic structure.

@shwetathareja @backslasht
The Bloom filter implementation in Lucene is part of the Lucene's codecs extensions, outside of Lucene core.
Digging further on the same, while exploring the existing implementation in Lucene and seeing the past changes (example), it seems like the implementation has been changed in the past, as it is marked experimental, and does not provide direct support for backward compatibility among Lucene versions.
This may be concerning for us to support version upgrades, and may require us to use an implementation which can ensure backwards compatibility.
Hence, I wanted to discuss:

Is it alright to provide this as an experimental feature flag gated setting in 2.10 given these constraints as it provides opportunity to gather customer feedback on the feature? This will restrict the upgrades for indices using the bloom filter postings when Lucene implementations change, unless customers disable bloom filters through re-index/force merge old segments into new.

We may need explore if it may be beneficial to use the code from Lucene's implementation and ensure backwards compatibility on it. This adds extra maintenance overhead for us but also provides more control, and opportunities to add support for more forms of fuzzy sets (e.g. https://arxiv.org/pdf/1912.08258.pdf) to optimize on.

Is it alright to provide this as an experimental feature flag gated setting in 2.10 given these constraints as it provides opportunity to gather customer feedback on the feature? This will restrict the upgrades for indices using the bloom filter postings when Lucene implementations change, unless customers disable bloom filters through re-index/force merge old segments into new.

Generally, we don't provide backward compatibility guarantees for experimental features. We would need to call it out explicitly as well. Do you know the reason why it is not part of Lucene core codecs?

Backward compatibility is must.
I agree with @shwetathareja, if backward compatibility is not supported, lets review our approach.

Do you know the reason why it is not part of Lucene core codecs?

Looks like only codecs in core are supported for backward compatibility. This is marked experimental along with other extension codecs (although it has been present for a long time in the Lucene repository) due to which the guarantees for backward compatibility may not apply. I can open an issue in the Lucene repo to discuss this with the community.

If backward compatibility is not supported, lets review our approach.

I agree.
This can be achieved through an extension of Lucene's PostingsFormat which can implement a postings format similar to Lucene's while adding needed semantics for ensuring backward compatibility. Are we open to introducing custom codecs like this in OpenSearch core?

This can be achieved through an extension of Lucene's PostingsFormat which can implement a postings format similar to Lucene's while adding needed semantics for ensuring backward compatibility. Are we open to introducing custom codecs like this in OpenSearch core?

We recently introduced ZStd as a custom codec (https://github.com/opensearch-project/OpenSearch/pull/9658) and there are more to come (Snappy). If via custom codec we can support backward compatibility, worth giving it a try.

For the bloom filter implementation, following is the throughput observed with varying false positive probabilities:

The storage/memory variation for different false positive probability on nyc_taxis dataset is as follows:

I'm working on collating the results for an XOR Filter implementation as well with same parameters.
Will update the issue with the same.

I worked on comparing different fuzzy set implementations over the past few days. Following is a comparison of the same with similar size overhead:

We observe XOR Filter to be providing the highest reported indexing throughput among the implementations. Although, this comes at the cost of higher construction time and JVM overhead during construction (XOR Filter implementation POC is based off of https://github.com/FastFilter/fastfilter_java)

Following is a result of micro-benchmarks performed using JMH to profile filter construction times:
Filter Construction
Benchmark                                (numIds)  (setTypeAlias)  Mode  Cnt      Score       Error  Units
FilterConstructionBenchmark.buildFilter   1000000    bloom_filter  avgt    3     26.229 ±     9.165  ms/op
FilterConstructionBenchmark.buildFilter   1000000      xor_filter  avgt    3     78.331 ±    27.188  ms/op
FilterConstructionBenchmark.buildFilter   1000000   cuckoo_filter  avgt    3     52.045 ±     9.371  ms/op
FilterConstructionBenchmark.buildFilter  10000000    bloom_filter  avgt    3    422.899 ±   578.249  ms/op
FilterConstructionBenchmark.buildFilter  10000000      xor_filter  avgt    3   2363.247 ±   781.973  ms/op
FilterConstructionBenchmark.buildFilter  10000000   cuckoo_filter  avgt    3    943.940 ±  1622.361  ms/op
FilterConstructionBenchmark.buildFilter  50000000    bloom_filter  avgt    3   8545.999 ±  1791.090  ms/op
FilterConstructionBenchmark.buildFilter  50000000      xor_filter  avgt    3  20415.212 ± 26552.341  ms/op
FilterConstructionBenchmark.buildFilter  50000000   cuckoo_filter  avgt    3  10126.537 ±   887.455  ms/op

Side note: While trying to use existing cuckoo filter implementation in OpenSearch, I encountered an issue: https://github.com/opensearch-project/OpenSearch/issues/10582
Will fix it separately.

@mgodwan : do you also see scope of improvement in XOR filter construction considering it is providing better throughput and lower latencies as compared to bloom and cuckoo filter?

@shwetathareja The implementation used for xor filter was based on https://arxiv.org/pdf/1912.08258.pdf, where the mapping step requires few auxiliary data structures which consume the high memory during construction. There was no evident way to get rid of the same during the experiments.

Hi, are we on track for this to be released in 2.12 ?

@kiranprakash154  yes we are targeting 2.12 for the release of bloom filter support for DocumentId in OpenSearch


cmd: pending plots changes by 1.0 release

Extracted from https://github.com/iterative/dvc.org/pull/1382#issuecomment-640435301 et al.

[x] Apply changes from iterative/dvc/pull/3963 once that is merged. - https://github.com/iterative/dvc.org/issues/1414#issuecomment-730566207
[x] Add YAML and TSV examples to plot show? Or maybe just translate JSON example to YAML and CSV to TSV.
[x] Per https://github.com/iterative/dvc.org/pull/1382#pullrequestreview-427733327 double check about "All plots are used" in plot show -h usage (targets arg). - https://github.com/iterative/dvc.org/issues/1414#issuecomment-730558360
[x] modify: how to make a regular output into a plot? See https://github.com/iterative/dvc/pull/3994#pullrequestreview-429085947 - #1946
Review term "props" in plots commands once the code base is final/stable (per https://github.com/iterative/dvc.org/pull/1382#pullrequestreview-427522723)
[x] term: "column index" vs "column number"? See https://github.com/iterative/dvc.org/pull/1382#discussion_r438996574 and https://github.com/iterative/dvc.org/pull/1382#pullrequestreview-427729775 - #1946
[x] For JSON plot files we say "every object should have the same structure" but actually I'm not sure what the exact restriction is. Ask/test/check. See https://github.com/iterative/dvc.org/pull/1382#pullrequestreview-427730625
Double check how to apply all Vega spec props in plots: modify subcmd only has a limited no. of options. Why isn't it like dvc config BTW, where you can give any key/value pair (core repo Q)? Moved to iterative/dvc/issues/4909

EXTRA: Possibly change the modify example explained in https://github.com/iterative/dvc.org/pull/1382#discussion_r436435646
EXTRA: Maybe address some of the discrepancies mentioned in this https://github.com/iterative/dvc.org/pull/1380#issuecomment-640181973
EXTRA: Is plots diff really a diff? See discussion in https://github.com/iterative/dvc.org/pull/1382#pullrequestreview-427524008
EXTRA: See #1800

@imhardikj some answers to https://github.com/iterative/dvc.org/pull/1946#issuecomment-727563679:

Apply changes from iterative/dvc/pull/3963

These changes are already applied

No, they're not. Several cmd ref Synopsis/usage sections and maybe some option descriptions still need the updates, I think (please double check).

maybe just translate JSON example to YAML and CSV to TSV

But this will result in same plot

Just add an expandable section under the sample data of https://dvc.org/doc/command-reference/plots/show#example-hierarchical-data to show how it looks in other formats. (Changing the extensions in some other unrelated sections doesn't sound like a useful alternative BTW.)

Per https://github.com/iterative/dvc.org/pull/1382#pullrequestreview-427733327

I checked this with examples which has 2 and 3 plot files, plots show generated image with 2 and 3 plots respectively.

Sounds good. Can you share the example dvc.yaml file with 2-3 plots though? And DVC version, command, and result. Thanks

@imhardikj remaining answers to https://github.com/iterative/dvc.org/pull/1946#issuecomment-727563679:

For JSON plot files we say "every object should have the same structure" but actually I'm not sure... Ask/test/check

doesn't hold true...

OK that's great investigation from your part, with the plots example and everything. So we need to update the plots ref(s) to explain what the behavior and restrictions (if any) are. 1. Update the description of <DVC_METRIC_Y> to specify only the first row matters; 2. Update the text in the plots index to something like "array of consistent objects is expected: " (also not sure "expected" is the right term, feel free to rewrite the whole paragraph if needed).
Please do that update in it's own PR.

Double check how to apply all Vega spec props...

I passed properties like this... dvc plots modify logs.csv --width 1000

Why did you expect arbitrary -- flags to have an effect? The valid options for the command are listed in https://dvc.org/doc/command-reference/plots/modify#options and no others will work (did it give you an error message, BTW?).
Some of the options (from x to title correspond to Vega properties). You can learn more about Vega and how it relates to DVC plots here: https://dvc.org/doc/command-reference/plots/show#example-vega-specification-file.
The question was whether it's possible to modify any other Vega props other than the options that the modify command provides. I guess probably only via a custom template (see https://dvc.org/doc/command-reference/plots#plot-templates).
This topic is a bit advanced so feel free to give it a shot to understand and if you can come up with a new section or example somewhere on how to modify any Vega property that would be great but don't worry too much about it. It's not key info we need to provide (I'm removing the check box for now). Thanks

Can you share the example dvc.yaml file with 2-3 plots though

@jorgeorpinel  I used dvc.yaml from example-get-staretd. I modified plots in evaluate stage like this:
- prc.json:
        ...
- prc1.json:
        ...
- prc2.json:
        ...

Edited similarly in evaluate.py to generate these files.. I changed x and y fields so plots are different
Command:
$ dvc plots show

Result:

DVC version:
$ dvc version
DVC version: 1.10.0 (pip)
---------------------------------
Platform: Python 3.6.9 on Linux-4.19.112+-x86_64-with-Ubuntu-18.04-bionic
Supports: All remotes
Cache types: hardlink, symlink
Cache directory: overlay on overlay
Workspace directory: overlay on overlay
Repo: dvc, git

Apply changes from iterative/dvc/pull/3963

These changes are already applied

No, they're not. Several cmd ref Synopsis/usage sections and maybe some option descriptions still need the updates.

I checked all changes in iterative/dvc/pull/3963 and those are already there in metrics and plot docs. I think all are covered by #1382 and #1444. One thing migth plots diff description as per https://github.com/iterative/dvc/pull/3963#pullrequestreview-426996969
According to review I think "Show multiple versions of plot metrics by overlaying them in a single plot." should be changed to "Show multiple versions of plot metrics by overlaying them in a single image."

Thanks for the evidence! 🙏

already there in metrics and plot docs

I guess you're right. I was thrown off by the PR you mentioned first (#1382) which does not address that. But #1444 does. I'll mark the check box here for now! Thanks

One thing migth plots diff description...

Yeah let's just double check that all other metrics and plots usage blocks correspond to the -h help output of the commands on the latest DVC version (1.9.1) please @imhardikj.

Closed by #2075 but I forgot remove it's draft status before merging...

Closed by #2075 but I forgot remove it's draft status before merging...


confirm prompt coming twice with yii2 latest version

',
                ['add/remove-img','id'=>$file->id],
                [
                  'data' => [
                     'method' => 'post',
		      'confirm' => 'Confirm msg'
                       ],
                                                        ]
                                                        )?>

now this is the issue with ref with #6642 here confirm prompt coming twice..

When does the issue occur?

when trying to generate confirm prompt on HTML::a tag using data['confirm']

What do you see?

prompt shows twice. once i click on then again shows same prompt

What was the expected result?

it should work only once.

So it's just HTML::a without any form tags or PJAX?

yes its just HTML::a tag in but yes its in form but not with $form object.

Then please edit 1st post to contain full example on how to reproduce it. Thanks.

My code for "delete" button in ActionColumn:
`'delete' => function ($url, $model, $key) {
$url = \yii\helpers\Url::to(['/url/delete', 'id' => $model->id]);
                        return Html::a('', $url, [
                            'title' => 'Удалить',
                            'class' => 'btn btn-sm btn-default',
                            'data-method' => 'post',
                            'data-pjax' => 1,
                            'data-confirm' => 'Вы уверены, что хотите удалить это правило?',
                        ]);
                    },`

If i put a grid in the form (ActiveForm) - prompt coming twice.
Without "form" around grid - prompt appears only once.

One more thing. Are you able to reproduce the same issue using code from master branch?

<?php $form = ActiveForm::begin([         'action' => 'clone',         'method' => 'POST',     ]); ?>                 <?= GridView::widget([                     'dataProvider' => $dataProvider,                     'columns' => [                         ['class' => 'yii\grid\SerialColumn'],                         'Descripcion',                         [                             'class' => 'yii\grid\CheckboxColumn',                             'multiple' => true                         ],                     ],                 ]); ?>
             <?= Html::submitButton('Duplicar preguntas seleccionadas', [                 'class' => 'btn btn-success',                 'data' => [                     'confirm' => '¿Está seguro?',                 ],             ]) ?>
     <?php ActiveForm::end(); ?>
Same problem without PJAX... v2.0.10

Hi, having the same issue since 2.0.10
You need to place your link with data-confirm attribute INSIDE yii ActiveForm to reproduce this bug.
So the click event and confirm dialog seem to be fired twice after that.

Closing this issue as a duplicate of #13255.
Please, visit issue #13255 to continue conversation


Submission of Part 2 - Modelling Framework

Dear @donotdespair
I just committed my submission for Part 2 - Modelling Framework (5254e4a6d0b28dbab481a51e09e08fdb1a6b30b0) and was hoping to submit it on LMS. However, the submission link seems to be closed. May I know how I should submit my work for Part 2?
Thank you very much.
Respectfully,
Ray

Thanks for letting me know, @rayccg!
I have now extended the availability of the assignements.


exorcisation, gusto

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 100
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[e,g]

/trunk merge


Auto mark: never render rect; move zero-ness to autoSpec

Still pretty rough… head's spinning a bit from all the combinations.
Fixes https://github.com/observablehq/plot/issues/1340 by preferring rectY over rect… but that messes with our zero-ness heuristic, which depended on the inferred mark implementation. Moved that logic to autoSpec but haven't fixed it in the heatmap case yet.
Fixes https://github.com/observablehq/plot/issues/1365 by partially reverting https://github.com/observablehq/plot/commit/6eab4f235808d7deae1a75373ed20b4b3fbfbb08 's changes to how we decide the mark type.
To-do:

[x] Fix heatmap issue: only default to zero-ness if the bar is "standing on" the baseline, i.e. doesn't have both x1 & x2 or y1 & y2 set
[x] Materialize less often?
[ ] Fix tests

Questions:

Should setting zero change which mark renders?

In the autoBarZero, zero was being used as a cue that we could draw bars instead of dots. I wonder if that's the right heuristic. The more salient thing about that dataset might be that there's exactly one data point per domain value?
Should setting zero change a line to an area? Areas' guarantee of a meaningful zero do distinguish them from lines, but lines could also have a meaningful zero. Area implies zero but zero doesn't imply area.
If someone has a temperature chart, they probably only expect setting zero to add a line. But maybe you shouldn't use zero for that?
Overall, it feels too "clever" and too surprising for setting zero to change the mark. But doesn't it feel wrong that you can't automatically get a bar chart from the alphabet dataset?

Current broken tests
Definitely gotta fix the heatmaps. The alphabet example I'm not sure about; maybe people should just have to specify bar there. The mean zero going back to being a line feels OK.

Before
After

The heatmap examples are now fixed by checking !colorReduce. Would that ever fail? I mean, culmen length and body mass both have meaningful zeros, but I still don't expect or want the baselines there, because the values aren't encoded by the length of the bars, only their position.
Binning / grouping should never change the zero-ness of anything, right? In a histogram, the binning is on the other dimension from the one with the meaningful zero.
In this PR we now have two places where we assert zero-ness: before inferring the mark type, and after. I'm trying to think through whether that makes sense. Before, we check only if a zero reducer has been applied. After, we check if we've picked a mark that has to "stand on" a baseline. That feels sorta reasonable?
For the autoBarZero test (the simple bar chart of alphabet), here's a demo of an alternate heuristic that prefers bars when there's one data point for each value in an ordinal domain. (But really it should probably depend on that and zero-ness.) https://observablehq.com/d/ac53225f9c7e967b

Paired with Mike. To move the zero-ness determination into autoSpec (which would move it above the determination of mark and transform implementations), we started down the road of mirroring the logic for deciding the mark and transform implementations, since zero-ness depends on that. But that started to feel like a boondoggle; we're going to refactor a bit, but the sequence of the logic will stay more similar to how it is now.
Here's my current understanding of how it should work:

The mark type (line, bar, area…) depends only on the chosen fields and reducers, never on zero-ness. Picking a zero reducer (count, sum…) may affect the mark type, but passing in zero: true won't.
The mark implementation (barX, barY) may depend on zero-ness, because, when there are three channels we need to fill (either x, y1, and y2 or y, x1, and x2) but only two channels specified in options (x and y), we need to infer whether x1 should be inferred to be 0, or y1 should be inferred to be 0.

TODO: Should this really depend on the zero option the user passes in, or does it only depend on if you've specified a zero reducer on that dimension?

The transform implementation does not depend on zero-ness.
The zero-ness, if still undefined, is chosen based on the mark and transform implementations. A dimension is zero-ful if it's defined, we're not binning along that dimension, and the mark is a bar, area, rect, or rule extending continuously along that dimension. At that point it affects only whether a baseline is drawn.

And here's a sketch of the refactoring. The public interfaces for autoSpec and auto won't change, but the bulk of the logic — formerly all held in auto, then split into auto and autoSpec — will be re-consolidated in a new private function, autoImpl.
// expose information about what would be done; don't instantiate
export function autoSpec(data, options) {
    const {x, y, fx, fy, color, size, mark} = autoImpl(data, options);
    return {x, y, fx, fy, color, size, mark};
}

// decide mark and transform implementations and anything that was undefined in options; everything but instantiating
function autoImpl(data, options) {
    // most of the auto logic gets re-consolidated here
    return {...options, markImpl, markOptions, transformImpl, transformOptions}
}

// actually instantiate; just the last few lines of today's auto
export function auto(data, options) {
    const {markImpl, markOptions, transformImpl, transformOptions, xZero, yZero, fx, fy, colorMode} = autoImpl(data, options)
    return marks(/* ... */);
}

OK, the only remaining two snapshot test failures are deliberate consequences of the change in philosophy to say that mark type should never depend on zero-ness. I've updated the tests so they won't fail any more, and updated the names: autoBarZero → autoDotZero; autoBarMeanZero → autoLineMeanZero.

Code
Before
After

alphabet, {x: {value: "frequency", zero: true}, y: "letter"}

weather, {x: "date", y: {value: "temp_max", reduce: "mean", zero: true}}

For the second one, it was already a bit of a toss-up which way we'd want to see. The first one's a bit of a shame; it feels a little weird that you can never get a simple bar chart from auto except by asking for it. 🤷
(Philosophical aside! I think part of the auto philosophy is that we should be able to infer mark types from information about the data. It feels nice to me to describe that property of the data that makes it deserve the mark, rather than just asking for the mark; it moves the location of human input upstream, so that we could potentially make other decisions based on it. The human annotation of zero-ness could also inform color scales, whereas the human annotation of bar-ness doesn't generalize so well. Better yet, if zero-ness were part of the table schema rather than part of the chart config, it could produce better defaults for all charts of that data. That feels like a good academic topic: what sorts of stronger types could we annotate numbers with to produce better default displays?)

I had my li’l auto matrix test, which works nicely in the Vite live preview:
export async function autoMatrix() {
  return htl.html`<div style="display: flex; flex-wrap: wrap;">
    <style>svg { width: 320px; }</style>
    ${await autoHistogram()}
    ${await autoDotZero()}
    ${await autoLineZero()}
    ${/* etc */}
  </div>`
}

But when I run yarn test I get:
  1) plot autoMatrix:
     TypeError: Cannot read properties of null (reading 'replace')
      at reindexStyle (file:///Users/toph/Development/plot/test/plot.js:74:62)
      at file:///Users/toph/Development/plot/test/plot.js:16:5
      at async Context.<anonymous> (file:///Users/toph/Development/plot/test/jsdom.js:29:14)

Because test/plot.js expects every top-level node to be a plot. If you think it'd be valuable to have I can try to make that work, but for now I took it out.

To fix the autoMatrix test we just need this tiny change:
--- a/test/plot.js
+++ b/test/plot.js
@@ -71,7 +71,7 @@ function reindexStyle(root) {
     const parent = style.parentNode;
     const uid = parent.getAttribute("class");
     for (const child of [parent, ...parent.querySelectorAll("[class]")]) {
-      child.setAttribute("class", child.getAttribute("class").replace(new RegExp(`\\b${uid}\\b`, "g"), name));
+      child.setAttribute("class", child.getAttribute("class")?.replace(new RegExp(`\\b${uid}\\b`, "g"), name));
     }
     style.textContent = style.textContent.replace(new RegExp(`[.]${uid}`, "g"), `.${name}`);
   }

To fix the autoMatrix test we just need this tiny change

Oooh, easy, thanks Fil! I'm gonna make that a separate PR because I also wanna think about which plots should actually be in the matrix and whether it makes sense to have that kind of redundancy. (Feels a little weird that the matrix is useful for looking at the live results, but doesn't add any coverage for the automated testing.)

I don’t think we should add the redundant matrix test. That was just an idea for debugging this problem.


git lfs pull ERROR

cannot pull .pt files in act_scales.
When run:
git lfs pull

got ERROR:
batch response: This repository is over its data quota. Account responsible for LFS bandwidth should purchase more data packs to restore access.

I also encountered the same problem, did you solve it?


Roll engine 3713ecf10728..9fd35df9bb47 (1 commits)

git@github.com:flutter/engine.git/compare/3713ecf10728...9fd35df9bb47
git log 3713ecf10728..9fd35df9bb47 --no-merges --oneline
2019-09-26<EMAIL_ADDRESS>Roll src/third_party/dart c6a14f4459..dd65f97118 (3 commits)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

Auto-roller completed checks. About to merge.


Add global custom queries feature for postgres

What does this PR do?
Adds support for global custom queries for the postgres integration.
Motivation
We run the same set of custom queries against multiple postgres databases. This feature will help to reduce the number of duplicate lines in the config file.
Additional Notes
All tests have passed locally.
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Changelog entries must be created for modifications to shipped code
[ ] Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
[ ] If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

@database-monitoring-agent Please review.


reduce enum array allocation in TimerContext

Motivation
reduce enum array allocation in TimerContext
Modifications
cache ServerQueryPhase.values().length in a static variable
Result
ServerQueryPhase.values() method is invoked exactly once
Additional context
https://www.gamlor.info/wordpress/2017/08/javas-enum-values-hidden-allocations/

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 61.62%. Comparing base (59551e4) to head (b1692a6).
Report is 71 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff              @@
##             master   #12579      +/-   ##
============================================
- Coverage     61.75%   61.62%   -0.13%
- Complexity      207      211       +4
============================================
  Files          2436     2451      +15
  Lines        133233   133733     +500
  Branches      20636    20704      +68
============================================
+ Hits          82274    82419     +145
- Misses        44911    45204     +293
- Partials       6048     6110      +62

Flag
Coverage Δ

custom-integration1
<0.01% <0.00%> (-0.01%)
:arrow_down:

integration
<0.01% <0.00%> (-0.01%)
:arrow_down:

integration1
<0.01% <0.00%> (-0.01%)
:arrow_down:

integration2
0.00% <0.00%> (ø)

java-11
27.65% <0.00%> (-34.06%)
:arrow_down:

java-21
61.62% <100.00%> (+<0.01%)
:arrow_up:

skip-bytebuffers-false
61.57% <100.00%> (-0.18%)
:arrow_down:

skip-bytebuffers-true
61.60% <100.00%> (+33.88%)
:arrow_up:

temurin
61.62% <100.00%> (-0.13%)
:arrow_down:

unittests
61.62% <100.00%> (-0.13%)
:arrow_down:

unittests1
46.76% <100.00%> (-0.13%)
:arrow_down:

unittests2
27.68% <0.00%> (-0.05%)
:arrow_down:

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Test refactors

Purpose *
Help me understand whats going on.
Small refactors in tests, ran mix format made additional changes

Merged. Great to see you find this library helpful and contributing 👍


Rob: Watch stoxmarket.com

Rob requests the watch of the watch_keyword stoxmarket\.com. See the Metasmoke search here and the Stack Exchange search here.

stoxmarket\.com has been seen in 0 true positives, 0 false positives, and 0 NAAs.

https://stackoverflow.com/questions/51075383

Coverage remained the same at 65.13% when pulling 3dbc9dcee12472ead09faf393a61efa5b5c93125 on auto-blacklist-1530165354.328128 into f451bf682e09e54db92d4d160f90eaf2f86f7a36 on master.

!!/approve


Use Cuddle to define CDDL in Shelley

Description
This addresses issue #4462

Moves some core type CDDL definitions to cardano-ledger-core
Defines Shelley CDDL types through Huddle
Adds huddle-based testing in Shelley
Moves the Shelley CDDL to being auto-generated via the Huddle def
Updates Conway to use some definitions from Shelley where they were unchanged
Updates the gen-cddl.sh script to check Shelley definitions

One unexpected change: the huddle definition for protocol_param_updates has a size limit on the max block header size. This is consistent with the Haskell serialisers and data structure.
Checklist

[x] Commit sequence broadly makes sense and commits have useful messages
[x] New tests are added if needed and existing tests are updated
[ ] All visible changes are prepended to the latest section of a CHANGELOG.md for the affected packages.
New section is never added with the code changes. (See RELEASING.md)
[x] When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
versioning process.
[ ] The version bounds in .cabal files for all affected packages are updated.
If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
[x] Code is formatted with fourmolu (use scripts/fourmolize.sh)
[x] Cabal files are formatted (use scripts/cabal-format.sh)
[x] hie.yaml has been updated (use scripts/gen-hie.sh)
[x] Self-reviewed the diff

Closing this in favour of #4553


Pipewire config that adds custom nodes for Wave XLR might be incorrect.

The change was made to make pipewire start successfully with custom config for Wave XLR after upgrade from 1.2.6-1 to 1.2.7-1
https://github.com/jmansar/wavexlr-on-linux-cfg/pull/2
The error was:
Could not determine card index, maybe set api.alsa.card

The change was to  set api.alsa.card instead of api.alsa.path which seemed to work.
Related change in pipewire that introduced the error:
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/ff63ca4d3633bf383ab32b4f6bd95612ecbcb9e7
However, after further investigation of pipewire code base, it's likely not the correct thing to do.
The suggestion to use api.alsa.card in the logs was later changed: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/4c09451e77ea5a9e537a2ebbf27304d0ad3fcc20
Also, it doesn't look like the code expects to use device alias (XLR) as device number as it attempts to parse it into a number.
Find out the correct way to point to Wave XLR device in pipewire config that does not rely on card number.

Reverted the change for now.


IE11 compatibility

when i print from IE11 i got a blank page.

Thanks.
I haven't done much IE testing so I will look into this

@hameddhib sorry for the delay.
I've just done some testing in both IE11 and IE10, I don't seem to be experiencing the same issues as you, can you perhaps send me a plnkr with the same behaviour you're seeing?
See if these examples work. That's what I'm testing off of.
https://rpdasilva.github.io/print-html-element/


Troubles with DELL

Hello,
I use Driver Automation tool so today I have problem with download of DELL.
It does not download Drivers catalog.
I received this error.

Is there exist some solution for fix this problem?
Thank you very much.
Lukas

started having this problem today, was working fine last week

Ok I fixed it. Go into msengpointmgr\Driver Automation Tool\Temp\ and delete everything. Launch the software.


Update package to casadi 3.2.2 and numpy 1.13

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Christmas day message

fix #38
Changed functionality
Now the Christmas day message will only display on the dedicated place on December 25 every year.
What I did

Created the scripts folder in order to create these sorts of small scripts
Added the div and p for the Christmas day message
Added the CSS styling for both of them
The display of the div is set none by default
In script implemented the condition that if the date is Dec 25 the set the div display to block otherwise to none

Screen Shoot

Thanks, I'm giving a review on this shortly.

ON Light mode: violet
ON Dark mode : dark green
Is this right?

ON Light mode: violet ON Dark mode : dark green Is this right?

I already merged this lol, I made it violet on light mode but didnt see if its too light on dark mode or no. Lemme see how it looks on dark mode.

@aliraza944 I had a look and its fine, not too bad but if you can make it dark-violet or purple in darkmode that would be great. Just make another PR, I didnt think about the color in darkmode lol

@aliraza944 I had a look and its fine, not too bad but if you can make it dark-violet or purple in darkmode that would be great. Just make another PR, I didnt think about the color in darkmode lol

So just do the changes, and I'll make a new release @aliraza944


OSError on script load. (time package error?)

Here is the code that I put in main.py:
import time
import random

while True:
    print(random.random())
    time.sleep(1)

While this works in the normal Python interpreter on my PC, 3DS.py throws this error:

Hello, the first problem is caused due to random.random() depending on the broken hashlib module. This is a known issue and a corresponding fix has already been supplied to my fork of CPython, which is going to be used in the WIP rewrite of 3DS.py.
For the time.sleep error, the issue is known as well, but I haven't found the time to look deeper into it yet. That's why I'm going to leave this issue open as some sort of progress tracker until a patch has been supplied to my Python fork.

I use this instead of time.sleep:
def sleep(seconds):
    start = time.monotonic()
    while(time.monotonic() < start + seconds):
        pass


遇到和之前几位一样的MONGODB后缀问题

Traceback (most recent call last):
File "scheduled_task.py", line 18, in
from owllook.spiders import QidianRankingSpider, ZHRankingSpider
File "/root/owllook/owllook/spiders/init.py", line 1, in
from .qidian_ranking import QidianRankingSpider
File "/root/owllook/owllook/spiders/qidian_ranking.py", line 8, in
from owllook.database.mongodb import MotorBaseOld
File "/root/owllook/owllook/database/mongodb/init.py", line 1, in
from .motorbase import MotorBase, MotorBaseOld, PyMongoDb
File "/root/owllook/owllook/database/mongodb/motorbase.py", line 11, in
@singleton
File "/root/owllook/owllook/database/mongodb/motorbase.py", line 19, in MotorBase
MONGODB = CONFIG.MONGODB
AttributeError: type object 'Config' has no attribute 'MONGODB'
false改了，没用

在config目录下建一个proconfig的文件将devconfig.py的内容给复制进去，就行了，


Private streams inconsistent UI position

When I open Zulip Desktop, the private streams are seperated with a nice line from the public streams.
Once I click on private messages on the top left, the line disappears and the private stream positions itself with the public ones.
Forcing a reload brings it back to the state with line and seperated.

The design here is intended to be that the separation is between streams that have recent traffic (in the last ~1200 messages or so) vs. streams that do not; this might align in your organization with whether the streams are public or private.  We also don't receive all of those messages immediately, so there can be an update to which streams are shown which way after a bit of time.
(Also, are any of these streams pinned?)
Could that explain what you're seeing?

OK, yes, that confirms my theory.  What's happening is that you have a private stream with little recent traffic, and when you click on "mentions", that fetches some older messages, including some that were sent to your private stream, and so Zulip now has recent messages for that stream in the local cache.
I think the fix here might be that it should only be being promoted when you actually click on the private stream (or receive a new message to it), not when you do a search/mentions narrow that contains a message on it.
(Also, it's very possible that we should re-introduce the feature that this fading only happens when you have >30 streams, since I feel like this fading feature is much less confusing if folks first see it when they're already longtime users)
@rishig @showell FYI.

thanks for the explanation!
For me, your proposed fixes would surely decrease the confusion about this switching.
I'm probably too used to slack UI where the private channels are visually seperated from the public ones. (not that I want it in zulip necessarily, but thats why my initial issue was phrased in that way)

Also, it's very possible that we should re-introduce the feature that this fading only happens when you have >30 streams,

Agreed (or ideally, we could set the number based on whether all the streams fit in the left sidebar.)

Closing, as the UI no longer uses lines/areas to separate streams.


output negotiated TLS1.3 group

This adds client-side output for TLS1.3 showing which group has actually been negotiated.

This pull request is ready to merge

Pushed. Thanks.


compaction: Consider merging chunks for the same series during compaction.

Proposal
Use case. Why is this important?
Compactions merge blocks. For chunks, however, it just appends chunks to the same set if they are for the same series: https://github.com/prometheus/prometheus/blob/3344bb5c332838df21f87b6473c0764315f5ca71/tsdb/compact.go#L1008
If we assume that chunks should cover 120 samples, during compaction we may end up with much smaller, inefficient chunks, especially with series with bigger scrape interval (15s -> 30m chunks; 1m -> 120m) or downsampled series (5m -> 10h; 1h -> 5d).
I would propose adding logic for chunk merging during the compaction process. I think we briefly mentioned this during the dev summit as well.
Any thoughts? (:

Didn't someone look at this before?

Actually dig further and we have some issues in archived TSDB:

https://github.com/prometheus/tsdb/issues/236
https://github.com/prometheus/tsdb/pull/397

I don't know why this issue ended up investigating chunks bigger than 120 samples chunks, I think it's clear it's not worth it.
The new information here is though downsampling, plus I think we tested only with 15s scrape interval (?). That's why it might be worth to repeat this test, but it's not a high priority. Also one of the arguments in the mentioned issue was that index size is not a big deal: For Thanos we see indexes beyond 30GB, so any improvement here is a win. As per older tests we might want to be careful to not make the compaction process taking to a lot longer.

The number of chunks makes no difference to index size.

I think it increases it a bit https://github.com/prometheus/tsdb/blob/master/docs/format/index.md#series but the question is how significant as we are talking only about edge chunks being potentially merged during compaction.

That's series, not chunks.

Each chunk has its entry in the index as far as I know (inside that series). That's the major contributor to the index size.

yes, so it can accumulate over compactions, especially for chunks that can be merged into 120 samples.

@bwplotka I can work on this if we have agreed on the idea of merging chunks : -)

Thanks! I think the agreement will be there only if we see benchmarking results that would confirm our reasoning here: chunks being partial for million of series on the edges of the block.

@irajdeep: As @bwplotka said the idea is still on but getting it upstream would depend on the benchmarks. Also, merging chunks is expensive. If you could implement it and benchmark, that would be great!

@codesome Is this still on? As per our bug scrub, it looks like for prometheus it would not really be a big performance gain.

I mean we are only guessing this. I think the key is to have some data first hot often this actually happens (that we have incomplete chunks).
Also, given the ideas we have for backfilling (which might result in small chunks) I think this is still worth checking out.
However I think, given that this affects mostly Thanos with downsampling, this issue should be rather tracked on Thanos board. Let's close for now (:

Moved to https://github.com/thanos-io/thanos/issues/2769

With https://github.com/prometheus/prometheus/issues/7396, it might be possible to have small chunks, though not in Prometheus as it will have 0 grace period. (all this assuming it will go in)


Add list of projects with dependencies on CF

We have not been great about updating the main projects that rely on being up to date with Capital Framework. Hopefully this handy checklist will help us keep track of what is and isn't updated after a release.

@Scotchester Updated all the projects to include some helpful details


Updated validation.py  python script

Corrected the behaviour of the validate_user function in validations.py
Closes: #1
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

@googlebot I signed it!


javax.usb.UsbPlatformException: USB error 12

when I am running I am getting error
javax.usb.UsbPlatformException: USB error 12: Unable to claim interface: Operation not supported or unimplemented on this platform
I have successfully run all high level examples.But when I run UsbInterface.claim() function I am getting this error.Usb devices that I have used is Webcam (made in china) ,HP Scanner,ZTE Modem.I have tested all three drivers WinUSB, libusb-win32 and libusbK  but all give same error.

I encountered the same problem.
Have you resolved this one?


I'm try to login with bluemix cli, but always get the following error

bluemix login  -a https://api.eu-gb.bluemix.net --sso --apikey
Get https://api.eu-gb.bluemix.net/v2/info: dial tcp <IP_ADDRESS>:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

The message indicated you were not able to connect <IP_ADDRESS> which is the IP address of api.eu-gb.bluemix.net
please check your network settings to see whether you can access url  https://api.eu-gb.bluemix.net/v2/info

by the way,  use 'bluemix login --sso' to login with one time passcode, use 'blueix login --apikey key or @keyfile' to login with api key or apikey file.


Ambiguous occurrence 'length'

Configuring hoodle-types-0.3.0...
Building hoodle-types-0.3.0...
Preprocessing library hoodle-types-0.3.0...
[ 1 of 12] Compiling Data.Hoodle.Primitive ( src/Data/Hoodle/Primitive.hs, dist/build/Data/Hoodle/Primitive.o )
[ 2 of 12] Compiling Data.Hoodle.Predefined ( src/Data/Hoodle/Predefined.hs, dist/build/Data/Hoodle/Predefined.o )
[ 3 of 12] Compiling Data.Hoodle.Util ( src/Data/Hoodle/Util.hs, dist/build/Data/Hoodle/Util.o )
[ 4 of 12] Compiling Data.Hoodle.Hashed ( src/Data/Hoodle/Hashed.hs, dist/build/Data/Hoodle/Hashed.o )
[ 5 of 12] Compiling Data.Hoodle.Simple.V0_1_1 ( src/Data/Hoodle/Simple/V0_1_1.hs, dist/build/Data/Hoodle/Simple/V0_1_1.o )
[ 6 of 12] Compiling Data.Hoodle.Simple.V0_2_2 ( src/Data/Hoodle/Simple/V0_2_2.hs, dist/build/Data/Hoodle/Simple/V0_2_2.o )
[ 7 of 12] Compiling Data.Hoodle.Simple.V0_3 ( src/Data/Hoodle/Simple/V0_3.hs, dist/build/Data/Hoodle/Simple/V0_3.o )
[ 8 of 12] Compiling Data.Hoodle.Simple ( src/Data/Hoodle/Simple.hs, dist/build/Data/Hoodle/Simple.o )
[ 9 of 12] Compiling Data.Hoodle.Generic ( src/Data/Hoodle/Generic.hs, dist/build/Data/Hoodle/Generic.o )
[10 of 12] Compiling Data.Hoodle.Zipper ( src/Data/Hoodle/Zipper.hs, dist/build/Data/Hoodle/Zipper.o )
src/Data/Hoodle/Zipper.hs:62:33:
Ambiguous occurrence ‘length’
It could refer to either ‘Data.Foldable.length’,
imported from ‘Data.Foldable’ at src/Data/Hoodle/Zipper.hs:22:1-20
or ‘Data.Sequence.length’,
imported from ‘Data.Sequence’ at src/Data/Hoodle/Zipper.hs:24:1-38
src/Data/Hoodle/Zipper.hs:62:46:
Ambiguous occurrence ‘length’
It could refer to either ‘Data.Foldable.length’,
imported from ‘Data.Foldable’ at src/Data/Hoodle/Zipper.hs:22:1-20
or ‘Data.Sequence.length’,
imported from ‘Data.Sequence’ at src/Data/Hoodle/Zipper.hs:24:1-38
src/Data/Hoodle/Zipper.hs:66:35:
Ambiguous occurrence ‘length’
It could refer to either ‘Data.Foldable.length’,
imported from ‘Data.Foldable’ at src/Data/Hoodle/Zipper.hs:22:1-20
or ‘Data.Sequence.length’,
imported from ‘Data.Sequence’ at src/Data/Hoodle/Zipper.hs:24:1-38
src/Data/Hoodle/Zipper.hs:98:15:
Ambiguous occurrence ‘length’
It could refer to either ‘Data.Foldable.length’,
imported from ‘Data.Foldable’ at src/Data/Hoodle/Zipper.hs:22:1-20
or ‘Data.Sequence.length’,
imported from ‘Data.Sequence’ at src/Data/Hoodle/Zipper.hs:24:1-38
src/Data/Hoodle/Zipper.hs:99:15:
Ambiguous occurrence ‘length’
It could refer to either ‘Data.Foldable.length’,
imported from ‘Data.Foldable’ at src/Data/Hoodle/Zipper.hs:22:1-20
or ‘Data.Sequence.length’,
imported from ‘Data.Sequence’ at src/Data/Hoodle/Zipper.hs:24:1-38

This prevents building hoodle in Stackage Nightly:

wavewave/hoodle#55
https://github.com/fpco/stackage/pull/1662#issuecomment-229371682


Shortcut doesn't open

when I chose a shortcut it says : catastrophic failure
can you fix it please
Thank you for the great Package,

It works on my machine. Could you please share the code you're using?
Here's the one I used:
import 'package:filepicker_windows/filepicker_windows.dart';

void main() {
  final file = OpenFilePicker()..title = 'Select a file';

  final result = file.getFile();
  if (result != null) {
    print(result.path);
  }
}

that's my code :
roby() {
final file = OpenFilePicker()..title = 'select a file';
final result = file.getFile();
if (result != null) {
return result.path;
}
}

Interesting, I have no idea why it doesn't work on your machine.

I found this on StackOverflow, which seems to be the same issue you're experiencing.
The answer got me thinking, can you clone this repository and add this line
options |= FILEOPENDIALOGOPTIONS.FOS_NODEREFERENCELINKS;

to open_file_picker.dart and run the example?

Just published a new version that has a new field: dereferenceLinks. By setting it to false, you can now directly open the shortcut file without resolving its target if that's what you want.


feat(WEB-1974): Disabling scroll for popup and slider

Jira Ticket - WEB-1974
Disabling the scrollbar preventing users to scroll when the popup or slider is open.
After closing it the scroll is back to its initial state.

:tada: This PR is included in version @typeform/embed-v1.9.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Show excludes in Excel report

Visualize excluded projects and scopes in the Excel report. See the commit messages for details.

This change is

Again, I didn't look deeply into the algorithm, but the formal aspects now look fine to me.


HTMLElement does not work with ReactNotifyMessageDetails

Describe the bug
ReactNotifyMessageDetails accepts MessageType = string | HTMLElement | ReactMessage as valid types for its detailedMessage prop. However, an error occurs when attempting to output a HTMLElement as a message using ReactNotifyMessageDetails with MessageManager.outputMessage.
To Reproduce
Steps to reproduce the behavior:
This sandbox reproduces the behavior:
ReactNotifyMessageDetails-does-not-support-html.
Please go to this sandbox and follow the instructions in the widget.
Current behavior
Error is thrown:
Objects are not valid as a React child (found: https://imjsdocumentprodeussa01.z13.web.core.windows.net/sandbox/compiler/index.html?lng=en&itwinid=402f1a92-c7b1-4012-b787-7fa45e2e7fe4&imodelid=b55dec38-d9b7-4029-9b9c-6b899151328f#). If you meant to render a collection of children, use an array instead.
Expected behavior
HTMLElement should be displayed in toast.

Hi, I'm currently working in this area, I'll check what's going on.

Hi @Alfonso-Martello, a fix for this was released today in 4.7.0. Let us know if this fixes your issue!


Mark if breaking change requires joined deployment

Feature Description
A breaking change in the UML should be markable if a joind deployment is required or not

Describe the solution you'd like

Extend JMM
Add new field to breaking changes report
Update comment in Java Code for breaking changes
Add info to breaking changes report

JMM revision 253 or higher supports default comment with new stereotype DefaultComment