Weird error logs

every 10 minutes I have this in my logs
cat /var/log/syslog

Apr  3 01:49:08 WP47 sm-mta[3913]: t2T697eH023503: to=<deploy@WP47>, delay=4+23:40:00, xdelay=00:00:00, mailer=local, pri=64650000, dsn=4.0.0, stat=Operating system error
Apr  3 01:49:08 WP47 sm-mta[4179]: t2T5n7eH022360: Warning: program /usr/sbin/sensible-mda unsafe: No such file or directory
Apr  3 01:49:08 WP47 sm-mta[4179]: t2T5n7eH022360: SYSERR(root): Cannot exec /usr/sbin/sensible-mda: No such file or directory

I didn't do any deployments
The whole another reason why I went to check logs is because my mariadb server went down.
I had to login and restarted, here is what I saw after I did sudo mysql service restart:
Checking for corrupt, not cleanly closed and upgrade needing tables.

mysql -u -p
status
Threads: 1  Questions: 59928  Slow queries: 0  Opens: 127  Flush tables: 1  Open tables: 93  Queries per second avg: 0.095

Why do I have so many open tables? what should I do?
Also, When you guys push new changes to ansible playbook, how should I make updates on production?
here is /var/log/mysql/error.log
150114 13:52:44 [Note] Event Scheduler: Purging the queue. 0 events
150114 13:52:44 [Note] InnoDB: FTS optimize thread exiting.
150114 13:52:44 [Note] InnoDB: Starting shutdown...
150114 13:52:46 [Note] InnoDB: Shutdown completed; log sequence number 3891278
150114 13:52:46 [Note] /usr/sbin/mysqld: Shutdown complete

150114 13:52:46 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
150114 13:53:30 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
150114 13:53:30 [Note] InnoDB: Using mutexes to ref count buffer pool pages
150114 13:53:30 [Note] InnoDB: The InnoDB memory heap is disabled
150114 13:53:30 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
150114 13:53:30 [Note] InnoDB: Memory barrier is not used
150114 13:53:30 [Note] InnoDB: Compressed tables use zlib 1.2.8
150114 13:53:30 [Note] InnoDB: Using Linux native AIO
150114 13:53:30 [Note] InnoDB: Using CPU crc32 instructions
150114 13:53:30 [Note] InnoDB: Initializing buffer pool, size = 128.0M
150114 13:53:30 [Note] InnoDB: Completed initialization of buffer pool
150114 13:53:30 [Note] InnoDB: Highest supported file format is Barracuda.
150114 13:53:30 [Note] InnoDB: 128 rollback segment(s) are active.
150114 13:53:30 [Note] InnoDB: Waiting for purge to start
150114 13:53:30 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.21-70.0 started; log sequence number 3891278
150114 13:53:30 [Note] Plugin 'FEEDBACK' is disabled.
150114 13:53:30 [Note] Server socket created on IP: '<IP_ADDRESS>'.
150114 13:53:30 [Note] Event Scheduler: Loaded 0 events
150114 13:53:30 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.0.15-MariaDB-1~trusty'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
150202 18:41:26 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
150202 18:41:26 [Note] InnoDB: Using mutexes to ref count buffer pool pages
150202 18:41:26 [Note] InnoDB: The InnoDB memory heap is disabled
150202 18:41:26 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
150202 18:41:26 [Note] InnoDB: Memory barrier is not used
150202 18:41:26 [Note] InnoDB: Compressed tables use zlib 1.2.8
150202 18:41:26 [Note] InnoDB: Using Linux native AIO
150202 18:41:26 [Note] InnoDB: Using CPU crc32 instructions
150202 18:41:26 [Note] InnoDB: Initializing buffer pool, size = 128.0M
150202 18:41:26 [Note] InnoDB: Completed initialization of buffer pool
150202 18:41:26 [Note] InnoDB: Highest supported file format is Barracuda.
150202 18:41:26 [Note] InnoDB: The log sequence numbers 3891278 and 3891278 in ibdata files do not match the log sequence number 23848351 in the ib_logfiles!
150202 18:41:26 [Note] InnoDB: Database was not shutdown normally!
150202 18:41:26 [Note] InnoDB: Starting crash recovery.
150202 18:41:26 [Note] InnoDB: Reading tablespace information from the .ibd files...
150202 18:41:26 [Note] InnoDB: Restoring possible half-written data pages
150202 18:41:26 [Note] InnoDB: from the doublewrite buffer...
150202 18:41:26 [Note] InnoDB: 128 rollback segment(s) are active.
150202 18:41:26 [Note] InnoDB: Waiting for purge to start
150202 18:41:26 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.21-70.0 started; log sequence number 23848351
150202 18:41:26 [Note] Plugin 'FEEDBACK' is disabled.
150202 18:41:26 [Note] Server socket created on IP: '<IP_ADDRESS>'.
150202 18:41:26 [Note] Event Scheduler: Loaded 0 events
150202 18:41:26 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.0.15-MariaDB-1~trusty'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
150315 23:20:00 mysqld_safe Number of processes running now: 0
150315 23:20:00 mysqld_safe mysqld restarted
150315 23:20:00 [Note] InnoDB: Using mutexes to ref count buffer pool pages
150315 23:20:00 [Note] InnoDB: The InnoDB memory heap is disabled
150315 23:20:00 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
150315 23:20:00 [Note] InnoDB: Memory barrier is not used
150315 23:20:00 [Note] InnoDB: Compressed tables use zlib 1.2.8
150315 23:20:00 [Note] InnoDB: Using Linux native AIO
150315 23:20:00 [Note] InnoDB: Using CPU crc32 instructions
150315 23:20:00 [Note] InnoDB: Initializing buffer pool, size = 128.0M
150315 23:20:01 [Note] InnoDB: Completed initialization of buffer pool
150315 23:20:01 [Note] InnoDB: Highest supported file format is Barracuda.
150315 23:20:01 [Note] InnoDB: The log sequence numbers 3891278 and 3891278 in ibdata files do not match the log sequence number 151959872 in the ib_logfiles!
150315 23:20:01 [Note] InnoDB: Database was not shutdown normally!
150315 23:20:01 [Note] InnoDB: Starting crash recovery.
150315 23:20:01 [Note] InnoDB: Reading tablespace information from the .ibd files...
150315 23:20:01 [Note] InnoDB: Restoring possible half-written data pages
150315 23:20:01 [Note] InnoDB: from the doublewrite buffer...
150315 23:20:01 [Note] InnoDB: 128 rollback segment(s) are active.
150315 23:20:01 [Note] InnoDB: Waiting for purge to start
150315 23:20:01 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.21-70.0 started; log sequence number 151959872
150315 23:20:01 [Note] Plugin 'FEEDBACK' is disabled.
150315 23:20:01 [Note] Server socket created on IP: '<IP_ADDRESS>'.
150315 23:20:01 [Note] Event Scheduler: Loaded 0 events
150315 23:20:01 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.0.15-MariaDB-1~trusty'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
150319 01:46:59 mysqld_safe Number of processes running now: 0
150319 01:46:59 mysqld_safe mysqld restarted
150319  1:46:59 [Note] InnoDB: Using mutexes to ref count buffer pool pages
150319  1:46:59 [Note] InnoDB: The InnoDB memory heap is disabled
150319  1:46:59 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
150319  1:46:59 [Note] InnoDB: Memory barrier is not used
150319  1:46:59 [Note] InnoDB: Compressed tables use zlib 1.2.8
150319  1:46:59 [Note] InnoDB: Using Linux native AIO
150319  1:46:59 [Note] InnoDB: Using CPU crc32 instructions
150319  1:46:59 [Note] InnoDB: Initializing buffer pool, size = 128.0M
150319  1:46:59 [Note] InnoDB: Completed initialization of buffer pool
150319  1:46:59 [Note] InnoDB: Highest supported file format is Barracuda.
150319  1:46:59 [Note] InnoDB: The log sequence numbers 3891278 and 3891278 in ibdata files do not match the log sequence number 224408254 in the ib_logfiles!
150319  1:46:59 [Note] InnoDB: Database was not shutdown normally!
150319  1:46:59 [Note] InnoDB: Starting crash recovery.
150319  1:46:59 [Note] InnoDB: Reading tablespace information from the .ibd files...
150319  1:46:59 [Note] InnoDB: Restoring possible half-written data pages
150319  1:46:59 [Note] InnoDB: from the doublewrite buffer...
150319  1:46:59 [Note] InnoDB: 128 rollback segment(s) are active.
150319  1:46:59 [Note] InnoDB: Waiting for purge to start
150319  1:47:00 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.21-70.0 started; log sequence number 224408254
150319  1:47:00 [Note] Plugin 'FEEDBACK' is disabled.
150319  1:47:00 [Note] Server socket created on IP: '<IP_ADDRESS>'.
150319  1:47:00 [Note] Event Scheduler: Loaded 0 events
150319  1:47:00 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.0.15-MariaDB-1~trusty'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
150324 00:28:12 mysqld_safe Number of processes running now: 0
150324 00:28:12 mysqld_safe mysqld restarted
150324  0:28:12 [ERROR] mysqld: Out of memory (Needed 128909312 bytes)
150324  0:28:12 [ERROR] mysqld: Out of memory (Needed 96681984 bytes)
150324  0:28:12 [ERROR] mysqld: Out of memory (Needed 72499200 bytes)
150324  0:28:12 [Note] InnoDB: Using mutexes to ref count buffer pool pages
150324  0:28:12 [Note] InnoDB: The InnoDB memory heap is disabled
150324  0:28:12 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
150324  0:28:12 [Note] InnoDB: Memory barrier is not used
150324  0:28:12 [Note] InnoDB: Compressed tables use zlib 1.2.8
150324  0:28:12 [Note] InnoDB: Using Linux native AIO
150324  0:28:12 [Note] InnoDB: Using CPU crc32 instructions
150324  0:28:12 [Note] InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
150324  0:28:12 [ERROR] InnoDB: Cannot allocate memory for the buffer pool
150324  0:28:12 [ERROR] Plugin 'InnoDB' init function returned error.
150324  0:28:12 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
150324  0:28:12 [Note] Plugin 'FEEDBACK' is disabled.
150324  0:28:12 [ERROR] Unknown/unsupported storage engine: InnoDB
150324  0:28:12 [ERROR] Aborting

150324  0:28:12 [Note] /usr/sbin/mysqld: Shutdown complete

