Not able to @ the bot in a Forum

Hello, @jakobdylanc, thanks for the llmcord. I have been playing with it in our Discord server.
I created two test channels (both non-private), one was a regular channel and the other was a Forum type channel.  I found I could mention the bot in the regular channel but not in the Forum channel.  In the later case, the bot just kept silent and gave no response.
Do you know whether it is a llmcord issue or a my Discord setting issue?
Thanks!

Thanks for using llmcord!
I intentionally restricted llmcord to only work in certain channel types. This is defined by ALLOWED_CHANNEL_TYPES at the top of llmcord.py.
The reason I didn't include forum channels is because, for some reason, the discord.py library does not have a fetch_message method for forum channels. fetch_message is important for llmcord's reply-based functionality.

Oh, I see. Looking at https://discord.com/developers/docs/resources/channel#channel-object-channel-types, I tried to append discord.ChannelType.guild_forum in ALLOWED_CHANNEL_TYPES but it did not work. The Discord python module complained:

AttributeError: type object 'ChannelType' has no attribute 'guild_forum'

My goal is to forward emails to our mailing-list to a Discord channel and let the LLM bot to make a draft reply. I just feel a Forum channel with posts (title + message) is better suited to email threads.

The correct entry would be discord.ChannelType.forum, per discord.py's documentation:
https://discordpy.readthedocs.io/en/stable/api.html?highlight=channeltype#discord.ChannelType
If you experiment and find anything out, let me know. I'll do the same when I have time :)

I tried discord.ChannelType.forum and the llmcord.py ran fine. But I still could not mention the bot (Llama) in the Forum.  In the regular channel, I could do it, but with a limitation.
I have a Discord webhook for the channel.  I posted a message via the webhook (Email-forwarder) and mentioned the bot.   But the bot did not respond.  However, I could manually mention the bot.  See the attachment.  Is it an issue of llmcord?

Yeah, llmcord does the following in its message filtering:
if discord_client.user not in new_msg.mentions:
    return

I think that since your bot is just pasting the literal mention string, it doesn't count as a proper mention, so it won't show up in mentions.
You can fix this by making it look for the literal mention string instead:
if discord_client.user.mention not in new_msg.content:
    return

This might be better, so I might push this change. For now you can try it yourself.
Just change this line:
https://github.com/jakobdylanc/llmcord/blob/1992a546e2ef013e615d1248cd05275ca515639b/llmcord.py#L76
To this:
or (new_msg.channel.type != discord.ChannelType.private and discord_client.user.mention not in new_msg.content)

I made the change at line 76 but it did not work.  Actually, I did use a proper mention (vs a literal string) in the format of <@AppId>,  e.g.,<@1295421604515287048> in the message, that's why we could see @Llama in the picture.

Oh whoops, llmcord also filters out all bot messages. I overlooked this : )
I'm on mobile right now so can't link to the code easily. But you should be able to find the line that filters out bot messages. Just remove it.

It's line 77

Thanks. It works now!

How are you finding the functionality in forums? Like continuing conversations?
I imagine it might work OK most of the time. But if you restart the bot, and then continue a previous conversation, I think you will see issues (this is when fetch_message would be called).

With the diff, I was able to mention the bot in Forum.  I have not done extensive test with the Forum yet.  But I saw errors with DM (a chain of short/empty responses).  See the attachment.
22c22
< ALLOWED_CHANNEL_TYPES = (discord.ChannelType.text, discord.ChannelType.public_thread, discord.ChannelType.private_thread, discord.ChannelType.private)
---
> ALLOWED_CHANNEL_TYPES = (discord.ChannelType.text, discord.ChannelType.public_thread, discord.ChannelType.private_thread, discord.ChannelType.private, discord.ChannelType.forum)
77d76
<         or new_msg.author.bot

Ah, I think that's because the bot is getting triggered by itself, since you removed the "new_msg.author.bot" check. You've opened a can of worms :)

I think instead of removing line 77, you should keep it, but change it to:
or (new_msg.channel.type == discord.ChannelType.private and new_msg.author.bot)

The change fixed the DM issue.  Thanks!


Center lines vertically in completion box

Lines are centered vertically in a lot of places, but not there. I think it is just something that was missed in https://github.com/godotengine/godot/pull/19735.

Thanks!


Potential vulnerabilities in Puppet files: Suspicious Comment

3 suspicious comments were found in 3 different scripts.
Script 1: https://github.com/dev-sec/puppet-os-hardening/blob/ee1851a31e5ed32f81d340d7b3b329711996aa38/manifests/suid_sgid.pp

Line 121: # todo: do without

Script 2: https://github.com/dev-sec/puppet-os-hardening/blob/ee1851a31e5ed32f81d340d7b3b329711996aa38/manifests/pam.pp

Line 154: # todo: not supported warning

Script 3: https://github.com/dev-sec/puppet-os-hardening/blob/ee1851a31e5ed32f81d340d7b3b329711996aa38/manifests/sysctl.pp

Line 225: # todo

A suspicious comment usually contains information on the presence of defects, missing functionality or weakness of the system.
This type of smell can lead to a well-known type of vulnerability, as documented by CWE (CWE-546). Suspicious comments can give insights on problems in the source code that can be leveraged by hackers to exploit your application.
Writing suspicious comments in Puppet configuration files is considered to be a security smell (cf. [icse20]).
Recommendation
Comments that suggest the presence of bugs, incomplete functionality, or weaknesses should be removed before deploying or open-source the application.

@cantebigene These todo's shouldn't be there, I agree ... but it's not about defects / weaknesses here. It's just a marker to include more operating systems in the future.


Auto-align the selected item on the view when the combo-box is opened

When the combo-box is opened the item that's already selected doesn't get scrolled into view which means the user has to scroll down to get to the selected item.
This is especially a problem for components like year-picker(which uses the Read-only Combobox) in which the year range might start from 1900 making the user scroll a lot to get to the required selection.
Ideal behavior->

Ideally, item that's already selected should be on the bottom of the list when the box is opened.

I think something like this in handleOpen will work. It probably needs some QA and maybe limited to only single select readonly variant?
    const index = findIndex(this.getOptions(), (item) =>
    isEqual(item, this.props.selection[0])
    );

    menuItemSelectScroll({
      container: this.menuRef,
      focusedIndex: index,
    });

I think something like this in handleOpen will work. It probably needs some QA and maybe limited to only single select readonly variant?
    const index = findIndex(this.getOptions(), (item) =>
    isEqual(item, this.props.selection[0])
    );

    menuItemSelectScroll({
      container: this.menuRef,
      focusedIndex: index,
    });

Yeah. I was thinking more of the same. And yes, it should be restricted to the readonly variant.

Yeah. I was thinking more of the same. And yes, it should be restricted to the readonly variant.


Make the corruption error more clear and fix zarf tools cache-clear

Description
This adds a more descriptive error and fixes issues with the cache clear command
Related Issue
Fixes #813
Type of change

[X] Bug fix (non-breaking change which fixes an issue)

Checklist before merging

[X] (Optional) Changes have been linted locally with golangci-lint. (NOTE: We haven't turned on lint checks in the pipeline yet so linting may be hard if it shows a lot of lint errors in places that weren't touched by changes. Thus, linting is optional right now.)

Would you mind dropping a screenshot for the pr of the improved error output?

Sure here ya go:


fix: corrected Index cond. for conditional formatting in table widget

Pull Request Template
Use this template to quickly create a well written pull request. Delete all quotes before creating the pull request.

Description

Please include a summary of the changes and which issue has been fixed. Please also include relevant motivation
and context. List any dependencies that are required for this change.

Fixes #8839

if no issue exists, please create an issue and ask the maintainers about this first

Type of change

Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions, so we can reproduce.
Please also list any relevant details for your test configuration.

Test A
Test B

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:green_circle: Total coverage has increased
// Code coverage diff between base branch:release and head branch: fix/fix-condtitional_formatting_break_table

Status
File
% Stmts
% Branch
% Funcs
% Lines

:green_circle:
total
55.13 (0.01)
37.05 (0.01)
34.02 (0)
55.65 (0.01)

:green_circle:
app/client/src/utils/autocomplete/TernServer.ts
52.94 (0.23)
41.67 (0.84)
36.21 (0)
56.99 (0.25)

/ok-to-test sha=8aa9639

/ok-to-test sha=8aa9639

/ok-to-test sha=8aa9639

/ok-to-test sha=d8b237d

@keyurparalkar verified this PR and working as expected now.. The conditional formatting remains on sorting


add common workflow for eos

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 62.56%. Comparing base (d2448fd) to head (a001d13).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #27   +/-   ##
=======================================
  Coverage   62.56%   62.56%
=======================================
  Files          19       19
  Lines         537      537
=======================================
  Hits          336      336
  Misses        201      201

Flag
Coverage Δ

python-3.11
62.56% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Send pre-workshop email to participants

A week before the workshop we should send out an email to the participant. Contents:

request to install git on their conference laptops and to create GitHub account
...tbc

An attempt for a complete list:

Create an account on https://github.com/
Install git: https://git-scm.com/downloads
Install cURL: https://curl.haxx.se/download.html
Install jq: https://stedolan.github.io/jq/

i created a first draft at http://etherpad.lobid.org/p/swib16-workshop-mail-ob4zg3cc.


Calculating M.nCr(n,r)

Do the checklist before filing the issue:

[x] Do you have Node.js and all the relevant dev-dependencies installed?
[ ] Is this a bug fix?
[x] Is this an enhancement?
[x] Is this a feature request?

NOTE: Provide a clear and concise description of the feature that needs to be added! Or if its a bug, then provide the necessary steps to reproduce it along with screenshots.

Combinatorics is an essential part of math, and nCr is one of its main utility function.
This issue aims at creating a function - M.nCr(n,r)
Math formula for nCr -
nCr = (n!) / (r! * (n-r)!)
M.nCr(3,2); // Returns 3

// Inital validation tests -
M.nCr(3,5); // Returns error - n >= r condition not satisfied.
M.nCr(-2,5); // Returns error - no negative numbers allowed
M.nCr(2.02,3); // Returns error - no floating numbers allowed

Links -
GFG- Calculating nCr
Edit -

Use existing functions like M.factorial to calculate factorial for M.nCr(n,r)

I would like to work for this

@sateslayer first fix your PR according to the changes requested!

Of course. This is the first time working with ES6, so I have very less idea where I am going wrong. Feel free to tell me if you find me unsuitable for your project.

Hi! Could you please assign this issue to me? I would be glad to work on this one.

@viditkumar you're assigned!


how to set up pagination for feed?

