Tool Builder Linking and Publishing

Notion ticket link

[[Tool Builder] Linking and Publishing] Resolve Bugs](https://www.notion.so/uwblueprintexecs/Tool-Builder-Linking-and-Publishing-4c41f00dcb554c8daa01dd4bcd862518)

Implementation description

[x] Unpublish tool on save
[x] Allow module linking without clicking into specific tool
[x] Make Unpublish and link buttons work as intended

Steps to test

Make 2 new tools
Go back to the admin/dashboard/tools page and ensure that you can link a module to the first tool (you will need at least 1 module not currently linked to a tool)
Make sure you are unable to link the second tool to the same module
Fill out all the required fields on one of you tools and try publishing it from the admin/dashboard/tools page
Try unpublishing said tool from the same page
Try unlink the tool
Repeat steps 2 - 6 in random orders and ensure that no unexpected bugs occur

What should reviewers focus on?

Module unlinking, linking, publishing, unpublishing

Checklist

[x] My PR name is descriptive and in imperative tense
[x] My commit messages are descriptive and in imperative tense. My commits are atomic and trivial commits are squashed or fixup'd into non-trivial commits
[x] I have run the appropriate linter(s)
[x] I have requested a review from the PL, as well as other devs who have background knowledge on this PR or who will be building on top of this PR

One thing of note is to do with the publish button state. While editing a tool, the "publish" button  is greyed out if the required fields are not filled out. This is not currently done in the the admin/dashboard/tools page as this page only checks if the tool is linked to a module and sets the publish button disabled state off of that. I don't think this should be the case, however the alternative seems to be duplicating the code from the tool builder (a very large function that needs to basically check all required fields as well as self check questions. Should I duplicate this code, leave the publish discrepancy as is (and let admins be sure that a tool is ready before publishing), or remove the nested function from the self check code.

One thing of note is to do with the publish button state. While editing a tool, the "publish" button is greyed out if the required fields are not filled out. This is not currently done in the the admin/dashboard/tools page as this page only checks if the tool is linked to a module and sets the publish button disabled state off of that. I don't think this should be the case, however the alternative seems to be duplicating the code from the tool builder (a very large function that needs to basically check all required fields as well as self check questions to make sure everything is filled out). Should I duplicate this code, leave the publish discrepancy as is (and let admins be sure that a tool is ready before publishing), or remove the nested function from the self check code. I think it would make the most sense if the 2 published buttons (inside the actual tool and on the tools landing page, behaved the same way).
This also ties in to a larger topic of the self check code, for instance I currently am perpetually checking to ensure the tool is publishable, which works fine for the most part, but I am also not sure how big these self check questionnaires will get. I note some slowdowns after adding ~20 questions which might be largely due to continual checking both for the submission as well as the fact that we're running on dev and not prod. The code I have written has it's flaws so I am really open to any suggestions, my current ideas include only checking when the mouse is within the radius of the submission button, leaving it as is since it will probably run fine on prod, or getting rid of it entirely since we can trust the admins to deduce when the required fields are filled ? Any thoughts?

I'm going to bring your questions up to the rest of p-team but my thoughts are:

Maybe we can keep the Publish button active whenever a module has been linked but run a function that checks whether the given tool is fully publishable on click. If the function deems the tool valid it just publishes but if not, it would pop a modal up saying that there are missing fields and a CTA to edit the tool.
We'll ask about the maximum on questions in a Self Check at the client meeting on Monday but I doubt that there will be more than 10 questions.

loom.com/share/8338da6de9fc49358bcc2c69c0859c28
Things are working well for the most part, able to publish and unpublish tools with linked modules from the Tool page and linked modules are not available to select from other tools.
However, from the video, you can see that sometimes when accessing the Tool Builder itself the linked module does not appear as an option nor as something that's selected which makes it impossible to publish from the tool builder. However, the module is still linked because I can publish and unpublish from the dashboard and it sometimes does appear (I think after publishing it appears consistently but without publishing it doesn't but this pattern could be a coincidence).

Thank you for catching this! Will look into it.

One thing of note is to do with the publish button state. While editing a tool, the "publish" button is greyed out if the required fields are not filled out. This is not currently done in the the admin/dashboard/tools page as this page only checks if the tool is linked to a module and sets the publish button disabled state off of that. I don't think this should be the case, however the alternative seems to be duplicating the code from the tool builder (a very large function that needs to basically check all required fields as well as self check questions to make sure everything is filled out). Should I duplicate this code, leave the publish discrepancy as is (and let admins be sure that a tool is ready before publishing), or remove the nested function from the self check code. I think it would make the most sense if the 2 published buttons (inside the actual tool and on the tools landing page, behaved the same way).
This also ties in to a larger topic of the self check code, for instance I currently am perpetually checking to ensure the tool is publishable, which works fine for the most part, but I am also not sure how big these self check questionnaires will get. I note some slowdowns after adding ~20 questions which might be largely due to continual checking both for the submission as well as the fact that we're running on dev and not prod. The code I have written has it's flaws so I am really open to any suggestions, my current ideas include only checking when the mouse is within the radius of the submission button, leaving it as is since it will probably run fine on prod, or getting rid of it entirely since we can trust the admins to deduce when the required fields are filled ? Any thoughts?

I'm going to bring your questions up to the rest of p-team but my thoughts are:

Maybe we can keep the Publish button active whenever a module has been linked but run a function that checks whether the given tool is fully publishable on click. If the function deems the tool valid it just publishes but if not, it would pop a modal up saying that there are missing fields and a CTA to edit the tool. Closing the modal just returns the user to the status quo tools page.
Ideally we won't duplicate code and instead hopefully be able to abstract this code out but if not, duplication is okay too.
We'll ask about the maximum on questions in a Self Check at the client meeting on Monday but I doubt that there will be more than 10 questions.

Your first suggestion makes sense and I'll probably implement that unless @tawnyzhao thinks otherwise. Do you think the same should be done within a module itself? Or is the performance fine?

One thing of note is to do with the publish button state. While editing a tool, the "publish" button is greyed out if the required fields are not filled out. This is not currently done in the the admin/dashboard/tools page as this page only checks if the tool is linked to a module and sets the publish button disabled state off of that. I don't think this should be the case, however the alternative seems to be duplicating the code from the tool builder (a very large function that needs to basically check all required fields as well as self check questions to make sure everything is filled out). Should I duplicate this code, leave the publish discrepancy as is (and let admins be sure that a tool is ready before publishing), or remove the nested function from the self check code. I think it would make the most sense if the 2 published buttons (inside the actual tool and on the tools landing page, behaved the same way).
This also ties in to a larger topic of the self check code, for instance I currently am perpetually checking to ensure the tool is publishable, which works fine for the most part, but I am also not sure how big these self check questionnaires will get. I note some slowdowns after adding ~20 questions which might be largely due to continual checking both for the submission as well as the fact that we're running on dev and not prod. The code I have written has it's flaws so I am really open to any suggestions, my current ideas include only checking when the mouse is within the radius of the submission button, leaving it as is since it will probably run fine on prod, or getting rid of it entirely since we can trust the admins to deduce when the required fields are filled ? Any thoughts?

I'm going to bring your questions up to the rest of p-team but my thoughts are:

Maybe we can keep the Publish button active whenever a module has been linked but run a function that checks whether the given tool is fully publishable on click. If the function deems the tool valid it just publishes but if not, it would pop a modal up saying that there are missing fields and a CTA to edit the tool. Closing the modal just returns the user to the status quo tools page.
Ideally we won't duplicate code and instead hopefully be able to abstract this code out but if not, duplication is okay too.
We'll ask about the maximum on questions in a Self Check at the client meeting on Monday but I doubt that there will be more than 10 questions.

Your first suggestion makes sense and I'll probably implement that unless @tawnyzhao thinks otherwise. Do you think the same should be done within a module itself? Or is the performance fine?

I think the performance is fine at reasonable numbers of Self Check Q, but just in case let's hold off until after the client meeting today (feel free to come if you're not busy and are free!) when I'll have a definitive answer to you about the upper bound on self check questions.


add mention of 4.0

@sqs sounds good. Things will begin shipping in this upcoming release behind the toggle, so we've got incremental releases covered.


why bracket is not downloading on windows 10....  its showing forbidden

Prerequisites

[x] Can you reproduce the problem with Debug -> Reload Without Extensions?
[x] Did you perform a cursory search to see if your bug or enhancement is already reported?
[x] Did you read the Troubleshooting guide?

For more information on how to write a good bug report read here
For more information on how to contribute read here
Description
[Description of the bug or feature]
Steps to Reproduce

[First Step]
[Second Step]
[and so on...]

Expected behavior: [What you expected to happen]
Actual behavior: [What actually happened]
Versions
Please include the OS and what version of the OS you're running.
Please include the version of Brackets. You can find it under Help -> About Brackets (Windows and Linux) or Brackets -> About Brackets (macOS)

Thanks for reporting us.
I tried to reproduce this issue at my end but issue is not observed in Win 10(64bit).
Could you please help us by providing more details of your machine?

Are you facing this issue in Win 10, 64 bit or 32 bit?


Add support for regex_replace_chars variable

what

Add regex_replace_chars variable
Update README
Bumped version of https://github.com/cloudposse/terraform-null-label.git to 0.16.0

why

This variable is passed through to the null-label module and allows more flexibility when naming resources

related
None

/codefresh run test

/codefresh run test

Hi @aknysh
Thanks for that. Done.
Let me know if any further issues.

/codefresh run test

/codefresh run test


Rotation doesn't work in 0.5.0

