cargo update

Motivation
refresh cargo.lock
Have you read the Contributing Guidelines on pull requests?
yes
Test Plan
Existing coverage
Related PRs

The ed25519-dalek: 1.0.0-pre.1 -> 1.0.0-pre.2 update is the only one that looks worrisome. If we have a guarantee that pre.1 is compatible with pre.2 then I think we should be ok to update things.

@bmwill  I don't think I'm capable to tell if it's 100% compatible, especially considering it is 8 months since last release.. @huitseeker you?
But anyway I think we definitely want to keep up with official releases as soon as possible?

@metajack added.

@msmouse I bring up my concern because the versions with have Major.Minor.Patch-Something aren't really semver compatible and breaking changes can occur when bumping to another Something version (e.g. look at the futures 0.3.0-alpha.XX crate and versions)

:umbrella: The latest upstream changes (presumably d2b27a12e8d6847b49dd6b8242989ee2d0b80ff4) made this pull request unmergeable. Please resolve the merge conflicts.

This will bitrot easily so I suggest using p=10 when you tell bors to land it.

I messed it up by trying to manually exclude the "ed25519-dalek 1.0.0-pre.2" change. Abandoning.


RuntimeError: Error(s) in loading state_dict - size mismatch for mel_spectrogram.mel_scale.fb: copying a param with shape torch.Size([1025, 128]) from checkpoint, the shape in current model is torch.Size([0]).

Not sure what's going on here, but I've submitted a code example:
import torch
import torchaudio

class Example(torch.nn.Module):
	def __init__(self, time_seconds: int = 1, sr: int = 16000,
		n_mels: int = 2**7, n_fft: int = 2**11, top_db: int = 80):
		super().__init__()

		self._time_seconds = time_seconds
		self._sr = sr
		self._n_mels = n_mels
		self._n_fft = n_fft
		self._top_db = top_db

		self._hop_length = int(self._n_fft / 4)

		self.mel_spectrogram = torchaudio.transforms.MelSpectrogram(sample_rate=self._sr,
			n_fft=self._n_fft, hop_length=self._hop_length,
			n_mels=self._n_mels)
		self.amplitude_to_db = torchaudio.transforms.AmplitudeToDB(stype='power',
			top_db=self._top_db)

	def forward(self, waveform: torch.Tensor):
		mel_spectrogram = self.mel_spectrogram(waveform)
		return self.amplitude_to_db(mel_spectrogram)

model1 = Example()
model2 = Example()

waveform_batch = torch.randn(1024, 1, 16000).type(torch.FloatTensor)

model1(waveform_batch[0]); 	# runs on one sample, no batch support!

model2.load_state_dict(model1.state_dict())

---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
<ipython-input-19-a8149d9091a8> in <module>
----> 1 model2.load_state_dict(model1.state_dict())

/opt/conda/lib/python3.7/site-packages/torch/nn/modules/module.py in load_state_dict(self, state_dict, strict)
    843         if len(error_msgs) > 0:
    844             raise RuntimeError('Error(s) in loading state_dict for {}:\n\t{}'.format(
--> 845                                self.__class__.__name__, "\n\t".join(error_msgs)))
    846         return _IncompatibleKeys(missing_keys, unexpected_keys)
    847

RuntimeError: Error(s) in loading state_dict for Example:
	size mismatch for mel_spectrogram.mel_scale.fb: copying a param with shape torch.Size([1025, 128]) from checkpoint, the shape in current model is torch.Size([0]).

Is there a workaround? Thank you

Hi. Are you using the latest master?  We recently pushed some code related to filter bank.

Hi @engineerchuan thanks for the response. I don't think it's that, but instead, related to https://github.com/pytorch/audio/issues/245

Thanks for reporting this, and providing a code snippet! I can reproduce on the last release, but on master the issue has been fixed and I get <All keys loaded successfully>. I'll close this issue, but please feel free to re-open if this continues on master.


How to set a other default group.

I know their is already a group called default and you start with it and I am wondering how I can set a other group to when they join, they are in it. Sorry if its in a doc but I can't find it

https://github.com/lucko/LuckPerms/wiki/Default-Groups

It shows what to do but I don't know where to put my default group name as my config is
rule1 {
if {
has-true="(<group.vip> | <group.vip+>) & <titles.tilecollector>"
has-false="<some.random.permission>"
lacks="<prison/group.prison_titlepack>"
}
give = [
"prison/group.prison_titlepack"
]
take = [
"some.random.permission"
]
}

Where do I put the default groups name?(Or whatever you would call it)

Wait may have found how to

Nope doesn't work I found this
rule3 {
if {
has-true="<group.default>"
}
take = [
"group.default"
]
give = [
"group.PokeNoob"
]
set-primary-group="PokeNoob"
}
}
(The areas where it says PokeNoob use to say member)

Groups are stored in lowercase. Try it with "group.pokenoob" and set-primary-group:"pokenoob"

It works, thank you!


How to get version of LiteDB?

Hi! I need to know which version of LiteDB is in my project. Is there any field property in LiteDatabase class?

@Garon147 You could do something like this:
string version = typeof(LiteDatabase).Assembly.GetName().Version.ToString()

@lbnascimento try this but it just returns "<IP_ADDRESS>"

@Garon147 This is weird, it should work even for really old versions of C#. What do you get for typeof(LiteDatabase).Assembly.FullName ?

@lbnascimento it returns this Assembly-CSharp, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null

@lbnascimento also I use unity package, maybe that's why it returns <IP_ADDRESS>


[Jetsurvey] Converted to use Material 3

All Compose components now use Material 3 instead of Material 2. The date picker is currently still using the MaterialDatePicker DialogFragment the same as before this change. This also fixes the visibility of the status bars when in light mode.

Found a few more issues that I'm working through now

It's looking much closer now! Please take a look

A few minor comments left (and some things to possibly address based on our email thread) but it's very close! Friendly reminder to please include screenshots in the main description :)


Integrate github actions into Haaukins project

Is your feature request related to a problem? Please describe.
Not exactly, will add ability to test and deploy all binaries with Github's CI.

[x] Run test cases
[x] Build binaries
[ ] Deploy to server

deployment phase left can be observed github-actions-test


Add optimized spack recipe for WRF on hpc6a

Install Spack v0.20
 export SPACK_ROOT=/shared/spack
 git clone -c feature.manyFiles=true -b releases/v0.20 https://github.com/spack/spack $SPACK_ROOT
 echo "export SPACK_ROOT=$SPACK_ROOT" >> $HOME/.bashrc
 echo "source \$SPACK_ROOT/share/spack/setup-env.sh" >> $HOME/.bashrc
 source $HOME/.bashrc

Add Spack cache
spack mirror add v0.20.1 https://binaries.spack.io/v0.20.1
spack buildcache keys --install --trust

Install WRF 4.4.2
spack compiler find
spack install<EMAIL_ADDRESS>build_type=dm+sm


Brand Bar background color visible with custom Nav color

This is apparent especially when you choose the Nav color to be white as there is a thin black line across the bottom.

Fix for this is implemented in the T3 project. The default color is overwritten via the custom branded css that's passed down via platform.
https://github.com/Tier3/T3/commit/342b91d43fe67fc05b60dadf7fc0e8fd21851248
fyi: @osbornm


[ARCTIC-1611]For flinkcontainer optimizer, When making a connection v…

issue: https://github.com/NetEase/arctic/issues/1611
Why are the changes needed?

Brief change log
make  https://github.com/NetEase/arctic/pull/1612  change into 0.4.x
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before making a pull request

Documentation

Does this pull request introduces a new feature? (yes / no)
no
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
no

LGTM


Snow Flake on vscode insiders and pushing death is very offensive to me

The Snow Flake on vscode insiders and pushing it as a "cozy"/"wintery" thing is very offensive to me. I come from Norway and people who glorify snow is equivalent to the people who glorified hitler during WW2. The amount of deaths caused by winter is massive, not to mention the depression the season brings and you want to bring that into my work space as well? This is unacceptable, everytime I leave my house I see snow and I want to escape into Visual Studio Code and get some work done and what do I see? More snow... To me this is equally offensive as a swastika.
This isn't just me either, think about the people who cannot even get snow, think about how you're making them feel, making them see what they cannot get, although personally I don't understand that. Snow is terrifying.
Version: 1.42.0-insider (user setup)
Commit: 26f5dfc
Date: 2019-12-19T05:31:04.916Z
Electron: 6.1.6
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Windows_NT x64 10.0.18362
Steps to Reproduce:

