Bump to .NET 7 to version 7.0.100-rc.2.22477.20

PR Summary
Update .NET 7 to version RC2 and update related packages
PR Context

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:

[ ] Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
(which runs in a different PS Host).

[ ] Issue filed:

[ ] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.

[ ] Issue filed:

[ ] Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).

[ ] Issue filed:

[ ] Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[ ] Issue filed:

I see:
Start-PSBuild -Clean
Cleaning your working directory. You can also do it with 'git clean -fdX --exclude .vs/PowerShell/v16/Server/sqlite3'
WARNING: The 'dotnet' in the current path can't find SDK version 7.0.100-rc.2.22477.20, prepending C:\Users\1\AppData\Local\Microsoft\dotnet to PATH.
WARNING: The currently installed .NET Command Line Tools is not the required version.

Installed version: 7.0.100-rc.2.22477.23
Required version: 7.0.100-rc.2.22477.20

Version 7.0.100-rc.2.22477.23 is official from https://dotnet.microsoft.com/en-us/download/dotnet/7.0


Using tfdbg with errors.

VERSION: TF-1.4.0
Problem:
I want to use tfdbg to debug NaN problem with tf_debug.LocalCLIDebugHook() , but encounter thie problem.
One more question, how to lower the size of dump files?
Logging is below:
Traceback (most recent call last):
  File "./train.py", line 166, in <module>
    _, loss, l2_loss, predicted, labels, label_lengths, step = sess.run(ops)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/monitored_session.py", line 521, in run
    run_metadata=run_metadata)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/monitored_session.py", line 892, in run
    run_metadata=run_metadata)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/monitored_session.py", line 967, in run
    raise six.reraise(*original_exc_info)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/monitored_session.py", line 952, in run
    return self._sess.run(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/monitored_session.py", line 1032, in run
    run_metadata=run_metadata))
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/debug/wrappers/hooks.py", line 157, in after_run
    self._session_wrapper.on_run_end(on_run_end_request)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/debug/wrappers/local_cli_wrapper.py", line 321, in on_run_end
    self._dump_root, partition_graphs=partition_graphs)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/debug/lib/debug_data.py", line 495, in __init__
    self._load_all_device_dumps(partition_graphs, validate)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/debug/lib/debug_data.py", line 517, in _load_all_device_dumps
    self._load_partition_graphs(partition_graphs, validate)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/debug/lib/debug_data.py", line 798, in _load_partition_graphs
    self._validate_dump_with_graphs(debug_graph.device_name)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/debug/lib/debug_data.py", line 874, in _validate_dump_with_graphs
    (node, datum.timestamp, repr(pending_inputs[node])))
ValueError: Causality violated in timing relations of debug dumps: model_train/model/model/decoder/while/BasicDecoderStep/TrainingHelperNextInputs/cond/Merge<PHONE_NUMBER>071447): these input(s) are not satisfied: [(u'model_train/model/model/decoder/while/BasicDecoderStep/TrainingHelperNextInputs/cond/Switch_1', 1)]

@zh794390558 Is it possible to share a minimum reproducible program, to help debug the problem?
@caisq might have some suggestions here.

@zh794390558 One way to reduce the size of the dump is to reduce your batch size.
Also, as @tatatodd suggested, a reproduction code would be helpful for me to diagnose the problem.

@zh794390558 another question for you: what operating system are you using with TF?

@caisq my OS  is centos, and the code is too large which is attention-based seq-2-seq model.   The https://github.com/tensorflow/nmt  repo is same to my.

I tried running tfdbg on the nmt model, so far I can't repro the issue on CPU yet. Will try again on a GPU machine soon.

@caisq I met the same problem in a GPU machine, but when switched to CPU, the issue is gone.

@zh794390558 @reset I tested the nmt model with tfdbg on a GPU machine

GeForce GTX 1050 Ti 4GB
Ubuntu 16.04
tf-nightly-gpu version: 1.5.0-dev20171206. (This is close to HEAD, installed with pip install tf-nightly-gpu)

The code I used to activate tfdbg is at: https://github.com/caisq/nmt/commit/a0591f3b7650f1be0d16ac681ec5df0686daaf65
I couldn't reproduce the error. I ran a few training iterations and couldn't observe any crashes of the sort you mentioned. Am I missing any keys to reproducing this issue?

@caisq tensorflow version maybe? both @zh794390558 and I are working on tf 1.4.0. I installed it with pip directly. maybe you can give it a try.

It has been 14 days with no activity and this issue has an assignee.Please update the label and/or status accordingly.

Nagging Assignee: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @caisq: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @caisq: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @caisq: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @caisq: It has been 15 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @caisq: It has been 169 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @caisq: It has been 184 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @caisq: It has been 199 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @caisq: It has been 214 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @caisq: It has been 244 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @caisq: It has been 259 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @caisq: It has been 274 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @caisq: It has been 289 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!


Use SPDX license expression

[x] I agree to follow the project's code of conduct.
[x] I added an entry to CHANGES.md if knowledge of this change could be valuable to users.
[x] I ran cargo fmt

Uses a SPDX license expression as recommended by Cargo.
This enables e.g. parsing via the CycloneDX Rust Cargo Plugin.

@bors r+

Filed #107 for the CI failure.

bors retry

bors r+


[SPARK-26191][SQL] Control truncation of Spark plans via maxFields parameter

What changes were proposed in this pull request?
In the PR, I propose to add maxFields parameter to all functions involved in creation of textual representation of spark plans such as simpleString and verboseString. New parameter restricts number of fields converted to truncated strings. Any elements beyond the limit will be dropped and replaced by a "... N more fields" placeholder. The threshold is bumped up to Int.MaxValue for toFile().
How was this patch tested?
Added a test to QueryExecutionSuite which checks maxFields impacts on number of truncated fields in LocalRelation.

Can one of the admins verify this patch?

ping @hvanhovell

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/5419/
Test PASSed.

Test build #99342 has started for PR 23159 at commit e9e7893.

Test build #99342 has finished for PR 23159 at commit e9e7893.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/99342/
Test PASSed.

@gatorsmile @cloud-fan Could you look at the changes - extracted from another PR: https://github.com/apache/spark/pull/22429

Test build #99513 has started for PR 23159 at commit bf968be.

Test build #99513 has finished for PR 23159 at commit bf968be.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/99513/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/5578/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/5584/
Test PASSed.

Test build #99520 has started for PR 23159 at commit a5e82f7.

Test build #99520 has finished for PR 23159 at commit a5e82f7.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/99520/
Test FAILed.

jenkins, retest this, please

Test build #99527 has started for PR 23159 at commit a5e82f7.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/5590/
Test PASSed.

@HyukjinKwon @dongjoon-hyun @srowen @zsxwing Do you have any objections of this PR?

Rather than change every single call to this method, if this should generally be the value of the argument, then why not make it the default value or something?

Test build #99678 has finished for PR 23159 at commit b6fa959.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/99678/
Test PASSed.

Rather than change every single call to this method, if this should generally be the value of the argument, then why not make it the default value or something?

New parameter aims to solve the problem when there are multiple callers, and each of them needs different maximum fields. So, a feasible approach is to propagate maxFields from callers to truncatedString. Changing global SQL config does not solve the problem.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/5760/
Test PASSed.

Test build #99715 has finished for PR 23159 at commit e0aa626.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/99715/
Test FAILed.

jenkins, retest this, please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/99735/
Test PASSed.

cc @cloud-fan and @gatorsmile .

Looks okay but let me leave it to @cloud-fan, @gatorsmile and @hvanhovell

@hvanhovell We all are waiting for your decision ;-). Please, review the PR.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/6313/
Test PASSed.

Test build #100349 has started for PR 23159 at commit 9acdf9d.

Test build #100349 has finished for PR 23159 at commit 9acdf9d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/100349/
Test PASSed.

I am going to close the PR since nobody interested in it :-(

@MaxGekk can you resolve the merge conflicts?

LGTM

Test build #100425 has started for PR 23159 at commit c6ad275.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/6389/
Test PASSed.

Merged build finished. Test PASSed.

merging to master.


frontend_server --initialize-from-dill does not account for autodetected sound mode

In https://github.com/flutter/flutter/pull/68898 I will land a mitigation that caches a sound dill separately from a non-sound dill. This only works if --sound-null-safety is specified from the command line.
If the soundness mode is autodetected, then the tool does not know whether the dill was compiled in sound or unsound mode.
There are three potential long term fixes:

The frontend_server accounts for sound/unsound in --initialize-from-dill and recompiles accordingly
The frontend_server communicates in some way to the tool what mode the dill was compiled in, and the tool implements additional caching logic to account for this.
The tool disables --initialize-from-dill

@jonahwilliams I am having a very similar problem with the expression compiler worker (that provides expression evaluation for webdev and google3). I was thinking about the following approach:

add null safety mode to metadata
add a "setNullSafetyMode" API to the expression compiler worker/frontend server
after the page is loaded in the debugger, read the metadata and let the worker/server know
what the mode is before loading dependency dill files

the worker/server in that case will load the corresponding sdk (instead of loading it on start)
this will need some refactoring of how we currently initialize the worker/server
the frontend server might need to know the mode before the debugger starts,
but it has assess to the metadata and can read the information from there directly

How does this sound?

/cc @jensjoha

When the incremental compiler is asked to load from dill it also knows which settings it is asked to compile with. It should give an error if the two are not compatible, that it doesn't is a bug and I'll fix that.
@annagrin either I'm mis-reading what you're writing (or missing something else) or you're talking about adding as metadata information that is already available.
For a little background information:

Each kernel library has a nnbd compilation mode (nonNullableByDefaultCompiledMode) and a isNonNullableByDefault
Each component (should) have a nnbd compilation mode (mode, modeRaw)
When asking to compile something the options given specify it as well

Is there something I'm missing?

@jensjoha the situation Anna is describing is a bit different because the tool which is passing in the dill files is not actually the tool that compiled them - it doesn't know the current mode and it doesn't actually read the dill files either (it is really just an intermediary between bazel/build_runner and the expression compiler worker).

@jensjoha @jakemac53 You are right - I thought that the situations are similar but  frontend server and expression compiler worker are different wrt compilation information. Frontend server gets the soundness info from compiling the app, and expression compilation worker just loads dill files from an unknown compilation. Even if the information is stored in the dill files, the expression compilation worker cannot load them without matching sdk outline file, so it has to get soundness info from somewhere. Metadata seems appropriate enough... So please ignore the my messages, as they seem not relevant:)

