primordic/IssueDupesLite huggingface dataset:
Repository: FabricMC/fabric

Issue #2546: fabric-api-0.5.7+build.2-20w14infinite.jar works not; only "1.16-alpha.20.13.inf" found instead of "1.16-20.w.14"
Created: 2022-09-23T13:42:40Z
I knew this is somewhat edge-case, but I wanted to install fabric for 20w14infinite. The Infinite Demension April Fool version.
However, having installed fabric-api-0.5.7+build.2-20w14infinite.jar and other necessary things, as I run the Minecraft launcher, this message pops out before the game even tries to start:

Mod 'Fabric API' (fabric) 0.5.7+build.2-20w14infinite requires version 1.16-20.w.14 of 'Minecraft' (minecraft), but only the wrong version is present: 1.16-alpha.20.13.inf!

I am no expert on coding and stuff, but at least, from this error message, even a three-year-old can infer that: the Fabric API and the Mojang .jar client file are referring the very same Infinite Demension version by different names: 1.16-20.w.14 and 1.16-alpha.20.13.inf.
I thought the .13.inf one was the misnamed one, so I proceeds to replace the client.jar with the one downloaded directly from Mojang. However, the problem preserves.
In my mindset I've long taken for granted, there's only one name for the Infinite Demension April Fool version, and it's "20w14∞", never "20w13∞". Today I question my memory ever before and gently ask for help. Either for a client.jar that refers it as 1.16-20.w.14, or a fabric-api-0.5.7+build.2-20w14infinite.jar that refers if as 1.16-alpha.20.13.inf.

Duplicate issue #2819: Incompatible mod set! for fabric 20w14infinite
Created: 2023-01-03T00:56:34Z
Im using fabric-api-0.5.7+build.2-20w14infinite because I can't find another one to try. I really don't understand what I need to do here, I installed both fabric and fabric api to 20w14infinite, I disabled all mods but still it doesn't work. Help please!

Closing comment (2023-01-03T08:58:45Z): Duplicate of #2546.
Repository: FabricMC/fabric

Issue #2962: Data generator can incorrectly override recipe IDs
Created: 2023-03-13T19:12:39Z
FabricRecipeProvider.getRecipeIdentifier replaces the namespace of the recipe with the mod id of the data generator:

  
    
      fabric/fabric-data-generation-api-v1/src/main/java/net/fabricmc/fabric/api/datagen/v1/provider/FabricRecipeProvider.java
    
    
        Lines 101 to 103
      in
      7d882bf
    
  
  
    

        
          
           protected Identifier getRecipeIdentifier(Identifier identifier) { 
        

        
          
           	return new Identifier(output.getModId(), identifier.getPath()); 
        

        
          
           } 
        
    
  


This can easily lead to invalid recipe advancements where the advancement's default has_the_recipe criterion still references the original namespace.

Duplicate issue #3270: nineBlockStorageRecipes doesn't save with mod id
Created: 2023-08-17T03:58:58Z
If you call CustomModRecipeProvider.nineBlockStorageRecipes it will save the advancements it creates for recipe possession tracking with the wrong Mod id for the resource location ("minecraft:", instead of "custommod:"). While it is easy to work around this, it would be nice if fabric added functionality to allow the passing of a mod id to CustomModRecipeProvider.nineBlockStorageRecipes so that developers can each call the same function instead of having to reimplement a work around for each mod they work on. If this is something that may be added please let me know and I will draft a PR and if this is not wanted let me know and I will close this.

Closing comment (2023-08-17T09:04:50Z): Duplicate of #2962. If you can provide a fix for that issue go ahead!
Repository: FabricMC/fabric

Issue #265: Update fabric loot table to 1.14.3 async json loading
Created: 2019-06-11T08:41:11Z
In 1.14.3 pre-1, mojang introduced async json loading for vanilla data. This broke the loot table api's mixin at 05f11b7#diff-0a1c21c182b8708aff532f69a5f4feffR40
The correct way is to inject at the apply method that takes (T, Executor).
Example error log:
https://hastebin.com/metaquketa.rb
https://hastebin.com/hadetobere.makefile
Reports on discord:
https://discordapp.com/channels/507304429255393322/507982478276034570/587759437687554078 (includes a log snippet)
https://discordapp.com/channels/507304429255393322/507982463449169932/587859116484067328
https://discordapp.com/channels/507304429255393322/507982478276034570/587918350437318656

Duplicate issue #270: Crash when opening world
Created: 2019-06-13T09:49:32Z
Minecraft: 1.14.3-pre2
Fabric API: fabric-api-0.3.0+build.184
Fabric Loader: 0.4.8+build.155-1.14.3-pre2+build.4