150324 00:28:12 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
150326 20:01:31 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
150326 20:01:31 [Note] InnoDB: Using mutexes to ref count buffer pool pages
150326 20:01:31 [Note] InnoDB: The InnoDB memory heap is disabled
150326 20:01:31 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
150326 20:01:31 [Note] InnoDB: Memory barrier is not used
150326 20:01:31 [Note] InnoDB: Compressed tables use zlib 1.2.8
150326 20:01:31 [Note] InnoDB: Using Linux native AIO
150326 20:01:31 [Note] InnoDB: Using CPU crc32 instructions
150326 20:01:31 [Note] InnoDB: Initializing buffer pool, size = 128.0M
150326 20:01:31 [Note] InnoDB: Completed initialization of buffer pool
150326 20:01:31 [Note] InnoDB: Highest supported file format is Barracuda.
150326 20:01:31 [Note] InnoDB: The log sequence numbers 3891278 and 3891278 in ibdata files do not match the log sequence number 224935377 in the ib_logfiles!
150326 20:01:31 [Note] InnoDB: Database was not shutdown normally!
150326 20:01:31 [Note] InnoDB: Starting crash recovery.
150326 20:01:31 [Note] InnoDB: Reading tablespace information from the .ibd files...
150326 20:01:31 [Note] InnoDB: Restoring possible half-written data pages
150326 20:01:31 [Note] InnoDB: from the doublewrite buffer...
150326 20:01:31 [Note] InnoDB: 128 rollback segment(s) are active.
150326 20:01:31 [Note] InnoDB: Waiting for purge to start
150326 20:01:31 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.21-70.0 started; log sequence number 224935377
150326 20:01:31 [Note] Plugin 'FEEDBACK' is disabled.
150326 20:01:31 [Note] Server socket created on IP: '<IP_ADDRESS>'.
150326 20:01:31 [Note] Event Scheduler: Loaded 0 events
150326 20:01:31 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.0.15-MariaDB-1~trusty'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution

Ohhh I wanted to file it against bedrock-ansible repo :-( my baadd

Closing this as it's on the wrong repo. But a few things:

http://serverfault.com/questions/58052/what-is-sensible-mda-and-do-i-need-it
Don't think that "tables open" is really a problem
Start a thread on Discourse about re-provisioning when we make updates

Done. https://discourse.roots.io/t/re-provisioning-ansible-instance/3407
Any idea why mysql server was shut down? Any way to figure it out?

@rstormsf I don't know if it's the same thing, but on my little 512 MB DigitalOcean droplet, the oom-killer will kill mysql after a few days unless I have added a swap file. You might search  /var/log/kern.log for 'oom-killer'. For me, mysql doesn't restart after being killed (like other services do, I'm told), so my site was left showing nothing but "Error establishing a database connection." I've been meaning to PR bedrock-ansible to add a swap file. Oh wait, someone did in roots/bedrock-ansible#152

Yeah call 1800MICROSOFT OR 18004MYXBOX. MIKE D PC HELP SERVICE@M13KD <EMAIL_ADDRESS>Virtualization AcademyXcl.Xbox.ComExpertZone.Microsoft.ComXBOX/MSFT LIVE Community Ambassador GAMER TAG:MSFT LIVE RocksAdd me. +17705724576Let's get this accomplished. Michael Christopher Duggan.-------- Original message --------From: Roman Storm<EMAIL_ADDRESS>Date: 04/03/2015  12:22 PM  (GMT-05:00) To: roots/bedrock<EMAIL_ADDRESS>Subject: Re: [bedrock] Weird error logs (#158)  Done. https://discourse.roots.io/t/re-provisioning-ansible-instance/3407
Any idea why mysql server was shut down? Any way to figure it out?
—Reply to this email directly or view it on GitHub.

@fullyint it was the exactly the same thing. Thank you for your information. I will know where to look for a fix. I also have 512 MB DO instance and I had the exact message "Error establishing a database connection."


Create lasallesanildefonso

Add domain lasallesanildefonso.es

@necto101 lib/domains/es/lasallesanildefonso: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@necto101 You might miss my previous comment. Please react.

@necto101 I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the aforementioned issue. Thank you for your understanding!


Permalink-like support for URLs referenced in record

Originally on 2011-04-15
It would be great to be able to consider records stored in Invenio as master resources of information.
If a record references an external URL, a weak link between the record in Invenio and the external resource is created. What if this resource is moved? The URL in the record must be updated! But what if some service has been built that assumed the URL initially provided by Invenio in the record would have stayed forever? The service would be broken.
To solve this issue, Invenio should be considered as master, to serve URLs, so that if the external URL changes, it would suffice to update an internal redirection table, and any external client, would transparently have the update.
This could be implemented in the following way:

we invent a new subfield to 8564 tag, that should contain an ID that will be used to build the "permalink". This subfield should be repeatable. Its value must be unique WRT the record. Say $7

everytime bibupload is seeing an 8564 tag with URL (or an FFT that will cause the 8564 tag to be automatically created), if it is missing the $7 subfield will automatically allocate it (this ID will be uniquely generated after properties of the URL)
a new URL handler should be added that would handle URLs such as:

http://<server>/record/<recid>/permalink/<ID>

such handle should check for authorization to access  and should then check within the record what  resolves to and should redirect the user using via an HTTP 307 (Temporary Redirect) (see also http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html)

format elements that were previously delegated to display links to the external URLs should instead provide the permalink.
if the $7 is missing upon formatting of the record, the original URL should be provided as compatibility.
if the external URL changes and an update to the record in Invenio is necessary, one have simply to update (e.g. via BibEdit) the $u field for the URL, without touching the $7.
additionaly we might decide that any bibupload that append a URL, whose field is specifying an existing $7, will erase the old field and will become the new URL.
if a URL is added without specifying a $7 it would automatically receive one from BibUpload. However if then it becomes clear that this URL should be the new reference for a resource that was previously already specified, the $7 of the old URL will be added to the new one (so the URL will be resolved by two permalinks, and that's why $7 should be repeatable).

At CERN this might be useful, for example, to implement a more robust integration with MediArchive. CDS would be the master reference for MediaArchive URLs, and if an URL on MediaArchive would change, only the record in CDS would need to be updated (any service using CDS as master won't be affected).

Redirection support has been added to Invenio-PIDStore used by Invenio 3.


Multiparty decryption error

I found that when I split the three party threshold multi key homomorphic sample code into three files for collaborative calculation, multiplication decryption would cause errors due to large approximation errors. I output some of the intermediate parameters and found that the logstd was too high, and the Elementwas also significantly different from normal decryption. I'm not sure if there was a problem with my code flow. Could you please help me check it.
resources.zip

I suggest posting this at https://openfhe.discourse.group/ We create issues only for confirmed bugs. Thank you!


Feature: Option to leave Quick ACtion open after action is clicked

Is your feature request related to a problem? Please describe.
Sometimes it is needed to have it open to allow multiple actions to be activated as needed without having to first open QuickActions windows and then click on Action.
Describe the solution you'd like
It would be good to have option to disable automatic closing of Quick Action windows. That would allow user to activate several Actions.
Along with that, it would be good to have an option to assign keyboard key (not hot-Key) that would activate action only while within QuickActions Window. In that case that would not have to be key combinations but plain keys, like numerical keys, function keys, or even letters.
Describe alternatives you've considered
One alternative is using HotKeys but that is cumbersome as user has to find available key combinations and remember them. Using Hotkeys is OK for few frequently used options but if there is number of them, then it becomes impractical.
The second alternative could be adding new option that would open minimalistic web browser window displaying selected HA lovelace view. That would allow user to prepare view that would be easily opened from Hass.Agent as some kind of control panel, showing not just buttons, but statuses too.

Good ideas!
[hassagent-179]
[hassagent-180]


Msal updates

@jamescro,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Moved query item tool tips to the left.

Fix #751

Signed-off-by: Sheik Hassan<EMAIL_ADDRESS>

Thanks @hassanNS


Render results to a chart

The chart should show percent of best speed in Y axis and the count of iterations in X axis. The mid value should be drawn solid, the min and max - dashed. Each lib should use unique random color.
Resulted image should be stored in the root of the repo and displayed in the readme.
I prefer to use https://vercel.com/docs/concepts/functions/edge-functions/og-image-generation as it most light (???) solution, in terms of npm module size.
An example:

Done by #5


Error messages for IntMatchers.between(a,b) are swapped

This code:
1.shouldBeBetween(2,3)
throws
java.lang.AssertionError: 1 is between (2, 3)
https://github.com/kotlintest/kotlintest/blob/c87d2827054fa004f79393e1a5a8610057be5944/kotest-assertions/src/commonMain/kotlin/io/kotest/matchers/ints/IntMatchers.kt#L11

@wallecnik Thanks for reporting this is now fix in #1213


Component not found: heltec_balancer_ble.

Does anyone know the problem? Always having the same issue.

I assume the external_components section is missing in your YAML. Please provide the full YAML so I can try to reproduce the issue.

You were absolutely right, it's working now. Thank you


Exception in onCommissioningRequested(): lateinit property chipClient has not been initialized

I'm trying to implement the commissioning mecanism in a custom app
After starting commissioning a device, the method AppCommissioningService's onCommissioningRequested() is properly called, but then the following exception is thrown:
lateinit property chipClient has not been initialized
Any idea why ?
How to initialize chipClient ?
For info, here is how chipClient is declared in the service:
@Inject
internal lateinit var chipClient: ChipClient

Do you have class ChipClient in your app?
See https://github.com/google-home/sample-app-for-matter-android/blob/main/app/src/main/java/com/google/homesampleapp/chip/ChipClient.kt.

Indeed, now I initialize the chipClient using the ChipClient_Factory:
chipClient = ChipClient_Factory.newInstance(this);
It seems to work, but then in order to call
chipClient.awaitEstablishPaseConnection(deviceId, metadata.getNetworkLocation().getIpAddress().getHostAddress(),
                metadata.getNetworkLocation().getPort(), metadata.getPasscode(), continuation);

a Continuation instance is needed.
Any idea how to initialize it properly in Java ?

Sorry, my area of expertise will be limited to the sample app itself and Kotlin.
But stackoverflow can always be your friend :-)

It look like a dependency injection issue. Your lateinit variable is not initialized which is strange as it's annotated with @Inject so it's supposed to be initialized by Dagger/Hilt. My first guess is that your AppCommissioningService class is not annotated with @AndroidEntryPoint so the Hilt compiler ignore the class and its fields annotated with @Inject aren't actually injected.


Default of poisson_multinomial throws DivisionByZero Error

Hey there :)
The implementation of poisson_multinomial suggests that 1 is a good default for the weight_range. In practice it raises RuntimeWarning: divide by zero encountered in scalar divide since np.log(weight_range) = 0 for weight_range = 1.
Best
Timon

This is a new feature that we're playing around with. All published models would use weight_range=1. I pushed a fix that avoid giving this warning.

Thanks Dave!


SHIFTR operator negative

Fixed negative numbers when pertaining to SHIFTR operator
This version allows usages between -2^31 to 2^31-1.

Addressed by https://github.com/wurstscript/WurstStdlib2/pull/430
The reason for the look of the function with just 1 return is, so that it can be inlined.


New version: TechSmith.Snagit.2022 version <IP_ADDRESS>942 (22.1.7)

Created by 🥟 Dumplings in workflow run #5840.

Log
Updated: 22.1.6 → 22.1.7
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

/azp run

Response: An error was encountered while processing request. Exception:
Exception Message: Unable to connect to the remote server (type WebException)

/azp run

/azp run

/azp run

This package installs and launches normally on a Windows 10 VM.

This package installs and launches normally on a Windows 10 VM.

https://github.com/microsoft/winget-pkgs/issues/142854


