Add support for building Realm & RealmSwift for tvOS

[x] [Notifier] Watch changes for tvOS without pipes

Thanks for your work on this, @kishikawakatsumi! Once you've added back in the RLMNotifier approach, you can close #2506 and we can use this PR as the defacto standard branch for tvOS.

I've just updated https://github.com/realm/realm-cocoa/pull/2721 to use GM build of core/framework, change default directory to Library/Caches, encryption disabled, and inter-process notification is disabled.
You can use pre-release version of Realm & RealmSwift for tvOS, like following:
pod 'Realm', git: 'https://github.com/realm/realm-cocoa', branch: 'kk-tvos'
pod 'RealmSwift', git: 'https://github.com/realm/realm-cocoa', branch: 'kk-tvos'

@kishikawakatsumi now that #2756 has been merged, could you please re-apply these changes? It should be simpler now that we're sharing build settings among schemes.

@jpsim Rebased #2756 other than unit tests on tvOS simulators. I'm working on re-enable unit tests.

Thanks for the hard work on this, @kishikawakatsumi, keep it up!

Unit tests on simulator now works again.

CI is failing due to hitting assertion failures: https://ci.realm.io/job/objc_pr/2271/configuration=Debug,swift_version=1.2,target=osx-swift/console and https://ci.realm.io/job/objc_pr/2271/configuration=Release,swift_version=2.1,target=ios-device-objc/console
Test Suite 'KVOTests' started at 2015-11-05 17:08:38 +0000
Test Case '-[RealmSwift_Tests.KVOTests testAllPropertyTypesMultipleAccessors]' started.
Assertion failed: (ret >= 0), function listen, file /Users/realm/workspace/objc_pr/configuration/Debug/swift_version/1.2/target/osx-swift/tightdb_objc/Realm/ObjectStore/impl/apple/external_commit_helper.cpp, line 222.

Testing failed:
	testAllPropertyTypesMultipleAccessors() encountered an error (Test session exited(-1) without completing. If you believe this error represents a bug, please attach the log file at /var/folders/bj/n03qf0s968d07kcp9bc4v_vw0000gl/T/com.apple.dt.XCTest-status/Session-2015-11-05_09:07:14-bUfEnr.log)
** TEST FAILED **

and
Test Suite 'iOS static tests.xctest' started at 2015-11-05 09:13:07.029
Test Suite 'ArrayPropertyTests' started at 2015-11-05 09:13:07.029
Test Case '-[ArrayPropertyTests testAddInvalidated]' started.
2015-11-05 09:13:07.460 TestHost[9068:60b] WARNING: An RLMRealm instance was deallocated during a write transaction and all pending changes have been rolled back. Make sure to retain a reference to the RLMRealm for the duration of the write transaction.
Assertion failed: (ret >= 0), function listen, file /Users/realm/workspace/objc_pr/configuration/Release/swift_version/2.1/target/ios-device-objc/tightdb_objc/Realm/ObjectStore/impl/apple/external_commit_helper.cpp, line 222.
** TEST FAILED **

@jpsim Thanks! I didn't notice those assertion failures. I've confirmed fixing locally and rebased it.

I've still not seen running tests on AppleTV devices from a command line. But they are succeeded running from Xcode (⌘ + U). So now @jp could you try to execute on CI machine?

I'll look into testing on device, sure. Yesterday you said that there were still a few failures when running from Xcode, do those now pass?

Yesterday you said that there were still a few failures when running from Xcode, do those now pass?

@jpsim Yes, the failures are due to invoke abstract class as tests from Xcode when I execute tests from "Test Navigator" pane. It won't occur when executing tests from "⌘ + U".
class RealmCollectionTypeTests: TestCase {
    var str1: SwiftStringObject!
    var str2: SwiftStringObject!
    var collection: AnyRealmCollection<SwiftStringObject>!

    func getCollection() -> AnyRealmCollection<SwiftStringObject> {
        fatalError("abstract")
    }

    func getAggregateableCollection() -> AnyRealmCollection<SwiftAggregateObject> {
        fatalError("abstract")
    }

ok great

@jpsim
Device tests on tvOS from command line freezes in replacing existing signature. It cannot launch TestHost.app. :cry:
Log:
Probing signature of /Users/katsumi/Desktop/Realm/realm-cocoa/build/DerivedData/Realm/Build/Products/Release-appletvos/Tests.xctest/Frameworks/libswiftXCTest.dylib
  /usr/bin/xcrun '--toolchain' '/Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain' 'codesign' '-r-' '--display' '/Users/katsumi/Desktop/Realm/realm-cocoa/build/DerivedData/Realm/Build/Products/Release-appletvos/Tests.xctest/Frameworks/libswiftXCTest.dylib'

Touch build/DerivedData/Realm/Build/Products/Release-appletvos/Tests.xctest
    cd /Users/katsumi/Desktop/Realm/realm-cocoa
    export PATH="/Applications/Xcode-beta.app/Contents/Developer/Platforms/AppleTVOS.platform/Developer/usr/bin:/Applications/Xcode-beta.app/Contents/Developer/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/libexec:/usr/local/bin:/usr/bin:/bin:/usr/libexec:/Users/katsumi/.nodebrew/current/bin:/usr/local/heroku/bin:/Users/katsumi/.rbenv/shims:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/katsumi/Desktop/infer/infer/bin"
    /usr/bin/touch -c /Users/katsumi/Desktop/Realm/realm-cocoa/build/DerivedData/Realm/Build/Products/Release-appletvos/Tests.xctest

CodeSign build/DerivedData/Realm/Build/Products/Release-appletvos/Tests.xctest
    cd /Users/katsumi/Desktop/Realm/realm-cocoa
    export CODESIGN_ALLOCATE=/Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate
    export PATH="/Applications/Xcode-beta.app/Contents/Developer/Platforms/AppleTVOS.platform/Developer/usr/bin:/Applications/Xcode-beta.app/Contents/Developer/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/libexec:/usr/local/bin:/usr/bin:/bin:/usr/libexec:/Users/katsumi/.nodebrew/current/bin:/usr/local/heroku/bin:/Users/katsumi/.rbenv/shims:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/katsumi/Desktop/infer/infer/bin"

Signing Identity:     "iPhone Developer: Katsumi Kishikawa (9NXEJ2L8Q6)"

