Mac Issue - Using pyenv

Hello! Using Mac with PyCharm (Community).
I attempted to decompile and received a zero division error in decompile_print_totals.
I am using pyenv and installed uncompyle6 into version 3.7.6 (3.7.9 is not available using pyenv, but I don't believe that should matter).
Is there something I missed? I seem to have set up my path files correctly...perhaps not. Can you take a look?

Thank you very much for reporting this, I'm about to make an update that will cleanup this error making it shorter and more informative.
When the script went to begin decompilation, it found nothing to decompile. This error message happened because I didn't prepare the script for that scenario.
Based on your screenshot above, do these paths exist on your computer

~/Applications/The Sims 4/Data/Simulation/Gameplay
~/Applications/The Sims 4/Game/Bin/Python

Lets start there and we can proceed onward if they do exist

Thank for your prompt reply, this makes sense now.
The Sims 4/Game path does not exist. The only files there are Client, Shared, and Simulation.

Interesting

Does ~/Applications/The Sims 4/Contents/Python/ contain generated.zip and
Does ~/Applications/The Sims 4/Contents/Data/Simulation/Gameplay contain base.zip, core.zip and simulation.zip?

If it does then those are the folders that should be used on mac

Yes, that is exactly correct!

Could I just modify the Data and Game Folders file paths at the bottom of settings.py to
os.path.join(game_folder, 'Python') instead of game_folder, 'Game', 'Bin', 'Python' ?

This is good news for you then and bad news for me lol
Right now here's how you can correct it:

Open settings.py
Look near the very end, you should see 2 entries named gameplay_folder_data and gameplay_folder_game. What these refer to is the location of those correct folders inside the game folder which are wrong on Mac because I'm convinced EA secretly likes to make thing very difficult on purpose.
Change gameplay_folder_data to os.path.join(game_folder, 'Contents', 'Data', 'Simulation', 'Gameplay')
Change gameplay_folder_game to os.path.join(game_folder, 'Contents', 'Python')

As for me, I now have to figure out how to make for 2 different paths on each system. Let me know if this helps you.

Thank you so much June! I will let you know if I run into any trouble or not. The Sims Team really DOES like to make it particularly difficult to do literally anything-at-all. I appreciate your help. I'll get back to you in a moment.

Weird. It did not fix the problem and I am receiving the same error. sigh They must really not want us to mess with their game. I imagine I will run into the same problem again but I want to make sure it wasn't anything on my end. Ill download python 3.7 and not use pyenv and see if there was an issue with the uncompyle6.

Can you take a screenshot of the end of the settings file? It's really strange you're still having this issue, I hate I don't have a mac to test it myself.

No problem! I am more than happy to give as much detail as I can for you. Covid has confined me to my computer.

I also reset everything and still received the same message. I will attempt to debug and see what it says. At one point I got a traceback base object exception but I didn't record it before I reset everything. I don't know if that means anything to you but I'll try to recreate it. I'm not well-versed in using debug ha but if it will help, you can walk me through it and I can provide whatever you need.

Does your game folder still point to ~/Applications/The Sims 4 or did you change it to ~/Applications/The Sims 4/Contents. It should be the former and still point to ~/Applications/The Sims 4. I say this because it looks like at one point in the messages you thought of changing it.

I left the top the same otherwise it would attempt to find another Contents folder inside of the Contents folder. That's why I don't understand why it didn't work. Is there another method of file pathing I should use at the top of settings? I figured it was a requirement for Mac to use the os.path.join but I could be wrong...

os.path.join is supposed to make paths work on all operating systems. Is it the exact same error in the exact same place?

Yes it is exactly the same. I also tried 'Users', 'casbu', ... and received the same message. I thought expanduser took care of that.

Go head and replace the contents of Utility/helpers_decompile.py with the update I made, you should still get an error but it should hopefully be more informative and less messy https://github.com/junebug12851/Sims4ScriptingBPProj/blob/master/Utility/helpers_decompile.py
Can you confirm after doing so the red text goes away in place of a proper error message? In the meantime I'm still trying to figure this out, I thank you for being patient and I'm sorry this is causing so much trouble.

It's not a problem at all, I appreciate you taking the time to go through this with me. Very cool of you. Let me update and I'll be back with you shortly.

Progress. It's definitely the file path. I'm just not sure why it is incorrect.

Interesting. Changing the above settings to my User and Name created a User folder in my project folder. I didn't unpack anything inside the Python folder but the fact that it is there is weird.

It's good the red error messages were cleaned up
Ahhh, wait! Your screenshot gave me an idea.
Delete the folder you just mentioned inside your project folder and replace Users with /Users. See if that helps.

Deleted it. Ran decompiler. No luck. It did however put the --util folder back into my main projects folder.

When you say put the __util folder back into your main projects folder, you mean as normal like Sims 4 Projects/__util or Sims 4 Projects/Project Name/__util?

Yes, it's back in the original Sims 4 Projects folder that holds my actual mod project folder.

In helpers/helpers_decompile.py, the function def decompile_zips(src_dir: str, dst_dir: str) -> None: on line 175
Can you add 2 print statements like so
...
    print(src_dir)
    for root, dirs, files in os.walk(src_dir):
        for ext_filter in script_package_types:
            for filename in fnmatch.filter(files, ext_filter):
                print(filename)
                decompile_zip(root, filename, dst_dir)

and tell me what it outputs

Hey guys,
Just an fyi, the proper path to the Contents folder needs to be /Users/user/Applications/The Sims 4.app/Contents
Without the .app any of the paths you try to use won't work. So technically ~/Applications/The Sims 4.app/Contents should work as well.

I only have helpers_decompile.py under Utility. Should it be under the helper folder?? I still ran the function and it printed:
/Users/casbu/Applications/The Sims 4/Contents/Data/Simulation/Gameplay
/Users/casbu/Applications/The Sims 4/Contents/Python

Your correct Utility/helpers_decompile.py
I really don't understand whats going on. If you go to /Users/casbu/Applications/The Sims 4/Contents/Data/Simulation/Gameplay in Finder, you do see zip files? Or are they different extensions like tar.gz or something else?

Also, I believe in the finder you won't see the words .app but you should be able to see it if you browse to it via terminal. I don't have Sims 4 installed on my Macbook anymore to verify. Good luck! Hope this helps you guys.

All three are zip files. I'm at a loss as to what's wrong.

Oh my gosh! ssinakhot thank you! Let me try this.

Thank you @ssinakhot !!!

No! Thank you @junebug12851 for packaging together an interesting boilerplate to simplify the the scripting portion of Sims 4.
I love how you added in the devmode/debugging capabilities. I will be testing them out on my Intellij IDEA version. The code is pretty well commented to help anyone getting into python. I am sure people will be using and contributing to the project to help keep it up to date.
I just wish the repo name wasn't "Sims4ScriptingBPProj". Haha!

Well I could cry...it did not work.

I tried both ways:
os.path.join('Users', 'user', 'casbu', 'Applications', 'The Sims 4.app')
os.path.join('/Users', 'user', 'casbu', 'Applications', 'The Sims 4.app')

Did I mess this up? Should I include Contents and remove the 'Contents' part at the bottom of settings.py?

@ssinakhot Thank you for the great feedback!!! Also I agree about the project name, I should have spent more time on it but it's named what it is now lol.

Just slight typo there buddy:
Try this
os.path.join('/Users', 'casbu', 'Applications', 'The Sims 4.app')
or
os.path.join('~','casbu', 'Applications', 'The Sims 4.app')
See if one of those works.

@junebug12851  You can rename repositories. But you'd need to update all your posts and references you had before.
I forked your project and renamed it to sims4_mod_boilerplate so it's nicely named in my local drive.

Ok I adjusted accordingly and received this message:

I'm looking into this still but this means it was ready to begin decompiling and has a pyc file ready to decompile, however when it went to execute uncompyle6 it wasn't able to find it at all. This means we're making progress and now we're at a different issue. Congrats on solving the first issue!
So to fix the second issue, go to your Python folder and in Scripts look for a file called uncompyle6, do you see it?

Hm there is a problem. Mac does not create a Scripts folder. It's just in there when I pip'd it in.

When I used debug it shows this. Could this be why?

Not even sure if the above matters as long as I can access the file. But I am able to locate the file, yes.

This would be the reason why, I suspected it was different on mac as well.

Macintosh HD/Users/casbu/.pyenv/versions/3.7.6/bin/uncompyle6

So try this
In Utility/helpers_package.py, replace the imports at the top with this:
import os
from subprocess import run, PIPE, call, DEVNULL
from Utility.helpers_path import get_sys_path, get_sys_scripts_folder, get_full_filepath, get_sys_folder

and somehwere around line 41 or near the bottom replace these lines in exec_package with this
    cmd = os.path.join(get_sys_folder(), 'bin', package)
    result = run(cmd + " " + args, capture_output=True, text=True)
    return (not str(result.stderr)) and (result.returncode == 0)

See if that works. We're close to the end!

Did you make those changes in helpers_package.py or helpers_path.py?

Whoops! Okay I fixed it. Sorry about that.

It's not a problem, did you add
import os
from subprocess import run, PIPE, call, DEVNULL
from Utility.helpers_path import get_sys_path, get_sys_scripts_folder, get_full_filepath, get_sys_folder

at the top of the same file helpers_package.py?

Gosh I am out of it. I missed the get_sys_folder. Here are new results.

It's no problem and this is really excellent! I feel we're almost there.
In helpers_package.py in def exec_package change this from:
cmd = os.path.join(get_sys_folder(), 'bin', package)

to
cmd = os.path.join(get_sys_folder(), package)

I think this may be it!

Eek! I hope so.

But the file does exist doesn't it?
Can you visit /Users/casbu/.pyenv/versions/3.7.6/bin/uncompyle6? That should be the direct path to it.

It does! I don't understand! Does this look right?

Hmm, can you add 2 print statements after the cmd like so:
...
    cmd = os.path.join(get_sys_folder(), 'bin', package)
    print(cmd)
    print(cmd + " " + args)
...

and tell me what it says. I'm really running out of ideas at this point

I tried the command with 'bin' included and one without since you had me change it previously. Both resulted in the same error:
get_sys_folder(), 'bin', package)
get_sys_folder(), package)

Honestly, at this point that's okay. You have been working on this with me for the past 5 hours and I don't know how I can ever thank you enough for trying to resolve this. Do you have a patreon or anything?

Your issue might be because of how you are using subprocess.run() and how MacOS parses commands.
You can try to place the cmd + args inside a list and see if that helps.
so
subprocess.run([path, arg1, arg2, arg3]) rather than trying to concat a string together.

