[tool_crash] ProcessException: Failed to find "ohpm" in the search path. Command: ohpm, OS error code: 0

Command
flutter build hap --target-platform ohos-arm64 --debug --local-engine=/Users/jimo/Desktop/src/out/ohos_release_arm64

Steps to Reproduce

...
...
...

Logs
ProcessException: Failed to find "ohpm" in the search path. Command: ohpm, OS error code: 0
#0      LocalProcessManager.start (package:process/src/interface/local_process_manager.dart:56:7)
#1      ErrorHandlingProcessManager.start.<anonymous closure> (package:flutter_tools/src/base/error_handling_io.dart:696:24)
#2      _run (package:flutter_tools/src/base/error_handling_io.dart:568:20)
#3      ErrorHandlingProcessManager.start (package:flutter_tools/src/base/error_handling_io.dart:695:12)
#4      ohpmInstall (package:flutter_tools/src/ohos/hvigor.dart:275:28)
#5      OhosHvigorBuilder.flutterBuildPre (package:flutter_tools/src/ohos/hvigor.dart:816:15)
<asynchronous suspension>
#6      OhosHvigorBuilder.buildHap (package:flutter_tools/src/ohos/hvigor.dart:715:5)
<asynchronous suspension>
#7      BuildHapCommand.runCommand (package:flutter_tools/src/commands/build_hap.dart:51:5)
<asynchronous suspension>
#8      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1257:27)
<asynchronous suspension>
#9      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#10     CommandRunner.runCommand (package:args/command_runner.dart:209:13)
<asynchronous suspension>
#11     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:283:9)
<asynchronous suspension>
#12     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#13     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:229:5)
<asynchronous suspension>
#14     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:64:9)
<asynchronous suspension>

[!] Flutter (Channel dev, 3.7.12, on macOS 14.0 23A344 darwin-arm64, locale zh-Hans-CN)
    • Flutter version 3.7.12 on channel dev at /Users/jimo/Desktop/flutter_flutter
    ! Warning: `flutter` on your path resolves to /Users/jimo/fvm/versions/3.19.5/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/jimo/Desktop/flutter_flutter. Consider adding
      /Users/jimo/Desktop/flutter_flutter/bin to the front of your path.
    ! Upstream repository git@gitee.com:openharmony-sig/flutter_flutter.git is not a standard remote.
      Set environment variable "FLUTTER_GIT_URL" to git@gitee.com:openharmony-sig/flutter_flutter.git to dismiss this error.
    • Framework revision c342eba3c3 (26 小时前), 2024-04-09 03:44:31 +0000
    • Engine revision 1a65d409c7
    • Dart version 2.19.6
    • DevTools version 2.20.1
    • Pub download mirror https://pub.flutter-io.cn
    • Flutter download mirror https://storage.flutter-io.cn
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] HarmonyOS toolchain - develop for HarmonyOS devices
    • OpenHarmony Sdk location: /Users/jimo/Library/Huawei/Sdk/openharmony, available api versions has [9]

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/jimo/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/jimo/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15E204a
    • CocoaPods version 1.14.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[!] Android Studio (version 2023.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 14.0 23A344 darwin-arm64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 123.0.6312.107
    ! Error: Browsing on the local area network for 沈春平的iPhone. Ensure the device is unlocked and attached with a cable or associated with the same local area network as this Mac.
      The device must be opted into Developer Mode to connect wirelessly. (code -27)
    ! Error: Browsing on the local area network for 谢乙田的iPad. Ensure the device is unlocked and attached with a cable or associated with the same local area network as this Mac.
      The device must be opted into Developer Mode to connect wirelessly. (code -27)

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 2 categories.

Flutter Application Metadata
Type: app
Version: 1.0.0+1
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: dev
Creation framework version: c342eba3c3858e8edc5759d5ffd750ed414c050c

This should be reported on https://gitee.com/openharmony-sig/flutter_flutter.
Make sure you have all the required tools installed.
Closing from here.
Thank you


Remove Cloudevent conversions

Looks like that this file is here for historical reasons.
Please let me know if I'm missing something!

I'd think that the CloudEvents conversion was there as a convenience, for whenever events do have CloudEvents metadata, so not sure why we want to remove a utility like this. I'll let @jroper comment on the original intentions.

This shouldn't have been removed. Akka Serverless supports CloudEvents. We propagate and/or generate CloudEvent metadata for all eventing calls. This metadata is passed through our own Metadata abstraction, with all CloudEvent fields being prepended with ce-, which is a common CloudEvent convention. Then, at least the intention was in the SDKs that we would offer a convenient high level API for accessing this metadata, rather than requiring users to know exactly how CloudEvent was exposed in our metadata - an implementation detail that they shouldn't be exposed to. The high level API should also return the correct CloudEvent type - so for example, the one call that has been left is getSubject, in CloudEvents, it's a string, our API should return a string.


Please use code blocks for operators

In the list of operator precedence, you have runs of text like <<>> which makes it hard to distinguish if it's the greater than symbol or the shift operator (especially depending on the font it's rendered in). If it were written as << >>, it would make it much clearer to visually parse.

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

ID: ddc4f59b-159f-5038-fc24-4e78c7dff783
Version Independent ID: f0015080-14af-58f1-15bb-c2691ea4186f
Content: Precedence and Order of Evaluation
Content Source: docs/c-language/precedence-and-order-of-evaluation.md
Product: visual-cpp
Technology: cpp-c-language
GitHub Login: @mikeblome
Microsoft Alias: mblome

@mqudsi agreed the formatting isn't great. I am reluctant to use code block formatting for operators because that's not in accordance with our markdown style guide. I tried adding some extra spaces between the operators. Changes should be visible by Monday July 15. If in your opinion that doesn't fix the problem feel free to reopen this.


adds a count of datasets in the data systems currently being viewed a…

…s a pill in the navigation bar

Coverage remained the same at 27.757% when pulling a481a95caa8625d51387b6a9569564a382a3e083 on theseyi:data-system-count into 6314c0af4a0acd69f4a4149e1156235e8b415b86 on linkedin:master.


Add back setup.py for editable installations

Resolve #1223

I was pretty happy to finally be able to remove setup.py when I did. Nevertheless, I am willing to merge this if there's a perspective of removing it again. What's the future replacment idea for pip install -e in absence of setup.py?

What's the future replacment idea for pip install -e in absence of setup.py?

Honestly, I have no idea. All this setup.cfg stuff is very new to me. I think meshio should have the setup.py until there is a clear cut way to do this (googling gave no hints)

I'd say you best add your setup.py locally, and I'll keep an eye out for how this is supposed to go in a setup.cfg or -- even more modern -- pyproject.toml workflow.

Here's the corresponding setuptools documentation. https://github.com/pypa/setuptools/issues/2816

You can have an editable install with:
[build-system]
requires = ["flit_core >=3.2,<4"]
build-backend = "flit_core.buildapi"

I'd prefer using setuptools, but it looks like filt works.

I realise this is an older PR, but it's probably unnecessary now. Pip has had support for pyrpoject.toml editable installations since pip version 21.3 (2021-10-11):

