Group member check seems too restrictive when combining mnemonics

If I understand things well the "not equal" check here https://github.com/trezor/python-shamir-mnemonic/blob/c919df7217d0f268e5830ec845c043f0a63b172c/shamir_mnemonic/shamir.py#L425 should be change into a "less than" check (and raised error message changed)
This would allow the following code to work :
mnemonics = shamir.generate_mnemonics(1, [(3, 5)], b"012345678901234567")
recovered = shamir.combine_mnemonics(mnemonics[0])

If I understand spec well and sss, the threshold is the mimimum share count needed to decode the secret, so it should be allowed to pass more shares.

I think you are right.
Workaround: If you have more shares than threshold, just pass the threshold shares to the library.
@andrewkozlik what do you think? Should we update the code in the library? It's reference implementation, so I think it makes sense.

should be change into a "less than" check

That's what I initially implemented. I recall that there was then a team discussion where it was decided to be strict about the number of shares provided. I can't remember the rationale for this change, since as I recall I didn't really agree with it.
I also previously had code which would automatically discard groups that are smaller than the group threshold, which I also removed in the same commit. The best that I can recall about the rationale is that the team came to a stance that the code shouldn't be too smart about processing the inputs, i.e. removing redundant information.
The commit message reads:

Update code, tests and vectors in accordance with the new requirement that the number of shares provided is equal to the threshold.

https://github.com/trezor/python-shamir-mnemonic/commit/06536e07c5810ffbd7337fe946558f5d11b16c6e#diff-bf3a7a9b0eedc233dfb28dd6bc7a662ae215fdf226b45f007628a7cdb6bead2fL678
Fun fact. On this pair of lines I had as a unit test exactly the code that @jfburdet is proposing:
https://github.com/trezor/python-shamir-mnemonic/commit/06536e07c5810ffbd7337fe946558f5d11b16c6e#diff-4c8758012944fc05228df26dd8616d92c721fa8ff87a521b8dd42f1493c27a88L19-L20

Functionally, changing the threshold check to a "less than" check is perfectly OK if all entered shares are correct.
The only issue that I can think of when the user enters shares above the threshold is if one or more of the shares is invalid. Say the threshold is 3 and the user enters 4 shares, 3 of them are correct and 1 is invalid. The code will try to interpolate all 4 and fail with Invalid digest of the shared secret.. The current solution forces the user to pick exactly 3 shares. If the user had tried entering different subsets of 3 shares instead of all 4, then they would eventually pick the 3 correct ones and recover their wallet correctly.
Of course this process of trying to pick subsets of size threshold when extra shares are provided can be automated. In the worst case scenario (threshold = 8, share_count = 16) this means going through 12870 combinations, which is not a big deal. I think I also proposed this in 2019, but we decided against it, probably on the grounds that brute-forcing the correct subset doesn't belong into the reference implementation. It something that shouldn't be happening automatically behind the user's back. It's more appropriate as a higher-level feature, possibly of the CLI.
@matejcik any thoughts?

The only issue that I can think of when the user enters shares above the threshold is if one or more of the shares is invalid

I'm pretty sure that this is it.
OTOH this seems to be before the 0.2 API rework, in particular, before ShareGroup was a thing. With the current API this is neatly solvable: introduce a "group validity" concept and change this whole loop into:
for group in groups.values():
    group.validate()

(and then later, if desired, we can call get_minimal_group(), which already exists, for passing into the _recover_secret() call)
one more thought: is the validity a property of a single share, or of the whole group? (or both?)
as in, there is an individual per-share checksum, but can a share with a valid checksum still be "invalid" with relation to the group, and if so, can we detect that?

is the validity a property of a single share, or of the whole group? (or both?)

I'd say both.
The shares are protected against accidental errors by a very strong per-share checksum. However, a malicious shareholder or attacker could supply the user with a malformed share that satisfies the per-share checksum but breaks the group checksum. There is no easy way to detect which share is the bad one. We can only detect that a bad share is present in the subset. So if we get threshold good shares and some bad ones, then we can determine the good ones by combining different subset of size threshold until we succeed. If we have less than threshold good shares in the set, then there is no computationally feasible way to tell which ones are the good ones.

Reviewing the code, ShareGroup.add() takes a Share instance, which can't be created from a share with invalid checksum, so this part of the code is sound.
And the _recover_secret() will accept all shares -- possibly more than threshold -- but raise if the group checksum does not match. If there is an attacker handing out malicious shares, there is no guarantee that we can do anything about it even if we do the subset thing.
This makes me think it's safe to implement the original suggestion of changing != to <, and possibly doing something about the group checksum error message.


sendDocument results in empty json (max files limit reached ??)

Anybody else had issues with sending files after a while ?  It seems I have ran into some limit due to amount of files i guess. This only happens with a specific bot token, with anothert it works fine. Is there any restriction on maxiumum amount of files sent ?
Traceback (most recent call last):
File "/usr/local/lib/python3.4/dist-packages/telepot/api.py", line 110, in _parse
data = json.loads(text)
File "/usr/lib/python3.4/json/init.py", line 318, in loads
return _default_decoder.decode(s)
File "/usr/lib/python3.4/json/decoder.py", line 343, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python3.4/json/decoder.py", line 361, in raw_decode
raise ValueError(errmsg("Expecting value", s, err.value)) from None
ValueError: Expecting value: line 1 column 1 (char 0)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.4/dist-packages/telepot/init.py", line 871, in collector
callback(item)
File "bot.py", line 114, in handle
bot.sendDocument(chat_id, document=open('some_file_which_exists', 'rb'))
File "/usr/local/lib/python3.4/dist-packages/telepot/init.py", line 507, in sendDocument
return self._sendfile(document, 'document', p)
File "/usr/local/lib/python3.4/dist-packages/telepot/init.py", line 466, in _sendfile
return self._api_request(method, _rectify(params), files)
File "/usr/local/lib/python3.4/dist-packages/telepot/init.py", line 434, in _api_request
return api.request((self._token, method, params, files), **kwargs)
File "/usr/local/lib/python3.4/dist-packages/telepot/api.py", line 131, in request
return _parse(r)
File "/usr/local/lib/python3.4/dist-packages/telepot/api.py", line 112, in _parse
raise exception.BadHTTPResponse(response.status, text, response)
telepot.exception.BadHTTPResponse:

I have the same issue, how to solve it?


Needles ports in Envoy configuration in virtual host domains

