dynamically add routes

Would it be possible to dynamically add routes found in a chunk loaded through import?
When a route is loaded asynchronously, the router context passed is a copy so the original context cannot be modified at the moment.

Basic example:
const route = {
  path: '/admin',
  children: [], // place for lazy routes
  async action(context) {
    const routes = await import('./admin/routes.js'); // load routes asynchronously
    context.route.children = routes; // dynamically add routes
    delete context.route.action; // execute action method only once
    return context.next(); // go to just loaded routes
  }
}

Also you can dynamically add new routes at any time:
routes.push(newRoute)

Would you describe your use case more or provide examples, why do you want to modify context?

Thanks a lot, it works perfectly, see the full code at https://github.com/FredericHeem/starhackit/blob/master/client/src/app/router.js


feat(shared-data): add magnetic block 2d rendering key

Overview
This PR adds a real 2d rendering key to the mag block so it can be rendered in our frontend codebases.
Review Requests
Pop over here and play with the mag block. You should be able to show and hide different layers.

Risk Assessment
Low

@jerader yes exactly!


DOC/MNT: add configure count time wrapper / decorator to docs

Description

configure_count_time_wrapper and configure_count_time_decorator
have existed from 2017, but were not included in the built docs.
Also change to use rd internally.
Motivation and Context

This is something that is frequently asked for and we already have the machinery extracted from the (now removed) spec API.  in ~2017 we generalized it but have not been using it.
How Has This Been Tested?

The wrapper already has tests in the test suite.

I am not sure that this is actually the best way to do this as it assumes that there is a single signal that we can set to adjust the count time, it may be better to have a protocal of checking for am obj.adjust_my_count_time_plan on the objects something like
def adjust_count_time(self, target: float) -> PlanFunction:
     current_time = yield from bps.rd(self.count_time)
     yield from bps.mv(self.count_time, target)
     return partial(self.adjust_count_time, target=current_time)  # return how to "undo" the change

Could also see a case for returning (old_time, new_time) as a tuple and assuming that we can use the same plan method to re-set it to the old one?

Could it be a dict instead, since some detectors have multiple attributes to be configured?  Keys would be as in stage_sigs (possibly referring to some.deeper.subdevice.with.count_time in the Device).

@prjemian: Abstract away from count time, exposure time to "time for measurement". Make it the responsibility of the ophyd Device to handle this rather than pushing it into plans.
@danielballan: Maybe should think of ophyd interface "conventions" for specialized cases like this, a tier of standard methods below "required" and even below the universal "optional" ones like stage.
@ksunden: Yaq has a similar notion, "traits": https://yaq.fyi/traits/
@prjemian: Implement as mix-in class.


An error occurs during the import of asset data.

Information about bug
An error occurs during the import of asset data.
when trying to import asset data with the purchase invoice  and the Gross purchase amount below error is occurring

