Colorbar does not plot for viz.topoplot

I am trying to visualize a topography with a colorbar, but I cannot for the life of me get the colorbar to show. I am using MNE 0.23.0.
Here is my code:
fig,ax=plt.subplots(1,1,figsize=(6,6),dpi=1200)
clim = dict(kind='value', lims=[4, 8, 12])

im,cm=mne.viz.plot_topomap(dist[0,:],raw_concat.info,contours=5,axes=ax,cmap='viridis',vmin=np.min(dist),vmax=np.max(dist))
ax_x_start = 0.95
ax_x_width = 0.04
ax_y_start = 0.1
ax_y_height = 0.9
cbar_ax = fig.add_axes([ax_x_start, ax_y_start, ax_x_width, ax_y_height])
# clb = plt.colorbar(cm, cax=cbar_ax,ax=ax)
unit_label='MDS distance'
# plt.colorbar(cm)
clb = fig.colorbar(cm, cax=cbar_ax,ax=ax)
clb.ax.set_title(unit_label,fontsize=14) # title on top of colorbar
plt.show()

I have also tried (following matplotlib example):
fig,ax=plt.subplots(1,1,figsize=(6,6),dpi=1200)
clim = dict(kind='value', lims=[4, 8, 12])

im,cm=mne.viz.plot_topomap(dist[0,:],raw_concat.info,contours=5,axes=ax,cmap='viridis',vmin=np.min(dist),vmax=np.max(dist))

divider = make_axes_locatable(ax)
cax = divider.append_axes("right", size="5%", pad=0.05)
plt.colorbar(im,cax=cax,ax=ax)

Your help is very much appreciated!

from pathlib import Path
import numpy as np
import matplotlib.pyplot as plt
import mne

sample_dir = Path(mne.datasets.sample.data_path())
sample_fname = sample_dir / 'MEG' / 'sample' / 'sample_audvis_raw.fif'

raw = mne.io.read_raw_fif(sample_fname)
raw.crop(tmax=60)
raw.pick('eeg')

fig, (ax, cbar_ax) = plt.subplots(1, 2, figsize=(6, 4), gridspec_kw=dict(width_ratios=[6, 1]))
clim = dict(kind="value", lims=[4, 8, 12])

dist = 10e-6 * np.random.randn(1, len(raw.ch_names))

im, cm = mne.viz.plot_topomap(
    dist[0, :],
    raw.info,
    contours=5,
    axes=ax,
    cmap="viridis",
    vmin=np.min(dist),
    vmax=np.max(dist),
)
unit_label = "MDS distance"
clb = fig.colorbar(im, cax=cbar_ax, ax=ax)
clb.ax.set_title(unit_label, fontsize=14)  # title on top of colorbar
plt.show()

this should work.
close the issue if so.

Hi Alexandre, thanks for the help. Your code helped me put the colorbar axes in the same figure, but I am not able to plot the colors themselves on the axes. How can I achieve this?

sorry I don't get what you mean

When I use the code you wrote, this is the product:

I can't get any colors on the colorbar itself. and the colorbar title also does not show

my code gives me this:

thats odd, how can I troubleshoot this issue? Do you think it could be an issue with Spyder? I should say that I am using spyder 4.2.1. I can't seem to download any version higher than that because of dependency conflicts

Do you think it could be an issue with Spyder?

try it in a system console with Python or IPython; if it works there and fails from within Spyder, then it's almost surely an issue with Spyder
Other things to try (in order):

see whether running import matplotlib.pyplot as plt; plt.ion() first fixes it; if so, one of the earlier lines was blocking execution of the later lines, so they weren't taking effect
in the terminal where the plot is failing, run mne.sys_info() and report the results here.

can you try directly from python or a notebook and not from spyder?

@drammock I tried plt.ion and it didn't make a difference.
I also tried updating every package including spyder and matplotlib and the issue still persists.
@agramfort I tried running the script in python3 terminal/bash and i still do not get any colors.

in the terminal where the plot is failing, run mne.sys_info() and report the results here.

@drammock I updated my previous comment

I can reproduce your error.  But I can also fix it by adding plt.ion() to @agramfort's code example (after the import statements).  Are you sure you tried including plt.ion() before the figure was created?

@drammock I tried putting plt.ion() right after importing and before the figure was generated. This is the script:
import scipy.io
import os
import numpy as np
# from mapping.barplot_annotate_brackets import barplot_annotate_brackets
import mne
from mne import io
import matplotlib.pyplot as plt
plt.ion()
mat=scipy.io.loadmat('/Volumes/tempdata/Study2/MDS/dist.mat')
dist=mat['dist']
pval=mat['pval']
#  topoplot

pvalpass=pval>0.05
dist[pvalpass]=0
# from mpl_toolkits.axes_grid1 import make_axes_locatable

data_path2='/Volumes/data2/Study2/Raw/P98/S02'
# data_path2='/Volumes/data2/Study1/Raw/P{0:02d}'.format(ps[participant])+'/S02'
for file in os.listdir(data_path2):
    if file.endswith('.vhdr'):
        data_path2=os.path.join(data_path2,file)
    # for file in os.listdir(data_path2):
    #     if file.endswith('.vhdr'):
    #         data_path2=os.path.join(data_path2,file)

raw_concat=io.read_raw_brainvision(vhdr_fname=data_path2,preload=True)
# actual topoplot

# dist = 10e-6 * np.random.randn(1, len(raw.ch_names))
fig, (ax, cbar_ax) = plt.subplots(1, 2, figsize=(6, 4), gridspec_kw=dict(width_ratios=[6, 1]))
clim = dict(kind="value", lims=[4, 8, 12])
plt.ion()
im, cm = mne.viz.plot_topomap(
    dist[0, :],
    raw_concat.info,
    contours=5,
    axes=ax,
    cmap="viridis",
    vmin=np.min(dist),
    vmax=np.max(dist),
)
unit_label = "MDS distance"
# plt.colorbar()
clb = fig.colorbar(cm, cax=cbar_ax, ax=ax)
clb.ax.set_title(unit_label, fontsize=14)  # title on top of colorbar
plt.show(block=True)

This is the figure I keep getting:

It's difficult to debug when your script references paths and data objects that I can't access.  Here is @agramfort's script again, with plt.ion() added in the latest possible place (just to emphasize where it needs to go).  Can you please test this script instead of the one using your own data, and tell us if it works?
from pathlib import Path
import numpy as np
import matplotlib.pyplot as plt
import mne

sample_dir = Path(mne.datasets.sample.data_path())
sample_fname = sample_dir / 'MEG' / 'sample' / 'sample_audvis_raw.fif'

raw = mne.io.read_raw_fif(sample_fname)
raw.crop(tmax=60)
raw.pick('eeg')
plt.ion()  # <<<<<< this needs to happen **before** you create the figure!!
fig, (ax, cbar_ax) = plt.subplots(1, 2, figsize=(6, 4), gridspec_kw=dict(width_ratios=[6, 1]))
clim = dict(kind="value", lims=[4, 8, 12])

dist = 10e-6 * np.random.randn(1, len(raw.ch_names))

im, cm = mne.viz.plot_topomap(
    dist[0, :],
    raw.info,
    contours=5,
    axes=ax,
    cmap="viridis",
    vmin=np.min(dist),
    vmax=np.max(dist),
)
unit_label = "MDS distance"
clb = fig.colorbar(im, cax=cbar_ax, ax=ax)
clb.ax.set_title(unit_label, fontsize=14)  # title on top of colorbar
plt.show()

I am still getting the same result, with plt.ion placed before plt.subplots

I tried fig.colorbar (im, cax=cbar_ax,ax=ax) in bash and it seems to have worked (used cm previously). Not sure why it is not working on spyder, however.
Thanks @agramfort @drammock

FYI, I just had a chance to test in spyder.  If you add show=False to the plot_topomap call, then it works with the inline backend too.


Fix markdown headers in README.md

Markdown requires a space between the hashes and the header.
For example;

##ABC doesn't work
## ABC works

oh man, good catch. Thank you!


