[cpp-windows] Lime randomly fails to preload the default asset library

This seems to happen randomly when I try building for windows, where the code compiles but when the application starts it gives the follwing error:

Lime Version: 8.1.1
Hxcpp Version: 4.3.2
Steps to reproduce:
It doesn't happen consistently but for any given lime project if it does happen once then it happens on every re-compilation (even if you run lime clean windows and re-compile)
I used the command lime create HelloWorld <my-test-project-name> to create the project, and the code I used is in the zip file below:
Testing3DStuff2.zip
Upon building and running with lime test windows -debug, it gives me the above error.
Additionally, if I move the generated "bin/" directory to a different location, then the executable works without any problems, which was pretty weird.
Video showcasing the compilation:
https://github.com/openfl/lime/assets/83609901/cc6f344b-c7b3-4d72-ba19-21f5d4d642a5
This only seems to happen when compiling to windows, I tested with html5 and it worked perfectly fine

I did a bit of digging around in the source code and it looks like the path to the manifest/default.json file seems to be mysteriously getting shortened by the SDL_GetBasePath function
(It should be C:\Users\......\Export\windows\bin\, but SDL_GetBasePath returned C:\Users\......\Export\windows\.
This seems to be related to https://github.com/libsdl-org/SDL/issues/4439 (this also explains why my exe file suddenly worked when I moved it up one directory)
This issue was fixed by https://github.com/libsdl-org/SDL/pull/4437 . But it looks like the SDL submodule that lime uses is from before that PR was merged.
So I'm guessing a submodule update should fix this issue.

Good to know.
Can you try with the 8.2.0-Dev branch? That uses more recent versions of the submodules.

That seems to fix the issue, thanks!
But now when after I compile I get this on the console:
Called from lime/_internal/backend/native/NativeCFFI.hx line 686
Called from lime/system/CFFI.hx line 111
Called from C:\HaxeToolkit\haxe\std/neko/Lib.hx line 35
Uncaught exception - load.c(357) : Primitive not found : ./lime@lime_joystick_get_num_trackballs(1)
Called from lime/_internal/backend/native/NativeCFFI.hx line 686
Called from lime/system/CFFI.hx line 111
Called from C:\HaxeToolkit\haxe\std/neko/Lib.hx line 35
Uncaught exception - load.c(357) : Primitive not found : ./lime@lime_joystick_get_num_trackballs(1)
Called from lime/_internal/backend/native/NativeCFFI.hx line 686
Called from lime/system/CFFI.hx line 111
Called from C:\HaxeToolkit\haxe\std/neko/Lib.hx line 35
Uncaught exception - load.c(357) : Primitive not found : ./lime@lime_joystick_get_num_trackballs(1)
Called from lime/_internal/backend/native/NativeCFFI.hx line 686
Called from lime/system/CFFI.hx line 111
Called from C:\HaxeToolkit\haxe\std/neko/Lib.hx line 35
Uncaught exception - load.c(357) : Primitive not found : ./lime@lime_joystick_get_num_trackballs(1)
Called from lime/_internal/backend/native/NativeCFFI.hx line 686
Called from lime/system/CFFI.hx line 111
Called from C:\HaxeToolkit\haxe\std/neko/Lib.hx line 35
Uncaught exception - load.c(357) : Primitive not found : ./lime@lime_joystick_get_num_trackballs(1)
Called from lime/_internal/backend/native/NativeCFFI.hx line 686
Called from lime/system/CFFI.hx line 111
Called from C:\HaxeToolkit\haxe\std/neko/Lib.hx line 35
Uncaught exception - load.c(357) : Primitive not found : ./lime@lime_joystick_get_num_trackballs(1)
Called from lime/_internal/backend/native/NativeCFFI.hx line 686
Called from lime/system/CFFI.hx line 111
Called from C:\HaxeToolkit\haxe\std/neko/Lib.hx line 35
Uncaught exception - load.c(357) : Primitive not found : ./lime@lime_joystick_get_num_trackballs(1)
Called from lime/_internal/backend/native/NativeCFFI.hx line 686
Called from lime/system/CFFI.hx line 111
Called from C:\HaxeToolkit\haxe\std/neko/Lib.hx line 35
Uncaught exception - load.c(357) : Primitive not found : ./lime@lime_joystick_get_num_trackballs(1)
Called from lime/_internal/backend/native/NativeCFFI.hx line 686
Called from lime/system/CFFI.hx line 111
Called from C:\HaxeToolkit\haxe\std/neko/Lib.hx line 35
Uncaught exception - load.c(357) : Primitive not found : ./lime@lime_joystick_get_num_trackballs(1)
Called from lime/_internal/backend/native/NativeCFFI.hx line 686
Called from lime/system/CFFI.hx line 111
Called from C:\HaxeToolkit\haxe\std/neko/Lib.hx line 35
Uncaught exception - load.c(357) : Primitive not found : ./lime@lime_joystick_get_num_trackballs(1)
Called from lime/_internal/backend/native/NativeCFFI.hx line 686
Called from lime/system/CFFI.hx line 111
Called from C:\HaxeToolkit\haxe\std/neko/Lib.hx line 35
Uncaught exception - load.c(357) : Primitive not found : ./lime@lime_joystick_get_num_trackballs(1)

Although the program itself runs just fine and doesn't crash

Don't know about the icon, but check if adding -eval fixes the compile-time errors.

Yes, adding -eval seems to fix those errors

Then in theory, lime rebuild cpp should also fix them. ...But it should also have been required to fix the SDL error, so I'd assumed you'd done it.

I had used lime rebuild windows cuz the readme said so. Is it different from lime rebuild cpp?

It's the same. I always say cpp to save myself the trouble of asking what system someone uses.
Hmm. Did you do git submodule sync and git submodule update?

I used git clone --recursive while cloning and then ran git submodule update. I just tried to run git submodule sync now and then tried to rebuild but the same error shows up

Oh wait, get_num_trackballs was removed, not added. Maybe all you need is lime rebuild tools.

I tried it now but the same error shows up

Maybe lime rebuild tools -clean? I don't know what else it would be.

No, same issue. Just to be sure, I tried using both lime test ... and haxelib run lime test ... but neither seem to fix it

Well, maybe double-check haxelib path lime to make sure it's the repo you just cloned. And try moving the old directory, so that it can't accidentally use any of the files from there.

Hi, sorry for the delay. I checked haxelib path lime and it does point to the newly cloned repo. I tried moving the old one and the issue still happens.
According to the error message, the problem seems to happen at line 686 in NativeCFFI.hx:
Called from lime/_internal/backend/native/NativeCFFI.hx line 686
Called from lime/system/CFFI.hx line 111
Called from C:\HaxeToolkit\haxe\std/neko/Lib.hx line 35
Uncaught exception - load.c(357) : Primitive not found : ./lime@lime_joystick_get_num_trackballs(1)

But line 686 is just this:
https://github.com/openfl/lime/blob/21e8e619c36a0fed8672caae84114b4c7ee8a563/src/lime/_internal/backend/native/NativeCFFI.hx#L686

If you go back as far as 7.9.0, you'll find that the line indeed does try to load get_num_trackballs.
https://github.com/openfl/lime/blob/7.9.0/src/lime/_internal/backend/native/NativeCFFI.hx#L686
This suggests that one way or another, you're still using a very old version of tools.n. Let's cover our bases here:

Move any installs of Lime 7.*.
Delete tools/tools.n from your new install.
Run any lime command (even just lime) and confirm that it recreates tools.n in the correct place.

Failing that:

Make sure your NativeCFFI.hx is up to date.
Run lime rebuild tools -verbose and look for anything odd.

I tried out your steps but the error still showed up, so I tried manually running the hxml files inside the tools folder and somehow when I rebuilt svg.n using tools/svg.hxml the error disappeared (no idea how) 🤔

Good to know, and glad you got it figured out.

Thanks for your help!

I just checked GitHub Actions, and it looks like we haven't been rebuilding svg.n. We've been using a prebuilt version committed in 2019. Continuing to use this same version for multiple releases hasn't been an issue so far, since lime.ndll hasn't removed any APIs in those releases. However, 8.2.0 will need a new svg.n due to that removal of lime_joystick_get_num_trackballs.
I updated the develop branch to make GitHub Actions build svg.n for the Haxelib bundle, and this will eventually get merged into 8.2.0-Dev before the 8.2 release.


[DataGrid] getAllRows method in DataGrid's apiRef

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
I recently updated the MUI in my project to the latest version (version 5) in order to use new features added to the DataGrid component.
I am using apiRef prop to manage the editable feature of the grid. It seemed to me that the ref includes many functions regarding rows but is missing  key function which is getAllRows.
I was wondering if it would be possible to add this function to the ref. It seems like a feature that can be achieved easily and I would be more than happy to work on it.
Examples 🌈
No response
Motivation 🔦
No response

Issue moved to mui/mui-x #4214 via ZenHub


[AMBARI-23746] ClusterStatusReport creates a map of host_id to compon…

…ent_name, needed change for resolving duplicate key
During server login in the UI, backend calls for generating a cluster report. As part of this call, it tries to create a map of host_id,component_name. When Multi-everything, this can result in duplicate entries and hence throws a violation.
Eg (host_id, component_name, service_id) = (1, DATANODE, 2) & (1, DATANODE, 102)
Hence we need service_id to be another distinguishing factor.
How was this patch tested?
Issue was that after creating same components on same host, we could not login to UI, with the fix we are able to do so.

Please review Ambari Contributing Guide before opening a pull request.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/2442/
Test FAILed.
Test FAILured.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/2448/
Test FAILed.
Test FAILured.


Add link to your own paper too

You have linked to other papers in the readme, but not to your own. Please always add a link to your Arxiv paper in your readme. The link is https://arxiv.org/abs/1802.00927

fixed, thanks!


Build native versioning code from scratch

Details
react-native-version wasn't working, so just do this from scratch.
Fixed Issues
Fixes https://github.com/Expensify/Expensify/issues/155197
Tests

Run

Tested On

Github

@AndrewGable looks like this was merged without passing tests. Please add a note explaining why this was done or remove the Emergency label if this is not an emergency.

Merge to unblock deploy


Default values to "Unknown"

To allow users to contribute partial data, attributes should be set to "Unknown" by default. For example, the Licence field should be "Unknown" (we don't know) unless a user specifically sets as "Not specified" (they don't say)

added unknown to: Type, collection size, data license and data size


Bumped nxpmicro-mfgtools

Description of changes
Bumped to release https://github.com/nxp-imx/mfgtools/releases/tag/uuu_1.5.21. Also since NXP changed their owner repo, update accordingly.
Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

Commit message does not fit contributing rules.

Result of nixpkgs-review pr 250894 run on x86_64-linux 1

1 package built:

nxpmicro-mfgtools

The package seems fine. As mentioned before, you'll need to redo the commit message. You can find the commit conventions here. It can also be useful to look at earlier commits if you're unsure.

Gotcha! Changed the commit message


Asyncssh 2.0.0 support

Removed the loop argument passed to asyncssh, as it's not supported anymore. However left in the init function of the netdev class, for compatibility.
Added server_host_key_algs argument to the arg dictionary. This is only added, if the user specifies the list, as it overrides the default algs.

Hello!
Thank you for supporting the project by your code!


Call to undefined method FFMpeg\Filters\Video\VideoFilters::getExtraParams()

$ffmpeg = FFMpeg::create([
'ffmpeg.binaries' => 'd:\ffmpeg\bin\ffmpeg.EXE',
'ffprobe.binaries' => 'd:\ffmpeg\bin\ffprobe.exe',
'timeout' => 3600,
'ffmpeg.threads' => 12,
]);
$MP4Path = 'F:\Tinywan\Video\fooimage2.avi';
$watermarkPath = 'F:\Tinywan\Video\00018.jpg';
$video = $ffmpeg->open($MP4Path);
$watermark = $video->filters()->watermark($watermarkPath, array(
'position' => 'relative',
'bottom' => 50,
'right' => 50,
));
// Extract the image into a new file
$video->save($watermark,'fooimage2_Watermark.avi');
var_dump($video);

@Tinywan, we're here to help, but we're all volunteers. There are some rules to respect when posting here.
When you create an issue, you have a layout which is provided which intend to help us understand what you're trying to do, and what is the problem you're facing. Copy-pasting piece of codes everywhere is of no help. I'm not gonna answer this issue until you fulfill correctly the layout below.
If you're uncomfortable reproducing it in a comment, please close this issue and create a new one.

Q
A

Bug?
no

New Feature?
no

Version Used
Specific tag or commit sha

FFmpeg Version
FFmpeg or AVConv and version

OS
Your OS and version

Actual Behavior
How does PHP-FFMpeg behave at the moment?
Expected Behavior
What is the behavior you expect?
Steps to Reproduce
What are the steps to reproduce this bug? Please add code examples,
screenshots or links to GitHub repositories that reproduce the problem.
Possible Solutions
If you have already ideas how to solve the issue, add them here.
Otherwise remove this section.


Sent with "or" instead of "tor"

This notification:

says sent with "or". It should say "tor".

Looked at this a little. From what I can see there are certain formats of strings that are expected. If there is a new string for TOR, the current parsing of the string in TaskSendMwc::processTask doesn't handle it.

Yes, I saw that but didn't want to mess anything else up by changing it so I opened the bug.

Verified with the latest build and observed the below message, hence closing this ticket.


Support for .theme-check customization path

By default the extension expects .theme-check at root path, it could be useful a configuration editor variable for overriding the default path.

Can you clarify your use case a bit? Is this because you work in a repo with multiple .theme-check.yml? I believe the logic we have right now is to bubble up from the path of the first opened file (but may be wrong).

Yes, I use a custom project structure where those files are on ./.config/ directory instead on ./ for example  ./.config/.theme-check It could be great to "manage" the theme check path as editor variable

Gotcha, so we're not talking about having N configs in a repo but more about having a config in a non-standard path. A bit like the --config flag for the command line, right?

The extension gets the config file: theme-check from root. I mean override the config file path in a variable like:

Maybe the --config flag could work but please let me know how to specify that :)


