Calendar Open View hotkey not working

Describe the bug
Calendar Open View hotkey not working
Steps to reproduce

Assign a custom hotkey to "Calendar: Open View"
Use the hotkey
Calendar does not open

Expected behavior
Calendar will not open after using the hotkey.
OS
Windows 10 Pro
Obsidian Version (e.g. v0.14.2)

Not sure if you've figured it out already or not, but I ran into this today. As it turns out, PEBCAK applies here.
While a note is open, click on the right sidebar

You should then see the calendar widget; now you can move the pane to your preference.

It might be nice for "Open Calendar" command to actively open the Calendar Widget instead of creating an instance in the collapsed right sidebar to help users like us. But this seems to be a feature, not a bug

This just solved my issue. Who knew, though?

I think the widget should open in the sidebar. That is exactly what the hotkey indicates: "Open view". This is how other plugins like outline or advanced tables work


ENG-4664 feat(portal): update queries in stake modal

Affected Packages
Apps

[ ] data populator
[x] portal
[ ] template

Packages

[ ] 1ui
[ ] api
[ ] graphql
[ ] protocol
[ ] sdk

Tools

[ ] tools

Overview
Based off branch/PR 4383 since there were some important updates to the stake modal that had to be accounted for. Cannot merge until we get that PR merged in.

Swapped out vaultDetails fetcher for react query hook
honestly can't remember some of the other updates since so much is crammed into this due it being based off another branch. Once that is merged and this is rebased, it will clear that all up.

Screen Captures
If applicable, add screenshots or screen captures of your changes.
Declaration

[x] I hereby declare that I have abided by the rules and regulations as outlined in the CONTRIBUTING.md

@Vitalsine85 -- I removed the do not merge label since this is onto the feature branch


Update rapidjson

This updates rapidjson from a 8 years old version to a98e99992bd633a2736cc41f96ec85ef0c50e44d (modified 3 days ago)

I have verified that after updating the python and grit version and applying this patch, rm -rf out/Default/ && gyp --depth . && ninja -C out/Default && out/Default/unit_tests succeeds.


In nz-select, options getting bold style randomly, when scrolling 2 to 4 times after selecting a value.

Reproduction link
https://stackblitz.com/edit/angular-6u5nzf?file=src%2Fapp%2Fapp.component.ts
Steps to reproduce

select any item,
scroll slowly 2 to 4 times
observe list font getting bold

What is expected?
font shouldn't get bold while scrolling
What is actually happening?
font is getting bolder after scroll which is not expected

Environment
Info

ng-zorro-antd
15.0.0

Browser
any browser

Has same issue.
Reproducible only on Chrome-based browsers (Firefox works good) and only when first item of the list is selected.

Any update on this?

Any update on this?

hello any update?


Migrate tutorials

Copy the old tutorials to the new docs folder, and update them so they work. Use this or this to render notebooks into the documentation.

Old tutorials meaning https://github.com/rbracco/fastai2_audio/tree/master/nbs ?

Sorry about the inaccurate description. From that link, the important ones are tutorial.ipynb (this one I already converted), and the ones that end with *_overview.ipynb that showcase the different modules. Maybe the those can be merged into one big overview notebook?
But there's also some awesome old notebooks from fastai_audio V1 that were never migrated, like Intro to audio

Will try to move them. Should I also add the nbs directory so that it would be easier to edit them or just build with mkdocs and thats it?

Just put them inside the docs/ folder and mkdocs takes care of converting them into the html page.

I tried both extensions that I mentioned in the first comment, and here are the resulting rendered notebooks:

mkdocs-jupyter

mknotebooks

Comparing the two I found mknotebooks to be better than the other. It correctly formats the cells, has better looking tables and includes a copy button on the side.

Hi there, in a PR to the old repo, I updated the tutorial there and also changed the dataset for the second part of the tutorial to speechcommands https://github.com/rbracco/fastai2_audio/pull/49/files#diff-f87f83a5969bea0062b298bc525a2f38 would you like I migrate that one here? or append it to the current tutorial? or do a second one?

Yes sorry that we couldn't merge that. If you could create a new tutorial in a separate PR to this, that would be great. I think having a one data set per tutorial would be better with folder categorising them together.

You mean create a folder in this path for each new ipynb?
https://github.com/fastaudio/fastaudio/tree/master/docs

Create a separate notebook for your tutorial. Name it whatever you like for now, create a PR and I will organise them into folders later.

I have the second part waiting to be pushed on https://github.com/fastaudio/fastaudio/pull/43 after the other PR is merged.
By the way, what is the state of the other tutorials??? like Intro to audio because just starting and will read them too, so I can get a better understanding... and maybe will try to port them on the way... if still possible.

Let's wait until the current set of PR's are merged. I think we need to migrate all the tutorials here but there is also the caveat that they need to be compiled to go on to the new mkdocs pages. fastaudio.github.io

We are only waiting for  https://github.com/fastaudio/fastaudio/pull/39 or there is another PR we are waiting on?
About the mkdocs, in the first post which one fast finally used?
Should we run them? it will be run with a GA? or?

But there's also some awesome old notebooks from fastai_audio V1 that were never migrated, like Intro to audio

I think I will start porting this ones, if I got stuck, I will ping on this issue.

I've already started on this one :)

Oh, good I see, you want that I check one of the others? or you will port them?

I'll probably finish it off soon, apologies for the delay. If you want to start on some issues though have a go at any of the unassigned ones in the issues list. #48  or #50 for example.


gbp.conf: fix default branch names

Make the default branch names compliant to DEP-14:
Recommended layout for Git packaging repositories
https://dep-team.pages.debian.net/deps/dep14/
Also added common import-orig filters for Github upstreams.

i dont agree with this change


Would like to use disk_cids in the CPI method "create_vm"

https://www.bosh.io/docs/cpi-api-v1-method/create-vm/ mentions:
disk_cids [Array of strings] Array of disk cloud IDs for each disk that created VM will most likely be attached; they could be used to optimize VM placement so that disks are located nearby.

most likely means that the disk might not be attached to the VM in some situation. Could you please describe the situation?
My understanding: when updating the VM with persistent disks, BOSH will detach the persistent disk, delete the old VM, create a new VM and attach the persistent disk. Then the disk_cids MUST be an array of the persistent disk CIDs, which were attached in the old VM. Could you please confirm it?
If the item 2 is correct, then CPI can use the disk_cids to do some optimization or validation. Example:

Check whether instance_type and the disk can work together. In Azure, some instance types support premium storage, some don't. CPI can fail fast if the specified instance type doesn't support the disk type.
Attach the disk when creating VMs. Then CPI does nothing in attach_disk. It may reduce deployment time.

It would be very nice if the item 1 and 2 is documented. CC: @mfine30 @jfmyers9 @dpb587-pivotal

most likely means that the disk might not be attached to the VM in some situation. Could you please describe the situation?

It will be empty in the case where a disk has not yet been created for new instances. For the specific case of when a disk passed to create_vm may not be used... it could happen in the case where someone runs cancel-task on a deployment which started running create_vm, but did not successfully finish nor get to the point of attaching disks. Future deploys after that failed deploy may then want to create new VMs and eventually attach the hinted disk.

... Could you please confirm it?

Currently, that looks to be the case. However, keep in mind we intend these as hints; not guarantees. The subsequent attach_disk calls should still work with changed CIDs, although if there is an IaaS incompatibility, the CPI may still error in the call.

optimizations/validations

Azure's use case with the instance type and premium storage matrix does make sense to have some validation (which I think the Azure API already provides). However, if you want additional, nicer user errors around this... you should always do this in, at least, the attach_disk stage (because that call can happen regardless of create_vm).
Regarding create_vm pre-attaching disks... you should avoid this. This causes the state of the IaaS resources to become different than BOSH expects. This can cause internal issues later if the BOSH resurrector attempts resurrecting a partially failed deploy, or if the user is trying to verify the state of their deployments with cck.
Also, these are disk hints... so in theory, director may follow up the create_vm with an attach_disk call with a different CID. To account for this, your attach_disk would need to introduce its own state management to detect if there is already a disk attached, and if it was "intentional" from BOSH's perspective. Having two separate systems managing this would likely introduce bugs somewhere along the way.
While those optimizations may save a few moments in the create_vm+attach_disk scenarios, the additional complexities it introduces is probably not worth it without extensive edge case testing on your side.
Hopefully this helps answer your questions? But happy to discuss further.
@dpb587-pivotal && @belinda-liu

Thanks @dpb587-pivotal && @belinda-liu for giving us so many helpful guidance.

validations

There's a problem about the instance type and premium storage. For example,

The instance_type Standard_DS1_v2 supports premium storage. By default, CPI will attach a premium persistent disk to it.
When the instance_type is changed to Standard_D1_v2, which doesn't support Premium storage. The old VM is deleted, and the original premium persistent disk should be attached to the new created VM. But it can't.

Short goals:
The instance type can be changed by vm_type or vm_resources. Using disk_cid, we can do the validations in create_vm for two scenarios. For vm_type changing, CPI need to fail fast and ask users to change instance type. For vm_resources changing, CPI needs to calculate a premium-storage-supported instance type if the disk is a premium one.
Long goals:

It would be very nice to make disk_cids guarantees.
We are also thinking about a proposal to add a new CPI method called validate_cloud_properties_changes?. Director can call it to validate whether cloud properties change (e.g. instance type change) is good or bad, before it really create a VM.

optimizations

I agree with you. We should avoid create-vm pre-attaching disks.

Hi @bingosummer,
We don't think it is likely that we will make the disk_cids on create_vm a guarantee any time soon. It seems cleaner that the disk_cids specified in attach_disk do not necessarily need to be included in this list. This separation will enable us flexibility when implementing advanced lifecycles in the future (i.e. attaching new disks without recreating the instance).
With regards to validate_cloud_properties_changes?, we aren't sure that other IAAS's would benefit from this interface change. This would be a concern for us going forward if we were to add this to the generic CPI interface. We would definitely like to hear more about the proposal and how it might be used generically to benefit all CPIs.
As to the original questions, it would be difficult for us to document situation in which the disk might not be attached to the VM in some situation as this is very IAAS specific.
We are going to close this issue. Please feel free to reopen it if you have any further questions.
Best,
@jfmyers9 && @jrussett, CF BOSH


CI: ipsec-upgrade: xfrm errors were changed - inbound_no_state