I hope we can resolve it in the future and I'm sorry we couldn't figure it out and that it took so long. As for patreon, I don't but I've been meaning to set one up, currently I take donations through PayPal<EMAIL_ADDRESS>Thank you for sticking with me!

Maybe it just won't work with pyenv and I'll have to install the python version directly in my system or something. Which is unfortunate but I don't mind the hassle if I can actually look at Sims python scripts to get some semblance of an idea of what I can do with it. Have a good evening...or morning/afternoon! You have been awesome. If you think of anything later on I've made sure to watch this repository. Go take a break ;)

@ssinakhot I really need to make a lot of upgrades in general on the code, especially to handle Mac now that I know more about Python and Sims 4 on Mac. If casbu tries it I hope it works. When all this is over I'm going to make some large-scale refactoring to the codebase.
@casbu Pyenv shouldn't really matter because in the end it's a working python installation in a folder of your computer. I may have to take that break lol. Try what ssinakhot said which is to replace
this
result = run(cmd + " " + args, capture_output=True, text=True)

with this
result = run([cmd, args], capture_output=True, text=True)

Good luck, I'm going to take a short break

@ssinakhot !!!!! That soothing wall of text that follows upon execution is a beautiful thing. I don't even know what to say. I really appreciate you. Wow.
@junebug12851 fyi, I did not include 'bin' in the exec_package since it was creating a bin/bin/ situation. Just so you know! You both are awesome!

Wait, you got it working! That's really awesome! What did you do to get it working?

I kept the modifications we made to helpers_package and settings,  but removed the 'bin' under exec_package cmd, then did exactly what @ssinakhot  said about using a list instead of concat for sub_processes and it worked like a charm. Thank you both for all of your help tonight. Have a good one!

Darn. So it ran. I assumed it was working. It created all of the folders inside of base.zip, core.zip, etc so the process was able to locate the files. Unfortunately the conversion of all files failed. Can you think of a reason as to why?

Can you copy and paste in here just those last 2 lines, what I'm seeing is this
/Users/casbu/.pyenv/versions/3/7/6/bin/uncompyle6
/Users/casbu/.pyenv/versions/3/7/6/bin/uncompyle6 -o "/Users/casbu/Documents/Sims 4 Projects/__util/Python/generated/protocolbu....

 If you type in uncompyle6 --help
you should see a line that's says this
uncompyle6 [OPTIONS]... [ FILE | DIR]...

Is it different on a mac?

It should be...but this is what I got.

That would be related to pyenv, could you run /Users/casbu/.pyenv/versions/3.7.6/bin/uncompyle6 --help?

let me try a few different ways, one moment.

Gotcha. Sorry. I am in the help menu now

Should I try decompyle3? I was looking at that in the uncompyle6 doc that it might work better.

@ssinakhot  and I are discussing using multiple compilers in a sequence for each file so that if one fails the other may succeed https://github.com/junebug12851/Sims4ScriptingBPProj/issues/2
However until then it should still work regardless, we have a different issue here where it's being told correctly what to do but it's not doing anything and returning an error.
Wait, lets see that error, give me a quick moment.

In helpers_package.py near the end, find def exec_package(package: str, args: str) -> bool: and add a print statement like so
...
    result = run(cmd + " " + args, capture_output=True, text=True)
    print(result.stderr)
    return (not str(result.stderr)) and (result.returncode == 0)

hopefully it'll give us an indication as to whats going on

Yea I was afraid to replace the work we did so it's just taking a moment to surf through all the files. Should have results in a minute or so.

Noticing it is feeding back No input files given to decompile

So uh, Just looking at the output I'm wondering why I see the x infront of the path for uncompyle6? Is that intentional?

Hm... I thought it was something you had included in the code to separate files? Guess not ha. I am not sure what that means.

The x is part of the progress bar. The progress bar is being broken up intil multiple lines because we have 3 print statement happening in that one function.

It's okay, I'm pretty sure this is related to the arguments.
[cmd, args] => ["uncompyle6", "-o input1 input2"], this won't work for MacOS.
It needs to be ["uncompyle6", "-o", "input1", "input2"] for it to work.
I am working right now I might be able to spend a couple minutes fixing the code later tonight or you can do some refactor for that input type.

I'm working on a solution that involves that now. Give me a quick moment @casbu

Take your time, no rush.

The thing is I already tried this on Windows and I couldn't get it to work because of errors which is why I instead built a string but it may work for you. It requires making lots of changes though.
Make exec_package header look like this
def exec_package(package: str, *args) -> bool:

Then, inside of the function, make run look like this
result = run([cmd] + list(args), capture_output=True, text=True)

Then inside of helpers_decompile.py  you should see near line 96 success = exec_package("uncompyle6",..., make it look like this:
            # Decompile it to destination
            success = exec_package("uncompyle6",
                                   "-o",
                                   '"' + dest_file_path + '"',
                                   '"' + src_file_path + '"')

This may or may not work for you, it gives errors on my end saying the file doesn't exist.

Your exec_package.py should look like this
def exec_package(package: str, *args) -> bool:
    """
    Executes the cli version of an installed python package

    :param package: Package name to execute
    :param args: Arguments to provide to the package
    :return: Return code for failure or success
    """

    cmd = get_full_filepath(get_sys_folder(), package)
    result = run([cmd] + list(args), capture_output=True, text=True)
    print(result.stderr)
    return (not str(result.stderr)) and (result.returncode == 0)

Woops let me remove the print on 52

Ah wait, it should look like this
def exec_package(package: str, *args) -> bool:
    """
    Executes the cli version of an installed python package

    :param package: Package name to execute
    :param args: Arguments to provide to the package
    :return: Return code for failure or success
    """

    cmd = os.path.join(get_sys_folder(), package)
    result = run([cmd] + list(args), capture_output=True, text=True)
    print(result.stderr)
    return (not str(result.stderr)) and (result.returncode == 0)

An additional change I forgot because you're on a mac

Ok that didn't work but I put the os.path.join back. and now its stating these results:

That's the error I get which is why I didn't initially do what @ssinakhot suggested, perhaps I'm implementing it wrong.

Ooookay I'm getting a parse error, assertion error,  and its quite long.

Wait....it just worked??

Ahh, stop it and remove the print statements

Oh my gosh I think it's working!! Should there be a mini progress bar running?

There should be, that's what the dots and x's are for. I reccomend to stop it and remove the print statements so it looks like this

Looks like it's working!!!!!

Lifesaver!!!! <3 Thank you so much!

Your welcome!! Enjoy your decompiled files!

I shall!


Do not clear documents on store.close()

We are using ojai-testing for unit testing our application. Additionally we want to use ojai-testing during development on the developer notebooks. With ojai-testing we don't need to connect to a cluster.
In our webservice applications, we are creating and closing the Ojai Store on each http request. That means that a document that was inserted first, can not be read by our api (using ojai-testing), because the store will be cleared after each http call.
Is there any way to not clear the store after calling close?
Maybe there would be a way to pass an option (like clearStoreOnClosing) while registering the InMemoryDriver (which passes this option to InMemoryConnection and this one to the InMemoryStore).
What do you think about this?

I cannot change the function signature since it has to comply with OJAI. I will look at alternatives and put something there soon.

@raman-nbg what I can do is the stores open (even when you say close) and the clean everything on connection.close()

@anicolaspp would there be any way to set a kind of a switch for this behaviour? We could pass this as option to DriverManager.getConnection("ojai:anicolaspp:mem", option).

Usage would look like this:
import org.ojai.json.Json;
import org.ojai.store.DriverManager;

Document options = Json.newDocument();
options.set("ojai.in-memory.store.preserve-data-on-close", true);
Connection connection = DriverManager.getConnection("ojai:anicolaspp:mem", options);

@raman-nbg that looks good to me. PR the changes and I will review them

see https://github.com/anicolaspp/ojai-testing/pull/6
If something is missing or should be changed, let me know

@anicolaspp did you already have time to have a look on the PR?

@raman-nbg I haven't. I will do it soon.

This has been fixed on version 1.0.12.


Pulse field visibility

Right now, Pulse serves two purposes:

To represent a resolved pulse event in a Graph.  The public functions return resolved values.
To represent Pulse defaults in a Graph.

This dual use creates a scenario we've avoided everywhere else: an unresolved Pulse instance can be created, potentially leading to panic! if one of the public functions is called on a field currently None

Closed via #109


Fixed #22 Get methods only return the first 10 objects

Updated bananaj Get methods to return the first 100 Mailchimp objects rather than just 10. Added method overrides with count and offset parameters so that the full list can be iterated.

I updated the file manager methods to return the uploaded or newly created objects rather than void. Therefore you no longer have to query for folders or files after you create or upload them.
This was added to the original pull request.

I also added error handling to the HTTP transport. You will no longer get a delayed exceptions, such as NullPointerException from the various object constructors, after a 400 series or 500 series transport error. You will now get a TransportException thrown directly from the HTTP transport methods identifying the precise point of failure.

Thanks a  lot for all your additions. I really appreciate it !


Buttons | Change 'Cancel' label to 'Back' in the UI |1|

https://trello.com/c/kDFUePTk/707-buttons-change-cancel-label-to-back-in-the-ui-1
Change the text from Cancel to Back. This should lessen the confusion that a user might be cancelling the proposal as opposed to cancelling out of the page.

 Buttons | Change 'Cancel' label to 'Back' in the UI |1|


fix(orchestrator): pass businessKey for assessments

backport of https://github.com/janus-idp/backstage-plugins/pull/2558

@mareklibra
to fix prettier run:
cd workspaces/orchestrator
yarn prettier --write .
then commit the changed files

The prettier is passing when executed in the plugin's folder but not on the workspace level.
We have discrepancy in the dependencies for prettier.
I will try to fix that in a separate PR.

meanwhile can you fix it so we can get this merged?
I need to backport https://github.com/janus-idp/backstage-plugins/pull/2573 and it would be difficult without this PR merged


Fixed a warning by surrounding marker creation with runloop magic.

Surrounded marker creation and setting with runloop magic to prevent a warning like this:
DEPRECATION: A property of Ember.SomeView:emberXXX was modified inside the didInsertElement hook. You should never change properties on components, services or models during didInsertElement because it causes significant performance degradation.

Awesome work, thanks. That is a really annoying message :-)

Release 0.2.1


Update related.md with new helm plugin

Add helm-github plugin to list in documentation

Hey @stevemcquaid! Once you accept the CLA we'd be happy to pull this in.

