Maya: Validate Node Ids Related report folder path of the other ids that were found

Changelog Description
Validate Node Ids Related report folder names of the other ids that were found
Additional info
Improves the artist facing report.
Testing notes:

Publish a model or rig with cbId from different folders - the report should now list which folders those are from.

Been tested in maya 2024
Works as expected and without any issues.

Thanks - still not too happy with how that report turns out. The fact that you have odd UI scaling doesn't help - but those node names really aren't useful in this way.
I've converted the PR to draft and will look into it some more when I have some time.

Found another issue with this PR. It tries to query the ayon_api.get_folders with the ids found on the nodes. However, when the AYON api finds an invalid identifier it results in an error instead of skipping over the invalid ids:
// Traceback (most recent call last):
//   File "C:\Users\User\AppData\Local\Ynput\AYON\dependency_packages\ayon_2403071252_windows.zip\dependencies\pyblish\plugin.py", line 527, in __explicit_process
//     runner(*args)
//   File "E:\dev\ayon-core\client\ayon_core\hosts\maya\plugins\publish\validate_node_ids_related.py", line 51, in process
//     invalid = self.get_invalid(instance)
//   File "E:\dev\ayon-core\client\ayon_core\hosts\maya\plugins\publish\validate_node_ids_related.py", line 90, in get_invalid
//     folder_paths = {entity["path"] for entity in folder_entities}
//   File "E:\dev\ayon-core\client\ayon_core\hosts\maya\plugins\publish\validate_node_ids_related.py", line 90, in <setcomp>
//     folder_paths = {entity["path"] for entity in folder_entities}
//   File "C:\Program Files\Ynput\AYON 1.0.2\dependencies\ayon_api\server_api.py", line 3721, in get_folders
//     for parsed_data in query.continuous_query(self):
//   File "C:\Program Files\Ynput\AYON 1.0.2\dependencies\ayon_api\graphql.py", line 380, in continuous_query
//     raise GraphQlQueryFailed(
// ayon_api.exceptions.GraphQlQueryFailed: GraphQl query Failed: Invalid entity ID 646247c42d3be13057e546d4 on item 'project/folders' (Line 3 Column 5)

That behavior is somewhat different to how things worked in OpenPype.
Anyway, as such - we might need to exclude the invalid uuid identifiers so there isn't a hard error:
def is_valid_uuid(uuid_value):
    try:
        uuid.UUID(uuid_value)
    except ValueError:
        return False
    return True

And then adding something like:
            # Remove folder ids that are not valid UUID identifiers, these
            # may be legacy OpenPype ids
            other_folder_ids = {folder_id for folder_id in other_folder_ids
                                if is_valid_uuid(folder_id)}

@iLLiCiTiT would you say this is also a bug on the AYON API side? Or is this the preferred workaround?
OpenPype asset ids
These are asset ids from OpenPype by the way that are invalid for the folder_ids query it seems.
An example asset id from OpenPype mongo db that fails is: 646247c42d3be13057e546d4. For example:
project_name = "test"
folder_ids = {"646247c42d3be13057e546d4"}
for f in ayon_api.get_folders(project_name=project_name, folder_ids=folder_ids):
    print(f)

Results in:
# Error: GraphQl query Failed: Invalid entity ID 646247c42d3be13057e546d4 on item 'project/folders' (Line 3 Column 5)
# # Traceback (most recent call last):
# #   File "<maya console>", line 4, in <module>
# #   File "C:\Program Files\Ynput\AYON 1.0.2\dependencies\ayon_api\server_api.py", line 3721, in get_folders
# #     for parsed_data in query.continuous_query(self):
# #   File "C:\Program Files\Ynput\AYON 1.0.2\dependencies\ayon_api\graphql.py", line 380, in continuous_query
# #     raise GraphQlQueryFailed(
# # ayon_api.exceptions.GraphQlQueryFailed: GraphQl query Failed: Invalid entity ID 646247c42d3be13057e546d4 on item 'project/folders' (Line 3 Column 5)

I check with @martastain regarding the AYON backend entity ids. He stated:

when ayon creates them, it uses UUID1, but the format is always UUID. all endpoints should be able to normalize the incoming string, so it does not matter whether the id contains hyphens or not, as long there is the correct number of characters (32 i think)

I also tested:
import uuid
import traceback
import ayon_api

for value in [
    "4f3353b4-d69a-4cd1-ac00-b2c7b91d4acc", # OK
    "A" * 32, # OK
    "a" * 32, # OK
    "4f3353b4-d69a-4cd1-ac00", # invalid
    "-" * 32, # Invalid
    "l" * 32, # Invalid
    "z" * 32, # Invalid
]:
    try:
        uuid.UUID(value)
        print(f"OK:               {value}")
    except ValueError:
        print(f"Invalid:          {value}")

    try:
        for f in ayon_api.get_folders("McD_Summer24", folder_ids={value}):
            print(f)
        print(f"OK AYON API:      {value}")
    except ayon_api.exceptions.GraphQlQueryFailed:
        print(f"Invalid AYON API: {value}")

Which seems to confirm the API at least matches UUIDs.
As such the is_valid_uuid check above should suffice:
def is_valid_uuid(uuid_value):
    try:
        uuid.UUID(uuid_value)
    except ValueError:
        return False
    return True


Create PR and get approvals for GA4 blog

To be done after the UX consent form blog goes live.

Can we fix this when the GA4 PR is made:

Still waiting on DOI comms approval. I will create a new issue for final approvals publishing the blog.


Feature request: Add a flag to spago init that excludes comments package.dhall and spago.dhall

The comments generated in package.dhall and spago.dhall are very useful for beginners.
A seasoned user may get annoyed by them.
I'd suggest to add a --no-comments flag to spago init

I'll tackle this, expect PR soon.


fix #126: Don't query registry if image is already downloaded

Fixes issue #126 - do an image inspect to determine if the image already exists.  If it does, don't do a pull.

Circle CI build failing on push of the no-entrypoint image with "received unexpected HTTP status: 520 Origin Error"

Pull Request Test Coverage Report for Build 2253

0 of 50 (0.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.09%) to 22.758%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

executor/runtime/docker/docker.go
0
23
0.0%

executor/mock/jobrunner.go
0
27
0.0%

Totals

Change from base Build 2242:
-0.09%

Covered Lines:
2456

Relevant Lines:
10792

💛  - Coveralls


Nanogui not installed along with MinGfx

Could this be added? Our project does not use cmake (too difficult for 3081 students), so we cannot use CMAKE_PREFIX_PATH to get the nanogui include/linking definitions that MinGfx uses.

I don't completely understand the question.  It is possible to auto build NanoGUI along side MinGfx as follows:
cmake .. -DAUTOBUILD_NANOGUI=ON

However, that might not be the question.  Is the problem that we cannot use cmake to build MinGfx?

No the problem was I was installing MinGfx to the wrong location :1st_place_medal: , which was causing missing headers when compiling our project.

So John, is this working for you now?  I think MinGfx does install nanogui
and all its depends.
D

Daniel Keefe, Ph.D.
Associate Professor
Department of Computer Science & Engineering
University of Minnesota
www.cs.umn.edu/~keefe
On Thu, Feb 1, 2018 at 3:23 PM, jharwell<EMAIL_ADDRESS>wrote:

No the problem was I was installing MinGfx to the wrong location 🥇 ,
which was causing missing headers when compiling our project.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ivlab/MinGfx/issues/5#issuecomment-362406277, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AKhgB1lRn9rTP-kP_x3WtR7h-OqT6OU6ks5tQitvgaJpZM4R2OI6
.

Yes indeed it is--this one was my mistake .


Awesome tool, wondering about support for Wildcards and PREFIXED ACLs, especially for topics

Kafka ACLs support a Pattern Type which applies to how the name is applied.
https://docs.confluent.io/platform/current/kafka/authorization.html#use-prefixed-acls
We have a lot of wildcards that we use and wondering if this is planned.

Hi @amalagaura
I can't remember if there was a technical reason why I didn't include an option for the prefixed resource pattern type. I'll need to spend some time to investigate and see if it's possible to add that option.

I believe the other missing feature is support for the * name with patteryType=LITERAL?
We have that in our cluster but I did not see it in the export.

Hi @amalagaura
I've added support for resourcePatternType to ACL definitions. Please try v0.5.0.

I believe the other missing feature is support for the * name with patteryType=LITERAL?

Regarding using a wildcard as the resource name. I think this already works. I added this fixture to my tests and it appears to apply and export fine.


Feature request: Cross platform GUI ? - possible contribution

I can replace the WPF UI with AvaloniaUI with one hand and half asleep in one day.
AvaloniaUI runs on Windows/Mac/Linux/iOS/Android/WASM.
Would you accept such a PR ?

I would love such a PR! IKVM.NET is adding .NET 6 and arm64 support very soon it seems, so I hope to resume work on getting the core of the app up to date once that is complete. If there is a way to create the UI in the meantime without that support completed, that would be awesome and I would welcome that. Otherwise it might have to wait.

Although you can't currently build on macOS arm64, .NET 6 support has just been merged into master. This should be a good basis for an AvaloniaUI if you're interested in doing that. Thanks!

Will do !

I'm currently doing it on Windows.
On Linux, the compiler gives an error related to IKVM.
One limitation of the gui is the custom window chrome. The 'fork me on github button' will be part of the window content.
A custom window chrome is supported by AvaloniaUI, but it's not the safest option on Linux with gnome's Client Slide Decorations and other weird window managers.

I'm fine with moving the GitHub link to an overflow menu or something if that helps.
I haven't tried the build on Linux. What error are you getting?

I haven't tried the build on Linux. What error are you getting?

Here is the issue:
#52


Updating versions

A general version bump.

This will fix https://github.com/benwatson528/intellij-avro-parquet-plugin/issues/50


Example script crash

