x509: certificate relies on legacy Common Name field, use SANs or temporarily enable Common Name matching with GODEBUG=x509ignoreCN=0

While testing a preview build of the check_cert binary, the above error message was thrown when our Nagios instance used the Go 1.15-generated binary against a system without any SANs entries, but with the CommonName field set.
x509: certificate relies on legacy Common Name field, use SANs or temporarily enable Common Name matching with GODEBUG=x509ignoreCN=0

This problem was not surfaced when performing initial testing with the go1.15beta1 release as noted on GH-24.

This problem was not surfaced when performing initial testing with the go1.15beta1 release as noted on GH-24.

I tested again just now using the lscert-v0.1.1-4-gcaf56ac-dirty-linux-amd64 binary I generated on June 11th and it did have the same result as noted above. I'm guessing that I did not test the Go 1.15 changes against all servers in our fleet and only against the most common configurations.

https://golang.org/doc/go1.15#commonname

X.509 CommonName deprecation
The deprecated, legacy behavior of treating the CommonName field on X.509 certificates as a host name when no Subject Alternative Names are present is now disabled by default. It can be temporarily re-enabled by adding the value x509ignoreCN=0 to the GODEBUG environment variable.
Note that if the CommonName is an invalid host name, it's always ignored, regardless of GODEBUG settings. Invalid names include those with any characters other than letters, digits, hyphens and underscores, and those with empty labels or trailing dots.

It's probably worth toggling this setting on for both binaries at application startup.
The bigger question:
Is a certificate valid if no Subject Alternative Name is present?

https://support.dnsimple.com/articles/what-is-ssl-san/

From a technical standpoint, every certificate issued today is effectively a SAN certificate, as the CA/B forum requires the certification authority to add the content of the common name to the SAN as well. Even if the certificate covers a single name, it will still use the SAN extension and include that single name.

Since certificates have a limited lifetime, I expect the Go developer's assumption is that only very old, likely expired certificates will be missing a SANs entry.

https://medium.com/@sajithekanayaka/solved-java-security-cert-certificateexception-no-subject-alternative-names-present-eec1669faf0d

When the server certificate is having Subject Alternative Names (SAN), the requesting home name must match with one of the SANs. If the server’s SSL certificate does not have SANs, then the requesting home name must match with the Common Name (CN) of the certificate.

https://tools.ietf.org/html/rfc2818

If a subjectAltName extension of type dNSName is present, that MUST
be used as the identity. Otherwise, the (most specific) Common Name
field in the Subject field of the certificate MUST be used. Although
the use of the Common Name is existing practice, it is deprecated and
Certification Authorities are encouraged to use the dNSName instead.

It's probably worth toggling this setting on for both binaries at application startup.

I think this is what I'll end up doing. Not sure yet if by adding an additional flag (e.g., --force-common-name or --ignore-sans or ...).

It's probably worth toggling this setting on for both binaries at application startup.

This is worth noting:

All Go 1.15 changes landed. Moving to Go 1.16 to drop the opt-out.

https://github.com/golang/go/issues/24151#issuecomment-625558467
If I read that correctly, then the environment variable approach to disable the behavioral change would not make it into later Go versions.
Ultimately the certs that we're working with (locally generated by campus CA) would need to be replaced with certificates containing SANs entries (at least the single entry reflecting the DNS name).

Relevant bits from the stdlib (crypto/x509/verify.go:

// ignoreCN disables interpreting Common Name as a hostname. See issue 24151.
var ignoreCN = !strings.Contains(os.Getenv("GODEBUG"), "x509ignoreCN=0")

// ...

const (

// ...

	// NameConstraintsWithoutSANs results when a leaf certificate doesn't
	// contain a Subject Alternative Name extension, but a CA certificate
	// contains name constraints, and the Common Name can be interpreted as
	// a hostname.
	//
	// This error is only returned when legacy Common Name matching is enabled
	// by setting the GODEBUG environment variable to "x509ignoreCN=1". This
	// setting might be removed in the future.
	NameConstraintsWithoutSANs

// ...

)

// ...

// VerifyHostname returns nil if c is a valid certificate for the named host.
// Otherwise it returns an error describing the mismatch.
//
// IP addresses can be optionally enclosed in square brackets and are checked
// against the IPAddresses field. Other names are checked case insensitively
// against the DNSNames field. If the names are valid hostnames, the certificate
// fields can have a wildcard as the left-most label.
//
// The legacy Common Name field is ignored unless it's a valid hostname, the
// certificate doesn't have any Subject Alternative Names, and the GODEBUG
// environment variable is set to "x509ignoreCN=0". Support for Common Name is
// deprecated will be entirely removed in the future.
func (c *Certificate) VerifyHostname(h string) error {
// ...
}

Probably worth evaluating our fleet to determine just how many of the certs failing this check we're actually dealing with. If just one, then we can likely consider that a bug with the certificate and work towards getting it replaced.

Also relevant:

GH-17
GH-5

and:
https://github.com/atc0005/check-cert/blob/6d84f7741eb4db5cb63cdab624da3e42a353aea8/cmd/check_cert/main.go#L206-L214

Basically it's worth reconsidering support for ignoring SANs entries as part of resolving this. The two items would almost need to be considered together since they're related to the same overall issue.

Basically it's worth reconsidering support for ignoring SANs entries as part of resolving this.

While we are using the support for skipping SANs checks (on our Nagios system) for systems that didn't have them at all, we were also using the SKIPSANSCHECKS keyword for monitoring certs such as used by outlook.office365.com with 20+ SANs entries.
The current version of this tool assumes that if you list any SANs entries, then you want exactly those SANs entries to be present on the certificate. More or less than specified is considered an error condition.
All of that said, keeping the SKIPSANSCHECKS keyword support for now is probably the correct way to go for now.
We're replacing local certs without SANs entries, so I suspect we'll be fine with the Go 1.15 default behavior and going forward should be fine with Go 1.16 changes. Once the first beta release of 1.16 drops we can test further.

Probably worth evaluating our fleet to determine just how many of the certs failing this check we're actually dealing with. If just one, then we can likely consider that a bug with the certificate and work towards getting it replaced.

This is what we ended up doing.

We're replacing local certs without SANs entries, so I suspect we'll be fine with the Go 1.15 default behavior and going forward should be fine with Go 1.16 changes. Once the first beta release of 1.16 drops we can test further.

Still the mindset here.

From doc comments in the current codebase:
https://github.com/atc0005/check-cert/blob/aa19a9c4779df09b54de8bffb85adbe80df1e7f5/internal/certs/validation-hostname.go#L167-L171
Not sure what else to do here. Perhaps sufficient support is present to consider this worked around/resolved for now:

the SKIPSANSCHECKS keyword is still supported
explicit functionality is present to allow skipping SANs checks
support is present to allow skipping hostname validation if SANs entries are not present on a certificate

See also:

https://github.com/atc0005/check-cert/issues/520
https://github.com/atc0005/check-cert/issues/505


Heatmaps don't render on my instance

Gitea version (or commit ref): 1.7.3
Git version: 2.17.1
Operating system: Ubuntu 18.04.2 LTS (GNU/Linux 4.18.0-1011-azure x86_64)
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[x] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[x] No
[ ] Not relevant

Log gist:

Description
These errors show up in the console after a long time of waiting for AJAX requests to complete:
Failed to load resource: the server responded with a status of 404 (Not Found)
Failed to load resource: the server responded with a status of 404 (Not Found)

The test instance is running at http://iiab-staging.eastus.cloudapp.azure.com/gitea/. I may take down this VM at any time with or without notice. Please let me know if I should leave it up.
Screenshots

The requested URL is missing the prefix:

Requested URL: http://iiab-staging.eastus.cloudapp.azure.com/api/v1/users/m-anish/heatmap
Correct URL: http://iiab-staging.eastus.cloudapp.azure.com/gitea/api/v1/users/m-anish/heatmap

I've fixed this by following the reverse proxy instructions.


Design the authenticate prompt

Description
Design the authentication prompt that is presented to the user when a app wants to authenticate.
Acceptance Criteria

[x] Must show the app info
[x] Must prompt the user to accept or reject the credentials the app wants to receive
[x] Must contain the ability to unlock IDM so that the user may select an identity
[x] Must contain the ability to choose which credentials the user will disclose

Hello, here's the current status for this.
It would be great if we have te prompt on the wallet side, this would avoid displaying the initial screen (Nomios is locked) without the CTAs and the identity selector.
I've tried to reuse as much as possible the components and structure of the modal-flow so that we can speed up the entire implementation for this.

Simplified version with the browser window pop-up:

Specs here:
https://drive.google.com/open?id=1rexaXUjfE0kWP0b0IBEhAgVN2-QPLKYi


Variable webpack_asset

I'm trying to include a different logo per locale:
{{ webpack_asset('@app/Resources/assets/images/logo-' ~ app.request.locale ~ '.svg') }}

But the compiler trows this error:
Argument passed to function webpack_asset must be text node to parse without context.
Any suggestions on how to handle this sort of thing?

In general, similar feature could be added as variables in assetic.
I tried to avoid it as it's usually best to include JavaScript files conditionally inside other JavaScript files - Webpack itself handles this pretty nicely and this results in "better" asset files (no duplicated content across different assets, better caching, conditional loading etc.)
In this case, it's the image that's being loaded, so it's a no-go for Webpack itself if you want it to load instantly.
For the moment, you could do this manually:
{{ app.request.locale == 'en'
<EMAIL_ADDRESS>        : (
            app.request.locale == 'de'
<EMAIL_ADDRESS><EMAIL_ADDRESS>        )
}}

Or by splitting into separate if-else statements.
I think variables would be nice, though. In such case it would be something like
{{<EMAIL_ADDRESS>variables= {locale: app.request.locale} ) }}

And you should also need to configure all possible values for locale variable in config.yml file.

That would be nice indeed. For now I think i will load it the old fashioned way.

@mariusbalcytis would you be willing to accept a pull request to implement such feature? I would love to give it a try.

For now, I'm thinking about another option how this could be handled. Webpack parses the code and sees the patterns where variables in the string takes place, then searches files by these patterns. I think this option would be less complicated to set-up and would work out-of-the-box in most cases.
For variables:

you should define exact variables in configuration;
you should pass each variable in twig tag / function;
you should make your (still) static string so that it matches something like img/logo-{locale}.png so that the code could make different variations;
if any file would not be found by all configures variable values, bundle would most probably need to throw an exception. For example, if you configure en, de and es as possible variables for locale, you should have img/logo-en.png, img/logo-de.png and img/logo-es.png all available in the system.

With parsing concatenation:

no additional configuration or passing variables in any specific way;
glob pattern is made from expression and used to find all files available. This would mean that your production values should match available files in your repository, there would be no way to check if images for all locales are there etc. But this might be good, also, if you do not intend to use any other variable there;
there might be problems with globing if there are lots of files that matches the pattern. I'm also not sure whether it should extend more than a directory (* vs ** in glob). I think it's better to be restrictive at first - it should suit most of the needs.

So, I'm going towards the second option - the given example would work out-of-the box in this case.
I'm planning to look into this, so reopening the issue. @vicnicius feel free to make a pull request if you're up to it, though.


Fix Coq-related bug #678

Is the MULTILINE flag intentional? I don't see rules requiring it, and I'd rather not have flags added with no effect.

Good point! I've updated the commit.
In fact, I just copied the flag from the Lean lexer, without knowing what it does... Now, I have looked up the doc for MULTILINE, and I tested the code. I don't know why MULTILINE was used in Lean.

Probably a bug in Lean as well. Would you mind adding an unit test to make sure one case you care about is working correctly now?


Allow setting the border style

It's hard-coded to be none even though it can be rounded:
https://github.com/ldelossa/buffertag/blob/main/lua/buffertag/config.lua#L4

@mosheavni just merged a proper setup function where you can feed in your config. See updated readme for details.


Does not seem to save new data, but reverts back to old data.

I am trying to store data with data store and then read with another file, but whenever I try to read it reverts the data to old data. I have tried both with the save() function and without, same issue all the time.