Closing comment (2019-06-13T09:51:27Z): Fabric API currently targets 1.14.2 and does not have support for 1.14.3 (Duplicate of #265)
Repository: FabricMC/fabric

Issue #66: Datapack tags always replace, even when they should append
Created: 2019-01-14T13:18:15Z
API version: 0.1.4.71
Description:
My mod adds new walls. So I have to add these new walls to the vanilla block tag minecraft:walls.
With a "false" value in the "replace" field, my walls should append to the vanilla ones. But instead, they replace them.

Duplicate issue #670: Neither vanilla nor modded tags applied to items
Created: 2020-06-08T19:17:41Z
When an acacia_log.json file is placed under src/main/resources/data/minecraft/tags/blocks, with the following contents:
{
  "replace": false,
  "values": [
    "minecraft:dirt"
  ]
}

Dirt does not register as an acacia log in recipes or when using clear in-game. Furthermore, if the same file is placed under .../data/modid/tags/blocks, the tag #modid:acacia_logs does not exist in-game.

Closing comment (2020-06-08T19:37:56Z): Probably related to #66

That still appears unsolved, too. And, while perhaps related, I am not confident that they are the same issue.
Repository: FabricMC/fabric

Issue #2080: Game can't start - Only fabric and api no mods
Created: 2022-03-18T02:48:57Z
22w11a snapshot
Fabric alone doesn't crash but as soon as I add fabric api, this crash happens:
I can't figure out what is causing it :(
error.txt

Duplicate issue #2084: [22w11a] Fresh client install crashes on start-up
Created: 2022-03-18T22:12:04Z
Log: https://gist.github.com/kwpugh/7360c1e6cbfd344cffa4167542d02847
Not sure if  this is Fabric or MultiMC
MultiMC launches 22w11a fine without  Fabric API jar

Closing comment (2022-03-18T22:48:20Z): Duplicate of #2080, already fixed in #2081.
Repository: FabricMC/fabric

Issue #546: Brightness issue
Created: 2020-03-27T18:48:55Z
Why is this software changing my brightness?

Duplicate issue #565: Seems to change color saturation when loaded 
Created: 2020-04-11T01:20:30Z
Attached are before and after pics. This is using the most recent version for the 20w15a minecraft snapshot. I'm not using any color altering programs like f.lux or anything.

Closing comment (2020-04-14T05:48:55Z): Duplicate of #546
Repository: FabricMC/fabric

Issue #210: Modded blocks don'r drop on breaking
Created: 2019-05-25T14:16:23Z
I've written to the authors of the mods with which I have this problem, and one suggested it may be an issue with API, as this was the only common change:
Modded blocks don't drop when broken in survival mode. I tested it with .165, .166, .167 on mods: Cotton resources, Epicurean, Extra Pieces and Blockus.

Duplicate issue #214: Block Loot Tables Broken
Created: 2019-05-26T07:31:27Z
I've gotten a few reports of Extra Pieces, along with other mods (namely Epicurean Gastronomy, Cotton Resources and Blockus) having their block drop loot tables broken (as in, none of the mods' blocks drop anything when mined) in recent versions of Fabric API (on 1.14.2).
Reportedly this affects API 0.3.0-pre builds 165, 166 and 167.

Closing comment (2019-05-26T07:33:53Z): Duplicate of #210
Repository: FastLED/FastLED

Issue #782: FastLED and arduino-esp8266
Created: 2019-04-28T11:09:16Z
hi,
I am using FastLED to drive around 422 WS2812B leds.
I work on esp8266 with arduino-esp8266 framework, building it in PlatformIO.
While using framework in version 1.8.0 (Arduino framework 2.4.3) everything works fine but if I change framework to 2.0.0 (Arduino framework 2.5.0), FastLED output is unusable.
in ver.2.0.0 everything complies fine terminal output is fine, just led are not working correctly.
Is there some incompatibility between FastLED and esp8266 arduino framework versions ?

Duplicate issue #813: 3.2.8 causes LED strip to be just white and uncontrollable on esp8266
Created: 2019-06-07T20:38:10Z
Hi, the new 3.2.8 solved the uploading issue on the esp8266 (Wemos D1 mini) for me, but now my leds stay 100% brightness white and they can't be controlled. I've tested the DemoReel100 and some of my sketches and they all just turn the strip white.
With 3.2.6 everything worked fine for me.
Tested with FastLED 3.2.8, esp8266 2.4.2 and 2.5.2, Arduino 1.8.7 and 1.8.9

Closing comment (2019-06-08T15:21:12Z): Related to #782? That in essence says (slightly redacted): "Arduino framework 2.4.3 everything works fine but if I change to Arduino framework 2.5.0, FastLED output is unusable." and "everything compiles fine, just led are not working correctly."
Repository: FastLED/FastLED

Issue #1818: Conflict between Audio library and ObjectFLED driver (Teensy 4.x)
Created: 2024-12-28T15:56:12Z
I've been using FastLED with the mighty Teensy 4.x platform for years for my Striptease project, together with Paul Stoffregen's WS2812Serial library, which implements non-blocking rendering to get the highest possible framerate, and Paul Stoffregen's Audio library, which provides professional audio processing capabilities.
When I saw the release notes for v3.9.8 I was thrilled to see this technology integrated into FastLED, so I made a quick test, replacing #define USE_WS2812SERIAL with #define FASTLED_USES_OBJECTFLED.
It kind of worked, as the fps jumped from 43 (plain FastLED) to 133 (the same I get with WS2812Serial), but there some issues, like random pixels flickering all the time (see video).
Probably there's something in my code, but maybe not. Perhaps some interaction with the audio shield and its library? For now I'll stay with WS2812Serial, as it works buttery smooth with my project, and I don't need massive scalability, but if you want me to do some specific test to try debugging this issue, please let me know and I'd be happy to collaborate.

Duplicate issue #1886: Flickering when using the ObjectFLED driver
Created: 2025-02-09T14:34:54Z
This issue is related to #1818.
One of my WS2812B LED strips, probably older than the other ones I have, does not work well when using the ObjectFLED driver.
I ran a few tests and this is the result:

FastLED with WS2812Serial driver => no problem
FastLED with ObjectFLED driver => flickering noise
Direct ObjectFLED (no FastLED) => no problem

@zackees Is FastLED initializing ObjectFLED with custom timings?

Closing comment (2025-02-11T10:01:01Z): This issue is related to #1818.
One of my WS2812B LED strips, probably older than the other ones I have, does not work well when using the ObjectFLED driver.
I ran a few tests and this is the result:

FastLED with WS2812Serial driver => no problem
FastLED with ObjectFLED driver => flickering noise
Direct ObjectFLED (no FastLED) => no problem

@zackees Is FastLED initializing ObjectFLED with custom timings?

ObjectFLED has its own timings. try setting the overclock factor to 1.1 or 0.9, one if those should fix it.
This reason is the time for the on value needs adjusting. Overclocking or under kicking will make it slide into specification.
Repository: FastLED/FastLED

Issue #1349: ESP32-C3 output stability issue (flickering, artifacts + guru meditation after few seconds)
Created: 2022-01-09T13:25:07Z
Problem description: same code works as expected on ESP32 & ESP32-S2 but on ESP32-C3 produce unexpected pixels flickering and other artifacts. Our project made for PIO and at that moment require newest SDK and some hacks to get working target ESP32-C3 on current VSCode + PIO version : https://github.com/DmytroKorniienko/FireLamp_JeeUI/tree/dev
target:
[env:esp32c3] ; 4mb without OTA
framework = arduino

