ipsec: Feed src_id to traces in do_netdev_encrypt for native routing

Please ensure your pull request adheres to the following guidelines:

[x] For first time contributors, read Submitting a pull request
[x] All code is covered by unit and/or runtime tests where feasible.
[x] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[x] All commits are signed off. See the section Developer’s Certificate of Origin
[x] Provide a title or release-note blurb suitable for the release notes.
[x] Thanks for contributing!

In do_netdev_encrypt for native routing mode, there are some drop notifications available. However, they are missing source identity currently. With the change in ae6868c, we can pass inherited source identity from mark to do_netdev_encrypt, so use that.
Add src_id information to drop trace inside the do_netdev_encrypt for native routing mode

This PR depends on https://github.com/cilium/cilium/pull/18608. I'll rebase this branch once it is merged.

Let me close this since now we have this PR.
https://github.com/cilium/cilium/pull/18682


Implementation of TripletMarginLoss

https://github.com/michuanhaohao/reid-strong-baseline/blob/672183d50b11054e24e72306b79692a004bea5cb/layers/triplet_loss.py#L113
If I understand it correctly, according to the official guide, TripletMarginLoss should take (anchor, positive, negative) as forward input instead of (dist_anc_pos, dist_anc_neg, 1).

@prismformore MarginRankingLoss and TripletMarginLoss  are different. TripletMarginLoss also is OK.

You are right. Thank you.


Add @stephenc as a maintainer of the structs plugin

@jglick or @oleg-nenashev

@daniel-beck PING

@stephenc I periodically (multiple times per day) review incoming notifications, that include all repos I watch. 3 minutes is not enough times to require a followup ping.

@daniel-beck it's more I have a release half cut: https://github.com/jenkinsci/structs-plugin/tree/structs-parent-1.8 and I would like to get it finished

Not sure if we need to wait for @jglick , who is the real maintainer of this plugin

So the reason I started the release was that @jglick told me I could release 1.8 myself... so I -
like the fool that I am - assumed he had checked and I was one of the maintainers... turns out I wasn't but I'm assuming he's ok

Given the restrictive wording of https://github.com/jenkinsci/structs-plugin/pull/21#issuecomment-308267072 I'd rather not assume his approval.
@stephenc Do you have a better reference than that?

@daniel-beck well he said it in a call he and I had, so if you want to wait for @jglick that's fine... hopefully my laptop does not die between now and then

Good enough for me.


Intelisense stopped working

Issue Type: Bug
Intellisense has stopped working after latest update.
VS Code version: Code - Insiders 1.24.0-insider (d29620f2ba89327f51bb6fb2f05dfdd65e2fcafe, 2018-05-07T08:55:27.483Z)
OS version: Windows_NT x64 10.0.15063

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz (4 x 3292)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: unavailable_softwarevideo_decode: enabledvideo_encode: enabledvpx_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
7.96GB (2.48GB free)

Process Argv
C:\Program Files\Microsoft VS Code Insiders\Code - Insiders.exe

Screen Reader
no

VM
0%

Extensions (11)

Extension
Author (truncated)
Version

ng-template
Ang
0.1.9

jshint
dba
0.10.18

vscode-eslint
dba
1.4.8

gitlens
eam
8.2.4

EditorConfig
Edi
0.12.1

tslint
eg2
1.0.28

python
ms-
2018.4.0

PowerShell
ms-
1.7.0

typescript-javascript-grammar
ms-
0.0.41

debugger-for-chrome
msj
4.4.3

vscode-react-native
vsm
0.6.9

Debug output from developer console:
 Cannot read property 'getConfiguration' of undefined: TypeError: Cannot read property 'getConfiguration' of undefined
    at FileConfigurationManager.getPreferences (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/typescript-language-features/out/features/fileConfigurationManager.js:106:45)
    at FileConfigurationManager.getFileOptions (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/typescript-language-features/out/features/fileConfigurationManager.js:73:31)
    at FileConfigurationManager.ensureConfigurationOptions (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/typescript-language-features/out/features/fileConfigurationManager.js:59:37)
    at FileConfigurationManager.ensureConfigurationForDocument (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/typescript-language-features/out/features/fileConfigurationManager.js:49:25)
    at TypeScriptCompletionItemProvider.provideCompletionItems (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/typescript-language-features/out/features/completionItemProvider.js:215:45)
    at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:661:233
    at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:96:887
    at new n.Class.derive._oncancel (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:76:776)
    at Object.t.asWinJsPromise (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:96:850)
    at e.provideCompletionItems (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:661:187)
    at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:673:315
    at e._withAdapter (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:666:579)
    at e.$provideCompletionItems (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:673:277)
    at e._doInvokeHandler (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:602:894)
    at e._invokeHandler (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:602:612)
    at e._receiveRequest (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:601:682)
    at e._receiveOneMessage (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:601:451)
    at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:600:384
    at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:603:463
    at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:88:432
    at e.fire (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:89:764)
    at Socket.<anonymous> (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:146:1016)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:191:7)
    at readableAddChunk (_stream_readable.js:178:18)
    at Socket.Readable.push (_stream_readable.js:136:10)
    at Pipe.onread (net.js:560:20)

log.ts:171   ERR Cannot read property 'getConfiguration' of undefined: TypeError: Cannot read property 'getConfiguration' of undefined
    at FileConfigurationManager.getPreferences (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/typescript-language-features/out/features/fileConfigurationManager.js:106:45)
    at FileConfigurationManager.getFileOptions (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/typescript-language-features/out/features/fileConfigurationManager.js:73:31)
    at FileConfigurationManager.ensureConfigurationOptions (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/typescript-language-features/out/features/fileConfigurationManager.js:59:37)
    at FileConfigurationManager.ensureConfigurationForDocument (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/typescript-language-features/out/features/fileConfigurationManager.js:49:25)
    at TypeScriptQuickFixProvider.provideCodeActions (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/typescript-language-features/out/features/quickFixProvider.js:143:51)
    at <anonymous>

log.ts:171   ERR Cannot read property 'getConfiguration' of undefined: TypeError: Cannot read property 'getConfiguration' of undefined
    at FileConfigurationManager.getPreferences (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/typescript-language-features/out/features/fileConfigurationManager.js:106:45)
    at FileConfigurationManager.getFileOptions (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/typescript-language-features/out/features/fileConfigurationManager.js:73:31)
    at FileConfigurationManager.ensureConfigurationOptions (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/typescript-language-features/out/features/fileConfigurationManager.js:59:37)
    at FileConfigurationManager.ensureConfigurationForDocument (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/typescript-language-features/out/features/fileConfigurationManager.js:49:25)
    at TypeScriptCompletionItemProvider.provideCompletionItems (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/extensions/typescript-language-features/out/features/completionItemProvider.js:215:45)
    at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:661:233
    at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:96:887
    at new n.Class.derive._oncancel (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:76:776)
    at Object.t.asWinJsPromise (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:96:850)
    at e.provideCompletionItems (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:661:187)
    at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:673:315
    at e._withAdapter (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:666:579)
    at e.$provideCompletionItems (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:673:277)
    at e._doInvokeHandler (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:602:894)
    at e._invokeHandler (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:602:612)
    at e._receiveRequest (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:601:682)
    at e._receiveOneMessage (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:601:451)
    at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:600:384
    at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:603:463
    at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:88:432
    at e.fire (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:89:764)
    at Socket.<anonymous> (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:146:1016)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:191:7)
    at readableAddChunk (_stream_readable.js:178:18)
    at Socket.Readable.push (_stream_readable.js:136:10)
    at Pipe.onread (net.js:560:20)

Seems to be fixed in 8a07c8d935998d1b1153dde0c5b337189d35cea0

This


Fix for Issue #135

Fixes issue #135 by adding

Parser support for property ref returns.
Related unit tests.

@csdahlberg Ok I've fixed the intendation, sorry for that.


'Select all' and 'Search' inputs are not labelled

The ‘Select all’ checkbox and ‘Search’ text field in the header of the Dropdown do not have textual labels. Because of this, the function of these input elements may not be apparent to users of assistive technologies. As there is no room for a visible <label> element, could you add a descriptive title attribute to each of these fields?

Another option is to add labels, but assign the sr-only class to them, which would hide them from regular users.


Making Photon work with GC

Turned out libc functions work great with Photon, it was the Boehm GC (libgc) that was causing segfaults. Making Photon work with GC is the only thing left to be done.
Stackful coroutines have their own stacks with dynamic sizes, such behavior makes it hard for the GC to detect alive objects. Does photon have a way to register coroutine stacks and let the GC know about context switching?
As I understand, Boehm GC has a way to let know about a new stack during context switching, but I didn't find this feature in Photon...
Originally posted by @medvednikov in https://github.com/alibaba/PhotonLibOS/issues/148#issuecomment-1584908127

Porting directives:
https://github.com/ivmai/bdwgc/blob/master/docs/porting.md#thread-support

@medvednikov take look at this

Great, thanks!  Will do.

Hey,
Just wanted to give you an update.
We managed to successfully make Photon work in V with the Boehm GC by using the recently introduced set_photon_thread_stack_allocator.
The change turned out to be very simple:
https://github.com/vlang/v/commit/9604a3f491a08ea1576b4722212b83c6a6a8d2a4
So thanks a lot for that! This surely made Photon a great option for all GC languages.

@medvednikov
Glad to know it's working.
And I didn't expect that the allocator could be implemented in V. It's really cool!

@lihuiba Thanks for all the assistance. I was surprised how easy it was to add support.
Regarding the allocator, I did try using the default allocator and also the stackful_malloc function provided, however I kept getting segfaults.
our malloc uses the GC malloc (when GC is on), so Im guessing if we were to use another allocator we may need to provide some extra information to the GC as well as the roots. I'm not sure though, that is just a guess.

@joe-conigliaro the stackful_malloc is intended for stackless coroutine, such as the one in C++20. It assumes a FILO order of allocation and deallocation. It is NOT a generic allocator.

Thanks for the reply @lihuiba, I had a feeling it was used for something like that due to the comment

@medvednikov @joe-conigliaro BTW, the threading part of photon now supports Windows via mingw (msys2). See https://github.com/alibaba/PhotonLibOS/pull/185/files#diff-f0db3c6fae5cc5fe519ada39d68af66b8c177096a3ee36c0d92893be964cf34c details.

