[Core] Update export syntax, move unit tests, update test dependencies

Changes

Updated export syntax in index.js files to be more concise. Taking advantage of the fact that we're using the babel stage-1 preset.
Removed redundant default export from the main library index.js. All components are on the exports object as is.

breaking! import Mui from 'material-ui'; is now import * as Mui from 'material-ui';

but don't use this anyways :smile:

const Mui = require('material-ui'); does not change :+1:

Updated eslint config

Added .yaml extension. (.eslintrc without an extension is now deprecated by eslint) finally we get syntax highlighting in our editor :hatching_chick:
Fixed up parser options and ecmaFeatures section to match latest eslint documentation
Added eslint-plugin-babel to fix false positives unsupported by eslint

Moved unit tests to the src folder next to their related component and made a few related tweaks to support
Updated some test dependencies (karma plugins and phantomjs)

[x] PR has tests / docs demo, and is linted.
[x] Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[x] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

Added .yaml extension

Any idea why we're using yaml not JSON / JS in the first place?

This looks good to me aside from deciding on the index.js vs direct import from component in tests.
As for the eslint extension, I don't have a strong opinion but agree with not using a deprecated form. If the consensus prefers js I'm good with that too (I'd prefer js over json because I'm not sure if their json has comment support which we've used a lot in the past).

@newoga their JSON does have comment support now

@mbrookes Not sure but didn't want to ruffle feathers!

I'm getting multiple warnings in the console:
Can't make class Card hot reloadable due to being read-only. To fix this you can try two solutions.
First, you can exclude files or directories (for example, /node_modules/) using 'exclude' option in
loader configuration. Second, if you are using Babel, you can enable loose mode for `es6.modules`
using the 'loose' option. See: http://babeljs.io/docs/advanced/loose/ and
http://babeljs.io/docs/usage/options/

@mbrookes Thanks, looking into

Squashed

Looks good here.

Looks good to me too :+1:

Awesome!

:tada:


Hockey Upload Size

When uploading via the hockey lane the file size is much larger than if i were to upload using the native mac hockey app.
    hockey(
      api_token: 'token',
      ipa: "MyApp.ipa",
      notify: '0',
      status: '1',
      teams: 'team',
      notes: changelog
    )

As far as I am aware it should be a small file size - is this something hockey is reporting incorrectly in its web UI or is there indeed extra build artefacts added to the hockey upload?
circled in red is the same version but uploaded through fastlane hockey

@ollieatkinson was the ipa created with fastlane in both cases ?

@xfreebird Yes, both created using fastlane - I uploaded the same IPA produced by gym :muscle:

could you download both ipa files and check the decompressed size of the binaries. It could be that the hockey desktop app repacks the ipa file with a better compression rate.

it seems like fastlane is bundling extra swift support files

vs Hockey

interesting that HockeyApp drops that folder. AFAIK SwfitSupport is needed for AppStore submission. I think that is why HockeyApp drops folder to save space on their servers, or a bug in their app.

Hm. OK - Is that something we would be able to strip for AdHoc deployment or do you think its better to leave them

I think it would be better to leave it, but it would work and without it. Not sure why Apple insists on that when submitting to AppStore.

@xfreebird It will be a build support file for the different iOS, you can compile swift 2 to run on iOS 7


What about docs

[ ] Create a docs folder
[ ] Create a new index.md document
[ ] Decide if we  want to go with sometime more complex


"Debug Assertion Failed!" when compiling method

Compiling or viewing this method causes a Microsoft Visual C++ Runtime Library error. I am running Windows 11 on Arm, so this might be an issue with the i386 emulation.

This is probably another case of #533, or is at least strongly related. There are some longstanding issues with the generation of the text maps used to remap from optimised method IPs to debug method IPs. As such it may potentially affect debugging, but otherwise can be ignored as it is not involved in normal execution.

As mentioned, I was using a debug version. Thanks again for your help.


chore: update issue templates

@yokuze @onebytegone @jimjenkins5 what do you think of adding these issue templates to our projects? These are a bit tuned towards our VideoJS projects (the MCVE examples, in particular). I'm thinking we use these across our VideoJS plugins, and then tweak that MCVE part so that a more generic version could be used across the rest of our FOSS repos.


Fix navbar alignment

@harikrishnan-annappilly
hola,
The issue is currently the right header navbar is at center.
I tried every method  i know to align it to right ,css inline style and bootstrap 5 flex fr.
Bring it back to the original position (right end) otoh try to bring the github logo to the center in mobile device view.
tia
TTD 🔢

[ ] Align nav to right end
[ ] Align github logo to the center (Mobile device)

well done my boy


[SR-15592] async function does return after a long delay (30s)

Previous ID
SR-15592

Radar
rdar://problem/86462682

Original Reporter
@dnadoba

Type
Bug

Status
Closed

Resolution
Invalid

Environment
Tested with macOS 12.1 and Xcode 13.1 and 13.2
Tested with an internal macOS 12 with an internal Xcode and nightly toolchain from 6. December 2021

Additional Detail from JIRA

Votes
0

Component/s
swift

Labels
Bug

Assignee
@ktoso

Priority
Medium

md5: af044e4e5b0ea6080858520963ff9731

Issue Description:
In the following test case testSimpleGet, print("failed") is executed but the return afterwards is sometimes never executed but most of the times executed after a delay of 30 seconds (observed through a breakpoint and print statement in the callee XCTAsyncTest). However, there should be no delay at all.
final class AsyncAwaitEndToEndTests: XCTestCase {
    func testSimpleGet() {
        #if compiler(>=5.5) && canImport(_Concurrency)
        guard #available(macOS 12.0, iOS 15.0, watchOS 8.0, tvOS 15.0, *) else { return }
        XCTAsyncTest {
            let client = makeDefaultHTTPClient()
            defer { XCTAssertNoThrow(try client.syncShutdown()) }
            let logger = Logger(label: "HTTPClient", factory: StreamLogHandler.standardOutput(label:))
            let request = HTTPClientRequest(url: "https://localhost:\(443)/get")

            guard let response = await XCTAssertNoThrowWithResult(
                try await client.execute(request, deadline: .now() + .seconds(0), logger: logger)
            ) else {
                print("failed")
                return
            }
        }
        #endif
    }
}

extension XCTestCase {
    @available(macOS 12, iOS 15, tvOS 15, watchOS 8, *)
    /// Cross-platform XCTest support for async-await tests.
    ///
    /// Currently the Linux implementation of XCTest doesn't have async-await support.
    /// Until it does, we make use of this shim which uses a detached `Task` along with
    /// `XCTest.wait(for:timeout:)` to wrap the operation.
    ///
    /// - NOTE: Support for Linux is tracked by https://bugs.swift.org/browse/SR-14403.
    /// - NOTE: Implementation currently in progress: https://github.com/apple/swift-corelibs-xctest/pull/326
    func XCTAsyncTest(
        expectationDescription: String = "Async operation",
        timeout: TimeInterval = 30,
        file: StaticString = #filePath,
        line: UInt = #line,
        function: StaticString = #function,
        operation: @escaping @Sendable () async throws -> Void
    ) {
        let expectation = self.expectation(description: expectationDescription)
        Task {
            do {
                try await operation()
            } catch {
                XCTFail("Error thrown while executing \(function): \(error)", file: file, line: line)
                Thread.callStackSymbols.forEach { print($0) }
            }
            print("fulfill")
            expectation.fulfill()
        }
        self.wait(for: [expectation], timeout: timeout)
    }
}

@available(macOS 12.0, iOS 15.0, watchOS 8.0, tvOS 15.0, *)
internal func XCTAssertNoThrowWithResult<Result>(
    _ expression: @autoclosure () async throws -> Result,
    file: StaticString = #file,
    line: UInt = #line
) async -> Result? {
    do {
        return try await expression()
    } catch {
        XCTFail("Expression did throw: \(error)", file: file, line: line)
        return nil
    }
}

The 30 seconds probably come from a XCTestCase.wait(for:timeout🙂 which we use to let the test fail if the closure given to XCTAsyncTest does not return after the given timeout.
This behaviour was observed while writing tests for swift-server/AsyncHTTPClient new async/await API. The test in its current form will fail (we try to execute a request without a running server and also set the deadline to .now) but should fail almost immediately and not after 30 seconds.
The full example can be found at https://github.com/dnadoba/async-http-client/tree/dn-async-await-bug-001
The test case is located at /Tests/AsyncHTTPClientTests/AsyncAwaitEndToEndTests.swift and test helpers at /Tests/AsyncHTTPClientTests/XCTest+AsyncAwait.swift

Thanks for closing!
I'm not able to transfer it to https://github.com/swift-server/async-http-client as it is part of another organisation. According to GitHub docs the repos need to be part of the same GitHub org.
Also I don't think it is important as the code has never actually landed in the repo. It was just an issue I have hit while developing the tests.


Hosting Bundle LTS Installer Permalink

There is a permalink to the current Hosting Bundle Installer.
Is there one for the latest LTS version? That would be a lot more useful since a lot of enterprises try to stay LTS on production applications. If so it would be wonderful to have it documented here as well.

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

ID: 65973393-2cb9-a656-01b8-7963a7a40b39
Version Independent ID: 22e2323b-18c3-ad2b-174c-84fbf642715e
Content: Hosting Bundle
Content Source: aspnetcore/host-and-deploy/iis/hosting-bundle.md
Product: aspnet-core
Technology: aspnetcore-hostdeploy
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

It's easy to get to from the link provided here in the doc

@Rick-Anderson I am only seeing the link to latest which is .net 7. Is there one for LTS which is .net 6?


fix example

Coverage remained the same at 95.0% when pulling 9be4326cc32dfdede47cf397612a884abbc1d613 on zemirco:patch-1 into 9eb347845998ca6a0cc2e22366bbc87c02617f22 on lipp:master.


Force patch issuer metadata for auth0 endpoint even if the issuer domain is not auth0.com

This ticket https://github.com/magda-io/magda-auth-oidc/issues/6 implemented logout workflow with auto patching for auth0.com.
However, currently, the auth0.com specific feature only available when the issuer domain contains auth0.com.
This ticket is about adding a new config option that allows explicitly turn on the patching behaviour for auth0 endpoint with custom domains.

closed via PR: https://github.com/magda-io/magda-auth-oidc/pull/15


Adding a custom class to the table

Adding this custom class wrapper will break the lines of code so the table no longer breaks out of the center content column.

Hi @adkinn, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Adam Kinney). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

@adkinn : Thanks for your contribution to the Azure documentation! The author, @christopheranderson, has been notified to review your proposed change.

#sign-off


Upgrade OpenSSL to latest 1.0.2 release due to vulnerability CVE-2018-0732

There were some vulnerability fixes since OpenSSL version 1.0.2l, see https://www.openssl.org/news/vulnerabilities-1.0.2.html.
I highly suggest to upgrade to the latest 1.0.2 version.

This is even more moot now thanks to #139.


Migrate the github workflow dependencies-update to tekton

Signed-off-by: Romain Arnaud<EMAIL_ADDRESS>Tested successfully when a PR is already opened and when a PR needs to be opened.

/retest

/lgtm


[AJ-789] hide the data tab in azure prod

Hiding the data tab for azure until release.
Azure dev:

GCP dev:

Azure prod (set isProd to true in dev.json):

GCP prod (set isProd to true in dev.json)

Sorry, I didn't bother looking at the failing integration tests. @jordansafer, you need to update the workspace-dashboard integration test so it does not expect that tab to be present (if not prod).


Enable image tests on aarch64

We're currently not running any tests on aarch64 which we should really begin to do. We can use the c6g ec2 instances to do it.
My notes:

We can boot test AMIs on AWS.
We cannot boot test qcow2 images because c6g instances (except for metal) don't support (nested) virtualization.

Testing on other alt arches would be nice as well but aarch64 is a good and easy start.

Was this done via #844?

@jrusz I think this is done, do you agree ? If so we can close the issue.


[OTHER] add hover effect on Github and theme icons

What would you like to share or ask?
Having hover effect on icons in a website makes it more interactive for user, as of now we don't have any hover effect on Github and Theme icons.
Specific requirements
Add text-violet-500 this  color when hovered on Github or theme icons.
Screenshots

Additional information
No response

is the issue still open? If it is open can you assign it to me

@srujith-reddy Sorry🙂 PR is already raised, you can look onto other open issues


Added Tranditional Chinese localization

please pull from staging instead of new-design

@nadirabbas thanks, I opened another PR.


Project Test Case 3 - servers not resting

Hi all, would anyone happen to know where I went wrong for my project test case 3? It appears that my server is not resting as it is supposed to for customer 10. Similarly, on 3.in, my server is supposed to rest after serving customer 5 but he serves customer 6 right away. Would greatly appreciate it if you can help to see where the problem is. Thanks!!!

//Execute for Wait/Queue class

//Execute for Done class

Try having the Servers rest in the Done event class.

Could your code be calling the rest time Supplier multiple times?

Could your code be calling the rest time Supplier multiple times?

Hint: You can call it with get() like in Lab 3.

Hi! I had the exact same problem with test case 3 line 38. I solved it by tweaking the logic in my Wait/Waiting class, at the part that returns a new Serve event. Hope it helps!

okay solved alr. thanks!!

hi how did you solve this?

@caleblowy create a new rest class to update server status, create new servingStatus attribute in Server, false by default. when a customer is served this changes to true, when a server is done this status does not change until the server is DoneResting (event executed) then servingStatus changes to false. in wait event, customer is only served when servingStatus is false.


Testing exact compressed data lengths is too brittle

Since compression libraries do not in general attempt to preserve the exact same compressed output for each compressed input across compatible releases, testing exact compressed data lengths is brittle – too brittle, in my opinion.
This is visible in current main, 1d959cfd8abadaa1fb1bbf05d9c37b0596ac6e48 since the release of lz4 1.25.
---- tests::lz4::roundtrip_compress_via_slice_decompress_via_vector stdout ----
thread 'tests::lz4::roundtrip_compress_via_slice_decompress_via_vector' panicked at src/lib.rs:106:5:
assertion `left == right` failed
  left: 329646
 right: 303278
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

---- tests::lz4::roundtrip_compress_via_slice_decompress_via_slice stdout ----
thread 'tests::lz4::roundtrip_compress_via_slice_decompress_via_slice' panicked at src/lib.rs:106:5:
assertion `left == right` failed
  left: 329646
 right: 303278

---- tests::lz4::roundtrip_compress_via_vector_decompress_via_slice stdout ----
thread 'tests::lz4::roundtrip_compress_via_vector_decompress_via_slice' panicked at src/lib.rs:106:5:
assertion `left == right` failed
  left: 329646
 right: 303278

---- tests::lz4::roundtrip_compress_via_vector_decompress_via_vector stdout ----
thread 'tests::lz4::roundtrip_compress_via_vector_decompress_via_vector' panicked at src/lib.rs:106:5:
assertion `left == right` failed
  left: 329646
 right: 303278

failures:
    tests::lz4::roundtrip_compress_via_slice_decompress_via_slice
    tests::lz4::roundtrip_compress_via_slice_decompress_via_vector
    tests::lz4::roundtrip_compress_via_vector_decompress_via_slice
    tests::lz4::roundtrip_compress_via_vector_decompress_via_vector

In this case,
diff --git a/src/lib.rs b/src/lib.rs
index 8581669..2460462 100644
--- a/src/lib.rs
+++ b/src/lib.rs
@@ -103,7 +103,7 @@ mod tests {
     test_variant!(zstd, compressed_len = 4990, None);

     #[cfg(feature = "lz4")]
-    test_variant!(lz4, compressed_len = 303_278, None);
+    test_variant!(lz4, compressed_len = 329_646, None);

     #[cfg(feature = "blosc2")]
     test_variant!(blosc2, compressed_len = 791_923);

would fix the regression, but perhaps it would be better to omit
https://github.com/cramjam/libcramjam/blob/1d959cfd8abadaa1fb1bbf05d9c37b0596ac6e48/src/lib.rs#L52
altogether.

Closed with https://github.com/cramjam/libcramjam/pull/8/commits/81afd2eea10f693bafcb59295814aac6b64a4b73 in #8


Compaction memory optimization

Enhancement
In a large wide table scenario(may be 10800 columns), a large number of Column Readers will occupy a lot of memory during load and compaction.
The main tasks are

[x] Share data field between ColumnReader
[ ] ColumnReader Cache
[ ] Outdata Rowset early release

Experimental setup
Table contains 10800 columns, and divided into 100 bucket.
Create 100 broker load tasks, each task load 1 file contains 10,000 lines of data(1.2G).
Memory Before optimization
The peak of rss is about 81.7G, the peak of tablet meta memory is 34.6G, the peak of column_reader_index_mem is 17.8G, and the peak of column_reader_meta_mem is 16.8G.

Memory after sharing data field between ColumnReader optimiztion #4875
Rss peaks at about 74.2G, tablet meta memory peaks at 27.3G, column_reader_index_mem peaks at 15.3G, and column_reader_meta_mem peaks at 11.9G, the memory of column_reader_meta_mem significantly lower than before.

In the process of column reader cache design, it is found that it may have some negative effects on query performance. On the other hand, the early release of Rowsets has been able to reduce the column reader meta memory usage to a great extent, so I think there is no need to do column reader cache optimization.


invalid option: --env when trying to fastlane deliver download_metadata --env app1

New Issue Checklist

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

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

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

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

Key
Value

OS
10.12.4

Ruby
2.0.0

Bundler?
false

Git
git version 2.11.0 (Apple Git-81)

Installation Source
/usr/local/bin/fastlane

Host
Mac OS X 10.12.4 (16E195)

Ruby Lib Dir
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib

OpenSSL Version
OpenSSL 0.9.8zc 19 Mar 2015

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

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

Xcode Version
8.3.1

System Locale

Error

No Locale with UTF8 found 🚫

fastlane files:
`./fastlane/Fastfile`
# Customise this file, documentation can be found here:
# https://github.com/fastlane/fastlane/tree/master/fastlane/docs
# All available actions: https://docs.fastlane.tools/actions
# can also be listed using the `fastlane actions` command

# Change the syntax highlighting to Ruby
# All lines starting with a # are ignored when running `fastlane`

# If you want to automatically update fastlane if a new version is available:
# update_fastlane

# This is the minimum version number required.
# Update this, if you use features of a newer version
fastlane_version "2.14.2"

default_platform :ios

platform :ios do
  before_all do
    # Configuring Slack webhook for #7nxt_notifications
     ENV["SLACK_URL"] = "https://hooks.slack.com/services/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"
     ENV["FASTLANE_PASSWORD"] = "PasswordPo1icyAtStanwoodRu1ez"
    #cocoapods
  end

  desc "Runs all the tests"
  lane :test do
    scan
  end

  desc "Submit a new Beta Build to Apple TestFlight"
  lane :testenv do
    UI.message([ENV["DLV_SCHEME"], "Successfully Uploaded"].join(': '))

  end

  desc "Submit a new Beta Build to Apple TestFlight"
  desc "This will also make sure the profile is up to date"
  lane :beta do
    # match(type: "appstore") # more information: https://codesigning.guide
    gym(scheme: ENV["DLV_SCHEME"]) # Build your app - more options available
    pilot

    # sh "your_script.sh"
    # You can also use other beta testing services here (run `fastlane actions`)
  end

desc "Snapshot and uploading to iTunes"
lane :screenshots do
  #snapshot
  #frameit(gold: true, path: ENV["DLV_SCS_PATH")
  deliver(
    force: true,
    metadata_path: ENV["DLV_MTD_PATH"],
    screenshots_path: ENV["DLV_SCS_PATH"]
  )
end

  desc "Deploy a new version to the App Store"
  lane :release do
    # match(type: "appstore")
    # snapshot
    gym(scheme: ENV["DLV_SCHEME"]) # Build your app - more options available
    deliver(force: true)
    # frameit
  end

  desc "Attachment"
  lane :attachment do

  end

  # You can define as many lanes as you want

  after_all do |lane|
    # This block is called, only if the executed lane was successful

    slack(
       message: "Successfully deployed new App Update, with attachment_properties",
       payload: {  # Optional, lets you specify any number of your own Slack attachments.
         "Build Date" => Time.new.to_s
       },
       attachment_properties: {
         image_url: "file://Users/talzion/Documents/Stanwood/Mach_Dich_Krass_Swift/fastlane/screenshot.jpg",
         fields: [{
           title: "Attachment",
           value: "Frameit Screenshots",
           short: true
           }]
       }
     )
  end

  error do |lane, exception|
     slack(
       message: exception.message,
       success: false
     )
  end
end

# More information about multiple platforms in fastlane: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Platforms.md
# All available actions: https://docs.fastlane.tools/actions

# fastlane reports which actions are used
# No personal data is recorded. Learn more at https://github.com/fastlane/enhancer

`./fastlane/Appfile`
app_identifier ENV["DLV_APP_IDENTIFIER"] # The bundle identifier of your app
apple_id ENV["DLV_ITC_USERNAME"] # Your Apple email address

team_id "[[DEV_PORTAL_TEAM_ID]]"  # Developer Portal Team ID
itc_team_name ENV["DLV_ITC_TEAM_NAME"]

# you can even provide different app identifiers, Apple IDs and team names per lane:
# More information: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Appfile.md

fastlane gems

Gem
Version
Update-Status

fastlane
2.28.3
💥 Check failed

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

slack-notifier
1.5.1

CFPropertyList
2.3.3

claide
1.0.1

colored2
3.1.2

nanaimo
0.2.3

xcodeproj
1.4.4

rouge
1.11.1

xcpretty
0.2.4

terminal-notifier
1.6.3

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.5.0

babosa
1.0.2

colored
1.2

highline
1.7.8

commander-fastlane
4.4.4

faraday
0.9.2

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20160615

http-cookie
1.0.2

faraday-cookie_jar
0.0.6

gh_inspector
1.0.2

mini_magick
4.5.1

multi_json
1.12.1

multi_xml
0.5.5

security
0.1.3

xcpretty-travis-formatter
0.0.4

dotenv
2.1.1

bundler
1.12.5

faraday_middleware
0.10.0

json
2.0.2

excon
0.51.0

rubyzip
1.2.0

plist
3.2.0

fastimage
2.0.0

addressable
2.4.0

terminal-table
1.6.0

generated on: 2017-04-25

I have found a solution by setting up a download_metadata lane and executing a shell script file.
the fastlane lane
  desc "Downloading Metadata"
  lane :download_data do
    sh ENV["DLV_DOWNLOAD_SCRIPT_PATH"]
  end

The app1 .env file, i'e, .env.app1 contains the shell script file path.
DLV_DOWNLOAD_SCRIPT_PATH=bash ./scripts/download_metadata_app1.sh

The .sh file contains a couple of commands to download the metadata and screenshots
#!/usr/bin/env bash

echo "=========== Downloading App1 Metadata =========="
fastlane deliver download_metadata  --metadata_path metadata/app1

echo "=========== Downloading App1 Screenshots =========="
fastlane deliver download_screenshots --screenshots_path screenshots/app1

Executing the lane
fastlane download_data --env app1


RWA 2181 added new secrets for replica

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/RWA-2181
Change description
Added secrets for replica database
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

don't need this any more as done elsewhere


Why does my loss decrease unstabley when I train the net with 500 patches?  Because the data is too little?

I1019 16:56:37.955636  8822 solver.cpp:305] Learning Rate Policy: waifu2x
I1019 16:56:37.956248  8822 solver.cpp:362] Iteration 0, Testing net (#0)
I1019 16:57:55.966459  8822 solver.cpp:429]     Test net output #0: loss = 0.0290823 (* 1 = 0.0290823 loss)
I1019 16:58:00.868696  8822 solver.cpp:253] Iteration 0, loss = 0.0311817
I1019 16:58:00.868749  8822 solver.cpp:269]     Train net output #0: loss = 0.0311817 (* 1 = 0.0311817 loss)
I1019 16:58:00.868759  8822 sgd_solver.cpp:116] Iteration 0, lr = 0.000249999
I1019 17:04:51.740345  8822 solver.cpp:253] Iteration 100, loss = 0.040274
I1019 17:04:51.740445  8822 solver.cpp:269]     Train net output #0: loss = 0.040274 (* 1 = 0.040274 loss)
I1019 17:04:51.740456  8822 sgd_solver.cpp:116] Iteration 100, lr = 0.000249924
I1019 17:12:32.962102  8822 solver.cpp:253] Iteration 200, loss = 0.0449925
I1019 17:12:33.355516  8822 solver.cpp:269]     Train net output #0: loss = 0.0449925 (* 1 = 0.0449925 loss)
I1019 17:12:33.355578  8822 sgd_solver.cpp:116] Iteration 200, lr = 0.000249849
I1019 17:19:23.685695  8822 solver.cpp:253] Iteration 300, loss = 0.0448228
I1019 17:19:23.849676  8822 solver.cpp:269]     Train net output #0: loss = 0.0448229 (* 1 = 0.0448229 loss)
I1019 17:19:23.849730  8822 sgd_solver.cpp:116] Iteration 300, lr = 0.000249774
I1019 17:26:06.037768  8822 solver.cpp:253] Iteration 400, loss = 0.0264396
I1019 17:26:06.037914  8822 solver.cpp:269]     Train net output #0: loss = 0.0264396 (* 1 = 0.0264396 loss)
I1019 17:26:06.037925  8822 sgd_solver.cpp:116] Iteration 400, lr = 0.0002497
I1019 17:32:44.985211  8822 solver.cpp:479] Snapshotting to binary proto file /home/yuyadan/caffe/examples/waifu2x_trainning_cpp/waifu2x_train_iter_500.caffemodel
I1019 17:32:45.585852  8822 sgd_solver.cpp:290] Snapshotting solver state to binary proto file /home/yuyadan/caffe/examples/waifu2x_trainning_cpp/waifu2x_train_iter_500.solverstate
I1019 17:32:49.843364  8822 solver.cpp:253] Iteration 500, loss = 0.0255457
I1019 17:32:49.843487  8822 solver.cpp:269]     Train net output #0: loss = 0.0255457 (* 1 = 0.0255457 loss)
I1019 17:32:49.843502  8822 sgd_solver.cpp:116] Iteration 500, lr = 0.000249625
I1019 17:39:36.430296  8822 solver.cpp:253] Iteration 600, loss = 0.037344
I1019 17:39:36.430485  8822 solver.cpp:269]     Train net output #0: loss = 0.0373441 (* 1 = 0.0373441 loss)
I1019 17:39:36.430498  8822 sgd_solver.cpp:116] Iteration 600, lr = 0.00024955
I1019 17:46:21.068217  8822 solver.cpp:253] Iteration 700, loss = 0.0357204
I1019 17:46:21.068420  8822 solver.cpp:269]     Train net output #0: loss = 0.0357205 (* 1 = 0.0357205 loss)
I1019 17:46:21.068434  8822 sgd_solver.cpp:116] Iteration 700, lr = 0.000249475
I1019 17:53:04.696640  8822 solver.cpp:253] Iteration 800, loss = 0.0162388
I1019 17:53:04.696722  8822 solver.cpp:269]     Train net output #0: loss = 0.0162389 (* 1 = 0.0162389 loss)
I1019 17:53:04.696733  8822 sgd_solver.cpp:116] Iteration 800, lr = 0.000249401
I1019 17:59:45.030585  8822 solver.cpp:253] Iteration 900, loss = 0.0165265
I1019 17:59:45.030730  8822 solver.cpp:269]     Train net output #0: loss = 0.0165266 (* 1 = 0.0165266 loss)
I1019 17:59:45.030741  8822 sgd_solver.cpp:116] Iteration 900, lr = 0.000249326
I1019 18:06:30.505097  8822 solver.cpp:479] Snapshotting to binary proto file /home/yuyadan/caffe/examples/waifu2x_trainning_cpp/waifu2x_train_iter_1000.caffemodel
I1019 18:06:30.517384  8822 sgd_solver.cpp:290] Snapshotting solver state to binary proto file /home/yuyadan/caffe/examples/waifu2x_trainning_cpp/waifu2x_train_iter_1000.solverstate
I1019 18:06:30.522547  8822 solver.cpp:362] Iteration 1000, Testing net (#0)
I1019 18:07:46.129395  8822 solver.cpp:429]     Test net output #0: loss = 0.0365902 (* 1 = 0.0365902 loss)
I1019 18:07:50.044318  8822 solver.cpp:253] Iteration 1000, loss = 0.032317
I1019 18:07:50.044371  8822 solver.cpp:269]     Train net output #0: loss = 0.0323171 (* 1 = 0.0323171 loss)
I1019 18:07:50.044381  8822 sgd_solver.cpp:116] Iteration 1000, lr = 0.000249252
I1019 18:14:30.554181  8822 solver.cpp:253] Iteration 1100, loss = 0.0319682
I1019 18:14:30.554280  8822 solver.cpp:269]     Train net output #0: loss = 0.0319683 (* 1 = 0.0319683 loss)
I1019 18:14:30.554291  8822 sgd_solver.cpp:116] Iteration 1100, lr = 0.000249177
I1019 18:21:23.975481  8822 solver.cpp:253] Iteration 1200, loss = 2.0083e-05
I1019 18:21:23.975605  8822 solver.cpp:269]     Train net output #0: loss = 2.0218e-05 (* 1 = 2.0218e-05 loss)
I1019 18:21:23.975615  8822 sgd_solver.cpp:116] Iteration 1200, lr = 0.000249103
I1019 18:28:05.186214  8822 solver.cpp:253] Iteration 1300, loss = 1.34425e-05
I1019 18:28:05.186306  8822 solver.cpp:269]     Train net output #0: loss = 1.35886e-05 (* 1 = 1.35886e-05 loss)
I1019 18:28:05.186317  8822 sgd_solver.cpp:116] Iteration 1300, lr = 0.000249028
I1019 18:35:01.660615  8822 solver.cpp:253] Iteration 1400, loss = 0.0427325
I1019 18:35:01.660747  8822 solver.cpp:269]     Train net output #0: loss = 0.0427326 (* 1 = 0.0427326 loss)
I1019 18:35:01.660758  8822 sgd_solver.cpp:116] Iteration 1400, lr = 0.000248954
I1019 18:41:42.918938  8822 solver.cpp:479] Snapshotting to binary proto file /home/yuyadan/caffe/examples/waifu2x_trainning_cpp/waifu2x_train_iter_1500.caffemodel
I1019 18:41:42.925552  8822 sgd_solver.cpp:290] Snapshotting solver state to binary proto file /home/yuyadan/caffe/examples/waifu2x_trainning_cpp/waifu2x_train_iter_1500.solverstate
I1019 18:41:47.056991  8822 solver.cpp:253] Iteration 1500, loss = 0.0451393
I1019 18:41:47.057047  8822 solver.cpp:269]     Train net output #0: loss = 0.0451395 (* 1 = 0.0451395 loss)
I1019 18:41:47.057057  8822 sgd_solver.cpp:116] Iteration 1500, lr = 0.000248879
I1019 18:48:31.680407  8822 solver.cpp:253] Iteration 1600, loss = 0.0348224
I1019 18:48:31.680615  8822 solver.cpp:269]     Train net output #0: loss = 0.0348226 (* 1 = 0.0348226 loss)
I1019 18:48:31.680629  8822 sgd_solver.cpp:116] Iteration 1600, lr = 0.000248805
I1019 18:55:14.063782  8822 solver.cpp:253] Iteration 1700, loss = 0.0411839
I1019 18:55:14.063937  8822 solver.cpp:269]     Train net output #0: loss = 0.0411841 (* 1 = 0.0411841 loss)
I1019 18:55:14.063948  8822 sgd_solver.cpp:116] Iteration 1700, lr = 0.000248731
I1019 19:02:05.532102  8822 solver.cpp:253] Iteration 1800, loss = 0.0407743
I1019 19:02:05.532209  8822 solver.cpp:269]     Train net output #0: loss = 0.0407745 (* 1 = 0.0407745 loss)
I1019 19:02:05.532230  8822 sgd_solver.cpp:116] Iteration 1800, lr = 0.000248657