platform = https://github.com/platformio/platform-espressif32.git#feature/arduino-upstream
platform_packages =
    ;framework-arduinoespressif32 @ https://github.com/espressif/arduino-esp32.git#2.0.1
    framework-arduinoespressif32 @ https://github.com/espressif/arduino-esp32.git

; platform = espressif32
; platform_packages =
;     toolchain-riscv-esp@file://d:\toolchains\riscv32-esp-elf ; https://github.com/espressif/crosstool-NG - toolchains releases
;     framework-arduinoespressif32@https://github.com/espressif/arduino-esp32.git
;     platformio/tool-esptoolpy @ ~1.30100

board = esp32dev ; board hack
;board = esp32-c3-devkitm-1
board_build.mcu = esp32c3
board_build.partitions = noota.csv
board_build.f_cpu = 160000000L
board_build.f_flash = 80000000L
; board_build.flash_mode = qio
board_build.arduino.ldscript = esp32c3_out.ld
build_type = debug
build_flags =
    ${extra32.build_flags}
    -DLED_BUILTIN=3 ; 3,4,5
    -DLAMP_DEBUG=1
    -DEMBUI_DEBUG
    ;-DFASTLED_ALLOW_INTERRUPTS=1
    ;-DFASTLED_INTERRUPT_RETRY_COUNT=3
    ;-DINTERRUPT_THRESHOLD=0
    ; Logging level: 1 = error, 2 = warning, 3 = info, 4 = debug, 5 = verbose
    ;-DCORE_DEBUG_LEVEL=4
    ;-DCONFIG_ARDUHAL_LOG_COLORS=1
lib_deps =
    ;${env32.lib_deps}
    https://github.com/plerup/espsoftwareserial.git
    https://github.com/DmytroKorniienko/DFRobotDFPlayerMini
    https://github.com/DmytroKorniienko/EmbUI.git#dev
    https://github.com/FastLED/FastLED.git
monitor_filters = esp32_exception_decoder, default
extra_scripts = replace_fs.py
monitor_speed = 460800
upload_speed = 921600
; monitor_port = COM11
; upload_port = COM11
; monitor_port = COM17
; upload_port = COM17
monitor_rts = 0
monitor_dtr = 0
; monitor_rts = 1
; monitor_dtr = 1

but I think same issue may be reproducible on any other environment with ESP32-C3 and exchange over WiFi via web-sockets / UDP
Let me know if you need any additional information/testing at any ESP32/ESP32-xx or ESP8266 controllers.
Related discussion: https://www.reddit.com/r/FastLED/comments/qfbz79/esp32_s3_lets_see_if_i_can_make_it_work_with/hm75n6o/

Duplicate issue #1389: Not working with ESP32 C3
Created: 2022-05-09T15:36:00Z
Hi,
I can compile but the result is lighting 2812 LED out of control
I suspect this is "just" timer issue as ESP32 C3 is 160mhz CPU
Can you give me some ways to change and try to fix this ?
Rgds

Closing comment (2022-06-21T14:47:12Z): do you use wifi at the same time?
could be a duplicate of #1349
Repository: FastLED/FastLED

Issue #744: FastLED does not work on STM32/BluePill  : BOUNTY US$40 for making it work.
Created: 2019-02-23T19:06:38Z
Arduino 1.8.8 , FastLED current master, the LED strip is working fine with this library on a Atmega328:
On a BluePill , STM32F103C8 , with STM32duino bootloader, I tried the example "ColorPalette"
changed only "#define LED_PIN"
to 17  as "PA7" is not recognized
then tried PB5 , (recognized).
no LED activity.

Duplicate issue #750: Support STM32F030C8T6
Created: 2019-03-07T12:31:10Z
Hello, anyone know to let me know about this library is compatible with the STM32F030C8T6? If it is not possible to adapt it?

Closing comment (2019-03-09T16:24:33Z): Duplicate of #744
Repository: FastLED/FastLED

Issue #754: not compiling on platformio, when selecting nodemcuv2
Created: 2019-03-13T17:44:43Z
in this project im using a nodemcu , apa102 leds , and an apds9960 .
if i use D1mini as the set on patformio it compiles ok,
but when using nodemcuv2 ( ESP12F) , i get the following error
 required`` from 'CLEDController& CFastLED::addLeds(CRGB*, int,  int) [with ESPIChipsets CHIPSET = (ESPIChipsets)5u; unsigned char DATA_PIN = 14u; unsigned char CLOCK_PIN = 13u; EOrder RGB_ORDE R = (EOrder)136u; unsigned char SPI_DATA_RATE = 4u]' src/main.cpp:464:79:   required from here /Users/Gus-nuevo/.platformio/lib/FastLED_ID126/fastpin.h:207:2: error: static assertion failed: Invalid pin specified static_assert(validpin(), "Invalid pin specified");
i think is not accepting the pins selected , when using nodemcu , but it is when selecting D1mini , as im using a NodeMCU  ( and is working fine) , there should be not reason for claiming such error .
tks

Duplicate issue #753: not compiling on platformio, when selecting nodemcuv2
Created: 2019-03-13T17:44:19Z
in this project im using a nodemcu , apa102 leds , and an apds9960 .
if i use D1mini as the set on patformio it compiles ok,
but when using nodemcuv2 ( ESP12F) , i get the following error
 required`` from 'CLEDController& CFastLED::addLeds(CRGB*, int,  int) [with ESPIChipsets CHIPSET = (ESPIChipsets)5u; unsigned char DATA_PIN = 14u; unsigned char CLOCK_PIN = 13u; EOrder RGB_ORDE R = (EOrder)136u; unsigned char SPI_DATA_RATE = 4u]' src/main.cpp:464:79:   required from here /Users/Gus-nuevo/.platformio/lib/FastLED_ID126/fastpin.h:207:2: error: static assertion failed: Invalid pin specified static_assert(validpin(), "Invalid pin specified");
i think is not accepting the pins selected , when using nodemcu , but it is when selecting D1mini , as im using a NodeMCU  ( and is working fine) , there should be not reason for claiming such error .
tks

Closing comment (2019-03-13T22:05:11Z): Closing t his as a duplicate of #754 - you submitted twice.
Repository: Fate-Grand-Automata/FGA

