System.DllNotFoundException: Unable to load DLL 'OpenCvSharpExtern'

Summary of your issue
An error occurs in OpenCV version 4.
This occurs only in the Windows 10 Pro N version. Additional media packs are installed.
It's OK in the Windows 10 Pro.
System.TypeInitializationException: The type initializer for 'OpenCvSharp.NativeMethods' threw an exception. ---> System.DllNotFoundException: Unable to load DLL 'OpenCvSharpExtern': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
   at OpenCvSharp.NativeMethods.redirectError(CvErrorCallback errCallback, IntPtr userdata, IntPtr& prevUserdata)
   at OpenCvSharp.NativeMethods.LoadLibraries(IEnumerable`1 additionalPaths)
   at OpenCvSharp.NativeMethods..cctor()
   --- End of inner exception stack trace ---
   at OpenCvSharp.NativeMethods.imgcodecs_imread(String filename, Int32 flags)
   at OpenCvSharp.Mat..ctor(String fileName, ImreadModes flags)
   at TemplateMatchLibrary.Form1.button1_Click(Object sender, EventArgs e) in C:\Factory\TemplateMatch\TemplateMatchOpenCvSharp\TemplateMatchOpenCvSharp\Form1.cs:line 45
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Environment
OpenCVSharp 4
Windows 10 Pro N, Version 10.0.10586

Additional media packs are installed.

is it this package? https://support.microsoft.com/en-us/help/4039813/media-feature-pack-for-windows-10-n-october-2017
To check dependencies of your OpenCvSharpExtern.dll is helpful. https://github.com/shimat/opencvsharp/issues/610

Hi, In my case my code run when I downgrade version to OpenCvSharp3-AnyCPU, and in Debug folder has an folder dll contain OpenCvSharpExtern.dll


[S2GRAPH-188]: migrate log4j.properties to log4j2.xml

s2rest_play.log:
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/data/home/apache-s2graph-0.2.1-SNAPSHOT-incubating-bin/lib/log4j-slf4j-impl-2.9.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/data/home/apache-s2graph-0.2.1-SNAPSHOT-incubating-bin/lib/slf4j-log4j12-1.7.21.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console. Set system property 'log4j2.debug' to show Log4j2 internal initialization logging.
NettyServer.main is deprecated. Please start your Play server with the play.core.server.ProdServerStart$.main.
fix https://issues.apache.org/jira/browse/S2GRAPH-188

@SteamShon  Will u look at it?

@sandyskies Thank you for fixing it.
I noticed that the ERROR message disappears after the log4j2.xml file has been migrated.
After adding the license header, I merge.
Thank you


Widget garbage collection

What steps will reproduce the problem?
Relates to #14102
Since now widgets may have event handles and behaviors attached to them.
This cause a memory leaks while widget usage as widget instance and behavior introduce a cycle reference.
Thus any usage of the Widget with attached behavior causes memory leak.
AnyWidget::widget([
    'id' => 'test',
    'as test' => [
        'class' => TestWidgetBehavior::className()
    ],
]);

What is the expected result?
Widget instance to be destroyed.
Memory usage stays the same after Widget::widget() or Widget::end().
What do you get instead?
Widget instance remains in memory consuming space without purpose.
Additional info

Q
A

Yii version
2.0.12

PHP version
*

Operating system
*

Unit test to reproduce:
class TestWidget extends Widget
{
    public static $instanceCount = 0;

    public function __construct($config = [])
    {
        parent::__construct($config);
        static::$instanceCount++;
    }

    public function __destruct()
    {
        static::$instanceCount--;
    }
}

class WidgetTest extends TestCase
{
    public function testGc()
    {
        TestWidget::widget([
            'id' => 'test',
            'as test' => [
                'class' => TestWidgetBehavior::className()
            ],
        ]);
        $this->assertSame(0, TestWidget::$instanceCount);
    }
}

ActiveForm and ActiveField also composes a cycle reference, which causes memory leak even without any behavior attached to them.

Even though these will remain in memory for some time, they still should get collected once the GC is running, which will happen at some point in the execution when PHP hits a limit:
http://php.net/manual/en/features.gc.collecting-cycles.php

Only when the root buffer is full does the collection mechanism start for all the different zvals inside.

...

The root buffer has a fixed size of 10,000 possible roots (although you can alter this by changing the GC_ROOT_BUFFER_MAX_ENTRIES constant in Zend/zend_gc.c in the PHP source code, and re-compiling PHP).

So in case PHP needs more memory it will run the GC itself, imo there is no need to Yii to handle this.


Update README.md

Describe your changes
Issue ticket number and link
Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.
[ ] CHANGELOG.md has been updated should there be relevant changes in this PR

the DCO check is failing, I think that is due to the missing Signed off by... footer in the commit message

I'm afraid I'm closing this one in favor of #276 which is ready to go and fixes an additional typo. Thanks for the PR though @kshtsk .

also, in the future, please do not push branches to an organization repository unless there is a good reason to.

also, in the future, please do not push branches to an organization s3gw-related repository unless there is a good reason to.

Sorry about that, I've just pressed suggest a change in GitHub UI, and it is created a branch which I didn't realize, I guess I have to much permissions.

alright, no problem, just a note for the future :)


Update to spigot-1.17.jar: No JavaScript Engine available (mac)

I have recently upgdated to Spigot 1.17. Now if I try to run any javascript commands from within the game nothing happens, and I get this message from the server (the following is produced if I try to do 1+1, but the same happens for any ScriptCraft functions):
[14:51:17] [Server thread/INFO]: nsm99999 issued server command: /js 1+1
[14:51:17] [Server thread/ERROR]: [scriptcraft] No JavaScript Engine available. ScriptCraft will not work without Javascript.

I also had to update my version of java (on MacOS Big Sur) for the Spigot update, so that may be causing the problem. My version is:
$ java -version
openjdk version "16.0.1" 2021-04-20
OpenJDK Runtime Environment Homebrew (build 16.0.1+0)
OpenJDK 64-Bit Server VM Homebrew (build 16.0.1+0, mixed mode, sharing)

Any ideas?  I realise that this may not be a ScriptCraft problem, but I guess others on macs might experience it with the new Java update.
Thanks in advance! (And thanks for ScriptCraft, it's fantastic, my kids have just discovered the castle() method and are desperate to try it out)

Nashorn Engine is what ScriptCraft uses.
https://github.com/walterhiggins/ScriptCraft/blob/6f5771d4c842ea86143ae5d5c9e022292bcd0de6/src/docs/java/jscript.java#L10
As of Java 15, the Nashorn Engine was removed due to maintanence costs. Minecraft 1.17 depends on versions of Java 16 and newer.
https://openjdk.java.net/jeps/372
A possible solution is to use a standalone version of Nashhorn available at https://github.com/szegedi/nashorn

Thanks @AdrianHDev . Any pointers about how to make ScriptCraft aware of the standalone version of Nashorn? I have tried putting the Nashorn jar in the same directory as the spigot server, and starting with something like:
java -jar spigot.jar -cp nashorn-core-15.2.jar
but I get the same error about no JavaScript engine being available.

Hey! Sorry, that would be something @walterhiggins would have to implement.

Hey ScriptCrafters - I was able to get a working version with Java 16 using the Standalone Nashorn.  It's really messy (I don't do any Java development and so don't understand the toolchain).
The branch is here:  https://github.com/davidyang/Scriptcraft
It still works with ant (I added Ivy and changed the .classpath since I was using Eclipse to get autocomplete).
Would love to merge this into main and have a working Scriptcraft - this really is the best plugin for building in Minecraft that I've found.

@davidyang Your version thows me the following error:
Could not initialize class org.openjdk.nashorn.internal.runtime.Context$AnonymousContextCodeInstaller
Is there anything about the build/deploy process that I'm missing?

https://github.com/walterhiggins/ScriptCraft/issues/452
Someone has released a patched version for GraalVM (https://github.com/ediloren/ScriptCraft)
There is a re-compiled JAR file that should work.

https://github.com/walterhiggins/ScriptCraft/issues/452
Someone has released a patched version for GraalVM (https://github.com/ediloren/ScriptCraft)
Hopefully the re-compiled JAR will work for you


[Bug] <Changes aren't saving>

Is there an existing issue for this?

[X] Yes, I have searched the existing issues and none of them match my problem.

Product Variant
Cloud (http://rxresu.me)
Current Behavior
Changes made to resume aren't saving properly. When I return to the site the changes aren't staying but rather reverting to the previous changes.
Expected Behavior
For the resume to be saved in the edited state
Steps To Reproduce
No response
What browsers are you seeing the problem on?
Firefox
What template are you using?
Azurill
Anything else?
No response

I'm experiencing the same bug.

I'm experiencing the same bug. Is it possible that I have two resume pages open at the same time causing the bug?

I'm only using a single page, on my resume

I just had the same issue.
Fill in all details I needed, checked - everything was fine.
Next morning see that resume roll back to some older stage.
The most weird thing there, is that I tried to download via download button under resume preview - it showed current outdated resume, then tried to download via download button from right sidebar - and it downloaded the expected filled in resume!🤯 But second try downloaded the current outdated version.
Do you believe in magic?😅


Fix document about importing library in Swift

To import EarlGrey library in Swift, #import <EarlGrey/EarlGrey.h> should be written in test bundle's bridging header.

Thanks for this, @dreamagicjp


Add SFP module details to interface details

I noticed that the interface details link (clicking on the magnifying glass on an interface in the Interfaces > Overview page) wasn't showing some of the information about the SFP transceivers I have plugged in to those ports.  It turns out that OPNsense is already grabbing that data (it's retrieved via ifconfig -v), but it just isn't parsing it when it's available.
So, this adds a few entries to the interface info in order to display those things.  In my case, these look like this:

field_name
field_value

sfp_transceiver_plugged
SFP/SFP+/SFP28 Unknown (RJ45)

sfp_transceiver_vendor
FS

sfp_transceiver_part_number
SFP-10GM-T

sfp_transceiver_serial_number
SOMESERIALNUMBER

sfp_transceiver_manufacturing_date
2000-01-31

In theory, there are also other things that could show up like module temperature or TX/RX strength (https://forums.freebsd.org/threads/network-card-sfp-module-status.68666/ has an example of this), but my modules don't report those, so I left them out since I wouldn't have a way of testing them.

This was still on my todo list after @swhite2 added the info in our axgbe driver.  Let me rearrange this a bit and add it to master.

@Kreeblah can you double check https://github.com/opnsense/core/commit/cca972c05b22a28e2b076a4297cbe139ae7519af on your end? Thanks!

Yep, that commit looks like it's working for me.  I'm seeing a row labeled sfp with the parsed data as columns in it.  Thanks!

@Kreeblah thank you for working on it


Auto Proxy Feature

I'm not sure how robust or usable this will be, but this is a functional auto proxy feature.
use -tul!auto after a [proxied] message to start auto proxy.
use tul!clearauto to clear the proxy
or use -tul!auto after a non-proxied message to end auto proxy

Based on some feedback:
tul!auto TULPAHERE sets up your auto message
tul!auto _____ (nothing) clears your auto
autoclear is removed.
changing the "tul!" prefix is supported as well as the "tupper" changes.

Hi! Thank you for the PR.
There's a few things which I've noted in the comments; other than that, please remove the console.logs in auto.js (and elsewhere, if I've missed any).
Other than that, here's a couple thoughts:

Being able to start autoproxying by adding some text to a message that's already about to be proxied is an interesting idea - but I'm not sure if this is exactly the way we want to go about it. We'll talk about it within the dev team.

 Consider adding something like Pluralkit's \ escaping, or something else to the same effect.

Having to call a database delete and set to change the current auto tupper seems a little inefficient. Could you see if it's possible to move that to a single database call somehow?

Most of what you mentioned should be fixed, minus where I left comments explaining what was going on.
",," at the beginning of a message should escape now.  I considered \ and --, but I pulled up my phone and ",," is very easy to type in both on phones and on the keyboard, is pretty low profile, so I used that instead.
I wasn't able to find a super elegant way to handle the delete/insert process.  I moved the code into "setAuto" instead of "addAuto" so it's only one function call. I used the "DB" connection pool so it isn't opening a new connection in order to run the two queries, which should be reasonably quick.  I tried making it one string but postgres complained.
There may be something you can do with INSERT ON CONFLICT, but I'm not too familiar with postgres and didn't want to mess with it too much.

Personally I'd still go for \ as the autoproxy escape character, both for ease of use between bots (as that's PK's) and because ,, is more likely to be used as a proxy. We shall know people, some in our system even, who use commas like periods in certain cases, so starting a message with ,,, wouldn't be unlikely- doing that and not having it proxy would seem strange.
That said, would you be opposed to adding something like PK's latch mode? From what we can tell it's the most used setting on that bot. You could use tul!auto latch to turn it on, and from there anytime another tupper is proxied you would automatically change the auto'd member. It works similar to your idea of appending -auto to a message, but would be a lot cleaner and simpler imho.

Is there some sort of character combination typed without a "shift/modifier" on a phone keyboard that would be good but also wouldn't be likely to interfere?  Changing what it is is super easy, so the tupperware people can easily pick/set whatever they like, but maybe ".,." or something like that would work better?
If it's set as a bracket it will use the bracket before it'll use the escape. Maybe there needs to be two escapes?
I think the only way for me to add a latch would be to add another database table and save to it as well.  If the tupperware people are alright with doing that (or if there's another better storage place for this stuff) I can try to add that in as well.

Well, you've already got the automatic table- why not just add another column called type or latch and query that to tell whether the user has latch mode on or not?
Also for us the backslash is as easy to get to as tapping and holding on a certain letter or tapping a couple other keys (which we often use for other punctuation, eg backticks). Obviously it depends on the keyboard, but I'm not sure that using a backslash as the escape character would be more difficult for most people than, say, typing another proxy- even if there's a modifier key involved. There's also the fact that typing ,, or ,., is two to three characters vs \ being one. If you really wanted to though you could probably add an escape_chars column to the automatic table and let users set a custom escape sequence with tul!escape or something similar.

The main reason for not putting it in the automatic table is that a record only exists out there when a user is currently auto proxying.  I could add a latch field on there, but I'd need to also make that member field able to be null so it can do double duty.  Totally possible, but a bit hacky.
I will try to do that and will also look at making the escape character a config setting.
I 100% can't put it into the auto table due to the auto table not being a long term storage area.  There is a setting tupperware already has that's similar in the member table, and an "auto-escape" setting could be added there, but I will avoid touching the existing stuff unless the tupperware dev team is alright with the idea of doing that.

If it helps any, we're part of the dev team. Got the dev role and everything on top of being mods in the support server lol
That being said, I don't see an issue with storing all the autoproxy data in the same table, especially if you're going to be querying it with (almost) every message sent. That way there everything's kept together. I also don't see an issue with setting the autoproxy member to null if you go that route- it's not really hacky, it's just a different way to handle storage. That would also make it easier to do things like set a no member latch option like \\ (a very common request with PK), where you can effectively turn off autoproxying for multiple messages (aka, set the member to null) while still automatically re-latching when brackets are used again.

Alright, this commit should do as you were recommending and adds is_sticky to the auto table (you'll have to delete the table if you already had it running).  It still uses ,, as the escape (easy to change, feel free to change it), but now
tul!auto -sticky
will set sticky mode where your next proxy turns into your auto
then an escaped message ,,blah will reset your auto to null and let you type normally again.
Sorry I didn't recognize you there as a dev.  I looked in your history to see and assumed you weren't "in the team."

Someone mentioned in another server abandoning -sticky and just having it always be "sticky".  I'm not sure if that is a good idea or not, but if you all want that I can make it work that way.

GitHub on desktop should mark us as contributors, but no worries pff
Another way you could do that is tul!auto and tul!auto [name], with tul!auto clear turning AP off. This would be more consistent with existing commands like tul!describe, where you have to add clear on the end to clear it.

TIL.
I guess the only issue there would be if a person wants to "be X" in chat and be able to "talk as Y" without ruining the fact that they "are" X.
tul!auto could be "sticky" with no ability to start as a name
tul!auto name could be "not sticky" and start you with a name
then tul!auto clear could reset everything?
Would having a member named "clear" cause any issues there?
Maybe tul!clear if nothing is planned for that command already, if not tul!autoclear instead?

Yeah, that would be an issue. I know that setting autoproxy using a name with PK still allows one-off messages through other system members without latching onto them, so the way you wrote it there seems best
As for the last bit, you could add off and disable as aliases for clear, then systems would have more options and shouldn't have to worry as much about it. If you do go that route then I'd check tupper names before handling the off/clear flag, to make things easier

This now works as described
tul!auto turns on sticky mode with no default tupper.
tul!auto name turns on non-sticky mode with the given name.
tul!clear/off/disable clears everything

Hey hey, I'm not really satisfied with your implementation of the escaping character for two reasons:

It's not standard: pluralkit already has a reasonable escape character, and using a different one will just confuse users moving from one bot to the other.
It fully disables autoproxy, so a user would have to re-enable it to send a new message. I'd like to see a way to send a single non-proxied message while still having autoproxy enabled.

I can change it to a \ if need be, it's set as a string that can be changed to whatever you want.
It shouldn't fully disable auto proxy.  If it's set to "sticky" then the escape will "stick" just like any other proxy, but if you're not in sticky mode it won't turn off.... or I didn't think it would?

Had to use -\ instead of \ because \ turns to \ in discord markup.

The markup change is client side; it should still be detected through the bot as a double backslash, if that helps

You are correct, it was another bug causing the issue.  Fixed and should be working with \ and \\ now.

Hey hey, sorry this is late. I appreciate your contributions to the project. This PR has a lot of conflicts now and we didn't seem to reach a consensus on the implementation here. In particular I don't think I agree with the database implementation - there can only ever be one row per tupper in the auto table, it might as well be a column in the tupper table to avoid needing additional joins or separate additional db requests. The thing that interests me is having special syntax to enable/disable autoproxy when proxying normally, but I think at this point I'd rather re-implement this separately instead of resolve the conflicts and style issues here. So I'm closing this now, but I do appreciate the efforts.


Pilot broken after update to spaceship 0.38.2

New Issue Checklist

[X] Updated fastlane to the latest version
[X] I have read the Contribution Guidelines

Issue Description
Complete output when running fastlane, including the stack trace and command used

You can use: --capture_output as the last commandline argument to get that collected for you

pilot --help
/usr/local/Cellar/ruby/2.3.1_2/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- unicode (LoadError)
	from /usr/local/Cellar/ruby/2.3.1_2/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/local/lib/ruby/gems/2.3.0/gems/babosa-1.0.2/lib/babosa/utf8/unicode_proxy.rb:1:in `<top (required)>'
	from /usr/local/Cellar/ruby/2.3.1_2/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/local/Cellar/ruby/2.3.1_2/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/local/lib/ruby/gems/2.3.0/gems/babosa-1.0.2/lib/babosa/identifier.rb:41:in `<class:Identifier>'
	from /usr/local/lib/ruby/gems/2.3.0/gems/babosa-1.0.2/lib/babosa/identifier.rb:31:in `<module:Babosa>'
	from /usr/local/lib/ruby/gems/2.3.0/gems/babosa-1.0.2/lib/babosa/identifier.rb:2:in `<top (required)>'
	from /usr/local/Cellar/ruby/2.3.1_2/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/local/Cellar/ruby/2.3.1_2/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/local/lib/ruby/gems/2.3.0/gems/babosa-1.0.2/lib/babosa.rb:16:in `<top (required)>'
	from /usr/local/Cellar/ruby/2.3.1_2/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/local/Cellar/ruby/2.3.1_2/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/local/lib/ruby/gems/2.3.0/gems/spaceship-0.38.2/lib/spaceship/client.rb:9:in `<top (required)>'
	from /usr/local/Cellar/ruby/2.3.1_2/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/local/Cellar/ruby/2.3.1_2/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/local/lib/ruby/gems/2.3.0/gems/spaceship-0.38.2/lib/spaceship.rb:3:in `<top (required)>'
	from /usr/local/Cellar/ruby/2.3.1_2/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/local/Cellar/ruby/2.3.1_2/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/local/lib/ruby/gems/2.3.0/gems/pilot-1.12.1/lib/pilot.rb:14:in `<top (required)>'
	from /usr/local/Cellar/ruby/2.3.1_2/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:68:in `require'
	from /usr/local/Cellar/ruby/2.3.1_2/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:68:in `require'
	from /usr/local/lib/ruby/gems/2.3.0/gems/pilot-1.12.1/bin/pilot:4:in `<top (required)>'
	from /usr/local/bin/pilot:23:in `load'
	from /usr/local/bin/pilot:23:in `<main>'

Environment
Please run fastlane env and copy the output below. This will help us help you :+1:
If you used --capture_output option please remove this block - as it is already included there.
✅ fastlane environment ✅
Stack

Key
Value

OS
10.11.6

Ruby
2.3.1

Bundler?
false

Git
git version 2.9.3 (Apple Git-75)

Installation Source
/usr/local/bin/fastlane

Host
Mac OS X 10.11.6 (15G1108)

Ruby Lib Dir
/usr/local/Cellar/ruby/2.3.1_2/lib

OpenSSL Version
OpenSSL 1.0.2j  26 Sep 2016

Is contained
false

Xcode Path
/Applications/Xcode-8.1.app/Contents/Developer/

Xcode Version
8.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE

fastlane files:
No Fastfile found
No Appfile found
fastlane gems

Gem
Version
Update-Status

credentials_manager
0.16.2
✅ Up-To-Date

fastlane_core
0.57.1
✅ Up-To-Date

deliver
1.16.0
✅ Up-To-Date

snapshot
1.16.4
✅ Up-To-Date

frameit
3.0.0
✅ Up-To-Date

pem
1.4.0
✅ Up-To-Date

cert
1.4.4
✅ Up-To-Date

produce
1.3.1
✅ Up-To-Date

pilot
1.12.1
✅ Up-To-Date

scan
0.14.2
✅ Up-To-Date

supply
0.8.0
✅ Up-To-Date

match
0.11.0
✅ Up-To-Date

screengrab
0.5.6
✅ Up-To-Date

fastlane
1.110.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.0.0

highline
1.7.8

commander
4.4.0

terminal-table
1.4.5

json
1.8.3

multipart-post
2.0.0

faraday
0.9.2

faraday_middleware
0.10.0

dotenv
2.1.1

net-ssh
3.2.0

net-sftp
2.1.2

plist
3.2.0

rubyzip
1.1.7

security
0.1.3

krausefx-shenzhen
0.14.11

slack-notifier
1.5.1

i18n
0.7.0

thread_safe
0.3.5

tzinfo
1.2.2

minitest
5.8.3

activesupport
<IP_ADDRESS>

CFPropertyList
2.3.4

claide
1.0.1

colored
1.2

nanaimo
0.2.2

xcodeproj
1.4.1

rouge
1.11.1

xcpretty
0.2.4

terminal-notifier
1.7.1

addressable
2.3.8

xcode-install
2.0.9

word_wrap
1.0.0

bundler
1.13.6

credentials_manager
0.16.2

multi_json
1.12.1

babosa
1.0.2

excon
0.54.0

gh_inspector
1.0.2

fastlane_core
0.57.1

fastimage
1.6.8

mini_magick
4.5.1

xcpretty-travis-formatter
0.0.4

uber
0.0.15

representable
2.3.0

retriable
2.1.0

mime-types-data
3.2016.0521

mime-types
3.1

hurley
0.2

little-plugger
1.1.4

logging
2.1.0

jwt
1.5.6

memoist
0.15.0

os
0.9.6

signet
0.7.3

googleauth
0.5.1

httpclient
<IP_ADDRESS>

google-api-client
0.9.20

io-console
0.4.5

generated on: 2016-11-29

$ gem list spaceship
*** LOCAL GEMS ***
spaceship (0.38.2, 0.38.1, 0.38.0, 0.37.0, 0.36.2, 0.36.0)

$ gem uninstall spaceship -v 0.38.2
Successfully uninstalled spaceship-0.38.2

$ pilot --help
---------------------------------------------
-------------------WARNING-------------------
---------------------------------------------
You're using an old version of spaceship
To ensure spaceship and fastlane works
update to the latest version.

Run `[sudo] gem update spaceship`

or `bundle update` if you use bundler.

You're on spaceship version: 0.38.1
Latest spaceship version  : 0.38.2

  pilot

  The best way to manage your TestFlight testers and builds from your terminal

  Commands:
    add        Adds new external tester(s) to a specific app (if given). This will also add an existing tester to an app.
    builds     Lists all builds for given application
    distribute Distribute a previously uploaded binary to Apple TestFlight
    export     Exports all external testers to a CSV file
    find       Find tester(s) (internal or external) by their email address
    help       Display global or [command] help documentation
    import     Create external testers from a CSV file
    list       Lists all registered testers, both internal and external
    remove     Remove external tester(s) by their email address
    upload     Uploads a new binary to Apple TestFlight

  Global Options:
    -u, --username STRING Your Apple ID Username (PILOT_USERNAME)
    -a, --app_identifier STRING The bundle identifier of the app to upload or manage testers (optional) (PILOT_APP_IDENTIFIER)
    -i, --ipa STRING     Path to the ipa file to upload (PILOT_IPA)
    -w, --changelog STRING Provide the what's new text when uploading a new build (PILOT_CHANGELOG)
    -d, --beta_app_description STRING Provide the beta app description when uploading a new build (PILOT_BETA_APP_DESCRIPTION)
    -n, --beta_app_feedback_email STRING Provide the beta app email when uploading a new build (PILOT_BETA_APP_FEEDBACK)
    -s, --skip_submission [VALUE] Skip the distributing action of pilot and only upload the ipa file (PILOT_SKIP_SUBMISSION)
(...)

Possibly related to https://github.com/fastlane/fastlane/pull/7210

The fix is to install the unicode gem (need to update pilot/spaceship? dependencies):
$ gem install unicode
Fetching: unicode-<IP_ADDRESS>.gem (100%)
Building native extensions.  This could take a while...
Successfully installed unicode-<IP_ADDRESS>
1 gem installed

$ gem update spaceship
Updating installed gems
Updating spaceship
Fetching: spaceship-0.38.2.gem (100%)
Successfully installed spaceship-0.38.2
Gems updated: spaceship

$ pilot --help
  pilot

  The best way to manage your TestFlight testers and builds from your terminal

  Commands:
    add        Adds new external tester(s) to a specific app (if given). This will also add an existing tester to an app.
    builds     Lists all builds for given application
    distribute Distribute a previously uploaded binary to Apple TestFlight
    export     Exports all external testers to a CSV file
    find       Find tester(s) (internal or external) by their email address
    help       Display global or [command] help documentation
    import     Create external testers from a CSV file
    list       Lists all registered testers, both internal and external
    remove     Remove external tester(s) by their email address
    upload     Uploads a new binary to Apple TestFlight

  Global Options:
    -u, --username STRING Your Apple ID Username (PILOT_USERNAME)
    -a, --app_identifier STRING The bundle identifier of the app to upload or manage testers (optional) (PILOT_APP_IDENTIFIER)
    -i, --ipa STRING     Path to the ipa file to upload (PILOT_IPA)
    -w, --changelog STRING Provide the what's new text when uploading a new build (PILOT_CHANGELOG)
    -d, --beta_app_description STRING Provide the beta app description when uploading a new build (PILOT_BETA_APP_DESCRIPTION)
    -n, --beta_app_feedback_email STRING Provide the beta app email when uploading a new build (PILOT_BETA_APP_FEEDBACK)
    -s, --skip_submission [VALUE] Skip the distributing action of pilot and only upload the ipa file (PILOT_SKIP_SUBMISSION)

babosa was introduced as dep. which in some cases requires unicode gem, and babosa did not specify it in gemspec. pr is out to add it to spaceship #7231

Thanks for the quick heads up! We're going to roll this change back and make a new release. Apologies for the trouble!

spaceship 0.38.3

Confirmed with 0.38.4:
$ gem uninstall unicode
Successfully uninstalled unicode-<IP_ADDRESS>

$ pilot --help
/usr/local/Cellar/ruby/2.3.1_2/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:120:in `require': cannot load such file -- unicode (LoadError)
	from /usr/local/Cellar/ruby/2.3.1_2/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:120:in `require'
	from /usr/local/lib/ruby/gems/2.3.0/gems/babosa-1.0.2/lib/babosa/utf8/unicode_proxy.rb:1:in `<top (required)>'
	from /usr/local/Cellar/ruby/2.3.1_2/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:68:in `require'
	from /usr/local/Cellar/ruby/2.3.1_2/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:68:in `require'
	from /usr/local/lib/ruby/gems/2.3.0/gems/babosa-1.0.2/lib/babosa/identifier.rb:41:in `<class:Identifier>'
	from /usr/local/lib/ruby/gems/2.3.0/gems/babosa-1.0.2/lib/babosa/identifier.rb:31:in `<module:Babosa>'
	from /usr/local/lib/ruby/gems/2.3.0/gems/babosa-1.0.2/lib/babosa/identifier.rb:2:in `<top (required)>'
	from /usr/local/Cellar/ruby/2.3.1_2/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:68:in `require'
	from /usr/local/Cellar/ruby/2.3.1_2/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:68:in `require'
	from /usr/local/lib/ruby/gems/2.3.0/gems/babosa-1.0.2/lib/babosa.rb:16:in `<top (required)>'
	from /usr/local/Cellar/ruby/2.3.1_2/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:68:in `require'
	from /usr/local/Cellar/ruby/2.3.1_2/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:68:in `require'
	from /usr/local/lib/ruby/gems/2.3.0/gems/spaceship-0.38.2/lib/spaceship/client.rb:9:in `<top (required)>'
	from /usr/local/Cellar/ruby/2.3.1_2/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:68:in `require'
	from /usr/local/Cellar/ruby/2.3.1_2/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:68:in `require'
	from /usr/local/lib/ruby/gems/2.3.0/gems/spaceship-0.38.2/lib/spaceship.rb:3:in `<top (required)>'
	from /usr/local/Cellar/ruby/2.3.1_2/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:68:in `require'
	from /usr/local/Cellar/ruby/2.3.1_2/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:68:in `require'
	from /usr/local/lib/ruby/gems/2.3.0/gems/pilot-1.12.1/lib/pilot.rb:14:in `<top (required)>'
	from /usr/local/Cellar/ruby/2.3.1_2/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:68:in `require'
	from /usr/local/Cellar/ruby/2.3.1_2/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:68:in `require'
	from /usr/local/lib/ruby/gems/2.3.0/gems/pilot-1.12.1/bin/pilot:4:in `<top (required)>'
	from /usr/local/bin/pilot:23:in `load'
	from /usr/local/bin/pilot:23:in `<main>'

$ gem update spaceship
Updating installed gems
Updating spaceship
Fetching: spaceship-0.38.4.gem (100%)
Successfully installed spaceship-0.38.4
Gems updated: spaceship
zergling:~ zergling$ pilot --help
  pilot

  The best way to manage your TestFlight testers and builds from your terminal

  Commands:
    add        Adds new external tester(s) to a specific app (if given). This will also add an existing tester to
an app.
    builds     Lists all builds for given application
    distribute Distribute a previously uploaded binary to Apple TestFlight
    export     Exports all external testers to a CSV file
    find       Find tester(s) (internal or external) by their email address
    help       Display global or [command] help documentation
    import     Create external testers from a CSV file
    list       Lists all registered testers, both internal and external
    remove     Remove external tester(s) by their email address
    upload     Uploads a new binary to Apple TestFlight

  Global Options:
    -u, --username STRING Your Apple ID Username (PILOT_USERNAME)
    -a, --app_identifier STRING The bundle identifier of the app to upload or manage testers (optional)
(PILOT_APP_IDENTIFIER)
    -i, --ipa STRING     Path to the ipa file to upload (PILOT_IPA)
    -w, --changelog STRING Provide the what's new text when uploading a new build (PILOT_CHANGELOG)
    -d, --beta_app_description STRING Provide the beta app description when uploading a new build
(...)

Thanks @lkraider 🎉


Allow configuration of (some) WebSocket protocol options from server CLI

There are a lot of knobs on a WebSocket server that can be turned to various effect.
For example, Autobahn WebSockets have an "auto ping" feature which can be used as a connection keep-alive feature.
These knobs seem to be controlled by a setProtocolOptions method on the factory.

https://autobahn.readthedocs.io/en/latest/websocket/programming.html#websocket-options

Sounds good.. I'll land the related patch. I'd like to treat this as temporary, though. In the longer run (after the server is split out into a separate package, and some other cleanups happen), we should remove the argv controls in favor of a config file.

Just as a potential discussion point ... Command line args and environment variables have ended up the least-effort way to control software that gets put into Docker containers because it's typically trivial to control those two inputs to a process.  Making a configuration file available requires a lot more effort - either creating the file and providing it as host-mount (or possibly other kind of) volume or building a wrapper around the entrypoint that itself knows about argv or env and generates a configuration file on the fly.


stuck at InterruptVectorDefault example blink

Hi , i have success flash ch32v003 sop16 with example blink provided in this repository with load command
but when i try to debug it still stuck in
InterruptVectorDefault () at ch32v003fun.c:738
738             asm volatile( "\n\

when i command next no response then Remote connection closed , when remote reset it still in the InterruptVectorDefault () at ch32v003fun.c:738
what cause this ?

Case is closed , I must use newer gnu risc-v to be able to debug


Fix manual targets sync for target explicitly specified

Checklist

[x] I have filed an issue about this change and discussed potential changes with the maintainers.
[x] I have received the approval from the maintainers to make this change.
[x] This is not a stylistic, refactoring, or cleanup change.

This PR is a continuation of https://github.com/bazelbuild/intellij/issues/4546. One issue is that for manual targets specified, they are also excluded without this change (see https://github.com/bazelbuild/intellij/issues/4546#issuecomment-1741969833).
This fix will only work currently if the shard_sync: true. Otherwise the query will not be performed.  Otherwise, two flags must be set for this part to work.
Issue number: https://github.com/bazelbuild/intellij/issues/4546
Description of this change
When allow_manual_targets_sync: true is set, this change will allow manual targets to be part of the target query. Because expansion of build targets currently only occur when the sharding approach is enabled, this change would also switch on the shard_sync: true option to enable this query to occur. The alternative would be to create another option to expand the query, so I wanted to get feedback about it.
I've also modified unit tests to perform the check for both on/off, asserting the presence of the manual attr query.

@rogerhu @tpasternak Can we have this documented somewhere next to https://ij.bazel.build/docs/project-views.html#derive_targets_from_directories ? I've sharing the issue for this PR but I think docs supposed to reflect such properties.

Yep! I have to file a ticket apparently since the Bazel IntelliJ docs are not open source. =)
https://bazelbuild.slack.com/archives/C025SBYFC4E/p1697741079375969

Created a ticket here: https://github.com/bazelbuild/intellij/issues/5590


The package does not run in php 7.3~

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

We will consider it later.


Discord message, user, client classes are stinky

Something should be done about them, because they are not as nice as they should be.
They don't store all the information that they need, and also, from_response methods are lacking in functionality.
todo: basically rewrite that part and rewrite the client too, make it more modular, and bring the user command processing somewhere else

Being dealt with in client-rewrite branch


import 'vanilla-js-calendar'

import 'vanilla-js-calendar' imports and empty object.

I'm having the same problem, I use webpack and I've tried every combination of import and require.


python311Packages.treq: 22.2.0 -> 23.11.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.treq is: Requests-like API built on top of twisted.web's Agent
meta.homepage for python311Packages.treq is: https://github.com/twisted/treq
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 23.11.0 with grep in /nix/store/xcccq98kxz8s1karyp2bid8prymd030k-python3.11-treq-23.11.0
found 23.11.0 in filename of file in /nix/store/xcccq98kxz8s1karyp2bid8prymd030k-python3.11-treq-23.11.0

Rebuild report (if merged into master) (click to expand)

21 total rebuild path(s)

21 package rebuild(s)

First fifty rebuilds by attrpath
buildbot
buildbot-full
buildbot-plugins.badges
buildbot-ui
gnome-keysign
magic-wormhole
matrix-synapse
matrix-synapse-plugins.matrix-synapse-ldap3
matrix-synapse-plugins.matrix-synapse-mjolnir-antispam
matrix-synapse-plugins.matrix-synapse-s3-storage-provider
matrix-synapse-plugins.matrix-synapse-shared-secret-auth
matrix-synapse-unwrapped
python310Packages.klein
python310Packages.magic-wormhole
python310Packages.magic-wormhole-mailbox-server
python310Packages.treq
python311Packages.klein
python311Packages.magic-wormhole
python311Packages.magic-wormhole-mailbox-server
python311Packages.treq
tahoe-lafs

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/xcccq98kxz8s1karyp2bid8prymd030k-python3.11-treq-23.11.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.treq https://github.com/r-ryantm/nixpkgs/archive/bd67762ed1a91e25dd017849ef452327e1f7f4e9.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/bd67762ed1a91e25dd017849ef452327e1f7f4e9#python311Packages.treq

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/xcccq98kxz8s1karyp2bid8prymd030k-python3.11-treq-23.11.0
ls -la /nix/store/xcccq98kxz8s1karyp2bid8prymd030k-python3.11-treq-23.11.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

20 packages built:

buildbot
buildbot-full
buildbot-plugins.badges
buildbot-ui
gnome-keysign
magic-wormhole (python311Packages.magic-wormhole)
matrix-synapse
matrix-synapse-plugins.matrix-synapse-ldap3
matrix-synapse-plugins.matrix-synapse-mjolnir-antispam
matrix-synapse-plugins.matrix-synapse-s3-storage-provider
matrix-synapse-plugins.matrix-synapse-shared-secret-auth
matrix-synapse-unwrapped
python310Packages.klein
python310Packages.magic-wormhole
python310Packages.magic-wormhole-mailbox-server
python310Packages.treq
python311Packages.klein
python311Packages.magic-wormhole-mailbox-server
python311Packages.treq
tahoe-lafs

Maintainer pings

Merge conflict, please open a new PR.


does not support ios 12

Thanks for the great library. I checked that this lib is set with IPHONEOS_DEPLOYMENT_TARGET = 8.0; but when I try using iOS 12, the protection is not working at all. I use these functions
CaptureProtection.preventScreenshot();
CaptureProtection.preventScreenRecord();

@HanggiAnggono hi, thx for report this. can you share react-native version?

@HanggiAnggono hi, thx for report this. can you share react-native version?

im using version 0.66.5 as of now

@HanggiAnggono thx. i will try iOS 12 for check for it asap

@HanggiAnggono thx. i will try iOS 12 for check for it asap

thank you, really appreciate it

import { useFocusEffect } from "@react-navigation/native";
import { useCallback, useState } from "react";
import {
  CaptureProtection,
  CaptureProtectionModuleStatus,
} from "react-native-capture-protection";

export const useScreenRecordDetect = ({ enabled }: { enabled: boolean }) => {
  const [isRecording, setIsRecording] = useState(false);

  async function protectScreen() {
    CaptureProtection.preventScreenshot();
    CaptureProtection.preventScreenRecord();
    CaptureProtection.addEventListener(({ status }) => {
      if (status === CaptureProtectionModuleStatus.RECORD_DETECTED_START) {
        setIsRecording(true);
      }
    });
  }

  function releaseProtection() {
    CaptureProtection.allowScreenshot();
    CaptureProtection.allowScreenRecord();
    setIsRecording(false);
  }

  useFocusEffect(
    useCallback(() => {
      if (enabled) {
        protectScreen();
      } else {
        releaseProtection();
      }

      return () => {
        releaseProtection();
      };
    }, [enabled]),
  );

  return { isRecording };
};

useScreenRecordDetect({enabled: true});

That's how I use the library. I don't quite understand what do you mean by modal

@HanggiAnggono hello I've been testing with iOS 12 and RN 0.66 and it seems to be working fine. Can you tell me how you are using the function? Is it possible that the modal is popping up after the function is called? If use like this case, possibility it's not work, but i will fix this in the future.

import { useFocusEffect } from "@react-navigation/native";
import { useCallback, useState } from "react";
import {
  CaptureProtection,
  CaptureProtectionModuleStatus,
} from "react-native-capture-protection";

export const useScreenRecordDetect = ({ enabled }: { enabled: boolean }) => {
  const [isRecording, setIsRecording] = useState(false);

  async function protectScreen() {
    CaptureProtection.preventScreenshot();
    CaptureProtection.preventScreenRecord();
    CaptureProtection.addEventListener(({ status }) => {
      if (status === CaptureProtectionModuleStatus.RECORD_DETECTED_START) {
        setIsRecording(true);
      }
    });
  }

  function releaseProtection() {
    CaptureProtection.allowScreenshot();
    CaptureProtection.allowScreenRecord();
    setIsRecording(false);
  }

  useFocusEffect(
    useCallback(() => {
      if (enabled) {
        protectScreen();
      } else {
        releaseProtection();
      }

      return () => {
        releaseProtection();
      };
    }, [enabled]),
  );

  return { isRecording };
};

useScreenRecordDetect({enabled: true});

That's how I use the library. I don't quite understand what do you mean by modal

@HanggiAnggono hello sir
As you reported, i have confirmed that it does not work on iOS 12 or earlier.
i try to fix that quickly
In the meantime, we recommend using it on iOS 13 or later.
sorry that this happened to you

@HanggiAnggono hello sir
As you reported, i have confirmed that it does not work on iOS 12 or earlier. i try to fix that quickly In the meantime, we recommend using it on iOS 13 or later.
sorry that this happened to you

thank you for the confirmation sir


Add design page on dev mode

The purpose of this PR is to create a page that consolidates all existing UI components.

Looks like there is an import issue

Good to me!


add -M to amixer to fix volume mapping issues #117

Change-type: patch
Details of this are in the following issue comment.
https://github.com/balenalabs/balena-sound/issues/117#issuecomment-609097464

@balena-ci retest

@MatthewCroughan seems like something is here wrong can you try please to run the following commands?

Run git clone https://github.com/MatthewCroughan/balena-sound.git --single-branch --branch MatthewCroughan:fix-amixer-volume-#117
Run: cd balena-sound
Run: git reset HEAD~3
Run: git add .

Run: git push -f https://github.com/MatthewCroughan/balena-sound.git MatthewCroughan:fix-amixer-volume-#117

@tmigone does this PR fix your issue?

I've done as you requested, though I don't actually understand what the problem is, so I'm running blind.

@balena-ci retest

@MatthewCroughan the PR checks are failing. I dont know why.

I was thinking there'd be a problem with running HEAD~3 since that puts me a few commits before, so I'll be overwriting previous work. But it is what you have requested, so I have done it.

@MatthewCroughan seems like something is here wrong can you try please to run the following commands?

Run git clone https://github.com/MatthewCroughan/balena-sound.git --single-branch --branch fix-amixer-volume-#117
Run: cd balena-sound
Run: git reset HEAD~1
Run: git add .
Run: git commit --amend
The file should be saved like this:

add -M to amixer to fix volume mapping issues #117
Change-type: patch

Run: git push -f https://github.com/MatthewCroughan/balena-sound.git fix-amixer-volume-#117

@balena-ci retest

@balena-ci retest

@balena-ci retest

@MatthewCroughan sorry, but i have no idea what is causing the failure here. @chrisys can you help here?

@MatthewCroughan can you try this again?

Run git clone https://github.com/MatthewCroughan/balena-sound.git --single-branch --branch fix-amixer-volume-#117
Run: cd balena-sound
Run: git reset HEAD~1
Run: git add .
Run: git commit --amend
The file should be saved like this:

add -M to amixer to fix volume mapping issues #117
Change-type: patch

Run: git push -f https://github.com/MatthewCroughan/balena-sound.git fix-amixer-volume-#117

@balena-ci retest

@MatthewCroughan sorry. It must be annoying for you, but can you do this comment again and the n not update your branch.

@balena-ci retest

@AlexProgrammerDE What I'm more annoyed about is that the commit no longer includes my actual changes, but includes changes from other people. I'm really confused about this. Have we not just defeated the purpose of git by including so many commits from other people? It's interesting to see CI cause so much trouble for such a simple change, without any feedback as to why it's happening.

@balena-ci retest

Any feedback?

@MatthewCroughan i am confused like you. @tmigone can you please help us?

Hey @MatthewCroughan, @AlexProgrammerDE, taking a look at this.
Our CI indeed is not very clear in communicating errors when something does not go as required, specially if you don't have access to the CI server to check the logs. Your point on lack of feedback being frustrating is super valid, we've been working on internally on improving this, thank you for letting us know. Also, we are in the process of revamping the contributing docs so that should improve too.
On to the problem here, I don't fully understand how the PR got into the state it's in, must be a combination of force pushes from both of you? My suggestion is that we take the lazy way out here, create a new PR and close this one. That would ensure a clean state and that commits are attributed to their authors too. Otherwise we could spend more time than what it's worth it. Let me know if this works for you and if you have any other questions! Thanks again for the contribution!
Here is how your commits should look like generally:
single line commit title, MANDATORY, usually "module: change explanation"

detailed description (OPTIONAL, can be multi line)

Change-type: major | minor | patch (MANDATORY, at least once in all of your PR commits)
Signed-off-by: Tomás Migone<EMAIL_ADDRESS>(OPTIONAL)

Note that new lines and order of elements ARE important. Change-type for instance requires a new line on top of it.
Looks like this if running git log:
commit 3e3a65eeb91abf0cd730e7899978a86eaec23d87
Author: Tomás Migone<EMAIL_ADDRESS>Date:   Fri Jan 10 09:57:17 2020 -0300

    multi-room: Add multi-room feature

    This feature adds multi-room audio streaming to balenaSound.
    No breaking changes were made, but considering this a major version bump since it's a big feature and all services were affected.

    New services added:
    - snapcast-server
    - snapcast-client
    - fleet-supervisor

    - By default, all audio services now stream to a fifo pipe file instead of alsa backend.
    - Multi-room can be disabled via env var DISABLE_MULTI_ROOM.

    Change-type: major
    Signed-off-by: Tomás Migone<EMAIL_ADDRESS>


Improve error message for non-constructable target for 'new'

Current behavior:
((o) Duktape [linenoise] 1.99.99 (v1.5.0-37-gf2be963)
duk> x = new undefined()
TypeError: not constructable
    at [anon] (duk_api_call.c:407) internal
    at global (input:1) preventsyield

Improve error message to e.g.
TypeError: undefined not constructable

New behavior with verbose, non-paranoid messages (default):
duk> new 123()
TypeError: 123 not constructable
    at [anon] (duk_api_call.c:411) internal
    at global (input:1) preventsyield

With verbose, paranoid messages:
duk> new 123()
TypeError: number not constructable
    at [anon] (duk_api_call.c:409) internal
    at global (input:1) preventsyield

With non-verbose messages (very low memory targets):
duk> new 123()
TypeError: 105
    at global (input:1) preventsyield

I like these small error message tweaks.  Even just seeing "undefined not constructable" (and it usually is undefined, rarely anything else in cases like this) tends to be immensely more useful than "not constructable".


Fill in LICENSE

Summary
Fill in the information of owner to LICENSE

Codecov Report
Base: 95.00% // Head: 95.00% // No change to project coverage :thumbsup:

Coverage data is based on head (513188a) compared to base (2748cc1).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #208   +/-   ##
=======================================
  Coverage   95.00%   95.00%
=======================================
  Files          30       30
  Lines        3764     3764
=======================================
  Hits         3576     3576
  Misses        188      188

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Adding Maeghan Porter

Adding myself to the table.

Added in https://github.com/opentffoundation/manifesto/pull/266


Fix docstring of argument 'phase' in construct_iir_filter

The docdict entry is for both IIR and FIR filters, thus it does not apply to construct_iir_filter.

Added a couple more fixes/improvements for TFRs/Spectrum I/O docstrings.


Toplevel error requiring "owl"

Installed Owl from source, I was trying to require "owl" in toplevel(utop), and came across such an error as follows:
utop # #require "owl";;
Error: The external function 'complex64_div_scalar' is not available
If anyone comes across similar error I would like to discuss about it. Thank you.

Hi @porcow,  just to make things clear: what OS / OCaml / OPAM version do you use?  I tend to follow the steps in Dockerfile whenever possible, so for example I use Ubuntu 16.04, OCaml 4.04.0, and OPAM 2.0.0-beta4.

Does this relate to the OPAM issue we discussed before? https://github.com/ocaml/opam/commit/718d6198e338069852dcdde067f56df236235370#diff-5508a1f41811a003b062a9d606062507
Please can you have a look if OPAM copied the Owl's lib file to stubslibs rather than stublibs? In that case, you need to either upgrade to OPAM 2 beta4 at least, or copy it back to stublibs manually.

OPAM copied the Owl's lib file to stubslibs rather than stublibs, I copied it back to sublibs, it works.

OPAM beta 4 fixed this issue, and OPAM beta 5 has been recently released.


Adds a tile for MS Exchange

What does this PR do?
Adds the MS Exchange tile

@zippolyte they want us to add them all to it


Add support for ARM platfoms

This creates ARM-compatible Docker Images in addition to the x86 bases images.

This should fix #45


Exchange Admin does not have access to the Org Settings

"You must have either an Exchange Administrator or a Global Administrator role to configure users for Briefings."
Exchange Admin roles do not have access to the Org Settings in the old or new (O365) admin center

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

ID: 4cee44a2-5742-83c0-ee3e-82a3a3f9417e
Version Independent ID: ad800194-4e32-0529-6844-7529a0d670d7
Content: Configure Briefing email - Cortana
Content Source: Briefing/be-admin.md
Product: mya
GitHub Login: @madehmer
Microsoft Alias: v-mideh

@jadesolis - Thank you for your feedback! I'm forwarding it on to the team and will update the documentation accordingly.


Create eparate even and odd numbers from an array of integers

Put all even numbers first, and then odd numbers
Pull Request Template
What have you Changed(must)
Write here what you have changed in the codebase
Issue no.(must) -
Pr will be close and marked as spam. If issue number not found or issue was assigned to someone else.
Marking as spam can block your account from HacktoberFest.
Self Check(Tick After Making pull Request)

[ ] This issue was assigned to me if not it will be marked as spam.
[ ] My file is in the proper folder
[ ] I am following clean code and Documentation.
[ ] I have added the title and what program will do first in the file
[ ] I have named the file as (Problem #). (Problem Title(in Camel Case)).(extension)
ex. 2. AddToNumbers.py

README - How to Contribute

@chalana98 you have to mention the issue number in the PR Body.


Take non-Send resources out of World

This PR builds on top of #9202 (I separated what could be separated from this PR into that one).
Objective
The aim of this PR is to be the "final" fix to our messy problems involving thread-local data (see https://github.com/bevyengine/bevy/discussions/6552 for context).
Bevy only deals with a handful of thread-local resources (that mostly come from low-level OS APIs or libs that talk to those), but that handful has resulted in a ton of internal complexity (in bevy_ecs, bevy_tasks, and bevy_app). And the way we're currently storing them makes it either difficult or impossible to implement some nice-to-have features (e.g. generalized multi-world apps, framerate-independent input handling, etc.).
Solution
tl;dr Separate non-Send data from the ECS entirely while keeping it indirectly accessible through an event loop running on the main thread. Then, move app updates into a separate thread (on permitting targets) so they don't block this event loop.
This setup should be familiar to any audio plugin developers (or async runtime developers). If a system on thread B needs to do something with data that can't leave thread A, it can just send a command to A's event loop and wait for A to run it (and send any result back).
Some unique benefits of separating Send and !Send data like this are:

Res and ResMut can be removed since they're redundant without NonSend and NonSendMut.
World becomes unambiguously Send, so it can be dropped on any thread.
The multi-threaded executor is able to run any system on any thread (including exclusive systems).
The multi-threaded executor is able to run any system without spawning a task for it (especially exclusive systems).
Any system from any world on any thread is able to remotely access the main thread's local resources.
Input events could be timestamped (with Instant::now()) with minimal expected delay/aliasing (event loop is not blocked).

Changelog
TODO: finish this section

NonSend and NonSendMut have been removed.
Moved storage of non-Send resources to an external ThreadLocals container. It's normally owned by the App.

Migration Guide
If you were doing this before:
fn foo(x: NonSend<X>) {
    /* ... */
}

you're doing this now:
fn foo(mut thread: ThreadLocal) {
    // `run` sends a closure to the TLS owning thread, then blocks until the closure is completed.
    // The closure can return `Send` values back to the caller.
    thread.run(|tls| {
        let x = tls.resource::<X>();
        /* ... */
    });
}

For better or worse, the handling that used to be buried inside the scheduler is now the responsibility of whoever writes an App runner. It's not too much boilerplate though IMO. Here's an example of a basic runner that runs the app once.
fn run_once(app: App) {
    let (mut sub_apps, tls, _runner) = app.into_parts();

    // Create event loop channel.
    let (send, recv) = app_thread_channel();

    // Insert channel.
    sub_apps.for_each(|sub_app| {
        tls.insert_channel(sub_app.world_mut(), send.clone());
    });

    // Move sub-apps to another thread.
    let thread = std::thread::spawn(move || {
        let result = std::panic::catch_unwind(std::panic::AssertUnwindSafe(|| {
            sub_apps.update();
            send.send(AppEvent::Exit(sub_apps)).unwrap();
        }));

        if let Some(payload) = result.err() {
            send.send(AppEvent::Error(payload)).unwrap();
        }
    });

    // Run an event loop in this thread.
    loop {
        let event = recv.recv().unwrap();
        match event {
            AppEvent::RunTask(task) => {
                task();
            }
            AppEvent::Exit(_) => {
                thread.join().unwrap();
                break;
            }
            AppEvent::Error(payload) => {
                std::panic::resume_unwind(payload);
            }
        }
    }
}

Spawning a thread like this is basically mandatory unless you're targeting an environment (i.e. wasm32) or are enabling a bevy compiler flag that forces completely single-threaded system execution. Otherwise, not doing so will risk running into a deadlock.
Unfortunately, the channel between the main and app threads can't always be a std::sync::mpsc::channel. The winit runner spawns an event loop that can only be woken up by winit events, so we have to use their special EventLoopProxy sender. That's the reason for the ThreadLocalTaskSender trait.

I think we should swap this to the 0.13 milestone now. We're drawing close and this is still in draft.

Let me see if I can have this ready for review this weekend. I've already rebased (just haven't pushed) and only the winit runner is unfinished.

I will move this out of draft soon. There is at least one thing to debug still. (The game examples crash after a couple seconds.)
Decided to push this to the next milestone after all since it'll need some thorough testing. It'll also be easier to review after #8745 and #9202 are merged. I'd still like to see this merged as soon as possible since it's blocking other important things.

Leaving a note to myself. #9826 made it possible for the render thread to spawn before the runner is called, so we can't add the ThreadLocalChannel resource to the RenderApp in winit_runner. We need ThreadLocalChannel to implement Clone so the main world can add it to the render world before/during extraction.

Couldn't you spawn a thread wrapping the EventLoopProxy within the winit plugin, and then send messages through a normal channel from there?

Could spawning a thread wrapping the EventLoopProxy within the winit plugin, and then sending messages through a normal channel from there work?

Are you suggesting a something like this?
// create a standard rust channel
let (send, recv) = std::sync::mpsc::channel();

// create a winit proxy
let proxy = event_loop.create_proxy();

// move it into a new thread (so there would be thread "main", thread "app", and now this)
std::thread::Builder::new()
    .name("winit-proxy-listener".into())
    .spawn(move ||
        while let Ok(event) = recv.recv() {
            // got something from the app, forward it to the event loop
            proxy.send(event).unwrap();
        }
    )
    .unwrap();

And were specifically addressing my last comment or what I wrote in the description about the ThreadLocalTaskSender? (Or both?) It does seem like an option to address both problems at once, so I do like your idea. It feels a little overkill to create a thread just to forward messages though. I wonder if the overhead from just having threads is negligible.

Also, side note, ThreadLocalChannel should implement Clone anyway. Once this PR is merged, I want to reorder the app construction process so that building plugins is deferred[^1] and only happens after the runner starts, so the channel will already exist when the RenderApp is created. We'd clone it and add it to the render world then.
[^1]: The only thing a plugin would be able to do immediately on import is change the runner.

That was roughly what I was thinking, yes.
It was a reply to both, plus a question since I'm dealing with some thread-related things in the context of hot reload and was curious if there was a reason it wasn't possible...
Although given that concern - maybe it could be a specialized thing that happens in the app thread as a task? The main thought is wrapping it up somehow to allow the communication into the world to rely purely on standard channels.

Also, side note, ThreadLocalChannel should implement Clone anyway. Once this PR is merged, I want to reorder the app construction process so that building plugins is deferred1 and only happens after the runner starts, so the channel will already exist when the RenderApp is created. We'd clone it and add it to the render world then.
Footnotes
1. The only thing a plugin would be able to do immediately on import is change the runner. [↩](#user-content-fnref-1-f502f6a44712d4e3447a7d1e560d88b2)

This actually brings up a question I've been mulling over - whether it's worth having two distinct plugin types: "Frame" plugins (that require non-send/sync elements and can't be disposed and re-created easily, like winit) and normal plugins (where either it's fully send/sync, or the elements that are non-send/sync are just optimizations/caching/etc and can be thrown away and re-created as needed - for example having a thread-local RNG instance)
I'm coming at this from the perspective of working on hot-reload, where having a fully separate "frame" would allow for much easier reload of the internals.

The main thought is wrapping it up somehow to allow the communication into the world to rely purely on standard channels.

Yeah, I think I'll try incorporating this idea. I am pretty unsatisfied with the ThreadLocalTaskSender trait, especially since it's just a byproduct of trying to interface with winit. It makes sense for WinitPlugin to adopt that complexity.

Is there an existing discussion related to plugin initialization and stuff? Somewhere where the "frame" idea either was discussed or could be raised effectively?

This actually brings up a question I've been mulling over - whether it's worth having two distinct plugin types: "Frame" plugins (that require non-send/sync elements and can't be disposed and re-created easily, like winit) and normal plugins (where either it's fully send/sync, or the elements that are non-send/sync are just optimizations/caching/etc and can be thrown away and re-created as needed - for example having a thread-local RNG instance).

I don't think we need this. The only thing in a plugin that "can't wait" is setting the runner function. The WinitPlugin only creates the EventLoop during its build method because the RenderPlugin needs a window to initialize the renderer on some targets.
If we defer plugins being built, then the EventLoop can just be created by the runner function. It won't need to be stored in TLS.

Is there an existing discussion related to plugin initialization and stuff? Somewhere where the "frame" idea either was discussed or could be raised effectively? (I don't want to pollute this PR with that)

I don't know of anything recent, so free to start one.

Thanks for the quick reply! I agree that it's not needed for this PR to work well - I think it's something that might be useful for other elements (like the editor, embedding in non-bevy apps, and hot reload).  I'll create a new discussion for that, but regardless am excited for this PR!

If we defer plugins being built

For context, I really want to do this anyways to address #1255.


The interrupted status should return to caller

MyBatis version
3.5.9
Database vendor and version
Test case or example project
Steps to reproduce
In org.apache.ibatis.datasource.pooled.PooledDataSource#popConnection

try {
if (!countedWait) {
state.hadToWaitCount++;
countedWait = true;
}
if (log.isDebugEnabled()) {
log.debug("Waiting as long as " + poolTimeToWait + " milliseconds for connection.");
}
long wt = System.currentTimeMillis();
state.wait(poolTimeToWait);
state.accumulatedWaitTime += System.currentTimeMillis() - wt;
} catch (InterruptedException e) {
break;
}

I think it should not break directly,It needs to return the interrupt status to its caller
Expected result
Actual result

closed via #2503


[BUG] Some of the *ToExport keys are missing from the module manifest

Describe the bug
As a best practice, module manifests should define all of the "ToExport" keys, or at the very least the following keys: "CmdletsToExport", "FunctionsToExport", "AliasesToExport", and the keys should not use wildcards.
This is because PowerShell analyzes the module manifest first, and if that has been properly defined then it skips the slower analysis. You can see this in the source code here: https://github.com/PowerShell/PowerShell/blob/master/src/System.Management.Automation/engine/Modules/AnalysisCache.cs#L126
If you are not exporting any Cmdlets or Aliases then they should be defined as empty array expressions like this: CmdletsToExport = @()

That looks like a perfect description of a pull request ... *wink *wink

Thank you very much!


[JavaScript] - "node" module resolution

Report

[x] I have searched existing issues and this is not a duplicate

Issues and Steps to Reproduce
When using Node module resolution, imports from subpaths like yoga-layout/load fail:
import { Overflow } from 'yoga-layout/load'  // fails

This occurs because the package.json uses exports that require bundler module resolution
(https://github.com/facebook/yoga/blob/main/javascript/package.json#L15):
"exports": {
    ".": "./src/index.ts",
    "./load": "./src/load.ts"
}

Many projects and libraries need to maintain compatibility with Node module resolution to support their users' existing codebases and build setups.
While direct application developers can potentially switch to "bundler" module resolution as a quick workaround, this becomes problematic for library authors building on top of yoga-layout. These library authors need to maintain the widest possible compatibility for their downstream users, making it difficult to require specific module resolution strategies.
Bundling yoga-layout as part of our library is not a viable solution as we want to leverage the existing npm ecosystem - allowing users to receive yoga-layout updates independently, maintain their own version management, and use standard module resolution patterns they're familiar with.
Expected Behavior
Imports from yoga-layout/load should resolve correctly when using node module resolution, ensuring broader compatibility across different projects and build configurations.
Actual Behavior
Get TypeScript error:
error TS2307: Cannot find module 'yoga-layout/load' or its corresponding type declarations.

node16 resolution should also work (with the caveats that option has more generally). That has been the resolution for Node 16 in @tsconfig/bases since May 2023 (which is a bit more recent than I expected).
Yoga took a dependence on ES modules for 3.0 to simplify the number of configurations, but that means type checker and bundler need to have some awareness of them. We removed the dependency on top-level await, because it was a bit too breaking, but the ecosystem is pretty increasingly depending on ES module semantics and resolution, so this is a place where projects really should try to put in the work to get a toolchain supporting them.
We export the main entrypoint outside package.json exports, but reaching into yoga-layout/dist/src/load would probably be the best way to get things working with old module resolution in the meantime.

Thanks for the detailed response. I agree that upgrading to modern module resolution is ideal, though it's not always possible in current projects.
Currently we can't create libraries that work across both resolution strategies:
// Works with 'node' resolution, fails with 'bundler'
import { Overflow } from 'yoga-layout/dist/src/load'

// Works with 'bundler' resolution, fails with 'node'
import { Overflow } from 'yoga-layout/load'

Would something like this in the package.json help support both cases?
"exports": {
    ".": "./src/index.ts",
    "./load": "./src/load.ts",
    "./dist/src/load": "./dist/src/load.js",
    "./dist/src/load.js": "./dist/src/load.js"
}

I think I’d be okay with going the other way, of adding a “/load” entry point file that just lives at the root for those not able to use ES resolution or top level await. So long as it’s able to resolve to the right place, after the transformation we do when shipping the source (yarn prepack triggers this).

Works for me. I'll make a PR at some point next week.

@NickGerleman For further compatibility, what are your thoughts on switching the import extensions from .ts to .js, or using the new --experimental-transform-types to transform them? Currently the imports within the declaration files all have .ts extensions.
https://devblogs.microsoft.com/typescript/announcing-typescript-5-7-beta/#path-rewriting-for-relative-paths

We rewrite .ts to .js in the source when we run the Babel transform before packing: https://github.com/facebook/yoga/blob/main/javascript/babel.config.cjs#L26
The packing step will also replace .ts with .js for entrypoints: https://github.com/facebook/yoga/blob/050ac8a4132fa5c888eb7c3518ea8c95dc5f6bec/javascript/just.config.cjs#L61
The declaration files do still have a .ts extension, but actually resolve to the .d.ts files, and are just used for type imports.
The original source files pre-transform are also still there, without the rewriting, but they should never be directly imported. They are more useful just for source maps pointing to original source if debugging the released package.

This approach doesn't work in TypeScript versions prior to 5.0 - you'll get TS2691 errors complaining that import paths cannot end with .ts extensions in declaration files, even though these are just type imports. For example:
error TS2691: An import path cannot end with a '.ts' extension. Consider importing './wrapAssembly.js' instead.

So it looks like declaration extensions don't get transformed https://github.com/microsoft/TypeScript/pull/59767#issuecomment-2389761587 🙃
For now, I see two paths:

We tweak .ts to .js manually in TypeScript source files.
We do something similar to prepack-package-json, but this seems a little convoluted.

Wouldn’t the first option break type-checking during development?
If TypeScript team says that .d.ts files don’t get rewritten because they are allowed to import via .ts, and the supported (last two years) of TS allow this, it might be better not to fuss with too much.

No, types are maintained. Try this branch - https://github.com/facebook/yoga/pull/1764

Closing - support not planned https://github.com/facebook/yoga/pull/1764#issuecomment-2561137878


feat: add DataInterpolationsRegularizationToolsExt extension

Move RegularizationSmooth definitions to the extension
Extension loads when RegularizationTools is loaded

Interestingly this doesn't fail locally 😅 ; neither on Windows nor on WSL(Ubuntu) for either versions.


⚠ Bofrost.be has degraded performance

In 70a3112, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1890 ms

Resolved: Bofrost.be performance has improved in 05d7609.


Transfer Repo to an Organization?

Create an organization for us and transfer this repo to there?
https://help.github.com/articles/transferring-a-repository-owned-by-your-personal-account/

git remote set-url origin git@github.com:meifamily/ptt-alertor.git
govendor sync
change go import directory
grant access for travis ci
modify .travis.yml

test

[ ] Everyone push success
[ ] Travis CI success
[ ] Deploy success
[ ] Run success

related PR
bc77b33045c0a61251482480edde36a09f7c2c59


Validate mnemonic index

Validate if the index to derive the private keys of the mnemonics-based wallet is missing.
At the time it throws an undescriptive error message:  Error: Expected UInt32, got null

Hey @josher8a and thanks for participating in the KMS repo. Would it be ok for you if we would do a code review the same way we do internally, and let you then process it to polish it a bit the code to comply with our internal quality gates?

Hi @vaclav-tatumio Of course, I'm happy to help!


expressInstall - controller.web.port wrong

When using expressInstall for 'host it myself' you are supposed to be able to set export ZITI_EDGE_CONTROLLER_PORT=8441. This works great for all the ports in the controller config file . See how address is overridden properly (:8441) but the listen interface is wrong (:1280)
web:
  # name - required
  # Provides a name for this listener, used for logging output. Not required to be unique, but is highly suggested.
  - name: client-management
    # bindPoints - required
    # One or more bind points are required. A bind point specifies an interface (interface:port string) that defines
    # where on the host machine the webListener will listen and the address (host:port) that should be used to
    # publicly address the webListener(i.e. mydomain.com, localhost, <IP_ADDRESS>). This public address may be used for
    # incoming address resolution as well as used in responses in the API.
    bindPoints:
      #interface - required
      # A host:port string on which network interface to listen on. <IP_ADDRESS> will listen on all interfaces
      - interface: <IP_ADDRESS>:1280
        # address - required
        # The public address that external incoming requests will be able to resolve. Used in request processing and
        # response content that requires full host:port/path addresses.
        address: bobby.com:8441

the only workaround i found at this is to leave port 1280 and not override ZITI_EDGE_CONTROLLER_PORT


Method to get varianset by ID?

Hi,  I searched the issues for this.  I would like to fetch a variantset by ID.  I don't see a get method defined in the GA4GH 0.5.1 API documentation,  although the google API defines
GET  /variantsets/variantSetId
Is this just missing from the documentation, or is it not part of 0.5.1?  In general can we count on a "get" method to retrieve any entity that has an ID?

Was added as part of this commit
https://github.com/ga4gh/schemas/blob/master/src/main/resources/avro/variantmethods.avdl#L55
/**************** /variantsets/{id} *******************/
/**
Gets a `VariantSet` by ID.
`GET /variantsets/{id}` will return a JSON version of `VariantSet`.
*/
org.ga4gh.models.VariantSet getVariantSet(
  /**
  The ID of the `VariantSet`.
  */
  string id) throws GAException;


multimc: add link to pr in aliases

Motivation for this change
I was confused why, as the package seemed maintained
Having this PR linked clears up the confusion
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

LGTM


Call to undefined function OptimistDigital\NovaBlog\Models\nova_lang_get_all_locales()

When I try to create a new Post I get the following error
Call to undefined function OptimistDigital\NovaBlog\Models\nova_lang_get_all_locales()

Having the same issue!

You need to install another package
https://github.com/optimistdigital/nova-lang

Hey! Thanks for reporting this. I've released 9.2.0 of nova-blog which includes a fix. Sorry for the delay.


[rv_dm] Fix RDC and DFT issue with resets

Convert the JTAG combined resets to have a synchronous assertion timing in the core clock domain, placing them on the D input of the first flop of the prim_flop_2sync, instead of the reset inputs of both flops. This removes the asynchronous reset assertion that may cause RDC issues, and it restores scan reset as the only reset for those 2 flops when in scan mode.
Note that prim_fifo_async_simple guarantees that a prior transaction in flight will at least maintain its data values, since the holding register is not reset. This mechanism does not guarantee that the request will be squashed, but it does guarantee that the request will not be malformed by the reset. In addition, if the JTAG reset is held for long enough (i.e. >= the round-trip delay), the response for any previously in-flight request will be dropped.

Note that the guarantee of not mangling the request, provided by prim_fifo_async_simple + long enough reset, is what's new since this was last proposed, in https://github.com/lowRISC/riscv-dbg/pull/5.

Please merge if there is agreement.
The failure is unrelated to this PR. The test was brought in via https://github.com/lowRISC/opentitan/pull/23378, where it experienced merge skew and started failing when rebased atop 3238897abe90a976ea45f78ed1c6eb39f9712d54 (from https://github.com/lowRISC/opentitan/pull/23544)

Let's merge this to include it in the next RC following today. If additional review feedback comes in, we can still do a follow-up PR if needed. But based on the discussion in the linked issue and @a-will 's expertise with the matter, I don't think this will be necessary.

Just some notes (reinforcing your reasoning here in one case):

I believe there is a potential corner case where a TRST may be missed if

the JTAG clock is faster than the RV_DM clock, and the TRST is not asserted for more than a cycle.

A TRST minimum width in the spec is par for the course, though. Ideally, we would filter short pulses, even, so glitches don't count. At least we have the schmitt triggers. :)

or the RV_DM core clock is not enabled (e.g. during sleep).

If we wanted to fix that, I don't think the answer is that async feedthrough reset, though. Probably, I'd choose to have this become a synchronous reset request that sticks until acknowledged by the RV_DM clock domain (via good, old prim_sync_reqack, perhaps). DMI would be blocked and yield errors until it cleared.
We'd need something like an SR latch for the TRST_N pin for that, since the pin is async to any clock. Without the latch, I think I'd only have the TRST_N pin reset the TAP FSM, then leave DTM and DMI reset duties to just dtmcs.dmihardreset.


Benchmark with other version and libraries

Library
Insert
findPk
complex
hydrate
with
memory usage
time

                           PDO |     71 |     78 |     58 |     57 |     55 |      768,832 |   0.32 |
                      Propel16 |    181 |    121 |     85 |    151 |    166 |    9,699,328 |   0.71 |
             Propel16WithCache |    117 |     67 |     76 |    129 |    130 |    9,699,328 |   0.53 |
                      Propel17 |    167 |    105 |     82 |    151 |    166 |    9,437,184 |   0.68 |
             Propel17WithCache |    118 |     69 |     70 |    117 |    109 |    9,699,328 |   0.49 |
                      Propel20 |    183 |    116 |     83 |    180 |    179 |   12,320,768 |   0.75 |
             Propel20WithCache |    129 |     78 |     81 |    153 |    143 |   10,747,904 |   0.59 |
        Propel20FormatOnDemand |    128 |     76 |     77 |    146 |    144 |    6,029,312 |   0.58 |
                    Doctrine24 |    305 |    260 |    152 |    458 |    461 |   16,252,928 |   1.67 |
           Doctrine24WithCache |    305 |    251 |     81 |    283 |    211 |   16,777,216 |   1.17 |
        Doctrine24ArrayHydrate |    304 |    256 |     82 |    158 |    137 |   15,728,640 |   0.97 |
       Doctrine24ScalarHydrate |    306 |    252 |     82 |    127 |    114 |   15,728,640 |   0.92 |
      Doctrine24WithoutProxies |    304 |    252 |     83 |    214 |    307 |   15,990,784 |   1.20 |

After merge PR #482

Library
Insert
findPk
complex
hydrate
with
memory usage
time

                      Propel20 |    184 |    118 |     88 |    179 |    180 |    5,767,168 |   0.75 |
             Propel20WithCache |    126 |     76 |     79 |    150 |    144 |    5,767,168 |   0.58 |
        Propel20FormatOnDemand |    129 |     76 |     78 |    146 |    145 |    5,767,168 |   0.58 |

Legend
In columns of "Insert", "findPk", "complex", "hydrate" and "with" represents the time in milliseconds.
In column "memory_usage" stated real memory usage in bytes, including the necessary classes to library work.
In column "time" indicates the time taken to perform all tests in seconds.
The lower the value, the better, for all the columns.
Please do not close this issue, I will be updated periodically.
My repository for this tests https://github.com/vlastv/php-orm-benchmark

Updated 2015-Dec-07 - including Yii 1, Yii 2, LessQL and Eloquent shows that Propel 2 is rather slow compared to the competition these days.
PHP-FPM 5.6.4 with opcode cache

Library
Insert
findPk
complex
hydrate
with
memory usage
time

PDO
111
121
15
78
221
774,944
0.55

LessQL
313
335
100
220
281
5,494,704
1.42

YiiM
683
332
99
195
104
9,175,040
2.18

YiiMWithCache
632
360
106
179
116
9,175,040
1.96

Yii2M
1207
1198
141
483
302
13,369,344
4.56

Yii2MArrayHydrate
1662
872
131
264
217
13,631,488
3.81

Yii2MScalarHydrate
1314
964
140
225
239
13,631,488
3.80

Propel20
568
183
377
747
824
10,747,904
4.19

Propel20WithCache
377
114
389
576
690
10,747,904
3.61

Propel20FormatOnDemand
393
129
241
629
748
11,010,048
3.42

DoctrineM
758
1023
1087
639
598
16,515,072
8.41

DoctrineMWithCache
776
1096
1224
879
637
15,990,784
9.18

DoctrineMArrayHydrate
800
1103
857
430
588
15,990,784
10.19

DoctrineMScalarHydrate
910
1285
1774
336
453
15,990,784
11.83

DoctrineMWithoutProxies
805
1190
1282
518
751
15,990,784
12.47

Eloquent
1206
733
188
289
527
11,272,192
4.36

EloquentWithoutEvent
1051
707
175
308
833
11,010,048
3.92

HHVM 3.10.1

Library
Insert
findPk
complex
hydrate
with
memory usage
time

PDO
58
29
10
40
92
763,920
0.25

LessQL
187
211
68
86
152
10,328,440
0.80

YiiM
383
201
111
85
46
6,325,032
1.09

YiiMWithCache
384
212
111
92
52
6,343,648
1.11

Yii2M
558
397
88
92
56
8,711,264
1.86

Yii2MArrayHydrate
566
348
90
83
57
8,744,344
1.77

Yii2MScalarHydrate
561
350
90
68
57
8,746,528
1.76

Propel20
426
128
639
451
532
10,362,480
2.72

Propel20WithCache
388
92
615
394
455
10,422,936
2.46

Propel20FormatOnDemand
352
92
605
309
482
10,449,600
2.36

DoctrineM
642
655
904
436
318
19,621,456
5.55

DoctrineMWithCache
658
682
948
452
338
19,631,944
5.72

DoctrineMArrayHydrate
627
664
911
224
240
18,423,328
5.27

DoctrineMScalarHydrate
636
659
949
159
202
17,339,720
5.17

DoctrineMWithoutProxies
663
702
905
282
344
19,384,088
5.46

Eloquent
633
298
110
101
215
13,945,632
1.75

EloquentWithoutEvent
597
318
126
122
242
13,865,192
1.77

Note: The reference is the PDO TestSuite (the number of tests is adjusted to make raw PDO score about 100 to each test). For the ORMs, the smaller score is the better (i. e. the faster).

@motin Please test on the php7 too

@Big-Shark Sure, will do

PHP-FPM 7.0.0 GA

Library
Insert
findPk
complex
hydrate
with
memory usage
time

PDO
78
89
4
74
207
1,720,072
0.45

LessQL
207
188
89
181
169
10,108,848
1.09

YiiM
437
193
87
116
84
4,194,304
1.70

YiiMWithCache
409
201
100
106
81
4,194,304
1.55

Yii2M
530
624
80
169
122
6,291,456
3.01

Yii2MArrayHydrate
515
489
84
130
107
8,388,608
2.17

Yii2MScalarHydrate
483
369
98
119
129
8,388,608
2.31

Propel20
404
95
375
534
534
6,291,456
4.11

Propel20WithCache
257
58
358
470
413
6,291,456
3.54

Propel20FormatOnDemand
358
54
482
426
464
6,291,456
4.40

DoctrineM
846
1396
3220
569
570
14,680,064
20.79

DoctrineMWithCache
547
722
1106
353
349
14,680,064
16.96

DoctrineMArrayHydrate
504
936
2698
285
523
14,680,064
13.22

DoctrineMScalarHydrate
753
1085
1567
197
377
14,680,064
19.21

DoctrineMWithoutProxies
496
871
1762
247
544
14,680,064
13.05

Eloquent
709
478
147
223
451
8,388,608
3.34

EloquentWithoutEvent
610
347
148
207
364
8,388,608
2.35

@motin Today I found yii cheating and fixed it, also updated propel, eloquent, yii2 and doctrine orm.
https://travis-ci.org/Big-Shark/forked-php-orm-benchmark

@Big-Shark Great, I updated the results for all benchmarks in the readme of https://github.com/Big-Shark/forked-php-orm-benchmark, and they are vastly different from last time. Lesson: We should make sure to get consistent, reproducible results before interpreting the numbers too much.

https://travis-ci.org/Big-Shark/forked-php-orm-benchmark

cool :) :+1:

But I guess there is something wrong with memory detection. Yii and Propel2 have the same memory 8,388,608, which is rather highly unusual.

@marcj It's very strangely, but we running every test for different thread, and calculate memory for thread
https://github.com/Big-Shark/forked-php-orm-benchmark/blob/master/propel_20/TestRunner.php
https://github.com/Big-Shark/forked-php-orm-benchmark/blob/master/propel_20/TestRunnerPropel20TestSuite.php

Just guessing, but the memory may be reserved in discrete chunks.


Coversion to int_ for unless tag

Describe the bug
The code following results in a reference being replaced with an int_ reference
{{ unless ({cookie:visited}) | contains(url) }}
  {{ new_cookie = (({cookie:visited}) + ',' + ({url})) }}
  {{ cookie:set :visited="new_cookie" }}
{{ /unless }}

results in the first line being changed to {{ unless (int_4d5317e034b8) | contains(url) }}
Interestingly it seems to work fine if logic is changed to:
{{ if ({cookie:visited}) | contains(url) }}
{{ else }}
  {{ new_cookie = (({cookie:visited}) + ',' + ({url})) }}
  {{ cookie:set :visited="new_cookie" }}
{{ /if }}

Still occurs if {cookie:visited} (instead of surrounded by brackets) is used.
Deleting the rest of the template does nothing - ie. the code above in isolation is enough to trigger this.
Impacted Products
Which Antlers Toolbox products does this bug apply to?

[- ] Antlers Toolbox for VS Code (v2.6.14)

Please let me know if I can provide more info? Totally possible my syntax is off - haven't played with the cookie function before today. 🙏

Thanks for the report! I've released a patch to correct this in the following versions:

Antlers Toolbox for VS Code 2.6.15
prettier-plugin-antlers (npm) 2.0.2
antlers-formatter (npm) 1.2.11


Zodiac Symbols

Hello, My name is Jhonatan and I would like to make this small contribution, which allows you to generate a random zodiac sign.
Reason:
Why not?
I like your project and for that reason I would like to contribute with a little bit of code.

So I am supportive of this addition and thank you for your work here!
My only question is around the list of symbols you have to pick from. You have:
["Ram","Bull","Twins","Crab","Lion","Virgin","Balance","Scorpion","Archer","Goat","Water-Bearer","Fish"]

I am no expert on this stuff, but when I do a search, my first hit returns:
["Aries","Taurus","Gemini","Cancer","Leo","Virgo","Libra","Scorpio","Sagittarius","Capricorn","Aquarius","Pisces"]

And these are the ones I am more familiar with also. Was there a reason you had the list you did?

So I am supportive of this addition and thank you for your work here!
My only question is around the list of symbols you have to pick from. You have:
["Ram","Bull","Twins","Crab","Lion","Virgin","Balance","Scorpion","Archer","Goat","Water-Bearer","Fish"]

I am no expert on this stuff, but when I do a search, my first hit returns:
["Aries","Taurus","Gemini","Cancer","Leo","Virgo","Libra","Scorpio","Sagittarius","Capricorn","Aquarius","Pisces"]

And these are the ones I am more familiar with also. Was there a reason you had the list you did?

Hi! Thanks for your reply. I decide this nomenclature because i think that is more international (English) but is true that the second list is more recognisable. I change this!

Coverage: 95.567% (+0.009%) from 95.558% when pulling 89fb35a679563c04f5b125561d97354766081cc4 on seon22break:master into 9dde97f9d57c786d8aa88efe7c769da2f779fb2a on chancejs:master.


feature/cli test

Codecov Report

Merging #8 into master will increase coverage by 2.33%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master       #8      +/-   ##
==========================================
+ Coverage   90.67%   93.00%   +2.33%
==========================================
  Files           9        9
  Lines        1072     1072
==========================================
+ Hits          972      997      +25
+ Misses        100       75      -25

Impacted Files
Coverage Δ

src/main.rs
100.00% <100.00%> (+30.76%)
:arrow_up:

src/git/mod.rs
93.50% <0.00%> (+16.88%)
:arrow_up:

Continue to review full report at Codecov.

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


CDC markdown / link edits

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/be82cf03c9b30bbee9a2189f632308935264e0b7/
Edited pages:

v19.1/change-data-capture.md
v19.2/change-data-capture.md
v2.1/change-data-capture.md
v20.1/change-data-capture.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/be82cf03c9b30bbee9a2189f632308935264e0b7/


unified linux repos.

When we install SQL server we install it via a yum/Debian repo, which is how you’re supposed to do it. If we have other packages like this:
https://docs.microsoft.com/en-us/sql/azure-data-studio/download?view=sql-server-2017
We should put them in the same yum/debian repo to simplify/unify package installation.
We should also put the pssdiag and sdp in our repos as well as it’ll help us in support getting those deployed to customer systems.
I propose we rename:
https://packages.microsoft.com/config/rhel/7/mssql-server-2017.repo
To something more generic and put all our RPMs in it. Same with the other distros repos. For anyone that that is already using the sql 2017 repo we can just clone the master ‘generic’ repo.
This way when product updates come out, customers can easily update them without doing manual procedures and it would also help if we start getting into package dependencies of our own (like if sql ops studio required sql server, for a bad example).
It’s not just that it makes it easier to install and update the packages, it looks a lot more professional for admins to install our packages via REPOs and while the repositories themselves won’t establish us as an open source software vendor, they will create the perception of it.
Rather then the SQL server Linux repository, it should be the Microsoft Redhat repository, or the Microsoft Ubuntu repository.
My 2 cents.

While we wait for this to be implemented, I created a script that uses curl, and hxnormailze and hxselect from the html-xml-utils library to get the download link from the ADS download page, wget to download the .deb and dpkg to install it. You can find it in a gist here. Works on Ubuntu right now because that's what I am using.


fix(gs): Broadcast state by viewports

Continuation of #120, required #133 first

A few people saw paused red unnameds that only exist on the client (unable to be killed and they stay in the client's viewport even when far away)
I've only ever seen it twice and I'm unable to replicate but I think broadcasting position when not in viewport is the only thing that potentially causes this


Configure alert via array

What do you think about ability to config alert using array?
Somehow like:
sweet()->generate([
    'title' => 'Are you sure?',
    'text' => 'You will not be able to recover this imaginary file!',
    'type' => 'warning',
    'showCancelButton' =>  true,
    'confirmButtonColor' => '#DD6B55',
    'confirmButtonText' => 'Yes, delete it!',
    'cancelButtonText' => 'No, cancel plx!',
    'closeOnConfirm' => false,
    'closeOnCancel' => false,
    'showConfirmButton' => true,
    'timer' => null,
    'callback' => 'function(isConfirm) {
       if (isConfirm) {
           swal("Deleted!", "Your imaginary file has been deleted.", "success");
       } else {
           swal("Cancelled", "Your imaginary file is safe :)", "error");
       }
    }'
]);

Pushed https://github.com/DraperStudio/Laravel-Sweet-Flash/commit/b605d296df8dd62f267e34f5b040a18ea0f5a60b to accept an array as key.
You should be able to do the following now
sweet()->config([
    'title' => 'Are you sure?',
    'text' => 'You will not be able to recover this imaginary file!',
    'type' => 'warning',
    'showCancelButton' =>  true,
    'confirmButtonColor' => '#DD6B55',
    'confirmButtonText' => 'Yes, delete it!',
    'cancelButtonText' => 'No, cancel plx!',
    'closeOnConfirm' => false,
    'closeOnCancel' => false,
    'showConfirmButton' => true,
    'timer' => null,
    'callback' => 'function(isConfirm) {
       if (isConfirm) {
           swal("Deleted!", "Your imaginary file has been deleted.", "success");
       } else {
           swal("Cancelled", "Your imaginary file is safe :)", "error");
       }
    }'
])->commit();

Pushed https://github.com/DraperStudio/Laravel-Sweet-Flash/commit/56d20924e84f861507cb6966de409dc79609e02b to add a little helper method so that you can just call sweet()->custom($config); instead of sweet()->config($config)->commit();

Thank you.


Mostly completed this

I think there are a few minor details to iron out with regard to the tracking step, I also need to test the alignment against previously aligned image sets that used the old methods

also should add that Manasi has been using this so thus far it seems like it works well on windows too