Upgrade to qt6 in preparation for OVITO 3.8.0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] ~Reset the build number to 0 (if the version changed)~
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] ~Ensured the license file is being packaged.~

Qt5 support for OVITO will be deprecated with the upcoming release of version 3.8.0. Therefore, the following changes are proposed:

Upgrade from qt5 to qt6
Remove runtime dependence on boost library (only it’s headers are needed to build OVITO)

Additionally, the ‘about’ section has been updated.

@conda-forge-admin, please rerender

-- Found Git: /opt/conda/bin/git (found version "2.39.2")
CMake Error at src/3rdparty/qwt/CMakeLists.txt:24 (FIND_PACKAGE):
  By not providing "FindQt5.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "Qt5", but
  CMake did not find one.

  Could not find a package configuration file provided by "Qt5" (requested
  version 5.12) with any of the following names:

    Qt5Config.cmake
    qt5-config.cmake

  Add the installation prefix of "Qt5" to CMAKE_PREFIX_PATH or set "Qt5_DIR"
  to a directory containing one of the above files.  If "Qt5" provides a
  separate development package or SDK, be sure it has been installed.

-- Configuring incomplete, errors occurred!

Mac OS X ARM fails with:
CMake Error at CMakeLists.txt:69 (FIND_PACKAGE):
  Found package configuration file:

    /Users/runner/miniforge3/conda-bld/ovito_1677881450213/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pla/lib/cmake/Qt6/Qt6Config.cmake

  but it set Qt6_FOUND to FALSE so package "Qt6" is considered to be NOT
  FOUND.

-- Configuring incomplete, errors occurred!

Mac OS X on x86_64 finds the wrong python version:
Found Python3: /Library/Frameworks/Python.framework/Versions/Current/bin/python3.11 (found version "3.11.2") found components: Interpreter
--

This results in the sphinx error:
Found Python3: /Library/Frameworks/Python.framework/Versions/Current/bin/python3.11 (found version "3.11.2") found components: Interpreter
--

@stukowski Is it possible to manually point cmake to the correct python version?

@stukowski Is it possible to manually point cmake to the correct python version?

Yes, in our own recipe we do the following (build.sh & bld.bat):
cmake \
    -DPython3_ROOT_DIR="${PREFIX}" \
    -DPython3_FIND_STRATEGY=LOCATION \
    -DPython3_FIND_VIRTUALENV=ONLY \
    -DPython3_EXECUTABLE=${PYTHON} \
   ...

cmake ^
    -DPython3_ROOT_DIR=%PREFIX% ^
    -DPython3_FIND_STRATEGY=LOCATION ^
    -DPython3_FIND_VIRTUALENV=ONLY ^
    -DPython3_EXECUTABLE=%PYTHON% ^
   ...

I'm not sure about the Qt6 related error on osx/arm64. It is preceded by the message
CMake Error at /Users/runner/miniforge3/conda-bld/ovito_1677881450213/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pla/lib/cmake/Qt6/QtPublicDependencyHelpers.cmake:255 (message):
  To use a cross-compiled Qt, please set the QT_HOST_PATH cache variable to
  the location of your host Qt installation.

which suggests that it is related to cross-compilation. We don't do cross-compilation in our own recipe, so I haven't encountered this kind of issue before. We should check what other conda-forge recipes do to build against Qt6 successfully.

 To use a cross-compiled Qt, please set the QT_HOST_PATH cache variable to
  the location of your host Qt installation.

While the cross compiling looks more promising the Mac Os X build still fails
[ 31%] Linking CXX shared library ../../../lib/ovito/libovito_qwt.dylib
ld: framework not found Metal
clang-14: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [src/3rdparty/qwt/CMakeFiles/Qwt.dir/build.make:1607: lib/ovito/libovito_qwt.dylib] Error 1
make[1]: *** [CMakeFiles/Makefile2:879: src/3rdparty/qwt/CMakeFiles/Qwt.dir/all] Error 2
make: *** [Makefile:146: all] Error 2

While the cross compiling looks more promising the Mac Os X build still fails
[ 31%] Linking CXX shared library ../../../lib/ovito/libovito_qwt.dylib
ld: framework not found Metal
clang-14: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [src/3rdparty/qwt/CMakeFiles/Qwt.dir/build.make:1607: lib/ovito/libovito_qwt.dylib] Error 1
make[1]: *** [CMakeFiles/Makefile2:879: src/3rdparty/qwt/CMakeFiles/Qwt.dir/all] Error 2
make: *** [Makefile:146: all] Error 2

This issue remains even when removing the cross compiling specific parts. I tested that in https://github.com/conda-forge/ovito-feedstock/pull/77

I don't have a good idea yet what is going on here. Unfortunately, I am not familiar enough with the conda-forge build environments.
I looked for other feedstocks that consume the qt6-main package but could not find one so far - aside from pyside6, which is not a regular application. Is there a way to search the conda-forge channel for packages that have qt6-main as a dependency?

you likely have to either disable metal, or bump the OSX SDK:
https://conda-forge.org/docs/maintainer/knowledge_base.html#requiring-newer-macos-sdks
Try to first increase the OSX (features used at compilation time), then the deployment target (what machines can use the final binaries)
See how they can be out of sync at first in qt
https://github.com/conda-forge/qt-main-feedstock/blob/qt6/recipe/conda_build_config.yaml#L4

@conda-forge-admin please rerender

@hmaarrfk  Thanks a lot

Yeah. It's easy to forget to rerender


[$500] Press highlight on a field in expense details overlaps with error message weirdly

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

Version Number: 1.4.29-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @luacmartins
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1705808584924989
Action Performed:
Precondition : Have some violation rules for the expenses in the OD

Create an expense report
Open the receipt to view the details
enter the required fields values (in this case category and tag fields)
Long press the category/tag field to highlight and observe

Expected Result:
There should be no overlapping.
Actual Result:
overlaps the error message weirdly
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

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

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

Screenshots/Videos
Add any screenshot/video evidence

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

Upwork Job URL: https://www.upwork.com/jobs/~01b61739c3e4f7859e
Upwork Job ID:<PHONE_NUMBER>960947200
Last Price Increase: 2024-01-23

Proposal
Please re-state the problem that we are trying to solve in this issue.
Highlighted area doesn't include the full row when there's an error message
What is the root cause of that problem?
The highlight style doesn't grow into  full row when there's an error message.
What changes do you think we should make in order to solve the problem?
We should update the styling to flex the highlighted area based on the content, inccluding the error message
What alternative solutions did you explore? (Optional)

Proposal
Please re-state the problem that we are trying to solve in this issue.
Error message out of hover frame
What is the root cause of that problem?
Inside src/components/ReportActionItem/MoneyRequestView.js we are displaying the error message via ViolationMessages but the only hovered component is MenuItemWithTopDescription
What changes do you think we should make in order to solve the problem?
The MenuItemWithTopDescription support displaying error via already existant props errorText.
We should pass the violation message throw it and remove ViolationMessages component.
POC:

Seems like a dupe of https://github.com/Expensify/App/issues/33527. @cead22 can you confirm if we're already fixing this?

Yeah


Alternative interaction pattern: clicking

In addition to shift-enter and the keyboard shortcuts, we should also be able to edit the notebook via clicking.

Agreed. My preference though is to keep any buttons for adding cells, moving them, etc as unobtrusive as possible.

See #50 for a proposed "new cell" click target.

Between #50 and #130, I consider this issue to be resolved. Clicking will also be involved in moving or deleted cells, but we have separate issues tracking those features.


Histograms/promtool tests

Fixes https://github.com/prometheus/prometheus/issues/11170
Replacement for #11381

@hdost do you know if you will be able to work on this anytime soon?

