text:
McLighting does't work in AP Mode

Describe the bug
I have flashed my Wemos D1 mini like described in the installation guide.
I'd have expected the AP Web UI to offer settings to change the lights settings or a setting to enable the AP Mode in definitions.h.
To Reproduce

Flash controller
Open Web UI

Expected behavior
See description.
Desktop (please complete the following information):

wemos d1 mini

Additional context
definitions.h settings:
#define USE_WS2812FX_DMA 0      // 0 = Used PIN is ignored & set to RX/GPIO3; 1 = Used PIN is ignored & set to TX/GPIO1; 2 = Used PIN is ignored & set to D4/GPIO2;  Uses WS2812FX, see: https://github.com/kitesurfer1404/WS2812FX
                                // or comment it out
#if defined(USE_WS2812FX_DMA)
  #define MAXLEDS 384           // due to memory limit of esp8266 at the moment only 384 leds are supported in DMA Mode. More can crash if mqtt is used.
#else
  #define MAXLEDS 4096
#endif
// Neopixel
#define LED_PIN 3          // PIN (15 / D8) where neopixel / WS2811 strip is attached; is configurable, if USE_WS2812FX_DMA is not defined. Just for the start
#define NUMLEDS 300         // Number of leds in the; is configurable just for the start
#define RGBORDER "RGB"    // RGBOrder; is configurable just for the start
#define FX_OPTIONS 48      // ws2812fx Options 48 = SIZE_SMALL + FADE_MEDIUM  is configurable just for the start; for WS2812FX setSegment OPTIONS, see: https://github.com/kitesurfer1404/WS2812FX/blob/master/extras/WS2812FX%20Users%20Guide.md
//#define LED_TYPE_WS2811    // Uncomment, if LED type uses 400 KHz (classic 'v1' (not v2) FLORA pixels, WS2811 drivers)
#define LED_BUILTIN 2      // ESP-12F has the built in LED on GPIO2, see https://github.com/esp8266/Arduino/issues/2192
char HOSTNAME[65] = "McLightingRGBW"; // Friedly hostname  is configurable just for the start. Hostname should not contain spaces as this can break Home Assistant discovery if used.

#define ENABLE_OTA 1                  // If defined, enable Arduino OTA code. If set to 0 enable Arduino OTA code, if set to 1 enable ESP8266HTTPUpdateServer OTA code.
//#define ENABLE_MQTT 1                 // If defined use MQTT OR AMQTT, if set to 0 enable MQTT client code, see: https://github.com/toblum/McLighting/wiki/MQTT-API, if set to 1, enable Async MQTT code, see: https://github.com/marvinroger/async-mqtt-client
//#define ENABLE_MQTT_HOSTNAME_CHIPID   // Uncomment/comment to add ESPChipID to end of MQTT hostname
//#define ENABLE_MQTT_INCLUDE_IP        // uncomment/comment to add the IP-adress to the MQTT message
//#define ENABLE_HOMEASSISTANT          // If defined, enable Homeassistant integration, ENABLE_MQTT must be active
//#define MQTT_HOMEASSISTANT_SUPPORT   // If defined, use AMQTT and select Tools -> IwIP Variant -> Higher Bandwidth
//#define DELAY_MQTT_HA_MESSAGE 5       // HA Status is send after DELAY_MQTT_HA_MESSAGE seconds, to save bandwith

//#define ENABLE_BUTTON 14              // If defined, enable button handling code, see: https://github.com/toblum/McLighting/wiki/Button-control, the value defines the input pin (14 / D5) for switching the LED strip on / off, connect this PIN to ground to trigger button.
//#define ENABLE_BUTTON_GY33 12         // If defined, enable button handling code for GY-33 color sensor to scan color. The value defines the input pin (12 / D6) for read color data with RGB sensor, connect this PIN to ground to trigger button.
//#define POWER_SUPPLY 12               // PIN (12 / D6) If defined, enable output to control external power supply
#if defined(POWER_SUPPLY)
  #define POWER_ON   HIGH           // Define the output state to turn on the power supply, either HIGH or LOW.  Opposite will be uses for power off.
#endif
//#define ENABLE_REMOTE 13              // If defined, enable Remote Control via TSOP31238. The value defines the input pin (13 / D7) for TSOP31238 Out

#if defined(ENABLE_BUTTON_GY33)
  #define GAMMA 2.5                   // Gamma correction for GY-33 sensor
#endif

#define ENABLE_STATE_SAVE             // If defined, load saved state on reboot and save state on SPIFFS

#define CUSTOM_WS2812FX_ANIMATIONS    // uncomment and put animations in "custom_ws2812fx_animations.h"
#define USE_HTML_MIN_GZ               // uncomment for using index.htm & edit.htm from PROGMEM instead of SPIFFS

#define TRANS_COLOR_DELAY 5            // Delay for color transition
#define TRANS_DELAY 10                 // Delay for brightness and speed transition

AP mode is used to define your wifi credentials to get the device onto your wifi.  Not to provide an access point for you to log into in order to control the lights.  That wouldn't be very useful if you have to log into the lights every time you wanted to change them.

AP mode is used to define your wifi credentials to get the device onto your wifi.  Not to provide an access point for you to log into in order to control the lights.  That wouldn't be very useful if you have to log into the lights every time you wanted to change them.

I'd have expected it to work because in the done todos is written:  'Also enable McLighting in Wifi AP mode.'
I have a light solution where no network access point is available. My mobile connects to the controller in the AP Mode by itself and I'd like to control the lights with my mobile.

I'd have expected it to work because in the done todos is written:  'Also enable McLighting in Wifi AP mode.'
I have a light solution where no network access point is available. My mobile connects to the controller in the AP Mode by itself and I'd like to control the lights with my mobile.

Yes, it shoud leave the config mode after 120 seconds of inactivity and is usable then as you expected.

Yes, it shoud leave the config mode after 120 seconds of inactivity and is usable then as you expected.

@bpohvoodoo after the config timeout the wifi AP is disabled and I cannot connect anymore.

@bpohvoodoo after the config timeout the wifi AP is disabled and I cannot connect anymore.

Okay it worked after a fresh upload of the software.
Thanks.

Okay it worked after a fresh upload of the software.
Thanks.

authors: atomroflman bpohvoodoo ryancasler

repo: FabLab-Luenen/McLighting


text:
Why are Style#withUnderline and Style#withFont client-side only?

I don't see this as just a client-side process, is there a reason for this?

This is a technicality with how the game is distributed. Proguard at build time will strip method not used in server platform, and since withFont is only used on client it is omitted from server.
A solution is adding a sort of style builder to fabric api so the methods can be bypassed (the backing fields exist regardless of platform)

source: gharchive/issue

repo: FabricMC/yarn

license_type: permissive

license_source: github-api


text:
Registry initializer method names post-22w19a

Before 22w19a, the registry initializer methods were named like this:

initAndGetDefault for non-DRM registries
registerAndGetDefault for DRM registries

Since 22w19a the method is considered a functional interface named BuiltinRegistries$Initializer. The class name was chosen because InitAndGetDefaulter doesn't sound great. But this raises a question: what should the methods be named then?
Ideas:

Keep current one
Rename to init. (initialize, but yarn convention abbreviates that.) The "get default" part is an implementation detail and should be documented on the functional interface.
Something else?

I think these methods should be named initialize. After all, the ModInitializer method is named onInitialize.


text:
Not compatible with JEI

Describe the Suggestion
REI frequently causes crashes, but JEI does not display recipes correctly.
Screenshots and Videos
No response
Additional Context
No response

I tried changing JEI versions and using other mods like EMI and it's been wildly inconsistent with showing stuff like assembly line crafting recipes

REI, JEI, and EMI are all supported.
If REI is crashing, report to REI.
Errors with all 3 should be mostly fixed in the next update.

authors: LyoGyo TropheusJ meishiffx

repo: Fabricators-of-Create/Create

license: MIT


text:
5.1 Patch 1 Crashes with Crafts and Additions 20230508b

Describe the Bug
The name lol, crash report linked. I'm not sure it's because crafts and additions, but the report mentions it.
Reproduction Steps

Updated from 0.5.0 Patch 6 to 0.5.1 Patch 1
Launched and got the report linked
Rolled back to 0.5.0 6 everything is fine again

Expected Result
Well not to crash with crafts and additons I guess
Screenshots and Videos
No response
Crash Report or Log
https://pastebin.com/bnyHqG5G
Operating System
Windows 11
Mod Version
0.5.1b
Minecraft Version
1.19.2
Other Mods
No response
Additional Context
No response

all addons are going to need updating

Got it, thanks!


text:
Major Frames issues after a while flying around

Describe the bug
I'm not sure why, but I'm having major FPS and TPS drops, both in single and multiplayer, after flying around for a while. I did some testing with a completely vanilla client and it doesn't happen. I'm not sure what is happening, as the log doesn't show anything weird as the game is running, although it gives some erros when closing the world and then crashes the client.
Here are some screenshots I took while flying around. It starts perfectly, with over 500fps sometimes, and then it starts going down. Eventually, it becomes unplayable until I close the client and open again.
I did notice this before, but I though was some combination of other mods I installed later. Today I decide to do the testing without any mods besides what is included in the modpack and the problem persists.
Please, let me know if there's any other information I can provide to help you figure it out! :)

Modpack version
3.8.3 for 1.18.2 (MultiMC)
Launcher
MultiMC
Other things

[ ] I updated FO to a newer version (mention, what version to what version)
[ ] I removed or added some mods (mention, which ones)

Additional context