Could not find the in docs.
seems the feed by default have only 10 posts. Is there anyway to get the previous posts in the feed?

This is not currently supported.

For the record, that's functionality I miss, too.  That is, allow fetching [...]/feed.xml?paged=2 or similar.


Wrong update to pc at instruction 1

https://github.com/kpmiller/emulator101/blob/157a840ea014077c5e300da2dbbac4f6566d6769/8080emu-first50.c#L370
Shouldn't the pc be updated to +=3? LXI is a 3bytes instruction.

Didn't see the line after the switch updating to += 1. My bad


Major performance increase by shortening URL regex

I am using STTweetLabel in a UITableView. In my case, there is one STTweetLabel per cell; each one detects three types of hotwords, including URL. I noticed that when I scrolled kind of fast, the performance wasn't that good, the scrolling was jumpy. I have been testing on an iPhone 5s and 6, both showed jumpy scrolling.
By simply changing the URL regex in STTweetLabel.m to a shorter regex, I got a major performance increase. I can scroll super fast and it's super smooth. Here's the regex I used instead:
#define STURLRegex @"(https?:\\/\\/)?([\\w\\-])+\\.{1}([a-zA-Z]{2,63})([\\/\\w-]*)*\\/?\\??([^#\\n\\r]*)?#?([^\\n\\r]*)"

You can test the regex here: http://regexr.com/39p0t
EDIT: please note regex fix below.

Has anyone tested using NSDataDetector  with NSTextCheckingTypeLink?  It would also remove the need for this project to maintain or test for regex, and it would allow the future implementation of other data types (e.g. all those supported by NSDataDetector).