Install latest build of insiders.

Does this issue occur when all extensions are disabled?: Yes
Additional reading on the issue that most certainly needs to be considered.
https://thoughtcatalog.com/jim-goad/2015/12/death-by-snow-14-ways-that-winter-weather-can-kill-you/
https://www.nrdc.org/stories/global-warming-101
https://www.recoveryranch.com/addiction-blog/snow-depression/

This is really offending for people that are suffering for global warming and desertfication areas.
Also It Is that a natural snow icon or a fake snow icon.
Please think about how much water Is wasted to create artificial snow just for games:
https://news.bloombergenvironment.com/environment-and-energy/fake-snow-for-china-olympics-needs-49-million-gallons-of-water

This is also highly offensive to everyone who has ever been called a snowflake or identifies as a snowflake.
Please remove.
https://en.wikipedia.org/wiki/Snowflake_(slang)

Perhaps this is not the correct platform for trolling?

No? Perhaps it same level "trolling" as https://github.com/microsoft/vscode/issues/87268 ?
Racism is the belief in the superiority of one race over another.[1][2][3] It may also mean prejudice, discrimination, or antagonism directed against other people because they are of a different race or ethnicity.[1][2] Modern variants of racism are often based in social perceptions of biological differences between peoples. These views can take the form of social actions, practices or beliefs, or political systems in which different races are ranked as inherently superior or inferior to each other, based on presumed shared inheritable traits, abilities, or qualities.
So removed santa hat is racism. Just because its offended for one person, microsoft prejudice, discrimination, or antagonism directed against other peoples

ДБ?

@braindigitalis It Is not trolling Is that when MS apply too extreme "politically correct" reactions it Is healty if the community react with a little bit of satire.

Also, seems, censoring everything just keep self "clean"

We could make the snowflake toggable https://github.com/microsoft/vscode/issues/87333 :smile:

If it was possible to just turn the slowflakes off, this whole debacle wouldn't happen :thinking:

It is really offending me because I am very snow sensitive and get hurt by snowflakes when it is snowing.
If I see that on the VS code I feel physically hurt.
So remove it immediately like you did the other thing.

Not to say that many Jews died when it was snowing outside.

On the other hand snowflake is the best symbol for spineless corporations bowing down to any random activist complain.

Also there was some recent effort to associate snowflake and Santa with its red hat to drug consumption so please don't talk about Its red hat and snow simbolol in the same thread.
https://www.vice.com/en_us/article/jgee9k/amazon-is-still-selling-festive-christmas-sweaters-showing-santa-doing-cocaine

I am with you guys- the one troll that offended many, many people got his wish filled.

If you do not like VSCode, do not use it. The simpliest solution!

@daniel1302 Please stop offended me! You're not my dad, I can use everything I like / dislike!

@PierreRambaud I am happy you are not my child.  @Christian-Schiffer created enough havoc already.

@daniel1302 ok boomer

So, interesting to see that this issue is actively watched but the only thing what happens, is that two posts were deleted instead of instapromptu removing the hurtful snowflake from the application, like the other thing.
I'd be really  grateful if that the correct reaction will be delivered like the other one, snowflakes do hurt and sting in the eyes, I won't be able to sleep if I see all day this hurtful symbol of pain in my IDE.

Some guy in Microsoft HQ is sweating right now.
Although this is 100% deserved.

His name is Christian, that must be a troll account, too good to be true :D

If you need further reference why snowflakes remind me of cold, pain and hurt see:
https://www.aao.org/eye-health/diseases/photokeratitis-snow-blindness
https://www.webmd.com/a-to-z-guides/news/20110120/snow-shoveling-injures-thousands-each-year#1

I'm from New Zealand, and in the Southern Hemisphere, it's not cold, but hot during the holiday season. I suggest you geo-locate the user's position and prompt them for the icon of their choice, e.g. snow, ice, fire, sun shine.

BTW. To original author of this shitstorm - Christian-Schiffer. W wonder is his name not offending him?
https://en.m.wikipedia.org/wiki/Christian_(given_name)
Maybe he should change it...

Every Christian should be renamed immediately to eliminate possible offence. The name should be strictly prohibited for future use.

https://en.wikipedia.org/wiki/Snowflake_(slang)

Can you people stick on topic? This is a serious discussion about the terror that is snow flakes and how it terrorises a lot of people everyday, even more now with the new VS Code update.

I would also like to point out that snow(flake) is white and is commonly used as a white supremacy symbol to oppress whole ethnicities which due to systemic geographic discrimination couldn't historically experience first-hand full range of weather phenomena.

Winter is one good buff against invaders in Russia. Praise the winter! Let it snow!
Also I think climate calculations are wrong and new ice age is nearby. There will be more snow. Thank you global warming fighters, for helping to make even more snow!

Thanks for creating this issue. We think this issue is unactionable or unrelated to the goals of this project. Please follow our issue reporting guidelines.
Happy Coding!


pull sync: implement protocol only

This PR:

import bitvector from swarm
add db close channel to SubscribePull to signal db closed when iterator returns
implements only the dumb protocol that handles the message exchanges
implement pullstorage module that wraps storage.Storer and handles basic operations of getting, putting, setting chunks from the localstore in return for requests coming in from the protocol

Next PR:

implement puller component that actually initiates requests to the protocol to retrieve intervals for certain peers
possibly under puller or another component to prioritize and decide which peers we want to sync with

Looks good to me as well so far, no special comments. I will wait for ready for review, and go through it again once is ready for review. I agree about bitvector that it could be separate PR, but also I don't think this PR is huge, as @janos said, large part is auto-generated code, so it's seems fine!

thanks guys. I removed the deliberate panic in an earlier commit today. i now also removed the implicit methods of Has and Set. I left the Get that invokes GetMulti and the Put, but yeah we can also get rid of those too. I could maybe take care of it when the other PRs are merged into this one? just don't wanna deal too much with rebasing one on top of the other.


Update PPP for Jia Le

Add PPP for jiale-c.md for individual component of week 7 tP tasks.

Codecov Report

Merging #28 (55ab3d2) into master (755a636) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #28   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

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 755a636...55ab3d2. Read the comment docs.


propsToPass.ref = 'wrapped' is incompatible with React Storybook

Are you submitting a bug report or a feature request?
Bug report
What is the current behavior?

Create a React Storybook with https://github.com/storybooks/storybook
Create a class component, and wrap it with Redux Form
Create a story in your storybook that renders this Redux Form-wrapped class component at the top level
React will throw Element ref was specified as a string (wrapped) but no owner was set.

What is the expected behavior?

The wrapped component should just render without throwing an error

What's your environment?
Redux Form 7.2.3
React Storybook 3.3.14
Other information
A workaround for this bug is to wrap the class component in a functional component before wrapping it with Redux Form. For example:
class MyComponent extends React.Component { /* ... */ }

const MyWrapper = (props) => <MyComponent {...props}/>

export default reduxForm({ /* ... */})(MyWrapper)

This causes the if (isClassComponent(WrappedComponent)) check in createReduxForm to return false, and thus the string wrapped won't be passed as a ref.

Can you create a failing test case for this, and submit it as a PR?

I am facing the same issue with class component but working fine with functional component. Any plan on when bug will be fixed?


IE pipes, IE barrels, fluid funnels, fluid funnel's taps, ceramic's faucet and channels, cant interact with the cauldron properly,

forge: <IP_ADDRESS>14
ceramics: 1.3.6
immersive engineering : 0.12.89
inspirations : 0.2.3
fluid funnel : 1.3.0
im not sure if it's something ive done or simply not included but for the last couple of weeks less and less mods have been able to interact with the cauldron
I have it set enabled for potions, and bigger inventory,
but only the immersive engineering pump can input and output properly on the cauldron in my pack

