text:
Create a new world and teleport to the new world will crash server

Server Plugins: Multiverse-Core
Create a new world and teleport to the new world will crash server
[22:56:06 ERROR]: [ca.spottedleaf.moonrise.common.util.TickThread] Thread serverlevel-tick-worker [world] failed main thread check: Loading in poi chunk off-main @ world test chunkX: -4 chunkZ: -3 - Is tick thread? true; Is server level tick thread? true; Currently ticking level: world; Is iterating over levels? true; Are we going to hard throw? true
java.lang.Throwable: null
        at ca.spottedleaf.moonrise.common.util.TickThread.ensureTickThread(TickThread.java:49) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.moonrise.patches.chunk_system.level.poi.PoiChunk.load(PoiChunk.java:52) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.moonrise.patches.chunk_system.scheduling.task.ChunkFullTask.run(ChunkFullTask.java:54) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.concurrentutil.executor.standard.PrioritisedThreadedTaskQueue$PrioritisedTask.executeInternal(PrioritisedThreadedTaskQueue.java:351) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.concurrentutil.executor.standard.PrioritisedThreadedTaskQueue.executeTask(PrioritisedThreadedTaskQueue.java:118) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.moonrise.patches.chunk_system.scheduling.ChunkTaskScheduler.executeMainThreadTask(ChunkTaskScheduler.java:370) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at net.minecraft.server.level.ServerChunkCache$MainThreadExecutor.pollTask(ServerChunkCache.java:788) ~[?:?]
        at net.minecraft.server.level.ServerChunkCache.pollTask(ServerChunkCache.java:340) ~[?:?]
        at net.minecraft.server.MinecraftServer.tickMidTickTasks(MinecraftServer.java:378) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at net.minecraft.server.MinecraftServer.moonrise$executeMidTickTasks(MinecraftServer.java:399) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at net.minecraft.server.level.ServerLevel.moonrise$midTickTasks(ServerLevel.java:345) ~[?:?]
        at net.minecraft.server.level.ServerLevel.lambda$tick$4(ServerLevel.java:779) ~[?:?]
        at net.minecraft.world.level.entity.EntityTickList.forEach(EntityTickList.java:48) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at net.minecraft.server.level.ServerLevel.tick(ServerLevel.java:746) ~[?:?]
        at net.minecraft.server.MinecraftServer.lambda$tickChildren$19(MinecraftServer.java:1849) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572) ~[?:?]
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317) ~[?:?]
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
        at java.base/java.lang.Thread.run(Thread.java:1583) ~[?:?]
[22:56:06 ERROR]: [ChunkTaskScheduler] Chunk system error at chunk (-4,-3), holder: NewChunkHolder{world=test, chunkX=-4, chunkZ=-3, entityChunkFromDisk=false, lastChunkCompletion={chunk_class=net.minecraft.world.level.chunk.ProtoChunk,status=minecraft:spawn}, currentGenStatus=minecraft:spawn, requestedGenStatus=minecraft:full, generationTask=ChunkProgressionTask{class: ca.spottedleaf.moonrise.patches.chunk_system.scheduling.task.ChunkFullTask, for world: test, chunk: (-4,-3), hashcode: 296571884, priority: COMPLETING, status: minecraft:full, scheduled: true}, generationTaskStatus=minecraft:full, priority=null, priorityLocked=false, neighbourRequestedPriority=null, effective_priority=null, oldTicketLevel=33, currentTicketLevel=33, totalNeighboursUsingThisChunk=41, fullNeighbourChunksLoadedBitset=32399872, currentChunkStatus=INACCESSIBLE, pendingChunkStatus=INACCESSIBLE, is_unload_safe=ticket_level, killed=false}, exception:
java.lang.Throwable: java.lang.IllegalStateException: Loading in poi chunk off-main
        at ca.spottedleaf.moonrise.patches.chunk_system.scheduling.ChunkTaskScheduler.unrecoverableChunkSystemFailure(ChunkTaskScheduler.java:336) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.moonrise.patches.chunk_system.scheduling.NewChunkHolder.lambda$setGenerationTask$4(NewChunkHolder.java:1622) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.moonrise.patches.chunk_system.scheduling.task.ChunkProgressionTask.complete0(ChunkProgressionTask.java:91) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.moonrise.patches.chunk_system.scheduling.task.ChunkProgressionTask.complete(ChunkProgressionTask.java:74) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.moonrise.patches.chunk_system.scheduling.task.ChunkFullTask.run(ChunkFullTask.java:85) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.concurrentutil.executor.standard.PrioritisedThreadedTaskQueue$PrioritisedTask.executeInternal(PrioritisedThreadedTaskQueue.java:351) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.concurrentutil.executor.standard.PrioritisedThreadedTaskQueue.executeTask(PrioritisedThreadedTaskQueue.java:118) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.moonrise.patches.chunk_system.scheduling.ChunkTaskScheduler.executeMainThreadTask(ChunkTaskScheduler.java:370) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at net.minecraft.server.level.ServerChunkCache$MainThreadExecutor.pollTask(ServerChunkCache.java:788) ~[?:?]
        at net.minecraft.server.level.ServerChunkCache.pollTask(ServerChunkCache.java:340) ~[?:?]
        at net.minecraft.server.MinecraftServer.tickMidTickTasks(MinecraftServer.java:378) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at net.minecraft.server.MinecraftServer.moonrise$executeMidTickTasks(MinecraftServer.java:399) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at net.minecraft.server.level.ServerLevel.moonrise$midTickTasks(ServerLevel.java:345) ~[?:?]
        at net.minecraft.server.level.ServerLevel.lambda$tick$4(ServerLevel.java:779) ~[?:?]
        at net.minecraft.world.level.entity.EntityTickList.forEach(EntityTickList.java:48) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at net.minecraft.server.level.ServerLevel.tick(ServerLevel.java:746) ~[?:?]
        at net.minecraft.server.MinecraftServer.lambda$tickChildren$19(MinecraftServer.java:1849) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572) ~[?:?]
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317) ~[?:?]
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
        at java.base/java.lang.Thread.run(Thread.java:1583) ~[?:?]
Caused by: java.lang.IllegalStateException: Loading in poi chunk off-main
        at ca.spottedleaf.moonrise.common.util.TickThread.ensureTickThread(TickThread.java:51) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.moonrise.patches.chunk_system.level.poi.PoiChunk.load(PoiChunk.java:52) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.moonrise.patches.chunk_system.scheduling.task.ChunkFullTask.run(ChunkFullTask.java:54) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        ... 17 more
[22:56:06 ERROR]: Negative index in crash report handler (20/22)
[22:56:06 ERROR]: Encountered an unexpected exception
java.lang.RuntimeException: Chunk system crash propagated to tick()
        at net.minecraft.server.MinecraftServer.runServer(MinecraftServer.java:1352) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at net.minecraft.server.MinecraftServer.lambda$spin$0(MinecraftServer.java:336) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at java.base/java.lang.Thread.run(Thread.java:1583) ~[?:?]
Caused by: java.lang.RuntimeException: Chunk system crash propagated from unrecoverableChunkSystemFailure
        at ca.spottedleaf.moonrise.patches.chunk_system.scheduling.ChunkTaskScheduler.unrecoverableChunkSystemFailure(ChunkTaskScheduler.java:365) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.moonrise.patches.chunk_system.scheduling.NewChunkHolder.lambda$setGenerationTask$4(NewChunkHolder.java:1622) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.moonrise.patches.chunk_system.scheduling.task.ChunkProgressionTask.complete0(ChunkProgressionTask.java:91) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.moonrise.patches.chunk_system.scheduling.task.ChunkProgressionTask.complete(ChunkProgressionTask.java:74) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.moonrise.patches.chunk_system.scheduling.task.ChunkFullTask.run(ChunkFullTask.java:85) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.concurrentutil.executor.standard.PrioritisedThreadedTaskQueue$PrioritisedTask.executeInternal(PrioritisedThreadedTaskQueue.java:351) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.concurrentutil.executor.standard.PrioritisedThreadedTaskQueue.executeTask(PrioritisedThreadedTaskQueue.java:118) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.moonrise.patches.chunk_system.scheduling.ChunkTaskScheduler.executeMainThreadTask(ChunkTaskScheduler.java:370) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at net.minecraft.server.level.ServerChunkCache$MainThreadExecutor.pollTask(ServerChunkCache.java:788) ~[?:?]
        at net.minecraft.server.level.ServerChunkCache.pollTask(ServerChunkCache.java:340) ~[?:?]
        at net.minecraft.server.MinecraftServer.tickMidTickTasks(MinecraftServer.java:378) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at net.minecraft.server.MinecraftServer.moonrise$executeMidTickTasks(MinecraftServer.java:399) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at net.minecraft.server.level.ServerLevel.moonrise$midTickTasks(ServerLevel.java:345) ~[?:?]
        at net.minecraft.server.level.ServerLevel.lambda$tick$4(ServerLevel.java:779) ~[?:?]
        at net.minecraft.world.level.entity.EntityTickList.forEach(EntityTickList.java:48) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at net.minecraft.server.level.ServerLevel.tick(ServerLevel.java:746) ~[?:?]
        at net.minecraft.server.MinecraftServer.lambda$tickChildren$19(MinecraftServer.java:1849) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572) ~[?:?]
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317) ~[?:?]
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
        ... 1 more
Caused by: net.minecraft.ReportedException: Chunk system error
        at ca.spottedleaf.moonrise.patches.chunk_system.scheduling.ChunkTaskScheduler.unrecoverableChunkSystemFailure(ChunkTaskScheduler.java:342) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.moonrise.patches.chunk_system.scheduling.NewChunkHolder.lambda$setGenerationTask$4(NewChunkHolder.java:1622) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.moonrise.patches.chunk_system.scheduling.task.ChunkProgressionTask.complete0(ChunkProgressionTask.java:91) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.moonrise.patches.chunk_system.scheduling.task.ChunkProgressionTask.complete(ChunkProgressionTask.java:74) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.moonrise.patches.chunk_system.scheduling.task.ChunkFullTask.run(ChunkFullTask.java:85) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.concurrentutil.executor.standard.PrioritisedThreadedTaskQueue$PrioritisedTask.executeInternal(PrioritisedThreadedTaskQueue.java:351) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.concurrentutil.executor.standard.PrioritisedThreadedTaskQueue.executeTask(PrioritisedThreadedTaskQueue.java:118) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.moonrise.patches.chunk_system.scheduling.ChunkTaskScheduler.executeMainThreadTask(ChunkTaskScheduler.java:370) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at net.minecraft.server.level.ServerChunkCache$MainThreadExecutor.pollTask(ServerChunkCache.java:788) ~[?:?]
        at net.minecraft.server.level.ServerChunkCache.pollTask(ServerChunkCache.java:340) ~[?:?]
        at net.minecraft.server.MinecraftServer.tickMidTickTasks(MinecraftServer.java:378) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at net.minecraft.server.MinecraftServer.moonrise$executeMidTickTasks(MinecraftServer.java:399) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at net.minecraft.server.level.ServerLevel.moonrise$midTickTasks(ServerLevel.java:345) ~[?:?]
        at net.minecraft.server.level.ServerLevel.lambda$tick$4(ServerLevel.java:779) ~[?:?]
        at net.minecraft.world.level.entity.EntityTickList.forEach(EntityTickList.java:48) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at net.minecraft.server.level.ServerLevel.tick(ServerLevel.java:746) ~[?:?]
        at net.minecraft.server.MinecraftServer.lambda$tickChildren$19(MinecraftServer.java:1849) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572) ~[?:?]
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317) ~[?:?]
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
        ... 1 more