Yes I have actually done some work , are the meetings still happening because I've tried joining a couple times, maybe i have the time wrong.
Currently, the existing grammar tooling is hard to debug (possibly due to the form I'm trying to create the input format)
I've started experimenting with using some different tooling altogether using a PEG grammar the initial creation has been better and the project/tooling around it is a bit better.
However this is a bit of a bigger change than I think we might want to go down, but it removes quite a bit of the ambiguity.
After reading the recent document around exposing metrics perhaps I might take a different angle on the format.
I'll put together a small post in thoughts around the format and ingestion design.

I could not find anywhere what the syntax is supposed to be. I just found a suggestion comment in the linked issue. I have created this doc to collaborate on the syntax and few examples for reference before we dive into the parser.

:wave: from the bug scrub.
We believe this has been superseded by more recent work on the testing framework. @hdost if you disagree, please follow up.
We'll close this for now.


💥 [DevOps] Testplan

💥 DevOps ticket

Create a Testplan which can be reused until we have cypress fullstack tests. This Testplan can be used to generate userstories as well.

What we test?
How we test?
When we test?
How much effort does each test have

Testplan

Test with staging data
Test with live data on staging

New Frontend

Test Login time on staging, still 2.5 seconds?
Send gdd - is the input sensitive to the , and . separators depending on the language?
login, logout
login, logout, login when this user just got gdd he never seen before - balance correct
password rest works
send gdd, balance correct, everything immediately updated?
balance & transactions is correct when loggin in & out two users

Old Frontend

Register still works?
Schöpfen funktioniert noch?
User suchen funktioniert
Balance & transactions correct?
Old Frontend same as new Frontend regarding balance & transactions?

@einhornimmond @Mogge

Reloading (F5) page of frontend failed with 404 Not Found

GDT is to short, is has only 2 decimals and need therefore only divided by 100.

In new frontend you can send yourself gradidos, than the transaction is display two times.

Wrong email is sended with password reset

Altes frontend muss gestestet werden!


[eas-cli] utils: amend rollouts definition

Why
Amend the definition of a rollout branch mapping to be position aware. For example, this is a valid rollout:
[
    {
      branchId: uuidv4(),
      branchMappingLogic: {
        operand: 10 / 100,
        clientKey: 'rolloutToken',
        branchMappingOperator: hashLtOperator(),
      },
    },
    { branchId: uuidv4(), branchMappingLogic: alwaysTrue() },
  ]

However, if the array items are switched, it should not be considered a rollout anymore. This is because we evaluate each item in the branch mapping like a switch statement. So in this example, it will always evaluate to true in the first statement and never evaluate the second:
[
    { branchId: uuidv4(), branchMappingLogic: alwaysTrue() },
    {
      branchId: uuidv4(),
      branchMappingLogic: {
        operand: 10 / 100,
        clientKey: 'rolloutToken',
        branchMappingOperator: hashLtOperator(),
      },
    }
  ]

Test Plan

[ ] amended tests pass

/changelog-entry chore amend branch mapping utility functions


Error on class OneSignal

Hi.
I tried to use your lib but I am getting the error:

Fatal error: Arrays are not allowed in class constants in /home/datalabs/public_html/tsca/app/OneSignal.php on line 40

which refers to:
const METHODS = ['GET', 'POST', 'PUT', 'DELETE'];
Was your lib working correctly?
PS: Thanks for creating and sharing the lib btw.

You'll need at least PHP 5.6。:)

I am... (PHP Version 5.6.30).

Really?
I'm sure arrays can be allowed in class constants after PHP 5.6. (https://secure.php.net/manual/en/migration56.new-features.php)
Please check your php version again.
Please restart your php-fpm process if you update your php.
I hope it's helpful. :)

You can check whether you have been install multiple versions of PHP.
Please run php -v or which php or where php to check it.


Submission_2213054_2213858_2210147_2212113

MEMBER

Lam Hoang Tan - 2213054 - Leader
Vo Quoc Tu - 2213858
Truong Nguyen Hoang Anh - 2210147
Nguyen Tran Khoa My - 2212113

POLICY DESCRIPTION
Column Generation (policy_id = 1)
Column Generation is an optimization method used to solve large-scale cutting stock problems by iteratively generating new patterns to improve the solution. The algorithm starts by using a set of initial patterns and then solves a linear programming (LP) relaxation of the problem. In each iteration, it solves a pricing problem to generate new patterns that can potentially reduce waste and improve material utilization. By adding these new patterns to the model, the algorithm narrows down the feasible solutions, ultimately arriving at the optimal cutting pattern. Column Generation helps efficiently tackle problems with large numbers of patterns and constraints, making it particularly useful in industries like textiles and manufacturing.
Implement details: None
Genetic Algorithm (policy_id = 2)
The Genetic Algorithm (GA) is a population-based search technique that is applied to solve the cutting stock problem through evolutionary principles. It generates an initial population of candidate solutions, each represented as a chromosome (a set of cutting patterns). Over multiple generations, the algorithm selects the best individuals based on a fitness function that evaluates material utilization and waste reduction. The algorithm then applies crossover and mutation operations to create new candidate solutions. This process is repeated for several generations, improving the solution until a near-optimal cutting pattern is found. The Genetic Algorithm is particularly effective in solving complex and large-scale cutting stock problems where traditional optimization methods may be less efficient.
Implement details: population_size=300, penalty=2, mutation_rate=0.1, MAX_ITERATIONS = 150
RESULT
Here the result when we run the first 100-espisode in this policy with seed = 42:

Policy
Average Filled Ratio
Average Trim Loss
Average Execution Time

Random
0.08
0.4122
29.15 seconds

Greedy
0.0613
0.5325
25.74 seconds

Column
0.1950
0.5694
23.62 seconds

Genetic
0.1374
0.4642
399.07 seconds

We had a small problem with GitHub and accidentally deleted the old PR. Can you merge this new pull request? We sincerely apologize for our mistake.

During the submission process, we encountered many problems. If there are any mistakes, we hope you will forgive us and merge them for us.


Builder + Space Chamber: can't place redstone on blocks

When using the Builder with a Spatial Chamber that contains a build in which redstone is used, the Builder will not be able to replicate the design. The Space Chamber Card does indicate the need for redstone but the Builder is unable to place it.
Would it be possible to make it so it can?

Aww derp, doing an automation of Compact Machine using RfTools builder to copy the exact needed construction to insert into the compacter area. Could not understand why the redstone did not copy over.
Ironblock with Redstone on top is not able to Copy, but Move from the Space Chamber works all fine.

Bump because automating compact machines needs something like this.

Did something change? I've managed to make the builder place redstone in copy mode this time.

Thanks.


Convert gen_oscal.sh to py and fix test to run on windows

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Convert gen_oscal.sh to py and change Makefile accordingly.
Now sort class names in fix_any.py in hopes output files don't change as much.
Fix directory creation test that was failing on windows.

Okay I had a quick look at this - so the issue which I think we will want to fix first is the fact flake8 / yapf are not covering the scripts folder.
In .pre-commit-config.yaml replacing both lines which are
        files: "^(trestle|tests)"

with
        files: "^(trestle|tests|scripts)"

will enable flake8 and yapf. My suggestion would be we fix this first for this patch.


Remove destructuring from examples webpack configs so they run in Nod…

…e < 6.
Per discussion here.

Should we also include an update of the main README that we support Node >=4 for running examples, and Node >= 6 for development of core library?

Should we also include an update of the main README that we support Node >=4 for running examples, and Node >= 6 for development of core library?

We should. @ericsoco can you add this to the main README with this change?


Add nominee: Productive Forests

Automatic addition of a new nominee submitted through the online form available at https://digitalpublicgoods.net/submission

@nathanbaleeta This looks good to me, thanks! 👍


Windows Vista not supported (PSAPI version)

I am using Windows Vista. I downloaded the BLT, extracted both folders (Mods and IPHLPAPI.dll) into the Payday 2 Folder. I downloaded the vcredist_x64.exe and vcredist_x84.exe. When I open the game from Steam, I get the error," Engine has stopped working." When I open the game from the Payday 2 Folder, I get," The procedure entry point K32GetModuleInformation could not be located in the dynamic link library KERNEL32.dll, followed by Engine has stopped working. When I remove the IPHLPAPI.dll, the game works normally. (I do not have any other addons like Hoxhud)
Okay I got a reply saying Vista doesn't work yet.

Thanks for reporting this issue.
The call K32GetModuleInformation is only available in PSAPI version 2 and greater (Windows 7 and greater)
We are working on a fix, however it requires the disuse of C++11 features, which are core to multi-threading compatability.

Re-opening (but renaming) issue.
This is a known issue that needs to be solved.

Got it running. No changes needed to the code. I followed the MSDN documentation (https://msdn.microsoft.com/en-us/library/windows/desktop/ms683201(v=vs.85).aspx). Define PSAPI_VERSION = 1 (In preprocessor definitions in the project settings) and including the library "psapi.lib".

I kinda read that solution as a hotfix. Then again, BLT is already very hacky.
Make a PR and I'll merge, but I don't feel capable of committing the mortal sin of intentionally writing hacky code.

Is there a compiled version of this available for download?
On Fri, Jul 3, 2015 at 12:27 AM, Waddlesworth<EMAIL_ADDRESS>wrote:

I kinda read that solution as a hotfix. Then again, BLT is already very
hacky.
Make a PR and I'll merge, but I don't feel capable of committing the
mortal sin of intentionally writing hacky code.
—
Reply to this email directly or view it on GitHub
https://github.com/JamesWilko/Payday-2-BLT/issues/10#issuecomment-118249895
.

+1 on is there a compiled version available, I wasn't able to resolve the dependencies to get the project compiling

SirWaddles. There is no modification to the code necessarily needed. You need to add Psapi.lib to the TARGETLIBS macro and compile the program with -DPSAPI_VERSION=1. There is no way we can add that in to your source code because it relates to compilation rather than the actual code.

Any progress on this?  A team member of mine is stuck on vista and is still awaiting a compatibility fix.

There are no plans to officially support anything except Windows 7, 8, and 10.


Rev GATK public dependency to 4.alpha.2-188-g7332d10-20170321.172613-1

This includes a fix to gatk-launch

@lbergelson please review

@takutosato With this merged, you should be able to update your master, run ./gradlew clean installDist, grab the updated gatk-launch, and use it for your M2 jobs. Let me know if this doesn't fix your problem!


Add FUTURE criteria: SUGGESTED link to badge entry

Currently users and potential co-developers can’t easily see if a project they’re looking at has a badge. In addition, if the badge is to be useful, people need to know that the badging project exists (without having to go to a website that they don’t know exists).
Here’s a potential FUTURE criteria – thoughts?
It is SUGGESTED that the project website, or front page of its repository, provide a link to its CII badge entry, including a graphic showing its current status.  DETAILS: If it’s on the project website it doesn’t need to be on its front page.  If the project website and repository front page are different, and it’s possible to put the badge status information on both, we encourage putting it on both.

Let's start by adding this to draft passing+1, but instead of focusing on the badge, let's require that projects document all their achievements whatever they are.  Draft criterion documentation_achievements added as commit 48c107a43d8a0529103fde375b3f58f49604b15d.

In the further future, we might add this to the "passing" level as a SHOULD or SUGGESTED criterion, but let's investigate this as passing+1 first.  Since a draft has been moved to other.md, I'm closing this issue.


No element found for selector: textarea

Hello! Make sure you use await ... or .then() to catch the promise after node_perplexityai is ready. The API is returning this error because it's trying to type in the input box on www.perplexity.ai, but the API is currently not ready.
Please re-open this issue if you get any other errors!

const perplexity = require("node_perplexityai");
const prompt = "What is brain";
(async () => {
const result = await perplexity.send(prompt);
console.log(result);
})();
Still getting same issue
this was the code

Ok, thanks for pasting the code. I'll look into it and see what's causing this issue.

Ok, it seems I just need to add a waitForSelector(...) in puppeteer before the message is sent. I'll push an update tomorrow and keep you updated!

Hey, I've added the waiting function. Could you try a fresh install and restart your script? Thanks!

looks like it cant bypass cloud flare

Oh yeah, cloudflare updated there bot blockers, I'll have to do a major fix on this. Thanks for your patience, I'll try to fix it ASAP.
FYI This will be easy to fix because I have a personal API for another site using cloudflare, and I've used the puppeteer stealth plugin and mixed in some headers, it worked. I'll just do the same for this.
Check back in tomorrow!

Reopening this issue because it's confirmed not working at all. I'll keep you updated

Problem fixed. Let me know if you have any more problems.


Readme-described model missing (and other models cannot be loaded)

Hello, thanks for sharing your code. I don't see a file named tusimple_lanenet_vgg.ckpt in the Dropbox.
When I try any of the other files in the Dropbox, I see:
DataLossError (see above for traceback): Unable to open table file ./model/tusimple_lanenet_vgg.ckpt.data-00000-of-00001: Data loss: not an sstable (bad magic number): perhaps your file is in a different file format and you need to use a different restore operator?
	 [[node save/RestoreV2 (defined at tools/test_lanenet.py:94) ]]

@johnwlambert use tusimple_lanenet_vgg.ckpt instead of tusimple_lanenet_vgg.ckpt.data-00000-of-00001


changes

Quite a bit of stuff seems to have changed very subtly in the past hour or two (maybe the new library)

The font looks different. Its definitly a different colour... (and its a different colour from the menu font, more garish blue)
I think the menu formatting might have changed too

how it looks now:

from my last screenshot, def different font, and colour...

I don't know which is better

[ ]  Show details no linger looks like a linky

What are the fonts? The  new one seems to be the one which everything is moving to.
I like the new one in the big blocks, but the old font works better in the menu, it must be slightly narrower so its a bit more compact....

I've done some screenshots (with a convenient tab containing a gene page loaded last night) and convinced myself that with the computer/browser combination I used, it's the same typeface; only the size has changed.
I do see the color changes, and I think I like the new left-hand menu color, but not the new color for all the links in the page body. I'm fairly sure that it was just using my browser default link color before the changes.
It would be very good if show/hide details resumed looking linkish.

Quite a bit of stuff seems to have changed very subtly in the past hour or two (maybe the new library)

Sorry about that.  On my screen it didn't look very different with the new library.  But I've been spotting little quirks too now I look closer.
I've completely reverted that change and I'll have another go after release.  Upgrading would have made a few things easier but it can wait.
It should now be back as it was.  Could you have a quick look and close this if it's OK?

I haven't spotted any problems.
That's a pain....

OK, please open new issues if you spot any other problems.


CONTRIBUTING Documment added

Revision needed for Contribution File

@BioDocker/contributors Can anyone review this pull-request


🐛 [cloud_firestore] Not getting live chat message data same time on multiple devices.

I am creating one chat application using Cloud Firestore. When I send messages from two devices at the same time then I am not able to receive messages on any one device. It is only working with a single device when the timeframe is the same for sending the messages.
Here is my code for receiving live messages :
FirebaseFirestore.instance
.collection('conversations')
.doc(convoID)
.collection("messages")
.orderBy("sent_date", descending: true)
.limit(1)
.snapshots()
.forEach((element) {
AppUtil.printData( "== MESSAGE RECEIVED ==");
});

@Javed-Sheta
Your question is better suited for support channels like StackOverflow, so please ask the same there.
Also check this video and see if it helps in your case: https://www.youtube.com/watch?v=DqJ_KjFzL9I
Closing from here, as this is more of a support question rather than bug or feature request.


modules/rosetta: configure nix build sandbox to use rosetta

Description of changes
With this we can do x86_64 builds on aarch64
Things done

Built on platform(s)

[ ] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Is there a command I can run on aarch64-darwin to test this by building an x86_64-linux derivation?

I will add a derivation to the PR that can be run for manual testing. I'll add one now

Ah specifically aarch64-darwin? Not that I know of. There might be a CLI for Virtualisation.framework. I've been using the utm.app GUI to test this.

I'm confused, I thought rosetta was the x86_64 virtualization layer on M1 Macs. Is this for Linux installed on M1 Macs or something?

When running a NixOS VM through virtualisation.framework Rosetta is available inside the VM

Given this is not really automatable by test and the way to check is "build any nix derivation" I don't think there is a need to add any further testing code. I'm going to merge as is


GitHub commit link is broken

What App Center service does this affect?
Build service
Describe the bug
In the build report, we have a link to the corresponding commit where the build is based in GitHub.
This link is missing one url part. The link has this pattern https://github.com/<repo><commit> but the corret to link back to github is https://github.com/<repo>/commit/<commit>
To Reproduce
Steps to reproduce the behavior:

Go to a build page
Click on the commit link
See a github 404 error

Expected behavior
An example broken commit link is https://github.com/gmsantos/TailwindTraders_6495qzpadb35eb0547b80de4c6e4275a7cb1625559e6d27b
Actually it should be
https://github.com/gmsantos/TailwindTraders_6495qzpa/commit/db35eb0547b80de4c6e4275a7cb1625559e6d27b
Screenshots

@gmsantos Thanks for reporting the bug! I wasn't able to reproduce the bug myself. We get the commit url from GitHub, which seems odd that this would happen. Let us investigate this a bit and I will get back to you.

I have created this repo using the App Center Demo Generator. I hope that help with the bug reproduction or the investigation.

@gmsantos are you still running into this issue? We were unable to repro this. Will close this out, but feel free to reopen if you still have the issue.


You are Jeff Boxos - and you must complete 27 (soon to be more) challenges to complete the game. You will be faced with obstacles, puzzles, and more (also known as "idfk what else"). The game is approximately 30 minutes or so for a new player.

How do you play your game?

W/A/S/D to move, J/L to switch level, I to reset
Code
Check off the items that are true.

[x] The game was made using the Sprig editor.
[x] The game is placed in the in the /games directory.
[x] The code is significantly different from all other games in the Sprig gallery (except for games labeled "demo").
[x] The game runs without errors.
[x] The name of the file/game contains only alphanumeric characters, -s, or _s.
[x] The game name is not the same as the others from gallery

Image (If an image is used)

[ ] The image is in the /games/img directory.
[ ] The name of the image matches the name of your file.

Thanks for your PR!

NOTE: ignore the other commits they're already merged into main, idk what WebStorm was cooking

This is an amazing game! It's very creative and challenging, and the variety of levels is incredible!!


[GH-549] fix transition slack attachment transition

Summary
In the case that a transition name does not match the to state in the slack attachment options picker, the user would receive an error such as below:
Note that Start Progress in this case is the transition name and the list In Progress, Solved, Close are the states.
2020-05-26T13:45:03.351+0200    error   mlog/sugar.go:23        ERROR:  {"plugin_id": "jira", "Status": "500", "Error": "\"Start Progress\" is not a valid state. Please use one of: \"In Progress, Solved, Closed\"", "Host": "", "RequestURI": "", "Method": "POST", "query": ""}
To fix this, the options picker value needs to be the state name, not the transition name.  The current modification will show the transition name in the picker, but the underlying value will be the to state
Testing
I modified my jira testing project. Jira link
In that instance I made the following workflow change (note the subtle spelling change)
From:
transition name: Backlog
to state name: Backlog
To:
transition name: Backlog
to state name: Bcaklog
Ticket Link
Fixes: #346

Codecov Report

Merging #581 into master will decrease coverage by 0.04%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #581      +/-   ##
==========================================
- Coverage   34.00%   33.96%   -0.05%
==========================================
  Files          37       37
  Lines        4602     4602
==========================================
- Hits         1565     1563       -2
- Misses       2888     2890       +2
  Partials      149      149

Impacted Files
Coverage Δ

server/issue_parser.go
0.00% <0.00%> (ø)

server/subscribe.go
65.55% <0.00%> (-0.40%)
: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 6e4ec47...00bc500. Read the comment docs.

@DHaussermann ping for review


crash via tf_should_use format_stack

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): no
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 16.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: -
TensorFlow installed from (source or binary): binary (pip)
TensorFlow version (use command below): v1.11.0-0-gc19e29306c 1.11.0
Python version: 3.6.3
Bazel version (if compiling from source): -
GCC/Compiler version (if compiling from source): -
CUDA/cuDNN version: 8.0
GPU model and memory: GTX 680 (will not be used)
Exact command to reproduce: -

Describe the problem
When __repr__ is called on some TF objects at the wrong time, this can lead to a crash (seg fault; see below). There can be various reasons why this can happen, e.g. when a debugger shows the locals of all threads. My case was this, but I think this doesn't matter:

Via better_exchook, I extended the output of sys.excepthook and some traceback functions to print out some local vars and their __repr__ output. There is something similar for IPython.
I created some tf.TensorArray and called unstack and I did not use the result value. That unstack method is wrapped via should_use_result.
The Python GC called the _TFShouldUseHelper.__del__ function at some random point, and this triggered the stack formating and then the call some some __repr__ of some TF objects.

Originally, this happened at exit, and I thought that probably it's just not safe at exit to touch any existing TF objects. So I fixed that case in better_exchook: It will not print any vars at exit. A test case to reproduce exactly that case is here.
However, now I get the same crash also not at exit but at another random point (see stack below). It will be hard to come up with a test case for this, as it is very non-deterministic when exactly the GC runs and calls the __del__ function.
Source code / logs
Current thread 0x00007f14209e8700 (most recent call first):
  File "/u/zeyer/py-envs/py36-tf111/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 1897 in name
  File "/u/zeyer/py-envs/py36-tf111/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 352 in name
  File "/u/zeyer/py-envs/py36-tf111/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 614 in __repr__
  File "/u/zeyer/setups/librispeech/2018-02-26--att/returnn/tests/../better_exchook.py", line 250 in pretty_print
  File "/u/zeyer/setups/librispeech/2018-02-26--att/returnn/tests/../better_exchook.py", line 487 in format_py_obj
  File "/u/zeyer/setups/librispeech/2018-02-26--att/returnn/tests/../better_exchook.py", line 571 in <lambda>
  File "/u/zeyer/setups/librispeech/2018-02-26--att/returnn/tests/../better_exchook.py", line 522 in _trySet
  File "/u/zeyer/setups/librispeech/2018-02-26--att/returnn/tests/../better_exchook.py", line 571 in format_tb
  File "/u/zeyer/.linuxbrew/opt/python3/lib/python3.6/traceback.py", line 37 in format_list
  File "/u/zeyer/.linuxbrew/opt/python3/lib/python3.6/traceback.py", line 193 in format_stack
  File "/u/zeyer/py-envs/py36-tf111/lib/python3.6/site-packages/tensorflow/python/util/tf_should_use.py", line 60 in __del__
  File "/u/zeyer/py-envs/py36-tf111/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 81 in __init__
  File "/u/zeyer/py-envs/py36-tf111/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 4181 in _add_device_to_stack
  File "/u/zeyer/py-envs/py36-tf111/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 4243 in device
  File "/u/zeyer/.linuxbrew/opt/python3/lib/python3.6/contextlib.py", line 81 in __enter__
  File "/u/zeyer/py-envs/py36-tf111/lib/python3.6/site-packages/tensorflow/python/ops/control_flow_ops.py", line 3366 in _GroupControlDeps
  File "/u/zeyer/py-envs/py36-tf111/lib/python3.6/site-packages/tensorflow/python/ops/control_flow_ops.py", line 3415 in group
  File "/u/zeyer/py-envs/py36-tf111/lib/python3.6/site-packages/tensorflow/python/ops/control_flow_ops.py", line 3486 in tuple
  File "/u/zeyer/py-envs/py36-tf111/lib/python3.6/site-packages/tensorflow/python/ops/gradients_impl.py", line 791 in _GradientsHelper
  File "/u/zeyer/py-envs/py36-tf111/lib/python3.6/site-packages/tensorflow/python/ops/gradients_impl.py", line 596 in gradients
  File "/u/zeyer/py-envs/py36-tf111/lib/python3.6/site-packages/tensorflow/python/training/optimizer.py", line 517 in compute_gradients
  File "/u/zeyer/py-envs/py36-tf111/lib/python3.6/site-packages/tensorflow/python/training/optimizer.py", line 401 in minimize
  File "tests/test_TFNetworkRecLayer.py", line 219 in test_rhn_nan
  File "tests/test_TFNetworkRecLayer.py", line 2175 in <module>

"ops.py", line 1897 in name, that is this code:
  @property
  def name(self):
    """The full name of this operation."""
    return c_api.TF_OperationName(self._c_op)

I often also see this just before the crash:
pure virtual method called

A Travis log with this crash can also be seen here, or here.
The C backtrace is this:
/lib/x86_64-linux-gnu/libpthread.so.0(raise+0x29)[0x7f7e8df1a269]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7f7e8df1a390]
/u/zeyer/py-envs/py36-tf111/lib/python3.6/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so(TF_OperationName+0xa)[0x7f7e5ccc0eca]
/u/zeyer/py-envs/py36-tf111/lib/python3.6/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so(+0x1982264)[0x7f7e5ca78264]
/u/zeyer/.linuxbrew/Cellar/python3/3.6.3/lib/libpython3.6m.so.1.0(_PyCFunction_FastCallDict+0x209)[0x7f7e8e1f61c9]
...

