Time.windows.com

The article states Allow access to all hosts via port 80 (HTTP), 443 (HTTPS), and 123 (UDP/NTP) I believe the only one that requires 123 is time.windows.com not all hosts.

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

ID: 1aafc065-6ee6-e3cf-31ba-ab3dd277fb23
Version Independent ID: 35d3102e-4ff7-9408-8dbd-513b7dfff5c0
Content: Windows Autopilot requirements
Content Source: windows/deployment/windows-autopilot/windows-autopilot-requirements.md
Product: w10
Technology: windows
GitHub Login: @greg-lindsay
Microsoft Alias: greglin

The http ports are used to determine if the client is online and able to access the Internet.  It does a test to verify that it can access www.msftconnecttest.com. See https://docs.microsoft.com/windows/privacy/manage-windows-1809-endpoints

I don’t disagree, but its not true that we need port 123 open for all the listed ports as the article says. We need 443/80 for everything and port 123 for a single URL.
Thanks
Robert
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Greg Lindsay<EMAIL_ADDRESS>Sent: Wednesday, October 9, 2019 2:43:23 PM
To: MicrosoftDocs/windows-itpro-docs<EMAIL_ADDRESS>Cc: Rkendall75<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/windows-itpro-docs] Time.windows.com (#5143)
The http ports are used to determine if the client is online and able to access the Internet. It does a test to verify that it can access www.msftconnecttest.comhttps://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.msftconnecttest.com&data=02|01||59db7158e6ca4d421fa308d74d01b5c9|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637062542044082521&sdata=4FMdLdrGe6YNd9%2Fa9udWcnx9DowasBZ%2FFDUGlml6l8I%3D&reserved=0. See https://docs.microsoft.com/windows/privacy/manage-windows-1809-endpointshttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fwindows%2Fprivacy%2Fmanage-windows-1809-endpoints&data=02|01||59db7158e6ca4d421fa308d74d01b5c9|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637062542044082521&sdata=rm755UVVOGPL31FhPibvUPyAdC4sHHHw%2BWrnrbRgSRA%3D&reserved=0
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fwindows-itpro-docs%2Fissues%2F5143%3Femail_source%3Dnotifications%26email_token%3DAJXJIXVNXH7EWYUBRS5DBT3QNZF7XA5CNFSM4I7EEBIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAZQGCI%23issuecomment-540214025&data=02|01||59db7158e6ca4d421fa308d74d01b5c9|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637062542044092526&sdata=zRGptqtfWClHuVB5uDh0Quh9j5XO86kLagAV7rw8Zt8%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJXJIXU45LSGWKGDEMINP6DQNZF7XANCNFSM4I7EEBIA&data=02|01||59db7158e6ca4d421fa308d74d01b5c9|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637062542044102535&sdata=%2BtX%2Buhyxl3%2BkSQiXksDLrk7sP7TX6TaEFYMLKhJcwHo%3D&reserved=0.

@greg-lindsay Would it be feasible to state in the document to limit allow access to 123 (UDP/NTP) only for a single domain (time.windows.com) as suggested? We would like to aid with relevant content updates if necessary. Thanks.

Maybe the proposed change is appropriate for Windows Autopilot and American or western countries with large enterprise deployments. To me, it looks slightly different, because I don't use Windows Autopilot and I also only manage a small business amount of computers. My specific case is for all the computers I manage, I quickly change time.windows.com to my local national (and trustworthy) NTP servers, like ntp.online.no in Oslo, Norway (and maybe no.pool.ntp.org). That makes it practical for me to allow more than 1 NTP server to pass the firewall (likely something like 5). In my own network, the NTP and SNTP ports are open for traffic in general, so any NTP server will work. On the other hand, allowing all addresses has caused some minor attack attempts to be reported in the firewall, from Chinese or Russian NTP servers.

The article states Allow access to all hosts via port 80 (HTTP), 443 (HTTPS), and 123 (UDP/NTP) I believe the only one that requires 123 is time.windows.com not all hosts.

I wonder if this is an indirect suggestion that the document phrasing seems to be too liberal. What @Rkendall75 also said, is that in his opinion, only one address is needed for the NTP port (UDP/NTP 123), but that seems to be too strict in my opinion. Since I don't have personal experience with Filtering or Firewall rules to allow only a small number of addresses, I don't have a useful suggestion for what would be a middle ground between those two opposite points. I also presume it is quite difficult to predict a reduced number of addresses to allow through the Firewall, even more so when it comes to determining what is a good solution for Windows Autopilot. Knowing that it is close to unpredictable which addresses (IP or DNS) will be preferred in environments beyond the United States, also taking into account that NTP server names might change over time, I don't know what could be a practical solution to implement for a change in the current document ("Your Mileage May Vary").

Exactly my comment was that the only host that needs 123 is whatever your time server is none of the other endpoints need that port opened.
Thanks
Robert
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Trond B<EMAIL_ADDRESS>Sent: Tuesday, June 9, 2020 10:14 AM
To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/windows-itpro-docs] Time.windows.com (#5143)
The article states Allow access to all hosts via port 80 (HTTP), 443 (HTTPS), and 123 (UDP/NTP) I believe the only one that requires 123 is time.windows.com not all hosts.
I wonder if this is an indirect suggestion that the document phrasing seems to be too liberal. What @Rkendall75https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FRkendall75&data=02|01||f52a8877876744b7e6f908d80c9884d7|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637273196479765435&sdata=XlRafX5WvctvXLPfuKam255U1JFFafgeXRgfrxORnPQ%3D&reserved=0 also said, is that in his opinion, only one address is needed for the NTP port (UDP/NTP 123), but that seems to be too strict in my opinion. Since I don't have personal experience with Filtering or Firewall rules to allow only a small number of addresses, I don't have a useful suggestion for what would be a middle ground between those two opposite points. I also presume it is quite difficult to predict a reduced number of addresses to allow through the Firewall, even more so when it comes to determining what is a good solution for Windows Autopilot. Knowing that it is close to unpredictable which addresses (IP or DNS) will be preferred in environments beyond the United States, also taking into account that NTP server names might change over time, I don't know what could be a practical solution to implement for a change in the current document ("Your Mileage May Vary").
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fwindows-itpro-docs%2Fissues%2F5143%23issuecomment-641455574&data=02|01||f52a8877876744b7e6f908d80c9884d7|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637273196479775430&sdata=0GQUcK0qnb19CLQtUo2JQgsdS3yX4rqNBxQwSf%2FN6u4%3D&reserved=0, or unsubscribehttps://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJXJIXVX2DMSR2TBP7PJA33RVZUV5ANCNFSM4I7EEBIA&data=02|01||f52a8877876744b7e6f908d80c9884d7|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637273196479785420&sdata=QlglnhKIvFKGBXqVFMImh0kuwN0eMe0nkZA5l7zfTzA%3D&reserved=0.

@e0i : Should we ask the document author for a final comment on this, whether it should be updated or not?

We haven't got feedback from Greg as commented above. The best way to get relevant feedback, in this case, is to come up with a PR with mentioned suggestions so I'm passing this to a contributor for that. Thank you for the discussion.

@Rkendall75 @illfated In my opinion this is addressed a bit further in the article:

In environments that have more restrictive Internet access, or for those that require authentication before internet access can be obtained, additional configuration may be required to allow access to the required services

The sentence you are referring to in the beginning of the article refers to a less restrictive environment (which also exists), and then it goes further to talk about what you need to do for more restrictive environments. If you find that this is not explicit enough, what wording would you see appropriate for the first sentence?

Allow access to all hosts via port 80 (HTTP), 443 (HTTPS), and 123 (UDP/NTP).

@VLG17 : Thank you for the practical feedback. Good & fair point.
I think the current phrasing/wording is OK as it is, based on your summary of what is actually already present in the document page. Giving access to only 1 NTP host (time.windows.com) on restricted networks, or access to all NTP hosts (UDP/123 completely open) on non-restricted networks. In my opinion, it is very difficult to find a middle ground between those two, because everyone and their mother has an opinion on how many and which NTP servers to allow.

@VLG17 Right to the point!. Thank you for providing this detail that is too easy to look over.


Intermittent failures of queue_unit_tests!?

I don't know how to see old runs of a GitHub Action for a PR but for #82 I had two failures of a database related test and IIRC it was queue_unit_tests. We should try to reproduce somehow... I had to manually re-run the workflow twice to get it working, so I know something was failing. It was just failing under the Linux job and not on OS X but I'm not sure that has any real bearing, could just be intermittent!?
On the other hand, if we can't reproduce, then not sure what to do. So give this a shot I guess or give up and close issue.

Ran this locally:
GOOD=0; TOT=0; for I in `seq 1000`; do TOT=$(($TOT+1)); ./queue_unit_tests && GOOD=$(($GOOD+1)); echo "Total: $TOT"; echo "Good: $GOOD"; done

and stopped it just now with this output
Total: 277
Good: 267

i.e. there have been 10 failures. So yes, this does seem to fail intermittently!

Here's a failed run:
BACKEND: Queue table 0 created
Test create_queue_table - OK (0)
BACKEND: Queue 0/0 created
Test create_queue - OK (0)
Test create_producer_thread - OK (0)
Test create_consumer_thread - OK (0)
BACKEND: Inserted queue entry 0 in queue 0/0, status=0
Test create_consumer_replay_thread - OK (0)
BACKEND: Subscriber 0/0/0 subscribed queue 0/0 with callback 0x7f4a0b62ce10
Test subscribe_queue - OK (0)
BACKEND: Subscriber 0 read 1 queue entries, new_read_head=0
CONSUMER 0: successful_dequeues=1, last_entry_id=0
BACKEND: Subscriber 0 consumed entries, new_consume_head=0, read_head=0
CONSUMER 0: successful_dequeues=1, successful_consumes=1
BACKEND: Subscriber 0/0/1 subscribed queue 0/0 with callback 0x7f4a0ae2be00
BACKEND: Subscriber 1 read 1 queue entries, new_read_head=0
CONSUMER 1: successful_dequeues=1, last_entry_id=0
BACKEND: Inserted queue entry 1 in queue 0/0, status=0
BACKEND: Attempting to notify local subscriber 0 (0x7f4a0b62ce10/0x7f4a0b62ce30/0x7f4a0b62ce60/0x55a5b417a530)
Consumer 0/0/0 received notification for queue 0/0, status 0
BACKEND: Notified local subscriber 0
BACKEND: Attempting to notify local subscriber 1 (0x7f4a0ae2be00/0x7f4a0ae2be20/0x7f4a0ae2be50/0x55a5b417a530)
Consumer 0/0/1 received notification for queue 0/0, status 0
BACKEND: Notified local subscriber 1
BACKEND: Subscriber 0 read 1 queue entries, new_read_head=1
BACKEND: Inserted queue entry 2 in queue 0/0, status=0
BACKEND: Attempting to notify local subscriber 0 (0x7f4a0b62ce10/0x7f4a0b62ce30/0x7f4a0b62ce60/0x55a5b417a530)
CONSUMER 0: successful_dequeues=2, last_entry_id=1
BACKEND: Subscriber 0 consumed entries, new_consume_head=1, read_head=1
CONSUMER 0: successful_dequeues=2, successful_consumes=2
BACKEND: Subscriber 1 read 1 queue entries, new_read_head=1
CONSUMER 1: successful_dequeues=2, last_entry_id=1
Consumer 0/0/0 received notification for queue 0/0, status 0
BACKEND: Notified local subscriber 0
BACKEND: Attempting to notify local subscriber 1 (0x7f4a0ae2be00/0x7f4a0ae2be20/0x7f4a0ae2be50/0x55a5b417a530)
Consumer 0/0/1 received notification for queue 0/0, status 0
BACKEND: Notified local subscriber 1
BACKEND: Subscriber 0 read 1 queue entries, new_read_head=2
CONSUMER 0: successful_dequeues=3, last_entry_id=2
BACKEND: Subscriber 0 consumed entries, new_consume_head=2, read_head=2
CONSUMER 0: successful_dequeues=3, successful_consumes=3
BACKEND: Inserted queue entry 3 in queue 0/0, status=0
BACKEND: Attempting to notify local subscriber 0 (0x7f4a0b62ce10/0x7f4a0b62ce30/0x7f4a0b62ce60/0x55a5b417a530)
Consumer 0/0/0 received notification for queue 0/0, status 0
BACKEND: Notified local subscriber 0
queue_unit_tests: queue.c:418: read_queue: Assertion `no_results == (*new_read_head - start_index + 1)' failed.
BACKEND: Subscriber 0 read 1 queue entries, new_read_head=3
CONSUMER 0: successful_dequeues=4, last_entry_id=3
BACKEND: Subscriber 0 consumed entries, new_consume_head=3, read_head=3
CONSUMER 0: successful_dequeues=4, successful_consumes=4
Aborted


Option to return fileStat info during listFiles

Goal of PR
Related to https://github.com/blockstack/gaia/issues/220, https://github.com/blockstack/gaia/issues/240
Provide ability to query file metadata (primarily lastModifiedDate) with the listFiles endpoint.
This may be needed by a future Collections historical file restoration tool -- pending discussion on historical naming scheme in https://github.com/blockstack/gaia/pull/248:

If a [gaiahub server] timestamp cannot be used [in the historical file name] then I have a couple alternative proposals that avoid bucket-wide index file race conditions and conflict resolution ... Use a random ID in this historical file name. Future file history restoration tooling could use the cloud driver provided lastModifiedDate that is now available in the fileStat operation. This field has integration testing showing accuracy and behavioral consistency across all currently supported cloud storage providers.

This feature does not cause additional request overhead with the current cloud providers -- their list file APIs already return this metadata alongside the filenames. The only additional overhead should be the additional data returned to clients that request it.
Implementation
Extends the existing POST ${hubUrl}/list-files/${address} endpoint.
If the POST body contains a stat: true field then the returned JSON includes the fileStat metadata:
{
  entries: [
    { name: string, lastModifiedDate: number, contentLength: number },
    { name: string, lastModifiedDate: number, contentLength: number },
    ...
  ]
  page: string // optional pagination marker
}

Without stat: true the previous behavior is preserved -- the returned JSON format remains:
{
  entries: string[], // file name strings
  page: string // optional pagination marker
}

Testing
Integration tests for all supported cloud providers -- all showing behavioral consistency.
Submission Checklist

[ ] Based on correct branch: feature submissions should be on develop, hotfixes should be on master

[ ] The code passes our eslint definitions, unit tests, and
contains correct TypeFlow annotations.

[ ] Submission contains tests that cover any and all new functionality or code changes.

[ ] Submission documents any new features or endpoints, and describes how developers
would be expected to interact with them.

[ ] Author has agreed to our contributor's agreement.

I'm in favor of this regardless of the eventual collections history naming scheme.

Agree with @jcnelson


[Task]: HTTP review

What needs to happen?
Following https://github.com/apache/hop/issues/3407#issuecomment-1816393414 , this task aims to collect all requirements around http transformers in order to make an actionable development.
@hansva , should http action be taken into account?
Issue Priority
Priority: 3
Issue Component
Component: Transforms

Please also take a look at https://github.com/apache/hop/issues/3440

If we can combine the code bases and create some shared classes between the action and the transforms then we could take it into account.


rewrite testing across clusters using fixtures

removes considerably more lines than added
rigorously tests accross all scheduler implementations: tests increase from 168 items to 231 items (not all are actually tested because there is no seperate CI for some)
move logic for paramaterized testing across multiple schedulers to two fixtures (one that runs locally and one that requires the CI environment): this allows adding new schedulers easily
add additional required disk argument for HTCondor to fixture using a temporary config default
test security on all clusters and add xfail for security on HTCondor and Slurm CI
modify the LocalCluster job_script to use a shebang line in order to behave equally to "real" schedulers (instead of "parsing" the jobscript and "emulating" a shell interpreter)

Please not that this conflicts and is not in sync with @lesteve's #353 . But it might be easier now since #521 was "fixed" .

IMHO this makes testing alot easier to read

@guillaumeeb , thanks for reviewing and catching some issues, I tried to incorporate them. I removed the changes to local.py and core.py as they are debatable and can go in a seperate PR . Hope no concerns are left. Added some docstrings to the fixtures.

Thanks once more @riedel !


Validation process for function call names and args before calling

While function calls seem to be correct so far under limited prompting, in more large-scale usage there will most certainly be some that are mangled (especially if a user opts to use gpt-3.5 instead of gpt-4). The validation should also contain a re-prompt when something looks wrong.

[x] Handle function names that don't match an allowed function
[ ] Handle function arg validation

Priority changed to low since, at least for OpenAI, function calls are now reliable. See https://openai.com/index/introducing-structured-outputs-in-the-api/


xt/check-signatures.t doesn't understand class $.variables

Given
my role X::Proc::Async is Exception {
    has Proc::Async $.proc;
}

in the source, and this in the docs:
=head2 method proc

    method proc(X::Proc::Async:D --> Proc::Async)

this fails:
➜  doc git:(main) ✗ RAKUDO_SRC=/Users/coke/sandbox/rakudo xt/check-signatures.rakutest doc/Type/X/Proc/Async.rakudoc
1..1
# Subtest: check X::Proc::Async methods
    1..1
    ok 1 - # SKIP X::Proc::Async.proc not found on X::Proc::Async
ok 1 - check X::Proc::Async methods

(OK, it SKIPs, but it should pass cleanly) - it doesn't realize that a getter is created for that class

Note - this is shown as a method in the source, but it's not a method. Perhaps the fix is to document it like https://docs.raku.org/type/IO/Handle#method_chomp


[Docs] Ruby bindings GitHub URL has changed

Moved from StuartApp/h3_ruby to seanhandley/h3_ruby

Coverage remained the same at 98.993% when pulling 47d3a445533b4eca1d72ada08d880e706b520c03 on seanhandley:patch-1 into 0d450072aac1b25d7b130150df923c3403ac7673 on uber:master.


Added polish translation

Added polish translation and references.

Thanks for your contribution. Unfortunately this PR has conflicts. Could you fix them? Also note that a "NE" reference should be added to the wind directions. (I need to add them to the other translations as well. It seems it is missing.


Remove quote before compare

testing the fix from https://github.com/dbt-labs/dbt-core/pull/4076 to see if it resolves https://github.com/dbt-labs/dbt-core/issues/4187

@ericf-firebolt we don't need this (for now) as we changed the view and table materialization to not use get_relation anymore.


chore: Update App.tsx with Firebase messaging integration and Redux store provider

Integrated Firebase Cloud Messaging (FCM) for push notifications.
Added Firebase configuration and initialization.
Set up message handling to display notifications within the app.
Integrated Redux store provider to manage global state.
Wrapped the App component with the Redux Provider.
Ensured Firebase messaging works seamlessly with Redux.
Updated dependencies to include Firebase and Redux libraries.

This update enhances the app's real-time notification capabilities and centralizes state management.

Please take pull before commit to the branch .


sort   fetch api  params  not  click  key

sort   fetch api  params  not  click  key

I don’t understand what you mean, can you describe it in detail


feature: use a non-patch approach to maintaining Tinkerbell actions

EKS Anywhere uses the upstream Tinkerbell writefile action to write various configuration files to disk during machine provisioning. We have developed a set of extensive patches to add new functionality and essentially changed writefile into a different action targeting EKS Anywhere clusters. Maintaining patches (totaling so far 8) has become cumbersome and makes understanding our default Tinkerbell templates unnecessarily difficult for both maintainers and the end user.
Given the action has taken on a new form, it would be useful to treat it as an entirely new action dedicated to EKS Anywhere needs that we maintain Go.

https://github.com/aws/eks-anywhere/issues/5292


Type hints for all public classes

Implement type hints with typing, at least for all public classes.

I wanted to type the complete library but the code under sosia/processing/ is way too complex.


Fast JIT call_indirect optimization

@chenyuyang2022 I added some comments in your last PR #1442

Thank you Wenyong,  I‘ll revise it.
From: Wenyong Huang @.>
Sent: Thursday, September 1, 2022 4:17 PM
To: bytecodealliance/wasm-micro-runtime @.>
Cc: Yang, Chenyu @.>; Mention @.>
Subject: Re: [bytecodealliance/wasm-micro-runtime] add elem_idx and func_idx exception checking in jit_compile_op_call_indtrect (PR #1443)
@chenyuyang2022https://github.com/chenyuyang2022 I added some comments in your last PR #1442https://github.com/bytecodealliance/wasm-micro-runtime/pull/1442
—
Reply to this email directly, view it on GitHubhttps://github.com/bytecodealliance/wasm-micro-runtime/pull/1443#issuecomment-1233916649, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A2H6LT3OYM2UHLYOH5QXRE3V4BQ6ZANCNFSM6AAAAAAQCCOWNM.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

@chenyuyang2022 I added some comments in your last PR #1442

Thank you Wenyong, I'll revise it in this PR.

https://github.com/bytecodealliance/wasm-micro-runtime/pull/1442#discussion_r960335912
@wenyongh I got an error after replacing this part with your code.
VOIDfast jit compilation failed: unknown error
WASM module load failed: fast jit compilation failed

@wenyongh @lum1n0us
我目前增加了三个block_import, block_nonimport和func_return三个BB，后续的结果处理等部分还没有写。方便的时候可以帮我看一下当前的部分存在哪些问题吗？谢谢~


Zero requests sent

How can I check that db1000n actually sends requests? "Traffic stats" shows that the number of requests sent is always zero but the number of requests attempted is higher than zero. I see the same results no matter how I run it - with or without VPN, from the command line or as a Docker container, from my laptop, or from a digitalocean instance.

Right now it seems like the targets are using some heavy geo blocking and I don't think we can do anything about it, admins are evaluating whether it's better to continue or change the target

Thank you for the quick answer


IPC-91: Test environment (Part 2)

Part of #91
Continuing down the README from where https://github.com/consensus-shipyard/ipc-agent/pull/157 left off.
New commands in this PR:

make topologies/<name>.sh to turn topologies/<name>.yaml into a runnable script
make setup/<name> to compile and run a topology script
make wallet creates a new wallet
make subnet creates a new subnet
make wallet/fund sends tokens to the wallet
make subnet/fund sends tokens to the subnet, executed on the parent node
make subnet/join makes the validator join the subnet , executed on the parent node

The only sane way to run these is e.g. make setup/simple.
Notes
It's not expected to start a validator before joining a subnet, yet it's done to simplify starting the containers with docker-compose. The validator will crash the first time it's started, but it's given a kick again in the post-up step, after joining; at that point it runs.

Useful tip from Will:
Address                                    Balance                      Nonce  Default
t1ah7phdlf5eg2nf25trxvvddzzde7w6ehtrfz2yi  1 FIL                        0
t1cp4q4lqsdhob23ysywffg2tvbmar5cshia4rweq  4998.998985909661230076 FIL  2      X

Here's an example log from setting up the simple topology: setup-log.txt
It actually fails at the end while setting up the sub-subnet with actor not found. I don't know why this error happens, but it's very frequent with the sub-subnet. cc @adlrocha

It's not expected to start a validator before joining a subnet, yet it's done to simplify starting the containers with docker-compose. The validator will crash the first time it's started, but it's given a kick again in the post-up step, after joining; at that point it runs.

We are improving this after this PR, and instead of crashing the validator polls to see if it can start mining on a subnet or not. https://github.com/consensus-shipyard/lotus/issues/166


refactor(demo): Faber creates invitation

It's better if Faber creates an invitation than Alice does because we can test mobile agents with Faber more easily.

Now, Faber creates an invitation and Alice receives it.
I didn't change the code but just exchanged connection-related code between Alice and Faber.
The second commit(1e6af7a) is a minor bug fix.

Codecov Report

Merging #995 (1e6af7a) into main (f90a27b) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 1e6af7a differs from pull request most recent head 9e6390e. Consider uploading reports for the commit 9e6390e to get more accurate results

@@           Coverage Diff           @@
##             main     #995   +/-   ##
=======================================
  Coverage   88.18%   88.18%
=======================================
  Files         488      488
  Lines       11552    11552
  Branches     1921     1921
=======================================
  Hits        10187    10187
  Misses       1305     1305
  Partials       60       60

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

However, do you think it will also be possible to modify the script so both sides can create and receive an invitation? Should be possible I think, and that way we don't have to remove the create invitation functionality from Alice

I'm not sure, but the functions like getConnectionRecord() will get complicated. Is it necessary for Alice has the invitation function?

If it's too complicated it's fine to just switch it around 👍


Improve Rich Logger

Why are the changes needed?
When executing flyekit pod task, we will have context in the container, and we don't want to use the rich logger to print them.
What changes were proposed in this pull request?
How was this patch tested?
from flytekit import task, workflow
from flytekit.loggers import logger
from flytekit import ImageSpec, Secret, task, workflow

@task(
    container_image= ImageSpec(
    python_version="3.9.13",
    packages=[
              "flyteidl==1.10.7b3",
              "git+https://github.com/flyteorg/flytekit.git@e52631f10d6362b80ddfb2eafc8e5f9c0d4c4d8d",
              ],
    apt_packages=["git"],
    registry="futureoutlier",
    env={"FLYTE_SDK_LOGGING_LEVEL": "20"},
)
)
def say_hello() -> str:
    logger.info("Hi, this is a test!")
    return "hello world"

if __name__ == "__main__":
    print(f"Running say_hello() {say_hello()}")

Setup process
Screenshots
Check all the applicable boxes

[ ] I updated the documentation accordingly.
[x] All new and existing tests passed.
[x] All commits are signed-off.

Related PRs

Docs link

@pingsutw I am not sure how to test it, my logs with failure scenario are still

@fg91 I've traced the git history and find that you have made this feature before, would you like to take a look?
Thank you!

Image built by this branch

Image built by default

have tried these 2 examples, still can't reproduce.
@task
def say_hello() -> None:
    raise Exception("This is a test exception")

from airflow.sensors.filesystem import FileSensor
from airflow.sensors.time_sensor import TimeSensor
from datetime import datetime, timedelta
from pytz import UTC

from flytekit import task, workflow

@task()
def t1():
    print("flyte")

@workflow
def wf_time_sensor():
    # sensor = FileSensor(task_id="id", filepath="/tmp/1234")
    sensor = TimeSensor(task_id="fire_immediately", target_time=(datetime.now(tz=UTC)+timedelta(seconds=1)).time())
    sensor >> t1()


Fix DAC issue convert summaries to use definition lists

What is the context of this PR?
This PR resolves a DAC issue with summaries that have multiple items per row. Screen readers have had trouble with row titles being read out correctly. So this change is to convert summaries to use definition lists instead of tables.
To get this to work and align correctly in all instances with flexbox, because theres no colspan alternative I have had to change the summary to go to the vertical view on the m breakpoint rather than the s one.
Also:

Updates the grouped example to show how rows with multiple items should be configured and fixes the formatting on one example.
Fixes bug where if there is a rowtitle and an errorMessage then only the errorMessage is shown
Fixes issue where values are slightly out of alignment with titles
Fixes a spacing issue where there is a rowtitle and a summaryTitle but no group title there was too much space between the two titles

How to review

Check grouped summary is read out correctly with a screenreader
Check that summaries still work correctly
Pass in  a rowtitle and an errorMessage and see that both are now displayed

 Should be using groups for summary of multiple answers to single question

So the recommendation is to use a definition list in the same way gov.uk do -> https://design-system.service.gov.uk/patterns/check-answers/
I don't think it would take much to convert this. I think if we were not going to prioritise this now the alternative would be to place text inside the problematic tr (What are your monthly household expenses?) and put that in a h4directly after the h3 (Spending). This way it sits outside of the table containing the items in the group.

Could you run a Percy check?

I don't think this part of the docs is relevant any longer


Missing controls in ioniq 5 in Europe

Recently installed the integration and cannot see the start climate or open charging door controls in HA.

These are in the developer menu under service.

That's one of my open questions too @cdnninja. Is the reason for this the programming effort to show these services here depending on the vehicle functions?

That's one of my open questions too @cdnninja. Is the reason for this the programming effort to show these services here depending on the vehicle functions?

I must have missed that.  Home assistant offers only select entities.   Many of those entities don't allow control.  Only ones with control are items like "lock". Remote start isn't one of them.   As such services are how we expose this.
You can add a button to the dashboard manually that calls the service but I don't know of a way to do it on my side.

There must be a way to archieve this somehow in HA. Look at the device defaults from Volvo V60 Recharge and Fiat 500e:

Thanks for posting! I will look at that code.
Switch entities are an option for sure. However I haven't seen anything that prompts for all the options start_climate needs.

Could I get more details on which integrations these are?  The native home assistant volvo one doesn't seem to have this atleast not easily seen in the code, documentation also makes no reference to it.
As for fiat https://github.com/wubbl0rz/FiatChamp isn't an integration but rather a add on.

@cdnninja you closed my post and tagged me here but I can't still find the answer. Why can I see all the controls of Kia Seltos 2023?

Have you looked in the developer services menu?

Sorry it's German but open the developer tools menu, go to 'services' and type 'hyundai'. You will see a list of all available services.

I do have it under services but the call service option is blacked and I can't call the service

Right now "heating" is required. I have seen it where home assistant knows this but doesn't bother to put it in even though off is selected.  Check the yaml to see if heating is so to 0 or not.   Call service button may still work even though grey.

@cdnninja is right. Just tried it and 'Call Service' was grey in my HA too but it works anyway. Heating in the car started.

It is still gray and I'm getting failed to call Kia climate unknown error

What do the logs say?

I see some issues: service "unlock" ist working, service "open_charge_port" not. The corresponding log entry is
2022-12-22 20:01:13.141 ERROR (SyncWorker_5) [hyundai_kia_connect_api.KiaUvoApiEU] Unknown API response format: {'error': 'Access to this API has been disallowed'}

We have an open issue for charge port as that is a brand new feature: https://github.com/Hyundai-Kia-Connect/kia_uvo/issues/243.  I think we are close on it but unfortunately I can't proceed without more detailed comparison.
For unlock I am not sure if typo but if not working can you open an issue for this?   As a reminder unlock typically relocks the car shortly after so please watch the car to confirm it didn't work.

Not that I am aware of.  Let me know if you see any data in the "Data" sensors attributes that you would like to see as a sensor but otherwise I will keep plugging away on other issues.   New issues are ideal for new items so I can track them.

I am fine @cdnninja. If you see any chance to get the services as "controls" as the thread starter mentioned that would be great but I assume there are a lot other relevant things to do.
Just tried to write a service button in the entities card that performs an action depending on the state but honestly I am not talented enough...
  - service: >
      {% if is_state('binary_sensor.ioniq_5_air_conditioner', 'off') %}
        kia_uvo.start_climate
      {% else %}
        kia_uvo.stop_climate
      {% endif %}
    data:
      device_id: 60843a78a5a7856d1c1dc8f14dc79d39

The only ones I would consider exposing as buttons within the integration are ones we can truly do justice to. start_climate requires settings which I don't know of a way to offer easily in the main screen.
Our key options for interaction are:
Button: https://developers.home-assistant.io/docs/core/entity/button
Select: https://developers.home-assistant.io/docs/core/entity/select
Number: https://developers.home-assistant.io/docs/core/entity/number (used for charge limits)
Cover: https://developers.home-assistant.io/docs/core/entity/cover
Lock: https://developers.home-assistant.io/docs/core/entity/lock
Lock and number already implemented.
Button not having the functionality for start_climate.  I could use it for force update or cached update, or potentially start/stop charge.
Cover making sense for open close of the charge port but I don't think that feature works yet.
Thoughts on what would be useful? I am also trying to be careful on how much we add to this integration as our list is getting long already and seems to grow by the month so want to make sure we don't bloat it too much.

Sorry for annoying questions but can you only use ONE key option per integration? Charge port may be a good idea but to be honest: if I want to plug/unplug the car I have to get to the car physically and can open it with the key or close it with the button in the charge port. Given that and considering that it only works with Ioniq 5 and EV6 I'd rather focus on stability. Start/stop charge has more potential to bring value (whereas I use the chargers API to to that).

I meant those are just the relevant types.  Any or all can be done just with time.

Happy New Year @cdnninja :-)
Based on your thoughts I would just go for these controls:
Button: deep refresh
Button: cache refresh (service does not seem to work on both of our Hyundai cars)
Is it possible to present button actions according to its state? E.g. have a button "Start charging" when the current state is "Stop charging" and vice versa?
And start climate would be pretty useful as a button with the given settings. I had a look at the plenty services settings the integration exposes. How is the native app handling this? In the app UI I do set and store all parameters. Then, to activate it there's just a single button. What would the service do when you just start climate without any further settings? Would it activate everything that's been set with the native app? Where are these settings saved? On their cloud infrastructure or locally in the app?

I don't think buttons can be state based, switches can though and are intended for state items.  As for storing parameters I think that is stored in app and not on server side.  Also could depend on region as this supports multiple APIs.

    await coordinator.async_start_charge(vehicle_id)
  File "/config/custom_components/kia_uvo/coordinator.py", line 212, in async_start_charge
    await self.hass.async_add_executor_job(
  File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/hyundai_kia_connect_api/VehicleManager.py", line 148, in start_charge
    return self.api.start_charge(self.token, self.get_vehicle(vehicle_id))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/hyundai_kia_connect_api/KiaUvoApiEU.py", line 848, in start_charge
    _check_response_for_errors(response)
  File "/usr/local/lib/python3.11/site-packages/hyundai_kia_connect_api/KiaUvoApiEU.py", line 113, in _check_response_for_errors
    raise error_code_mapping[response["resCode"]](response["resMsg"])
hyundai_kia_connect_api.exceptions.DeviceIDError: Invalid request body - Invalid deviceId. ```
 thats what i get on start charge

@rchiileea you are on latest version right?

Yea just re-downloaded to check

OK so more info on this, I have tried all the versions, errors still happening, if I delete the the intergration the first call service I try works (only been testing on lock and unlock so far) will test the charge when next plugged in.
What I have figured out is if I say call service to unlock the car it will unlock, if Ithen call service to lock the car I have to reload the integration to be able to call service to lock the car (its the same vise versa and I presume once plugged in to charge it will be the same again. for the call service to start and stop charge will need a reload of the integration in between.

Based on your error this is tracked separately and occurs when a push notification is sent. Logins are invalidated.  It's a new issue.

Based on your error this is tracked separately and occurs when a push notification is sent. Logins are invalidated. It's a new issue.

I known issue?

@cdnninja I think its more related to the api with uk anyway, when i load the app I have to refresh quite a bit and use my pin to get updated info from the car and thats with bluelink app.

Can these services be added to the regular integration options?

@mintgroen what do you mean?

The question is why are all of the possible actions already integrated as entity?
I've created a script to call the climate control service, from that you can add a button on a dashboard.
A little workaround, but it works.

Because every car is different and requires different parameters. I can't expose that as a button to do that.
One way that I saw in another integration is add remote start and settings for items like that to integration config.  Then use those for the for the car start button.  However that can't be car specific.

Somewhat irrelevant. EVs still have the same parameters needed like temperature, what to heat, steering, seats etc.


Timeout fetching data, most devices disabled

Version of the custom_component
ha-tplink-deco v0.0.1
running on a pi 4b with armv7
home assistant version: core-2022.2.0.dev20220118
Installation Type | Home Assistant Container
Python Version | 3.9.7
Timeout/nonetype issue logs
This error originated from a custom integration.

Logger: custom_components.tplink_deco
Source: helpers/update_coordinator.py:193
Integration: TP-Link Deco (documentation, issues)
First occurred: 8:11:05 AM (1 occurrences)
Last logged: 8:11:05 AM

Timeout fetching tplink_deco data

custom component logs
This error originated from a custom integration.

Logger: custom_components.tplink_deco
Source: custom_components/tplink_deco/coordinator.py:119
Integration: TP-Link Deco (documentation, issues)
First occurred: 8:11:25 AM (1 occurrences)
Last logged: 8:11:25 AM

Error calling on_close function <function async_dispatcher_connect.<locals>.async_remove_dispatcher at 0xa99e4ad8>: object NoneType can't be used in 'await' expression

Describe the bug
The integration on 0.0.1 will successfully install through hacs and looks like it successfully configures on the integrations page but then immediately after the success message, the list of devices on my deco will be pulled but almost all devices are disabled. I have 40 entities but only 14 devices because so many devices on my wifi have been found but are disabled, seemingly from this timeout. There are no other errors popping up except these. I'm interested in helping with the fix but I'm not sure where to start

Could you clarify, by disabled, do you mean unavailable or that mean "Enable Entity" is off)?

I think there are a couple of things going on here:

Since the log said "First occurred: 8:11:05 AM (1 occurrences)" sounds like it only happened once. If it's happening a lot then that's a problem, but once is fine.

The custom components logs looks like an actual bug, but that's unrelated to the timeouts and disabled entities. I'll send a fix for that, but should be unrelated as it only happens when integration is removed.

Thanks for taking a look. I don’t know if it’s happening multiple times but it seems like it doesn’t check again because all the disabled entities are disabled by the integration so I think the answer to your question is both. The weird thing is some devices are shown as available and active and some are totally unavailable but they are all listed as entities just the unavailable ones aren’t listed as devices, if that makes sense. I’m attaching a screenshot of another one’s history to show that some are working fine. The ones that show up properly are all tp link Kasa switches and plugs that I’ve already added through the Kasa integration, but this deco integration is still adding the info that I would expect based on the deco docs if that helps and makes sense

On Jan 20, 2022, at 12:50 PM, Amos Yuen @.***> wrote:

Could you clarify, by disabled, do you mean unavailable or that mean "Enable Entity" is off)?
I think there are a couple of things going on here:
Since the log said "First occurred: 8:11:05 AM (1 occurrences)" sounds like it only happened once. If it's happening a lot then that's a problem, but once is fine.
The custom components logs looks like an actual bug, but that's unrelated to the timeouts and disabled entities. I'll send a fix for that, but should be unrelated as it only happens when integration is removed.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.