Caused by: java.lang.IllegalStateException: Loading in poi chunk off-main
        at ca.spottedleaf.moonrise.common.util.TickThread.ensureTickThread(TickThread.java:51) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.moonrise.patches.chunk_system.level.poi.PoiChunk.load(PoiChunk.java:52) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.moonrise.patches.chunk_system.scheduling.task.ChunkFullTask.run(ChunkFullTask.java:54) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.concurrentutil.executor.standard.PrioritisedThreadedTaskQueue$PrioritisedTask.executeInternal(PrioritisedThreadedTaskQueue.java:351) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.concurrentutil.executor.standard.PrioritisedThreadedTaskQueue.executeTask(PrioritisedThreadedTaskQueue.java:118) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at ca.spottedleaf.moonrise.patches.chunk_system.scheduling.ChunkTaskScheduler.executeMainThreadTask(ChunkTaskScheduler.java:370) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at net.minecraft.server.level.ServerChunkCache$MainThreadExecutor.pollTask(ServerChunkCache.java:788) ~[?:?]
        at net.minecraft.server.level.ServerChunkCache.pollTask(ServerChunkCache.java:340) ~[?:?]
        at net.minecraft.server.MinecraftServer.tickMidTickTasks(MinecraftServer.java:378) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at net.minecraft.server.MinecraftServer.moonrise$executeMidTickTasks(MinecraftServer.java:399) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at net.minecraft.server.level.ServerLevel.moonrise$midTickTasks(ServerLevel.java:345) ~[?:?]
        at net.minecraft.server.level.ServerLevel.lambda$tick$4(ServerLevel.java:779) ~[?:?]
        at net.minecraft.world.level.entity.EntityTickList.forEach(EntityTickList.java:48) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at net.minecraft.server.level.ServerLevel.tick(ServerLevel.java:746) ~[?:?]
        at net.minecraft.server.MinecraftServer.lambda$tickChildren$19(MinecraftServer.java:1849) ~[purpurasync-1.21.1.jar:1.21.1-DEV-6823c53]
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572) ~[?:?]
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317) ~[?:?]
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
        ... 1 more

@Happy-FZM Which version are you using?

Server name: PurpurAsync
Version: 1.21.1-DEV-6823c53 (MC: 1.21.1)
API version: 1.21.1-R0.1-SNAPSHOT
Github commit: 6823c53

@Happy-FZM Which version are you using?

Server name: PurpurAsync Version: 1.21.1-DEV-6823c53 (MC: 1.21.1) API version: 1.21.1-R0.1-SNAPSHOT Github commit: 6823c53

This version is not ready for use and I am still rewriting the patch for parallel worlds

@Happy-FZM Which version are you using?

Server name: PurpurAsync Version: 1.21.1-DEV-6823c53 (MC: 1.21.1) API version: 1.21.1-R0.1-SNAPSHOT Github commit: 6823c53

This version is not ready for use and I am still rewriting the patch for parallel worlds

Okay but I think this bug maybe caused by some patches upstream (Purpur), I tried to switch the upstream back to Paper it did not reproduce this bug

@Happy-FZM Which version are you using?

Server name: PurpurAsync Version: 1.21.1-DEV-6823c53 (MC: 1.21.1) API version: 1.21.1-R0.1-SNAPSHOT Github commit: 6823c53

This version is not ready for use and I am still rewriting the patch for parallel worlds

Okay but I think this bug maybe caused by some patches upstream (Purpur), I tried to switch the upstream back to Paper it did not reproduce this bug

I have the same assumptions, I will find out where the problem is.

@Happy-FZM Which version are you using?

Server name: PurpurAsync Version: 1.21.1-DEV-6823c53 (MC: 1.21.1) API version: 1.21.1-R0.1-SNAPSHOT Github commit: 6823c53

This version is not ready for use and I am still rewriting the patch for parallel worlds

Okay but I think this bug maybe caused by some patches upstream (Purpur), I tried to switch the upstream back to Paper it did not reproduce this bug

I have the same assumptions, I will find out where the problem is.

Great!

One of the Purpur patches radically changes the way chunks work, so maybe I'll switch to a patch from another fork: https://github.com/CraftCanvasMC/Canvas/blob/master/patches/server/0048-Multithreaded-Ticking.patch

The patch looks good


text:
Compiler errors due to old 0.9 version of openssl crate.

My system has OpenSSL 1.1.1, and openssl crate 0.9 doesn't work with it. Check out the related issue here:
https://github.com/sfackler/rust-openssl/issues/987
That issue has been linked to several other issues like this one for crates with the same issue as frank_jwt.
Thanks!

While openssl-rust crate dependency has been bumped to 0.10 in b5dc47ed608448c7c6a02f97e7f2140548220336, crates.io index wasn't updated, so cargo thinks there were no updates to this crate. Perhaps a new release is in order?

Just submitted a PR to resolve this. #46

I suspect it's not reflected the change because its a < 1.0 release, therefore Cargo can not assume it's BC safe.
For those looking for a work around, you can use @koala-kalda's branch temporarily by changing you Cargo.lock to use his commit:
frank_jwt = { git = "https://github.com/koala-kalda/frank_jwt", rev = "af4f3480fa26f628519712df719470feb7654896" }

I was blocked, too, with my Rocket project but the workaround helped.
Looking forward to seeing #46 merged, thanks! :+1:

openssl = "0.10.15"

source: gharchive/issue

authors: GildedHonour Gisleburt apiraino freiguy1 koala-kalda mbelop

license_type: permissive

license_source: bigquery


text:
When posting a review comment fails, make sure the text does not get lost

Is just posted a review comment which failed to be posted, and since the keyboard and input bar was already dismissed, I lost the whole post 😭.
Either we can have the message be posted with a “not sent” state (and a retry option) or at least be able to recover the text from the dismissed input bar somehow.

Bug Report Dump (Auto-generated)

Version 1.19.0 (1524439576)
Device: iPad7,3 (iOS 11.3)
TestFlight: false

I dig this. @BasThomas want to give it a shot? Maybe we just expose this cache() function so we can manually do caching? Or maybe we move posting/caching out to its own thing entirely (w/in the client or something).

authors: BasThomas rnystrom

repo: GitHawkApp/GitHawk

license: MIT

license_source: github-api


text:
Asss

Zz
Sent with GitHawk

Sent with GitHawk


text:
GUI broken?

I don't know if this is an issue on my side but since the interface changed I have parts of the GUI cut off by the window. As well as some text values being cut off weirdly. I am running python 3.8.10 on KDE neon 5.25. I tried to look in to the code but I didn't find anything looking out of place, also I am not familiar with tk enough to know. Any ideas what I could try to fix this? Changing the window size does nothing...

I'm not all that good in tkinter myself.
Can you try to add in interface/__init__.py the geometry such that it looks like:
# Make the window
self.root = Tk()
self.root.geometry("1570x770")
# Make the title that will appear in the top left
self.root.wm_title("Raspberry PI PICO PIO Emulation")

For me, that displays the whole window and it allows resizing.
That probably doesn't solve the misalignment in the frame with "Clock=0" on top. That frame is built in the file interface/_mid_frame.py. It calls various UI elements in interface/_interface_item.py. In that file, in the class "Interface_Item" a width parameter is set. I suspect that it goes wrong with the width somehow. You can try to set the widths in calls such as
super().__init__(frame, display_name, row, col, 40)
in class Var_List and  class Var_List_IRQ. Try changing the number 40.

I tried that on my own already but it doesn't help, even if I set a higher window size like 1800x800 the added space is just filled with white (same as when I try to resize). Changing values in  super().__init__(frame, display_name, row, col, 40) did do something so I will have to investigate that further and try to find optimal values for me. (But tbh viewing the FIFOs is more important to be atm, the small snippets shown for the names of the variables are currecntly sufficient for me to guess what it is). Below is what a higher window size looks like.

I'm not sure what the cause is. I'm using:
Linux Mint 20.3 Cinnamon
python 3.8.10
tkinter 8.6.10
Could there be an issue with the fonts that are used? I noticed that in  _mid_frame.py I use a specific font. Maybe just after self.root = Tk() you can set a default font by self.root.option_add("*Font", "aerial 10"). That doesn't help with the misalignment, but maybe it does help with the missing information.

Yeah this is very weird since I am using the exact same python and tk version, the for setting didn't do anything unfortunately. I guess I'll try to look in to it later and maybe submit a PR if I manage to get down to the origin of this.

no reactions in a year -> close

authors: GitJer diminDDL


text:
动态设置主题不支持css module

使用了css module 的例子：

src/setCustomThemeDep.js saveThemeOptions sourceThemeStyle
被:global{}包裹的样式，在提取后类名多了:global

没有被:global{}包裹的样式，提取的是编写代码的时候的类名

::v-deep 这个也被打包进去

authors: BoxiTon ctocto

repo: GitOfZGT/some-loader-utils


text:
🛑 torrentzap is down