It seems using caffe. I am not familiar with caffe and I don't know about your code.
Maybe code has a bug or some hyperparameter is inappropriate. I don't have advice for this.


ec2_instance - Instance does not require IMDS access to require a token

https://aquasecurity.github.io/tfsec/v0.61.3/checks/aws/ec2/enforce-http-token-imds/#possible-impact
Do not think there's any cost behind this one

Should always be true

#28


getting The method 'ancestorWidgetOfExactType' isn't defined for the class 'BuildContext'.

Describe the bug
Running "flutter pub get" in safehandsfordoc... Launching lib\main.dart on Chrome in debug mode... lib\main.dart /D:/flutter/.pub-cache/hosted/pub.dartlang.org/overlay_support-1.0.5/lib/src/overlay.dart:156:19: Error: The method 'ancestorWidgetOfExactType' isn't defined for the class 'BuildContext'.
'BuildContext' is from 'package:flutter/src/widgets/framework.dart' ('/D:/flutter/packages/flutter/lib/src/widgets/framework.dart'). Try correcting the name to the name of an existing method, or defining a method named 'ancestorWidgetOfExactType'. if (context.ancestorWidgetOfExactType(OverlaySupport) != null) { ^^^^^^^^^^^^^^^^^^^^^^^^^
/D:/flutter/.pub-cache/hosted/pub.dartlang.org/overlay_support-1.0.5/lib/src/overlay_entry.dart:17:37: Error: The method 'ancestorWidgetOfExactType' isn't defined for the class 'BuildContext'.
'BuildContext' is from 'package:flutter/src/widgets/framework.dart' ('/D:/flutter/packages/flutter/lib/src/widgets/framework.dart'). Try correcting the name to the name of an existing method, or defining a method named 'ancestorWidgetOfExactType'. final animatedOverlay = context.ancestorWidgetOfExactType(_AnimatedOverlay);
                         ^^^^^^^^^^^^^^^^^^^^^^^^^

/D:/flutter/.pub-cache/hosted/pub.dartlang.org/overlay_support-1.0.5/lib/src/theme.dart:53:20: Error: The method 'inheritFromWidgetOfExactType' isn't defined for the class 'BuildContext'.
'BuildContext' is from 'package:flutter/src/widgets/framework.dart' ('/D:/flutter/packages/flutter/lib/src/widgets/framework.dart'). Try correcting the name to the name of an existing method, or defining a method named 'inheritFromWidgetOfExactType'. return context.inheritFromWidgetOfExactType(OverlaySupportTheme) as OverlaySupportTheme;
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Failed to compile application. Exited (sigterm)
To Reproduce
Steps to reproduce the behavior:

just added in pubyaml
returned OverlaySupport
used  showSimpleNotification

Version (please complete the following information):

Flutter Version: Flutter 1.26.0-17.2
OS:  WEB
OverlaySupport Version : ^1.0.5

Solution possibly here: https://api.flutter.dev/flutter/widgets/BuildContext/ancestorWidgetOfExactType.html

It seems that new flutter beta version has removed the depcreated function such as inheritFromWidgetOfExactType.
Does 1.2.0-nullsafety.0 works for your project ?  if it works , maybe I don’t need to release a new version based on the 1.0.5

Solution possibly here: https://api.flutter.dev/flutter/widgets/BuildContext/ancestorWidgetOfExactType.html

this worked thank you so much for the quick response @fengwang  :)
@boyan01  thank you for response and for this amazing package