Issue #953: Skills are not being used on second and third wave. 
Created: 2021-11-16T18:12:27Z
Preparation

 I tested the latest release
 I looked at other issues (even the closed ones)
 I read the Troubleshooting Guide

FGO server
NA
FGA build number
1554
Describe the bug
Skills are not being used on the second and third wave, and looking at the debug mode, it looks like it's not trying to match anything in the area for Waver's skills from the second turn onward, but I'm not sure how it's intended to behave there.
Here's the command that I'm using for the battle config.

Video
https://streamable.com/ruhe1d
Device model
Bluestacks 4 for Mac
Android version
7
Screen size
1280x720
RAM
8GB allocated

Duplicate issue #954: Battle Configs breaking on Wave 2
Created: 2021-11-16T18:25:46Z
Preparation

 I tested the latest release
 I looked at other issues (even the closed ones)
 I read the Troubleshooting Guide

FGO server
NA
FGA build number
1554
Describe the bug
Two previously working battle configs both run into the same problem after the recent updates. The clear starts normally, picks support, does wave 1 properly. Wave two it skips all skill usage and starts facecarding. Doesn't even seem to attempt to select skills, or miss buttons. Restarted the app, rewrote the turn in one of the Battle Configs, still nothing. Doesn't seem to matter if I start the script from the combat screen or the support screen. Let me know what other information I can get for you to help you help me. Thanks for the help and the solid application.
Video
https://streamja.com/05n4j
Device model
Bluestacks 4
Android version
7
Screen size
1600x900
RAM
4GB

Closing comment (2021-11-16T19:00:30Z): Duplicate of #953
Repository: Fate-Grand-Automata/FGA

Issue #977: Automatic friend requests that meet your criteria
Created: 2021-11-23T19:06:20Z
Preparation

 No one has asked for this feature before in other issues (even the closed ones)

Describe the feature
(English is not my first language, so please excuse my mistakes.)
I've thought automatically sending a friend request to someone who meets your criteria would be nice, such as "10/10/10 Waver with MLB Chaldea Teatime". If you want to avoid spam you could temporarily stop it after one friend request is sent.

Duplicate issue #1145: Send friend request automatically after battle (plz :'D)
Created: 2022-04-05T22:52:08Z
Preparation

 No one has asked for this feature before in other issues (even the closed ones)

Describe the feature
It would be so helpful. Like, I use FGA a lot to farm but in turn I don't really have many friends (big sad) so when I'm playing against bosses I don't have many friends supports to choose from.
Like you would make me so happy (and my life a bit easier) if you added this feature.

Closing comment (2022-04-06T05:21:04Z): Duplicate of #977
Repository: Fate-Grand-Automata/FGA

Issue #571: New JP UI Update - Not working with non-16:9 display
Created: 2020-11-25T11:56:44Z
Before opening an issue:

 I tested the latest release
 I looked at other issues (even the closed ones)
 I read the Troubleshooting Guide
 I'll fill this template properly


Your issue will get closed/locked by the bot in case proper info isn't provided
If you open unnecessary/dumb issues, you'll be rewarded with appropriate tags.

Describe the bug
FGO JP just dropped an update where they made their UI adaptive. This removes the blue bars on the sides and messes up the areas that are checked. I personally think they're just out to get you lol /s
I haven't tested yet but it might still work on regular 16:9 screens.
Screenshots

Device Info (please fill at-least 'Device model'):

Device model: Xiaomi Mi 9T
Screen size: 1080x2340
Android Version: Android 10 - Pixel Experience

Duplicate issue #648: order change doesn't work
Created: 2020-12-29T15:35:13Z
[ yes] I tested the latest release
[ y] I looked at other issues (even the closed ones)
[ y] I read the [Troubleshooting Guide]
[ y] I'll fill this template properl

Describe the bug
order change, click in wrong area '-'
Video

  
    
    

    SVID_20201229_172526_1.mp4
    
  

  

  


Device Info (please fill at-least 'Device model'):

Device model: [ Huawei p20]
Screen size: []
Android Version: [android 10, emui 10]
RAM: [4 ram]

Closing comment (2020-12-29T15:42:49Z): Duplicate of #571
If you're really using the latest canary build, then add a comment there.
Repository: Fate-Grand-Automata/FGA

Issue #993: Sometimes, the currently selected party is detected incorrectly
Created: 2021-12-07T14:03:30Z
Preparation

 No one has asked for this feature before in other issues (even the closed ones)

Describe the feature
I formatted this as a feature request because as far as I can tell this is an issue that has nothing to do with FGA since it occurs I repeat the scripts actions manually. The problem is with the party screen where the 'start quest' button gets locked this happens when Party X is already selected and I or FGA selects Party X again using the top bar. The workaround I want to suggest for this issue is to add a setting which will make FGA always select a different first and then select the desired party. I don't know how hard this stuff is on the back-end but the simplest example I could think of is select Party X+1 then Party X but then idk what to do with Party 10.

Duplicate issue #1247: quest start button doesnt work until change team
Created: 2022-07-14T03:09:32Z
Preparation

 I tested the latest release
 I looked at other issues (even the closed ones)
 I read the Troubleshooting Guide

FGO server
KR
FGA build number
1721
Describe the bug
quest start button doesnt work until change team
I read #465 this but I find some people solved this problem by increasing the resolution. So I think It's not just a game lssuse. I also tried to solve this problem by increasing the resolution, but this is not possible with my mobile device
ps and I dont know why but I faild to record my screen so I brought a similar video
Video
https://www.youtube.com/watch?v=q_QZFBIWgDU
Device model
Galaxy Tab S8
Android version
12
Screen size
2560 x 1600
RAM
8gb

Closing comment (2022-07-15T19:00:26Z): Duplicate of #993
If you can't record a video, you should not just use a random video you found somewhere. I was confused why FGO has blue bars and why the FGA stop button looks weird.
Repository: Fate-Grand-Automata/FGA

Issue #1211: FGO no longer fills the full screen on Realme
Created: 2022-06-13T09:45:50Z
Preparation

 I tested the latest release
 I looked at other issues (even the closed ones)
 I read the Troubleshooting Guide