Amazing news!


Move ReadTheDocs configuration to use YAML config

This PR fixes build issues with the ReadTheDocs pipeline by moving over to a YAML-based configuration that gives us a bit more control. In particular, we can then move QuTiP to install after Cython has been installed, working around a bug in QuTiP's setup.py.

Coverage remained the same at 74.549% when pulling<PHONE_NUMBER>06c044fb01d894fae0751c65e92f37 on cgranade/fix-rtd-1 into 3c9cc7e0194a92c6563392979d4d9cb693fb9eef on master.

Out of interest, could you briefly explain why qutip needs this special attention? (I may be adding it as a requirement to another project sometime soon)

The basic problem with including QuTiP is that its setup.py script needs Cython to already be installed. When pip tries to collect a list of dependencies it fails due to Cython not being present. The conda-forge recipe for QuTiP avoids this problem, as does installing with pip after Cython has been successfully installed.


Backend API Specification : Main Page

Request List

Fetch Main Data
Course Search

Fetch Main Data
Request
GET /api/main/

Response
JSON containing proper data.
Refer to sample.zip in below comment.
Request without login / with expired session will result in 400 Bad Request.
Course Search
This API is for search modal.
Request
POST /api/main/search/

URL-encoded parameter : (may change to JSON)

Parameter
Description
Example

node_title
Name of treenode you want to search for.
생물학 및 실험

title
Search option : course title
실험

code
Search option : code
034.033

credit
Search option : credit
1

category
Search option : category
교양

area
Search option : area
학문의 기초

subarea
Search option : subarea
과학적 사고와 실험

college
Search option : college
자연과학대학

dept
Search option : department
생명과학부

Response
List of JSON as a search result.
Parameters are same as search options above.
{
    "data": [
        {
            "title": "컴퓨터의 개념 및 실습",
            "other_tags": "..."
        },
        {
            "title": "컴퓨터과학이 여는 세계",
            "other_tags": "..."
        }
    ]
}

sample.zip

GET /api/main

should return major info too, as frontend needs it. #61

