Buggy Logic in trpo_mpi.utils.traj_segment_generator, 'ep_lens' key unreliable.

The function will record improper episode lengths in the returned dictionary.
The current episode length is recorded under 'current_it_len'. This is reset to zero even if the episode is not finished when yielding on line 89.
When the episode finishes, 'current_it_len' is recorded in the dictionary's ep_lens list. This length could be significantly shorter than the actual episode length.
The amount of time steps stored in 'total_timestep' as current_it_timesteps is correct; however, if using the ep_lens list, the length of the episode is shorter than it actually is.
Example:
Assume batch size (horizon) of 1200. Each episode lasts 500 time steps.
First iteration:  'ep_lens' = [500, 500], as only two episodes were completed. 'total_timesteps' is correct at 1200.
Second iteration: 'ep_lens' = [300, 500], as the episode from the last iteration completes, one more completes fully, and the next is ongoing on time step 400.
Third iteration: 'ep_lens' = [100, 500, 500].
The corresponding reward in 'ep_rets' is correct for the entirety of the episodes, but the length of the episodes as found in 'ep_lens' list are significantly shorter than expected.
I'm unsure what the episode lengths in 'ep_lens' are used for, but if they're used for some normalization based on the rewards, any of those calculations would be incorrect.

Hello,
thanks for reporting the issue, looks like a legit bug.

I'm unsure what the episode lengths in 'ep_lens' are used for

They are only used for logging (I have to double check), so that should be only a minor bug.
See here: https://github.com/hill-a/stable-baselines/blob/baa4aa5a3c3ffe4ef192b1d4b1c64e15c307c13f/stable_baselines/trpo_mpi/trpo_mpi.py#L464

I added a fix; apologies if it's minor enough of a bug to not warrant a PR. It looks like it affected logging in both TRPO and PPO1 modules, and the fix is only a few lines of change.

if it's minor enough of a bug to not warrant a PR

Everything that can be improved is worth a PR ;) (and the small ones are easier to review)


Reduce the number of places that know that we encode article DOIs for URIs

URI encoding can be removed completely if we change the router to recognise the route /articles/:prefix/:suffix instead of /articles/:doi.


layout: address deprecated method warning

warning: use of deprecated method `chrono::TimeZone::datetime_from_str`:
use `DateTime::parse_from_str` instead
  --> src/models/layout/mod.rs:77:9
   |
77 |     Utc.datetime_from_str(ts, "%FT%TZ")
   |         ^^^^^^^^^^^^^^^^^
   |
   = note: `#[warn(deprecated)]` on by default

Thanks for this PR! I think the timing was unfortunate because @alanssitis submitted #70 right before this one that also resolves the same issue. Closing in favour of that one.


[stable/zetcd] zetcd chart

A chart that bootstraps zetcd with an optional etcd-operator cluster.

/ok-to-test

/ok-to-test


mongodb cascade relationships

Hello, Thank you for reporting this enhancement feature
I will change this to implement cascade delete because I already created an issue for
cascade persist

delivered in the following versions :

v2.1.0
v1.2.0


move trial text to show-viewercode page

Purpose
Move trial paragraph from create-viewercode page to show-viewercode page
Fixes UML-810
Checklist

[x] I have performed a self-review of my own code
[ ] I have added relevant logging with appropriate levels to my code
[ ] I have updated documentation (Confluence/GitHub wiki/tech debt doc) where relevant
[ ] I have added tests to prove my work
[ ] The product team have tested these changes

Coverage remained the same at 81.507% when pulling 1f5dd996d15af1bf0a4539bde66ca84c8875ddd8 on UML-810-trial-paragraph into 271afc47be6aa1c44dd6c5772db29d27c5686b42 on master.


enhance(oidc): add more claims

closes https://github.com/go-vela/community/issues/996
Note: I intended to include whether the build was triggered from a fork, but it seems we don’t currently store that information in the database. Therefore, I decided to omit that detail for now. If someone wants to add this feature in the future, they will also need to update the database to capture this data.

Is there an intention to follow up this PR with the API implementation here?

Is there an intention to follow up this PR with the API implementation here?

Can you expand on this a bit more? The code I added should be returned in the API payload due to https://github.com/go-vela/server/blob/0894432bab40b5b6981007233aca0f7d093194b1/api/build/id_token.go#L121.

Is there an intention to follow up this PR with the API implementation here?

Can you expand on this a bit more? The code I added should be returned in the API payload due to
https://github.com/go-vela/server/blob/0894432bab40b5b6981007233aca0f7d093194b1/api/build/id_token.go#L121
.

Whoops, got confused and thought image was net new. Yep lgtm


 Root level README is yet to be updated. But I am not sure if I should add my stuff above tensorflow-hub or replace tensorflow-hub portion with tensorflow-metadata.

You need to change the top level .travis to include the job to build metadata.
You can change it to include only metadata. You may have to rebase that file in this PR on occasion as that file may update frequently.

https://github.com/IBM/powerai/issues/39

Addressed the review comments.


Create category /  sub category for sorting thing when data scale up

Hi, I've just randomly pulled your project and I think it is nice compared to old twiki and xwiki.
Currently we can just write books with chapter, but there is no way to sort them by group.
Feature would add a way of creating category, eventually sub categories to save our book outside the global namespace.
Also, would you add later file upload on article like zip pdf ... ? Thanks

Hi @kopax, Thank you for your suggestions.
You can add an extra layer of categorisation by using tags. These can be added in the right sidebar when editing a book. Here you can also upload attachments, of any file type, to a page as requested:

If you instead wanted an extra level in the heirachy, That is already an open issue under #95.
Does the above solve your requests?

@ssddanbrown thanks for the info.
About the categorization by tags, it is good to be able to have tag for finding out a book from its tag. But as a way to display book, tags don't allow to list and display books by category, they are all mixed up. I think this is somehow very important if you want to have many books many users, and users to be allowed to read/display just certain categories of books.
My use case is that we have services (marketing, developers,....) and users should be able to display/read book only from their own services

@kopax You can create roles, assign them to users, Then change permissions of particular books to only be readable/editable by certain roles. That sounds like what you're asking here.

@ssddanbrown even if it's true, it is not nice to do it for each book (rather than just adding it to a category where user have permissions).
On the UI side, user will not have a way to browse by hierarchy other than filtering.
I believe we should create a bookshelf, and a UI to browse bookshelf.
I think this is not possible :

This is what we need :

As of the next release BookStack will have Bookshelves as described here which brings a level of categorization to Books.  This appears to meet the main request of this issue so I will close this.

@ssddanbrown just wow. We've been going on with wikijs and aren't really satisfied of their UI that has many bugs. BookStack was good at testing but lacking some important feature. It sounds good if you corrected all that, is there a way to test online?

@kopax You can see the demo site here:
<EMAIL_ADDRESS>It resets every half hour and some features are disabled (I think adding users or updating settings).

@ssddanbrown I don't see how you solved the categories permissions issues.
Our organization needs groups, and permissions should be given to group.
Right now with wikijs, we are able to protect anywhere in such path (not by group but at least individually): a>b>c>d>e>f.


Deploy Ask-Anything as APIs locally/on cloud using langchain-serve

Repo - langchain-serve.

Exposes APIs from function definitions locally as well as on the cloud.
Very few lines of code changes and ease of development remain the same as local.
Supports both REST & WebSocket endpoints
Serverless/autoscaling endpoints with automatic tls certs on the cloud.
Real-time streaming, human-in-the-loop support - which is crucial for chatbots.

Disclaimer: I'm the primary author of langchain-serve. Would be happy to collaborate on this!

Thanks for your suggestion! Hopefully for your collaboration!


Different handling of DateTime conversion

The main purpose of this pull request is to use the ISO8601 standard for encoding and decoding DateTime instances. It also fixes the issue where fractional seconds are discarded when decoding a timestamp/timestamptz. When working with a timestamp column, a user of this library should first convert a DateTime instance to UTC. When working with a timestamptz column, a user may use a DateTime instance in local time.
Additional details: The version number has been changed to 0.3.2. The unit test package has been changed to the renamed 'test' package.

Hi, thanks for taking the time to clean this up. This looks really good. Sorry about my delay in responding.
My only concern is around the use of time zone names. I think the driver should pass time zone offset to the database instead.
From memory last time I looked at this the result of DateTime.timeZoneName differs depending on OS, and some of the abbreviations are actually ambiguous. i.e. EST could be Australian or US eastern time. I think it is better to stick with passing a timezone offset.

I think @xxgreg means the following problem with timeZoneName: https://github.com/xxgreg/dart_postgresql/issues/46#issuecomment-62625164
I'm not sure if it was addressed in the SDK.
PS: Maybe you put the unittest to test migration into a seperate PR, that should be easy to merge.

Thanks for the link. This is one specific example of the problem.
We must also consider a more general problem, which is given an ISO 8601 string + a time zone name, it is both difficult, and not always possible to correctly convert this into a UTC ISO 8601 string.
It is difficult because you need a database containing the history of every time zone change in every country. These timezone databases are not always complete or up to date.
It is not aways possible because of ambiguous time zone abbreviations, different operating system time zone names, and bugs.
In my opinion since we already know the time zone offset we should just pass this to the database.

OK, I think that is a great idea and I've added another commit to address that issue along with tests to ensure it.

Thanks ;)  I'll take a look at this in a couple of days.

Apologies for my slow reply.
I'm happy to merge as is. I noticed a few minor things that may be worth fixing.
Perhaps I'm using an old version or a strange config, but for BC dates postgresql doesn't match Dart's subset of ISO 8601. It would be nice to have a fix for this. Probably just need to check for a BC suffix, and add a negative prefix.
For example this is what I see:
testdb=> insert into datetest values ('-0200-01-01T00:00:00.000');
ERROR:  time zone displacement out of range: "-0200-01-01T00:00:00.000"
LINE 1: insert into datetest values ('-0200-01-01T00:00:00.000');
                                     ^
testdb=> insert into datetest values ('0200-01-01T00:00:00.000 BC');
INSERT 0 1
testdb=> select * from datetest;
           t
------------------------
0200-01-01 00:00:00 BC
(1 rows)

Can you add this comment back in, somewhere in decodeDateTime():
    // Built in Dart dates can either be local time or utc. Which means that the
    // the postgresql timezone parameter for the connection must be either set
    // to UTC, or the local time of the server on which the client is running.
    // This restriction could be relaxed by using a more advanced date library
    // capable of creating DateTimes for a non-local time zone.

There also used to be a test for large dates i.e. 5-6 digits - I can't see this any more.

I'm adding the comment back in. Per the notes on BC dates and large dates, I did a bit of research (this is a topic I am unfamiliar with). Effectively, ISO 8601 makes a suggestion as to how to handle BC dates and 5+ digit dates, however, it is not part of the standard and apparently the client/server must agree - and Dart and PostgreSQL do not agree. The year 10000 encodes to +010000 in Dart but PostgreSQL expects simply 10000 (which goes against the standard recommendation, I believe). This would also be true of negative values ('BC') - and apparently that technically includes dates prior to 1583. I think a future pull request could provide some special handling of dates outside of that range, and I may have an opportunity to put that together next week.

I've also added a commented out test for checking those edge cases (BC, 5-digit year) that can be uncommented once implemented.

I finally was able to take a couple of hours to work on this. Thank you for being patient. I've added back the BC date support and had a quick pass over the tests. Please take a look and see if the changes make sense to you. Then I'll publish 0.3.2.
Cheers for the hard work.