Thanks @bacongobbler! Still waiting on the verification email for the CLA. I'm 99% sure the first email bounced and the website doesn't have an option to resend.
I have ticket # 48185 open with linux foundation if anyone here has access to that system.

@k8s-ci-robot CLA should now be signed.

👍


CNCF SIG-Runtime Presentation/Discussion(?)

Hello Sysbox team,
I'm one of the co-chairs of the CNCF SIG-Runtime, I'm reaching out and I think it would be great for you to present/discuss the project at one of our meetings. For example, discuss things such as architecture overview and use cases.
Let me know if this something you'd be interested in doing. If yes, please feel free to add it to our agenda or reach out to me (raravena80 at gmail.com)
Thanks!

Hi @raravena80 , thanks for reaching out, we would be very happy to present at the CNCF SIG runtime meeting and would love to get your feedback.
I've added a meeting date to the agenda (Thursday 02/04/2021).
Thanks again!

Hi @raravena80 , thanks for reaching out, we would be very happy to present at the CNCF SIG runtime meeting and would love to get your feedback.
I've added a meeting date to the agenda (Thursday 02/04/2021).
Thanks again!

@ctalledo awesome! Looking forward!

@ctalledo awesome! Looking forward!

Had a meeting with the CNCF to present on Sysbox on 02/04/2021. Thanks @raravena80 for the opportunity, hope you found it interesting!
Closing this issue!


Can now get all items instead of only backlog and current

The current for_product method only calls for the default amount of items which is only "backlog" and "in-progress" status. There is a now one that will search for all statuses.

@dalexj Looks like the tests are broken on CI. Can you please fix them?

@fluxusfrequency I can run all the tests locally and they work. I also cannot access the CI. Does it have any API keys to get to the test sprintly project?


Add loading state to workspace component

In this PR, I created a new component called WorkspaceLoadingIndicator. This component will be used in two scenarios: when realm info is being loaded and when a new realm is being initialized after user registration.
https://github.com/user-attachments/assets/60cdc83c-926b-465d-9c31-be0400d00f70
*) The failing test seems unrelated to this PR, and I am unable to reproduce it locally. However, I will continue investigating.

could you merge the main branch and also confirm that clicking on the create workspace button also shows the loading state correctly?


1.0.17 crashing when trying to load project

See attached crash-log, everytime I try to load my project it crashes and creates no recovery files.
Log 2024-7-29--14-44-08.txt

Which game? Try deleting the AppData/Local/Smithbox folder, that will reset the CFG variables. I'm guessing you might have enabled "Use project meta", and since I changed the ColorEdit stuff, those old files will be invalid, causing your error.

Using Elden Ring, deleting that folder fixed the issue indeed.


Add changes to fix issues running the Spacewalk client in Kubernetes

Removes the backoff crate. Assuming that the retry() function introduces some side effects, we manually implement the retry logic now. To get the exponential duration from an iterator, we use a new crate exponential-backoff. This crate is only used for convenience to get the duration, it does not contain any logic for actually retrying.
Retrying  for Subxt RPC error due to closed connection
Sometimes, the runner encounters the following error:
[2024-05-07T13:56:14Z INFO  runner::runner] Error fetching executable: SubxtError: Rpc error: RPC error: The background task been terminated because: Networking or low-level protocol error: WebSocket connection error: connection closed; restart required. Retrying...
[2024-05-07T13:56:15Z INFO  runner::runner] Error fetching executable: SubxtError: Rpc error: RPC error: The background task been terminated because: Networking or low-level protocol error: WebSocket connection error: connection closed; restart required. Retrying...

I found this PR which adds a new experimental implementation of an RPC client that automatically reconnects. This implementation is only available in subxt v0.35 or later. I tried bumping the subxt dependencies we use in Spacewalk to that version but I encountered conflicts because our Polkadot dependencies are too outdated.
-> I created https://github.com/pendulum-chain/spacewalk/issues/521 as a follow-up and we'll ignore this issue for now.
Related to https://github.com/pendulum-chain/tasks/issues/207.

@pendulum-chain/devs this is now ready for review

Regarding the error due to close connection, could we retry a new one after a failure here by simply creating a new client instance with Ok(OnlineClient::from_url(url).await?)?

Good point. I looked into this again and realized that this logic was kind of in place before. In this loop, the runner is restarted if try_get_release() returns an error. The problem was that the changes I made were missing the maximum retry timeout that exists in the backoff crate (max_elapsed_time). Instead of defining a maximum duration for which the logic is retried, we can only specify the number of retries, but I now derive that here so the result is similar.  With this, the retry_with_log() functions will now return an error in time that is either caught inside the loop I linked to previously, or if it happens elsewhere will make the runner stop entirely. Once stopped, they can be automatically restarted in the infrastructure.

Once stopped, they can be automatically restarted in the infrastructure.

Okay understood, I didn't consider this behavior, makes sense!

Over the weekend, the runner client again encountered the error.
[2024-05-13T08:43:43Z INFO  runner::runner] Error reading chain storage for release: SubxtError: Rpc error: RPC error: The background task been terminated because: Networking or low-level protocol error: WebSocket connection error: connection closed; restart required. Retrying...

Because I slightly changed the phrasing in the log messages, I was able to pin it down to this line which means that the runner was only 'hanging' in this loop statement. Now I noticed that the call to maybe_restart_client doesn't do anything in this case because the child process (the actual vault client binary) is still running and working fine. I tested it and it's still able to process issue and redeem requests, and the RPC connection of the vault client is also working. This is interesting but my assumption is that the RPC connection of client is fine because of its periodic restart every 3 hours, thus the connection is always kind of fresh, whereas the runner never restarts or refreshes its RPC connection. That's why I added some logic to just try and create a new RPC client in the runner.

Something was off with the iterator returned by the exponential-backoff crate and it kept on returning values. I removed that crate completely and now we do everything manually. I also added some small tests for the retry_with_log_... functions so that we can now be sure that they don't retry more often than they should.

@ebma you can squash and merge this now. I reverted to older version, as 2024-04-18 has some problems.
Pendulum's CI is using 2024-04-18, but it's using the stable spacewalk when it was still 2024-02-09; and there were no problems so far.


30ignition: add wipefs to the initramfs

Needed for https://github.com/coreos/ignition/pull/991.

@jlebon Do I understand correctly that landing this will not automatically pull it into kola CI runs for https://github.com/coreos/ignition/pull/991?

@jlebon Do I understand correctly that landing this will not automatically pull it into kola CI runs for coreos/ignition#991?

See https://github.com/coreos/ignition/pull/991#issuecomment-638263550


Check for previous/existing GitHub issues/module proposals

[X] I have checked for previous/existing GitHub issues/module proposals.

Check this module doesn't already exist in the module indexes

[X] I have checked for that this module doesn't already exist in the module indexes; or I'm proposing the module to be migrated from CARML/TFVM.

Bicep or Terraform?
Bicep
Module Classification?
Pattern Module
Module Name
avm/ptn/aca-lza/hosting-environment
Module Details
This Azure Container Apps pattern module represents an Azure Container Apps deployment aligned with the cloud adoption framework implementing industry proven practices, such as those presented in Azure landing zones guidance in the Cloud Adoption Framework, owned and operated by a workload team. This avm pattern module provides a production ready reference implementation of a containerized apps hosting environment with Azure Container Apps.

As part of this pattern module the following services will be deployed:

A resource group (Spoke) to deploy all resources
A VNet with 4 subnets hosting the services
An internal Azure container apps environment
An Azure key vault exposed through a private endpoint
An Azure Container Registry reachable through a private endpoint
Azure Application Gateway or Azure Front Door to expose applications hosted at Azure Container Apps
A Virtual Machine serving as a jump box for the locked down environment

Do you want to be the owner of this module?
Yes
Module Owner's GitHub Username (handle)
kpantos
(Optional) Secondary Module Owner's GitHub Username (handle)
No response

This module will take a dependency on https://github.com/Azure/Azure-Verified-Modules/issues/604.

Hi @kpantos,
Thanks for requesting/proposing to be an AVM module owner!
We just want to confirm you agree to the below pages that define what module ownership means:

Team Definitions & RACI
Shared Specification (Bicep & Terraform)
Module Support

Any questions or clarifications needed, let us know!
If you agree, please just reply to this issue with the exact sentence below (as this helps with our automation 👍):
"I CONFIRM I WISH TO OWN THIS AVM MODULE AND UNDERSTAND THE REQUIREMENTS AND DEFINITION OF A MODULE OWNER"
Thanks,
The AVM Core Team
#RR

I CONFIRM I WISH TO OWN THIS AVM MODULE AND UNDERSTAND THE REQUIREMENTS AND DEFINITION OF A MODULE OWNER

Hi @kpantos,
Thanks for confirming that you wish to own this AVM module and understand the related requirements and responsibilities!
Before starting development, please ensure ALL the following requirements are met.
Please use the following values explicitly as provided in the module index page:

For your module:

ModuleName - for naming your module
TelemetryIdPrefix - for your module's telemetry

For your module's repository:

Repo name and folder path are defined in RepoURL
Create GitHub teams for module owners and contributors and grant them permissions as outlined here.
Grant permissions for the AVM core team and PG teams on your GitHub repo as described here.

Check if this module exists in the other IaC language. If so, collaborate with the other owner for consistency. 👍
You can now start the development of this module! ✅ Happy coding! 🎉
Please respond to this comment and request a review from the AVM core team once your module is ready to be published! Please include a link pointing to your PR, once available. 🙏
Any further questions or clarifications needed, let us know!
Thanks,
The AVM Core Team

@kpantos, thanks again for proposing this module! Please don't forget to add the discussed details to the description, including the architectural diagram, and bill of materials. Thanks!

[x] Module published.
[x] GitHub teams are available and assigned to their parents.
[x] CODEOWNERS file updated.

Thank you for your work @kpantos! I'm closing this issue now.


handle when can't package files

handle when can't package files, need to fall back to copy files one by one.
right now it interrupts the whole copy process.
or allow user to check off  package files for transfer

fixed in v1.3


abnormal muscle gating pore sodium currents

Valerie Hinard's Comments:
Dear MGI experts,
Using a lot the Mammalian Phenotype to annotate proteins into the nextprot database, I would like to suggest a new phenotype in the domain of the muscle electrical activity: "the abnormal muscle gating pore sodium currents". Would you agree to add it?
This phenotype appears in mutated organism and is responsible for hypokalaemic periodic paralysis in humans.
Those mutations change the biophysical properties of the voltage-gated sodium channel Nav1.4 and create an abnormal large sodium current called "gating pore current".
Waiting for your answer,
Thank you
Valerie Hinard
Ref:MSG063028