CI failure
Hit on https://github.com/cilium/cilium/pull/27448
Link: https://github.com/cilium/cilium/actions/runs/5923431755
Sysdumps: cilium-sysdumps.zip
[=] Test [no-ipsec-xfrm-errors]
  [-] Scenario [no-ipsec-xfrm-errors/no-ipsec-xfrm-error]
  🟥 Node  xfrm errors were changed (previous errors: , current errors: inbound_no_state:1)

📋 Test Report
❌ 1/51 tests failed (0/312 actions), 13 tests skipped, 1 scenarios skipped:
Test [no-ipsec-xfrm-errors]:
connectivity test failed: 1 tests failed

Closing, as the branch didn't contain https://github.com/cilium/cilium/commit/b55ca78259545111c475ef754f21aace46e5ca96 (x-ref: https://github.com/cilium/cilium/issues/27276).


Auto deploy and Issue/PR templates

Description
This PR is not feature-related, but instead adds the following to the repo:

New releases (tags) are auto-deployed to Rubygems upon successful test run.
There's now an Issue Template that users will see when opening an issue.
There's now a Pull Request Template that users will see when submitting a PR.

Additional Notes
Auto deployment key has been safely encrypted and deploy will trigger only when a new tag is pushed. This will automatically happen every time we create a new release here on GitHub.
Travis will also proceed with the release only if the tests are passing for Ruby 2.3.1 and Rails 4.2.
In case we added a more recent version of Ruby/Rails to the travis matrix, this condition should be updated as well.
@nicolasblanco please review this one and let me know if you have anything against it 😄

@nicolasblanco merging in and trying it with release v0.10.1, but I can remove it later if you want.


Exclude smoke tests not for current environment

This PR excludes smoke tests not meant for the current environment when they're run by Concourse. To facilitate this, any tests not meant for a particular environment should be marked up as @replatformingnot<environment> in Smokey, where <environment> is to be replaced with the name of the environment in which they should not be run.
The reason for this change is to allow us to run smoke tests for publishing content, ensuring that they do not run in production.
Trello: https://trello.com/c/9QipS0X0

Nice I didn't know that the tags expression could contain a logical AND.


Update KUDO to 0.8.0.

@viivek46 well spotted: https://github.com/mesosphere/kudo-cassandra-operator/pull/24/commits/63d2d0fd7c76c9ebe80fc1598a0c8295f342597d
I just ran ./tests/run.sh to get it updated automatically.


using animated progressbar consumes 50% cpu

Hi,
I'm creating a webpage that uses 3 animated progress bar's, they use 50% of my cpu. If I remove them it goes back to normal

I've been hit by this problem for some time now. It looks like browser vendors aren't fixing it. Can we update bootstrap so that it will no longer rely on css3 to do the animation?

It will be significantly improved if the animation works with transform (which would require 2 pseudo elements.) For example, you can add the following patch (after the bootstrap SCSS imports):
.progress-bar-striped {
  background: none;
  position: relative;
  overflow: hidden
}
.progress-bar-striped:before {
  content: "";
  background-color: $progress-bar-bg;
  position: absolute;
  top: 0;
  height: $progress-height;
  left: 0;
  width: 100%;
}
.progress-bar-striped:after {
  content: "";
  position: absolute;
  top: 0;
  height: $progress-height;
  width: calc(100% + #{$progress-height});
  left: 0;
  @include gradient-striped();
  background-size: $progress-height $progress-height;
  will-change: transform;
}
.progress-bar-animated {
  animation: none;
}
.progress-bar-animated:after {
  animation: progress-bar-stripes-optimized $progress-bar-animation-timing;
}
@if $enable-transitions {
  @keyframes progress-bar-stripes-optimized {
    from { transform: translateX(0); }
    to { transform: translateX(-1 * $progress-height); }
  }
}


[QUESTION] What would prompt "equals()" in AbstractItem to not be called ?

Referencing #285 .
I couldn't re-open the issue.
I noticed my "equals()" method in my SectionItem which extends AbstractSectionableItem<> is not being called and I am stumped as to what I am missing when initializing my adapter.

@ahmedkhan23, the equals() method is used everytime the object is compared to another one, so it happens all the time in a java.util.List when you get an item. If you don't have an unique ID value for your item, then you can use default java implementation: return this == o.

@davideas in my implementation for my SectionItem it is never getting called

@ahmedkhan23, it's Java, so it is called. Read this article: https://www.sitepoint.com/implement-javas-equals-method-correctly:
Try to put some logs in it, but of course when you retrieve from a list you should search it correctly.
If you put log you will see it will be called tons of times!

@davideas my equals method in SectionItem is not called when the adapter/recyclerview are being setup. It is only called when I remove an item from the adapter.
Is this expected ?
Put logs/breakpoints/ checked your sample app. In your sample app the equals method is indeed called when the recyclerview/adapter are first being setup - at least what I could gather by using breakpoints.

Is this expected ?

Yes.
My sampleApp builds the initial list differently than yours I suppose.

@davideas even when I do a proper implementation of equals() method, the regular Java implementation of "return this == o" - I am seeing the issue of my views being recycled in different positions as I scroll up and down my list. Can't pinpoint the error for the longest time.

problem was in my bindView() ... I had an if clause but no "else", so the settings from the "if" were being applied to other view holders as I was scrolling up and down ...


Now removing comments from RST for more complex example

List of related issues or pull requests
Refs: PR#312
Describe the changes made in this pull request
I noticed that comments in e.g. a section would not be processed by #PR312, changed it a bit in this PR and added a more realistic example, i.e the howfairis readme
Instructions to review the pull request
Same as before:
# in an activated venv with dev dependencies installed
pytest tests/remove_comments_rst
pytest tests/
pytest livetests/
bash clitests/script.sh

Longer, different format

Yep I saw that too, one of the reasons why having expected text and original text is helpful. The reason is that a piece of content can be associated with multiple nodes in the tree. I thought I could fix it some other way, by combining the node's .line property with the length of the string in it (.rawsource) and then overwrite a copy of the original text with spaces. That way, you'd just redact the comment and not touch anything else. Problem I encountered is that I can't figure out what the value of .line represents. I assumed it meant "the line where the content starts", but the debugger says otherwise. I get at least two behaviors, both different than what I assumed. So, for the moment, I think we're stuck with the duplication.
Made issue #315

Thanks for reviewing!


NPE when using CLion to debug with LLDB (macOS)

A recent change broke the ability to use LLDB for debugging on macOS. This renders it unusable with CLion 2019.3.6 and plugin version 2<IP_ADDRESS>.0 on macOS 10.14.6. The Jetbrains team are looking at resolving the issue of the NPE on there side (see comment). However, the change in the plugin has caused a regression so it would be good to undo that until its fixed in CLion.

This is the same issue as #1736.

@tpasternak is this also fixed with https://github.com/bazelbuild/intellij/pull/4003?


Daniel

Changed  Elements from being added as a subdirectory in CMake to being a package/library installed, found, and linked. Updates to standalone EVPFFT to capture this functionality for Matar.

I will definitely need to modify the document as well


Add support for woff2 fonts

Currently woff2 fonts return "unsupported font format". Please support woff2.

I have an update. I've cleaned up the code and it's ready for review. The implemented functionality so far is enough to parse all Go font family woff2 files that I was able to throw at it. It's definitely incomplete and not 100% spec compliant regarding validation of errors, etc. But one step at a time; it should be enough to resolve this issue. I wanted to get it to this point first and work on the rest in future changes.
However, I'll be transparent, one of the reasons I'm working on the woff2 package is because I want to use it as a pet project to test out a custom code review tool for Go that I'm (slowly) working on. To that end, I plan to self-host this woff2 decoder package (similar to https://dmitri.shuralyov.com/kebabcase) and do development there. In other words, I know it'd be easier to just put it on GitHub and use pull requests, but that's not my goal with this project.
Another important factor is that it might make sense for this library/repository to just contain the woff2-related code inside. There's some stuff around tags that can be reused. It'd be easier to be able to change all relevant code with 1 PR rather than having send changes 2 separate repos.
But I do like the idea of having a standalone woff2 decoder (and in the future, encoder) package, similar to how there are standalone packages for various image formats, such as image/png, image/jpeg, golang.org/x/image/bmp, etc.
So, how we proceed is largely up to you @ConradIrwin and @bramp:

If you're okay with having the woff2 decoder be a standalone package elsewhere and have sfnt be a client of that package, and deal with my indieweb-inspired experiment of developing a Go package not on github, I can send both things for review.
If we go this route, I'm happy to help maintain things, and if there need to be any breaking API changes, I'll follow up here to keep things building (see my policy on breaking API changes here).
(Here's a preview of what the package's API looks like so far: https://redpen.io/rk9a75c358f45654a8.)

Otherwise, if you wish, you're welcome to copy/use my woff2 decoder code and implement a copy of it inside this repo to resolve this issue. I'm licensing my code liberally with the Go license, but you can just reuse the existing MIT license of this repo. But I'll continue development of my standalone woff2 package separately.

@shurcooL hey! Absolutely fine if you want to host the woff2 decoder — we should probably start tagging dependency versions ourselves.
What would the diff look like to read woff2 files?
If I remember rightly, woff2 files are just a different container for sfnt, including some crazy compression rules. Does it makes sense to do woff2 -> sfnt and then re-use the sfnt parser in this library, or would it make sense to define a very basic common interface so that we can re-use the table parsing logic from this library, but rely on woff2 to extract and decompress each table?
type FontContainer interface{
   TableList() ([][4]byte, err)
   Table(tab [4]byte) ([]byte, err)
}

hey! Absolutely fine if you want to host the woff2 decoder — we should probably start tagging dependency versions ourselves.
What would the diff look like to read woff2 files?

Great! Let me send a PR to this repo to give you a better idea of what it'll look like, and you can review that.

If I remember rightly, woff2 files are just a different container for sfnt, including some crazy compression rules.

Yes, woff2 is very similar to sfnt and woff1. The compression rules are quite simple, they basically replace zlib with Brotli, that's about it. However, there are quite a few rules in https://www.w3.org/TR/WOFF2/ about what counts as invalid woff2 files that a spec-compliant parser must reject, e.g.:

The CompressedFontData stream MUST be compressed using the Brotli compression algorithm [Brotli]. If the decompression of the data block fails for any reason, the WOFF2 file is invalid and MUST NOT be loaded.

If the transformLength of the transformed loca table is not equal to zero, or if the encoded origLength does not match the calculated size defined above the decoder MUST reject the WOFF2 file as invalid.

My goal with the woff2 package is to implement all those for rules for correctness, and have the StrictParse-like behavior.

Does it makes sense to do woff2 -> sfnt and then re-use the sfnt parser in this library, or would it make sense to define a very basic common interface so that we can re-use the table parsing logic from this library, but rely on woff2 to extract and decompress each table?

Yes, that is the general direction I wish to follow. Inspiration for me is the image.Image interface that allows all image format encoder/decoders to able to work interchangeably on image data. However, I think we should take our time getting there, and take small, testable steps that get us closer, because figuring out a good common interface isn't trivial.
A good first step IMO is to resolve this issue—to add support for parsing woff2 files to font/sfnt package, and add tests for it. That'll allow all the commands in cmd/font to operate on .woff2 files, which is useful. Then, we can think about what priorities to accomplish next and work on them one at a time.


Base model with abstraction by computed_field

Initial Checks

[X] I have searched Google & GitHub for similar requests and couldn't find anything
[X] I have read and followed the docs and still think this feature is missing

Description
i need build the model with abstraction, which require field definition by the class attribute or computed_field.
Pseudo example base model with description which fields are expected
class EntityBase(BaseModel):
    value: str

    @abstractmethod
    @computed_field
    def type(self) -> int | None:
        pass

By this I mean that the type field must be defined in one of the following ways:

Simple class attribute definition:
class EntityTypeOne(EntityBase):
    type: int

The model postprocessing
class EntityTypeTwo(EntityBase):
    context: dict = Field(exclude=True)

    @model_validator(mode="after")
    def _process_model_after(self):
        """Some complex processing with `type` computing by `context`"""
        ...

    @computed_field
    def type(self) -> int:
        return self._type

$\textcolor{yellow}{\textsf{Or it would be more correct to add a special pydantic decorator to mark such fields.}}$
Profit

The model transparency (ABC)
Single point of additional processing of expected attributes - the base model

Affected Components

[ ] Compatibility between releases
[ ] Data validation/parsing
[ ] Data serialization - .model_dump() and .model_dump_json()
[ ] JSON Schema
[ ] Dataclasses
[ ] Model Config
[ ] Field Types - adding or changing a particular data type
[ ] Function validation decorator
[ ] Generic Models
[X] Other Model behaviour - model_construct(), pickling, private attributes, ORM mode
[ ] Plugins and integration with other tools - mypy, FastAPI, python-devtools, Hypothesis, VS Code, PyCharm, etc.

@Docdez,
Thanks for your question. This is currently supported. See https://docs.pydantic.dev/latest/concepts/models/#abstract-base-classes.
Here's an example of how you can apply this: https://github.com/pydantic/pydantic/blob/752daaf14181f3d8a410a015482648b8d9d896d1/tests/test_computed_fields.py#L532

@sydney-runkle
Thanks for the answer, but I mean a bit different.
class EntityBase(BaseModel, ABC):
    value: str

    @computed_field
    @property
    @abstractmethod
    def type(self) -> int | None:
        pass

Clear that it's easy for the computed_field
class EntityTypeTwo(EntityBase):
    context: dict = Field(exclude=True)

    @model_validator(mode="after")
    def _process_model_after(self):
        self._type = 1 if "foo" in self.context else None

    @computed_field
    def type(self) -> int | None:
        return self._type

But doesn't work with the simple field definition
class EntityTypeOne(EntityBase):
    type: int

ValueError: you can't override a field with a computed field

Seems it's the common abs restriction for class attributes also(?)

Yeah, I suppose this does look a bug! Reopening.


[MYVIC-114] Datadriven IE support configuration

Description

MYVIC-114
Motivation and Context

Merge patch in vic-gov-au for kinder map back to here.
https://github.com/dpc-sdp/vic-gov-au/blob/develop/patches/%40dpc-sdp%2Bmyvic-data-driven-component%2B1.8.1.patch
How Has This Been Tested?

Tested in kinder map already.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Improvement/refactoring (non-breaking change that doesn't add any features but makes things better)

Checklist

[x] The PR title is no longer than 64 characters.
[x] My code follows the code style of this project.
[x] I've added relevant changes to the documentation (applies to new features and breaking changes in core

Hi @hgaitanis can you please merge this after review? It should be part of the MYVIC-114. Thanks!


How to initialize LSTMStateTuple ?

In ptb_word_lm.py tutorial. When I set tf.nn.rnn_cell.BasicLSTMCell to  state_is_tuple=True, it fail initialise the state at the begining of each epoch. What is the way to initialise a LSTMStateTuple ?
I did use cell.zero_state to get the varible for the initial state, which works fine. However, when I want to get initial values of the initial state using initial_state.eval(), I got an error saying that AttributeError: LSTMStateTuple object has no attribute 'eval'.
Please see a simplified version of my code below (this code works well when state_is_tuple=False)
    state = lstm.initial_state.eval()
    for step, (x, y) in enumerate(reader.ptb_iterator(train_data,
                                                    batch_size, num_steps)):
        feed_dict = {
            input_data: x, targets: y,
            lstm.initial_state: state
        }
        _cost, state, _ = sess.run(
            [cost, lstm.final_state, train_op],
            feed_dict=feed_dict
        )

The main reason for feeding this initial_state into feed_dict is to propagate the cell's state to the next iteration.
Many Thank

A) use the zero_state function on the cell object
B) for an rnn, all time steps share weights.  We use one matrix to keep all gate weights.  Split by column into 4 parts to get the 4 gate weight matrices.
C) StackOverflow is a better place to ask.