@SebastienThiebaud @inorganik
I forked and branched develop and created 87c835518588c37dcd73690dccbd8e06a9e456ae implementing NSDataDetector for link detection.  I added a workaround so that the test_setTextAndGetHotWords_setTextWithOneEncapsulateLinkWithSpecialCharacters_hotWords test would pass because NSDataDetector will only detect (http://foo.com/?arg=bar) but not (http://foo.com/?arg=bar(baz)).
All other tests pass except test_setTextAndGetHotWords_setTextWithOneLinkWithSpecialCharacters_hotWords because it is my understanding that [] are valid characters per RFC3986, correct?
If this is sufficient I can remove that test and submit a pull request including all the changes.
How did you benchmark the performance previously?
For a future pull request my hope is to be able to use the NSURL object returned from NSDataDetector and pass it back to the detection block so that one could simply call [[UIApplication sharedApplication] openURL:url];.  This saves the need for doing any URL parsing or creation yet again in the detection block and allows for easy external app integration; for example, simply including mailto in the allowed protocols would allow "string with<EMAIL_ADDRESS>to automatically be parsed into a NSURL object that would open the Mail app without any other application changes.  Thoughts?

Update -- after benchmarking (n = 1000) it appears the original regex is faster than NSDataDetector, bummer.  Even though the proposed regex doesn't match all cases, just for comparison I also included it:
            user        system    total        real
orig       10.730000   0.110000  10.840000 ( 10.909613)
nsdd       11.290000   1.210000  12.500000 ( 12.603403)
new_regex  4.200000    0.090000   4.290000 (  4.416512)

Interesting... that's pretty cool. Thanks for sharing!

A pretty big refactoring is on the way. With some performance improvements.

Awesome Sebastian!  When do you think the new version will be pushed?  Just found STTweetLabel and am excited to implement it.

3.1.18 is available with a ton of fixes (auto layout, performances)


Upload private docs

Status
In Progress
Related Issues
related: https://github.com/demisto/etc/issues/30289
Description
Added support for private packs docs
Screenshots

@barchen1 also look at the build. We have some failures for playbooks. Such as:
11:48:54.629980 fail: /home/circleci/project/content-repo/.content-bucket/Packs/SafeBreach_Insights/Playbooks/SafeBreach_Process_Behavioral_Insights_Feed_README.md. Exception: Traceback (most recent call last):
  File "/home/circleci/project/content-repo/./gendocs.py", line 319, in process_extra_readme_doc
    yml_data = yaml.safe_load(yml_matter)
  File "/home/circleci/.local/share/virtualenvs/project-zxI9dQ-Q/lib/python3.9/site-packages/yaml/__init__.py", line 162, in safe_load
    return load(stream, SafeLoader)
  File "/home/circleci/.local/share/virtualenvs/project-zxI9dQ-Q/lib/python3.9/site-packages/yaml/__init__.py", line 114, in load
    return loader.get_single_data()
  File "/home/circleci/.local/share/virtualenvs/project-zxI9dQ-Q/lib/python3.9/site-packages/yaml/constructor.py", line 49, in get_single_data
    node = self.get_single_node()
  File "/home/circleci/.local/share/virtualenvs/project-zxI9dQ-Q/lib/python3.9/site-packages/yaml/composer.py", line 36, in get_single_node
    document = self.compose_document()
  File "/home/circleci/.local/share/virtualenvs/project-zxI9dQ-Q/lib/python3.9/site-packages/yaml/composer.py", line 55, in compose_document
    node = self.compose_node(None, None)
  File "/home/circleci/.local/share/virtualenvs/project-zxI9dQ-Q/lib/python3.9/site-packages/yaml/composer.py", line 84, in compose_node
    node = self.compose_mapping_node(anchor)
  File "/home/circleci/.local/share/virtualenvs/project-zxI9dQ-Q/lib/python3.9/site-packages/yaml/composer.py", line 127, in compose_mapping_node
    while not self.check_event(MappingEndEvent):
  File "/home/circleci/.local/share/virtualenvs/project-zxI9dQ-Q/lib/python3.9/site-packages/yaml/parser.py", line 98, in check_event
    self.current_event = self.state()
  File "/home/circleci/.local/share/virtualenvs/project-zxI9dQ-Q/lib/python3.9/site-packages/yaml/parser.py", line 428, in parse_block_mapping_key
    if self.check_token(KeyToken):
  File "/home/circleci/.local/share/virtualenvs/project-zxI9dQ-Q/lib/python3.9/site-packages/yaml/scanner.py", line 116, in check_token
    self.fetch_more_tokens()
  File "/home/circleci/.local/share/virtualenvs/project-zxI9dQ-Q/lib/python3.9/site-packages/yaml/scanner.py", line 173, in fetch_more_tokens
    return self.fetch_stream_end()
  File "/home/circleci/.local/share/virtualenvs/project-zxI9dQ-Q/lib/python3.9/site-packages/yaml/scanner.py", line 377, in fetch_stream_end
    self.remove_possible_simple_key()
  File "/home/circleci/.local/share/virtualenvs/project-zxI9dQ-Q/lib/python3.9/site-packages/yaml/scanner.py", line 318, in remove_possible_simple_key
    raise ScannerError("while scanning a simple key", key.mark,
yaml.scanner.ScannerError: while scanning a simple key
  in "<unicode string>", line 3, column 1:
    A special feed based triggered j ...
    ^
could not find expected ':'
  in "<unicode string>", line 3, column 119:
     ...  SafeBreach generated indicator.
                                         ^

11:48:54.738093 fail: /home/circleci/project/content-repo/.content-bucket/Packs/IAM/Playbooks/IAM_-_Check_If_User_Should_Be_Terminated_README.md. Exception: Traceback (most recent call last):
  File "/home/circleci/project/content-repo/./gendocs.py", line 319, in process_extra_readme_doc
    yml_data = yaml.safe_load(yml_matter)
  File "/home/circleci/.local/share/virtualenvs/project-zxI9dQ-Q/lib/python3.9/site-packages/yaml/__init__.py", line 162, in safe_load
    return load(stream, SafeLoader)
  File "/home/circleci/.local/share/virtualenvs/project-zxI9dQ-Q/lib/python3.9/site-packages/yaml/__init__.py", line 114, in load
    return loader.get_single_data()
  File "/home/circleci/.local/share/virtualenvs/project-zxI9dQ-Q/lib/python3.9/site-packages/yaml/constructor.py", line 49, in get_single_data
    node = self.get_single_node()
  File "/home/circleci/.local/share/virtualenvs/project-zxI9dQ-Q/lib/python3.9/site-packages/yaml/composer.py", line 36, in get_single_node
    document = self.compose_document()
  File "/home/circleci/.local/share/virtualenvs/project-zxI9dQ-Q/lib/python3.9/site-packages/yaml/composer.py", line 55, in compose_document
    node = self.compose_node(None, None)
  File "/home/circleci/.local/share/virtualenvs/project-zxI9dQ-Q/lib/python3.9/site-packages/yaml/composer.py", line 84, in compose_node
    node = self.compose_mapping_node(anchor)
  File "/home/circleci/.local/share/virtualenvs/project-zxI9dQ-Q/lib/python3.9/site-packages/yaml/composer.py", line 127, in compose_mapping_node
    while not self.check_event(MappingEndEvent):
  File "/home/circleci/.local/share/virtualenvs/project-zxI9dQ-Q/lib/python3.9/site-packages/yaml/parser.py", line 98, in check_event
    self.current_event = self.state()
  File "/home/circleci/.local/share/virtualenvs/project-zxI9dQ-Q/lib/python3.9/site-packages/yaml/parser.py", line 428, in parse_block_mapping_key
    if self.check_token(KeyToken):
  File "/home/circleci/.local/share/virtualenvs/project-zxI9dQ-Q/lib/python3.9/site-packages/yaml/scanner.py", line 116, in check_token
    self.fetch_more_tokens()
  File "/home/circleci/.local/share/virtualenvs/project-zxI9dQ-Q/lib/python3.9/site-packages/yaml/scanner.py", line 223, in fetch_more_tokens
    return self.fetch_value()
  File "/home/circleci/.local/share/virtualenvs/project-zxI9dQ-Q/lib/python3.9/site-packages/yaml/scanner.py", line 577, in fetch_value
    raise ScannerError(None, None,
yaml.scanner.ScannerError: mapping values are not allowed here
  in "<unicode string>", line 2, column 169:
     ... wing fields to make its decision: Employee Status, Rehired Emplo ...
                                         ^

@barchen1 I am looking at the preview site and not seeing the following script documentation: Code42UsernameSearch

Added a fix for private packs Scripts, it should work now

@barchen1 I think you can merge

@glicht I want to merge this PR first, cause I want to test it one more time with the description field fix I added in the upload_docs.py.


openssh key type: ssh-rsa is not supported

Having trouble using priv/pub key to connect using Posh-ssh.  I was under the impression RSA keys were supported - I am using rsa ssh2 4096 bit key.  Any help would be appreciated.
POSH-SSH Version - Manifest   3.0.0      beta1      Posh-SSH
new-session command throws this error:
"new-sshsession : openssh key type: ssh-rsa is not supported"
command resembles -  new-sshsession -computername mysystem -Credential $cred -KeyFile C:\users\jondoe\Documents\SSH_KEY_PRIV.pem
$cred = get-credential ( values supplied are usrename and private key pass phrase)

For RSA it is only the old format, the newer format is still held up as a PR for the library https://github.com/sshnet/SSH.NET/pull/614 https://github.com/sshnet/SSH.NET/pull/614

On Apr 15, 2021, at 11:34 AM, Andrew Roe @.***> wrote:
Having trouble using priv/pub key to connect using Posh-ssh. I was under the impression RSA keys were supported - I am using rsa ssh2 4096 bit key. Any help would be appreciated.
new-session command throws this error:
"new-sshsession : openssh key type: ssh-rsa is not supported"
command resembles - new-sshsession -computername mysystem -Credential $cred -KeyFile C:\users\jondoe\Documents\SSH_KEY_PRIV.pem
$cred = get-credential ( values supplied are usrename and private key pass phrase)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/darkoperator/Posh-SSH/issues/388, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAD7IHS7JEUUIH3BYOMJG43TI4BQTANCNFSM427XWZ3A.

Thank you I didn't realize that ....

@darkoperator Sorry, if I understand it correctly https://github.com/sshnet/SSH.NET/issues/883 was supposed to have solved this issue? And if I understand your comment there 3.0 release is including it and should have this issue addressed?
I'm just confused cause I'm still seeing this with posh-ssh 3.0.0

Still not supported it was mentioned that it was holding release which it was not. So it could be me miss understanding the message
Sent from my iPhone

On Oct 1, 2021, at 11:31 AM, Eugene Tolmachev @.***> wrote:

@darkoperator Sorry, if I understand it correctly sshnet/SSH.NET#883 was supposed to have solved this issue? And if I understand your comment there 3.0 release is including it and should have this issue addressed?
I'm just confused cause I'm still seeing this with posh-ssh 3.0.0
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

Looked up how to create "the old format" (PEM) on a linux machine:
$ ssh-keygen -m PEM -t rsa -b 4096

Is there any plan to support 4096-bit RSA keys?

I know the library supports OpenSSH format, but I do not believe PEM cert v01 is supported.


Improve User Overrides for Keybindings

I'm frustrated with the keybinding interface...
PROBLEMS

Cannot view default JSON
GUI view mixes defaults and user setting, while json view does not. Thus there is no way to reveal the JSON of the default bindings.

Keybinding deletion is too complicated and redundant
Deleting a default binding from the GUI adds an override to my user bindings.
Deleting the same default binding from the GUI adds a duplicate override to my user bindings.
Deleted bindings still appear in the list if bindings in the GUI, leading the user to believe that they are not deleted.

Command discovery is broken
In the GUI view there is no way to discover a command unless a key is already bound it.
In the JSON view... text expansion / autocompletion of the command field mashes together all possible commands and overflows the view. there is no partial autocompletion to discover commands incrementally

SOLUTION
if an overlay system is required... identify keybindings by mnemonic id so that entries the delete bindings added by deeper layers are easier to comprehend. fix the bugs with duplication. expose the default json so that it is discoverable. fix autocompletion.
USE CASE
Try remapping all of your function keys. It is extremely difficult.

Cannot view default JSON

There is an action to see only Default keybindings

There is also a command to open as json file Preferences: Open Default Keyboard Shortcuts

Deleting a default binding from the GUI adds an override to my user bindings.

This is the only way you can delete a default keybinding. Please let me know If you have other ideas.

Deleting the same default binding from the GUI adds a duplicate override to my user bindings.

Please provide me an example to repro.

Deleted bindings still appear in the list if bindings in the GUI, leading the user to believe that they are not deleted.

Can you please be specific. Please give an example.

In the GUI view there is no way to discover a command unless a key is already bound it.

Also please give us an example.

In the JSON view... text expansion / autocompletion of the command field mashes together all possible commands and overflows the view. there is no partial autocompletion to discover commands incrementally

Also please give us an example with screenshot. Easier to understand.


Bump version to 1.0.5

Checklist

[X] Used a fork of the feedstock to propose changes
[X] Reset the build number to 0 (if the version changed)

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


KAFKA-12193: Re-resolve IPs after a client disconnects

This patch changes the NetworkClient behavior to resolve the target node's hostname after disconnecting from an established connection, rather than waiting until the previously-resolved addresses are exhausted. This is to handle the scenario when the node's IP addresses have changed during the lifetime of the connection, and means that the client does not have to try to connect to invalid IP addresses until it has tried each address.
Reviewers: Mickael Maison<EMAIL_ADDRESS>Satish Duggana<EMAIL_ADDRESS>David Jacot<EMAIL_ADDRESS>More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.
Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

This is a backport of 131d475 to 2.3. As with #10061, the conflicts were due to the missing connection timeout config, which was added in 2.7, and didn't meaningfully change the behavior.

Test failures appear to be in unrelated code


Fix invalid return address 0 in GDScript

Fixes #70936, created by 0c15844.
In the past, all method returns would have a temporary return address assigned to it, even if its return type is null. Now, the return address can be empty (Address:NIL, which has an address of 0), but the bytecode still attempts to send the returned value to this address. Address:NIL is the default state of the Address class when using an empty constructor, so sending the returned value here probably messes some stuff up for things that use Address() to represent an empty address (Such as the unary operator).
I'm not too knowledgable on the inner workings of the VM/Compiler, so this may not be the correct fix. The bug is gone and all tests pass, so I assume this was the problem...
If this is not the correct fix, please let me know :+1:

This really only work by accident because the MethodBind call and the ptrcall instructions have the same arguments. It that ceases to be the case in the future this will introduce problems. I also think there are other cases where this is a problem, not only with ptrcall.
In any case, I have a fix for this bug ready: #71107

Superseded by #71107.

Awesome, thanks!


GHC 8.8 compatibility

Incorporates #123 and adds 8.8 travis build.

oops, there are some more 2,15,0 checks left.


testing/remove-mixed-breed

One less thing to worry about - since "mixed breed" testing profile was introduced, we have increased coverage with different profile significantly, and also introduced 4x different testing combinations on libvcx_core level.

Codecov Report

Merging #907 (d0633e7) into main (bb1d3c5) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #907   +/-   ##
=======================================
  Coverage   43.37%   43.37%
=======================================
  Files         438      438
  Lines       34780    34780
  Branches     7580     7580
=======================================
+ Hits        15085    15086    +1
  Misses      15233    15233
+ Partials     4462     4461    -1

Flag
Coverage Δ

unittests-aries-vcx
43.37% <ø> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

aries_vcx/src/common/keys.rs
44.64% <ø> (ø)

aries_vcx/src/core/profile/mod.rs
0.00% <ø> (ø)

aries_vcx/src/utils/devsetup.rs
45.51% <ø> (ø)

... and 3 files with indirect coverage changes


automatic builds when pushed to master branch

see https://docs.docker.com/docker-hub/builds/

this is obsolete now right?


Removed calls to function causing deprecation warning where possible

i removed most deprecated warning only left is hiden=True
I also removed some unreachable code

Hi @07pepa ,
Could you please check the tests. And there are some conflicts.
Thank you for the PR!

is all green https://github.com/07pepa/beanie/actions/runs/8921580966/job/24501959415

@roman-right ?

running ci cd maybe
and @roman-right merging it

@dotKokott can be merge RN


LHC-HCG run 1 combination changes to port to 74X-root6 ?

Creating the PR at the moment even if it doesn't merge, so that we can see what's missing.

Fixed the merge conflicts, and made it compile and passed a few basic tests.

This all looks good, thanks! There are a couple of issues where an earlier commit has been included in this branch by hand which first needs to be resolved. As an example, in MultiDimFit, the --forceFirstFit is not used anywhere although the option is there. I'll check for any more and merge after that

Thanks for this, I've tested out a few toys and things seem to behave well.
I tagged the version of 74x-root6 before the merge as v.6.2.1 in case we
spot something later
On Sat, Apr 23, 2016 at 4:46 PM, Giovanni Petrucciani <
<EMAIL_ADDRESS>wrote:

Fixed the merge conflicts, and made it compile and passed a few basic
tests.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/cms-analysis/HiggsAnalysis-CombinedLimit/pull/303#issuecomment-213752494


What type exactly supports the Input of Image Schema??

Hi, I'm currently trying to put images into my base pdf.
I put my images from my local computer and convert them into base64 string and it works well.
But when I try to put images downloaded from the Amazon S3 storage, it doesn't work well.
I think the reason it doesn't work is that the content-type of images downloaded from S3 is octet-stream.
I tried to convert content-type of these images into image/jpeg or something, it shows just blank.
Is it correct that pdfme doesn't support application/octet-stream;base64 string and only supports image;base64 string?

Hey @pmw1407 I met some issues to display correctly my input images.
I managed to get a rid of it like this.
Here is my fetcher.
export const fetchImage = async (url: string): Promise<string> => {
  try {
    const response = await fetch(url);
    const buffer = await response.buffer();
    return buffer.toString("base64");
  } catch (error) {
    console.error(error);
  }
};

And here is when I generate it:
const image = await fetchImage(IMAGE_URL);
const pdf = await generate({
    template,
    inputs: {
        image1: `data:image/png;base64,${YOUR_BASE64_STRING}`
    },
    options: { font: fonts },
  });

Hey @pmw1407 I met some issues to display correctly my input images.
I managed to get a rid of it like this.
Here is my fetcher.
export const fetchImage = async (url: string): Promise<string> => {
  try {
    const response = await fetch(url);
    const buffer = await response.buffer();
    return buffer.toString("base64");
  } catch (error) {
    console.error(error);
  }
};

And here is when I generate it:
const image = await fetchImage(IMAGE_URL);
const pdf = await generate({
    template,
    inputs: {
        image1: `data:image/png;base64,${YOUR_BASE64_STRING}`
    },
    options: { font: fonts },
  });

Thanks bro I'll try this!!


Spanish translation strings

spanish strings
https://github.com/btcontract/lnwallet/issues/81

I think you should translate "Lightning" to "Relámpago".

Bitcoin is easy to pronounce for Spanish speakers, Lightning isn't.
Actually Portuguese is my primary language, and I think "Relámpago" fits better, as it is a longer name, but let's see if something evolves naturally. At least I think we should remain open to the possibility of translating "Lightning" if we see that wide adoption will depend on that.

exactly, I wanna see how things are going, if we have to change it we do it, let's try it in testnet and hear what spanish speakers says, and then we change it or not


Update issue templates

Add template for new issues

Are we still able to open other types of Issues that are not bugs with this template?


Bug: Changing Curtain Position with BLE resets to old position after a second

Describe The Bug
Changing Curtain Position with BLE resets to old position after a second
To Reproduce
Have Curtain Position at 53% and then change to 100% using BLE. The curtain move, then resets to 53% in Homekit directly and the curtain stops moving.
Expected behavior
Curtain moves to target position; homekit updates to target position (100%). Curtain doesn't stop.

            },
            "options": {
                "devices": [
                    {
                        "deviceId": "E3E1DC747270",
                        "configDeviceName": "Closed Window Curtain",
                        "configDeviceType": "Curtain",
                        "connectionType": "BLE",
                        "curtain": {
                            "set_minStep": 1,
                            "set_min": 5,
                            "set_max": 95,
                            "hide_lightsensor": true
                        },
                        "logging": "debug"
                    },

Screenshots
No response
Device & Model
Switchbot Curtain 2, firmware 6.0
Node.js Version
v16.19.0
NPM Version
v8.19.3
Homebridge Version
v1.6.0
Homebridge Switchbot Plugin Version
v2.4.1-beta.7
Homebridge Config UI X Plugin Version
v4.50.2
Operating System
Raspian

can you try v2.5.0

duplicate to #666


Licensing question

Hello again :)
We are looking to use dlib in our monitoring agent (netdata) to power some anomaly detection features on the agent.
I see dlib is boost and we are GPLv3. I'm just starting process to make sure we are compatible etc. which i will follow up with our legal team as it's not anything i have a great understanding of myself at all.
But i was just wondering if you see any potential issues with netdata making use of dlib in this way? Or have any precedence of other example projects that might have used dlib in similar ways etc.
Many thanks for the project, love it!

Na, you can use dlib with that. There is no conflict.

Hello Davis,
May it is possible to get advice about pretrained models?
There are restrictions for landmark model due to dataset restrictions.
But are pretrained detectors restricted too? Like Hog and CNN one?
Or recognition model?
Thanks,
Valentina

I see, Davis, thank you!


Variables do not come out normally because metadata is wrong in Cloud Functions

This issue is a sub-issue of

#19

[Variables]

It was confirmed that the variables were output only when the variables were changed from the dict type to the list of dict as shown below.
AS-IS
{
    'labels': { 'env': 'dev' }
}

TO-BE
{
   'labels': [{'key': 'env', 'value': 'dev'}]
}

It works fine as intended.


Rewrite of inventory functionality with dramatically reduced number of stat calls.

Also make remote and local inventory run asyncronously via coroutines.
Asynchronously retrieve mtimes (via coroutines) before needrun computation.

This rewrite has been greatly inspired by PR #675 by @mhulsman. It this previously merged PR with a simplified codebase, uses coroutines instead of threads and futher reduces the number of stat calls.
This PR also changes Snakemake's required Python version to >=3.7 because of the coroutine usage.

Very nice idea to use the job files to further reduce stat usage.  I quickly scanned through the code, and I noticed that is_newer is not cached now. This is actually where  the majority of the 'stat' time is spent (see last comment on PR #663 for some benchmarking).  In PR #675, this required a separate mtime_target cache, due to the handling of mtime of symbolic links and their targets.

I'll have a look.

Thanks for pointing me to that. Now, is_newer properly uses mtime, and mtime is cached for local, local_target and remote in one object. The rewrite not only leads to properly cached is_newer, it also reduces the number of stat calls for that to 1 instead of 4.


feat(radio-group): support options and label-key and value-key

Checklist
List of tasks you have already done and plan to do.

[ ] Fix linting errors
[ ] Tests have been added / updated (or snapshots)

Change information
Describe your modifications here.
Issues
The issues you want to close, formatted as close #1.
Related Links
Links related to this pr.

参考 https://github.com/varletjs/varlet/commit/c1501ab5a6dea0129601408af467b4c507ec5f26，补充缺失的 style import。

参考这个 commit，补充缺失的 style import。

done


x/build: one freebsd-arm-paulzhol builder is missing

From https://farmer.golang.org:
host-freebsd-arm-paulzhol: 0/0 (1 missing)

Perhaps the builder needs attention or its ExpectNum configuration value is out of date. @paulzhol, are you able to take a look?

Sorry I was doing some maintenance and upgrading the host, but it took longer than expected. I've restored it for now and will continue during the weekend.

No problem at all, and thanks for the update. This issue was mostly to ensure it wasn't gone without you realizing that. Since it's back, marking as fixed.


test: fix appveyour flakiness

Crashpad sometimes prevents us from removing a folder in tests.
References #2778.

TBR: @JoelEinbinder


Blog: The Triage Rhyme

A fun little ditty to aid triagers in remembering one developer's take on some key aspects of the triage process.
Description of change

Checklist

[ ] npm test passes
[ ] documentation is changed or added (if applicable)
[ ] permission has been obtained to add new logo (if applicable)
[ ] contribution guidelines followed here

Is it normal that all links point the file index.md? :thinking:

Is it normal that all links point the file index.md? 🤔

I'm going to say no - @adamfarley what's the idea of the index.md links?

Is it normal that all links point the file index.md? 🤔

I'm going to say no - @adamfarley what's the idea of the index.md links?

It's the method I used to create easily-identifiable tooltips for supplimentary information. The links themselves are incidental, so I used index.md because it keeps you on the blog page while still being a valid link (to keep the linter happy).
Happy to use a different method for the supplimentary info if anyone has ideas.

:wave:  Maybe you can:

create internal links on images or texts as anchors, links look like #something
use this anchors as links for your "tooltips".

e.g.
Define an anchor:
[my text or image](#tress)
Use this anchor:
is for TReSS, so go take a [gander](#tress "Identify failed pipelines via TRSS.").

FYI: On vacation. I will make any changes when I return in 2 weeks, if nobody beats me to it. :)

@adamfarley merge conflicts. Do you still want this to be merged? I might suggest that it makes more sense to go in a wiki somewhere for maintainers as it has little meaning to our external users

ping @adamfarley

I'm going to close this for now, feel free to re-open it


Support for thenlper/gte-large

Hello - Wondering if it's possible to add the gte class of models? Thank you!

Model links which we need to assess for quality and speed:
https://huggingface.co/Qdrant/gte-large-onnx-Q
https://huggingface.co/Qdrant/gte-small-onnx
https://huggingface.co/Qdrant/gte-large-onnx
https://huggingface.co/Qdrant/gte-base-onnx

Prefer gte-large-onnx over gte-large-onnx-Q


Zqs 1055 create circuits guide

Description
Include description of feature this PR introduces or a bug that it fixes. Include the following information:

Context: why is it needed? In case of bug, what was the cause for the bug?

This guide gives significant information on using Circuits in Orquestra

Concise description of the implemented solution.
If any dependencies are added, list them and justify why they are needed.

Please verify that you have completed the following steps

[x] I have self-reviewed my code.
[x] I have included test cases validating introduced feature/fix.
[x] I have updated documentation.

@mstechly

Minor comments, overall looks great! One thing that I feel like we're missing is a an explanation how we create gates. I mean: why one would do RZ(1.234)(2) and not RZ(1.234, 2) (as they do in pyquil AFAIR). I know the order of the arguments has been somewhat confusing to people in the past, so it's worth explaining.
Also, I wonder whether it could use a "software nerds" section, which explains in more detail how the implementation works under the hood. You know, factories and all the goodies. I don't know if it's worth it though?

for why we create gates that way: I actually don't know! Why do we do it that way? I can explain how we create them, but I don't know why 😅
for the software nerds section: I think if you're nerdy enough to want to know that and understand what we put there, you'll more so just dig into the code. Maybe it would be worth having an overarching "for software nerds" page that talks about general info? rather than have a different "for nerds" section in each guide

@1ethanhansen I'd leave the "Why gates are this way" section to @dexter2206 :)
Good point, source code is a better place to look for such info 👌


x/tools/gopls: the code in the workspace failed to compile

What version of Go are you using (go version)?

go version go1.15 windows/amd64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
set GO111MODULE=on
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\www\AppData\Local\go-build
set GOENV=C:\Users\www\AppData\Roaming\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=E:\GoProject\go\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=E:\GoProject\go
set GOPRIVATE=
set GOPROXY=https://goproxy.cn,direct
set GOROOT=E:\Go
set GOSUMDB=sum.golang.google.cn
set GOTMPDIR=
set GOTOOLDIR=E:\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=NUL
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Users\www\AppData\Local\Temp\go-build025204942=/tmp/go-build -gno-record-gcc-switches

What did you do?
when I use vscode open my gopath folder, it shows that The code in the workspace failed to compile (see the error message below) and go [-e -json -compiled=true -test=true -export=false -deps=true -find=false -- ./]: exit status 1: go: cannot find main module; see 'go help modules': packages.Load error.

What did you expect to see?
What did you see instead?

Are you using the vscode-go extension? If so, what version is it?
Have you tried the troubleshooting steps described in https://github.com/golang/tools/blob/master/gopls/doc/troubleshooting.md?
/cc @stamblerre

Looks like GO111MODULE=on but there is no go.mod (i.e. GOMOD=NUL).
Please see https://github.com/golang/vscode-go/issues/275#issue-648468015 and make sure to open vscode from the folder with go.mod file.

i have met the same problems, version 0.16.1.  i have set go.mod file correctly(GOMOD is ok).  But the promotion is always occured when i open modify etc...

@mrlay: Please provide your gopls logs. Information on how to capture them can be found here.

I have solved this question

i have met the same problems, version 0.16.1. i have set go.mod file correctly(GOMOD is ok). But the promotion is always occured when i open modify etc...

I have solved this problem in vscode.In setting json,I add  "go.buildOnSave": "workspace",

Glad you were able to solve it. I'm going to close this issue. @mrlay, please file a new issue to continue this discussion.

I also encountered the same type of error in the vscode and go plugins
my go env

set GO111MODULE=on
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\admin\AppData\Local\go-build
set GOENV=C:\Users\admin\AppData\Roaming\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=E:\Go
set GOPRIVATE=
set GOPROXY=https://goproxy.cn,direct
set GOROOT=D:\Go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=D:\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=NUL
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Users\admin\AppData\Local\Temp\go-build384423178=/tmp/go-build -gno-record-gcc-switches

The code in the workspace failed to compile (see the error message below). If you believe this is a mistake, please file an issue: https://github.com/golang/go/issues/new. go [-e -json -compiled=true -test=true -export=false -deps=true -find=false -- ./]: exit status 1: go: cannot find main module; see 'go help modules' : packages.Load error

@PICKQUE: Please make sure to open your workspace to your module root (the directory containing the go.mod file). This is currently a requirement of gopls, but we're working on changing that in future versions. If that doesn't resolve the problem, please file a new issue.

@kittyhappy  thanks your advice, which help solve it.  @PICKQUE you can try create a  *.code-workspace project files, and add the configurations which @kittyhappy adviced, may be the case would be solved.

@PICKQUE: Please make sure to open your workspace to your module root (the directory containing the go.mod file). This is currently a requirement of gopls, but we're working on changing that in future versions. If that doesn't resolve the problem, please file a new issue.

i'm sure the root directory exist the go.mod and the go version is 1.15(i'm upgrade yesterday，but it's not work

Looks like GO111MODULE=on but there is no go.mod (i.e. GOMOD=NUL).
Please see golang/vscode-go#275 (comment) and make sure to open vscode from the folder with go.mod file.

Wonderful! Solved my problem!

@PICKQUE: Please make sure to open your workspace to your module root (the directory containing the go.mod file). This is currently a requirement of gopls, but we're working on changing that in future versions. If that doesn't resolve the problem, please file a new issue.

I have sloved this problem by using go mod init command ;

When I was developing Golang with Vscode on MacOS, vscode prompt  "The code in the workspace failed to compile (see the error message below). If you believe this is a mistake, please file an issue: https://github.com/golang/go/issues/new. go [-e -json -compiled=true -test=true -export=false -deps=true -find=false -- ./]: exit status 1: go: cannot find main module; see 'go help modules' : packages.Load error"
I have tried all the above solutions, but they still don't work. I am very upset. What should I do

@wenchao5211: Please follow the steps in the troubleshooting guide and file a new issue so we can help you understand the problem.

I had the same problem. I found out that if first ran: go module init ....... Then found out that I had to set GO111MODULE to on. Still the same error.
When removing the go.sum file  and re running go module init .......  Error was gone.

I also have this problem. How can I solve it?
The code in the workspace failed to compile (see the error message below). If you believe this is a mistake, please file an issue: https://github.com/golang/go/issues/new. go [-e -json -compiled=true -test=true -export=false -deps=true -find=false -- ./]: exit status 1: go: cannot find main module; see 'go help modules' : packages.Load error

Unsupported
Open a directory that contains a module in a subdirectory. gopls will not work in this case.

For vscode I have a workaround, do not know if this work for other editors.
My directory structure is:
Projects
  Someproject1
    microservice1
      go.mod
      go.sum
      main.go
    microservice2
      go.mod
      go.sum
      main.go
  Someproject2
  ...

opening "Somepoject1" in vscode causes a problem.
To solve this I have made a second directory structure:
Workspaces

If i start working on a project for the first time I open the respective directory in "Workspace"s  in vscode. Then I save the workplace in the same place. Then I add al the microservice directories from the corresponding project directory in "Projects" to the workspace. When closing the workspace I save it.
If I want to start working on an existing workspace I choose open workspace and choose the right workspace file.
it's a little bit of work to setup but it works.
no errors any more

Sorry, I got it resolved, but thank you very much!
---Original---
From<EMAIL_ADDRESS>Date: Tue, Nov 17, 2020 17:35 PM
To<EMAIL_ADDRESS>Cc: "Comment"<comment<EMAIL_ADDRESS>Subject: Re: [golang/go] x/tools/gopls: the code in the workspace failed to compile (#40790)
Unsupported
Open a directory that contains a module in a subdirectory. gopls will not work in this case.
For vscode I have a workaround, do not know if this work for other editors.
My directory structure is:
Projects   Someproject1     microservice1       go.mod       go.sum       main.go     microservice2       go.mod       go.sum       main.go   Someproject2   ...
opening "Somepoject1" in vscode causes a problem.
To solve this I have made a second directory structure:
Workspaces
If i start working on a project for the first time I open the respective directory in "Workspace"s  in vscode. Then I save the workplace in the same place. Then I add al the microservice directories from the corresponding project directory in "Projects" to the workspace. When closing the workspace I save it.
If I want to start working on an existing workspace I choose open workspace and choose the right workspace file.
it's a little bit of work to setup but it works.
no errors any more
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.


add kafka-msk (TLS) capability

What
bump version of dp-kafka to TLS-enabled
add config for kafka TLS to this app
How to review
check still runs with old and new kafka
Who can review
! me

sorry, Sandy, I just realised I'd not commited some changes that you asked for...


user.getUser broken when using expand param

This commit adds the expand param https://github.com/floralvikings/jira-connector/commit/ea53fd8fbe9431fd2106551587eff8409d96f8a5 but that causes an authentication issue when hitting jira.
This is because the docs say to provide an expand object. This is similar to getIssue but it gets iterated and parsed into a string over there. https://github.com/floralvikings/jira-connector/blob/master/api/issue.js#L995
The user methods do not have a buildRequestOptions function so I've fixed this by just iterating over the expand fields in the getUser function. https://github.com/rjgoldsborough/jira-connector/tree/fix-user-expand.
Let me know if you'd prefer a buildRequestOptions in the user file or maybe it's time to move it to the jiraClient file like the makeRequest function.

Yeah buildRequestOptions should probably be in jiraClient; when I initially wrote most of these functions, I don't think I realized that the expand parameter could be used in so many places.  I'll merge your PR for now and look into making the buildRequestOptions function more generic; I don't have a testing JIRA project set up anymore, though, so it might take me a while to get the code all tested.

Great, thanks. I have a test jira and am actively working with jira-connector so I may take a crack at adding this in more generically.


Error: Minified React error #130; visit https://reactjs.org/docs/error-decoder.html?invariant=130&args[]=undefined&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

Describe the bug
So I followed a tutorial to create a new custom widget for the cms but after I compile gives me an error when I access to the netlify cms like the title shows.
Here is the tutorial: https://dev.to/room_js/create-a-custom-widget-for-netlify-cms-4gl9
To Reproduce

Create a control widget
Create a preview widget
Register the widget
Add the field to the schema

Expected behavior
Shows the custom widget(the editor) and work as expected.
I assume this tutorial is out of date so if so you could give me support in that sense.

Hi @miguelt1, if you follow the error link you can see the error:

It looks like the custom widget is trying to render an undefined value.
Can you share a public repo reproducing the issue? I believe this doesn't happen with every custom widget, so the reproduction scenario you shared only works with the specific widget you're building.


Why two separate libraries for result and maybe

My question concerns the initial decision to split result and maybe into two separate repositories/libraries. From my understanding, both encapsulate the concept of railway-oriented programming. I believe it would be much simpler if they were merged into the result library, as I currently need both in my project.
I'm highlighting this issue because I encountered problems running pytest on this library. Specifically, rustedpy-maybe is defined as maybe under the src directory. As a result, pip install -e . doesn't work correctly since it tries to find rustedpy_maybe under src, fails to locate it, and causes conflicts. I have already merged the two projects locally, but this isn't backwards compatible because instead of using from result import *, you now have to use either from result.result or from result.maybe. If we agree to merge these two projects, we need to decide on the approach. We could maintain from result import * and add from result.maybe separately, but I believe it's better to import explicitly.
What are your thoughts on this? I've already created a function maybe(v: T | None) -> Maybe[T] (issue #4) and two decorators as_maybe and as_async_maybe (issue #1). Everything is tested and type-hinted, so if we decide to proceed, I can submit a comprehensive pull request to the result library containing all these changes.
Alternatively, if you prefer to first implement these changes in the current library before considering a merge into result, we need to address the naming issue. One solution could be to rename src.maybe to src.rustedpy_maybe, or perhaps you have another workaround in mind?

Currently the projects are setup to be ship separately, result and rustedpy-maybe (I failed to contact the owner of 'maybe' PyPI project, so we weren't able to acquire that name).
I don't have any intention to merge the two projects as you mention, I don't think there's any need currently, but that may change in future depending on how things go. But right now, I'm going to keep the separate.
We may benefit slightly from reducing some duplicate project files if the two were merged, but given this library is not used by many people, I don't want to put in the effort doing all that work until it's absolutely necessary or someone (such as yourself perhaps) volunteers because you're actually using this library in a real project.
If anyone wants to use both result and rustedpy-maybe, they'll need to just install both. I don't want to create a single library with multiple things in it (result, maybe, plus more things in the future?). Maybe this will change in the future, but not right now.
We also have a really good name, result, but that name doesn't make sense if we put the maybe inside the same result library.

initial decision to split result and maybe into two separate repositories

There was no decision to split. Result was created back in like 2016 by the original author and this maybe library was created last year because someone asked for it. This maybe library is used by very very few people: https://pypistats.org/packages/rustedpy-maybe compared to result: https://pypistats.org/packages/result

I'm highlighting this issue because I encountered problems running pytest on this library. Specifically, rustedpy-maybe is defined as maybe under the src directory. As a result, pip install -e . doesn't work correctly since it tries to find rustedpy_maybe under src, fails to locate it, and causes conflicts

The issue you're describing isn't what I've encountered before. Here's what I did,
python -m venv venv # create a new virtualenv

source venv/bin/activate # activate the virtualenv

make install # I just added the Makefile now, see https://github.com/rustedpy/maybe/blob/master/Makefile

make test # Should work correctly

cd result
pip install -e . # now you should be able to install result in the same virtualenv as well

It could be you've got a very polluted virtualenv (or you're not using a virtualenv at all!?). Always use a virtualenv (or a virtualenv manager like Poetry), Python's dependency system isn't great and running pip without a virtualenv is going to cause problems eventually with your OS.
Run pip list to see what's installed in your virtualenv (or in your non-virtualenv environment if you're not using a virtualenv)

If you have any problems while working on a PR for specific issue, just post a comment there and I'll try to help.


Added editorconfig rules

@nucliweb can you explain this a bit?

Sorry @antiboredom
With these rules we can ensure consistency in the format of all files.
This can prevent differences in indents, charset, end of line, etc... in the commits and PR
We have plugins for a lot of editors in http://editorconfig.org/

Ah - I see! So this is for us as developers/contributors rather than as rules for the user-facing side?

Yes.
Thanks for merge ;)


5.3 - inline editable blocks broken with custom admin route

Module version(s) affected
5.3.1
Description
If a custom admin route is set, inline editable blocks cannot be saved. Version 5.3 of this module assumes the admin route is /admin
How to reproduce
Set a custom admin route.
Add a Content Block to an element area.
Make changes to the content block and try to save it.
Browser console shows a 404 error and the changes are not saved.
Possible Solution
Update line 245 of ElementalAreaController.php to:
$form->setFormAction(AdminRootController::admin_url("$urlSegment/elementForm/$id"));

Additional Context
No response
Validations

[X] Check that there isn't already an issue that reports the same bug
[X] Double check that your reproduction steps work in a fresh installation of silverstripe/installer (with any code examples you've provided)

PRs

https://github.com/silverstripe/silverstripe-elemental/pull/1282

PR merged. This will be automatically tagged by GitHub Actions.


OnReceiveBytes does not seem to receive anything

Hi,
just started to explore this useful plugin.
Sending data via Emit() works perfectly, but I am unable to receive any data. IP / Port is set correctly. Wireshark shows that data is arriving on the machine.
I followed all explanations but no success.
Is there anything I must do except set IP / Port and wait for the OnReceiveBytes() event?
Thanks in advance,
best regards,
fwerre

Make sure your component is set to auto-listen to your port in default properties, or if you don't use that, start listening manually as described in https://github.com/getnamo/udp-ue4#how-to-use---basics

Thanks getnamo,
I tried both, but no success. It seems that OnReceiveBytes() never fires an event.
Is there any way to debug this? As said, data is definitely arriving on the machine / IP / port
Fwerre

I'd recommend testing it locally on the same machine first with e.g. https://gist.github.com/getnamo/8117fdc64209af086ce0337310c52a51 and sending data and waiting for echo response. That should show both paths working. If it works locally, try again over LAN, then if that works try over public IP. This way you can ensure there isn't a firewall blocking the data. Also keep in mind that ports are exclusive, so if another program is using that port it may be stealing it from your unreal project when it attempts to listen to it.

Thanks a lot, the node echo server was really helpful to prove all is working correctly.
The reason for my problem was I messed up the receive / transmit ports,
Thanks again for your help!
fwerre


support multiple registers

This introduces a new configuration item otherRegisters, which
allows you to specify a map from register names to database
configurations for other registers that this app can serve.
The app decides which register to use on a per-request basis, by
inspecting the X-Forwarded-Host or Host headers, and pulling out the
bit before the first dot.  If it matches a named register in
otherRegisters, it serves from that register; otherwise, it serves
from itself.
To do this, there is a new class AllTheRegisters, which allows you to
pick out a register using its getRegisterByName() method.  This
returns an EverythingAboutARegister instance.
EverythingAboutARegister has all the things you need for an individual
register instance - MemoizationStore, DBI, RegisterMetadata, etc.
I also removed RegisterNameConfiguration, as that is no longer a
globally unique thing.  You now need to inject
EverythingAboutARegister or RegisterData and get the name from that.
All this code was just a first attempt and a proof-of-concept.  Here
are some outstanding questions:

what's our strategy to move forward with this?  do we want to
deploy this to multiple environments?
do we want to stick with the "default register" model? I did this
so that we could make a forwards-compatible change to the
configuration file format, but should we ensure that each register
is explicitly called?
have we got the right abstractions here?  Is
EverythingAboutARegister really duplicating the responsibility that
PostgresRegister already has?  Should those two classes be merged?
what's going on with all this dependency injection stuff? Can we
simplify it, by getting rid of some of the Factory<>s and
Provider<>s?

I've tested this locally, manually, but there are some bits I haven't
tested:

I haven't tested proofs, to ensure that the MemoizationStores are
truly isolated from each other

Can we match the whole Host / X-Forwarded-Host header so that we can support multiple discovery environments or multiple environments from a single system?

@andyjpb can you give an example of what you mean? I'm not sure I understand.

@michaelabenyohai mentioned that we need to ensure the flyway migration script still works, which currently I think it doesn't.

not ready for merging. closing for the moment


Allow embedders to specify arbitrary data to the isolate on launch.

Currently, only certain fields are available to the isolate on launch. These fields are currently present in the RuntimeController::WindowData struct. While the data in that struct is meant to persist across isolate restarts, the engine doesn't care what that data looks like. Also, when embedders want to add new fields to that struct, they need to patch the engine. The engine should instead deal with data mappings directly and function as a dumb pipe for launch information specified by the embedders and made available to the isolate on launch.

/cc @HansMuller @matthew-carroll

FYI this will get pushed back due to a slew of recent high-priority internal issues. I'm adjusting the milestone to Sept 2019.

This is patched in https://github.com/flutter/engine/pull/13047


Getting EXC_BAD_ACCESS sometimes

Hi, In my project I have pretty big store and sometimes when I am trying to run the app in XCODE I get EXC_BAD_ACCESS error and the app crashes. I noticed that if I am cleaning the app it works again but the EXC_BAD_ACCESS is coming back in a later stage. I am little bit worried that it will happened in production to users that will use the app so I wanted to know if someone here is familiar with this issue?
This is my AppState:

As you can see from the attached image its pretty big (and it will become bigger)
And the crash occur when the app tries to subscribe to the store for the time

Thanks!

I wonder if this has something to do specifically with ReSwift-Router? Does the crash ever occur for other store subscriptions?
For comparisons sake, I've worked on a ReSwift app with an AppState thats over twice the size of your screenshot and have not experienced a crash like this.

I had it when I was accessing the store.state from my reducer (which you should never do).

Hi @mjarvis there is a chance that it is related to the Router since I am also using heavily in Router in my app. And yes sometimes it occur in one of my action creators (the EXC_BAD_ACCESS raised when I return nil from the first action creator that I use in the app)
@Dimillian - for sure I am not calling store inside one of my reducers since it's a REDUX bad practice

Hi Guys, I am still getting EXC_BAD_ACCESS from time to time. If I clean the project and build it again it is not happening but after several days it crashes again. This is very strange issue and it's very hard to debug it. (I tried to enable zombies, perform analyse to the project but everything seems to be ok)

I was facing this in my last app which was developed by 3 people. We faced this because sometimes we dispatched actions and subscribing in different queues by mistake which is difficult to track. Now we didn't face this in our new project since we subscribe and dispatch in main queue most of the time. If we really needs to dispatch actions in a private queue, we would make sure that we subscribed in the same queue.


Access to extern crates through prelude is experimental when using pyclass in module

For whatever reason, using #[pyclass] from a separate module file (i.e. not in the lib.rs root file), requires the extern_prelude feature to be enabled in lib.rs, though it's not entirely clear why this is.
The error message is quite confusing, so if it can't be fixed, it might be worth documenting the fix somewhere. True, the compiler error does tell you to enable the feature, but it's unclear that the feature must be enabled in the root file as opposed to in the file generating the error. Googling for extern_prelude gives almost no explanation of this error, but it seems like it has to do with the use of something like pyo3::prelude::blah outside of a use statement. I'm guessing that happens somewhere in what the #[pyclass] macro expands to.
Reproducing
cargo new --lib eprelude && cd eprelude
Cargo.toml:
[package]
name = "eprelude"
version = "0.1.0"
authors = ["Author<EMAIL_ADDRESS>
[dependencies.pyo3]
version = "0.5.0-alpha.1"

lib.rs:
#![feature(specialization)]
// Including this feature here fixes the problem:
// #![feature(extern_prelude)]

extern crate pyo3;

pub mod foo;

foo.rs:
use pyo3::prelude::{pyclass};

#[pyclass]
pub struct Foo {}

The error message is misleading here; The problem is that the generated code use std:: instead of ::std::


Highlight dates

This just adds another parameter highlightDates to the DatePicker component which accepts an array of Moment objects representing the dates to be highlighted.
Highlighted dates will display with a green background in the calendar.
I've used this in my own log/journal app to indicate days that already have existing entries.

Current coverage is 90.67% (diff: 75.00%)

Merging #540 into master will increase coverage by 0.08%

@@             master       #540   diff @@
==========================================
  Files            10         10
  Lines           340        343     +3
  Methods          14         14
  Messages          0          0
  Branches         52         53     +1
==========================================
+ Hits            308        311     +3
  Misses           14         14
  Partials         18         18

Powered by Codecov. Last update 9d8da30...fb16ead

I like this, this may warrant a new example on the example site (not blocking this PR). Can you please rebase so this is ready to merge?

Thanks Martijn. I went ahead and updated the docs and examples, then rebased and squashed.

Sorry,  I merged again a PR that affects your code. I'm really sorry! If you have no time to update the PR again, I can try doing that before I merge it in. Also, is there a way increase the code coverage of the touched code? It seems that it doesn't hit the target of 75%.

No worries! I'll have a go at it tomorrow.

Okay, rebased and fixed the patch coverage. Took the highlightDates parameter out of date_input.jsx as it wasn't actually doing anything there, and so wasn't testable.

Awesome!

I'll release this soon!


Binding Quickstart - which input and output should we use?

Per this pool request (https://github.com/dapr/docs/pull/2368) we created a Quickstart for Bindings using Kafka for both input and output. This is not ideal as the functionality is the same as the PubSub Quickstart. I am researching other options and will suggest them on this issue and new pull request.

As a team we have been going with the following:

input: cron (system)
output: postgresql

Bindings are typically about inputs and outputs from 'external things'.  We like these because the amount of setup and account hookup is extremely low.
Thoughts?

Per your PR this is live now!
https://docs.dapr.io/getting-started/quickstarts/bindings-quickstart/


Overview of accepting businesses in a chosen area by map

As an owner of a EAK, I want to get an overview of all accepting businesses in a chosen local area on a map, so that I know where I can benefit from discounts.
Acceptance criteria:

[X] ~Local area could be chosen by PLZ~
[ ] Local area could be chosen by positioning function of the smartphone
[ ] Accepting businesses are point out by dots on the map

Technical tasks: #25, #26, #27

Zip code search was migrated to #44.


Upgrade to reel 0.6.0

@ctso I think 0.6.0 is out now: https://rubygems.org/gems/reel/versions/0.6.0
Would it be related to https://github.com/berkshelf/berkshelf-api/issues/206 ?

@scalp42 yes, definitely related to #206.  Updated PR to use reel 0.6.0.
fwiw - I've been running a berkshelf-api server for 3 weeks now with this patch, no issues.

I see that master has been updated.  Sorry for the noise :)
closing


Button colors doesn't respect current theme

I tried to implement a simple confirmation dialog with CoreDialog, here's what I get:

Despite that the primary color is blue, the button that showed is purple, and there are no parameters I can pass to customize it.
I use Material2. Do you have any solution?

This library uses MD3. Mixing it with MD2 leads to issues with colors.
If more people request it, I might support MD2 as separate dependencies.

Yes please. I've considered to use MD3 before, but sadly some components hasn't been supported yet.

Workaround
You can add Material3 dependency and use it in your theme:
private val LightColorPalette = lightColors(
    primary = BrandBlue,
    primaryVariant = BrandBlue,
    secondary = BrandYellow,
    onPrimary = Color.White,
    onSecondary = Color.White,
    error = Red,
    onError = Color.White
)

@Composable
fun AppTheme(content: @Composable () -> Unit) {
    MaterialTheme(
        colors = LightColorPalette,
        typography = Typography,
        shapes = Shapes
    ) {
        androidx.compose.material3.MaterialTheme(
            colorScheme = androidx.compose.material3.MaterialTheme.colorScheme.copy(
                primary = LightColorPalette.primary,
                primaryContainer = LightColorPalette.primary,
                secondary = LightColorPalette.primary,
                secondaryContainer = LightColorPalette.primary,
                tertiary = LightColorPalette.secondary,
                tertiaryContainer = LightColorPalette.secondary,
                onPrimary = LightColorPalette.onPrimary,
                onSecondary = LightColorPalette.onPrimary,
                onTertiary = LightColorPalette.onSecondary,
                error = LightColorPalette.error,
                onError = LightColorPalette.onError,
                surface = LightColorPalette.surface,
                background = LightColorPalette.background
            ),
            androidx.compose.material3.MaterialTheme.shapes.copy(
                small = Shapes.small,
                medium = Shapes.medium,
                large = Shapes.large
            ),
            content = content
        )
    }
}

Theming Guide.
You can also use Material3 Theme Builder to generate M3 theme.

it's works, thanks

what color is used for what?  primary = LightColorPalette.primary,
primaryContainer = LightColorPalette.primary,
secondary = LightColorPalette.primary,
secondaryContainer = LightColorPalette.primary,
tertiary = LightColorPalette.secondary,
tertiaryContainer = LightColorPalette.secondary,
onPrimary = LightColorPalette.onPrimary,
onSecondary = LightColorPalette.onPrimary,
onTertiary = LightColorPalette.onSecondary,
error = LightColorPalette.error,
onError = LightColorPalette.onError,
surface = LightColorPalette.surface,
background = LightColorPalette.background
I want to know for calendarview I need to change all the purple colors to a different one .


how to convert inception-resnet-v1 model from tensorflow to caffe?

how to convert inception-resnet-v1 model from tensorflow to caffe? pls help me

Hi @LeeTaiTai , the tensorflow README has a very similar example and you can refer to it. Thanks!


Cannot find a method to refresh an access token

There is the generateAccessToken method of the ApiClient for generating an access token from the authorization code.
There is also the platform documentation's "Use refresh tokens" section that says that changing the grant_type from authorization_code to refresh_token and supplying a refresh_token instead of code param should make the same flow work for refreshing one.
There is however no way that I can see to refresh a token with the available methods in this package.

Am I just missing it?
Is it not included for a reason? (the php client seems to have it, the java client seems to be also missing it)
Can we add it? If so, made PR #282 for it.

Hello @Chee7ah thank you for reaching out on this topic. We are looking into extending this feature across all of our SDKs


Remove serde_test::Token::EnumStart, rename EnumMap*

Noted in #794.
EnumStart is only used by deserialize, which means that it can't be used in assert_tokens. Its use case is covered by the other Enum*Start tokens, and in fact, it's more confusing because it is essentially ignored.
Additionally, Enum* should be renamed to Variant* for consistency. I also propose that EnumMap be renamed to StructVariant.

I agree with all of that. The serde_test crate dates back to before we had established naming conventions within Serde for a lot of these things.

I'd be willing to offer a PR for this that can be merged on a breaking release. Not sure when that'd be.

Thanks, please open a PR but only including the changes to the Token enum. You don't need to fix the serde_test serializer and deserializer or the test suite to use the new names.
That way we can discuss and agree on an API now, then one of us can wrap up the rest of the change when we are ready for the next major release. I think that will be easier than writing the whole change now and dealing with merge conflicts.

Okay! Sounds good to me.

I changed my mind on EnumStart - it is important for testing how enums deserialize when the format represents the variant not as a string. For example bincode represents the variant as a u32.
Example from our test suite that could not be written without EnumStart: test_enum_out_of_range
test_enum_out_of_range<Enum> {
    &[
        Token::EnumStart("Enum"),
        Token::U32(4),
        Token::Unit,
    ],
    Error::Message("invalid value: integer `4`, expected variant index 0 <= i < 4"),
}

How about just improving support for EnumStart in assert_ser_tokens / assert_tokens?

Fixed in #845.

Sorry I got a bit late to this— I think it'd be best to serialise enums with multiple tokens so that Enum is used always, rather than making variants include names and not have the start header. I think it'd be cleaner and make it easier to understand the purpose of the token rather than duplicating the information over multiple token types.

Other than that :+1: to the changes and I'm cool with everything else.

Thanks @clarcharr! I filed #849 to follow up on your suggestion.


Preprocessor definitions in robot_schema.json

The file robot_schema.json still contains preprocessor definitions:
"preprocessor": {
  "definitions": {
  }
}

Why? My understanding is that RobotFramework_TestsuitesManagement does not support preprocessor definitions. But if the schema allows this we run into danger, that someone uses this - with the outcome that the content is ignored and the user gets no feedback.
What is not computed and not wanted, should not be allowed.

Hi Son,
we should always hide future functionality as long it's not completely implemented.
Thank you,
Thomas

Hello Thomas and Holger,
I created the pull-request #118 for this ticket.
Thank you,
Son

solved and already merged with #118


Require MFA for sensitive portions documentation/examples

You don't require Multi-Factor Authentication to access an application in general, but you do require it to access the sensitive portions within it. For example, the consumer can sign in to a banking application with a social or local account and check account balance, but must verify the phone number before attempting a wire transfer.

This is a scenario I need to implement, however this document doesn't provide, or provide links to, any documentation as to how this may be implemented :(

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

ID: d8c394d1-e3b1-b88c-416c-3f8e0ab3ae3d
Version Independent ID: 8aafb9d8-72cb-c9b4-5a01-9e5633764f39
Content: Azure Active Directory B2C: Multi-Factor Authentication
Content Source: articles/active-directory-b2c/active-directory-b2c-reference-mfa.md
Service: active-directory-b2c
GitHub Login: @davidmu1
Microsoft Alias: davidmu

@justrhysism We received this link from the engineering team, hope it might help: https://social.msdn.microsoft.com/Forums/en-US/f7a26ab7-940e-40a2-8147-29447f84314c/azure-b2c-step-up-authentication?forum=WindowsAzureAD.  We have opened an item in our documentation backlog to have this investigated and updated. We'll respond back to you on this issue when we've done the work. For now, we'll close this GitHub issue.
#please-close

@justrhysism We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Connecting using port forwarding results in failed connections

Attempting to use the $expose_docker_tcp in config.rb establishes the vagrant port-forwarding. I am then setting the DOCKER_HOST var to the port that is exposed to the host:
export DOCKER_HOST=tcp://localhost:4243

Attempting to invoke docker version results in
Client version: 0.11.1
Client API version: 1.11
Go version (client): go1.2.2
Git commit (client): fb99f99
2014/06/04 09:36:42 Get http://localhost:4243/v1.11/version: EOF

Further digging using "curl http://localhost:4243/v1.11/version" results in:
curl: (52) Empty reply from server

It appears that the port is not being utilized by the docker service in the CoreOS vm.

Moved to https://github.com/coreos/bugs/issues/1378


Suggestion is not Displaying

I am using the below code in order to get the result from the API and during log i successfully see the response with no erro but suggestion is not displaying
private void initializeSearch() {

      final SearchView mSearchView = appBarMainScreenBinding.searchView;
      if (mSearchView != null) {
          mSearchView.setVersionMargins(SearchView.VersionMargins.TOOLBAR_SMALL);
          mSearchView.setHint("search");
          mSearchView.setOnQueryTextListener(new SearchView.OnQueryTextListener() {
              @Override
              public boolean onQueryTextSubmit(String query) {
                  mHistoryDatabase.addItem(new SearchItem(query));
                  mSearchView.close(false);
                  return true;
              }

              @Override
              public boolean onQueryTextChange(String newText) {
                  appBarMainScreenBinding.searchView.showProgress();
                  getMoviesList(newText);
                  return false;
              }
          });
          mSearchView.setOnOpenCloseListener(new SearchView.OnOpenCloseListener() {
              @Override
              public boolean onOpen() {
                  return true;
              }

              @Override
              public boolean onClose() {
                  return true;
              }
          });
      }

  }

private void getMoviesList(final String query) {
      qeryResult.clear();
      RetrofitBuilder retrofit = new RetrofitBuilder();
      final RetrofitInterface service = retrofit.mApi;

      service.searchMovie(API_KEY,query)
              .subscribeOn(Schedulers.newThread())
              .observeOn(AndroidSchedulers.mainThread())
              .subscribe(new Observer<Movies>() {
                  @Override
                  public void onCompleted() {
                      appBarMainScreenBinding.searchView.hideProgress();
                      searchAdapter.notifyDataSetChanged();
                      appBarMainScreenBinding.searchView.showSuggestions();
                  }

                  @Override
                  public void onError(Throwable e) {
                      appBarMainScreenBinding.searchView.hideProgress();
                      e.printStackTrace();
                  }

                  @Override
                  public void onNext(Movies movies) {
                      for (MovieDetails details : movies.results) {
                          Logger.d("add");
                          SearchItem searchItem = new SearchItem(details.original_title);
                          qeryResult.add(searchItem);
                      }
                  }
              });
  }

What version do you use? This was fixed in alpha5.

What version do you use?

I solve that issue by setting setSuggestionsList() funtion Thanks @HusseinElFeky

Oh yeah. I didn't notice that. Great.

If we have and ID with SearchItem than how to handle ID ?

What do you exactly mean by ID in your case here? What do you want to achieve?

You can use setOnSearchItemClickListener() on SearchAdapter if you want to do actions from that SearchItem. Is that what you meant?

Ohh Thanks I can solve my issue using that thanks for your help @HusseinElFeky

You're welcome. ;)

But I am now facing attempt to java.lang.IllegalStateException: attempt to re-open an already-closed object: SQLiteDatabase: and I think which was fixed in previous version

Yes, it's still an issue that needs to be fixed. Check issue #178.

@lapism You should mark this as a duplicate of #178.

Some LG users is getting this crash related with SQLite:
Fatal Exception: java.lang.IllegalStateException: Cannot perform this operation because the connection pool has been closed.
       at android.database.sqlite.SQLiteConnectionPool.throwIfClosedLocked(SQLiteConnectionPool.java:982)
       at android.database.sqlite.SQLiteConnectionPool.waitForConnection(SQLiteConnectionPool.java:600)
       at android.database.sqlite.SQLiteConnectionPool.acquireConnection(SQLiteConnectionPool.java:349)
       at android.database.sqlite.SQLiteSession.acquireConnection(SQLiteSession.java:1032)
       at android.database.sqlite.SQLiteSession.executeForCursorWindow(SQLiteSession.java:972)
       at android.database.sqlite.SQLiteQuery.fillWindow(SQLiteQuery.java:62)
       at android.database.sqlite.SQLiteCursor.fillWindow(SQLiteCursor.java:143)
       at android.database.sqlite.SQLiteCursor.getCount(SQLiteCursor.java:132)
       at android.database.AbstractCursor.moveToPosition(AbstractCursor.java:219)
       at android.database.AbstractCursor.moveToFirst(AbstractCursor.java:258)
       at com.lapism.searchview.SearchHistoryTable.getAllItems(SearchHistoryTable.java:111)
       at com.lapism.searchview.SearchAdapter$1.publishResults(SearchAdapter.java:182)
       at android.widget.Filter$ResultsHandler.handleMessage(Filter.java:282)
       at android.os.Handler.dispatchMessage(Handler.java:102)
       at android.os.Looper.loop(Looper.java:148)
       at android.app.ActivityThread.main(ActivityThread.java:5527)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:730)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:620)

It is related?

Yes, I think. Same idea.

Guys I am gonna check it today after work.

@lapism OK, cool. Can you also check #310 when you are free?

@lapism really only two users get this problem. I think is more priority the issue of duplicate ID.

First is duplicated ID, second onTextChanged

Yeah, indeed.


Debugging / logging facility

println!() debugging sucks because we need to remember to remove it before commit, hence have to insert it for every bug hunt, and 'users' of our compiler are left without context / methods to diagnose the issue when we crash.
However, logging is great.
Requirements:

println debugging on steroids, maybe with some fields like class=, etc.
CLI-facility to filter logging output based on fields
-v flags generally increases verbosity

Existing Solutions:

'standardized' logging macros + pluggable loggers https://github.com/rust-lang-nursery/log

problem: not structured

would be helpful to filter by field names, e.g. to view debug-level output only if the tag for a certain class is set

not a MUST for @problame , though
plus, users of such a logging framework need to remember to set those tags
and we have no parallelism, so the log output should be fully reproducible

We decided to use the nursery log crate, and started using it in https://github.com/comprakt/comprakt/pull/136/commits/8622f4de4fc3e2ed69752f9a6f159a6084f67f8c


Update dependencies and workflows

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (4c490e2) to head (8612f85).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #113   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           38        38
  Lines          817       817
  Branches        57        57
=========================================
  Hits           817       817

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


Add LIMIT and OFFSET support

Usually needed for pagination in apis...

Thanks for this request, I plan this feature for 0.2.1 release because the next release (0.2.0) is already pretty busy :)

Thanks for this request, I plan this feature for 0.2.1 release because the next release (0.2.0) is already pretty busy :)

@dave08 Kotysa 0.2.1 was release, you can now use LIMIT and OFFSET with Kotysa :)
val paginated = (sqlClient selectFrom USER
        limit 10 offset 12
        ).fetchAll()

Nice :+1:, thanks!


[Master] release/v1.1.1 QA Sign-off

This PR is automatically created by CI to release a new official version of caver-java-ext-kas.
When this PR is approved by QA team, a new version will be released.

v1.1.1 QA result

Package
Tests
Failures
Ignored
Duration
Success rate
Newly Added

xyz.groundx.caver_ext_kas.exception
4
0
0
0.024s
100%
0

xyz.groundx.caver_ext_kas.kas.anchor
25
0
0
0.793s
100%
0

xyz.groundx.caver_ext_kas.kas.kip17
30
0
0
12.810s
100%
0

xyz.groundx.caver_ext_kas.kas.tokenhistory
84
0
0
2.588s
100%
0

xyz.groundx.caver_ext_kas.kas.utils
2
0
0
0.025s
100%
0

xyz.groundx.caver_ext_kas.kas.wallet
123
0
0
47.708s
100%
0

xyz.groundx.caver_ext_kas.node
46
0
0
1.176s
100%
0

xyz.groundx.caver_ext_kas.wallet
131
0
0
31.508s
100%
0


inih compile-time options

Consider implementing inih syntax options as flags.
As of 3f9fcb24033a6a786199886153da1d4b6119c36c, INI_ALLOW_MULTILINE is disabled, and others are their defaults.

As of release v0.2.0, parsing multi-line entries is supported with the -m flag.
The other syntax options can be added as needed.


Adding a new monitor via API problem in NTFY

📑 I have found these related issues/pull requests
kuma log
2024-09-28T03:36:15+01:00 [MONITOR] ERROR: Cannot send notification to kuma
Error: Error: AxiosError: Request failed with status code 400 {"code":40018,"http":400,"error":"invalid request: actions invalid; parameter 'url' is required for action 'view'","link":"https://ntfy.sh/docs/publish/#action-buttons"}
at Ntfy.throwGeneralAxiosError (/app/server/notification-providers/notification-provider.js:38:15)
at Ntfy.send (/app/server/notification-providers/ntfy.js:72:18)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Monitor.sendNotification (/app/server/model/monitor.js:1427:21)
at async beat (/app/server/model/monitor.js:964:21)
at async safeBeat (/app/server/model/monitor.js:1032:17)
🛡 Security Policy

[X] I agree to have read this project Security Policy

Description
No response
👟 Reproduction steps
When I add it manually it works perfectly but when I add a new monitor via api with the NTFY notification it gives me this error. I've tested SMTP notification and it works fine.
👀 Expected behavior
Receive notification on NTFY
😓 Actual Behavior
I don't get the notification on ntfy
🐻 Uptime-Kuma Version
1.23.13
💻 Operating System and Arch
ubuntu 22
🌐 Browser
edge
🖥 Deployment Environment

Runtime:
Database:
Filesystem used to store the database on:
number of monitors:

📝 Relevant log output
No response

This is fixed in v2.0 but has not been back ported to the 1.23.x series. See #4500 for additional details on said release
V2
https://github.com/louislam/uptime-kuma/blob/b287a25de735d14c6e078d57e99b4587f10697cd/server/notification-providers/ntfy.js#L59-L67
1.23.x
https://github.com/louislam/uptime-kuma/blob/936665aac32ae86834723af695b21e54c38f616a/server/notification-providers/ntfy.js#L54


Allow chaining of multible animations

This PR

Adds a new feature

Describe the changes below:
With this commit it is possible to chain more than one animation together for example:
this.mole.anims.play('digging',true).anims.chain('lifting').anims.chain('looking').anims.chain('lowering');
This commit introduces a property nextAnimsQueue. It holds all additional nextAnim-Keys in the order the chain()-method was called. It is handed over to the nextAnim-Property in the stop()-method.

Thanks, I like this feature :) I had to fix some lint errors that prevented it from building, but otherwise, it looks good.