    /usr/bin/codesign --force --sign 26C896B60A13E38F0F5C81E60B2A786234BE5F9F --timestamp=none /Users/katsumi/Desktop/Realm/realm-cocoa/build/DerivedData/Realm/Build/Products/Release-appletvos/Tests.xctest

writeDictToFile:1278 ==== Successfully wrote Manifest cache to /var/folders/wr/f0q3fd5976nd8fwpwk717btr0000gn/C/com.apple.DeveloperTools/All/Xcode/EmbeddedAppDeltas/3d7cf2c566bf62d201eb7903faa4db87/dfc1205d89010714a4c87e1c710b0e651568377a/ManifestCache.plist
/var/folders/wr/f0q3fd5976nd8fwpwk717btr0000gn/T/A18A38CB-22F9-4B0F-B683-2F5712748D0B-49424-00005C6608C9D5D0/tmp/XCTest.framework: replacing existing signature
/var/folders/wr/f0q3fd5976nd8fwpwk717btr0000gn/T/A18A38CB-22F9-4B0F-B683-2F5712748D0B-49424-00005C6608C9D5D0/tmp/IDEBundleInjection.framework: replacing existing signature

I saw an issue like that when working on refactoring the Xcode projects. IIRC I resolved it by rebooting the device and / or my computer.

My solution to running tvOS tests on device is somewhat inelegant, but fairly trivial.
xcodebuild fails to run tvOS framework unit tests on physical devices, but has no issues whatsoever running unit tests for an application.
So I've shared the TestHost scheme and added both test suites as its "testables".
To run Objective-C and Swift tests independently would require sharing two test host schemes, but because both these test suites only take a few seconds to run I opted to combine both sets of tests.
I should be able to set this up in the office on CI early next week (the TV is no longer attached to CI at the moment because I was testing it directly).

One major limitation about the current device tests is that test output isn't logged other than *** Tests Succeeded *** or *** Tests Failed ****. We could set up some remote logging if we find that it's necessary, but I'm not inclined to do that immediately.

@jpsim Thank you very much to be able to run tests on devices! I've pushed tvOS examples (response cache sample and pre-loaded readonly data sample). Please review thouse if you get a chance.

simulator & device tests now run (and pass! :tada:) on CI.
https://ci.realm.io/job/objc_pr/2408/configuration=Release,swift_version=2.1,target=tvos/console
https://ci.realm.io/job/objc_pr/2408/configuration=Release,swift_version=2.1,target=tvos-device/console

@kishikawakatsumi can't seem to get Realm (core) to build in xcode 7.1 using a4e49b7. Is there a relatively stable commit in this branch you recommend using? I'm getting errors specifically in the recently added code. Here's the I'm seeing in case you're interested:
Pods/Realm/Realm/ObjectStore/impl/apple/external_commit_helper.cpp:47:52: No member named 'listen' in 'realm::_impl::ExternalCommitHelper'
Pods/Realm/Realm/ObjectStore/impl/apple/external_commit_helper.cpp:50:31: Use of undeclared identifier 'm_thread'
Pods/Realm/Realm/ObjectStore/impl/apple/external_commit_helper.cpp:60:18: Use of undeclared identifier 'm_thread'
Pods/Realm/Realm/ObjectStore/impl/apple/external_commit_helper.cpp:65:38: Unknown type name 'm_realms_mutex'
Pods/Realm/Realm/ObjectStore/impl/apple/external_commit_helper.cpp:79:5: Use of undeclared identifier 'm_realms'
Pods/Realm/Realm/ObjectStore/impl/apple/external_commit_helper.cpp:84:38: Unknown type name 'm_realms_mutex'
Pods/Realm/Realm/ObjectStore/impl/apple/external_commit_helper.cpp:85:44: Use of undeclared identifier 'm_realms'
Pods/Realm/Realm/ObjectStore/impl/apple/external_commit_helper.cpp:90:13: Use of undeclared identifier 'm_realms'
Pods/Realm/Realm/ObjectStore/impl/apple/external_commit_helper.cpp:97:28: Out-of-line definition of 'listen' does not match any declaration in 'realm::_impl::ExternalCommitHelper'
Pods/Realm/Realm/ObjectStore/impl/apple/external_commit_helper.cpp:104:38: Unknown type name 'm_realms_mutex'
Pods/Realm/Realm/ObjectStore/impl/apple/external_commit_helper.cpp:105:30: Use of undeclared identifier 'm_realms'

In case it's not obvious, I've tried installing the branch using CocoaPods using the suggested dependency targets.

@azoff Thank you for pointing out! I forgot to push a commit. It's my bad.
I've fixed and rebased to master, then pushed. Can you try again?

@kishikawakatsumi yes that worked!

I've updated this PR to use core's 0.95.1 release, which contains tvOS slices. We should then be able to merge this pending #2914.

Addressed feedback.

Remaining CI failure is a missing provisioning profile for the tv device. Code changes look good to me.

The tvOS machine should have the appropriate provisioning profile. I re-bootstrapped all the CI machines yesterday (after this job was last run), so I'm now rerunning the job for the last commit to see if that helps at all.

@kishikawakatsumi @bdash @tgoyne I think this is ready to go.

@kishikawakatsumi if you have time, it'd be nice to update the examples to use Realm notifications.

:+1:

@jpsim I've updated to use notification block.

:+1:

A 2.5MB binary blob for test data is sorta excessive. The repo is already bloated enough that it won't add all that much to the clone time, but it triples the size of the zip downloaded for CI jobs.

A 2.5MB binary blob for test data is sorta excessive.

Ouch, I hadn't noticed it was that large. I've culled the data down to just places in California and then compacted the file, so now it's about ~200KB.


srcSize is incorrect

https://github.com/luben/zstd-jni/blob/1f04f24d02bd7c74c890b1325766b808fb353b4e/src/main/java/com/github/luben/zstd/ZstdDecompressCtx.java#L251
Expected:
The srcSize should be srcBuf.limit()-srcBuf.position()
e.g.
https://github.com/luben/zstd-jni/blob/1f04f24d02bd7c74c890b1325766b808fb353b4e/src/main/java/com/github/luben/zstd/ZstdDecompressCtx.java#L238-L243
Actual:
This will throw srcSize is incorrect if srcBuf.position() isn't 0

yes, you are right. Looks there was miss in testing as we used buffers with postition() == 0


Event listener

Hi all,
I was Tuya dimming units that can also can be switched by a physical switch. I would like to receive an update through the socket connected to the device to know when that happens, so i can sync my Dashboard (Openhab). Anyone any success in getting this to
work?
I think i could add a listener to the socket on the device object directly, but it seems like a hack to me: what happens when the the socket closes and a new one is made? I assume the socket listener is gone then as well. Also, i may read data which is the response  to a command instead of a physical switch...
Any thoughts?
thanks! Michiel

Hi Michiel,  tinytuya is a command line Tuya library that allows you to poll devices for state or change state (on/off/dim/color).  A python script could be written to continually poll every X seconds and report changes (tinytuya also supports socket persistence).  I'm not familiar enough with Openhab to know what you are needing.  Does it work with MQTT?

Hi all. I just started to work with tuya and I am also no expert in homeautomation or network communication.
My target was to monitor if a switch is pressed. Of course I can do that by polling the status but I would prefer the switch to send an event which I can receive in python.
What I found out so far:
I logged the communication on my router and analyzed it whit Wireshark. And it looks like the Smart Live App is not polling for status. But if I press the switch the app shows the new state right away. This also works if I disconnect the router from the internet.
Has anyone an idea how tuya is doing that?
Is someone more experienced in network communication than me and could do a more detailed analysis of the communication?
If we find out how it works we could maybe develop the same functionality for python.
PS: thanks for tinytuya i really like it.

Based on my research into other Tuya projects as well as the https://iot.tuya.com/ developer portal, I discovered two ways that Tuya devices communicate:

Tuya Cloud - as IoT devices, they are designed to connect with the TuyaCloud to post status changes as well as receive commands.  This is how 3rd party integrations like Alexa are able to control and display Tuya devices.  This is also why you are able to control your Tuya devices from your smart phone even when you are not on your local network.

Local Network - the Tuya devices also communicate on the local area network.  It does so in two ways:

UDP Broadcasts - Tuya devices broadcast basic information about themselves via UDP packets (port 6666 and 6667) - this payload contains useful but public information (ID, IP, Product SKU and Version) but does not provide state data or the ability to control it.  This communication is use to help determine the IP address of Tuya devices that can change over time (DHCP) as well as discover new devices.  This is used by tinytuya during the python -m tinytuya scan command.

TCP Server - Tuya devices listen on port TCP 6668 for clients.  Clients connect with this to get state data and to send control codes in an encrypted way.  The encryption key is set when you pair the Tuya device with the Smartlife App (the first time or any subsequent time will change the key -- the key is stored in the Tuya device and in TuyaCloud).  The Smartlife App uses this local TCP server and encryption key to connect to the Tuya devices directly. This is also how tinytuya works.  It connects directly to the Tuya device over this TCP port and uses the encrypt key you provide (which can be pulled from TuyaCloud via the python -m tinytuya wizard command).  Once a client like tinytuya is connected, the Tuya device will send state changes and heartbeat information over that TCP link for the duration of the TCP link.  In your example, even when you disabled your connection to the internet, your SmartLife App was still connected to your Tuya device (TCP 6668) and therefore was able to reflect the state changes (turn on/off) of the device even without the internet connection to TuyaCloud.

My attempt to diagram this connectivity is here: https://raw.githubusercontent.com/jasonacox/tinytuya/master/docs/TinyTuya-diagram.svg
You can mimic the functionality that you are looking for in Python by keeping a persistent TCP connection to the Tuya devices.  You can do that with tinytuya using the set_socketPersistent(False/True) function and create a heartbeat loop and event handler for state changes for each device.  This is similar to what localtuya is doing for Home Assistant ingegration (see https://github.com/rospogrigio/localtuya).
Here is a possible/poor example, but may help:
import tinytuya
import time

# tinytuya.set_debug(True)

d = tinytuya.OutletDevice(DEVICEID, DEVICEIP, DEVICEKEY)
d.set_version(3.3)
d.set_socketPersistent(True)

print(" > Fetch Status < ")
data = d.status()
print(data)
time.sleep(2)

while(True):
    data = d.heartbeat()
    print('Heartbeat response: %r' % data)
    time.sleep(2)

Hi thank you so much. Your answer and example was super helpful.
Maybe you could consider to put your example also to the "Programming with TinyTuya" section on the main page.
I reused your code to control a Zigbee light whit a curtain control in a way that the light turns on when I close the curtain. My actual code is a little bit more complicated (depended on time and curtain position). The control works now in real time.
To sum it up I'm super happy.
My simplified code (maybe helpful for someone else):
`b = Bridge(ip='???',username="???")
b.connect()
LN=[8,9]
def Light(x):
if x == 'on':
b.set_light(LN, 'on', True)
elif x == 'off':
b.set_light(LN, 'on', False)
d = tinytuya.OutletDevice('???', '???', '???')
d.set_version(3.3)
d.set_socketPersistent(True)
print(" > Send Request for Status < ")
payload = d.generate_payload(tinytuya.DP_QUERY)
d.send(payload)
try:
while(True):
# See if any data is available
data = d.receive()
print('Received Payload: %r' % data)
    print(data)

    if data != None:
        if data.get('dps') ==  {'1': 'stop'}:
            Light('')
        if data.get('dps') ==  {'1': 'close'}:
            Light('on')
        if data.get('dps') ==  {'1': 'open'}:
            Light('off')

    # Send keyalive heartbeat

print(" > Send Heartbeat Ping < ")
    payload = d.generate_payload(tinytuya.HEART_BEAT)
    d.send(payload)

except KeyboardInterrupt:
pass`

I wonder what is the appropriate procedure to get zigbee PIR data without stressing the tiny PIR battery by constantly polling.
If i poll the z-bridge does it poll the sensor or does it report an internal state?
Is "data = d.receive()" polling the internal buffer or does it ask the remote device?

@PepeTheFroggie https://github.com/jasonacox/tinytuya/issues/221#issuecomment-2559797687


Starknet by Example's translation is relatively good, and I have made…

… corrections to the translation errors I found during today's learning process.
Issue(s):
Description
Starknet by Example's translation is relatively good, and I have made corrections to the translation errors I found during today's learning process.
Checklist

[*] CI Verifier: Run cairo_programs_verifier successfully
[*] Contract Tests: Added tests to cover the changes
[*] Remix Link: Added a link to open the contract in Remix
[*] Deployed Contract (Optional): If possible, include a Voyager link to a deployed contract on Goerli

@cryptonerdcn Could you review the changes made to the translation?

@julio4
The content seems OK, but this PR needs to rebase these changes to the main branch because this .po file is an older version.
@shepf
Could you do that?

@julio4 The content seems OK, but this PR needs to rebase these changes to the main branch because this .po file is an older version. @shepf Could you do that?

I submitted a PR based on the latest main branch~


Bump diagnostics bokeh dependency to 2.4.2

Bumps dask.diagnostics bokeh dependency to 2.4.2, to match up with the proposed version bump in https://github.com/dask/distributed/pull/4614.
cc @quasiben @jacobtomlinson

[ ] Closes #xxxx
[ ] Tests added / passed
[ ] Passes pre-commit run --all-files

Seems fine with me. cc @jsignell as this will need to be bumped in conda-forge as part of the release.


Static interface methods are only supported starting with Android N in Kotlin 1.3.20

When I've added the library in gradle and build, I got an error.

implementation 'com.squareup.okhttp3:logging-interceptor:3.13.1'

Static interface methods are only supported starting with Android N

Per the release notes, OkHttp requires that you enable Java 8 in your builds to function as of 3.13 and newer. You can learn more about how to enable this at https://developer.android.com/studio/write/java8-support.
You need to add something like
android {
    compileOptions {
        targetCompatibility = "8"
        sourceCompatibility = "8"
    }
}

to your application build.gradle.

Thank you.
Now it's working fine.


Using  causes "Uncaught TypeError: Cannot read property 'constructor' of null"

When using the provider setup like so:
import Signt from 'react-sight'
  ReactDOM.render(
    <Sight>
      <AppContainer store={store} routes={routes} />,
    </Sight>
    document.getElementById('root')
  );

I get "Uncaught TypeError: Cannot read property constructor of null"

Could it maybe have to do with stateless components not having a constructor? Are stateless components supported?
Did I maybe miss something in setup?

Thanks for trying it out!
 It looks like you're using our npm module - this was our beta code but we forgot to take it down. We started out as an npm module but moved all of its functionality to our chrome extension. The module no longer works. We updated npm to point to this repo for instructions.
To use React Sight, you only need to install the chrome extension.

Perfect great to know. Only tried this out after not getting the chrome extension to work (Cannot read property getState of undefined).


Transparent decryption with metadata replacing

Added processing DataRowDescription and ParameterDescriptionData. In DataRowDescription now we replace OID values that tell drivers which data types will be returned. In ParameterDescriptionData we replace OIDs for parameters in prepared statements. To tell apps that they should pass string value instead of binary (that will be changed on Acra side)
Extend encryptor config with two new fields: default_data_value and data_type. Last values generated via protobuf in similar way as token type.
Added support of text format values in binary protocols (prepared statements). Previously was supported only binary formatted values.
Refactored QueryDataEncryptor to re-use functions related to parsing placeholders and saving encryptor's settings in context/client session values
Extended ClientSession interface to provide KV interface and store session related data for client/db packet handlers
Removed legacy acra-log-verifier config file from configs folder
Added updating context (ctx) with flag after successful decryption (base.[MarkDecryptedContext|IsDecryptedFromContext]). Needs for replacing with default values binary data types that hard to determine when they was untouched
Removed legacy interface method SubscribeOnColumnDecryption and all related methods of proxies due to not using
Refactored PgSQLDataEncoderProcessor. Now it used not only for tokenization, but for decoding all input data from database and encoding before sending to client. Also removed this logic from PostgresqlDecryptor which now responsible only for database packet parsing. All other data manipulations moved to OnQuery/OnBind/OnColumn subscribers
Additionally removed DecodedData wrapper for Column structs used by decryptor

It's ready to review. Probably last changes will be related to encryptor's config validation and updating changelogs (after that I will change it from status Draft). So welcome to review.
Checklist

[+] Change is covered by automated tests
[+] The coding guidelines are followed
[+] Public API has proper documentation in the Acra documentation site or has PR on documentation repository
with new changes
[-] CHANGELOG.md is updated (in case of notable or breaking changes)
[-] CHANGELOG_DEV.md is updated
[ ] Benchmark results are attached (if applicable)
[ ] Example projects and code samples are up-to-date (in case of API changes)

you prefer that I will fix current comments, commit, wait approval and after that split it into the separate PRs and review one more time or we can finish it as is and keep it in mind in the future?)

I think we can left this PR as is :)


