Phoscon Web App stays empty

hi there,
i just moved my deconz from a pi 2b raspian to my homeassistant pi 4b.
i managed to get everything working including my phoscon backup i did before.
today i updated  to the new HA version and its not working anymore.
i can access Deconz and the devices are there but if i open Phoscon Web the site keeps empty.
i already tried to reinstall the addon serveral times and restart the pi/HA..
like this i cant control any lights :/
Please help!

If you are still having issues, here is what I did
Click on the phoscon "P" icon
It should give you a screen that is partially functional.
Click on the 3 horizontal bars icon in the upper left hand corner and select logout
Go back to any other menu in home assistant such as overview
Click on the deconz app.
Mine then prompted me to enter a new password twice
Once it logged in everything was functional, however the entity names had changed so I had to rename everything to get Hass entities working again.
It seems to have been changes to the conbee firmware that necessitated the reset.
I hope this helps.

I'm facing the same issue, I think it's due a lack of https support  on the Deconz/Phoscon side.
Try to access it over http, it'll work.

@Sirezul It is party that, but it also is partly to the fact you can't access it over the external IP if your port isn't open.

thank you very much for your answers.
i just did everything new and changed to the conbee stick.


Viewer Shows a Grey Outline

After turning off and then turning on again, the viewer caused a problem where there is now a grey outline blocking the pictures from showing and when going into big mode it only disappears when the mouse isn't hovering over the area. Hard to describe but there is also the mini controls appear at the top now and the configuration is behind the outline so I can't access it further.

I cannot reproduce this issue.
May be affected by other extensions or scripts.
Can you disable other extensions or scripts and try again?
Or just reinstall eh-view-enhance.

Yes reinstalling worked thank you


Backport:[Cloud Driver]Huawei CCE node operating system options are mismatched

https://github.com/rancher/rancher/issues/18674

Tested with rancher/rancher:master from Apr 30.
This version of Huawei CCE driver node os options are the same as Huawei public cloud.
Confirmed fixed.


Example traces on the homepage not available

Hello!
When I try to click on "Placebo classification and description" on the homepage, the JS tries to access https://oughtinc.github.io/static/traces/01GCZNZ1YC0XRE1QHSAV6MPWJD/trace.jsonl, which 404's. I assume that this is not intentional? :)

Those trace files are still in an old, uncompatible format, e.g. the trace for that file is stored at https://oughtinc.github.io/static/traces/01GCZNZ1YC0XRE1QHSAV6MPWJD/trace.jsonl. We've been meaning to rerun the recipes so that ice.ought.org can be updated with new code and viewing e.g. https://ice.ought.org/traces/01GCZNZ1YC0XRE1QHSAV6MPWJD includes the latest features, but we've been lagging. I hadn't really thought about this opposite but equally broken perspective. Maybe we should just hide all those traces in the meantime.

Haha no worries, though just FYI nothing seems to exist at https://oughtinc.github.io/ , and on top of that the CORS request from ice.ought.org fails :P

Yeah, right now we're just using https://oughtinc.github.io for static file serving

Right, I'm just saying, it looks like static files are not being served from https://oughtinc.github.io as the site apparently doesn't currently exist

I edited the first sentence of my comment which had said the wrong thing.
There is definitely a file at https://oughtinc.github.io/static/traces/01GCZNZ1YC0XRE1QHSAV6MPWJD.jsonl that exists and is being served, which is what we need. But there's no index page at https://oughtinc.github.io/.

the CORS request from ice.ought.org fails

I don't know what you mean. https://ice.ought.org/traces/01GCZNZ1YC0XRE1QHSAV6MPWJD looks fine to me and I see no network or console errors.

Ohhh my bad, I got that confused with the other trace URL you posted. All good now!


chore: bdd-spring-1574806253 to 0.0.1

chore: Promote bdd-spring-1574806253 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Timestamp with nanoprecision results in arrow error

Export of a datetime2(7) column with this value: "8900-12-31 00:00:00.0000000" results in the following error: pyarrow.lib.ArrowInvalid: Casting from timestamp[ns] to timestamp[us] would lose data: -2639760884514619392.
If the value is cast to a datetime2(3) no error and getting the data from parquet looks ok.
However if the value is cast to datetime2(4) no errors are reported but the value stored in parquet now is: "1886-05-08 05:05:15.485381".
Not sure if it's an error in arrow-odbc or an error in arrow.
I've used pyarrow version 12.0.1 and arrow-odbc: 1.2.0

Hi thanks for the Bug report. Are you writing or reading data? What database and driver are you using?

hm, okay I am missing something. This test passes for me:
def test_timestamp_ns():
    """
    Query a table with one row. Should return one batch
    """
    table = "OneRow"
    os.system(f'odbcsv fetch -c "{MSSQL}" -q "DROP TABLE IF EXISTS {table};"')
    os.system(f'odbcsv fetch -c "{MSSQL}" -q "CREATE TABLE {table} (a DATETIME2(7));"')
    rows = "a\n2014-04-14 21:25:42.0748412"
    run(["odbcsv", "insert", "-c", MSSQL, table], input=rows, encoding="ascii")

    query = f"SELECT * FROM {table}"
    reader = read_arrow_batches_from_odbc(
        query=query, batch_size=100, connection_string=MSSQL
    )
    it = iter(reader)
    actual = next(it)

    schema = pa.schema([("a", pa.timestamp("ns"))])
    expected = pa.RecordBatch.from_pydict({"a": [1397510742074841200]}, schema)
    print(expected[0])
    print(actual[0])
    assert expected == actual

    with raises(StopIteration):
        next(it)

Still running on a windows PC and with ODBC 17 driver version, but I think I am likely to miss something else.

Given that I now have test reading Datetime2(7) which seems to work, and also looking at the original error message you send I have doubts I can reprocude it. It seems the error occurs converting from pyarrow to pyarrow. arrow-odbc would use [ns] to represent a Datetime2(7) to not loose any precision, as it is also documented in the readme. It seems to me some downstream processing expects [us].
Best Markus

I've looked into apache arrow to check if there are limitations in the high value of a datetime but so far did not found any relevant info.

I really would need a reproducing example. High values did not cause this error then I inserted in the test (the year did overflow though in the database, but reading it was fine). Also the error message points from an arrow to arrow conversion, which does not happen within this library. At least it is not supposed to. Do you have a minimum reproducing example?

Hi Markus,
This is an example. In the query text you can try the scenarios by casting to a datetime2(7) => results in error, by casting to datetime2(3) => everything works ok and by casting to datatime2(4) no errors but when data is retrieved (I used duckDB) the value for valid_time = '1886-05-08 05:05:15.485381'
`from arrow_odbc import read_arrow_batches_from_odbc
import pyarrow as pa
import pyarrow.parquet as pq
from pyarrow import fs
connection_string="Driver={ODBC Driver 18 for SQL Server};Server=localhost;TrustServerCertificate=yes;"
lfs = fs.LocalFileSystem()
def read_rows():
return read_arrow_batches_from_odbc(
query=f"select cast('8900-12-31' as datetime2(4)) as valid_time",
connection_string=connection_string,
batch_size=100,
user="sa",
password="iRefact2017",
)
def write_parquet(writer, batch):
writer.write(batch)
def export():
reader = read_rows()
writer = pq.ParquetWriter(where=f"./test.parquet",schema=reader.schema,filesystem=lfs,compression="snappy")
for batch in reader:
write_parquet(writer, batch)
writer.close()
export()
`

Mmmh, the code is not nicely formatted. Hopefully you can use it.

Hello @ErikJansenIRefact ,
fromatting was not a problem. If I replace the final call to export in your example with read_rows it runs just fine. The exception is not raised when reading rows from the database, that works, but them writing them to parquet. My reading of the error is that the parquet writer does not support nanosecond precision and does not convert silently in order to avoid information loss you are not aware of. My suggestion would be to transform any timestamp with nanoseconds precision into one with milliseconds precision before writing it to parquet.
Best, Markus

Did some more value tests. A value: select cast('2200-12-31' as datetime2(7)) as valid_time works fine. A value: select cast('2300-12-31' as datetime2(7)) as valid_time results in an error. So it seems there is a kind of high value for datetimes.

Thanks Markus. So basically it's an issue in Arrow.

You are welcome
IMHO it is more a decision of arrow, rather than an issue. Not silently dropping information is likely a design choice. However, I think that parquet does support nano seconds, so they also might just decide to support it in the writer.
FYI: If you just want to export a database to parquet you could also skip the intermediate step via arrow and use the odbc2parquet command line tool.

Tested without writing to parquet. It seems the value is not converted correctly already in arrow.
The datetime2(7) '8900-12-31' is converted to a pyarrow wrongly. So it's not an issue in writing to parquet. Checked the docs and parquet version 2.6 is required to support nanosecond precision datetimes.
This is the result of the recordBatch (converted to a pyarrow table). It is a nanosecond precision timestamp but somewhere it's value is converted wrongly.
pyarrow.Table
valid_time: timestamp[ns]
valid_time: [[1886-05-08 05:05:15.485380608]]

Sorry to bother you again but could you take a look if somewhere in the conversion from database to arrow something goes wrong?

This is a different issue. I also saw that behavior. It is highly likely that this is an integer overflow. I would need to investigate in order to figure out if something can be done about it.

Hello @ErikJansenIRefact
arrow-odbc-py 1.2.2 is released. It raises an error with a descriptive message if it discovers out of range timestamps.
Best, Markus


Add trigger to a pipeline

Add an action to the pipeline context menu to be able to add a trigger a pipeline. Adding a trigger would create the required Tekton resources (EventListener, TriggerTemplate, etc) in order to configure triggers and expose a webhook url that user can add to the Git provider repository settings. Example:
https://github.com/tektoncd/triggers/tree/master/examples/github
User should be able to easily get access to the webhook url associated with the pipeline after triggers are configured.

Should this be through Tekton CLI or k8s API?


[FEATURE] Add instructions/explanation on what profiles are

Is your feature request related to a problem? Please describe.
Profiles are currently glanced over in our documentation, with no explanation of what profiles are and how to use them. We should add a section explaining this feature

Closing this as being tracked by #416


transferTo can transfer only part of the file, so need to loop

We (Elastic APM) have a customer (using tomcat 9.0.72) that is hitting this bug. The file copy is getting interrupted (likely from CPU time slicing signals, which is happening because of additional profiling executing in the background) and so only partly completes. As the current implementation doesn't loop, this results in a corrupt war/zip file that can't be loaded. To complete the file copy, transferTo needs to loop

LGTM

@rmaucher applied this PR earlier today.


chore: import json-files instead of requiring them

Testing

Trade-offs

Dependencies

Screenshots

:tada: This PR is included in version 2.153.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.153.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


SDP-831: Edit receivers

Edit receiver page. Email and External ID only

stellar-disbursement-platform-frontend-preview is available here:http://sdp-frontend-pr5.previews.kube001.services.stellar-ops.com/


Upgrade to Go 1.18

Also update getTestResty() to use either PROJECT_* or JFROG_* env vars

@maheshjfrog No update to CHANGELOG since there is no functionality changes, and we are not making a release. We can include this in the next release if we want.


ENH: Ndim linear operator