some references:
http://www.tandfonline.com/doi/full/10.1080/19336950.2015.1031937
http://jgp.rupress.org/content/145/2/93.full
http://www.sciencedirect.com/science/article/pii/S0896627305005179
Definition from the last article:
" non-sodium-selective cation current that is unaffected by the pore blocker tetrodotoxin (TTX) and therefore represents ion movement through a permeation pathway in domain II rather than through the central pore"
see also http://www.ncbi.nlm.nih.gov/pubmed/25382261
From what I can tell these currents are always abnormal.
New term:
muscle gating pore current MP:0020381


Document DCO

Document the requirement to use DCOs for projects of stage 2 and higher, what it means, and how developers can do the sign-off.
Documentation should be part of the project-handbook in the TC repo.

Info on how to require sign-offs in web-based commits: https://github.blog/changelog/2022-06-08-admins-can-require-sign-off-on-web-based-commits/

DCO Bot: https://github.com/apps/dco


Adding Drag to fill Cells Functionality in Game of Life

@llaske in the game of life activity, it becomes very tedious to click at individual cells and enable them. What I propose is adding a click-and-drag functionality (much like using a paintbrush in paint) to fill the cells. This would also enable adding cells while generations are moving fast as adding a single cell just vanishes very quickly.
I will achieve this by adding mouse-down and mouse-move event listeners.
I have actually tried implementing it and it works pretty well.
If you like this feature can you assign it to me? Thanks!

It's a good idea. BTW it should support both mouse and touch event.
There is nothing like assigned issue. Everyone is free to contribute. See here for more.

i've made a PR, please review it @llaske

@llaske since no one is working on this issue can i?

@VedantSharma11 yes, sure.

Fine @llaske ill work on the fix then

Fixed in https://github.com/llaske/sugarizer/pull/1592


Apply checkstyle to test modules + fix checkstyle issues

Description
Require checkstyle also on all test modules
Type of Change
Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] New and existing unit/integration tests pass locally with my changes

@Frawless @im-konge
Quaestion is :)
What is out default indent settings
I have in IDEA
4
4
8
Lukas has I think
4
4
4
not sure what is better
If we decide I can in this PR also change indentation in rest of the files

As I mentioned before, 4,4,4 is natural for me, the 8 spaces for the continuous lines is a bit weird for me. And I think that it should be same across everything (I mean the 4 spaces).

As I mentioned before, 4,4,4 is natural for me, the 8 spaces for the continuous lines is a bit weird for me. And I think that it should be same across everything (I mean the 4 spaces).

ok then I can require it and change it in my IDEA


Full revocation status list is actually required for revocable credential issuance?

Currently, the library requires us to pass a full revocation status list object when issuing revocable credentials. From my understanding, this is mostly needed to determine whether the revocation status type is issuance_by_default or issuance_on_demand (as seen here), and, in the latter case to determine the new accumulator value (as seen here).
However, as issuance_type has been removed from the spec and now only issuance by default is allowed, I think it would make sense remove this possibility from this library, which will result in a simplified code that will not require the consumer application to provide the revocation status list object every time a credential is issued.
Am I missing something?

The full revocation status list is there to support Verifiable Data Registry (VDR) methods that require the full state of the RevReg be tracked, vs. Indy’s deltas. I don’t think it has anything to do with the issuance type AFAIK. In the full state usage, the flag could save the first full state entry.
On your second statement, I don’t think it is quite right.  The spec. is a ledger-agnostic version of the existing functionality, and since issuance_type is supported in the existing implementation, it should continue to be. It is not needed by “full-state” implementations (as mentioned above), but is for delta-state methods. In the spec, issuance_type of issuance_on_demand is strongly discouraged (since it is silly…), but not removed.

Thanks @swcurran for the answer!
I started my reasoning considering issuance_by_default as the only possible issuance_type because this field is not mentioned in the current spec. issuanceType is in REVOC_REG_DEFs data model (for Indy ledgers) but in AnonCreds spec it is not included in the data model (see section 7.3.1).
There are, however, a few references to this concept:

In Collecting Data for Generating the Non-Revocation Proof
In AnonCreds Issuer Setup With Revocation where it mentions ISSUANCE_ON_DEMAND but has a broken link

Should it be included and marked as "deprecated" or "kept for legacy reasons but please please please don't use it"?

now only issuance by default is allowed

This is not necessarily true. The data model in this spec always contains the full state (so for every index whether it is revoked / unrevoked ). Therefore the issuance_by_default or issuance_on_demand doesn't matter anymore. You could have started with either of them, but the accumulator that you will derive from the full state will be the same as we have all the indexes with their state (instead of how it used to be where you got "this is the starting point (all revoked or all unrevoked) and this is how it changed over time)"

However, as issuance_type has been removed from the spec and now only issuance by default is allowed, I think it would make sense remove this possibility from this library, which will result in a simplified code that will not require the consumer application to provide the revocation status list object every time a credential is issued.

I think this makes sense. From what I remember there is a separate method to update the status list. So if you want to use issuance_on_demand, you can call the issue method first, and then separately call the update_status_list method right?
This way issuance is separate from managing which credentials are revoked

Should it be included and marked as "deprecated" or "kept for legacy reasons but please please please don't use it"?

So as mentioned above. To the spec, it doesn't matter. You always have the full state in the data model, in which case the issuance type doesn't change the end result


Issue: Notifications "lock up" NeoVim for 15 seconds or more

I share my LazyVim (Nvim v0.9.5) config between 3 computers - MacOS Sonoma 14.3.1, Ubuntu Workstation 22.04, and 2 Ubuntu 22.04.3 LTS workstations. On all three, when I have notify enabled, notifications pop up and stay on top and prevent me from doing anything else for at least 15 seconds, and in at least one case for several minutes. Is it possible I have a misconfiguration?

Same here. Still could not find a solution except disabling the plugin.


SingularException during interpolation

Certain input birth rate landscapes result in SingularException. Changing the order for the interpolation fixes the issue, for example via: interp = PolyharmonicInterpolation.PolyharmonicInterpolator(X,Y,3) in ploidyMovement.jl. May want to add this as user parameter with a default setting.

The singular exception was highlighting issues with the interpolator and we will leave as is (with default value set to 2) and not accessible to the user. For now, we will add an extra "more problem-specific" error message.


X not started