It looks like the email upload didn’t work. I’m also adding a screenshot from my ha integrations page to show the difference between the and device’s counts

Hmm, that is quite strange, because there shouldn't be any devices, only entities. My code doesn't specify any device_info, so there should not be any associated devices.
My integration view:

I'm curious what the devices look like? Could you get a screenshot? Particularly interested in:

How are they named and does it look correct (e.g. Chris Laptop)?
What entities connected to the devices?

Let me take a look tonight and send some more screenshots. I guess it has the devices because it’s linking the TP-link Kasa devices with their entities from the deco integration but I have no clue how it’s linking, maybe just name? Also weird thing if it’s supposed to only be entities - it looks like only the devices have the deco attributes that the deco integration specifies is mac address

On Jan 20, 2022, at 3:52 PM, Amos Yuen @.***> wrote:

Hmm, that is quite strange, because there shouldn't be any devices, only entities. My code doesn't specify any device_info, so there should not be any associated devices.
My integration view:
I'm curious what the devices look like? Could you get a screenshot? Particularly interested in:
How are they named and does it look correct (e.g. Chris Laptop)?
What entities connected to the devices?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.

So I'm using the mac address as the entity unique ID, there's a good chance that the other Kasa integration is also doing that. In that case, HA is maybe merging them or something. I think the solution is for me to use a different unique ID.