fix avoid potential buffer overflow (#35537)

pick #35537
If skip more than once when available is zero, then a buffer overflow occurs.

Proposed changes
Issue Number: close #xxx

run buildall


Annotation examples for Reel

I would like to test out the new annotation features of Reel.  Could you please post some examples?  Thank you very much for this excellent work!

Working on it. There sure will be examples once the code is released.

I've put several annotations into some examples illustrating some annotation features - namely into:

object-movie-clockwise-sprite
object-movie-dual-orbit-sequence
object-movie-multi-row-sequence
panorama-non-looping-stitched

I plan to put more for the 1.2 release, but this would do it for the 1.2 Beta, I hope. Also see the Annotations for documentation.
You also can see them live at http://test.vostrel.cz/jquery.reel/example (those with annotations are marked with asteriks).


[curl] Add support of different features.

This PR adds different features for the cURL library and, as an example, adds corresponding parts to the CPR library.
Default-Features: openssl, http2, ssh (as in previous builds)
Feature: curl
Description: Builds curl executable (placed in the /tools directory)
Feature: http-only
Description: Disables all protocols except HTTP/HTTPS/HTTP2
Feature: http2
Build-Depends: nghttp2, openssl
Description: HTTP2 support (requires openssl)
Feature: openssl
Build-Depends: openssl
Description: SSL support via OpenSSL
Feature: winssl
Description: SSL support via Schannel
Feature: ssh
Build-Depends: libssh2
Description: SSH support via libssh2

I have tested as many features as possible, however I found some dark corners of the Default-Features #2697 support.
For example,
Source: cpr
Build-Depends: curl[core]

Vcpkg still tries to install default features:

$ vcpkg install cpr --dry-run
curl[core,openssl,ssh,http2]:x86-windows

$ vcpkg install cpr[core] --dry-run
curl[core,openssl,ssh,http2]:x86-windows

The only way to avoid it is to install corresponding dependencies manually:

$ vcpkg install cpr[core] curl[core] --dry-run
curl[core]:x86-windows

However it still fails at the end:

Starting package 2/2: cpr:x86-windows
Building package cpr[core]:x86-windows...
The build command requires all dependencies to be already installed.
The following dependencies are missing:
curl[core]:x86-windows

So, I had to change Build-Depends: curl[core] to just Build-Depends: curl in CPR and, again, to install cURL manually: vcpkg install cpr[core] curl[core]. Now it works.

cc @ras0219-msft @alexkaratarakis
Could you guys have a look at this PR and give your opinion, please?

Vcpkg still tries to install default features:
The only way to avoid it is to install corresponding dependencies manually:

Yes, that is intended, see discussion on #2697 :)
I am guessing the error message is the one you added with the diff in https://github.com/Microsoft/vcpkg/issues/2861 ? (Because it still says "build command", while this is the "install command").
Build-Depends: curl[core] should be valid and if specified explicitly and it doesn't work, it's a bug :/

Thanks for the PR!
I'll corroborate what @Squareys mentioned -- the "by design" behavior is that if you haven't explicitly told us that you know about the package (by pre-installing it or listing it on the command line), then we use the defaults. Note that if you currently have curl[core] installed, it should not install defaults (that would be a bug :)).

Starting package 2/2: cpr:x86-windows
Building package cpr[core]:x86-windows...
The build command requires all dependencies to be already installed.
The following dependencies are missing:
curl[core]:x86-windows

This is definitely a bug; you should never see "The build command requires all dependencies to be already installed." during an installation.
While trying to investigate that bug (I'm not able to repro it yet so further information would be awesome :)), I did find another serious bug in feature dependencies. If you had an installed package with a dependency like curl[core], the remove command did not consider that to be a dependency on curl so you could remove curl without removing cpr. I've pushed a fix to master for that, as well as rebased this PR onto that fix.
Finally, I pushed some changes (let me know if you think these are a problem):

I removed the transitive feature descriptions from cpr

Features aren't a good fit for this sort of "pass-through" because there isn't an observable difference between install curl[openssl] cpr[core] and install curl[openssl] cpr[openssl]. Instead, cpr should list cpr's capabilities and curl should list curl's capabilities :) If we want to have a command line experience like install cpr[curl:openssl] that does some amount of pass-through, then we can definitely discuss that separately

I inverted the logic of only-http to be non-http. Part of the design of features is that they must express positive relationships with code (i.e. adding a feature should add code, not remove it). Default features are a key part of making this work in the case of things like this -- non-http can be on by default, and removed to turn on the USE_HTTP_ONLY flag.

(
@ras0219-msft

Note that if you currently have curl[core] installed, it should not install defaults (that would be a bug :)).

Off the top of my head I cannot remember writing a test for that. I have a hunch that this may be an actual issue.
)

@Squareys It worked that way for me already in my usages :) But I've added a test as well: https://github.com/Microsoft/vcpkg/commit/71d44cebdb85926bc00241fc08f0dcaaedb868d2

I found more bugs with feature packages (😦) but I've fixed all of them that I'm aware of (😄) so please try out c267f32b -- I'll rebase this PR onto that and push it here.

However I can't go with a separate triplet

Ideally, you can edit the existing triplets (x86-windows.cmake) locally to meet your needs. If that doesn't work well, we have several scenarios that need adjusting :)

Ideally, you can edit the existing triplets (x86-windows.cmake) locally to meet your needs.

And to force other people to do it? No, it does not make sense. Ideally, vcpkg install curl[winssl] would do the job.
Anyway, thanks.


Climatisation time left Unavailable at startup

If the electric climatisation isn't running when HA is started, Climatisation time left will be grayed out and Unavailable until the heater is started.
Setting it to default to 0 if it's not available would resolve this.

The library should return 00:00 if climatisation isn't running. If the sensor is unavailable it might be that the specific API response attribute has changed and isn't numeric when the heater isn't running.
I'll see if I can find something that might work for next release.

Update, checked again, and it doesnt start working if I start the heater either.
To get it to work, I need to reload the integration while the heater is running, then it works.

Update, checked again, and it doesnt start working if I start the heater either. To get it to work, I need to reload the integration while the heater is running, then it works.

Ok, that should be enough to find the issue. Most probably it doesn't return the json from API when heater isn't running and the "sensor" isn't marked as supported.

Should be fixed in latest release.


Inconsistent state transition

I am having inconsistency problems while moving between the two states (that has the same url and parameters).
For details, please see http://plnkr.co/xLA21CmQ32uklXOlnXMI
Note: Try going to state 2 and then go back to state 1. Try this couple of times, you will notice that i takes '2' clicks to move to state 2.
This is a serious isssue, as this will be break the common routing scenario when you have child states (like item-view and item-edit) that share same url.
Reproducible in 2.0.15, 2.0.16 and 2.0.17
Works in 2.0.13

Having two states with the same URL is not supported and has never been supported. The correct approach is to have a parent state with a URL, and 2 URL-less child states. Please see StackOverflow for further details, as I have already addressed this scenario there.

@nateabele thanks for the comment.
But, if we create a parent state (with or without abstract), my scenario will only work if the template of the new parent template contains 'ui-view' directive.
Is there a way to avoid it?
http://plnkr.co/edit/xLA21CmQ32uklXOlnXMI see updated plunker

You can use a named ui-view in a parent state, and target it in the child state configuration.


My App don´t start

I did all the thing listed in is page, but now my app doesn´t start

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

ID: 5823a3fa-87be-0b27-155b-b44130c67e84
Version Independent ID: c90633f5-22b9-f7dd-fd08-c9affc251dd4
Content: Splash Screen - Xamarin
Content Source: docs/android/user-interface/splash-screen.md
Product: xamarin
Technology: xamarin-android
GitHub Login: @davidortinau
Microsoft Alias: daortin

Please provide additional information about the error you are experiencing, and confirm that you were able to run the linked sample successfully.


Fail to query data after insert

I use node-sqlite3 (v4.2.0) in my electron(v8.2.5) project.
I enable wal mode and hold a connection pool for reading (i have mutiple read connections and only one write connection)
step1: create read connection: connection-read-1
step2: create read connection: connection-read-2
step3: create write connection: connection-write-3,  and insert some user data
step4: fail to use connection-read-1 or connection-read-2 to query user data inserted in  step3
step5：create read connection: connection-read-4， i can query the user data by connection-read-4
it seems that some error happen while resuing connection

it's caused


kestrel hosting.ini multiple endpoints

at present the hosting.ini used by kestrel can only have a single endpoint address; is there any plans to allow multiple endpoints ie. http/https or multi-homing of the site? and/or hosting multiple sites/endpoints under the same instance of dnx kestrel?

This issue was moved to aspnet/KestrelHttpServer#200


Stopped working

Mine, seems to have stopped working. When I click the button nothing happens.

Can you share details? I'm using v0.25.0 on Windows as the latest one and it still works.

It has stopped working for me also on 2 computers. Both are MacOS.
Version: 1.74.0 (Universal)
Commit: 5235c6bb189b60b01b1f49062f4ffa42384f8c91
Date: 2022-12-05T16:43:37.594Z
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 21.6.0
Sandboxed: No

Here Windows 11. And comment button doesn't do anything now.

@MichaelCurrin Same here. Installed the extension @ latest version, but the button does nothing.
Windows 10. VSCode <IP_ADDRESS>

SAme problem with  v0.25.0
on Win11 and Ubu22.04 server

@MichaelCurrin Please, comeback =)

Ah thanks all for the info. And the GitLens tipoff.

I'm going to install GitLens and check the error log

Aha. Here is error message when using the sandboxed extension for log messages and GitLens installed on and kept enabled.

Okay I have a fix to use rootUri instead of _rootUri and that works in the sandbox.
I have an issue getting the extension to install in VS Code though - my first time installing it using WSL on Windows.
 DONE  Packaged: build/auto-commit-msg-0.25.1.vsix (26 files, 34.73KB)
<3>init: (20977) ERROR: UtilConnectToInteropServer:307: connect failed 2
                                                                        make: *** [Makefile:52: e] Error 1

Let me know if you have any ideas there, otherwise I'll keep testing in the sandboxed window and publish that ASAP

Fixed in PR - for review if anyone wants to help
https://github.com/MichaelCurrin/auto-commit-msg/pull/91/files#diff-04bba6a35cad1c794cbbe677678a51de13441b7a6ee8592b7b50be1f05c6f626L41

Fixed in PR - for review if anyone wants to help
https://github.com/MichaelCurrin/auto-commit-msg/pull/91/files#diff-04bba6a35cad1c794cbbe677678a51de13441b7a6ee8592b7b50be1f05c6f626L41

out of my knowledge. Hope anyone here can help you. And thx you for your work under that project!

Published as v0.25.2 in the extension store. Release on GH: https://github.com/MichaelCurrin/auto-commit-msg/releases/tag/v0.25.2

I also added a feature for one than one repo to be used at once v0.26.0


credential: include license files in all published crates