tt_py_untilize_with_halo.py:148 -- remove the assertion (shouldn't be there)

This assertion should not be there.
Shapes which were Failing  due to this assertion

@shwetankTT what is the status of each of these shapes' tests after removing the extraneous assertion?

These tests are passing now.


kind --help command wont show --config option

Bug description
Expected behavior
Steps to reproduce the bug
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
How was Istio installed?
Environment where bug was observed (cloud vendor, OS, etc)

raised issue in this repo by mistake


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-yml-archive-non-versioning-archive/pull/516 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-yml-archive-non-versioning-archive.git

Docs Build status updates of commit 015148b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-3.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-3.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


[SPARK-50059][CONNECT][PYTHON] API compatibility check for Structured Streaming I/O

What changes were proposed in this pull request?
This PR proposes to add API compatibility check for Spark SQL Structured Streaming I/O functions
Why are the changes needed?
To guarantee of the same behavior between Spark Classic and Spark Connect
Does this PR introduce any user-facing change?

No
How was this patch tested?

Added UTs
Was this patch authored or co-authored using generative AI tooling?

No

Merged to master.


Switch names resetting to 'Button 1'

I have a number of IKEA TRADFRI button switches, which I am connecting to HomeKit via a Conbee II and homebridge-deconz running on an RPi 4. The buttons expose into HomeKit but their names continually reset to 'Button 1'. This makes it somewhat difficult to distinguish between them, requiring me to open the Advanced Features in Home+ (which does show the correct name as pulled through from Phoscon). I have tried changing the name in Home+, which sticks for a few minutes before the name resets to 'Button 1'.
I believe this may be a bug, but if I'm missing a setting somewhere, please do let me know!

I think that's a feature of Home+.  I shows the label, like Apple's Home app, instead of the service name.  I do see the changed service name in Eve, even after Home+ has reverted to the label.
As of iOS 16, service names are initialised from the accessory name, instead of the service name, as exposed by the accessory (i.c. the Homebridge plugin).  I see that I don't yet expose Configured Name on the Stateless Programmable Switch service - will add that to the next release.

Thanks for the clarification! I think between this and #88, I need to have a chat with the Home+ developer! Thank you for all your excellent work on homebridge-deconz! It's fantastic and I much prefer the HomeKit-side control we get too!


feat(contentful): Create webhooks programatically

Overview
Completes ticket 216478
Changes
Minor

Adds Javascript/Typescript code/project that creates, or updates, a webhook in Contentful
Adds a shell script that runs the above from Terraform, when certain conditions are met and changed

How to review the PR
Core functionality
Test webhook creation

Follow the instructions in the README.md to set environment variables, build the project and run it

WEBHOOK_URL is what I used to find matching existing webhooks; so please don't use our actual existing webhook URL otherwise you'll overwrite the existing one.

Validate that the webhook has been created in Contentful, with the correct header, filters, URL, and name

Test webhook update

After running the above, change WEBHOOK_NAME, and re-run the script
Validate that the webhook has been renamed
Delete it for the next section

Terraform
Webhook creation

Set contentful_management_token in your Terraform vars
Set contentful_upsert_webhook in your TF vars
Run the TF. I'd recommend targetting just the specific null_resource that runs the Bash script (that runs the JS, that...) by adding  the argument  -target="null_resource.health_check"
Assert that the null_resource is created
Verify that the webhook has been created with the name "Plan Tech Webhook - "

Webhook remains unmodified

Run TF apply
Assert that the null_resource resource remains unchanged, as we have not modified anything

Webhook updates

Add contentful_webhook_name to your TF vars with whatever name you want
Run TF again
Assert that the webhook has been modified and matches new name

Delete the webhook from above
Webhook DOESNT upsert

Set contentful_upsert_webhook to false

Run TF apply - null resource should be recreated; let it be

Verify that the webhook wasn't created

Set contentful_upsert_webhook back to true

Remove contentful_management_token

Run TF Apply - again null_resource should be recreated

Again, verify that the webhook wasn't created though

Checklist
Delete any rows that do not apply to the PR.

[x] Title uses Angular commit convention
[x] PR targets development branch
[x] Terraform has been updated

This seems to be making the webook in contentful twice?

Think I fixed this? Missed a return statement after the update, whoops.


proposal: regexp: add support to !re

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

$ go version
go1.16.4

Does this issue reproduce with the latest release?
There's no issue, this is a request for enhancement
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/fidencio/.cache/go-build"
GOENV="/home/fidencio/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/fidencio/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/fidencio/go"
GOPRIVATE=""
GOPROXY="direct"
GOROOT="/usr/lib/golang"
GOSUMDB="off"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/golang/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.16.4"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build3703314101=/tmp/go-build -gno-record-gcc-switches"

What do you want?
While there are workarounds for the behaviour I think that should be supported (as keeping allow  and deny lists), I'd love to see the support for !re being introduced to the language.
This would allow things to be slightly simpler on the developer side.

What exactly does "!re" refer to?

What exactly does "!re" refer to?

@seankhliao, let me first say I'm taking https://github.com/google/re2/wiki/Syntax as a reference.
What I'm looking for is a way to support something  that does not match a specific re (as in everything else but that).
So, for instance "!(foo)" would match anything else but "foo".
Is this, somehow, more clear?
Again, we could easily work this around with a deny list (instead of an allow list).

Package regexp implements re2, any new language features would have to be accepted by re2 before it can be implemented here. google/re2#156 has indicated that it will not be supported.
Closing as there's nothing to do

@seankhliao, makes sense!
Thanks a whole lot for finding the pointer to the re2 issue, very much appreciated, and, at least, we have this archived for the next person who requests something similar.


Idea for a strategy to find the repo from the remote list

Idea for a strategy to find the repo from the remote list:

List all remotes
Filter by keeping only the ones targeting github.com
Hit the first one on the github API (https://api.github.com/repos/{the_repo})
See if it has a "parent" attribute:

it it has one, the good one is the parent, and we have the github URL. no longer need to care about knowing its local name.
if it has none, lucky you it's the right one

Demo of finding it indirectly:
$ curl https://api.github.com/repos/seluj78/python-docs-fr | jq .parent.url
"https://api.github.com/repos/python/python-docs-fr"

Or demo of lucky "it was the right one so it has no parent":
$ curl https://api.github.com/repos/python/python-docs-fr | jq .parent.url
null

Originally posted by @JulienPalard in https://github.com/Seluj78/Potodo/issues/37#issuecomment-565355937

@JulienPalard I'll propose a PR in this idea.

@awecx still waiting 😉

still WIP :sweat_smile:

@awecx ping

If you don't have time to work on it, hit me up and I'll do it 😉


[SPARK-19795][SPARKR] add column functions to_json, from_json

What changes were proposed in this pull request?
Add column functions: to_json, from_json, and tests covering error cases.
How was this patch tested?
unit tests, manual

Test build #73751 has started for PR 17134 at commit b67b9e4.

Test build #73751 has finished for PR 17134 at commit b67b9e4.

This patch fails SparkR 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/73751/
Test FAILed.

Test build #73782 has started for PR 17134 at commit f3258c7.

Test build #73782 has finished for PR 17134 at commit f3258c7.

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/73782/
Test PASSed.

Test build #73918 has started for PR 17134 at commit 3748d9b.

Test build #73918 has finished for PR 17134 at commit 3748d9b.

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/73918/
Test PASSed.

merged to master


Manage Trusted Domains: https://* no longer works

VSCode Version: 1.52.0-insider (050a123750e4ef4009930d0da1ff7a1a6441d4f3)
OS Version: Windows_NT x64 10.0.19042

Steps to Reproduce:

add https://* as a Trusted Domain
open a link such as https://twitter.com

Does this issue occur when all extensions are disabled?: Yes

I verified this works with the latest insiders release (version 1.52.0-insider (ee46c1f89ebb213e0827886f1688c0fbb55be49f))

/verified


Logout user when access token expires

Describe the bug
User should be logged out on token expiration instead of showing authorization error.
Would you like to work on the issue?

[x] Yes
[ ] No

No, just refresh the token.

@liveHarshit Shouldn't this also be implemented? So that if it happens that the token does not get refreshed due to some reason, then the user gets logged out.

So that if it happens that the token does not get refreshed due to some reason, then the user gets logged out.

yes, if okhttp authenticator will give invalid access token after implementing refresh token, then the user should logout.

This is already implemented.
https://github.com/fossasia/open-event-organizer-android/blob/27753c7dc33e2c8ef317d749f50706b9ac15d7d7/app/src/main/java/com/eventyay/organizer/data/auth/AuthHolder.java#L66-L70

Then debug why 401 errors were being shown to the user


[AutoPR containerregistry/resource-manager] chore: jsonfmt containerregistry

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

This PR has been merged into https://github.com/Azure/azure-sdk-for-java/pull/3165


declared(params) not play well with rails strong parameters

It seems like that this PR #797 which make declared(params) return Hashie::Mash instead of native Hash causing issue with Rails strong parameter, as it causes attributes.respond_to?(:permitted?) && !attributes.permitted? alway return false, unless when the hash has key 'permitted'.
     def sanitize_for_mass_assignment(attributes)
        if attributes.respond_to?(:permitted?) && !attributes.permitted?
          raise ActiveModel::ForbiddenAttributesError
        else
          attributes
        end
      end

Could we revert it back to normal Hash to make it play well with Rails?
Thanks, Anh Nguyen.

@anhhnguyen206 see hashie_rails


Update package.json - require node 18

Adapter is tested against node 18 / 20 only.
Node 14 and node 16 are outdated since onths and no longer maintained.
Hance adapter should require node 18 as minimum.
Please merge PR / adapter engines clause for next release. An urgent extra release is not required as repository build talkes repository head revision anyway.

@mcm1957
Is there any way to run the adapter checker (e.g. inside tetst-and-commit.yml) every time I open a PR to my master branch to avoid things like this? The problem is,  that these issues don't pop up until you open a PR to the stable repo - which is too late.

This is an open issue - you are right.
First:
If you use iobroker.dev a version of the adapter checker is running. But this version is slightly outdated.
I am currently working at the adapter checker to update checks and release new versions from tzie to time. Currently there are app 60 open issues - so it will take soe time. I've set up the checker at repository PRs to always use the latest version of the chcker. Sad to say, the webbased iobroker.dev needs several task done to use the newest chcker - and those tasks cannot be done by me (no rights and missing knowedge. Updating the webbased chcker need access to iobroker webservers - so this can be done by bluefox only.
What you can do is startung the latest chcker manually:
npx @iobroker/repochecker https://github.com/ioBroker/ioBroker.javascript

see https://github.com/ioBroker/ioBroker.repochecker#how-to-test-via-cli
I plan to reactivate a sort of recurrent scan of all repositories. But I cannot give an estimate when this will be done.
You suggestion to add it to standard tests looks like a good idea - I will evaluate how a workflow could be created to check and create a useable feedback. This check should be run independent of standard checks as the repochecker too often reports errors which must be ignored and the repochecker should not technical block creating a release. But I will evaluate if / how this can be implemented so that the checker results reach dev earlier - at least if they are interesed.
And THANKS for fast response / merging.


Expose tautomer scoring functions to python

This exposes the pieces of the tautomer scoring function to make it easier to adjust from python and other languages.
Example
      terms = rdMolStandardize.SubstructTermVector()
      terms.append(rdMolStandardize.SubstructTerm("C=0", "[#6]=,:[#8]", 1000))

      rdMolStandardize.ScoreSubstructs(m, terms) # now == 1000

I think all the comments are up to date except the thread-safety issue.  Because the scoring function is buried pretty deeply, this is going to be a bit hard to solve.
Currently it isn't a problem and it existed before so maybe we punt for now?
Ideally we would make substructure matching itself thread safe, but I've always been scared by that.

I should say it would be hard to solve unless we copy-construct the queries every time.   One solution would be to make the function a functor i.e.
structure TautomerScorerBase {
   virtual ~TautomerScorerBase() {}
   virtual int score(const ROMol &m) = 0;
}

And have the default implementation be thread safe on construction
class ScoreTautomers : public TautomerScorerBase {
   std::vector<ScoreSubstructs> terms = getDefaultSubstructScores();
   int score(const ROMol &m) {
         return scoreHeteroHs(m) + scoreRings(m) + scoreSubstructs(m, terms);
   }
};

TautomerEnumerator te;
te.setScoringFunction(ScoreTautomers());

But this is an API change.


Release and debug mode different for NNBD-migrated code

The following code prints an exception in release/profile mode, but works as expected in debug mode:
import 'package:flutter/material.dart';

void main() => runApp(new MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'hello',
      home: Scaffold(
        floatingActionButton: FloatingActionButton(
          child: Text('123'),
          onPressed: () {
            try {
              print(BoxBorder.lerp(null, null, 0));
            } catch (e) {
              print(e);
            }
          },
        ),
      ),
    );
  }
}

The behavior stays the same when the implementation of BoxBorder.lerp is reduced to the following (have to update call-sides to new signatures):
  static BoxBorder? lerp(BoxBorder? a) {
    if (a is Border?) {
      print('a is Border?');
      return null;
    }
    if (a is Border) {
      print('a is Border');
      return const BorderDirectional();
    }
    print('throw');
    throw 'Help!';
  }

