TypeError: async_update_entity() got an unexpected keyword argument 'device_id'

I'm getting following errors on HA startup for all of the sensors based on entities (lights, media_player with fixed mode). A sensor based on daily_fixed_energy isn't throwing it. It's happening for sensors I'm grouping and not.
HA version: 2021.12.0
power calculation version: 0.18.3
sensor:
  - platform: powercalc
    manufacturer: ikea
    model: LED1537R6
    entities:
      - entity_id: light.l10
      ...
  - platform: powercalc
    entity_id: media_player.tv
    standby_power: 18.6
    fixed:
      states_power:
        playing: 169
  - platform: powercalc
    name: fridge_energy
    daily_fixed_energy:
      value: 0.73

2022-02-22 22:26:55 DEBUG (MainThread) [custom_components.powercalc.sensor] Binding sensor.l10_power to device ebexxxxxxxxxxxxxxxxxxxxxxxx0
2022-02-22 22:26:55 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback create_individual_sensors.<locals>.<lambda>(<Event homeas...nt_started[L]>) at /config/custom_components/powercalc/sensor.py:438
Traceback (most recent call last):
File "/usr/local/lib/python3.9/asyncio/events.py", line 80, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/core.py", line 835, in _onetime_listener
self._hass.async_run_job(listener, event)
File "/usr/src/homeassistant/homeassistant/core.py", line 452, in async_run_job
return self.async_run_hass_job(HassJob(target), *args)
File "/usr/src/homeassistant/homeassistant/core.py", line 433, in async_run_hass_job
hassjob.target(*args)
File "/config/custom_components/powercalc/sensor.py", line 438, in <lambda>
lambda _: bind_entities_to_devices(
File "/config/custom_components/powercalc/sensor.py", line 525, in bind_entities_to_devices
ent_reg.async_update_entity(entity.entity_id, device_id=device_id)
TypeError: async_update_entity() got an unexpected keyword argument 'device_id'

This issue confuses me a lot, because it complains about async_update_entity method not have a device_id argument.
I had another look into the HA core code, where this function is defined, and I see in the history this argument was always there. At least the last 11 months. So I don't understand why you get this error.
Are you able to check this file on your HA installation:
homeassistant/helpers/entity_registry.py
I am interested in line 504 https://github.com/home-assistant/core/blob/dev/homeassistant/helpers/entity_registry.py#L504.
You could also sent me the whole file as you want.

I'm using a supervised HA installation, not sure how to get to this file yet. I'm not certain when this error start showing up though.

Good question ;-). I have asked on HA discord dev channel if someone has an idea what can cause this error for you.

I have asked to dev channel btw 12 days ago, but never got an answer. I really have no clue what causes this issue and how to debug it.
Do you still experience this issue?

Hi @bramstroker, I'm having the same issue.
Home Assistant 2021.12.7
power calculation version: 0.18.4
The content of the file you asked for in my installation:
Fetch entities which are not already disabled
    entities = async_entries_for_device(self, event.data["device_id"])
    for entity in entities:
        self.async_update_entity(
            entity.entity_id, disabled_by=RegistryEntryDisabler.DEVICE
        )

@nikadaika The line number I referred to is not correct anymore. There has been added some code since I commented so the code has been shifted a few lines.
I need the signature of async_update_entity method:
 def async_update_entity(
        self,
        entity_id: str,
        *,
        area_id: str | None | UndefinedType = UNDEFINED,
        capabilities: Mapping[str, Any] | None | UndefinedType = UNDEFINED,
        config_entry_id: str | None | UndefinedType = UNDEFINED,
        device_class: str | None | UndefinedType = UNDEFINED,
        device_id: str | None | UndefinedType = UNDEFINED,
        disabled_by: RegistryEntryDisabler | None | UndefinedType = UNDEFINED,
        # Type str (ENTITY_CATEG*) is deprecated as of 2021.12, use EntityCategory
        entity_category: EntityCategory | str | None | UndefinedType = UNDEFINED,
        hidden_by: RegistryEntryHider | None | UndefinedType = UNDEFINED,
        icon: str | None | UndefinedType = UNDEFINED,
        name: str | None | UndefinedType = UNDEFINED,
        new_entity_id: str | UndefinedType = UNDEFINED,
        new_unique_id: str | UndefinedType = UNDEFINED,
        original_device_class: str | None | UndefinedType = UNDEFINED,
        original_icon: str | None | UndefinedType = UNDEFINED,
        original_name: str | None | UndefinedType = UNDEFINED,
        supported_features: int | UndefinedType = UNDEFINED,
        unit_of_measurement: str | None | UndefinedType = UNDEFINED,
    ) -> RegistryEntry:

There you go:
def _async_update_entity(
       self,
       entity_id: str,
       *,
       area_id: str | None | UndefinedType = UNDEFINED,
       capabilities: Mapping[str, Any] | None | UndefinedType = UNDEFINED,
       config_entry_id: str | None | UndefinedType = UNDEFINED,
       device_class: str | None | UndefinedType = UNDEFINED,
       device_id: str | None | UndefinedType = UNDEFINED,
       disabled_by: RegistryEntryDisabler | None | UndefinedType = UNDEFINED,
       entity_category: str | None | UndefinedType = UNDEFINED,
       icon: str | None | UndefinedType = UNDEFINED,
       name: str | None | UndefinedType = UNDEFINED,
       new_entity_id: str | UndefinedType = UNDEFINED,
       new_unique_id: str | UndefinedType = UNDEFINED,
       original_device_class: str | None | UndefinedType = UNDEFINED,
       original_icon: str | None | UndefinedType = UNDEFINED,
       original_name: str | None | UndefinedType = UNDEFINED,
       supported_features: int | UndefinedType = UNDEFINED,
       unit_of_measurement: str | None | UndefinedType = UNDEFINED,
   ) -> RegistryEntry:

Looks like something is missing here:
entity_category: str | None | UndefinedType = UNDEFINED,

It's very strange because there is en underscore in your function definition. Mind def _async_update_entity vs def async_update_entity. Are you able to sent me the full file? You could at a gist at github, or email me bgerritsen_at_gmail_dot_com. Or discord bramski#3414

@nikadaika @bbiegun I think I have found the issue. This seems to be a problem with HA versions lower than 2022.2
I have added an extra check, when the HA version is lower than 2022.2 than the powercalc entities will not be bound to a device.
Has been resolved in v0.19.0-beta.6.
However you are recommended to update HA to a more recent version.

Thanks, @bramstroker. I decided to update HA to the most recent version and deal with the breaking changes. It fixed the problem like you predicted.

@nikadaika that's great. Just released v0.19.0 which also contains this fix.


Controllers

Hello Reviewer!!!
I have completed the task assigned to me for today and below is a summary of my work:

Correct use of git-flow
No linter errors
Creation of controllers
Creation of create, update, index, and show methods in controllers
Task completion

If you have any suggestions for me, please let me know via the comment section of this PR.

Hello Desmond, in you review you asked that I shouldn't use rails generate
scaffold. But how were you able to conclude that I used the command because
I didn't even know about it until now???
On Tue, Jun 20, 2023, 1:22 AM Desmond Owusu Ansah @.***>
wrote:

@.**** requested changes on this pull request.
Hi @David-Lanzz https://github.com/David-Lanzz ,
Good job so far!
There are some issues that you still need to work on to go to the next
project but you are almost there!
https://camo.githubusercontent.com/3a1773e67b59be57886dfad87493afeb1a30964d11e0a9ec62f4e712796decf1/68747470733a2f2f6d65646961312e67697068792e636f6d2f6d656469612f5959687432555456343175317678485473732f67697068792d646f776e73697a65642d6d656469756d2e676966
Highlights
📌 Your linters are passing ✅
📌 Descriptive pull request✅
📌 Good commit messages ✅
📌 Your README file is okay✅
Required Changes ♻
Check the comments under the review.
Optional suggestions
Every comment with the [OPTIONAL] prefix is not crucial enough to stop
the approval of this PR. However, I strongly recommend you to take them
into account as they can make your code better.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something
is not 100% clear.
Please, remember to tag me in your question so I can receive the
notification.
Please, do not open a new Pull Request for re-reviews. You should use the
same Pull Request submitted for the first review, either valid or invalid
unless it is requested otherwise.
As described in the Code reviews limits policy
https://microverse.zendesk.com/hc/en-us/articles/1500004088561 you have a
limited number of reviews per project (check the exact number in your
Dashboard). If you think that the code review was not fair, you can request
a second opinion using this form https://airtable.com/shrQAqnBwek5a0O0s.
In app/controllers/posts_controller.rb
https://github.com/David-Lanzz/lanzz-blog/pull/4#discussion_r1234566256:

+class PostsController < ApplicationController

def index
@post = Post.all
end

def show
@post = Post.find(params[:id])
end

def new
@post = Post.new
end

def create
@post = Post.new(posts_params)

if @post.save

 redirect_to @post

else

 render 'new'

end
end

def update
@post = Post.find(params[:id])

if @post.update(posts_params)

 redirect_to @post

else

Please from the project requirement, you should NOT use the rails
generate scaffold command to generate your controllers and your views.
Remember that this project is to show you how to set up controllers by
yourselves so make sure that you set up everything by yourself 😄

In app/controllers/likes_controller.rb
https://github.com/David-Lanzz/lanzz-blog/pull/4#discussion_r1234566433:

def index

@like = Like.all
end

def new
@like = Like.new
end

def show
@like = Like.find(params[:id])
end

def create
@like = Like.find(params[:id])
if @like.save

 redirect_to @like

else

 render 'new'

end
end

def update
@like = Like.find(params[:id])
if @like.update(likes_params)

 redirect_to @like

else

 render 'new'

end

Please from the project requirement, you should NOT use the rails
generate scaffold command to generate your controllers and your views.
Remember that this project is to show you how to set up controllers by
yourselves so make sure that you set up everything by yourself 😄

In app/controllers/users_controller.rb
https://github.com/David-Lanzz/lanzz-blog/pull/4#discussion_r1234566552:

def index

@users = User.all

end

def show

@users = User.find(params[:id])

end

def new

@users = User.new

end

def create

@users = User.new(user_params)

if @users.save

 redirect_to @users

else

 render 'new'

end

end

def update

@user = User.find(params[:id])

if @user.update(user_params)

 redirect_to @user

else

 render 'edit'

end

end

Please from the project requirement, you should NOT use the rails
generate scaffold command to generate your controllers and your views.
Remember that this project is to show you how to set up controllers by
yourselves so make sure that you set up everything by yourself 😄

In config/routes.rb
https://github.com/David-Lanzz/lanzz-blog/pull/4#discussion_r1234568317:

@@ -3,4 +3,5 @@

Defines the root path route ("/")
root "articles#index"

resources :users,:posts,:likes,:comments

I suggest that you should make sure that your application handles
only the 4 required URLs. 👇 as requested in the project requirement.

Make sure that when you run the rails routes command in your console, you
can see the following output
[image: image]
https://user-images.githubusercontent.com/92303891/246955805-5b47a454-ee8b-4a2b-a6dc-f3ff356ca5ee.png

In app/controllers/comments_controller.rb
https://github.com/David-Lanzz/lanzz-blog/pull/4#discussion_r1234568436:

def index

@comment = Comment.all

end

def show

@comment = Comment.find(params[:id])

end

def new

@comment = Comment.new

end

def create

@comment = Comment.new(comments_params)

if @comment.save

 redirect_to @comment

else

 render 'new'

end

end

def update

@comment = Comment.find(params[:id])

if @comment.update(comments_params)

 redirect_to @comment

else

 render 'new'

end

end

Please from the project requirement, you should NOT use the rails
generate scaffold command to generate your controllers and your views.
Remember that this project is to show you how to set up controllers by
yourselves so make sure that you set up everything by yourself 😄

—
Reply to this email directly, view it on GitHub
https://github.com/David-Lanzz/lanzz-blog/pull/4#pullrequestreview-1487056105,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2REL2XS37CGTOD4JTJVWC3XMDUMRANCNFSM6AAAAAAZMQOLEU
.
You are receiving this because you were mentioned.Message ID:
@.***>


ReferenceMany: insert an empty array

Q
A

Type
improvement

BC Break
yes

Fixed issues
#1195

Summary
See #1195

#1624

Glad you decided to be "someone to pick that PR up"! 🎉
Unfortunately we still need to consider https://github.com/doctrine/mongodb-odm/pull/1624#issuecomment-319175763, even more than before, after 6 more years of previous behaviour and no 3.0 on horizon.

@malarzm Added optional parameter insertEmptyArray

@malarzm ping :)

Thanks for the patience while I've been on vacations :) This is a good start, however there are few things I need you to do.. First things first, please rebase your work atop current 2.6.x branch, some of the errors will go away. Other things (in random order)

Same feature should be made available for EmbedMany association
XML mapping support is missing, you can take a look here https://github.com/doctrine/mongodb-odm/blob/2.6.x/lib/Doctrine/ODM/MongoDB/Mapping/Driver/XmlDriver.php#L454 how bool-ish attributes should be handled. XSD (https://github.com/doctrine/mongodb-odm/blob/2.6.x/doctrine-mongo-mapping.xsd) file shall be updated accordingly
New option should be added to https://github.com/doctrine/mongodb-odm/blob/2.6.x/lib/Doctrine/ODM/MongoDB/Mapping/ClassMetadata.php#L155. Combined with 1 this should effectively make ?? false construct not needed in your code
How about naming the feature storeEmptyArray? Right now we're strictly talking about inserting document, but there's more to consider like clearing a persistent collection, which right now issues a $unset query here https://github.com/doctrine/mongodb-odm/blob/2.6.x/lib/Doctrine/ODM/MongoDB/Persisters/CollectionPersister.php#L82

Thanks for your detailed answer. I'll get to it soon.
P.S. I hope you had a good rest :)

@malarzm ping :)

Done
Done

Thank you very much for the code review!

One last thing I've caught, sorry it's that late in the process. Also if you'd been fixing that, mind squashing commits so there's just 1?

Done

Awesome! Thank you @khaperets very much for sticking with us (me) and seeing this to an end 🍻

@malarzm Many thanks for your help!


packageDocumentation (and all valid TSDoc summaries) not being displayed as descriptions in the API Reference

Expected Behavior

Packages with TSDoc comments tagged @packageDocumentation elements should be showing their descriptions (summaries) properly in the API Reference. Also, any summaries in the beginning of a valid TSDoc comment should be shown as descriptions for their related reference in the generated output.
Current Behavior

The properly tagged @packageDocumentation elements in the API Reference aren't being included in the output. Neither are any valid summaries from TSDoc comments for any other related element, even though the output does indicate when it's missing.
Related to https://github.com/backstage/backstage/issues/7162 but thought it should be discussed separately.
Possible Solution

Steps to Reproduce

See the API Reference: https://backstage.io/docs/reference/
Context

Tried to take a stab at helping out #7162 today and focusing on why the package descriptions (and in fact, ALL descriptions on all pages!) are blank.

My current findings:

TSDoc requires that the @packageDocumentation element and it's summary be the first TSDoc comment in the resulting index.d.ts file. You can test this with the TSDoc Playground: https://tsdoc.org/play
All of our .ts files have Copyright headers.
However, the generated .d.ts files strip this properly. It's the .d.ts used for creating a resulting .api.json map, which is then read in and used to generate the Markdown.
I've tried various permutations of stripping copyright (just in case), playing with whitespace for @packageDocumentation, but not able to get it to generate.
Interestingly, on packages that LACK the @packageDocumentation, it's PROPERLY indicating as such in the output. (via a hidden warning)

So this tells me that it can interpret whether or not there is a summary for the @packageDocumentation.
My guess is since we're not using the raw api-extractor nor the api-documenter commands, something about the script/api-extractor.js we wrote is somehow skipping this.
I tried playing around with it, including digging into the elements with this._createDescriptionCell without much luck.
https://github.com/backstage/backstage/blob/68eddf88a02a2244cf10e64a7dd969133ddd64a1/scripts/api-extractor.ts#L605-L609

Providing this background here as the folks who may have created this original script MIGHT have a guess maybe based on this info here in, but after playing around I just couldn't come to a solution. Also the community might have some ideas or some cycles to dig into this, specifically.
Bottom line in my mind is fixing this would immediately provide a ton of value as all of the existing info would be elevated, and you can even see the summaries (the descriptions) that exist on many many other functions, objects, classes, etc, are ALSO not being elevated, which tells me the core issue here is not whether or not the @packageDocumentation works but much more specifically that our output generation does NOT display the element summaries as descriptions at all.
I can find no issues in the TSDoc project nor Stack Overflow or Google where anyone's had ANY such issues in their generation, again why I'm speculating it's something to do with how we hacked the API to self-generate it.
Your Environment

OS:   Darwin 21.1.0 - darwin/x64
node: v14.18.1
yarn: 1.22.1
cli:  0.9.0 (local)