Yes, this is an issue described in the cauldron fluid handler logic, you must fill in 250mb increments. Ceramics does 10mb. If you need to, use a dispenser to fill them.


Order Hall Missions and Artifact frames need to be skinned

Currently using the default blizzard skins.

so are profession frames fwiw


Housekeeping

Just wondering is there a way to delete unique properties related to a movie if I delete the movie? I mean that if I delete the movie "The Raiders of the Lost Ark", it would be reasonable to delete all pages (properties) that were created when I entered the movie in the first place. Provided that they are not used elsewhere in the graph. I don't know if Logseq has an in-built way to do this, an advanced query maybe?

If you want to delete a movie, you may need to navigate to the movie page and click on "delete page" to remove the page itself. After that, you can delete the corresponding movie entry. These actions are part of Logseq's functionality and are not within the scope of the plugin.


Update manual installation steps

@CawaMS

@northtyphoon,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@northtyphoon : Thanks for your contribution to the Azure documentation! The author, @CFreemanwa, has been notified to review your proposed change.

#sign-off

#sign-off


Use more descriptive accessible headings for search result pages

Fixes

Fixes https://github.com/WordPress/openverse/issues/790 by @alexstine (by way of @zackkrida extracting the issue from a tracking issue of several required accessibility fixes)
Description

The large number of added lines come from snapshot tests, not actual code changes. See the testing instructions section for details about these.
The PR adds new sr-only text to the page, as suggested by Alex in the issue. I've chosen to use different variations based on the search type and count of media. In my first attempt, I used two separate h1s. However, this caused an issue with introducing unintended height. Rather than adding additional classes to the second one to prevent that, I decided to just put them inside the same h1, with each bit wrapped in a span so I could mark them as aria-hidden or sr-only as needed. This appears to work in all my testing (ORCA on Linux, NVDA on Windows and VoiceOver on macOS, the latter two in VMs), but please try to break this to make absolutely sure I've got it right.

For "all-media" search types, the string is "All results for {query}, {imageResults}, {audioResults}" where the image and audio results are either "No images/audio", "{count} images/audio", or "Over 10000 images/audio". This means the title will inform that the query was for all media types, and the count of results for each media type. That might be too tedious, compared to a unified count, I'm not sure.
For individual media types, the string is either "No image results for {query}", "1 image result for {query}", "{count} image results for {query}", or "Over 10000 image results for {query}" where "image" can be either image or audio depending on the search type.

Testing Instructions

Run the application locally using just p frontend dev from the root directory of the repository.
Execute a search from the homepage, and using a screen reader, observe the h1 of the page. Confirm it meets the requirements laid out in the issue.
I used snapshot tests rather than individual assertions for each possibility of the accessible text because otherwise I would have to duplicate the translation, which isn't the point. Ideally this would use a diff snapshot test, render a couple "baseline" variations, and then snapshot diff against those to confirm they are all different in code, but you can do this by reading the snapshots themselves. This is a small component, so the snapshots are not too cumbersome.
I wanted to use inline snapshots, because I've found those easier to work with in the past. However:

You cannot use them in an each test
Our trailing whitespace pre-commit fix kept trimming whitespace present in the one that isn't in the each block, and I was worried about how many different formatting issue's I'd need to fight against overall. We should disable that trailing whitespace check for anything linted by ruff, prettier, or eslint, though, as it's just duplicating those tools and is less configurable in cases like this... plus, in this case, it was modifying a string literal in the code, which is no good!

Anyway, that's out of scope for this issue. I just wanted to explain the decisions I made there.
Checklist

[x] My pull request has a descriptive title (not a vague title likeUpdate index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[x] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no visible errors.
[N/A] I ran the DAG documentation generator (if applicable).

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@sarayourfriend, I'm drafting this PR to prevent pings while the comments on prettier and snapshot changes are addressed.

@obulat @dhruvkb This is ready for review.

A few snapshots need updating after the merge of #3967

I had to squash this PR, the back-and-forth commits were making rebases a pain. I should be able to merge this now so long as CI passes, there are no changes other than updates to the snapshots that Zack mentioned.


Fixed wrong ask usage examples.

As discussed in #1758

I would also mention something like this:

Note that ask itself does not prompt the user immediately. The question is deferred until the first time fetch is used to obtain the setting. That means you can ask for many variables, but only the variables used by your task(s) will actually prompt the user for input.

The way the examples are written right now it is implied that ask immediately displays a prompt, which is not the case.

Ops, I forgot to remove the redundant set usages.
Done now. Also added the info about ask waiting for the first fetch to actually ask the question. I didn't know that to be honest :-) So, yes, it is good to point that out in the docs.

Looks great, thanks! 🎉

:tada:


SSL certificates expired

I think the SSL certificate that gets bundled here has already expired.
So using --https won't work anymore on Chrome for example.

ahh, yes - thanks for reminding me! Will fix that ASAP with a new cert with longer expiry time.. watch this space..

Fixed in lws v1.1.3 and local-web-server v2.2.3. You may need to mark the new certificate as trusted, sorry about that.
Let me know if you find anything else 👍


HelmChart type resources cannot be deployed when clusternet-agent sets AppPusher=false

What happened:
I have a child cluster and cluster-agent is started in Dual mode with AppPusher=false, then pull mode is used for application deployment.
        - --cluster-sync-mode=Dual
        - --feature-gates=SocketConnection=true,AppPusher=false,Recovery=true,Predictor=true

and i found Generic resources can be deployed normally, but HelmChart type resources cannot be synchronized.
What you expected to happen:
When the child cluster uses pull mode, HelmChart type resources can be deployed normally.
How to reproduce it (as minimally and precisely as possible):
sub resource is as follows:
apiVersion: apps.clusternet.io/v1alpha1
kind: Subscription
metadata:
  name: test
  namespace: test
spec:
  clusterTolerations:
  - operator: Exists
  feeds:
  - apiVersion: clusters.clusternet.io/v1beta1
    kind: HelmChart
    name: test
    namespace: foo
  schedulerName: default
  schedulingStrategy: Replication
  subscribers:
  - clusterAffinity: {}

The description and HelmRelease are automatically generated by the deployer.
Anything else we need to know?:
Upon examining the code, it was found that if AppPusher is set to false, the HelmRelease will not be updated. This causes the cluster-agent to be unable to watch for changes in HelmChart, and thus no updates are made.
This issue is caused by improper handling in the handleDescription function of the controller. The code can be found here.
Why there is such a limitation here, and can this limitation be lifted?
	if !*mcls[0].Status.AppPusher {
		deployer.recorder.Event(descCopy, corev1.EventTypeNormal, "", "target cluster has disabled AppPusher")
		klog.V(5).Infof("ManagedCluster with uid=%s has disabled AppPusher", mcls[0].UID)
		return nil
	}

	if err = deployer.populateHelmRelease(descCopy); err != nil {
		return err
	}

Environment:

Clusternet version: master

i found Generic resources can be deployed normally, but HelmChart type resources cannot be synchronized.

Currently helm charts are deployed solely by clusternet-controller-manager.

Why there is such a limitation here, and can this limitation be lifted?

You can try to mitigate this.


Manually close the ContentDialog in teardown

As discussed. Closes #15364.
Prevents one crash on Windows 10. Opens the door to may more horrors.
Co-authored by: @j4james

You will need to use the Signed-off-by: Name <e-mail> format when you actually merge this


[Select] Make outlined variant the default one

Change the default variant from standard to outlined. Rationale in Material Studies: Text Fields. Done for TextField in #23503.
Contributes to: #20012
Checklist:

[ ] Change the default variant of the Select component
[ ] Change the default variant of the NativeSelect component better be done in a separate PR, not a small thing, IMO
[ ] Update the Select docs
[ ] Review the variant usage of the FormControl and see if it is safe to change it
[ ] Entry in the migration guide
[ ] Change docs/pages/api-docs/select.json (or maybe it is generated?)
[ ] In the docs, remove all explicit variant="outlined" props
[ ] Where necessary, add variant="standard" to selects who had no variant before
[ ] Codemod like this + test
[ ] Review tests
[ ] Review <TextField select>

@mbrookes - please let me know if I am missing something from the above. FWIW, the biggest inconvenience of the outlined Select is that the label prop value should match the InputLabel text.

[x] I have followed (at least) the PR section of the contributing guide.

FWIW, the biggest inconvenience of the outlined Select is that the label prop value should match the InputLabel text.

True. I think that most developers use the composed version (). It's handled for them. We have #21782 to better solve this problem.

Change docs/pages/api-docs/select.json (or maybe it is generated?)

yarn docs:api will take care of it

Codemod like this + test

Or modify it to support both use-cases

@mbrookes @oliviertassinari I need your advice on how to scope this changeset. This change seems to be triggering multiple related ones. Here's what I am seeing so far:
The Select component obtains its default variant from the parent FormControl, which is "standard" atm. Based on the examples, I assume that a significant amount of users wrap Select in FormControl.
With that in mind, I see two possibilities:
A) Change the default variant of the Select, and leave the FormControl change for a follow-up PR. Smaller and safer, but to put it simply - won't do much, apart from the users who use it without a FormControl. This approach also raises the question of what should be done for the docs page - should all FormControl wrappers get variant="outlined"? Or should we count that the follow-up PR will take care of that?
B) Change the default variant of FormControl to "outlined". This is what I have been exploring so far, but it ripples through several areas - see the argos build failure. The variant change affects the default look of FormHelperText and InputLabel. It also subtly breaks such compositions:
<FormControl ...>
... <Input />
</FormControl>

