Recommend xvfb-run -d instead of xvfb-run -a

Fixes #270

Thank you @micheljung for submitting a PR :smile_cat:
In light of https://github.com/plotly/orca/issues/270#issuecomment-561815224, I think we should keep mention of the -a flag for older versions of xvfb-run (which are still prevalent). However, mentioning users should use -d for newer versions of xvfb-run is a great addition.

@micheljung do you mind me taking over this PR and make the appropriate modifications?

@antoinerg not at all, go ahead :)


My name is Natalya. I enjoy self-hosting all the services I use because it makes me feel more secure knowing I control all my data. But a lot of the time I have to spend hours configuring these services because they were built with one system in mind. If only there was a standard system that I wouldn't have to configure.

(hint hint Docker)


assertion failed: key > self.key

Describe the bug
Using reth 0.1.0-alpha.4 (0ef68b7d) on Ubuntu 20.04 LTS, after syncing for ~2 days I now get an error: "assertion failed: key > self.key" immediately upon starting reth from the command line.

Steps to reproduce
Steps to reproduce:

cargo install --locked --path bin/reth --bin reth
RUST_LOG=info RUST_BACKTRACE=1 reth node --http.api all --ws.api all

Node logs
root@reth:~/reth# RUST_LOG=info RUST_BACKTRACE=1 reth node --http.api all --ws.api all
2023-07-22T15:33:22.139508Z  INFO reth::cli: reth 0.1.0-alpha.4 (0ef68b7d) starting
2023-07-22T15:33:22.139792Z  INFO reth::cli: Configuration loaded path="/root/.local/share/reth/mainnet/reth.toml"
2023-07-22T15:33:22.139809Z  INFO reth::cli: Opening database path="/root/.local/share/reth/mainnet/db"
2023-07-22T15:33:22.147788Z  INFO reth::cli: Database opened
2023-07-22T15:33:22.147842Z  INFO reth::cli: Pre-merge hard forks (block based):
- Frontier                         @0
- Homestead                        @1150000
- Dao                              @1920000
- Tangerine                        @2463000
- SpuriousDragon                   @2675000
- Byzantium                        @4370000
- Constantinople                   @7280000
- Petersburg                       @7280000
- Istanbul                         @9069000
- MuirGlacier                      @9200000
- Berlin                           @12244000
- London                           @12965000
- ArrowGlacier                     @13773000
- GrayGlacier                      @15050000
Merge hard forks:
- Paris                            @58750000000000000000000 (network is not known to be merged)

Post-merge hard forks (timestamp based):
- Shanghai                         @1681338455

2023-07-22T15:33:22.148109Z  INFO reth::cli: Transaction pool initialized
2023-07-22T15:33:22.148127Z  INFO reth::cli: Connecting to P2P network
2023-07-22T15:33:22.148220Z  INFO net::peers: Loading saved peers file=/root/.local/share/reth/mainnet/known-peers.json
2023-07-22T15:33:22.260003Z  INFO reth::cli: Connected to P2P network peer_id=0xca51…a516 local_addr=<IP_ADDRESS>:30303
2023-07-22T15:33:22.260149Z  WARN consensus::engine: Pipeline sync progress is inconsistent first_stage_checkpoint=17721430 inconsistent_stage_id=MerkleExecute inconsistent_stage_checkpoint=0
2023-07-22T15:33:22.260162Z  INFO reth::cli: Consensus engine initialized
2023-07-22T15:33:22.260169Z  INFO reth::cli: Engine API handler initialized
2023-07-22T15:33:22.260325Z  INFO reth::cli: RPC auth server started url=<IP_ADDRESS>:8551
2023-07-22T15:33:22.260340Z  INFO reth::cli: RPC IPC server started url=/tmp/reth.ipc
2023-07-22T15:33:22.260346Z  INFO reth::cli: Starting consensus engine
2023-07-22T15:33:22.260652Z  INFO reth::node::events: Executing stage pipeline_stages=1/13 stage=Headers from=17721430 checkpoint=100.0% eta=unknown
2023-07-22T15:33:22.260669Z  INFO reth::cli: Status connected_peers=0 stage=Headers checkpoint=100.0% eta=unknown
2023-07-22T15:33:22.260669Z  INFO execute{stage=Headers}: sync::stages::headers: Target block already reached checkpoint=100.0% target=Hash(0xda1578b300bd2b572e6d281fde6e81a41a774b7eb325a8ba6640166d8cd9600a)
2023-07-22T15:33:22.260702Z  INFO reth::node::events: Stage finished executing pipeline_stages=1/13 stage=Headers block=17721430 checkpoint=100.0% eta=unknown
2023-07-22T15:33:22.260739Z  INFO reth::node::events: Executing stage pipeline_stages=2/13 stage=TotalDifficulty from=17721430 checkpoint=100.0% eta=unknown
2023-07-22T15:33:22.260743Z  INFO reth::node::events: Stage finished executing pipeline_stages=2/13 stage=TotalDifficulty block=17721430 checkpoint=100.0% eta=unknown
2023-07-22T15:33:22.260767Z  INFO reth::node::events: Executing stage pipeline_stages=3/13 stage=Bodies from=17721430 checkpoint=100.0% eta=unknown
2023-07-22T15:33:22.260774Z  INFO reth::node::events: Stage finished executing pipeline_stages=3/13 stage=Bodies block=17721430 checkpoint=100.0% eta=unknown
2023-07-22T15:33:22.260799Z  INFO reth::node::events: Executing stage pipeline_stages=4/13 stage=SenderRecovery from=17721430 checkpoint=100.0% eta=unknown
2023-07-22T15:33:22.260803Z  INFO reth::node::events: Stage finished executing pipeline_stages=4/13 stage=SenderRecovery block=17721430 checkpoint=100.0% eta=unknown
2023-07-22T15:33:22.260821Z  INFO reth::node::events: Executing stage pipeline_stages=5/13 stage=Execution from=17721430 checkpoint=100.0% eta=unknown
2023-07-22T15:33:22.260893Z  INFO reth::node::events: Stage finished executing pipeline_stages=5/13 stage=Execution block=17721430 checkpoint=100.0% eta=unknown
2023-07-22T15:33:22.260908Z  INFO execute{stage=MerkleUnwind}: sync::stages::merkle::unwind: Stage is always skipped
2023-07-22T15:33:22.260917Z  INFO reth::node::events: Executing stage pipeline_stages=6/13 stage=MerkleUnwind from=17721430 checkpoint=17721430 eta=unknown
2023-07-22T15:33:22.260927Z  INFO reth::node::events: Stage finished executing pipeline_stages=6/13 stage=MerkleUnwind block=17721430 checkpoint=17721430 eta=unknown
2023-07-22T15:33:22.260955Z  INFO reth::node::events: Executing stage pipeline_stages=7/13 stage=AccountHashing from=17721430 checkpoint=100.0% eta=unknown
2023-07-22T15:33:22.260962Z  INFO reth::node::events: Stage finished executing pipeline_stages=7/13 stage=AccountHashing block=17721430 checkpoint=100.0% eta=unknown
2023-07-22T15:33:22.260978Z  INFO reth::node::events: Executing stage pipeline_stages=8/13 stage=StorageHashing from=17721430 checkpoint=100.0% eta=unknown
2023-07-22T15:33:22.260983Z  INFO reth::node::events: Stage finished executing pipeline_stages=8/13 stage=StorageHashing block=17721430 checkpoint=100.0% eta=unknown
2023-07-22T15:33:22.261004Z  INFO reth::node::events: Executing stage pipeline_stages=9/13 stage=MerkleExecute from=0 checkpoint=35.5% eta=unknown
thread 'tokio-runtime-worker' panicked at 'assertion failed: key > self.key', crates/primitives/src/trie/hash_builder/mod.rs:125:9
stack backtrace:
   0: rust_begin_unwind
             at /rustc/8ede3aae28fe6e4d52b38157d7bfe0d3bceef225/library/std/src/panicking.rs:593:5
   1: core::panicking::panic_fmt
             at /rustc/8ede3aae28fe6e4d52b38157d7bfe0d3bceef225/library/core/src/panicking.rs:67:14
   2: core::panicking::panic
             at /rustc/8ede3aae28fe6e4d52b38157d7bfe0d3bceef225/library/core/src/panicking.rs:117:5
   3: reth_primitives::trie::hash_builder::HashBuilder::add_leaf
   4: reth_trie::trie::StateRoot<TX,H>::calculate
   5: <reth_stages::stages::merkle::MerkleStage as reth_stages::stage::Stage<DB>>::execute::{{closure}}
   6: reth_stages::pipeline::Pipeline<DB>::execute_stage_to_completion::{{closure}}
   7: <tracing::instrument::Instrumented<T> as core::future::future::Future>::poll
   8: reth_stages::pipeline::Pipeline<DB>::run_loop::{{closure}}
   9: reth_stages::pipeline::Pipeline<DB>::run_as_fut::{{closure}}
  10: reth_beacon_consensus::engine::sync::EngineSyncController<DB,Client>::try_spawn_pipeline::{{closure}}
  11: <futures_util::future::future::map::Map<Fut,F> as core::future::future::Future>::poll
  12: <tracing_futures::Instrumented<T> as core::future::future::Future>::poll
  13: <futures_util::future::select::Select<A,B> as core::future::future::Future>::poll
  14: tokio::runtime::park::CachedParkThread::block_on
  15: tokio::runtime::handle::Handle::block_on
  16: <tokio::runtime::blocking::task::BlockingTask<T> as core::future::future::Future>::poll
  17: tokio::loom::std::unsafe_cell::UnsafeCell<T>::with_mut
  18: tokio::runtime::task::core::Core<T,S>::poll
  19: tokio::runtime::task::harness::Harness<T,S>::poll
  20: tokio::runtime::blocking::pool::Inner::run
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
2023-07-22T15:33:22.337775Z ERROR reth_tasks: Critical task `pipeline task` panicked: `assertion failed: key > self.key`
Error: Critical task `pipeline task` panicked: `assertion failed: key > self.key`

Location:
    /rustc/8ede3aae28fe6e4d52b38157d7bfe0d3bceef225/library/core/src/convert/mod.rs:717:9
root@reth:~/reth#

Platform(s)
Linux (x86)
What version/commit are you on?
0.1.0-alpha.4 (0ef68b7d)
What database version are you on?
Current database version: 1
Local database version: 1
If you've built Reth from source, provide the full command you used
No response
Code of Conduct

[X] I agree to follow the Code of Conduct

Could be related to https://github.com/tokio-rs/tokio/issues/3619

Facing the same issue.


feat(Algebra/Category/Ring/Constructions): categorical product of rings is the cartesian product

Can you add this to the module docstring?

Done.

maintainer merge

bors r-
Can you merge master and fix the build?
bors d+

bors r+


fix: access public runtime config warning

This fixes the following warning from nuxt
[nuxt] [runtimeConfig] You are trying to access a public runtime config value (google-adsense) directly from the top level. This currently works (for backward compatibility with Nuxt 2) but this compatibility layer will be removed in v3.5. Instead, you can update config['google-adsense'] to config.public['google-adsense'].

Fixes #173