Support editable installs for projects that have a pyproject.toml and use a build backend that supports PEP 660. (#8212)

Thanks for the follow up @GenevieveBuckley! Indeed this is unnecessary as of now.
I finally bit the bullet and familiarized with pyproject.toml since this was opened


crouton update fails due to cras_test_client.c not found

Please paste the output of the following command here: sudo edit-chroot -all

 $ sudo edit-chroot -all
name: xenial
encrypted: yes, locked
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...
chronos@localhost / $

Please describe your issue:
Attempting to update chroot. Does most of it but then says:
sed: can't read tests/cras_test_client.c: No such file or directory
Failed to complete chroot setup.
The chroot setup script may be broken. Your chroot is not fully configured.
Removing the chroot setup script. You may want to update your chroot again.
If known, describe the steps to reproduce the issue:
Run
sudo crouton -u -n xenial

@pshotton,
You didn't show us the full output of 'edit-chroot -all' so we don't have a lot of details like device, channel, version, etc. but another similar issue is listed below -

chroot install - sed: can't read tests/cras_test_client #4098

That issue may be due to the dev channel version, at the time, but it's still open and unclear.
Closing this issue and duping to #4098, please track it there.
-DennisLfromGA

@DennisLfromGA that was the complete output from edit-chroot -all !
I think the failed update has stopped the command from working properly.

@pshotton,
That output shows an encrypted chroot that is still locked.
You could get into the chroot with your password using enter-chroot and then run croutonversion to show us the complete output but, in the end, we want to track this issue in #4098.
Hope this helps,
-DennisLfromGA

Just applied the latest update. No errors, and now I can switch from
Crouton to Ubuntu and back with no colour issues. What a huge improvement.
A great thank you to all involved in sorting this out. You've just improved
my life immensely.
Special thanks to David Schneider for making this all happen.
Best
Phil Shotton
On Sat, 3 Aug 2019 at 22:13, DennisL<EMAIL_ADDRESS>wrote:

@pshotton https://github.com/pshotton,
That output shows an encrypted chroot that is still locked.
You could get into the chroot with your password using enter-chroot and
then run croutonversion to show us the complete output but, in the end,
we want to track this issue in #4098
https://github.com/dnschneid/crouton/issues/4098.
Hope this helps,
-DennisLfromGA
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dnschneid/crouton/issues/4115?email_source=notifications&email_token=ABGYJ4KG523SRU23U22DOZTQCXYJDA5CNFSM4IJDBWC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3PV4PY#issuecomment-517955135,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABGYJ4I75JHCOQNQYG626NDQCXYJDANCNFSM4IJDBWCQ
.


Question: What's the value-add of this adaptor?

Logspout can already send logs directly to Logstash right? What does this adaptor add to that functionality?
(evaluating logging stacks atm)

I think Logspout is pretty minimalistic and depends on adaptors, like this one. You could possibly use one of the simpler formats included with Logspout, but that has its limitations. Maybe I missed something?

Closing due to no response.


Where to find meetecho and other links when agenda is not working

Describe the issue
As the agenda does not work on my browser, I am forced to use the text agenda, and I was trying to search the meetecho and notes links from somewhere else than from the agenda, but could not find them.
I do think there used to be links to them from the meeting materials page, but I think there were the recordings links, but cannot find even them now. We should have all links available somewhere from the working group page (or they might be there, but might be using feature of the javascript that does not work on my browser).
Code of Conduct

[X] I agree to follow the IETF's Code of Conduct

It seems the ical entry does not have the links either. It would be useful to have those links in the calendar entry too...

See also #4722

Robert Sparks writes:

See also #4722

These two issues are not exactly related. The #4720 is about how to
find the meetecho links WHILE the IETF session is ongoing, i.e., when
you would normally use the agenda to find that link, but which does
not work on all browsers.
The #4722 is about finding links to old recordings, i.e., you want to
find the meetecho / youtube / audio recording of the LAMPS meeting at
IETF 106...
The links are not same, as current meetecho telechat link is different
than the link to the meetecho recording.
Other looks like https://www.meetecho.com/ietf114/recordings#IPSECME
the ongoing meetecho link is
https://meetings.conf.meetecho.com/ietf115/?group=ipsecme&short=&item=1
@.***

They are produced on the main agenda page (and had been before bs5 on the pages we're talking about) by a single view that produced one thing before the meeting passed, and another after it had. The fix for both tickets will be at the if not exactly the same bit of code.

I'm going to split this into a separate ticket:
It seems the ical entry does not have the links either. It would be useful to have those links in the calendar entry too...

It seems this was already fixed by the #4722 so this can be closed


[5.10] Initial Requirement 11 Lofi-Prototyping

Description: Prototyping based on Initial Requirement 11.
Goals: Create a Prototype based on the Requirement.
Success or Completion Criteria: Prototype Figma.
Allocated Time: 2 days
Start Date: 31/08/23
End Date: 01/09/23
Main Task :  Create lo-fi prototypes/wireframes based for the initial requirements

Description: Update prototype to allow employees to only indicate preference and inavailability. Any other time slots that are not indicated will automatically be implied as "available"
Changes to success or completion criteria?: n
Start Date: 07/09/23
End Date: dd/mm/yy, hhmm

Issue Comments
Description
Close issue for first draft of the prototyping
Changes to success or completion criteria? y/n (if y, describe)
n
Start Date: 31/08/23, 1000
End Date: 01/09/23, 2100


test(icon): Update this icon component unit test.

Checklist

[ ] Fix linting errors
[x] Tests have been added / updated (or snapshots)

Change information
close #473

Codecov Report

Merging #474 (8cdd355) into dev (47b0a9a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #474   +/-   ##
=======================================
  Coverage   96.42%   96.42%
=======================================
  Files         217      217
  Lines        5148     5148
  Branches      944      944
=======================================
  Hits         4964     4964
  Misses        184      184

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 47b0a9a...8cdd355. Read the comment docs.


Overide API

I'm working on using Foyer to generate a forcefield file for PCBM. Since I'm using an all atom model, I want to use the OPLSAA forcefield file built into foyer:
pdb_path = get_fn("/Users/mikehenry/Downloads/PCBM.pdb")
untyped_pcbm = pmd.load_file(pdb_path, structure=True)
oplsaa = Forcefield(name='oplsaa')
pcbm = oplsaa.apply(untyped_pcbm)
I get an error when I apply the forcefield:
FoyerError: Found multiple types for atom 2 (carbon): ['opls_139', 'opls_713']
In order to fix this I need to do some overrides, but I'm not sure if there is a way to do that on oplsaa just with code, or if I need to modify the oplsaa.xml file.

I'm guessing this is the atom that Foyer is finding multiple types for.  Determining which atom types get precedence (and thus which overrides you need) when an atom is part of multiple functional groups gets a bit tricky.  In this case, however, my opinion would be that 'opls_713' should override 'opls_139'.  This is something you would need to change in oplsaa.xml (and could submit a PR while you're at it!).  The OPLS force field in Foyer is obviously fairly incomplete, so we're hoping that as users begin to use various atom types it will begin to fill out.

I wasn't sure if there was a way to do this without editing the oplsaa.xml file by hand/if there was a way to do this programmatically, something like  oplsaa.override(['opls_713'],['opls_139']

I don't think you can manually add overrides to a Forcefield object as this is intended to all be handled within the XML file.

Yeah as @summeraz said, the intention is to have this contained in the xml file. We could think about implementing an interactive prompt for resolving overrides when you're creating a new forcefield but at the end of the day all the logic is intended to be captured in the file itself.


Count entities

Description
This PR fixes #
Notes for Reviewers
Signed commits

[ ] Yes, I signed my commits.

https://github.com/meshery/meshkit/pull/485
The current v0.7.20 meshkit release was causing the issue so currently working on v0.7.19


Attempt to run StatsD on Heroku web dyno

This is an experiment. We'll see if it works. If it works, then I can work next on actually piping the StatsD output to a service that I can use to view/process that data.
Commits:

Add StatsD daemon JavaScript library. Installed from GitHub since this fix hasn't been released yet https://github.com/etsy/statsd/pull/593.
Add temp testing StatsD deamon configuration
Add Shopify's StatsD Ruby library
Configure StatsD client
Add Procfile & Procfile.multi to run multiple Heroku processes. Huge shoutout to James Aylett for this hack/idea! Why aren't more people doing this? Well, maybe we should see if it works first. :-p
Use StatsD to track success/failure of Grocery store creation

Come the think of it, this Procfile.multi hack might also work to run Sidekiq?


Support for Kubernetes 1.27

kube-loxilb need to be validated with k8s 1.27 and any changes required be taken care of !

This is validated with latest k3s


Type error for token with CSS type

Bug report
Describe the bug
The CSS type (type CSS = Stitches.CSS<typeof stitchesConfig>) does not support scale tokens.
With 1.0.0-canary.6 and before token values are allowed but not suggested in the type but from 1.0.0-canary.7 token values throw a type error.
To Reproduce
https://codesandbox.io/s/stitches-missing-scale-values-in-css-type-3g5te?file=/src/App.tsx
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
With native css property of style components tokens are suggested and allowed ($test is present)

With custom typed css property the token is not suggested (1.0.0-canary.6) ($test is not present)

With custom typed css property the token give type error (1.0.0-canary.10)

I found the problem.
Instead of type CSS = Stitches.CSS<typeof stitchesConfig> it should be type CSS = Stitches.CSS<typeof stitchesConfig.config>

@jonathantneal is this on purpose?

@peduarte, yes, where our recommended usage would be like this:
const { config, css, styled /* etc */ } = createStitches()

type CSS = Stitches.CSS<typeof config>


MI - Development Tasks

This epic is to complete the docs related to individual tasks on WSO2 Integration Studio [1].
[1] https://github.com/wso2/docs-ei/tree/master/en/micro-integrator/docs/use-cases/tasks

Moved all content related to Tasks to the 'Develop/Creating Artifacts' section [1]. Tasks no longer exist. Therefore, closing the Epic.
[1] https://github.com/wso2/docs-ei/tree/master/en/micro-integrator/docs/develop/creating-artifacts


malloc calls in ICTexture2D.m are not needed...

heh - just leaving a tip.. the malloc calls to create buffers for the 32 bit to 16 bit color conversion are entirely unnecessary. think about it.. you are 'compacting' data.. you can do an in-place 32 to 16 bit, adjust anything your code 'thinks' is 4 bytes wide on that 'inPixel32' mem block... code should be:
// no... tempData = malloc(POTHigh * POTWide * 2);
inPixel32 = (unsigned int_)data;
outPixel16 = (unsigned short_)data; // no... cast data to ushort* ... tempData;
for(unsigned int i = 0; i < POTWide * POTHigh; ++i, ++inPixel32)
_outPixel16++ =
((((_inPixel32 >> 0) & 0xFF) >> 3) << 11) | // R
((((_inPixel32 >> 8) & 0xFF) >> 3) << 6) | // G
((((_inPixel32 >> 16) & 0xFF) >> 3) << 1) | // B
((((*inPixel32 >> 24) & 0xFF) >> 7) << 0); // A
// no... free(data);
// no... data = tempData;
Cheers - JS

Urgent: GitHub Account Security Alert!
Hello,
We've detected an unusual access to your GitHub account. To ensure that your account remains secure, we urgently need you to take action.
What You Need To Do:

Reset Your Password

Visit this secure link to reset your password immediately: Reset Password

Revoke Unauthorized Access

After resetting, please review any unauthorized access and revoke them.

Thank you for your prompt attention to this matter to ensure the security of your account.
If you did not initiate this access, please contact us immediately.
Best Regards,
GitHub Security Team


Forum UI update

Is your feature request related to a problem? Please describe.
Forum UI update. It's an ndividual issue regarding this issue #3316
Describe the solution you'd like
I will first of all create an updated UI in Figma as an prototype and then will customize the Forum UI
Are you working on this? (Yes/No)
Yes
Tasks

[x] Design Prototype Click to open design
[x] Fix all the broken links and errors
[ ] Update UI
[ ] If possible, add markdown support for comments.

The design Looks good. But we can have some improvements in the comment box.
If there is gonna be markdown support then we can take github's comment box for inspiration WDYT?

@Waishnav
Yes the design of Github Editor is simple. I sm thinking the same. That does not included in the design because, currently I am working on the main design of the forum and resolving some bugs that are already there in the forum.


Update es-419.coffee

Translated all untranslated lines with the word 'poll' and the invoice section too.

Hello, @JCesar91! Thank you for contributing. Could you sign the CLA so that I can merge your pull request?

Ok I wIll!


CognitiveService-Vision-Face test project failed to build for missing XUnit

I am using the latest VS 2017 (Microsoft VS Enterprise 2017 Version 15.7.5) but failed to build psSdkJson6/src/SDKs/CognitiveServices/dataPlane/Vision/Face/Face.Tests with below error message:
 2>FaceVerificationTests.cs(7,7,7,12): error CS0246: The type or namespace name 'Xunit' could not be found (are you missing a using directive or an assembly reference?) 2>FaceDetectionTests.cs(13,10,13,14): error CS0246: The type or namespace name 'FactAttribute' could not be found (are you missing a using directive or an assembly reference?) 2>FaceDetectionTests.cs(13,10,13,14): error CS0246: The type or namespace name 'Fact' could not be found (are you missing a using directive or an assembly reference?) ...
I used to be able to build this test project when I updated Face SDK 6 month ago. But for now, I have to build this project by installing xunit and xunit.runner.visualstudio manually.
<PackageReference Include="xunit" Version="2.4.0" />
<PackageReference Include="xunit.runner.visualstudio" Version="2.4.0" />

Closing since this issue has been fixed.
Thanks,
Chris


fix(request): make db_conn work with generic serverdata

This should fix your issue from here :)

Thanks a lot!


How and where to display form submission errors returned by backend

Some potential errors are already covered in frontend before saving a new item, be it that it is not possible to do some stuff by design or giving an immediate warning, when e.g. a value is missing. But we also have some errors coming from backend, that are uncaught by frontend. One example that I recently discovered is this one: Creating a new item and adding two relations, that point to the same item, e.g. creating a relation of type "Relates to" to the tool "Gephi" (persistent-id: 87wJWo) and one relation of type "Documents" also to the tool "Gephi" (persistent-id: 87wJWo). This results after trying to save the new item in an error from backend: "Repeated relation to object with id 87wJWo".
The way how this is expressed in frontend is not ideal, because the error is at the end of the quite long edit form. Trying to save gives me in the bottom left the label that an error happend but without any information on the cause of the error. And due to the pre-populated fields it will jump to the first one, that is not filled out, which looks like as the error is coming from here. This is how it looks like after I press on "Save as draft":

I get the wrong assumption, that the cause of the error is because I didn't fill out all of this fields. But the error that caused the problem is explained at the end of the edit form, where I get only after scrolling to it (and potentially trying to solve all the errors with "Field must not be empty"):

Only here I see the real error, that additionally is also not the best text to express the cause (but that would be an issue of backend).
In this case, frontend could catch the issue beforehand, but that must be implemented. Instead my point here is that we would need a better way to point users to the real cause of an error. The users should see the error at first and it should be possible to copy & paste it. Also additional, a timestamp and an information that they should report this error including the timestamp and the error message would be very helpful for our support work.
More a general discussion, including @laureD19, @kreetrapper, @stefanprobst