Hi,
Same issue when I used with cucumber-js tests :(

Hi,
Same issue when I used with cucumber-js tests :(
@julien235
Seems like it has to do with multiple declared stores. If you have multiple files you can try passing the store through functions.

Do either of you have any code to demonstrate the issue you're having?

Set up two files, declare store in both, use module.exports to run one file
using the main file, write something, read using 2nd file consoles.log and
then read it using the first file. I think this should replicate the issue.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jonschlinkert/data-store/issues/39#issuecomment-788081107,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHNIFRBL3GQKHMSTIDADPILTBO5UFANCNFSM4V2NNDJA
.

I'm using a single file but creating multiple store instances to limit the scope of individual classes. Faced with the fact that deleted data was returned when trying to write to a file. I also use a wrapper for store.
This is a bad solution, but this helped:
const config = require('../config.js')

export class DB {

    private get db() {
        const db: any = require('data-store')({ path: process.cwd() + config.dbPath })

        if (this.prefix && !db.has(this.prefix)) {
            db.set(this.prefix, {})
        }

        return db
    }

    constructor(private prefix?: string) {}

    get(key?: string): any {
        if (this.prefix && key) {
            return this.db.get(`${this.prefix}.${key}`)
        }

        if (this.prefix && !key) {
            return this.db.get(this.prefix)
        }

        if (key) {
            return this.db.get(key)
        }

        return undefined
    }

    //other methods...
}


work with no project files available

Its useful to create an empty local switch for a new project, so should work when no .opam files are available.

could potentially be combined with dune init :-)


URL validator converting all to lower case

Hi,
When using the url validator it converts the string to lower case.
Is there anyway to stop this from happening?  Not sure if this is a bug or by design but it causes me some issues as I need the case to be preserved for the bit 'THIS_IS_UPPER' in the following example.
value ='https://www.myDOMAIN.co.uk/THIS_IS_IN_UPPER'
url = validators.url(value, allow_empty = False)
print(f'validated url: {url}')

validated url:https://www.mydomain.co.uk/this_is_in_upper

Many thanks

Hi @danielwmartin !
I'm afraid that in v.1.3.3, validators.url() will always return a lowercase URL. While this is currently by design, it's actually a design error, since per the related RFC specs (which I just checked) portions of URLs may be case sensitive (specifically the path portion - domains are case insensitive). The bug will be fixed in v.1.3.4.
In the meantime, an alternative is to use the corresponding checkers.is_url() function. It will not return a URL, but it will give you True if your (case-sensitive) value is a valid URL:
from validator_collection import validators, checkers

value = 'https://www.myDOMAIN.co.uk/THIS_IS_IN_UPPER'
lowercase_value = validators.url(value)
is_valid = checkers.is_url(value)

print(lowercase_value)
# Prints 'https://www.mydomain.co.uk/this_is_in_upper'

print(is_valid)
# Prints 'True'


fix(Topology/MetricSpace/InfSep): Make infsep consistent with diam, infdist

Redefine Set.infesep and Set.infsep to be EMetric.infsep and Metric.infsep

When I created infsep two years ago, I think it was an error to overuse dot notation in the way that I did, because it just
makes it inconsistent with other, similar constructions elsewhere like Metric.diam, etc.
As such, this refactor removes the dot notation of the original file, and makes some other smaller improvements as part
of streamlining the file, such as removing [Finite s] lemmas and keeping only s.Finite lemmas.

please mark as awaiting-review and merge master if it's ready for review

Apologies, have been in writing up hell. Not had much time to attend to my PRs.

No problem! I'll mark it as awaiting-author for now. Please change the labels once it's ready for review.

I actually think this is a step back: infsep makes sense in an emetric space. It's not the same situation as Metric.ball vs EMetric.ball

I actually think this is a step back: infsep makes sense in an emetric space. It's not the same situation as Metric.ball vs EMetric.ball

How do you mean?


error in flutter

C:\src\flutter\bin\flutter.bat --no-color build apk
The plugin flutter_facebook_login uses a deprecated version of the Android embedding.
To avoid unexpected runtime failures, or future build failures, try to see if this plugin supports the Android V2 embedding. Otherwise, consider removing it since a future release of Flutter will remove these deprecated APIs.
If you are plugin author, take a look at the docs for migrating the plugin to the V2 embedding: https://flutter.dev/go/android-plugin-migration.
Building with sound null safety
Running Gradle task 'assembleRelease'...
Warning: Mapping new ns http://schemas.android.com/repository/android/common/02 to old ns http://schemas.android.com/repository/android/common/01
Warning: Mapping new ns http://schemas.android.com/repository/android/generic/02 to old ns http://schemas.android.com/repository/android/generic/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/addon2/02 to old ns http://schemas.android.com/sdk/android/repo/addon2/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/repository2/02 to old ns http://schemas.android.com/sdk/android/repo/repository2/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/sys-img2/02 to old ns http://schemas.android.com/sdk/android/repo/sys-img2/01
lib/pages/add_message_page.dart:1:1: Error: A library can't opt out of null safety by default, when using sound null safety.
// @dart=2.9
^^^^^^^^^^^^
Error: Cannot run with sound null safety, because the following dependencies
don't support null safety:

package:flutter_facebook_login
package:flutter_emoji

For solutions, see https://dart.dev/go/unsound-null-safety
FAILURE: Build failed with an exception.

Where:
Script 'C:\src\flutter\packages\flutter_tools\gradle\flutter.gradle' line: 1005

What went wrong:
Execution failed for task ':app:compileFlutterBuildRelease'.

Process 'command 'C:\src\flutter\bin\flutter.bat'' finished with non-zero exit value 1

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 36s
Running Gradle task 'assembleRelease'...                           37.3s
Gradle task assembleRelease failed with exit code 1

Facing the same issue. any update from author???


mWeb/Chrome - Send money - After several entries and deletions of numbers, the cursor disappears

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Issue found when executing PR https://github.com/Expensify/App/pull/15710
Action Performed:

Go to URL https://staging.new.expensify.com/
Login with any account
Tap on the FAB button -> Send money
Enter and delete numbers several times

Expected Result:
The cursor is present
Actual Result:
After several entries and deletions of numbers, the cursor disappears
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[x] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/93399543/224387824-a7882447-8046-43ce-afcd-a8000e120df9.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub

Triggered auto assignment to @mateocole (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

@mateocole Whoops! This issue is 2 days overdue. Let's get this updated quick!

yep going to have an engineer double check to confirm this isnt intentional and something we can mark as external

Triggered auto assignment to @PauloGasparSv (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

Bump @kbecciv, and can you also confirm if this was reported using an emulator or an actual device?

QA team is using Actual devices always.

Thksss @kbecciv, I wanted to make sure this wasn't related to the emulator and if there was a possibility this would only be reproducible in an actual device.
Can you also give me feedback on this comment?

Bump @kbecciv

@PauloGasparSv Show taps option is enabled and issue is reproduced on my device SG21/13 with build <IP_ADDRESS>
Uploading Screen_Recording_20230317_173843_Chrome.mp4…

Thks @kbecciv!!
I wanted to make sure because it's hard to understand what happens when the little round cursor goes to the top of the screen! It looks like you can't do anything after that happens and the cursor gets stuck on the top of the screen so I'll try to reproduce that.
I still couldn't reproduce it so maybe I'll have to ask for help in slack for someone with an android device!

Not overdue!

Taking this one after asking Paulo 1:1 I think its related to this change https://github.com/Expensify/App/pull/15710

Hey, I am Nicolay from Callstack and i will check this issue

@narefyev91 @PauloGasparSv and me could not reproduce this, lets close this one out, if it comes back as a problem we can reopen

When executing this PR https://github.com/Expensify/App/pull/16340, issue is not fixed on build <IP_ADDRESS>
https://user-images.githubusercontent.com/93399543/226689539-50c19909-55b0-45e4-99d4-3b51d07fda8c.mp4

@kbecciv Hmm maybe whats the device you are testing on? Is it only chrome mWeb?

This is Andriod/Chrome

@narefyev91 are you able to repro using Android/chrome

@mountiny @kbecciv based on the video and my test now - cursor disappeared because you click not on number pad - but somewhere in between buttons. Text input automatically loose focus (when you click outside) - in my view it's expected behaviour.
https://user-images.githubusercontent.com/28352309/226867234-ed9eb3ec-0fb2-4368-93d6-8cf7fae4b682.mov

Can we make it so the cursor appears again once you start typing again?

@mountiny yup - will prepare a PR with that fix

Reviewing label has been removed, please complete the "BugZero Checklist".

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[ ] [@mountiny] The PR that introduced the bug has been identified. Link to the PR:
[ ] [@mountiny] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[ ] [@mountiny] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
[ ] [] Determine if we should create a regression test for this bug.
[ ] [@narefyev91] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[ ] [] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:


Text input nodes ignore shift

Godot version:
Commit 72d87cf
OS/device including version:
Debian sid
Issue description:
Text input nodes ignore shift (and, possibly, other modifier keys), making it impossible to enter shifted characters.
Steps to reproduce:
Enter text in the editor. Especially, shifted characters from the upper row like parentheses.
Minimal reproduction project:

Additional notes:
Seems to be IME-related, as the last system update deactivated my IME. Reactivating it solved the issue.
Even then, it seems that Godot needs an IME to detect shifted characters. Is that an acceptable behavior?

What is your IME?

Commit which cause this issue - https://github.com/godotengine/godot/pull/31740

CC @bruvzg

I can't reproduce any input issues with or without IME.
Please specify what's the exact configuration that doesn't work. Also, could you try inputting non-working keys into the attached project and provide the output.
test_proj.zip

I use Kubuntu 19.04 without any bigger modifications
$ setxkbmap -query
rules:      evdev
model:      pc105
layout:     pl

CTRL, ALT and others seems to work, but only shift not working good(Shift - 1000015)
K:      41 U:      61 P: True == a
K:      41 U:      61 P:False == a
K: 1000015 U:       0 P: True ==
K: 1000015 U:       0 P:False ==
K: 1000015 U:       0 P: True ==
K:      41 U:      61 P: True == a
K:      41 U:      61 P:False == a
K: 1000015 U:       0 P:False ==
K: 1000016 U:       0 P: True ==
K:      41 U:      61 P: True == a
K:      41 U:      61 P:False == a
K: 1000016 U:       0 P:False ==
K: 1000018 U:       0 P: True ==
K:      41 U:      61 P: True == a
K:      41 U:      61 P:False == a
K: 1000018 U:       0 P:False ==
K:       0 U:     105 P: True == ą
K:       0 U:     105 P: True == ą

Tried few other distros including fresh install of Kubuntu 19.04 and still can't reproduce it. I have no clue what's wrong. Just as an educated guess, please try following patch:
diff --git a/platform/x11/os_x11.cpp b/platform/x11/os_x11.cpp
index 687981f32..7fa60d960 100644
--- a/platform/x11/os_x11.cpp
+++ b/platform/x11/os_x11.cpp
@@ -1767,6 +1767,7 @@ void OS_X11::handle_key_event(XKeyEvent *p_event, bool p_echo) {
 	XKeyEvent xkeyevent_no_mod = *xkeyevent;
 	xkeyevent_no_mod.state &= ~ShiftMask;
 	xkeyevent_no_mod.state &= ~ControlMask;
+	XLookupString(xkeyevent, str, 256, &keysym_unicode, NULL);
 	XLookupString(&xkeyevent_no_mod, str, 256, &keysym_keycode, NULL);

 	// Meanwhile, XLookupString returns keysyms useful for unicode.
@@ -1777,8 +1778,6 @@ void OS_X11::handle_key_event(XKeyEvent *p_event, bool p_echo) {
 		xmblen = 8;
 	}

-	keysym_unicode = keysym_keycode;
-
 	if (xkeyevent->type == KeyPress && xic) {

 		Status status;

If it won't help, #31740 should be reverted.

With this path Shift works, but compilation show this wartning:
[ 34%] platform/x11/os_x11.cpp: In member function 'void OS_X11::handle_key_event(XKeyEvent*, bool)':
platform/x11/os_x11.cpp:1770:1: warning: value computed is not used [-Wunused-value]
 + XLookupString(xkeyevent, str, 256, &keysym_unicode, NULL);

Using Elementary OS (based on Ubuntu 18.04) and have the same issue. Thought I was crazy at first!

I'm also experiencing this issue. I tried the patch above (in https://github.com/godotengine/godot/issues/32268#issuecomment-535343289) and it fixed it for me! Thanks :-)


Switch from raw ENV to travis-config

[x] test in staging

This is behaving well in staging, fwiw :+1:


FILE PATH NAMES ARE TOO LONG!!! Could not copy the file C:\n\xamarin\firebase\ios\cloudfirestore<excessively-long-path>

Please, for the love of whatever you believe in, shorten the file paths. I cannot publish my app at all once this package gets transitively included with Plugin.Firebase.
I have Windows long paths enabled which hasn't helped this issue, and I have my nuget's stored under C:\n, the shortest filepath possible. Yet I cannot build my app:

Firebase is a wonderful feature set, and I'd really love to use it.
Using .NET 8.0 with .NET MAUI. Cannot build, rebuild, or publish in VS due to this issue that shouldn't be an issue.

It's a shame how an entire plugin is rendered unusable because of something like file name length.
@Quaybe have you found a better workaround that doesn't have to resort to building stuff through the console and disabling the iOS platform?

It's a shame how an entire plugin is rendered unusable because of something like file name length.
@Quaybe have you found a better workaround that doesn't have to resort to building stuff through the console and disabling the iOS platform?

After making those changes, I just can't use the rebuild or build options in VS. Basically it seems VS doesn't fully support the maxfilename registry change, but it partially does. So, I can debug (F5) the app and it builds and runs fine. I can also clean the project by right clicking on the project in VS.
But if I try to right click > Build or right click > rebuild, it fails with the file length issue. So for the last several weeks, I have just avoided doing that, and this has worked ok for me. If I absolutely need to, I will close it all out and do a "dotnet restore" from the command line.
I should also note though, that this issue prevents me from publishing the app in VS as well. So I have to do a roundabout way to publish and sign the app for Google Play store. So far I've only published for Android. I'm developing for iOS, but haven't gotten to the publish point yet.

Thanks, man. I guess I'll have to disable iOS for the time being and just hope for the best. Since it's a bindings thing I don't even think there's an alternative plugin or something that could be used in .NET MAUI instead of Plugin.Firebase.


Fix passing filter_min_reads as int

Description of the bug
When analyzing non-duplex reads it makes sense to set filter_min_reads to an int, however. when setting --filter_min_reads 1 you will encounter the following error:
 --filter_min_reads: expected type: String, found: Integer (1)
even passing --filter_min_reads "1" does not seem to solve this issue.
Command used and terminal output
nextflow run nf-core/fastquorum --input $sample_sheet --outdir $outdir --fasta $reference_fasta --mode rd --groupreadsbyumi_strategy Identity --groupreadsbyumi_edits 0 --duplex_seq false --filter_min_reads 1 -profile docker -resume

Error message:
--filter_min_reads: expected type: String, found: Integer (1)

Relevant files
No response
System information
Nextflow version: 24.04.2
Hardware: HPC
Executor: slurm
Container: docker/singularity
OS: Ubuntu
nf-core/fastquorum v1.0.1dev

@SPPearce has suggested a workaround of --filter_min_reads '"1"' for the time being

Fixed in #66


global is not defined in the browser

The check for if the TextDecoder polyfill is required currently references global, which only exists on Node.js and not in the browser.
https://github.com/near/borsh-js/blob/261d9cde21665de5a9e2c75ec2509c0bfb7030bf/borsh-ts/index.ts#L6-L9
With bundlers that don't automatically polyfill global this causes problems and requires hacks to make it work. What you would think of one of the following solutions?

typeof TextDecoder !== "function" ? encoding.TextDecoder : TextDecoder
typeof globalThis.TextDecoder !== "function" ? encoding.TextDecoder : globalThis.TextDecoder

globalThis has been available for a while now, but I think the first one is best since it doesn't make any assumptions about the name of the global variable. Any thoughts? I'm happy to submit a PR for this.

Shouldn't the TypeScript compiler check the availability of the globalThis variable?
// cat index.ts
console.log(global, globalThis, global == globalThis);

$ yarn run tsc index.ts
index.ts:1:13 - error TS2304: Cannot find name 'global'.

1 console.log(global, globalThis, global == globalThis);
              ~~~~~~

index.ts:1:33 - error TS2304: Cannot find name 'global'.

1 console.log(global, globalThis, global == globalThis);
                                  ~~~~~~

Found 2 errors.

This package depends on @types/node, which provides the definition of global to Typescript. globalThis is part of Typescript's built-in type library.

@dimfeld any luck on this issue so far? I'm trying to use the solana web3.js library for my Vue.js project but I can't proceed cause of this. it's kinda sad the maintainers aren't fixing this issue.

I submitted #40 to fix it. No response yet.

@dimfeld too bad, in the meantime do you have any idea or any "hacky" tricks to circumvent this?

Seems like the best solution for now is to add something like this to the top of your app's root HTML file:
<script>
    window.global = window;
 </script>

Depending on your bundler, you could also use some sort of replacement plugin to change global.TextDecoder to just TextDecoder or globalThis.TextDecoder.

Thanks for the fix guys!

@dimfeld @glennmichael123 @ilyazub v0.7.0 released!

@volovyk-s thank you so much!!


Responsive Material-UI

Google have published guidelines for Responsive UI in MD: https://www.google.com/design/spec/layout/responsive-ui.html#
As responsive design is a Roadmap item, this issue is to intended log the intent, and capture feedback.
A common question on gitter is whether MUI includes a grid system, or, failing that, what grid system to use.
In addition to making individual components more responsive, this is an opportunity to provide the grid system that complements the core Material-UI components.

I don't think we should do layout too. It's against unix philosophy. There are already many awesome grid systems out there. The specs are for applications not libraries.
Frankly I believe we shouldn't have all the components either! It would be great if we didn't have Table, GridList and SvgIcon  in this repository, let along a layout system. That's my opinion, absolutely open to discussion :sweat_smile:
The more code we add to this library the harder it gets for us and other contributors to keep consistency and a lot harder to change core stuff. We might wanna consider breaking this repo down if we wish to support more components.

I think it depends on the goal of the library. If the overall goal is to be a reference implementation to the Material Design spec in React (Similar to how angular-material is the reference implementation in Angular) than I think it should implement the spec in full.
On the other hand, if MUI is just a collection of Material Design components than it doesn't really matter and you can pick and choose what components you want. With this approach you get more control and allow more selectiveness, but you lose the status of :tada: reference implementation :tada:. On a personal note, I think having a full reference implementation within the React community is a good thing.
@alitaheri I think that either way, breaking down the repo into isolated components would be great. Being able to just install FlattButton or Dialog would be a huge benefit, but I know discussions in the past have mentioned the difficulty of isolating components due to shared implementation details.

@Aweary I agree with you :+1: Then it boils down to what the goal of this library actually is.

but I know discussions in the past have mentioned the difficulty of isolating components due to shared implementation details.

True :sweat_smile: we should investigate this in more details.

I've just had a read of the spec, and come away with the impression that it's a series of guidelines for ways to make an application responsive, rather than a spec for responsive components.
I think our purpose should be something like "to be a toolkit for building Material design compliant applications", and as such there are maybe some building blocks that we should include to make doing some of the responsive pieces more straightforward, but there is nothing that needs implemented here directly to my mind.
@alitaheri - I agree that table, grid-list, and icons should be separate (and thought that when some of them were added... e.g. https://github.com/zippyui/react-datagrid is much better that <Table /> - a material-ui/table project would seem logical to me!)

Its a spec in the sense that it defines specific values (breakpoints, grid row count, gutters/margins, etc.) that you would implement to be compliant. You can see how angular-material does it: https://material.angularjs.org/latest/layout/container

@alitaheri I would argue that the response layout is a core part of the MD philosophy.

Develop a single underlying system that allows for a unified experience across platforms and device sizes. Mobile precepts are fundamental, but touch, voice, mouse, and keyboard are all ﬁrst-class input methods.

Yes it's debatable, but my concerns aren't related to whether we should implement these or not. It's simply that we cannot maintain everything ourselves, there are so many components here already. Angular has a big team, we aren't that big. I'm only saying we should break it down to smaller projects, whether it's under material-ui or not. by doing that we can have specific maintainers, not general ones who know so little about some components and so much about others.

@alitaheri
I agree. Maintaining the grid system in addition is huge. Great point mate.
I think that breaking the grid/layout system into a separate project, or finding an existing one that we can integrate with seamlessly is the best route :+1:

@mbrookes @oliviertassinari Would it be possible to make quick fixes, like make that Appbar to have mobile height, and few little things which are easy to implement, without having to implement a whole new grid system.
There will soon be a sky rocketing number of web apps thanks to new progressive web-app technology. I think it makes a lot of sense to make Material-UI compatible on Mobile Web. We are using it for our new web app but the Appbar doesn't look great at unless its 56.

@julianmartinezmansell For a quick fix, you can do the following:
const muiTheme = getMuiTheme({
  appBar: {
    height: 56, // Instead of 64
  },
});

And few little things which are easy to implement, without having to implement a whole new grid system.

True, but we need to think and solve the problem globally.

While a grid system would be nice, I recommend against it in this project.
it may be just as easy to support a recommended grid system.  Grids are difficult to maintain, and I wouldn't want that noise in this issue tracker.  A separate grid-specific project is doable, but making material-ui responsive doesn't mean taking on the whole responsibility.  As long as it can be responsive with the addition of other projects (with a reasonable developer experience), I think it should stay out of this project.
With that said (and the reason I read this issue) is to try and understand the "recommended way" for this project. For example, is a css reset recommended? Which one? or is it not necessary (and why)?  Grid system? Which one?
I think a sample repo/starter might be really useful.  The docs app could certainly be this, but as I read them I haven't bumped into a grid or a reset.
I guess this is all to say, it would be nice to see a prescribed best way of doing things in one of the getting started docs (or sample repo), albeit noting that the developer is free to implement any way they would like.

FYI - while looking at the styling issues/options (one of those being JSS), I bumped into perdido is a grid system for JSS ported from LostGrid.  JSS + CSSX + perdido may be a really good combination.

@rosskevin I wish CSSX had syntax highlighting and autocomplete/snippet support in my editor!!

@nathanmarks - agreed, I need to see if I can get JetBrains to ignore CSSX (at least), it is trying to reformat it (incorrectly) and I'm addicted to just typing + reformat all the time.
Also there is an eslint issue.  @krasimir is going to look at it soon, and see if he can get a solution.  As a nice to have he might get some css linting as well.

@rosskevin I love the look of it, but I feel like you have to sacrifice even more in the way of development tools than you already do with object literals. It would be fantastic to have syntax highlighting and css linting!

Hey guys,
just so you know that there is eslint-plugin-cssx that transforms the CSSX expressions to an empty object literal. So, at least we can make js linting tools happy. If you need same logic in another context feel free to use this code.

@krasimir Thanks for sharing this project. That could be useful.
The tooling, is definitely one aspect of CSS in JS that will need to improve if we want this approach to success.

I think that this should be flagged as a milestone towards v1.

This is a huge problem the should be fixed right away. When scanning the documentation, it took me quite awhile to figure out that this library didn't include a responsive component by default and then finally to stumble across this discussion about the topic. The fact that the Google Material UI spec talks about Responsive UI specifically and Materialize CSS implements components and has an entire page dedicated to mobile makes it clear that this is an important topic. That being said, the immediate resolution to this problem is not a difficult one to start. I propose putting a blurb somewhere in the documentation to highlight either this discussion or general philosophy behind this library. Saying something like "We don't have a grid system because it doesn't necessarily place nice with inline CSS and would bloat the library. Please see alternatives like flexboxcss." Would be extremely helpful for the community trying to implement their first components. Please don't wait on v1 to update the documentation. Thanks! :)

After looking through this, I'm trying to stay positive here, however, I think I have to transition back to Bootstrap.
I don't understand how you can implement a component system without taking into account responsive design in 2016. I can't seem to find how to modify my Toolbar like bootstrap does at breakpoints (Turning my menu items into a dropdown icon as you go smaller, etc). Sure, I can add Flexbox, but neither the documentation or help areas tell me how to interact with Material UI components in any meaningful way to make them responsive with a CSS grid system.
If I'm missing something, please feel free to correct me. However, without this basic implementation, or explanations/samples in the documentation, I don't see how Material UI could be used in a production app.

@lesreaper There is a refactor of the library currently under development that has better support for responsive applications.
However, I have a question regarding the specific example you used (turning menu items into a dropdown icon). What technique are you referring to specifically?

@nathanmarks I'm referring to the moving of UL's into a dropdown icon list. Here are 2 examples below from Bootstrap. The top is a wide desktop, over 992px, and the other is a mobile under 480px. I'm skipping the inbetweens for clarity's sake.
I don't understand how any of this could be possible with just adding Flexbox and using the current Material UI components. Am I wrong?

I don't understand how any of this could be possible with just adding Flexbox

@lesreaper The material design equivalent to the bootstrap example you showed seems to be the <Drawer /> docked / open behavior depending on the screen width.
I agree, that's definitely not something you can achieve with a simple browser layout engine, like flexbox our media queries. You need to interact at the React properties level of abstraction.
Material-UI provides simple components that you can compose to get whatever behavior you need. I think that we have an implementation example of what you are looking for https://github.com/callemall/material-ui/blob/master/docs/src/app/components/Master.js#L194.
Material-UI don't provide any layout abstraction yet.
We are focing on the core components, we have still quite a lot to do in this area.

Depending on the extent, making material-ui's components responsive is likely a very large project.  What would be a nice start, would be to make it possible/easy to define responsive styles to material-ui's components.  A step beyond that would be to allow you to define component params for 2 states, one for desktop one for cell phone (I know truly responsive designs have more than the 2 break points, but having the 2 would go a long way).
Some examples....
The stepper being horizontal on desktop, vertical on mobile (A smaller change, would be to shorten the labels on smaller devices).
Pretty much the same thing would be nice on the Tabs and Menu.
Of course this stuff could be done manually (in my case I'm using redux) and could be passing the screen width to the components that need to be responsive.  But this is obviously far from ideal when the usual solution for this is a purely CSS solution.  The styles that are defined in the JS on the components would be a good place, I'm just not aware of any way to define responsive styles here.

As I am experimenting with integrating MUI components into a new project, I think it would be really helpful to make sure that we play nicely with Radium.  That would allow a good deal of flexibility on a per component basis for example supporting @media directives in the style object.
This would allow us to make individual components more responsive independently of integrating a grid.

In our product, we created our own components that manages responsiveness of layouts and of other components. The responsive components bind themselves to the onResponsiveChange of the ResponsiveStore. So when the screen size changes, an event is fired, the component rerenders with the new breakpoint and screen info.
It makes it easy to define a xs/sm/md/lg grid. Media queries becomes simple ifs
Here is a minimal example: https://gist.github.com/vizath/605d5e1dc8eece005aa9cf6a8407ea2e
<Drawer open={Response.isAtLeast(Responsive.LAPTOP) || this.state.opened} />
<Stepper orientation={Response.isAtMost(Responsive.TABLET) ? 'vertical' : 'horizontal'} />
const ResponsiveStepper = ({ orientation, ...others }) => {
  if (orientation === 'responsive') {
    orientation = Response.isAtMost(Responsive.TABLET) ? 'vertical' : 'horizontal';
  }
  return (<Stepper orientation={orientation} {...others} />);
};

etc.

Thanks @vizath for the example.  It pointed me in the right direction and I just found the redux-responsive project.  From a quick reading of the docs,  it appears to work similarly to your custom components.
The approach is simple and performant.  Since we will be using Redux, I think we will try this solution.

@rlmckenney thanks for sharing, I'm starting the implementation of my own redux-responsive 7 minutes ago and just stopped :D

As an FYI to those watching, I have implemented flexboxgrid.com on material-ui#next as a set of self contained react/jss components that is tightly integrated with material-ui#next theme's responsive breakpoints.  I don't have time to create and maintain another OSS project, but if someone wants to, I'm happy to contribute this working code and sample. NOTE: this only works on the next branch and is not applicable to material-ui 0.15.x.   Please contact me if interested, this could be published as something like material-ui-layout or material-ui-grid.

@rosskevin I would love to have a look at it. Would it make sens to share it in a gist?

@oliviertassinari

Code gist
Samples gist

The Samples gist recreates the flexboxgrid.com homepage samples.

@rosskevin Sweet. Thanks.
I think that we could create a Layout docs section.
So people know we don't provide any solution for it and we can link some great project solving the issue.

@oliviertassinari I would be in favour of adding something based on @rosskevin's work to next. This is the single biggest FAQ by far on gitter, and a having "native" solution would make so much sense.

@rlmckenney I knocked up a trivial responsive grid system using Flexbox and redux-responsive a couple of days ago.  Could probably simplify the breakpoint selection, but it's not terrible as is.  Has covered all my use-cases so far.

@rosskevin I'm curious. Why not using flexboxgrid with responsive breakpoints matching ours?
@mbrookes I agree, we need to do something about it! That could be a good idea.
However, I'm wondering if we have the time to maintain it.

@oliviertassinari I chose to use the flexboxgrid css code (it uses myth in the src), converted to jss within react components using material-ui breakpoints.  The rationale is that when you boil down the original css code, it is quite repetitive and a good case to use jss (less to maintain).  I also wanted fully self contained react components that can be included like any other react component (without a toolchain or global setup), as well as the dynamic prefixing etc that jss offers.
I do not think it is much to maintain, just check the commit log as evidence. Given periodic checks against commits from kristoferjoseph/flexboxgrid, there isn't much in the code as upkeep effort.  What I fear is the number of the support questions, not in that the code will be changing much, but in that users will want to do things with it and not understand how to do it.  This may be unfounded, given that the original project only has 144 issues all-time total, and it has 4000+ stars.

I like the idea of https://github.com/callemall/material-ui/pull/5267, been using angular-material styles in the past, and loved it. its offers really more flexibility than flexboxgrid.

I suppose if MUI want to use any grid system it should follow Google Material specification. So, from one hand it can be flexible, from the other it should not give the control to make grid inconsistent to GMD.

@rosskevin Right, from a technical point of view, I completely understand. I was more interested in the material design specification. Turn out, after digging into the specification. I think that there is a real need for us to implement a solution. The material spec layout system is a 12 column system, with some specific breakpoints and margins / gutters.
I just had a look at #5267, that seem more complex but interesting too.

A material-ui spec grid would be very useful. We've considered react-mdl but only need the grid, currently trying to decide on the best route forward. There doesn't seem to be a good material spec grid out there that integrates well with material-ui.

@dano-giftbit I needed one too and was thinking the same thing, MDL but just the grid... I whipped up a starter this week and would interested in your thoughts.  I'm going to be testing it with the full material-ui component kit next week, got a holiday coming up and need to head out of town right now though ;)
https://www.npmjs.com/package/material-grid

@Cleanshooter Thanks for sharing this project.
That's another good one to have a look at when designing our API / implementation.

Have a look at Hedron built with styled-components. Worked for me like a charm.

I have given a shot to that component. I would love to get some feedback #5808.

I first iteration have been merged with #5808. If you find anything that could be improve, fell free to  raise your voice / open a PR. Thanks.

Awesome work @oliviertassinari!

Thanks, I have done a second iteration on that component for higher flexibility https://github.com/callemall/material-ui/pull/5827.

That looks fantastic, @oliviertassinari, When do you think it will get tagged and bagged?

@DoWhileGeek What do you mean by tagged or bagged? Official Release won't happen until we have migrated all the components but we plan to do some beta / alpha releases before.

do you plan  plan to do some beta / alpha releases to happen still in this q1 ?
Cheers

@thomasmodeneis We do, have a look at https://github.com/callemall/material-ui/releases/tag/v1.0.0-alpha.1.

@oliviertassinari oh nice, thanks.

Another alternative is https://github.com/material-components/material-components-web/tree/master/packages/mdc-layout-grid


AttributeError: 'DbtOsmosis'

When a user runs dbt-osmosis diff -m some_model ... they are getting AttributeError: 'DbtOsmosis':
dbt-osmosis diff -m some_model  --project-dir /path/to/dbt/transformations --profiles-dir /path/to/dbt/transformations/profiles --target target0
INFO     🌊 Executing dbt-osmosis

INFO     Injecting macros, please wait...
Traceback (most recent call last):
  File "/Users/myuser/.pyenv/versions/3.10.7/bin/dbt-osmosis", line 8, in <module>
    sys.exit(cli())
.....
AttributeError: 'DbtOsmosis' object has no attribute '_get_exec_node'. Did you mean: 'get_ref_node'?

Note
Please note that no error when running the dbt-osmosis workbench - that one runs nicely.
Configuration:

dbt version: 1.2.0
python version: Python 3.10.7

This issue is no longer present, though diff commands are undergoing rework!


feat: add support for custom initializationOptions and originalRootUri

This is a total hack, but actually helps sourcegraph-go activate and initiate a connection with go-langserver. See https://github.com/sourcegraph/sourcegraph-go/issues/28

Codecov Report

Merging #11 into master will increase coverage by 0.01%.
The diff coverage is 75%.

@@            Coverage Diff             @@
##           master      #11      +/-   ##
==========================================
+ Coverage   65.48%   65.49%   +0.01%
==========================================
  Files          11       11
  Lines         310      313       +3
  Branches       19       20       +1
==========================================
+ Hits          203      205       +2
- Misses        107      108       +1

Impacted Files
Coverage Δ

src/index.ts
61.87% <75%> (+0.1%)
:arrow_up:

Continue to review full report at Codecov.

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

@lguychard Oh, for sure, it's 100% weird and a total hack. This isn't intended to get merged in as-is. This was only intended to aid the discussion in https://github.com/sourcegraph/sourcegraph-go/issues/28. There are more details to be sorted out.
Have you seen https://yargs.js.org/ ? The entire README used to be written in pirate-speak 😆

Closing in favor of https://github.com/sourcegraph/lsp-client/pull/36


Live Print Output

Thank you for this plugin!
Is your feature request related to a problem?
The output only appears at the end of the evaluation.
However, often if one encounters problems, the cell will never fully evaluate.
Stopping the cell leads to no output at all.
This makes debugging really hard.
Describe the solution you'd like
Live print output like in Mathematica notebooks.
If possible also PrintTemporary output.
Additional context
Example code:
Do[
    Print[i]; Pause[1]
    , {i, 1, 5}
]

Thanks for the feedback. It should be a bug; I'll investigate this issue and get back to you.

8c66289


bug: reading in batch mode not work properly

Bug Report
YDB Python SDK version:
ydb==3.17.2
Environment
Ubuntu 22.04, Python 3.11.7, x86_64
Current behavior:
When i read messages from topic in batch mode, i expect got 1+ messages, got only 1 every time
Expected behavior:
When i read messages from topic in batch mode, i got more than 1 message
Related code:
    async def _consume(self, reader: ydb.TopicReaderAsyncIO) -> None:
        while True:
            try:
                batch = await reader.receive_batch()
                if not batch:
                    await asyncio.sleep(1)
                    continue

            except TimeoutError as e:
                self.__logger.info('Error while receiving batch: %e ', e)
                continue

            for message in batch.messages:  #  <== got only 1 message here every time
                try:
                     ....  # processing

fixed here https://github.com/ydb-platform/ydb-python-sdk/releases/tag/3.18.0


Made the JDL files a bit simpler

As I'm using those for Devoxx, and I just finished testing everything - can we wait until Devoxx is finish to merge those? I don't want to re-test everything...

@jdubois Okay, but I promise you they are good to go ;)

Oops I totally missed this!!
Sorry @MathieuAA I'm merging this now

I totally forgot this PR!! I guess there was no urgency :) thanks Julien!I've got to come up with a new base JDL example one day


Build server problem

[00:36] kashike: @everyone We have removed public access to our Jenkins instance. Please switch to using our API for all downloads if you are still using Jenkins - documentation can be found at https://papermc.io/api/docs/ if you are unfamiliar.
https://papermc.io/downloads also exists for downloading normally, if you don't need to automate your downloads.

[00:36] kashike: @everyone We have removed public access to our Jenkins instance. Please switch to using our API for all downloads if you are still using Jenkins - documentation can be found at https://papermc.io/api/docs/ if you are unfamiliar.
https://papermc.io/downloads also exists for downloading normally, if you don't need to automate your downloads.


feat[configmap]: added binaryData functional

subj

Hello! Thanks for suggestion! I will add this in next release after additional testing


Update site_info.json to add TCCON sites info

Addition of TCCON site details

The reason is that they are referred to with a 2-letter site code in the TCCON data. But I agree that it is not really good given the amount of other sites that we have. I can put a 3-letter code, no pb on this

Yes, that makes sense - 3-letter codes look good though.

Localisations seems to be completely wrong, I will double check the script to create them

Should be good now. Some sites have a changing latitude/longitude (change of a few cents of degrees). Put them in an array style but not sure this is the right things to do.
Also, ordering the keys and formatting with an indent of 2 before storing changed the display of the other sites. Is it ok?

Can I just check - has is been reformatted because you ran black (or something else) over it?

No, it's because I converted my dict to json with json.dumps(d, indent=2, sort_keys=True)

Are we good to merge or should I format this otherwise?

Are we good to merge or should I format this differently?

I am a little concerned about the reformatting across the whole file - just in case anyone else has been using a derivative of this file they'd like to be able to merge back in at some point. Would be it be possible to ensure the updates only impact the added lines or would that be difficult to do?

I've done as much as I could to keep the old formattimg. But the identation was not homogeneous and some sites where not stored at their place (in terms of allphabetical order). Reordering just the sites and not the keys inside (i.e. "height", "latitude",..) would have been too much of a pain, so I there is some changes there too.
I think we should go with this as it is. Tell me if you're not ok @rt17603

By the way, I'm not saying this was done perfectly but there was originally a logic to the order of the inlets, with the first generally being the default used. So I think we may need to a bit cautious with reordering the heights lists even if it seems logical to order with largest inlet first.

The heights are not reordered as they are not keys to the json files. So that is kept. But the network order is changed some times which might change the first inlet (if all networks have not the same first inlet).
Anyhow I'm planning to delete this PR and go for yours


Fix customer comparators bug

Fix NPE when comparing by customer's last date

since getLastDate can be null, put those customers at the bottom.

Fix case sensitivity when sorting by customer name from A-Z
Fixes #178, #175

Codecov Report

Merging #195 (987c3fc) into master (6027ab6) will decrease coverage by 0.06%.
The diff coverage is 75.00%.

@@             Coverage Diff              @@
##             master     #195      +/-   ##
============================================
- Coverage     56.33%   56.26%   -0.07%
  Complexity      775      775
============================================
  Files           143      143
  Lines          3309     3311       +2
  Branches        358      358
============================================
- Hits           1864     1863       -1
- Misses         1341     1344       +3
  Partials        104      104

Impacted Files
Coverage Δ

src/main/java/seedu/address/model/Model.java
90.00% <75.00%> (-10.00%)
:arrow_down:

...c/main/java/seedu/address/model/customer/Name.java
66.66% <0.00%> (-16.67%)
:arrow_down:

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


Send Trade Window when Player click on Villager

Depends on #5 #6

Use the old Shopkeepers config file aresv1.yml to add name of items from the file created in #6 to the file containing the positions from #5
When the player interact with one of the villager open a Trade Window with the items from the config

Closed by #43


Test docs deploy

Github Actions to publish documentation site to Netlify.
The actions also:

generate client/java javadoc
generate openapi spec
generate latest version spec definition to be put in static pages

Steps to reproduce test to verify the GitHub action behaviour.

Create branch from main repo and current OpenLineage/docs repo into website directory. Please mind deleting .github dir and .last_spec_commit_id file.
Create test-docs-deploy branch in your private repo from the previously created branch
Create netlify site and and into GitHub NETLIFY_SITE_ID and NETLIFY_TOKEN_SECRET secrets
To run some tests one can do the following modifications:
change version of some facet to non existing - to make sure that newly published site will contain the new version. This will also let verify if openapi got changed.
modify some java doc description of the client/java to make sure java doc gets modified

Pushing the test-docs-deploy branch will trigger the changes. Although normally they run on main branch when main is modified  or tag is created, for repositories other than Openlineage/Openlineage they're triggered on push to test-docs-deploy.

GitHub Actions run:

https://github.com/pawel-big-lebowski/OpenLineage/actions/runs/10108140162
https://github.com/pawel-big-lebowski/OpenLineage/actions/runs/10108140160


Unable to resolve module error after importing Axios

I am posting this, because https://github.com/facebook/react-native/issues/11498 was closed, but the bug still persists and the workaround does not permanently fix the problem. Check details from over there, exact same situation. Can't import any new modules.

+1

+1

https://github.com/facebook/react-native/issues/11498#issuecomment-273972902

This fix might work for this particular packages, but we cannot import any new added module

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with Canny! Check out its new home: https://react-native.canny.io/feature-requests/p/unable-to-resolve-module-error-after-importing-axios


Create MOM-2023-11-02.md

What type of PR is this?
Add one of the following kinds:

documentation
subproject management

What this PR does / why we need it:
Meeting Minutes, 2nd November
Please Review them

Please @grgpapadopoulos, @sebKoeller could you review meeting minutes


Add suggestion to go to the parent definition when using typing.override

It might be nice to have a popup allowing user to go to the parent (parents?) definition of a method when using @override:
class A:
    def func(self):
        pass

class B:
    def func(self):
        pass

class C(B, A):
    @override  # On hover, add a goto to the parent (parents?) definition.
    def func(self):
        ...

This is already achievable when calling super().func(), but we do not necessarily call super.

I think this is already tracked somewhere. @heejaechang, do you remember where that is?

we didn't implement code lens for type/method hierarchy. implemented just show type hierarchy if that's what you are asking.
we can't implement code lens for type/method hierarchy due to threading/memory sharing limitation we have on js.

If vscode has support for go to definition on hover, we could leverage that. But also, for go to def on @override, we have two potential approaches: going to definition of the decorator or the parent definition. To gather more feedback, we are moving this issue to discussion as an enhancement request for comments and upvotes.


Add cytoscape export

would it be possible to get to make a download available of the MS2LDA network to upload into CytoScape e.g.?

yep, should be easy - import formats are very straightforward


add configurable search operator for ListOperation

WHY
BEFORE - What was wrong? What was happening before this PR?
This is an old issue since #1980 . There were workarounds, but we can make developers life easier. A few days a solution to solve this problem pop-up in #4277 but we talked about it and decided that it was better to make it configurable than "hardcode" ilike for some db's and like for others.
AFTER - What is happening after this PR?
We still use like by default, but the search operator is now configurable, so you can change it globally for ALL CRUDS in the backpack.operations.list config file, or per crud $this->crud->setOperationSetting('searchOperator', 'ilike') in your setupListOperation.
HOW
How did you achieve that, in technical terms?
Added a config for the operator.
Is it a breaking change?
No it's not.

This. Is. PERFECT!

Non-breaking. Good naming. Surgical change.
Thank you @pxpm ! Well done!

I am guessing the relevant change is also needed on the FetchOperation trait to allow for case insensitive search in a select field with an ajax data source.

Hello @siddharth-bhansali and I guess you are right 🙃
I've submitted the PR to pro that would:

Make the searchOperator for Fetch by default the same that is defined for List.
Added it as a operation configuration, so you can change it if it's different from the List one.

Thanks for the feedback 🙏

Hello @siddharth-bhansali and I guess you are right 🙃
I've submitted the PR to pro that would:

Make the searchOperator for Fetch by default the same that is defined for List.
Added it as a operation configuration, so you can change it if it's different from the List one.

Thanks for the feedback 🙏

@pxpm great! I had been following this thread for a while now and eagerly was waiting for the change, however didn't happen with the select. For now I have overridden the trait, but a configurable operator would be great! Thank you very much!


Handle all the datatypes in the EMA sampler

Now that we support msgpack the types that might be in the data hash are more varied than they used to be.
Adds the ability to format any type as a string in order to handle this

It looks like the regular dynamic sampler is also going to be impacted by this, will update that as well


Why must Keyframe<T>.value() be T: Copy?

Why must T be Copy? How can one access a value in a keyframe with non-copy types?

I believe the motivation here must be to avoid unnecessary allocations. This makes sense as allocating on each tween would be crippling for performance.
Perhaps instead of returning an owned type, the caller to ease() could pass an output: &mut Self? That would allow for tweening types that are non-copy, by writing into the output.

I believe the reason for ease() working with values rather than references is that the former is better for primitive types. An f32 is smaller than a pointer on 64-bit processors, and it should be slightly faster since no dereferencing is needed.
Tweening primitive values or small structures seemed like the most common use case to me at the time, but the current design obviously has some downsides for larger structures or structures that can't be copied.


refactor: rename genesis type RegisteredRelayer to RegisteredCounterpartyPayee

Description
Renaming GenesisState field to RegisteredCounterpartyPayee to align
needs: #1513
closes: #XXXX

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards.
[ ] Wrote unit and integration tests
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added relevant godoc comments.
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

Codecov Report

Merging #1514 (49f585b) into main (5e5e2cd) will decrease coverage by 0.02%.
The diff coverage is 87.80%.

@@            Coverage Diff             @@
##             main    #1514      +/-   ##
==========================================
- Coverage   80.27%   80.24%   -0.03%
==========================================
  Files         166      166
  Lines       12252    12257       +5
==========================================
+ Hits         9835     9836       +1
- Misses       1954     1957       +3
- Partials      463      464       +1

Impacted Files
Coverage Δ

modules/apps/29-fee/types/codec.go
44.44% <50.00%> (+0.69%)
:arrow_up:

modules/apps/29-fee/types/genesis.go
78.12% <60.00%> (-3.85%)
:arrow_down:

modules/apps/29-fee/ibc_middleware.go
93.97% <100.00%> (ø)

modules/apps/29-fee/keeper/genesis.go
87.50% <100.00%> (ø)

modules/apps/29-fee/keeper/grpc_query.go
75.54% <100.00%> (ø)

modules/apps/29-fee/keeper/keeper.go
92.48% <100.00%> (ø)

modules/apps/29-fee/keeper/msg_server.go
96.00% <100.00%> (ø)

modules/apps/29-fee/keeper/relay.go
88.23% <100.00%> (ø)

modules/apps/29-fee/types/msgs.go
90.75% <100.00%> (ø)


Feat timeline fractions

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Bug] Step value set, and thumb label

Enabling thumb label, and using a step value will produce a label update even with the intermediate values while dragging.
I tried StepValueContinuously = false, but it doesn't works.
Example:
StepValueContinuously = false
ShowTextAboveThumbs = true
LowerValue = 0
UpperValue = 5
MaximumValue = 0
MinimumValue = 100
StepValue = 1
now, drag the Max thumb.. and the user see the label updated with the intermediate values (5.1, 5.2, 5.3 ....) until you stop dragging, and the label is update with the right clamped value.

My fault.
Once set StepValueContinuously = true, it works as expected :)
Sorry :P

@Magic73 yes, you are right. The property name is misleading. The only reason why I'm not renaming it is that it is already used by a number of developers.


feat: Explore chart link in a new tab on Dashboard

Feat(dashboard): Explore chart button in a new tab
SUMMARY
The "explore chart" button used to open in a new tab in previous 1.X versions. This features was useful as it easily allow editor to modify dashboard while keeping the dashboard view on the original tab. This small PR modify current behavior to open Explore Chart in a new tab.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
TESTING INSTRUCTIONS

Go to a Dashboard
In the Slice Dropdown Menu, click on "Explore Chart"
This will open a new tab

ADDITIONAL INFORMATION

[X] Has associated issue: see #20646
[ ] Required feature flags:
[X] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

Cmd-click (alt-click on Windows) should open in a new tab. It is well documented that same-tab should be the default.

Like @philihp said, it's a link so user can just cmd+click (or, alternatively, click on chart's title, which does the same thing) to open in a new tab. The old behaviour was changed to stay in the same tab by default, as it grants us the benefits of recently implemented Single Page App architecture.

Clear for me. Thank you for you comments


Update to latest from upstream 5.6 (02-Oct-16)

New tested PR without conflicts: https://github.com/webOS-ports/qtwebengine/pull/42


NullPointerException log with no stack trace

Hi,
I've deployed an application with webserver + web client based on Vert.x 3.5.0.
Shortly after it was put in production, I have observed NullPointerExceptions in the log in this form:
2018-01-17 11:10:25.852-0800 vert.x-eventloop-thread-1 ERROR java.lang.NullPointerException
2018-01-17 11:10:36.602-0800 vert.x-eventloop-thread-5 ERROR java.lang.NullPointerException

Intertwined with other exceptions that do not have a stack trace that I will create separate tickets for that also do not have a stack trace in the log.
When I attached Java Flight Recorder I was able to get the stack trace for the NullPointerException:
Stack Trace	Count
      java.lang.RuntimeException.<init>()	4,156
         java.lang.NullPointerException.<init>()	4,156
            io.vertx.core.http.impl.ConnectionManager$ConnQueue.lambda$connectionFailed$2(Channel, Handler, Throwable)	4,156
               io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(boolean, PoolMetrics, Object, ContextTask, Handler)	4,156
                  io.vertx.core.impl.ContextImpl.executeFromIO(ContextTask)	4,156
                     io.vertx.core.http.impl.ConnectionManager$ConnQueue.connectionFailed(ContextImpl, Channel, Handler, Throwable)	4,156
                        io.vertx.core.http.impl.ConnectionManager$ConnQueue.access$1500(ConnectionManager$ConnQueue, ContextImpl, Channel, Handler, Throwable)	4,156
                           io.vertx.core.http.impl.ConnectionManager$ChannelConnector.lambda$connect$2(boolean, HttpVersion, ConnectionManager$ConnQueue, ContextImpl, Waiter, int, String, AsyncResult)	4,156
                              io.vertx.core.net.impl.ChannelProvider.lambda$connect$0(Handler, ChannelFuture, Future)	4,156
                                 io.netty.util.concurrent.DefaultPromise.notifyListener0(Future, GenericFutureListener)	4,156
                                    io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultFutureListeners)	4,156
                                       io.netty.util.concurrent.DefaultPromise.notifyListenersNow()	4,156
                                          io.netty.util.concurrent.DefaultPromise.notifyListeners()	4,156
                                             io.netty.util.concurrent.DefaultPromise.tryFailure(Throwable)	4,156
                                                io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run()	611
                                                   io.netty.util.concurrent.PromiseTask$RunnableAdapter.call()	611
                                                      io.netty.util.concurrent.ScheduledFutureTask.run()	611
                                                         io.netty.util.concurrent.AbstractEventExecutor.safeExecute(Runnable)	611
                                                            io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(long)	611
                                                               io.netty.channel.nio.NioEventLoop.run()	611
                                                                  io.netty.util.concurrent.SingleThreadEventExecutor$5.run()	611
                                                                     java.lang.Thread.run()	611
                                                io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.fulfillConnectPromise(ChannelPromise, Throwable)	3,545
                                                   io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect()	3,545
                                                      io.netty.channel.nio.NioEventLoop.processSelectedKey(SelectionKey, AbstractNioChannel)	3,545
                                                         io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized()	3,545
                                                            io.netty.channel.nio.NioEventLoop.processSelectedKeys()	3,545
                                                               io.netty.channel.nio.NioEventLoop.run()	3,545
                                                                  io.netty.util.concurrent.SingleThreadEventExecutor$5.run()	3,545
                                                                     java.lang.Thread.run()	3,545