I think that the expression compiler worker will still benefit from better error reporting here though - we had discussed adding that ourselves but may no longer need to (although it wouldn't hurt as an extra layer of invalidation if it is cheap to do).

It would probably be best to capture that in a new issue on the Dart SDK? This is specifically about caching dills for the flutter tool build process

Yes, agreed that it isn't directly related to this

This is fixed


Missing file

For the DEB package, this shows: "404 That file isn’t here anymore".

hi @JakubTetek,
thanks for the report. Could you please let me know where exactly this one is happening? Immediately when you open the app?

Ah, got it. The link to DEB package.

I'll fix the readme file. Meanwhile you can get the deb package on releases page - https://github.com/KryDos/todoist-linux/releases

thanks again @JakubTetek, I've changed the readme file.


add Yorango to INTHEWILD.md

Successfully using both vertical and horizontal scrolling (on mobile) in production for Yorango's Listings marketplace :)

I'm glad you found it useful! Thanks for the contribution. :)


Change Expiry Time of tokens?

Can anyone help me with this?

You can change the expire date by overwriting the ACCESS_TOKEN_EXPIRE_SECONDS like so:
# expires in 6 months
from oauth2_provider import settings as oauth2_settings
oauth2_settings.DEFAULTS['ACCESS_TOKEN_EXPIRE_SECONDS'] = 1.577e7

Thanks wagner!


update ETCDUnitSize  for VirtualCluster

What type of PR is this?
/kind feature

What does this PR do?
update ETCDUnitSize  for VirtualCluster set

Which issue(s) does this PR fix?

Fixes #
Special notes for your reviewer:

Does this PR introduce a user-facing change?

see https://github.com/kosmos-io/kosmos/pull/707/checks?check_run_id=30087887457

see https://github.com/kosmos-io/kosmos/pull/707/checks?check_run_id=30087887457

already update


feat: Add tertiary brand color variable

This is connected to #374, a ticket I added for including a tertiary brand color variable in the color-palette settings file.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Attempt to invoke virtual method 'java.io.OutputStream' java.net.Socket.getOutputStream on a null object reference.

Description
I have print btn.
When I click for the first time everything is fine. Sometimes I click a second time and it's also good, but there is such a random error
Steps to reproduce
Steps to reproduce the behavior:
const client = TcpSocket.createConnection({
            host: printer.ip,
            port: printer.port,
          }, () => {
            client.write(data);
            client.destroy();
          });

          client.on('error', (error) => {
          });

          client.on('close', () => {
          });
  });

Current behavior
Attempt to invoke virtual method 'java.io.OutputStream' java.net.Socket.getOutputStream on a null object reference.
Expected behavior
Code to need works.
Screenshots

Relevant information

OS
android

react-native
0.64.3

react-native-tcp-socket
5.6.0

You can use my fork at https://github.com/gajjartejas/react-native-tcp


Fr proxy documentation is incomplete: /fr/docs/Web/JavaScript/Reference/Objets_globaux/Proxy

Hello,
Not sure if I should post this in french or english... Let's say english.
I just observed that the french version of the documentation about proxies is lacking the description of all the traps methods one can find in the english version.

french: https://developer.mozilla.org/fr/docs/Web/JavaScript/Reference/Objets_globaux/Proxy#Méthodes_pour_le_gestionnaire
english: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy#Methods_of_the_handler_object

I didn't check if the same problem appears for other languages.
Cheers!

Hi @Blind4Basics !
Unfortunately there are a lot of translations on MDN that are not up to date with the English version. We don't ave an official transation procedure, or teams working on them all. It is done on an adhoc volunteer basis, mostly.
Would you be interested in bringing this translation to up to date? @SphinxKnight does alot of French translations, and could help you with some pointers.

Hello @Blind4Basics bonjour :)
I'll go with English as well for Chris ^^.
Thanks for the feedback, there was a typo in the "macro" which was supposed to list all of the methods: that I fixed.
However this is just a quick patch and this "old" macro should be removed altogether + the page needs a bit of love. @Blind4Basics would you be interested in updating the page so that it matches the English version? If not, tell me and I'll take care :)
As Chris said, this is all done on a volunteering basis so if you want/are able to lend a hand, you're more than welcome :)

Hello, again,
Thanks for the suggestion (and the correction, ofc). Unfortunately, I'm only a hobbyist at coding, so... I'm sorry but I'm not volunteer to go further for now.  ;s
thx again and take care!


Trying to create a simple job after installation -

Hi All,
After installing  the components of hydro graph i am unable to execute a simple job
I am attaching the output from the console and also the log file that was created
Kindly help
console_output.txt
test_Job_1447992331_1509650889666_1509651221569.log

Hi @nagarjunsrinivasICF,
Looks like Gradle is unable to resolve the dependencies for your job to execute. You may need to update the repositories section in build.gradle on your ELT project to add the repository URLs that contain the repositories. For example -
repositories {
mavenLocal()
mavenCentral()
maven {
url 'http://conjars.org/repo/'
}
maven {
url 'http://maven.twttr.com/'
}
maven {
    name 'redshift'
    url 'http://redshift-maven-repository.s3-website-us-east-1.amazonaws.com/release'
}

}
For the Oracle and teradata dependencies, you will have to manually add them in your repo cache under $HOME/.m2/repositories folder. If you are not using any Oracle or Teradata components, you may choose to comment out the dependencies in the build.gradle file of your project.

Closing this issue due to inactivity for 5 days. Please reopen the issue if more information is required.


Use original level strings

The level_str breaks the color coding of log levels e.g. in Grafana. Using the original as_str from tracing_core::Level fixes this issue.

"Original level strings" seems to mean "level strings from tracing_core which have no relation to Loki".
Could the strings be taken from https://grafana.com/docs/grafana/latest/packages_api/data/loglevel/ instead?

Member
Value

alert
"critical"

crit
"critical"

critical
"critical"

dbug
"debug"

debug
"debug"

emerg
"critical"

eror
"error"

err
"error"

error
"error"

fatal
"critical"

info
"info"

information
"info"

informational
"info"

notice
"info"

trace
"trace"

unknown
"unknown"

warn
"warning"

warning
"warning"

So perhaps "trace", "debug", "info", "warning", "error"?

Going with Level.as_str is in my opinion the easier implementation

"easier" is very far back in my list of implementation concerns. First come correctness and sensibility.
I can see the argument that matching the default level output of tracing_subscriber::fmt is good.
I would somehow assume that uppercase is uncommon in structured logs, but that was just a gut feeling not backed by any data. The screenshot in your documentation link does show lowercase log levels. I'll try looking for some other Loki client libraries.

I only found these:
https://github.com/grafana/loki/blob/31ca108a3cf5bcb87ffeb54d06d6fa4c53e4830d/clients/pkg/promtail/targets/gelf/gelftarget.go#L24-L34
https://github.com/grafana/loki/blob/31ca108a3cf5bcb87ffeb54d06d6fa4c53e4830d/clients/pkg/promtail/targets/journal/journaltarget.go#L363-L383
So maybe go with the lowercased variants of the tracing levels? "error", "warn", "info", "debug", "trace"?

sounds good, I updated the PR

Thanks!

Released a new version tracing-loki 0.2.0 on crates.io.

Thank you!


Make MOSN support Istio1.4

Solutions
a new pr for merge

These are related to PR review records https://github.com/mosn/mosn/pull/1025 and https://github.com/mosn/mosn/pull/1001.


Add IPv6 Local Address

Without having a local ipv6 address, ex local 2001:db8::1, in the server.conf, openvpn prefers ipv4 and uses ipv6 only when ipv4 is not available. Adding this onto my local configuration has let chrome use happy eyeballs again to pick whatever is faster.

Nevermind, it looks like my ip address extension on chrome just had cached data and it wasn't actually using ipv6 more than v4.

@Rishi556 That is quite interesting, thanks for posting.


Error in Explorer Connections is not readable

The error resulting from scaffolding is not readable. It's possible to do Toggle Developer Tools and search for it, but I think it should be possible to view the whole error without doing that.

The full error shows if you hover over that red message. I'll add a better way to view it. You can also find the log file by going to Settings > Open App Data Folder > Logs folder

Thank you, yes it actually does show the error after a couple of seconds on hover.

#202 adds a way to copy the error text to the clipboard by just clicking the error bubble. Will go out with next release.


convert coverageGlobalScope to support service workers

Fixes: https://github.com/iFaxity/vite-plugin-istanbul/issues/103

LGTM! Merging and will publish a new version soon.
Thanks for the contribution.


[bug] Navbar doesn't hide in fullscreen

Disappears in tachiyomi fullscreen but not neko

fixed in 1.0.6


feat: add prerenderPresetDefault

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#471  👈
#465
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @hi-ogawa and the rest of your teammates on  Graphite

Merge activity

Jul 1, 4:28 AM EDT: @hi-ogawa started a stack merge that includes this pull request via Graphite.


Project: Wpf .NET5

[Enter feedback here]

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

ID: ba9dc9d2-795c-9612-3585-408b4621c080
Version Independent ID: f73fc16d-d842-4507-9fdb-b42856720355
Content: Getting started with WebView2 for WPF apps - Microsoft Edge Development
Content Source: microsoft-edge/webview2/gettingstarted/wpf.md
Product: microsoft-edge
Technology: webview
GitHub Login: @MSEdgeTeam
Microsoft Alias: msedgedevrel

Project Wpf .NET5
Visual Studio Community Version 16.9.0 Preview 1.0
WebView2 version 1.0.664.37
source = new Uri("https://www.microsoft.com");
Output: blank view.

Hi @terrytham, sorry to hear about this issue. Are you still encountering this issue?


Cannot compile startHere example