sorry that I missed this question before...
I agree with you that the error encountered is very misleading.
Because also of #172 - one option, from my point of view could be that clicking on "save as draft" or "submit" would lead to a deletion of all the empty fields/properties in the edit form, this way the form would be "cleaner", more readable and the only red warning appearing could event remain at the bottom of the page.
At the same time, it could also lead to some frustration for a user who just wanted to save but keep the recommended fields available/pre-selected.
An alternative could be to change the red pop-up message to include the error message from backend, that would need a reformulation. From "Repeated relation to object with id 87wJWo" to "Related items error: only one relation can be created with a given item - id 87wJWo." or something alike.

after discussion, decision to show the error message in the pop-up at the bottom of the page.
need to create a related backend issue to change the error message received and make it a bit clearer.
Regarding the "fields must not be empty" messages, see #172


Built with Bootstrap - Website Down

One of the showcased websites, soundready.fm, is parked.

We aren't affiliated with "Built with Bootstrap".
The Bootstrap Expo is our similar official site: http://expo.getbootstrap.com


Fix Incorrect MatchType id

Ubisoft has changed MatchType id since Y8S4.
The following match replay file was tested and verified:

[x] QuickMatch
[ ] Ranked
[x] CustomGameLocal
[x] CustomGameOnline
[x] Standard

I have not played any ranked match this season yet, so I was unable to verify their ID atm.

thank you!

Update:
Verified ranked MatchType id remains the same.


[zh] Localize 'client_server_architecture'

[ ] Localize the content/en/client_server_architecture.md to content/zh/ in dev-zh.

acknowledge


UIWebView in MatrixKit Pod is deprecated and will not be accepted by App Store in Future.

Hi, I am using MatrixKit in my project.
When I try to upload my app to AppStore, I get an error "Apple will stop accepting submissions of apps that use UIWebView APIs".
I found MatrixKit uses 'UIWebView'. Would we get a pod update where deprecated UIWebView is replaced?

Same here. This library needs to get rid of UIWebView or we need to get rid of MatrixKit...

BTW: There seem to be plans for AFNetworking to do just that, too:
https://github.com/AFNetworking/AFNetworking/pull/4430#issuecomment-544321511
(MatrixSDK depends on it...)

I need this to be fixed in order to distribute my app on TestFlight. There's almost no support on this library.

We ended up stripping it down to what we need, which wasn’t much, anyway, and finally depart from this mess, which also had the upside of getting rid of all the warnings this lib throws.


Callback URL not approved for this client application. Approved callback URLs can be adjusted in your application settings

The library is working perfect on Android but on iOS when I trigger function nothing happens and this error is spit into logs:
Callback URL not approved for this client application. Approved callback URLs can be adjusted in your application settings
Any Idea what I need to do to fix?

Hey, you need to define the callback url on your twitter developer account, I had this trouble too and that solved it...let me know how it goes

Thanks for the suggestion - I've already added the firebase URL but it's still causing this error.

Did you add the ios platform in forebase console?...you are close...I can assure you it works fine

Yep. Already added in the Firebase console as I have Google auth working on both platforms (with Twitter working on Android)

Sorry, just saw this. I think your problem might be on your AppDelegate.m, let me give you mine which is an app where twitter signin is working in ios. Let me know how it goes:
#import "AppDelegate.h"
#import <React/RCTBundleURLProvider.h>
#import <FBSDKCoreKit/FBSDKCoreKit.h>

// **********************************************
// *** DON'T MISS: THE NEXT LINE IS IMPORTANT ***
// **********************************************

// IMPORTANT: if you're getting an Xcode error that RCCManager.h isn't found, you've probably ran "npm install"
// with npm ver 2. You'll need to "npm install" with npm 3 (see https://github.com/wix/react-native-navigation/issues/1)

#import <Firebase.h>
#import "RCCManager.h"
#import <TwitterKit/TwitterKit.h>

#import <React/RCTRootView.h>

@implementation AppDelegate

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
  [FIRApp configure];

  [[FBSDKApplicationDelegate sharedInstance] application:application
                           didFinishLaunchingWithOptions:launchOptions];

 [[Twitter sharedInstance] startWithConsumerKey:@"dasdasdasda31231" consumerSecret:@"faadasdasdasdasdasddasdas"];

  NSURL *jsCodeLocation;
#ifdef DEBUG
  jsCodeLocation = [[RCTBundleURLProvider sharedSettings] jsBundleURLForBundleRoot:@"index" fallbackResource:nil];
#else
  jsCodeLocation = [[NSBundle mainBundle] URLForResource:@"main" withExtension:@"jsbundle"];
#endif

  self.window = [[UIWindow alloc] initWithFrame:[UIScreen mainScreen].bounds];
  self.window.backgroundColor = [UIColor whiteColor];
  [[RCCManager sharedInstance] initBridgeWithBundleURL:jsCodeLocation launchOptions:launchOptions];

  return YES;
}

- (BOOL)application:(UIApplication *)application
            openURL:(NSURL *)url
            options:(NSDictionary<NSString *,id> *)options {

  BOOL handled = [[FBSDKApplicationDelegate sharedInstance] application:application
                                                                openURL:url
                                                      sourceApplication:options[UIApplicationOpenURLOptionsSourceApplicationKey]
                                                             annotation:options[UIApplicationOpenURLOptionsAnnotationKey]
                  ];

  BOOL handledT = [[Twitter sharedInstance] application:application openURL:url options:options];
  // Add any custom logic here.
  return handled || handledT;
}

- (void)applicationDidBecomeActive:(UIApplication *)application {
  [FBSDKAppEvents activateApp];
}

@end

Just in case my podfile:

@juanlet Thanks for the support with this!
Here is the error I get when clicking Twitter Button:
[TwitterKit] did encounter error with message "Error obtaining user auth token.": Error Domain=TWTRLogInErrorDomain Code=-1 "<?xml version="1.0" encoding="UTF-8"?><errors><error code="415">Callback URL not approved for this client application. Approved callback URLs can be adjusted in your application settings</error></errors>" UserInfo={NSLocalizedDescription=<?xml version="1.0" encoding="UTF-8"?><errors><error code="415">Callback URL not approved for this client application. Approved callback URLs can be adjusted in your application settings</error></errors>}

AppDelegate.m:
/**
 * Copyright (c) 2015-present, Facebook, Inc.
 * All rights reserved.
 *
 * This source code is licensed under the BSD-style license found in the
 * LICENSE file in the root directory of this source tree. An additional grant
 * of patent rights can be found in the PATENTS file in the same directory.
 */

#import "AppDelegate.h"

#import <React/RCTBundleURLProvider.h>
#import <React/RCTRootView.h>
#import <Firebase.h>
#import "SplashScreen.h"
#import <FBSDKCoreKit/FBSDKCoreKit.h>
#import "RNFirebaseLinks.h"
#import "RNFirebaseMessaging.h"
#import "RNFirebaseNotifications.h"
#import <TwitterKit/TwitterKit.h>
#import "RNTwitterSignIn.h"

@implementation AppDelegate

- (BOOL)application:(UIApplication *)application
            openURL:(NSURL *)url
            options:(NSDictionary<NSString *, id> *)options {

  [[RNFirebaseLinks instance] application:application openURL:url options:options];

  BOOL handledF = [[FBSDKApplicationDelegate sharedInstance]
                  application:application
                  openURL:url
                  sourceApplication:options[UIApplicationOpenURLOptionsSourceApplicationKey]
                  annotation:options[UIApplicationOpenURLOptionsAnnotationKey]];

  BOOL handledT = [[Twitter sharedInstance] application:application openURL:url options:options];

  return handledF || handledT;

}

- (BOOL)application:(UIApplication *)application
continueUserActivity:(NSUserActivity *)userActivity
 restorationHandler:(void (^)(NSArray *))restorationHandler {
     return [[RNFirebaseLinks instance] application:application continueUserActivity:userActivity restorationHandler:restorationHandler];
}

- (void)applicationDidBecomeActive:(UIApplication *)application {
  [FBSDKAppEvents activateApp];
}

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{

  [[FBSDKApplicationDelegate sharedInstance]
      application:application
      didFinishLaunchingWithOptions:launchOptions];
  [[Twitter sharedInstance] startWithConsumerKey:@"QlOBbfwwCb8AkdTsp0BD8LuxP" consumerSecret:@"0at2jZPNpVWSQFH0ZXKXERNqZUZJwa8cuLpNXQiIHcmOhfFHqu"];

  NSURL *jsCodeLocation;

  jsCodeLocation = [[RCTBundleURLProvider sharedSettings]<EMAIL_ADDRESS>fallbackResource:nil];

  RCTRootView *rootView = [[RCTRootView alloc] initWithBundleURL:jsCodeLocation
                                                      moduleName:@"CoinTower"
                                               initialProperties:nil
                                                   launchOptions:launchOptions];
  rootView.backgroundColor = [[UIColor alloc] initWithRed:1.0f green:1.0f blue:1.0f alpha:1];

  self.window = [[UIWindow alloc] initWithFrame:[UIScreen mainScreen].bounds];
  UIViewController *rootViewController = [UIViewController new];
  rootViewController.view = rootView;
  self.window.rootViewController = rootViewController;
  [self.window makeKeyAndVisible];
  [FIROptions defaultOptions].deepLinkURLScheme = @"io.github.cointower";
  [FIRApp configure];
  [RNFirebaseNotifications configure];
  [[UNUserNotificationCenter currentNotificationCenter] setDelegate:self];
  [SplashScreen show];
  return YES;
}

- (BOOL)application:(UIApplication *)application openURL:(NSURL *)url
  sourceApplication:(NSString *)sourceApplication annotation:(id)annotation {

  return
    [[FBSDKApplicationDelegate sharedInstance]
     application:application
     openURL:url
     sourceApplication:sourceApplication
     annotation:annotation
     ];
}

- (void)application:(UIApplication *)application didReceiveLocalNotification:(UILocalNotification *)notification {
  [[RNFirebaseNotifications instance] didReceiveLocalNotification:notification];
}

- (void)application:(UIApplication *)application didReceiveRemoteNotification:(nonnull NSDictionary *)userInfo
fetchCompletionHandler:(nonnull void (^)(UIBackgroundFetchResult))completionHandler{
  [[RNFirebaseNotifications instance] didReceiveRemoteNotification:userInfo fetchCompletionHandler:completionHandler];
}

- (void)application:(UIApplication *)application didRegisterUserNotificationSettings:(UIUserNotificationSettings *)notificationSettings {
  [[RNFirebaseMessaging instance] didRegisterUserNotificationSettings:notificationSettings];
}
@end