What does this PR try to resolve?
It appears that the addition of license files was missed when the cargo-credential* crates were added to this cargo workspace. This PR adds symbolic links to the license files so that cargo publish picks them up and includes the files when publishing them to crates.io (which is a requirement for both the Apache-2.0 and the MIT license).
How should we test and review this PR?
Running cargo package for the cargo-credential* crates should result in a copy of the LICENSE-APACHE and LICENSE-MIT files to be included in the "packaged" files.
Additional information
Similar changes have been pushed for other workspace members in the past, for example https://github.com/rust-lang/cargo/pull/7886

Thanks for the contribution!
@bors r+

:pushpin: Commit a13a6905e96fe644d3ec1bb08c6ebf4cc5677874 has been approved by weihanglo
It is now in the queue for this repository.

:hourglass: Testing commit a13a6905e96fe644d3ec1bb08c6ebf4cc5677874 with merge 746802cfe26bad9183017d3e874cf2fed682a201...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing 746802cfe26bad9183017d3e874cf2fed682a201 to master...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing 746802cfe26bad9183017d3e874cf2fed682a201 to master...

:eyes: Test was successful, but fast-forwarding failed: 422 Changes must be made through a pull request.

Thanks!


Remove unnecessary closing bracket

This is a documentation change.
Summary
This change remove unnecessary closing bracket in this section:
https://mmistakes.github.io/minimal-mistakes/docs/configuration/#analytics
in table, row with "Google Analytics Global Site Tag)"
Context
No, it's not related to any GitHub issue. This is just a quick fix in the documentation.

Thanks!


Open external links in new tab

Whenever opening links that redirect you to an external website, it's best practice to make this link open a new tab. Currently this isn't the case, and it's irritating for the end user.

Opening a new tab without explicit user action is unfortunately a bad accessibility practice as explained on the following link https://www.w3.org/WAI/WCAG21/Techniques/general/G200

In general, it is better not to open new windows and tabs since they can be disorienting for people, especially people who have difficulty perceiving visual content.


Tweaks to s3UploaderAdditionalFiles

Make the s3UploaderAdditionalFiles paths relative to the task directory, not the logrotate path
Allow the additional files to specify a glob

This should make things much more flexible and allow us to have something like an upload folder or other globs that match a wider range of things
/cc @tpetr

Another that has been working well, going to merge. Quick note that we'll need to add a short note in the next release on the change in configuration (ability to add a directory relative to task folder, default directory is the task folder, not logs now)


Add some lightweight host/namespace validation

@flaviuvadan, I wanted to share a tip I learned the hard way when working with the requests library. In the following code:
resp = requests.post(
    url=urljoin(self.host, "api/v1/workflows/{namespace}").format(
        namespace=namespace if namespace is not None else self.namespace
    ),
    params=None,
    headers={"Authorization": f"Bearer {self.token}"},
    data=req.json(
        exclude_none=True, by_alias=True, skip_defaults=True, exclude_unset=True, exclude_defaults=True
    ),
    verify=self.verify_ssl,
)

If you don't include the protocol in the base URL, urljoin might not be able to determine the base URL properly, and only show the path part of the URL. For example, if you use localhost:2746 instead of https://localhost:2746, you might only see "api/v1/workflows/{namespace}" and experience unexpected behavior.
To avoid this, make sure to include the protocol in the base URL, like so: https://localhost:2746. I hope this helps someone avoid the same issue I faced!"
Originally posted by @tavallaie in https://github.com/argoproj-labs/hera/discussions/576#discussioncomment-5734592

Thanks for bringing this up @elliotgunton. I certainly recognize the challenge.. should we add a validator to the global config or the service that checks for this? Perhaps the service is easiest because the init can have this check 🤔


mongodb version

A nice addition to the readme would be the minimum MongoDB version that this lib is compatible with? Unless I missed it in the readme, but I didn't see it.

The minimum mongodb version is under the please note section :)

yeah sorry, I think I saw it as soon as I opened this issue LOL


Secure /etc/kibana/kibana.yml

Feature Request
Currently, /etc/kibana/kibana.yml is world-readable.
Please make it RW only for the elasticsearch user.
Feature Description
When storing credentials inside kibana.yml it shoul not be readable by any other user than the elasticsearch user for security reasons.

Thanks for the issue @varac. There's no guarantee that Elasticsearch will be on the same system as a host running Kibana, but the Kibana packages do create a kibana system user that the service runs under. Would changing the permissions to 0660 for the kibana:kibana or root:root work?

@tylerjl Sorry, I was not looking properly. It should indeed get the permissions and ownership you are proposing.

Thx !


Add PR template

Description
This PR adds new pull request and issue templates to project. The templates provide structured guidelines for contributors, ensuring that necessary information is included in PRs.
Related Issue
https://github.com/michaelfeil/infinity/issues/416
Type of Change

[ ] Bug fix
[x] New feature
[x] Documentation update

Checklist

[x] I have read the CONTRIBUTING document.
[x] My code follows the code style of this project.
[ ] I have added tests to cover my changes. (Not applicable for documentation changes)
[ ] All new and existing tests passed. (Not applicable for documentation changes)
[x] My changes generate no new warnings.
[x] I have updated the documentation accordingly.

License
By submitting this PR, I confirm that my contribution is made under the terms of the MIT license.

@fadkeabhi FYI, this template is not beeing used. In needs to be a yaml file. Regardless, thanks for the contribution.

Hi @michaelfeil,
Thank you for your feedback! I followed the official GitHub guidelines for creating pull request templates as outlined here. However, I'm not sure why it didn't work as expected. If you could provide any insights or suggestions for adjustments, I’d appreciate it!
Thanks again for your support!


mapping.txt not uploaded with Android gradle plugin 1.5.0

I'm using the following plugin versions in my build.gradle:
buildscript {
    // ...
    dependencies {
        classpath 'com.android.tools.build:gradle:1.5.0'
        classpath 'de.felixschulze.gradle:gradle-hockeyapp-plugin:3.3.1'
    }
}

I could upload the apk but then when I checked on HockeyApp I realized that the mapping.txt file was not uploaded. I ran ./gradlew uploadReleaseToHockeyApp --debug and saw this:
17:51:26.104 [DEBUG] [org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter] Executing actions for task ':app:uploadReleaseToHockeyApp'.
17:51:26.105 [DEBUG] [org.gradle.api.Task] Using android application variants
17:51:26.111 [DEBUG] [org.gradle.api.Task] Obfuscation is not used

When I use the Android gradle plugin version 1.3.1 it works fine and the mapping file is uploaded.
Wild guess : perhaps the API of the plugin was changed and the applicationVariant.getObfuscation() method that is used here doesn't exist anymore? I didn't investigate this further..

Hi,
thanks for your bug report.
The method is still available - but i see the same result with the missing mapping.txt on our project.
I will investigate this tomorrow why this happens.

Looks like applicationVariant.getObfuscation() is broken - i now use getMappingFile() instead.

New version (3.4) is released and should be available in 1-2 hours.

Thanks. I'll give it a try.

I also created a ticket for the gradle-android-plugin: https://code.google.com/p/android/issues/detail?id=195983

works with version 3.4 :+1: :top:


actually, we probably should include a dynamic combination generator in this fork

it's currently embedded in mixs_linkml_from_xlsx.py but could be extracted.

It looks like there would be 253 combination classes


Allows users to run computations in Apache Spark

Hi Shaik, thanks for submitting this. However, judging from the number of commits here, it looks like you could be merging from the wrong branch. I think the only commit we need is e9e6f71901849041477b2f5bc8438ad332220d63. I can take care of merging that commit.

Fixed in #182 / 2efd65644d3d0272ced200c0daccf9c8783e0751


Adding more precise repeating

What happened?
Hello, you have no discussion page so I ask here.
Do you plan to add hourly (most useable), minutely or even secondly repeating feature?
How to reproduce the bug

Package Version

PHP Version

Laravel Version

Which operating systems does with happen with?
No response
Notes
No response

Hi @theveloperspl
Thanks for binging that up. I'm not planning to add such repetition settings since I won't make use of it personally. but I welcome PRs.


Network dashboard: port utilization wrong unit

Describe the bug
Port utilization in Network dashboard shown wrong utilization in % due to wrong unit seleected. Harvest reports utilization in 0-1 format, but unit in Grafana is selected as 0-100.
Environment

Harvest version: harvest version 21.05.2-1 (commit ce091de) (build date 2021-06-14T20:31:09+0530) linux/amd64
Command line arguments used: /opt/harvest/bin/harvest restart --config /opt/harvest/harvest.yml
OS: CentOS 7
Install method: yum
ONTAP Version: 9.7
Other:

To Reproduce
Open network dashboard and look at Port utilization % graph and compare to receive/send graph.
Expected behavior
Unit in Grafana should be set to Percentile (0.0 - 1.0) instead of Percentile (0 - 100) as that will give correct results.

Actual behavior

Possible solution, workaround, fix
Change unit in graph settings.

changed percent limit from 0-100 to 0-1.

Verified the fix in Harvest <IP_ADDRESS>


Missing config.example

The link to config.example doesn't resolve, file seems to be missing.

Yeah, I messed up the .gitignore.. Should be fixed now
On Tue, Apr 13, 2021 at 5:53 PM Croq360 @.***> wrote:

The link to config.example doesn't resolve, file seems to be missing.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/wouterdebie/locast2tuner/issues/37, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABKABS6XQSQSUZGV55VKR3TITDNJANCNFSM424HCEVA
.


PUT and PATCH with identical mapping path can't coexist in editor

When the following is placed into the Swagger editor, the ui will show either the PUT or the PATCH, but not both.  Additionally, if the editor is shut down, then restarted, it crashes, requiring a manual edit of the swagger.yaml in order to get the editor going again.  Swagger definition and stack track posted below.
swagger definition
  /widget/{widgetId}:
    x-swagger-router-controller: widgetPut
    put:
      summary: Update a widget
      operationId: widgetPut
      consumes: ["application/json"]
      produces: ["application/json"]
      parameters:
        - name: widgetId
          in: path
          description: The UID of the widget
          required: true
          type: string
        - name: body
          in: body
          description: widget content
          required: true
          schema:
            type: object
      responses:
        "200":
          description: OK
          schema:
            $ref: "#/definitions/SuccessResponse"
        default:
          description: Error
          schema:
            $ref: "#/definitions/ErrorResponse"

  /widget/{widgetId}:
    x-swagger-router-controller: widgetPatch
    patch:
      summary: Patch a widget
      operationId: widgetPatch
      consumes: ["application/json"]
      produces: ["application/json"]
      parameters:
        - name: widgetId
          in: path
          description: The UID of the widget
          required: true
          type: string
        - name: body
          in: body
          description: widget content
          required: true
          schema:
            type: object
      responses:
        "200":
          description: OK
          schema:
            $ref: "#/definitions/SuccessResponse"
        default:
          description: Error
          schema:
            $ref: "#/definitions/ErrorResponse"