replaces font-cwtex-q* 0.1 by font-cwtex-q 0.4

[x] The commit message includes the cask’s name and version.
[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] Checked there are no open pull requests for the same cask.
[x] Checked there are no closed issues where that cask was already refused.
[x] When naming the cask, followed the token reference.
[x] brew cask install {{cask_file}} worked successfully.
[x] brew cask uninstall {{cask_file}} worked successfully.

This solve issue #447. However, rather than keeping the original names and leave it remain 5 different fonts, I combined them together since the new releases from GitHub project page put all of them in one single package.

Thank you!

Thank you for the contribution. It needed some fixes, so they were made in 7bf6512e1959a2553f295f5359eb5f862ad4e8a6. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.


Post liker list

This PR closes #370
I have added a new page to show post likes and it is responsive.

This PR closes issue no. #370 I have added a new page to show post likes and it is responsive.

won't a modal look better @Palakkgoyal ? instead of separate page for likes?
Like this?

Your approach is good, but I doubt if we really needed a separate page to show this small data?

This PR closes issue no. #370 I have added a new page to show post likes and it is responsive.

won't a modal look better @Palakkgoyal ? instead of separate page for likes? Like this?

Yes, you are right I initially go for the modal but I faced some problems like on mobile if user click back to close the modal(instead of the close icon) then they get out of the website. But Okay, I will try that approach again and resolve the issues.