Dependencies:
  @backstage/catalog-client       0.3.19
  @backstage/core-components      0.3.3, 0.4.2, 0.5.0, 0.6.1
  @backstage/core-plugin-api      0.1.13
  @backstage/plugin-catalog-react 0.4.6, 0.5.2

Thank you for reporting! Can add that the current package index page format along with all the package documentation was added in #7181. That change was at the very least working locally, some something changed between then and now :grin:

Ah, most likely gonna be the bump in #8023 that changed something, will have a look at what might've changed


Adding test cases for create edit

Please set the title of your pull request in the following format: [Project id/Independent study/Issue fix/...]. project name, eg., E904. Integrating courses and assignments on Expertiza with Moodle
We suggest you including the below information in your pull request:

A description of the changes proposed in the pull request.
@mentions of the person or team responsible for reviewing proposed changes.

About Expertiza Bot

If you have any questions about comments given by the expertiza-bot (example), you could create a comment in your pull request with the format /dispute [UUID1] [UUID2] (example) then the professor and TAs will be notified.
Here is a video about how to communicate to expertiza-bot.

@akk5597 all the suggestions are committed.Please approve


Interface Overview on wrong side when workbench.sideBar.location = "right"

VS Code Version: Version: 1.55.0-insider (Universal)
OS Version: Darwin arm64 20.1.0

Version: 1.55.0-insider (Universal)
Commit: 5d80c30e5b6ce8b2f5336ed55ad043490b0b818f
Date: 2021-03-08T05:24:34.127Z (15 hrs ago)
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 20.1.0

Hi there VSCode team, thank you for all your work! I have a small visual bug report. The "Help: User Interface Overview" does not point to the right side when "workbenchh.sideBar.location": "right" is in your settings.json.
Steps to Reproduce:

Set "workbench.sideBar.location": "right" in your settings.json or in the settings GUI
Open command palette (cmd+shift+p on mac os) and run "Help: User Interface Overview"
See the interface overview point to the left still

You can see the interface overview still points to the left side:

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

Duplicate of #100407 (which is also marked as a duplicate of #92312)


updated phylogeny loading to also handle taxa linked by glottocode

Codecov Report

Merging #457 into master will decrease coverage by 0.1%.
The diff coverage is 93.75%.

@@            Coverage Diff             @@
##           master     #457      +/-   ##
==========================================
- Coverage   94.27%   94.16%   -0.11%
==========================================
  Files          24       24
  Lines        1536     1542       +6
==========================================
+ Hits         1448     1452       +4
- Misses         88       90       +2

Impacted Files
Coverage Δ

dplace_app/loader/tree.py
94.52% <93.75%> (-2.5%)
:x:

Continue to review full report at Codecov.

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


controller - write callback functions in callback.py

please implement the call-back functions used in the application in this file.

see pull request #30


@jonallured: fix elasticsearch environments

As discussed in https://github.com/artsy/bearden/issues/300, I use a new ENV var called ELASTICSEARCH_ENV to deduce the index name for Organizations.
Thanks for catching that issue - it recently caught me out in Diffusion too, so I really should have foreseen it.
I've updated the config vars in Heroku staging/production.
Migration
We need to re-migrate now I guess, since all our staging data incorrectly went into a production index. So on staging first, and then production, we should do this:
# this recreates the index and all its settings/mappings without reindexing the data.
Organization.reload_index!
# exit the rails console...
bundle exec rake elasticsearch:reindex

I'm happy to do that myself once this is merged, but let me know if you'd rather do it.
Fixes https://github.com/artsy/bearden/issues/300

Nice one - I'll babysit this one out to staging and production. 💯

Ok, this is merged, deployed and migrated on both staging and production - thanks so much for your help @cavvia!! ❤


Need to be more precise about version of TensorFlow IO

The API has changed so need to use the matching version of TensorFlow IO, not the latest.

As always, the pylint and 'Code Check' failures are because of a pre-existing line being too long which cannot easily be fixed.


failed to reproduce the result using the training code

When I used the training code directly on MSCOCO and Painter By Numbers datasets by:
th train-vgg-decoder.lua --contentDir /path/to/dir --styleDir /path/to/dir

I couldn't reproduce the results as is listed on the paper and github.
For example, when using bike and starry night, I got:

when using brad_pitt and la_muse, I got:

These are results with decoder and without optimization, and the training process uses all the default parameters as in the code. Are there any suggestions or ideas why the it comes out like this?
Sincerely thanks!

Actually, I believe my samples came from a decoder that used instance norm. I don't quite remember the specifics but instance norm should give a decent boost in quality. (Sorry about the misleading defaults.) If you want to play around with my trained decoder, just email me.

Thanks for your previous response and I already received your trained decoder, which has an amazingly good performance. However, I need to train the model for my own research task, but I still cannot reproduce the training result. Actually I found the decoder network architecture is different from what is designed in train-vgg-decoder.lua, which is like this:
nn.Sequential {
  [input -> (1) -> (2) -> (3) -> (4) -> (5) -> (6) -> (7) -> (8) -> (9) -> (10) -> (11) -> (12) -> (13) -> (14) -> (15) -> (16) -> (17) -> (18) -> (19) -> (20) -> (21) -> (22) -> (23) -> (24) -> (25) -> (26) -> (27) -> (28) -> (29) -> (30) -> (31) -> (32) -> (33) -> (34) -> (35) -> (36) -> (37) -> output]
  (1): nn.SpatialFullConvolution(256 -> 128, 3x3)
  (2): nn.SpatialZeroPadding(l=-1, r=-1, t=-1, b=-1)
  (3): nn.InstanceNormalization
  (4): nn.ReLU
  (5): nn.SpatialFullConvolution(128 -> 128, 3x3)
  (6): nn.SpatialZeroPadding(l=-1, r=-1, t=-1, b=-1)
  (7): nn.InstanceNormalization
  (8): nn.ReLU
  (9): nn.SpatialUpSamplingNearest
  (10): nn.SpatialFullConvolution(128 -> 128, 3x3)
  (11): nn.SpatialZeroPadding(l=-1, r=-1, t=-1, b=-1)
  (12): nn.InstanceNormalization
  (13): nn.ReLU
  (14): nn.SpatialFullConvolution(128 -> 128, 3x3)
  (15): nn.SpatialZeroPadding(l=-1, r=-1, t=-1, b=-1)
  (16): nn.InstanceNormalization
  (17): nn.ReLU
  (18): nn.SpatialFullConvolution(128 -> 64, 3x3)
  (19): nn.SpatialZeroPadding(l=-1, r=-1, t=-1, b=-1)
  (20): nn.InstanceNormalization
  (21): nn.ReLU
  (22): nn.SpatialFullConvolution(64 -> 64, 3x3)
  (23): nn.SpatialZeroPadding(l=-1, r=-1, t=-1, b=-1)
  (24): nn.InstanceNormalization
  (25): nn.ReLU
  (26): nn.SpatialUpSamplingNearest
  (27): nn.SpatialFullConvolution(64 -> 64, 3x3)
  (28): nn.SpatialZeroPadding(l=-1, r=-1, t=-1, b=-1)
  (29): nn.InstanceNormalization
  (30): nn.ReLU
  (31): nn.SpatialFullConvolution(64 -> 64, 3x3)
  (32): nn.SpatialZeroPadding(l=-1, r=-1, t=-1, b=-1)
  (33): nn.InstanceNormalization
  (34): nn.ReLU
  (35): nn.SpatialFullConvolution(64 -> 3, 3x3)
  (36): nn.SpatialZeroPadding(l=-1, r=-1, t=-1, b=-1)
  (37): nn.Sigmoid
}

But when I used this structure to train the decoder again, I still got a similar result like before:

The color of the trained decoder is quite strange and seems not to be improving during the training process. I already used the instance normalization and deconvolution layer like the architecture above.  Could you give some more hints about what parameters or options do I need to tune, such as learning rate, tvloss, pixelloss, or other parameters?
Sincerely thanks!


analytical placement flow

One can now run vpr with constraint file that records all fixed io.

So far this looks really good. I suspect run_ap_with_constraint.py will become very useful later. Right now, since the flow is so young this is fine, but eventually we may want to support running circuits in parallel and collecting information about each run. But its probably best to wait until the pipeline is more mature.
For now, my expected use-case for these scripts is to run a single circuit on a single architecture. But it is 100% a good idea to ensure that multiple circuits are supported.

Also, could you please rebase this branch onto master?


Error 101 when running make test-chunk-prove