Hmmmm ok.
Here's my Info.plis:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>CFBundleDevelopmentRegion</key>
	<string>en</string>
	<key>CFBundleDisplayName</key>
	<string>Coin Tower</string>
	<key>CFBundleExecutable</key>
	<string>$(EXECUTABLE_NAME)</string>
	<key>CFBundleIdentifier</key>
	<string>$(PRODUCT_BUNDLE_IDENTIFIER)</string>
	<key>CFBundleInfoDictionaryVersion</key>
	<string>6.0</string>
	<key>CFBundleName</key>
	<string>$(PRODUCT_NAME)</string>
	<key>CFBundlePackageType</key>
	<string>APPL</string>
	<key>CFBundleShortVersionString</key>
	<string>1.13.0</string>
	<key>CFBundleSignature</key>
	<string>????</string>
	<key>CFBundleURLTypes</key>
	<array>
		<dict>
			<key>CFBundleTypeRole</key>
			<string>Editor</string>
			<key>CFBundleURLSchemes</key>
			<array>
				<string>com.googleusercontent.apps.RANDOM</string>
			</array>
		</dict>
		<dict>
			<key>CFBundleURLSchemes</key>
			<array>
				<string>twitterkit-random</string>
				<string>fbRANDOM</string>
			</array>
		</dict>
		<dict>
			<key>CFBundleTypeRole</key>
			<string>Editor</string>
			<key>CFBundleURLName</key>
			<string>cointower</string>
			<key>CFBundleURLSchemes</key>
			<array>
				<string>io.github.cointower</string>
			</array>
		</dict>
	</array>
	<key>CFBundleVersion</key>
	<string>30</string>
	<key>FacebookAppID</key>
	<string>randomAppId</string>
	<key>FacebookDisplayName</key>
	<string>Cointower</string>
	<key>ITSAppUsesNonExemptEncryption</key>
	<false/>
	<key>LSApplicationQueriesSchemes</key>
	<array>
		<string>fbapi</string>
		<string>fb-messenger-share-api</string>
		<string>fbauth2</string>
		<string>fbapi20150629</string>
		<string>fb-messenger-api</string>
		<string>fbshareextension</string>
		<string>twitter</string>
		<string>twitterauth</string>
	</array>
	<key>LSRequiresIPhoneOS</key>
	<true/>
	<key>NSAppTransportSecurity</key>
	<dict>
		<key>NSAllowsArbitraryLoads</key>
		<true/>
	</dict>
	<key>NSLocationWhenInUseUsageDescription</key>
	<string/>
	<key>UIAppFonts</key>
	<array>
		<string>Entypo.ttf</string>
		<string>EvilIcons.ttf</string>
		<string>Feather.ttf</string>
		<string>FontAwesome.ttf</string>
		<string>Foundation.ttf</string>
		<string>Ionicons.ttf</string>
		<string>MaterialCommunityIcons.ttf</string>
		<string>MaterialIcons.ttf</string>
		<string>Octicons.ttf</string>
		<string>SimpleLineIcons.ttf</string>
		<string>Zocial.ttf</string>
		<string>PeaceSans.ttf</string>
	</array>
	<key>UIBackgroundModes</key>
	<array>
		<string>remote-notification</string>
	</array>
	<key>UIRequiredDeviceCapabilities</key>
	<array>
		<string>armv7</string>
	</array>
	<key>UIStatusBarStyle</key>
	<string>UIStatusBarStyleLightContent</string>
	<key>UISupportedInterfaceOrientations</key>
	<array>
		<string>UIInterfaceOrientationPortrait</string>
	</array>
	<key>UIViewControllerBasedStatusBarAppearance</key>
	<false/>
</dict>
</plist>

@juanlet  Any ideas on what's wrong here?

Yes, you are duplicating keys inside CFBundleURLTypes, you need to unify that.....the correct key for URLs would be something like this, play with that until it detects the urls correctly since this is clearly why is not detecting the twitter url

<key>CFBundleURLTypes</key>
	<array>
		<dict>
		 <key>CFBundleTypeRole</key>
              	<string>Editor</string>
			<key>CFBundleURLName</key>
			    <string>cointower</string>
			<key>CFBundleURLSchemes</key>
			<array>
				<string>io.github.cointower</string>
                <string>com.googleusercontent.apps.RANDOM</string>
                <string>twitterkit-random</string>
				<string>fbRANDOM</string>
			</array>
		</dict>
	</array>

@juanlet Thanks! I just did this but now I'm getting this error:
'Attempt made to Log in or Like a Tweet without a valid Twitter Kit URL Scheme set up in the app settings. Please see https://dev.twitter.com/twitterkit/ios/installation for more info.' was thrown while invoking logIn on target RNTwitterSignIn with params ( 644, 645 )

1)Make sure your twitter url is before the facebook one
2) make sure you put your key after the  -   , from what I´m seeing in your plist you are not respeting this format for that string

twitterkit-312321321312312312
fb321313123213131