Start with Windows not working..

Selecting the box "Start with Windows" does not seem to be working. Tried with Aurora with and without admin mode.
running Windows 10 64bit
Aurora 0.6.0
Selecting "Start Aurora in a minimized state" this works when I manually open Aurora
** Checked my Startup tab after rebooting, Aurora is there, Status Enabled, Startup impact Not measured
It's defiantly is not starting up on reboot.

Can you open properties of Aurora.exe, if there's a button for "unblock" or "this file came from another computer". Unblock it and try again.

Can you open properties of Aurora.exe, if there's a button for "unblock" or "this file came from another computer". Unblock it and try again.

you talking about right clicking the Aurora.exe / Properties ?
theirs no options like those.
Aurora also shows to be in my regedit>windows>currentversion>run
"C:\Program Files**\Aurora.exe" -silent -delay 5000

you talking about right clicking the Aurora.exe / Properties ?
theirs no options like those.
Aurora also shows to be in my regedit>windows>currentversion>run
"C:\Program Files**\Aurora.exe" -silent -delay 5000

I don't even have skype installed :)
I just changed the regedit file to "C:\Program Files\Logitech Gaming Software\Mods\Aurora\Aurora.exe" /autostart /tray -silent
that fixed it.
probably don't need the /tray (going to remove that and reboot again. I think just /autostart is probably what fixed it.

I don't even have skype installed :)
I just changed the regedit file to "C:\Program Files\Logitech Gaming Software\Mods\Aurora\Aurora.exe" /autostart /tray -silent
that fixed it.
probably don't need the /tray (going to remove that and reboot again. I think just /autostart is probably what fixed it.

That's not possible? I don't have those options implemented.

That's not possible? I don't have those options implemented.

I just altered the registry Run file.
This is what it was: "C:\Program Files**\Aurora.exe" -silent -delay 5000
This is what it is now: "C:\Program Files**\Aurora.exe" /autostart -silent
Seems to have fixed it. Maybe you can use this info to fix the select box.
As far as Aurora I have only ever run the official setup exe and then replaced those files with 0.6.0 later on.

I just altered the registry Run file.
This is what it was: "C:\Program Files**\Aurora.exe" -silent -delay 5000
This is what it is now: "C:\Program Files**\Aurora.exe" /autostart -silent
Seems to have fixed it. Maybe you can use this info to fix the select box.
As far as Aurora I have only ever run the official setup exe and then replaced those files with 0.6.0 later on.

Try just with "-silent". /autostart should have no effect on Aurora.

Try just with "-silent". /autostart should have no effect on Aurora.

sure I'll try it. give me a minute

sure I'll try it. give me a minute


Revert "Chore/fix semgrep path"

Reverts Uniswap/token-lists#605

Add

Out

Uploading document(2).pdf…


[stable/postgresql] Improve 'extraEnv' example in values

Signed-off-by: juan131<EMAIL_ADDRESS>Is this a new chart
NO
What this PR does / why we need it:
Improve the example in the values.yaml so users understand how to use the extraEnv parameter.
Which issue this PR fixes

fixes https://github.com/helm/charts/issues/19386

Checklist

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

/lgtm


C++: Model for gets

Create a model for gets and fgets.

There are some failing unit tests and a failing qlformat test.

Test failures: There were some new duplicate test results in the code repo, due to both the argument and return value of gets being considered a taint source (with one now flowing to the other).  I've put these test changes in https://git.semmle.com/Semmle/code/pull/36297 and I'm hoping that the tests will pass there.
I've also put in a rather general fix for this kind of duplication, which affects a handful of other tests as well.  In the case of gets the results are closer to what the old security taint tracking library gave us, in other cases they may not be but I believe they are (1) of higher quality and (2) not going to affect the samate test suite (because it doesn't care how many times a result is reported, nor even which line it's reported on, so [de-]duplication is transparent to it).


Make default parameter overloads binary compatible

This changes all overloads from https://github.com/microsoft/OpenAPI.NET/commit/f00c27cc0e104dd67ae26f85323950a7ae44e5d4 to be binary compatible for not having 1.2.0 break 1.1.4 upgrades

Retargetting on master


Where clause

Hi @pvecchiato @sjauld. Is it possible to use linq to generate a where clause from a JsonColumnType?

Hi @pvecchiato @fsergiojr @johnludgate @sjauld Is it possible to use linq to generate a where clause from a JsonColumnType?

@sjauld any news about this?

Hi @robertovaldesperez - apologies for the delayed response.
We're happy to review and accept a pull request if this is a feature you would like add.


refactor: Adds path.purge to ast-types tool

Coverage remained the same at 60.465% when pulling f47ab638b294842cb84a006d37f6cabb6c27047b on typings-update into<PHONE_NUMBER>b769b5a15d6cce2e6611ee09581e01 on master.


Add flag to inhibit movie creation in comp mode

Since we are looking at testing code by running short matches in CI and the videos created are discarded, it is unnecessary to record the movie in the first place.
Not doing a recording greatly increases the speed of the simulation and as such decreases the CI time. On an example CPU-only system a 5-second match is reduced from 2 minutes 18 seconds to 24 seconds.
This would most benefit #271 and PeterJCLaw/code-submitter#10

Since the quality of the recording is (IIRC) already controllable via the match file, maybe an option is to have quality 0 imply this?

Since the quality of the recording is (IIRC) already controllable via the match file, maybe an option is to have quality 0 imply this?

I was thinking simply having an environment variable like SR_COMP_NO_RECORD but using the match file also acheives a similar end.

I was thinking simply having an environment variable like SR_COMP_NO_RECORD but using the match file also acheives a similar end.


Minor improvements

This issue is imported from pivotal
Small findings after test

@arnoutt Could not reproduce _Fonts in Safari are not displaying correctly (Firefox = OK)_ (Okke Harsta - Jan 6, 2020)

@okkeh re: fonts issue, the current version on .test.surfconext.nl looks different in Safari than it does in Firefox..

(Left = Safari)  (Arnout Terpstra - Jan 6, 2020)

@arnoutt and if you try a private window in Safari? Or do a hard refresh? Cmd/Shift R (Okke Harsta - Jan 6, 2020)

@okkeh this was in a private window. Hard refresh no effect!

Probably my content blocker? I'll check. (Arnout Terpstra - Jan 6, 2020)

@okkeh this was already in a private window :) refresh has no effect. Also, it\'s not my content blocker... (Arnout Terpstra - Jan 6, 2020)

Then I need to investigate. Might be a browser interpretation of the fonts downloaded:
https://account.test.surfconext.nl/fonts/proxima_nova/ProximaNovaSoft-Semibold.otf
https://account.test.surfconext.nl/fonts/proxima_nova/ProximaNovaSoft-Medium.otf
To manage expectations: I have no idea how to fix this, but I'll Google;-(
(Okke Harsta - Jan 6, 2020)

Bad news: https://stackoverflow.com/questions/5082632/same-font-except-its-weight-seems-different-on-different-browsers (Okke Harsta - Jan 6, 2020)

Hmm but this is a rendering issue? In safari, the font I see is still Arial... (AFAICT) (Arnout Terpstra - Jan 6, 2020)

Solved by converting ttf font files to woff/woff2 (Okke Harsta - Jan 7, 2020)


commands_map broken after switch to redis ~4

redis-rb 4 introduced  a breaking change in version 4.0 where redis.client became a CLIENT command to Redis server. This breaks commands_map that sets values on redis.client.command_map, but probably also the whole subscribe_stop function.
An easy fix is to just replace redis.client with redis._client, as I've done here: https://github.com/path-network/logstash-input-redis/commit/fb7e374e1a2e0ed2310fe76e9ae6a3daf6c1dbc3
According to the redis-rb changelog for 4.0.1 the proper way to replace client usage is to use a new redis.connection function instead.

Thanks for the report, we pushed 3.6.1 please let us know if you run into any issues.
In the fix we tried to avoid using the 'internal' _client unless necessary: https://github.com/logstash-plugins/logstash-input-redis/pull/86 ... but otherwise it started based on your suggestions.


Fix typo in trusted types

We want to check for either trustedTypes or TrustedTypes here, until the capitalized TrustedTypes implementation is gone

Looks like something is up with travis launching Chrome, but I think unrelated to this change


Show dynamic greeting message

@rashikaranpuria Hi Rashi, I was not sure how to separate step 3 and step 4, so I decided to work on them in one branch. I will add changes as you suggested for step 3 in this PR as well.


add a footer to this website

Description
i want to add a footer to codetalk website as it is essential
Screenshots

Additional information
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I have checked the existing issues
[ ] I'm a GSSoC'23 contributor
[X] I want to work on this issue

Description
i want to add a footer to codetalk website as it is essential
Screenshots

Additional information
No response
Record

[x]  I agree to follow this project's Code of Conduct
[x]  I have checked the existing issues
[ ]  I'm a GSSoC'23 contributor
[x]  I want to work on this issue

Hi @GAGANRAGHAV can you please double check if this is the project you're referring to, as you're talking about codetalk website


Remove the magic from js.constructorOf[C]

It can be implemented in user-space as:
def constructorOf[C <: js.Any](implicit ct: ConstructorTag[C]): js.Dynamic =
  ct.constructor

This is a binary-incompatible change, so it needs to go in 1.0.0.

My work in progress for #2805 and #2398 suggests that js.constructorOf will be revived as more fundamental. Therefore, I think it makes sense to keep it as a primitive.


Out of date Chrome

I feel like you might just need to update to a more recent Electron? I dont know, but anyways, noticed there haven't been any new releases since 0.1 and this popped up a little while ago:

I tried fixing this by cloning the repo and updating the Electron version, but I couldn't get it to run afterward. I'm a newbie with package management, npm, and electron, but I'm trying to figure it out.


"The cleanup of defaultuser1 accounts" incorrect information

The following needs to be corrected because customers complain about it. Our doc says:
"The account itself has a randomly generated password, which is validated against an organizations password policy, doesn't show up for device sign-in, and is automatically removed after the user resets their password. Multiple defaultuser profiles may exist but can be safely ignored."
In fact, this is the actual behavior:
In Windows 10 (based on internal csswiki): The cleanup of defaultuser1 accounts is not time-based. It’s triggered off the next sign-in (not just unlock) by a local admin. (This is the same behavior for the cleanup of the OOBE ‘defaultuser0’ account.)
In Windows 11 (information received from dev bobgil@microsoft.com): "In Win11 this scenario has an improved underlying infra whereby SSPR should work and delete the sandbox profile without requiring a local admin logon. The customer could test on Win11 to confirm this works in their environment. However, there are no plans to backport that functionality to Win10."

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