Reference issue
Closes Issue  #11908
What does this implement/fix?
Adds ndim class attribute to LinearOperator.

Please, explain me why the completely unrelated test fails.

Hi @Mazay0
Sometimes those types of changes get into the master branch in between releases. I think Matt and Ilhan are pretty close to a fix.
If that is the only thing failing then I would not worry about it on this PR. It’s a known issue and once a fix is in you can always rebase this branch to reflect the changes if that fix goes in before this one.
Sincerely,
-Lucas Roberts

On Apr 22, 2020, at 12:53 PM, Mazay0<EMAIL_ADDRESS>wrote:

Please, explain me why the completely unrelated test fails.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Thanks, merged.


SQL Service Accounts and GPO Settings

Hello,
Please provide more information regarding group policy settings for SSIS service accounts. As well as the error of packages getting stuck in "Pending Execution" when permissions are not set for the service account.
GPO requirements:
Impersonate a client after authentication
Replace a process level token
Adjust memory quotas for a process

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

ID: 9b3831a3-6c86-243c-4b07-8960e4d06d7b
Version Independent ID: dfd7599d-88eb-99f2-c227-0c9dc82bfd87
Content: Configure Windows service accounts and permissions - SQL Server
Content Source: docs/database-engine/configure-windows/configure-windows-service-accounts-and-permissions.md
Product: sql
Technology: configuration
GitHub Login: @markingmyname
Microsoft Alias: maghan

@bernaljo -- thank you again for writing to us.
@markingmyname -- please look into this issue.

#assign @chugugrace

@bernaljo
Have you had a chance to visit this page as well - https://docs.microsoft.com/en-us/sql/integration-services/service/integration-services-service-ssis-service?

Closing this as it's been a while since there's no response.


Tenant information is not set if clone mediator is used.

When logged in using a tenant, the tenant information is not printed in front of the log event inside the clone mediator. Log mediators outside of the clone mediator works fine. It seems the reason here is tenant information is not set inside the clone mediator. This is evident from the TID in the wso2carbon.log(inside clone mediator its -1).
Steps to Reproduce

Create an API
In the in sequence add a clone mediator
Inside clone mediator target add a log mediator
Add some log mediators after clone mediator too.
Send a request to the API.
In the wso2carbon.log you can see tenant information is not printed in logs inside clone mediator while tenant information is printed in the logs outside the clone mediator.

public commit: #https://github.com/wso2/wso2-synapse/commit/ecfe8d24a361ab26367f0febecdb5758fa03b1af,


Incorrect endpoints for update forwardProxy

There was no entry for forwardProxy after executing the following commands.

From my understanding, the above endpoints are correctly as follows (need /config/authsettingsV2).
If my understanding is correct, could you please update as the following?
Export settings
az rest --uri /subscriptions/REPLACE-ME-SUBSCRIPTIONID/resourceGroups/REPLACE-ME-RESOURCEGROUP/providers/Microsoft.Web/sites/REPLACE-ME-APPNAME/config/authsettingsV2?api-version=2020-09-01 --method get > auth.json
Import settings
az rest --uri /subscriptions/REPLACE-ME-SUBSCRIPTIONID/resourceGroups/REPLACE-ME-RESOURCEGROUP/providers/Microsoft.Web/sites/REPLACE-ME-APPNAME/config/authsettingsV2?api-version=2020-09-01 --method put --body @auth.json

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

ID: 75e17529-8b8a-1d67-f0e1-840d1d3ca990
Version Independent ID: 265645df-ef21-4631-1744-7014b3ee681a
Content: Authentication and authorization - Azure App Service
Content Source: articles/app-service/overview-authentication-authorization.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

@syukumoto
Thanks for your feedback! We will investigate and update as appropriate.


The website examples should more prominently link back to component pages

Lots of links point to the examples but it's not obvious that each component page also contains examples.

I think this is now in a much better state.


Add minute based aggregation of pokemon activity to heatmap

This PR adds a slider below the heatmap(both normal and single report) when it's activated. The slider can be used to adjust the data which is used for the heatmap, based on the minute on which the pokemon spawned or was active. For example if the slider's set to 30, all pokemon with the minute of the expire_timestamp being between 30 and 45 are used, as a pokemon is active for 15 minutes.

the heatmap now also takes the hour of the day into account and hence it's a 24 hour slider(10 minute steps)

Looks awesome!

That is awesome!

@rollator I slightly adjusted code style and merged it. Thanks!

Great, thanks :D


Importing assest fails during creation

I'm trying to import a simple entity with an asset related to it but during the import I get, I already tried many things like clean up the whole workspace
Uncaught exception: can't modify frozen String: ""
	/usr/local/lib/ruby/gems/2.7.0/gems/http-2.2.2/lib/http/response/body.rb:57:in `force_encoding'
	/usr/local/lib/ruby/gems/2.7.0/gems/http-2.2.2/lib/http/response/body.rb:57:in `to_s'
	/usr/local/Cellar/ruby/2.7.1_2/lib/ruby/2.7.0/forwardable.rb:235:in `to_s'
	/usr/local/lib/ruby/gems/2.7.0/gems/contentful-management-2.12.0/lib/contentful/management/response.rb:85:in `no_content_response?'
	/usr/local/lib/ruby/gems/2.7.0/gems/contentful-management-2.12.0/lib/contentful/management/response.rb:33:in `initialize'
	/usr/local/lib/ruby/gems/2.7.0/gems/contentful-management-2.12.0/lib/contentful/management/client.rb:387:in `new'
	/usr/local/lib/ruby/gems/2.7.0/gems/contentful-management-2.12.0/lib/contentful/management/client.rb:387:in `execute_request'
	/usr/local/lib/ruby/gems/2.7.0/gems/contentful-management-2.12.0/lib/contentful/management/client.rb:459:in `put'
	/usr/local/lib/ruby/gems/2.7.0/gems/contentful-management-2.12.0/lib/contentful/management/request.rb:51:in `put'
	/usr/local/lib/ruby/gems/2.7.0/gems/contentful-management-2.12.0/lib/contentful/management/asset.rb:61:in `block in process_file'
	/usr/local/lib/ruby/gems/2.7.0/gems/contentful-management-2.12.0/lib/contentful/management/asset.rb:53:in `each'
	/usr/local/lib/ruby/gems/2.7.0/gems/contentful-management-2.12.0/lib/contentful/management/asset.rb:53:in `process_file'
	/usr/local/lib/ruby/gems/2.7.0/gems/contentful_bootstrap-3.12.0/lib/contentful/bootstrap/templates/base.rb:129:in `rescue in block in create_assets'
	/usr/local/lib/ruby/gems/2.7.0/gems/contentful_bootstrap-3.12.0/lib/contentful/bootstrap/templates/base.rb:112:in `block in create_assets'
	/usr/local/lib/ruby/gems/2.7.0/gems/contentful_bootstrap-3.12.0/lib/contentful/bootstrap/templates/base.rb:111:in `each'
	/usr/local/lib/ruby/gems/2.7.0/gems/contentful_bootstrap-3.12.0/lib/contentful/bootstrap/templates/base.rb:111:in `create_assets'
	/usr/local/lib/ruby/gems/2.7.0/gems/contentful_bootstrap-3.12.0/lib/contentful/bootstrap/templates/base.rb:20:in `run'
	/usr/local/lib/ruby/gems/2.7.0/gems/contentful_bootstrap-3.12.0/lib/contentful/bootstrap/commands/update_space.rb:54:in `update_json_template'
	/usr/local/lib/ruby/gems/2.7.0/gems/contentful_bootstrap-3.12.0/lib/contentful/bootstrap/commands/update_space.rb:32:in `run'
	/usr/local/lib/ruby/gems/2.7.0/gems/contentful_bootstrap-3.12.0/lib/contentful/bootstrap/command_runner.rb:23:in `update_space'
	/Users/eric.santos/Github/contentful-database-importer.rb/lib/contentful/database_importer.rb:60:in `bootstrap_update_space!'
	/Users/eric.santos/Github/contentful-database-importer.rb/lib/contentful/database_importer.rb:80:in `update_space!'
	/Users/eric.santos/Github/contentful-database-importer.rb/lib/contentful/import.rb:354:in `<top (required)>'

the import.rb looks like this
  include Contentful::DatabaseImporter::Resource

  self.table_name = 'program'
  self.content_type_id = 'program'
  self.content_type_name = 'program'

  id Contentful::DatabaseImporter::IdGenerator::Base, template: '{{content_type_id}}_{{id}}' # Optional - By default it's the IdGenerator::Base(template: '{{content_type_id}}_{{index}}')

  field :id, type: :integer
  field :femaleWebTitle, type: :asset

end```

Just an extra info when I try to run again