From what I see, for the above to look correct, Input should be replaced with OutlinedInput.
Maybe there's C) another approach?
FWIW, I am very supportive of outphasing the "standard" variant of selects and inputs. It definitely feels like a usability mistake in hindsight.

B) Sounds like the best way to go. It does involve diving into multiple parts of the codebase.

@petyosi How is the effort going? Did you face a blocker?

Hey, sorry for the delay, Working through the screenshot differences, I will push an update for review this week.

whether the standard variant should still be named standard as it is not a default value.

@mnajdova If I recall correctly, the name originates from when we introduced the filled, and outlined variant. It likely has this meaning:

a pattern or model that is generally accepted:

https://dictionary.cambridge.org/dictionary/english/standard
It doesn't age well if it's not the default, agree. Should it be enough to make a breaking change? I guess we have to weigh the cost. cc @mbrookes. In any case, I think that it's outside the scope of this PR and should concern a potential follow-up. Personally, I think that it would cost a lot for some value, maybe not enough.

I think that it's outside the scope of this PR and should concern a potential follow-up. Personally, I think that it would cost a lot for some value, maybe not enough.

Agree, it is definitely out of the scope of this PR, just thought to mention it as we are making the changes now. So far developers were never typing variant="standard", as it was the default value. Now that it is not a default value, they would need to add it, so my thought was instead of adding variant="standard", they could add variant="underlined". But on the other hand, I get that it may not be work the effort, but let's at least consider it before making the final decision.
Let me update the branch with the latest changes, so we can take a look on the changes & visual regressions better.

One more BC done 🙏


QR code doesn't properly render on Windows

I'm opening this issue because:

[x] I have found a bug
[ ] I want to request a feature
[ ] I have a question
[ ] Other

the qrcode is too big!!!
When I zoom the  cmd window, the QR code disappears.

My Go version is: (paste the output of go version and remember that qrcp requires at least version 1.8 of Go)
My GOPATH is set to: (paste the output of echo $GOPATH)

Hello @jianboy, thanks for reporting!
Please allow me some time to research why the qrConfig.HalfBlocks = false was introduced in the first place, and then plan a solution.
Does it work fine for you if you set qrConfig.HalfBlocks = true?
Thanks,
C

Hello @jianboy, thanks for reporting!
Please allow me some time to research why the qrConfig.HalfBlocks = false was introduced in the first place, and then plan a solution.
Does it work fine for you if you set qrConfig.HalfBlocks = true?
Thanks,
C

I set qrConfig.HalfBlocks = true ,
and qrcode is flat.

@Lorenz11x are you having this issue in Windows?

it maybe cause by the bug:
https://github.com/mdp/qrterminal/issues/20

@claudiodangelis  si, in Windows10.
Soluzione?

We just deployed a new version, 0.6.1, which uses a different QR encoding library (props to @anoop-b :tada:).
Can you @Lorenz11x and @jianboy please try the new version and let me know if it fixes the issue?
Thanks,
C

It can not show qr correctly. May be you can open a file with a default software and not show it in cmd windows.

@jianboy just wondering: does it work with a monospace font?

@jianboy just wondering: does it work with a monospace font?

monospace font? I didn't know how to try it.

it works on monospace not others,i have the same problem with poster.

I can confirm that it works well in powershell on windows and cmd. But qr-code disappears after cmd window is resized.
Also works well on the new windows terminal. I think Microsoft is addressing these underlying issues with the introduction of new terminal.

Hey @jianboy , I couldn't reproduce this issue with the new build. Could you try doing a fresh install of qrpc?

Hey @jianboy , I couldn't reproduce this issue with the new build. Could you try doing a fresh install of qrcp?

sure, you can see my video:
http://cdn.yoqi.me/direct/2020-05-01/Video_2020-05-01_044740.mp4

I can confirm that it works well in powershell and cmd on windows . But qr-code disappears after cmd window is resized.
Also works well on the new windows terminal. I think Microsoft is addressing these underlying issues with the introduction of new terminal.

Hey, I also use Windows terminal, but the QR code cannot be displayed properly
go version go1.14.2 windows/amd64
Font: CaskaydiaCove Nerd Font Mono

I think it should be related to the font. I can display it normally with FuraCode Nerd Font Mono

Thanks everyone for reporting. In my understanding, the issue with the QR in Windows is always related to the font used in terminal, either it is not monospace or line spacing is too high.
Since this is not really an issue with qrcp itself I'm considering closing this issue in a few days.

run this qrcp.reg:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Console%SystemRoot%_system32_cmd.exe]
"CodePage"=dword:0000fde9
"FontFamily"=dword:00000036
"FontWeight"=dword:00000190
"FaceName"="Consolas"
"ScreenBufferSize"=dword:232900d2
"WindowSize"=dword:002b00d2

Hello @rongzedong, thanks for this tip.
Is there anyone in this conversation who can successfully resolve the problem by using the specific configuration as per @rongzedong suggestion?
Thanks

I don't want modify registry. I tried another way.

Can somebody on windows please test if this works ? PR

Hello everyone, we released a new version, 0.6.4, which adds the option to open the QR into a browser window:
qrcp --browser MyDocument.pdf

This can be useful for those running into rendering issues in the terminal.
Cheers,
Claudio

I developed a software to realize this function.

Oh that's great!

By the way, since I'm not hearing anymore about this issue, I will close the ticket for now.
Thanks everyone!

我开发了一个软件来实现这个功能。

请问你的QR sednto未发布吗？


Fix compinit to reproduce zcompdump when it needs

Follow-up of #104. See https://github.com/zplug/zplug/pull/104#issuecomment-222701579.

Thanks!


Failed: Update autorest version to prerelease 3.0.0-alpha.20240827.1

Generated by Autorest Regen Preview build 20240827.1Triggered from pull request: https://github.com/Azure/autorest.csharp/pull/5014

API change check
API changes are not detected in this pull request.


SyntaxError: Unexpected token 'export'

Seen from export default every;

For v0.1, just ignore export. For v0.2 we need to make it actually work.

Turns out ignoring export is about as hard as converting everything to module.exports, which is what we will need to do anyway.

Fixed


Universal Blue Sericea distrobox permission errors

What happened?
Hello,
After freshly installing universal blue sericea, it looks like distrobox is not working properly. I can create a container, but when I try to enter it, I get this error: Error: unable to start container "d26a061e9e53e15393c42ea7a6c2fa78268bd33d72e6d43d2c75ba4384c337de": crun: make /var/home/brandon/.local/share/containers/storage/overlay/daaf476633d847190290c64911628ba7c330918ed23e5ba400b4558cc48000f9/merged private: Permission denied: OCI permission denied
This is also not a bug from the ISO per say, as it looks like this happens when migrating a fedora sericea install. I have not tried the official universal blue iso.
Relevant log output
No response