I think we should change backend API that returns ALL data of disciplines.
It may returns like
{
  "disciplines" : [
    {
      "name" : "컴퓨터공학부",
      "type" : "주",
      "data" : ~
    },
    {
      "name" : "수리과학부",
      "type" : "부",
      "data" : ~
    },
}

There are some conflicts between frontend and backend.

Tooltip needs
 rather than \n.
and some other things. I think we should make sure of complete frontend/backend spec.

frontend spec

frontend will process json response with this form.

{
  "totalSimData" : [
    {
      "major" : {
        "name" : string,
        "type_" : string
      },
      "semesters" : [
        {
          "year" : string,
          "season" : string,
          "subjects" : [
            {
              "title" : string,
              "category" : string,
              "tooltip" : string
            },
            ...
          ]
        },
        ...
      ],
      "remainSubject" : [
        {
          "title" : string,
          "category" : string,
          "tooltip" : string
        },
        ...
      ],
      "creditResults" : {
        "totalReq" : int,
        "totalAcq" : int,
        "mandatoryReq" : int,
        "mandatoryAcq" : int,
        "electivesReq" : int,
        "electivesAcq" : int,
        "liberalReq" : int,
        "liberalAcq" : int
      }
    },
    ...
  ]
}

total : full of credits
mandatory : 전필
electives : 전선
liberal : 교양, 모든 교양을 포함함(free 제거)

Changed sample.zip properly. @MKRoughDiamond


Suggestion: don't strip outer arrays automatically

https://github.com/DanielHabenicht/MMM-json/blob/d63c154ac2d074e80ab34da331b9ca05a149f53c/node_helper.js#L28-L31
If the outer object is an array it is stripped here. Though I would think it's quite elegant if MMM-json would just display arrays as arrays.
Especially considering my PR #2, how nice and powerful would it be if jq would produce an array and it would be displayed.
An example
My request + jq generate a list of episodes to watch:
[.result.episodes[]|[.showtitle,.title]|join(" - ")]
[
  "Sherlock - The Sign of Three",
  "Suits - She's Gone",
  "The Boys - The Name of the Game",
]

Currently it would display the first string, but split into characters:

A work around is to include an additional array
[[.result.episodes[]|[.showtitle,.title]|join(" - ")]]

It would imho be even nicer if MMM-json would display arrays just as lists, without the indexes (0, 1, 2) in my example. Maybe even allow single values to be displayed?
If you're interested a a PR, please let me know.

Mhm, that would be reasonable I think. It was just that my first use case was an array of objects so I coded it into the application instead of my configuration. ^^
I think I will setup versioning before your PR gets merged but you can incorporate it into your current one if you like.


Display the number of favorites next to the link (Feature request)

Any suggestions on how I could add the number of products favorited next to the link to favorites page ?

@catalin88
You can override add_link_to_mark_product_as_favorite.rb deface and use favorite_users_count attribute on product to show how many people have marked it favorite.
In case you want to add number of favorite products with respect to user just next to favorite products tab you can override add_link_to_users_favorite_products.rb deface and use spree_current_user.favorite_products.count.


use default marker if the scripted one isnt defined

there is no javelin counter defined so it should be using a default one instead of giving an error.

i think this is fixed now?


Update script after switching to submodule for uberenv

This PR will fix Uberenv CI (related to https://github.com/LLNL/uberenv/pull/65).
closes #451

[x] Test Uberenv CI before merging. (https://lc.llnl.gov/gitlab/smith/serac/-/jobs/244823)

Codecov Report

Merging #461 (4145cf0) into develop (e94a19b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #461   +/-   ##
========================================
  Coverage    92.71%   92.71%
========================================
  Files           47       47
  Lines         2430     2430
========================================
  Hits          2253     2253
  Misses         177      177

Continue to review full report at Codecov.

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


Syntax highlighting incorrect for type literals

protected _normalizeDatasets<A, B>(fromX: boolean): {a: A; b: B}[] {
  return Stacked.prototype._normalizeDatasets.call(this, fromX);
}

The typed object literal for the return typing "{a: A; b: B}" wrecks syntax highlighting for the rest of the page. I have tried putting a semicolon after the B as well and the syntax highlighting is still incorrect. Is this an issue with my syntax, or is there a bug with the plugin?

Recent updates of the syntax definition files seem to address this issue. On my machine (latest on the master branch) your code shows up correctly:


Many models have missing standby_power

I can suggest to correct model.json files (when it is unknown) to 0.4W (as it has quite high probability to be closest to real standby power).
When more measurements will be ready it will be easier to predict real standby power as the same generation of Zigbee modules sholud have close power draw.

Also all model.json needs to be updated which have no measure_ props. Will do my files in the next week

I'm currently on vacation till September 12. After that I will start to update my files.

Thanks a lot. Yesterday I updated my files with measure_ props. Will need to add some missing standby_usage when I have my Shelly back.
@franzbischoff Are you able to add missing properties to Sonoff B02 LUT?

Hi, I did my measurements using the Sonoff DualR3 information. It is not precise enough to give me the wattage of the standby consumption...
I did make several readings on every 10% of the lamp and did a linear regression to estimate the correct consumptions, but the standby I think I won't get the proper number...

TODO:
Missing standby:

Signify LCT003 (@bramstroker)
Signify LCT010 (@bramstroker)
Signify LCT012 (@bramstroker)
Signify LTC001 (@bramstroker)
Signify LTW001 (@bramstroker)
Signify LWA004 (@bramstroker)
Tradfri LED1545G12 (@CM000n)

Missing measurement info

Signify LCA001 (@CM000n)
Signify LCT015 (@CM000n)
Tradfri LED1545G12 (@CM000n)

Ordered another power meter which hopefully will be able to measure small currents so I can fix the missing standby usages. Will be delivered next sunday.
@CM000n are you able to fix the 4 model.json's as mentioned above. Thanks a lot.


Exception thrown by safe::operator~() for Stored types smaller than int

As detailed in Issue #49, the static_assert in safe::operator~() is missing a logical !.
BUT when I attempted to correct this and write a simple unit test, I observed surprising behavior.  The simplest reproduction is:
#include "../include/safe_integer.hpp"

#include <cstdint>

// Note: requires trivial fix for static_assert problem described in Issue #49.
int main(){
    const boost::numeric::safe<std::uint8_t> val(1);
    ~val;
}

Result:
libc++abi.dylib: terminating with uncaught exception of type std::domain_error: Value out of range for this safe type

I argue that this is surprising behavior: I expect that bitwise not should always succeed and return a result in range.
The reason for this error is the implementation of operator~():
    constexpr safe_base operator~() const {
        static_assert(
            !std::numeric_limits<Stored>::is_signed,
            "Bitwise inversion of signed value is an error"
        );
        return ~(m_t);
    }

The expression ~(m_t) results in type promotion, and is of type int.  When the safe_base<std::uint8_t> is constructed from the large int value (through the implicit conversion to the return type), an exception is thrown.
This could be fixed with an explicit cast to Stored when that type is smaller than int, but I'm not sure that's in the spirit of this library.

See also this discussion of an earlier pull request here: Wrong check in operator~ #23.

I think I've come to agree with you.  The current code does not invoke this exception.


Remix Vite Plugin watches server.watch.ignored files

Reproduction
Checkout https://github.com/janvogt/remix-vite-watches-ignored-repro, run npm run dev and wait a couple of seconds.
See git log for the two changes from npx create-remix@latest.
System Info
I believe the relevant info is that be reproduced on linux as long as /proc/sys/fs/inotify/max_user_watches is not extremly high. I hit this issue multiple times with:
$ cat /proc/sys/fs/inotify/max_user_watches
122722

Here's the output anyway:
$ npx envinfo --system --npmPackages '{vite,@remix-run/*}' --binaries --browsers
System:
  OS: Linux 6.6 NixOS 24.05 (Uakari) 24.05 (Uakari)
  CPU: (8) arm64 Neoverse-N1
  Memory: 7.76 GB / 15.20 GB
  Container: Yes
  Shell: 3.7.1 - /run/current-system/sw/bin/fish
Binaries:
  Node: 20.18.0 - /nix/store/hsh74yzdb9yk834w9j5qz0w3sw84wcfv-nodejs-20.18.0/bin/node
  npm: 10.8.2 - /nix/store/hsh74yzdb9yk834w9j5qz0w3sw84wcfv-nodejs-20.18.0/bin/npm
npmPackages:
  @remix-run/dev: ^2.14.0 => 2.14.0
  @remix-run/node: ^2.14.0 => 2.14.0
  @remix-run/react: ^2.14.0 => 2.14.0
  @remix-run/serve: ^2.14.0 => 2.14.0
  vite: ^5.1.0 => 5.4.11

Used Package Manager
npm
Expected Behavior
npm run dev should work, despite a deeply nested folder in the project directory. As long as this folder is server.watch.ignored.
Actual Behavior
npm run dev crashes with
$ npm run dev

> dev
> remix vite:dev

  ➜  Local:   http://localhost:5173/
  ➜  Network: use --host to expose
  ➜  press h + enter to show help
node:internal/fs/watchers:247
    const error = new UVException({
                  ^

Error: ENOSPC: System limit for number of file watchers reached, watch '/home/jan/opensource/repro/remix-vite-watches-ignored-repro/clean-repro/dont_watch/8/8/52/5'
    at FSWatcher.<computed> (node:internal/fs/watchers:247:19)
    at Object.watch (node:fs:2490:36)
    at createFsWatchInstance (file:///home/jan/opensource/repro/remix-vite-watches-ignored-repro/clean-repro/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:42779:17)
    at setFsWatchListener (file:///home/jan/opensource/repro/remix-vite-watches-ignored-repro/clean-repro/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:42826:15)
    at NodeFsHandler._watchWithNodeFs (file:///home/jan/opensource/repro/remix-vite-watches-ignored-repro/clean-repro/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:42981:14)
    at NodeFsHandler._handleFile (file:///home/jan/opensource/repro/remix-vite-watches-ignored-repro/clean-repro/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:43045:23)
    at NodeFsHandler._addToNodeFs (file:///home/jan/opensource/repro/remix-vite-watches-ignored-repro/clean-repro/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:43287:21)
Emitted 'error' event on FSWatcher instance at:
    at FSWatcher._handleError (file:///home/jan/opensource/repro/remix-vite-watches-ignored-repro/clean-repro/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:44480:10)
    at NodeFsHandler._addToNodeFs (file:///home/jan/opensource/repro/remix-vite-watches-ignored-repro/clean-repro/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:43295:18) {
  errno: -28,
  syscall: 'watch',
  code: 'ENOSPC',
  path: '/home/jan/opensource/repro/remix-vite-watches-ignored-repro/clean-repro/dont_watch/8/8/52/5',
  filename: '/home/jan/opensource/repro/remix-vite-watches-ignored-repro/clean-repro/dont_watch/8/8/52/5'
}

Node.js v20.18.0

Potential fix
Changing both of these lines:
[https://github.com/remix-run/remix/blob/bff2d58bdd22fe305f3e7ca8ddad03c5940f4e90/packages/remix-dev/vite/plugin.ts#L1053]
[https://github.com/remix-run/remix/blob/bff2d58bdd22fe305f3e7ca8ddad03c5940f4e90/packages/remix-dev/vite/plugin.ts#L1273]
from
watch: viteConfig.command === "build" ? null : viteUserConfig.server?.watch,

to
watch: viteConfig.command === "build" ? null : viteUserConfig.server?.watch,

fixes this issue.
I do not know if that would have unintended side efects. I traced changes to vite config and found that server.watch.ignored is overwritten in the second line. PR 8320 that introduced that line, didn't seem to intend this beaviour. In fact, it solved a similar problem #8313 for npm run build. Wheras in that case disabling watching altogether, is no solution for npm run dev to support HMR.


activeTitleStyle doesn't work

choiceConfig: SmartSelectChoiceConfig(
isGrouped: true,
glowingOverscrollIndicatorColor: kPrimaryColor,
style: SmartSelectChoiceStyle(
activeColor: kPrimaryColor,
checkColor: Colors.white70,
activeTitleStyle: TextStyle(
color: Colors.white70
),
)
//          secondaryBuilder: (context, item) => CircleAvatar(
//            backgroundColor: kPrimaryColor,
//            child: Text('H')
//          )
),
#activeTitleStyle color doesn't work !

Hi @Okayo18, I apologize for this long response.
You can use choiceTitleBuilder to build the custom choice title widget
SmartSelect<T>.[single|multiple](
  ...,
  choiceTitleBuilder: (context, item, filter) {
    return S2Text(
      text: item.title,
      style: TextStyle(
        color: item.selected ? Colors.blueAccent : Colors.black54
      ),
      highlight: filter,
      highlightColor: Colors.redAccent.withOpacity(.7),
    );
  },
);

I released https://pub.dev/packages/flutter_awesome_select with fixed null safety.
Could you check that everything works for you?

Hi everyone,
I'm really sorry for not maintaining the smart_select package in a long time. It's been a great project, but it's become too difficult for me to maintain, especially since I've been going through a tough time for the past few years.
In its place, I've released a new package called choice. The combination to smart_select and chips_choice with cleaner, more flexible, and composable API for creating inline or prompted choice widgets with single or multiple selection.
I hope you'll check out choice. I think you'll find it to be a great replacement for smart_select.
Thanks for your understanding.


Get platform working on coreOS beta channel (with Docker 1.9)

At the moment only works on CoreOS stable on Docker 1.8.3. This is down to a docker in docker issue when starting up the mesos slave container.
The specific error there was -
Failed to create a containerizer: Could not create DockerContainerizer: Failed to create docker: Failed to get docker version: Failed to execute 'docker -H unix:///var/run/docker.sock --version': exited with status 127

WIP for docker overlay/mesos-consul/traefik or Fabio/coreOS beta here

Had the same issue with the current CoreOS beta, which uses Docker 1.9.1. Fixed it by using
docker run \
    --net=host \
    --privileged \
    -v /sys/fs/cgroup:/sys/fs/cgroup \
    -v /var/run/docker.sock:/var/run/docker.sock \
    -v /usr/bin/docker:/usr/bin/docker \
    -v /lib64/libdevmapper.so.1.02:/lib/libdevmapper.so.1.02:ro \
    -v /lib64/libsystemd.so.0:/lib/libsystemd.so.0:ro \
    -v /lib64/libgcrypt.so.20:/lib/libgcrypt.so.20:ro \
    ... <other settings> \
    mesosphere/mesos-slave:0.27.0-0.2.190.ubuntu1404

I get this on consul container output on beta -
Error response from daemon: Cannot start container 62ab37a0b249225b45ef3ec1efe5b72a787a98d93c92797644bf1073d418d83e: failed to create endpoint consul on network bridge: Error starting userland proxy: listen udp <IP_ADDRESS>:53: bind: cannot assign requested address```

This should be fixed for mesos-slave in https://github.com/Capgemini/Apollo/commit/6c14298c706749c730de07223828d6702aa68979 on #636


Interaction with trace

Reuse the existing interface:

Use existing trace-on/trace-off triggers
Potential race condition when trigger is set to those action.

Use halted signal

The signal has to be in-band to be synchronized with trace output transaction.
With a new xtrcen signal in the interface
Same behavior as halted signal. Avoid confusion with ”halt” in Debug spec

Conclusion is to use new signal (or a vector) rather than halted, @AoteJin to work on the details

Revisit the e-trace and debug spec, trace-on/trace-off trigger are defined as sideband signal to trace encoder and their priority are UNDEFINED (debug spec says it should be defined by trace spec, while e-trace spec doesn't define it, hmmm... ). Thus, it cannot be a candidate for trace control.
Based on discussion on TG meeting, adding another bit alongside halted signal to bundle a vector  is friendly to future extension.

[new_bit, halted]
Tracing?
Disable reason

00
Yes
n/a

01
No
entering Debug Mode

10
No
due to security rules

11
No
reserved for future

It should be general to accommodate both e-trace and n-trace.

@bcstrongx @sifiverobert @IainCRobertson could you help review the above solution. If the idea is acceptable, the external debug security spec will follow this direction.

This looks good to me.

Looks good to me as well.

Apologies for the delay - I've been on vacation.  This looks good to me too.  We will need an issue opening against the E-Trace spec.  At some point the interface will be pulled out of the E-trace spec into a separate standalone doc, but either way this change will lead to a minor-version change (if still within E-Trace it would be 2.1.0).
You should also add guidance about interoperability with trace encoders compatible with the current spec (OR these 2 bits together and connect to the TE's 'halted' input).
Regarding your comment about trace-on/off priority, can you clarify what you mean exactly?  The E-Trace spec is clear that tracing starts from the cycle in which trace-on is asserted, and stops after the cycle in which trace-off is asserted.  By implication, if both are asserted together, only instructions retired in that cycle will be traced.  I don't see an ambiguity about priority here.  Or is your concern something else?

Apologies for the delay - I've been on vacation. This looks good to me too. We will need an issue opening against the E-Trace spec. At some point the interface will be pulled out of the E-trace spec into a separate standalone doc, but either way this change will lead to a minor-version change (if still within E-Trace it would be 2.1.0).

Sure! I will open an issue for e-trace regarding the  new signal.

You should also add guidance about interoperability with trace encoders compatible with the current spec (OR these 2 bits together and connect to the TE's 'halted' input).

Thanks for reminding! It is a really good point.

Regarding your comment about trace-on/off priority, can you clarify what you mean exactly? The E-Trace spec is clear that tracing starts from the cycle in which trace-on is asserted, and stops after the cycle in which trace-off is asserted. By implication, if both are asserted together, only instructions retired in that cycle will be traced. I don't see an ambiguity about priority here. Or is your concern something else?

Actually, I mean the following case might be hazardous with trace-on/trace-off signals:

Triggers set to trace-on at PC 0x8 while trace-off at PC 0x4
Triggers set to trace-on at PC 0x8 while xtrcen enforce trace-off at PC 0x4 (assuming privilege change after 0x4)

Case 1: assuming code is executing linearly and is active initially, trace will stop after 0x4, and then start at 0x8.  If 0x4 is a 16-bit instruction then the instruction at 0x6 will not be traced (though I think you're assuming 32-bit instructions and 0x8 is the instruction after 0x4).
Case 2: xtrcen if a level, not a pulse (same as halted signal).  So if was low after 0x4, nothing will be traced again until it goes high.  However, all signals on the interface are ignored when halted is high (or xtrcen is low), and this includes the triggers.  So when xtrcen eventually goes high again, tracing will not start until there is a trace-on trigger.  In other words trace on/off triggers are only effective if the code they are associated with is permitted to be traced.  This could definitely be clarified.

I think the previous discussion to leverage trace-on/trace-off for security control is to avoid the xtrcen or halted signal be used. And if xtrcen and halted signal is not in place, the trace-on/trace-off signal are not blocked. Then case 2 is basically a variant of case 1. The case 1, as described above, effective appear as there is no trace-on/trace-off happened. This my concern.

Okay, so in that case, tracing should continue.  The trace-off at 0x4 says "this is the last instruction traced", but the trace-on at 0x8 says "this is the 1st instruction traced".   The end result is that the trace enable never actually goes low.
However, I accept that this is not stated explicitly and could be clarified.

The external debug security spec use the signal vector to inform the trace module that it should stop output per commit #19.
It uses the name sec_check for new signal, will align to the trace spec when it is updated.


Consider explicitly listing diversity & inclusivity goals

In the words of @techiecheckie on Twitter,
Your recruiting document is trying really hard but not enough. Recruiting diversely means little w/o hiring followup. I'd prefer to see explicit numbered diversity goals rather than, again, vague non-committance. Especially bc you already know your most diverse pool of applicants will come from ppl least likely to get in.
Tweets start here.

I'll note that this is something we would really like to do, but have thus far been counseled against it by our HR lawyer for legal reasons. Worth exploring whether there are ways we can set goals around building an inclusive company while staying within the bounds of what's legal!

Twitter released something like what I'm talking about recently: https://blog.twitter.com/2015/we-re-committing-to-a-more-diverse-twitter
So I doubt it's illegal. I'd bring this document up and see if you can't work something out.

Oh, awesome, hadn't seen that! Will discuss with HR and see what we can do :)

Checking in to pick this thread up again. Am super impressed with this handbook and am currently building something out for my community. Would love to hear how this turned out.


Out of the box, getting 400s for participate endpoint

After setting up sixpack for the first time, I'm playing with the default endpoints provided in the docs and getting a "missing arguments" response.
Here's the curl:
curl http://localhost:5000/participate?experiment=button_color&alternatives=red&alternatives=blue&client_id=12345678-1234-5678-1234-567812345678
Tried a bunch of different permutations of parameters, as well.
Here's the log from sixpack on the inbound request:
<IP_ADDRESS> - - [19/Aug/2015 13:23:06] "GET /participate?experiment=new-header HTTP/1.1" 400 -
<IP_ADDRESS> - - [19/Aug/2015 13:25:39] "GET /participate?experiment=button_color HTTP/1.1" 400 -
<IP_ADDRESS> - - [19/Aug/2015 13:27:48] "GET /participate?experiment=button HTTP/1.1" 400 -
<IP_ADDRESS> - - [19/Aug/2015 13:28:00] "GET /participate?experiment=button HTTP/1.1" 400 -
<IP_ADDRESS> - - [19/Aug/2015 13:38:31] "GET /participate?experiment=new-header HTTP/1.1" 400 -
<IP_ADDRESS> - - [19/Aug/2015 13:38:57] "GET /participate?experiment=new-header HTTP/1.1" 400 -
<IP_ADDRESS> - - [19/Aug/2015 13:40:14] "GET /convert?experiment=new-header HTTP/1.1" 400 -
And, all occurances give "missing arguments":
{"status": "failed", "message": "missing arguments"}
I might be missing something simple here, but I dove into the code, and it looks like I should be passing all the required parameters in the URI.
Thanks!

All calles to participate require at least two alternatives, experiement name, and client_id. Seems you're missing those in your subsequent calls.

The request I'm using should be valid:
curl http://localhost:5000/participate?experiment=button_color&alternatives=red&alternatives=blue&client_id=12345678-1234-5678-1234-567812345678
gives:
<IP_ADDRESS> - - [19/Aug/2015 13:53:17] "GET /participate?experiment=button_color HTTP/1.1" 400 -
And...
{"status": "failed", "message": "missing arguments"}

Figured it out. If you put an " ' " around the string in curl, it works. My bad. Thanks for the assist.
You might want to edit the docs, though!


angularjs and php

For the sake of mysql database, i need also to try angular in php and not just in nodejs.
we know that $routeProvider change url address but when reload it gets 404 so i just made some redirection to main page with .htaccess but weird things happened.. instead of redirection, it executes $routeProvider's url which accidentally makes better..
here's my .httaccess and i'm using xampp:
ErrorDocument 404 /mysite/

Hi @skynet8,
Could you share you .htaccess? I also want to run angular docs under apache.
Thanks!


can not find env_CF_MIMO_noGroup.py

when i run main.py, there is an error: could not find module env_CF_MIMO_noGroup

Many thanks for pointing out the bug. I have updated the 'main.py' for the import modules.

Moreover, as outlined in the README, users should commence by configuring the environment in "env/env_CF_MIMO.py" before running the code. The primary task involves completing the "compute_reward" function on line 137 and the "step" function on line 140. In my paper, I have designated the sum-SE as the reward; however, you will need to adapt it to align with your specific requirements.

And I will update the repo to the lastst version of my code soon


"require function is used in a way in which dependencies cannot be statically extracted"

I'm not sure this is an issue on the boilerplate side, but I have seen a lot of posts on the web saying this is a webpack configuration issue.
The error I'm getting is require function is used in a way in which dependencies cannot be statically extracted
I get the error from formidable which is relied on by Auth0.
Any ideas? It's reproducible in a fresh copy of the boilerplate.

Try using the new dynamic requires with webpack:
https://github.com/airbnb/babel-plugin-dynamic-import-webpack
http://2ality.com/2017/01/import-operator.html
import('some-module')
  .then(module => {
    module.foo()
  })

I managed to get it working with: new webpack.DefinePlugin({ "global.GENTLY": false }),
I have no idea the implications of doing this.

Probably has to do with https://github.com/felixge/node-gently. I would recommend using dynamic imports tho

Could you clarify which module 'some-module' would be in this context, and what module.foo() would be also?
Because I'm not directly running the dependency, formidable, I'm not sure how I would go about this.

Look through the links in this comment: https://github.com/chentsulin/electron-react-boilerplate/issues/832#issuecomment-287568603. They explain what import() is and how to use it

@amilajack I understand your reluctance to look at this issue, but I think there's a problem here more unique to this boilerplate than you're thinking. I've been researching this for a few hours and could really use your input if you have a moment.
The problem OP is highlighting is an issue in node-formidable. There's an expression in the top of one their files that reads:
if (global.GENTLY) require = GENTLY.hijack(require);

The standard fix is to set GENTLY=false, which avoids require being overwritten
In your boilerplate, however, some plugin or webpack setting is changing this line to this:
var require;if (global.GENTLY) require = GENTLY.hijack(require);

This overwrites global require & breaks the module, which is not something the end user can fix.
If anything I think this is a bug in whatever is changing the expression, but I can't figure out what's doing it.
Do you have any ideas what might be declaring this var?
I thought it was class prop transform, but it looks like class prop transform also happens in stage-0 and maybe the env preset, so i'm not clear how to remove/isolate it w/o removing basically the entire babel config.

I can't speak to the accuracy of what @brandonmp posted, but I know that I ran into the problem trying to implement Auth0. I imagine Auth0 would get a lot of complaints about their package not working, but I don't see any reports of this problem there https://github.com/auth0/auth0.js
I also don't see the issue with this project demoing Auth0 in Electron: https://github.com/darkyen/pkce-demos
Again, I can't speak to the source of the problem. This is just some circumstantial evidence that suggests @brandonmp may be correct.

if anyone's having the same sorts of troubles @Slapbox  & i are describing w/ auth0, a quick-fix is to just require the minified script from the CDN in a

I'm getting 'require is not a function' when trying to use auth0

@AlexCatch , @gazzer82.
You'd probably have to add an alias as well. I was getting the same error with superagent and the fix mentioned was to use an alias as well. Have a look at this comment. Something similar should work for auth0 as well.
https://github.com/felixge/node-formidable/issues/337#issuecomment-264337905

I've created a repository with node-auth0 already bundled for anyone to use in their own project to avoid any issues with formidable and similar errors.
https://github.com/patrykkrawczyk/node-auth0-bundle
Just get the node-auth0-bundle.js file from the dist directory, place it in your project and reference it with import/require statements as such:
import { ManagementClient } from './libs/node-auth0-bundle'
import { AuthenticationClient } from './libs/node-auth0-bundle'


Fixed "Arithmetic operation resulted in an overflow." error

During normal operation I saw this error come up when running read scans. The variable was an int and can overflow if incremented past max. We start with a random value so it will be arbitrarily close to this max at init time. The value is now a uint so that it will go to 0 and not overflow when incremented past max.

The variable was an int and can overflow if incremented past max.

It should just wrap around to become negative, that doesn't break the roundrobin since it uses a modulo. In a sense that when you do
int.MaxValue + 1
It shouldn't throw an exception, did you see that happening?

Yes :) It happened and halted my calls. I was surprised as well since typically that exception will only fire if turned on. It should be off by default. This may be an issue with my project (I do build this client from source) but I figured that its better to make this sort of thing impossible since the sign is not important to the function of that counter.

Thanks for the contribution Bryan!


publish<EMAIL_ADDRESS>

Requested by: @antonpirker
Merge target: (default)
Quick links:

View changes
View check runs

Assign the accepted label to this issue to approve the release.
Leave the #retract comment under this issue to retract the release (original issuer only).
Targets

[ ] pypi
[ ] gh-pages
[ ] registry
[ ] github
[ ] aws-lambda-layer
[ ] sentry-pypi

Targets marked with a checkbox have already been executed.  Administrators can manually tick a checkbox to force craft to skip it.

Please wait with approving this release, we need to add some docs first! Thanks!


Change some enum underlying values

enum defaults to int which is a larger size than what most of our enums need (e.g. for appearance visualizers especially). Many could be bytes or ushorts instead.
AFAIK this still matters (from vague memory Q's compression would've made it not matter?) and should help reduce bandwidth slightly.

Seems simple, you can assign me to this.


How do i set it up

I have successfuly built and installed metacity-decor. I also downloadé a gnome tgeme that includes metacity tbeme. I set the theme using lxappearance. Then i put the name of the metacìy theme in theme section of the plugin using wcm. I actovated the plugin but nothing happened. Seems am not doing something right.
Please help me have the correct setup.
Thanks

You should set the theme through wayfire.ini

In addition, use # instead of #

Thanks for your response. Please what's the configuration syntax to set matacity theme in wayfire.ini

See metadata/metacity-decor.xml

Thanks a lot. I got it set up and working perfectly. Awesome!
On Sat, 3 Aug 2024 at 11:08, Edwin Lau @.***> wrote:

See metadata/metacity-decor.xml
—
Reply to this email directly, view it on GitHub
https://github.com/marcof-nikogo/metacity-decor/issues/1#issuecomment-2266662269,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKBRKHYZBK44P3ESB64IVETZPST3NAVCNFSM6AAAAABJWTS5MOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRWGY3DEMRWHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Built on Debian stable against wayfire 0.8.0


As a user I want to know what the (gas) fees are for sending messages so that I can set up a schedule that makes sense for me.

Closing and moving to Volume EPIC.


Raise deployment target to OS X 10.11 El Capitan

Relevant discussion: #1217

Any thoughts on going further than this (with 10.16 11.0 on the horizon)?

Any thoughts on going further than this (with 10.16 11.0 on the horizon)?

Based on https://github.com/ViennaRSS/vienna-rss/projects/5 we already have a lot to gain by moving to 10.11, so perhaps we should start there, and then look at the 10.12 stuff after?

This has been dragging on for years, so I'm give it 72 hours for comment and then merge it by the weekend.

@Eitot if you can please update the README.md file to reflect the new minimum supported versions and remove the draft label, then I will approve it.

Merging based on https://github.com/ViennaRSS/vienna-rss/issues/1217#issuecomment-450607954


Adding Prometheus Rule for Dead Man's Snitch API Call

In a previous PR, the metric was exposed without a corresponding alert. This PR adds an alert to fire when the API is unreachable for 15 minutes.

/approve


update fa/yii.php

Q
A

Is bugfix?
no

New feature?
no

Breaks BC?
no

Tests pass?
no

Fixed issues
none

in persian we never use plural type of these words.
i.e. 5 روز
not 5 روزها

@jafaripur seems you have added these lines, can you comment on this change?

seems to be in line with https://github.com/yiisoft/yii2/commit/e093e77027d0792dc66b83ad709923a8daeb7cb2 , @emadgh can you please check this change and confirm this is correct?

@cebe Yes translations for number or month can use without plural.

okay, thanks for the quick response!

merged, thank you!


control_plane/attachment_service: complete APIs

Depends on: https://github.com/neondatabase/neon/pull/6468
Problem
The sharding service will be used as a "virtual pageserver" by the control plane -- so it needs the set of pageserver APIs that the control plane uses, and to present them under identical URLs, including prefix (/v1).
Summary of changes

Add missing APIs:

Tenant deletion
Timeline deletion
Node list (used in test now, later in tools)
/location_config API (for migrating tenants into the sharding service)

Rework attachment service URLs:

/v1 prefix is used for pageserver-compatible APIs
/upcall/v1 prefix is used for APIs that are called by the pageserver (re-attach and validate)
/debug/v1 prefix is used for endpoints that are for testing
/control/v1 prefix is used for new sharding service APIs that do not mimic a pageserver API, such as registering and configuring nodes.

Add test_sharding_service.  The sharding service already had some collateral coverage from its use in general tests, but this is the first dedicated testing for it.

Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.
[ ] Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
[ ] If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

[ ] Do not forget to reformat commit message to not include the above checklist

Mostly just for my curiosity, did you by any chance consider using sqlite? It seems like an in-process database could save some complexity.

Mostly just for my curiosity, did you by any chance consider using sqlite? It seems like an in-process database could save some complexity.

Yes -- postgres is used because that's what we'll use in production: I don't want to test against a different database than we run with.  It also simplifies life to avoid dealing with two SQL dialects.  The impact to  test  runtime from adding a postgres process is very small, but if we want to eliminate it I'd do it by just adding a non-persistent mode to the attachment service (i.e. use no database at all), since in most tests it is never restarted.

Also regarding tenant_location_config: I didn't keep up with all the changes, but, is this the first API that allows configuring a (single-)sharded tenant?

Yes, although it has allowed it for some time already: because tenant creation is really just an attach, one can create a multi-sharded tenant by issuing a series of /location_config calls to shards.

Regarding tenant_location_config: would prefer if, isntead of special-casing creation later, it would detect the need to create first, do it if necessary, then enter common code path of update. Rationale: it de-special-cases the creation to some extend. Doesn't have to be this PR though.

This code is refactored in https://github.com/neondatabase/neon/pull/6521 -- the create and update paths are still separate, but in a more obvious way that avoids having to read back and forth in the function.


fix yarn.lock folder bug

There is an error when you use npm as package manager. docker-compose mounts yarn.lock inside the docker image. If you're not using yarn, docker creates a yarn.lock folder and you will get an error if you want to install another package. This patch fixes this issue.

Nice thank you for this @YEK-PLUS  will get this merged in.

:tada: This PR is included in version 1.12.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Feat: add KEP of cloud resource data passing

Signed-off-by: Qiaozp<EMAIL_ADDRESS>Description of your changes
Add KEP to conclude the discussion in https://github.com/kubevela/kubevela/issues/4339

Fixes #
I have:

[x] Read and followed KubeVela's contribution process.
[ ] Related Docs updated properly. In a new feature or configuration option, an update to the documentation is necessary.
[x] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

Special notes for your reviewer

ping @Somefive


Ruby 3.0.2 bundle install tries to install rubysl

Subject of the issue
Ruby 3.0.2 bundle install complains on rubysl.
Works with Ruby 2.6.5.
$ bundle
Fetching gem metadata from https://rubygems.org/.........
Resolving dependencies...
Bundler found conflicting requirements for the Ruby version:
  In Gemfile:
    Ruby

    rspec-expectations was resolved to 3.10.0.pre, which depends on
      Ruby (>= 1.8.7)

    rubysl was resolved to 1.1.0, which depends on
      rubysl-irb (~> 1.0) was resolved to 1.0.2, which depends on
        Ruby (~> 1.8.7)

This gets evaluated somehow:
platforms :rbx do
  gem 'rubysl'
end

Your environment

Ruby version: 3.0.2
rspec-expectations version: HEAD

Steps to reproduce
export USE_GIT_REPOS=1
rvm use 3.0.2
bundle

Expected behavior
Bundle install should succeed.
Actual behavior
See error above.

I'm not sure thats up with your local bundler, try ensuring its on the latest version, that platform should only be run on rubinius.

Btw, it looks similar to https://github.com/rubygems/bundler/issues/2774.


integrate videojs

hello, is there any plan to integrate videojs or other video player?
here is a vue version of videojs  [https://www.npmjs.com/package/vue-video-player]

Yes, we're planning this feature, as a matter of fact we were already tinkering with it. :)

Great..


Consider exposing Colr::ResolvedPaint paint parameter value types to f32

Similar to how we expose metrics as f32 but ensure their resulting value is computed the same way as in FreeType, I think we should expose the resulting COLRv1 parameters in ResolvedPaint as f32 for consistency with metrics.
Thoughts? Was there a particular reason for exposing them as Fixed so far?

While we don’t have an explicit policy, so far we’ve generally avoided floating point in read-fonts and have tried to keep the model as close to the specification as possible. This also facilitates direct comparisons to FT as ResolvedPaint is a fairly close match to FT_COLR_Paint.
That said, this particular code does substantial processing so could be an exception. If you’re not making use of this directly in the Skia ffi code, we could arguably just move it to skrifa as a private module and modify it as needed.

Good point about the boundary between skrifa and read_fonts with regards to what data types to use. I think I can do the conversions on the Skrifa side then when implementing the COLRv0/v1 driver.


adding yaml def and dbt tests for action_network full_refresh

Generated a models yaml file and added some appropriate tests to fields like id and _airbyte_*_hasid.

yeah wow you know it's a good time when Github won't load the diff for the only file added by the PR lol. @royconst can you confirm that these tests pass when running dbt locally?

Yes, can confirm. 960 tests all passed. @emily-flambe


[Terra] Update terra block explorer

Latest will be columbus-5 https://twitter.com/terra_money/status/1432927061849427968

don't merge this yet, Terra team might add url redirect support later

this still works after columbus-5, let's merge it anyway


fix: Fixed spelling of 'ChaosCenter' in Sidebar Concepts section

Signed-off-by: hajowieland<EMAIL_ADDRESS>What this PR does / why we need it:
Just a small spelling fix in the Concept section of the sidebar in our documentation.
Special notes for your reviewer:
--

Also realized that there are other places too in the docs where the same error is present would you like to maybe do a global search and replace in the repo and fix all of them in this PR @hajowieland

@gdsoumya no worries - I replaced all occurrences of misspelled ChoasCenter with a global search and replace.

@hajowieland awesome thanks, will merge once ci completes


fix silently failing links

As noticed by @hrhotz some links were broken but not producing an error in vl
I changed vl to debug mode so that these errors at least show up in output (for example: here), even though job will still exit successfully,
also fixed any other links failing this way (many were due to using wrong scheme http/https)
remaining bad links:

bunch of reveal.js links in shared/slides/project_presentation.html but maybe we can just remove that now that we've moved to remark? (@bebatut?)
https://www.genome-cloud.com/ in topics/introduction/tutorials/options-for-using-galaxy/slides.html not sure where that should point

@shiltemann I will clean any mention to reveal.js (in an other branch...)

@shiltemann I will merge this one and open an issue for the link in topics/introduction/tutorials/options-for-using-galaxy/slides.html

@shiltemann Thanks a lot!


Blank parameters.

Hello,
How I can get parameters from device where parameter is "Blank"
Example:
InternetGatewayDevice.LANDevice.1.WLANConfiguration.1.PreSharedKey.1.PreSharedKey blank

GitHub is for defect tracking, not support requests. Please close this issue and your question on the mailing list or discourse page.
-dan

On Mar 28, 2019, at 2:24 AM, lcielec<EMAIL_ADDRESS>wrote:
Hello,
How I can get parameters from device where parameter is "Blank"
Example:
InternetGatewayDevice.LANDevice.1.WLANConfiguration.1.PreSharedKey.1.PreSharedKey blank
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Fixed bug in filename variable, add README and requirements files

Fixed bug related to filename variable in app.py
removed unused imports
added minimal README.md with screenshoot
added requirements.txt and requirements-dev.txt

Thanks, @izikeros :)


Missmatch between dev / build for typescript files with ?url

Describe the bug
I am trying to import a typescript file with ?url in my application.
I would like to get the file back with already stripped types (so as a js file). This is what happens in dev mode. In production mode, the file is left untouched and I get the raw typescript source.
The documentation is not very clear about what should happen, but I would argue, that this missmatch is a bug.
Reproduction
https://stackblitz.com/edit/vitejs-vite-rdougd?file=main.js,test.ts&terminal=dev
Steps to reproduce

Run npm dev to get the typescript compiled to js.
Run npm build && npm preview to get the typescript in its raw form
Observe, that there is a missmatch

System Info
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.18.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    vite: ^5.2.11 => 5.2.11

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Duplicate of #6757


No code is the most important, it is perfect!

No code is better than every line of code! Learned,today!

I hope there is no more code in the world !


Atom forgot the previous open status.

Description
Open multi project in the same same window, next time open, changed to separated window.
Steps to Reproduce

Open a project A.
Click file -> reopen project, select a project B.
Now the two projects are in the same window of atom, atom show two tabs on the top of window: A and B.
Close atom.
Open atom.

Expected behavior: The two tabs show in the same atom window as previous open time.
Actual behavior: Sometimes atom opens two separated window for the two projects, sometimes atom only open an empty window.
Reproduces how often: Frequently.
Versions
Atom : 1.17.0
Electron: 1.3.15
Chrome : 52.0.2743.82
Node : 6.5.0
OSX : Sierra 10.12.4

As part of this if I add a project folder to Atom from an empty window closing and reopening Atom has consistently lead to an empty window.
If I then reopen project (same project noted before) Atom opens a new window. If I then close the empty window and finally close the project window, reopening will open the project window.

It seems that the same window I mentioned in step 3 is a feature of OSX but not atom. So I think   this issue is not an exact issue.


Error: load selection timeout

Hey,
I have a "load selection timeout" error when doing ctx.get_contents(). I am sorry I don't get much output, but happy to provide more (I am new to Rust).
I am using ubuntu 17.10, rust 1.23.
I could not find anything related to that on the issues.
Let me know what I can do to give you more information.
Cheers

I'm not sure exactly how you're using rust-clipboard, but in X11 clipboard contents are not actually stored in the clipboard. Applications make the content available to the clipboard. If the clipboard is empty, or the most recent application (process) to have provided clipboard contents has exited, the clipboard will be empty, and you'll see this timeout error (at least I do, when using rust-clipboard).
You can verify this by copying something into the clipboard prior to running your code.

See #61. That's how I wound up here :-)


Make some dependencies optional

What maintenance does this project need?
Requirements file needs to be revised for earthkit-data as it installs too many things. We could solve that through optional dependencies in the toml config, for instance having an option to install all dependencies, or just a subset, or just the basic ones.
Organisation
ECMWF

At the moment, there are these sources requiring additional packages/libraries:

"cds", "ads": cdsapi
"mars": ecmwf-api-client
"ecmwf-opendata": ecmwf-opendata
"polytope": polytope-client
"wekeo", "wekeo-cds": hda
"fdb": pyfdb

We have two options to make any of them optional:

turn the source into a plugin. E.g. "polytope" source can be implemented as the"earthkit-data-polytope" plugin. So it will only be available when the user installs it (and this will install all its dependencies)
make the dependency optional in the config and print a proper error message when someone wants to use a source where the dependency is not installed.

There is also the question of the supported data file formats. The following list contains the current formats and their (Python) dependencies:
"grib": eccodes, (cfgrib, xarray for to_array)
"bufr": pdbufr
"odb": pyodc, (pandas for to_pandas)
"netcdf": netcdf4, xarray
"csv": (pandas for to_pandas)
Please note that when xarray is used currently dask is required too.

If we start by just making the dependency optional, I think it will be simpler/quicker.
Then later we can consider plugins, and separate repos etc.


Fixes of around 350 PSScriptAnalyzer warnings

This is the clean and rebased version with the split into 4 separate commits as requested by the original PR #4205
Most of them are fixes of PSPossibleIncorrectComparisonWithNull, PSAvoidUsingCmdletAliases (mostly for ForEach-Object, Where-Object, Select-Object) and some PSUseDeclaredVarsMoreThanAssignment warnings.
As part of this, it was also found that a test in ParameterBindingTests needed improvement because since the null comparison is now correct, the test failed initially and needed correcting.

@bergmeister,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

@bergmeister Thanks for your conttribution!
Wait maintainer's reviews.

@bergmeister Sorry, it seems @lzybkr meant that we should put each change kind in separate commit: %, ?, OutputType, $null and so on. I have no idea how this could be done now without a complete re-work.
@lzybkr Can we review as is?

If you do a soft reset, then git add -p, git will interactively ask you which diffs (not files, but individual diffs) to add. It's still time consuming, but it makes it much easier to manage big changes, e.g. if we need to use git bisect to narrow down a failure.

OK. I have created #4261, which contains the separation of the commits as requested and will close this one.


Unskip reflection unit test since proto is fixed

(merging since relevant tests were passed in Jenkins runs before Kokoro deployment)


Update CMake (IDFGH-7227)

Is your feature request related to a problem? Please describe.
Need to be able to user newer CMake version.
Describe the solution you'd like
Either update CMake to a newer version (current one is 20.3) or allow overriding it from the PS1 export script.
Describe alternatives you've considered
Additional context
CMake should be using the latest official version or, at least, one closer to it. The one being distributed with IDF 4.4.1 it's way outdated.
As an alternative it should be possible to easily override this. Currently overriding this is only possible by using the python utility in tools. It should be possible to pass the parameter to the PS1 script.

Thank you for the reminder @josesimoes. We were going to upgrade the bundled CMake version in relation to https://github.com/espressif/esp-idf/issues/4162. We will speed up the process.

Thanks! looking forward to it as currently I have to go around this with a bunch of hacks.
Nevertheless, please consider the suggestion to be able to pass the prefer-system option in export.ps1

In fact, I'm not sure why CMake is currently marked as "required" in tools/tools.json when installing on Windows. On macOS and Linux it is "optional". This allows the developer to use their own version of CMake. (Same for ninja.)
We'll see about making cmake and ninja also "optional" on Windows.

Hi. please, to update Cmake, where can I find the idf_tools.py file?
I'm running the instructions from this tutorial https://docs.espressif.com/projects/esp-idf/en/latest/esp32/get-started/linux-macos-setup.html and got stucked in the update step.
Sorry if it is the wrong topic or too much basic to ask here.


Where can I find more info about this Hformer?

Congrats on the release!
Where can I find more info about this Hformer? The blog post does not give many details.

Hi @jzhang38 , thx for your interest in our work! We will include more details in the technical report, which will be released later this week.

@jzhang38 Hi, thx for your interest in our work! We will include more details in the technical report, and it will take some time to prepare it.


[Documentation Update]: adding Naive Bayes algorithm under machine learning section

Is there an existing issue for this?

[X] I have searched the existing issues

Issue Description
i want to add the documentation for naive bayes classification algorithm under machine learning section.
Suggested Change
i will provide a detail documentation of naive bayes , its uses and applications and code details under documentation
Rationale
to increase the knowledge under machine learning section
Urgency
High
Acknowledgements

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository
[X] I have read and followed the Contribution Guidelines
[X] I have followed the code style guidelines of this project
[X] I have checked for any existing open issues that my pull request may address
[X] I have ensured that my changes do not break any existing functionality
[X] Each contributor is allowed to create a maximum of 4 issues per day. This helps us manage and address issues efficiently
[X] I have read the resources for guidance listed below
[X] I have not used AI-generated content (e.g., ChatGPT, other AI tools)
[X] I have not used content from existing sites (e.g., text, images)
[X] I have followed all security rules and only shared trusted resources

@Ajay-Dhangar please assign this issue to me along with level and label


Rebrand to SLED

What's Wrong with SLC?
Unintuitive pronunciation
SLC (Spatial Lighting Controller) is supposed to be pronounced "silk," but nobody would ever pick up on that without that being explained. Feels like it's trying too hard.
Name Adds Little Character to the Branding
What's so "silky" about this library anyways? If I push hard enough I could try to spin that into a message about being super smooth and lightweight, but I feel like we can do much better.
Benefits of SLED (Spatial LED)

For starters, it actually spells the word it's pretending to be.
A sled better represents the aspirations of the project: sleek, lightweight, fast and sturdy.
With a goal of breaking away from just room lighting control, SLED at least thematically has a better tie in with the next major application for this library: Christmas lights.
Opens the door to a much cuter api, heavily inspired by Rocket. (Not final lol)let mut sled = SLED::new("path/to/config/file");
sled.set_control("Color", RGB(1.0, 0.0, 0.0));
sled.set_control("Brightness", 1.0);

sled.set_driver(|controls| {
  let (r, g, b) = controls.get::<RGB>("Color")?;
  let brightness = controls.get::<F32>("Brightness")?;

  println!("Final color is: ({}, {}, {})",
    r * brightness, g * brightness, b * brightness
  };

  Ok(())
});

loop {
  sled.step();
}

More specifics on the rearchitecting will be handled in a different issue.

Moving from an issue to a discussion; closing.


feat: lint-staged

I noticed that projects were not currently husky and I added

I appreciate the effort here, but I'm personally not a fan of project-level git hooks in general. I just let my editor format and lint, and let CI prevent anything from falling through the cracks.


chore(rspack): skip multi compiler pressure test

(which may be the source of crashing in CI)

skip_ci

[skip ci]


Score format maybe outdated in the tutorial and readme

I found that the returned score format is perhaps outdated in this tutorial:
https://www.brain-score.org/tutorial/quickstart
and the readme on the github page:
https://github.com/brain-score/vision
xarray.Score (aggregation: 2)
array([0.01538053, 0.00571393])
Coordinates:
* aggregation  (aggregation) U6 'center' 'error'
Attributes:
raw:                   xarray.Score (aggregation: 2)>\narray([0.10192326...
ceiling:               xarray.Score (aggregation: 2)>\narray([8.21840601...
model_identifier:      pixels
benchmark_identifier:  dicarlo.MajajHong2015.IT-pls

In my recent usage, I believe the aggregation is removed and should be replaced by something like score.item() and score.error.item()?

Hey @YudiXie thanks for catching this! You are correct, and I will update it tomorrow. This is also related to your other issue (#563), so I will address this tomorrow as well. Thanks again!


Open iamge folder <-> Save folder modifier

When "Save folder modifier" is active:
"Open image folder" should open the folder in with the last screenshot - taken with the specific profile - was saved.

Done :^)


Forestry calls from public and ui tweaks

Description

Types of changes

Checklist

[ ] I have read the CONTRIBUTING doc
[ ] I have checked that unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments

SonarQube Analysis: https://sonarqube-vmvfjv-tools.pathfinder.gov.bc.ca/dashboard?id=common-forms-toolkit-pr-89


Fix package adding missed commit

Missed a commit in the last PR to fix solution package
Type of Change

[ X] Bug Fix

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@2b2ef9b). Click here to learn what that means.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main      #22   +/-   ##
=======================================
  Coverage        ?   30.28%
=======================================
  Files           ?       23
  Lines           ?     2998
  Branches        ?        0
=======================================
  Hits            ?      908
  Misses          ?     2021
  Partials        ?       69

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


Don't crash couch_index_server if the db isn't known yet

Overview
If a ddoc is added immediately after database creation (_users and
_replicator when couchdb is used in a multi-tenant fashion), we can
crash couch_index_server in handle_db_event, as mem3_shards:local
throws an error.
Testing recommendations
Create new $prefix/_replicator ddocs while under heavy indexing load elsewhere and observe a crash without this patch, and no crash with it.
Related Issues or Pull Requests
#3068
Checklist

[x] Code is written and works correctly
[ ] Changes are covered by tests
[ ] Any new configurable parameters are documented in rel/overlay/etc/default.ini
[ ] A PR for documentation changes has been made in https://github.com/apache/couchdb-documentation

Good catch!

Please, please backport this to 3.x.


Manson (BK Precision) power supplies

The BK Precision 9103/9104 power supply supports a serial protocol described in the Programming Manual.
The protocol uses CR line endings. Each successful command receives a reply of OK\r. Volts and amps are multiplied by 100. Here are examples of the basic commands. Note the magic 3, more on that below.
These can be tested at the command line with:
$ picocom -b 9600 --echo --omap lfcr --imap crcrlf /dev/cu.usbserial-0001

Command
Example output
Explanation

SOUT 1

Set output on

SOUT 0

Set output off

GOUT
0
Output is 0=off, 1=on

GETD
1002 0045 0
Presently outputting 10.02V, 0.45A, 0=CV mode vs 1=CC mode

GETS 3
1000 0050
Present settings (whether outputting or not) are 10.00V, 0.50A

VOLT 31000

Set present voltage setting to 10.00V

CURR 30021

Set present current setting to 0.21A

GOVP
4270
Upper limit of voltage is 42.70V

GOCP
2040
Upper limit of current is 20.40A

ENDS

Unlock the button panel before disconnecting

The max power output for the 9103/9104 is 320W. The two models just vary by their voltage/current limits. I do not know how to identify which the device is.
Other models of BK Precision power supplies use a similar protocol but there are variants like, "current value will have one decimal place for models 1687B, 1688B, 1900B, 1901B, and 1902B, and two decimal places for Model 1685B."

Above I've ignored the "preset" feature of the power supply, which is complicated, but in brief: Many of the command operands take a prefix of 0-3, where 3 means "the value it is set to now" and 0-2 mean "the stored value for preset A, B, or C". For example: VOLT 01000 sets Preset A voltage to 10.00V, whereas VOLT 31000 sets the output voltage to 10.00V.
Presets can also be used to create a program that switches between presets automatically at intervals.

I think there's an undocumented command GMOD which returns some kind of model identifier. Their PSCS program has some logic that tries to identify the model using the first digit. Pseudocode:
      if (response.startsWith("8"))
        return "SSP" + response;
      if (response.startsWith("6"))
        return "KPS" + response;
      if (response.startsWith("NTP5"))
        return "NTP" + response.substring(3);
      if (response.startsWith("SDP"))
        return "SDP" + response.substring(3);
      return response.startsWith("-", "");

My model returns 8320 which would translate to the model SSP8320 which points to (drumroll) the Manson SSP-8320. Gasp!
This Python project (N.B.: GPLv3) has more info about all the Manson models and which ones are resold as BK Precision.

Doesn't look too complicated, I can try to throw something together quickly when I get a chance. But it's always tricky to develop without having hands on the hardware.


boards: arm: Reset Ethernet PHY after system timer on mimxrt1xxx_evk's

Moves the Ethernet PHY reset routine on mimxrt1xxx_evk boards to execute
in the POST_KERNEL initialization level rather than the PRE_KERNEL_2
level because it relies on a kernel service, k_busy_wait(). Leverages
the existing CONFIG_PHY_INIT_PRIORITY to allow users to configure when
within the POST_KERNEL level this routine occurs, which by default is
set correctly to the following order:
Init Function			Init Level	Priority
--------------------------------------------------------------------------------------
sys_clock_driver_init		PRE_KERNEL_2	CONFIG_SYSTEM_CLOCK_INIT_PRIORITY=0
mcux_igpio_##n##_init		POST_KERNEL	CONFIG_KERNEL_INIT_PRIORITY_DEFAULT=40
mimxrt1064_evk_phy_reset	POST_KERNEL	CONFIG_PHY_INIT_PRIORITY=70
eth_init			POST_KERNEL	CONFIG_ETH_INIT_PRIORITY=80
net_init			POST_KERNEL	CONFIG_NET_INIT_PRIO=90

This fixes an issue that was introduced in commit
f0b3146ff5538e5381318a309fec292d3fbb1f3f, which caused the system timer
to be initialized after the Ethernet PHY reset. As a result, the
k_busy_wait() never returned and the kernel never finished booting. The
serial driver never initialized and there was no output on the console,
not even a boot banner.
Tested on the mimxrt1064_evk board with samples/net/dhcpv4_client.
Signed-off-by: Maureen Helm<EMAIL_ADDRESS>Fixes #38186
cc: @ainguraXmarquiegui

Compliance failure is due to the table in the commit message

@dleach02, @hakehuang - are you able to ack?

Tested mimxrt1050_evk and mimxrt1020_evk.
I used c8c3d32a0f126e449924fc3cbe0ed5d7d3cbadfa from main and cherry-picked bea067f041c5dab3913040a3be84722308d1e6b4 .
Using test samples/net/zperf both boards boot and can be ping-ed.


fix(ion-datetime): remove log on deceleration

Short description of what this resolves:
DateTime is very slow on mobile devices, especially Android
Changes proposed in this pull request:

Do not log on each deceleration

Ionic Version: 2.x
Fixes: #8515

Thanks, look like this got fixed as well by 713e2a1a33ded9dd238a3babe16db72c2f751741


Sway user config theme definition

Hi,
First, thank you for this great distribution for my RaspberryPi 4!
Sadly I cannot figure how to customize the desktop theme...without modifying it in /etc/sway of course.
I have this in my ~/.config/sway/config
include /etc/sway/definitions

set $mod Mod4
set $term xterm
set $theme /etc/sway/themes/matcha-green
set $background ~/wallpaper.jpg
set $gui-font DejaVu Sans 13
set $term-font Inconsolata 13
input * xkb_numlock enable

include /etc/sway/inputs/*
include /etc/sway/outputs/*
include /etc/sway/modes/default
include /etc/sway/modes/resize
include /etc/sway/config.d/*

Some of my values are applied : $mod, $term, $theme, input
But not these : $background, $gui-font, $term-font
I really had hard time to understand, I thought it will be a problem of ordering but I believe I almost tried every possible combination...without success
Any advice?

For the $background variable I have noticed that the '~' symbol doesn't work, but the use of $HOME usually does work...
for the other variables, I think maybe the use of quotas will help...

Not better with $HOME sadly...
What do you mean by "the use of quotas"?


Is it supported to have more than one SIGNING_SECRET per app?

When managing multiple bots under the same server, it would be useful to have only one bolt.App Instance and verify requests
given a set of signing secrets instead of just one
Reproducible in:
Latest bolt version
slack-bolt==1.1.4
slack-sdk==3.1.0
Python 3.8.6

If not possible, what's the recommended approach? One server pero bot?

I extend the question for any way to having multiple WebClients with different tokens available through dep injection to use one client or another one depending on the command

I extend the question for any way to having multiple WebClients with different tokens available through dep injection to use one client or another one depending on the command

Hey there, not sure if this is useful but I am currently trying to achieve the same objective. If you are using Flask for your applications, you will know that you need to use a SlackRequestHandler to route your requests through Flask and then onto your applications.
What I was thinking is that you could intercept the request before it is handled and dynamically update your token and signing_secret values by reassigning the app._token and app._signing_secret variables. However I noticed that you try to determine where the request came from before it is handled you will get a 401 status code when it is passed on to the handler. Quite a strange side-effect.

Hey there, not sure if this is useful but I am currently trying to achieve the same objective. If you are using Flask for your applications, you will know that you need to use a SlackRequestHandler to route your requests through Flask and then onto your applications.
What I was thinking is that you could intercept the request before it is handled and dynamically update your token and signing_secret values by reassigning the app._token and app._signing_secret variables. However I noticed that you try to determine where the request came from before it is handled you will get a 401 status code when it is passed on to the handler. Quite a strange side-effect.

Context.
`
Relevant imports.
app = App(
# token=os.environ.get("BOT_ACCESS_TOKEN"),
# signing_secret=os.environ.get("SLACK_SIGNING_SECRET")
)
@flask_app.route("/slack/events", methods=["POST"])
def slack_events():
# Depending on where the request came from as your bot may be unique per team.
team = request.form['team-domain']
if team == "a":
    app._token = team_a_token
    app._signing_secret = team_a_signing_secret
else:
    # Some other token.

return handler.handle(request)

`

Context.
`
Relevant imports.
app = App(
# token=os.environ.get("BOT_ACCESS_TOKEN"),
# signing_secret=os.environ.get("SLACK_SIGNING_SECRET")
)
@flask_app.route("/slack/events", methods=["POST"])
def slack_events():
# Depending on where the request came from as your bot may be unique per team.
team = request.form['team-domain']
if team == "a":
    app._token = team_a_token
    app._signing_secret = team_a_signing_secret
else:
    # Some other token.

return handler.handle(request)

`

I am yet to test this as I am trying to understand why am I getting a 401 status code after looking at the response, but will keep you updated if I find a way around this.

I am yet to test this as I am trying to understand why am I getting a 401 status code after looking at the response, but will keep you updated if I find a way around this.

Thank you for your help @cookieplug. What i did to workaround this limitation is manage bolt apps as blueprints, and then dividing them by routes. Something like this:
from bot_a import bolt_app
from bot_b import bolt_app as bolt_app_b
from slack_bolt.adapter.flask import SlackRequestHandler as FlaskToChalice

app = Flask(__name__)

bolt_adapter = FlaskToBolt(app=poll_bolt_app, chalice=app)
bolt_adapter_b = FlaskToBolt(app=poll_bolt_app_b, chalice=app)

@app.route('/first')
def first():
    return bolt_adapter.handle(app.current_request)

@app.route('/second')
def first():
    return bolt_adapter.handle(app.current_request)

And then each bolt_app has the proper signing secret and bot token

Thank you for your help @cookieplug. What i did to workaround this limitation is manage bolt apps as blueprints, and then dividing them by routes. Something like this:
from bot_a import bolt_app
from bot_b import bolt_app as bolt_app_b
from slack_bolt.adapter.flask import SlackRequestHandler as FlaskToChalice

app = Flask(__name__)

bolt_adapter = FlaskToBolt(app=poll_bolt_app, chalice=app)
bolt_adapter_b = FlaskToBolt(app=poll_bolt_app_b, chalice=app)

@app.route('/first')
def first():
    return bolt_adapter.handle(app.current_request)

@app.route('/second')
def first():
    return bolt_adapter.handle(app.current_request)

And then each bolt_app has the proper signing secret and bot token

Thanks for sharing the thoughts here! These should be helpful for others too. Let me add my comments here.
We are not planning to add the feature to automatically switch multiple signing secrets in a single Bolt app at this time. In line with this, having separate endpoints is a recommended way for running multiple Bolt apps in a single Web app instance (as @Ambro17 shared above). A concrete example can be like this:
from slack_bolt import App
from slack_bolt.adapter.flask import SlackRequestHandler

app_a = App(signing_secret="secret-a", token="xoxb-a")
app_b = App(signing_secret="secret-b", token="xoxb-b")

@app_a.command("/app-a-command")
def app_a_command(ack):
    ack("This is App A!")

# To share a single listener among multiple apps,
# You can use non-decorator registration
def say_something(body, say, logger):
    logger.info(body)
    say("What's up?")

app_a.event("app_mention")(say_something)
app_b.event("app_mention")(say_something)

# To simplify above, you can go wit this
apps = [app_a, app_b]
for app in apps:
    app.event("app_mention")(say_something)

from flask import Flask, request

flask_app = Flask(__name__)
# Flask handler for App A
handler_a = SlackRequestHandler(app_a)
# Flask handler for App B
handler_b = SlackRequestHandler(app_b)

# Request URL for App A
@flask_app.route("/slack/app_a/events", methods=["POST"])
def slack_app_a_events():
    return handler_a.handle(request)

# Request URL for App B
@flask_app.route("/slack/app_b/events", methods=["POST"])
def slack_app_b_events():
    return handler_b.handle(request)

dynamically update your token and signing_secret values by reassigning the app._token and app._signing_secret variables

I don't recommend this approach. There are two reasons. Firstly, as the field names start with _, they are private. We may change the internals in the future. The second one is more important. The values are shared among request handers. Thus, modifying them at runtime causes race condition issues when handling simultaneous requests.

I extend the question for any way to having multiple WebClients with different tokens available through dep injection to use one client or another one depending on the command

You can use global/listener middleware to inject anything to a context arg.
database = {}

@app.middleware
def set_web_clients(context: BoltContext, next):
    user_token = database.get(context.user_id)
    if user_token is not None:
        context["user_token_client"] = WebClient(token=user_token)
    next()

@app.event("app_mention")
# or @app.event("app_mention", middleware=[set_web_clients]) if you apply the middleware only for this listener
def event_test(context: BoltContext):
    user_client: WebClient = context["user_token_client"]
    search_result = user_client.search_messages(query="my message")
    do_something(context.user_id, search_result)

Hope this was helpful to you.

Thanks for sharing the thoughts here! These should be helpful for others too. Let me add my comments here.
We are not planning to add the feature to automatically switch multiple signing secrets in a single Bolt app at this time. In line with this, having separate endpoints is a recommended way for running multiple Bolt apps in a single Web app instance (as @Ambro17 shared above). A concrete example can be like this:
from slack_bolt import App
from slack_bolt.adapter.flask import SlackRequestHandler

app_a = App(signing_secret="secret-a", token="xoxb-a")
app_b = App(signing_secret="secret-b", token="xoxb-b")

@app_a.command("/app-a-command")
def app_a_command(ack):
    ack("This is App A!")

# To share a single listener among multiple apps,
# You can use non-decorator registration
def say_something(body, say, logger):
    logger.info(body)
    say("What's up?")

app_a.event("app_mention")(say_something)
app_b.event("app_mention")(say_something)

# To simplify above, you can go wit this
apps = [app_a, app_b]
for app in apps:
    app.event("app_mention")(say_something)

from flask import Flask, request

flask_app = Flask(__name__)
# Flask handler for App A
handler_a = SlackRequestHandler(app_a)
# Flask handler for App B
handler_b = SlackRequestHandler(app_b)

# Request URL for App A
@flask_app.route("/slack/app_a/events", methods=["POST"])
def slack_app_a_events():
    return handler_a.handle(request)

# Request URL for App B
@flask_app.route("/slack/app_b/events", methods=["POST"])
def slack_app_b_events():
    return handler_b.handle(request)

dynamically update your token and signing_secret values by reassigning the app._token and app._signing_secret variables

I don't recommend this approach. There are two reasons. Firstly, as the field names start with _, they are private. We may change the internals in the future. The second one is more important. The values are shared among request handers. Thus, modifying them at runtime causes race condition issues when handling simultaneous requests.

I extend the question for any way to having multiple WebClients with different tokens available through dep injection to use one client or another one depending on the command

You can use global/listener middleware to inject anything to a context arg.
database = {}

@app.middleware
def set_web_clients(context: BoltContext, next):
    user_token = database.get(context.user_id)
    if user_token is not None:
        context["user_token_client"] = WebClient(token=user_token)
    next()

@app.event("app_mention")
# or @app.event("app_mention", middleware=[set_web_clients]) if you apply the middleware only for this listener
def event_test(context: BoltContext):
    user_client: WebClient = context["user_token_client"]
    search_result = user_client.search_messages(query="my message")
    do_something(context.user_id, search_result)

Hope this was helpful to you.

Thank you for your example @seratch!
I think this might be a recurrent question once one starts to divide functionality in more than one bot but one web server.
Perhaps it might be useful to give it a place in the docs so we can find it more quickly,
What do you think?

Thank you for your example @seratch!
I think this might be a recurrent question once one starts to divide functionality in more than one bot but one web server.
Perhaps it might be useful to give it a place in the docs so we can find it more quickly,
What do you think?

Welcome back @seratch! Thanks a lot for the insightful comments, the approach both yourself and @Ambro17 have suggested definitely seems like the way to go. Not sure why I didn't think of using 2 app instances sooner!

Welcome back @seratch! Thanks a lot for the insightful comments, the approach both yourself and @Ambro17 have suggested definitely seems like the way to go. Not sure why I didn't think of using 2 app instances sooner!

I think this might be a recurrent question once one starts to divide functionality in more than one bot but one web server.
Perhaps it might be useful to give it a place in the docs so we can find it more quickly,
What do you think?

Thanks for the suggestion! Currently, the team is updating the documents as preparation for Socket Mode release #159 - after finishing the task, let me revisit this. We may update the part on adapters to have an additional line that navigates developers to this issue.
As I've provided answers to all the questions here, allow me to close this issue now.

I think this might be a recurrent question once one starts to divide functionality in more than one bot but one web server.
Perhaps it might be useful to give it a place in the docs so we can find it more quickly,
What do you think?

Thanks for the suggestion! Currently, the team is updating the documents as preparation for Socket Mode release #159 - after finishing the task, let me revisit this. We may update the part on adapters to have an additional line that navigates developers to this issue.
As I've provided answers to all the questions here, allow me to close this issue now.


Gravatar

This change assumes that the email encryption branch is merged first.  It looks like a lot of changes, but it's not; it's almost all tweaks to the tests so they support VCR cassettes.

LGTM


Can we update dependencies

Hi Team, I just created a basic Vue JS app while learning Vue and found this plugin has a fair bit of outdated dependencies that npm audit flags.
I have tried updating the dependencies in my fork here, but I am just not familiar enough with Vue to test this out.
If the fork looks reasonable I can create a PR.
Cheers

We’ll try to update the dependencies as soon as possible. Besides the results of npm audit, does the plugin work for you?

@Lorti Thank you very much. I shall revert my playground code and double check that the plugin works fine. With my fork it does throw an exception, haven't wrapped my head around, if it is my code or the test case or something else.

I updated and tested with yalc all works fine, I needed this in a god damn hurry so I've repacked it here https://www.npmjs.com/package/vue-cli-plugin-e2e-nightwatch-cucumber-repack


Capture session on background thread

Getting a warning for CameraController line 73
   captureSession.startRunning()

-[AVCaptureSession startRunning] should be called from background thread. Calling it on the main thread can lead to UI unresponsiveness

I've now fixed this, thanks!