ID: c2015c6c-60c7-bb74-469c-e9320301d08a
Version Independent ID: 0ff19de6-c892-10ff-5fe8-f6a70abfa3f5
Content: Self-service password reset for Windows devices - Azure Active Directory - Microsoft Entra
Content Source: articles/active-directory/authentication/howto-sspr-windows.md
Service: active-directory
Sub-service: authentication
GitHub Login: @Justinha
Microsoft Alias: justinha

@sopopa2
Thanks for your feedback! We will investigate and update as appropriate.

Thanks @sopopa1
I created a pull request to update the information. https://github.com/MicrosoftDocs/azure-docs-pr/pull/212202
@Justinha  please review my PR if you can. This was also added to the backlog two years ago but hasn't gotten addressed. https://github.com/MicrosoftDocs/azure-docs/issues/47674
I also created an internal work item here. https://ceapex.visualstudio.com/contributor program/_workitems/edit/711986.
@sopopa2 If you are internal, feel free to use the form I linked for future requests.


Azure Spring Cloud: Support API to enable/disable MSI

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

Can one of the admins verify this patch?

/azp run automation - sdk

Merge blocked by breaking change AddedPropertyInResponse. @leonard520 would you confirm it's really necessary? then we will merge this PR.

/azp run automation - sdk

@leni-msft Our backend is ready and please help to merge the PR. Thanks.


Add Easy ontrol app features

This a feature request for some of the settings that are available in the Easycontrol app(Android) right side

pop out panel(see pic)
-Away
-Child-Lock
-Advance
-Boost
I'm alway using boost to increase/decrease the heating for a few hours or advance to skip to the next preset.
Would be great if these were available through Homes Assistant and being able to see and control the state from the dashboard.
My thermostat is the Bosch EasyControl CT200.
Thanks
Update...
I have now managed to get the "Boost" and "Away" functions by enabling the following entities
for Boost enable the following entities;

switch.boost
number.boost_duration
number.boost_temperature
sensor.hc1_boost_remaining_time

For away anable the following entities;

binary_sensor.autoawayenabled
switch.away_mode
number.away_mode_temp

There doesn't seem to be any entity to enable the "Advance" feature from the app?

I don't know what is advanced feature. Provide bosch scan and analyze what would you like to have.
I'll close issue now and reopen if you come back with data (too many users just ask for something without giving any details so I have too many issues open).


[FEATURE REQUEST] ...File imports stop happening automatically (YNAB devs must like chaos)

Yesturday YNAB removed the ability to import new bank downloads and made it happen automatically. I thought I would open this just in case this is something you guys could do with the toolkit to put back. They really made a mess with this happening automatically and now if I miss a few or more (I tend ot go backpacking for days/weeks) days my imports will be all over the place. CHAOS!
I am pretty sure I am not in the minority.
Thank you!!!

I see they rolled it back. I wonder if a lot of people were up in arms over it or they acutally had real issues.

@axenstarr They rolled it back because of syncing issues, but they said they will make it automatic again as soon as they resolve those issues. Here is their status page on it: https://ynabstatus.com/incidents/tv3rc887hdng

@DavidCannon its coming back now. I've emailed thier support my dislike for it but not likely to get anything back.


update implementation

Pull Request Test Coverage Report for Build 197

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.645%

Totals

Change from base Build 196:
0.0%

Covered Lines:
2179

Relevant Lines:
2352

💛  - Coveralls


add nginx client_max_body_size value

The default value is too low at 1MB resulting in 413 Request Entity Too Large. For a development environment setting this way higher shouldn't be a problem

@ahjorth thanks so much for your contribution. Will merge once the new version is released.

You need to copy-over the value after securing a domain, as it disregards the value in the listen 80 scope.


Update NP-Guard to v1.4.1

Description
Update dependency: NP-Guard to v1.4.1 to address a known bug.
Checklist

[ ] Investigated and inspected CI test results
~[ ] Unit test and regression tests added~
~[ ] Evaluated and added CHANGELOG entry if required~
~[ ] Determined and documented upgrade steps~
~[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)~

Testing Performed

CI only

In addition to reviewing your code, reviewers must also review your testing
instructions and make sure they are sufficient.

Current dependencies on/for this PR:

master

PR #3696   👈

This comment was auto-generated by Graphite.

The crucial test ci/prow/local-roxctl-tests has passed, so this is mergable already.


Update mgmt SDK for new ServiceLinker swagger

API change check for Azure.ResourceManager.ServiceLinker
API changes have been detected in Azure.ResourceManager.ServiceLinker. You can review API changes here


[Feature Request]  SANCTUM SUPPORT

For now I check all the issue and found a way to add sanctum support but I think instead of manual, the library could make this integrated with test like the cache and queue by @GromNaN made to support.  This has status backlog in Jira, but I think with the quick support of cache in 4.3 version it should easily added and add also in docs. Thanks
Copy original PersonalAccessToken
cp ./vendor/laravel/sanctum/src/PersonalAccessToken.php ./app/Models/PersonalAccessToken.php
<?php

namespace App\Models;

use MongoDB\Laravel\Eloquent\Model;
use Laravel\Sanctum\Contracts\HasAbilities;

class PersonalAccessToken extends Model implements HasAbilities
{
    /**
     * The attributes that should be cast to native types.
     *
     * @var array
     */
    protected $casts = [
        'abilities' => 'json',
        'last_used_at' => 'datetime',
        'expires_at' => 'datetime',
    ];

    /**
     * The attributes that are mass assignable.
     *
     * @var array
     */
    protected $fillable = [
        'name',
        'token',
        'abilities',
        'expires_at',
    ];

    /**
     * The attributes that should be hidden for serialization.
     *
     * @var array
     */
    protected $hidden = [
        'token',
    ];

    /**
     * Get the tokenable model that the access token belongs to.
     *
     * @return \Illuminate\Database\Eloquent\Relations\MorphTo
     */
    public function tokenable()
    {
        return $this->morphTo('tokenable');
    }

    /**
     * Find the token instance matching the given token.
     *
     * @param  string  $token
     * @return static|null
     */
    public static function findToken($token)
    {
        if (strpos($token, '|') === false) {
            return static::where('token', hash('sha256', $token))->first();
        }

        [$id, $token] = explode('|', $token, 2);

        if ($instance = static::find($id)) {
            return hash_equals($instance->token, hash('sha256', $token)) ? $instance : null;
        }
    }

    /**
     * Determine if the token has a given ability.
     *
     * @param  string  $ability
     * @return bool
     */
    public function can($ability)
    {
        return in_array('*', $this->abilities) ||
            array_key_exists($ability, array_flip($this->abilities));
    }

    /**
     * Determine if the token is missing a given ability.
     *
     * @param  string  $ability
     * @return bool
     */
    public function cant($ability)
    {
        return !$this->can($ability);
    }
}

Then in AppServiceProvider
<?php

namespace App\Providers;

use Illuminate\Foundation\AliasLoader;
use Illuminate\Support\ServiceProvider;

class AppServiceProvider extends ServiceProvider
{
    /**
     * Register any application services.
     */
    public function register(): void
    {
        //
    }

    /**
     * Bootstrap any application services.
     */
    public function boot(): void
    {
        $loader = AliasLoader::getInstance();
        // using custom PersonalAccessToken model instead of Sanctum's
        $loader->alias(\Laravel\Sanctum\PersonalAccessToken::class, \App\Models\PersonalAccessToken::class);
    }
}

All references
https://github.com/mongodb/laravel-mongodb/issues/2444
https://github.com/mongodb/laravel-mongodb/issues/2445
https://jira.mongodb.org/browse/PHPORM-88

will this update #2580, like override also the extended SpatieRole? If so this update would open up a lot package to be usable that using only Eloquent
<?php
namespace App\Models;
use Spatie\Permission\Models\Role as SpatieRole;

class Role extends SpatieRole
{
use DocumentModel
    // You might set a public property like guard_name or connection, or override other Eloquent Model methods/properties
}

also this for the context of santum
use Laravel\Sanctum\PersonalAccessToken as SanctumPersonalAccessToken;
class PersonalAccessToken extends SanctumPersonalAccessToken
{
// ...
}

I read this Fix #2120 so it does fix issue with extending


Support headers in network package

Current implementation of network client doesn't support headers, causing problems like #43
https://github.com/xendit/xendit-java/blob/master/xendit-java-lib/src/main/java/com/xendit/network/BaseRequest.java

Yeah, we need this. Especially for XenPlatform, where we need to add for-user-id in the header.


xxx already declared error

What happened?
Trying to import my terraform state, I get the error:
 $ pulumi import --from terraform ~/tree/.../terraform.tfstate
[...]
error: anonymous.pp:0,0-9,2: "test_s3" already declared; "test_s3" already declared, and 5 other diagnostic(s)

Strongly suspect this is because the terraform has multiple resource types with the same id:
data "aws_iam_policy_document" "test_s3" {
  statement {
    effect = "Allow"

    actions = [
      "s3:List*",
      "s3:Get*",
      "s3:PutObject",
      "s3:DeleteObject"
    ]

    resources = [
      "${test_s3_bucket.geoip.arn}/*",
      "${test_s3_bucket.geoip.arn}"
    ]
  }
}

resource "aws_iam_policy" "test_s3" {
  name        = "test_s3"
  path        = "/"
  description = "IAM policy for accessing test s3 bucket"
  policy      = data.aws_iam_policy_document.test_s3.json
  tags        = local.tags
}

resource "aws_iam_role_policy_attachment" "test_s3" {
  role       = aws_iam_role.test_update.name
  policy_arn = aws_iam_policy.test_s3.arn
}

But this should be legal.
Example
See test case: https://github.com/brianmay/pulumi_2169
Output of pulumi about
base-5.2$ pulumi about
warning: using pulumi-language-go from $PATH at /nix/store/j1kjljhp66ia1ml9ssj47mglm25v09pf-pulumi-language-go-3.122.0/bin/pulumi-language-go
Enter your passphrase to unlock config/secrets
    (set PULUMI_CONFIG_PASSPHRASE or PULUMI_CONFIG_PASSPHRASE_FILE to remember):
Enter your passphrase to unlock config/secrets
CLI
Version      3.122.0
Go Version   go1.22.5
Go Compiler  gc

Plugins
NAME  VERSION
aws   6.44.0
go    unknown

Host
OS       darwin
Version  14.5
Arch     arm64

This project is written in go: executable='/nix/store/05saqcgidraqmn4z82prsp7rbj9hjmwm-go-1.22.5/bin/go' version='go version go1.22.5 darwin/arm64'

Current Stack: organization/simple/test

TYPE                                               URN
pulumi:pulumi:Stack                                urn:pulumi:test::simple::pulumi:pulumi:Stack::simple-test
pulumi:providers:aws                               urn:pulumi:test::simple::pulumi:providers:aws::default_6_44_0
aws:iam/rolePolicyAttachment:RolePolicyAttachment  urn:pulumi:test::simple::aws:iam/rolePolicyAttachment:RolePolicyAttachment::test_s3
aws:iam/policy:Policy                              urn:pulumi:test::simple::aws:iam/policy:Policy::test_s3
aws:iam/role:Role                                  urn:pulumi:test::simple::aws:iam/role:Role::test_update
aws:s3/bucketV2:BucketV2                           urn:pulumi:test::simple::aws:s3/bucketV2:BucketV2::test