amplify push api not working

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
16.13.1
Amplify CLI Version
7.6.15
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Amplify Categories
api
Amplify Commands
push
Describe the bug
I have created multiple .graphql files in schema directory, and removed schema.graphql file from /amplify/backend/api/<API_NAME>/schema/ directory.
running amplify api gql-compile command works and returns successfully
running amplify push prompt with following message:
✔ This version of Amplify CLI introduces additional security enhancements for your GraphQL API. @auth authorization rules applied on primary keys and indexes are scoped down further. The changes are applied automatically with this deployment. This change won't impact your client code. Continue (Y/n) · yes
Choosing yes, creates an empty schema.graphql file in directory /amplify/backend/api/<API_NAME>/
As schema.graphql file is empty, this leads to following error when pushing changes
✖ There was an error pulling the backend environment dev. 🛑 An error occurred during the push operation: Syntax Error: Unexpected <EOF>
Expected behavior
In case, .graphql files placed in /amplify/backend/api/<API_NAME>/schema/ directory, those files should be used, instead of creating an empty schema.graphql in /amplify/backend/api/<API_NAME>/
Additionally, schema path specified as gqlSchemaPath in cli-inputs.json file should be used
Reproduction steps
Create .graphql files in /amplify/backend/api/<API_NAME>/schema/ directory
Remove schema.graphql file in /amplify/backend/api/<API_NAME>/ directory
Run amplify push
On following prompt, choose yes
✔ This version of Amplify CLI introduces additional security enhancements for your GraphQL API. @auth authorization rules applied on primary keys and indexes are scoped down further. The changes are applied automatically with this deployment. This change won't impact your client code. Continue (Y/n) · yes
Error is thrown 🛑 An error occurred during the push operation: Syntax Error: Unexpected <EOF>
GraphQL schema(s)

# Put schemas below this line

Log output

# Put your logs below this line
% amplify push --y

✔ This version of Amplify CLI introduces additional security enhancements for your GraphQL API. @auth authorization rules applied on primary keys and indexes are scoped down further. The changes are applied automatically with this deployment. This change won't impact your client code. Continue (Y/n) · yes

✖ There was an error pulling the backend environment dev.
🛑 An error occurred during the push operation: Syntax Error: Unexpected <EOF>

GraphQL request:1:2
1 |
  |  ^

Additional information
No response

Hey @adilusman51 :wave: thanks for raising this! This appears to be a duplicate of https://github.com/aws-amplify/amplify-cli/issues/9624 and should be fixed with https://github.com/aws-amplify/amplify-cli/pull/9670. From the issue linked,

By deleting the empty file before answering the second question I was able to get the push to complete successfully.

Marking as a duplicate bug and closing in favor of tracking the existing item. Please subscribe to #9624 for additional updates

@josefaidt Thanks for providing an update, this is in fact a duplicate issue of #9624


About batch_size in training configuration?

Hi Luo, thanks for your remarkable work!
I am here wondering why use batch 128 in 4gpu DDP training? That is to say 32 per GPU which only accounts for less than 1/2 GPU memory. Is that for some special purpose?

Hi @xiao2mo,  there is no special purpose. We set batch size 32 per GPU because some of our machines are 16G per card, and we need to test some other parameters like frame number. It is an appropriate batch size to finish the hyper-parameters study.  If your card has more than 16G, a suggestion is to test a large frame number, then a  large batch size.

I see it. The main problem in my exps is that batch size in DDP configuration may result in different results. Thank u.

hi
我这边是两张卡，每张卡是16G。
可是我能设置的batchsize是 16， 请问这是为什么呢？
训练配置如下
01/10/2022 16:18:00 - INFO -   ***** Running test *****
01/10/2022 16:18:00 - INFO -     Num examples = 497
01/10/2022 16:18:00 - INFO -     Batch size = 16
01/10/2022 16:18:00 - INFO -     Num steps = 32
01/10/2022 16:18:00 - INFO -   ***** Running val *****
01/10/2022 16:18:00 - INFO -     Num examples = 497
222
333
01/10/2022 16:18:12 - INFO -   ***** Running training *****
01/10/2022 16:18:12 - INFO -     Num examples = 130260
01/10/2022 16:18:12 - INFO -     Batch size = 16
01/10/2022 16:18:12 - INFO -     Num steps = 40705
01/10/2022 16:21:34 - INFO -   Epoch: 1/5, Step: 50/8141, Lr: 0.000000001, Loss: 0.455173, Time/step: 4.041784

用的资源如图：


Fix encoding non-UTF8 values in String field

Fixes #297
One outstanding issue is what behaviour do we expect from Bytes() and SetBytes()?
Currently, these return/take the UTF8 encoded bytes, regardless of the specified encoding, but it seems like it could be more appropriate to return/take bytes in the specified encoding.
I tried doing this, but this led to issues with other functions in the library which expected the current behaviour, and users of this library may expect the same.

Closing in favour of #299


Danfoss Link Thermostat is recognized as a temperature Sensor

Describe The Bug:
Hi joeyhage,
I have eleven thermostats (Danfoss Link System) connected to Alexa and they are working fine (you can find four of them in the screenshot below under favorites). These thermostats are the only devices I control via Alexa. All my other smarthome stuff is controlled via HomeKit.
I wanted to use your plugin to transfer these thermostats to HomeKit. Unfortunately, the plugin recognizes them as temperature sensors.
Have I done something wrong or is it a bug?
Maybe there is one thing. The mode of the thermostats is not changeable in Alexa. The mode is always „Benutzerdefiniert“, in English „custom“.
Best regards,
Patrick
To Reproduce:

Expected behavior:

Logs:
[04/11/2023, 15:22:50] [HB Supervisor] Starting Homebridge with extra flags: -I -P /var/lib/homebridge/node_modules --strict-plugin-resolution
[04/11/2023, 15:22:50] [HB Supervisor] Started Homebridge v1.7.0 with PID: 8077
[04/11/2023, 15:22:51] Loaded config.json with 4 accessories and 6 platforms.
[04/11/2023, 15:22:51] Loaded 12 cached accessories from cachedAccessories.
[04/11/2023, 15:22:51] ---
[04/11/2023, 15:22:52] Loaded plugin<EMAIL_ADDRESS>[04/11/2023, 15:22:52] Registering platform 'homebridge-alexa-smarthome.HomebridgeAlexaSmartHome'
[04/11/2023, 15:22:52] ---
[04/11/2023, 15:22:52] Loaded plugin<EMAIL_ADDRESS>[04/11/2023, 15:22:52] Registering platform 'homebridge-deconz.deCONZ'
[04/11/2023, 15:22:52] ---
[04/11/2023, 15:22:52] Loaded plugin<EMAIL_ADDRESS>[04/11/2023, 15:22:52] Registering accessory 'homebridge-dummy.DummySwitch'
[04/11/2023, 15:22:52] ---
[04/11/2023, 15:22:52] Loaded plugin<EMAIL_ADDRESS>[04/11/2023, 15:22:52] Registering platform 'homebridge-eveatmo.eveatmo'
[04/11/2023, 15:22:52] ---
[04/11/2023, 15:22:52] Loaded plugin<EMAIL_ADDRESS>[04/11/2023, 15:22:52] Registering platform 'homebridge-harmony.HarmonyHubWebSocket'
[04/11/2023, 15:22:52] ---
[04/11/2023, 15:22:52] Loaded plugin<EMAIL_ADDRESS>[04/11/2023, 15:22:52] Registering platform 'homebridge-shelly-switch.Shelly Switch'
[04/11/2023, 15:22:52] ---
[04/11/2023, 15:22:52] Loading 6 platforms...
[04/11/2023, 15:22:52] [Warmwasser] Initializing Shelly Switch platform...
[04/11/2023, 15:22:52] [Wetterstation] Initializing eveatmo platform...
[04/11/2023, 15:22:52] [Wetterstation] Authenticating using 'refresh_token' grant
[04/11/2023, 15:22:55] [Wetterstation] Loading new data from API for: weatherstation
[04/11/2023, 15:22:55] [deCONZ] Initializing deCONZ platform...
[04/11/2023, 15:22:55] [deCONZ] homebridge-deconz v1.0.6, node v18.16.0, homebridge v1.7.0, homebridge-lib v6.6.4
[04/11/2023, 15:22:55] [deCONZ] warning: recommended version: node v20.9.0
[04/11/2023, 15:22:55] [deCONZ] warning: recommended version: homebridge v1.6.1
[04/11/2023, 15:22:55] [HarmonyHub] Initializing HarmonyHubWebSocket platform...
[04/11/2023, 15:22:55] [HarmonyHub] HarmonyPlatform Init
[04/11/2023, 15:22:55] [HomebridgeAlexaSmartHome] Initializing HomebridgeAlexaSmartHome platform...
[04/11/2023, 15:22:55] Loading 4 accessories...
[04/11/2023, 15:22:55] [Fenstersensor] Initializing DummySwitch accessory...
[04/11/2023, 15:22:55] [Fenstersensor] Setting switch to false
[04/11/2023, 15:22:55] [WW Danfoss] Initializing DummySwitch accessory...
[04/11/2023, 15:22:55] [WW Danfoss] Setting switch to false
[04/11/2023, 15:22:55] [WW Timer 10 Minuten] Initializing DummySwitch accessory...
[04/11/2023, 15:22:55] [WW Timer 10 Minuten] Setting switch to false
[04/11/2023, 15:22:55] [Jemand zuhause] Initializing DummySwitch accessory...
[04/11/2023, 15:22:55] [Jemand zuhause] Setting switch to true
[04/11/2023, 15:22:55] [deCONZ] Phoscon-GW: dresden elektronik deCONZ / ConBee II gateway v2.24.1
[04/11/2023, 15:22:55] [deCONZ] Phoscon-GW: warning: recommended version: deCONZ v2.23.2
[04/11/2023, 15:22:55] [HarmonyHub] DidFinishLaunching
[04/11/2023, 15:22:55] [HarmonyHub] (HarmonyHub)INFO - Loading activities...
[04/11/2023, 15:22:55] [HarmonyHub] (undefined)WARNING - platform undefined is empty
[04/11/2023, 15:22:55] [HarmonyHub] INFO - starting hub discovery
[04/11/2023, 15:22:55] [HomebridgeAlexaSmartHome] Alexa-Remote: cookie was provided
[04/11/2023, 15:22:56] [deCONZ] hardware: Raspberry Pi 4B 1.4 (8GB)
[04/11/2023, 15:22:56] [deCONZ] os: Raspbian GNU/Linux 11 (bullseye) [32 bit]
[04/11/2023, 15:22:56] [deCONZ] restored 3 accessories from cache
[04/11/2023, 15:22:56] [deCONZ] ui server: listening on http://<IP_ADDRESS>:43333/
[04/11/2023, 15:22:56] [HomebridgeAlexaSmartHome] Alexa-Remote: Authentication checked: true
[04/11/2023, 15:22:56] Initializing platform accessory 'Walküre (Wohnzimmer) Wohnzimmer'...
[04/11/2023, 15:22:56] Initializing platform accessory 'Walküre (Wohnzimmer) Hobbyraum'...
[04/11/2023, 15:22:56] Initializing platform accessory 'Walküre (Wohnzimmer) Außen'...
Setup Payload:
X-HM://0023YKLJ1BGMN
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:

    ┌────────────┐
    │ 296-28-413 │
    └────────────┘

