Taking over 60 seconds to "Setup" After restart

Describe the bug
After a restart of Home Assistant, I will get a notification that the component took too long to initialize. Component/Plugin still works as it should.
Notification is as follows:
Setup of platform alexa_media is taking longer than 60 seconds. Startup will proceed without waiting any longer.
To Reproduce
Restart Home Assistant via Server Control
Expected behavior
Either to not run "Setup" on every restart of homebridge, or for the setup to not take over 60 seconds.
System details

Home-assistant (version):  0.98.5
Hassio (Yes/No): Yes
alexa_media version: 2.1.2
alexapy version: 1.1.2

Logs
2019-09-10 14:18:13 DEBUG (MainThread) [custom_components.alexa_media] Testing login status: {'login_successful': True}
2019-09-10 14:18:13 DEBUG (MainThread) [custom_components.alexa_media] Setting up Alexa devices for w********1@g*******m
2019-09-10 14:18:13 DEBUG (MainThread) [custom_components.alexa_media] w********1@g*******m: Websocket created: <alexapy.alexawebsocket.WebsocketEchoClient object at 0x7f26fedf73d0>
~
2019-09-10 14:18:14 DEBUG (MainThread) [custom_components.alexa_media] w********1@g*******m: Websocket succesfully connected
~
2019-09-10 14:18:15 DEBUG (MainThread) [custom_components.alexa_media] w********1@g*******m: Found 8 devices, 1 bluetooth
2019-09-10 14:18:15 DEBUG (MainThread) [custom_components.alexa_media] Locale en-us found for G************QQ9
2019-09-10 14:18:15 DEBUG (MainThread) [custom_components.alexa_media] DND False found for G************QQ9
2019-09-10 14:18:15 DEBUG (MainThread) [custom_components.alexa_media] Locale en-us found for G************KVQ
2019-09-10 14:18:15 DEBUG (MainThread) [custom_components.alexa_media] DND False found for G************KVQ
2019-09-10 14:18:15 DEBUG (MainThread) [custom_components.alexa_media] w********1@g*******m: Existing: [] New: ['Big Echo', 'Echo Dot Bedroom']; Filtered out by not being in include: [] or in exclude: ["******'s Alexa Apps", 'Echo Dot Living Room', 'Living Room', 'Everywhere', 'This Device', "******'s Alexa Apps"]
2019-09-10 14:18:15 INFO (SyncWorker_15) [homeassistant.loader] Loaded alarm_control_panel from homeassistant.components.alarm_control_panel
2019-09-10 14:18:15 INFO (MainThread) [homeassistant.setup] Setting up alarm_control_panel
2019-09-10 14:18:15 INFO (MainThread) [homeassistant.setup] Setup of domain alarm_control_panel took 0.0 seconds.
2019-09-10 14:18:16 DEBUG (MainThread) [custom_components.alexa_media] w********1@g*******m: Updated last_called: {'serialNumber': 'G************QQ9', 'timestamp':<PHONE_NUMBER>666}
2019-09-10 14:18:16 DEBUG (MainThread) [custom_components.alexa_media] w********1@g*******m: last_called changed:  to {'serialNumber': 'G************QQ9', 'timestamp':<PHONE_NUMBER>666}
2019-09-10 14:18:16 INFO (MainThread) [homeassistant.setup] Setup of domain alexa_media took 4.7 seconds.
2019-09-10 14:18:16 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.alexa_media
2019-09-10 14:18:16 INFO (MainThread) [homeassistant.components.notify] Setting up notify.alexa_media
2019-09-10 14:18:16 DEBUG (MainThread) [custom_components.alexa_media.helpers] async_get_service: Trying with limit 5 delay 2 catch_exceptions True
2019-09-10 14:18:16 DEBUG (MainThread) [custom_components.alexa_media.notify] w********1@g*******m: Media player G************QQ9 not loaded yet; delaying load
2019-09-10 14:18:16 DEBUG (MainThread) [custom_components.alexa_media.helpers] async_get_service: Try: 1/5 result: False
2019-09-10 14:18:16 INFO (MainThread) [homeassistant.components.switch] Setting up switch.alexa_media
2019-09-10 14:18:16 INFO (MainThread) [homeassistant.components.alarm_control_panel] Setting up alarm_control_panel.alexa_media
2019-09-10 14:18:16 DEBUG (MainThread) [custom_components.alexa_media.helpers] async_setup_platform: Trying with limit 5 delay 2 catch_exceptions True
2019-09-10 14:18:16 DEBUG (MainThread) [custom_components.alexa_media.helpers] async_setup_platform: Trying with limit 5 delay 2 catch_exceptions True
2019-09-10 14:18:16 DEBUG (MainThread) [custom_components.alexa_media.switch] w********1@g*******m: Loading switches
2019-09-10 14:18:16 DEBUG (MainThread) [custom_components.alexa_media.switch] w********1@g*******m: Media player G************QQ9 not loaded yet; delaying load
2019-09-10 14:18:16 DEBUG (MainThread) [custom_components.alexa_media.helpers] async_setup_platform: Try: 1/5 result: False
2019-09-10 14:18:16 DEBUG (MainThread) [custom_components.alexa_media.helpers] async_setup_platform: Trying with limit 5 delay 2 catch_exceptions True
2019-09-10 14:18:16 DEBUG (MainThread) [custom_components.alexa_media.media_player] w********1@g*******m: Refreshing Big Echo
2019-09-10 14:18:16 DEBUG (MainThread) [custom_components.alexa_media.media_player] Big Echo: Last_called check: self: G************QQ9 reported:
2019-09-10 14:18:16 DEBUG (MainThread) [custom_components.alexa_media.alarm_control_panel] w********1@g*******m: No Alexa Guard entity found
2019-09-10 14:18:16 DEBUG (MainThread) [custom_components.alexa_media.alarm_control_panel] w********1@g*******m: Skipping creation of uninitialized device: <Entity Alexa Guard: None>
2019-09-10 14:18:16 DEBUG (MainThread) [custom_components.alexa_media.helpers] async_setup_platform: Try: 1/5 result: False
2019-09-10 14:18:16 DEBUG (MainThread) [custom_components.alexa_media.media_player] w********1@g*******m: Refreshing Echo Dot Bedroom
2019-09-10 14:18:16 DEBUG (MainThread) [custom_components.alexa_media.media_player] Echo Dot Bedroom: Last_called check: self: G************KVQ reported:
2019-09-10 14:18:16 DEBUG (MainThread) [custom_components.alexa_media.helpers] w********1@g*******m: Adding [<Entity Big Echo: standby>, <Entity Echo Dot Bedroom: standby>]
2019-09-10 14:18:16 DEBUG (MainThread) [custom_components.alexa_media.helpers] async_setup_platform: Try: 1/5 result: True
2019-09-10 14:18:20 DEBUG (MainThread) [custom_components.alexa_media.helpers] async_get_service: Try: 2/5 result: <custom_components.alexa_media.notify.AlexaNotificationService object at 0x7f26f99bff10>
2019-09-10 14:18:20 DEBUG (MainThread) [custom_components.alexa_media.switch] w********1@g*******m: Loading switches
2019-09-10 14:18:20 DEBUG (MainThread) [custom_components.alexa_media.switch] w********1@g*******m: Found G************QQ9 dnd switch with status: False
2019-09-10 14:18:20 DEBUG (MainThread) [custom_components.alexa_media.switch] w********1@g*******m: Found G************QQ9 shuffle switch with status: None
2019-09-10 14:18:20 DEBUG (MainThread) [custom_components.alexa_media.switch] w********1@g*******m: Found G************QQ9 repeat switch with status: None
2019-09-10 14:18:20 DEBUG (MainThread) [custom_components.alexa_media.switch] w********1@g*******m: Found G************KVQ dnd switch with status: False
2019-09-10 14:18:20 DEBUG (MainThread) [custom_components.alexa_media.switch] w********1@g*******m: Found G************KVQ shuffle switch with status: None
2019-09-10 14:18:20 DEBUG (MainThread) [custom_components.alexa_media.switch] w********1@g*******m: Found G************KVQ repeat switch with status: None
2019-09-10 14:18:20 DEBUG (MainThread) [custom_components.alexa_media.helpers] w********1@g*******m: Adding [<Entity Big Echo do not disturb switch: off>, <Entity Big Echo shuffle switch: off>, <Entity Big Echo repeat switch: off>, <Entity Echo Dot Bedroom do not disturb switch: off>, <Entity Echo Dot Bedroom shuffle switch: off>, <Entity Echo Dot Bedroom repeat switch: off>]
2019-09-10 14:18:20 DEBUG (MainThread) [custom_components.alexa_media.helpers] async_setup_platform: Try: 2/5 result: True
2019-09-10 14:18:20 DEBUG (MainThread) [custom_components.alexa_media.alarm_control_panel] w********1@g*******m: No Alexa Guard entity found
2019-09-10 14:18:20 DEBUG (MainThread) [custom_components.alexa_media.alarm_control_panel] w********1@g*******m: Skipping creation of uninitialized device: <Entity Alexa Guard: None>
2019-09-10 14:18:20 DEBUG (MainThread) [custom_components.alexa_media.helpers] async_setup_platform: Try: 2/5 result: False
2019-09-10 14:18:26 WARNING (MainThread) [homeassistant.components.alarm_control_panel] Setup of platform alexa_media is taking over 10 seconds.
2019-09-10 14:18:28 DEBUG (MainThread) [custom_components.alexa_media.alarm_control_panel] w********1@g*******m: No Alexa Guard entity found
2019-09-10 14:18:28 DEBUG (MainThread) [custom_components.alexa_media.alarm_control_panel] w********1@g*******m: Skipping creation of uninitialized device: <Entity Alexa Guard: None>
2019-09-10 14:18:28 DEBUG (MainThread) [custom_components.alexa_media.helpers] async_setup_platform: Try: 3/5 result: False
2019-09-10 14:18:31 DEBUG (MainThread) [custom_components.alexa_media] w********1@g*******m: Received websocket command: PUSH_EQUALIZER_STATE_CHANGE : {'destinationUserId': 'A**********AIM', 'bass': 0, 'treble': 0, 'dopplerId': {'deviceSerialNumber': 'G************KVQ', 'deviceType': '************'}, 'midrange': 0}
2019-09-10 14:18:45 DEBUG (MainThread) [custom_components.alexa_media.alarm_control_panel] w********1@g*******m: No Alexa Guard entity found
2019-09-10 14:18:45 DEBUG (MainThread) [custom_components.alexa_media.alarm_control_panel] w********1@g*******m: Skipping creation of uninitialized device: <Entity Alexa Guard: None>
2019-09-10 14:18:45 DEBUG (MainThread) [custom_components.alexa_media.helpers] async_setup_platform: Try: 4/5 result: False
2019-09-10 14:19:16 ERROR (MainThread) [homeassistant.components.alarm_control_panel] Setup of platform alexa_media is taking longer than 60 seconds. Startup will proceed without waiting any longer.
2019-09-10 14:19:16 INFO (MainThread) [homeassistant.bootstrap] Home Assistant initialized in 65.79s
2019-09-10 14:19:16 INFO (MainThread) [homeassistant.core] Starting Home Assistant
~
2019-09-10 14:19:17 DEBUG (MainThread) [custom_components.alexa_media.media_player] w********1@g*******m: Refreshing Echo Dot Bedroom
2019-09-10 14:19:17 DEBUG (MainThread) [custom_components.alexa_media.media_player] Echo Dot Bedroom: Last_called check: self: G************KVQ reported: G************QQ9
2019-09-10 14:19:17 DEBUG (MainThread) [custom_components.alexa_media.media_player] w********1@g*******m: Refreshing Big Echo
2019-09-10 14:19:17 DEBUG (MainThread) [custom_components.alexa_media.media_player] Big Echo: Last_called check: self: G************QQ9 reported: G************QQ9
2019-09-10 14:19:17 DEBUG (MainThread) [custom_components.alexa_media.media_player] Disabling polling for Big Echo
2019-09-10 14:19:17 DEBUG (MainThread) [custom_components.alexa_media.media_player] Disabling polling for Echo Dot Bedroom
2019-09-10 14:19:17 DEBUG (MainThread) [custom_components.alexa_media.alarm_control_panel] w********1@g*******m: No Alexa Guard entity found
2019-09-10 14:19:17 DEBUG (MainThread) [custom_components.alexa_media.alarm_control_panel] w********1@g*******m: Skipping creation of uninitialized device: <Entity Alexa Guard: None>
2019-09-10 14:19:17 DEBUG (MainThread) [custom_components.alexa_media.helpers] async_setup_platform: Try: 5/5 result: False