Hello,
I was trying to implement simple rotation. I realized, the code works properly in 0.0.1 version but doesn't in an actual 0.5.0 version.
Any ideas where can be the problem?
0.0.1 Jsfiddle (works)
0.5.0 Jsfiddle (doesn't work)

Tried 0.5.1 ?

Yes, it doesn't work neither.

@lukasmatta Check out the dev branch. If it works over there, then the bug is fixed and soon will be released.

@DmitryBaranovskiy It works when using dev  branch version. Thank you.


Devop 2122 eon smart contract tools fixes

Description

This pull request provides a fix for a wrong env var being used in the ssignAndSend function and a validation for the value env var in delegate method.
Jira Ticket
DEVOP-2122
Changes

Fix bug in signAndSend function

Add validation for minimal required value in delegate amount

Breaking Changes

-<EMAIL_ADDRESS>Checks

[X] Project Builds
[X] Project passes tests and checks
[X] Updated documentation accordingly
[ ] Breaking changes have been correctly tagged and notified

Additional information

Before merging please ensure docs.horizen.io is aligned with the change in folder structure. ctrl+f v2 on https://docs.horizen.io/horizen_eon/tutorials/forger_node_setup_guide


External xrefs with a certain anchor format cause fatal error

For example the following URLs cannot be used as link targets

https://tagmanager.google.com/#/admin/accounts/create
https://tagmanager.google.com/?hl=en#/admin/accounts/create

Tested with the following link format:
<xref href="https://tagmanager.google.com/#/admin/accounts/create" format="html" scope="external">link text</xref>
Using the DITA-OT3.x bundled with Oxygen 21

Using DITA OT 3.2.1 I can publish a topic containing such a link without any problems.
Is this a publishing or a validation problem?
The link can be alternatively written by escaping the "/" which occur after the anchor part:
        "https://tagmanager.google.com/#%2Fadmin%2Faccounts%2Fcreate"

Using DITA OT 3.2.1 I can publish a topic containing such a link without any problems.
Is this a publishing or a validation problem?
The link can be alternatively written by escaping the "/" which occur after the anchor part:
        "https://tagmanager.google.com/#%2Fadmin%2Faccounts%2Fcreate"

I found the issue when trying to transform a Ditamap to XHTML, which gave an unnamed fatal error in Oxygen. I then found the issue by validating all the map's files.
Thanks for the escape suggestion, it worked for me. In fact, you only need to escape the first "/" after the anchor character.

I also cannot reproduce this problem publishing with an older DITA OT (version 2.5.4).
Oxygen reports a validation error on the link but I'm not sure that in this case our reported error is accurate or not, I will add an internal issue on our side to look into this.
Indeed, the workaround to avoid Oxygen complaining about the link is to escape at least the first "/".


Add raw stc

Add functionality to extract raw time course of a brain region
In this commit, I have extended the script to include functionality that allows users to directly access the raw time courses of a specific brain region through its label without any transformation. This enhancement enables more flexible and detailed analysis of source data.

CI failure does not seem related to this PR.
I think it makes sense to add this functionality, although I was a bit confused by the term "raw" timecourses. I've changed the wording in the changes/devel.rst file when resolving a conflict there, but this is just a suggestion, feel free to change it again @BabaSanfour .
Could we add a unit test for the new functionality?

@wmvanvliet the change should be fine ; The CI failure is fixed - somehow.
For the unit test I will add it later today. I found this comment "# XXX we don't check pca_flip, probably should someday...".
Should I add pca_flip unit test also ?

If you could yes thank you :)

Not sure the errors are related to my pull request; they in viz and transform tests which I didn't touch

CI failures seem related:
 mne/tests/test_source_estimate.py:63:39: F401 [*] `mne.fixes._safe_svd` imported but unused
mne/tests/test_source_estimate.py:67:63: F401 [*] `mne.source_estimate._prepare_label_extraction` imported but unused

I agree it better reflects the logic of mne. Thanks for your work! Glad to contribute.


AttributeError: 'Flask' object has no attribute 'login_manager'

I'm getting the following error when trying to run version 0.5a with
/home/bitcoin/.specter/.env/bin/flask run --cert /home/bitcoin/.specter/cert.pem --key /home/bitcoin/.specter/key.pem --port 25442 --host '<IP_ADDRESS>'

Traceback (most recent call last):
  File "/home/bitcoin/.specter/.env/lib/python3.7/site-packages/flask/app.py", line 2447, in wsgi_app
    response = self.full_dispatch_request()
  File "/home/bitcoin/.specter/.env/lib/python3.7/site-packages/flask/app.py", line 1952, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/home/bitcoin/.specter/.env/lib/python3.7/site-packages/flask/app.py", line 1821, in handle_user_exception
    reraise(exc_type, exc_value, tb)
  File "/home/bitcoin/.specter/.env/lib/python3.7/site-packages/flask/_compat.py", line 39, in reraise
    raise value
  File "/home/bitcoin/.specter/.env/lib/python3.7/site-packages/flask/app.py", line 1948, in full_dispatch_request
    rv = self.preprocess_request()
  File "/home/bitcoin/.specter/.env/lib/python3.7/site-packages/flask/app.py", line 2242, in preprocess_request
    rv = func()
  File "/home/bitcoin/.specter/specter_warden/src/warden/routes.py", line 56, in before_request
    specter_wallets = have_specter_wallets(load=False)
  File "/home/bitcoin/.specter/specter_warden/src/warden/routes.py", line 90, in have_specter_wallets
    wallets = list_specter_wallets(load)
  File "/home/bitcoin/.specter/specter_warden/src/warden/warden_modules.py", line 168, in list_specter_wallets
    specter_data = specter_update(load)
  File "/home/bitcoin/.specter/specter_warden/src/warden/warden_modules.py", line 63, in specter_update
    specter_data = Specter(data_folder=data_folder)
  File "/home/bitcoin/.specter/.env/lib/python3.7/site-packages/cryptoadvance/specter/specter.py", line 158, in __init__
    self.check(check_all=True)
  File "/home/bitcoin/.specter/.env/lib/python3.7/site-packages/cryptoadvance/specter/specter.py", line 197, in check
    self.check_for_user(u)
  File "/home/bitcoin/.specter/.env/lib/python3.7/site-packages/cryptoadvance/specter/specter.py", line 323, in check_for_user
    self.check_wallet_manager(user)
  File "/home/bitcoin/.specter/.env/lib/python3.7/site-packages/cryptoadvance/specter/specter.py", line 273, in check_wallet_manager
    self.device_manager,
  File "/home/bitcoin/.specter/.env/lib/python3.7/site-packages/cryptoadvance/specter/specter.py", line 593, in device_manager
    return self.user.device_manager
  File "/home/bitcoin/.specter/.env/lib/python3.7/site-packages/cryptoadvance/specter/specter.py", line 589, in user
    return self.user_manager.user
  File "/home/bitcoin/.specter/.env/lib/python3.7/site-packages/cryptoadvance/specter/user_manager.py", line 94, in user
    return self.get_user(current_user)
  File "/home/bitcoin/.specter/.env/lib/python3.7/site-packages/cryptoadvance/specter/user_manager.py", line 81, in get_user
    if user and not user.is_anonymous:
  File "/home/bitcoin/.specter/.env/lib/python3.7/site-packages/werkzeug/local.py", line 328, in __bool__
    return bool(self._get_current_object())
  File "/home/bitcoin/.specter/.env/lib/python3.7/site-packages/werkzeug/local.py", line 306, in _get_current_object
    return self.__local()
  File "/home/bitcoin/.specter/.env/lib/python3.7/site-packages/flask_login/utils.py", line 26, in <lambda>
    current_user = LocalProxy(lambda: _get_user())
  File "/home/bitcoin/.specter/.env/lib/python3.7/site-packages/flask_login/utils.py", line 346, in _get_user
    current_app.login_manager._load_user()
  File "/home/bitcoin/.specter/.env/lib/python3.7/site-packages/werkzeug/local.py", line 347, in __getattr__
    return getattr(self._get_current_object(), name)
AttributeError: 'Flask' object has no attribute 'login_manager'

This has been fixed on newer version


Docker images for service module

Issue Type

Feature request

Molecule and Ansible details
ansible <IP_ADDRESS>
molecule, version <IP_ADDRESS>rc12.dev18

Molecule installation method: pip from master
Ansible installation method: brew

Desired Behaviour
It's a known pain to make docker container to work properly with systemd services. I've came to the following solution, which seems to work the best:
platforms:
  - name: centos7
    image: centos:7
    privileged: true
    command: /usr/lib/systemd/systemd

The same is required for fedora and opensuse images.
And on a side note, alpine image fails to start with default command sleep infinity, so it requires something like:
platforms:
  - name: alpine
    image: alpine
    command: sleep 10000

And the feature request is: is it possible to add those examples at least in documentation and maybe in molecule.yml template?

I tend to use the LXD back-end for testing roles with service modules. Systemd is relatively well supported in there and does not require root privileges - something that is a non-starter on my CI server.
Personally, I wouldn't recommend running --privileged containers, especially containing software that does quite far reaching system calls like systemd. I would prefer if LXD or vagrant were recommended for testing these types of roles instead of essentially turning off containerization.

To each their own, right? Docker isn't a VM, and there is only so much that can be tested under Docker.  For example, once you start testing roles which touches files under /etc, you will get an error message, b/c Docker doesn't allow those files to be modified.
I don't mind people using Docker to test systemd roles if they choose to.  However, I assume they know what they are doing by doing so.
Due to the above, I would rather not document this for the time being.


Upgrade bitcoin_hashes dependency

We just released a new version of bitcoin_hashes, upgrade the dependency to v0.11.0

Changes in force-push:

Pulled the first patch out into a separate PR: #1094 because it is trivial and unrelated to this.
Rebased on master

No other changes.

Rebase only, no other changes.


Alerts Not Triggering for Failed DQ Test Cases After Upgrade to 1.5.4

Description:
SMTP alerting for failed DQ (Data Quality) test cases on table followers has stopped working. The system seems to be detecting events correctly, but no alert emails are being sent.
Steps to Reproduce:

Upgrade OpenMetadata from version 1.4.3 to 1.5.4.
Set up SMTP email alerts for failed DQ test cases.
Run tests that generate DQ test failures.
Monitor if alert emails are sent to the configured followers.

Expected Behavior:
Email alerts should be triggered and sent to the followers when a DQ test case fails.
Observed Behavior:

Subscriptions are correctly detecting change events.
Alert triggers are being evaluated properly.
Quartz alert jobs are being created as expected.
However, no alert emails are being sent for failed DQ test cases.

Environment:

OpenMetadata Version: 1.5.4
Previous Version: 1.4.3 (where the issue was not present)
SMTP setup is confirmed to be working and has not changed since the upgrade.

hey, we were able to unblock TestCase and TestSuite alerting by this workaround
---
Index: openmetadata-service/src/main/java/org/openmetadata/service/util/SubscriptionUtil.java
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
diff --git a/openmetadata-service/src/main/java/org/openmetadata/service/util/SubscriptionUtil.java b/openmetadata-service/src/main/java/org/openmetadata/service/util/SubscriptionUtil.java
--- a/openmetadata-service/src/main/java/org/openmetadata/service/util/SubscriptionUtil.java	(revision 95ef74c8de81c7dc84045a71df4fee42d983058a)
+++ b/openmetadata-service/src/main/java/org/openmetadata/service/util/SubscriptionUtil.java	(revision f60abbb5e794b2ed6f48e6f50d1943ba8609ceb4)
@@ -305,6 +305,33 @@
     return Optional.empty();
   }