[04/11/2023, 15:22:56] Homebridge v1.7.0 (HAP v0.11.1) (Homebridge A981) is running on port XYZXY.
[04/11/2023, 15:22:56] [HomebridgeAlexaSmartHome] Alexa-Remote: Change Base URL for API calls to eu-api-alexa.amazon.de
[04/11/2023, 15:22:57] [deCONZ] Phoscon-GW: websocket connected to ws://XYZ.XYZ.XYZ.XY:
[04/11/2023, 15:22:57] [HomebridgeAlexaSmartHome] Successfully authenticated Alexa account.
[04/11/2023, 15:22:57] [HomebridgeAlexaSmartHome] Found 11 devices connected to the current Alexa account.
[04/11/2023, 15:22:57] [HomebridgeAlexaSmartHome] BEGIN devices connected to Alexa account

 [
  {
    "displayName": "EG Wohnen",
    "deviceType": "TEMPERATURE_SENSOR"
  },
  {
    "displayName": "OG Kind",
    "deviceType": "TEMPERATURE_SENSOR"
  },
  {
    "displayName": "UG Bad",
    "deviceType": "TEMPERATURE_SENSOR"
  },
  {
    "displayName": "OG Bad",
    "deviceType": "TEMPERATURE_SENSOR"
  },
  {
    "displayName": "UG Gast",
    "deviceType": "TEMPERATURE_SENSOR"
  },
  {
    "displayName": "EG HWR",
    "deviceType": "TEMPERATURE_SENSOR"
  },
  {
    "displayName": "OG Bad HK",
    "deviceType": "TEMPERATURE_SENSOR"
  },
  {
    "displayName": "EG Flur",
    "deviceType": "TEMPERATURE_SENSOR"
  },
  {
    "displayName": "OG Arbeit",
    "deviceType": "TEMPERATURE_SENSOR"
  },
  {
    "displayName": "OG Schlafen",
    "deviceType": "TEMPERATURE_SENSOR"
  },
  {
    "displayName": "EG WC",
    "deviceType": "TEMPERATURE_SENSOR"
  }
]

END devices connected to Alexa account
[04/11/2023, 15:22:57] [HomebridgeAlexaSmartHome] 0 devices provided in settings but 11 matching Alexa smart home devices were discovered.
[04/11/2023, 15:22:57] [HomebridgeAlexaSmartHome] Updating device states
[04/11/2023, 15:22:57] [HarmonyHub] (HarmonyHub)INFO - Discovered Activity : PowerOff
[04/11/2023, 15:22:57] [HarmonyHub] (HarmonyHub)INFO - Discovered Activity : Radio Charivari
[04/11/2023, 15:22:57] [HarmonyHub] (HarmonyHub)INFO - Discovered Activity : Fernsehen
[04/11/2023, 15:22:57] [HarmonyHub] (HarmonyHub)INFO - Discovered Activity : Apple TV
[04/11/2023, 15:22:57] [HarmonyHub] (HarmonyHub)INFO - Discovered Activity : Spielen
[04/11/2023, 15:22:57] [HarmonyHub] (HarmonyHub)INFO - Discovered Activity : Radio Bayern 3
[04/11/2023, 15:22:57] [HarmonyHub] (HarmonyHub)INFO - Discovered Activity : Radio Antenne Bayern
[04/11/2023, 15:22:57] [HarmonyHub] (HarmonyHub)INFO - Discovered Activity : Musik streamen
[04/11/2023, 15:22:58] [deCONZ] Phoscon-GW: warning: BJ Wandsender 1: exposed by draft ddf
[04/11/2023, 15:22:58] [deCONZ] Phoscon-GW: BJ Wandsender 1: add accessory
[04/11/2023, 15:22:58] [deCONZ] BJ Wandsender 1: Busch-Jaeger RB01 v0.0.0 (4 resources)
[04/11/2023, 15:22:58] [deCONZ] Phoscon-GW: warning: BJ Wandsender 2: exposed by draft ddf
[04/11/2023, 15:22:58] [deCONZ] Phoscon-GW: BJ Wandsender 2: add accessory
[04/11/2023, 15:22:58] [deCONZ] BJ Wandsender 2: Busch-Jaeger RB01 v0.0.0 (4 resources)
[04/11/2023, 15:22:58] [deCONZ] Phoscon-GW: dresden elektronik deCONZ / ConBee II gateway v2.24.1 (2 accessories for 6 devices, 8 resources)
[04/11/2023, 15:22:58] [deCONZ] Phoscon-GW: warning: recommended version: deCONZ v2.23.2
[04/11/2023, 15:22:58] [deCONZ] Phoscon-GW: migration: /resourcelinks/1: 8 resources
[04/11/2023, 15:22:58] [deCONZ] 1 gateways
[04/11/2023, 15:22:58] [deCONZ] created debug dump file /var/lib/homebridge/homebridge-deconz.json.gz
[04/11/2023, 15:22:59] [HomebridgeAlexaSmartHome] Initialize Devices - UnsupportedDeviceError(Unsupported device: EG Wohnen with type: TEMPERATURE_SENSOR. Currently supported device types are: LIGHT,SWITCH,SMARTLOCK,SMARTPLUG,THERMOSTAT,ALEXA_VOICE_ENABLED,AIR_QUALITY_MONITOR.)
[04/11/2023, 15:22:59] [HomebridgeAlexaSmartHome] Initialize Devices - UnsupportedDeviceError(Unsupported device: OG Kind with type: TEMPERATURE_SENSOR. Currently supported device types are: LIGHT,SWITCH,SMARTLOCK,SMARTPLUG,THERMOSTAT,ALEXA_VOICE_ENABLED,AIR_QUALITY_MONITOR.)
[04/11/2023, 15:22:59] [HomebridgeAlexaSmartHome] Initialize Devices - UnsupportedDeviceError(Unsupported device: UG Bad with type: TEMPERATURE_SENSOR. Currently supported device types are: LIGHT,SWITCH,SMARTLOCK,SMARTPLUG,THERMOSTAT,ALEXA_VOICE_ENABLED,AIR_QUALITY_MONITOR.)
[04/11/2023, 15:22:59] [HomebridgeAlexaSmartHome] Initialize Devices - UnsupportedDeviceError(Unsupported device: OG Bad with type: TEMPERATURE_SENSOR. Currently supported device types are: LIGHT,SWITCH,SMARTLOCK,SMARTPLUG,THERMOSTAT,ALEXA_VOICE_ENABLED,AIR_QUALITY_MONITOR.)
[04/11/2023, 15:22:59] [HomebridgeAlexaSmartHome] Initialize Devices - UnsupportedDeviceError(Unsupported device: UG Gast with type: TEMPERATURE_SENSOR. Currently supported device types are: LIGHT,SWITCH,SMARTLOCK,SMARTPLUG,THERMOSTAT,ALEXA_VOICE_ENABLED,AIR_QUALITY_MONITOR.)
[04/11/2023, 15:22:59] [HomebridgeAlexaSmartHome] Initialize Devices - UnsupportedDeviceError(Unsupported device: EG HWR with type: TEMPERATURE_SENSOR. Currently supported device types are: LIGHT,SWITCH,SMARTLOCK,SMARTPLUG,THERMOSTAT,ALEXA_VOICE_ENABLED,AIR_QUALITY_MONITOR.)
[04/11/2023, 15:22:59] [HomebridgeAlexaSmartHome] Initialize Devices - UnsupportedDeviceError(Unsupported device: OG Bad HK with type: TEMPERATURE_SENSOR. Currently supported device types are: LIGHT,SWITCH,SMARTLOCK,SMARTPLUG,THERMOSTAT,ALEXA_VOICE_ENABLED,AIR_QUALITY_MONITOR.)
[04/11/2023, 15:22:59] [HomebridgeAlexaSmartHome] Initialize Devices - UnsupportedDeviceError(Unsupported device: EG Flur with type: TEMPERATURE_SENSOR. Currently supported device types are: LIGHT,SWITCH,SMARTLOCK,SMARTPLUG,THERMOSTAT,ALEXA_VOICE_ENABLED,AIR_QUALITY_MONITOR.)
[04/11/2023, 15:22:59] [HomebridgeAlexaSmartHome] Initialize Devices - UnsupportedDeviceError(Unsupported device: OG Arbeit with type: TEMPERATURE_SENSOR. Currently supported device types are: LIGHT,SWITCH,SMARTLOCK,SMARTPLUG,THERMOSTAT,ALEXA_VOICE_ENABLED,AIR_QUALITY_MONITOR.)
[04/11/2023, 15:22:59] [HomebridgeAlexaSmartHome] Initialize Devices - UnsupportedDeviceError(Unsupported device: OG Schlafen with type: TEMPERATURE_SENSOR. Currently supported device types are: LIGHT,SWITCH,SMARTLOCK,SMARTPLUG,THERMOSTAT,ALEXA_VOICE_ENABLED,AIR_QUALITY_MONITOR.)
[04/11/2023, 15:22:59] [HomebridgeAlexaSmartHome] Initialize Devices - UnsupportedDeviceError(Unsupported device: EG WC with type: TEMPERATURE_SENSOR. Currently supported device types are: LIGHT,SWITCH,SMARTLOCK,SMARTPLUG,THERMOSTAT,ALEXA_VOICE_ENABLED,AIR_QUALITY_MONITOR.)
[04/11/2023, 15:23:01] [HarmonyHub] INFO - stopping hub discovery, hubs found : <IP_ADDRESS>|Harmony Hub|17095773

Plugin Config:
{
    "bridge": {
        "name": "Homebridge A981",
        "username": "0E:24:41:4A:A9:81",
        "port": XYZXY,
        "pin": "[296-28-413](tel:296-28-413)",
        "advertiser": "avahi"
    },
    "accessories": [
        {
            "name": "Fenstersensor",
            "stateful": true,
            "dimmer": false,
            "reverse": false,
            "time": 10000,
            "random": false,
            "resettable": false,
            "brightness": 0,
            "disableLogging": false,
            "accessory": "DummySwitch"
        },
        {
            "name": "WW Danfoss",
            "stateful": true,
            "dimmer": false,
            "reverse": false,
            "time": 1000,
            "random": false,
            "resettable": false,
            "brightness": 0,
            "disableLogging": false,
            "accessory": "DummySwitch"
        },
        {
            "name": "WW Timer 10 Minuten",
            "stateful": true,
            "dimmer": false,
            "reverse": false,
            "time": 1000,
            "random": false,
            "resettable": false,
            "brightness": 0,
            "disableLogging": false,
            "accessory": "DummySwitch"
        },
        {
            "name": "Jemand zuhause",
            "stateful": true,
            "dimmer": false,
            "reverse": false,
            "time": 1000,
            "random": false,
            "resettable": false,
            "brightness": 0,
            "disableLogging": false,
            "accessory": "DummySwitch"
        }
    ],
    "platforms": [
        {
            "name": "Config",
            "port": XYZY,
            "platform": "config"
        },
        {
            "platform": "Shelly Switch",
            "name": "Warmwasser",
            "notification_port": XYZXY,
            "devices": [
                {
                    "name": "WW Pumpenrelais",
                    "ip": "XYZ.XYZ.XYZ.XY",
                    "authetification": "xyzxyzxyz"
                }
            ]
        },
        {
            "name": "Wetterstation",
            "ttl": 540,
            "extra_co2_sensor": false,
            "weatherstation": true,
            "airquality": false,
            "co2_alert_threshold": 2000,
            "log_info_msg": true,
            "auth": {
                "client_id": "XYZXYZ",
                "client_secret": "XYZXYZXYZ,
                "grant_type": "refresh_token",
                "refresh_token": "XYZXYZ"
            },
            "platform": "eveatmo"
        },
        {
            "name": "deCONZ",
            "platform": "deCONZ"
        },
        {
            "name": "HarmonyHub",
            "hubIP": "XYZ.XYZ.XYZ.XY",
            "DELAY_BEFORE_RETRY_AFTER_NETWORK_LOSS": 60000,
            "HUB_CONNECT_TIMEOUT": 10000,
            "HUB_SEND_TIMEOUT": 30000,
            "TVAccessory": false,
            "sortInput": 0,
            "switchAccessories": true,
            "showTurnOffActivity": "inverted",
            "otherPlatforms": [
                {
                    "TVAccessory": false,
                    "sortInput": 0
                }
            ],
            "platform": "HarmonyHubWebSocket"
        },
        {
            "devices": [],
            "auth": {
                "refreshInterval": 4,
                "proxy": {
                    "clientHost": "homebridge.local",
                    "port": 9000
                }
            },
            "amazonDomain": "amazon.de",
            "language": "de-DE",
            "performance": {
                "cacheTTL": 30,
                "backgroundRefresh": false
            },
            "debug": true,
            "platform": "HomebridgeAlexaSmartHome"
        }
    ]
}