FGO server
NA
FGA build number
1692
Describe the bug
Since yesterday, I noticed my FGA suddenly has a bit problem. I thought that because of FGO currently unable to Fullscreen since yesterday (12Jun2022) but it still happen even when I turned off the 'Ignore notch calculation'. I followed the troubleshooting guide and re-starting my phone still result the same.
Hope it can be fixed before lottery events.
Anyway, I want to say TQVM for this app. It has helped me all the farming and saving time by a lot..
Video

  
    
    

    VID_20220613172038.mp4
    
  

  

  


Device model
Realmi GT Neo 2
Android version
12
Screen size
1080x2400
RAM
12

Duplicate issue #1229: Can not select friend servant in selecting friend servant page
Created: 2022-07-05T08:05:49Z
Preparation

 I tested the latest release
 I looked at other issues (even the closed ones)
 I read the Troubleshooting Guide

FGO server
JP
FGA build number
1707
Describe the bug
FGA could automatically select the battle stage, however, when showing the scene of friend servant selecting, it just suddenly stops. The scene seems freezed.
Video

  
    
    

    record.mp4
    
  

  

  


Device model
Realme GT
Android version
12
Screen size
2400*1080
RAM
12GB

Closing comment (2022-07-05T08:07:47Z): Duplicate of #1211
Repository: Fate-Grand-Automata/FGA

Issue #662: SPAM SKILL
Created: 2021-01-07T07:08:22Z
Hei its me again!
Yesterday you say to use spam skill i need to activate the skill first right? I already set the skill in command menu and test it, but after the cooldown is over it does not clicking the skill at all

Duplicate issue #671: HAI!
Created: 2021-01-19T02:56:58Z
So i have a question how spam skill work? I turn it on but nothing happen.
Thank you

Closing comment (2021-01-19T06:56:27Z): Duplicate of #662
You ignored what I told you.
Repository: Fate-Grand-Automata/FGA

Issue #796: JP - No support being picked after 6th Anniv Patch - Append Skills breaks the support picker
Created: 2021-08-01T16:21:07Z
Before opening an issue:

 I tested the latest release
 I looked at other issues (even the closed ones)
 I read the Troubleshooting Guide
 I'll fill this template properly

Describe the bug
Support picker no longer working with the Append Skills released for JP's 6th anniversary
Screenshots / Video
https://imgur.com/a/CSdZv4P
Device Info (please fill at-least 'Device model'):

Device model: BlueStacks Hyper-V 4.280
Screen size: 1920x1080
Android Version: Android 7.1.1
RAM: 4GB

Duplicate issue #807: Bug Report
Created: 2021-08-07T05:24:23Z
Before opening an issue:

[x ] I tested the latest release
[x ] I looked at other issues (even the closed ones)
[x ] I read the Troubleshooting Guide
[x ] I'll fill this template properly


Your issue will get closed/locked by the bot in case proper info isn't provided
If you open unnecessary/dumb issues, you'll be rewarded with appropriate tags.

Describe the bug
A clear and concise description of what the bug is.
Include steps to reproduce the error if required
Having issue where servant picker won't select the correct servant when the max skills is selected


  
    
    

    record.mp4
    
  

  

  


Screenshots
If applicable, add screenshots to help explain your problem.
It is recommended that you at-least add one screenshot of FGO running on your device.
Video
If relevant, include a video of the script running on your device with Debug mode ON
Recording functionality is available within the app in More options.
Device Info (please fill at-least 'Device model'):

Device model: [Samsung galaxy S10+]
Screen size: [e.g. 1280x720]
Android Version: [e.g. Android 7.1]
RAM: [e.g. 3GB]

Closing comment (2021-08-07T05:37:23Z): Duplicate of #796 😞
Repository: Fate-Grand-Automata/FGA

Issue #1258: FGA not choosing servant after game update.
Created: 2022-07-27T11:36:10Z
Preparation

 I tested the latest release
 I looked at other issues (even the closed ones)
 I read the Troubleshooting Guide

FGO server
CN
FGA build number
1741
Describe the bug
Fgo cn update changed something? ig... it isn't detecting ce or cards? dunno which, i just wanted to farm QP...
Video
https://youtu.be/yZwFqhhVgzE
Device model
MEMU
Android version
7
Screen size
No response
RAM
No response

Duplicate issue #1264: FGA not choosing support servant
Created: 2022-07-29T02:41:33Z
Preparation

 I tested the latest release
 I looked at other issues (even the closed ones)
 I read the Troubleshooting Guide

FGO server
CN
FGA build number
1742
Describe the bug
Game updated and servant selection didn't work. Updated FGA to BUILD: 1742 and restarted my phone. Still have the same issue.
Video

  
    
    

    record.mp4
    
  

  

  


Device model
Galaxy S10+
Android version
12
Screen size
2280x1080
RAM
8GB

Closing comment (2022-07-29T10:09:21Z): Duplicate of #1258
Repository: Fate-Grand-Automata/FGA

Issue #776: Problem with mlb ce (Keleidoscope)
Created: 2021-07-12T15:13:00Z
Before opening an issue:

 I tested the latest release
 I looked at other issues (even the closed ones)
 I read the Troubleshooting Guide
 I'll fill this template properly

I have this problem: even if I check the option to use only mlb ce, the app in game still selects the ce not mlb. I have this problem with the kaleidoscope but i have not tried with other ce.
Device Info

Device model: [Samsung A40]
Screen size: [1080 x 2340 pixel]
Android Version: [Android 11]
RAM: [4 GB]

Duplicate issue #960: Not recognizing mlb kscope
Created: 2021-11-17T09:35:50Z
When given the option to choose any servant but with limit broken scope, it will choose the first scope it sees, limit broken or not. This is with MLB checked option.

Closing comment (2021-11-17T09:40:27Z): Duplicate of #776
If I remember correctly, MLB KScope is one of the things that just doesn't work because the image detection can't handle it.
Repository: Fate-Grand-Automata/FGA

Issue #371: Support for Unlimited Refreshes
Created: 2020-09-10T13:14:58Z
Hi,
I saw this in the Work project, and I think I have an idea of how to set this:
Instead of having the scales (0-50) for prefs.support.maxUpdates reflect the exact number of updates, we can dedicate one value (0 or 50) as the option for "unlimited" and notify users via the description text. Then we can check for that specific value so that it has a different behavior (refreshing without increasing numOfUpdates)