@ebrevdo Thank you. But I still can't initialize state from LSTMStateTuple.
When state_is_tuple = False, I can get new state values by new_state_val = state.eval(), and then feed new_state_val into feed_dict.
However, when state_is_tuple=True, I can't initialize the state values as LSTMStateTuple does not have eval(). So I instead do the following:
new_state = state
new_state[0].assign(state[0].eval())
new_state[1].assign(state[1].eval())

I got an error saying --> AttributeError: 'Tensor' object has no attribute 'assign'
Could you please advise how to get the initial state from the LSTM cell when state_tuple=True?
Many thanks : D

Usually states are fed to tf.nn.rnn via initial_state parameter.  you can use cell.zero_state method to get an all zeros initial state.  Alternatively, you do not have to pass one and cell.zero_state will be called for you.  You do not need to store an initial state to a Variable in most cases.

@ebrevdo Perharps, I didn't describe my problem clearly. I did use cell.zero_state to get the varible for the initial state, which works fine. However, when I want to get initial values of the initial state using initial_state.eval(), I got an error saying that AttributeError: 'LSTMStateTuple' object has no attribute 'eval'.
Please see a simplified version of my code below (this code works well when state_is_tuple=False)
        state = lstm.initial_state.eval()
        for step, (x, y) in enumerate(reader.ptb_iterator(train_data,
                                                        batch_size, num_steps)):
            feed_dict = {
                input_data: x, targets: y,
                lstm.initial_state: state
            }
            _cost, state, _ = sess.run(
                [cost, lstm.final_state, train_op],
                feed_dict=feed_dict
            )

The main reason for feeding this initial_state into feed_dict is to propagate the cell's state to the next iteration.
Many Thank

LSTMStateTuple is just a tuple.  You can create it with two placeholders and when you run session, pass values for those placeholders with the feed_dict param.  To evaluate an LSTMStateTuple, simply call session.run(lstm_state_tuple).

@ebrevdo can you give a code example ?

It seems I'm late to the party but can someone explain why the state is a tuple and not just a single value? thanks.

LSTMTuple consists of previous cell state, and output.

It seems that this issue was resolved a long time ago. But I stuck on this problem not so long ago and didn't figure out good solution from upward thread.
So I decided to share solution I found. Possibly it would be useful for somebody.
After creating cell (e.g. with MultiRNNCell) we can receive zero_state of it cell. Hence we can initialise Tensor with such shape and feed value into it. After that we only need to pass it into RNN directly.
Code example:
`
Code example:
init_state = cell.zero_state(batch_size[0], tf.float32)

init_state = tf.identity(init_state, 'init_state') #Actually it works without this line. But it can be useful

_lstm_state_ = tf.contrib.rnn.LSTMStateTuple(init_state[0, 0, :, :], init_state[0,1,:,:])

preds, final_state = tf.nn.dynamic_rnn(cell, x, initial_state=(_lstm_state_,), parallel_iterations=1)

`
Imo, this solution much scalable (e.g. for adding more layers) than creating placeholder for each LSTM layer parameter.


FrontEnd: Colors in CSS

Description 📜
I would describe the different ways or methods in which one can specify the colors in CSS.I would also document how we can add text color, background color etc. using CSS.

Domain of Contribution 📊

[ ] Android Dev (Flutter, Java, Kotlin)
[ ] Backend Dev (Java, .NET, Python)
[ ] C/CPP
[ ] Competitive Programming
[ ] Cyber Security
[ ] DSA
[ ] Database
[ ] Datascience with Python
[ ] Datascience with R
[x] Frontend Dev (HTML, CSS, JS)
[ ] Frontend Dev (React, Angular, Vue)
[ ] Golang
[ ] Interview Prep
[ ] Java
[ ] JavaScript
[ ] MERN
[ ] Machine Learning
[ ] Open Source
[ ] Python
[ ] Rust
[ ] Statistics
[ ] UI/UX

/assign

/assign

/assign

\assign document

\assign

\assign

/assign

I would like to work on the issue with documentation. Batch 18 Frontend Subhradwip Kulavi

@Ayan-thecodeking can you please assign this to me

/assign documentation

\assign Document

@Ayan-thecodeking can you please assign this to me

go ahead @ArpitaGupta4086


memray table/tree/flamegraph/summary should accept more than one result argument