Screenshots:

Environment:

Plugin Version: v2.0.1
Homebridge Version: v1.7.0
Node.js Version: v18.16.0
NPM Version: don’t know, but its new installed less than one week ago
Operating System: Raspbian

I just tried to add the Danfoss Thermostats as well and I'm running into the exact same bug.

After updating to version v2.0.8 and v2.1.0 I see additional logs during the startup process (screenshot see below).
Maybe they can help to solve the issue with the Danfoss Link thermostats.
For me it seems that each thermostat will be recognized as a temperature sensor AND as a thermostat.
Here one example out of the log for one thermostat "OG Bad":
"SKILL_eyJza2lsbElkIjoiYW16bjEuYXNrLnNraWxsLmE5Y2U3ZjU4LTZkZjAtNDAwMi1hOTMzLTM5OTI3MjhmYTBmYSIsInN0YWdlIjoibGl2ZSJ9_Room:7": {
                  "applianceId": "SKILL_eyJza2lsbElkIjoiYW16bjEuYXNrLnNraWxsLmE5Y2U3ZjU4LTZkZjAtNDAwMi1hOTMzLTM5OTI3MjhmYTBmYSIsInN0YWdlIjoibGl2ZSJ9_Room:7",
                  "endpointTypeId": "",
                  "driverIdentity": {
                    "namespace": "SKILL",
                    "identifier": "eyJza2lsbElkIjoiYW16bjEuYXNrLnNraWxsLmE5Y2U3ZjU4LTZkZjAtNDAwMi1hOTMzLTM5OTI3MjhmYTBmYSIsInN0YWdlIjoibGl2ZSJ9"
                  },
                  "manufacturerName": "Danfoss A/S",
                  "friendlyDescription": "Thermostat connected via Danfoss",
                  "modelName": "",
                  "deviceType": "CLOUD_DISCOVERED_DEVICE",
                  "version": "0",
                  "friendlyName": "OG Bad",
                  "friendlyNameModifiedAt":<PHONE_NUMBER>839,
                  "capabilitiesModifiedAt":<PHONE_NUMBER>839,
                  "ipAddress": "",
                  "port": "",
                  "entityId": "ad1263af-bace-49a9-85ae-ce2eadfd1c64",
                  "applianceNetworkState": {
                    "reachability": "REACHABLE",
                    "lastSeenAt":<PHONE_NUMBER>245,
                    "createdAt":<PHONE_NUMBER>839,
                    "lastSeenDiscoverySessionId": {
                      "value": "c932f1d2-6d13-47fd-b3c9-1e5c19dbb8d9"
                    }
                  },
                  "tags": {
                    "tagNameToValueSetMap": {}
                  },
                  "additionalApplianceDetails": {
                    "additionalApplianceDetails": {}
                  },
                  "firmwareVersion": "0",
                  "actions": [],
                  "capabilities": [
                    {
                      "capabilityType": "AVSInterfaceCapability",
                      "type": "AlexaInterface",
                      "version": "3",
                      "interfaceName": "Alexa"
                    },
                    {
                      "capabilityType": "AVSInterfaceCapability",
                      "type": "AlexaInterface",
                      "version": "3",
                      "properties": {
                        "supported": [
                          {
                            "name": "temperature"
                          }
                        ],
                        "proactivelyReported": true,
                        "retrievable": true,
                        "readOnly": false
                      },
                      "interfaceName": "Alexa.TemperatureSensor"
                    },
                    {
                      "capabilityType": "AVSInterfaceCapability",
                      "type": "AlexaInterface",
                      "version": "3",
                      "properties": {
                        "supported": [
                          {
                            "name": "targetSetpoint"
                          }
                        ],
                        "proactivelyReported": true,
                        "retrievable": true,
                        "readOnly": false
                      },
                      "interfaceName": "Alexa.ThermostatController"
                    },
                    {
                      "capabilityType": "AVSInterfaceCapability",
                      "type": "AlexaInterface",
                      "version": "3",
                      "properties": {
                        "supported": [
                          {
                            "name": "connectivity"
                          }
                        ],
                        "proactivelyReported": true,
                        "retrievable": true,
                        "readOnly": false
                      },
                      "interfaceName": "Alexa.EndpointHealth"
                    }
                  ],
                  "applianceTypes": [
                    "TEMPERATURE_SENSOR",
                    "THERMOSTAT"
                  ],
                  "isEnabled": true,
                  "aliases": [],
                  "connectedVia": "",
                  "alexaDeviceIdentifierList": [],
                  "applianceKey": "ad1263af-bace-49a9-85ae-ce2eadfd1c64",
                  "identifiers": {
                    "networkInterfaceIdentifiers": []
                  },
                  "applianceDriverIdentity": {
                    "namespace": "SKILL",
                    "identifier": "eyJza2lsbElkIjoiYW16bjEuYXNrLnNraWxsLmE5Y2U3ZjU4LTZkZjAtNDAwMi1hOTMzLTM5OTI3MjhmYTBmYSIsInN0YWdlIjoibGl2ZSJ9"
                  },
                  "ipaddress": "",
                  "applianceLambdaControlled": true,
                  "mergedApplianceIds": [
                    "SKILL_eyJza2lsbElkIjoiYW16bjEuYXNrLnNraWxsLmE5Y2U3ZjU4LTZkZjAtNDAwMi1hOTMzLTM5OTI3MjhmYTBmYSIsInN0YWdlIjoibGl2ZSJ9_Room:7"
                  ]
                }

@patrickkuhl thanks for providing the additional logs! I will work on adding support for this and let you know once it can be tested.

Since v2.2.0 of this plugin included significant changes, please reopen a new issue with debug logs if this is still a problem.


[Transition] Document the grouping feature

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Summary 💡
It will be nice to have something like the AnimatePresence of Framer Motion for Material-UI transitions.
This component creates a copy of the component after unmount. Then it animates the component unmount, and then it deletes the copy.
Motivation 🔦
When I have a list of components and I remove an item, I want to animate the unmounting process with a Material-UI transition.
If the list is being modified in different parts of the program, to create a timeout for animating, and then removing objects can get messy. Therefore, the approach of AnimatePresence that creates a copy of the component until the transition is done, is a cleaner approach for me.

@cjoecker From what I understand, this is the purpose of this component: https://reactcommunity.org/react-transition-group/transition-group.

@oliviertassinari you are right. The problem with the react-transition-group is that I need to use CSS for the animations. To animate the height with CSS is a headache as you can see here.
That's why I love to use the Collapse component of Material-UI. But it doesn't work with react-transition-group :(

@oliviertassinari you are right, thanks!
I just realized I can use the Collapse Material-UI component with the react-transition-group library :)
Somehow the animation is not working with the Collapse component when I mount a new item. It works only for unmounting.
With Zoom component is working for mounting and unmounting.
Is it a Bug in the Collapse component?
You can check here the codesandbox.

@cjoecker Yeap, my version:
import * as React from "react";
import { makeStyles, createStyles, Theme } from "@material-ui/core/styles";
import { TransitionGroup } from "react-transition-group";
import Paper from "@material-ui/core/Paper";
import Box from "@material-ui/core/Box";
import Collapse from "@material-ui/core/Collapse";

const useStyles = makeStyles((theme: Theme) =>
  createStyles({
    root: {
      height: 300
    },
    container: {
      display: "flex",
      justifyContent: "space-around",
      height: 120,
      width: 250
    },
    halfWidth: {
      width: "50%"
    },
    paper: {
      margin: theme.spacing(1)
    },
    svg: {
      width: 100,
      height: 100
    },
    polygon: {
      fill: theme.palette.common.white,
      stroke: theme.palette.divider,
      strokeWidth: 1
    }
  })
);

export default function SimpleCollapse() {
  const classes = useStyles();
  const [item, setItem] = React.useState(0);

  console.log("item", item);

  React.useEffect(() => {
    const internval = setInterval(() => {
      setItem((item) => (item + 1) % 2);
    }, 2000);

    return () => {
      clearInterval(internval);
    };
  }, []);

  return (

        <TransitionGroup>
          <Collapse key={item} in>
            <Paper elevation={4} className={classes.paper}>
              <Box sx={{ p: 2 }}>{item}</Box>
            </Paper>
          </Collapse>
        </TransitionGroup>

  );
}

@cjoecker Do you want to update the documentation to mention the grouping feature?

@oliviertassinari  Sure, I can do it :)


DEVPROD-5460: Update GraphQL queries to use specific arguments

DEVPROD-5460
Description
Uses the new GraphQL arguments.
I'm going to temporarily support both ID and repoID for the RepoSettings and RepoEvents queries, because I noticed a weird bug where the directive didn't behave as expected (even after making updates in the backend) and I was able to bypass restrictions as a regular user. I'll have to update the directive in the backend anyways, so I'll do that after this PR is merged.
Testing

Since I changed the definition of FormToGql for project settings, I updated transformers tests

tested on beta, should be non-breaking I think


fix: no longer download automatically from share links

Closes https://github.com/datadryad/dryad-product-roadmap/issues/3411

I've deployed this branch on production


Changed Query