This PR closes issue no. #370 I have added a new page to show post likes and it is responsive.

won't a modal look better @Palakkgoyal ? instead of separate page for likes? Like this?

Yes, you are right I initially go for the modal but I faced some problems like on mobile if user click back to close the modal(instead of the close icon) then they get out of the website. But Okay, I will try that approach again and resolve the issues.

ohhh, I think Vijaylakshmi made the frontend  part for this, you can try to take help from her if you still face issue :)

This PR closes issue no. #370 I have added a new page to show post likes and it is responsive.

won't a modal look better @Palakkgoyal ? instead of separate page for likes? Like this?

Yes, you are right I initially go for the modal but I faced some problems like on mobile if user click back to close the modal(instead of the close icon) then they get out of the website. But Okay, I will try that approach again and resolve the issues.

ohhh, I think Vijaylakshmi made the frontend part for this, you can try to take help from her if you still face issue :)

Oh yes! she did hey @VijayalakshmiGanesh would you like to share about that?

Hey, I did the required changes and also made it darkmode compatible.

Hey, I did the required changes and also made it darkmode compatible.

awesome! merging it asap!

Yes, sure.

I have added some responsive. Can you please check and is there anything else I can do?


Fix imports in ouroboros-network

Description

ouroboros-network: fixed imports on mingw32
Bump versions