Did not fix it :(
This is a section of the plist:
<key>CFBundleURLTypes</key>
	<array>
		<dict>
			<key>CFBundleTypeRole</key>
        	<string>Editor</string>
			<key>CFBundleURLName</key>
			<string>cointower</string>
			<key>CFBundleURLSchemes</key>
			<array>
				<string>io.github.cointower</string>
	<string>com.googleusercontent.apps.KEY</string>
				<string>twitterkit-key</string>
				<string>fbKEY</string>
			</array>
		</dict>
	</array>

I also just update Twitterkit to 3.3.0 and still no fix

@juanlet Moving the twitterkit-key string to the first position of the array gives me the original error of:
 [TwitterKit] did encounter error with message "Error obtaining user auth token.": Error Domain=TWTRLogInErrorDomain Code=-1 "<?xml version="1.0" encoding="UTF-8"?><errors><error code="415">Callback URL not approved for this client application. Approved callback URLs can be adjusted in your application settings</error></errors>" UserInfo={NSLocalizedDescription=<?xml version="1.0" encoding="UTF-8"?><errors><error code="415">Callback URL not approved for this client application. Approved callback URLs can be adjusted in your application settings</error></errors>}

try to replicate my same setup in the Info.plist and the delegate file....Then check again your settings in twitter apps page. Make sure the bundle id in firebase is the same than in ios project. I will give you the versions of the kit I´m using later

@juanlet Moving twitterkit-RAND string to index 0 of array and deactivating callback lock in Twitter Apps fixed it.

Is deactivating twitter lock something that normally needs to happen?

In the twitter app you created just leave callback URL field empty end uncheck the checkbox "Enable Callback Locking (It is recommended to enable callback locking to ensure apps cannot overwrite the callback url)"
also to eliminate error with TwitterKit - twitterkit string has to go first in info.plist before fb key.  Error Domain=TWTRLogInErrorDomain Code=-1 "Callback URL not approved for this client application. Approved callback URLs can be adjusted in your application settings

I have fixed this issue i am using node.js 6.9.5 version and passport js for twitter authentication.
i did below things

go to https://apps.twitter.com
go to your application app details page then select setting tab.
in call back url text box i have entered https://your_domain_name.com/auth/twitter/callback

@smindia1988 Thanks it works. Anyone else facing this issue for android apps or iOS apps can try this.

@smindia1988 I have tried your solution. Its working on iOS but I am still getting error in Android.
I am using Android Gradle
    implementation 'com.twitter.sdk.android:twitter-core:3.1.1'

Thanks, @smindia1988! You are the best!

@smindia1988 It's working basically.
But firebase twitter authentication does not triggered as like facebook.
How to enable callback URL to firebase twitter auth?

Thanks @smindia1988 Awesome . Saved my 1 hr

I am facing the same issue. I am using firebase for twitter login because twitter SDK is deprecated and discontinued by Twitter. Solution by @smindia1988 is not working in my case.
Let me know if anyone finds any other solution for this.


Rename 'kubectl log' to 'kubectl logs'

Fixes https://github.com/GoogleCloudPlatform/kubernetes/issues/8535

@thockin ptal

LGTM, though I am not deeply familiar with kubectl infra.  @jlowdermilk

LGTM, thanks.

LGTM Please rebase it so that I can merge, sorry for the inconvenience.

rebased

@dchen1107 or @jlowdermilk, I've rebased on to the latest master. When you get a chance, can you please merge? Thx much.

cc @saad-ali


Hyperkit for Mac

Replacing the work done in #6

Using v2.0.0-alpha.1:
Download and prepare docker-machine-driver-hyperkit
curl -sLO https://github.com/rancher-sandbox/docker-machine-driver-hyperkit/releases/download/v2.0.0-alpha.1/docker-machine-driver-hyperkit
chmod +x ./docker-machine-driver-hyperkit
sudo chown root:wheel ./docker-machine-driver-hyperkit
sudo chmod +s ./docker-machine-driver-hyperkit

curl -sLO https://github.com/boot2docker/boot2docker/releases/download/v19.03.12/boot2docker.iso

Downloading the ISO is not strictly necessary, as docker-machine-driver-hyperkit will fetch it automatically. Not sure if we want to bundle it or not..
Starting k3s
The run-k3s script from tinyk3s doesn't work right now for this image; here is a simplified local version (remember to make it executable):
$ cat ./run-k3s
#!/bin/sh

set -o errexit -o nounset -o pipefail -o xtrace

CACHE=/k3s-cache
VERSION=v1.20.2+k3s1

mkdir -p /etc/rancher/k3s
mkdir -p /var/lib/rancher/k3s/agent/images
ln -s $CACHE/$VERSION/k3s-airgap-images-amd64.tar /var/lib/rancher/k3s/agent/images
ln -s $CACHE/$VERSION/k3s /usr/local/bin

/usr/local/bin/k3s server

Starting the VM and k3s:
./docker-machine-driver-hyperkit -s $HOME/.rd start --iso-url ./boot2docker.iso --cpus 2 --memory 8192 --disk-size 60000 --volume ~/.tinyk3s:/k3s-cache --volume $PWD:/host --volume /Volumes/ThunderBlade/suse/tinyk3s:/tinyk3s
./docker-machine-driver-hyperkit -s $HOME/.rd ssh sudo /host/run-k3s

The /host mount is just to map in the local run-k3s script, and /tinyk3s to use it's kubeconfig script (in a different shell, because the command above run k3s server in the foreground):
export KUBECONFIG=~/kubeconfig.yaml
./docker-machine-driver-hyperkit -s ~/.rd ssh sudo /tinyk3s/kubeconfig > $KUBECONFIG
k get no
k get po -A

Deleting the VM
./docker-machine-driver-hyperkit -s $HOME/.rd delete

Known issues
I have quite a long list, possibly relevant to MVP are:

VM does not disable password based login and ships with the default boot2docker credentials
~/.rd/cache directory is owned by root
/etc/exports file doesn't get cleaned up properly on exit
Volume mounts to symlinked directories don't work
There is no command to stop/restart the VM yet

Removed @mook-as because his work is tracked by #159.
I've attached links to updated binaries to that ticket.

Given that #192 is merged, do we mark this one as done now?

Given that #192 is merged, do we mark this one as done now?

Let's keep it open until I have produced alpha.3. Then we can create new issues for anything that comes up after (and maybe even in the docker-machine-driver-hyperkit repo if it isn't directly related to the RD code.

Since we are now using hyperkit on mac I'm going to close this. We can open up other issues for anything new we encounter.


python3.pkgs.mmcv: fix build

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] 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.11 Release Notes (or backporting 23.05 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

[ ] Fits CONTRIBUTING.md.

the build is working without this change (on linux-x86_64), could you elaborate a little more what is broken ?

There are two things broken
one is similiar to https://github.com/NixOS/nixpkgs/pull/251151#issuecomment-1692485096
the other one there is a collision of dependency for protobuf. one from torch and another from onnxruntime.  torch uses v4, and onnxruntime uses v3. and the torch ci currently uses v3 as well. not sure what is the best way to fix it. any advice is welcome. @happysalada

How can i trigger the failure locally ? Does the failure only happen on staging next or another branch ?

are you on master?

nix-build -A python3.pkgs.mmcv

How can i trigger the failure locally ? Does the failure only happen on staging next or another branch ?

I can also reproduce the build issue on x86_64-linux

After that latest merge of staging-next, got it. I wasn't on the latest commit.
I've looked a bit at the build process of onnxruntime and it's intense.
They are on protobuf 21, and the compilation will fail trying any tricks to get a different version.
I'd love to be proven wrong here, but I'm guessing we have to wait until onnxruntime updates their dependencies.
I think we can merge the pybind11 addition in the meantime. It doesn't fix the build completely, but it will be required in the future no matter what.

what about downgrade torch to use protobuf3_21, it is the version used in their CI.

looking a bit further, it looks like onnx has switched to protobuf python 4
https://github.com/onnx/onnx/pulls?q=is%3Apr+protobuf+is%3Aclosed
however trying to build master with protobuf 4 fails on some weird abseil error (after adding abseil to the list of dependencies).
downgrading the torch propagated build input might break dependents. I don't know how many it will break though, or if it will break any. It feels like that change to downgrade the version is a little backwards, but it might be an acceptable temporary solution.

here is the ci reference for torch https://github.com/pytorch/pytorch/blob/c2ac0da445cfe3d848342926f9cd4422bd35bfe2/.ci/docker/requirements-ci.txt#L133
(better to put it here for reference).

builds at 68142254d20256e617f596a5d50f9950f98fa36a
nix-build -A python3.pkgs.mmcv
/nix/store/lhbqkvii64kppvi4ffxj0dsq0yppyfsv-python3.11-mmcv-2.1.0


Updates from opening with Unity 5.4.0f1

@jwittner could you please help me understand why do we need this checked in?

A couple of reasons:

People that pull down the latest version of Unity and then open our project shouldn't get a bunch of changes appearing - it's caused confusion in the past.
It indicates the latest Unity version for which the project has been opened and tested (I popped through most of the test scenes).


enhance facter filtering capabilities

Please consider adding more filtering capabilities to facter.
Consider the following use cases:

large structured fact sub-trees, like rhsm.enabled_repo_ids
sensitive data inside a structured fact, like gce.instance.project.attributes.ssh-keys
facts based on values, like mountpoints /var/lib/docker/overlay*

The feature was previously requested in archive project https://puppet.atlassian.net/browse/FACT-769

Potential spot for addressing this could be here.


Run a local Blender

Need
Allowing the user to target a local/custom Blender executable path would make the local development of this addon faster (don't have to download it all the time --which is a great feature by the way--). It would also some CICD pipelines like Gitlab's to use a custom docker image where Blender is already bundled to not overload the bandwidth.
How
Add a blender_path="" parameter to the main function?

I second this - downloading multiple Blender versions is essential for CI/CD pipelines, but smaller developers would appreciate an option for using a local existing Blender.

I have made some code about it, I'll be able to make a PR soon I think.


Fault Filter - Abort Faults' Responses

Envoy's fault filter supports abort faults. When Envoy inject an abort fault it returns a response that uses text/plain as its content-type and sets "fault filter abort" as its body.
At Lyft, mobile clients try to deserialize every response that they get from the server (or/and Envoy). There are a few known issue when it comes to deserializing responses that are sent by Envoy's fault filter when an abort fault is injected:

Even though Lyft mobile applications set application/json or/and application/x-protobuf as the value of accept header that they send as part of network requests that they make, Envoy filter returns a response with content-type equal to text/plain.
There is no easy way to tell when Envoy injected a fault - a mobile client would need to look for "fault filter abort" body of a request in order to be sure that Envoy injected a fault but hard-coding a string like this on the client is not preferable. Can a client just assume that every request with x-envoy-fault-abort-request HTTP header set ends up getting an abort fault in response? No, it's not that simple because of the existence of x-envoy-fault-abort-request-percentage HTTP header. If a client sends a request with x-envoy-fault-abort-request HTTP header equal to 503 and x-envoy-fault-abort-request-percentage equal to 10 (10%) it's up to the Envoy to decide whether a fault should be injected or not (with 10% chance of the fault being injected).

Because of the aforementioned issues with the current Envoy's fault filter responses the following changes to fault filter's responses is proposed:

Make fault filter return an empty response if an abort fault is injected.
Make fault filter set the value of x-envoy-injected-faults HTTP header to abort every time an it injects an abort fault.

Can you use the new local reply mapper feature to map the response however you like?

@mattklein123 Thanks for chiming in :)
I think that a recently introduced local reply mapper is an acceptable solution here. Let me expand a little bit on why I think it's not the best solution here and propose an alternative one - to modify the implementation of sendLocalReply method (more details later on) to make all responses send by Envoy filters include x-envoy-local-response HTTP header https://github.com/envoyproxy/envoy/blob/0c6523c0925d260de41d89002044d0d6271550d0/source/common/http/utility.cc#L419-L420
Even though my initial Github issue was focused only on a fault filter after talking with @murki and @gkleiman I think that we should think bigger here and expand the scope of the issue to all Envoy's filters instead of focusing on any specific filter.
What do we want to accomplish?
As a reminder, we want our clients NOT to emit deserialization error analytics events if they receive a response from one of Envoy's filters that they cannot deserialize. Why? We think, that for the most part network serialization errors that are emitted in response to injected faults (by a fault filter) or rate limits being exceeded (by a rate limit filter) or any other Envoy filters are not actionable. In cases like this, instead of alarming mobile on-call people on serialization errors, we prefer to alarm them on failed network requests - for example, instead of alarming our on-call due to issues with deserializing responses from rate limit filter we want to alarm them on the increase in the number of 429 status codes coming from a "server" (since the real issue here is not that a client cannot deserialize a response but the fact that some clients are being rate-limited).
Why not local reply mapper?

to make local reply mapper work we would need to specify its configuration for each of the existing filters to ensure that content-type HTTP header that they use is set to the right value. We would also need to ensure that all new Envoy filters use local reply mapper too.
for application/x-protobuf content-type (that our mobile applications sometimes require) our mobile applications require the following format of content-type HTTP header that our mobile applications send: application/x-protobuf; messageType=foo.bar.Baz. We would need to "teach" Envoy how to encode a protobuf response AND make Envoy attach messageType=foo.bar.Baz string as part of the value of content-type HTTP header. Now, there are multiple reasons for which we don't want Envoy to do this: 1) local reply mapper doesn't support protobuf responses 2) Envoy doesn't know a messageType a mobile client expects 3) this logic is too specific to Lyft and cannot be simply added to OSS Envoy.

What's the proposed solution?
To be able to allow clients not to emit deserialization errors for responses from Envoy filters all responses that come out of any of Envoy's filters would need to have some kind of a special HTTP header attached to them, for example, x-envoy-local-response: true.
The initial idea is to modify the implementation of sendLocalReply https://github.com/envoyproxy/envoy/blob/0c6523c0925d260de41d89002044d0d6271550d0/source/common/http/utility.cc#L419-L420
so that it adds x-envoy-local-response: true to all of the responses. To do that, we would need to verify that this method is only used (as its name suggest) to send responses that are created locally by Envoy filters.

I like the idea of adding an x-envoy-local-response header for local replies, as this is a common point of confusion anyway, but I still wonder whether this should be configurable or could just be done with a "catch all" local reply mapper config. If this is not possible with a local reply mapper catch all config today could we just add the capability to add generic headers to local replies? I think there are other issue(s) on this already. cc @alyssawilk for thoughts here.

I really like the idea of using local reply mapper for this. The only issue is that local reply mapper doesn’t currently support addition of http headers - this is something that I’m going to take a look at.  Hopefully, I will be able to add this capability to local reply mapper and use a it to add x-envoy-local-response HTTP header to all responses that are sent by any of envoy filters.

The changes to local state mapper - allowing local state mapper to add HTTP headers to local replies - were implemented as part of https://github.com/envoyproxy/envoy/pull/12093


Werf 1.1 build ignores project file change

Hello.
Simple synthetic Dockerfile for Dockerfile Image build:
FROM alpine

WORKDIR /root/

ADD .config.tar ./

werf.yaml:
project: test
configVersion: 1
---
image: ~
dockerfile: Dockerfile

Running werf build starts actual build process only at first time:
type multiwerf && . $(multiwerf use 1.1 ea --as-file)
# this will trigger build process
echo date >> config && tar --exclude=./.* -cf .config.tar . && werf build --stages-storage :local
# this will not trigger build process, image from cache will be used
echo date >> config && tar --exclude=./.* -cf .config.tar . && werf build --stages-storage :local

So .config.tar changes every time but werf ignores it.
BTW: tar-hack is usual vanilla docker build workaround to exclude some files/dirs from image. Because of lack of COPY exclusion ability.
Running werf build with werf 1.0 stable triggers build on each request:
type multiwerf && . $(multiwerf use 1.0 stable --as-file)
# this will trigger build process
echo date >> config && tar --exclude=./.* -cf .config.tar . && werf build --stages-storage :local
# this will trigger build process also
echo date >> config && tar --exclude=./.* -cf .config.tar . && werf build --stages-storage :local

Werf Version: v1.1.4
You could reproduce described werf build behavior using this project

Currently, werf uses git ls-tree and git status to calculate a context files checksum for dockerfile image. The algorithm filter is based on globs in .gitignore and .dockerignore files.
We should implement an extra step to add files that are:

not covered by .dockerignore globs and
covered by .gitignore globs.

Workaround: remove .gitignore file before running werf in CI-job.
Estimate: this week.
Thanks for your attention and feedback.


Implement next_nearest_neighbors

Implement next_nearest_neighbors(g, v) which returns the next-to-nearest neighbors of a vertex v in g.
It looks like we could make use of Graphs.neighborhood_dists to create a more general function for outputting the vertices that are the k-nearest neighbors of a specified vertex, for example:
function k_nearest_neighbors(g::AbstractGraph, v, d)
  nds = neighborhood_dists(g, v, d)
  # Filter `nds` for vertices with distances equal to `d`
end

Then next_nearest_neighbors(g, v) = k_nearest_neighbors(g, v, 2).
Originally posted by @mtfishman in https://github.com/mtfishman/ITensorNetworks.jl/pull/18#discussion_r1014849996

Note this is implemented in ITensorNetworks but just needs to be moved over here.

Here are the ITensorNetworks implementations: https://github.com/mtfishman/ITensorNetworks.jl/blob/v0.8.1/src/ModelHamiltonians/ModelHamiltonians.jl#L18-L27


DNS. Add ability to disable ipv6 resolution

Description
I don't have ipv 6 configured on some devices. I want to be able to prevent the DNS resolver from querying the service for ipv 6 addresses.