@soichih I have been trying different query combinations. However, for these projects ( https://brainlife.io/project/6047cd06ebfe45c5c93a9a67
and https://brainlife.io/project/5fe56eca57aacdb8482fd198 ) the output has at least 1 same related paper.
Please try the above changes. Also, please suggest how can I improve the search query.
What other fields apart from neuroscience and neuroimaging I can include in the query to narrow or broader the results?

Can you remind me why we stopped using the interpret API to generate MAG query from user input?


minor: fix example in docstring, use np.ceil instead of math.ceil

The example was still in Matlab syntax. I fixed it to work in Python.
Furthermore, the module imported math for its ceil function and numpy ... I dropped math and use np.ceil instead.

Apart from my minor comment, +1 for merge.

Thanks @sappelhoff! Regarding the import in the example, could anyone else confirm that we want to have it (e.g. for doctest) or that we don't need it?

yup, just removed it (again) ... to be honest, I just added it in an attempt to fix the
Expected:
    array([ 36, 260], dtype=int64)
Got:
    array([ 36, 260])

but apparently it didn't do anything.

Weird. It seems like output formatting differs between platforms/versions/etc., but now only one Travis job fails:
Expected:
    array([0.36900026, 1.76007351])
Got:
    array([ 0.36900026,  1.76007351])

One possible hack would be to convert the array to a list:
>>> peak_mags.tolist()
[0.36900026, 1.76007351]

Ugly, but it works.

What about dropping the doctest and reverting it to a normal example? Now there are differences in displayed digits after the comma...

let's try this one last time with the expected number of floating points ... if that doesn't work, we can remove the doctest and I'll check how to format the example as a non-doctest example ...

I don't know, comparing floats is always not a good idea. Usually, we would use np.allclose to compare two arrays with a certain tolerance.

You can also try using # doctest: +NORMALIZE_WHITESPACE to take care of the whitespace problem when printing ndarray, it might work. If that didn't, you could do # doctest: +SKIP to avoid running the line at all. But it looks like whatever you did might already make it pass.

okay, they passed ... let's break it again with trying # doctest: + NORMALIZE_WHITESPACE

mmmh broken again. Did I use the NORMALIZE_WHITESPACE incorrectly? Otherwise, I'd try the +SKIP next.

The problem is that you don't have any whitespace in the expected output, so this parameter does not work because it matches any sequence of whitespace in the expected output to any sequence of whitespace in the actual output (https://docs.python.org/3/library/doctest.html#doctest.NORMALIZE_WHITESPACE). There is not whitespace in front of the first element in the expected output, so this can't be matched. Also, you have the dtype issue on AppVeyor again.
You can either revert to the previous commit and hope that this never breaks, or just skip the doctest business completely here.

So with this extensive skipping, it's working. It looks bad but at least there is an example.

Yes, it's not pretty. You could also remove these four lines that you skip, because we don't have to show expected results if they are not tested. If you want to leave it in, I'm fine with that too. Either way, +1 for merge.


[BUG] do not save window for tree-like plugins

Describe the bug
I'm using nvim-tree.lua plugin and when exit vim with the tree window (on the right side) open and then open the vim again the plugin opens the same window for the tree but it's blank. I don't think it's necessary to save tree-like plugin windows.
To Reproduce
Steps to reproduce the behavior:

install nvim-tree.lua plugin
open vim, open tree window, open another file
exit vim
open vim

Expected behavior
no window for tree-like plugin windows

Hi, this is not really an issue with auto-session. You'll find that even if you save and restore sessions manually yourself, these plugins tend to not be savable to a session.
There are closed issues about using the plugin's hooks to close those windows before saving the session you might want to check out.
https://github.com/rmagatti/auto-session/issues/50

Non of solutions in the referenced issue works for now. Nevertherless I used other plugins on old vim that handled this automatically.

Sorry to hear that @im-n1.
I'd be happy to reopen this and help you debug through why the hooks don't work for you!
I'm just not particularly interested in building support directly into the plugin to interface with tree-like plugins as then I'd need to theoretically support a potentially unlimited number of tree-like plugins. So the approach I went with here is to have customizable hooks anyone can use to tweak behaviour that interfaces with other plugins themselves. I realize this approach leans towards the more generalized and perhaps less convenient side of things, but it also makes sure I'm not spending too much time trying to keep up with every tree-like plugin out there and instead am focused on session related features.
I hope that makes sense.
Thanks again for the issue submission, let me know if you'd like help with debugging your hooks!
Cheers!

Just a note, I also made a PR to fix this upstream in nvim-tree, which should work for all sessions, as it restores the nvim-tree after a SessionLoadPost event. I think this is ultimately the solution that needs to happen, but that plugin should work in the meantime!


Plays multiple instances of video - you can hear many audio tracks being played in the background

You hear the video playing multiple times automatically in the background .

Are you running the app on simulator or real device?

Thank you for the latest update. It fixes the issue.


[bug]: send assets blocks

Background
Call "send assets" rpc blocks when there is a pending "send assets"
Problems
but it still blocks after the pending tx was confirmed.
I found that tapd and lnd  are waiting a unboardcast tx (transfer_txid=99fa8693f02cbb1a3e4799ef20de71436bd23a33ef44a41b4fcf7edc4a5559ff)
testnet tx url
https://mempool.space/testnet/tx/99fa8693f02cbb1a3e4799ef20de71436bd23a33ef44a41b4fcf7edc4a5559ff
Bug
I'm wondering if in this situation, the transaction was recorded in the database by its txhash before it was successfully broadcasted.
Logs in tapd daemon
2023-09-05 08:40:23.641 [INF] RPCS: Starting RPC Server
2023-09-05 08:40:23.641 [INF] RPCS: RPC server listening on <IP_ADDRESS>:10029
2023-09-05 08:40:23.642 [INF] CONF: Starting HTTPS REST proxy listener at <IP_ADDRESS>:8089
2023-09-05 08:40:23.642 [INF] RPCS: gRPC proxy started at <IP_ADDRESS>:8089
2023-09-05 08:40:23.642 [INF] SRVR: Taproot Asset Daemon fully active!
2023-09-05 08:40:27.016 [WRN] FRTR: No response channel for resumed parcel, not delivering notification
2023-09-05 08:40:27.016 [INF] FRTR: ChainPorter executing state: SendStateWaitTxConf
2023-09-05 08:40:27.016 [INF] FRTR: Waiting for confirmation of transfer_txid=99fa8693f02cbb1a3e4799ef20de71436bd23a33ef44a41b4fcf7edc4a5559ff

Logs in lnd daemon
2023-09-05 08:38:39.654 [INF] BTCN: Verified 1 filter header in the last 58.54s (height 2476455, 2023-09-05 08:38:31 +0000 UTC)
2023-09-05 08:38:39.956 [INF] NTFN: New block: height=2476455, sha=000000000000001a32b8eecf638378379eca1e501fb983adeb29f130e47abfbd
2023-09-05 08:38:39.956 [INF] UTXN: Attempting to graduate height=2476455: num_kids=0, num_babies=0
2023-09-05 08:38:45.629 [INF] BTCN: Lost peer <IP_ADDRESS>:18333 (outbound)
2023-09-05 08:40:16.873 [INF] RPCS: Canceling transaction subscription
2023-09-05 08:40:16.873 [INF] NTFN: Canceling confirmation notification: conf_id=1, txid=99fa8693f02cbb1a3e4799ef20de71436bd23a33ef44a41b4fcf7edc4a5559ff
2023-09-05 08:40:22.010 [INF] RPCS: New transaction subscription
2023-09-05 08:40:22.012 [ERR] RPCS: [/walletrpc.WalletKit/ImportTapscript]: error importing script into wallet: address for script hash/key 23e0c0eb20f5bc5a37b52e3330808f78d7dfa82ae2c0ba000360551a045bf707 already exists
2023-09-05 08:40:27.017 [INF] NTFN: New confirmation subscription: conf_id=2, txid=99fa8693f02cbb1a3e4799ef20de71436bd23a33ef44a41b4fcf7edc4a5559ff, num_confs=1 height_hint=247645

Not sure. I would avoid shutting down tapd while there are still unconfirmed send requests going on, as it looks like it blocks on startup.

If there are 3 utxo in my lnd daemon,


Indentation in if and case expressions

Consider this snippet:

what = if foo
  42
else
  'doh!'
end

I get:
C:  2:  3: Use 2 (not -5) spaces for indentation.
W:  5:  1: end at 5, 0 is not aligned with if at 1, 7
This other snippet, on the other end, is considered good by rubocop:

what = if foo
         42
       else
         'doh!'
       end

To me, this second sample is just crazy; also, almost no editor will accept to indent code at column 7.

using
Lint/EndAlignment:
  AlignWith: variable

but still getting:
lib/rspec-rerun/tasks.rb:31:13: C: Use 2 (not -5) spaces for indentation.
            opts
            ^^^^
lib/rspec-rerun/tasks.rb:32:11: C: Align else with if.
          else
          ^^^^

on
opts = if opts.is_a? Hash
  opts
else
  { retry_count: opts }
end

any idea what I could do ?

@grosser Run rubocop --debug lib/rspec-rerun/tasks.rb and check if you're really getting configuration from the file where you have set
Lint/EndAlignment:
  AlignWith: variable

because the ElseAlignment and IndentationWidth cops both look at the EndAlignment configuration and should not report offenses in your case.

thanks, that worked ... an inherited file had
Lint/EndAlignment:
  Enabled: false


Change constant current calibration to not use a load resistor

I've tweaked how the constant current calibration works. It no longer uses a load resistor and instead you short the output terminals. This is effectively the equivalent of the open circuit calibration routine for the voltage but for current
This means it now can sweep the entire current range giving a greater degree of accuracy

As you can see here we have the entire range available as calibration data:

It now also uses the A_ADC to determine the output current used instead of the V_ADC. This will remove any potential errors that were introduced by #7
This has now made my device incredibly accurate

Looks promising! I am somewhat curious as to where the current goes? Is it dumped into GND? Could a hardware change not make the DPS suddenly costume the 5A?

If you have a look at the second graph the DPS is passing through 5A. This might make it a bit clearer:

If you think about it whatever the load resistor is (ideally shorted ~0 Ohms in this calibration mode) then the DPS will always be sinking that full current to ground. The hardware is designed to allow this so it will be safe to do so


Your session has expired. Please login again.

Your session has expired. Please login again.

Is this happening while you try to use the link made from the "singlesignon" token? If so, I'm having that problem too

I can get the SSO token and everything looks fine, but when I try to use the link it says it's expired. I set the expiry to 30 minutes, and tried setting the IP address as <IP_ADDRESS> and as my computer's public IP address

The workaround for my problem after asking support was to update the password on the user (even if it is the same password). So I needed to add an extra edit user API call before using the SSO link.
It's strange that it fixes it, but I'll take it.

Any solution for this ?
I am stuck here

Same problem here! And the solution @etetland-va provided is not working for me. Any solution?

This error message is also used if the IP address does not match.
I have a server configured only use IPv4, and it signs tokens with an IPv4 address. If an IPv6 user accesses my server using an IPv4 translation service, they will get a token but be unable to use it.


Debugger Fixes for Godot 4.0

This is a continuation of #400 by @RedMser.
Current state:

The main thing holding this back, besides some issues with the debugger, is compat with 3.x.
Keeping compatibility with multiple Godot versions will probably double the size of this PR, due to having to create duplicates of every system (debugger, connection, etc.) which must be interchangeable. Not to speak of automatic version detection, which I'm not sure how it should be done just yet.

I'm opening this as a draft PR so I have a place to keep some notes.

Wow, I wasn't lying when I said was barely git-literate. I have no idea how I managed to create this PR against the wrong repo!


Edge TPU example

Hello Zigzag team,
I'm going through the Edge TPU example and trying to understand the details of the hardware-arch/mappings in Zigzag. I have a couple of questions on that.
I'm using this mapping found by Zigzag for Layernode 13 of Resnet-18. Edge_TPU-resnet18-layer_LayerNode_13_complete.json With that, I created the following nested loops based on my understanding of the loop ordering/blocking found by Zigzag. The _s loops correspond to the spatial mapping and will be unrolled if in an HLS setting. I also commented the memory hierarchy next to the highest-level loop each one serves.

Based on the hardware architecture description, this is what I think it should look like:

(1). Is this understanding of the Zigzag outputs correct?
(2). In the .json file, temporal mapping for each operands has N values (each value then contain some loops and their sizes). N seems to correspond to the number of mem hiers for that operand. Is this correct? If so, why does the spatial mapping have N+1 values?
(3). Based on what's generated, I understand that for the RF_1B for weights, it is essentially a register for the single weight spatially reused by each 4x4 MAC array unit. However, I don't understand the reuse pattern for RF_2B for outputs. It seems to me that C (input channel) is unrolled so that outputs can be accumulated across input channels and stored in RF_2B, but RF_2B is only large enough to store 1 output, so it has to be constantly updated. Am I missing something?
(4). In Edge TPU example, lines 29-41, the RF_2B is defined as size 16 with two read ports and two write ports, could you explain what this is trying to describe? It seems to me that this is just a 16b register (in FFs). Why would it have 2 ports for read and write?
Sorry for the long post and thanks in advance for your time!

Hi, thanks for your questions and apologies for the delay in response.

Yes, your understanding is correct.
N is indeed the number of levels in the memory hierarchy for that operand. Spatially there is an additional bottom-most level which represents the unrolling of the MAC itself.
Your drawing is correct for the W RF, however it's incorrect for O. Let me call the RF for output RF_O. Your drawing represents the served_dimensions = {(0, 1, 0, 0), (0, 0, 1, 0), (0, 0, 0, 1)} for RF_O, as one RF_O is serving all MACs across D2, D3, D4. In the actual memory hierarchy definition, a single RF_2B is only serving D2, and as such there will be D1 * D3 * D4 instances across the entire hierarchy. This is difficult to visualize, as there are 4 dimensions which in your drawing you have flattened to 2. Depending on the temporal mapping, it is possible that the same output can be reused.
I think you're correct that RF_O doesn't need 2 read and 2 write ports. @LY-Mei any thoughts on this?

Let me know if you have additional questions!
Kind regards,
Arne

Arne,
Thanks for getting back to me. I think I understand now. I somehow missed that RF_2B is only serving D2 so there are a lot more instances than I initially thought. An updated visualization would maybe look something like this?

Best,
Siyuan

Yes, your new visualization is more accurate. Each RF_2B (O) will be serving across dimensions D1, D3 and D4, so in total there will be D1D3D4 instances in the entire hierarchy. Also keep in mind that in a real architecture you would have some form of reduction (adder tree) from those MACs to the RF for output, which is abstracted out in ZigZag. The write bandwidth of the RF will determine the amount of outputs that can be reduced in a single clock cycle and will limit the spatial unrolling onto the physical dimensions accordingly.


[HUDI-1611] Added a configuration to allow specific directories to be filtered out during Metadata Table bootstrap.

What is the purpose of the pull request
During the bootstrap of the Metadata Table, all the directories which contain the partition metadata directory are assumed to be partitions and are added to the metadata table.
In our HDFS clusters, we have directories like .backup, .temp which are used by various teams for non-hoodie purposes (e.g. .backup may be keeping a snapshot of the dataset). During bootstrap, Metadata Table ends up containing all those paths also as partitions.
In this patch, I would like to introduce a configuration for HoodieMetadataConfig to filter out some directories based on a regular expression string.
Brief change log
Added a config to HoodieMetadataConfig.
Added a unit test.
Verify this pull request
This change added tests and can be verified as follows:
Extended the unit test TestHoodieBackedMetadata#testOnlyValidPartitionsAdded
Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Codecov Report

Merging #2565 (6cb664d) into master (26da4f5) will decrease coverage by 1.81%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master    #2565      +/-   ##
============================================
- Coverage     50.92%   49.10%   -1.82%
+ Complexity     3168     2819     -349
============================================
  Files           433      378      -55
  Lines         19812    16948    -2864
  Branches       2033     1714     -319
============================================
- Hits          10090     8323    -1767
+ Misses         8902     7967     -935
+ Partials        820      658     -162

Flag
Coverage Δ
Complexity Δ

hudicli
36.90% <ø> (ø)
0.00 <ø> (ø)

hudiclient
100.00% <ø> (ø)
0.00 <ø> (ø)

hudicommon
51.36% <0.00%> (-0.03%)
0.00 <0.00> (ø)

hudiflink
43.21% <ø> (ø)
0.00 <ø> (ø)

hudihadoopmr
33.16% <ø> (ø)
0.00 <ø> (ø)

hudisparkdatasource
?
?

hudisync
?
?

huditimelineservice
?
?

hudiutilities
69.46% <ø> (-0.06%)
0.00 <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ
Complexity Δ

...pache/hudi/common/config/HoodieMetadataConfig.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

...apache/hudi/utilities/deltastreamer/DeltaSync.java
70.50% <0.00%> (-0.36%)
50.00% <0.00%> (-1.00%)

...main/java/org/apache/hudi/hive/HiveSyncConfig.java

...udi/timeline/service/handlers/BaseFileHandler.java

...in/java/org/apache/hudi/hive/SchemaDifference.java

...di/timeline/service/handlers/FileSliceHandler.java

...va/org/apache/hudi/hive/util/ColumnNameXLator.java

.../src/main/java/org/apache/hudi/dla/util/Utils.java

...in/scala/org/apache/hudi/HoodieEmptyRelation.scala

...src/main/scala/org/apache/hudi/DefaultSource.scala

... and 47 more

@nbalajee Can you review this ?

@nbalajee Can you review this ?

Reviewed the changes.  LGTM.

LGTM.

just curious. actual bootstrap should have some config on these lines right? while bootstrapping data to hudi, filter directories based on some predicate. can't we reuse the same?
CC @bvaradar @n3nash

@prashantwason can you take care of @nsivabalan comment and concern, we can merge then.

just curious. actual bootstrap should have some config on these lines right? while bootstrapping data to hudi, filter directories based on some predicate. can't we reuse the same?
CC @bvaradar @n3nash
I did not find any such config in HoodieBootstrapConfig. I feel keeping it separate may be better:

so as to not be confusing the two features which work independently (also the configs in bootstrap have a prefix hoodie.bootstrap)
building the HoodieWriteConfig will be awkward with having to provide a HoodieBootstrapConfig when enabling Metadata Table


django 1.7?

The docs still list django 1.7 as the max.  Does this support newer versions?  If so, can you update the readme to the latest tested.  If not, what's the rub?

Yes, it should also work with django 1.8.x and 1.9.x. The README has been updated to reflect this.


WIP Transfers EC.Labels and EC.Annotations to the POD spec

Description
How can this be tested?

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 64.50%. Comparing base (2904e52) to head (3cc39af).
Report is 4 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4153      +/-   ##
==========================================
+ Coverage   64.48%   64.50%   +0.01%
==========================================
  Files         399      399
  Lines       26766    26778      +12
==========================================
+ Hits        17260    17272      +12
  Misses       8145     8145
  Partials     1361     1361

Flag
Coverage Δ

unittests
64.50% <100.00%> (+0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Inconsistant behavior of renderers.

Behavior 1:

Open VAPOR, load DUKU, create a barb renderer.
Enable it, you see 16 barbs on the screen.
This is behavior 1.

Behavior 2:

Open VAPOR, load Katrina.
Close Katrina.
Load DUKU, create a barb renderer.
Enable it, you see nothing on the screen.
This is behavior 2.

I believe there shouldn't be a discrepancy between behavior 1 and 2.

Duplicate of #479

Update on 12/20: This bug stays the same, and seems quite different issue #479 . Not sure why it was labeled Duplicate. @sgpearse

No longer relevant.


Update Simplified Chinese Translation

88ad94a src/drivers/webextension/_locales/zh_CN/messages.json
Based on merged pr #2887

Thanks!


fixed compatibility with sylius 1.0.0

strict type hinting from interfaces, updated form type class

Thanks for the help :)


How?

No Duplicate...
How can i make the players
dont earn mass by 35 massed bots?
Ex : 10 massed bots (Cant earn mass in 600+)
What i want : 35+ mass (Cant earn mass in 600+)

The size is here. Change 41 (17 in mass) to your desired size.  You can figure out what 35 in size is by using the calc command. Or if you don't feel like doing that you could just replace prey._size <= size with prey._mass <= mass


Cleanup and clarify recurrences src / Fix #100

I am working on functionality that given a dynamical system it animates the action of AttractorsViaRecurrences. I will contribute this in a separate PR, but I am doing pretty good, here is where I am now:
https://github.com/JuliaDynamics/Attractors.jl/assets/19669089/d4e856fe-85da-473d-b00b-10f8211c9740
During this journey, I had some problems with our source code. I admit, I find it surprising how difficult the source code is to read, given the success of the algorithm.
In this PR I do the following:

Re-organize the source code more logically
Re-named many variables and functions so that they better convey what they do. E.g., visited_cell was a poor name. It contained the (default) label that visited cells obtain. You'd think it would contain a cell (i.e., a cartesian index instead). A better name is visited_cell_label. Etc.
Fix #100
Add many more comments to the source code to better explain things

oooof oh boy this is finally done. Took me quite a while to go through the source code and really clarify things as much as possible.
@awage or @kalel can you please review and leave an Approving review if you don't find anything wrong so that I can merge this in? This PR does not alter any functionality, it only re-wrote the source code to be more readable.

Hi! I will review the code today and leave some comments if any.

I am done with the review. There is the function update_fsm_state! that should be changed. I will think about a better way to write this function.

Thanks @awage. I have addressed all comments. Please leave an approving review (by clicking review, and then selecting approve), if you think this should be merged.

Codecov Report

Merging #101 (0fd57db) into main (8171746) will increase coverage by 0.05%.
The diff coverage is 91.66%.

@@            Coverage Diff             @@
##             main     #101      +/-   ##
==========================================
+ Coverage   84.27%   84.32%   +0.05%
==========================================
  Files          20       22       +2
  Lines        1151     1155       +4
==========================================
+ Hits          970      974       +4
  Misses        181      181

Files
Coverage Δ

src/continuation/continuation_recurrences.jl
79.31% <ø> (ø)

src/mapping/attractor_mapping.jl
80.95% <ø> (ø)

.../mapping/grouping/attractor_mapping_featurizing.jl
62.29% <ø> (ø)

src/mapping/recurrences/sparse_arrays.jl
70.58% <100.00%> (ø)

src/mapping/recurrences/grids.jl
96.59% <96.59%> (ø)

src/mapping/recurrences/finite_state_machine.jl
94.40% <94.40%> (ø)

...pping/recurrences/attractor_mapping_recurrences.jl
82.14% <82.14%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[BUG+REQ]: subtitles menu

We have

but if you choose all or none they should exclude each other.
Plus: is there any way to remember sub selections?

Plus: is there any way to remember sub selections?
Yes, set it in cli-default.yml

Yes, set it in cli-default.yml

Thanks.
I can't find reference to the options:
q: 0
nServer: 1
mp4mux: false

Where I can find reference?

https://github.com/anidl/multi-downloader-nx/blob/master/docs/DOCUMENTATION.md#--dlsubs
You would have it set like this:
dlsubs: ["en", "es-ES"]

I meant the 3 options I quoted as code.

ah, gotcha. "nServer" doesn't do anything anymore, it's essentially the "x" flag. "mp4mux" was also replaced by just "mp4", and "q" does exist, it's for quality selection: https://github.com/anidl/multi-downloader-nx/blob/master/docs/DOCUMENTATION.md#-q

So, should I edit and/or delete those lines?

You don't have to, you can ignore those and they just won't do anything


has_many :through relationships?

We're trying to use cocoon to support the following relationship:
Product has_many :product_people
Product has_many :people, :through => :product_people
ProductPerson belongs_to :product
ProductPerson belongs_to :person
Person has_many :products, :through => :product_people

Now, the idea is that when creating a new product, we're trying to manage people, by adding more people and managing their titles.etc.
However, something appears to be not working her with cocoon. I can see that it's meant to look for something like _new_person or whatever, but instead of that we're seeing _0_person and I'm sure this is because of the partials and the arguments we're sending to cocoon helpers. However, I don't see a way around this. In the view we have:
= f.semantic_fields_for :product_people do |pp|
	= render 'person_fields', :f => pp
		%li
			Bio and details can be added after the film is accepted.
			.links
				= link_to_add_association 'Add person', pp, :person, :id => 'addRole'

I have tried changing the link_to_add_association by passing in "f" instead of "pp", but that just gives me ruby errors. How I see it - we appear to have done everything correctly, but this level of depth isn't supported?

just a note that the local variable representing form MUST be named :f.  Took me a long time to figure this out.

Uhm, there is no such dependency afaik. All my examples are created with f but you give the form name to the link_to_add_association or link_to_remove_association.
Would you mind creating a separate issue for this?

thanks, i did so here https://github.com/nathanvda/cocoon/issues/286


Replace Gurobi classical optimizer with SCIP open-source solver?

Gurobi is a commercial software for optimization problems and it requires a license to run (freely available for a limited period of time, should be 18 months from the installation) even for the basic version which scales up only to something around 200 variables.
At the moment, QUnfold is using the Gurobi Python API (see gurobipy) to implement a Gurobi-based classical solver as a state-of-art benchmark for classical optimization (both for integer and binary variables models). However, it would be better to provide an open-source and non-commercial alternative for the same purpose, in order to have full knowledge and control on what is happening under-the-hood when needed.
One possibility would be to adopt the SCIP (Solving Constraint Integer Programs) software which offers a Python interface as well (see PySCIPOpt docs). A bit of work would be required to move from Gurobi to SCIP but I don't see any potential issue in the migration.
Maybe @carlasophie can help us here.

By the way, I just found out that also Qiskit is providing a sort of wrapper for both the Gurobi and the IBM Cplex classical solvers within their qiskit-optimization package (see here).


[V5] Win64 - Wallet connection issue

The new wallet still doesn't connect to the peers, whereas the old wallet, after downloaded the newly updated blockchain, now sync faster, but after synced the (old) wallet doesn't open as expected and it says 'rescanning...'
I can't use both wallets
The OS is Windows 64 bit.
P.S. @marpme Why have you closed the issue that I opened a couple of hours ago, when:

No one answered it nor solved it.
Why you closed it without say anything?!

Show some respect.

The old 4.x and new 5.x create different types of files/structure locally on your computer  in your datadir.
Unless you are running each verge-qt.exe with a different datadir for each different version, you will probably run into weird problems having both versions in the same datadir.
I would focus on 1 problem..
-get 4.0 to work
-get 5.0 to work
Either way the first step would probably be the same .. wipe out everything in datadir except wallet.dat would be a good start, and re-load the correct bootstrap.

I am the average Joe.
Where is datadir located? I went to User/Name of the User/AppData/Roaming/Verge.
Have not found it there. Though I found wallet.dat
what does re-load the correct bootstrap mean?

Well,
First, there's no issue that you opened a couple of hours ago from your username in this repository, if you opened in another repository, sorry that you didn't get feedback on it but we got to filter the issues and when you open up a repository it clearly describes what's about. So I'd leave an apology to @marpme here.
@jrsikors suggested that you have at least one wallet to work. Let's start out with the v5 which looks like is giving you a headache.
Start by downloading a copy of the blockchain from here : https://verge-blockchain.com/
While downloading, let's continue
If we assume you want to run both wallet versions, you'll have to create a different datadir for the v5 wallet, you just can't have v4 and v5 run on the same data directory. Let's keep the v4 as is.
I suggest you to create a datadir named Verge5 in the same directory where Verge is, and change the shortcut to the wallet (on your Desktop I suppose) by adding the following parameter :
c:\users\kevin\Desktop\verge-qt.exe -datadir=C:\Users\Kevin\AppData\Roaming\Verge5
You can have more instructions here about that point  : https://bitzuma.com/posts/moving-the-bitcoin-core-data-directory/
Try opening up the wallet, you'll have a first launch experience. When done close it. Now, extract the blockchain archive that you downloaded earlier to a folder, and copy-paste the whole content in the Verge5 directory, ensuring that you overwrite what's already there (besides the wallet.dat).
Open up the wallet again, and it 10 minutes you should be done.
If you're not getting connections, you can copy-paste the list of servers from this file :
https://github.com/vergecurrency/VERGE/blob/0d669aab902c12c97cd8beabe8151b3e26f3f3b8/doc/peers.txt
--
Please be aware that our community and core team is volunteer-based. Nobody is paid, nor works full time with Verge. Consider being respectful and polite while opening an issue. No need to use CAPS LOCK TO WRITE A TITLE, neither being rude to the team members.
We will help you, we're here for that.
If this answer helped you, consider donating to the team : https://vergecurrency.com/donate/

if you have coins in your wallet .. make sure you have a backup of your wallet.dat on a USB drive or another computer before doing any of this (you should already have one anyways 💯 ) from User/Name of the User/AppData/Roaming/Verge

and for QT 101... inside your data directory:
User/Name of the User/AppData/Roaming/Verge
You should see a bunch of files and folders.  There are a few key ones:
-wallet.dat = your wallet
-peers.dat = file containing other peers in the verge network
-debug.log = debug log
some folders like /chainstate/ /blocks/ , maybe a blkindex.dat ... this is the blockchain you've downloaded.
so essentially to nuke it and start over, you just want to delete everything inside your User/Name of the User/AppData/Roaming/Verge folder EXCEPT wallet.dat.
the next time you start verge-qt , it will re-create all the files needed and start re-downloading the blockchain.
Manuel's method is the exact same (new/empty data directory), but it's safer because you aren't "deleting" anything.  But i like to live life on the edge 😀
once you get to that point -- and you run 5.x verge-qt --  if you still have peers issues -- we should be able to help easily with that... but need to see if you even need help after doing that stuff

Jeez bro you on fire @jrsikors

I deleted all the files expect the Wallet.dat.
I started Verge-qt and the deleted files came back.
Still blockchain is stuck with no connection to peers.

go to Help -> debug -> console
type:
addnode add "otcwkocmpptqadjc.onion"
hit enter
addnode add "vav7wo53kmlmxm4b.onion"
hit enter
give it a few minutes and see if they show up.  I'm not in front of QT right now but I think that's the right command to add a node.

I deleted all the files expect the Wallet.dat.
I started Verge-qt and the deleted files came back.
Still blockchain is stuck with no connection to peers.

Have you done the whole process I suggested ?

This is the result from adding nodes:
|   | otcwkocmpptqadjc.onion
| Method not found (code -32601)
| vav7wo53kmlmxm4b.onion
Method not found (code -32601)

Maybe put add in quotes as well: “add”
-Jeff

On Jun 11, 2019, at 1:34 PM, kevintenda<EMAIL_ADDRESS>wrote:
This is the result from adding nodes:
|   | otcwkocmpptqadjc.onion
| Method not found (code -32601)
| vav7wo53kmlmxm4b.onion
Method not found (code -32601)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@2lazy2debug  I tried but couldn't finish it.
Thinking of delete all the blockchains and wallets and start over.  What do you think? I just need one running wallet.
Already have the backup. Money are safe.

I tried this way
"add otcwkocmpptqadjc.onion"
And this  "add" "otcwkocmpptqadjc.onion"
Same code error

Set add after node.. < addnode NODE add >

Should give an empty reply, or error if already added

thanks, @cod3gen , sorry not at my computer and didn't have time to google yet.. was about to.  that's what i was missing
so
addnode node "otcwkocmpptqadjc.onion" add
addnode node "vav7wo53kmlmxm4b.onion" add

@kevintenda did you copy paste the values I linked before? you should have your VERGE.conf file filled with "addnode=mynode.onion"

@cod3gen
You means like this:  "otcwkocmpptqadjc.onion" "add"?

@2lazy2debug I'll try that now.
I have not done it cause I didn't know how to.
I do it now.

you can do this in console as well with these commands:
addnode node "otcwkocmpptqadjc.onion" add
addnode node "vav7wo53kmlmxm4b.onion" add

Doesn't work neither that those peers in the link

you can do this in console as well with these commands:
addnode node "otcwkocmpptqadjc.onion" add
addnode node "vav7wo53kmlmxm4b.onion" add

The response
| addnode "node" "add|remove|onetry"  Attempts to add or remove a node from the addnode list. Or try a connection to a node once. Nodes added using addnode (or -connect) are protected from DoS disconnection and are not required to be full nodes/support SegWit as other outbound peers are (though such peers will not be synced from).  Arguments: 1. "node"     (string, required) The node (see getpeerinfo for nodes) 2. "command"  (string, required) 'add' to add a node to the list, 'remove' to remove a node from the list, 'onetry' to try a connection to the node once  Examples: > verge-cli addnode "<IP_ADDRESS>:21103" "onetry" > curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "addnode", "params": ["<IP_ADDRESS>:21103", "onetry"] }' -H 'content-type: text/plain;' http://<IP_ADDRESS>:20103/  (code -1)
-- | --