Remove hosts:port in the domains generation.
Virtual host matching in Envoy does not consider port. Port matching is performed at the Listener and FilterChainMatch stage. By the time Envoy processes RouteConfiguration, the port is ignored.
Example:
"route_config": {
"name": "9080",
"virtual_hosts": [
{

  "name": "ratings.default.svc.cluster.local:9080",

    "domains": [

     "ratings.default.svc.cluster.local",

     "ratings.default.svc.cluster.local:9080",   *** to be removed

     "ratings",

     "ratings:9080",  *** to be removed

     "ratings.default.svc.cluster",

     "ratings.default.svc.cluster:9080", *** to be removed

     "ratings.default.svc",

     "ratings.default.svc:9080", *** to be removed

     "ratings.default",

     "ratings.default:9080", *** to be removed

     "<IP_ADDRESS>",

     "<IP_ADDRESS>:9080" *** to be removed

    ],

....

Thank you for creating this. I list the main blockers here. I have less knowledge at istio flows and use cases so please add what's missing.
[x] Split inbound capture port and outbound capture port
[ ] Better LDS: the ability to drain partial of the filterchains(currently envoy could only drain a full listener). A milestone of FilterChainDiscoveryService
[ ] Use separate FilterChainMatcher for inbound and outbound listener. Motivation: Avoid share not-bind-to-port listeners. Align with the goal of deprecating these listener spec at envoy community.
Alternative solutions: Below are not designed to resolve the issue here but could be utilized to solve.
k8s-CNI. Protocol-sniff.

@andraxylia does envoy actually completely ignore the port?

If you have domains: [ foo.com ] and I send curl foo.com -H "Host foo.com:80" will it match?
If you have domains: [ foo.com:9090 ] and I send curl foo.com -H "Host foo.com:80" will it match?

Related to envoyproxy/envoy#886

Thanks Andra, it sounds like the port is still required from that though?

The port is required, otherwise curl foo.com -H "Host foo.com:80 will fail

If you have domains: [ foo.com ] and I send curl foo.com -H "Host foo.com:80" will it match?

No.

If you have domains: [ foo.com:9090 ] and I send curl foo.com -H "Host foo.com:80" will it match?

No.
The port is required (Envoy performs exact match against Host / :authority headers), but please leave the port-less virtual host as well, since reverse proxies usually don't append port to the Host header, so you might see Host: foo.com on port 9090.


⚠ Bofrost.be has degraded performance

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

HTTP code: 200
Response time: 841 ms

Resolved: Bofrost.be performance has improved in 42a070c.


Clarification on pipe() + non-operators

As mentioned in #2995, the pipeable operators docs state:

The former toPromise() "operator" has been removed because an operator returns an Observable, not a Promise. There is now an Observable.toPromise() instance method.

Hoever, pipe does (imo rightly) work with non-operators:
typeof of(1,2,3).pipe(() => 5) // "number"

Since the idea is to eventually move to |>, I'd really love for the documentation to be clear it's a supported usage and for the type defs to be updated accordingly. ❤
RxJS version: 6.0.0-alpha

Your're totally right.
The problem was (in the short term) that many users were very confused by source.pipe(map(fn), toPromise(), filter(x => x)), for better or worse. So I was trying to get people to think in terms of "piping" operators, and not further complicate things by having them pipe to other types.
Maybe my babying there is a little over zealous.
There's, of course, also the matter of TypeScript typings, and how to get proper inference through there, pipe already has some issues in that department.
I'll try to figure something out soon.

Awesome, thanks @benlesh!

:+1:


make text movable

Closes #70

There is a missing newline in almost every new method and missing spaces around '@'. I believe you left them on purpose in order to test the auto-refactoring?
A class comment should be added anyway.

I can confirm that I, while doing this with @johannes-poetzsch, did not care about those because I knew we had the auto-refactor.
But you are right that there are some things we did not do yet, one of which is the class comment.


RuntimeError: CUDA error: CUBLAS_STATUS_EXECUTION_FAILED when calling cublasGemmEx( handle, opa, opb, m, n, k, &falpha, a, CUDA_R_16F, lda, b, CUDA_R_16F, ldb, &fbeta, c, CUDA_R_16F, ldc, CUDA_R_32F, CUBLAS_GEMM_DFALT_TENSOR_OP)

I found an error
RuntimeError: CUDA error: CUBLAS_STATUS_EXECUTION_FAILED when calling cublasGemmEx( handle, opa, opb, m, n, k, &falpha, a, CUDA_R_16F, lda, b, CUDA_R_16F, ldb, &fbeta, c, CUDA_R_16F, ldc, CUDA_R_32F, CUBLAS_GEMM_DFALT_TENSOR_OP)``
when attempting to call the run the sample code provided in the ReadMe,:
`from big_sleep import Imagine

dream = Imagine(
    text = "fire in the sky",
    lr = 5e-2,
    save_every = 50,
    save_progress = True
)

dream()`

The error seems to have occurred here:
File "D:\Anaconda\lib\site-packages\torch\nn\functional.py", line 1753, in linear     return torch._C._nn.linear(input, weight, bias)
Does anyone know why this would occur? I am running my code on a 64 bit Windows 10 laptop with a GeForce GTX 1660 Ti Graphics Card

I am gettind the same error.

Having the same error utilizing a 1660 Super. Thinking it may have something to do with the GPU.

I fixed it by reinstalling pytotch

Having this issue on Debian with my GTX 1660 Super. Reinstalling pytorch did not help.

Got this issue too, using the default CLI, not a .py file with my parameters. How to fix it?


Add inscriptions and change supply.

Add inscriptions and change supply.

outdated pr. later update in pr #2077 was already merged.


(maint) Change run_puppet max_timeout param to timeout_seconds

In the next versions of PE, this parameter will change from max_timeout to timeout_seconds.

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


Include required HTML5 meta tags

Help prevent garbled text by specifying UTF-8 encoding
Include compatibility mode trigger for IE

Thanks!


Getting error

I am getting error "Failed to download resource "jemalloc_bottle_manifest" while installing ffmpeg by brew. any suggestion? Thanks a lot.

Hi, instead installing ffmpeg on your machine I ussualy use ffmpeg-static and ffprobe static
And the I use it like these :
const Ffmepg = require('fluent-ffmpeg')
const ffmpegStatic = require('ffmpeg-static')
const ffprobeStatic = require('ffprobe-static');

ffmpeg.setFfmpegPath(ffmpegStatic)
ffmpeg.setFfprobePath(ffprobeStatic)


Add struct sockaddr_dl for macos and freebsd

Freebsd: https://github.com/freebsd/freebsd/blob/master/sys/net/if_dl.h#L59
Macos: https://github.com/apple/darwin-xnu/blob/master/bsd/net/if_dl.h#L95

Thanks! Looks like the FreeBSD CI builder is failing though?

@LuoZijun You probably need to add the sys/net/if_dl.h header during the build script for FreeBSD builds to make sure this struct is visible (see https://github.com/freebsd/freebsd/blob/82974662ad9f9ece5f8374d2c898e83bd03aece9/sys/net/if_dl.h). You can look through libc-test/build.rs for where to do this.

:umbrella: The latest upstream changes (presumably #867) made this pull request unmergeable. Please resolve the merge conflicts.

@Susurrus okay.

@alexcrichton ping ...

I think the current styling is to have commas after every field in a struct.

@Susurrus okay, i have fix that code style.
but macos libc-test is failure.
i have no idea for that.

@Susurrus okay, it's done.

@alexcrichton all green.

@alexcrichton ping ...

:pushpin: Commit 64246e0 has been approved by alexcrichton

@bors: r+
Thanks!

:hourglass: Testing commit 64246e006edca0c78a1c2c69d3ae8b7aff4d3c2f with merge 385a82275adff0d7d2afca70488403578d99e0fd...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 385a82275adff0d7d2afca70488403578d99e0fd to master...


Build from local Dockerfile

Hey,
Just a quick note asking if building images from a local Dockerfile was on your roadmap? From what I can see, that is not currently supported. To be clear, what I mean is creating a GenericContainer from a Dockerfile that you keep within the repository itself.

Hey @JimNero009
I had a similar requirement last week but I opted to build and push the image to DockerHub instead.
I didn't think it was the responsibility of testcontainers to build the image as the API could get quite complex (build args, etc).

Hi Christian,
Thank you for your answer. The reason I ask is because I see that the Java library has support for this, and the Python library has similar support (in the context of a docker-compose file, in any case) so it seemed a logical extension to include it here. I personally think it would be an incredibly powerful feature that would allow node developers everywhere to properly test artefacts they are producing before pushing it anywhere, speeding up iteration time.
Just food for thought :)

Hey @JimNero009
I've started work on this feature. What do you think about the following API:
const { GenericContainer } = require("testcontainers");

(async () => {
  const context = "/src";
  const src = ["Dockerfile", "index.js"];
  const imageName = "my-custom-image";
  const tag = "1.0.0";
  const container = await GenericContainer.fromDockerfile(imageName, tag, context, src);

  const startedContainer = await container
      .withEnv("KEY", "VALUE")
      .withExposedPorts(8080)
      .start();

  await startedContainer.stop();
})();

Hey @cristianrgreco -- sorry for the tardiness of my reply.
I think we're looking pretty good with that! A couple of suggestions:

Is it really necessary to have an image name and tag seperated like that? Since this is a container being built from a local Dockerfile, I think an optional parameter that specifies an image name for later reference is sufficient here. In the use cases I'm thinking of, knowing the name of the container I've created is irrelevant and should be abstracted away from me.
If I'm understanding correctly, you are explicitly passing in a list of file names that the Docker deamon needs to build the image from the Dockerfile? I quite like that, but seeing as there is a strong convention for dockerfiles to be called 'Dockerfile;, there is maybe something we can do around defaults here.

For my understanding, where is the path passed into 'context' relative to? I can imagine it making sense to be relative to a project root.
Nice work, and super glad you've decided to look at this feature :)

Hey @JimNero009,
Thanks for the feedback, both great points.
In terms of the first point, if the name of the container is abstracted away, does it make sense to keep the image once the application has terminated? I see that the Java port of testcontainers will auto-delete the image by default on shutdown, wondering if we should do the same?
For the second point, after having gotten feedback from members of the Java port of testcontainers, I think I'll be changing this so you just provide a context path, and we use all the files in that directory. I think it makes sense because the Dockerfile already specifies what should be copied into the image.
The path can be either relative or absolute, I was thinking it could be used like this:
const context = "/tmp";  // absolute path in the FS
const context = path.resolve(__dirname, "dir") // relative from the current directory of the node module

Hello! First of all, your implementation of testcontainers is amazing. Thank you so much for all of your work. I just wanted to ask about this feature (building from local Dockerfile) and see if you have an ETA for when it will be completed. It seems like it will be super awesome.

Hey @JimNero009, @ebenson6295,
Thanks for the positive feedback!
This feature is now available in version 1.1.19.
Example usage from the README:
const path = require('path');
const { GenericContainer } = require("testcontainers");

(async () => {
  const buildContext = path.resolve(__dirname, "my-dir");

  const container = await GenericContainer.fromDockerfile(buildContext);

  const startedContainer = await container
      .withEnv("KEY", "VALUE")
      .withExposedPorts(8080)
      .start();

  await startedContainer.stop();
})();

Hey, thanks for the awesome package! ❤
I'm using the GenericContainer.fromDockerFile API, trying to give the built image a name and tag so I can avoid rebuilding the image every test run.
Correct me if I'm wrong, but I quickly looked through the codebase and I don't think it's possible atm?


Generate documentation for File singleton methods

Description
When generating documentation from the Ruby source, some File methods do not get parsed into the yardoc.
Steps to reproduce
This is the minimal reproduction for the issue. I've done my best to remove
all extraneous code and unique environment state on my machine before providing
these steps:

Run the following command in the Ruby source: yardoc *.c
Run yri File.exist?

Actual Output
No documentation for `File.exist?'
Expected Output
The documentation from the source code.
Solution
In the Ruby core, file.c uses define_filetest_function() to define certain File singleton methods, including File.exist? YARD's C parser doesn't find them.
This PR modifies YARD::Handlers::C::MethodHandler to process define_filetest_function.
Completed Tasks

[X] I have read the Contributing Guide.
[X] The pull request is complete (implemented / written).
[X] Git commits have been cleaned up (squash WIP / revert commits).
[X] I wrote tests and ran bundle exec rake locally (if code is attached to PR).

Coverage decreased (-0.03%) to 93.613% when pulling a3f4f4ab2eed36bfa5d11f367a753057ecd78281 on castwide:file_singleton_methods into c26eedab6eb3832e91c8fd745ef3e05da4c9a45e on lsegal:master.


Add new __idiv metamethod

Changes

Adds the new __idiv metamethod to the metamethod table.

https://create.roblox.com/docs/release-notes/release-notes-593
https://github.com/Roblox/luau/blob/master/rfcs/syntax-floor-division-operator.md
Checks
By submitting your pull request for review, you agree to the following:

[x] This contribution was created in whole or in part by me, and I have the right to submit it under the terms of this repository's open source licenses.
[x] I understand and agree that this contribution and a record of it are public, maintained indefinitely, and may be redistributed under the terms of this repository's open source licenses.
[x] To the best of my knowledge, all proposed changes are accurate.

@aetter
This now seems to have been enabled,

Thank you @lolmansReturn! I've been checking this week over week and am glad to finally see it get in. I also appreciate how you matched our nonsensical indentation style on the table. 😄


[11.0.x] ISPN-12184 Don't override explicit authentication mechanisms

https://issues.redhat.com/browse/ISPN-12184

A green build !

@tristantarrant is this updated with the comments I made for the master PR? or I need to review this one? :)

Yes, I believe I've backported all the relevant ones (a lot of the changes were in the multi endpoint code)

integrated! thanks @tristantarrant !


Not able to install

The readme doesn't say anything about npm install sqlagent/mongodb
Use npm install sqlagent followed by npm install mongodb

The readme doesn't say anything about npm install sqlagent/mongodb
Use npm install sqlagent followed by npm install mongodb


[Firefox] Releasing mouse over a button after dragging sash causes button click

Found in Firefox (v126): Using the demo at https://allotment.mulberryhousesoftware.com/
Drag the divider between allotment.tsx and allotment.module.css to the left and keep the left mouse button depressed until it's over the a file listing (such as allotment.tsx) then release the mouse.
This results in a new pane being opened for allotment.tsx
This behavior does not happen in Chrome.

@laurenga Thanks for reporting this. I can reproduce it so that's a good start!
I can't commit to a timescale for fixing this. There's a chance it's really simple, but there's also a good chance it's a tricky browser behaviour thing, e.g. https://github.com/w3c/pointerevents/issues/75.
I'll also consider adding an onDrag callback to accompany the onDragStart and onDragEnd callbacks

Thank you for taking a look. I'm hopeful it's something simple. I wonder if event.preventDefault() on the drag event is enough to help with it.


Add : Nikhil Bhange

Description

Related Issues

Changes Proposed

Checklist

[x] I have read and followed the Contribution Guidelines.
[x] All new and existing tests passed.
[x] I have updated the documentation to reflect the changes I've made.
[x] My code follows the code style of this project.
[x] The title of my pull request is a short description of the requested changes.

Screenshots
Note to reviewers

I am a passionate developer with experience in building web applications using modern technologies.


download youtube audio

Description
Accept YouTube video link and download audio file

Type of issue

[X] Feature (New Script)
[x] Bug
[x] Documentation

Checklist:

[x] I have read the project guidelines.
[x] I have checked all the existing projects, before submitting a new project issue.
[x] I have checked previous issues to avoid duplicates.
[x] This issue will be meaningful for the project.

I can do this. Can you assign me this issue?

I would like to work on this.

I would like to work on this, i have previousely worked on python projects related to audio seperation from videos and have created plugins

I would like to work on this, i have previousely worked on python projects related to audio seperation from videos and have created plugins

This issue has been assigned already

@AdityaJ7 Thank you for assigning me! I have started working on it, I think this project will need some time, what is the time limit for completing this? I'll update you regularly.

Hey, I'd love to do this task!

@AdityaJ7 Thank you for assigning me! I have started working on it, I think this project will need some time, what is the time limit for completing this? I'll update you regularly.

Complete before 7 days

Hey, I'd love to do this task!

Hi @Vyprath thanks for showing interest in this issue but it has already been claimed by someone else, please check other unclaimed issue or create your own issue if you think our repos are , missing any script
Thanks

@AdityaJ7 Thank you for assigning me! I have started working on it, I think this project will need some time, what is the time limit for completing this? I'll update you regularly.

Complete before 7 days

Yes, I think that is enough!

Please give me some more time.

I have submitted a pull request. Please check and sorry for the delay.


Create GUI for sshnoports for windows/linux/macos

### MVP Release tasks
- [x] 1. GUI config file management
- [x] 1.1. syncing using atServers (with a last updated time to prevent conflicts)
- [x] 1.2. Import/exporting from local filesystem to sandbox
- [x] 2. Talk to Gary
- [x] 2.1. Pure Dart SSH (@gkc as part of v4.0.0 changes)
- [x] 2.2. Implement Background Sessions in GUI
- [x] 2.2.1. Lengthen timeout for sshnp gui ~
- [x] 3. Error Messages
- [x] 3.1. When bad connection info is supplied
- [x] 3.2. When daemon timeout / is offline
- [ ] 4. Unit tests for sshnp
- [x] 5. GUI private key file management

A partner requires a GUI for sshnp, that can also forward ports without any ports being needed to be opened on the device or firewalls.

[x]  Create MVP
[x] Design Nicer GUI
[ ] Code final product
[ ] Automate testing
[ ] Launch

Some useful material in this document
Key enabler: since advent of the rendezvous service, sshd does not need to run on the client. Therefore we can run a client on any platform as we just need an ssh client
Functionality of the GUI needs to include something like the "Tunnel" section of the Putty app (Source, Destination, and local or remote)

Setting priority to P0 as this needs to get done during this sprint. Removing the SP estimate so we remember to discuss during sprint planning

Figma Here's where I'm working!

A little more in the ways of the base code for sshnp to get this over the hump, but config files are there which means we should be able to get started.
Ideally the GUI reads ~/.sshnp/config/* for all of the various config files saved to the device, then only gets the ones where "FROM" matches the currently onboarded atSign. Alternatively (or in addition), these same config files are stored on the atServer so that your config follows you to your other machines.

@CurtlyCritchlow Please can you provide an update on this ticket and also this other ticket

PR #306 provides the necessary methods to read in all of the config files which contain this information. I will also write the code to write a file for the add new connection

Update: we can ssh from the GUI app. To complete the MVP we had to display the string printed to stdout upon success in the UI.

Increasing the SPs as I will be focusing on this in PR70

A short task list for my focuses:

[x] Refactor home screen controllers to enable proper file management
[ ] Implement terminal screen controllers to enable multiple terminal windows (terminal process/ssh instance management)
[ ] Implement dynamic navigation controller to enable multiple terminal navigation (UI navigation management)
[ ] Pure Dart SSH

UI design of the key management has been completed. The design implementation was started in PR74 and will continue in PR75.

The UI design for macOS app has been mostly completed. Pending is the onboarding screen. The next activities are to complete the onboarding/landing screen, unit test, widget test and update the app to use the latest version of sshnoports.

The above mentioned activities are still in progress.

The onboarding screen has been completed, Private key management functionality has been added. Pending activity is to pass the private key properties to the dart.ssh client to ssh to a remote device.

Hi @CurtlyCritchlow we have a launch date of Jan 19th on the GUI, is that still accurate?  :-)

Looking to pushed to test flight by Jan 17th. We'll still have to do user testing, so not ready for an official launch to production but would be ready for early adopters if the team decide to make it available to them.

App was pushed to test flight for testing. This sprint it will be pushed to windows dashboard for testing (already started). Updates and big fixes based on preliminary testing are. Adding keybindings, make hung shell non blocking

Awesome @CurtlyCritchlow congrats!

Duplicate of #717


Initial Implementation for Conversion of SWIFT MT to ISO 20022

Purpose
The purpose of this initial implementation is to create a foundational framework for converting SWIFT MT messages to the ISO 20022 XML format. This will enable organizations to transition more efficiently from the traditional SWIFT MT standard to ISO 20022, aligning with the latest industry protocols for financial messaging.
Goals
The goal of this implementation is to provide accurate and reliable mappings between SWIFT MT and ISO 20022 message fields, ensuring data integrity and compatibility across systems. This conversion tool aims to facilitate seamless integration with ISO 20022, laying the groundwork for further enhancements and supporting additional message types as industry needs evolve.

Language changes are LGTM


FORMS-5839 - Add datalayer support to CC Adaptive Forms

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

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

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes and the overall coverage did not decrease.
[ ] All unit tests pass on CircleCi.
[ ] I ran all tests locally and they pass.

@sauraku , pls share the schema for each component going as part of data layer as part of this review.

It seems that the data layer schema is going via this PR: https://git.corp.adobe.com/livecycle/af2-docs/pull/173/files
I've added all the changes I've made so far in this JIRA: https://jira.corp.adobe.com/browse/FORMS-5839
I'll add them to the a wiki once the changes are finalized.


Create Documentations for  Constitutive, Instance Hyponym, Instance Hypernym, Antonym, Equal Synonym,Similar

Create Documentations for;

Constitutive,
Instance Hyponym,
Instance Hypernym,
Antonym,
Equal Synonym,
Similar

Did #49 resolve the issue? If so, can this be closed?

Yes, #49 resolve the issue.
On Tue, Oct 20, 2020 at 12:53 PM Michael Wayne Goodman <
<EMAIL_ADDRESS>wrote:

Did #49 https://github.com/globalwordnet/gwadoc/pull/49 resolve the
issue? If so, can this be closed?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/globalwordnet/gwadoc/issues/46#issuecomment-712795587,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFPXA4DIAWCDTZLGMMM6S33SLV22RANCNFSM4SMPSOTQ
.

Great, I'll close it then


Async-safe client.Get() for all tests

What this PR does:
Many of the test flakes we currently see relate to fairly simple problems where calls to Get() and other methods of client expect to operate synchronously.
In fact, envtests and e2e tests both use "real" k8s clusters and are asynchronous systems. It would be more reasonable to expect async behaviour by default, which this PR does by creating a new k8s test client and overriding its Get() method with a Get() wrapped in an Eventually().
Test PR to see whether my idea of replacing all Get() calls with a new asyc-safe Get() works.
We see similar issues with the HTTP client, so this PR might form a basis for fixing both.
Which issue(s) this PR fixes:
Fixes #337 and others
Checklist

[ ] Changes manually tested
[ ] Automated Tests added/updated
[ ] Documentation added/updated
[ ] CHANGELOG.md updated (not required for documentation PRs)
[ ] CLA Signed:  DataStax CLA

Putting this on hold in favour of #378. Current status:

Reduced failing tests down to 4, but one is the envtests (which contain many subtests).
The approach mostly works, but for some reason specific calls still panic.
Next step is to try to eliminate the panics being thrown by async Get() (due to the eventually calls). A first attempt at hand coding a retry loop using channels and timers is in the commit above. Still needs work to ensure early return is happening correctly when UnsafeGetSync() call inside Get() has successfully retrieved an object.

I haven't been able to make progress with this. Closing and will work on it as time permits.


Fix some plural messages

This will fix some plural messages to be plural aware.
Tests: Not tested, based on logic.
Fixes #1922
Signed-off-by: Safa AlFulaij<EMAIL_ADDRESS>

@SafaAlfulaij: thank you for your contribution. But you must base your changes on the develop branch - not master (see https://github.com/vector-im/riot-android/blob/master/CONTRIBUTING.rst#how-to-contribute). Could you please update your PR?
It would be great if you can fix the conflict in the NotificationUtils.java file too.
By the way, you will have to sign off your PR (see https://github.com/vector-im/riot-android/blob/master/CONTRIBUTING.rst#sign-off) If you agree, all that's needed is to include the line in your commit or pull request comment:
Signed-off-by: Your Name<EMAIL_ADDRESS>

LGTM

https://github.com/vector-im/riot-android/blob/b70bda3a9cd9dd5462eae0a850aed61242c3fa82/vector/src/main/java/im/vector/adapters/VectorPublicRoomsAdapter.java#L86
https://github.com/vector-im/riot-android/blob/f8cea1c50d994bd3a4ab062df04f6a635b6d3927/vector/src/main/java/im/vector/fragments/VectorRoomDetailsMembersFragment.java#L848
https://github.com/vector-im/riot-android/blob/b70bda3a9cd9dd5462eae0a850aed61242c3fa82/vector/src/main/java/im/vector/activity/VectorRoomActivity.java#L3102
PLEASE DONT MAKE PUZZLE STRINGS :(
Even with READ:{} popup


TransitionListenerAdapter and NavigationTransitionListener classes not found exception with v2.3

Bug Information
Version Number of Plugin: 2.3
Device Tested On: Multiple Android devices ≤ API 25
Simulator Tested On: Multiple Android simulators ≤ API 25
Version of Xamarin: 4.8
Steps to reproduce the Behavior
Just use the package on an Android device running an Anroid API lower than 26, version where the missing class was added.
Devices running API 26 onwards have no issues.
Expected Behavior
No exceptions, like in version 2.2 an prior. Rollbacking to version 2.2 fixes the problem.
Actual Behavior
Starting from version 2.3, the following exception occurs and the app crashes : https://gist.github.com/toverux/c6cb85da2f41cb0fc64a574632360087

thank you for the report!
Wow... this is unexpected :( Maybe api 25 and lower does not support the listener, i have to check.
Do you confirm that the error is here even when the linker is disabled?

Hi, thanks for your answer! Yes, the exception also occurs with linking disabled.

Thanks for this report. I'm having same problem here.
Also downgraded to 2.2 and it's working fine.

welp... i wasn't using the support libraries for the listener!
Fixed in the next release


Rage flag causing unhandled CLI query error

Steps To Reproduce
Run ./scripts/dev-rome check --rage
Rome exits with:
Unhandled CLI query error
Error: rage() can only be called before a query has been dispatched

Expected Results
Rome should complete the command and create a tarball containing debugging information.

The condition on line 315 in Client.ts should be inverted.

Fixed by #791.


Homepage shelter popup on top. Must hand-test for integration with style changes.

Description

Addresses issue #37

Must be hand-tested with new popup style changes PR
On the home page, this should make the shelter popup sit on top of everything else. More visible, especially on mobile phones.
List of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[?] (Maybe with new styles) Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] This pull request relates to a ticket.
[x] This code is tested. (With master branch)
[x] I want my code added to the response theme.

@plocket do you want me to resolve the conflicts or would you like to do it?

@plocket As with #30, I think if you re-pull master to your fork and re-push the branch on the fork, it might get rid of the docs commit 8638b5a here.

I'll either fix the conflicts or make a new branch with the same changes.

Replaced by #49 .


Whitening update

Hi developers,
when I recently looked in detail at the whitening routine from NoisePy, I noticed that the tapered section is tapered separately from the whitened section of the input spectrum.
This has no consequence for the case where phase-only is chosen, because the amplitude of the main section is 1 and the amplitude of the taper where it connects to the main (untapered) part of the spectrum is also 1. However, for the case where spectral smoothing is used, this may introduce a jump in the fourier amplitude spectrum that may lead to high-frequency artefacts in the time-domain output.
I created an updated routine. This may have to be edited (for example, I used numpy rfftn rather than scipy). I also added a test to check that at least in the part where the signals are expected to be consistent, their respective error is small. Please, after review, remove the plotting statements in this test so that the test can be run without interaction.

P.S.: I suggested tentatively Xiaotao and Chenxin and reviewers, but if they do not have time or someone else has more time, feel free to change that!


Tree fails to load when using rarefied table from moving pictures tutorial

If you replace docs/moving-pictures/table.qza for this table from the tutorial everything works fine except the visualization fails to load with this error:
require-2.1.22.min.js:19 TypeError: Cannot read property 'x2' of undefined
    at Empress.getX (empress.js:217)
    at Empress.getCoords (empress.js:446)
    at Empress.drawTree (empress.js:210)
    at Empress.centerLayoutAvgPoint (empress.js:1174)
    at Empress.initialize (empress.js:203)
    at empress.html:312
    at Object.execCb (require-2.1.22.min.js:30)
    at ea.check (require-2.1.22.min.js:18)
    at ea.<anonymous> (require-2.1.22.min.js:23)
    at require-2.1.22.min.js:8

Just in case, here's the broken artifact.

I have a theory, does this happen if you pass the --p-no-filter-unobserved-features-from-phylogeny?

While working on #240 I wound into the same sort of error ("Cannot read property 'x2' of undefined"). In that case, the problem was caused by a node being set to undefined by accident, due to passing an invalid key to empress._treeData (since in JS an out-of-bounds index on an object is just undefined).
Not sure exactly what's going on...

I have seen this before and I think is because the expansion of the tree is not working properly. I'll take a look ... a quick fix is to not do shifting in the tree and pass unknown to the size.


Fix title on README - experiment with forked pr

The Issue

Fix title on README
Experiment with forked PR and tests

It worked @bmartinez287 !


Improve samples

[x] Code sample lines are too long, find a way to split code so users don't have to scroll horizontally. Consider also making variable names in code sample shorter
[x] Don't use explicit cast when using Response<T>

Also,
The Storage team has made SAS URI generation much easier.  Instead of using a *SasBuilder, the happy path scenario in the latest GA release of Blobs looks like:
var blob = new BlobClient(ConnectionString, ContainerName, BlobName);
await blob.UploadAsync(LocalFilePath);
Uri sas = blob.GenerateSasUri(BlobSasPermissions.Read, DateTimeOffset.UtcNow.AddDays(1));

We can look into this for the training samples instead of asking the customer to upload their files and create the SAS token

Created an issue for the Storage part => https://github.com/Azure/azure-sdk-for-net/issues/17746

Created an issue for the Storage part => https://github.com/Azure/azure-sdk-for-net/issues/17746


Add CountdownClock app

New app for a countdown clock. Displays time remaining in days/minutes/hours, with support for event passing.
First pass at Tidbyt and Github, so hopefully all goes well!

I have read the CLA Document and I hereby sign the CLA

retrigger

recheck

Issue with initial contribution. Will resubmit.


Won't you add UHV+ textures?

I don't know if such a question should be asked, I used machine translation, the tone may not be very good.

I assume you're here for the 1.12 one? Since I'm following the GTCEu Modern and UHV+ items are not yet implemented in it, I will be focusing on the Items available first!
I will eventually make it tho, just not on priority!

Is 1.20.2


[1 of 2] DCOS-8059: Change type key to fieldType

Reviewer: @MatApple

i know this is kinda messed up, but should we change the functionality to make it use type instead? this way, the Advanced Install modal will be able to take advantage of it with the universe package schemas

So you're suggesting we make this change to reactjs-components? I'm fine with that, just want to make sure I understand what you're suggesting.

you'd make the change here
similar to how the boolean does it a couple lines down. instead of looking in fieldProps.fieldType, it would look at fieldProps.type. this will allow us to build forms from legit schemas and use number fields.
what you would have to do is go through all the service-schemas and job-schemas and change all of the fieldType: 'number' to type: 'number'

@kennyt Makes sense! I'll do that.

Haha left the same comment as Kenny on Part 2 of this. Once we've verified all the schemas adhere to this change then lets 🚢 . Do we need the hold merge label till then?

@jfurrow ^^

@MatApple That discussion is continued here: https://github.com/dcos/dcos-ui/pull/614/files/a2404207b20927c8fad068302ccff13c3926aa21#r69782580 I believe this is ready to ship.

@jfurrow can you post a pic of Integration tests passing locally? :)

@MatApple for sure!


Allow any select statement for CREATE TABLE AS SELECT ...

Also fixes a semantics bug in the schema produced by some such statements.

This fixes https://github.com/dolthub/dolt/issues/1478


Docker Support

Add Dockerfile to build on Docker, then use it on CI/CD #2.

No longer needed because the project was transferred from Google Cloud Build to Circle CI.


Issue in running model for Street2Shop dataset

Thank you for the scripts to convert Street2Shop annotations to COCO format.
On running the scripts, although I am getting the number of images in 'gallery' as 0 for every category, and all available test images are  'user images'. Could you please confirm the numbers of the gallery images obtained?

There was a small bug, which may have caused the trouble. Now, it should be fixed.
Please make sure that you use proper paths to meta dir and the image folder with images in jpg format.


Enhance e.g. #software table with sortability

The tables for 'Software' are sorted on 'Total hits' descending.  When making a new release of a software it's more interesting to look at the 'Today' and 'Yesterday' hits numbers.  Obviously this can be done by eye, but it would be more convenient if a user could click on the requisite column heading to have the sorting switch to it (and toggle ascending/descending if already selected).
Obviously then either the Highchart pie chart would need some labelling or even better, switch to the selected column's data.
The same could be applied to the Schemas data table.

A potential alternative for this is jsGrid, which is a quick and easy way to get sortable, event-capable data grids. http://js-grid.com/ is the site. Using the static data source method (Just feed an array to data: ), getting a sortable grid is 21 lines of JS.

See https://github.com/EDSM-NET/EDDN/pull/104

The PR has long since been merged and working well.


Expose verisign exceptions

Coverage decreased (-0.03%) to 61.065% when pulling 8eef95b58ee535c9edab41f8cea5f1a4e6da67ca on castrapel:expose_verisign_exception into 4cc2befbfb1d5c704c0b7a672e3d0724b6a663fc on Netflix:master.

Coverage decreased (-0.03%) to 61.065% when pulling 8eef95b58ee535c9edab41f8cea5f1a4e6da67ca on castrapel:expose_verisign_exception into 4cc2befbfb1d5c704c0b7a672e3d0724b6a663fc on Netflix:master.


play button missing

Did you read the README?

[X] I have read the README, the theme is installed/configured correctly and the "Troubleshooting" section contains no information related to my problem

Do you have the latest versions of Spicetify, Spotify and Bloom?

[X] I'm using the latest versions of Spicetify, Spotify and Bloom

Is there already an issue for your problem?

[X] I have checked older issues, open and closed

Is your problem definitely caused by the theme?

[X] I have checked the app behavior without the theme and it is different

Environment & Computer Info
- Spotify version: <IP_ADDRESS>7.g36b715a1
- Installed from: spotify webiste
- Spicetify version: 2.25.3
- Color scheme: dark
- Extensions: x
- Custom apps: x
- Bloom installation method: github

Description
the play button is missing
Screenshots

however, works after i update spicetify version


Dev Portal rating not visible

Description:
Rating stars are not shown. see below image

Affected Product Version:
APIM 4.0.0 M7

for anonymous users, ratings are not shown either


Rename examples/widget_demo -> slider, textbox_demo -> textbox

'demo' feels redundant?

I tend to agree with you.


optional property paths (*, ?) are very slow

(Created from OWLIM-1104).
Prop paths using optional constructs (p? and p*) are extremely slow.
These paths alone are necessarily slow because they must return all nodes.
But nobody uses them alone, people always use them in combination with a non-optional path.
So one has to use workarounds, eg rewrite q/p? to q|q/p, to get good perfomance.
Use cases:

In Getty queries Vladimir Alexiev uses many rewritten patterns like this:

gvp:placeType/gvp:broaderGenericExtended? ->
gvp:placeType|(gvp:placeType/gvp:broaderGenericExtended)

In OWLIM-2627 Barry Norton suggests a similar but wordier workaround for BM data:

?x q/p? ?y ->
{?x q ?y} union {?x q ?z . ?z p ?y}

SHACL uses rdf:List for many of its constructs (sometimes unnecessarily) and uses rdf:rest*/rdf:first to unroll the list, eg see ClosedConstraintComponent.
Unless fixed, one can't use the SHACL SPARQL Definitions to implement SHACL in rdf4j

Another typical example is poor man's RDFS inference: rdf:type/rdfs:subClassOf*

American Art Collaborative discusses using rdf:List for "people depicted, with order". In this case a natural query would be
crm:P62_depicts/(rdf:rest*/rdf:first)?
but should be rewritten to
crm:P62_depicts | crm:P62_depicts/rdf:first | crm:P62_depicts/rdf:rest+/rdf:first

It seems to me that this can be fixed by internally rewriting to an alternative (union) path: one without the optional property and another with it.
p?/q -> q|p/q
p*/q -> q|p+/q
q/p? -> q|q/p
q/p* -> q|q/p+

Implementaton suggestion:

add a path characteristic "positive" (cannot be empty) vs "non-negative" (can be empty); the names are by analogy with integers.
design rewrite rules to produce alternatives where the positive path is always present, but the non-negative path alternates

More examples:
p?/q? -> ()|p|q|p/q

This alone will be slow since it's non-negative (() is the bad part), but when combined with a positive path, it can be made fast again, eg:
p?/q?/r ->
  r | (()|p|q|p/q)/r ->
  r | r|p/r|q/r|p/q/r ->
  r|p/r|q/r|p/q/r

necessarily slow

The reason is that ?x prop* ?y must return EVERY node:
every node is connected by a zero-length path of any prop to itself.

Some more thoughts on implementation.
First compute path nature (POS, NON) (see prop paths):

iri is POS
^elt is same
elt1 / elt2 is POS if either one is POS, else NON
elt1 | elt2 is POS if both are POS, else NON
elt* is NON
elt+ is same
elt? is NON
!whatever is POS (it's a path of length one)
(elt) is same

If the 2010 prop path language needs to be handled too:

(elt1 ^ elt2 is shorthand for elt1 / ^elt2)
elt{n,m} is NON if n=0 else is same
elt{n} is NON if n=0 else is same
elt{n,} is NON if n=0 else is same
elt{,n} is NON

Then the following rewrite rules are executed repeatedly.
pX are POS paths, nX are NON paths, qX are either, () is the empty path (which is NON).

Prioritize
Push POS paths to the left of alternatives (I assume they are evaluated left to right). This matters for LIMIT queries.

n|p -> p|n

Expand Alternatives
Push alternatives to the top level.

^(q1|q2) -> ^q1 | ^q2
q1/(q2|q3) -> q1/q2 | q1/q3
(q1|q2)/q3 -> q1/q3 | q2/q3
(q1|q2)* -> q1* | q2*
(q1|q2)+ -> q1+ | q2+
(q1|q2)? -> q1? | q2?
q* -> q+ | ()
q? -> q | ()

Simplify

q|q -> q
q/() -> q
()/q -> q

The expansion could create some consecutive iteration symbols that should also be simplified. But because such are allowed in original path, I guess there already is such simplification:
q** -> q*
q*+ -> q*
q+* -> q*
q++ -> q+
q*? -> q*
q?* -> q*
q+? -> q?
q?+ -> q?
q?? -> q?

I think that's all that's needed.

Eg if you try the rewrites on Use Case 5 above, you get this sequence
crm:P62_depicts/(rdf:rest*/rdf:first)? expand
crm:P62_depicts/(rdf:rest+|())/rdf:first)? expand
crm:P62_depicts | crm:P62_depicts/(rdf:rest+|())/rdf:first) expand
crm:P62_depicts | crm:P62_depicts/(rdf:rest+/rdf:first | ()/rdf:first) expand
crm:P62_depicts | crm:P62_depicts/rdf:rest+/rdf:first | crm:P62_depicts/()/rdf:first simplify
crm:P62_depicts | crm:P62_depicts/rdf:rest+/rdf:first | crm:P62_depicts/rdf:first
This is correct and fast enough. But the most natural way to write it is the fastest, because it finds the shortest paths first.
crm:P62_depicts | crm:P62_depicts/rdf:first | crm:P62_depicts/rdf:rest+/rdf:first
So I think we need these changes:
2. Prioritize
q|() -> ()|q
n|p -> p|n only if n != ()

Eliminate empties
()|... -> ... only if this alternative is at top level
This means that a query ?x p* ?y will be treated as ?x p+ ?y and will NOT return every node. This may fail some conformance test, but is exactly the wanted behavior (whoever wants to find all nodes in a repo?)

Possibly related is issue #689 , which turned out to be partly caused by a bug in binding retention, but also a related query optimization issue. We've improved query optimization for arbitrary-length paths in RDF4J 2.1.4 to the effect that the optimizer will almost always execute the zero-or-more part last (leading to most variables being bound already and therefore far less options to search through). I have not yet looked at your analysis in sufficient detail to figure out whether that corresponds with your findings, but in practical terms it might be good to try your slow queries with the new planner, and see if there's an improvement.

In addition to performance, it's important to return the shortest-path results first,
because that is the expected order (e.g. for list unrolling rdf:rest*/rdf:first).

I confirmed the issue exists in RDF4J 2.1.3, 2.1.6, and 2.2
Using the dataset http://vocab.getty.edu/dataset/aat/full.zip I had results similar to the following on each.
prefix gvp:http://vocab.getty.edu/ontology#
ask { ?x gvp:broader|(gvp:broader/gvp:broaderGenericExtended) ?y } # ~25ms
ask { ?x gvp:broader/gvp:broaderGenericExtended? ?y } # ~2500ms

It's been a while since I looked at this but we should investigate how the planner orders execution of the path elements and how it ensures that as much as possible, it executes paths with bound start or end points first.
As for output ordering: a SPARQL query result is unordered by nature, so any ordering that you rely on (other than an externally imposed one using an ORDER BY clause) is bound to give you problems in the future.

Also surprised that the issue still exists post 2.1.4 (and the fix for #689). Might be worth checking if that fix was somehow accidentally not included in later releases.

As for output ordering: a SPARQL query result is unordered by nature

It won't hurt to have a sensible order, esp for rdf:List

people who use rdf:rest*/rdf:first will get a nasty surprise if it's not
I would guess that Jena's list:member https://jena.apache.org/documentation/query/extension.html#property-functions returns them in order


Please release GHC 7.10.1 compatible version to Hackage

Fwiw, the Git-version seems to build fine, and also passes the testsuite with GHC 7.10.1

I fixed the build but forgot to push to Hackage. It's done now.

thanks!


Obs shape None when using environment HandReach-v0

Hi,
The code seems to work properly when using the Reacher-v2 environment. It fails when trying the new HandReach-v0, however. It is a MuJoCo-based environment for the Shadow Dexterous Hand.
I think it has something to do with the multiprocessing_env.py  file, since obs_shape always return None with this env. Also, is there a way to switch to "normal" processing with a single environment instance? If N_ENVS = 1, can it switch to a non-multiprocessing version of the algorithm?

Looks like the observation_space for HandReach-v0 is different than the usual environments. It returns a dict with multiple Spaces. Dict(achieved_goal:Box(15,), desired_goal:Box(15,), observation:Box(63,))

The fix is to make the new environments compatible with older ones, using
env = gym.wrappers.FlattenDictWrapper(env, dict_keys=['observation'])
Available at https://blog.openai.com/ingredients-for-robotics-research/


Add CI tests that install without -e

The current CI tests all install the package with pip install -e .. This doesn't fully test the packaging, because it roughly corresponds to adding the directory to sys.path. If there is a mistake in the manifest file or listed packages to install, it will not be caught.
We should add a job that installs with pip install ., without -e.
Prompted by a regression introduced in #38, which is fixed by #40.

@ltalirz I think running the test job in this way is enough. Is there a simple way to do this without copy-pasting the entire setup + job stage?


Replace local_action/wait_for with win_wait_for, when install on Windows.

Native win_wait_for module works better, and is not relying on dns requests, thus not require hostname to be resolvable.

Thanks!


Improve IP search

Due to the nature of the long format in the database you need to enter an exact and correct IP address to make the search work.
Is there any way for "fuzzy searches" like: 192.168 or 82.212.221?
/cc @confuser

Try using the % wildcard with a query?
So SELECT FROM db where ip = '192.168%'

Wont work - check the SQL structure. You can not fuzzy select that easily if it's a long data type.
—
Sent from Mailbox.app
On Sun, Feb 8, 2015 at 10:42 AM, Chris Ireland<EMAIL_ADDRESS>wrote:

Try using the % wildcard with a query?
So SELECT FROM db where ip = '192.168%'
Reply to this email directly or view it on GitHub:
https://github.com/BanManagement/BanManager-WebUI/issues/26#issuecomment-73403814

Wont work - check the SQL structure. You can not fuzzy select that easily if it's a long data type as stated in the OP.
Here's the example data:
CREATE TABLE IF NOT EXISTS `bm_players` (
  `id` binary(16) NOT NULL,
  `name` varchar(16) NOT NULL,
  `ip` int(10) unsigned NOT NULL,
  `lastSeen` int(10) NOT NULL
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

INSERT INTO `bm_players` (`id`, `name`, `ip`, `lastSeen`) VALUES
(0x0def9953a5c84761851288fd54bb7c09, 'Console',<PHONE_NUMBER>,<PHONE_NUMBER>),
(0x4a3d31eabc914d81b2463ebed946d022, 'frdmn',<PHONE_NUMBER>,<PHONE_NUMBER>),
(0x9b5058e90afb4566a9d39a0ec23df26b, 'RAB5804', 410621565,<PHONE_NUMBER>);

Should be able to do a range search
SELECT * FROM bm_players WHERE ip BETWEEN INET_NTOA("<IP_ADDRESS>")  AND INET_NTOA("<IP_ADDRESS>")

@confuser Thanks! I'll see what i can do with this :+1:

Since 17b4fbd, you can search for IP ranges like:

<IP_ADDRESS>-<IP_ADDRESS>
192.168.1-192.168.2 => <IP_ADDRESS> - <IP_ADDRESS>
192-193 => <IP_ADDRESS> - <IP_ADDRESS>


Adoption - hook post OSP 17.1 OC ironic

Add a hook to set up the OSP 17.1 overcloud ironic.

ironic-python-agent glance images
ironic provisioning network
enroll ironic nodes

Jira: OSPRH-12423

@hjensas I guess this needs a rebase? As the change to include the ironic net is already merged

@hjensas I guess this needs a rebase? As the change to include the ironic net is already merged

Won't the merge bot/github just figure that out? I think we can just approve and lgtm and then it will figures itself out? (Not 100% sure, but I think so - doing so will save CI resources.)

/approve
@hjensas let's try, but I'm not sure haha

/approve
@hjensas let's try, but I'm not sure haha

I asked in openstack-k8s-operators, the respons is "needs a rebase to fix the tree" :(
So ... I rebased it.
I want gerrit again ... :upside_down_face:

@jparoly for awareness

For anybody interested how the hook is connected to data-plane-adoption: https://github.com/openstack-k8s-operators/data-plane-adoption/pull/765

/lgtm
(replicating GH approval given by @ciecierski)


What is "Event History" mentioned in the feature list?

I could not find anything about this in the code.

Hi @ftrrtf ,
The "Event History" is provided by subscription state handlers. While not specifically an event history system, it could be used to implement one.
The Thruway router allows you to define handlers that are triggered when a client subscribes to a topic. This handler can then publish events to that particular client that are necessary to bring the client up-to-date on that topic.
I will try to create an example to demonstrate the use when I have a chance.

Hi @mbonneau,
Thank you, that would be wonderful!

@mbonneau Any ETA? Thanks.

@ftrrtf
I have made an example of how to use "event history" (not the official event history). For now it is located at https://github.com/mbonneau/ThruwayEventHistory/tree/master - we might pull that into the project at some later date as this functionality is pretty generic.
This is a pretty basic example but could be used to build out more complex things if the need arises (stuff that generates a state based on databases or something or only provides events that are still relevant)
Let me know how this works out.

@mbonneau Thank you very much for this example!
For my task I need something like wamp.topic.history.since, described in https://github.com/tavendo/WAMP/blob/master/spec/advanced/event-history.md
Your example has helped me better understand how all this things work in the Thruway. Now I will try to adapt it to since-like feature. If you have any thoughts or suggestions about that — It would also be good to write them.
Thanks again ;)

The implementation of the spec wamp.topic.history.since could all be done with a regular client (except for the feature announcement).
It would be a better approach to use the example and modify it to send you history since an option on the subscription. Otherwise you will have to deal with duplicate delivery issues or missed event issues.
This would also remove the need to make an RPC whenever you subscribe.


unhosted amplitudejs with IPFS hosting ?

Question Checklist

[x] Updated Amplitude.js to the latest version ( ipfs publish with DNSLink TXT )
[x] I read the docs
[x] I searched for existing GitHub issues

Question Subject

How could any help hosting Amplitude on IPFS http://ipfs.io/ ?
And so code versioning is automatic...
Easy, just modify song list in index.html, then
ipfs add -r flat-black/
added QmPemJBuHRdLTfQLc5sNFUBD4qKpvKnwzDafFhWLjMc5vE flat-black
Is in use in http://copylaradio.com/ webradio music recorders as static DApp to offer global Jukebox Interface over IPFS
Question Description

https://ipfs.copylaradio.com/ipfs/QmPemJBuHRdLTfQLc5sNFUBD4qKpvKnwzDafFhWLjMc5vE/
https://imgur.com/OpcQA4d

This is awesome! I'd love to learn how to implement this with AmplitudeJS. I'll add this to the roadmap.

I'm closing this issue for now, but we will keep track of it on our roadmap so we can get this implemented.


Exception handling

I see this part of the Docs isn't written, I tried
begin
 ...
rescue Exception => e
  puts e
end

but the "=>" doesn't play nice, what is the crystal way to do it ?

So I got my answer from @jhass  on the IRC, so
begin
  ...
rescue e : Exception
  puts e
end

Yes. I've been finishing the docs lately, and exception handling and generics are the two missing bits. I'll finish them during the next week, and maybe I'll add a section that talks about the compiler's command line and some FAQ.

@asterite Thanks :)


My memory is being eaten alive ...

OS: Windows 10 (64 bit)
.NET: I have pretty much everything up until 4.6.2 installed + .NET Core
Reopening VsCode causes it to eat 1GB in about 15 seconds.
Can't give you my project (.NET 4.6), but a common theme seems to be that I have a lot of compilation errors due to overhauling what I'm coding rather drastically. I also have quite some deps in that particular project (akka, nodatime, windowsazure sdk, servicefabric, newtonsoft, streamstone, serilog etc...). I know that's not a lot to go on. Willing to help pin point if you can point me in the right direction. Turning on the logging in VsCode does not shown anything out of the ordinary. I'll try downgrading and see whether that changes anything.

That's a completely normal behavior because Ionide type check on start all project it can find in the directory and all subdirectories.

There's only one project to be found ...

Try downgrading to 2.8.10 and check if behavior is the same. 2.9.0 introduced background checking, maybe I've done something wrong there.

Okay, things seem to be much more reasonable after I've uninstalled the latest version and installed 2.8.10

Should be better in 2.9.4


Allow renaming deployed release?

What do you think about allowing to rename to existing deployed release while upgrade?

You would want it to do something like this?

Change release name
Regenerate all templates
Destroy old resources
Create new resources

Or are you thinking it would work differently?

Yes, though release name may have not so drastic impact on templates and eventually existing resources.

Added to feature triage queue

Was not implemented I believe?

It might be possible this could be implemented as a plugin by interacting with tiller directly. Still, I'll file this as a feature request for the time being.

Any update about it?

This is still a big problem for us.
/remove-lifecycle stale

This isn't something we plan to implement any time soon. If someone from the community wants an idea for a plugin, this is a great opportunity to do so!

Is it just a matter of renaming on the config map?

Ah yeah, ok. Hrm. I'm also looking for a lower touch solution (ie. rename in place w/o create/destroy), but not sure if you could change the annotations or other properties without a create/destroy cycle.

Some k8s resources like Service get the release name prepended so that multiple releases can coexist (otherwise nameclash would occur and prevent installation).

/remove-lifecycle stale

Closing this as a wontfix as the effort and risk involved to rename the rendered resources without causing downtime for the application is incredibly high. Given the time investment and risks involved, it's probably not worth the time to consider implementing a vanity name change.
We'd still love to see someone pick this up as a plugin! If that plugin seems like a workable solution then we can consider absorbing that into the core Helm codebase. Thanks!

Oh, I need change release name only..

Changing the release name also affects how the templates can be rendered as many charts rely on {{ .Release.Name }}, hence the high risk.

Changing the release name also affects how the templates can be rendered as many charts rely on {{ .Release.Name }}, hence the high risk.

Very bad call to use the release name within templates, are we looking to change this in helm 3 as we can afford to put in breaking changes

@thangbn We are using release name for labeling the objects in order to associate them with release (they are creating through operator so we cannot use other options)

@thangbn - It is common to use release name within templates exactly with the purpose of associating them with the release name (like @AssafKatz3 said) and I do not believe this is in any way a bad call or practice (unless there's a better way of doing the same thing which I am not familiar with).


Run cell and bellow & Run cells above not working

Environment data

VS Code version: 1.56.0-insider
Jupyter Extension version: v2021.6.780948196
Python Extension version: v2021.5.756443519-dev
OS:  Windows_NT x64 10.0.19041
Python and/or Anaconda version: Python 3.8.8 & conda 4.9.2
Type of virtual environment used: conda
Jupyter server running: Local

Nothing happens when I click 'Run cell and bellow' or 'Run cells above'. Jupyter output doesn't log any new entry when doing either but seems to be working fine when clicking the run all button, or running cell by cell with 'enter+shift' or the run cell button.

@grudloff If you first run a cell with shift+enter, then use the "run cell and below" button, does that work? "Run cell and below" isn't working for me either but I'd like to confirm that I'm seeing the same cause you're reporting. To me it looks like "Run cell and below" and "Run cells above" will not work if there's no active kernel for the current active notebook at the time that the command is invoked.

Instead I believe we'd want to start the kernel if one hasn't already started when "Run cell and below" or "Run cells above" are invoked. Though this is also likely happening because I don't believe we're autostarting kernels anymore after the latest notebook API changes landed.

In my case, it doesn't work even when a cell has been run before and the kernel is already started.

Doing the same in native jupyter notebook under the same environment works as expected without any issue.

@joyceerhl the fix is pretty simple we need to call getOrCreate instead of get.

Seems my problem was unrelated. I am still experiencing the same issue.

@grudloff This fix will become available in the next release that we publish. Can you try this temporary VSIX out (should already contain the fix) and let us know if the problem persists? https://github.com/microsoft/vscode-jupyter/suites/2626147023/artifacts/57578598

Hello @joyceerhl. Thanks for the help but sadly the issue still remains.

Normal VS Code was working fine for me.


Feature request: changes to removal of leftovers confirmation window

Whenever I review the list of suggested leftovers to remove, I tend to look through their paths to make sure that they are indeed related to a program I just removed.
The problem is that very often their path lengths are way bigger than the available screen space on my laptop, and I have to resize the path column manually to see the end of the path.
I suggest either changing the row width so that it is able to wrap long string or truncate these paths somewhere in the middle so that only the beginning and the end of them are shown, and the rest is replaced with: '...'.
Either of the suggested variants can be optional, with the possibility to enable it in the program settings.

I've tried before but couldn't find any good way of doing it. I checked again and it would require modifying how ObjectListView renders the entries, which makes this a very low priority.


[Spike] Epinio in docker

Adding Epinio to marketplaces is nice but:

integrating with those is slow
it costs money for the users that want to try out Epinio

Our official installation method with helm is simple but still not an 1-command setup. It would be nice if people could simply run a command (e.g. docker run ...) and they could get their hands on an Epinio installation that they can play with.

One approach: https://github.com/epinio/helm-charts/pull/241
should deprecated this PR: https://github.com/epinio/epinio/pull/1590

Awesome, I'm sure we can use/adapt it to also speed up things for the QA.


workspaces increase exponentially in length

Describe the bug

workspaces get longer when you switch between them

To Reproduce
Steps to reproduce the behavior:

switch to an empty workspace
switch back
repeat (and with other workspaces)

Expected behavior

The text from the empty workspaces disappear when they are not focused and are empty

System information:

Distro: NixOS unstable (with lix)
Compositor: sway
Ironbar version: 4695279d6927d05b6d3ed5a930e53f04d797c379

Configuration

Share your bar configuration and stylesheet as applicable:

https://git.gay/pinkcreeper100/nix-config/src/branch/main/modules/home/desktop/ironbar
Screenshots
https://github.com/JakeStanger/ironbar/assets/35699052/d5bbb275-9847-43b7-81bd-36c9cfde00e2

This was a regression due to changes made for Hyprland recently, and me not testing those changes on Sway properly. Lesson learned, apologies, fix landing in a few mins.


Added initial draft for OSL closures

A first draft for adding OSL closures to represent the MaterialX PBS library in OSL.
This PR is created to be a forum for discussion. When the proposal is finalized a real PR should be made to https://github.com/AcademySoftwareFoundation/OpenShadingLanguage instead.

This is looking very good!

We eventually want this header to live in the OSL repo, right ?
@fpsunflower Yes absolutely. I probably should have made this PR directly to OSL in the first place.. But as soon as this initial design has been stabilized I will make a proper PR to the OSL repo (and I think we're getting close). Then we can finalize it there and anyone who wants to contribute can start adding implementations in testrender.

I'll make sure to merge this PR first, saving all discussions here, and will link to this from the PR in OSL so all conversation history is preserved.

What was the reasoning behind changing thin-film interference from a separate BSDF to a set of optional parameters on all BSDFs? I couldn't find any discussion about that here or on the Slack.

This was discussed in one of the threads marked as resolved, here:
https://github.com/materialx/MaterialX/pull/614#discussion_r611825067


Create README.md

This is the first pull request. It includes the newly created README.md file.

Good job on this Vasile 💯 Congrats with your first successful pull request.


Rewrite Registry contracts

Rewrite registry contract to latest Cairo. (use Scarb v2.5.3, sn-foundry v0.17)
Make registry upgradeable

Maybe change the mesage by removing the "Make registry upgradeable"


Swap crash reporting with unified analytics

Fixes:

https://github.com/flutter/flutter/issues/147260

Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] I followed the breaking change policy and added Data Driven Fixes where supported.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

We should land this before GA3 is taken offline

I'll be remaking this PR since the cla/google check is failing.


nicer make default

📝 Summary
$ make
Usage:
  make <target>

Help
  help             Display this help.
  v                Show the version

Build
  clean            Clean the build directory
  build-cli        Build the CLI
  build-httpserver  Build the HTTP server

Test & Development
  test             Run tests
  test-race        Run tests with race detector
  lint             Run linters
  fmt              Format the code
  gofumpt          Run gofumpt
  lt               Run linters and tests
  cover            Run tests with coverage
  cover-html       Run tests with coverage and open the HTML report
  docker-cli       Build the CLI Docker image
  docker-httpserver  Build the HTTP server Docker image

✅ I have run these commands

[x] make lint
[x] make test
[x] go mod tidy

This is a nice trick


Avoid pairing null byte characters

Fixes #2537.
I am relatively new to this area, so feedback is super appreciated! :bow:
When a document had null bytes, we were previously detecting whether such bytes were paired with other characters. Thus, if we had a string like the following in the buffer:
{someLetter}{nullByte}{variationSelector}

TokenIterator::isPairedCharacter returned true for {nullByte}{variationSelector}.
Although I suspect it would be technically possible for null bytes to be paired with other unicode characters, as soon as we insert a null byte into the DOM it gets ripped off.
This screwed up our measurement mechanism, which wasn't able to match DOM positions against the model. A solution for this could have been to substitute this line with:
continue if char.indexOf('\0')

However, this would skip the whole paired character and it's inconsistent with what gets displayed to the user. This PR changes the behavior of isPairedCharacter so that it skips null bytes when detecting pair code points.
/cc: @maxbrunsfeld @nathansobo @atom/feedback for :eyes:

:zap: Excellent find.


Backend setCookie logs user out

Bug report
Describe the bug
The official example "auth-helpers/examples/nextjs" logs the user out, when navigating to the /middleware-protected URL.
To reliably reproduce it, set the JWT expiry limit to something low, for example 10 seconds.

To Reproduce

Start the example with a 10 sec JWT expiry limit.

System information

OS: macOS
Browser: Chrome
Version of supabase-js: latest
Version of Node.js: v16.17.1

Additional context
I believe the problem is with setting the cookie on the server side and sending it back to the client. If I comment out the content of setCookie(), the problem is fixed:
https://github.com/supabase/auth-helpers/blob/b8b565b889a7332a07c73f2c1eb3bbefcd0fbce6/packages/nextjs/src/index.ts#L139-L147
Why is this even done actually? I mean why do we need to set cookies on the server? Is it to avoid a duplicate refresh token reuse? Which isn't a problem when using reuse interval right?

This behavior seems correct to me since the JWT would have expired which in turn would reject all requests to the Supabase database for user not logged in. If you are still signed in on the client then what would happen when a request is made with an expired JWT?

The access token expires, the refresh token obviously doesn't. It should just do a refresh.

I'm observing the same issue with the remix auth helpers and here's what I understand is happening:
What's probably happening is that the client is doing a refresh. This means that when the server does a refresh with the old refresh token, it receives a response that the refresh token is invalid.
If you close the client and then re-open it after the access token has expired, the token refresh on the server might be working correctly and setting the cookie correctly.

The point is that the browser is not running when you go to a middleware page. For example the user logs in one day and returns the next day, at which point the token is definitely expired. Then the middleware will run and log the user out.

This will probably get fixed by https://github.com/supabase/gotrue-js/pull/598

No activity since Feb and the JWT expiry limit set is unrealistic for an app.


LFS-52 / LFS-55: Don't embed React into every frontend component

Fade is indeed not supposed to stay there. But turning it into an external doesn't work, because it is actually internal code not supposed to be used outside of material-ui itself. The real fix is to replace it with an actual color manipulation library.


Investigate Python wrapper + Pypi distribution?

Ditching this idea.
Brew + Scoop + NPM should be enough.


extend openshift-ansible CI with conformance test-free containerized deployment

A must for termination of aos-ci-test based tests. Disabling e2e conformance tests for the same reason as I did for the system container based deployment. We still need to debug the failing tests. Currently, we don't have human power and capacity to do that.

@stevekuznetsov @sdodson
@jhadvig FYI

Tested here: https://ci.openshift.redhat.com/jenkins/job/test_pull_request_openshift_ansible_extended_conformance_install_containerized/18/

did we fix the installer to allow containerized to use the SHA hashes for the images? this job was borked before...

looks like no:
935f0d704319        openshift/node:v3.7.0-alpha.1                                                                          "/usr/local/bin/origi"   6 seconds ago        Up 5 seconds                                    origin-node

did we fix the installer to allow containerized to use the SHA hashes for the images? this job was borked before...

@sdodson is that even possible? The openshift-ansible always expects the version, no hash.

Exactly... this was a conversation we had in an architecture call months ago -- we need a way to signal "I know what I'm doing, don't touch me" or other protections to ensure that if we tag it as a version we know that we are testing the correct images -- disable pulling? Idk.

Given the images are built locally, we always test the correct images. Is not that enough?

did we fix the installer to allow containerized to use the SHA hashes for the images? this job was borked before...

I'd assumed that Jan had found some way around that when these tests were initially implemented. If not then we'll have to wait until we fix that.

This job is still valuable even with the published version of Origin on the Hub.


HOTFIX: checkstyle error in ProcessorStateManager

[ant:checkstyle] [ERROR] /home/chia7712/kafka/streams/src/main/java/org/apache/kafka/streams/processor/internals/ProcessorStateManager.java:513:18: Variable 'oldType' should be declared final. [FinalLocalVariable]

related to a0da6785a27b13be173762965402b55860ac5635
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@cadonna @guozhangwang Could you take a look?

Thanks! Was just about to do a hotfix PR myself.

Ran checkstyle and spotbug locally and looks good.

To 2.6 as well.


Add ability for user to supply HydroShare profile link for a creator

Describe the feature you'd like and what it will do
On the submit to HydroShare page, enable the metadata element that allows users to specify the HydroShare profile for the creator to link that creator to their HydroShare profile. This metadata field is optional. The link should be provided as a URL to the profile. For example:
https://www.hydroshare.org/user/10/
Why is this feature important?
Completes metadata for a creator in HydroShare.
Is your feature request related to a problem? Please describe.
N/A
Additional context
N/A

@horsburgh Should this optional field also be added to Contributors?

@Maurier - this functionality should create the same information that is created in HydroShare when one adds a contributor. In HydroShare, you have the option to create a contributor from a HydroShare user or by filling in a form about another person. So, whatever metadata is created by HydroShare when you add a contributor to the resource, the DSP should create the same metadata. Since you don't have the option of searching the list of HydroShare users to add a contributor to a resource in DSP, you should just provide the full set of metadata fields for the DSP user to fill out (including the optional HydroShare profile link).
Is that consistent with your thinking?

Yes, that makes sense.


Add test for deny-all network policy

Depends on: https://github.com/test-network-function/cnf-certification-test-partner/pull/144
Adds a test to make sure that any network policies attached to namespaces running CNF workloads have a default deny-all type of network policy for both ingress and egress traffic.
This requires work on the side of the partner running their CNF workload to make sure they have not only a default network policy but a policy that allows the traffic that they need specifically.  Eg. allowing pods in a single namespace to talk to each other.

Marking this PR as work in progress again so we can clarify the requirements.

FAILURE https://www.distributed-ci.io/jobs/b2fcec72-1668-4628-8b03-2eb9e1085c8f/jobStates
from Add test for deny-all network policy #423

It is failing because we don't have default network policies created in our testing environment, I'll do it and test it together with this change to confirm it passes the test (it should). But don't worry about the warning, it is in our side :)

@ramperher Yeah I figured once I finally get the CI fixed here I'd give a heads up to you prior to merging to add some network policies on your side for testing.  Just trying to get this thing to give me all of the green checks 😄

@ramperher Yeah I figured once I finally get the CI fixed here I'd give a heads up to you prior to merging to add some network policies on your side for testing. Just trying to get this thing to give me all of the green checks smile

I've created this to test the network policies, let's see! https://softwarefactory-project.io/r/c/dci-openshift-app-agent/+/25993
Then, I've put build-depends: 25993 in the description of this PR, so that DCI will take that code as base to run the debug job. I'll try a run right now

FAILURE https://www.distributed-ci.io/jobs/9fa801d9-90a8-42b9-90a7-960519901edb/jobStates
from Add test for deny-all network policy #423

This job is from your last commit submitted, and we can see the test is passing. The job is marked as failed because it is failing the test related to ICMP connectivity, but it is my fault, I need to properly configure the network policies to allow ping between different namespaces. Apart from this, from my side it's fine to merge this change.

@ramperher For cross-namespace pinging, I have an example here: https://github.com/test-network-function/cnf-certification-test-partner/blob/main/test-target/pod-to-pod-np.yaml

@ramperher For cross-namespace pinging, I have an example here: https://github.com/test-network-function/cnf-certification-test-partner/blob/main/test-target/pod-to-pod-np.yaml

Yes, that's the one I was following yesterday, but I have two namespaces and several pods per namespace, I will continue checking this right now, anyway you can go on with this change, it's working fine. Thanks!


"Please use torch.amp.autocast('cpu', args...) instead"

This is for bugs only
Did you already ask in the discord?
Yes
You verified that this is a bug and not a feature request or question by asking in the discord?
Yes
Describe the bug
I am getting this error when training specific layers of a Flux LoRA:
:\ai-toolkit\venv\lib\site-packages\torch\utils\checkpoint.py:1399: FutureWarning: torch.cpu.amp.autocast(args...) is deprecated. Please use torch.amp.autocast('cpu', args...) instead.
with device_autocast_ctx, torch.cpu.amp.autocast(**cpu_autocast_kwargs), recompute_context:  # type: ignore[attr-defined]
Also, the result of the LoRA isn't very good, so I'm not sure if its because of this warning or the training itself.

I was informed: its torch related to the code used, its only a warning and everyone get it

I'm having the same problem, need a torch downgrade?


Run PEXes as normal applications

The PEX runtime presents several differences from the typical python runtime and this can lead to problems PEXing various python programs:

The need to mark a PEX as not zip-safe for application code that uses filesystem APIs to find code and resources in the application.
The merging of the sys.path from individual pre-installed wheel chroots can expose bugs in underlying distributions that are normally masked by being installed in the same chroot as their enclosing dependency set.

Although 1 has a workaround with --not-zip-safe it's often surprising to users and not easy to discover as a problem solution. Item 2 doesn't have a solution and this leads to the inability to PEX certain applications that use namespace packages inconsistently in particular (see #331 for examples).
Recent work that added the --unzip option showed that 1st unzipping PEXes led to better cold and warm cache startup latency. If we were to push on this, one solution to both of the problems listed above would be for PEXes to always unzip / re-package themselves in the pex cache with standard site-packages layout (ie: in one sys.path chroot). This should even improve PEX performance more since the sys.path would have less entries allowing imports provided by the PEX to be found in a single fs search instead of needing to search 1 (the pex zip itself) + N (pex dependencies) locations.

Would it be feasible to consider allowing the building of PEX files unzipped, which aren't intended to be run on another host? The result of something like PEXBuilder.build_unzipped() could be just the unzipped chroot path copied into the pex cache, which an application depending on pex could use to know how to invoke the unzipped PEX file.
Rationale
The lazy-loading ipex functionality added to pants in pantsbuild/pants#8793 currently has to go through a round trip of (when the ipex is first executed) downloading wheels => stuffing them in a pex file, and if pex files were then unconditionally unzipped on top of that it would then involve a third crossing of that zipped/unzipped bridge. Stuffing 3rdparty dependencies into the resulting pex file appears to take more time than actually resolving dependencies, especially when the resolve is mostly cached, and the resulting pex will always be run on the same host because ipex will exec the built pex immediately after it is produced.

The Pex API has supported this for a long time and Pants has correspondingly used it for a long time:
https://github.com/pantsbuild/pex/blob/916e61e04634c60d09ee25859c76ba4f27282e51/pex/pex_builder.py#L462-L477

I had forgotten the difference between .build() and .freeze()! Thank you so much!!

I suspect an inverted flag to indicate e.g. "--force-zip" might be nice to leave around for tight-quartered execution of large pex envs where expansive space consumption may not be desirable (like a pex that contains tensorflow + friends executing on a PySpark worker, etc) - otherwise, this sounds great to me as a default mode.
pex execution overhead is a major UX issue for us particularly with O(GB) pex envs that we toss around inside notebooks.

A speed hack note when implementing this:
If we find sys.argv[0] (the PEX zip file) is writeable, we could re-write its shebang to point to the selected interpreter to fully eliminate re-exec overhead on subsequent runs:
$ cat __main__.py
#!/usr/bin/python
def _maybe_reexec():
    import sys

    _BINARY = sys.argv[0]
    _NEW_SHEBANG = b"#!" + sys.executable.encode("utf-8") + b"\n"

    with open(_BINARY, "rb") as fp:
        shebang = fp.readline()
        if shebang == _NEW_SHEBANG:
            return

        import os
        import shutil

        new_binary = "{}.rewrite".format(_BINARY)
        with open(new_binary, "wb") as new_fp:
            new_fp.write(_NEW_SHEBANG)
            new_fp.write(fp.read())

        shutil.copymode(_BINARY, new_binary)
        os.rename(new_binary, _BINARY)
        os.execv(_BINARY, sys.argv)

_maybe_reexec()
del _maybe_reexec

print("Hello")

$ zip main.zip __main__.py && cat <(echo '#!/usr/bin/env python') main.zip > main.pex && chmod +x main.pex
  adding: __main__.py (deflated 53%)
$ head -1 main.pex
#!/usr/bin/env python
$ time ./main.pex
Hello

real	0m0.051s
user	0m0.044s
sys	0m0.007s
$ head -1 main.pex
#!/usr/bin/python
$ time ./main.pex
Hello

real	0m0.023s
user	0m0.020s
sys	0m0.003s
$ time python -c 'print("Hello")'
Hello

real	0m0.022s
user	0m0.018s
sys	0m0.004s

This self-modifying executable approach could be made robust by writing down the values of any PEX_* environment variables that affect interpreter selection and if those don't match on a subsequent run, then re-run interpreter selection and if a new interpreter is called for, re-run the application install / shebang re-write.


Pry Timeout

When using binding.pry in a post request unicorn will timeout ?

@EdwardReed I haven't run into this before.
Is this happening in a dev, test, staging, or production environment?
Do you have a backtrace?

@EdwardReed is this still an issue for you? How can we replicate it?

I've run into this before. This is a "known issue" with Unicorn because of its timeout. You can replicate it by placing a binding.pry in any controller action. Wait 10 seconds and in the Foreman log you should see the Unicorn worker getting killed and restarted.
If we switch to Puma, I believe this problem should go away.

If we switch to Puma, I believe this problem should go away.

Have you tried this? Puma is multithreaded, and there are known issues with Pry and threads.

Ah, okay. I have not tried it myself, so I was not aware of this issue.

I can confirm this is the case with Puma on a Suspenders app running the proposed config in https://github.com/thoughtbot/suspenders/pull/501

@pedrosmmoreira what is the case, it works or it presents thread issues? If it works, I'd close this issue in favor of #501.

@tute, I've tried reproducing this again and I believe the timeouts I am seeing are due to Rack::Timeout

As of https://github.com/thoughtbot/suspenders/commit/a470912e9df01fda62f0c23ce032a1c9b5493b69 rack-timeout is only loaded in staging and production. Does that fix the issue?

This should be fix as of linked commit. Closing for now.


feat(generation-transformer): add generation transformer support

Closed in favor of https://github.com/aws-amplify/amplify-category-api/pull/2813

Closing in favor of:

https://github.com/aws-amplify/amplify-category-api/pull/2813


More than one decorators is not well displayed by structure explorer

From<EMAIL_ADDRESS>on 2010-11-26T14:00:15Z
With code structure explorer, if a class method have more than one decorator, the corresponding icon in the explorer turn to grey.
The explorer baloon-tip did recognize well the method. It just the icon than turn to grey with no need/explanation
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=470

From pierre.raybaut on 2011-05-16T01:17:43Z
Labels: Cat-OutlineExplorer

From pierre.raybaut on 2012-04-12T06:01:54Z
This issue was updated by revision 0dd40e12ca48 .
Status: Fixed


Fix typo

Just some copy pasta cleanup.

Not sure what to make of the CI fail? Seems like a file that shouldn't be checked?
reuse....................................................................Failed
- hook id: reuse
- exit code: 1

# MISSING COPYRIGHT AND LICENSING INFORMATION

The following files have no copyright and licensing information:
* actions-ci/run_local_actions.sh

meh. just some ci nitpickery.


Travis integration

fixes #14 @tomelm has enabled travis for this repo.

Looks great! Remove the TDOAuths and then if Travis still passes, ship it! :shipit:


Suspicious number of Trust_system.Actions.Connected logs

In an honest network we should see exactly one of those per incoming request/gossip message. But e.g. here we see far more Connected actions recorded than anything else. They should be paired up with increases/decreases for whatever the connection was made for. Something's wrong.

Looking at the place we record Connected, I don't think it's wrong. So we are probably just missing some credits/deductions. We are missing them for incoming SNARK gossip at the least.


Need support for custom detachKeys

I'm an emacs user and every time I want to use ctrl-p, I have to type it twice since ctrl-p is the prefix of the detachKeys.
docker already has a config file which can change the detachKeys, docker/docker#3519. But it doesn't work in docker-compose.
Someone who also get trouble in this issue. #62

The upstream issue has been closed, so this one could probably be closed too.


Add Radar support to detect nearby characters/items

To pick up items or talk to characters you need to be "near" them, to detect whether you are near something we need to add a radar-like feature to locate them using the physics features

closed by c95ce3a802cec659adfe5c084b8654bd6f39233e


Event Rect Single does't support???

Old version (0.4.x) support event rect single, but in 0.6.x I don't see this. I need to show tooltip on mouse over near to vertical gridline of POINT, show with Event Rect Multiple it does not work.
Please bring it back!

I believe this is a duplicate of #2362


Feature/command lined parser

Command line parser works well, but still there are no file parser
and I'm not sure about necessity of IP parametr for server

@NeklesaYuri  We could remove IP parameter if it is redundant, please consult @pgmvp
Also as a described in File-Server-App-Architecture there should be separate class responsible for parsing config. I will add separate task for that.

@alexchmykhalo, we decided to remove IP parameter since it is not used right now.
I've added separate class for parsing config file, but I'm not sure if I used the right approach
Also should there be ability to combine command line and config file parameters somehow?

@alexchmykhalo  should there be a default config file?
And actually I dont understand well why we need separate class for file parse, if it anyway would be launched from command line. Wouldn't implementation be easier if we wanted to combine the use of command line and config file parameters in a single class?


OpenCV

Hi, are there any benefits from source compilation instead of using binaries? It takes hell lot of time :)
Regards,

Because of pytorch's ### cmake -DCMAKE_CXX_FLAGS=-D_GLIBCXX_USE_CXX11_ABI=0
option

I mange to compile and run this simple example https://github.com/pytorch/examples/tree/master/cpp/custom-dataset with opencv binaries included in default colab ubuntu 18.04 even with Pre-cxx11 ABI version of libtorch