For dev who did not migrated to nullsafety. please consider use : 1.0.5-hotfix1
overlay_support: ^1.0.5-hotfix1


1.1.2 Craft 1st Interview Questions

Questions that the group crafted for 1st round of interview with the Client.


Is it Updated for Laravel 8?

Can i use this for my laravel 8 app? thanks

It should work. If not, let me know.

It should work. If not, let me know.

Compatibility for Laravel 8 onwards added See PR: https://github.com/woenel/prpcmblmts/pull/6


Add wrapping error and move stacktrace to extensions

To provide at least a little more info, wrap the fetch function with a message to indicate that we had an issue calling the url, rather than is ambiguous TypeError that we get today

I have remove the options from the log for now

@mayakoneval Is this something we can still merge?


Add some formatting guidelines

With people contributing, everyones going to format the code slightly differently. I think adding something as simple as a .editorconfig file to the repo could make things a little more consistent.
There's also the option of adding some git hooks, but this would be a little more complicated.
An example .editorconfig could be something like:
# EditorConfig is awesome: https://EditorConfig.org

# top-most EditorConfig file
root = true

[*]
charset = utf-8
end_of_line = lf
indent_size = 4
indent_style = space
insert_final_newline = true
trim_trailing_whitespace = true

# Batch Files
[*.{cmd,bat}]
end_of_line = crlf

