Jump to content
  • Sky
  • Blueberry
  • Slate
  • Blackcurrant
  • Watermelon
  • Strawberry
  • Orange
  • Banana
  • Apple
  • Emerald
  • Chocolate
  • Charcoal

Lizzian

Administrators
  • Content Count

    245
  • Joined

  • Last visited

  • Days Won

    28

Lizzian last won the day on October 27 2018

Lizzian had the most liked content!

About Lizzian

  • Rank
    LizzyTheAdmin

Contact Methods

  • Website URL
    https://www.theender.net
  • Minecraft
    LizzyTheSiren
  • GitHub
    LizzyTrickster
  • IRC
    Lizzy @ irc.esper.net

Profile Information

  • Gender
    Female
  • Location
    The Ether
  • Interests
    Many things

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. The first parameter for the send() function should be the modem that you want to receive the message, not the one you're sending from
  2. You need to use the full address with modem.send()
  3. I'm actually surprised that the avatar import feature works at all. The login system for Discord expects the field in a given response to be a direct URL to the avatar, but in Discord's case it's just the hash for it and would require more steps to build the full URL. For reference, Discord's API (when you log in via it) gives the forums the following, which is not helpful unless there's a way to construct the full URL (which isn't possible from what I can tell) "avatar": "8342729096ea3675442027381ff50dfe" The Twitter integration is actually built in so I suspect that one works. Ultimately this isn't something I can easily fix, sorry
  4. Update as of the 26th of February: It would appear that the forums has deleted my last two updates to the OP of this thread and also asked me to "update" to the latest version again today, despite me doing it yesterday.... I am confident that the mix of MyISAM and InnoDB tables are to cause for this weirdness. I am now going to look at replacements. In the mean time, please make notes of stuff you post cause it could end up going poof
  5. Thanks for the offer, I think I've got it working properly now (see my edit on the bottom of the OP). If it ends up being an issue again I may call for help
  6. As of the start of May 2020, i didn't notice any more issues with the forums, which I'm guessing is due to a combination of some settings I changed as well as setting up the background tasks to be run via cron on the webserver (as apossed to running with general traffic, which only got triggered by logged in members), therefore I'm going to assume that the issue is resolved and we'll be staying with the current forum set. If this issue does rear it's head again at some point, I will take another look at other solutions. Just a heads up, this is going to be a bit of a long post with a bit of technical information mixed in. Forum access over the past few days You may have tried to access the forums over the last few days (13th - 15th of January, 2020) and been met with a message that read something like "Forums are currently offline due to database corruption". Whilst the forums are now back up again, the database corruption is still here. I'll get into the specifics in a bit but first a bit of context: Context: Over the period of the last month, I have been migrating to a new (and cheaper) dedicated server. The forums' files were moved over last weekend but they've been pointing at my database cluster for the past few weeks. Unfortunately, what wasn't apparent to me at the time (and I only realised it yesterday), is that the OC Forums' Database has a mix of InnoDB tables (good, they can replicate) and MyISAM tables (bad, they don't replicate). This has resulted in the database servers printing to their respective consoles, that various tables within the Forum's database are marked as crashed and should be repaired. After a while (or a few requests to the same table, I'm not entirely sure what causes it), it also causes the node that was being accessed to completely crash out, resulting in cutting off anything else that also happened to be using that node at the time. I've limited the forums to one node so the impact is lessened, but it still takes some time when Systemd restarts the downed node and gets it re-synced with the surviving node. I've also tried repairing the tables using various mysqlcheck commands, which didn't succeed. I found an option in the config to use "InnoDB" as the table storage method, but any combination of activating that and converting the MyISAM tables to InnoDB ones just ends up in either more crashes or stuff not even loading at all. Nothing I have tried is getting it back to how it was before all my migrations started a month ago. I do have some backups, but they're either from over a month ago, or already contain the corruption. Going forward, there'll be daily snapshots of the database nodes, but that doesn't help fix things retroactively sadly. What's the TL;DR? As it stands right now, the databases are corrupted and the frequency of the crashes is only going to get worse. One of the tasks that is currently "stuck" (and trying to manually run kills the database) is the cache clearing process. The table it accesses is a MyISAM-backed one. With no way to convert the tables or fix the corruption and the only way to "back up" the data of the forum is to take a snapshot of the (corrupted) database, there isn't a lot of options to be able to do a backup-wipe-and-reload whilst keeping all the data. Future plans and fixes To those of you who have been giving some domains towards the license costs, Thank you! They are a good help. The amount on the sidebar is currently a little off because trying to update the value end up killing the Database node, which is what alerted me to this issue in the first place (it doesn't auto-update annoyingly). So what's the plan? Right now? I honestly don't know. I'm contemplating switching to a different forum software, preferably something free/open source. But moving all the topics, discussions and userdata over is going to be a pain, even more so when the database is in a fragile state. I was looking into seeing if I could get the Wayback Machine to snapshot the entirety of the forums, but their site for snap-shotting everything confused me. (If you know more about this, please @Lizzian me on either the Discord guild or IRC). AFAIK the Wayback Machine allows you to snapshot single pages, so if you want to snapshot random pages/threads, please do. I'll be leaving this topic open for replies (if permissions allow you to reply, I don't know if you can and the database might die again if I try to look), so if you have any questions either reply to this thread or poke me on IRC/Discord. In writing all of the above, the database node that the forums is pointing to has died a total of 5 times so far and even made the container that the node was running in crash. Edit as of 24th of January: I think I have possibly fixed some of the issues? The cache table (which was at a whopping 18GB or so when I was trying to fiddle with stuff last week) has now been manually cleared out. Had to do that 2k rows at a time or the mysql client and server got killed for exceeding the container's allocated RAM amount. The tasks are now running smoothly and so far (it's only been 10 minutes since i did it) there have been no errors in the console! Update as of the 26th of February: It would appear that the forums has deleted my last two updates to this post and also asked me to "update" to the latest version again today, despite me doing it yesterday.... I am confident that the mix of MyISAM and InnoDB tables are to cause for this weirdness. I am now going to look at replacements. In the mean time, please make notes of stuff you post cause it could end up going poof
  7. OpenComputers version 1.7.5 has been released for MC Versions 1.7.10, 1.10.2, 1.11.2 & 1.12.2 (NOTE: This will be the last version to support MC 1.11.2, future updates will continue to support 1.7.10, 1.10.2 & 1.12.2)  As always, remember to make a backup of your world. Got an issue? Post it on the GitHub Issue Tracker or the support section of the forums. Download on Curse. New Features/Support This will be the last version for Minecraft 1.11.2. Minecraft 1.7.10, 1.10.2, and 1.12.2 will keep receiving updates. Added: Barcode reader upgrade! (AmandaCameron) An Analyzer can now be installed in a Tablet as an upgrade. Provides the barcode_reader component. When clicking on a block with a tablet containing this upgrade, the tablet_use event will contain information the Analyzer would normally reveal. This allows getting components' addresses into OC directly by clicking on blocks. Added: Config option to set max signal queue size (default 256, the same as before). Signals pushed to the computer when the queue is full are dropped. Added: Allow different HTTP request methods in internet.request (the method to use is now the fourth optional argument). Added: You can now install Angel Upgrades in drones (Minecraft 1.12 only). Added: Chargers can now charge items in nearby players' inventories. Added: Experience Upgrade now shows its level in its tooltip (Minecraft 1.12 only). Added: Extended item information to Thaumcraft Essentia Jars on Minecraft 1.12 (seebs) Added: Support for SimpleLogic bundled cables on Minecraft 1.12. (asiekierka) Added: Re-added Wireless Redstone (ChickenBones Edition) support on Minecraft 1.12. Misc: Hide bounding box wireframe on screens while not sneaking Misc: More robot names. Misc: Updated the chinese translation of the manual. (3TUSK, ZeroAurora, JackyWangMislantiaJnirvana) Changed: Cleaned up some wording in the config file. Changed: gpu.bind is now faster. Changed: computer.pushSignal now accepts tables of simple key-value pairs, but not nested tables. Changed: APU tiers now correspond to their CPU tiers. Changed: Putting unmanaged hard drives into a Raid now forces them into managed mode along with wiping them. Fixed: Robots being unable to use buckets. Fixed: Fluid dupe bug that I will not explain to you. Fixed: Tier 2 wireless network card not receiving wired messages. Fixed: Return value of robot.swing when the block breaks too fast. Fixed: Server racks not sending messages to mountables quickly enough. Fixed: Relays not displaying traffic accurately. Fixed: Relay message relaying issues. Fixed: itemDamageRate config option set to 0 not working. (svitoos) Fixed: Crash with hologram.copy. Fixed: Geolyzer's isSunVisible. Fixed: Crash with remote terminals. Fixed: A Robot without inventory deleting the items it drops. Fixed: too long without yielding sometimes not triggering when it should. Fixed: Crash when blowing up a computer while code is running. Fixed: Another fluid dupe bug that I will definitely not explain to you either. Stop asking. Fixed: Available architectures not always being what they should be. Fixed: Crashes in AE2 integration. Fixed: The AE2 ME Interface part not having network control. Fixed: AE2 ME cells not having all intended information on inspection. (wkalinin) Fixed: Crash with AE2 when power usage is disabled. Fixed: AE2 interface not being recognized as components when channels are disabled. Fixed: Some AE2 integration not working on 1.7.10. (wkalinin) Fixed: Another crash with AE2 when power usage is disabled. Fixed: Specific AE2 integration being very slow. Fixed: Crash with IC2 Classic. OpenOS fixes/improvements Fixed: Error related to installing OPPM. Fixed: OpenOS timers being starved during blocking pulls. Fixed: reset alias to reset the screen resolution to its maximum. Fixed: Certain TCP connections in Network loot disk Fixed: Various vt100 fixes Fixed: Now errors properly on using print with bad __string metamethods List of contributors payonel, AmandaCameron, wkalinin, LizzyTrickster, svitoos, kchanakira, seebs, asiekierka, 3TUSK, ZeroAurora, JackyWangMislantiaJnirvana
  8. Did you install openos to a hdd and then boot into that before you tried installing Lunatic?
  9. I've removed the link in the OP as it directs to a generally non-standard site. @AtomicScience please use Paste/Hastebin or GitHub for sharing code as they are easier to see the code and no possibility of a virus or something being included
  10. Lizzian

    Font fixing

    What screen resolution do you have? Have you also tried with a lower OC-screen resolution? The characters get squashed when the OC-screen size is bigger than the physical monitor of your pc/laptop can handle
  11. It will be ported when it can. Right now I don't think many other mods are supporting 1.13 and i believe something is changing again in 1.14 which would make updating to 1.13 a pain because it'd have to be re-done. Check the issue tracker on GitHub, there's probably a ticket there for 1.13/1.14 support
  12. Should be fixed now, thanks for reporting it to us
  13. I've poked @Sangar on discord but i'm also gonna poke him here too (I'm not sure if the forums emails when people get pinged...) Hopefully it's just a case of adjusting the cert request.
  14. Looking at your second screenshot, the last command you tried did invoke OPPM but it couldn't find the package. It's unclear from the screenshot, but it looks like you've specified "gen2halo" as the package name. That doesn't exist and I'm guessing you'll want "gen2holo".
  15. OpenComputers version 1.7.4 has been released for MC Versions 1.7.10, 1.10.2, 1.11.2 & 1.12.2  As always, remember to make a backup of your world. Got an issue? Post it on the GitHub Issue Tracker or the support section of the forums. Download on Curse. New Features/Support Misc: when powering on, drones may fly a bit higher will fly a above their starting block to get above nonfull blocks (such as chests) Misc: more robot names Misc: robot/drone swing respects harvestability of block vs tool Fixed: zero sized files (bufferChanges failing to do its job) Fixed: client crash when using remote terminal out of range Fixed: inventory controllers now honor specified target slot Fixed: T1 wireless cards now properly ignore wired messages Fixed: waila integration by checking for nulls with relay block Fixed: practical logisitics integration by not passing null for EnumFacing Fixed: locking items in hotbar when gui is open Fixed: some container names localized OpenOS fixes/improvements Fixed: fixed event timing issues when pulling smaller timeouts than a current timer Added: tty handles '\v' code to move cursor down one line Misc: some openos cleanup Misc: more memory savings Misc: slightly faster boot up times List of contributors payonel, Wilma456 Anar Abdullayev, TheCodex6824
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use and Privacy Policy.