upgrading to nuxt v3.5 seems to resolve this warning.


Fix: bad id type and attestation column

:tada: This PR is included in version 0.10.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


feat: use koanf instead of viper

I'm unsure about the PR idea.
I mean this PR seems to get out the blue.
What are you trying to solve ?
Why using koanf instead of viper on this project ?
what could it bring ?
Thanks
Please note I'm not suspicious or sarcastic, I'm simply clueless
I'm a random Gopher, following the project

@ccoVeille Thanks for you attention, I prefer to koanf with less dependencies and more stable interface for multiple/dynamic/remote config support.
And in the near future, kod just need rely on koanf's interface for configs, after supporting WithConfigProvider(p koanf.Provider :-)

FYI: https://github.com/knadh/koanf/wiki/Comparison-with-spf13-viper

Thanks

Did you try using @zxilly (hi 👋) tool on your code to see the difference of size?
https://github.com/Zxilly/go-size-analyzer


[wish] [snap] source pre downloading

This wish would enable snapcraft.io to build for us the snap package on architecture other than x86_64 (eg aarch64). I don't know how popular linux PC on arm will become in the near future, so it's not super high priority. Today we are limited to x86_64 since the github action runners are only on this arch (one can add a custom linux runner if he wants, but we don't have one).
The problem is that snapcraft remote build happens in a sadboxed environment which has no network access: all the sources need to be downloaded as a build dependency or as a source entry in the snap file.
The request is:

a mode where the scripts only download the sources (of opam files, but also opam installer), to be run locally before calling snapcraft remote-build --build-on=arm64
a mode were a local directory is used to "download" sources of things (both by the scripts and by opam), to be used by the scripts when run from the snap

I have no idea how feasilble this is. Maybe it's easier to buy an arm linux box and link it to github actions.

apparently opam 1.2 will have:

opam install now has a --download-only flag, allowing opam's caches to be primed

apparently opam 1.2 will have:

opam install now has a --download-only flag, allowing opam's caches to be primed

@gares : do you want to put yourself in as assignee for this?

I don't have time to implement it anytime soon :-/

Triage note: we already have difficulties to maintain the platforms we already have, so I am very reluctant to add new platforms without justification.
Another reason is that CI burns quite a bit of electricity for each platform we add.


Deleting OperationHandler for handling /operation endpoint on server

Part of https://github.com/GoogleCloudPlatform/kubernetes/issues/3644

Thanks.
I had been assuming that we would not break compatibility in v1beta1/2. However, if nobody is really using /operations, we could. Not sure how to figure that out -- I haven't found anything useful via web search. For now, we could start by making /operations registration optional, and disable it in v1beta3.
Also, we shouldn't return operations, either, then. Otherwise, users won't have any way to find out the statuses of their requests. This is probably the first thing we have to do. We need to deprecate the sync parameter and force all requests to be synchronous:
https://github.com/GoogleCloudPlatform/kubernetes/blob/24e59de06e4da61f5dafd4cd84c9340a2c0d112f/pkg/apiserver/resthandler.go#L152
Status would then only be returned for errors.
I assume Go's mux handles requests concurrently by default, so "long" running requests shouldn't block other requests.
Once we no longer need operations, then we can rip out the handler registration, and the actual operations code:
https://github.com/GoogleCloudPlatform/kubernetes/blob/24e59de06e4da61f5dafd4cd84c9340a2c0d112f/pkg/apiserver/resthandler.go#L311
https://github.com/GoogleCloudPlatform/kubernetes/blob/9b40c52c249fc6ed5e523af0442c25e2c0f02b0b/pkg/apiserver/operation.go#L97
The current operations behavior could be effectively be replaced by events: #3692.
Useful waiting behavior would be replaced by new "reification" events and/or watching status fields: #1899.
/cc @smarterclayton

We probably don't need to even leave backwards compat, because the only way you get an operation is to get one from a response.  The server already makes a decision whether to delay you for a real response, so every request has the potential to return a response immediately, so clients not handling that would be broken today.  We could leave the operation endpoints, but merely have them return empty.  Everything else can simply be ripped out wholesale (I think).
The muxes are concurrent.

On Jan 21, 2015, at 8:32 PM, Brian Grant<EMAIL_ADDRESS>wrote:
Thanks.
I had been assuming that we would not break compatibility in v1beta1/2. However, if nobody is really using /operations, we could. Not sure how to figure that out -- I haven't found anything useful via web search. For now, we could start by making /operations registration optional, and disable it in v1beta3.
Also, we shouldn't return operations, either, then. Otherwise, users won't have any way to find out the statuses of their requests. This is probably the first thing we have to do. We need to deprecate the sync parameter and force all requests to be synchronous:
https://github.com/GoogleCloudPlatform/kubernetes/blob/24e59de06e4da61f5dafd4cd84c9340a2c0d112f/pkg/apiserver/resthandler.go#L152
Status would then only be returned for errors.
I assume Go's mux handles requests concurrently by default, so "long" running requests shouldn't block other requests.
Once we no longer need operations, then we can rip out the handler registration, and the actual operations code:
https://github.com/GoogleCloudPlatform/kubernetes/blob/24e59de06e4da61f5dafd4cd84c9340a2c0d112f/pkg/apiserver/resthandler.go#L311
https://github.com/GoogleCloudPlatform/kubernetes/blob/9b40c52c249fc6ed5e523af0442c25e2c0f02b0b/pkg/apiserver/operation.go#L97
The current operations behavior could be effectively be replaced by events: #3692.
Useful waiting behavior would be replaced by new "reification" events and/or watching status fields: #1899.
/cc @smarterclayton
—
Reply to this email directly or view it on GitHub.

ok. Thanks for the detailed explanation.
I will send a different PR then, which first forces all requests to be synchronous so that we do not return operations to clients.
Once that is submitted, then we can come back to this PR to remove the handler registration.

I messed up in merging/rebasing.
This branch seems corrupted beyond repair. Will send this PR again.


Bug: Submitter getting stuck on Windows CMF

Expected Behaviour
When I hit submit, the submitter should create a job bundle and submit it.
Current Behaviour
After Effects freezes and a command prompt pops up. The command prompt is outputting to a log file. Here is a screenshot of the log file and the command prompt. It looks like it's stuck on a prompt

I'm attaching a screenshot of my deadline config:

Note that there is no storage profile selected. I've never had to make a storage profile for my other renders, but that seems to be what caused the prompt to appear.
Reproduction Steps
Spin up new Windows Server 2019 EC2 instance. Install python 3.11, the aws cli, Deadline Cloud Monitor, and the latest After Effects. pip install deadline and deadline-cloud-for-after-effects. Clone this repo and install the submitter according to the readme. Create a new project and try to submit.
Code Snippet
n/a

This is resolved in the newest version of the submitter that is coming out soon.


Update documentation/usage for genomeID in mega script

Users can send in chrom.sizes as genomeID in mega script if they also send in site file and ligation junction; make this clear in usage (ideally add documentation as well on github)

Done, though still need to update wiki documentation


Update mac os requirements

Add homebrew ruby formulae to fix github-linguist install error
When running gem install github-linguist

5

Hmmmm, there shouldn't be any need to install ruby from brew as it's already installed on macOS. What's the error this is fixing?

Closing as we can't really fix an issue properly without the actual error message. @tattali Don't hesitate to open an issue with details if you ever get that error again.


Fix for nvm_ls current always returning "N/A"

since the VERSION var wasn't used anywhere (it's called VERSIONS) and it's easier to just echo...

Woops! Sorry I didn't see there was already a PR for this...closing!


New style vstack

New style vstack to support double backprop.

Rebased on top of master.

@takagi san, thank you for the review! I made some changes to the code according to your feedback.


Port to Godot 4.3

Significant changes:

Update .gitignore to match https://github.com/github/gitignore/blob/6eeebe6f49678aacd8311ce079842c971b3ebe96/Godot.gitignore
Replace onready with @onready
Replace File class with FileAccess equivalent
Renamed some functions, properties and class names to their Godot 4 counterparts (e.g. get_ok() to get_ok_button(), Sprite to Sprite2D)
Disabled unnecessary update() calls (I don't think these are necessary anymore, but I might be wrong.)

Great work, thanks! I know the codebase is a little bit messy, and there are a lot of features need to be added, but I don't have enough time to work on those. I am planning to work on those when I get a chance.

Thank you for merging! Take as much time as you need, there's no rush.
If it's alright with you, I might take a look into making some further changes myself, in the meantime. My first idea is to restructure the user_interface.tscn scene slightly, using nested BoxContainers with different separations instead of the "HorizontalMargin" and "VerticalMargin" separators. I may also replace the long $Path/To/Node node paths with scene-unique names, i.e. %Node. Would it be alright for me to implement those changes?

Of course. Go for it. I will try to make file exporters abstract as much as possible when I get time.


Add support for optional source_uri field

A tag has a source (e.g.., GraphSense Public TagPack) and an optional source_uri (e.g., the tagpack URI)

Good point. Let's discuss next week: we need to cover the following cases:
1.) tag is retrieved from some Web source:
source: https://archive.org/donate/cryptocurrency/
2.) tag is retrieved from 3rd party data source and the data source wants to provide a back-link
source: https://sometool.com/btc/some_address
3.) tag is retrieved from 3rd party data source; no backlink provided
source: some data source (no URI)
We could, of course, leave things as they are and display the tagpack title an creator instead. Let's discuss this in our next call.

this is obsolete now

Updated documentation acordingly:
https://github.com/graphsense/graphsense-tagpack-tool/blob/master/README_tagpacks.md#tagpack-properties

Has been clarified in https://github.com/graphsense/graphsense-dashboard/issues/279


Database impersonation in ODBC for postgres based connectors

Hello,
A few questions after reading about database impersonation here:
https://tableau.github.io/connector-plugin-sdk/docs/auth-modes
The documentation states "This applies to databases that support a user(authenticated_user) that can delegate requests to another user(delegated_user) by enabling the client to pass a DelegationUID(delegated_user) to the database server"
What method is used at the database level?  In postgres for instance this would done with "set role".
(https://www.postgresql.org/docs/current/sql-set-role.html)
To clarify, in this scenario a workbook would be published with stored credentials and authenticated to the database with those same credentials.  When a user accesses the workbook the user's username (odbc/jdbc username) is passed as the delegated_user and runs a "set role <delegated_user>."
Are these assumptions correct for how database impersonation works with a database like postgres?
thanks,
-Christian

I think your understanding is correct about how database impersonation works. The exact JDBC driver property for passing DelegationUID could be different for different databases. This property will have to be specified in the connector plugin properties file. I am sorry that the example link is broken in the auth-modes wiki page. I will fix it.

Hi Christian
Here’s where we mention JDBC only for new connectors in the Tableau Exchange.

Note: The Tableau Exchange no longer accepts submissions of ODBC connectors. Only JDBC connectors are accepted.

https://tableau.github.io/connector-plugin-sdk/docs/gallery-submission
For Postgres JDBC I think passing user should work instead of DelegationUID, although I haven't tested it so can't say for sure.
 if (attr[connectionHelper.attributeTableauServerAuthMode] == connectionHelper.valueAuthModeDBImpersonate) {
        var str = attr[connectionHelper.attributeTableauServerUser];

        if (!isEmpty(str)){
            props["user"] = str;
        }

}

Ok thanks for the confirmation.


OpenALPR Local: TypeError: 'Event' object is not callable

Home Assistant release with the issue:

0.85.0
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):