Found no pending operations associated with test

Backend
Name           MEL
URL            file://~
User           brmay
Organizations
Token type     personal

Dependencies:
NAME                                 VERSION
github.com/pulumi/pulumi-aws/sdk/v6  6.44.0
github.com/pulumi/pulumi/sdk/v3      3.121.0

Pulumi locates its logs in /tmp/brmay/nix-shell.Podmtd by default

Additional context
I reported here because it seems to be related to terraform state, and this seems to be the project for that.
Apologise if I reported the bug in the wrong place... Please do let me know if that is the case.
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Thanks for opening the issue!

I'm facing a similar issue where I'm trying to import both S3 and its bucket policy, but they both share the same ID.
I'm currently running an older version of Pulumi (v3.92.0) on a test VM, and it works fine with this version. However, the pipeline uses the latest version of Pulumi, which is where the issue appears.


Added custom parser option to client. Matches existing node method (#751)

Any chance of this getting merged? This is currently blocking our usage of superagent

Some minor nit picks:

jsdoc has wrong type for parse method argument
I'd suggest just a literal copy/paste of the node/index.js parse method code and jsdoc to keep the variable name this._parser the same

I'd be +1 to merge this with that bit of cleanup.

We've decided to rename this function to serialize()


Network: netinfo not showing mode

maverick-netinfo should show whether an interface is in managed or monitor mode

Large amount of info retrieved from netinfo fact when running directly, but when run through maverick-netinfo is not present.  Weird.

pyric fails on getcard call when called under module:
Traceback (most recent call last):
  File "/srv/maverick/software/maverick/bin/maverick-netinfo", line 47, in <module>
    _netinfo.getinfo()
  File "/srv/maverick/software/maverick/manifests/maverick-modules/maverick_network/facts.d/netinfo.py", line 102, in getinfo
    _ifobj = pyw.getcard(self._if)
  File "/usr/local/lib/python2.7/dist-packages/pyric/pyw.py", line 269, in getcard
    if nlsock is None: return _nlstub_(getcard, dev)
  File "/usr/local/lib/python2.7/dist-packages/pyric/pyw.py", line 2236, in _nlstub_
    return fct(*argv)
  File "/usr/local/lib/python2.7/dist-packages/pyric/pyw.py", line 270, in getcard
    return devinfo(dev, nlsock)['card']
  File "/usr/local/lib/python2.7/dist-packages/pyric/pyw.py", line 1028, in devinfo
    idx = _ifindex_(dev)
  File "/usr/local/lib/python2.7/dist-packages/pyric/pyw.py", line 2165, in _ifindex_
    if iosock is None: return _iostub_(_ifindex_, dev)
  File "/usr/local/lib/python2.7/dist-packages/pyric/pyw.py", line 2217, in _iostub_
    return fct(*argv)
  File "/usr/local/lib/python2.7/dist-packages/pyric/pyw.py", line 2172, in _ifindex_
    raise pyric.error(pyric.EINVAL, e)
pyric.error: [Errno 22] ifr_ifrn (dev name) wman0 is invalid

Ah, maverick-netinfo not passing the interface name into the module as a string.  Casting fixes.


AB#28770 switch from order to fsp selection

Describe your changes
Removes selection of PA by order to selecting by FSP which guarantees in most cases immunity from order changes in UI and more randomised tests.
Checklist before requesting a review

[x] I have performed a self-review of my code
[x] I have added tests wherever relevant
[x] I have made sure that all automated checks pass before requesting a review
[x] I do not need any deviation from our PR guidelines

Just a minor change if possible - and I would change all the places you return 400 to -1 (or at least, with this kinds of "search" functions)

Thanks a lot!

Just a minor change if possible - and I would change all the places you return 400 to -1 (or at least, with this kinds of "search" functions)

Thanks a lot!


why a job instead of just a pod?

I often see folks not clean up the job correctly bc deleting the pod doesn't remove the job. Is there a need for a job?

Good question. We should be probably just use a pod instead with no downside

Hmm trying to remember why I switched to jobs instead of pods the way it was before.
I think it had to do with pods getting killed with violence and there not being any trace of what happened whatsoever. Jobs stay around and let me at least inspect logs and kubectl describe the pod for instance.
With better external logging / persistence of run pods, pods do make more sense.


guides/Cloud_development merge

NOTE:

Please fill out the template below

Did you read the instructions in the README?

Yes

Have you read the instructions in CONTRIBUTING?

Yes

Have you written this article by yourself? Have you taken inspiration from anywhere and then written it in your words?

I wrote this article by using personal experience with the product and a bit of information from the official website for the more intricate details.

Please improve your article to include:

How to install Firebase
any other specific stuff one needs to know

P.S. Really good references

Edited really good after review! :tada:  Merging this PR


[QUESTION] Uploading from Android

Hello,
Love the project and I was wondering if there was any ways to upload a pic from Android phones? Is there any current app on the store that could support it? It's not so much to upload my whole library, more to share a video file or stuff like that, that's to big to share on Discord due to the file limit.
Cheers for an answer from anyone

i did a quick google search and found this:
https://f-droid.org/en/packages/com.nyx.custom_uploader/
not sure if it will work, or if it will work how you want it to though.


minor changes to support testing on windows

The following changes are made to support testing on windows.

Changing single quote to double quite for system call
separating setting environment variables in windows and linux

Please apply the same changes in test/xpu/xpu_test_utils.py

@fengyuan14, please take a look, thanks.

Please help to ensure the Linux test result with the same number of PASSED, SKIPPED and XFAIL as before.


Tombola add user ticket

Description

[x] Ability for admin to add a ticket to a user
[x] Fix a bug : balance was not unlocked if user tried to buy a ticket without enough money

Checklist

[ ] Created tests which fail without the change (if possible)
[ ] All tests passing
[ ] Extended the documentation, if necessary

Deleted, branch error


[epic] Implement upgrade tests for Catalogd

In order to have confidence that feature additions and bug fixes are reflected after an upgrade, we should add a suite of upgrade tests that:

Install the most recent public release.
Create objects that sufficiently exercise our API surface and behaviors.
Upgrade in place from the most recent public release to a build from the current commit.
Make assertions that prove that changes from the current commit are reflected.

@joelanford mentioned that his intent to add this as an e2e test.


Documentation to use it with HA ? Primary,Backup,Monitor node ? Should it require 3 exporter each for one node ?

I am using Solace Software Broker with HA and DR Site so in total running 6 nodes of Solace.
Main Site => Primary,Backup,Monitor[3]
Dr Site=> Primary,Backup,Monitor[3]
Any reference/document to monitor this kind of topology.

Here is what i would use:
Create a: https://github.com/solacecommunity/solace-prometheus-exporter/blob/master/docker/solace_prometheus_exporter.ini
and inject this via docker volume to /etc/solace_prometheus_exporter.ini
[endpoint.msg-broker-std]
Version=*|*
Health=*|*
Spool=*|*
Redundancy=*|*
ConfigSyncRouter=*|*
Vpn=*|*
VpnReplication=*|*
ConfigSyncVpn=*|*
Bridge=*|*
VpnSpool=*|*

[endpoint.msg-broker-stats]
VpnStats=*|*
BridgeStats=*|*

[endpoint.msg-broker-details]
ClientStats=*|*
QueueRates=*|*
QueueDetails=*|*

[endpoint.monitoring-broker]
Version=*|*
Health=*|*
Spool=*|*
Vpn=*|*
Bridge=*|*
VpnSpool=*|*

Here the Prometheus config.

Here a guess you run the exporter along with the broker?
I in my case have a singe central exporter and inject username and pw with http post.
This makes updates much easier, caused by the huge amount of broker we operate.

scrape_configs:
  - job_name: solace-msg-broker-std
    scrape_interval: 15s
    metrics_path: /msg-broker-std
    static_configs:
      - targets:
        - broker-main-a:9628
        - broker-main-b:9628
        - broker-dr-a:9628
        - broker-dr-b:9628

  - job_name: solace-msg-broker-stats
    scrape_interval: 5m
    metrics_path: /msg-broker-stats
    static_configs:
      - targets:
        - broker-main-a:9628
        - broker-main-b:9628
        - broker-dr-a:9628
        - broker-dr-b:9628

  - job_name: solace-msg-broker-details
    scrape_interval: 15m
    metrics_path: /msg-broker-details
    static_configs:
      - targets:
        - broker-main-a:9628
        - broker-main-b:9628
        - broker-dr-a:9628
        - broker-dr-b:9628

  - job_name: solace-mon-broker
    scrape_interval: 15s
    metrics_path: /monitoring-broker
    static_configs:
      - targets:
        - broker-main-mon:9628
        - broker-dr-mon:9628

Attention:

If you expect more then 1000 queues per vpn
If you expect more then 1000 connected msg clients
solace-msg-broker-details: will harm your broker performance!

Didt that help? Can this issue be closed?


New version: Alibaba.AlibabaCloudCLI version 3.0.211

Created by 🥟 Dumplings in workflow run #6431.

Log
Updated: 3.0.210 → 3.0.211
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

/azp run

Automatic Validation ended with:

Installation failed with exit code -1978335187
2024-07-09 01:33:36.436 [FAIL] Installer failed security check. Url: https://github.com/aliyun/aliyun-cli/releases/download/v3.0.211/aliyun-cli-windows-3.0.211-amd64.zip Result: 0x80004005

Automated error analysis suggests -1978335187 may mean Installer failed security check. Another script should retry this every 18 hours.
(Automated response - build 886.)

/azp run

Automatic Validation ended with:

Installation failed with exit code -1978335187
2024-07-09 17:51:29.843 [FAIL] Installer failed security check. Url: https://github.com/aliyun/aliyun-cli/releases/download/v3.0.211/aliyun-cli-windows-3.0.211-amd64.zip Result: 0x80004005

Automated error analysis suggests -1978335187 may mean Installer failed security check. Another script should retry this every 18 hours.
(Automated response - build 886.)

/azp run

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


support for PowerShell

First thing: Thank you very much, really nice theme. I used to switch themes depending on the project type. Now I have a couple weeks without switching, they just look great on Night Owl 👍
I also use VS Code for almost every text editing, and I do a lot of Powershell. And PS scripts looks... kinda funny.

Hope you find some time to check it out. Thanks again for your effort!

Yeahhh that's really fugly. Would you mind please PR-ing the demo folder with an example file? That would really help me out to get this taken care of, as it's not my typical workflow. Thanks!

Sure Sarah! I'll get that done first thing morning!

This is fixed! Please let me know if there's anything that needs work. Thanks!


Port planning_scene_tutorial

Port planning_scene_tutorial, adresses #6
Also adds pre commit because formatting is way too easy with this.

This is a nit pick but my setup prints planning_scene_tutorial-1 in front of each line.

I had export RCUTILS_CONSOLE_OUTPUT_FORMAT="[{name}]: {message}" in my bashrc but I removed it and got the same result (maybe I did something wrong).

I have planning_scene_tutorial-X too in my prints. Though I don't know a way to not print it tbh.
export RCUTILS_CONSOLE_OUTPUT_FORMAT="[{name}]: {message}" did not work for me for this particular as well.


build: support building against Foundation.framework

This enables building XCTest against the System Foundation.framework on
macOS.  This requires that the executable path is computed using URL
(NSURL) as the lastPathComponent has been explicitly made
unavailable.
/Users/compnerd/SourceCache/swift-corelibs-xctest/Sources/XCTest/Public/XCTestMain.swift:99:48: error: 'lastPathComponent' is unavailable: Use lastPathComponent on URL instead.
        let exeName = CommandLine.arguments[0].lastPathComponent
                                               ^~~~~~~~~~~~~~~~~
Foundation.StringProtocol:7:16: note: 'lastPathComponent' has been explicitly marked unavailable here
    public var lastPathComponent: String { get }
               ^

Ok, cool. Yeah, I think using SwiftPM as the cross-platform workflow entry point is the recommended path, but if you find it helpful/convenient to be able to use Corelibs XCTest on macOS, I don't see any particular reason to put up roadblocks for that.


More deps are needed for real world app

Hi,
On the main app layer i have more than deps. So I think it needs more, or just let me provide a list or something.

Whoops. Didn’t mean to close!
Cool ;) Thanks for the real world feedback. The only limit to adding more overloads is that IntelliJ can get overwhelmed.
Unfortunately, a list will not work because I need access to the types, at least, I believe it won’t—I’ll do some more explorations, as it would be nicer to both implement and use if I could accept variadic arguments.
In case that is not possible, how many layers do you currently need? I originally had 22, but it got a little slow w/ IDEA.
For now though, I also made a version ZLayer[Your with Layer].fromMagic(...) which performs the same way. This will let you break out large sub graphs and overcome the limit for now.