Im having probems in compiling the startHere example. Im using Arduino IDE 1.8.3, already downloaded SimpleList, ArduinoJson. Updated esp8266 packages (2.4.0) and removed the old ones. Im getting this error when trying to compile using the  NodeMCU 1.0(ESP-12E Module).
In file included from /home/andre/.arduino15/packages/esp8266/hardware/esp8266/2.4.0/tools/sdk/lwip2/include/lwip/ip_addr.h:43:0,                  from /home/andre/.arduino15/packages/esp8266/hardware/esp8266/2.4.0/tools/sdk/include/user_interface.h:30,                  from /home/andre/arduino-1.8.3/libraries/easyMesh-master/src/easyMeshSTA.cpp:13: /home/andre/arduino-1.8.3/libraries/easyMesh-master/src/easyMeshSTA.cpp: In member function 'void easyMesh::tcpConnect()': /home/andre/.arduino15/packages/esp8266/hardware/esp8266/2.4.0/tools/sdk/lwip2/include/lwip/ip4_addr.h:199:54: error: request for member 'addr' in '*(uint8*)(&((easyMesh*)this)->easyMesh::_stationConn.espconn::proto.espconn::<anonymous union>::tcp->_esp_tcp::local_ip)', which is of non-class type 'uint8 {aka unsigned char}'  #define ip4_addr1(ipaddr) (((const u8_t*)(&(ipaddr)->addr))[0])                                                       ^ /home/andre/.arduino15/packages/esp8266/hardware/esp8266/2.4.0/tools/sdk/lwip2/include/lwip/ip4_addr.h:205:38: note: in expansion of macro 'ip4_addr1'  #define ip4_addr1_16(ipaddr) ((u16_t)ip4_addr1(ipaddr))                                       ^ /home/andre/.arduino15/packages/esp8266/hardware/esp8266/2.4.0/tools/sdk/lwip2/include/arch/cc.h:87:24: note: in expansion of macro 'ip4_addr1_16'  #define IP2STR(ipaddr) ip4_addr1_16(ipaddr), \                         ^ /home/andre/arduino-1.8.3/libraries/easyMesh-master/src/easyMeshSTA.cpp:199:23: note: in expansion of macro 'IP2STR'                        IP2STR(_stationConn.proto.tcp->local_ip),                        ^ /home/andre/.arduino15/packages/esp8266/hardware/esp8266/2.4.0/tools/sdk/lwip2/include/lwip/ip4_addr.h:200:54: error: request for member 'addr' in '*(uint8*)(&((easyMesh*)this)->easyMesh::_stationConn.espconn::proto.espconn::<anonymous union>::tcp->_esp_tcp::local_ip)', which is of non-class type 'uint8 {aka unsigned char}'  #define ip4_addr2(ipaddr) (((const u8_t*)(&(ipaddr)->addr))[1])                                                       ^ /home/andre/.arduino15/packages/esp8266/hardware/esp8266/2.4.0/tools/sdk/lwip2/include/lwip/ip4_addr.h:206:38: note: in expansion of macro 'ip4_addr2'  #define ip4_addr2_16(ipaddr) ((u16_t)ip4_addr2(ipaddr))                                       ^ /home/andre/.arduino15/packages/esp8266/hardware/esp8266/2.4.0/tools/sdk/lwip2/include/arch/cc.h:88:5: note: in expansion of macro 'ip4_addr2_16'      ip4_addr2_16(ipaddr), \      ^ /home/andre/arduino-1.8.3/libraries/easyMesh-master/src/easyMeshSTA.cpp:199:23: note: in expansion of macro 'IP2STR'                        IP2STR(_stationConn.proto.tcp->local_ip),                        ^ /home/andre/.arduino15/packages/esp8266/hardware/esp8266/2.4.0/tools/sdk/lwip2/include/lwip/ip4_addr.h:201:54: error: request for member 'addr' in '*(uint8*)(&((easyMesh*)this)->easyMesh::_stationConn.espconn::proto.espconn::<anonymous union>::tcp->_esp_tcp::local_ip)', which is of non-class type 'uint8 {aka unsigned char}'  #define ip4_addr3(ipaddr) (((const u8_t*)(&(ipaddr)->addr))[2])                                                       ^ /home/andre/.arduino15/packages/esp8266/hardware/esp8266/2.4.0/tools/sdk/lwip2/include/lwip/ip4_addr.h:207:38: note: in expansion of macro 'ip4_addr3'  #define ip4_addr3_16(ipaddr) ((u16_t)ip4_addr3(ipaddr))                                       ^ /home/andre/.arduino15/packages/esp8266/hardware/esp8266/2.4.0/tools/sdk/lwip2/include/arch/cc.h:89:5: note: in expansion of macro 'ip4_addr3_16'      ip4_addr3_16(ipaddr), \      ^ /home/andre/arduino-1.8.3/libraries/easyMesh-master/src/easyMeshSTA.cpp:199:23: note: in expansion of macro 'IP2STR'                        IP2STR(_stationConn.proto.tcp->local_ip),                        ^ /home/andre/.arduino15/packages/esp8266/hardware/esp8266/2.4.0/tools/sdk/lwip2/include/lwip/ip4_addr.h:202:54: error: request for member 'addr' in '*(uint8*)(&((easyMesh*)this)->easyMesh::_stationConn.espconn::proto.espconn::<anonymous union>::tcp->_esp_tcp::local_ip)', which is of non-class type 'uint8 {aka unsigned char}'  #define ip4_addr4(ipaddr) (((const u8_t*)(&(ipaddr)->addr))[3])                                                       ^ /home/andre/.arduino15/packages/esp8266/hardware/esp8266/2.4.0/tools/sdk/lwip2/include/lwip/ip4_addr.h:208:38: note: in expansion of macro 'ip4_addr4'  #define ip4_addr4_16(ipaddr) ((u16_t)ip4_addr4(ipaddr))                                       ^ /home/andre/.arduino15/packages/esp8266/hardware/esp8266/2.4.0/tools/sdk/lwip2/include/arch/cc.h:90:5: note: in expansion of macro 'ip4_addr4_16'      ip4_addr4_16(ipaddr)      ^ /home/andre/arduino-1.8.3/libraries/easyMesh-master/src/easyMeshSTA.cpp:199:23: note: in expansion of macro 'IP2STR'                        IP2STR(_stationConn.proto.tcp->local_ip),                        ^ /home/andre/.arduino15/packages/esp8266/hardware/esp8266/2.4.0/tools/sdk/lwip2/include/lwip/ip4_addr.h:199:54: error: request for member 'addr' in '*(uint8*)(&((easyMesh*)this)->easyMesh::_stationConn.espconn::proto.espconn::<anonymous union>::tcp->_esp_tcp::remote_ip)', which is of non-class type 'uint8 {aka unsigned char}'  #define ip4_addr1(ipaddr) (((const u8_t*)(&(ipaddr)->addr))[0])                                                       ^ /home/andre/.arduino15/packages/esp8266/hardware/esp8266/2.4.0/tools/sdk/lwip2/include/lwip/ip4_addr.h:205:38: note: in expansion of macro 'ip4_addr1'  #define ip4_addr1_16(ipaddr) ((u16_t)ip4_addr1(ipaddr))                                       ^ /home/andre/.arduino15/packages/esp8266/hardware/esp8266/2.4.0/tools/sdk/lwip2/include/arch/cc.h:87:24: note: in expansion of macro 'ip4_addr1_16'  #define IP2STR(ipaddr) ip4_addr1_16(ipaddr), \                         ^ /home/andre/arduino-1.8.3/libraries/easyMesh-master/src/easyMeshSTA.cpp:201:23: note: in expansion of macro 'IP2STR'                        IP2STR(_stationConn.proto.tcp->remote_ip),                        ^ /home/andre/.arduino15/packages/esp8266/hardware/esp8266/2.4.0/tools/sdk/lwip2/include/lwip/ip4_addr.h:200:54: error: request for member 'addr' in '*(uint8*)(&((easyMesh*)this)->easyMesh::_stationConn.espconn::proto.espconn::<anonymous union>::tcp->_esp_tcp::remote_ip)', which is of non-class type 'uint8 {aka unsigned char}'  #define ip4_addr2(ipaddr) (((const u8_t*)(&(ipaddr)->addr))[1])                                                       ^ /home/andre/.arduino15/packages/esp8266/hardware/esp8266/2.4.0/tools/sdk/lwip2/include/lwip/ip4_addr.h:206:38: note: in expansion of macro 'ip4_addr2'  #define ip4_addr2_16(ipaddr) ((u16_t)ip4_addr2(ipaddr))                                       ^ /home/andre/.arduino15/packages/esp8266/hardware/esp8266/2.4.0/tools/sdk/lwip2/include/arch/cc.h:88:5: note: in expansion of macro 'ip4_addr2_16'      ip4_addr2_16(ipaddr), \      ^ /home/andre/arduino-1.8.3/libraries/easyMesh-master/src/easyMeshSTA.cpp:201:23: note: in expansion of macro 'IP2STR'                        IP2STR(_stationConn.proto.tcp->remote_ip),                        ^ /home/andre/.arduino15/packages/esp8266/hardware/esp8266/2.4.0/tools/sdk/lwip2/include/lwip/ip4_addr.h:201:54: error: request for member 'addr' in '*(uint8*)(&((easyMesh*)this)->easyMesh::_stationConn.espconn::proto.espconn::<anonymous union>::tcp->_esp_tcp::remote_ip)', which is of non-class type 'uint8 {aka unsigned char}'  #define ip4_addr3(ipaddr) (((const u8_t*)(&(ipaddr)->addr))[2])                                                       ^ /home/andre/.arduino15/packages/esp8266/hardware/esp8266/2.4.0/tools/sdk/lwip2/include/lwip/ip4_addr.h:207:38: note: in expansion of macro 'ip4_addr3'  #define ip4_addr3_16(ipaddr) ((u16_t)ip4_addr3(ipaddr))                                       ^ /home/andre/.arduino15/packages/esp8266/hardware/esp8266/2.4.0/tools/sdk/lwip2/include/arch/cc.h:89:5: note: in expansion of macro 'ip4_addr3_16'      ip4_addr3_16(ipaddr), \      ^ /home/andre/arduino-1.8.3/libraries/easyMesh-master/src/easyMeshSTA.cpp:201:23: note: in expansion of macro 'IP2STR'                        IP2STR(_stationConn.proto.tcp->remote_ip),                        ^ /home/andre/.arduino15/packages/esp8266/hardware/esp8266/2.4.0/tools/sdk/lwip2/include/lwip/ip4_addr.h:202:54: error: request for member 'addr' in '*(uint8*)(&((easyMesh*)this)->easyMesh::_stationConn.espconn::proto.espconn::<anonymous union>::tcp->_esp_tcp::remote_ip)', which is of non-class type 'uint8 {aka unsigned char}'  #define ip4_addr4(ipaddr) (((const u8_t*)(&(ipaddr)->addr))[3])                                                       ^ /home/andre/.arduino15/packages/esp8266/hardware/esp8266/2.4.0/tools/sdk/lwip2/include/lwip/ip4_addr.h:208:38: note: in expansion of macro 'ip4_addr4'  #define ip4_addr4_16(ipaddr) ((u16_t)ip4_addr4(ipaddr))                                       ^ /home/andre/.arduino15/packages/esp8266/hardware/esp8266/2.4.0/tools/sdk/lwip2/include/arch/cc.h:90:5: note: in expansion of macro 'ip4_addr4_16'      ip4_addr4_16(ipaddr)      ^ /home/andre/arduino-1.8.3/libraries/easyMesh-master/src/easyMeshSTA.cpp:201:23: note: in expansion of macro 'IP2STR'                        IP2STR(_stationConn.proto.tcp->remote_ip),                        ^
Thanks