# JSON Files
[*.{json,json5,webmanifest}]
indent_size = 2

# YAML Files
[*.{yml,yaml}]
indent_size = 2

or we could set up something like pre-commit hook, but this will add some more dependencies to the project. Maybe a github workflow?

Good point. I'll think about the best way to do this.

Closed in favor of https://github.com/Gabisonfire/torrentio-scraper-sh/issues/36


Bump xamlTools to 17.12.35305.252

This is from the VS build for Friday, 9/06. Also updated CHANGELOG.

/azp run dotnet.vscode-csharp


Docs and type improvments

Use type script types inside js-docs
Add return type to fineOne method

Well done! 💯


Import error. No query results for model [App\User]

Laravel Version: 5.8
Adldap2-Laravel Version: ^6.0
PHP Version: 7.2.11
LDAP Type: ActiveDirectory

Description:
Hi,
I'm having an issue with my import / Sync. Most all of my users import from AD just fine however some of them say that they imported but are not. Looking at the logs it show this...
[2020-03-25 09:14:01] production.INFO: User 'User, Some' is being imported.
[2020-03-25 09:14:01] production.INFO: User 'User, Some' is being synchronized.
[2020-03-25 09:14:01] production.INFO: User 'User, Some' has been successfully synchronized.
[2020-03-25 09:14:01] production.ERROR: Unable to import user User, Some. No query results for model [App\User].
If I try to import a single user that return this error I get the same thing...
| User, Some | 99999     |<EMAIL_ADDRESS>|
+--------------------------+--------------+--------------------+
Would you like these users to be imported / synchronized? (yes/no) [yes]:

y

1/1 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓] 100%
Successfully imported / synchronized 0 user(s).
So out of lets say 1000 user 95% of them import just fine, the other 5% return this error. No query results for model [App\User]. Any idea why this is?

Hi @northify,
That's strange... Are there any exceptions shown in your log after you run the single user import?

Hi @stevebauman
Thanks for the quick reply.
No, no exceptions. Only the importing being logged.
So to get the user in my DB I have had to manually insert it. After I manually insert it and then do an import / sync it finds it syncs just fine. Really weird.

Can you post your Eloquent App\User.php model code as well as your users database migration so I know what columns you're using?

Oh that's allot! Pretty big application.
My App\User.php code base is very large with many trait files attached.
Also I have lots of migrations for the users table.
Here are the fillable on my User model
    protected $fillable = [
        'from_ad',
        'new_user_account_id',
        'company_id',
        'location_id',
        'title_id',
        'department_id',
        'manager_id',
        'supervisor_id',
        'employee_type',
        'agency_id',
        'account_expires',
        'username',
        'name',
        'first_name',
        'last_name',
        'distinguished_name',
        'description',
        'email',
        'phone_primary',
        'password',
        'status',
        'user_status',
        'app_admin',
        'default_approver',
        'apps_imported',

    ];

My ldap_auth
'sync_attributes' => [

        'from_ad'               => true,
        'company_id'            => 'company',
        'location_id'           => 'physicaldeliveryofficename',
        'title_id'              => 'title',
        'department_id'         => 'department',
        'manager_id'            => 'manager',
        'supervisor_id'         => 'assistant',
        'employee_type'         => 'employeetype',
        'status'                => 'useraccountcontrol',
        'account_expires'       => 'accountexpires',
        'username'              => 'samaccountname',
        'name'                  => 'cn',
        'first_name'            => 'givenname',
        'last_name'             => 'sn',
        'email'                 => 'mail',
        'phone_primary'         => 'telephonenumber',
        'description'           => 'description',
        'distinguished_name'    => 'distinguishedname',
        'expirable'             => 'employeetype',
        'user_status'           => 'comment',

    ],

Will this help or need all the App\User.php and traits?

Oh that's allot! Pretty big application.

Yeah it may be asking to post a lot for sure 😅
I may need to see traits - the reason I'm asking is because your Eloquent model is for some reason throwing this exception that you've seen: No query results for model [App\User]
Do you traits perform any findOrFails on your App\User model before it saves to the database?

Do you maybe hook into the User::saving Eloquent event anywhere in your application as well?

Here is my ImportTraits.php. I dont have any findOrFails. I do lots of mutate fuctions.
Let me check on the events.
<?php

namespace App\Traits\UserModel;

use App\Company;
use App\Location;
use App\Title;
use App\Department;

trait ImportTraits
{
    /**
     * When a user is imported from AD, mutate the users
     * company name to the correct company id
     */
    public function setCompanyIdAttribute($value)
    {
        if ($this->preventCompanyIdAttrSet) {
            $this->attributes['company_id'] = $value;
        }else{
            // Account for JKES hack!
            if($value == 'JKES'){
                $this->attributes['company_id'] = 12;
            }else{
                $company = Company::where('company_acronym', $value)->first();
                $this->attributes['company_id'] = $company->id;
            }

        }

    }

    /**
     * When a user is imported from AD, mutate the users
     * location name to the correct location id
     */
    public function setLocationIdAttribute($value)
    {
        // If the imported user has a location set
        if(isset($value)){
            // Match the imported location with the location in local database
            $location = Location::where('location_name', $value)
                                ->where('company_id', $this->company_id)
                                ->first();
            if(isset($location->id)){
                $this->attributes['location_id'] = $location->id;
            }else{
                // If Location does not exist, create it
                $location = new \App\Location();
                $location->company_id = $this->company_id;
                $location->location_name = $value;
                $location->save();
            }

        }

    }

    /**
     * When a user is imported from AD, mutate the users
     * title name to the correct title id
     */
    public function setTitleIdAttribute($value)
    {

        // If the imported user has a title set
        if(isset($value)){
            // Match the imported title with the title in local database
            $title = Title::where('title_name', $value)
                            ->where('company_id', $this->company_id)
                            ->first();
            if(isset($title->id)){
                $this->attributes['title_id'] = $title->id;
            }else{
                // If Title does not exist, create it
                $title = new \App\Title();
                $title->company_id = $this->company_id;
                $title->title_name = $value;
                $title->save();
            }

        }

    }

    /**
     * When a user is imported from AD, mutate the users
     * department name to the correct department id
     */
    public function setDepartmentIdAttribute($value)
    {

        // If the imported user has a department set
        if(isset($value)){
            // Match the imported department with the department in local database
            $department = Department::where('department_name', $value)
                            ->where('company_id', $this->company_id)
                            ->first();
            if(isset($department->id)){
                $this->attributes['department_id'] = $department->id;
            }else{
                // If Department does not exist, create it
                $department = new \App\Department();
                $department->company_id = $this->company_id;
                $department->department_name = $value;
                $department->save();
            }

        }

    }

    /**
     * When a user is imported from AD, mutate the users
     * manager name to the correct manager id
     */
    public function setManagerIdAttribute($value)
    {
        if ($this->preventManagerIdAttrSet) {
            $this->attributes['manager_id'] = $value;
        }else{
            if(isset($value)){
                // Match the imported distinguishedname with the distinguished_name in local database
                $manager = $this->where('distinguished_name', $value)->first();

                // Check if manager field is set
                if(isset($manager)){
                    $this->attributes['manager_id'] = $manager->id;
                }else{
                    $this->attributes['manager_id'] = null;
                }
            }
        }
    }

    /**
     * When a user is imported from AD, mutate the users
     * supervisor name to the correct manager id
     */
    public function setSupervisorIdAttribute($value)
    {
        if ($this->preventSupervisorIdAttrSet) {
            $this->attributes['supervisor_id'] = $value;
        }else{
            if(isset($value)){
                // Match the imported distinguishedname with the distinguished_name in local database
                $supervisor = $this->where('distinguished_name', $value)->first();

                // Check if supervisor field is set
                if(isset($supervisor)){
                    $this->attributes['supervisor_id'] = $supervisor->id;
                }else{
                    $this->attributes['supervisor_id'] = null;
                }
            }
        }
    }