If this sounds good then I can go ahead and contribute a PR.
I just need to know if setting the "unlimited" preference to 0 is better or if 50 is better (or if a new max value is preferred)

Duplicate issue #460: Add option for "Update Support" looping as a fallback
Created: 2020-09-23T08:07:17Z
I'm not sure if this is already a thing, but I didn't notice it in the app. Basically, it would be nice to have a loop update until the app finds the preferred support, if it can't already find a preferred support in the support list.

Closing comment (2020-09-23T10:32:47Z): Duplicate of #371
Repository: FeatureBaseDB/featurebase

Issue #1114: Feature: Row Scaling 
Created: 2018-02-13T21:51:12Z
Description
Explore new methods for improving how pilosa handles massive rowsets.  Resources could be managed a bit more efficiently  with smarter fragment management.
Success criteria (What criteria will consider this ticket closeable?)
Demonstrate responsive queries to multi-billion row dataset

Duplicate issue #1595: Transposed indexes
Created: 2018-08-13T02:02:06Z
I may have misunderstood the statement, but in the OSCON 2017 talk, I believe @jaffee said transposed indexes could be created?
Given an index foo with a field named bar, a frame may look like the following



-
10
11




1
0
1


2
1
0



Where Row(bar=2) would return [10]
The transpose would be:



-
1
2




10
0
1


11
1
0



Which would (theoretically) model an index named bar with a field named foo supporting Row(foo=10) which would return [2].
However this assumption of an index named bar would be surprising since indexes are created explicitly. This would suggest a different method of querying may be necessary to support this implicit transposed index, like RowT(bar=10) which would translate to, "give me the bars where foo is 10" which would be [2].
Not a fully fleshed out idea, but just braindumping based on what I learned about Pilosa today and the use case I have.

Closing comment (2018-08-13T14:20:30Z): @bruth In previous versions of Pilosa we supported "inverse" frames; that's what @jaffee would have been referring to. We decided to remove that feature because of the limitations that it introduced. Pilosa is built to scale horizontally; the number of columns can grow into the billions, but the number of rows is limited by things like memory and data density. If a frame was configured to maintain its inverse version, it became difficult to scale because there would be a limit on the number of columns you could introduce as well (since the dictated the number of rows in the inverse view).
In addition to that limitation, the inverse view could significantly affect import speed.
Because of this, we decided to remove "inverse" frames until/unless we come up with a better way to scale rows without significantly affecting performance. That work is being tracked in #1114.
Repository: FeatureBaseDB/featurebase

Issue #351: Remove '.n' suffix requirement for ranked frames
Created: 2017-02-28T19:24:16Z
Description
Ranked frames should be specified using an option in the frame schema instead of using the .n suffix.
Success criteria (What criteria will consider this ticket closeable?)

 Create a frame using {"options":{"cacheType":"ranked"}} during creation to specify a ranked frame.

Duplicate issue #284: Stop specifying cache type with frame name suffix
Created: 2017-02-02T14:00:48Z
Currently, in order to specify that a frame should have a top-n sorted cache, one must name the frame with a .n suffix (see FrameSuffixRank variable in frame.go). Since we're moving toward explicit creation of frames, we should capture and store a frame's cache type along with its schema and other meta data.

Closing comment (2017-03-08T18:01:52Z): Closing as duplicate of #351
Repository: FeatureBaseDB/featurebase

Issue #333: Lazy loading on startup
Created: 2017-02-21T17:34:20Z
Description
When starting up, pilosa can take a significant amount of time to load its data before being able to respond to requests. It would be desirable to decrease the amount of time from startup to being able to serve a request by doing some kind of lazy loading. This came up when certain queries were causing pilosa to crash and be restarted in a production environment - this would have been much less obvious from the outside (to other non-crashing queries) if pilosa had been able to serve requests in the intervening few seconds while it was starting.
Success criteria (What criteria will consider this ticket closeable?)
The time from startup to accepting connections and serving requests is significantly smaller for large databases.

Duplicate issue #649: Can't use `/debug/pprof` during startup
Created: 2017-06-16T19:43:23Z
Expected behavior
go tool pprof <pilosa_binary> localhost:10101/debug/pprof/profile generates a cpu profile.
Actual behavior
If you issue the above command while pilosa is starting (loading a large index) - before it logs Listening as http://:10101 It times out.
Steps to reproduce the behavior
Start a pilosa instance which has a lot of data on disk (such as the taxi dataset). Then issue the above command before it logs the "listening" line.
Information about your environment (OS/architecture, CPU, RAM, cluster/solo, configuration, etc.)
Seen on linux/amd64 both cluster and solo.

Closing comment (2017-06-21T15:50:58Z): This is related to #333 to some degree - take the discussion on that ticket into account when implementing this.
Repository: FeatureBaseDB/featurebase

Issue #2015: Container iteration bug in roaring functions
Created: 2019-06-18T18:34:01Z
For bugs, please provide the following:
What's going wrong?
For some Roaring Bitmap operations that use iterators under the hood and whose input requires iteration to the next container, the result of the operation may be incorrect.
What was expected?
see below.
Steps to reproduce the behavior
Slice Range
bm := NewBitmap(65536)
start, end := uint64(1), uint64(131072)
fmt.Println(bm.SliceRange(start, end))

>> []
expected [65536]
Count Range
bm := NewBitmap(65536)
start, end := uint64(65536), uint64(2)
fmt.Println(countRangeSlice(a, start, end))

>> 1
expected 0
Shift
bm := NewBitmap(65535, 131073)
bm1, _ := bm.Shift(1)
fmt.Println(bm1.Slice())

>> [131072 131074]
expected [65536 131074]
Information about your environment (OS/architecture, CPU, RAM, cluster/solo, configuration, etc.)
Mac, on Pilosa master.
Success criteria (What criteria will consider this ticket closeable?)
The above functions work as expected. Bonus for test cases written to check for iterating through containers.