Thanks for your positive feedback! Glad I could help support phaser :-)


Integrate updater and migrate to 1.0 API

The GitHub actions should provide everything required for the updater and should expose the built artifacts as well.

[x] Updater artifacts
[x] Migrate to 1.0
[ ] Code signing

Github Actions should be fully compatible with the current Tauri version.

@jbolda can you assign me please so I can follow on this? Thanks!

Updated to 1.0 beta-rc on #98

I don't think there is much else we can do here. A possible additional feature to auto generate a updater json file is tracked in #251.


Push a new release to puppetforge

Right now the puppetforge release for this module is outdated, from Jan 2015. Could you push a new release to forge please.
Thanks

That's funny, I was reminding myself how that works just moments ago.. Expect something real soon...

Cool, 0.2.0 now pushed to the Forge - thanks for the reminder :)


Improve ListArtifact

[x] I have read and agree to the contributing guidelines for submitting new pull requests.

Describe your changes
Added

Generic type support to ListArtifact.
Iteration support to ListArtifact.

Issue ticket number and link
NA

Many Artifact refactors incoming


fix: use semver for workspace packages

Closes #34
✅ Pull Request Checklist:

[x] Included link to corresponding GitHub Issue.

[x] Added/updated unit tests and storybook for this change (for bug fixes / features).
[x] Added/updated documentation (for bug fixes / features)
[x] Filled out test instructions.