Not addnode node...
addnode otcwkocmpptqadjc.onion add
addnode vav7wo53kmlmxm4b.onion add

oh it's just the ordering? 🤕  💩   my bad

Not addnode node...
addnode otcwkocmpptqadjc.onion add
addnode vav7wo53kmlmxm4b.onion add

Now it says null

null is good, just give it a few mins now and see if the peers start connecting / increasing on their own

That means they are now added 👍 try doing the commands again and you should get error instead

Sync Header is moving. Up to 5%

It will take a while to download the whole blockchain,, many hours , so just let it go for a bit.  Manuel earlier suggested downloading the 'bootstrap':

Start by downloading a copy of the blockchain from here : https://verge-blockchain.com/

Basically you can download a zip of the whole blockchain, close down QT client, unzip it to your data directory (overwrite existing files/folders), and then open QT , and you will pretty much be sync'd.
Both ways work, it just depends on whether or not you are feeling patient.  Sometimes downloading the blockchain zip can take hours, so it's easier to just let the chain download 'naturally' like you are doing.

Up to 55%
I got time. Finger cross everything will go smooth.

Last night the wallet has finished to download all the blocks. I launched it today and this is the result:
-It took half an hour to load the blocks and get to the wallet.
-Waited for over an hour for the wallet to connect to the nodes. But nothing.
-I had to add the nodes manually, like I did yesterday, and successfully download the last few blocks.