Updating from JSON Template '/Users/eric.santos/Github/contentful-database-importer.rb/import_Gymondo Contentful Space20200611-15568-887wbd'
Creating Asset 'webapp-titleimage-wide'
Asset 'webapp_titleimage_wide' already created! Updating instead.
Traceback (most recent call last):
	15: from /Users/eric.santos/Github/contentful-database-importer.rb/lib/contentful/import-program.rb:36:in `<main>'
	14: from /Users/eric.santos/Github/contentful-database-importer.rb/lib/contentful/database_importer.rb:80:in `update_space!'
	13: from /Users/eric.santos/Github/contentful-database-importer.rb/lib/contentful/database_importer.rb:60:in `bootstrap_update_space!'
	12: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful_bootstrap-3.12.0/lib/contentful/bootstrap/command_runner.rb:23:in `update_space'
	11: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful_bootstrap-3.12.0/lib/contentful/bootstrap/commands/update_space.rb:32:in `run'
	10: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful_bootstrap-3.12.0/lib/contentful/bootstrap/commands/update_space.rb:54:in `update_json_template'
	 9: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful_bootstrap-3.12.0/lib/contentful/bootstrap/templates/base.rb:20:in `run'
	 8: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful_bootstrap-3.12.0/lib/contentful/bootstrap/templates/base.rb:111:in `create_assets'
	 7: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful_bootstrap-3.12.0/lib/contentful/bootstrap/templates/base.rb:111:in `each'
	 6: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful_bootstrap-3.12.0/lib/contentful/bootstrap/templates/base.rb:114:in `block in create_assets'
	 5: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful-management-2.12.0/lib/contentful/management/environment_association_methods_factory.rb:23:in `create'
	 4: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful-management-2.12.0/lib/contentful/management/resource.rb:256:in `create'
	 3: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful-management-2.12.0/lib/contentful/management/resource_requester.rb:31:in `create'
	 2: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful-management-2.12.0/lib/contentful/management/request.rb:51:in `put'
	 1: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful-management-2.12.0/lib/contentful/management/client.rb:459:in `put'
/usr/local/lib/ruby/gems/2.7.0/gems/contentful-management-2.12.0/lib/contentful/management/client.rb:388:in `execute_request': HTTP status code: 409 Conflict (Contentful::Management::Conflict)
Message: Version mismatch error. The version you specified was incorrect. This may be due to someone else editing the content.
Request ID: 2f08a9eb2ea57b0e240255d8209b01be
	22: from /Users/eric.santos/Github/contentful-database-importer.rb/lib/contentful/import-program.rb:36:in `<main>'
	21: from /Users/eric.santos/Github/contentful-database-importer.rb/lib/contentful/database_importer.rb:80:in `update_space!'
	20: from /Users/eric.santos/Github/contentful-database-importer.rb/lib/contentful/database_importer.rb:60:in `bootstrap_update_space!'
	19: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful_bootstrap-3.12.0/lib/contentful/bootstrap/command_runner.rb:23:in `update_space'
	18: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful_bootstrap-3.12.0/lib/contentful/bootstrap/commands/update_space.rb:32:in `run'
	17: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful_bootstrap-3.12.0/lib/contentful/bootstrap/commands/update_space.rb:54:in `update_json_template'
	16: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful_bootstrap-3.12.0/lib/contentful/bootstrap/templates/base.rb:20:in `run'
	15: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful_bootstrap-3.12.0/lib/contentful/bootstrap/templates/base.rb:111:in `create_assets'
	14: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful_bootstrap-3.12.0/lib/contentful/bootstrap/templates/base.rb:111:in `each'
	13: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful_bootstrap-3.12.0/lib/contentful/bootstrap/templates/base.rb:112:in `block in create_assets'
	12: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful_bootstrap-3.12.0/lib/contentful/bootstrap/templates/base.rb:129:in `rescue in block in create_assets'
	11: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful-management-2.12.0/lib/contentful/management/asset.rb:53:in `process_file'
	10: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful-management-2.12.0/lib/contentful/management/asset.rb:53:in `each'
	 9: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful-management-2.12.0/lib/contentful/management/asset.rb:61:in `block in process_file'
	 8: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful-management-2.12.0/lib/contentful/management/request.rb:51:in `put'
	 7: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful-management-2.12.0/lib/contentful/management/client.rb:459:in `put'
	 6: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful-management-2.12.0/lib/contentful/management/client.rb:387:in `execute_request'
	 5: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful-management-2.12.0/lib/contentful/management/client.rb:387:in `new'
	 4: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful-management-2.12.0/lib/contentful/management/response.rb:33:in `initialize'
	 3: from /usr/local/lib/ruby/gems/2.7.0/gems/contentful-management-2.12.0/lib/contentful/management/response.rb:85:in `no_content_response?'
	 2: from /usr/local/Cellar/ruby/2.7.1_2/lib/ruby/2.7.0/forwardable.rb:235:in `to_s'
	 1: from /usr/local/lib/ruby/gems/2.7.0/gems/http-2.2.2/lib/http/response/body.rb:57:in `to_s'