Docker version 18.09.0, build 4d60db4 on Debian GNU/Linux 9.6 (stretch) with 4.9.0-8-amd64
Component/platform:

https://www.home-assistant.io/components/image_processing.openalpr_local/
Description of problem:
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
image_processing:
 - platform: openalpr_local
   region: eu
   source:
    - entity_id: camera.hof

Traceback (if applicable):
Exception ignored in: <module 'threading' from '/usr/local/lib/python3.6/threading.py'>
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/threading.py", line 1352, in _after_fork
    thread._stop()
TypeError: 'Event' object is not callable

Additional information:

Are you still having this issue? If so, have you tried updating to the latest version of home assistant 0.90? Thanks

@webdjoe yes, absolutely. HA v0.93.2
2019-06-01 16:36:15 INFO (SyncWorker_6) [homeassistant.loader] Loaded openuv from homeassistant.components.openuv
Exception ignored in: <function _after_fork at 0x7f937065dae8>
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/threading.py", line 1338, in _after_fork
    thread._stop()
TypeError: 'Event' object is not callable

And then every few seconds:
Exception ignored in: <function _after_fork at 0x7f937065dae8>
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/threading.py", line 1338, in _after_fork
    thread._stop()
TypeError: 'Event' object is not callable

Nope, still does not work.


Add synthetic datasets fix

This fixes #5314 and #5315  that was reverted by #6288 by re-introducing a fix by @comicchang in  #6283 . Fix #6283 was not merged as it was submitted after #6288 reverted it.
The error was that import tensorflow as tf is not allowed (sorry didn't know that).
I think I checked everything, lgtm
@ilblackdragon @caisq @martinwicke

Can one of the admins verify this patch?

@comicchang Could you sign the CLA? I didn't rewrite my commit to add your changes, I added your changes directly. As you are a contributor, you need to sign it :)

My bad @comicchang, it doesn't need CLA, it says you need confirm here that you are OK with this PR

😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that they're okay with their commits being contributed to this project. Please have them confirm that here in the pull request.

@zafartahirov I've already sighed the CLA
I'm ok with this PR
But...didn't my PR/commits already merged to the master?

@comicchang No it didn't, it was revoked before the merge was complete

@zafartahirov
I'm confused, but l'm sure the PR was already merged.
https://github.com/tensorflow/tensorflow/tree/master/tensorflow/contrib/learn/python/learn/datasets
https://github.com/tensorflow/tensorflow/commit/81eae9ac713e02b6d36785de8b7f29258601592b

That's odd, when I was reading the #6288 it was saying that it got cancelled -- my bad, will close it now

I know what happened - You are right, I checked it now - I was reading an old thread from #6283 before you reverted the changes - disadvantage of keeping open tabs as my "todo-list", my bad :)

That's ok.
Have a good day :)
Zafar Takhirov<EMAIL_ADDRESS>周三下午2:17写道：

I know what happened - You are right, I checked it now - I was reading an
old thread from #6283 https://github.com/tensorflow/tensorflow/pull/6283
before you reverted the changes - disadvantage of keeping open tabs as my
"todo-list", my bad :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/pull/6433#issuecomment-268445225,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABMu0WXuZQEm3bX3rtAnuQjio7nJ18VNks5rKMRcgaJpZM4LSmeY
.


WIP - scoped store after .reset()

THIS IS WORK IN PROGRESS
closes #149

closing in favor of #153


Add ability to rename a workflow when importing from dockstore [SATURN-1145]

Steps to test/reproduce:
From the homepage go to browse data. From there choose the code & workflows tab and from there choose to import from dockstore. Once you've chosen a wdl from dockstore select to import to Terra and once you are redirected be sure to change back from dev to localhost.
Tested by:

importing a variety of dockstore workflows and renaming them
attempting to rename workflows to names that were already in use
attempting to rename workflows invalid names
importing dockstore workflows and not renaming them
importing dockstore workflows to brand new workspaces
imported workflows on both Anvil and Datastage

First testing observation: The import button is not disabled if the workflow name is invalid because it contains a space. However, the import worked! If I try to duplicate it or copy it to another workspace, those buttons are disabled due to the space in the name.
I think it's entirely possible that we added this protection because of problems down the line (maybe when actually running the workflow). We should disable the import button if the name is invalid.


Executing arbitrary logic when a feature flag status gets retrieved from storage

I checked Bugsnag's new feature, where we can now include the enabled feature flags to be part of the error reports.
They updated their Ruby SDK to allow developers to include feature flags as part of the error reports like so:
Bugsnag.add_feature_flag('New checkout flow')

On my team, we disabled Flipper's preload due to performance implications, so we would like to call Bugsnag.add_feature_flag every time we interact with Flipper to retrieve the status of a particular feature flag. Can I do that already?
One way to achieve this would be to make the Feature class observable and register observers in the library like the example below:
class FeatureCheckObserverForBugsnag < Flipper::FeatureCheckObserver
  def call(feature, enabled)
    if enabled
      Bugsnag.add_feature_flag(feature.name)
    else
      Bugsnag.clear_feature_flag(feature.name)
    end
  end
end

Flipper.add_feature_check_observer(FeatureCheckObserverForBugsnag.new)

# Flipper will now include the new observer on every new instance of Feature that it instantiates

Let me know if there is already an approach to get the outcome I'm looking for and if you have any comments about my proposal. I will happily implement it if you think it is worth it.
Cheers!

@nicolasiensen This should be possible with Flipper's existing support for Instrumentation (assuming you're using Rails, it everything will already be configured for you). I'll update the docs based on this discussion because that link doesn't show you how to do custom stuff, but try adding this to an initializer in your app:
ActiveSupport::Notifications.subscribe('feature_operation.flipper') do |name, start, finish, id, payload|
  if payload[:operation] == :enabled?
    puts "#{payload[:feature_name]} enabled? #{payload[:result]}"
  end
end

Now when I run this code…
Flipper.enabled? :instrument
Flipper.enable :instrument
Flipper.enabled? :instrument

…I see this:
my_feature enabled? false
my_feature enabled? true

Other operations besides :enabled? are :enable, :disable, :add, :remove, :exist?, and :clear.
Let me know if this doesn't solve your problem and I'll reopen the issue.


Binding retries in stateless brokers

According to OSB Bindings spec:

200 OK: MUST be returned if the binding already exists and the requested parameters are identical to the existing binding. The expected response body is below.