+  private static Set<UUID> findTablesForTestSuite(UUID testSuiteId , CollectionDAO daoCollection) {
+
+    Set<UUID> tableIds = new HashSet<>();
+    List<CollectionDAO.EntityRelationshipRecord> tables = daoCollection.relationshipDAO()
+            .findFrom(testSuiteId, Entity.TEST_SUITE,Relationship.CONTAINS.ordinal());
+
+    tables.forEach(table-> tableIds.add(table.getId()));
+
+    return tableIds;
+  }
+
+  private static Set<UUID> findRelatedEntities(UUID entityId, String entityType, CollectionDAO daoCollection) {
+    Set<UUID> relatedEntityIds = new HashSet<>();
+
+    if (Entity.TEST_CASE.equals(entityType)) {
+      List<CollectionDAO.EntityRelationshipRecord> testSuites = daoCollection.relationshipDAO()
+              .findFrom(entityId, Entity.TEST_CASE, Relationship.CONTAINS.ordinal());
+      testSuites.forEach( testSuite -> relatedEntityIds.addAll(findTablesForTestSuite(testSuite.getId(),daoCollection)));
+    } else if (Entity.TEST_SUITE.equals(entityType)) {
+      relatedEntityIds.addAll(findTablesForTestSuite(entityId, daoCollection));
+    } else {
+      throw new IllegalArgumentException("findRelatedEntities: Unsupported entity type: "+ entityType);
+    }
+
+    return relatedEntityIds;
+  }
+
   public static Set<String> buildReceiversListFromActions(
       SubscriptionAction action,
       SubscriptionDestination.SubscriptionCategory category,
@@ -338,22 +365,35 @@
       receiverList = action.getReceivers() == null ? receiverList : action.getReceivers();
     }

+    Set<UUID> relatedEntityIds = Set.of(entityId);
+    String relatedEntityType = entityType;
+
+    if  (Entity.TEST_SUITE.equals(entityType) || Entity.TEST_CASE.equals(entityType))  {
+      relatedEntityIds = findRelatedEntities(entityId , entityType ,daoCollection);
+      relatedEntityType = Entity.TABLE;
+    }
+
     // Send to Admins
     if (Boolean.TRUE.equals(action.getSendToAdmins())) {
       receiverList.addAll(getAdminsData(type));
     }

-    // Send To Owners
-    if (Boolean.TRUE.equals(action.getSendToOwners())) {
-      receiverList.addAll(
-          getOwnerOrFollowers(type, daoCollection, entityId, entityType, Relationship.OWNS));
-    }
+    for (UUID relatedentityId : relatedEntityIds) {
+
+      // Send To Owners
+      if (Boolean.TRUE.equals(action.getSendToOwners())) {
+        receiverList.addAll(
+                getOwnerOrFollowers(type, daoCollection, relatedentityId, relatedEntityType, Relationship.OWNS));
+      }

-    // Send To Followers
-    if (Boolean.TRUE.equals(action.getSendToFollowers())) {
-      receiverList.addAll(
-          getOwnerOrFollowers(type, daoCollection, entityId, entityType, Relationship.FOLLOWS));
+      // Send To Followers
+      if (Boolean.TRUE.equals(action.getSendToFollowers())) {
+        receiverList.addAll(
+                getOwnerOrFollowers(type, daoCollection, relatedentityId, relatedEntityType, Relationship.FOLLOWS));
+      }
     }
+
+    LOG.debug("Action receiversList :" + receiverList.toString());

     return receiverList;
   }

Resolved here: https://github.com/open-metadata/OpenMetadata/pull/18181


Lost casing?

Attempting to extract ver-IX86-1.dll causes MPQ Editor to lowercase the file to ver-ix86-1.dll.
Using version <IP_ADDRESS>3
ver-IX86-1.zip

Hi, using version <IP_ADDRESS>6 it works perfectly. Could you check with the new version?

Download page shows <IP_ADDRESS>4: http://www.zezula.net/en/mpq/download.html
File version show <IP_ADDRESS>5, there is no <IP_ADDRESS>6
I did some testing again, and this only occurs when you drag and drop the file to extract it, the filename does not lose casing when you click on the Extract button.

I dragged the file to both Windows Explorer and Total Commander, both kept casing.
Could you please post your Windows Version (also if 32 or 64bit)?

Windows 10.0.10586 x64

Nevermind, I had modified one of my list files and added ver-ix86-1.dll to it, I just deleted it and deleted my temp folder, now MPQEditor extracts properly.


TS07-EditInformations

Coverage decreased (-1.1%) to 92.512% when pulling 87a7de1e5baae9f45d3ccdab4ab93e5c722185a7 on devel into 6e5fac5099c7d8b8f5147240233102f0c7f2ad2a on master.


Add install script option to force a restart of the K3s service

Proposed Changes
Add an option to the install script (INSTALL_K3S_FORCE_RESTART) to force a restart of the K3s service even if there are no binary/service/environment variable changes.
Types of Changes
Install script changes
Verification
Install K3s using the install script, perform a reinstall (simply run the script again) and observe that it does not restart the K3s service. Run the install script a third time, but this time with INSTALL_K3S_FORCE_RESTART=true and observe that K3s is restarted when the script is run.
Linked Issues
https://github.com/k3s-io/k3s/issues/3232
Further Comments

Already merged, needs testing.


V1 - Fix NFT Treasury view for the SEBDAO

The V1 of homebase app is not showing the list of NFT for this DAO - which in turns isn't helpful
Probable issue - changing BCD API to the new APIs


Validation location errors found in java implementation

Found some validation errors when using the latest java build from main;
Incorrect highlight of definition name, instead of type reference;

All errors being assigned to first occurrence of type reference;

If given a definition where the relation name and direct relation are the same word - the type is highlighted instead
https://github.com/openfga/language/blob/main/pkg/js/util/exceptions.ts#L433
Test case:

- name: invalid type error maps to wrong location when duplicate relation name is used in direct assignment
  dsl: |
    model
      schema 1.1
    type custome
    type bank
      relations
        define customer : [customer]
    type account
      relations
        define owner : [customer]
  expected_errors:
    - msg: "`customer` is not a valid type."
      line:
        start: 5
        end: 5
      column:
        start: 23
        end: 31
      metadata:
        errorType: invalid-type
    - msg: "`customer` is not a valid type."
      line:
        start: 8
        end: 8
      column:
        start: 20
        end: 28
      metadata:
        errorType: invalid-type


the third parameter of VmCreator.create should be resource_pool not compilation

https://github.com/cloudfoundry/bosh/blob/master/bosh-director/lib/bosh/director/package_compiler.rb#L153
<EMAIL_ADDRESS>stemcell,
@compilation_resources, network_settings,
nil, @compilation_env)
It will eventually turn to cpi call  def create_vm(agent_id, stemcell_id, resource_pool, network_spec, disk_locality = nil, environment = nil)
https://github.com/cloudfoundry/bosh/blob/master/bosh_aws_cpi/lib/cloud/aws/cloud.rb#L85
And cpi think the third parameters should be  resource_pool,   am i understand correctly ?

third argument to the create_vm CPI call is cloud_properties for the VM configuration. during normal deployment that comes from resource pool and during compilation it comes from compilation's config.


Failed to bundle .prisma dependency

This sample project is really awesome! I am trying to share the Prisma schema and client between repos, and this great sample inspired me, but still fall into some issues. When trying to import typed-prisma-package in another project as a private package, it shows the error below:

Invalid package name ".prisma" of package ".prisma@*": name cannot start with a period.

im having same issue and wondering if anyone figured this out

I think it might work good if you go the tar route and zip it up in a file but using npm publish might be where it fails

any update?


Fix a couple of typos in readme.md

Fixing a couple of grammatical mistakes in the readme

thank you @flynnious


[Feature Request] QRCode analyzing in pictures

Explain in detail what your suggested feature would be used for.
In places like Vket and avatar museum and poster systems, there are QRCodes that link back to the store.  Without the necessary tools built in, QR-Codes are relatively useless.
I've built a project with the necessary tools to scan images in vrchat and places the QRCode in the link the clipboard, however I feel like others might like the idea about collecting the URLs and matching it to the picture.
I'm aware that a feature that I made with VRCPictureToClipboard was included in the December update, but I would also like have this included as well. While, I personally don't use VRCX, but I know it's a tool that others have been accustom to using!
Describe how it would look if it requires a UI.
I imagine that when the photo is taken that a list of "scanned QR codes can be listed in a table or in a note section of the image it's attached to. Possibly in a table if needed.
Explain why people would want to use it.
As previously stated before, this just enhances the ability of VRCX while also bringing the world, avatar, and tool creators the ability to promote themselves and their projects.
Here is a link to the referenced code:
https://github.com/Duinrahaic/VRCPictureToClipboard/blob/master/VRCPictureToClipboard/QRReader.cs

I recommend you use something like VRhands Frame this is simply a request out of the scope of this application and it code base is already under a major rewrite as is.


Error message when queueing URIs

I have my fileserver and filename-to-URI translator working. Adding URIs to the queue works, except that, when loading to an empty queue, the first URI winds up at the end, with the others being loaded in the correct sequence ahead of it. Should I always force the fueue position instead of "next"? That worked to get them in order, and I can do a little scripting to retrieve the queue and figure out the right numbers.  Meanwhile, at every invocation of sonos add_uri_to_queue, I get one of these error messages. If you let me know where you think they might originate, I can add some debugging code to try to find the cause.
ran@delve:trackserver$ for i in cat cs_uris;do sonos add_uri_to_queue $i next;done
<function zero_parameters..wrapper at 0x7fe2a85809d0>
<function zero_parameters..wrapper at 0x7f787d97b9d0>
<function zero_parameters..wrapper at 0x7f7966cd9a60>
<function zero_parameters..wrapper at 0x7ff2d9330a60>
<function zero_parameters..wrapper at 0x7f8b053c99d0>
<function zero_parameters..wrapper at 0x7f09344039d0>
<function zero_parameters..wrapper at 0x7f45a108e9d0>
<function zero_parameters..wrapper at 0x7f115cb779d0>
<function zero_parameters..wrapper at 0x7fb2ec2f09d0>
<function zero_parameters..wrapper at 0x7faf7d4269d0>
<function zero_parameters..wrapper at 0x7f5164c47a60>
<function zero_parameters..wrapper at 0x7f7e9368aa60>
Here are the URIs. I don't see anything odd about them. Maybe the numeric IP address instead of a host name??
cs_uris.txt

Adding URIs to the queue works, except that, when loading to an empty queue, the first URI winds up at the end, with the others being loaded in the correct sequence ahead of it. Should I always force the fueue position instead of "next"? That worked to get them in order, and I can do a little scripting to retrieve the queue and figure out the right numbers

If you use the action add_uri_to_queue without any positional arguments (i.e., without a <queue_position or next> argument), each track should be added to the end of the queue in sequence.

<function zero_parameters..wrapper at 0x7fe2a85809d0>

Looks like that's a bug on my part. Fix should be simple.

Should be fixed in v0.4.71. Please check and confirm. Thanks.

That fixed it. Thanks.
The README gives the impression that a number/next is a required parameter. Maybe use square brackets to identify optional stuff? That's a convention that CLI users are accustomed to.

The README gives the impression that a number/next is a required parameter. Maybe use square brackets to identify optional stuff? That's a convention that CLI users are accustomed to.

The behaviour is fully described at the start of the Queue Actions section.


Education doc for Non-native arithmetic

Document explaining the rationale on Non-native arithmetic in PLONK.
Similar to: https://hackmd.io/@arielg/B13JoihA8, but more detailed, accessible to newer ZK developers

https://hackmd.io/@JkY-zACaSqerTtn_UwFjKg/SJZw6x75o
Published.


Fixes #23714 -- date filter during DST change