Hello
me too, what's the solution?

@mjoelmendes As far as I know easymesh has been abandoned (see the git activity). I am maintaining a fork though: https://gitlab.com/painlessMesh/painlessMesh which should compile fine (and if not, feel free to submit a bug report :))

Having the same issue. Thank you, @BlackEdder , will try your library now.


term parentage modification

I think that GO:0047334
(diphosphate-fructose-6-phosphate 1-phosphotransferase
activity) which is currently a child of GO:0016301
(kinase activity), might be better placed under
GO:0008443 (phosphofructokinase activity).
Thanks for looking into it.
Chris
Reported by: c_tissier
Original Ticket: "geneontology/ontology-requests/3199":https://sourceforge.net/p/geneontology/ontology-requests/3199

thanks www.movied.org


InvalidOperationException: Unable to resolve service for type 'Microsoft.AspNetCore.Http.IHttpContextAccessor' while attempting to activate 'OpenCqrs.Dependencies.Resolver'

WebAPI project, core 2.1.1.

I'll have a look as soon as I can, thanks.

I'm using 2.1.1 and it does work properly.
What's your setup like?

This is a know bug (#27) but it should happen only on console apps.

:) I got this issue during xUnit integration tests creation first. To get integration things work right I have injected all in test constructor:
    public SomeTestConstructor()
    {
        IConfiguration configuration = new ConfigurationBuilder()
            .AddJsonFile("appsettings.json", false, true)
            .Build();

        var service = new ServiceCollection();

        service
            .AddOpenCqrs(typeof(TestCommand))
            .AddSqlServerProvider(configuration)
            .AddServiceBusProvider(configuration);

        _serviceProvider = service.BuildServiceProvider();

        var builder = new AppStub(_serviceProvider);
        builder
            .UseOpenCqrs()
            .EnsureDomainDbCreated();

        _testItemId = Guid.NewGuid();
    }

When I got the error i have tried to inject the IHttpContextAccessor by injecting it to service:
services.AddHttpContextAccessor();
The issue was not resolved. So I have cloned the repository, and used service locator for resolver:
public class HandlerResolver : IHandlerResolver
{
    private readonly IServiceProvider _serviceProvider;

    public HandlerResolver(IServiceProvider serviceProvider)
    {
        _serviceProvider = serviceProvider;
    }

    public THandler ResolveHandler<THandler>()
    {
        var handler = _serviceProvider.GetService<THandler>();

        if (handler == null)
            throw new HandlerNotFoundException(typeof(THandler));

        return handler;
    }
}

Also I have removed Resolver class and interface, changing references to IServiceProvider directly.
Maybe this was not the best solution, but this was the hot fix to make things work. Hopefully MS will do solve lazy object resolving issue sometimes. :)

Emm... I just forgot to clarify, that was really surprised, when found the error in Web API response. This was the main reason WHY I used service locator pattern for IoC container.
Startup file of API:
public class Startup
{
    public Startup(IConfiguration configuration)
    {
        Configuration = configuration;
    }

    public IConfiguration Configuration { get; }

    // This method gets called by the runtime. Use this method to add services to the container.
    public void ConfigureServices(IServiceCollection services)
    {
        services.AddAutoMapper();
        services.AddMvc().SetCompatibilityVersion(CompatibilityVersion.Version_2_1);

        // In production, the Angular files will be served from this directory
        services.AddSpaStaticFiles(configuration =>
        {
            configuration.RootPath = "ClientApp/dist";
        });

        services.AddAuthentication(JwtBearerDefaults.AuthenticationScheme)
            .AddJwtBearer(o =>
            {
                o.Authority = Configuration["Authentication:AADInstance"]
                              + Configuration["Authentication:TenantId"];
                o.Audience = Configuration["Authentication:ClientId"];
                o.TokenValidationParameters = new TokenValidationParameters
                {
                    RoleClaimType = ClaimTypes.Role,
                    ValidateIssuer = true
                };
            });

        services.AddDbContext<EfCoreContext>(options =>
            options.UseSqlServer(
                Configuration.GetConnectionString("SqlConnection"),
                db => db.MigrationsAssembly("SomeProject.Web")
                )
            );

        services.Configure<AADOptions>(Configuration.GetSection("Authentication"));

        services.AddTransient<AADUserSyncService>();
        services.AddTransient<GraphApiUserService>();

        services.AddOpenCqrs(typeof(CreateFeedbackCommand))
            .AddSqlServerProvider(Configuration)
            .AddServiceBusProvider(Configuration);
    }

    // This method gets called by the runtime. Use this method to configure the HTTP request pipeline.
    public void Configure(IApplicationBuilder app, IHostingEnvironment env)
    {
        if (env.IsDevelopment())
        {
            app.UseDeveloperExceptionPage();
        }
        else
        {
            app.UseExceptionHandler("/Error");
            app.UseHsts();
        }

        app.UseHttpsRedirection();
        app.UseStaticFiles();
        app.UseSpaStaticFiles();

        app.UseAuthentication();

        app.UseMvc(routes =>
        {
            routes.MapRoute(
                name: "default",
                template: "{controller}/{action=Index}/{id?}");
        });

        app.UseSpa(spa =>
        {
            // To learn more about options for serving an Angular SPA from ASP.NET Core,
            // see https://go.microsoft.com/fwlink/?linkid=864501

            spa.Options.SourcePath = "ClientApp";

            if (env.IsDevelopment())
            {
                spa.UseAngularCliServer(npmScript: "start");
            }
        });

        app.UseOpenCqrs().EnsureDomainDbCreated();
    }
}

Thanks @asokalskyy I'll fix this issue in the next release.

Fixed in Version 5.3


TOC id generation conflict

Current Behavior
At https://github.com/skeletonlabs/skeleton/blob/2f3eaf8015d3b44f8f5d01fb6d89677aa0b11253/packages/skeleton/src/lib/utilities/TableOfContents/crawler.ts#L42
It might be good to append a '-toc' or other random string to ensure that it doesn't conflict with any other element  id's that are the same as the textContent.  You can see this conflict on https://www.skeleton.dev/elements/chat when clicking on Prompt on the TOC.  I also query the logic of assigning an empty string for the id as a fallback as that would break navigation in situations where they might have an icon or other nested structure that doesn't resolve to text coming out ?
Expected Behavior
No response
Steps To Reproduce
No response
Link to Reproduction / Stackblitz
No response
More Information
No response

Good call!

Resolved per https://github.com/skeletonlabs/skeleton/pull/1915


snapdragon flight maintenance issues

This is a rough list of the things that have made maintaining this platform more difficult than it needs to be.

parameter system duplicated in place (99% identical)

Action: merge src/lib/parameters/parameters.cpp and src/lib/parameters/parameters_shmem.cpp

DriverFramework sensor drivers