** stack trace ***
line 113 is referring to the second instance of the mapping key, which in this case is the patch version.
{ [YAMLException: duplicated mapping key at line 113, column 3:
      /messages/{messageId}:
      ^]
  name: 'YAMLException',
  reason: 'duplicated mapping key',
  mark:
   Mark {
     name: null,
     buffer: 'swagger: "2.0"\r\ninfo:\r\n  version: "0.0.1"\r\n  title: Project Castle APIs\r\n# during dev, should point to your local machine\r\nhost: localhost:10010\r\n# basePath prefixes all resource paths \r\nbasePath: /\r\n# \r\nschemes:\r\n  # tip: remove http to make production-grade\r\n  - http\r\n  - https\r\n# format of bodies a client can send (Content-Type)\r\nconsumes:\r\n  - applic
ation/json\r\n# format of the responses to the client (Accepts)\r\nproduces:\r\n  - application/json\r\npaths:\r\n\r\n  /messages:\r\n    x-swagger-router-controller: messagesCreateOrSend\r\n    post:\r\n      summary: Create and/or send a message\r\n      description: The message entity is entirely defined by the object passed in `body`, and is intentionally left implementation agnostic.  If `sen
d` is *false* the message should be saved as a draft, otherwise the message should be marked for delivery.  Either way, return the resulting `messageId`.  This endpoint MUST be called to create a message; updates should use **PUT /messages/{messageId}** or **PATCH /messages/{messageId}** \r\n      operationId: messagesCreateOrSend\r\n      consumes: ["application/json"]\r\n      produces: ["applic
ation/json"]\r\n      parameters:\r\n        - name: send\r\n          in: query\r\n          description: send message if *true*, save as draft otherwise\r\n          required: true\r\n          type: boolean\r\n        - name: body\r\n          in: body\r\n          description: message content\r\n          required: true\r\n          schema:\r\n            type: object\r\n      responses:\r\n
      "200":\r\n          description: OK\r\n          schema:\r\n            $ref: "#/definitions/ObjectResponse"\r\n        default:\r\n          description: Error\r\n          schema:\r\n            $ref: "#/definitions/ErrorResponse"\r\n\r\n\r\n  /widget/{widgetId}:\r\n    x-swagger-router-controller: widgetPut\r\n    put:\r\n      summary: Update a widget\r\n      operationId: widgetPut\r\n
     consumes: ["application/json"]\r\n      produces: ["application/json"]\r\n      parameters:\r\n        - name: widgetId\r\n          in: path\r\n          description: The UID of the widget\r\n          required: true\r\n          type: string\r\n        - name: body\r\n          in: body\r\n          description: widget content\r\n          required: true\r\n          schema:\r\n
type: object\r\n      responses:\r\n        "200":\r\n          description: OK\r\n          schema:\r\n            $ref: "#/definitions/ObjectResponse"\r\n        default:\r\n          description: Error\r\n          schema:\r\n            $ref: "#/definitions/ErrorResponse"\r\n\r\n\r\n  /widget/{widgetId}:\r\n    x-swagger-router-controller: widgetPatch\r\n    patch:\r\n      summary: Patch a wi
dget\r\n      operationId: widgetPatch\r\n      consumes: ["application/json"]\r\n      produces: ["application/json"]\r\n      parameters:\r\n        - name: widgetId\r\n          in: path\r\n          description: The UID of the widget\r\n          required: true\r\n          type: string\r\n        - name: body\r\n          in: body\r\n          description: widget content\r\n          required
: true\r\n          schema:\r\n            type: object\r\n      responses:\r\n        "200":\r\n          description: OK\r\n          schema:\r\n            $ref: "#/definitions/ObjectResponse"\r\n        default:\r\n          description: Error\r\n          schema:\r\n            $ref: "#/definitions/ErrorResponse"\r\n\r\n\r\n  /messages/{messageId}:\r\n    x-swagger-router-controller: messages
UpdateOrSend\r\n    put:\r\n      summary: Update or send a message\r\n      description: If `send` is *false* update the message, otherwise send the message.  Either way, return the messageId.\r\n      operationId: messagesUpdateOrSend\r\n      consumes: ["application/json"]\r\n      produces: ["application/json"]\r\n      parameters:\r\n        - name: messageId\r\n          in: path\r\n
  description: The UID of the message\r\n          required: true\r\n          type: string\r\n        - name: send\r\n          in: query\r\n          description: send message if *true*, save as draft otherwise\r\n          required: true\r\n          type: boolean\r\n        - name: body\r\n          in: body\r\n          description: message content\r\n          required: true\r\n          sch
ema:\r\n            type: object\r\n      responses:\r\n        "200":\r\n          description: OK\r\n          schema:\r\n            $ref: "#/definitions/ObjectResponse"\r\n        default:\r\n          description: Error\r\n          schema:\r\n            $ref: "#/definitions/ErrorResponse"\r\n\r\n\r\n  /attachments/{messageId}:\r\n    x-swagger-router-controller: attachments\r\n    post:\r\n
      summary: Attach a file residing on the user\'s device to a message\r\n      description: This endpoint should return the URI of the attachment\r\n      operationId: attachments\r\n      consumes: ["application/json"]\r\n      produces: ["application/json"]\r\n      parameters:\r\n        - name: messageId\r\n          in: path\r\n          description: The UID of the message to be associated
 with the attachment\r\n          required: true\r\n          type: string\r\n        - name: body\r\n          in: body\r\n          description: encoded attchment content\r\n          required: true\r\n          schema:\r\n            type: object\r\n      responses:\r\n        "200":\r\n          description: OK\r\n          schema:\r\n            $ref: "#/definitions/ObjectResponse"\r\n
 default:\r\n          description: Error\r\n          schema:\r\n            $ref: "#/definitions/ErrorResponse"\r\n\r\n\r\n  /search/messages:\r\n    x-swagger-router-controller: searchMessages\r\n    post:\r\n      summary: Returns messages for the authenticated user\r\n      description: Messages can be filtered using predefined parameters, or arbitrary search parameters can be defined using t
he \'arbitraryFilterParams\' parameter.\r\n      operationId: searchMessages\r\n      consumes: ["application/json"]\r\n      produces: ["application/json"]\r\n      parameters:\r\n        - name: body\r\n          in: body\r\n          description: Filters to use as part of the search\r\n          required: true\r\n          schema:\r\n            $ref: "#/definitions/Filter"\r\n      responses:\
r\n        "200":\r\n          description: OK\r\n          schema:\r\n            $ref: "#/definitions/ObjectResponse"\r\n        default:\r\n          description: Error\r\n          schema:\r\n            $ref: "#/definitions/ErrorResponse"\r\n\r\n\r\n# complex objects have schema definitions\r\ndefinitions:\r\n\r\n  Filter:\r\n    type: object\r\n    properties:\r\n      limit:\r\n        type
: string\r\n        description: Number of messages to return.  Limit is applied after messages have been filtered and sorted.\r\n      tags:\r\n        type: array\r\n        description: List of tags to filter on.  Only messages associated with these tags will be returned.\r\n        items:\r\n          type: string\r\n      userId:\r\n        type: string\r\n        description: Only messages b
elonging to the specified userId will be returned.  This can be used for delegation; the auth token pasesed with the request will be used to determine entitlement.\r\n      sortOrder:\r\n        type: array\r\n        description: An arbitrary string passed to the adapter ("ascending", "descending", "sentiment", etc).  Implementation is adapter-specific.  Should only be applied after all filtering
 is complete.\r\n        items:\r\n          type: string\r\n      startDate:\r\n        type: string\r\n        description: Only messages created/sent/received on or after this date will be returned.  Will work in conjunction with "endDate".\r\n      endDate:\r\n        type: string\r\n        description: Only messages created/sent/received on or before this date will be returned.  Will work in
 conjunction with "endDate".\r\n      sentiment:\r\n        type: array\r\n        description: The sentiment of the message.  Can be one or more values between 1.0 and -1.0\r\n        items:\r\n          type: number\r\n      arbitraryFilterParams:\r\n        type: object\r\n        description: Used to pass arbitrary key/value parameters to the adapter\r\n\r\n\r\n  ObjectResponse:\r\n    type: s
tring\r\n    description: Used to return an arbitrary string and an array of objects, both optional.\r\n    properties:\r\n      message:\r\n        type: string\r\n      data:\r\n        type: array\r\n        items:\r\n          type: object\r\n\r\n\r\n  ErrorResponse:\r\n    required:\r\n      - message\r\n    properties:\r\n      message:\r\n        type: string\r\n\u0000',
     position: 3295,
     line: 112,
     column: 2 },
  message: 'duplicated mapping key at line 113, column 3:\n      /messages/{messageId}:\n      ^' }

This issue was moved to swagger-api/swagger-editor#840


Disambiguate /users/me route (fixes #2933)

This makes sure that me doesn't match for :objectId at the route level.

It seems the wrong fix for the issue. The express handle should not fall through :objectId as we are not supposedly calling next() after handling the /me route...

Hmm, yeah, I think I must have had an old cached version of parse-server when I was debugging this. Never mind!

Alright! Let us know if it reappears :)


fix(lint): add default eslint file, fix cmd

Project linting was setup in a weird way:

there was a deprecated .eslintrcfile with minimal config
there was a non-standard eslint.json file with loads of rules
the npm script didn't find any errors when I tested by turning on the semi rule

I remember @zackarychapple had asked me for help some time ago and it was me that got back to him saying that we needed to use the npm script as eslint -c eslint.json './**/*.js', but when testing today on the console and trying to integrate with my editor, I found out that doesn't do anything.
This PR the consolidates all config in a standard .eslintrc.json file and explicitly lists dirs to lint (I tried not doing that but it seemed to hang on windows... my bet is that node_modules isn't being ignored automatically).

Follow up to the node_modules issue: https://github.com/eslint/eslint/issues/5780

Added .eslintignore and updated npm script to use solution provided in https://github.com/eslint/eslint/issues/5780#issuecomment-205341956.
The lint command now correctly works for all .js files inside the project, and it ignores the templates because they are .ts anyway.

<3 it !  LGTM.

Is this going to fix https://github.com/angular/angular-cli/issues/371?

Removed the inaccurate comment from .eslintignore, otherwise everything is the same.

Also related to the initial problem https://github.com/eslint/eslint/issues/5796

@hansl this is unrelated to #371, but I'll have a look at it with what I've learned from this PR.


Crash calling a class' #object_id or #hash

I was toying with the Class class and wondering why for example String == String returns false. Then I tried to implement it in terms of the object_id of the class (I figured it would have one, being an instance of Class) and it threw an error:
; ModuleID = 'main_module'

%String = type { i32, i32, i32, i8 }
%CFileIO = type { i8* }
%"->" = type { i8*, i8* }
%"struct.LibABI::UnwindException" = type { i64, i64, i64, i64, i64, i32 }
%Exception = type { i32, %String*, i1, %"Array(String)"* }
%"Array(String)" = type { i32, i32, i32, %String** }
%StringIO = type { i32, i8*, i32, i32, i32 }
%ArgumentError = type { i32, %String*, i1, %"Array(String)"* }

and many more lines.

Yup. The meta-model is kind of broken right now... we still have to rethink it and fix it.

This is working now. There's no object_id for a class as its represented as a number for now, but you can invoke crystal_type_id on them to get some kind of id.


Embed a Ruby interpreter into the bot so plugins can be written in Ruby

This would be such a cool feature.

Adding research:
https://silverhammermba.github.io/emberb/embed/


smart_class_demo : "Error reading network: cannot parse future versions: 6"

When trying to run the smart_class_demo (pulled the code a few days ago), I get the following error:
"Error reading network: cannot parse future versions: 6"
I read about a similar issue where it was suggested to use older versions of the pre-trained models. However, none of the previous version solved the problem. When I go back to R1 in the open_model_zoo library, the error changes to
Face Detection network output layer(658) should be DetectionOutput, but was Convolution
So I am at a loss which version to use here. Any help is greatly appreciated.

Hey, @pvk444 !
Supposedly, the master branch of this repo should work with the latest available release (R1 to date). Try to use model_downloader from this repo to get all the models you need.

@pvk444 please specify OpenVINO and Open Model Zoo versions that you're using. Is the problem reproducible with OpenVINO R2'2019?

It's unclear to me how this is possible. At the time of this issue's creation the models referenced from the master branch of the repo had version 5, not 6. Moreover, I've checked the face-detection-adas-0001.xml model from R1, and the output layer is of type DetectionOutput.
However, the issue should be moot by now anyway. R2 is already out, and Inference Engine now supports version 6 models. So I'm going to close this; please reopen it if you still have problems.


[RFC] Automatic routing for bulk

Requirement
In logs analytics use case of OpenSearch, users may ingest large numbers of documents into the cluster, so the cluster may have big scale, having hundreds of nodes and thousands of shards distributed on different nodes. When using bulk api to ingest documents, the documents will be dispatched to all of the shards in different nodes by the coordinate node, if one of the nodes in the cluster get stuck by JVM full GC or one of the shards has performance issue, then the whole processing time of the bulk operation will be increased and may cause the queue of the write thread pool holds too many pending indexing requests and then cause indexing rejection.
Instead of distributing the indexing requests to different nodes, some users add a random routing value to each of the indexing requests in the bulk operation, to route all of the indexing requests in one bulk operation to only one shard, this can reduce the impact of the long-tail shard or stuck node, reduce the network roundtrip,  and reduce the indexing latency and cpu usage, and then improve the indexing performance.
Even though we can add routing to the indexing requests in the client side, but some common-used ingest tools such as Logstash, Filebeat, Fluent-bit do not support setting random routing value for bulk operation, so users cannot be benefited, the only way they can do is that they use their own ingest tools or use OpenSearch client to ingest documents, write some code to implement automatic routing for bulk, which is not friendly.
Proposal
So my proposal is that we implement automatic routing for bulk in OpenSearch server side, generate a random routing value for each bulk, all of the indexing requests in the bulk will have the same routing value and will be written to the same shard, results in improving the performance of the cluster. We can add an index level setting which can enable or disable the automatic bulk routing for every index, and this setting can be updated dynamically, that makes it convenient to use.
Here is a diagram showing the difference between bulk request without routing and bulk request with automatic routing.

Negative effects
However, automatic routing for bulk can introduce some small issues, one issue is that it may cause data skewness between shards, because the number of indexing requests in each bulk maybe different, so the storage between shards maybe not balanced in a short time, but with continuous ingesting documents, the storage will be balanced eventually. On the other hand, in most cases, ingest tools are used to write documents to OpenSearch, so the number of indexing requests in each bulk always are same in most time because the configuration like bulk size in these tools are fixed, so data skewness may not be a problem. Another issue is that users are unable to use GET API to get document by doc id  without specifying the routing value after they enable this feature, but in log analytics scenario it’s not common to use GET API, and actually, they can use IDs query instead to get a document by its id, like this:
GET test/_search
{
  "query": {
    "ids": {
      "values": ["V9Yz04kBPxX-VGLPvqlZ"]
    }
  }
}

Overall, automatic routing for bulk is recommended to be used in log analytics and other use cases which write more and read less, the OpenSearch cluster have big scale and high ingesting load, and the indices which are ingesting documents has hundreds of primary shards and even more. Users can benefit from this feature by reducing the indexing latency and indexing rejection, and then improving the indexing performance.

Similar issue https://github.com/opensearch-project/OpenSearch/issues/4984

@Bukhtawar yeah, the requirement in that issue is similar to this one, but our solution is quite simple, just generate a random string routing for each bulk in server side to route all the indexing requests in one bulk to one shard. One user of AWS OpenSearch Service reported that currently they generate the random routing in their client, and get indexing performance improved and lower write rejection than before, so they want OpenSearch to implement random routing for bulk functionality in server side so that they can use this functionality much easier.

@gaobinlong we have been prototyping very different approach for bulk indexing that changes the way the data goes in and out, moving off from batching to streaming, there are still opportunities to improve the coordinator roles in how to dispatch the bulk requests internally  (from one or many clients).

So my proposal is that we implement automatic routing for bulk in OpenSearch server side, generate a random routing value for each bulk, all of the indexing requests in the bulk will have the same routing value and will be written to the same shard, results in improving the performance of the cluster.

I see a few other problems with this approach (beside the ones you mentioned, please correct me if I am wrong):

it will conflict with any user defined routing
it will introduce the deviation in behaviour between indexing the same document using index API or bulk API (since we won't respect the default routing rules and that may impact search lookup I believe)

[1] https://github.com/opensearch-project/OpenSearch/issues/3000

@reta for the streaming API, can we stream the the payload directly to the data nodes and ensure we pass the routing information back in the response so that it is transparent to the end user?

@gaobinlong This solution makes updates inefficient. Also, the get API will not work.
@reta With streaming API as well, the span out is what makes everything inefficient. Additionally, having an ability to decouple the routing from the id(especially when our system generates the id e.g. data streams) makes it simple for us to adaptive shard selection on indexing in future.

I see a few other problems with this approach (beside the ones you mentioned, please correct me if I am wrong):

it will conflict with any user defined routing
it will introduce the deviation in behaviour between indexing the same document using index API or bulk API (since we won't respect the default routing rules and that may impact search lookup I believe)

[1] #3000

@reta If there are user defined _id or routing existing in the incoming documents of the bulk request, automatic routing will not be generated for these documents, users can still use custom _id and _routing if they want.
For indexing same document using index API or bulk API, I think automatic routing will not impact the search results, because without using custom routing, when calling search API, it will execute query on every shard and then collect results, the results are same; and if user specifies custom routing, automatic routing takes no effect, the results are still the same.
For streaming index API, I've read the issue carefully, it's really a cool feature, but I think we have a long way to go if we want most ingestion tools such as Logstash, Beats, Fluent-bit and other third-party tools to support that API, so if bulk API will not be deprecated in the future, the automatic routing feature for bulk is still valuable?

Thanks @gaobinlong

@reta If there are user defined _id or routing existing in the incoming documents of the bulk request, automatic routing will not be generated for these documents, users can still use custom _id and _routing if they want

:+1:

For indexing same document using index API or bulk API, I think automatic routing will not impact the search results, because without using custom routing, when calling search API, it will execute query on every shard and then collect results

That's where I see the potential problem: the fetch phase would go and fetch documents, the _id is used as the default routing strategy to locate the right shard.

For streaming index API, I've read the issue carefully, it's really a cool feature, but I think we have a long way to go if we want most ingestion tools such as Logstash, Beats, Fluent-bit and other third-party tools to support that API, so if bulk API will not be deprecated in the future, the automatic routing feature for bulk is still valuable?

Yes, we have a long way to go, and yes, we won't be removing the old API in foreseeable future

@gaobinlong From the discussion here looks like there will be impact on the get API and search fetch path. There are other alternatives which are being considered to improve the indexing performing issues. Do you think those alternatives can help here ? If yes, then feel free to resolve this issue.

That's where I see the potential problem: the fetch phase would go and fetch documents, the _id is used as the default routing strategy to locate the right shard.

@reta, @sohami , for search API, this feature will not impact it because the result of the query phase contains the shard id, so in fetch phase, we get the target shard id by the query result directly:
https://github.com/opensearch-project/OpenSearch/blob/b3049fb5ec860f63fdfe33c5b176869b1e4255e6/server/src/main/java/org/opensearch/action/search/FetchSearchPhase.java#L183
, but for get API, I'm thinking of transform the get document request to a search request when this feature is enabled for the target index, even though the performance is less efficient, but because this feature targets for the use cases like log analytics, observability and security analytics which writes more and read less, get/update/delete document APIs are rarely used, so it could be acceptable by the users(we should document this negative effect), what do you think about this?
@sohami I think this feature may not conflict with other alternatives, it mainly aims to  reduce the impact of the long-tail shard or stuck node, reduce and indexing rejection and the cpu usage of the node, it can improve the indexing performance in a whole, but will not improve the indexing performance in document or shard level, so if other alternatives can improve the indexing performance in document or shard level, I think they can be combined to get great benefits.

, but for get API, I'm thinking of transform the get document request to a search request when this feature is enabled for the target index, even though the performance is less efficient, but because this feature targets for the use cases like log analytics, observability and security analytics which writes more and read less, get/update/delete document APIs are rarely used, so it could be acceptable by the users(we should document this negative effect), what do you think about this?

@gaobinlong I think we for observability in particular, get API is super useful and used quite often (find trace by _id fe). I am reluctant to move forward with this proposal taking into account that we already have tools for users to use custom _id and _routing (if they want). But I may certainly miss something, but I think we have other options to better address the issue at large.


lua global variable usage

From the latest draconis, as of 2022-02-13:
2022-02-13 19:22:19: WARNING[Main]: Undeclared global variable "registered_nodes" accessed at /home/1hit/worlds/world/worldmods/draconis/mapgen.lua:34
2022-02-13 19:22:41: WARNING[Main]: Assignment to undeclared global "ice" inside a function at /home/1hit/worlds/world/worldmods/draconis/items.lua:12.

Fixed as of latest commit.


Fix #35369.

This commit removes the runtime flag introduced in #31065 since it has been 6 months since that change.

I'm not sure what's happening in the workflow run, but I'll resolve the merge conflicts for starters:
Merge commit information not found for pull request 35386.
Error: Process completed with exit code 1.
Error: The template is not valid. envoyproxy/toolshed/actions-v0.2.31/gh-actions/github/checkout/action.yml (Line: 143, Col: 12): Error reading JToken from JsonReader. Path '', line 0, position 0.```

LGTM, thanks!

@adisuissa I had to rebase again to deal with a new conflict on the changelog, and it looks like that killed your review.
Should I use merge commits instead of rebasing to resolve this kind of conflict in the future?

@adisuissa I had to rebase again to deal with a new conflict on the changelog, and it looks like that killed your review. Should I use merge commits instead of rebasing to resolve this kind of conflict in the future?

Yes, merge is better than rebase+force-push. See contribution guidelines.

@adisuissa I had to rebase again to deal with a new conflict on the changelog, and it looks like that killed your review. Should I use merge commits instead of rebasing to resolve this kind of conflict in the future?

Yes, merge is better than rebase+force-push. See contribution guidelines.

I did a merge instead of a rebase this time and Github still dismissed your review.
Is there some other way I should be fixing the merge conflicts?
Or should I let someone with write access fix the merge conflicts in the changelog, so that they can merge immediately instead of needing to fix it multiple times?


Build license info component

Type

✨ Feature

UI Requirements

[ ] Word/related icons for all possible licenses

Acceptance Criteria

[ ] The interface should be able display appropriate icons and text for all licenses

Problem to be solved / User Story
In order to
understand how I should cite this material
As a
user
I need/want/expect
to see clear licensing information on the item page

Could we try a variant with the CC BY spelled out like they do on Soundcloud? Creative Commons License
https://soundcloud.com/wellcomelibrary/diagnosis-of-a-depressive-illness-in-general-practice

@jennpb do you have a list of the licenses we need to cater for? thanks

@gestchild
CC0
CC BY
CC BY NC
CC BY NC ND
PDM
Copyright not cleared
I don't think we have any SAs.

Duplicate of #1078


Only use MCP Golden AMIs

MCP will only allow the use of Golden AMIs as part of Kubernetes clusters. SPS deployments need to include only those.

MCP updates the list of Golden AMIs on the 15th of each month, and publishes the list to SSM parameters in each account with the following keys:
/mcp/amis/aml2-eks-1-XX
where XX matches the version of the Kubernetes cluster where it can be deployed
Drew modified the SPS Terraform scripts to automatically retrieve the AMIs values from those parameters at deployment time.
This means that every new deployment will automatically use the correct AMIs, and existing deployment will have to be re-deployed at most every 5-6 months, when MCP sends us a warning email...


Update README.md

Add a new line return to fix the configuration file sample.

Thanks @lilic, just submitted a PR to that repo :)

/close
Thanks! 🎉 Closing this one.


fix: prerelease nuget generation

Trouble when building prereleases NuGet packages. Seems like there's a problem with the tool-script we're using.
Including exported DSC resources causing the problem, but since we're not using that, I commented out and documented.

If we have time left in the future, we can look into it further, for now, it seems enough.


Java: Add HSCAN command

Issue #, if available:
N/A
Description of changes:
Add support for the HSCAN command to the Java client. The NOVALUES clause is not supported due to being added in Redis 7.2.5
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

This PR currently includes the contents of #1705 since it's based on it.


catalyst: init at 3.8.2

Description of changes
Add Catalyst to nixpkgs.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Icon doesn't seem to be working and I'm not sure why

I'll have to make a new pull request


Replaced HashMap in ZooCacheFactory with bounded-size Cache

Related to #2699

Closing due to @ctubbsii comment


the penultimate exception is thrown instead of the last one

Description
When a series of different exceptions is thrown, the last one is expected to be thrown from the Retry::execute() call
Actually, the second-to-last one is thrown.
Change Log

Added

Fixed

The correct exception is thrown if multiple ones occur during execution

Changed

Updated

Removed

Deprecated

Security

closed by #64

thx ;) if you could please tag 1.0.9 before Monday — I have a PR that would benefit from this change 😂