Checklist

Branch

[x] Updated changelog files.
[x] Commit sequence broadly makes sense
[x] Commits have useful messages
[ ] The documentation has been properly updated
[ ] New tests are added if needed and existing tests are updated
[ ] If serialization changes, user-facing consequences (e.g. replay from genesis) are confirmed to be intentional.

Pull Request

[x] Self-reviewed the diff
[x] Useful pull request description at least containing the following information:

What does this PR change?
Why these changes were needed?
How does this affect downstream repositories and/or end-users?
Which ticket does this PR close (if any)? If it does, is it linked?

[x] Reviewer requested

Seems like there still some fixing to do. There was build warnings on windows machine

@bolt12 it should be fixed.

Heap reached limit on x86_64-darwin, I have a branch with a bunch of improvements which I will submit as a separate PR.


Website caching works really badly on Vercel

So I just rebuilt my site on Vercel and added and removed some stuff but the removed stuff are still there with just 404s and the added things are not there. Does anyone know a quick fix for this?

@onrecc I agree. I have had similar issues. I usually end up doing a redeploy in vercel to make it work.

Yep I also found that out after playing for a while. I'd expect Vercel to work well since, if I understood correctly, they have funded this project and are promoting it.

Yea, quick solution is to turn off the build cache: https://github.com/shuding/nextra/issues/1564#issuecomment-1447419595