hmm, for me it's working just fine, and just like you I rebased from a fedora sericea install. Are you on :latest?

No, I rebased to fedora 39. Let me rebase to :latest and see (I guess I don't know the difference between the two).

Okay, I rebased to :latest and I am still having this issue.

It seems this is affecting podman as well, as I can't start a container with it as well. It get the same error: Error: unable to start container "fb0631f2e02535c35f599873526daeed4adfad08b5fed87ca1338ba2551ed12a": crun: make /var/home/brandon/.local/share/containers/storage/overlay/d42cba2791b52073031974e106424fbaa669feac5dcfbbada8c7fa4e21128ea5/merged private: Permission denied: OCI permission denied

I didn't know what to do to fix this, so I went ahead and reinstalled, with silverblue as my image, universal blue directly from the official iso and it all worked great. I don't know what the issue was, maybe something of a bad install. I'm not sure, but I hope it never happens again and no one else is plagued by this.


Re-enable ngsPETSc tests

1f7a3f0c412eaa2c3654afd9fd45020f5f9ec4ea has disabled the  ngsPETSc test notebook, even when running with real numbers, due to https://github.com/NGSolve/ngsPETSc/issues/33
Revert when the upstream issue is solved.

MPI wrapper is now off by default, see https://github.com/NGSolve/netgen/commit/1e7624c7f589cd08c7915a73a10da665a8cc4eec, and thus ngsPETSc tests can be re-enabled.


Readme update for clarification

I thought the README might benefit from some formatting and cleaning up.

Sounds about right.


Quickfix action to prefix unused terms with '_'

This resolves #843

Can you please add a test for this?

Of course!

@alanz @lorenzo should we turn on Haskell CI's CircleCI for PRs? I think it may currently only be running on our own individual accounts

I thought it was already on!

Might be set to run PRs only after they are accepted?

I thought it was on already

The circle ci issue was on my part. I had tinkered with it on my fork. And apparently if you watch a fork it dosen't build for PRs to upstream.


[Bug]: Cannot find module 'puppeteer-core/internal/common/DeviceDescriptors.js'

Bug description
Steps to reproduce the problem:
Ubuntu 20.04.4 LTS (GNU/Linux 5.4.0-110-generic x86_64)

npm i puppeteer --save
create script from source https://github.com/checkly/puppeteer-examples/blob/master/1. basics/screenshots.js
node test.js

Puppeteer version
19.0.0
Node.js version
v10.19.0
npm version
6.14.4
What operating system are you seeing the problem on?
Linux
Relevant log output
Error: Cannot find module 'puppeteer-core/internal/common/DeviceDescriptors.js'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/var/www/tariffer/node_modules/puppeteer/lib/cjs/puppeteer/puppeteer.js:33:14)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)

@elephantux we don't support Node 10, could you try with Node 14 at least.

This helped, but now the script crashes on this error:
Error: Failed to launch the browser process!
[1018/083524.552398:ERROR:zygote_host_impl_linux.cc(90)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.

@elephantux do you run it as root?

@elephantux do you run it as root?

I think so. I run php unit test via ssh and logged in as root

Then you should do like the message says: 1) either run as a non-root 2) or add --no-sandbox for the launch args. I recommend running as a non-root user.


Extend Bezier and Line to support IFlip

Extends the Bezier2, Bezier3, Line2, and Line3 shapes to support IFlip. This can be a nice convenience function if iterating from 0 to 1 using g/point-at, allowing changes along the line to happen in reverse.
Adds basic test cases to verify behavior using g/point-at and g/flip.
Thanks again so much for creating such a useful library.

Oh thank you @dgtized! These are helpful additions indeed... will try to push a new version asap (but have to read up first how to do that w/ clojars these days)


Fix instructions to run locally

Description

I had to set DB_USER seperately for the DB migrations to run.
I had to copy over the settings.yaml file because it wasn't created by default.

Hi @kiwiidb thanks for your contribution.

This better?

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1167

Relevant Lines:
1951

💛  - Coveralls


Songhai society to language mapping