Looks like that is the case at https://github.com/home-assistant/core/blob/f72bf2145b7e310f34f23ad34f8294d8fe1360ce/homeassistant/components/tplink/init.py#L243

That makes sense to me for how they’re merging but why would the entities be disabled for ones that don’t match the tplink Kasa integration? They should still be available but just not merged, right?

On Jan 20, 2022, at 4:32 PM, Amos Yuen @.***> wrote:

So I'm using the mac address as the entity unique ID, there's a good chance that the other Kasa integration is also doing that. In that case, HA is maybe merging them or something. I think the solution is for me to use a different unique ID.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.

I just manually enabled some of the “unavailable” entities and they look ok now. Ok as in they are displaying the attributes that your deco integration says should be picked up from the deco wifi. Did I miss something in the readme about manually enabling the entities for wifi clients I want to track? It seems like I just got mixed up with how to manage on the ui, and the code is all good. If this needs an update on readme I can write something out and add an image or two for future users  reference

Just to be clear I do not have an issue with the mac address id overlap causing devices to show up, because those actually were working immediately. The ones without Mac id overlap are the ones that were problematic but now knowing to manually enable those entities it seems like it’s all working fine. I can make a PR to automatically track the entities and/or update the readme to explain for new users if they encounter a similar issue

You shouldn't need to manually enable the entities, they should be enabled by default. Not really sure why they are disabled.
Could you confirm if the entities that were disabled are the non-merged ones?
Assuming it's not really a problem, I'll probably leave the unique_id alone then.