Duplicate issue #2013: int range bug in Pilosa
Created: 2019-06-14T16:51:26Z
What's going wrong?
Wrong answer on range query. See steps below:
Fri 06/14 11:44:46:~()$ curl localhost:10101/index/bla -d'{}'
{"success":true}
Fri 06/14 11:48:15:~()$ curl localhost:10101/index/bla/field/aint -d'{"options": {"type": "int", "min": -9223372036854775808, "max": 9223372036854775807}}'
{"success":true}
Fri 06/14 11:48:34:~()$ curl localhost:10101/index/bla/query -d'Set(10, aint=11) Set(100, aint=15)'
{"results":[true,true]}
Fri 06/14 11:48:43:~()$ curl localhost:10101/index/bla/query -d'Row(aint > 100)'
]{"results":[{"attrs":{},"columns":[10,100]}]}

What was expected?
the two values for field aint are 11 and 15 so aint > 100 should return no columns.
Information about your environment (OS/architecture, CPU, RAM, cluster/solo, configuration, etc.)
This is happening in go-pilosa CI tests, and also on my Mac locally. 1.3.0 and v1.3.1

Closing comment (2019-06-18T20:52:22Z): This might be related to #2015.
Repository: FeatureBaseDB/featurebase

Issue #1129: Imports aren't working behind proxy / load balancer
Created: 2018-02-21T19:46:53Z
Expected behavior
Data imported successfully
Actual behavior
2018/02/21 11:54:16 parsing: input.csv
2018/02/21 11:54:16 grouping 22 bits
2018/02/21 11:54:16 importing slice: 0, n=22
Error: import node: host=0.0.0.0:10101, err=Post http://0.0.0.0:10101/import: dial tcp 0.0.0.0:10101: connect: connection refused

Steps to reproduce the behavior
Run import against pilosa endpoint published through a proxy.
Information about your environment (OS/architecture, CPU, RAM, cluster/solo, configuration, etc.)
Solo node, official docker image v0.8.8

Duplicate issue #928: Fragment endpoint should always return scheme
Created: 2017-11-03T18:33:13Z
Expected behavior
The /fragment/nodes endpoint should always return a scheme property in the response json. [Alternatively Node structs in the import library should have a default scheme.]
Actual behavior
When running via the docker container on localhost a request to get fragments returns [{"host":"localhost:10101"}] with no scheme field.
This results in failure to import data for anything that calls Import (for example using pdk/ctl fails).
This is due to the fact that Import calls FragmentNodes which makes a request to get the location of fragments and the client library decodes the response into a Node  struct that has no default for the scheme. When the Node is then used (back in the Import method) the subsequent call to ImportNode fails since there is no scheme.
Steps to reproduce the behavior
Run an instance of pilosa in docker as per the "get started" documentation. Create an index and frame.
Make a request for fragments:
curl "http://localhost:10101/fragment/nodes?index=segment&slice=0"
Response is:
[{"host":"localhost:10101"}]
Note the lack of a protocol field in the response payload.
Information about your environment (OS/architecture, CPU, RAM, cluster/solo, configuration, etc.)
Mac running pilosa locally in docker.
Success criteria (What criteria will consider this ticket closeable?)
All requests to the fragments endpoint consistently return a payload including protocol.

Closing comment (2018-04-17T21:10:35Z): The 0.0.0.0 bind address  issue is being tracked in #1129
Repository: FeatureBaseDB/featurebase

Issue #1352: un-export methods on Fragment
Created: 2018-06-02T03:39:40Z
Description
As part of shrinking the API, there are quite a few methods on Fragment that can be un-exported. Things like FieldSum and ClearBit are examples, but likely most if not all of them. This will require changing the fragment tests to be internal, and to no longer rely on the test package for things like test.MustOpenFragment.
Success criteria (What criteria will consider this ticket closeable?)
Most if not all methods on Fragment are no longer exported. It may also be feasible to un-export Fragment itself.

Duplicate issue #1356: un-export methods on Fragment
Created: 2018-06-05T17:36:15Z
Description
There are several methods on fragment which are exported, but really don't need to be. It seems like they are only used in tests.
We should move fragment_test.go to fragment_internal_test.go and make it part of the pilosa package.
I started to do this, but there are some uses of the test package (like test.MustOpenFragment), as well as a test that relies on the bolt implementation of AttrStore that would need to be refactored.
I think to fully accomplish this, we also need to create an in-memory implementation of AttrStore to use for tests.
Success criteria (What criteria will consider this ticket closeable?)
Fragment methods are un-exported.

Closing comment (2018-06-05T22:30:44Z): duplicate of #1352
Repository: Figma-Linux/figma-linux

Issue #57: Segmentation fault 
Created: 2019-08-21T08:54:31Z
do not open battle crashes, appear in syslog logs. Aug 21 11:41:58 kernel: [150276.592383] figma-linux [22206]: segfault at 0 ip 00007ff1195dd5a1 sp 00007ff0ee096758 error 4 in libc-2.27.so [7ff11944f000 + 1e7000].
Version figma 0.5.3
Ubuntu Version 18.04.3
do you know how to deal with such a problem?

Duplicate issue #60: App immediately closes
Created: 2019-08-30T06:36:30Z
App version: 0.5.4
Operating System (Platform and Version):  deepin os 15.11 based on debian stable

Bug description
i run the app window opens and closes immediatly
Screenshots
If applicable, add screenshots to help explain your problem.

i have the same issue with the snap version. what could be causing this problem?

Closing comment (2019-11-26T14:35:53Z): Dup #57
Repository: Figma-Linux/figma-linux

Issue #57: Segmentation fault 
Created: 2019-08-21T08:54:31Z
do not open battle crashes, appear in syslog logs. Aug 21 11:41:58 kernel: [150276.592383] figma-linux [22206]: segfault at 0 ip 00007ff1195dd5a1 sp 00007ff0ee096758 error 4 in libc-2.27.so [7ff11944f000 + 1e7000].
Version figma 0.5.3
Ubuntu Version 18.04.3
do you know how to deal with such a problem?

Duplicate issue #70: App doesn't launch on Fedora
Created: 2019-10-28T11:00:17Z
App version: I don't even know how to check that
Operating System (Platform and Version): Fedora 30