I stepped through the code and I was not able to really understand where that exception is happening, and why.

Is this error poorly handled in code?
Is this something that I am not doing right and I need to fix in my code?
Why does the log not include the stacktrace?

Looking at the Event Log in Java Mission Control this is what I see:
Name	Value	Identifier	Content Type	Relational Key
Start Time	1/17/18 1:51:40.518 PM	(startTime)	timestamp
End Time	1/17/18 1:51:40.518 PM	(endTime)	timestamp
Duration	0 s	(duration)	timespan
Class	java.lang.NullPointerException	thrownClass	class
Message		message	text
Event Thread	vert.x-eventloop-thread-5	(thread)	thread
   	Throwable.<init>() line: 251
   	Exception.<init>() line: 54
   	RuntimeException.<init>() line: 51
   	NullPointerException.<init>() line: 60
   	ConnectionManager$ConnQueue.lambda$connectionFailed$2(Channel, Handler, Throwable) line: 370
   	ContextImpl.lambda$wrapTask$2(boolean, PoolMetrics, Object, ContextTask, Handler) line: 342
   	ContextImpl.executeFromIO(ContextTask) line: 200
   	ConnectionManager$ConnQueue.connectionFailed(ContextImpl, Channel, Handler, Throwable) line: 367
   	ConnectionManager$ConnQueue.access$1500(ConnectionManager$ConnQueue, ContextImpl, Channel, Handler, Throwable) line: 193
   	ConnectionManager$ChannelConnector.lambda$connect$2(boolean, HttpVersion, ConnectionManager$ConnQueue, ContextImpl, Waiter, int, String, AsyncResult) line: 533
   	ChannelProvider.lambda$connect$0(Handler, ChannelFuture, Future) line: 43
   	DefaultPromise.notifyListener0(Future, GenericFutureListener) line: 507
   	DefaultPromise.notifyListeners0(DefaultFutureListeners) line: 500
   	DefaultPromise.notifyListenersNow() line: 479
   	DefaultPromise.notifyListeners() line: 420
   	DefaultPromise.tryFailure(Throwable) line: 122
   	AbstractNioChannel$AbstractNioUnsafe$1.run() line: 269
   	PromiseTask$RunnableAdapter.call() line: 38
   	ScheduledFutureTask.run() line: 120
   	AbstractEventExecutor.safeExecute(Runnable) line: 163
   	SingleThreadEventExecutor.runAllTasks(long) line: 403
   	NioEventLoop.run() line: 463
   	SingleThreadEventExecutor$5.run() line: 858
   	Thread.run() line: 748