Whoops. Didn’t mean to close!
Cool ;) Thanks for the real world feedback. The only limit to adding more overloads is that IntelliJ can get overwhelmed.
Unfortunately, a list will not work because I need access to the types, at least, I believe it won’t—I’ll do some more explorations, as it would be nicer to both implement and use if I could accept variadic arguments.
In case that is not possible, how many layers do you currently need? I originally had 22, but it got a little slow w/ IDEA.
For now though, I also made a version ZLayer[Your with Layer].fromMagic(...) which performs the same way. This will let you break out large sub graphs and overcome the limit for now.

OH! IT IS POSSIBLE! Bless you @octavz! You just helped me delete 90% of the code in this thing and simplified the call-site.

OH! IT IS POSSIBLE! Bless you @octavz! You just helped me delete 90% of the code in this thing and simplified the call-site.

14 files changed, 98 insertions(+), 2831 deletions(-) and it works better <3

14 files changed, 98 insertions(+), 2831 deletions(-) and it works better <3

22 is prett yrandom, we have small modules and i easily gathered around 25, given the fact that every zio lib will also provide functionality as a layer is easy to pile up. Ofc we used ++ but I'd prefer to not use that at all unless tgey are top level.

22 is prett yrandom, we have small modules and i easily gathered around 25, given the fact that every zio lib will also provide functionality as a layer is easy to pile up. Ofc we used ++ but I'd prefer to not use that at all unless tgey are top level.

Also i couldn't figure out how to use provideSome with a lot of layers.  Having  provideSomeMagic in between could help with the layers pile, but it doesn't work with a lot of layers.
Other than that we already committed code in repos with zio-magic. :)  Great work. Thanks!

Also i couldn't figure out how to use provideSome with a lot of layers.  Having  provideSomeMagic in between could help with the layers pile, but it doesn't work with a lot of layers.
Other than that we already committed code in repos with zio-magic. :)  Great work. Thanks!

Oh! Now it should work w/ varargs actually. So no limits! @octavz

Oh! Now it should work w/ varargs actually. So no limits! @octavz

Try using the non-snapshot: `"io.github.kitlangton" %% "zio-magic" % "0.1.3"

Try using the non-snapshot: `"io.github.kitlangton" %% "zio-magic" % "0.1.3"


asciidoctor-gb fails to load in metanorma exec