make test-chunk-prove runs for 10-20 minutes before it terminates, complaining that process didn't exit successfully: "/data/scroll-prover/target/release/deps/chunk_tests-2cc1811299f948cd test_chunk_prove_verify" (signal: 9, SIGKILL: kill)
In case it helps, the message prior to the error message is printed out a few minutes before, and it hadn't printed anything out for a while.
Here are more details of the trace:
...
2023-10-05T00:15:36.290214221+00:00 INFO halo2_proofs::circuit::floor_planner::single_pass - region state circuit (synthesize_sub) part2_16 2nd pass synthesis took 57.795971ms
2023-10-05T00:15:36.290310397+00:00 INFO halo2_proofs::circuit::floor_planner::single_pass - region state circuit (synthesize_sub) part2_24 2nd pass synthesis took 57.877096ms
2023-10-05T00:15:36.291487719+00:00 INFO halo2_proofs::circuit::floor_planner::single_pass - region state circuit (synthesize_sub) part2_0 2nd pass synthesis took 60.293544ms
2023-10-05T00:15:36.292047993+00:00 INFO halo2_proofs::circuit::floor_planner::single_pass - Merge 32 subCS back took 13.82µs
2023-10-05T00:15:36.292106747+00:00 INFO halo2_proofs::circuit::floor_planner::single_pass - 32 sub_regions of state circuit (synthesize_sub) part2 2nd pass synthesis took 60.996997ms
error: test failed, to rerun pass `-p integration --test chunk_tests`

Caused by:
  process didn't exit successfully: `/data/scroll-prover/target/release/deps/chunk_tests-2cc1811299f948cd test_chunk_prove_verify` (signal: 9, SIGKILL: kill)
make: *** [Makefile:42: test-chunk-prove] Error 101

Seems out-of-memory. Need to check CPU and MEM usage.

yes, you're correct, i can see memory climbing and then drops to 0 right when the command crashes.
what is the required memory? i am running with 64GB on a CPU instance (no GPUs).
I can also run with GPUs, if you can provide specs for that. ideally for both cpu and gpu so i can compare.

Could try to run on a server with 500G memory.
I think we haven't prepare enough to open-source for GPU. May need to wait for a while, thanks.

That did it, thanks!


Provide artifacts on Maven central

Some people still use Maven ;)

No need to push to Maven Central. Simply configure a repositories block in the POM file
<repositories>
    <repository>
        <id>jcenter</id>
        <url>http://jcenter.bintray.com/</url>
    </repository>
</repositories>

Version 1.9.0 can now be found in Maven central


[SparkR][Minor] Remove reference link for common Windows environment variables

What changes were proposed in this pull request?
The PR removes reference link in the doc for environment variables for common Windows folders. The cran check gave code 503: service unavailable on the original link.
How was this patch tested?
Manual check.

Test build #64267 has started for PR 14767 at commit 2bf9be0.

Test build #64267 has finished for PR 14767 at commit 2bf9be0.

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

Merged build finished. Test PASSed.

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

LGTM. This addresses one of the (non-warning, non-NOTE) message from CRAN check too.

merged to master and branch-2.0


Working in Zend framework

I have this in gruntfile:
uncss: {
    dist: {
        files: [{
            src: 'public/styles/cleancss/tidy.css',
            dest: 'application/views/layouts/default.phtml'
        }]
    }
}

Paths are relative to root, but when I type grunt to cli, it finish with fatal error:
Running "unst:dist" (uncss) task
Fatal error: PhantomJS: Cannot open about:blank

What is that mean? Src is access from http, but dest does not. It is routed by ZF. Is that problem?

Does this still happen with 0.5.2+?

Closing due to lack of reply and a repo to reproduce the issue.


The system cannot find the path specified:

So, I kind of know the problem, the thing is I don't know how to solve it.
Some time ago I changed my Windows name to something else ("Purple" [no, seriously]), so the program is trying to find a file/folder called "WiiMusicEditorPlus" located in "C:/Users/[user]/AppData/Local/WiiMusicEditorPlus". But, since my old Windows name was linked to my Microsoft account and when I changed it I unlinked it, it's trying to find the file located in "C:/Users/Purple/[...]", even though my user folder itself is still called "thego".
I'm pretty sure there's probably almost no fix for this problem that could work for everyone in every situation, so is there a way to change the directory it's looking for when starting up the exe?

Ok I will see if I can a fix for that.

If you have python installed on your computer can you try running:
import os
print(os.path.expanduser('~'))

Tell me if that gives the correct name/path of your user folder.

Try also using this version

@TheGoldenPotion Any update on this?


Grobid displaying information which is not mentioned in PDF file

Hi,
When I am parsing a pdf, I am getting the doi, volume, and issue in the TEI when consolidate header option is used. I wanted to know how is it getting it since none of this is mentioned in the PDF file itself.
Also, are there any other fields that are extracted in this manner.
Thanks in advance :)

Dear @rohittilwani, this additional data, by default, is taken from CrossRef. See the documentation here.

Thanks @lfoppiano .
Also, is this information (DOI, volume, etc.) extracted from CrossRef even if it is available in the article.

The final data is the result of the merge between what is extracted from the PDF document and what is returned from Crossref. Sometimes, for example in the case of preprints, the bibliographic data is overridden with the peer-reviewed version of the article.


Add droctothorpe as member

Closed this issue in favor of this PR. There are some conflicting instructions on the website vs the readme here / community repo.
Please provide links to PRs or other contributions (2-3):

https://github.com/kubeflow/pipelines/pull/10471
https://github.com/kubeflow/katib/pull/2183
https://github.com/kubeflow/pipelines/pull/8517

** Please list 2 existing members who are sponsoring your membership:**
@connor-mccarthy
@andreyvelich
** Please test your PR **
Run
cd github_orgs
pytest test_org_yaml.py

Include the output in the PR
===================================================================================== test session starts =====================================================================================
platform darwin -- Python 3.11.4, pytest-7.4.3, pluggy-1.0.0
rootdir: /Users/inn487/code/kubeflow/internal-acls/github-orgs
plugins: anyio-4.0.0, cov-4.1.0
collected 1 item

test_org_yaml.py .                                                                                [100%]

====================================================================================== 1 passed in 0.11s ======================================================================================

/lgtm
/approve

@droctothorpe Please sign your commit for DCO.

Thanks, @andreyvelich. Fixed! 👍

Great, thanks @droctothorpe!
/lgtm
/approve


newly created documents not showing until refresh of page

when a user creates new a document on the homepage it doesn't  show up on the list of available docs until refresh .

i got this fixed


merge from arlac77/npm-package-template

package.json

chore(package): remove ^4.3.1 (devDependencies.rollup-plugin-babel)

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


DBZ-701 Support for arrays with large OID

https://issues.jboss.org/browse/DBZ-701

Applied. Thx!


Skip dss with empty fields

Fixes issue we're running into with https://github.com/CliMA/ClimaCore.jl/issues/1265

I think its best to have the exception handling code higher up rather at the location of the weighted_dss call.
As discussed in https://github.com/CliMA/ClimaCore.jl/issues/1265 , there is no reason to call tracer_hyperdiffusion_tendency! when there are no tracers!

@dennisYatunin, any idea why this is resulting in behavioral changes for some jobs? cc @szy21, @simonbyrne

Hmm, the results actually look very strange.

Ah, I think I might know. For some quantities like ᶜ∇²specific_tracers (which is a NamedTuple), it should be isempty(propertynames(x)), but for some other quantities like ᶜ∇²uₕ, it should be just isempty(x)?

Ah, I think I might know. For some quantities like ᶜ∇²specific_tracers (which is a NamedTuple), it should be isempty(propertynames(x)), but for some other quantities like ᶜ∇²uₕ, it should be just isempty(x)?

Ok, that makes sense.
I've been thinking about this a bit more, and I'm also wondering what broadcast expressions are doing with empty fields-- I think this is exercising an untested edge case in ClimaCore fields, cc @simonbyrne. Should we add some unit tests to ClimaCore so that we're sure this short circuits to no-ops?

This is fixing an issue that was fixed in the latest ClimaCore update.


QRS detection still detects on noise.

QRS detection algorithm marks noise as a heart beat.  Also marking is off by a few samples.

QRS threshold is not set yet.
The QRS detection is off due to the phase shift cause by filtering.
Will fix.

fixed in latest push


Delete edit concert events

How does this look?

This review is incomplete - just addressing a few things regarding the EventController


Deploy web application to DigitalOcean

Steps:

[x] Create a VM on DigitalOcean with Ubuntu-server 20.04.2 LTS 64-bit
[x] Login to the VM via SSH
[x] Install Docker and docker-compose
[x] Clone blobfishes sources from GitHub
[x] Create a MongoDB cluster on DigitalOcean (#42)
[x] Create file .env and fill-in credentials for MongoDB instance
[x] Run docker-compose up -d
[x] Test webapp locally: curl -v http://localhost:3000/
[x] Open incoming ports on the VM
[x] Test webapp remotely using a browser http://vm_ip_address:3000

Document all the steps in a document under docs/

All the steps have been performed according to this document:
https://github.com/aquariophilie/blobfishes/blob/main/docs/deploy-blobfishes-to-digitalocean.md


fix(button.tsx): Relative Spinner size

[X] I have followed the Your First Code Contribution section of the Contributing guide

Summarize the changes made and the motivation behind them.
This PR makes the  component inside the  component to be relative to the Button size when isProcessing=true. It also adds an width animation when the flag is toggled.

Reference related issues using # followed by the issue number.
Fix #850
If there are breaking API changes - like adding or removing props, or changing the structure of the theme - describe them, and provide steps to update existing code.

@rluders weird, the test in the CI / build workflow does not fail locally for me.

https://github.com/themesberg/flowbite-react/actions/runs/5605163775/jobs/10253955428#step:8:342 I'm also not sure why exactly this is happening

I notice that some tests are failing, not 'cause the test subject is failing but because the test itself has some implementation issue... maybe some rendering, or delay process that is causing the issue. Probable we should create an issue to fix it, I'm sure that the problem isn't related to this PR specifically.


Web Performance Decrease When Using Low Power Mode on iOS

There is a noticeable performance decrease when viewing a Flutter website on iOS while in low power mode. I’m running iOS 14.7.1 and using Safari as my browser.
This is the website I was viewing when I noticed the performance issue: https://davidcobbina.com/#/home

@rbebb
There is a noticeable performance decrease. Can you provide what are the exact difference you noticed ?
If you make a simple app and run it on iOS device in low power mode, does it show a noticeable performance difference ?
We would need an actionable data such as code sample and flutter doctor -v to properly address this issue.
Thanks.

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


update: use lock

How about using File.flock to get a true lock on the lockfiles? Might even simplify the code; then you'd only need to read the lock file if you needed the PID of the other process (e.g. for the error message). And we could use it to do multi-reader/one-writer locking if that becomes relevant.

@apjanke unfortunately we need a lock implementation in Bash not Ruby.

Oh darn. Sorry about that. I just woke up and apparently my brain is only half functioning.
Okay, I get it now – it's using mkdir for atomicity doable portably from bash. I think it'll work as is. Let me mull it over a bit.
It's possible we'll need distinct locks for different operations in the future, if we're ambitions. How about making $HOMEBREW_LIBRARY/lock.d a permanent directory, and making $HOMEBREW_LOCK_DIR be $HOMEBREW_LIBRARY/lock.d/formulae, so we could add other lock dirs in the future without cluttering Library? Just in case.

Yes, this is mainly to use mkdir as an atomic operation to create lock. However, it does have a possible race situation when handling stale lock directory as described in comment section of http://wiki.bash-hackers.org/howto/mutex
I'm open to a better lock bash implementation. But I couldn't find one myself.
As for supporting name lock, I'm thinking leave it as is for now because we probably should avoid to use bash lock if possible due to its imperfections.

Re: ps: fuser or lsof are other options with less failure. I'd really rather we tried to lean into a simple Unix command unless we can demonstrate failure cases, particularly given this implementation is racy. If we're going to write a lot of code for this: I'd rather it worked.
Another option is:
$ /usr/bin/time ruby -e 'File.new("/Users/mike/fish").flock(File::LOCK_EX)'
        0.06 real         0.04 user         0.02 sys

Sorry for being muddle-headed earlier and not realizing this was bash.
I agree with xu-cheng now that this is a good way to go and will work as is, with mkdir providing the atomicity. The race condition that's left in the directory cleanup seems like the only issue would be getting a false positive (thinking the other process still held the lock when in fact it doesn't), but the failure mode for that is nondestructive, just displaying the error message, and re-running brew update will work and clean up the lock. That's not a big deal.
I can't think of a better native bash implementation, and think this one is sufficient, unless there's a different problem I'm overlooking. And just using ps or lsof or anything else that just queries who's using what is going to be racy.
The problem with shelling out to Ruby is that you'd need to keep that flocking ruby process alive for the duration of the update, which would be more complicated than what we have now.

If this has a known race-condition I'm a pretty hard 👎 on using it instead of a far more simple implementation using something like ps, fuser or lsof.

fuser -uf /usr/local/bin/brew in /usr/local/Library/Homebrew/cmd/update.sh seems pretty consistently reliable to me?

It's only technically a "race": all outcomes still serialize the operations in a correct, safe order. It's just a minor loss of efficiency. Would matter in something like a high volume web server, but not for brew's purposes.
I don't think we really know if those other implementations are reliable. If they aren't, they'd just cause rare, intermittent, hard-to-reproduce problems for users in the wild, maybe hat just looked like repo's in a weird state. They wouldn't know what to report and we'd have no way of diagnosing. I know you like to actually see a bug happen before fixing it, but this may be a case where we just can't really know. Maybe some of those weird user config issues that Martin likes to tackle are due to this. Maybe (probly) they aren't.
ps, fuser, and lsof all have the same problem: they're point-in-time observations. If we stick with one of those, doesn't really matter which we use. But if we use mkdir, we can be more confident that there aren't unknown weird failures happening for users out there. And we'd be setting a good example for other coders. :)

Maybe some of those weird user config issues that Martin likes to tackle are due to this.

Not sure what this is referring to, to be honest. 😀

ps, fuser, and lsof all have the same problem: they're point-in-time observations. If we stick with one of those, doesn't really matter which we use.

Exactly. Using one of these is as good as not locking at all. (Which worked fairly well so far.)

But if we use mkdir, we can be more confident that there aren't unknown weird failures happening for users out there. And we'd be setting a good example for other coders. :)

:+1: I'm in favor of the current implementation. Using an atomic mkdir as a mutex is a pretty standard technique in shell scripting as far as I know. I've used it successfully in a serializing logger invoked from something like make -j4 and it works well in practice.

Exactly. Using one of these is as good as not locking at all. (Which worked fairly well so far.)

Can you care to explain what the failure case is on them, please? Currently we're proposing adding an unlicensed, racy 30 line file where it's unclear where the benefit is over a single command.

Can you care to explain what the failure case is on them, please?

The usual failure case in a concurrent setting: In the time between making the observation (and processing it) and updating some state variable (in the current code a directory and a PID file) things can (and will) change. And we need to keep some state as, e.g., fuser alone won't tell us why a file is being accessed (is that a brew update running or something else). To stay with the fuser example, it's also horribly slow on my system (around 5 s to completion) and spawns an entirely new perl process. Or am I missing something here?

Currently we're proposing adding an unlicensed, racy 30 line file where it's unclear where the benefit is over a single command.

I don't think it makes sense to speak of licenses when using a simple mkdir and exploiting its atomicity. I'm nor sure why you claim it's racy because as far as I know it is not. (The current implementation looks correct to me.)

Fine, as mentioned before, I don't have strong feelings here. This just feels pretty overkill for what it's being used for currently. If you run brew update in two tabs at once it'll complain but it backs onto Git's locking which behaves as expected. As mentioned before I don't really approve of fixing bugs speculatively; this is "fixing" something not reported by users and introduces new code which may have edge cases which will cause issues for users. Doesn't seem like a net positive to me.

This just feels pretty overkill for what it's being used for currently. If you run brew update in two tabs at once it'll complain but it backs onto Git's locking which behaves as expected. As mentioned before I don't really approve of fixing bugs speculatively; this is "fixing" something not reported by users and introduces new code which may have edge cases which will cause issues for users. Doesn't seem like a net positive to me.

I can sympathize with your view. In practice brew update finishes sufficiently quickly and is probably never run by users in parallel. I can imagine this might change once we flip the switch on auto-update before install/upgrade.
I think the main motivation here is that printing one understandable error generated by brew instead of the more granular error reporting by git. Also, our update involves several invocations to git and while they individually do the right thing and leave the repository in a sane state, I'm not entirely sure that our sequence of git invocations is free from bugs if it happened to run in parallel. (But yes, this is unlikely to happen in practice and the clearer user-facing error reporting might be more important.)
I'm pretty confident that using mkdir is the right thing, I'm not entirely sure yet that the rest of the implementation is robust enough that it won't introduce new issues.