@ebrevdo any idea what could be causing this?

My guess: Some Swig internals, which do not expect a thread change in certain context (which is triggered here by the Python GC calling __del__ in some unexpected context).

@allenlavoie may have insight.

Nothing jumps out to me as an obvious cause. Sounds like this needs debugging, and without a more concrete reproduction I'm not sure there's much to be done.
Is there a loop you can construct which eventually results in this bug being triggered?

Nagging Assignee @ebrevdo: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @ebrevdo: It has been 29 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

I removed better_exchook (removed the import, and the two commands in main) and still am no able to replicate in py3.5

See my earlier explanation. Only with better_exchook you can trigger this
crash.
Am Do., 22. Nov. 2018, 08:34 hat ebrevdo<EMAIL_ADDRESS>geschrieben:

I removed better_exchook (removed the import, and the two commands in
main) and still am no able to replicate in py3.5
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/22770#issuecomment-440864313,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADm_IWoiR4eA4WIOBZ5tbeIXC5NLRDSks5uxfEFgaJpZM4XKiRX
.

ok i was able to replicate the issue.  gonna see if i can run this under address sanitizer...

So, to make it clear: There is a Python object which corresponds to a graph in C++ which does not exist anymore, or has become invalid? How is this possible? This is via Swig, right? I thought that Swig does some sort of reference counting.
Or does the C++ graph object itself still exists, but accessing it becomes invalid? Is there a flag or so that marks that the object is invalid now? Maybe there should just be a check for this flag and if the object is invalid, any related functions should return some sane value (None or so) or throw a Python exception, instead of this crash?
I feel like cleaning/sanitizing the stack trace to try to avoid any possible access to such objects is just a workaround to the problem.