I might be wrong but I noted that this node - addnode otcwkocmpptqadjc.onion add - might be dead.

I believe the wallet should always connect automatically to the nodes without my intervention. How can we fix this?

Generally peers info are stored into the peers.dat file. however you can be sure to always have an online peer by adding some nodes to the verge.conf file in the datadir folder, as I told you already twice.
just copy paste them from the sample file I provided earlier. at least 10-15 of those nodes are always active.

Generally peers info are stored into the peers.dat file. however you can be sure to always have an online peer by adding some nodes to the verge.conf file in the datadir folder, as I told you already twice.
just copy paste them from the sample file I provided earlier. at least 10-15 of those nodes are always active.

To be more precise the first time you dropped a link with a list of servers and that's it. Haven't really explained it what should I do with it. How to use it. Where to, and so on.
Later on you asked if I added that list on verge.conf... But obviously I haven't done it since your instructions were incomplete, make it hard for me to follow it.
Now, I am looking at datadir folder but there is no verge.conf file. This could explain why I have no nodes.

To be more precise the first time you dropped a link with a list of servers and that's it. Haven't really explained it what should I do with it. How to use it. Where to, and so on.
Later on you asked if I added that list on verge.conf... But obviously I haven't done it since your instructions were incomplete, make it hard for me to follow it.