Module
assets
Version
Assets: v0.0.1 (pre-prod)
ERPNext: v15.34.0 (pre-prod)
Frappe Framework: v15.41.0 (pre-prod)
Installation method
None
Relevant log output / Stack trace / Full Error Message.
Traceback (most recent call last):
  File "apps/frappe/frappe/core/doctype/data_import/importer.py", line 149, in import_data
    doc = self.process_doc(doc)
  File "apps/frappe/frappe/core/doctype/data_import/importer.py", line 251, in process_doc
    return self.insert_record(doc)
  File "apps/frappe/frappe/core/doctype/data_import/importer.py", line 270, in insert_record
    new_doc.insert()
  File "apps/frappe/frappe/model/document.py", line 291, in insert
    self.run_before_save_methods()
  File "apps/frappe/frappe/model/document.py", line 1091, in run_before_save_methods
    self.run_method("validate")
  File "apps/frappe/frappe/model/document.py", line 962, in run_method
    out = Document.hook(fn)(self, *args, **kwargs)
  File "apps/frappe/frappe/model/document.py", line 1322, in composer
    return composed(self, method, *args, **kwargs)
  File "apps/frappe/frappe/model/document.py", line 1304, in runner
    add_to_return_value(self, fn(self, *args, **kwargs))
  File "apps/frappe/frappe/model/document.py", line 959, in fn
    return method_object(*args, **kwargs)
  File "apps/assets/assets/assets/doctype/asset/asset.py", line 131, in validate
    self.validate_gross_and_purchase_amount()
  File "apps/assets/assets/assets/doctype/asset/asset.py", line 384, in validate_gross_and_purchase_amount
    frappe.throw(error_message, title=_("Invalid Gross Purchase Amount"))
  File "apps/frappe/frappe/__init__.py", line 652, in throw
    msgprint(
  File "apps/frappe/frappe/__init__.py", line 617, in msgprint
    _raise_exception()
  File "apps/frappe/frappe/__init__.py", line 568, in _raise_exception
    raise exc
frappe.exceptions.ValidationError: Gross Purchase Amount should be equal to purchase amount of one single Asset.
Please do not book expense of multiple assets against one single Asset.

Purchase Amount filed is also required in template along with Gross Purchase Amount

Functionality working after entering purchase amount field in data import file


 tags with no href

Hello, I'm trying to use your converter (thank you) to convert some code, but the problem is it has some  tags without href, for which your library throws a malformed link exception. The  in the code I want to convert are like:
<a rel="nofollow">4d10f06 </a>
The little research I have done says points that that is valid HTML.

Hi Flamma, you are right, I will update the library as soon as I found a minute.


add stable audio tools as a library + code snippets.

Adds inference snippets, download count support for stable audio tools.

The failing test is unrelated to this PR.

Given there is more or less agreement here, I will merge this!

@Vaibhavs10 does the model card also require "library_name: "stable_audio" to be added? https://huggingface.co/stabilityai/stable-audio-open-1.0

@NielsRogge Yes it does! Actually, it requires library_name: stable-audio-tools in the model card metadata.

Ok, opened a PR here: https://huggingface.co/stabilityai/stable-audio-open-1.0/discussions/25

Thanks for the ping, @NielsRogge, and to take of this - I made a note in my internal doc not to forget about this!


Change Dependency so it can't put itself into an invalid state

The Behaviour is able to do whatever it wants to the Dependency. That's great for flexibility, but not great for consistency. Probably just throw exceptions in the setter if the operation would put the Dependency in an invalid state (i.e. multiple implementation mechanisms all being set at the same time)

Alternatively, the DI container can support multiple mechanisms at the same time. That means that it's not invalid. Also, that means that the default behaviour is not flexible enough - it should support either only a single implementation, or as many implementations as you want. That also means that there should be multiple Implementation Instances and Implementation Factories

This ticket relates to multiple implementations being added to a single dependency, which is a valid scenario. If a dependency should only have a single implementation, either use the standard dependency and lock it, or write a custom IDependency. Otherwise, the dependency class handles this scenario as of #34


Updates and deduplication

I discovered that some models were using ME updates that already existed in shared folders, so I added references to the shared folders and removed the updates from the model folders.
EliteBook Folio 9470m and Pro x2 612 G2 had two BIOS versions, I removed both and added a new version.
I also added support for HP ProBook 4x0 G4 and G5.
Now my working dir is clean and I am going on vacation.

Thanks for the effort, but I have to admit that I do not like the idea that a ZBook gets its ME update from a ProBook 6x0 G1. Of course, it is possible but is it also understandable by the operator? I doubt so.
For example, if I would update the ME files in the shared folder "HP EliteBook 8xx G1", I would not expect this to have an effect for a ZBook. I really see an benefit of this deduplication in terms of storage and update effort, but for any other operator not aware of the dependencies I fear this to cause confusion.
It would be perfectly fine if we could create one shared folder that is able to "group" those ME in a way an operator directly understands the dependencies.
Given that you are on your way to your vacation, I will most likely merge this PR but revert the changes for the ZBooks.
Enjoy your vacation!

I see the problem. What about renaming "HP ProBook 6x0 G1" to "HP ProBook 6x0 G1-HP ZBook 1x G2"?
This could work for some of the other models too, but I see that the compatibility of sp82486 in "HP ZBook 1x G4" should be taken a closer look at, according to the release notes it supports a lot of models, but it doesn't specify which generation.

I just create issue #72 to discuss this after your vacation.

@datagutten For your information, all HP ProBook 4x0 G4  devices were using a custom TPM-BIOS-Settings.txt file while the one in \Shared\HP ProBook 4x0 G4\TPM-BIOS-Settings.txt contained the same settings. I guess this was remnants of your tests, so I changed that that all use the shared file.


How to convert an existing AKS public cluster to a private cluster?

How to convert an existing AKS public cluster to a private cluster?

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

ID: 0b68f2c4-bb6c-11a2-6c61-8af4057a2438
Version Independent ID: e3498bed-1447-6841-8353-9f1b5d3dc8df
Content: Create a private Azure Kubernetes Service cluster - Azure Kubernetes Service
Content Source: articles/aks/private-clusters.md
Service: container-service
GitHub Login: @mlearned
Microsoft Alias: mlearned

@mtricolici Thank you for sharing your query! We are currently investigating and will get back to you shortly on this.

@mtricolici As mentioned in mentioned article under limitation converting an existing AKS cluster to private one is not supported:

You can indeed provide it as a feedback on our forum here.
Our Product Group are quite active on these forums and the post with highest number of upvotes is taken into consideration and worked upon.
Hope it helps!!!
Do let me know in case of any more queries.

thanks


Remove the word "Alpha" from the splash screen.

I think we can safely say rviz2 is no longer alpha.  This
change adds in the current version from the package.xml, though
this is likely to lag behind when a new release is made.  I'm
not quite sure how to improve that.
While we are in here, also switch from the "ROS 2.0" nomenclature
to just "ROS 2".
Signed-off-by: Chris Lalancette<EMAIL_ADDRESS>

@ros-pull-request-builder retest this please

Linux
Linux-aarch64
macOS
Windows

The test failures are all in CycloneDDS itself (so not related to this PR).  @ahcorde if you approve this, I can go ahead and merge it.  Thanks!

Thanks!  Merging.


Issue : Error Handling in Stripe Session Creation

Issue : Error Handling in Stripe Session Creation
Description
The error handling in the Stripe session creation process should be more descriptive to help debug issues more effectively.
Steps to Reproduce

Trigger an error during the Stripe session creation.
Observe the generic error message in the response.

Expected Result
The error message should be more descriptive and provide helpful debugging information.

Closing Remarks for Issue #25
Issue: Incorrect Transaction Update Method
Resolution:
The Prisma update method was corrected from prisma.transaction.update to prisma.transactions.update. This resolves errors encountered during transaction status updates.
Related Pull Request: #28


Can SE blocks be used for regression tasks?

Hi,@lishen-shirley
Can SE blocks be used for regression tasks? For example, hand posture estimation.

SE blocks can be regarded as a basic component for learning representations with convolutional network architectures. As we know, the module or the idea has been used in a wide range of visual tasks, such as classification, detection, segmentation, depth-estimation and super-resolution though we mainly evaluated it in classification tasks.


Proposal detail not being shown

The proposal 1 on Desmos is submitted and can be shown in the proposal page but it's showing undefined in the detail page.

Also should the url uses chain-id in the path instead of DSM?

Just want to add that also votes and deposits are not shown:

On BigDipper the data are shown properly:


Add closing functionality to Viceroy for Handles

This adds the ability for Viceroy to handle closing handles for
Response, Request, Body, and StreamingBody Handle types via the close
host calls that were added to the public ABI and internally for C@E
which has rolled out to the fleet. While this does not include any SDK
updates for the tests, I've tested this out with the new version of the
Rust SDK to make sure things work out correctly which helped find a bug
or with how I implemented it with Viceroy. With this we can still work
with old versions of the SDK and handle the new SDK as well.
Closes #64

No worries @cratelyn should be good now

I did a full squash so I can merge with just the one commit @cratelyn and so will need a ♻ ✔

❤ Thanks @cratelyn


BMIT.DataLibrary Incorporation Example

An idea on how you could utilize the MetadataDatabase library I'm working on to autoload mechdefs, vehicledefs (and in the future pilots,events,etc) with BTML.  Link to BMIT GitHub.  You only need the BMIT.DataLibrary project from my repo.  This is just a quick/dirty example, I'm sure there are better ways to incorporate but I hope you can get the basic idea of functionality from this example.
public static void Init()
{
...
//Not sure if this is the right path, but need full path to metadatadatabase.db file. using your path to mods as example to base it on.

var MDDPath = Path.GetFullPath(Path.Combine(Path.GetDirectoryName(VersionManifestUtilities.MANIFEST_FILEPATH), @"......\BattleTech_Data\StreamingAssets\MDD\MetaDataDatabase.db"));

// TODO: load mods in the correct order
using(var db = new BMIT.DataLibrary.MDData(MDDPath))
{
foreach (var modDef in modDefs)
 {
    LoadMod(modDef, db);
  }
}
....
LoadMod(ModDef moddef, BMIT.DataLibrary.MDData db)
...

/*
Not sure where to put this UpdateUnitDefs call yet - wherever you read in the mechdef,vehicledef,etc and actually use them. I see you read them into a JObject in InferIDFromFileAndType and I see you add them to potentialAdditions. When a potentialAddition becomes an actual addition you would need to read in the def.json file as a JObject and call db.UnitDefsUpdate.
*/

//Example - I know the mod structure is not quite this
foreach(var mechdefpath in mod.mechdefspaths)
{
    var jObj = Newtonsoft.Json.Linq.JObject.Parse(File.ReadAllText(mechdefpath ));
    db.UnitDefsUpdate(jObj, UnitType.Mech);
}

Potential Issues:
Once the MetadataDatabase.db has been updated with a def, that def must exist in the VersionManifest.CSV list (or get loaded by BTML someway).  If that def is removed, the MetadataDatabse.db must also have it's associated entries removed.  Failure to do this will cause infinite/hanging loading screens.  I will add def deletion functionality to the library, but it means the mod manager must be used to 'Uninstall' a mod, and not simply just delete it.  Alternatively, some sanity check could be run on inititalization that cleans the db of any def that isn't found in the associated json files.  Obviously removing a def from an active campaign will break it, if the player has the mech or the parts in his inventory or it's saved during a contract with one in play.

DB/Savegame management will be an important part of the project as a whole as it evolves. Mods should be able to be installed and uninstalled without much impact to the end user.
Regarding licensing, ModTek is licensed under the UNLICENSE, which means it's released to the public domain. That also means that any included code will have to licensed like that, so I'll probably use your project as a jumping off platform to how the DB works and what needs to be done, and write separate code that actually does it or you'll have to 'release' the code to me in a pull request that acknowledges that you're agreeing to the license.
Also, as an observation, I don't think it's a very good idea to write raw SQL into your code -- instead, I would look up documentation on how to use a library (preferably the one that the game uses to write to the DB) that does it for me. Again, I haven't worked on this particular problem at all, so it might ultimately be needed.

They are using Mono.Data.Sqlite, I'm using Microsoft.Data.Sqlite.  Either will work similarly.  If you check out the BattleTech.Data classes in Assembly_CSharp you'll see they are using SQL right in the code as well.  As far as I know that's the only way to work with sqlite in .Net but there could be a wrapper out there that I'm not aware of.  (Although even entity and such when you get to the lower layers you're still seeing sql, it's just a lot of it is autogenerated by the library for you).
I'm pretty open to licensing, I figured by putting it on GitHub it's open to the world anyway but I can look into setting a specific license for it.

Definitely have some kind of wrapper to escape data and mitigate SQL injection attacks. You definitely wouldn't want a mod to become a malware vector because BT assumes the database is safe to ingest naively.

ModTek will end up using the game MDD extension methods, as provided by the game's assembly.


Question regarding keyboard overview guide?

Dear @Vonng
A quick question. Is the keyboard overview guide of your own making or do you use a tool to generate this?
kind regards,

Well, it's hand made 🤣
Source file:  https://github.com/Vonng/Capslock/blob/master/images/keyboard.html

Thanks so much, exactly what I was looking for! 🙏


Consider simplifying the zero-copy SB API

Is your feature request related to a problem? Please describe.
After some refactoring in PR #1154 the whole CFE_SB_ZeroCopyHandle_t has become somewhat extraneous - there is no extra handle/descriptor for a zero copy buffer - they are all the same, and this simply refers to the same buffer descriptor now.
Describe the solution you'd like
The API can be simplified and this extra handle removed.  The buffer content pointer is good enough to reconstitute the descriptor  pointer (fixed offset).
Describe alternatives you've considered
Leave API as is (backward compatible, just a little more complex than it needs to be).
Additional context
This will affect public APIs - CFE_SB_ZeroCopyGetPtr, CFE_SB_ZeroCopyReleasePtr, CFE_SB_TransmitBuffer.  (CFE_SB_ZeroCopySend and CFE_SB_ZeroCopyPass are affected but already deprecated).
Requester Info
Joseph Hickey, Vantage Systems, Inc.

I'd like to fit this in Caelum if we can, lower priority than the rest but a goal.


run-android has started taking very long ( > 20 mins )

Please provide all the information requested. Issues that do not follow this format are likely to stall.
Description
I have been working on react-native since more than a year now. The run-android command didn't use to take more than a couple of minutes. However, when I ran the command for a new projects initiated with the init command it took more than 20 minutes ( didn't check when it finished so not sure of total time ) for it to complete.
Also surprisingly there is hardly any CPU usage as well as can be seen.
Initially I used to execute the react-native command via npx but then I installed the cli globally but the issue still continues ( v. 4.13.0 )
React Native version:
Run react-native info in your terminal and copy the results here.
Says error Unrecognized command "info".
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

Initiate new project via react-native init project
Run react-native run-android

Expected Results
Describe what you expected to happen.
It should have completed in a couple of minutes triggering CPU usage when ran
Snack, code example, screenshot, or link to a repository:

@chrisglein as I mentioned I am unable to run react-native info

What version of react-native do you believe you have? Your original bug report doesn't include the version. What is the output of the help command? I don't know how far back info goes, but it's been there a while. It sounds like you had some issues running react-native with npx and then shifted to a global install - that might be part of your problem?

Have you tried to run react-native info at the root of your project?


Fixed Issue #16 : Added a directory structure graphic in README.md

Perfect! Thanks a lot! 😄  👍  👍  🎉

Glad to help :smile: :tada:


Bluetooth connection instable with Android Outdoor Phones

Hello, i wrote an app that connects to an external ble device. It works pretty well on iPhones and common Android phones such as Samsung, Sony etc. but i'm having trouble with two somewhat exotic outdoor phones: Cubot KingKong (2018) and Blackview BV 6000. Connecting usually works but the routines device.discoverAllServicesAndCharacteristics() and device.writeCharacteristicWithResponseForService() are extremely slow and unstable. They work at most 1 out of 10 times. Do you have any ideas what could be the issue? I am using react-native-ble-plx 0.10.0

Please try connectivity and characteristic write with nRF Connect application if you can. See if it responds similarly.


Packed bed example

This PR adds a 3D packed bed test for the VANS equations with 10,000 particle.  The end time of the test was reduced drastically since in Debug mode the test always timed out.

The test is working fine, I checked it on my machine. I just think that the test should not write any outputs, and we should write some simulation information in the output file. By comparing this information, we would be sure that the test results are identical on different machines.

Yeah that's a great idea. What do you suggest in terms of term? Maybe we could add an additional post-processing tool that calculates pressure drop between two boundary ids and use that as the verification? what do you think @tonielgeitani

The test is working fine, I checked it on my machine. I just think that the test should not write any outputs, and we should write some simulation information in the output file. By comparing this information, we would be sure that the test results are identical on different machines.

Yeah that's a great idea. What do you suggest in terms of term? Maybe we could add an additional post-processing tool that calculates pressure drop between two boundary ids and use that as the verification? what do you think @tonielgeitani

Yes, bed pressure drop and average voidage in the packing region are good, in my opinion.

Yes of course. I agree. I will start working on the average voidage and the pressure drop

Very good work. I just have two small comments.
1, The test still writes one output
2, We should add the unit of the pressure drop after reporting the value


Advise named subjects, also;

Recommend short syntax when testing true or false- which do not really need
a description (overly verbose).

@gavinlaking, would it not be nicer to suggest using some of RSpec's magic matchers?
We could then have things like the following.


Support for ansible-vault

Feature Request
Is your feature request related to a problem? Please describe.
I have an issue when I need to store sensitive data within the confines of the Ansible operator.  At present, there isn't a means to do so using native Ansible features like ansible-vault.
Describe the solution you'd like
We use ansible-vault to encrypt secrets within the confines of an ansible playbook.  This is simply done using the ansible-vault command, pasting in a string to encrypt, and it returns a hash.  In order to access the secrets, the --ask-vault-pass option must be supplied to the ansible-playbook command.  A prompt is given asking for the vault password, and the password used to create it is used to reveal/decrypt the value.
There's also an option to have a file on the ansible host that contains the password, and this can be fed into the ansible-playbook command in lieu of the ask-vault-pass option.
With the current operator, there's not way, as far as I know, to have ansible run with an option to read a password file, or otherwise.  Even so, some mechanism to store the password on the image securely is needed.  One option perhaps would be to store the vault password as a k8s secret and looking it up with the ansible k8s module to create the password file, or build a way within the operator binary to look up the k8s secret.
One drawback with this approach is getting the vault password created in the first place.  Maybe something like bitnami-labs/sealed-secrets can be used here.  Overall perhaps use of sealed secrets addresses some of these challenges, however having a one-stop-shop of native ansible functionality within the confines of the operator makes things a bit more fluid.
My current use case is around storing usernames and passwords in a configuration file for an application, specifically Jetty.  The passwords differ across our data center environments, so having the power of group_vars or the like (without having to rely on an inventory) within ansible could be useful within an operator use case.  Therefore, this config file needs to be an Ansible template.  "The like" would be doing something like this to get namespace specific values, for example, our namespaces may be named solr-dev, solr-tst, solr-prd:
└── roles
    └── solr.provisioning
        ├── defaults
        │   └── main.yml
        ├── meta
        │   └── main.yml
        ├── tasks
        │   └── main.yml
        ├── templates
        │   ├── solr.yaml.j2
        │   └── zookeeper.yaml.j2
        └── vars
            ├── main.yml
            └── solr-dev.yml

- name: Include environment specific jetty variables
  include_vars: "{{ namespace }}.yml

Now, with all of that said, one of the challenges in my environment is the k8s admin not allowing a service account to create secrets.  If I could do that, then I could just set a bunch of facts and use those as vars to supply the credentials to a k8s secret that's simply stringData.  Our service accounts, at present, are allowed to perform verbs against any CRDs we've created within the platform.  Native CRs are more of less off limits since our service accounts are cluster scoped (service account lives in the namespace of the operator and our operators are cluster scoped).
Regardless, having the ability to use native ansible-vault as opposed to having to rely on k8s secrets (or in some cases in conjunction with k8s secrets) may make things a bit more flexible.

/remove-lifecycle stale
cc: @fabianvf

/lifecycle frozen

@fabianvf is willing to help anyone who wants to implement this.

@fabianvf I've never written a single piece of go.  I suppose that would be a prerequisite towards helping implement this?

@ktreese it wouldn't hurt, though if you're familiar enough with other programming languages I don't think it would be too hard. I was thinking of making this a more general feature by adding a command line flag to the operator-sdk exec-entrypoint and run --local subcommands for Ansible-based Operators that allowed a user to specify arbitrary CLI arguments that we pass through to ansible-runner. That would mostly just involve:

Adding the flag to the Ansible flag set here: https://github.com/operator-framework/operator-sdk/blob/master/pkg/ansible/flags/flag.go#L40 ,
Updating the Run function to make use of that flag https://github.com/operator-framework/operator-sdk/blob/master/pkg/ansible/run.go#L68
The above step would likely involve adding a field to store the flags to the Runner struct: https://github.com/operator-framework/operator-sdk/blob/master/pkg/ansible/runner/runner.go#L146
Making the cmdFunc interface and the methods that implement it accept and use the additional flag: https://github.com/operator-framework/operator-sdk/blob/master/pkg/ansible/runner/runner.go#L71-L99

And then of course testing/etc. If you did decide to take a stab at it I'd be happy to help, I'm fabianvf on the Kubernetes Slack and freenode.


Delete/Create playlist Crashed Game. (Muted/Pause Song Involved?)

Deleting a playlist Crashes the game for me.
To Reproduce
Steps to reproduce the behavior:
1: Create Playlist.
2: Add a song to it.
3: Delete it in the playlist.
4: Crash.
Update: Sadly, I misunderstood how it worked and I did something completely different to break it. Still trying to determine.
Expected behavior
To remove the song from the playlist and possibly remove the playlist all together since there are none in it.
Update: It has something to do with playlists itself. Deleting/Creating playlists.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Windows 64 Bit
Version 64 (Development Branch)

Additional context
Etterna0.64-git-0dfc498950 crash report (build 0dfc498950, 20181205 @ 23:08:26)
Crash reason: Access Violation
Unknown thread
ragesurface_load_png.cpp:23 Reading the png file.
ragesurface_load_png.cpp:23 Reading the png file.
ragesurface_load_png.cpp:23 Reading the png file.
ragesurface_load_png.cpp:23 Reading the png file.
ragesurface_load_png.cpp:127 Header only png about to be processed.
Thread: Main thread
ragefiledriverdirecthelpers.cpp:165 C:/Users/Jeremy/Desktop/etterna-source/etterna/Save/LocalProfiles/00000000/Etterna.xml
ragefiledriverdirecthelpers.cpp:230 C:/Users/Jeremy/Desktop/etterna-source/etterna/Save/LocalProfiles/00000000/Screenshots/*
ragefiledriverdirecthelpers.cpp:230 C:/Users/Jeremy/Desktop/etterna-source/etterna/Save/LocalProfiles/00000000/Screenshots/*
ragefiledriverdirecthelpers.cpp:165 C:/Users/Jeremy/Desktop/etterna-source/etterna/Save/LocalProfiles/00000000/Screenshots/newdir.temp.newdir
ragefiledriverdirecthelpers.cpp:230 C:/Users/Jeremy/Desktop/etterna-source/etterna/Save/LocalProfiles/00000000/Screenshots/*
Thread: Decode thread
ragesounddriver_generic_software.cpp:234 Processing the sound while buffers are available.
ragesounddriver_generic_software.cpp:234 Processing the sound while buffers are available.
ragesounddriver_generic_software.cpp:234 Processing the sound while buffers are available.
ragesounddriver_generic_software.cpp:234 Processing the sound while buffers are available.
ragesounddriver_generic_software.cpp:234 Processing the sound while buffers are available.
Thread: Mixer thread
Thread: Music thread
ragefiledriverdirecthelpers.cpp:230 C:/Users/Jeremy/Desktop/etterna-source/etterna/Themes/_fallback/*
ragefiledriverdirecthelpers.cpp:230 C:/Users/Jeremy/Desktop/etterna-source/etterna/Themes/*
ragefiledriverdirecthelpers.cpp:230 C:/Users/Jeremy/Desktop/etterna-source/etterna/Themes/_fallback/Sounds/*
ragefiledriverdirecthelpers.cpp:230 C:/Users/Jeremy/Desktop/etterna-source/etterna/Themes/_fallback/*
ragefiledriverdirecthelpers.cpp:230 C:/Users/Jeremy/Desktop/etterna-source/etterna/Themes/_fallback/Sounds/*
Thread: DirectInput thread
inputhandler_directinput.cpp:907
inputhandler_directinput.cpp:883
inputhandler_directinput.cpp:901
inputhandler_directinput.cpp:907
inputhandler_directinput.cpp:883
00a8bb54: Etterna!uWS::WebSocket<0>::send [00970000+de5d0+3d584]
00f1750a: Etterna!uWS::HttpSocket<0>::upgrade [00970000+46a770+13cd9a]
00a2d929: Etterna!uS::Socket::write [00970000+779c0+45f69]
00f682b5: Etterna!uWS::HttpSocket<0>::upgrade [00970000+46a770+18db45]
00ac8570: Etterna!uWS::WebSocket<0>::send [00970000+de5d0+79fa0]
00ba6ae6: Etterna!uWS::WebSocket<0>::send [00970000+de5d0+158516]
00d04a12: Etterna!uWS::WebSocket<0>::send [00970000+de5d0+2b6442]
775d35cc: ntdll!RtlRunOnceExecuteOnce [77580000+53590+3c]
00ac92a1: Etterna!uWS::WebSocket<0>::send [00970000+de5d0+7acd1]
00a33899: Etterna!uS::Socket::write [00970000+779c0+4bed9]
00a336fe: Etterna!uS::Socket::write [00970000+779c0+4bd3e]
00f1750a: Etterna!uWS::HttpSocket<0>::upgrade [00970000+46a770+13cd9a]
00a2d929: Etterna!uS::Socket::write [00970000+779c0+45f69]
00f682b5: Etterna!uWS::HttpSocket<0>::upgrade [00970000+46a770+18db45]
00ac8570: Etterna!uWS::WebSocket<0>::send [00970000+de5d0+79fa0]
00ac858d: Etterna!uWS::WebSocket<0>::send [00970000+de5d0+79fbd]
00ac8674: Etterna!uWS::WebSocket<0>::send [00970000+de5d0+7a0a4]
00d04a12: Etterna!uWS::WebSocket<0>::send [00970000+de5d0+2b6442]
00ac92a1: Etterna!uWS::WebSocket<0>::send [00970000+de5d0+7acd1]
00ad60e0: Etterna!uWS::WebSocket<0>::send [00970000+de5d0+87b10]
00a33899: Etterna!uS::Socket::write [00970000+779c0+4bed9]
00a336fe: Etterna!uS::Socket::write [00970000+779c0+4bd3e]
00f1750a: Etterna!uWS::HttpSocket<0>::upgrade [00970000+46a770+13cd9a]
00a2d929: Etterna!uS::Socket::write [00970000+779c0+45f69]
00f682b5: Etterna!uWS::HttpSocket<0>::upgrade [00970000+46a770+18db45]
00ac8570: Etterna!uWS::WebSocket<0>::send [00970000+de5d0+79fa0]
775d35cc: ntdll!RtlRunOnceExecuteOnce [77580000+53590+3c]
00ac92a1: Etterna!uWS::WebSocket<0>::send [00970000+de5d0+7acd1]
00a33899: Etterna!uS::Socket::write [00970000+779c0+4bed9]
00a336fe: Etterna!uS::Socket::write [00970000+779c0+4bd3e]
00f1750a: Etterna!uWS::HttpSocket<0>::upgrade [00970000+46a770+13cd9a]
00a2d929: Etterna!uS::Socket::write [00970000+779c0+45f69]
00f682b5: Etterna!uWS::HttpSocket<0>::upgrade [00970000+46a770+18db45]
00d5fb88: Etterna!uWS::WebSocket<0>::send [00970000+de5d0+3115b8]
00a7ce44: Etterna!uWS::WebSocket<0>::send [00970000+de5d0+2e874]
009edb6c: Etterna!uS::Socket::write [00970000+779c0+61ac]
00c7f352: Etterna!uWS::WebSocket<0>::send [00970000+de5d0+230d82]
009e6aaa: Etterna!uS::Node::`default constructor closure' [00970000+756a0+140a]
009e71ac: Etterna!uS::Socket::allocMessage [00970000+77070+13c]
009f1b8f: Etterna!uS::Socket::write [00970000+779c0+a1cf]
775b68ae: ntdll!LdrLoadDll [77580000+367e0+ce]
775c491a: ntdll!RtlAllocateHeap [77580000+447f0+12a]
00dabde6: Etterna!uWS::WebSocket<0>::send [00970000+de5d0+35d816]
00f6974e: Etterna!uWS::HttpSocket<0>::upgrade [00970000+46a770+18efde]
775e2ffa: ntdll!RtlValidSecurityDescriptor [77580000+62f10+ea]
Static log:
Etterna0.64-git-0dfc498950
Compiled 20181205 @ 23:08:26 (build 0dfc498950)
Log starting 2018-12-05 20:33:30
Verbosity: 1
Windows 6.2 (Win8) build 9200 []
WARNING: Main title or music file for '/AdditionalSongs/Otaku's Dream 9th Anime Mix/(porkypink) Make My Day!/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/Otaku's Dream 9th Anime Mix/(porkypink) Sekai wa okujou de miwataseta/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/Otaku's Dream 9th Anime Mix/(Shizuru) Nijiiro Sentimental/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/Ace Megapack/NEBULA GRASPER/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/StepmaniaFreak's Favorites/(Dj_Ossa) zl/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/Otakus Dream 1st Video Game Mix/[foamysminion] Bloody Angel/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/PARANOiA Collection/PARANOiA EViL -52 DECLiNE-/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/Ben Speirs' SPEIRMIX VS EuroVision/Wolves of the Sea/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/PARANOiA Collection/PARANOiA GENOCiDE/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/Community Keyboard Megapack - Volume 1/(pfx13AE) geeks' coup d'etat/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/Community Keyboard Megapack - Volume 2/(skauert) Nebula Grasper/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/Community Keyboard Megapack - Volume 4/(Exige) HOT PEPPERZ/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/Community Keyboard Megapack - Volume 4/(leonid)Youshou 02/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/VGMP 2/Stage 3 (Rebirth)/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/VGMP 2/The Decisive Battle (T0rajirou)/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/VGMP 4/Mario Theme (BT REMIX) (wv)/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/FFR Community Pack 4/(Patashu) Judgment Day/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/FFR Community Pack Spring 2012/Coward Killing Time (LegendaryHawk)/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/FFR Community Pack Spring 2012/Na o kansuru mono-tachi (Scylaax)/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/FFR Community Pack Spring 2012/The Big Crunch (Kommisar)/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/FFR Community Pack Summer 2012/Centipede (Rog)/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/FFR Community Pack Summer 2012/Watashi Wa Mizuki Desu (Rin-Dude)/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/Keyboard Mega Pack/Oi Punk/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/Keyboard Mega Pack/Paranoia Survivor MAX/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SmO/PFX13AE_geeks' coup d'etat/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/Keyboard Mega Pack/synciidx/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/Keyboard Mega Pack 1.5/PSM - t0rajir0u/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 4th/[Cho] Nosimyounghe [Hard R,K Mix] - Vocaloid/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 4th/[Cho] Sinsekai [Inst ver] - Vocaloid/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 4th/[songgot] SigSig(ssry ha2 mix) -beatmania/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/Keys of Flames/TKM (Loki)/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[akatsuki] Answer/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[akatsuki] NecroFantasia-LifeZero/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[ALICE_] Anti the infinity Holic/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[ALICE_] Boku-Boku beta/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/Kommisar Mix 2/(Kommisar) Nix-Tek/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[ALICE_] D2/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[ALICE_] Doll's Garden/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[ALICE_] OUT LAW - Reborn/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[ALICE_] plastic method/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[ALICE_] style/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[ALICE_] Sweet Dream/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[ca25nada] Polaris/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[ca25nada] Pure Ruby/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[CoolSlayer]  Evans-prototype-/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[CoolSlayer] 3y3s/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[CoolSlayer] Trust me/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Einar]in the Sky/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Einar]Rune/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Einar]Sky Garden/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Frandre_S] Anonymous Music/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Frandre_S] Azul/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Frandre_S] Midnight Dragon/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Frandre_S] Secret Cage/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[FreeStep] Faith is for the Transient People/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[FreeStep] fly high/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[FreeStep] Happy succession/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[FreeStep] i LOVE/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[FreeStep] mmmaster/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[FreeStep] morning person/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[FreeStep] my soul your beats/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[FreeStep] my soul your beats(ver.rock)/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[FreeStep] Oriental Dark Flight/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[FreeStep] ReaLoveReaLife/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[FreeStep] sunny starry carnival/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[FreeStep] Wishmaster/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[FreeStep] yamatonadesico education/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[G.S.S] dreamofwinds - love™/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[G.S.S] Gekkou/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[G.S.S] infina/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[G.S.S] Through the Fire and Flames/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[G.S.S]Crossroad of Sadness/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[G.S.S]Dazzlin Darlin -AKIBA KOUBOU mix-/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[G.S.S]Holic/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[G.S.S]MouUtaShikaKikoenai/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/DDREvolved's SOUNDS OF 2011/IT IS SO/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[G.S.S]Sonne/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[G.S.S]SuperSonic (Mr.Funky Remix)/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Golgo13(Sensationer)]i_Love/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Golgo13(Sensationer)]Memory_of_wind/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Golgo13(Sensationer)]sO mUCH iN LUV ~Melodic Hip Twisted Mix~/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Golgo13]Say that U/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[hunsoku] KIMONOPRINCESS/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[hunsoku] L.E.F. (Loud Electronic Ferocious)/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[hunsoku] Ojamajo Carnival!! (ParaPara Remix)/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/MAX/foon_period/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[hunsoku] Onna no Ko Otoko no Ko (TV Size)/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[hunsoku] ruka_momoi/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[hunsoku] someday/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[hunsoku] SUPER SAMURAI/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Jin] Moko Painter's Song/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Jin]T.R.E2/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Kardia]Blast from the Sun/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Kong]taboo tears you up/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[kooh] 3y3s_L/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[kooh] Memory_of_Beach_Remix/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[kooh] Sweet_Shining_Shooting_Star/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[leonid] Sonne/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[md]never no astray/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[md]Strawberry lemonade/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[melon&leeonid] GIGA BREAK/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[melon] GO! GO! MANIAC/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[melon] NEXT ARCADIA/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[melon] Real Over Drive/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[moon's]Native Faith/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[moon's]Rebuked Inada's Princess/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[moon's]Yokai ga Sumu Yama - Life in the Mountain/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Nibac]pippi girl/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[otogitune] BlythE ExtenD/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[otogitune] Extreme Z4/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[otogitune] futurism -UPPERBRAZE MIX-/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[otogitune] La notti bianche/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[otogitune] Legend of Seeker/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[otogitune] OblivioN (electroshock mix)/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[route]Fire Storm/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Saymun] Hina Choco Dark Matter/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[songgot]gengaozo/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[tjddydrl] otenbakoimusume/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[tjddydrl]Illusinox of Deep Below Intelligetion/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[tjddydrl]YOU (RE-FINAL EDIT)/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Warwolf]FUWATANITY/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Yume] Anisakis/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Yume] Atsuki Kettoshatachi -Billy Remix-/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Yume] Chaotic Crimson Of Pandora/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Yume] Dekirukanatte Hoshimittsu/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Yume] HIGH SCHOOL OF THE DEAD/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Yume] Jewelry/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Yume] Libera me/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Yume] MAX LOVE/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Yume] My Soul, Your Beats!/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Yume] Sakure Sakura Saku ~Ano Hi Kimi wo Matsu Sora to Onaji~/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Yume] Second Heaven/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Yume] Someone Else/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Yume] true love/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Yume] Yumemiboshi Boom! Boom!/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[Yume]_NO,_Thank_You!/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 5th/[ZZibu] Pure Pure Heart(tv size)/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/Hard Songs Megapack Volume 1/Beast and the Harlot/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/MAX/Mix of the MaxXes/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/Hard Songs Megapack Volume 11/Animalove/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/Hard Songs Megapack Volume 11/SpaceSpagetti IcyWorld/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/MomoSpark's Fucking Songs Pack/Quasar/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 8th/[10Dollar] - Another Day/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 8th/[10Dollar] - Blade/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 8th/[10Dollar] - Compressed eyes/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 8th/[10Dollar] - ELPIS/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 8th/[10Dollar] - Evangelize (blurry images)/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 8th/[10Dollar] - Factory/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 8th/[10Dollar] - Flowers/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 8th/[10Dollar] - Kamikaze Remix/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 8th/[10Dollar] - Memories of Sky/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 8th/[10Dollar] - Soukyuu sukaisukureipa/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 8th/[10Dollar] - Zirkfied/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 8th/[75] - Another Alien World/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 8th/[Areicia] - 2D Dream Fever/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 8th/[Areicia] - Chikyuusaigo no Kokuhaku wo/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 8th/[Areicia] - Chikyuusaigo no Kokuhaku wo(Full)/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
WARNING: Main title or music file for '/AdditionalSongs/SMOC 8th/[Areicia] - Colorful(Magibeat Remix)/' came up blank, forced to fall back on TidyUpData to fix title and paths.  Do not use # or ; in a song title.
Staticlog limit reached
Players joined: P1
Top Screen: ScreenSelectMusic
Current renderer: Direct3D
Partial log:
55:54.466: not pausing a sound because it's not playing
56:26.103: MusicWheel::Select()
56:26.103: WheelBase::Select()
56:28.630: Format jpg failed: Not a JPEG file: starts with 0x89 0x50
56:28.631: Format bmp failed: not a BMP
56:28.631: Format gif failed: not a GIF file
56:28.631: Format jpeg failed: Not a JPEG file: starts with 0x89 0x50
56:28.633: Graphic file "/AdditionalSongs/ov1_simfiles2/owenviau1.jpg" is really png
57:50.010: Saving Etterna Profile to: /Save/LocalProfiles/00000000/
57:50.099: c:\users\jeremy\desktop\etterna-source\etterna\src\ragefiledriverdirect.cpp:167: remove 'C:/Users/Jeremy/Desktop/etterna-source/etterna/Save/LocalProfiles/00000000/Screenshots/newdir.temp.newdir'
-- End of report

I seemed to have misunderstood the playlist thing. I seemed to have done something else to break it. Not sure how exactly. It has something to do with right clicking/muting current song/chart and playlist.

Have you figured out the steps to reproduce this? I'll try to crash in debug in the weekend, if i manage to repro i might get it fixed (If not I'll share where it's crashing here or in #development in the EO discord so someone else can look at it)

Sadly, I have not. It's such a strange event to cause it. I mentioned notes on the general idea how to do it but not exact sorry.

Crash by deleting "Favorites" playlist from video in issue #428 - crashinfo.txt

Should be fixed by 7f0b4a6b27a74ffb69245572a59c1acea06b9b0f


how to pass variables to view dynamically?

Hi,
I want to pass some specific parameters(such as static base url) to all the views. After searching apis, I find that only the method yii\web\View::beforeRender can meet my requirement. I use $this->params[key] = value in the beforeRender to pass values to all view. But the passed variables can only be accessed in the form of $this->params[key].
I want the passed variables can be available in the direct form: $key. I notice that the parameters of beforeRender is $viewFile and $params.  The second parameter $params is the local variables available among view files. However $params is declared as passed by value, so I can't use $params[key]=value to add variables dynamically.
Is there another api which can meet my need? Many thanks!

you can not

Correct. There's no such feature. What's your use case?

If you need a static variable in all your views you can extend yii\web\view

But the passed variables can only be accessed in the form of $this->params[key].
I want the passed variables can be available in the direct form: $key.

why do you need it this way? You can use http://php.net/manual/en/function.extract.php to turn params into variables.

For example, the base url of static files should passed to all the view. The view files are written in Smarty. I just want all the passed parameters are the same for the front end. I know there is an api called View::setVar in the Phalcon framework. You can always use it to pass variables, and the passed variables are the same with call render

I still do not see why $this->params does not work, you can even configure it in the application config...

The problem is not $this->params does not work(actually it works well in my project). The problem is that front end must use {$this->params.key} to get the value in the smarty syntax and it's weird for the front end.
What I want is that is there an approach to pass variables to the view just like passed in the View::render method?

How I can understand you have a few variables that you need in all your views. And therefore I would extend the the yiew class with all your needed variables and than you can set them in your controller or view and use them in your view with $this->variable

I wish these variables can be added or removed dynamically in the configure file, rather than they are property of some class...
While it's ok that view class does not support this feature...

I don't think we're going to support it. That's not really common request and I doubt it will be used often.

To solve this i have extended base/Controller:
namespace common\masters;
use Yii;
use yii\web\Controller;
class CommonController extends Controller
{
private $arViewVars = [];
public function init()
{
//echo "CommonController .init() 1.0.0 Running...";
parent::init();
}//init
protected function addToView($sVarName,$mxVarVal)
{
    $this->arViewVars[$sVarName] = $mxVarVal;
}//addToView

protected function render($view,$params = array())
{
    $params = array_merge($this->arViewVars,$params);
    return parent::render($view,$params);
}//render

}CommonController
all my controllers extend my CommonController:
//@file: \frontend\controllers\SiteController.php 1.0.0
use common\masters\CommonController;
class SiteController extends CommonController
{
public function init()
{
//echo "SiteController .init() 1.0.0 Running...";
parent::init();
}//init
public function index()
{
    $sVar = "hello world";
    $this->addToView("myVar",$sVar);
    return $this->render("view_index");
}//init

}//SiteController
i hope it helps

How about this
namespace app\classes;

class View extends \yii\web\View
{
    public $localVars = [];
    public function renderFile($viewFile, $params = [], $context = null)
    {
        if(!empty($this->localVars)){
            $params = array_merge($this->localVars, $params);
        }
        parent::renderFile($viewFile, $params, $context);
    }
}

Then in config
'components' => [
    'view' => [
        'class' => 'app\classes\View',
        'localVars' => [
            'foo' => 'bar',
            'm_id' => 3426,
        ]
    ]
]


onHttpCallResponse in Root Context getting blocked till after onStart of other VMs

Problem Statement
We are building a Wasm based C++ Envoy filter using proxy-wasm-cpp-sdk that needs to make an external HTTP call before the stream context starts. However we are running into some issues (described below) when there is a delayed response from the server. We are running the setup in Istio 1.5.5.
Current Implementation
In order to ensure that the data gets populated prior to servicing requests our plan was to setup a singleton Wasm VM which does the following in its onStart() function:

Makes an httpCall to the external server
Sets the shared data with http response json value

We then have the non singleton VMs which execute the following logic in their onStart() function:

Wait for the shared data to be present for upto 10 secs
Read the shared data value and load it into memory

Test case

Set the Envoy worker thread concurrency value to 2
Add a delay of 5 seconds to the response from the HTTP external server

Expected Behavior

1 BaseVM executing the singleton wasm module
2 Thread-Local VMs executing the filter wasm module
In RootContext onStart() function Singleton VM fetches the data and writes to the shared buffer.
In RootContext onStart() Thread-local VMs read the data from the buffer and keep it in memory.
Thread-Local VMs continue the stream context based execution.

Observed behavior

1 Base VM executing the singleton wasm module appearing to be part of the main Envoy thread
1 Base VM and 1 Thread-Local VM executing the filter wasm module both appearing to be part of the same main Envoy thread
2 Thread-Local VMs executing the filter wasm module appearing to be part of the Envoy worker threads
The Base VM and Thread-Local VM part of the main worker thread are unable to read the shared data and fail in their onStart()
The onHttpCallResponse fn gets called after the failure of the VMs in the main worker thread
The 2 thread local VMs are able to then read from the shared data
The Base VMs are not invoked when request are made to the envoy proxy

Based on the logs (as shown below) it seems as if the onStart functions of the VMs booted as part of the main Envoy thread need to complete before the onHttpCallResponse can be processed. This occurs only in the case of the external HTTP server taking a longer time to respond.
Questions

Is this the correct approach in order to achieve our objective?
What is the difference between Base VM and Thread-local VM?
Why are there Base VMs created in addition to the Thread-local VMs for the filter wasm module that is meant to be run only per worker thread?
From within a VM is it possible to identify if the given VM is a Base or a thread local VM?

Log Output

[Envoy (Epoch 0)] [2020-08-03 21:10:21.114][19][debug][wasm] [bazel-out/k8-opt/bin/external/envoy/source/extensions/common/wasm/_virtual_includes/wasm_vm_base/extensions/common/wasm/wasm_vm_base.h:38] WasmVm created envoy.wasm.runtime.v8 now active
[Envoy (Epoch 0)] [2020-08-03 21:10:21.114][19][debug][wasm] [external/envoy/source/extensions/common/wasm/wasm.cc:121] Base Wasm created 1 now active
[Envoy (Epoch 0)] [2020-08-03 21:10:21.274][19][warning][wasm] [external/envoy/source/extensions/common/wasm/context.cc:1092] wasm log my_filter my_filter: secret fetch httpCall was successful
...
[Envoy (Epoch 0)] [2020-08-03 21:10:22.842][19][debug][config] [external/envoy/source/extensions/filters/network/http_connection_manager/config.cc:420]       name: envoy.filters.http.wasm
   "runtime": "envoy.wasm.runtime.v8",
     "filename": "/var/local/lib/wasm-filters/my_filter.wasm"
[Envoy (Epoch 0)] [2020-08-03 21:10:22.845][19][debug][wasm] [bazel-out/k8-opt/bin/external/envoy/source/extensions/common/wasm/_virtual_includes/wasm_vm_base/extensions/common/wasm/wasm_vm_base.h:38] WasmVm created envoy.wasm.runtime.v8 now active
[Envoy (Epoch 0)] [2020-08-03 21:10:22.845][19][debug][wasm] [external/envoy/source/extensions/common/wasm/wasm.cc:121] Base Wasm created 6 now active
[Envoy (Epoch 0)] [2020-08-03 21:10:22.932][19][debug][wasm] [external/envoy/source/extensions/common/wasm/context.cc:1086] wasm log my_filter my_filter: Sleeping for 1 second...
[Envoy (Epoch 0)] [2020-08-03 21:10:23.981][19][debug][wasm] [external/envoy/source/extensions/common/wasm/context.cc:1086] wasm log my_filter my_filter: Sleeping for 1 second...
...
[external/envoy/source/extensions/common/wasm/context.cc:1086] wasm log my_filter my_filter: Sleeping for 1 second...
[Envoy (Epoch 0)] [2020-08-03 21:10:33.423][19][debug][wasm] [external/envoy/source/extensions/common/wasm/context.cc:1086] wasm log my_filter my_filter: Getting shared data secret failed
[Envoy (Epoch 0)] [2020-08-03 21:10:33.423][19][debug][wasm] [bazel-out/k8-opt/bin/external/envoy/source/extensions/common/wasm/_virtual_includes/wasm_vm_base/extensions/common/wasm/wasm_vm_base.h:38] WasmVm created envoy.wasm.runtime.v8 now active
[Envoy (Epoch 0)] [2020-08-03 21:10:33.444][19][debug][wasm] [external/envoy/source/extensions/common/wasm/wasm.cc:285] Thread-Local Wasm created 7 now active
[Envoy (Epoch 0)] [2020-08-03 21:10:33.446][19][debug][wasm] [external/envoy/source/extensions/common/wasm/context.cc:1086] wasm log my_filter my_filter: Sleeping for 1 second...
...
[Envoy (Epoch 0)] [2020-08-03 21:10:42.884][19][debug][wasm] [external/envoy/source/extensions/common/wasm/context.cc:1086] wasm log my_filter my_filter: Sleeping for 1 second...

[Envoy (Epoch 0)] [2020-08-03 21:10:44.011][31][debug][wasm] [bazel-out/k8-opt/bin/external/envoy/source/extensions/common/wasm/_virtual_includes/wasm_vm_base/extensions/common/wasm/wasm_vm_base.h:38] WasmVm created envoy.wasm.runtime.v8 now active
[Envoy (Epoch 0)] [2020-08-03 21:10:44.100][31][debug][wasm] [external/envoy/source/extensions/common/wasm/wasm.cc:285] Thread-Local Wasm created 13 now active
[Envoy (Epoch 0)] [2020-08-03 21:10:44.105][31][debug][wasm] [external/envoy/source/extensions/common/wasm/context.cc:1086] wasm log my_filter my_filter: Secret json parsed successfully
[Envoy (Epoch 0)] [2020-08-03 21:10:44.105][31][debug][wasm] [external/envoy/source/extensions/common/wasm/context.cc:1086] wasm log my_filter my_filter: Converting shared data to secret json was successful

cc @jplevyak @PiotrSikora

Would it be possible to attach a (perhaps cut down) version of your configuration and/or plugin?
It would help ensure that any changes fix what you are seeing.

@jplevyak Sure, here is the code we're using:
Singleton filter: https://gist.github.com/mcieplak/b0d11d420bac4a32ca930b16e888b976
Non singleton filter: https://gist.github.com/mcieplak/b3e0352e534fa763fa7be712011b7aef

@jplevyak @kyessenov
We should not busy wait in the main thread, othewise we are not giving the other thread to finish its work.
I am wondering if the non-singleton filter should try to read the the shared data in the stream context, not the main context.
If it cannot read the data, the filter should treat it like NOOP, or propagation delay. It will only have to read it once and store it in the root context.

You cannot hard loop in Envoy under any circumstances.  Envoy is an event driven system and each worker thread is shared with many many connections.  This is not a Wasm problem.  Please revise your code and if you have problems open a new issue.


No screenshots?

No screenshots??

Gnome and macOS have native screenshot facilities. It would be redundant to add that capabiloty to Ghostty. If you are just looking for examples of Ghostty "in action" there are many examples in the Discord server.

There is a website issue already tracking adding a showcase section to the website.


do you know from where to get data for https://boosters.pro/championship/data_fusion/overview

do you know from where to get data for https://boosters.pro/championship/data_fusion/overview

A proper way to get competition data is to contact platform admins directly

But how  find them
On Wed, Jul 13, 2022, 1:28 AM Dmitry Dremov @.***>
wrote:

Closed #1 https://github.com/dremovd/data-fusion-2-baseline/issues/1 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/dremovd/data-fusion-2-baseline/issues/1#event-6982872780,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACXFSRYAW2Q2FZKVGR5RJ43VTZHXBANCNFSM5YHEDG7Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

This competition is from the boosters.pro platform.
They have an official telegram chat https://t.me/boosters
I also asked about their policy in general - if the dataset is no longer available on the platform it means that dataset owner asked them to delete the dataset after competition end, so there is no "right" way to get it.
The only chance is to ask several participants to share the dataset privately until somebody will agree.
I prefer to comply with competitors rules.


Module for Azure CosmosDb

Publish a module to Terraform Registry that helps to deploy Azure CosmosDb account.
Related Terraform resource:

https://www.terraform.io/docs/providers/azurerm/r/cosmosdb_account.html

i would love to help on this one.

we should also look at the rest of the control plane, like creating databases, collections, setting throughput, setting up geo-replication, multi-master etc.

That will be definitely awesome to get all those features indeed. We need to check what is available in the Terraform ressource, and also in the Azure GO SDK. Maybe we will have to improve the TF resource first.

I see from the provider that they have a resource for Account and for Database but cannot see anything for Collection ........
Do we need to add this first?

I see that there is a resource for a mongo db collection, but it seems there is no for document db collection yes. The Azure Go SDK seems to define what's needed to work with collection here. I am not a CosmosDb expert, but might be interesting to explore this way and add support for collection if possible.
Maybe you can do it in two times:

working on a basic module for account + db
extend the provider and add the new features in the module

What do you think?

Sure, i can start with a module for acct + db. And then, time permitting, look to extend the provider.
ARM support for database and collection is very new. I think it was only announced recently at Build.


Bump numpy 1.12.4 for support apple M1 chip

I have run PythonInterpreterTest class successful.
I want to bump beam in PyFlink, but pemja depends on numpy==1.19.5.
The conflict is caused by:
   apache-flink 1.15.dev0 depends on numpy>=1.21.4
   apache-beam 2.36.0 depends on numpy<1.22.0 and >=1.14.3
   pemja 0.1.2 depends on numpy==1.19.5

@maver1ck Thanks for the reminder. I have release pemja 0.1.5 including this patch.


Update srs-eng files

What's in this PR:

add/update srseng test db
add altlable file for srseng
updated .hfstol files
add new layout files needed for new test data

Codecov Report

Merging #965 (699078f) into main (61a04c3) will decrease coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #965      +/-   ##
==========================================
- Coverage   79.59%   79.56%   -0.03%
==========================================
  Files         136      136
  Lines        4640     4640
  Branches      610      610
==========================================
- Hits         3693     3692       -1
  Misses        820      820
- Partials      127      128       +1

Impacted Files
Coverage Δ

src/CreeDictionary/CreeDictionary/views.py
78.70% <0.00%> (-0.93%)
:arrow_down:

Continue to review full report at Codecov.

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


chore: adding container widget to wds for user testing

Pull Request Template
Use this template to quickly create a well written pull request. Delete all quotes before creating the pull request.

Description
In this PR, we are adding container widget into wds widgets set, so that it is available to build the sample app for user testing anvil.
note: Container widget might be remove altogether if it has no purpose once zones is implemented.
PR fixes following issue(s)
Fixes # (issue number)

if no issue exists, please create an issue and ask the maintainers about this first

Media

A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video

Type of change

Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
Chore (housekeeping or task changes that don't impact user perception)
This change requires a documentation update

Testing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

[ ] Manual
[ ] JUnit
[ ] Jest
[ ] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/ok-to-test


EPIC: Dependency Handling for a distributed project setup

Each project / repository inside the open component model setup has dependencies on other modules which are specified in go.mod files. These dependencies can be categorized into 2 categories and each category has its caveats.

Common Dependency Handling: There are a few dependencies which are present in all projects, and we refer to specific versions of a dependency. This created 2 problems:

Using a specific old version: Anyone trying to develop has to revert the dependencies to older version. Due to the indirect dependency, it might require the correction in ~ 9 projects and all of the projects might not even be on the same version.

Using different dependency versions for different project. Ideally, they all should be on the same version  to get the same functionality and to avoid detecting failing e2e, etc. tests. Eg: ocm-controller versions

https://github.com/open-component-model/mpas-product

Proposed Solutions:

Have a github actions gather common dependencies from all projects and prevent merging if common dependencies are not on the same/latest version. The versions which should be used should be compiled by the action and stored in a file so that someone who start developing knows the new version they can use locally while developing rather than waiting for the PR to fail and correct before merge

ocm cli dependency: The ocm-cli is referred by all projects and apart from the above problem of using different versions, when ever there are changes(refactoring/features) in the CLI, the failures in other projects should be identified and fixed/reported. The failure should not be a landmine for someone starting a new ticket and the failure-fix should be part of the already identified work done on the cli

Refactoring: If changes are compatible or not, the only solution to detect breaking changes is to download all projects locally, dependencies in the projects need to refer to local ocm, and then run the tests. It is a task in itself

New Feature: There should be a version description/commit indicating the last stable ocm-cli compatible with all projects or use the approach of problem 1
Proposed Solution:

Go recommends modularizing projects and having a single go.mod file. But since each project has to be able to run in bundles {mpas, mpas-prod, mpas-proj, git-cont, replication-cont, ocm-contr, ocm-cli}, {ocm-cli, ocm-controller, ocm-e2e-f}, {ocm-cli} modularization will not work.

Following a non-go approach, where we only commit go.mod file and NOT the go.sum(.gitignore) file. Then improve the central CI pipeline to make it a true CI:

Consume a linux Golden image from the multi-cloud team, create a docker-file and install all required dependencies to be able to run go mod tidy and go build
Use sap-piper-library or any container-execution functionality to run go commands(go mod tidy, go build) in the container
The go.sum is generated for the project in the pipeline and commited to git
When there is any change in the cli, the go.mod for each project is edited to use the latest ocm-cli, and the pipeline will download the dependencies and add the go.sum and that will trigger the e2e,etc. tests for each project in the corressponding PRs and we would be able to see the failures at a central place. This is true CI
If fix is small then fix it, if complicated, create follow up ticket with the logs from the pipeline

For 2. also see open-component-model/ocm-project#121

Tasks:

[ ] #34
[ ] #35

closed this task, #34 and #35 are the follow ups


When I try to save edits to automations in the webbrowser I get a 404. (file is named automations.yaml)

Home Assistant release (hass --version):
0.45.1
Python release (python3 --version):
3.4.2
Component/platform:
haspbian
Description of problem:
When I try to save something to the home automation, i get a 404, http://hassbian.local:8123/api/config/automation/config/1496087113456 404 (Not Found). I have named the file automations.yaml and included it in my configuration.yaml file. the chmod of automations.yaml is -rwxrwxrwx.  I can see my automations, but when I click on them I get another 404, http://hassbian.local:8123/api/config/automation/config/playP3 404 (Not Found), also the automations work as expected.
Expected:
To be able to save and edit my automations
Problem-relevant configuration.yaml entries and steps to reproduce:
automations.yaml
- id: playP3
  alias: Play Rain Lullaby
  trigger:
    platform: state
    entity_id: input_select.lullaby
    to: "Rain"

  action:
    service: media_player.play_media
    data:
      entity_id: media_player.koket
      media_content_id: http://http-live.sr.se/p3-mp3-192
      media_content_type: audio/mp3
# If you select "None, turn the Chromecast off
- id: stopP3
  alias: Stop the Lullaby
  trigger:
    platform: state
    entity_id: input_select.lullaby
    to: "None"

  action:
    service: media_player.turn_off
    data:
      entity_id: media_player.koket

configuration.yaml
automation: !include automations.yaml

Where is automations.yaml located?

default hasspbianfolder/same folder as configuraition.yaml
/home/homeassistant/.homeassistant/automations.yaml

Like I said in #7707: I think it would be a nice addition if the automations editor checks whether it can load/read/write automations at all, and shows an error with instructions on forehand.
Now it's just a matter of trial and error to see whether the API returns something useful and the front-end can be rendered.

@corneyl you got it working? do you see what could be wrong with my setup? Atleast intentionally I'm using the default, that's what makes it weird that it's not working...

Yes, I got it working, had used the wrong file name automation.yaml. Saving is also working.

I think, maybe my system cannot create files, I have had some problems with my database and someone said you could remove it so that home-assistant created a new one. It has not, even tried a reboot.

I'm running chrome ni osx might be worth mentioning, I get the error:
Currently Chrome is the only supported browser.
even though i'm using chrome, not sure if that is intended.

@kristoffernolgren I have the exact same problem. Can also see the automations on the frontend but clicking them or attempting to add a new one yields a 404.
Using Docker by the way.

Some people (me included) are having an issue where the save button doesn't do anything at all.  No 404's, no nothing.

The 404 is hidden in the javascript console.
For me, this was resolved by adding the 'config' component to my configuration.yaml, per the suggestion in https://github.com/home-assistant/home-assistant/issues/8334#issuecomment-313439603
This issue could be closed, though ideally, we should update the doco to provide more guidance on dependencies for the automation editor.


chore: use ctx parameter in cmdInfo

cmdInfo has ctx as parameter, so I believe it would be more reasonable to use context parameter rather than client context when logging

Thanks


Feature request: Sample::as_f32

I am making a library for audio creation and want to add support for (floating point) audio buffers from WAV files. In order to make this work, I would need the ability to convert an arbitrary sample into a floating point value.
This wouldn't be a direct cast, but rather an appropriate rescaling. For instance,
fn as_f32(x: i8) -> f32 {
    x as f32 / i8::MAX as f32
}

or perhaps something slightly more clever that clamps the range between -1.0 and 1.0 exactly.
The reason I'm making this an issue rather than a direct PR is that this might create some confusion with the (unused?) Sample::as_i16. That one is a direct cast, rather than a conversion, and it would be odd having different behavior for these two methods. Maybe into_f32 could be a better name?

This also came up here: https://github.com/ruuda/hound/issues/57#issuecomment-1214424166. My conclusion is that there is no way to implement this that is both obvious and consistent across all types, so I would like to leave it out of Hound; you can normalize the samples wherever you consume them. It’s slightly more code, but at least the behavior is explicit.

Alright, that's understandable. Thank you!


Compatibility Tester randomly passes/fails

Hello there,
I'm trying to implement receiver.js into our player code. However, tests on compatibility tester are passing or failing randomly, against same code.
Any thought much appreciated, thanks.

Generally this is a timing issue, if the embed doesn't respond fast enough the test will fail.
You can see the tests here: https://github.com/embedly/player.js/blob/gh-pages/scripts/test.js#L163

Hey, thanks for super prompt answer. Actually it always passes ready, and if it pass addEventListener then passes everything too, but if it fails on addEventListener then fails obviously. Still not sure actual reason but
receiver.emit('timeupdate', { data: {
  seconds: audio.currentTime,
  duration: audio.duration
}})

returns false on failed attempts. I saw that if receiver.eventListeners hasn't it's own property or listener it returns false but no idea why it has not related listeners.

You might be sending timeupdate events too quickly. They should 1 every 200-300 milliseconds, so if you are pushing a ton the count will be off here:
https://github.com/embedly/player.js/blob/gh-pages/scripts/test.js#L183

Hmm, ok I have tried but still failing sometimes, however, all methods and events working actually if I try manually and that's good enough for me, closing issue. Thank you again.


[STREAMPIPES-321] Updated flinkruntime jobstatus checks to check actual running status

Purpose
If the flink job is not found, then it means that it is cancelled or failed. So streampipes should continue to stop this PE from its in-memory storage and mark the whole pipeline as Stopped.
Approach
Changed in FlinkRuntime.java. Modified method discardRuntime() to also check if the job is present and its state is running then cancel the job, else if job is present but bot running then don't throw exception.
Also change method getJobStatus() method to return job with any status.
Remarks
Fixes: https://issues.apache.org/jira/projects/STREAMPIPES/issues/STREAMPIPES-321

Hi @mfaizanse, thanks again for your PR. I just checked out your PR and it works as aspected.