The code will print throw in release mode, and a is Border? in debug mode. The latter is the expected behavior. Modifying the function in the following ways makes the exception go away, but I cannot explain why that is, because it shouldn't matter:

replacing return const BorderDirectional() with return null
removing the second if
duplicating the same function in the same class under a new name lerp2 and calling this function also makes the exception go away (why?? it's the same code in the same scope).
copying the function as is into another class and calling it on that other class makes the exception go away
turning the function into a toplevel function and calling that function makes the problem go away.

It is completely unclear to my why the function changes it behavior when the modification described above are performed. I also don't know how to debug this further since extracting the function makes the problem go away....
For the record, the behavior in release mode should be the same as it is in debug mode.
Prior to migrating the file that contains BoxBorder.lerp to NNBD in https://github.com/flutter/flutter/commit/e8c942104bb4b414b67e303a54b00e8fc45c67a6 everything worked as expected.

@leafpetersen Any idea what is going on here or how to debug this further? It's a mystery to me right now...

This is a bug in Dart AOT compiler (in implementation of is tests).
Small repro:
abstract class A {}
class B extends A {}
class C extends A {}

void foo(A? x) {
  if (x is C?) {
    print('$x is C?');
    return;
  }
  print('$x is not C?');
}

void main() {
  B();
  C();
  foo(B());
  foo(null);
}

Correct behavior in JIT:
$ out/ReleaseX64/dart --enable-experiment=non-nullable foo.dart
Instance of 'B' is not C?
null is C?

Incorrect behavior in AOT:
$ pkg/vm/tool/precompiler2 --enable-experiment=non-nullable foo.dart foo.snapshot
$ pkg/vm/tool/dart_precompiled_runtime2 foo.snapshot
Instance of 'B' is not C?
null is not C?

Fix: https://dart-review.googlesource.com/c/sdk/+/158800

@alexmarkov Thanks for looking into and fixing it!

The fix landed in Dart SDK repo. Do we need to cherry-pick it to the next release?
@a-siva @pcsosinski

The fix was rolled into Flutter in a51dc3d913344f3073da12f4aae654c3299dec6c.

@goderbauer is this something we need to fix on beta/stable in your opinion?

@pcsosinski The bug in Dart was exposed in Flutter by PR https://github.com/flutter/flutter/pull/62951, so if that PR made it into any bata or stable releases we should definitely cherry-pick this fix. Even if that PR didn't make it into any releases, I'd be in favor of cherry-picking this fix since it can easily cause other nasty bugs, which are going to be hard to discover since they only manifest in release (production!) mode. I'd say we should cherry-pick.

This bug can appear in AOT mode when doing is test with nullable type (x is Foo?) in migrated code. While user code is unlikely to trigger this bug, we have a bunch of migrated code in Dart SDK, Flutter and various packages.

thanks
@goderbauer e8c942104bb4b414b67e303a54b00e8fc45c67a6 went in 8/11, 2 days after our 1.21 branch point and well after 1.20, so we'r good there
@alexmarkov I don't think we're expecting folks to run migrated code on the beta release yet, are we?

@pcsosinski Only the code we migrated so far (Dart SDK/core libraries, a few packages, part of Flutter). Don't know if we have is tests with nullable types in that code (we certainly do after e8c942104bb4b414b67e303a54b00e8fc45c67a6).

I just did a quick search: the only is check with nullable types we have in the flutter/flutter code base was introduced in https://github.com/flutter/flutter/commit/e8c942104bb4b414b67e303a54b00e8fc45c67a6.


update dependencies

Is it complaining when installing or something?
Can you delete node_modules after making this change, npm install, then run the tests to make sure this doesn't mysteriously break anything?
Thanks! :smile:

Hey I don't think we need to update this unless you want to use some new functionality. I'll close this PR but feel free to reopen it.


Watch config maps and redeploy: Number of consumers per adapter should be re-configurable & expired TLS certificates must be rotated

The controller should watch for the config-redis ConfigMap and re-configure the receive adapter with the new number of consumers, when modified.
The controller should also watch for the config-tls ConfigMap and re-create the Redis connection when a new TLS certificate is added since certs do expire and need rotation. (https://github.com/knative-sandbox/eventing-redis/blob/8dae13bfc4e1d5b107c83d6d2de0a7718936cbe4/source/pkg/reconciler/streamsource/controller.go#L91-L99)
Relevant PRs: https://github.com/knative-sandbox/eventing-redis/pull/10
https://github.com/knative-sandbox/eventing-redis/pull/47
cc: @lionelvillard @beemarie

/assign

/reopen


chore: speed up kind.sh up a little

by installing all the operators in parallel and then wait their Readiness before installing Apex.

@chirino commits needs signoffs, so can you please signoff the commit.

lgtm, as well (once Signed-off-by gets added)


Distributed Flowgraph Execution

OK, still working on this, and I am expecting to give it a try without using a Redis queue. I'm keeping the text below, but it needs a rewrite.

This will generalize the zqd service (#1208) to execute parallelizable queries using multiple K8s pods.
The zqd process will work as it does now, receiving queries from Brim as a JSON AST of Procs.
There will be an env var that configures zqd to support distributed Flowgraph execution, if this is set, then
in driver.Compile, when Procs are detected that can have parallel execution, zqd will take the Proc that can be executed in parallel, and the sources of data for those process (e.g. S3 objects), serialize them, and add this to a work queue that we will maintain on Redis.
There will be a pool of "zq workers" that pull work items from the Redis queue, and send the completed work back to the zqd instance that requested it. (Right now I'm not sure whether the completed work will written directly back to to the zqd instance, or whether it will be buffered through a Redis data structure like a stream.)
One subtask will be to create a zqd queue command that starts a zq worker, which will be similar to zqd listen, except that it will have no Rest API, and will obtain work from a Redis work queue.
Another subtask will be to modify zqd to add work to the Redis queue.
[Eventually, after the basic stuff works, we can make the zqw processes smart about what they will pull off the queue. For example, they could selectively pull queued work items that require access to S3 objects that they already have in local cache. The point is that scheduling work will be a distributed task where the workers can attempt to optimize their throughput based on their context. ]
There is a google doc that discusses some future options for zq workers. It is very rough now, and does not mention Redis, but it will eventually be "pounded" into a roadmap for more advanced distributed Flowgraph execution.
https://docs.google.com/document/d/1ugCkJMTXPKe1UCTRxU4MKeodbrFySVeQpP2QBgCuctA/edit#

After a discussion with Henri, I've refined some of the idea about how to implement this.
Henri pointed out that Procs are receiver driven, so having a Proc pull fits more naturally into the existing pattern. He suggested I could implement a new type of Proc that pulls results that the zq workers have completed. To make this convenient, the first approach I will try is to have the zq workers pull their work items from a queue in Redis, and then have them write their results back to a Redis stream. Then, on the receiver side, a Proc in the zqd instance that initiated to work will pull the data from the Redis stream.
On the driver side, Henri suggested that the code is driver that set up the Procs could also enqueue the work to be done in parallel to the Redis queue.
So, (1) I need a new Proc type to Pull results from a Redis stream (this Proc would be added into the FlowGraph, for example, right before a "Merge" Proc,
(2) that Proc is created in the Driver around the same time the Driver code enqueue the work item runs. (We do not need to involve Procs in the queuing of work.)

👍

(2) that Proc is created in the Driver around the same time the Driver code enqueue the work item runs. (We do not need to involve Procs in the queuing of work.)

I think the way to do this would be in two steps, similarly to how we parallelize an flowgraph for local execution:
0. A new AST node and proc implementation are created for the "redis reader" proc

An AST transform adds parallel branches with "redis reader" procs (invoked similarly to driver.parallelizeFlowgraph()).
driver.Compile() gets compiles that transformed AST which will result in the redis reader procs starting to read from redis as soon as their Pull() method is called.

This is still a work in progress -- the comments above reflect how the ideas are evolving. I'll add more later.

This design has changed enough for me to use a new epic. Closing.


Reuse fileRegistry in recursive bundling

Quite a significant performance bottleneck for bigger projects using same imports is not reusing fileRegistry in recursive bundling.
https://github.com/SimplrJS/scss-bundle/blob/master/src/bundler.ts#L111
fileRegistry should be given to the inner bundle call.

Done: https://github.com/SimplrJS/scss-bundle/commit/20edbb4e77f66441750efa17f585bbe1c02e840c


HIP draft - Rewards Distribution Change

Ed: rendered view - https://github.com/helium/HIP/blob/ac9a22163e66b5a94287a93783fa9df45632710e/0061-Rewards-Distribution-Change.md

hey @Wazzy95  would you like to present the HIP draft on the community call tomorrow at 12pm-1:30pm ET (5pm-6:30pm UTC)? Here's the call details: bit.ly/38HQ9Mm

hey @Wazzy95  would you like to present the HIP draft on the community call tomorrow at 12pm-1:30pm ET (5pm-6:30pm UTC)? Here's the call details: bit.ly/38HQ9Mm

Hi @edakturk14 unfortunately I can't do tomorrow, thanks for the invite.

hi, @jamiew here. I'm renaming this to Increase Challenger Rewards to help delineate from other reward change proposals. @Wazzy95 please let me know if you'd prefer something else (but also specific)

This HIP draft has been numbered and merged for discussion as HIP 61.
Please direct future questions & comments to the new tracking issue: #421
If you are one of the named authors, please include #421 in future pull requests to have them automatically merged.


Enable NSIS logging in the build.

This will generate an install.log file in the target directory when installing.

Looks like this nsis package is not available in Conda Forge:
Channels:
 - conda-forge
Platform: win-64
Collecting package metadata (repodata.json): ...working... done
Solving environment: ...working... failed

PackagesNotFoundError: The following packages are not available from current channels:

  - nsis=[build=*log]

Current channels:

  - https://conda.anaconda.org/conda-forge

To search for alternate channels that may provide the conda package you're
looking for, navigate to

    https://anaconda.org/

and use the search bar at the top of the page.

Pacackage also not found in defaults:
Channels:
 - conda-forge
 - defaults
Platform: win-64
Collecting package metadata (repodata.json): ...working... done
Solving environment: ...working... failed

PackagesNotFoundError: The following packages are not available from current channels:

  - pkgs/main::nsis=[build=*log]

Current channels:

  - https://conda.anaconda.org/conda-forge
  - defaults

To search for alternate channels that may provide the conda package you're
looking for, navigate to

    https://anaconda.org/

and use the search bar at the top of the page.


Setting ROM region as cacheable in MRAC - Cause RISC-V to throw an exception on FPGA

On FPGA, setting ROM region as cacheable in MRAC causes RISC-V to throw "invalid operation" exception.
When the exception is triggered, the MEPC register points to the PC location where the the MRAC register is set.
While, the issue doesn`t present on Verilator, an investigation should be performed to rule out an actual RTL cause.

We are likely running into FPGA specific issues.
When the illegal instruction exception is fired mtval gets stored with the instruction.
mtval: 0xa0b79073
Supposed to be: 0x7c009073
A slightly different ROM binary with identical setup code running on the same FPGA image does not reproduce this illegal instruction exception.

This was resolved by fixing the FPGA frequency.


Summary report type

Hi!
It would be great if you could choose the summary report type. For example --jpeg, --html or --pdf.
snikt.R --notrim --jpeg AB.fq.gz
or
snikt.R --notrim --jpeg AB.jpeg AB.fq.gz
Best wishes,
Marsel

Hi Marsel,
Thank you for using our tool and suggesting improvements!
Due to current priorities, I can only invest time for critical bug fixes. But I will keep this in mind to implement whenever I get a chance. Until then, may I suggest an alternative - you can use the -k or --keep option to retain intermediate files. SNIKT makes these graphs as images and then knits the report as HTML along with numerical stats. At the end of execution, it simply deletes those (intermediate) images. With choosing to retain, you will get results at least as JPEG images.
Hope this helps.
Best,
Piyush


v0.8.0 release

This is the PR of the release redesign release. This should not require a proper review anymore, since the release is already done, and just not have been merged into main.
After merging, we can add a tag and GitHub release notes. We can discuss them in the comments here, but I think they can be very minimal, since we basically changed everything :D Maybe we could cherry-pick some new features?
Just for reference

the storybook runner is failing because of a bug, that will be fixed in the next release
the "Node.js CI / check_updates" action will be deleted

I still needed to do some commits (mostly cherry-picking from development) to pass all the tests:

playwright tests were broken at the time of the release, so I cherry-picked the fix that I actually did later
I found and fixed this issue. I misinterpreted the dimension of this and thought that it was responsible for a failing test. So it was not mandatory to fix this.
also I picked this fix from yesterday, because suddenly the other tests failed as well


Document data format for upload API

Followup to https://github.com/pypa/warehouse/issues/2666#issuecomment-351438657 . As @di said,

Metadata is specified at https://packaging.python.org/specifications/core-metadata/ but the conversion between this and "what fields PyPI accepts" is not documented. Perhaps we need more information here: https://warehouse.readthedocs.io/api-reference/legacy/#upload-api

Working on it :+1:

Thanks! This'll especially be helpful in light of Dustin's work on PEP 566.

@alanbato We talked a little in IRC and now I'm not sure whether you have a WIP to share?
I'm sorry that you're stuck on this -- last week @di was working on another project, but this week he returns to concentrating on Warehouse. Do you think you could join us at one of our livechats to talk about it synchronously with him?

I'm not sure if all the fields defined in the Core Metadata spec and inside forklift relevant. Like the dependency and file information (digests), for example.

The dependency information is definitely relevant (when it is able to be provided). The digests are optional (Warehouse can and will compute them itself) but when provided, it will verify that they match.

Also, regarding dependecy information, in the form there are "legacy dependency information" and "newer dependency information" fields, which ones should appear in these docs?
Since we're talking about Legacy API Docs I'm assuming the former, but I'm not sure.

Let's just document the newer ones for now, these are the fields clients should be using.

@brainwane Here's the PR #3520 (WIP). I still need to continue working on the info now that @di has cleared some things for me. And I've already added tomorrow's livechat to my calendar so I don't forget. :+1:

https://github.com/pypa/warehouse/issues/9085 pointed out that for "multiple use" classifier fields, the metadata field is singular (Classifier) while the form-field is plural (classifiers), a distinction that this documentation should make.

One of the things that's come up in https://github.com/pypa/twine/issues/743: how should incoming names be normalised?

It would be nice to standardize the error output of the servers too. Currently each index implementation serves different error codes / messages for very common snafus: lack of privileges during upload, overwrites, authentication failures, data validation errors, etc.
It's impossible to implement common checks for these in the tooling, and many of the error messages presented are confusing otherwise (e.g. Artifactory's laconic "403 Forbidden" when someone forgets to update the version in their setup.py).

I'd say specifications on the errors return by the index server would belong in a PEP.

There is now PEP 694: Upload 2.0 API for Python Package Repositories, which has discussions on discuss.python.org which is relevant to this issue.


Application launcher demo

Once #168 has been completed, we can build a demo for the application launcher as seen ehre: http://www.patternfly.org/pattern-library/application-framework/launcher/#/design

Supporting Wireframe from OpenShift:

Added an example in react on how to implement this with the drop down.  See PR 1127 in @patternfly/react-core .
https://github.com/patternfly/patternfly-react/pull/1127
https://1127-pr-patternfly-react-patternfly.surge.sh/patternfly-4/components/dropdown

After discussion with team we are going to add a React PF4 component for the app launcher.
This is currently being tracked by the following issue:
https://github.com/patternfly/patternfly-react/issues/1130


Withdraw problem

Hi
I also have problem with withdraw my btc form exchange , Could you help me?

My username is: pawel_ko

@pawelkop our hot wallet was empty.


Fix class name for ASEM (ER) specialist

See https://github.com/computational-cell-analytics/micro-sam/blob/dev/finetuning/specialists/training/electron_microscopy/organelles/asem_finetuning.py#L18C1-L36C22 for details
Hint: replace the class object name with any custom name

Fixed at https://github.com/computational-cell-analytics/micro-sam/pull/496


Current emoji code doesnt support animated emojis.

Describe the bug

Your config file
No response

(on the topic of emojis, I don't believe Emojiful supports emojis with capitals in? correct me if i'm wrong but i think the emoji would have to be lowercase'd before being sent into the Minecraft chat in order to be picked up by Emojiful.)

Indeed from you screenshot it appear that the animated format has an additional a. As I'm not a nitro membre I wasn't aware of it. I'm gonna fix this in the next version of the mod

if it helps, regex for ANY_DISCORD_MENTION_PATTERN in M2DUtils could be <a?(?::\w+:|@&*|#)\d+>, and line 111's regex in M2DUtils could be <a?:(\w+):\d+> and you'd be pretty much set

also, im aware its not the primary topic of the issue report but i still wanna mention it anyway, I don't think Emojiful allows emojis with capitals in? When I tried adding emojis with capitals they simply didn't appear in the emojiful selection, and the official emojiful datapack creation bot in the emojiful Discord also lowercases every emote name.
I'm bringing this up here as this means any emotes with capital letters in that are sent in discord chat wont appear correctly in game. Lowercasing the emoji name shows up fine, however. (screenshots are from a fork where the emojis are lowercased before being sent)


FileReq::data data member shadows Resource::data member function

We know that the FileReq is inherited from Request and Request is inherited from Resource. However, FileReq has a data member FileReq::data whose name is same as Resource::data member function. Therefore, I have to call Resource::data like this:
req->uvw::Resource<uvw::FileReq, uv_fs_t>::data(ctx);

which is quite not elegant and annoying since I have to know the template arguments of Resource.

What name would be good for that?

I'm not so sure. Perhaps m_data is a good choice but it will break the code style.

I think I'm missing something. FileReq has no public member named data. Is the private one that gives you an error?

Yes.
That's true for MSVC (but I haven't tried to compile). Intellisense seems to think FileReq::data has an operator () overloading function.

Oh, ok, sorry, I didn't get it initially. So who cares of the name after all.
I'll change it the soonest. Thank you for reporting it.

Upstream. Let me know if it works for you.

It should work now. Thanks for your support.


Allow disabling nrf51/rt feature

Why would you want to disable rt?

Because I based my prototype on https://github.com/japaric/cortex-m-quickstart which includes locally defined interrupt handlers, and attempting to build with nrf51/rt enabled gives me an error related to duplicate interrupt handlers. Unless nrf51-hal requires the nrf51/rt defined interrupt handlers (which it doesn't appear to yet) it should allow disabling these.
I have since switched the rt feature on and got rid of my own interrupt handlers, but I still think it would be good to make that an option to users of the library.

Hm... that's really weird. I'll have to check the consequences of such a change...


Cell Forge missing recipe

As title says, cell forge has no recipe in the latest 1.19.2 version.

looking at the data file you have the type set to  "type": "minecells:cell_forge_recipe",
So my assumption is Minecells is not compatible with REI hence me not seeing recipe,. and also, how is one supposed to craft a cell forge in a cell forge?

Hi, the Cell Forge is not available in survival yet. Sorry for not making it clear 😅
I still have to sort some things out before making it usable, like REI compatibility. And I have to figure out if the Cell Forge is actually the best approach, or if I should do something different in its place.
I can change the name to "Cell Forge (creative only)" until it's ready / replaced

Ah this makes sense. i imagine "cells" are also not yet ready? not seeing any at all

You can turn on the minecells.mobsDropCells gamerule to make them drop! But for now they're disabled, because without the cell forge they have no use

Recent version adds a completely reimagined and fully fleshed out version of the Cell Crafter!


[i18n-de-es-ru] add adjust nomination to start_nominating

done de.
make sure to add "rebonding" section too.


UDR metric fetch failed 500 Internal

Hello
My configuration:
      - UP_PROMETHEUS_DISABLE=false
      - UP_UNIFI_CONTROLLER_0_USER="unifipoller"
      - UP_UNIFI_CONTROLLER_0_PASS="xxxxxxx"
      - UP_UNIFI_CONTROLLER_0_URL=https://<IP_ADDRESS>

Problem:
2023/03/04 11:51:31 [INFO] Re-authenticating to UniFi Controller: https://<IP_ADDRESS>
2023/03/04 11:51:31 [ERROR] metric fetch failed: re-authenticating to https://<IP_ADDRESS>: unifi controller: (user: "unifipoller"): https://<IP_ADDRESS>/api/auth/login (status: 500 Internal

I create user in UDR

I have no more UDR I close


How do I initialize the DB?

Thanks for the great repository, Chris!
I'm getting an error when I try to sign up as a new user:
File "/var/www/convers.ai/python/flask-mongo-app/run.py", line 118, in register
    users = mongo.db.users
AttributeError: 'NoneType' object has no attribute 'users'

I've never worked with MongoDB before. But I suspect it's because my database is empty, i.e. has no columns?
Any command I need to run in order to initialize the database?
The DB itself seems to be working. I successfully ran this:
from pymongo import MongoClient
client = MongoClient(host = ["<IP_ADDRESS>:27017"])
client.server_info()

Hi there. Thanks for your message. The live demo uses a MongoDB Atlas service. You might need to set up a free account at MongoDB Atlas to get access to your own database. It should work fine from there.
I have not set up a MongoDB server locally yet, so I’m not sure how to get that to work. As you say, it PyMongo’s MongoClient seemed to connect, I would have thought it was working.
I’ll try this later. Let me know how you get on if you have time.
Thanks again
Chris

On 3 May 2021, at 16:20, leobaumgardt @.***> wrote:

Thanks for the great repository, Chris!
I'm getting an error when I try to sign up as a new user:
File "/var/www/convers.ai/python/flask-mongo-app/run.py", line 118, in register
users = mongo.db.users
AttributeError: 'NoneType' object has no attribute 'users'
I've never worked with MongoDB before. But I suspect it's because my database is empty, i.e. has no columns?
Any command I need to run in order to initialize the database?
The DB itself seems to be working. I successfully ran this:
from pymongo import MongoClient
client = MongoClient(host = ["<IP_ADDRESS>:27017"])
client.server_info()
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hi @leobaumgardt did you get this working? I'm just following up on previous issues.
Thanks
Chris

DB has connected with this config for me
[DEFAULT]
SECRET_KEY = secret123
SECURITY_PASSWORD_SALT = x123456
DATABASE_NAME = users
MONGO_URI = mongodb://<IP_ADDRESS>:27017/users

Thanks for your update. Is it working as expected for you now?

On 4 Jan 2022, at 08:29, Jaggernaut @.***> wrote:

DB has connected with this config for me
[DEFAULT]
SECRET_KEY = secret123
SECURITY_PASSWORD_SALT = x123456
DATABASE_NAME = users
MONGO_URI = mongodb://<IP_ADDRESS>:27017/users
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.


chore: jsonfmt network 2019

Ran jsonfmt -w "specification/network/**/stable/2019*/**/*.json"

Can one of the admins verify this patch?

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-go

Automation for azure-sdk-for-js

Automation for azure-sdk-for-python

@nschonni This seems to trigger errors here either undo changes to that directory or fix the errors if you can

Automation for azure-sdk-for-java

@nschonni  please resolve the conflicts due to release date is tomorrow

@dsgouda  can we merge this list of a fixes as well? One known job is failed, the rest of them looks to be passed

commited with --amend w/o changes to re-trigger CI

@dsgouda can you please help to merge?


Preserve source order

Just had an idea to solve #61 without changing the API.
@kof if you agree with this, I'll finish the PR by adding a test.

We thought about reverse order rendering of styles with @nathanmarks and he found a case where this still breaks.

It is fixing a simpler case though.

Here is the case where its still a problem.
class MyAwesomeApp {
  render() {

      <MyAwesomeIcon />

WELCOME!

      <MyAwesomeToolbar />

  }
}

class MyAwesomeToolbar {
  render() {
    const classes = this.context.styleManager.render(styleSheet);
    return (

        <MyAwesomeIcon className={classes.icon} />

    );
  }
}

I don't see any real fix right now other than "never pass a class from a parent"

I don't really understand your issue yet and what you exactly mean by "reverse order rendering of styles". The solution I propose is to keep a global index counter to set the index at the same point as when the source code was imported / parsed. This way we have the same behavior as when we were using CSS-Modules.
So in this case your example would be:
@injectSheet(stylesA) // index is set to -10000 and used later for style sheet creation
class MyAwesomeIcon {
  render() {
    const classes = this.props.sheet.classes;
    return (

    );
  }
}

import {MyAwesomeIcon} from "./MyAwesomeIcon";

@injectSheet(stylesB) // index is set to -9999 and used later for style sheet creation
class MyAwesomeToolbar {
  render() {
    const classes = this.props.sheet.classes;
    return (

        <MyAwesomeIcon className={classes.icon} />

    );
  }
}

import {MyAwesomeIcon} from "./MyAwesomeIcon";
import {MyAwesomeToolbar} from "./MyAwesomeToolbar";

@injectSheet(stylesC) // index is set to -9998 and used later for style sheet creation
class MyAwesomeApp {
  render() {

      <MyAwesomeIcon />

WELCOME!

      <MyAwesomeToolbar />

  }
}

Resulting in the following priority order:
MyAwesomeApp -> MyAwesomeToolbar -> MyAwesomeIcon

Actually this behavior is even better than with CSS Modules. Because in CSS Modules the order is determined upon import, but this proposal would determine order upon Component Definition. This is actually significant because this is the most optimal time to do so. With CSS Modules the style sheet order can get wrong when dependent styles are imported between the style import and the actual Component Definition.

I misinterpreted your suggestion. Looks very promising!

By reverse order rendering I meant:
<SheetB />
<SheetA />

So the parent's sheet is rendered lower in the head than the child, and you did that by starting with a negative index.

I have been using a similar technique for https://github.com/wikiwi/react-jss-theme (discontinued) and now https://github.com/wikiwi/themr. It works great so far! If you agree I'll finish this PR by adding some tests.

@nathanmarks found one potential case where it will not work:
// Button.js
const Button = (props) => (
  <button>
    {clone(props.icon)}
  </button>
)

// something.js
import Icon from 'icon';
import Button from './Button'

<Button icon={<Icon />} />

@kof Can you explain your case more in detail?

So the case is where a generic component accepts a react element, clones that element and tries to override some rule props using an own rule over class name.
Now the specificity of the  rule from Button component depends on whether  the "something.js" module has imported "Icon" first and "Button" second or the other way around. If Icon is imported first and button second, the sheets order will be , so the icon sheet will have a stronger selector.

I would still go for your solution because I don't know anything better and it will work in the most cases.

Maybe defining the index inside of the constructor is lightly better, because then it depends on element creation time, not on require() time.

Lets fix this, I think its even worth an article about specificity issues.

Alright, I'll update this PR by tomorrow.

Ready to be reviewed

I guess we would have much nicer tests if we would use enzype + snapshots ...

Snapshot means using jest right? I'm not familiar with jest sounds like a major change.

Yeah its a bit a bigger change. Also we would loose testing in real browser, which might be ok for this project, because all DOM stuff happens in the core anyways.

Will merge it for now, though I think this approach is a bit verbose)

A bit yes, maybe you can find ways to make it less verbose.

A bit yes, maybe you can find ways to make it less verbose.


Watchdog timeout incorrectly set to infinity

For some reason the watchdog timeout keeps being set to infinity in my application. Best I can tell, this can only happen if the WATCHDOG_USEC environment variable is unset or does not contain a valid integer.
When I try to debug this (by doing some rpc calls into the application) I can see the correct values for the environment variable.
I use distillery for deployment, but I don't think that's the cause.
systemd  Unit:
[Unit]
Description=xxx
Wants=network-online.target
After=network.target network-online.target

[Service]
Type=notify
ExecStart=/etc/init.d/xxx systemd_foreground
User=userxxx
Group=users
WorkingDirectory=/home/userxxx
WatchdogSec=15
NotifyAccess=all
Restart=on-failure

[Install]
WantedBy=multi-user.target

watchdog state:
$ app.sh rpc ":systemd.watchdog(:state)"
:infinity

config.exs:
config :systemd,
  unset_env: false

WATCHDOG_USEC environment variable:
$ app.sh rpc ":os.getenv('WATCHDOG_USEC')"
'15000000'

WATCHDOG_USEC  to integer conversion:
$ app.sh rpc ":os.getenv('WATCHDOG_USEC') |> :string.to_integer()"
{15000000, []}

systemd_sup:init/1 return value:
$ app.sh rpc ":systemd_sup.init([])"
{:ok,
 {%{strategy: :one_for_one},
  [
    %{
      id: :socket,
      start: {:systemd_socket, :start_link, [local: '/run/systemd/notify']}
    },
    %{id: :watchdog, start: {:systemd_watchdog, :start_link, [:infinity]}}
  ]}}

WATCHDOG_USEC and systemd_sup:init/1 in one call (to exclude any timing issues):
$ app.sh rpc "[:os.getenv('WATCHDOG_USEC'), :systemd_sup.init([])]"
[
  '15000000',
  {:ok,
   {%{strategy: :one_for_one},
    [
      %{
        id: :socket,
        start: {:systemd_socket, :start_link, [local: '/run/systemd/notify']}
      },
      %{id: :watchdog, start: {:systemd_watchdog, :start_link, [:infinity]}}
    ]}}
]

What is the :os.getpid() and :os.getenv('WATCHDOG_PID') values?

:os.getpid() and :os.getenv('WATCHDOG_PID'):
$ app.sh rpc "[:os.getpid(), :os.getenv('WATCHDOG_PID')]"
['24553', '24545']

$ ps faux
ubnt     24545  0.0  0.0   3376  2432 ?        Ss   13:42   0:00 /bin/sh /etc/init.d/xxx systemd_foreground
ubnt     24548  0.0  0.0   5032  2932 ?        S    13:42   0:00  \_ bash -c ...
ubnt     24549  0.0  0.0   5036  2924 ?        S    13:42   0:00      \_ /bin/sh ...
ubnt     24553 88.7  0.4<PHONE_NUMBER>2 ?        Sl   13:42   0:06          \_ /home/ubnt/app/releases/1.7.1/app.sh ...
[...]

(I think this should be fine, because the .service sets NotifyAccess=all)
Other things that may be useful:
$ app.sh rpc ":os.getenv('NOTIFY_SOCKET')"
'/run/systemd/notify'

$ app.sh rpc ":systemd_watchdog |> Process.whereis() |> :sys.get_state()"
{:state, :infinity, true}

$ app.sh rpc ":systemd_watchdog |> Process.whereis() |> :sys.get_status()"
{:status, #PID<12066.2358.0>, {:module, :gen_server},
 [
   [
     "$ancestors": [:systemd_sup, #PID<12066.2355.0>],
     "$initial_call": {:systemd_watchdog, :init, 1}
   ],
   :running,
   #PID<12066.2356.0>,
   [],
   [
     header: 'Status for generic server systemd_watchdog',
     data: [
       {'Status', :running},
       {'Parent', #PID<12066.2356.0>},
       {'Logged events', []}
     ],
     data: [{'State', {:state, :infinity, true}}]
   ]
 ]}

Ok, so I see the problem there. The PID of the BEAM VM is different from the watched PID:
$ app.sh rpc "[:os.getpid(), :os.getenv('WATCHDOG_PID')]"
['24553', '24545']

And man 3 sd_watchdog_enabled explicitly say that:

If the $WATCHDOG_USEC environment variable is set, and the $WATCHDOG_PID variable is unset or set to the PID of the current process, the service manager expects notifications from this process.

Due to that the default interval is set to infinity and it is marked as a disabled. Now I think that it could be set to be disabled, but the interval still would be set to the passed value, however that would have different behaviour from the systemd implementation.
From what I see the main problem is that you are using SysV-like init file and that is the PID watched, not the BEAM VM:
$ ps faux
ubnt     24545  0.0  0.0   3376  2432 ?        Ss   13:42   0:00 /bin/sh /etc/init.d/xxx systemd_foreground
ubnt     24548  0.0  0.0   5032  2932 ?        S    13:42   0:00  \_ bash -c ...
ubnt     24549  0.0  0.0   5036  2924 ?        S    13:42   0:00      \_ /bin/sh ...
ubnt     24553 88.7  0.4<PHONE_NUMBER>2 ?        Sl   13:42   0:06          \_ /home/ubnt/app/releases/1.7.1/app.sh ...

I have tested the application using mix release, but I can also try to setup tests with Distillery and Relx, however as I do not use them currently then it probably will be left as "help wanted".

And man 3 sd_watchdog_enabled explicitly say that:
[…]

Thank you for that! I must've misremembered what exactly NotifyAccess does.

[…] but I can also try to setup tests with Distillery and Relx, however as I do not use them currently then it probably will be left as "help wanted".

 However, I'm fairly certain that at least one of them (PID 24553 above) is always "added" by distillery.
Anyway, thanks again for you help! I think this is can be resolved as user error 🙂

I have created #14 that will always set the interval and will just not enable the watchdog if the PID is not the same. In that way user will be still able to force it if needed.


Build Error: Cannot resolve reference: 'Com.ViewPagerIndicator'

When I tried to upgrade the xamarin forms version to 4.2 stable (old version was 2.5) keeping the carouselview.formsplugin.Android(CarouselView.FormsPlugin nuget(version 5.2) is already installed in android and .net standard projects). I am getting following errors.
Cannot resolve reference: 'Com.ViewPagerIndicator' ,referenced by 'CarouselView.FormsPlugin.Android' Please add a nuget pacakage or assembly reference for 'Com.ViewPagerIndicator' Or remove the reference to 'CarouselView.FormsPlugin.Android' .
We are using xamarin.android.Support libraries of v4,v7 and v13. Could you please help us on this.

@pramodhgeorge2019 here some referenced issues that should not be closed
#261
#518
#525
#489

Thanks. Probably when will fix come? Any workaround? Highly appreciated if any.

A fix will come out soon. Been working on it for a while.

Thanks a lot Alex !
On Tue 22 Oct, 2019, 10:42 PM Alexander Reyes<EMAIL_ADDRESS>wrote:

A fix will come out soon. Been working on it for a while.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/alexrainman/CarouselView/issues/551?email_source=notifications&email_token=ANRZ22RSDJF27GGMHDZA4KDQP4YAJA5CNFSM4JDK22V2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB6QADY#issuecomment-545062927,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANRZ22TD6CTBMJFZLQTE6ATQP4YAJANCNFSM4JDK22VQ
.


Missing pixi.js.d.ts

I just updated to PixiJS v6 RC and wanted to check if the updated types in v6 broke our Angular project and I get this errors that certain attributes don't exist anymore on certain types. If I check the v6 docs, the attributes are still there and not deprecated. Then I saw, that the pixi.js.d.ts is missing from node_modules/pixijs and maybe that confuses the typescript compiler.
I get this error from VS Code:
"Unable to open 'pixi.js.d.ts': Unable to read file '/Users/toms/Coding/WaveModeler/node_modules/pixi.js/pixi.js.d.ts' (Error: Unable to resolve non-existing file '/Users/toms/Coding/WaveModeler/node_modules/pixi.js/pixi.js.d.ts')."
And a lot of compilation errors like this:
ERROR in src/app/main/processTabContent/editor/editor.component.ts:102:18 - error TS2339: Property 'loader' does not exist on type 'Application'. this.pixiApp.loader.load(() => this.pixiApp.renderer.render(this.pixiApp.stage));
Environment

pixi.js version: 6.0.0-rc
OS & Version: macOS 11.1 Big Sur
Angular Version: Angular 10
Typescript Version: 3.9.7

Thanks for reporting.
Do you have a reproduction of these errors? That would be helpful to verifying.
The first error doesn't make sense to me because we removed the pixi.js.d.ts file. Are you sure that isn't referenced somewhere in your project? The new type file should be in node_mdoules/pixi.js/index.d.ts.
As for the missing loader on Application, should be pretty straightforward. Can you describe any other missing properties you're seeing or is it just loader? Or again if you could get us a repo that reproduces this that's the most helpful.

Thanks for reporting.
Do you have a reproduction of these errors? That would be helpful to verifying.
The first error doesn't make sense to me because we removed the pixi.js.d.ts file. Are you sure that isn't referenced somewhere in your project? The new type file should be in node_mdoules/pixi.js/index.d.ts.
As for the missing loader on Application, should be pretty straightforward. Can you describe any other missing properties you're seeing or is it just loader? Or again if you could get us a repo that reproduces this that's the most helpful.

@bigtimebuddy I'll try to make an StackBlitz example :)
In the meantime: Those aren't the only errors. Here are a few more. I guess all connected to the error with the wrong *.d.ts
src/app/main/toolbar/export/StageExporter.ts:46:42 - error TS2339: Property 'extract' does not exist on type 'Renderer | AbstractRenderer'. Property 'extract' does not exist on type 'AbstractRenderer'. const dataURL = pixiApp.renderer.extract.canvas(stage).toDataURL();
src/app/main/toolbar/export/StageExporter.ts:81:25 - error TS2339: Property 'ticker' does not exist on type 'Application'. pixiApp.ticker.remove(exportFunc);
src/shapes/flowObjectShapes/activity/ActivityShape.ts:69:47 - error TS2554: Expected 0-1 arguments, but got 4. this.lineStyle(ActivityStyle.borderWidth, ActivityStyle.borderColor, 1, 0.5);

@bigtimebuddy I'll try to make an StackBlitz example :)
In the meantime: Those aren't the only errors. Here are a few more. I guess all connected to the error with the wrong *.d.ts
src/app/main/toolbar/export/StageExporter.ts:46:42 - error TS2339: Property 'extract' does not exist on type 'Renderer | AbstractRenderer'. Property 'extract' does not exist on type 'AbstractRenderer'. const dataURL = pixiApp.renderer.extract.canvas(stage).toDataURL();
src/app/main/toolbar/export/StageExporter.ts:81:25 - error TS2339: Property 'ticker' does not exist on type 'Application'. pixiApp.ticker.remove(exportFunc);
src/shapes/flowObjectShapes/activity/ActivityShape.ts:69:47 - error TS2554: Expected 0-1 arguments, but got 4. this.lineStyle(ActivityStyle.borderWidth, ActivityStyle.borderColor, 1, 0.5);

The extract one has been fixed already (unreleased). Application ticker will get fixed with loader (working on that now).
Will look into lineStyle issue. I thought that was deprecated in favor of an single object. Hmm, will take a look.

The extract one has been fixed already (unreleased). Application ticker will get fixed with loader (working on that now).
Will look into lineStyle issue. I thought that was deprecated in favor of an single object. Hmm, will take a look.

@tomasfreres I think I hit all of these issues. Can you please confirm about the pixi.js.d.ts error? I'm not seeing how that's possible. A reproduction would help.

@tomasfreres I think I hit all of these issues. Can you please confirm about the pixi.js.d.ts error? I'm not seeing how that's possible. A reproduction would help.


[RFC]: add math/base/special/acotf

Description
This RFC proposes adding math/base/special/acotf, which would be the single-precision equivalent of math/base/special/acot.
float stdlib_base_acotf( const float x )

Related Issues
None.
Questions
No.
Other
No.
Checklist

[X] I have read and understood the Code of Conduct.
[X] Searched for existing issues and pull requests.
[X] The issue name begins with RFC:.

I'd like to work on this.

Hey @kgryte, while implementing this, I got to know that, since we require atanf for this, and upon passing -infinity to acotf, or -0 to atanf, our atanf returns 0, instead of -0. This applies for both C and JavaScript implementations of atanf.
This leads to the failure of one particular test case, which checks if the function returns "-0" if provided "-infinity".

In the case of current acot, this problem doesn't arise, but it does come up in case of acotf.

Which behavior is the correct behavior?

The correct behavior is that of acot, i.e, it returns -0 when provided -infinity.
Applying the same implementation for acotf, this fails.

The question is more fundamental. Should atan distinguish between signed zeros? This is a mathematical question.

It's possible, e.g., that the tests for acot are incorrect, but this gets back to what the behavior of atan should be.

We get our answer from http://www.dsc.ufcg.edu.br/~cnum/modulos/Modulo2/IEEE754_2008.pdf

For the functions expm1, exp2m1, exp10m1, logp1, log2p1, log10p1, sin, tan, sinPi, atanPi, asin, atan, sinh, tanh, asinh, and atanh, f (+0) is +0 and f (−0) is −0 with no exception.

Meaning, atanf is incorrect here.

When I checked logging the values with atan, it returns:
atan( -0 ) = -0
atan( +0 ) = 0

Yes, but we should not just rely on what the current behavior is in stdlib, as the current behavior could be wrong. In this case, we need to consult the specification to ensure that our current atan behavior adheres to IEEE 754 semantics.
In this case, it does. Which just means that our current atanf implementation does not handle signed zero correctly.

Yes, and also, upon doing the same for atanf, it gives 0 in both cases.
We might need to modify our atanf implementation.

The reason it doesn't is pretty straightforward. We just need to make a small modification to atanf which we can observe in atan. Namely, the following
https://github.com/stdlib-js/stdlib/blob/edc9c69f219cd5bdcf08fe2f2bf0f03c191776b0/lib/node_modules/%40stdlib/math/base/special/atanf/lib/main.js#L89
should be modified to
if ( isnanf( x ) ) {
+ if ( isnanf( x ) || x === 0.0 ) {

This is a bug in the original Cephes implementation. You'll want to fix in both our JS and C atanf implementations.

When you make patch, can you also add corresponding tests to atanf?

I suggest making a quick patch in a separate PR to keep things clean.

Great, I'll follow that. Thanks for clearing this out.
This can be a nice example for why we shouldn't rely on just one source, like cephes.

Indeed! And the importance of tests! We are apparently missing corresponding tests in atan, as well. You can include those in your patch.


Draft acceptance criteria for the Wallet API v2

Valentin to start the spec, then bring in @vegaprotocol/qa to assist in the AC creation

The PR #1477 goes some way towards this but probably shouldn't be considered wallet spec.


Collaborate on TypeScript related things on this repository?

Hi, @ljharb
I'm now the maintainer of https://github.com/import-js/eslint-import-resolver-typescript, we just moved it to import-js org recently. And there are a lot of TypeScript only related issues in this repository, maybe I can help to collaborate, how do you think?

That'd be great! PRs are most welcome :-)

That'd be great! PRs are most welcome :-)

@ljharb
Some issues can be closed directly in favor of eslint-import-resolver-typescript, another thing would be adding a section about TypeScript resolver.
I’m here also asking for permission to maintain the issues at least, how do you think?

Sure, I've given you Triage access.


Add homework

Good Job!!!   @zjdzzz123
Python homework:

Total questions: 108
Correct answers: 108
Score: 100.00%

Numpy homework:

Total questions: 10
Correct answers: 10
Score: 100.00%

Pandas homework:

Total questions: 12
Correct answers: 12
Score: 100.00%

@zjdzzz123
把Python编程的扩展作业也做一下吧哈？

@zjdzzz123
完成Python基础作业，Matplotlib+Seaborn数据可视化作业，Sklearn建模和调参作业！


Sor10874/numeric text field

Provides support for numeric types in FormTextField.

adds a FieldType and a Domain? property to the BaseFieldState, and the FieldProperties. These are common to all elements, but only used in FormTextField and BaseTextField.
adds Saver supporting logic for the new properties
invokes the appropriate keyboard for integer, floating point, or non-numeric input on BaseTextField
adds some validation strings for numeric inputs, and refactors validation a bit
extensions on FieldType and platform types to make things a little simpler
tests
test refactoring to support FieldProperties (tests were broken).

thanks @kaushikrw merging!


add multiple versions of conda to the test matrix

(merging as the tests I'd expect to pass pass, and the tests that #43 aim to pass don't)


What's the meaning by "Points above vertex id 845 are not defined on the reference" in ibug2did.txt?

I don't understand the meaning of "Note: Points above vertex id 845 are not defined on the reference and thus not available in all model resolutions."?
I also think the mapping from landmarks to vertices is a little complex. Why use three file (image_0010.pts,ibug2did.txt,model_contours.json)to do this simple task?

Well, the reference has 845 vertices. So, naturally, all points in the mapping that have a vertex id higher than the number of vertices of the model you're using, will not be defined in that model. (So you should uncomment them in the mappings file).

Thank you


Add CI and test with JUnit

Added CI and test with JUnit.
Also updated from gradle 7.4 to 8.7. (All the wrapper and gradlew changes are done automatically with ./gradlew wrapper --gradle-version 8.7.)
See test here.

GitHub doesn't like how I moved the test file, but you can compare the deleted TestMain with the new one to see the diff. I just replaced everything with assertions. Hope this helps.

Closes #4

Rebased this so i can have the gradle wrapper validation action run on this. I am not too sure about those tests. Some of those seem very fragile keeping in mind future updates (for example max fairy souls will certainly change at some point). Maybe this can be helped by pinning the repo commit? I also think those tests should be split up into multiple functions.

Done


Fix feature-platform tests

Description of changes:
Fixing feature platform tests, setting standard column names
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/platform_tests ref=trial

/platform_tests ref=trial

/platform_tests ref=trial

/platform_tests ref=trial

/platform_tests ref=trial

/platform_tests ref=trial

/platform_tests ref=trial


Replace kafka with amqp in headers

Sync codes from https://github.com/Azure/azure-sdk-for-java/pull/33210

API change check
APIView has identified API level changes in this PR and created following API reviews.
spring-messaging-azure-eventhubs


Extra release note for the next 2.2 (after 0211)

This:

(sql change) The generation algorithm for the OID column for tables in pg_catalog has been modified. As with previous CockroachDB releases, we guarantee that the OID values are consistent between pg_catalog tables (so that tables can be joined together) but we do not guarantee that they are stable across CockroachDB versions. Avoid storing them in client apps.

Including this in next Monday's release candidate. Forgot to in the previous beta. What's the source PR for this change, @knz?

That would be #33697.

Thanks, @knz.


Returning a list from python

Hi,
I am trying to get a list generated in python into javascript, however this is not working.
Here is my Python code
@eel.expose
def remember_settings():
	with open('../config/settings.json', 'r') as f:
		data = json.load(f)
		region = data['region']
		url = data['url']
		webhook = data['webhook']
		use_proxies = data['use_proxies']
		browser = data['browser']
		licensekey = data['license']
		theme = data['theme']
	return [region, url, webhook, use_proxies, browser, licensekey, theme]

And here is my JavaScript code:
window.onload = function remembersettings () {
  load_settings = eel.remember_settings()();
  alert(load_settings[0]);
}

Right now it just comes up with an empty alert, and typeof just returns object...
Am I doing something wrong?

Okay so it works now if I do
window.onload = async function remembersettings () {
  let settings = await eel.remember_settings()();
}

Is this the best/fastest way to do it?

@04fsnape This is probably the nicest way to do it in my opinion.
The async style would be;
window.onload = function remembersettings () {
    eel.remember_settings()(function(list){
        alert(load_settings[0]);
    });
}


Fix "Baisakhi" in translations to be "Vaisakhi"

https://www.sikhitothemax.org/shabad?id=3980&q=Baisakhi&type=3&source=all&highlight=47360 is not fixed but bani_db is showing a pending change even though i believe it received +2 votes @ManjotS

same with https://www.sikhitothemax.org/shabad?id=3980&q=Baisakhi&type=3&source=all&highlight=47365

fixed in prod


Incomplete README.md content

Description：
Incomplete azd command for deploying projects

Suggestion：
Please update the steps as follows:
1. Log in to Azure Developer CLI. This is only required once per-install.
azd auth login

2. Initialize this template using azd init
azd init --template build5nines/azd-react-bootstrap-dashboard

3. Use azd up to provision your Azure infrastructure and deploy the web application to Azure.
azd up

@crpietschmann and @hemarina for notification.

Thanks for the PR. The readme has been updated.


enable strict deabstraction on crashers.swift (SR-8303)

This fixes two things that were breaking strict deabstraction in crashers.swift:

Strict deabstraction makes some errors happen earlier, which was blocking partitioning from happening in crashers.swift. I moved the tests with those errors to a new file.
formGraphOp does not have a check for unsupported attribute types, so the unsupported types get into graph lowering and cause an assertion failure. I added a check for unsupported attribute types in formGraphOp.

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow


X.U.NamedActions: Do not discard all keybindings in addDescrKeys

Discarding keybindings may yield unintended behaviour when keybindings are added via combinators, instead of the keys field.  This makes the
combinators noncommutative, which is very counterintuitive.
Related: https://old.reddit.com/r/xmonad/comments/10g1v1r/deftogglestrutskey_not_working/

This is a PR because I don't use NamedActions and, though I've verified that this doesn't immediately break things with the simplest config, someone else should look at ti

Checklist

[x] I've read CONTRIBUTING.md

[x] I've considered how to best test these changes (property, unit,
manually, ...) and concluded: tested manually; seems to do the trick.

[x] I updated the CHANGES.md file

Let's see, then :)


Maven Refactor

In order to reduce number of virtual machines, support adding maven build support to primary nimbus system, instead of creating a separate virtual machine.

fixed with https://github.com/darkn3rd/storm-vagrant/commit/d7fcb3d19b1abd892aa2b1c278e82f58bc42ba1e

PR https://github.com/darkn3rd/storm-vagrant/pull/17


Add file UT de la Costa

Add domain Universidad Tecnológica de la Costa

@ingjando85 First stage of verification passed, official domain for Universidad Tecnologica de la Costa is utdelacosta.edu.mx as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@ingjando85 Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


Items add by script don't get arranged in a circle.

I'm adding buttons to a circular container via a script, but all of them just appear in the top left corner of the container. Perhaps an "update" function to reconfigure the placement of children nodes could be helpful.

You can already do that, using either circular_container.emit_signal("sort_children") or circular_container._resort()
I agree that an exposed function to do it would be better though.


Why are the links to v0.1 not in english ?

This bring you to the demo page, but for v0.1, the demo page is in english so the link should also be in english 🤔
No ?

updated


Sub task strikethrough appearing for incomplete tasks in page preview

Please check that this issue hasn't been reported before.

[X] I searched previous Bug Reports didn't find any similar reports.

Expected Behavior
When a sub-task is incomplete, it would appear as incomplete on the page preview.
Current behaviour
At the moment all sub tasks with completed main tasks shows with a strikethrough in the page preview:

Steps to reproduce
Create a task, with a sub-task. Complete the main task while leaving the sub-task un-checked.
Use a task query to find the sub-task.
Use the link for a page hover.
For me it shows the task as complete and sub-task with a strikethrough.
Which Operating Systems are you using?

[ ] Android
[ ] iPhone/iPad
[ ] Linux
[ ] macOS
[X] Windows

Obsidian Version
1.2.2
Tasks Plugin Version
3.0.0
Checks

[X] I have tried it with all other plugins disabled and the error still occurs

Possible solution
No response

@DannyHatcher-Git have you done this:
https://publish.obsidian.md/tasks/How+To/Style+custom+statuses

No, I haven't added/changed anything about the tasks plugin since instillation so is all default features.

No, I haven't added/changed anything about the tasks plugin since instillation so is all default features.

That would explain it. This is from the Tasks settings page:

Please do read the Status docs. Thanks.
If you following them and it still doesn't work, let me know here and I will re-open the issue.

I think I may have misunderstood what you meant by incomplete, as in progress. Still, after setting up styles, and if you do actually still have a problem, let me know and I will re-open it.

Yeah, when I said incomplete I meant - [ ]
I will experiment with adding a style as currently it is just default to see if that fixes it.


Fix Parser Bug causing 2x Dupe Data & Optimize Parser

I noticed i was receiving ~275 rows of data per second from a single umyo device. It is supposed to take a sample at 5us acquisition time + 2us conversion time), oversample them 128x, and bundle 8 samples into a data packet. (1 / (0.000007 * 128)) / 8 = 140 packets per second theoretically. So we have been getting ~2x the data. Where does it come from?
The parser code had a subtle bug. Everytime data is received on the serial port the parser is called and the current device data is written to display (or file). The issue is that sometimes the serial port contains a partial packet. The parser is called on this data update. Then regardless of whether we parsed a (full) new packet or not we write a new row of data to screen or file.
The usb basestation adds RSSI and header making the packet size 65, but the station can only send 64 bit packets. so each umyo packet results in 2 basestation packets (64/1). At the python level this results in double the data production with ~half of them duplicates!!!!!!!
I also simplified and optimized the parser logic so it more precisely identifies, validates and processes each packet.
finally i added an illustrative simple_data_logger.py (based on turfptax's script) that logs data using the new parser approach.

need to further review this patch... the changes i made weren't integrated with the pygame visualization scripts. Note: they viz scripts do not contain the bug because they filter packets in plot_prepare with: " if(devices[d].data_id != last_data_id[d]):"

@jbherman Me and my team mate are working on a project with uMyo sensors and we got really interested in your code updates. We would like to incorporate them into our project as well.  Are you planning on finalizing your patch any time soon?


[Feature Request]: add navbar

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
i wanted to add navbar to provide users with easy navigation
Use Case
implementation of navbar enhance user experience
Benefits
Users can find what they need quickly
Priority
High
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC contributor
[X] I want to work on this issue
[X] I'm willing to provide further clarification or assistance if needed.

What are the things you want to add in navbar

I go through your code base but i did not find any webpage like stuff where to add this navbar and what are the things that you want to add the navbar

Kindly assign this issue to me; I would like to contribute to this project.


Add NGINX integration with 3scale on Kubernetes

One of the things missing from this PR is the documentation.
The documentation for this PR is still in PR #1305.
I will hold on to it for now once I have the complete docs ready for deploying everything.
Else we can leave this open till as such time the docs shape up.

I see our work on Kubernetes deployment as a work in progress (and said as much in the change log). It doesn't have to be fully-functional or fully-documented for the version 0.10.0 release next week. Mainly we need the single-node case operational so that REDACTED can use it.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1392   +/-   ##
=======================================
  Coverage   98.22%   98.22%
=======================================
  Files          54       54
  Lines        2472     2472
=======================================
  Hits         2428     2428
  Misses         44       44

Continue to review full report at Codecov.

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

:+1:


cashu: adj. dependencies

Add some scripts in misc/scripts
Remove k256, bip32, hex, log, rand and itertools deps
Add  once_cell and instant deps
Downgrade bitcoin to v0.30 and base64 to v0.21  (lightning-invoice uses bitcoin v0.30 and bitcoin uses base64 v0.21)
Replace utils module with util
Remove utils from cashu-sdk
Some cleanups

I'm happy enough to ignore the CI and it can be fixed in https://github.com/thesimplekid/cashu-crab/pull/79.

I'm happy enough to ignore the CI and I can fix in #79.

Now should succeed


A data generation problem

Hi, when I use the autopilot to start data generation, I get a "failure" as the following picture:

I know this problem is common, but I worry it will affect the final result of model training since we imitate an imperfect expert. How do you think about this?

In addition, I don't why I get some black points in the images. Do you know the cause?

Hi, sorry for the late reply.
The expert uses collision avoidance heuristics which has certain loopholes resulting in few collisions. Ideally, this should be removed from the training data but I think as long as this type of data is very less compared to the proper driving data, the model should be able to learn proper driving behavior.
These black dots are due to some rendering issues when running CARLA with opengl. You can try running with vulkan to remove these artifacts. For running with vulkan, just replace -opengl with -vulkan when launching the CARLA server.


Quick tile settings causes complete reset

Why does it completely reset the tiles each time you go into the settings for it?

Curious about that, too.
However, I've upgraded to Android 14 and seems like QS Editor isn't possible anymore (no root and nor shizuku), except change by restore app settings.

Sorry for bump, but it was resolved on my side by install add-ons.


move qmp handling to neonvm-runner

Problem description / Motivation
As discussed here.
There's a few reasons for this:

neonvm-controller sleeps during reconcile while waiting for QEMU; we'd like to avoid sleeps there
Using QEMU events subscription would be hard (but not impossible) in neonvm-controller because of the execution & data model, but we can make it easy for neonvm-runner. See also: #327
Exposing QMP port cluster-wide is a potential security hole. See also: #414

Feature idea(s) / DoD
QMP is inaccessible outside the runner pod; neonvm-runner is exclusively responsible for making the CPU/memory changes that the controller requests (+ starting migration?).
Implementation ideas
Some considerations to be made w.r.t. #738, if we end up merging that PR. But general idea should be to expose some http server that handles:

Returning current CPU/memory
Changing CPU/memory to desired values

This requires bumping the "runner version" to handle that.
We'd probably also end up getting rid of the QMP port from the VM spec — special care needs to be taken to gradually phase that out (+ make sure cplane doesn't set that for new VMs).

An alternative is to move the qmp handling logic into the VMLet abstraction (as discussed here. With this we can start moving VM management stuff into the VMLet. This change allows us to make runner simpler and keep it just as a runner. However, we have to expose QMP over the cluster but that's not a big issue and we can protect it using RBAC, for example.
Related idea: having VMLet allows us to do crictl stuff in one place. This way we don't have to mount containerd.sock into the runner pod and avoid complexities of managing two containers in the runner pod (ref: #738).

Do together with #716

Back-link: mentioned this issue here.


Links / UI layout that is referenced is outdated

The UI for the Exchange admin center has changed and the page no longer reflects the proper steps

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

ID: db2dbb29-38c4-afe4-bc0d-3bbc195f6288
Version Independent ID: bcfee113-ecfe-e358-974e-6f9cd76b8d35
Content: Create a shared mailbox - Microsoft 365 admin
Content Source: microsoft-365/admin/email/create-a-shared-mailbox.md
Service: o365-administration
GitHub Login: @SKjerland
Microsoft Alias: sharik

@RobvanB Thank you for your feedback. We have updated the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/6379

@msbemba Thank you very much for the contribution and updating the documentation with PR. @RobvanB Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Crash when extracting inner let rec in tactics

module Bug

open FStar.Tactics.Effect

let crash ()  : Tac int =
  let rec aux () : Tac int = 123 in
  let r = aux () in
  r

$ ./bin/fstar.exe Bug.fst --odir o --codegen OCaml | clip.exe
Extracted module FStar.Pervasives.Native
Extracted module FStar.Preorder
Extracted module FStar.Monotonic.Pure
Unexpected error; please file a bug report, ideally with a minimized version of the source program that triggered the error.
Failure("This should not happen (should have been handled at Tm_abs level for effect FStar.Tactics.Effect.TAC)")

Hit this today


Drop preLaunchTask in launch.json and npm run compile in test

https://github.com/Microsoft/vscode/blob/master/extensions/html/.vscode/launch.json#L21
and
https://github.com/Microsoft/vscode/blob/master/extensions/html/server/package.json#L30
It does not make sense to run the compilation each time when you are debugging, as the normal development work flow should be

run npm run watch as a task / terminal command
make changes
launch extension to see behavior or run unit tests

Having the compilation step adds 5-10s time to the last step which I want to do as frequently as possible. Same for /extensions/css.

Instead of relaunching, why not reloading [Extension Development Host] window? That's much faster.
Removing the prelaunch task just increases the chances that old JavaScript is used, or that the JavaScript is missing or doesn't compile.

The main problem was launching the compound debug of Client/Server often time out because it's waiting for the build.
I have changed compile script from && to & to parallelize the compilation, so it's done faster.
gulp compile-extension:html-language-features-client & gulp compile-extension:html-language-features-server

So at the end it's just using tasks or running the commands manually. I prefer the latter so I guess I'll just remove the prelaunchtask during development and not commit it.


Visual blocks

Visual blocks only go to solid blocks, not on blocks like water or slabs.
So for example claiming an ocean, you'll only see the visual blocks underneath on the sand.
It used to be on the higest block on the y coordinate corner, water in this case ^

Fixed in https://github.com/MinecraftPortCentral/GriefPrevention/commit/624fa61e165e903768e5288e613207dad28451be


Initial commit of the XSUAA node.js tutorial

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Generating Routes

will need to add @tanstack/router-cli to generate routes

route autogeneration should already be handled by @tanstack/router-plugin and @vitejs/plugin-react-swc. If you want/need to use babel, you should use @vitejs/plugin-react. As per the tanstack router documentation.


Switch UI to react WIP

[x] Unify react wip flow into repo
[x] Linting errors
[x] Allow running react version side by side with vue version to allow merging before full feature parity
[ ] Implement all flows

[x] Importers create/update/delete
[x] Importers enable/disable
[ ] Exporter settings

[x] Excel
[x] JSON
[ ] Ynab
[ ] Google sheets

[x] General settings (num scraping days and show browser)

Maybe in a separate PR:

[ ] Improve UX to match design
[ ] Solve ynap api issue and remove disabling of https check
[ ] Error reporting (sentry)
[ ] Analytics
[ ] Download Chrome progress
[ ] Remove vue

[ ] Switch to electron-react-boilerplate?
[ ] Replace electron builder vue
[ ] Remove view files and build

[ ] Check for updates flow
[ ] Monorepo

[ ] Separate to worskpaces (yarn workspaces? with lerna)?
[ ] Solve react dependency issue and remove SKIP_PREFLIGHT_CHECK hack

I don't think we have to match to the design. I think we need to focus on supporting the same functionality as before.
Any improvments can be done by other PRs. We have to break the change.

Added the option to switch between the vew and react ui so we won't have to wait for full feature parity in order to merge.
I think I will add the ynab settings implementation and then want to merge (defaulting the ui to the old implementation but allowing to switch).
@baruchiro  WDYT?
(Ignore the redness of the screenshots, that is not how it looks)

@brafdlog Yes, I think it is the best option. Once it will be merged we will be able to do small changes, and also contributors will see their effect.

@baruchiro there are more things I want to add but since this allows the option of switching between old and new UI I don't think we should wait any longer.
Would love to get your feedback

* What about keep the Vue UI as default?

I know the e2e tests are not so useful, but they are what we have. I think keeping the Vue as default will ignore the tests problem, for now, see if you prefer to solve the issue or avoid it for now.


5-2 missing a song

for 5-2, you only included the boss music. theres not an option to change the beginning part of "He Is the Light in My Darkness"

it'd just be adding "Ferryman Intro"

some songs, usually ambient ones or intros to boss songs, can't be replaced directly in ustmanager so they have to be replaced as a global sound.
cerberus intro (0-5), cerberus outro (0-5), the calm-only version of a thousand greetings (1-2), theme of cancer (1-2), in the presence of a king intro (2-4), theme of cancer (4-3), deep blue intro (5-1), the abyss and the serpent intro (5-4), chord of the crooked saints (6-1), fallen angel (6-2), the world looks white (7-1), theme of cancer (7-1), and bull of hell intro (7-1).
the intro for he is the light in my darkness just happens to be one of these.

if you wanna replace it the name for it as a global sound is "Ferryman Intro", but keep in mind this will replace all instances of it so custom levels that use the song will have it replaced, which could sound weird