Bug description
On a lonely starry night, I clicked on the Figma-Linux app icon on my minimalistic GNOME interface window. Nothing happened. I did it again, been doing it for about 3 months now, nothing's happening. Perhaps it was me Einstein was talking about.
Additional context
I'm a Linux noob. Let all jargon be minified. Thanks for your devotion and hard work.

Closing comment (2019-11-26T14:35:33Z): Dup #57
Repository: Figma-Linux/figma-linux

Issue #57: Segmentation fault 
Created: 2019-08-21T08:54:31Z
do not open battle crashes, appear in syslog logs. Aug 21 11:41:58 kernel: [150276.592383] figma-linux [22206]: segfault at 0 ip 00007ff1195dd5a1 sp 00007ff0ee096758 error 4 in libc-2.27.so [7ff11944f000 + 1e7000].
Version figma 0.5.3
Ubuntu Version 18.04.3
do you know how to deal with such a problem?

Duplicate issue #67: Crashes at login screen
Created: 2019-10-03T00:06:54Z
App version: 0.5.6-1
Operating System (Platform and Version): Manjaro 18.1.0 Juhraya

Bug description
When the login screen appear, the application crashes. I see the Google logo, but nothing else renders, then it crashes.
Additional context
Here's the output from dmesg:
[177550.803799] figma-linux[15307]: segfault at 0 ip 00007f7198666c55 sp 00007f71748a9628 error 4 in libc-2.29.so[7f719852d000+14a000]
[177550.803826] audit: type=1701 audit(1570061172.144:806): auid=1000 uid=1000 gid=1001 ses=1 subj==unconfined pid=15201 comm="figma-linux" exe="/opt/figma-bin/figma-linux" sig=11 res=1

Closing comment (2019-11-26T14:34:54Z): Dup #57
Repository: Figma-Linux/figma-linux

Issue #13: Can't launch app on CentOS 7 x64
Created: 2018-09-21T11:51:30Z
App version: 0.2.0
Operating System (Platform and Version): CentOS 7 x64

Bug description
Can't start app:

Duplicate issue #31: Does not launch on Linux Mint
Created: 2019-03-07T08:11:10Z
Linux Mint Cinnamon 64 bit

Bug description
Figma does not launch, when running from terminal the following error is seen:
A JavaScript error occurred in the main process
Uncaught Exception:
Error: Cannot open /opt/figma-linux/resources/app.asar/main/binding.node: Error: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /tmp/.org.chromium.Chromium.BYeE9K)

Closing comment (2019-03-07T09:53:42Z): Hi.
What's version of gcc on your Linux?
dup #13
Repository: Figma-Linux/figma-linux

Issue #139: Figma Desktop App is out of date
Created: 2020-11-25T03:39:57Z
App version: 0.6.3
The output of screenfetch:

           /:-------------:\          jann@localhost.localdomain
        :-------------------::        OS: Fedora 
      :-----------/shhOHbmp---:\      Kernel: x86_64 Linux 5.9.8-200.fc33.x86_64
    /-----------omMMMNNNMMD  ---:     Uptime: 16h 20m
   :-----------sMMMMNMNMP.    ---:    Packages: 1885
  :-----------:MMMdP-------    ---\   Shell: fish 3.1.2
 ,------------:MMMd--------    ---:   Resolution: 3200x1080
 :------------:MMMd-------    .---:   DE: GNOME 3.38.1
 :----    oNMMMMMMMMMNho     .----:   WM: Mutter
 :--     .+shhhMMMmhhy++   .------/   WM Theme: -dark
 :-    -------:MMMd--------------:    GTK Theme: Adwaita [GTK2/3]
 :-   --------/MMMd-------------;     Icon Theme: Adwaita
 :-    ------/hMMMy------------:      Font: Cantarell 11
 :-- :dMNdhhdNMMNo------------;       Disk: 4.5T / 8.3T (55%)
 :---:sdNMMMMNds:------------:        CPU: AMD Ryzen 5 2600 Six-Core @ 12x 3.6GHz
 :------:://:-------------::          GPU: Radeon RX 560 Series (POLARIS11, DRM 3.39.0, 5.9.8-200.fc33.x86_64, LLVM 11.0.0)
 :---------------------://            RAM: 5459MiB / 7966MiB

Type of installed package (Snap, AppImage, deb, rpm, pacman): rpm

Bug description
When starting figma-linux, an error stating "Figma Desktop App is out of date!" appears, preventing the user from opening the app.
Screenshots

Duplicate issue #143: Out Of Date
Created: 2020-11-25T11:39:42Z

Closing comment (2020-11-25T17:52:30Z): Dup #139
Repository: Figma-Linux/figma-linux

Issue #255: Font helper support (enhancement)
Created: 2022-01-21T11:22:27Z
Hi, could you please add support for this font helper: https://github.com/tryvin/figma-linux-font-helper

Duplicate issue #255: Font helper support (enhancement)
Created: 2022-01-21T11:22:27Z
Hi, could you please add support for this font helper: https://github.com/tryvin/figma-linux-font-helper

Closing comment (2023-09-12T23:59:57Z): I'm running into this same issue where the variations of the fonts are loaded with their full postscript name instead of the font name (same as #255 (comment)).
It looks like the postscript name is being returned in this function 
  
    
      figma-linux/src/main/Fonts/TTF.ts
    
    
         Line 144
      in
      afcdbf2
    
  
  
    

        
          
           public getData(): Fonts.IFontsFigmaItem { 
        
    
  

 . However, I don't see the fontName, which I think is what should be displayed, making its way through the return chain.
What changes need to be made to load font families such that they match the other Figma clients? Would the maintainers be open to spinning it out into a separate ticket?
Repository: Figma-Linux/figma-linux

Issue #93: All characters in Gnome file dialog (export) are broken
Created: 2020-03-02T04:17:52Z
App version: 0.6.2
Operating System (Platform and Version): Fedora 31
Type of installed package: Snap

Bug description
All characters in Gnome file dialog (export) are broken
Screenshots

Duplicate issue #120: Sving file and Import objects fonts fail
Created: 2020-08-19T17:06:56Z
Hello.
When i try to save file or import object, i see that (picture).
https://b.radikal.ru/b36/2008/ca/8ce3791d129b.png
OS: KDE Neon.

Closing comment (2020-09-02T20:47:03Z): Dup #93