📝 Test Instructions:

❓ Does this PR introduce a breaking change?

[ ] Yes
[x] No

💬 Other information

I'm not sure why the design-system package isn't working the same as the others.

I'm not sure why the design-system package isn't working the same as the others.

Can you expand on that? What does it do differently? Can't tell from the code alone

When the version was specified 0.4.0 instead of workspace:* it fails to build in CI - https://github.com/gohypergiant/standard-toolkit/actions/runs/11978494290/job/33401372516 - but I could not reproduce locally.

Might be relevant ... which I'm assuming the later workspace: is preferred. Though depending on how changesets interplay with it, may need to go the other route.

If link-workspace-packages is set to true, pnpm will link packages from the workspace if the available packages match the declared ranges. For instance<EMAIL_ADDRESS>is linked into bar if bar has "foo": "^1.0.0" in its dependencies and<EMAIL_ADDRESS>is in the workspace. However, if bar has "foo": "2.0.0" in dependencies and<EMAIL_ADDRESS>is not in the workspace<EMAIL_ADDRESS>will be installed from the registry. This behavior introduces some uncertainty.
Luckily, pnpm supports the workspace: protocol. When this protocol is used, pnpm will refuse to resolve to anything other than a local workspace package. So, if you set "foo": "workspace:2.0.0", this time installation will fail because<EMAIL_ADDRESS>isn't present in the workspace.
This protocol is especially useful when the link-workspace-packages option is set to false. In that case, pnpm will only link packages from the workspace if the workspace: protocol is used.

Per Bryan's note, to ensure that local packages are only used we still need to specify the workspace protocol but use specific versions instead of the * e.g.
"@accelint/vitest-config": "workspace:0.1.3"

As specifying as
"@accelint/vitest-config": "0.1.3"

Is grabbing the remote published package off of npm.

Since this doesn't impact the actual published code, no need for a changeset imo.


Get stack by name is not working

Before you describe your issue, idea or feature, please consider using this issue template.

Get stack by name is not working, i.e route /api/name/:organisationName is responding with error code 500

Type of issue:

[X] Bug / Error
[ ] Idea / Feature
[X] Improvement detail

Short description on the issue

Get stack by name is not working, i.e route /api/name/:organisationName is responding with error code 500

Possible fix

Modify the /name/:organisationName for proper functioning

@psnmissaka Please check the issue and let me know your thoughts.

I have checked it second time and found that instead of /api/name/:orgName /api/org/name/:orgname worked. So closing this issue.