Error:
irb(main):002:0> require 'asciidoctor-gb'
LoadError: cannot load such file -- byebug
	from /Users/myself/.rbenv/versions/2.4.3/lib/ruby/gems/2.4.0/gems/asciidoctor-gb-0.3.1/lib/asciidoctor/gb/converter.rb:10:in `require'

From https://github.com/riboseinc/metanorma/issues/18

Fixed here: https://github.com/riboseinc/asciidoctor-gb/commit/2d40c56ac52454695dd97c09854c9176fa7e7881


Can't instantiate Vm with volatile image

Bug Report
Version of OpenNebula

[ ] 5.2.2
[ ] 5.4.0
[ ] 5.4.1
[ ] 5.4.2
[ ] 5.4.3
[ ] 5.4.4
[X] 5.4.5
[ ] Development build

Probably other versions affected, not tested.
Component

[ ] Authorization (LDAP, x509 certs...)
[ ] Command Line Interface (CLI)
[ ] Contextualization
[ ] Documentation
[ ] Federation and HA
[ ] Host, Clusters and Monitorization
[ ] KVM
[ ] Networking
[ ] Orchestration (OpenNebula Flow)
[ ] Packages
[ ] Scheduler
[ ] Storage & Images
[X] Sunstone
[ ] Upgrades
[ ] User, Groups, VDCs and ACL
[ ] vCenter

Not sure is it a sunstone issue or core issue.
Description
Tried instantiating a VM from template with defined volatile swap disk
Expected Behavior
VM is instantiated on first try
Actual Behavior
Instantiate denied with error message:
[one.template.instantiate] Error allocating a new virtual machine template. DISK 2: SIZE attribute must be a positive integer value.
But just hitting the Create button again - the VM is instantiated.
How to reproduce
Create а VM template with disks as follow
disk0 - non-persistent
disk1 - volatile, SIZE:2GB, TYPE:swap, BUS: scsi, CACHE:none
VM template:
CONTEXT = [
  NETWORK = "YES",
  PASSWORD = "storpool",
  SSH_PUBLIC_KEY = "$USER[SSH_PUBLIC_KEY]" ]
CPU = "1"
DISK = [
  CACHE = "none",
  DEV_PREFIX = "sd",
  DISCARD = "unmap",
  DRIVER = "raw",
  IMAGE_ID = "58",
  IO = "native" ]
DISK = [
  CACHE = "none",
  DEV_PREFIX = "sd",
  DRIVER = "raw",
  FORMAT = "raw",
  IO = "native",
  SIZE = "2048",
  TYPE = "swap" ]
...

Create/Instantiate a VM - it will fail with error message.
Just hitting the create/instantiate again - the VM is instantiated.

This seems to be an issue in 5.4.6.  I have tried the patch above but it doesn't seem to work, are there other files that need changing also?
Thanks

@laurencegill
After applying the patch you need to "compile" the change in the main.js. Usially I do the following(I am using CentOS):
yum install npm
npm install bower -g
npm install grunt-cli -g

cd /usr/lib/one/sunstone/public
npm install
bower --allow-root install
grunt sass
grunt requirejs

And then restart opennebula-sunstone service

Thanks! That has now fixed the issue, every day's a school day :)


Update tooltip docs to add note about disabled

What are you trying to accomplish?
Documenting that tooltip should not be used with disabled.
List the issues that this change affects.
Follow up to Slack thread
Closes https://github.com/primer/view_components/issues/2085
Risk Assessment

[x] Low risk the change is small, highly observable, and easily rolled back.
[ ] Medium risk changes that are isolated, reduced in scope or could impact few users. The change will not impact library availability.
[ ] High risk changes are those that could impact customers and SLOs, low or no test coverage, low observability, or slow to rollback.

Anything you want to highlight for special attention from reviewers?
I noticed that the Accessibility section and the What type do I set information was not being rendered on the doc page for tooltip. I'm assuming this is due to the ongoing docs migration work, and we're only allowing top-level text.
I think this information is very important to surface so I opted to remove the headings to ensure it shows up in the doc.
Merge checklist

[ ] Added/updated tests
[x] Added/updated documentation
[ ] Added/updated previews (Lookbook)
[ ] Tested in Chrome
[ ] Tested in Firefox
[ ] Tested in Safari
[ ] Tested in Edge

Take a look at the What we look for in reviews section of the contributing guidelines for more information on how we review PRs.

Please merge whenever since I don't have merge authorization! Thank you!


Flake8 rule 'E999' reported an invalid point

Flake8 reported an invalid point for the rule E999, with the messge SyntaxError: invalid syntax.

Debug information:
Atom version: 1.11.2
Flake8 version: 3.0.4 (mccabe: 0.5.2, pyflakes: 1.2.3, pycodestyle: 2.0.0) CPython 2.7.12 on Darwin

Please update your flake8 version (pip install -U flake8). This particular error should be fixed in flake8>=3.2.1.

Closing due to a lack of response, if you are still having issues after updating flake8 please provide code to reproduce this!


Notification upon load completion

Anyone have an example YAML or Node-Red of how you're detecting when the load is complete? I'd like to send a notification over my Alexa devices.

There is a boolead attribute called "wash_completed"(or "run_completed in version 0.2.x) for this.
Caution because I just changed "wash_completed" to "run_completed" with last release 0.2.0 to properly manage the attribute for different devices type

Fantastic, that will work nicely.

Hi @daveonkels can you please share how u implemented the run_completed boolean?
pretty new on ha and i see only a sensor for the wasing machine

Sure, I'll whip up a version of this after work now that I know how to get it done. The key is to monitor for changes to the underlying attribute, in this case 'run_completed' but since that's an attribute from the main payload it's a bit harder to fetch.

Close this issue, please use #13 for additional discussion about this point.


How to use this for real time grasp detection?

I was trying to use this code for real time grasping. As a first step I tried to run eval on a tiff image from cornell dataset without using the labels.I observed that before feeding the depth image to the net, the code is cropping the image using the dataset labels. If I comment out the cropping function the results are not accurate.

Hi @skoarkid
The GG-CNN is trained on the cropped patches of the cornell data, as this more closely resembles the scene for the real robot (i.e. single object, close up on a table).  The cornell data images are taken from a long way away and contain lots of background.
If you're interested in using this for real time grasping, I'd recommend looking at my other repo which contains ROS nodes for using this on a real robot. https://github.com/dougsm/mvp_grasp


udevd daemon don't start on new S6 overlay

Home Assistant release with the issue:
109.6
Operating environment:
docker on Synology NAS on root
Hardware context:
I have two USB stick attached on my Synology one for ZWave and another one for Zigbee
I've recently loaded up 109.6 using the official HA image and started to run into ZWave issues.
Indeed if NAS restart the usb mount point can be changed (once the ZWave is on the ttyACM0 another time on the ttyACM1 and inversely for the Zigbee).
for this reason I'm forced to go through the serial by-id mount point.
But the udevd daemon doesn't seem to start (/etc/cont-init.d/udev.sh)
If i lauch commands in manual
udevd --daemon
udevadm trigger
the /dev/serial/by-id is successfully created
if y try to launch /etc/cont-init.d/udev.sh directly i have /etc/cont-init.d/udev.sh: Permission denied error i make a whoami for getting current user and i'm right in root.
make
ls -la /etc/cont-init.d/udev.sh
-rw-r--r--    1 root     root           304 Apr 29 12:24 /etc/cont-init.d/udev.sh
and it seems I don't have the right of execution.

It doesn't need execution permissions.
This generally happens when one overrides the CMD or ENTRYPOINT of the Docker container. Especially on Synology, which tends to read the defaults and overrides them permanently. Make sure you set not CMD. If we detect a CMD is set, the init system will not start (to prevent multiple instances of Home Assistant for example).

Indeed i updated the image, but the old init was still there.
I flush image and recreate form scratch and work great :)
thanks !


fix: get_gutter_width() horizontal scroll issues

Fingers crossed that get_gutter_width() has no more surprises! 😆
Closes #16.

We should also open an issue with neovim.


add suggested fix to prefer error

This error:
[Service.ServiceError.invalid-interface: Please choose which KeyedCache you prefer, multiple are available: MemoryKeyedCache, FluentCache<SQLiteDatabase>]

Should show the user how to fix it:
config.prefer(MemoryKeyedCache.self, for: KeyedCache.self)

Let's please add it to the Vapor docs, it was pretty much waste of time look for this solution when the service is not running without it. 😬 😬


27 canvas codeblock deletion

:ballot_box_with_check: Definition of Done checklist

[ ] Meaningful title and valuable description in pull request
[ ] Code change tested manually if not covered by automated tests
[ ] Pull request linked to one or more issues/stories
[ ] Acceptance criteria of the linked stories satisfied
[ ] Code change comprehended by those who approved it
[ ] State of target branch maintained or improved after the code change

I couldn't find where I could add a description so I'll add a small one here. This pull request contains the code necessary for code block deletion including a new trash can icon in the selection menu. Now we are able to drag code blocks from the canvas to this trash can icon which will remove them.


Why not super() in Bubble init?

https://github.com/discopy/discopy/blob/7b0f7776382593a5049c74b18e72ee530043a4d7/discopy/cat.py#L696
Super is in the other methods.

I would have to double check but I think the reason was that we wanted monoidal.Bubble to call cat.Box.__init__ and not monoidal.Box.__init__ (which would be what happens with super()). Best way to check this would be to run the test suite, please open a PR with your proposed change so I can review it.


Fixes dart empty comments

Resolves #2898
Also fixes empty doc comments eating the next line:
Expected:

Actual:

This type of issue happens easily when using \s to mean whitespace within a line as \s also matches the \n. In most contexts it should probably be replaced by [\t ] when using multi-line matching.
Changes

Distinguish between an empty block comment (/**/ and an opening doc-comment (/**) by adding a negative look-ahead for /.
Only match for up to a single space following a doc-comment (///) instead of any number of whitespace.

Checklist

[x] Added markup tests, or they don't apply here because...
[x] Updated the changelog at CHANGES.md
[x] Added myself to AUTHORS.txt, under Contributors

While working on this fix I noticed a number of issues from the markdown-sublanguage in JSDoc-style doc comments.
/**
Markdown
*/

Since Dart considers these legacy and recommends replacing them with \\\ doc comments, it might be worth removing the special handling for \** comments alltogether.

For historical reasons, dartdoc supports two syntaxes of doc comments: /// (“C# style”) and /** ... / (“JavaDoc style”). We prefer /// because it’s more compact. /* and */ add two content-free lines to a multiline doc comment. The /// syntax is also easier to read in some situations, such as when a doc comment contains a bulleted list that uses * to mark list items.
If you stumble onto code that still uses the JavaDoc style, consider cleaning it up.

https://dart.dev/guides/language/effective-dart/documentation#do-use--doc-comments-to-document-members-and-types

Since Dart considers these legacy and recommends replacing them with \\ doc comments, it might be worth removing the special handling for ** comments alltogether.

We usually don't get in a rush to "deprecate" things from languages if there is potentially still real code out there in the world that we might want to highlight.  I wonder if there isn't some way to make it behave better or if it's always been that broken?
If it's also been broken though and there isn't an easy way to fix it then I could be persuaded regarding removal.


Switch CI to GitHub Actions

Unfortunately, the doctests don't work currently, but I have no idea why.

Hmm… it seems the doctests (more specifically the way the test suite is set up) are more generally broken. This works:
$ stack exec doctest src -- -XNoStarIsType
Examples: 181  Tried: 181  Errors: 0  Failures: 0

But using the test suite (stack test) results in a lot of errors (not-in-scope errors indicating the modules under test are not being loaded…). Sorry, I haven't tried with cabal.
Maybe we need to rewrite tests/DocTest.hs or the test-suite in dimensional.cabal according to latest best practices?

Superseded by #225. Thanks @konsumlamm for starting and @LaurentRDC for getting this done!


Condiational validation rules ? [Question]

I have to buttons in my WPF GUI:
Generate and Compare.
And I have two settings in the GUI I have to check against when one of these buttons are clicked in my validator.
 public HashingViewModelValidator()
        {
            this.CascadeMode = CascadeMode.StopOnFirstFailure;

            When(vm => vm.ActionType == ActionType.Compare, () => // only validate on compare click
            {
                if (vm.IsSettingX) // <-- Need the ViewModel here again
                {
                    FilePathRule();
                    HashTypeRule();
                    OriginalHashRule();
                }
                else if (vm.IsSettingY) // <-- Need the ViewModel here again
                {

                }
            });

            When(hm => hm.ActionType == ActionType.Generate, () => // only validate on compare click
            {
                // the same root checks go here, but other rules apply.
            });
        }

Otherwise I will end up with 4 when rules. To optimize it, I would use RuleSets.

That won't work I'm afraid....you can't access the viewmodel instance directly except within a rule definition. You'd need to use When conditions on the rules to do this.


RDK-332: Add official extender implementation

Changing bhaul indexes so that it doesn't interfere with AP interfaces.
Added support for sixth vap (sta) in wifi_vap_info_map_t
- filling structure in wifi_getRadioVapInfoMap with client_wifi_hal
calls
Added setting sta network config via wifi_createVAP, which fills wifi_sta_network_t structure with data contained in vap_info (as for AP).
Signed-off-by: Michal Cytrycki<EMAIL_ADDRESS>

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

https://jenkins.code.rdkcentral.com/job/github-triggered/20531/ started

https://jenkins.code.rdkcentral.com/job/build-component/55761/ started.

build-tur-bb Console Log uploaded to Gist URL: https://gist.github.com/b9147d5b80074f202c84de741d53e771

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/13902/ started

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/13908/ started

https://jenkins.code.rdkcentral.com/job/github-triggered/20538/ started

https://jenkins.code.rdkcentral.com/job/build-component/55767/ started.

build-tur-ext Console Log uploaded to Gist URL: https://gist.github.com/ea693470d9ce2af946aeccccb74e218e

build-tur-bb Console Log uploaded to Gist URL: https://gist.github.com/c4049f4f300206bef93da1fb5d730fd7

https://jenkins.code.rdkcentral.com/job/github-triggered/20546/ started

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/13918/ started

https://jenkins.code.rdkcentral.com/job/build-component/55768/ started.

Smoke tests for ['build-rpi-broadband'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/122431/

Smoke tests for ['build-tur-bb'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/122432/

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/14097/ started

https://jenkins.code.rdkcentral.com/job/github-triggered/20797/ started

https://jenkins.code.rdkcentral.com/job/build-component/55957/ started.

https://jenkins.code.rdkcentral.com/job/github-triggered/20814/ started

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/14113/ started

Smoke tests for ['build-rpi-broadband'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/122811/

Smoke tests for ['build-tur-bb'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/122812/

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/14225/ started

https://jenkins.code.rdkcentral.com/job/github-triggered/20965/ started

https://jenkins.code.rdkcentral.com/job/build-component/56102/ started.

Smoke tests for ['build-rpi-broadband'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/123099/

Smoke tests for ['build-tur-bb'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/123100/

https://jenkins.code.rdkcentral.com/job/github-triggered/21819/ started

https://jenkins.code.rdkcentral.com/job/build-component/56987/ started.

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/14834/ started

Smoke tests for ['build-rpi-broadband'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/124827/

Smoke tests for ['build-tur-bb'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/124828/


Remove Windows NDK symlink and run apk check + build in separate steps

An obscure one-line apk build failure got shadowed by a much larger deprecation warning shown by cargo check right above, deemed irrelevant. Separating these steps will make it clear when the issue is code-related (ndk, ndk-glue) or build-related (ndk-build, cargo-apk, cargo-subcommand).

GH actions virtual environments have finally been fixed to provide a space-less path to the SDK and NDK by default :tada:. The workaround - introduced in #92 - can finally be removed again!

  = note: 'C:\Program' is not recognized as an internal or external command,
          operable program or batch file.

Ha, very funny. Build-tested this before to make sure the images have been deployed, turns out mine uses Version: 20210121.0 (January 21st) but android-ndk-rs is somehow stuck on 20201210.0 (December 10th).

  = note: 'C:\Program' is not recognized as an internal or external command,
          operable program or batch file.

Ha, very funny. Build-tested this before to make sure the images have been deployed, turns out mine uses Version: 20210121.0 (January 21st) but android-ndk-rs is somehow stuck on 20201210.0 (December 10th).

Hey, the CI magically re-ran 35 mins ago!
Just ran into the inverse error here: https://github.com/MarijnS95/android-ndk-rs/runs/1786432472?check_suite_focus=true:
New-Item: D:\a\_temp\36b3b79e-1665-493e-8ec0-69903de7a78a.ps1:4
Line |
   4 |  New-Item -Path $sdk_root -ItemType SymbolicLink -Value $oldAndroidPat …
     |  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Cannot create symbolic link because the path C:\Android already exists.

Time to merge!

Hey, the CI magically re-ran 35 mins ago!
Just ran into the inverse error here: https://github.com/MarijnS95/android-ndk-rs/runs/1786432472?check_suite_focus=true:
New-Item: D:\a\_temp\36b3b79e-1665-493e-8ec0-69903de7a78a.ps1:4
Line |
   4 |  New-Item -Path $sdk_root -ItemType SymbolicLink -Value $oldAndroidPat …
     |  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Cannot create symbolic link because the path C:\Android already exists.

Time to merge!

Had a hunch, thanks!
The issue was anyway reopened with the "awaiting deployment" flag: https://github.com/actions/virtual-environments/issues/1122#event-4256944059 but it looks like it reached us as well :)

Had a hunch, thanks!
The issue was anyway reopened with the "awaiting deployment" flag: https://github.com/actions/virtual-environments/issues/1122#event-4256944059 but it looks like it reached us as well :)


[Embeddium?] Missing support for the FREX Flawless Frames API for Replay Mod.

Mod Name
Embeddium / Replay Mod
Mod Homepage
https://www.curseforge.com/minecraft/mc-mods/embeddium | https://www.replaymod.com/download/
Minecraft version
1.20.1
Describe the bug
Replay Mod actually used to work with Embeddium (using Connector) without any issues. It seems that something got changed, however. Whenever you try to render a clip, there will be a grayed out "Render" button along with a warning message.
Screenshots

Additional context
Please take a look at the report I made on Embeddium's repo: https://github.com/embeddedt/embeddium/issues/241

Fixed it. Even with the Lazurite update I couldn't render anything, but after making a fresh installation I noticed that everything worked fine. There probably was some breaking change in an Embeddium update that altered the config file in some way. Anyway, I deleted all config files so that they could generate again and everything works perfectly!


Enable write perm for doxygen ci

Enabling write perm for CI, github bot failing since it doesn't have write permission to the repo (for documentation purposes)

I left another branch with the name doxygen_issue for testing


allow country-specific (African countries) customization in the survey

Would like to take part in the survey by sharing with research institutes in Kenya and also academic institutions having research computing components. Can i be included in the 2019 drafting process?

Of course you are more than welcome to join us for the 2019 process. I will contact you with your gmail address provided to see what we can do.
Regards,
Olivier


Move this repository to a more accessible location

As DDOX is quite important to the D ecosystem, I believe it should be easier for people to discover, contribute, and have merge rights. Having it in dlang, dlang-community, or vibe-d would be a step forward IMO. I give those options by order of preference, as dub depends on ddox, I think dlang is the best place, with dlang-community a close second.
Would that work for you @s-ludwig ?

Would be no problem, as long as nobody goes crazy with breaking changes.

Judging from other repositories, I don't think that'd be an issue.

since you still own the source I don't think there will be a big problem, since github just redirects the old repo URLs (even release downloads) to the new one.

Ping @s-ludwig

Yeah, so what's the plan? To @dlang?

Yes I think that's the right location. Do you have access or do you need me to do anything ?

I think you'll have to accept the repo and add me back with permissions, as I don't have owner permissions for dlang itself. I'll invoke the transfer now, though.

Scrap that, you need owner access to initiate the transfer, too. I've made you an admin for ddox instead.

Now I just don't have access to the repository anymore.

Should be fixed

can be closed then?

I saw dub had the old repository for syncing, I changed it to dlang/ddox now


[5.12] Update K8s version to 1.23.12

Explain the changes
This PR attempts to fix broken minikube deployment in our sanity tests by updating k8s version to what we have in master.

[ ] Doc added/updated
[ ] Tests added

We are doing a direct PR into 5.12 and not a backport as this fix was part of https://github.com/noobaa/noobaa-core/pull/6973 which we don't want to backport


Remove strongSwan-based implementation of Cloud Network Instance

The Cloud Network Instance (L3 network with an IPSec connection to a remote VPN endpoint) is not covered by tests and has never been used in production.
Instead, the prevailing opinion is that VPN connectivity (and any other more advanced networking service) should be provided as a part of an application deployed on top of EVE.
Even if we decide to keep native IPSec support inside of EVE, it is easier to first refactor the core of zedrouter and then bring it back piece by piece. But in that case we should also add some Eden tests for Cloud Network Instances to have this feature regularly exercised.

By all means, yes. If it is never used in production, and not tested, let us get rid of it.
We always can deploy an ipsec edge container when we need it. If the demand is there, we then can make it a native thing again, although likely we would do it more simply: one of the standard networks with an api option that connects it to some other network over ipsec.

Should we mark the enum value in the api for cloud ni type as deprecated or currentky not implemented as part of this PR?

Should we mark the enum value in the api for cloud ni type as deprecated or currentky not implemented as part of this PR?

I'm not really sure. There are several network instance types defined by ZNetworkInstType which EVE currently does not implement. I don't know if we want to deprecate them all. There is also a question of how tightly coupled is EVE to this API. Since there are now talks about moving API to a separate repo, maybe a lack of implementation should not be reflected in the API definition? Another point is that while we are removing ZnetInstCloud implementation from dom0, maybe the same Network Instance API could work as an input for an application deployed by EVE and providing this service? My suggestion would be to keep the API as it is and we will see later.

LGTM


Get rid of lodash to achieve a smaller file size

When creating a browser bundle for my unirouter library, I noticed that redux-actions was pulling in nearly 10k from Lodash. I traced it to flux-standard-action, and the isPlainObject call. To eliminate 10k from flux-standard-action's file size, I wrote a standalone isPlainObject function.
This is mostly extracted from Lodash 4, as are the tests. I didn't include the IE6/7 host object check, but that's easy to add in if you'd like. Let me know what you think!

@bkonkle thanks for the contribution - I think in the time that this PR was made and now the lodash file sizes have improved, and I just tested v1.1.0 and found it to be < 10k [uncompressed] including index.js and all dependencies. Let me know if you see anything wildly different from this.
Improvements like this are welcome though, so if you find something else, feel free to crack open another PR! :)

It's very sad it is closed, because it's a pain to use redux-promise -> flux-standard-actions with SystemJS. Because when I agreed to configure lodash.isplainobject, it required yet more three modules: _basefor, isarguments, keysin. My config.js is getting bugger and bigger, and soon exceeds a size of lodash

@JaKXz instead of replacing lodash modular dependencies, would you consider switching dependencies to lodash main module and import from its entries? For example,
Before
import isPlainObject from 'lodash.isplainobject';
import isString from 'lodash.isstring';
import isSymbol from 'lodash.issymbol';

After
import isPlainObject from 'lodash/isPlainObject';
import isString from 'lodash/isString';
import isSymbol from 'lodash/isSymbol';

Thus, for those users who's also using lodash in their user space, the bundler (rollup/webpack) could resolve these modules and create a smaller output. What do you think?

One benefit of this approach is user can combine with babel-plugin-lodash and thus preventing importing the whole lodash into their bundle.

Hey @tomchentw I think that's a reasonable suggestion, want to make a PR? :)
I have a broader, naive question though, probably for @jdalton:
Would it be possible to have lodash itself depend on all the lodash.* modules and just export them under the one var _? There's probably a maintenance issue I'm not thinking of, but perhaps lerna can help with that?

Hi @JaKXz!
The lodash.* packages are self-contained, zero dependency, packages. This means there'd likely be duplication. The preferred route would be to use something like babel-plugin-lodash. In v5 we're dropping the monolithic file altogether opting for folks to use the babel plugin if they want the monolithic-like syntax.

In this case though simply upgrading lodash.isplainobject to ^4.0.0 would get you reduced deps as it now has no deps.

You can look to others like redux which cherry-pick Lodash's lodash/isPlainObject as well into their package build.

@jdalton thanks for the reply :)
I believe we are at ^4.0.0: https://github.com/acdlite/flux-standard-action/blob/master/package.json#L56
but yeah that's a good idea, I'll take a look at redux.

If you go the redux route you can combo with lodash-webpack-plugin for an even smaller bundle.

I've created the PR #51 to address it.


Search bar - categories bar is not properly styled

This is a pretty useful option so we can leave it but we need to add proper margins and set the right font

This should be done based on design https://www.figma.com/file/hrwE3VsMBHgdJoS86rVr4W/Desktop-%26-Mobile-Vue-Storefront?node-id=9338%3A7843

According to latest news from Storefront UI team, they will start working on some examples regarding search results for desktop and mobile view not earlier than at the end of March.


Always getting span_id as null

Hi Team,
I'm trying to use DynamicallyLoadTracer to load zipkin or jaeger library. But i'm always getting parent span is as NULL after ectracting client message.
When i do gdb i can find span_id is null. Could you please suggest what could be the issue here.
This is my client tracer id: uber-trace-id=16b388d3ff1dd88d:4a2e6836f0c9fa90:16b388d3ff1dd88d:1
after this particular line of code:
auto span_context_maybe = opentracing::Tracer::Global()->Extract(OTCorrInfo);
Code for tracer initialization is as below:
const char * configuration=R"({"service_name":"finlistval"},{"disabled": "false"})";
auto& tracer_factory = handle_maybe->tracer_factory();
auto tracer_maybe =tracer_factory.MakeTracer(configuration, error_message);
if (!tracer_maybe) {
sprintf(errMsg,"Failed to create tracer [%s]",error_message.c_str());
OTLogger(errMsg,0);
return -1;
}
tracer = *tracer_maybe;
if(tracer==NULL)
{
sprintf(errMsg,"Tracer is null");
OTLogger(errMsg,0);
}
Gdb output of span_context_maybe =
$1 = {has_value_ = true, contained = {m_value = std::unique_ptropentracing::v3::SpanContext containing 0x0, m_error = {
_M_value = 0, _M_cat = 0x7fff00000005}}}
Please let me know , what i'm doing wrong.

config.yml indentation issue


Bug with New-SSHSession after Remove-SSHSession

Hello,
by creating SSH Sessions the Session ID Starts to count by 0.
When i create 3 Session for the first time. Get-SSHSession looks like:
SessionId  Host                                                                Connected

0      TEST-01                                                           True
1      TEST-02                                                           True
2      TEST-03                                                           True

After Removing the first two Session. Get-SSHSession look like:
SessionId  Host                                                                Connected

2      TEST-03                                                           True

When i create new SSHSession the Session ID starts counting by 1 (not 0)
When the SessionID is in use (like SessionID 2, it still create a new Session with the SessionsID 2)
SessionId  Host                                                                Connected

1      TEST-01                                                           True
2      TEST-02                                                           True
2      TEST-03                                                           True

Is this a bug? Or did i something wrong?
To create a new session i use this snipped:
$created_SSH_Session = New-SSHSession -ComputerName $ComputerName -Credential $Credentials -AcceptKey
$SSH_Session = Get-SSHSession -Index $created_SSH_Session.SessionID
$SSH_Stream = $SSH_Session.Session.CreateShellStream("dumb", 0, 0, 0, 0, 1000)

it is a bug, I will look at how to fix the logic

On Feb 4, 2016, at 9:51 AM, BornToBeRoot<EMAIL_ADDRESS>wrote:
Hello,
by creating SSH Sessions the Session ID Starts to count by 0
When i create 3 Session for the first time Get-SSHSession looks like:
SessionId Host Connected
0      TEST-01                                                           True
1      TEST-02                                                           True
2      TEST-03                                                           True
After Removing the first two Session Get-SSHSession look like:
SessionId Host Connected
2      TEST-03                                                           True
When i create new SSHSession the Session ID starts counting by 1 (not 0)
When the SessionID is in use (like SessionID 2, it still create a new Session with the SessionsID 2)
SessionId Host Connected
1      TEST-01                                                           True
2      TEST-02                                                           True
2      TEST-03                                                           True
Is this a bug? Or did i something wrong?
To create a new session i use this snipped:
$created_SSH_Session = New-SSHSession -ComputerName $ComputerName -Credential $Credentials -AcceptKey
$SSH_Session = Get-SSHSession -Index $created_SSH_SessionSessionID
$SSH_Stream = $SSH_SessionSessionCreateShellStream("dumb", 0, 0, 0, 0, 1000)
—
Reply to this email directly or view it on GitHub https://github.com/darkoperator/Posh-SSH/issues/88.

I found the bug and fixed.
@darkoperator can you please have a look at https://github.com/darkoperator/Posh-SSH/pull/89


BMC/Host Signed image Test

[ ] BMC signed image
[ ] Host signed image

https://gerrit.openbmc-project.xyz/#/c/openbmc/openbmc-test-automation/+/25080/


[4.2] Add tabbed sections to Binding Names + Verbs/Alternative Bindings Page

Thank you! I'm going to hold off on bringing this over to v5.0 documentation for now; I want to see how it feels in v4.2 first (and that'll take a bit of time to get a feel for it)