Additional context
Plugin works fine after restart of services, however it just takes forever for home assistant to restart.
Originally set up this plugin via alexpy pip installation/manual install. Removed all of that and installed via HACS.
Have restarted HASS Multiple times. As stated, it works once home-assistant is up, it just delays start.

Thanks that's a bug. It shouldn't be retrying the alarm control panel in this situation since that's not an error. I'll add it to the queue to fix.

Referenced PR should fix this. You can just replace the file.

I replaced the content of helpers.py and am still seeing an issue with setup time

2019-09-16 10:03:28 ERROR (MainThread) [homeassistant.components.alarm_control_panel] Setup of platform alexa_media is taking longer than 60 seconds. Startup will proceed without waiting any longer.

The issue appears to be related to the alarm_control_panel component of Alexa Media

2019-09-16 10:03:28 INFO (MainThread) [homeassistant.setup] Setup of domain alarm_control_panel took 68.2 seconds.

 If you still see it I'd need logs.

5243d547122e85fa1b5b99b597d1bd05  helpers.py
I have removed the pycache directory in custom_components/alexa_media. Let me know what you need from logs and I'll get them here. Thank you for your hard work!

As a second data point, I made this update and it did fix the startup issue.

Stop home-assistant
Update helpers.py
Remove pycache
Start back up

If it matters, I have alexa_media_player being managed by HACS

No dice here.

Stop hass
Update helpers.py
Remove custom_components/alexa_media/__pycache__
Remove custom_components/__pycache__ (for good measure)
Start hass

fwiw I did not need to touch my __pycache__, and I believe Python should be smart enough to work this out for itself (based on ctime).
For anyone arriving here now looking for a fix, this should set you straight:
curl -O /path/to/hass/config/custom_components/alexa_media/helpers.py https://github.com/custom-components/alexa_media_player/blob/2cf63a3c3307798bad1f28076768c2f37ba6433b/custom_components/alexa_media/helpers.py

Change the url above to https://raw.githubusercontent.com/custom-components/alexa_media_player/2cf63a3c3307798bad1f28076768c2f37ba6433b/custom_components/alexa_media/helpers.py 😃

Thanks @aneisch, clipboard error!

Can confirm the updated file fixes the issue. Thank you.

For anyone else who stumbles here. I still had the "issue" but it turns out my configuration was wrong. I had both:
alexa_media:
  accounts:
    - email: !secret amazon_email
      password: !secret amazon_pass
      url: "amazon.com"

AND
alarm_control_panel:
  - platform: alexa_media

in my config. If you have alexa_media: it will import all of the supported platforms.


Token not authenticating on online server but working on localhost

Hello there, this is not my first time of using slim-jwt-auth, I have used the version 2.3 before on a project and it worked well. Now the version 3 is not working on the online server, I am receiving a status code of 401 Unauthorized when on an online server but working very well on localhost. I am hosting the project on a subdomain. please, what could be the problem?

I am receiving a status code of 401 Unauthorized when on an online server

My guess is live PHP process in live server does not receive the Authorization header.
Look for differences between the dev and production server.
For example if live server is using FastCGI then by default Apache does not pass credentials to FastCGI process. You need to specifically tell FastCGI to pass the Authorization header with config:
FastCgiExternalServer /usr/lib/cgi-bin/php7-fcgi -host <IP_ADDRESS>:9000 -pass-header Authorization