I have a similar problem  with all entries almost immediately   going unavailable

I'm not sure if it's related but all devices are unavailable and error in log
This error originated from a custom integration.

Logger: homeassistant
Source: custom_components/tplink_deco/coordinator.py:72
Integration: TP-Link Deco (documentation, issues)
First occurred: 5 February 2022, 15:23:02 (1 occurrences)
Last logged: 5 February 2022, 15:23:02

Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/config/custom_components/tplink_deco/__init__.py", line 130, in update_listener
    await async_reload_entry(hass, entry)
  File "/config/custom_components/tplink_deco/__init__.py", line 116, in async_reload_entry
    await async_setup_entry(hass, entry)
  File "/config/custom_components/tplink_deco/__init__.py", line 82, in async_setup_entry
    hass.data[DOMAIN][entry.entry_id] = await async_create_coordinator(hass, entry, api)
  File "/config/custom_components/tplink_deco/__init__.py", line 61, in async_create_coordinator
    coordinator = TplinkDecoDataUpdateCoordinator(
  File "/config/custom_components/tplink_deco/coordinator.py", line 72, in __init__
    update_interval=timedelta(seconds=scan_interval_seconds),
TypeError: unsupported type for timedelta seconds component: NoneType

That's unrelated, not sure how you got into that state, but looks like I need to make those values required in the config.

I've had trouble reproing, so I'm not enitrely sure, but I suspect that the initial query is failing and so the integration is loaded in a failed state, which might cause all the entities to be added as unavailable.
In https://github.com/amosyuen/ha-tplink-deco/releases/tag/v1.0.1 I've added a retry for expired auth and timeouts which should help mitigate this.

I wonder if there is some issue just on the 32bit pi. That’s where I initially saw this issue and had to go and manually enable devices/entities. I will try on a higher power server that runs x86_64 and see if that has the same issue. I know there were docker containers that failed on the 32 bit pi. I’ll post an update when I’ve tried on my 64bit intel

On Feb 14, 2022, at 4:12 AM, Amos Yuen @.***> wrote:

I've had trouble reproing, so I'm not enitrely sure, but I suspect that the initial query is failing and so the integration is loaded in a failed state, which might cause all the entities to be added as unavailable.
In https://github.com/amosyuen/ha-tplink-deco/releases/tag/v1.0.1 I've added a retry for expired auth and timeouts which should help mitigate this.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.

Closing the issue as haven't received further reports


Godot crashes when minimizing a subwindow

Tested versions
Reproducible in 4.3-dev3 and dev4
System information
Godot v4.3.dev4 - Windows 10.0.19045 - GLES3 (Compatibility) - Intel(R) HD Graphics 4600 (Intel Corporation; <IP_ADDRESS>26) - Intel(R) Core(TM) i3-4330 CPU @ 3.50GHz (4 Threads)
Issue description
Basically I opened the script editor in a subwindow, tried to minimize it, and Godot crashed. Later on I checked if this also happens in normal projects and yes, it does.
Here's a short video:
https://github.com/godotengine/godot/assets/136469511/f790186c-0758-4514-8296-9c9d8843bbea
Steps to reproduce

Add a Window node to your scene.
Make sure to disable this setting display/window/subwindows/embed_subwindows.
Minimize it.

-- Or within Godot --

Go to script editor.
Make it floating.
Minimize it.

Minimal reproduction project (MRP)
N/A.

Can you please try with dev5?

Yes, it still happens in dev5.

I don't have this problem.
Checked in 4.3 dev 4 - dev 5
Godot v4.3.dev5 - Windows 10.0.19045 - GLES3 (Compatibility) - Radeon RX 560 Series (Advanced Micro Devices, Inc.; 31.0.14001.45012) - Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz (4 Threads)

Can't reproduce it on Windows 11 (NVIDIA GPU), neither in GLES/Compatibility nor it Vulkan/Forward+.


build tf v2.5.0 falied

According to your method, I compiled tensorflow_aarch64 on tf2.5, but it reported an error:
ERROR: /root/tensorflow/tensorflow/python/BUILD:2531:29: Linking of rule '//tensorflow/python:gen_candidate_sampling_ops_py_wrappers_cc' failed (Exit 1): gcc failed: error executing command /usr/bin/gcc @bazel-out/host/bin/tensorflow/python/gen_candidate_sampling_ops_py_wrappers_cc-2.params bazel-out/host/bin/_solib_aarch64/_U_S_Stensorflow_Spython_Cgen_Ucandidate_Usampling_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so.2: error: undefined reference to 'std::allocator<absl::lts_2020_09_23::string_view>::allocator()' collect2: error: ld returned 1 exit status Target //tensorflow/tools/pip_package:build_pip_package failed to build
build command
BAZEL_LINKLIBS=-l%:libstdc++.a bazel build --config=noaws --config=nogcp --config=nohdfs --config=nonccl --jobs=64 //tensorflow/tools/pip_package:build_pip_package
But I built whl success at tf v2.4.1， And There is tf2.5.x version in the whl package you provided, is this a bug of 2.5.0?

I build v2.4.1 success , but build v2.5.0/v2.5.1/v2.5.2/v2.5.3 failed, I feel so confused  =.=

Hi!
I also failed to build v2.5 about a year ago, and I think it might be a bug of this version...

Hi!
I also failed to build v2.5 about a year ago, and I think it might be a bug of this version...

But I saw that you have provided the whl of v2.5.x, and I am curious about how this is generated. After downloading, I can pip install it on my personal arm machine

you have provided the whl of v2.5.x

That's just a placeholder...
A year ago linaro did release 2.5.x wheels but they are now removed from their server and I didn't backup them. I also have no idea how they did that, since there are no instructions shared by them.
But I just found a repo PINTO0309/Tensorflow-bin, which listed building commands for every version. You may give it a try.

You may give it a try.

Thank you for your reply,I will try it now!


Screen Sharing via Jitsi no longer works on 2.17.2 (latest)

My Setup

Operating System: Windows 10 Pro
App Version: 2.17.2
Installation type: exe

[x] I have tested with the latest version
[x] I can simulate the issue easily

Description

Current Behavior
When starting screen sharing popup window keeps loading and never gives option to select whole screen or , app windows. Problem exists since version 2.16.2 .
Expected Behavior
Screen sharing should start and work normally.

I confirm that bug.
Screen Sharing is broken.

I have tested Screen Sharing on version 2.16.0 and have the same bug.
Checked version 2.15.5 and it works fine.

we have the same issue on 2.17.0 and 2.16. clients on Windows and Ubuntu. Jitsi Video/Audio works but screen sharing stuck on loading. Please fix this.

Rocket.Chat Electron version 2.17.1 didn't fix that issue, please fix it.

Same problem on MacOs Catalina with Rocket.Chat Electron version 2.17.1.

updated my thread for the issue , it persists through latest 2.17.1 version.

Same problem on 2.17.2

Just another having the same issue vote.

Stuck on 2.15.5 because I need to use it :(

Stuck on 2.15.5 because I need to use it :(

Same for me.

Also stuck on 2.15.5...

Works like a charm now ! Thanks !

Having exactly this issue with freshly installed 2.17.7


Angular getstorybook broken

Issue details
Added storybook to a fresh angular project and it needs extra steps to install.
Steps to reproduce
Here's what I expected to work:
ng new angular-test
cd angular-test/
yarn add @storybook/cli --dev
yarn run getstorybook
yarn run storybook

Here are the additional steps I had to take to get the example working:
yarn add @storybook/addon-notes --dev
yarn add @types/lodash-es --dev
yarn storybook

Please specify which version of Storybook and optionally any affected addons that you're running

@storybook/cli 3.3.0

Affected platforms

This appears to be a problem with the CLI for angular

So is it fixed?


chore(deps): prebuild for electron 13

Adds prebuild for electron 13 and fixes
In file included from ../../nan/nan.h:2884:
../../nan/nan_typedarray_contents.h:34:43: error: no member named 'GetContents' in 'v8::ArrayBuffer'
      data   = static_cast<char*>(buffer->GetContents().Data()) + byte_offset;
                                  ~~~~~~  ^
1 error generated.
make: *** [Release/obj.target/sourceId2Coordinates/node_addons/sourceId2Coordinates/src/index.o] Error 1

@saghul I successfully tested this, please approve if you agree to the approach.

Thank you!

@saghul Would it also be possible to cut a release, then I can update jitsi-meet-electron to electron 13 (chrome 89 -> 91, pipewire fixes)

@horymury Mind doing one please Horatiu?

@saghul @csett86   it is in progress.

@saghul @csett86 it is in progress.

it's done.


chore: jxpy to 0.0.30

chore: Promote jxpy to version 0.0.30

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign
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.

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


Fix broken descriptions.

I broke stuff with my last change, this fixes that...
Broken description:
wrapped: ; ; ; :
      ...
        wrapped: :

Fixed:
wrapped: (with other funk):
      ...
        wrapped: (with inner wrapper):

@ljharb Updated.


scripts throw 'expected binary operator'

@riconeitzel what host environment do you have? I have never seen this error

OS X El Capitan, using ZSH
Best, Rico

On 08 Jun 2016, at 17:37, Alexander Paliarush<EMAIL_ADDRESS>wrote:
@riconeitzel what host environment do you have? I have never seen this error
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Ok, thanks, never tried that though. Everything worked fine in the native El Capitan terminal and PhpStorm terminal


LAE identifiers

How do we want to migrate the LAE identifiers?

Put them in a local_identifier field so we can map them to the old IDs?
Use them as the primary identifiers instead of minting new NOIDs?  Since they are 5 characters, they won't conflict with Plum's identifiers.
Something else?

Use them as the primary identifiers instead of minting new NOIDs? Since they are 5 characters, they won't conflict with Plum's identifiers.

I like this one, if it's not going to cause a hassle at a later date for some reason.


HADOOP-19153. hadoop-common exports logback as a dependency

Critical: remove the obsolete exclusion list from hadoop-common.
Diligence: expand the hadoop-project exclusion list to exclude all ch.qos.logback artifacts

How was this patch tested?

Manual inspection of the pom as installed in local maven repo
hadoop-release-support maven verified that logback wasn't coming in transitively

For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

targeting 3.4 for this pr; to cherrypick into 3.4.1 and trunk once approved. I was working on this branch so as not to contaminate my maven repo with local -3.4.1 artifacts

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
17m  6s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-3.4 Compile Tests _

+0 :ok:
mvndep
4m 14s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
46m  0s

branch-3.4 passed

+1 :green_heart:
compile
21m  1s

branch-3.4 passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
compile
17m 17s

branch-3.4 passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
mvnsite
2m 14s

branch-3.4 passed

+1 :green_heart:
javadoc
1m 47s

branch-3.4 passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javadoc
1m 23s

branch-3.4 passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
shadedclient
132m 33s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 32s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m  8s

the patch passed

+1 :green_heart:
compile
18m  7s

the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javac
18m  7s

the patch passed

+1 :green_heart:
compile
17m  4s

the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
javac
17m  4s

the patch passed

+1 :green_heart:
blanks
0m  1s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
2m 11s

the patch passed

+1 :green_heart:
javadoc
1m 41s

the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javadoc
1m 22s

the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
shadedclient
45m 57s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
0m 32s

hadoop-project in the patch passed.

+1 :green_heart:
unit
19m 14s

hadoop-common in the patch passed.

+1 :green_heart:
asflicense
0m 59s

The patch does not generate ASF License warnings.

255m 16s

Subsystem
Report/Notes

Docker
ClientAPI=1.44 ServerAPI=1.44 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6999/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6999

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell detsecrets xmllint

uname
Linux 50df8958460a 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.4 / a32f8b1c3062b33ada0f37365803523285b360af

Default Java
Private Build-1.8.0_422-8u422-b05-1~20.04-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_422-8u422-b05-1~20.04-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6999/1/testReport/

Max. process+thread count
1263 (vs. ulimit of 5500)

modules
C: hadoop-project hadoop-common-project/hadoop-common U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6999/1/console

versions
git=2.25.1 maven=3.6.3

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.


Warning about unsupported caller_location intrinsic

Kani almost always emits the following annoying warning on any program:
warning: Found the following unsupported constructs:
             - caller_location (1)

         Verification will fail if one or more of these constructs is reachable.
         See https://model-checking.github.io/kani/rust-feature-support.html for more details.

warning: 1 warning emitted

for example, on this tiny program:

#[kani::proof]
fn main() {
    let _x: bool = kani::any();
}

using the following command line invocation:
kani test.rs

with Kani version: f4796eacbdae07a4cbd305bebabbc2364f8bddd9
It's not clear what the source of this intrinsic is, so it might be worth investigating if this is coming from codegen itself.

This still occurs on programs involving panic!, e.g:
#[kani::proof]
fn main() {
    panic!("Some message");
}

$ kani simp_panic.rs
warning: Found the following unsupported constructs:
             - caller_location (1)

         Verification will fail if one or more of these constructs is reachable.
         See https://model-checking.github.io/kani/rust-feature-support.html for more details.

warning: 1 warning emitted

Checking harness main...
...

Reopening.


Unit testing regression metrics

to - @mail4umar @VerticaDataScientist
cc - @oualib
Please review it. I have put comments in testcases for mismatches and clarifications.

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

@mail4umar can you please check carefully this PR? It seems @vikash018 is modifying some of your plotting files.

@vikash018 please always add the right label to the PR.


[App] Add lightning zip command

What does this PR do?

Adds command to download content from the Lightning Filesystem as a zip file.

➜ lightning pwd
/default-project

➜ lightning ls
wide-tan-ryq8

➜ lightning zip wide-tan-ryq8
Downloaded to ./wide-tan-ryq8.zip

➜ unzip -l ./wide-tan-ryq8.zip
Archive:  ./wide-tan-ryq8.zip
  Length      Date    Time    Name
---------  ---------- -----   ----
        0  02-17-2023 11:34   code/.lightning-app-sync
       41  02-17-2023 11:34   code/app.py
---------                     -------
       41                     2 files

Fixes bug in cp._sanitize_path
Refactors token client

Before submitting

Was this discussed/agreed via a GitHub issue? (not for typos and docs)
[ ] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure your PR does only one thing, instead of bundling different changes together?
Did you make sure to update the documentation with your changes? (if necessary)
Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
Did you list all the breaking changes introduced by this pull request?
Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

Reviewer checklist

[ ] Is this pull request ready for review? (if not, please submit in draft mode)
[ ] Check that all items from Before submitting are resolved
[ ] Make sure the title is self-explanatory and the description concisely explains the PR
[ ] Add labels and milestones (and optionally projects) to the PR so it can be classified

@luca3rd This is kinda of a confusion API.
Won't it be better to have lightning cp r:. . --zip, so we don't introduce a new command ?
Best,
T.C


Fix keyframe pasting to respect interpolation graph

Demo
Before the fix:

the curve is slightly horizontally offset from the keyframes

the green y curve is copied from x, but does not match x's curve

the curve does not properly display default values when the keyframe has a type that does not match the track (not pictured)

after the fix:

the curve is correctly aligned with the keyframes

the green y is copied from x, and does match x

the curve correctly shows default values (not pictured)

Note

also adds 'copy keyframe' to a single keyframe's context menu. Missed this on the first pass.

The ! makes this function's type signature unreliable.


Configure Atlantis

https://www.runatlantis.io/docs/atlantis-yaml-reference.html

atlantis plan

Ran Plan in dir: . workspace: default
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

data.aws_availability_zones.all: Refreshing state...
data.aws_ami.ubuntu: Refreshing state...

------------------------------------------------------------------------

An execution plan has been generated and is shown below.

To discard this plan click here.

atlantis apply

Ran Apply in dir: . workspace: default
Apply Failed: Pull request must be approved before running apply.

/atlantis apply

/atlantis apply

atlantis apply

Ran Apply in dir: . workspace: default
Apply Failed: Pull request must be approved before running apply.

atlantis apply

Ran Apply in dir: . workspace: default
Apply Error
no plan found at path "." and workspace "default"–did you run plan?

atlantis plan

Ran Plan in dir: . workspace: default
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

data.aws_availability_zones.all: Refreshing state...
data.aws_ami.ubuntu: Refreshing state...

------------------------------------------------------------------------

An execution plan has been generated and is shown below.

To discard this plan click here.

atlantis apply

Ran Apply in dir: . workspace: default
Apply Error
exit status 1: running "sh -c terraform apply -no-color /root/.atlantis/repos/CMeza99/terraform-up-and-running/3/default/terraform-up-and-running-default.tfplan" in "/root/.atlantis/repos/CMeza99/terraform-up-and-running/3/default":
aws_security_group.example: Creating...
  arn:                                  "" => "<computed>"
  description:                          "" => "Managed by Terraform"
  egress.#:                             "" => "<computed>"
  ingress.#:                            "" => "1"
  ingress.516175195.cidr_blocks.#:      "" => "1"
  ingress.516175195.cidr_blocks.0:      "" => "<IP_ADDRESS>/0"
  ingress.516175195.description:        "" => ""
  ingress.516175195.from_port:          "" => "8080"
  ingress.516175195.ipv6_cidr_blocks.#: "" => "0"
  ingress.516175195.protocol:           "" => "tcp"
  ingress.516175195.security_groups.#:  "" => "0"
  ingress.516175195.self:               "" => "false"
  ingress.516175195.to_port:            "" => "8080"
  name:                                 "" => "terraform-example-instance"
  owner_id:                             "" => "<computed>"
  revoke_rules_on_delete:               "" => "false"
  vpc_id:                               "" => "<computed>"
aws_security_group.elb: Creating...
  arn:                                   "" => "<computed>"
  description:                           "" => "Managed by Terraform"
  egress.#:                              "" => "1"
  egress.482069346.cidr_blocks.#:        "" => "1"
  egress.482069346.cidr_blocks.0:        "" => "<IP_ADDRESS>/0"
  egress.482069346.description:          "" => ""
  egress.482069346.from_port:            "" => "0"
  egress.482069346.ipv6_cidr_blocks.#:   "" => "0"
  egress.482069346.prefix_list_ids.#:    "" => "0"
  egress.482069346.protocol:             "" => "-1"
  egress.482069346.security_groups.#:    "" => "0"
  egress.482069346.self:                 "" => "false"
  egress.482069346.to_port:              "" => "0"
  ingress.#:                             "" => "1"
  ingress.2214680975.cidr_blocks.#:      "" => "1"
  ingress.2214680975.cidr_blocks.0:      "" => "<IP_ADDRESS>/0"
  ingress.2214680975.description:        "" => ""
  ingress.2214680975.from_port:          "" => "80"
  ingress.2214680975.ipv6_cidr_blocks.#: "" => "0"
  ingress.2214680975.protocol:           "" => "tcp"
  ingress.2214680975.security_groups.#:  "" => "0"
  ingress.2214680975.self:               "" => "false"
  ingress.2214680975.to_port:            "" => "80"
  name:                                  "" => "terraform-example-elb"
  owner_id:                              "" => "<computed>"
  revoke_rules_on_delete:                "" => "false"
  vpc_id:                                "" => "<computed>"

Error: Error applying plan:

2 error(s) occurred:

* aws_security_group.elb: 1 error(s) occurred:

* aws_security_group.elb: Error creating Security Group: InvalidGroup.Duplicate: The security group 'terraform-example-elb' already exists for VPC 'vpc-6632df0f'
	status code: 400, request id: c701a8a7-0b7a-484c-bf0d-16aaf02036ca
* aws_security_group.example: 1 error(s) occurred:

* aws_security_group.example: Error creating Security Group: InvalidGroup.Duplicate: The security group 'terraform-example-instance' already exists for VPC 'vpc-6632df0f'
	status code: 400, request id: eaefc08e-23db-4f14-ba1e-0ff0fce10f24

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

aws_security_group.example: Creating...
  arn:                                  "" => "<computed>"
  description:                          "" => "Managed by Terraform"
  egress.#:                             "" => "<computed>"
  ingress.#:                            "" => "1"
  ingress.516175195.cidr_blocks.#:      "" => "1"
  ingress.516175195.cidr_blocks.0:      "" => "<IP_ADDRESS>/0"
  ingress.516175195.description:        "" => ""
  ingress.516175195.from_port:          "" => "8080"
  ingress.516175195.ipv6_cidr_blocks.#: "" => "0"
  ingress.516175195.protocol:           "" => "tcp"
  ingress.516175195.security_groups.#:  "" => "0"
  ingress.516175195.self:               "" => "false"
  ingress.516175195.to_port:            "" => "8080"
  name:                                 "" => "terraform-example-instance"
  owner_id:                             "" => "<computed>"
  revoke_rules_on_delete:               "" => "false"
  vpc_id:                               "" => "<computed>"
aws_security_group.elb: Creating...
  arn:                                   "" => "<computed>"
  description:                           "" => "Managed by Terraform"
  egress.#:                              "" => "1"
  egress.482069346.cidr_blocks.#:        "" => "1"
  egress.482069346.cidr_blocks.0:        "" => "<IP_ADDRESS>/0"
  egress.482069346.description:          "" => ""
  egress.482069346.from_port:            "" => "0"
  egress.482069346.ipv6_cidr_blocks.#:   "" => "0"
  egress.482069346.prefix_list_ids.#:    "" => "0"
  egress.482069346.protocol:             "" => "-1"
  egress.482069346.security_groups.#:    "" => "0"
  egress.482069346.self:                 "" => "false"
  egress.482069346.to_port:              "" => "0"
  ingress.#:                             "" => "1"
  ingress.2214680975.cidr_blocks.#:      "" => "1"
  ingress.2214680975.cidr_blocks.0:      "" => "<IP_ADDRESS>/0"
  ingress.2214680975.description:        "" => ""
  ingress.2214680975.from_port:          "" => "80"
  ingress.2214680975.ipv6_cidr_blocks.#: "" => "0"
  ingress.2214680975.protocol:           "" => "tcp"
  ingress.2214680975.security_groups.#:  "" => "0"
  ingress.2214680975.self:               "" => "false"
  ingress.2214680975.to_port:            "" => "80"
  name:                                  "" => "terraform-example-elb"
  owner_id:                              "" => "<computed>"
  revoke_rules_on_delete:                "" => "false"
  vpc_id:                                "" => "<computed>"

Error: Error applying plan:

2 error(s) occurred:

* aws_security_group.elb: 1 error(s) occurred:

* aws_security_group.elb: Error creating Security Group: InvalidGroup.Duplicate: The security group 'terraform-example-elb' already exists for VPC 'vpc-6632df0f'
	status code: 400, request id: c701a8a7-0b7a-484c-bf0d-16aaf02036ca
* aws_security_group.example: 1 error(s) occurred:

* aws_security_group.example: Error creating Security Group: InvalidGroup.Duplicate: The security group 'terraform-example-instance' already exists for VPC 'vpc-6632df0f'
	status code: 400, request id: eaefc08e-23db-4f14-ba1e-0ff0fce10f24

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

Locks and plans deleted for the projects and workspaces modified in this pull request:

dir: . workspace: default


Stuck loading forever

Describe the bug
I think since a few days ago the app is broken and stuck loading the channels like it is shown in the screenshot.
To Reproduce
Steps to reproduce the behavior:

Open the app

Expected behavior
Live twitch channels are shown
Screenshots

Desktop (please complete the following information):

OS: Windows 10
Browser: Google Chrome
Version 102.0.5005.63
App Version 1.11.0

Additional context
When opening the chrome inspector for the app the error states:
popup.js:25 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'enabled')
    at y.yk [as constructor] (popup.js:25:41860)
    at y.V [as render] (popup.js:2:24064)
    at P (popup.js:2:21591)
    at popup.js:2:17544
    at Array.some (<anonymous>)
    at x (popup.js:2:17441)

Opening the related JS file and "pretifying" the Code it states this error:

Like I already answered this same question on Chrome Web Store, I may have messed up with the data migration with the last version. I have a couple of fixes ready for shipping but I'll have to wait until Chrome Web Store allows me to do so.

In the meantime, one of the options is to reset the extension and everything should be fixed.
However, due to an error with one of the migrations, the badge icon gets disabled and you'll have to manually enable it in the settings.

Sorry, didn't see the question in the Chrome Web Store. Indeed uninstallting and re-installing fixed the issue 👍🏻

I totally understand you. External dependencies which don't respond accordingly are pretty frustrating...


sh sample/t2v.sh  error,

sh sample/t2v.sh
Using model!
Traceback (most recent call last):
File "/data/zhangmaolin/code/Latte/sample/sample_t2v.py", line 160, in
main(OmegaConf.load(args.config))
File "/data/zhangmaolin/code/Latte/sample/sample_t2v.py", line 34, in main
vae = AutoencoderKL.from_pretrained(args.pretrained_model_path, subfolder="vae", torch_dtype=torch.float16).to(device)
File "/home/user/anaconda3/envs/py39/lib/python3.9/site-packages/diffusers/models/modeling_utils.py", line 812, in from_pretrained
unexpected_keys = load_model_dict_into_meta(
File "/home/user/anaconda3/envs/py39/lib/python3.9/site-packages/diffusers/models/modeling_utils.py", line 155, in load_model_dict_into_meta
raise ValueError(
ValueError: Cannot load /data/zhangmaolin/code/Lattle_file/Latte/t2v_required_models because decoder.conv_in.bias expected shape tensor(..., device='meta', size=(64,)), but got torch.Size([512]). If you want to instead overwrite randomly initialized weights, please make sure to pass both low_cpu_mem_usage=False and ignore_mismatched_sizes=True. For more information, see also: https://github.com/huggingface/diffusers/issues/1619#issuecomment-1345604389 as an example.
您好，能帮忙看下这个问题怎么解决吗，我跑t2v.sh的时候报错，期待您的回复

sh sample/t2v.sh Using model! Traceback (most recent call last): File "/data/zhangmaolin/code/Latte/sample/sample_t2v.py", line 160, in main(OmegaConf.load(args.config)) File "/data/zhangmaolin/code/Latte/sample/sample_t2v.py", line 34, in main vae = AutoencoderKL.from_pretrained(args.pretrained_model_path, subfolder="vae", torch_dtype=torch.float16).to(device) File "/home/user/anaconda3/envs/py39/lib/python3.9/site-packages/diffusers/models/modeling_utils.py", line 812, in from_pretrained unexpected_keys = load_model_dict_into_meta( File "/home/user/anaconda3/envs/py39/lib/python3.9/site-packages/diffusers/models/modeling_utils.py", line 155, in load_model_dict_into_meta raise ValueError( ValueError: Cannot load /data/zhangmaolin/code/Lattle_file/Latte/t2v_required_models because decoder.conv_in.bias expected shape tensor(..., device='meta', size=(64,)), but got torch.Size([512]). If you want to instead overwrite randomly initialized weights, please make sure to pass both low_cpu_mem_usage=False and ignore_mismatched_sizes=True. For more information, see also: huggingface/diffusers#1619 (comment) as an example.
您好，能帮忙看下这个问题怎么解决吗，我跑t2v.sh的时候报错，期待您的回复

Hi, thank you for your issue. I found that some files in t2v_required_models are named incorrectly. I have modified it correctly and you can rename your downloaded file according to my modified file name.

我更新了您的代码，问题依然存在，似乎是加载的模型和模型构建代码里面尺寸不匹配
Traceback (most recent call last):
File "/data/zhangmaolin/code/Latte/sample/sample_t2v.py", line 160, in
main(OmegaConf.load(args.config))
File "/data/zhangmaolin/code/Latte/sample/sample_t2v.py", line 34, in main
vae = AutoencoderKL.from_pretrained(args.pretrained_model_path, subfolder="vae", torch_dtype=torch.float16).to(device)
File "/home/user/anaconda3/envs/torch2.0/lib/python3.10/site-packages/diffusers/models/modeling_utils.py", line 812, in from_pretrained
unexpected_keys = load_model_dict_into_meta(
File "/home/user/anaconda3/envs/torch2.0/lib/python3.10/site-packages/diffusers/models/modeling_utils.py", line 155, in load_model_dict_into_meta
raise ValueError(
ValueError: Cannot load /data/zhangmaolin/code/Latte/t2v_required_models because decoder.conv_in.bias expected shape tensor(..., device='meta', size=(64,)), but got torch.Size([512]). If you want to instead overwrite randomly initialized weights, please make sure to pass both low_cpu_mem_usage=False and ignore_mismatched_sizes=True. For more information, see also: https://github.com/huggingface/diffusers/issues/1619#issuecomment-1345604389 as an example
我的依赖包存放在代码根目录下面

我的配置文件如下

我的环境如下：
Package                 Version

absl-py                 2.1.0
accelerate              0.27.2
antlr4-python3-runtime  4.9.3
av                      11.0.0
Brotli                  1.0.9
certifi                 2024.2.2
charset-normalizer      2.0.4
decord                  0.6.0
diffusers               0.24.0
einops                  0.7.0
filelock                3.13.1
fsspec                  2024.2.0
gmpy2                   2.1.2
grpcio                  1.60.1
huggingface-hub         0.20.3
idna                    3.4
imageio                 2.34.0
importlib-metadata      7.0.1
Jinja2                  3.1.3
lazy_loader             0.3
Markdown                3.5.2
MarkupSafe              2.1.3
mkl-fft                 1.3.1
mkl-random              1.2.2
mkl-service             2.4.0
mpmath                  1.3.0
networkx                3.1
numpy                   1.24.3
omegaconf               2.3.0
packaging               23.2
pandas                  2.2.0
pillow                  10.2.0
pip                     23.3.1
protobuf                4.25.3
psutil                  5.9.8
PySocks                 1.7.1
python-dateutil         2.8.2
pytz                    2024.1
PyYAML                  6.0.1
regex                   2023.12.25
requests                2.31.0
safetensors             0.4.2
scikit-image            0.22.0
scipy                   1.12.0
setuptools              68.2.2
six                     1.16.0
sympy                   1.12
tensorboard             2.16.2
tensorboard-data-server 0.7.2
tifffile                2024.2.12
timm                    0.9.16
tokenizers              0.15.2
torch                   2.0.1
torchaudio              2.0.2
torchvision             0.15.2
tqdm                    4.66.2
transformers            4.37.2
triton                  2.0.0
typing_extensions       4.9.0
tzdata                  2024.1
urllib3                 2.1.0
Werkzeug                3.0.1
wheel                   0.41.2
zipp                    3.17.0

class AutoencoderKL(ModelMixin, ConfigMixin, FromOriginalVAEMixin):
r"""
A VAE model with KL loss for encoding images into latents and decoding latent representations into images.
This model inherits from [`ModelMixin`]. Check the superclass documentation for it's generic methods implemented
for all models (such as downloading or saving).

Parameters:
    in_channels (int, *optional*, defaults to 3): Number of channels in the input image.
    out_channels (int,  *optional*, defaults to 3): Number of channels in the output.
    down_block_types (`Tuple[str]`, *optional*, defaults to `("DownEncoderBlock2D",)`):
        Tuple of downsample block types.
    up_block_types (`Tuple[str]`, *optional*, defaults to `("UpDecoderBlock2D",)`):
        Tuple of upsample block types.
    block_out_channels (`Tuple[int]`, *optional*, defaults to `(64,)`):
        Tuple of block output channels.
    act_fn (`str`, *optional*, defaults to `"silu"`): The activation function to use.
    latent_channels (`int`, *optional*, defaults to 4): Number of channels in the latent space.
    sample_size (`int`, *optional*, defaults to `32`): Sample input size.
    scaling_factor (`float`, *optional*, defaults to 0.18215):
        The component-wise standard deviation of the trained latent space computed using the first batch of the
        training set. This is used to scale the latent space to have unit variance when training the diffusion
        model. The latents are scaled with the formula `z = z * scaling_factor` before being passed to the
        diffusion model. When decoding, the latents are scaled back to the original scale with the formula: `z = 1
        / scaling_factor * z`. For more details, refer to sections 4.3.2 and D.1 of the [High-Resolution Image
        Synthesis with Latent Diffusion Models](https://arxiv.org/abs/2112.10752) paper.
    force_upcast (`bool`, *optional*, default to `True`):
        If enabled it will force the VAE to run in float32 for high image resolution pipelines, such as SD-XL. VAE
        can be fine-tuned / trained to a lower range without loosing too much precision in which case
        `force_upcast` can be set to `False` - see: https://huggingface.co/madebyollin/sdxl-vae-fp16-fix
"""

_supports_gradient_checkpointing = True

@register_to_config
def __init__(
    self,
    in_channels: int = 3,
    out_channels: int = 3,
    down_block_types: Tuple[str] = ("DownEncoderBlock2D","DownEncoderBlock2D","DownEncoderBlock2D","DownEncoderBlock2D"),
    up_block_types: Tuple[str] = ("UpDecoderBlock2D","UpDecoderBlock2D","UpDecoderBlock2D","UpDecoderBlock2D"),
    block_out_channels: Tuple[int] = (128,256,512,512),
    layers_per_block: int = 2,
    act_fn: str = "silu",
    latent_channels: int = 4,
    norm_num_groups: int = 32,
    sample_size: int = 32,
    scaling_factor: float = 0.18215,
    force_upcast: float = True,
):

手动按照config.json里面的参数，在代码里面改了一下配置文件可以了，感觉是代码没有自动加载config.json，另外安装了imageio==2.20.0和imageio-ffmpeg


Disable install for all users

"Install for all users" disabled for Word and Excel addon.
Please also disable for PowerPoint installer.

Thanks

Word 和 Excel 插件禁用“为所有用户安装”。 另请禁用 PowerPoint 安装程序。 谢谢

Thank you very much, solved my problem

A new version has been released.


Impl DiscreteFinite for usize

Would it be possible to implement DiscreteFinite for usize?
https://github.com/ripytide/discrete_range_map/blob/main/src/discrete_finite.rs
I have a use case where I'm using array indices as the keys for a range map. The rough idea is that most of the time, the array has mostly the same values, so storing it as a range map is far more efficient (and makes a few algorithms easier to implement). Hence this request.

Absolutely, I completely forget about usize whoops.
I think given all the brilliant suggestions you've provided thus far, I will try to implement them all in the next few days and then after a bit of testing releasing all the new improvements in a v0.7.0.


Apply peer name filter for Chaincode approve operation

Signed-off-by: “Nithin<EMAIL_ADDRESS>

LGTM


Middleware not adding headers on an options/pre-flight call?

Hi,
I am still working on the project I raised and closed an earlier issue for and am now having CORS problems again but struggling to work out why. The summary of what I "think" is happening is:

The app is sending a custom header which I haven't managed to find yet on a POST, which causes it to make a pre-flight/options call to check what is allowed. (this is nothing to do with SLIM obviously). I have found that I can 'break' the headers with an incorrect attempt to set them and the calls work ok, SLIM responds to the POST with the correct headers.

The SLIM middleware is not responding to the OPTIONS call with the same headers as it is for POST calls, I have the middleware installed and logging so when normal calls come in I see the logs, but I never see anything for a pre-flight call which even if it was responding differently, I'd expect to see as log entry.

Point 1 above I need to sort out myself and am doing so in parallel. Point 2 I would really like some help to work out why SLIM isn't invoking the middleware for a pre-flight call.
More details below the line.

Using Slim 3.8.1 with Cors-Middleware 0.5.2. I'm trying to develop the UI with Ionic (via Ionic Creator) so using AngularJS. Using inspect I can see the headers being set on the POST as below, but the OPTIONS one seems to return different headers:
Response when I allow headers to go correctly and results in an OPTIONS call:
Request URL:https://<mydomain>.azurewebsites.net/logon
Request Method:OPTIONS
Status Code:200 OK
Remote Address:<ip_removed>:443
Referrer Policy:no-referrer-when-downgrade

Response Headers
Allow:OPTIONS, TRACE, GET, HEAD, POST
Content-Length:0
Date:Mon, 02 Oct 2017 12:38:42 GMT
Public:OPTIONS, TRACE, GET, HEAD, POST
Server:Microsoft-IIS/8.0
Set-Cookie:ARRAffinity=71348a31a0fb1ab0cb27394a14e292875f39c36acbe2721cdaa782e123565e70;Path=/;HttpOnly;Domain=<mydomain>.azurewebsites.net
X-Powered-By:ASP.NET

Response below when I 'break' the headers and it doesnt result in a pre-flight check:
Request URL:https://<mydomain>.azurewebsites.net/dashboard
Request Method:POST
Status Code:200 OK
Remote Address:<ip_removed>:443
Referrer Policy:no-referrer-when-downgrade

Response Headers
Access-Control-Allow-Credentials:true
Access-Control-Allow-Origin:https://creator.ionic.io
Access-Control-Expose-Headers:Authorization
Access-Control-Expose-Headers:Accept
Access-Control-Expose-Headers:Content-Type
Access-Control-Expose-Headers:Origin
Cache-Control:no-store, no-cache, must-revalidate
Content-Encoding:gzip
Content-Length:431
Content-Type:application/json;charset=utf-8
Date:Mon, 02 Oct 2017 13:09:51 GMT
Expires:Thu, 19 Nov 1981 08:52:00 GMT
Pragma:no-cache
Server:Microsoft-IIS/8.0
Vary:Origin,Accept-Encoding
X-Powered-By:ASP.NET
X-Powered-By:PHP/7.0.23

Note I know that there are a couple of things I need to hide there once I get to the bottom of this issue such as ASP.NET and PHP but not worried about it at this stage.
I've implemented the middleware as below, I've added a few permitted origins including evil.com due to using browser extension for debugging, I get the issues when that is switched off:
$app->add(new \Tuupola\Middleware\Cors([
  "origin" => ["https://creator.ionic.io", "http://evil.com", "http://<my_domain>.azurewebsites.net", "https://<my_domain>.azurewebsites.net"],
  "methods" => ["GET", "POST", "PUT", "PATCH", "DELETE", "OPTIONS"],
  "headers.allow" => ["Content-Type", "Authorization", "Accept", "Origin"],
  "headers.expose" => ["Content-Type", "Authorization", "Accept", "Origin"],
  "credentials" => true,
  "cache" => 0,
]));

Have I missed something that is obvious in how to make it fire the middleware on the OPTIONS or preflight request?
It appears to me that the lack of any log entry on an OPTIONS and the different headers returned may point to the middleware just not being invoked on an OPTIONS call but its a guess

It appears to me that the lack of any log entry on an OPTIONS and the different headers returned may point to the middleware just not being invoked on an OPTIONS call but its a guess

Sounds like the request is not even handled by Slim. Looking at the the example headers there is for example:
Server:Microsoft-IIS/8.0
X-Powered-By:ASP.NET

Maybe IIS or ASP somehow captures the requests?  In any case to be able to debug I need example curl command line request and the response headers. For example:
$ curl "https://api.example.com/" \
    --request OPTIONS \
    --include
    --header "Access-Control-Request-Method: PUT" \
    --header "Origin: http://www.example.com"

HTTP/1.1 200 OK
Access-Control-Allow-Origin: http://www.example.com
Vary: Origin
Access-Control-Allow-Methods: GET, POST, PUT, PATCH, DELETE

Thanks Mika, yep that sounds like a reasonable hypothesis - I will do some digging and see if I can find why that might be.
In the mean time I have also run the CURL request (running from windows using Confused By Code's tool: http://www.confusedbycode.com/curl/#downloads):
Request:
curl "https://eneroppdemoapi01.azurewebsites.net/logon" --request OPTIONS --include --header "Access-Control-Request-Method: POST" --header "Origin: http://localhost"
Response is:
HTTP/1.1 200 OK
Allow: OPTIONS, TRACE, GET, HEAD, POST
Content-Length: 0
Server: Microsoft-IIS/8.0
Public: OPTIONS, TRACE, GET, HEAD, POST
X-Powered-By: ASP.NET
Set-Cookie: ARRAffinity=71348a31a0fb1ab0cb27394a14e292875f39c36acbe2721cdaa782e123565e70;Path=/;HttpOnly;Domain=eneroppdemoapi01.azurewebsites.net
Date: Mon, 02 Oct 2017 14:27:00 GMT

As expected - no logging from the middleware or SLIM at all, so I suspect you are right, I'll update if I find anything further. Any ideas always welcome obviously

As an update if anyone else is hosting in a similar environment, Mika you were right on it not hitting SLIM, the reason being that IIS grabs it and processes. In order to force the OPTIONS request all the way through the SLIM I needed to add the below to the web.config on the server:
<system.webServer>

</system.webServer>
Now when I run the same CURL command I get a different response, which looks like the method type of options in not allowed. I am not seeing anything in the logs still for SLIM / middleware but it's getting further in.
HTTP/1.1 405 Method Not Allowed
Allow: GET, HEAD, OPTIONS, TRACE
Content-Length: 101
Content-Type: text/html
Server: Microsoft-IIS/8.0
X-Powered-By: ASP.NET
Set-Cookie: ARRAffinity=71348a31a0fb1ab0cb27394a14e292875f39c36acbe2721cdaa782e123565e70;Path=/;HttpOnly;Domain=eneroppdemoapi01.azurewebsites.net
Date: Mon, 02 Oct 2017 14:38:23 GMT

The page you are looking for cannot be displayed because an invalid method (HTTP verb) is being used.

I also get the same error when I call it from the Ionic Creator tool which is encouraging.

Finally found exactly what I needed to add to the Web Config, with a combination of:

https://stackoverflow.com/questions/30346907/how-to-remove-webdav-module-from-iis
https://stackoverflow.com/questions/22495240/iis-hijacks-cors-preflight-options-request

Attaching the web.config in case it is of any use to someone. Mika, it may be worth a note on the repo or this page: https://www.slimframework.com/docs/start/web-servers.html to the effect that if using the CORS middleware you need more than just the config on the web-servers page at present to make it work.
Obviously if someone is using PHP 5.6 then the line below needs updating (or if it is in a different location):
D:\Program Files (x86)\PHP\v7.0\php-cgi.exe
web.config.txt
Thanks for the initial suggestion Mika, I have been playing with this for almost 3 days now, finally working no problem.
Cheers
Dave


How to access "Fill" opacity value?

When saving PSD from SAI2 program, certain layer blending modes make it store opacity of that layer as "Fill" value instead, with "Opacity" value 255.
Is there a way to access this "Fill" opacity value?
I found some method named "fillOpacity" on the layer in the object tree, but it did not show anything usable. Probably it's not what I guessed.
In SAI:

In Photoshop:

My current (testing) workaround for the following:
layer with offending blend mode + N% opacity

is this:
folder - offending blend mode + 100% opacity
|- layer inside - normal mode + N% opacity

Here is my testing file: test_all_blending_modes.psd.zip

You can access this using node.layer.opacity when you are iterating through layers in your psd file

I can't, unfortunately. Double-checked right now again.
For the layer in question (screenshots and attachment above) it says 255, while in editor it's 50%.

So you do Math.round(node.layer.opacity*100/255)/100, then you will get the value between 0 and 1.
In your case, 50% would be -> 0.5.

Ok here it goes:
To get the opacity property, you use the following function, as mentioned before:
node.layer.opacity - this will return you the opacity between 0 and 255
To get the fill property, you have to use those following methods:
node.layer.fillOpacity().layer.adjustments.fillOpacity.obj.value;
"Simple like that" hahahaha
The value of the fill also will return between 0 and 255
To transform 0-255 to percentual value, you have to do
var result = node.layer.opacity;
Math.round(result*100/255)/100

This will return the value between 0 and 1, in your example, the value would be 0.5 (50%).

Oh, this really works. Thanks.
I'm using this for JS canvas, so I'm converting to a [0-1] float.
Maybe you also know something about layer masks? #60


Categorical feature: does LightGBM deal with non-int data types?

In the documentation here (https://lightgbm.readthedocs.io/en/latest/Parameters.html#categorical_feature), it is stated that categorical feature values must be integers.
However, in another documentation (https://lightgbm.readthedocs.io/en/latest/pythonapi/lightgbm.train.html#lightgbm.train), the categorical features values only need to be lower than int32 max value.
I tried to specify a float column as categorical feature, and the training works. The script is as follows:
import pandas as pd
import lightgbm as lgb
from sklearn import datasets

X_, y = datasets.load_wine(return_X_y=True)
X = pd.DataFrame(X_, columns=['col_%d' % _ for _ in range(X_.shape[1])])
d_train = lgb.Dataset(X, y)

param = dict(max_depth=5)
model = lgb.train(param, d_train, num_boost_round=20,
                  categorical_feature=['col_0'])   # col_0's data type is float

x = X.iloc[4, :]
y_pred = model.predict(x)

Can I get some clarification here?  Thanks!

@jsh9 You described the expected behavior. The first link is for LightGBM CLI version, and the second one is for Python-package. So, in CLI version it's possible to use only ints, and for Python-package you can use some other data types.
https://github.com/microsoft/LightGBM/blob/4fc0416fabee5ba8f062f6d7dd966e1b207b7f4f/tests/python_package_test/test_engine.py#L639-L644
If you are interested, here is the comment, which elaborates why I wrote "some other data types": https://github.com/microsoft/LightGBM/issues/2134#issuecomment-520261059.

@jsh9
Sure, here are answers for your question: https://github.com/microsoft/LightGBM/issues/804#issuecomment-507169407, https://github.com/microsoft/LightGBM/issues/1936#issuecomment-463958324.