Add "reload page" button when Lounge fails to start.

It's hard to reload when in fullscreen mode:

It would be really sweet if it would look like the reload button on the chat page for consistency, but I won't push too much if other @thelounge/maintainers don't like that idea :)
I can't get it to show up right now, but 100%-wide red ribbon that turns green when clicking on it.

I'm not sure I'm happy with the idea of it looking the same as that, it would feel very out of place on this screen, and we plan to remove the other one anyway. I think what we have here is nicer. I understand the consistency though.

It would be really sweet if it would look like the reload button on the chat page for consistency

I've thought about it too, but it doesn't look good. Also, #1185 PR removes that wide button completely, so I think it's better to keep current one.


[Tomato] verify_ssl directive doesn't accept path to cert as docs claim

Home Assistant release with the issue:
0.67.0
Last working Home Assistant release (if known):
None
Operating environment (Hass.io/Docker/Windows/etc.):
Docker
Component/platform:
Tomato
Description of problem:
Same problem as #7892 (fixed in #9788) -- for verify_ssl, the docs say "you can pass a location on the device where a certificate can be used for verification", but it errors out on startup if you pass anything but a boolean.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
device_tracker:
  - platform: tomato
    host: <IP_ADDRESS>
    username: !secret tomato_username
    password: !secret tomato_password
    http_id: !secret tomato_http_id
    ssl: true
    verify_ssl: /config/tomato.pem

Traceback (if applicable):
2018-04-15 12:04:52 ERROR (MainThread) [homeassistant.config] Invalid config for [device_tracker.tomato]: invalid boolean value /config/tomato.pem for dictionary value @ data['verify_ssl']. Got '/config/tomato.pem'. (See ?, line ?). Please check the docs at https://home-assistant.io/components/device_tracker.tomato/

Additional information:
I assume this isn't the only component with this issue. All components with verify_ssl should be verified and patched if needed.

Try verify_ssl: "/config/tomato.pem". The validation checks for boolean or a file.


Atom/quick ideas based on a Jelly corpus

Putting this here, so it doesn't get lost and forgotten in the Jelly chatroom history:
I used SE Data Explorer to gather a corpus of Jelly source code lines, on which I performed some frequency analysis, resulting in

A list of characters by frequency
A list of common 2-grams
A list of common 3-grams
A list of common 4-grams