So this actually has the line numbers for where the exception is happening.
Looks like it's in  io.vertx.core.http.impl.ConnectionManager
In this method:
private void connectionFailed(ContextImpl context, Channel ch, Handler<Throwable> connectionExceptionHandler,
        Throwable t) {
      // If no specific exception handler is provided, fall back to the HttpClient's exception handler.
      // If that doesn't exist just log it
      Handler<Throwable> exHandler =
          connectionExceptionHandler == null ? log::error : connectionExceptionHandler;

      context.executeFromIO(() -> {
        connectionClosed();
        try {
          ch.close();
        } catch (Exception ignore) {
        }
        exHandler.handle(t);
      });
    }
  }

And in this line:
 ch.close();
So somehow the channel is null, and it gets into this method.
This exception is happening very often (10k times in the 2 minutes of Java Flight Recording)
Thank you

I think it's still happening.
I see
2018-05-17 11:47:15.502-0700 vert.x-eventloop-thread-3 ERROR NULL

In the logs
I don't have the stack trace as it happens rarely

@michaelpog sure thanks


Add a case for scheduling to run whenever transitioning from an image pull

If we're using an auto-upgrade image, scheduling needs to wait for the image to be pulled. In this case, we're now waiting for the image to be pulled before proceeding with checking scheduling.
TODO - need to add a test for this.
Checklist