In 64861e4, torrentzap (torrentzap.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: torrentzap is back up in 984be00 after 12 minutes.


text:
🛑 twoc is down

In 482556f, twoc (twoc.co.uk) was down:

HTTP code: 0
Response time: 0 ms

Resolved: twoc is back up in 4e09009 after 19 minutes.


text:
🛑 detonics is down

In ca9a7b1, detonics (detonics.com) was down:

HTTP code: 403
Response time: 555 ms

Resolved: detonics is back up in b2aaf58 after 37 minutes.


text:
🛑 orkut is down

In 2fa3e92, orkut (orkut.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in bb5d085.


text:
🛑 orkut is down

In 31a2669, orkut (orkut.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in 06e43fc.


text:
🛑 orkut is down

In 54f6194, orkut (orkut.com.br) was down:

HTTP code: 404
Response time: 124 ms

Resolved: orkut is back up in fe14257.


text:
🛑 orkut is down

In 58ccb51, orkut (orkut.com.br) was down:

HTTP code: 404
Response time: 377 ms

Resolved: orkut is back up in 23db5fe.


text:
🛑 orkut is down

In 634f8c6, orkut (orkut.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in a072302.


text:
🛑 orkut is down

In c73e688, orkut (orkut.com.br) was down:

HTTP code: 403
Response time: 237 ms

Resolved: orkut is back up in a2e5eca.


text:
🛑 orkut is down

In 1251d3e, orkut (orkut.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in 516c48b.


text:
🛑 orkut is down

In 975e8e2, orkut (orkut.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in 6b61cc9.


text:
🛑 ojolink is down

In 1a2945f, ojolink (ojolink.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ojolink is back up in eab6369.


text:
🛑 orkut is down

In 8a25e10, orkut (orkut.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in db61ba0.


text:
🛑 orkut is down

In 5195b55, orkut (orkut.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in 999b37d.


text:
🛑 mynewsize is down

In 52be1ed, mynewsize (mynewsize.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: mynewsize is back up in 5dc7583.


text:
🛑 orkut is down

In ad09851, orkut (orkut.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in d0884cb.


text:
🛑 orkut is down

In 088ab03, orkut (orkut.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in ae77f89.


text:
🛑 penispedia is down

In 962b518, penispedia (penispedia.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: penispedia is back up in 35917af.


text:
🛑 orkut is down

In 77fbcc7, orkut (orkut.com.br) was down:

HTTP code: 429
Response time: 1056 ms

Resolved: orkut is back up in 889947b.


text:
🛑 adult-mate is down

In 159ca8f, adult-mate (adult-mate.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: adult-mate is back up in a4c70f0.


text:
🛑 sohu is down

In c6e57e3, sohu (sohu.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: sohu is back up in ff7948c.


text:
🛑 adult-mate is down

In bf793cb, adult-mate (adult-mate.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: adult-mate is back up in 968b3f0.


text:
🛑 inkcityusa is down

In 975e2a2, inkcityusa (inkcityusa.com) was down:

HTTP code: 502
Response time: 496 ms

Resolved: inkcityusa is back up in d553ea0.


text:
🛑 orkut is down

In ba82735, orkut (orkut.com.br) was down:

HTTP code: 429
Response time: 803 ms

Resolved: orkut is back up in 0c88f72.


text:
🛑 nedis is down

In cd06208, nedis (nedis.nl) was down:

HTTP code: 500
Response time: 4682 ms

Resolved: nedis is back up in 46f445e.


text:
🛑 orkut is down

In 4c26347, orkut (orkut.com.br) was down:

HTTP code: 429
Response time: 816 ms

Resolved: orkut is back up in c00a0f3.


text:
🛑 orkut is down

In b8e22bd, orkut (orkut.com.br) was down:

HTTP code: 429
Response time: 812 ms

Resolved: orkut is back up in 49e3939.


text:
🛑 orkut is down

In 79a97e3, orkut (orkut.com.br) was down:

HTTP code: 429
Response time: 787 ms

Resolved: orkut is back up in 8721a9d.


text:
🛑 ojolink is down

In b144391, ojolink (ojolink.net) was down:

HTTP code: 403
Response time: 483 ms

Resolved: Ojolink is back up in b6b0754.


text:
🛑 orkut is down

In d7eaf1f, orkut (orkut.com.br) was down:

HTTP code: 429
Response time: 687 ms

Resolved: orkut is back up in 21a8256.


text:
🛑 sohu is down

In bf0a5fd, sohu (sohu.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: sohu is back up in d058946.


text:
🛑 ojolink is down

In e251490, ojolink (ojolink.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ojolink is back up in bbbd07a.


text:
🛑 ojolink is down

In d0cb142, ojolink (ojolink.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ojolink is back up in 04848af.


text:
🛑 xxlhd is down

In 5b8bf43, xxlhd (xxlhd.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: xxlhd is back up in 944fb9b.


text:
🛑 ojolink is down

In b405cb6, ojolink (ojolink.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ojolink is back up in 44e1e1b.


text:
🛑 ojolink is down

In 1914c93, ojolink (ojolink.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ojolink is back up in e85efec.


text:
🛑 baidu is down

In 75b79f2, baidu (baidu.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: baidu is back up in f2a139d.


text:
🛑 youjizz is down

In 8bc1ed3, youjizz (youjizz.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: youjizz is back up in 9550a0b after 48 minutes.


text:
🛑 ojolink is down

In 6c9446d, ojolink (ojolink.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ojolink is back up in e2197de after 40 minutes.


text:
🛑 ojolink is down

In 6fb050c, ojolink (ojolink.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ojolink is back up in c53e374 after 8 minutes.


text:
🛑 torrentzap is down

In c8dcd39, torrentzap (torrentzap.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: torrentzap is back up in ebe6191 after 16 minutes.


text:
🛑 ojolink is down

In 2eb1db0, ojolink (ojolink.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ojolink is back up in e429487 after 22 minutes.


text:
🛑 twoc is down

In 415a405, twoc (twoc.co.uk) was down:

HTTP code: 0
Response time: 0 ms

Resolved: twoc is back up in ea9be0b after 1 hour, 47 minutes.


text:
🛑 orkut is down

In bc05ea1, orkut (orkut.co.in) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in 2f6932b after 9 minutes.


text:
🛑 orkut is down

In f538d9e, orkut (orkut.co.in) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in 735e1eb after 14 minutes.


text:
🛑 orkut is down

In dd49003, orkut (orkut.co.in) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in eb57048 after 11 minutes.


text:
🛑 ojolink is down

In e80c2c7, ojolink (ojolink.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ojolink is back up in b8a20a5 after 10 minutes.


text:
🛑 torrentzap is down

In 7336eab, torrentzap (torrentzap.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: torrentzap is back up in b18fc54 after 45 minutes.


text:
🛑 coverups is down

In 8bc3172, coverups (coverups.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: coverups is back up in 151a692 after 18 minutes.


text:
🛑 orkut is down

In bab53cb, orkut (orkut.co.in) was down:

HTTP code: 0
Response time: 0 ms

Resolved: orkut is back up in f07499a after 8 minutes.


text:
Investigate AND verify stuck & missing donations

On thursday/friday a user reported their donations were not showing up on ETH mainnet to this project
https://giveth.io/project/emergency-relief-fund-for-brazil-floods
I was able to confirm this by making a donation myself in ETH to their project on mainnet, I cannot find the donation in 'my donations' or on the project table, nor in the back-up service.
Here are the three donations we know of that we're not caught anywhere:
https://etherscan.io/tx/0x331ff224c7e4dcc3ce9bb6aa6b3a67e1d7b1c7f1c27e6fdead150fd09a6499b6
https://etherscan.io/tx/0xf1a4fb4c446c25529fed988c83381db41fd6cbbe8aae69a58f2a93a60a8b9f73
https://etherscan.io/tx/0x0373f7efaeb12c205e2c26f2b14a49194b9e619c6728c8a5a4f8cf36f635ef6f
Alternatively, when I was testing donations to other projects on ETH mainnet my donations show up in my donations but they are stuck in a pending state, I also cannot find them in the back-up service. I made some donations on Optimism mainnet and encountered no issues for comarison.

Here are the txs for my stuck pending donations:
https://etherscan.io/tx/0xc81021a481b1a21947b1aed7199cd7febdd662cd9a4ee839eb734849b59b24c2
https://etherscan.io/tx/0x5c4cab8d517393178a6f59af693185848c57b21975710cb71f706e8984b117db

I tested today, late friday making a donation on eth mainnet this donation was successful and show on my donations and the projects donations table. however the previous donations on eth mainnet do not show.
How did this happen? We should 1st add the missing donations into our DB. 2nd we need to investigate how this happens that donations are stuck as pending and how it can occuer that other donations are just not caught by any service at all, but only for eth mainnet

Also, there is 61 failed donations in the back-up service that needed to be checked they have been added back to our UI! This is from last week when the donation verification service went down unexpectedly.

@divine-comedian
I checked the DB for your first three transactions (https://etherscan.io/tx/0x331ff224c7e4dcc3ce9bb6aa6b3a67e1d7b1c7f1c27e6fdead150fd09a6499b6, https://etherscan.io/tx/0xf1a4fb4c446c25529fed988c83381db41fd6cbbe8aae69a58f2a93a60a8b9f73,
https://etherscan.io/tx/0x0373f7efaeb12c205e2c26f2b14a49194b9e619c6728c8a5a4f8cf36f635ef6f)
We have them in the DB in draft_donation table, and they are not matched(Still pending) so this is the problem that is why we haven't matched them although they have been successful.
And about the other two TXs that @divine-comedian mentioned, now we have the TXs in our db for those, so there isn't any problem related to them
https://etherscan.io/tx/0xc81021a481b1a21947b1aed7199cd7febdd662cd9a4ee839eb734849b59b24c2
https://etherscan.io/tx/0x5c4cab8d517393178a6f59af693185848c57b21975710cb71f706e8984b117db
TL;DR
Unfortunately, our draft donation service doesn't work properly.
I will post more details as I find any reason

Thanks @mohammadranjbarz - unfortunately I was not able to replicate the issue @divine-comedian was facing (my donation showed instantly and as complete) which leads me to concur with @mohammadranjbarz that we need to take a look at backup service.
I was investigating a lead regarding outdated infura endpoints (which I would still like to revisit, but need someone from frontend to take a look) but seeing it works now I am assuming the problem was temporary. I did check for incidents on infuras side for the relevant time, but nothing out of the ordinary.

So far we're missing the following donations:
https://giveth.io/project/emergency-relief-fund-for-brazil-floods

[ ] https://etherscan.io/tx/0x0373f7efaeb12c205e2c26f2b14a49194b9e619c6728c8a5a4f8cf36f635ef6f
[ ] https://etherscan.io/tx/0xf1a4fb4c446c25529fed988c83381db41fd6cbbe8aae69a58f2a93a60a8b9f73

https://giveth.io/es/project/skatehive-skateboarding-community?tab=donations

[ ] https://etherscan.io/tx/0x75558bed003bb9b55c4ceaddce6119f228db8ec217bb90a414afd0bc1cb97965
[ ] https://gnosisscan.io/tx/0xfa65ef0a52e2f3b96c5802dcee4783858511989b7235035e8cab4d527fa15a1a

So far from user reports we're missing the following donations:
https://giveth.io/project/emergency-relief-fund-for-brazil-floods

[ ]  https://etherscan.io/tx/0x0373f7efaeb12c205e2c26f2b14a49194b9e619c6728c8a5a4f8cf36f635ef6f
[ ]  https://etherscan.io/tx/0xf1a4fb4c446c25529fed988c83381db41fd6cbbe8aae69a58f2a93a60a8b9f73

https://giveth.io/es/project/skatehive-skateboarding-community?tab=donations

[ ]  https://etherscan.io/tx/0x75558bed003bb9b55c4ceaddce6119f228db8ec217bb90a414afd0bc1cb97965
[ ]  https://gnosisscan.io/tx/0xfa65ef0a52e2f3b96c5802dcee4783858511989b7235035e8cab4d527fa15a1a

@divine-comedian Now about 70 donations have been created by draft donation service and got verified, four TXs that you already said 3 of them have been added but the fourth one has not matched yet, so this problem is almost fixed, but not 100%,  I'm still working

@mohammadranjbarz when you merge this today, all the missed donations should be considered, right? wondering because GIvbacks and QF data analysis are blocked 😅

@mohammadranjbarz when you merge this today, all the missed donations should be considered, right? wondering because GIvbacks and QF data analysis are blocked 😅

Yess,  I just need to check the recurring donations streams, it would work but I need to check the documents in the DB

what's the status on this?

@maryjaf to confirm if this is working on staging.

@maryjaf to confirm if this is working on staging.

my missing donation to https://giveth.io/project/commons-stackproject on 6 May,  have been added correctly
but for other donations for any users, I don't know how can I check @mohammadranjbarz

There is just one transaction I made here that needs to be added manually since it didn't appear caught in any service
#1580

@CarlosQ96 can you pls take this up as @mohammadranjbarz is not well.

Mohammad adding in manually the one missing transaction, we can close this one.

authors: divine-comedian geleeroyale jainkrati laurenluz maryjaf mohammadranjbarz

repo: Giveth/impact-graph


text:
feat: iterator helpers for driver interfaces

this is just a little thing that I didn't want to get in the way of anything else. Seems like this API would be useful in a number of cases.

What's the use case? Using block_on for getting batches from a stream probably isn't what we want to be doing.

yeah I pulled this out of the previous PR because I thought it would be more controversial.
I wanted to have an async and a sync interface, just for ease of use (mostly these are going to be used in testing/etc.... this (relative to the other PRs in this sequence is optional)

I don't think it's worth trying to have a sync interface for this. block_on can easily lead to deadlocks and generally pretty inefficient here (all would block the entire thread even if the stream isn't producing batches).
all could also be replaced with collect: https://docs.rs/futures/latest/futures/stream/trait.StreamExt.html#method.collect (still async though)

source: gharchive/pull-request

authors: scsmithr tychoish

repo: GlareDB/glaredb


text:
Repository organization

It's difficult to see how your software files all tie together, perhaps keep them all in a singular folder?

I have now rearranged them into a single folder and added documentation.

authors: SimoneMarcigaglia SmartMilk


text:
Entity destory packet is not send when disconnecting

When a player gets disconnected or is kicked, the EntitiesDestoryMessage is not broadcasted to all clients. When interacting with the player the servers notices that there is no entity: Player Paulomart tried to attack an entity that does not exist

Is it possible that no entities are removed? I think it should be done it pulse() but could not find anything?

fixed in https://github.com/GlowstonePlusPlus/GlowstonePlusPlus/commit/e326e50342560543fbbd5c42ebd03d9b19e54daa

authors: Paulomart mastercoms

repo: GlowstonePlusPlus/GlowstonePlusPlus

license: mit


text:
Update weston and patches

Required some manual work to update, but last I tried, it still works.

Works like a breeze - I have just reset my index to your branch. Thanks!

authors: ChristophHaag Gnurou

repo: Gnurou/weston


text:
1985

About the PR
i made maxcaps smaller and deadlier
Why / Balance
i'm tired of the allegations, and i'm tired of collateral damage
shit will gib at higher ranges but at that point it's just maxcap ss13 :trollface:
Technical details
makes explosion range scale on the order of cuberoot, at the cost of having vastly increased maxintensity - for global thremonuclear war
Media

Requirements

[X] I have read and am following the Pull Request and Changelog Guidelines.
[X] I have added media to this PR or it does not require an ingame showcase.

Breaking changes

Changelog

:cl: router

tweak: Maxcap explosives (overpressurized gas tanks) now scale their range by cube root instead of square root, but deal a lot more damage close to the center.

you can also make maxcaps deal negative structural damage so they deal more to people than to structures

ok what the fuck i can't do ANYTHING

Can you make Holy Grenade do ONLY limb damage? Its whole thing is:
"Thou mayest blow Thine enemies to tiny bits in Thy mercy."
And NOT Blow thine STATION to tiny bits

repo: Goob-Station/Goob-Station


text:
React native build fixes

[x] web build: babel lodash + webpack plugin
[x] use api 28 on android
[x] rename gooddollar.com usage to gooddollar.org - iOS
[x] rename gooddollar.com usage to gooddollar.org - android

@mauriguz verify this are done and close

@sirpy what's point number 1? ability to build web same as master?

@mauriguz yes, there was this lodash webpack  plugin that was added to react-native or web dont remember which

everything is done - closing issue

authors: mauriguz sirpy

repo: GoodDollar/GoodDAPP


text:
Not working in Safari 15.3

I am using it in Angular project and the code snippet looks like this
import dialogPolyfill from 'dialog-polyfill';
if (this.dialogBox) {
dialogPolyfill.registerDialog(this.dialogBox.nativeElement);
this.dialogBox.nativeElement.showModal();
}
The dialog is rendered on the normal page and not as a modal window
Please help me understand what is missing.

I didn't give this polyfill a try as the author did, but I know that the same behavior for normal dialog. Hence, it seems that polyfill just recognizes Safari 15.3 as supporrting browser but it isn't?

repo: GoogleChrome/dialog-polyfill


text:
Setting user-agent via page.setUserAgent along with page.setRequestInterception does not correctly change the user-agent.

Steps to reproduce
Tell us about your environment:

Puppeteer version: 1.9.0
Platform / OS version: Ubuntu 16.04
URLs (if applicable):
Node.js version: 11.0.0

What steps will reproduce the problem?
Setting user-agent via page.setUserAgent, then allow request interception via page.setRequestInterception(true) and surcharge headers with whatever you want.
Please include code that reproduces the issue.
var express = require('express');
const puppeteer = require('puppeteer');

(async () => {
    //Set small express server to print headers
    new Promise((resolve, reject) => {
        let port = 3001;

        let app = express();
        app.use(express.json());
        app.listen(port);
        app.route('/test').get((req, res) => {
            console.log(JSON.stringify(req.headers));
        });
    });

    //Create browser
    let puppeteerArgs = [
        '--no-sandbox',
        '--disable-setuid-sandbox',
        '--enable-features=NetworkService'
    ];
    let browser = await puppeteer.launch({
        headless: true,
        args: puppeteerArgs
    });

    //Create page and set user-agent and interception
    var page = await browser.newPage();

    await page.setUserAgent('newUserAgent');
    await page.setRequestInterception(true);
    page.on('request', request => {
        request.continue({headers: {}});
    });

    //Call the api
    await page.goto('http://localhost:3001/test');

})();

What is the expected result?
Printed headers object should contain the user-agent set by page.setUserAgent.
What happens instead?
Print headers object contains the puppeteer user-agent.
So we have to explicitely change it in the returned header of request.continue().
This should either be changed or written in the doc.

So we have to explicitely change it in the returned header of request.continue().

@rqueraud So what are you trying to achieve when doing request.continue({headers: {}});?
P.S. I expected a different pattern to be used with header overrides - sent a PR with an example for the documentation.

@aslushnikov  With that example, I was showing that not overriding any fields in the headers still resulted to the userAgent header to be reinitialized as if no page.setUserAgent() were used.
But I imagine that it was not working because i wasn't using the correct pattern. Following the new example you provided in the doc made it work. Thanks.

authors: aslushnikov rqueraud

repo: GoogleChrome/puppeteer


text:
feat(Page,ElementHandle,Input): add callback when typing each char

feat(Page, ElementHandle,Input): add callback when typing each char
This patch support callback function when typing each char in text
Fixes #1272

I signed it!

I had update email

Hey @daviscai,
Any reason why the following wouldn't work for you?
async function typeWithCallback(text, callback) {
  for (let i = 0; i < text.length; ++i) {
    await page.keyboard.type(text[i]);
    callback();
  }
}

authors: aslushnikov daviscai


text:
fix: TypeScript declarations

Previously, the functions fileOpen and  fileSave used an undefined generic type of O. This caused TypeScript compiler issues in some environments. (details in commit discussion)
If I understand the types correctly, the generic type O is not needed. We just want TypeScript to know that options is either of the array type [FirstFileSaveOptions, ...CoreFileOptions[]] or of the object type FirstFileSaveOptions.

@googlebot I signed it!

Thank you very much!

authors: simon-lammes tomayac

repo: GoogleChromeLabs/browser-fs-access


text:
Fixes the case when a partition was pushed down but not included in the row restriction correctly

Added few new tests to cover those cases and in other classes to improve coverage.

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

authors: jayehwhyehentee prodriguezdefino


text:
Object storage: Add metadata to indicate if the compiled crcmod was i…

…nstalled by PKB or not.(issue: 457) Fix azure package installation. (issue: 448)

@yuyantingzero Please take a look. Fixing a couple of issues with object storage benchmark.

LGTM

authors: stfeng yuyantingzero

repo: GoogleCloudPlatform/PerfKitBenchmarker


text:
type annotations added for aerospike_benchmark.py

The following methods had their type annotations added
GetConfig(user_config : Dict[str, Any] )  -> Dict[str, Any]
Prepare(benchmark_spec: benchmark_spec.BenchmarkSpec)
Run(benchmark_spec: benchmark_spec.BenchmarkSpec) -> List[sample.Sample]
Cleanup(benchmark_spec: benchmark_spec.BenchmarkSpec) -> None

Is there anything else I should take care of?

Is there anything else I should take care of?
No this is all, we can pull this change now. Thank you!

@bvliu @jellyfishcake Could you let me know why the feedback/copybara — Google internal checks FAILED for runs with create time 2024-10-08T21:40:  check was not successfull ?

@bvliu @jellyfishcake Could you please let me know why the feedback/copybara — Google internal checks FAILED for runs with create time 2024-10-08T21:40: check was not successfull ?

Yes, this is an issue on our side. We will fix it from our side.


text:
Uses package.json overrides to fix NPM vulnerabilities reported by Dependabot.

WIP: DO NOT MERGE
This PR resolves critical and high severity npm audit vulnerability warnings that could not be fixed with npm audit fix, or even npm audit fix --force. It does this by using the overrides field in package.json.
Overriding versions were selected by looking at "Patched Versions" in the Github/National Vulnerability Database advisory. For example, Server Side Request Forgery in axios is patched in 1.7.4.
Where possible, the earliest patched version was used (avoiding major version updates that are more likely to introduce breaking changes).

Need to discuss pros and cons with this approach.
For example:
Scenario 1: Setting overrides in package.json locks those dependencies (and the locking mechanism is decoupled from package-lock.json). Because of this, if a user upgrades npm packages as normal, it might be possible to introduce breaking changes.
Scenario 2: Fixing vulnerability warnings in this way could itself introduce difficult to detect breaking changes. The only way I can think to mitigate this is lots of end to end testing.

Reopened to see if CLA checks are fixed.


text:
bug: fix incompatible com.coveo:fmt-maven-plugin:2.11:format version

According to https://github.com/coveooss/fmt-maven-plugin#using-with-java-8, the version 2.11 is only compatible with Java11. This project specifies maven compiler as 1.7.

@c24t would you be able to review/merge this? I don't have permission to add reviewers nor merge.


text:
examples/v2/cloud_functions does not explain how the files under 'function' get deployed

In both the jinja2 and python folders the cloud-functions are referenced as gs://cloud-function-sample/function.zip. This sounds like one you need to zip whatever is in the functions dir (with or without the directory) and use gsutil to upload it.
It would be nice to change the example to have the cloud-bucket uploading step as part of the deployment manager script.

Hi Stefan,
DM doesn't execute as a script, so we actually don't have a method for creating zip files and uploading them to GCS. I've clarified this in our functions sample README. Let me know if that's not clear enough though and we can rehash it in this thread.

The function code now is deployed as part of the deployment

Thanks a lot. This is helpful.

authors: aljim ensonic krwenholz


text:
set up CLA checks for the repo

cf. the legacy repo

done


text:
Don't add entries to classpath in maven project

From either runtimes or facets. Let maven handle it
@nbashirbello @akerekes
close #312

LGTM

I think the push failure is flakiness, but yell if any other tests start failing after this.

authors: akerekes elharo


text:
pubsub.Topic.create() returns None?

I'd really like to write
topic = pubsub.Topic('topic').create()

Looks like from the code we have today, that we don't return anything, so this won't work (topic will be None right here).

We've spoken a bit about this. That is un-Pythonic.
For example, see from the standard library.
>>> a = [1, -1, 10, 6]
>>> b = a.sort()
>>> b is None
True
>>> a
[-1, 1, 6, 10]

Being able to chain things nicely is un-Pythonic? Do we have more references to why this is a bad idea? Can you point me to that discussion?
It looks like Boto does this... See:

http://boto.readthedocs.org/en/latest/ref/sqs.html#boto.sqs.connection.SQSConnection.create_queue
https://github.com/boto/boto/blob/develop/boto/sqs/connection.py#L68

Having been inside, boto is not a very Pythonic library. Method chaining is a JavaScript idiom, not Python.

That doesn't really answer things for me ... :(
I think the bigger issue is that I don't see a use for a Topic object that isn't 'created'. that is, what can I do with topic = pubsub.Topic('name') besides create it?
Would this method be better as a factory?
topic = pubsub.Topic.create('topic-name')

or
topic = pubsub.create_topic('topic-name')

?

Yeah I was going to point out pubsub.create_topic('topic-name')

I'll let @tseaver speak on the design, but for us, the point of a method like topic.create() is to make it clear to the user when they are making an HTTP request and when they are just updating a local property of a Topic object.
So they have the option of "functional" approach pubsub.create_topic('topic-name') or OO approach topic.create()

Yeah I was going to point out pubsub.create_topic('topic-name')

Does that exist? I don't see it...

the point of a method like topic.create() is to make it clear to the user when they are making an HTTP request and when they are just updating a local property of a Topic object.

Totally agree - I don't want to hide that a request is being made.
Wouldn't the two options go against the whole "one way to do things" idea?

Indeed they would violate the Zen of Python "There should be one-- and preferably only one --obvious way to do it.". @tseaver has mentioned abolishing functions of the form
top_level_package.verb_thing(args)

in favor of
thing = top_level_package.Thing(...)
thing.verb(args)

What's the reason for that ?
If we're going to go that way, I'd like to re-open the topic of enforcing all our methods to be chainable. I'd rather go the package.verb_thing(args) though....

authors: dhermes jgeewax

repo: GoogleCloudPlatform/gcloud-python


text:
Is the gem working?

I'm trying to use this gem but so far am unsuccessful with trying to load it.
I installed as usual. I used sudo, since this is the system installation of ruby.
In irb I do this and it says cannot load such file:
irb(main):001:0> require 'gcloud'
LoadError: cannot load such file -- gcloud
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from (irb):1
	from /usr/bin/irb:12:in `<main>'
irb(main):002:0>

I only have one ruby installation and that's the system one.
Could it be the gem is broken? If it isn't then I apologize for submitting this issue and I'll try again.

Sorry it's my own error.

Hey what was the error?

@quekshuy Can you please post your error and solution? It may help @VincentVanGoat resolve #229.

Hello,
Sorry for the delay in responding.
In an older version of the gem, the requires weren’t working. I updated to
a later version of the gem (0.2.0) and it works now. Is it happening with
the latest version for you @VincentVanGoat?
On Wed, Aug 19, 2015 at 4:03 PM Chris Smith notifications@github.com
wrote:

@quekshuy https://github.com/quekshuy Can you please post your error
and solution? It may help @VincentVanGoat
https://github.com/VincentVanGoat resolve #229
https://github.com/GoogleCloudPlatform/gcloud-ruby/issues/229.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/gcloud-ruby/issues/84#issuecomment-132819761
.

Yes. I found that in my project as well. It is fixed now! Thanks!

No problem. Again, sorry I didn’t reply sooner!
On Thu, Aug 20, 2015 at 12:16 PM Kanishka Misra notifications@github.com
wrote:

Yes. I found that in my project as well. It is fixed now! Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/gcloud-ruby/issues/84#issuecomment-133128627
.

authors: VincentVanGoat quartzmo quekshuy

repo: GoogleCloudPlatform/gcloud-ruby


text:
Add Terraform deployment module

Added a script to deploy Autoneg via Terraform.

Thanks @rwkarg for the detailed feedback - +1 to your comments.
Overall comment - as some of these resources are autogenerated by kubebuilder, can you think of a good way to merge those changes into this TF code without manual editing?

Overall comment - as some of these resources are autogenerated by kubebuilder, can you think of a good way to merge those changes into this TF code without manual editing?

There are stuff like k2tf which might work, I would imagine it doesn't take kindly to referencing Terraform variables...

Ah right now I see the prior discussion. I agree that we should keep it here in this case.

authors: rosmo soellman


text:
Cleaning up README and adding make create instead of using steps

Cleaning up README and using 'make create'

Test the please

ok to test

test this please

/ok-to-test

test this please

/lgtm
/approve

authors: chrislovecnm homernajafi

repo: GoogleCloudPlatform/gke-datadog-demo


text:
Xamarin Support

Hello team,
I am not sure whether this is the correct place to ask this, however, I am currently evaluating the different services in Xamarin and came across different issues and unexpected errors. I want to know whether Xamarin is supported so I can investigate the behavior in more details at my end.
The following issue states that the technology is not fully supported for Storage:
https://github.com/google/google-api-dotnet-client/issues/1162
Is this the official statement with all your services or it is just the object storage.
Thanks

No, Xamarin isn't supported right now. We would like to have as broad support as possible, but supporting mobile platforms can present various challenges, particularly in the authorization space where browser interaction is required.

authors: StefanNenchev jskeet

repo: GoogleCloudPlatform/google-cloud-dotnet


text:
message type "google.appengine.logging.v1.RequestLog" isn't linked in

logging: unmarshalling proto payload: any: message type "google.appengine.logging.v1.RequestLog" isn't linked in

Code:
func main() {
	ctx := context.Background()

	lc, err := logadmin.NewClient(ctx, "cbro-scratch")
	if err != nil {
		errorf("logadmin.NewClient: %v", err)
	}

	entries := lc.Entries(ctx)
	for {
		e, err := entries.Next()
		if err != nil {
			errorf("Entries: %v", err)
		}
		log.Print(e.Payload)
	}
}

cc @zombiezen

Aha, I have a fix.  Do we know what other types can occur in here?

I'm not sure, I think they could be anything. Is there no general solution for this?

There's a small list. See
https://github.com/googleapis/googleapis/issues/187. I did the main audit
log proto but haven't gotten around to the other ones.
On Fri, Nov 11, 2016 at 3:57 PM Chris Broadfoot notifications@github.com
wrote:
I'm not sure, I think they could be anything. Is there no general solution
for this?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-go/issues/423#issuecomment-260053802,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARoHZZnUFOkuAv1UPp7pKzIQgqI8FrDyks5q9NaogaJpZM4KwGOL
.

@jba, that bug doesn't mention RequestLog, which is where this error came from.

@pongad looks like we need to add
_ google.golang.org/genproto/googleapis/appengine/logging/v1

to the import list of logadmin.go. We already do this for audit logs so I assume there away to configure it.

Sorry, I don't completely understand this. Are appengine/logging/v1 and cloud/audit somehow privileged that we should always include them? From the proto doc it looks like any service can define its own error type and messages of those types can be fetched. Shouldn't it be up to the user to link in these types? Otherwise, I think we'd have to make logadmin.go import every possible log types right?

No, there's a fixed set of services that can use protos, so a fixed set of types. There is a list somewhere, but for now we can just link in this proto.
BTW, I was wrong in thinking this was an issue in generated code. It's just a one-line change to the handwritten logadmin client.
Running broady's code will only be an adequate test for you if you've written GAE logs to your project. If not, then ask broady to test for you.

@broady I just submitted CL that should fix this. Could you try again?

Assuming this specific issue (linking in RequestLog) is fixed.

Weird. My code doesn't print any log entries.
Does it need a filter? It shouldn't, right?

That's really odd. @broady do you know an easy way to give my test project an appengine log? I can try testing it on my side.

authors: broady jba pongad zombiezen

repo: GoogleCloudPlatform/google-cloud-go


text:
Add test to make sure we're playing nice with google/apiclient dependencies

Since we have some shared dependencies with google/apiclient and many users likely will be using both libraries, we should ensure that our dependency versions do not conflict with theirs on a running basis.

moved to wiki.

repo: GoogleCloudPlatform/google-cloud-php


text:
Log Viewer - Add elegant unhandled exception handler

inside LogLoaddingWrapperAsync
Unhandled exception goes up to UI thread caller.

use ErrorHandlerUtils.HandleExceptionsAsync to guard async methods.


text:
Pubsub feature

I merged m2_master into my pubsub_feature. I wasn't sure if I should to a PR to pubsub_feature or m2_master first.

Hi Jim,  Normally, here is the way to check in new features.  Create a feature branch at GoogleCloudPlatform from master ( not  m2_master, We are moving on to master branch now).  Then you create PR from your fork branch to this feature branch.
The build error says you created some strings in resources but not used.
CloudExplorerPubSubNoSubscriptionsFoundCaption
PubSubNewTopicWindowHeader
CloudExplorerPubSubListSubscriptionsErrorCaption
CloudExplorerPubSubLoadingSubscriptionsCaption
Found unused strings.

Was any of this previously reviewed? Or is this all new code?

This was previously reviewed, but I had to make some changes to the xaml to
work with other changes.
On Mar 23, 2017 5:17 PM, "iantalarico" notifications@github.com wrote:

Was any of this previously reviewed? Or is this all new code?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-visualstudio/pull/518#issuecomment-288898477,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APoS-qt3LfslRCaRFh-zoIq4hgAfyz2Uks5rowutgaJpZM4Mne1v
.

Can you just point out the files with changes so we can review them? I'd rather no re-review 2000 lines of code :)

authors: Deren-Liao ILMTitan iantalarico


text:
Add ID to cloud build steps.

This will show up in the cloud build result page as step name.

Example: https://console.cloud.google.com/cloud-build/builds/cd8ec535-24bb-4909-96cf-01f5e80c2071?project=dpt-demo-3-devops


text:
Unnecessary null assignment in BigQuery Java example

https://github.com/GoogleCloudPlatform/java-docs-samples/blob/master/bigquery/cloud-client/src/main/java/com/example/bigquery/QuickstartSample.java#L35
No need to assign null here. All objects are null by default after declaration.

Notice: this issue has been closed because it has been inactive for 192 days. You may reopen this issue if it has been closed in error.

authors: kurtisvg polleyg

repo: GoogleCloudPlatform/java-docs-samples


text:
fix: flaky test in compute sample: WindowsOs Image

Fixes #7686 #7688
Both the issues are flaky. Hence, increased timeout for the operations and added MultipleAttemptsRule.

Approved, but please keep the comments in mind before merging


text:
Question: why no chroot()?

From my read of the designdoc and quick look at the code, I think kaniko works by unpacking the image onto the real (inside the container) / and just assuming that the kaniko machinery can stay out of the way of the user's container data via an explicit whitelist.
I'm curious:  Why not unpack into a subdir, and chroot() there when it's time to RUN commands?  That way the "working directory" root is cleanly separated from the actual kaniko agent's root filesystem.  From what I can see, kaniko already assumes it is running as uid=0 (correct?) to preserve file permissions, run commands (apt-get) as root, etc so invoking chroot() should work just fine.
(I feel like this is such an obvious approach that I was expecting to see it mentioned in the docs, with an explanation of why it wasn't the approach taken.  I'm hoping to discover that reason with this issue/question...)

Really good question! chroot can't be run inside a default container in kubernetes or docker without the --privileged flag.
I've been playing around with a version of this that uses proot/ptrace to fake a chroot, I think it can work here and help reduce privileges.

Actually, it looks like my memory on this was wrong. It's the "mount --bind" that many programs use to populate a chroot before using that causes trouble inside a standard container that doesn't have the --privileged flag.
docker run -it alpine sh
mkdir newroot
cd newroot/
mkdir bin lib
cp -r /bin/* bin/
cp -r /lib/* lib/
chroot /newroot /bin/sh

We should probably do this to help separate the unpacking from the base kaniko directories. I don't think it would help much with dropping privileges though, because we'd still need to be root to create the initial rootfs.

I tried using chroot to execute commands in a subdirectory. Since we can't use "mount --bind" I had to copy over relevant directories (/proc, /dev, /sys, /etc). Copying basically took forever and didn't really work, so I don't think we'll be able to use chroot.

authors: anguslees dlorenc priyawadhwa

repo: GoogleCloudPlatform/kaniko


text:
running two times KUBERNETES_PROVIDER=ubuntu ./kube-up.sh

Hi ,
I ran below command 2 times. First time i canceled it because it failed with below error.
can't be established.
ECDSA key fingerprint is 44:a4:6f:2e:d6:95:78:09:50:b7:5b:23:28:30:51:54.
when i run below second time i am getting below error? any help??
KUBERNETES_PROVIDER=ubuntu ./kube-up.sh
[sudo] password to copy files and start node:
cp: cannot create regular file ‘/opt/bin/etcd’: Text file busy
cp: cannot create regular file ‘/opt/bin/kube-apiserver’: Text file busy
cp: cannot create regular file ‘/opt/bin/kube-controller-manager’: Text file busy
cp: cannot create regular file ‘/opt/bin/kube-scheduler’: Text file busy
start: Job is already running: etcd

sounds like etcd, kube-apiserver, etc are still running.  Find them with ps and kill them, and then try again?

I did...
I created shell script ..:)
sudo service etcd stop
rm -rf /opt/bin/etcd
rm -rf /opt/bin/kube-scheduler
rm -rf /opt/bin/kube-controller-manager
rm -rf /opt/bin/kube-apiserver
rm -rf /opt/bin/flanneld
rm -rf /opt/bin/kubelet
rm -rf /opt/bin/kube-proxy

I modified utuntu/util.sh, and get 'Cluster validation succeeded'
First add -f for all cp commands, like this: cp ~/kube/default/* /etc/default/  ===> cp -f ~/kube/default/* /etc/default/
Then rerun ./kube-up.sh, you will encounter "start: Job is already running: etcd"
Then Modified utuntu/util.sh, change 'service XXX start' to 'service XXX restart' , and run kube-up.sh
You'll get the success message

authors: erictune svennela yueyemaitian

repo: GoogleCloudPlatform/kubernetes


text:
Update "Getting started on Google Compute Engine" docs

I'm a recent user of Kubernetes, and I struggled a bit to get it up and running on GCE.  It looks to me like the Getting started on Google Compute Engine]() doc is a bit out of date.  I've updated the doc with what I think it should look like, and I'll link the PR here.
The main issues I found are:

The "Getting VMs" section could be clearer, and some of the docs linked to are out of date.
I believe gcloud preview  is now required for kube-up.sh.
Failure is messy with kube-up.sh, so a note to run kube-down.sh in case of failure before re-running kube-up.sh would be helpful.

Isaac - thanks for these fixes! (we've been a bit negligent about making sure all of our documentation stays up to date as the underlying source/examples have been churning so quickly).

authors: ihmccreery roberthbailey


text:
Doc generation should remove old doc files

Right now, our doc generation scripts notice if you make changes and
don't regen docs, don't include new docs, etc.  But they miss it if your
changes should have REMOVED a doc.  Both kubectl-apiversion and
kubectl-clusterinfo should have been removed, but weren't.
This patch starts tracking all generated doc files and will cause
problems if files should be removed and aren't.

this will definitely need a rebase.  (and poor @jlowdermilk has been looking at some of my other docs stuff...)

lgtm

lets wait to merge until after merge of
https://github.com/GoogleCloudPlatform/kubernetes/pull/6744

rebased PTAL

lgtm

authors: eparis jlowdermilk


text:
kubelet/rkt: Remove dependencies on rkt.store

1st commit change getImageID() and remove the code that uses store.
2nd commit update the godep by removing the rkt.store package.
This could probably fix #7850
/cc @vmarmol @dchen1107 @yujuhong

Looks good overall and easier solution than most others! Thanks @yifan-gu!

@vmarmol Nit addressed!

LGTM, merging.

authors: vmarmol yifan-gu


text:
Use Kubernetes Downward API and cgroup to compute available memory on GKE

Add mechanisms to determine the memory available for the container.
Previously the available memory was fetched from /proc/meminfo however those values are set for the supervisor and not the container which may lead to wrong heap allocation for the JVM.
This PR introduces two ways of computing the available memory:

Through the Downward API (which requires the user to set environment variables in Kubernetes config files)
Using cgroup (This may not work for some containers e.g Rocket)

The variable name for the Downward API is "KUBERNETES_MEMORY_LIMIT" which may be subject to change.
It might be useful to use cgroup only when some flags are set in order to conserve the current default behavior.
This PR fixes #14

@cassand Can you please resolve the conflicts with master?

@dlorenc Can you do quick pass at this PR. We decided to just put this in for the time being.

@cassand @dlorenc  What do you think of renaming KUBERNETES_MEMORY_LIMIT to CONTAINER_MEMORY_LIMIT_BYTES and calculating it from GAE_MEMORY_MB by default, and then using CONTAINER_MEMORY_LIMIT_BYTES everywhere.

authors: cassand meltsufin

repo: GoogleCloudPlatform/openjdk-runtime


text:
Forked Bunsen and reorganized directories.

Description of what I changed

To merge our Bunsen fixes, e.g., for issues #55 and #156, we have to fork it as our Bunsen PRs are not being reviewed/merged (seems there is no one maintaining Bunsen ATM). This PR does that and also restructures the
directories to make it more clear where each piece is.

E2E test

TESTED:
Only relying on unit and e2e tests as this should not make any functional changes.
Checklist: I completed these to help reviewers :)

[x] My IDE is configured to follow the code style of this project.
No? Unsure? -> configure your IDE, format the code and add the changes with git add . && git commit --amend

[x] I am familiar with Google Style Guides for the language I have coded in.
No? Please take some time and review Java and Python style guides. Note, when in conflict, OpenMRS style guide overrules.

[x] I have added tests to cover my changes. (If you refactored existing code that was well tested you do not have to add tests)
No? -> write tests and add them to this commit git add . && git commit --amend

[x] I ran mvn clean package right before creating this pull request and added all formatting changes to my commit.

[x] All new and existing tests passed.
No? -> figure out why and add the fix to your commit. It is your responsibility to make sure your code works.

[x] My pull request is based on the latest changes of the master branch.
No? Unsure? -> execute command git pull --rebase upstream master

Hi @kimaina and @omarismail94, I finally decided to fork only pieces of Bunsen that we need and bring them under our repo for now. I have also restructured the files. Most of the files are either copied from Bunsen with no change or moved to pipelines/. I have tried to highlight all the changes in Bunsen pom.xml files by keeping the old code as a comment. For our pipelines/ related edits, please make sure you check the changes; thanks.

@bashir2
Seems like there are conflicts in the PR after #195  got merged to the master. Can you please resolve these?
I was also looking into a way to make bunsen into a submodule, but that might not be possible, unless it is forked into your own repo with the fixes, and then point to the forked repo. What do you think?

@bashir2
Seems like there are conflicts in the PR after #195 got merged to the master. Can you please resolve these?
I was also looking into a way to make bunsen into a submodule, but that might not be possible, unless it is forked into your own repo with the fixes, and then point to the forked repo. What do you think?

Thanks @omarismail94 for the suggestion. I actually started by bringing bunsen as a sub-module but then it required many changes in the pom.xml files. Instead, I decided to reorganize directories like this to keep the changes in Bunsen to a minimum. The benefit is that it will be easier to merge our changes to the up-stream repo, if the work on that started again.


text:
Migrate Spark 3 metrics to use PrometheusServlet

We could utilize Spark 3's prometheus support, instead of using the JMX exporter. This would get rid of the additional complexity and CPU overhead of running the exporter agent. However, I am almost 100% sure this is going to change the exposed set of metrics and their names. Spark's documentation is not to great on the PrometheusServlet usage, here's a better tutorial: https://dzlab.github.io/bigdata/2020/07/03/spark3-monitoring-1/.

Any update on this?


text:
bug: Rename cloudbuild.yaml to cloudbuild_mim.yaml

This is needed since few jump start solutions already have cloudbuild.yaml.

/gcbrun

authors: kweinmeister singhalbhaskar


text:
jib cache metadata-v2.json seems to grow without bound

$ cd ~/Library/Application\ Support/google-cloud-tools-java/jib

$ ls -1 *.tar.gz | wc -l
      15

$ jq '.layers[].reference.digest' metadata-v2.json | wc -l
313

$ jq '.layers[].reference.digest' metadata-v2.json | sort -u | wc -l
13

Ah nice catch! Looks like we might have a bug in our cache writing system that is not detecting previous entries that are the same.

Fortunately looks like it's just the JSON entries that we missed de-duplication. The TAR files are unique.

authors: briandealwis chanseokoh coollog

repo: GoogleContainerTools/jib


text:
updating helm to 3.11

Just been using the updated render-helm-chart version just released in https://github.com/GoogleContainerTools/kpt-functions-catalog/pull/1024 (Thanks for the super fast turnaround on this btw!)
I ran into some version issues in the traefik chart and noticed the helm version could do with an update https://github.com/traefik/traefik-helm-chart/blob/master/traefik/templates/deployment.yaml#L2 |

@jracollins Thank you for the contribution. The change looks good.
I just to ask some short questions (currently we do not catch up with dependent tool releases due to the releasing overhead and sustainability concerns).

A newer version 3.11.1 (instead o f 3.11.0) is released to patch a CVE fix , I'd suggest using that one instead.
I assume helm has some backward compatibility support for major versions, so using the old version (3.8.0) won't break helm but does a no-op for certain behaviors which are added in the newer versions (3.11.0). Is this correct?
For the traefik specific version requirement, do you mind elaborating what the issues you encountered? Just to help future customers who use older render-helm-chart versions, and to help us better evaluate the support.

Not sure how I missed the 3.11.1 - fixed.
So the actual error I ran into was the one I linked in https://github.com/traefik/traefik-helm-chart/blob/master/traefik/templates/deployment.yaml#L2 rather than anything unexpected and was:
[FAIL] "gcr.io/kpt-fn/render-helm-chart:unstable" in 300ms
  Stderr:
    "failed to evaluate function: failed to run function: failed to run generator: unable to run: 'helm template' with env=[]; \"exit status 1\": \"Error: execution error at (traefik/templates/deployment.yaml:3:8): ERROR: Helm >= 3.9.0 is required\\n\\nUse --debug flag to render out invalid YAML\\n\""
  Exit code: 1

I had a look at the changelog and not sure specifically what changes in 3.9 that the traefik chart depends on. 3.9 is quite old now (May 2022) but if adhering to semver properly, it should just be additional features rather than any breaking changes.

cc @natasha41575 (in case kustomize users run into the same issue)

authors: jracollins yuwenma


text:
formatting changes introduced by eval

kpt pkg get https://github.com/GoogleContainerTools/kpt.git/package-examples/wordpress@next
cd wordpress
kpt fn render
kpt fn eval --image gcr.io/kpt-fn/set-namespace:v0.1 -- namespace=wordpress
git diff

Two issues:

Why is set-namespace changing the formatting?
More importantly: This is a general issue that can happen with arbitrary functions. The current answer is that you should run render after eval. But then, why not just have eval perform formatting as well as a convenience?

But you can have a pipeline with just a validator and render would format?
Not all functions are or will be using Go or kyaml, so the general question about formatting by eval is orthogonal.

Agree. So how about formatting resources as part of eval command as with clear messaging. In the following example, search(without replace) is formatting resources with clear messaging.
$ kpt fn eval --image gcr.io/kpt-fn/search-replace:v0.1 -- by-value=4

[RUNNING] "gcr.io/kpt-fn/search-replace:v0.1"
[PASS] "gcr.io/kpt-fn/search-replace:v0.1"
  Results:
    [INFO] Matched field value to "4" in file "resources.yaml" in field "spec.replicas"
    [INFO] Formatted resources.

authors: frankfarzan phanimarupaka

repo: GoogleContainerTools/kpt


text:
request for kpt live get

Similar to kubectl get, we can have a kpt live get command to get the status of resources in a package.

btw, kubectl get doesn't work with a kpt package with a grouping object.

@Liujingfang1 I am not sure I follow this exactly.  You'd like to get all of the resources in the package?

Yes, with this command, users can see the resources applied to cluster and their status. It might be similar to the kpt live status. In that case, we can close this issue.
The more interesting case is for targeting multiple cluster or filtering out certain resources that don't target the current cluster. This is a different problem, we can track it as a different issue.


text:
WIP: surface render results in packagerevisionresources api

This PR exposes kpt fn render results in the porch API (packagerevisionresources).
I will update the description with an example payload for the API shortly.
A few things that I plan to do after getting initial feedback on the PR:

Expose the render results in case of error
Try out approachs of saving the function results. A few alternatives I want to try out:

Save render results in the package itself. API to read the result from the resource in the package.
Save render results in the git-commit. Quick look suggests there isn't any limit on the git commit message https://stackoverflow.com/questions/9733757/maximum-commit-message-size, but may depend on the git hosting provider.
Add tests

/cc @mortent @justinsb

/cc @ChristopherFry


text:
Equals method on Element

The equals method on Element ignores the Properties. There is a deepEquals method to perform an equals if it is desired that the Properties are included in the test.
What should the default be? The Properties are an integral part of the Element (cf Gaffer1 where the Properties were separate) so suggest the default is that the Properties should be included in the equals.
We want to support multigraphs, where there can be multiple edges between nodes (even of the same element type), so it feels more consistent with that aim to have Properties included in the equals.
If the consensus is to leave it as it is, can we record the justification here?

I agree, properties are an integral part of elements so let’s make the equals method compare everything in an element.

Merged into develop.


text:
Improve docs and developer experience for working with the adaptive resolution system

Improve developer experience for writing nodes which take adaptive resolution data (like Copy to Points) - a way of generalising and automating manual composition - automatic copying of the primary input to parameters (always do that and discard if unused? essentially acts as the automatic insertion of cull nodes?)
More docs for the macros like node_fn (and the confusing similar ones to that)

Closed by #1942

repo: GraphiteEditor/Graphite


text:
Node versioning system

Since nodes are constantly changing, we currently have to run automated upgrade scripts to replace node internals with the current version, update inputs, etc. A non destructive node versioning system similar to Crates is necessary for compatibility and ease of use.
Each instance of a node will store its version, and the document node definition will also store the version. The definition version will be incremented every time a node is changed, and every time a new version is created an upgrade script can be included to upgrade from the previous version to that version.
When the editor notices an out of date node, it prompts the user to upgrade it. It will use the mapping of version to upgrade scripts one by one to get the node to the most up to date version. The important part is that a node will never be automatically changed unless a user explicitly requests it. An ignore box should also be available, which dereferences the users node from the node definition.
Note that this is not related to editor structs and fields. That will still require breaking changes or best attempts at upgrading.

Perhaps this solution will help you figure out the problem click

authors: adamgerhant jdpoccorie


text:
🛑 Server Gaming is down

In 3ba7115, Server Gaming (https://game.greathost.ro) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Server Gaming is back up in 118b5ea after 21 minutes.

repo: GreathostRo/upptime


text:
🛑 Server Ultra is down

In 31449fd, Server Ultra (https://ultra.greathost.ro) was down:

HTTP code: 403
Response time: 1981 ms

Resolved: Server Ultra is back up in b5677c1 after 1 minute.


text:
🛑 Server Gaming is down

In e3eb2d6, Server Gaming (https://game.greathost.ro) was down:

HTTP code: 403
Response time: 1164 ms

Resolved: Server Gaming is back up in 902a374 after 8 minutes.


text:
[1주차] 숫자 야구 게임 기능 구현 미션 제출입니다.

안녕하세요, 리뷰어님!
저는 자바스크립트가 처음이라 조금씩 찾아보면서 하다보니 생각보다 오래 걸리더군요.. 2~3일을 몇시간에 걸쳐서 완성했답니다.
우선, 코드 컨벤션 내용을 최대한 지켜보려고 했는데 내용이 너무 길고 한번에 외우는게 불가능해보여서 제대로 지켜졌는지 확인이 불가능하네요.. (참고 부탁드립니다!)
제가 실행하다보면서 약간 이해가 안되는 부분(?)이 몇가지 생겼는데 만약 알고 계신 내용이라면 알려주세요!!😊

3스트라이크를 맞춰서 게임이 종료될 때 printResult(result) 함수에서 insertAdjacentHTML() 이 부분이 alert()경고문 보다 늦게 나오더군요..!
저는 자바스크립트를 싱글스레드로 알고 있어서 처음에는 왜 그런지 이해를 못했어요. 그래서 조금 찾아보았는데 브라우저(?)에서 실행되는 뭐라뭐라 작성되어 있는데 사실 잘 이해가 안가더군요..
알고 계신다면 알려주시길 부탁드립니다!🙏🙏🙏

추가) cypress test를 까먹고 있었어요..! 실행해보니 test 1개만 통과하고 있어서 insertAdjacentHTML -> innerHTML로 변경했습니다.

우선, 다시 한번 코드 리뷰 감사드립니다!
코드 리뷰 내용에 따라 일부 내용 수정을 진행해봤어요😊

답변
이전에 못했던 질문을 남겨드리며, 저도 정확히는 이해하지 못했고 사실임을 뒷받침해줄 수 있는 문서들이 전무하다 보니 일부 설명은 추측성임을 알려드립니다.
핵심만 요약

innerHTML과 alert 모두 동기적인 코드이고, 이전에 예상하셨던 대로 순서대로 실행되는 것이 맞습니다. innerHTML로 인해 DOM 트리가 변경되는 것도 동기적으로 일어납니다.
그러나, innerHTML로 인해 리페인팅, 즉 변경된 웹페이지를 브라우저가 다시 그려내는 작업은 비동기적으로 실행됩니다. 즉, 즉시 반영되지는 않습니다.
이 리페인팅을 하는 작업은 동기적인 코드인 innerHTML과 alert이 모두 실행된 후 더 이상 실행시킬 동기적인 작업이 없을 때야 비로소 리페인팅이 일어나기 때문에, 사용자가 alert 창이 닫힌 후에야 이 작업이 수행되게 됩니다.
setTimeout으로 감싸진 alert 코드의 경우 setTimeout 역시 비동기적으로 실행되는 함수이므로 동기적으로 실행되는 코드보다는 우선순위가 낮으며, 이로 인해 리페인팅보다 늦게 실행된 것으로 추정하고 있습니다. 4번 질문에 대해 명확한 공식 문서를 찾지 못해 답변을 하지 못했습니다.

아래의 코드를 실행해 보세요
document.body.innerHTML = 'innerHTML';
console.log(document.body.innerHTML) // 'innerHTML'
alert('Alert!');

이 코드를 실행하면, Alert!가 먼저 띄워지고 화면에 innerHTML이라는 텍스트가 보이지 않으므로 마치 innerHTML이 실행되지 않고 Alert!가 먼저 실행된 것처럼 보입니다.
그러나, console.log의 결과를 보시면 아시겠지만 document.body.innerHTML에 값을 할당한 이후의 값이 정상적으로 출력된 것을 확인하실 수 있습니다. 즉, DOM 트리에는 변경사항이 반영되었지만 브라우저가 변경사항을 리페인팅하는 작업만이 아직 수행되지 않았음을 확인할 수 있습니다.
세부 설명
왜 이러한 현상이 발생하는지, 제가 알고 있는 지식을 가능한 한 동원해 설명해 보겠습니다. 여기서부터는 지루한 개념 설명이 포함됩니다.
1⃣ JavaScript는 싱글 스레드 방식으로 작동한다

자바스크립트 엔진은 자바스크립트를 실행하고 해석하는 소프트웨어입니다. 자바스크립트 코드를 읽고 기계어로 변환해 실행하는 등의 역할을 수행합니다. Chrome의 V8 엔진이 대표적인 예시입니다.
자바스크립트 엔진은 콜 스택이라는 것을 가집니다. 자바스크립트 코드를 읽으며 실행해야 하는 코드가 생길 때마다, 이 콜 스택에 수행해야 하는 작업이 하나씩 삽입됩니다. 이후 콜 스택에서 작업을 하나씩 빼며 자바스크립트의 코드들이 실행되게 됩니다.
자바스크립트 엔진이 가지는 콜 스택은 하나입니다. 따라서 한 번에 하나의 작업만을 수행할 수 있으며, 따라서 JavaScript는 싱글 스레드 방식으로 작동하게 됩니다.

2⃣  WebAPI의 도움으로 비동기 작업을 수행할 수 있다
여기까지만 보면 웹 브라우저에서는 하나의 작업을 수행하는 동안, 다른 작업은 수행할 수 없어야 하는데, 애니메이션이 재생되면서도 사용자는 다른 작업을 할 수 있고, 대용량의 파일을 다운받으면서도 다른 작업을 할 수 있는 점은 설명이 되지 않을 겁니다. 허나 런타임 환경에서는 JavaScript는 WebAPI의 도움을 받아 여러 작업들을 수행할 수 있게 됩니다.

WebAPI란 네트워크 요청, 클릭 등의 여러 이벤트 처리, 타이머 등 브라우저에서 제공해주는 다양한 API 및 기능들을 의미합니다.
JavaScript는 싱글 스레드이지만, WebAPI는 멀티 스레드입니다. 따라서 JavaScript는 WebAPI의 보조를 받아 비동기적으로 실행해야 하는 작업들을 WebAPI에게 수행할 것을 지시할 수 있습니다. 이것이 JavaScript가 싱글 스레드임에도 불구하고 여러 개의 작업이 한꺼번에 진행될 수 있는 이유입니다.

3⃣ 이벤트 루프가 비동기 작업들의 실행을 담당합니다
여기에서는 이러한 비동기 작업들 (setTimeout 포함) 이 어떻게 수행되는지, 좀 더 깊게 들어가 보겠습니다.

콜 스택
위에서 설명드렸습니다. 실행해야 하는 코드를 콜 스택에 넣고, 콜 스택에서 함수를 빼내면서 해당 함수를 실행하게 됩니다. 더 요약하면 콜 스택에는 실행될 예정인 작업들이 들어갔다 나오는 겁니다.
마이크로 태스크 큐 / 매크로 태스크 큐
WebAPI가 비동기 작업들의 수행을 지시해 비동기 작업이 수행된 후 작업이 완료되면, 종류에 따라 마이크로 태스크 큐 또는 매크로 태스크 큐에 작업이 들어가 대기하게 됩니다.
- setTimeout을 예로 들면, setTimeout은 타이머에 제시된 시간이 끝나면 setTimeout 내의 함수가 매크로 태스크 큐에 들어가게 되고, 이후 실행되기를 기다립니다. setTimeout의 타이머 자체는 WebAPI에서 처리하지만 내부의 함수들은 결국 매크로 태스크 큐에서 나와 이벤트 루프에 의해 콜 스택으로 가야 실행되는 것이죠.
이벤트 루프
자바스크립트 엔진의 구성 요소로, 마이크로 태스크 큐와 매크로 태스크 큐 등 여러 큐들을 확인하면서 처리 준비가 된 비동기 작업들을 수행하는 역할을 합니다.
즉 이벤트 루프는 콜 스택과 큐를 확인하면서 비동기 작업 이후 실행되어야 할 함수들을 관리해 콜 스택으로 밀어넣어주는 역할을 수행하는 등, 전반적인 관리 역할을 하는 것이죠.
이벤트 루프는 크게 아래의 우선순위대로 수행됩니다.

콜 스택이 비어 있는 지 확인합니다. 콜 스택이 비어 있지 않다면, 현재 수행해야 하는 동기적인 작업들이 있음을 의미하므로, 대기합니다. 즉, 동기적인 작업의 우선순위가 제일 높습니다.
콜 스택이 비어 있고, 마이크로 태스크 큐가 비어 있지 않다면, **마이크로 태스크 큐에 있는 모든 작업을 순차적으로 실행합니다.
마이크로 태스크 큐가 비어 있다면, 매크로 태스크 큐에 있는 모든 작업을 순차적으로 실행합니다.

이러한 방식으로, 동기적인 코드, 그리고 비동기적인 코드 모두 콜 스택에서 하나씩 최종 실행되므로 싱글 스레드의 특성이 유지되는 것입니다. 그리고 우선순위도 지니고 있죠.
WebAPI가 다른 작업들을 멀티 스레드를 이용해 병행 처리를 한다고 해도 작업이 최종 완료되기 위해서는 자바스크립트 엔진 내의 큐에 들어가야 하며, 큐에서 실행할 작업이 나와 콜 스택에 옮겨지고 나온 후에야 작업이 비로소 실행되는 것입니다.
4⃣  innerHTML과 alert를 사용하는 예제에서 innerHTML보다 alert이 먼저 반영되는 이유
여기서부터는 저도 100% 제대로 이해하고 있지 않습니다. 틀린 설명이 있을 수 있음은 감안해 주셨으면 합니다.
document.body.innerHTML = 'innerHTML';
alert('Alert!');

지금까지의 원리를 바탕으로 왜 Alert!이 먼저 보이고, Alert!을 닫고 나서야 브라우저에 innerHTML이 그려지는 지를 알려 드리겠습니다.

document.body.innerHTML = 'innerHTML'이 가장 먼저 실행됩니다. 이 작업은 동기적이므로, 콜 스택에 올라와 바로 실행되게 되며, DOM 트리에 'innerHTML'로 바뀐 텍스트가 적용되어 업데이트되게 됩니다. 그러나 변경사항을 실제로 브라우저에 그리는 리페인팅 작업은 비동기로 진행되며 즉시 실행되지 않습니다.

alert 함수가 실행됩니다. alert은 동기적이므로, 콜 스택에 올라와 바로 실행되게 되며, 사용자가 상호작용을 해 닫을 때까지 동기적으로 계속해서 작동하므로 자바스크립트의 하나뿐인 스레드가 더 이상 진행되지 않고 정지하게 됩니다. 그렇기 때문에, 실행 중인 애니메이션이 있을 경우 애니메이션이 아예 멈추는 등의 현상이 일어납니다. 메인 스레드를 이렇게 동기적인 코드가 막아 실행이 일시정지 되는 현상을 **블로킹(Blocking)**이라고 합니다. 리페인팅은 비동기 작업이므로 Web API의 지시에 의해 브라우저에서 리페인팅 작업을 수행할 수는 있겠지만, 리페인팅 역시 이벤트 루프에 의해 콜 스택으로 이동되야 실행되므로 최종적인 작업 완료가 되지는 않습니다.

alert창을 사용자가 닫으면, 최종적으로 콜 스택이 비게 되며, 이제 이벤트 루프에 의해 완료 대기 중인 비동기 작업들이 실행될 수 있게 됩니다. 이벤트 루프의 경우 아쉽지만 저도 어느 큐에서 관리되는 지는 명확하게 알아내지 못했습니다. 렌더링 큐에서 관리된다는 이야기도 있고, 렌더링 파이프라인에서 관리된다는 이야기도 있는 등 의견이 상당히 다양합니다.

어쨌든 이렇게 Alert 창이 닫힌 이후에야 콜 스택이 비니 리페인팅도 반영될 수 있다는 점만 알아두시면 됩니다. 그래서 리페인팅이 Alert 창이 뜨는 것보다 더 늦게 발현되는 것이죠.
5⃣  setTimeout을 alert에 사용된 경우 리페인팅이 먼저 실행될 수 있는 이유
명확한 공식 자료가 마땅치 않은 상황입니다. 명확하지 않은 부분은 명확하지 않다고 덧붙여 이야기하겠습니다.
alert함수는 동기적으로 작용하므로 비동기 작업인 리페인팅보다는 사실상 우선 순위가 높으므로 먼저 실행될 수 있었습니다. 그러나 setTimeout은 비동기 함수이므로 이야기가 달라질 수 있습니다.
document.body.innerHTML = 'innerHTML';이 우선적으로 실행되는 것은 우선 맞습니다. 이 코드가 실행된 이후에는 콜 스택이 비겠죠.
그러면 이제, 매크로 태스크 큐에 들어가는 setTimeout과 리페인팅을 하는 작업들이 실행 준비 상태에 있게 됩니다. 둘 다 비동기 작업이면서, 이벤트 루프는 한 번에 하나의 작업만을 콜 스택에 옮길 수 있으니 둘 중 어느 하나가 먼저 실행되겠죠.
아쉽게도 여기서부터는 두 작업 중 어느 작업이 먼저 실행될 지에 대한 우선순위를 알지 못해 저도 설명이 어렵습니다. 그러나 이전과 달리 두 함수 모두 비동기인 포지션으로 옮겨졌으므로 동기적인 코드를 실행하는 것과는 상황이 다르겠구나 라는 점만 이해해주시면 그것으로 충분하다고 생각합니다.
6⃣  보너스: setTimeout의 딜레이?
setTimeout을 0.0001ms 등의 굉장히 작은 값을 할당했는데도 500ms를 설정한 것과 동일하게 리페인팅이 먼저 일어난 것에 대해 의아해하셨을 것입니다.
결론적으로는 브라우저에는 최소 지연 시간이라는 것이 존재합니다. setTimeout을 0ms로 맞춰도 실제로는 0ms가 아니라, 4ms가 됩니다.
그렇기 때문에 비동기 코드인 setTimeout은 0ms더라도 즉시 실행되지 않으며, 정말로 0ms로 실행된다고 해도 앞서 말씀드린 동기적인 코드들이 실행된 후 이벤트 루프가 큐에 들어간 코드들을 더 낮은 우선순위로 실행한다는 점을 봤을 때, 비동기 코드는 절대 즉시 실행될 수가 없습니다.

최소 지연 시간이 있으므로 즉시 실행되기 어렵다
비동기로 처리된다는 것만으로 콜 스택에 들어가는 다른 동기적인 코드에 비해 우선순위가 떨어진다를 염두해두시면 될 것 같습니다.


text:
'child_process' module can not found in '@grnsf/if-plugins/build/lib/shell  When I introduce plugins into the React project

Rationale

Implementation details

When I introduce plugins into the React project，and use {e-Net} in if-plugin,
there will be display this issue:
'child_process' module can not found in '@grnsf/if-plugins/build/lib/shell
Priority

May I ask if this plugin is incompatible with the React framework?
Scope

Size

What does "done" look like?

Does this require updates to documentation or other materials??

Deadline

Acceptance criteria

Hi @lyxHanHan. I've investigated the issue. If you're explicitly using webpack, you'll need to add the following configuration to your webpack.config.js file:
// webpack.config.js ..., resolve: {     extensions: [".ts", ".js"],     fallback: {       "child_process": false,       // and also other packages that are not found     }   },
However, if you're relying on the node_module implicitly, you'll need to add the following to your package.json file:
"browser":{ "child_process": false }
Please let us know if this solution resolves your problem.

Solved, thank you for your help！🙏

Closing as resolved

authors: jmcook1186 lyxHanHan manushak

repo: Green-Software-Foundation/if-plugins


text:
color of EUI value on map popup

In the existing implementation, these are always CSS blue, which seems wrong:

In the updated version, the color seems to match the chart on the building report, but not always. Here's one that looks red, but the chart would indicate should be orange:

I wonder if the difference between apps (deployed and staged) has something to do with a last minute (Jan 2021) changes to seattle.json that were made but never deployed
https://github.com/GreenInfo-Network/seattle-building-dashboard/commit/ae6f8071413cf53f8bc2d54468d11bbe55b53bba
https://github.com/GreenInfo-Network/seattle-building-dashboard/commit/9fb353ebe10dba158320278708b7d60fb332e96d
Why red and not orange, I'm not sure
┆Issue is synchronized with this Asana task

See building_layer.js

license: ISC


text:
Two buildings on top of each other?

Mike:

I found a weird situation in the test environment. It looks like the same shape is in compliance/out of compliance and corresponding to multiple buildings. It seems like it’s simultaneously crosshatched/normal.

Seems like there's two shapes on top of each other?

I notice in those screenshots above that one is called "WESTWOOD VILLAGE - BLDG B" and the other is "WESTWOOD VILLAGE - BUILDING F"
Seems likely this is two footprints directly overlapping each other? It's also possible they are separately benchmarked, but with similar/same lat-lngs

We might not be able to clear this up during this phase of work.
But one approach would be to query for building footprints that have X% spatial overlap

Closing as not in scope for this phase of work

authors: danrademacher tomay


text:
RuntimeWarnings and ValueErrors

Hi,
I am a new user of NucleoATAC, and I have been able to run the test examples without any problem. However, when I try using NucleoATAC on my own ATAC data, I run into 1 of 2 issues.
Here is the first issue. In this case, I get a RuntimeWarning from numpy. It is generated as a result of a divide by zero error in Step 3. In this case the output still seems to be created despite the warning. I've included the standard output below:
Command run:  /usr/bin/nucleoatac run --bam 150407/AC8.sorted.bam --bed test.bed --fasta hg19_genome.fa --out AC8_test
nucleoatac version 0.3.2
start run at: 2016-04-27 16:56
---------Step1: Computing Occupancy and Nucleosomal Insert Distribution---------
Making figure
---------Step2: Processing Vplot------------------------------------------------
---------Step3: Obtaining nucleosome signal and calling positions---------------
/usr/lib/python2.7/site-packages/nucleoatac/NucleosomeCalling.py:120: RuntimeWarning: divide by zero encountered in log
nuc_lik = np.sum(np.log(nuc_model) * mat)
/usr/lib/python2.7/site-packages/nucleoatac/NucleosomeCalling.py:120: RuntimeWarning: invalid value encountered in multiply
nuc_lik = np.sum(np.log(nuc_model) * mat)
/usr/lib/python2.7/site-packages/nucleoatac/NucleosomeCalling.py:121: RuntimeWarning: divide by zero encountered in log
null_lik = np.sum(np.log(null_model) * mat)
/usr/lib/python2.7/site-packages/nucleoatac/NucleosomeCalling.py:121: RuntimeWarning: invalid value encountered in multiply
null_lik = np.sum(np.log(null_model) * mat)
---------Step4: Making combined nucleosome position map ------------------------
---------Step5: Calling NFR positions-------------------------------------------
end run at: 2016-04-27 16:56
Here is the second issue. In this case I get another numpy RuntimeWarning. It is created as a result of an overflow in Step 1. Subsequently, there is a ValueError. This causes the program to crash.
Command run:  /usr/bin/nucleoatac run --bam 150407/AC6.sorted.bam --bed test.bed --fasta hg19_genome.fa --out AC6_test
nucleoatac version 0.3.2
start run at: 2016-04-27 17:19
---------Step1: Computing Occupancy and Nucleosomal Insert Distribution---------
/usr/lib/python2.7/site-packages/nucleoatac/Occupancy.py:45: RuntimeWarning: overflow encountered in power
res[nz] = a * x_mod[nz]**(k-1) * np.exp(-x_mod[nz]/theta) / (theta **k * gamma(k))
Traceback (most recent call last):
File "/usr/bin/nucleoatac", line 31, in
nucleoatac_main(args)
File "/usr/lib/python2.7/site-packages/nucleoatac/cli.py", line 56, in nucleoatac_main
run_occ(occ_args)
File "/usr/lib/python2.7/site-packages/nucleoatac/run_occ.py", line 96, in run_occ
fragment_dist.modelNFR()
File "/usr/lib/python2.7/site-packages/nucleoatac/Occupancy.py", line 65, in modelNFR
nuc[nuc<=0]=min(min(nfr)*0.1,min(nuc[nuc>0])*0.001)
ValueError: min() arg is an empty sequence
nuceloATAC (0.3.2)
python (2.7.5)
numpy (1.11.0)
Any insight would be greatly appreciated!

Both issues occurred when using a BED file that was too small (smaller than the example file). The issue did not re-occur when using a larger BED file.

repo: GreenleafLab/NucleoATAC


text:
Photolithography branch

fully finish Photolithography, no crashes ETC, textures and other stuff will be done in the following branch of mine

Reviewed and resolved every problem

And thats why 2 people are needed for changes

@BLocky104

Last recipe in Photolithography :

        ASSEMBLER_RECIPES.recipeBuilder()
                .input(CONTROLLED_SHAPED_NAQUADRIA_CHARGE)
                .input(NAQUADRIA_CHARGE)
                .output(CONTROLLED_SHAPED_NAQUADRIA_CHARGE)
                .EUt(250) // TODO was missing, I don't which value you want
                .duration(120)
                .circuitMeta(2)
                .buildAndRegister();

the EUt value was missing, just added a arbitrary value.

some textures are missing :

shaped_high_energy_gamma_shield
hasoc_lithography_mask
naquadria_charge
engraved_oganesson_wafer
photopolymer_plate

repo: Gregtech-Beyond/gregtech-beyond-core


text:
Extensions to SHOW Statements for information_schema tables

What type of enhancement is this?
API improvement, User experience
What does the enhancement do?
MySQL supports SHOW XXXX from [table] or SHOW FULL XXX from [table] to query information_schema, for example:
SHOW FULL TABLES WHERE Table_type != 'VIEW'

SHOW TABLE STATUS

SHOW PROCEDURE STATUS where DB='public';

SHOW INDEX FROM `monitor`;

SHOW FULL COLUMNS from `monitor`;

We have to support these syntax sugars if we want to improve the compatibility of MySQL protocol.
Tasks:

[x] Refactor show tables and show databases executor, make them querying from information_schema and support where clause such as SHOW FULL TABLES WHERE Table_type != 'VIEW'. https://github.com/GreptimeTeam/greptimedb/pull/3423
[ ] show columns
[ ] show table status
[ ] show index
[ ] SHOW CHARACTER SET
[ ] SHOW COLLATION
[ ] Improve show variables.

Implementation challenges
No response

The related MySQL documents:

https://dev.mysql.com/doc/refman/8.0/en/show.html
https://dev.mysql.com/doc/refman/8.0/en/extended-show.html

I'll implement the extensions to the show statement for information_schema in 0.7

I'll implement the below show statements:
SHOW CHARACTER SET
SHOW COLLATION
SHOW COLUMNS
SHOW DATABASES
SHOW FUNCTION STATUS
SHOW INDEX
SHOW OPEN TABLES
SHOW PROCEDURE STATUS
SHOW STATUS
SHOW TABLE STATUS
SHOW TABLES
SHOW TRIGGERS
SHOW VARIABLES

Navicat will submit "show status" and "show table status" upon connection.

Navicat will submit "show status" and "show table status" upon connection.

show status looks working but returns empty:
mysql> show status;
Empty set (0.03 sec)

I'll implement show table status based on #4218 .

repo: GreptimeTeam/greptimedb


text:
WAL disk usage based flush strategy

What type of enhancement is this?
Tech debt reduction
What does the enhancement do?
If WAL takes up too much disk space, the recovery process may take a long time to finish.
We can implement a FlushStrategy by checking the disk usage of WAL files, and flush the data in memtable to SST so that WAL files can be compacted.
Implementation challenges
No response

I'm interested in this issue. Can you assign this task to me?

I'm interested in this issue. Can you assign this task to me?

Some info that maybe useful for this:

Engine::get_used_size returns the disk usage of log files.
FlushStrategy determines whether to flush memtables to SST.
And the check happens everytime a new batch is written to memtable.

Please let me know if you need any help :grinning:

Thx!

We can implement a FlushStrategy by checking the disk usage of WAL files, and flush the data in memtable to SST

We might need to find out the regions with largest disk consumption or referring the oldest WAL file and flush those regions. But we lack some mechanism to get a global view of the regions now.

As mentioned in #1462, I'd like to close this issue. We could reopen #1462 if we need to implement a flush strategy based on disk usage.

authors: ShenJunkun evenyag v0y4g3r


text:
Heading Part resolved

Here i have resolved the part where now the heading (NavBar) will not cover the contents .

@GreyBeard42 sir please check my PR
i have made the changes and made it dynamic ( it is adaptable on mobile and navbar part is resolved)


text:
Add tests based on mock device

Description of change

Pull-Request Checklist

[x] Code is up-to-date with the main branch
[x] npm run lint passes with this change
[ ] npm run test passes with this change
[ ] This pull request links relevant issues as Fixes #0000
[ ] There are new or updated unit tests validating the change
[ ] Documentation has been updated to reflect this change
[ ] The new commits follow conventions outlined in the conventional commit spec

Codecov Report

Merging #1 (d2e7492) into main (832b6ac) will increase coverage by 25.60%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##             main       #1       +/-   ##
===========================================
+ Coverage   64.15%   89.75%   +25.60%
===========================================
  Files           5        5
  Lines         159      166        +7
  Branches       14       17        +3
===========================================
+ Hits          102      149       +47
+ Misses         57       17       -40

Impacted Files
Coverage Δ

src/PirateMidiDevice.ts
100.00% <100.00%> (+73.33%)
:arrow_up:

src/index.ts
100.00% <100.00%> (+41.66%)
:arrow_up:

src/utils/parseMessage.ts
100.00% <100.00%> (ø)

src/BaseDevice.ts
83.72% <0.00%> (+15.11%)
:arrow_up:

Continue to review full report at Codecov.

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

authors: GriffinSauce codecov-commenter

repo: GriffinSauce/pirate-midi-usb


text:
🛑 walletcheck API endpoint is down

In 7ced6dd, walletcheck API endpoint (https://grinnode.live:8080/walletcheck/grin1zxwrf5yaxlyps4mpx3n7j9kp4su3gzgpdhfk2sgv56q0prcdlzls9e6e0y) was down:

HTTP code: 0
Response time: 0 ms

Resolved: walletcheck API endpoint is back up in e75ba89.

repo: Grinnode-live/upptime