If live uses vanilla Apache make sure the required RewriteRule exists in .htaccess file.
RewriteRule .* - [env=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

Yes, thank you for your reply. I have contacted the hosting company and they have resolved the issue. It was from their end.

Great!

For me work only when I changed setting 'hesder' into 'X-Token'


Allow different uploaders

Currently, KnowledgeBase only supports Carrierwave. We should allow for other uploaders as well, like the awesome refile!

:+1:


Build host connected and valid Apple ID in Fastlane, but Apple ID shows as None and Team dropdown box is empty

I'm connected to my Mac build host, which I've used before for building this project. I have the same Apple ID I've used to build the project as well. But after updating to Visual Studio 15.7.4, when I go to iOS Project Properties -> iOS Bundle Signing and select Automatic Provisioning, the Apple ID label text is "None" and the Team dropdown box is empty. What can I do to troubleshoot this?

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

ID: 5ccadd93-fcc8-6a15-9670-d5af7ee7f6f8
Version Independent ID: 188007d3-cf20-97ba-137f-64ff25a88e7c
Content: Automatic Provisioning for Xamarin.iOS - Xamarin
Content Source: docs/ios/get-started/installation/device-provisioning/automatic-provisioning.md
Product: xamarin
GitHub Login: @asb3993
Microsoft Alias: amburns

Hi @zanoo, try this: in Visual Studio 2017, select Tools > Options. Then, in the Options window, select Xamarin > Apple Accounts (docs about Xamarin's tools for Apple account management). Make sure that your Apple account is still listed here; if not, add it. Then, go back to the iOS Bundle Signing tab and see if it's available there. If this doesn't work, please feel free to post on Developer Community for support. Thank you!


Pass title info to versionist

Title info can be passed along (--title, -t).
Change-type: minor
Depends on: https://github.com/product-os/versionist/pull/208

LGTM, but converted to draft, as PR it depends on hasn't landed yet

@balena-ci rebase

@balena-ci rebase

@balena-ci I self-certify!


Invalid note type during convert?

Hello, I would like to ask about several matters that bugs me being driven away from the actual "sentaku".
1-tile away slides

I know this is a convert, what I want to ask is "Isn't a very short slide notes are rather impossible in general?". iirc the original one had around 2~8 ticks.
Break Slide and Break Hold
Is this specific for sentakki itself?
Slide "animation" delay
As what I know that post-tap and the slide animation starts 1 beat interval, I'll assume the interval difference in here is not by bpm?
Also the plan of Slide note will be always attached to Star-skinned Tap as one entity or you could allow the possibility of being UTAGE memes?
I think thats the thing I would like to ask, thanks!

1 tile away slides: I remember seeing something of the sort before in the official game, however I do agree that it is quite unfun seeing as half of the time the end node is immediately triggered.
Break Slide and Break Hold: Slides don't exactly have a break modifier, it is only the tap portion that does, but the color is transferred to the body anyways. Break holds are indeed a sentakki specific addition.
Slide "animation" delay: They are affected by bpm as set by the mapper. Looking at the code more closely, there may be a slight measuring error causing it to be measured in half-beats. So the default delay in converted maps is half a beat, with it not being present if the slide is wayy too short (hardly happens)

1 tile away slides: I remember seeing something of the sort before in the official game, however I do agree that it is quite unfun seeing as half of the time the end node is immediately triggered.

Hmmm, is this something like Believe the Rainbow? I tried to look on it and it does have at least 2-tiles to operate the stars. If it's utage hmmmmm... should be a different matter of course.

Break Slide and Break Hold: Slides don't exactly have a break modifier, it is only the tap portion that does, but the color is transferred to the body anyways. Break holds are indeed a sentakki specific addition.

I see. I wonder how confusing the Both Break Slide when it happen to exist (since break color takes precedence over note skin, but don't have precedence over the

Slide "animation" delay: They are affected by bpm as set by the mapper. Looking at the code more closely, there may be a slight measuring error causing it to be measured in half-beats. So the default delay in converted maps is half a beat, with it not being present if the slide is wayy too short (hardly happens)

I guess this is rather unintended feature right?

I see. I wonder how confusing the Both Break Slide when it happen to exist
Break color currently have top priority over Twins

I guess this is rather unintended feature right?
I think there was a reason for this at the time, maybe because the delay was too long to feel natural

Feel free to visit the discord server for easier discussion on this matter.

I see, I guess I can consider this as done for now, may visit later on for possible interests -w-) :thumbsup:

Testing the star delay, it seems that having it default to a full beat causes most stars to not exhibit any delays. And I can recall encountering this issue in the past.
osu std sliders aren't long enough to allow for the star to be delayed a full beat, causing the delay to be cancelled. Forcing the delay would be arguably worse due to the star moving from one end to the other so fast that the star flies over to hishi.


Move cli into feast package

Currently pip install feast does not include the cli, which is outside of the feast package. Moving it into the feast package and updating the entrypoint for the feast command.

/lgtm


More sounds

Let's add sounds for:

Platform being pushed
Platform carried/released (on the actions)

or maybe platforms should always be making a humming noise? Well, maybe not. May be weird with visibility/disappearing.

Platform being destroyed
Switch pressed/released
Hitting a side wall (maybe a softer "thud")

Goal is to have enough sounds to make a blind playthrough not too hard. Although quite some places are probably blind-impossible - still would be nice to have a blind playthrough route. Pretty sure the ending of the game is possible that way, but not sure if any of the three Anti-Hub sections is playable blindly.

FYI blind playthrough likely NOT possible without major cheese.

Crumbling Upwards is very likely IMPOSSIBLE blind.

Suspecting some cheese here though that might actually enable it. Wasn't able to pull it off yet.

Ski Dyver would need VERY ACCURATE memoization. A sound effect when passing a gate might help, but probably not even that much. Likely impossible.
Rest seems possible. In particular, when having all three abilities, the longest anti-hub section seems doable blindly.

Still to do:

Platform being pushed

Some humming noise.

Platform carried/released (on the actions)

Grab/ungrab as sweep?

Platform moving "fast":

Humming noise.

Platform being destroyed

Explosion-ish but very weak.
Only if done by a RiserFsck.

Switch pressed/released

Sweep up/down.

Still to do:

Platform being pushed

Some humming noise.

Platform carried/released (on the actions)

Grab/ungrab as sweep?

Platform moving "fast":

Humming noise.

All done; there is some clicking noise to fix though. Filing a separate issue for that.


Article images max-height forced to 64vh

This line is working against us in some articles.
Why do we have a max-height?

This was a fast solution intended to prevent images from taking up too much of the screen:
(without max-height)

(with max-height)

Open to suggestions! Note that this is implemented in 4 places (also a fast solution) so ideally the fix is applied to all four places...even better, set up a single place for this fix! :D Thanks sir

(#322 is potentially related to this...)

@victorvalle did you have more thoughts? specific places where this is negatively affecting images? I'm inclined to close as it's over a year old :)

🔔 🔔 🔔  @victorvalle 🔔 🔔 🔔
Do you want to keep this open? A lot of things have changed in images, I'm not sure if this is necessary — please take a look and add any more clarification if we should move forward.

🔔 🔔 🔔  @victorvalle 🔔 🔔 🔔
Do you want to keep this open? A lot of things have changed in images, I'm not sure if this is necessary — please take a look and add any more clarification if we should move forward.

no... It happened a long time ago. No need to keep this open.

no... It happened a long time ago. No need to keep this open.


[Bug] Error occurred when gpintsystem using auto failover for coordinator feature

Cloudberry Database version
1.6.0
What happened
Error occurred when gpintsystem using auto failover for coordinator feature ,After configure with --enable-external-fts and etcd cluster also be installed;  The command I'm used is 'gpinitsystem  -c gpinitsystem_config  -h hosts -s gp140 -p /data/cloudberrydb/cbdb_etcd.conf -F /data/cloudberrydb/fts_service.conf  -U 1'
More detail errors see as below pitcures.

What you think should happen instead
No response
How to reproduce
https://www.linen.dev/s/cloudberrydb/t/22304006/hi-i-have-learned-that-there-is-an-auto-failover-for-coordin#23604d14-b41f-48a2-8b4e-92eae01b45cd External fts setup.pdf
The document on  website is not detailed enough .
Operating System
openEuler 22.03 (LTS-SP4)
Anything else
No response
Are you willing to submit PR?

[X] Yes, I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct.

Hi @jiaqizho, please double check the failures, thanks!

not support multi endpoints yet.

not support multi etcd endpoints，so gpdb doesn't support high availability right now?
Is the description of the official website inaccurate?   https://cloudberrydb.org/zh/docs/cbdb-op-software-hardware

@fsmiledream  can you check USE_INTERNAL_FTS value in pg_config.h ?


Tag and release new version and publish to npm

It would be nice if antennas is available npmjs.org.
So installing it would be as easy as running: npm install -g antennas

That's a good idea. If I can set aside some time for this repo, I'll get this setup.

Done!
You can now go npm install -g antennas and use antennas to launch it, or you can also use npx antennas to run it directly from NPM.

Done!
You can now go npm install -g antennas and use antennas to launch it, or you can also use npx antennas to run it directly from NPM.


Maha: Asynchronous-Programming, 3 Weeks.

Learning Objectives

🥚 You understand the JavaScript Event Loop, and can demonstrate this by using setTimeout and setInterval to schedule simple tasks.
🥚 You can explain why Asynchronous Programming is important for programs that have blocking and non-blocking tasks.
🥚 You can explain the basics of the Client/Server model and HTTP requests and can fetch data from RESTful APIs.
🐣 You can break down an asynchronous problem into smaller tasks and solve it using promises. This includes identify which tasks depend on each other and which are independent:

dependent tasks: The return value from one task is required to start the next task, these must be completed in a specific order - .then
independent tasks: These tasks do not use each other's return values, they can be completed at the same time - Promise.allsystem.

🐣 You can fetch data from an API and render it into the DOM using /api-calls, /handlers and async/await syntax.
🐣 You can write unit tests for functions that return promises using async/await syntax.

[ ] I have pushed my progress to stopWatch repo

What went well?
Understanding ..

sychornous and Asychronous
SetTimeout and setInterval

What went less well?
Separation concerns specially the start handler
Lessons Learned

Difference between sychornous and Asychronous
SetTimeout / cleartimeout
SetInterval / clear interval

Sunday Prep Work
Ongoing

todo-list repo
I Need Help With:

I didn’t succeed in applying http methods at todo-list project as it is required.
I still have problems in separate of concerns .

What went well?
Understanding fetch, async/await , try-catch block ..
What went less well?
Didn’t finish todo-list project
Lessons Learned

async/await syntax.
http request methods.

Sunday Prep Work
Not Yet


Ticket/2.8.x/update key

Currently blocked on getting some releases out the door, and then we'll go and bulk merge everything. I'm not sure which branches are currently in development, so I did everything that could potentially have a release in the future. If for some reason a release is cut from a branch that does not have these changes, we will see failures.


Clear incorrectly reported errors in d2i_CMS_ContentInfo

Fixes openssl#19003

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

Merged to master and 3.0 branches. Thank you.


Support Lambda Runtime Python3.10

CloudFormation Lint Version
v0.77.1
What operating system are you using?
Ubuntu
Describe the bug
E3030 You must specify a valid value for Runtime (python3.10). Valid values are ["dotnet6", "dotnetcore1.0", "dotnetcore2.0", "dotnetcore2.1", "dotnetcore3.1", "go1.x", "java11", "java8", "java8.al2", "nodejs", "nodejs10.x", "nodejs12.x", "nodejs14.x", "nodejs16.x", "nodejs18.x", "nodejs4.3", "nodejs4.3-edge", "nodejs6.10", "nodejs8.10", "provided", "provided.al2", "python2.7", "python3.6", "python3.7", "python3.8", "python3.9", "ruby2.5", "ruby2.7"]

Expected behavior
Python3.10 should be allowed: https://aws.amazon.com/blogs/compute/python-3-10-runtime-now-available-in-aws-lambda/
Maybe I should wait a bit longer and is this added by some CF spec update from AWS.
Reproduction template
  Function:
    Type: "AWS::Serverless::Function"
    Properties:
      ...
      Runtime: "python3.10"
     ...

Covered by automated PR #2698

@kddejong can we expect a new release soon so we can start using python 3.10 ?

Released in v0.77.2


Upgrade to Django 4.1.x

Upgrade Django, wagtail-purge, Django-pwned-password,django-basic-auth-ip-whitelist
Move logic from DeleteView -> delete() to form_valid()
Make test more robust
Upgrade dj-database-url to 2.x, and enable CONN_HEALTH_CHECKS
Bump django-two-factor-auth to 1.15.x that has confirmed support for Django 4.1
Bump django-ratelimit to 4.1.0
django-pwned-passwords seems be abandoned https://github.com/jamiecounsell/django-pwned-passwords/pull/11 (replaced with it with it's fork)

Update: Rebased on main and use official release version of wagtail-purge=0.3.0

@frjo Update with main and resolved conflicts.

Test are failing, found this regarding SuccessURLAllowedHostsMixin:

The undocumented django.contrib.auth.views.SuccessURLAllowedHostsMixin
mixin is replaced by RedirectURLMixin.

https://github.com/django/django/blob/21382e2743d06efbf5623e7c9b6dccf2a325669b/docs/releases/4.1.txt#L573-L574

Upgrade dj-database-url to 2.x, and enable CONN_HEALTH_CHECKS
Bump django-two-factor-auth to 1.15.x that has confirmed support for Django 4.1
Bump django-ratelimit to 4.1.0

@theskumar I merge in a couple of you other update PRs so this one has a small merge conflict now.
Will run this on test for a some days to be sure but it seems good to go in my testing.

Thanks for the quick merging. I've resolve the conflicts with main.

@frjo Would you be more comfortable if I stack the wagtail upgrade PR onto this django 4x PR? from testing perspective?

@theskumar Yes, I think it would be good to do the Wagtail 5 onto of Django 4. I think we can get this PR quickly tested and then merged in to main.
For Django 4.2.x LTS we need Wagtail 5 I believe. But that where I would like to go before the end of the year.

Done. Updated the base of the wagtail 5x to this PR.


Pin black and ruff versions

Closes #145
Changes
Modify pyproject.toml to pin black version (currently 24.1.1) and ruff version (currently 0.1.15), and add a black configuration argument so that black errors if it doesn't match the pinned version when run. AFAIK this is the only file that needs modification.
The changes don't quite meet the goal of avoiding duplicate version declarations (we're limited by the TOML file spec), but a mismatch between the black version pinned in development dependencies and the required version specified in tools.black should show up early in tests.
ruff doesn't have a flag that checks for a required version, so these changes won't prevent somebody from using a manually-up/downgraded version.
Internals

Pin black and ruff versions for consistency between local and CI/CD environments

Tests

[x] QC test passes locally (make test)
[ ] CI tests pass

Reviewer

@trdean1

Awesome, yes I think this should do it!
Maybe a question for @zebengberg  - is there a reason why the check in the action is different than the check in the makefile when it comes to what black gets run over?
I think this is why Tristian had to update the two test files here, but those did not get flagged by the CI/CD tests when I made my changes

Awesome, yes I think this should do it!
Maybe a question for @zebengberg - is there a reason why the check in the action is different than the check in the makefile when it comes to what black gets run over?
I think this is why Tristian had to update the two test files here, but those did not get flagged by the CI/CD tests when I made my changes

I think it's a historical artifact. We should try to rectify this.

Awesome, yes I think this should do it!
Maybe a question for @zebengberg - is there a reason why the check in the action is different than the check in the makefile when it comes to what black gets run over?
I think this is why Tristian had to update the two test files here, but those did not get flagged by the CI/CD tests when I made my changes

I think it's an historical artifact. We should try to rectify this.
I'm not sure if we can run Makefile recipes in the windows workflows, so addressing this may not be as simple as copying the recipe.

I can attest that this is true. Unfortunately we can't run the make on windows, so we'll either have to run the commands in CI, or just run the commands on the windows specific install.
Havin the windows specific test is important, so unfortunately I think the only thing to do is copy the commands into the action.
@thabbott Feel free to go ahead with this in this in the PR

Awesome, yes I think this should do it!
Maybe a question for @zebengberg - is there a reason why the check in the action is different than the check in the makefile when it comes to what black gets run over?
I think this is why Tristian had to update the two test files here, but those did not get flagged by the CI/CD tests when I made my changes

I think it's an historical artifact. We should try to rectify this.
I'm not sure if we can run Makefile recipes in the windows workflows, so addressing this may not be as simple as copying the recipe.

I'm a little confused what this has to do with Makefile recipes in Windows workflows. Is the idea that we'd rather be able to run make black-check in the GitHub action (so we don't have to manually maintain agreement with the Makefile), but can't because we don't currently install make in Windows workflows?

I think I've taken care of the windows workflow issues: test.yaml now

includes a step to install make on windows runners
uses Makefile recipes to installs a pycontrails dev environment and lint/test
specifies bash as the shell for the lint/test step, which stops windows workflows from passing despite linting errors (compare https://github.com/contrailcirrus/pycontrails/pull/146/commits/6dc660d679f77dc9233e4a177cf513318ad1972a, where windows runners should fail but don't, to https://github.com/contrailcirrus/pycontrails/pull/146/commits/dc06df164dd3597ed09acb9a054484512b4dd156, where they correctly fail)
Any outstanding issues I should address before I merge?

Can I use a Makefile recipe to install pycontrails-bada, or is should I leave those steps as they are?

I think leave as is! I don't think this recipe would work for windows, even with your support for make here.


⚠ Bofrost.de has degraded performance

In 868d9bb, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1531 ms

Resolved: Bofrost.de performance has improved in 26dcedc.


Modal popup javascript removing style element from body

This code should only remove the 2 style attributes used by the modal, not the style itself.

Fixed.


Unable to get server certificates

I can not  get this proxy to work I've changed resolver address tried different syntax and different port numbers I still get the error unable to retrieve server certificate I've been trying for the last week to get it work!

You shouldn't really have to change resolver addresses and ports. Giving a provider name should be enough:
dnscrypt-proxy -R okturtles

What does the following command return on your system?
drill -p 443 txt 2.dnscrypt-cert.fr.dnscrypt.org @<IP_ADDRESS>

Or if you just have dig:
dig -p 443 txt  2.dnscrypt-cert.fr.dnscrypt.org @<IP_ADDRESS>

The first command returns saner error unable to retrieve certificates Don't have drillDig command returns connection timed out I'm using tails debain Linux system Thank you so much for your reply Sent using CloudMagicOn Mon, Jan 5, 2015 at 16:37,  Frank Denis<EMAIL_ADDRESS>wrote:            You shouldn't really have to change resolver addresses and ports. Giving a provider name should be enough:
dnscrypt-proxy -R okturtles
What does the following command return on your system?
drill -p 443 txt 2.dnscrypt-cert.fr.dnscrypt.org @<IP_ADDRESS>
Or if you just have dig:
dig -p 443 txt  2.dnscrypt-cert.fr.dnscrypt.org @<IP_ADDRESS>
—Reply to this email directly or view it on GitHub.

Are you running it over Tor? As far as I know, Tor doesn't support UDP.

Yes I am but I'm using tcp only and port 443 so that should work?Sent using CloudMagicOn Mon, Jan 5, 2015 at 18:27,  jedisct1/dnscrypt-proxy<EMAIL_ADDRESS>wrote:            Are you running it over Tor? As far as I know, Tor doesn't support UDP.
—Reply to this email directly or view it on GitHub.

It might change at some point but unfortunately, UDP is still required to retrieve the certificates. So you should not block port 443/UDP, at least for packets sent to the DNS resolver you are using.

Hi @jedisct1 ,
Is it possible to force dnscrypt-proxy to fetch server certificates over TCP?
I tried --tcp-only, but it still failed when retrieving server certificates.
I'm behind my company's firewall and UDP over port 443 is not allowed, and it's not possible to ask administrator to open the port for me.


remove develop branch

The main/ develop split adds a frustrating roadblock to development as it effectively requires doubling up of review on changes.  Would be much more straightforward to just merge feature branches straight into main and tag releases.  Possibly also creating release branches.
I think this may have implications for the documentation on readthedocs so need to investigate that before removing the develop branch.

I've come to learn that this style of development ('main+friends') is called trunk-based development.
I'm a fan of 'tag to release' as a model - microsoft really like release branches, but I believe that they also commit to patching critical bugs previous releases (hence causing the history to diverge), which we would never do for tubular - people should just update to a version with the bug patched. The release branches would effectively be save-game points on the journey through the commit history, which is exactly the same as tags.

Thanks for the link.  I agree about tagging vs. release branches, no current plans to bugfix old releases.  Trunk based development with tagged releases seems like the way to go.  Will look to make this change after the next release.

Changed pypi release process to trigger upon creating a release on github (which also creates a release tag) in #161.  Have now removed develop branch so we will use  trunk-based development from main from now on.


Bloxstrap has a seizure

Hi, new here. I went around and downloaded Bloxstrap, and resized it to see all the options it has to offer. Bloxstrap immediately had seizures.
The window frame resizes before the application itself and sits there until the window frame catches up:

The application outright flashes at ridiclous speeds on resize (Can't get a image when it resizes, it looks something like this):

It only gets worse the bigger the window of Bloxstrap is.
Specifications
I know, I know.
CPU: Pentium E6500 - 2C/2T 2.93 GHz
GPU: Integrated (Intel G41 Express Chipset DX10), 798MB shared VRAM
RAM: 1981 MB
Operating System: Windows 7 (Build 7601.24546) 64-Bit
Storage Device: HDD, sadly...
Workaround

The seizure does not happen when disabling the Windows Aero effects. But then some applications demand Aero, and then some other application functionality breaks (Discord makes every non-Roblox application screenshared have a literal seizure)

Question
Is Bloxstrap meant to work on these PC specifications?

The problem is just that it's a little slow when resizing, and that's it?

Issue has been awaiting clarification for over a month, closing as stale. If you have anything further to add, just respond and I'll reopen.


Flushing a view via FlushAsync breaks AntiForgeryToken via HTML Helper & FormTagHelper

If a view calls FlushAsync before a call to IHtmlHelper.AntiForgeryToken or the use of the FormTagHelper (by way of them being deferred in a declared section), then no anti-forgery cookie is sent to the client, as the headers are flushed before the helper can add the cookie to the response. No error is thrown during the GET requests, however any subsequent attempt to POST the form will result in InvalidOperationException: The required anti-forgery cookie "__RequestVerificationToken" is not present.
This is most easily demonstrated in the canonical use of FlushAsync in flushing the  element before the result of the view in _Layout.cshtml:
<!DOCTYPE html>

    <meta charset="utf-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
<EMAIL_ADDRESS>- My ASP.NET Application</title>
    <link rel="stylesheet" href="~/lib/bootstrap/css/bootstrap.css" />
    <link rel="stylesheet" href="~/css/site.css" />

@{ await FlushAsync(); }

    @RenderBody()
    @await RenderSectionAsync("Body", required: false)
   ...

This will cause the following view to fail upon POST:
@model WebApplication7.Models.LoginViewModel

@{
    ViewBag.Title = "Log in";
}

@section Body {
<EMAIL_ADDRESS>

            @using (Html.BeginForm("Login", "Account", new { ReturnUrl = ViewBag.ReturnUrl }, FormMethod.Post, new { @class = "form-horizontal", role = "form" }))
            {
                @Html.AntiForgeryToken()

Use a local account to log in.

...

Suggested Fix
To fix this we'll need to come up with a way to coordinate the sending of the cookie header before the helper has run.
Here's a straw-man idea to get started:
Have the helpers throw an exception if they attempt to set the cookie but the headers are already flushed. This will alert the dev to the issue they've introduced which can then be mitigated using the change below.
Make the Flush method set the anti-xsrf cookie based on a flag that can be set from the view (e.g. a property on the base class or a value in the ViewBag). This way, the view and layout page can coordinate to conditionally send the header only when it's required, e.g.
_Layout.cshtml
...

@{ await FlushAsync(); } @* This will automatically flush the anti-xsrf cookie if  *@

    @RenderBody()
    @await RenderSectionAsync("Body", required: false)
...

Login.cshtml
@model WebApplication7.Models.LoginViewModel
@{
    ViewBag.Title = "Log in";
    // Indicate to the layout page that anti-xsrf token must be sent during pre-flush
    ViewBag.RequiresAntiForgeryToken = true;
}
@section Body {
<EMAIL_ADDRESS>

            @using (Html.BeginForm("Login", "Account", new { ReturnUrl = ViewBag.ReturnUrl }, FormMethod.Post, new { @class = "form-horizontal", role = "form" }))
            {
                @* The helper would need to coordinate with the value already flushed to the client
                      so as to ensure the correct hidden field value is rendered here *@
                @Html.AntiForgeryToken()

Use a local account to log in.

...

Checked in - 951ed05893d10beafbbe6449652684c19f2384ae


Plot graph refactor

Lots of refactorings to move executable code out of the top level.  Almost everything is now done in functions.

Thanks!

Am I understand correctly, that now refactoring is done?

If you're asking because you want to go ahead and make your changes without worrying about the file changing underneath you then let's say yes, it's done and you can go ahead!

Thanks!

Am I understand correctly, that now refactoring is done?

If you're asking because you want to go ahead and make your changes without worrying about the file changing underneath you then let's say yes, it's done and you can go ahead!

Perfect!


int error while searching for meta-analysis

If you have a study that has an int in the title, like "This is my 454 title" and then you search for: study_title includes " 454 ", the search will error out with: The includes operator is not for use with data of type <type 'int'>

This is related to the old search functionality, which has been superseded by redbiom. Closing.


Compilation error due to lodash and underscore definitions conflict

In Visual Studio while working on grunt-ts itself, I'm intermittently getting an issue with the lodash definition and underscore definitions conflicting with each other.
To fix it, I've had to comment out the ThrottleSettings, TemplateSettings, List<T>, and Dictionary<T> interfaces in underscore.d.ts, as well as commenting out the line that declares the actual _ variable.
I'm not sure what I did to get Visual Studio to recompile these files as it had been working fine.
How do people feel about me checking in this hacked-up definition?  If we ever refresh with tsd it will break.  How do other people handle this?  I tried to remove the underscore.d.ts altogether and underscore.string started having problems.  Is there a lo-dash string we could use instead?

Should be fixed in 6d7742e544aea9c352a9e152f20081df69e2a6ec.


4.2 Cloud Wallet Interfaces and Open API Integration

the para says,

APIs implemented for the specifications above (IF002 - IF005) SHALL follow the OCI OpenAPI specification for Digital Wallet Providers. See OpenAPI Spec for further details.

I suggest to remove all but IF002 from the sentence, as OCI has not specified IF005 yet and IF003/4 cannot be specified as far as I understand.

Triage:

[ ] Is Issue appropriate for OCI Architecture
[ ] Assign Size
[ ] Assign Priority
[ ] Assign Label (if needed)
[ ] OCI affected Artifacts Identified
[ ] Assign Triage - Artifact Version Target (v x.x.x Milestone)
[ ] Assign Triage - Interop Profile Version Target (v x.x.x Milestone)
[ ] Create sub-project (if needed)

None of the specifications have been specified - can't comply with them.
Alex: Maybe: "APIs implemented for the specifications above (IF002 - IF005) SHALL follow published OCI OpenAPI specifications for Digital Wallet Providers. At time of writing, only IF002 is covered by the OpenAPI Spec. See OpenAPI Spec for further details."

Alex: Or: "APIs implemented for the specifications above (IF002 - IF005) SHALL follow published OCI OpenAPI specifications for Digital Wallet Providers. As of April 2023, only IF002 is covered by the OpenAPI Spec. See OpenAPI Spec for further details."

May result in removal of 1, 3, 4, 5 and creation of Issues to complete the work.

while we're at it, we should also replace the MUST with a SHALL

Implementers MUST conform to [RFC7231] and [RFC2616] when processing and returning HTTP Status Codes

July, 27: released in Digital Wallet Criteria v3.0.0,  interop profile v3.2.0


Update sbt-scalajs, scalajs-compiler, ... to 1.3.0

Updates

org.scala-js:sbt-scalajs
org.scala-js:scalajs-compiler
org.scala-js:scalajs-test-bridge

from 1.2.0 to 1.3.0.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-js" } ]

labels: library-update, semver-minor

I have a problem with this: users of the library will be forced to upgrade to Scala.js 1.3, otherwise they will see an error like “unsupported IR version 1.3”.
Is there a way to ask Scala.js to emit an IR compatible with older versions? @sjrd

There is no way to ask that of Scala.js. If there was, we wouldn't bump the IR version in the first place.
That said, this has never been an issue before. Scala.js doesn't break stuff, so upgrading is always an option for the users. It can happen that we introduce a regression, despite all our efforts, but that's pretty rare.
This isn't something new in Scala.js 1.x. We've applied that policy in 0.6.x for years (where for example 0.6.29 was not forwards binary compatible with 0.6.28) and somehow people never complained about that. Now that we make it front and center in every release notes, maintainers question it (you're not the first), although in fact no user has ever experienced any issue with that in the past 5 years.
This is also not really different than any regular library. It's just that for libraries, Ivy resolution automatically brings in a newer version of a transitive dependency when necessary; whereas here, you might have to follow an error message that tells you to modify the version of sbt-scalajs yourself.


feat: add object retention feature

Adds the object retention feature and tests

The current failure is just because the test project isn't allowlisted yet, it should be soon


Latest d.ts

Docs Build status updates of commit 9b7a89d:
:clock10: Pending: waiting for processors (41 builds ahead of you)
:warning: Docs Build is busy, currently there are 41 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 9b7a89d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/docs-ref-autogen/excel/excel/excelscript.pivotlayout.yml
:white_check_mark:Succeeded

generate-docs/api-extractor-inputs-excel/excel.d.ts
:white_check_mark:Succeeded

generate-docs/json/excel/excel.api.json
:white_check_mark:Succeeded

generate-docs/script-inputs/excel.d.ts
: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.


Yet another incomplete class path

Sorry for yet another issue regarding the missing classpath. I've read most of the existing ones but I couldn't proceed with fixing this myself. I read #37 which is a close match, but there it says the issue was fixed in 0.6.6 (I'm on 0.8.3).

As this image shows, no matter what java file I open I get the incomplete classpath error even though I clearly have build.gradle in the same project folder. I've used the project opened for a long time and I've seen no misconfiguration regarding Gradle itself.
This is not an Android application, just pure Java which the upstream JDT server seems to support.

Just have the same problem what i try is install the older version and it work

Tentatively closing as there is a good chance this has been resolved by the upgrade to version 0.39.0 of the language server.


small changes to simplify the build

address @jakirkham 's comments

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Test npm Packaging

Build a separate application (use the demo) in order to test the final npm package and ensure it works properly in an application.
https://dev.to/scooperdev/use-npm-pack-to-test-your-packages-locally-486e
https://javascript.plainenglish.io/how-to-test-a-node-package-locally-8dde33e642df
https://medium.com/@oresoftware/node-js-how-to-test-your-new-npm-module-without-publishing-it-every-5-minutes-3b6f8e0491dd

Works very well; must remember to import the style.css somewhere like App.vue.


Support for (partial) < py37 target-versions?

Is there interest towards partial support for Python < 3.7 target-versions?
Even though Python < 3.7 is currently EoL as far as python.org is concerned, for example Ubuntu ESM has 14.04 with Python 3.4 supported until 2024, 16.04 with Python 3.5 supported until 2026, etc.
I have a small project that is currently intended to work down to Python >= 3.3 for $reasons (soon >= 3.5), and could look into contributing exclusions and adjustments to advise given by ruff that, if followed, would break the project on these old versions. This would certainly be far from exhaustive, covering just what I happen to come across, so I guess it's debatable whether doing something like this would be better than the current status, i.e. no support for such old versions.

I think I'd prefer not to extend official pre-3.7 support. If there were one or two adjustments that were really impactful, I'd consider including them, but frankly it's helpful to be able to draw a line at 3.7.

Understood, no problem, I'll add the relevant exclusions in the project config.


bug: Limit server params to 3

App is working in https://pr-89--pyshiny.netlify.app/components/inputs/action-button/
Merging


[2.0.0] NativeAdmobOptions is not overriding theme

First of all, thanks for the package. Its really good.
I am using NativeAdmobOptions for change ad theme, but its not change anything.
My NativeAdmobOptions (show media works but styles not working)
NativeAdmob(
        adUnitID: "ca-app-pub-3940256099942544/2247696110", // Google native unit id for test
        options: NativeAdmobOptions(
          ratingColor: Colors.red,
          headlineTextStyle: NativeTextStyle(color: Colors.red),
          bodyTextStyle: NativeTextStyle(color: Colors.red),
        ),
      ),

Result:

@devibrahimkarahan Hey, thanks for pointing this out. Just reviewed the code and fixed the issue. Please update to the latest to get the fix!
Close this if that is not happening anymore

Thanks, fixed


ValueConvertible cannot be used with dictionary literal in swift 3.0.2

Hello:
Just started using MongoKitten and I got to this error:

I am running swift 3.0.2 on macOSX 10.11.6 (EL Capitan).
Thanks!

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

MongoKitten 3 requires any dictionary to be explicitly marked as a Document.
So that would work like this:
let document: Document = [
    "key": ["$exists": true] as Document
]

This is solved in MongoKitten 4 (but requires Swift 3.1)

Nice, thanks for the answer ;)


oxford nanopore data

Hi guys,
I have some ONP resequencing data that I would like to run through snpArcher if possible. I've generated .bams deduplicated with sambamba outside of snpArcher, as ONP data are single end and I wasn't sure how that would be handled. Additionally, the alignment step was taking a super long time. I would now like to generate vcfs for these few samples and run them through the rest of the pipeline. I tried manually making a results directory then a subdirectory with the name of the reference, then dropping the bams and genome files in. When I go to submit the job I get the following error:
Using workflow specific profile /hb/groups/bernardi_lab/Jason_OPOR/snpArcher/profiles/slurm for setting default command line arguments.
snpArcher: Using Snakemake 8.10.7
Building DAG of jobs...
InputFunctionException in rule fastp in file /hb/groups/bernardi_lab/Jason_OPOR/snpArcher/workflow/rules/fastq.smk, line 31:
Error:
  ValueError: can only convert an array of size 1 to a Python scalar
Wildcards:
  refGenome=DFU_1000_500_no_contaminants.fasta
  sample=DFU_Big_file_pc2_36_37_38_39
  run=DFU
Traceback:
  File "/hb/groups/bernardi_lab/Jason_OPOR/snpArcher/workflow/rules/common.smk", line 218, in get_reads
  File "/hb/home/jwjohns/.conda/envs/snparcher/lib/python3.11/site-packages/pandas/core/base.py", line 418, in item (rule fastp, line 68, /hb/groups/bernardi_lab/Jason_OPOR/snpArcher/workflow/rules/fastq.smk)

I realize that the solution to this may be quite complicated, especially since ONP data are single end reads, but I thought I would drop a note to see if you guys have dealt with this before and have a quick fix. If it's at all complicated I'll probably just run these few samples through the same workflow (haplotypecaller, filtering, QC, etc.), but manually - especially since it's only a few files. Let me know what you think. Thanks!

I'm not sure that GATK is the best method to use for calling SNPs with ONT data, to be honest. Something like pepper is probably going to work a lot better. While we have aspirations to eventually support this within the snpArcher framework, it is a long term goal likely dependent on further funding for development, so unfortunately not something we are likely to be able to implement soon.

That makes sense, Tim. Thank you for the advice!


feat: add getContainer method to public api

Pull request type
Check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

NOTE: Before to create a PR, read our contributing guide

NOTE: Try to limit your pull request to one type, submit multiple pull requests if needed.

What is the current behavior?
Issue Number: N/A

NOTE: Describe the current behavior that you are modifying, or link to a relevant issue.

Currently, there seems to be no way to get the container dom element from a sigma renderer instance.
What is the new behavior?

NOTE: Describe the behavior or changes that are being added by this PR.

This PR adds a new getContainer method to the public api, which simply returns the container dom element.
Other information

NOTE: Any other information that is important to this PR such as screenshots of how the component looks before and after the change.

This can be useful e.g. for toggling fullscreen mode on the container dom element. It would also avoid having to pass down the container element separately via React context in react-sigma (see https://github.com/sim51/react-sigma/blob/main/packages/core/src/components/SigmaContainer.tsx#L91).

Thanks a lot! Your PR has been manually rebased and merged, and it will be available with the next version (I'm not exactly sure when, though).


feat(vite-plugin-nitro): add initial support for sitemap generation

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/analogjs/analog/blob/main/CONTRIBUTING.md#-commit-message-guidelines
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

Which package are you modifying?

[ ] vite-plugin-angular
[x] vite-plugin-nitro
[ ] astro-angular
[ ] create-analog
[ ] router
[x] platform
[ ] content
[ ] nx-plugin
[ ] trpc

What is the current behavior?
Closes #307
What is the new behavior?
Added a config property in pre-render (though, now, that could probably change in the end). This ends up being a property that is just used to generate the domain name needed... I'm open to changing that to a top-level property, I think it'll make more sense.
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information
[optional] What gif
none yet :(

Thanks for the review. Made requested changes.

Thanks! @allcontributors add @QuantariusRay for code


deleteMany not working on prisma 6.1.0

Bug description
The deleteMany directive (when inserting or updating records) does not work on prisma 6.1.0. The bug was detected after upgrading. A downgrade to 5.22.0 solves the issue.
How to reproduce

Expected behavior
No response
Prisma information

// Add your schema.prisma

// Add your code using Prisma Client

Environment & setup

OS:
Database:
Node.js version:

Prisma Version

6.1.0

I have also encountered the same issue with MongoDB.

Hi @alzatius
Can you please provide the relevant parts of your schema and query? This will help in reproducing the issue.

Hi Rafael,
The relevant code is:
export const updateBoard = async (board: QBoard) => {
let retData: QData = {
isError: false,

isShop: false,

errorMsg: "",

data: null,

};
let itemModels: MediaItemBoard[] = [];
board.items.map((item, index) => {
itemModels.push({

  index: index + 1,

  fileId: item.fileId,

  fileExt: item.fileExt,

  alt: item.alt,

} as MediaItemBoard);

});
let updBoard = null;
try {
updBoard = await prisma.mediaPanelBoard.update({

  where: {

    id: board.panelId,

  },

  data: {

    name: board.name,

    itemHeight: board.itemHeight,

    itemWidth: board.itemWidth,

    items: {

      deleteMany: {},

      create: itemModels,

    },

  },

  include: {

    items: true,

  },

});

} catch (e) {
retData.isError = true;

if (e instanceof Prisma.PrismaClientKnownRequestError) {

  if (e.code === "P2025") {

    // the code for non-found record

    return await addAtelierBoard(board);

  }

} else if (

  e instanceof Prisma.PrismaClientKnownRequestError ||

  e instanceof Prisma.PrismaClientUnknownRequestError

) {

  retData.errorMsg = e.message;

} else {

  retData.errorMsg = "Unknown message";

}

} finally {
retData.data = updBoard;

}
return retData;
};
And the schema:
model MediaPanelBoard {
id         String           @id @unique
createdAt  DateTime         @default(now())
updatedAt  DateTime         @updatedAt
name       String           @default("")
atelierId  String           @default("")
itemHeight Int              @default(100)
itemWidth  Int              @default(100)
atelier    UserAtelier      @relation(fields: [atelierId], references: [id], onDelete: Cascade)
items      MediaItemBoard[]
@@index([atelierId])
}
model MediaItemBoard {
id        String          @id @default(uuid())
createdAt DateTime        @default(now())
updatedAt DateTime        @updatedAt
boardId   String          @default("")
index     Int             @default(1)
fileId    String          @default("")
fileExt   String          @default("")
alt       String          @default("")
board     MediaPanelBoard @relation(fields: [boardId], references: [id], onDelete: Cascade)
@@index([boardId])
}
The issue started to happen after I upgraded from 5.22 to 6.1.
I hope this helps.
Cristian
From: Raphael Etim @.>
Sent: Monday, December 23, 2024 10:02 AM
To: prisma/prisma @.>
Cc: Cristian Alzati @.>; Mention @.>
Subject: Re: [prisma/prisma] deleteMany not working on prisma 6.1.0 (Issue #25903)
Hi @alzatius https://github.com/alzatius
Can you please provide the relevant parts of your schema and query? This will help in reproducing the issue.
—
Reply to this email directly, view it on GitHub https://github.com/prisma/prisma/issues/25903#issuecomment-2559246303 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AA46KWWGDK2Q7WZ2ZM4Z6N32G7GOVAVCNFSM6AAAAABT6ZHWGOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJZGI2DMMZQGM .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/AA46KWTQJM3OHDF3XAXXHWD2G7GOVA5CNFSM6AAAAABT6ZHWGOWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUYRL756.gif Message ID: @.*** @.***> >

Hi again,
I forgot to include the schema’s config:
generator client {
provider = "prisma-client-js"
}
datasource db {
provider     = "mysql"
url          = env("DATABASE_URL")
relationMode = "prisma"
}
Cheers,
Cristian
From: Raphael Etim @.>
Sent: Monday, December 23, 2024 10:02 AM
To: prisma/prisma @.>
Cc: Cristian Alzati @.>; Mention @.>
Subject: Re: [prisma/prisma] deleteMany not working on prisma 6.1.0 (Issue #25903)
Hi @alzatius https://github.com/alzatius
Can you please provide the relevant parts of your schema and query? This will help in reproducing the issue.
—
Reply to this email directly, view it on GitHub https://github.com/prisma/prisma/issues/25903#issuecomment-2559246303 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AA46KWWGDK2Q7WZ2ZM4Z6N32G7GOVAVCNFSM6AAAAABT6ZHWGOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJZGI2DMMZQGM .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/AA46KWTQJM3OHDF3XAXXHWD2G7GOVA5CNFSM6AAAAABT6ZHWGOWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUYRL756.gif Message ID: @.*** @.***> >

Hi @alzatius
Can you please share the error message you got? I can confirm the deleteMany works with Prisma version 6.1.0.


TypeError: Cannot assign to read only property 'exports' of object '#'

Current Behavior

I tried to import ReactPlayer to my react rails app. I added the line below:
import ReactPlayer from 'react-player' and the page cannot be loaded. I saw the error below in console:
TypeError: Cannot assign to read only property 'exports' of object '#<Object>'
    at Module.<anonymous> (utils.js:126:1)
    at ./node_modules/react-player/lib/utils.js (utils.js:368:1)
    at __webpack_require__ (index-07d9361752105ff10b68.js:64:30)
    at ./node_modules/react-player/lib/players/index.js (index.js:81:1)
    at __webpack_require__ (index-07d9361752105ff10b68.js:64:30)
    at ./node_modules/react-player/lib/index.js (index.js:81:1)
    at __webpack_require__ (index-07d9361752105ff10b68.js:64:30)

It fails at this line:
module.exports = __toCommonJS(utils_exports);
Expected Behavior

I want to use ReactPlayer to play a video but it fails at importing
Steps to Reproduce

I just add the line below into my app and the page error out:
import ReactPlayer from 'react-player'
Environment

URL attempting to play:
localhost
Browser: Chrome
Operating system: macOS 13.5.1

Other Information

node version: v14.21.3
yarn version: v1.22.19
babel.config.js:
module.exports = function(api) {
  var validEnv = ['development', 'test', 'production']
  var currentEnv = api.env()
  var isDevelopmentEnv = api.env('development')
  var isProductionEnv = api.env('production')
  var isTestEnv = api.env('test')

  if (!validEnv.includes(currentEnv)) {
    throw new Error(
      'Please specify a valid `NODE_ENV` or ' +
        '`BABEL_ENV` environment variables. Valid values are "development", ' +
        '"test", and "production". Instead, received: ' +
        JSON.stringify(currentEnv) +
        '.'
    )
  }

  return {
    presets: [
      isTestEnv && [
        '@babel/preset-env',
        {
          targets: {
            node: 'current'
          },
          modules: 'commonjs'
        },
        '@babel/preset-react'
      ],
      (isProductionEnv || isDevelopmentEnv) && [
        '@babel/preset-env',
        {
          forceAllTransforms: true,
          useBuiltIns: 'entry',
          corejs: 3,
          modules: false,
          exclude: ['transform-typeof-symbol']
        }
      ],
      [
        '@babel/preset-react',
        {
          development: isDevelopmentEnv || isTestEnv,
          useBuiltIns: true
        }
      ]
    ].filter(Boolean),
    plugins: [
      'babel-plugin-macros',
      '@babel/plugin-syntax-dynamic-import',
      isTestEnv && 'babel-plugin-dynamic-import-node',
      '@babel/plugin-transform-destructuring',
      [
        '@babel/plugin-proposal-class-properties',
        {
          loose: true
        },
      ],
      [
        '@babel/plugin-proposal-private-methods',
        {
          loose: true
        }
      ],
      [
        '@babel/plugin-proposal-object-rest-spread',
        {
          useBuiltIns: true
        }
      ],
      [
        '@babel/plugin-transform-runtime',
        {
          helpers: false,
          regenerator: true,
          corejs: false
        }
      ],
      [
        '@babel/plugin-transform-regenerator',
        {
          async: false
        }
      ],
      isProductionEnv && [
        'babel-plugin-transform-react-remove-prop-types',
        {
          removeImport: true
        }
      ]
    ].filter(Boolean)
  }
}

webpack.config
const path = require('path');
module.exports = {
  mode: 'production',
  entry: './src/index.js',
  output: {
    path: path.resolve(__dirname, 'dist'),
    filename: 'bundle.js',
  },
  module: {
    rules: [
      {
        test: /\.js$/i,
        include: path.resolve(__dirname, 'src'),
        use: {
          loader: 'babel-loader',
          options: {
            presets: ['@babel/preset-env'],
          },
        },
      },
      {
        test: /\.css$/i,
        include: path.resolve(__dirname, 'src'),
        use: ['style-loader', 'css-loader', 'postcss-loader'],
      },
      {
        test: /\.mp4$/,
        use: {
          loader: 'file-loader'
        }
  }
    ],
  },
  devServer: {
    contentBase: path.resolve(__dirname, 'dist'),
    watchContentBase: true,
  },
};

I don't see anyone facing the same issue, I guess it might not be related to the package. But I don't know how to debug and proceed. Please help, thanks

I get something similar:
Warning: React.jsx: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: object.

And when trying to fetcher the player/file like the example in the readme with youtube
I need to do
import ReactPlayer from 'react-player/file.js'

@angela318  if in the last two weeks you found a work around could you please keep me in touch? 🙏
thanks in advance

I get something similar:
Warning: React.jsx: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: object.

And when trying to fetcher the player/file like the example in the readme with youtube
I need to do
import ReactPlayer from 'react-player/file.js'

@angela318 if in the last two weeks you found a work around could you please keep me in touch? 🙏
thanks in advance

I haven't found any workaround and am currently using the video tag directly
Reference: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/video


Fix types for use() module

Depends on https://github.com/i18next/i18next/pull/1296

@jamuhl patch release

published in<EMAIL_ADDRESS>


Security error. Parameter is not valid.

The tool was awesome and it definitely helps a lot.
I am trying to run it on a solution and I have encountered this issue.

Hi @Adterania , do you have any video or audio files in any of your apps inside that solution? Just realised that I am not handling them yet, thus they should throw this kind of error

Hi @Adterania , do you have any video or audio files in any of your apps inside that solution? Just realised that I am not handling them yet, thus they should throw this kind of error

Wait, I think they get ignored. But either way, can you actually open make.powerapps.com and check inside the Media section of your app(s) what kind of resources you have there? I'm curious if it's a "broken image" that's causing this problem, or if it's something else

Not entirely sure why it breaks for you, but I was able to replicate the behaviour (approximately) by adding "broken media files" (that is, items added as JPG files, but they aren't valid images) to an app.
Added some extra code to handle such problems, the documentation will include a comment saying "Resource Preview is not available, media file is invalid." if it encounters such a problem

This fix will be included in the next release

Latest release is now available: https://github.com/modery/PowerDocu/releases/tag/v-1.1.0


Restructure documentation of implementations in providers

Implementation specific stuff has been documented in provider-{name}(7), which were never meant to hold implementation specific information.
This PR creates a structure for implementation specific documentation, and paves the way by moving the documentation for EVP_MD implementations found in the FIPS and default providers.  It's with the expectation that others will participate as well and move some other implementation specific documentation in a similar way.

Not for this PR but it would be very nice if find-doc-nits could somehow figure out if stuff in section 7 was missing.

Hmmmmm... So you mean like pilfering through all OSSL_ALGORITHM for each of our providers and figuring out what man pages there should be to document them? That could be doable.
Like you said, another PR...

Hmmmmm... So you mean like pilfering through all OSSL_ALGORITHM for each of our providers and figuring out what man pages there should be to document them? That could be doable.

Yes. Even nicer if we can go through the gettable/settable lists and figure out what parameters should be documented.

Yes. Even nicer if we can go through the gettable/settable lists and figure out what parameters should be documented.

That should be doable.  We even have an appropriate command to give us that information...

I think I've addressed all concerns so far.

24 hours has passed since 'approval: done' was set, but this PR has failing CI tests.  Once the tests pass it will get moved to 'approval: ready to merge' automatically, alternatively please review and set the label manually.

24 hours has passed since 'approval: done' was set, but this PR has failing CI tests.

@iamamoose, considering we have Travis timeouts more often than not, this will get annoying fast...

24 hours has passed since 'approval: done' was set, but this PR has failing CI tests.

@iamamoose, considering we have Travis timeouts more often than not, this will get annoying fast...

it will only ever do one message per PR and it's not clever enough to know the difference between a real CI fail and a timeout or something we actually care about.  Got an alternative suggestion?  Should we believe that it if was put in 'approval done' then we'll assume someone already doesn't care about the failed CI and move it to ready anyway?

Those are good questions.  BTW, I wasn't thinking that the script would nag, but rather that this will probably happen in a number of PRs and become annoying through that repetition.

Should we believe that it if was put in 'approval done' then we'll assume someone already doesn't care about the failed CI and move it to ready anyway?

I've so far seen us act in a way that makes 'approval done' fairly trustable.  There are a number of PRs where people have explicitly waited to see how the CIs fare before setting that label.

24 hours has passed since 'approval: done' was set, but this PR has failing CI tests.

@iamamoose, considering we have Travis timeouts more often than not, this will get annoying fast...

it will only ever do one message per PR and it's not clever enough to know the difference between a real CI fail and a timeout or something we actually care about. Got an alternative suggestion?

I have an alternative suggestion: we MUST fix the root problem which is the fact that the CIs ar constantly failing on the stable branches!
Here for example is the Travis CI history of the last months which shows a disastrous success rate:
$ pdftotext travis-ci-history.pdf - | tr '\f' '\n'  | awk '/^#/ {count[$2]++} END {for (x in count) print x, count[x];}'
passed 169
failed 468
errored 136
started 1
canceled 1

cc @openssl/otc

How do you want to do that if most of the false failures (not counting extended tests now)  are timeouts?

And isn't the Travis history document about the merged commit tests which include extended tests which have been broken for quite long time due to #11182. But in case of PR CI runs we are talking about the base set of tests.

How do you want to do that if most of the false failures (not counting extended tests now) are timeouts caused by infrastructure?

travis_retry?
https://docs.travis-ci.com/user/common-build-problems/#timeouts-installing-dependencies


test: add unit tests to hydrate/values

PR Checklist

[x] Addresses an existing open issue: fixes #447
[x] That issue was marked as status: accepting prs
[x] Steps in CONTRIBUTING.md were taken

Overview
An ongoing PR for adding unit tests to hydrate components.
currently added:

src/hydrate/values/readAuthorIfExists
src/hydrate/values/readOwnerFromGitRemote
src/hydrate/values/readFundingIfExists

@all-contributors please add @rnr1 for test.

🤖 Beep boop! This comment was added automatically by all-contributors-auto-action.
Not all contributions can be detected from Git & GitHub alone. Please comment any missing contribution types this bot missed.
...and of course, thank you for contributing! 💙


added vpc endpoint to access secrets manager

What's this PR do?
Solves #10

Summary by CodeRabbit

New Feature: Added a new attribute region to the VPC module to specify the AWS region.
New Feature: Introduced an AWS VPC endpoint for Secrets Manager, enhancing security by enabling private connections between the VPC and Secrets Manager. This change allows the VPC to directly access Secrets Manager without needing to traverse the public internet.
Refactor: Added a new variable "region" in the VPC module for better configurability and code reusability.

@AgusPk just need to run terraform fmt in the file that is failing on CI, the rest is OK 👌🏻


Jenayah: Watch digitalnewsday.com

Jenayah requests the watch of the watch_keyword digitalnewsday\.com. See the MS search here and the Stack Exchange search here.

digitalnewsday\.com has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Approved by Makyen in Charcoal HQ


Please tell how to use flag into our ImageView

i am getting Flag String in the console, but i am not able to set that string on imageView.
I am pasting my code here.
please suggest how to find the bundle so that imageView can pick the image associating with that string.
Thanks.
func didSelected(with country: Country) {
self.flag_ImgView.image = UIImage(named: country.flag)
self.countryName_Lbl.text = country.name
}

@cnfuzedRk62 we use flag as emoji for lite storage and size
you can use this extension to convert flags to UIImage
extension String {
    func toImage() -> UIImage? {
        let size = CGSize(width: 24, height: 24)
        UIGraphicsBeginImageContextWithOptions(size, false, 0)
        UIColor.white.set()
        let rect = CGRect(origin: .zero, size: size)
        UIRectFill(CGRect(origin: .zero, size: size))
        self.draw(in: rect, withAttributes: [.font: UIFont.systemFont(ofSize: 24)])
        let image = UIGraphicsGetImageFromCurrentImageContext()
        UIGraphicsEndImageContext()
        return image
    }

Using
self.flag_ImgView.image = UIImage(named: country.flag.toImage())

Thank you so much for your response.
On Fri, 23 Jul 2021 at 1:58 PM, Ahmad Almasri @.***>
wrote:

@cnfuzedRk62 https://github.com/cnfuzedRk62 we use flag as emoji for
lite storage and size
you can use this extension to convert flags to UIImage
extension String {
func toImage() -> UIImage? {
let size = CGSize(width: 24, height: 24)
UIGraphicsBeginImageContextWithOptions(size, false, 0)
UIColor.white.set()
let rect = CGRect(origin: .zero, size: size)
UIRectFill(CGRect(origin: .zero, size: size))
self.draw(in: rect, withAttributes: [.font: UIFont.systemFont(ofSize: 24)])
let image = UIGraphicsGetImageFromCurrentImageContext()
UIGraphicsEndImageContext()
return image
}
Using
self.flag_ImgView.image = UIImage(named: country.flag.toImage())
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ahmedAlmasri/DialCountries/issues/1#issuecomment-885484124,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMNAVQZQCZFEDWCQXLZSUADTZER2BANCNFSM5A3QAQTQ
.

@cnfuzedRk62 You are welcome, I will close this issue

Sure
On Fri, 23 Jul 2021 at 2:02 PM, Ahmad Almasri @.***>
wrote:

@cnfuzedRk62 https://github.com/cnfuzedRk62 You are welcome, I will
close this issue
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ahmedAlmasri/DialCountries/issues/1#issuecomment-885486463,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMNAVQ7TEIHAFK6WPQOLTWLTZESK3ANCNFSM5A3QAQTQ
.


Fix Renovate labels on major updates

Tell Renovate to add the MAJOR-UPDATE label to the other labels for major
package updates, rather than replacing the default list of labels.
In addition, Renovate renamed the preset with the recommended settings from
base to recommended, so change the config to use the new name.

#3460  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


test: get integration tests working

Signed-off-by: Sean Tedrow<EMAIL_ADDRESS>

I'm merging because I don't think @Sean-Tedrow-LB is able to sign his previous commit after I clicked "Update branch" on GitHub. Will make sure to not click that button going forward unless commits are already signed.


Feature/interface

Сhanges in this pr completely change the interface of interaction with the SDK
The newBandwidthKit file contains all the necessary methods and documentation for them.
You can approve the PR if you agree with the following changes or leave a comment

I think this looks great @artemHrebinikChisw, thanks!


Tabby cat

[If your PR is related to a contribution to the taxonomy, please, fill
out the following questionnaire. If not, replace this whole text and the
following questionnaire with whatever information is applicable to your PR.
https://github.com/instructlab/taxonomy/issues/798
Describe the contribution to the taxonomy

...
...
...

Input given at the prompt

   ...

Response from the original model

  ...

Response from the fine-tuned model

  ...

Contribution checklist

[ ] The contribution was tested with ilab generate
[ ] No errors or warnings were produced by ilab generate
[ ] All commits are signed off (DCO)
[ ] The qna.yaml file contains at least 5 seed_examples
[ ] The qna.yaml file was linted and prettified (yaml-validator can do both)
[ ] An attribution.txt file in the same folder as the qna.yaml file
[ ] Content does not include PII or otherwise sensitive or confidential information
[ ] Content does not include anything documented in the project's Avoid these Topics guidelines
](https://github.com/instructlab/taxonomy/issues/798)

I've merged your qna.yaml with another tabby_cat qna.yaml and the new PR is here
https://github.com/instructlab/taxonomy/pull/1118

Closing per https://github.com/instructlab/taxonomy/pull/1118.


Restore test_computation_in_grpby_columns and test_struct_self_join

Fixes #5286.
Now that rapidsai/cudf#10717 is fixed, we can re-enable the tests that were disabled in #5288.

build


Ratking rats (pipe crawling abuse)

Ratking rats can attack people while in pipes.

reproduce by spawning rat while in pipe. Let it loose

this bug, with NPC system, where attacking is forced, what ignores containers. Someone on wizdens fixed this, but his pr rejected, i take his pr later


Update validate-notebooks.yml

Removed cached dependencies

Took 47 min to run so might need to consider if we want this

I don't like a build that takes 47min to run. What was the point of eliminating the caching?

@jpfairbanks Using cached versions caused the notebook tests to fail.  We could remove notebook tests altogether, or make smaller ones.  @Saityi

I think we may be seeing inconsistently failing builds when the cache is hit @jpfairbanks Specifically, IJulia seemingly fails to compile. I was encountering this issue a bit when first setting up the regression tests and thought I'd solved it.
40d0f9c5a0/cache.tzst -P -C /home/runner/work/StockFlow.jl/StockFlow.jl --use-compress-program unzstd
Cache restored successfully
Cache restored from key: Linux-test-julia-cache-83b2336a22a63ff57c0c2514ad1fd293f2b50aae8f35340d1b278652a2d186b7

[...]

ERROR: The following 1 direct dependency failed to precompile:

IJulia [7073ff75-c697-5162-941a-fcdaad2a7d2a]

Failed to precompile IJulia [7073ff75-c697-5162-941a-fcdaad2a7d2a] to "/home/runner/.julia/compiled/v1.9/IJulia/jl_m8mJqv".
ERROR: LoadError: ArgumentError: Path to conda environment is not valid: /home/runner/.julia/conda/3/x86_64

I've tried disabling the precompiling altogether, but that just punts the failure to another location because it compiles before running notebooks.
What we're trying to do is validate the notebook examples as part of CI to 1. detect regressions using real examples and 2. validate that the notebook examples -- which are important because we expect they'd useful to prospective users -- are always in working order. We've struggled to get the build both efficient and consistent, though. Caching improves efficiency, but leads to consistency issues, where the cached state is sometimes missing something it needs and we see stuff like the above or 'No such kernel named julia-1.9'; no caching is consistent, but takes an inordinate amount of time. I've hit the limit of my Julia & Jupyter Notebook knowledge, though, and I'm not sure how to move forward.
Options I was thinking about include:

Spending more time hitting my head against the wall hoping I can figure out how to set up caching for Julia+Notebooks. I'm not sure at all what's missing here.
Creating a more self-contained 'examples' module for CI which contains the notebook examples but runs in CI with standard dependencies for StockFlow.jl (no more IJulia issues)

This introduces a difficulty in keeping the two in sync, so I'm less inclined towards this option

Creating a 'smoke test' module that hits all of the features used in the notebooks and papers, but isn't the actual examples or in a notebook
Setting the notebook validation to only run before merges or on manual triggers
Converting the notebooks examples to simple Julia files à la other AlgebraicJulia libraries I've seen like AlgberaicRewriting and generating docs from them.

I think we do want to keep interactive notebooks around, though.

I haven't had much time to dedicate to StockFlow.jl lately, so thinking about the above options is as far as I've gotten. Maybe you can provide some suggestions / thoughts?

I think another option is to convey the notebooks to Literate.jl examples or Docs pages and then use the standard AlgebraicJulia organization-level CI environments to build the docs. Then if the docs build, we know that the examples are working. How does that sound?

Closed so we don't accidentally merge this


Full End-to-End Guide for Deploying on Sharingan Testnet

Describe the documentation you'd like
A comprehensive, end-to-end guide for deploying on the Sharingan testnet. This guide should be broad and encompass various languages and SDKs, specifically starknet-rs, starknet-js, and starknet-py, among others. The objective of this guide is to provide developers with a clear understanding of how to deploy on the testnet using existing tooling and/or scripts in different languages.
Preferred Format
The guide should be easy to understand and should be formatted as follows:

Introduction: Brief about Sharingan testnet, its applications and its importance.
Pre-requisites: List of things/programs required before the process begins.
Step-by-Step Instructions: A step-by-step process on how to deploy on the testnet.

Section for each language/SDK.
Each step should have a brief explanation of what is happening.
Code snippets for each step where applicable.
Any images or diagrams that can be used to help illustrate the process.

Troubleshooting: Common errors and their solutions.
Conclusion: Final thoughts and a brief about what can be done after the deployment.

Additional context or references
Please include references or links to official resources that provide more detailed information about the Sharingan testnet and the specific SDKs (starknet-rs, starknet-js, starknet-py).
Who can help?
Anyone with experience deploying on the Sharingan testnet using one or more of the SDKs listed above is encouraged to contribute. If you are a developer with experience in one of these areas, please consider sharing your expertise to help create this guide.
Thank you!

can you assign it to me?? I would love to do this

can you assign it to me?? I would love to do this

Let’s go ! Assigned to you

@abdelhamidbakhta I have made the pull request :)

@AbdelStark Can I take this issue ser :)

repository archived in favor of https://github.com/madara-alliance/madara


Unblock dashboard projects page

Here's the error, which comes when you call sdk.getApps after you do sdk.setProviderOrSigner to JSON RPC:

Here's where the error is happening in SDK: https://github.com/nftlabs/nftlabs-sdk-ts/blob/8ce839528f723f9d687885b3656bd1e8e7cf37ba/src/core/module.ts#L221
Which is gotten to from starting at this function:
https://github.com/nftlabs/nftlabs-sdk-ts/blob/8ce839528f723f9d687885b3656bd1e8e7cf37ba/src/core/index.ts#L189
Going through this function:
https://github.com/nftlabs/nftlabs-sdk-ts/blob/8ce839528f723f9d687885b3656bd1e8e7cf37ba/src/core/registry.ts#L29

Here's the blocked code: https://github.com/nftlabs/console/pull/386/files


Updating external-dns image version from 0.8.0 to 0.10.2

/cc @alebedev87
/cc @lmzuccarelli

@Connect2naga - can you investigate why the tests are failing

/cc @arjunrn

@Connect2naga  - good to see all tests passing

/lgtm

/approve


[stable/seq] Add an easy way to set the cache size limit

Is this a new chart
No.
What this PR does / why we need it:
Surfaces the cache.systemRamTarget configuration variable with a reasonably conservative default value for Kubernetes so that users experiencing any instability can tweak the value.
Also updates our recommendations around the resources confiruation.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/lgtm

we continue to get this in production
how do i inject the cache size ratio in the helm chart ? or directly in the k8 deployment ?
[17:08:38 ERR] Cache warmup failed; the system will continue managing cache resources, however this problem indicates critical storage issues and should be investigated
System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at Newtonsoft.Json.JsonTextReader.PrepareBufferForReadData(Boolean append, Int32 charsRequired)
at Newtonsoft.Json.JsonTextReader.ReadData(Boolean append, Int32 charsRequired)
at Newtonsoft.Json.JsonTextReader.ReadStringIntoBuffer(Char quote)
at Newtonsoft.Json.JsonTextReader.ParseValue()
at Flare.MemoryEncoding.Serializer.ReadProperty(JsonTextReader json, List1 properties, List1 values, SharedAssets sharedAssets)
at Flare.MemoryEncoding.Serializer.ReadObject(JsonTextReader json, SharedAssets shared)
at Flare.MemoryEncoding.Serializer.Deserialize(Span`1 documentBytes, SharedAssets shared)
at Flare.Storage.StorageEngine.Get(EventStoreRange range, RetrievalStatistics statistics, CancellationToken cancel, SharedAssets shared)+MoveNext()
at Flare.Cache.SegmentCache.WarmUpSegment(Segment seg, CancellationToken cancelRM, SharedAssets shared)
at Flare.Cache.SegmentCache.WarmUpCache(CancellationToken cancelRM)


Notify user if they need to approve a bootstrap CSR

This adds a notification to the bootstrap process to inform the user when they need to approve a CSR.  It serves two purposes:

Currently if you do bootstrap.sh and then, say, just run-wasi, the kubelet just sits there but all your tests fail because it's waiting on TLS cert approval.  Now the user will have a visual prompt of what they need to do.

In preparation for #318, it provides a point in the output where a test harness can know that the CSR is ready, and can extract the CSR name in order to approve it.

Note that the actual interaction is NOT provided by the kubelet crate, either by logging macros or by println!.  This is because we cannot control the log level on the kubelet crate, and we do not want to use println! in the crate because it could in principle be hosted in a non-console environment.  Therefore instead the kubelet application passes in a callback representing how it would like to notify its users - in our cases via println! again because the justfile logging settings didn't show info messages.

The UI looks like this:

NOTE: To be clear: the prompt does not introduce any new wait into the kubelets; the bootstrap module does not wait for a response to the message.  It is purely informational.

In preparation for #318, it provides a point in the output where a test harness can know that the CSR is ready, and can extract the CSR name in order to approve it.

Non-blocking question on this? If we are expecting a computer to parse this, should we have it in a computer parsable format rather than a human one?

@thomastaylor312 I wondered about having the format more machine-readable. But the primary use is to provide a human with an explanation of what the program is waiting for.  I did wonder about splitting it across two lines e.g.
BOOTSTRAP: blah blah blah, run next line
BOOTSTRAP: the actual command  # easy to parse

but I didn't think that would particularly help with the machine processing case.  Can we think of a format that would work well for both?  If not I'll stick to what I got and RELEASE THE REGEXES.

The closest I can think of is JSON, which is only kinda human readable. So RELEASE THE ~KRAKEN~ REGEXES


Update expected-lite to 0.7.0

https://github.com/martinmoene/expected-lite/releases/tag/v0.7.0

coverage: 59.866%. remained the same
when pulling 66731b05b41c06b9a8f4910754b06667c856fc4a on feature/bump-expected
into af9abc5457b323cc307ad881d5dabb458a9a2c47 on master.


[feat] add slug to object search param.

Summary

add slug to object search param.

Thank you for review @platfowner! now merging...


Don't show color control codes when running on windows

Right now, the unix-style color escape sequences aren't properly interpreted in the output by the windows command prompt. They should probably just be disabled when running on windows.

Hello again @pefoley2. Thanks for reporting this.
So how does Cygwin or gitbash handle this on Windows? This is because the os information will return that is in on Windows yet works in these cases. Good point raising this though, it can be irritating getting malformed characters.

The color codes don't seem to work in the cygwin terminal either, I still get stuff like "+"

Alright thanks for that info.

Okay I personally don't like to run another program in order to fix one, but using ANSICON seems to solve the problem https://github.com/adoxa/ansicon
It seems to work but I haven't tested it extensively.

Or I found some code that can add support, but it's written in C, so I'm not really sure how to implement it into Drive.
https://github.com/mattn/ansicolor-w32.c

@powerunlimited thank you for the reference. I'll take a look at it after Friday once my exams are done.


[Error]Report Error

cheat version: 1.05
windows version: win11 22621.1848

Hi, thanks for reporting.
This is a known issue, it will be fixed in v1.0.6


Close help dialog when the canvas is clicked

@davkal , @bowenli From #1325. Closes the 'Help' dialog when it is open and the background is clicked. I looked for other related dialog windows to see if there needed to be a dedicated action for this, but this was the only one I could find that didn't have this behavior already.

LGTM
and tests! well done.


Add the nginx-route relation and nginx_route charm library

Add nginx-route relation with the nginx_route charm library to handle nginx-route relation in the provider and requirer side.
While the Nginx ingress integrator charm will continue to accept the ingress relation, a warning will now be prepended to the status message for any applications connected via the ingress relation.
Here's an example of the warning message: app [<app-name>] connected via deprecated ingress relation, please update to nginx-route relation

Also still looks like there are 2 failing checks


Added util functionalities to return build actions to Soong layer.

Added a public build-actions struct which can be used to compared with expected build actions data in Soong layer.
Added a public util function so that we can choose specific module build actions to be compared in Soong testing/debugging mode.

Since Colin has provided a patch for adding integration test, abandoned this patch so.


.active class applied to .main-menu li when using custom relative URLs in Menus

I am building a one page site, however there a couple of separate pages (eg Posts page, Archives, 404 etc) that I need to link back to the Home page, not an anchor on that particular page. When using a relative URL with the anchor link, the .main-menu li has an .active class applied to it.
How can this bug be reproduced?

Step one
Create a custom relative link in Menus eg.  /#style-anchor
Step two
Save Menu

What did you expect to happen?
As expected the link behaves as normal, scrolling to it's respective anchor tag on the homepage, and when on a separate page, links back to the anchor on the homepage
What happened instead?
However, when using a relative URL with the anchor link, the .main-menu li has an .active class applied to it.
Please List the Following:

OS & version: Mac OS El Capitan 10.11.6
Node version (node -v) [Node v4+ is required] : v5.1.1
Foundation version (bower list) : 6.2

Include Test Case (if applicable):
http://bossy2.dylanmcleod.net.au/
I've tried removing all custom JS and deactivating plugins.

Might be related to #933

https://github.com/olefredrik/FoundationPress/pull/1032


Stalled"

According to https://wiki.mozilla.org/BugBot#stalled.py the stalled keyword is removed from FIXED bugs, but it's actually removed from all resolved bugs. I find this too aggressive for security bugs since it distorts the apparent progress the teams have made in the weekly reports, and because the way the reports are generated it inflates the historical numbers that then no longer match the output from the previous week's reports.
I would request that the "stalled" keyword be left on the ones resolved DUPLICATE, INCOMPLETE, INVALID, MOVED, and WORKSFORME. Almost all the "stalled" security bugs are created from Socorro reports and have no testcase. INCOMPLETE means we've given up, DUPLICATE is obvious, and WORKSFORME generally means we think the crash signature has subsided. In the latter case, though, sometimes it means the symptoms have shifted and they might be re-linked in the future. Or the bug might be re-opened based on future data. MOVED doesn't mean the bug is any less stalled, just that we're tracking it elsewhere. INACTIVE is essentially a synonym for "stalled" (but I don't think we use it much)
If you want to get fancy:

for WORKSFORME bugs you could look a "testcase" attachment or keyword (note: NOT "testcase-wanted"--do an exact match on the keyword). If those are present it's probably safe to remove the "stalled" keyword on WORKSFORME
for DUPLICATE bugs you could look at the bug it's duplicated to and leave the "stalled" keyword if it's duplicated to a bug with a "stalled" keyword.

It's not worth the effort to get fancy, though. just leave the keyword present for INCOMPLETE, DUPLICATE, and WORKSFORME bugs.
The original FIXED resolution was the right impulse: if we fixed something it's not stalled. It's also safe enough to remove the stalled keyword from definitive resolutions WONTFIX and INVALID.
How strongly do you want to get rid of the "stalled" keywords? Is their presence messing up some stats somewhere, or is it just a matter of "this seems technically incorrect"? If resolved "stalled" bugs are something you definitely want to get rid of across the board then could you limit the script to bugs where cf_last_resolved<3w? Not my preference, but at least the change would fall outside the window of the security bug reports and I wouldn't get alarmed managers and directors asking me why the numbers don't make sense.
Thanks for considering this!