Bug: Ryuk fails to start due to port binding

Describe the bug
I upgraded from 3.5.0 to 4.1.0 and the container itself fails to spawn because the Ryuk container setup fails. I've tried debugging the issue and it looks like it is trying to bind the port exposed on IPv6 to the port on IPv4 (the container_port variable is correct for IPv4), which are for some reason different ports.
$ docker ps
CONTAINER ID   IMAGE                       COMMAND       CREATED         STATUS         PORTS                                         NAMES
4f1bad20a38c   testcontainers/ryuk:0.5.1   "/bin/ryuk"   7 seconds ago   Up 5 seconds   <IP_ADDRESS>:33029->8080/tcp, :::32775->8080/tcp   testcontainers-ryuk-1cf580e2-54c4-496d-a1d7-17f495911219

To Reproduce
Provide a self-contained code snippet that illustrates the bug or unexpected behavior. Ideally, send a Pull Request to illustrate with a test that illustrates the problem.
>       Reaper._socket.connect((container_host, container_port))
E       ConnectionRefusedError: [Errno 61] Connection refused

Runtime environment
Provide a summary of your runtime environment. Which operating system, python version, and docker version are you using? What is the version of testcontainers-python you are using? You can run the following commands to get the relevant information.
$ uname -a
Darwin jupiter.local 23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:30:44 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T6000 arm64
$ python --version
Python 3.11.7
$ docker info
gine - Community
 Version:    25.0.4
 Context:    colima
 Debug Mode: false
 Plugins:
  compose: Docker Compose (Docker Inc.)
    Version:  2.25.0
    Path:     /Users/sondre/.docker/cli-plugins/docker-compose

Server:
 Containers: 4
  Running: 0
  Paused: 0
  Stopped: 4
 Images: 112
 Server Version: 24.0.7
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 61f9fd88f79f081d64d6fa3bb1a0dc71ec870523
 runc version: v1.1.9-0-gccaecfc
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 6.5.0-21-generic
 Operating System: Ubuntu 23.10
 OSType: linux
 Architecture: aarch64
 CPUs: 2
 Total Memory: 3.817GiB
 Name: colima
 ID: ac2c6903-b356-409d-9301-b040440d1efd
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  <IP_ADDRESS>/8
 Live Restore Enabled: false

i cant reproduce on my m1 environment, but after what i saw on ipv6 working with compose i have no doubt there is a potential for an issue here.

Hi @sondr3!
Sorry to hear that you are having problems. I am on an M3 setup myself, but haven't encountered the same problem that you have. Am I reading it right that you are using colima with a x86 VM as your Docker runtime on an M1 / arm64 system?
Do you encounter the same problem if you run with a native arm64 backend without virtualization/colima?
We'll follow you up closely on this one, as Ryuk is important for us to run smoothly on all architectures.

@santi, correct. However, I can't run the image natively, I need to run the MSSQL Docker image for tests at $WORK and it only has amd64 images available :(
$ colima status
INFO[0000] colima is running using macOS Virtualization.Framework
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: virtiofs
INFO[0000] socket: unix:///Users/sondre/.colima/default/docker.sock