Action: "port" in tree PX4 drivers and drop DriverFramework
(https://github.com/PX4/Firmware/pull/12783)
Action: unify all sensor handling with regular PX4 (calibration parameters, ifdef mess in calibration routines, etc)

init is a mess

PX4 init for nuttx, linux, qurt is all different - https://github.com/PX4/Firmware/tree/master/posix-configs/eagle
PX4 linux has no standard install location, packaging, or system init (start via /etc/rc.local if at
all)
Action: create linux package with px4 binary, config pieces, DSP binary (libpx4.so), etc

development environment issues

not clear what is and isn't' available on qurt and problems aren't caught until runtime
difficult to get set up
various ATLFlight/cmake_hexagon issues and unnecessary non-standard cmake magic

circular dependencies between parameters, muorb, shmem, etc

extern symbols with no proper include paths, linking dependencies
untangling this mess would help a lot

build system

there's an eagle build on jenkins (with old private container), but the binaries it produces don't seem to actually work on hardware
no excelsior build at all

no automated testing

Action: add eagle hardware testing to Jenkins (WIP)
Action: add excelsior hardware testing to Jenkins

I'll add a couple of points:

Maintenance of docs and dependencies abandoned:

No answers here: https://github.com/ATLFlight/cross_toolchain/issues
Neither here: https://github.com/ATLFlight/dspal/issues

No tooling/instrumentation about Qurt/DSP side:

We don't know free stack, RAM, CPU load!
We don't get crash stack traces, it just reboots.

Compiler for Qurt is based on Clang 3.5.0 and prevents us from going from C++11 to C++14 or C++17.


RO-3972 Update master dependencies

This change is the result of running gating/update_dependencies/*
See update_dependencies in https://rpc-openstack.atlassian.net/wiki/spaces/RE/pages/19005457/RE+for+Projects for more details.

This should unblock the pip install failures we're hitting.


Clobber log output file by default

The standard Unix utility behavior is to clobber files specified as write output.
When mongocli downloads logs, it refuses to run if the destination file exists:
./bin/mongocli atlas logs download atlas-51fpbe-shard-00-01.zjgzi.mongodb.net mongodb.gz --projectId 5f49cd4b6d8c874ca774824f --out -
Error: open -: file exists

As a user of a unix-like operating system, I expected mongocli to clobber the output file, especially one that it created by itself without direction from me (#460, I expected default destination to be standard output).
If no-clobber behavior is desired, it should be provided as an option, and in that case mongocli should ask the user whether to clobber the file if the input device is a terminal and not immediately give up. See, for example, cp -i behavior:
serene% cp -i bin/mongocli -
cp: overwrite '-'?

My personal opinion on clobbering by default is that it's risky and a usability issue, with that said we are willing to add the inverse of cp -i and it's to instruct the download to clobber with an extra flag, adding this will also enable you to do something like
mongocli atlas logs download atlas-51fpbe-shard-00-01.zjgzi.mongodb.net mongodb.gz --out /dev/stdout which should address #460

I understand how someone not familiar with unix command line may be surprised by output files being clobbered but this is the behavior of the vast majority of unix programs. Log files are generally unconditionally appended to by default.

and a usability issue

In my opinion the usability issue is that mongocli refuses to work unless the user deletes files that mongocli created.

Like I mentioned in this case will add the ability to over write the destination file but it won't be default, also for clarification and also why this command works the way it does is that you won't be able to get a plain text file, it'll be a gzip file you'll need to unzip, this is currently and atlas limitation

I am aware that the atlas api provides gzipped logs but this doesn't mean a commond-line tool must only provide gzipped logs.


Handle MultimapKeysSideInput in State GetRequests

This PR closes #31628 adding handling for MultimapKeysSideInput in State GetRequests. Since this surfaced in Java validation tests of org.apache.beam.sdk.transforms.ViewTest, validated on Prism via:
TEST=org.apache.beam.sdk.transforms.ViewTest
./gradlew :runners:portability:java:ulrLoopbackValidatesRunnerTests -PjobEndpoint=localhost:8073 --tests="$TEST"

This PR fixes the following ViewTest tests:

testMapAsEntrySetSideInput
testWindowedMultimapAsEntrySetSideInput
testWindowedMapAsEntrySetSideInput
testMultimapAsEntrySetSideInput

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

R: @lostluck


KAFKA-8585; Controller should change leader and isr optimistically

Since it has the cached leader and ISR state, the controller can optimistically assume it has the latest state when performing an update and save a little latency. If the state was changed by the leader, it can do the lookup and retry.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Just an update on this PR. Basically I am going to put this optimization on hold for a little while. The challenge I have been running into is the fact that we depend on the cached LeaderAndIsr value not only to get the latest zkVersion, but to decide whether a state change is even needed. So in the case of a controlled shutdown, for example, if we have not seen the latest ISR expansions, then we may fail to shrink all needed ISRs. There has always been a window for this, but it was relatively small because we always did a fresh query before doing the ISR shrinks. Now the window is significantly larger since leaders delay (by 1 minute!) sending leader and ISR change notifications to the controller. This makes the risk of this change causing a delayed ISR shrink during controlled shutdown potentially higher than any performance benefit we get from it.
Separately, we are considering introducing an AlterIsr API so that the controller is the only one that can change leader and ISR state. Once we have that, this optimization will make more sense because we will be able to assume that the controller's cache is accurate. I will revisit this patch if and when we have that.


Change repo's 'crystal-language' topic to 'crystal'

The Crystal community has somewhat decided to use crystal as the language's topic.
To avoid fragmentation in the community, please change the crystal-language topic, that only has ~28 repositories at the moment, to crystal.
Any contributor can change it from the repo's homepage.
See crystal-lang/crystal#4241 for more context.
Thank you very much :)

Done :+1:


numba for pytorch Tensor for multiple gpus

Reporting a bug

[yes] I have tried using the latest released version of Numba (most recent is
visible in the change log (https://github.com/numba/numba/blob/main/CHANGE_LOG).
[yes] I have included a self contained code sample to reproduce the problem.
i.e. it's possible to run as 'python bug.py'.

I want to use numba for pytorch Tensors. I have two gpus. The following code works Okay for device-0 but not for device-1.
When I run the following code, I get an error similar to issue #4092
from numba import cuda
import torch

@cuda.jit
def addone(out):
    idx = cuda.grid(1)
    out[idx] = out[idx] + 1

a = torch.zeros(10).cuda(1)
addone[1, 10](cuda.as_cuda_array(a.data))
print(a)

The error is:
numba.cuda.cudadrv.driver.CudaAPIError: [1] Call to cuPointerGetAttribute results in CUDA_ERROR_INVALID_VALUE

I am using numba=0.53.1. I can solve the error by "cuda.select_device(1)", however I assume this is not the ideal way.

@xuxy09, to help us diagnosis the problem, can you paste the output from running numba -s from the terminal?


Google search fails for plus codes

Test case

Generate a valid plus code
Search in Google search

Expected outcome
Search result shows location. This specification is advertised at https://plus.codes/developers:

Thanks to the plus symbol in each code, they are easy to identify (in Google search, for example). The plus symbol also allows to correctly interpret partial plus codes. [Emphasis added]

Actual outcome
Search result does not show location.

Discussion
Here is a plus code for a place:

4WCH+97 Huntingdon Valley, Bryn Athyn, PA

I tried searching for that on Google using various formats. My computer is close to this location, no VPN. Here are the results:

✅ 4WCH+97 Huntingdon Valley, Bryn Athyn, PA
✅ 4WCH+97
❌ 4WCH+

I was expecting 4WCH+ to present a map on Google.com search results but it did not:

Using https://plus.codes I can confirm that this is a valid code. It will NOT work if you paste it into the search box at https://plus.codes but it WILL work if you use https://plus.codes/87G64WCH+ then zoom into somewhere near me and then search.
This confirms that it is a valid plus code.

Google searches only support codes of at least 10 digits (that is, two digits after the +). You can do a search for a shorter code in Google Earth, but it must be a global code ("8FVC4WCH+") not an address ("4WCH+ Zurich, CH" does not work).
Currently our focus is on supporting searches at an address level, not at this larger level. If you can explain your use case we can use that to prioritise additional support.

Thank you. Now that I understand the position, I believe the discrepancy can be resolved by editing
https://plus.codes/developers
to state:

Thanks to the plus symbol in each code, they are easy to identify. The plus symbol also allows to correctly interpret partial plus codes. Google search supports some plus codes.

If https://plus.codes/developers is on GitHub then I can send a PR.

Source for the website is not on GitHub but I'll look into the change in our next refresh.

Thanks for looking into this.


SOLR-15972 Add wrapper jar and export-ignore attr

Tested via: git archive --format tgz HEAD | tar -zt | grep wrapper
https://issues.apache.org/jira/browse/SOLR-15972

I'm not sure why you want to have the wrapper versioned - for me it's one way or the other. Since you can't publish it in source releases and the infrastructure to automatically download it is in place - why add things to make it more complicated?

I'm just trying to make my internal, non internet accessible CI work. Like I said on the Jira, I have a maven mirror but not a GitHub mirror. I suppose the other option is that I install gradle from somewhere and use that instead of the wrapper?

I'm +0. My view is very polarized - either remove the gradle wrapper download infrastructure or use it for what it was added. Occam's razor.

I ended up being able to install the full gradle version and use that for CI instead of trying to hack around the wrapper being missing.


Plain text format for Ghost emails

At the moment Ghost doesn't send a plain-text formatted email for some of its email notifications like Password Resets, Members Sign Ups/Ins and others.
To give email readers a fallback options (and a better preview!) it would be good to add a plain text version of these emails.

Not sure this is correct, or at least by my understanding of what it means to include a fallback. Waiting for more info.

Damn, you're totally right. Sorry for the noise. I must've completely misread the source email I tested off AND missed the setting on the tool I was using 😭
Closing issue.


Add DNS multi

Credit to original PR #2402

Testet this with simply dns, works just fine. Hope to see it the build soon

Would love to get this merged as its a pretty small change


Rearanged main clustered lighting loop to avoid unrolling and improve compile time

in the original call where lighting was called manually 4 times, the compilation time on my MacBookPro per simple shader using clustered lighting was around 180ms.
with changed code, with just a single call to lighting, the compilation time dropped to around 70ms.

And no change in runtime perf?


storage_write_api: choosing stream type for batch load jobs

Some thoughts on picking the best stream type for batch ingestion :

According to GCP documentation, pending type is the recommanded choice for batch ingestion. It provides atomic operations and can be seen as an alternative to BQ load jobs, which we use when choosing gcs_stage mode.
I understand from the same documentation and from the explanation given in this project's README.md that the commited type is offers an optimal read latency for streaming use cases.

My feeling is that the pending type would be the best choice when setting options.storage_write_batch_mode to true.

My bad, just saw that pending type is already in use : https://github.com/z3z1ma/target-bigquery/blob/main/target_bigquery/storage_write.py#L62.
I believe that the README should be corrected on this though. I can create a quick PR if that's ok with you @z3z1ma :slightly_smiling_face:

Sure sounds good! Yes that's a mistranslation on my end. It should say that storage write batch mode uses pending streams as you'd expect. 😅

Dedicated PR #17


add chinese README

Pull Request Test Coverage Report for Build 14

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 12:
0.0%

Covered Lines:
52

Relevant Lines:
52

💛  - Coveralls


drivers/pipes: using rmutex to protect pipe and avoid deadlock

Summary
drivers/pipes: using rmutex to protect pipe and avoid deadlock
The backtrace when bug occurs:(signal break current stack, and write pipe in signal handler)
nxsem_wait
nuttx/sched/semaphore/sem_wait.c:176
nxmutex_lock
nuttx/libs/libc/misc/lib_mutex.c:204 (discriminator 2) pipecommon_write
nuttx/drivers/pipes/pipe_common.c:538 (discriminator 2) file_write
nuttx/fs/vfs/fs_write.c:91
write
nuttx/include/unistd.h:523 (discriminator 2)
nxsig_deliver
nuttx/sched/signal/sig_deliver.c:170 (discriminator 4) arm_sigdeliver
nuttx/arch/arm/src/armv7-a/arm_sigdeliver.c:107
irq_waitlock
nuttx/sched/irq/irq_csection.c:204
nxsem_post
nuttx/sched/semaphore/sem_post.c:86 (discriminator 2) nxmutex_unlock
nuttx/libs/libc/misc/lib_mutex.c:339 (discriminator 2) pipecommon_poll
nuttx/drivers/pipes/pipe_common.c:769
file_poll
nuttx/fs/vfs/fs_poll.c:321
poll_fdsetup
nuttx/fs/vfs/fs_poll.c:194
poll
nuttx/include/sys/poll.h:164
uv_run
apps/system/libuv/libuv/src/unix/core.c:449
adb_hal_run
apps/system/adb/microADB/hal/hal_uv.c:76
adbd_main
apps/system/adb/adb_main.c:157
nxtask_startup
nuttx/libs/libc/sched/task_startup.c:70 (discriminator 2) nxtask_start
nuttx/sched/task/task_start.c:134

Impact
using rmutex protect pipe
Testing
Vela

[Experimental Bot, please feedback here]
NuttX PR Requirements Review
While the provided summary gives a high-level idea of the PR, it needs more detail to meet the NuttX requirements.
Here's a breakdown of what needs improvement:
Summary:

Why is the change necessary?: You mention a deadlock scenario with a backtrace. Clearly explain the root cause of this deadlock.  Why is using a rmutex the appropriate solution? Are there alternative solutions considered?
What functional part of the code is being changed?:  Be specific about which files and functions within drivers/pipes are modified.
How does the change work?  Detail the mechanism of using rmutex for protection. How does this prevent the deadlock described?  Avoid vague terms like "protect."

Impact:

You only address the impact on the user with "using rmutex protect pipe".  This statement is too vague. Elaborate on the user-facing changes (if any).
Address all other impact categories (build, hardware, documentation, security, compatibility).  State "NO" if no impact exists, but provide justification for each.

Testing:

Insufficient detail: "Vela" doesn't provide enough context. Specify:

Build host operating system, CPU architecture, and compiler version.
Target architecture and board configuration.

Missing logs:  Include relevant before and after logs demonstrating:

The deadlock occurring before the change.
Successful operation after the change, proving the fix.

Concisely:
No, this PR does not currently meet the NuttX requirements. The information provided needs to be more comprehensive and detailed.

@Donny9 please fix the commit log message. It should include a brief explanation why this modification is necessary / recommended

@acassis hello，Indeed, the backtrace can elucidate the rationale behind introducing this specific case. The reason lies in our internal usage of adb, where a scenario arises in which a task is actively monitoring a pipe. Concurrently, another task sends a signal to this monitoring task, and within the signal handler, there's an attempt to write to the same pipe. Without incorporating a recursive lock mechanism, this scenario can lead to a deadlock.
By implementing a recursive lock, we allow the same thread to safely re-acquire the lock multiple times, including within signal handlers, without causing a deadlock. This ensures that the signal handler can execute its intended operations, such as writing to the pipe, without disrupting the ongoing monitoring activities or violating the locking protocol.

@Donny9 please fix the commit log message. It should include a brief explanation why this modification is necessary / recommended

@acassis hello，Indeed, the backtrace can elucidate the rationale behind introducing this specific case. The reason lies in our internal usage of adb, where a scenario arises in which a task is actively monitoring a pipe. Concurrently, another task sends a signal to this monitoring task, and within the signal handler, there's an attempt to write to the same pipe. Without incorporating a recursive lock mechanism, this scenario can lead to a deadlock.
By implementing a recursive lock, we allow the same thread to safely re-acquire the lock multiple times, including within signal handlers, without causing a deadlock. This ensures that the signal handler can execute its intended operations, such as writing to the pipe, without disrupting the ongoing monitoring activities or violating the locking protocol.

Understood, thank you! That was the explanation I was willing in the commit message :-)


EctoEnum macro should implement embed_as/1 and equal?/2

After updating Ecto to 3.2.0, I get the following warnings for each use of EctoEnum:
warning: function embed_as/1 required by behaviour Ecto.Type is not implemented (in module Module.Enum)
  lib/namespace/module.ex:9: Module.Enum (module)

warning: function equal?/2 required by behaviour Ecto.Type is not implemented (in module Module.Enum)
  lib/namespace/module.ex:9: Module.Enum (module)

I guess to prevent this warnings from showing up changing the macro would be sufficient.

Any update on this? I see that there already is a PR.


test_string_poly() in test_nonlinear.py is flaky

In 7/100 runs, I'm getting an unexpected optimal objective value, namely 1.69200831463043. The expected objective value is 1.692489081738 (which happened in 93/100 runs). I've only observed this when not compiled in debug mode.
One way to fix this is to increase the tolerance of the test, but I just wanted to check that (a) you can reproduce this, and (b) this is expected.

I think this occurs because the constraints can be generated differently. For example, in two runs of the example, I get
created nonlinear constraint   [nonlinear] <voldef>: ( +1.5707963267949 * <ncoils> * <coildiam> * <wirediam> * <wirediam> +3.14159265358979 * <coildiam> * <wirediam> * <wirediam> -1 * <volume>) == 0;

and
created nonlinear constraint   [nonlinear] <voldef>: ( +1.5707963267949 * <coildiam> * <wirediam> * <wirediam> * <ncoils> +3.14159265358979 * <coildiam> * <wirediam> * <wirediam> -1 * <volume>) == 0;

Now if the order of the variables is different, then presolving might work differently (for example, if you have x*y*z SCIP might decide to make this into a quadratic as w = x * y and w*z. if you have y*z*x then one might obtain w = y*z and w*x).
In this particular case, presolving is indeed working differently and this explains the different results.
The reason why the variables are sorted different, I suspect, is because we are using the pointer of the variables to create a dictionary in python and then making a list out of it. In _addNonlinearCons you find
        variables = {var.ptr():var for term in terms for var in term}
        variables = list(variables.values())

I guess we could use something more deterministic than the ptr of the variables, but still I wouldn't know if the conversion from dict to list is always sorted in the same way.
So yeah, the solution right now would be to increase the tolerance if this is failing.

I briefly looked into replacing variables = list(variables.values()) by variables = sorted(variables.values(), key=lambda var: var.name), but no success. I'll change the tolerance to 1.0e-3 in our code base. Would you mind doing the same in this Github repo (I would send you a pull request myself, but as I'm about to go on holiday, I'm a bit short on time).

sure


FIND MY ARTIST

FIND MY ARTIST
User Story
AS A music lover with a busy schedule
I WANT to see the top tracks and info about any artist
SO THAT I can keep informed.
Acceptance Criteria
GIVEN the music dashboard
WHEN a user searches for an artist
THEN they are presented with information about the artist
AND the artist’s top tracks
AND the artist is added to the search history.

GIVEN the music dashboard
WHEN a user searches for an artist
THEN they are presented with information about the artist
AND the artist’s top tracks
AND the artist is added to the search history.


ExpoLocalization error

Hi,
After upgrading posthog ^1.1.5 to "^2.1.1" this version i am facing this issue:
Error: Cannot find native module 'ExpoLocalization'
Even i try to install npm i expo-localization, but still same error
My react and react-native version
"react": "17.0.2",
"react-native": "0.68.0",

I am also having the same issue

Update: installing expo modules solved the problem! Just run npx install-expo-modules@latest
Reference: https://docs.expo.dev/bare/installing-expo-modules/#automatic-installation

In order to use Expo modules in your app, you will need to install and configure the expo package.

Hi,
After upgrading posthog ^1.1.5 to "^2.1.1" this version i am facing this issue: Error: Cannot find native module 'ExpoLocalization'
Even i try to install npm i expo-localization, but still same error
My react and react-native version "react": "17.0.2", "react-native": "0.68.0",

Update: installing expo modules solved the problem! Just run npx install-expo-modules@latest
Reference: https://docs.expo.dev/bare/installing-expo-modules/#automatic-installation
In order to use Expo modules in your app, you will need to install and configure the expo package.

For people, like me, who have no option/don't want to to implement expo in any fashion - I looked at the source code and talked to community support who told me that vanilla ReactNative is not supported.
However, there is some light.

This issue exists that hopefully soon will support vanilla.
After some tinkering I successfully mocked all expo modules with the libraries mentioned in the issue above. This is possible since the only thing expo provides are some constants.   I did this my using a babel alias plugin which replaces the libraries: expo-application, expo-device, expo-localization and expo-file-system.

Hey there 👋 as of v2.2.0 expo modules are no longer required. Check out the docs to see the installation instructions for non-expo projects.
NOTE: The initialisation of PostHog has slightly changed so be sure to check that out. (The old way still works but may have some race condition issues).


Use Google's InstanceID API

https://developers.google.com/instance-id/guides/android-implementation

:+1:

if could
well..that will really awesome!!!

To add some perspective -- this is not an awesome feature but a requirement by Google:
According to this, the gcm.register is deprecated since May 2015:
GCM register() is deprecated starting May 28, 2015. New app development should use the Instance ID API to handle the creation, rotation, and updating of registration tokens.
While there do not seem to be direct implications (it still works), it would be prudent to plan for migration for the day will come when GCM stops accepting new register() calls.

@miraculixx Agreed, that's why I'm working on it. :smiley_cat:

@macdonst glad to hear :+1: thanks

Anyone who wants to test it can check out branch issue188. It seems to be working just fine but I need to do more testing.

Fix committed will be official in 1.4.0 release.

Thanks @macdonst ! :+1:
Can you please also update the README.md file to reflect the changes on how to use it. :smiley:

+1

@bhaveshgohel I already did under Android compilation. No changes to JS code are necessary.

Ohh... Thanks @macdonst! :smiley:

It added the "Find accounts on the device" Contact permission. What is that permission used for, if it's used?

@jayj Hmm...that is Google Play Services adding that. Lemme see if I can make that smaller.

@jayj I just merged a PR from contributor @smdvdsn that should remove the need for the "Find accounts on device" permission.

@macdonst  I've looked everywhere but I cannot find how to get hold of an InstanceID using this plugin... Can you shed some light on it?


Wallet.preferredEndpoints overriding ChainProvider.endpointOptions

This still defaults to https://rpc-juno.itastakers.com/:
<ChainProvider
  chains={chains}
  endpointOptions={{
    [chainName]: {
      rpc: ["https://rpc-juno.pupmos.network:443"],
      rest: ["https://api-juno.pupmos.network:443"],
    }
  }}
  assetLists={assets}
  wallets={[...keplrWallets, ...cosmostationWallets, ...leapWallets]}
  signerOptions={signerOptions}
>

Only by mutating wallet endpoints does it switch to pupmos.network nodes:
<ChainProvider
  /* ... */
  wallets={[...keplrWallets, ...cosmostationWallets, ...leapWallets].map(wallet => {
    if (wallet.preferredEndpoints?.[chainName]) {
      wallet.preferredEndpoints[chainName].rpc = ['https://rpc-juno.pupmos.network:443'];
      wallet.preferredEndpoints[chainName].rest = ['https://rpc-juno.pupmos.network:443'];
    }
    return wallet;
  })}
  /* ... */
>

Got it! will be solved in next version, thank you!


Use realistic timer for Gauge.set_to_current_time

set_to_current_time is expected to set the value to a realistic time.
Performance counters are monotonic but don't say anything about the actual
time.

My reading of the docs is that this is wall time.

What exactly? You docs say that it sets to current unix time which I thought to be epoch time.  However:
>>> from timeit import default_timer
>>> from time import time
>>> from datetime import datetime
>>> datetime.fromtimestamp(default_timer())
datetime.datetime(1970, 1, 5, 19, 25, 4, 943824)

>>> datetime.fromtimestamp(time())
datetime.datetime(2016, 10, 17, 19, 50, 9, 261461)

This seems rather useless to me and a pretty bad regression IMHO (got a lot of time()-metric > X alerts :)).