    /**
     * When a user is imported from AD, mutate the users status
     * 512 identifies an enabled user in AD
     * 514 identifies a disabled user in AD
     */
    public function setStatusAttribute($value)
    {
        if ($this->preventStatusAttrSet) {
            $this->attributes['status'] = $value;
        }else{
            if(isset($value)){
                if($value == 512) {
                    $this->attributes['status'] = 'Enabled';
                }elseif($value == 514) {
                    $this->attributes['status'] = 'Disabled';
                }
            }
        }
    }

    /**
     * Set expirable to true if account employee_type is C, V, or A
     */
    public function setExpirableAttribute($value)
    {
        if ($this->preventExpirableAttrSet) {
            $this->attributes['expirable'] = $value;
        }else{
            if(isset($value)){
                if($value == 'C' || $value == 'V' || $value == 'A') {
                    $this->attributes['expirable'] = true;
                }elseif($value == 'F') {
                    $this->attributes['expirable'] = false;
                }
            }
        }

    }

}

Yup everything looks fine in your trait... Maybe do a global search for firstOrFail or findOrFail in your application to see if there's anything that could generate the exception.
Since this only occurs on some users and not others, it seems there's some logic in your application potentially throwing it.

Ok was just about to send you my events on import and I do have firstOrFail on all of them.
I have 3 listeners that fire on the import event. All do the same kind of thing. This one associates application model to the user model
public function handle(Imported $event)
    {
        // Get local user: After import, match with user->username in local db
        $user = User::whereUsername($event->user->getAccountName())->firstOrFail();
        // Get all applications
        $applications = Application::get();
            // Check if user has not already been imported
            if($user->apps_imported == false){
                // Get user company
                $companyId = $user->company_id;
                // Attach each company application to the imported user
                foreach($applications as $application){
                    if($companyId == $application->company_id){
                        $user->applications()->attach($application);
                    }
                }
                // Set the app_imported to true
                $user->apps_imported = true;
                // Save user
                $user->save();
            }
            // Log import action
            Log::info("Adding user '{$event->user->getCommonName()}' applications");

    }

Okay, can you disable the listeners and see if the issue persists when importing?

OK I think I found the issue.
Disabling the listeners and importing gave me this.
It seems because I'm only accounting some of the useraccountcontrol status codes. It looks like if an account has a status code I'm not accounting for it fails.

[2020-03-25 11:53:33] production.INFO: User 'User, Some [99999]' has been successfully synchronized.
[2020-03-25 11:53:33] production.ERROR: Unable to import user User 'User, Some [99999. SQLSTATE[HY000]: General error: 1364 Field 'status' doesn't have a default value (SQL: insert into `users` (`objectguid`, `from_ad`, `company_id`, `location_id`, `title_id`, `department_id`, `manager_id`, `employee_type`, `account_expires`, `username`, `name`, `first_name`, `last_name`, `email`, `phone_primary`, `description`, `distinguished_name`, `expirable`, `user_status`, `password`, `updated_at`, `created_at`) values (0e9dedsdd-2a0a-4baf-bdaf-9461828d8f10, 1, 9, 830, 2031, 644, ?, F,<PHONE_NUMBER>854775807, .......))

Does that sound right to you?
Because if you look at my setStatusAttribute function in my import traits above it is only accounting for 2 status codes.

Spot checking the users that fail, all have useraccountcontrol codes other than 512 or 514

It seems because I'm only accounting some of the useraccountcontrol status codes. It looks like if an account has a status code I'm not accounting for it fails.
Does that sound right to you?

I'm not sure honestly, you'll have to deep-dive in your application and see where this App\User query is occurring during import. I don't have access to your full repository, so I can only assist so much while missing 99% of the code base.

For reference, the Import job in Adldap2-Laravel does not use findOrFail on your configured Eloquent user model:
https://github.com/Adldap2/Adldap2-Laravel/blob/0c828772333936f4c26c1ce27bd372008eae7e6e/src/Commands/Import.php#L85-L112

OK. Thanks for putting me on the right track. You are always a great help. Thanks!!

Hi @stevebauman,
Replacing 'firstOrFail' with 'first' and accounting for the different status codes fixed this issue for me.
Thanks again!

Awesome, glad you were able to resolve it! No problem at all :smile:


Question: Possible to individually control each LED?

I don't know a lot about the protocol, but is it possible to individually address each LED, or is it only the effects provided by the controller that can be used?
It would be easier if the ELK-BLEDOM protocol supports this, and it could be integrated into the library. If not, I'll have to set something up with an arduino.

No. This protocol is for an LED strip I bought off AliExpress (something like this) a few years ago. They only support one colour at a time.
Only the effects on the controller itself are supported, though you can make your own by rapidly sending "set colour" commands yourself.

Ok, that's what I was thinking could be the case. Cheers


Should the state be merged at the same level as actions and getters?

In the readme, you mention

Should the state be merged at the same level as actions and getters?

I figured we should open a discussion around this 🙂

My 2 cents:
I think we should either scope all things into relevant properties, eg:
store.state.counter
store.getters.doubleCount
store.actions.reset()

or scope none
store.counter     // state
store.doubleCount // getter
store.reset       // action

Having them all merged in the "root" store might cause naming conflicts between getters and state. However, you could make the argument that having a getter with the exact same name as a property in the state is a fairly bad design decision to begin with. In the case of a naming conflict, the state one should probably overwrite the getter, as getters will often rely on the state value to produce their own value.
A big pro for having them all in the root is that you would be able to do things like
import { useStore } from '@/stores/my-store';

export default createComponent({
  setup() {
    const { counter, doubleCount, reset } = useStore();
  }
});

where you can destructure any of the 'items' in the store.
Is there any specific reason why you decided on putting actions / getters in the root currently @posva?

hey, thanks for opening the discussion. Initially I only had getters and I wanted to differentiate them from state. Then I added actions.

Having them all merged in the "root" store might cause naming conflicts between getters and state. However, you could make the argument that having a getter with the exact same name as a property in the state is a fairly bad design decision to begin with.

Totally :)

In the case of a naming conflict, the state one should probably overwrite the getter, as getters will often rely on the state value to produce their own value.

I don't think it really matters as long as there is an explicit error for the user

A big pro for having them all in the root is that you would be able to do things like