I tried to write some simpler test case. See the commit I just referenced. That code sometimes crashes in various different way.

Oh interesting, good find. So maybe we just need to set some Python properties to None when the destructor for the C Graph object runs? https://github.com/tensorflow/tensorflow/blob/73f193aa4b9999e0a5bf7d29b1838e2a662e9507/tensorflow/python/framework/c_api_util.py#L52

Hi @albertz !
It is not crashing now in 2.x version any more. Attached gist for reference.
Thank you!

@mohantym Is this also for the code in https://github.com/albertz/playground/commit/114bcaf7abe9da0c083ec64e01bac2357806d523 ?
What was done to resolve this?

@albertz !
I have used compatibility mode as it was originally 1.x codebase (updated comments in code ). Yeah , I got the code from your Github repo only.
Thank you!

Yeah , I got the code from your Github repo only.

In your gist, you had the initial code here in this issue, but I was referring to this simplified code: https://github.com/albertz/playground/commit/114bcaf7abe9da0c083ec64e01bac2357806d523

Hi @albertz !
I am facing an attribute error with new code. Attached gist for reference.
Thank you!

@albertz !
I am observing a different behaviour in 2.9 and nightly. Could you let us know from your end.
Thank you!

I can replicate the error in tf-nightly.  in Python 3.10.  Running in gdb, here's the stack trace at segfault:
Thread 1 "python3" received signal SIGSEGV, Segmentation fault.
__strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
74	../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory.
(gdb) bt
#0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
#1  0x00007fffbc50f975 in pybind11::detail::type_caster<char, void>::cast(char const*, pybind11::return_value_policy, pybind11::handle) ()
   from /home/ebrevdo/.local/lib/python3.10/site-packages/tensorflow/python/client/_pywrap_tf_session.so
#2  0x00007fffbc52d350 in pybind11::cpp_function::initialize<char const* (*&)(TF_Operation*), char const*, TF_Operation*, pybind11::name, pybind11::scope, pybind11::sibling, pybind11::call_guard<pybind11::gil_scoped_release> >(char const* (*&)(TF_Operation*), char const* (*)(TF_Operation*), pybind11::name const&, pybind11::scope const&, pybind11::sibling const&, pybind11::call_guard<pybind11::gil_scoped_release> const&)::{lambda(pybind11::detail::function_call&)#3}::_FUN(pybind11::detail::function_call&) ()
   from /home/ebrevdo/.local/lib/python3.10/site-packages/tensorflow/python/client/_pywrap_tf_session.so
#3  0x00007fffbc5359a1 in pybind11::cpp_function::dispatcher(_object*, _object*, _object*) ()
   from /home/ebrevdo/.local/lib/python3.10/site-packages/tensorflow/python/client/_pywrap_tf_session.so
#4  0x00005555556dbfee in ?? ()
#5  0x00005555556d2c93 in _PyObject_MakeTpCall ()
#6  0x00005555556cc65d in _PyEval_EvalFrameDefault ()
#7  0x00005555556dc798 in _PyFunction_Vectorcall ()
#8  0x00005555556c6ee7 in _PyEval_EvalFrameDefault ()
#9  0x00005555556dc798 in _PyFunction_Vectorcall ()
#10 0x00005555556c6ee7 in _PyEval_EvalFrameDefault ()
#11 0x00005555557aaa22 in ?? ()
#12 0x00005555557aa962 in PyEval_EvalCode ()
#13 0x00005555557d1374 in ?? ()
#14 0x00005555557cbbdb in ?? ()
#15 0x00005555557d1121 in ?? ()
#16 0x00005555557d0754 in _PyRun_SimpleFileObject ()
#17 0x00005555557d04b3 in _PyRun_AnyFileObject ()
#18 0x00005555557c42ca in Py_RunMain ()
#19 0x000055555579ee19 in Py_BytesMain ()
#20 0x00007ffff7c337fd in __libc_start_main (main=0x55555579ede0, argc=2, argv=0x7fffffffde18, init=<optimized out>, fini=<optimized out>,
    rtld_fini=<optimized out>, stack_end=0x7fffffffde08) at ../csu/libc-start.c:332
#21 0x000055555579ed1a in _start ()