Oh i think I understand now; you’ve been referring to legacy (2.7) docs.  default_timer is time.perf_counter() as of Python 3.3: https://docs.python.org/3.5/library/timeit.html#timeit.default_timer

Thanks!

It would be really cool if you could push a quick new release, since this is a nasty regression on Python 3.3+ and will probably also confuse new users.


add step to deploy.yml workflow to use correct version of node

adding step in Deploy workflow, prior to the 'Build and Install' step, so set the correct version of node (v12.13.1) to use for npm operations

Hi @dominikwilkowski ,
Do you mean this step. The step that I added in deploy.yml already exists in merge-checks.yml.
Sorry if I've misunderstood your question :bow:


Database with flow support

I am currently just messing around with different technologies and was wondering if there is some good database with flow type support?
I am currently using sqlite and it's not very fun to work with types in there.

MongoDB seems to have very nice support. What about SQL databases?


EIP-7594: Specify inclusion proof function to run.

For by root and by range requests checks, the exact function to run is specified for KZG commitments, but not for the inclusion proof.
This PR aligns both checks.

Additional question: Should the SHOULD be replaced by a MUST?
Consequences could be quite dramatic if a client actually considers a block with data column sidecars with invalid inclusion proof and/or invalid KZG proofs.

Additional question: Should the SHOULD be replaced by a MUST?

