Update Get-UserBriefingConfig.md

I'll ask Mathew A. to review these changes first because I'm not really sure about some of this.

Docs Build status updates of commit 2541e1f:
:clock10: Full build: the average full build time is 17 min(s) 11 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 2541e1f:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/powershell-v2-module/Get-UserBriefingConfig.md
:x:Error

Details

exchange/exchange-ps/exchange/powershell-v2-module/Get-UserBriefingConfig.md

[Error]

Failed to parse this MAML markdown file due to :33:(624) '```yaml
Type: String
Position: Named
Default va...'
 Invalid yaml: unknown key Applies to, please use PlatyPS to do content validation

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit a76db56:
:clock10: Full build: the average full build time is 17 min(s) 11 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit a76db56:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/powershell-v2-module/Get-UserBriefingConfig.md
:x:Error

Details

exchange/exchange-ps/exchange/powershell-v2-module/Get-UserBriefingConfig.md

[Error]

Failed to parse this MAML markdown file due to :33:(757) '```yaml
Type: String
Position: Named
Default va...'
 Invalid yaml: unknown key Applies to, please use PlatyPS to do content validation

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit ecef5b9:
:clock10: Full build: the average full build time is 17 min(s) 11 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit ecef5b9:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/powershell-v2-module/Get-UserBriefingConfig.md
:x:Error

Details

exchange/exchange-ps/exchange/powershell-v2-module/Get-UserBriefingConfig.md

[Error]

Failed to parse this MAML markdown file due to :47:(757) 'Not applicable'
 Expect Heading, please use PlatyPS to do content validation

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit cc52625:
:clock10: Full build: the average full build time is 17 min(s) 11 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit cc52625:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/powershell-v2-module/Get-UserBriefingConfig.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit eedde13:
:clock10: Full build: the average full build time is 17 min(s) 12 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit eedde13:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/powershell-v2-module/Get-UserBriefingConfig.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit e8e8303:
:clock10: Full build: the average full build time is 17 min(s) 12 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit e8e8303:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/powershell-v2-module/Get-UserBriefingConfig.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit d8df2b1:
:clock10: Full build: the average full build time is 17 min(s) 13 sec(s), this is based on the last 1000 build(s) for this repository.

@chrisda -ok, Mathew A. has approved this latest version, so please review and if you:

have edits, please email or ping me via Teams
approve, please publish when you're able.

Thanks for your time on this!

Docs Build status updates of commit d8df2b1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/powershell-v2-module/Get-UserBriefingConfig.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit c6e3c56:
:clock10: Full build: the average full build time is 17 min(s) 15 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit c6e3c56:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/powershell-v2-module/Get-UserBriefingConfig.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 729f35c:
:clock10: Full build: the average full build time is 17 min(s) 15 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 729f35c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/powershell-v2-module/Get-UserBriefingConfig.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 4b62623:
:clock10: Full build: the average full build time is 17 min(s) 19 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 4b62623:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/powershell-v2-module/Get-UserBriefingConfig.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


@orta => Update what is artsy link to the meta repo.

Replacing https://github.com/artsy/mobile/blob/master/what_is_artsy.md.

awesome, yep


Implement ADAPTIVE STORAGE OPTIMIZER

An adaptive optimizer helps optimize one aspect (e.g. row group size or column order) of HDFS wide tables adaptively. There are three type of adaptive optimizer:
Column Order Optimizer;
Row Group Size Optimizer;
Compression Codec Optimizer.
We are going to implement at least the first two in V2.0. Compression Codec Optimizer can be left to a later version.

Looks good to me.


Border Radiuses under rounded-lg broke after installing shadcn

Current Behavior
Can't use rounded- properties under rounded-lg, they have no effect.
Expected Behavior
I commented borderRadius
 borderRadius: {
lg: "var(--radius)",
md: "calc(var(--radius) - 2px)",
sm: "calc(var(--radius) - 4px)"
 },

Now it's working again.
Steps To Reproduce
I will write steps to reproduce soon, for now I think the issue seems to be that I installed it into an existing project?
Link to Reproduction / Stackblitz
No response
More Information
No response

I had to import the scss into the layout. Found this out after following the manual installation.
import "../app.postcss";


⚠ Bofrost.be has degraded performance

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

HTTP code: 200
Response time: 2693 ms

Resolved: Bofrost.be performance has improved in 01fa532.


Input history of commanded yaw offset

Y_MErrSet in the DISCON.IN can now take a scalar or a filename as input. If a filename is specified, the given file will be loaded expecting the following:

two white-space delimited columns with time and commanded offset
the file will be read until there are no more lines with numerical values

Outside of the above comment, this looks pretty good. Do you have a sample yaw time history file you could include as well?

Most of this has been included in newer versions of ROSCO with open-loop control enabled, and the yaw control updates have been made in: https://github.com/NREL/ROSCO/pull/145. Going to close


Add ID source: curated on-chain groups

The group will be maintained on-chain in a smart contract
Additions/modifications to group membership would be conditionally permitted by, for example, a DAO multisig.
Group membership queries should be accessible via the APIs to client apps. It should be transparent to the client app that the data is on-chain.

Example telegram bot: https://github.com/GazeCoin/tipdai.git (telegram branch)

Proposed flow:

Bot service runs on server
Telegram group admin adds the bot to the group
Bot commands: Join, Leave, Help
Join will create a magic link to interrep.link. This will allow connection to metamask in the usual way.
The magic link will identify the telegram user and group. Needed to prevent reuse.

Some requirements for the smart contract:

Data structures to support the merkle tree will be required: Leaves, then intermediate hashes at each level to the root. Zero hashes will be constants.
Updates to the merkle tree only allowed by the admin and authorised accounts.
An addLeaf method will accept a Semaphore ID commitment argument. This will be added as a new leaf to the MT. It will compute the hash, then all hashes in the path up to the root. A newRootHash event will be issued.
A findIdCommitment method will locate a given ID commitment, and, if found, return its index, path (including siblings), and the root hash. If the entry is not in the MT, return an error.
deactivateLeaf method will find a leaf, mark it as inactive, and compute new hashes along the path.
The contract should support multiple groups, with a separate MT for each.
Number of levels: Each group will have a defined number of levels.

The subgraph will need to refer to this contract in addition to the off-chain contract. The same schema entities will be added to. At least 1 additional attribute will be available: path


Proposal: New Collector API

