Fix odd spacing in JS challenge

Addresses the JS challenge generator trying to wrap the <ol> element inside of a paragraph (and obviously failing)
Closes #6840

:+1:

FreeCodeCamp/seed/challenges/03-back-end-development-certification/dynamic-web-applications.json


Excise ".NET Aspire app" from training modules

Describe the issue or suggestion
Per email thread, change ".NET Aspire app" to something like ".NET Aspire project" on all training modules

Associated WorkItem - 263795

https://github.com/MicrosoftDocs/learn-pr/pull/45144


Use new FCM APIs

As of now FCM notifications are sent to https://fcm.googleapis.com/fcm/send which is a legacy API.
Messages should be sent to current API endpoint:
https://fcm.googleapis.com/v1/{parent=projects/*}/messages:send

You can change the API Endpoint for FCM by setting an attribute in push notification config as follows,
PUSH_NOTIFICATIONS_SETTINGS = {
    "FCM_API_KEY": "********",
    "FCM_POST_URL": "https://fcm.googleapis.com/v1/projects/{project_id}/messages:send",
     .......
     .......
}

Now what I can suggest is that the default FCM POST URL should be changed to new format by adding a mandatory parameter "PROJECT_ID" in FCM Config

Sorry for my previous replies. I had just started looking into the documents today.
Just now I have found that, for new FCM updates, another way is already implemented in this library. (Thanks to the contributors)
Follow this document here: (Was mentioned as hot-linked in repository's main readme)
https://github.com/jazzband/django-push-notifications/wiki/Multiple-Application-Support

What concern me is that since APIs are different they accept different parameter format.
Looking into Firebase docs seems that API v1 has a different param signature from legacy one.
There is an official guide which explains why just changing URL is not enough.

What concern me is that since APIs are different they accept different parameter format.
Looking into Firebase docs seems that API v1 has a different param signature from legacy one.
There is an official guide which explains why just changing URL is not enough.

Where you able to solve this??

Where you able to solve this??

ATM I do not have time to work on a PR about this issue.
Since Google is still maintaining legacy API (to keep alive many legacy app) this is not an high-priority.
When I have some free time I could try to address this.

This could be accomplished by using official firebase-admin or by using the example code provided by firebase guide.

What concern me is that since APIs are different they accept different parameter format.
Looking into Firebase docs seems that API v1 has a different param signature from legacy one.
There is an official guide which explains why just changing URL is not enough.

First of all, sorry to be not responsive here as it's my secondary github account. Seems like I went for a winter sleep :P
Thanks, @sevdog for pointing the issue with my short reply. Yes, just changing URL is not enough here and actually its not the true solution in any system anywhere.
So AT THAT TIME, how I solved was by overriding few core methods for myself following the official that you had also mentioned in your reply. So I actually had to customize the library on a short notice to meet my deadline. But unfortunately, that was not something to be shared with public or send a PR as well :D
@sevdog , thanks again for your latest suggestion, I will go through this new library as I predict that I will have to work on push notifications soon and quite on a large scale TBH. :D

The legacy API are deprecated from yesterday and will be removed on June 20th 2024

Looking aroud there is this package which implements only FCM: https://github.com/xtrinch/fcm-django/
It can be taken as an example.


Hacktoberfest Contributions

Any useful resource with respect to pentesting and vulnerable machines/environment

Thanks for the contribution during Hacktoberfest !!!


No data in documentation, just title and description

Describe the bug
I have a similar issue like: https://github.com/StydeNet/enlighten/issues/62
Laravel framework is at 9.13.0, Enlighten is at 0.7.3.
The documentation no longer has request and response data in them, just the test's method title and description (if included with a docblock).
To Reproduce
Steps to reproduce the behavior:

Run php artisan enlighten
Run php artisan enlighten:export
Click on any section. It will only show the title and description

Expected behavior
Response and request data should be available when viewing documentation for an endpoint/method

I have the same issues
Here is what I did:

Remove all files in: /resources/views/vendor/enlighten
Re-export views : php artisan vendor:publish --tag=enlighten-views


Suppress RedundantVisibilityModifierRule if explicit API mode enabled

Expected Behavior of the rule

If explicit API mode is enabled:
kotlin {
    explicitApi()
}

Detekt should suppress RedundantVisibilityModifierRule for public modifier.
Context

Explicit API mode was added in Kotlin 1.4
It prevents libraries' authors from making APIs public unintentionally. In this mode, you should explicitly specify the visibility modifier even if it is public.

Looks like it is not fixed in 1.15.0
I've created the minimal project to reproduce this bug.
https://github.com/osipxd/detekt-explicit-api-mode-test

Looks like the value in AnalysisFlags, used to get explicitMode is default value, so it is always DISABLED and AnalysisFlag is immutable.
https://github.com/JetBrains/kotlin/blob/8be23df668be32bad8c23f49f0b9f8feb7cb6cd9/compiler/util/src/org/jetbrains/kotlin/config/AnalysisFlag.kt#L32-L34

Thanks for checking this feature thoroughly.
I scrolled through the version history of the Kotlin compiler. Luckily, I found another possible solution by using another internal function.
Please check out the referenced PR. Thank you!

Thanks for checking this feature thoroughly.
I scrolled through the version history of the Kotlin compiler. Luckily, I found another possible solution by using another internal function.
Please check out the referenced PR. Thank you!


Figs04 05

Figure S05:

Figure S04:

The build fails after 14 seconds... I am not sure what's going on.

Should be fixed. Rerun.

Wow! remarkible!


Add mobile view for tooltip

Reference #461

@algomaster99 take a look at the CodeClimate complaints. Probably some parts could be generalized, deduplicated.

@shcheklein

How this is similar isn't making sense to me.

@algomaster99 codeclimate produces false positives indeed, treat it as warnings/recommendations. If it's clear that it is a false positive, not new or something the is a button per each item to close the issue (Invalid, Not New, etc)

Looks great, thanks @algomaster99
I wasn't really thinking on a typical popup with margins everywhere though, but more of a "frame" design where the tooltip takes the full lower 1/3 (more or less) of the screen, kind of like this:

What do you think? Also the x (to close tooltip) should definitely be larger please, for easier touch.

@jorgeorpinel Might be a great idea but since there is an overlay (translucent black), scrolling won't be possible. I will have to see. Thanks for the suggestion though!

X (close button) - yes, we can make it larger, or write somewhere that touch to any part of the screen closes the message.
@algomaster99 @jorgeorpinel I totally fine with current implementation - it's simple and doing it's job. I've asked @iAdramelk to review as well. As soon as it's done will be happy to merge.
@algomaster99 please, create a ticket to refactor hard coded constants.

@algomaster99 it looks like styles are broken, inline code sections do not work in the mobile view. I haven't checked other stuff.

@shcheklein which sections? I don't get you. Can you also share a screenshot?

@algomaster99

@shcheklein Oh okay. I don't know why that isn't working. I am confused too. :confused:

@shcheklein Oh okay. I don't know why that isn't working. I am confused too. 😕

I think that this is because it is now rendered outside of markdown component. You need to add className="markdown-body" to the markdown root, to make global markdown styles work.

@iAdramelk
I added markdown-body to <ReactMarkdown className="markdown-body" source={this.props.description} /> which fixes the styles of inline-code but removes the font.

Should I add another style, something like .portal and hardcode the font-family there?

Should I add another style, something like .portal and hardcode the font-family there?

@lgomaster99  yep, I think we need to add second class with font here. Not sure about the name through. I think portal and it's content should be separate entities:

Portal is just a mount point where we can add arbitrary html. It shouldn't have it's own styles.
Tooltip visual styles that can be reused between desktop and mobile version. In perfect world they didn't have ant position logic inside and can be placed anywhere.
Tooltip positioning logic. It can be either separate, or the part of the unified tooltip component.

In this logic font is a part of the Tooltip visual styles and should be placed near them.

@shcheklein This can be merged now. 💯


Fetch results from the scorecard API

Rather than cache scores from the BQ dataset to a database, we could fetch them from the API instead:
https://api.securityscorecards.dev
This will definitely be slower but has a number of benefits:

Scores will be up-to-date
We don't need the overhead of constructing and pulling the database
We don't need to make sacrifices in terms of the amount of information we cache in order to keep the database a manageable size

One thing to keep in mind is that this would end up shipping off the names of private repositories if there are any in the BOM. The only way I can think to mitigate that would be to check if the repo is public before making the call.

Done. Scores are fetched from the API. We check if a repo is public before calling the scorecard API.


Multi-Sig Wallet support.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I'm looking for multi-sig transactions as it comes with polkadot blockchain.
Describe the solution you'd like
A clear and concise description of what you want to happen.
can you guys enable multi-sig transactions & you can easily open this on https://staging.opentensor.ai/#/accounts
so I can easily test?
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Once testing is complete then we can move multi-sig on deployment. as multi-sig is already in the explorer cloned from polkadot.
Additional context
Add any other context or screenshots about the feature request here.

Regards
Ehti & @hueymahl

As a little more context, we are developing an opens-source multi-sig wallet using the polkadot tools that can be used by the community at large.  We have a specific need for one, but want to donate our work to the cause.
Currently we have created the wallet and it is partly functional - we can send tao to it but we can't send from it.  To send from the multi-sig wallet, or stake/unstake to a hotkey, we believe we need for multi-signature calls to be enabled on bittensor.

Closed as this issue is for https://github.com/opentensor/subtensor


it is possible to flash inside a ESP32 Basic Core

I ran the following commands
git clone --recursive https://github.com/Blockstream/Jade.git $HOME/jade
cd $HOME/jade
cp configs/sdkconfig_jade.defaults sdkconfig.defaults
idf.py flash monitor

But I'm not able to boot after the fash my ESP32 Basic Core https://shop.m5stack.com/products/esp32-basic-core-iot-development-kit-v2-6
I keep receiving the following info
Writing at 0x00124122... (79 %)
Writing at 0x0012bbe2... (81 %)
Writing at 0x001362da... (83 %)
Writing at 0x0013dd30... (85 %)
Writing at 0x00143670... (87 %)
Writing at 0x001490c3... (88 %)
Writing at 0x001509b0... (90 %)
Writing at 0x001565cb... (92 %)
Writing at 0x0015bda3... (94 %)
Writing at 0x0016173f... (96 %)
Writing at 0x00166d17... (98 %)
Writing at 0x0016c69f... (100 %)
Wrote 1437664 bytes (875724 compressed) at 0x00010000 in 21.5 seconds (effective 534.9 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 126...
Writing at 0x00009000... (100 %)
Wrote 3072 bytes (126 compressed) at 0x00009000 in 0.1 seconds (effective 374.7 kbit/s)...
Hash of data verified.
Compressed 8192 bytes to 31...
Writing at 0x0000e000... (100 %)
Wrote 8192 bytes (31 compressed) at 0x0000e000 in 0.1 seconds (effective 492.8 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...
Executing action: monitor
Serial port /dev/ttyUSB3
Connecting....
Detecting chip type... Unsupported detection protocol, switching and trying again...
Connecting.......
Detecting chip type... ESP32
Running idf_monitor in directory /home/vincent/Github/Jade
Executing "/home/vincent/.espressif/python_env/idf4.4_py3.10_env/bin/python /home/vincent/Github/Jade/tmp/esp-idf/tools/idf_monitor.py -p /dev/ttyUSB3 -b 115200 --toolchain-prefix xtensa-esp32-elf- --target esp32 --revision 1 /home/vincent/Github/Jade/build/jade.elf -m '/home/vincent/.espressif/python_env/idf4.4_py3.10_env/bin/python' '/home/vincent/Github/Jade/tmp/esp-idf/tools/idf.py'"...
--- idf_monitor on /dev/ttyUSB3 115200 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0138,len:1496
load:0x40078000,len:14572
ho 0 tail 12 room 4
load:0x40080400,len:2956
0x40080400: _init at ??:?

entry 0x400805d4
ets Jul 29 2019 12:21:46

rst:0xc (SW_CPU_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0138,len:1496
load:0x40078000,len:14572
ho 0 tail 12 room 4
load:0x40080400,len:2956
0x40080400: _init at ??:?

I'm doing something wrong? or it is not possible to use the firmware inside the https://shop.m5stack.com/products/esp32-basic-core-iot-development-kit-v2-6

You're using the Jade hardware config file, use M5 black instead. Change third command to:
cp configs/sdkconfig_display_m5blackgray.defaults sdkconfig.defaults

Mh, yeah I tried also this during my install experience but I keep receiving the following error
Running idf_monitor in directory /home/vincent/Github/Jade
Executing "/home/vincent/.espressif/python_env/idf4.4_py3.10_env/bin/python /home/vincent/Github/Jade/tmp/esp-idf/tools/idf_monitor.py -p /dev/ttyUSB3 -b 115200 --toolchain-prefix xtensa-esp32-elf- --target esp32 --revision 3 /home/vincent/Github/Jade/build/jade.elf -m '/home/vincent/.espressif/python_env/idf4.4_py3.10_env/bin/python' '/home/vincent/Github/Jade/tmp/esp-idf/tools/idf.py'"...
--- idf_monitor on /dev/ttyUSB3 115200 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0138,len:1496
load:0x40078000,len:14572
ho 0 tail 12 room 4
load:0x40080400,len:2956
0x40080400: _init at ??:?

After you cp configs/sdkconfig_display_m5blackgray.defaults sdkconfig.defaults, you may need to also:
rm sdkconfig
idf.py fullclean

just to make sure any files created with the inappropriate config are cleaned.

Oh, looks like that I ran the opposite commands
idf.py fullclean
rm sdkconfig

Now worked, thanks

I just managed to find my M5 'basic' (black base/body)  which I think is similar and that worked with latest master - so cool - should all be working then.
Many Thanks, closing this item.


HA Sentence Wildcards Stops Willow

I have tested this a few times, but it appears that when I try to call an automation in HA via a wildcard sentence, {lists},  willow is unable to perform/access the intent.  I am on Willow 0.1.1 and HA 2023.8.4.  When I remove the wildcard automation, Willow goes back to working as intended

Willow sends the transcription as-is to Home Assistant and gets the response of whatever it does. Willow has nothing to do with specific parsing of intents, transcripts, commands, actions, etc.
Have you tried it in Home Assistant? You can click the Assist icon in the type right corner of the web interface. Type in your commands as they are transcripted. This way you can debug your intents without having to speak to Willow. When they're configured properly you can speak to Willow and we'll send the transcript that should match your intent , with the outcome being identical to typing it in the web interface.

Ok it appears to be a HA issue. I am trying to capture the whole sentence, but doesn't seem to want to allow me to do that


How does packing work for non-MPT models?

I have noticed that llm-foundry has a data collator for packing short examples into one training instance to reduce waste on padding. This relies on 3-d attention mask to make sure it equal to training with separate instances.  However, 3d attention mask is not supported by HuggingFace Transformers' model implementations.
I wonder when I use llm-foundry for training llama2, falcon, and mistral, does llm-foundry automatically replace the attention implementation to support 3d attention mask or that's something we need to implement by ourselves.
Also does the data collator work for SFT where we have prompts and responses?

Your understanding is correct. We do not create a 3d attention mask for llama, mistral, etc. For MPT, you can control this behavior with the attn_uses_sequence_id argument. In practice it seems to be ok to train with packed sequences without the 3d mask, although I'd be happy to hear about any experience you have with and without the extra masking!
The data collator does work for SFT with prompt/response, yes.

Thanks for confirming. I guess in order to make it work for llama, we will need to implement something similar to what you have done for MPT to support attn_uses_sequence_id. I will share our findings and code once it's done.

Hi @dakinggg, a relevant question, when I set packing_ratio=2, the data loader fetches 2 x per_device_batch_size examples for each device batch. What happens to those overflow examples / tokens? Do we just drop them?

I have tried training without 3d attention mask on very short examples. Packing ratio is > 100. The train loss didn't converge.

When you set packing ratio, yes it will concatenate samples together. As for convergence, there could be many things that affect this. We haven't seen any issues with sequence packing not converging. One thing is that if you don't change any other hyperparameters, sequence packing means you have (many) more tokens per batch than before, so a different learning rate may be required.

When you set packing ratio, yes it will concatenate samples together. As for convergence, there could be many things that affect this. We haven't seen any issues with sequence packing not converging. One thing is that if you don't change any other hyperparameters, sequence packing means you have (many) more tokens per batch than before, so a different learning rate may be required.

You are right...  I needed to train the model for a few more steps with a larger LR. Thanks for the help.

I have implemented the 3d attention mask for Mistral. (basically adding sequence_id support)
It seems 3d attention mask does help. Please see the below plots.

(The eval set is a subset of train set with packing ratio = 0 for infra validation purposes)
Also, I had to switch to<EMAIL_ADDRESS>in order to my patch to work. Otherwise, the loss won't converge.

I'd be curious to know if that model is actually better. It looks like your dataset was pretty easy and the model got it completely (0 loss). It seems reasonable that the packed, non masked version would converge to not quite 0, since it can't predict the first token after an eos. But the models may be pretty much identical otherwise.

In this new experiment, train eval set doesn't overlap the train set. In this way, we test the model's generalization capability w/ or w/o 3d attention mask. Indeed, the model is not actually better with attention mask.

Closing as I think the question has been answered. Fell free to open a new issue if you have more questions!


rewrite Community class and internal data handling

this is a rewrite of the community class, as discussed here, to be more lightweight and transparent. I also renamed a few functions for clarity and changed the way the internal data handling works. Should be a lot more efficient this way
tests are passing locally, but i am having trouble getting the quilt stuff stable on travis

Have you tried add numpy to the environment.yml?

The new way Travis is setup, it is only using the requirements files and not even reading the environment.yml


Article not consistent

Dear Sir,
After create a Azure Bot.
To add the user-assigned managed identity to your bot's web app:

Go to the app service page for your bot's web app.
There is no app service found.

If I do publish through Bot Framework Composer, it will create a app service.
But create from Azure Portal, there is no app service created.

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

ID: 7cf57ecf-7774-8f8b-1e47-cf628c3bfa25
Version Independent ID: ba30559c-36df-69c6-2703-cd67aa1380c2
Content: Create an Azure Bot resource in the Azure portal - Bot Service
Content Source: articles/v4sdk/abs-quickstart.md
Service: bot-service
GitHub Login: @JonathanFingold
Microsoft Alias: iawilt

create app service manually.


Is it possible to generate a table sorted in month?

Like: https://dants.github.io/index_sysvenues_deadline.html

The table cells appear really nice, we may call for some maintainers for an implementation in a near future.


libiconv:x64-windows build failure

Host Environment

OS: Windows
Compiler: MINGW64 CMake

To Reproduce
Steps to reproduce the behavior:
./vcpkg install cairo --triplet x64-windows
Failure logs
Error: Building package libiconv:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: libiconv:x64-windows
Vcpkg version: 2021-05-05-9f849c4c43e50d1b16186ae76681c27b0c1be9d9
Additional context
I'm following instructions from here: https://github.com/cpp-io2d/P0267_RefImpl/blob/master/BUILDING.md

Please attach the failure logs :)

@AaronVanCuren
Can you provide the error info here?

Closing this issue for now since inactive thread. Please feel free to reopen this issue if it is sill a problem for you.
Note: Please update to the latest vcpkg to rebuild. If still failed, please provide the error log.


[#530] Usage message customization

Added support to flexible usage message building (see issue #530):

[new] customizable Help object injectable through CommandLine.helpFactory(IHelpFactory)
[new] customizable usage message sections definition and ordering through List<ISectionRenderer> Help.sections()
[refactoring] customizable usage message members (headings, argument lists, ...) through their respective renderers (existing hard-coded rendering blocks have been encapsulated into the new objects and existing Help entry points have been wired back)

(no test added yet -- waiting for your considerations about this implementation)

Thanks! Limited internet connectivity now. Will try to review this week.

Perhaps a good way forward is to split this work. Can you provide a PR of more limited scope to address the first two points:

allow injecting customizable Help object through IHelpFactory
allow reordering and course-grained customization of help sections with List<ISectionRenderer> Help.sections()

We already agreed these would be good changes so I imagine this can be merged fairly quickly.
After that we can take another look at potential further improvements.
Thoughts?

Looking back at my initial feedback I realize now that it doesn't sound very friendly. Apologies, that was not intended. Are you still interested in helping to improve this area?

Looking back again my initial feedback doesn’t look that unfriendly.  Bit worried about not getting a response. I hope you’re okay.
If you’re not interested in working on this further just give a shout.

Hi, sorry for my late reply: I had to move accordingly to my requirements, so I couldn't amend my proposal in the meantime.
I fully understand your observations (my redundant interfaces were an intermediate step toward the full modularization of the rendering elements), but at this point my implementation has nonetheless incompatibly diverged: I can keep alive my PR branch if you want to pick some of it, but I'm not gonna accomodate your request, sorry.

@stechio I wanted to thank you again for pointing out that in picocli-3.7/3.8 the usage help message customizability was not great. Thanks to your ideas, proposals and discussions, picocli-3.9.0 has just been released with significant improvements in this area. Your name is mentioned in the release notes to reflect this.
I believe tickets like this one already prove how useful these improvements are.
I'm going to close this PR now since I think we have gotten as much value out of it as we can.
Again, many thanks, and please feel free to suggest further improvements!


Avoid MultiPartParser silent large headers failures

Allow the multipart chunk's http headers field size to be up to 8192 bytes. Make the MultiPartParser raise MultiPartParserError if the limit is exceeded.
note: The problem has been spotted earlier https://stackoverflow.com/questions/70572148/django-silently-discarding-uploaded-files-with-long-paths

Hi @opichals 👋
Thanks for the patch. Is there an accepted ticket on trac for this? I couldn't see one.
https://code.djangoproject.com/
Also, adding a setting is also a little controversial. If a ticket is accepted I think considerations of other solutions would be needed and consensus would need to gained from the community (likely through discussion on the forum) before a setting can be added.

Hi @opichals 👋
Thanks for the patch. Is there an accepted ticket on trac for this? I couldn't see one.

I couldn't find any either. Just the stackoverflow article. Also I have hit this bug in our production app.

https://code.djangoproject.com/
Also, adding a setting is also a little controversial. If a ticket is accepted I think considerations of other solutions would be needed and consensus would need to gained from the community (likely through discussion on the forum) before a setting can be added.

Fair, I am ready to make the max value say 8192 and then separate the commit introducing the settings for it but I think the current value 1024 is just too small and therefore I added it.
The naming is derived from multiple occurrences in other OSS so it is google searchable:

https://github.com/openstack-archive/deb-python-eventlet/blob/master/eventlet/wsgi.py
https://github.com/i2p/i2p.i2p/blob/master/apps/i2ptunnel/java/src/net/i2p/i2ptunnel/I2PTunnelHTTPServer.java
https://bugs.launchpad.net/keystone/+bug/1098177

@smithdc1 Dropped the settings. Made the maximum limit 8192.

@opichals Thanks :+1: Welcome aboard :boat:
Let's move it forward.


WRO-4973: Fix wrong ilib path when locales option is 'all'

Checklist

[x] I have read and understand the contribution guide
[ ] A CHANGELOG entry is included
[ ] At least one test case is included for this feature or bug fix
[x] Documentation was added or is not needed
[ ] This is an API breaking change

Issue Resolved / Feature Added
Fixed the incorrect behavior found in the automation test.
Locals no longer exist under @enact/i18n after Enact v3.0.0 and are located on the iLib module.
For the "--locales=all" option to work correctly, the directory of the locales must be redirected.
Resolution
Redirect the directory from @enact/i18n to ilib.
Additional Considerations
Links
WRO-4973
Comments
Enact-DCO-1.0-Signed-off-by: Taeyoung Hong<EMAIL_ADDRESS>

Please put the change log.

Please put the change log.

OK


FW: On failsave plane tumbled and rolled some times

Which failsafe was this? Please attach the log once we have it.

This has been hunted down to manual override in RTL, which is fixed on the release branch.


Add ownCloud (or webDav) support

There are some public services offering ownCloud access (https://owncloud.org/providers/)
It is also self hosted and imho the best opensource cloud.
https://github.com/bnoffer/owncloud-sharp
There is great library for c#

Looks ok at first inspection.
You wouldn't know if one of the listed providers offers >= 10GB free storage space quota as listed in the CloudFS prerequisites?

I don't know, I'm hosting it at myself.
But I'll take a look

https://www.tucloudserver.com/console/cart.php?gid=6
This one is :D

Hi @JuniorJPDJ,
I just committed preliminary WebDAV support with 23195b17 on a feature branch if you'd like to take an early look. The WebDAV gateway completed the CloudFS test suite successfully on a non-OneCloud hoster (German Telekom MagentaCloud) and a public OneCloud-based hoster from your list (oCloud.de).
I'm not ready to release this code just yet because the login credentials can't be persisted until the config encryption feature requested in https://github.com/viciousviper/DokanCloudFS/issues/17 is in place - which means that you'll have to re-authenticate via the login form each time the WebDAV gateway is instantiated.
However, I'd certainly value your feedback on the general suitability of the WebDAV gateway for self-hosted OneCloud environments.
BTW, apparently none of WebDAV interfaces of the large cloud providers implements quota information via quota-available-bytes and quota-used-bytes while the OCloud-based provider did. Is there another established quota scheme I should support or do they just suck?

Fixed in ef512681.


Changes by create-pull-request action

Automated changes by create-pull-request GitHub action

Codecov Report

Merging #10 (3939019) into main (95ff1af) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #10   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            7         7
  Lines          287       287
=========================================
  Hits           287       287

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Add swap to memory module

I just moved over from i3status-rs and love waybar.
The one thing I miss is out-of-the-box swap support along with RAM stats. With memory-hungry stuff I'm used now to keep an eye on the free sway. I can certainly make a simple custom module, but since the infrastructure if all there (at least for linux. No idea about BSD), I think it might be a nice addition.

So, you want to see swap usage separately, don't you?

Yep.
Though, what do you mean, "separately"? Is it now included in something? A search for "swap" in the wiki doesn't give results

I asked whether it should be calculated as a part of RAM on not.
I think I can add in memory module the same options as now for RAM. E.g swap-available.

That would be great!
M.
10 Aug 2021 10:20:05 Anakael @.***>:

I asked whether it should be calculated as a part of RAM on not.
I think I can add in memory module the same options as now for RAM. E.g
swap-available.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on
GitHub[https://github.com/Alexays/Waybar/issues/1156#issuecomment-895830055],
or
unsubscribe[https://github.com/notifications/unsubscribe-auth/AAXOOKMLKS24EHSGGNH6ARLT4DOLJANCNFSM476XGIPA].
Triage notifications on the go with GitHub Mobile for
iOS[https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675]
or
Android[https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email].
[data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAEIAAABCCAYAAADjVADoAAAAAXNSR0IArs4c6QAAAARzQklUCAgICHwIZIgAAAAnSURBVHic7cEBDQAAAMKg909tDwcUAAAAAAAAAAAAAAAAAAAAAPBjRFIAASHKmKkAAAAASUVORK5CYII=###24x24:true###][Tracking
image][https://github.com/notifications/beacon/AAXOOKK7OENYSULIGQFJBE3T4DOLJA5CNFSM476XGIPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGVSUQJY.gif]

Can you check https://github.com/Anakael/Waybar/tree/pr/anakael/add-swap-flags ?
If it works fine, I'll open PR.

@Anakael I have tried it in my machine, it looks well, can you merge it into mainilne?
Thanks.

Could an icon for swap be added as well?
In my build, I am just doing it like this:
sed -i 's/fmt::arg("icon", getIcon(used_ram_percentage, icons)),/fmt::arg("icon", getIcon(used_ram_percentage, icons)), fmt::arg("iconswap", getIcon(used_swap_percentage, icons)),/g' src/modules/memory/common.cpp


CPX31 "big" instances getting created and deleted by itself

Heya! Back again with another issue.
I created my cluster last week, and I was wondering why I couldn't see the "big" CX31 instances, but I continued on with my day. Today I received an email about this new instance being created and how to access it, but when I went into the Hetzner UI , nothing was to be seen.
Few hours later and I receive a new message about it being created and available, and I got into the UI and I can see it! Then shortly after the big machine are deleted.
I have not run the hetzner-k3s tool, so i'm wondering how all of this is happening. Any clue?
This is the config i'm using:
masters_pool:
  instance_type: cpx21
  instance_count: 3
  location: nbg1
  # labels:
  #   - key: purpose
  #     value: blah
  # taints:
  #   - key: something
  #     value: value1:NoSchedule
worker_node_pools:
- name: small
  instance_type: cpx21
  instance_count: 4
  location: nbg1
  # labels:
  #   - key: purpose
  #     value: blah
  # taints:
  #   - key: something
  #     value: value1:NoSchedule
- name: big
  instance_type: cpx31
  instance_count: 2
  location: nbg1
  autoscaling:
    enabled: true
    min_instances: 0
    max_instances: 3

Hi! That's normal with autoscaling enabled. Depending on the resources required the cluster might create or delete the servers but it also can move pods around where there is capacity to try and remove excess nodes. By default the auto scaler removes nodes that have been underused for 10 minutes straight. You can see a little weird creating and deleting more often than normal if you don't have cpu and memory requests for some workloads. Is that the case? What are you running in the cluster?

Also, now that I remember, I fixed a problem with autoscaling in the second most recent release. Which version are you using? If not the latest then run the create command again because it will upgrade the auto scaler to the latest version.

Ah I see and it makes sense. So I see that all my worker nodes are fully utilized even though nothing is happening it basically causes my whole infrastructure to crash. I cannot access the domains until the usage has dropped again.
I saw it happen a few days ago where one worker node was utilized to the max, and then suddenly nothing worked but all the other worker nodes were almost idle.
Not really sure what causes it to spike like this out of the blue.
As a reference: I'm building a service, but there's no users of it yet as I haven't officially launched yet.

The master nodes are almost idling. Here's an example

I'm on 1.0.1 - it doesn't seem like there's an issue with your autoscaler.

Also it might be worth noting that even though the autoscaler spins up an extra instance, that instance is pretty much idle 1-5% CPU usage. Again, i'm a bit confused on what caused this spike and caused the cluster to stop responding.

Alright I think this is what's causing the high CPU usage possibly.
alertmanager-prometheus-kube-prometheus-alertmanager-0   2/2     Running             1 (2m2s ago)    2m4s
deploy-internalproxy-5bf45d8ff7-9znfv                    1/1     Running             0               9m24s
deploy-internalproxy-5bf45d8ff7-dqmzb                    1/1     Running             0               9m24s
deploy-internalproxy-5bf45d8ff7-jgkgw                    1/1     Terminating         0               19m
deploy-internalproxy-5bf45d8ff7-kss9s                    0/1     Terminating         0               15m
deploy-internalproxy-5bf45d8ff7-l5v28                    1/1     Running             0               9m24s
deploy-internalproxy-5bf45d8ff7-mmhw4                    0/1     Terminating         0               148m
deploy-internalproxy-5bf45d8ff7-mrgxp                    1/1     Terminating         0               168m
deploy-internalproxy-5bf45d8ff7-n5hfs                    1/1     Terminating         0               19m
deploy-internalproxy-5bf45d8ff7-pkw56                    1/1     Terminating         0               155m
deploy-internalproxy-5bf45d8ff7-qx68z                    1/1     Running             0               9m24s
deploy-internalproxy-5bf45d8ff7-rj7kv                    0/1     Terminating         0               148m
deploy-internalproxy-5bf45d8ff7-tqmx8                    0/1     Terminating         0               15m
deploy-loki-deployment-cd6d9c94b-jzjnr                   1/1     Running             0               9m24s
deploy-loki-deployment-cd6d9c94b-nvbhw                   1/1     Terminating         0               168m
deploy-loki-deployment-cd6d9c94b-rxppp                   1/1     Terminating         0               19m
django-backend-deployment-5d5dd58fbf-5s67s               1/1     Running             0               9m23s
django-backend-deployment-5d5dd58fbf-7jh6h               1/1     Terminating         0               19m
django-backend-deployment-5d5dd58fbf-bm74c               1/1     Running             0               9m23s
django-backend-deployment-5d5dd58fbf-czppz               1/1     Terminating         0               168m
django-backend-deployment-5d5dd58fbf-h6dxr               0/1     ContainerCreating   0               9m24s
django-backend-deployment-5d5dd58fbf-rg6r2               0/1     Terminating         0               15m
django-backend-deployment-5d5dd58fbf-vwtz5               0/1     Terminating         0               148m
django-backend-deployment-5d5dd58fbf-w8fvm               0/1     Terminating         0               148m
django-backend-deployment-5d5dd58fbf-wdqcn               0/1     Terminating         0               15m
django-celery-beat-deployment-779cd594cb-b76c5           1/1     Terminating         0               168m
django-celery-beat-deployment-779cd594cb-dnqp6           1/1     Terminating         1 (16m ago)     19m
django-celery-beat-deployment-779cd594cb-jdtcm           1/1     Running             0               9m22s
django-celery-deployment-85c747f96f-7pqq6                0/1     Terminating         0               15m
django-celery-deployment-85c747f96f-89f6f                1/1     Terminating         1 (16m ago)     19m
django-celery-deployment-85c747f96f-8f9cg                1/1     Terminating         0               28m
django-celery-deployment-85c747f96f-92bbh                1/1     Running             0               9m25s
django-celery-deployment-85c747f96f-kp8fj                1/1     Terminating         0               168m
django-celery-deployment-85c747f96f-ml5jr                1/1     Terminating         2 (27m ago)     36m
django-celery-deployment-85c747f96f-plt7f                0/1     Terminating         0               148m
django-celery-deployment-85c747f96f-tsmvh                1/1     Terminating         1 (16m ago)     19m
django-celery-deployment-85c747f96f-tvxdt                1/1     Running             0               9m23s
django-celery-deployment-85c747f96f-w6wlj                0/1     Terminating         0               148m
django-celery-deployment-85c747f96f-znqsd                1/1     Running             0               9m23s
django-celery-yagna-deployment-c7889788b-2bk9h           0/1     Terminating         0               148m
django-celery-yagna-deployment-c7889788b-4pgdc           0/1     Running             0               9m24s
django-celery-yagna-deployment-c7889788b-6l66l           0/1     Terminating         3 (150m ago)    168m
django-celery-yagna-deployment-c7889788b-7swbx           0/1     Terminating         1 (21m ago)     28m
django-celery-yagna-deployment-c7889788b-7zbcf           0/1     Terminating         0               15m
django-celery-yagna-deployment-c7889788b-92g7w           0/1     Terminating         0               19m
django-celery-yagna-deployment-c7889788b-hr7cv           0/1     Terminating         0               15m
django-celery-yagna-deployment-c7889788b-lqn59           0/1     Running             0               9m24s
django-celery-yagna-deployment-c7889788b-ndn9q           0/1     Running             0               9m24s
django-celery-yagna-deployment-c7889788b-rfqkn           0/1     Terminating         0               148m
django-celery-yagna-deployment-c7889788b-z8ch4           0/1     Terminating         0               36m
funding-service-deployment-56d9f866b6-d6q4n              0/1     Terminating         0               148m
funding-service-deployment-56d9f866b6-gzkfn              1/1     Terminating         0               19m
funding-service-deployment-56d9f866b6-qzbfs              1/1     Running             0               9m24s
metrics-server-7bf7496f67-52sn6                          0/1     Terminating         0               15m
metrics-server-7bf7496f67-5qds4                          0/1     Running             0               9m24s
metrics-server-7bf7496f67-x856t                          0/1     Terminating         0               148m
pgadmin-deployment-86d84859db-tx4p9                      1/1     Terminating         0               148m
pgadmin-deployment-86d84859db-v9l59                      0/1     Terminating         0               15m
pgadmin-deployment-86d84859db-w9dl8                      1/1     Running             0               9m23s
prometheus-grafana-795c877745-8z4pp                      2/3     Running             0               9m23s
prometheus-grafana-795c877745-nxfbv                      0/3     Terminating         0               15m
prometheus-grafana-795c877745-vwclk                      3/3     Terminating         0               168m
prometheus-kube-prometheus-operator-7679f7fddb-4zt6s     0/1     Terminating         0               148m
prometheus-kube-prometheus-operator-7679f7fddb-8c57k     0/1     Terminating         0               15m
prometheus-kube-prometheus-operator-7679f7fddb-hz9cz     1/1     Running             0               9m24s
prometheus-kube-state-metrics-675b965b4c-lzlth           1/1     Terminating         0               168m
prometheus-kube-state-metrics-675b965b4c-qgk48           1/1     Terminating         0               19m
prometheus-kube-state-metrics-675b965b4c-sxpvr           1/1     Running             0               9m24s
prometheus-prometheus-kube-prometheus-prometheus-0       2/2     Running             0               114s
prometheus-prometheus-node-exporter-8n95v                1/1     Running             6 (14m ago)     4d
prometheus-prometheus-node-exporter-cq7kt                1/1     Running             7 (2m12s ago)   4d
prometheus-prometheus-node-exporter-kk7qj                1/1     Running             9 (41m ago)     4d
prometheus-prometheus-node-exporter-z7jdp                1/1     Running             4 (3h2m ago)    4d
redis-deployment-8685bb9c8d-6tkm9                        1/1     Running             0               9m25s
redis-deployment-8685bb9c8d-ctk68                        0/1     Terminating         0               15m
redis-deployment-8685bb9c8d-dd5b5                        1/1     Terminating         0               148m
selenium-chrome-node-5ff98b7c67-qrnlv                    1/1     Running             0               9m25s
selenium-chrome-node-5ff98b7c67-wct5m                    0/1     Terminating         0               15m
selenium-edge-node-6dfd48484c-c9nj9                      1/1     Terminating         0               168m
selenium-edge-node-6dfd48484c-fgbk4                      1/1     Running             0               15m
selenium-firefox-node-7d559964f9-drm6b                   1/1     Running             0               9m22s
selenium-firefox-node-7d559964f9-qb6xh                   1/1     Terminating         0               19m
selenium-firefox-node-7d559964f9-vwvxn                   1/1     Terminating         0               155m
selenium-hub-554bc5f9cd-b9wm2                            0/1     Terminating         0               148m
selenium-hub-554bc5f9cd-jp7vx                            0/1     Running             0               9m25s
selenium-hub-554bc5f9cd-r68sb                            0/1     Terminating         0               15m

Sounds like its starting and terminating services left and right out of the blue

I usually have a list of like 1/8 of this when using kubectl get pods

Hmmm seems like everything is stuck in a terminating state. I tried force deleting everything but the resource usage remains just as high

Can you try this please:

Upgrade the tool to the latest version, v1.0.4
Re-run the create command with this new version
Cordon all the autoscaled nodes that are currently not ready etc
Force delete the stuck pods with

kubectl -n <namespace> delete pod XXX --force --grace-period=0

And check

that new nodes are created automatically and become ready
that the pods get rescheduled on the new nodes

If this fixes the problem, then you can just delete the problematic nodes that you cordoned. I am asking you to try this to check if it's a problem with specific nodes for some reason, because I am not sure of what's happening in your cluster.

Hi, did you try what I suggested?

Heya! Sorry, i'll try and use the new version.
I force deleted the pods a few days ago and since then the problem has not happened. So I can probably not provide any immediate feedback to this issue unless it happens again.

I see. Weird though. Shall we close this or do you want to keep it open for now? You can always open another issue if it happens again :)

Closing for now! Thanks :-)

Sure thing 👍

Hmm something happened again. It seems that if a node gets overloaded and has no resources left, then other parts of the cluster become unavailable.
I installed OpenLens and got this view of the cluster

As you can see one of the nodes are suddenly not ready, and when that happens then i'm unable to see the metrics of the cluster. I would assume that one node going down shouldn't affect the rest of the service

This is how the hetzner graphs look for the node

Here's one of the other workers

As you can see it's pretty much idle, so i'm wondering why it can cause so many issues.

Aha! Okay so metrics issue fixed. I didn't have a HA config for metrics.

Nvm, metrics unavailable again :D
@vitobotta do you know if --enable-aggregator-routing=true is enabled for the kube-apiserver by default with your project?

I am not sure, I haven't come across it before. However if it's not you can specify extra args for each k8s component, including the API server.
About the metrics, you mean the metrics-server right? Is it running? If yes what do you see in the logs?


Implement Optimized Multileaving

First we need a solver for constraint satisfaction problems.
Do you have any ideas? (Sorry, I'm new in Python)

scipy may be a good candidate

I didn't know that scipy can. Thank you!

Let me try this if you havent yet

Of course!


allow a way for the child to communicate with the parent

and vice versa. Possibly by just using a pipe?

looks like there's already a pipe but it's closed before control is returned to the application. Possibly just need an option to not close the pipe

@kahing Thank you for the request. Please explain what scenario do you want to implement?
It is possible to extend Context with a binary data which will be transferred to the child on the start.
The library use a unnamed pipe to transfer context to the child but there is no a way to use the pipe after terminating of the parent's process because the pipe is closed automatically by OS (on parent's side).
If you want sometimes to connect to the child and send complex commands, we can use Named Pipe, i think. For simple commands is better to use System Signals.

The use case is the parent want to wait for the child to potentially show errors to the user. I currently use signals as you can see in https://github.com/kahing/goofys/commit/eb7963e9fb33235d5650ee0f634902cffdded573 . However things like error messages are lost. I could use the logfile mechanism but that seems kind of overkill for just one error message.

Ok, i think i understood you. I have an idea how to implement it.

Would like to know how this issue is going... A pipe is also a good solution, if not the best, when the parent process wants to pass some credentials to its child.


Commonize sortable form element for taxon tagging

We have two extremely similar sortable fields, used for tagging related
content to content items. We will soon be adding a third of these fields
(for external related links), so in preparation for this, this change
separates the repeated HTML from the content of the form elements, so
that it can be reused without copying and pasting.
Trello
https://trello.com/c/42clJNoN/184-add-external-link-sidebar-overrides-for-the-new-navigation

It turns out that external links cannot be curated in content-tagger without significant work, so we won't need this after all.


Acl

@prestigejo can you please validate this ?

@sebheitzmann what's that?
I've tried to check but you've changed more than 200+ files and erase some Wandi's parts (vendor names, docs, translations, ...), so what's the purpose of this huge PR?
Maybe you're mistaken about the branch?

Hello @sebheitzmann,
I'm very surprised. Why did you create a side project based on a fork instead of implementing (or improving) features on the main project (even more without mention)? This is not really the spirit of an open source project.


[PROBLEM] 2251. Number of Flowers in Full Bloom

Difficulty
Hard
Problem Description
You are given a 0-indexed 2D integer array flowers, where flowers[i] = [starti, endi] means the ith flower will be in full bloom from starti to endi (inclusive). You are also given a 0-indexed integer array people of size n, where people[i] is the time that the ith person will arrive to see the flowers.
Return an integer array answer of size n, where answer[i] is the number of flowers that are in full bloom when the ith person arrives.
Link
No response

Can  I get assignend this

can you assign me?


adds policyreport adapter helm config for falcosidekick

Signed-off-by: Mritunjay Sharma<EMAIL_ADDRESS>
What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

If this PR will release a new chart version please make sure to also uncomment the following line:

/kind chart-release

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area falco-chart

/area falco-exporter-chart

/area falcosidekick-chart

What this PR does / why we need it:
This PR adds support for policy report adapter in falcosidekick which was made available in its latest release.
Link to PR that added support is https://github.com/falcosecurity/falcosidekick/pull/256
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Checklist

[x] Chart Version bumped
[x] Variables are documented in the README.md
[ ] CHANGELOG.md updated

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: mritunjaysharma394
To complete the pull request process, please assign kris-nova after the PR has been reviewed.
You can assign the PR to them by writing /assign @kris-nova in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Welcome @mritunjaysharma394! It looks like this is your first PR to falcosecurity/charts 🎉


Random Matchup

Can you implement random matchup? I'm very frustrated when I want to play random matchup but it's not implemented yet.

Random Matchup isn't related to Game Sync, so I'm not sure why you're asking here.
Anyway, it cannot be implemented because there is currently no way to generate valid signatures, which the game requires in order to start the battle.
See: mm201/pkmn-classic-framework#116


Allow disallowed field value to be false. Added unit tests LB 65

Liquibase validate changesets before they are applied to a DBMS.
For example, following changeset for PostgreSQL is rejected because
PostgreSQL does not support ordered sequences:
<changeSet id="1" author="author">
   <createSequence cycle="false"
                   cacheSize="20"
                   incrementBy="50"
                   sequenceName="SOME_SEQUENCE"
                   ordered="true"
                   startValue="1"/>
</changeSet>

However, if someone writes the following changeset it will be
rejected by liquibase as well:
<changeSet id="1" author="author">
   <createSequence cycle="false"
                   cacheSize="20"
                   incrementBy="50"
                   sequenceName="SOME_SEQUENCE"
                   ordered="false"
                   startValue="1"/>
</changeSet>

This commit improves the validation in order to write ordered=false
explicitly.

This is a duplicate of #900 which was closed as "should not bring in"


Allow implementation of an interface to be passed as a constructor argument

Ran the tests, all green. Code looks good, thanks.


Feature Request: Support constraints on persistent volume id/path

This will greatly help with multi tenant cluster reservations.  We run many different disk configurations in combinations of RAID/JBOD, SDD/HDD, NFS. Currently, mesos supports no means of differentiating them. A useful workaround would be to filter either the path or the  volume id to some regex.

One way to support different disk configurations is to set an agent attribute for the different configurations and then use Marathon-style placement constraints recently introduced in #333.
@gabrielhartmann Please comment if there is a better alternative.

This works well if configuration is uniform per node.  However, the per resource determination is more flexible and could conceivably be used for more open ended cases.

Hi Dylan, we are looking to introduce support for resource labels/attributes in Apache Mesos such that volumes can be tagged as SSD, HDD, etc. Once support lands in Apache Mesos, we'll work to plumb it in to dcos-commons, and finally the Cassandra Integration.

Hi, has there been any progress in this area? Deploying services such as cassandra and HDFS is not really reliable unless they can each be assigned the right disks. For example HDFS might require larger disks than cassandra while they are both running on  a large node. Currently the first disk (mount) that fits will be assigned even if its size is way larger than needed.


Set Karen Puckett's status to 'InCommunity' in E2E tests

This was causing the E2E tests to fail
Release checklist
As part of our continuous deployment strategy we must ensure that this work is
ready to be released at any point. Before merging to main we must first
confirm:
Pre merge checklist

[ ] Have all changes to any dependencies been deployed to both preprod and
production in a backwards compatible way? (This includes our API,
infrastructure, third-party integrations and any secrets or environment variables)
[ ] Has a required data migration been included in this change or been done in
advance?

Post merge checklist
Once we've merged we now need to release this through to production before
considering it done.
Find the build-and-deploy job in CircleCI
and work through the following steps:

[ ] Has the product manager asked to provide approval for this feature?

[ ] Has the product manager approved?

[ ] Manually approve release to preprod
[ ] Verify change released to preprod
[ ] Manually approve release to prod
[ ] Verify change released to production

Should a release fail at any step, you as the author should now lead the work to
fix it as soon as possible.

I think we looked at this before - the problem with updating to InCommunity is a) it's not realistic, and b) it means they don't have an associated prison. I think there was some chat before about what to do, and I forget what the decision was. Lemme dig through Slack and confirm

@pezholio Yep, this was mentioned on the last PR when I tried to make this change maybe we could merge this whilst we wait for the chat to happen then we can revert it as it's a very minor change?
As things stand I don't think the E2Es have passed this year and I'm worried that even if we fix this it might unearth other issues.

Ah, good call, do they pass running locally? I thought not having a prison would mean the tests still failed?

Good point, I haven't tried them locally. Will give it a go tomorrow

npm run test:e2e:ui is your friend 👍

I didn't realise it was that easy.
As you suspected it doesn't pass as Karen doesn't have a Prison


(feat): add Faraday proxy support

Summary
Adding the ability to use a proxy when proxy from ENV is not suitable.
proxy = {
  :uri      => 'http://proxy.example.com',
  :user     => 'foo',
  :password => 'bar'
}

OpenAI::Client.new(access_token: "access_token_goes_here", proxy: proxy)

All Submissions:

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?

I checked out this branch (rebasing on alexrudall:ruby-openai main) and it worked for me!
I noticed this branch is missing test coverage. I found a couple libraries with test coverage for the proxy configuration:

sentry-ruby tests their URI object support by checking the state
oktokit also uses state based assertions

@alexrudall would you accept this PR with or without test coverage? Or would you prefer oktokit style test coverage?

Apologies for the delay in review.

@danilrwx Thanks very muchfor this PR and for adding to the README - a bit more about when/why you might want to do this could be really helpful.
@cpb - yes, a simple 'happy path' test would be great, can probably be added to 1 of the specs in spec/openai/client/client_spec.rb

* In which case, this could be just added to the existing README example to help users do this.

Thank for the feedback @alexrudall, see:

https://github.com/alexrudall/ruby-openai/pull/539


Ability to capture implicit typeclass instances within the schema

Problem
One of the core features zio-schema provides is to derive a Schema[A] for a type A once, and then use this data type to derive the implementation of additional functionalities such as codecs. Although the schema captures many information about the type - its structure, annotations, etc. - this might not be enough customization.
Consider for example the JSON codec in zio-schema. It is implemented in a way that it takes a Schema[A] and converts that to a zio-json codec:
def jsonCodec[A](schema: Schema[A]): ZJsonCodec[A]

normally with such a typeclass + derivation based design a user expects to be able to customize the instances, for example to implement a ZJsonCodec for a custom type by hand but use the typeclass derivation feature for the rest of the types. In this case the expectation is that the derivation macro picks up the hand-made implicit if it is in scope and does not even build the auto-generated codec for that particular type.
Using zio-schema to implement the derivation is a great simplification but it currently does not allow the above use case - once we captured the type's schema we no longer have enough type information to summon implicits for its inner types - the place where we could do that is the macro deriving the schema itself.
It would be nice to somehow be able to ask zio-schema to summon arbitrary typeclasses automatically so they can be readily accessed from the Schema types as a value.
Detailed requirements:

It should work separately from schema derivation - a 3rd party library may have predefined schemas (maybe even hand-written like in zio-flow) that we would like to reuse
It should be something that takes a schema and a typeclass type and somehow annotates the schema's each node with summoned typeclass instances
Transient fields should not summon the typeclass
Should support annotating with more then once typeclasses, an (optional) optimization can be to do it in one run

A draft solution proposal
One possible implementation could be a similar macro to the one that derives Schema itself and make it summon implicits and store them in the generated schema (similar to magnolia, but following the schema derivation macro's all features such as transient fields).
To minimize the required core changes it could store the summoned implicits in the schema's existing annotations fields. This would also allow storing multiple implicits, by providing a T[_] => Annotation mapping to this macro.
There are some open questions though:

It feels right to say this macro takes an existing schema and annotates that. But in fact it has to replicate the type level traversal of the original macro in order to get the types for each level, so probably it does not really take much advantage of the provided existing schema.

What if it is modified and there is a mismatch?
On the other hand there are some cases especially when dealing with polymorphic types where currently we need to hand-write schema instances. I feel like passing those hand-written schemas to this summoner macro may allow it to work where the original derivation macro does not.

It seems like we could purpose this into special derivation machinery.
e.g.:
trait Deriver[F[_]] {
  def deriveRecord[A](record: Schema.Record[A], fields: => Chunk[F[A]], summoned: => Option[F[A]]): F[A]
  def deriveEnum[A](enum: Schema.Enum[A], cases: => Chunk[F[A]], summoned: => Option[F[A]]): F[A]
  def derivePrimitive[A](st: StandardType[A], summoned: => Option[F[A]]): F[A]
}

object Derive {
  def derive[F[_], A](deriver: Deriver[F])(implicit schema: Schema[A]): F[A] = ???
}

Such that you would do: derive[JsonCodec, JsonCodec.deriver] (or more useably, delegate to this invocation inside of JsonCodec.derive[A]).

This definitely looks cleaner than what I suggested but it feels like a bigger change, requiring rewriting all the current zio-schema based derived codecs. Although that may only be the json codec for now (in zio-schema itself), and we already rewrote the other codecs (protobuf, thrift) that are directly implementing encoding and decoding to use the mutable builder/processor patterns.

Do we really have to re-write any of them? They will still work as they do now. It can be up to every implementor whether to use deriving or just schema directly.


Torrents have to be stopped individually because of dht node cache

When stopping a set of torrents with
// okay
foreach (TorrentManager tm in Engine.Torrents)
{
    await tm.StopAsync();
}

// doesnt work
await Task.WhenAll(Engine.Torrents.Select(tm => tm.StopAsync()));

i constantly run into the issue of
The process cannot access the file 'C:\...\dht_nodes.cache' because it is being used by another process..
The error stems from this line
        async ReusableTasks.ReusableTask MaybeSaveDhtNodes ()
        {
            if (!Settings.AutoSaveLoadDhtCache)
                return;

            var nodes = await DhtEngine.SaveNodesAsync ();
            if (nodes.Length == 0)
                return;

            await Task.Run (() => {
                var savePath = Settings.GetDhtNodeCacheFilePath ();
                var parentDir = Path.GetDirectoryName (savePath);
                Directory.CreateDirectory (parentDir);
                File.WriteAllBytes (savePath, nodes);  // <-- file in use
            });
        }

This is with version v2.0.1

This is an interesting issue! This is should be relatively easy to fix. In the meantime you should be safe using the 'working' approach as a temporary workaround.
If you're interested in contributing a fix, I believe the best option would be to only store the Dht node cache when the final torrent has stopped, and/or as part of ClientEngine.SaveStateAsync.

Fixed in master and 2.0! Keep an eye out for an update NuGet release!

Thank you very much, it seems to be fixed now


Fixed a typo in a method name in the README

Coverage remained the same at 97.543% when pulling 3b2c128f8965c1538e07da1b84a94979f7aeea9f on HugoGiraudel:patch-1 into 72feeb37daf5cfa5a9c299ac27b982da30bcbb4f on AdamPflug:master.

Thank you!


negative EAD

I have been seeing instances where EAD is negative. This seems really weird. See the min of the histogram in the image.

sampling a stage damage function where damage is negative?
maybe we need to use a truncated normal truncating at 0?

This is not the sample min, this is the histogram min. This is not a concern unless we find reasons to believe that we have a sample min below zero (e.g. an entire bin resides strictly below zero). Closing this issue.


BinanceApiWebSocketClient - does this work?

i am tring to use onCandlestickEvent but i don't get any exceptions and it seems to create websocket ok... but I dont receive any events?

I was recently able to get it to work, Vlad.  Can you post a bit of your code?  I had an issue with similar symptoms, when I had the symbol uppercase.

Hi @vladimirus , it does, yes, please provide some more details about the code you are using. Thanks.

The code is quite simple: https://gist.github.com/vladimirus/a834c6569f2b0695135347cd3b78db0d
I am waiting for a long time (30 mins) but have no output nor exception

I found the problem, the pair ("NEOETH" in my case has to be lowercase) :)

Great @vladimirus , yes, indeed, all symbols for streams are lowercase. This is stated in the docs (https://github.com/binance-exchange/binance-official-api-docs/blob/master/web-socket-streams.md), but it's not very obvious, perhaps I could lowercase automatically whatever argument is passed in the API.

FWIW, I got it from the examples.  I noticed the REST client uses uppercase and the WebSocket client uses lowercase.  Is that just a Binance API inconsistency?
https://github.com/binance-exchange/binance-java-api/blob/master/src/test/java/com/binance/api/examples/CandlesticksCacheExample.java


iosdk start

iosdk is slow to start on my pc.
Can you add a "iosdk started in mm:ss" at the end of starting process?
So i can do something betwenn iosdk start and its end

not sure if we can lower the memory requirements it loads locally and entire development and server system


[3.0.0] Third party key manager configuration

Description
Needs to add configuration template for third party key manager.

@AmaliMatharaarachchi  shall we elaborate the issue further. And please add the labels/ label suggestions on issue type, priority, affecting version, etc.

Fixed in https://github.com/wso2/carbon-apimgt/pull/7750


Added message when user mispells 'urlpatterns' in some 'urls' module

I found this kind of error when I mispelled urlspattern instead of urlpatternsinside my blog/urls.py file.
So the console was throwing an error, but this error do not helped me to found the problem. Check it:
django.core.exceptions.ImproperlyConfigured: The included URLconf '<module 'blog.urls'
from '.../my_project/blog/urls.py'>' does not
 appear to have any patterns in it. If you see valid patterns in the file then the
 issue is probably caused by a circular import.

The problem is not with a circular import, but with the mispelled urlpatterns variable itself, so I'm doing this pull request.
I appreciate any feedback.
Thanks,
Igor

I forgot to add changes to test files in the first commit, but now seems ok. Thanks.

Hi @igorkf, thanks, may I ask you to fill out a ticket? We use it to verify the proposed changes sound good.

Hi @igorkf, thanks, may I ask you to fill out a ticket? We use it to verify the proposed changes sound good.

Hi @jacobtylerwalls. Thanks for replying me.
I have just created this ticket.

I commited new message suggested by @felixxm

@igorkf Thanks for updates :+1: Welcome aboard :boat:

@felixxm thanks! Django is awesome


Invalid API key

Running the test script occur this error message:
Checking PEP 508 requirements…
Passed!
Checking installed package safety…
An error occurred:
Your API Key '1ab8d58f-5122e025-83674263-bc1e79e0' is invalid. See https://goo.gl/O7Y1rS

It's definitely this case https://github.com/pypa/pipenv/issues/4188
@EugenioCorso could you please go through such an issue an try to propose a solution (if there's already one)? Thanks!

Direi che questa si risolve così: https://github.com/pypa/pipenv/issues/4188#issuecomment-614877929
Puoi provare e confermare @EugenioCorso? Grazie

@libremente I tried and it works!

Removed .env file because no longer needed, the issue was solved here


Using seed for the password

I think it will be nice if the program would take an initial seed for the random process, so that it is repeatable. Such that
xkcdpass --seed="random123" would always produce "bloated uncheck trance unless violator washboard" or something like that.
There are many use case, such as generating easy to remember hash of a password, generating random words that associates to xkcd.com/936, etc etc.
Any way of making xkcdpass generate the words deterministic would be nice.

I think this is a bad idea and poses a huge security risk. The purpose of a random password generator is that it's nondeterministic. You don't want an attacker to be able to regenerate your password.
For example, a user may use predictable seeds to create passwords for websites.
xkcdpass --seed="google.com"

If I know your seed, I know your password.

@ghyde This is true, but there are other applications that would benefit from seeds. For instance, testings could rely on deterministic seeds. other use would be for generating username for websites.

What kind of testing would required deterministic seeds? Also, xkcdpass shouldn't be used to store or regenerate usernames or passwords. That should be managed somewhere else, like a password manager.

I'd rather not weaken the core logic if at all possible, even for legitimate reasons. However there are a couple of alternatives:
For testing might I suggest using a custom word list? It is fairly straightforward to constrain the generation logic to always return the same password that way (indeed the current tests take this approach).
Another alternative is to import the main script into your own code (see examples directory) and set python's seed yourself.


Schema submodules and python packaging

This PR contains 3 new features:

git submodules
protoc plugin for schema translation
python package of schema 'snapshot'

@kellrott @buchanae @adamstruck @mayfielg @prismofeverything @k1643 Can you code review?

bioschemas
Common data structures and APIs.
This repo contains

git submodules from ga4gh, gdc and bmeg
A utility to read the schemas and produce different output (jsonschema and cerberus)

packaging
The schemas are packaged into a python module bioschemas
The justification for the packaging is threefold:

Moves complexities of gitmodule management from the end user to the package release process
Each of the submodules referenced have many other components other than the schemas themselves.  Packaging allows us to trim all components other than schema source.
The generated snapshot is checked into git - the rationalization is that is allows us to tag package explicitly and allows clients to install the package without submodule complexity.

pip install git+https://github.com/ohsu-computational-biology/bioschemas

package release
cd bin
./package-all.sh
 ... generates schema snapshot ...
 ... runs setup tests ...
----------------------------------------------------------------------
Ran 4 tests in 0.100s

OK

usage
$ bioschemas-snapshot --help
usage: bioschemas-snapshot [-h] [-o OUTPUT] [-v]

Extract bioschemas schema directory [ga4gh,bmeg,gdc]

optional arguments:
  -h, --help            show this help message and exit
  -o OUTPUT, --output OUTPUT
                        Extract to this directory name. Must not already
                        exist; it will be created as well as missing parent
                        directories.
  -v, --version         Print git hashes

The snapshot can be used by any language context and has the following structure:
.
├── cerberus
│   ├── bmeg
│   ├── ga4gh
│   │   ├── ga4gh
│   │   └── google
│   │       ├── api
│   │       └── protobuf
│   └── gdc
├── jsonschema
│   ├── bmeg
│   ├── ga4gh
│   │   ├── ga4gh
│   │   └── google
│   │       ├── api
│   │       └── protobuf
│   └── gdc
└── proto
    ├── bmeg
    └── ga4gh
        ├── ga4gh
        └── google
            └── api

python usage
import  bioschemas

bioschemas.schema_path()
>> '/home/someuser/bioschemas/bioschemas/snapshot'

 bioschemas.json_schema('Resource')
>> {u'properties': {u'checksum': {u'type': u'string'}, u'class': {u'type': u'string'}, u'created': {u'type': u'string'}, u'datasetID': {u'type': u'string'}, u'description': {u'type': u'string'}, u'format': {u'type': u'string'}, u'gid': {u'type': u'string'}, u'id': {u'type': u'string'}, u'info': {u'type': u'object'}, u'location': {u'type': u'string'}, u'mimeType': {u'type': u'string'}, u'name': {u'type': u'string'}, u'size': {u'type': u'integer'}, u'type': {u'type': u'string'}}, u'type': u'object'}

 bioschemas.cerberus_schema('Resource')
>> {u'checksum': {u'type': u'string'}, u'class': {u'type': u'string'}, u'created': {u'type': u'string'}, u'datasetID': {u'type': u'string'}, u'description': {u'type': u'string'}, u'format': {u'type': u'string'}, u'gid': {u'type': u'string'}, u'id': {u'type': u'string'}, u'info': {u'type': {u'type': u'dict'}}, u'location': {u'type': u'string'}, u'mimeType': {u'type': u'string'}, u'name': {u'type': u'string'}, u'size': {u'type': u'integer'}, u'type': {u'type': u'string'}}

bioschemas.git_hashes()
>>  {u'bioschemas': u'f40f653', u'bmeg': u'537f94a', u'created_at': u'2016-11-18T17:47:56.858397Z', u'gdc': u'288f042'}

bioschemas.gdc_submission_template('file')

>> {u'aliquots': {u'submitter_id': None}, u'analytes': {u'submitter_id': None}, u'archives': {u'submitter_id': None}, u'cases': {u'submitter_id': None}, u'centers': {u'code': None}, u'data_formats': {u'name': None}, u'data_subtypes': {u'name': None}, u'derived_files': {u'submitter_id': None}, u'described_cases': {u'submitter_id': None}, u'experimental_strategies': {u'name': None}, u'file_name': None, u'file_size': None, u'md5sum': None, u'platforms': {u'name': None}, u'portions': {u'submitter_id': None}, u'project_id': None, u'related_files': {u'submitter_id': None}, u'samples': {u'submitter_id': None}, u'slides': {u'submitter_id': None}, u'state_comment': None, u'submitter_id': None, u'tags': {u'name': None}, u'type': u'file'}

utilty
The ga4gh and bmeg cannonical schemas are maintained in protobuf.  The bin/custom-plugin.py processes the schemas for alternate uses (jsonschema, cerebus).  The bioschemas/snapshot directory contains output from protoc.
Please do not hand edit, rather change custom-plugin.py or json-to-cerberus.py

I suggest putting a very simple readme file in schemas and bioschemas to describe what those directories are.
Is the snapshot python specific? If we have another client library, say for Go or Scala, would it share the same snapshot or generate its own?

@buchanae  thanks.  no, the snapshots are not python specific.  I'll add the readme and change the example

Assorted thoughts, none of these are really blockers for this PR.

Do we want to include the snapshot code in the actual repo?
It looks like there is some tests built in. Can we get a .travis.yml file to trigger them ?
We should find a way to include the framespace api ( https://github.com/ohsu-computational-biology/ccc_api/tree/master/proto/framespace ) probably need @jacmarjorie for that. We may want to depreciate the ccc_api repo....

Thanks @kellrott
>Do we want to include the snapshot code in the actual repo?
The only reason to have it in is that AFAIK, it is needed if we want to do
pip install git+https://github.com/ohsu-computational-biology/bioschemas

I may be wrong about that.  Does anyone have ideas?
We can certainly deprecate it if/when we use pypy for pip distribution.
>It looks like there is some tests built in. Can we get a .travis.yml file to trigger them ?
Sure. I'll add an issue to track for next PR.
>We should find a way to include the framespace api
Sure. I'll add an issue to track for next PR.

@buchanae
See latest commits for README and command line usage for other lang environments

I suppose the pip install point is pretty valid. We probably don't want to have to go to pypy until things are more mature.
Anybody else have comments?

@kellrott @buchanae @adamstruck @mayfielg @prismofeverything @k1643 Since no other comments, I plan on merging this morning at 11:00.  Let me know ...


Q: Consul leadership not working?

I'm running multiple instances of nomad-firehose (each instance on a different box) and I've noticed that all of them produce the same output, it seems like the leadership mechanism is not working:
$ consul --version
Consul v0.9.3
Protocol 2 spoken by default, understands 2 to 3 (agent will automatically use protocol >2 when speaking to compatible agents)

$ nomad --version
Nomad v0.6.0

$ SINK_TYPE=stdout ./nomad-firehose-linux-amd64 evaluations
INFO[0000] Trying to acquire leader lock
INFO[0000] Lock acquired
INFO[0000] No Last Change Time restore point, starting from scratch
{"ID":"687332a6-679f-e913-1b9c-a91528a9eba8","Priority":50,"Type":"service","TriggeredBy":"deployment-watcher","JobID":"XXX","JobModifyIndex":0,"NodeID":"","NodeModifyIndex":0,"DeploymentID":"3c22e031-cb8a-f8e2-9923-4e715e78c57c","Status":"complete","StatusDescription":"","Wait":0,"NextEval":"","PreviousEval":"","BlockedEval":"","FailedTGAllocs":null,"ClassEligibility":null,"EscapedComputedClass":false,"AnnotatePlan":false,"QueuedAllocations":{"XXX":0},"SnapshotIndex":1573880,"CreateIndex":1573880,"ModifyIndex":1573883}
{"ID":"24fe786e-8f94-3558-62e7-0c11bfea960d","Priority":50,"Type":"service","TriggeredBy":"deployment-watcher","JobID":"XXX","JobModifyIndex":0,"NodeID":"","NodeModifyIndex":0,"DeploymentID":"3c22e031-cb8a-f8e2-9923-4e715e78c57c","Status":"complete","StatusDescription":"","Wait":0,"NextEval":"","PreviousEval":"","BlockedEval":"","FailedTGAllocs":null,"ClassEligibility":null,"EscapedComputedClass":false,"AnnotatePlan":false,"QueuedAllocations":{"XXX":0},"SnapshotIndex":1573868,"CreateIndex":1573868,"ModifyIndex":1573870}
(...)
INFO[0010] Writing lastChangedTime to KV: 1573883
INFO[0020] Writing lastChangedTime to KV: 1573883
INFO[0030] Writing lastChangedTime to KV: 1573883
INFO[0040] Writing lastChangedTime to KV: 1573883
INFO[0050] Writing lastChangedTime to KV: 1573883
INFO[0060] Writing lastChangedTime to KV: 1573883
INFO[0070] Writing lastChangedTime to KV: 1573883
INFO[0080] Writing lastChangedTime to KV: 1573883
INFO[0090] Writing lastChangedTime to KV: 1573883
INFO[0100] Writing lastChangedTime to KV: 1573883
INFO[0110] Writing lastChangedTime to KV: 1573883
INFO[0120] Writing lastChangedTime to KV: 1573883
INFO[0130] Writing lastChangedTime to KV: 1573883
INFO[0140] Writing lastChangedTime to KV: 1573883
INFO[0150] Writing lastChangedTime to KV: 1573883
INFO[0160] Writing lastChangedTime to KV: 1573883
INFO[0170] Writing lastChangedTime to KV: 1573883
INFO[0180] Writing lastChangedTime to KV: 1573883
INFO[0190] Writing lastChangedTime to KV: 1573883
INFO[0200] Writing lastChangedTime to KV: 1573883
INFO[0210] Writing lastChangedTime to KV: 1573883
INFO[0220] Writing lastChangedTime to KV: 1573883
INFO[0230] Writing lastChangedTime to KV: 1573883
INFO[0240] Writing lastChangedTime to KV: 1573883
INFO[0250] Writing lastChangedTime to KV: 1573883
INFO[0260] Writing lastChangedTime to KV: 1573883
INFO[0270] Writing lastChangedTime to KV: 1573883
INFO[0280] Writing lastChangedTime to KV: 1573883
INFO[0290] Writing lastChangedTime to KV: 1573883
INFO[0300] Writing lastChangedTime to KV: 1573883
INFO[0310] Writing lastChangedTime to KV: 1573883
^CINFO[0316] Caught signal, releasing lock and stopping...
INFO[0316] [sink/stdout] ensure writer queue is empty (0 messages left)
INFO[0316] Writing lastChangedTime to KV: 1573883

Am I doing something wrong? 🤔

@jippi any chance that you could take a look at this issue?

@jvrplmlmn Looks like acquiring and releasing the lock happens in the NewFirehose function.
Maybe it should be happening in Start

Can confirm that this is the case; I noticed this when testing #19. It appears the New* functions immediately release the lock after acquisition.

@jippi any chance you can take a look?

ah, i think i've found the bug - kinda silly issue, let me try and come up with a patch for it

Fixed https://github.com/seatgeek/nomad-firehose/releases/tag/v1.0.0
the code was totally broken :p

I think this is still broken. With this docker-compose.yml with self-contained Consul, Zookeeper, Kafka, and one instance of nomad-firehose, I'm still able to run two producer instances of nomad-firehose at the same time:
version: '3.5'

services:
  consul:
    image: consul
    environment:
      CONSUL_BIND_INTERFACE: eth0
  nomad-firehose:
    image: seatgeek/nomad-firehose:v1.0.0
    depends_on:
      - consul
    # change jobs to allocations or nodes or whatever
    command: nomad-firehose jobs
    environment:
      NOMAD_ADDR: YOUR_NOMAD_CLUSTER_HERE
      NOMAD_REGION: ...
      NOMAD_CACERT: ...
      SINK_TYPE: kafka
      SINK_KAFKA_BROKERS: kafka:29092
      SINK_KAFKA_TOPIC: foo
      CONSUL_HTTP_ADDR: http://consul:8500
  zookeeper:
    image: confluentinc/cp-zookeeper:latest
    environment:
      ZOOKEEPER_CLIENT_PORT: 32181
      ZOOKEEPER_TICK_TIME: 2000
    extra_hosts:
      - "moby:<IP_ADDRESS>"
  kafka:
    image: confluentinc/cp-kafka:latest
    depends_on:
      - zookeeper
    environment:
      KAFKA_BROKER_ID: 1
      KAFKA_ZOOKEEPER_CONNECT: zookeeper:32181
      KAFKA_ADVERTISED_LISTENERS: PLAINTEXT://kafka:29092
      KAFKA_OFFSETS_TOPIC_REPLICATION_FACTOR: 1
    ports:
      - 9092:9092
    extra_hosts:
      - "moby:<IP_ADDRESS>"

This alone works great, I can follow along the Kafka topic, but when I try to start another nomad-firehose instance, it sits and waits 15 seconds for the lock, but then gives up and starts writing anyway:
$ docker-compose run --rm --no-deps nomad-firehose
INFO[0000] Trying to acquire leader lock (nomad-firehose/jobs.lock)
INFO[0015] Lock acquired
INFO[0015] Restoring Last Change Time to 62731127
INFO[0015] [sink/kafka] Starting writer

The other producer continues writing and doesn't try to reacquire the lock. At this point, we start seeing duplicate events on the Kafka topic.
Is this expected behavior?

@wyattanderson after 3h of weekend coding, i ended up refactoring everything - it should be latest and 1.1.0 tag
I did some basic testing, and it seem to be working as expected. Let me know what you experience

Excellent. Looks like it works now. Thanks so much!


Update patternfly and patternfly-react components

Fixes: #1619
Update the following:
patternfly from 4.185.1 to 4.215.1
react-charts from 6.55.16 to 6.94.1
react-console from 4.53.20 to 4.92.1
react-core from 4.202.16 to 4.241.1
react-icons from 4.53.16 to 4.92.1
react-table from 4.71.16 to 4.110.1

/ost

I ran a basic regression sanity and it LGTM.


refactor: change in order of middleware parameters

context is now the first parameter
d is the second parameter

#39  👈 (View in Graphite)
main

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


fix(types): use protractor from global namespace

Relates to https://github.com/angular/protractor/issues/3367


[BUG] FDAR state is invalid, Not ARM

Not much to go from here, guessing it's due to binary somehow though.
I'm waiting for MAS to upgrade to Ren'Py 8 so I can rewrite this Submod properly, until then I recommend not trying to use the submod, sorry!

Alright thank you, I appreciate it.


[REVIEW] GitHub profile

GitHub Profile Link:
https://github.com/rofazayn
You can also join the Discord community here
Feel free to check out other cool repositories of the EddieHub Community here

Thanks for sharing :) These are suggestions from my side

You can add more context to your custom profile maybe
Add a description to the pinned projects might help

Reviewed on live stream https://www.youtube.com/watch?v=XT3_O4jULRE
looks good 👍

maybe add a bit more to your GitHub bio on the left
could you add the technologies you use to your customised profile

I hope that helps, it will grow with time also 🤓


Update homework_3.sql

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Submission of assignment
What did you learn from the changes you have made?
How to write some SQL queries
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
No,
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
No
How were these changes tested?
Tested on DB SQLite
A reference to a related issue in your repository (if applicable)
Checklist

[ -] I can confirm that my changes are working as intended

I have submitted my homework 3, kindly grade it


Bump ml job test timeout from 60 to 75 minutes

Due to newly occurring timeout issues blocking this week's release.
Some more investigation is merited to understand the longer test run, but aside from that this is the fastest path to mitigation.

This is currently blocking main for the ml team. I feel very confident/safe in this change, so I'm going to override and merge without waiting for the checks to complete.

/check-enforcer override

This seems to primarily after tests running on the MacOS runner. Those tests seem to take upwards of 10-20 minutes more than every other runner.


Enchantments doing nothing

I have HxC-Core and HxC-Enchantments and yet all of the enchantments seem to do nothing in Minecraft 1.7.10. I downloaded and installed the mods using Curse for Minecraft. I have 32 mods total running and all other mods run fine, no bugs or crashes. Also i can't seem to find anything information on what the "charge system" is or what it does.

"Charge" is required for any enchant to work, just sneak while holding an enchanted item in hand to convert xp to charge. Each enchant has a configurable amount of charge required.
You can either A.) Change requirements to 0 B.) Disable charge system
I use this mod on my server and my enchants do work.

Okay so I disabled the charge system in the config file and after restarting the game, enchanted items no longer show the "charges: x" in the tool tip but when I press Sneak it still drains my levels and the new enchantments still don't do anything at all. I may try testing the mod separately in a new world to see if this problem is a conflict with another mod in my current world.

HxCBlocks is the reason it's crashing, I haven't finished the rewrite of the mod, so it's currently broken.

You don't have to send me the crash reports you know, usually if it's my fault I get the crash reports in
https://github.com/HxCKDMS/AutomaticCrashReports/issues

okay so i removed hxc-blocks and it runs now. testing the enchantments via creative mode in a fresh world and it seems like the majority of them do nothing at all. Vampirism did seem to do a little bit of hunger healing and regeneration did heal me very slowly when my hunger was low. Other than that, the other enchantments didn't work. I tested quite a few of them like Jump Boost, did not improve my jump. Homing did not cause arrows to follow or even curve towards targets. Nightvision failed, etc. I'm thinking maybe each enchantment has to be on a specific item to work but i have no idea which enchantments go where. I tested them on a few different items, from weapons, bows and armors. The Aura's i put on armor and did nothing. Combat based ones i put on weapons. Buffs i put on armor as well. I charged all of the enchanted items to over 10k just to be sure there was enough charge. So i don't have a clue why it isn't working.
In my main world, i have removed this mod because the charge system was still draining my lvls even though i disabled it. So for now, i'm done trying this one out. All testing I do shows negative results, aside from Regen and Vampirism.

Just FYI The enchants all have been tested in latest version to work, I'll make an update that specifies what the conditions are to make them work, maybe when you hold shift, but they do work.


Avoid opening the compose box for sidebar clicks.

We no longer automatically open the compose box for sidebar
actions.  The logic behind this is that most users spend more time
reading messages than composing messages, and opening the compose
box can interfere with efficient browsing.  On a mobile device, the
compose box takes up a significant chunk of your screen real estate.
On a bigger device, the compose box intercepts important navigation
keys like page-up and end, and even when it allows them, it can be
jarring.
This change definitely introduces a tradeoff, as there will be
slightly more friction for users to compose new messages.  My
judgment is that we have plenty of other options available:

hotkeys: enter, r, c, C
clicking on the message you're replying to
click on "New topic"
click on "New private message"
use stream chevron send-message option
use topic chevron send-message option
use buddy list chevron send-message option
use message info menu option
use buddy list search and hit enter for the first user
in the search results (I think we should change this too)

This commit also simplifies our code, since it's purely removing
code.  If we want to re-introduce auto-open capability, we will
probably want to use an approach that is more testable.  The logic
that was removed here was part of a function that is 200+ lines in
length, so it was never unit tested. It also seemed to have a logic
flaw in terms of assuming that the else clause for the
narrowed_to_topic() test implied we were dealing with private
messages.  That may have been true in the context it was originally
written, but it was a ticking time bomb, because what if you are
just narrowed to a stream?
Fixes #3886

Automated message from Dropbox CLA bot
@showell, it looks like you've already signed the Dropbox CLA. Thanks!

@showell I initially made these changes in #3960, but @timabbott thought otherwise. Nonetheless, I agree with your changes.

@lonerz Ha, I didn't realize that!  I think we're obviously on the same page. :)
Here was some related conversation on chat: https://chat.zulip.org/#narrow/near/188034/stream/frontend/topic/unit.20testing.20compose.2Estart

Closing my PR the.

Reading the code, I think there was no "ticking time bomb", because exports.narrowed_by_reply ensures the narrow was a topic or pm-with narrow.

So I think removing the topic code path here is probably the right thing to do.  I'm much more skeptical of removing the pm-with code path -- I think users have a fairly strong expectation that clicking on a user in the right sidebar gets them in a position to "just type" to send a message to that user.
I think there's a good reason to have asymmetric behavior here -- the reading-to-writing ratio for PMs is generally close to 1, whereas for stream messages it is generally much more than 10 (depending on the size of the stream, etc.).

Ok, we should probably re-open this discussion on chat.  I think the code on lines 216-219 has no good reason to be 168 lines away from the code on lines 378-383 that Josh and I removed, so we could probably combine them and extract a method called narrow.activate_compose that we can put some tests around.
One data point on PMs is that currently, when you click on the upper left sidebar, it doesn't open the compose box.  It's interesting to me that nobody's really complained about that.  But I also find your asymmetry argument somewhat persuasive, so I'd be inclined to say that any narrowing action related to PMs should open the compose box, whereas no narrowing actions related to streams should open the compose box.  (In streams mode, you'd click on buttons/messages/hotkeys once you're in the narrow, but not as part of a narrowing action.)

Abandoning this PR, based on latest decisions.  I'm working on a more involved PR that addresses the compose box a bit more deeply.


Prefer Grafana 9 workload

Prefer usage of Grafana 9 container image from RHCC. Grafana 7 is EOL
upstream and receives no security support. Prefer use of Grafana 9 which
is still supported.

This would need to be cherry picked to the release-op-1.5.4 branch if approved and merged. (I will handle the paper work.)

All the nodes are failing in zuul.... going to try a preemptive recheck, but this code path isn't even tested, so I should really just force merge this down 🤷🏻

/recheck

recheck

recheck

recheck


Slack link on the website is not working

Description

link on the website bottom leads to the attached screenshot
Expected Behavior

Screenshots/Logs

Hey @N-Saipraveen , are you referring to the bottom footer of Layer5 website?
As I have tested the link https://slack.layer5.io/ is working fine.

hey @N-Saipraveen can u add the link here where its not working.