Make readme more readable by hiding benchmark results under  tag

Thanks @nazar-pc this is a good suggestion.
I am nearly done with a new major version, and will use that to add a table of contents to the README, rather than the details tag. I don't want to introduce HTML markup into a markdown file. I know one can, but would rather solve this with a table of contents.

Without <details> is is very inconvenient to scroll the page back and forth. Table of contents will only solve the inconvenience partially.

Sure, but <details> will only work when viewed as HTML, not in the Terminal or in Markdown viewers that don't support embedded HTML tags. At the end of the day, it's a Markdown document, not an HTML file, otherwise it would have been written as an HTML document. Furthermore, the performance numbers are important.

What about moving benchmark results into their own file?

That would mean another file in the repo, and indirection, all in the name of reducing scrolling. The numbers need to be visible at first glance, e.g. when doing design estimates. It's a core function of the README, more so than any other section.


[BUG]: Event when user disconnects all wallets

Is your request related to a problem?
I have a complex flow using multiple wallet connectors, and thus am managing connected wallets internally and not only via Onboard. If the user uses the Onboard disconnect all wallets button, I would like to catch an event and wipe those wallets from my internal state as well (since they are no longer available), however I see nothing in the docs which provides this.
I've also tried adding a watcher to the connectedWallet value to see if it is updated when all wallets are disconnected, but it doesn't appear to update.
Am I missing something in the docs, or can you add this minor feature?
Thanks
Feature Description
No response
Alternative Solutions
No response
Anything else?
No response

@Adamj1232 That worked a treat! Thanks for your support ^^


Does this gem support the "save" scope?

I want to be able to retrieve a user's saved posts/comments (see app)
Does this gem offer such capability? I was thinking of using RedditKit, but as listed here, it does not support OAuth. However, I plan to use omniauth-reddit for signing in users to my app.
Thank you.