A quick head up when I'm in bed. The most important motivation is I need a bash version of lock when installing vendor Ruby as part of moving to Ruby 2.0 only. brew update just happens to be a nice place to have the same feature and is helping to separate one big PR to multiple smaller ones.
Now I need to go to sleep.

A quick head up when I'm in bed. The most important motivation is I need a bash version of lock when installing vendor Ruby as part of moving to Ruby 2.0 only. brew update just happens to be a nice place to have the same feature and is helping to separate one big PR to multiple smaller ones.

Sorry if this sounds a bit harsh, but it would have helped to have that (and maybe a bit more) in the PR body instead of “No description provided.” It's not a completely trivial change and as such it deserves a few explanatory words.

Now I need to go to sleep.

Of course; don't lose sleep because of this! This PR will still be there tomorrow.

The most important motivation is I need a bash version of lock when installing vendor Ruby as part of moving to Ruby 2.0 only. brew update just happens to be a nice place to have the same feature and is helping to separate one big PR to multiple smaller ones.

While I normally agree with splitting up PRs like this I think if the lock is mainly intended for another feature it'd be good to review it in that context. Happy to leave it open for now, though.

I have update the lock implemention:

the lock will be created at /tmp folder
the lock now accepts the lock name.
address some of @UniqMartin 's concern using double lockers.

The moving to ruby 2 is still a work in process and it's another huge PR. If you are interested, you can view the process here https://github.com/Homebrew/brew/compare/master...xu-cheng:vendor

The moving to ruby 2 is still a work in process and it's another huge PR. If you are interested, you can view the process here master...xu-cheng:vendor

Do you want any comments on this yet?

Do you want any comments on this yet?

Be free. Any comment is appropriated.

@xu-cheng It seems I can't comment easily until it's a PR so maybe just worth opening it and sticking [WIP] in the title.

@mikemcquaid #195

I found a way to use flock(2) to lock the file. I have updated the implementation, please review.

@xu-cheng Nice idea but I'd rather we avoid a Python dependency here. shlock (https://developer.apple.com/legacy/library/documentation/Darwin/Reference/ManPages/man1/shlock.1.html) may be a good option on OS X and flock on Linux. If neither command exists, I think it's fine to just avoid locking and print a message telling people not to run in parallel.

@mikemcquaid the shlock is similar to my previous implementation that it is not as reliable as flock.  You can see more detail at BUGS section in the manpage.
Also shlock and flock have much different syntax to use.
How about this? Use Linux native flock if possible, otherwise use ruby to create flock similar to my current implementation. Therefore, I think I cover both Linux and OS X.

Updated the PR.

@xu-cheng Neither of those BUGS seem to matter to us? Honestly I'm not even sure why we care this much about locking brew update to stop weird messages from Git (and similarly with installing a vendored Ruby). I'd just prioritise only OS X for now until our cross-platform support is much further along.

Honestly I'm not even sure why we care this much about locking brew update to stop weird messages from Git (and similarly with installing a vendored Ruby).

As I said before, the lock is essential for install-vendor.

As I said before, the lock is essential for install-vendor.

You've said that but I still don't really understand the justification of why we need such careful locking right now and it seems massively overkill that we're at the point where we're writing off things like shlock but at this point I just want to get this mergeable and move on and hope this doesn't introduce user issues.

You've said that but I still don't really understand the justification of why we need such careful locking right now and it seems massively overkill that we're at the point where we're writing off things like shlock but at this point I just want to get this mergeable and move on and hope this doesn't introduce user issues.

Sorry, but I really disagree. As talked in previous  discussion among other maintainers, the careful locking is important. Since we can get it right, why not. And I don't think a one line ruby code is overkill, considering this is what you suggested in the early of discussion.

Ok, that's fine.

More testing and address all comments. I think this it ready.


Bug: Missing target element "hiddenInput" for "polaris-autocomplete" controller

Steps to reproduce:

Go to https://polarisviewcomponents.org/lookbook/inspect/autocomplete/basic
Open console
Select any tag from dropdown

@k0va1 thanks! Fixed 👍


Add implementation for Cognitive Services Bing Auto Suggest

Update pom.xml files to reflect the new directory structure in github

Can one of the admins verify this patch?


Create constraint only on table recreation

It would be great, if creations of constraints could be disabled for incremental materialization, and enabled for materialize=table and for full refresh.

dbt Constraints does not recreate a constraint if it is already in place. The expectation is that an incremental materialization would only add the constraint when a --full-refresh operation is performed and subsequent executions would just verify that the constraints are still there.
not_null constraints aren't really being added on subsequent executions on Snowflake. From my testing I determined that it was faster to alter the table than have logic to identify which columns are already not-null. Snowflake doesn't take any time to validate not_null constraints because it already knows from its statistics in cloud services whether any micro-partitions contain a null in a column.
If you are asking for the tests in this package to be executed selectively, that is a function controlled by dbt Core, not dbt Constraints. The tests in this package operate like any other dbt test and execute when dbt chooses to execute them.


USD to not received

My hamster token cut Gaye Lekin USD mein nahin mila tone bhi cut Gaya

@ssahil123S Thanks for posting the issue.
Your query would be best dealt with by the support team.
Please see the link below to our dedicated support line:
Support : Help Center
Note: Click on the live chat icon at the bottom corner of the page to start a conversation


event.results[i].final

Hi,
I was checcking for the code and I found this propertie "event.results[i].final" like "undefined".
Shouldn't it be "event.results[i].isFinal"?
Best regard,

Fixed in v1.0.6


Search within tags name:en or name:fr.

No locations will be found which are listed under name:en.
Example: The name of the city is available under name in Arabic and name:en in English.
Unfortunately I can't find the place if I search for it and it is available under name:en.
Is a search also possible in name:en?

The search is based on the search language of your browser: if your browser is configured to use the 'en' language, then the search is made on name:en.
Could you give us more context about this issue ? which city are you talking to ?

An example: I am on holiday in an Arab country.
There exists the tag name, name:ar, name:en and name:fr for an object (restaurant, city, ...).
The language of my browser is German.
The tag name:de does not exist there, because nobody adds it in the map, because it is not typical.
Name:en exists because the tag/language English is very common.
For example, I can't find a restaurant that can be found under name:en, because my browser language is German.
name and name:ar consists of arabic characters!
I'll never find the restaurant or the village unless the tag name:de exists.
This is also the case in Russia.
name is in Russian, but name:de does not exist.
name:en is widely used
Example:
amenity 	fast_food
name 	ماكدونالدز
name:ar 	ماكدونالدز
name:en 	Mc Donald's
Search for McDonald's is unsuccessful!


Save Actions does not work when detekt plugin is also enabled

The Save Actions plugin does not work when the detekt plugin is also installed and enabled. This may be a bug in either plugin. See other plugin's issue.

No, the autocorrect feature is disabled. Just installing and enabling the detekt plugin is enough to break Save Actions.


Revisit integration testing setup

This morning @Cafe137 asked me for a help with integration tests as they were failing with ECONNREFUSED.
I am not sure how the integration testing setup was created. Currently the local bee nodes are by default searched at http://bee-0.localhost. I assume this is thanks to bee-local? But at the same time we have the ./test/bee.sh script that orchestrates the cluster with docker and is presented as the way to go to run the test but the nodes are not found under this URL which makes the test fails. It is possible to configure that with env. variable, but I think this should work out-of-the-box.
So I would either change the defaults from http://bee-0.localhost to http://localhost:1633 or fix the ./test/bee.sh script to be reachable under that address.
@nugaon @agazso what do you think?

I vote for changing the defaults.

Yeah, we discussed it internally and we gonna change the defaults to support the ./test/bee.sh and have custom setting for CI.


ScalaFiddle.scala:-5: ERROR: Library com.thoughtworks.binding %%% binding % 10.0.1 is not allowed

I choose Binding.scala 10.0.1 in "All versions", and I got an error
ScalaFiddle.scala:-5: ERROR: Library com.thoughtworks.binding %%% binding % 10.0.1 is not allowed

See https://scalafiddle.io/sf/dGkVqlV/9

Yea, for some reason the compiler backend is not updating the libraries automatically from the editor like it should. It requires a manual restart of the compiler services. Now it works OK again.

@ochrons Errors for 10.0.2 now.
ScalaFiddle.scala:-5: ERROR: Library com.thoughtworks.binding %%% binding % 10.0.1 is not allowed

Restarted the services again, should work now :)


Daikin Auth / Config URL not loading