It may also be necessary to just double check Songhai SCCS24, xd480. Some of the ethnographics might be describing other varieties that are not Zarma-Kaado.
Harald wrote:
RE Songhay, quite possibly Zarma is the best match but looking at the source titles (I don't have the fulltexts handy) I think the SCCS sources listed may also have datapoints from other Songhays in Mali. Might be good with an actual check of the ethnographic sources.
Kate wrote this in the current document:
Note 8Feb2018: Changed after HH questioned whether specifically Hombori; SCCS notes specify that focus is ""The central Songhai at the bend of the Niger"" [in southwesternmost Niger, i.e. Niamey area]. Appropriate match is therefore Zarma-Kaado.

This is an ambiguous case., as I believe many of the main sources of the SCCS discuss the Songhai 'people' as a broad group with many subgroups. However, after more searching I do believe a better match would be:
koyr1242 - Koyraboro Senni Songhai (alternative name: Gao Songhai)
or possibly
koyr1240 - Koyra Chiini Songhay (alternative name: Songhai of Timbuctu)
Why:
-SCCS pinpointing sheet states the focus is on the "Bamba, or central division" Songhai at the "bend in the Niger" - I took this to be the area around Niamey on my last read, but in fact it should be in Mali, possibly centered on the town of Bamba (17°02′N 1°24′W)
-Wikipedia describes Bamba as "a small town and rural commune in the Bourem Cercle of the Gao Region of Mali. The town is located on the left (north) bank of the Niger River, 190 km east of Timbuktu and 230 km northwest of the town of Gao. The commune of Bamba includes 19 villages and 7 nomadic population groups. The population are primarily Songhais but also Tuaregs and Bozos."
-Bamba falls between the primary field sites of the two anthropologists whose field work dates were used to select a focal year of 1940 for the Songhai case in the SCCS: Timbuktu (H. Miner) and Ayorou (J. Rouch)
Jean Rouch's work focused on the Songhai in general - for example his 1960 book discusses the influence of Songhai subgroups (Sorko, Gow) and neighbouring  non-Songhai groups on Songhai religion.
Wikipedia describes one of Rouch's primary field sites as the town of Ayorou, on the Niger-Mali border, 208 km northwest of the capital Niamey
Regarding the possible match to zarm1239 -- both popular (wikipedia) and formal (academic book reviews) descriptions of Rouch's work often mention his interest/work on the "Zarma and Songhai"
Rouch, J. 1954. Les Songhay. Paris.
Rouch, J. 1960. La Religion et la Magie Songhay. Paris.
Miner's book focuses on three ethnic groups in the town of Timbuktu, one of which is the Songhai. ["The Primitive City of Timbuctoo is a report of the life and customs of three major ethnic groups living in this ancient city, as seen by Mr. Miner during a seven months' residence there. The three groups studied were the Arabs, the Songhoi, and the Taurey. The author shows that each of these groups casts its influence upon the religion, customs, mores, education, and life in general of all its inhabitants, e.g., Arabs on Songhoi and vice versa. [...] The author gives a clear picture of the geographical location of Timbuctoo and the surrounding countries and a very vivid and picturesque description of the marriage and divorce customs of each of the groups. He likewise furnishes interesting details and other information of birth customs, birth rates, death, and burial practices of each of the great groups, reporting numerous of their beliefs in life after death, the types of spirits believed in, and methods of controlling or appeasing the evil spirits."
Here is a bit more detail on how the architects of the SCCS viewed Songhai divisions: (from the society's SCCS pinpointing sheet (Murdock and White, 1969)):
The Songhai are divided into:
(1) the Bamba (Central Songhai, centered on the bend of the Niger River in Mali -- this group is the focus for the SCCS "as they are the best known to history"),
(2) the Kadobi (eastern Songhai, around Tillabery), and
(3) Galibi Arb (western Songhai, around Goundam and Niafunke).

Thank you so much @kirbykat ! I know it takes time to go through and investigate this.
Lucky for is in GB, we already have koyr1242 and koyr1240 :D!

Done as part of #183


feat/HDH-95

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[ ] Issue
[x] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[x] Tested Locally
[x] Optional Screen Shoot.

The urls would be like:

/certifications/?lvl=developer
/certifications/?lvl=administrator
/certifications/?lvl=architect

Also hid the number of Certs in the Cards if "numberOfCerts" was not specified.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Great solution @wei-harness. Hmm though when clicking on https://642dadaf47a4460fca964c4f--harness-developer.netlify.app/certifications/continuous-integration/?lvl=architect, does not bring up the Arch Tab. Not sure if there is a way to enable that.

Great solution @wei-harness. Hmm though when clicking on https://642dadaf47a4460fca964c4f--harness-developer.netlify.app/certifications/continuous-integration/?lvl=architect, does not bring up the Arch Tab. Not sure if there is a way to enable that.

Should be fixed now.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Windows 11 10.0.22000.21876 not supported

Please, attach your RDPConf screenshot and termsrv.dll.

Closed because the requested information was not provided. Without it, the issue is invalid.


Change the font color of the paragraph in the card

The features section on the website shows features through card. It consists of an h3 and a paragraph. What I observe is that the font colour of both the elements is the same thus I am not able to derive an hierarchy.
It will be great! If we can make the paragraph a little bit greyish so that we can see the hierarchy and skim through it with just reading the key points.
Before:

After:

I used #5E6573.

@tommoor, please let me know your thoughts on this.

Works for me, I think it's a good improvement 👍


Adds Pred API

Coverage remained the same at 100.0% when pulling 068843a1d8ca84a29e577162b6a57ce5231bf130 on rstegg:pred-api into b431fcf4b522542f307d2a55366381d46ffee9f4 on evilsoft:docs.

Coverage remained the same at 100.0% when pulling a202b02cf923a336930637f7d63e34f3a013340c on rstegg:pred-api into 6c72ddeb887fb1deaec186b02f75376f8aacbe89 on evilsoft:docs.

Thanks! Your review has cleared up a lot of lingering confusions.


allow bold/italics/links via text "entities"

can only send plaintext

Can you elaborate on the issue here? What happens if I send hello (that's telegram bold)

itll send plaintext hello (no bold)
there's also another field called parse_mode if we want to allow full markdown text (no entities)


Update to 1.19.3

Describe the Suggestion
I don't know if this is already in the works or just looked over, but on Modrinth it is currently on 1.19.2.
So, yeah, if you guys haven't read the title already please update to 1.19.3.
Screenshots and Videos
No response
Additional Context
No response

The update will come when it’s ready. We are waiting for forge create first.

The update will come when it’s ready. We are waiting for forge create first.

https://github.com/Creators-of-Create/Create/tree/mc1.19.3/dev?


Color and Temperature selection in Home app does not work correctly

Describe the bug
I have Feit Electric recessed LED light bulbs - color and tunable white, Tuya-compliant (model LEDR6). The on/off, brightness features work fine. However, when I select a color in the Home app, the bulbs don't change the color correctly 50% of the time. When they are not correct, the color from the bulb is pale white, dimmed, and sometimes flickered. This does not happen when I changed the color through Feit app (colors set correctly at the bulbs.)
To Reproduce
Steps to reproduce the behavior:

Setup homebridge-tuya-web per instructions
Open the Home app on iOS
Open up light bulb accessory
Change the color to any color (red, green, blue, or something) in the color dial.

Expected behavior
Color is shown correctly at the bulb.
Screenshots
Sorry, didn't take photos of the light
Device

Plugin: @milo526/homebridge-tuya-web
Version: 0.3.34-0
Model : LIGHTBULB

Additional context
It seems the problem has to do with how Homebridge/Home app sends events when a color is selected. When you select a color, the Home app fires 2 set events back-to-back; one to set Hue and one to set Saturation. This creates a race condition in the code that causes two setDeviceState calls being made, one with correct Hue value but old/stale Saturation %, and one with correct Saturation % but with old/stale Hue value.
I fixed this by wrapping the setColor method using debounce so it will wait for all the setHue and setSaturation calls to complete, and use the last values. Also in the setColor method, use the value from cached state rather than the passed in color value.
This seems to work well but the downside is that we always return successful callback set method.
I'll add my PR shortly. (PS it also has the color temperature code...)

This is great, I hope it fixes the issue for me as well. Thanks a bunch for doing this!

As mentioned in the #33, @milo526/homebridge-tuya-web@beta should include these fixes, in a way that the Home app still gets the proper callback. Could you please install the beta version and see if that solves your issues?

@milo526 I love the new refactored accessory code. Looks awesome!

@milo526 just installed the @beta and it's working well! Actually much better than what I had in my code. Let me close this bug now. Thank you so much!


VOCSegmentation

train_data = VOCSegmentation(root='/home/', year='2007', image_set='train',transforms=
                                                               transforms.ToTensor())

ERROR:
DIR     /torchvision/datasets/voc.py
img, target = self.transforms(img, target)
TypeError: call() takes 2 positional arguments but 3 were given
Chnage:
separation the img transforms and target transforms ?

You are passing a image transform ToTensor as joint transform for images and targets:
https://github.com/pytorch/vision/blob/0bd7080c6fa4d8a07f34aa66caf10683824e5b82/torchvision/datasets/voc.py#L69-L70
If you don't need a transform for your target, simply change the instantiation call to
VOCSegmentation(root='/home/', year='2007', image_set='train', transform=transforms.ToTensor())

Note the change from transforms to transform.

@pmeier Thank you!!!!
train_data = VOCSegmentation(root='/home/hanwei-1/', year='2007', image_set='train',                                   transform= transforms.ToTensor(),                                  download=False)
this did not work
TypeError: batch must contain tensors, numbers, dicts or lists; found <class 'PIL.PngImagePlugin.PngImageFile'>
I think need to transform img and target both, so use this call and work perfect
train_data = VOCSegmentation(root='/home/hanwei-1/', year='2007', image_set='train',                                   transform= transforms.ToTensor(),                                  target_transform=transforms.ToTensor(),                                  download=False)
transforms is a bug

this did not work

Could you please post the actual code where this error occurred? Simply doing this works fine
from torchvision.datasets import VOCSegmentation
from torchvision import transforms

dataset = VOCSegmentation(VOC_ROOT, year="2007", image_set="train",
                          transform=transforms.ToTensor())

image, target = dataset[0]
print(type(image), image.size())
print(type(target), target.size)

and prints:
<class 'torch.Tensor'> torch.Size([3, 281, 500])
<class 'PIL.PngImagePlugin.PngImageFile'> (500, 281)

transforms is a bug

No, it is not. It is intended as joint transform and thus cannot be used with a single image transfomr such as ToTensor(). If you use the parameters transform and target_transform they are internally converted into a joint transform:
https://github.com/pytorch/vision/blob/0bd7080c6fa4d8a07f34aa66caf10683824e5b82/torchvision/datasets/vision.py#L15-L26
which is then used in __getitem__():
https://github.com/pytorch/vision/blob/0bd7080c6fa4d8a07f34aa66caf10683824e5b82/torchvision/datasets/voc.py#L122-L125

I want to use one argument transforms to complete transform img and target
But this argument cannot work

You still haven't shown us any code. Please do that.

Do you want to have the same transformation applied to both the image and target? If yes, you could simply do
transform = transforms.ToTensor()
dataset = VOCSegmentation(VOC_ROOT, year="2007", image_set="train",
                          transform=transform, target_transform=transform)

Yes
I use the same transformation
train_data = VOCSegmentation(root='/home/', year='2007', image_set='train',
                                                   transforms=transforms.Compose([transforms.Resize((100, 100)),
                                                                                transforms.ToTensor()]),
                                                   target_transform=transforms.Compose([transforms.Resize((100, 100)),
                                                                                transforms.ToTensor()]))
train_loader = torch.utils.data.DataLoader(train_data, batch_size=2)

I'm still lost: this does not throw an error. Do you still have a problem or is everything working as expected?

On a site note:

If you want to use the same transform for both image and target, its better to create it upfront and pass it twice instead of creating it twice within the call.

from torch.utils.data import DataLoader
from torchvision.datasets import VOCSegmentation
from torchvision import transforms

transform = transforms.Compose([
    transforms.Resize((100, 100)),
    transforms.ToTensor(),
])

dataset = VOCSegmentation('~/Downloads', year="2007", image_set="train",
                          transform=transform, target_transform=transform)

loader = DataLoader(dataset, batch_size=2)

for input, target in loader:
    print(input.size(), target.size())

Do you really want to resize your images to (100, 100)? Since this ignores the aspect ratio of the image, the motif could be heavily distorted. Especially on masks this could have some unintended side effects. You probably want something like transforms.CenterCrop() to get all images to the same size.

@pmeier Thank you so much！
Use transforms argument will throw an error.

We need special transforms for joint image and target transform, see https://github.com/pytorch/vision/blob/master/references/segmentation/transforms.py for an example.
This will be particularly important for randomized transforms, such as random flip.
Closing as it is standard behavior for now

@fmassa @pmeier Thank you so much！

Thanks for the help @pmeier !


[WIP] Bootstrap sbt build

This PR introduces an sbt build definition to compile optimus-cirrus.
While I was able to compile most of the project, some pieces of the code have been temporarily commented out due to the following blockers:

Unresolved dependencies
Missing proto files
Unavailable internal libraries or source files

I am opening this WIP PR to request assistance in locating the missing pieces.
Dependency Resolution
I used the package names to reverse-engineer the dependencies. Most of the time the latest available version of a dependency worked out of the box, or I used the latest source-compatible version.
I encountered very few version conflicts, with only one that I could not resolve. It's a version conflict on scala-xml.
To proceed further, could you clarify the internally used versions for the following dependencies?

zinc
scalaxb
scala-xml
coursier-core

Alternatively, if you can provide a complete list of dependencies with their versions, that would be helpful.
Missing .proto files
I managed to generate the Java code of the provided .proto files using  the sbt-protobuf plugin. However, it appears some .proto files are missing. Base on my investigation, I suspect the missing files include:

dsi.proto
prc.proto
expressions.proto
and possibly envelope.proto.

Could you confirm if the above-mentioned .proto files are missing? If so could you provide them?
Missing internal libraries or missing source files
Below is a list of packages that appear to be missing from the codebase.
com.ms.infra.zookeeper.utils
com.ms.infra.zookeeper.utils.hosted
com.ms.zookeeper.clientutils
msjava.base.dns
msjava.base.event.publication.watchtower
msjava.base.io
msjava.base.lang
msjava.base.multimeter.meters
msjava.base.slr.internal
msjava.base.sr
msjava.base.util.internal
msjava.base.util.uuid
msjava.hdom.input
msjava.hdom.output
msjava.logbackutils.async
msjava.kerberos.auth
msjava.management.jmx
msjava.msnet.auth
msjava.msnet.internal
msjava.msnet.ssl
msjava.msxml.xpath
msjava.pool
msjava.pool.base
msjava.protobufutils.server
msjava.threadmonitor.thread
msjava.tools.util
msjava.zkapi
msjava.zkapi.internal
optimus.dht.server.api.registry.RegistryConsts
optimus.dht.server.management.DHTManagementInterfacen
optimus.dsi.util
optimus.platform.reactive
optimus.security.akka.http.client.SimpleNoAuthenticationHttpClient
optimus.security.akka.http.common.AkkaConfigurations
optimus.tools.testplan.model.TestplanField.TestCases

On a case by case basis, could you provide the necessary source files, or some guidance to resolve this?
Smaller issues
Additional issues are documented in the comments below.

Hi @adpi2, this is great to see! Thank you for working on it. I'm working on getting all these questions answered, and plan to have some more info for you later this week. Where possible I'm pushing more files out that contain the requested information, so that it will stay up-to-date.

I've pushed a new commit today that includes the majority of the .obt files so that the dependency relationships are clearer/up-to-date. The few that are left out contain information we cannot open-source but I can share the relevant subset if needed.
Also, please check the 2 files in the oss-utils module; I've dumped the whole transitive dependency set of optimus.buildtool.app in text and image form, which answers several of the version questions.
We are still working on what to do about the libraries that are not publicly available, as well as the other questions - .proto files should be coming soon, at least.

Thank you, @ms-valerie, for your responsiveness. I'll get back to working on this PR in January. I look forward to the missing .proto files and libraries, but there is no need to rush.

Noted. We have a plan now for the 'Missing internal libraries or missing source files' now and are going to open-source them. It's not actually a ton of files; we aim to get that done in January so if you prefer to wait to revisit until we have all that available, it would make sense.


flexbox is broken in beta.10 and beta.11

From http://www.joshmorony.com/an-in-depth-look-at-the-grid-system-in-ionic-2/ I studied how to split screen into parts with flexbox, but after beta.9 it stopped working.
Here are two almost identical plunkers to compare:
flexbox beta.9
flexbox beta.10
Can you confirm that it is broken and not something changed behind the scene?

Hello @lain-me ! Thanks for using Ionic! In beta.10 we did a complete overhaul of of our layout which may cause problems with older tutorials that have not been updated. I would recommend contacting josh about it! Thanks for using Ionic!

What changes in that before the "scroll-content" had a display flex, but now a new class has been added "show-page" on ion-page which is setting the display block.
There are 2 things that you can do for a quick fix, wrap the ion-rows in an ion-grid and give it a height of 100% (remove padding if required) or wrap it in a div, and set it's display to flex and a height of 100%.

simply putting a div with 100% height worked


Uncaught Error: mobx-react-lite@3 requires mobx at least version 6 to be available

[Enter steps to reproduce:]

...
...

Atom: 1.51.0 x64
Electron: 5.0.13
OS: Mac OS X 10.15.6
Thrown From: Hydrogen package 2.14.5
Stack Trace
Uncaught Error: mobx-react-lite@3 requires mobx at least version 6 to be available
At /Users/Stefanos/.atom/packages/Hydrogen/node_modules/mobx-react-lite/lib/utils/assertEnvironment.js:9

Error: mobx-react-lite@3 requires mobx at least version 6 to be available
    at /packages/Hydrogen/node_modules/mobx-react-lite/lib/utils/assertEnvironment.js:9:11)
    at /packages/Hydrogen/node_modules/mobx-react-lite/lib/utils/assertEnvironment.js:12:3)
    at Module.get_Module._compile (/private/var/folders/8v/q6m26w716_995ss22_1r_84w0000gr/T/AppTranslocation/E29DFF61-824C-4183-A91B-739505004399/d/Atom.app/Contents/Resources/app/static/<embedded>:11:147498)
    at Object.value [as .js] (/private/var/folders/8v/q6m26w716_995ss22_1r_84w0000gr/T/AppTranslocation/E29DFF61-824C-4183-A91B-739505004399/d/Atom.app/Contents/Resources/app/static/<embedded>:11:151046)
    at Module.load (internal/modules/cjs/loader.js:701:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:633:12)
    at Function.Module._load (internal/modules/cjs/loader.js:625:3)
    at Module.require (/app.asar/static/index.js:72:46)
    at require (/private/var/folders/8v/q6m26w716_995ss22_1r_84w0000gr/T/AppTranslocation/E29DFF61-824C-4183-A91B-739505004399/d/Atom.app/Contents/Resources/app/static/<embedded>:11:146814)
    at /packages/Hydrogen/node_modules/mobx-react-lite/lib/index.js:3:1)
    at /packages/Hydrogen/node_modules/mobx-react-lite/lib/index.js:42:3)
    at Module.get_Module._compile (/private/var/folders/8v/q6m26w716_995ss22_1r_84w0000gr/T/AppTranslocation/E29DFF61-824C-4183-A91B-739505004399/d/Atom.app/Contents/Resources/app/static/<embedded>:11:147498)
    at Object.value [as .js] (/private/var/folders/8v/q6m26w716_995ss22_1r_84w0000gr/T/AppTranslocation/E29DFF61-824C-4183-A91B-739505004399/d/Atom.app/Contents/Resources/app/static/<embedded>:11:151046)
    at Module.load (internal/modules/cjs/loader.js:701:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:633:12)
    at Function.Module._load (internal/modules/cjs/loader.js:625:3)
    at Module.require (/app.asar/static/index.js:72:46)
    at require (/private/var/folders/8v/q6m26w716_995ss22_1r_84w0000gr/T/AppTranslocation/E29DFF61-824C-4183-A91B-739505004399/d/Atom.app/Contents/Resources/app/static/<embedded>:11:146814)
    at /packages/Hydrogen/node_modules/mobx-react/dist/mobxreact.cjs.production.min.js:1:324)
    at /packages/Hydrogen/node_modules/mobx-react/dist/mobxreact.cjs.production.min.js:4:3)
    at Module.get_Module._compile (/private/var/folders/8v/q6m26w716_995ss22_1r_84w0000gr/T/AppTranslocation/E29DFF61-824C-4183-A91B-739505004399/d/Atom.app/Contents/Resources/app/static/<embedded>:11:147498)
    at Object.value [as .js] (/private/var/folders/8v/q6m26w716_995ss22_1r_84w0000gr/T/AppTranslocation/E29DFF61-824C-4183-A91B-739505004399/d/Atom.app/Contents/Resources/app/static/<embedded>:11:151046)
    at Module.load (internal/modules/cjs/loader.js:701:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:633:12)
    at Function.Module._load (internal/modules/cjs/loader.js:625:3)
    at Module.require (/app.asar/static/index.js:72:46)
    at require (/private/var/folders/8v/q6m26w716_995ss22_1r_84w0000gr/T/AppTranslocation/E29DFF61-824C-4183-A91B-739505004399/d/Atom.app/Contents/Resources/app/static/<embedded>:11:146814)
    at /packages/Hydrogen/node_modules/mobx-react/dist/index.js:5:20)
    at /packages/Hydrogen/node_modules/mobx-react/dist/index.js:10:3)
    at Module.get_Module._compile (/private/var/folders/8v/q6m26w716_995ss22_1r_84w0000gr/T/AppTranslocation/E29DFF61-824C-4183-A91B-739505004399/d/Atom.app/Contents/Resources/app/static/<embedded>:11:147498)