How can this requirement be achieved in stateless brokers (see https://github.com/openservicebrokerapi/servicebroker/issues/203 and https://github.com/openservicebrokerapi/servicebroker/issues/225#issuecomment-311230413)? This requirement implicitly stands that:

Broker stores the request payload for each binding somewhere (i.e. broker is stateful).
Broker is able to re-retrieve the credentials for existing Binding (despite that there is no GET endpoint).

I'm pretty sure that existing stateless brokers don't respect this requirement, otherwise they are stateful 😕
Shall we remove this requirement from the spec?

This seems to be a subset of #225

@arschles it's related, but not a subset.
The question for this issue is whether this requirement is always respected in the current world of brokers. If not, we should remove it from the spec.
Also see related issue in Service Catalog: #1062
If this requirement is respected, there is no need for preventing duplicate requests from the Service Catalog side.

related #291
proposal: https://github.com/openservicebrokerapi/servicebroker/issues/291#issuecomment-323344056

I'm not sure what a good solution to this issue is. I understand the reasoning behind a stateless broker not being able to respond with a 200 OK here as it can't remember what parameters were used originally, but those brokers could always just respond with a 409 Conflict:

409 Conflict: MUST be returned if a Service Binding with the same id, for the same Service Instance, already exists or is being created but with different parameters.

What do you think @fmui ?

Looks like we solved that already by accident. See #528

You're right, that does technically solve this, but I still think that the spec doesn't offer much guidance as to what service brokers should do if they don't have state and they can't determine if the configuration parameters were the same as before. Should they return a 200 or 409 in that case?

Is this a problem for anyone, or can we close this for now and wait until it becomes a problem?

Closing due to inactivity. Please reopen if this becomes a problem for anyone.


Application in list taking too much space

When an application description is too big it increases the height of its container, breaking the application grid.

Can reproduce in Firefox 113 and GNOME Web 44.2.

Seems like the line clamping here isn't working anymore https://github.com/flathub/website/blob/main/frontend/src/components/application/ApplicationCard.tsx#L64-L65


Implement reference object generator as replacement to DOM node

It would be nice if a function could be passed instead of an html element for reference at init.  The function would return a bounding box that could be used for positioning.
The function is necessary --- rather than just a plain object --- to allow for cases where the bounding box would change over time.  This would allow updates with popper.update().
Having this feature would make support for libs like Cytoscape much better.
Thanks for your consideration.

That's something I'd like to add but I haven't time at the moment. There's some work needed to make this idea work.

More context on the feature's requirements.
It should provide all the informations needed by Popper.js to be able to compute the position of the popper, for instance:

Context of the fake element (where "is" it located in the DOM?) to make it possible to properly position the popper;
All its sizes (everything outputted by getBoundingClientRect())
Popper.js must be changed to properly handle a function instead of an element.

@FezVrasta Would it be possible to pass in a DOM-like object (or have the function return such an object)?  For example:
let makeFakeDiv () => {
  return {
    getBoundingClientRect: function(){ /* ... */ },
    parentElement: document.body
  };
};

let popper1 = new Popper( makeFakeDiv() );

// or

let popper2 = new Popper( makeFakeDiv );

This would probably not require as invasive changes, but the list of fields expected for the fake DOM object would have to be documented.  Even popper1 can still be dynamic by changing what getBoundingClientRect() returns, so it would suffice for the Cytoscape.js usecase.

As long your custom object "looks" like a DOM node I think Popper.js shouldn't complain about it.

+1 for this. IMO the "DOM-like" object would be best. After some digging, it looks like the following interface would be needed:
getBoundingClientRect() : DOMRect
clientWidth : Integer
clientHeight : Integer
offsetParent : HTMLElement? = window.document.documentElement

Is there anything I'm missing? Obviously DOMRect you'd just need the interface, as constructing a literal DOMRect isn't supported in most browsers and isn't needed I assume, just so long as it has the same properties.

I guess something needs to change in Popper.js to tell it to call the "DOM-like-object-factory-function-wahtever" and update clientWidth, clientHeight and offsetParent if you don't want to use getters

I'd be pro getters and no factory function - it would mean this would be a smaller PR, without closing the door on a function in future?
But if not, what about an onBeforeUpdate callback? People could hook into that and update their "DOM-like" object's props? Though I guess that essentially comes to the same thing as getters anyway.

Do you need a PR if you use getters? 🤔
I'm not against them, I'm not updated about the browser support and I think that a change like this would be quite minimal:
if(typeof reference === 'function') reference = reference() // I mean, with an actual type checking that works, lol

Ok, updated my informations:

Hahaha - well down to IE9 is enough for popper yeah?
Ah yeah, can start using it straight away 😉 I guess just documenting that it reference needs to match this interface, rather than an HTMLElement?
Well, I know my use case would be covered purely by getters, but @maxkfranz does it cover your needs?

Please do let me know if it works for you and share some working code if you can.

Will do - I'll try get something together in the next few days

I put together this:
http://codepen.io/FezVrasta/pen/evoMrR?editors=1010
I'm not sure if everything works, we should add a set of tests to make sure everything works properly.

+1 for tests. I created a fork of that codepen and it looks to be playing pretty nicely with a range - which is my use case, essentially having a toolbar object hover over text selection.

Damn that's really cool! Great work

I referenced #9 because seems like a natural step to support @bedeoverend use case.
I'm not sure how to proceed with it, basically we need to support a "non rectangular" reference element/area...

@FezVrasta I tried to implement #9 earlier but when I dug into the code a little bit I feel uncertain about how should that fit into current calculations.

As long as some kind of dom-like object is officially supported/documented as reference, that works for me.

@FezVrasta Perfect, thanks.  I agree that the generator is just a nice-to-have.

Awesome! Thanks @FezVrasta.
Personally, I'd prefer if it were documented that reference just had to match a certain interface i.e. be an object which has getBoundingClientRect() function and clientWidth / clientHeight properties (and maybe offsetParent). That way I'm not limited to just using HTMLElement or the new Reference class. But I'm not sure if that's shared by anyone or just me. I also understand that that could be annoying as it means you have to have backwards compatibility for it going forward.

actually I'd like to avoid to add more code to the library since it's growing too much for my tastes in the past months.. Maybe I could simply document as you suggested and put the sample ReferenceClass in the docs folder (or a gist link) for reference?

Yeah I think that sounds good. A gist or a guide on how to use it would be good 👍

I agree it's better / more flexible to just have documentation.

Looks like the recent changes introduced in 1.5.1 broken the possibility to use an object as reference element.
We should update the code to fix it.


signup page with email verification

Created a signup page with Email verification. Passwords are hashed before storing them to the database. I have kept the UI same as the General Diary page has. For sending OTP to email I used nodemailer.
Before reviewing edit the environment variables. Edit NODEMAILER_SENDER_ID with the Gmail id from which you want to send OTP mail and NODEMAILER_SENDER_ID_PASSWORD with the password of your Gmail account. Also, edit the google account settings. Go to your Google account > search for less secure apps> enable it.

@anugoyal998 Good Work!🎉


Using own maps

Hello there,
Are you able to use your own maps with the Web Map Service? It are PNG files.

Please ask questions on stack overflow with the openlayers-3 tag

Creating the new tag 'openlayer' requires at least 1500 reputation. Try something from the existing tags list instead.

I don't have 1500 repuation so I'm not allowed.

openlayers-3 tag not openlayer


Release of new Version

Updates of npm dependiencies
Refactoring of ETL and ETL-Documentation
open github link in new tab
Fixed typos in ETL documentation
Fixed typo on imprint page

Typos have been fixed by https://github.com/hochschule-darmstadt/einander-helfen/pull/158/commits/a59e8df682cbc37395ff67abfb7d281fb7a7f04f :D


Solidity version fetching

Add ability to fetch solidity versions from source code and pass it to hardhat

Hi @varex83, can I work on this?


%husktowns_current_location_plot_members% fails to return correct plot member list and can throw exceptions

We also encountered errors when using the %husktowns_current_location_plot_members% placeholder, and PAPI testing also resulted in errors.
Reproduction method: when the plot is not specified.
When using the %husktowns_current_location_plot_members% placeholder, the returned result is incorrect (returns "Not a plot"), and PAPI testing also returns "Not a plot". However, the %husktowns_current_location_claim_type% placeholder returns normally (returns "plot").
Reproduction method: when the plot is specified, regardless of whether the plot members and administrators are set, the result is always "Not a plot".

I've split this issue up into two issues; #371 & #372


Reports: Link the report type in the header to its definition on About

We're open to ideas to how to approach this (e.g., a direct link on the report type label, or hyperlinked text "What are XXX reports?", etc) but the general idea is to have the Report Type label in the header on board report pages (screenshot 1) hyperlink to the anchor of the type definition on the About Us page (screenshot 2).

Links to:

The report type on the About Us page is hyperlinked to search for that report type ... Adding the link from the report to definition of type on About would be a nice loop.

@hancush It seems like a good way to get this done is to amend partials/component_bill_type_table.html to include IDs for each paragraph element over in django-councilmatic. Then we could add an html_id entry to each bill type in councilmatic/settings_jurisdiction.py in this repo that we'll use to generate a link in the bill type label on the detail pages.
How does that approach sound to you?

Overall, sounds like a good approach, @antidipyramid! Since this is Metro customization, what do you think about overriding the bill type table partial in this repo to add the ID, instead of making the change upstream?

@hancush Oh that's a much better idea, thanks. I forgot that you could override templates!

@shrayshray We added report type alphabetization and report type links to the staging site. How does it look?

@antidipyramid looks great!


[BUG]: Missing  {card: { network: string[]; }; } is not assignable to type DefaultValuesOption

What happened?
Version: @stripe/stripe-js 4.1.0
Others: @stripe/react-stripe-js 2.7.3
We are urged to implement a card-selector for the dual cartes_bancaires - visa/mastercard option in France.
I am following the docs to do so but am running into a typing error when trying to set the default value for one of these cards in the options for the stripe payment element.
Related documentation:
https://docs.stripe.com/js/elements_object/create_payment_element#payment_element_create-options-defaultValues-card
Environment
No response
Reproduction
No response
### Tasks
- [ ] https://github.com/stripe/stripe-js/pull/628

Hey there -- looking to get this corrected, but in the interim please use ts-ignore.

@Smoggert thanks for the report, this has been updated in 4.4.0.


Update README.md

Fixing incorrect documentation link.

Got my projects mixed when I wrote the earlier draft of the documentation. The wrong link is for the Specter docs!

Got it, TY!


Consider changing the data shape of Lua.diagnostics.globals setting

The language server requires the Lua.diagnostics.globals setting to be an array of strings, while luacheck allows for a more precise configuration of existing globals — https://luacheck.readthedocs.io/en/stable/config.html#custom-sets-of-globals.
If we also allow globals-as-nested-tables configuration, we can improve the accuracy of lining, but we need to make sure it won't break other uses of this setting.

Alternatively, we could use a new setting key for luacheck globals.


Add Javadoc for JavaHamcrest <IP_ADDRESS> to hamcrest.org. Closes #117

Fixed to correct version <IP_ADDRESS> instead of 2.0.0

Hi! Could somebody pull this? It's would only take a moment, and save some people a lot of time!


Error when subsetting with selected rows and cols

Hi, thank you for developing this wonderful tool. I have encountered an error when trying to dot plot selected rows and cols using the following script.
cellphonedb plot dot_plot --rows in/rows.txt --columns in/columns.txt
It showed Error: Invalid value for '--rows': File 'in/rows.txt' does not exist. It seems rows.txt and columns.txt files are not in the correct directory. I am wondering where these two files should be placed.
Thank you,

Hi @garfieldyc, thank you for using CellPhoneDB.
Can tou confirm if rows.txt and columns.txt are actually inside the in folder you mention?
If you've cloned the repository and you're trying to run the examples keep in mind that the paths for those is
in/example_data/ from the base path CellphoneDB where the repository was cloned.

Hi @garfieldyc, thank you for using CellPhoneDB.
Can tou confirm if rows.txt and columns.txt are actually inside the in folder you mention?
If you've cloned the repository and you're trying to run the examples keep in mind that the paths for those is in/example_data/ from the base path CellphoneDB where the repository was cloned.

Thank you for your reply. It works now.


Memory allocations and stuff

I have been making some measurements about memory usage/allocation rate with dyn4j. I know dyn4j does not go to great lengths in order to reduce allocations and such (and the resulting cleaner code is appreciated).
I found some small bits of code though where writing more memory allocation sensitive code can bring big ‘savings’.
In my experiment (numbers are approximations from what I remember, but make the point):
2000 rectangle random-ish scene
500 frame simulation
Current version: ~120-130 million Vector2 allocations
Version 1 (only rewrite of parts in Sequencial impulses algorithms): ~ 40-45 million allocations
Version 2 (version 1 + some more small scope changes in other places): ~20 million allocations
This is from a draft experimental implementation, but the reasoning was to change only a few but critical parts.
I think v1 could be a good candidate to actually implement. The changes are small and limited to one class yet the gains are quite good. v2 needs some discussion whether it is worth it for the extra bits.
 But on the other hand reducing the strain ‘for free’ should not be bad either. Also will probably help for lower end computers/mobiles.
@wnbittle I would make a pull request, but didn’t knew how much memory sensitive code is ok (if at all)

Less object allocations are great.  What I try to do is weight the readability change vs. the improvement.  In my experience object allocation on modern VMs is ridiculously good, but on Android its lackluster at best.
I know that I don't want object pooling or array management.  Inlining is fine as long as the more readable code is available via comments.  Stuff like v1.product(v2).sum(v3).difference(v4) to v5.x = (v1.x * v2.x) + v3.x - v4.x would be fine.
Maybe if you gave a few examples of what you had in mind and I could speak to each?

Agreed, no object pooling (if you mean making x objects in some array and then reusing them) or strange array hacks in general, since those are ugly and error prone.
Most of what I did is

Inlining as you mentioned
Moving object allocations outside of 'hot' loops
Re-arrange code

Here are some examples:

Inline to eliminate vector allocations:

Vector2 p1 = c1.sum(r1);
Vector2 p2 = c2.sum(r2);
Vector2 dp = p1.subtract(p2);
double penetration = dp.dot(N) - contact.depth;

The above can become
double dpx = (c1.x + r1.x) - (c2.x + r2.x);
double dpy = (c1.y + r1.y) - (c2.y + r2.y);
double dpDotN = dpx * N.x + dpy * N.y;
double penetration = dpDotN - contact.depth;

Use alternative method calls to move allocations outside (nested) loops:

for (int i = 0; i < size; i++) {
    ...
    Vector2 c1 = t1.getTransformed(m1.getCenter());
    Vector2 c2 = t2.getTransformed(m2.getCenter());

The above can become
Vector2 c1 = new Vector2();
Vector2 c2 = new Vector2();
for (int i = 0; i < size; i++) {
    ...
    t1.getTransformed(m1.getCenter(), c1);
    t2.getTransformed(m2.getCenter(), c2);

Reuse vectors that are declared outside (nested) loops

for (int k = 0; k < cSize; k++) {
    ...
    Vector2 J = N.product(jp);

The above can become
for (int k = 0; k < cSize; k++) {
    ...
    J.set(N).multiply(jp);

Perform multiple computations with one object where 'convinient':

public Vector2 getFarthestPoint(Vector2 vector, Transform transform) {
    Vector2 localn = transform.getInverseTransformedR(vector);
    int index = getFarthestVertexIndex(localn);
    return transform.getTransformed(this.vertices[index]);
}

The above can become
public Vector2 getFarthestPoint(Vector2 vector, Transform transform) {
    Vector2 localn = transform.getInverseTransformedR(vector);
    int index = getFarthestVertexIndex(localn);
    transform.getTransformed(this.vertices[index], localn);
    return localn;
}

Use local variable as internal allocated memory:

private double getRelativeVelocityAlongNormal(ContactConstraint contactConstraint, Contact contact) {
    Vector2 rv = this.getRelativeVelocity(contactConstraint, contact);
    return contactConstraint.normal.dot(rv);
}

The above can become
private final Vector2 buffer = new Vector2();
private double getRelativeVelocityAlongNormal(ContactConstraint contactConstraint, Contact contact) {
    this.getRelativeVelocity(contactConstraint, contact, buffer);
    return contactConstraint.normal.dot(buffer);
}

Those are probably all the 'patterns' I applied and got to reduce the total Vector2 allocations as the issue says. In my opinion:
1 is ok to use almost anywhere with the appropriate comments
2-3 are ok to use but only on limited places where a lot of allocations are eliminated and it's worth it
4 is not really great to do
5 is not really great to do but in specific circumstances can be profitable
So with those I experimented to make
Version 1 = use 1, 2, 3 & 5 without contraints but only within a single class (SequencialImpulses)
Version 2 = v1 + limited use of all in other 'hot' classes/methods

I would consider 1-3 acceptable with original code commented out (or sufficient English comments) but only where there's a significant benefit.  4-5 I wouldn't want at all - too risky.  Speaking for myself here, I would most certainly introduce a bug this way.
I feel like we're nearly in alignment.  I would suggest we start at SequentialImpulses for example and see what 1-3 does for us.

Ok I'll follow up here with some sample implementations using patterns 1-3.

In the old forum (a long time ago) these exact changes were discussed but it was hard to keep track and it died.
To share some insights from way back:
On Desktop Java these "allocation saving improvements" have nearly no measurable effect on performance. The JVM is amazingly fast in that regard.
Android (Lollipop and onwards) behaves similar, performance impact of object creation are minor. The main problem is the Garbage Collector. If the GC can't keep up with the temporary objects created, memory will steadily rise until the JVM has to allocate more system memory. Which Android tries to prevent first, by an in-depth garbage collection, causing the application to pause for a noticable amount of time every few seconds.
What I am trying to say: One can gain performance by reducing object allocations below the memory churn rate of the device. After that, the impacts are minor. Newer Android versions improve steadily towards Desktop Java performance, just a matter of time.
It would be best to concentrate on easy hotspots first, test them against a specific target device and see if this solves the problem, already.

Yeah this is pretty much it. I think I actually remember seeing the discussion in the forum back in the day as well :)
I can confirm that on desktop allocations are close to free. What is good is that the majority of all allocations happen in the SequencialImpulses class so we can optimize a bit there and the total number of allocations becomes much smaller 'for free' (this is the definite hotspot for allocations).
I have no devices to test on unfortunately, but as long as the changes do not decrease code quality and are contained in a small set of classes I don't see much potential issues with it.

I can test the code changes against different devices. I just need to know for which device and Android version.
However, I don't have a dyn4j benchmark or anything like that. If someone accidentially happens to have one...

@mtsamis No pressure at all, just wondering if you had more changes coming with this one and if so, did you want to target 3.4.0 or 3.4.1 (so i can mark it appropriately).  With the holidays coming I'll have a little more time and would like to release 3.4.0 sometime in the next week or two.

Sounds good to make the 3.4.0 release in the holidays!
Let's leave this one for 3.4.1; I have most of those already implemented somewhere but I'll have to clean up, document, organize it etc. It's not that important change anyway.

@mtsamis  With 4.x out now are there additional changes that you are planning to implement?  Either way it would probably make sense to close this issue.


Lines with links do not render with proper styling

Issue
When a line that starts with an achor link is bolded, the entire line gets bolded.
Reproducing the issue:
Case: Only the link is bolded(NOTE: ensure 'Lorem Ipsum' is an anchor link)
Copy: Lorem ipsum - dolor sit amet, consectetur adipiscing elit
Precondition: Bold only the Lorem ipsum part
Result: The entire line is bolded
Result HTML:

      Lorem ipsum
     - dolor sit amet, consectetur adipiscing elit

Expected result: Only Lorem ipsum is bolded
Expected HTML:

    Lorem ipsum
   - dolor sit amet, consectetur adipiscing elit

Current workarounds
Workaround 1: Inserting an invisible character at the start of the line extra line(ie. a space) causes the issue to semi-resolve itself
Copy: [INVISIBLE_CHARACTER]Lorem Ipsum - dolor sit amet, consectetur adipiscing elit
Result: Only the Lorem Ipsum is bolded
Result HTML:

    Lorem ipsum
   - dolor sit amet, consectetur adipiscing elit

Workaround 2: Italicizing the bolded link causes the link to be bolded and italicized and the rest of the line appear correct
Copy: Lorem Ipsum - dolor sit amet, consectetur adipiscing elit
Result: Only the Lorem Ipsum is bolded and italicized
Result HTML:

    Lorem ipsum
   - dolor sit amet, consectetur adipiscing elit

Hey @joerodrig thanks for reporting the issue.

I will look into it and get back to you if I need more details.
Cheers


4th 3D Axis (trackball rotation) on rotation tool

The current gizmo is currently missing a trackball rotation axis making fast random rotation impossible. This would be especially convenient for placing rocks and foliage in different random orientations FAST.

Would be a case of adding an "outer" ring to the rotation gizmo that has an orientation that matches the camera.


Fortnite Free Codes (June 2024): How to Redeem Codes for Free? Get V-Bucks In Fortnite

Epic Games Fortnite is an enhanced version of the popular Battle Royal Fortnite. A standout feature of Epic Games Fortnite is its daily redemption codes, which add excitement and urgency to the player experience.
This article has got you all covered! Fortnite V-Bucks Gift Card Codes V-Bucks Claim your V Bucks Package by filling out the form below: Please note Fortnite V-Bucks Claim your V Bucks Package by filling out the form below: Please note that you can only use this generator once every 15 minutes so that Epic Games doesn't get suspicious. V-bucks code daily update!
✅👉CLICK HERE TO CLAIM CODES 👈✅
Post Update: Daily in June 2024
Regularly, Epic Games joins forces with prominent celebrities, brands, and unexpected personalities to introduce fresh content to Fortnite. Acquiring these items can be costly and challenging. Fortunately, Epic Games has integrated a code system into the game that allows players to claim complimentary in-game rewards such as V-Bucks and cosmetics. Fortnite is still one of my favorite battle royale experiences because it’s addictive and fun to play with friends. A myriad of challenges, items to complete, and exciting rotating events prove that the game won its popularity for a reason.
Look no further! This article lays out everything you need to know about Fortnite codes, including the currently active ones for June 2024, how to redeem them, and some insider tips for grabbing those elusive rewards.
All ways to get free V-Bucks in Fortnite
Daily Quests. Daily Quests provides you with around 50 V-Bucks every day.
Login Rewards. Daily Login Rewards include V-Bucks on certain days and the amounts are huge.
Timed Missions. You may find Timed Missions with 25-40 V-Buck rewards.
Main Questline.
Side Quests.
Events.


Release v1.2.1 does not publish windows installer package

Previous release v1.2.0 has 18 assets, one of which is an msi package, while v1.2.1 only has 10 assets. The only package available for Windows is a zip file.

@stuartpa had you been uploading the MSIs manually?

v1.2.1 has been pushed to all package managers, Winget usually takes 24/48 hours to get through moderation (this PR will be merged automatically when moderation is complete):
https://github.com/microsoft/winget-pkgs/pull/112781

Winget PR is merged, 1.2.1 is available in winget.


Camera usage ?

I created a graph with nodes having fixed positions (ie : {id: 'node1', label: 'Node 1', x: 12, y: 34}).
My nodes and edges are declared in two separate arrays.
const network = new Sigma()

network.addRenderer({
    container: document.getElementById('container'),
    type: 'webgl',
})

network.settings({
    minArrowSize: 100,
    labelThreshold: 1,
    zoomMin: 0.1,
    zoomMax: 10,
    defaultNodeColor: '#00f',
    sideMargin: 3,
})

nodes.forEach(node => {
    node.size = 1
    network.graph.addNode(node)
})

edges.forEach(edge => {
     network.graph.addEdge(edge)
})

network.refresh()

Now, the network.refresh call centers my graph nicely in the container. But I want to trigger actions that would focus on specific nodes, and I struggle to understand how I'm supposed to do that.
I read the camera API documentation, and noticed the goTo, graphPosition and cameraPosition methods, but was unable to find my way with these.
What I tried:

logged network.cameras[0], and confirmed that its x and y coordinates (displaying 0, 0) were not related in any way to the coordinates of my nodes, which range from 0 to 30 (I have a node placed at coordinates 0,0, which is placed on the central vertical axis, somewhere between the center of the container and its top, so 0,0 from the node does not match 0,0 from the camera, be it the center of the camera or one of its corners). My conclusion was that I needed to use the graphPosition and cameraPosition methods to convert the coordinates between the node's and camera's.
network.cameras[0].goTo({x: node.x, y:node.y}), I noticed that the camera moved very slightly, but did not center on my node
const newCoords = network.cameras[0].cameraCoordinates(node.x, node.y), followed by network.cameras[0].goTo({x:newCoords.x, y: newCoords.y, ratio:1}). I noticed that the newCoords object had the exact same coordinates as the node's, and so the camera moved slightly as well, but not centered on my node (camera was placed at x:0,y:0, the node was placed at x:3,y:9, then camera position displayed x:3,y:9).
same as previous, but with a ratio of 0.5. I could only confirm that the zoom level increased, but the camera was still centered on the same spot.
disabled autoRescale (and augmented the distance between my nodes). The results looks way better when I network.cameras[0].goTo({x: node.x, y:node.y}) right after the first render. But if I drag the view and trigger it once again, the camera is applied the same vectorial movement from my current view. Which means the camera was probably not following the view being dragged.

So, my question is about clarifying the way I am supposed to interact with the camera API.
Where can I find examples for this usage, guidance, or any advice ?
I searched the issue tracker for examples of graphPosition and cameraPosition usage, but could not find relevant information.
How is the camera linked to the container? How can I make it follow the mouse dragging my network? And can I center it on multiple nodes at once ?
Precision : now that autoRescale is disabled, my full network is not centered beautifully on first render, and I don't know how to achieve this.

Hi @jb2b38 did you ever solve this? I have the same issue and also searched through other issues with no luck and facing the same problems you have described here.

Same here

Hi,
This is a working example : https://plnkr.co/plunk/tmGBNZSQ88LpGeoF
If you click on a node, the camera go to the node's position.
What you missed is that sigma create its own graph structure (see sigma.graph).
So in this example, I search a node into the sigma graph structure bu the node's id :
s.graph.nodes().find(function (node) {
   return node.id === nodeId;
});

The second important point is that Sigmajs can have many cameras, and the coordinates are tracked under the attributes read_${CAM_PREFIX}:x (same for y, size, color) .
So to retrieve the position of a node for a specifc camera you need to do :
var sigmaNode = s.graph.nodes().find(function (node) {
  return node.id === nodeId;
});
s.cameras[0].goTo({
  x: sigmaNode["read_" + s.cameras[0].prefix + 'x'],
  y: sigmaNode["read_" + s.cameras[0].prefix + 'y'],
});

NOTE: The example is a stupid  because in the event, we already have the corresponding sigma node in  e.data.node.It's just to show you how to navigate into the sigma graph structure

Let me know if this answer respond to your need, so I can close the issue.


Validate the init command when it is executed on top of projects

Purpose

$subject

Fixes https://github.com/ballerina-platform/ballerina-lang/issues/11239
Automation tests

Integration tests

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes
Ran FindSecurityBugs plugin and verified report? yes
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes

Codecov Report

Merging #12739 into master will increase coverage by 0.02%.
The diff coverage is 81.94%.

@@             Coverage Diff              @@
##             master   #12739      +/-   ##
============================================
+ Coverage     59.85%   59.87%   +0.02%
  Complexity      659      659
============================================
  Files          2065     2065
  Lines        101682   101733      +51
  Branches      12936    12950      +14
============================================
+ Hits          60862    60914      +52
+ Misses        35625    35614      -11
- Partials       5195     5205      +10

Impacted Files
Coverage Δ
Complexity Δ

...a/org/ballerinalang/packerina/cmd/InitCommand.java
75% <81.94%> (+6.19%)
0 <0> (ø)
:arrow_down:

...a/org/ballerinalang/bre/bvm/WorkerDataChannel.java
82.09% <0%> (-4.33%)
0% <0%> (ø)

...et/http/actions/httpclient/AbstractHTTPAction.java
78.01% <0%> (-0.87%)
0% <0%> (ø)

...e/src/main/java/org/ballerinalang/bre/bvm/BVM.java
80.34% <0%> (-0.04%)
0% <0%> (ø)

...org/ballerinalang/bre/bvm/WaitCallbackHandler.java
82.56% <0%> (ø)
0% <0%> (ø)
:arrow_down:

.../org/ballerinalang/packerina/init/InitHandler.java
80.48% <0%> (+1.21%)
0% <0%> (ø)
:arrow_down:

...java/org/ballerinalang/packerina/BuilderUtils.java
78.84% <0%> (+3.84%)
0% <0%> (ø)
:arrow_down:

.../wso2/ballerinalang/compiler/BinaryFileWriter.java
73.56% <0%> (+4.59%)
0% <0%> (ø)
:arrow_down:

...va/org/ballerinalang/channels/ChannelRegistry.java
94.59% <0%> (+5.4%)
0% <0%> (ø)
:arrow_down:

.../org/ballerinalang/packerina/cmd/BuildCommand.java
19.71% <0%> (+11.26%)
0% <0%> (ø)
: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 0547701...28a8ce3. Read the comment docs.


Screen sharing on v4.x

Hey @LichKing-2234, we had a method to capture the screen with v3.7.0 of the react-native SDK.
Do we have support for sharing the screen on react-native SDK v4.x? The api reference has an empty table:

Is this planned for the future? Can we add this as a feature request?

Yess, its supported. Checkout this example https://github.com/AgoraIO-Extensions/react-native-agora/tree/main/example/src/examples/advanced/ScreenShare.
I'm facing some issues with the iOS screen share extension tho.

You can refer to the this example.

Yess, its supported. Checkout this example https://github.com/AgoraIO-Extensions/react-native-agora/tree/main/example/src/examples/advanced/ScreenShare.
I'm facing some issues with the iOS screen share extension tho.

Maybe you can point me in the right direction @EkaanshArora @LichKing-2234 .
I'm trying to implement the screen share feature which is working fine on Android, but it does not on iOS (using the v4.0.0).
Calling showRPSystemBroadcastPickerView() opens the picker with the app extension, after pressing Start Broadcast the count down goes to 0, but it never start recording the screen (I attached a SS).
I already:

Added the Broadcast Upload Extension.
Updated the NSExtensionPrincipalClass to AgoraReplayKitHandler.

is there something I'm missing?
I'm using the RN v0.66.5 and my ios target is 12.1.


PIC 9(11)v9(02) fields converting full of spaces into 0.00

Describe the bug
The hex value in the source file is<PHONE_NUMBER>4040404040404040, which is full of zeroes. But while reading the file , the spaces converted into 0.00. We are expecting null here.
Code snippet that caused the issue
  spark.read
   .format("cobol")

Expected behavior
A clear and concise description of what you expected to happen.
Context

Cobrix version:
Spark version:
Scala version:
Operating system:

Copybook (if possible)
         01  RECORD.
           05  FIELD1    PIC 9(11)V9(02).

Attach a small data file that can help reproduce the issue, if possible.
Read_options:
{'encoding': 'EBCDIC', 'ebcdic_code_page': 'cp037', 'string_trimming_policy': 'none', 'debug_ignore_file_size': 'true'}
@yruslan , Could you please guide us to fix this issue

There is an option ('improved_null_detection') that improves the behavior of null detection.  But even when it is turned on the issue you specified takes place. Will fix.
In 2.5.0 the option will be turned on by default.


Wrong iOS version detected

I'm using iOS 9.0.2 (updated after 9.1 was released) on an iPhone 5S, but canijailbreak says that I'm using 9.1.

a) this is not for support
b) you are misunderstanding the website, it's "IF you are on this version, CAN you jailbreak?".
Closing this.


Timeline 2

Fixes #88

Codecov Report
Attention: Patch coverage is 17.39130% with 19 lines in your changes missing coverage. Please review.

Files with missing lines
Patch %
Lines

...seedu/address/model/types/common/DateTimeUtil.java
12.50%
7 Missing :warning:

src/main/java/seedu/address/ui/MainWindow.java
0.00%
5 Missing :warning:

...rc/main/java/seedu/address/logic/LogicManager.java
0.00%
2 Missing :warning:

src/main/java/seedu/address/model/AddressBook.java
33.33%
2 Missing :warning:

...rc/main/java/seedu/address/model/ModelManager.java
0.00%
2 Missing :warning:

...edu/address/model/types/event/UniqueEventList.java
66.66%
1 Missing :warning:

Files with missing lines
Coverage Δ
Complexity Δ

src/main/java/seedu/address/model/Model.java
100.00% <ø> (ø)
2.00 <0.00> (ø)

...edu/address/model/types/event/UniqueEventList.java
57.74% <66.66%> (+4.88%)
19.00 <0.00> (+1.00)

...rc/main/java/seedu/address/logic/LogicManager.java
68.00% <0.00%> (-5.92%)
3.00 <0.00> (ø)

src/main/java/seedu/address/model/AddressBook.java
79.59% <33.33%> (-3.02%)
17.00 <1.00> (ø)

...rc/main/java/seedu/address/model/ModelManager.java
78.20% <0.00%> (-2.06%)
27.00 <0.00> (ø)

src/main/java/seedu/address/ui/MainWindow.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

...seedu/address/model/types/common/DateTimeUtil.java
21.42% <12.50%> (-3.58%)
2.00 <1.00> (ø)


fix always scrollToTop, introduce slate heading anchors UUID based

@nileshgulia1 Thank you for this PR.
Still, the scroll seems not to work properly when you're opening in new tab. See attached video:
open-in-new-tab.webm

@avoinea Sorry, The customization paths were incorrect. Fixed in 26624ae

@nileshgulia1 Can you please move this to a dedicated add-on? This feature will be needed for sure to be used also with other EEA websites.
We will also have to extend it's functionality to add support for accordion / tabs to open closed accordion / tab pane if the heading is within there.

@avoinea New addon created https://github.com/eea/volto-anchors/pull/1
The slate heading anchors are now based on sluggified titles. TOC blocks are also aware of title slugs when navigating along with a fix for override_toc.


allow internalFetch to pass env and locals

With Cloudflare at least, internalFetch is mostly useless in many situations, as environment variables are only available through the event, and are reset to {} by internalFetch.
Also, locals is the most common place for middleware to store request context, and as middleware isn't run again when internalFetch is used, it's useful to be able to pass this through from the parent request.

An alternative would be to change the second argument to an APIEvent and just override request, params, clientAddress, $type, and fetch, and pass through the rest. This way we wouldn't need to add more arguments if more properties are added to APIEvent in the future. But that would be a breaking change.


Improved Dice score

Match each nucleus in users volume with greatest overlap (best Dice score?) in gold standard, compute average Dice score across all nuclei.
Also need to go in the other direction: gold -> user

Have implemented a multilabel version of the Dice score in Matlab, code here:
Seems to work well, need to implement in ninjato.

Implemented


'index.js' could not be saved. Error: undefined

Go to Atom
Click save
No save

It was working perfectly 3 hours before. I had no idea what changed. I legit just kept pushing changes to my file.
I expect it to push to firebase.
I get error 'index.js' could not be saved.
Error: undefined
Every time I save.
I am runing on the latest version of mac, firebase and atom.  I have no idea what changes were caused that made it start doing this. I added one var that was supposed to give firebase access to this directory, then was getting the error.

Thanks for reaching out!
We require the template to be filled out on all new issues and pull requests. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests.
Thanks for understanding and meeting us half way 😀

But this looks like an individual issue, maybe caused by the OS or permissions, I have the same setup and I couldn't reproduce this, if the issue is still persisting feel to open a new issue with the provided template and share as much information to try reproducing the bug


nixos/test-driver: use usb-ehci controller instead of piix3-usb-uhci

Motivation for this change
nixosTests.boot.biosUsb and nixosTests.boot.uefiUsb are very slow to run right now.
On my system this change cuts running time of these tests from ~13 minutes to ~2 minutes.
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[X] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

i just tested in on my laptop, this is cool.
I would immediately merge it but i wonder why the borg test says "no attempt"

i wonder why the borg test says "no attempt"

These tests aren't enabled for aarch64 for some reason. x86_64 tests are passing.


Discard fetches when the active account has changed

When we go and fetch some data from the server, we should be sure to associate the resulting data with the right account, and not with some other of the user's accounts. In particular this should be the case even if the fetch took a while, and if in the interim the user went and switched to look at a different account (the new "active account".)
We'll need to solve this as part of #5005, where we'll potentially have several fetches going concurrently for several different accounts, and each will need to know which account the results should get stored under.
But pending that, in our current world where we have server data for just the one active account at a time, it'd be enough to discard the fetch's result (and ideally cancel the fetch itself, #4170) if the active account has changed by then.
Currently we do this in the event-queue long-polling loop in startEventPolling, which is the most important case, but not most other places -- notably, not in ~doInitialFetch~ registerAndStartPolling, or the various message-fetching actions in fetchActions.js.
Issues #4170 and #4659 cover parts of how we might do this.
Issue #3791 is basically an example symptom of this.

We got a report today of what is probably this issue:
https://chat.zulip.org/#narrow/stream/48-mobile/topic/local.20cross-realm.20leakage.20issue/near/1444848

Any objection to changing the title from

Discard fetches when the active account has changed

to

Discard fetches when the active, logged-in account has changed

, since we probably want to cancel fetches on logout too?


Reported institutions aggregate report isn't being parsed

Reported institutions aggregate report isn't being parsed and isn't rendering on the front end. A sample report is available here: http://s3.amazonaws.com/cfpb-hmda-public/dev/reports/aggregate/2018/49740/i.json

It looks like the chunk of code responsible for listing the institutions was looking for respondent id/name fields instead of an array of institutions.


Execute alexnet using ligbpuarray backend

I am trying to execute alexnet using new libgpuarray backend for 1 gpu. The modifications that I have done to the 1 gpu sample are as in - 1gpu_libgpuarray_patch.txt
However, with these changes I get following error -
ValueError: ('The following error happened while compiling the node', DnnVersion(), '\n', 'context name None is already defined')
Complete error log - 1gpu_libgpuarray_error.txt
Further updating train.py to use
theano.gpuarray.use("cuda")instead of     theano.gpuarray.use(config['gpu']) then it starts training. But I don't think that this is correct. Please advise.

@deepali-c
The changes for making the single GPU train.py working requires changing any sandbox.cuda functions to gpuarray alternatives. moving any import theano after setting up device context. The  device context can be set up like this:
https://github.com/uoguelph-mlrg/Theano-MPI/blob/master/theanompi/models/test_model.py#L11
The parallel loading part is also different but still based on socket and ipc handle. See
https://github.com/uoguelph-mlrg/Theano-MPI/blob/master/theanompi/models/data/proc_load_mpi.py#L126
The two GPU version train_2gpu.py will require including replacing the pycuda.device_d2d() function with two pygpu.collectives.broadcast() function calls.
As the method used in this work has a strong dependency on the CudaNdarray Backend of Theano version < 0.9 and the pycuda library, we'd better make a new branch for trying the new GPUArray Backend.

I have tried below mentioned two approaches, for using new backend with 1 gpu :

Modified train.py to setup device context as in Theano-MPI: (Along with changes to use gpuarray alternatives)

    import os
    os.environ['THEANO_FLAGS'] = 'device={0}'.format(config['gpu'])
    import theano.gpuarray
    # This is a bit of black magic that may stop working in future
    # theano releases
    ctx = theano.gpuarray.type.get_context(None)

This gives the following error:
THEANO_FLAGS=device=cuda0,mode=FAST_RUN,floatX=float32 python train.py
....
...#more output here
.....
`TypeError: Cannot convert Type TensorType(float64, 4D) (of Variable HostFromGpu(gpuarray).0) into Type TensorType(float32, 4D). You can try to manually convert HostFromGpu(gpuarray).0 into a TensorType(float32, 4D).`

Updated train.py according to the patch I have shared in this thread previously then it works fine.

The difference is that in #1 I am trying to setup device context using the new method, instead of the pycuda gpu setup. Looks like I have missed something while doing so, please advise.

@deepali-c
The error looks like something with floatX.
Anyways, I just created a pygpu branch. And the single GPU train.py is working. You can compare your path with this commit to see what are the necessary changes.
To use it, I recommend upgrading to the bleeding edge libgpuarray/pygpu and theano. I just tried on them and it's working.

@hma02 , Thank you so much for these changes. The 1 gpu examples works with libgpuarray on my setup as well.
I am working on the 2 gpu sample next.

@deepali-c
I just made the train_2gpu.py working based on pygpu collectives, which is then based on NCCL. So you need to install NCCL, libgpuarray and its wrapper pygpu in order to run this.

Thanks @hma02 .
I observed the following error while executing the 2 gpu sample with gpuarray backend:
Process Process-2:
Process Process-1:
Traceback (most recent call last):
Traceback (most recent call last):
  File "/usr/lib/python2.7/multiprocessing/process.py", line 258, in _bootstrap
  File "/usr/lib/python2.7/multiprocessing/process.py", line 258, in _bootstrap
    self.run()
  File "/usr/lib/python2.7/multiprocessing/process.py", line 114, in run
    self.run()
  File "/usr/lib/python2.7/multiprocessing/process.py", line 114, in run
    self._target(*self._args, **self._kwargs)
  File "train_2gpu.py", line 356, in train_net
    self._target(*self._args, **self._kwargs)
  File "train_2gpu.py", line 356, in train_net
    gpu_send_queue.put(this_val_error)
    gpu_send_queue.put(this_val_error)
UnboundLocalError: local variable 'gpu_send_queue' referenced before assignment
UnboundLocalError: local variable 'gpu_send_queue' referenced before assignment

I made the following change in the code - train_2gpu.py and then it could proceed without the above error.
-        gpu_send_queue.put(this_val_error)
-        that_val_error = gpu_recv_queue.get()
-        this_val_error = (this_val_error + that_val_error) / 2.
-
-        gpu_send_queue.put(this_val_loss)
-        that_val_loss = gpu_recv_queue.get()
-        this_val_loss = (this_val_loss + that_val_loss) / 2.
+        if os.environ['backend']=='gpuarray':
+           exch.exchange()
+       else:
+           gpu_send_queue.put(this_val_error)
+           that_val_error = gpu_recv_queue.get()
+           this_val_error = (this_val_error + that_val_error) / 2.
+
+           gpu_send_queue.put(this_val_loss)
+           that_val_loss = gpu_recv_queue.get()
+           this_val_loss = (this_val_loss + that_val_loss) / 2.

@deepali-c
Sorry, I forgot to debug the valuation part. See the [last commit] (https://github.com/uoguelph-mlrg/theano_alexnet/commit/31222da3f5ba7ec4b3bc78a8ae5a95ebf80aaa77#diff-238fca2c2416136f03efe7a9d712964dL356) regarding this issue.
The exch.exchange() is for exchanging the total_params. Here what we need is to average the validation error and cost over two workers, which is similar but exch is a instance already bound to those total_params.

Thanks @hma02.
I got it now.


Do not restore the promise chain on error, instead continue errors

Hello,
I have an issue where I'm using the promise in one of my components and it is not able to catch the error because returning the error restores the promise chain to be handled by the next then.
For example inside the component:
  update = (data) => {
    this.props
      .updateData(data)
      .then(data => this.onSuccess(data))
      .catch(err => this.onError(err));
  };

The above code will never run this.onError(err) even if in the error case.

@KevinGrandon Hi, yes I will add a test or two

@KevinGrandon Just fixed the test. It was simpler than I thought..


Customization of look & feel or alternative theme

Hello!
Thanks for creating great project! I really like it.
It would be nice if there was possibility to customize look & feel of Mutate or if there was alternative themes. E.g. thin, black launcher with box corners would be great!
Moreover, it would be nice if user could customize location of the launcher on the screen (e.g. in the middle instead of the top of the screen).
Can you create something like that or guide me, how can I do it myself?
Regards.

I would also be interested in this, mainly for the sake of changing the font to appear in line with the rest of my system.

@motdef I actually tried dmenu for launching apps and Gnome Pie for the same thing and controlling audio. It's sort of minimalist alternative for Mutate with slightly different approach. Choice of the concrete solution depends on user's needs. :-)

The most recent pull requests that got merged have a dark them in them.  I have compiled them locally and it looks great!  https://github.com/qdore/Mutate/pull/97


I changed the REAMDE.md, check that it is complete.

I changed the REAMDE.md, check that it is complete.

The licence and an easy way to found the tutorial???

The licence and an easy way to found the tutorial???

The licence it's not in Grispy or Pyedra ... but I can put it
The link to the tutorial it's a great idea


weird hack in PygmentsRenderer

the type mistletoe.block_token.BlockCode cannot directly access its attribute content, so I had to do this. :)

I'm not too familiar with pygments, but it's clear to see that unit tests are sorely missing. I'd suggest to add at least one test case so that this type of problems wouldn't go undetected.
Are you sure this hack is needed with the master version, though? A content property was added to the BlockCode class a while back which is supposed to do this de-referencing for you.

close: I can confirm @anderskaplan's words, i.e. there seems to be no problem accessing the BlockCode's property content since e853a0def73f4d4.


Music Bot does not realize its in voice channel

Attempting to autosummon...
Found owner in "pls work", attempting to join...
Traceback (most recent call last):
File "C:\Users\kchoe\AppData\Local\Programs\Python\Python35\lib\site-packages\discord\client.py", line 275, in _run_event
yield from getattr(self, event)(_args, *_kwargs)
File "C:\Users\kchoe\Desktop\MusicBot\musicbot\bot.py", line 696, in on_ready
owner_vc = await self._auto_summon()
File "C:\Users\kchoe\Desktop\MusicBot\musicbot\bot.py", line 148, in _auto_summon
await self.cmd_summon(owner.voice_channel, owner, None)
File "C:\Users\kchoe\Desktop\MusicBot\musicbot\bot.py", line 1311, in cmd_summon
player = await self.get_player(author.voice_channel, create=True)
File "C:\Users\kchoe\Desktop\MusicBot\musicbot\bot.py", line 354, in get_player
voice_client = await self.get_voice_client(channel)
File "C:\Users\kchoe\Desktop\MusicBot\musicbot\bot.py", line 241, in get_voice_client
voice_client = VoiceClient(**kwargs)
File "C:\Users\kchoe\AppData\Local\Programs\Python\Python35\lib\site-packages\discord\voice_client.py", line 191, in init
raise RuntimeError("PyNaCl library needed in order to use voice")
RuntimeError: PyNaCl library needed in order to use voice
^^this is when i first turn on the bot
then when i try to play a song it says
[Command]<PHONE_NUMBER>36888835/Kevin (!play kill yourself)
<class 'musicbot.exceptions.CommandError'>: The bot is not in a voice channel.  Use !summon to summon it to your voice channel.

This just started happening to me tonight as well.
Attempting to autosummon...
Found owner in "League", attempting to join...
Traceback (most recent call last):
File "C:\Users\Collin\AppData\Local\Programs\Python\Python35\lib\site-packages\discord\client.py", line 275, in _run_event
yield from getattr(self, event)(*args, **kwargs)
File "C:\Users\Collin\Desktop\MusicBot-review\MusicBot\musicbot\bot.py", line 696, in on_ready
owner_vc = await self._auto_summon()
File "C:\Users\Collin\Desktop\MusicBot-review\MusicBot\musicbot\bot.py", line 148, in _auto_summon
await self.cmd_summon(owner.voice_channel, owner, None)
File "C:\Users\Collin\Desktop\MusicBot-review\MusicBot\musicbot\bot.py", line 1311, in cmd_summon
player = await self.get_player(author.voice_channel, create=True)
File "C:\Users\Collin\Desktop\MusicBot-review\MusicBot\musicbot\bot.py", line 354, in get_player
voice_client = await self.get_voice_client(channel)
File "C:\Users\Collin\Desktop\MusicBot-review\MusicBot\musicbot\bot.py", line 241, in get_voice_client
voice_client = VoiceClient(**kwargs)
File "C:\Users\Collin\AppData\Local\Programs\Python\Python35\lib\site-packages\discord\voice_client.py", line 191, in init
raise RuntimeError("PyNaCl library needed in order to use voice")
RuntimeError: PyNaCl library needed in order to use voice

Change the zip link in requirements.txt to discord.py[voice] and update deps

copying cffi\ffiplatform.py -> build\lib.win-amd64-3.5\cffi
copying cffi\lock.py -> build\lib.win-amd64-3.5\cffi
copying cffi\model.py -> build\lib.win-amd64-3.5\cffi
copying cffi\recompiler.py -> build\lib.win-amd64-3.5\cffi
copying cffi\setuptools_ext.py -> build\lib.win-amd64-3.5\cffi
copying cffi\vengine_cpy.py -> build\lib.win-amd64-3.5\cffi
copying cffi\vengine_gen.py -> build\lib.win-amd64-3.5\cffi
copying cffi\verifier.py -> build\lib.win-amd64-3.5\cffi
copying cffi_init_.py -> build\lib.win-amd64-3.5\cffi
copying cffi_cffi_include.h -> build\lib.win-amd64-3.5\cffi
copying cffi\parse_c_type.h -> build\lib.win-amd64-3.5\cffi
copying cffi_embedding.h -> build\lib.win-amd64-3.5\cffi
running build_ext
building '_cffi_backend' extension
error: Unable to find vcvarsall.bat
----------------------------------------

Command "C:\Users\kchoe\AppData\Local\Programs\Python\Python35\python.exe -c "import setuptools, tokenize;file='C:\Users\kchoe\AppData\Local\Temp\pip-build-62lt64z7\cffi\setup.py';exec(compile(getattr(tokenize, 'open', open)(file).read().replace('\r\n', '\n'), file, 'exec'))" install --record C:\Users\kchoe\AppData\Local\Temp\pip-sq1qmzoa-record\install-record.txt --single-version-externally-managed --compile" failed with error code 1 in C:\Users\kchoe\AppData\Local\Temp\pip-build-62lt64z7\cffi
You are using pip version 7.1.2, however version 8.1.2 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
C:\Users\kchoe\Desktop\MusicBot>

this is what i got when i did that

Add 'cffi==1.6.0' on a new line

onto requirements?

Yea

it worked! thank you so much

dab

Change link to what?


Private mode

Would it be possible to add a private mode like what is in the native safari app?

It's certainly possible! However I'll be honest I don't have a lot of time to work on this project at the moment. I will tell you that in the current app store version you can turn off history tracking in the settings. This will keep pages from being store in history.


Unbalanced calls to begin/end appearance transitions for

The warning "The unbalanced calls to begin/end appearance transitions" seems to occur on my UINavigationViewController when i tries to present another controller.

How are you presenting the new controller?

            self.transition = BubbleTransition()
            self.transition.startingPoint = self.btn_AddJoke.center
            let nav = UINavigationController.init(rootViewController: vc)
            nav.setNavigationBarHidden(true, animated: false)
            nav.transitioningDelegate = self
            nav.modalPresentationStyle = .custom
            nav.setNavigationBarHidden(true, animated: false)
            self.present(nav, animated: true, completion: nil)

OK, pushing a navigation controller causes that.
I'm a bit stumped, help on the subject is welcome.

Same problem here. Anybody has the solution?

I was able to fix this by changing the modalPresentationStyle of the navVC to .overFullScreen
navVC.modalPresentationStyle = .overFullScreen`


Add custom WSDL cache option

Currently the library caches WSDLs for the lifetime of the process. This is not ideal for long running processes like a backend service that connect to many SOAP webservices.
Adding an option to override the current lifetime cache with a custom cache so user can bring their own cache, e.g. TTL or LRU. I had considered just disabling the cache using the existing option, but this is not also not ideal.
Code changes:

Adding IWSDLCache interface which can be extended with custom caching implementations
Added DefaultWSDLCache implementation which matches current caching handling, ie global singleton which indefinitely caches WSDLs.
Added options.wsdlCache to allow users to override the default cache.
Added test cases for default cache and overriding option.

I also tested with npm link against an existing application that uses node-soap. By adding ?v=1, ?v=2 and so on to the WSDL URL, you can simulate loading many different WSDLs. Setting  max-old-space-size to something like 128, eventually the process will crash with the default cache. For my application, this occurred around 1000th WSDL with a 128mb limit. I updated to use a cache with a set max item limit and memory remained low and the process did not crash even when reaching the 1000 WSDL loaded mark.

Hi @millerdk12,
Thanks for the improvement. I will include this into next release.

Great, thanks for taking a look!

@millerdk12 version 1.1.6 has been released


Support Python 3.8?

:wave: hi there, thanks for maintaining this package.  A brief look through the code doesn't show any language features from python >=3.9, but the pyproject.toml lists it as a requirement.  Would you be amenable to loosening support to 3.8?

Hi! Yes, I will add support for 3.8

Added in 1.0.1


PowerToys Run windows position changes based on number of results

Microsoft PowerToys version
0.83.0
Installation method
PowerToys auto-update
Running as admin
None
Area(s) with issue?
PowerToys Run
Steps to reproduce

Disable clear previous query on launch setting.

open PowerToys Run

Type words in input box until result listed becomes fewer.

Now close the PowerToys Run.
Reopen it.

Now the position of the PowerToys Run would have changed based on the number of results.

✔ Expected Behavior
The position of PowerToys Run not changes based on number of results of previous query.
❌ Actual Behavior
Position of PowerToys Run changing based on number of results of previous query.
Other Software
No response

I am able to repro.


AI when enabled, makes debugging in VS 2019 2-2.5 times slower

Hi Guys,
I'm not sure this is the right place for that issue but let's at least start here.
We have regular .NET Core 2.2 SPA APP, we use SQL Server & SignalR and do not do anything extra ordinary. When we debug in the VS all requests from ther client (browser) takes huuuuge amount of time, seconds. When code runs without debugger attached everything is just flying. I started investigating and found that if I disable AI in the VS->Tools->Options->IntelliTrace->General Enable Intelli Trace things start working almost like without having debugger. We observe same behaviour on all our dev machines (about 15). So, as for me, that is usability bug. I'm happy to help to investigate, could provide any extra info needed. Feel free co contact me in skype yahor.si igf needed.
Thanks

IntelliTrace and ApplicationInsights are separate products. Though the title say AI, the descriptions and steps are about IntelliTrace.
Can you confirm if this is intellitrace? I'll tag someone with VS knowledge to send this issue to the right place based on that.

Sorry, that's intellitrace

To identify if this has anything to do with App Insights, re-enable IntelliTrace, but then go to Tools -> extensions and disable the "Developer Analytics Tools"  extension.

If debugging is fine with IntelliTrace enabled and AppInsights disabled, this could be an issue with the AI debug extension in VS.
if debugging is still bad with AppInsights disabled, the quickest way to get help from the right people is to submit feedback from inside VS itself via Help -> send feedback -> report a problem

Developer Analytics Tools

Today I had a bit of time, I have disabled "Developer Analytics Tools", it is not in Tools, it is in Extensions top menu. But perf is really really horrible. So, perf is not Developer Analytics Tools.
And I should say, VS & IntelliTrace & still AI are on the quality state that I cannot even imagine.
It is completely unusable and it is not only from perf view.
I tried today to really use IntelliTrace and AI buit in VS to build request processing timeline and I should say, this thing is not used by onyone and not tested by anyone coz it just does not work.
When I enable IntelliTrace events, requests start taking seconds, it's like literally 4-10 seconds while befoe it was like 100-200ms. How that is possible at all (( And, even working so slow, the result, events and AI viewer built in VS are still unusable
And by the way, I was unable to report the bug(s) because of the bug in the bug reporting (((((
It just fails to authenticate me, while I'm successfully logged in in VS.
I'm dying ((((
Need VS quality engeneer to demo all the problems I've got

Ok, lets get back to that :)
As I wrote above, the biggest contributer to the very slow debugging performance is IntelliTrace. When we just disable IntelliTrace response time (under debugging in VS) goes from seconds (1-20) to under second 600ms - 800ms
See https://developercommunity.visualstudio.com/content/problem/620245/intellitrace-very-slow-debugging-expirience.html
But, then, if we disable ApplicationInsights in code, e.g. just comment UseApplicationInsights call WebHostBuilder, we see another ~2 to 2.5 times response time improvement (again under debugging).
I think paying 2-2.5 times is too much for having AI
PS: Please let me know if anyone is still following that issue, or I need to close this one and create new one.
PPS: I'll edit the title according to findings

Application Insights SDK does behave differently when it's used in VS Debug scenarios and indeed adds an additional overhead:

AI SDK would write Debug.Output with all event information;
AI SDK will push copy of this data to Event Source id Debug listeners are enabled for Event Sources (default in VS debug, I guess);
AI SDK will write Event Source messages about each execution step if process-level listeners are enabled (I guess that's also default in VS Debug);
Finally, DeveloperMode=true will be automatically enabled in AI SDK for Debug mode to make sure that each and every Telemetry item is not batched and is sent instead as soon as they are produced.

Overall, a series of optimizations in AI SDK is off in this case and is expected to be that way to simplify debugging (with the exception of slowing debugging down a little as you noticed).
You can control Configuration.TelemetryChannel.DeveloperMode setting for sure. I imagine there is a setting in VS Debug that may allow to disable Event Source listeners as well. I don't think Debug.Output can be disabled easily, though.
Unfortunately, I cannot speak to any possible issues with VS and Intellitrace, that portion of the issue should be moved accordingly to the places where these teams track items and/or UserVoice.

Thank you for the answer.
Is't is possible to do the things you mentioned but async?
Like writing to the Debug.Output and so on?
Even taking what you sad I still think the price of being 2.5x slower under debugger is IMHO to big.

Unfortunately, I cannot speak to any possible issues with VS and Intellitrace, that portion of the issue should be moved accordingly to the places where these teams track items and/or UserVoice.

I've already created ticked for the VS team with recorded repo
https://developercommunity.visualstudio.com/content/problem/620245/intellitrace-very-slow-debugging-expirience.html

Developer Mode to false should make most of the operations like serialization and sending events, async.
Debug.Output, though would still be typical Debug.Output as well as any Event Source subscriptions.
I can advise on customizing ai.config and Telemetry Configuraiton options (e.g. you can try DisableTelemetry=true; in #if DEBUG scenarios).
Not sure if there is way to radically improve/change the established integration protocol with VS Debug tools, though. @gardnerjr , is there something else I'm missing that may help here or that we can easily fix without a lot of rework?

What we do right now is simple - we turn AI off (or better say do not turn AI on) for Development environment. One more reason why - is because we gave up trying to use it in real live in dev environment. E.g. we're unable to use it to analyse requests timeline in VS.

how much console and telemetry output do you have that it is making debugging 2x slower? 2x slower to me implies that there's a LOT of console output and telemetry that has to be processed to see if it is telemetry, and then if it is telemetry to do the things the AI extension does to analyze it.  The VS extension itself is full of AI telemetry so we debug the extension with AI turned on all the time and I don't know I've ever noticed debugging being 2x as slow.
if you still want telemetry but NOT any of the debug time features of the AI extension, you can turn off the console output of telemetry (documented elsewhere), which will effectively make it so that the extension doesn't see any telemetry so it doesn't do anything.  telemetry would still be sent by AI though while debugging.
or you could explicitly set developermode to false to get the retail behavior instead of debug behavior?


Update FindBugs version

There is a bug within the older version of FindBugs which causes the build to break with the newest version of maven.  This should be updated to fix.

Merged into develop