Describe Your Problem:
I cannot access the authorisation URL to finish the Authentication flow. I've gotten this working before, but I'm really at a dead end now.
I have tried callback server on <IP_ADDRESS> and <IP_ADDRESS> but neither makes a difference. IP and ports are identical in both config and Daikin app settings.
This was working perfectly until (I think) my Homebridge IP changed. I updated the IP in config and daikon but I've never been able to get the URL to load.
Logs (with debug mode enabled):
[06/09/2024, 11:45:26] [DaikinCloud] [API Syncing] Failed to get cloud devices from Daikin Cloud: invalid_grant (The provided authorization code or refresh token is revoked.)
Plugin Config:

{
    "clientId": "3lmGZit8ev5lx_dxnSYcq5kE",
    "clientSecret": "xIV4_fcgBDLB-DJZeUDDe5LHTs9yJ8JmLf9s7j9TIwTQBhxRAhDot53_ZhFZbUs2L-hqwSNH-AtL04VRn6bw8Q",
    "callbackServerExternalAddress": "192.XXX.X.XXX",
    "callbackServerPort": "8582",
    "oidcCallbackServerBindAddr": "<IP_ADDRESS>",
    "showExtraFeatures": false,
    "updateIntervalInMinutes": 15,
    "forceUpdateDelay": 60000,
    "platform": "DaikinCloud"
}

Fixed. I presumed . daikin-controller-cloud-tokenset file was gone because it didn't return when using dir. I had to use ls -a instead. This displayed the config file which I could then delete.

Fixed per above.

Got the same issue, following Daikin API registration change/crash/whatever
Deleting the .daikin-controller-cloud-tokenset file made the authentication process triggering again, and the registration working like a charm

under which path can I find this file?

under which path can I find this file? works it with v2.5.0 or have i update to the beta version? Thanks

I'm using the container version and it's in /var/lib/homebridge, which is the default path when you connect via ">_Terminal" through the GUI.


⚠ Bofrost.lu has degraded performance

In 3040d95, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1609 ms

Resolved: Bofrost.lu performance has improved in 5e543b3 after 7 minutes.


refactor spatial discretisation class

see #16.
the new spatial discretisation base class and derived classes need to process a Model, along with an input mesh in order to:

count the number of variables needed, and therefore the size of the state vector
replace all Variable nodes with Vector nodes
replace all spatial gradient operators with Matrix nodes

example use:
model = ReactionDiffusionModel()
param_file = Parameters("file.dat")
param_file.process(model)
disc = FiniteVolumeDiscretisation(mesh_dx=0.1, something_else=2)
y0 = disc.process(model)

My current thoughts are that the discretisation class should also generate initial conditions (perhaps from functions contained in the Variable nodes of the expression tree?), and output the initial state vector from the process function so that it can be used by the solver class