Commands
     -7:43.3.0 hydrogen:run (input.hidden-input)
     -7:31.2.0 core:copy (atom-notification.fatal.icon.icon-bug.native-key-bindings.has-detail.has-close.has-stack)
     -3:46.6.0 core:confirm (input.hidden-input)

Non-Core Packages
Hydrogen 2.14.5
kite 0.187.0
platformio-ide-terminal 2.10.0
script 3.26.0

I also had this issue this morning.  Threw a major wrench in my workday.  I don't (knowingly) use mobx, and don't know where this issue came from.  I did a complete uninstall of atom ( https://discuss.atom.io/t/how-to-completely-uninstall-atom-for-mac/9084/41 ), and then re-installed. Now the problem is gone.

Thanks for reporting the issue, folks!
We did push out a new release of Hydrogen but we haven't modified any of our MobX dependencies recently. It looks like this is limited to macOS so something funky might be going on there.

Oof. Based on #2006 it looks like we aren't on the right version of mobx.
@aviatesk @BenRussert  Would it suffice to merge the PR referenced above?

It's interesting that a reinstall of atom worked, I wonder if there is some dependency conflict. I wonder if an uninstall/reinstall of hydrogen would have done the trick?

Would it suffice to merge the PR referenced above?

@captainsafia I think there's a good chance that we're already upgrade compatible to mobx 6 based on a skim of the breaking changes, but someone will need to try bumping the version and a little qa on it locally to see if anything breaks.

@BenRussert Thanks for confirming!
Anyone in the thread interested in testing this out?

On second thought, I saw the CI errors for #2006 and it looks like a bit of a chore.
I wonder if anyone can repro? or this may have possibly been a fluke conflict with atom or another package. If it's not happening anymore we may as well stick with mobx 5 for now.


docs: fix typo in astro.md

Cannot find module 'unocss/astro'

@silverwolf42 why did you close the pr?

@silverwolf42 why did you close the pr?

it's work
i made a mistake


Nest Temperatures back to front

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.31.0
Python release (python3 --version):
3.4
Component/platform:
Raspi 3
Description of problem:

Seeing the internal and external temperatures back to front since the  0.31.0 update
Expected:
Problem-relevant configuration.yaml entries and steps to reproduce:

Traceback (if applicable):

Additional info:

Latest update 0.31.1 has resolved the issue.


Problem with dangerouslySetInnerHTML?

Hi, I was glad being able to use react-web-animations, cool library!
I found something strange when I have an element with dangerouslySetInnerHTML inside <Animation/>. Simply, the dangerouslySetInnerHTML content is not displayed before onPlay. Once trigged play, it would be fine.
Also tried all possible fill options, got the same behavior.
If I use <Animation/> inside a wrapper component, and force shouldComponentUpdate of the wrapper, I see that both before and after animation the dangerouslySetInnerHTML is lost, while only during the animation they are displayed.
Any ideas? Could this be a react thing?

More specifically, if my wrapper is like:
const Wrapper = (props) => <Animation {...props}>{props.children}</Animation>

And use it with
<Wrapper keyframes={keyframes} timing={timing}>

</Wrapper>

The
 appears empty before and after, but only show someHtml during the animation

@t47io thanks for letting me know about this, I will take a look and see if I can re-create

@t47io can I get a little more context? I am trying this example here and it seems to work okay - https://github.com/bringking/react-web-animation/blob/bug/set-inner-HTML/example/src/with_inner_html.js

@bringking Hi, thanks a lot for testing! I tested with your example too, and it works. I found that the problem is with preact, not react. As the dangerouslySetInnerHTML content disappears when I have this in webpack.config.js:
    resolve: {
        alias: {
            react: 'preact-compat',
            'react-dom': 'preact-compat',
        },
    },

I use preact because of its smaller size. I will create another ticket there. Thanks!

can close now

@SiqiTian-minted okay good to know. I can do a spike and see if there is something we can do to support preact-compat and inferno-compat

good to know and thanks a lot! curious what does it take to support those?

@SiqiTian-minted I don't know yet, haven't dug in, I think it might be related to the way we rely on refs to get access to the node... but that is just a hunch


D417 for missing arguments is google only

In principle D417 (new in v4.0.0 c02884919e3f3708a1343443b52cb9b69434663c by @samj1912 as part of support for the Google coding style #275, further enhancement in #384 ) could be performed under the numpy convention, which has a well defined parameters section.
In fact, it could be applied to the default pep257 convention with a simple substring check - are all the function arguments present anywhere in the docstring? This wouldn't catch everything but would be better than nothing?

I added support for numpy style docs for now

Ah, pull request #407 - looks good :)

@samj1912 As suggested by the OP's inclusion of --add-select in #461, it appears that D417 is still excluded when convention=numpy. Same on my end - should this exclusion be removed?
On the same topic, should the exclusion of D413 be removed for NumPy docstrings, as well? Everything I've seen on NumPy docstring style suggests that a blank line before closing the string is standard.


move to clusterscoped genclient

I think you will have to delete the client dir and rerun the codegen.

/lgtm


Fix PosixPath error that occurs when running build_dataset()

Convert PosixPath objects to strings so that tf.data.TFRecordDataset(tfrecordfiles) doesn't throw an error for some (older) TF versions

The pytest test_list_tfrecords will keep failing due to the filename variable being defined as a PosixPath object. @quantumjot can you fix that or should I try to?
tmp_path = PosixPath('/tmp/pytest-of-runner/pytest-0/test_list_tfrecords0')
    def test_list_tfrecords(tmp_path):
        """Check that list_tfrecords returns a list of tfrecord files when using
        different inputs, e.g. single file, folder or list."""
        filename = Path(tmp_path) / "test.tfrecord"
        _ = _test_write_images(filename)

        # single path to file
        files = list_tfrecord_files(filename)
>       assert files == [filename]
E       AssertionError: assert ['/tmp/pytest...est.tfrecord'] == [PosixPath('/...st.tfrecord')]

Yes, I think you'll need to update the test too, to make sure the paths are equivalent. Go for it!


Run mypy on python 3.7

Summary
Details and comments

@manoelmarques because of the force-push I was unable to follow the PR. The last commit LGTM.


get_sessionid() is not same value with server side

I am using get_sessionid() to get socket id which should be similar to socket.id.
However, it is not matched with id from server side.
Javascript has socket.id, Java has socket.id(). Both work well and matched with server side.

Fixed by #410