I was thinking of making the whole store a shallowReactive to automatically unwrap getters when accessed (instead of having to use .value. In that scenario, destructuring wouldn't work. But I don't think that's a problem as having the store on a variable makes more sense when reading the code because variables are likely to have a broad naming like name, items instead of being prefixed with a name like user.name, cart.items
Personally, I like the idea of grouping everything into the store without having state, getters or actions

Would it make sense to use .value on the state properties as well? That way you could say:
store.counter === ref()          // state
store.doubleCount === computed() // getter

It would also help clearing up confusing while working on components "When to use .value and when not to". Currently, the indicator to use .value is the absence of .state., but if they're both in the root, it could be confusing to have to combine
store.counter
store.doubleCount.value

Would it make sense to use .value on the state properties as well?

No, that's not desirable. Having not to use .value is much easier

Currently, the indicator to use .value is the absence of .state., but if actions / getters are both in the root, it could be confusing to have to mix

To be fair it's the same as ref vs reactive. I don't think this is a problem, specially given autocompletion

With

Getter with params that act like computed properties

implemented, the difference between an action and a getter wouldn't be clear anymore:
store.state.counter      // state
store.doubleCount        // getter
store.counterPlus(5)     // action or getter?

Having them all scoped would solve this, and would also mean it "follows" the structure of the createStore config parameter:
store.state.counter
store.getters.doubleCount
store.getters.counterPlus(5)
store.actions.incrementBy(5)

When / if the getters-with-params functionality is implemented, would Pinia still have "getters without parameters" too? Eg would store.doubleCount become store.doubleCount()?

The getters with parameters is different from a function, it's still an idea and no proposal has been made. Otherwise yeah, it would just be an action

Hi, this is a great project, I love it! Something I yearned for a long time now.
Little backstory to understand where I'm coming from:
What brought me to Vue was the sweet, simple style of handling state.
This example from the Vue docs got me all fired up:

{{ message }}

  <button v-on:click="reverseMessage">Reverse Message</button>

Finally a framework using a immutable state as source of truth and then build something from that in a functional fashion with vue.render(), whenever this changes. "Awesome! 👍" I thought.
But then Vuex gets recommend a lot and vuex kind of gets in the way of things with their overly boilerplate actions and mutations stringifed syntax. (by no fault of theirs, we simply hadn't the reactive tech yet ).
SoI tended to use vue-apollo instead, but it also gets kind of verbose (see our discussion here)
With this in mind I petition to also changes Pinias' interface to have state, getter & actions on the same level. I think there is real merit in this simplicity. I see Issue #84 also as a expression of this opinion.
Furthermore maybe if the suggestion of getting rid of the .value could be turned on it's head by using computed (like @rijkvanzanten suggested but combine them with a js getter, I think that would be really cool.
I mean something like this sketch
// ** are for empathizing
export const useMainStore = createStore({
  // a function that returns a fresh state
  state: () => ({
    counter: 0,
    **get double()**  {
       return doubleCount.value; // either this
       return counter*2// or maybe don't even need computed
    },
  }),
  // optional getters
  getters: {
    doubleCount: **computed**(() => state.counter * 2),
  },
// optional actions
  actions: {
    setCounter(val:number) {
      this.state.counter = val;
    },
  },
})

Now it should work without .value all around

import { useMainStore } from '@/stores/main'

export default defineComponent({
  setup() {
    const {state:main} = useMainStore()
    console.log(store.counter); // 0

    main.counter = 2 // TS-Error , because its  Readonly<T>
    main.setCounter(2); // alrighty
    console.log(main.counter) // 2
    console.log(main.double) // 4, I guess 🤔

    return {
      // gives access to the `counter` and `double`
     ...toRefs(main) // not sure about `toRefs()`

      // gives access to the whole store
      store: useMainStore(),
    }
  },
})

Also I think there would be great advantages in picking up suggestions from #58 to use Typescripts Readonly utility type to indicate state shouldn't be modified from outside, as I tried to show here as well.
Love to hear your thoughts about this!

The overall direction was exposing everything at the same level. See https://github.com/posva/pinia/pull/190
You won't be able to do const { state } = useMainStore() though

You won't be able to do const { state } = useMainStore() though

I don't think that's a problem, as it's the same with props and reactive objects.
Would that mean that—even though it might be a bit of a weird use case—you'd be able to do something like:
const { counter } = toRefs(useMainStore());

?

Yes, since to unwrap we would internally use reactive or shallowReactive

Awesome, very promising!
@PR #190:
 // gives access only to the state
      state: computed(() => main.state),

Lovely 😍
I also think people will get used to toRefs for destructuring, since we have to do it often with props.
Does this mean, after this changes, there won't be a .value mismatch between state & getters? If yes, would adding another indirection like using js property getter help or doesn't it work?

Closing since #190 was merged
@JoeSchr That code you shared is precisely something that cannot be done anymore 😅 . It might be worth exposing some readonly $state if there is a usecase for it

@posva looks sweet, will have to check it out over the next few days!

ah, but now you can change the state directly, without needing a action right? I feel like this is invalidating the use case for a store, namely the one-direction-flow of data. In my opinion if state can be changed directly, quickly there will be spaghetti code and a lot of coupling and major headaches when debugging. :(

See https://github.com/posva/pinia/issues/58


fix/rounding for balance over hundred percent

Before submitting this PR, please make sure:

[x] Your code builds clean without any errors or warnings
[x] You are using approved title ("feat/", "fix/", "docs/", "refactor/")

A description of the changes proposed in the pull request:
The changes presented in this PR are expected to fix the issue shown at https://github.com/hummingbot/hummingbot/issues/4946, which is caused by rounding errors at operations, as smart rounding could lead to lower values for the divisor of the operation which result is shown.
Tests performed by the developer:
The test is expected to be run by the issue creator as I could not replicate the scenario with my current configuration of the application. If there is any way to simulate the scenario without having wallets please let me know.
Warning These changes only could be merged after being tested by the issue creator or any other HummingBot community member.
Tips for QA testing:
No additional recommendations are brought taking into account the slightness of the modifications.

Hello @sisco0
A Pull Request Proposal was created related to this PR: https://snapshot.org/#/hbot.eth/proposal/0x54e13602869ce0e51447ad750a5b766ff64e142f24d6340434ef70e9a7e77cf4
Make sure to keep an eye on community reviews for the following days.
Thank you for contributing with Hummingbot Client!


Cyborgs do not lose battery power over time

Description
I was in a round as a cyborg and my power level never went below 100% the entire time.
Additional context
I was not using any headlamp for the entire round. Borgs should still have a innate power draw for being active.

That's odd, just earlier today I played a round and my battery was similarly seemingly stuck at 100%, but after doing... something(?) it started going down as usual

Alright I see a bug happening, I think I can get to the bottom of this tomorrow if nobody else does

Just discovered that i was losing power over time while sitting in a cyborg charger. After re-entering it and charging back to full i never lost power again.

After some debugging, the bug is actually weirder than I thought. It's calling a method that should normally be called when the battery is removed whenever you select/unselect a module, but I can't figure out why

Resolved.


Minor README.md fixes

grammar
links for better navigation

Coverage remained the same at 96.925% when pulling e264c2fe013223aac5a8414b40502f6710021ca7 on demidovakatya:dev into bc4b18f1e1e01f104c3d63962c6f42462553cd45 on javascript-obfuscator:dev.

Coverage remained the same at 96.925% when pulling e264c2fe013223aac5a8414b40502f6710021ca7 on demidovakatya:dev into bc4b18f1e1e01f104c3d63962c6f42462553cd45 on javascript-obfuscator:dev.


Cannot build Component example if Component directory has different name than published Component name (IDFGH-13653)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
v5.3-dev-2440-g0de2912f91
Operating System used.
Linux
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
None
What is the expected behavior?
I expected to be able to build the Component example even if the local Component directory name differs from the published Component's name.
Local Component path: ~/repos/esp-idf-rc522 (cloned from here)
Component name on Component Registry: abobija/rc522
What is the actual behavior?
Instead, it throws me an error:
The component abobija__rc522 could not be found. This could be because: component name was misspelled, the component was not added to the build, the component has been moved to the IDF component manager or has been removed and refactored into some other component.

Steps to reproduce.
This throws an error that component cannot be found:

git clone git@github.com:abobija/esp-idf-rc522.git
cd esp-idf-rc522/examples/basic
idf.py build

But if we clone the repo into local dir named rc522 (because that is the name of published Component) then it works:

git clone git@github.com:abobija/esp-idf-rc522.git rc522
cd rc522/examples/basic
idf.py build

Build or installation Logs.
idf.py build
Executing action: all (aliases: build)
Running cmake in directory /home/abobija/repos/esp-idf-rc522/examples/basic/build
Executing "cmake -G Ninja -DPYTHON_DEPS_CHECKED=1 -DPYTHON=/home/abobija/.espressif/python_env/idf5.3_py3.12_env/bin/python -DESP_PLATFORM=1 -DCCACHE_ENABLE=0 /home/abobija/repos/esp-idf-rc522/examples/basic"...
-- IDF_TARGET is not set, guessed 'esp32' from sdkconfig '/home/abobija/repos/esp-idf-rc522/examples/basic/sdkconfig'
-- Found Git: /usr/bin/git (found version "2.43.0")
-- The C compiler identification is GNU 13.2.0
-- The CXX compiler identification is GNU 13.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /home/abobija/.espressif/tools/xtensa-esp-elf/esp-13.2.0_20230928/xtensa-esp-elf/bin/xtensa-esp32-elf-gcc
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /home/abobija/.espressif/tools/xtensa-esp-elf/esp-13.2.0_20230928/xtensa-esp-elf/bin/xtensa-esp32-elf-gcc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /home/abobija/.espressif/tools/xtensa-esp-elf/esp-13.2.0_20230928/xtensa-esp-elf/bin/xtensa-esp32-elf-g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Building ESP-IDF components for target esp32
Using component placed at /home/abobija/repos/esp-idf-rc522 for dependency "abobija/rc522", specified in /home/abobija/repos/esp-idf-rc522/examples/basic/main/idf_component.yml
Processing 2 dependencies:
[1/2] abobija/rc522 (2.6.1) (/home/abobija/repos/esp-idf-rc522)
[2/2] idf (5.3.0)
CMake Error at /home/abobija/repos/esp-idf/tools/cmake/build.cmake:268 (message):
  Failed to resolve component 'abobija__rc522'.
Call Stack (most recent call first):
  /home/abobija/repos/esp-idf/tools/cmake/build.cmake:310 (__build_resolve_and_add_req)
  /home/abobija/repos/esp-idf/tools/cmake/build.cmake:599 (__build_expand_requirements)
  /home/abobija/repos/esp-idf/tools/cmake/project.cmake:710 (idf_build_process)
  CMakeLists.txt:8 (project)

-- Configuring incomplete, errors occurred!
HINT: The component abobija__rc522 could not be found. This could be because: component name was misspelled, the component was not added to the build, the component has been moved to the IDF component manager or has been removed and refactored into some other component.
Please look out for component in 'https://components.espressif.com' and add using 'idf.py add-dependency' command.
Refer to the migration guide for more details about moved components.
Refer to the build-system guide for more details about how components are found and included in the build.
cmake failed with exit code 1, output of the command is in the /home/abobija/repos/esp-idf-rc522/examples/basic/build/log/idf_py_stderr_output_566422 and /home/abobija/repos/esp-idf-rc522/examples/basic/build/log/idf_py_stdout_output_566422

More Information.

I don't like the idea of publishing a component like abobija/esp-idf-rc522 to match the repository name.
I also don't like the idea of renaming the repository to rc522 to match published Component name because of side effects.
I can write instructions for local development to clone the repo into the local rc522 directory using git clone git@github.com:abobija/esp-idf-rc522.git rc522, but I think that would be a bit messy for contributors.

Is it possible to modify the build tool so that it figures out that it's the same component and doesn't throw an error if the local component directory name is different from the published name?

Hello @abobija, thank you for opening the issue,
you are right, currently ESP-IDF CMake build system uses directory names internally, and there is currently no way to pass the real component name from the Component Manager to the build system. I think it can be changed in the future ESP-IDF releases, but not for existing ones.

Thank you for your response. I sincerely hope for prioritization of this issue as it will allow flexibility in publishing components 🙏🏼


AutoMod offender events no longer showing up

Describe your issue
As a user, I expect to be notified when AutoMod catches my message. However, as of a few days ago, this no longer happens.
My understanding is that the PubSub topic we used to use for this no longer provides that data, and we have to migrate over to the following PubSub topic to get the functionality back: user-moderation-notifications.USERID.CHANNELID

Documentation can be seen here

This has been fixed

Note: we still haven't implemented the user-moderation-notifications topic (which is completely fine, especially with an eventsub topic around the corner) -- twitch simply reverted the behavior where they stopped sending automod_message_rejected over chat_moderator_actions (so our old pubsub handler started working again)


fix composite queries

Jordan did this and merged it into main today. I don't know the commit, its the one that happened just before I closed this ticket


MINOR; Fix UpdateMetadataRequestTest.testVersionLogic's assertions

UpdateMetadataRequestTest.testVersionLogic's assertions must verify the deserialized request.
Committer Checklist (excluded from commit message)

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

@chia7712 Could you take a look at this one please?

retest this please

ok to test

Test failures not related, merging to trunk.


Make CallByNeed Serializable and Typename.full a val

Maybe this should be 2 PR but given how simple it is maybe not.

Make CallByNeed Serializable is pretty much self explanatory
Make TypeName.full a val is for perf reason.  It gets expensive if called repeatedly.

Not on it specifically but was running a microbenchmark in scio after upgrading to 0.10.0 and ~30% on the time was spent in this method.


Set focus on errors

Versions:

VueJs: 2.5.2
Vee-Validate: 2.0.0-rc.19

Description:
I am having problems setting focus on child input components when I call validateAll method  from parent component. Is there a way to set focus on first error from errorBag ?

This is not the scope of vee-validate, but It should be straight forward to implement, after validateAll or validate. Assuming you have refs on your inputs you can just call focus on them.
await this.$validator.validate();

// if there is an error with the "email" name.
if (this.errors.has('email') {
  // assuming you named your refs the same as their names
  this.$refs.email.focus();
}


⚠ Bofrost.at has degraded performance

In 4cbc589, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1265 ms

Resolved: Bofrost.at performance has improved in b88dcff after 6 minutes.


No 7.x versions for drupal/redis

It used to work a few days ago, but as of today there is 7.x version of drupal/redis. Off course, there is a 7.x release on drupal.org.
$ composer update
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - The requested package drupal/redis ^7.3 exists as drupal/redis[8.1.0-alpha1, dev-8.x-1.x, 8.1.x-dev] but these are rejected by your constraint.

Same issue for drupal/feeds.

Sorry, don't know what happened exactly. Triggered an update on for both module.

Thanks


fix #388 application sent page adjustments

Coverage remained the same at 100.0% when pulling 5e8f6493ee5bc4b085b55538a0aa6960f4a40862 on 388_application_sent_page_adjustments into 1953d038a7fd3bedb4bdafe557c67eb876380d0e on dev.

Coverage remained the same at 100.0% when pulling 11fc26039da1dd34703bbb155b9d9b53d56a1ea8 on 388_application_sent_page_adjustments into a785f1959b51a1610024e5bcb285358b7c97dff5 on dev.

Coverage remained the same at 100.0% when pulling 9d128fa2fee40df24d1c4e45b2e56923896e0d74 on 388_application_sent_page_adjustments into a785f1959b51a1610024e5bcb285358b7c97dff5 on dev.

Coverage remained the same at 100.0% when pulling 258f65300d82e5ea0e363cbbec5789a76c38052c on 388_application_sent_page_adjustments into af512a05569e5e9e09afb75921b24590e3c2b3d2 on dev.

Coverage remained the same at 100.0% when pulling 258f65300d82e5ea0e363cbbec5789a76c38052c on 388_application_sent_page_adjustments into af512a05569e5e9e09afb75921b24590e3c2b3d2 on dev.

Coverage remained the same at 100.0% when pulling b39bf715b9fb574ce6a5308db58c84435095f657 on 388_application_sent_page_adjustments into af512a05569e5e9e09afb75921b24590e3c2b3d2 on dev.

Coverage remained the same at 100.0% when pulling 353f2337f238189da84aeca7bf67112654f13bd4 on 388_application_sent_page_adjustments into af512a05569e5e9e09afb75921b24590e3c2b3d2 on dev.

Coverage remained the same at 100.0% when pulling 7ca908d6f325113b4af370543ee7c1fa3ac20b8d on 388_application_sent_page_adjustments into 9824530e419935759f1492ac412593cbfb5343a5 on dev.

Coverage remained the same at 100.0% when pulling 06568d1f606233e360288b5cc4e6e8debf34ec36 on 388_application_sent_page_adjustments into 0b926a96e8ecd29d4b53ebac91f33dc0e80c80a4 on dev.


Get Topiary working with mice

[x] Get pyensembl working with arbitary GTFs (including updating release_info.py, common.py, url_templates.py, etc. to not be human specific); see https://github.com/hammerlab/pyensembl/pull/99
[x] Change varcode's reference_name.py (which is currently human specific); see https://github.com/hammerlab/varcode/pull/106
[x] Already done? Mice in mhctools's alleles.py

Fixed by https://github.com/hammerlab/pyensembl/pull/114 and https://github.com/hammerlab/varcode/pull/118


Suppress provider log output

What this PR does / why we need it:
Suppress terraform providers stderr when "TF_LOG="
fixes #246
NONE

/lgtm

/approve

/retest


onboarding: Unavailable subdomain help text on the form for creating an new organization results in content overflow scrollbars.

To reproduce:

Register for a new organization at zulipchat.com/new, and follow the emailed link to the form at /accounts/register.
In the 'Organization URL' field, enter a subdomain already in use, like 'asdf'.

Screenshot:

@zulipbot add "bug" "area: onboarding"

@zulipbot add "good first issue"

@jackrzhang Can I take this issue?

@tear44 Sure, go for it! It's currently open to be claimed. (you can comment "@zulipbot claim")

Ah, that seems to have triggered it despite the quotes. @zulipbot abandon

@zulipbot claim

@zulipbot claim


feat: show multi-address modal post wallet creation

Checklist

[x] JIRA - LW-9804
[ ] Proper tests implemented
[x] Screenshots added.

Proposed solution
Explain how does this PR solves the problem stated in JIRA ticket.
You can also enumerate different alternatives considered while approaching this task.
Testing
Describe here, how the new implementation can be tested.
Provide link or briefly describe User Acceptance Criteria/Tests that need to be met
Screenshots

Changes unknown
when pulling d58b6367707b25586bebfd44f4a843eeb05085eb on feat/lw-9804-multi-wallet-modal
into ** on feat/lw-9881-remove-beta-dapp-modal**.

Approved. But please resolve conflicts. 👍


Can I use Qt5 instead of Qt4 dependencies on Raspberry Pi?

I'm running Ubuntu 21.04 for Raspberry Pi ubuntu-21.04-preinstalled-desktop-arm64+raspi, unfortunately apt can't find Qt4 libraries (libqtgui4 and libqt4-test). I tried a few repositories recommended by others with no luck. Can I use libqt5gui5 instead? I need only imshow to work.

I tested the installation without Qt4 and imshow seems to work as expected. I'm getting this warning, though:
qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in "/home/paul/.local/lib/python3.9/site-packages/cv2/qt/plugins"

BTW, libqt5gui5 is installed.

These packages ship with their own copy of Qt 5. Your system Qt is not used.

Thank you. I was under the false impression that libqtgui4 and libqt4-test are required dependencies. Read it somewhere. I was also installing: libhdf5-dev libhdf5-serial-dev and libatlas-base-dev. Was that unnecessary?
What is this message about, then?
qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in "/home/paul/.local/lib/python3.9/site-packages/cv2/qt/plugins"

The pre-built wheels ship currently only with X Window System (X11) plugin (qxcb). Your system is probably running Wayland instead of that. However, if imshow works, then your system supports also X11 and you can ignore that message.
https://doc.qt.io/qt-5/qpa.html#qpa-plugins

And yes, installing external dependencies is unnecessary when using the manylinux opencv-python wheels installed via pip. The packages depend of course on some external libraries such as Glibc and X11 libraries. but those are very likely already included in all desktop GNU/Linux distributions.

Thank you for a quick response.


Added wifi credentials

self explanatory

Why isn't this merge? If it can't be merged before X, please state so at the top of the PR description.

Closes #123.


Helper for search/filter items

coud probably done via a helper class which just calls the correct update methods on the drawer

Items shouldn't be erased only invisible

still for the adapter is a remove

no helper :P
define a FilterPredicate which will internally be used to filter out the items
itemAdapter.withFilterPredicate(new IItemAdapter.Predicate<IItem>() {
            @Override
            public boolean filter(IItem item, CharSequence constraint) {

                return false;
            }
        })

afterwards you can simply do:
itemAdapter.filter("test");

or to reset
itemAdapter.filter();

@mikepenz everytime a pleasure :-)


fix: Define a max heap size for linux_android

Summary
Fixes gradle build daemon being killed in linux_android builds. Currently, Android builds may fail because the memory used by the build exceeds the memory available.
Checklist

[X] I have tested this on a device and a simulator
[ ] I added the documentation in README.md
[ ] I mentioned this change in CHANGELOG.md
[ ] I updated the typed files (TS and Flow)
[ ] I added a sample use of the API in the example project (example/App.js)

This has actually been released as 4.0.3. There should have been an automated message saying that but, ironically, CircleCI was broken...


Improvements to test-package-files

Checks for package.json in node_modules as well.

test-package-files task from Makefile checks for all package.json from exercises and its subdirectories which also includes any node_modules inside. eg. exercises/phone-number/node_modules/{some-package}/package.json. This is usually not the case, but happened with me since I had created the phone-number exercise and had tested in the same directory. The task fails since these file obviously don't match.

Error does not show filename.

Filename which does not match would be helpful here
⇒  make test
make[1]: *** [test-package-files] Error 1
make: *** [test] Error 2

@tejasbubane I am wondering if this is why @arthurchipdean's alphametics PR is not building( #299 ) .
If you're planning on working on this, great, otherwise I may fix it later to move things along.  Let me know.  Thanks!

I am wondering if this is why @arthurchipdean's alphametics PR is not building( #299 )

Nope that is a genuine error. package.json for alphametics has been change but the change is not propagated over to other files. My scenario won't happen on travis since there will be no node_modules inside exercises directory. Can happen on local if you run test on single exercise using yarn install && yarn test.
I am working on fixing this.
Action items:

[ ] Show filenames in error msg for test-package-files.
[ ] Ignore node_modules inside exercises.

@tejasbubane if you just add the -maxdepth=1 parameter to the find command I think you can ignore the nested package.json files.  I just tried it and it worked for me.
Good luck!

Thanks @matthewmorgan That totally worked!


Portability

If bitser is not in the same folder as main.lua, LoverNet can't find it.

Unless I'm mistaken, windows does not use soft links correctly, which is what I am using excessively.
seppi@seppi7:~/repos/lovernet/client♠ ls -lah
total 16K
drwxr-xr-x 2 seppi seppi 4.0K Apr  3 14:50 .
drwxr-xr-x 5 seppi seppi 4.0K Apr  1 20:09 ..
lrwxrwxrwx 1 seppi seppi   13 Apr  3 14:50 bitser.lua -> ../bitser.lua
-rw-r--r-- 1 seppi seppi  143 Apr  1 17:37 conf.lua
lrwxrwxrwx 1 seppi seppi   13 Mar 28 18:30 define.lua -> ../define.lua
lrwxrwxrwx 1 seppi seppi   15 Mar 28 18:27 lovernet.lua -> ../lovernet.lua
-rw-r--r-- 1 seppi seppi 3.2K Apr  1 20:23 main.lua

Obviously the workaround is to replace the soft links with the files themselves, but then from a development perspective you lose the purpose of having the softlinks: keeping the client and server up to date.
In my personal projects, everything is developed on Linux (with deployment being zip -r ../out.love *), but obv I would love support from other developers - which means I should probably work in a portable environment (which is what you're suggesting I think).
I have an idea to resolve this issue to avoid softlinks: I would combine the client and server example into one example that a user could either choose to make a client or a server - further showing how extendible the software is.
Any other ideas?

d16b519faad17498e6fbdf44aac070c65879b453

Fixed this with a6ddc96571a187cfc9a35684d8ea49700c3ea51d
@VideahGams please tell me if this works on windows cleanly!


Connecting to Bluetooth devices fails after exiting app while connecting

Connecting to Bluetooth devices is no longer possible (on API level 27) after the following steps:

Launch WearMouse and selects a device
Tap on "Connect"
Exit the app by swiping right while the status of the device is shown as "Connecting..."

After these steps, device entries no longer react to touches and connecting to devices is thus no longer possible. This is not fixed by force stopping the app, but is fixed by turning Bluetooth off and on again in the watch settings.

And this is just one of the reasons why this API wasn't public until SDK 28. :)

Luckily this bug is not triggered too easily and the obvious workaround does fix it. Thanks for the confirmation that the issue is indeed unfixable on API levels <= 27.


Edit machine-learning-r-csharp-cluster-model.md

Edit complete.

Hi @ShawnJackson, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;


Cannot import name 'string_int_label_map_pb2'

Hello, When I try to run the main_train.py, I got this error :

from object_detection.protos import string_int_label_map_pb2
ImportError: cannot import name 'string_int_label_map_pb2'

Please how can I solve it????

This error occurs if the protobuf libraries aren't compiled correctly. Check ou the Protobuf Installation/Compilation section in my installation guide for a step-by-step guide on how to correctly compile the protobuf libraries.
If this doesn't solve your problem take a look at the following Github issues:

https://github.com/tensorflow/models/issues/1595
https://github.com/tensorflow/models/issues/6148


WIP: Updates to the notebooks to work with the new registry interface

Thank you Adbu! This PR will be the perfect testbed for the one more test infra poking idea I want to push, e.g the current failures only tell you that there are issues and you can see the details in the rendered artifacts. So I'm bringing in a tool that will expose the tracebacks into the CI logs.

I have just realized thatI have made a few unnecessary changes while doing the testing that I haven't removed yet. I will work on removing those.


⚠ SolarOscp has degraded performance

In 6fa91f7, SolarOscp ($SOLAROSCP_URL) experienced degraded performance:

HTTP code: 200
Response time: 378 ms

Resolved: SolarOscp performance has improved in b6da652 after 10 minutes.


feat: expose the getPeers function on BeeDebug

resolves #153

Makes sense, I'll do it before merge


Tests are broken on main branch.

https://github.com/effector/swc-plugin/blob/96ce0427f6d8ed1e6667eb763f079562de8a6146/tests/fixture.rs#L5
Tests are broken on main branch.
With new swc crates versions, ecma:: namespace should be used
This code fixes tests
use swc_core::{
    common::chain,
    ecma::transforms::testing::test_fixture,
    ecma::visit::as_folder,
    ecma::visit::Fold
};

Fixed here - https://github.com/effector/swc-plugin/pull/14


drivers: Add Atmel SAM counter (TC) Driver

Add basic counter driver based on Timer Counter (TC) module for Atmel SAM E70/V71 series.
Remarks:

The driver is not thread safe.
The driver does not implement guard periods. Use at your own risk or
submit a patch.

Tested on Atmel SMART SAM E70 Xplained board
Depends on #zephyrproject-rtos/hal_atmel/pull/15

I was hoping to avoid proving support for all Atmel SAM family and limit it only to SAM E70/V71 series for now. I have only SAM E70 Xplained board. @stephanosio @nandojve if any of you would be willing to test the driver on SAM3X/4S/4E SoCs I will update the PR.

I have 4L/4S/4E/V71 boards here. If you decide move forward and update hal_atmel for anyone of those I can run TC tests to help you.

I've pushed a new version that supports all SAM series. For know that HAL fixes are done as patch. Once we have a basic patch infrastructure in soc/ introduced by #36181 some (but not all of the HAL patches) can be moved there.

Hi @mnkp ,
I tested with success on SAMV71 and SAM4S. For some reason my SAM4E don't trigger ISR. I need look with time to understand what could be the problem. I think it can be my board. BTW, I discovered that SAM4E TC is 32 bits. SAM4L seems to work but clock is to fast and timer couldn't be configured. I need time to enable a generic clock to enable a slow clock.

@nandojve Thanks for all the help!

For some reason my SAM4E don't trigger ISR.

I double checked DTS to make sure I haven't made a mistake, but all looks well.

I discovered that SAM4E TC is 32 bits.

Thanks, I missed this. I'll need to update the PR.

SAM4L seems to work but clock is to fast and timer couldn't be configured. I need time to enable a generic clock to enable a slow clock.

Yes, unfortunately. Without a slow clock and 16-bit channel the supported time span is very short. In the counter sample one could manually shorten the time when the alarm is triggered and verify that the callback is executed. Temporarily, just to test the driver.

SAM4L seems to work but clock is to fast and timer couldn't be configured. I need time to enable a generic clock to enable a slow clock.

Yes, unfortunately. Without a slow clock and 16-bit channel the supported time span is very short. In the counter sample one could manually shorten the time when the alarm is triggered and verify that the callback is executed. Temporarily, just to test the driver.

Added #36406 to enable a slow clock at Generic Clock 5 (TC0). This is something that allow true test with HW.

Hi @mnkp ,
I conducted more tests with SAM4E. I changed source clock to clk = <3> and cheated at sam_tc_input_freq_table to force a run. The TC is working OK for SAM4E. However, SLCK don't work as clock source and I'm pretty convinced that there is nothing to do with TC driver implementation.
Please, update remaining details to move forward.

@mnkp https://github.com/zephyrproject-rtos/hal_atmel/pull/15 is merged now.

All issues should be fixed now apart from

support for short relative alarms
slow clock on SAM4L, depends on #36406

The driver supports now 32-bit TC counter on SAM4E series, though the feature was not tested.

@nandojve thanks for the comments. Everything should be fixed now.


Add file above and sub folders

Describe the bug
Add file above and Add file below doesn't support folders.
To Reproduce
Steps to reproduce the behaviour:

Create a new project
Within Explorer, add a new file "manual.fs" in a folder "folder"
Add <Compile Include="folder/manual.fs" /> to your fproj file.
Switch to "F#" and use Add File above to add a file "new.fs" above "manual.fs"

Expected behaviour
The file "new.fs" is created in the folder "folder" and added to the project
What happens instead
File "new.fs" is added in the root of the project. It is not added to the project.
Environment (please complete the following information):

OS: Windows 10
Ionide version: 4.0.0
VSCode version: 1.35.1

i am having this same issue. it seems in all cases where ionide should edit fsproj on my laptop it simply will not work. it does however work fine on my other computer.

Actually @SCullman i found the solution. if i went to the vscode output tab (down near console) and select forge i saw that when i added a file it came up with an error message complaing about not having dot-net core 2.1 i installed it form here( just the release version) https://dotnet.microsoft.com/download/dotnet-core/2.1 and now it is sorted.
To the ionide team: maybe either make forge work for dotnet core 3.xx or make a note that it requires 2.1.


windows10 atom1.28 launch crashed

Prerequisites
When  I launch the atom application,it crashed immediately
operation_log.txt
Description
[Description of the issue]
Steps to Reproduce

[First Step] start atom.exe

Expected behavior: [What you expect to happen]
Actual behavior:  when app run
Reproduces how often:  100%
Versions
Atom    : 1.28.0
Electron: 2.0.3
Chrome  : 61.0.3163.100
Node    : 8.9.3
apm --version
apm  1.19.0
npm  3.10.10
node 6.9.5 x64
atom 1.28.0
python 3.6.3
git 2.16.1.windows.1
visual studio
Additional Information
[1772:3988:0702/123735.350:VERBOSE1:crash_service_main.cc(78)] Session start. cmdline is [--reporter-url=https://crashreporter.atom.io --application-name=Atom "--crashes-directory=C:\Users\rayyu\AppData\Local\Temp\Atom Crashes" --v=1]
[1772:3988:0702/123735.354:VERBOSE1:crash_service.cc(142)] window handle is<PHONE_NUMBER>081072
[1772:3988:0702/123735.354:VERBOSE1:crash_service.cc(284)] pipe name is \.\pipe\Atom Crash Service
dumps at C:\Users\rayyu\AppData\Local\Temp\Atom Crashes
[1772:3988:0702/123735.354:VERBOSE1:crash_service.cc(288)] checkpoint is C:\Users\rayyu\AppData\Local\Temp\Atom Crashes\crash_checkpoint.txt
server is https://crashreporter.atom.io
maximum 128 reports/day
reporter is electron-crash-service
[1772:3988:0702/123735.354:VERBOSE1:crash_service_main.cc(94)] Ready to process crash requests
[1772:112:0702/123735.354:VERBOSE1:crash_service.cc(317)] client start. pid = 10492
[1772:112:0702/123736.630:VERBOSE1:crash_service.cc(317)] client start. pid = 10392
[10760:7596:0702/123736.676:VERBOSE1:crash_service_main.cc(78)] Session start. cmdline is [--reporter-url=https://crashreporter.atom.io --application-name=Atom "--crashes-directory=C:\Users\rayyu\AppData\Local\Temp\Atom Crashes" --v=1]
[10760:7596:0702/123736.680:VERBOSE1:crash_service.cc(142)] window handle is<PHONE_NUMBER>0906DA
[10760:7596:0702/123736.680:VERBOSE1:crash_service.cc(284)] pipe name is \.\pipe\Atom Crash Service
dumps at C:\Users\rayyu\AppData\Local\Temp\Atom Crashes
[10760:7596:0702/123736.680:VERBOSE1:crash_service.cc(288)] checkpoint is C:\Users\rayyu\AppData\Local\Temp\Atom Crashes\crash_checkpoint.txt
server is https://crashreporter.atom.io
maximum 128 reports/day
reporter is electron-crash-service
[10760:7596:0702/123736.680:ERROR:crash_service.cc(295)] could not start dumper
[1772:8136:0702/123742.562:VERBOSE1:crash_service.cc(325)] client end. pid = 10492
[1772:8136:0702/123742.821:VERBOSE1:crash_service.cc(325)] client end. pid = 10392
[1772:8136:0702/123743.822:VERBOSE1:crash_service.cc(346)] zero clients. exiting
[1772:3988:0702/123743.822:VERBOSE1:crash_service.cc(486)] session ending..
[1772:3988:0702/123743.822:VERBOSE1:crash_service.cc(491)] clients connected :2
clients terminated :2
dumps serviced :0
dumps reported :0
[1772:3988:0702/123743.822:VERBOSE1:crash_service_main.cc(99)] Session end. return code is 0

Same problem, wait the answer~~~

Thanks for opening this @yl23250. Are you possibly behind a proxy and running shadowsocks? If so, you are likely running into https://github.com/atom/atom/issues/17557. You can follow along in that issue for updates about a fix.
While the team continues to investigate this issue we suggest using Atom 1.27.2, which you can download here:
https://github.com/atom/atom/releases/tag/v1.27.2
After downloading that version make sure to temporarily disable auto-updating by going to Settings > Core > Automatically Update. Let me know if that does not get things working for you.

I experienced the same issue with latest version.
I didn't check logs but it also crashes on startup. Previous version works fine.
I'm on Windows 7 64-bit and I'm not behind a proxy.
Hope that helps a bit!

1.28.1 seems to be working just fine.


Support visionOS platform for nostr-swift & nostr-sdk-swift

Describe the enhancement
Add support in swift bindings for VisionOS platform
Use case
Id like to use this to build an nostr application for VisionOS
Additional context
I don't know a lot about NDK, but a couple of things I think need to be done.
On the swift side, the Package.swift needs to update to swift-tools-version: 5.9 and .visionOS(.v1) added to platforms. Also, I assume that nostr_sdkFFI xcframework needs to be built for visionOS.

Unfortunately rust not support visionOS targets yet: https://github.com/rust-lang/rust/issues/112930

Unfortunately rust not support visionOS targets yet: rust-lang/rust#112930

Ah, good to know. Hopefully it can happen in the near term.


fix(signers): switch to the official AWS SDK for Rust

Motivation
rusoto is only passively maintained
Solution
switch to the official SDK: https://docs.aws.amazon.com/sdk-for-rust/latest/dg/welcome.html
PR Checklist

[x] Added Tests
[x] Added Documentation
[x] Updated the changelog

first line of the docs is that it might be subject to breaking changes. Is this change driven by a specific need? Are we sure the dev preview is the correct place to start depending on it?

@prestwich one specific need on my side is that I'd like to to run the signer over vsock instead of TCP which is possible via: https://docs.rs/aws-sdk-kms/0.17.0/aws_sdk_kms/struct.Client.html#method.from_conf_conn
It's still a developer preview, but it's IMHO on a similar level as Rusoto or better. I've been using it since early alphas and breaking changes took a few minutes of refactoring work from my time so far.

(I'm not blocked by this change; I thought I may just upstream it, but ok to put it off until the SDK has a stable release)

Thanks @tomtau! I think given breakages let's hold off here, but supportive of this directionally eventually.


Clear contexts on unload test helper

I was using the test helper from
https://github.com/node-red/node-red/blob/master/test/nodes/helper.js
when i realized some weird behaviour that i related to node context data, not ocurring in a real nodered instance. After some debugging I ended up cleaning contexts after each test. I've added
contexts.clean({allNodes:[]})
on
https://github.com/node-red/node-red/blob/master/test/nodes/helper.js#L119
As i see a comment wondering if there was someting else to cleanup, should i make a pull request of it?
Thank you

Looks sensible - and makes me aware I've not added context-accessing tests for the inject/change/switch nodes which would have tripped over this.
Will add for the next release.


Changes in README.md

Notes for Reviewers
This PR fixes #7454 and #7416
This PR resolves the issue of License option below Meshery logo and also the links in README.md
Signed commits

[x] Yes, I signed my commits.

Thanks for this, @ShivangShandilya 👍