[TRIVIAL] Add unit test for redundant payment

High Level Overview of Change
The preflight check to enforce that payee and payer must not be the same account have been in rippled at least 9 years, however we do not have unit test for this case. Add it.
Context of Change
Apparently other crypto ledgers are attacked by creating large number of transactions with the same payee and payer. We are immune to this type of attack, but it is not obvious. Let's make it clear and also improve unit test coverage.
Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Refactor (non-breaking change that only restructures code)
[x] Tests (you added tests for code that already exists, or your new feature included in this PR)
[ ] Documentation update
[ ] Chore (no impact to binary, e.g. .gitignore, formatting, dropping support for older tooling)
[ ] Release

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (fad9d63) 61.48% compared to head (bec1e8f) 61.49%.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #4860   +/-   ##
========================================
  Coverage    61.48%   61.49%
========================================
  Files          797      797
  Lines        70121    70122    +1
  Branches     36238    36238
========================================
+ Hits         43114    43119    +5
- Misses       19763    19764    +1
+ Partials      7244     7239    -5

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@intelliot this is ready to merge


fix: flux error properly read by cloud

Closes #22327

[ ] CHANGELOG.md updated with a link to the PR (not the Issue)
[x] Well-formatted commit messages
[x] Rebased/mergeable
[x] Tests pass

Before this change:

After this change:


Slot collision on latch with and (&) operator

Bug Report

Using and (&) operator to calculate slots index can lead to severe collision.
https://github.com/tikv/tikv/blob/9b8785a42f6e03621c0d0ce66799761b3e00f9cc/src/storage/txn/latch.rs#L212-L214
See more: https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=cdfa59d515af83e611e9492d5da3ecac
What version of TiKV are you using?

master

TiKV will use a power of two as the real capacity of latches instead of the value configure by user. See  https://github.com/tikv/tikv/blob/master/src/storage/txn/latch.rs#L136

Latch size is rounded up to the power of 2. & equals % in this case.


Update Download page

Add next steps -> Getting started
Be upfront w/ Linux/MacOS support using tabs (like Consul), but no windows

Closed by #119


Correctly parse arguments from environment variables

Fixes https://github.com/rust-lang/cargo/issues/14381.
The current parsing doesn't correctly handle arguments like --x="y z". To be noted: if you don't want the dependency, I can write a parser by hand too, shouldn't take many lines of code to do.
r? @epage

I'm unsure what the compatibility guarantees are around this.  @ehuss if you have any insight, it'd be appreciated.
In general, we recommend starting with an issue.  That way we make sure we are all on the same page (e.g. the definition of the problem in this PR is unclear) and, if we go through multiple possible PRs for the problem (which is common enough), the conversation on the problem and solution space is centralized rather than split among all of the PRs.

I opened https://github.com/rust-lang/cargo/issues/14381 too.


New version of PyVista broke the CI testing

The default BG color changed so we need to update the baseline image.
FYI @banesullivan

Ah yes, we changed the default theme of PyVista to be more document/website friendly. This sort of change shouldn't happen again


Q: CM3 inherited from RPI2 and not RPI3?

I'm trying to use CM3 with eMMC with meta-raspberrypi and it boots fine with build image. Interestingly when looking at documentation for CM3 it should be similar to RPI3 (processor used is: https://www.raspberrypi.org/documentation/hardware/raspberrypi/bcm2837/README.md). Even if it is working shouldn't be cm3 inherited from RPI3-64?  Marek

we have separate machine configs for 64bit RPI 3 machines, but I think you are right that it should be inheriting raspberrypi3 machine setup and not rpi2 as far as SOC is concerned @agherzan added this machine config for cm3 and I guess there might have been some reason to pin it to rpi2 and not use rpi3 specs.

IIRC CM3 should use same cpu ase RPI 3 - 64 bit. So probably inherit from raspberry3-64? My problem is I'm hunting is that CM# have eMMC but in u-boot it's not working so I'm trying to find root cause. Thanks for heads up.

first try the 32bit version.

I tried with 32bit version and eMMC start working. But I didn't try u-boot-2017.09 from rocky but latest 2018.07 which works fine. I'll try also with 2017.09 and let you know.

OK thanks,  would you care to send a pull request to change the SOC type in machine conf file.

Yes sure.

@kraj well situation is bit problematic. Inherit from raspberry3 is OK but with this setup in rocko u-boot won't start at all (I need to use latest one). So I'll create PR only for machine change then.

@nandra @kraj I can't remember exactly why this happened but I think it was from the times where rpi3 and cm3 where inheriting rpi2. We should change it to rpi3. @nandra What do you mean by the latest one?

@nandra https://github.com/agherzan/meta-raspberrypi/pull/288

Fixed by #288.


Passing Data Through Props not updated in docs v.17.0.1

In react v17.0.1 I guess the documentation is not updated regarding the props
When I hover the props it shows this in my IDE:
React.Props<T> is now deprecated, which means that the children property is not available on P by default, even though you can always pass children as variadic arguments to createElement. In the future, if we can define its call signature conditionally on the existence of children in P, then we should remove this.

Error:
TypeScript error in $PROJECT_PATH/Game.component.tsx(6,52):
Property 'num' does not exist on type 'Readonly<{}> & Readonly<{ children?: ReactNode; }>'.  TS2339

    4 |     render(){
    5 |         return (
  > 6 |             <button className="square">{this.props.num}</button>
      |                                                    ^
    7 |         )
    8 |     }
    9 | }

You’re using TypeScript. If you’re using TypeScript you need to declare the type of your props. This is unrelated to React.


Spatial is spelled wrong in code and examples