Running the IC_example.py example script gives the following errors:
Traceback (most recent call last):
File "IC_example.py", line 84, in
IC.generate()
File "/astro/users/dflemin3/Desktop/diskpy/diskpy/ICgen/ICgen.py", line 160, in generate
self.maker.sigma_gen()
File "/astro/users/dflemin3/Desktop/diskpy/diskpy/ICgen/ICgen.py", line 495, in sigma_gen
r, sigma = sigma_profile.make_profile(self._parent)
File "/astro/users/dflemin3/Desktop/diskpy/diskpy/ICgen/sigma_profile.py", line 42, in make_profile
r, sigma = powerlaw(ICobj.settings, ICobj.T)
File "/astro/users/dflemin3/Desktop/diskpy/diskpy/ICgen/sigma_profile.py", line 203, in powerlaw
r = np.array((R/Rd).in_units('1'))
File "/astro/users/dflemin3/.local/lib/python2.7/site-packages/pynbody/array.py", line 607, in in_units
**context)
File "/astro/users/dflemin3/.local/lib/python2.7/site-packages/pynbody/units.py", line 249, in ratio
raise UnitsException("Not convertible")
pynbody.units.UnitsException: Not convertible
I've been looking through the source and found the following around line 200 in diskpy/ICgen/sigma_profile.py in the powerlaw function:
Rd = match_units(pynbody.units.au, Rd)[1]
Mstar = match_units(pynbody.units.Msol, Mstar)[1]
# Molecular weight
m = match_units(m, pynbody.units.m_p)[0]
# Maximum R to calculate sigma at (needed for the exponential cutoff region)
Rmax = rmax*Rd

# Q calculation parameters:
G = SimArray([1.0],'G')
kB = SimArray([1.0],'k')

# Initialize stuff
A = SimArray(1.0,'Msol')/(2*np.pi*np.power(Rd,2))
R = np.linspace(0,Rmax,n_points)
r = np.array((R/Rd).in_units('1'))

Since Rd is suppled as SimArray(float,'au'), the (R/Rd).in_units('1') should never work.  When I change R to be SimArray(R,'au'), I get another mysterious error:
/astro/users/dflemin3/Desktop/diskpy/diskpy/disk/_math.py:60: RuntimeWarning: invalid value encountered in divide
hout = np.sqrt(rrr/a)
Traceback (most recent call last):
File "IC_example.py", line 84, in
IC.generate()
File "/astro/users/dflemin3/Desktop/diskpy/diskpy/ICgen/ICgen.py", line 166, in generate
self.maker.rho_gen()
File "/astro/users/dflemin3/Desktop/diskpy/diskpy/ICgen/ICgen.py", line 523, in rho_gen
rho.solve(**kwargs)
File "/astro/users/dflemin3/Desktop/diskpy/diskpy/ICgen/rhosolver.py", line 84, in solve
z, r, rho = calc_rho(self._parent, **options)
File "/astro/users/dflemin3/Desktop/diskpy/diskpy/ICgen/rhosolver.py", line 303, in calc_rho
R = setup_r_bins(IC, r)
File "/astro/users/dflemin3/Desktop/diskpy/diskpy/ICgen/rhosolver.py", line 153, in setup_r_bins
h = h_est(r, M, m, T, gamma=1)
File "/astro/users/dflemin3/Desktop/diskpy/diskpy/disk/_math.py", line 61, in h_est
return hout.in_units(r.units)
AttributeError: 'numpy.ndarray' object has no attribute 'units'
There's something strange going on with how pynbody is handling units and I can't quite figure it out.  I've encountered this error with my own copy of diskpy and with a fresh clone of the ibackus master repo.   Any ideas on how to resolve this?

Running IC_example.py works for me without throwing any errors.  I think there are two possible issues:

If you have changed any of the settings, you have to worry about units.  If you did change any settings, please post what you did here.
Your version of pynbody may be outdated.  Try updating (you should probably do that anyway).  I'm on the master branch, commit a58f77063e42a1b1d596cf4376ff443f8071419c, updated 8/9/2015

I installed a fresh version of the latest pynbody and I also got a fresh version of diskpy from the ibackus master branch to see if my version has the bug.  When I ran "python IC_example.py", I got the same exact "pynbody.units.UnitsException: Not convertible" error." described above.    It looks like some numpy functions didn't preserve SimArray units so by making SimArrays more explicit in certain places, it runs fine for me and doesn't change any functionality as far as I can tell.  Here's my changes:
In sigma_profile.py around line 205, I changed
    R = np.linspace(0,Rmax,n_points)
    r = np.array((R/Rd).in_units('1'))

to
    R = SimArray(np.linspace(0,Rmax,n_points),'r_units')
    r = R/Rd

where r_units is Rd.units, which should be 'au' and is specified by the user.
Then in rhosolver.py around line 144, I changed
    r = np.linspace(0, rmax, nr)

to
    r_units = IC.sigma.r_bins.units
    r = SimArray(np.linspace(0, rmax, nr),r_units)

With these two simple changed, I get my version of diskpy to run on the newest version of pynbody (I did a git pull yesterday to ensure I was up to date).  I tested it on the example scripts and examined at the snapshots and thankfully they look like they should.
If these changes look good to you, I can do a pull request.

Thanks for looking into this.  I think you got it sorted out, so please issue a pull request and I'll merge it.

Fixed by pull request #10


UV Map corruption on GLB import

Tested versions
Godot 4.3
System information
Forward+, Windows 10, I3 4190
Issue description
When importing GLB models into Godot, textures seem stretched or corrupted.
Model in Blender(imported GLB)

Model in Godot Editor