I have RTX2080 (connected to monitor)and Intel UHD 630 (primary, connected to monitor). Host is on AlmaLinux8.4 (clone RHEL8), guest OS is Ubuntu 20.04
Use NVIDIA-GRID-Linux-KVM-460.32.04-460.32.03-461.33.zip
Install NVIDIA-Linux-x86_64-460.32.04-vgpu-kvm.run
After installation have next on host:
[user@localhost work]$ mdevctl types 0000:01:00.0   nvidia-256     Available instances: 0     Device API: vfio-pci     Name: GRID RTX6000-1Q     Description: num_heads=4, frl_config=60, framebuffer=1024M, max_resolution=5120x2880, max_instance=24   nvidia-257     Available instances: 0     Device API: vfio-pci     Name: GRID RTX6000-2Q     Description: num_heads=4, frl_config=60, framebuffer=2048M, max_resolution=7680x4320, max_instance=12   nvidia-258     Available instances: 0     Device API: vfio-pci     Name: GRID RTX6000-3Q     Description: num_heads=4, frl_config=60, framebuffer=3072M, max_resolution=7680x4320, max_instance=8   nvidia-259     Available instances: 0     Device API: vfio-pci     Name: GRID RTX6000-4Q     Description: num_heads=4, frl_config=60, framebuffer=4096M, max_resolution=7680x4320, max_instance=6   nvidia-260     Available instances: 3     Device API: vfio-pci     Name: GRID RTX6000-6Q     Description: num_heads=4, frl_config=60, framebuffer=6144M, max_resolution=7680x4320, max_instance=4
First, why RTX6000 with TU102GL, not TU104GL? My card have gpu TU104.
Next, in KVM create new VM with Ububtu 20.04 and add new PCI device with XML
Install NVIDIA-Linux-x86_64-460.32.03-grid.run
After reboot have no graphics, black screen.
nvidia-smi
`+-----------------------------------------------------------------------------+
| NVIDIA-SMI 460.32.03    Driver Version: 460.32.03    CUDA Version: 11.2     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  GRID RTX6000-6Q     On   | 00000000:04:00.0 Off |                  N/A |
| N/A   N/A    P8    N/A /  N/A |    432MiB /  6144MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|  No running processes found                                                 |
+-----------------------------------------------------------------------------+lsmod | grep nvidianvidia_drm             57344  0
nvidia_modeset       1228800  1 nvidia_drm
nvidia              34050048  1 nvidia_modeset
drm_kms_helper        217088  4 qxl,nvidia_drm
drm                   552960  6 drm_kms_helper,qxl,drm_ttm_helper,nvidia_drm,ttmXorg.0.log[     3.818] (--) Log file renamed from "/var/log/Xorg.pid-895.log" to "/var/log/Xorg.0.log"
[     3.818]
X.Org X Server 1.20.9
X Protocol Version 11, Revision 0
[     3.836] Build Operating System: Linux 4.15.0-130-generic x86_64 Ubuntu
[     3.836] Current Operating System: Linux user-KVM 5.8.0-59-generic #66~20.04.1-Ubuntu SMP Thu Jun 17 11:14:10 UTC 2021 x86_64
[     3.836] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic root=UUID=7cbeea00-f21b-4a76-ba88-0649e9195180 ro quiet splash vt.handoff=7
[     3.836] Build Date: 17 January 2021  09:13:31AM
[     3.837] xorg-server 2:1.20.9-2ubuntu1.2~20.04.1 (For technical support please see http://www.ubuntu.com/support)
[     3.837] Current version of pixman: 0.38.4
[     3.837] 	Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[     3.837] Markers: (--) probed, () from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[     3.839] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jul  7 16:54:24 2021
[     3.839] (==) Using config file: "/etc/X11/xorg.conf"
[     3.839] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[     3.839] (==) ServerLayout "Layout0"
[     3.839] () |-->Screen "Screen0" (0)
[     3.840] () |   |-->Monitor "Monitor0"
[     3.842] () |   |-->Device "Device0"
[     3.842] () |-->Input Device "Keyboard0"
[     3.842] () |-->Input Device "Mouse0"
[     3.842] (==) Automatically adding devices
[     3.842] (==) Automatically enabling devices
[     3.842] (==) Automatically adding GPU devices
[     3.843] (==) Automatically binding GPU devices
[     3.847] (==) Max clients allowed: 256, resource mask: 0x1fffff
[     3.847] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[     3.847] 	Entry deleted from font path.
[     3.847] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[     3.847] 	Entry deleted from font path.
[     3.847] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[     3.847] 	Entry deleted from font path.
[     3.847] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[     3.847] 	Entry deleted from font path.
[     3.847] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[     3.848] 	Entry deleted from font path.
[     3.848] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/Type1,
built-ins
[     3.848] (==) ModulePath set to "/usr/lib/xorg/modules"
[     3.848] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[     3.848] (WW) Disabling Keyboard0
[     3.848] (WW) Disabling Mouse0
[     3.848] (II) Loader magic: 0x556d1102f020
[     3.848] (II) Module ABI versions:
[     3.856] 	X.Org ANSI C Emulation: 0.4
[     3.860] 	X.Org Video Driver: 24.1
[     3.860] 	X.Org XInput driver : 24.1
[     3.860] 	X.Org Server Extension : 10.0
[     3.861] (++) using VT number 1
[     3.863] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c1
[     3.864] (II) xfree86: Adding drm device (/dev/dri/card0)
[     3.868] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 12 paused 0
[     3.877] (II) xfree86: Adding drm device (/dev/dri/card1)
[     3.878] (II) systemd-logind: got fd for /dev/dri/card1 226:1 fd 13 paused 0
[     3.909] (--) PCI:*(0@0:1:0) 1b36:0100:1af4:1100 rev 4, Mem @ 0xf0000000/67108864, 0xf4000000/67108864, 0xfcc14000/8192, I/O @ 0x0000c040/32, BIOS @ 0x????????/131072
[     3.909] (--) PCI: (4@0:0:0) 10de:1e30:10de:1329 rev 161, Mem @ 0xfa000000/16777216, 0xd0000000/268435456, 0xf8000000/33554432
[     3.910] (II) LoadModule: "glx"
[     3.910] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[     3.910] (II) Module glx: vendor="X.Org Foundation"
[     3.910] 	compiled for 1.20.9, module version = 1.0.0
[     3.911] 	ABI class: X.Org Server Extension, version 10.0
[     3.911] (II) LoadModule: "nvidia"
[     3.911] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[     3.911] (II) Module nvidia: vendor="NVIDIA Corporation"
[     3.911] 	compiled for <IP_ADDRESS>1, module version = 1.0.0
[     3.911] 	Module class: X.Org Video Driver
[     3.911] (II) NVIDIA dlloader X Driver  460.32.03  Sun Dec 27 18:56:00 UTC 2020
[     3.912] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[     3.912] (II) systemd-logind: releasing fd for 226:1
[     3.912] (II) Loading sub module "fb"
[     3.912] (II) LoadModule: "fb"
[     3.913] (II) Loading /usr/lib/xorg/modules/libfb.so
[     3.913] (II) Module fb: vendor="X.Org Foundation"
[     3.913] 	compiled for 1.20.9, module version = 1.0.0
[     3.913] 	ABI class: X.Org ANSI C Emulation, version 0.4
[     3.913] (II) Loading sub module "wfb"
[     3.913] (II) LoadModule: "wfb"
[     3.913] (II) Loading /usr/lib/xorg/modules/libwfb.so
[     3.914] (II) Module wfb: vendor="X.Org Foundation"
[     3.914] 	compiled for 1.20.9, module version = 1.0.0
[     3.914] 	ABI class: X.Org ANSI C Emulation, version 0.4
[     3.914] (II) Loading sub module "ramdac"
[     3.914] (II) LoadModule: "ramdac"
[     3.914] (II) Module "ramdac" already built-in
[     3.915] (EE) No devices detected.
[     3.915] (II) Applying OutputClass "nvidia" to /dev/dri/card1
[     3.915] 	loading driver: nvidia
[     4.058] (==) Matched qxl as autoconfigured driver 0
[     4.058] (==) Matched nvidia as autoconfigured driver 1
[     4.058] (==) Matched nouveau as autoconfigured driver 2
[     4.058] (==) Matched modesetting as autoconfigured driver 3
[     4.058] (==) Matched fbdev as autoconfigured driver 4
[     4.058] (==) Matched vesa as autoconfigured driver 5
[     4.058] (==) Assigned the driver to the xf86ConfigLayout
[     4.059] (II) LoadModule: "qxl"
[     4.059] (II) Loading /usr/lib/xorg/modules/drivers/qxl_drv.so
[     4.059] (II) Module qxl: vendor="X.Org Foundation"
[     4.059] 	compiled for 1.20.7, module version = 0.1.5
[     4.059] 	Module class: X.Org Video Driver
[     4.059] 	ABI class: X.Org Video Driver, version 24.1
[     4.059] (II) LoadModule: "nvidia"
[     4.059] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[     4.059] (II) Module nvidia: vendor="NVIDIA Corporation"
[     4.059] 	compiled for <IP_ADDRESS>1, module version = 1.0.0
[     4.059] 	Module class: X.Org Video Driver
[     4.059] (II) UnloadModule: "nvidia"
[     4.059] (II) Unloading nvidia
[     4.059] (II) Failed to load module "nvidia" (already loaded, 0)
[     4.059] (II) LoadModule: "nouveau"
[     4.059] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[     4.059] (II) Module nouveau: vendor="X.Org Foundation"
[     4.059] 	compiled for 1.20.3, module version = 1.0.16
[     4.059] 	Module class: X.Org Video Driver
[     4.059] 	ABI class: X.Org Video Driver, version 24.0
[     4.059] (II) LoadModule: "modesetting"
[     4.059] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[     4.059] (II) Module modesetting: vendor="X.Org Foundation"
[     4.059] 	compiled for 1.20.9, module version = 1.20.9
[     4.059] 	Module class: X.Org Video Driver
[     4.059] 	ABI class: X.Org Video Driver, version 24.1
[     4.059] (II) LoadModule: "fbdev"
[     4.059] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[     4.059] (II) Module fbdev: vendor="X.Org Foundation"
[     4.059] 	compiled for 1.20.1, module version = 0.5.0
[     4.059] 	Module class: X.Org Video Driver
[     4.059] 	ABI class: X.Org Video Driver, version 24.0
[     4.059] (II) LoadModule: "vesa"
[     4.059] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[     4.059] (II) Module vesa: vendor="X.Org Foundation"
[     4.059] 	compiled for 1.20.4, module version = 2.4.0
[     4.059] 	Module class: X.Org Video Driver
[     4.059] 	ABI class: X.Org Video Driver, version 24.0
[     4.059] (II) NVIDIA dlloader X Driver  460.32.03  Sun Dec 27 18:56:00 UTC 2020
[     4.059] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[     4.059] (II) qxl: Driver for QXL virtual graphics: QXL 1
[     4.059] (II) NOUVEAU driver Date:   Mon Jan 28 23:25:58 2019 -0500
[     4.059] (II) NOUVEAU driver for NVIDIA chipset families :
[     4.059] 	RIVA TNT            (NV04)
[     4.059] 	RIVA TNT2           (NV05)
[     4.059] 	GeForce 256         (NV10)
[     4.059] 	GeForce 2           (NV11, NV15)
[     4.059] 	GeForce 4MX         (NV17, NV18)
[     4.060] 	GeForce 3           (NV20)
[     4.060] 	GeForce 4Ti         (NV25, NV28)
[     4.060] 	GeForce FX          (NV3x)
[     4.060] 	GeForce 6           (NV4x)
[     4.060] 	GeForce 7           (G7x)
[     4.060] 	GeForce 8           (G8x)
[     4.060] 	GeForce 9           (G9x)
[     4.060] 	GeForce GTX 2xx/3xx (GT2xx)
[     4.060] 	GeForce GTX 4xx/5xx (GFxxx)
[     4.060] 	GeForce GTX 6xx/7xx (GKxxx)
[     4.060] 	GeForce GTX 9xx     (GMxxx)
[     4.060] 	GeForce GTX 10xx    (GPxxx)
[     4.060] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[     4.060] (II) FBDEV: driver for framebuffer: fbdev
[     4.060] (II) VESA: driver for VESA chipsets: vesa
[     4.060] (WW) Falling back to old probe method for modesetting
[     4.060] (WW) Falling back to old probe method for fbdev
[     4.060] (WW) Falling back to old probe method for modesetting
[     4.060] (WW) Falling back to old probe method for fbdev
[     4.060] (II) [KMS] Kernel modesetting enabled.
[     4.060] (EE) No devices detected.
[     4.060] (EE)
Fatal server error:
[     4.060] (EE) no screens found(EE)
[     4.060] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[     4.060] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[     4.060] (EE)
[     4.066] (EE) Server terminated with error (1). Closing log file.`

I managed start Xorg. I change mdev to nvidia-259 (GRID RTX6000-4Q Description: num_heads=4, frl_config=60, framebuffer=4096M, max_resolution=7680x4320). But now I see only black screen with logo UBUNTU. And is what next?
How Can I check what nvidia loaded successfully and how can I use vnc with nvidia?
ps -A | grep gnome-session shows two gnome-session-*

First, why RTX6000 with TU102GL, not TU104GL? My card have gpu TU104.

The RTX6000 (TU102) offers more profiles than the T4 (TU104), so by using it you get access to 3 and 6 GB profiles.
The full lists are here:
https://docs.nvidia.com/grid/latest/grid-vgpu-user-guide/index.html#vgpu-types-tesla-t4
https://docs.nvidia.com/grid/latest/grid-vgpu-user-guide/index.html#vgpu-types-quadro-rtx6000

I managed start Xorg. I change mdev to nvidia-259 (GRID RTX6000-4Q Description: num_heads=4, frl_config=60, framebuffer=4096M, max_resolution=7680x4320). But now I see only black screen with logo UBUNTU. And is what next?
How Can I check what nvidia loaded successfully

nvidia smi on the guest should show that the vGPU (RTX6000-4Q) is present and that Xorg is running (under Processes:).
$ nvidia-smi
Sun Jul 11 14:53:41 2021
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 460.73.01    Driver Version: 460.73.01    CUDA Version: 11.2     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  GRID P40-8Q         Off  | 00000000:07:01.0  On |                  N/A |
| N/A   N/A    P8    N/A /  N/A |    666MiB /  8192MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A       762      G   /usr/lib/xorg/Xorg                 94MiB |
+-----------------------------------------------------------------------------+

and how can I use vnc with nvidia?

To use vnc you can install x11vnc on the guest, this allows you to take advantage of the vGPU for rendering. I will also note that I had issues with getting this to work with the GNOME display manager and ended up installing LightDM instead.
sudo x11vnc -display :0 -auth /var/run/lightdm/root/:0 -forever -shared