I just tried out the spatial stuff and it worked great, thanks!
Small nit: I noticed that things are spelled "spacial" but I believe it should be "spatial" (see https://en.wikipedia.org/wiki/Spatial).
Happy to do a PR for this myself but wanted to raise an issue first to gauge interest.
Thanks for reading my nit issue 😅

Oh yeah, that should definitely be fixed :sweat_smile:


ValueError: '/1/tags' is not in the subpath of '/2' OR one path is relative and the other is absolute

Suppose the error happen when --data-dir run parameter of sd is set.
Error itself:
File "", line 883, in exec_module
File "", line 241, in _call_with_frames_removed
File "/content/drive/MyDrive/SD/extensions/a1111-sd-webui-tagcomplete/scripts/tag_autocomplete_helper.py", line 224, in
write_tag_base_path()
File "/content/drive/MyDrive/SD/extensions/a1111-sd-webui-tagcomplete/scripts/tag_autocomplete_helper.py", line 191, in write_tag_base_path
f.write(TAGS_PATH.relative_to(FILE_DIR).as_posix())
File "/usr/lib/python3.10/pathlib.py", line 818, in relative_to
raise ValueError("{!r} is not in the subpath of {!r}"
ValueError: '/content/drive/MyDrive/SD/extensions/a1111-sd-webui-tagcomplete/tags' is not in the subpath of '/content/repository' OR one path is relative and the other is absolute.
run parameters: -u -m launch --data-dir /content/drive/MyDrive/SD --xformers --xformers-flash-attention

This is due to a Gradio security feature / issue. The javascript side of the extension (~80% of the functionality) will not be able to access files that are not in the root folder of the webui. And for good reason, as Gradio is a local server that can be shared and thus accessed from outside, if arbitrary client side javascript could access any files on your system, it would be a massive risk.
But due to this, as you said, if the data dir or extensions dir is anywhere outside of the webui root, the script won't work. Sadly nothing I can do about it with the current way this works, it would need manual deactivation of the aforementioned Gradio security features by editing their code.

@TokcDK Good news, if still needed:
With the most recent update, the extension can now work with data-dir.
You will need to add the --gradio-allowed-path argument to your webui start script to make this work, else the helper will not throw the error anymore, but the server will still return 403 Unauthorized for any extension javascript file or tags file the webui tries to load.
A word of caution if you share the webui on your local network or even as a public server:
The allowed path will be publicly exposed. A simple JavaScript fetch("file=path/to/file") can access any file contents in that directory and its subdirectories, as long as the filename is known. You need to be careful what you allow in there.
I suggest only allowing the install dir of tag autocomplete itself for base functionality, or if you use wildcard extensions and want to use the wildcard completion feature, the whole extensions dir at most.

/content/drive/MyDrive/SD

Ok, understood you. Thanks for the info!


Checking out a PR will try to fetch tags and display an error

Extension version: 0.15.0
VSCode version: 1.43.2
OS: macOS Catalina (10.15.3)
git version: 2.24.1

Steps to Reproduce:

Clone https://github.com/microsoft/vscode-python (or a fork of it), and make sure you have the tags locally as well
Checkout a PR (here it was https://github.com/microsoft/vscode-python/pull/10883/)
The checkout succeeds, but I get a notification saying "Error" as well:

Content of the GitHub Pull Request output panel:
[Info] Review> switch to Pull Request #10883 - start
[Info] Unshallowing failed: Failed to execute git {
  "exitCode": 1,
  "gitCommand": "pull",
  "stdout": "",
  "stderr": "From github.com:ericsnowcurrently/vscode-python\n * [new branch]          ci-update-to-3.8  -> ericsnowcurrently/ci-update-to-3.8\n * [new branch]          completions-script-tests -> ericsnowcurrently/completions-script-tests\n * [new branch]          consolidate-fs-usage -> ericsnowcurrently/consolidate-fs-usage\n * [new branch]          extension-activation-deferred -> ericsnowcurrently/extension-activation-deferred\n * [new branch]          fix-2696-add-mypy-regex-test -> ericsnowcurrently/fix-2696-add-mypy-regex-test\n * [new branch]          fix-9939-reduce-ci-py-versions -> ericsnowcurrently/fix-9939-reduce-ci-py-versions\n * [new branch]          fs-new-api        -> ericsnowcurrently/fs-new-api\n * [new branch]          fspaths-module    -> ericsnowcurrently/fspaths-module\n * [new branch]          internal-tools-helper -> ericsnowcurrently/internal-tools-helper\n * [new branch]          jedi-upgrade      -> ericsnowcurrently/jedi-upgrade\n * [new branch]          master            -> ericsnowcurrently/master\n * [new branch]          pep8-rename       -> ericsnowcurrently/pep8-rename\n * [new branch]          prettier-line-length-100 -> ericsnowcurrently/prettier-line-length-100\n * [new branch]          prettier-line-length-80 -> ericsnowcurrently/prettier-line-length-80\n * [new branch]          pytest-adapter    -> ericsnowcurrently/pytest-adapter\n * [new branch]          pythonPathUpdater-unit-tests -> ericsnowcurrently/pythonPathUpdater-unit-tests\n * [new branch]          release           -> ericsnowcurrently/release\n * [new branch]          revert-fs-changes -> ericsnowcurrently/revert-fs-changes\n * [new branch]          stub              -> ericsnowcurrently/stub\n * [new branch]          update-ts-mockito -> ericsnowcurrently/update-ts-mockito\n ! [rejected]            0.3.21            -> 0.3.21  (would clobber existing tag)\n"
}. Falling back to git pull
[Info] Review> checkout failed #{"message":"Failed to execute git","stdout":"","stderr":"From github.com:ericsnowcurrently/vscode-python\n * [new branch]          ci-update-to-3.8  -> ericsnowcurrently/ci-update-to-3.8\n * [new branch]          completions-script-tests -> ericsnowcurrently/completions-script-tests\n * [new branch]          consolidate-fs-usage -> ericsnowcurrently/consolidate-fs-usage\n * [new branch]          extension-activation-deferred -> ericsnowcurrently/extension-activation-deferred\n * [new branch]          fix-2696-add-mypy-regex-test -> ericsnowcurrently/fix-2696-add-mypy-regex-test\n * [new branch]          fix-9939-reduce-ci-py-versions -> ericsnowcurrently/fix-9939-reduce-ci-py-versions\n * [new branch]          fs-new-api        -> ericsnowcurrently/fs-new-api\n * [new branch]          fspaths-module    -> ericsnowcurrently/fspaths-module\n * [new branch]          internal-tools-helper -> ericsnowcurrently/internal-tools-helper\n * [new branch]          jedi-upgrade      -> ericsnowcurrently/jedi-upgrade\n * [new branch]          master            -> ericsnowcurrently/master\n * [new branch]          pep8-rename       -> ericsnowcurrently/pep8-rename\n * [new branch]          prettier-line-length-100 -> ericsnowcurrently/prettier-line-length-100\n * [new branch]          prettier-line-length-80 -> ericsnowcurrently/prettier-line-length-80\n * [new branch]          pytest-adapter    -> ericsnowcurrently/pytest-adapter\n * [new branch]          pythonPathUpdater-unit-tests -> ericsnowcurrently/pythonPathUpdater-unit-tests\n * [new branch]          release           -> ericsnowcurrently/release\n * [new branch]          revert-fs-changes -> ericsnowcurrently/revert-fs-changes\n * [new branch]          stub              -> ericsnowcurrently/stub\n * [new branch]          update-ts-mockito -> ericsnowcurrently/update-ts-mockito\n ! [rejected]            0.3.21            -> 0.3.21  (would clobber existing tag)\n","exitCode":1,"gitCommand":"pull"}
[Info] Review> Queuing additional validate state
[Info] Review> Validating state...
[Info] Found GitHub remote
[Info] Review> no matching pull request metadata found for current branch pr/ericsnowcurrently/10883-2

+1, this is unfortunately making the extension unusable for me at present, when trying to review a forked PR

/duplicate https://github.com/microsoft/vscode-pull-request-github/issues/2187


RRD path fix and tests

Fix from https://github.com/graphite-project/graphite-web/pull/2377 and added tests.

Codecov Report

Merging #2383 into master will increase coverage by 0.22%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #2383      +/-   ##
==========================================
+ Coverage   79.62%   79.85%   +0.22%
==========================================
  Files          85       85
  Lines        8893     8895       +2
  Branches     1899     1899
==========================================
+ Hits         7081     7103      +22
+ Misses       1551     1526      -25
- Partials      261      266       +5

Impacted Files
Coverage Δ

webapp/graphite/readers/rrd.py
85.48% <100%> (+38.81%)
:arrow_up:

webapp/graphite/settings.py
76.61% <0%> (-1%)
:arrow_down:

webapp/graphite/finders/standard.py
75.18% <0%> (-0.76%)
:arrow_down:

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 570265e...eed617a. Read the comment docs.

Thanks a lot, @piotr1212 ! Merging this.


Adding animation example

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Added animation example

Hi @condor-webdev, thank you for the PR! Unfortunately, I will have to close it because it adds a non-https link to the article, which we do not accept.
Feel free to open a new PR though. Happy coding!


Algorithm Architecture and Pytorch Implementation

Hi,
This is really a nice work,
I've faced some issues related to TensorFlow and CUDA, and I'm not that good with TensorFlow, I'm a Pytorch guy.
So I've decided to make a Pytorch implementation for MBPO, and I'm trying to understand your code..
From my understanding:
Taking AntTruncatedObs-v2 as a working example,
Pytorch Pceucode:
Total epochs = 1000
Epoch steps = 1000
Exploration epochs = 10
01. Initialize networks [Model, SAC]
02. Initialize training w/ [10 Exploration epochs (random) = 10 x 1000 environmnet steps]
03. For n in [Total epochs - Exploration epochs = 990 Epochs]:
04.    For i in [ 1000 Epoch Steps]:
05.        If i % [250 Model training freq] == 0:
06.            For g in [How many Model Gradient Steps???]:
07.                Sample a [256 size batch] from Env_pool
08.                Train the Model network
09.            Sample a [100k size batch] from Env_pool
10.            Set rollout_length
11.            Reallocate Model_pool [???]
12.            Rollout Model for rollout_length, and Add rollouts to Model_pool
13.        Sample an [action a] from the policy, Take Env step, and Add to Env_pool
14.        For g in [20 SAC Gradient Steps]:
15.            Sample a [256 size batch] from [05% Env_pool, 95% Model_pool]
16.            Train the Actor-Critic networks
17.    Evaluate the policy

Is that right?
My questions are about lines 06 & 11:
06: You're using some real time period to train the model.. in terms of gradients steps, How many steps they're?
11: When you reallocate the Model_pool, you set the [Model_pool size] to the number of [model steps per epoch],
But.. Isn't that a really huge training set for SAC updates? Are you disgarding all Model steps from previous epochs?
Sorry for this very big issue..
Best wishes and kind regards.

Rami Ahmed

Also, regarding line 11,
for how long should Model_pool expand? Bc it occupys the GPU's memory as it grows.

For line  6, I think it stops training until validation loss converges.
I have implemented a pytorch version myself (https://github.com/jiangsy/mbpo_pytorch/tree/master/mbpo_pytorch), and you may view it as a reference (there are some still gaps in performance but may still provide some help).

For line  6, I think it stops training until validation loss converges.
I have implemented a pytorch version myself (https://github.com/jiangsy/mbpo_pytorch/tree/master/mbpo_pytorch), and you may view it as a reference (there are some still gaps in performance but may still provide some help).

Thank you very much.. @jiangsy

Thank you very much.. @jiangsy

Here is a pytorch implementation that achieves the same performance on walker and hopper: https://github.com/Xingyu-Lin/mbpo_pytorch. Other tasks not tested.


bicep serialize tiny fixes

Boolean values must be lowercase
SiteLogsConfigData.Serialization.cs is not respecting the Name field. Hardcoding to logs for now
FileSystemApplicationLogsConfig.Serialization.cs fix to closing bracket

API change check
API changes are not detected in this pull request.


lone ops dont spawn with a planet anymore

About the PR

made lone ops spawn with their shuttle instead of a whole planet, the shuttle spawns on its own map, but ftling to the station works (cough, cough, salvage missions).
Why / Balance

Technical details

Media

Requirements

[X] I have read and am following the Pull Request and Changelog Guidelines.
[X] I have added media to this PR or it does not require an ingame showcase.

Breaking changes

Changelog

:cl:

tweak: Lone operatives spawn with their shuttle rather than an entire planet again

Summary by CodeRabbit

New Features

Introduced new game events: LoneOpsSpawn and SleeperAgents.

Improvements

Enhanced ZombieOutbreak with refined player role selection.
Updated GasLeak and SolarFlare events with specific audio announcements for better player awareness.

Balancing

Adjusted event occurrences for SleeperAgents and MassHallucinations to improve gameplay dynamics.

resolves #739

fixes performance issues so im merging


translations.js is being generated differently between different machines

The order of the keys are different.
This can't happen with Asset Pipeline, otherwise my application.js is going to be different across my app servers, and that causes a different asset fingerprint.
I'm trying to look further into this, but still haven't figured after what commit this started happening, will update if I find something.

Someone has kindly submitted a PR: #318
So I guess now would be great to discuss and decide what we want:

sorted translation to ensure consistency for translation files generated on different machines
keep translation unsorted, resolve by chaning gems like russian
both (with option), default unsorted

Second case (just keep unsorted) is not an option as it's hard to patch all the gems (especially not actively maintained ones, see yaroslav/russian#56, there are still no feedback). And I saw a lot of neglected gems recently.
I think current behavior (unsorted) with option enabling sorting will satisfy everyone. Good explanation in README is required too.
Personally, I do not care for order of keys at all.
@msjonker, can you please tell you opinion? And thanks for pull request!

The only reliable solution we found to ensure consistent asset fingerprints was to sort prior to JSON. I agree that this could be turned on as an option, for those who don't want this. However, I don't think the sorting of the JSON should have any adverse effects, aside from the extra processing.

I guess we can add it as an option, but warn about this "unsorted" behaviour until next major version
And then always sort it for next major version (if no one objects)
That option can be default to true (since they can set it back and we are still in rc)

That works for me.

#318 is almost done.
Could you guys review it (or even try it) to see if that's what you want.
Once reviewed I will merge.

Looks good for me, but can't battle test it now.

I will wait until you have battle test it :clock3:

Well, I don't sure that I will be able to battle test it all — we are no more working on the machines where I've noticed this.

@rafaelgaspar Are you able to test #318?

Sorry, I ended up having to scope my JS translations better to avoid this bug, so I can't reproduce it anymore in my app.

Well then I will just merge it.

Closing since #318 merged
Reopen if you can prove it doesn't work


Automate reporting and clean up of cloud account resources

[ ] IBM Cloud
[ ] AWS
[ ] Azure

Tasks

[ ] Report on what is currently there
[ ] Define tagging scheme for resources
[ ] Define process for cleaning resources
[ ] Automate cleanup

Exploring Azure CLI/API that will give options to retrieve the resource usage with billing cost

Azure Initial Version :
https://github.com/cloud-native-toolkit/azure-utilities
Future Releases for Azure

Currently test CLI with MFA but need to change to Service Principal
Extract consumption via JM
Tagging Scheme for all resources since currently resources provisioned are not tagged properly
Support the resources delete based on TAGs, Location , Resource Types
Support the retrieve of cost , billing based on date range (weekly , monthly )
Support the one click deletion of Azure Cloud Resources (Nuke very dangerous if someone accidentally run which will blow up entire account in few min)

Note:

For some reason, both myself and @Richard can’t access Azure Billing , Cost management via CLI scripts as we tried several options.

Our benefit of doubt is “Our subscription falls under parent IBM account which may need to give access.

Azure Initial Version :
https://github.com/cloud-native-toolkit/azure-utilities
Future Releases for Azure

Currently test CLI with MFA but need to change to Service Principal
Extract consumption via  JMESPath language while we sort out the permission for Billing / Cost
Tagging Scheme for all resources since currently resources provisioned are not tagged properly
Support the resources delete based on TAGs, Location , Resource Types
Support the retrieve of cost , billing based on date range (weekly , monthly )
Support the one click deletion of Azure Cloud Resources

Note:

For some reason, both myself and @Richard can’t access Azure Billing , Cost management via CLI scripts as we tried several options.
Our benefit of doubt is “Our subscription falls under parent IBM account which may need to give access”

@mjperrins  - FYI


Fix flaky test due to create bigquery dataset naming conflict

Integration test apache_beam.examples.complete.game.hourly_team_score_it_test.HourlyTeamScoreIT.test_hourly_team_score_output_checksum_on_small_input is flaky (~20%). The error message is
Conflict: 409 .. Already Exists: Dataset apache-beam-testing:hourly_team_score_it_dataset16752110784291

e.g.
https://ci-beam.apache.org/view/PostCommit/job/beam_PostCommit_Python_Examples_Direct/1436/
https://ci-beam.apache.org/view/PostCommit/job/beam_PostCommit_Python_Examples_Direct/1433/
https://ci-beam.apache.org/view/PostCommit/job/beam_PostCommit_Python_Examples_Direct/1428/
notice that all failed tests are trying to create dataset ALL ending with 4291. random.randint() becomes not random somehow, possibly some random.seed(x) was called before this test run.
Switch to use secrets.token_hex which cannot be affected by seed set.

Fix test_hourly_team_score_output_checksum_on_small_input flaky

Include python bigquery integration test created tables to clean up job

Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run Clean GCP Resources

Run Clean GCP Resources

Run Clean GCP Resources

Run Clean GCP Resources

Run Python Examples_Direct

Run Python Examples_Direct

with pattern added the job https://ci-beam.apache.org/job/beam_CleanUpGCPResources/ will return a fail state due to lack of permission to some tables, which likely not created by jenkins but some manual runs. This is not severe: see context in #24770

test succeeded: https://ci-beam.apache.org/job/beam_PostCommit_Python_Examples_Direct_PR/23/

Pretty high probability. It is failing on last 4 consecutive runs. Nice if we also have some errorprone task for python code...


Possible new module: pgpainless-autocrypt

It might be a nice idea to create a new module which implements Autocrypt.
The module would be opinionated and simplify operations like creating keys etc. by following the autocrypt recommendations
What do you think?

Not an immediate need on our end, but would be nice eventually.
I'm not sure that Autocrypt handles creating keys? The only thing I can foresee using (on Android) is creating autocrypt email header, and parsing autocrypt email header, for public key exchange and knowing rules for automatic encryption.

fyi, there is https://github.com/iNPUTmice/lttrs-autocrypt

Out of scope for now.


Using only two decoder GRU?

Hi,
in network.py function decode1,
dec_ = attention_decoder(dec, hp.embed_size, memory, variable_scope="attention_decoder1") # (N, T', 256)
dec = dec_ + attention_decoder(dec_, hp.embed_size, memory, variable_scope="attention_decoder2") # (N, T', 256) # residual connections
In case of Tacotron, it uses attention RNN(1 layer GRU) and decoder RNN(2layer GRU). Attention in Tacotron scores memory(from encoder GRU) with query (from attention RNN) and makes context vector.
This context vector is concatenated with attention RNN's cell output to form decoder RNN's input.
Figure 1 in linked paper's architecture seems to be the same with Tacotron except that it has 8 layers.(https://arxiv.org/pdf/1609.08144.pdf)
Context vector should be shared for two decoder layers, but two attention decoder with different variable_scope will calculate context vector twice.

Awesome! I've reflected your suggestion. One thing I think differently than you is I don't see the context vector should be shared for the folloing two layers because we are to do a residual connection vertically.
Sorry for my late response. Please check my revision, and leave any comments if necessary.


Regex of CompileWarning will be mismatched some other warnings.

Here is an example log:
/Volumes/data/workspace/ABCFile.m:110:27: warning: unused variable 'domainWhitelist' [-Wunused-variable]
ld: warning: Could not find or use auto-linked framework 'CoreAudioTypes': framework 'CoreAudioTypes' not found
ld: Undefined symbols:
  _xxxx, referenced from:
      -[ABC testcase] in tests.o
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Because of the parser will move to top for next fast check, the line of ld warning will be mismatched and outputs of Undefined symbols will be disappeared like this:

I think the regex of CompileWarning should exclude LDWarning properly like this:
static let regex = Regex(pattern: #"^(?!ld)(([^:]*):*\d*:*\d*):\swarning:\s(.*)$"#)

Hey @blastmann! Thanks for filling this. It looks like this relates to xcbeautify's one-line-at-a-time logic. I plan to refactor this after I release 2.0.0 (expected to release this week). It'll likely be a couple of weeks before I can introduce the logic that I think will be necessary to then fix this issue. In the meantime, you might find it helpful to pass the --preserve-unbeautified flag. Rest assured, this is on my radar.


Client ID and Invalid credentials

The information in the Readme is not very helpful.  I got to the point where I am able to redirect to bungie, but there is no place to pass the client ID as a param. I hard coded it in and was able to authorize the app, but now I am getting an invalid credentials error. This is the only response I'm getting back from Bungie:
Parameters: {"message"=>"invalid_credentials", "origin"=>"https://myurl.com/signin", "strategy"=>"bungie"}
@RuBAN-GT

Good day, @brianbolnick. I added an example of how I integrated this gem with my rails. On the Bungie side You should set only redirect url, scopes and origin header settings.

Thanks @RuBAN-GT! That's helpful. However, on the initial redirect to Bungie I keep getting an "Authorization query string parameters are not valid." error due to the client_id not being populated in the URL params. Here is an example request string:
https://www.bungie.net/en/OAuth/Authorize?client_id&redirect_uri=http%3A%2F%2Flocalhost%3A3001%2Fusers%2Fauth%2Fbungie%2Fcallback&response_type=code&state=6a8720d4709be588b4bc83a42744f8fbef65136cadf75abb
Notice client_id is blank. If I manually add client_id=<id> to the URL is redirects me to the right place and allows me to authorize. I've tried adding the client ID as a param but it doesn't look like that sticks either:
<%= link_to "Sign in with Bungie", user_bungie_omniauth_authorize_path(:client_id=>'=<id>') %>
Any thoughts?

I find the cause: You can set OAuth Client Type on the application settings page, and type changes the main ideas of authentication.
My URL string has another form with client type "Not applicable": https://www.bungie.net/en/Application/SignIn/11253?state... and it doesn't use client_id field. May be when I created this gem this option was not implemented or I...skiped it) Then You should set "Not applicable" option and everything should work. If it's useful then I have working example with this gem: https://grimoire.fydir.ru/
@brianbolnick, how do you think: for rails integration it's important difference between "Not applicable" and "Confidential"  methods?

Ok that makes sense I got that piece working thanks for the input! Now I am gettinERROR -- omniauth: (bungie) Authentication failure! csrf_detected: OmniAuth::Strategies::OAuth2::CallbackError, csrf_detected | CSRF detected
When going back to my app. What do you have set as your origin header? I am wondering if there is something else missing from the config.omniauth block @RuBAN-GT

@brianbolnick, I set * in application Origin header field on the Bungie application page. In README I showed all settings for config.omniauth.

@brianbolnick, I created the dev brunch, that changes oauth2 strategy. Please, change OAuth Client Type to Confidential and try to use a new version of gem from git.

I'm still working off the master branch trying to fix this error:
ERROR -- omniauth: (bungie) Authentication failure! csrf_detected: OmniAuth::Strategies::OAuth2::CallbackError, csrf_detected | CSRF detected
I've copied everything from your readme but the redirect from bungie back to my app is throwing that error @RuBAN-GT

@brianbolnick, I upgrated this gem, now You can use bungie authentication without any problems. Please, read the README again (now, it has new description) and try reconfigure your settings.

What are you using as the redirect_url? I currently have
https:///auth/bungie/callback
But am getting an invalid credentials error due to a mismatch of urls. I have the same url in my config as I do on bungie's app settings. @RuBAN-GT

This should be re-opened. I see the same behavior above using OmniAuth::Builder. Other OmniAuth strategies are working without issue, just this one is misbehaving. I'm willing to provide any info requested to prove this is still broken.


npm installation error

Do you want to request a feature or report a bug?
bug
What is the current behavior?
While running npm install -g preact-cli, the installation fails saying:
➜  ~ npm install -g preact-cli
npm ERR! Unexpected end of input at 1:51497
npm ERR! 3","cookie":"0.0.3","crc":"0.2.0","fresh":"0.1.0","methods":"0.0.1","
npm ERR!                                                                      ^

yarn global add preact-cli works perfectly fine. Looks like a npm issue to me.
If the current behavior is a bug, please provide the steps to reproduce.

npm uninstall -g preact-cli
npm install -g preact-cli

The whole npm install log is available here in this gist.

Please mention other relevant information.

node version: 8.3.0
npm version: 5.3.0
yarn version: 0.27.5
Operating system: macOS Sierra

This sure is an npm issue.
It is because of an incomplete request. Either in the cache or from the remote server.
npm cache clean --force && npm install -g preact-cli

will do the trick (removes the whole cache 😅 and install it again)


On methodology we should outline WHY for each source we are using

[ ] in the methodology stress the reason why we wanted to specifically highlight opioid use as a subset of that data source because of the prevalence of that crisis. Kind of like how we that overarching message regarding racism and its relationship to scarce data, we could include the need to highlight opioid use.
[ ] same for all existing conditions

Assign to JC - to start next sprint

track under #1706


Add multi-block support

Description of changes:
This change adds support for multiple block
requests and receives. A sequence of up to
NUM_OF_BLOCKS_REQUESTED will be requested
which are sequential in block number if
still needed. Upon receiving the OTA agent
will determine if the block is needed.
With this feature the request data block behavior changes to request up to the first NUM_OF_BLOCKS_REQUESTED needed from a starting index. For example...If 10 blocks are needed and block 3 has already been received and the NUM_OF_BLOCKS_REQUESTED configured is 3 then the first request would reach out for blocks 0-2 (inclusive). If block 0 and 1 were received then only block 2 would be requested as block 3 is already received. This will not purposely re-request stored blocks.
With this feature upon receiving a new block the block will be stored. Any duplicate blocks are discarded.
DISCLAIMER: This is not a very efficient implementation. Often blocks are requested a number of times because we're not tracking what has been requested. This optimization can be added later.
Issue #, if available:
https://forums.freertos.org/t/bitmap-in-modular-ota-example/19994/4
Testing
Case 1: NUM_OF_BLOCKS_REQUESTED == 1
Successfully connected to IoT Core
OTA Event Queue created.
OTA Event Sent.
OTA Event received
Received Event is 1
Request Job Document event Received
-------------------------------------
OTA Event Sent.
OTA Event received
Received Event is 2
Received Job Document event Received
-------------------------------------
Received OTA Job.
OTA Event Sent.
OTA Event received
Received Event is 4
Request File Block event Received
-----------------------------------
Starting The Download.
Requesting blocks 0-1
OTA Event Sent.
OTA Event received
Received Event is 5
Received File Block event Received
---------------------------------------
Downloaded block 0. Remaining blocks to download: 18.
OTA Event Sent.
OTA Event received
Received Event is 4
Request File Block event Received
-----------------------------------
Requesting blocks 1-2
OTA Event Sent.
OTA Event received
Received Event is 5
Received File Block event Received
---------------------------------------
Downloaded block 1. Remaining blocks to download: 17.
OTA Event Sent.
OTA Event received
Received Event is 4
Request File Block event Received
-----------------------------------
Requesting blocks 2-3
OTA Event Sent.
OTA Event received
Received Event is 5
Received File Block event Received
---------------------------------------
Downloaded block 2. Remaining blocks to download: 16.
OTA Event Sent.
OTA Event received
Received Event is 4
Request File Block event Received
-----------------------------------
Requesting blocks 3-4
OTA Event Sent.
OTA Event received
Received Event is 5
Received File Block event Received
---------------------------------------
Downloaded block 3. Remaining blocks to download: 15.
OTA Event Sent.
OTA Event received
Received Event is 4
Request File Block event Received
-----------------------------------
Requesting blocks 4-5
OTA Event Sent.
OTA Event received
Received Event is 5
Received File Block event Received
---------------------------------------
Downloaded block 4. Remaining blocks to download: 14.
OTA Event Sent.
OTA Event received
Received Event is 4
Request File Block event Received
-----------------------------------
Requesting blocks 5-6
OTA Event Sent.
OTA Event received
Received Event is 5
Received File Block event Received
---------------------------------------
Downloaded block 5. Remaining blocks to download: 13.
OTA Event Sent.
OTA Event received
Received Event is 4
Request File Block event Received
-----------------------------------
Requesting blocks 6-7
OTA Event Sent.
OTA Event received
Received Event is 5
Received File Block event Received
---------------------------------------
...
...
Downloaded block 17. Remaining blocks to download: 1.
OTA Event Sent.
OTA Event received
Received Event is 6
Close file event Received
-----------------------
Downloaded Data Lorem ipsum dolor sit amet,
OTA Completed successfully!

Case 2: NUM_OF_BLOCKS_REQUESTED == 4
[WARN] pthread_attr_setstack failed with return value: 22. Default stack will be used.
[WARN] Increase the stack size to PTHREAD_STACK_MIN.
[WARN] pthread_attr_setstack failed with return value: 22. Default stack will be used.
[WARN] Increase the stack size to PTHREAD_STACK_MIN.
[WARN] pthread_attr_setstack failed with return value: 22. Default stack will be used.
[WARN] Increase the stack size to PTHREAD_STACK_MIN.
[WARN] pthread_attr_setstack failed with return value: 22. Default stack will be used.
[WARN] Increase the stack size to PTHREAD_STACK_MIN.
[WARN] pthread_attr_setstack failed with return value: 22. Default stack will be used.
[WARN] Increase the stack size to PTHREAD_STACK_MIN.
Suspend resume task
D Transport_OpenSSL: Successfully imported root CA.
D Transport_OpenSSL: Successfully imported client certificate.
D Transport_OpenSSL: Successfully imported client certificate private key.
D Transport_OpenSSL: Setting server name a3ixdjl0lkg4lt-ats.iot.us-east-1.amazonaws.com for SNI.
D Transport_OpenSSL: Established a TLS connection.
Successfully connected to IoT Core
OTA Event Queue created.
OTA Event Sent.
OTA Event received
Received Event is 1
Request Job Document event Received
-------------------------------------
OTA Event Sent.
OTA Event received
Received Event is 2
Received Job Document event Received
-------------------------------------
Received OTA Job.
OTA Event Sent.
OTA Event received
Received Event is 4
Request File Block event Received
-----------------------------------
Starting The Download.
Requesting blocks 0-4
OTA Event Sent.
OTA Event received
Received Event is 5
Received File Block event Received
---------------------------------------
Downloaded block 0. Remaining blocks to download: 18.
OTA Event Sent.
OTA Event received
Received Event is 4
Request File Block event Received
-----------------------------------
Requesting blocks 1-5
OTA Event Sent.
OTA Event received
Received Event is 5
Received File Block event Received
---------------------------------------
Downloaded block 1. Remaining blocks to download: 17.
OTA Event Sent.
OTA Event received
Received Event is 4
Request File Block event Received
-----------------------------------
Requesting blocks 2-6
OTA Event Sent.
OTA Event received
Received Event is 5
Received File Block event Received
---------------------------------------
Downloaded block 2. Remaining blocks to download: 16.
OTA Event Sent.
OTA Event received
Received Event is 4
Request File Block event Received
-----------------------------------
Requesting blocks 3-7
OTA Event Sent.
OTA Event received
Received Event is 5
Received File Block event Received
---------------------------------------
Downloaded block 3. Remaining blocks to download: 15.
OTA Event Sent.
OTA Event received
Received Event is 4
Request File Block event Received
-----------------------------------

...
Downloaded block 17. Remaining blocks to download: 1.
OTA Event Sent.
OTA Event received
Received Event is 6
Close file event Received
-----------------------
Downloaded Data Lorem ipsum dolor sit amet,
OTA Completed successfully!

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Formatting with uncrustify results in significant changes. I'll format at the end once I have approvals to avoid bloating this PR.


Make certified assets functionality available as a library.

This also updates the dependencies and the toolchain version to prevent incompatibilities.

Oh, I didn't see that one.
I was setting up some basic CI and inadvertently created merge conflicts.


start serving from the plats dir, change in www/* => cordova prepare

Start serving from the platforms directory.
Advantages:
* Better support for custom workflows: .sass file changed -> gulp compile -> copy results to platform dir -> BrowserSync(LiveReload) picks up changes from platform dir
* Support for changes to cordova merges directory

Whenever a change happens in the www/* dir, run cordova prepare

@nikhilkh


How to run Amandroid in parallel mode?

Hi,
I am wondering how to enable parallel mode for Amandroid? As suggested here, Akka Actor should be used, but how do I actually use it for Amandroid?
Thank you in advanced!

I forget to update the website. The Akka actor code has been removed.

Thanks for your reply. In this case, is it a good practice to set parallel=true in config.ini as an alternative?


start issue

I got following error when i tried to start:
(minerva-author) MSKI2114:minerva-author xiey$ python src/app.py
Traceback (most recent call last):
  File "/Volumes/GoogleDrive/My Drive/GitHub/minerva-author/src/app.py", line 39, in <module>
    import ome_types
  File "/Users/xiey/miniconda3/envs/minerva-author/lib/python3.10/site-packages/ome_types/__init__.py", line 12, in <module>
    from .model import OME
  File "/Users/xiey/miniconda3/envs/minerva-author/lib/python3.10/site-packages/ome_types/model/__init__.py", line 1, in <module>
    from .affine_transform import AffineTransform
  File "/Users/xiey/miniconda3/envs/minerva-author/lib/python3.10/site-packages/ome_types/model/affine_transform.py", line 1, in <module>
    from ome_types.dataclasses import ome_dataclass
  File "/Users/xiey/miniconda3/envs/minerva-author/lib/python3.10/site-packages/ome_types/dataclasses.py", line 11, in <module>
    from pydantic.dataclasses import _process_class
ImportError: cannot import name '_process_class' from 'pydantic.dataclasses' (/Users/xiey/miniconda3/envs/minerva-author/lib/python3.10/site-packages/pydantic/dataclasses.cpython-310-darwin.so)

It looks like you're on a Mac, is that right? Did you use the latest instructions for creating the conda environment, updated on August 23? You could also try the pre-built Mac release at https://github.com/labsyspharm/minerva-author/releases .

Hi @jmuhlich
Thanks for your reply. Yeah, the pre-built Mac release works! Tho something is weird. It eats up all the hardware storage on my computer (600GB) and then triggers crash of my Mac. Do you have any thoughts on this? Thanks.

I am also having a lot of disk thrashing which eventually fills the entire file system; the program is idle when this is happening. It’s actually about 1-2 gb/minute which is pretty alarming.

That sounds quite serious. I’ve not encountered that problem before, but I’ll see if I can reproduce on my Mac.

I will see if I can reproduce this issue on my MacOS. Do you have any information on the nature of the files that are generated?

The console reports a bunch of warnings about a constantly changing set of temporary directories. Example:
[28310] WARNING: file already exists but should not: /var/folders/8v/5lyn4dwx3wz_cwy2tkp9h89m0000gn/T/_MEIQyMzMQ/lib-dynload/zlib.cpython-310-darwin.so
[28600] WARNING: file already exists but should not: /var/folders/8v/5lyn4dwx3wz_cwy2tkp9h89m0000gn/T/_MEIU6u8h2/lib-dynload/_asyncio.cpython-310-darwin.so

Looking in that area, the files seem to be python scripts, compiled pyc files, and copies of shared libraries. More copies of this are created every 10 seconds or so.

@YubinXie
Your initial issue running python src/app.py is fixed on master.

I got following error when i tried to start:
(minerva-author) MSKI2114:minerva-author xiey$ python src/app.py
...

If you pull from master, the python src/app.py command runs the app as expected.
I have tested this on my MacOS v12.6.

As for the major executable issue seen by @YubinXie and @jil24, I've discovered the root cause and will be releasing a fully patched release as soon as possible. The latest release has merely been remediated to write these errant temporary files much less frequently.
The root issue stems from our python packaging dependency leading to incorrect handling of multiprocessing.

The latest v1.11.1 release resolves both issues in this thread. The suite of WARNING: file already exists but should not messages will still appear, but only on initialization of the app. 700 MiB will be written to /var/folders as required by the app, but no further data will be written to that directory.


Automated release for multiple hdk versions

Example Version:
0.3.3-pre+hdk-0.0.122
The +… part is valid semver:
https://semver.org/#spec-item-10
Implementation:

when ready to release a new version, cut a branch eg:
release/0.3.4
push branch to GitHub
on CI, we detect this new branch (release/x.x.x) and:
Run tests and checks
If anything fails, try clearing .cargo and target and try again
Read the current hdk version in use from cargo.toml (eg 0.0.122)
Bump version in cargo.toml to 0.3.4-pre+hdk-0.0.122
Git tag that version number
Push to GitHub
Push to crates.io
Repeat this process for all higher hdk versions that exist (eg 0.0.123, etc)
Repeat this process for up to 10 hdk versions total, including those lower than the starting hdk version

notes:

All of this happens on the release/0.3.4 branch
Only release versions when all checks pass
Stop trying to go up if a version fails
Stop trying to go down if a version fails

Hopefully not needed now that hdk is stabilizing


add hoodle (wavewave/hoodle#55)

To be honest I am not sure if this builds in Stackage Nightly, but here goes anyway.
(I wish stack would make that easier to test!)

cc wavewave/hoodle#55

A "just build all packages you think we need" flag might be useful.

Build failure:
Preprocessing library hoodle-types-0.3.0...
[ 1 of 12] Compiling Data.Hoodle.Primitive ( src/Data/Hoodle/Primitive.hs, dist/build/Data/Hoodle/Primitive.o )
[ 2 of 12] Compiling Data.Hoodle.Predefined ( src/Data/Hoodle/Predefined.hs, dist/build/Data/Hoodle/Predefined.o )
[ 3 of 12] Compiling Data.Hoodle.Util ( src/Data/Hoodle/Util.hs, dist/build/Data/Hoodle/Util.o )
[ 4 of 12] Compiling Data.Hoodle.Hashed ( src/Data/Hoodle/Hashed.hs, dist/build/Data/Hoodle/Hashed.o )
[ 5 of 12] Compiling Data.Hoodle.Simple.V0_1_1 ( src/Data/Hoodle/Simple/V0_1_1.hs, dist/build/Data/Hoodle/Simple/V0_1_1.o )
[ 6 of 12] Compiling Data.Hoodle.Simple.V0_2_2 ( src/Data/Hoodle/Simple/V0_2_2.hs, dist/build/Data/Hoodle/Simple/V0_2_2.o )
[ 7 of 12] Compiling Data.Hoodle.Simple.V0_3 ( src/Data/Hoodle/Simple/V0_3.hs, dist/build/Data/Hoodle/Simple/V0_3.o )
[ 8 of 12] Compiling Data.Hoodle.Simple ( src/Data/Hoodle/Simple.hs, dist/build/Data/Hoodle/Simple.o )
[ 9 of 12] Compiling Data.Hoodle.Generic ( src/Data/Hoodle/Generic.hs, dist/build/Data/Hoodle/Generic.o )
[10 of 12] Compiling Data.Hoodle.Zipper ( src/Data/Hoodle/Zipper.hs, dist/build/Data/Hoodle/Zipper.o )

src/Data/Hoodle/Zipper.hs:62:33: error:
    Ambiguous occurrence ‘length’
    It could refer to either ‘Data.Foldable.length’,
                             imported from ‘Data.Foldable’ at src/Data/Hoodle/Zipper.hs:22:1-20
                          or ‘Data.Sequence.length’,
                             imported from ‘Data.Sequence’ at src/Data/Hoodle/Zipper.hs:24:1-38

src/Data/Hoodle/Zipper.hs:62:46: error:
    Ambiguous occurrence ‘length’
    It could refer to either ‘Data.Foldable.length’,
                             imported from ‘Data.Foldable’ at src/Data/Hoodle/Zipper.hs:22:1-20
                          or ‘Data.Sequence.length’,
                             imported from ‘Data.Sequence’ at src/Data/Hoodle/Zipper.hs:24:1-38

src/Data/Hoodle/Zipper.hs:66:35: error:
    Ambiguous occurrence ‘length’
    It could refer to either ‘Data.Foldable.length’,
                             imported from ‘Data.Foldable’ at src/Data/Hoodle/Zipper.hs:22:1-20
                          or ‘Data.Sequence.length’,
                             imported from ‘Data.Sequence’ at src/Data/Hoodle/Zipper.hs:24:1-38

src/Data/Hoodle/Zipper.hs:98:15: error:
    Ambiguous occurrence ‘length’
    It could refer to either ‘Data.Foldable.length’,
                             imported from ‘Data.Foldable’ at src/Data/Hoodle/Zipper.hs:22:1-20
                          or ‘Data.Sequence.length’,
                             imported from ‘Data.Sequence’ at src/Data/Hoodle/Zipper.hs:24:1-38

src/Data/Hoodle/Zipper.hs:99:15: error:
    Ambiguous occurrence ‘length’
    It could refer to either ‘Data.Foldable.length’,
                             imported from ‘Data.Foldable’ at src/Data/Hoodle/Zipper.hs:22:1-20
                          or ‘Data.Sequence.length’,
                             imported from ‘Data.Sequence’ at src/Data/Hoodle/Zipper.hs:24:1-38

and
> /tmp/stackage-build9/poppler-0.14.0$ runghc -clear-package-db -global-package-db -package-db=/home/stackage/work/builds/nightly/pkgdb Setup configure --package-db=clear --package-db=global --package-db=/home/stackage/work/builds/nightly/pkgdb --libdir=/home/stackage/work/builds/nightly/lib --bindir=/home/stackage/work/builds/nightly/bin --datadir=/home/stackage/work/builds/nightly/share --libexecdir=/home/stackage/work/builds/nightly/libexec --sysconfdir=/home/stackage/work/builds/nightly/etc --docdir=/home/stackage/work/builds/nightly/doc/poppler-0.14.0 --htmldir=/home/stackage/work/builds/nightly/doc/poppler-0.14.0 --haddockdir=/home/stackage/work/builds/nightly/doc/poppler-0.14.0 --flags=

SetupWrapper.hs:60:49: error:
    Ambiguous occurrence ‘exeExtension’
    It could refer to either ‘Distribution.Simple.BuildPaths.exeExtension’,
                             imported from ‘Distribution.Simple.BuildPaths’ at SetupWrapper.hs:11:40-51
                          or ‘System.Directory.exeExtension’,
                             imported from ‘System.Directory’ at SetupWrapper.hs:23:1-23
                             (and originally defined in ‘directory-<IP_ADDRESS>:System.Directory.Internal.Config’)


Elm: Support for elm-lsp

This adds support for elm-lsp, making good on https://github.com/antew/vim-elm-analyse/issues/1 :)
The language server only supports diagnostics so far, but I'll be adding more soon.
Please let me know if anything looks odd, I am currently terrible at vimscript!

Cheers! :beers:


Issue building Tensorflow 1.8.0 from sources

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): OEL 7.4 (Oracle Linux)
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: NA
TensorFlow installed from (source or binary): Source
TensorFlow version (use command below): 1.8.0
Python version: 3.4.1
Bazel version (if compiling from source): 0.19.2
GCC/Compiler version (if compiling from source): 4.8.5
CUDA/cuDNN version: Not using Cuda
GPU model and memory: NA
Exact command to reproduce: bazel build --config=opt //tensorflow/tools/pip_package:build_pip_package

### Describe the problem
Describe the problem clearly here. Be sure to convey here why it's a bug in TensorFlow or a feature request.
While trying to build tensorflow from source, it failed stating:
"gcc: error: pywrap_tensorflow_internal_versionscript.lds: No such file or directory"

### Source code / logs
ERROR: /scratch/pransen/tensorflow-1.8.0/tensorflow/python/BUILD:3315:1: Linking of rule '//tensorflow/python:_pywrap_tensorflow_internal.so' failed (Exit 1) gcc failed: error executing command /bin/gcc -shared -o bazel-out/host/bin/tensorflow/python/_pywrap_tensorflow_internal.so -Wl,--version-script pywrap_tensorflow_internal_versionscript.lds '-Wl,-rpath,$ORIGIN/,-rpath,$ORIGIN/..' ... (remaining 90 argument(s) skipped)

@pransen  Request you to try bazel clean and build again.
bazel clean --expunge

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue?

We are closing this issue for now due to lack of activity. Please comment if this is still an issue for you. Thanks!


File not closed when finished() called.

In the following, the file is never closed when file.txt size is >= 1024 (using default buffer size of 1024).
var lineReader = require('line-reader')
var fs = require('fs')

var lines = ""
//var N = 511 // File is closed
var N = 512 // File is not closed
//var N = 513 // File is not closed
for (var i=0;i<N;i++) {
	lines = lines + " " + "\n"
}
fs.writeFileSync("file.txt", lines)

var i = 0
lineReader.eachLine('file.txt', function(line, last) {
  console.log(i + " " + line)
  if (i == 1) return false
  i = i+1
  return true
})

If I modify line_reader.js as below (and replace finish() with finish(reader) elsewhere)
   function finish(reader) {
      reader.close()
...

the file is closed.  (I have not run extensive tests on the fix.)

Was fixed by https://github.com/nickewing/line-reader/pull/12


misc bugs with relations

Well, misc strange bugs, mostly visible when we load ToOne entitty from not-owning side. Also, fixes edge cases when we can't resolve Abstract Discriminator entity type before we actually load disc value.
Should fix #87 as well. Should be merged only after @mpclarcson checks ).

@DavidBadura , please merge as checked.


link to better jupyter notebook preview

As mentioned in the deep dream tutorial readme the jupyter notebook preview on nbviewer is better than the one on github. Specifically, github removes the network graph visualizations.

Can one of the admins verify this patch?

We probably want to leave it the way it is for consistency with the rest of the tutorials. It should probably be a relative link like the others, though, so feel free to make it a relative link instead.

@jhseu As far as I can tell, this is the only tutorial which is a jupyter notebook, and clicking that link just redirects to github, so I think it's doomed to inconsistency regardless 😉

Jenkins, test this please


adding stats on access frequency

closing in favor of https://github.com/HackRVA/memberdashboard/pull/168


FluentAvalonia v2-preview2

Preview 2 to go along with the release of Avalonia 11.0-preview2 that released today
[Change log]

[Feature] Added localization ability to FA controls, currently implemented for NavigationView, TabView, InfoBar, and TeachingTip (#195)
[New Control] Ported TeachingTip from WinUI (#197)
[Fix] Border removed from TransparentButton control theme for Button
[Update] Avalonia ColorPicker updates (#202)
[Fix] Fixed issue where MenuFlyoutSubItem caused crashed if force closed
[Fix] Refactored FAPathIcon to ensure changing Data invalidates the icon and remove the cached geometry object (#203)
[Fix] Fixed an issue with CoreWindow where window size would be 16x8 px smaller than set size (#203)
[Fix] Refactored some of CoreWindow/CoreWindowImpl to improve OS specific code so Win32 stuff can be properly trimmed on non-Windows systems (#203)
[Update] Added the missing Avalonia TitleBar styles

Will merge probably on Monday. I think that's just about it, unless something large comes up between now and then.

There is a rather bad breaking-change PR I did: https://github.com/AvaloniaUI/Avalonia/pull/8793
That requires going through the templates of each control listed in that PR and updating the template part names. I will do this for you in another PR here but can't promise it will be done by Monday.

@amwx I finished two pull requests that should fix all this and they are ready to merge


Fluid Player Not entering true full screen mode on iOS

I installed fluid player about 10 days ago and when i tested it I could have sworn that it entered a true full screen mode which has a slightly different native style to it on ios.
But today i realized this feature wasnt working. Ive torn my site down and played with many config variables for fluid player and I still cant get it to trigger full screen mode.
So i went to the actual fluid player site and it seems as tho the player on their homepage is not entering full screen either.
I though it might be an ios issue so i went to other sites i found that use fluid player. A NSFW site called fuckler.com uses it and its version 1.1 and it seems like it works in true fullscreen perfectly. Below ive attatched pictures of the behavior fluidplayer is showing on full screen. Youll notice that you can see the adresss bar and footer bar in portrain mode on ios and in landscape mode you see the url bar.

Below is the native iOS player that was playing before. This is the functionality that I want and that im almost positive was working with fluid player before. And as i stated this functionality works on the site i found called fuckler.com but i wont post those screenshots because that would be NSFW and innapropriate.

Can someone else confirm this? Is this a change to the API? I noticed a recent changelog entry where there are some changes made to iOS display attributes.

After some research I found that I can get fluid player to enter true full screen on mobile if I set the layout option to browser instead of default which is was set to before.

Is there a way to make it so that I can use the styling of and functionality of the default option while maybe manually edditing in whatever trigger makes true full screen happen on iOS.

Hi @leather-s, are you using the latest version of Fluid Player? This issue you're having a specifically for iOS mobile is this correct? I will mark this bug and take a look into it.

Fluid Player Not entering true full screen mode on iOS
Any solution for this i just recently started using the fluidplayer which i really so far apart from this issue that looks still not fix the issue related to Fluid Player Not entering true full screen mode on iOS
if any one could help much appreciate here is testing area anyone can have a look where i am currently testing the player  http://chattt123.xyz


Components in turbo-frame are being ignored due to url mismatch

We have "tabs" in our app. Basic links that swap the contents of a turbo-frame. We have bridge components included in the content that gets dynamically loaded into the frame based on the tab you click. They're being ignored because the bridge's location doesn't match the metadata's url in bridgeDidReceiveMessage https://github.com/hotwired/strada-ios/blob/main/Source/BridgeDelegate.swift#L118 which appears to be the url from the link initiating the request, whereas the bridge location is still based on the initial page visit.
We tried this with the turbo-native-demo and experienced the same results with the menu controller.
What's the expectation here? Is there a way around this for the time being, or have we implemented something incorrectly? We don't really see anything in the documents around this. Just a comment in the strada-web library.
// Include the url with each message, so the native app can
// ensure messages are delivered to the correct destination
Thanks!

I've also run into this with a response that redirects to a different URL - for example, in my application, the entrypoint URL for the Turbo webview is /dashboard, and that redirects to /users/log-in if there is not an active user session.
I've observed the same behaviour with components being ignored due to a URL mismatch after this redirect, since the URL has changed from /dashboard to /users-log-in without the bridge delegate location being updated.
I've been looking around at how I can update the location myself, but because of how Turbo navigation visits work, I don't think there's a direct WKWebView delegate method I can use, since the URL could be modified by Turbo via pushState, rather than an actual navigation.

I've worked around this by forking and removing the assertion that the BridgeDelegate location matches the message metadata URL property. I then removed the package dependency and re-added it using my own repository. I originally tried extending or overriding BridgeDelegate, but the class being final prevents all the overrides I attempted.
I would like to arrive at a point where I can submit a PR for this problem, but I'm unsure of what the purpose of the guard is. I'm guessing it's to prevent messages being passed to a component that is part of the view hierarchy, but concealed by something else?
Keeping the location more up-to-date in the BridgeDelegate would be a solution, however there are several ways the location could change - it could be redirected, be navigated outside the webview (like using window.location or pushState), or like @mike-northsail ran into, could be a frame update. I think to track the location would require intercepting Turbo events in hotwired/strada-web, and passing this through to the BridgeDelegate somehow.
If it is important that the URL gets matched against, it is still possible to access this within each BridgeComponent's onReceive function - so if necessary, each component could guard or otherwise check that the component is running on the URLs it expects to be run on.

They're being ignored because the bridge's location doesn't match the metadata's url in bridgeDidReceiveMessage https://github.com/hotwired/strada-ios/blob/main/Source/BridgeDelegate.swift#L118 which appears to be the url from the link initiating the request, whereas the bridge location is still based on the initial page visit.

This is surprising behavior. We heavily use turbo-frame elements and have not experienced this issue directly. You can see the metadata url is populated from window.location.href: https://github.com/hotwired/strada-web/blob/main/src/bridge_component.js#L48C12-L48C32
Is the document url changing after loading new turbo-frame content?

Can you enable debug logging in the strada-ios and turbo-ios libraries and paste a log of events? I'm curious to see where things are breaking down.

https://github.com/hotwired/strada-ios/blob/main/docs/ADVANCED-OPTIONS.md#enable-debug-logging
https://github.com/hotwired/turbo-ios/blob/main/Docs/Advanced.md#enable-debug-logging

I can, but I'll note I have a slightly different cause of this issue - for me, it's that turbo-ios doesn't seem to be aware of the current webview's updated URL after navigation.
Here's what I get from turbo-ios:
2023-10-26 00:11:56 +0000 [Session] visit ["options": Turbo.VisitOptions(action: Turbo.VisitAction.replace, response: nil), "reload": false, "location": http://localhost:3000/dashboard]
2023-10-26 00:11:56 +0000 [ColdBootVisit] startVisit http://localhost:3000/dashboard [:]
bridgeDestinationViewDidLoad: http://localhost:3000/dashboard
bridgeDestinationViewWillAppear: http://localhost:3000/dashboard
bridgeDestinationViewDidAppear: http://localhost:3000/dashboard

Then if I tap on the 'Continue with Google' button (which the BridgeComponent is bound to):
bridgeDidIgnoreMessage: Message(id: "1", component: "google-auth", event: "authorize", metadata: Optional(Strada.Message.Metadata(url: "http://localhost:3000/users/log-in")), jsonData: "{\"metadata\":{\"url\":\"http:\\/\\/localhost:3000\\/users\\/log-in\"}}")

If I add a breakpoint in BridgeDelegate#bridgeDidReceiveMessage, location is "http://localhost:3000/dashboard", while the URL in the message metadata (coming from strada-web), is "http://localhost:3000/users/log-in". If I print the BridgeDelegate's bridge's webView's URL, it is:
(lldb) p bridge?.webView?.url
(Foundation.URL?) "http://localhost:3000/users/log-in"

So it's like the location that the bridge is aware of is not following when navigation occurs. I've been patching out that guard completely, but now that I look at it, I wonder if I'd be better to check the webView URL at runtime when that guard check occurs instead.
Here's what my backend request logs look like:
Started GET "/dashboard" for ::1 at 2023-10-26 13:16:30 +1300
Processing by DashboardController#show as HTML
Completed 401 Unauthorized in 2ms (ActiveRecord: 0.0ms | Allocations: 307)

Started GET "/users/log-in" for ::1 at 2023-10-26 13:16:30 +1300
Processing by Users::SessionsController#new as HTML
...etc

This flow is based on the Turbo-iOS demo application, specifically catching the 401 response, and then prompting for authentication.
Just like the demo application, my sign-in route is configured to open with 'modal' presentation, so I have two sessions in my app - one for the main webview, and another for modals. The session initialisation code for both includes initializing the bridge:
public func makeSession() -> Session {
        let configuration = Self.makeWKWebViewConfiguration()
        let session = Self.makeSession(configuration: configuration)
        session.delegate = self
        session.webView.uiDelegate = self
        Bridge.initialize(session.webView)

        return session
    }

I hope this helps!

In our case it's as simple as including a turbo-frame in the turbo-native-demo index.ejs and to wrap the strada-menu.ejs in a corresponding turbo frame.

  <turbo-frame id="demo-frame">frame waiting...</turbo-frame>

    Menu example

  <turbo-frame id="demo-frame">
    ...
  </turbo-frame>

We tried the suggestion from @joshmcarthur and when using the webView.url it allows us to keep the guard in place while still having the bridge delegate work as expected. Though at this time we're also using a version that has completely removed the guard.

Shot in the dark here… but can you print out the two URLs that are being compared in the guard statement? I'm wondering if a trailing slash is messing things up.

http://localhost:3000/clients/1 <- holds the turbo-frame and is the original url bound to the bridge delegate's location variable
http://localhost:3000/clients/1/tickets <- new url due to the history.pushState when advancing a turbo-frame
In our case, we have a single turbo frame acting as a dynamic placeholder for our links that give the visual representation of tabs. When you click on a tab, they update the content of the frame and turbo uses the history.pushState to update the url. We need this to allow the pull to refresh function to maintain the tab state. When the new tab html loads into the frame, strada-web uses the current (updated from the pushstate) location when binding the new bridge components, but the bridge delegate associated with the current session/webview is using the stale location variable in the guard as we haven't technically invoked a route proposal.

I'd imagine this is also going to affect someone who is using a lazy-loaded turbo frame (or in fact multiple turbo-frames on a page that navigate to different places), since strada-web is using the URL from the window.location object, not from the frame's src.

Hi there, I hit the same issue with bridgeDidIgnoreMessage here https://github.com/hotwired/strada-ios/blob/main/Source/BridgeDelegate.swift#L120 because location does not match message.metadata?.url
In my case its pretty simple in that when the app launches the WebView visits localhost:3000 which goes to the home#index action where I redirect_to another path if the user is logged out.
In that case the Strada component is not rendered.
Interestingly if I navigate away in the same view then hit the NavigationController "back" button, the component is now rendered fine. Only that first load is not working.
Also, other tabs that do not redirect render the components as expected

I have the same issues withbridgeDidIgnoreMessageafter redirect and after clicking to link with data-turbo-action="advance"

I had something similar to this and the difference was the trailing slash at the end of the url (url with trailing slash works fine).
Here's the a snapshot of the log testing both cases:
No slash:
2023-11-12 19:14:10 +0000 [Session] visit ["location": http://<IP_ADDRESS>:3000, "options": Turbo.VisitOptions(action: Turbo.VisitAction.advance, response: nil), "reload": false]
2023-11-12 19:14:10 +0000 [ColdBootVisit] startVisit http://<IP_ADDRESS>:3000 [:]
bridgeDestinationViewDidLoad: http://<IP_ADDRESS>:3000
bridgeDestinationViewWillAppear: http://<IP_ADDRESS>:3000
bridgeDestinationViewDidAppear: http://<IP_ADDRESS>:3000
bridgeDidIgnoreMessage: Message(id: "1", component: "sync", event: "connect", metadata: Optional(Strada.Message.Metadata(url: "http://<IP_ADDRESS>:3000/")), jsonData: "{\"metadata\":{\"url\":\"http:\\/\\/<IP_ADDRESS>:3000\\/\"},\"syncTitle\":\"Sync data\"}")
2023-11-12 19:14:12 +0000 [Bridge] ← pageLoaded ["timestamp":<PHONE_NUMBER>935, "restorationIdentifier": c5689ea0-844d-4e20-8b72-4529521cba73] [:]

With slash:
2023-11-12 19:13:11 +0000 [Session] visit ["options": Turbo.VisitOptions(action: Turbo.VisitAction.advance, response: nil), "reload": false, "location": http://<IP_ADDRESS>:3000/]
2023-11-12 19:13:11 +0000 [ColdBootVisit] startVisit http://<IP_ADDRESS>:3000/ [:]
bridgeDestinationViewDidLoad: http://<IP_ADDRESS>:3000/
bridgeDestinationViewWillAppear: http://<IP_ADDRESS>:3000/
bridgeDestinationViewDidAppear: http://<IP_ADDRESS>:3000/
bridgeDidReceiveMessage Message(id: "1", component: "sync", event: "connect", metadata: Optional(Strada.Message.Metadata(url: "http://<IP_ADDRESS>:3000/")), jsonData: "{\"metadata\":{\"url\":\"http:\\/\\/<IP_ADDRESS>:3000\\/\"},\"syncTitle\":\"Sync data\"}")
2023-11-12 19:13:13 +0000 [Bridge] ← pageLoaded ["restorationIdentifier": a2092ce4-70b9-48a6-ae67-cc0dab0b2d5c, "timestamp":<PHONE_NUMBER>697] [:]

Shot in the dark here… but can you print out the two URLs that are being compared in the guard statement? I'm wondering if a trailing slash is messing things up.

There seem to be 2 separate issues in this thread:

Stale BridgeDelegate.location causing messages to be ignored
Turbo-frames not updating the URL and causing messages to be ignored

Given the title of this issue is for turbo-frames, I created a new issue (#23) with my investigation of the stale location bug.  The two issues are related and cause the same behaviour, however I suspect they have different underlying causes.

Hey folks, can you give PR #24 a try? Thanks to @joshmcarthur for the idea of grabbing the URL at runtime!

Resolved via #24.


Mypy type checking

Description

See https://github.com/DLR-RM/stable-baselines3/pull/1143
Context

[ ] I have raised an issue to propose this change (required)

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation (update in the documentation)

Checklist:

[ ] I've read the CONTRIBUTION guide (required)
[ ] The functionality/performance matches that of the source (required for new training algorithms or training-related features).
[ ] I have updated the tests accordingly (required for a bug fix or a new feature).
[ ] I have included an example of using the feature (required for new features).
[ ] I have included baseline results (required for new training algorithms or training-related features).
[ ] I have updated the documentation accordingly.
[ ] I have updated the changelog accordingly (required).
[ ] I have reformatted the code using make format (required)
[ ] I have checked the codestyle using make check-codestyle and make lint (required)
[ ] I have ensured make pytest and make type both pass. (required)

Note: we are using a maximum length of 127 characters per line

we need to update the github action

I think there's no need: mypy is installed with sb3 and make type included mypy type check

I think there's no need: mypy is installed with sb3 and make type included mypy type check

yep, I realized that when I was about to change the action, still I added some color ;)

Ok I can see!


feat(katana): implement starknet_simulateTransactions trace API

Still relevant @kariy ? Let's bounty if it is

I was going to take it!


Passcode not same as old passcode.

User can restrict or  allow the old passcode in passcode change option.

Hello,
I'm really sorry, but I don't understand what this does. There are also a number of code changes I would like, if we proceed with this, but first I'd like to understand the purpose.
Why is the first commit a pull request from master? I would like a rebase, instead of a merge like this.

I'm sorry, but it has been a month, so I will have to close this.


Automator: update common-files@master in istio/istio@master

Generated by Automator - 2022-06-30T18:29:30+00:00

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio
d8bbbac3fb3d90ade26aa94ea1863ac576a9ccde
link
true
/test integ-pilot-istiodremote-mc_istio

integ-security-multicluster_istio
d8bbbac3fb3d90ade26aa94ea1863ac576a9ccde
link
true
/test integ-security-multicluster_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test unit-tests_istio

/retest-required

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio
d8bbbac3fb3d90ade26aa94ea1863ac576a9ccde
link
unknown
/test integ-security-multicluster_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-security-multicluster_istio

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio
d8bbbac3fb3d90ade26aa94ea1863ac576a9ccde
link
unknown
/test integ-security-multicluster_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio
69b8429601b4534b076836e4139b6368cc2f3e4e
link
true
/test integ-security-multicluster_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio
69b8429601b4534b076836e4139b6368cc2f3e4e
link
true
/test integ-security-multicluster_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

/test integ-security_istio


GPU-Z Plugin

** Name of the plugin **
GPU-Z Plugin
** Version **
1.0.0
** Author of the plugin **
RecklessBoon
** Description of the plugin **
While GPU-Z is running on the server machine, this plugin can poll the shared memory and insert the hardware data into Macro Deck 2 as variables. (i.e. It can grab CPU / GPU temperatures and the like)
** Link to the icon **
https://raw.githubusercontent.com/RecklessBoon/Macro-Deck-GPU-Z-Plugin/master/Resources/Macro_Deck_GPU-Z_Icon.png
** GitHub repository **
https://github.com/RecklessBoon/Macro-Deck-GPU-Z-Plugin/tree/v1.0.0
** Dependencies **
Macro Deck version: <IP_ADDRESS>291257
Newtonsoft.Json version: 12.0.2 NuGet

Please create a new issue once the issues are fixed.


Pass Events to DateHeader Component

Do you want to request a feature or report a bug?
Feature
What's the current behavior?
The DateHeader component is aware of it's own date, but it is not aware of the events occurring on that date.
What's the expected behavior?
I would like to pass the events corresponding to the date of the DateHeader so the DateHeader is able to apply styles based on the events of that day.
This use case has arisen from the following requirement: "When a day has at least 1 event, the date header should be bold."

Let me know what you think, and thank you for considering my feature request.

I'm a bit concerned about potential perf issues for doing the extra filtering for calendars with many dates, since in most cases the events are used. I think this can be worked around without a change by passing the events you're interested in to a custom date header component

@jquense Thanks for taking a look, performance concerns sound reasonable so I can accomplish this with a custom date header like you mentioned.


Update poru version to 5.1.0 (Lavalink 4)

Since there is a new version of poru that has moved to lavalink 4, I want to contribute and update the command variables in Lunox so that they work correctly with Poru 5.1.0. Currently testing.
Check list:

[x] Fix the Play command
[ ] Fix playlists (idk how to fix playlists)
[ ] Fix/add thumbnail display
[ ] Check and fix bugs

no playlist system in this source from the begining

okay


AKS to Private Link connection information is missing

Please provide information on connecting AKS to Storage Accounts using Private Endpoints.

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

ID: 724d659c-dcc8-7c77-1994-b3e8cc62eb8f
Version Independent ID: f6c82819-267b-6d05-fb0b-ced6f4eb5ca3
Content: Concepts - Storage in Azure Kubernetes Services (AKS) - Azure Kubernetes Service
Content Source: articles/aks/concepts-storage.md
Service: container-service
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

@dash042
Please go through this below doc link for your reference.
https://techcommunity.microsoft.com/t5/core-infrastructure-and-security/private-aks-and-acr-using-private-endpoint-part-2-2/ba-p/3122281#:~:text=AKS should have access to ACR Private Endpoint,the Private DNS Zone of the private ACR.
if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

@dash042
We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


Defining a transformation without bounds on a target should fail validation

The NumericalTarget constructor will happily accept a transformation without any bounds. This causes the call to target.transform() to turn the dataframe into NaNs.
from baybe.targets import NumericalTarget, TargetMode, TargetTransformation

# should fail, no bounds defined
target = NumericalTarget(
    name="Target_1",
    mode=TargetMode.MIN,
    transformation=TargetTransformation.LINEAR,
)

import pandas as pd

# RuntimeWarning: invalid value encountered in divide
#   res = (upper - arr) / (upper - lower)
print(target.transform(pd.DataFrame([1, 2, 3])))

    0
0 NaN
1 NaN
2 NaN

Thanks for reporting! This is for sure an error, but since our bounds are entirely optional, the solution to the problem is not to enforce bounds but to simply apply no transform, i.e., return the original series/dataframe. I'll create a fix today.

Thanks for reporting, will have a look into this!

PR (#451 ) is up :)


urllib3.connection.HTTPSConnection SDK error for Azure Resource Graph

Package Name:
Package Version:
Operating System:
Python Version:

Describe the bug
We are using python SDK for azure.mgmt.resourcegraph for querying the assets. But SDK most of the time giving us follwoing error stating: <urllib3.connection.HTTPSConnection object at 0x3ed9892d49a0>: Failed to establish a new connection: [Errno 110] Connection timed out
To Reproduce
Steps to reproduce the behavior:
1.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Hi @tsaindane-cloudwiz thank you for the feedback, we will investigate and get back to you asap. Could you please share the package version, operating system and python version you are running on?

package version of azure.mgmt.resourcegraph is 7.0.0
Its running on google's cloud function V1 with Python version: Python 3.9

Hi @tsaindane-cloudwiz
You mean you are using the ResourceGraphClient.resource method like in this sample? Yet with that, I failed to reproduce this issue. Please follow https://github.com/Azure/azure-sdk-for-python/blob/main/doc/dev/debug_guide.md to provide detailed log for deep investigation.

@ChenxiJiang333 Yes I am using ResourceGraphClient.resource method. So, this issue is not happening consistently, so in our architecture, we have 15-20 may be more parallel requests calling this function and for some of the request we faced this issue.

@tsaindane-cloudwiz Please know that python SDK is just a tool to send/receive http request/response, like what the method ResourceGraphClient.resource doing is just to call the api resources. Since it was an error returned by service, it's suggested to seek help from service team by opening issue at https://github.com/Azure/azure-rest-api-specs/tree/main. And I still hope you can follow https://github.com/Azure/azure-sdk-for-python/blob/main/doc/dev/debug_guide.md to provide a log to help service team address the issue.


documentation-folder-reorg

Documentation folder reorg

You might want to mark this as draft until it can be gone over to ensure no broken links etc. I will volunteer to use grep etc. to search for obsolete references to design and requirements folders in various documents.

Please check these links - files and line numbers are shown. Thanks!
chris@chris-z4:~/mmiele-DASH/DASH/documentation$ grep -rn --include=*.md '.md' |grep 'design/'
high-avail/xsight-labs-ha-proposal-v1.md:11:https://github.com/Azure/DASH/blob/main/documentation/high-avail/design/high-availability-and-scale.md
general/dash-sonic-hld.md:471:For testing purposes, it is convenient to express test configurations in a single canonical format, and use this to drive the different API layers to verify correct behavior. A tentative JSON format for representing DASH service configurations is described in https://github.com/Azure/DASH/blob/main/documentation/gnmi/design/dash-reference-config-example.md. Test drivers can accept this input, transform it into different schemas and drive the associated interfaces. For example, a JSON representation of an ACL rule can be transformed into gNMI API calls, SAI-redis calls, SAI-thrift calls, etc.
general/dash-high-level-design.md:282:Scale](../../high-avail/design/high-availability-and-scale.md) document.
general/dash-high-level-design.md:346:HLD](https://github.com/Azure/DASH/blob/main/documentation/general/design/dash-sonic-hld.md).
general/dash-high-level-design.md:408:HLD](https://github.com/Azure/DASH/blob/main/documentation/general/design/dash-sonic-hld.md).
general/dash-high-level-design.md:599:- [SONiC DASH HLD](https://github.com/Azure/DASH/blob/main/documentation/general/design/dash-sonic-hld.md)
chris@chris-z4:~/mmiele-DASH/DASH/documentation$ grep -rn --include=*.md '.md' |grep 'requirements/'
general/dash-high-level-design.md:113:  service](https://github.com/Azure/DASH/blob/main/documentation/vnet2vnet-service/requirements/README.md)
general/dash-high-level-design.md:115:  service](https://github.com/Azure/DASH/blob/main/documentation/vnet-peering-service/requirements/README.md)
general/dash-high-level-design.md:117:  service](https://github.com/Azure/DASH/blob/main/documentation/stpl-service/requirements/README.md)
general/dash-high-level-design.md:119:  service](https://github.com/Azure/DASH/blob/main/documentation/load-bal-service/requirements/README.md)
general/dash-high-level-design.md:121:  service](https://github.com/Azure/DASH/blob/main/documentation/encrypt-gw-service/requirements/README.md)
general/dash-high-level-design.md:123:  service](https://github.com/Azure/DASH/blob/main/documentation/express-route-service/requirements/README.md)

@chrispsommers Working on broken links, thank you for creating the list.

@chrispsommers Working on broken links, thank you for creating the list.

The sheer power of the grep command. :)

Ready for another review pass.

I think you missed this one:
high-avail/xsight-labs-ha-proposal-v1.md:11:https://github.com/Azure/DASH/blob/main/documentation/high-avail/design/high-availability-and-scale.md
general/dash-sonic-hld.md:471:For testing purposes, it is convenient to express test configurations in a single canonical format, and use this to drive the different API layers to verify correct behavior. A tentative JSON format for representing DASH service configurations is described in https://github.com/Azure/DASH/blob/main/documentation/gnmi/design/dash-reference-config-example.md. Test drivers can accept this input, transform it into different schemas and drive the associated interfaces. For example, a JSON representation of an ACL rule can be transformed into gNMI API calls, SAI-redis calls, SAI-thrift calls, etc.
general/dash-high-level-design.md:282:Scale](../../high-avail/design/high-availability-and-scale.md) document.

Fixed the links as follows:
high-avail/xsight-labs-ha-proposal-v1.md:11:https://github.com/Azure/DASH/blob/main/documentation/high-avail/design/high-availability-and-scale.md
High Availability and Scale document for the requirements.
general/dash-sonic-hld.md:471: https://github.com/Azure/DASH/blob/main/documentation/gnmi/design/dash-reference-config-example.md.
Reference configuration example (JSON).
general/dash-high-level-design.md:282:Scale](../../high-avail/design/high-availability-and-scale.md) document.
High Availability andScale document.

@chrispsommers Let me clean the README files. I'll delete the links.

@chrispsommers Removed obsolete links from the README files.

@chrispsommers I think I made the required fixes.
To avoid annoying conflicts with changes made using the old organization. and if there are no showstoppers, can you please approve the PR?
@KrisNey-MSFT can merge it into the main branch and we'll make adjustments if needed using the new organization.
Thanks

@chrispsommers I think I made the required fixes. To avoid annoying conflicts with changes made using the old organization. and if there are no showstoppers, can you please approve the PR? @KrisNey-MSFT can merge it into the main branch and we'll make adjustments if needed using the new organization. Thanks

Hi Michael, I still want to review it a bit more prior to approving. I understand the desire for speed, but the scope of this change pretty large so we need to get it right. Thanks for your patience.

@chrispsommers Take your time and let me know when you are done. Thanks

Hi @mmiele did you intend to remove all those obsolete "Back to" links? I still see many:
chris@chris-z4:~/mmiele-DASH/DASH/documentation$ grep -rn --include=*.md '.md' |grep 'Back to'
high-avail/slides/README.md:1:[ [ << Back to parent directory](../README.md) ]
high-avail/slides/README.md:3:[ [ << Back to DASH top-level Documents](../../README.md#contents) ]
README.md:1:[[ << Back to DASH top-level README ](../README.md)]
general/dash-general-compliance-requirements.md:1:[ [ << Back to parent directory](../README.md) ]
general/dash-general-compliance-requirements.md:3:[ [ << Back to DASH top-level Documents](../../README.md#contents) ]
general/sdn-pipeline-basic-elements.md:1:[<< Back to parent directory](../README.md) ]
general/sdn-pipeline-basic-elements.md:3:[<< Back to DASH top-level Documents](../../README.md#contents) ]
general/dash-high-level-design.md:5:[<< Back to parent directory](../README.md) ]
general/dash-high-level-design.md:7:[<< Back to DASH top-level Documents](../../README.md#contents) ]
general/sdn-features-packet-transforms.md:1:[<< Back to parent directory](../README.md) ]
general/sdn-features-packet-transforms.md:3:[<< Back to DASH top-level Documents](../../README.md#contents) ]
general/program-scale-testing-requirements-draft.md:2:[ [ << Back to parent directory](../README.md) ]
general/program-scale-testing-requirements-draft.md:4:[ [ << Back to DASH top-level Documents](../../README.md#contents) ]
vnet2vnet-service/vnet-to-vnet-service.md:5:[[<< Back to parent directory](../README.md)]
vnet2vnet-service/vnet-to-vnet-service.md:7:[[<< Back to DASH top-level Documents](../../README.md#contents)]

I stumbled on this, it is obsolete and should be deleted: https://github.com/mmiele/DASH/blob/documentation-folder-reorg/documentation/images/README.md

@chrispsommers Let me look into the links issue.

@chrispsommers Thank you for your thorough review. :heavy_check_mark: Until next time. :thumbsup:

@KrisNey-MSFT The PR is ready to be merged into the main branch.

@chrispsommers Thank you for your thorough review. ✔ Until next time. 👍

My pleasure buddy, great to work together again. We make a good tag-team.


Export useOnBottomScroll hook

The useOnBottomScroll is super useful when building your own notifications ui. This PR exports it.

Thanks for the contribution @kavdev!


Concerning sequence to sequence task using autotrain

Feature Request
"Hello, does autotrain --config <path_to_config_file> currently support sequence-to-sequence tasks?"
Motivation
autotrain --config <path_to_config_file>  supports sequence-to-sequence tasks
Additional Context
No response

seq2seq simply doesn't work with autotrain. all params are hard coded and.

would you mind elaborating? it should not be the case. if it is, ill fix it asap.


Document workaround for issue with usage in Vite

I don’t know why this issue is happening, but multiple people have run into it.
Refs #150
Closes #158

The workaround has been confirmed in #158


Notes on EAK/Ember CLI use and config

There was an issue a while back about how to use with initializers in EAK/Ember CLI. It's actually really easy and I took notes.

Most of the code of the library was rewritten to be an Ember addon compatible with Ember 1.13.
Now, the README is showing how to register wrappers in the initializer.
You can get the most recent version of ember-easy-form on the branch 1-0-stable or as an ember-addon here.


Make Flow layout usage opt-out

Describe your motivation
When having available server side Layout and no react layout is defined we should automatically get the server side layout as long as the developer doesn't mark the view as no flow layout.
This will make the Layout feature work the same way as it does with Flow routes.
Describe the solution you'd like
When file-routes are generated we check routes without layout against available server layouts and add the "flowLayout": true flag into the file-routes.json so that the server side layout is used.
Describe alternatives you've considered
No response
Additional context
No response

Will close vaadin/flow#19904


Port to python3?

Recently nixpkgs started using resholve in xdg-utils package. I only noticed it due to unrelated failures: python2packages use some oldsetuptoolsversion that don't support--parallel(I useenableParallelBuildingByDefault = true;). I was surprised to see that something still uses python2` to build my desktop system.
Would it be reasonable to post resholve to python3 ecosystem? Would it take a lot of effort? Or perhaps it's blocked on upstream depends stuck on python2?

See #88

This (or something like it) should eventually be ripe, btw. The c++ version of OSH is very close to parity with the reference python implementation, at which point some work on a new way to drive the parser and get a parse tree wouls clear the way for the refactoring needed to make use of it.
resholve lives right on top of the existing parser (I actually monkey-patch it to collect interesting nodes as they are instantiated to save us the time of a full walk) so there's some chance that could be a slog. To prepare for that, I've already done a fair amount of refactoring to resholve to mostly-contain the interactions with the parse tree in our own abstractions.
Porting should either be easy enough in that process, or easy enough to tack on after it. (The actual version port shouldn't be much work here tbh. This isn't an old py2 codebase. All of my other Python work is py3.)

For the time being I proposed https://github.com/NixOS/nixpkgs/pull/288407 for nixpkgs to make python2 packages compatible with enableParallelBuildingByDefault.

Looks like https://github.com/NixOS/nixpkgs/pull/288407 is blocked on lack of review. :(


CXG conversion should enforce that the var dataframe generates columns with "name_X"

In the genecode dry run script: https://github.com/chanzuckerberg/single-cell-curation/blob/main/scripts/schema_bump_dry_run_genes/gene_bump_dry_run.py#L78-L90 we assume that all gene names are stored in columns in the var dataframe with the pattern name_X (ex: "name_0", "name_1", etc).
However, in the CXG conversion code: https://github.com/chanzuckerberg/single-cell-data-portal/blob/9fe1a2550c5a571fdce55f708bd337e09435380b/backend/layers/processing/h5ad_data_file.py#L216-L225 we don't actually enforce this. The issue we had with dataset b2dda353-0c96-42df-8dcd-1ea7429a6feb in collection 1b014f39-f202-45ae-bb7d-9286bddd8d8b was that the var dataframe already had an index specified with name ensg_id, which was also a column in the var dataframe. This meant that we never entered the block of code that calls convert_index_to_column().
There isn't anything technically wrong with how the CXG conversion code is behaving. The expectation of transform_dataframe_index_into_column is to ensure that there is an index on the var dataframe that is also a column. However, since it's a bit easier for us to assume that gene names being used are stored in var dataframe columns following the same naming convention (and there may be other downstream places that make this assumption), it seems better to just update the CXG conversion code to adhere to what we expect in the genecode dry run script, rather than alter the genecode dry run script to search through the var dataframe's index name.
Steps would be to:

Update CXG conversion code and deploy to dev/staging/prod
Create a new revision for b2dda353-0c96-42df-8dcd-1ea7429a6feb that goes through the new CXG conversion code
Re-run the gencode dry run script

@joyceyan if we decide that re-running the gencode script to capture this dataset is not a priority, we can simplify resolution steps to step 1 as described, and then step 2 will be taken care of as a result of running the migration

@nayib-jose-gloria Ah gotcha - I think that we'd want to verify that the new CXG conversion code is working as expected, but it seems like it may be easier to just do the testing in dev and then running the migration in dev/staging/prod so we don't have to manually create new revisions.

@joyceyan nit: check uuids in the description as two of them (the ones being auto-formatted into links) have only 7 hex chars in the first segment. Should have 8.


Reduce benchmark suite running time

What was wrong?
https://github.com/ethereum/py-evm/issues/1607
How was it fixed?
Reduced benchmark suite running time

Let's reopen this later, if it becomes necessary again. It's not a huge change, the PR has been quiet a long time, and benchmarking has been fast enough lately.