(that said, the new tf2 code calls tf.disable_v2_behavior(), which drops you back in TF1-mode.  I don't know the support story for this anymore...)

Hi,
Thank you for opening this issue. Since this issue has been open for a long time, the code/debug information for this issue may not be relevant with the current state of the code base.
The Tensorflow team is constantly improving the framework by fixing bugs and adding new features. We suggest you try the latest TensorFlow version with the latest compatible hardware configuration which could potentially resolve the issue. If you are still facing the issue, please create a new GitHub issue with your latest findings, with all the debugging information which could help us investigate.
Please follow the release notes to stay up to date with the latest developments which are happening in the Tensorflow space.


migrate LifecycleOwner into commonMain

With lifecycle dependency from jetbrains, we can migrate some LifecycleOwner and SavedStateRegistryOwner codes from androidMain to commonMain, it will be easier for daily development.
maybe fix #410, #431

I just found this feature has been implemented,  what a surprise!


Update managed-policies.md

Specifying that the below policies are acquired through SD transition

@MicrosoftGuyJFlo
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


getRadioCapabilities: reduce verbose logging

Since printf is used for logging there is no way to configure the ammount of logs printed.
getRadioCapabilities prints excesivelly each time it's called. Change that so that logs are only printed when there was an error.
Signed-off-by: Piotr Nakraszewicz<EMAIL_ADDRESS>Signed-off-by: Piotr Nakraszewicz<EMAIL_ADDRESS>

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/13433/ started

https://jenkins.code.rdkcentral.com/job/github-triggered/19860/ started

https://jenkins.code.rdkcentral.com/job/build-component/55103/ started.


The coordinate type of 3D pose

Dose the network output the camera coordinate of 3D poses?

For 3D pose estimation, the network output is in normalized coordinates (roughly [-1,1]) and can be associated with the pixel coordinates.


Command atcab_sha_hmac_init is failed with status 0xf4

I'm trying to generate a hmac digest. I am using slot 6 for this which is configured like this:
=========================  Slot: 6   ==================
Decoding SlotConfig value = 0x0F8F
Read key (except ECC private keys): 15
 If slot contains ECC private keys:
  External signatures of arbitrary messages are enabled: 1
  Internal signatures are enabled: 1
  ECDH operation is permitted for this key: 1
   ECDH master secret output mode: 1
NoMac bit: 0
LimitedUse bit: 0
EncryptRead bit: 0
IsSecret bit: 1
Write key: 15
Write config: 0x0 (hex) = 0000 (bin)
  Write cmd: Always
  DeriveKey cmd: Can't be used
  GenKey cmd: may NOT be used
  PrivWrite cmd: Forbidden
-------------
Decoding KeyConfig value = 0x007C
Private bit: 0
PubInfo bit: 0
KeyType: 7 [SHA or other]
Lockable bit: 1
ReqRandom bit: 1
ReqAuth bit: 0
AuthKey: 0
IntrusionDisable bit: 0
X509id: 0

The configuration zone is locked and I can interact with the i2c device.
Then I create a random key:
head -c 16 /dev/urandom > hmac.key

I can write the key (works only with less than 32 bytes):
atecc -b1 -c "hmac-write-key 6 0 hmac.key"
read key from file: Success

Then I try to digest a message:
echo "This is a test" > message
touch hmac.digest
# Usage: hmac-dgst <slot_id> <payload_file> <hmac_output>
atecc -b1 -c "hmac-dgst 6 message hmac.digest"
Command atcab_sha_hmac_init is failed with status 0xf4

Do I miss something? Is it necessary to lock the slot 6 before calculating the hmac? Is KeyType  7 [SHA or other] correct?
Thanks in advance for any pointers to get more familiar with atecc-util!

Could you please try the following patch:
diff --git a/atecc.c b/atecc.c
index 37312df..184d3ab 100644
--- a/atecc.c
+++ b/atecc.c
@@ -135,6 +135,7 @@ int main(int argc, char *argv[])
     ATCAIfaceCfg cfg = cfg_ateccx08a_i2c_default;
     cfg.atcai2c.bus = DEFAULT_I2C_BUS;
     cfg.atcai2c.slave_address = DEFAULT_I2C_SLAVE;
+    cfg.devtype = ATECC608A;

     while ((c = getopt(argc, argv, "h::c:b:s:vr:")) != -1) {
         switch (c) {

Is KeyType 7 [SHA or other] correct?

Yes
It works for me with the following slot config:
=========================  Slot: 7   ==================
Decoding SlotConfig value = 0x4AC9
Read key (except ECC private keys): 9
 If slot contains ECC private keys:
  External signatures of arbitrary messages are enabled: 1
  Internal signatures are enabled: 0
  ECDH operation is permitted for this key: 0
   ECDH master secret output mode: 1
NoMac bit: 0
LimitedUse bit: 0
EncryptRead bit: 1
IsSecret bit: 1
Write key: 10
Write config: 0x4 (hex) = 0100 (bin)
  Write cmd: Encrypt
  DeriveKey cmd: Can't be used
  GenKey cmd: may NOT be used
  PrivWrite cmd: Encrypt
-------------
Decoding KeyConfig value = 0x003C
Private bit: 0
PubInfo bit: 0
KeyType: 7 [SHA or other]
Lockable bit: 1
ReqRandom bit: 0
ReqAuth bit: 0
AuthKey: 0
IntrusionDisable bit: 0
X509id: 0

Thanks for the quick response. Just tested this with current master. It still fails.
Please note that my ATECC608A is using i2c 0x35 and I set DEFAULT_I2C_SLAVE  to 0x6A in config.h in order to talk to the device.
$ ./atecc -c serial
0123*********
$ head -c 16 /dev/urandom > hmac.key
$ atecc -b1 -c "hmac-write-key 6 0 hmac.key"
read key from file: Success
$ echo "This is a test" > message
$ touch hmac.digest
$ atecc -b1 -c "hmac-dgst 6 message hmac.digest"
Command atcab_sha_hmac_init is failed with status 0xf4
$ git diff
diff --git a/atecc.c b/atecc.c
index 744c322..d1514fe 100644
--- a/atecc.c
+++ b/atecc.c
@@ -136,6 +136,7 @@ int main(int argc, char *argv[])
     ATCAIfaceCfg cfg = cfg_ateccx08a_i2c_default;
     cfg.atcai2c.bus = DEFAULT_I2C_BUS;
     cfg.atcai2c.slave_address = DEFAULT_I2C_SLAVE;
+    cfg.devtype = ATECC608A;

     while ((c = getopt(argc, argv, "h::c:b:s:vr:")) != -1) {
         switch (c) {
diff --git a/config.h b/config.h
index 6fa7f00..6d4153e 100644
--- a/config.h
+++ b/config.h
@@ -1,6 +1,7 @@
 #pragma once

-#define DEFAULT_I2C_BUS 9
-#define DEFAULT_I2C_SLAVE 0xC0
+#define DEFAULT_I2C_BUS 1
+//#define DEFAULT_I2C_SLAVE 0xC0
+#define DEFAULT_I2C_SLAVE 0x6A

 #define MAX_CMDS 32

Hello,
Is that on purpose that ReqRandom bit is set to 1? As far as I remember, in this case ATECC chip requires nonce to be generated by internal RNG and this may be the reason for sha_hmac_init to fail.

Thanks for pointing me out the ReqRandom bit!
My first steps with ATECC608A were done with sample configs as it was difficult for a hobbyist without access to the complete datasheet to find a proper configuration.
The sample configures the device for multiple scenarios and there is another key slot without ReqRandom that I could use:
=========================  Slot: 8   ==================
Decoding SlotConfig value = 0x0F0F
Read key (except ECC private keys): 15
 If slot contains ECC private keys:
  External signatures of arbitrary messages are enabled: 1
  Internal signatures are enabled: 1
  ECDH operation is permitted for this key: 1
   ECDH master secret output mode: 1
NoMac bit: 0
LimitedUse bit: 0
EncryptRead bit: 0
IsSecret bit: 0
Write key: 15
Write config: 0x0 (hex) = 0000 (bin)
  Write cmd: Always
  DeriveKey cmd: Can't be used
  GenKey cmd: may NOT be used
  PrivWrite cmd: Forbidden
-------------
Decoding KeyConfig value = 0x003C
Private bit: 0
PubInfo bit: 0
KeyType: 7 [SHA or other]
Lockable bit: 1
ReqRandom bit: 0
ReqAuth bit: 0
AuthKey: 0
IntrusionDisable bit: 0
X509id: 0

Then I still needed Evgeny Bogers suggested patch to make it work. Without it, the following error occurs:
head -c 16 /dev/urandom > hmac.key
atecc -b1 -c "hmac-write-key 8 0 hmac.key"
#read key from file: Success
echo "This is a test" > message
touch hmac.digest
atecc -b1 -c "hmac-dgst 8 message hmac.digest"
#Command atcab_sha_hmac_finish is failed with status 210

Got it, thanks!

without access to the complete datasheet

I've been told that you can literally type "atecc608a complete datasheet" in Google to find one.


Added Star Trek Trivia Game

PR Description 📜
A fun trivia game centered around the famous Star Trek franchise, which would include the following:
Multiple Difficulty Levels: Different difficulty levels to cater to various levels of Star Trek knowledge.
Variety of Questions: A diverse range of questions covering different aspects of Star Trek, such as characters, aliens, technology, quotes, and memorable moments. This ensures that the quiz appeals to a wide audience and offers a mix of challenging and easier questions.
Time Constraints: A 10 second time limit to answer each question, increasing the pressure and making the game more exciting.
Winning Criteria = 100 points
Fixes #2413

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for website preview in assets/images
[x] I have added entries for my game in main README.md
[x] I have added README.md in my folder
[x] I have added working video of the game in README.md (optional)
[x] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @tayyab-ilyas ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

hey @gurjeetsinghvirdee ! can you check this out? also please don't forget to assign the Gssoc'23 label. Thanks!

Can you re-add the screenshot in assets/images it's not working correctly

Can you check now? working for me..

Thank you  @tayyab-ilyas , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀

hey @gurjeetsinghvirdee on the issue this was given the level 3 label

hey @gurjeetsinghvirdee on the issue this was given the level 3 label

That was automated by github action not given by any  human & labels should be given on the quality of PR

hey @gurjeetsinghvirdee on the issue this was given the level 3 label

That was automated by github action not given by any human & labels should be given on the quality of PR

cool.


Noetic devel

pull request

Hi, @Ananya2528
The master branch does not represent a specific ROS version as there are several minor differences in each branch.
Is there any particular reason for merging noetic-devel into master?


Running latest TextAdept gives "seg fault".

Issue description
When running the textadept in nixos-unstable or nixos-19.03 the only output is "Segmentation fault".  With nixos-18.9 it works but is an old version.
Steps to reproduce
Install textadept from either unstable or 19.3 and execute it with textadept in a terminal.
Technical details
Please run nix-shell -p nix-info --run "nix-info -m" and paste the
results.

system: "x86_64-linux"
host os: Linux 4.14.113, HixOS, 18.09.2532.571b40d3f50 (Jellyfish)
multi-user?: yes
sandbox: yes
version: nix-env (Nix 2.1.3)
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Hm, could not reproduce.
Does textadept-curses start? Does the crash happen if you create a fresh user? What GPU and what GPU driver do you use?

And about the nightly — I think the library directories have to be added to LD_LIBRARY_PATH environment  variable, and you might need to use patchelf to set the binary interpreter which is not in /lib/ld-linux.* but inside glibc in case of NixOS.

Okay.  I just updated to 19.03 and discovered the TextAdept now works!  I had installed my system very shortly before its release so I was still on 18.09.
I had tried the TextAdept in the 19.03 and the latest but both on a 18.09 system.
Is there a proper way to handle this?
Is it worth trying to fix the 19.03 TextAdept to run on a 18.09 system?  Or is there a way to mark or flag a warning when installing the 19.03 TextAdept on 18.03?

Hmm. There are multiple possible causes and they are all a bit complicated (and so workarounds are not applied by default or do not even exist in an automatic form).
It might be OpenGL driver issue (general case of that is being discussed on its own… approximately all the time… and it's complicated because of dependence on hardware).
It might be locale-related (which also has its own discussion from time to time… there is a nice solution that adds triple-digit number of megabytes to closure size which is not nice for containers, so it's all complicated)
It might be something else entirely, of course.

Closing since it sounds like the immediate problem was resolved, but I'm happy to reopen if anyone thinks there's an unresolved-but-actionable underlying issue.


Typo that breaks "make_cache" in new integrated yum_repository code

Description
With older version of chef-client, was previously using the public yum repo to do installs similar to:
yum_repository 'package_name' do
description 'package description'
baseurl 'http://path.com'
action [:create, :makecache ]
end
With the new chef-client version (and integrated yum_repository) "makecache" is no longer a valid option: Above code throws:
Chef::Exceptions::ValidationFailed
----------------------------------
Option action must be equal to one of: nothing, create, remove, make_cache, add, delete!  You passed :make cache.
Would be nice to support ":makecache" and ":make_cache" with depreciation warning but I have already updated recipes to test ":make_cache"
Found typo in provider that is still set to ":makecache" when all other resources (and above in provider) support :make_cache
Chef Version
Chef: 12.14.77
Platform Version
Centos7
Replication Case
Run any:
yum_repository with action [:makecache or :make_cache ]
Client Output
When run with older ":makecache"
Chef::Exceptions::ValidationFailed
----------------------------------
Option action must be equal to one of: nothing, create, remove, make_cache, add, delete!  You passed :make cache.
When updated to run with new ":make_cache"
NoMethodError
-------------
undefined method `action_make_cache' for #Chef::Provider::YumRepository:0x00000003c575a8
Did you mean?  action_makecache
Stacktrace
N/A
NOTE: CHEF CLIENT BUGS ONLY
Fix-
Propose longer term support both [:makecache ] and [:make_cache] with depreciation warning.
ASAP fix- Line 97 on below link.
Change
from- (action :makecache do)
to - (action :make_cache do)
https://github.com/chef/chef/blob/master/lib/chef/provider/yum_repository.rb

@85matthew I fixed this one here https://github.com/chef/chef/pull/5348
Sorry you're running into this

Got it. thanks for the quick response!
Any idea when a new chef-client version/build will be published?

@85matthew Today if we don't hit and road blocks

thanks!
On Thu, Sep 22, 2016 at 9:56 AM, Tim Smith<EMAIL_ADDRESS>wrote:

@85matthew https://github.com/85matthew Today if we don't hit and road
blocks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/chef/chef/issues/5364#issuecomment-248945961, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJp7POMLBdulxWBO6xzN18BwMjwJbPuDks5qsqUjgaJpZM4KDQfs
.


Dataset

Thanks for your sharing. Can you tell me  where  I can download the data set?

I also want to download the data set. Is there anybody can share?

I also want to download the data set. Is there anybody can share?

Same, want to download the dataset. However, I found another paper said that "Unfortunately, this dataset cannot be released to the community due to contract obligations." I am afraid the dataset cannot be released.

I also want to download the data set. Is there anybody can share?

Same, want to download the dataset. However, I found another paper said that "Unfortunately, this dataset cannot be released to the community due to contract obligations." I am afraid the dataset cannot be released.

Yeah, thank you. got it.


ML_DSA: ntt.rs now has a vectorized structure.

lgtm, I assume you move other parts in arithmetic later? Or do you first want to vectorise what's in there now and then do more later if necessary, that's fine too.

I already starting moving in the arithmetic, the plan is to set up a vectorized structure for file and then start filling out the AVX2 code and what not after.


do not fail the sensor attribute when building an entity address

Do warn. Also when FlexMeasuresa starts.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

5 of 8 (62.5%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.01%) to 68.367%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

flexmeasures/data/models/time_series.py
4
7
57.14%

Totals

Change from base Build<PHONE_NUMBER>:
-0.01%

Covered Lines:
7095

Relevant Lines:
9843

💛  - Coveralls


localhost identifier

It might be a good idea to pull the call back up to a config.js setting so that it can be changed in one place for using this on a externally facing server.

That's true! Great idea.
Do you want to create a pull request?

I sure can.  I’ve never done a pull to a public repository so I’ll have to figure that outl
From: Amaury Martiny
Sent: May 31, 2017 8:52 AM
To: amaurymartiny/react-redux-auth0-kit
Cc: rogueturnip; Author
Subject: Re: [amaurymartiny/react-redux-auth0-kit] localhost identifier (#5)
That's true! Great idea.
Do you want to create a pull request?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Composer update + leverage symfony/flex ~1.1

Nicolas, I'm sorry but merging other pending PRs introduced conflicts in this one. Can you please take a look? Thanks!

This PR will also fail tests, because when the doctrine/* packages get updated, you'll bump into the same issue as I did in #846 :

I think we need to either selectively update symfony/* components, or lock the versions of doctrine/*, or do something similar as you did in https://github.com/symfony/symfony/pull/28038

The drawback of using * as Symfony constraint is that composer validate now complains about using unbounded constraint (and it is perfectly right about it).
Thus, any time you use composer require for new components, they would still get an actual constraint (unless you explicitly force *, but then you're responsible for the unbounded constraint).
I suggest keeping bound constraints.


perf(TemplateLibrary): template library should use hooks issue done

Signed-off-by: Iliyas Attarwala<EMAIL_ADDRESS>Issue #105
Changed Template Library Component to use Hooks.
Changes

Changed functions to use Hooks
Changed TemplateLibrary to use Hooks instead of PureComponent and ran all tests using npm run test

Thank you for reveiwing and the compliment :)


How to get script output?

Trying to find how to get the output of the job been executed. The last_message column on jobs.job_executions only contains last message of scheduler.

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

ID: 386f5b1f-e835-0a3b-8e3f-302a6bf5670e
Version Independent ID: 2470305f-0366-36ba-5365-adba61dd02b2
Content: Create and manage Elastic Database Jobs with Transact-SQL (T-SQL) - Azure SQL Database
Content Source: articles/sql-database/elastic-jobs-tsql.md
Service: sql-database
Sub-service: scale-out
GitHub Login: @jaredmoo
Microsoft Alias: jaredmoo

If you specify output server/database/table, then the first result set is written. However if you are looking for info message output (e.g. T-SQL PRINT statements), we unfortunately don't capture it anywhere.

@jaredmoo Thanks for your reply. I'm wondering where should I find errors when script execution failed. I'm running a script that cost 15 hours when I run from Azure Date Studio, but maybe because it lasted for too long, Azure Data Studio cannot capture messages. Then I switch to Elastic Job. The script can succeed after around 30 minutes but I don't get expected results on tables that supposed to be changed.
Do you have any suggestion on how can I run a SQL script that supposed to run for a few hours and get script output?

If the script fails then the error will show up in job execution last_message. However if you just get "unexpected results" then doesn't that mean we don't have an error to show you?

@wy193777 Its been a while we heard from you. We will proceed to close this issue now.
If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


Fix variable shadow issue

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Upload model to GCS during multi-TPU training in colab, cell stuck

Hi
I am trying to run multi-TPU training on colab using notebook_launcher. In the training loop, I am able to save the model locally using accelerator.save(model.state_dict(), local_file_name). However when I try to upload it to GCS using gsutil cp, the cell gets stuck
accelerator.print('Inside saving')
accelerator.save(model.state_dict(), local_file_name)
accelerator.print('Model saved')
accelerator.print('Uploading model')
if accelerator.is_main_process:
  gcs_file_name = os.path.join(MODELS_DIR, args.save_prefix, '{}.pt'.format(num_steps))
  ! gsutil cp {local_file_name} {gcs_file_name}
accelerator.print('Upload done to {}!'.format(gcs_file_name))

Output and where it gets stuck:
Inside saving
Model saved
Uploading model

Is it not possible to upload to GCS during train loop? If so, is there another solution?
Thanks

I am very unfamiliar with GCS, so can't really chime in. Maybe it doesn't work properly in the subprocesses run for the 8 cores of the TPU. Does it work if you do this after the notebook_launcher(training_func)?

@sgugger yes it works after notebook_launcher(training_func).
But that would mean that the upload would only happen if the training loop finishes. Then in case colab interrupts my training and closes the runtime, the local files would be gone.

@sgugger I know this isn't really huggingface/accelerate related, but do you know of a solution/hack so that I don't lose training progress? It doesn't have to be GCS upload.
Any help would be much appreciated!

You could push your model to the Hugging Face Hub when you want to checkpoint (with the push_to_hub method), this way you can resume training from anywhere.


[bugfix] resolve color contrast issues

Makes checkboxes white instead of blue, because blue's meaning is already used for "individual track selection" so having it on label and track toggles confuses that meaning.
Uses config merge strategy described in https://github.com/girder/girder_web_components#customizing-vuetify-configuration
fixes #34

There was a previous issue on the color of the blue in the login screen and others being too bright

Too bright where?  What page?

There was a previous issue on the color of the blue in the login screen and others being too bright

Too bright where? What page?

He was specifically referencing the login page, but I think it extended to the register page as well.  It was the brightness of the blue in the header and buttons I believe.  It's linked in the google doc as #10 (very minor feature).

@BryonLewis here are some screenshots.  I also adjusted secondary because I didn't think the contrast in the data browser header bar was good.


chore/simplify hmr

* Please fill in the required items.

Priority*

[ ] High: This PR needs to be merged first for other tasks.
[ ] Middle: This PR should be merged quickly to prevent conflicts due to common changes. (default)
[x] Low: This PR does not affect other tasks, so it can be merged later.

Purpose of the PR*
I want to simplify and remove unnecessary thinks from hmr module
Changes*
I moved some files to folders.
I added max reconnecting tries on initializeWebSocket
I cleaned code a little.
And a little more, let's take a look
How to check the feature
Nothing changed for facilities.

That's became, when i was trying to solve #477 😆


Simplify attention function

What does this PR do?

Use one definition rather than multiple (will make it easier to do shared things once, such as calculating the FP8 KV cache reciprocal).
Add key/value arguments, so that we don't need the PREFILL_IN_KV_CACHE constant.
Make it kwargs-only (to avoid mixing up the various Tensor args).

Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you read the contributor guideline,
Pull Request section?
[ ] Was this discussed/approved via a Github issue or the forum? Please add a link
to it if that's the case.
[ ] Did you make sure to update the documentation with your changes? Here are the
documentation guidelines, and
here are tips on formatting docstrings.
[ ] Did you write any new necessary tests?

Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Compilation caching system connected to the HF Hub

As per title.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Correction for raw affiliation Department of Business Administration, University Canada west, Vancouver, Canada

Correction needed for raw affiliation Department of Business Administration, University Canada west, Vancouver, Canada
raw_affiliation_name: Department of Business Administration, University Canada west, Vancouver, Canada
new_rors: 028d12s45
previous_rors:
works_examples: W4390921200
contact: dcf89244b85328386216e2ffb0c6fc07:14bca452 @ ourresearch.org

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


build: Add CMake support

Description
This PR rewrites most of the existing Visual Studio-based build system in CMake. It is an initial PoC to simplify the build process. If this kind of work is interesting, it can be further refined to include:

Packaging (MSI/NuGet through CPack)
Better transitive dependencies and properties, which will automatically propagate things like include headers without having to copy/paste them for each target
Better build settings

@alessandrogario this looks great, I appreciate your contribution to the project. Would it be possible to add the following?

[ ] Add Copyright header to all of the added files. Something like

# Copyright (c) blah blah.
# SPDX-License-Identifier: MIT

[ ] Add a github workflow that runs the CMake build. This way we can catch if a change breaks the CMake based build.

Please file an issue and link this PR to it.

Triage discussion: this may help with issue #717

@alessandrogario can you rebase (and address comments as appropriate)?

@alessandrogario still a build failure.  It would be great if we could get this one merged soon if you can take a look at the failure.

@alessandrogario still a build failure. It would be great if we could get this one merged soon if you can take a look at the failure.

Hello @dthaler! I'm getting some build errors that I can't reproduce locally; the packaging code is already standalone, and if you would like to merge it now I can move the rest in a new PR

For the execution context cicd errors, I looked at the vcxproj file differences and one thing I note is that the generated vcxproj file for execution_context_kernel.vcxproj has:
<PreprocessorDefinitions>WIN32;_WINDOWS;WINNT=1;_WIN64;_AMD64_;AMD64;MSC_NOOPT;DEPRECATE_DDK_FUNCTIONS=1;DBG=1;_WIN32_WINNT=0x0A00;WINAPI_FAMILY=WINAPI_FAMILY_DESKTOP_APP;WINAPI_PARTITION_DESKTOP=1;WINAPI_PARTITION_SYSTEM=1;WINAPI_PARTITION_APP=1;WINAPI_PARTITION_PC_APP=1;_NO_CRT_STDIO_INLINE=1;NDEBUG;UNICODE;_UNICODE;CMAKE_INTDIR="Debug";%(PreprocessorDefinitions)</PreprocessorDefinitions>

whereas the checked in one has:
<PreprocessorDefinitions>_DEBUG;WINAPI_FAMILY=WINAPI_FAMILY_DESKTOP_APP;WINAPI_PARTITION_DESKTOP=1;WINAPI_PARTITION_SYSTEM=1;WINAPI_PARTITION_APP=1;WINAPI_PARTITION_PC_APP=1;%(PreprocessorDefinitions);_NO_CRT_STDIO_INLINE=1</PreprocessorDefinitions>

It's possible that the difference is causing the github failure.

For the execution context cicd errors, I looked at the vcxproj file differences and one thing I note is that the generated vcxproj file for execution_context_kernel.vcxproj has:
<PreprocessorDefinitions>WIN32;_WINDOWS;WINNT=1;_WIN64;_AMD64_;AMD64;MSC_NOOPT;DEPRECATE_DDK_FUNCTIONS=1;DBG=1;_WIN32_WINNT=0x0A00;WINAPI_FAMILY=WINAPI_FAMILY_DESKTOP_APP;WINAPI_PARTITION_DESKTOP=1;WINAPI_PARTITION_SYSTEM=1;WINAPI_PARTITION_APP=1;WINAPI_PARTITION_PC_APP=1;_NO_CRT_STDIO_INLINE=1;NDEBUG;UNICODE;_UNICODE;CMAKE_INTDIR="Debug";%(PreprocessorDefinitions)</PreprocessorDefinitions>

whereas the checked in one has:
<PreprocessorDefinitions>_DEBUG;WINAPI_FAMILY=WINAPI_FAMILY_DESKTOP_APP;WINAPI_PARTITION_DESKTOP=1;WINAPI_PARTITION_SYSTEM=1;WINAPI_PARTITION_APP=1;WINAPI_PARTITION_PC_APP=1;%(PreprocessorDefinitions);_NO_CRT_STDIO_INLINE=1</PreprocessorDefinitions>

It's possible that the difference is causing the github failure.

I have removed the NuGet package, and changed the workflow settings. Will take a look at this right away!


Unclear how to configure new node when adding member to cluster

I've started a single-node cluster:
% ./bin/etcd -name=uno -initial-cluster=uno=http://<IP_ADDRESS>:2380
2014/10/29 13:57:37 etcd: no data-dir provided, using default data-dir ./uno.etcd
2014/10/29 13:57:37 etcdserver: start node bc3f316962a4ce82 in cluster 9dbd6201abd472d6
2014/10/29 13:57:37 etcd: listening for peers on http://localhost:2380
2014/10/29 13:57:37 etcd: listening for peers on http://localhost:7001
2014/10/29 13:57:37 etcd: listening for client requests on http://localhost:2379
2014/10/29 13:57:37 etcd: listening for client requests on http://localhost:4001
2014/10/29 13:57:38 raft: leader changed from 0 to bc3f316962a4ce82
2014/10/29 13:57:38 etcdserver: published {Name:uno ClientURLs:[http://localhost:2379 http://localhost:4001]} to cluster 9dbd6201abd472d6

I want to add a node, so I make the following API request:
% curl -X POST http://<IP_ADDRESS>:4001/v2/admin/members -H "Content-Type: application/json" -d '{"peerURLs":["http://<IP_ADDRESS>:8080"]}'
{"id":"81adb4cd6185c55c","peerURLs":["http://<IP_ADDRESS>:8080"]}

Now it is unclear what args I actually need to use in order to join the cluster. What would the necessary invocation of etcd be here to bring up a new node in this cluster with the peerURL http://<IP_ADDRESS>:8080?

It seems that you cannot add member to a single member cluster


Add missing regions and correct shortcodes for multiple countries

Region name and shortCode fixes include these countries:

Cambodia
Chad
Comoros
Cook Islands
Fiji
France
Ghana
Georgia
Grenada
Greece
Greenland
Guadeloupe
Guinea
Iceland
Israel
Japana
Kenya
Latvia
Lebanon
Libya
Lithuania
Luxembourg
Macedonia
Malta
Marshall Islands
Moldova
Monaco
Morocco
New Zealand
Palestine
Phillipines
Romania
Saint Kitts and Nevis
Saint Vincent and the Grenadines
Tajikistan
Timor-Leste
Tuvalu

Wow, fantastic @ellenhutchings! Thanks ever so much. I'll roll a new version shortly.


Randomly raising ERR_HTTP2_GOAWAY_SESSION errors with Testcafe v. 1.14

What is your Test Scenario?
We are running testcafe tests for a web application on a staging environment, both on local machines and on CI.
What is the Current behavior?
With the upgrade to Testcafe version 1.14+ we suddenly encounter this type of error:
1) Unhandled promise rejection:
      Error [ERR_HTTP2_GOAWAY_SESSION]: New streams cannot be created
      after receiving a GOAWAY
      at ClientHttp2Session.request (internal/http2/core.js:1563:13)
      at DestinationRequest._sendRealThroughHttp2
   (xyz\node_modules\testcafe-hammerhead\lib\request-pipeline\destination-request\index.js:47:32)
      at DestinationRequest._send
   (xyz\node_modules\testcafe-hammerhead\lib\request-pipeline\destination-request\index.js:99:18)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (internal/process/task_queues.js:93:5)
      Browser: Chrome 90.0.4430.212 / Windows 10

These errors are not happening all the time, we can also not provide any clear way to reproduce it (beyond using Testcafe version 1.14).
When they do occur, it is rather rarely (~ 1 in 10 test files) but currently it prevents us from using Testcafe 1.14+.
Downgrading to Testcafe 1.13, we do not see these errors at all anymore.
What I can share about the involved server configuration (staging system) is that we are running nginx 1.18.
The config looks something like this
server {
    listen 443 ssl http2 default_server;
[...]

Generally the downgrading to http1 is working, and is also working with Testcafe 1.13.
So somehow it seems there is a bug in version 1.14 where from time to time, the downgrading from http2 to http1 fails and the "GOAWAY" is triggered.
What is the Expected behavior?
Not to raise any ERR_HTTP2_GOAWAY_SESSION errors when running tests with Testcafe 1.14
What is your web application and your TestCafe test code?
I cannot really share much here. I can tell you that it does not seem to be connected to specific test code, because it can happen randomly with different tests. Watching video recordings of failed tests, it seems the error gets raised mostly between page requests.
Steps to Reproduce:

Run tests with Testcafe v. 1.14 against a server that supports http 2 and http1.1  where the downgrading is handled automatically 10 to 30 times

reproduced with chrome and firefox in headless and non-headless mode
Your Environment details:

testcafe version:                   1.14.2
node.js version:                    v16.1.0
command-line arguments:  testcafe chrome:headless
browser name and version: Chrome 90, Firefox 88
platform and version:         Windows 10
other:                                 Unfortunately hard to reproduce

I have the same issue. I think this is rather a hammerhead issue.
Hammerhead (or testcafe) should try to create a new http2 connection on this kind of failure instead of failing completely.
Hammerhead is reusing the same http2 connection for all requests to the same host. So recovering from a broken connection should happen here.


IRC Integration [External Plugin]

SwiftSwitch and SwiftKit both had IRC integration to chat with folks. I propose an IRC integration, as an external plugin, to support IRC chat within the OSRS chat box.

Note: I only saw a note about filing plugins as feature requests on this issue and did not see the plugins repo itself until now. I will follow these instructions: https://github.com/runelite/plugin-hub#creating-new-plugins


[WFCORE-3121] Don't register /core-service=management/access=identity…

… as a domain-wide resource
https://issues.jboss.org/browse/WFCORE-3121
Needs https://github.com/wildfly/wildfly/pull/10372 first.

retest this please

retest this please


App Check no longer compiles as an Objective-C++ module as of 10.16.0

Per Paul B - this has already been noticed internally and is in progress, he mentioned I could open an issue for tracking and I'd like to do so
My original comment on the PR between firebase-ios-sdk 10.15.0 and 10.16.0 follows:

When I attempt to update react-native-firebase to firebase-ios-sdk 10.16.0, including this PR, I receive this:

❌ /Users/mike/work/invertase/react-native-firebase/tests/ios/build/Build/Products/Debug-iphonesimulator/FirebaseAppCheck/FirebaseAppCheck.framework/Headers/FIRAppCheck.h:19:1: use of '@import' when C++ modules are disabled, consider using -fmodules and -fcxx-modules
@import FirebaseAppCheckInterop;
^

I traced it to this PR when I noticed that header file changed in my pod cache between 10.15.0 and 10.16.0. Is this an expected outcome? (stated differently, is there something I need to change so this works, ideally that wouldn't be a breaking change for us since we're adopting a feature release here...)
It's coming from here:
https://github.com/invertase/react-native-firebase/blob/c9b695aa8fd75d5a1d070ecbb6bb9ac4e9ff062e/tests/ios/testing/AppDelegate.mm#L21
Which goes to here:
https://github.com/invertase/react-native-firebase/blob/c9b695aa8fd75d5a1d070ecbb6bb9ac4e9ff062e/packages/app-check/ios/RNFBAppCheck/RNFBAppCheckModule.h#L22
Which goes to here:
https://github.com/invertase/react-native-firebase/blob/c9b695aa8fd75d5a1d070ecbb6bb9ac4e9ff062e/packages/app-check/ios/RNFBAppCheck/RNFBAppCheckProviderFactory.h#L18
...and that file doesn't go through with our compiler settings 🤔
Is there anything that can be done here?
In issues past, I have attempted to provide build instructions for our test app over in react-native-firebase so reproductions are easy but I/we have observed you all may have difficulty since it requires a relatively up to date javascript / node environment etc etc and that's a time suck if you don't already have it running. Let me know if you want repro instructions or any other information though, happy to collaborate of course
Originally posted by @mikehardy in https://github.com/firebase/firebase-ios-sdk/issues/11660#issuecomment-1754072270

Just as a release note - this puts us in a little bit of a bind release-wise with a crash bug in Firestore from the gRPC library change making 10.16.0 a desirable update contrasted with an inability to recommend it as a general thing with an app check compile failure.
It does not appear possible to use podspec magic in our react-native-firebase podspec to alter the gRPC transitive dependency version from FirebaseFirestore.podspec, nor does it appear possible to override the gRPC pod version to 1.49.1 in an app's Podfile. If I am wrong in that I'd welcome the correction so we could provide guidance to fix firestore crashes
If I am write that there is no easy way to override the gRPC update in 10.15.0 firebase-ios-sdk release then it would be nice to see either a 10.15.1 that included just the gRPC change as a cherry-pick or to see a 10.16.1 (or 10.17.0 I suppose) that just had the compile fix so that either could come sooner. This may have all already been taken into account, but I mention it just in case. Cheers

I'm not recommending this, but the right podspec magic might be to copy the FirebaseFirestore.podspec, change the grpc dependency, rename the podspec, publish it and depend on that pod from react-native.

@mikehardy Is there a reason that react-native needs to integrate via Objective-C++ versus Objective-C? If not, using Objective C could be a workaround.

React-native is C++ now, they use code generators etc, all of which results in lots of C++ in the system so that's outside our ability to change I believe

FYI, we plan to have a fix in the 10.17.0 release due out the week of October 23rd. We considered a patch, but determined the change is too far-ranging and should go through the full minor release cycle.


Breaking: Home Assistant MQTT name guidelines change

Hi,
after upgrading my HA to version 2023.8.2 I receive warnings that some MQTT names will not work from version 2024.2 on as they violate the new guidelines (Discussion here: https://community.home-assistant.io/t/psa-mqtt-name-changes-in-2023-8/598099 )
All sensors in the warning in my installation are pretty much all PHL MQTT elements. Warning is:
Discovered entities with a name that starts with the device name
This stops working in version 2024.2.0. Please address before upgrading

Filing this issue, because this must be somehow addressed in the next few months in PHL.
When this is fixed, a few lines would be fine what needs to be changed in the HA programming as I honestly have no clue what needs to be done.

Just had a look at this. Made a quick change to see if it resolves it. Thanks for the heads up and if it's sorted I will commit it to a branch and then you can try it out. And then I'll merge it.

@plambrechtsen Any update here?

@plambrechtsen Any updates to the MQTT warnings? Thank you :)

@plambrechtsen Are you still around in your project?
This becomes emerging, 2023.2 is nearby ;-)

@jacotec please try this version and let me know if it works for you:
functions.py.txt
delete .txt as github does not allow uploading python scripts


Refactor Sinopia email task and tests

No longer need to parse the sqs-sensor message body to retrieve email or resource uri, depends on PR #66

based on post-standup discussion, we think it's best to leave this till #70 is done:  the refactoring would likely leverage the sqs-message-parse task in the stanford DAG, since the email task pre-dates that task and does its own message parsing.  but it seems very possible that the xcom written by sqs-message-parse will change as part of #70, possibly upending any work that'd go into this ticket now.

@jermnelson Presumably you are talking about these lines: https://github.com/LD4P/ils-middleware/blob/main/ils_middleware/tasks/sinopia/email.py#L86-L87  Are we going to replace those data with another source? The description of this ticket doesn't make that clear.

@jermnelson this may be a duplicate of the work in #118 / #111 that I'm working on, so I've moved it to the backlog for now. If not a duplicate can you clarify? Thanks.


Name conflict

harbor is a very well-known name in containerisation circles, for https://goharbor.io/.  Difficult step, but I'd suggest renaming this (even in a small, subtle way, like to harbor-ai, to avoid confusion/conflict.  I think it would be better to do this sooner rather than waiting until the project gets bigger, as it will only get harder to change as more people know the name.

Thanks for raising this, I'm considering a few possible options:

domainify the name: harbor.sh for example, exactly after the CLI name
use a self-expanding acronym that'll include Harbor in it's name, for example HBR - Harbor Bash Resource

I agree that it could be a concern, but I doubt that Harbor will ever be big enough for people to actually confuse it with the docker registry counterpart, similarly to how there are libraries with identical names in different languages and the naming conflict isn't a big problem due to semantic distinction


Added section about interrupts, closes #98

Signed-off-by: Daniel Egger<EMAIL_ADDRESS>

@korken89 Added the link.

bors r+


Internal Redirect: Add support for configurable maximum hops

Title: Internal Redirect: Add support for configurable maximum hops and request with body
Description:
Add configurable maximum number of hops internal redirect should follow. The current behavior is that maximum_hops always equals to 1. The state is tracked by existence of x-envoy-original-url. We should do this bookkeeping in StreamInfo::FilterState once #9143 is done.
Number of maximum hops can be configured at the HCM level or the route level.
HCM level is easier to implement.
route level is confusing since route can change across redirects, but maybe we can always respect the config on the first route a request hits?

@alyssawilk


JS prototype extension issues

Hello!
First off - let me thank everyone involved in this project. It's amazing! The universal native bridge portion alone is a golden egg.
I'm building cordova apps with Ember, and was seeing some strange breakages that are being caused by the javascript prototype extensions that ace uses colliding with some behavior of Ember. I was able to temporarily work around them for now by simply dropping Extensions.js from the cordova_plugins.js manifest (not using any features that depend on the extensions)

Now, I realize that this problem is not a fault of ace by itself - Ember's prototype extensions are ..extensive.. (wayy more evil there than in Extensions.js), and we're on the path towards removing them from our projects entirely (Ember provides alternate ways to use the utility functions).
After browsing the code, it doesn't seem like these extensions are used in many places, and in some cases might be there to simply provide a more "java-like" syntax (though I could be mistaken).
tldr;
I wanted to see how the maintainers of this project would feel about moving away from JS prototype extensions. I'd be happy to contribute a branch for review, if "no extensions" sounds like a desirable goal for maximal compatibility with various projects.
In the meantime, I'll be profiling the actual conflicts more in-depth (sorry for the lack of details!), and perhaps starting to tinker with the no-extensions refactors, but I don't want to be maintaining a personal fork if you all disagree (would probably approach it from the ember side in that case, since a supported path already exists).
Thanks for reading, and thanks again for this project!

I'm not a big fan of prototype extensions either.
+1

So, I went ahead and made a branch to test out the refactors:
https://github.com/runtrizapps/ace/tree/prototype-ext-refactor
I was able to solve my issue (it was a conflict with Array.prototype.removeAt).
I refactored "in place" by replacing calls like
data.removeAt(1) with
ace.Extensions.removeAt.call(data, 1)
and then did some further refactors to
removeAt(data, 1) by storing a local reference to ace.Extensions.removeAt.call
I still need to verify my changes further (and run tests if available?) - I should have some time later this week to do a proper PR and writeup.

I think it's reasonable to move away from any extensions that are problematic.  So feel free to submit a pull request.  Thanks!


Front-matter is removed from CHANGELOG when running commit-and-tag-version

Describe the bug
When I run npx commit-and-tag-version any front matter on my changelog is removed
My existing changelog has some front matter:
---
status: new
---

# Changelog

All notable changes to this project will be documented in this file. See [commit-and-tag-version](https://github.com/absolute-version/commit-and-tag-version) for commit guidelines.

## [4.13.0](https://gitlab.com/.../compare/4.12.3...4.13.0) (2023-10-18)

### Features

Current behavior
# Changelog

All notable changes to this project will be documented in this file. See [commit-and-tag-version](https://github.com/absolute-version/commit-and-tag-version) for commit guidelines.

## [4.13.2](https://gitlab.com/.../compare/4.13.0...4.13.2) (2023-10-19)

Front matter is removed
Expected behavior
Front matter should be maintained, so that we can attach fuller metadata to our changelogs
Environment

commit-and-tag-version version(s): Latest
Node/npm version: npm 18
OS: Mac OS

Possible Solution
I am unsure where to start looking through the code, I presume it is something in the parse/write process, where the front matter gets stripped off before or after the new commit history is added

@TimothyJones PR raised, happy to squash prior to merge in https://github.com/absolute-version/commit-and-tag-version/pull/108


fix regex in check43

Let's say you have a rule like <IP_ADDRESS>/8 in a default security group, the check fails when it should not.
The output from aws ec2 command is like this:
IPPERMISSIONS   2181    tcp     2181
IPRANGES        <IP_ADDRESS>/8
IPPERMISSIONS   9092    tcp     9092
IPRANGES        <IP_ADDRESS>/8

Simply changing the expression by adding a space fixes this problem
egrep ' <IP_ADDRESS>|\:\:\/0'

Good catch @ilyas28. Thanks!

Good catch @ilyas28. Thanks!


db.last() - get the last recorded entry

Is your feature request related to a problem? Please describe.
I am trying to get the very last entry inserted in the database. From the doc I can't see any way to do this efficiently.
I was hoping to be able to query by index but this is not an option.
Describe the solution you'd like
Ideally a db.last() function to return the last inserted point would work well.
If not I would be happy to know any efficient way to get the last entry of the db.
Describe alternatives you've considered
Well I could maybe query by time with a start time early enough to grab at least one point.
Then collect the last entry in the list. Not great.
Additional context
nothing to add

I found one way to do it with the index.latest_time function (which is with a tipo as lateset_time, I must have an older version)
Time = TimeQuery()
t = db.index.lateset_time
db.search(Time == t1)

Let me know if there is a better way to it.
It could be nice to include the usage of latest_time in the doc.

The current index in tinyflux does not keep track of the order of what was recently inserted into the database.  Even if this was supported, the index would be wiped of this information when the python process is stopped since the index is not persistent (like you will find in a db server).
Are you trying to get the latest timestamp associated with a Point?  I suppose there is a case where you insert a Point that is way into the past when you manually specify the time to be in the past- do you want to retrieve this item?  Or simply the item with the most-recent timestamp?  To get the Point with the latest timestamp:
There is an API call for the Index actually that is used internally, if you want to access it directly as sort-of a hack, do this:
from tinyflux import TinyFlux, Point

# Your db.
db = TinyFlux("test.db")

# Make sure the index is valid.  It should be unless you turned indexing off yourself.
assert db.index._valid

# Here's the api call:
max_time = db.index.latest_time

print(max_time)

should print 2023-09-25 20:18:57.502769+00:00
I just saw your follow up and fixed the spelling bug.  There is a new version, 0.4.1, with the spelling fixed.  Here is the reference in the readme:
https://tinyflux.readthedocs.io/en/latest/tinyflux.html#tinyflux.index.Index.latest_time

Thank you. Yes it's the latest timestamp that I need. Not the latest inserted although in my particular application they are always the same. A plain write once recording db.
will go with the latest_time method then.