[X] The title of this PR would make a good line in Acorn's Release Note's Changelog
[X] The title of this PR ends with a link to the main issue being address in parentheses, like: This is a title (#1216). Here's an example
[X] All relevant issues are referenced in the PR description. NOTE: don't use GitHub keywords that auto-close issues
[X] Commits follow contributing guidance
[ ] Automated tests added to cover the changes. If tests couldn't be added, an explanation is provided in the Verification and Testing section
[X] Changes to user-facing functionality, API, CLI, and upgrade impacts are clearly called out in PR description
[ ] PR has at least two approvals before merging (or a reasonable exception, like it's just a docs change)

https://github.com/acorn-io/hub/issues/372


Added support form darwin-arm64.

Updated go.mod to have a newer version of golang.org/x/sys that supports darwin-arm64.
Fixed Dockerfile.dapper so that it runs again.

#106

@cbron I know that this is outside the scope of this PR, but would be good to move/mirror this image on our side, just to avoid issues similar to the CIS benchmark forked repo.
https://github.com/rancher/dapper/blob/ab46ce231eeed3520bce79ef8ddba17ac9c34fc4/.drone.yml#L337


perform clock intialization and clock test only on primary processor

BMC as per design should do clock initialization and clock test only for primary processor, host takes care of secondary processors.

BMC as per design should do clock initialization and clock test only for primary processor, host takes care of secondary processors.

It would be better to add some additional details in the commit message ,  .Like recently Hostboot added support to run non-primary processor set_ref clock and cloc test support. This commit is to avoid duplicate hwp procedure execution on secondary prcessor.

BMC as per design should do clock initialization and clock test only for primary processor, host takes care of secondary processors.

It would be better to add some additional details in the commit message , .Like recently Hostboot added support to run non-primary processor set_ref clock and cloc test support. This commit is to avoid duplicate hwp procedure execution on secondary prcessor.

done

done

fixes SW553792


Segmentation fault when MultiplicativeDepth is set to a value less than 0

Hi! I found the following code snippet produce segmentation fault.
#include "openfhe.h"

using namespace lbcrypto;

int main() {
    CCParams<CryptoContextCKKSRNS> parameters;
    parameters.SetMultiplicativeDepth(-1);

    CryptoContext<DCRTPoly> cc = GenCryptoContext(parameters);
    return 0;
}

I think the library should throw proper exception when multiplicative depth value is negative.

Related to @400


TargetProcess Integration Broken

User in this case is reporting that the TogglButton integration with TargetProcess is broken; this after (apparently) TargetProcess has changed their platform.

User now reporting that it works fine. Closing. Will report if another user reports the same issue.

Since @vedr4n has noted that the issue is gone, closing issue now.


Error Unknown response type Json

I am getting an error parsing a Json response. With my limited understanding of Json is it because the response start with array.
I am using request library
https://github.com/request/request
And I am getting the data from the following service.
https://api.tfl.gov.uk/StopPoint/490002072A/Arrivals
Error: Unknown response type: "{"statusCode":200,"body":[{"$type":"Tfl.Api.Presentation.Entities.Prediction, Tfl.Api.Presentation.Entities","id":"-580534719","operationType":1,"vehicleId":"BF65WJK","naptanId":"490002072A","stationName":"Sandilands Tram Stop","lineId":"119","lineName":"119","platformName":"U","direction":"outbound","bearing":"273","destinationNaptanId":"","destinationName":"Purley Way, Colonnades","timestamp":"2019-02-27T09:37:38.4799254Z","timeToStation":156,"currentLocation":"","towards":"South Croydon or West Croydon","expectedArrival":"2019-02-27T09:40:14Z","timeToLive":"2019-02-27T09:40:44Z","modeName":"bus","timing":{"$type":"Tfl.Api.Presentation.Entities.PredictionTiming, Tfl.Api.Presentation.Entities","countdownServerAdjustment":"-00:00:02.6243184","source":"2019-02-27T02:35:21.836Z","insert":"2019-02-27T09:36:59.861Z","read":"2019-02-27T09:36:57.155Z","sent":"2019-02-27T09:37:38Z","received":"0001-01-01T00:00:00Z"}},{"$type":"Tfl.Api.Presentation.Entities.Prediction, Tfl.Api.Presentation.Entities","id":"-739400795","operationType":1,"vehicleId":"BP15OLT","naptanId":"490002072A","stationName":"Sandilands Tram Stop","lineId":"119","lineName":"119","platformName":"U","direction":"outbound","bearing":"273","destinationNaptanId":"","destinationName":"Purley Way, Colonnades","timestamp":"2019-02-27T09:37:38.4799254Z","timeToStation":891,"currentLocation":"","towards":"South Croydon or West Croydon","expectedArrival":"2019-02-27T09:52:29Z","timeToLive":"2019-02-27T09:52:59Z","modeName":"bus","timing":{"$type":"Tfl.Api.Presentation.Entities.PredictionTiming, Tfl.Api.Presentation.Entities","countdownServerAdjustment":"-00:00:02.6751628","source":"2019-02-27T02:35:21.836Z","insert":"2019-02-27T09:37:09.88Z","read":"2019-02-27T09:37:07.17Z","sent":"2019-02-27T09:37:38Z","received":"0001-01-01T00:00:00Z"}},{"$type":"Tfl.Api.Presentation.Entities.Prediction, Tfl.Api.Presentation.Entities","id":"1989751219","operationType":1,"vehicleId":"BP15OMB","naptanId":"490002072A","stationName":"Sandilands Tram Stop","lineId":"119","lineName":"119","platformName":"U","direction":"outbound","bearing":"273","destinationNaptanId":"","destinationName":"Purley Way, Colonnades","timestamp":"2019-02-27T09:37:38.4799254Z","timeToStation":1745,"currentLocation":"","towards":"South Croydon or West Croydon","expectedArrival":"2019-02-27T10:06:43Z","timeToLive":"2019-02-27T10:07:13Z","modeName":"bus","timing":{"$type":"Tfl.Api.Presentation.Entities.PredictionTiming, Tfl.Api.Presentation.Entities","countdownServerAdjustment":"-00:00:02.7104852","source":"2019-02-27T02:35:21.836Z","insert":"2019-02-27T09:37:14.52Z","read":"2019-02-27T09:37:11.825Z","sent":"2019-02-27T09:37:38Z","received":"0001-01-01T00:00:00Z"}},{"$type":"Tfl.Api.Presentation.Entities.Prediction, Tfl.Api.Presentation.Entities","id":"1698915770","operationType":1,"vehicleId":"LJ08CTE","naptanId":"490002072A","stationName":"Sandilands Tram Stop","lineId":"194","lineName":"194","platformName":"U","direction":"outbound","bearing":"273","destinationNaptanId":"","destinationName":"West Croydon","timestamp":"2019-02-27T09:37:38.4799254Z","timeToStation":1532,"currentLocation":"","towards":"South Croydon or West Croydon","expectedArrival":"2019-02-27T10:03:10Z","timeToLive":"2019-02-27T10:03:40Z","modeName":"bus","timing":{"$type":"Tfl.Api.Presentation.Entities.PredictionTiming, Tfl.Api.Presentation.Entities","countdownServerAdjustment":"-00:00:02.7146433","source":"2019-02-27T02:35:21.836Z","insert":"2019-02-27T09:36:49.846Z","read":"2019-02-27T09:36:47.139Z","sent":"2019-02-27T09:37:38Z","received":"0001-01-01T00:00:00Z"}},{"$type":"Tfl.Api.Presentation.Entities.Prediction, Tfl.Api.Presentation.Entities","id":"-15610565","operationType":1,"vehicleId":"LJ13CHY","naptanId":"490002072A","stationName":"Sandilands Tram Stop","lineId":"194","lineName":"194","platformName":"U","direction":"outbound","bearing":"273","destinationNaptanId":"","destinationName":"West Croydon","timestamp":"2019-02-27T09:37:38.4799254Z","timeToStation":634,"currentLocation":"","towards":"South Croydon or West Croydon","expectedArrival":"2019-02-27T09:48:12Z","timeToLive":"2019-02-27T09:48:42Z","modeName":"bus","timing":{"$type":"Tfl.Api.Presentation.Entities.PredictionTiming, Tfl.Api.Presentation.Entities","countdownServerAdjustment":"-00:00:02.6688867","source":"2019-02-27T02:35:21.836Z","insert":"2019-02-27T09:36:49.846Z","read":"2019-02-27T09:36:47.139Z","sent":"2019-02-27T09:37:38Z","received":"0001-01-01T00:00:00Z"}},{"$type":"Tfl.Api.Presentation.Entities.Prediction, Tfl.Api.Presentation.Entities","id":"-1803100894","operationType":1,"vehicleId":"LJ10HVE","naptanId":"490002072A","stationName":"Sandilands Tram Stop","lineId":"198","lineName":"198","platformName":"U","direction":"outbound","bearing":"273","destinationNaptanId":"","destinationName":"Thornton Heath, High Street","timestamp":"2019-02-27T09:37:38.4799254Z","timeToStation":1160,"currentLocation":"","towards":"South Croydon

It appears to be valid based on jsonlint.com
Is this error happening when trying to use Dialogflow?

It turned to be error in my script. Looking at the stack trace in Firebase console I made the assumption DialogFlow was not able to parse the JSON.
 at WebhookClient.addResponse_ (/user_code/node_modules/dialogflow-fulfillment/src/dialogflow-fulfillment.js:277:13)     at responses.forEach (/user_code/node_modules/dialogflow-fulfillment/src/dialogflow-fulfillment.js:243:51)


webrtc_streamer fails when server and client are not the same machine

I am trying to get audio from streamlit clients. I have implemented the simple first example:
from streamlit_webrtc import webrtc_streamer
webrtc_streamer(key="sample")

It works on my PC. When I use my PC as a server or use a cloud server it does not.
If I press "START" I get the error "navigator.MediaDevices is undefined. It seems the current document is not loaded securely."
If I press "SELECT DEVICE" I get "Component Error"
This happens with an android phone and iOS on an iPad and with a PC when using a cloud server.
Additionally, when running the code on a DigitalOcean droplet I get the following warning, fyi:
/miniconda3/lib/python3.12/site-packages/google_crc32c/__init__.py:29: RuntimeWarning: As the c extension couldn't be imported, google-crc32c is using a pure python implementation that is significantly slower. If possible, please configure a c build environment and compile the extension   warnings.warn(_SLOW_CRC32C_WARNING, RuntimeWarning)

I also tried on streamlit.app at https://webrtctestzz.streamlit.app/. Different errors.
Start gives: 'NotReadableError: Could not start video source"
Select device gives: "Device not available (Could not start video source)"
This is all curious since the following app works on all platforms: https://style-transfer-webrtc.streamlit.app

OK. I have to add https.


Fix "OpenRefine" cannot be opened because the developer cannot be verified - on MacOS

Is your feature request related to a problem or area of OpenRefine? Please describe.
OpenRefine will not open on MacOS - this error is presented:

Describe the solution you'd like
Build OpenRefine with a verified developer so this error does not occur.
Describe alternatives you've considered

Open System Preferences
Open Security & Privacy
If you have recently been prevented from opening OpenRefine by the reported error, you can bypass this restriction in this System Preferences panel.

Additional context
This issue could be addressed by improving the download instructions to include the work around, or by including a text file describing the workaround in the downloaded disk image.

You didn't describe which download instructions URL you followed along with.
Was it ours here? https://github.com/OpenRefine/OpenRefine/wiki/Installation-Instructions#macos

Duplicate of #2191

I'll close this issue since it's a duplicate.  Please take a look at our explanation in #2191
And thanks for using OpenRefine!  If you have other issues, please let us know!


Learn Functional Programming by Building a Spreadsheet - Main menu description

Describe the Issue

I believe we should improve the final phrase:
"This project will cover concepts like the map() method, find() method, parseInt(), the includes() method."

Affected Page
https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures-v8/
Your code
.
Expected behavior

Change it maybe to this:
"This project will cover concepts like the map(), find(), parseInt(), and includes() methods."

Screenshots
No response
System
.
Additional context
No response

Thanks for opening this issue.
This looks like something that can be fixed by "first-time" code contributors to this repository. Here are the files that you should be looking at to work on a fix:
List of files:

https://github.com/freeCodeCamp/freeCodeCamp/blob/main/client/i18n/locales/english/intro.json

Please make sure you read our guidelines for contributing, we prioritize contributors following the instructions in our guides. Join us in our chat room or our forum if you need help contributing; our moderators will guide you through this.
Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first.
Happy contributing.

Hi,
Hope you are doing great.
I would like to work on this.

We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue.
Issues labeled with help wanted or first timers only are open for contributions.
Please make sure you read our guidelines for contributing. We prioritize contributors following the instructions in our guide. Join us in our chat room or the forum if you need help contributing - our community will be happy to assist you.

The bug has been resolved.
I have created a pull request.
Please verify.


[Bug]: Handle parameters in "Content-Type=; charset=utf-8"

zot version
v1.4.3 and above
Describe the bug
Expect and handle parameters. Although the spec says exact media-type, but clients may add params.
To reproduce

Configuration
Client tool used
Seen error

Expected behavior
No response
Screenshots
No response
Additional context
No response

@rchincha can you please update the description to be more explicit?

Related to https://github.com/opencontainers/distribution-spec/issues/408

https://github.com/opencontainers/distribution-spec/pull/469
^ we should probably expect paramaters (to be safe) but ignore everything except params[0]


Consumption update

Consumption sensors are now displaying data from the most recent midnight until current time as opposed to 24 hours * number of days back.
Consumption sensors are now only updated at startup, at midnight and when the car is unplugged.
Lifetime energy sensor added (and rounded).
Voltage sensor main sensor now inVoltageT2T3 since the voltage sensor used before is not anymore available within the SignalR stream.

Great stuff. Makes sense with the change

Great stuff. Makes sense with the change