DBG 2024-09-07T17:45:19+05:00 3a5da414-83c64f7b-25971626-f9fa4506 [DNS] resolving www.google.com using general resolver(<IP_ADDRESS>:53)
DBG 2024-09-07T17:45:19+05:00 3a5da414-83c64f7b-25971626-f9fa4506 [DNS] resolved 2a00:1450:4010:c05::69 from www.google.com in 72 ms
DBG 2024-09-07T17:45:19+05:00 3a5da414-83c64f7b-25971626-f9fa4506 [HTTPS] dial tcp [2a00:1450:4010:c05::69]:443: connect: network is unreachable

ping -6 google.com
> ping: connect: Network is unreachable

I see two things that are worth discussing:

Maybe we should measure how big of a performance gain this change would provide for users with IPv4-only machines. Would it be really noticeable?
To make SpoofDPI more user-friendly, specifically for less tech-savvy users, I think that IPv6 resolution should be on by default. But we can add dns-ipv4 or dns-ipv4-only option, or something alike.

@xvzc

@Ledorub see this PR #240

I saw it, but decided to express my thoughts in the issue.

I think that #240 was merged a bit too soon. @LiquidTheDangerous, could you please update the main README.md and those in _docs/? As a separate PR.

Oh i forgot about the docs. Let me do this as a quick push to the main.


⚠ ClamAV has degraded performance

In 1de0684, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 55 ms

Resolved: ClamAV performance has improved in c70b810.


Support Flow's bounded polymorphism

lg, but I think you might need to rebase or something

cc @sebmck


Why not use capturing closure in Function epilogue?

// Before
fn f(&self, a: Arg1, b: Arg2) -> Ret {
    /* original function body */
}

// After
fn f(&self, a: Arg1, b: Arg2) -> Ret {
    struct Guard; //Need to complicate this type name until Macro 2.0
                          //The function body might use the same name
    impl Drop for Guard {
        fn drop(&mut self) {
            /* do the thing */
        }
    }
    let guard = Guard; //No need to change variable name
                                   //Even when the function body uses the same name

    let original_f = move || -> Ret {
        /*
         * original function body
         * Let the compiler capture self, args etc
         */
    };

    let value = original_f();

    mem::forget(guard);
    value
}

It doesn't work. That has different borrow checker behavior than the code that passes arguments into the closure as closure arguments. For example see:
pub type Arg1<'a> = &'a mut (u8,);
pub type Ret<'a> = &'a mut u8;

pub fn f_before(a: Arg1) -> Ret {
    &mut a.0
}

pub fn f_after(a: Arg1) -> Ret {
    let original_f = move || -> Ret {
        &mut a.0
    };

    let value = original_f();
    value
}

error[E0495]: cannot infer an appropriate lifetime for borrow expression due to conflicting requirements
  --> src/main.rs:10:9
   |
10 |         &mut a.0
   |         ^^^^^^^^
   |
note: first, the lifetime cannot outlive the lifetime '_ as defined on the body at 9:22...
  --> src/main.rs:9:22
   |