@avinashbot Wow! Thank you for the explanation and script! I didn't know about the 1000 post limit, either. Is that also the case for the Reddit website? (I have around 950 saves, so I'm not sure.)
The only workaround I see (for my app in particular) to the 1K posts issue is... If I store each post in my own database, and every time the user syncs up, the saved count goes up past 1K if needed. But that assumes a user has under 1K posts to begin with... (I am preparing the migrations for this approach just for a deadline for class, but am still unsure whether I should do this, as I'd be documenting the entirety of reddit almost.)


StatusBarManager.HEIGHT is undefined

[ ] Review the documentation: https://facebook.github.io/react-native
[ ] Search for existing issues: https://github.com/facebook/react-native/issues
[ ] Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment
  React Native Environment Info:
System:
  OS: Windows 7
  CPU: x64 Intel(R) Core(TM) i5 CPU         650  @ 3.20GHz
  Memory: 4.24 GB / 15.87 GB
Binaries:
  Yarn: 1.7.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
  npm: 6.4.1 - C:\Program Files\nodejs\npm.CMD
IDEs:
  Android Studio: AI-173.4907809

"@babel/runtime": "^7.0.0",
"create-react-class": "^15.6.3",
"native-base": "^2.8.0",
"react": "16.5.0",
"react-native": "0.57.1",
"react-native-datepicker": "1.7.2",
"react-native-firebase": "5.0.0",
"react-native-google-autocomplete": "0.1.5",
"react-native-image-crop-picker": "0.21.2",
"react-native-loading-spinner-overlay": "0.5.2",
"react-native-modal": "^6.5.0",
"react-navigation": "2.17.0",
"rxjs": "6.3.3",
"rxjs-compat": "^6.3.3"
Description
Is their an existing issues with the  "react-native": **"0.57.1",? this just happen after i clean the gradle

Reproducible Demo
Could not even reproduce this o my other project

Closing because of inactivity.
That said it seems that this is caused by your upgrade process, I suggest you take a closer look at the changelog for extra info.


nixos/memcached: added simple set/get test

Motivation for this change
Initially developed to test the bump on the stable channel this test should help use gain more confidence in package bumps of memcached regarding the core functionality.
The test ensures that the services comes up and accepts/provides values.
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
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 nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

@GrahamcOfBorg test memcached

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: tests.memcached
Partial log (click to expand)
Cannot nix-instantiate `tests.memcached' because:
error: undefined variable 'callTests' at /var/lib/gc-of-borg/nix-test-rs-20/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-20/nixos/release.nix:337:21

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: tests.memcached
Partial log (click to expand)
Cannot nix-instantiate `tests.memcached' because:
error: undefined variable 'callTests' at /var/lib/gc-of-borg/nix-root/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/gleber-bastion/nixos/release.nix:337:21

@GrahamcOfBorg test memcached

Success on aarch64-linux (full log)
Attempted: tests.memcached
Partial log (click to expand)
machine: exit status 1
syncing
machine: running command: sync
machine: exit status 0
test script finished in 19.86s
cleaning up
killing machine (pid 627)
vde_switch: EOF on stdin, cleaning up and exiting
vde_switch: Could not remove ctl dir '/build/vde1.ctl': Directory not empty
/nix/store/3a58zab3aqgxl3w0ybqa4ssl1gbrln3j-vm-test-run-memcached

Success on x86_64-linux (full log)
Attempted: tests.memcached
Partial log (click to expand)
machine# [   12.462896] dhcpcd[702]: eth0: leased <IP_ADDRESS> for 86400 seconds
machine# [   12.623285] dhcpcd[702]: eth0: adding route to <IP_ADDRESS>/24
machine# [   12.624995] dhcpcd[702]: eth0: adding default route via <IP_ADDRESS>
machine: exit status 0
test script finished in 14.16s
cleaning up
killing machine (pid 593)
vde_switch: EOF on stdin, cleaning up and exiting
vde_switch: Could not remove ctl dir '/build/vde1.ctl': Directory not empty
/nix/store/cizdjph9r9rig4nadp4cmrj4y3gk1k6g-vm-test-run-memcached


Expose Kubernetes rest config

I'd like to expose the rest configuration in order to be able to create custom clients e.g. a generic (non resource-scoped) dynamic client or a specific Openshift client in order to access some sub-resources (in my case, processing Openshift templates).
Can it be exposed?

This would be very useful for initializing other clients. At the moment I have recreate the code that is already in the SDK to get a new instance of the config to pass to my other clients

@nicolaferraro Yes I think exposing the config should be alright since there's a legitimate use case.
Can you please update the CHANGELOG with:
The SDK exposes the Kubernetes rest config via `k8sclient.GetKubeConfig()` #338

Thanks @hasbro17, I think it should be ok now.


Apply where filters without granularity - Resolves #253

When there was no granularity in the query, custom 'where' clauses were not being applied.

Coverage increased (+0.01%) to 71.172% when pulling 7914fb5d2ec988d6a4ba8d8bb613f595e9f09f5f on skje:master into 034fd077e1215366c59742be5475abdc3bad1292 on airbnb:master.


🐞[Bug]: Regarding the UI Elements

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
Regarding the UI Elements
the UI elements are not style or aligned properly
according to issue #12
Expected behavior
the UI elements are not style or aligned properly
Add ScreenShots
check this
https://github.com/Anishkagupta04/RAPIDOC-HEALTHCARE-WEBSITE-/assets/125277258/74b02675-4bec-44b0-bc58-84485c979bf9
What browsers are you seeing the problem on?
Microsoft Edge
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@Anishkagupta04 and @varshith257 i want to work upon it

Assigning

i thought by changing css we can fix it @Anishkagupta04 can you please assign me

hy @Rishikesh63 i work on it


Have instance url be actual text and not placeholder?

Maybe this is a bad suggestion, but it might be good to have the url of the official Linkwarden instance being the actual prefilled text in the configuration panel of the extension instead of just placeholder

Ok, will change this


[numpy] np.tensordot fails with 0-size tensor

Description
np.tensordot does not work with 0-size tensor
Environment info
python 3.7.3
Minimum reproducible example
import mxnet as mx
import numpy as _np
from mxnet import np, npx
a_np = _np.empty((0, 4))
b_np = _np.empty((5, 0))
ret = _np.tensordot(a_np, b_np, axes=((0,), (1,)))
print(ret)
npx.set_np()
a = np.empty((0, 4))
b = np.empty((5, 0))
a.attach_grad()
b.attach_grad()
with mx.autograd.record():
  ret = np.tensordot(a, b, axes=((0, ), (1, )))
ret.backward()
print(ret)
print(a.grad)
print(b.grad)

The result is
[[0. 0. 0. 0. 0.]
 [0. 0. 0. 0. 0.]
 [0. 0. 0. 0. 0.]
 [0. 0. 0. 0. 0.]]

Intel MKL ERROR: Parameter 9 was incorrect on entry to cblas_sgemm.
[[0. 0. 0. 0. 0.]
 [0. 0. 0. 0. 0.]
 [0. 0. 0. 0. 0.]
 [0. 0. 0. 0. 0.]]
[]
[]

Thank @ckt624 @reminisce for kind help.

@mxnet-label-bot add [bug]

Tried the test script on latest master and the bug is fixed now.

Closing the issue, feel free to reopen if the same bug pops up again.


transforms to_pil_image clamp

I was trying to convert images from tensor to save them on disk later and noticed strange behaviour in v2.ToPILImage.
If I save tensor calling save_image from torchvision.utils, it results in this:

However, if I try to convert tensor by calling v2.ToPILImage and then save it with Image.save() thats what I get:

As you can see, there are these strange bright pink areas.
Torchvision.utils saves the image this way:
https://github.com/pytorch/vision/blob/e0fd033c7db4f4e2e30d3452ed03ce35e097fc01/torchvision/utils.py#L149-L150
In v2.toPILImage there's following:
https://github.com/pytorch/vision/blob/e0fd033c7db4f4e2e30d3452ed03ce35e097fc01/torchvision/transforms/functional.py#L280-L281
so I manually did transform my image:
ndarr = result_tensor.mul(255).add_(0.5).clamp_(0, 255).permute(1, 2, 0).to("cpu", torch.uint8).numpy()
result_img = Image.fromarray(ndarr)
and the problem disappeared.
I don't know about adding 0.5 (I assume it is used for better rounding), but from what I understand clamp() is missing here.

Thanks for the report @irtez
What's the min() and max() values of the tensor image? It's possible that the float tensor isn't exactly within [0, 1] which might be causing the under/overflow issues

Thanks for the report @irtez
What's the min() and max() values of the tensor image? It's possible that the float tensor isn't exactly within [0, 1] which might be causing the under/overflow issues

Yes, this is causing the problem, last layer of my net is convolutional and output tensors are not in [0, 1]. But shouldn't toPILImage clamp these out-of-range values like save_image to not cause problems with image?

That's a fair point, but unfortunately, it's quite hard to please everyone here and for every user who would like the transfrom to clamp the input, we'd find another user who doesn't want the clamping to happen.
Always clamping and in every single transform is potentially a waste of time and negatively affects performance, for those users who know that the [0, 1] range is always respected on float tensors. So right now, we don't clamp of check manually, and rely on the (documented) assumption that the input is in [0, 1] if the image is a float. The drawback is that in some cases, it will lead to the issue you're experimenting though :/
Your best bet here would be to manually clamp to [0, 1] before calling ToPilImage() (or more generally, right after the output of your network)


swkbd: fix support for latest libnx commits.

Thanks for the PR! I'll merge it when the libnx changes get released.


[Enhancement]use awaitility  in partial update testcases

Proposed changes
Issue Number: close #xxx
#37817
use awaitility  to replace thread.sleep in partial update regression testcases

run buildall

run buildall


Convert spack-install script to ansible

This change:

Swaps out the remainder of the shell install spack script for ansible
Refactors ramble install script for code reuse between spack and ramble

Note to reviewer:

First review changes to community/modules/scripts/ramble-setup/templates/ramble_setup.yml.tpl
Then you can skip review of duplicate community/modules/scripts/spack-install/templates/spack_setup.yml.tpl
After above conversation and ignoring lines from deleted file PR is 139 lines

Testing:

I have manually tested both spack and ramble deployments
I tested parallel spack build with 12 VMs all running install in parallel on filestore HDD.

As designed only 1 machine grabbed lock and performed install

Submission Checklist
Please take the following actions before submitting this pull request.

Fork your PR branch from the Toolkit "develop" branch (not main)
Test all changes with pre-commit in a local branch #
Confirm that "make tests" passes all tests
Add or modify unit tests to cover code changes
Ensure that unit test coverage remains above 80%
Update all applicable documentation
Follow Cloud HPC Toolkit Contribution guidelines #

2 actions requested, 3rd optional

I realize I put some of the comments on the 2nd file. This is user/UI error. They are meant to apply to both playbooks.

not a fan of using Terraform templating to render Ansible

I understand. I have made a point to not render anything into the body of the ansible and require all rendered variables are defined at the top. This allows for this file to be more or less reused in a non-rendered condition. It is written such that we could pass all the vars as args in startup-script but this looks very ugly. Without trying to solve the larger problem of how we pass args I am trying to make the script compatible with future changes.


Client still depends on legacy API

The Git LFS v1 Original API says:

This describes the original API for Git LFS v0.5.x. It's already deprecated by the batch API.

and the Git LFS v1 Batch API says:

This is a newer API introduced in Git LFS v0.5.2, and made the default in Git LFS v0.6.0. The client automatically detects if the server does not implement the API yet, and falls back to the legacy API.

However v1.0.0 of the client still depends on the legacy API for clone operations. During git clone, GETing LFS objects will fail with the following error where the legacy API is not available:
Repository or object not found: http://localhost/scm/test/lfsrepo.git/info/lfs/objects/1b88b71728388427ca7c6df0948add966bb0799b6a2dbb669145e84526fa81b4

Blah, you're right! Looks like the smudge command is still using the old API for some reason:
trace git-lfs: HTTP: 200
17:22:07.449748 run-command.c:351       trace: run_command: 'git-lfs smudge '\''gif/droidtocat.gif'\'''
17:22:07.450162 run-command.c:199       trace: exec: '/bin/sh' '-c' 'git-lfs smudge '\''gif/droidtocat.gif'\''' 'git-lfs smudge '\''gif/droidtocat.gif'\'''
trace git-lfs: run_command: 'git' config -l
trace git-lfs: run_command: 'git' config -l -f .git/config
Downloading gif/droidtocat.gif (24.65 KB)
trace git-lfs: HTTP: GET https://github.com/github/git-lfs-test.git/info/lfs/objects/d1c8fab51418ef587fcf5dd8e73c60b9700704e2f8f5292ea12ec27c285b23a3
trace git-lfs: HTTP: 200
trace git-lfs: HTTP: GET https://github-cloud.s3.amazonaws.com/alambic/media/111976139/d1/c8/d1c8fab51418ef587fcf5dd8e73c60b9700704e2f8f5292ea12ec27c285b23a3?actor_id=21
trace git-lfs: HTTP: 200

We'll get that fixed up in 1.0.1. Thanks for the report!


Add setting to enable wireguard NAPI threading

Description
This adds a new setting to enable wireguard NAPI threading on the wireguard interfaces. NAPI threading can be used with wireguard to help increase maximum packets-per-second by distributing the tunnel's load from one core to many cores via a NAPI kernel thread.
This option is off by default and can be configured via the FelixConfiguration the same way wireguard can be toggled on and off.
Tested on a bare metal Kubernetes cluster. NAPI threading is enabled on the second pass of ensureLink, once the interface is up. I get operation not permitted on the first run before the up|peertopeer flags are set, which is why I have a flag guard.
This affects calico-node the most when it's configuring the wireguard interface. All other components are reconciling the new FelixConfiguration parameter.

Related issues/PRs
https://github.com/projectcalico/calico/issues/9223

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

Add setting to enable wireguard NAPI threading

Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one docs-* label.

docs-pr-required: This change requires a change to the documentation that has not been completed yet.
docs-completed: This change has all necessary documentation completed.
docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

release-note-required: This PR has user-facing changes. Most PRs should have this label.
release-note-not-required: This PR has no user-facing changes.

Other optional labels:

cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

/sem-approve

/sem-approve

Addressed comments and rebased to resolve a conflict.

/sem-approve

/sem-approve

/sem-approve

/sem-approve

/sem-approve

I think my local development is having an issue is this part of the E2E test, which is why I'm struggling to iterate on this test:
felix-0-127157-3-felixfv[stderr] docker: Error response from daemon: OCI runtime create failed: container_linux.go:377: starting container process caused: pr
ocess_linux.go:495: container init caused: rootfs_linux.go:76: mounting "/home/debian/calico/felix/bin/calico-felix-race-amd64" to rootfs at "/usr/local/bin/
calico-felix" caused: mount through procfd: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified
 host path exists and is the expected type.
felix-1-127157-2-felixfv[stderr] docker: Error response from daemon: OCI runtime create failed: container_linux.go:377: starting container process caused: pr
ocess_linux.go:495: container init caused: rootfs_linux.go:76: mounting "/home/debian/calico/felix/bin/calico-felix-race-amd64" to rootfs at "/usr/local/bin/
calico-felix" caused: mount through procfd: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified
 host path exists and is the expected type.

I have that file:
debian@devvm:~/calico/felix$ ls -l bin/calico-felix-race-amd64
-rwxr-xr-x 1 debian docker 149270288 Oct 16 21:35 bin/calico-felix-race-amd64
debian@devvm:~/calico/felix$

debian@devvm:~/calico/felix$ docker version
Client:
 Version:           20.10.5+dfsg1
 API version:       1.41
 Go version:        go1.15.15
 Git commit:        55c4c88
 Built:             Mon May 30 18:34:49 2022
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server:
 Engine:
  Version:          20.10.5+dfsg1
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.15.15
  Git commit:       363e9a8
  Built:            Mon May 30 18:34:49 2022
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.13~ds1
  GitCommit:        1.4.13~ds1-1~deb11u4
 runc:
  Version:          1.0.0~rc93+ds1
  GitCommit:        1.0.0~rc93+ds1-5+deb11u5
 docker-init:
  Version:          0.19.0
  GitCommit:

Should I use a different VM than Debian? What distro / version does CI run on?

@jrcichra yes, please try with Ubuntu.

Thanks @mazdakn I am able to run the wireguard e2e tests now with an Ubuntu 24.04 VM and docker + buildx + ipv6 networking enabled. I moved my test into a better location. I can confirm that in the E2E test the Apply() / ensureLink step is properly setting up the interface. Once the reconcile loop sets NAPI threading on my Eventually() test passes.
The only downside right now is increased E2E test duration. Since ensureLink sets wireguard NAPI threading once the wireguard link is up because that's the only time you can set NAPI threading, it slows down the E2E test. You'll see:
Creating Command [docker exec felix-0-149774-29-felixfv cat /sys/class/net/wg0/threaded]

for a bit until the reconcile loop sets NAPI threading. I'm not sure how to reduce that unless we modify how often ensureLink is executed or maybe trigger when the link status / flags are changed.
make fv GINKGO_FOCUS="the Wireguard device should be configurable" GINKGO_ARGS="-ginkgo.progress -ginkgo.v -ginkgo.failFast" |& tee fv.log

Ran 12 of 987 Specs in 790.061 seconds
SUCCESS! -- 12 Passed | 0 Failed | 0 Pending | 975 Skipped
PASS
+ status=0
+ echo 'Test batch 1 completed with status 0'
Test batch 1 completed with status 0
+ exit 0
+ st=0
+ echo 'Result: 0'
Result: 0
+ '[' 0 -ne 0 ']'
+ '[' 0 -eq 0 ']'
+ echo 'All tests passed'
All tests passed
make[1]: Leaving directory '/home/ubuntu/calico/felix'

Thanks again for walking me through this!

@jrcichra Yes, I think the execution time is going to rise dramatically. I think it's better to NOT double the number of test cases. Instead you can add a single test to the current tests cases. As an example, it's possible to set the value, wait until reading from disk return the correct value. You can switch back and forth the value, and it should be enough.

@jrcichra Thanks for the changes. I think we are getting close to merging this. I left few comments about the test setup. It feel moving the test changes into an independent test make it more clean.

/sem-approve

@jrcichra thanks for updates. The CI failed in the pre-flight test. You need to run make generate in the root directory of Calico to generate doc update for FelixConfiguration. This is a new tool we recently added.

@mazdakn thanks just rebased and generated those. I see this has the tag docs-not-required but I would like to include some docs for this change with its caveats. The performance increase from it is really great and it significantly increases the packets per second we can push through calico with wireguard enabled, but we have seen instances of complete NAPI lockups on older kernels during peer removal and I'd like to document that fact and the active investigation so users are aware if they decide to use this setting<EMAIL_ADDRESS>We've backported this patch into our kernels which at least unwedges the NAPI lock when we drain the node<EMAIL_ADDRESS>

/sem-approve

@mazdakn Added documentation for this feature here: https://github.com/tigera/docs/pull/1741

I don't believe that the latest CI failures are related to my change? https://tigera.semaphoreci.com/jobs/91a8c163-f4da-4366-bb1e-5869adaa0c07#L2599. I can rebase if it's a known issue.

/sem-approve

@jrcichra you need to rebase the change. One test failed which is not related to this PR, and it's already fix in the master branch.

/sem-approve

The CI failed in Win FV CAPZ which is a know issue and is not related to this PR.

@jrcichra Thanks for your contribution.

@jrcichra will you be able to cherry pick this PR to v3.29 and v3.28?

@jrcichra will you be able to cherry pick this PR to v3.29 and v3.28?

Sure, I'll make PRs for those.


Feature Request:  Make QVsToASCII from Consensus.h public

Currently I've simply copied the code, though it might be better to have a shared set of public utility functions like this

I think pbbam has some utility functions like this. We should work with Derek on a unified data model.

The function is available to anyone who imports the header no? It's a pretty standard conversion that's available in most parsing libraries as well.

Nope - the anonymous namespace limits it to the local translation unit.  I agree with Lance on this, though - a couple such functions are fundamental enough that it's worth pushing them as low in the stack as possible, and PbBam is the logical place.

sounds like this is an issue for PbBAM, can I close this?

No response, assuming is pbbam issue


nix profile install nixpkgs#bats fails with: pyyaml-6.0 not supported for interpreter python2.7

Describe the bug
nix profile install nixpkgs#bats fails with the error message:

pyyaml-6.0 not supported for interpreter python2.7

Steps To Reproduce
Steps to reproduce the behavior:

nix profile install nixpkgs#bats

Expected behavior
install bats
Screenshots

nix profile install nixpkgs#bats --show-trace
error: pyyaml-6.0 not supported for interpreter python2.7

       … while evaluating anonymous lambda

       at /nix/store/8dy3nx5wi65gg4ns0h80pw2v1llghx6h-source/pkgs/development/interpreters/python/mk-python-derivation.nix:31:1:

           30|
           31| { name ? "${attrs.pname}-${attrs.version}"
             | ^
           32|

       … from call site

       at /nix/store/8dy3nx5wi65gg4ns0h80pw2v1llghx6h-source/lib/customisation.nix:72:16:

           71|     let
           72|       result = f origArgs;
             |                ^
           73|

       … while evaluating 'makeOverridable'

       at /nix/store/8dy3nx5wi65gg4ns0h80pw2v1llghx6h-source/lib/customisation.nix:70:24:

           69|   */
           70|   makeOverridable = f: origArgs:
             |                        ^
           71|     let

       … from call site

       at /nix/store/8dy3nx5wi65gg4ns0h80pw2v1llghx6h-source/pkgs/development/interpreters/python/python-packages-base.nix:19:12:

           18|     let
           19|       ff = f origArgs;
             |            ^
           20|       overrideWith = newArgs: origArgs // (if pkgs.lib.isFunction newArgs then newArgs origArgs else newArgs);

       … while evaluating 'makeOverridablePythonPackage'

       at /nix/store/8dy3nx5wi65gg4ns0h80pw2v1llghx6h-source/pkgs/development/interpreters/python/python-packages-base.nix:17:37:

           16|   # This function introduces `overridePythonAttrs` and it overrides the call to `buildPythonPackage`.
           17|   makeOverridablePythonPackage = f: origArgs:
             |                                     ^
           18|     let

       … from call site

       at /nix/store/8dy3nx5wi65gg4ns0h80pw2v1llghx6h-source/pkgs/development/python-modules/pyyaml/default.nix:10:1:

            9|
           10| buildPythonPackage rec {
             | ^
           11|   pname = "pyyaml";

       … while evaluating anonymous lambda

       at /nix/store/8dy3nx5wi65gg4ns0h80pw2v1llghx6h-source/pkgs/development/python-modules/pyyaml/default.nix:1:1:

            1| { lib
             | ^
            2| , buildPythonPackage

       … from call site

       at /nix/store/8dy3nx5wi65gg4ns0h80pw2v1llghx6h-source/lib/customisation.nix:72:16:

           71|     let
           72|       result = f origArgs;
             |                ^
           73|

       … while evaluating 'makeOverridable'

       at /nix/store/8dy3nx5wi65gg4ns0h80pw2v1llghx6h-source/lib/customisation.nix:70:24:

           69|   */
           70|   makeOverridable = f: origArgs:
             |                        ^
           71|     let

       … from call site

       at /nix/store/8dy3nx5wi65gg4ns0h80pw2v1llghx6h-source/lib/customisation.nix:171:34:

          170|
          171|     in if missingArgs == [] then makeOverridable f allArgs else throw error;
             |                                  ^
          172|

       … while evaluating 'callPackageWith'

       at /nix/store/8dy3nx5wi65gg4ns0h80pw2v1llghx6h-source/lib/customisation.nix:120:35:

          119|   */
          120|   callPackageWith = autoArgs: fn: args:
             |                                   ^
          121|     let

       … from call site

       at /nix/store/8dy3nx5wi65gg4ns0h80pw2v1llghx6h-source/pkgs/top-level/python-packages.nix:9475:12:

         9474|
         9475|   pyyaml = callPackage ../development/python-modules/pyyaml { };
             |            ^
         9476|

       … while evaluating anonymous lambda

       at /nix/store/8dy3nx5wi65gg4ns0h80pw2v1llghx6h-source/pkgs/stdenv/generic/make-derivation.nix:212:13:

          211|       (map (drv: drv.__spliced.buildBuild or drv) (checkDependencyList "depsBuildBuild" depsBuildBuild))
          212|       (map (drv: drv.__spliced.buildHost or drv) (checkDependencyList "nativeBuildInputs" nativeBuildInputs
             |             ^
          213|          ++ lib.optional separateDebugInfo' ../../build-support/setup-hooks/separate-debug-info.sh

       … from call site

       … while evaluating 'getOutput'

       at /nix/store/8dy3nx5wi65gg4ns0h80pw2v1llghx6h-source/lib/attrsets.nix:825:23:

          824|   */
          825|   getOutput = output: pkg:
             |                       ^
          826|     if ! pkg ? outputSpecified || ! pkg.outputSpecified

       … from call site

       … while evaluating the attribute 'nativeBuildInputs' of the derivation 'python2.7-configargparse-1.5.3'

       at /nix/store/8dy3nx5wi65gg4ns0h80pw2v1llghx6h-source/pkgs/stdenv/generic/make-derivation.nix:270:7:

          269|     // (lib.optionalAttrs (attrs ? name || (attrs ? pname && attrs ? version)) {
          270|       name =
             |       ^
          271|         let

       … while evaluating the attribute 'out.outPath'

       at /nix/store/8dy3nx5wi65gg4ns0h80pw2v1llghx6h-source/lib/customisation.nix:207:13:

          206|             drvPath = assert condition; drv.${outputName}.drvPath;
          207|             outPath = assert condition; drv.${outputName}.outPath;
             |             ^
          208|           };

       … while evaluating the attribute 'propagatedBuildInputs' of the derivation 'resholve-0.8.3'

       at /nix/store/8dy3nx5wi65gg4ns0h80pw2v1llghx6h-source/pkgs/stdenv/generic/make-derivation.nix:270:7:

          269|     // (lib.optionalAttrs (attrs ? name || (attrs ? pname && attrs ? version)) {
          270|       name =
             |       ^
          271|         let

       … while evaluating the attribute 'out.outPath'

       at /nix/store/8dy3nx5wi65gg4ns0h80pw2v1llghx6h-source/lib/customisation.nix:207:13:

          206|             drvPath = assert condition; drv.${outputName}.drvPath;
          207|             outPath = assert condition; drv.${outputName}.outPath;
             |             ^
          208|           };

       … while evaluating the attribute 'buildInputs' of the derivation 'bats-1.8.2'

       at /nix/store/8dy3nx5wi65gg4ns0h80pw2v1llghx6h-source/pkgs/stdenv/generic/make-derivation.nix:270:7:

          269|     // (lib.optionalAttrs (attrs ? name || (attrs ? pname && attrs ? version)) {
          270|       name =
             |       ^
          271|         let

       … while evaluating the attribute 'drvPath'

       at /nix/store/8dy3nx5wi65gg4ns0h80pw2v1llghx6h-source/lib/customisation.nix:213:7:

          212|     in commonAttrs // {
          213|       drvPath = assert condition; drv.drvPath;
             |       ^
          214|       outPath = assert condition; drv.outPath;

Additional context
upgrading bats fails with the same error (assuming one had installed it before)
Notify maintainers
n.a.
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.0.11-arch1-1, Arch Linux, noversion, rolling`
 - multi-user?: `no`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.11.1`
 - channels(mkhl): `"nixpkgs"`
 - nixpkgs: `/home/mkhl/.nix-defexpr/channels/nixpkgs`

This will be fixed by https://github.com/NixOS/nixpkgs/pull/205387


Remove deprecated usages of Buffer constructor

new Buffer(string, [encoding]) is deprecated in newer JS code & NodeJS, so this switches to use Buffer.from instead. This makes the tests less noisy.

Thanks :)


Orchestrator Integrity Check: Internal Links in Descriptions

@jamesrwelch - As discussed, I retired an existing Data Element PATIENT DIAGNOSIS INDICATOR (DEMENTIA) in CR8008:

In the Orchestrator, the Integrity Check: Internal Links in Descriptions is showing that there is an issue with internal links to other dictionary items:

When checking the item, there doesn't appear to be an issue.
The text, in reality, should be the retired text so we wouldn't want to update it.

Can the Orchestrator be updated so it doesn't look for links in retired items?
If not, we could have a lot to go through as when retiring a data set there could be a lot of Data Elements that have to be retired.

@jamesrwelch - as discussed this morning, these are the Integrity Checks that are no longer required:

Classes Linked to Retired Attributes
Attributes linked to a class
All items are within their validity date

And these are the possible new Integrity Checks required:

Identify newly retired items in the branch, i.e. those that have "The last live version of this item is available in the ?????? release of the NHS Data Model and Dictionary." in the text
Live Attributes / Data Elements where all codes have been retired
Live Data Elements linked to retired Attributes


XGBoost4J: Exporting to, then importing a model from stream results in wrong model format exception

Hi there!
I'm currently having issues with exporting and importing an XGBoost model to/from a Stream. I export the model to a ByteArrayOutputStream with the saveModel method on ml.dmlc.xgboost4j.java.Booster :
https://github.com/dmlc/xgboost/blob/3f38d983a671632bfb0dbdcdead6f2aa408a06f2/jvm-packages/xgboost4j/src/main/java/ml/dmlc/xgboost4j/java/Booster.java#L393-L396
At a later point i try to import the previously exported model again from an InputStream using the loadModel method on ml.dmlc.xgboost4j.java.XGBoost:
https://github.com/dmlc/xgboost/blob/3f38d983a671632bfb0dbdcdead6f2aa408a06f2/jvm-packages/xgboost4j/src/main/java/ml/dmlc/xgboost4j/java/XGBoost.java#L56-L65
Altough the Stream contains the exact same data the import fails with the following exception:
Caused by: ml.dmlc.xgboost4j.java.XGBoostError: [16:24:54] D:\a\xgboost\xgboost\src\learner.cc:785: Check failed: fi->Read(&tparam_.objective): BoostLearner: wrong model format
	at ml.dmlc.xgboost4j.java.XGBoostJNI.checkCall(XGBoostJNI.java:48)
	at ml.dmlc.xgboost4j.java.Booster.loadModel(Booster.java:81)
	at ml.dmlc.xgboost4j.java.XGBoost.loadModel(XGBoost.java:64)
	...

I recently upgraded from version 1.3.1 to 1.4.1. I never encountered this problem with version 1.3.1. I noticed an entry in the changelog mentioning changes to the export/importing of models ([jvm] Add ability to load booster direct from byte array (#6655)). Might i be using the new API wrong?
Library version: XGBoost4J 1.4.1

I think this might be relevant? https://github.com/dmlc/xgboost/pull/7067

I think this might be relevant? #7067

I can confirm the mentioned pull request solves my issue. Thanks for your quick response!


Linting

As stated in 3 other PRs, i am handling the versioning of dependencies but this commit looks good, i will check it out when im on my pc again

Thanks!

Sorry to ask here, but why do you want to manage your package only with dependabot? Looking at the PR, it looks like dependabot won't submit the PR even though have a newer version.

I manage it manually, whenever i release smt, i don't want to release a new version just because of a dependency update, i connected dependabot to retrieve notifications for vulnarabilities in case some happen

If you don't want to release a new version because of the package, you can just not release it and release it when new features come out
Anyway, I see.


FootBar UI-UX Improvment

Is your feature request related to a problem? Please describe.
Your Website is Good but , the Footbar looks very simple and not eye catching and appeling to other people.
Describe the solution you'd like
I can improve the Footbar using Animations and Cool Stuff , so people will more eager to use your website
Additional context

@Priyaaa1 please assign this issue to me under Gssoc24

@Priyaaa1 please assign asap under gssoc24 with labels


Update README.md

The current list of contributors is 'static'. If we link it to the contributors on the website, it will be 'dynamic'.
Update the list of contributors, and link it to the contributors' webpage on the Flow website (so it's always updated)

Pull Request Test Coverage Report for Build 3089

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 89.372%

Totals

Change from base Build 3086:
0.01%

Covered Lines:
7753

Relevant Lines:
8675

💛  - Coveralls


How to generate images from custom captions, using the pre-trained model?

In the eval_coco.yml or eval_bird.yml set B_VALIDATION to FALSE.
Then use the command for generating images in validation stage.


RFC: Slow network / local rate limit HTTP filter

At Lyft we have a desire to build a slow network simulation system. This would allow debug versions of our applications to request various slow network profiles, without requiring attachment to a special access point, emulator, etc.
Our plan is to do this via a new HTTP filter that has roughly the following capabilities:

Allow latency injection in both the downstream and upstream direction.
Allow throughput limiting in both the downstream and upstream direction.
Allow variable throughput/latency stability via randomness (to simulate spotty networks).

We would like to allow this via fixed configuration / xDS, but also, optionally, via request headers along the lines of:
x-envoy-throttle-upstream-throughput: int (kilobytes)
x-envoy-throttle-downstream-throughput: int (kilobytes)
x-envoy-throttle-network-stability: int (percentage between 0 and 100)
x-envoy-throttle-latency: int (milliseconds)
x-envoy-throttle-throughput-stability: int (percentage between 0 and 100)

Potentially we would also offer pre-canned profiles, configurable via both static config and request headers such as:
x-envoy-throttle-profile: {“no-connection”, “EDGE”, “3G”, “LTE”}

In general, this code will not be difficult to write. There are some additional safety knobs we will need around max concurrent throttled requests, runtime disable, etc.
One thing to consider is whether this should be a new filter, or if we should build this functionality into the existing HTTP fault filter. My inclination is to build a new filter, but there is enough overlap that it might make sense to build this into the existing HTTP fault filter so I'm curious to hear everyone's opinion.
@envoyproxy/maintainers @rshriram @lita @Reflejo  @goaway

No opinion on which filter this goes in, but just one thought which is this seems like an L7 filter doing L4 work.  Are we planning on doing any enforcement if one stream on a connection asks for 3G semantics and another requests LTE, or just assume that since this is mainly for test purposes, it's on the operator to have proper client enforcement and just have the last update take precedence?

Are we planning on doing any enforcement if one stream on a connection asks for 3G semantics and another requests LTE, or just assume that since this is mainly for test purposes, it's on the operator to have proper client enforcement and just have the last update take precedence?

My feeling initially is that it's up to the operator. Really the only reason that we propose doing this at the HTTP layer is so that the client can drive the test profile via headers. There isn't any good way to do this at L4 unless we build a proprietary prefix protocol (send some proto before any other data that is then stripped) which I suspect would be substantially more effort for most client implementations.

1 is useful, though I believe Roman setup Lyft fault filters in the
downstream path using the ingress listener.
On 2/3 - One of the reasons I had initially dumbed the http fault filter to
discrete delays instead of a throughput constrained model was because of
the fact that at application layer (python requests, java lib, etc), these
two are indistinguishable. Http is a message oriented protocol. A message
that arrives late is same as a message that slowly trickles in, because the
app only processes things at message boundaries.
It would make sense to build a controller in the fault filter that
dynamically adapted the delays injected per outbound request, to simulate
things like long fat pipes, etc. (assuming app is sending multiple requests
per upstream, instead of a ping pong model). Essentially a stateful fault
injection filter that kept track of a pseudo session and injected variable
(or distribution driven) delay in requests in that session.
If you are talking about tcp proxy, then 2/3 would be great.
On Wed, Feb 13, 2019 at 1:36 PM Matt Klein<EMAIL_ADDRESS>wrote:

At Lyft we have a desire to build a slow network simulation system. This
would allow debug versions of our applications to request various slow
network profiles, without requiring attachment to a special access point,
emulator, etc.
Our plan is to do this via a new HTTP filter that has roughly the
following capabilities:

Allow latency injection in both the downstream and upstream
direction.
Allow throughput limiting in both the downstream and upstream
direction.
Allow variable throughput/latency stability via randomness (to
simulate spotty networks).

We would like to allow this via fixed configuration / xDS, but also,
optionally, via request headers along the lines of:
x-envoy-throttle-upstream-throughput: int (kilobytes)
x-envoy-throttle-downstream-throughput: int (kilobytes)
x-envoy-throttle-network-stability: int (percentage between 0 and 100)
x-envoy-throttle-latency: int (milliseconds)
x-envoy-throttle-throughput-stability: int (percentage between 0 and 100)
Potentially we would also offer pre-canned profiles, configurable via both
static config and request headers such as:
x-envoy-throttle-profile: {“no-connection”, “EDGE”, “3G”, “LTE”}
In general, this code will not be difficult to write. There are some
additional safety knobs we will need around max concurrent throttled
requests, runtime disable, etc.
One thing to consider is whether this should be a new filter, or if we
should build this functionality into the existing HTTP fault filter. My
inclination is to build a new filter, but there is enough overlap that it
might make sense to build this into the existing HTTP fault filter so I'm
curious to hear everyone's opinion.
@envoyproxy/maintainers
https://github.com/orgs/envoyproxy/teams/maintainers @rshriram
https://github.com/rshriram @lita https://github.com/lita @Reflejo
https://github.com/Reflejo @goaway https://github.com/goaway
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/envoyproxy/envoy/issues/5942, or mute the thread
https://github.com/notifications/unsubscribe-auth/AH0qd9wTUtC7xaN4JRcytAmFYUs752WEks5vNFtIgaJpZM4a6BNg
.

@rshriram we are definitely going to build all this functionality (I agree that in many cases for a message oriented exchange, latency is all that matters, but for a progressive download even over HTTP it might not always be the case). The question is where to build it. I think you are saying you would like this as part of the fault filter? If so that's fine with me.

It seems like x-envoy-throttle-latency: int (milliseconds) should be controlled independently for upstream/downstream. This is more consistent with the other related parameters and allows for a little more flexibility.

It seems like x-envoy-throttle-latency: int (milliseconds) should be controlled independently for upstream/downstream. This is more consistent with the other related parameters and allows for a little more flexibility.

ACK, I agree we should split this (and all other settings) into independent upstream/downstream options.

Note that I think we also want response headers that are set when a throttling profile in place. Thus, if the throttling is user driven the client can adjust UI, etc. accordingly. I will think more about this and update the spec.

@mattklein123 Hi Matt!
I've noticed that in order to support rate limiting at HTTP level you added new methods to StreamDecoderFilterCallbacks/StreamEncoderFilterCallbacks, namely,

StreamDecoderFilterCallbacks::injectDecodedDataToFilterChain(data, end_stream)
StreamEncoderFilterCallbacks::injectEncodedDataToFilterChain(data, end_stream).

Do I understand correctly that adding rate limiting at L4 would require similar changes to ReadFilterCallbacks/WriteFilterCallbacks ? Let's say

ReadFilterCallbacks::continueReading(data, end_stream)
WriteFilterCallbacks::continueWriting(data, end_stream)

Do you have any plans to extend ReadFilterCallbacks/WriteFilterCallbacks this way ?
Is it a good place to contribute ? Or do you see any blockers for that ?

@yskopets I think doing an L4 rate limiting filter would be a lot simpler since the filter manager is a lot simpler. I'm pretty sure it could be built with the existing APIs.

Going to close this out. We can track enhancements as new feature requests.


updated torbrowser (5.5.4)

Thank you for the contribution. It was merged directly as 1be603e612ba505626f80a8cced0fee433d4e9a8 to keep commit history cleaner. Your contribution is still credited to you.


New function of tryCatch

Is your feature request related to a problem? Please describe.
try catch statement for function

:tada: This issue has been resolved in version 1.8.0-beta.2 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.8.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Preset for IBM 1.2 MB 5.25 disks

I would like to write 1.2 MB 5.25 IBM disks but I cannot figure out the correct parameters to set.
Can a preset like --ibm-preset-1440 be added but for this kind of disks?

Belatedly: yes. Except that my 5.25" drive is broken and even then I have no hardware to test the written disks on!

Belatedly: yes. Except that my 5.25" drive is broken and even then I have no hardware to test the written disks on!

David,
Would a donation of a working drive help?
What would good defaults for a 1.2MB 5.25” and a 360kB 5.25” IBM floppy be?
As a side note, I have a completed and (mostly) working fluxengine, using a
Raspberry Pi 4 as the client host, installed in a chassis intended for
SATA/SAS hard drive copying and erasing. I’ll post some pictures, if anyone
is interested.
Thanks!

Alex

On Mon, Jan 18, 2021 at 14:34 David Given<EMAIL_ADDRESS>wrote:

Belatedly: yes. Except that my 5.25" drive is broken and even then I have
no hardware to test the written disks on!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/davidgiven/fluxengine/issues/189#issuecomment-762436176,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFLVO4WVJXKGMC3CPUEGMZLS2SEKLANCNFSM4R6KNH3A
.

--
Alexander Jacocks, RHCE           | Staff Solution Architect
(e<EMAIL_ADDRESS>        | Public Sector Business Development
(c)<PHONE_NUMBER>                | Tyson's Corner, VA
(g) CC28 8136 C253 907A B9BB  9EEA D3C8 1A3A 790A 0AB9

David,
Would a donation of a working drive help?
What would good defaults for a 1.2MB 5.25” and a 360kB 5.25” IBM floppy be?
As a side note, I have a completed and (mostly) working fluxengine, using a
Raspberry Pi 4 as the client host, installed in a chassis intended for
SATA/SAS hard drive copying and erasing. I’ll post some pictures, if anyone
is interested.
Thanks!

Alex

On Mon, Jan 18, 2021 at 14:34 David Given<EMAIL_ADDRESS>wrote:

Belatedly: yes. Except that my 5.25" drive is broken and even then I have
no hardware to test the written disks on!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/davidgiven/fluxengine/issues/189#issuecomment-762436176,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFLVO4WVJXKGMC3CPUEGMZLS2SEKLANCNFSM4R6KNH3A
.

--
Alexander Jacocks, RHCE           | Staff Solution Architect
(e<EMAIL_ADDRESS>        | Public Sector Business Development
(c)<PHONE_NUMBER>                | Tyson's Corner, VA
(g) CC28 8136 C253 907A B9BB  9EEA D3C8 1A3A 790A 0AB9

@ajacocks I am interested in your pictures & chassis model (though perhaps in a different issue, so we don't misuse this issue). :D

@ajacocks I am interested in your pictures & chassis model (though perhaps in a different issue, so we don't misuse this issue). :D

I'm on the lookout for a 5.25" drive, but they're hard to find for any reasonable sum in Switzlerland. Maybe it's possible to repair the drives I currently have, although how to do this without wrecking the track alignment is a concern. There is a computer recycling place that has lots of old hardware... which is current closed for lockdown reasons.
BTW, regarding a chassis: I have my drives in a full-height tape drive external enclosure. Turns out that a full height drive is not the same size as two half height drives.

I'm on the lookout for a 5.25" drive, but they're hard to find for any reasonable sum in Switzlerland. Maybe it's possible to repair the drives I currently have, although how to do this without wrecking the track alignment is a concern. There is a computer recycling place that has lots of old hardware... which is current closed for lockdown reasons.
BTW, regarding a chassis: I have my drives in a full-height tape drive external enclosure. Turns out that a full height drive is not the same size as two half height drives.


Per instance configuration

Hi @kernow,
Quick question: Is there any way to have different setups per processor / parser instance?
I can see that currently it is loading the configuration directly from the Shortcode class.
For example:
  rule(:block_tag)        { match_any_of Shortcode.configuration.block_tags }
  rule(:self_closing_tag) { match_any_of Shortcode.configuration.self_closing_tags }

Unfortunately not without rewriting the code to invoke an instance of Shortcode rather than using a singleton pattern for the main object.
Do you want to have the same shortcode tags handled differently within the same app?

Yes. That's what i need right now. Would you be open to launch a new release if I manage to keep the singleton functionality as default but be able to inject a configuration instance in the classes that use it?

Should be resolved by https://github.com/kernow/shortcode/pull/45


Failed to launch Emulator_da: Emulator didn't connect within 60 seconds

I have just created a new Flutter project and it's showing me this error.
I have been facing this error for a long time now.
To fix this, I have to go to Android Studio every single time I want to run the Emulator, and then wipe the data.
I need a clear solution so I can run the Emulator without having to back to Android Studio every single time to wipe the data.
When I ran "flutter doctor" and "flutter doctor -v", I found that I have no issues.
Please help...

Hi @PinskyLabs
Android emulator isn't part of Flutter, the error you mention also reproduces without Flutter, based on my search.
Make sure you've updated your Android Studio and emulator in your SDK manager
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


updateSampleInfo not loading files correctly - can't updateGeneInfo

Hi!
I am trying to see if I can analyze proteomics data. I am having problems updating the pyWGCNA sample info.
I load the sample info, but the structure of pyWGCNA.datExpr.obs is different than the one you get from the tutorial:

the sample_id is loading incorrectly.
Then, I am updating the GeneInfo by first getting my gene list as followed:
geneList = PyWGCNA.getGeneList(dataset='hsapiens_gene_ensembl',                                attributes=['uniprotswissprot',                                             'external_gene_name',                                             'gene_biotype'],                                maps=['prot_name', 'gene_name', 'gene_biotype'])
I can see a geneList similarly to that from the tutorial, but pyWGCNA.updateGeneInfo(geneList) has an indexing error.

Do you think this is an issue getting the gene list from BioMart?
Hopefully you can help me!
Thank you

Hi @franjmt
I would assume if you request the same thing directly from ensemble website, you probably get the same table.
My other assumption is that if you change the order of the attributes, will it affect the output? maybe the values of other columns with the same index are different...
I could add a line of code at the end to basically unique the indexes but I prefer to keep the raw input from the ensemble website and the user will be responsible for making sure to pass the write input to the updateGeneInfo() function.


Rename table trigger to table update trigger

Changes
Rename table trigger to table update trigger.
The decision was takes during the table trigger final UX review.
This is the design doc for reference.
Tests

[X] make test passing
[X] make fmt applied
[X] (existing) relevant integration tests applied

@sebastien-db
I will probably generate it tomorrow. If you want this change to be in the cut, you need to update the proto definition here
https://github.com/databricks/universe/blob/54d48ce455bf2fb6b5f11b831b8365f9d070e1ff/elastic-spark-common/api/messages/triggers.proto#L77-L81
message TableTriggerConfiguration {
  option (databricks.openapi.message).openapi_name = "TableUpdateTriggerConfiguration";
  // A list of Delta tables to monitor for changes. The table name must be in the format `catalog_name.schema_name.table_name`.
  repeated string table_names = 1;


need team eyes/blessing on new opennews blurb

This is now at the top of the homepage, so I want to explicitly request a team review on it:

OpenNews is a joint project of Mozilla and the Knight Foundation dedicated to helping journalism thrive on the open web by supporting the international community of developers, designers, and data journalists in newsrooms.

Note: I'm using "joint project" instead of "partnership" because although the latter is accurate, it's a weird as the main noun defining OpenNews.

questions that jump out at me:
international (as a defining part of the program description) y/n?
and, newsrooms seems a little narrow. possible edits:

in journalism (though that says journalism twice in one sentence)
in and around journalism (clunky)

OpenNews is a joint project of Mozilla and the Knight Foundation dedicated to helping journalism thrive on the open web by supporting the community of developers, designers, and data journalists in and around newsrooms.

?

how about just in and around newsrooms

"OpenNews is a joint project of Mozilla and the Knight Foundation that helps journalism thrive on the open web by supporting the community of developers, designers, and data journalists."

OpenNews is a joint project of Mozilla and the Knight Foundation that helps journalism thrive on the open web by supporting the vibrant community of developers, designers, and data journalists.
or some other adjective
?

"growing" maybe feels like the expected word, but it is also a true word

I will admit that I added and then removed "vibrant" days ago because it felt a little copywriting-y. "Growing" seems accurate and good, if expected.
It's a little conceptually weird to not have anything after "developers, designers, and data journalists" though, right? Because we're not supporting all developers and designers. I mean, no one will be confused, but if this is gonna be front and center, I want to make it as watertight as possible.
What about:

OpenNews is a joint project of Mozilla and the Knight Foundation that helps journalism thrive on the open web by supporting the vibrant community of news developers and data journalists.

I like how tight that is. I still think "vibrant" maybe sounds copywrite-y though :/

I'm OK with "growing"
On Thu, Jan 15, 2015 at 3:45 PM, Ryan Pitts<EMAIL_ADDRESS>wrote:

I like how tight that is. I still think "vibrant" maybe sounds copywrite-y
though :/
—
Reply to this email directly or view it on GitHub
https://github.com/mozilla/mozilla-opennews/issues/203#issuecomment-70184681
.

i also like how tight that is, but...
do we care about
losing designer as a separate group from developer?
AND
the fact that data journalist is super broad and can mean excel driven reporting?

Oh god, "vibrant" was all cold pills, I meant to write "growing."
We don't really talk much about designers on the site now, so IDK—I liked having it in, but I dunno if I care about losing it. I feel more strongly that it's cool to go big-tent with the data journalists, since a ton of the Source Learning stuff is super helpful for even the CAR-iest people.

More:

OpenNews is a joint project of Mozilla and the Knight Foundation that helps journalism thrive on the open web by supporting the growing community of news developers, designers, and data-wranglers.

or

OpenNews is a joint project of Mozilla and the Knight Foundation that helps journalism thrive on the open web by supporting developers, designers, and data nerds in and around newsrooms.

I like the "growing community" version, will integrate.

this is blessed and added in #223. closing.


Error with Private Producers

System Health details
N/A
Checklist

[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of any previous issues..

Describe the issue
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 354, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/iec/coordinator.py", line 377, in _async_update_data
    last_meter_read = int(devices_by_id.counter_devices[0].last_mr)
                          ~~~~~~~~~~~^^^
TypeError: 'NoneType' object is not subscriptable

Reproduction steps

Start HA with private producers

Debug logs
When calling https://iecapi.iec.co.il/api/Device/{{contract_id}}/{{device_id}} with a private producer - you get:

{
    "data": {
        "counterDevices": null,
        "mrType": "00"
    },
    "reponseDescriptor": {
        "isSuccess": false,
        "code": "07",
        "description": "No authorization for this type of product: Private Producer"
    }
}

So you can't extract last_meter_read

### Diagnostics dump

_No response_

@GuyKh
I am happy to help with debugging this, let me know what you need :)

Sovled with #146


updated notebook

Codecov Report

Merging #39 (52126a0) into master (6c5cba1) will increase coverage by 0.11%.
The diff coverage is n/a.

:exclamation: Current head 52126a0 differs from pull request most recent head 3d203f6. Consider uploading reports for the commit 3d203f6 to get more accurate results

@@            Coverage Diff             @@
##           master      #39      +/-   ##
==========================================
+ Coverage   73.13%   73.25%   +0.11%
==========================================
  Files          13       13
  Lines        1236     1234       -2
  Branches      234      233       -1
==========================================
  Hits          904      904
+ Misses        290      288       -2
  Partials       42       42

Flag
Coverage Δ

unittests
73.25% <ø> (+0.11%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

thingsvision/model_class.py
70.68% <0.00%> (+0.73%)
:arrow_up:

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 6c5cba1...3d203f6. Read the comment docs.


the usage of nuScenes dataset

Hi, author.
I want to know how much nuScenes data (full dataset v1.0) do you use for centerpoint training and validation and construct the following directory?
Taking 'samples' directory for example, only one subset blob data, e.g. v1.0-trainval01_blobs, is used in the directory 'samples', or the data in different samples directories are extracted from several blobs, e.g. v1.0-trainval01_blobs and v1.0-trainval02_blobs, and then get them together to form a new 'samples' directory?

it has been a long time since I downloaded the data. But I use the whole dataset so it is probably all the blobs file.


python311Packages.gymnasium: temporarily disable pygame-related tests

Description of changes
pygame is currently broken which causes gymnasium to fail.
As it is not a core dependency of gymnasium (only used for testing) I suggest to temporarily disable those tests.
Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 293194 run on x86_64-linux 1

2 packages failed to build:

python311Packages.torchrl
python311Packages.torchrl.dist

4 packages built:

python311Packages.gymnasium
python311Packages.gymnasium.dist
python311Packages.skrl
python311Packages.skrl.dist

pygame build should be fixed with #293361


Add UML

Please check out the UML Diagram and approve it

For 'Vibe' Class, you have an emotion attribute which is an Emotion object, but beneath it you have a connection to an 'Emoticon' class which doesn't have anything? Also EmotionalState class is just kinda floating by the MainActivity class

Good catch, I updated it

Merged, and Mohammad also took a look at the UML so it wasn't just me who reviewed it.


Update README

Consolidate install instructions.
It removes some redundant information (several sudo dlite install) and adds some more information

:+1:


yte v1.3.0

This adds the missing dpath dependency and updates to v1.3.0.

Hi! This is the friendly automated conda-forge-webservice.
It appears you are making a pull request from a branch in your feedstock and not a fork. This procedure will generate a separate build for each push to the branch and is thus not allowed. See our documentation for more details.
Please close this pull request and remake it from a fork of this feedstock.
Have a great day!

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Add default .scala-steward.conf for Scala Steward itself

In some scenarios there is a need to limit dependencies you want to update for all repos.
Currently you'd need to update repo configuration (.scala-steward.conf) for every project you are working on.
If the repo doesn't have configuration (maybeRepoConfig) it will fallback to empty RepoConfig.default.
This PR is adding ability to override fallback to RepoConfig.default by reading .scala-steward.conf within main scala steward repo. It gives you all the features as described in repo-specific-configuration.md
Specifically, you can limit dependencies by providing allow settings (which is helpful if you have 100+ repos and you want to propagate specific dependencies, only)
Changes

Added --repos-default-conf setting (default to .scala-steward.conf)
Chain of configuration: check repoConf ($repo/.scala-steward.conf) => fallback to reposDefaultConf (root/.scala-steward.conf) => fallback to empty configuration
Added extra tests

I really like this idea and it will solve #1470.
Have you had a look how difficult it is to merge local configuration with global one ?
So that in the case of an available local configuration it would override the global one ?
The only minor comment I have after going through the PR is that the default global scala-teward.conf you are referencing in the docs and examples start with a dot. Which would hide i. I would prefer "default.scala-teward.conf" or "global.scala-teward.conf"

@mzuehlke thanks for feedback
I think it could be nice continuation of this feature (I see some complexity with "mergeability" for some settings, see below)
Seems so far we have allow / ignore / pin options to be merged, rest should be just repo (local) over global:

Allow - I'd vote for superset since each project knows which the only repos it want to get, and each steward knows which dependencies it wants to operate.
In case of different combinations of artifact, artifact / module, artifact / module / revision we should pick the most restrictive one.
If one of Local / global settings are empty, just pick another one.

Ignore - union

pin - union with Local preference in terms of revision

At the same time, let me rename config to be global.scala-steward.conf, makes sense

Thanks for the detailed investigation. Sound feasible.
But I'm totally fine with doing this in a follow up PR.

@mzuehlke updated

Thanks @eugeniyk
I have no possibility to approve or merge.
This is up to @fthomas

Author of #1470 here. Looks like this will solve that issue. Just wanted to reach out to say thank you for this PR/contribution. ❤

@eugeniyk Btw, you can fix the formatting by running sbt fmt.

I actually fix formatted version ;)

@fthomas you have quite advanced defence here: wart, fmt, codacy ;)

Wow, this PR also solves our use-case in https://github.com/fthomas/scala-steward/issues/1411 , this is awesome. Thanks @eugeniyk


Update material3 with built-in insets support

Feedback for updated insets support in https://issuetracker.google.com/issues/243713323

You'll need to rebase onto main before merging because of the lintDebug issue.

I was looking to apply changes here to one of my own projects and noticed change in color of bottom bar after making it.....seems like same difference with NowInAndroid app (with these changes)....not sure if intentional?

That's very odd, why would the colors change after changing some inset-related code?
Does it by any chance have to do with the new androidxComposeMaterial3 dependency bump instead? Have you found out what exactly is it that changes the colors?

I think it's related to removal of Surface(color = MaterialTheme.colorScheme.surface)

I think it's related to removal of Surface(color = MaterialTheme.colorScheme.surface)

Yup that was the reason. Consulting with our designs, I've updated to match the style we want here. @dturner and @ricknout please take another look!


Chore/cleanup setup

Align setup with other similar repositories:

Add docker image entrypoint
Use project name as GitHub Packages publishing maven repository

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


final draft 1

Major changes since the last pull request, code comments should explain code functionality.

Looks like Rodrigo's concern about variable security is all taken care of by Google. You can't select anything via the console through Google's layers of abstraction!


Packet integrity error and  Authentication failure

Hi, I am trying your plugin on Windows 8.1 and when I try to login using ssh key with config
{
  "type": "sftp",
  "host": "myhost",
  "user": "me",
  "port": "22",
  "remote_path": "/path/to/folder",
  "ssh_key_file": "path/to/ssh"
}

but I get error "Disconnected by host (PROTOCOL_ERROR): Packet integrity error."
If I try to log in using  password
{
  "type": "sftp",
  "host": "myhost",
  "user": "me",
  "password": "password"
  "port": "22",
  "remote_path": "/path/to/folder",
  "ssh_key_file": "path/to/ssh"
}

Then I get error "Authentication failure. Available authentication methods: publickey,keyboard-interactive"
What am I doing wrong?

Trudko said:

Hi, I am trying your plugin on Windows 8.1 and when I try to login using ssh key with config
{
"type": "sftp",
"host": "myhost",
"user": "me",
"port": "22",
"remote_path": "/path/to/folder",
"ssh_key_file": "path/to/ssh"
}
but I get error "Disconnected by host (PROTOCOL_ERROR): Packet integrity error."

Same Problem on Windows 7 and MacOSX 10.10.2 after Updating node from 0.10.x to 0.12.
Any ideas?

Hi guys,
Sorry for the long period of inactivity.
We are currently working on a new version : better code, more stable, and bug fixes.
I will note that bug and see it after the next release (1.1.0).
Thank you for using our work ! :)

Hi guys,
This problem is still alive ?
My previous work should have corrected it.


TOP blockchain support

Description
add TOP blockchain.  http://developers.topnetwork.org/en/
Testing instructions
unit test. TopAddress*, TopSigner*, TopTransaction*, TWAnySignerTop*, TWTopCoinType*
Types of changes
New feature (non-breaking change which adds functionality)
Checklist

[x] Prefix PR title with [WIP] if necessary.
[x] Add tests to cover changes as needed.
[x] Update documentation as needed.
[x] I have read the guidelines for adding a new blockchain
[x] If there is a related Issue, mention it in the description (e.g. Fixes #<issue_number> ).

Can you fill in the checklist for new blockchain support:
https://developer.trustwallet.com/wallet-core/newblockchain

The blockchain has launched mainnet and has stably run for at least 3 ~ 6 months without major security incidents.
The blockchain has extensive public documentation and tools available for developers to use.
The native coin is listed in the top 30 coins on CoinMarketCap and proposal gets approved on [https://governance.trustwallet.com].
The project needs to provide API/JSON-RPC access to the node with a load balancing setup for private use, see detail requirements here.
The native coin is tradable on major exchanges.


Separate UI Tests from E2E tests

Feature Request
RetroQuest makes use of unit tests (Jest) and end to end tests (protractor) to make up its automated testing strategy.  Currently, the end to end tests are trying to accomplish multiple tasks:

UI Tests
Integration Tests
End to End Tests

The other challenge with these tests is that they take a long-time to execute.  Almost 53 seconds on a computer with a 12 core process for just 21 tests compared to 4.4 seconds to run 326 unit tests.  This makes it more hassle for engineers to consistently run the tests
E2E Test Execution
Executed 21 of 23 specs INCOMPLETE (2 PENDING) in 38 secs.
[HPM] Client disconnected
[10:49:40] I/launcher - 0 instance(s) of WebDriver still running
[10:49:40] I/launcher - chrome #01 passed
Done in 52.72s.

Unit Test Execution
Test Suites: 51 passed, 51 total
Tests:       326 passed, 326 total
Snapshots:   0 total
Time:        3.836 s, estimated 7 s
Ran all test suites.
Done in 4.42s.

What are We Doing?
Separate UI tests from protractor to run quickly and give confidence in the behavior of the UI.
What are We not Doing?

Adding additional UI tests coverage
Testing UI functionality that cannot be easily imitated by JSDOM and thus won't give us confidence of stable software
Replacing protractor for true end to end tests

What does it look like to be Done?

UI Tests extracted from protractor likely into Jest Test Runner
Tests run quickly and accurately

Design

This will likely make use of Angular Testing Library

@rkennel Is this complete? From what I can tell it looks like #284 closes this issue


DOC: Add explicit reasoning for the lack of Herm/Sym check in 'linalg.eigh'

Fixes #7308

I've just hit the green button since the prose can be changed easily enough later just in case it is not clear.


MetaStream type should allow factory to return nullish value

According to the docstring for metaStream:

If the function returns null/undefined, no further action will be taken

So shouldn't the factory type here
https://github.com/thi-ng/umbrella/blob/fe6cee7534b8534ee97aa52b159979dba6b90461/packages/rstream/src/metastream.ts#L108
allow nullish values:
    factory: Fn<A, Subscription<B, B> | null | undefined>;

Currently, usages like this
    metaStream((x: string | undefined) => x && reactive(x));

get an error like this
Argument of type '(x: string | undefined) => "" | rs.Stream<string> | undefined' is not assignable to parameter of type 'Fn<string | undefined, Subscription<string, string>>'.
  Type '"" | Stream<string> | undefined' is not assignable to type 'Subscription<string, string>'.
    Type 'undefined' is not assignable to type 'Subscription<string, string>'. [2345]

You're absolutely right, @gavinpc-mindgrub! Have updated the sigs and also switched to the more general ISubscription interface as return type (even though currently everything is pretty much a subclass of Subscription only)...

Many thanks @postspectacular!


md-data-table overwrites the ng-class property of the tr element

When you add an ng-class directive to the tr element that is part of the ng-repeat of a data table, the ng-class directive is overwritten by the md-data-table directive.  Eg, if you change the sample to have ng-class on the tr element like this:
      <tr md-auto-select
      ng-class="{'too-many-calories': dessert.calories.value > 300}"
      md-disable-select="dessert.calories.value > 300" data-ng-repeat="dessert in desserts.data | orderBy: query.order | limitTo: query.limit : (query.page -1) * query.limit">

You will notice that this ng-class does not exist when the table is rendered in the browser.
I'll be putting up a pull request for this in a minute.

This shouldn't be an issue anymore.


Concatinate the first Name, Middle Name, Last Name from the input excel and write the results into full Name column.

Concatinate the first Name, Middle Name, Last Name from the input excel and write the results into full Name column.
Excel.xlsx

@anusha305
This pull request (PR) has conflicts; please refrain from merging it on GitHub and avoid accessing others folders unrelated to the changes. I'm unable to merge the PR at this time.
Task -15
Code verified.

@anusha305
Task -16
Code verified. Default activity name

Task -17
Code verified. Default activity name

Task -18
Code verified. Default activity name


Improve rclone search

Search files in the rclone mount also without file extension to maximize matching

@Gaisberg I'm using you fork of RDT sincr I use symlinks (with Zurg, Rclone). What did actually your fork change compared to main version? And are these changes already added to main version or should stick to your fork?


x/build/internal/coordinator/remote: add support for LUCI bots in session manager

This work was completed.


invalid COG from GDAL 3.1.0 onwards

Not sure whether this is the right place to report this but it seems relevant as it can be reproduced using rio cogeo create and rio cogeo validate.
Use the files in validate.zip to reproduce:
rio cogeo create temp.tif cog.tif && rio cogeo validate cog.tif with GDAL 3.0.4 creates a COG and validation outputs this:
Reading input: /temp.tif
Adding overviews...
Updating dataset tags...
Writing output to: /cog.tif
/cog.tif is a valid cloud optimized GeoTIFF

whereas running the same command with GDAL 3.1.0 (also tested 3.1.1 and 3.1.2 with the same result) makes rio cogeo validate return an error:
Reading input: /temp.tif
Adding overviews...
Updating dataset tags...
Writing output to: /cog.tif
The following errors were found:
- The offset of the main IFD should be 8 for ClassicTIFF or 16 for BigTIFF. It is 192 instead
/cog.tif is NOT a valid cloud optimized GeoTIFF

Again, I guess the error rather has its origin in either GDAL itself or rasterio, however I think it is worth at least documenting it here as it affects COG creation using rio-cogeo.
I'll investigate further on the GDAL and rasterio issue trackers but do you have a clue where the issue could be?

👋 @ungarj
I'm getting the same results when using GDAL command
$ gdaladdo tempr.tif -minsize 64
$ gdal_translate temp.tif temp_cog.tif -co TILED=YES -co COPY_SRC_OVERVIEWS=YES -co COMPRESS=DEFLATE

$ tiffdump temp_cog.tif
Magic: 0x4949 <little-endian> Version: 0x2a <Cl
Directory 0: offset 192 (0xc0) next 718 (0x2ce)
...

The validation script seems ok, so I don't really get why it's different.
Sadly I believe this is a GDAL problem!

Wait 👀 https://github.com/OSGeo/gdal/blob/master/gdal/swig/python/samples/validate_cloud_optimized_geotiff.py#L183-L213
This might just mean that you can't use the validation script with COG created with gdal3.1 😭

@ungarj, as pointed by @geospatial-jeff on a private slack, this is because of the Ghost Area https://gdal.org/drivers/raster/cog.html#header-ghost-area
Looking at GDAL docs, I wasn't aware that ghost area would be present for GeoTIFF that were created without the new COG driver... this is either a GDAL/Libtiff bug or something expected but that should also be documented in the https://gdal.org/drivers/raster/gtiff.html page
cc @rouault

this is either a GDAL/Libtiff bug or something expected but that should also be documented in the https://gdal.org/drivers/raster/gtiff.html page

The COG driver is mostly a wrapper over the GTiff one. So if using the COPY_SRC_OVERVIEWS=YES creation option, the ghost area will be created.
I'm not sure what "rio cogeo validate" runs, but it should be updated with the logic of latest validate_cloud_optimized_geotiff.py

Thanks @rouault this is really helpful!

I'm not sure what "rio cogeo validate" runs, but it should be updated with the logic of latest validate_cloud_optimized_geotiff.py

rio cogeo validate is not updated with the latest change you added to the gdal script because sadly we (I mean in rasterio) don't have access to the bytes directly so we can't do https://github.com/OSGeo/gdal/blob/master/gdal/swig/python/samples/validate_cloud_optimized_geotiff.py#L196-L208 😭
I'll see if I can PR rasterio to add such method.

yon't have access to the bytes directly

you can probably relax the test on the location of the first IFD to be within the first 200 bytes or so

Hi and thanks @vincentsarago and @rouault for the quick responses!

Proposed a new Reader for Rasterio, so we can access the bytes directly
https://rasterio.groups.io/g/dev/topic/add_reader_for_direct_file/75989193?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,75989193

When I look at https://github.com/OSGeo/gdal/blob/master/gdal/swig/python/samples/validate_cloud_optimized_geotiff.py#L196-L208 I see a problem that should be fixed in GDAL. That Python script is using GDAL's VSI API to work around a defect in the GDAL metadata API, no?

That Python script is using GDAL's VSI API to work around a defect in the GDAL metadata API, no?

well, this is really low level information, that is of little use except for the validation script, hence I didn't feel like adding it into metadata.

I would tend to agree with @sgillies that it will be nice to have this feature (accessing the hidden metadata) directly in GDAL. Not sure what's the easiest way forward.
Would be nice to just be able to do GetMetadataItem("GDAL_GHOST_AREA_METADATA") 🤷

Would be nice to just be able to do GetMetadataItem("GDAL_GHOST_AREA_METADATA")

See https://github.com/OSGeo/gdal/pull/2832


Add new feature: debugScript

Test scripts/setup scripts/cleanup scripts are designed to run in
background jobs, which makes debugging quite difficult. This new feature
allows user to print call trace and variable trace, or set break points
at specific lines/variables/commands/functions.
Example I: Print call trace for all background powershell scripts.

lisa.ps1 run xml\HV_Sock.xml -debugScript All

Example II: Print both call trace and variable (trace level 2).

lisa.ps1 run xml\HV_Sock.xml -debugScript All -traceLevel 2

Example III: Debug a specific script

lisa.ps1 run xml\HV_Sock.xml -debugScript .\setupscripts\HV_Sock_Basic.ps1

Example IV: Set breakpoint at lines

lisa.ps1 run xml\HV_Sock.xml -debugScript .\setupscripts\HV_Sock_Basic.ps1 -breakLine 53, 93

Example V: Set multiple breakpoints

lisa.ps1 run xml\HV_Sock.xml -debugScript .\setupscripts\HV_Sock_Basic.ps1 -traceLevel 2 -breakLine 53, 93 -breakVariable ReturnCode  -breakCommand InvokeCommand, TestPartI

In manual debug mode( hit breakpoint ), Enter "h" for help

[DBG]: [Job1]: h

Reference Docs:
Debug-Job
Set-PSDebug
Set-PSBreakpoint
This commit also includes a behavior change about saving log to file.

$jobResults = @(Receive-Job -id $jobID -ErrorAction SilentlyContinue)
$error[0].Exception.Message | out-file -encoding ASCII -append -filePath $logFilename

Changed to:

$jobResults = @(Receive-Job -id $jobID *>&1)

This allows script to log all the errors occurred during the test script running with complete information along with log context.
Ref:
About Redirection

Another scenario is to customize debug context in DebugScript.ps1, This has to be done in the file DebugScript.ps1. I gave a brief example in the file.

Hi,
When running an xml file that runs lisa vms in parallel (e.g. hyperv_fvt.xml), I'm seeing some errors in PS console that normally don't appear without debugScript param:
_Out-File : Cannot bind argument to parameter 'FilePath' because it is an empty string.
At C:\Users\v-adsuho\Documents\lisa\utilFunctions.ps1:1149 char:79

... .ToString() | out-file -encoding ASCII -append -filePath $logFilename

                                                         ~~~~~~~~~~~~

CategoryInfo          : InvalidData: (:) [Out-File], ParameterBindingValidationException
FullyQualifiedErrorId : ParameterArgumentValidationErrorEmptyStringNotAllowed,Microsoft.PowerShell.Commands.OutFileCommand_

Otherwise, in normal xmls (with just one suite), this behavior doesn't occur.

Modified, thank you very much for testing and feedback!
I suppose this is about parameter passing. Before this PR, $logFileName is defined in the function declaration but not used inside it. I simply assumed it is always available, which is not true, not all the invokes of this function provides this parameter.
Anyway, you might add a cleanup script to any case to reproduce this issue if you wish.

<cleanupScript>SetupScripts\DM_DISABLE.ps1</cleanupScript>

Thank you for the code change!


Release 3 Milestone Tasks

Items not finished in Release 2

[ ] Evaluate colors to match standards #217
[ ] Add Country webview to match Android #209
[ ] Action buttons for follow & spam #73
[ ] Remove default Gravatar for search links if possible #206
[ ] Rethink activity indicator for graph and overall #205
[ ] Animate bar value changes #77
[ ] Icons missing from Tag & Category entries #118

If We Have Time (from Release 2)

[ ] Published posts section should be collapsed upon loading #128
[ ] Pagination is required on View All #178
[ ] Add comment followers total to Comments section #155
[ ] Navbar improvements #142
[ ] Auto-fetch new data if time period has elapsed #111
[ ] Advanced error handling & retry mechanisms #108
[ ] Create separate data model for remote layer #94
[ ] Extract helper methods into unit-testable classes #86
[ ] Take NSLocale as parameter in services #80

Un-prioritized new items for Release 3

[ ] Add error condition display to post details and view all screens #224
[ ] Enable all warnings (or close to all) in Xcode build #218
[ ] Unify strings and pull from widgets.wp.com if possible #132

This is no longer valid to what's in Release 3. Will recreate.


Installing the project with Python 3.9.5 fails

It seems openvino isn't supporting python 3.8+ yet
RuntimeError

  Unable to find installation candidates for openvino (2021.3.0)

@moracabanas hey, which OS do you use? It works well for me with MacOS 11.2 (Python 3.8.6) and Ubuntu 20.04 (Python 3.8.6)

Thanks for your fast reply.  I'm on windows 10 python 3.9.5 with Poetry
Checking on Openvino last release is not updated to be 3.9 compatoble yet

@moracabanas as you can find in Requirements, our library doesn't support python 3.9+ too.

Sorry about that I misunderstood 3.8+. I thought 3.8+ means that you can use any >3.8 python version.
Thanks you for taking your time to provide a solution. For the moment I will try to use pyenv to manage python system version so Poetry initializes the project with the correct version for developement. Then I use a docker container with the target Python version.
I was looking for a solution because I have a background process holding python 3.9.5 for the next 5h 😂 so I am stuck.
No hurries and thanks you so much!

@moracabanas thanks for your feedback, I fixed readme to clear up the confusion

@moracabanas thanks for feedback. We migrated to 'blessed' library. Please try to use new version of our library.

That was fast!
Working as expected!
Thanks you so much!


texture issue with setDepthTest(true)

there are a tile map layer, a DrawNode, and a barbarian Sprite.
I use DrawNode follow mouse point to makr up which tile was selected.

but when I move the DrawNode to the between of barbarian and tile map. the texture of barbarian will break the DrawNode like his:

the issue looks caused by VertexZ. it also happened on object in tiles. compare top of two grasses, and barbarian behind a high tile

You'll either need to fully sort all tiles, sprites, or other nodes using topological sorting.
Or if you are using Native-only, or WebGL and not canvas, you can use the alpha discard shader with an appropriate alpha value (likely in your case 0.5 will work if all your textures transparent areas are all or nothing, on or off)

Hi, Steve, I tried fully sort all tiles, but seems not help for the issue.
https://github.com/BrookHuang/SRPG
here is my code, you can clone it as a test case.

@pandamicro
Please take a look for this bug on web,
I need you help~ Thanks

@BrookHuang
Hi! I ran your project and it's surely bit odd.
In my opinion, you could refer to our js-test/TileMap test/TMX ISO ZOrder, which may suit your occasion;)


Move Mercurial instructions, document how to create patch

Also:

Add a "Useful commands" doc
Switch http to https where possible
Clean up other documents to reduce duplication

Fixes issue #92

You can also get an idea of the logic by looking at the commit history
https://github.com/mozilla-l10n/documentation/commits/issue92


Laradock mysql exited with code 2

please help, mysql won't rune when i first do 'docker-compose up -d nginx mysql' I already did a clean install docker and pull the latest from this repo but still haven't found the solution.
Info:

Docker version ($ docker --version): Docker version 17.03.1-ce, build c6d412e
Laradock commit ($ git rev-parse HEAD): b2ad5f16e8e82fd5f1f9364ba9b26b85df212c7f
System info (Mac, PC, Linux):  PC
System info disto/version: Windows 10 Pro 64 bit v.1703

Issue: Laradock mysql exited with code 2
What seems to be going wrong?
my mysql won't start at first 'docker-compose up -d nginx mysql'
when i tried to do 'docker-compose ps' the mysql state is 'exit 2'

Relevant Code:
this is what it's look like after i did 'docker-compose up mysql'
mysql_1               | 2017-05-19T08:37:22.284861Z 0 [ERROR] InnoDB: posix_fallocate(): Failed to preallocate data for file ./mysql/time_zone.ibd, desired size 16384 bytes. Operating system error number 28. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/ operating-system-error-codes.html
mysql_1               | 2017-05-19T08:37:22.284915Z 0 [Warning] InnoDB: Retry attempts for writing partial data failed.
mysql_1               | 2017-05-19T08:37:22.284923Z 0 [Warning] InnoDB: Error while writing 16384 zeroes to ./mysql/time_zone.ibd starting at offset 131072
mysql_1               | 2017-05-19T08:37:22.335184Z 0 [ERROR] InnoDB: posix_fallocate(): Failed to preallocate data for file ./mysql/time_zone.ibd, desired size 16384 bytes. Operating system error number 28. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/ operating-system-error-codes.html
mysql_1               | 2017-05-19T08:37:22.335236Z 0 [Warning] InnoDB: Retry attempts for writing partial data failed.
mysql_1               | 2017-05-19T08:37:22.335244Z 0 [Warning] InnoDB: Error while writing 16384 zeroes to ./mysql/time_zone.ibd starting at offset 131072
mysql_1               | 2017-05-19T08:37:22.385395Z 0 [ERROR] InnoDB: posix_fallocate(): Failed to preallocate data for file ./mysql/time_zone.ibd, desired size 16384 bytes. Operating system error number 28. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/ operating-system-error-codes.html
mysql_1               | 2017-05-19T08:37:22.385444Z 0 [Warning] InnoDB: Retry attempts for writing partial data failed.
mysql_1               | 2017-05-19T08:37:22.385452Z 0 [Warning] InnoDB: Error while writing 16384 zeroes to ./mysql/time_zone.ibd starting at offset 131072
mysql_1               | 2017-05-19T08:37:22.435737Z 0 [ERROR] InnoDB: posix_fallocate(): Failed to preallocate data for file ./mysql/time_zone.ibd, desired size 16384 bytes. Operating system error number 28. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/ operating-system-error-codes.html
mysql_1               | 2017-05-19T08:37:22.435788Z 0 [Warning] InnoDB: Retry attempts for writing partial data failed.
mysql_1               | 2017-05-19T08:37:22.435797Z 0 [Warning] InnoDB: Error while writing 16384 zeroes to ./mysql/time_zone.ibd starting at offset 131072
mysql_1               | 2017-05-19T08:37:22.435957Z 0 [ERROR] [FATAL] InnoDB: Out of tablespace during rollback. Consider increasing your tablespace.
mysql_1               | 2017-05-19 08:37:22 0x7fd031586700  InnoDB: Assertion failure in thread<PHONE_NUMBER>02240 in file ut0ut.cc line 916
mysql_1               | InnoDB: We intentionally generate a memory trap.
mysql_1               | InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
mysql_1               | InnoDB: If you get repeated assertion failures or crashes, even
mysql_1               | InnoDB: immediately after the mysqld startup, there may be
mysql_1               | InnoDB: corruption in the InnoDB tablespace. Please refer to
mysql_1               | InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
mysql_1               | InnoDB: about forcing recovery.
mysql_1               | 08:37:22 UTC - mysqld got signal 6 ;
mysql_1               | This could be because you hit a bug. It is also possible that this binary
mysql_1               | or one of the libraries it was linked against is corrupt, improperly built,
mysql_1               | or misconfigured. This error can also be caused by malfunctioning hardware.
mysql_1               | Attempting to collect some information that could help diagnose the problem.
mysql_1               | As this is a crash and something is definitely wrong, the information
mysql_1               | collection process might fail.
mysql_1               |
mysql_1               | key_buffer_size=8388608
mysql_1               | read_buffer_size=131072
mysql_1               | max_used_connections=0
mysql_1               | max_threads=151
mysql_1               | thread_count=0
mysql_1               | connection_count=0
mysql_1               | It is possible that mysqld could use up to
mysql_1               | key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68190 K  bytes of memory
mysql_1               | Hope that's ok; if not, decrease some variables in the equation.
mysql_1               |
mysql_1               | Thread pointer: 0x0
mysql_1               | Attempting backtrace. You can use the following information to find out
mysql_1               | where mysqld died. If you see no messages after this, something went
mysql_1               | terribly wrong...
mysql_1               | stack_bottom = 0 thread_stack 0x40000
mysql_1               | mysqld(my_print_stacktrace+0x2c)[0xe81c7c]
mysql_1               | mysqld(handle_fatal_signal+0x459)[0x7aa4c9]
mysql_1               | /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7fd04d101890]
mysql_1               | /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7fd04bb0a067]
mysql_1               | /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7fd04bb0b448]
mysql_1               | mysqld[0x780c0b]
mysql_1               | mysqld(_ZN2ib5fatalD1Ev+0x15d)[0x110b54d]
mysql_1               | mysqld(_Z13row_undo_stepP9que_thr_t+0x66c)[0x109785c]
mysql_1               | mysqld(_Z15que_run_threadsP9que_thr_t+0xa34)[0x1026a74]
mysql_1               | mysqld(_Z31trx_rollback_or_clean_recoveredm+0xd2f)[0x10e693f]
mysql_1               | mysqld(trx_rollback_or_clean_all_recovered+0x4e)[0x10e77de]
mysql_1               | /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7fd04d0fa064]
mysql_1               | /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fd04bbbd62d]
mysql_1               | The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
mysql_1               | information that should help you find out what is causing the crash.
laradock_mysql_1 exited with code 2

I'm getting the same error.

https://github.com/laradock/laradock/issues/868#issuecomment-297675241 ?

my env is already like this
DATA_SAVE_PATH=/tmp
so what should i change actually ?

'/tmp' dir not exists on windows.
My 'solution' - don't use DATA_SAVE_PATH
(in docker-compose.yml)
### MySQL Container #########################################

    mysql:
      build:
        context: ./mysql
      environment:
        - MYSQL_DATABASE=${MYSQL_DATABASE}
        - MYSQL_USER=${MYSQL_USER}
        - MYSQL_PASSWORD=${MYSQL_PASSWORD}
        - MYSQL_ROOT_PASSWORD=${MYSQL_ROOT_PASSWORD}
      volumes:
        # without DATA_SAVE_PATH
        - mysql:/var/lib/mysql
      ports:
        - "${MYSQL_PORT}:3306"
      networks:
        - backend

Or you can specify a directory that exists on your computer.

thanks, i remove the line and it's work properly now 😃

This worked for me on Linux as well, thanks!

Yeah, it works for me on linux ubuntu 17.10

It also works on macOS high sierra. Thanks!

The only solution worked is by @alchimik worked 👯♂

I first built the default MySQL 8 container, then tried to switch to 5.7 when I had this error. I tried the mentioned solutions. I removed the stored mysql data from ~/.laradock on my Windows 10 machine.

I first built the default MySQL 8 container, then tried to switch to 5.7 when I had this error. I tried the mentioned solutions. I removed the stored mysql data from ~/.laradock on my Windows 10 machine.
Saved my life.

@bbarclay your case same with me, I try to delete the folder ~/.laradock/data/mysql in my Mac machine. and everything works.

I found that in the new installation the DATA_PATH_HOST is set to DATA_PATH_HOST=~/.laradock/data I changed it to DATA_PATH_HOST=./data and now it works.

@a1tem Thanks! It works for me on windown10.

Thank @alchimik . You saved my life

@bbarclay your case same with me, I try to delete the folder ~/.laradock/data/mysql in my Mac machine. and everything works.

Thanks!
Worked on macOS Mojave 10.14.5, MyQL 5.7

@alchimik Thanks man!!! I was hours trying to figure it out! Genius!

It works in ubuntu 18 too

This issue is related to a miss-configuration on laradock .env file. It is trying to store mysql data on ~/.data/.
Just change DATA_PATH_HOST to DATA_PATH_HOST=./data. Re-build everything and now it is working.

worked like a charm :)

'/tmp' dir not exists on windows.
My 'solution' - don't use DATA_SAVE_PATH
(in docker-compose.yml)
### MySQL Container #########################################

    mysql:
      build:
        context: ./mysql
      environment:
        - MYSQL_DATABASE=${MYSQL_DATABASE}
        - MYSQL_USER=${MYSQL_USER}
        - MYSQL_PASSWORD=${MYSQL_PASSWORD}
        - MYSQL_ROOT_PASSWORD=${MYSQL_ROOT_PASSWORD}
      volumes:
        # without DATA_SAVE_PATH
        - mysql:/var/lib/mysql
      ports:
        - "${MYSQL_PORT}:3306"
      networks:
        - backend

Or you can specify a directory that exists on your computer.

Thank you, that worked for me, too. The problem appeared to me with mysql 5.7, not mysql 8 (latest).