ps -A | grep gnome-session shows two gnome-session-*

I see that you still have the QXL graphics adapter attached to the VM, maybe that is the issue? Anyway, I would remove that display adapter since I don't see why you would need it.
Also, if it helps, here is my xorg.conf

Click to show
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 460.73.01

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Thank you. And now it works. But fps is very low (few frames in second) and gpu usage up to 98%


Add more details to non-functional requirements [28 Feb, 23:59]

I added accessability, version, and localization sections for non-function requirements. However, I think that the content of version and localization is not enough. For this reason, we can add some new features in these sections.

It is continued on #28.


Feature: update docker hub description when publishing an image

PR Checklist
PR Structure

[x] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[x] This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[x] This PR's title starts with name of package that is most changed in the PR, ex.
paymentservice.stellar, or all or doc if the changes are broad or impact many
packages.

Thoroughness

[x] This PR adds tests for the most critical parts of the new functionality or fixes.

What
Update docker hub description when publishing an image.
Why
So the Docker Hub contains information about the root repository from where those images were generated.

Reference Server Preview is available here:https://anchor-ref-pr530.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr530.previews.kube001.services.stellar-ops.com/

Reference Server Preview is available here:https://anchor-ref-pr530.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr530.previews.kube001.services.stellar-ops.com/

Reference Server Preview is available here:https://anchor-ref-pr530.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr530.previews.kube001.services.stellar-ops.com/

Reference Server Preview is available here:https://anchor-ref-pr530.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr530.previews.kube001.services.stellar-ops.com/

Reference Server Preview is available here:https://anchor-ref-pr530.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr530.previews.kube001.services.stellar-ops.com/

Reference Server Preview is available here:https://anchor-ref-pr530.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr530.previews.kube001.services.stellar-ops.com/

Closing this issue because descriptions will be updated manually for now.


Rewrite the merge bags tool in C++ because of rosjava error

Because of rosjava, the merge bag tool with the python API doesn't work with the error:
genmsg.msg_loader.MsgNotFound: Cannot locate message [Header]: unknown package [std_msgs] on search path [{}]
This doesn't happen with the C++ API because we have the sci cam add tool that runs fine, and we're actually using it to preprocess the bags because the other tool doesn't work.

To just fill in some detail, the isaac tool named isaac/src//dense_map/geometry_mapper/tools/add_sci_cam_to_bag.cc (which shows how to use the C++ API to process a bag) should be copied to the astrobee repo, renamed to merge_bags.cc, and some simple modifications need to be made to it to append multiple bags to a bag instead of appending sci cam images, and the old merge_bags.py tool this would replace should be wiped.
This is overall little work and will greatly improve our bag processing toolchain. The new tool should be tested though with a problematic bag to ensure it works where the old one did not. Also the documentation in astrobee where this tool is referenced should be updated.

I replaced merge_bags.py with a C++ tool called merge_bags. This fixes the rosjava issue. The API of the new tool is:
merge_bags -output_bag out.bag input1.bag input2.bag ...


adding tracker urls when torrent was loaded from magnet link

This looks great to me! I'll add a test to verify this works :)

Merged manually after I added a test covering this change!
Your commit: https://github.com/alanmcgovern/monotorrent/commit/27b8ea5fd1c85ec5a03ce248348b83f94a5c3fac
My tests: https://github.com/alanmcgovern/monotorrent/commit/7400a9bbaa5fdde13dd5c28dc8e3b81a8e3e6e17

Note: I did change the final implementation so the AnnounceUrls aren't exposed in two places. They're already accessible via the TrackerManager :)


types(h): Support passing props to Component when using h

fix #3218

👍 simpler than I expected, ty. Should I open a new issue for the TSX problem, this doesn't fix it.

TSX is not related with this, can you create another issue for the TSX problem?


Feature/improved failure handling experience

Hello!
I have 2 ideas (and ready implementations in this PR) to improve error message readability.
The first idea
I often encounter is overly detailed logging of complex structures in the "Expected" messages.
For example:
let's have this schema
const Obj = Record({
  id: Number,
  name: String,
  nested: Record({
    id2: Number,
    name2: String,
    nested2: Array(
      Record({
        nested3: Record({
          id3: String,
        }),
      }),
    ),
  }),
});

// and we will validate this object
const result = Obj.validate({
		id: 3,
		name: "test"
})

The validation result will be very messy:
{
      nested: 'Expected { id2: number; name2: string; nested2: { nested3: { id3: string; }; }[]; }, but was missing'
}

It seems unnecessary to describe the expected type since it is already known in the runtypes schema description. Moreover, this description complicates error message readability.
Instead, I propose writing "Expected (array | tuple | object | dictionary) but was ..."
in this PR result will change to this
{
      nested: 'Expected object, but was missing'
}

It looks readable and doesn't lose its meaning.
The second idea
In messages like "Expected something but was (array | object)" it would be helpful to see exactly which entity was received.
I have decided to add a new field called extraDetails next to the details field, which will contain not only the error message but also the actual value (received field) and possibly the error code.
Let's go back to the previous schema and pass it this object as input:
const result = Obj.validate({
      id: 3,
      name: 5,
      nested: { nested2: { a: 'b' } },
  })

In this PR, the result.extraDetails field will contain this convenient message:
 {
      name: {
        message: 'Expected string, but was number',
        received: 5,
        code: 'TYPE_INCORRECT'
      },
      nested: {
        id2: {
          message: 'Expected number, but was missing',
          received: undefined,
          code: 'PROPERTY_MISSING'
        },
        name2: {
          message: 'Expected string, but was missing',
          received: undefined,
          code: 'PROPERTY_MISSING'
        },
        nested2: {
          message: 'Expected array, but was object',
          received: { a: 'b' },
          code: 'TYPE_INCORRECT'
        }
      }
  }

Thus, extraDetails will improve error perception without affecting the existing details field.

Thanks suggestion! Per-property failcode is one of missing thing in runtypes at this moment, so sounds good overall, but in the second idea, it sounds quite frightening to me to expose the received value into the error, because I'm pretty sure not a few users would be logging errors as is and sending the logs into somewhere insecure. Thus, at least received property should be explicitly enabled by a flag for each specific runtype the user intends to behave like that, such as runtype.withOptions({ includeReceivedValueInFailure: true }).
I'd say this should be worth beaking-changing the content of details property, for simplicity of the API surface. Besides, I'm now quite nervous and pessimistic at versioning i.e. I think every single change to any behavior that can be observable by users should be treated as a breaking change (even with notice not to depend on). So, if possible, I'd like to include this PR into the next major release.


@22Nov Explore Feature

[x] Explore Feature End Points

These issue completed late because of data scraping and cleaning.

These issue completed late because of data scraping and cleaning.

These issue completed late because of data scraping and cleaning.


Fire .change event when value in awesomplete input changes

Right now awesomplete fires an awesomplete-selectcomplete event whenever a selection is complete.  But I often may not care about how the value of the input changed but only that it did.  If the element also fired a normal change event, then I could write my code without depending on whether the input is or is not using awesomplete.

Good point! We should also fire the input event if we do this.

In the meantime you can workaround by:
var input = document.getElementById('textInputCSSID');
input.addEventListener("awesomplete-selectcomplete", function(event) {
var changeEvent = new Event('change');
input.dispatchEvent(changeEvent);
});


Validations and model specs

Features added in this PR:

[x] Added validations for the User and Post model
[x] Added unit specs for all of the models' methods and validations

Thank you 🙏 @ichala


Use a single test thread when running miri

Which issue does this PR close?
Testing to see if this closes https://github.com/apache/arrow-rs/issues/879
Theory is that something about the new version of MIRI uses more memory
Rationale for this change
MIRI is failing on master for reasons that are not reproducible (yet) locally for myself or @Jimexist
What changes are included in this PR?
add --test-threads=1 command
Are there any user-facing changes?
No

Codecov Report

Merging #891 (0dd0d62) into master (898924f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #891   +/-   ##
=======================================
  Coverage   82.45%   82.45%
=======================================
  Files         168      168
  Lines       48231    48231
=======================================
  Hits        39767    39767
  Misses       8464     8464

Impacted Files
Coverage Δ

arrow/src/datatypes/datatype.rs
65.36% <0.00%> (-0.44%)
:arrow_down:

parquet/src/encodings/encoding.rs
94.67% <0.00%> (+0.19%)
: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 898924f...0dd0d62. Read the comment docs.

Single thread did not seem to help but skipping the cache did https://github.com/apache/arrow-rs/runs/4059773777?check_suite_focus=true
I'll open a new PR with just the right change


Should installing a pack enable the included extensions?

Issue Type: Bug
Testing #54862
Installing an extension pack with some included extensions already installed but disabled, currently does not enable these extensions. It seems to make sense to enable these similarly to installing any missing ones.
VS Code version: Code - Insiders 1.26.0-insider (5fae91d61f12726e149fe5baed342eac2fbf8f88, 2018-07-25T01:56:56.548Z)
OS version: Darwin x64 17.7.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz (8 x 2200)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: enabledrasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
3, 3, 4

Memory (System)
16.00GB (0.52GB free)

Process Argv
/Applications/Visual Studio Code - Insiders.app/Contents/MacOS/Electron

Screen Reader
no

VM
22%

Extensions (2)

Extension
Author (truncated)
Version

autofilename
Jer
0.1.3

999-pack1
chr
0.12.0

I would not agree for this. Pack is just a bundle of independent extensions to install together. Enabling the extensions user disabled just a pack is installed might not be expected for the user.


fix(behavior_velocity_planner::intersection): strictly wait at 1st stop line when occlusion is detected

Description
停止してからパラメーターで指定される時間だけ厳密に停止するように修正
Same as
https://github.com/autowarefoundation/autoware.universe/pull/3528
https://github.com/autowarefoundation/autoware.universe/pull/3539
Related links

Tests performed

Notes for reviewers

Interface changes

Effects on system behavior

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

(色々いじってしまいましたが無視してもらって大丈夫です。Create merge commitでmergeしたいと思います。)


Add signet option to Admin UI

in the Admin UI:

Elsewhere in the code there is this enum match:
match network {
        Network::Bitcoin => Currency::Bitcoin,
        Network::Regtest => Currency::Regtest,
        Network::Testnet => Currency::BitcoinTestnet,
        Network::Signet => Currency::Signet,
    }

Support for all options is desired.

I think we should still implement this. The new setup UI will still take a while.

I could take a look at this.

👏 🙌
-GK