The except block catching all exceptions is ugly, but I can't rely on pytz library, which is optional, and therefore I can't catch pytz.exceptions.AmbiguousTimeError exception.

Sorry for the delay. This had slipped off my radar.
I just pushed the change to the debug view which was independent from the main discussion and uncontroversial.
I agree that it makes sense to ignore timezone-related formatters (i.e. return the empty string) for naive datetimes.
I'm happy to look at an updated patch.


OpenId with Linkedin

https://developer.linkedin.com/docs/android-sdk
https://developer.linkedin.com/docs/android-sdk-auth#

#steps are given here:
https://www.numetriclabz.com/android-linkedin-integration-login-tutorial/

The minimum supported version is Android 4.4.2 (API 19).

Associate your Android app with your LinkedIn app by Creating a new app in LinkedIn Developer account
in   https://www.linkedin.com/developer/apps
using
SHA key
package com.suman.openid.login;
 Hash key =  ```` Zw7q34ULemGotVG+3Mf9vhLSKJ8= ````

Create a New Application
Company Name:Required*
Application Name:Required*
Application Description:Required*
Application Logo:Required*
Select File to Upload
Application Use:Required*
Website URL:Required*
Privacy Policy URL:
Business Email:Required*
Business Phone:Required*

To generate hash key from terminal
keytool -exportcert -keystore YOUR_RELEASE_KEY_PATH -alias YOUR_RELEASE_KEY_ALIAS | openssl sha1 -binary | openssl base64

Create a New Application
Company Name:Required*
Technicise Software & Technologies Pvt Ltd
Application Name:Required*
LogIn_With_Linkedin
Application Description:Required*
A demo app which will login with LinkedIn Open id. To register a user some basic info is needed, which will get in return from linkedin.
Application Logo:Required*
Select File to Upload
Application Use:Required*
Website URL:Required*
http://technicise.com/
Privacy Policy URL:
Business Email:Required*
<EMAIL_ADDRESS>Business Phone:Required*
8961222035
I have read and agree to the LinkedIn API Terms of Use.
Submit     Cancel

Client ID:
819tnppscmzen9
Client Secret:
 nJzqhbvVX0F4mHfb
Authorized Redirect URLs:

https://developer.linkedin.com/docs/oauth2
OAuth 1.0a
Default "Accept" Redirect URL:


New app_identifier arguments cause unavoidable breaking change

See comments on https://github.com/getsentry/fastlane-plugin-sentry/pull/19#pullrequestreview-39054097
These should either:

Not have a default value (can't specify nil or empty string to override default value to get back previous behavior)
Just be put in the version argument instead. Having a separate arg that is just concatenated on the version arg doesn't make sense as an API.

I'll submit a revert of d2d22d6fda4a88475889a53a836683b829e383ee and f218eddec2219f4e916b348d6f49638c4214bfdf unless anyone has objections.

It is concatenated with a -, we don't want that people have to do it by themselves since is a thing which could easily be forgotten.
We can argue about the necessity of the default value but I don't want to remove the separate app_identifier parameter.

I see. Just curious, is having the app identifier in the version number recommended? The CLI documentation doesn't mention it: https://docs.sentry.io/learn/cli/releases/#creating-releases
The reason this is a breaking change is that unless the user changes their fastlane setup, they would be opted-in to this new version numbering scheme (app_identifier-version) which I believe breaks the processing unless the client is also changed. Unfortunately, some clients can't be changed (i.e. they may already be released and sending data to just version), so the default behavior of the added args should match the behavior before the change.
I'll remove my PR and put up a new one that just removes the default value and verify that the behavior matches that of before the change. I would also say that we should do the same with the dist argument and make false the default value (see #24) so that users don't need to specify false in the command.

Hey,
Sorry for the late reply, you are right the docs should be improved in this matter.
We've recently changed the whole release system which made this change necessary for our mobile clients.
Currently, it's only here https://docs.sentry.io/clients/react-native/sourcemaps/
I will merge your PR to remove the default value for now.
Thank you


[TW#16576] esp_bt_controller_mem_release doesn't work

In my test APP, i have BT compiled in but it is not started and not initialized, so esp_bt_controller_mem_release should release all the memory. But it doesn't.
ESP_ERROR_CHECK( heap_caps_add_region(mem_start, mem_end)); crashes, and if i remove the check, the two calls look like this:
I (1415) BTDM_INIT: Release DRAM [0x3ffae6e0] - [0x3ffaff10]
I (1425) BTDM_INIT: Release DRAM [0x3ffb0000] - [0x3ffc0000]

both are unsuccessful and return -1 (ESP_FAIL).
[0x3ffae6e0] - [0x3ffaff10] does not match any region in soc_memory_regions.
heap map at boot looks like this:
[Nov 15 18:32:56.607] I (800) heap_init: At 3FFAFF10 len 000000F0 (0 KiB): DRAM
[Nov 15 18:32:56.607] I (806) heap_init: At 3FFD03E0 len 0000FC20 (63 KiB): DRAM
[Nov 15 18:32:56.629] I (813) heap_init: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM
[Nov 15 18:32:56.629] I (819) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
[Nov 15 18:32:56.629] I (825) heap_init: At 400937A4 len 0000C85C (50 KiB): IRAM

https://github.com/espressif/esp-idf/blob/e6afe28bafe5db5ab79fae213f2e8e1ccd9f937c/components/soc/esp32/soc_memory_layout.c#L77

Actually it does work, but with small issue. When i call 	esp_bt_controller_mem_release(ESP_BT_MODE_CLASSIC_BT);  from app_main, its very first line in app_main, then it works without issues. When i call it later, didnt check yet what place it is, but for sure before BT init, then i have heap corrupt issues.

@negativekelvin , the range is valid. The end address is also align to 4bytes. The problem is fixed in 2d148cd34b01aedf66a4fc846de0c296b790ee5a


ValueError: Index (1) out of range (0-0)

When slicing a length-1 dimension with a boolean, an unexpected ValueError is raised. This differs from the netCDF4 behaviour where such an operation is legal.
This is a test function that illustrates this behaviour:
def test_bool_slicing_length_one_dim(tmp_netcdf):
    with h5netcdf.File(tmp_netcdf, 'w') as ds:
        ds.dimensions = {'x' : 1, 'y' : 2}
        v = ds.create_variable('hello', ('x', 'y'), 'float')
        v[:] = np.ones((1,2))

    bool_slice = np.array([1], dtype=np.bool)
    #This should work:
    with netCDF4.Dataset(tmp_netcdf, 'r') as ds:
        data = ds.variables['hello'][bool_slice,...]

    #So does this:
    with h5netcdf.File(tmp_netcdf, 'r') as ds:
        data = ds['hello'][bool_slice,...]

  File "build/bdist.linux-x86_64/egg/h5netcdf/core.py", line 98, in __getitem__
  File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper (-------src-dir-------/h5py/_objects.c:2582)
  File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper (-------src-dir-------/h5py/_objects.c:2541)
  File "/home/laliberte/anaconda2/lib/python2.7/site-packages/h5py/_hl/dataset.py", line 462, in __getitem__
    selection = sel.select(self.shape, args, dsid=self.id)
  File "/home/laliberte/anaconda2/lib/python2.7/site-packages/h5py/_hl/selections.py", line 92, in select
    sel[args]
  File "/home/laliberte/anaconda2/lib/python2.7/site-packages/h5py/_hl/selections.py", line 259, in __getitem__
    start, count, step, scalar = _handle_simple(self.shape,args)
  File "/home/laliberte/anaconda2/lib/python2.7/site-packages/h5py/_hl/selections.py", line 447, in _handle_simple
    x,y,z = _translate_int(int(arg), length)
  File "/home/laliberte/anaconda2/lib/python2.7/site-packages/h5py/_hl/selections.py", line 467, in _translate_int
    raise ValueError("Index (%s) out of range (0-%s)" % (exp, length-1))
ValueError: Index (1) out of range (0-0)

Ok, I've checked and it seems to be an issue coming from h5py. When replacing netCDF4 with h5py, the error is raised at the first read trial.
The test:
def test_bool_slicing_length_one_dim(tmp_netcdf):
    with h5netcdf.File(tmp_netcdf, 'w') as ds:
        ds.dimensions = {'x' : 1, 'y' : 2}
        v = ds.create_variable('hello', ('x', 'y'), 'float')
        v[:] = np.ones((1,2))

    bool_slice = np.array([1], dtype=np.bool)
    #This should work:
    with h5py.File(tmp_netcdf, 'r') as ds:
        data = ds['hello'][bool_slice,...]

    #So should this:
    with h5netcdf.File(tmp_netcdf, 'r') as ds:
        data = ds['hello'][bool_slice,...]

I think andrewcollette describes this pretty well in the linked issue:

I think the issue is that NumPy supports per-axis boolean masks, while h5py only supports a single mask whose shape matches the entire dataset. The error message could certainly be more helpful... a PR would be more than welcome for this.

We do support lists of indices, though... if you want to select elements along a particular axis one option would be to transform your mask to a list of indices using e.g. mask.nonzero(). But note that for large masks this becomes inefficient, as the underlying HDF5 mechanism doesn't scale well.

We could certainly add mask.nonzero() transform in h5netcdf.legacyapi when passed 1D boolean indexers.

@laliberte 5+ years is a long time, but maybe you are still looking for that feature getting implemented. It's approaching in #125.


Phone Number

When you sign in for the first time and try to edit your information, the system requires that you enter a cell phone number or leave the preset one in place.
Please remove this requirement

I am not able to reproduce this on the master branch.
The grey text is a suggestion but it's not stored in the database. We should at least update the suggested address to be near Grand Rapids.

don[t want extra data to protect so no.


Transcript to STDOUT?

It would be very convenient if textra could display the output to STDOUT, via some optional command line argument.
This would make it easier to say, use with python subprocess to automate running it on images and then capture the text to a string (which we could then use programmatically however one likes.)
It's not hard to work around and just use the file system for this, but it would make it a little easier.

Working on adding this feature in. Thanks for the feedback!

Working on adding this feature in. Thanks for the feedback!

Thank you! We have been going back-and-forth on Mastodon, so I appreciate your efforts! looking forward to the next release; my fork is a bit of a hack. 😂

Closed with latest release!


Pro-active security improvement

The details of this task are restricted: https://github.com/ARMmbed/mbedtls-restricted/issues/689

Further improvements of the same kind: https://github.com/ARMmbed/mbedtls-restricted/issues/692


Investigate SingleThreaded race error

Currently, the race detector reports an unusual race when running go-fuse as-is: https://github.com/superfly/litefs/pull/5
This has been fixed by enabling SingleThreaded but that shouldn't be necessary. More investigation will be necessary to figure out what's going on.

FUSE implementation replaced. No longer have this issue.


Identity highlights for the March releases

Please review 🙏

@weshaggard  We merged it in #2501 though - not the master. Is that still an issue?


arbitrary integer sizes, bit fields, and packed structs

Proposal:
@intType(false, 3) creates an unsigned integer type with 3 bits. This can be used just like any other integer type. We already have this builtin function, but it currently causes an error to not use one of the common bit counts.
When placed in a normal struct, it gets its own byte and it is addressable.
When placed in an extern struct, it follows the rules of C bit fields depending on the target environment.
When placed in a packed struct, it may or may not be addressable. It will be a compile error if you try to address it and it is not addressable. If placed before other byte-aligned fields, it may cause those fields to no longer be byte-aligned and hence cause them to become unaddressable.
Another reason to have arbitrary integer sizes is that a programmer could do something like:
const int = @intType(true, 31);
const Result = struct {
    flag: bool,
    number: int,
}
fn foo() -> Result {
    ...
}

Now the return type of function foo could theoretically be a scalar integer instead of a struct, and this optimization could happen in the compiler instead of by the user manually.

Let's say we have this struct:
const u1 = @intType(false, 1);
const u2 = @intType(false, 2);
const u3 = @intType(false, 3);

const Data = packed struct {
    a: u3,
    b: u3,
    c: u2,
};

Now we have a function:
fn foo(data: &const Data) {
    const ptr = &data.b;
    // what is @typeOf(ptr) ?
}

I propose that the type looks like this (examples):

&:3 u3
&:3 const volatile u3

So the :3 means, this pointer is 3 bits offset from the byte the pointer points to. The maximum is 7, because if it were 8 then the pointer doesn't have to be a bit offset pointer, and if it were 9 then it should be 1 with the pointer pointing to the next byte.

can the bit count go arbitrarily high? what arithmetic operations would be allowed for uncommon bit count types?
I've got a concern that perhaps the declarations of u1, u2, etc would become a hassle for large code bases. I assume that @intType(false, 1) would be idempotent accross all files, so you could declare a field with it in one file and a parameter type with it in another file, and the two would be the same type. but would you really want to do that? in your examples you're using aliases that you made, and I imagine most users will want to do the same. furthermore, the name u1 is the obvious choice for what to name it.
proposal: define builtin types for u1..u7. these are probably going to be the most common uncommon bit count types used, and it would unify the community to have official definitions and names for them.
are there examples of existing C programs using an uncommon bit count integer larger than a byte?

proposal: define builtin types for u1..u7. these are probably going to be the most common uncommon bit count types used, and it would unify the community to have official definitions and names for them.

I think this sounds reasonable.
We could also have in the standard library, something like:
pub const u1 = @intType(false, 1);
pub const u2 = @intType(false, 2);
pub const u3 = @intType(false, 3);
...
pub const u31 = @intType(false, 31);
pub const u33 = @intType(false, 33);

And then in users' code:
use @import("std").more_int_types;

The use dumps the types into the current namespace.
We could also do pattern matching on symbol name lookups and resolve any i\d+ or u\d+ symbols to automatically resolve to an int type like this.

are there examples of existing C programs using an uncommon bit count integer larger than a byte?

Here is an example of C code using bitfields with bit count larger than a byte:
https://github.com/Chadderz121/csud/blob/master/include/hcd/dwc/designware20.h#L164
When translated into Zig, this would use uncommon bit count integers since that is how bit fields work in Zig. I'm not aware of it being possible to have uncommon bit count integers as a general type outside of a bit field.

can the bit count go arbitrarily high? what arithmetic operations would be allowed for uncommon bit count types?

I think we can make it go arbitrarily high, and we can support all arithmetic operations on all bit count types.


Fail if --rbe is provided explicitly but RBE can't be used

Related issue: https://github.com/flutter/flutter/issues/150881
observed behavior
If you have the wrong macos sdk installed, rbe builds will fallback to local builds.
expected behavior
I expect the build to fail with a note of mixmatched macos sdks.

I'm confused what the expectation is here - it might be valid to have multiple MacOS SDKs installed or switch between them. Fallback to local builds if RBE cache is not available makes sense generally. What is the expectation?

I'd like the behavior where we get RBE or fail.  That way I don't have to discover the hard way that things are broken after potentially wasting a lot of time.  Maybe we could make the fallback work in the absence of --rbe or --no-rbe.  But if someone explicitly specifies --rbe it's RBE or fail.

@gaaclarke Want to take a shot at implementing this one?

I'm in the middle of some heavy graphics stuff, after that I'm open to it.

I ended up doing this on accident in another refactor.
We will now have --build-strategy=remote, which only uses RBE Builds.


carousel

Template request
Describe the template you need
Additional information
Optional: Add screenshots, or Figma/Sketch files

@surajkrishan Thank you for your request.
Unfortunately you provided very less information. 🙈
Do you have any examples for carousels you want to see in Chakra-Templates?

@surajkrishan Thank you for your request.
Unfortunately you provided very less information. 🙈
Do you have any examples for carousels you want to see in Chakra-Templates?

👋🏻  @hauptrolle,
it would be great to see a carousel component in chakra templates something like a bootstrap carousel (for eg)
https://getbootstrap.com/docs/5.0/examples/carousel/

Hey @hauptrolle, Can I take up this issue?

Hey @hauptrolle, Can I take up this issue?

Sure, go ahead! Any ideas which slider library u want to use?

Hey @hauptrolle, Can I take up this issue?

Sure, go ahead! Any ideas which slider library u want to use?

I haven't thought of any yet.

Hey 👋🏽, just wanted to know can I also contribute to this. I was thinking of using react-slick package as it provides touch support on mobile screens.

Sure, react-slick sounds good! :)


Interfaces with "/" are automatically sorting first when it should be based on number before "/"

Environment

Python version: 3.8.10
Nautobot version: 1.2.3

Steps to Reproduce

Adding Arista device type DCS-7280SR-48C6
Look how interfaces are sorted

Expected Behavior
Interfaces should start:
Ethernet1
Ethernet2
...
Ethernet48
Ethernet49/1
Ethernet50/1
...

Observed Behavior

In [5]: for intf in Interface.objects.all():
   ...:     print(f"Interface.name:{intf.name}, Interface._name:{intf._name}")
   ...:
Interface.name:Ethernet49/1, Interface._name:0049999999999999Ethernet000001............
Interface.name:Ethernet49/2, Interface._name:0049999999999999Ethernet000002............
Interface.name:Ethernet48, Interface._name:9999999999999999Ethernet000048............

Based on reviewing naturalize_interface this is working as implemented - Ethernet49/1 is interpreted as "slot 49, id 1" while Ethernet48 is interpreted as "slot N/A (mapped to 9999, i.e. last in the ordering), id 48", hence why all the slotted interfaces are sorted before all the non-slotted interfaces, but ordering is preserved within each group.
It would certainly be possible to change things so that "slot N/A" gets sorted first rather than last, but I'd definitely be concerned as to whether this change would result in another bug being filed down the line complaining that "Ethernet100" gets sorted before "Ethernet 1/1", i.e. asking for the current behavior to be restored.
I'll also note that there is already a lot of previous history in NetBox surrounding interface ordering behavior - as of yet no one there or here has been able to come up with a one-size-fits-all solution to respecting all interface numbering conventions on differing platforms and OSes - this is simply a very difficult problem to solve.

I wonder if Ethernet48 should instead be "slot 48, id 0" in that case then.

I had similar concerns. The best I could think of is to provide this as a "pluggable feature", with the ability to send slug to a custom function.

After deliberation we decided the juice is not worth the squeeze to change this at this time. If we were to change the way interface names are sorted (which would be considered a breaking change), or allow for the sorting to be pluggable, it would have to be in Nautobot v2 or later.


Missing permissions to create a directory in the database container

Hi @tometchy ,
Great stuff, it helped me a lot, but I had to modify the Docker file for the mssql to execute the mkdir and chmod commands as root user and then back to the mssql user for the scripts part as follows:
# We choose exact tag (not 'latest'), to be sure that new version won't break creating image
FROM mcr.microsoft.com/mssql/server:2019-latest

# change active user to root
USER root

# Create app directory
RUN mkdir -p /usr/src/app
WORKDIR /usr/src/app

# Copy initialization scripts
COPY . /usr/src/app

# Grant permissions for the run-initialization script to be executable
RUN chmod +x /usr/src/app/run-initialization.sh

# change back to user mssql
USER mssql

# Set environment variables, not to have to write them with docker run command
# Note: make sure that your password matches what is in the run-initialization script
ENV SA_PASSWORD CorrectHorseBatteryStapleFor$
ENV ACCEPT_EULA Y
ENV MSSQL_PID Express

# Expose port 1433 in case accesing from other container
EXPOSE 1433

# Run Microsoft SQl Server and initialization script (at the same time)
# Note: If you want to start MsSQL only (without initialization script) you can comment bellow line out, CMD entry from base image will be taken
CMD /bin/bash ./entrypoint.sh

Could you please have a look and update the file if this is correct?

You're right, the policy has changed, thanks for the comment. I will look at it more carefully (at the evening probably) and then change the file. In case you or some other reader doesn't know - this can be changed at the docker-compose file level as well, but your approach with adding it to Dockerfile looks simpler. Thanks again :)


Fix hashbang

To run these scripts on a system where /bin/sh is not bash we
need a different hashbang.

Thanks. Could you set these to #!/usr/bin/env bash instead so that it is compatible with NixOS? Then I think I can accept the PR.

Thanks!


virtually-geometric  兄弟。

1真心崇拜一下。 要是wiki完善些【how to build wasm】。或许会有更多人加入。
2很遗憾的下面的两个大佬没有开源，嘿嘿，我是顺着网线找到这个你这个GitHub。is a great work！！！！
https://discourse.threejs.org/t/virtually-geometric/28420
https://zhuanlan.zhihu.com/p/556616601?utm_id=0

Thanks, the project is quite a mess at the moment but depending on how this goes im planning on documenting everything.
I agree that its a shame that no implementations of virtual geometry are open source that's part of the reason for this repo. The whole thing seems relatively straightforward but the devil is in the details.
Regarding the wasm compilations get emsdk, activate the emsdk environment and run "three-nanite/src/metis-js/metis-5.1.0/em-build.sh" and "src/meshoptimizer/js-build.sh".
Note that some paths will need to be updated inside the scripts.


seqfault compiles

interface DBNotify

class Foobar is DBNotify
  var _env: Env
  let sqlConnector: SqlConnecter
  new iso create(env': Env) =>
    _env = env'
    sqlConnector = SqlConnecter(_env, Foobar(env'))

actor Main
  var _env: Env
  new create(env': Env) =>
    _env = env'
    let sqlConnector = SqlConnecter(_env, Foobar(env'))

actor SqlConnecter
  let _env: Env
  var _notifier: DBNotify iso

    new create(env: Env, notifier': DBNotify iso) =>
    _notifier = consume notifier'
    _env = env

edit: minimized it even more (no C reference)

Where does this segfault? And i wouldn't consider this a bug per se as you do call C from Pony which has the same risk of segfaulting than any other C program.
So, are you sure this segfault is due to a bug in Pony? Note, that Pony does not guarantee segfault-free programs when calling arbitrary C-code.

It looks like the post was edited to remove the FFI calls.
I haven't run this example yet, but it looks like it's an OOM issue - every Foobar that gets created will create another Foobar in its constructor - meaning that you'll keep allocating Foobars until you're out of memory.
Pony can't protect you against the consequences of allocating more memory than the OS can allow - ultimately I don't think there's much we can do to handle this "gracefully".

This is indeed smashing the stack due to infinite recursion. In the future it would be nice to have a static analysis tool to detect this kind of bug.
Closing the issue since there isn't much we can do at this point.


AKS Learn feedback: Test3

Type of issue
Typo
Feedback
Test3
Page URL
https://review.learn.microsoft.com/en-us/azure/aks/use-managed-identity?branch=pr-en-us-278352#next-steps
Content source URL
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/aks/use-managed-identity.md
Author
@tamram
Document Id
01e98043-dc80-490e-a761-8d558ff4e6df

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

ID: 6a9c74a8-9f1a-3d3d-3aed-f8ec45f92e05
Version Independent ID: 01e98043-dc80-490e-a761-8d558ff4e6df
Content: Use a managed identity in Azure Kubernetes Service (AKS) - Azure Kubernetes Service
Content Source: articles/aks/use-managed-identity.md
Service: azure-kubernetes-service
Sub-service: aks-security
GitHub Login: @tamram
Microsoft Alias: tamram

@JasonWHowell
It looks like your issue is resolved since you closed this thread.
If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.


is it possible to select maximum two days??

hi i do allowsMultipleSelection property true. but i want maximum 2 selection so is it possible?

U can call deselectDate when there are more than two dates selected.


perlPackages.CryptOpenSSLX509: init at 1.813

Motivation for this change
Adds the Crypt::OpenSSL::X509 Perl module
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Notify maintainers
cc @volth

@stigtsp it seeams 1.813 has been published since. Could you refresh the PR?

@stigtsp it seeams 1.813 has been published since. Could you refresh the PR?

Rebased and refreshed! :)

@GrahamcOfBorg build perl528Packages.CryptOpenSSLX509 perl530Packages.CryptOpenSSLX509


chore(AlgebraicGeometry/EllipticCurve/Weierstrass): change the ext lemma for EllipticCurve

Now it doesn't require that the discriminant is equal. This is like Units.ext.

bors d=@Ruben-VandeVelde

I think this is fine, yeah.
bors merge

I think you should type bors r+


build:embedded_binaries/A-server.jar is missing or modified

I use envoy1.10 build with docker in centos.It work fine in the past,but today it report this error "FATAL: corrupt installation: file '/build/tmp/_bazel_bazel/install/7da6a92c096ada842b8d48c251312343/_embedded_binaries/A-server.jar' is missing or modified.  Please remove '/build/tmp/_bazel_bazel/install/7da6a92c096ada842b8d48c251312343' and try again."
I haven't change anything about ci script.
Here are my build cmd:
export ENVOY_DOCKER_BUILD_DIR=/data/envoy110
IMAGE_NAME=envoyproxy/envoy-build-centos ./ci/run_envoy_docker.sh './ci/do_ci.sh bazel.release.server_only'
Any help will be appreciate!!

It doesn't work when I remove tmp/_bazel_bazel/install/7da6a92c096ada842b8d48c251312343 and try again.

I have found out why ,some url have been disabled.


[Feature] - ClickHouse on EKS

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

What is the outcome that you are trying to reach?

Describe the solution you would like

Describe alternatives you have considered

Additional context

Alex: Please update the ClickHouse blueprint repo link here

I met with CliCkHouse team and provided guidance and review comments on thier blueprint PR. We can track this issue until the blueprint is published

https://awslabs.github.io/data-on-eks/docs/blueprints/distributed-databases/clickhouse


cordova build failed

> Task :app:transformClassesWithDexBuilderForDebug

> Task :app:transformDexArchiveWithExternalLibsDexMergerForDebug FAILED
D8: Program type already present: android.support.v4.os.ResultReceiver$MyResultReceiver

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:transformDexArchiveWithExternalLibsDexMergerForDebug'.
> com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives:
  Learn how to resolve the issue at https://developer.android.com/studio/build/dependencies#duplicate_classes.
  Program type already present: android.support.v4.os.ResultReceiver$MyResultReceiver

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 1m 40s
36 actionable tasks: 11 executed, 25 up-to-date
/Vishnu Personal/Ionic/mpApp/platforms/android/gradlew: Command failed with exit code 1 Error output:
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
D8: Program type already present: android.support.v4.os.ResultReceiver$MyResultReceiver

Try put this inside project.properties
android.enableJetifier=true
android.useAndroidX=true

This is a real problEM, I AM HOCKED HERE FOR DAYS.


Handle a backslash well

$ ruby -e '"\\".foo'
-e:1:in `<main>': undefined method `foo' for "\\\\":String (NoMethodError)
"\\\\".foo
    ^^^^

Found by @nobu
The problem is that Exception#message escapes the message. Not only error_highlight but also "\\\\":String (NoMethodError) is wrong. This should be fixed in the side of Exception#message in any way, but I have no good idea how to fix.

This issue has been fixed in the side of the interpreter https://bugs.ruby-lang.org/issues/18367


Allow default parameters for all CS/JDL paramaters in cloud_scheduler.conf.

Currently identified as missing are: default_VMInjectCA, default_VMKeepAlive, and default_VMUseCloudInit.

A default VMKeepAlive time can be set on a per cloud basis in cloud_resources.conf by adding a time (in minutes) to any cloud entry.
[cloud]
...
keep_alive: 5
...
This was done to give more control over commercial versus 'free' clouds.

UseCloudInit defaults to True and looks like it can be deprecated / removed

default_VMInjectCA already supported.


Remove app.client

Fixes #228
Proposed changes

Remove .client attribute on App - it was deprecated since 0.13 until 0.14.

Codecov Report

Merging #229 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #229      +/-   ##
==========================================
- Coverage   96.23%   96.21%   -0.02%
==========================================
  Files          24       24
  Lines        1036     1031       -5
  Branches       97       97
==========================================
- Hits          997      992       -5
  Misses         33       33
  Partials        6        6

Impacted Files
Coverage Δ

bocadillo/applications.py
99.47% <ø> (-0.02%)
:arrow_down:

Continue to review full report at Codecov.

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

Codecov Report

Merging #229 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #229      +/-   ##
==========================================
- Coverage   96.23%   96.21%   -0.02%
==========================================
  Files          24       24
  Lines        1036     1031       -5
  Branches       97       97
==========================================
- Hits          997      992       -5
  Misses         33       33
  Partials        6        6

Impacted Files
Coverage Δ

bocadillo/applications.py
99.47% <ø> (-0.02%)
:arrow_down:

Continue to review full report at Codecov.

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


Fix issue #73 and #70

Changes made for "^U" in fix_line_issues.rs do not show up properly in GitHub's code preview.  Recommend viewing via a text editor.
I moved the "fix_new_line.rs" to "fix_line_issues.rs" as a potential file to handle string cleanup so impacts to existing memory management, etc. would not be impacted.

@LSchallot Thanks for your PR. Will have a look at this when I get a moment. I can't promise any ETA.

Hi @LSchallot ! Thanks again. With the minor fix noted above, I've applied the fixes on the monorepo on which I develop for Rust: https://github.com/conradkleinespel/duck/pull/39
I'll soon publish a new releases for rpassword with this :+1:


Not able to create font

Hi I am not able to create font using the font_to_py.py. I want to create freesans24.py and freesans36.py

It would help if you explained the nature of your difficulty. This works here:
[adminpete@capybara]: /mnt/qnap2/data/Projects/MicroPython/micropython-font-to-py
$ ./font_to_py.py -x FreeSans.otf 24 freesans24.py
Writing Python font file.
Height set in 2 passes. Actual height 24 pixels.
Max character width 25 pixels.
freesans24.py written successfully.

I was having problems with this same issue myself, but the script worked once I changed the first line of font_to_py.py (and font_test.py) from this:
#! /usr/bin/python3
to this:
#!/usr/bin/env python3
So perhaps those files ought to be updated, to allow for alternate Python install environments.

Thanks for that. Now done.


about frcnn_128_512.backbone.pth.tar

Thanks for sharing your great work.
I was trying to run the model, however I didn't find the pretrained frcnn_128_512.backbone.pth.tar for videonet. Could you please share it? Thanks.

Ok, this pre-train model is in this link: lip-reading model

Thanks for your reply.
I still got some issues  when I run eval.py:
CTCNet-main\nichang\models\base_av_model.py", line 69, in from_pretrain
from . import get
ImportError: cannot import name 'get' from 'nichang.models' (unknown
location)
I didn't find a function called get.
And I printed conf["model_name"] and it showed "AVFRCNN2". I didn't find a
model called AVFRCNN2.
Thanks.
On Fri, Feb 10, 2023 at 10:57 PM Kai Li (李凯) @.***>
wrote:

Ok, this pre-train model is in this link: lip-reading model
https://bit.ly/3ep9W06
—
Reply to this email directly, view it on GitHub
https://github.com/JusperLee/CTCNet/issues/1#issuecomment-1426616475,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALY6PX73UAKNI4EV26P6AU3WW4L3ZANCNFSM6AAAAAAUYKWZ6M
.
You are receiving this because you authored the thread.Message ID:
@.***>

I'm very sorry for any confusion I may have caused you.
AVFRCNN2 is the name of my previous model, which should now be replaced by the CTCNet model. You may need to modify the "model class" in the pre-trained model, for example, replace all instances of "AVFRCNN2" with "CTCNet". As I am currently preparing a paper for a conference, it may take me some time to adjust the names in the pre-trained model.

No worries. Thanks.
I tried to replace class CTCNet with "AVFRCNN2" and got the error about mismatch:
Error(s) in loading state_dict for AVFRCNN2:
Missing key(s) in state_dict: "masker.video_block.video.0.proj.conv.weight", "masker.video_block.video.0.proj.conv.bias", "masker.video_block.video.0.proj.norm.weight", "masker.video_block.video.0.proj.norm.bias", "masker.video_block.video.0.proj.norm.running_mean"...............
Could you please check for me when you are available? Thanks.

No worries. Thanks.
I tried to replace class CTCNet with "AVFRCNN2" and got the error about mismatch: Error(s) in loading state_dict for AVFRCNN2: Missing key(s) in state_dict: "masker.video_block.video.0.proj.conv.weight", "masker.video_block.video.0.proj.conv.bias", "masker.video_block.video.0.proj.norm.weight", "masker.video_block.video.0.proj.norm.bias", "masker.video_block.video.0.proj.norm.running_mean"...............
Could you please check for me when you are available? Thanks.

Ok. I will check quickly.

I have modified the URL for the checkpoints in the README. You can use the new checkpoints, and I have tested them without any issues.

Thanks. Yes, it worked.


really drop python<=3.7 support

Filer all code over pyupgrade --py38-plus.

Cannot make all CIs pass without errors 🤔

I have helped you a bit, thank you for this PR :pray:
Much neater now.

Thx 👍 😄


write specific deepstream version

Thanks for PR, but I'll not merge it as this repo is compatible with both deepstream-5.0, 5.1 and even more than these.


The size of type Rotations.RotXYZ{Float64} is not known.

I still get a size error, although I checked out the latest Rotations.jl
julia> Pkg.status()
- Rotations                     0.3.5              master

The error is the following:
ERROR: The size of type `Rotations.RotXYZ{Float64}` is not known.

If you were trying to construct (or `convert` to) a `StaticArray` you
may need to add the size explicitly as a type parameter so its size is
inferrable to the Julia compiler (or performance would be terrible). For
example, you might try

    m = zeros(3,3)
    SMatrix(m)      # this error
    SMatrix{3,3}(m) # correct - size is inferrable

Stacktrace:
 [1] StaticArrays.Size(::Type{Rotations.RotXYZ{Float64}}) at /home/zorn/.julia/v0.6/StaticArrays/src/traits.jl:42
 [2] size(::Type{Rotations.RotXYZ{Float64}}) at /home/zorn/.julia/v0.6/StaticArrays/src/abstractarray.jl:7
 [3] *(...) at /home/zorn/.julia/v0.6/StaticArrays/src/matrix_multiply.jl:199

Just to double-check, which version of StaticArrays are you using?

julia> Pkg.status()
- StaticArrays                  0.3.0

BTW this is julia v0.6, but that is not the problem, is it?

Oh, yes that is definitely a problem.
See https://github.com/JuliaArrays/StaticArrays.jl/issues/113 and https://github.com/JuliaArrays/StaticArrays.jl/issues/109. In particular, the problem in the latter means that any type defined after StaticArrays is imported will not function correctly. We are working hard to rewrite StaticArrays to work with the new compiler (such extremely low-level packages are susceptible to subtle compiler changes that occur with new versions of Julia) but it's a non-trivial amount of work to do in spare time, so it might be another week or two before the v0.6 version is fully up-and-running, sorry.
(I'll edit the title and leave the issue open until StaticArrays is fixed).

Fixed by https://github.com/FugroRoames/Rotations.jl/pull/25.

Thanks!


[ISSUE_TEMPLATE] First implementation of the issue template

Hi,
@kisvegabor, could you help us to get this file as an issue template for this repo? I tried to follow the issue template of the main lvgl repo.
Let me know if you have any suggestions.
Regards

Merged!
It looks good in the practice too.

Great, thanks for the help!


[WIP] Investigate density

[ ] I have followed (at least) the PR section of the contributing guide.

Buttons https://deploy-preview-22016--material-ui.netlify.app/components/buttons/#densities
Button Groups https://deploy-preview-22016--material-ui.netlify.app/components/button-group/

@joshwooding Which problem are you going after?

@joshwooding Which problem are you going after?

Following the Material Design specs closer regarding density

This is more a personal investigation

Best not to create a PR then, even as a draft, until you have something you want to share publicly

This is more a personal investigation

Best not to create a PR then, even as a draft, until you have something you want to share publicly

I'm happy to share it publicly, I said it's more of a personal investigation but it really means I'm not advocating for it but I'll close this for now.


Rename roles variable

The different configs uses roles as a variable. Since this is a protected name I get a warning every time I run ansible. I should simply rename it, just have to make sure I don't e.g. break the zsh include thingy.

Closed by b31457b683e060ff8c340f9a0e321ad2ec47bdac


Unable to resolve module './views/Header/HeaderStyleInterpolator

Hello People. I did update react-navigation-stack to  "react-navigation-stack": "^2.0.0-alpha.26" to implement ios 13 modal. Can help me with issue? Thanks.

React-Native - 60.5
React-navigation-stack - 2.0.0-alpha.26

try deleting your node_modules and reinstalling, and/or react-native start --reset-cache (expo start -c if using expo).

Thanks @satya164 . Perfect.


Adding missing params

Closes https://github.com/MicrosoftDocs/office-docs-powershell/issues/7187

Docs Build status updates of commit 18f38a3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

@Kateyanne Please merge this PR. Thanks

Docs Build status updates of commit 4227921:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Replace "WIP" notification with link to CfC

[ ] Needs Indico link to be ready

I included the link to indico in PR #160. It is now configured in _config.yml.


AttributeError: 'VocabWeightHandler' object has no attribute 'name'

System information.

Have I written custom code (as opposed to using a stock example script provided in Keras):
https://colab.research.google.com/drive/1BD9G1o7CNxAaKKyihCKx0wa1zW-tmn0r?usp=sharing
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
TensorFlow installed from (source or binary): pip
TensorFlow version (use command below): 2.6.0
Python version: 3.8
Bazel version (if compiling from source):
GPU model and memory:
Exact command to reproduce:

Describe the problem.
Tensorflow profiler crashes when using string categorical layer, not allowing to profile models with those layers.
Maybe the same issue

The same issue happened to me.
I "fixed" it by changing the Tensorboard(histogram_freq=0), but it seems you mentioned it's a bad idea as we can't get tensorflow profiler in tensorboard.

This is a known bug with some special classes we introduced for handling StaticHashTable and MutableHashTable in keras layers (TrackableWeightHandler and VocabWeightHandler). Both the classes have caused a number of issues, so I believe the best approach here would be to remove them entirely. We will need to think about the design of how best to do that.

Is there any update on this issue?

I faced the same issue when trying to integrate Tensorboard with the official Tensorflow RNN classification tutorial: https://www.tensorflow.org/text/tutorials/text_classification_rnn.


Error regarding Geometry Message

Hello @alanzjl
Great Work!
I was facing issue while running pretrain.py:
WARNING:root:Failed to import geometry msgs in rigid_transformations.py.
WARNING:root:Failed to import ros dependencies in rigid_transforms.py
WARNING:root:autolab_core not installed as catkin package, RigidTransform ros methods will be unavailable

Its from autolab_core that I already installed as per the installation file. I also tried installing it from source: https://berkeleyautomation.github.io/autolab_core/install/install.html#option-2-install-from-source-for-ros but that also does not work.
Does it have to do something with ROS? I also installed ros-humble-geometry-msgs. But that also does not work.
Thanks.

Hi @vedantdave97 thanks for your interest! Feel free to ignore those warnings - they are for ROS-related stuff however in this package autolab-core was only used for pose transformations, hence no ROS. If the script is failing it should be due to other reasons - what's the full terminal output and what's the command that you were running?
Alan

Hello @alanzjl
Thanks for the reply. That was just a warning. It was working.
Just one question: From what I can see, you provided a collab that contains pretrained model loading. Also the same is in the train_nn.py. Is there any script for pretraining as in the paper? Am I missing something?
Regards,
Vedant

Hi @vedantdave97 thanks for your interest! You are right that the colab only contains inference code that loads the pretrained models. However, the pretraining code is also in this repository. Checkout here,
pretrainer = T3Pretrain(cfg)
pretrainer.setup_model()
pretrainer.setup_optimizer()
pretrainer.setup_dataset()
print("Dataset setup complete")
# pretrainer.train()
pretrainer.test(20, "", 0, False)

If you uncomment the pretrainer.train() line then feed in the proper data mixture then that's it for pretraining.


Add configurable crypto operation maximum data size

Allow MSL configurations to specify a maximum size for data processed by a crypto operation, to ensure compatibility with all participating entities. Perhaps this belongs in MessageCapabilities. Application data can be split across MSL payload chunks to satisfy this limit, but errors would need to be thrown for data in tokens and headers.
The default size should be set to 100KiB.

I believe this is closed based on a status report I saw from SecEng; can you confirm?


WRP-11279 : Fix broken links referencing other props in documentation

Checklist

[x] I have read and understand the contribution guide
[ ] A CHANGELOG entry is included
[ ] At least one test case is included for this feature or bug fix
[ ] Documentation was added or is not needed
[ ] This is an API breaking change

Issue Resolved / Feature Added
There are broken links that refer to other props in the documentation.
Broken links

https://enactjs.com/docs/modules/ui/Button/#ButtonBase.iconFlip
https://enactjs.com/docs/modules/ui/GridListImageItem/#GridListImageItem.placeholder
https://enactjs.com/docs/modules/ui/IconButton/#IconButtonBase.children
https://enactjs.com/docs/modules/ui/Layout/#Layout
https://enactjs.com/docs/modules/ui/Layout/#CellBase.shrink
https://enactjs.com/docs/modules/ui/Layout/#CellBase.size
https://enactjs.com/docs/modules/ui/Layout/#LayoutBase
https://enactjs.com/docs/modules/ui/Routable/#Routable.defaultConfig.navigate
https://enactjs.com/docs/modules/ui/Spinner/#SpinnerBase.blockClickOn
https://enactjs.com/docs/modules/ui/ToggleIcon/#ToggleIconBase.children
https://enactjs.com/docs/modules/ui/ToggleItem

Private API broken links

enact\packages\ui\Item\Item.js 53,34
enact\packages\ui\Routable\Router.js 48,34
enact\packages\ui\ViewManager\TransitionGroup.js 97,34

Resolution
Fix links to broken props in the documentation
Additional Considerations
Links
WRP-11279
Comments
Enact-DCO-1.0-Signed-off-by: Hoeun Ryu<EMAIL_ADDRESS>

The PR has been updated to fix additional broken links

https://enactjs.com/docs/modules/ui/Layout/#Layout
https://enactjs.com/docs/modules/ui/ToggleItem
enact\packages\ui\Item\Item.js 53,34
enact\packages\ui\Routable\Router.js 48,34
enact\packages\ui\ViewManager\TransitionGroup.js 97,34

The PR has been updated to fix additional broken links

enact\packages\spotlight\Spottable\Spottable.js 251,34


Upside down in/output at specific toggle group

Can the addon deal with this like upside down the input and output of shaders?

This should be fixed by setting RESHADE_DEPTH_INPUT_IS_UPSIDE_DOWN to 1, I think. REST itself does not intervene in how the game applies it's own shaders.

But it only upside down inside some shaders of the game.

I have a similar problem with that other anime game from this developer, my RESHADE_DEPTH_INPUT_IS_UPSIDE_DOWN is set to 1 and it fixes the depth buffer for shaders, but there are a lot of shaders in the group settings that show the preview upside-down and using them will make affected shaders also flip upside down. For example, I have one pixel shader where the preview is exactly the 3D scene without the UI, but it's upside down. If I select it and set Invocation location to AFTER DRAW or ON RENDER TARGET CHANGE, the UI is perfectly excluded and right-side-up, but anything ReShade touches is flipped upside down.

There are some other pixel shaders that seem to contain most of the UI and don't flip anything.

The NPC nameplate is not excluded properly here.
It would be nice to have some kind of upside-down toggle somewhere, but I don't actually know how any of this works, so maybe there's already something I could do if I knew how.

Same issue with Genshin as well. Some shaders are flipped such as this one for fog which breaks when I want to use that toggle group so I can use MXAO and RTGI without applying to the fog as otherwise they will show through. However, as you can see it is flipped so it renders upside down so we need a switch for this toggle group to flip it.

Added option to flip with 1.3.8

Added option to flip with 1.3.8
Thanks for adding this but running into an issue with flipping, it doesn't do the full image. I suspect it may be related to my game resolution being 2560x1440 but the addon is reporting 3840x2160 resulting in a mismatched flip.

If you're using FSR2/DLSS with scaling factor != 1.0: Don't


npm ERR! errno ECONNREFUDED

Error occurs, while building HUE release-4.5 in NO-internet environment. How it can be fixed?
--- Generating /ws/build/hue/rpm/BUILD/hue-release-4.5.0/desktop/conf/pseudo-distributed.ini
sed -e 's:$HADOOP_HOME:/usr/lib/hadoop:' /ws/build/hue/rpm/BUILD/hue-release-4.5.0/desktop/conf/pseudo-distributed.ini.tmpl > /ws/build/hue/rpm/BUILD/hue-release-4.5.0/desktop/conf/pseudo-distributed.ini
make[1]: Leaving directory /ws/build/hue/rpm/BUILD/hue-release-4.5.0/desktop' make[1]: Entering directory /ws/build/hue/rpm/BUILD/hue-release-4.5.0'
npm install
make[1]: Leaving directory `/ws/build/hue/rpm/BUILD/hue-release-4.5.0'
RPM build errors:
npm ERR! Linux 3.10.0-957.21.3.el7.x86_64
npm ERR! argv "/usr/local/node/bin/node" "/usr/local/node/bin/npm" "install"
npm ERR! node v0.10.44
npm ERR! npm  v2.15.0
npm ERR! code ECONNREFUSED
npm ERR! errno ECONNREFUSED
npm ERR! syscall connect
npm ERR! Error: connect ECONNREFUSED
npm ERR!     at errnoException (net.js:905:11)
npm ERR!     at Object.afterConnect [as oncomplete] (net.js:896:19)
npm ERR!  { [Error: connect ECONNREFUSED]
npm ERR!   code: 'ECONNREFUSED',
npm ERR!   errno: 'ECONNREFUSED',
npm ERR!   syscall: 'connect',
npm ERR!   parent: 'hue' }
npm ERR!
npm ERR! If you are behind a proxy, please make sure that the
npm ERR! 'proxy' config is set properly.  See: 'npm help config'
npm ERR! Please include the following file with any support request:
npm ERR!     /ws/build/hue/rpm/BUILD/hue-release-4.5.0/npm-debug.log
make[1]: *** [npm-install] Error 1
make: *** [apps] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.QmZnXL (%build)
Bad exit status from /var/tmp/rpm-tmp.QmZnXL (%build)
FAILURE: Build failed with an exception.
As I guess, npm tries to install packages from https://registry.npmjs.org/, which is unreachable. What's the best way to solve this?
Thanks in advance!

It won't work without Internet, you would need an internal proxy that hosts these packages or tweak npm to have those downloaded beforehand so that it fetches them locally.

It won't work without Internet, you would need an internal proxy that hosts these packages or tweak npm to have those downloaded beforehand so that it fetches them locally.

I made on server with internet:
npm install --no-bin-links
got a node_modules dir with all modules
Then copied it to root directory of hue project on remote server and got the following error while npm run webpack:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/node/bin/node',
1 verbose cli   '/usr/local/node/bin/npm',
1 verbose cli   'run',
1 verbose cli   'webpack' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose node symlink /usr/local/node/bin/node
5 verbose run-script [ 'prewebpack', 'webpack', 'postwebpack' ]
6 info prewebpack<EMAIL_ADDRESS>7 info webpack<EMAIL_ADDRESS>8 verbose unsafe-perm in lifecycle true
9 info<EMAIL_ADDRESS>Failed to exec webpack script
10 verbose stack Error<EMAIL_ADDRESS>webpack: webpack --config webpack.config.js
10 verbose stack Exit status 8
10 verbose stack     at EventEmitter. (/usr/local/node-v0.10.44-linux-x64/lib/node_modules/npm/lib/utils/lifecycle.js:217:16)
10 verbose stack     at EventEmitter.emit (events.js:98:17)
10 verbose stack     at ChildProcess. (/usr/local/node-v0.10.44-linux-x64/lib/node_modules/npm/lib/utils/spawn.js:24:14)
10 verbose stack     at ChildProcess.emit (events.js:98:17)
10 verbose stack     at maybeClose (child_process.js:766:16)
10 verbose stack     at Process.ChildProcess._handle.onexit (child_process.js:833:5)
11 verbose pkgid<EMAIL_ADDRESS>12 verbose cwd /ws/build/hue/rpm/BUILD/hue-release-4.5.0
13 error Linux 3.10.0-957.21.3.el7.x86_64
14 error argv "/usr/local/node/bin/node" "/usr/local/node/bin/npm" "run" "webpack"
15 error node v0.10.44
16 error npm  v2.15.0
17 error code ELIFECYCLE
18 error<EMAIL_ADDRESS>webpack: webpack --config webpack.config.js
18 error Exit status 8
19 error Failed at the<EMAIL_ADDRESS>webpack script 'webpack --config webpack.config.js'.
19 error This is most likely a problem with the hue package,
19 error not with npm itself.
19 error Tell the author that this fails on your system:
19 error     webpack --config webpack.config.js
19 error You can get information on how to open an issue for this project with:
19 error     npm bugs hue
19 error Or if that isn't available, you can get their info via:
19 error
19 error     npm owner ls hue
19 error There is likely additional logging output above.
20 verbose exit [ 1, true ]

Yeah, the only solution I've found - run npm install --no-bin-links on host with internet, and then copy-paste desktop/core/src/desktop/static/desktop/js/bundles/* and webpack-stats* to the remote host. Looks like a fit workaround.
Just a wish - it would be excellent, if hue could be build without internet!
Thanks


V3 paging loadstate

Any plans on merging this anytime soon?

is there a chance this PR would be merged in the future?


CI: Get roxctl for e2e

Description
With https://github.com/openshift/release/pull/29752, e2e tests will run in a test-bin. This PR will give that a roxctl and upgrader.
Checklist

[ ] Investigated and inspected CI test results

Testing Performed
CI is sufficient

/test all

/test gke-nongroovy-e2e-tests

/test gke-upgrade-tests

/test push-images

/test gke-upgrade-tests


'Failed ports' message is missing flavor

In this log the first line has flavors, but the second one doesn't:
[00:02:33] Built ports: archivers/py-python-lzo@py36 biology/py-bx-python@py36
[00:02:33] Failed ports: biology/py-bx-python:build-depends

Is 3.6 default for you or 2.7? It may be related to #542

2.7 is default.

Request was: biology/py-bx-python@py27 biology/py-bx-python@py36

This seems fixed for 3.2.5:
[00:01:10] Built ports: misc/freebsd-release-manifests devel/py-setuptools ports-mgmt/poudriere-devel
[00:01:10] Failed ports: devel/py-six@py36:build


update fpga submodule

This repairs and updates the FPGA subrepo. There was a faulty install path in libxil that broke the Dockerfile in DPsim. See https://github.com/sogno-platform/dpsim/issues/231
There were some commits on a non-master branch, which I removed. I think it's unacceptable to have some branch that diverged from the master in node. Please first merge in the subrepo before updating a submodule here.

now the CI is happy.


Hotfix/fix ci again

Use correct tag for skipping test
Fix failure of JS Driver by avoiding method to grab screenshot (For now)

Going to triple check this first locally running everything to check this "should" now pass!

# iPhone 11 - iOS 13
WARNING: --format=json is deprecated and will be removed after version 5.0.0.
Please use --format=message and stand-alone json-formatter.
json-formatter homepage: https://github.com/cucumber/cucumber/tree/master/json-formatter#cucumber-json-formatter.

Using the reports, passing, html, junit and json profiles...
......--------......................---..........

14 scenarios (3 skipped, 11 passed)
49 steps (11 skipped, 38 passed)
1m6.135s
[12:31:49] luke@luke-VirtualBox:~/Code/design-system$ bundle exec rake design_system:all
# iPhone 8 - iOS 12
Running all design system tests

WARNING: --format=json is deprecated and will be removed after version 5.0.0.
Please use --format=message and stand-alone json-formatter.
json-formatter homepage: https://github.com/cucumber/cucumber/tree/master/json-formatter#cucumber-json-formatter.

Using the reports, passing, html, junit and json profiles...
......--------......................---..........

14 scenarios (3 skipped, 11 passed)
49 steps (11 skipped, 38 passed)
1m5.684s
[12:41:21] luke@luke-VirtualBox:~/Code/design-system$


fix: range in border radius

👨💻 Changes proposed(What did you do ?)

change background colour for border radius

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title and description of the PR is clear and explains the approach.

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


CORS Issue Preventing Build History Page Pagination and Search Functionality

On the build history page, only the first page of data loads correctly. Subsequent data fetches for pagination and search filtering are not working as expected.
When attempting to use the search feature, a CORS error is thrown. We identified that this is due to the absence of certain custom headers required by the search feature in the CORS_HEADERS_ALLOWED list.
After adding these headers, the CORS error is resolved. However, the underlying issue of pagination and search not fetching new data persists. This behavior affects the usability of the build history page, as users are unable to navigate to other pages or filter results effectively.

It appears that the API calls it makes to the backend is same on each page, search or filter - which is causing the issue. Since the request is always the same it only fetches the same data for the first page:
https://art-dash-server-hackspace-martin.apps.artc2023.pc3z.p1.openshiftapps.com/api/v1/builds/?page=2


Serial::usartX(..)  [.unwrap()]

With some  HALs  let txrx1 = Serial::usartX(..)[.unwrap()]; the unwrap is needed and with others it is not. (They give and  error).

The HALs do not provide a consistent API at this level. This has been resolved this by wrapping setup for different HALs and hardware in setup() functions that are board specific.


Make images as condition not text

great job! I have a question that is ok that make images as condition instead of text? for example, as for original dataset the dataset structure is like this:
fill50k/train.jsonl
fill50k/images/X.png
fill50k/conditioning_images/X.png

can i use the conditioning_images as condition, and change the relevent part of the code in here:
class MyDataset(Dataset):
    def __init__(self):
        self.data = []
        with open('./training/cfill50k/prompt.json', 'rt') as f:
            for line in f:
                self.data.append(json.loads(line))

    def __len__(self):
        return len(self.data)

    def __getitem__(self, idx):
        item = self.data[idx]

        image_filename = item['image']
        source = item['source']
        target = item['target']

        image = cv2.imread('./training/cfill50k/' + image_filename)

        # Do not forget that OpenCV read images in BGR order.
        image = cv2.cvtColor(image, cv2.COLOR_BGR2RGB)

        image = (image.astype(np.float32) / 127.5) - 1.0

        return dict(jpg=image, source=source, txt=target)

Thank you!

Hello, have you solved this problem?