thanks @maciejlebkowski I will tag new version tomorrow 😁

@mlebkowski i just released 1.0.9, sorry for the delay

thx, appreciate quick reaction 👏


FZF Bash reverse I-search is autopopulated with unknown sequence of characters

[x] I have read through the manual page (man fzf)
[x] I have the latest version of fzf
[x] I have searched through the existing issues

Info

OS

[x] Linux
[ ] Mac OS X
[ ] Windows
[ ] Etc.

Shell

[x] bash
[ ] zsh
[ ] fish

Problem / Steps to reproduce
I installed fzf using git, enabling bash key bindings. Initially, the keybindings worked wonderfully. Now, every time I type ctrl-R, 2-4 repetitions of 1R or ;1R are entered automatically.

I have confirmed that the issue is not with the binary by running seq 10000 | fzf.
Do you know what might be causing this issue?
Thanks for creating fzf, and for your help in advance!

I'm not sure what's going on. Does disabling mouse help? i.e. export FZF_DEFAULT_OPTS='--no-mouse'

Only one ;1R was printed out when I exported this option.

What happens when you run echo -e "\x1b[6n"? What is printed on the screen? And have you tried using a different terminal emulator?

In a Jupyter Lab terminal using Bash:
$ echo -e "\x1b[6n"

$ ;1R;1R;1R