Ah, try using the mcr.microsoft.com/azure-sql-edge:1.0.7 image instead. It has ARM64 support and the API is compatible with mssql (Note: I haven't tried it extensively, only used as part of testing in this repo).
import sqlalchemy
from testcontainers.mssql import SqlServerContainer

with SqlServerContainer("mcr.microsoft.com/azure-sql-edge:1.0.7") as mssql:
    engine = sqlalchemy.create_engine(mssql.get_connection_url())
    with engine.begin() as connection:
        result = connection.execute(sqlalchemy.text("select @@VERSION"))

Using that image work without emulating amd64, but ryuk still fails to start sadly. Interestingly it mostly works when I try to debug and step through, so it may be a timing issue? Not really sure, it works maybe 1 in 5 attempts.

Having digged further into this, I strongly believe port bindings are not to blame for this problem. The <IP_ADDRESS>:33029->8080/tcp, :::32775->8080/tcp of your docker ps output indicates that port 33029 on IPv4 and port 32775 on IPv6 are mapped to port 8080 on the inside of your container on their respective IP interfaces. Nothing wrong with that.
If this behavior appears randomly in some cases and consistently when using breakpoint(), I agree it more likely looks like a timing issue. The mysterious thing is that the wait strategy for the Ryuk container is identical to the wait strategy in the Java implementation, which doesn't report the same problem. At the point of the ConnectionRefusedError, are you 100% sure the Ryuk container is running at all? Only case I can think about is that the RYUK_RECONNECTION_TIMEOUT is set so low that Ryuk terminates before a socket is connected. Could you try updating to the latest release (4.3.1) and setting an env variable as RYUK_RECONNECTION_TIMEOUT=30s?

I experienced the same problem on a Mac. Downgrading testcontainers (4.3.2 -> 3.7.1) fixed the issue.

The same happened to me. Fixed downgrading it to 3.7.1.
Why Ryuk container is not running during tests in the 3.7.1 version? It seems testcontainers >= 4 now uses ryuk in test execution

RYUK_RECONNECTION_TIMEOUT=30s doesn't do anything for me on 4.3.3 but setting a breakpoint here and pausing for a split second reliably works.

sounds like ports become available later on colima, and so we'd want to actually check those and not just wait on logs, if we wanted to be compatible with colima's differences with docker

does this tweak to retry for ~20 seconds help?
pip install git+https://github.com/testcontainers/testcontainers-python.git@issue486_explore_retry

It doesn't because an unhandled OSError gets thrown.
Simply handling the OSError doesn't help either. I get these exceptions:
[Errno 61] Connection refused
[Errno 22] Invalid argument
[Errno 22] Invalid argument
...
[Errno 22] Invalid argument

Something like this appears to resolve it but I don't know enough about this library, Python, or sockets to know if it's the correct approach.
        last_connection_exception: Optional[OSError] = None
        for _ in range(50):
            try:
                Reaper._socket = socket()
                Reaper._socket.connect((container_host, container_port))
                last_connection_exception = None
                break
            except OSError as e:
                last_connection_exception = e
                from time import sleep

                sleep(0.5)
        if last_connection_exception:
            raise last_connection_exception

Thanks @alexanderankin. I didn't do a great job explaining but I found that I needed to recreate the socket in addition to handling the exception type.

Looks like another instance of https://github.com/moby/moby/issues/42442

I had the same issue of ConnectionRefused on linux via Rancher Desktop (colima based), and using the issue486_explore_retry branch it's fixed for me.
Before I saw this thread, I investigated using a new breakpoint() around the socket connection, and even waiting <0.5s to continue, this fixed the connection refused, same as others above.
So I' m strongly leaning towards a timing issue in colima (behaviour deviating from docker engine), especially since the branch linked fixed it for me.
Note that the main branch fails most tests otherwise, due to missing Ryuk connection, and this ever since 4.1 introduced it! Same on work's Intel macbooks, testcontainers-py >=4.1 via Rancher Desktop is a no-go for us, had to pin to <=3.7
Suggest polishing this timing/retry branch, and consider merging, if it proves a good compromise.

alright im going to merge the associated PR - this will close this issue. please try the next release (4.4.0) when its released in couple mins

#539

and re-open/comment (and we'll reopen) this issue if needed.


fix: graceful fps logging fallback when pipeline context is not popul…

…ated

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


Prepare for update to SceneKit version?

Hi @rsanchezsaez ,thanks for providing a terrific framework to us. Now i want to move the code to Scenekit.But I met problems with Scenekit + CardboardSDK-iOS.In my code i use SCNRenderer to match with CBDViewController's openGL Context.But the [SCNRenderer render] function is deprecated: deprecated in iOS 9.0.And Particle Effects can not show correctly.
So,is there possible to change the project to Scenekit? Thanks.

Hi Ijfdestiny,
I have been trying render an SCNScene into GLKView's EAGLContext using the SCNRenderer, but it only renders black. I made a SceneKit replacement for the TreasureRenderer in the sample code as a test.  The same scene renders into an SCNView, even one using the same EAGLContext.
- (void)setupRendererWithView:(GLKView *)glView
{
	     [EAGLContext setCurrentContext:glView.context];
	     self.renderer =  [SCNRenderer rendererWithContext:glView.context options:nil];
	     self.renderer.scene = self.scene;
   ...

Did you manage to get a scene rendered into the Cardboard EAGLContext?

Hi CacheLine,maybe you forgotten to call [renderer render] in drawEyeWithEye:(CBDEye *)eye ?

Thanks Ijfdestiny, I just triple checked.  Nothing as easy as that :-(
I had also tried calling [renderer renderAtTime:] since they say [renderer render] is deprecated. It didn't help.

How about the view matrix and perspective of the cameraNode,did you tramsform then to SCNMatrix format?

(void)drawEyeWithEye:(CBDEye *)eye
{
glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT);
_view = GLKMatrix4Multiply([eye eyeViewMatrix], _camera);
_perspective = [eye perspectiveMatrixWithZNear:_zNear zFar:_zFar];
cameraNode.transform = SCNMatrix4FromGLKMatrix4(GLKMatrix4Transpose(_view));
[cameraNode.camera setProjectionTransform:SCNMatrix4FromGLKMatrix4(_perspective)];
[_renderer render];
}

Thank you IjfDestiny!
I was neglecting the glClear, without which everything was black.  I also missed the setProjectionTransform, and most annoyingly, the use of the transpose of the GL matrix to get the node transform.
Thank you again

It seems this have been resolved. Can this issue be closed? :)

I'm closing this issue now, let me know if there are any more issues.
In case it helps, a CBDSceneKit example project has just been added, demonstrating usage of the CardboardSDK with SceneKit+SpriteKit.


Docs have styling issues

Jinja docs have styling issues. Maybe we can limit table of contents depth to 3 or 4 levels?

https://jinja.palletsprojects.com/en/3.1.x/api/#jinja2.Environment

Duplicate of https://github.com/pallets/pallets-sphinx-themes/issues/64


tor: <IP_ADDRESS> -> <IP_ADDRESS>

Changes in version <IP_ADDRESS> - 2024-10-24
  This is minor release fixing an important client circuit building (Conflux
  related) bug which lead to performance degradation and extra load on the
  network. Some minor memory leaks fixes as well as an important minor feature
  for pluggable transports. We strongly recommend to update as soon as possible
  for clients in order to neutralize this conflux bug.

  o Major bugfixes (circuit building):
    - Conflux circuit building was ignoring the "predicted ports"
      feature, which aims to make Tor stop building circuits if there
      have been no user requests lately. This bug led to every idle Tor
      on the network building and discarding circuits every 30 seconds,
      which added overall load to the network, used bandwidth and
      battery from clients that weren't actively using their Tor, and
      kept sockets open on guards which added connection padding
      essentially forever. Fixes bug 40981; bugfix on <IP_ADDRESS>-alpha;

  o Minor feature (bridges, pluggable transport):
    - Add STATUS TYPE=version handler for Pluggable Transport. This
      allows us to gather version statistics on Pluggable Transport
      usage from bridge servers on our metrics portal. Closes
      ticket 11101.

  o Minor features (fallbackdir):
    - Regenerate fallback directories generated on October 24, 2024.

  o Minor features (geoip data):
    - Update the geoip files to match the IPFire Location Database, as
      retrieved on 2024/10/24.

  o Minor bugfixes (memleak, authority):
    - Fix a small memleak when computing a new consensus. This only
      affects directory authorities. Fixes bug 40966; bugfix
      on <IP_ADDRESS>-alpha.

  o Minor bugfixes (memory):
    - Fix memory leaks of the CPU worker code during shutdown. Fixes bug
      833; bugfix on <IP_ADDRESS>-alpha.

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 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.

backport in https://github.com/NixOS/nixpkgs/pull/351594


example doesn't do anything on Linux/Manjaro

import puppeteer from<EMAIL_ADDRESS>
const browser = await puppeteer.launch();
const page = await browser.newPage();
await page.goto("https://example.com");
await page.screenshot({ path: "example.png" });

await browser.close();

nothing happens. I don't see any browser open or screenshot.png created.
I tried adding { headless false } and I get this error:
Check file:///home/ettinger/src/accounts/bot/test.ts
error: Uncaught TimeoutError: Timed out after 30000 ms while trying to connect to the browser! Only Chrome at revision r991974 is guaranteed to work.
    throw new TimeoutError(
          ^
    at https://deno.land/x/puppeteer@14.1.1/src/deno/BrowserRunner.ts:162:11
    at Object.action (deno:ext/web/02_timers.js:145:13)
    at handleTimerMacrotask (deno:ext/web/02_timers.js:62:12)
➜  bot
$

I ran this command and it finished:

$ PUPPETEER_PRODUCT=chrome deno run -A --unstable<EMAIL_ADDRESS>Already downloaded at /home/ettinger/.cache/deno/deno_puppeteer/chromium/linux-991974/chrome-linux/chrome

same here:
error: Uncaught (in promise) Error: Failed to launch the browser process!
TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

  throw new Error(
        ^
    at waitForWSEndpoint (https://deno.land/x/puppeteer@14.1.1/src/deno/BrowserRunner.ts:176:9)
    at async BrowserRunner.setupConnection (https://deno.land/x/puppeteer@14.1.1/src/deno/BrowserRunner.ts:145:31)
    at async ChromeLauncher.launch (https://deno.land/x/puppeteer@14.1.1/src/deno/Launcher.ts:114:26)
    at async file:///home/green/ts2/test.js:3:17

I was running into this issue on Ubuntu, when trying to launch chromium using the exact same arguments as the ones I found while inspecting the deno process, I noticed Chromium was crashing with
execv /home/jesper/.cache/deno/deno_puppeteer/chromium/linux-991974/chrome-linux/chrome_crashpad_handler: Permission denied (13)

Needless to say, adding execute permissions to chrome-linux/chrome_crashpad_handler fixed it for me.


Remove objective-c layer

Why?
The Current version of "Ably Asset Tracking SDK" has two layers to communicate with swift and objective-c.
The differences between them are slight:

the inability to use Swift Result<T,U> in objective-c
the inability to use Swift enums in objective-c

Using these layers impose code duplication, which in turn could generate potential bugs, e.g.:
https://github.com/ably/ably-asset-tracking-swift/blob/0885a04f729964d3b396a0f5e735b7ae128b2ef6/Sources/AblyAssetTrackingPublisher/DefaultPublisher.swift#L237-L257
Solution
I replaced the Swift Result<T,U> type with a custom ATResult class that can be used in both languages with ease.
I also added a helper for ATResult that can unwrap its properties to enums, and because of that, the Swift code refactoring goes easier.
https://github.com/ably/ably-asset-tracking-swift/blob/f6bc65b6cdbf58990530d5d6153fc469587ee2e8/Sources/AblyAssetTrackingCore/ResultHandler.swift#L41-L68
Usage of ATResult Swift helper

When ATResult success property has no value, you can use enumUnwrap static var directly on the ATResult instance
https://github.com/ably/ably-asset-tracking-swift/blob/f6bc65b6cdbf58990530d5d6153fc469587ee2e8/Sources/AblyAssetTrackingPublisher/DefaultPublisher.swift#L499-L506

When ATResult success property has some value, you can use the enumUnwrap(T) method directly on the ATResult, where T is an expected type of value/object wrapped by success(T) case:
https://github.com/ably/ably-asset-tracking-swift/blob/f6bc65b6cdbf58990530d5d6153fc469587ee2e8/Sources/AblyAssetTrackingPublisher/DefaultPublisher.swift#L272-L282

I decided to use the result wrapped in an object instead of using the success:error: block because:

it's much easier to refactor the whole Swift code
it's similar to the Swift Result<T,U> type

This solution is not ideal, but it's a win-win for both platforms

Adding to my above comment: I'm not fully sure how to add Objective-C classes to a Swift Package Manager project; when I first tried it complained that I had mixed different languages in a package and that this was not allowed. But I know that our old friend Quick manages to do it - the QuickSpec class is defined in Objective-C and is available from Swift simply by doing import Quick.

I think the approach of introducing an Obj-C-friendly Swift.Result equivalent makes sense. I was wondering if it's necessary to give up the type safety that we get from Swift.Result, though. It was all of the /* Void */ etc comments on the ResultHandler types that drew this to my attention.
Could we define our ATResult class as a generic Objective-C class, like this?
@interface ATResult<Success, Failure> : NSObject

@property(nonatomic, nullable) Success success;
@property(nonatomic, nullable) Failure failure;

@end

(Edit: actually, the Failure doesn't need to be generic, that's always ErrorInformation for us…)
This will get imported into Swift as a generic type, too.
I haven't been able to try this myself yet since I'm struggling to get the project to build, so not sure how viable it is. Does it sound worth investigating?

of course this is much better approach, I don't know why I thought that generics are not available in objective-c

Adding to my above comment: I'm not fully sure how to add Objective-C classes to a Swift Package Manager project; when I first tried it complained that I had mixed different languages in a package and that this was not allowed. But I know that our old friend [Quick](https:/
/github.com/Quick/Quick) manages to do it - the QuickSpec class is defined in Objective-C and is available from Swift simply by doing import Quick.

It's a bit tricky but it's doable. All you have to do is to separate Objective-C and Swift layers and use Objective-C code as a dependency for Swift target.
I've made a simple example.
Mixed-SPM.zip

I think the approach of introducing an Obj-C-friendly Swift.Result equivalent makes sense. I was wondering if it's necessary to give up the type safety that we get from Swift.Result, though. It was all of the /* Void */ etc comments on the ResultHandler types that drew this to my attention.
Could we define our ATResult class as a generic Objective-C class, like this?
@interface ATResult<Success, Failure> : NSObject

@property(nonatomic, nullable) Success success;
@property(nonatomic, nullable) Failure failure;

@end

(Edit: actually, the Failure doesn't need to be generic, that's always ErrorInformation for us…)
This will get imported into Swift as a generic type, too.
I haven't been able to try this myself yet since I'm struggling to get the project to build, so not sure how viable it is. Does it sound worth investigating?

I love the idea but unfortunately it's not so universal because:

I love the idea but unfortunately it's not so universal

That's a shame.
So, I'm quite uneasy about giving up the type safety at the Swift level. It seems like quite a step backwards in terms of quality of the Swift API – it gives up quite a lot of compile-time safety.
How about we both spend a bit of time thinking about alternatives that don't give up this safety (or can do it together, if you prefer)? And if we don't come to a conclusion on a viable alternative, then I'll need to understand a bit better how the existing (split Swift / Obj-C) way of doing things works, but I think that it might be a better option.

but I think that it might be a better option

(Or one of the other alternatives @QuintinWillison suggested in #102, e.g. a separate Obj-C facade).

So, I'm quite uneasy about giving up the type safety at the Swift level. It seems like quite a step backwards in terms of quality of the Swift API – it gives up quite a lot of compile-time safety.

I'm not happy with that either, but this is the risk that we know https://github.com/ably/ably-asset-tracking-swift/pull/85#discussion_r578496865

How about we both spend a bit of time thinking about alternatives that don't give up this safety (or we can do it together if you prefer)? And if we don't come to a conclusion on a viable alternative, then I'll need to understand a bit better how the existing (split Swift / Obj-C) way of doing things works, but I think that it might be a better option.

Of course, I can give it another "thinking iteration" ;) maybe I'll have a better idea.
Pair programming it's not what I prefer - so we can do it separately, if you don't mind.
It's not so urgent so you can take a time to think about it :)

but I think that it might be a better option

(Or one of the other alternatives @QuintinWillison suggested in #102, e.g. a separate Obj-C facade).

maybe, but I guess we don't want to maintain two separate layers for Swift and objective-c ... it could be a potential source of future bugs.

maybe, but I guess we don't want to maintain two separate layers for Swift and objective-c ... it could be a potential source of future bugs.

I think we don't want to, sure. But then I guess we might need to answer the question "how much are we willing to compromise the quality of our Swift public API in order to have a single public API that also works with Objective-C"?  For example, for me, losing strong type information is an unacceptable loss for the Swift API. I think we should get a better idea of the options and then think about this.

One thing I've noticed is that it appears that in the public API, the only ResultHandler success types that we use are Void and Bool. So one option would be to keep the generic ResultHandler for usage inside the library, and then in the public interface:

ResultHandler<Void> can just become (ErrorInformation?) -> Void
we can introduce a specialised BoolResult type and then ResultHandler<Bool> becomes (BoolResult) -> Void

This is just an idea but worth thinking about.

this type of closure has to be multiplied every time when new returning type appears

Do you mean "this type of result class"?

BoolResult

I mean type like StringResult URLResult etc

Yep. Yeah, it's a potential issue, for sure.

@lawrence-forooghian since there is still "work in progress" I've changed this PR to Draft

I think we need a broader conversation about this, possibly in https://github.com/ably/ably-asset-tracking-swift/issues/217.

@lukasz-szyszkowski I think we can close this and replace it with a PR for https://github.com/ably/ably-asset-tracking-swift/issues/218 instead?

@lukasz-szyszkowski, I think we can close this and replace it with a PR for #218 instead?

Correct, I'm closing it now.


Discuss if we should resolve connections host paths into absolute paths for SQLite database

Currently, we explicitly try to resolve relative host paths given by user (or as provided in our example workflows) into absolute file paths in the case of SQLite databases by prefixing it with the initialised project's directory path. We also do make a check that such resolved path exists and if does not exists then we raise an error saying that the file does not exist. This has been the implementation since the PR: https://github.com/astronomer/astro-sdk/pull/1338
However, considering @feluelle 's opinion, we should not need to do any of such transformation.
This ticket calls for a discussion on this approach.

We have a concern with the way we right now handle transformation of SQLite host path from relative to absolute. The implementation currently lives close to Project module and we have a opinion that it should live close to connections handling, perhaps have a common utility that is used by both Project Initialisation and Validation. At the moment, for the SQLite validations when file does not exist, we raise an exception instead of just returning Failed as a boolean.


Adding OperationsApi to GAX

LGTM

Current coverage is 70.08% (diff: 82.03%)

Merging #144 into master will increase coverage by 3.17%

@@             master       #144   diff @@
==========================================
  Files            52         55     +3
  Lines          2049       2216   +167
  Methods           0          0
  Messages          0          0
  Branches        288        291     +3
==========================================
+ Hits           1371       1553   +182
+ Misses          601        583    -18
- Partials         77         80     +3

Powered by Codecov. Last update 8eeab01...6ba912c


chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
8113eed -> 58d733c

github.com/IBM/platform-services-go-sdk
require
patch
v0.53.0 -> v0.53.1

github.com/gruntwork-io/terratest
require
patch
v0.46.5 -> v0.46.6

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
patch
v1.23.15 -> v1.23.16

Release Notes

IBM/platform-services-go-sdk (github.com/IBM/platform-services-go-sdk)
v0.53.1
Compare Source
Bug Fixes

IAM Policy Management: update rule conditions based on API def (#288) (aa2f6a2)

gruntwork-io/terratest (github.com/gruntwork-io/terratest)
v0.46.6
Compare Source
Modules affected

helm

Description

Added support for the --repo options to the helm test feature

Special thanks

Special thanks to the following users for their contribution!

@jguionnet

Related links

https://github.com/gruntwork-io/terratest/pull/1365
https://github.com/gruntwork-io/terratest/pull/1368

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.23.16
Compare Source
Bug Fixes

deps: update gomod (#696) (a30b93b)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

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


training with resolution 1024

I don't have access to enough computation resource so I'm training on 8gpus with resolution 1024 on cityscapes, and I find it really hard to recover the result that's even nearly compatible to the ones in the paper. Would really appreciate if you can let me know if this is caused by the resolution? And what should I modify in configuration for resolution 1024 to work reasonably well?

I keep getting validation pq around 35-40, is that normal?


Add ability to read and select camera view points

For vtkjs files only, if there is a "cameraViewPoints" field,
the camera view points will be read into paraview glance and
saved in the store. If there are any camera view points loaded,
and if the view is a 3D view, a menu button will appear at the
bottom of the VtkView, allowing the user to select a camera view
point. When a view point is selected, the view point will be set
and rendered.
One thing that might be nice to add is to animate the transitions
to the camera view points. It's currently just an instant transition.
One thing we'll need to add soon is a way to set the visibility
of actors at different camera view points.

Here's a sample file to try out.
openvr_vtkjs.vtkjs.gz

And here's a picture of it in action:

Creating animation should be easy for the viewpoints. You can look into the store or proxy on how we do that. We may just need to provide a random camera method as well to enable animation rather than a specific reset camera orientation.
For the actor visibility, that should be easy to, but maybe you may want to make sure it can be capture in the viewport structure. I'm not sure if we should go with the VTK structure or the Proxy/Glance stucture
cameraViewPoints = {
  'Viewport name': {
      view: {
          cameraPosition: ...,
      },
      representations: {
          'datasetName': {
              ...repPropsValues
         }
     },
   }
}

or more VTK based

cameraViewPoints = {
  'Viewport name': {
      camera: {},
      actors: {
         'datasetName': {
              ...actorPropsValues
         }
      },
      props: {
         'datasetName': {
              ...propsPropsValues
         }
      },
     ....
  }
};

Lets go with
cameraViewPoints = {
  'Viewport name': {
      camera: {},
      show: ['dataset name 1'],
      hide: ['dataset name 2'],
  }
}

@jourdain Sounds good. The only other potential issue I could think of, is that it is possible for multiple datasets to have the same name, right?

But maybe this is just an edge case we can ignore...

It should not be possible to have the same name since the name is used for the directory to store the data. We may have to look into the issue. Might be a bug somewhere here

The above was done by loading the same dataset into paraview-glance twice in a row. I think we are going to skip over looking into that situation for now.

The latest commit changed the structure of the view point objects to match this structure.
Now, the visibilities of the sources get modified (if they are specified) when the view point changes.
Attached below is an example.
visibilities.vtkjs.gz

The ParaView side of this is mostly complete, except that only the data sets that are visible in the main window are currently written out to ParaView glance.

I wasn't using commitizen to make my commits... I can go back and fix that and force-push

This PR now depends on this VTK.js PR.

Looks good just by glimpsing through the code.

Unfortunately, I realized that when a .vtkjs file is embedded in the paraview glance html, this code block does not get called, and the camera view points do not get set in the store. This is because importBase64Dataset gets called directly instead.
@jourdain, do you know if there is a way for us to set the camera view points on the store within that function?

I'll see what I can do. But I need to finish up something before.

Add the following line in that method.
pxm.set({ '$store': store }, true);
And add the following after that if block
if (reader.getCameraViewPoints) {
  proxyManager
    .getReferenceByName('$store')
    .dispatch(
      Actions.SET_CAMERA_VIEW_POINTS,
      reader.getCameraViewPoints()
    );
}

@jourdain This worked great. Thank you so much, Seb!

FYI @floryst

I merged in my PR, so some things will have to be tweaked. I can help with that.

I just merged in master, so the new re-write branch which got merged yesterday is now a part of this branch, and there are no more merge conflicts.
However, for some reason, I think the performance went down due to merging master into this branch. For my examples, the time it freezes when the textures update is now extra long. The chrome performance tool doesn't seem to indicate anything specific (at first glance) to me either. The performance profiles from chrome are attached below. You can see that for some reason, after the update, I have some long pauses in rendering for no reason that is immediately apparent to me. Things like this:

Additionally, when loading my VTK.js file samples, there are new errors (usually 4 - 12 for my tests) that appear that state the following:
attempt to set zero width color range

There's also a new warning, vtkProxyManager did not request an animation.
These can all be seen in the sample log file attached below also.
Anyways, I think that other than that, this PR is in good condition, and if there are no more requested changes, it can be merged after this one gets merged, and the vtk-js version here gets updated.
Unfortunately, the project is also ending today, so I am not sure how much more time I will get to spend on this. But like I mentioned, I think it is in pretty good condition overall!
profile_before_updates.json.gz
profile_after_updates.json.gz
glance.log

Actually, this profile (attached below) may be more informative. It looks like there is a good 4 second freeze in this one that appears to be caused by the texture shader being compiled multiple times in a row, and each time takes ~1 second. That would maybe explain the long freezes for texture updates. But I'm not sure why it's happening.

Before the updates to master, it looks like there may have been a different call stack for updating the texture:

Just making some guesses...
profile_after_updates2.json.gz

My guess is that there was a loading lock happening to only make a render
call at the end of the initialization. Now the render hook on the proxy
manager trigger a render after every change right away. Hence the request
animation warnings.
On Wed, Jan 1, 2020 at 03:16 Patrick Avery<EMAIL_ADDRESS>wrote:

Actually, this profile (attached below) may be more informative. It looks
like there is a good 4 second freeze in this one that appears to be caused
by the texture shader being compiled multiple times in a row, and each time
takes ~1 second. That would maybe explain the long freezes for texture
updates. But I'm not sure why it's happening.
[image: image]
https://user-images.githubusercontent.com/9558430/71637478-2cbf7600-2c12-11ea-80a9-c990c8e414b4.png
Before the updates to master, it looks like there may have been a
different call stack for updating the texture:
[image: image]
https://user-images.githubusercontent.com/9558430/71637499-a22b4680-2c12-11ea-9d5a-a5ebb0d5b037.png
Just making some guesses...
profile_after_updates2.json.gz
https://github.com/Kitware/paraview-glance/files/4013730/profile_after_updates2.json.gz
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Kitware/paraview-glance/pull/284?email_source=notifications&email_token=AACH45SFPUABIJRNIXTWGU3Q3P4HHA5CNFSM4JSJ5XGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEH43XGQ#issuecomment-570014618,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACH45XGYQKFEW23QIGWAQLQ3P4HHANCNFSM4JSJ5XGA
.

I'm not sure what changes caused the "zero-width data range" errors, but the issue stems from proxyManager.getRepresentation(...) in GlanceVtkJsReader.js calling AbstractRepresentationProxy.setColorBy with model.rescaleOnColorBy === true, which tries to rescale the color range to the data range. This all happens right before rep.setRescaleOnColorBy(false). Not sure how it was working before.

Before we were delaying the call to render when a state was loading.


Fix MessageNotInflight error

Fixes #3435
I'm not sure, if the error text is correct, because I couldn't reproduce the error. It is documented to be a valid error, but no idea, how to actually force it.

Coverage decreased (-0.1%) to 94.425% when pulling 7c71290ca1e509e05ad2af883444a8f864b3f40d on gruebel:fix-sqs-message-not-inflight-error into f749f583eea70f86b69650bd3d3ea83e60c97c64 on spulec:master.

Coverage decreased (-0.1%) to 94.425% when pulling 7c71290ca1e509e05ad2af883444a8f864b3f40d on gruebel:fix-sqs-message-not-inflight-error into f749f583eea70f86b69650bd3d3ea83e60c97c64 on spulec:master.

Coverage decreased (-0.1%) to 94.425% when pulling 7c71290ca1e509e05ad2af883444a8f864b3f40d on gruebel:fix-sqs-message-not-inflight-error into f749f583eea70f86b69650bd3d3ea83e60c97c64 on spulec:master.

Coverage decreased (-0.1%) to 94.425% when pulling 7c71290ca1e509e05ad2af883444a8f864b3f40d on gruebel:fix-sqs-message-not-inflight-error into f749f583eea70f86b69650bd3d3ea83e60c97c64 on spulec:master.

@gruebel Just so know you're not alone:  I looked into this issue back in November and I simply could not find any way to reproduce the error on a real AWS backend.

@gruebel Just so know you're not alone:  I looked into this issue back in November and I simply could not find any way to reproduce the error on a real AWS backend.

Hmm.. not a fan of unreproducible bugs :)
What is the AWS output for this scenario?

Hmm.. not a fan of unreproducible bugs :)
What is the AWS output for this scenario?

@bblommers nothing just a 200 status response. You can invoke the change_message_visibility method multiple times with the same ReceiptHandle and you always get positive response.

@bblommers nothing just a 200 status response. You can invoke the change_message_visibility method multiple times with the same ReceiptHandle and you always get positive response.

I'm checking with the user who raised this on how to reproduce the error, will mark this as draft to prevent it from being merged until we know for sure what the desired behaviour is.

I'm checking with the user who raised this on how to reproduce the error, will mark this as draft to prevent it from being merged until we know for sure what the desired behaviour is.

Thank you for looking into addressing this. I posted an update in the original bug report: https://github.com/spulec/moto/issues/3435. As noted by @gruebel, AWS allows calling change_message_visibility multiple times (you can also delete a message multiple times).

From what I can see, we shouldn't raise the error here:
https://github.com/spulec/moto/blob/master/moto/sqs/models.py#L884
The following method will fail if we remove that if-statement: test_change_message_visibility_on_visible_message
However - running this test against AWS itself also fails as it stands, as the SQSError is not thrown in the last assert. So I guess we can remove that test alltogether
Haven't been able to test the idempotent delete-message use case yet.

I've (finally..) verified the behaviour against AWS - this is now fixed in #4655


test limb darkening

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

Project coverage is 28.75%. Comparing base (2d8818b) to head (152cac0).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #24   +/-   ##
=======================================
  Coverage   28.75%   28.75%
=======================================
  Files          11       11
  Lines         800      800
=======================================
  Hits          230      230
  Misses        570      570

Flag
Coverage Δ

unittests
28.75% <ø> (ø)

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

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


Update devnet docz

Fixes  https://github.com/nearprotocol/nearcore/issues/581

Seems this broke docs.


What about adding new feature like 'service catalog' to metadata center

I have read codes and blogs about metadata center which was created in dubbo 2.7. The new feature is very useful for service mock, testing and so on.  And I have a suggestion about this module.
In big companies, there are thousands of services in various applications. It is important to make it convenient to find certain service and its description(tell users how to use this service, who own this service and so on). For example, I want to find a service which contains methods about consumer account management. If dubbo supports service catalog feature, I can find certain service with search by key word "consumer account". And service (such as "ConsumerManagementService") catalog can shown me its methods(such as "findAccountById") list and description(such as
"/**

@MethodDesc("Find account info by id")
@RequestParams( @Param(name="Id", desc="accountId"))
@ResponseParam( desc="Account info dto list")
*/
") about every method. This feature will help to improve development efficiency and avoid repeated coding.

I think implement of this feature has two parts:
1. In Dubbo, add annotations for application, service and method. And put these information to metadata center with metadata report.
2. In Dubbo-Admin, add search and display functions.
What about adding this feature? If this feature is necessary, I can develop for it.

@beiwei30 @chickenlj


"Response is too large" when downloading blobs

The Issue
This occurred while downloading lbry://youtubeweek-jaclynglenn#6c2a342e1d65a944ee98284ff6f71c7e2fb2f5c3 but I was unable to replicate after trying again. Also had downloaded the same blob previously from same host without issue on another machine.
2017-12-12 11:37:55,401 INFO     lbrynet.core.Wallet:823: Resolving @TheRubinReport#17d6ddffe0593e86b2ad294da430b53f991fe9c3
2017-12-12 11:38:02,007 INFO     lbrynet.daemon.Downloader:95: Download lbry://youtubeweek-jaclynglenn status changed to initializing
2017-12-12 11:38:02,009 INFO     lbrynet.daemon.Downloader:95: Download lbry://youtubeweek-jaclynglenn status changed to downloading_metadata
2017-12-12 11:38:02,009 INFO     lbrynet.core.client.ConnectionManager:42: Connection Manager 9378bcf7a21f107d032806aac1f55b62caf9ab56c4fa0f4ea40c3da3943502271d9ea0e1b23796d4ae4677ad56eda31e initialized
2017-12-12 11:38:02,334 INFO     lbrynet.core.client.BlobRequester:414: Offered rate 0.000000/mb accepted by <IP_ADDRESS>
2017-12-12 11:38:02,404 INFO     lbrynet.core.client.BlobRequester:563: Blob 9378bcf7a21f107d has been successfully downloaded from <IP_ADDRESS>:3333
2017-12-12 11:38:03,200 INFO     lbrynet.lbry_file.EncryptedFileMetadataManager:246: Saved sd blob hash 9378bcf7a21f107d032806aac1f55b62caf9ab56c4fa0f4ea40c3da3943502271d9ea0e1b23796d4ae4677ad56eda31e to stream hash 474f95d352ac42916bb1d26874dda19d0d590f1dc273372e4fdf0b6765a963e4e189490ea8d61559a41ef45f63d65f71
2017-12-12 11:38:03,217 INFO     lbrynet.daemon.Downloader:187: Downloading lbry://youtubeweek-jaclynglenn (9378bc) --> D:\LBRY Downloads Main PC\Jaclyn Glenn- Atheism, Break Ups, and Doing Ayahuasca.mp4
2017-12-12 11:38:03,217 INFO     lbrynet.daemon.Downloader:95: Download lbry://youtubeweek-jaclynglenn status changed to running
2017-12-12 11:38:03,219 INFO     lbrynet.core.client.ConnectionManager:42: Connection Manager Jaclyn Glenn- Atheism, Break Ups, and Doing Ayahuasca.mp4 initialized
2017-12-12 11:38:03,403 INFO     lbrynet.file_manager.EncryptedFileDownloader:32: lbry://youtubeweek-jaclynglenn (9378bc) is running
2017-12-12 11:38:03,604 INFO     lbrynet.core.client.BlobRequester:414: Offered rate 0.000000/mb accepted by <IP_ADDRESS>
2017-12-12 11:38:04,575 INFO     lbrynet.core.client.BlobRequester:414: Offered rate 0.000000/mb accepted by <IP_ADDRESS>
2017-12-12 11:38:04,720 INFO     lbrynet.core.client.BlobRequester:563: Blob b33864256678513e has been successfully downloaded from <IP_ADDRESS>:3333
2017-12-12 11:38:05,608 INFO     lbrynet.core.client.BlobRequester:563: Blob 0cd7be482a18e335 has been successfully downloaded from <IP_ADDRESS>:3333
2017-12-12 11:38:06,312 INFO     lbrynet.core.client.BlobRequester:563: Blob 6fa143dae11e8098 has been successfully downloaded from <IP_ADDRESS>:3333
2017-12-12 11:38:07,434 INFO     lbrynet.core.client.BlobRequester:563: Blob 86f0ea748776d85b has been successfully downloaded from <IP_ADDRESS>:3333
2017-12-12 11:38:07,775 INFO     lbrynet.core.client.BlobRequester:563: Blob f72f658343f0146d has been successfully downloaded from <IP_ADDRESS>:3333
2017-12-12 11:38:07,821 WARNING  lbrynet.core.client.ClientProtocol:60: Response is too large from <IP_ADDRESS>:3333. Size 65600
2017-12-12 11:38:07,829 WARNING  lbrynet.core.client.BlobRequester:294: An error occurred while downloading 85edf7f242ef1f8964ff21bef1a9b356f13b8f4fb0022c0020ad22289cc5f4abd0276900acf6f5ceb147e925834c9c88 from <IP_ADDRESS>:3333. Error: Traceback (most recent call last):
Failure: lbrynet.core.Error.ConnectionClosedBeforeResponseError:
2017-12-12 11:38:07,848 ERROR    lbrynet.core.client.ClientProtocol:192: The connection to <IP_ADDRESS>:3333 is closing due to an unexpected error: [Failure instance: Traceback (failure with no frames): <class 'lbrynet.core.Error.ConnectionClosedBeforeResponseError'>:
]
2017-12-12 11:38:07,849 ERROR    lbrynet.core.client.ClientProtocol:192: The connection to <IP_ADDRESS>:3333 is closing due to an unexpected error: [Failure instance: Traceback (failure with no frames): <class 'lbrynet.core.Error.ConnectionClosedBeforeResponseError'>:
]
2017-12-12 11:38:07,852 INFO     lbrynet.core.client.ClientProtocol:228:
2017-12-12 11:38:07,871 INFO     lbrynet.core.client.ClientProtocol:230: The connection to <IP_ADDRESS>:3333 is closing due to an error: Traceback (most recent call last):
Failure: lbrynet.core.Error.ConnectionClosedBeforeResponseError:
2017-12-12 11:38:07,871 WARNING  lbrynet.core.client.ClientProtocol:237: Not asking for another request from <IP_ADDRESS>:3333
2017-12-12 11:38:15,128 INFO     lbrynet.core.client.BlobRequester:563: Blob 43c2e2879d31f6f9 has been successfully downloaded from <IP_ADDRESS>:3335
2017-12-12 11:38:23,328 INFO     lbrynet.core.client.BlobRequester:563: Blob 85edf7f242ef1f89 has been successfully downloaded from <IP_ADDRESS>:3335
2017-12-12 11:38:24,497 INFO     lbrynet.core.Wallet:676: Skipping dust
2017-12-12 11:38:24,497 INFO     lbrynet.core.Wallet:676: Skipping dust
2017-12-12 11:38:35,226 INFO     lbrynet.core.client.BlobRequester:563: Blob 1546546d7fade754 has been successfully downloaded from <IP_ADDRESS>:3335
2017-12-12 11:38:44,256 INFO     lbrynet.core.client.BlobRequester:563: Blob dc9b382b0a8b45b0 has been successfully downloaded from <IP_ADDRESS>:3335
2017-12-12 11:38:53,803 INFO     lbrynet.core.client.BlobRequester:563: Blob 61ca972fbf7c4337 has been successfully downloaded from <IP_ADDRESS>:3335
2017-12-12 11:38:57,448 INFO     lbrynet.core.client.BlobRequester:563: Blob 9a9bbeaa7f9808ed has been successfully downloaded from <IP_ADDRESS>:3335
2017-12-12 11:39:03,223 INFO     lbrynet.core.client.BlobRequester:563: Blob f842931a1b85debe has been successfully downloaded from <IP_ADDRESS>:3335
2017-12-12 11:39:09,621 INFO     lbrynet.core.client.BlobRequester:414: Offered rate 0.000000/mb accepted by <IP_ADDRESS>
2017-12-12 11:39:11,384 INFO     lbrynet.core.client.BlobRequester:563: Blob 061c050a3211fecd has been successfully downloaded from <IP_ADDRESS>:3335
2017-12-12 11:39:12,138 INFO     lbrynet.core.client.BlobRequester:563: Blob f001486a6f3d5f27 has been successfully downloaded from <IP_ADDRESS>:3333
2017-12-12 11:39:13,469 INFO     lbrynet.core.client.BlobRequester:563: Blob 9d19032a2eecd566 has been successfully downloaded from <IP_ADDRESS>:3335
2017-12-12 11:39:14,026 INFO     lbrynet.core.client.BlobRequester:563: Blob 2463d5056f5d04f7 has been successfully downloaded from <IP_ADDRESS>:3333
2017-12-12 11:39:15,246 INFO     lbrynet.core.client.BlobRequester:563: Blob 76a4764dcc766cd1 has been successfully downloaded from <IP_ADDRESS>:3335
2017-12-12 11:39:15,788 INFO     lbrynet.core.client.BlobRequester:563: Blob d9fab58d27c60db4 has been successfully downloaded from <IP_ADDRESS>:3333
2017-12-12 11:39:17,664 INFO     lbrynet.core.client.BlobRequester:563: Blob 856266e4baa438a5 has been successfully downloaded from <IP_ADDRESS>:3333
2017-12-12 11:39:18,605 INFO     lbrynet.core.client.BlobRequester:563: Blob dab084f38803d899 has been successfully downloaded from <IP_ADDRESS>:3335
2017-12-12 11:39:19,487 INFO     lbrynet.core.client.BlobRequester:563: Blob c3adfc0402e98503 has been successfully downloaded from <IP_ADDRESS>:3333
2017-12-12 11:39:21,565 INFO     lbrynet.core.client.BlobRequester:563: Blob 2ba009720037ade8 has been successfully downloaded from <IP_ADDRESS>:3335
2017-12-12 11:39:22,035 INFO     lbrynet.core.client.BlobRequester:563: Blob 6d4d4cf11b899272 has been successfully downloaded from <IP_ADDRESS>:3333
2017-12-12 11:39:24,562 INFO     lbrynet.core.client.BlobRequester:563: Blob ce240a20f5db9520 has been successfully downloaded from <IP_ADDRESS>:3335
2017-12-12 11:39:25,082 INFO     lbrynet.core.Wallet:676: Skipping dust
2017-12-12 11:39:25,082 INFO     lbrynet.core.Wallet:676: Skipping dust
2017-12-12 11:39:30,460 INFO     lbrynet.core.client.BlobRequester:563: Blob ebe6a07da7a6fcb7 has been successfully downloaded from <IP_ADDRESS>:3335
2017-12-12 11:39:34,812 INFO     lbrynet.core.client.BlobRequester:563: Blob 6618054eedf27c04 has been successfully downloaded from <IP_ADDRESS>:3335
2017-12-12 11:39:37,710 INFO     lbrynet.core.client.BlobRequester:563: Blob 66fff11eccbe2c39 has been successfully downloaded from <IP_ADDRESS>:3335
2017-12-12 11:39:51,801 INFO     lbrynet.core.client.BlobRequester:563: Blob d69137e0776327e8 has been successfully downloaded from <IP_ADDRESS>:3333
2017-12-12 11:39:53,358 INFO     lbrynet.core.client.BlobRequester:563: Blob 45975c580349b1fa has been successfully downloaded from <IP_ADDRESS>:3333
2017-12-12 11:39:54,283 INFO     lbrynet.core.client.BlobRequester:563: Blob dfa4553dd23040a0 has been successfully downloaded from <IP_ADDRESS>:3335
2017-12-12 11:39:54,292 INFO     lbrynet.core.client.BlobRequester:563: Blob 7251502fe30105d2 has been successfully downloaded from <IP_ADDRESS>:3333

System Configuration

LBRY Daemon version:
LBRY App version:
LBRY Installation ID:
Operating system:

Anything Else

Screenshots

We saw this happen on content hosted on cluster host 8 and cluster host 10

Just happened to me now when downloading lbry://thebadsamaritanmustdie  on 0.19.1

2018-03-21 12:44:41,997 INFO     lbrynet.core.client.BlobRequester:487: Requesting blob f6354f9680b8a8a1467655f81114d8ae4c5d62df3eaa4b0e03e7e0961b19300b2459dd79bdf621f868b094db979a832a from <IP_ADDRESS>:3333
2018-03-21 12:44:42,094 WARNING  lbrynet.core.client.ClientProtocol:60: Response is too large from <IP_ADDRESS>:3333. Size 66996
2018-03-21 12:44:42,095 WARNING  lbrynet.core.client.BlobRequester:294: An error occurred while downloading f6354f9680b8a8a1467655f81114d8ae4c5d62df3eaa4b0e03e7e0961b19300b2459dd79bdf621f868b094db979a832a from <IP_ADDRESS>:3333. Error: Traceback (most recent call last):
Failure: lbrynet.core.Error.ConnectionClosedBeforeResponseError:

2018-03-21 12:44:42,095 ERROR    lbrynet.core.client.ClientProtocol:192: The connection to <IP_ADDRESS>:3333 is closing due to an unexpected error: [Failure instance: Traceback (failure with no frames): <class 'lbrynet.core.Error.ConnectionClosedBeforeResponseError'>:
]
2018-03-21 12:44:42,096 ERROR    lbrynet.core.client.ClientProtocol:192: The connection to <IP_ADDRESS>:3333 is closing due to an unexpected error: [Failure instance: Traceback (failure with no frames): <class 'lbrynet.core.Error.ConnectionClosedBeforeResponseError'>:
]
2018-03-21 12:44:42,096 INFO     lbrynet.core.client.ClientProtocol:228:
2018-03-21 12:44:42,096 INFO     lbrynet.core.client.ClientProtocol:230: The connection to <IP_ADDRESS>:3333 is closing due to an error: Traceback (most recent call last):
Failure: lbrynet.core.Error.ConnectionClosedBeforeResponseError:

2018-03-21 12:44:42,096 WARNING  lbrynet.core.client.ClientProtocol:237: Not asking for another request from <IP_ADDRESS>:3333

@tzarebczan can you check loggly for frequency?

Only happened twice in the last month, both times on lbrynet-0.18.2. Closing.


Update building-from-source.md

Just updating the building guide with and advise

/azp skip

can i merge?

Yes!


cmake: Populate var CMAKE_GCOV

For each compiler, also set a CMAKE_GCOV var referencing the appropriate
gcov tool.
Tested with gcc and host-gcc on the ChromeOS codebase.
Signed-off-by: Jeremy Bettis<EMAIL_ADDRESS>

Approvers, can you review this please? When using the zephyr sdk to calculate test coverage, the various cross-compilers emit different versions of the coverage data, and only the matching version of gcov can process those files, so I need to be able to find the right path to gcov for each arch.

@keith-zephyr Can you look at this?

evgeniy-paltsev: I made your requested changes, can you re-review please?


Storybook links lead to 404

https://quicktype.github.io/glide-data-grid At time of writing, this link leads to a Github Pages 404.

Duplicate of https://github.com/glideapps/glide-data-grid/issues/774


[FLINK-6745] [docs] Updated Table API / SQL docs: Overview

Thanks for the feedback @alpinegizmo and @sunjincheng121.
I updated the PR.

Will correct the remaining mistakes and merge this...

I merged it into the tableDocs branch. @fhueske can you close this PR?


[Linux] [Offline] The libgconf-2.so.4 library is now deprecated and is no longer included in the distribution.

Bug description
Hi.
In the previous version there was no problem, but in this update of my linux distribution (linux mint 19 to mint 20) it can no longer run piskel because apparently a library is missing (I don't know how to install, I run it from terminal). Researching the internet this libconf-2.so.4 library is already obsolete.
I tried to download it with my "apt" package manager:
sudo apt install libgconf2-4
But it is no longer available, I don't know what else I can do.
Regards.
Steps to reproduce the bug

I enter the folder "Piskel-0.14.0-64bits"
In the terminal I run ./piskel
The terminal issues the following message:
./piskel: error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: No such file or directory

Environment details

operating system:  Linux (Linux Mint 20 Ulyana  kernel: 5.4.0-42-generic)
browser (or offline application version): Offline application version

Sprite details

number of frames:
sprite resolution:
session duration:

Feel free to include a screenshot of the bug, a .piskel file of the sprite or anything else that can help us investigate.

Workaround to this:
sudo apt-get install libgconf-2-4

Try running/building the desktop app via #1049.


A Package Conflict When Installing Dependencies

Kindly remind a package conflict between tokenizers==0.13.3 and transformers==4.40.0 when installing dependencies.
Error Message:
INFO: pip is looking at multiple versions of transformers to determine which version is compatible with other requirements. This could take a while.
ERROR: Cannot install -r requirements.txt (line 19) and tokenizers==0.13.3 because these package versions have conflicting dependencies.

The conflict is caused by:
    The user requested tokenizers==0.13.3
    transformers 4.40.0 depends on tokenizers<0.20 and >=0.19

Replace transformers==4.40.0 with transformers can address this issue for installation.

Thank you very much for your suggestion. However, we set 'transformers==4.40.0' to ensure compatibility with LLaMA3. We have already replaced 'tokenizers==0.13.3' with 'tokenizers' in the requirements.

Thanks for addressing my issue. Have a good weekend :)


Fix information leakage vulnerability in the Webhook server.

Description
If the body of the request was not correctly read the error provided was directly sent to the user. Now a standard error message is sent every time there is a problem in the processing of the request body, this fix avoid also the information leakage due to the use of specific errors for every different problem.

/ok-to-test

/lgtm
A bit intimidating the title, and not sure it really reflects the problem (it seems more information leakage), but the fix seems ok to me.

Completely agree with you, it seems a possible information leakage due to the knowledge of the specific error by the possible attacker.

/rebase

/merge


Feature request: Youtube downloading video support

Download videos using yt-dlp library

Too much complexity, might work on later

working through right now!


As a publisher I want to route links to TaxonPages via OTU UUIDs

Project option to list a canonical TP URL
Maybe a re-direct endpoint to the API
Also permit hitting OTU pages via https://orthoptera.speciesfile.org/otus/<uuid>

If we create a model:
ProjectOtuResolver
project_id
otu_query_params JSONB
site  STRING  like https://orthoptera.speciesfile.org
resource (path) STRING like otus/
Then we can map OTU UUIDs to sites that request .html.  Sites tthat request .json can hit api/vN.

Feels like maybe we don't need project ID, but could treat this as Community data sensu Namespace.  ProjectID could be added to otu_query_params

Another use case beyond the COLDP exports is updating SF IDs/URLs in Wikidata, which are all pointing at the old sites currently:
https://www.wikidata.org/wiki/Property:P6050
https://www.wikidata.org/wiki/Q10509344


fix CDDL tests

Some of the Shelley CCDL tests are silently failing. We need to fix this.

apologies, this is redundant with #1253


Waypoint: Change the Font Size of an Element

Challenge http://www.freecodecamp.com/challenges/waypoint-change-the-font-size-of-an-element has an issue.
***The challenge says to make the p elements set the font-size to 16 px.

This should be fixed now. Feel free to reopen if issue still persist.


fix: check app loading state on post

close #100

The erreur came from the backend (it couldn't return any app data even though it existed)


FIX: Missing Saccade information in Eyelink File

This is an issue as PR.
I hit an edge case in one of my Eyelink files, where the participant was in the middle of a saccade upon recording start. This edge case results in missing values (i.e. ".") in the "ESACC" event of the ASCII file, that need to be properly converted to nans during reading.
it was a quick fix, and I added a line to the test suite to simulate this edge case, but Let me know if you want me to share a file and code to reproduce the error, or if you need more info.

... marking for merge-when-green and will merge main into this branch once https://github.com/mne-tools/mne-python/pull/11878 lands which hopefully should make CIs happy here


Container not found. Error : 39987

Hi,
I was deploying azure storage on iot edge via marketplace image of azure storage (mcr.microsoft.com/azure-blob-storage)
After deploying the container on iotedge, it was showing running but when i checked the logs i found out this :
Starting Azure Blob Storage on IoT Edge, version <IP_ADDRESS>.
[2019-12-18 14:42:09.284] [info    ] [tid 1] [MetaStore.cc:558] [Initialize] Existing DB version:1, current version:1
[2019-12-18 14:42:09.288] [info    ] [tid 40] [main.cc:77] [GCUncommittedBlocks] GCUncommittedBlocks thread starts. UncommittedBlocksExpiryTimeInMinutes:1440
[2019-12-18 14:42:09.288] [info    ] [tid 40] [main.cc:89] [GCUncommittedBlocks] GCUncommittedBlocks thread sleeps. UncommittedBlocksExpiryTimeInMinutes:1440
[2019-12-18 14:42:10.351] [info    ] [tid 1] Microsoft.Azure.Devices.BlobStorage.Common.EventGridConfiguration: Event Grid endpoint not specified, events turned off.
[2019-12-18 14:42:10.457] [info    ] [tid 1] Microsoft.AzureStack.Services.Storage.EntryPoint.BlobService: BlobService - In StartAsync
[2019-12-18 14:42:10.968] [info    ] [tid 1] Info_debug: Loading config Param {0} ({1}) read: {2}, p0="NephosAllowPathStyleUris", p1="Allow path-style URIs", p2="true"
[2019-12-18 14:42:10.969] [info    ] [tid 1] Info_debug: Successfully loaded {0}: {1}, p0="NephosAllowPathStyleUris", p1="True"
[2019-12-18 14:42:10.980] [info    ] [tid 1] Info_debug: Loading config Param {0} ({1}) read: {2}, p0="Nephos.MaskClientIPAddressesInLogs", p1="Indicates whether client IP addresses should be masked in logs.", p2="false"
[2019-12-18 14:42:10.981] [info    ] [tid 1] Info_debug: Successfully loaded {0}: {1}, p0="Nephos.MaskClientIPAddressesInLogs", p1="False"
[2019-12-18 14:42:10.981] [info    ] [tid 1] Info_debug: Loading config Param {0} ({1}) read: {2}, p0="NephosIncludeInternalDetailsInErrorResponses", p1="Include internal details in error responses", p2="true"
[2019-12-18 14:42:10.981] [info    ] [tid 1] Info_debug: Successfully loaded {0}: {1}, p0="NephosIncludeInternalDetailsInErrorResponses", p1="True"
[2019-12-18 14:42:10.994] [info    ] [tid 1] Info_debug: Loading config Param {0} ({1}) read: {2}, p0="StampName", p1="Stamp Name", p2="Default Stamp"
[2019-12-18 14:42:11.893] [info    ] [tid 1] Microsoft.AzureStack.Services.Storage.EntryPoint.BlobService: BlobService - StartAsync completed
[2019-12-18 14:42:11.922] [info    ] [tid 1] Microsoft.Azure.Devices.BlobStorage.Tiering.BlobTieringService: Starting service...
[2019-12-18 14:42:12.123] [info    ] [tid 1] [BlobInterface.cc:1490] [ListBlobsInOrder] ListBlobsInOrder received. Container:imageblob BlobNameStart:null MaxBlobNames:1 OrderType:0 Flags:1
[2019-12-18 14:42:12.123] [error   ] [tid 1] [MetaStore.cc:1928] [ListBlobsInOrder] Container not found. Name:imageblob
[2019-12-18 14:42:12.123] [error   ] [tid 1] [BlobInterface.cc:1528] [ListBlobsInOrder] ListBlobsInOrder failed. Container:imageblob Error:39987
[2019-12-18 14:42:12.159] [info    ] [tid 1] Microsoft.Azure.Devices.BlobStorage.Ttl.BlobTtlService: Starting service...
[2019-12-18 14:42:12.326] [info    ] [tid 34] [ContainerInterface.cc:148] [ListBlobContainers] ListContainers received. ContainerNamePrefix:null ContainerNameStart:null MaxContainerNames:10
[2019-12-18 14:42:12.327] [info    ] [tid 34] [ContainerInterface.cc:168] [ListBlobContainers] ListContainers completed. ContainerEntryCount:0 NextContainerName:null
Application started. Press Ctrl+C to shut down.
Hosting environment: Production
Content root path: /azure-blob-storage/
[2019-12-18 14:42:13.147] [info    ] [tid 20] [BlobInterface.cc:1490] [ListBlobsInOrder] ListBlobsInOrder received. Container:imageblob BlobNameStart:null MaxBlobNames:1 OrderType:0 Flags:1
[2019-12-18 14:42:13.147] [error   ] [tid 20] [MetaStore.cc:1928] [ListBlobsInOrder] Container not found. Name:imageblob
[2019-12-18 14:42:13.147] [error   ] [tid 20] [BlobInterface.cc:1528] [ListBlobsInOrder] ListBlobsInOrder failed. Container:imageblob Error:39987
[2019-12-18 14:42:14.149] [info    ] [tid 20] [BlobInterface.cc:1490] [ListBlobsInOrder] ListBlobsInOrder received. Container:imageblob BlobNameStart:null MaxBlobNames:1 OrderType:0 Flags:1
[2019-12-18 14:42:14.149] [error   ] [tid 20] [MetaStore.cc:1928] [ListBlobsInOrder] Container not found. Name:imageblob
[2019-12-18 14:42:14.149] [error   ] [tid 20] [BlobInterface.cc:1528] [ListBlobsInOrder] ListBlobsInOrder failed. Container:imageblob Error:39987
[2019-12-18 14:42:15.149] [info    ] [tid 20] [BlobInterface.cc:1490] [ListBlobsInOrder] ListBlobsInOrder received. Container:imageblob BlobNameStart:null MaxBlobNames:1 OrderType:0 Flags:1
[2019-12-18 14:42:15.150] [error   ] [tid 20] [MetaStore.cc:1928] [ListBlobsInOrder] Container not found. Name:imageblob
[2019-12-18 14:42:15.150] [error   ] [tid 20] [BlobInterface.cc:1528] [ListBlobsInOrder] ListBlobsInOrder failed. Container:imageblob Error:39987
[2019-12-18 14:42:16.151] [info    ] [tid 20] [BlobInterface.cc:1490] [ListBlobsInOrder] ListBlobsInOrder received. Container:imageblob BlobNameStart:null MaxBlobNames:1 OrderType:0 Flags:1

Now, i am not sure why this is happening after following all steps from below azure docs correctly

Container Create Options :
{
    "HostConfig": {
        "Binds": [
            "local-image-repository:/blobroot"
        ],
        "PortBindings": {
            "11002/tcp": [
                {
                    "HostPort": "11002"
                }
            ]
        }
    }
}

Module Twin Settings :
{
    "deviceAutoDeleteProperties": {
        "deleteOn": true,
        "deleteAfterMinutes": 7200,
        "retainWhileUploading": false
    },
    "deviceToCloudUploadProperties": {
        "uploadOn": true,
        "uploadOrder": "OldestFirst",
        "cloudStorageConnectionString": "SENSITIVE CONTENT",
        "storageContainersForUpload": {
            "imageblob": {
                "target": "imageblob"
            }
        },
        "deleteAfterUpload": false
    }
}

Can somebody help here ?

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

ID: d574f299-1f45-ad1b-755f-ced23163a60a
Version Independent ID: 54532d7c-60b0-8522-9455-4ec094af9cb4
Content: Deploy blob storage on module to your device - Azure IoT Edge
Content Source: articles/iot-edge/how-to-deploy-blob.md
Service: iot-edge
GitHub Login: @arduppal
Microsoft Alias: arduppal

@tanieee28 Please help with the link of document on which above document feedback request is created.
Under this repository we want to make sure any issue is linked to a doc so we can help others that may be having the same issue.

@AshokPeddakotla-MSFT I have followed the below document for deploying blob storage on IoT Edge :

@tanieee28 I followed the documentation and the config which you have provided and able to deploy module successfully without any issues.
Could you please provide more detailed steps to repro your issue? Where are you seeing this error message?
@arduppal Do you have any suggestions for this issue?

@tanieee28 Have you had a chance to see my response? Do let us know the requested details for further help.

Hi @AshokPeddakotla-MSFT . Sorry for delayed response.
I have also followed the same document and still when deploying the module, after module start the above mentioned error logs are coming ( Error 39987)
Let me explain the scenario again,

I am deploying the blob on iotedge with the configuration mentioned above in the issue.
I have an azure blob storage on AZURE whose connection string i have given in the same configuration.
After successful deployment, the module is showing running but in the logs i am seeing that the module is not able to find the local container named as imageblob, and it is showing the error as "Container Not Found"

"storageContainersForUpload": {
"imageblob": {      //local container name
"target": "imageblob"   //remote container name
}
}
More Info:
I am doing this on Raspberry Pi 3 ( raspbian stretch)
iotedge -- latest version

@tanieee28  Thanks for the details. I am assigning this to the author @arduppal for further assistance.

@arduppal Please check this issue and provide your suggestions.

@tanieee28 Have you created storage container "imageblob"? This error is to be expected on a fresh deployment when you haven't created any containers/blobs yet. The upload module is trying to push out blobs based on the configuration you specified but it looks like there is nothing to push out yet.
Let me know if you have any questions.

@tanieee28 Does the above suggestions helped you resolve the issue? Do let us know if you need further help.

@mbialecka Sorry for delayed response.
Yes, its a fresh deployment and what i was expecting is that local blob module should create the local blob container by itself and should not through above logs stating that it is not able to find it.
However, With some help i was able to resolve this by using Azure storage explorer. So, i connected the storage explorer with the local blob storage using the connection string and later created the blob container named "imageblob" from the storage explorer functionalities.
But, i am still concerned about the local blob module as its the module's work to create an internal blob container from given configs. Above solution can be a workaround but its not a solution and it will be helpful if the owner of this module fixes this in future.
Thanks

@AshokPeddakotla-MSFT : Can you close this issue?

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

Hi. I have the same problem on a fresh deployment. I have created a docker volume called "storagevolume". Then below is my deployment settings:
Container create options:
{     "Env": [         "LOCAL_STORAGE_ACCOUNT_NAME=localstorage",         "LOCAL_STORAGE_ACCOUNT_KEY=KEY"     ],     "HostConfig": {         "Binds": [             "storagevolume:/blobroot"         ],         "PortBindings": {             "11002/tcp": [                 {                     "HostPort": "11002"                 }             ]         }     } }
Module twin settings:
{     "deviceAutoDeleteProperties": {         "deleteOn": false,         "deleteAfterMinutes": 35791,         "retainWhileUploading": true     },     "deviceToCloudUploadProperties": {         "uploadOn": true,         "uploadOrder": "OldestFirst",         "cloudStorageConnectionString": "DefaultEndpointsProtocol=AZURE-STORAGE-ENDPOINT",         "storageContainersForUpload": {             "localblobstorage": {                 "target": "edgelocalstorage"             }         },         "deleteAfterUpload": false     } }
The error I see is:
[2021-06-29 10:02:00.719] [error   ] [tid 1838] [MetaStore.cc:1953] [ListBlobsInOrder] Container not found. Name:localblobstorage [2021-06-29 10:02:00.719] [error   ] [tid 1838] [BlobInterface.cc:1535] [ListBlobsInOrder] ListBlobsInOrder failed. Container:localblobstorage Error:39987 [2021-06-29 10:02:01.722] [info    ] [tid 1838] [BlobInterface.cc:1494] [ListBlobsInOrder] ListBlobsInOrder received. Container:localblobstorage BlobNameStart:null MaxBlobNames:1 OrderType:0 Flags:1
I can clearly see that module cannot find the source container. But isn't it module's responsibility to create that container upon start?

Yes, i agree and as from the comments from @arduppal it was expected to be added in next update.
Till that time, you can create a container with the name specified ("localblobstorage") in your azureblobstorage module using azure storage explorer App.
Here is the link to get the app, [https://azure.microsoft.com/en-in/features/storage-explorer/]

Thanks @tanieee28. Actually I was not successful in manually creating local storage via storage explorer. I will redo and if I face same issue will write here.
@arduppal, any timeline on the updated version? I'm using version <IP_ADDRESS>.

I can't manually create container using the storage explorer. I'm using the following connection string to connect to storage account:
DefaultEndpointsProtocol=http;BlobEndpoint=http://<IP_ADDRESS>:11002/localstorage;AccountName=localstorage;AccountKey=NTUZVOQjzS1976mG1Tnzbm4In1FpZDLQgoXcB7BTJcZpEcFfA+rnbgzcC2mkCXdmyoXQDkReLLr0Glrg8gXcUg==;
I face the following error:
`Unable to retrieve child resources.
Details:
{
"name": "RestError",
"message": "One of the request inputs is not valid.\nRequestId:3e3f5d3b-3fc0-4baf-9965-931bb3f569f8\nTime:2021-06-29T21:27:05.4881822Z",
"stack": "RestError: One of the request inputs is not valid.\nRequestId:3e3f5d3b-3fc0-4baf-9965-931bb3f569f8\nTime:2021-06-29T21:27:05.4881822Z\n    at new RestError (C:\Program Files (x86)\Microsoft Azure Storage Explorer\resources\app\node_modules\@azure\core-http\dist\index.js:2362:28)\n    at handleErrorResponse (C:\Program Files (x86)\Microsoft Azure Storage Explorer\resources\app\node_modules\@azure\core-http\dist\index.js:3246:17)\n    at C:\Program Files (x86)\Microsoft Azure Storage Explorer\resources\app\node_modules\@azure\core-http\dist\index.js:3182:18\n    at processTicksAndRejections (internal/process/task_queues.js:97:5)",
"code": "InvalidInput",
"statusCode": 400,
"request": {
"streamResponseStatusCodes": {},
"url": "http://<IP_ADDRESS>:11002/?include=metadata&comp=list",
"method": "GET",
"headers": {
"_headersMap": {
"x-ms-version": {
"name": "x-ms-version",
"value": "2020-04-08"
},
"user-agent": {
"name": "user-agent",
"value": "Microsoft Azure Storage Explorer, 1.19.1, win32 azsdk-js-storageblob/12.4.1 (NODE-VERSION v12.16.3; Windows_NT 10.0.18363)"
},
"x-ms-client-request-id": {
"name": "x-ms-client-request-id",
"value": "203d8317-1183-47d7-9d6f-26b9b4f7beec"
},
"x-ms-date": {
"name": "x-ms-date",
"value": "Tue, 29 Jun 2021 21:27:05 GMT"
},
"authorization": {
"name": "Authorization",
"value": "SharedKey localstorage:qAgjrg6rMCNEFxQsg+cVT8czp72qnPZvl0zpffeev7Y="
},
"cookie": {
"name": "Cookie",
"value": ""
}
}
},`

Yes, I checked this in  my environment and saw the same error.
let me try to debug this.
@AshokPeddakotla-MSFT Request your help on this incase its an issue from some new updates.

Any update on this from MS? @AshokPeddakotla-MSFT @arduppal

@arminghasemazar Could you please let us know what is the error you were facing when using Azure Storage Explorer to create the container manually?

@SatishBoddu-MSFT  Already wrote here.

I can't manually create container using the storage explorer. I'm using the following connection string to connect to storage account:
DefaultEndpointsProtocol=http;BlobEndpoint=http://<IP_ADDRESS>:11002/localstorage;AccountName=localstorage;AccountKey=NTUZVOQjzS1976mG1Tnzbm4In1FpZDLQgoXcB7BTJcZpEcFfA+rnbgzcC2mkCXdmyoXQDkReLLr0Glrg8gXcUg==;
I face the following error:
`Unable to retrieve child resources.
Details:
{
"name": "RestError",
"message": "One of the request inputs is not valid.\nRequestId:3e3f5d3b-3fc0-4baf-9965-931bb3f569f8\nTime:2021-06-29T21:27:05.4881822Z",
"stack": "RestError: One of the request inputs is not valid.\nRequestId:3e3f5d3b-3fc0-4baf-9965-931bb3f569f8\nTime:2021-06-29T21:27:05.4881822Z\n at new RestError (C:\Program Files (x86)\Microsoft Azure Storage Explorer\resources\app\node_modules@Azure\core-http\dist\index.js:2362:28)\n at handleErrorResponse (C:\Program Files (x86)\Microsoft Azure Storage Explorer\resources\app\node_modules@Azure\core-http\dist\index.js:3246:17)\n at C:\Program Files (x86)\Microsoft Azure Storage Explorer\resources\app\node_modules@Azure\core-http\dist\index.js:3182:18\n at processTicksAndRejections (internal/process/task_queues.js:97:5)",
"code": "InvalidInput",
"statusCode": 400,
"request": {
"streamResponseStatusCodes": {},
"url": "http://<IP_ADDRESS>:11002/?include=metadata&comp=list",
"method": "GET",
"headers": {
"_headersMap": {
"x-ms-version": {
"name": "x-ms-version",
"value": "2020-04-08"
},
"user-agent": {
"name": "user-agent",
"value": "Microsoft Azure Storage Explorer, 1.19.1, win32 azsdk-js-storageblob/12.4.1 (NODE-VERSION v12.16.3; Windows_NT 10.0.18363)"
},
"x-ms-client-request-id": {
"name": "x-ms-client-request-id",
"value": "203d8317-1183-47d7-9d6f-26b9b4f7beec"
},
"x-ms-date": {
"name": "x-ms-date",
"value": "Tue, 29 Jun 2021 21:27:05 GMT"
},
"authorization": {
"name": "Authorization",
"value": "SharedKey localstorage:qAgjrg6rMCNEFxQsg+cVT8czp72qnPZvl0zpffeev7Y="
},
"cookie": {
"name": "Cookie",
"value": ""
}
}
},`

Any update on this issue?

Any update on this issue?

Same issue here... since the IoT device is not on my local network (it´s an Edge) I cannot use the Storage Explorer to create the container. Is there any update on this issue?

I had similar issue with storage explorer. Then i figured out the issue in my connection string, I was missing account name in blob endpoint inside connection string
Following is my connection string
DefaultEndpointsProtocol=http;BlobEndpoint=http://<IP_ADDRESS>:11002/gatewayftpfiles;AccountName=gatewayftpfiles;AccountKey=

Same issue for me even with account anme in blob endpoint : storageconnectionstring=DefaultEndpointsProtocol=http;BlobEndpoint=http://<IP_ADDRESS>:11002/devstoreaccount11;AccountName=devstoreaccount11;AccountKey=*****
Is there any update about this issue?

Any updates on this issue?

Any updates on this issue?
@AshokPeddakotla-MSFT

@tanieee28 - When you originally filed this issue, the info you provided contained an Azure Storage account access key. The key has been edited out of the issue and replaced with the <account-key> placeholder, but we recommend you revoke/rotate account keys to ensure that key cannot be used.


Add Pedro's publications

Please add missing pubs from https://scholar.google.com/citations?hl=en&user=U1A6iBMAAAAJ&view_op=list_works&sortby=pubdate for 2017, 2016, 2015 and 2014

@shrev I opened my web page and the list of publications is not yet showing the pubs available in my Google Scholar link. Did you add them?
If not, Craig said that most pubs may be in his bib file, so you can copy them from there.

@szeke I will look into the issue.


Issue #SC-1627 feat:test case for user request validator and keycloak…

…service

Codecov Report

Merging #779 into 2.6.5-to-2.7.0 will increase coverage by 0.33%.
The diff coverage is n/a.

@@                 Coverage Diff                  @@
##             2.6.5-to-2.7.0     #779      +/-   ##
====================================================
+ Coverage             38.56%   38.89%   +0.33%
- Complexity              979      989      +10
====================================================
  Files                   149      149
  Lines                 10085    10085
  Branches               1120     1120
====================================================
+ Hits                   3889     3923      +34
+ Misses                 5787     5753      -34
  Partials                409      409

Impacted Files
Coverage Δ
Complexity Δ

...g/sunbird/common/request/UserRequestValidator.java
38.87% <0%> (+5.32%)
99% <0%> (+10%)
: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 85f0223...e5da22c. Read the comment docs.


When a directory has been entered by way of zoxide, it should be selected in parent (left) column

What system are you running Yazi on?
Linux X11
What terminal are you running Yazi in?
kitty 0.31.0
Yazi version
yazi 0.2.2 (a19e263 2024-01-24)
Did you try the latest main branch to see if the problem has already been fixed?
Tried, but the problem is still present
Describe the bug
When I navigate to a directory, it is shown and highlighted in the parent column, but if I jump to a directory using zoxide, the highlighted directory is not updated in the parent column.
Expected Behavior
Regardless of how I enter a directory, it should be shown and highlighted in the parent column.
To Reproduce
Jump to a directory using zoxide. Note that the directory is not highlighted in the parent column.
Configuration
Not relevant
Anything else?
No response

Should be fixed in https://github.com/sxyazi/yazi/pull/581


Fix relative README link

Now they are https://github.com/DNBbank/getting-started/blob/master/python/(../README.md)
Should be https://github.com/DNBbank/getting-started/blob/master/README.md

Thank you :v:


Inconsistent Datum Inclusion in Witness Set Between Legacy Lucid and Lucid-Evolution Versions

In the legacy Lucid version, when performing a payToContract operation with a datum, the datum is automatically included in the witness set by default unless explicitly specified as inline.
However, in the updated lucid-evolution version, the datum is not included in the witness set when using the following code:
When doing the following on lucid-evolution the datum is not included into the witness set.
 .pay.ToContract(     contractAddress,     { kind: "asHash", value: datumCBOR },     assetsToLock,   )

Hey @hadelive  @solidsnakedev Tested this fix, and unfortunately, it's still not adding the datum to the witness set using the example code above.

I tested release 0.3.10 and can confirm this is now fixed, and I can see the data being added to the witness set. Thanks @hadelive


support square brackets in Spark

Support square brackets for SparkSQL which is used to access data in complex data types such as array and structs.
I couldn't find an explicit documentation of this support in SparkSQL documentation. However, it can be inferred based on the Hive compatibility doc and Hive documentation itself:

https://docs.databricks.com/spark/latest/spark-sql/compatibility/hive.html
https://cwiki.apache.org/confluence/display/Hive/LanguageManual+UDF#LanguageManualUDF-OperatorsonComplexTypes

FWIW this syntax is commonly used in SparkSQL examples: https://stackoverflow.com/questions/28332494/querying-spark-sql-dataframe-with-complex-types

Coverage remained the same at 99.815% when pulling 9d20469b3706c03e2937ce0991ba01c619e4faca on forestfang-stripe:forestfang--sparksql-square-brackets into 3cd6d98d2ab1b05e9588f0f80f30067b54326ef9 on zeroturnaround:master.

Thanks for the PR.
This issue is now fixed in SQL Formatter 6.0


Use of data element in result

The 'data' element is not always used to contain the main results - compare 'programs', crops, genome maps, and 'germplasm related calls'.

Yes, this is a feature. Data only contains paginated results.

Reinhard, I agree that this is a feature and will close this issue.  Please re-open if you disagree.
Thanks,
Jan Erik


Azure Devops integration

Detailed Description
Is there a way or at least a workaround to integrate with azure devops ?
Context
Generate release note on azure devops Wiki. in Universal artefact folder as a md file
Possible Implementation
Azure devops extension ?
Your Environment

Version Used: 5.1 GitVersion only is used
Edition Used (.NET Core, .NET Framework): linux on build agent. Win and Mac on dev computer
Operating System and version (Windows 10, Ubuntu 18.04): ubuntu, win 10 & 11, MacOS

Any joy?

@cedrox @dazinator I am not a big user of Azure DevOps, so I am not the right person to attempt to take on this work.
Within GitReleaseManager, we now have both a GitHub and GitLab provider, which has been working well for what I use it for.  Within both GitLab and GitHub, there is a similar structure in terms of issues, which are mapped to milestones, which can then flow into a release.
Within Azure DevOps (from the quick look that I have done just now), there doesn't seem to be the same structure.  If we can agree a path forward to map the constructs of GitReleaseManager into Azure DevOps, then I think it would be a great addition.
As users of Azure DevOps, how would you see this coming together?

The construct I'd find useful would be release notes generation as an artifact.
I'll do my best to share as much hopefully relevent info as I can.
Builds
Work items in devops can be linked with git commits, and builds. This link happens automatically if you include the work item number in a git commit (similar to how it works with github - unsurprisingly). If that git commit also triggers a build you will see the build in devops, with that workitem linked, and the commit linked to work item.
SemVer
We use gitversion in Builds to ensure build numbers are semver. Not sure how relevent this is.
GitFlow
We use git flow branching model. Typically we are interested in having release notes for each release of master branch. We don't care about generating release notes for every CI build.
How we get release notes
There is a URL that takes this form:
https://dev.azure.com/[your org]/[your proj]/_traceability/runview/workitems?currentRunId=[build id]
When we use this with a build Id for a build of master branch, we are able to see the total list of workitems that were merged in the git flow release to master - so this is the complete set of items in this release.
Our product team uses this link to manually create some release notes which they circulate.
What I'd like to accomplish
I'd like to be able to run some tool during a build (or release) pipeline, with this build Id as an argument, and have it ingest these work items from azure devops and output some release notes artifact to disk. With that I could then achieve things like the following (outside the responsibility of the GRM tool)

upload that as build artifact for prod team to find.
Add a subsequent build step that creates a wiki page from this file (OP desires this) so that it could be revised and edited.

Releases (Side note).
In devops, aside from build pipelines, there are also release pipelines which are purely edited through the UI. A yaml build pipeline when it completes could be a trigger for such a release pipeline. For example when a build of the master branch completes, a release pipeline can be triggered which would be used to deploy the assets through to staging, prod etc. I mention this because I could see this tool also being used in a Release pipeline instead of just a yaml build pipeline, with the build id that triggered the release.
Other info
DevOps doesn't have milestones exactly.. workitems can have parents and children, which can have start and end dates. It is pretty customisable here so not every project may use the same model / structure. Each project must chose a "process model" to use and custom ones can be derived from the standard ones, and then tailored. I am most familiar with the "Agile" process model, which is where you typically have the following work item types: Epics broken down into Features, broken down into User stories, broken down into Tasks. Typically the content for release note generation would be the user story level - although i guess you could also pull in the parent feature and the parent epic as useful headers / subheaders. Tasks would be too granular I suspect.
I am not familiar with what this project does for automation around milestones and whether any of that could apply here.


[hotfix] Reduce and simplify code for column creation in RocksDB backend

What is the purpose of the change
This PR is a simple refactoring of some RocksDB state backend code.
Brief change log
Verifying this change
existing tests
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

cc @StefanRRichter, @carp84

@azagrebin Can you rebase and have also have one build triggered? Then I will take a look.

Merging.


HCAP-1422 - Phase/Allocations do not get populated after Site is edited

Work completed:

Initially, when the details page mounted - The parent component SiteViewDetails, and the child 'SiteViewDetaisTabs' were each fetching the site details. The child was handling all logic for participants/phases, but the parent was handling logic for editing sites. (Thus why phases/allocations were not being re-fetched after successful edit)

Reduced network calls on initial load to 3 - getSite, getParticipants, getPhases, and moved that logic to the parent.

Moved API calls to service files. (There is inconsistency in how we handle the response, but I did not address those inconsistencies in this PR)

Fixed bug - if you edit a site, the phase data is still visible.

Manually tested al actions to ensure they are still working as intended.

Additional work

removed an additional button click on cypress test, it was already being clicked in setAllocationForm(), also updated spelling mistake on fn name.

Looks good so far. I'll give it a proper review on Monday once I have a chance to try it out myself.


/dev/null permissions are wrong

Description
Since 20-Aug-2020, the access rights for /dev/null are set to crw-r--r-- instead of crw-rw-rw- every few hours. This happens on two Flatcar Container Linux stable releases:

2345.3.1
2512.3.0

Impact
Most shell scripts break when unable to write to /dev/null.
Environment and steps to reproduce

Set-up: VMWare ESX with six Flatcar Container Linux clusters, all of which are affected.
Task: The Flatcar Container Linux clusters all run a Docker Swarm.
Action(s): nothing
Error: various failures due to /dev/null not being writable by non-root users

Expected behavior
/dev/null should be writable by everyone.
Additional information
Previously, we had a custom udev rule installed to work around https://github.com/coreos/bugs/issues/2437
This udev rule is no longer required, and has been removed. The /dev/null issue remains, however.
Reboots briefly fix the problem, which then returns after a number of hours.

Hello,
thank's for reaching out. I checked some of the servers we have running and didn't see this issue. Would be good if you can trace which process changes the permissions. I'll try to come up with instructions for doing it.

We're doing this right now: https://access.redhat.com/solutions/1240813
When the issue hits again, I hope to know more.

I can't access the contents of the link you posted, but I would try it with this here:
docker run --privileged -v /usr/lib/modules:/usr/lib/modules -v /sys/kernel/debug:/sys/kernel/debug -v /sys/fs/bpf:/sys/fs/bpf --rm -it quay.io/iovisor/bpftrace bpftrace -e 'tracepoint:syscalls:sys_enter_fchmodat { if (str(args->filename)=="/dev/null") {printf("%d %s %s\n", pid, comm, str(args->filename)); } }'

Yet, it will only print the process name and PID, not the parents.

You can try to watch for the modification with
docker run --privileged -v /dev:/dev --rm -it fedora sh -c 'dnf install -y inotify-tools && inotifywait -r -m -e attrib /dev/null'

and when a line is printed, dump the contents of a long running tracer, for example the some bpftrace commands or simply
 docker run --privileged --rm -it fedora sh -c 'dnf install -y perf && perf trace -a --expr '*chmod*,*mknod*''

We eventually found it with a kernel audit rule:
-w /dev/null -p a -k null-watch
$ sudo journalctl -xef | grep null-watch
Sep 02 12:01:05 *** kernel: audit: type=1300 audit(1599040865.584:9617): arch=c000003e syscall=90 success=yes exit=0 a0=7fde40e35f38 a1=1a4 a2=7fde418a4c58 a3=0 items=1 ppid=41209 pid=41210 auid=500 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=20 comm="pypy" exe="/home/core/pypy/bin/pypy" subj=system_u:system_r:kernel_t:s0 key="null-watch"
Sep 02 12:01:05 *** audit[41210]: SYSCALL arch=c000003e syscall=90 success=yes exit=0 a0=7fde40e35f38 a1=1a4 a2=7fde418a4c58 a3=0 items=1 ppid=41209 pid=41210 auid=500 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=20 comm="pypy" exe="/home/core/pypy/bin/pypy" subj=system_u:system_r:kernel_t:s0 key="null-watch"
Sep 02 12:02:50 *** audit: EXECVE argc=3 a0="grep" a1="--colour=auto" a2="null-watch"
^C
$ ls -l /dev/null
crw-r--r--. 1 root root 1, 3 Sep  1 17:07 /dev/null

The process was /home/core/pypy/bin/pypy, which lead to an ansible playbook that was run every 24 hours.
That means the problem was not caused by Flatcar Container Linux. Thank you for thinking along with us!


Generate command reference via cobra/doc

The framework we utilize allows generating markdown from the code to automatically document all command line options:
https://chromium.googlesource.com/external/github.com/spf13/cobra/+/refs/heads/master/doc/md_docs.md

Tried generating markdown from the example but hitting a dependency issue. Guessing it's because doc is a package in the already imported cobra. Will look for a workaround in the vendor conf.
make: Entering directory '/home/scanf/opt/og/src/github.com/cilium/cilium/cilium'
go build -i -ldflags '-X "github.com/cilium/cilium/pkg/version.Version=0.13.90 6a7d1459a48e Fri, 10 Nov 2017 18:47:25 -0800 go version go1.9 linux/amd64"' -o cilium
# github.com/cilium/cilium/cilium/cmd
cmd/root.go:47:28: cannot use rootCmd (type *"github.com/cilium/cilium/vendor/github.com/spf13/cobra".Command) as type *"github.com/spf13/cobra".Command in argument to doc.GenMarkdownTree
make: *** [Makefile:6: cilium] Error 2
make: Leaving directory '/home/scanf/opt/og/src/github.com/cilium/cilium/cilium'


make failed ---undefined reference to symbol 'sem_post@@GLIBC_2.2.5'

Linking CXX executable ngram_query
[ 28%] Built target ngram_query
[ 28%] Building CXX object klm/lm/builder/CMakeFiles/dump_counts.dir/print.cc.o
[ 28%] Building CXX object klm/lm/builder/CMakeFiles/dump_counts.dir/dump_counts_main.cc.o
Linking CXX executable dump_counts
/usr/bin/ld: ../../util/stream/libklm_util_stream.a(chain.cc.o): undefined reference to symbol 'sem_post@@GLIBC_2.2.5'
//lib/x86_64-linux-gnu/libpthread.so.0: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
make[2]: *** [klm/lm/builder/dump_counts] Error 1
make[1]: *** [klm/lm/builder/CMakeFiles/dump_counts.dir/all] Error 2
make: *** [all] Error 2

Did you try this commit? https://github.com/redpony/cdec/pull/82

It works, please commit it!


Dolishnii/social group error

Supposedly have fixed the SocialGroup error (pls make sure that I actually have).

@VadymLevkovskyi requesting a review


Better titles for browser tab

I'm not very familiar with hugo so I'm not sure I'll be able to help here, but I would like the title of the page (shown in the browser tab) to change when selecting different pages in the site.
For example when clicking "sponsors" I would like the chrome tab header to say MapLibre -Sponsors instead of Maplibre - MapLibre.
@maxammann is this possible and simple?
The following should say Maplibre - Home

The following should say MapLibre - Community

You get the point...

Yeah I can fix that when I have time. Definitely possible

I can probably send a PR if you direct me to the right location

For some reason the .Title here refers to the sites title instead of the page's title:
https://github.com/maplibre/maplibre.github.io/blob/main/layouts/partials/head.html#L40
That could be because no page titles are set maybe.

Is it paddocks that it's related to lower case vs upper case? I see that the title is defined in lowercase but the template has this in upper case. Not sure how relevant my observations are though.


IPFS Desktop Crash

Please describe what you were doing when this error happened.
Checking for updates
Specifications

OS: darwin
IPFS Desktop Version: 0.15.1
Electron Version: 12.0.5
Chrome Version: 89.0.4389.128

Error
TypeError: ctx.manualCheckForUpdates is not a function
    at click (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/tray.js:216:30)
    at MenuItem.click (electron/js2c/browser_init.js:73:1742)
    at Object.a._executeCommand (electron/js2c/browser_init.js:81:2492)

@unbeatable-101 can you please attach your logs?

From the "IPFS icon" menu in your menubar/system tray, go to Advanced → Open Logs Directory (for Linux users who do not have this menu, logs can be found in $HOME/.config/IPFS Desktop )
Find *.log files
Attach error.log and combined.log to this issue.

combined.log
error.log

I don't know, since I have been using https://github.com/ipfs-shipyard/go-ipfs-desktop.
I'll download again and see.

It doesn't seem to happen


Allow parse to handle rational literals

e.g.
⋕ "1/2"
⋕ "π/4"
⋕ "3.14/2.718"
⋕ "-2/3"
⋕ "4/-5"
⋕ "-7/`6"

Great, thanks!


asciidoctor.css Unexpected missing generic font family in stylesheet

We are using the asciidoctor.css stylesheet we found in your project to help with the vscode-didact project (https://github.com/redhat-developer/vscode-didact) and while working through some issues reported by SonarCloud, I received the error: Unexpected missing generic font family
on this line: https://github.com/darshandsoni/asciidoctor-skins/blob/71ce8dcd401600985dcce7b78d5b5d8b20a0a52d/css/asciidoctor.css#L234
.verseblock pre{font-family:"Open Sans","DejaVu Sans",sans;font-size:1.15rem;color:rgba(0,0,0,.85);font-weight:300;text-rendering:optimizeLegibility}

Here's a bit more about the issue: https://rules.sonarsource.com/css/RSPEC-4649
It appears that 'sans' is not a globally accepted font name, but 'sans-serif' is.

@bfitzpat You might want to take a look at #37, specifically the recommendation to not use the current asciidoctor.css stylesheet in this repo (which we are in the process of replacing as per the instructions below):

use the following URL to retrieve the default stylesheet for the latest release directly from the GitHub repository:
<EMAIL_ADDRESS>If you want to link against the development version instead, you can use this URL:
<EMAIL_ADDRESS>
I would suggest replacing the stylesheet you are currently using with one of the links above and seeing if that resolves your issue.

Thanks @dohliam  -- I'll take a look!

Closing this issue as an unneeded fix. Thanks @dohliam !


Value names of BlockRotation enum are not entirely accurate to what they are used for

So the values imply that they're in increments of 90 or 180 degrees but they don't often seem to be used for that. I would suggest dropping the 90 from CLOCKWISE_90 and COUNTERCLOCKWISE_90 since they are used for that in general. I don't know what CLOCKWISE_180 could be renamed to; maybe REFLECT or something?

Perhaps INVERT?

MIRROR?

It seems as though I misspoke; They do only seem to be used for increments of 90 degrees.

Unfortunately, this issue is invalid because these field names are auto-generated from bytecode clues (enum names in ldc)


Manage temperature sensor ?

Hello,
Thank you for you job !
All work well exept my temperature sensor.
I'm able to retrieve the battery level or strength of the signal in home assistant for the temperator sensor device but I don't have the temperature measured.
Did I do something wrong when setting up the integration by selecting the wrong sensor type?
If yes, is it possible to modify later a Jablotron sensor type within the integration with HA.
If not, is this a known problem?
Thanks for your answer :)

Did I do something wrong when setting up the integration by selecting the wrong sensor type?

There's no support currently because I don't have any temperature sensor. If you are willing to help us on Discord we may add to feature in the future.

If yes, is it possible to modify later a Jablotron sensor type within the integration with HA.

There's no UI but you can do it in .storage/core.config_entries


VMS: add alias macros to avoid 31 character symbol name limit warning

Affected symbol names:
generate_stateless_cookie_callback
verify_stateless_cookie_callback

Merged.  ca1ed2904e9235deb8bf2d32629c6a49b61bf7c0