Currently, the Collector, responsible for pulling together all of the streams, currently walks to children it's passed, convert onX callbacks to streaming callbacks. The API currently looks like this:
<Collector>
  <button onClick={e$ => e$.map(() => ({ type: "CLICK" })}>
    Click me.
  </button>
</Collector>

The issue here is twofold:

When I start writing a component that I want to stream events from, I often forget the collector. Implementing the button, from a React perspective, looks the same. This is both good, because it simplifies the transition, but not so good if it produces unexpected bugs. "Doing it wrong" should be clearer.
The onX callbacks can no longer be type-checked, because React's type definitions expect a function of SyntheticEvent => T but it's now Observable<SyntheticEvent> => Observable<T>. I really want to be able to fully typecheck a brookjs app, so solving this is required.

Instead, I'm proposing an API that looks like this:
<Collector>
    {collect => (
        <button onClick={collect(e$ => e$.map(() => ({ type: "CLICK" }))}>
            Click me.
        </button>
    )}
</Collector>

This makes it explicit that you need to wrap your event listener with the collect function, which is responsible for wrapping your function and providing a callback to React. In addition to this explicitness, collect can be typechecked to ensure they match.
The downside in the addition of some boilerplate: both the function children as well as the collect callback.
Alternative: HOC
Instead of wrapping in a component with a render children, we could make this a HOC that gets configured with the callbacks it needs. So an API like this:
const Button = ({ onClick }) => (
    <button onClick={onClick}>
        Click me.
    </button>
);

withCollector(Button, {
    events: {
        onClick: e$ => e$.map(() => ({ type: "CLICK" })
    }
});

We could flatten this configuration object if we wanted:
withCollector(Button, {
    onClick: e$ => e$.map(() => ({ type: "CLICK" })
});

But I'm suggesting the events key because it would allow us to include a combiner key as well, which would allow us to merge events however we'd like:
withCollector(Button, {
    combine: ({ onClick$, onChange$ }) => onChange$.sampledBy(onClick$)
    events: {
        onClick: e$ => e$.map(() => ({ type: "CLICK" }),
        onChange: e$ => e$.map(e => ({ type: "TYPE", value: e.target.value })
    }
});

And now the component will only event a typing event when a button is clicked. Collector current has preplug, which would allow you to do something similar, but it's a bit more cumbersome because we can't provide named streams to the preplug callback.
The counterpoint is it's not clear how to handle the "modify streams by context" use case. In the above example, the resulting Button only emits a CLICK action. In the current implementation, we can modify the values emitted thus:
<Collector preplug={src$ => src$.map(action => ({ ...action, type: 'FORM_CLICK' }))}>
    <Button />
</Collector>

This, when embedded in a larger component, allows leaf components to emit generic actions while the container components scope those actions based on their context.
The render children version can continue to function in this manner without issue; the HOC will likely need an API change. I'm envisioning the returned component itself would expose preplug:
const CollectedButton = withCollector(Button, {
    combine: ({ onClick$, onChange$ }) => onChange$.sampledBy(onClick$)
    events: {
        onClick: e$ => e$.map(() => ({ type: "CLICK" }),
        onChange: e$ => e$.map(e => ({ type: "TYPE", value: e.target.value })
    }
});

<CollectedButton preplug={src$ => src$.map(action => ({ ...action, type: 'FORM_CLICK' }))} />

If we're going to go with combine conceptually, we should provide the merged stream as well as access to the dependent streams, so something like this:
combine: (inst$, { onClick$, onType$ }) => onType$.sampledBy(onClick$);

We should then provide a helper function (withoutBy?) that you can use with #thru to get back a new stream with a provided stream removed:
combine: (inst$, { onClick$ }) => inst$.thru(withoutBy(onClick$));

would return a merged stream that contains onType$ alone.
This allows developers to say "I have a stream of 6 types of actions, and I want to interact with 2 of them and pass the rest on", they have a means of getting back a stream that to use in that way.
We should pull all of the Kefir helpers into a separate library as well.

Doing this as a high-order component has a couple nice things about it:

Inclusion of combine, which should also be called with the component's props.
Pass preplug directly rather than wrapping in another Collector.
Simpler markup for the component itself; gets decorated w/ additional logic rather than embedding it in JSX, which can be very verbose.
No breaking changes before 0.12.0 because we introduce it through a new HOC, and can deprecate Collector / Aggregator outright.

Still considering new names as well, and deprecating both Collector & Aggregator for these new components. Something stream-y / brook-y would be more this lib's style.

We're going with toJunction (Collector) & RootJunction (Aggregator). A Junction is a point where two rivers come together. We also considered Confluence, but it's Atlassian's product & a bit more esoteric.
Thank you WeAllJS Slack for helping with the naming!


Fix macOS/Bash 3.2 breakage; eliminate subshells from exec-test, preprocess

These changes produce some substantial performance benefits across all platforms, but most especially on Windows. I'm using them in the mainline of my own project as of https://github.com/mbland/go-script-bash/pull/165 (Travis CI results, Coveralls results).
If this PR contains too many changes at once, I'm happy to break it up. Also, I just noticed that this PR addresses #98, without even having looked at #122 before.
cc: @ztombol @stroupaloop
macOS fix
The first commit in this set fixes the three existing tests that failed for Bash 3.2.57(1)-release, the default version for macOS 10.12.3 and other earlier versions of macOS and OS X. This was due to the ERR trap not always firing as it should; adding some guard logic to bats_error_trap before calling it from bats_teardown_trap resolved the issue.
Performance impact on Bats's own test suite
The remaining commits methodically eliminate subshells to improve overall test performance, especially those spawned by bats_capture_stack_trace via bats_debug_trap.
Under Bash 3.2.57(1)-release on a MacBook Pro with a 2.9GHz Intel Core i5 CPU and 8GB 1867MHz DDR3 RAM, the timing for the original set of tests (which don't include the four test name-related cases added by one of the later commits in this series) run via bin/bats test/ went from:
  44 tests, 0 failures

  real    0m7.565s
  user    0m3.664s
  sys     0m3.368s

to:
  real    0m4.319s
  user    0m2.559s
  sys     0m1.454s

Performance impact on a large Bats test suite
In my https://github.com/mbland/go-script-bash project, I'd already optimized the tests to disable Bats stack trace collection almost as much as possible, bringing the time for the full ./go test suite on the same machine, OS, and Bash version from O(7-8min) down to the following at https://github.com/mbland/go-script-bash/commit/69ad67f8474522540c9f90d7fd4f93903aaa63ce:
  789 tests, 0 failures, 2 skipped

  real    2m57.196s
  user    1m30.371s
  sys     1m17.703s

Running again at the same commit, but using Bats with these changes included, the suite now runs in:
  real    1m24.217s
  user    1m1.195s
  sys     0m17.700s

Performance impact on Windows
The impact is even more dramatic on Windows. On the same MacBook Pro, running Windows 10 under VMware Fusion 8.5.3 with 4GB RAM, and the timing for ./go test before my changes to go-script-bash was in the O(50-60min) range for every version of Bash I have installed.  Afterwards, it was down in the O(20+min range).
Using Bats with these changes included, running the MSYS2-based Bash 4.3.46(2)-release that ships with (what is probably a slightly outdated version of) Git for Windows, the suite now runs in:
  real    6m20.981s
  user    1m53.852s
  sys     3m16.015s

Running Bash 4.4.11(2)-release running under Cygwin:
  real    5m22.506s
  user    1m34.462s
  sys     2m41.568s

And running Bash 4.3.11(1)-release as part of the Windows Subsystem for Linux (i.e. Ubuntu on Windows 10):
  real    3m40.502s
  user    0m36.531s
  sys     3m1.516s

Other versions tested
In addition to the Bash versions mentioned above, I've also tested these changes using the following Bash versions:

4.2.25(1)-release: the version from the default Ubuntu 12.04.5/Precise image on Travis CI
4.3.42(1)-release: the latest on Alpine Linux
4.3.46(1)-release: the latest on Ubuntu 16.10
4.4.12(0)-release: the version from FreeBSD 10.3-RELEASE-p11
4.4.12(1)-release: the latest at the time of writing, on both Arch Linux and macOS via Homebrew

All of the go-script-bash tests passed on these other platforms in less than half the time from before. All of the Bats tests passed on every platform with the exception of a few on Alpine Linux; I can perhaps address these failures in the future.
Future steps
There are other subshells that can likely be eliminated in other parts of Bats, particularly those that happen at startup when bin/bats is collecting information on the test suite, which introduces a bit of a startup pause proportional to the number of tests to run (especially noticeable on Windows). However, this seems like a good place to stop for now.

AMAZING!
I also noticed all those time spent in the debug handler and was trying to do something about that, but... These commits are great!
Unfortunately it seems you won't have your commits merged... :(

@ret2libc, fortunately there will be soon a new Maintainer(s) #150
You may know, how to merge the PR in your own fork?
http://stackoverflow.com/questions/6022302/how-to-apply-unmerged-upstream-pull-requests-from-other-forks-into-my-fork

@Sylvain303 Is there any news on #150 that hasn't been posted to that thread? There hasn't been any response to it since I threw my hat in the ring as a potential maintainer.
@ret2libc I've since done a few more optimizations, posted to my fork as the mbland/bats optimized-20170317. It's  effectively "done" in terms of optimizing by eliminating subshells and subprocesses. No improvements as dramatic as in this PR, but still substantial. I've debated posting them to this PR, or opening a new PR, but decided to wait until this one and #150 finally get traction.

@Sylvain303 thanks I'm already aware of that ;)
@mbland that's really cool, thanks. I hope this thing will get some attention soon.

Oh, and for anyone who isn't familiar with managing repos with multiple remotes, the Git commands to pull my changes into your repo should be something like:
$ git remote add mbland git@github.com:mbland/bats.git
$ git fetch mbland --tags
$ git checkout -b optimized optimized-20170317

To see the tag comments with the summaries (whereby optimized-20170205 corresponds to the branch used for #210):
$ git show optimized-20170205
$ git show optimized-20170317

@mbland, no, no special news for #150, I'm just optimist. :)
Coming back to your PR, here:
https://github.com/sstephenson/bats/pull/210/files#diff-669b297cddac27dc2ecc950eb92aa5fcL316
Are changes equivalent?
Previous version does deleting \r, does your version do the same?
I'm trying to merge your PR in my internal unittest. I'm using a "python trick like" sourcing detection:
#!/bin/bash
main() {
  echo "sourced=$sourced"
}

[[ $0 != "$BASH_SOURCE" ]] && sourced=1 || sourced=0

if [[ $sourced -eq 0  ]] ; then
   main "$@"
fi

My current bats-preprocess version (with your modifications).
As you changed in bats-exec-test, the internal behavior, I'm asking if it benefits for something here?
I mean sourcing it instead of executing it.
a sub-shell is spawned for:
$(< "$BATS_TEST_FILENAME")

It would be easier for me to keep source detection feature, than having to rely on some other trick.
More on bats-preprocess I feel it should perform input cleanup itself, but that may be another question/optimization.
Could you also enable issues, on your bats fork, so I can comment there?

@mbland, I found where you've handled '\r' dos end-of-line:
https://github.com/sstephenson/bats/pull/210/files#diff-e5a78c356c58edaf23c12ce3dae62023R39
great!


Unused inputs for _environmental_effect

Below is the _environmental_effect function:
function _environmental_effect(
    metacommunity,
    species,
    patch,
    generation,
    landscape::Matrix{Float64},
    environmental_optimum::Vector{Float64};
    h = 1.0,
    σ = 50.0,
)
    Δ = landscape[patch...] - environmental_optimum[species]
    ξ = 2σ^2.0
    modifier = exp(-(Δ^2.0) / (ξ))
    return h * modifier - h
end

Is there a reason we need to call/input metacommunity and generation? As far as I can tell we don't use them in the function so it seems unneeded?

It was a actually for a fourth secret reason that I opened the issue, which was that when I was trying to dig into the environmental effect it just felt weird. Vibes were shaky but not off.


Command are not working %python.command.python....%

Environment data

VS Code version: 1.33.1
Extension version (available under the Extensions sidebar): 2019.4.12954
OS and version: MAC 10.14.4
Python version (& distribution if applicable, e.g. Anaconda): python3.7.3
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A

Expected behavior
Used all command with CMD+SHIT+P
Actual behavior
All python commands are in the format Python: %python.command.python....%
I don't know why I have this issue, I cannot use this extension. Everything is installed by following the tutorial. But the vscode command is not working, there is not the text select interpreter. It is installed, but I have nothing.
Of course, I tried to uninstall/install but the same issue. I reset all my settings and nothing change.

Seems like you may have a corrupted install.
Please could you:

uninstall the python extension,
completely exit (quit) VS Code. (please close all instances of vscode)
Open vscode,
Reinstall the python extension

Else:

Select the command Open Extensions Folder from the command palette
Find the folder ms-python.python** directory and just delete it
Reinstall the python extension

Closing as this should solve this issue.
If it doesn't please do let us know and we'll be happy to reopen this issue.


Upgrade to Vite

[x] remove webpacker
[x] install vite-rails
[x] make the editor UI work with Vite and TailwindCSS 3
[x] move the live preview client lib to Vite
[x] migrate the jest tests -> vitest
[x] fix the linter
[x] fix the preview
[x] clean code
[x] test with Maglev production apps
[x] rake tasks to precompile assets in production
[x] test against Node 18

I'm keen to test the install 😄
(guessing it still has a few paces to go though - just tried a fresh install but same issue popping up:
√ maglev % bundle exec rails g maglev:install
        rake  maglev:webpacker:compile
yarn install v1.22.19
[1/4] 🔍  Resolving packages...
success Already up-to-date.
✨  Done in 0.22s.
Compiling...
Compilation failed:
Browserslist: caniuse-lite is outdated. Please run:
  npx browserslist@latest --update-db
  Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
node:internal/crypto/hash:67
  this[kHandle] = new _Hash(algorithm, xofLen);
                  ^

It annoys me, however, as it still claims nodeJS 18.2.0 even though I did asdf local nodejs 16.18.0 and asdf reshim - not sure why it "still" demands v18 - so I might be 'crying wolf' without any reason 😢 (since @drnic reported a succesfull install using Node v16)

I'm keen to test the install 😄
(guessing it still has a few paces to go though - just tried a fresh install but same issue popping up:
√ maglev % bundle exec rails g maglev:install
        rake  maglev:webpacker:compile
yarn install v1.22.19
[1/4] 🔍  Resolving packages...
success Already up-to-date.
✨  Done in 0.22s.
Compiling...
Compilation failed:
Browserslist: caniuse-lite is outdated. Please run:
  npx browserslist@latest --update-db
  Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
node:internal/crypto/hash:67
  this[kHandle] = new _Hash(algorithm, xofLen);
                  ^

It annoys me, however, as it still claims nodeJS 18.2.0 even though I did asdf local nodejs 16.18.0 and asdf reshim - not sure why it "still" demands v18 - so I might be 'crying wolf' without any reason 😢 (since @drnic reported a succesfull install using Node v16)

hey @wdiechmann, new version released! It should be good now 🤞


Nuxt3 nuxt.config.ts

Environment
plugins parameters cannot be assigned to parameters of type "InputConfig<NuxtConfig, ConfigLayerMeta>". Object text can only specify known properties, and "plugins" are not in the type "InputConfiguration<NuxtConfiguration, ConfigLayerMeta>". Ts (2345)
Reproduction
plugins parameters cannot be assigned to parameters of type "InputConfig<NuxtConfig, ConfigLayerMeta>". Object text can only specify known properties, and "plugins" are not in the type "InputConfiguration<NuxtConfiguration, ConfigLayerMeta>". Ts (2345)
Describe the bug
plugins parameters cannot be assigned to parameters of type "InputConfig<NuxtConfig, ConfigLayerMeta>". Object text can only specify known properties, and "plugins" are not in the type "InputConfiguration<NuxtConfiguration, ConfigLayerMeta>". Ts (2345)
Additional context
plugins parameters cannot be assigned to parameters of type "InputConfig<NuxtConfig, ConfigLayerMeta>". Object text can only specify known properties, and "plugins" are not in the type "InputConfiguration<NuxtConfiguration, ConfigLayerMeta>". Ts (2345)
Logs
plugins parameters cannot be assigned to parameters of type "InputConfig<NuxtConfig, ConfigLayerMeta>". Object text can only specify known properties, and "plugins" are not in the type "InputConfiguration<NuxtConfiguration, ConfigLayerMeta>". Ts (2345)

@xunzhaotech Please provide information on how to reproduce that error.

Not exactly same as @xunzhaotech but similar problem exists even on minimal reproduction link

How to deal this bug?

Can be closed. Original poster never provided a reproduction. The reproduction from @doganalper does not have an issue anymore:


Word Count

Hi guys,
I have an issue with exercise word count. It works in ABAP but not on Exercism.
It looks like that the plattform is not able to work with adding 1 to the reference which is marked red.
All tests with a word count greater than 1 fail.
Please have a look on the screenshot.
Thanks in advance.
Michael

@mickrig thanks, can you post the code as text here in the issue? https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks

@larshp Yes, sure, please find the code below
CLASS zcl_word_count DEFINITION
  PUBLIC
  FINAL
  CREATE PUBLIC .

  PUBLIC SECTION.
    TYPES:
      BEGIN OF return_structure,
        word  TYPE string,
        count TYPE i,
      END OF return_structure,
      return_table TYPE STANDARD TABLE OF return_structure WITH KEY word.
    METHODS count_words
      IMPORTING
        !phrase       TYPE string
      RETURNING
        VALUE(result) TYPE return_table .
  PROTECTED SECTION.
  PRIVATE SECTION.
ENDCLASS.

CLASS zcl_word_count IMPLEMENTATION.

  METHOD count_words.
    DATA(string) = replace( val = to_lower( phrase ) sub = `'` with = `` occ = 0 ).
    string = replace( val = string sub = `\t` with = ` ` occ = 0 ).
    string = replace( val = string sub = `\n` with = ` ` occ = 0 ).
    string = condense( replace( val = string regex = `[^a-z0-9]` with = ` ` occ = 0 ) ).

    DO.
      TRY.
          DATA(substring) = segment( val = string
                            index = sy-index
                            sep = ` ` ).
          TRY.
              DATA(single_count) = REF #( result[ word = substring ]-count ).
              single_count->* += 1.
            CATCH cx_sy_itab_line_not_found.
              APPEND VALUE #( word = substring  count = 1 ) TO result.
          ENDTRY.

        CATCH cx_sy_strg_par_val.
          EXIT.
      ENDTRY.
    ENDDO.

  ENDMETHOD.
ENDCLASS.

downport problem, the reference is lost,


Remove old rnpm for react-native 0.60

I have folow this migration guide for fix the rn60 warning
I don't have time to test this change yet, but I accept any feedbacks
#359

Looks nice, I will try to test it later today.
I would favor that we keep the existing rnpm entry for now, so that people can continue using React Native pre-0.60 for a while.

I find this part of migration guide and fixed the react-native.config.js

How we can do android link with react-native link?
Anybody has the answer?

Looks nice, I will try to test it later today.
I would favor that we keep the existing rnpm entry for now, so that people can continue using React Native pre-0.60 for a while.

@brodybits I had read on migration guide, and see this info:

"rnpm" is deprecated and support for it will be removed in next major version of the CLI.

It's not because react-native version, but the cli version, they are independent.
New versions of react-native-cli show this warning and version 2.0.0 is not compatible.
You can see more info here.

@andpor any more changes request?

+1 can we help move this along in any way?

I'll create a another npm package for solve this problem.
This PR has more a month, and not had activity.

I don’t think creating another npm package solves any problems. That just spreads the community out more. This package has weekly downloads and many contributors in just think it would be helpful if the owner or maintainer was a little more active or delegated permissions for keeping PRs like this moving along for the library.
Sent from my iPhone

On Aug 21, 2019, at 9:40 AM, Carlos Roberto<EMAIL_ADDRESS>wrote:
I'll create a another npm package for solve this problem.
This PR has more a month, and not had activity.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Yes not solve, it's only a idea
This workaround install from my fork directly.
yarn add carlosroberto555/react-native-sqlite-storage
I used on my personal project, and autolink works like a charm.

The PR is merged and released under 4.0.0 - sorry for delay, quite busy lately.

The burden on library maintainers for react-native 0.60 (both in their paying project work, and whatever libraries they maintain) is pretty serious, and it's vacation season - glad to see this merged but everyone be as helpful as you can in the libraries you use, pretty much like submitting the PR here (❤) and being patient. Cheers


Code generator generates incorrect package names

Code generator generates package names with dots which fails to compile.
The behavior has been changed by this commit:
https://github.com/kubernetes/code-generator/commit/5ac21ed6de7ac91d03e7917872c463de906d46a6#diff-9b57faef7d093e48f0c343f34da19a15
Before package names were first part of  group name and after change package names are equal to group names. This causes compilation errors as package names contain dots.

Closing since this is a duplicate issue: https://github.com/kubernetes/kubernetes/issues/82860
Fix is in progress here: https://github.com/kubernetes/kubernetes/pull/82410
/close


Environment variable names are converted to uppercase in the container

ServiceMonitor converts the environment variable names to upper case when adding to the app pool process.
Below line in IISConfigUtil.cpp seems to do a in place conversion of the environment name to upper case. FilterEnv(filter, CharUpper(pstrNameCheck), pstrValue)
This is causing environment variable replacement using ConfigBuilders to fail unless we change all AppSetting keys to be upper case which is not ideal.

Any ETA on the fix. Thank you.

Fixed in #33

Any news on a release, or do I need to compile this myself?

@bariscaglar looks like this slipped through the cracks. Do you have someone who can take a look at releasing this?

Actually looks like I misspoke. <IP_ADDRESS> has this change in it already

Jumped the gun on that. Looked back on the build history. <IP_ADDRESS> was built from 5f6d9673131817e52b481f8005cc782c90290860


Allow you to set pod labels

The current deployment lacks the ability to set pod labels. While this may not directly affect the usage of Mattermost, it is a common feature needed in bigger environments. This adds the ability to set them

/check-cla


Remove unnecessary cast in cabi_dealloc

I don't understand why that one C# test failed ..

Looks strange, try rerunning?

Seems to be working fine now


Update to homepage to include template elements

Hi @DuncanmaMSFT, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

I think that this is stale now.


Update Play Core Library for Android 14 Compatibility

Firstly, thank you for this package @MinaSamir11  and the maintainers!
Issue Description:
There is an important compatibility issue with the current version of the Play Core library (com.google.android.play:core) and the upcoming Android 14 (targetSdkVersion 34).
Problem:
Google has introduced a backwards-incompatible change to broadcast receivers in Android 14 to improve user security. As a result, the current version of the Play Core library (core:1.9.0) is incompatible with targetSdkVersion 34. This incompatibility will cause crashes and other issues in apps targeting Android 14.
Impact:
Target SDK Requirement: From August 31, Google Play requires all new app releases to target Android 14.
Release Block: Apps using the current version of the Play Core library will not be able to release future versions to production or open testing.
User Security: The security improvements in Android 14 are crucial for user protection, and maintaining compatibility is essential.
Required Action:
Please update the Play Core Maven dependency to an Android 14 compatible version. This will ensure that applications using this library can continue to be released on the Google Play Store without any issues.
Reference:
Play Core Migration Guide

Pull Request raised for this fix here
https://github.com/MinaSamir11/react-native-in-app-review/pull/176

same here

@Durkaen you can use the fix as I have added in the PR

I will check out ur pull request.

@Durkaen It seems that you are using the previous version, please checkout and mention your installed in-app-review version & update it to the latest version.
Thanks

@MinaSamir11 I am running on 4.3.3v

What is the current status of this? Will it get merged and released?

Hey guys, I'm having the same issues as well, any news? I noticed that the PR created for this issue was closed.

Hey guys, I'm having the same issues as well, any news? I noticed that the PR created for this issue was closed.

Already fixed in the latest version 4.3.3 &
please checkout if you're using another lib already using play core.

Yeah, it's all good :D Google mentioned a list of versions and I didn't notice that the current version is not on that list  😭

@HarshitMadhav Hey guys I am on the latest version but still facing issue in android. In the console it shows that it's working but the popup didn’t appear in debug mode and internal testing any solution for it?

@HarshitMadhav @MinaSamir11  Hey guys I am on the latest version but still facing issue in android. In the console it shows that it's working but the popup didn’t appear in debug mode and internal testing any solution for it?

Please read well the readme file, to solve your issue.

@Durkaen It seems that you are using the previous version, please checkout and mention your installed in-app-review version & update it to the latest version.
Thanks

Oh my bad, sorry. I've upgraded to the latest version now, everything's fine. :)

I'm a little confused,
Are we supposed to upgrade this packaged to the latest 4.3.3? Or, are we supposed to use this fix
Can anybody please guide? Thank you so much.

I'm a little confused,
Are we supposed to upgrade this packaged to the latest 4.3.3? Or, are we supposed to use this fix
Because in the latest commit, it seems that the package have removed the play core dependency and are not moving forward with it (reference)
Can anybody please guide? Thank you so much.

Did you follow the captain instructions or the passenger in the plane 😄
do not be confused this commit means nothing, it isn't affect on any thing in the package.
use the latest version.
Have a nice day.

@MinaSamir11
haha, good example.
thank you, have a nice day to you too.


Don't emphasize the zeros by default in 2D plots

In all the line plots of makie's documentation the lines that cross 0 are emphasized by default.
This is problematic, as it conveys information the user did not choose to convey. Sometimes it is useful to emphasize a zero line, sometimes not. Definitely it is not useful in every single possible case.
The important part is that for a user it is trivial to do that if they wish so, by adding two lines! calls.
It is much more difficult, obscure, and unreasonable, to change the defaults of a plotting package, per plotting script!
Please give power to the users, and be much more restrained with the "installation defaults". There is a reason none of the great plotting packages that are used routinely in scientific publications don't emphasize things by default. The ones I know from the top of my head, GR, PyPlot and VegaPlot, do not do such an invasive thing by default.

In principle I'm fine with emphasising the coordinate axes, and I notice that Mathematica does this by default. But right now I'm staring at a beautiful mesh plot with a black line over the top 😰

this got fixed


Verifier module to implement for resolution up to root

Implement the central verification algorithm that recurses up the tree from a DID until reaching a root, verifying the document metadata proofs at each step.

Initial refactor bbe4ec4 of Chain and DIDChain to allow assignment and getting of a root timestamp.

Closed after #52


Allow cimport of cpython in the limited API

Fixes #5634.
Fixes #5697 (from a Cython point of view; Numpy still includes stuff that isn't limited API compatible).
I've done two things:

Added two values of check_size to "opaque" and "opaque_in_limited_api". These don't check the object size at import (which avoids need to do sizeof on opaque types). However they're restricted so they can't be used as a way of disabling the size check.
Added a compiler directive for cdef functions that wraps them in an #if guard. It's mainly for our internal use so undocumented but I'm fairly relaxed if people find and use it.

With these I can get all of the pxd files (except cpython.array.pxd) so that they can be be cimported in limited API mode. Of course, much of them won't work, but it won't present a compile error unless used. Which at least means that people can use the bits that do work.

NumPy hid the things that broke this in https://github.com/numpy/numpy/pull/25531 which was recently merged.

https://github.com/cython/cython/pull/3694 looks to be an alternative approach for this problem. It's definitely simpler, but I suspect a bit less helpful. But maybe should be evaluated as another option.

I think your view is that these inline functions/properties should compile into something valid in the limited API, but something that emits a runtime exception/warning (and maybe a C compile warning). The advantage of that approach is that users could write code that compiles under all modes, but selects a Python fallback at runtime.
To me that seems like something that'd be best done by something like c_compile_guard? In that it could automatically generate the exception-raising code and we wouldn't have to come up with ad-hoc solutions each time.

With that said, I'm not quite convinced by this. Mainly because many of the other declarations in the pxd files just won't exist in Limited API mode, and thus won't compile. I'm not sure it makes sense for us to hold our cdef inline helper functions to a higher standard than the rest of the Python C API.


add nuclear energy classes #522 #692

closes #522
closes #692

I don't know why the catalog file has changed, at least I didn't do it on purpose. Can you take a look @sfluegel05 ?


How can I change default animation speed

Hello.
I have trouble with changing animation speed.
There is no options for changing animation velocity and other animation options.
not snapTo Velocity options. I want to know default animation options.
Please let me know.  Thanks!

+1

any update?

anyupdate?

+1, Love the lib btw ❤

anyupdate?

me need this too +1

Spring 9 has been released, it would be very cool to have it since having a spring based component without being able to controll is is so frustrating :-)

To anyone looking for changes in speed/velocity.  You can fork the repo and change the mass, tension, and friction to increase the speed.  Mass is related to the bounce effect on open or close.  Friction & tension are related to speed.  I am using this:
mass: .01
tension: 700
friction: 15
Change need to be made in the BottomSheet.tsx file


Unknown error in server 1.3.8

I had to update the Fractal server at UZH today (unrelated, was a Python 3.9.0 issue, see https://github.com/fractal-analytics-platform/fractal-demos/issues/65). I thought I'd also update to fractal-server-1.3.8, as that looked to perform well in all the testing and wasn't a major change.
Unfortunately, it brok on production when trying to run a workflow with the following error.
I now went back to running a 1.3.6 server (with Python 3.10), so production is running again. But we should figure out what caused this issue.
UNKNOWN ERROR
Original error: Traceback (most recent call last):
  File "/data/homes/fractal/anaconda3/envs/fractal-server-1.3.8/lib/python3.10/site-packages/fractal_server/app/runner/__init__.py", line 228, in submit_workflow
    output_dataset_meta = await process_workflow(
  File "/data/homes/fractal/anaconda3/envs/fractal-server-1.3.8/lib/python3.10/site-packages/fractal_server/app/runner/_slurm/__init__.py", line 125, in process_workflow
    output_dataset_metadata = await async_wrap(_process_workflow)(
  File "/data/homes/fractal/anaconda3/envs/fractal-server-1.3.8/lib/python3.10/site-packages/fractal_server/app/runner/common.py", line 244, in async_wrapper
    return await loop.run_in_executor(executor, pfunc)
  File "/data/homes/fractal/anaconda3/envs/fractal-server-1.3.8/lib/python3.10/concurrent/futures/thread.py", line 52, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/data/homes/fractal/anaconda3/envs/fractal-server-1.3.8/lib/python3.10/site-packages/fractal_server/app/runner/_slurm/__init__.py", line 77, in _process_workflow
    output_task_pars = execute_tasks(
  File "/data/homes/fractal/anaconda3/envs/fractal-server-1.3.8/lib/python3.10/site-packages/fractal_server/app/runner/_common.py", line 617, in execute_tasks
    current_task_pars = call_parallel_task(
  File "/data/homes/fractal/anaconda3/envs/fractal-server-1.3.8/lib/python3.10/site-packages/fractal_server/app/runner/_common.py", line 510, in call_parallel_task
    for key, val in this_meta_update.items():
AttributeError: 'NoneType' object has no attribute 'items'

Most likely cause is that this was a scmultiplex task, which does not write a valid dictionary to the output JSON file, but just a null value (since there is no return {} here).
Our tests always return a dictionary, and that's why this was not caught.
I'll release 1.3.9 shortly, also covering the null case.

Ah that would make sense :)

I'll release 1.3.9 shortly, also covering the null case.

The new use case should be now covered in 1.3.9.


[reactive-element] Rename Warnings type to WarningKind. Add docs.

Warnings should have been named as a singular noun phrase.
I kept the old name too, though we might want to get rid of it as the number of people relying on it is probably close to 0.
Also added some docs.

@sorvell wdyt about removing the old Warnings name?

Oh, we should add this to the changelog.


Clean up configuration files

Proposed change

Clean up configuration files
Type of change

[ ] New country/market holidays support (thank you!)
[ ] Supported country/market holidays update (calendar discrepancy fix, localization)
[x] Existing code/documentation/test/process quality improvement (best practice, cleanup, refactoring, optimization)
[ ] Dependency upgrade (version update)
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] Breaking change (a code change causing existing functionality to break)
[ ] New feature (new python-holidays functionality in general)

Checklist

[x] I've followed the contributing guidelines
[x] This PR is filed against beta branch of the repository
[x] This PR doesn't contain any merge conflicts and has clean commit history
[x] The code style looks good: make pre-commit
[x] All tests pass locally: make test, make tox (we strongly encourage adding tests to your code)
[x] The related documentation has been added/updated (check off the box for free if no updates is required)

coverage: 100.0%. remained the same when pulling d3f08d57406b04c5b8eb265e1101cbefc3b6f618 on arkid15r:clean-up-configs into bf54ecdeb526e082d90e076a204c162f4e4f1e61 on dr-prodigy:beta.


Various Fixes

Here are a bunch of fixes for various issues and some general cleanup. I can split it up into separate PRs of your choosing if it helps.
At least locally, the first fastbin activator fix significantly reduced the number of TestFastbinRoundTrip failures - I thought it solved it, but then saw the failure one more time out of tens of test runs, whereas before the fix it failed nearly always. The second fastbin activator fix might be related and help cover the remaining race condition, but can't tell for sure until we see the failure again or don't. In any case I think it's correct, whereas the previous atomic boolean use, at least to me, didn't seem to do what someone thought it's supposed to do :-)
If I misunderstood anything or anything requires revision, let me know.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Aries-rsa-pr/7/

Yay, Jenkins like it!
Maybe have it run a few more times to see if we get the fastbin failure again?

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Aries-rsa-pr/8/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Aries-rsa-pr/9/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Aries-rsa-pr/10/

Added a couple dependency updates.
Now 4/4 Jenkins runs are successful, so looking good. btw what I've seen matches ARIES-1835 more than it does ARIES-1836.

Yes. Would be great if you could split it up. All together it is a bit much to validate... and more PR look good in the stats :-)


Support function array/broadcast_to

Support function array/broadcast_to
example
> require 'chainer'
> x = Numo::SFloat.new(3).seq
> h = Chainer::Functions::Array::BroadcastTo.broadcast_to(x, [3,2,3])
> h.data
=> Numo::SFloat#shape=[3,2,3]
[[[0, 1, 2],
  [0, 1, 2]],
 [[0, 1, 2],
  [0, 1, 2]],
 [[0, 1, 2],
  [0, 1, 2]]]

@hatappi I fixed https://github.com/red-data-tools/red-chainer/pull/60#discussion_r206909139 https://github.com/red-data-tools/red-chainer/pull/60#discussion_r206911797

Please resolve conflicts 🙏

I have rebased. @hatappi

@youchan
Sorry for the late review.
Thank you for contributing 🎉


⚠ Bofrost.be has degraded performance

In 75fe2d7, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1437 ms

Resolved: Bofrost.be performance has improved in b6e8339 after 25 minutes.


docs(IconSearch): fix copy to clipboard

Fixes #1314
This PR:

fixes copy to clipboard for the Icon search
fixes the prop table's display of default and required props for all components

Codecov Report

Merging #1317 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1317   +/-   ##
=======================================
  Coverage   99.75%   99.75%
=======================================
  Files         140      140
  Lines        2402     2402
=======================================
  Hits         2396     2396
  Misses          6        6

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 4a321ec...85be224. Read the comment docs.


Idea: Development scaffolding similar to front-end

Recently when I was trying to develop the front end, I found that the overall development experience was not very good. Maybe we can try to refer to elecron-vite
Make similar scaffolding to help development

But I think this is not the main demand at the moment.

for other wrappers, the role of webUI is better the smaller it is, it’s just a binary protocol between the backend and frontend.
The webUI itself does not serve as a backend, for example, in the case of deno.js and this, in my opinion, is more good than bad.
For the C++ version, etc. maybe everything is different

In fact, the current difficulty is that if we combine webui with front-end vue react, then we have to introduce a different port js webui.js into index.html during development. When using packaged files, we need to directly introduce webui.js
And the code of backend is also different between develop and release
It would be nice if these differences could be smoothed out.But I haven’t thought of a solution for price comparison at the moment.

Just adding my .02$
I quite prefer that I have the freedom to implement whatever development tools I like into the development workflow in WebUI.
I think that one option would be to provide examples as part of the WebUI documentation of how existing frontend tooling like tsc, rollup/webpack can be easily integrated into a WebUI based development set up.
Modern dev tools like mise could come in quite handy in devising such examples.
(I am currently in the process of integrating mise watch, tsc + rollup for a webui-go project. The tooling is not quite ready to share yet though)


Fix/iterator is not a function

@mirceanis not going to solve any problem, but it will help us digging the real cause of errors.


Grid size optimize T3

Following Gavin's PR#295, this test on T3 kernel grid size is done on master. From the result, the block size is chosen to be 2048. Increases the block size always benefits the kernel currently. The timing result is below.
This PR timing:

master timing:

compute throughput is increased. (Green is master)

active warps increased. Although it still didn't catch the theoretical warps

waves per SM is close to 1

profiling results: http://uaf-10.t2.ucsd.edu/~yagu/SDL_GPU_plots/grid_size/profiling_T3_block.ncu-rep

Wrong code, sorry


TouchScreenButton not triggering action assigned in the inspector on Android devices

Godot version
v4.1.2.stable.official [399c9dc39]
System information
Windows 11, Compatibility renderer
Issue description
Action not triggering on TouchScreenButton when assigned the action in the Inspector's Action property and specifically the is_action_just_pressed() method. The is_action_pressed() is working normally but the former doesn't trigger when tested via remote debug and on apk export. only on the Android device. on the Run project on pc the button triggers normally.
Steps to reproduce
add a TouchScreenButton node assign an action on it's action property in the Inspector, call the action in a script using Input.is_action_just_pressed() note it's not Input.is_action_pressed() that one is working ok, test it on an Android device not in the pc
Minimal reproduction project
android_input assign_bug.zip

Thanks for the report! Consolidating in https://github.com/godotengine/godot/issues/70951.

فعل كل التطبيقات في الاندرويد هذا الجهاز

فعل

****

فعل كل التطبيقات في الاندرويد هذا الجهاز

I used translate, but what do you mean with "Activate all applications on this Android device" I don't understand can you elaborate


Don't use Preprocessor or use a separate intent tree for target

Here is an example of the y_processor after serialization:
{
    "columns": {
        "target": [
            "NumericIntent",
            [
                [
                    "DropFeature",
                    "dropper",
                    {
                        "keep_columns": false,
                        "name": null,
                        "threshold": 0.3
                    }
                ],
                [
                    "SimpleImputer",
                    "simple_imputer",
                    {
                        "override": null,
                        "name": null,
                        "keep_columns": false
                    }
                ],
                [
                    "Scaler",
                    "scaler",
                    {
                        "override": null,
                        "name": null,
                        "keep_columns": false
                    }
                ]
            ],
            [
                "GenericIntent",
                "NumericIntent"
            ]
        ]
    },
    "postprocess": [],
    "intents": {
        "GenericIntent": {
            "multi": [
                [
                    "MultiImputer",
                    "multi_impute",
                    {
                        "override": null,
                        "name": null,
                        "keep_columns": false
                    }
                ]
            ]
        },
        "NumericIntent": {}
    }
}

Since we are using the same Intent tree for target (y) as for features (x), any transformers used in the Intent tree can be selected for target. This first require all transformers to implement a reverse_transform function. Secondly, Using DropFeatures does not make sense for target. If there is any null value for target, the framework should simply fail the training. Lastly, it does not make sense to do one-hot-encoding or scaling or imputing for target.
I think the best approach is to have a separate intent tree and design transformation properly for target specifically.

Closing in favor of issue #1. A solution that works with the intent based system seems to be the way to go forward as discussed.


draging audio progress bar back breaks the audio timming

when playing an audio and you drag the progress bar back most times it breaks and the audio still continues from the time you were before going back. Please this needs a fix  thanks. the only way to work around is to stop and play audio again

You need to make sure that unbind() is not being called, automatic rebinding of audio time is dependent on that


chore: release v0.1.23

🤖 New release

stn: 0.1.22 -> 0.1.23

Changelog

[0.1.23] - 2024-01-24
Bug Fixes

Add check for installation before status, fix some logging (#46)

This PR was generated with release-plz.

still doesn't fix changelog, but fixes bugs, so will release it.


Move emails to event driven actions

Using https://docs.nestjs.com/techniques/events , it would be nice to send an event that the user was created / deleted to then send an email in another service, which would create a better separation of concerns.

closed by cc1c10b00af26b1acf8de8115e8109a4cc4cfdfc


(litmus-portal) feat.- Analytics frontend updates and monitoring for v2

Proposed changes

Updating existing analytics code on frontend.
Adding data source, dashboards and monitoring pages for analytics v2

Types of changes
What types of changes does your code introduce to Litmus? Put an x in the boxes that apply

[x] New feature (non-breaking change which adds functionality)
[x] Bugfix (non-breaking change which fixes an issue)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices applies)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[x] I have signed the commit for DCO to be passed.
[x] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[ ] I have added necessary documentation (if appropriate)

Dependency

None.

Special notes for your reviewer:
PR for 2.0 beta 0

/run-e2e


[BACKPORT][SPARK-23040][CORE] Returns interruptible iterator for shuffle reader

Backport https://github.com/apache/spark/pull/20449 and https://github.com/apache/spark/pull/20920 to branch-2.3

What changes were proposed in this pull request?
Before this commit, a non-interruptible iterator is returned if aggregator or ordering is specified.
This commit also ensures that sorter is closed even when task is cancelled(killed) in the middle of sorting.
How was this patch tested?
Add a unit test in JobCancellationSuite

Test build #88777 has started for PR 20954 at commit e9a661f.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/1880/
Test PASSed.

Test build #88777 has finished for PR 20954 at commit e9a661f.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/88777/
Test FAILed.

retest this please

Test build #88781 has started for PR 20954 at commit e9a661f.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/1883/
Test PASSed.

Test build #88781 has finished for PR 20954 at commit e9a661f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/88781/
Test PASSed.

thanks, merging to 2.3!

Hi, @cloud-fan and @jiangxb1987 .
It seems that the newly added test case starts to fail at sbt-hadoop2.7. Could you take a look at the failure?

https://amplab.cs.berkeley.edu/jenkins/view/Spark QA Test (Dashboard)/job/spark-branch-2.3-test-sbt-hadoop-2.7/lastCompletedBuild/testReport/org.apache.spark/JobCancellationSuite/interruptible_iterator_of_shuffle_reader/

Thanks for reporting, I'll be looking into the flaky test.


Feature suggestion

Is your feature suggestion related to a current problem or issue? Please describe.
A clear and concise description of what the problem is. Ex. I''ve found it difficult when [...]

Sometimes, reviewers are taking weeks to review an assigned article.
Writers are taking too long to make changes to their articles (as suggested by reviewers).

Describe the solution you'd like to implement to the program
A clear and concise description of what you want to happen.

Reviewers to be allowed a maximum of one week to provide feedback after assigning an article. This will ensure that reviewers only assign themselves the workload they're able to handle comfortably within a short time.
Writers to be allowed a maximum of three days to complete revisions.

Describe alternatives you've considered or seen
A clear and concise description of any alternative solutions or features you've considered.
Additional context on how you could go about building this
Add any other context or screenshots about the feature request here.

Thank you for sharing @EKahuha
Great insight!!


[BUG] Failed to connect to vector store

I'm not quite sure how this happened but perhaps a day after I added a bit more than 2k docs to the database I noticed that the docker was not in docker ps, so I booted it back up with the command and now it seems to be stuck on failing to startup the vector store db.
 Using local vector store
Waiting for vector store to start
Marqo found an existing vector store. Waiting for vector store to be available...
  Waiting for vector store to be available...
  Waiting for vector store to be available...
  Waiting for vector store to be available...
  Vector store is available. Vector store setup complete
Starting Marqo throttling
Called Marqo throttling start command
Marqo throttling is now running
/usr/local/lib/python3.8/site-packages/transformers/generation_utils.py:24: FutureWarning: Importing `GenerationMixin` from `src/transformers/generation_utils.py` is deprecated and will be removed in Transformers v5. Import as `from transformers import GenerationMixin` instead.
  warnings.warn(
INFO:ModelsForStartup:pre-loading ['hf/e5-base-v2', 'open_clip/ViT-B-32/laion2b_s34b_b79k'] onto devices=['cpu']
ERROR:marqo.tensor_search.on_start_script:Failed to bootstrap vector store. If you are using an external vector store, ensure that Marqo is configured properly for this. See https://docs.marqo.ai/2.8/Guides/Advanced-Usage/configuration/ for more details. Error: timed out
INFO:marqo.tensor_search.index_meta_cache:Starting index cache refresh thread

###########################################################
###########################################################
###### STARTING DOWNLOAD OF MARQO ARTEFACTS################
###########################################################
###########################################################

INFO:CUDA device summary:Found devices [{'id': -1, 'name': ['cpu']}]
INFO:SetBestAvailableDevice:Best available device set to: cpu
loading for: model_name=hf/e5-base-v2 and properties={'name': 'intfloat/e5-base-v2', 'dimensions': 768, 'tokens': 512, 'type': 'hf', 'model_size': 0.438, 'text_query_prefix': 'query: ', 'text_chunk_prefix': 'passage: ', 'notes': ''}
config.json: 100%|█████████████████████████████████████████████████████████████████████| 650/650 [00:00<00:00, 51.1kB/s]
model.safetensors:  17%|██████████                                                  | 73.4M/438M [00:03<00:17, 21.0MB/s]ERROR:marqo.tensor_search.index_meta_cache:Failed to connect to vector store. If you are using an external vector store, ensure that Marqo is configured properly for this. See https://docs.marqo.ai/2.8/Guides/Advanced-Usage/configuration/ for more details. Error: timed out
model.safetensors:  89%|██████████████████████████████████████████████████████       | 388M/438M [00:18<00:05, 8.52MB/s]ERROR:marqo.tensor_search.index_meta_cache:Failed to connect to vector store. If you are using an external vector store, ensure that Marqo is configured properly for this. See https://docs.marqo.ai/2.8/Guides/Advanced-Usage/configuration/ for more details. Error: timed out
model.safetensors: 100%|█████████████████████████████████████████████████████████████| 438M/438M [00:23<00:00, 18.5MB/s]
tokenizer_config.json: 100%|███████████████████████████████████████████████████████████| 314/314 [00:00<00:00, 24.7kB/s]
vocab.txt: 100%|█████████████████████████████████████████████████████████████████████| 232k/232k [00:00<00:00, 2.92MB/s]
tokenizer.json: 100%|████████████████████████████████████████████████████████████████| 711k/711k [00:00<00:00, 1.93MB/s]
special_tokens_map.json: 100%|█████████████████████████████████████████████████████████| 125/125 [00:00<00:00, 58.7kB/s]
INFO:marqo.s2_inference.s2_inference:loaded hf/e5-base-v2 on device cpu with normalization=True at time=2024-06-17 08:03:33.051778.
INFO:ModelsForStartup:hf/e5-base-v2 cpu run succesfully!
loading for: model_name=open_clip/ViT-B-32/laion2b_s34b_b79k and properties={'name': 'open_clip/ViT-B-32/laion2b_s34b_b79k', 'dimensions': 512, 'note': 'open_clip models', 'type': 'open_clip', 'pretrained': 'laion2b_s34b_b79k'}
open_clip_pytorch_model.bin:  23%|███████████▍                                       | 136M/605M [00:04<00:13, 35.3MB/s]ERROR:marqo.tensor_search.index_meta_cache:Failed to connect to vector store. If you are using an external vector store, ensure that Marqo is configured properly for this. See https://docs.marqo.ai/2.8/Guides/Advanced-Usage/configuration/ for more details. Error: timed out
open_clip_pytorch_model.bin:  95%|████████████████████████████████████████████████▌  | 577M/605M [00:19<00:00, 29.3MB/s]ERROR:marqo.tensor_search.index_meta_cache:Failed to connect to vector store. If you are using an external vector store, ensure that Marqo is configured properly for this. See https://docs.marqo.ai/2.8/Guides/Advanced-Usage/configuration/ for more details. Error: timed out
open_clip_pytorch_model.bin: 100%|███████████████████████████████████████████████████| 605M/605M [00:19<00:00, 30.3MB/s]
INFO:marqo.s2_inference.s2_inference:loaded open_clip/ViT-B-32/laion2b_s34b_b79k on device cpu with normalization=True at time=2024-06-17 08:04:01.227559.
INFO:ModelsForStartup:open_clip/ViT-B-32/laion2b_s34b_b79k cpu run succesfully!
INFO:ModelsForStartup:0.028252077102661134 for hf/e5-base-v2 and cpu
INFO:ModelsForStartup:0.03686392307281494 for open_clip/ViT-B-32/laion2b_s34b_b79k and cpu
INFO:ModelsForStartup:completed loading models
INFO:marqo.connections:Took 1.652ms to connect to redis and load scripts.
INFO:CachePatchModels:completed prewarming patch models

###########################################################
###########################################################
###### !!COMPLETED SUCCESSFULLY!!!
INFO:     Application startup complete.
INFO:     Uvicorn running on http://<IP_ADDRESS>:8882 (Press CTRL+C to quit)
ERROR:marqo.tensor_search.index_meta_cache:Failed to connect to vector store. If you are using an external vector store, ensure that Marqo is configured properly for this. See https://docs.marqo.ai/2.8/Guides/Advanced-Usage/configuration/ for more details. Error: timed out
ERROR:marqo.tensor_search.index_meta_cache:Failed to connect to vector store. If you are using an external vector store, ensure that Marqo is configured properly for this. See https://docs.marqo.ai/2.8/Guides/Advanced-Usage/configuration/ for more details. Error: timed out
ERROR:marqo.tensor_search.index_meta_cache:Failed to connect to vector store. If you are using an external vector store, ensure that Marqo is configured properly for this. See https://docs.marqo.ai/2.8/Guides/Advanced-Usage/configuration/ for more details. Error: timed out
ERROR:marqo.tensor_search.index_meta_cache:Failed to connect to vector store. If you are using an external vector store, ensure that Marqo is configured properly for this. See https://docs.marqo.ai/2.8/Guides/Advanced-Usage/configuration/ for more details. Error: timed out
ERROR:marqo.tensor_search.index_meta_cache:Failed to connect to vector store. If you are using an external vector store, ensure that Marqo is configured properly for this. See https://docs.marqo.ai/2.8/Guides/Advanced-Usage/configuration/ for more details. Error: timed out
ERROR:marqo.tensor_search.index_meta_cache:Failed to connect to vector store. If you are using an external vector store, ensure that Marqo is configured properly for this. See https://docs.marqo.ai/2.8/Guides/Advanced-Usage/configuration/ for more details. Error: timed out
ERROR:marqo.tensor_search.index_meta_cache:Failed to connect to vector store. If you are using an external vector store, ensure that Marqo is configured properly for this. See https://docs.marqo.ai/2.8/Guides/Advanced-Usage/configuration/ for more details. Error: timed out

Hello @DuckY-Y, thanks for reporting this issue. I'll have a look and keep you updated about the progress.

@DuckY-Y Thanks for reporting this issue. We've established the root cause and are working to include a fix for this in a release this week. Please also note that this issue is limited to the built-in Vespa and does not affect Marqo upgrades when an external Vespa is used.

@DuckY-Y we've addressed this issue in Marqo 2.9 which was released this week. Please see the documentation for how to transfer your container state from any version (2.x) to Marqo 2.9: https://docs.marqo.ai/2.9/Guides/Advanced-Usage/transferring_state/?h=state


[TEVA-2531] Improve job application timeline

Jira ticket URL
https://dfedigital.atlassian.net/browse/TEVA-2531
Screenshots of UI changes:

Review app deployed to https://teaching-vacancies-review-pr-3454.london.cloudapps.digital

View application correctly shows me both the shortlisted and rejected timestamps as a jobseeker.

However as a Hiring Staff user I cannot see the timestamps of when I completed each action. Hiring staff should be able to see time as well as date for review, shortlist, and reject events.

@cesidio looks good, dates and times as expected, including withdrawn time.


feat: Update Operator SDK version strategy

The goal of this PR is to create a strategy (document or script) for updating Operator SDK version in the project.
My goal was to have all operator generated files in a separate folder (inspired by https://github.com/dora-metrics/pelorus/pull/1045), but helm and Go Operator SDK structures are different, its not the best idea to try to put Go generated files in a separate folder.
The idea is: in temporaries folders, create Operator SDK structure using the current Operator SDK version and the version which we want to upgrade it to, following these steps:
operator-sdk init --project-name=oadp-operator --repo=github.com/openshift/oadp-operator --domain=openshift.io
operator-sdk create api --group oadp --version v1alpha1 --kind DataProtectionApplication --resource --controller
operator-sdk create api --group oadp --version v1alpha1 --kind CloudStorage --resource --controller
Then generate a diff file and apply changes to repo code.
It seems to work https://github.com/operator-framework/operator-sdk/issues/6628
There are still a few points to adjust, like: when do we update boilerplate year? What to update in go.mod? Create another Makefile? ( the example added can be run with make -f oadp.mk help)

Should we update hack/boilerplate.go.txt to match this?
https://github.com/openshift/oadp-operator/blob/0347669ab8b5f051d815a59d6f45183742380720/LICENSE#L179-L191

also run operator-sdk create webhook command after operator-sdk create api?

The idea is really nice, may be tricky to maintain with more diffs.
We have something like that in other project, right?
https://github.com/dora-metrics/pelorus/tree/master/scripts/pelorus-operator-patches
The benefit is that we can always re-generate operator starting from scratch.
This is fine for operator where there is not a huge number of changes to the initial files generated by the operator-sdk however in the case of oadp-operator where majority of the code is implemented within that generated initial files this may be very hard to maintain, especially when we are talking later about backports to older releases.
What about using kustomize files instead of patches whenever applicable ?

@mpryc similar yes, but we will not have patch files here. Its terrible developer experience (editing a diff file instead of a yaml file, for example).
We would re-generate files only when we want to update opeartor-sdk version, then we would create a diff file (not tracked by git), and then apply it and then open a PR for that action.
kustomize files can be an option, but not for all things I think. Makefile may be updated, for example. And that is the thing I think we need to be more careful: editing generated files. So, when we update then, it is a smooth experience. Maybe just adding new things to the end of those files can be enough to avoid patching errors

/remove-lifecycle stale
Still want to work on this

unstale?

@kaovilai going to close this one and create small PRs that together do the same


Reorder libraries for building demos.

List the CommodityTracking library first, then the OpenCV libraries.
On Ubuntu 14.04 with g++ 4.8.4 this is the only way I can get the demos to build
and link without errors.

Thanks!


[popin] Style override missing

https://github.com/KleeGroup/focus-components/blob/master/application/popin/index.js#L10

According to me this is no longer a bug as the Popin was entirely rewritten


v-text evaluates HTML entities hard-coded strings

Version
2.6.11
Reproduction link
https://jsfiddle.net/m297ke3y/9/
Steps to reproduce

Add a v-text directive to any tag
Hardcode a string into it (i.e '
This & That
')

What is expected?
HTML entities should not be evaluated in the hard-coded string, they should be written out as they are.
What is actually happening?
HTML entities in the string are converted to their equivalent symbols.

I'm not sure if this is intended behaviour, but it seems odd that the two behaviours in my jsfiddle should differ.

I'm not sure if this is intended behaviour

it's intended, html entities are replaced by the browser

https://jsfiddle.net/j936ezqh/

I'm not sure if this is intended behaviour

it's intended, html entities are replaced by the browser
[image]
https://jsfiddle.net/j936ezqh/

Hey @jacekkarczmarczyk! Thanks for the reply!
It makes that the browser renders the entities. I'm still a bit unsure as to why the raw string is evaluated differently from the variable in the example. Do you have any insights there?

Closing as this is how the browser works. Characters are escaped differently in JS and in HTML Remember to use the forum or the Discord chat to ask questions!


feat(csi): be able to set io timeout on nvme initiator

User sets the timeout in storage class and from there it is propagated
to CSI agent that sets it on the device.
Resolves: CAS-499

Good catch @hoverbear we probably should try both paths?
On Mon, 29 Mar 2021 at 19:53, Ana Hobden @.***> wrote:

@Hoverbear approved this pull request.
Code seems fine otherwise.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/openebs/Mayastor/pull/815#pullrequestreview-623497223,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADZX7VK57YDYSHN2ETXWR3TTGC5A5ANCNFSM4Z4ZO6JA
.

bors merge


Failed to apply settings: push configuration is invalid.

What App Center service does this affect?
App Center - Push notifications
Describe the bug
Cannot add Package SID and Security Key
To Reproduce
Steps to reproduce the behavior:
Go to Microsoft partner center -> copy application SID and secret key and paste to app center.
See error: "Failed to apply settings: push configuration is invalid"
Found a matching issue from earlier that was apparently fixed, but it seems to be back now.
https://github.com/Microsoft/appcenter/issues/290

@LauriRantasalo thanks, I'll take a look.

@LauriRantasalo I just tested it with an app I created and it works as expected. The field names are wrong, I copied the Application ID and Application Secret and it worked for me. Can you try again?

Yeah I was using the Package SID before. Works now with application ID and secret. Thanks.

@LauriRantasalo trying to understand what we need to do to fix this, isn't Package SSID and Application ID the same thing?

No, for me when configuring the Appcenter push notifications it asked for Package SID and Application secret. When viewing the application details from Mircosoft Partner Center, the package SID can be found under Product Identity, where as the application ID is under WNS/MPNS --> Live Services link. (Above the Application Secret).

@LauriRantasalo We made some additional docs updates last week (multiple places) to address this issue. Can you please take another look and let me know if what's there works for you?


Attaching to LPC55S69 seems to stop code execution

Describe the bug
A clear and concise description of what the bug is.
When executing
probe.attach("LPC55S69JBD100", Permissions::default())
it seems to stop the execution of the code running on the lpc55S69.
Because this is also done as part of the flash command, code execution is stopped during the flash procedure, and a manual reset is required. This breaks the RTT connection, making it hard to use the RTT logging (with cargo-embed).
To Reproduce
Steps to reproduce the behavior:
(Using the LPC55S69-EVK)

Flash a simple led blink program to the lpc55S69, for example:

#![no_main]

use cortex_m::delay::Delay;
use cortex_m_rt::entry;
use hal::drivers::pins::Level;
use hal::prelude::*;
use lpc55_hal as hal;
use panic_rtt_target as _;
use rtt_target;

#[entry]
fn main() -> ! {
    rtt_target::rtt_init_print!();
    rtt_target::rprintln!("Starting I2C Test");

    let hal = hal::new();

    let mut anactrl = hal.anactrl;
    let mut pmc = hal.pmc;
    let mut syscon = hal.syscon;
    let mut iocon = hal.iocon.enabled(&mut syscon);

    let clocks = hal::ClockRequirements::default()
        .system_frequency(96.MHz())
        .configure(&mut anactrl, &mut pmc, &mut syscon)
        .unwrap();

    let systick = hal.SYST;
    let mut delay = Delay::new(systick, 96_000_000);

    let mut gpio = hal.gpio.enabled(&mut syscon);
    let pins = hal::Pins::take().unwrap();

    let mut red = pins
        .pio1_6
        .into_gpio_pin(&mut iocon, &mut gpio)
        // on = low, off = high
        .into_output(Level::High);

    loop {
        red.set_low().unwrap();
        rtt_target::rprintln!("Test");
        delay.delay_ms(1000);
        red.set_high().unwrap();
        delay.delay_ms(1000);
    }
}

Cargo.toml:
[package]
name = "startup_test"
version = "0.1.0"
edition = "2021"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
lpc55-hal = "0.3.0"
rtt-target = { version = "0.3.0", features = ["cortex-m"] }
cortex-m-rt = "0.6"
cortex-m = "0.7.6"
panic-rtt-target = { version = "0.1.1", features = ["cortex-m"] }

You should not see any led blinking now.
3. press the reset button on the board. The led will start blinking now.
4. Run this script on the host PC:
use probe_rs::{CoreStatus, Permissions, Probe};
use std::{thread, time};

fn main() {
    // Get a list of all available debug probes.
    let probes = Probe::list_all();

    // Use the first probe found.
    let probe = probes[0].open().unwrap();

    // Attach to a chip.
    let mut session = probe
        .attach("LPC55S69JBD100", Permissions::default())
        .unwrap();
}

The led will now stop blinking again.
Expected behavior
A clear and concise description of what you expected to happen.
Expected the led to keep blinking. (Thus indicating that the code on the LPC55S69 keeps running).
I ran a similar test on the LPC845. Here, the code execution was not stopped by probe.attach() (as expected).
Stacktrace
If applicable, add a stacktrace to help explain your problem.
not applicable
Desktop (please complete the following information):

Windows 10

Additional context
Add any other context about the problem here.
After connecting using probe.attach(), the status can be read. This status indicates the board is running.
Functions such as core.halt(), core.reset() and core.run() change the status as expected, but do not seem to correspond with the actual status of the board (I never see the led blinking again, until a manual reset using the button on the board).

@MikeJongen Can you please retest against #1276 ?
I don't expect this to fix the problem, but noticed that the target yaml has updated flash values when generated against the latest pack files. Before continuing, I'd like to make sure that this doesn't make things worse :)

with #1276, I get the error:
thread 'main' panicked at 'called Result::unwrap() on an Err value: ArchitectureSpecific(RegisterRead { address: 12, name: "DRW", source: ArchitectureSpecific(NoAcknowledge)
})', src\main.rs:20:10
line 20 is the attach:
let mut session = probe
.attach("LPC55S69JBD100", Permissions::default())
.unwrap();

#1276 Helps bring us closer, but this issue still needs resolution.

Based on https://github.com/probe-rs/probe-rs/pull/1907#issuecomment-1831832480 I believe this issue should be fixed. Please feel free to reopen if it's not the case.


3.0的dev版编译通过但是控制台有错误信息。

微软提示：
app.UseCors()必须在app.UseRouting()和app.UseEndpoints()之间。
fail: Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware[1]
An unhandled exception has occurred while executing the request.
System.InvalidOperationException: Endpoint Host.Controllers.JobController.GetAllJobBriefInfo (Host) contains CORS metadata, but a middleware was not found that supports CORS.
Configure your application startup by adding app.UseCors() inside the call to Configure(..) in the application startup code. The call to app.UseAuthorization() must appear between app.UseRouting() and app.UseEndpoints(...).
at Microsoft.AspNetCore.Routing.EndpointMiddleware.ThrowMissingCorsMiddlewareException(Endpoint endpoint)
at Microsoft.AspNetCore.Routing.EndpointMiddleware.Invoke(HttpContext httpContext)
at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)
at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext, ISwaggerProvider swaggerProvider)
at Host.Startup.<>c.<b__5_0>d.MoveNext() in D:\workspace\quartzui-dev\QuartzNetAPI\Host\Startup.cs:line 84
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)

正在调整


AVT 3 Number Input, Form, Form item Components - VO does not announce value or increment when the up and down arrows used to input the number.

Environment
macOS Mojave version 10.14.2
Chrome version 72.0.3626.96 (Official Build) (64-bit)
Detailed Description
With VoiceOver enabled Tab to number input. (Focus is on the up arrow)
Press the up arrow. Voice over does not announce the value or the increment number.
Tab to the down arrow is the same.
Tab to the Number input and the value is announced.
Enter an odd number directly into the Number field.
Shift-Control-Option to enter the stepper
Control Option Up or Down Arrow keys to change the number.
The number is not announced correctly by VoiceOver.
Expected result:
When on an arrow that increments the number up or down the user should be advised that the number is incrementing by 10 as well as the number that is displayed in the number input field.
If a user inputs a number directly that is in the wrong increments they should get a warning.
If they change the number using the VO Control-Option-Up or Down arrow keys the number should be announced correctly.

This issue should remain open until it is fixed and retested.


Need clearer permissions requirements

In the Prerequisites sections, it says:

Delete work items and Restore work items: Have the Delete and restore work items project-level permission set to Allow. Also, to restore work items, you must have Basic access or higher. Users with Stakeholder access can view the contents of the Recycle Bin, but can't restore or permanently delete items in the bin.

The wording implies that Basic access is needed only to destroy or restore work items. We lost some time to figure out that Basic access is also needed to delete a work item.

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

ID: 0e9f02cb-f094-d6bc-ca7b-973db9de0082
Version Independent ID: 1af6a7f5-9e99-ec99-081d-c0bf9e7ac5f5
Content: Remove, delete, and restore work items in Azure Boards - Azure Boards
Content Source: docs/boards/backlogs/remove-delete-work-items.md
Product: devops
Technology: devops-agile
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

@Bliyaal - Thank you for the feedback. I'll update the article to clarify the required permissions within the next 7 days.


[PROJECT] Join a Host Page

Background
This project started with the redesign of the OC website discovery page https://opencollective.com/discover focusing on the experience to find a host, or "host-shopping."
During the discussion, we realized that most Collectives joining the platform already know what host they are going to join. For this reason, and to simplify the experience of using the platform, we are considering deprecating https://opencollective.com/discover and substitute it with a better search experience.
Adding also a page specifically to join a host, where we can showcase the host organizations that are partnering with us
Project goal

Design a page to join a fiscal host
2. Design a better search experience to find profiles from anywhere on the platform

Team
@Memo-Es (Owner)
Project priorities
- Substitute the discovery page with a better search experience

Design a dedicated page to find a fiscal host, showing our main host partners and a list of hosts with basic filters
Edit the 'Create Collective Flow' according to the new Collective<>Host logic
Include the 'What's new?' design in the new features discovery experience. https://docs.google.com/document/d/1VcO_mQDsbPC0foW_WZ7a-L337I3VJVRHCQIPSLYNqrY/edit?usp=sharing

Related issues: #3892
Milestones

[x] New search experience proposal (Wireframes)
- [ ] Search feedback loop and adjustments Moved to search experience redesign issue
[x] Join a host page proposal (Wireframes)
[x] Join a host page feedback loop
[x] High definition UI development
[x] Mobile versions
[x] Design in production

Added to the roadmap for this sprint, ty @Memo-Es !

Also related: #2970

Review Call Notes:
search improvements is a continuation of this project. New issue to be opened by @Memo-Es
Next steps: close the project.

Design proposal
We designed a page for collectives to choose and apply to a fiscal host; this page is adapted to be a part of the flow to accept financial contributions (Part of the create collective flow) and from the settings page of the collective.

Create collective flow
Settings (New admin dashboard)

First, we have a small information box with the main info to get as much of the host context for OC
We have a section of 'Featured hosts' to display our hosts and partner hosts more prominently
It features a basic set of filters by:

Country
Fee structure
Currency
Services available

We included a secondary CTA to know more about becoming a host and the possibility to join

cc @alanna @kaylarep

Feedback from slack
Looking good! It’s such a big improvement.

I think the key categories for fiscal hosts are location (currency is implied from this), fees, entity type (charity/nonprofit, company, co-op, etc) and services/focus area (likely tags, like open source, mutual aid, etc)
In the screen where someone is selecting self-hosting, I don’t think there’s a big choice between Stripe account or Bank account - (many?) most people will connect both. So visually it doesn’t need to be designed as this big choice moment. The big choice is between self-hosted or fiscal host.
I agree this page can live at opencollective.com/hosts - it can mainly function as a ‘find a host’ tool, but also serve the purpose of people just wanting to see and understand the diversity of hosts (maybe they are thinking of starting one, donating, etc).
The ‘what is fiscal hosting’ page is so great and right now we don’t highlight it or link to it well, so let’s make sure we link from this page to that one, if people want to learn more about what hosting is about.

By @alanna

https://www.loom.com/share/343a86026d1648a6bd264017b5f0e55c

This is great! I think this will help a lot! Thank you so much for this! And looking forward for this interface!

Just to summarise the discussion I've had with @znarf @Memo-Es @Betree et al
We should take another run at the design above, taking a more opinionated view on what 'the happy path' is. i.e. that there are hosts that we are very close to 'incubate' hosts that we know and trust and other host that we know little to nothing about. There is still the option to manage your own money but we need to make it obvious that this is at your own risk.
Some more detailed points:

on the 'join a host' page we could organise the page to make hosted the obvious path.
the 'other host' search could be replaced with the search that we already have (in terms of filters and the card content), but we would need to add a filter for hosts that are accepting applications and an option to remove 'featured' hosts as they'll most likely be hard coded in the top section.

I'm personally not feeling like this is scoped enough... We don't have a great enough understanding of exactly what people search for when they're trying to find a host (and I don't think we're currently gathering that information from hosts in a streamlined way that makes it easy to surface the important details.)
If these are the filters we're using

It features a basic set of filters by:

Search
'Sort By' Options (with option of Ascending or Descending)
Budget
Number of Backers
Year Formed
Alphabetical
Recently Active (as in when someone was last active on their page either by donation, update, expense, etc.)
Location (We can expand this filter later to include region→city, but for now, I think it is enough to display countries only)
Fee structure (No host-fee and Host fee)
Currency
Services available
Accounting
Taxes
Invoicing
Payments
Liability
We included a secondary CTA to know more about becoming a host and the possibility to join

We need a lot more here...

We need to be gathering this specific information from any group who onboards into OC as a 'Fiscal Host'.
These questions are not granular enough to be truly helpful in 'finding a host'

Some context: There's "What country are you located in?"(Which needs to be asked to Collectives and fiscal hosts. But there's also "What countries can you host groups from?" e.g. OCF is located in the USA, but can host international groups as long as they follow our International Activity Policy.  Because of all this nuance, the 'location' filter is not helpful, and could actually filter out some eligible groups.
Also, I'm not certain about the goal of this project, as we don't have a large number of fiscal hosts to select from. Also also, just of the top of my head, I imagine that Collectives may want to know 'Mission' details when selecting a host (e.g. a lightweight fiscal sponsor vs. an 'arts-based' fiscal sponsor. )
Or are we trying to educate/promote to collectives better about the offerings of the select 'verified/1st party' fiscal hosts? I don't think the 'Filter' suggestions are a good enough representation of what hosts offer/collectives look for. (e.g. accepts Government grants, virtual cards, how often are expenses processed - a few more off the top of my head, but I imagine there's even more/better ones)
Since our offerings to fiscal hosts are not currently quite comprehensive, this might not really be a useful tool in its current proposal.
Who is the audience for this project?

Groups who join OC wanting transparent finance, but not sure which host to use?  How many fiscal hosts are currently using OC, that this would truly be a beneficial sampling to a lost collective

(Then, if they aren't eligible for our main hosts, we direct them to IC, which there is not much support for. So we end up with a lot of abandoned collectives, who wasted some of their time setting up a collective/learning the platform when they cant even be hosted by a Host using the platform)

Groups who join OC thru their host (they don't need this feature then)

Is this a duplicate of https://github.com/opencollective/opencollective/issues/5672?


Creating dynamic routes

Hi @typicode , Is there any provision to create a route immediately after updating DB(schema json) i..e I would be adding new data to schema.json and it should be available immediately as new route(API) without any server restart.
Could you please help with your thoughts?

I'm facing the same problem. @typicode
json-server adds routes based on the "root" objects or arrays an object (memory or json).
If I want to add a new "root" array I would like to have the /endpoint automatically added for further usage.
I've tried mocking the idea based on this code
     const plural = require('json-server/lib/server/router/plural'); server.use('/:name',function(req, res, next) {         if(req.method === 'POST') {             if(!router.db.get(req.params.name).value()) {                 const opts = { foreignKeySuffix: 'Id', _isFake: false };                 router.db.defaults({[req.params.name]: []}).write();                 server.use(/${req.params.name}, plural(router.db, req.params.name, opts))             }         }         next(); });
But it doesn't seem to work this way. Do you have an idea how to achieve this without restarting the whole server?

I've found a workaround using express-dynamic-middleware.
Feels abit hacky but is doing what's needed.
const dynamicMiddleware = require('express-dynamic-middleware');
let server;

function startServer(jsonFile) {
    server = jsonServer.create();
    let router = jsonServer.router(jsonFile);
    let dynamicRouter = dynamicMiddleware.create(router);
    const defaults = jsonServer.defaults();

    server.use('/:name',function(req, res, next) {
        if(req.method === 'POST') {
            if(!router.db.get(req.params.name).value()) {
                router.db.defaults({[req.params.name]: []}).write();
                dynamicRouter.unuse(router);
                router = jsonServer.router(jsonFile);
                dynamicRouter = dynamicMiddleware.create(router);
                server.use(dynamicRouter.handle());
            }
        }
        next();
    });
    server.use(defaults);
    server.use(dynamicRouter.handle());
    server.listen(8080, () => {
        console.log('API listening on port 8080.');
    });
}


update TileDB-VCF to 0.24.0

Do we want to start building tiledbvcf-py for Windows in this PR or a subsequent one?

Do we want to start building tiledbvcf-py for Windows in this PR or a subsequent one?

We can do a follow-up and I'll try to fix arm in a follow-up. We need to get at least the Linux build out today.


Add BufWriter

There is already a BufReader, so people would expect to have a BufWriter too. A lazy implementation is to simply wrap BufWriter from futures-0.3.

I am currently trying to implement this and encountered some issues, if I make a pull request will someone be able to guide me through?

Hi @Drevoed, yes, we're happy to mentor there. Please be aware that we're currently en route to RustConf, so we might take some time.
Also feel free to jump on the Discord.

Ref #131 also (tracking issue for async_std::io)