I suppose that's the same output! The second and third ;1R show up after a short delay.
Do you have any suggestions for other emulators I could try?

The second and third ;1R show up after a short delay.

They shouldn't. See "Device Status Report" in https://en.wikipedia.org/wiki/ANSI_escape_code.
What about this one? What do you see on the screen? Note that you should terminate cat with CTRL-C.
echo -e "\x1b[6n"; cat

The sequence reports the cursor position on the screen. This is how it looks on my terminal.
> echo -e "\x1b[6n"; cat

^[[2;1R^C
> echo -e "\x1b[6n"; cat

^[[5;1R^C
> echo -e "\x1b[6n"; cat

^[[8;1R^C
> echo -e "\x1b[6n"; cat

^[[11;1R^C

ctrl-C doesn't terminate cat for me, but hitting ctrl-D twice does. If I type something in cat, the first ctrl-D prints out what I just typed in, and the second ctrl-D terminates.
For cat alone, ctrl-D once terminates.
$ echo -e "\x1b[6n"; cat

^[[2;1R^[[2;1R^[[2;1R^C^C^C^C$
$ echo -e "\x1b[6n"; cat

^[[25;1R^[[25;1R^[[25;1R$
$ echo -e "\x1b[6n"; cat

^[[21;1R^[[21;1R^[[21;1Rsometextsometext$

ctrl-C doesn't terminate cat for me; two ctrl-Ds do, though. If I type some text, the first ctrl-D duplicates the text, and the second ctrl-D terminates.
With cat alone, one ctrl-D terminates.
$ echo -e "\x1b[6n"; cat

^[[2;1R^[[2;1R^[[2;1R^C^C^C$
$ echo -e "\x1b[6n"; cat

^[[5;1R^[[5;1R^[[5;1R$
$ echo -e "\x1b[6n"; cat

^[[8;1R^[[8;1R^[[8;1Rtexttext$
$ cat
$

So for some reason, your terminal emulator is reporting the cursor position three times instead of one and they are fed into fzf prompt. Ideally, this should be fixed from your terminal emulator's side, but I can make fzf ignore those extra sequences.

Thank you! The support is much appreciated.


Test results for all 0.9.0 editor images

Description
I ran tests for all 0.9.0 editor images.
[The test project][https://github.com/mob-sakai/docker/tree/main/reference-project-test]:

The default packages (for the installed Unity version) will be installed.
IL2CPP will be selected as backend scripting (except for base, windows-mono and mac-mono).
Contains empty tests for playmode and editmode.

Category
Action
Description

Build
unity-builder@main
Build an empty scene.

Test
unity-test-runner@main
all test mode.

Results
The test workflows have been dispatched as follows:

Test All ✅(Run manually. Find all 0.9.0 editor image tags in DockerHub and dispatch the test workflows for each modules.): Result

(dispatch) -> Test All ✅ (base, [2018.3.1f1, 2018.3.2f1, ...]): Result
(dispatch) -> Test All ❌ (linux-il2cpp, [2018.3.1f1, 2018.3.2f1, ...]): Result
(dispatch) -> Test All ✅ (windows-mono, [2018.3.1f1, 2018.3.2f1, ...]): Result
(dispatch) -> Test All ✅ (mac-mono, [2018.3.1f1, 2018.3.2f1, ...]): Result
(dispatch) -> Test All ❌ (android, [2018.3.1f1, 2018.3.2f1, ...]): Result
(dispatch) -> Test All ✅ (ios, [2018.3.1f1, 2018.3.2f1, ...]): Result
(dispatch) -> Test All ✅ (webgl, [2018.3.1f1, 2018.3.2f1, ...]): Result

Failures

Module
Version
Cause

android
2019.2.0f1
exit code: 134

linux-il2cpp
2019.3.0f6
il2cpp.exe did not run properly. unknown arguments: --sysroot-path=/

linux-il2cpp
2019.3.1f1
il2cpp.exe did not run properly. unknown arguments: --sysroot-path=/

linux-il2cpp
2019.3.2f1
il2cpp.exe did not run properly. unknown arguments: --sysroot-path=/

linux-il2cpp
2019.3.3f1
il2cpp.exe did not run properly. unknown arguments: --sysroot-path=/

linux-il2cpp
2019.3.4f1
il2cpp.exe did not run properly. unknown arguments: --sysroot-path=/

linux-il2cpp
2019.3.5f1
il2cpp.exe did not run properly. unknown arguments: --sysroot-path=/

linux-il2cpp
2019.4.0f1
C++ code builder is unable to build C++ code for Linux: Could not find valid clang executable at clang

Do we need to fix or ignore the failed image?
Note

This test results DO NOT guarantee that the 'successful' image supports all use cases.
The 2018.2.x images has been created but be ignored for test.

Since these are all older versions (<=2019.4.0f1), we can probably ignore these? We can put a comment on https://game.ci/docs/game-ci/docker-images#older-versions-of-unity, saying we support versions > 2019.4.0f1.

As for this repo we're providing docker images, which I would argue is a bit more universal than CI specifically. Therefor I would not drop support for <= 2019.4.0f1.
However it looks like all errors are in early patch levels of new minor releases (all starting from 0f1 or 0f6), and based on that I think it's perfectly acceptable to not fix these.
I do think it would be useful to keep a list of defects somewhere. This could be a nice addition to the UI of the versioning backend. If we were to be able to create an issue there and link it to certain builds as well as github issues, then we have it nicely documented.

Since @mob-sakai fixed most of the failures listed here, should we close this issue and open a separate issue just for the android-2019.2.0f1 exit code: 134 error?


Collab notebook error during Phyloio visualization

"Run Foldtree" and ""Plot Foldtree output" finish successfully, but the PhyloIO visualization fails due to id_mapper error (image attached).

I've successfully run the phylo io step today. can you tell me what input you used so I can replicate the error?


Z5: Early import seems to create race condition and afterwards citekey confusion

Be being really nasty to BBT, it seems that I have produced a strange citekey confusion:
Starting from Zotero 5.0.20 without the BBT addon I imported the file
hystop-redu.txt
(renamed to hysop-redu.bib) five times. Afterwards I installed BBT 5.0.22 and
restarted zotero. After the restart I did not wait for BBT to become ready, but
immediately started to import the file hystop-redu.bib again while BBT was occupied with
dealing with all the entries in my library without citekeys.
Hence, in the 6th imported version of hystop-redu.bib, my citekeys were not imported.
Now, after this import was complete and also BBT was ready for business,
I imported  hystop-redu.bib again.
Clicking now on the first tag, i.e. on "<-- Tag Not Handled ..><--keyword=#key0 ............",
and clicking afterwards on the corresponding paper in the central paper list, I get
, i.e. the citekey in the central list and in the info window is
equal to the citekey Klein-2013-HMM in my bibfile.
Now, clicking on Tags, afterwards on notes and afterwards on info in the right-hand part of the
zotero window, I get
, i.e. the citekey in the info window is now
Kleinrepresentationresulthysteresis2014b but the citekey in the center is still  Klein-2013-HMM.
And now it becomes even more wired: Attaching the dataset for this  paper in the sixth, i.e. in the second to last,  import of  hystop-redu.bib,  by clicking the strange tag and clicking on
the  dataset method again, and returning afterwards to the dataset within the last import
of hystop-redu.bib, the citekey in the import window become Klein-2013-HMM again.
I agree that this error in this situation is maybe not important, since I ignored that BBT is not ready,
but considering it may allow to get rid of a more general problem.

If you're importing before BBT says "ready for business", you're importing using the stock importers of Zotero. I wish to X1 that I could just lock the Zotero UI until BBT is ready for business, or that Zotero would have a clean mechanism allowing extensions to initialize, but I can't, and it doesn't. I'm hoping one of the Zotero devs gets me some info, but I'm not holding my breath. The init circus has cost me a disproportionate amount of time already, so I can't assure you I'm going to try and work around this without infra support by Zotero.
I'm having some difficulty following the scenario TBH. I'd need to see the content of the extra field, because right now I don't know whether a citekey is pinned. A copy of your Zotero DB and the better-bibtex.sqlite files may tell me more.
1 where X is your pick of deity, I'll take whatever works.

Since there seems now to be a kind of progress bar part of zotero, showing up e.g. if one tries
to empty the trash if it contains many items, there may be some (small?) hope to get access to this component maybe also  from your extension.
But, after some tests I realized now that my problem seems not to be an  problem with the initialization of BBT, but a general bug:
I seems that the citekey of the first open opened is stored somehow, and is shown up
later for all papers in the "info" tab on the right-hand side,  if before the "notes" or the "tag"-tab
have been cheeked.
To reproduce this
I start Zotero 5.0.20 with BBT 5.0.22 and wait until BBT is ready for business. Afterwards I import
citekey-conf.txt,
and open the first entry (Aaa) in the list. Afterwards I open the second entry (Bbb) in the list.,
and the citekey shown in the info tab is BBB, i.e. the citekey in my bibtex file, which was imported imported thanks to thanks to BBT.
Opening the tags view, afterwards the notes view and finally the info view again, I end up with:

So the citekey displayed in the  info panel now shows the  citekey AAA, i.e. the one displayed for the first paper opened. If I open now the last paper (CCC)  in the list, the citekey shown initially is the correct one, but after opening the  the tab view or the note view and reopening the info
view, the displayed citekey key ist AAA again.
If I quit afterwards zotero and start it again, and now open e.g. the last paper in this libary, i.e. (CCC),
then this citekey shows up for all papers in the info view, if before the notes or the tags view were chose.

I could indeed tap into the progress bar, so the init race condition should now be solved in .23
The info pane citekey not updating is currently a known problem -- the item pane is really resistant to monkey patching. I'll try what I can but it's starting to look like the real solution will only come when Zotero adds the citekey field as a native field. This is planned, but there's no clear time line -- but not before the end of the year.

:robot: bleep bloop; this is your friendly neighborhood build bot announcing test build 4325 ("itemPane refresh").

Can you try 4325?

4325 solves the item pane refresh problem.

Thanks for your efforts.
(As check for the "user have to wait" time, I have imported https://github.com/retorquere/zotero-better-bibtex/files/1318045/hystop-redu.txt renamed to hysop-redu.bib five times to zotero 5.0.20 without bbt. After installing bbt, 4325 and
restarting zotero  BBT blocked the  zoterio UI for around 22 seconds since also the citekey needed
to be created. At the following start of zotero, bibtex blocked the UI for around 6 seconds. )
P.S.: I have really tried to create problems by removing/deinstalling BBT just during a file import, but I have not succeed.

(For comparison: If I remove the collections and the iitems of my five hysop-redu.bib inports,
empting the trash takes around 4 seconds.)

It's possible that Zotero will at some point have a more structural solution for extension init, but right now this makes sure BBT is in a stable state before you can start messing with its database.
I think I've also fixed the issue from https://github.com/retorquere/zotero-better-bibtex/issues/737#issuecomment-331079921 (to the extent that it is fixable at all) -- are you satisfied with how it works now?

Oh wait you already said it was fixed. Great, then I'm merging this in.


Segfault on running sample roundtrip with ASAN

Compile:
g++ -fno-omit-frame-pointer -fsanitize=address -g3 roundtrip.c -o roundtrip -I../../include/ -L../../src/.libs/ -llcms2
Run:
./roundtrip ../../testbed/test1.icc
ASAN:SIGSEGV
==10718== ERROR: AddressSanitizer: SEGV on unknown address 0x000000000008 (pc 0x7f634eeb302c sp 0x7fff570ac170 bp 0x7fff570ac210 T0)
AddressSanitizer can not provide additional info.
==10718== WARNING: Trying to symbolize code, but external symbolizer is not initialized!
#0 0x7f634eeb302b (/home4/Little-CMS-master/src/.libs/liblcms2.so.2+0x7002b)
src/cmsxform.c:189
#1 0x400f95 (/home4/Little-CMS-master/utils/samples/roundtrip+0x400f95)
utils/samples/roundtrip.c:67
#2 0x7f634e799ec4 (/lib/x86_64-linux-gnu/libc.so.6+0x21ec4)
#3 0x400a48 (/home4/Little-CMS-master/utils/samples/roundtrip+0x400a48)
==10718== ABORTING
Analysis:
It fails with test1.icc,test2.icc & bad.icc. Pass with test3.icc, test4.icc & test5.icc
It faults in dereference:
189     p -> xform(p, InputBuffer, OutputBuffer, Size, 1, &stride);

Fixed, thanks for pointing it out.
Regards
Marti Maria
The LittleCMS project
http://www.littlecms.com
From: Gaurav<EMAIL_ADDRESS>Sent: miércoles, 25 de noviembre de 2015 3:22
To: mm2/Little-CMS<EMAIL_ADDRESS>Subject: [Little-CMS] Segfault on running sample roundtrip with ASAN (#65)
Compile:
g++ -fno-omit-frame-pointer -fsanitize=address -g3 roundtrip.c -o roundtrip -I../../include/ -L../../src/.libs/ -llcms2
Run:
./roundtrip ../../testbed/test1.icc
ASAN:SIGSEGV
==10718== ERROR: AddressSanitizer: SEGV on unknown address 0x000000000008 (pc 0x7f634eeb302c sp 0x7fff570ac170 bp 0x7fff570ac210 T0)
AddressSanitizer can not provide additional info.
==10718== WARNING: Trying to symbolize code, but external symbolizer is not initialized!
#0 0x7f634eeb302b (/home4/Little-CMS-master/src/.libs/liblcms2.so.2+0x7002b)
src/cmsxform.c:189
#1 https://github.com/mm2/Little-CMS/pull/1  0x400f95 (/home4/Little-CMS-master/utils/samples/roundtrip+0x400f95)
utils/samples/roundtrip.c:67
#2 https://github.com/mm2/Little-CMS/issues/2  0x7f634e799ec4 (/lib/x86_64-linux-gnu/libc.so.6+0x21ec4)
#3 https://github.com/mm2/Little-CMS/pull/3  0x400a48 (/home4/Little-CMS-master/utils/samples/roundtrip+0x400a48)
==10718== ABORTING
Analysis:
It fails with test1.icc,test2.icc & bad.icc. Pass with test3.icc, test4.icc & test5.icc
It faults in dereference:
189 p -> xform(p, InputBuffer, OutputBuffer, Size, 1, &stride);
—
Reply to this email directly or view it on GitHub https://github.com/mm2/Little-CMS/issues/65 .  https://github.com/notifications/beacon/AAMLwh2pQtEs72uvvJfTFJOpLaUdCkPzks5pJRLOgaJpZM4Go5Xp.gif

Also, I noticed other samples are written with old code base, they need to be modified for correct working.


create pulsar-io source/sink fail by use "--sink-config-file"

Describe the bug
A clear and concise description of what the bug is.

create pulsar-io source/sink fail by use "--sink-config-file", but use "--sink-config" key/value is ok.
pulsar 2.5.2
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]

Additional context
Add any other context about the problem here.

@xuesong172500 Hi, --sink-config-file should be in YAML format and source-config is JSON format.

Close this issue since the question has been answered by @Technoboy-


namespaces incorrect check in custon commands

🐞 Bug Report
Please fix regex check namespaces in command custom files:
in https://github.com/php-telegram-bot/core/blob/9ca6158f9fe6cf5aa06f9c46377b3c1164bdf444/src/Telegram.php#L350
if you set a tab or a space before 'namespace ...', this regex does not work as expected
this solution fixed issue:
if (preg_match('#^\s+namespace\s+(.+?);#m', $content, $m)) {

?
!

Operating system
Ubuntu

PHP Telegram Bot version
last

PHP version
7.4

MySQL version
none

Update Method
Webhook / getUpdates

Hi @alligator77, thanks for reporting!
We just need to make sure that there are no false positives, so we try to keep that regex as "strict" as possible.
Out of curiosity, why do you have your namespace declaration indented?

Hi @alligator77, thanks for reporting!
We just need to make sure that there are no false positives, so we try to keep that regex as "strict" as possible.
Out of curiosity, why do you have your namespace declaration indented?

#^\s+namespace\s+(.+?);#m works fine with and without spaces or tabs
PHPStorm indented this by default

Counter question, why isn't PSR4 used to download commands?
Minimum php version in composer 7.x, but still use include_once?

@alligator77 Very valid question. The whole structure of the commands is very not-pretty, I know. The initial idea of how commands should be loaded is an outdated way of thinking but the new way hasn't been implemented yet.
There are a few issues about this but nobody (including me) has had the time to have a go at it 😕
(Check the "Commands" column here: https://github.com/php-telegram-bot/core/projects/1)
Absolutely it should be managed better though, which will hopefully happen at some point!

@alligator77 Very valid question. The whole structure of the commands is very not-pretty, I know. The initial idea of how commands should be loaded is an outdated way of thinking but the new way hasn't been implemented yet.
There are a few issues about this but nobody (including me) has had the time to have a go at it 😕
(Check the "Commands" column here: https://github.com/php-telegram-bot/core/projects/1)
Absolutely it should be managed better though, which will hopefully happen at some point!

I think, need to predefined commands list (These class files are in fact already present and rarely change in production) commans in config by name in array key, like:
[
  'user' => [
     'start' => 'name\space\to\StartCommand',
  ]
]

and then load classes if need via psr.
Just need to refactoring method getCommandObject and add property for commands list..
Essentially, there are few changes.


Added RegisterContext.closeHeaders logic

Added support for a closeWithHeaders flag on RegisterContext.register. If true, the supplied headers will be sent to RegisterContext.unregister from RegisterContext.close. Related discussion can be found at #180

Looks good.  Thanks!


Fix “incomplete” typo

This fixes the “incompelte” -> “incomplete” typo in the README.

Coverage decreased (-0.02%) to 99.301% when pulling dc4d6510d5eccf52435504f66a48c5a64ea3f1bb on ddfreyne:patch-1 into ddf42a00a514ef58adb3752e3ecd3019f4e78bf7 on piotrmurach:master.

Thanks ❤