From: elsirion @.>
Sent: Sunday, April 23, 2023 8:31:51 AM
To: fedimint/fedimint @.>
Cc: Gary R Krause @.>; Author @.>
Subject: Re: [fedimint/fedimint] Add signet option to Admin UI (Issue #2013)
Closed #2013https://github.com/fedimint/fedimint/issues/2013 as completed via #2304https://github.com/fedimint/fedimint/pull/2304.
—
Reply to this email directly, view it on GitHubhttps://github.com/fedimint/fedimint/issues/2013#event-9074834191, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJJ3KEKEVSFPWA7ONUJP4RTXCUOLPANCNFSM6AAAAAAWFSC7HE.
You are receiving this because you authored the thread.Message ID: @.***>


A check before jQuery UI related functions

First of all, thank you for your great work ;)
As mentioned in #173 and #144, there have been requests to decouple GridStack from jQuery UI.
I understand a full decoupling will require a lot of work, but that will be a great plus when it happens ;)
FYI, I am currently working on a Drupal 8 module to integrate with your plugin, and have similar point like the other threads: Admin editable, but front end static.
The addition of staticGrid option helps this, however I noticed JS errors when no jQuery UI is loaded.
At ~line 875 no check is run prior to calling .draggable and .resizable. The issue is resolved once I add a check:
if (this.opts.draggable || this.opts.resizable) { ....
I am not sure about any better check up there.
I wonder if you could incorporate the fix into the next release?
I would also love to hear if jQuery UI decoupling is on the roadmap?
Sorry if I missed any other related thread to this issue. The above two mentioned are the closest I found by now.
Thanks again.

Let's start with the juicy stuff: part of the gridstack roadmap is to get rid of all dependencies, not just jqueryui. There will be a plugin system, initially just for drag/resize, and we'll kickstart it by providing two or three options for drag/resize. As part of that, we will necessarily have to accomplish the query you're asking about.
There are a couple ways to enable/disable drag and resize. That makes it awfully easy to do a small fix like the one you're proposing but end up in a weird state.
Perhaps it's worth adding in a variable that holds the status of whether or not draggable/resizable are allowed, independently. These can be checked before any call to .draggable or .resizable are made.
Our "next big thing" is definitely to build out the plugin system, but just in case it doesn't make it into v0.3.0, I would be happy to implement exactly what you're asking for.

Awesome, glad to hear it is on the roadmap ;)
Thank you for any possible short term fix on this as this is likely one of the most wanted features when I release the module. Truly appreciated.

Closing. This has been resolved.


Fixed #31591 -- Clarified "reverse" lookup name in making queries docs.

Also https://github.com/django/django/commit/2b1ea4b3c2e32d0510a72bed4a67bec572a57442, adjusts examples to match the example models at the top.

@carltongibson Thanks :+1: looks good.


LG G3 Gyro Issues(Cardboard 0.6)

I'm having an issue with my LG G3 where the Head Pose resets back to center frequently and randomly. It also occurs in the Cardboard Demo Project.
I'm using Cardboard 0.6 and Unity 5.3.1p2
The problem doesn't occur on any of my other dev phones or tablets that I've tested so far:
Nexus 7, Nexus 9, Samsung S5, Samsung S4

Duplicate of #120.


Config syntax error on startup

Just updated to the latest release, The docker wont launch instead will exit, below is the log output,

<EMAIL_ADDRESS>entrypoint-config /usr/app
node dist/src/entrypoint-config.js

/usr/app/node_modules/json5/lib/parse.js:1083
const err = new SyntaxError(message)
SyntaxError: JSON5: invalid character '"' at 11:5
at syntaxError (/usr/app/node_modules/json5/lib/parse.js:1083:17)
at invalidChar (/usr/app/node_modules/json5/lib/parse.js:1028:12)
at Object.afterPropertyValue (/usr/app/node_modules/json5/lib/parse.js:654:15)
at Object.default (/usr/app/node_modules/json5/lib/parse.js:146:37)
at lex (/usr/app/node_modules/json5/lib/parse.js:78:42)
at Object.parse (/usr/app/node_modules/json5/lib/parse.js:25:17)
at Object. (/usr/app/src/common/config/setup.ts:56:30)
at Module._compile (internal/modules/cjs/loader.js:1085:14)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
at Module.load (internal/modules/cjs/loader.js:950:32)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>entrypoint-config: node dist/src/entrypoint-config.js
npm ERR! Exit status 1
npm ERR! Failed at the<EMAIL_ADDRESS>entrypoint-config script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2021-10-03T02_27_45_193Z-debug.log
cat: can't open '/tmp/config.json': No such file or directory
cat: can't open '/tmp/config.json': No such file or directory
cat: can't open '/tmp/config.json': No such file or directory
cat: can't open '/tmp/config.json': No such file or directory
Setting timezone:
Run on startup:
Run once:
Exiting...

SyntaxError: JSON5: invalid character '"' at 11:5

You have an syntax error in your config.json(5) at line 11, column 5.

hmm, could you assist with my config file? I think I followed the conversion tutorial correctly but perhaps screwed something else up?
(replaced sensitive information with X's)
{
"accounts": [
// Multiple accounts can be configured here
{
"email"<EMAIL_ADDRESS>"password": "X",
"totp": "X"
},
],
"searchStrategy": "promotion"
"runOnStartup": true,
"timezone": "Australia/Sydney",
"intervalTime": 60,
"cronSchedule": "0 6 * * *",
"runOnce": false,
"logLevel": "info",
"notifiers": {
"type": "email",
"smtpHost": "smtp.gmail.com",
"smtpPort": 465,
"emailSenderAddress"<EMAIL_ADDRESS>"emailSenderName": "Epic Games Captchas",
"emailRecipientAddress"<EMAIL_ADDRESS>"secure": true,
"auth": {
"user"<EMAIL_ADDRESS>"pass": "X",
},
"webPortalConfig": {
"baseUrl": "192.168:3055",
}
},
}

A couple things:

The syntax error was a missing comma after "promotion"
notifiers should be within an array
Your baseUrl isn't a valid IP, but I assume that's just some redaction you did

Here's the fixed version:
{
    "accounts": [
        // Multiple accounts can be configured here
        {
            "email"<EMAIL_ADDRESS>            "password": "X",
            "totp": "X"
        },
    ],
    "searchStrategy": "promotion",
    "runOnStartup": true,
    "timezone": "Australia/Sydney",
    "intervalTime": 60,
    "cronSchedule": "0 6 * * *",
    "runOnce": false,
    "logLevel": "info",
    "notifiers": [{
        "type": "email",
        "smtpHost": "smtp.gmail.com",
        "smtpPort": 465,
        "emailSenderAddress"<EMAIL_ADDRESS>        "emailSenderName": "Epic Games Captchas",
        "emailRecipientAddress"<EMAIL_ADDRESS>        "secure": true,
        "auth": {
            "user"<EMAIL_ADDRESS>            "pass": "X",
        },
        "webPortalConfig": {
            "baseUrl": "192.168:3055",
        }
    }],
}

Awesome that work thank you!
I have noticed however on the capcha portal on the email comes through as portalUrl: "http://localhost:3000 instead off the IP I specified

You placed the
"webPortalConfig": {
            "baseUrl": "192.168:3055",
        }

block inside the notifier. Move it to the root level of the config and you should be good. Refer to the example if you get stuck.

@claabs Just wanted to say thanks, I had the same issue. Traced it back to the config thanks to your reply.

Let me know if there's any way I can improve the documentation for the config file. I think of most things from a developer standpoint, but I want to be sure someone with less experience can get started easily as well.

Thanks Claabs, I managed to get everything working, thanks for the assist and great work on the App!

I'm getting this error again, I don't know why it stopped working again!?
/usr/app/node_modules/json5/lib/parse.js:1083
const err = new SyntaxError(message)
^
SyntaxError: JSON5: invalid character '"' at 19:5
at syntaxError (/usr/app/node_modules/json5/lib/parse.js:1083:17)
at invalidChar (/usr/app/node_modules/json5/lib/parse.js:1028:12)
at Object.afterPropertyValue (/usr/app/node_modules/json5/lib/parse.js:654:15)
at Object.default (/usr/app/node_modules/json5/lib/parse.js:146:37)
at lex (/usr/app/node_modules/json5/lib/parse.js:78:42)
at Object.parse (/usr/app/node_modules/json5/lib/parse.js:25:17)
at Object. (/usr/app/src/common/config/setup.ts:56:30)
at Module._compile (internal/modules/cjs/loader.js:1085:14)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
at Module.load (internal/modules/cjs/loader.js:950:32)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>entrypoint-config: node dist/src/entrypoint-config.js
npm ERR! Exit status 1
npm ERR! Failed at the<EMAIL_ADDRESS>entrypoint-config script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2021-10-07T04_45_03_500Z-debug.log
cat: can't open '/tmp/config.json': No such file or directory
cat: can't open '/tmp/config.json': No such file or directory
cat: can't open '/tmp/config.json': No such file or directory
cat: can't open '/tmp/config.json': No such file or directory
Setting timezone:
Run on startup:
Run once:
Exiting...
Here's the config again:
{
"accounts": [
{
"email"<EMAIL_ADDRESS>"password": "x",
"totp": "xx",
},
],
"searchStrategy": "promotion",
"runOnStartup": true,
"timezone": "Australia/x",
"intervalTime": 60,
"cronSchedule": "0 6 * * *",
"runOnce": false,
"logLevel": "info",
"webPortalConfig": {
"baseUrl": "<IP_ADDRESS>:3055",
}
"notifiers": [
{
"type": "email",
"smtpHost": "smtp.gmail.com",
"smtpPort": 465,
"emailSenderAddress"<EMAIL_ADDRESS>"emailSenderName": "Epic Games Captchas",
"emailRecipientAddress"<EMAIL_ADDRESS>"secure": true,
"auth": {
"user"<EMAIL_ADDRESS>"pass": "x",
},
},
],

}

Oh how frustrating! I have solved it, I also encountered another error of a 'not a valid web address', solved this by putting http in front of the IP address for the web url and now everything is working nicely :)
Hopefully I wont break anything else by missing a comma.


Why the loss computed during training is Nan？

I followed the actions in the readme documentation to configure the environment（Create a virtual environment via .yml), and downloaded the Dataset-mini v1.1 to ../  . But the loss calculated when running run.py training is nan. When debugging, I found that when the data passed through the front_conv layer of the FingerPrinter model, the values of the calculated tensor were all 0 or nan. What‘s wrong and why is this happening?

Sorry for not giving you a good answer. Can you provide environmental information?
conda env export > my_env.yml