Didn't notice sorry, could've mentioned earlier.
Instruction on how to create and use the verge.conf file are on the readme in front page of the repo, thus I assumed you knew what I was talking about :
https://github.com/vergecurrency/VERGE#wallets
Create a verge.conf file and just paste the whole addnode=somehting list. You can even use the example file given, just change username and password.

The nodes all disappearing isn't abnormal for Tor.. i always check:
https://verge-blockchain.info/network
and grab a couple of those to add manually.
Not finding any peers happens to me as well, but Marvin and Justin and many many people haven't been able to duplicate the issue.. so it comes down to probably our ISPs.
As for the blocks taking forever to load, that almost sounds computer related.

To be more precise the first time you dropped a link with a list of servers and that's it. Haven't really explained it what should I do with it. How to use it. Where to, and so on.
Later on you asked if I added that list on verge.conf... But obviously I haven't done it since your instructions were incomplete, make it hard for me to follow it.

Didn't notice sorry, could've mentioned earlier.
Instruction on how to create and use the verge.conf file are on the readme in front page of the repo, thus I assumed you knew what I was talking about :
https://github.com/vergecurrency/VERGE#wallets
Create a verge.conf file and just paste the whole addnode=somehting list. You can even use the example file given, just change username and password.

Like I said earlier, in my second post on this page, I am the average Joe, I'll try my best to follow it.
Correct me if I am wrong:

Download the pre-compiled software - I assume download the wallet !?

Install - If it meant the wallet then it's done already

In windows file explorer, open c:\Users\XXX\AppData\Roaming\VERGE (be sure to change XXX to your windows user) - OK

Right click and create a new file verge.txt - I right clicked and then clicked on Text Document and I named it verge.txt

Edit the file to have the following contents (be sure to change the password) - I edited the file as per instruction and gave a random password.

Save and close the file - OK

Rename the file to verge.conf - OK I noted that now I have two files one called verge.txt and the other called verge.conf. Is that right?

Start the VERGE-qt program. OK

Open up VERGE-qt console and run getinfo (or getmininginfo) to verify settings - I am assume after the wallet is open, got to find somewhere a getinfo to verify settings which should be the ones I wrote  on verge.conf.

And finally add the list of the nodes in verge.conf.
Waiting for the wallet to open for the 9th instruction.

Can't find getinfo nor getmininginfo. What is it? Where to find?

The nodes all disappearing isn't abnormal for Tor.. i always check:
https://verge-blockchain.info/network
and grab a couple of those to add manually.
Not finding any peers happens to me as well, but Marvin and Justin and many many people haven't been able to duplicate the issue.. so it comes down to probably our ISPs.

I doubt the issue is the ISP. In my case I can tell that I've been using the wallets for about two years and never had a problem with the nodes. I started to have the problem with this new wallet. At the same time I have another XVG wallet, in my MAC and I don't have any problem with the nodes.
I woldn't say the nodes disappear because this implies they were already there. As I understand my problem was just the lack of nodes, since the day one. That's why blockchain couldn't start.

As for the blocks taking forever to load, that almost sounds computer related.

I mentioned it takes thirty mins to open just to check whether or not that was normal. This pc is old, indeed.

UPDATE:
Since last time I wrote you here I noted two improvements in the wallet:

Now to launch the wallet takes 3-4 mins and not 30 mins as I said before. (no joking)
The wallet is automatically connecting to the nodes, despite the fact I have not added the list of nodes into verge.conf. (not even sure if the way I create verge.conf file is correct, therefore I haven't continued, waiting for a feedback from verge devs).

Can't figure out how that was sorted.
At this point I think the issue is solved and can be closed.
Thanks to @jrsikors @2lazy2debug @cod3gen

Thank you for your valueable feedback, if there’s anything we can help you with. Let us know. Have a great day :)


Store should have a public method to trigger a refilter

Currently if we want a store to be refiltered we would either need to 'setFilter' or 'noteDataUpdated'. There is also a 'rebuildFiltered' method but it is marked as private.
The the problem is one of semantics but probably worth the change. In a client app we have a filter function that does not need to change but a property on a model that is used to do the filter is user settable. We don't want to 'setFilter' over and over with the very same function. We don't really want to call noteDataUpdated because, it hasn't. And we don't want to call a private function.

Seems like we should be able to automatically update the filtered record set via a mobx autorun, that would probably handle the majority of use-cases here with custom filtering controls (though we should also just make rebuildFiltered public - don't see any reason for it to be private)

John -- lets go ahead and take care of this one in this release.  I think publicizing the method makes sense.  Perhaps a rename is in order -- applyFilter()'? refreshFilter() runFilter() ?
Running the filter in an autorun in an interesting idea as well.  Just thinking about the best mechanics for doing that.....


allow a file to be specified by name

On the server side the tag should be given priority, but if none matches but a file name does it should be considered the matching file.

Done in commit 93e1c70ab98b7694c0e1ee7fdaa4fc572612140c.


demo 模拟器编译报错

ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
检查build settings
valid architectures：arm64 arm64e armv7 armv7s
architectures：Stardard architectures
设置应该没有问题

找到类似issue，真机可通过编译，此问题close https://github.com/pili-engineering/PLPlayerKit/issues/375


Compile error: kDynamicsProcessorParam_MasterGain deprecated

For AudioKit 5.2.1:
The flag kDynamicsProcessorParam_MasterGain has been renamed to kDynamicsProcessorParam_OverallGain, which causes a compile error for target iOS 15.
Please update the sources for this.
Thanks!

We don't support beta software and this appears to be an error in Apple deprecation.  Easy enough to change that to the constant. I believe its 6.

Made the change on develop which you should use if you're also on beta iOS. https://github.com/AudioKit/AudioKit/commit/f6ac112ce97092b2394776088edaa39213c2d92d

btw, https://github.com/AudioKit/AudioKit/issues/2568

Hi,
You are right, that changing it for myself is easy enough, but I didn't think that this could be an Apple issue.
Anyway, now you updated it already.
May thanks for your ultra-fast response and support!
Matthias

On 24.08.2021, at 09:38, Aurelius Prochazka @.***> wrote:
btw, #2568 https://github.com/AudioKit/AudioKit/issues/2568
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/AudioKit/AudioKit/issues/2580#issuecomment-904400512, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC5TKG2ADFBKX4BJIG26CCLT6NEATANCNFSM5CWGWMLQ.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email.


Palo Alto Admin UI integration with Azure AD

I configured Azure AD with Palo Alto firewall for accessing web UI but I encounter a problem.
What I did?
I did following link steps in my environment but I get an error when I log in to Firewall
https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/active-directory/saas-apps/paloaltoadmin-tutorial.md
Error

Firewall Logs

Azure AD Test result

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

ID: 1e69aa64-39b1-c520-b803-cdf72d374e2f
Version Independent ID: bca80503-0cb4-427b-5789-97dfe3dc6b59
Content: Tutorial: Azure Active Directory integration with Palo Alto Networks - Admin UI
Content Source: articles/active-directory/saas-apps/paloaltoadmin-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @jeevansd
Microsoft Alias: jeedes

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

@v-hagamp Can you please review this and work with Mansi and Rakesh to get this updated.

The error shown above normally reflects an issue with the admin role. Once the user is authenticated by the IDP, the assertion/response is sent back to the PAN-OS device with the claims. Which needs to include one for admin role. The PAN-OS device performs the authorization of the user based on the admin role. If the assertion does not contain the admin role claim or does not match what's configured on PAN-OS, the user will not be authorized. Below are some troubleshooting tips to diagnose the issue:
The name of the claim that you configure on Azure must match what's configured in the Admin Role Attribute in the SAML authentication Profile in PAN-OS:

Configure the value of the adminrole claim in Azure to match an admin role defined in PAN-OS. In this example, I am passing the implicit superuser role during the assertion. This can be verified using SAML-Tracer or any such tool.

There could possibly be something else going on. But based on the description, 9/10 - the issue is related to a missing admin role claim or misconfiguration.

I'll review the configs again.
Thanks!

Hello, I had the same problem, I can confirm that the attribute is called "adminrole" and has value "fwadmin" as in the guide, the claim is passed correctly, but I still get the same error "x is not authorized"

Hello, Im experiencing the same issue. Im using "Superuser" rather than "superuser" as thats how its spelt on the firewall.
Did you manage to resolve the issue?


[Feature]: read a textfile and split by line

Feature Request
how can I split a textfile into lines and store them into a vector-store, like those features in flowise and langflow? thanks!
can node-split cover my request?
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Rivet 1.3 will include a Split Text node that will let you split something into an array by new lines! Putting that into a Split Vector Store should get them into the vector store :+1: Just working on publishing now.


Dependency of one service on another while deploying

Hi,
I am implementing a DRF based SAAS application based on the concept and structure mentioned in this repo. My application has apps which handles the necessary models, serializers and views. It also has services which depend on one or more apps. By this i mean that an app can be used in one or more services which in turn deduces the fact that a database can be shared by multiple services. I have encountered 2 edge case which i need to solve before moving it into production.
Case 1:  How do we handle the deployment of services dependent on a common app when the database schema related to the app changes? Let us say, If serviceA and serviceB uses the appC which connects to databaseZ. Both the services are deployed separately using pex files. If i make some model changes in appC and initiate the deployment of both services A and B. If the deployment of serviceA happens fast, it makes the necessary migrations in the databaseZ which might effect the business logic in serviceB and results in the failure of requests to B.
Case 2: How do we handle race conditions in accessing databaseZ by both services? Let us say, serviceA is writing a transaction to databaseZ and serviceB also wants to write to the databaseZ. Won't this result in a lock and make serviceB wait.?
Please help me understand how to handle the above 2 cases and let me know if i have missed some detail while implementing.
Thanks,

In my experience it may be necessary to split model changes into two or more steps, where you simply introduce the migration first, then the model change and app code, when adding features. For removing you go in reverse, deploy the change that removes all references to the model field first (perhaps after deploying an initial migration changing a required field to optional) then when there is no code using the field go ahead and deploy the migration that removes it from the DB.
That is, separate DB migration changes from app code changes so that they can co-exist without issue.

These aren't Pants or Django questions per se, but general software engineering and system design questions. For both your cases I recommend studying the locking properties of your database system, and the general principles of backwards-compatible schema design.

I will close this as general. But feel free to open issues that pertain specifically to Pants (bugs, feature requests etc.)


Make a few changes to support Unity 2019

In theory it also supports 2017.1 but I haven't tested!
Changes done:
Do the old way of "using" for the lower API Compatibility Level
Add if else define statement to support the Experimental namespace for AssetImporters

Thanks for the PR. Do you actually need 2019 support? I didn't include it because 2019 LTS is obsolete.

I create content for VRChat so I'm limited to their Unity version which is currently on version 2019.
I want 2019 support but that's up to you.
I could always just fork and create an installable UnityPackage (not UPM) for us VRChat people.

Are they still using 2019? It's a bit surprising to me, but okay, it makes sense.
Could you revert changes in Util.cs? These changes are unneeded.

Could you revert changes in Utils.cs? These changes are unneeded.

Reverted 👍

Ah, one thing I forgot to change is the Unity version listed here https://github.com/keijiro/Metatex/blob/main/Packages/jp.keijiro.metatex/package.json#L10
I think that's how the Package Manager assumes compatibility 😅


front: fix navigation for builders

Description
Fixes: https://github.com/dust-tt/tasks/issues/353
Admin was visible for builders (but would redirect to apps)
Risk
N/A
Deploy Plan

deploy front

:warning: Modulo linting