Made a start on this (and #23), but more work needed on this issue:

[ ] discretise Scalar based on variable domain (using IndependentVariable class?)
[ ] discretise Variable into Vector with the correct slice
[ ] incorporate boundary conditions into discretisation of rhs
[ ] concatenate right-hand sides into a single dydt numpy array
[ ] more testing


Code line confusion

Hi group 5,
It's great that you used projectile motion with air resistance as your function to implement. While I go through your code I am not clear on these lines
vx=vx-constdtvxmath.sqrt((vx2)+(vy2))
vy=vy-dt(g+constvymath.sqrt((vx2)+(vy2)))
Also you have used constant value defined earlier in your code. Please help me to understand these lines.

@pratibha77118 This part of the code updates the velocities considering two forces: gravitational acceleration and air drag. The gravitational force acts downward, which is why we subtract g from the vertical velocity vy. The air drag acts against the direction of motion and is dependent on the projectile's speed, hence the use of sqrt((vx2)+(vy2)) which calculates the resultant speed. The const value represents the drag coefficient.
I am sorry. I am still working on documentation. I believe that our documentation will clear all these kinds of confusions.


Write BalancerPoolAdaptor.sol and BalancerPoolAdaptor.t.sol (migrated from PR #112)

Core changes:
This PR is a continuation of PR #112 as the original PR was shelved due to other strategic priorities. Over time the old PR became too outdated vs main so this new branch was created with copied-over code from core BalancerPoolAdaptor files.
There are a number of different phases / scopes for the BalancerPoolAdaptor development. They are as follows:

Scope 1: Setup and properly calling relayer with basic joinData (using mockChainlinkDataFeed for bb-a-usd : USDC for tests)
Scope 2: Integrate fully functioning PriceRouterV2 and Balancer specific Extension contract
Scope 3: Source and prepare docs or other resources for strategists to have calldata at the ready for use with BalancerPoolAdaptor.sol

Scope 1 Original TODOs:

[x] Stub out code w/ referenced docs on how to interact with specific pool types in join/exit functions

[/] Understand how the relayer works, I think that’s indicative of the types of functions we will need

[x] Stub out strategist functions for joins/exits/swaps for respective pools

Weighted, Stables & Linear Pools require joins/exits
Composable Stable Pools require swaps
NOTE: These are all encompassed into using the BalancerRelayer and the complexities of interacting with different types of the Relayer are out of scope for the BalancerPoolAdaptor development. Details of how to encode calldata for different actions for Strategists will be outlined as per Issue #113

[x] Peer review w/ Crispy on adaptor design/approach
[x] Revise implementation code
[ ] Write unit tests & integration tests
[ ] Peer review & Finalize
[ ] Final Peer review & Finalize for audit submission

Notes:

Managed Pools outside of scope since they are not fully implemented/in use in Balancer ecosystem yet (to be done in a later adaptor)

Live Discussion Topics (discussed during the Draft PR stage)

Strategist adaptorData will need to be carefully input. A new issue, issue #113 will be used to record best practices for this. Updates to Balancer will have to be tracked in case there are breaking changes (version updates, etc.).

References:

Balancer Docs for indication of what pools use joins/exits, vs swaps:
Relayer details:
Docs on Relayer:

 ℹ Detailed Notes on DD
This documents some of the distilled steps taken so far in the due diligence/development of this adaptor:

Relayer usage:

Initially thought as something only EOAs were to use, the BalancerRelayer was explored more via assessing VaultAction.sol, BalancerRelayer.sol, etc. As well as a thorough discussion with CrispyMangoes.
Initial singular functions were created for join, exit, and swaps, but that was deemed unnecessary if BalancerRelayer.sol was to be used.

Gauge Interactions:

Mainly researched Balancer gauge codebase, docs, and Curve docs and codebase for gauge details too.
Some interfaces are not readily available so some needed to be created. The interfaces I'm referring to need work still but are just roughly done for the first commit.
msg.sender within gauge internal accounting needs to be confirmed to be cellar instead of gravityBridge addresses when dealing with depositing and withdrawing bpts

Initial PR #112  --> past work all documented there.

<!--- example - Design decisions made in PR>
<!--- example - Remember running `forge fmt` before committing the PR>
<!--- example - Reference for how to run relevant tests i.e. forge test --match-contract X --fork-url $RPC_URL -vvv>

lint on files outside of the scope of this project, may need to rebase / revert those files back. Will revisit after scope of this PR is complete.


Sometimes getting a SyntheticEvent as currentValues in formChange

Just started trying version 0.14, and formChange handler is not functioning properly. It sometimes takes normal events instead of the model. Maybe you are passing the onChange prop to the children?

Ah, I know whats wrong. Its the passing of props to to the form element. It seems that a native form also has an onChange. Will revert back to strict control of props passed. Will release fix now :-)

Try now

Yup, that's fixed now, thx :)


Run CI on all branches

There was a mistake in the project I copied the CI config from. This correctly runs CI on PR's from all branches.

Oh, so the [main] meant that only PRs from main to other branches would run the job? And no list there means all PRs from and to all brancher run it?

yep exactly. if you look at the last PR the checks didn't run 😅


[TF==2.0.0-alpha0] tf.keras.Model reinitializes set weights.

System information

Have I written custom code: Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 16.04
TensorFlow installed from (source or binary): pip install tensorflow==2.0.0-alpha0
TensorFlow version (use command below): 2.0.0-alpha0
Python version: 3.7.1
Using only CPU

Describe the current behavior
When I initialize a convolution layer with some weights, instead of the weights being set, it will be randomly re-initialized. Print output returns at each run a different weight.
Code to reproduce the issue
import tensorflow.keras
import numpy as np

weight = np.ndarray(
    shape=[1, 1, 1, 1],
    dtype='float32')
weight[0, 0, 0, 0] = -0.8888
bias = np.ndarray(
    shape=[1],
    dtype='float32')
bias[0] = 0

weights = [weight, bias]

inputs = tensorflow.keras.layers.Input(shape=(1,1,1), name='inputs')
outputs = tensorflow.keras.layers.Conv2D(filters=1,
                                 kernel_size=1,
                                 strides=(1,1),
                                 kernel_regularizer=tensorflow.keras.regularizers.l2(0.0005),
                                 weights=weights,
                                 use_bias=True,
                                 activation=None,
                                 padding='same')(inputs)
model = tensorflow.keras.Model(inputs=inputs,
                              outputs=outputs)

for layer in model.layers:
    for weight in layer.get_weights():
        print(weight) # wrong output: [[[[1.6804]]]] [0.]

Describe the expected behavior
with:

keras version 2.1.5
using tensorflow backend version 1.6.0

When I initialize a convolution layer with some weights, the weights will be set and stick. Print output returns as expected: [[[[-0.8888]]]] [0.]
This is an useful feature, especially when one is converting from one model format to another. For example when converting darknet (model.cfg, model.weights) to keras (model.h5).
Code to reproduce
import keras
import numpy as np

weight = np.ndarray(
    shape=[1, 1, 1, 1],
    dtype='float32')
weight[0, 0, 0, 0] = -0.8888
bias = np.ndarray(
    shape=[1],
    dtype='float32')
bias[0] = 0
weights = [weight, bias]
inputs = keras.layers.Input(shape=(1,1,1), name='inputs')
outputs = keras.layers.Conv2D(filters=1,
                                 kernel_size=1,
                                 strides=(1,1),
                                 kernel_regularizer=keras.regularizers.l2(0.0005),
                                 weights=weights,
                                 use_bias=True,
                                 activation=None,
                                 padding='same')(inputs)
model = keras.Model(inputs=inputs,
                              outputs=outputs)

for layer in model.layers:
    for weight in layer.get_weights():
        print(weight)  # correct output: [[[[-0.8888]]]] [0.]

Questions:
Is this intended? Or how can this be disabled? How can I help you solve this issue. Thanks for taking your time looking into this.

@mauricelucy I am closing this as it was resolved in tf-nightly-gpu-2.0-preview==2.0.0.dev20190723. Please check the gist here. Please feel free to open if the issue persisits. Thanks!


Unexpected usage of context prop on connected component

Do you want to request a feature or report a bug?
Bug/Unexpected behavior
What is the current behavior?
When passing context prop to connected component, it's replacing original Context and connect() returning an undefined.
Related code line:
https://github.com/reduxjs/react-redux/blob/94799efd81323ec07075dc303603b42300e0e034/src/components/connectAdvanced.js#L216
Example:
https://codesandbox.io/s/mm039l9q7x
What is the expected behavior?
Not use context prop or document this behavior.
Which versions of React, ReactDOM/React Native, Redux, and React-Redux are you using?  Which browser and OS are affected by this issue? Did this work in previous versions of React-Redux?
Latest

Based on my understanding, v6 allows you to provide a custom context, in which case React-Redux will use your provided context instead of its default one. This allows you to use your own context consumer in your connected components.
You need to pass the same context to both <Provider /> and your connected components.
const MyContext = React.createContext();

// provide to the Provider
<Provider store={store} context={MyContext} />

// provide to all of your connected components
// two ways of doing this:
connect(mapState, mapDispatch, null, { context: MyContext })(MyComponent)
// or
const MyConnectedComponent = connect(mapState, mapDispatch)(MyComponent)
<MyConnectedComponent context={MyContext} />

Up through v5, store was effectively a "reserved prop name" for the connected wrapper components, as the wrapper interpreted that as "this prop is an alternate Redux store to subscribe to".  Similarly, in v6, context is effectively a "reserved prop name", as it's interpreted as "this prop is an alternate React context to read the store state from".
We do need to document this, but this is intentional, and part of the reason for the major version bump.


macos Unsupported spec Error

Great work! I have this action that runs perfectly on windows-latest and ubuntu-latest, but fails to run on macos-latest with:
Run sayyid5416/pyinstaller@v1
with:
python_ver: 3.10
spec: ui.py
requirements: requirements.txt
upload_exe_with_name: s3backup
options: --onefile, --name "s3backup", --windowed
exe_path: ./dist
Run python "/Users/runner/work/_actions/sayyid5416/pyinstaller/v1/src/checks.py"
python "/Users/runner/work/_actions/sayyid5416/pyinstaller/v1/src/checks.py"
shell: /bin/bash --noprofile --norc -e -o pipefail {0}
env:
spec: ui.py
upload_exe_with_name: s3backup
File "/Users/runner/work/_actions/sayyid5416/pyinstaller/v1/src/checks.py", line 25
f"Unsupported input 'spec = {spec}' was provided. Supported types: {', '.join(supported_spec)}",
^
SyntaxError: invalid syntax
My action:
jobs:
pyinstaller-build:
runs-on: ${{ matrix.os }}
strategy:
matrix:
os: [ubuntu-latest, windows-latest, macos-latest]
steps:
- name: Create Executable
uses: sayyid5416/pyinstaller@v1
with:
python_ver: '3.10'
spec: 'ui.py'
requirements: 'requirements.txt'
upload_exe_with_name: 's3backup'
options: --onefile, --name "s3backup", --windowed

I'll look into this. Can you provide all the logs in proper format or any minimal reproducible example?

I just had the same issue, here are my logs @sayyid5416
logs_13.zip

Fails under MacOS-latest but works under the macos-13 beta image.

@AnnoyingRain5 Can you provide the link of the workflow where it failed instead of providing the zip file? It will help diagnosing the issue faster.

@sayyid5416
workflow yaml file
Workflow run
I believe this could be due to an outdated version of python being shipped with MacOS, I have run into similar issues with this in the past.

@AnnoyingRain5 It says SyntaxError, but there is no syntax error in checks.py.

I believe this could be due to an outdated version of python being shipped with MacOS

Can you try with lower python versions like 3.10 or 3.9?

Python versions below 3.10 do not support f-strings, the python version shipped with that version of macOS is below 3.10 AFAIK.

@AnnoyingRain5 If I can understand it properly, this issue is specific to this pyinstaller action That's why I'm closing this issue now.

This issue would be fixed if your script installed the latest version of python before attempting to run checks.py

@AnnoyingRain5 Can you run some tests with test branch. I've done changes you asked for.

Works great, thanks!
https://github.com/AnnoyingRain5/Relink-Client/actions/runs/5010618603

@AnnoyingRain5 It would be great if you could test with few more different types of configurations on different machines like windows, Ubuntu and MacOS

Also f-strings were added in version 3.6.

Oops, I was thinking of match statements, but... wouldn't that mean that macos-latest has a version older than 3.6? Wow.

@AnnoyingRain5 It would be great if you could test with few more different types of configurations on different machines like windows, Ubuntu and MacOS

I'll do some better tests later today, thanks!


[CSharp] Add PromDialog.Attachment method for asking the user to upload a file

This feature has been brought to Bot Builder SDK for NodeJS but not yet to the C# part (see this issue). The use case is the bot wants to prompt the user to upload a file (eventually corresponding to a certain content type). A new method Attachment for PromptDialog class could easily bring this feature.

I took the pull request. I will make refinements to it and add appropriate test cases.

Sorry I was not available the past few days so I couldn't add the test cases on time. Thanks for taking the pull request anyway.


[Bug] [CoreCLR]: MelonUtils.GetValidTypes() breaks mod invoking it under Wine

All of the following criteria must be met

[X] All Requirements must be installed.
[X] Full Latest.log file included. If no file exists then leave this unchecked and state so.

All of the following are optional to answer

[ ] Tried reinstalling the Game.
[X] Tried reinstalling MelonLoader.
[X] Tried restarting PC.
[X] Was able to see the Start Screen.

Describe the issue.
Title explains it all. I have traced down the breakage to specifically lines 223 and 224 in MelonUtils.cs. I am unable to confirm if it also happens in the standard .NET Framework version, but it does 100% happen in the experimental CoreCLR version.
Latest.log
Did you attach your log file?

[X] Yes, I attached my log file to the text box above.
[ ] No, I could not find a log file at {Game_Directory}\MelonLoader\Latest.log

@BowDown097 I wasn't able to reproduce your issue because I don't have a wine environment setup, but I've found a probable cause as well as an oversight on my part with regards to how mods are loaded when ML is not running in debug - that latest commit should fix your issue. This link should go live within a couple of minutes for a hopefully fixed build: https://nightly.link/LavaGang/MelonLoader/actions/runs/2160789757