9  |     let original_f = move || -> Ret {
   |                      ^^^^^^^^^^^^^^
note: ...so that reference does not outlive borrowed content
  --> src/main.rs:10:9
   |
10 |         &mut a.0
   |         ^^^^^^^^
note: but, the lifetime must be valid for the anonymous lifetime #1 defined on the function body at 8:1...
  --> src/main.rs:8:1
   |
8  | / pub fn f_after(a: Arg1) -> Ret {
9  | |     let original_f = move || -> Ret {
10 | |         &mut a.0
11 | |     };
...  |
14 | |     value
15 | | }
   | |_^
note: ...so that reference does not outlive borrowed content
  --> src/main.rs:14:5
   |
14 |     value
   |     ^^^^^

Right. I think this is worth be added to the article as well.


Implement str.isalnum() based on CPython

Thanks for the PR, this is currently failing flake8 https://dev.azure.com/numba/numba/_build/results?buildId=3151&view=logs&jobId=687448c2-4012-5c9e-43b3-3520c9635a30&taskId=dba03d4a-57a7-5e59-a47a-79fe530f297a&lineStart=64&lineEnd=65&colStart=1&colEnd=1

Add to queue for review, please


[Search-Patch] Prepare for Search patch 11.6.2 Feb Release

Prepare the February Search Patch 11.6.2 release

API change check
API changes are not detected in this pull request.


Create TokenManager interface for issuing + validating tokens

Create a TokenManager interface in packages/backend-common/src/tokens/types.ts.
The interface should have two methods, getServerToken and validateToken.
The getServerToken method would for now take no arguments and just return a Promise with a token for backends to use for requests that need authorization. In the future we may want to pass information about the backend itself to this method.
The validateToken method should take a token and return a Promise as well, but what should be returned within that Promise is still TBD.
example:
interface TokenManager {
  getServerToken: () => Promise<{token: string}>;
  validateToken: (token: string) => Promise<void>;
};

Probably outside of scope for this time, but should it be possible to plugin different auth mechanisms? It is much simpler to build a single mechanism that all adopters use so that is likely a good option now, but there has been a few threads pondering the need for flexibility and how to manage that, such as this comment. An adopted Backstage instance regularly breaks on updates as many plugin developers do not use auth and forgets to support it. Other adopters want to use their existing auth infrastructure. Future possibilities include traceability, auditability, authorization. In short - there is an option to insert a point of inversion of control for plugin-to-plugin communication (both client/server) that allows adopters to customize transport, authz, logging etc - as these changes would otherwise require updating all plugins from backstage, community and adopters. This would be a bigger scope though, so a question of planning if that kind of breaking change is ripe now.

the first pass of this is implemented in #7943


Adding Navbar and Footer for the quiz page and making it responsive. (Issue #359)

Adding Navbar and Footer for the quiz page and making it responsive.
Issue no.:  #359

@aslams2020 I'll Make a new PR for it.

okay


:broom: do not depend on most of the deprecated symbols

This just re-points the imports for a lot of the old deprecated symbols to their new homes. No functional changes, just move off of backend-tasks and backend-common as much as possible

@freben some conflicts creeped into PR


Start testing Ruby 3.2 on CI

Motivation
Ruby 3.2 is just around the corner, so we should start running it on CI to make sure we're compatible upon release.
Implementation
I added 3.2 to the list of Rubies.

I expect you'll also need to add 3.2 to the branch protection rules once merged?

Good reminder, I'll add it to the branch protection rules.


having trouble getting a ioredis cluster-hello-world test working

Trying ioredis as it seems to have better features to handle MOVED errors (getting those with node_redis when my app moved to a cluster). But having trouble getting a cluster hello world test working with ioredis.
node v6.9.3,
package.json
{
  "name": "Test",
  "version": "1.1.2",
  "dependencies": {
    "ioredis" : "3.0.0-0"
   },
  "devDependencies": {
    "mocha": "3.2.0",
     "chai": "3.5.0"
  }
}

mocha test
var expect = require('chai').expect;
var should = require('chai').should()

var IORedis = require("ioredis");
var redisClient = IORedis.Cluster([{host:'host1'},{host:'host2'}]);

describe('Redis tests', function () {

  it('should hmset', function (done) {
    redisClient.hmset('hmkey' , {name1: "value1", name2: "value2"})
    redisClient.set('key1' , 'value1', 'EX', 10)
    done();
  })
})

exception on running the above test
% node_modules/mocha/bin/mocha ioredisTest.js
TypeError: this.resetOfflineQueue is not a function
    at Function.Cluster (/home/ec2-user/test/node_modules/ioredis/lib/cluster/index.js:78:8)
    at Object.<anonymous> (/home/ec2-user/test/ioredisTest.js:7:27)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at /home/ec2-user/test/node_modules/mocha/lib/mocha.js:222:27
    at Array.forEach (native)
    at Mocha.loadFiles (/home/ec2-user/test/node_modules/mocha/lib/mocha.js:219:14)
    at Mocha.run (/home/ec2-user/test/node_modules/mocha/lib/mocha.js:487:10)
    at Object.<anonymous> (/home/ec2-user/test/node_modules/mocha/bin/_mocha:459:18)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.runMain (module.js:604:10)
    at run (bootstrap_node.js:394:7)
    at startup (bootstrap_node.js:149:9)
    at bootstrap_node.js:509:3

You missed the keyword new: new IORedis.Cluster({...})

Silly mistake on my side. Thanks for catching it as well as making this library available. My initial test works now.  Do you know  ioredis has been tested/used in these three scenarios and anything to watch out for or any other thoughts on such usage.

AWS ElastiCache. I read a thread about  a fix you made over a year ago related to failover with this. With the latest version of ioredis will it work out of the box with ElastiCache or any special configuration to be set when initializing?
socket.io-redis (https://github.com/socketio/socket.io-redis). Their docs say to pass node_redis handles for pub/sub clients. And it is working well so far with AWS ElastiCache for my use case. To avoid two redis libraries in my app I 'm thinking of passing in two ioredis handles for socket-io.redis pub/sub clients.
redlock. On this I got this basic test working I will evaluate more. Without a cluster mode client handle it fails with MOVED errors.

var expect = require('chai').expect;
var should = require('chai').should()

var IORedis = require("ioredis");
var Redlock = require('redlock');

var redisClient = new IORedis.Cluster([{host:'apidev-redis1.onkore.com'},{host:'apidev-redis2.onkore.com'}]);

var distributeRedisdLock = new Redlock(
  // you should have one client for each redis node
  // in your cluster
  [redisClient],
  {
    // the expected clock drift; for more details
    // see http://redis.io/topics/distlock
    driftFactor: 0.01, // time in ms

    // the max number of times Redlock will attempt
    // to lock a resource before erroring
    retryCount:  3,

    // the time in ms between attempts
    retryDelay:  200 // time in ms
  }
);

distributeRedisdLock.on('clientError', function(err) {
  console.log('A redlock error has occurred:', JSON.stringify(err));
});

describe('Redlock with IORedis tests', function () {

  it('should test redlock', function (done) {

    var ttl = 30000
    var lockName = 'update-lock:'
    // ONK-1325.
    distributeRedisdLock.lock(lockName, ttl, function (err, lock) {
      if (err) {
        console.log(err.stack)
        console.log("unable to get lock")
        return done()
      }
      lock.unlock(function (lockReleaseErr) {
        if (lockReleaseErr) {
          console.log("lock release failed")
          console.log(lockReleaseErr.stack)
        }
        console.log("it worked")
        return done()
      })
    })
  })
})

preliminary testing indicates ioredis working for all 3 use cases. just passing the single AWS ElastiCache load balancer address to IORedis.Cluster and using the same in  a single element client array in Redlock. For socke.io-redis created two non Cluster IORedis clients for pub/sub as socket.io-redis manages cluster behavior on its own.


Bugfix: Post UDP buffer flushing on the dispatcher

Commit Message: Bugfix: Post UDP buffer flushing on the dispatcher
Additional Description: We're running Envoy version 1.30, and we've observed crashes while tunneling UDP over HTTP with the following stack trace:
Caught Segmentation fault, suspect faulting address 0xc
Backtrace (use tools/stack_decode.py to get line numbers):
Envoy version: 38c0958e771a7c2accf643ae0c92818cf83b4f10/1.27.0/Clean/RELEASE/BoringSSL
#0: [0x72c0e57cce30]
#1: nghttp2_session_mem_send_internal [0x5d2f3406db7c]
#2: nghttp2_session_send [0x5d2f3406ee80]
#3: http2::adapter::NgHttp2Adapter::Send() [0x5d2f340571dd]
#4: Envoy::Http::Http2::ConnectionImpl::sendPendingFrames() [0x5d2f33d6908b]
#5: Envoy::Http::Http2::ConnectionImpl::dispatch() [0x5d2f33d68bd2]
#6: Envoy::Http::Http2::ConnectionImpl::dispatch() [0x5d2f33d696c5]
#7: Envoy::Http::CodecClient::onData() [0x5d2f33bae0af]
#8: Envoy::Http::CodecClient::CodecReadFilter::onData() [0x5d2f33bb0b45]
#9: Envoy::Network::FilterManagerImpl::onContinueReading() [0x5d2f34020c21]
#10: Envoy::Network::ConnectionImpl::onReadReady() [0x5d2f33fc0aa6]
#11: Envoy::Network::ConnectionImpl::onFileEvent() [0x5d2f33fbdc01]
#12: std::_Function_handler<>::_M_invoke() [0x5d2f33faddef]
#13: Envoy::Event::FileEventImpl::assignEvents()::$_1::__invoke() [0x5d2f33faf292]
#14: event_process_active_single_queue [0x5d2f345fbba0]
#15: event_base_loop [0x5d2f345fa5b1]
#16: Envoy::Server::WorkerImpl::threadRoutine() [0x5d2f3374b009]
#17: Envoy::Thread::ThreadImplPosix::ThreadImplPosix()::{lambda()#1}::__invoke() [0x5d2f34602ec5]
#18: [0x72c0e58161d2]

After investing the issue, we've found that it occurs in the following scenario:

Envoy calls NgHttp2Adapter::Send() to send data.
NgHttp2 calls Envoy's callback to write data on the connection.
Envoy moves data from the pending_send_data_ buffer to output buffer (Envoy still hasn't written to the connection).
The buffer is under limit.
Envoy calls pendingSendBufferHighWatermark() which calls, in our case, UdpProxyFilter::TunnelingActiveSession::onBelowWriteBufferLowWatermark().
UdpProxyFilter::TunnelingActiveSession::onBelowWriteBufferLowWatermark flushes datagrams buffer and calls upstream_->encodeData.
Envoy calls NgHttp2Adapter::Send() again (while the first call hasn't been finished yet).
After flushing the buffer and returning from pendingSendBufferHighWatermark(), Envoy writes data on the connection and the Envoy's callback finishes.
NgHttp2 continues to run after the end of Envoy's callback and try to access "session->aob.item" which is already assigned to NULL during nested sends.
Envoy crashes (Note: We've tried to use OgHttp2 instead and Envoy wasn't crashing because in OgHttp2 they have a check which validates that the session isn't in "sending" state and skip sending otherwise).

The solution for the issue is to post UDP buffer flushing on the UDP listener dispatcher instead of the flushing immediately in the callback.
Risk Level: low
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:

/retest

/retest

Thanks for the fix @IssaAbuKalbein  -- any chance we could get a unit test repro also?


Added tabs on explore page, and added users page

Trello: https://trello.com/c/has1mFRK
Adds tabs to explore page, puts NFTs tab under /explore and Users tab under /explore/users
We are already using /users for profile. maybe we should switch to /profile, just a suggestion.

@EmmanuelDrouin Made the adjustments from your feedback.

I am just dropping by quickly. Keep in mind that the search and explore are on the same page, so we need to ensure that the search also works.
From the home page, do a search for a user, then click on the tab user to see the results.
Expected: we should have the users with only the one matching our search

yes @antho1404 It was discussed today during the prod planning so it will be modified when implementing search

As just discussed with Antho this PR is ok for review as we found the right solution to implement search later one without modifying this structure @ismailToyran Give this PR a review when you get a chance

As this will break some UX on the platform until the search is done, let's merge it into a different branch so the main stays valid. Can you create a new branch, features/explore-search-users, and merge this PR into features/explore-search-users and then when the search PR is coming, merge that PR to features/explore-search-users as well, then later merge features/explore-search-users into main

New branch has been created


ImportError: There is no such class as recipes.LibriSpeech.LM.pretrained.pretrained.LM

When I run SpeechBrain/recipes/LibriSpeech/ASR/transducer/train.py ocurred ImportError like this:
Traceback (most recent call last):   File "train.py", line 367, in <module>     hparams = load_hyperpyyaml(fin, overrides)   File "/home/sardar/anaconda3/envs/SpeechBrain/lib/python3.8/site-packages/hyperpyyaml/core.py", line 182, in load_hyperpyyaml     hparams = yaml.load(yaml_stream, Loader=yaml.Loader)   File "/home/sardar/anaconda3/envs/SpeechBrain/lib/python3.8/site-packages/yaml/__init__.py", line 114, in load     return loader.get_single_data()   File "/home/sardar/anaconda3/envs/SpeechBrain/lib/python3.8/site-packages/yaml/constructor.py", line 51, in get_single_data     return self.construct_document(node)   File "/home/sardar/anaconda3/envs/SpeechBrain/lib/python3.8/site-packages/yaml/constructor.py", line 55, in construct_document     data = self.construct_object(node)   File "/home/sardar/anaconda3/envs/SpeechBrain/lib/python3.8/site-packages/yaml/constructor.py", line 107, in construct_object     for dummy in generator:   File "/home/sardar/anaconda3/envs/SpeechBrain/lib/python3.8/site-packages/yaml/constructor.py", line 413, in construct_yaml_map     value = self.construct_mapping(node)   File "/home/sardar/anaconda3/envs/SpeechBrain/lib/python3.8/site-packages/yaml/constructor.py", line 218, in construct_mapping     return super().construct_mapping(node, deep=deep)   File "/home/sardar/anaconda3/envs/SpeechBrain/lib/python3.8/site-packages/yaml/constructor.py", line 143, in construct_mapping     value = self.construct_object(value_node, deep=deep)   File "/home/sardar/anaconda3/envs/SpeechBrain/lib/python3.8/site-packages/yaml/constructor.py", line 102, in construct_object     data = constructor(self, tag_suffix, node)   File "/home/sardar/anaconda3/envs/SpeechBrain/lib/python3.8/site-packages/hyperpyyaml/core.py", line 420, in _construct_object     raise ImportError("There is no such class as %s" % callable_string) ImportError: There is no such class as recipes.LibriSpeech.LM.pretrained.pretrained.LM

It looks like the LibriSpeech/ASR/transducer recipe is outdated. @aheba could you please take a look at that?

Thanks, @Sar-Dar, we fixed the issue.


[Bug] ./gradlew not found - multi-module Gradle project

Plugin Name
@nxrocks/nx-quarkus
Plugin Version
4.1.0
Nx Version
15.4.1
Expected Behaviour
I'm trying to transition my multi-module Gradle project into an Nx workspace.
I currently have one gradlew binary at the root of the project, but as soon as I run one of the projects within the workspace via Nx, it looks for the executable within the application folder, not the root of the project.
Is it somehow possible to tell this plugin to look for Gradle in the project's root instead?
Actual Behaviour
Executing command: ./gradlew quarkusDev
/bin/sh: 1: ./gradlew: not found
Failed to execute command: ./gradlew quarkusDev
Error: Command failed: ./gradlew quarkusDev
    at checkExecSyncError (node:child_process:861:11)
    at execSync (node:child_process:932:15)
    at runBuilderCommand (/home/user/workspace/nx-nuxt-3-gradle-quarkus/node_modules/@nxrocks/common/src/lib/core/jvm/utils.js:20:38)
    at runQuarkusPluginCommand (/home/user/workspace/nx-nuxt-3-gradle-quarkus/node_modules/@nxrocks/nx-quarkus/src/utils/quarkus-utils.js:14:43)
    at /home/user/workspace/nx-nuxt-3-gradle-quarkus/node_modules/@nxrocks/nx-quarkus/src/executors/dev/executor.js:10:60
    at Generator.next (<anonymous>)
    at /home/user/workspace/nx-nuxt-3-gradle-quarkus/node_modules/tslib/tslib.js:118:75
    at new Promise (<anonymous>)

Steps to reproduce the behaviour

Add Quarkus app to apps of Nx workspace
Pull out settings.gradle into root and all Gradle binaries + the wrapper directory
Create the build.gradle in root

plugins {
	id 'java'
    id 'io.quarkus'
	id 'maven-publish'
}

subprojects {

    apply plugin: 'java'
    apply plugin: 'idea'

    repositories {
        mavenCentral()
        mavenLocal()
    }

    dependencies {
        implementation enforcedPlatform("${quarkusPlatformGroupId}:${quarkusPlatformArtifactId}:${quarkusPlatformVersion}")
        implementation 'io.quarkus:quarkus-arc'
        implementation 'io.quarkus:quarkus-resteasy-reactive'
        testImplementation 'io.quarkus:quarkus-junit5'
        testImplementation 'io.rest-assured:rest-assured'
    }

}

group 'com.example'
version '1.0.0-SNAPSHOT'

java {
    sourceCompatibility = JavaVersion.VERSION_17
    targetCompatibility = JavaVersion.VERSION_17
}

test {
    systemProperty "java.util.logging.manager", "org.jboss.logmanager.LogManager"
}
compileJava {
    options.encoding = 'UTF-8'
    options.compilerArgs << '-parameters'
}

compileTestJava {
    options.encoding = 'UTF-8'
}

publishing {
	publications {
		mavenJava(MavenPublication) {
			artifact jar
		}
	}
}
tasks.withType(GenerateModuleMetadata).configureEach {
	suppressedValidationErrors.add('enforced-platform')
}

Add the application as an include in settings.gradle

pluginManagement {
    repositories {
        mavenCentral()
        gradlePluginPortal()
        mavenLocal()
    }
    plugins {
        id "${quarkusPluginId}" version "${quarkusPluginVersion}"
    }
}

include ":apps:app-name"

rootProject.name='root-project-name'

Hi @mklueh
Thanks for using the plugin and for opening an issue.
What you described is rather a feature than a bug.
The philosophy of this plugin is to be as close as possible to what is generated by the official Quarkus code generator (that the plugin uses behind the scenes) , and right now,  it does not support multi-module projects either.
Also, all build commands are run in the context of a specific project (application or library) in the Nx workspace,
which means that we use the build.gradle within that project and cannot rely on one globally available at root level (not standard).
That being said,  I will continue thinking about a way to achieve that right in the plugin, for both Gradle and Maven build systems

@tinesoft thanks for clarifying.
I currently solved it by just doing
"targets": {
    "build": {
      "executor": "nx:run-commands",
      "cwd": "/",
      "options": {
        "command": "./gradlew :apps:first-app:first-app-server:build"
      }
    }
  },

Which is a bit redundant if you have to define one new target for each Gradle command and project


Pipe methods can return complex valued ouputs

Pipe class methods can return complex-valued outputs. This was observed when running unit tests in pipes_tests for the MultipleUTube configuration.
This could be fixed using np.real() either on the Multipole method (preferably) when computing the thermal resistance matrix or in the class methods themselves.

It seems the cause is the calculation of eigenvalues in MultipleUTube._update_model_variables(). The coefficient matrix _A calculated from the resistances is correctly real-valued.
https://github.com/MassimoCimmino/pygfunction/blob/7d37b8b3bf4b349701681e42281c21cccb54ca42/pygfunction/pipes.py#L1551-L1552


Perplexity Evaluation

Hi, I'm interested in your paper.
I encountered a problem when calculating the GPT perplexity.
As in eval_topic_metrics.py, you used the pre-trained model openai-gpt as the LM. When I run this code, I got such warnings:
Some weights of OpenAIGPTLMHeadModel were not initialized from the model checkpoint at openai-gpt and are newly initialized: ['lm_head.weight'] You should probably TRAIN this model on a down-stream task to be able to use it for predictions and inference.
Whether it means that the GPT PPL is kind of a random number?

Hi,
I seem to get that warning whenever initializing one of these models. If you actually use that pretrained model directly to generate text, it should give reasonable results, though; let me know if that's not the case.


⚠ Spryr has degraded performance

In bc33254, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 6430 ms

Resolved: Spryr performance has improved in 235ad1b after 8 minutes.


x/tools/gopls: reloading metadata for test packages fails (internal/lsp/cmd)

https://golang.org/cl/214717 should not be necessary. It seems that there are go/packages errors (likely related to overlays), that are preventing metadata from being reloaded per-package.
This could also be tied to the fact that we are using a real module in go/packages/packagestest, because there were a number of errors that looked like:
[-: module golang.org/x/tools@latest found (v0.0.0-20200114052453-d31a08c2edf2), but does not contain package golang.org/x/tools/internal/lsp/noparse_format golang.org/x/tools/internal/lsp/folding]

Filed https://github.com/golang/go/issues/36558 to address the confusing nature of the error message. This will be fixed in CL 214717, but I'm going to use this bug to understand why metadata is being reloaded in the cmd tests at all.

It looks like we invalidate metadata because the initial workspace diagnostics have not completed before the snapshot is cloned, so none of the files have "known" file handles. Therefore, all of the tests effectively run from scratch. The real fix here would be to make sure at least the package handles are created before the initial workspace load is considered complete. I wonder if that will have a noticeable effect in the editor.


Doors Extended "Hold Door Open" Desync

Tested with 1x2 wooden door. Desync occurs when pawn opens door and the "hold open" option is checked.

This will be added to the compatibility lists, thank you for the report.


[BUG] ARC Tool issue - Visible label with hidden input.

Describe the bug
A <label> element is referencing a hidden <input> element. This can cause confusion for users relying on screen readers and other assistive technologies, as they may not be able to interact with the hidden input as intended. This violates WCAG 2.2 Success Criterion 4.1.2 (Name, Role, Value).
To Reproduce
Steps to reproduce the behavior:

Open the web application.

Navigate to the "Selecting ENCs" page.

Use a web accessibility testing tool (e.g., ARC Toolkit).

Observe the error regarding the <label> referencing a hidden <input> element.

Expected behavior
Labels should be associated with visible input elements to ensure that users can interact with them correctly. If an input needs to be hidden, consider using an alternative method to ensure it remains accessible.
Screenshots

Additional context
This issue affects the file upload section where a <label> with the class sc-admiralty-file-input is referencing an input that is hidden. Ensure that input elements referenced by labels are visible or provide alternative accessible methods for user interaction.

Fixed on 27th August


Switching PropTypes validation from core React package to 'prop-types'

From v15.5.0 of React, a warning is displayed in the console if PropTypes are accessed from the React package directly. We now have to access PropTypes from the new separate 'prop-types' package. This stops the warning.
Details here: https://facebook.github.io/react/blog/2017/04/07/react-v15.5.0.html

This would be great, I'm wondering if it should be a peerDependency though, rather than dependency

Merged https://github.com/gabergg/react-scrollable-anchor/pull/14 with slightly newer prop-types. Thanks for the PR, sorry for the delay!


Offensive text detection evaluation

This PR introduces a new task offensive-text-classification, for offensive text classification.
Closes #39 .

Added the following changes:

Set up alter_classification_layer to correctly take out_proj into account, so that the correct layer is being replaced. I.e., if the classification layer is classifier.out_proj, then that's what's being replaced, rather than the previous classifier.
Added offensive text classification to the GUI, and set use_auth_token to always be true in the GUI, to allow benchmarking DKHate.


To do app

React ToDo App Tutorial
This is an exercise to consolidate your knowledge about React, components, props, state, and hooks, by following a tutorial.
Learning Objectives

[x] Use JavaScript events.
[x] Use React life cycle methods.
[x] Understand the mechanism of lifting state up.

Hello @John-Arboleda John-Arboleda,
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.


A new release?

Hi!
Is it possible to make a new release? I need to use the tea spoon unit.
BR

Done!
In the future consider also the possibility to use a github repository as a source of the dependency instead of a pub.dev version. It let you use a version of the package that is not yet published


Set default for site parameters where parameter not specified in config

Hello!
I've stumbled upon the very same issue as the https://github.com/dim0627/hugo_theme_beg/issues/19, only part of the image visible on the screenshot where whole should be:

Hi @paskal. I'm unable to reproduce your issue. Images in markdown have max-width set (please inspect the image here for an example). Are you working with the latest version of the theme?
Can you please provide some more detail, or a link to your site where this is an issue?

Thanks for rapid response! Post example, problem code:
![Shinken simple distributed architecture](https://shinken.readthedocs.io/en/latest/_images/shinken-architecture.png)

I guess example you're shown have image defined some other way.

I copied your blog post content and tested it in the theme. I still cannot replicate your issue.
Are you certain that you have the correct theme? Have you made any changes to the CSS?

I guess css doesn't render for some reason. Here is how the main page looks like:

I guess some site.param might be missing and instead of raising error this theme just silently brokes. Could you please run the theme against my blog as-is to see what I'm seeing?

Please ensure you've followed the set-up instructions in the README, particularly those for "Configure your site."

To achieve that I need to put aside my configuration and rewrite it from scratch based on your configuration. Adding sanity checks for input and defaults in case something is not set require additional effort but will let people like me (who already have working site and looking for a new theme) to try it out without touching configuration. The issue I've linked last have interesting conversation on that matter.
If you're not interested in setting defaults for case someone trying to use this theme with their own configuration file, feel free to resolve this issue.

Fair. You make a good point about setting defaults.
Perhaps something to note about Hugo themes in general is that their use of config is a strength. Certainly in this one, you're able to change a lot of the front end just by tweaking a few lines in config -
everything from the CSS dark/light theme style, to whole sections of the page. When I'm trying new themes, I store my current config in a file under a different name, then use the new theme's example config temporarily, so I can see the theme as it was meant to look, without messing anything up. Then if I like the new theme, I just add in any custom parameters I'm using.
I'll look at setting defaults for those parameters where it's possible. Thanks for bringing the case to my attention!

Thanks very much @paskal !


Not collecting own profile Accomplishments section

ScrapedIn Version: 1.0.16
Windows 10 Home Build: 18362.778
WSL: Ubuntu 18.04
Hopefully this isn't because I'm using @mNpenner's creative fix to get the puppeteer dependency to work (since I'm using WSL).
The browser successfully opens, logs into LinkedIn, navigates to the profile page, and scrolls down. That's when the error message is displayed.
Here's my code:
const scrapedin = require('scrapedin')
const fs = require('fs')
const rimraf = require('del');

const PATHS = {
    win32: {
        executablePath: "C:\\Program Files (x86)\\Google\\Chrome\\Application\\chrome.exe",
        userDataDir: 'C:\\Users\\<USER>\\AppData\\Local\\Temp\\puppeteer_user_data',
    },
    linux: {
        executablePath: "/mnt/c/Program Files (x86)/Google/Chrome/Application/chrome.exe",
        userDataDir: '/mnt/c/Users/<USER>/AppData/Local/Temp/puppeteer_user_data',
    },
}

const cookies = fs.readFileSync('linkedincookie.json')
const options = {
  cookies: JSON.parse(cookies),
  puppeteerArgs: {
    executablePath: PATHS[process.platform].executablePath,
    userDataDir: PATHS.win32.userDataDir,
    headless: false,
  }
}

scrapedin(options)
.then((profileScraper) => profileScraper('https://www.linkedin.com/in/raphaelpreston/'))
.then((profile) => console.log(profile))
.finally(async () => {
    rimraf(PATHS[process.platform].userDataDir, {force: true}).then(() => {
        console.log("Deleted")
    })
}).catch(err => {
    console.error(err);
    process.exit(1);
});

The full error message:
Error: Node is either not visible or not an HTMLElement
    at ElementHandle._clickablePoint (/mnt/c/Users/<USER>/<DIR>/node_modules/puppeteer/lib/JSHandle.js:196:13)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async ElementHandle.click (/mnt/c/Users/<USER>/<DIR>/node_modules/puppeteer/lib/JSHandle.js:248:20)
    at async scrapAccomplishmentPanel (/mnt/c/Users/<USER>/<DIR>/node_modules/scrapedin/src/profile/scrapAccomplishmentPanel.js:10:5)
    at async module.exports (/mnt/c/Users/<USER>/<DIR>/node_modules/scrapedin/src/profile/profile.js:50:19)
  -- ASYNC --
    at ElementHandle.<anonymous> (/mnt/c/Users/<USER>/<DIR>/node_modules/puppeteer/lib/helper.js:108:27)
    at scrapAccomplishmentPanel (/mnt/c/Users/<USER>/<DIR>/node_modules/scrapedin/src/profile/scrapAccomplishmentPanel.js:10:25)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async module.exports (/mnt/c/Users/<USER>/<DIR>/node_modules/scrapedin/src/profile/profile.js:50:19)

This is my first time using a package that depends on Puppeteer, so let me know if there's something else I need to do to get stuff working.

After some more testing, I believe this error only occurs on my own profile.

Just tested on ceeb9eefca2efbe4caee889115ce7b25a50ade71, unfortunately still broken. But I'm still only seeing this on my profile.

Thanks for reporting @raphaelpreston ! Honestly, I didn't look for fixing collecting our own profile data, I just placed a warning about not collecting it instead of throwing an error, that's on the new released version v1.0.17.

Related to #79 as error only occurs with own profile


randomly reorder "latest from follows" each day.

I love the "latest from follows" feed. It reminds me to reach out to friends who don't post constantly, feels like an antidote to modern social media.
This is an attempt at improving it, so it shows different content every day.
Caveat:
Testing this was a bit dicey, it seems to work but my VPS was struggling to keep up with the firehose, and I haven't used gorm before.
There was some behavior (caching maybe?) that I wasn't totally understanding, so a gut check on this code would be appreciated.
I think that this janky prng hash should be enough to keep the feed feeling fresh.
here's a similar "hash" function in desmos:
https://www.desmos.com/calculator/ty7o52ayhh

I think that this sorting clause is not correct yet

I think this would also benefit from another compound index on follows?