[20:57:25] [Render thread/WARN]: Ambiguity between arguments [teleport, location] and [teleport, destination] with inputs: [0.1 -0.5 .9, 0 0 0]
[20:57:25] [Render thread/WARN]: Ambiguity between arguments [teleport, location] and [teleport, targets] with inputs: [0.1 -0.5 .9, 0 0 0]
[20:57:25] [Render thread/WARN]: Ambiguity between arguments [teleport, destination] and [teleport, targets] with inputs: [Player, 0123, @e, dd12be42-52a9-4a91-a8a1-11c01849e498]
[20:57:25] [Render thread/WARN]: Ambiguity between arguments [teleport, targets] and [teleport, destination] with inputs: [Player, 0123, dd12be42-52a9-4a91-a8a1-11c01849e498]
[20:57:25] [Render thread/WARN]: Ambiguity between arguments [teleport, targets, location] and [teleport, targets, destination] with inputs: [0.1 -0.5 .9, 0 0 0]
[20:57:25] [Render thread/INFO]: Loaded 7 recipes
[20:57:25] [Render thread/INFO]: Loaded 1141 advancements
[20:57:25] [Render thread/INFO]: Environment: authHost='https://authserver.mojang.com', accountsHost='https://api.mojang.com', sessionHost='https://sessionserver.mojang.com', servicesHost='https://api.minecraftservices.com', name='PROD'
[20:57:25] [Render thread/INFO]: Applied 0 biome modifications to 0 of 61 new biomes in 247.9 ?s
[20:57:25] [Server thread/INFO]: Starting integrated minecraft server version 1.18.2
[20:57:25] [
[2022-06-01-1.log.gz](https://github.com/Fabulously-Optimized/fabulously-optimized/files/8819501/2022-06-01-1.log.gz)
[latest.log](https://github.com/Fabulously-Optimized/fabulously-optimized/files/8819502/latest.log)
Server thread/INFO]: Generating keypair
[20:57:29] [Server thread/INFO]: Preparing start region for dimension minecraft:overworld
[20:57:29] [Render thread/INFO]: Preparing spawn area: 0%
[20:57:30] [Render thread/INFO]: Preparing spawn area: 0%
[20:57:30] [Render thread/INFO]: Preparing spawn area: 3%
[20:57:31] [Render thread/INFO]: Preparing spawn area: 8%
[20:57:31] [Render thread/INFO]: Preparing spawn area: 12%
[20:57:32] [Render thread/INFO]: Preparing spawn area: 18%
[20:57:32] [Render thread/INFO]: Preparing spawn area: 23%
[20:57:33] [Render thread/INFO]: Preparing spawn area: 30%
[20:57:33] [Render thread/INFO]: Preparing spawn area: 35%
[20:57:34] [Render thread/INFO]: Preparing spawn area: 36%
[20:57:34] [Render thread/INFO]: Preparing spawn area: 42%
[20:57:35] [Render thread/INFO]: Preparing spawn area: 47%
[20:57:35] [Render thread/INFO]: Preparing spawn area: 54%
[20:57:36] [Render thread/INFO]: Preparing spawn area: 60%
[20:57:36] [Render thread/INFO]: Preparing spawn area: 68%
[20:57:37] [Render thread/INFO]: Preparing spawn area: 73%
[20:57:37] [Render thread/INFO]: Preparing spawn area: 79%
[20:57:38] [Render thread/INFO]: Preparing spawn area: 86%
[20:57:38] [Render thread/INFO]: Preparing spawn area: 92%
[20:57:38] [Server thread/INFO]: Changing view distance to 20, from 10
[20:57:38] [Server thread/INFO]: Changing simulation distance to 6, from 0
[20:57:38] [Render thread/INFO]: Time elapsed: 9360 ms
[20:57:38] [Server thread/INFO]: Yumatan[local:E:336653c0] logged in with entity id 809 at (-17.5, 80.0, 15.5)
[20:57:38] [Server thread/INFO]: Yumatan joined the game
[20:57:39] [Render thread/INFO]: Started 10 worker threads
[20:57:39] [Render thread/INFO]: Loaded 0 advancements
[20:57:43] [Server thread/INFO]: [Yumatan: Set own game mode to Spectator Mode]
[20:57:43] [Render thread/INFO]: [CHAT] Set own game mode to Spectator Mode
[20:58:13] [Server thread/INFO]: Saving and pausing game...
[20:58:13] [Server thread/INFO]: Saving chunks for level 'ServerLevel[New World]'/minecraft:overworld
[20:58:13] [Server thread/INFO]: Saving chunks for level 'ServerLevel[New World]'/minecraft:the_end
[20:58:13] [Server thread/INFO]: Saving chunks for level 'ServerLevel[New World]'/minecraft:the_nether
[20:58:20] [Render thread/INFO]: Flushed changes to Minecraft configuration
[20:58:25] [Render thread/WARN]: Reclaimed 3264 bytes at address 2170457855568 that were leaked from an unknown location (logging is disabled)
[20:58:25] [Render thread/WARN]: Reclaimed 21760 bytes at address 2170422994944 that were leaked from an unknown location (logging is disabled)
[20:58:25] [Render thread/WARN]: Reclaimed 8892 bytes at address 2170528763056 that were leaked from an unknown location (logging is disabled)
[20:58:25] [Render thread/WARN]: Reclaimed 59280 bytes at address 2170550194224 that were leaked from an unknown location (logging is disabled)
[20:58:25] [Render thread/WARN]: Reclaimed 432 bytes at address 2169823202464 that were leaked from an unknown location (logging is disabled)
[20:58:25] [Render thread/WARN]: Reclaimed 2880 bytes at address 2169900501040 that were leaked from an unknown location (logging is disabled)
[20:58:25] [Render thread/WARN]: Reclaimed 6048 bytes at address 2169825403456 that were leaked from an unknown location (logging is disabled)
[20:58:25] [Render thread/WARN]: Reclaimed 20960 bytes at address 2170452984016 that were leaked from an unknown location (logging is disabled)
[20:58:36] [Render thread/INFO]: [CHAT] Saved screenshot as 2022-06-01_20.58.36.png
[21:00:36] [Server thread/INFO]: Saving and pausing game...
[21:00:36] [Server thread/INFO]: Saving chunks for level 'ServerLevel[New World]'/minecraft:overworld
[21:00:36] [Server thread/INFO]: Saving chunks for level 'ServerLevel[New World]'/minecraft:the_end
[21:00:36] [Server thread/INFO]: Saving chunks for level 'ServerLevel[New World]'/minecraft:the_nether
[21:00:38] [Server thread/INFO]: [Yumatan: Set own game mode to Creative Mode]
[21:00:38] [Render thread/INFO]: [CHAT] Set own game mode to Creative Mode
[21:00:43] [Server thread/INFO]: Yumatan has reached the goal [Sky's the Limit]
[21:00:43] [Render thread/INFO]: [CHAT] Yumatan has reached the goal [Sky's the Limit]
[21:00:43] [Render thread/INFO]: Loaded 5 advancements
[21:01:07] [Render thread/WARN]: Reclaimed 2544 bytes at address 2170450651664 that were leaked from an unknown location (logging is disabled)
[21:01:07] [Render thread/WARN]: Reclaimed 134880 bytes at address 2170429752864 that were leaked from an unknown location (logging is disabled)
[21:01:07] [Render thread/WARN]: Reclaimed 864 bytes at address 2169854471632 that were leaked from an unknown location (logging is disabled)
[21:01:07] [Render thread/WARN]: Reclaimed 5760 bytes at address 2169733547088 that were leaked from an unknown location (logging is disabled)
[21:01:07] [Render thread/WARN]: Reclaimed 20232 bytes at address 2170538064336 that were leaked from an unknown location (logging is disabled)
[21:01:07] [Render thread/WARN]: Reclaimed 16960 bytes at address 2169862699312 that were leaked from an unknown location (logging is disabled)
[21:01:48] [Server thread/INFO]: [Yumatan: Set own game mode to Spectator Mode]
[21:01:48] [Render thread/INFO]: [CHAT] Set own game mode to Spectator Mode
[21:01:59] [Server thread/INFO]: [Yumatan: Set own game mode to Creative Mode]
[21:01:59] [Render thread/INFO]: [CHAT] Set own game mode to Creative Mode
[21:02:53] [Render thread/INFO]: [CHAT] Saved screenshot as 2022-06-01_21.02.53.png
[21:03:04] [Render thread/INFO]: [CHAT] Saved screenshot as 2022-06-01_21.03.04.png
[21:03:09] [Render thread/INFO]: [CHAT] Saved screenshot as 2022-06-01_21.03.08.png
[21:03:23] [Server thread/INFO]: Saving and pausing game...
[21:03:23] [Server thread/INFO]: Saving chunks for level 'ServerLevel[New World]'/minecraft:overworld
[21:03:23] [Server thread/INFO]: Saving chunks for level 'ServerLevel[New World]'/minecraft:the_end
[21:03:23] [Server thread/INFO]: Saving chunks for level 'ServerLevel[New World]'/minecraft:the_nether
[21:03:24] [Server thread/INFO]: Yumatan lost connection: Disconnected
[21:03:24] [Server thread/INFO]: Yumatan left the game
[21:03:24] [Server thread/INFO]: Stopping singleplayer server as player logged out
[21:03:24] [Server thread/INFO]: Stopping server
[21:03:24] [Server thread/INFO]: Saving players
[21:03:24] [Server thread/INFO]: Saving worlds

Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Server thread"

Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Thread-1"

Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "IO-Worker-18"

Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Worker-Main-13"

Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Render thread"

Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Worker-Main-3"
AL lib: (EE) alc_cleanup: 1 device not closed
Process exited with code 1.
Clipboard copy at: 01 Jun 2022 21:07:19 -0300

Edit by Madis0: formatted and collapsed logs

Reclaimed 3264 bytes at address 2170457855568 that were leaked from an unknown location (logging is disabled)

These lines are interesting, though I'm not sure what they really refer to.
Could you disable the JVM flags that are added by this modpack in instance settings? You could also try disabling the RAM limits.

These lines are interesting, though I'm not sure what they really refer to. Could you disable the JVM flags that are added by this modpack in instance settings? You could also try disabling the RAM limits.

I'm not sure how to do this... Would you mind helping me? I'm using MultiMC launcher, where should I go to change those configs?

Ok, I'm not sure if it that what you meant, but I disabled Java Arguments and Memory on the Settings tab in MultiMC (I just unticked the boxes) and it made it better. I still have some spikes in TPS and FPS but they are not happening that often and are sparse, not compromising gameplay at all. I'll do some more testing later today. Thanks for the insight.

Yes, that is what I meant. When you test today, please confirm whether you actually needed to uncheck both boxes or just one of them (I am assuming memory is the culprit).

Got it, then I'll probably remove both in the next version.

Aren't the JVMs flags in FO Just the vanilla ones ?

Aren't the JVMs flags in FO Just the vanilla ones ?

They are from the Fabric Loader installer -> vanilla launcher. But I guess there may still be differences in launchers which cause this, e.g. LWGJL and Java versions.

Isn't that a memory leak from some mod?

CaffeineMC/sodium-fabric#1024 - I wouldn't touch memory settings and just wait for this to be fixed.

Well, that update can take time so I would assume it's better to workaround it on FO side...

so this'll be getting a fix? LETS GOOOO

literally the only reason my performance sucks so much

the drops are usually way lower with pregenerated chunks, so this is mostly a slow chunk loading issue

though it could also be mipmaps

there is usually less drops with pregenerated chunks, so this is mostly a slow chunk loading issue

In that case you could try #305

sure, is there a fix for this on serverside though? elytra users use a lot of ram

the only solution i know is pregenerating chunks, but its a bad idea to do this before new 1.19 update because deep dark

oh right i can just loot the elytras in a 5k-10k radius

sure, is there a fix for this on serverside though? elytra users use a lot of ram

FO has never been supported on the server. See the wiki for more info and what can you use on the server.

Presumably fixed in 3.9.0


text:
Fixed potential issues and cleaned up old unused stuff

Added null checks to mitigate errors when not connected or still connecting
Renamed "Voiation" to "Violation" (UI only)
Removed remnants of XP and levels

Yay, thanks. :)

source: gharchive/pull-request

repo: Facepunch/webrcon

license: mit

license_source: bigquery


text:
why use mjml?

first, mjml & mjml-react did a great job!  save lots of my working time.
while we build a dynamic email(with identity user info, aka, username).
react email -> mjml-react -> mjml -> html
so, i just concern why do not transfer react email directly to html
react email(with mjml-dsl in react component) -> html
with react server render function, like this API renderToStaticMarkup maybe have some

render performance improvement
more easy to use for react developer ( mjml-react did also)

Hi @fuchao2012. I am not sure I understand what you mean. The render function for v3 of mjml-react is unchanged from V2 and it uses renderToStaticMarkup. We just moved it here to limit the dependencies on the core package export.
We also only leave this render in as an example/suggestion as we recognize it may not work for everybody. It should be possible to implement a way of going from an email built with mjml-react to html that works best for your project.

thx for the quick answer. @emmclaughlin .
i was working on a DSL writen in react, which intend to generate react -> email html, just like mjml do.
after finish this, while people can just use react to write email. (you must know the s**k experience of writing table..tr...td)
in mjml
// notice.mjml
<mj-section>
    <mj-column>
        <mj-button>hello world</mj-button>
    </mj-column>
</mj-section>

in react
// notice.tsx
<MjSection>
     <MjColumn>
         <MjButton>Hello world</MjButton>
     </MjColumn>
</MjSection>

above this what mjml-react do

i am concern that, while we transfer react email into mjml then into html, Is there room for performance improvement here?
Why don't we just render react as email， Must we transfer into mjml?
this is my question.
take mjml-button as a example in mjml source code.
// mjml-button.js
class MjButton extend BodyComponent {
   styles: xxx,
   attributes: xxx,
   render(){
       // button in html tables
  }
}

can we just change it  into react code like
// react-dsl-button.tsx

const DslButton = (props) => {
   const {styles, attributes} = props;
   return (
       // button in html tables
   )
}

When used this dsl component, again, you can call the react API renderToStaticMarkup  directly render the react component as email
Just as what i say, render function like here, still dependent on mjml2html API from mjml, which is not what i want.
Maybe a picture is worth a thousand words？ ；-p

Thanks again for your quick reply and look forward to discussing email rendering techniques with you

what i wana do ,just done by the follow guys, they are realy great!

React Email - A collection of high-quality, unstyled components for creating beautiful emails using React and TypeScript.
Mailing - Build emails in React, send from anywhere.
JSX-email - JSX Mail is an email framework that uses React to create email templates.

Thank you for clarifying, that makes sense.
Mjml does not render to html in isolation. That is, we can't just replace the content of an mjml-react component with equivalent html. This project chooses to rely on mjml2html as emails are difficult and mjml does a great job of reducing the work required by developers to build emails that safely render across the multitude of email clients.
There are definitely packages that build emails in a different way, and many are likely good and potentially render the react code html faster. However, for this application the focus is on enabling developers to get all the benefits of using mjml to develop emails while still working in a react environment.
In short, the reason to use mjml is to build emails that look great and work across many email clients.

repo: Faire/mjml-react


text:
Add external-probes policy

This policy matches pod specifications that specify an external host in a livenessProbe or readinessProbe, which may be undesirable RE: Pod probes lead to blind SSRF from the node  #99425.
The checkPod rule avoids checking pods with a
metadata.ownerReference, to avoid duplicate action-items for pods that belong to
other pod-controllers also checked by this same policy.
This was tested against:

A deployment with a single container, whos readinessProbe targets an external host.
A deployment whos second container has a readinessProbe targeting an
external host.
A single pod whos readinessProbe targets an external host.
A cronJob with a readinessProbe targeting an external host.

Description

Checklist

[ ] I have updated the CHANGELOG of any plugins updated
[ ] I have updated the version file of any plugins updated
[ ] I have added tests wherever appropriate
[ ] I have labeled this PR with a label per plugin updated

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant ivanfetch

repo: FairwindsOps/insights-plugins


text:
Allow FAMC.PEDI to indicate which spouse it refers to

The INDI.FAMC structure allows several substructures to clarify the relationship between parents and child: PEDI to note its kind, STAT to note its confidence, and NOTE``/SNOTE for notes.
However, it does not provide a standard way to indicate which parent is being discussed.
For example, we can indicate both birth and foster families as such
0 @I1@ INDI
1 FAMC @F1@
2 PEDI BIRTH
1 FAMC @F2@
2 PEDI FOSTER

but we cannot indicate with this structure that one partner of the FAM is the birth parent and the other is not.
For adoption we can use the ADOP.FAMC.ADOP:
0 @I2@ INDI
1 ADOP Y
2 FAMC @F3@
3 ADOP HUSB

be we don't have a similar tool for other cases.

I propose we add a ADOP.FAMC.ADOP-like structure with its same four options to go under PEDI, FAMC-STAT, BIRT.FAMC, and CHR.FAMC.
I tentatively propose the tag PARENT, though I'm not crazy about that tag; alternatives welcome.
Combined with the change in cardinality of PEDI from #256/#274, this would let us do things like
0 @I3@ INDI
1 FAMC @F4@
2 PEDI BIRTH
3 PARENT WIFE
1 FAMC @F5@
2 PEDI FOSTER
3 PARENT BOTH
2 PEDI ADOPTED
3 PARENT HUSB

This may also help resolve #334 which requests per-parent PEDI-like information

My opinion is that the PARENT.BOTH model is too limited because it doesn't allow a per-parent substructure.   For comparison, https://www.familysearch.org/developers/docs/api/types/xml_fs_ChildAndParentsRelationship shows that FamilySearch FamilyTree (and similarly GEDCOM X) does allow a per-parent substructure.   That allows specifying a different source, or other information, per parent.

Discussion 8/17/2023: PEDI tags are now {0:M} in 7.1 in #274 so it can now be used with parent-specific substructures, which resolves my concern.

Discussed in steering committee
We want to proceed with this to fill the need currently motivating the _FREL and _MREL extensions. _FREL and _MREL are currently not the ideal solution because they overlap in meaning with PEDI.
There is some potential overlap in meaning between one PEDI with BOTH and two, one with HUSB and one with WIFE. In particular, consider
1 FAMC @F1@
2 PEDI FOSTER

This option is what 5.5.1 and 7.0 has and does not specify which parents are meant. We expect many of them implied both parents, but can't assert that in general
1 FAMC @F1@
2 PEDI FOSTER
3 PARENT BOTH

This option is more compact
1 FAMC @F1@
2 PEDI FOSTER
3 PARENT HUSB
2 PEDI FOSTER
3 PARENT WIFE

This option is more versatile
To resolve this, we propose not including the BOTH value, only HUSB and WIFE, and recommending including two PEDI if a user wishes to explicitly indicate that both partners are meant.

As I drafted a PR for this, I can no longer follow our rationale against BOTH. As far as I can tell, we were opposed to having the ability to split a structure into two structures that jointly provide the same information. But that is something done all over GEDCOM: any time there's a {0:M} cardinality structure with a {0:M} cardinality substructure, or a <List:Enum> payload with {0:M} cardinality, or the g7:ALIA structure in any form we are faced with the same potential for someone to decide to split a structure into pieces or not. I don't see how this is different, and am not happy with requiring duplicate information (repeated DATE and STAT) if we want to assert the same PEDI applies to both parents.
In case I have misunderstood/misremembered the rationale agaisnt BOTH, there are two other approaches we could take to avoid duplicating information: make PEDI.PARENT either a <List:Enum> or have {0:M} cardinality.
1 FAMC @F1@
2 PEDI FOSTER
3 PARENT HUSB, WIFE

1 FAMC @F1@
2 PEDI FOSTER
3 PARENT HUSB
3 PARENT WIFE

As I drafted a PR for this, I can no longer follow our rationale against BOTH. As far as I can tell, we were opposed to having the ability to split a structure into two structures that jointly provide the same information. But that is something done all over GEDCOM: any time there's a {0:M} cardinality structure with a {0:M} cardinality substructure, or a <List:Enum> payload with {0:M} cardinality, or the g7:ALIA structure in any form we are faced with the same potential for someone to decide to split a structure into pieces or not. I don't see how this is different, and am not happy with requiring duplicate information (repeated DATE and STAT) if we want to assert the same PEDI applies to both parents.
In case I have misunderstood/misremembered the rationale agaisnt BOTH, there are two other approaches we could take to avoid duplicating information: make PEDI.PARENT either a <List:Enum> or have {0:M} cardinality.
1 FAMC @F1@
2 PEDI FOSTER
3 PARENT HUSB, WIFE

1 FAMC @F1@
2 PEDI FOSTER
3 PARENT HUSB
3 PARENT WIFE

The rationale was just to remove multiple ways of doing the same thing.  So BOTH vs separate info for each, are two ways of doing the same thing, and we already have to support separate info for each in the case where the info is different for each.
I agree that either of the two approaches quoted above are better than BOTH.  The first one (using a list) seems overkill for a list whose max size is 2.  The second one seems fine to me, and supports the case where extensions put substructures under the PARENT tag and want different info per parent.

Off the top of my head I question the removal of “BOTH” vs the two proposed options as they relate to create SQL queries against the column FAMC.PEDI. PARENT
1 FAMC @F1@
2 PEDI FOSTER
3 PARENT HUSB, WIFE

And
1 FAMC @F1@
2 PEDI FOSTER
3 PARENT HUSB
3 PARENT WIFE

Whereas:
1 ADOP Y
2 FAMC @F3@
3 ADOP HUSB

Provides a single column for this data!  I rather see:
1 FAMC @F1@
2 PEDI [ADOP | FOSTER | BIRTH | … ]
3 PARENT BOTH

Parent-child links
The original proposal seeks to allow the INDI.FAMC structure to describe the pedigree of the associated parent-child links separately, along with any changes over time (https://github.com/FamilySearch/GEDCOM/issues/256, https://github.com/FamilySearch/GEDCOM/issues/339).
Therefore it no longer makes sense begin by stating a PEDI and whether this applies to the FAM.HUSB, FAM.WIFE, or both.  Instead, the pedigree history for each parent should be clearly and separately described.  A suggested approach is:
+1 FAMC @<XREF:FAM>@                     {0:M}    g7:INDI-FAMC
     +2 HUSB                             {0:1}
        +3 PEDI <Enum>                   {0:M}    g7:PEDI
           +4 STAT                       {0:1}    g7:FAMC-STAT
           +4 DATE <DateValue>           {0:1}    g7:DATE
     +2 WIFE                             {0:1}
        +3 PEDI <Enum>                   {0:M}    g7:PEDI
           +4 STAT                       {0:1}    g7:FAMC-STAT
           +4 DATE <DateValue>           {0:1}    g7:DATE

In the simplest form, this is no more verbose than the PEDI per parent in the original proposal.
Example:
1 FAMC @F1@
2 HUSB
3 PEDI BIRT
2 WIFE
3 PEDI BIRT

More complex cases:
1 FAMC @F1@
2 HUSB
3 PEDI FOSTER
4 DATE FROM 1997 TO 1999
3 PEDI ADOP
4 DATE FROM 2000
2 WIFE
3 PEDI BIRT

The ordering of the PEDI or dates could be used to infer the latest / preferred / current status and may benefit applications where only one pedigree status may be stored / described at a time.

Family-event links
With any of the proposed changes to the INDI.FAMC structure, it is not necessary for ADOP.FAMC, BIRT.FAMC, CHR.FAMC and SLGC.FAMC to carry full information about pedigree as this simply ends up facilitating two ways to describe the pedigree.  The INDI.FAMC structure is the natural place for pedigree rather than in any events which happen to be associated with that.
Moreover, whilst it may be desirable to link certain events to the associated FAM, this option is not available for generic events (e.g. an event corresponding with the FOSTER).  In such as case, the links to the parents involved would need to be made using the ASSO with ROLE.  This may be a better candidate for linking individuals involved in these 'child-family events' rather than FAMC.

While I agree that the informational representation makes sense, from a data normalization standpoint it is incorrect!
In this model, the subtags for FAMC should/must be broken out into a new record type to provide for the M-M relationship.  This is why the ADOP event tag with its underlying subtags must be maintained and can provide for multiple adoption events for an individual.  The addition of a FOST (foster) event tag with similar subtags as ADOP would also be warranted!
I would recommend against the proposed changes to the FAMC to include unnormalized subtags.

ADOP.FAMC, BIRT.FAMC, CHR.FAMC and SLGC.FAMC are all events and event based data (date, place, notes, restriction, religious affiliation, etc) should be maintained only with the event.  Splitting information as suggested would be the wrong approach!

There is no suggestion of splitting information from an event.  Events are permitted to include one or more ASSO structures to define the role of other individuals in the event.  It can already be exploited to link any pedigree related event to one or both of the associated parents without the need for the use of pointers to a given FAM record.
1 EVEN
2 TYPE Foster
2 ASSO @I2@
3 ROLE FATH

1 ADOP
2 ASSO @I2@
3 ROLE PARENT
2 ASSO @I3@
3 ROLE MOTH

There is also nothing in these suggestions preventing multiple adoptions or other pedigree related events, if this were appropriate.
The current state is that a GEDCOM reader needs to interpret all ADOP.FAMC, SLGC.FAMC, BIRT.FAMC, CHR.FAMC and INDI.FAMC structures, just to be sure it can determine the correct pedigree for a given parent-child relationship.  This is not desirable and must be considered in the solution to this issue.

The current state is that a GEDCOM reader needs to interpret all ADOP.FAMC, SLGC.FAMC, BIRT.FAMC, CHR.FAMC and INDI.FAMC structures, just to be sure it can determine the correct pedigree for a given parent-child relationship. This is not desirable and must be considered in the solution to this issue.

What is wrong with checking and actually reading the information already found in the ADOP, SLGC, … events where the information should be contained?  My software already does this when building the relationships between the INDI and FAM record.
You must go to the ADOP event or any other EVEN.FAMC to check if the event is restricted before making the connection between the individual and the family record when displaying the connection, so if go there for that then just go there for who did the adoption, when and where!

And why must you indicate FATH or MOTH?  That can be found when going to the family record and checking the link for SEX, or alternatively a Gender if added to the GEDCOM Standard.

What is wrong with checking and actually reading the information already found in the ADOP, SLGC, … events where the information should be contained? My software already does this when building the relationships between the INDI and FAM record.

It is assumed that all contributors are capable of writing code which can interpret GEDCOM which is compliant with the specifications as written (as indeed all my applications do).  This does not imply the current design is desirable or should be retained.  The requirement to query multiple structures needlessly increases the overhead to accurately determine the pedigree of a given parent-child link.
GEDCOM 7.0 did not make any substantive changes to FAMC related structures, retaining the GEDCOM 5.4+ behaviour.  It is perfectly reasonable to question aspects of a 27 year old design which have not seen consistent or robust implementation by developers (as exemplified by prolific use of _FREL and _MREL tags).

You must go to the ADOP event or any other EVEN.FAMC to check if the event is restricted

No version of GEDCOM to date has provided a mechanism to assert a RESN relating to the pedigree status between a child and their parent.

And why must you indicate FATH or MOTH? That can be found when going to the family record and checking the link for SEX, or alternatively a Gender if added to the GEDCOM Standard.  If you indicate MOTH, which mother in a same sex adoption?

A description of 'mother', 'father' may not be be indicated by the biological sex of a parent.  The examples given show the optional use of ASSO with ROLEs of FATH, MOTH, and PARENT thus supporting any 'biological sex' or 'gender identity' pertaining to the associated parents, independently of their 'INDI.SEX' value.  Nothing suggested precludes adoption by a same sex couple.

If you indicate MOTH, which mother in a same sex adoption?

This mother is clearly indicated by the individual pointed to by the parent ASSO.  Nothing prevents two ASSO structures, pointing to different individuals, with ROLE of MOTH.

No version of GEDCOM to date has provided a mechanism to assert a RESN relating to the pedigree status between a child and their parent.

So your interpretation of the ADOP.RESN tag in conjunction with a ADOP.FAMC and ADOP.FAMC.ADOP does not provide a mechanism?
I use the following successfully to set a restriction on the information to connect the Adoption of a this individual to the member of the family indicated (Wife individual, Husband individual, Both individuals:
1 ADOP
2 DATE ...
2 RESN ...
2 FAMC @...@
3 ADOP [HUSB | WIFE | BOTH ]

We could update the ADOP tag in the following way to add additional precision to allow for the adoption event to be restricted or the indication of who adopted the individual.  :
n ADOP [Y|<NULL>]
+1 TYPE <Text>
+1 <<INDIVIDUAL_EVENT_DETAIL>>
+1 FAMC @<XREF:FAM>@
+2 ADOP <Enum>
+3 PHRASE <Text>
+3 RESN <List:Enum>

The following would indicate the event of an adoption (date, place) has no restriction but the fact that the individual indicated by the HUSB relationship is restricted.  Valuable when a same sex couple does not want to indicate who is the potential biological parent vs the none biological parent.

1 ADOP
2 DATE ...
2 FAMC @...@
3 ADOP HUSB
3 RESN ...

This mother is clearly indicated by the individual pointed to by the parent ASSO. Nothing prevents two ASSO structures, pointing to different individuals, with ROLE of MOTH. Nothing suggested precludes adoption by a same sex couple.

An ADOP.ROLL indicating "Mother" is not neccessary since this indicates a SEX that may not be the individuals current Gender and should be left to the actual indication within the INDI.SEX tag for that person.

GEDCOM 7.0 did not make any substantive changes to FAMC related structures, retaining the GEDCOM 5.4+ behaviour. It is perfectly reasonable to question aspects of a 27 year old design which have not seen consistent or robust implementation by developers (as exemplified by prolific use of _FREL and _MREL tags).

While I agree that it is perfectly reasonable to question any structure regardless of its age (27 years or 1 Day), I'm not convinced that _FREL and _MREL as part of the family record or implemented in other ways is the correct answer!  As I've indicated, the violation of normalization design is not desirable as well.  The overhead of looking at a different structure may or may not be increased, this all depends on how the back-end database is designed and loaded.  In my case the entire Individual Record (INDI) is in memory so the overhead is almost zero.  On the other-hand if the load uses the FAMC level 1 tag to generate a relationship and no other data from other Events (ADOP.FAMC, BIRT.FAMC, CHR.FAMC and SLGC.FAMC) in considered, then the load should be changed so runtime does not have the overhead.
The removal of the EVENT.FAMC has other implication as well.  Conversion of the current EVENT.FAMC in v7.13 and earlier to an EVENT.ASSO in the future can not be directly made without loading the FAM record then extracting the INDI link for that person, then loading the parent INDI record to determine the SEX (if not restricted) so we can indicate MOTH/FATH in the child record.

I could be convinced of the following for an adoption:
1 ADOP
2 DATE ...
2 PLACE ...
2 FAMC @F1@
3 ADOP BOTH
3 RESN ...

1 FAMC @F1@
2 PEDI ADOPTION
3 PARENT BOTH
3 RESN ...

Where the ADOP.FAMC.ADOP and FAMC.PEDI.PARENT can be [WIFE | HUSB | BOTH].  I'm not sure why "BOTH" is not liked by some individuals!
Birth information would be the same with the only change other than the BIRT tag would be the PEDI tag.
These would be consistent with the current model require minimal changes during conversion and satisfy the need for the FAMC to indicate some form of relationship to the FAM record with the RESN to restrict the information when wanting to hide the birth/biological or adoptive parent.
I've always though of the Birth parents as the biological ones, if birth indicates to some "the people present or given the child at the birth" (mostly needed to hide the world from truths they are not ready for), a new and different Event or Fact should be indicated/created so a specific meaning for the BIRT tag can be established!

Discussed in steering committee
Based on 4 voices with 4 opinions, we are rethinking this and maybe not adding it.
Adoption: use INDI.ADOP.FAMC.ADOP to indicate who adopted by. Thus the INDI.FAMC with PEDI ADOPTED does not indicate whether they were adopted by one or both partners; that information is in the adoption event instead.
Foster: make a FAM with the partners who fostered and point to it with the FAMC that has a PEDI.FAMC. Thus the INDI.FAMC with PEDI FOSTER does indicate that each of the partners in the FAM were involved in the fostering.
Birth: have a BIRT.FAMC pointing to a FAM with the parents who were recognized as such at birth. Thus the INDI.FAMC with PEDI BIRT does indicate that each of the partners in the FAM were involved in the birth, and should not be used for step-families where one partner is a birth parent the another is not.
Those are the only three PEDI in the current spec, so the PEDI.PARENT may not be needed at this time.
This begs two questions.

Does this invalidate how any current tool is interpreting the current spec?
How do we communicate these uses – presumably briefly in the spec and in more detail in the technical FAQ?

We welcome additional comments, input, and ideas

Does this invalidate how any current tool is interpreting the current spec?

Inclusion of an associated adoption event or use of ADOP.FAMC.ADOP was always optional.  Thus, a GEDCOM writer is free to use PEDI ADOPTED in the same way that you suggest for birth and foster.  It does not seem appropriate to restrict that use.
The only time that PEDI ADOPTED does not apply to both partners is if ADOP.FAMC.ADOP indicates otherwise.  This special case allows for one adoptive and one birth parent in a family, potentially avoiding the need for two FAM records.

authors: Norwegian-Sardines chronoplexsoftware dthaler elyoh tychonievich

repo: FamilySearch/GEDCOM


text:
OSK 2002 Informal Statement

[ ] Original
[x] English translation

Sekalian tahun kedepannya juga 😀


text:
Support Image Maker not functioning with new event CE

Preparation

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

FGO server
NA
FGA build number
1483
Describe the bug
Used Support Image Maker for Scenic Beauty Craft Essence.
However, in the Support List, it does not detect the CE at all.
Video
Recording evidence:

Device model
Samsung Galaxy J7 Prime
Android version
8
Screen size
1080 x 1920
RAM
3 GB

Your video is private, not unlisted.

Your video is private, not unlisted.

Hi, I've fixed it. It's unlisted now. So sorry for that minor hiccup.

The Friend option selection is working well. It's only the event CE not detecting at all, strange.
Thanks for creating this app, it's been helping me rest while I work hahaa.

I'm seeing that 10/10/10 does not seem to work.

Duplicate of #850

Thanks - I didn't know it's a duplicate issue.

Btw, just use event CE filters built into FGO, no need to create new support images.

authors: JusKIdding reconman

repo: Fate-Grand-Automata/FGA


text:
🛑 Asset Delivery is down

In 426c6a3, Asset Delivery (https://assetdelivery.roblox.com) was down:

HTTP code: 404
Response time: 80 ms

Resolved: Asset Delivery is back up in 91fceaf after 41 minutes.

repo: FearedFusionX/Ro-Status


text:
🛑 Voice Chat API is down

In 36494d4, Voice Chat API (https://voice.roblox.com/) was down:

HTTP code: 404
Response time: 156 ms

Resolved: Voice Chat API is back up in 2ba4992 after 3 minutes.


text:
Idea - Delay for Update for Players

Hi!
I have an idea for your awesome tool.
Dont know if its possibile - maybe im dreaming too much.
So, Im running crontabs to automate (Mod)Updates.  which is a very nice feature. But sometimes there ar updates in primetime, where raids are going on. My idea was, to give the normal players an command, to do an Update later. I thought about an chatcommend, which had to be used of X% of connected players to force the server to an cancelupdate and do it later a day. Maybe only 1 time useable for each update.
What do you think about it? Would it be possibile?

This has now been added to 1.6-dev.unstable
This monitors the ServerGame log (which requires the arkflag_servergamelog=true option), and cancels the update if /cancelupdate has been said in the last 5 minutes.

Dammed thats awesome!
Would it be possible to set how many players, or better to set how many percent of connected players has to do this command? Think there will be some trolls if one command is enought to cancel the update. And is it possibile to flag players who had used this command? For trolls again, if they try to move the update over half day. Or maybe if an update got canceled, and the next update cant if this is easier for you.

Be carefull about using servergame log https://survivetheark.com/index.php?/forums/topic/8280-server-game-log-server-stability-note-for-server-admins/

Unfortunately the other option would be to use the RCON GetChat command, which fetches the chat log buffer.  However, it also clears the chat log buffer, and so would not work if another RCON client is monitoring chat.
Another option would be a mod that monitors chat.  However, I think this is beyond the scope of this project.

For Arma 2 and 3, there are tools to monitor the Server within BattleEye, but i dont know, if this is possible in ARK and how far BattleEye is implemented to it. Give me some hours (or days :P), i will search for other ways to do this. I think this could be a very nice and helpful feature.

authors: arkfrancegaming klightspeed talpidae

repo: FezVrasta/ark-server-tools


text:
Libc issue on Debian Bullseye

Hello,
Thanks for this cool plugin !
I'm trying to use the lv2 version on Debian Bullseye (inside Carla) but there's a libc mismatch (2.31-13+deb11u6)

Do you think of anything that could avoid this ?
Cheers
Erwan

Did you build yourself or use my binaries?

I used the binary (my cmake version is too old)
CMake Error at CMakeLists.txt:1 (cmake_minimum_required):   CMake 3.24.0 or higher is required.  You are running version 3.18.4

I've tried statically linking c++ standard library
I've also rolled back cmake requirement to 3.16
do either of those solve it for you?

Hello,
1.0.10 binary (lv2) is loading now !
I have try to compile it but i'm getting this :
  CMake 3.22 or higher is required.  You are running version 3.18.4
Let's have fun now :)
Thanks

repo: FigBug/Wavetable


text:
🛑 logs.mmattbot.com is down

In f10e73a, logs.mmattbot.com (https://logs.mmattbot.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: logs.mmattbot.com is back up in e90264d after 27 minutes.

repo: Fijxu/justlog-instances-uptime


text:
🛑 logs.spanix.xyz is down

In 35aa664, logs.spanix.xyz (https://logs.spanix.xyz/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: logs.spanix.xyz is back up in 70b791b.


text:
Revert "Blog Content Update"

reverting to previous version due to errors.
error on fil.org:
{     "m.server": "fil.ems.host:443" }
error on fil.org/blog:
ipfs resolve -r /ipfs/bafybeic4og7mkly4xszdwz44dpszdmjvzvmt6lzhbxjmgey7jwc632rpta/blog: func called on wrong kind: "LookupBySegment" called on a data.Bytes node (kind: bytes), but only makes sense on map or list

@matthendrian this issue is fixed with the latest rebuild, so if it's okay with you, I'm closing this PR (feel free to re-open if you actually want to revert for content reasons)

authors: matthendrian orvn


text:
chore: release main

:robot: I have created a release beep boop
app-info: 1.0.2
1.0.2 (2022-10-12)
Bug Fixes

add the @readonly tag to appInfo properties (8ea488a)

errors: 1.2.3
1.2.3 (2022-10-12)
Bug Fixes

correct property and method privacy JSDoc (1b52fee)
use module.exports for consistency (8cdd4d7)

log-error: 1.3.7
1.3.7 (2022-10-12)
Bug Fixes

correct property and method privacy JSDoc (1b52fee)
use module.exports for consistency (8cdd4d7)

Documentation Changes

use GitHub's note/warning highlights (4a40080)

Dependencies

The following workspace dependencies were updated

dependencies

@dotcom-reliability-kit/app-info bumped from ^1.0.1 to ^1.0.2
@dotcom-reliability-kit/serialize-error bumped from ^1.1.2 to ^1.1.3
@dotcom-reliability-kit/serialize-request bumped from ^1.0.1 to ^1.0.2

middleware-log-errors: 1.2.8
1.2.8 (2022-10-12)
Bug Fixes

correct property and method privacy JSDoc (1b52fee)

Documentation Changes

use GitHub's note/warning highlights (4a40080)

Dependencies

The following workspace dependencies were updated

dependencies

@dotcom-reliability-kit/log-error bumped from ^1.3.6 to ^1.3.7

middleware-render-error-info: 1.1.6
1.1.6 (2022-10-12)
Bug Fixes

correct property and method privacy JSDoc (1b52fee)

Documentation Changes

use GitHub's note/warning highlights (4a40080)

Dependencies

The following workspace dependencies were updated

dependencies

@dotcom-reliability-kit/app-info bumped from ^1.0.1 to ^1.0.2
@dotcom-reliability-kit/log-error bumped from ^1.3.6 to ^1.3.7
@dotcom-reliability-kit/serialize-error bumped from ^1.1.2 to ^1.1.3

serialize-error: 1.1.3
1.1.3 (2022-10-12)
Bug Fixes

correct property and method privacy JSDoc (1b52fee)

serialize-request: 1.0.2
1.0.2 (2022-10-12)
Bug Fixes

correct property and method privacy JSDoc (1b52fee)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/Financial-Times/dotcom-reliability-kit/releases/tag/app-info-v1.0.2 :sunflower:

:robot: Release is at https://github.com/Financial-Times/dotcom-reliability-kit/releases/tag/errors-v1.2.3 :sunflower:

:robot: Release is at https://github.com/Financial-Times/dotcom-reliability-kit/releases/tag/log-error-v1.3.7 :sunflower:

:robot: Release is at https://github.com/Financial-Times/dotcom-reliability-kit/releases/tag/middleware-log-errors-v1.2.8 :sunflower:

:robot: Release is at https://github.com/Financial-Times/dotcom-reliability-kit/releases/tag/middleware-render-error-info-v1.1.6 :sunflower:

:robot: Release is at https://github.com/Financial-Times/dotcom-reliability-kit/releases/tag/serialize-request-v1.0.2 :sunflower:

repo: Financial-Times/dotcom-reliability-kit


text:
Twitter official app in-app browser on iOS not working

When we open Twitter official app in-app browser from tweets or something, polyfill does not work properly.
My environment is:

Device: iOS 10.2.1
App version: 6.73.2

A Twitter official apps User-Agent is:
Mozilla/5.0 (iPhone; CPU iPhone OS 10_2_1 like Mac OS X) AppleWebKit/602.3.12 (KHTML, like Gecko) Mobile/14D27 Twitter for iPhone

I accessed with remove min,  the server responds:

/* Polyfill service v3.17.0
 * For detailed credits and licence information see https://github.com/financial-times/polyfill-service ….
 *
 * UA detected: other/0.0.0 (unknown/unsupported; using policy `unknown=ignore`)
 * Features requested: Array.prototype.find,Array.prototype.findIndex,Array.prototype.includes,Element.prototype.dataset,IntersectionObserver,MutationObserver,default,fetch,http://performance.now
 *  */

/* No polyfills found for current settings */

And, I tried to investigate in development. Requested with ua and above User-Agent string:
http://localhost:3000/v2/polyfill.js?ua=Mozilla/5.0%20(iPhone;%20CPU%20iPhone%20OS%2010_2_1%20like%20Mac%20OS%20X)%20AppleWebKit/602.3.12%20(KHTML,%20like%20Gecko)%20Mobile/14D27%20Twitter%20for%20iPhone

And redponds:
/* Polyfill service DEVELOPMENT MODE - for live use set NODE_ENV to 'production'
 * For detailed credits and licence information see https://github.com/financial-times/polyfill-service.
 *
 * UA detected: ios_saf/10.2.0
 * Features requested: default
 *
 * - URL, License: CC0 (required by "default") */

with polyfill's code. I guess that the problem seems Normalized User-Agent in vcl.

When testing locally, were you using the code in master? If so, that has changes which are not yet live on https://polyfill.io. If it works in master branch, it will be fixed in the next release ✨

Yes, I've tested on master branch and it works. thanks!

I will close this issue as the fix will be in the next release :-) If you watch this repository or follow @polyfillio on twitter you will get notifications when we release new versions of the service.

authors: JakeChampion ysugimoto

repo: Financial-Times/polyfill-service


text:
Image not appearing

In Mendix 5.14.1, the image(s) do not appear in the carousel. I debugged it, and it appears it's obtaining the filename, rather than the guid. Updating line 286 to the following appeared to solve it:
carouselItem = carouselItem.split('{{img}}').join(window.location.origin +'/file?guid='+ objs[i].getGuid());

@bgeveritt thanks for the feedback, I've used the widget in 5.14.1 and not encountered this issue. However I your solution is the better practise and should be added.

Fixed in new release.

authors: bgeveritt simonmartyr

repo: Finaps/BootstrapCarousel


text:
Multiple Pages Feature

Hello,
I've done a modification that uses a single long list of resistor values (rather than the original 2D array) and outputs to multiple pages where required. If you're interested I can fork & make a pull request.
My update still uses the same three label layouts, but adds a column & row to the layout type. Then uses numpy to pad & rearrange the list into a 2D array, which are rendered and exported as before. I'm not a big python programmer so it may not be the most elegant but it seems to work well.

In general I like the idea. There is one usecase, though, which requires a 2D layout: if you want to print on sticker pages that have stickers removed already. For example, you printed all your stickers and need another new value. You have a half used sticker page, so you want to position the new value on the next unused sticker.
I specifically did the 2d layout for this usecase, because I didn't know from the beginning which resistor types I will have in the bags and printed new ones as I bought them.

Of course! I definitely did it more for my specific use case which was just "making a new set, no regard for previous prints," but that's something I'll expand upon a little more to see if there's a user friendly (esp wrt non-programmers) for it to work. Either way I'm happy to leave it just as a personal fork if you don't think it's necessary.
And yeah numpy was not my ideal - it's a lot for some simple array maths, it was more chosen for simplicity of programming. But also something I will investigate replacing with a couple loops instead.
Here's the pastebin if you'd like to take a look though: https://pastebin.com/LafCNFM8

In general, I think this is not a bad idea, but it would need wie some cleanup. I don't want to add any extra complexity in main(). That includes the comments inside of it, and the README.md file. I spent a lot of time to structure the project in a way that the readme file and in general the entire usage of the script is as simple as possible. Don't underestimate the effect such a change would have on those.

All good points. I'll have a think and see what I can come up with that work with the existing methods. And even then, no dramas if you prefer not to incorporate any changes, as I said I'm happy to leave it as a fork. Thanks!

After merging #18  and #16, it is now supported that either a 1D or 2D array can get specified, and it will get automatically broken down into rows, columns and pages.
Does this satisfy your usecase?
Greetz

@azrieltomas Without further activity, I will close this issue in a couple of days because I assume that the recent changes solved your problem.

Sorry for the delay - yeah that's fantastic. Thanks

Sorry for the delay - yeah that's fantastic. Thanks

No problem, glad to hear :)
Didn't mean to pressure you, just weren't sure if you are still active on github and see my message :)

authors: Finomnis azrieltomas

repo: Finomnis/ResistorLabels


text:
incompatible

Since all of these issues are closed I create a new one. For me and as I can see many others this is still an issue. It's breaking! I am not able to continue with my project!
Because http >=0.13.0 depends on http_parser ^4.0.0 and firebase >=7.0.0 <9.0.0 depends on http_parser ^3.0.0, http >=0.13.0 is incompatible with firebase >=7.0.0 <9.0.0.
And because firebase_storage >=8.0.0 depends on firebase_storage_web ^1.0.0 which depends on http ^0.13.0, firebase >=7.0.0 <9.0.0 is incompatible with firebase_storage >=8.0.0.

Hi @vogttho
When opening an issue, please try to provide all of the information indicated in the template.
Closing this issue, since no information has been provided.
Thank you.

authors: markusaksli-nc vogttho

repo: FirebaseExtended/flutterfire


text:
Code system references without codes defined throws an exception

library Test version '1.0.0'

codesystem "v3.ServiceDeliveryLocationRoleType": 'http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType'

define f: "v3.ServiceDeliveryLocationRoleType" is CodeSystem

Throws a KeyNotFound exception during compilation.
Expected value of f should be true according to the Java cqf ruler.

In our cql to elm compiler?

Yes.  More crucially, I wrote this test because this will fail.  We create codesystem declarations in our classes as CqlCode[] because I think you can use in on code systems as well as value sets, but this creates type confusion that will cause this operator to return false, and also prevents ChangeType from working, because our TypeResolver says a CodeSystemRef should be a CqlCodeSystem primitive.
`

Blocked. Waiting on #519

authors: EvanMachusak baseTwo

repo: FirelyTeam/firely-cql-sdk


text:
🛑 Collection is down

In 6637130, Collection (https://data.fitzmuseum.cam.ac.uk) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Collection is back up in 47e6704 after 27 minutes.

repo: FitzwilliamMuseum/uptime


text:
Add Nong Song: DANCE TILL YOU'RE DEAD

Song Name
DANCE TILL YOU'RE DEAD
Artist Name
RagenYT
Source
Youtube
Youtube Link
https://www.youtube.com/watch?v=r5_NvFTfAWc
Direct File Link
No response
Song ID
1
Start Offset [ms]
0
Extra
No response

accept

authors: FrozenPaperclip neprao

repo: FlafyDev/auto-nong-indexes


text:
Add Ben 10 phonk by ...

Song Name
Ben 10 phonk
Artist Name
...
Source
Youtube
Youtube Link
7hjWnoknt0A
Direct File Link
No response
Song ID
2
Start Offset [ms]
0
Extra
Created from Auto Nong.
Created for level: 13519
Downloaded: Yes

reject
popular songs like "Polargeist" are too inconvenient to be replaced by smth unrelated and are therefore usually rejected.
Note that you can still use the song yourself, but it won't be public

authors: Erik-Bas SpuckwasserDE


text:
Class 'FACTFinder\Core\AbstractConfiguration' not found

Start the Cron Job I get follow error:
Warning: include(FACTFinder\Core\AbstractConfiguration.php): failed to open stream: No such file or directory in /var/www/html/htdocs/lib/Varien/Autoload.php on line 94

Warning: include(): Failed opening 'FACTFinder\Core\AbstractConfiguration.php' for inclusion (include_path='/var/www/html/htdocs/app/code/local:/var/www/html/htdocs/app/code/community:/var/www/html/htdocs/app/code/core:/var/www/html/htdocs/lib:.:') in /var/www/html/htdocs/lib/Varien/Autoload.php on line 94

Fatal error: Class 'FACTFinder\Core\AbstractConfiguration' not found in /var/www/html/vendor/flagbit/factfinder/src/lib/FACTFinderCustom/Configuration.php on line 9
TRIGGER: shutdown function
Last error:
Array
(
    [type] => 1
    [message] => Class 'FACTFinder\Core\AbstractConfiguration' not found
    [file] => /var/www/html/vendor/flagbit/factfinder/src/lib/FACTFinderCustom/Configuration.php
    [line] => 9
)

Is it working if you start the job manually on shell?
Does you job change the directory before starting the script?

I execute the cron.sh in the project root directory.

The module is working in Shop. This exception only throwing if you execute the cron.sh?
Did you install magento with composer? Do you have a minimum setup to reproduce this error if you use composer?

Hello,
I have the same issue.
When generating the export from back office there is no error.
When using cron.sh I get the error "Class 'FACTFinder\Core\AbstractConfiguration' not found".
I tried including the lib/FACTFinder/Loader.php file in lib/FACTFinderCustom/Configuration.php , it solves the cron issue it is not usable from website.
The cron is not run using shell_exec but like that :
    Mage::getConfig()->init()->loadEventObservers('crontab');
    Mage::app()->addEventArea('crontab');
        Mage::dispatchEvent('always');
        Mage::dispatchEvent('default');

Any clue on how to fix this ?
Best regards,
Jonathan

Did you install magento and this extension via composer? I did a clean magento 1.9.3.10 demo store installation from scratch with this extension. The shedule sh script works fine for me. It looks like a problem with autoloading of factfinder's library.
@boehsermoe Did you use /var/www/html/htdocs or /var/www/html as magento-root-dir?
@boehsermoe and @jriboux is your vendor folder inside magento root or one folder above?
Can you provide me a minimal composer.json to reproduce your installation, please?

authors: boehsermoe jriboux mbraeuner

repo: Flagbit/Magento-FACTFinder


text:
Enable per-Flag Segments

It would be great to be able to define and manage a Segment specifically for a Flag, that is not shared with the Project as a whole. This would help with e.g. scheduled roll-out, as well as cases where the Segment is specific to the flag and would only work to add noise to the list of Segments within the project.
Need to give consideration to the Edge API and server-side SDKs too.

I could see this as being very helpful in keeping the clutter down significantly.

I'm going through some major restructuring as I'm coming off or our POC and moving into a QA environment.  I would find it very valuable if all flag variants could have segment like rules.  I seem to be creating a large number of duplicated data to have a segment and variant for each feature.

There are some things that need to be done on the Front End:

[ ] Don't show flag-based segments in the Project level Segments list - this data will be added to the API
[ ] Allow users to create Segments at a Flag level in the flag modal

https://github.com/Flagsmith/flagsmith/pull/1389 Adds a field named feature to both request (for create) and response(to identifiy feature based segments)
on /project/segment/ viewset

Ready to test under the flag flag_based_segments @dabeeeenster

authors: TD-4242 dabeeeenster gagantrivedi kyle-ssg

repo: Flagsmith/flagsmith


text:
feat: Add seats to next invoice

Thanks for submitting a PR! Please check the boxes below:

[x] I have run pre-commit to check linting
[x] I have filled in the "Changes" section below?
[x] I have filled in the "How did you test this code" section below?
[x] I have used a Conventional Commit title for this Pull Request

Changes
This simple fix of flipping a boolean pushes the invoice date for the new seat to the next billing period to satisfy this ticket.
How did you test this code?
I connected my local running code to the flagsmith-test chargebee account and manually added a seat then verified that the unbilled charges increased, see below:

Codecov Report
Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (99180cd) 95.54% compared to head (2c0b5a9) 95.56%.
Report is 6 commits behind head on main.

Files
Patch %
Lines

...ns/0008_add_manage_segment_overrides_permission.py
88.23%
2 Missing :warning:

api/app/settings/local.py
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2977      +/-   ##
==========================================
+ Coverage   95.54%   95.56%   +0.01%
==========================================
  Files        1013     1014       +1
  Lines       29331    29421      +90
==========================================
+ Hits        28025    28116      +91
+ Misses       1306     1305       -1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

authors: codecov-commenter zachaysan


text:
Added plugin to take JSON file(s) as input.

Motivation for changes:
Rather than convert JSON to csv or text parsing, simply use JSON.
Detailed changes:

Added plugin that takes either a JSON file or a directory containing multiple JSON files and converts the contents into entries.

Config usage if relevant (new plugin or updated schema):
tasks/templates:
  input_json_task_name:
    json:
      files: <filename here>.json OR
      files: '<path/to/JSON/files/>*.json'
      encoding: <JSON encoding here>
      entry:
        - <entry field name that also exists as a JSON field name>
        - <entry field name>: <JSON field name>
        - get_remnants

SCHEMA:
schema = {
    'type': 'object',
    'properties': {
        'files': {'type': 'string'},
        'encoding': {'type': 'string', 'default': 'utf-8'},
        'entry': {
            'type': 'array',
            'items': {
                'oneOf': [
                    {'type': 'string'},
                    {
                        'type': 'object',
                        'additionalProperties': {
                            'type': 'string', 'format': 'regex'
                        },
                    },
                ]
            },
        },
    },
    'required': ['files'],
    'additionalProperties': False,
}

Log and/or tests output (preferably both):

flexget --test execute --task input_json --debug --dump

2019-11-10 21:37 INFO     manager                       Test mode, creating a copy from database ...
2019-11-10 21:37 INFO     manager                       Test database created
2019-11-10 21:37 INFO     performance                   Enabling plugin and SQLAlchemy performance debugging
2019-11-10 21:37 VERBOSE  task_queue                    There are 1 tasks to execute. Shutdown will commence when they have completed.
2019-11-10 21:37 VERBOSE  details       input_json      Produced 6 entries.
2019-11-10 21:37 VERBOSE  task          input_json      ACCEPTED: `black` by accept_all plugin
2019-11-10 21:37 VERBOSE  task          input_json      ACCEPTED: `white` by accept_all plugin
2019-11-10 21:37 VERBOSE  task          input_json      ACCEPTED: `red` by accept_all plugin
2019-11-10 21:37 VERBOSE  task          input_json      ACCEPTED: `blue` by accept_all plugin
2019-11-10 21:37 VERBOSE  task          input_json      ACCEPTED: `yellow` by accept_all plugin
2019-11-10 21:37 VERBOSE  task          input_json      ACCEPTED: `green` by accept_all plugin
2019-11-10 21:37 VERBOSE  details       input_json      Summary - Accepted: 6 (Rejected: 0 Undecided: 0 Failed: 0)
-- Accepted: ---------------------------
title            : black
url              : https://google1.com
original_url     : https://google1.com
accepted_by      : accept_all
category         : hue
code             : 255,255,255,1
color            : black
original_task    : primary_task_name
original_title   : black
quality          : <LazyField - value will be determined when it is accessed>
task             : input_json

title            : white
url              : https://google2.com
original_url     : https://google2.com
accepted_by      : accept_all
category         : hue
code             : 0,0,0,1
color            : white
original_task    : primary_task_name
original_title   : white
quality          : <LazyField - value will be determined when it is accessed>
task             : input_json

title            : red
url              : https://google3.com
original_url     : https://google3.com
accepted_by      : accept_all
category         : hue
code             : 255,0,0,1
color            : red
original_task    : primary_task_name
original_title   : red
quality          : <LazyField - value will be determined when it is accessed>
task             : input_json

title            : blue
url              : https://google4.com
original_url     : https://google4.com
accepted_by      : accept_all
category         : hue
code             : 0,0,255,1
color            : blue
original_task    : primary_task_name
original_title   : blue
quality          : <LazyField - value will be determined when it is accessed>
task             : input_json

title            : yellow
url              : https://google5.com
original_url     : https://google5.com
accepted_by      : accept_all
category         : hue
code             : 255,255,0,1
color            : yellow
original_task    : primary_task_name
original_title   : yellow
quality          : <LazyField - value will be determined when it is accessed>
task             : input_json

title            : green
url              : https://google6.com
original_url     : https://google6.com
accepted_by      : accept_all
category         : hue
code             : 0,255,0,1
color            : green
original_task    : primary_task_name
original_title   : green
quality          : 720p hdtv
task             : input_json

2019-11-10 21:37 VERBOSE  list_add      input_json      adding accepted entries into entry_list - test
2019-11-10 21:37 INFO     performance                   Performance results for task input_json:
2019-11-10 21:37 INFO     performance                   list_add        took 0.58 sec (33 queries)
2019-11-10 21:37 INFO     performance                   status          took 0.22 sec (4 queries)
2019-11-10 21:37 INFO     manager                       Removed test database

Actual Config for above output:
tasks:
  input_json:
    accept_all: yes
    json:
      files: fake_data.json
      entry:
        - title: color
        - original_task: 't.*k'
        - get_remnants
    list_add:
      - entry_list: test

Actual fake_data.json:
{
"item1": {
      "title": "test_of_title1",
      "color": "black",
      "url": "https://google1.com",
      "category": "hue",
      "task": "primary_task_name",
      "code": "255,255,255,1"
      },

"item2": {
      "title": "test_of_title2",
      "color": "white",
      "url": "https://google2.com",
      "category": "hue",
      "task": "primary_task_name",
      "code": "0,0,0,1"
      },

"item3": {
      "title": "test_of_title3",
      "color": "red",
      "url": "https://google3.com",
      "category": "hue",
      "task": "primary_task_name",
      "code": "255,0,0,1"
      },

"item4": {
      "title": "test_of_title4",
      "color": "blue",
      "url": "https://google4.com",
      "category": "hue",
      "task": "primary_task_name",
      "code": "0,0,255,1"
      },

"item5": {
      "title": "test_of_title5",
      "color": "yellow",
      "url": "https://google5.com",
      "category": "hue",
      "task": "primary_task_name",
      "code": "255,255,0,1"
      },

"item6": {
      "title": "test_of_title6",
      "color": "green",
      "url": "https://google6.com",
      "category": "hue",
      "task": "primary_task_name",
      "code": "0,255,0,1",
      "quality": "hdtv 720p"
      }
}

To Do:

[ ] Discuss how much to de-serialize
[ ] Discuss where to de-serialize

I only de-serialize datetime strings to datetime object. Everything else is left as a string. More decoding can be added in the future, if it is needed. I think this one is ready to go, if one of you all could do one last review.

I modified your plugin a bit to simplify as many things as I could, which could be used as a model. I think it's best to only add to add features where absolutely necessary.
Multi-file support can be handled with inputs plugin, (or when we merge it, glob like support could be done with parameterize plugin.)
https://github.com/Flexget/Flexget/blob/json_input/flexget/plugins/input/json.py

Thanks!

authors: gazpachoking metaMMA

repo: Flexget/Flexget


text:
JavaScript

JavaScript
User Story
As a boot camp student
I want the prework notes to be structured on a webpage
So that I can easily find and read the information
Acceptance Criteria
GIVEN a Prework Study Guide website
WHEN I view the study guide
THEN I can see the four topics I learned listed along with a suggestion on what I should study first

Added for loop and functions


text:
Oculus rift controller compatibility

Oculus rift controller are not compatible. There are some weird button mapping problems.

The main issue seems to be the Pointer not working properly, everything else seems fine

authors: FlorianJa Grosskopf

repo: FlorianJa/BeamLite-Unity


text:
{System.TypeInitializationException: The type initializer for 'AngleSharp.TextEncoding' threw an exception.

The error occurs when I try invoke DocumentBuilder on a web page
The message associated with the exception is:
'euc-jp' is not a supported encoding name.
Parameter name: name
Is there anything I can do to avoid the error.

Yes - use the latest version. The bug you describe should not occur in the latest version. (see #79)

repo: FlorianRappl/AngleSharp


text:
Chart - enable usage of left & right 'y' axis

Description
Possibly related to https://github.com/orgs/FlowFuse/projects/15?pane=issue&itemId=32022297
But specifically to enable both left and right 'y' axis to be utilized independently, with different scaling.
This would be helpful for many user applications where 2 values are being compared on the same timescale, but have different y scaling, For example I'm monitoring a energy diverter and on the left y axis record the amount of power being diverted (Unit = Watts, scale = 0 - 4000), whilst on the right y axis record the operating temperature of the diverter (Unit = degC, scale = 0 - 50).
Currently using just the left y axis for both which results in the temperature being a flat line due to the power scale.
Same situation arises when comparing temperature & windspeed on a chart, as a visual comparison because users can then assess 'feelslike' temp.
Below is a random example

Have you provided an initial effort estimate for this issue?
I am no FlowFuse team member

this would be great

That would be great for standard climagraphs /w temp on one side , humidity or precipitation on the other.

authors: Paul-Reed m-schaeffler pduw-et

repo: FlowFuse/node-red-dashboard


text:
[Vue] Support entire routes

/matches
/match/
/user/
/servers/
GetRecentMatches
maybe more

done


text:
Tactical Helmet battery config not working + mispell

I set the tactical helmet's battery to last for 99999 seconds, but it still drains at seemingly the normal pace.
Also, the tactical helmet seems to be mispelt as Tactical h elmet

Duplicate #58

authors: Autumnis FluffyFishGames

repo: FluffyFishGames/AdvancedCompany


text:
Unsats upon merging FBbt with Uberon

Merging FBbt with the taxon-neutral ontology Uberon still results in ~100 unsatisfiable classes. They are all caused by the fact that 7 FBbt classes are simultaneously part of both the central nervous system and the peripheral nervous system (something that Uberon does not allow, hence the unsatisfiability). Those classes are:

adult stomodeal nerve,
dorsal margin photoreceptor cell R7,
dorsal margin photoreceptor cell R8,
embryonic/larval frontal nerve,
embryonic/larval recurrent nerve,
larval esophageal nerve 1,
larval esophageal nerve 2.

adult stomodeal nerve
Explicitly classified as both nerve (which in FBbt, and in Uberon, is defined as being part of the PNS) and part of some adult hypocerebral ganglion (which is itself classified as part of the adult CNS).
The classification as a part of the hypocerebral ganglion seems wrong judging by the 1994 description from Rajashekhar and Singh (FBrf0080339), since the nerve is not entirely contained within the HCG. The relation should probably be innervates some 'adult corpus cardiacum' instead.
dorsal margin photoreceptor R7
(The problem with dorsal margin photoreceptor cell R8 is exactly the same.)
Classified as part of some dorsal margin ommatidium, which is ultimately (through both ommatidium and dorsal rim area) part of some retina, which is itself part of the adult PNS.
And also classified as part of some dorsal rim area optic column, which is ultimately a synaptic neuropil, which is part of some neuropil, which is itself part of the CNS.
The latter classification is probably wrong, because:

as a synaptic neuropil, the dorsal rim area optic column is expected to “consist largely of synapsing neuron projections”, i.e. be devoid of neuronal bodies, so it seems unlikely that photoreceptor cells would be entirely contained within it;
the parent term dorsal margin photoreceptor (under which 'dorsal margin photoreceptor cell R7' is automatically classified) is said to be 'sending synaptic output to region' some 'dorsal rim area optic column', which is more consistent with the idea of a receptor cell that is located in the retina and that projects to an optic column.

Suggested fix here is to simply remove the 'part of' some 'dorsal rim area optic column' classification. (No need to replace it with 'sends synaptic output to region' some 'dorsal rim area optic column', since that relation is inherited from 'dorsal margin photoreceptor'.)
embryonic/larval frontal nerve
(The problem with 'embryonic/larval recurrent nerve', 'larval esophageal nerve 1', and 'larval esophageal nerve 2' is the same.)
Ultimately classified as a nerve and therefore as part of the PNS.
And also directly classified as part of some embryonic/larval stomatogastric nervous system (SNS), which is part of the embryonic/larval CNS.
To solve this particular contradiction, I’m inclined to drop the relationship with the stomatogastric nervous system. All those nerves are already said to be innervating one or several of the ganglions that make up the embryonic/larval SNS (which are themselves part of that system), so they would still be (indirectly) linked to the SNS without being “part” of it.

Following Uberon’s last release there are also 845 new unsats that are caused by the fact that insect dorsal ectoderm derivative in Uberon is classified as a multi-cellular anatomical structure, whereas our our dorsal ectoderm derivative is classified only as an anatomical entity.
I think our classification is correct (a “dorsal ectoderm derivative” can be a single cell, such as a histoblast, or even an acellular structure, such as an apodeme), so that is something that will need fixing on the Uberon side.


text:
NPC Issue

I have an issue where OPPED players can use the NPC GUI but de-OPPED players can't.

What permissions do you have set?

There are no permissions for it I believe, I believe it's an issue  with world guard. I'm using a different plugin for protection and it works fine! Issue with world guard or Quests?

Impossible to know without knowing which permissions are set. If this is still an issue, please open a new ticket with more information.

repo: FlyingPikachu/Quests


text:
🛑 Autogestión Clientes is down

In 4831f4f, Autogestión Clientes (https://sacautogestion.focasoftware.com/index) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Autogestión Clientes is back up in 5096dbb.

repo: Foca-Software/status


text:
🛑 Backend Mercado Pago Foca is down

In 830a399, Backend Mercado Pago Foca (http://mp.focasoftware.com/webservices/testFront) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Backend Mercado Pago Foca is back up in d2b6482.


text:
Use default 2204 image with included virtual MIDI drivers

For newer Ubuntu versions, it's no-longer required to use this trick to pin your image to GCP.

@lozjackson sorry for the ping, just wanted to see if this new Ubuntu series of images worked for you

@pete-woods thanks

authors: lozjackson pete-woods

repo: Focusrite-Novation/node-midi


text:
Groups are not available anymore since update 2.7.1

Describe the bug
I cannot trigger groups anymore. E.g. a toggle command results with Error: Philips Hue: 3, resource, /groups/192, not available
The light nodes however still work as before.
Flow to Reproduce
[
    {
        "id": "b98f04a8.011838",
        "type": "tab",
        "label": "Test",
        "disabled": false,
        "info": ""
    },
    {
        "id": "c03c5f03.c0fce",
        "type": "ccu-value",
        "z": "b98f04a8.011838",
        "name": "1 kurz",
        "iface": "HmIP-RF",
        "channel": "000198A9913C72:2 Taster Arbeitszimmer:2",
        "datapoint": "PRESS_SHORT",
        "mode": "",
        "start": true,
        "change": true,
        "cache": false,
        "queue": false,
        "on": 0,
        "onType": "undefined",
        "ramp": 0,
        "rampType": "undefined",
        "working": false,
        "ccuConfig": "ee924885.ee4ac8",
        "topic": "${CCU}/${Interface}/${channel}/${datapoint}",
        "x": 150,
        "y": 120,
        "wires": [
            [
                "1d1af0ca.36140f"
            ]
        ]
    },
    {
        "id": "1d1af0ca.36140f",
        "type": "function",
        "z": "b98f04a8.011838",
        "name": "Licht an/aus",
        "func": "msg.payload.toggle = true\n\nreturn msg;",
        "outputs": 1,
        "noerr": 0,
        "x": 1350,
        "y": 120,
        "wires": [
            [
                "101c4c2a.c95794"
            ]
        ]
    },
    {
        "id": "335bc3dd.c6a93c",
        "type": "ccu-value",
        "z": "b98f04a8.011838",
        "name": "2 kurz",
        "iface": "HmIP-RF",
        "channel": "000198A9913C72:1 Taster Arbeitszimmer:1",
        "datapoint": "PRESS_SHORT",
        "mode": "",
        "start": true,
        "change": false,
        "cache": false,
        "queue": true,
        "on": 0,
        "onType": "undefined",
        "ramp": 0,
        "rampType": "undefined",
        "working": false,
        "ccuConfig": "ee924885.ee4ac8",
        "topic": "${CCU}/${Interface}/${channel}/${datapoint}",
        "x": 150,
        "y": 181,
        "wires": [
            [
                "788dd8e2.b5a0c8"
            ]
        ]
    },
    {
        "id": "b1ad8740.279878",
        "type": "ccu-value",
        "z": "b98f04a8.011838",
        "name": "1 lang",
        "iface": "HmIP-RF",
        "channel": "000198A9913C72:2 Taster Arbeitszimmer:2",
        "datapoint": "PRESS_LONG",
        "mode": "",
        "start": true,
        "change": true,
        "cache": false,
        "queue": false,
        "on": 0,
        "onType": "undefined",
        "ramp": 0,
        "rampType": "undefined",
        "working": false,
        "ccuConfig": "ee924885.ee4ac8",
        "topic": "${CCU}/${Interface}/${channel}/${datapoint}",
        "x": 150,
        "y": 240,
        "wires": [
            [
                "b30fccfb.a08ef"
            ]
        ]
    },
    {
        "id": "606cb9c5.d50c28",
        "type": "function",
        "z": "b98f04a8.011838",
        "name": "Helligkeit +",
        "func": "var trigger = flow.get('T01_1l');\n\nif (trigger == 1) {\n    var br = msg.payload.brightness;\n\n    if (br == 100) {\n        msg = null;\n    } else if (br >= 92) {\n        br = 100;\n        msg.payload = {\n            \"brightness\": br\n        };\n    } else {\n       msg.payload = {\n            \"incrementBrightness\": 10\n        };\n    }\n    flow.set('T01_1l', 0);\n    return msg;\n}",
        "outputs": 1,
        "noerr": 0,
        "x": 1350,
        "y": 240,
        "wires": [
            [
                "101c4c2a.c95794"
            ]
        ]
    },
    {
        "id": "bc9b9eda.f8f61",
        "type": "ccu-value",
        "z": "b98f04a8.011838",
        "name": "2 lang",
        "iface": "HmIP-RF",
        "channel": "000198A9913C72:1 Taster Arbeitszimmer:1",
        "datapoint": "PRESS_LONG",
        "mode": "",
        "start": true,
        "change": true,
        "cache": false,
        "queue": false,
        "on": 0,
        "onType": "undefined",
        "ramp": 0,
        "rampType": "undefined",
        "working": false,
        "ccuConfig": "ee924885.ee4ac8",
        "topic": "${CCU}/${Interface}/${channel}/${datapoint}",
        "x": 150,
        "y": 300,
        "wires": [
            [
                "ba9507ae.8715d8"
            ]
        ]
    },
    {
        "id": "a0431cf9.c8684",
        "type": "function",
        "z": "b98f04a8.011838",
        "name": "Helligkeit -",
        "func": "var trigger = flow.get('T01_2l');\n\nif (trigger == 1) {\n    var br = msg.payload.brightness;\n\n    if (br == 1) {\n        msg = null;\n    } else if (br <= 6) {\n        br = 1;\n        msg.payload = {\n            \"brightness\": br\n        };\n    } else {\n       msg.payload = {\n            \"decrementBrightness\": 10\n        };\n    }\n    flow.set('T01_2l', 0);\n    return msg;\n}",
        "outputs": 1,
        "noerr": 0,
        "x": 1350,
        "y": 300,
        "wires": [
            [
                "101c4c2a.c95794"
            ]
        ]
    },
    {
        "id": "a4b3eb71.321a38",
        "type": "function",
        "z": "b98f04a8.011838",
        "name": "Lichtfarbe",
        "func": "var trigger = flow.get('T01_2k');\n\nif (trigger == 1) {\n    var ct = msg.payload;\n\n    if (ct.colorTemp > 480) {\n        msg.payload = {\n            \"colorTemp\": 153\n        };\n    } else {\n        msg.payload = {\n            \"incrementColorTemp\": 60\n        };\n    }\n    flow.set('T01_2k', 0)\n    return msg;\n}",
        "outputs": 1,
        "noerr": 0,
        "x": 1340,
        "y": 181,
        "wires": [
            [
                "101c4c2a.c95794"
            ]
        ]
    },
    {
        "id": "101c4c2a.c95794",
        "type": "hue-group",
        "z": "b98f04a8.011838",
        "name": "Arbeitszimmer",
        "bridge": "1132a929.428347",
        "groupid": "3",
        "colornamer": true,
        "skipevents": false,
        "x": 1720,
        "y": 221,
        "wires": [
            []
        ]
    },
    {
        "id": "b30fccfb.a08ef",
        "type": "function",
        "z": "b98f04a8.011838",
        "name": "Trigger",
        "func": "flow.set('T01_1l',1);\nmsg.payload = {\n            \"status\": true\n        };\nreturn msg;",
        "outputs": 1,
        "noerr": 0,
        "x": 480,
        "y": 240,
        "wires": [
            [
                "b0bed0e5.9c1ea"
            ]
        ]
    },
    {
        "id": "ba9507ae.8715d8",
        "type": "function",
        "z": "b98f04a8.011838",
        "name": "Trigger",
        "func": "flow.set('T01_2l',1);\nmsg.payload = {\n            \"status\": true\n        };\nreturn msg;",
        "outputs": 1,
        "noerr": 0,
        "x": 480,
        "y": 300,
        "wires": [
            [
                "b0bed0e5.9c1ea"
            ]
        ]
    },
    {
        "id": "788dd8e2.b5a0c8",
        "type": "function",
        "z": "b98f04a8.011838",
        "name": "Trigger",
        "func": "flow.set('T01_2k',1);\nmsg.payload = {\n            \"status\": true\n        };\nreturn msg;",
        "outputs": 1,
        "noerr": 0,
        "x": 480,
        "y": 180,
        "wires": [
            [
                "b0bed0e5.9c1ea"
            ]
        ]
    },
    {
        "id": "b0bed0e5.9c1ea",
        "type": "hue-group",
        "z": "b98f04a8.011838",
        "name": "Arbeitszimmer",
        "bridge": "1132a929.428347",
        "groupid": "3",
        "colornamer": true,
        "skipevents": false,
        "x": 820,
        "y": 240,
        "wires": [
            [
                "a4b3eb71.321a38",
                "606cb9c5.d50c28",
                "a0431cf9.c8684"
            ]
        ]
    },
    {
        "id": "ee924885.ee4ac8",
        "type": "ccu-connection",
        "z": "",
        "name": "CCU3",
        "host": "192.168.37.2",
        "regaEnabled": true,
        "bcrfEnabled": true,
        "iprfEnabled": true,
        "virtEnabled": true,
        "bcwiEnabled": false,
        "cuxdEnabled": true,
        "regaPoll": true,
        "regaInterval": "30",
        "rpcPingTimeout": "60",
        "rpcInitAddress": "192.168.37.1",
        "rpcServerHost": "0.0.0.0",
        "rpcBinPort": "2069",
        "rpcXmlPort": "2070",
        "queueTimeout": "5000",
        "queuePause": "250",
        "contextStore": ""
    },
    {
        "id": "1132a929.428347",
        "type": "hue-bridge",
        "z": "",
        "name": "Hue Bridge",
        "bridge": "192.168.37.3",
        "key": "something here",
        "interval": "3000",
        "disableupdates": false
    }
]

Expected behavior
The groups should be able to be triggered again like in former versions < v. 2.7.1
Please complete the following information:

NodeRED version: 1.06
NodeJS version: ?
Device running NodeRED: Linux Debian @ Intel(R) Atom(TM) x5-Z8350 CPU

Hi,
I have the same problem.
And if I try to switch a group, some other lights will turn on.
Yesterday evening after the update, I tried to switch on a group of lights in the living room, the lights in the bedroom turned on.
Unfortunately my wife was still in bed. :-(

Same here, messages to groups seem to control other lights after the update.

Same here, controlling lights on groups are affecting all lights.

It might be related to this change? https://github.com/Foddy/node-red-contrib-huemagic/commit/77db69fd0df47dde049af475cf27e25a5ba23a58#diff-06dfc8188f358fc40c7a56cb8874e79bR86-R87

Sorry. This was a pretty weird error… However, the problem no longer seems to occur with the latest version (2.7.2)

Thanks for the quick fix!

Wow! That's a awesome quick response-time!
Enjoy your coffee/beer/kebap/whatever. You`ve earned it!!
Thanks!

I'm up to date with huemagic 2.7.2, however still see this problem on one of my bridges. The second bridge is reporting groups just fine. Can this issue be re-opened? Or do i need to submit a new issue for this?

authors: Foddy FreeTimeCoder82 Phalynx Spampunk aav7fl hurenkam jnbht stieler-it

repo: Foddy/node-red-contrib-huemagic


text:
🛑 Uptime Kuma is down

In ebb4513, Uptime Kuma (https://status.forgoodeyesonly.eu) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Uptime Kuma is back up in 6c47cec after 3 hours, 5 minutes.

repo: ForGoodEyesOnly/status


text:
Error in test case "fclaw_global_new default options"

When configuring the latest develop-3d branch with --enable-debug on Linux I run into the following error when calling make check-TESTS
FAIL: src/forestclaw.TEST --test-case="fclaw_global_new default options"

The corresponding error message is
 ../forestclaw/src/fclaw_global.h.TEST.cpp:62: ERROR: CHECK( glob->user == nullptr ) is NOT correct!
  values: CHECK( 0xffffffffffffffff == nullptr )

glob->user isn't being initialized in fclaw_global_new() 🤦. I'll have a fix soon.

Everything runs through cleanly now, thanks!

authors: hannesbrandt scottaiton

repo: ForestClaw/forestclaw


text:
CompoundTags have no Equals override

When comparing compound tags the bar for equality is set extremely low. Two compound objects are equal if they have the same type (guaranteed) and their names are the same.
This is because the CompoundTag class does not override the Tag.Equals method leading to this bizarre behaviour. A very simple check is this:
using SharpNBT.SNBT;
Console.WriteLine(StringNbt.Parse("{value:385}") == StringNbt.Parse("{data:[1,2,3,4]}"));

This will pass even though the two compounds aren't remotely the same.

Currently compound tags only compare the name of the tag to determine equality, and do not check contents. The given example results in two tags where neither has a name, therefore are considered "equal" using that very generic comparison. While it would be somewhat trivial to implement, comparing dictionaries (i.e. compound tags) for equality is not going to be efficient (deep nesting, binary data, etc), and rarely ever useful or meaningful beyond these simple examples.
While I am not outright opposed to implementing it, I am leaning strongly in favor of not doing so, as Linq and/or existing extension methods (Union, Intersect, etc) available to the IDictionary interface already exist to solve this problem, if a deep comparison is actually needed. Otherwise this can result in a foot-gun where someone assumes that calling == on two tags (or even abstract Tag instances)  is going to be a relatively cheap operation, not realizing that this could severely degrade performance, as real-world use of compound tags often contain tens of even hundreds of MB of data. This is likely why the .NET runtime's dictionary implementation likewise does not include this interface, which the compound tag replicates for the sake of a familiar API surface.
I am open-minded to arguments to the contrary, but it should be noted that comparing table/dictionary types for equality is a "code smell" in pretty much any language, including C#. Typically you would want to be checking for known/expected keys, and handling them as-needed to validate the data.
I will consider a compromised "middle-ground" solution, where compound tags compare equality of their names, number of items, and perhaps check if all child key names are the same, but a full recursive comparison of child-types and their equality is going to require some powerful persuasion.

It's more a case of "fixing" an unintuitive == implementation
I do agree with this. The default equality for compound tags should only be true when the objects are the same reference.

As it goes for code I think the best implementation would be removing the IEquality interface from Tag and creating another abstract EqualityTag class to reintroduce the old mechanic

I intended to address this part of your comment in my previous reply, but yes, I agree this sensible and more in line with language conventions. The only part of I dislike about this approach is that it loses the ability to check for equality of tags without first casting or pattern-matching a Tag into its concrete type. Realistically I am uncertain how often this is actually needed/used, but it could potentially be a breaking change to the existing API. For now I will most likely opt for fixing the behavior, obsoleting equality of list/array/compound types to set off compiler warnings, but postpone the actual removal of the interface for a future major version bump.

I think the only issue here is that you would need to cast to EqualityTag instead of Tag, no?

@Fisch37 Assuming each tag shared a common interface that implemented IEquality, then technically yes. Either way it would still require casting a Tag instance to a more derived type in order to perform the operation. This is obviously not a difficult task, and pretty much required to do anything useful with a Tag anyways, but I feel is a bit less ergonomic if simply scanning through a collection in search of a particular value.
It also may bring up some new issues with what is considered "equal" and the rules for type coercion. For example, assume we have three EqualityTag instances with the same name. Concretely they are an IntTag, a LongTag and a FloatTag, with the values 1, 1L, and 1.0f respectfully. Should these be considered equal? I personally would say "no", and enforce they should be of the same tag type, but it could be argued that they are depending on another's perspective and/or expectations. Comparing an int, long, and float is a valid comparison in C# (with no explicit type conversion), and the following is valid:
long a = 1L;
int b = 1;
float c = 1.0f;
bool IsTrue = (a == b && b == c);

Realistically, finding a tag with a specific value is not commonly needed, and the typical use-case is finding a tag with a certain name then doing something with its value, so this "sacrifice" will be of little consequence.


text:
Experimental GRID layout

Try making grid layout using experimental CSS grid instead of flexbox
more: http://gridbyexample.com/
support: http://caniuse.com/#feat=css-grid

flexbox still wins for now, CSS grid is not even supported without custom browser config