These lists gave me an idea of which common phrases deserve a 2-byte (or even 1-byte) alias. I compiled a big list of ideas for new atoms and quicks inspired by them. Feel free to comment on their merit or implementation here.
Some thoughts that came out of this in the chatroom:

We probably want a new chain separator for µ€, because it’s ridiculously common.
Ð€ and Ðf and some others should have really been one byte, but it isn’t too late to make aliases for them.
€ is by far the most common character in Jelly code, which is maybe surprising given that Jelly has automatic vectorization. We might want a 1-byte alias for S€, which comes up very often. We might also want to make a bunch of quicks that are short for “get all (blah) and map over them”, e.g. □ÐP could be short for ŒP□€.
Dennis considered amending the Jelly SBCS with aliases that free up more room for 1-byte monads. For example, 0xF8 could be represented by both ẏ and Ŝ, making room for a new monadic atom Ŝ while retaining backwards compatibility.

I considered a hacky solution for mapping structures back when I added prefixes and suffixes. It would be  and the nilad would signal the type of structure to map over. It would be similar to ;. from J

In that sense, a quick with syntax (A)(B)(Q), where Q is the quick, that would be equivalent to (A)€(B)/(C), where C is one of ¤$¥ corresponding to the arity of A, would be useful too, at least empirically.

@GolfingSuccess Can you share some examples demonstrating how that would be useful? I'm intrigued.

I've implemented all of the constant nilads. https://github.com/DennisMitchell/jellylanguage/commit/09eecfd17400acb8fe49afcb4acdfb4b59d147de

), Ƈ, Ɱ, and Ƭ are now aliases for µ€, Ðf, Ð€, and ÐĿ. https://github.com/DennisMitchell/jellylanguage/commit/26ac6389934006e750e2ce8a83f75f8b55578d32

§ and Ä have been implemented as potential replacements for S€ and +\. They vectorize at depth 1.

These atoms along with several more nilads have been added. beb17f3
Œd ( UŒD)
Œḍ (ŒḌU)
ŒH (œs2)
œP (Ṭœp)
œṖ (Ṭœṗ or Ṭk)
Here is an updated list with implemented tokens at the bottom.


Fixes deepdive-load test with huge.sql to be lighter

Looks great @netj !
make test ONLY=test/postgresql/deepdive_load.bats runs without any failure and it loads correctly the sentences_input.sql file in the genomics application, is it enough to merge this PR or is there another test I should try first ?

Nope, Travis also confirms everything's fine.  The test failed fast when prior to our fix, but since the fix it was INSERTing too much rows unnecessarily and made the test too costly so I tweaked it a bit.  Please merge if it LGTY


add: anchor has target attribute & img can be centered

Now the img tag can be centered by adding the attribute align="center" and also the anchor tag can use the target attribute.

@crowlKats What do you think about this? (:

@tmchein what is going on with the css changes? diff is quite hard to read. If you want to change the css, please do so by changing the main.scss file in the style folder and running make build

Oh I didnt know that, I will change the main.scss.
What I tried to do is to do img[align=center] so the user could center images with the attribute.

@crowlKats Check back again pls (:


memcached server hard coded

The memcached server address is hard coded for internal use. The work-around is to add the following code to the top of the getInstance() method of the CachePool class, and then use http://localhost:2990/jira to run locally (change to add parsing for your host and return the host address).
if("localhost".equalsIgnoreCase(host)){
	return host;
}

 Add Memcache to Configuration Manager and Admin.vm

Update 3.0.1 added memcached to VOC Volume configuration "Gadget Caching" for Server Host and Server Port.


ebiten: SetWindowPosition should take a 'monitor'

Now SetWindowPosition takes two numbers representing a position, but it is a little ambiguous which monitor is adopted. Should we add a new struct Monitor and give one to SetWindowPosition explicitly?

This sounds logical enough, yeah.
It seems like it currently works based on the current monitor the window is on. Maybe it would be good to make the proposed SetWindowPosition function also accept an argument to work the way it currently does (where it sets the position using the current monitor), as GLFW currently seems to just allow you to specify the window position, regardless of monitor.