Or you may try creating a virtual environment without .yml option.

I had the same problem when I ran it on RTX3090 with batchsize=640

**name: tensorflow
channels:

defaults
dependencies:
_libgcc_mutex=0.1=main
_openmp_mutex=4.5=1_gnu
ca-certificates=2022.4.26=h06a4308_0
certifi=2021.10.8=py38h06a4308_2
cudatoolkit=11.0.221=h6bb024c_0
ld_impl_linux-64=2.35.1=h7274673_9
libffi=3.3=he6710b0_2
libgcc-ng=9.3.0=h5101ec6_17
libgomp=9.3.0=h5101ec6_17
libstdcxx-ng=9.3.0=hd4cf53a_17
ncurses=6.3=h7f8727e_2
openssl=1.1.1n=h7f8727e_0
pip=21.2.4=py38h06a4308_0
python=3.8.10=h12debd9_8
readline=8.1.2=h7f8727e_1
setuptools=61.2.0=py38h06a4308_0
sqlite=3.38.2=hc218d9a_0
tk=8.6.11=h1ccaba5_0
wheel=0.37.1=pyhd3eb1b0_0
xz=5.2.5=h7b6447c_0
zlib=1.2.12=h7f8727e_2
pip:

absl-py==0.15.0
appdirs==1.4.4
astunparse==1.6.3
audioread==2.1.9
cachetools==5.0.0
cffi==1.15.0
charset-normalizer==2.0.12
click==8.1.3
cycler==0.11.0
decorator==5.1.1
faiss-gpu==1.6.5
flatbuffers==1.12
fonttools==4.33.3
gast==0.3.3
google-auth==2.6.6
google-auth-oauthlib==0.4.6
google-pasta==0.2.0
grpcio==1.32.0
h5py==2.10.0
idna==3.3
importlib-metadata==4.11.3
joblib==1.1.0
kapre==0.3.5
keras==2.8.0
keras-nightly==2.5.0.dev2021032900
keras-preprocessing==1.1.2
kiwisolver==1.4.2
libclang==14.0.1
librosa==0.9.1
llvmlite==0.38.0
markdown==3.3.6
matplotlib==3.5.1
numba==0.55.1
numpy==1.19.5
oauthlib==3.2.0
opt-einsum==3.3.0
packaging==21.3
pillow==9.1.0
pooch==1.6.0
protobuf==3.20.1
pyasn1==0.4.8
pyasn1-modules==0.2.8
pycparser==2.21
pyparsing==3.0.8
python-dateutil==2.8.2
pyyaml==5.4.1
requests==2.27.1
requests-oauthlib==1.3.1
resampy==0.2.2
rsa==4.8
scikit-learn==1.0.2
scipy==1.8.0
six==1.15.0
soundfile==0.10.3.post1
tensorboard==2.8.0
tensorboard-data-server==0.6.1
tensorboard-plugin-wit==1.8.1
tensorflow==2.4.0
tensorflow-estimator==2.4.0
tensorflow-gpu==2.4.0
tensorflow-io-gcs-filesystem==0.25.0
termcolor==1.1.0
tf-estimator-nightly==2.8.0.dev2021122109
threadpoolctl==3.1.0
typing-extensions==<IP_ADDRESS>
urllib3==1.26.9
wavio==0.0.4
werkzeug==2.1.2
wrapt==1.12.1
zipp==3.8.0
prefix:
**

`name: tensorflow
channels:

defaults
dependencies:
_libgcc_mutex=0.1=main
_openmp_mutex=4.5=1_gnu
ca-certificates=2022.4.26=h06a4308_0
certifi=2021.10.8=py38h06a4308_2
cudatoolkit=11.0.221=h6bb024c_0
ld_impl_linux-64=2.35.1=h7274673_9
libffi=3.3=he6710b0_2
libgcc-ng=9.3.0=h5101ec6_17
libgomp=9.3.0=h5101ec6_17
libstdcxx-ng=9.3.0=hd4cf53a_17
ncurses=6.3=h7f8727e_2
openssl=1.1.1n=h7f8727e_0
pip=21.2.4=py38h06a4308_0
python=3.8.10=h12debd9_8
readline=8.1.2=h7f8727e_1
setuptools=61.2.0=py38h06a4308_0
sqlite=3.38.2=hc218d9a_0
tk=8.6.11=h1ccaba5_0
wheel=0.37.1=pyhd3eb1b0_0
xz=5.2.5=h7b6447c_0
zlib=1.2.12=h7f8727e_2
pip:

absl-py==0.15.0
appdirs==1.4.4
astunparse==1.6.3
audioread==2.1.9
cachetools==5.0.0
cffi==1.15.0
charset-normalizer==2.0.12
click==8.1.3
cycler==0.11.0
decorator==5.1.1
faiss-gpu==1.6.5
flatbuffers==1.12
fonttools==4.33.3
gast==0.3.3
google-auth==2.6.6
google-auth-oauthlib==0.4.6
google-pasta==0.2.0
grpcio==1.32.0
h5py==2.10.0
idna==3.3
importlib-metadata==4.11.3
joblib==1.1.0
kapre==0.3.5
keras==2.8.0
keras-nightly==2.5.0.dev2021032900
keras-preprocessing==1.1.2
kiwisolver==1.4.2
libclang==14.0.1
librosa==0.9.1
llvmlite==0.38.0
markdown==3.3.6
matplotlib==3.5.1
numba==0.55.1
numpy==1.19.5
oauthlib==3.2.0
opt-einsum==3.3.0
packaging==21.3
pillow==9.1.0
pooch==1.6.0
protobuf==3.20.1
pyasn1==0.4.8
pyasn1-modules==0.2.8
pycparser==2.21
pyparsing==3.0.8
python-dateutil==2.8.2
pyyaml==5.4.1
requests==2.27.1
requests-oauthlib==1.3.1
resampy==0.2.2
rsa==4.8
scikit-learn==1.0.2
scipy==1.8.0
six==1.15.0
soundfile==0.10.3.post1
tensorboard==2.8.0
tensorboard-data-server==0.6.1
tensorboard-plugin-wit==1.8.1
tensorflow==2.4.0
tensorflow-estimator==2.4.0
tensorflow-gpu==2.4.0
tensorflow-io-gcs-filesystem==0.25.0
termcolor==1.1.0
tf-estimator-nightly==2.8.0.dev2021122109
threadpoolctl==3.1.0
typing-extensions==<IP_ADDRESS>
urllib3==1.26.9
wavio==0.0.4
werkzeug==2.1.2
wrapt==1.12.1
zipp==3.8.0
prefix:
`

But don't know why, it seems to work suddenly，My configuration is CUDA11.0, CUDNN 8.0, tensorflow2.4, I hope it can help you.

But don't know why, it seems to work suddenly，My configuration is CUDA11.0, CUDNN 8.0, tensorflow2.4, I hope it can help you.

But the current results show that it is abnormally high, the first epoch reaches 83%, I don't know why.Because I've been busy lately, I can't figure out the reason for the time being.

@Novicei

But the current results show that it is abnormally high, the first epoch reaches 83%, I don't know why.Because I've been busy lately, I can't figure out the reason for the time being.

Is the 83% for validation or actual test? It's totally normal in validation accuracy for 1s input, because the validation set consists of a few hundred 30s songs database.

Is for validation.I followed the 620_lamb file you posted for training.But I look at the accuracy rate you posted, the first epoch starts at 65%. #15

@Novicei It is possible that the validation accuracy is low on the first epoch with a larger batch size. However, in the end, in the 100th (or more) epoch, bsz=640 will get better validation accuracy than bsz=120. The slow training of bsz=640 suggests that the new scheduler for learning rate and temperature will be useful. However, this topic has not been discussed further in the paper.

@mimbres I don't understand what you mean by that. I mean, I used your 640 configuration file for the experiment, but the verification accuracy of the output is 83% for the first epoch 1s, 100% for the 5s and above, and the accuracy for the seventh epoch 1 second is about 93% % This should not match your results in #15, I don't know what's wrong, maybe it's my environment.

@Novicei Sorry, I misunderstood your question last time.
As you mentioned, the mini-test validation accuracy (~94%) of current repo with the 640 configuration  is higher than that I reported in #15 (~83%). Let me share a new 640_lamb_ep400 result.

It is also noticeable that the val_loss scale is different from #15.
To explain, we can get different scale of val_loss and val_acc depending on the selection of validation set we use in the mini-search-validation(). The value of max_n_samples and the size of validation set has changed since performing the pre-release experiment mentioned in #15. 'max_n_samples' is currently set to 3,000 for quick validation. You can set up to 25,000 as needed.
Thanks for reporting this!


Seeing websocket handshake failue with end of stream when connecting to echo.websocket,org both on SSL and TCP.  Code is very similar to the client example

using boost 1.75 on CentOS7 and beast version is 306. Appreciate the help. If error code is needed I only have the error message but if one can tell me how to get error code of beast will change and post it here

Can you share a github project so I can reproduce?

I dont. Its an official one. So its not in here :(

would you be able to share with me a minimal complete example of the connect issue? It would probably require about 50 lines of code in one .cpp file to reduce it to the minimum number of steps to reproduce.

Sure will try it to redact and paste it here.  Give like 15 min

Hey so I figured the issue - some how my URI path was messed up and instead of / it had some other data member. So once I found that and fixed the WS handshake went thro fine. Thanks
Cheers

I am marking it closed.


[Bug] Minimap context menu items don't work?

Reproducible in vscode.dev or in VS Code Desktop?

[X] Not reproducible in vscode.dev or VS Code Desktop

Reproducible in the monaco editor playground?

[X] Not reproducible in the monaco editor playground

Monaco Editor Playground Link
No response
Monaco Editor Playground Code
No response
Reproduction Steps

right-click inside Minimap to display context menu

attempt to use any of the menu items, for example: Minimap

Actual (Problematic) Behavior
Context menu items don't work, for example: if Minimap is checked, I expected selecting this menu item to disable the Minimap. Instead it does nothing and the Minimap item is still checked.
Expected Behavior
No response
Additional Context
The Minimap context menu does work when I tried it in vscode.dev. The context menu is not present in the monaco editor playground, so I couldn't test it there. I'm not setting any complicated options when setting up the editor:
var editorDiv = $scope.selector("#CMpopoutJavaScript").get(0);
$scope.monacoObjText = monaco.editor.create(editorDiv, {
          value: null, language: 'javascript', automaticLayout: true
});

Using version 0.36.1 of monaco on both Chrome and Firefox running on Mac OS.

See https://github.com/microsoft/monaco-editor/issues/3559