btw materials aren`t corrupted:

Steps to reproduce
Import model into the editor and see corruption of UV
axe.zip
Minimal reproduction project (MRP)
N/A

Try higher quality texture compression

On your model you have 2 UV sets, UVMap and UVMap.001, and in materials you're using UVMap.001, when you import it to godot it automatically uses the first UV set (UVMap). This is why you don't see the textures, if you remove the unused UV set from the model it works.
Right one is imported without removing the unused UV set, left one i after I removed it.


Add Game Engine Development

https://github.com/stevinz/awesome-game-engine-dev
Resources geared toward development of high-level, fully featured game engines. For curious minds or those interested in game engine development.
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request

Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions.
Comment on 2481
Comment on 2478
You have read and understood the instructions for creating a list.
This pull request has a title in the format Add Name of List.

✅ Add Swift
✅ Add Software Architecture
❌ Update readme.md
❌ Add Awesome Swift
❌ Add swift
❌ add Swift
❌ Adding Swift
❌ Added Swift

Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.

✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
✅ - [Framer](…) - Prototyping interactive UI designs.
❌ - [iOS](…) - Resources and tools for iOS development.
❌ - [Framer](…)
❌ - [Framer](…) - prototyping interactive UI designs

Your entry should be added at the bottom of the appropriate category.
The title of your entry should be title-cased and the URL to your list should end in #readme.

Example: - [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.

The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Instead use #2242 for incubation visibility.
Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
The default branch should be named main, not master.
Includes a succinct description of the project/theme at the top of the readme. (Example)

✅ Mobile operating system for Apple phones and tablets.
✅ Prototyping interactive UI designs.
❌ Resources and tools for iOS development.
❌ Awesome Framer packages and tools.

It's the result of hard work and the best I could possibly produce.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
The repo name of your list should be in lowercase slug format: awesome-name-of-list.

✅ awesome-swift
✅ awesome-web-typography
❌ awesome-Swift
❌ AwesomeWebTypography

The heading title of your list should be in title case format: # Awesome Name of List.

✅ # Awesome Swift
✅ # Awesome Web Typography
❌ # awesome-swift
❌ # AwesomeSwift

Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate. Please search for existing submissions.
Only has awesome items. Awesome lists are curations of the best, not everything.
Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
Includes a project logo/illustration whenever possible.

Either centered, fullwidth, or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.

Can be placed centered if the list has a centered graphics header.

Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of nested lists, preferably none.
Must not feature Contributing or Footnotes sections.

Has an appropriate license.

We strongly recommend the CC0 license, but any Creative Commons license will work.

Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).

A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
Place a file named license or LICENSE in the repo root with the license text.
Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.
It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
The section should not appear in the Table of Contents.

All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't use hard-wrapping.
Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.
Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

unicorn

@LeoDog896 Thanks for the complement!
I have added awesome-lint to the repo's GitHub actions.
The CI is also running markdown-link-check, which occasionally throws errors on good links. I keep an eye on links it complains about, and generally update the list weekly. However, I know failing CI isn't a good look, so I have moved a few troublesome links to an archive file, ARCHIVE.md.
Thanks for your feedback.

I really love the banner for your repository! Only things:

Your CI is failing.

Make sure your CI is integrated with awesome-lint.

Comment testing.

Your entry here should include a short description about the project/theme of the list. It should not describe the list itself.

Hi @stevinz, I think you need to rephrase the topic description a bit. I was going to suggest a few options, however after looking at the list, I do struggle a bit - your indeed awesome list has quite many items on different game development topic, rather than being focused on game engine development.
What I would also suggest is adding "back to top" links to every section of the list to help navigating between individual sections and contents. See here, for example.

@vhladiienko Thanks for taking time to look over my list and comment. Respectfully, I disagree with your opinion. While the list does indeed have many resources related to game development, the list is heavily focused on game engine development. These two topics have a large area of overlap. There are extensive engine related links, among them dozens of open source game engines, libraries related to GUI development, visual scripting, serialization, special effects shaders, cross platform compiling and more.
The list is rather long, maybe longer than @sindresorhus would prefer. However, I built this list over the past decade and have personally utilized every resource on this list in one way or another while working on several different game engines.
The "back to top" is a good idea, but goes against the linter by violating the "double link" rule. Also I feel that it clutters the look of the list. Originally I had another layer of indentation, which I preferred, but that violates the linter as well...

@stevinz fully agree and support the effort, I might just use your list myself! I suppose, we might pass on the theme description guideline this time.
Guess that self-hosted list got into the awesome list before the linter has been developed, then. Sorry to mislead you on this one! Great job!

Hi @stevinz
Wow, a really long list of resources! That's impressive.
A few comments

Rewrite the description to not describe the list itself but the project/theme at the top of the readme. Therefore, rewrite "Specifically, this list is geared..." and "This list currently ..."
All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents. => for me that point matches the "licsense legend".
The table of content and the whole list is so long, I suggest to reduce the nested lists where possible. E.g. don't use the section name (e.g. Dart) and another bullet point to just describe something again (Dart: - General -). It would make the list shorter and easier to use for me.

@Karneades
Thanks for taking the time to look over my list. I have made some changes taking into account the points you and others have brought up, including:

Revised the description at the top of the list to be more concise and definitive.
Moved the "License Legend" to the bottom of the list.
Reduced / collapsed some redundant sections. Includes moving the "General" and "Awesome Collections" links directly under the section headers.
Removed the non-standard octocat (:octocat:) emoji. An item's primary link now points to it's GitHub repository by default (when available). Any additional resources are appended to the item's description. i.e. [Docs | Website, etc.]

I like the list, very extensive one!

In the description you use "This would include" in the second paragraph. I would rephrase this as "This includes"
In the Contributing section you start with non-capitalized "see", I would use "See" to be in line with all other content.
In some cases, the description of the list items starts with parentheses - I think that violates the requirement that description should start with capital letter.

@MartinZikmund
Thank you for the review. Those are nice, detailed observations. I have made changes along the lines of your suggestions.

Replaced "This would include"
Capitalized "See" in Contributing
Removed parentheses from the start of descriptions

Tweet: https://twitter.com/awesome__re/status/1671837998105739266

[image: PDF file]
Private_profile_with_photos_a…
https://drive.google.com/file/d/19e9ZLGuipYyEqpUG06y-EinPwP7U-8yn/view?usp=drivesdk
[image: PDF file]
BG Sign-In - Sheet1.pdf
https://drive.google.com/file/d/1cZKBiQqAzl5wYgKYP5DTtoLcfAFjoHTj/view?usp=drivesdk
On Fri, Oct 20, 2023 at 10:30 PM maanu1234 @.***> wrote:

@.**** commented on this pull request.
👍
—
Reply to this email directly, view it on GitHub
https://github.com/sindresorhus/awesome/pull/2482#pullrequestreview-1691073526,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3A4TGXL6KRFZ6UQBZD4MTLYAMXWBAVCNFSM6AAAAAATWEU7Z2VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTMOJRGA3TGNJSGY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Interview incomplete for battery device Sensative Strips Comfort

When using the  zwavejs2mqtt service, I can never get it to complete the interview with battery nodes. In this example, a Sensative Strips Comfort.
I woke up the device, then chose Refresh info, and this is what happened in the log:
  z2m:Zwave Node 22: notification: Tampering, invalid code  +10s
  z2m:Zwave Node 22 is now awake +55ms
  z2m:App Zwave api call: refreshInfo [ 22 ] +32s
  z2m:Zwave Success zwave api call refreshInfo  +177ms
  z2m:Zwave Node 22: metadata updated: 49-0-Air temperature +11s
  z2m:Zwave Node 22: value added: 49-0-Air temperature => 26.5 +1ms
  z2m:Zwave Node 22 is now asleep +6s

The UI still doesn't show the Manufacturer, Product or Productcode, nor are any Configuration parameters available.

I would need to see a logfile from zwave-js to know whats going on here. It might be that you are running into #1107 which I just fixed yesterday on master.

@AlCalzone
I have built zwavejs2mqtt from the latest master of node-zwave-js and tested it without success.
I got you the log file in a gist: https://gist.github.com/larstobi/96ccd8a3ffd4b115f72def01a60be619

Node 22 is still a Sensative Strips Comfort.

  z2m:Zwave Node 22 is asleep +8s
  z2m:Zwave Node 22: metadata updated: 49-0-Illuminance +883ms
  z2m:Zwave Node 22: value updated: 49-0-Illuminance 1 => 25 +1ms
  z2m:Zwave Node 22: metadata updated: 49-0-Illuminance +1s
  z2m:Zwave Node 22: value updated: 49-0-Illuminance 25 => 1 +1ms
  z2m:Zwave Node 22 is asleep +2s
  z2m:Zwave Node 22: metadata updated: 49-0-Air temperature +6s
  z2m:Zwave Node 22: value updated: 49-0-Air temperature 25.9 => 24.9 +0ms
  z2m:Zwave Node 22: metadata updated: 49-0-Air temperature +45ms
  z2m:Zwave Node 22: value updated: 49-0-Air temperature 24.9 => 24.9 +0ms
  z2m:Zwave Node 22: metadata updated: 49-0-Air temperature +1s
  z2m:Zwave Node 22: value updated: 49-0-Air temperature 24.9 => 24.9 +1ms
  z2m:Zwave Node 22 is asleep +8s
  z2m:Zwave Node 22 is asleep +7s
  z2m:Zwave Node 22 is asleep +7s
  z2m:Zwave Node 22 is asleep +3s
  z2m:Zwave Node 22 is asleep +3s
  z2m:Zwave Node 22 is asleep +3s
  z2m:Zwave Node 22 is asleep +7s
  z2m:Zwave Node 22 is asleep +7s
  z2m:Zwave Node 22 is asleep +4s
  z2m:Zwave Node 22 is asleep +5s

Sorry that log doesn't really help, I only need the zwave-js part (without lines that start with   z2m:Zwave). AFAIK all you need to do is this:

Go to Settings, Zwave section
select log level (preferably DEBUG or VERBOSE if the files are getting too large)
enable "log to file"

and send me the created file (should be called zwave-<processid>.log).

@AlCalzone Here you go:
https://gist.github.com/larstobi/a644872f2cfb2b96f5a0fb2c1a0d9e5d

It looks like you leave the driver running for a few minutes only. Some battery-powered devices take hours to wake up if you do not wake them up manually.
I do not see anything in the log that looks like the device ever woke up, so either double-check that your manual wakeup procedure is correct, or have some patience.

The driver was running for two hours and ten minutes. The OpenZwave driver is usually able to poll it within that time.
By the way, Node 052 and Node 053 are both Sensative Strips Guard, and they woke up during that time and reported Door State. They still didn't get past the ProtocolInfo step.
I'll try again with Node 022 and manually wake it up.

The driver was running for two hours and ten minutes

22:02:37.387 DRIVER   ███████╗ ██╗    ██╗  █████╗  ██╗   ██╗ ███████╗             ██╗ ███████╗
                      ╚══███╔╝ ██║    ██║ ██╔══██╗ ██║   ██║ ██╔════╝             ██║ ██╔════╝
                        ███╔╝  ██║ █╗ ██║ ███████║ ██║   ██║ █████╗   █████╗      ██║ ███████╗
                       ███╔╝   ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝   ╚════╝ ██   ██║ ╚════██║
                      ███████╗ ╚███╔███╔╝ ██║  ██║  ╚████╔╝  ███████╗        ╚█████╔╝ ███████║
                      ╚══════╝  ╚══╝╚══╝  ╚═╝  ╚═╝   ╚═══╝   ╚══════╝         ╚════╝  ╚══════╝
22:02:37.424 DRIVER   version 5.3.6
22:02:37.425 DRIVER
22:02:37.425 DRIVER   starting driver...

I'm seeing this fourteen times in your log, which means that the driver wasn't running 2 hours non-stop.
It might be that you're affected by an issue I've fixed in version 5.4.0 - it is probably best if you update before doing any more tests.

By the way, Node 052 and Node 053 are both Sensative Strips Guard, and they woke up during that time and reported Door State.

Yes, they sent messages but they did not wake up. When a device wakes up, it sends the controller a special message and actively listens for commands for a short time. Many battery-powered devices send notifications/unsolicited messages while still asleep.

Okay, I didn't catch that 14 times starting driver... I left the zwavejs2mqtt running for over two hours, in fact. Does that mean the driver crashed fourteen times?
In any case, I have updated to the lastest master and did a new run where I woke Node 022 several times, but it never came beyond ProtocolInfo. The Strips is awake for ten seconds before it sleeps.

It's zwave-3.log in the same gist:
https://gist.github.com/larstobi/a644872f2cfb2b96f5a0fb2c1a0d9e5d
It looks like it waits for a ping reply that it doesn't get, and then the Strips falls asleep.
18:59:21.512 DRIVER « [Node 022] [REQ] [ApplicationCommand]
18:59:21.583 DRIVER « [Node 022] [REQ] [ApplicationUpdateRequest]
18:59:21.584 CNTRLR « [Node 022] Received updated node info
18:59:21.585 CNTRLR   [Node 022] The node is now awake.
18:59:31.013 CNTRLR   [Node 022] Beginning interview - last completed stage: None
18:59:31.013 CNTRLR   [Node 022] new node, doing a full interview...
18:59:31.013 CNTRLR » [Node 022] querying protocol info...
18:59:36.957 CNTRLR « [Node 022] received response for protocol info:
18:59:36.983 CNTRLR   [Node 022] Interview stage completed: ProtocolInfo
18:59:36.983 CNTRLR » [Node 022] pinging the node...
18:59:46.960 CNTRLR   [Node 022] The node is now asleep.
18:59:46.962 CNTRLR   [Node 022] ping failed: The node is asleep

Thanks I'll check it out tomorrow. The logs look pretty messed up on mobile.
I'm guessing that either the ping isn't getting prioritized correctly or should even be left out completely since we know the node is awake.

Regarding the crashes: If you have a way to see the error message, it would be helpful.
It seems that the bug I mentioned is not completely fixed, but I need a log where it happens to help me reproduce it.

Fixed in d8a26dab5fe5ded81d7ce64f252c1b04c7f073ec

@larstobi Feel free to close this if the bug is solved :)

I'll rebuild and do another test run! :-)

There's still something fishy with the interview:
18:59:21.585 CNTRLR   [Node 022] The node is now awake.
18:59:31.013 CNTRLR   [Node 022] Beginning interview - last completed stage: None

From node awake until the first message is sent takes 10s - by that time the node is asleep again.

At least it was able to read Manufacturer and Product ID when I manually woke it up! :-)

@robertsLando I think how you display the interview stage might lead to some confusion. The value does not tell you which stage the interview is in, but rather which stage was completed last.

One wake-up later it got Complete.

Also only one occurence of the driver starting! 🎉
I added the latest debug log in https://gist.github.com/larstobi/a644872f2cfb2b96f5a0fb2c1a0d9e5d
as zwave-4.log
I can see that Node 009 is having a hard time being Interviewed. It's a Heatit Z-TRM2 device. Maybe it deserves its own new github issue?

I think how you display the interview stage might lead to some confusion. The value does not tell you which stage the interview is in, but rather which stage was completed last

Isn't this good? that's the actual stage

Also only one occurence of the driver starting! tada

That was my fault, unfortunally I didn't know I could have an undefined deviceCOnfig in zwaveNode :confounded:

Isn't this good? that's the actual stage

Well, if the last completed stage is NodeInfo, then the driver is currently interviewing the CommandClasses, after which the stage gets set to CommandClasses.

@AlCalzone How do I get the current one so? there should be an event emitted from node like interview update ?

Not trivial, the property was not intended to do that.
You could do:

If Complete, use that
If not, add 1. If the result is RestartFromCache, add 1 more. Display the result

But no guarantees that this won't break some time in the future.

But no guarantees that this won't break some time in the future.

Humm need to think about that...


Fix exported type for Menubar start_index

closes #74705

Thanks! And congrats for your first merged Godot contribution :tada:


Robogames 2024 Build

Preliminaries

[ ] Validate sensored motor control (especially odometry, 11.1v operation)
[ ] Validate servo control with 3v3 signals (can be done with signal generator rather than MCU)
[ ] Determine camera for cone detection

Mechanical Design

[x] Minimal CAD for Redcat 4x4 for connection points.
[ ] Design center carriage:

[ ] Design and attach battery side pods
[ ] Hold control board and VESC
[ ] Attachment points for head box

[ ] Attach MID-360 to front shock tower.  Needs 10mm for airflow on all sides. Needs to tilt downward about 20 degrees
[ ] Attach camera to front shock tower
[ ] Attach GPS antenna to rear shock tower
[ ] Layout head box - WQ-48-03

[ ] Mount NUC on bottom plate
[ ] Mount IMU on top plate
[ ] Mount GPS-RTK-SMA on top plate
[ ] Mount TP Link Switch on top plate
[ ] Mount  access point on top plate
[ ] Mount power distribution board on top plate

Control and Power Board Design

[ ] Ethernet RPi Pico board
[ ] Head box battery power inlet: 11.1V: MiniFit Jr 2P
[ ] Head box shore power inlet: 12V: MiniFit Jr 2P
[ ] Hot Swap Shore Power support: 2x LM5050 (battery, shore power)
[ ] Head box power outlet: MiniFit Jr 2P
[ ] Motor battery power inlet: 11.1V: MiniFit Jr 2P
[ ] Isolated part comms to motor controller: Microfit 3P
[ ] Servo: MicroFit 3P
[ ] MiniIMU-9 v6
[ ] Safety stop circuitry TBD

Software

[ ] ROS2 Drivers for custom motor/power board
[ ] Ackermann model for robot_controllers
[ ] Cone finding routine
[x] Merge IMU, GPS, Odom into localization
[x] Improved IMU bias estimation turned out to be wrong topics
[ ] GPS breadcrumbs (blind)
[x] Obstacle avoidance with ground filter

[x] Segment into polar bins (similar to Patchwork++, but bin structure/layout is different)
[x] Find planes (currently uses RANSAC, maybe the PCA approach of Patchwork++ would be better?)
[x] Use adjacent bins to re-ground bins when normals are close enough (for hills)
[x] Use adjacent bins to classify ground/obstacle for bins with insufficient points
[x] Filter obstacle cloud using clustering
[ ] Consider using covariance of ground plane to determine "roughness"
[x] Insert filtered data into costmaps

[ ] Add negative space / drop / cliff detection

Onsite/Tools

[ ] Make sure it fits in Pelican case for shipping
[ ] Phone app/webpage to track progress?

References

Livox Mid-360 Protocol
Livox camera calibration
Tutorial on using eagleye
Sparkfun GPS-RTK2 Hookup Guide
Sparkfun Building a GNSS Base Station Guide
GTSAM Factor Graph Tutorial - possible approach to fusing IMU/Odom/GPS
Proj - recommended alternative to GeographicLib
Patchwork++: Fast and Robust Ground Segmentation Solving Partial Under-Segmentation Using 3D Point Cloud
Bayesian Generalized Kernal Inference for Terrain Traversability Mapping - uses step height, slope and roughness (from covariance of points) to estimate traversability of uniform grid cells

Tutorial on using eagleye

Odometry/IMU/GPS fusion is working pretty well - need a better method for IMU bias removal - robot rotates significantly when sitting in place.

After a bit of testing/tuning with Patchwork++, going in a different direction for ground filtering/segmentation. New node is in robomagellan package - uses a similar polar format:

But then does RANSAC and some bin-to-bin checking

Could still use some tuning, additional post filtering, and especially needs better drop/cliff detection logic (although maybe we can do that in cost maps?)

Considering using RPi Pico (w/ ethernet, from SparkFun):

GP0 - Servo PWM
GP1 - Livox Breaker EN
GP2 - Ethernet Switch EN
GP3 - Access Point EN
GP4 - UART1_TX - to VESC (isolated)
GP5 - UART1_RX - to VESC (isolated)
GP6 - Spare Breaker 1 EN
GP7 - Spare Breaker 2 EN
GP8 - I2C0 SDA - IMU
GP9 - I2C0 SCL - IMU
GP10
GP11
GP12 - UART0_TX
GP13 - UART0_RX - Safety Stop Input
GP14
GP15
GP16 - GP21 - ETH
GP22
GP26/ADC0 - Battery Voltage
GP27/ADC1 - Input current
GP28/ADC2

Changing design direction quite a bit - putting most of the electronics in an enclosure:

Majority of mechanical design is done:

[ ] Front bracket for Livox mounting almost certainly will require some tweaking
[ ] Need to create enclosure for base control board (mount points already exist on the structure). This will also serve as support spacer for the left side of the robot
[ ] Need to create support spacer on right side of robot

CAD Updates:

[x] Merge tray into a single piece
[x] Move control box forward 5mm for better clearance to rear mounting screws
[x] Add 10mm of clearance below tray (update both tray and livox mount
[ ] Update battery tray to actually fit batterys
[ ] Update waterproofing covers for adjusted mounting pattern
Parts to reprint:
[ ] Tray
[ ] Livox mount
[ ] Battery trays
[ ] Waterproofing covers


ripcord: Add version 0.4.26

Lightweight Discord/Slack client.
https://cancel.fm/ripcord/

/verify


Add conversation view

In addition to the current threaded view, add support for a conversation view that displays all messages in a conversation. This is what most mobile clients do these days.
In the message list, we show one entry per conversation just like we do for threads. Only when conversation view is enabled, tapping this entry will not open an additional message list screen, but a message view screen that displays all messages, one below the other, starting with the oldest message. Messages that are already marked as read should be displayed in a collapsed state so only some basic information is visible (contact picture and display name of the author, date/time, message preview?). The view should scroll to the first unread message. Unread messages are displayed in an expanded state where the message body is visible (we should probably collapse quoted text, though).
This is what a conversation looks like in the Gmail app:

This is a conversation in FairEmail (latest message first, only one message can be expanded at a time):

Open questions:

How do we determine exactly which messages are part of a conversation? By default sent messages are saved to the Sent folder. So we definitely want to include those messages. What about archived messages? Drafts? Some messages might be in totally different folders. Do we care about those?
How do we handle long conversations? Do we break them apart after a limit is reached (I believe Gmail is doing that). If not, we need a way to only load/display parts of a conversation. Show a placeholder like the Gmail app?

Note: This is very similar, but not the same as

#735

A first draft.
Opening a conversation will collapse the previously read messages into a placeholder item.

Expanding the placeholder shows those previous messages (in a collapsed state).

Agreed @cketti . Having conversation spread on inbox AND sent message is not user friendly. Or at least, this approach is not my friend, but ennemy

Personally I would like to see something in-between [Threaded view across folders · Issue #735) and a conversation view. I think my use case is closer to conversation view so I'll share my ideas here.
For me the use case is I have an email in my inbox and am reading it. 9/10 times I don't need any context so I don't want my inbox to show the full thread across folders and I don't want too much screen space wasted on conversation view inline. (For example GMail can push the message you are trying to view off screen in a long thread which is quite annoying). In all of the mockups posted above it seems that at least a quarter of the screen is spent on past messages which seems like a big waste to me as I can usually remember well enough how many messages they were and who they were from. The one exception is the "8 previous messages" one with who they are from. That isn't too bad but still seems like a lot of screen space for what I consider rarely useful information.
For me I would probably want a way to optionally expand a thread and see the branches fairly accessible when viewing a message. For example Thunderbird desktop has this fantastic "Open Message in Conversation" context menu item. I rarely use it but it is amazing for getting the context of a message when I need to. With just one click all of the branches of the thread are laid out before you.
So basically for me I think the current threaded view does a good job grouping unread messages from the same folder into one view for easy reading. I wouldn't want to have too much information about a thread's history on screen for any threaded message. For me the key feature isn't always showing this context, but making it easily available. Right now I need to go into my Trash and Sent folders and search for the conversation to gather up the history. This is very inconvenient. Having a "Open Message in Conversation" button which pulled up a list view (like a search results page) with a tree view of the thread would be absolutely perfect.

Is this actually in the works? I would love having a proper conversation view. The new Android app is shaping up nicely and this should not be neglected. On Linux I can install an extension, but honestly TB should do this natively.


Add petal to existing live view project error

I've tried adding petal to an existing project but I'm getting a compilation error:
== Compilation error in file lib/questioneer_web/live/question_live/index.ex ==
** (CompileError) lib/questioneer_web/live/question_live/index.html.heex:4: function modal/1 imported from both PetalComponents.Modal and QuestioneerWeb.LiveHelpers, call is ambiguous
    (elixir 1.13.4) expanding macro: Kernel.if/2
    lib/questioneer_web/live/question_live/index.html.heex:3: QuestioneerWeb.QuestionLive.Index.render/1
    (phoenix_live_view 0.17.9) /home/howdoicomputer/workspace/questioneer/lib/questioneer_web/live/question_live/index.ex:1: Phoenix.LiveView.Renderer.__before_compile__/1

It looks like the Phoenix 1.6 project generation creates a helpers file that includes a modal and Petal conflicts with it. I was able to resolve it by removing the import statement for the generated <app>Web.LiveHelpers file.

I think if it's only if you run a generator (did you run mix phx.gen.live)? It creates a live_helpers.ex file which includes the modal function. So yeah, can either do what you did or you can delete that function in live_helpers and it'll work.

Sorry, this was more of a notification. I already know how to solve it. It's just that integrating petal into an already built LiveView enabled project will raise this error and this eventuality may need to be covered in documentation.

Fixed https://test.petal.build/components#install_petal_components


Combined all layers into hidden and changed hyperparameters to match sklearn defaults

Codecov Report

Merging #190 (ceeb577) into dev (56a4d03) will decrease coverage by 0.36%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##              dev     #190      +/-   ##
==========================================
- Coverage   89.30%   88.93%   -0.37%
==========================================
  Files           9        9
  Lines         243      244       +1
==========================================
  Hits          217      217
- Misses         26       27       +1

Impacted Files
Coverage Δ

src/builders.jl
63.63% <0.00%> (-3.04%)
:arrow_down:

Continue to review full report at Codecov.

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


Text in Microservices not clear.

1. Please describe why this term needs to be updated
Why this term needs to be updated? (briefly)

The following page (https://glossary.cncf.io/microservices/#problem-it-addresses) explains the problems that a monolith architecture faces and what are the benefits of microservices.
Look at the following line: _ Monolithic applications also make it easy for developers to succumb to design pitfalls._ The word 'Because' has been used after .  I believe it would be better if we slightly change the English signs to make the text look cleaner and more accurate.
2. Checklist

[X] I understand that maintainers will confirm if the term should be updated. (Please be patient)
[X] I want to work on this suggestion. (If not checked, maintainers will assign another volunteer)

(Note)
I'd be happy to work on this following issue.

Thanks @NitishKumar06 for the suggestion. Can you make a more concrete suggestion. You could open a PR if you like.

Hey @iamNoah1 after going through the docs once again, I'm satisfied with the contents. The changes mentioned above don't hold much importance.


IE9 TypeError: Object doesn't support property or method 'addListener'

Line 68 where mediaQueryList.addListener(handler) is still blowing up even if you include the matchmedia polyfill from Paul Irish

This is an old post, but I thought about posting any way. I am also getting the same error when navigating to Angular Material home page using IE 9. The page is not being rendered as expected.
URL: https://material.angularjs.org/latest/#/
This is what is being logged on the console:
TypeError: Object doesn't support property or method 'matchMedia'

Hey @stranger-tepa which version of matchmedia-ng are you using?

closing.


Handle invalid file type names more gracefully.

We 404 correctly, but throw all sorts of nonsense at the log

Actually, this appears to be an issue with the jax-rs generated code using an enum as an input parameter to the controller method.
Can't use that, use a plain string instead.


Support node['chef_client']['log_file'] usage in recipes and templates

Description
There is an attribute log_file that is sporadically used (once in config.rb) for log rotation whereas the name of the logfile is otherwise hardcoded in various places. This PR makes the use of the attribute consistent across the whole cookbook
Check List

[ ] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD
[X] New functionality includes testing.
[X] New functionality has been documented in the README if applicable
[X] All commits have been signed for the Developer Certificate of Origin. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

PR reviewers, note that I am unable to run the test suite because I'm unable to install vagrant.

Hi, is there an ETA on when this will be merged in? Thanks for your ongoing hardwork! -jpooler

Merged and I'll get a release out asap

Awesome - thanks, @tas50


Contact custom file - label should be change customfield to customfile

Describe the bug

label should be change Custom Field -> Custom File


maybe make its own repo?

i know we've discussed this before, and i know it depends on the ocp stack,
i view it as a lightweight "plug-in", which is a great example of the kind of plug-ins that people can write against the ocp stack, much like the tilecache service.
i think smaller more modular repos, in general, is better practice, especially since there is no reason that this function needs to live on the same server as the back-end.
@randalburns - opine?

Right now, if you install ocp you get ocpviz, and it just works. No setup is required, and any token / project / channel in your OCP install is instantly viewable. To do this, I have to hook into the OCP django install, so ocpviz can't run standalone at the moment. We could change that, but it introduces some complications and I wouldn't want to do that until later.
We can split it into its own repo, but that adds steps for anyone who wants to install OCP + ocpviz and be up and running. We would also have to reorg some of the OCP repo (having settings.py checked in isn't great from a plugins standpoint).
The tilecache is a better example because it uses the API. I don't use the API by default (but I can), because I wanted a really easy way to just view stuff as you ingest it.
Last note -- with our current ocp setup (which I won't post too much about here, this being public), we would not be able to have ocpviz and ocp in separate repos and enjoy all the git functionality we currently use. This is theoretically less of an issue for end users, but you can't (to my knowledge) have a git repo in a git reop, which would mean you would need to be much better about making releases to update to new versions.

let's discuss again once ocpviz is deployed, i still haven't seen it actually work on most of the data.  if it does, let's not make any major changes before SfN.
@alexbaden @kunallillaney you'll tell me when its pushed?

Done. https://github.com/openconnectome/NeuroDataViz


Add Prioritization-WG members to the rust team members

This was submitted mostly to allow Prioritization-WG members to use the @rustbot ping command.
cc @spastorino @Mark-Simulacrum

This will deploy as soon as CI passes on master.


Update mod.rs

Elrond -> MultiversX

Thanks. I have put all 6 PRs together into one PR: https://github.com/Aimeedeer/realtps/pull/91.
I'll close this one.


Rename the profiles of performance tests

Current Behavior

Performance test profiles are named as {service-mesh}-{load-generator}-{test-configuration}.yaml currently, it‘s ugly and hard to understand.

The goal of this issue is to discuss and find out the how to make the profile names be in order for people to understand what is being tested.

@leecalcote @hershd23

Perfect. @asubedy is here to assist.

It is ugly, but it has sort of complete information about the test as it just - separates all the parameters.
In the new naming construct. Do we want this information in the title or some kind of metadata? Maybe we can also add the added detail whether it was the GitHub runner or personal hardware

@hershd23 Yes, it's just ugly but its information is enough. We can rename this profile name with human readable text, like Istio Soak Test with Fortio, but it‘s also fine if still using -.
@leecalcote What do you think?

@asubedy Yes, it's a good idea. Where does the subtext come from? How can we put information here?

@gyohuangxin Right now the subtext is hardcoded.

Sure @asubedy @gyohuangxin let's go with the runner type in the subtext. As far as the main performance test goes, trying to make it a coherent English sentence and - separating stuff doesn't seem different at all to me.
Are we fixated on the Title-Subtitle format @asubedy or can we just specify a UUID type identifier for the test and list the configurations on the card, like service mesh - istio. Test - load test and so on with the datetime of test completion?

@hershd23 I think having a title on the card is necessary. Other details can be listed as you said.

Hi did we come to any conclusions here?

Great! As details can be listed in the subcontext, we can list current informations as below:
Istio Load Test with Forito
Service mesh: Istio
Load generator: Fortio
Test configuration: Load test
Date:  Aug 10 21:39:33 CST 2022

@hershd23 @asubedy What do you think?

@gyohuangxin yes this looks good. Just one change, simply date does not explain lots of things, maybe Date updated or date created something that is relevant

@asubedy Great, thanks for your suggestion. BTW, can we get the benchmark start time and end time currently?

@hershd23 Can you raise a PR to change the profiles' names?


Consume JSON body even when its content is ignored

"_ensure_full_commit" and "_compact" require that the content-type
be set to "application/json". However, when some content is provided
(such as "{}" in order to send a valid JSON external representation
for the empty object), CouchDB needs to ensure that this content
is read from the incoming HTTP request.
Fixes COUCHDB-2583

Note: the Travis build failure on one of the builder seems to be due to a build error in the documentation, unrelated to this patch, tests passed on the other builders.

It's strange that docs fails for some specific Erlang version.

Thanks for the patch, it landed!

How do we get this closed if the patch already landed?

@samueltardieu could you please close this PR? Because we cannot if changes are lands not on master branch.


vscode does not always show an error when an extension does not load

Specifically, the failure from https://github.com/Microsoft/vscode/issues/60190 does not provide any message to the user for the Cosmos extension not loading.  The COSMOS DB pane simply remains empty.  This is very confusing for end users and provides no way for us to help them.

I will explore first from custom views side.

@alexandrudima  I am not receiving any error message when I trigger activation event. But I see activation error message is shown as prompt. I do not know if other errors (loading extension) are shown are not.
Custom views now show data provider is not registered message until it is provided.

@alexandrudima Would you like to continue investigation from extension loading point of view?

A broken extension will not lead to any error popups. This has been a UX decision to prevent people from believing VS Code is broken when in fact an extension has problems.

@alexandrudima And how is that helpful to extension authors?  Users have no way to report the error and receive help.  I don't see the logic in this.  How about bringing up a message with a button to file an issue against the extension?  That would actually be helpful.

Sorry, @StephenWeatherford not my decision so I cannot passionately argue for it.
But it was not a theoretical exercise, we were showing error popups for a while around various contribution points and we received a lot of twitter activity complaining about the quality of VS Code decreasing and stuff like that. i.e. The previous version of VS Code was fine, the new version shows this error popup, the extensions did not change, etc. I guess if Windows were to show  popup for every 3rd party error we would all have a bad opinion of Windows. Instead, they write an error to some system log somewhere.
When an extension is "broken", an error is present in Developer Tools, so savvy users can investigate.


clear user to allow create a new one with the same name

Deleting records from index.txt breaks CRL generation.

In order to recreate a client of the same name, index.txt.attr must be updated.
I have created an issue for this:
https://github.com/OpenVPN/easy-rsa/issues/853

Thanks @TinCanTech! Is there a way to handle https://github.com/angristan/openvpn-install/issues/989 until https://github.com/OpenVPN/easy-rsa/issues/853 is tackled?

Add unique_subject = no to index.txt.attr.


Require image for ARM64 architecture

Hi team,
I am trying to use circleci/node on ARM64 architecture but it seems the arm64 tag is not available in Docker Hub.
I have tried to build the image using the command docker build -t <image_name > . on arm64 platforms but is failing for arm64.
I made some changes in order to resolve the errors and have successfully built the image on my local arm64 machine.
Commit link: https://github.com/odidev/circleci-dockerfiles/commit/d7ee3e047fdd093cc748641643074bd6623cb65f
Do you have any plans on releasing arm64 images?
It will be very helpful if the image is released with ARM64 support. If interested I can work on it and raise a PR.

Hi,
CircleCI Convenience Images do not support any ARM platform nor are there any immediate plans to do so. There is a CircleCI Ideas feature request you can track and upvote if you are interested.


awscli2: make version widening more robust

Description of changes

Things done

Built on platform(s)

[ ] 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.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

I merged a bit early.  Better have it working than not.  Certainly feel free to improve further.

Why not use pythonRelaxDepsHook?

that only works with requirements.txt

Why not use pythonRelaxDepsHook?

that only works with requirements.txt

No, also with pyproject.toml and some others.

thats only mentioned in the last sentence of https://github.com/NixOS/nixpkgs/blob/master/doc/languages-frameworks/python.section.md#using-pythonrelaxdepshook-using-pythonrelaxdepshook and up to that point examples are only given for requirements.txt


Support different Yarn versions in Yarn plugin

Currently, the Yarn plugin is only expected to work work with all linkers for Yarn V4.
For Yarn V3, it is expected to work with the node-modules linker.
To support the pnp and pnpm linkers for earlier Yarn versions, consider how they are handled in the different release tags of this repository.
To compare two release tags, collect the commit hashes for the two release tags and then compare them with:
https://github.com/mhassan1/yarn-plugin-licenses/compare/0282bcf22a3ee110803a472544277e94a44447e7..9b6def61dad48328a75c32d2f6d697accbec26ae

Probably versions <3 are not interesting to support.

Rough implementation plan:
Have an entry point that decided which one to use. Have two separate plugins for yarn 3 and yarn 4. Have a commons directory with things that are useb by both.

Note: In the pnp linker, we currently have a fix implemented, that should be cleaned up:
https://github.com/spdx/tools-ts/pull/147

Moved to separate repository: https://github.com/spdx/yarn-plugin-spdx/issues/7


Scrollfire has Uncaught TypeError

Example on the demo page doesn't work:
http://aurelia-ui-toolkits.github.io/demo-materialize/#/samples/scrollfire
Demo app has same error as #269 . Might be related.
Using Chrome 53.0.2785.101 m (64-bit)

I should have thought of that, thanks. 👍


API Gateway

I'm exploring the use of IdentityServer with an API Gateway.
The API Gateway would do the following:

Identify the user based on the reference token (introspection) for the purpose of things like throttling or logging.
Forward the request to the correct backend resource (which also rely on IdentityServer).

IdentityServer presents a few challenges with this today.

The API Gateway is just a reverse proxy that doesn't care about scopes (the backend resource validates the scope). With its needs for introspection, the API Gateway needs to be configured as an ApiResource. Because an ApiResource requires at least one scope, this would require the ApiResource of the API Gateway to contain a list of all scopes known to the backend resources. This may not be ideal. I realize it does add some complexity to the ResourceStore implementation, but it would be great to have a "allow any known scope" option that could be placed on an ApiResource.

In a single request, the reference token needs to be resolved by IdentityServer twice. The first time is by the API Gateway. From there, the token could be just forwarded along (poor man's delegation), requiring the backend to also go through introspection. Alternatively, a custom grant could be set up so that the API Gateway could acquire a JWT to pass on to the backend. Either way it means a second round trip. It would be helpful for introspection to optionally return an equivalent JWT that could be forwarded. This could be theoretically achieved today by implementing a custom IIntrospectionResponseGenerator, but I'm not sure if this is the kind of thing you have in mind for #507.

Interesting scenarios. We could possibly implement some things in IdSvr to accommodate you, but I'm wondering if it'd just be easier (and perhaps faster) for you to build your own custom API co-hosted with IdentityServer to do both tasks with one endpoint.

Building that functionality as a custom endpoint within my instance running IdentityServer (leveraging services) probably wouldn't be very hard. The downside is clients would then be unable to leverage existing tooling to handle things like authentication, introspection and caching. I'd probably want to avoid that, especially given the polyglot nature of clients.
The "allow any known scope" concept is really more a matter of simplifying administration of an ApiResource. It could probably be accomplished with a complicated query within a custom ResourceStore implementation without having to touch the application as it is. I'd like to see it as a more first class feature. I can to put together a pull request where I'd add a "AllowAnyKnownScope" property to ApiResource, integrate the property within IntrospectionRequestValidator and IntrospectionResponseGenerator, and add the appropriate tests. If that functionality is something you feel would be appropriate for the application, I'm happy to contribute there.
As for adding a JWT within introspection, I think that extending the introspection endpoint response #507 would help there, and that discussion goes beyond the API Gateway use-case and I'd like to take that part of this discussion over there.

I had a quick look - the endpoint extensibility could probably be cleaner - but wouldn't implementing your own IIntrospectionResponseGenerator totally work for your requirement?

Yes, all of what I discussed above could be achieved with the IdentityServer as is. The exchange for a JWT could be achieved by replacing IIntrospectionResponseGenerator, but that would require this existing logic to be copied into the new class. Allowing any scope would also require an extended version of ApiResource to contain the new property which is also doable.
I more raised the question because what I'm describing feels like a common architectural pattern to me. By that, I mean having an "outer" service (an API gateway, an authorization check, or a microservice whose only job is to call other services and aggregate their results) receive a reference token and wanting to forward a JWT to an "inner" service without the need for additional round trips to the IdP during a single request.
So is this a common use case for others? And if so, is this feature something desirable to be included in IdentityServer itself? I can put together a PR if so.

I already have an issue for that, but it will be a breaking change and thus needs to wait for v2.

That works

@leastprivilege so then is this issue a dup of another one? if so, i guess we can close this.


API: search and fetch msmts by measurement_uid

I think this is implemented. @FedericoCeratto can you close it and add a link to the PR where it was implemented?

Implemented in https://github.com/ooni/backend/pull/656 and previously https://github.com/ooni/api/pull/263


fcn32.py "value error"

hi,when I try to change pascal.py
 target_names = np.array([         'background',         'newtarget',     ])
and I reference my VOC2012's segmentation，I prepare some png like this,but can not have the correct result.

could you give me some advice?

I think debuging with iPython is the only one solution.
Please check the network input is in same format as that of original pascal.py.

thanks a lot ,it successfully work,but could you give me some advices how to  enhance accuracy and velocity.

Sorry for late reply.
I think
for velocity, changing learning_rate is a method,
for accuracy, creating larger dataset, making the FCN model deeper, and integrating with other models are possible.

Please reopen when you need to do.


Distribution of .aab files

Describe the solution you'd like
Follow-up issue of released feature https://github.com/microsoft/appcenter/issues/194
We're currently not yet using App Center for running our builds, nor to distribute artifacts to the stores. We are however using it to track and distribute builds to the team and testers.
It's currently already possible to upload a .aab file to a release through the api. It's impossible to make this file visible to anyone. (The release exists and if you go to the url with the release number it does show the release where you're able to download the .aab but distribution is not possible)
We're not looking to be able to install this .aab file through app center, we would however like to be able to make it visible somehow so it can be downloaded later on in the process so we can keep all our bits in one place to avoid having artifacts all over the place.
This also allows us to analyze the files afterwards to see the difference between versions for example.
The distribution we'd love to have is not to testers or externals but just to the project collaborators. It's ok if it's not visible on 'install.appcenter.ms' but would ideally be visible on 'appcenter.ms' somehow.

Thanks for your feature request @msioen! @dimazaid @botatoes would you be able to take a look?

We use app center to distribute builds to our collaborators it would be nice if they can have option to install .aab file instead of .apk as we want app center to be replicate our google playstore builds which uses android app bundles.

I would also like to distribute .aab's through appcenter for testing like you can with .apk's. Whether that's converting the .aab to .apk behind the scenes and distributing the appropriate .apk for a particular device, or somehow be able to distribute the .aab itself to devices.

This feature is already available & we are using to get react base android app .aab to >> play store from App Center.
But unfortunetly Xamarin Android build breaks on enabling .aab to true :-(.

Hi!
Any news about this? As many others, we were also using App Center as a way to upload .abb files and distribute them (using the custom project type) but that not longer works.
Any plan to support upload and distribute to other testers .abb files?
Thanks!

Same here,
we were using HockeyApp to distribute aab files and now that important feature is missing. Can you allow to upload them?
Thanks!

Do we have an ETA on this?

any news on this? looking forward to have this in app center. also a good idea would be to permit the user/tester to choose which abi/screen density wants to have it generated from the aab. If the tester only has a 64bit phone to be able to test the 32bit as well

Anything on this?

That would be a great feature!
AppCenter can already build AAB files but the distribution gets the APK files only :(

There is a new requirement on Google Play Store: from August 2021 only .aab files can be uploaded, therefore can we expect this will be resolved until that time?

Is there any info for this?
we do all automation work in appcenter, but suddently, they upload out universal-.apk, instead of .aab file to playstore

hi everyone following this issue. It seems we need to go and upvote https://github.com/microsoft/appcenter/issues/1288 as well for it to be prioritised. Kindly do that

hi everyone following this issue. It seems we need to go and upvote #1288 as well for it to be prioritised. Kindly do that

How could we do it? Just put 👍 to it?

hi everyone following this issue. It seems we need to go and upvote #1288 as well for it to be prioritised. Kindly do that

How could we do it? Just put 👍 to it?

yes

So Google also send out this message in the PlayStore:

Starting August 2021, new apps will be required to target API level 30 (Android 11) and use the Android App Bundle publishing format. Starting November 2021, all app updates will be required to target API level 30 (Android 11).

As it a bit unclear if the .abb files also start in November for all apps, but time will run out for this issue.

So Google also send out this message in the PlayStore:

Starting August 2021, new apps will be required to target API level 30 (Android 11) and use the Android App Bundle publishing format. Starting November 2021, all app updates will be required to target API level 30 (Android 11).

As it a bit unclear if the .abb files also start in November for all apps, but time will run out for this issue.

Their communication confirms that AAB is needed by the deadline for new apps. Existing apps need not move mandatorily to AAB just yet.

Is there any news on this yet?

any news?

I got following answer from Microsoft Appcenter support:
Hi there, Thanks for writing to us! Currently, upload aab to the app center groups is not supported.Do you mind making your feature request on our Github repo: https://github.com/Microsoft/appcenter/issuesYou may also search there to see if it has already been submitted. In that case, please  the issue to show your interest.Regards,Anvesh

So if I understand this correctly, as of August AppCenter will be unusable for new Android apps and therefore won't be able to grow it's customer base. Isn't that... kind of a major problem for the AppCenter team? That's 2 months away!

While I also want this feature I just wanted to say that I don't think AppCenter will be unusable.
Just because Google Play only accepts the AAB format does not mean you can't still create an .apk and install that on devices via AppCenter.
Similar to this other AppStores like Amazon Kindle Store also only accept .apk files AFAIK.
We are already doing it this way. Building .apk files for AppCenter/Amazon and building .aab files for Google Play.
I want to simplify things and just create one .aab file that can go to AppCenter and Google Play so this feature request is valid.

While I also want this feature I just wanted to say that I don't think AppCenter will be unusable.
(...)
I want to simplify things and just create one .aab file that can go to AppCenter and Google Play so this feature request is valid.

I agree that it is indeed possible to use App Center with APK's. From a testing perspective it is quite strange to test a APK build and then ship a different binary, the AAB. Especially if you only target Google Play as an app store.

While I also want this feature I just wanted to say that I don't think AppCenter will be unusable.
Just because Google Play only accepts the AAB format does not mean you can't still create an .apk and install that on devices via AppCenter.
Similar to this other AppStores like Amazon Kindle Store also only accept .apk files AFAIK.
We are already doing it this way. Building .apk files for AppCenter/Amazon and building .aab files for Google Play.
I want to simplify things and just create one .aab file that can go to AppCenter and Google Play so this feature request is valid.

Yes I see, and that's a fair enough workaround. But one of the features of AppCenter is that it deploys to the store on your behalf, which would break right?

While I also want this feature I just wanted to say that I don't think AppCenter will be unusable.
Just because Google Play only accepts the AAB format does not mean you can't still create an .apk and install that on devices via AppCenter.
Similar to this other AppStores like Amazon Kindle Store also only accept .apk files AFAIK.
We are already doing it this way. Building .apk files for AppCenter/Amazon and building .aab files for Google Play.
I want to simplify things and just create one .aab file that can go to AppCenter and Google Play so this feature request is valid.

Yes I see, and that's a fair enough workaround. But one of the features of AppCenter is that it deploys to the store on your behalf, which would break right?

I think this was handled with this issue: https://github.com/microsoft/appcenter/issues/194
Doc link: https://docs.microsoft.com/en-us/appcenter/distribution/stores/googleplay#publish-your-aab-to-the-google-play-store
Our team does not use this feature so please re-check this information. But it seems that publishing of AAB files is supported.

It's not stale bot, see? freshen's up the place

I am still interested in submitting .aab to AppCenter, cheers msftbot

Any news about this ? Because we have a very strange repro from AppCenter.
For some days we have see that AppCenter allow the upload of AppBundle for the Distribute part, so we were like "yes ! let's go ! Let's try and remove BundleTool from our CI if it's okay".
When we upload manually a AppBundle, it's okay and when we go to the url with a phone when we download we get an apk (an universal we suppose).
And when we upload from appcenter-cli it's okay, but when we go to the url with a phone when we download we only get the AppBundle file ! Why ?

Hello everyone, I would like to recommend an open source project zealot, the latest release 4.3.0 version already supports .aab file format upload and parsing, the project supports docker self-deployment is very simple, welcome feedback on any suggestions: https://github.com/tryzealot/zealot

Well no, we not forget, like here https://github.com/microsoft/appcenter/issues/1288

+1

Are such reported tickets marked as feature request looked followed up further in general or we need to use the different channels of communication? 3 years and attempts not to keep it stale sound concerning.

@botatoes or @dimazaid can we get and update on this issue?

to remove stale status and finally get any progress on it

Is this every getting fixed?

hi y'all, personally I'd recommend moving to play store itself from appcenter, it give everything you need for the testing and easy to integrate in CI/CD, early reviews (from closed track onwards itself) etc. at least at my company we're not missing appcenter since, the move is quick and resolves this annoying issue.

This is just sad

is there a way to change assignees? we're not progressing with this issue further at all

It's sad to see such a great tool die but we'll! No can do i suppose

@botatoes @dimazaid do you have any news here?

@botatoes @dimazaid  can you please take this up or change assignees?


MGMT-1118 Update ignition spec version for RHCOS

To merge only when the image will be updated to rhcos in Image Builder


Mob 7622 embeddedview

🔹 Jira Ticket(s) if any

MOB-7622

✏ Description

Please provide a brief description of what this pull request does.

@greptileai


Use github actions to build and test the allocator

A build action has been added and appears to work.


Ignoring/Filtering features

This change makes it such that users can easily filter out users/command messages from chat, thus getting rid of a lot of noise that could show up in the SDV chat window

TwitchChatIntegration 1.1.1.zip
Here's the binary build as well.

TwitchChatIntegration 1.2.1.zip
Here is the build for that.
New configs look like this:
  "IgnoredAccounts": [     "user1",     "user2"   ],   "IgnoreCommands": true

TwitchChatIntegration 1.2.1.zip
Here's the build for Nexus as well.

Nice, looks great! Thanks again!
(Also, at this point I feel like you've given this mod more love than me, so if you ever feel like you want to take it over, just tell me :') )


CoreNetworkUtils may return link-local DNS server address without interface

That may be a bug in Inet6Address.getHostAddress() implementation on some Androids.
We have two options:

Return address with interface attached, and make sure that Android's DnsUpstream and CoreLibs evdns supports it.
Simply strip out such addrs.

Let's simply strip them


Hangouts will not load

Describe the bug

When trying to log in to Hangouts, I get a screen that says "Couldn't sign you in - this browser or app may not be secure."
To Reproduce

Steps to reproduce the behavior:

Add Hangouts as a service
Click on the Hangouts icon
Follow the login instructions
See error

Expected behavior

Expect to be logged into Hangouts!
Screenshots

Desktop:

OS: Windows 10
Ferdi Version 5.4.3

Server Used: https://api.getferdi.com

Thank you for your report.
This issue is already being discuddes in #264


Great project!

Oh, fine that you did not gave up after the disappointing reddit poll -- I felt a bit sad as my comments might have been not very motivating.
Your project was gone for a few days, and I did not expect to see it again, it was only some luck that I tried your link again a few days later.
May I ask which AI tools you use currently? I am using mostly the OpenAI tools, as I have a paid subscription. I am using GPT-4, GPT4 o1-mini and GPT4 o1 preview, which all behave differently. The plain GPT-4 is still best in writing good technical English, o1-mini is very fast and powerful, but sometimes a bit stupid. And o1 preview sometimes crashes for longer texts, and is a bit expensive. Only 200 requests in four weeks allowed, for $20.
I still can not understand these fools that hate AI processed content that much, even when it has best quality. I assume nearly no one will create textual content in these days without strong AI support, but they might not mention it. It would be too expensive to do all manually -- like building all our goods in tiny shops instead of in large factories with machines.
I am currently working on chapter 14 about Option types. Will try to read one of your texts in the next weeks, if your repository remains online.
Best regards,
Dr. Stefan Salewski

When I write articles, I write them in my native language and ask the AI to translate them into English. Moreover, I ask to translate into 1-2 paragraphs. Otherwise, if you give the entire text in one request to the AI, it starts adding its own text. I use a different approach to writing a book. I came up with the list of chapters myself. The chapters in the list are what I worked with myself. Then I made a list of what should be in the chapter and asked the AI to supplement the list of recipes in the chapter. Sometimes I learned something new from the additions from the AI. Then I asked for a separate request for each recipe from the chapter to generate an explanation and a code example. I myself compile and run the codes that the AI generated for each recipe and make edits to the code and description of the recipe. Sometimes I have to advise the AI which code example should be used for a recipe. I mainly use ChatGPT o1-preview.  In general, AI among people will go through the phases: denial, humility, acceptance. For example, most programmers already use AI in development environments as smart code autocomplete. And programmers who receive a salary for their work in the form of code are not embarrassed by the fact that 80% of their code was generated by AI.

the book is written for beginners in Rust and not for beginners in programming. in general, I think that rust as a programming language cannot be the first for a person who came to the field of programming. you need to start programming with python or typescript then java or kotlin and then only C/C++ or Rust

in general, in order to study rust, you first need to read a fundamental theoretical book about how to program in rust. and then my book will be useful with recipes for typical problems and tasks facing a programmer who has started writing production code in Rust. As you noticed, my book does not contain theoretical and conceptual things. a purely applied approach to programming in rust.

Hello,
I think I agree with you in most points. Learning Rust as the first language is indeed very difficult, I would not recommend to try that. I have used for some years the Nim language, which is a bit simpler than Rust and has a syntax similar to Python, and I tried to write a real beginner book for that language. That was in 2020, without AI support, I got some negative feedback about a few grammar errors, and i think that very few people actually read that book.
Your approach, starting with a text in your native language is interesting. When GPT-3.5 came out I tried it for translating German language to English and was not too happy with the results, but I assume this process works now much better. But actually we have for many computer terms no words in German, so for me writing from the beginning in (bad) English is a quite good solution.
My current strategy with GPT is typically, that I ask GPT4-mini to create a complete draft (in English) for the full chapter. Then I typically ask them to add more content that they forget, following by a lot of manual editing. For single sections I then ask the plain GPT-4 to improve the grammar (please rewrite the text in good and correct technical English). When I am done with my own edits, I might ask GPT-4 o1 preview to rewrite the full chapter again  (please rewrite the complete text and remove redundancies and verbosity). Sometimes this works good, but for longer texts it might fail.
My general feeling is, that letting GPT generate text on its own from the beginning is a good strategy, because that text is typically good, and this process is stable, while text, that I create myself, is often removed by GPT later.
Final note: You might consider removing the "for Beginner" from your book title, it might be misleading. Generally I think, we both will have a hard time find readers for our books. When there are a few hostile fools at Reddit, it makes no sense to advertise it there. Perhaps we finally have to publish at Amazon, because many people have the habit to look for books only there. I think it is not difficult to sell a book there, started by a few fake 5 star reviews. But I would not like to go that way, and I am not writing to earn money with the book. On the other hand, having a few readers would be not bad.
Best regards,
Stefan Salewski

I add tagline for book title

I do not want sell this book. Reddit it is not good place for promotion )


[$1000] Web- Chat - The background opacity becomes darker when opening each page, specifically incase of thread only.

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

Action Performed:
on Performed:

Go to any "thread."
Click on "Settings."
Click on "Welcome message."
Notice that when opening each page, the background becomes progressively darker, incase of threads, other than that the opacity remains the same throughout.

Expected Result:
The background opacity should remain the same throughout.
Actual Result:
The background opacity becomes darker when opening each page
Workaround:
Unknown
Platforms:

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

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: yes
Reproducible in production?: yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/abbe4740-ff08-475a-80b9-47dd9a49f318
https://github.com/Expensify/App/assets/93399543/d7c9ed12-b865-4838-a12a-7598968a8406
Expensify/Expensify Issue URL:
Issue reported by: @usmantariq96
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1685509854226419
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01a83e84ece19a3c9b
Upwork Job ID:<PHONE_NUMBER>044399616
Last Price Increase: 2023-06-02

reproducible, and I don't see a dupe - moving to external

Agreed this is a dupe for https://github.com/Expensify/App/issues/19073
Closing this issue.


Mention alternatives

@fonsp as discussed a list of alternatives. I've tried to mention every related Julia package and not be too positive or negative about any of them. Feel free to modify the text as you like
I've used one sentence per line because it makes the Git diff more readable, makes it easier to check whether sentences accidentally all start with the same word ("Next, we [...]. Next, they [...]. Next, the code was [...]") and easier to switch sentences around

Thanks! I also mentioned slider server alternatives, which now includes PSHTML :)

Let's also add some part of this to PSHTML?


Using the agent properly

After I finally understood what I was doing wrong on #218 I finally had sucess in colleting something from the agent but... I think I dont know how to use it properly...
I read the DOCS but, even after reading, I'm sure that I'm clueless.
Using this project as an example I inserted these lines in banco.php:
			require_once __DIR__."/vendor/autoload.php";

			define('AOP_CACHE_DIR',__DIR__.'/Cache/');
			define('PLUGINS_DIR',__DIR__.'/Plugins/');
			define('APPLICATION_NAME','testegpdpinpoint');
			define('APPLICATION_ID','testegpdpinpoint');

			require_once __DIR__. '/vendor/naver/pinpoint-php-aop/auto_pinpointed.php';

I used composer.phar to install the AOP to the project.
so... I was hoping to see some classes and queries but isnt showing something relevant.

so... what am I missing?

@dv-morais
Please fellow our plugins example:  https://github.com/pinpoint-apm/pinpoint-c-agent/blob/master/Example/PHP/Plugins/

Tried my best with the examples but I dont think I got the hang of it... I think I'm not using the hook option properly. What am I doing wrong?
<?php

///@hook:Banco::conectar
///@hook:Banco::__construct
///@hook:Banco::desconectar
namespace Plugins;
use Plugins\Candy;

 class DvmPlugin extends Candy
 {

	///@hook:Banco::conectar
	///@hook:Banco::__construct
	///@hook:Banco::desconectar

	 public function onBefore(){
         pinpoint_add_clue("stp",PHP_METHOD);
         pinpoint_add_clues(PHP_ARGS,print_r($this->args,true));
     }

	///@hook:Banco::conectar
	///@hook:Banco::__construct
	///@hook:Banco::desconectar

     public function onEnd(&$ret){
         pinpoint_add_clues(PHP_RETURN,"ture");
     }

	///@hook:Banco::conectar
	///@hook:Banco::__construct
	///@hook:Banco::desconectar

     public function onException($e){
         pinpoint_add_clue("EXP",$e->getMessage());
     }
 }

?>

@dv-morais
check the readme https://github.com/pinpoint-apm/pinpoint-php-aop/tree/dev


fix(#1578): allow github access groups to be created without a list of teams

Previously, the contents of the github block were not serialized to input JSON being sent to the Cloudflare API unless there was at least one team specified, even though the teams field is optional.
This commit changes the behavior of the github block to create include, require and exclude blocks with github organizations without specifying a list of teams.
Testing was done on my personal Cloudflare Zero Trust account. Running terraform apply twice still results in "detected" changes even though they have been applied. I think this is related to issue #1553.

@jacobbednarz I took a stab at resolving #1578, mind you this is only my second time updating a terraform provider so go easy on me 🙏

acceptance tests look good here
TF_ACC=1 go test $(go list ./...) -v -run "^TestAccCloudflareAccessGroup" -count 1 -parallel 1 -timeout 120m -parallel 1
?   	github.com/cloudflare/terraform-provider-cloudflare	[no test files]
=== RUN   TestAccCloudflareAccessGroupConfig_Basic
--- PASS: TestAccCloudflareAccessGroupConfig_Basic (44.76s)
=== RUN   TestAccCloudflareAccessGroup_Exclude
--- PASS: TestAccCloudflareAccessGroup_Exclude (19.17s)
=== RUN   TestAccCloudflareAccessGroup_Require
--- PASS: TestAccCloudflareAccessGroup_Require (18.84s)
=== RUN   TestAccCloudflareAccessGroup_FullConfig
--- PASS: TestAccCloudflareAccessGroup_FullConfig (18.87s)
=== RUN   TestAccCloudflareAccessGroupWithIDP
--- PASS: TestAccCloudflareAccessGroupWithIDP (25.27s)
=== RUN   TestAccCloudflareAccessGroup_Updated
--- PASS: TestAccCloudflareAccessGroup_Updated (28.77s)
=== RUN   TestAccCloudflareAccessGroup_CreateAfterManualDestroy
--- PASS: TestAccCloudflareAccessGroup_CreateAfterManualDestroy (23.47s)
PASS
PASS	github.com/cloudflare/terraform-provider-cloudflare/cloudflare	180.013s
?   	github.com/cloudflare/terraform-provider-cloudflare/tools/cmd/changelog-check	[no test files]
?   	github.com/cloudflare/terraform-provider-cloudflare/tools/cmd/maintainer-only-file-check	[no test files]
?   	github.com/cloudflare/terraform-provider-cloudflare/tools/cmd/tf-log-check	[no test files]
?   	github.com/cloudflare/terraform-provider-cloudflare/version	[no test files]

if you add a CHANGELOG entry (notes above from the automation), we can get this merged.

Thanks @jacobbednarz, added the changelog!


MGMT-16857: Fix error of missing networkoperator annotation

In OCP 4.15, recert with the IP replacement enabled fails due to a networkoperator annotation missing. This change makes this IP replacement a soft one, but added a TODO as we should still verify whether it should actually be a soft one or not.

/lgtm
/approve


Add org name to consortium error message

Improve troubleshooting by including org name in the error message:
"Attempted to include a member which is not in the consortium"
New message:
"Attempted to include member BadOrgName which is not in the consortium"
This will help users that have an incorrect config transaction pinpoint the reason for failure.
Signed-off-by: David Enyeart<EMAIL_ADDRESS>

@Mergifyio backport release-2.2


Fix minor issues in the new parser

Missing @Test annotation that was accidentally removed during conflict resolution.
Typo in a method name.

Please squash.


Migrate Oauth to declarative in the Admin Console

Summary
Migrate Oauth to declarative in the Admin Console
Ticket Link
MM-11941
Checklist

[x] Ran make check-style to check for style errors (required for all pull requests)
[x] Ran make test to ensure unit and component tests passed
[x] Includes text changes and localization file (.../i18n/en.json) updates

@saturninoabril @hmhealey @kaakaa I've overridden part of the #1576  PR (the Admin console for Oauth part), because we can't do that split easily in the declarative admin console. Is it ok?

Is it the admin.gitlab.EnableMarkdownDesc?  I think it's fine.  Actually, I prefer your solution to have it in a single translation.

@saturninoabril Yes, is that, and the Google and Office365 messages too. I prefer to have entire blocks of text together too, because is the same text, not unrelated chunks of text.


Request for build instructions (release?)

Could you please provide (say, in the readme of this repo), or point me to, instructions for building the plugins from this repo source?
While I want to be able to do this myself, you could take pity on me, and any other DITA-OT users who want to try these plugins, by providing a built release here on GitHub. It's just a suggestion: I understand that you will have other, higher priorities.
Or... I say this because I see prebuilt JAR files in this ("source") repo... was my half-awake first attempt last night (#3) essentially correct? Can I indeed simply drop this repo as-is into the DITA-OT plugins directory, and then run dita -install? Should that "just work"?

The plugin directories can be dropped directly in as you suggested. The JAR files are external libraries required to make the build work -- ideally those would not be in this repo at all, and instead would be pulled in with a release build, but I haven't had much time to work on that.


chore(main): release 1.0.0

:robot: I have created a release beep boop
1.0.0 (2023-05-06)
Bug Fixes

fix generate pre-commit hook (309f19f)
fix generate pre-commit hook args (c25b29a)
fix pre-commit ci (f10ac28)

Documentation

add all contributors (5fb34a2)
add andrewthetechie as a contributor for ideas, code, and 2 more (#10) (00a47b6)
cleanup extra contributors header (7f87c47)

Miscellaneous Chores

release 1.0.0 (3a3ca43)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/andrewthetechie/cookiecutter-autodocs/releases/tag/v1.0.0 :sunflower:


Implement juliaup self update

That command should simply update the binary of itself, plus the julialauncher binary next to it. Again needs to integrate with https://github.com/JuliaLang/juliaup/issues/100.

Implemented.


Zl encoder

These commits add functionality to classifiers hooked on top of a VAE. First, I added access to soft classifications, before argmax. Second, I added an option to concatenate the VAE l_encoder output to the z_encoder output so that the classifier has access to the library depth estimate.

Codecov Report

Merging #280 into master will increase coverage by 0.12%.
The diff coverage is 82.85%.

@@            Coverage Diff             @@
##           master     #280      +/-   ##
==========================================
+ Coverage   91.55%   91.67%   +0.12%
==========================================
  Files          31       31
  Lines        2416     2439      +23
==========================================
+ Hits         2212     2236      +24
+ Misses        204      203       -1

Impacted Files
Coverage Δ

scvi/inference/annotation.py
92.52% <82.85%> (+1.42%)
:arrow_up:

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 aa614bd...00b45e2. Read the comment docs.

Looks good to me, thanks for your contribution @davek44


Use basicHTML over JSDOM

Switching to a much lighter HTML/DOM implementation drastically improves memory usage.
See:

https://github.com/WebReflection/basicHTML
https://twitter.com/tpillard/status/1240127729359630336

Fixes #1
Notes:

Tests input HTML is incomplete, resulting in failing tests
If run in strict mode, (such as in 99_memory_leak), it'll fail due to basicHTML's dataset/DOMStringMap not returning a value in deleteProperty

Thanks @ziir ! 🙏

patch landed https://github.com/WebReflection/basicHTML/commit/fa398a8ce0080902c1b2149c08b8c05084183174 👋