Precedent says no. For example, the equivalent check for BlobSidecarsByRoot:
https://github.com/ethereum/consensus-specs/blob/57483cb0075f1eaa413b77d1833b393513f70981/specs/deneb/p2p-interface.md?plain=1#L294

Thank you for the remark and change @jtraglia!


Cleanup in EThread.

Remove useless stuff, convert to declaration initialization,
For #1997.

[approve ci autest]


Can not run the code of Visualize the SMPL Mesh

I'm trying to run the code of visualize the smpl mesh but it failed and here is the error.
Would you please tell me why it doesn't work? Thanks.

This visualization only works with local machines. It will pop up a window to show. It does not support running on the remote server without GUI.


How to get all invitations so I can access the list of data for a conference

I tried client.get_all_invitations() but nothing was being outputted after 5-10 minutes.
I want to explore data beyond ICLR 2019 from the README front page.
import openreview

client = openreview.Client(baseurl='https://api.openreview.net', username='<your username>', password='<your password>')
notes = openreview.tools.iterget_notes(client, invitation='ICLR.cc/2019/Conference/-/Blind_Submission')
for note in notes:
    print(note.content['title'])

Is conference venue invitations documented somewhere for easy accessibility?

I would suggest querying the submissions by venue id:
client.get_all_notes(content={ 'venueid': 'ICLR.cc/2022/Conference'})

this will return all the accepted papers.
cc @racheljsmart to follow up with the user.

Is there a way to get the list of possible venue ids? There seems to be quite a bit of discrepancies in terms of capitalization etc.

There is a group called venues where we store all the venues that hosted so far. There is another group called active_venues that contains the venues that are active (currently under review).

Brilliant! For anyone finding this post looking for code, the way to get them is
client.get_group("venues").members
not
openreview.tools.get_all_venues(client)

Another caveat for future people, venueid is not always populated
for example
client.get_all_notes(content={"venueid": "ICLR.cc/2019/Conference"})
returns an empty list

venueid is not always populated

what does one do in those cases?


Out of memory 99

To cover issue #99.
From now on compute_neighborhoods is a generator to be memory efficient. This means the user gets an iterator instead of a result. The user needs to call next(compute_neighborhoods) to iterate over the results.

Coverage decreased (-61.0%) to 24.079% when pulling 2dfacb44b8e6aaca6001a8c7ac8536405757221a on out_of_memory_99 into f5d82cc658e34fcd085cda904988708082480f54 on development.

I have checked the issues with prospector and solved them.


feat(templates): improve welcome screen luminance effect

Make the logo aware of the luminance effect as well:
Before:
https://user-images.githubusercontent.com/11247099/179776050-3a52dde4-09e8-4769-aac0-2e2f939d2f53.mp4
After:
https://user-images.githubusercontent.com/11247099/179775519-389585c7-49b2-425b-9333-8e5afb82d33f.mp4

In light mode, the "3" is not very readable when the teal background, I would suggest changing it to black, or at least making it darker in light mode. However, the SVG is merged with the mountain so I can't change it separately. Might need help from who has the source file of the logo.
To improve the "physics" even further, I would suggest we move the loading bar to the top or bottom of the screen, otherwise it's a bit less natural that the bar does not light up the logo.

/cc @Flosciante @Atinux

Thank you @antfu
The main issue I have is the color contrast here:

Happy for you to try with the navbar at the top, also something I wanted to explore: https://codepen.io/Chokcoco/pen/dypaobm
Happy for you to give an update?

@Atinux Yes I am aware of it but I can't modify it as the "3" is blended with the mountain. Need some help here:

In light mode, the "3" is not very readable when the teal background, I would suggest changing it to black, or at least making it darker in light mode. However, the SVG is merged with the mountain so I can't change it separately. Might need help from who has the source file of the logo.

I wanted to explore: codepen.io/Chokcoco/pen/dypaobm

Do you mean by replacing the loading bar to be like the demo? It looks great and sure I can give it a spin

I have tried two styles, in two commits:
Conic fa1ddce3a1f0918a1e692df0244bcc2c84d4d650
(from https://codepen.io/Chokcoco/pen/dypaobm)
https://user-images.githubusercontent.com/11247099/182845140-8e0a3049-08d8-46d2-aa00-35fb63b5ba16.mp4
Blurred Progress d2f84f14ab9c45e560d1e8ebbeb427b5b745a3f5
https://user-images.githubusercontent.com/11247099/182845201-c2a8eae8-7c69-4a5c-8dc1-17379716390d.mp4
What do you think?

Sorry for the delay of my answer.
I love the Blurred Progress @antfu (damn I wish to have answer before the RC8).

Do I need to make a manual release @pi0 ?

Released as patch<EMAIL_ADDRESS>


Does anyone have a working AWS NLB configuration with ambassador?

Hi,
My apologies for asking this question in issues. Don't know where else to put it.
I am trying to setup a kubernetes cluster in AWS EKS that uses a NLB loadbalancer with ambassador edge stack/emissary ingress. However after hours of troubleshooting and trying I didn't get it to work.
Following this guide: https://www.getambassador.io/docs/edge-stack/1.14/topics/install/yaml-install/ Ambassador edge stack v1.14 installs just fine without any errors and creates all the necessary pods and resources. It also creates an ELB loadbalancer automatically (this one does nothing I think?).
After following this: https://www.getambassador.io/docs/edge-stack/1.14/topics/running/ambassador-with-aws/ it sets it up a NLB in AWS.
Everything seemed fine so far. However, after deploying a test application and pasting the public dns name of the NLB in a browser, the browser just keeps loading. And in the logs of ambassador we see 'http 200 (OK)', but no response in the browser. Seems like traffic gets in, but no traffic gets out? We don't have any firewalls, acl of security groups enabled that block any traffic.  This test application worked fine when deployed on a prototype cluster in Virtualbox with MetalLB.
Could anyone share his/her config files for installing/configuring ambassador with NLB like the one below?
Important to note --> The config file in the guide should be changed to http and https? HTTP and HTTPS results in an error (capital letters not allowed).
apiVersion: v1
kind: Service
metadata:
  name: ambassador
  namespace: ambassador
  annotations:
    service.beta.kubernetes.io/aws-load-balancer-type: "nlb"
    service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled: "true"
spec:
  type: LoadBalancer
  ports:
  - name: HTTP --> http
    port: 80
    targetPort: 8080
  - name: HTTPS --> https
    port: 443
    targetPort: 8443
  selector:
    service: ambassador

Used software:
Kubernetes 1.21 (in EKS)
Ambassador edge stack 1.14
Test application used to test connection:
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx-test
  labels:
    app: nginx-test
spec:
  replicas: 1
  revisionHistoryLimit: 2
  selector:
    matchLabels:
      app: nginx-test
  template:
    metadata:
      labels:
        app: nginx-test
    spec:
      containers:
      - name: nginx-test
        image: nginx:alpine
        imagePullPolicy: Always
        ports:
        - containerPort: 80
---
apiVersion: v1
kind: Service
metadata:
  name: nginx-test
spec:
  selector:
    app: nginx-test
  ports:
    - protocol: TCP
      port: 80
---
apiVersion: getambassador.io/v2
kind: Mapping
metadata:
  name: nginx-test
spec:
  prefix: /
  rewrite: /
  service: nginx-test:80

The problem is not in the AWS LB, red this https://github.com/emissary-ingress/emissary/issues/3894#issue-1034656091
Appear that ambassador guys dont read the issues in this repo. The issue persist at this moment, the worst is that exist only 1 images for emissary 2.X

I've been fooling around trying to get this product work in our new Argo cluster for the better part of a day. They really need to go through their docs on AWS, its a mess and its a mismatch of instructions that have you creating multiple services that conflict etc and its about as clear as mud. Close to just moving to another product. EKS AWS should be smooth as butter install for a product like this.

I concur, this is terrible. I can't get ambassador + AWS NLB to work and we already tried an ALB configuration before also without success.

did someone found a solution for this issue ? i was able to register ONLY one Host with Lets Encrypt, the following ones are have a problem and can't be reached for ACME to verify the request.....they are also not reachable through HTTP.
Deleting the first register, and creating some of the following ones its working fine, but only for a single host....
Any idea ?

My solution ultimately was to switch back to NGINX Ingress and configure it myself.

#4153 might be related.
I was able to get NLB working with the following setup
apiVersion: getambassador.io/v3alpha1
kind: Listener
metadata:
  labels:
    app.kubernetes.io/name: emissary
    app.kubernetes.io/instance: server
  name: https
  namespace: emissary
spec:
  hostBinding:
    namespace:
      from: SELF
  l7Depth: 1
  port: 8443
  # documentation says to use protocol over protocolStack but there is a current bug with that approach
  # https://github.com/emissary-ingress/emissary/issues/4153
  #protocol: HTTPSPROXY
  protocolStack: [ "PROXY", "TLS", "HTTP", "TCP" ]
  securityModel: XFP

---

apiVersion: getambassador.io/v3alpha1
kind: Host
metadata:
  labels:
    app.kubernetes.io/name: emissary
    app.kubernetes.io/instance: server
  name: all
  namespace: emissary
spec:
  hostname: "*"
  tlsSecret:
    name: ambassador-certs
  tls:
    min_tls_version: v1.2
  mappingSelector:
    matchLabels:
      # associate all mappings that contain this label
      app.kubernetes.io/component: api

---

apiVersion: v1
kind: Service
metadata:
  annotations:
    service.beta.kubernetes.io/aws-load-balancer-type: external
    service.beta.kubernetes.io/aws-load-balancer-scheme: internet-facing
    service.beta.kubernetes.io/aws-load-balancer-nlb-target-type: ip
    service.beta.kubernetes.io/aws-load-balancer-backend-protocol: tcp
      #service.beta.kubernetes.io/aws-load-balancer-proxy-protocol: "*"
    service.beta.kubernetes.io/aws-load-balancer-attributes: "load_balancing.cross_zone.enabled=true"
  labels:
    app.kubernetes.io/component: ambassador-service
    app.kubernetes.io/instance: emissary-ingress
    app.kubernetes.io/managed-by: getambassador.io
    app.kubernetes.io/name: emissary-ingress
    app.kubernetes.io/part-of: emissary-ingress
    product: aes
  name: emissary-ingress
  namespace: emissary
spec:
  ports:
  - name: http
    port: 80
    targetPort: 8080
  - name: https
    port: 443
    targetPort: 8443
  selector:
    app.kubernetes.io/instance: emissary-ingress
    app.kubernetes.io/name: emissary-ingress
    profile: main
  type: LoadBalancer

The key for me is that the pre-canned protocol HTTPSPROXY didn't set the protocolStack correctly. So I had to over-ride what the default was.

I'm just trying to get NLB (Layer 4) with HTTP (no TLS) to work, and I'm gettin 400's.

module

  config:
    diagnostics:
      allow_non_local: true
      enabled: false
    use_proxy_proto: true

svc - attributes (I’m running the last aws-load-balancer-controller, so these annotations don’t necessarily match the ambassador docs, but they are correct, as I’ve verified at the NLB)

    service.beta.kubernetes.io/aws-load-balancer-attributes: access_logs.s3.bucket=,access_logs.s3.enabled=false,access_logs.s3.prefix=,deletion_protection.enabled=false,load_balancing.cross_zone.enabled=true
    service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled: "true"
    service.beta.kubernetes.io/aws-load-balancer-nlb-target-type: ip
    service.beta.kubernetes.io/aws-load-balancer-proxy-protocol: '*'
    service.beta.kubernetes.io/aws-load-balancer-scheme: internal
    service.beta.kubernetes.io/aws-load-balancer-type: external

listener

spec:
  hostBinding:
    namespace:
      from: SELF
  port: 8080
  protocol: HTTP
  securityModel: INSECURE

host

spec:
  acmeProvider:
    authority: none
  hostname: '*'
  requestPolicy:
    insecure:
      action: Route
  selector:
    matchLabels:
      a8r.io/hostname: wildcard
      a8r.io/requestPolicy: route-insecure
  tlsSecret: {}

also verified the NLB has 3 healthy targets, and Proxy protocol v2: On
NLB Listener is listening on port 80, Target Group is set to forward to 8080 (the listening address of the pods, not the service)

Port forwarding to the service works, which definitely points to some issue between the NLB and the Ambassador Edge Pods
k port-forward svc/ambassador-edge-default 8080:80
Forwarding from <IP_ADDRESS>:8080 -> 8080
Forwarding from [::1]:8080 -> 8080
Handling connection for 8080

http localhost:8080
HTTP/1.1 200 OK
...

<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>

I can confirm that the protocol stack is the problem. Removing protocol and setting protocolStack: [ "PROXY", "HTTP", "TCP" ] Fixes the issue for me.


Support leader election in controller

Our controller should support leader election for clusters where there are multiple copies of the controller run.

@directXman12, this one has your name all over it, hoss

I have some questions here, because I'm concerned with the amount of complexity that leader election will add (even though the code is already written), both in comprehending the codebase and more importantly, debugging user submitted issues:

Do you have a use case for multiple controllers in a single cluster?
What will the replicas do?

Very interested in learning the deeper internals here, as well as understanding the upstream design decisions.

moving this into the beta cycle

Do you have a use case for multiple controllers in a single cluster?

Yes.  We deploy all k8s controllers in an active/passive HA mode in OpenShift clusters with HA masters.  We plan to deploy an instance of the service catalog controller in the same way - one controller instance per master, colocated with each master.

What will the replicas do? Wait until they're elected?

Yep.

If we do run multiple controllers, can we use a distributed lease to provide mutual exclusion for side-effecting operations (such as REST calls to brokers)?
Note that I don't necessarily believe this is a better solution than leader election. I do want to understand the overall goal here

This is basically exactly how leader election is implemented.  See #647


Archive snapshots of websites locally

Allows to create HTML snapshots of websites and store them locally in the linkding data folder. This feature is only included in a new variant of the Docker image (latest-plus). I did not include it in the default variant as it consumes more resources: it requires a Chromium installation in the Docker image, more runtime memory to run Chromium, and more disk space to actually store snapshots.
Snapshots are created using single-file-cli. For now, snapshots can only be created on the server, which means websites with paywalls, or requiring login will not work. Future improvements could be to integrate this with the browser extension or allow uploading snapshots manually.
Snapshots are created automatically by default when using the alternative Docker image variant, a setting allows turning that off. Alternatively, snapshots can be created manually from the bookmark details view. Snapshots can be viewed from the bookmark details view as well.

Can you just switch to this image in docker-compose.yml, or does it need to be a fresh install?

You should be able to switch between images without issues. The default image just has the snapshot feature disabled and lacks the dependencies to run it.


chore: remove duplicate arbitrum chain logo entry

What it solves
Remove duplicate entry
Resolves #
How this PR fixes it

I have read the CLA Document and I hereby sign the CLA

I have read the CLA Document and I hereby sign the CLA

Hi @RamanSB , closing this PR as Scroll is not officially supported.


refactor(workflows): Update workflow versions, steps

Update action versions to latest
Limit uses of cd in publish workflow
Use env variables for repeated cURL arguments

thank you! :) i agree we should move it to npm build, good points