Feature Request
Would be nice if I could do:
memray table dump/*.bin

instead of
memray table dump/a.bin
memray table dump/a.bin
memray table dump/c.bin

Describe the solution you'd like A clear and concise description of what you want to happen.
Add any considered drawbacks.
When more than one result is passed evaluate it in a loop.
Describe alternatives you've considered A clear and concise description of any alternative
solutions or features you've considered.
Keep requiring 3 calls.
Teachability, Documentation, Adoption, Migration Strategy If you can, explain how users will be
able to use this and possibly write out a version the docs. Maybe a screenshot or design?
Feels like by intuition it should just work, so should be easy to teach.

We have discussed this feature and we have decided to reject it because this is possible to do with a simple shell loop and supporting this in the reporters will add some complexity as some flags like -o wouldn't make sense if multiple inputs were given.


Allow Pass-through (of Sorts) of RecognitionResult/MessageResponse

Feature Request

The ask is to allow (a variation) of the RecognitionResult/MessageResponse to pass-through to the client to transcription (RecognitionResult) and for chat messages (MessageResponse).
Describe alternatives you've considered

You need both for those use cases!
Additional context

NA

PR Merged: https://github.com/dvonthenen/enterprise-reference-implementation/pull/28
Closing!


mergeSchema - fragment node doesn't match new names

Currently the way fragment is passed from resolvers to schema is made through exact match of type names and fields on a subschema query filtering level. It should first happen before the subschema, on a mergedSchema level, thus allowing passing fragments for "top level" delegates.
Example

Fixed by https://github.com/apollographql/graphql-tools/commit/a0e5e2ca91219739a48be959403502edc168c354#diff-d1c31d9764c4c5294b2d2d4dd94457a7


Swift.BinaryInteger's signum() type is Self

I noticed that Swift.BinaryInteger's signum type is Self and not Int. Sigh. I feel like I should add an Int requirement.

This is one of those things you never notice because all the comparison operators are generic, so the signum return value is almost always implicitly converted to whichever type you're comparing it against.

Is it possible to write a macro that reminds you of default implementations you’ve not overridden? Sounds like it would be useful.

I looked it up because I thought it might be an associated type. Who messed with the timeline without my permission? Zzz 🫠

If I decide to require the Self.Digit version, I might remove the Int one.

I'll add a Digit requirements to NBKBinaryInteger and remove the current Int methods.
func signum() -> Self  // ✅
func signum() -> Digit // ✅
func signum() -> Int   // ❌

The Self requirement comes from Swift.BinaryInteger, so it's not like I can easily remove it.

I'll note that using Digit rather than Int causes a mismatch with compared(to:) -> Int. Hm.

Also, I remember why I thought the signum used an associated type. I thought it did because the stride does.

OK. In the fullness of abstraction, I think any Integer protocol should have a Signum associated type which corresponds to a signed machine word. In Swift, this corresponds to Int, and it will never be anything else so adding an associated type for it only serves to make generic signatures longer. It would be nice, however, if Swift had a feature that allowed you to assume the type of an associated type when it is unspecified. Swift does have a similar, yet different, feature where you can assign a default associated type. The difference being that I would need, for the sake of abstraction, a default associated type constraint.


Store tau and eta

Hi @matt-frey: I was wondering about merging in this branch, the changes to detect parcel points that add up in the same grid cell, and some latest changes. Is this one ready to merge?

@sjboeing I think so. Do we want to apply this change now? If yes, it makes sense to merge this branch first and then do a new pull request.

@sjboeing I added another option (cannot be set by the user though) in order to catch the restart case with tau and eta. See also https://github.com/matt-frey/epic/pull/276/commits/624ae1e490a875aa9529810554884b5a34d5668d. I think this PR is ready for review.


[bug] Protection values not refreshed

Version
Checklist:

[x] I am not using Home Assistant. Or: a developer has told me to come here.
[x] I have checked the troubleshooting section and my problem is not described there.
[x] I have read the changelog and my problem is not mentioned there.

Build/Run method

[ ] Docker
[ ] PKG
[x] Snap package
[ ] Manually built (git clone - yarn install - yarn run build )

Zwavejs2Mqtt version: 5.11.0
Z-Wave JS version: 8.7.5
Describe the bug
On a Fibaro FGD-212 dimmer, I use protection commands to prevent using the physical switch the night (thank you children ;) )
When I change the value in the control panel (or from mqtt), the change is effectuve but I have the old value
To Reproduce
I've made a screen recording of the reproduction: https://www.screencast.com/t/aX5b6cZFJ
Expected behavior
When I change the protection, I want to see the new value
Additional context
I have attached log files.
Nota, in the logs, I do the counter than in the video
In the video, I try to set No Operation Possible
In the log I try to set [Unprotected]
zwavejs_2021-11-18.log
zwavejs2mqtt_2021-11-18.log

If the value isn't updated It means I don't receive a value updated event. This could happen when the device isn't reporting it to zwave and the reason could be on device configurtations or a bug in device firmware.
cc @AlCalzone

An additional information, before I was on OZW 1.4 and when I was changeng the protection, I had the new new value

Hm, seems like that value is actually not refreshed.


runpod.start_pod(pod.id) don

runpod.start_pod(pod.id) don't work.
After inserting the pod.id, the runpod.start_pod command doesn't work. There was an attribute error that says that "AttributeError: module 'runpod' has no attribute 'start_pod'". There was no problem with runpod.stop_pod(pod.id), and runpod.terminate_pod(pod.id). Just the start_pod function.

Its called resume_pod() not start_pod().

OK. Just tried it, but got another error:
"QueryError: There are not enough free GPUs on the host machine to start this pod.". This is strange because I just entered 1 for the gpu_count parameter. I also checked that there are sufficient GPUs available in runpod, so that shouldn't be the problem.

Probably no GPU available on the host your pod is on, best to check it in the GUI.
Although the GUI says there are GPUs available, you need it to be available on the host machine that your pod is on.


Looks huge in 1080

It used to look fine, but I think the changes to accomodate for 4k screen made things look huge in 1080 screens.

Please note the version you are using (manually build newest, or stable 3.0.0)

Didn't manage to reproduce on a 1080p screen, can you try sending a picture of what it looks like ?

@RononDex was able to reproduce a similar glitch, I fixed it so i'm closing this for now, feel free to reopen if the issue is still there on the 3.1.0


docs don't just work

Following docs at https://github.com/cloudfoundry-incubator/lattice/blob/master/development/README.md to build lattice from a feature branch.
After running brew install boot2docker
$ development/setup
...
github.com/cloudfoundry-incubator/lattice/cell-helpers/tee2metron
Post http:///var/run/docker.sock/v1.19/images/create?fromImage=cloudfoundry%2Flattice-pipeline%3Alatest: dial unix /var/run/docker.sock: no such file or directory. Are you trying to connect to a TLS-enabled daemon without TLS?

@davidwadden  suggested:
$(boot2docker shellinit)`

`docker ps` should show empty list not error

then if you `docker pull cloudfoundry/lattice-pipeline`  and then `docker images` it should show in the list

Following guidance of error responses, I ran boot2docker init and boot2docker up before (boot2docker shellinit) would run. Still getting the same error as with development/setup:
$ docker ps
Get http:///var/run/docker.sock/v1.19/containers/json: dial unix /var/run/docker.sock: no such file or directory. Are you trying to connect to a TLS-enabled daemon without TLS?

The docs don't say anything about  docker pull cloudfoundry/lattice-pipeline. Anyway, same error.
$ docker pull cloudfoundry/lattice-pipeline
Post http:///var/run/docker.sock/v1.19/images/create?fromImage=cloudfoundry%2Flattice-pipeline%3Alatest: dial unix /var/run/docker.sock: no such file or directory. Are you trying to connect to a TLS-enabled daemon without TLS?

closing in favor of #157


Release Google.Cloud.Dialogflow.V2 version 4.14.0

Changes in this release:
New features

Add the enable_extended_streaming flag (commit 7db6a56)

Created release for Google.Cloud.Dialogflow.V2-4.14.0


5571migrate tests to junit5

PR description
issue #5571
Fixed Issue(s)

#5571

this one is superseded by #5571 - right? can this one be closed?

Yes, #5571 can be closed.

closing this one as it's a subset of #5571


Update Snorkel blurb

Add bit on comparison with DeepDive
Add pointers to / notes about various contrib libraries (current and upcoming) + explain relation to Snorkel / DP
General editing pass

Also: Add a section on release notes!


roblox

Please fill out the issue checklist below and provide ALL the requested information.

[x] I reviewed open and closed github issues that may be related to my problem.
[ ] I tried updating to the latest version of the CF CLI to see if it fixed my problem.
[ ] I attempted to run the command with CF_TRACE=1 to help debug the issue.
[ ] I am reporting a bug that others will be able to reproduce.

Describe the bug and the command you saw an issue with
Provide details on what you were trying to do (and why).
What happened
A clear and concise description of what happen.
Expected behavior
A clear and concise description of what you expected to happen.
Exact Steps To Reproduce
Steps to reproduce the behavior; include the exact CLI commands and verbose output:

Run cf ...
Bind a service cf bind-service
See error

Provide more context

platform and shell details ( e.g. Mac OS X 10.11 iTerm)
version of the CLI you are running
version of the CC API Release you are on

Notes regarding V6 and V7 CLI support:

V6:

Minimum supported version of CF Deployment: v7.0.0 (CAPI Release: 1.74.0 (APIs 2.128.0 and 3.63.0))
Maximum supported version of CF Deployment: v13.4.0 (CAPI Release: 1.94.0 (APIs 2.149.0 and 3.84.0))

V7:

Minimum supported version of CF Deployment: v13.5.0 (CAPI Release: 1.95.0 (APIs 2.150.0 and 3.85.0))

roblox hac

roblox hacked


Colors added in IB from a separate Pod always fail tests, but still work when running

When applying a color from an Asset Catalog that exists in another Pod to an element in Interface Builder, the test that gets created to validate that the color can be loaded will always fail.
The problem stems from the fact that it's assumed the color exists in R.hostingBundle, which isn't the case when the Asset Catalog exists in another Pod. However, the .xib or .storyboard file does nothing to help the situation, because there is no indication of the bundle the color exists in. Surprisingly, despite the IB file not having that information, the color loads perfectly at runtime.

I have included a sample app, RSwiftColors (at the bottom) that will reproduce the issue if you run the tests. The line that fails is
UIKit.UIColor(named: "CoolColor", in: R.hostingBundle, compatibleWith: nil) == nil

At first I thought maybe colors are special, and passing a nil bundle will result in the framework searching for the color, it seems like that's what IB is doing anyway.
UIKit.UIColor(named: "CoolColor", in: nil, compatibleWith: nil) == nil

That fails too. However, specifying the correct bundle works as you would expect
UIKit.UIColor(named: "CoolColor", in: Bundle(url: Bundle.main.url(forResource: "SeparateBundle", withExtension: "bundle")!)!, compatibleWith: nil)

To be honest I don't know what the best solution to this problem is. R.swift does have a knowledge of all the colors from Asset Catalogs included in the main bundle, so for a workaround if the color included in the IB resource doesn't match, it's excluded from validate. But that also defeats the entire purpose of the test, making it basically pointless.
The other solution is much more technical. If the select target has a [CP] Copy Pods Resources build phase, it can grab the output .xcfilelist from that phase and grab up all the Asset Catalogs from there, identifying the correct bundle to associate with each color. The impact here is 2-fold, performance and the added fragility due to the coupling with Cocoapods.
Perhaps somebody who understands more about how colors within Asset Catalogs actually works can help come up with a more elegant solution.
RSwiftColors.zip

Hmm.... interesting...
I think using a color from a separate bundle isn't a supported feature in UIKit, and Interface Builder showing the color in the picker is a bug.
If you change the color in the asset catalog of the separate bundle, and relaunch the app, it will still show the old color. That old color was saved in the Storyboard when it was last opened in Interface Builder.
If you change the color in the asset catalog of the main bundle, and relaunch the app, it will show the new color.

@tomlokhorst good observation, the color value is definitely cached in the storyboard until the storyboard is relaunched and updated.
I was able to get an extra layer of verification by printing the textColor of the UILabel, and also printing the color fetched via UIColor(name:bundle:).
Before changing the color in the pod bundle:
Optional(UIExtendedSRGBColorSpace 0 1 0 1)
Optional(kCGColorSpaceModelRGB 0 0 1 1 )

After changing the color in the pod bundle:
Optional(UIExtendedSRGBColorSpace 0 1 0 1)
Optional(kCGColorSpaceModelRGB 0 0 1 1 )

So the named color did change, but the storyboard didn't just like you suggested. It's understandable that the feature doesn't work, since image resources don't work like that either and collisions would cause problems. I was just excited for the possibility that Apple somehow supported it.
I'll close out this issue.


Allowing send + sync for Context

I'm not sure whether it's safe to make Context send, but I'm currently failing to share an Arc<Mutex<Context>> due to
`*const extern "C" fn(*mut pulse_sys::pa_context, *const i8, *mut pulse_sys::pa_proplist, *mut std::ffi::c_void)` cannot be sent between threads safely

I'm not sure if it helps, this is the full log output when trying to do:
(move || ) the context Arc<Mutex<_>>

help: within `pulse::context::Context`, the trait `std::marker::Send` is not implemented for `*const extern "C" fn(*mut pulse_sys::pa_context, *const i8, *mut pulse_sys::pa_proplist, *mut std::ffi::c_void)`
   = note: required because it appears within the type `std::marker::PhantomData<*const extern "C" fn(*mut pulse_sys::pa_context, *const i8, *mut pulse_sys::pa_proplist, *mut std::ffi::c_void)>`
   = note: required because it appears within the type `pulse::callbacks::MultiUseCallback<(dyn std::ops::FnMut(std::string::String, pulse::proplist::Proplist) + 'static), extern "C" fn(*mut pulse_sys::pa_context, *const i8, *mut pulse_sys::pa_proplist, *mut std::ffi::c_void)>`
   = note: required because it appears within the type `pulse::context::CallbackPointers`
   = note: required because it appears within the type `pulse::context::Context`
   = note: required because of the requirements on the impl of `std::marker::Send` for `std::sync::Mutex<pulse::context::Context>`
   = note: required because of the requirements on the impl of `std::marker::Send` for `std::sync::Arc<std::sync::Mutex<pulse::context::Context>>`

I'm trying to share a Context & Mainloop with a hyper thread, both wrapped inside an Arc<Mutex<_>>, so my only option for now would be to handle these in a new thread and use an mpsc channel to communicate between them.

I've made my struct send + sync and have no problem, so it should be okay to add this to mainloop & context.

Ok, I have not done a properly thorough investigation, but I have evaluated it and spend a fair bit of time coming through various bits and pieces. With the threaded mainloop you need to hold the lock while using objects, thus so long as you do that, I believe everything should be fine, as discussed in the relevant commit I have made and its changelog entry. I have released v2.5 with the necessary change :)
Also, I found a use-after-free bug whilst looking into this, so thanks for prompting me to do so :)

Hi, many thanks for investigating.
I'm running my hotfix stuff inside a tokio engine between multiple hyper instances and have not faced any issue for far.
Regarding your problem of users forgetting to acquire a lock:
AFAIK you could make the methods require &mut self instead of &self, this way borrowck would enforce using a mutex.


yaml - ignorePreflightErrors need to under nodeRegistration

file: kubeadm-config.v1beta3.md
ignorePreflightErrors need to under nodeRegistration.

That is exactly what the reference is saying.

I think you're suggesting a clarification to https://kubernetes.io/docs/reference/config-api/kubeadm-config.v1beta3/ @felixlutq
Have I got that right?

https://kubernetes.io/docs/reference/config-api/kubeadm-config.v1beta3/
In the example:
apiVersion: kubeadm.k8s.io/v1beta3
kind: InitConfiguration
bootstrapTokens:

token: "9a08jv.c0izixklcxtmnze7"
description: "kubeadm bootstrap token"
ttl: "24h"

token: "783bde.3f89s0fje9f38fhf"
description: "another bootstrap token"
usages:

authentication

signing

groups:

system:bootstrappers:kubeadm:default-node-token

nodeRegistration:
name: "ec2-10-100-0-1"
criSocket: "/var/run/dockershim.sock"
taints:

key: "kubeadmNode"
value: "master"
effect: "NoSchedule"

kubeletExtraArgs:
v: 4

ignorePreflightErrors:

IsPrivilegedUser
imagePullPolicy: "IfNotPresent"

localAPIEndpoint:
advertiseAddress: "<IP_ADDRESS>"
bindPort: 6443
certificateKey: "e6a2eb8581237ab72a4f494f30285ec12a9694d750b9785706a83bfcbbbd2204"
skipPhases:

addon/kube-proxy

From: Tim Bannister @.>
Sent: Wednesday, 9 March 2022 12:30 AM
To: kubernetes/website @.>
Cc: felixlutq @.>; Mention @.>
Subject: Re: [kubernetes/website] yaml - ignorePreflightErrors need to under nodeRegistration (Issue #32125)
I think you're suggesting a clarification to https://kubernetes.io/docs/reference/config-api/kubeadm-config.v1beta3/ @felixlutq https://github.com/felixlutq
Have I got that right?
—
Reply to this email directly, view it on GitHub https://github.com/kubernetes/website/issues/32125#issuecomment-1061837537 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AYEAGDK7DB3YV4EE3HUKL5TU65P6JANCNFSM5QGHXKKQ .
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675  or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/AYEAGDP424E2ZTSEPJF4UCLU65P6JA5CNFSM5QGHXKK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOH5FFVYI.gif Message ID: @.*** @.***> >

https://kubernetes.io/docs/reference/config-api/kubeadm-config.v1beta3/
In the example:
apiVersion: kubeadm.k8s.io/v1beta3
kind: InitConfiguration
bootstrapTokens:

token: "9a08jv.c0izixklcxtmnze7"
description: "kubeadm bootstrap token"
ttl: "24h"

token: "783bde.3f89s0fje9f38fhf"
description: "another bootstrap token"
usages:

authentication

signing

groups:

system:bootstrappers:kubeadm:default-node-token

nodeRegistration:
name: "ec2-10-100-0-1"
criSocket: "/var/run/dockershim.sock"
taints:

key: "kubeadmNode"
value: "master"
effect: "NoSchedule"

kubeletExtraArgs:
v: 4

ignorePreflightErrors:

IsPrivilegedUser
imagePullPolicy: "IfNotPresent"

localAPIEndpoint:
advertiseAddress: "<IP_ADDRESS>"
bindPort: 6443
certificateKey: "e6a2eb8581237ab72a4f494f30285ec12a9694d750b9785706a83bfcbbbd2204"
skipPhases:

addon/kube-proxy

From: Qiming Teng @.>
Sent: Wednesday, 9 March 2022 12:17 AM
To: kubernetes/website @.>
Cc: felixlutq @.>; Mention @.>
Subject: Re: [kubernetes/website] yaml - ignorePreflightErrors need to under nodeRegistration (Issue #32125)
That is exactly what the reference is saying.
—
Reply to this email directly, view it on GitHub https://github.com/kubernetes/website/issues/32125#issuecomment-1061824908 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AYEAGDK42LNGRS4VYKUZDKTU65OPLANCNFSM5QGHXKKQ .
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675  or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/AYEAGDIGSMAXPIYXZS3DMJDU65OPLA5CNFSM5QGHXKK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOH5FCTDA.gif Message ID: @.*** @.***> >

Hi @felixlutq
I'm going to edit your follow-up for readability - to make the YAML formatting more obvious.

That YAML from the email message is equivalent to:
---
apiVersion: kubeadm.k8s.io/v1beta3
kind: InitConfiguration
bootstrapTokens:
- token: "9a08jv.c0izixklcxtmnze7"
  description: "kubeadm bootstrap token"
  ttl: "24h"
- token: "783bde.3f89s0fje9f38fhf"
  description: "another bootstrap token"
  usages:
  - authentication
  - signing
  groups:
  - system:bootstrappers:kubeadm:default-node-token
nodeRegistration:
  name: "ec2-10-100-0-1"
  criSocket: "/var/run/dockershim.sock"
  taints:
  - key: "kubeadmNode"
    value: "master"
    effect: "NoSchedule"
  kubeletExtraArgs:
    v: 4
ignorePreflightErrors:
- IsPrivilegedUser
   imagePullPolicy: "IfNotPresent"
localAPIEndpoint:
  advertiseAddress: "<IP_ADDRESS>"
  bindPort: 6443
certificateKey: "e6a2eb8581237ab72a4f494f30285ec12a9694d750b9785706a83bfcbbbd2204"
skipPhases:
- addon/kube-proxy

It looks like the rest of your follow-up message is missing @felixlutq. I can see the start of a sentence, “In the example:”, but not the remainder.
/triage needs-information.

/triage needs-information

Okay, that  makes sense. The example might be wrong. I'll look into it.

/sig cluster-lifecycle

looks like both https://github.com/kubernetes/kubernetes/blob/master/cmd/kubeadm/app/apis/kubeadm/v1beta2/doc.go and https://github.com/kubernetes/kubernetes/blob/master/cmd/kubeadm/app/apis/kubeadm/v1beta3/doc.go have some minor indentation issues. i though that we fixed these (apparently not).
i can send PR for k/k later today.

/triage accepted
/kind bug
/remove-triage needs-information

/assign
Reference is being regenerated using the updated doc comments.


sdnotify (READY) support

I am in progress (learning howto) to create and run the containers fully under systemd by utilizing the quadlets system which is part of Podman >4.4
One of the benefits of it is to use the sdnotify system to let systemd know when a started container is fully loaded and ready.
"--sdnotify=container" instead of "--sdnotify=conmon"
For this to work, we need to use the systemd wrappers as start entry point within the containers. As there is no downside of using the wrappers while not using the sdnotify system itself, I would like to ask to make it the default entry point such that I can just pull the images from the registry instead of building them myself.

I'll have to check but I don't think sdnotify is supported by Docker.

Did some research and indeed, --sdnotify is not supported by Docker.
--sdnotify seems to be by default set with container.
podman inspect ovos_stt_fasterwhisper | jq .[].Config.sdNotifyMode
"container"

For podman systemd integration having the ovos service reporting back that it is ready to rock and roll, we need to include the systemd wrappers within the containers and change the entry points to use them.
https://github.com/OpenVoiceOS/ovos-buildroot/tree/5c7af8b05892206846ae06adb3478f1df620bf6b/buildroot-external/rootfs-overlay/base/usr/libexec
You need the mycroft-systemd-* files.

As example for the messagebus service, instead of having the ENTRYPOINT = "ovos-messagebus" we will have to change the entry point to; calling that wrapper file  "mycroft-systemd-messagebus".
It does the same, starting the messagebus service, houwever really sending the sdnotify READY back to the system.
That way we can use the --sdnotify=container podman flag to let systemd know the service itself is fully ready, instead of the container has been launched. (the container could be launched but system will otherwise not know if the messagebus itself is also fully started/ready)

I think theae files should be part of a Python package on PyPi and renamed to ovos.
What do you think?

all of the systemd hook files on PyPi?  That would make things easy

Agree! Will ping @JarbasAl for when he is back from holidays.

all of the systemd hook files on PyPi? That would make things easy

i dont mind adding those entrypoints to the repos, but sdnotify should not be a hard dependency (as we want to support non systemd services too), either add a new entrypoint or make the sdnotify import optional in the main entrypoints (use it if its there else ignore)

That would probably be the quickest way to make it optional for sure.

I once made this;
https://github.com/j1nx/mycroft-systemd
I could transfer it so we can bump/ change the files.

I once made this; https://github.com/j1nx/mycroft-systemd
I could transfer it so we can bump/ change the files.

Yeah and maybe build a PyPi package based on specific directory.

That's what I was thinking when I looked also.

Here we go!
https://github.com/OpenVoiceOS/ovos-systemd
No clue about PyPi packaging but gave access to any distro admin, so we should be able to get it up to date.

@builderjer Did you started the work on the systemd wrappers already?
I just discovered that for the auto-update/rollback feature of podman it actually needs the "sdnotify=container" flag as the rollback uses it to determine if the update was succesfull or not.

Not entirely true anymore;
https://github.com/containers/podman/pull/19353
Looks like we can also use the healthy checks now to report back to systemd. Will do some testing with it.

@j1nx  what happens if systemd is not running on the system (like SysV)?

I'll close this issue as for now this will not be implemented.


Update downgrades on 2018.2

Prerequisites

[x] Plugin is in the latest version
[x] Issue was not reported yet
[x] Stack trace (if provided) contains mobi.hsz.idea.gitignore package name

Steps to Reproduce

Install AS 3.2 (2018.1.6)
Install .ignore plugin
Update to AS 3.3 (2018.2.?)

Expected behavior:
Update installs newer version, if at all
Actual behavior:
After update, IDEA wants to install an older version:

Reproduces how often:
only had one installation to upgrade, but I suspect 100%
Versions
Plugin:
<IP_ADDRESS> was used on AS 3.2

IDE:
Android Studio 3.3
Build #AI-182.5<IP_ADDRESS>99772, built on December 25, 2018
JRE: 1.8.0_152-release-1248-b01 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o

OS:
Windows 10 10.0

I'm experiencing similar issue. After I did update to IJ 2018.3, I was forced to downgrade .ignore plugin down to version 2.6.2.

IDE in version 2018.2+ will be supported again with the upcoming release v3.1.1

Fixed and released with v3.1.1

I just got a prompt to downgrade from <IP_ADDRESS> to 2.6.2 again.


Bluetooth: controller: Error in handling invalid PDU in LLCP, leading to ASSERT

A situation with a central not rejecting overlapping local initiated PHY_REQ, but instead sends PHY_UPD_IND has been seen, leading to a situation where 'our' peripheral will have both remote and local procedure expecting a PHY_UPD_IND PDU and will thus hit the ASSERT 'That cannot happen' in ull_cp_rx().
Solution is to refactor and handle the invalid behaviour as elsewhere - and terminate connection.
Also refactor to ensure that a local procedure that is 'overtaken' by a central initiated counterpart should no longer expect PDUs other that UNKNOWN_RSP and REJECTs
This is fixed by: https://github.com/zephyrproject-rtos/zephyr/pull/56840

Please use our bug template when reporting bugs. You need to edit this issue to include the needed information from https://github.com/zephyrproject-rtos/zephyr/blob/main/.github/ISSUE_TEMPLATE/bug_report.md

Fixed in https://github.com/zephyrproject-rtos/zephyr/pull/56840


Process never ends when migrating

Right now when we do a migration, e.g. with
npx truffle migrate --network rinkeby

it does do the migration, but the process never actually stops and goes back to bash. Instead, after the final Saving artifacts... message it just hangs.
Not sure if that's a problem with our migration steps or what.
It's annoying, and means we can't automate this process with a script.
The hacky way to fix it would be, I guess, to make a migration script named 999_exit.js which just does a process.exit() . Feels dirty, but better than nothing?

This might be fixed with latest version of truffle: https://github.com/trufflesuite/truffle/releases/tag/v4.1.10

Fix for a bug that was causing Truffle to hang or error as commands exit when connected to Infura, especially when using the newest release of truffle-hdwallet-provider. Thanks @roderik for helping debug this.


HHH-10349 : PersistenceUtilHelper should call getDeclaredField/Method…

… inside of privileged block

Merged.

Cool


Skandinaviska Enskilda Banken AB (publ) wish to run a sealer node

Company

Full legal name: Skandinaviska Enskilda Banken AB (publ)
Company website: http://www.sebgroup.com
Representative contact name: Sahand Javidi
Representative contact email<EMAIL_ADDRESS>Additional contacts: Johan Hörmark, Anders Hallme, Wiktor Hejchman
Additional contact emails<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
I hereby recognize that our company does not already have a Node in this network
Sealer Node

Sealer address: <0xf0f8ccb45672efbd8050571706fb016833b28225>
Link: TBD

Motivations
SEB wants to run nodes as a part of the Digital Bond issuance in Project Saturn, where SEB collaborates with CACIB to create a network used for managing the Digital Bond.

@wiktorhejchman I try to add this node but it didn't start creating blocks. Can you check that you have activated the mining properly ?

@wiktorhejchman @rghoshfinaxys this sealer is now added 1 vote (over 2 needed)

@wiktorhejchman @rghoshfinaxys 2 nodes have votes now. You should be sealing properly now


Vue.js is detected but the Vue Panel is not showing

Version
5.3.3
Browser and OS info
Chrome 83.0.4103.97 / Windows 10
Steps to reproduce
After enter the page Vue.js is detected on this page. The message "Open DevTools and look for the Vue panel" at the Vue-devtools icon.
What is expected?
Appears Vue Panel on DevTools
What is actually happening?
It's not appearing

I found this  suggestion that worked for me. It is a good work around.

Go to the DevTools settings
Under Apperance, choose a different theme
The Vue Panel should be back now in DevTools
Go back to dev tools settings and put your theme back to what you had before
The Vue Panel should still be there

I hope this works for you too.

I have the same issue here with Chrome Version 83.0.4103.97 (Official Build) (64-bit).
Updating the theme didn't fix the issue, the vue tab is still not visible.

F#@k!!!, I've lost many many time with this!!!! Thanks @landocalris

Worked for me! Thanks @landocalris

The above workaround does not work in Firefox.

I'm having the same problem and none of these suggestions nor any other I've been able to google is causing it to show again.  Dang it's much harder to developer when I can't see my state.
macOs Catalina 10.15.5
Version 83.0.4103.106 (Official Build) (64-bit)

Here doesn't work either.

Well this doesn't seem to always fix the issue for me. very frustrating

I can confirm the workaround (https://github.com/vuejs/vue-devtools/issues/1209#issuecomment-641916382) with Chrome Version 84.0.4147.105 (Official Build) (64-bit) on mac os x 10.14.6

Make sure that Vue is not accidentally set in production mode. For me changing it to Development Mode fixed the issue.

Same problem on OSX 10.15.6 and Chrome 85.0.4183.83. None of the above-mentioned solutions have worked.

I found this  suggestion that worked for me. It is a good work around.

Go to the DevTools settings
Under Apperance, choose a different theme
The Vue Panel should be back now in DevTools
Go back to dev tools settings and put your theme back to what you had before
The Vue Panel should still be there

I hope this works for you too.

Switch on or off the plugin several times, and then change the theme
Or turn off the devtools of vue2, and then change the theme

Thank You Its Work For Me
On Mon, Sep 21, 2020 at 1:22 PM Wells Su<EMAIL_ADDRESS>wrote:

Switch on or off the plugin several times, and then change the theme
Or turn off the devtools of vue2, and then change the theme

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/vuejs/vue-devtools/issues/1209#issuecomment-695947091,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AL2B5WCWVFUEDYFY3FIRIILSG35K5ANCNFSM4NYNRQHQ
.

This worked for me.
https://github.com/vuejs/vue-devtools/issues/620#issuecomment-699594776

Works like a charme! Thank you! Here a screenshot of how to find the appearance settings for dummies like me :-D

Switch on or off the plugin several times, and then change the theme
Or turn off the devtools of vue2, and then change the theme

This worked for me. Thanks.

turning off the vue2 devtools and changing the theme worked for me.

Nothing worked for me - until I opened the devtools settings, and clicked 'restore defaults and reload" in the bottom right of the settings screen.
Vue pane now visible. :-)

work for me - up vue-router to vue-router@next, firstly just installed router for vue2

Deleting and re-installing the vue devtools (beta version) plus restoring the devtools defaults for chrome did the trick for me.

I found this  suggestion that worked for me. It is a good work around.

Go to the DevTools settings
Under Apperance, choose a different theme
The Vue Panel should be back now in DevTools
Go back to dev tools settings and put your theme back to what you had before
The Vue Panel should still be there

I hope this works for you too.

Thank you so. It works.

Tried all the suggestions and none worked for me with the beta plugin and Vue 3.
On browser Chromium, Chrome and Brave, on Ubuntu 20.04.

I just removed the regular vue devtools and installed beta version for vue3 and it worked for me.

I just removed the regular vue devtools and installed beta version for vue3 and it worked for me.

I found this  suggestion that worked for me. It is a good work around.

Go to the DevTools settings
Under Apperance, choose a different theme
The Vue Panel should be back now in DevTools
Go back to dev tools settings and put your theme back to what you had before
The Vue Panel should still be there

I hope this works for you too.

Your solution worked for me. Thanks

I just removed the regular vue devtools, installed beta version for vue3 and it worked for me.

Actually, this worked for me, but I had to do an additional step. All in all, these are the steps:

remove regular vue devtools
remove the new vue devtools (since i have them both installed)
re-add the new vue devtools

That's it.

I just removed the regular vue devtools, installed beta version for vue3 and it worked for me.

Actually, this worked for me, but I had to do an additional step. All in all, these are the steps:

remove regular vue devtools
remove the new vue devtools (since i have them both installed)
re-add the new vue devtools

That's it.

thanks ~  haha

I found this  suggestion that worked for me. It is a good work around.

Go to the DevTools settings
Under Apperance, choose a different theme
The Vue Panel should be back now in DevTools
Go back to dev tools settings and put your theme back to what you had before
The Vue Panel should still be there

I hope this works for you too.

Install vue dev tool beta from here, then try these steps

None of these work for me, still facing the issue.

Thanks, @B45i this helped.  Also, it may help to have the Beta version instead of the regular version.

Beta version works. But why stable version not?

@camohub Stable doesn't support Vue 3

This works for 6.x version, you need to remove or disable 5.x version before doing this.

I found this  suggestion that worked for me. It is a good work around.

Go to the DevTools settings
Under Apperance, choose a different theme
The Vue Panel should be back now in DevTools
Go back to dev tools settings and put your theme back to what you had before
The Vue Panel should still be there

I hope this works for you too.

The workaround does't work for me on Chromium v83.

Yep, turning the extension off and on again actually did work
https://www.youtube.com/watch?v=p85xwZ_OLX0

My case is I used a internal vue.js, which does not have a .min extension, but its content seems like a minimized version... If those workarounds not help, maybe you should check your vue resource is not vue.min.js

I installed the beta version, and I also had to play with the settings, finally worked! Thank you!

remove all the plugins, just like react, redux, vue-performance, old vue devtool....
restart your chrome
wow ,it works!

For me this was critical:
When I install plugin for short moment in upper right chrome corner the VUE ICON appears with message (screenshot is not my):

And CRITICAL is to click right button on that icon and choose "PIN" (it to extensions icons bar) - if you not do it - then you will never see that icon again (which is mistake). After that shut down and reopen chrome. And now in you page with vue, this icon sould have  green colors (you can click on it) - and in chrome console you should see

I had already installed the Beta version, removed the old version of Vue devtools, but it still wasn't working, then I finally closed devtools and reopened them, and the tab showed up!
TL;DR: if nothing works for you, try just closing the panel and reopen the Chrome devtools panel!

https://devtools.vuejs.org/guide/faq.html#the-vue-devtools-don-t-show-up

For what it's worth, reloading the Chrome Devtools window also works, and I suspect the "new theme" trick works because it includes a Chrome Devtools reload under the hood.
The MacOS keyboard (when Devtools is focused, at least) is Option+R. You can also bring up the Command Palette in Devtools and type "reload".
Note: This is incredibly and inexplicably hard to Google, and it's not documented in Devtools docs as far as I can tell. This is really bizarre, because it seems like pretty core functionality and is very helpful in cases like these.

I tried closing the dev tool and did a hard refresh (shift + click the reload icon on Mac) and it worked.

How do you open "Devtool Settings" ? I don't see this?

How do you open "Devtool Settings" ? I don't see this?

@clwilliams8 it's the gear icon. But my reload trick should work and is quicker, let me know if it's working for you?

thanks for the help. for me it ended up that i wasn't running my vite complier 🤷🏼♂

I tried everything and it just did not work for me at all. and btw how do I install the beta version !

Restore defaults and reload in Dev Tools settings worked for me

In my case I just restored to default settings and viola it's showin in panel now.

@vinit095 's solution is the only thing that worked for me.  I tried un/re-installing the extension, upgraded Chrome to 122.0.6261.94, rebooted my Mac, nothing worked except this.

Restore defaults and reload in Dev Tools settings worked for me

Oh thanks that solved my problem!

I try all methods mentioned above but not work yet. After reset devtool setting, it appears:

Go to the DevTools settings
Click restore defaults and reload

None of the above solutions works when using Edge Version 124.0.2478.97 (Official build) (64-bit)


why python and yarn-model doesn't produce the same training result?

Using same parameter and dataset, the model trained from python is different from yarn cluster(dmlc-core/tracker/dmlc-submit --cluster=yarn),
I means the difference is auc, logloss which relative to predicting power, the yarn-model model is superior than python's always...
anybody come across the same issue?
[updated] When I ran the same python program in our server side, previously i ran it on my MacOS, the result almost the same as yarn cluster!!! seems this issue settled ^0^ , but i still wonder why MacOS can't produce the accurate result? ?

Not the same seed?


IGNITE-4169 DML integration w/data streamer

Closing this due to releasing DML streaming feature via different branch. New pull request:
https://github.com/apache/ignite/pull/1553


Unable to create client scope

I'm trying to create a client scope. The call is successful, but the UI of Keycloak throws an error when I want to display my new client scope.
Error message in UI: "Danger alert:n is undefined Press here to refresh and continue"
It is noticeable that openid-connect value in protocol is displayed incorrectly. For all other items "OpenID Connect" is display, but for my new client scope "openid-connect" is displayed.
The question now is whether I am executing the call incorrectly or whether there is possibly an error.
Has anyone else already had this problem?
Here is my code to create the client scope:
List<ProtocolMapper> protocolMappers = [];
ProtocolMapper mapper = new() { Name = myName, Protocol =  "opernid-connect", _ProtocolMapper = "oidc-hardcoded-claim-mapper", ConsentRequired = false };
Dictionary<string, string> mapperConfig = new()
{
				{ "access.token.claim", "true" },
				{ "claim.name", myName},
				{ "claim.value", myId},
				{ "id.token.claim", "true"},
				{ "userinfo.token.claim", "true"},
				{ "access.tokenResponse.claim", "false"}
};

mapper.Config = mapperConfig;
protocolMappers.Add(mapper);

clientScope = new()
{
				Name = newName,
				Protocol =  "opernid-connect",
				ProtocolMappers = protocolMappers,
};

await KeycloakClient.CreateClientScopeAsync(Realm, clientScope, cancellationToken);

Issue can be closed. I found my mistake: Protocol =  "opernid-connect" has an r that has crept in


SFC compiler: optional chaining generates different event

Version
3.1.4
Reproduction link
https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8ZGl2IEBjbGljaz1cImEuYlwiPkNsaWNrICh3b3Jrcyk8L2Rpdj5cbiAgPGRpdiBAY2xpY2s9XCJhPy5iXCI+Q2xpY2sgKGJyb2tlbik8L2Rpdj5cbjwvdGVtcGxhdGU+XG5cbjxzY3JpcHQgc2V0dXA+XG5jb25zdCBhID0ge1xuICBiKCkgeyBhbGVydChcIndvcmtzXCIpIH1cbn1cbjwvc2NyaXB0PiJ9
Steps to reproduce
Click on the repro divs, one works, the other doesn't.
The reason why is evident if you look at the generated JS code.
SFC compiler handles event listeners that are an expression, such as a.b, as functions themselves and invokes (...args) => a.b && a.b(args)
It does not consider a?.b to be such an expression, though, and invokes () => a?.b.
What is expected?
Both works
What is actually happening?
Only first link works

You could take this opportunity to optimise generated code a.b && a.b(...args) into a.b?.(...args).
Not only is the latter shorter, it also evaluates the first part only once, which might be relevant if there are side-effects -- and one common side-effect is reactivity tracking, so it's just more performant.
Downside: if targeting a browser that doesn't support optional chaining, the code needs to be transpiled. With evergreen broswers, everybody supports it nowadays (Chrome 80, FF 74, Safari 13.1): https://caniuse.com/mdn-javascript_operators_optional_chaining
PS: The issue creation app replaces + with   everywhere, including in the repro link and that breaks links to sfc.vuejs.org.

source:
transformOn
      const isMemberExp = isMemberExpression(exp.content);

a?.b evals to false


Cannot load Fabulous Project

How to reproduce:

Do the getting started in Fabulous documentation: https://fsprojects.github.io/Fabulous/index.html#getting=started
Build in VStudio
Open in VSCode (with Ionide)

the result for both Android and iOS project:
Status: failed to load

Error:
Could not load file or assembly 'Microsoft.Build, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. StackTrace: at Microsoft.FSharp.Compiler.SourceCodeServices.ProjectCrackerTool.ProjectCrackerTool.FSharpProjectFileInfo..ctor(String fsprojFileName, FSharpOption`1 properties, FSharpOption`1 enableLogging) at Microsoft.FSharp.Compiler.SourceCodeServices.ProjectCrackerTool.ProjectCrackerTool.getOptions@396(Boolean enableLogging, FSharpList`1 properties, Dictionary`2 cache, String file) at Microsoft.FSharp.Compiler.SourceCodeServices.ProjectCrackerTool.ProjectCrackerTool.getOptions(String file, Boolean enableLogging, FSharpList`1 properties) at Microsoft.FSharp.Compiler.SourceCodeServices.ProjectCrackerTool.ProjectCrackerTool.crackOpen(String[] argv)

Fabulous projects are partially using old/verbose fsproj files (due to Xamarin). Unfortunately, we don't support those.
Closing as wontfix


Add test for envoyfilter

Hoping this will detect https://github.com/istio/istio/issues/34356
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

/test integ-assertion-k8s-tests_istio

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
2f4bcbd98e16fb55ed0da1ebfee9d19963148c90
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
2f4bcbd98e16fb55ed0da1ebfee9d19963148c90
link
/test release-notes_istio

integ-multicluster-k8s-tests_istio
2f4bcbd98e16fb55ed0da1ebfee9d19963148c90
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test release-notes_istio

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
2f4bcbd98e16fb55ed0da1ebfee9d19963148c90
link
/test integ-multicluster-k8s-tests_istio

release-notes_istio
2f4bcbd98e16fb55ed0da1ebfee9d19963148c90
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
2f4bcbd98e16fb55ed0da1ebfee9d19963148c90
link
/test integ-multicluster-k8s-tests_istio

release-notes_istio
2f4bcbd98e16fb55ed0da1ebfee9d19963148c90
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
2f4bcbd98e16fb55ed0da1ebfee9d19963148c90
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
2f4bcbd98e16fb55ed0da1ebfee9d19963148c90
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-assertion-k8s-tests_istio

/test release-notes_istio

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-ipv6-k8s-tests_istio
2f4bcbd98e16fb55ed0da1ebfee9d19963148c90
link
/test integ-ipv6-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


Adding my file

Description 📜
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
Fixes # <issue_number_here>

Type of change 📝

[ ] Audio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)
[ ] Video (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)
[✅ ] Documentation (Content Creation in the form of codes or tutorials)
[ ] Other (If you choose other, Please mention changes below)

Domain of Contribution 📊

[ ] Android Dev (Flutter, Java, Kotlin)
[ ] Backend Dev (Java, .NET, Python)
[ ] C/CPP
[ ] Competitive Programming
[ ] Cyber Security
[ ] DSA
[ ] Database
[ ] Datascience with Python
[ ] Datascience with R
[ ] Frontend Dev (HTML, CSS, JS)
[ ] Frontend Dev (React, Angular, Vue)
[ ] Golang
[ ] Interview Prep
[ ] Java
[ ] JavaScript
[ ] MERN
[ ] Machine Learning
[ ] Open Source
[✅ ] Python
[ ] Rust
[ ] Statistics
[ ] UI/UX

Checklist ✅

[ ] I follow Contributing Guidelines & Code of conduct of this project.
[ ] I have performed a self-review of my own code or work.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] My changes generates no new warnings.
[✅ ] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

Please check it out and let me know the changes.


MongoDB may not be replicating properly

I've observed a few times when attempting to connect that my username and password are rejected. This could possibly mean mongoDB hasn't properly replicated it's data in the cluster.

Problem should be solved with the most recent deployment.


Auto orientation is broken?

I made a very basic application template:
<p>
  Lorem ipsum dolor sit amet, consectetur adipiscing elit.
</p>

{{bootstrap-datepicker}}

{{outlet}}

As you can see the datepicker is completely miss positioned.

Interestingly if I have only {{bootstrap-datepicker}} in my template, it works fine:

I guess it's a known issue https://github.com/eternicode/bootstrap-datepicker/issues/1317, and the fix is waiting for the pull request review https://github.com/eternicode/bootstrap-datepicker/pull/1329.

thanks @soulim!  good to know. Let's wait for that merge.

Seems like this problem does not belong to the component, so I'm closing this issue. Hope it'll be fixed soon in bootstrap-datepicker.


External Projects

Having a method to list external projects on the website and show people who have worked on them and scrape their commits would be useful and help promote contribution to larger projects.
This should be a simple matter of adding a toggle to a project marking it as "external"

Severino Center would be interested in a general project visiblity application like rcos.io to increase the visiblity of the innovation ecosystem.

This was completed by #68


Daily backup of YouTube Channel (without overwriting)

I've been using:
youtube-dl -f best -ciw -o "%(title)s.%(ext)s" -v URL_of_YT_channel
in order to backup YouTube channels. It does seem to rewrite the files, however. I thought the -w was not to rewrite? I'd like to run it once a day and only scrape the videos that haven't been downloaded already. What's the recommended way to do that? I also want to keep videos that were removed from the channel (I don't want them to be deleted from the backup).
Thanks!

Read FAQ.


Node Icon smaller than what's in preview

I'm using Fira Code but the Node.js icon looks smaller than how it looks in preview (I'm also on Hyper Shell)

Any idea what might be causing this?

Same issue using iTerm2
[

Duplicate of #377


Kick invalidated mysteriously

During a "Duo duel" mission after destroying the first mech (Phoenix Hawk LAM, PHX-HK2) the other (WASP LAM, WSP-100A) was sitting in a burning forest. My Hatchetman was close to it, so I tried to go melee it. No matter how many times I tried to target the Wasp for a melee attack the game instead told me I'd be walking next to it, without the melee dialog. Eventually I tried to just stand and shoot and my turn was instead passed on the Hatchetman. Annoyed, I tried moving my Firestarter closer and instead it moved and immediately finished my turn, without any chance to fire, giving the Wasp a free turn of shooting at my Hatchetman's immobile back.
After the Wasp's free turn, everything worked normally again and the Hatchetman finished the fight with a melee attack.
I've seen something similar happen on Baradul's Roguetech youtube series once or twice, although I think for him it only happened randomly for one mech, rather than entire turn getting wasted

RogueLogs(1).zip


Future updates

Will this working in future updates? Now we are at v26.00, does this works now?

#9 👋


Flight mode persistency between saves

If save is loaded where you were flying: Car slams to the ground

Potential quick workaround: prevent saving while flying.
If it's possible, you could check if the player is driving and above a certain altitude on game start and activate flight mode accordingly, all contained within the mod?

Checking for height above ground during load with raytracing seems like a pretty reasonable solution.

Just pushed a version of this (beea1c6) if you want to grab the build/ folder and test it!

What a legend. Testing.

It's working flawlessly

Awesome, thanks for testing!


Possible rejection because of private API usage

Current behavior
Describe what happens when you encounter this issue.
It hasn't happened for me yet ;)
Reproduction steps
Send iOS app to review
Expected behavior
iOS app should pass review
Platform
Which player are you experiencing the problem on:

iOS

Video sample
Any
Recently added support for request headers for iOS uses private API. AVURLAssetHTTPHeaderFieldsKey used here: https://github.com/react-native-community/react-native-video/blob/master/ios/RCTVideo.m#L338 is not officialy documented, therefore some apps might be rejected because of it.

Why cant you use documented setValue function so set header values? I am not a iOS specialist, but it would be nice if someone could check if it could be used instead of the private API call.

@c-goettert Did you have success on this?

@c-goettert any update on this?


Persistent retries

I had a couple other thoughts on this:

It should be possible to turn off. I'm not sure if the default is on or off, but some users may not have local storage for the updates or they may not want to have extra eMMC writes. E.g., Lichee Pi Zero...
If fwup exits with an error while the cached file is being replayed back, that's pretty bad since it means that prior to the crash, fwup got farther with the same data. Given that the data is protected against disk corruption by SHAs, this really shouldn't happen. I'm thinking that it should send up a failure to NH and erase the cached data.
If fwup exits while downloading firmware, the partially downloaded file should be erased. You might be doing this and I didn't read closely enough. The logic here is to prevent bytes that cause fwup to error out from being used more than once.

Btw, there's a current issue with nerves_hub_link that may make affect this work. The issue is that nerves_hub_link assumes that the currently running firmware is valid, but this isn't guaranteed. Fwup is set up to verify this and error out if you're not running validated firmware, but really nerves_hub_link shouldn't even try to apply a firmware update until it's valid. This race hits when a device is stepped through updates. I.e., it updates to firmware 1.0 and then immediately updates to 2.0. After the 1.0 update there's a race between nerves_hub_link to get the 2.0 download link and for some other software to mark the 1.0 firmware as valid. Based on how Nerves sets things up, the validation happens before nerves_hub_link starts, but that's not generally the case.


Armorblox TemplateSpec Solution

Change(s):
See guidance below
Reason for Change(s):
This PR is part of template spec solution migration for solution Armorblox.
See guidance below
Version Updated:
2.0.0
Required only for Detections/Analytic Rule templates
See guidance below
Testing Completed:
The link for test results is - https://microsoftapc.sharepoint.com/:w:/r/teams/SentinelCATTeam/_layouts/15/Doc.aspx?sourcedoc={C331DC3F-E9A4-4830-9387-DBFF0EE29EE3}&file=Sentinel Solution Migration -TemplateSpec - Armorblox.docx&action=default&mobileredirect=true&share=IQE_3DHDpOkwSJOH2_8O4p7jASay0lgO_hQGqGvIrJw8mVw
See guidance below
This is an ISV solution.

Please update Azure Sentinel to Microsoft Sentinel for below files

Are we have a separate PR for supporting the Playbook?

Closing this PR as migration of this solution will be done at next iteration.


Maestro-bot updater script failed to update release/2.1

https://devdiv.visualstudio.com/DevDiv/_build/index?buildId=1609398&_a=summary
2018-04-19T19:39:09.0680672Z Updating  version variables in E:\A\_work\26\s\build\dependencies.props
2018-04-19T19:39:21.3817970Z ##[error]error: src refspec dotnetbot/UpdateDeps does not match any.
error: failed to push some refs to<EMAIL_ADDRESS>E:\A\_work\26\s\scripts\UpdateDependencies.ps1 : Cannot bind argument to
parameter 'Message' because it is null.
At line:1 char:1
+ & "E:\A\_work\26\s\scripts\UpdateDependencies.ps1" -BuildXml https:// ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (:) [UpdateDependencies.ps1], Param
   eterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,U
   pdateDependencies.ps1

cc @ryanbrandenburg

I sent a PR for this, self-assigning to track until we've confirmed that it works through Maestro.

New error.
remote: Permission to aspnet/Universe.git denied to dotnet-maestro-bot.
Your branch is ahead of 'origin/release/2.1' by 1 commit.
  (use "git push" to publish your local commits)
E:\A\_work\26\s\scripts\UpdateDependencies.ps1 : Cannot bind argument to
Process completed with exit code 0 and had 3 error(s) written to the error stream.

Before switching to hub.exe, the way this worked is that dotnet-maestro-bot would push to its fork of Universe, https://github.com/dotnet-maestro-bot/Universe

Reacting with #1111.

For sure we should change the name, but it shouldn't matter because it's on different forks, and the PR was created.

I think VSTS isn't happy because git.exe is writing to stderr. Also, we should add a check for an existing PR and update that one instead of creating a new PR.
 Error creating pull request: Unprocessable Entity (HTTP 422) A pull request already exists for dotnet-maestro-bot:rybrande/UpgradeDepsTest.

We pushed to the same branch that the maestrobot used last time, so we DID update the PR. Do we want to update the text of the message as well?

Let's double check that we're using Invoke-Block everywhere so Powershell doesn't make us miss failures now that we're ignoring StdErr.

We're good on Invoke-Blocks, so the only work item left here would be if we wanted to update PR text.

Closing this since there's no reply. @natemcmaster if you had further comments feel free to re-open.