/usr/local/lib/ruby/gems/2.7.0/gems/http-2.2.2/lib/http/response/body.rb:57:in `force_encoding': can't modify frozen String: "" (FrozenError)

Turns out was an issue with the ruby version that I was running 2.7.0 and seems like something related to immutable strings was introduced, I'm not sure actually maybe the repo owner can answer what's the compatibility.


Tag new version

Could you guys tag a new version with the current state? We at php-pm need the new MultipartParser :)

We're working on completing the work on MultipartParser in #41. The current state doesn't work well with large requests :(.

Let me add that I'm planning to spend most of my day on #41 tomorrow to get this done A.S.A.P.

Very very nice @WyriHaximus! Let me know if I can support you somewhere.

Will do @marcj, I'll get the todos checked off and ping you to test them in php-pm :).

Thanks for filing this ticket, I can assure you we're working hard on this :+1:
This ticket currently targets an unstable development feature, so I've just filed #105 to keep track of the underlying feature request here. Please bear with us, we'll keep this ticket updated :+1:


Failed to build Docker image: exec: "docker": executable file not found in $PATH

Just cloned anythingv3.0 off of Replicate and am attempting to run it on my computer. After cloning the repository, I am running the command cog run script/download-weights but receive the error: "Building Docker image from environment in cog.yaml...
ⅹ Failed to build Docker image: exec: "docker": executable file not found in $PATH"
First time doing this. Not quite sure what to do.
Here is what the cog.yaml file looks like:
build:
  gpu: true
  python_version: "3.10"
  python_packages:
    - "diffusers==0.11.0"
    - "torch==1.13.0"
    - "ftfy==6.1.1"
    - "scipy==1.9.3"
    - "transformers==4.25.1"
    - "accelerate==0.15.0"

predict: "predict.py:Predictor"

@RationalChestnut According to the prerequisites in readme, you will need to install Docker before you can run Cog.


Start scanning on multiple HCI-devices not possible

I want to create an application, which scans for devices on multiple HCI-devices ( up to 3 dongles)
that's why I tried to set NOBLE_HCI_DEVICE_ID and create new Noble Objects (from noble/lib/noble.js) but the second noble do not start.
might be cause the binding is always the same object (module.exports = new NobleBindings(); in hci-socket/bindings.js)
so it would be nice to have the feature to scan on multiple bluetooth dongles
here is some example code
import Noble from 'noble/lib/noble';
import bindings from 'noble/lib/resolve-bindings';

var initNoble = function (noble) {
  noble.on('stateChange', function (state) {
    if (state === 'poweredOn') {
      noble.startScanning();
    } else {
      console.log('noble powered OFF');
    }
  });
}
let scan = function(hciId){
  process.env.NOBLE_HCI_DEVICE_ID = '' + hciId;
  let noble = new Noble(bindings());
  initNoble(noble);
}

scan(0);
scan(1);
scan(2);

The main goal of this project is a uniform API for all supported platforms (macOS, Linux, Windows, web bluetooth etc).
Feel free to fork and mod the source to get what you want working :)


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-main" workflow

Codecov Report

Merging #755 (682c4a0) into main (cfaa8f5) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@           Coverage Diff           @@
##             main     #755   +/-   ##
=======================================
  Coverage   95.69%   95.69%
=======================================
  Files           1        1
  Lines         395      395
  Branches       53       53
=======================================
  Hits          378      378
  Misses         17       17


Changing the location of Windows SDK

Hi,
I'm currently dealing with this issue: https://github.com/Microsoft/vcpkg/issues/5866
I have the proper Windows SDK installed, but since my C HDD is rather small, VC installed these SDKs to a location on my D drive. Now the OpenGL installation cannot find the SDKs because it's looking for them at:
C:\Program Files (x86)\Windows Kits\10\Lib\10.0.17763.0...
but they're not there, they are at:
D:\Windows Kits\10\Lib\10.0.17763.0...
How can I tell vcpkg to look for SDKs on this other location? Thanks!

@vahisht, in VCPKG, it try to find windows sdk by environment variable '$env:ProgramFiles' and '${env:ProgramFiles(x86)}',  so you can check the 2 variables value, from your logs, it seems that point to 'C:\Program Files (x86)', try to workaround by override that value to windows sdk location manually in VCPKG, not sure if that works,
I tried to install VS and SDKs to D drive by VS installer, however, it installed sdks to C:\Program Files (x86), so I haven't try that workaround yet. let me know if that works.
See
bootstrap.ps1 and vcpkg_get_windows_sdk.cmake

@cbezault, do you have any good suggestion?

@PhoebeHui Thanks for the tip! I already tried a different workaround as suggested by the user cwbhhjl in #5495 , which relies on a Windows directory junction placed in the C:\Program Files (x86)\Windows Kits\ that links to the correct folder on the other drive. This solution does work, even though it requires some magic with cmd (not powershell).
Specifically what you want to do is use the mklink command with the /J parameter

@vahisht, mklink the correct folder looks more intelligent, great to hear that works! I will close this issue, and left #5495 open to track, let's see if we have a good solution to handle this in future.


AOT compiled JavaScript?

Hello! Is it possible that Graal's JavaScript partial evaluator can be used to AOT JavaScript code?

Hi @roman01la, please see this discussion.


Check for nulls within IsWanderer and IsWayfarer

Couldn't quite find where in the method the null reference error is coming from, so I just checked for nulls everywhere since it's not a super commonly used function anymore.

Accepted


Support sending and receiving file descriptors over Unix domain sockets

The Unixes and Unix-likes support sending an open file descriptor between two processes using Unix domain sockets. The receiving process receives a reference to an open kernel object as if it called dup() on the original file descriptor. Users have expressed a desire to send file descriptors over NTS and NTC sockets. This PR adds support to NTS socket to send and receive file descriptors over Unix domain sockets. Support for similar functionality in NTC will be proposed in a subsequent PR.

I have addressed all your review comments except for the one about partially setting up recvmsg before checking the user supplies valid capacity, and your comment about a UDS test to ensure timestamps and file descriptors can be passed together in the same control message.


Bounds atrribute not working for a array of lat and lng

Since in leaflet maps we have possibility to set map centered on bounds points like here:
map.fitBounds([
    [40.712, -74.227],
    [40.774, -74.125]
]);

is it possible to use array of lat and lng like above in bounds attribute?
I noticed that in bounds.js you check if bounds have properties like southWest and northEast  and if not you don't fire fitBounds().
Documentation

http://leafletjs.com/reference.html#latlngbounds factory accepts any length Array of coordinates. I wonder if we can do the same, it just means calculating maximums and minimums lats/longs of points in list. Suggestions on preferred/already in use functional library for min/max calculations? I'm new to the project.


Fixes four bugs

Fixes four bugs:

An error saving state data on the golf assessment page due to refactoring on the index page and the assessment calling functions there (the refactoring was not carried through to the assessment).
In some cases the save and exit button will not close the window; now a message is displayed in that case.
Tetris was completely broken due to a fixed typo in a function name not globally applied.
Improvements to conformance of data for numeric type questions caused the correct answer for those questions to display code to the user; now it just displays the minimum number (as all numeric correct answers are single values in this prototype).

:+1:.


Read function needs to actually pass through workers & chunk size

The read function doesn't actually pass through the workers & chunk size. Oops.
To control chunk size:
storage/sliced_object_download_component_size (bytes) (docs)
To control max workers:
storage/process_count (I think)

The docs don't specify the default for the process count. Need to figure out what it does. Maybe it's already smart, and we actually shouldn't try to "help" it. Based on our reference benchmark actually …

I tried tweaking these settings to try and squeeze even more performance out but couldn’t improve on the default behavior.

So … well, TODO: rename issue to "remove these parameters from read function"


Monorepo and different .lintstagedrc.json configuration files

We have a monorepo with .lintstagedrc.json in every project and in .husky/pre-commit we have npm exec -- lint-staged. This works fine.
Now we would like to add a "lint-push" hook. For this we created .husky/pre-push with npm exec -- lint-staged --diff="origin/develop...$(git rev-parse --abbrev-ref HEAD)" but this will use the same .lintstagedrc.json files all over the monorepo.
It would be nice to have a parameter telling what should be the config name. We can't use --config because this can point only to a single configuration which we can't use in our monorepo.
Or can it be already done with some workaround?

Hello, do you mean you want to use multiple configs with different names in your pre-push hook compared to normal pre-commit? Maybe I'm misunderstanding.
A possible workaround might be to switch to the JS config because then you could create it dynamically based on an env variable, for example.

@iiroj yes, you got it right. Switching to JS config is a good idea, thank you. Feel free to close this issue.


Does the stateful_lstm.py example make sense?

I was going over the example in:
https://github.com/fchollet/keras/blob/master/examples/stateful_lstm.py @fchollet
and I'm a bit confused. The RNN assumes size (nb x 1 x 1). When cos (of size N x 1 x 1) is given as input, model._fit will randomly sample different mini-batches from the input at each iteration. How is the temporal dependency kept? I'm also confused about the propagation of derivatives with stateful RNNs -  how are the derivatives wrt the internal states propagated back in time?

I'm also confused about the propagation of derivatives with stateful RNNs - how are the derivatives wrt the internal states propagated back in time?

They're not. "Stateful" only means that the final states from one batch are reused as the initial states for the next batch.
I don't understand your first question.

Cool. In the first question I meant that the final states from the previous batch will have nothing to do with the current batch if they are sampled at random. Or am I missing something?

@fchollet It actually doesn't:

shuffle=False is missing in call to fit()
training data is not shuffled in regard to batch_size (kth timestep for sequence s should be at [s+k*batch_size, ...])

(2) can be fixed by inserting after line 41:
assert cos.shape[0] % batch_size == 0
cos = cos.reshape(batch_size, -1, cos.shape[1], cos.shape[2])
cos = cos.transpose(1, 0, 2, 3)
cos = cos.reshape(-1, cos.shape[2], cos.shape[3])

Before:

Epoch 0 / 25
Epoch 1/1
50000/50000 [==============================] - 22s - loss: 339.1427
Epoch 1 / 25
Epoch 1/1
50000/50000 [==============================] - 22s - loss: 149.8113

Fixed:

Epoch 0 / 25
Epoch 1/1
50000/50000 [==============================] - 22s - loss: 79.9879
Epoch 1 / 25
Epoch 1/1
50000/50000 [==============================] - 23s - loss: 9.7246

@NasenSpray I agree with 1st point (shuffle=False), but would you be so kind to elaborate on your additions on shuffle in regard to batch_size?
I've added your insertion to the code and it effectively shuffles the input sequence the way when 1st element of the initial 'cos' will be followed by the 2000th element, 2nd element - by the 2001st element, and so on. It is strange and results in the very strange output:

May be you could explain a little bit more?

Yes, shuffle should be set to False. Thanks for spotting this.
On 26 February 2016 at 10:38, Dmitry Lukovkin<EMAIL_ADDRESS>wrote:

@NasenSpray https://github.com/NasenSpray I agree with 1st point
(shuffle=False), but would you be so kind to elaborate on your additions on
shuffle in regard to batch_size?
I've added your insertion to the code and it effectively shuffles the
input sequence the way when 1st element of the initial 'cos' will be
followed by the 2000th element, 2nd element - by the 2001st element, and so
on. It is strange and results in the very strange output:
[image: image]
https://cloud.githubusercontent.com/assets/5587574/13361674/304bbf16-dcd1-11e5-9fef-84c0543c4182.png
May be you could explain a little bit more?
—
Reply to this email directly or view it on GitHub
https://github.com/fchollet/keras/issues/1820#issuecomment-189417684.

@fchollet credits go to @NasenSpray actually ;)

@lukovkin think about how data is fetched and what that means for stateful RNNs. Example with batch size 2:

As you can see, the sequences must be interleaved in such a way that the individual "lanes" in a mini-batch get consecutive timesteps of their sequence. The code cuts the data in len/batch_size chunks and interleaves them, but I forgot about the plots and that's why it looks so messed up.

@NasenSpray Sorry, I don't get your notation wrt LSTM(n) - what does LSTM(0) and LSTM(1) exactly mean and why LSTM is spread across the batches?
As I could see from the docs and code,

You can set RNN layers to be 'stateful', which means that the states
computed for the samples in one batch will be reused as initial states
for the samples in the next batch.

And in the code it also just sets initial_states equal to states.
So as far as I understand, LSTM itself is not being spanned across the batches.

I really think something about stateful is not working. My biggest confirmation of this is the given example (stateful_lstm.py) works exactly the same if you set stateful=False
It would be great if there was some example toy problem that needed state and showed how it works. I am trying to understand the code but theano debugging still makes my brain explode.
I was trying to modify the text generation to  emulate the behavior of this code base (karpathy/min-char-rnn.py). But even though I think I have everything working it only really works when timesteps are large enough. At 1 timestep it does not converge beyond basic 1 step prediction.

I really think something about stateful is not working. My biggest confirmation of this is the given example (stateful_lstm.py) works exactly the same if you set stateful=False

@9aradox this is because fit and predict are called with the entire sequence, so stateful or not the result would be the same.

From the Keras FAQ (http://keras.io/faq/#how-can-i-use-stateful-rnns) it says:

all batches have the same number of samples
If X1 and X2 are successive batches of samples, then X2[i] is the follow-up sequence to X1[i], for every i.

While model.fit will make mini-batches that does not follow these assumptions (especially 2.). To illustrate the problem, if we change the input sequence length to be non-dividable by batch_size:
cos = gen_cosine_amp(xn=507)

training will crash.

I am not sure what you are saying. I think I understand the batching issues. I don't have any problem running code it is just if you have a problem that needs state and you trying to use 1 timestep then it just doesn't converge.
I do find the number 2 restriction confusing but I am pretty sure with 1 timestep like this example it doesn't matter.
None of this explains why the stateful example in keras works fine when you set stateful=False. This seems to invalidate it as an example. Also it does not matter if you do the prediction one item at a time. This code also works fine with stateful = False in both layers.
#WARNING This loop takes forever.
print('Predicting')
predicted_output = []
x = np.zeros((batch_size, 1, 1))
for c in cos:
x [0] = c
prediction = model.predict(x, batch_size=1)
#print (prediction)
predicted_output.append(prediction[0][0])

@9aradox I had stateful working with batch_size=1, but not for cos in example, but for financial TS data.
It is interesting that val loss with stateful and shuffle=True was better than for stateful=True and shuffle=False, which doesn't make a lot of sense.

I think a reason why the example still works in the stateful=false case, might have to do with the fact that the period on the cosine function is 25, the same as the batch size, this would equate to predicting a bunch of exponentials going to zero. I haven't tried but worth mentioning. I think @NasenSpray had it right by reshuffling the series such that consecutive batches process the series in order as in the doc.

I think a reason why the example still works in the stateful=false case, might have to do with the fact that the period on the cosine function is 25, the same as the batch size, this would equate to predicting a bunch of exponentials going to zero.

You would think the period is 25 because of the argument period in gen_cosine_amp, but it is in fact close to 1000 due to the way that argument is used:
cos[i, 0, 0] = amp * np.cos(idx / (2 * np.pi * period))
I think the actual reason for why stateful=False still gets "good" results is that the model tries to predict only one step ahead, which is a very easy task because of the data. To see how easy it is, consider the simple baseline where your prediction of one step ahead is exactly the same as the current value. This simple baseline, surprisingly, achieves MSE=0.0203 which is way better than anything the current model achieves. To really test the effect of statefulness, one should set the look-ahead (prediction point ahead of current time) to something like 100 to make the problem more challenging. When you do that, be careful to to use
expected_output[i, 0] = cos[i + lahead, 0, 0]
At line 44, because for some reason the current code tries to predict the average of look-ahead values. I did all this and I got an MSE of 35 and 243 for stateful and stateless models respectively, which clearly shows the benefit of statefulness. I think the example should be modified as well.

@NasenSpray
Your solution works when (as you said yourself) the labels are also rearranged. Here is the code for those interested. Add all of these after line 48:
print('Rearranging the data to satisfy stateful requirements')
cos = cos.reshape(batch_size, -1, cos.shape[1], cos.shape[2])
cos = cos.transpose(1, 0, 2, 3)
cos = cos.reshape(-1, cos.shape[2], cos.shape[3])
expected_output = expected_output.reshape(batch_size, -1, expected_output.shape[1])
expected_output = expected_output.transpose(1, 0, 2)
expected_output = expected_output.reshape(-1, expected_output.shape[2])

The fixed version will get an MSE close to 2 for lookahead=100 in just 3 epochs which is pretty good (compare to the results I reported in my previous comment).

@sadeghmir
I recently have been thinking of this problem and you provided exactly right answer. Thanks a log.
A small observation is below.
With the modification
     expected_output[i, 0] = cos[i + lahead, 0, 0]
I had:
stateful=False  resulted in loss 241
stateful=True  resulted in loss 53
Then, in the hope of making the learning faster, I changed the batch_size to 2500 from 25.
Thanks to nvidia titan X, it became much faster but the result was quite different, the loss was 322. However, the output waveform was much better then the former two cases. So, I change the epochs=250 from 25, which resulted in almost all the same wave form with loss 166!
My conclusion is that the magnitude of the loss is somewhat unrelated to the overall waveform reconstruction.

How does the statement

If x1 and x2 are successive batches of samples, then x2[i] is the follow-up sequence to x1[i], for every i.

make sense in the use case of a time series? Instead of having a dependency between x1[i] and x2[i], one has a dependency between x1[i] and x1[i+1], so between two adjacent samples within one batch. I strongly believe that the way the data has to be modelled for LSTMs in Keras is misleading, even in other contexts. I cannot see how this way would make sense.


go: enable http.url standard tag test

If it's ok for you, it's good to me, just put it as ready for review


Remove experimental flag from Vault docs

https://helidon.io/docs/v2/#/mp/vault/01_vault

PR was merged. This issue can be closed. Resolves didn't work. I don't know why.


Fixes position.Point2.closest method

I found myself needing to get the closest element in a list of points set at Point2(math.inf, math.inf). This was failing with the following exception
Traceback (most recent call last):
  File "/Users/jthomas/.pyenv/versions/3.6.5/lib/python3.6/site-packages/sc2/main.py", line 127, in _play_game_ai
    await ai.on_step(iteration)
  File "/Users/jthomas/git/lambdanaut-sc2/lambdanaut/bot.py", line 3112, in on_step
    await self.micro_manager.run()
  File "/Users/jthomas/git/lambdanaut-sc2/lambdanaut/bot.py", line 3021, in run
    await self.do_combat()
  File "/Users/jthomas/git/lambdanaut-sc2/lambdanaut/bot.py", line 2989, in do_combat
    nearest_enemy_cluster = army_center.closest(self.bot.enemy_clusters)
  File "/Users/jthomas/.pyenv/versions/3.6.5/lib/python3.6/site-packages/sc2/position.py", line 63, in closest
    return closest_element
UnboundLocalError: local variable 'closest_element' referenced before assignment

This sets the closest element to be the first one before continuing onwards to the next elements, and also fixes my problem.

I'm doing some stuff with k-means where a cluster with 0 data points has a centroid of Math.inf. Sometimes, especially early in the game, none of my clusters have any data points, so it's a list of Math.inf.

This PR would also fix an edge case where all elements in the list are the same point.

If you think this is superfluous, then I'm okay with it not being merged.
I think it makes the function "safer" though

Its not up to me to decide.
I just thought its a very rare case.
We could also change if distance < closest_distance_squared: to if distance <= closest_distance_squared:
I think that would be a "cleaner" fix.

I merged master into develop to start working on the dev branch. I fixed this issue while updating :)
Develop branch should include a fix for your problem now.


Multi updates needed before the modification of the post to be accepted

I need to modify at least 2 times post until the post is really updated : the hubpress post editor show the old version after saving modification the first time.

@javathought does this behavior still happen for you? If not, would you mind closing out the bug?

I did not do post updates since your comment. Tried one today : it's ok and did not happen.


Question about compartmentalized ciliogenesis vs cytosolic ciliogenesis

Hi @krchristie  - think that you are the best person to answer this :-)
I see that we have the term cytosolic ciliogenesis in the GO but not compartmentalized ciliogenesis.
I was looking at this paper https://pubmed.ncbi.nlm.nih.gov/34357392/ where "Twitchy is required for compartmentalised and cytosolic ciliogenesis" and I wasn't sure if 'non-motile cilium assembly' GO:1905515 was equivalent to compartmentalized ciliogenesis?

Hi @hattrill
The simple answer is that 'non-motile cilium assembly' GO:1905515 is NOT equivalent to compartmentalized ciliogenesis, though ALL 'non-motile cilium assembly' GO:1905515 IS compartmentalized ciliogenesis, according to Avidor-Reiss & Leroux 2015 (abstract copied in below). However, MOST 'motile cilium assembly is also compartmentalized ciliogenesis.
Avidor-Reiss T, Leroux MR. Shared and Distinct Mechanisms of Compartmentalized and Cytosolic Ciliogenesis. Curr Biol. 2015 Dec 7;25(23):R1143-50. doi: 10.1016/j.cub.2015.11.001. PMID:26654377 https://pubmed-ncbi-nlm-nih-gov.ezproxy.jax.org/26654377/

Most motile and all non-motile (also known as primary) eukaryotic cilia possess microtubule-based axonemes that are assembled at the cell surface to form hair-like or more elaborate compartments endowed with motility and/or signaling functions. Such compartmentalized ciliogenesis depends on the core intraflagellar transport (IFT) machinery and the associated Bardet-Biedl syndrome complex (BBSome) for dynamic delivery of ciliary components. The transition zone (TZ), an ultrastructurally complex barrier or ‘gate’ at the base of cilia, also contributes to the formation of compartmentalized cilia. Yet, some ciliated protists do not have IFT components and, like some metazoan spermatozoa, use IFT-independent mechanisms to build axonemes exposed to the cytosol. Moreover, various ciliated protists lack TZ components, whereas Drosophila sperm surprisingly requires the activity of dynamically localized TZ proteins for cytosolic ciliogenesis. Here, we discuss the various ways eukaryotes use IFT and/or TZ proteins to generate the wide assortment of compartmentalized and cytosolic cilia observed in nature. Consideration of the different ciliogenesis pathways allows us to propose how three types of cytosol-exposed cilia (primary, secondary and tertiary), including cilia found in the human sperm proximal segment, are likely generated by evolutionary derivations of compartmentalized ciliogenesis.

My understanding is that in mammals, where most cells have a single "primary" non-motile cilium and various kinds of epithelial cells have multiple motile cilia, all of this ciliogenesis is compartmentalized. I'll get to sperm ciliogenesis in a bit.
From the paper on Twitchy you are asking about it clearly also occurs in Drosophila sperm ciliogenesis. With respect to annotation of the Twitchy paper, I think that since Drosophila has such a limited set of cells that make cilia at all, I think you could safely annotate to the "non-motile cilium assembly" term.
My recollection is "cytosolic ciliogenesis" is a bit of a special situation that occurs is certain places such as some of the proteozoa, which I think may be the reason @paolaroncaglia originally created the term.
The mammalian sperm ciliogenesis that I'm familiar with has extra assembly mechanisms like the manchette so I'm not completely sure how that would be categorized. I don't think I've ever encountered the term "cytosolic ciliogenesis" when reading about sperm ciliogenesis in mice. However this quote from the Twitchy paper you asked about as well as the Avidor-Reiss & Leroux abstract both talk about at least some metazoan spermatogenesis being cytosolic.
Hodge SH, et al. Twitchy, the Drosophila orthologue of the ciliary gating protein FBF1/dyf-19, is required for coordinated locomotion and male fertility. Biol Open. 2021 Aug 15;10(8):bio058531. doi: 10.1242/bio.058531. Epub 2021 Aug 6. PMID:34357392

Primary cilia are compartmentalised from the rest of the cell by a ciliary gate comprising transition fibres and a transition zone. The ciliary gate allows the selective import and export of molecules such as transmembrane receptors and transport proteins. These are required for the assembly of the cilium, its function as a sensory and signalling centre and to maintain its distinctive composition. Certain motile cilia can also form within the cytosol as exemplified by human and Drosophila sperm. The role of transition fibre proteins has not been well described in the cytoplasmic cilia.

I wonder if we need to look more closely into whether sperm ciliogenesis and possible create terms for both cytosolic & compartmentalized versions..., noting at the same time that sperm structure is relatively varied across species/taxa and assembly might also be variable. I don't really have time to look into that right now though...
Does this address your current annotation needs @hattrill ?
If you think we should have new terms to address that at least some spermatogenesis is cytosolic, I guess we could leave the ticket open until I have a chance to consider if we should have multiple types of "sperm flagellum assembly", one term under "cytosolic ciliogenesis" & another under a term for "compartmentalized ciliogenesis" that does not yet exist.
Let me know what you think @hattrill

Hi @krchristie and @hattrill ,

My recollection is "cytosolic ciliogenesis" is a bit of a special situation that occurs is certain places such as some of the proteozoa, which I think may be the reason @paolaroncaglia originally created the term.

It was actually added by @ukemi in Jan 2017. There's no PMID. The only direct annotation is to Drosophila.
Best,
Paola

Hi @krchristie
Thanks for that - it explains a lot and is very helpful. From what you've said, I think that I am happy to just explicity label when it is 'cytosolic ciliogenesis' rather than go down the rabbit hole of creating many more terms - a lot of the various flavours of ciliogenesis are just variations on a theme and are not when defined in how exactly they differ as far as I can see. I'll close this - it will be useful for future reference!
Hi @paolaroncaglia thanks for responding  - lovely to hear from you. Hope all is well with you!

Hi @hattrill - I've reopened this because I read a little bit more of the Avidor-Reiss & Leroux mini-review of cytosolic vs compartmentalized ciliogenesis and I think that this does actually reflect some different mechanisms of ciliogenesis that merit better incorporation into the ontology.
I have other higher priority projects right now, but I want to remember to get back to this. I'll definitely check in with you before making any changes that might affect Drosophila annotations.

@hattrill - Now that I understand cytosolic ciliogenesis better, I wanted to add this quote from the Avidor-Reiss & Leroux mini-review since it might affect your understanding of how you want to do your annotations.
Basically, at least in sperm (I'm not as clear on the protozoa yet), "cytosolic ciliogenesis" is NOT a type of ciliogenesis, it is a part of of a specialized ciliogenesis that occurs in certain cells,  i.e. some sperm and some protozoa AND the compartmentalized portion of ciliogenesis occurs BEFORE the cytosolic phase of ciliogenesis in both mammalian and Drosophila sperm.
So, when the paper you asked about says "Twitchy is required for compartmentalised and cytosolic ciliogenesis", you might want to look at whether they think Twitchy is involved in both compartmentalised and cytosolic ciliogenesis, OR whether Twitchy in ONLY involved in compartmentalized ciliogenesis, but thus disrupts cytosolic ciliogenesis as well because the preceding compartmentalized phase of ciliogenesis did not occur correctly.

Drosophila Sperm Flagella

Drosophila and other insects have compartmentalized sensory cilia and largely cytosolic sperm flagella. Like mammalian sperm and Giardia flagella, Drosophila spermatid flagella comprise two regions, but in Drosophila the proximal cytosolic axoneme is very long ($1,800 mm), whereas the distal compartmentalized cilium is very short ($2 mm) (Figure 3Av) [32,46].

In spermatocytes, flagella formation initiates with compartmentalized ciliogenesis, whereby a basal body docks at the plasma membrane and forms a short ($1 mm) primary cilium (Figure 3Av). However, this compartmentalized ciliogenesis is independent of IFT, and the cilium is composed mainly of a TZ [21,24]. Later during meiosis, the basal body, together with the membrane-enclosed axoneme, invaginates into the cell and attaches to the nucleus. Subsequently, in spermatids, axonemal microtubules extend from the short compartmentalized region derived from the spermatocyte primary cilium. While this extension takes place, the TZ migrates distally along the axoneme and away from the basal body, leaving behind a cytosolic microtubule-based axoneme. The cytosolic portion elongates and ultimately forms the strikingly long cytosolic cilium. Cytosolic ciliogenesis continues by addition of dynein arms and other motile axoneme components directly from the cytoplasm [32,46]. Finally, the cytosolic axoneme associates with the plasma membrane through a process called individualization (reviewed in [47]).

Several studies strongly argue that IFT is dispensable for Drosophila sperm cytosolic ciliogenesis. Mutations in kinesin-II or core IFT subcomplex components (such as nompB/IFT88/ Polaris/OSM-5, Oseg1/IFT122, and Oseg2/IFT172) disrupt sensory cilia, but not sperm formation [3,29,30]. In contrast, the TZ was recently shown to play a role in separating the cytosolic sperm region from the compartmentalized flagellar tip. Specifically, several TZ proteins, namely Cep290,
B9d1, B9d2, and Mks1, migrate away from the basal body to expose the proximal sperm axoneme to the cytoplasm [21]. The TZ protein Cep290 is essential for compartmentalization and axoneme assembly of the flagellar tip [21]. The axoneme forming at the flagellar tip later becomes the cytosolic axoneme and therefore disruption of Cep290 impacts the cytosolic axoneme.

Because the formation of a short compartmentalized cilium that depends on TZ proteins precedes the formation of the cytosolic axoneme, the TZ machinery may be indirectly essential for cytosolic ciliogenesis in Drosophila sperm.

Thanks @krchristie - that's  really helpful. I will go back and have another look with this in mind.

@hattrill What is the action for this one?

It appears that this was an issue about annotation choice and is resolved.


bpf: Remove misleading MaxIdentity const

The MaxIdentity const was incorrectly used to define the BPF map size for the
policy tail call. The value should be the maximum endpoint ID. Fortunately the
value was the same but as we grow the identity space, the BPF maps would become
unnecessarily big.

This change is

test-me-please


Move to flipboxfactory/craft-meta

We're removing usage of this plugin from our clients and we recommend you switch to SuperTable, Neo, etc.


ratelimit: make HTTP filter timeout configurable.

This was a requested feature in #990 and it also turns out that
//test/integration:ratelimit_integration_test was flaking on the low
default timeout in ASAN builds.
There are still some other flakes that occur in --runs_per_test=1000,
but these seem unrelated.
Fixes #990.

This is great, thanks. As long as you are in here do you mind doing this for the TCP rate limit filter also?

Do you want to stick with "indefinite" default timeout for TCP filter or give it some  default value?

Oops. There is no timeout? :(
I would just make it 20ms default to match the HTTP one.


Fix image stretching

Codecov Report

Merging #673 into master will increase coverage by 11.70%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master     #673       +/-   ##
===========================================
+ Coverage   58.35%   70.06%   +11.70%
===========================================
  Files          98       20       -78
  Lines        5117     1306     -3811
===========================================
- Hits         2986      915     -2071
+ Misses       2131      391     -1740

Impacted Files
Coverage Δ

...s/CompoundMessage/Views/CompoundBubbleLayout.swift

...ttoAdditions/Source/Common/UIColor+Additions.swift

...rcleProgressIndicatorView/CircleProgressView.swift

...sage/Content/MessageContentPresenterProtocol.swift

...Input/Photos/PhotosInputPermissionsRequester.swift

...ems/TextMessages/TextMessagePresenterBuilder.swift

...tions/Source/Input/HorizontalStackScrollView.swift

...aceholder/PhotosInputPlaceholderDataProvider.swift

ChattoAdditions/Source/Common/Cache.swift

...dditions/Source/Input/Text/TextChatInputItem.swift

... and 67 more

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 eefb2e5...e28cf98. Read the comment docs.


Implement interpolated skybox stars

This adds an implementation to interpolate the skybox stars. The stars are originally drawn using texture rectangles, which are not possible to interpolate. Instead we have to draw the stars as quads against the projection matrix to take advantage of the matrix interpolation system.
The stars have "real" world positions which we can use to position a matrix, and then scale to match the shape of each star, then we apply the billboard matrix rotation so that they always face the camera. We have to perform additional math on the star positions to bring the stars "closer" to the camera, as some of them are beyond the Far clipping value of the projection matrix (causing them to not render).
The interpolated stars flow will only execute when a FPS setting above 20 is used, otherwise the original stars are rendered.
I did my best to calculate the math such that the interpolated stars are as close as possible in size/position to how the original stars were. Any remaining differences are largely just from texture rectangles "snapping" to whole integer values, where as quads have more precision.
https://github.com/user-attachments/assets/7cf2e24c-2c04-4c2b-9072-831621dc1344
There is an additional bug fix to correct missing alpha fading on the stars when they appear/disappear. This required a similar "fix" that the bombers notebook needed for some of its elements.
Closes #492

I could also see this worth being pointed to Satoko instead so that it gets release sooner.


Documentation: Add instructions to install NPM for Jupyter lab install

NPM is required to install lab extensions but is not mentioned in the docs.

https://github.com/twosigma/beakerx-www/commit/90c9305ae8590410e077b6047d327337b95b2e96


Add 16.0 image

I've done a little local testing, and this should just work.
Odoo appears to use Python 3.10 for their own testing. We can add other versions if we want.

Odoo appears to use Python 3.10 for their own testing.

What is the evidence? runbot?

Yes, runbot, see http://runbot33.odoo.com/runbot/static/build/19496136-16-0/logs/base.txt

Thanks!
If Odoo's runbot is on 3.10 I suppose it is ok to test OCA on 3.10 too.


Not able to use repos.getReadme()

Hey Mike,
Thanks for this great package. I am not able to get the read me for a specific repo, I am supposed to pass repo.id and user.id?
`gitClient.repos.getReadme({
user: user,
repo: repo
}, (err, res)=> {
   // ...
  });`

I'm getting a 404, I tried passing the id's or repo.name, user.login, no success.
Also it's not clear why it requires the user as parameter?
Thanks,
Philippe.

This repo is no longer maintained.
You should be able to get the readme with the following fork: https://github.com/kaizensoze/node-github. You shouldn't need the id's, just the names so: user: "kaizensoze", repo: "node-github".
docs: https://kaizensoze.github.io/node-github/#api-repos-getReadme

Thanks a bunch!


lnwallet: Extract funding tx creation to a separate method

handleContributionMsg does a lot of things and could use some refactoring to improve readability. I have extracted the funding tx creation to a separate method but I'm open to rethinking or expanding the scope of this refactor.
We are testing out some alternative funding arrangements at @muun and this would also make it easier to keep our changes synced with upstream.

Since this PR is not actually changing behavior or adding tests, I'll close awaiting upcoming changes to the wallet which can incorporate a similar refactoring.


flyway: 6.5.5 -> 7.1.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/flyway/versions.
meta.description for flyway is: "Evolve your Database Schema easily and reliably across all your instances"
meta.homepage for flyway is: "https://flywaydb.org/"
meta.changelog for flyway is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 7.1.1 with grep in /nix/store/bxrvdvbs8fp02p9ara99n6i5cabag4v3-flyway-7.1.1

directory tree listing: https://gist.github.com/8b7a0e2bca67bd62c57b5cad56c595d0

du listing: https://gist.github.com/3e4ad2b2788022a65ac2d73416c7768c

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
flyway

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/bxrvdvbs8fp02p9ara99n6i5cabag4v3-flyway-7.1.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A flyway https://github.com/r-ryantm/nixpkgs/archive/1a130e752ab0ca5c1d9b582378c501602143eb3c.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/bxrvdvbs8fp02p9ara99n6i5cabag4v3-flyway-7.1.1
ls -la /nix/store/bxrvdvbs8fp02p9ara99n6i5cabag4v3-flyway-7.1.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

1 package built:

flyway

Maintainer pings
cc @cmcdragonkai for testing.

Result of nixpkgs-review pr 102292 run on x86_64-darwin 1

1 package built:

flyway


Polarity of LiPo battery connector

Hello all!
The board doesn't have the usual + and - markings near the battery connector, and I don't want to fry the board :)
Does anyone know which one is + and - ?
Thanks.

Realized that the pigtail cable that comes with the board already has the needed polarity.

The appropriate and usually supplied connector is polarized and thus only
plugs in one way. It can be verified without power using an ohm meter. And
then using the appropriate black and red sharpie markers for future
reference
On Thu, Mar 31, 2022, 10:02 AM Levy Carneiro Jr. @.***>
wrote:

Hello all!
The board doesn't have the usual + and - markings near the battery
connector, and I don't want to fry the board :)
Does anyone know which one is + and - ?
Thanks.
—
Reply to this email directly, view it on GitHub
https://github.com/Xinyuan-LilyGO/TTGO-T-Display/issues/82, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AWCIWVTJSQ2NMXQEHMKREC3VCW5AFANCNFSM5SFVZ4KA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Weave contacting old hosts-- NOT listed in ipam status. How to fix?

Our production cluster is having problems.  We know the issue is somehow related to #3300  and others.
We understand the reclaiming issue, and we know a fix is in progress for that.
What we've been doing as a workaround is to manually run this:
weave --local status ipam
and then remove unreachable peers.
Up until today, that's always worked. But today, we are seeing that even after removing all unreachable peers, we still see weave attempting and connecting to old hosts--even when IPAM shows no unreachable peers.
Here is the output of weave --local status ipam ( note no unreachable peers listed)
[root@ip-172-22-21-36 ~]# docker exec $CONTAINER_ID /home/weave/weave --local status ipam
a2:72:ce:d0:74:8c(ip-172-22-21-36.ec2.internal)   131072 IPs (06.2% of total) (20 active)
e2:c3:34:fa:1d:4a(ip-172-22-0-158.ec2.internal)    65536 IPs (03.1% of total)
0e:30:5d:48:8f:1a(ip-172-22-16-109.ec2.internal)    32768 IPs (01.6% of total)
fa:93:43:24:ce:ed(ip-172-22-8-124.ec2.internal)    65536 IPs (03.1% of total)
a6:7f:9c:d4:b7:aa(ip-172-22-5-85.ec2.internal)   262144 IPs (12.5% of total)
ea:44:8e:b0:8b:f9(ip-172-22-13-48.ec2.internal)   131072 IPs (06.2% of total)
76:d7:31:af:88:6e(ip-172-22-5-11.ec2.internal)    32768 IPs (01.6% of total)
b2:8a:72:cb:e1:dc(ip-172-22-13-118.ec2.internal)  1245184 IPs (59.4% of total)
72:95:b2:4d:0a:54(ip-172-22-21-228.ec2.internal)   131072 IPs (06.2% of total)

But we still see that pod attempting to  connect to old nodes:
9/11/18
3:25:58.112 PM
2018-09-11T19:25:58.112052Z ::  stream=stderr k8s_pod_name=weave-net-h6tjz k8s_pod_id=2e58a5cd-a5bd-11e8-93de-1216123c75f4 k8s_namespace_name=kube-system k8s_host=ip-172-22-21-36.ec2.internal k8s_controller-revision-hash=715543512 k8s_name=weave-net k8s_pod-template-generation=4 k8s_role_kubernetes_io/networking=1  INFO: 2018/09/11 19:25:58.111709 ->[<IP_ADDRESS>:6783] error during connection attempt: dial tcp4 :0-><IP_ADDRESS>:6783: connect: connection timed out
env =	prod host =	ip-172-22-21-36 source =	/apps/fluent-out/kubernetes.log.20180911.log sourcetype =	container_logs timeendpos =	27
9/11/18
3:25:55.167 PM
2018-09-11T19:25:55.167990Z ::  stream=stderr k8s_pod_name=weave-net-h6tjz k8s_pod_id=2e58a5cd-a5bd-11e8-93de-1216123c75f4 k8s_namespace_name=kube-system k8s_host=ip-172-22-21-36.ec2.internal k8s_controller-revision-hash=715543512 k8s_name=weave-net k8s_pod-template-generation=4 k8s_role_kubernetes_io/networking=1  INFO: 2018/09/11 19:25:55.167684 ->[<IP_ADDRESS>:6783] error during connection attempt: dial tcp4 :0-><IP_ADDRESS>:6783: connect: connection timed out
env =	prod host =	ip-172-22-21-36 source =	/apps/fluent-out/kubernetes.log.20180911.log sourcetype =	container_logs timeendpos =	27
9/11/18
3:25:20.479 PM
2018-09-11T19:25:20.479820Z ::  stream=stderr k8s_pod_name=weave-net-h6tjz k8s_pod_id=2e58a5cd-a5bd-11e8-93de-1216123c75f4 k8s_namespace_name=kube-system k8s_host=ip-172-22-21-36.ec2.internal k8s_controller-revision-hash=715543512 k8s_name=weave-net k8s_pod-template-generation=4 k8s_role_kubernetes_io/networking=1  INFO: 2018/09/11 19:25:20.479638 ->[<IP_ADDRESS>:6783] error during connection attempt: dial tcp4 :0-><IP_ADDRESS>:6783: connect: connection timed out
env =	prod host =	ip-172-22-21-36 source =	/apps/fluent-out/kubernetes.log.20180911.log sourcetype =	container_logs timeendpos =	27
9/11/18
3:24:38.751 PM
2018-09-11T19:24:38.751900Z ::  stream=stderr k8s_pod_name=weave-net-h6tjz k8s_pod_id=2e58a5cd-a5bd-11e8-93de-1216123c75f4 k8s_namespace_name=kube-system k8s_host=ip-172-22-21-36.ec2.internal k8s_controller-revision-hash=715543512 k8s_name=weave-net k8s_pod-template-generation=4 k8s_role_kubernetes_io/networking=1  INFO: 2018/09/11 19:24:38.751631 ->[<IP_ADDRESS>:6783] error during connection attempt: dial tcp4 :0-><IP_ADDRESS>:6783: connect: connection timed out
env =	prod host =	ip-172-22-21-36 source =	/apps/fluent-out/kubernetes.log.20180911.log sourcetype =	container_logs timeendpos =	27
9/11/18
3:22:58.271 PM
2018-09-11T19:22:58.271834Z ::  stream=stderr k8s_pod_name=weave-net-h6tjz k8s_pod_id=2e58a5cd-a5bd-11e8-93de-1216123c75f4 k8s_namespace_name=kube-system k8s_host=ip-172-22-21-36.ec2.internal k8s_controller-revision-hash=715543512 k8s_name=weave-net k8s_pod-template-generation=4 k8s_role_kubernetes_io/networking=1  INFO: 2018/09/11 19:22:58.271652 ->[<IP_ADDRESS>:6783] error during connection attempt: dial tcp4 :0-><IP_ADDRESS>:6783: connect: connection timed out

I had noticed this but not put too much priority on it, since the underlying issue is in-process. This turned out to be a mistake.  Today in production, one node in a similar state as above became completely unresponsive and unable to run workloads. These messages were in the kubelet logs:
Sep 11 15:00:48 ip-172-22-5-85.colinx.com kubelet[26696]: E0911 15:00:48.027998   26696 kuberuntime_manager.go:646] createPodSandbox for pod "fluentd-log-collector-7rj88_ops(873bc81e-b5e8-11e8-a439-12dbc5d74712)" failed: rpc error: code = Unknown desc = NetworkPlugin cni failed to set up pod "fluentd-log-collector-7rj88_ops" network: unable to allocate IP address: Post http://<IP_ADDRESS>:6784/ip/043abf8a8261ea4bd530395b71ab8273374ae7a4650efe575188707cd925e55e: dial tcp <IP_ADDRESS>:6784: connect: connection refused
Sep 11 15:00:48 ip-172-22-5-85.colinx.com kubelet[26696]: E0911 15:00:48.028056   26696 pod_workers.go:186] Error syncing pod 873bc81e-b5e8-11e8-a439-12dbc5d74712 ("fluentd-log-collector-7rj88_ops(873bc81e-b5e8-11e8-a439-12dbc5d74712)"), skipping: failed to "CreatePodSandbox" for "fluentd-log-collector-7rj88_ops(873bc81e-b5e8-11e8-a439-12dbc5d74712)" with CreatePodSandboxError: "CreatePodSandbox for pod \"fluentd-log-collector-7rj88_ops(873bc81e-b5e8-11e8-a439-12dbc5d74712)\" failed: rpc error: code = Unknown desc = NetworkPlugin cni failed to set up pod \"fluentd-log-collector-7rj88_ops\" network: unable to allocate IP address: Post

Again, we understand that a fix for the root issue (not cleaning up old peers ) is underway.  What we need now is a way to clean up old peers that works even when there are no unreachable peers in ipam status, and that doesn't involve stopping all the workloads.
Our cluster is k8s 1.10.3, based on kops 1.10.beta in AWS

@dcowden thanks for reporting this issue

one node in a similar state as above became completely unresponsive and unable to run workloads.

Based on the kubelet log NetworkPlugin cni failed to set up pod I assume it is weave-net pods that is not responding or failed to setup pod. When in this state did you see any activity/errors in the weave pod logs?

I'm going to pull all of the logs from all weave pods during the event. the file will be large, but it will have all we can offer in terms of diagnosis.
One message I see that's really odd is this one:
WARN: 2018/09/11 20:06:05.876256 Vetoed installation of hairpin flow FlowSpec{keys: [EthernetFlowKey{src: ea:44:8e:b0:8b:f9, dst: aa:d8:e1:9c:db:8a} InPortFlowKey{vport: 1}], actions: [OutputAction{vport: 1}]}

It looks like the first unusual message I see in the logs is at 1:15pm. each weave pod reports a message like this one:
 2018-09-11T17:15:12.611382Z ::  stream=stderr k8s_pod_name=weave-net-bg27v k8s_pod_id=39f582d5-a64c-11e8-93de-1216123c75f4 k8s_namespace_name=kube-system k8s_host=ip-172-22-5-11.ec2.internal k8s_controller-revision-hash=715543512 k8s_name=weave-net k8s_pod-template-generation=4 k8s_role_kubernetes_io/networking=1  DEBU: 2018/09/11 17:15:12.610249 EVENT UpdatePod {"metadata":{"annotations":{"ad.datadoghq.com/ptplace-bff.check_names":"[\"prometheus\"]","ad.datadoghq.com/ptplace-bff.init_configs":"[{}]","ad.datadoghq.com/ptplace-bff.instances":"[ { \"prometheus_url\": \"http://%%host%%:8080/metrics/\", \"namespace\": \"ptplace-bff\", \"metrics\": [ \"*\" ] } ]"},"creationTimestamp":"2018-08-30T19:23:57Z","generateName":"ptplace-bff-55698bd6d7-","labels":{"affiliation":"colinx","app":"ptplace","billing":"ecom","component":"ptplace-bff","dr":"mission-critical","heritage":"Tiller","pod-template-hash":"1125468283","release":"ptplace-bff"},"name":"ptplace-bff-55698bd6d7-rw94q","namespace":"default","resourceVersion":"42878536","selfLink":"/api/v1/namespaces/default/pods/ptplace-bff-55698bd6d7-rw94q","uid":"3dbfc523-ac8a-11e8-a439-12dbc5d74712"},"spec":{"containers":[{"image":"quay.io/colinx/ptplace:1.0.9430","imagePullPolicy":"Always","lifecycle":{"preStop":{"exec":{"command":["/home/appuser/preStop.sh"]}}},"name":"ptplace-bff","ports":[{"containerPort":8080,"protocol":"TCP"}],"readinessProbe":{"failureThreshold":3,"httpGet":{"path":"/ptpr/api/heartbeat","port":8080,"scheme":"HTTP"},"initialDelaySeconds":90,"periodSeconds":5,"successThreshold":1,"timeoutSeconds":90},"terminationMessagePath":"/dev/termination-log","terminationMessagePolicy":"File"}],"dnsPolicy":"ClusterFirst","imagePullSecrets":[{"name":"gitlab"},{"name":"quay"}],"nodeName":"ip-172-22-5-85.ec2.internal","restartPolicy":"Always","schedulerName":"default-scheduler","securityContext":{},"serviceAccount":"colinx","serviceAccountName":"colinx","terminationGracePeriodSeconds":43200},"status":{"conditions":[{"lastProbeTime":null,"lastTransitionTime":"2018-08-30T19:23:57Z","status":"True","type":"Initialized"},{"lastProbeTime":null,"lastTransitionTime":"2018-08-30T19:25:48Z","status":"True","type":"Ready"},{"lastProbeTime":null,"lastTransitionTime":"2018-08-30T19:23:57Z","status":"True","type":"PodScheduled"}],"hostIP":"<IP_ADDRESS>","phase":"Running","podIP":"<IP_ADDRESS>","qosClass":"Guaranteed","startTime":"2018-08-30T19:23:57Z"}} {"metadata":{"annotations":{"ad.datadoghq.com/ptplace-bff.check_names":"[\"prometheus\"]","ad.datadoghq.com/ptplace-bff.init_configs":"[{}]","ad.datadoghq.com/ptplace-bff.instances":"[ { \"prometheus_url\": \"http://%%host%%:8080/metrics/\", \"namespace\": \"ptplace-bff\", \"metrics\": [ \"*\" ] } ]"},"creationTimestamp":"2018-08-30T19:23:57Z","generateName":"ptplace-bff-55698bd6d7-","labels":{"affiliation":"colinx","app":"ptplace","billing":"ecom","component":"ptplace-bff","dr":"mission-critical","heritage":"Tiller","pod-template-hash":"1125468283","release":"ptplace-bff"},"name":"ptplace-bff-55698bd6d7-rw94q","namespace":"default","resourceVersion":"45031531","selfLink":"/api/v1/namespaces/default/pods/ptplace-bff-55698bd6d7-rw94q","uid":"3dbfc523-ac8a-11e8-a439-12dbc5d74712"},"spec":{"containers":[{"image":"quay.io/colinx/ptplace:1.0.9430","imagePullPolicy":"Always","lifecycle":{"preStop":{"exec":{"command":["/home/appuser/preStop.sh"]}}},"name":"ptplace-bff","ports":[{"containerPort":8080,"protocol":"TCP"}],"readinessProbe":{"failureThreshold":3,"httpGet":{"path":"/ptpr/api/heartbeat","port":8080,"scheme":"HTTP"},"initialDelaySeconds":90,"periodSeconds":5,"successThreshold":1,"timeoutSeconds":90},"terminationMessagePath":"/dev/termination-log","terminationMessagePolicy":"File"}],"dnsPolicy":"ClusterFirst","imagePullSecrets":[{"name":"gitlab"},{"name":"quay"}],"nodeName":"ip-172-22-5-85.ec2.internal","restartPolicy":"Always","schedulerName":"default-scheduler","securityContext":{},"serviceAccount":"colinx","serviceAccountName":"colinx","terminationGracePeriodSeconds":43200},"status":{"message":"The node was low on resource: nodefs.","phase":"Failed","reason":"Evicted","startTime":"2018-08-30T19:23:57Z"}}

@dcowden thanks for sharing the logs.
Issue you reported which is error during connection attempt: dial tcp4 :0-><IP_ADDRESS>:6783: connect: connection timed out is basically noise in the logs which should not have any functional impact. Like you mentioned the PR in progress will fix this issue. But very unlikely this can be cause for node unresponsiveness.
Looking at the logs there are errors which are indicating nodes were low on resources.
For e.g
status":{"message":"The node was low on resource: nodefs.","phase":"Failed","reason":"Evicted","startTime":"2018-08-30T19:23:57Z"}}

"status":{"message":"Pod The  node was low on resource: [DiskPressure].","phase":"Failed","reason":"Evicted","startTime":"2018-09-11T17:05:14Z"}}

Are you sure there are no other errors/alerts in the cluster other than errors in the Weave pods?
Also is it possible that logs in the Weave pods were so noisy that nodes ran out of disk space?

@murali-reddy Yes, i think you're right. we've independently concluded that the root cause of this issue was disk pressure ( nodefs). I think that's the root issue of our outage.
That said, we're still a little concerned about the weave logs showing connecting to hosts that are old, even when they are not listed in ipam status.

That said, we're still a little concerned about the weave logs showing connecting to hosts that are old, even when they are not listed in ipam status.

@dcowden If you don't do rmpeer if would see these logs, but are you seeing that, there is attempt by weave to connect to the hosts that are deleted and were removed from weave peer list with rmpeer?
I can not observe this behaviour. Once a peer is removed with  rmpeer there is no attempt to connect to the deleted peer.

"attempt to connect" is totally separate from IPAM.  There is a weave forget command for the latter, distinct from weave rmpeer.
(yes, it's confusing)

@bboreham thanks. So it seems logical to do weave forget along with weave rmpeer in #3399?

Yes.

But isn't it the case that a) weave forget is a local operation, rather than cluster-wide, and b) we do not know the relationship between peer names and peer addresses?

a) #3399 runs everywhere; yes you have to do this outside of the only-run-once logic
b) that's a harder problem.  better to just replace the entire list, i.e. weave connect --replace

This symptoms reported in this issue are fixed in 2.5.0 release by  #3372, #3399. Please reopen if you still see the issue with 2.5.0 release.


Do a deep merge on bindings rather than a shallow

What are you trying to accomplish with this PR?
Make it possible to have multiple overlapping configurations that will be deep merged to form one sane configuration.
Eg. lets say you have following configurations:
common.yaml:
common:
  registry: private-thingy
...
app:
  port: 4200
  name: cat-service
  lb_id: nonprod
....

and then you have environment specific one:
production.yaml:
app:
  lb_id: prod

Currently we only merge top level entries with merge so eg. if lb_id was on top this would be fine but for more complex configurations people tend to separate things in to nested entries. Another example could be eg. setting resources but overriding limits in certain env, think of:
  resources:
    limits:
      cpu: "3"
      memory: "1Gi"
    requests:
      cpu: "3"
      memory: "1Gi"

and then in nonprod you wanna override the requests for example.
How is this accomplished?

Pull the bindings loop in to the parser
do a deep_merge! instead of merge!
profit

tl;dr s/merge/deep_merge but I thought its cleaner to pull the loop in to the parser too. Makes testing lot more easier and harder to screw up if doing changes in both deployer and renderer
What could go wrong?

Seriously though, if someone is relying on the wrong behaviour (shallow merge) this might cause a surprise, but technically doing so is wrong .. so :)

Rebase done

I was able to confirm successful 🎩  using the collection-with-erb fixtures with both kubernetes-render and kubernetes-deploy. We'll :shipit: once CI passes.


fixed error doc formatting

fixed error doc formatting

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (85dfad2) 56.31% compared to head (62859a6) 56.31%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3587   +/-   ##
=======================================
  Coverage   56.31%   56.31%
=======================================
  Files         100      100
  Lines       11952    11952
=======================================
  Hits         6731     6731
  Misses       5221     5221

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Flake installation not working

After installing from the repos flake, im getting a lot of warnings and errors.
nvs nodejs
warning: Use of deprecated "Deno.writeAllSync()" API. This API will be removed in Deno 2. Run again with DENO_VERBOSE_WARNINGS=1 to get more details.
⠋ fetchingwarning: Use of deprecated "Deno.customInspect" API. This API will be removed in Deno 2. Run again with DENO_VERBOSE_WARNINGS=1 to get more details.
√ finished fetch
? Which Package [type OR press enter OR use arrow keys] › warning: Use of deprecated "Deno.stdin.rid" API. This API will be removed in Deno 2. Run again with DENO_VERBOSE_WARNINGS=1 to get more details.                 : Event-driven I/O framework for the V8 JavaScript engine
warning: Use of deprecated "Deno.isatty()" API. This API will be removed in Deno 2. Run again with DENO_VERBOSE_WARNINGS=1 to get more details.
Failed getting version info from one of the sources (nixhub.io):I/O framework for the V8 JavaScript engine
    Error: Looks like www.nixhub.io has updated, meaning this CLI tool needs to be updated (issue finding list $("main ul"))
  nodejs-slim_latest                             : Event-driven I/O framework for the V8 JavaScript engine
error: Uncaught (in promise) TypeError: Cannot read properties of null (reading 'filter')JavaScript engine
      if (versions.filter((each2) => each2.version.startsWith(versionPrefix)).length == 0) {aScript engine
                   ^js-repl                      :
    at file:///nix/store/l462xk35gch0qkwmh75lif6xmk8dljzp-source/build_helper/main.bundle.js:212747:20
    at eventLoopTick (ext:core/01_core.js:63:7)

After some cleanup
warning: Use of deprecated "Deno.customInspect" API. This API will be removed in Deno 2. Run again with DENO_VERBOSE_WARNINGS=1 to get more details.
warning: Use of deprecated "Deno.stdin.rid" API. This API will be removed in Deno 2. Run again with DENO_VERBOSE_WARNINGS=1 to get more details.
warning: Use of deprecated "Deno.isatty()" API. This API will be removed in Deno 2. Run again with DENO_VERBOSE_WARNINGS=1 to get more details.
Failed getting version info from one of the sources (nixhub.io):I/O framework for the V8 JavaScript engine
   Error: Looks like www.nixhub.io has updated, meaning this CLI tool needs to be updated (issue finding list $("main ul"))
error: Uncaught (in promise) TypeError: Cannot read properties of null (reading 'filter')JavaScript engine
   if (versions.filter((each2) => each2.version.startsWith(versionPrefix)).length == 0) {aScript engine
                ^js-repl                      :
 at file:///nix/store/l462xk35gch0qkwmh75lif6xmk8dljzp-source/build_helper/main.bundle.js:212747:20
 at eventLoopTick (ext:core/01_core.js:63:7)

The deprecation warnings ill be happy to submit a pr to fix, but the exception itself and the update to the cli message i have no clue about.
Thanks for the cool tool regardless

Thanks for reporting! Looks like nix.io updated their site.
I published nvs v1.3.8 just now and it should go back to working as expected. Also I added a bit better protection so that these warnings dont completely block the other valid responses from other sources.
Let me know if you've still got an issue on your end


Present a proposal of the component file structure

This is a proposal of how we could structure the repository to separate individual components yet make the entire library easy to include.

Each component lives in ./component/{name}, where {name} is the  singular machine name we use for specific components. Bootstrap does not always appear to be consistent, e.g. _buttons.scss (plural), but button.js (singular).
Each component has a {name}.scss and {name}.js, so they can be reliably included anywhere and everywhere.
Each component is responsible for including or importing its own dependencies, such as Bootstrap code. An example of that can be seen in ./component/button/button.scss.
To include the entire library in one go, include ./component/cds.scss and ./component/cds.js.
The exact way we want to include Bootstrap probably needs tweaking, as including private files (leading underscore in the file name) is at our own risk. @pm1v21 pointed out Bootstrap documents recommended inclusion strategies on https://getbootstrap.com/docs/5.2/customize/sass/#importing.

Closing this in favor of https://github.com/nihruk/cds/pull/5


Create dependabot.yml

Keeps the used github actions up to date

I am not sure how this works with dependabot, given that both branches are maintained actively I added the file on both branches, not sure which one is checked, I think it is the best to add the file on both branches


Copy release images to redhat-isv on quay

This PR introduces an action that's invoked via workflow call.
It waits for build-release and build-multiarch to complete, and then copy all of those images to the redhat-isv organization in Quay.
This should push a little more than we want (e.g. rc, betas, etc), but we don't automatically use these images in pipelines. To use it in pipelines, we must submit a PR to the pipeline to point to the new images in redhat-isv. From that perspective, adding extra images to the org should cause no problems.
Signed-off-by: Jose R. Gonzalez<EMAIL_ADDRESS>

/hold cancel

Alright folks, here's the corresponding pipeline run that tests this PR in my fork:
https://github.com/komish/openshift-preflight/actions/runs/2246117575
The corresponding repositories are here
https://quay.io/repository/komish/preflight-test (destination)
https://quay.io/repository/komish/preflight (source)
PTAL

/lgtm


[$250] Split expense - Scan receipt does not show red brick road error details

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.67-2
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @shawnborton
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1714397696317219
Action Performed:

Open NewDot app
Click on Fab > Split expense
Scan a receipt with details missing and split
Open the receipt from the preview

Expected Result:
The error message on the preview says "Receipt missing details" but when you go to view the Split details, you don't know which details are actually missing. We should highlight under the specific inputs which details were missing, for example, if the Merchant name couldn't be found, let's highlight the Merchant row
Actual Result:
In the split details view, there is no indication of which fields need to be fixed.
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/38435837/4af32aeb-8837-4e8f-afaa-05b5dd9aceb6

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01395d5820a0885f64
Upwork Job ID:<PHONE_NUMBER>119090688
Last Price Increase: 2024-05-25

Issue OwnerCurrent Issue Owner: @shubham1206agra

Added to vip-split, and sending external to see if this can be worked on by contributors.

Proposal
Please re-state the problem that we are trying to solve in this issue.
In the split details view, there is no indication of which fields need to be fixed.
What is the root cause of that problem?
We pass the split draft transaction to MoneyRequestComfirmationList if it exists. If we edit any field before the scan is complete, we will create a split draft transaction in Onyx and the state of the scan will be ready. After the scan is complete, the receipt state is updated in the current transaction and it's not updated in split draft transaction.
https://github.com/Expensify/App/blob/8db67c4da2e5547abd08441503ca92fe06363d7f/src/pages/iou/SplitBillDetailsPage.tsx#L129
So the error field will not appear in confirm page because we use the draft transaction which has the scan state is ready.
https://github.com/Expensify/App/blob/8db67c4da2e5547abd08441503ca92fe06363d7f/src/components/MoneyRequestConfirmationList.tsx#L335
What changes do you think we should make in order to solve the problem?
In SplitBillDetailPage, we already pass hasSmartScanFailed to confirm page which check the current transaction. So we can do the same by creating hasMissingSmartscanFields variable on SplitBillDetailPage and passing hasMissingSmartscanFields it to confirm page
const hasMissingSmartscanFields = TransactionUtils.hasMissingSmartscanFields(transaction);

https://github.com/Expensify/App/blob/8db67c4da2e5547abd08441503ca92fe06363d7f/src/pages/iou/SplitBillDetailsPage.tsx#L77-L78
And then replace TransactionUtils.hasMissingSmartscanFields(transaction) check here with this prop
!!hasSmartScanFailed && hasMissingSmartscanFields

https://github.com/Expensify/App/blob/8db67c4da2e5547abd08441503ca92fe06363d7f/src/components/MoneyRequestConfirmationList.tsx#L335
What alternative solutions did you explore? (Optional)
NA

@ishpaul777 I can reproduce this bug by editing any field before the scan is complete. As the video below, I edited the category field before the scan is complete.
https://github.com/Expensify/App/assets/161821005/4d02f5e8-d202-47ab-99fe-107aa4278867

@shubham1206agra The problem is, we pass split draft transaction as transaction prop into MoneyRequestComfirmationList and the state of the scan in draftTransaction is ready that makes TransactionUtils.hasMissingSmartscanFields(transaction) returns false in MoneyRequestComfirmationList although the scan is complete. So we should check TransactionUtils.hasMissingSmartscanFields with the current transaction in SplitBillDetailsPage and pass it as a new prop to MoneyRequestComfirmationList

Update on this one @shubham1206agra?

Issue not reproducible during KI retests. (First week)

Asked #qa to check via https://expensify.slack.com/archives/C9YU7BX5M/p1717088516206259
Assigning a BZ buddy as I head OOO until June 11th.
@jliexpensify - if the test confirms we can't reproduce, we can close this, otherwise continue with the normal process

issue fixed.
https://github.com/Expensify/App/assets/43996225/c2f508ef-9e93-4cd7-9491-4672fbd2795b

Awesome thanks! Job removed, closing!


Fill translated values in ViewAction modal form

[x] Changes have been thoroughly tested to not break existing functionality.
[ ] New functionality has been documented or existing documentation has been updated to reflect changes.
[x] Visual changes are explained in the PR description using a screenshot/recording of before and after.

Before

After

Good catch there