feat(fe): add 404 not found page

Description
Closes #221
존재하지 않는 링크로 접속했을 때 표시할 404 not found 페이지를 구현합니다.
나중에 @vueuse/head 등으로 metadata를 추가하면 <meta name="robots" content="noindex" />까지 추가하면 더 좋을 것 같습니다!

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines
[x] Read the Contributing Guidelines and follow the Commit Convention
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

좋아요~~~


log scaling on volcano plot

Counts data can be toggled: for the volcano, assume the example will hold more generally.

log scaling in place... if we have a real-life sample that needs something more flexible, we'll handle it then.


Failure handling

How does BOHB handle failures currently? AFAIK, they are just considered as bad configurations.
It would be nice if specific exceptions (Eg: IO or network connectivity errors ) can be handled with a min number of retries.

@sfalkner I would like to use BOHB for long running training jobs as well, on preemptible instances. I can't imagine that all workers will survive the whole optimization process. It would definitely be important to retry failed configurations at least a couple of times, and the high-budget jobs are especially likely to fail at some point due to longer running times.
Come to think of it, the way to handle this best would probably be to have the Worker save periodic checkpoints to cloud storage, and be able to re-create the Worker if it fails and resume from that checkpoint, until it completes its allotted budget successfully.
Of course, this means that TCP socket connectivity is NOT the way to find out that a Worker is permanently dead - you have to handle the situation where the same job is now resumed by a new Worker instance. So instead of sockets, it should be persistent event queues or DB entries or something.
In effect, I guess this means getting rid of the NameServer as it is now and replacing it with a persistent cloud data structure to represent current state, which can be written and read by Workers and the Master.


Add docstrings to RustSimDriveParams

Fixes: https://github.nrel.gov/MBAP/fastsim/issues/348
The docstrings were added by referencing other parts of the code. Some were slightly adjusted to enhance clarity where possible.
NOTE: this also incorporates a change that seems to have fixed the unit tests not building in Github actions:
The root cause appears to be a breaking change in numpy 1.24 and later that causes an error in another dependency (pymoo?). I limited the max version of numpy to be <1.24 to fix. A more comprehensive fix might involve updating all the deps.

NOTE: I noticed the unit tests don't seem to be passing via Github Actions. I tried an experiment based on this thread to increase the swap space thinking it might have been a memory issue but that didn't work:
https://github.com/actions/runner/issues/2468
Not sure at this point what is wrong with the automated tests although I wonder if it could be the "vehicle import" tooling since that requires network access? Just a wild guess at this point...

OK, not sure if this definitively fixed the unit tests but it appears to be a breaking change in numpy 1.24 and later that causes this. This shows up in one of the dependencies. I limited the max version of numpy to be <1.24 to fix but there's probably a better, more comprehensive fix involving updating all the deps.

Also addresses #9

@jakeholden , @michael-okeefe should get most of the credit for this, FYI


Test with Marshmallow v2 and v3

Configure travis to test with marshmallow versions:

2.15.5
3.0.0b15

Nice!


Potential warning/heads up in advance for 4.3

From leaks of the beta client, 4.3 seems to be adding in a lot of QoL changes to the game so far. Obviously these are all subject to change, so maybe some of these won't make it into the final update.
However, there is one QoL update that's simply been listed by leakers as being a "game resource anomaly prompt", which upon being triggered just forces the game to close. There's no info on how exactly this is triggered, or if it does anything more than described (say flag accounts that trigger this) but the obvious implications are this could certainly affect modding in general. And given how this FPS unlocker works, I see it potentially, if not certainly, triggering this prompt.
At best, assuming the unlocker does trigger this, I see it being an annoyance until the mod is updated to bypass this prompt. At worst, if this does end up flagging accounts, then we could see this being the day we've all dreaded of Hoyo actually banning accounts for using this.
As such, assuming this change does make it into final, then this just serves as a notification to the developer of needing to potentially update the unlocker if possible, as well as a potential caution point to users to maybe not use the mod once 4.3 drops.

4.2 beta had changes that weren't brought into 4.2 live, so I'll assume that's what gonna happen for 4.3
I care less about any leaks


Add legacy projects

Add the projects for a couple of assemblies that are no longer in active development but we still need to ship for the time being.
These changes are mostly about basic cleanup to get the sources added to the repo and integrated with the build. Future changes will get the associated unit tests, if any, up and running, and introduce NuGet packages for these assemblies.

@AndyGerlicher @rainersigwald @cdmihai Could you review, please?

LGTM, but I think @cdmihai might be the best person to get the localized build going.

Thanks for doing this!
LGTM except for the loc part failing CI. Ideally we could turn it off for now? @cdmihai is there an easy way? I don't want to block the package creation on work for loc.

You need to add a bail out mechanism for projects that don't want to be localized. Have their csprojes define a property like '$(DoNotLocalizeMe)` and then update the localization import in here: https://github.com/Microsoft/msbuild/blob/master/src/dir.targets#L12

@cdmihai I've updated the commits to disable localization for these two projects.

Loc changes look good.

Also, please run poli-check before merging :)

@cdmihai Ran Policheck and cleaned up a few things. I'll merge this once the pull request builds complete successfully.