python310Packages.gdown: 4.6.3 -> 4.6.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.gdown is: A CLI tool for downloading large files from Google Drive
meta.homepage for python310Packages.gdown is: https://github.com/wkentaro/gdown
meta.changelog for python310Packages.gdown is: https://github.com/wkentaro/gdown/releases/tag/v4.6.4
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.6.4 with grep in /nix/store/hff48y7r488x1araq4g9j9717ivdy13q-python3.10-gdown-4.6.4
found 4.6.4 in filename of file in /nix/store/hff48y7r488x1araq4g9j9717ivdy13q-python3.10-gdown-4.6.4

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
gdown
python310Packages.gdown
python311Packages.gdown
tts

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/hff48y7r488x1araq4g9j9717ivdy13q-python3.10-gdown-4.6.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.gdown https://github.com/r-ryantm/nixpkgs/archive/7360d251c779c33bf2812695d1c34a8d09557023.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hff48y7r488x1araq4g9j9717ivdy13q-python3.10-gdown-4.6.4
ls -la /nix/store/hff48y7r488x1araq4g9j9717ivdy13q-python3.10-gdown-4.6.4/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @breakds for testing.

@ofborg build tts


Added Qualcomm Microcontroller Extensions

We have added 15 extensions to the Microcontroller Integer Unit.
The specifications are publicly available at
https://github.com/quic/riscv-unified-db/releases
The development of the ELF psABI with Qualcomm extensions is currently underway.
Support for these extensions in the LLVM toolchain is also in progress.

Thanks for the PR!
The referenced extensions are listed as version 0.1. However, when looking at the referenced repo, the individual extensions don't have a version. For the XThead* extensions we simply set v1.0 for all extensions, so it is clear they won't ever change.
The referenced document has a "DRAFT" watermark, which usually implies that the extensions are not frozen. If that's the case, then this is a blocker for upstreaming.

Thanks, Christopher, for the quick feedback.
Although the spec is labeled as a draft, it is currently in a stable state. The upcoming PDF release will reflect this status, and the list of extensions and their instructions is also considered stable.
We have assigned version 0.1 to the extensions because we are in the process of implementing assembler support for the instructions in LLVM. This allows us to correct any typos and minor issues in the spec if needed. Once this process is complete, the extensions and spec will be promoted to version 1.0.
As we begin to upstream support in LLVM under the experimental extension, we have decided to introduce the Qualcomm vendor extensions in this spec. The patches will refer to Qualcomm extension names, use the "qc" prefix for instructions, and include Qualcomm vendor relocations. This is the spec that should contain such information.

@cmuellner, the new frozen release is out: https://github.com/quic/riscv-unified-db/releases.
We will promote it to 1.0 once we finalize the assembler support in the LLVM toolchain.


[Bug] SaaS Connectivity docs refer to old CLI command

The SaaS Connectivity docs need to refer to the new SailPoint CLI command, sail.

Fixed in https://github.com/sailpoint-oss/developer.sailpoint.com/pull/113


Revising taxi fare regression tutorial to .7

Revising taxi fare regression tutorial to upcoming ML .NET .7 API release
Code sample PR is https://github.com/dotnet/samples/pull/441

The build is green 🚦   :shipit: when ready!


Extends commands "teams team remove", "teams team archive", and "teams team unarchive" to add an extra option to get to the correct team. Closes #3483

Extends commands teams team remove, teams team archive, and teams team unarchive to add an extra option to get to the correct team. Closes #3483

Thank you @nanddeepn! We'll review it asap

Thank you very much. Looks good. Manually merged.
Created issue #3502 to track the removal of the teamId property in the v6 release.
Cheers


Feature/remove forks and registrations from anonymized nodes

Purpose
For https://openscience.atlassian.net/browse/OSF-4501
Registrations and forks are leaky for anonymized data, and were recently removed from the project view on the OSF. This matches that removal. Also, node_logs params were super-leaky, so we're applying strict anonymization to them as well while we're at it.
Note: This will not prevent people from going to the node's registration list URL. We can talk about if we really want to go that far, but as of the current implementation, it's just making it harder to do. But there are more ways for people to find anonymous data if they really want to, such as searching for registrations with the same name or similar, so if we want to get serious about this, we may have to re-think our approach.
Changes

Restrict fields in the node serializer so that registration links aren't serialized and, consequently, you can't embed registrations. When forks are added to the node serializer, we'll want to avoid whitelisting the forks field;
Embed meta information to the API when data is anonymized (there is a meta dictionary at the same level as the top-level data dictionary. The meta dictionary will say anonymous: true if data is anonymized, otherwise it will not appear);
Update logs so that nobody can accidentally add leaky information. This is done by restricting log information to id, date, and the type of action; no params or relationship links will show.

Side effects
The upcoming log renderer will need to handle the case of not having much information, and Henrique has been notified.

:+1:


ImportError: cannot import name _hough_circle

hi, when I run lsm, it shows

ImportError                               Traceback (most recent call last)
 in ()
----> 1 from shapenet import ShapeNet
2 # Read data
3 dset = ShapeNet(im_dir=im_dir, split_file=os.path.join(SAMPLE_DIR, 'splits_sample.json'), rng_seed=1)
4 test_mids = dset.get_smids('test')
/home/cloud/Downloads/lsm-master/shapenet.py in ()
8
9 from config import SHAPENET_IM
---> 10 from loader import read_camera, read_depth, read_im, read_quat, read_vol
11
12
/home/cloud/Downloads/lsm-master/loader.py in ()
3 from scipy.io import loadmat
4 from skimage.io import imread
----> 5 from skimage.transform import resize
6
7
/home/cloud/Downloads/lsm-master/env/lib/python2.7/site-packages/skimage/transform/init.py in ()
----> 1 from .hough_transform import (hough_line, hough_line_peaks,
2                               probabilistic_hough_line, hough_circle,
3                               hough_circle_peaks, hough_ellipse)
4 from .radon_transform import (radon, iradon, iradon_sart,
5                               order_angles_golden_ratio)
/home/cloud/Downloads/lsm-master/env/lib/python2.7/site-packages/skimage/transform/hough_transform.py in ()
2 from scipy import ndimage
3 from .. import measure
----> 4 from ._hough_transform import (_hough_circle,
5                                _hough_ellipse,
6                                _hough_line,
ImportError: cannot import name _hough_circle

Hey. This seems like an error on the dependencies for scikit-image. I found this issue which suggests that the requirements for scikit-image may not be properly installed. Could try installing matplotlib (pip install matplotlib) in the virtualenv and see if it fixes the problem?

Closing issue due to inactivity


[SUPPORT] Hudi Job fails fast in concurrent write even with high retries and long wait time

Describe the problem you faced
We have a usecase where might have a lot of concurrent writes to the same partition under special scenarios. We are testing if Hudi supports this natively by changing some of the lock retry/wait-time parameters.
We are trying allow all these writers to go through with optimistic retries eventually by using really high num_retries and wait_time_ms parameters.
To Reproduce
We are using DynamoDB as the lock provider, running these loads on AWS EMR
We have the following using options related to concurrency control:
      "hoodie.write.concurrency.mode" -> "optimistic_concurrency_control",
      "hoodie.write.lock.client.wait_time_ms_between_retry" -> "60000",
      "hoodie.write.lock.max_wait_time_ms_between_retry" -> "600000",
      "hoodie.write.lock.num_retries" -> "60",
      "hoodie.write.lock.wait_time_ms" -> "360000",
      "hoodie.write.lock.wait_time_ms_between_retry" -> "360000",
      "hoodie.cleaner.policy.failed.writes" -> "LAZY",
      "hoodie.write.lock.dynamodb.endpoint_url" -> "dynamodb.us-east-1.amazonaws.com",
      "hoodie.write.lock.dynamodb.partition_key" -> "PrepareMergeJob-capitalcasetable-NA",
      "hoodie.write.lock.dynamodb.table" -> "DatastoreWriteLockTable",
      "hoodie.write.lock.provider" -> "org.apache.hudi.aws.transaction.lock.DynamoDBBasedLockProvider",
      "hoodie.write.lock.dynamodb.region" -> "us-east-1",

We spinned up 7 jobs that writes to the same table. Each job should take around ~20 minutes to finish on its own.
Expected behavior
These 7 jobs will have conflicting writes and will retry and will succeed eventually.
Base on the retry parameters I have set, I'd expect it to run for at least 4 hours.
Environment Description

Hudi version : 0.13.0

Spark version : 3.3

Hive version : 3.1.3

Hadoop version : 3.3.3

Storage (HDFS/S3/GCS..) : S3

Running on Docker? (yes/no) : no

Additional context
Running these workloads on EMR. This is a follow up to this issue: https://github.com/apache/hudi/issues/9512
Stacktrace
Seeing these errors after 0.5 hours for 40% of the jobs:
java.util.ConcurrentModificationException: Cannot resolve conflicts for overlapping writes
	at org.apache.hudi.client.transaction.SimpleConcurrentFileWritesConflictResolutionStrategy.resolveConflict(SimpleConcurrentFileWritesConflictResolutionStrategy.java:108)
	at org.apache.hudi.client.utils.TransactionUtils.lambda$resolveWriteConflictIfAny$0(TransactionUtils.java:85)
	at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1384)
	at java.util.stream.Streams$ConcatSpliterator.forEachRemaining(Streams.java:742)
	at java.util.stream.Streams$ConcatSpliterator.forEachRemaining(Streams.java:742)
	at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:647)

OCC is not designed for high frequency concurrent access, we are working hard towards non-blocking concurrency control: https://github.com/apache/hudi/pull/7907

Thanks! That's good to know. Meanwhile we can build our own "lock"
However, does this symptom also mean these retry parameters does not work for DynamoDB based lock provider? I was looking into the source code and seems DynamoDBLockProvider is not picking up some of the parameters like "write.lock.num_retries". Is that true?

@Jason-liujc I did a fix around the same line which will be included in 0.14. Dynamodb config class had some configuration issues which was not allowing it to pick default params. Although I haven't tried this around num_retries. Can you try with this PR - https://github.com/apache/hudi/pull/8868

Thanks. We've tried the newest update from DynamoDBBasedLockProvider and DynamoDbBasedLockConfig but we are still seeing jobs fail pretty soon if encountering conflicting writes.
Just going through the source code, I'm seeing ZookeeperBasedLockProvider is using retry under the hood: https://github.com/apache/hudi/blob/9e9f768434333380640ba5e452b168f9e92ee110/hudi-client/hudi-client-common/src/main/java/org/apache/hudi/client/transaction/lock/ZookeeperBasedLockProvider.java#L58
Whereas DynamoDB is not: https://github.com/apache/hudi/blob/9e9f768434333380640ba5e452b168f9e92ee110/hudi-aws/src/main/java/org/apache/hudi/aws/transaction/lock/DynamoDBBasedLockProvider.java#L62
My theory right now is when we are using DynamoDB Lock Provider, the retry parameters are not used, hence the job fails pretty fast. (i.e. hoodie.write.lock.num_retries). Since going through the Hudi created DynamoDB entry, I don't see any state regarding how many retries a given lock was used.
Let me know if that's the case or an expected behavior from Hudi.

@Jason-liujc I believe the issue you're seeing is unrelated to lock acquisition. From the multi-writer docs:

For example, when two writers write to non overlapping files, both writes are allowed to succeed. However, when the writes from different writers overlap (touch the same set of files), only one of them will succeed

From the error you posted, it seems like both writers write to the same file ID so one of them fails. The PR that @danny0405 linked addresses this issue by resolving the conflicts during compaction/read-time.

Thanks. We've tried the newest update from DynamoDBBasedLockProvider and DynamoDbBasedLockConfig but we are still seeing jobs fail pretty soon if encountering conflicting writes.
Just going through the source code, I'm seeing ZookeeperBasedLockProvider is using retry under the hood:
https://github.com/apache/hudi/blob/9e9f768434333380640ba5e452b168f9e92ee110/hudi-client/hudi-client-common/src/main/java/org/apache/hudi/client/transaction/lock/ZookeeperBasedLockProvider.java#L58
Whereas DynamoDB is not:
https://github.com/apache/hudi/blob/9e9f768434333380640ba5e452b168f9e92ee110/hudi-aws/src/main/java/org/apache/hudi/aws/transaction/lock/DynamoDBBasedLockProvider.java#L62
My theory right now is when we are using DynamoDB Lock Provider, the retry parameters are not used, hence the job fails pretty fast. (i.e. hoodie.write.lock.num_retries). Since going through the Hudi created DynamoDB entry, I don't see any state regarding how many retries a given lock was used.
Let me know if that's the case or an expected behavior from Hudi.

Can we please confirm this issue if it persists ?
Should we start using zookeeper rather then DynamoDB lock ?

@SamarthRaval @Jason-liujc As discussed, the retry configuration is unrelated to the problem you are facing. The only way to handle such scenario's at this moment will be handling retries at your application level code.


more bokeh controls

I expect most plots should have box zoom and save. Crosshairs? Hover? Zoom in and zoom out icons might be easier to immediately identify, maybe add them too.
Things like selection and lasso are probably best addressed in beta.

@alorenzo175 sounds like you're on your way to closing this with your validation graphics.

yes #76

closed by #76


PHP 7.2 + QA Tools - follow up #129, #132, #134

Closes #129
Closes #132
Closes #134
Resolves #139
/cc @froschdesign

Thanks for working on that but please split into smaller PRs

I don't know how to configure all these cache adapters on travis for all supported PHP versions... I was trying multiple times and still something is failing 😞

Sorry, closed by accident

@webimpress Can you try to split this PR? It's very complicated to review and test it.

@webimpress I tend to agree with @thomasvargiu , particularly as #132 is unrelated to QA tooling, and needs to be rewritten.
I'll merge #129 for now, and then start working on a patch that incorporates the QA-related commits from this one.

Closing in favor of #148, which incorporates commits from this patch.


add USING statement for covering / MV indices for using existing inde…

Is your feature request related to a problem?
As a flint user, I'd like to use existing indices / index-templates for using as the index targets of the flint accelerated tables
What solution would you like?
Use existing index name to create the acceleration process - this will actually not create an index but use the given name as the target of the acceleration ETL store.
The next SQL syntax suggested:
CREATE (SKIPPING/COVERING/MV) INDEX
ON alb_logs USING ss4o_logs-elb-prod
WITH (
  auto_refresh = true,
  refresh_interval = '1 minute',
  checkpoint_location = 's3://test/'
)

Would initiate the acceleration ETL sync process without actually creating a new index in OpenSearch, it will use the ss4o_logs-elb-prod index (index template) as the data store for the acceleration content.
It may validate the following:

match source table (catalog) columns exist in the given index_mapping
match the index has an alias with the correct flint naming convention
match the index_template (mapping) has the correct covering - matadata fields exist (covering / MV columns)

Issues Resolved
#72
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Could you explain the semantics of this new syntax? So user already has index with Flint metadata, this actually not CREATE but just alias their index name with expected Flint name. Why this has to be done in Flint extension?

this is to be done in flint since we do need to add the metadata section to an existing opensearch index
it will take an existing index and add the correct flint name according to the convention and the _meta columns that are accelerated

I see. If so, could you do it as how we support index_settings option? I think you just need to add one more alias option in FlintSparkIndexOption and use it in FlintClient and FlintMetadata. No need to change so many places.

remove this PR since the functionality will be moved to materialized view


Increase instance size for API and supplier app

Since we expect an increase in requests for the last days of the G-Cloud 8 service submission, we raise the size of EC2 instances for supplier frontend and Data API apps.
This is the same as we did for G7 and it was all good (see Alexey's commit here: https://github.com/alphagov/digitalmarketplace-aws/commit/df1f1effc792f5d7211896e1dcd8ea8ae1609dcc)
We can reduce these to the previous value after the service submission is closed.

Yeah, looks good. 👍
Are we going to lower the max_instance_count to 5, or is it on 10 forever now?

It didn't ever get rolled back to 5, not sure if that was on purpose or not.  But if we do want to go back to 5 then now isn't the time.

Latest commit looks like it's doing what it's meant to. 👍  👍

Oooh, nice way to compare.
Bit nervous, but going to run this and see what happens.


Screen flickering on Dialog closes | Radix Themes

Bug report
Current Behavior
Sample video, please notice the flickering I have provided the stackblitz project repo link please check.
https://github.com/user-attachments/assets/8aef7930-464f-470e-8ef7-16a7be11546d
Expected behavior
I expected this to close smoothly without any flickering issue visible to the users.
Reproducible example
StackBlitz Project Link https://stackblitz.com/edit/stackblitz-starters-fsfdnffv?file=app%2Fpage.tsx
Your environment

Software
Name(s)
Version

Radix Package(s)
themes
3.1.6

React
n/a
18.2.0

Next
n/a
13.5.1

Browser

Assistive tech

Node
n/a
v22.12.0

npm/yarn

Operating System

I am seeing the same issue on Arc Version 1.74.0 (57065) / Chromium Engine Version 131.0.6778.205 both in this stackblitz repo and my own code.
This happens with both AlertDialog and Dialog. I just started using Radix, so I am not sure how to debug this yet, but I will try to find out more!

I suspect this issue should be moved to https://github.com/radix-ui/themes
From some very rough debugging I found a solution by changing the times of the animations. .rt-BaseDialogOverlay &:where([data-state='closed'])::before { has been changed from 160ms to 200ms.
.rt-BaseDialogOverlay {
    &:where([data-state='closed']) {
        animation: rt-dialog-overlay-no-op 200ms cubic-bezier(0.16, 1, 0.3, 1) !important;
    }
    &:where([data-state='open'])::before {
        animation: rt-fade-in 200ms cubic-bezier(0.16, 1, 0.3, 1) !important;
    }
    &:where([data-state='closed'])::before {
        opacity: 0;
        animation: rt-fade-out 200ms cubic-bezier(0.16, 1, 0.3, 1) !important;
    }
}

.rt-BaseDialogContent {
    &:where([data-state='open']) {
        animation: rt-dialog-content-show 200ms cubic-bezier(0.16, 1, 0.3, 1) !important;
    }
    &:where([data-state='closed']) {
        opacity: 0;
        animation: rt-dialog-content-hide 100ms cubic-bezier(0.16, 1, 0.3, 1) !important;
    }
}


Helm 3 docs update

For https://github.com/rancher/docs/issues/2029.
@ibrokethecloud should review this before it gets merged

There is a small issue with the commands.
Command should be of the form:
helm install rancher rancher-stable/rancher --namespace cattle-system --set hostname=rancher.demo
The PR has dropped --name rancher. We only need to drop --name
This leaves the command as:
helm install rancher-stable/rancher --namespace cattle-system --set hostname=rancher.demo
This will fail because helm3 still wants a name or --generate-name argument.

Thanks @ibrokethecloud, @catherineluse should be ready now for your review


EHC Sensor Issues

Cynthia contacted me on Tuesday morning that she was going to EHC to check on some of the sensor issues.
According to the tech dashboard, the gateway had communicated with all four nodes and sent data through the network and to the database sometime in the past. One main problem is that although the gateway communicated with node #18000282 it did not send any strings of data. I had Cynthia reset the system and check the wiring on that node.
Cynthia reset the system. It had some issues pinging the nodes right away and it took several times for it to successfully link to the nodes and send a time stamp update to the dashboard.
This site has since gone down again and it's still not getting data strings for node #18000282

that sound like an issue on the node with the antenna and not having enough signal strength on it. it could be that the antenna is broken, not properly attach or an issue with objects in the way (not likely). that shouldn't stop it from collection data, though. can you have her download the data from the node itself and check that data.

Do we have any follow up information on this site?


Package request: atom-editor zen-browser gdm-settings

Project description

Metadata

homepage URL:
source URL:
license: mit, bsd, gpl2+ , ...
platforms: unix, linux, darwin, ...

Add a :+1: reaction to issues you find important.

There is gdm-settings and no zen browser
github atom-editor was already removed.

One issue per package and fill in the issue template.


Add autoclose option.

Is your feature request related to a problem? Please describe.
I often stage, commit and then push changes. Then I have to close the the neogit view.
Describe the solution you'd like
Would be cool that after push is finished and succeded, neogit closes automatically.
Or we could have something like:
autoclose_on: commit|push|pull

Describe alternatives you've considered
Close manually :-)
Additional context
I know this is only for lazy people like me.

Or maybe introduce events which users could subscribe to, would cover that case and, I assume, many others without being too specific about implementation on neogit side.

I'd say just using vim user autocommands like we did for the refresh event should be fine.


Create BackStockPros

MarketBack , notebook , june 11, 2024 link
MarketBack , notebook , september 16, 2024 link
Backdoor attack via jumps-Diffusion and stochastic processes : BackStockPros
Hello Dear @beat-buesser ! , I recently performed a more specific and complex analysis on stochastic calculations and jumps incorporating a more advanced Bayesian analysis, in order to understand the change in data distribution during a backdoor attack, you will find attached the full code, you can also download in the code the full csv file containing all the details of this Bayesian stochastic analysis.
Description
Diffusion Process with Jumps :
Now, suppose the underlying diffusion process is no longer simply geometric Brownian motion, but there is also a jump process,
$$
\frac{d S_t}{S_t} = \nu dt + \sigma dW_t + (\eta - 1) dq_t,
$$
where $dq_t$ is a homogeneous Poisson process, with parameter $\lambda$, and where $\eta - 1$ corresponds to the amplitude of the jump (making $S_t$ pass to $\eta S_t$ if there is a jump at time $t$).
This research paper presents a comprehensive approach for executing backdoor attacks on audio data. It uses a diffusion model and a Bayesian approach (via stochastic process effects). The effectiveness of the attack method and its discretion are confirmed by evaluation results, which highlight their ability to manipulate the integrity and security of audio systems.

Simulation of a continuous change in performance due to backdoor triggering using the Ornstein-Uhlenbeck process
Simulate performance fluctuations due to the backdoor trigger using the Ito formula for jump-diffusion
Simulate the spread of the backdoor effect using the Black-Scholes to Diffusion method
Simulate the spread of the backdoor effect over time using the Kolmogorov-Feller equation

After compilation, please examine the results of the csv file. This file contains information that can help improve understanding in various fields, such as finance, particle physics and chaotic time, where the passage of data to undetectable backdoors, biological simulations etc...
Testing
UPDATE Notebook:  a more comprehensible version for those not familiar with Bayesian techniques  BackStockPros,  notebook complet
code update,  this version is correctly optimal it integrates all simulations correctly in Bayesian execution
easy to understand
UPDATE Best (easy to understand )!  please consider the following BackStockPros,  notebook complet
Reference  maybe
Reference  nice
Reference 0
Reference 1
Reference 2
Reference 3
Reference 4
Reference 5
Reference 6
Reference 7
Reference 8
Reference 9
Reference 10
Reference 11
Reference 12
Reference 13, very nice
Reference 14, just very happy
Reference 15
Reference 16

Hi @OrsonTyphanel93 Thank you very much for your pull request! Have you published these results somewhere in a conference paper?

Closing because of inactivity, please reopen if still current.


fixes #100 support for @Indexed annotation

split blocking and reactive base configurations

can you please split the changes, it is very difficult to review

fixes #100


Where has example for use the GRPC to transport JSON ?

Hi, I would like to use GRPC to send the PUSH notification to APNS, the APNS requires HTTP2 with JSON format data, how could I use JSON in GRPC to instead of the PROTOBUF ? When can I find the example ?
Thanks

You can't use gRPC to communicate with APN services. Even if we'd be to provide an example to use gRPC with JSON payloads instead of protobuf, it'd still wouldn't work. It's not because both APN and gRPC work on top of HTTP/2 that they are compatible protocols. They're not.


When creating feature vector from dense representation by array, do you use the first element as the first feature or the label?

Hi,
When creating feature vector from dense representation by array, do you use the first element in the array for the first feature and the second for the second and so on or is the first element for the label as a placeholder?
Thanks,

Hi,
This library don't provide any functions to handle labeled feature vector, so you should write & use code like below:
public class FVecFloatArrayWithLabel implements FVec {
    private final float[] values;
    private final boolean treatsZeroAsNA;

    FVecFloatArrayWithLabel(float[] values, boolean treatsZeroAsNA) {
        this.values = values;
        this.treatsZeroAsNA = treatsZeroAsNA;
    }

    @Override
    public double fvalue(int index) {
        if (values.length <= index + 1) {
            return Double.NaN;
        }

        double result = values[index + 1];
        if (treatsZeroAsNA && result == 0) {
            return Double.NaN;
        }

        return result;
    }
}


Problem using React component in content scripts

I have a problem using React components in content scripts. It seems to me that this is the most natural use of the script, in this case.
Uncaught SyntaxError: Cannot use import statement outside a module (at index.js:1:1)`

import { createRoot } from 'react-dom/client';
import Main from './Main';

const container = document.createElement('div')
const rootEl = document.createElement('div')
const styleEl = document.createElement('link')
const shadowDOM = container.attachShadow?.({ mode: 'open' }) || container
styleEl.setAttribute('rel', 'stylesheet')
styleEl.setAttribute('href', chrome.runtime.getURL('contentStyle.css'))
shadowDOM.appendChild(styleEl)

shadowDOM.appendChild(rootEl)
document.body.appendChild(container)

const root = createRoot(container); // createRoot(container!) if you use TypeScript
root.render(<Main/>);

How to solve it?

You can confirm by putting this code in index.tsx in content. It will not work.

I would appreciate information on how to make it work.

Thanks for reporting, will look into this asap!

Please, I want to use this in my project.

Fixed!

@pixelkoduje were you able to get it to work ?


Fix FAQ typo

Reported by @kayceesrk

Does this also update the footer?

Ah, I missed that it was occurring twice. Thanks, fixed.


Improve performance for Kafka consumer

Some users have reported that 1.5.x version of this plugin being slower than 1.4.2 which is very weird. We'd like to get to the bottom of this. Starting with an audit of existing code for obvious issues, and then attaching a profiler would help find hotspots.
See ref: https://github.com/elastic/logstash/issues/3477#issuecomment-137772888

As far as i remember, this line:
https://github.com/logstash-plugins/logstash-input-kafka/blob/master/lib/logstash/inputs/kafka.rb#L169
decodes messages in single thread. Even if we set 'consumer_threads' it will only affect things that happen inside jruby-kafka library. So if we have expensive codec, then decoding message may be bottleneck.
As a workaround i use codec plain and decode messages in filter.

Please note this proposed consumer threading change:
https://github.com/joekiller/jruby-kafka/pull/33
On Sep 6, 2015 9:30 AM, "Jakub Podeszwik"<EMAIL_ADDRESS>wrote:

As far as i remember, this line:
https://github.com/logstash-plugins/logstash-input-kafka/blob/master/lib/logstash/inputs/kafka.rb#L169
decodes messages in single thread. Even if we set 'consumer_threads' it
will only affect things that happen inside jruby-kafka library. So if we
have expensive codec, then decoding message may be bottleneck.
As a workaround i use codec plain and decode messages in filter.
—
Reply to this email directly or view it on GitHub
https://github.com/logstash-plugins/logstash-input-kafka/issues/40#issuecomment-138086036
.

Some more performance discussion here: https://discuss.elastic.co/t/logstash-input-kafka-add-field-very-slow/28541/1

@suyograo @talevy  I've been working on a new 2_x version that uses the jruby-kafka 2_x stuff. Here are my preliminary results:
Old
1 Thread:
2.86MiB 0:00:32 [  91KiB/s] [  91KiB/s]

4 Threads:
2.86MiB 0:00:31 [93.1KiB/s] [93.1KiB/s]

1 Decorated Thread:
2.86MiB 0:00:41 [71.2KiB/s] [71.2KiB/s]

4 Decorated Threads:
2.86MiB 0:00:44 [66.4KiB/s] [66.4KiB/s]

New
1 Thread:
2.86MiB 0:00:32 [89.6KiB/s] [89.6KiB/s]

2 Threads:
2.86MiB 0:00:23 [ 126KiB/s] [ 126KiB/s]

4 Threads:
2.86MiB 0:00:19 [ 147KiB/s] [ 147KiB/s]

1 Decorated Thread:
2.86MiB 0:00:43 [66.6KiB/s] [66.6KiB/s]

2 Decorated Threads:
2.86MiB 0:00:28 [ 101KiB/s] [ 101KiB/s]

4 Decorated Threads:
2.86MiB 0:00:23 [ 124KiB/s] [ 124KiB/s]

Gist: https://gist.github.com/joekiller/68a6aa2e12524445d60e


Unconsistent behaviour when converting data types into Swift objects

Xcode version: 8.3.2
Firebase SDK version: 4.0.0
Firebase Product: database

The problem
The way some data stored in Firebase Database is converted into Swift objects is unconsistent.
Steps to reproduce:
For example, i have data stored in Firebase Database like this (JSON)
"test-dict": {
  "2": true,
  "3": true,
  "4": true
},

when i am trying to cast this in Swift to Dictionary [String: Any] or [String: Bool] it always fails.
the actual type in swift for this will be Array [Any]
particular for this example the array will be: [NSNull, NSNull, Bool, Bool, Bool]
but when we add another literal key to the dict:
"test-dict": {
  "2": true,
  "3": true,
  "4": true,
  "a": true
},

it successfully casts to [String: Any] or [String: Bool]
Was this behaviour supposed to be so or is it an issue?

This is the intended behavior as the Realtime Database coerces objects with numerical keys to arrays. Specifically, "... if all of the keys are integers, and more than half of the keys between 0 and the maximum key in the object have non-empty values, then Firebase clients will render it as an array." Once you introduce a non-numerical key, the clients know it's an object again.
See https://firebase.googleblog.com/2014/04/best-practices-arrays-in-firebase.html for a little more detail.


Improve test covarage

add AbstractExceptionTest
add CircuitBreakingExceptionTest
add CloneFailedExceptionTest
cover specific test cases

Coverage increased (+0.09%) to 94.456% when pulling e8d861359ade336badcac3211e5aa447097479a6 on Abrasha:improvement/exception-test into 021e4dfb501a8e6e5810a4f0efe1267810d62d64 on apache:master.

Merged. Thanks @Abrasha !


fix: sample - cacheControl is set under metadata, not top level as comment suggests

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[x] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[x] Ensure the tests and linter pass
[x] Code coverage does not decrease (if any source code was changed)
[x] Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

cacheControl metadata should be on the top level as it exists as part of an Object's resource.

cacheControl metadata should be on the top level as it exists as part of an Object's resource.

@jkwlui Sounds good to me. Just FYI, it currently doesn't work set at the top level using version "@google-cloud/storage": "^5.0.1",

@jgresham can you share the code attempting to set cacheControl at the top-level?
I have this and I can verify cacheControl is set on the remote object.
  async function setFileMetadata() {
    // Set file metadata.
    const [metadata] = await storage
      .bucket(bucketName)
      .file(filename)
      .setMetadata({
        // Predefinded metadata for server e.g. 'cacheControl', 'contentDisposition',
        // 'contentEncoding', 'contentEncoding', 'contentLanguage', 'contentType'
        contentDisposition: 'attachment; filename*=utf-8\'\'"anotherImage.jpg"',
        contentType: 'image/jpeg',
        cacheControl: 'private',

        // Note or actionable items for user e.g. uniqueId,
        // object description or other useful information.
        metadata: {
          description: 'file description...',
          modified: '1900-01-01',
        },
      });

    console.log(metadata);
  }

@jkwlui
const { Storage } = require("@google-cloud/storage")
const storage = new Storage({
  projectId: PROJECT_ID,
})
let imageMetadata = {
      contentType: "image/jpeg",
      // cacheControl: "no-cache, max-age=0",   <--- does not work here
      metadata: {
        // default GCP Storage file caching is "public, max-age=3600"
        // override so that users immediately see new files after updating
        cacheControl: "no-cache, max-age=0",
      },
    }
let imageBucket = storage.bucket("my-bucket")
let bucketFile = imageBucket.file("file-path/file-name")
let writeStream = bucketFile.createWriteStream(imageMetadata)
let writeStreamResp = await promiseWriteStream(imageBuffer, writeStream)

Ah I see.
so from the documentation of File.createWriteStream(), the first argument is expected to have type CreateWriteStreamOptions. This is not the metadata of the object. However with that being said, we did provide convenient options here like contentType and predefinedAcl which actually maps back to the metadata field of the option. See https://github.com/googleapis/nodejs-storage/blob/master/src/file.ts#L1693-L1715
The metadata field of CreateWriteStreamOptions actually corresponds to the top-level metadata as is expected for file.setMetadata().

Thank you for the details @jkwlui! I closed the PR.


Add backers and sponsors from Open Collective

This is for your open collective backers and sponsors to appear directly on your README.
see how it'll look here
More info
Also add badges on top.

Thanks @piamancini.  I set up the project on Open Collective, but haven't coordinated with others on moving over any existing backers or our existing funds.  It might take a bit of time to do this coordination, but then we'll definitely want to update the readme to promote the project.
In short, this PR might sit for a bit before getting merged.

SGTM. whatever works for you in terms of time :) Shout if you have any questions.
best


Is it possible to create predefined pages?

Hello, first of all I love this project I would like to congratulate the team for bringing this plugin to Grapes.
What I would like to ask is, if it is possible to create default pages so that the user cannot delete them.
Let me explain, I have an ecommerce site and I have 4 default pages, Home, Cart, Product Page and Tracking, I don't want the user to delete those 4, but if I want him to be able to create more pages, is it possible?

At the moment it would be possible for the user to delete them, I'm not sure if the Pages API has such functionality but I guess from the UI side it's just a matter of hiding the delete button. You could exclude the pages from the editor then add them during the export/publish step.

Is there an example of how we could hide the delete button for those specific pages?

Haven't tried it yet, will look into adding it to the core


Testcafe hides/swallows half of my console.log when using electron

What is your Test Scenario?
I am using testcafe to write tests for both my website and my electron desktop application. In the website I can debug any issues I have by adding console.log to my implementation and opening chrome devtools.
In my electron desktop application; only half of my console.log show up; electron has two processes, the main and the renderer process, any console.log in the main process goes to STDOUT ; any console.log in the renderer process goes to the chrome devtools. I can see my logs in chrome devtools but not STDOUT
What is the Current behavior?
I can only see half of my console.log in electron apps.
What is the Expected behavior?
I expect to see all of my console.log in electron apps.
What is your web application and your TestCafe test code?
Sharing the application and a test case is more challenging; however I did track down the code that causes the bug.
I opened a PR to make logs available ( https://github.com/DevExpress/testcafe-browser-provider-electron/pull/53 ).
The implementation of testcafe-browser-provider-electron just hides all stdout from the electron main process by setting stdio: 'ignore' when spawning the electron child process.
Your Environment details:

testcafe version:                   1.7.0
node.js version:                    10.15.3
command-line arguments:  testcafe tests/testcafe/*.ts
browser name and version: electron
platform and version:          Linux

Thank you for report and PR. We will discuss it.


Hook monaco completion provider to filter members starting with underscores

Given a non filtered babylon.d.ts
Before:

After:

@deltakosh, after merging you need to update the babylon.d.ts with the regular one, and remove any auto-post-processing-step if needed.

yep yep it is done:)

So thankful to @sailro as it helps removing some build steps :-)

Do we still need this ?
https://github.com/BabylonJS/Babylon.js/blob/master/Tools/Gulp/tasks/gulpTasks-intellisense.js#L15

Nope, it is removed in my branch


Feature request (?): set endofline type (crlf / lf)

Please add option to set (and also show in the status bar) the line ending mode (if not already available, and I'm not aware of).
Just like 'eofnewline', we could have 'newlinemode' or even 'newline', with 'crlf' or 'lf' variants.
Cheers!

Now supported with > set fileformat unix or > set fileformat dos.


Add Bitnob wallet to compatibility matrix

Bitnob is a custodial wallet that allows you Buy, sell, borrow, earn, send, receive, and pay with Bitcoin in minutes. It was built in Africa. Opening this issue to add it to the compatibility matrix, i am working on the PR too.

Cool, thanks for letting us know. Looking forward to your PR.


How to ignore npm scripts?

I have a npm script named eslint, then when running task eslint in lint-staged actually I mean to run eslint bin under node_modules rather than npm run eslint script.
So I can only rename my eslint script for now.

For now, renaming your package.json script is the only option. Something like lint would be okay. However, this behavior could be removed in the future. I am closing the issue but feel free to continue the discussion if required.

@JounQin see https://github.com/okonet/lint-staged/issues/296#issuecomment-331890580


Replace "request" by "got"

Less dependency
Use only stream

I use got@5 because node-sass support NodeJS 0.10 and 0.12.
/cc @sindresorhus
Graph deps compare Request Graph vs Got Graph

I'm not thrilled about being pinned to an older version a library, although it does appear to still be receiving update. NodeJS < 4 support is not going away time soon. Our most used version is 0.12.

// @floatdrop

@xzyfer got 5.x will receive updates until Node.JS 0.10 is deprecated.
lgtm.

Thanks for the clarification @floatdrop

We need to revert this because need to support proxies. I didn't realise proxies weren't supported at the time, my mistake.

Sorry about that but got doesn't support proxy @sindresorhus?

Not yet built-in, but you can easily add it: https://github.com/sindresorhus/got#proxies

tunnel current has [failing tests] for node 0.10 and 0.12 which are important to us. It may still work but this doesn't inspire confidence and users are currently experiencing issues.


make leader election option "LeaseDuration/RenewDeadline/RetryPeriod" configurable

In this pr, we set the default value for LeaseDuration/RenewDeadline/RetryPeriod.
But sometimes, the default config is not suitable for every component, so we should make these options are configurable.

/cc @deads2k @soltysh @sttts

I'm a little concerned about adding these logs, because the calculation comment in the origin default catches a very specific case where the kube-apiserver can have 60s network disruption and the user of library-go want to tolerate it.
The reason why we want to customize these 3 parameters is we have a different case where we care about the load that the leader election process created than disruption tolerance. And there will be other cases cares about other aspects in the future.
So from a user's perspective, the logs of kube-apiserver network issue tolerance, graceful lease duration and so are not very useful information and a little confusing.

I'm ok with this in principle, but I'd like to see a klog statement that prints out the calculation that appears in this comment in the original default:

clock skew tolerance is leaseDuration-renewDeadline == ??s
kube-apiserver downtime tolerance is == ??s
lastRetry=floor(renewDeadline/retryPeriod)*retryPeriod == ??s
downtimeTolerance = lastRetry-retryPeriod == ??s
worst non-graceful lease acquisition is leaseDuration+retryPeriod == ??s
worst graceful lease acquisition is retryPeriod == 26s
this gives 107/26=4 retries and allows for 137-107=30 seconds of clock skew
if the kube-apiserver is unavailable for 60s starting just before t=26 (the first renew),
then we will retry on 26s intervals until t=104 (kube-apiserver came back up at 86), and there will
be 33 seconds of extra time before the lease is lost.

where the numbers are correct for the values that are provided. It's a long log line (or multiple log lines), but it really helps explain what will happen at runtime.

I'm a little concerned about adding these logs, because the calculation comment in the origin default catches a very specific case where the kube-apiserver can have 60s network disruption and the user of library-go want to tolerate it.
The reason why we want to customize these 3 parameters is we have a different case where we care about the load that the leader election process created than disruption tolerance. And there will be other cases cares about other aspects in the future.
So from a user's perspective, the logs of kube-apiserver network issue tolerance, graceful lease duration and so are not very useful information and a little confusing.

Also the "clock skew tolerance" part seems not calculated correctly in library-go, from the leader-election pkg comment: https://github.com/kubernetes/client-go/blob/1517ffb8d37c99e6a3a2842bcdee0aa271f0332b/tools/leaderelection/leaderelection.go#L27 It should be tolerant to arbitrary clock skew.

I think the calculations can be done independent of the desired tolerance.  The tolerance is an output of the calculations.

It should be tolerant to arbitrary clock skew.

Only if it remains constant.  When skew shifts (the rate it refers to), it fails.

tolerance

Agree， but tolerance is not everyone's focus,  for example, in the case "load" matters, I would more like to see loadPerHour = 3600/retryPeriod included in the calculation result.

/retest


aarch64: fix BTI in bsaes assembly code

Prevents crashes on AArch64 systems with BTI enabled where the bit-sliced AES implementation gets used.
Found the hard way by @rossburton  - thanks

The other files you mention use AARCH64_SIGN_LINK_REGISTER, which combines PAC (pointer authentication) with a BTI landing pad

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

If you use AARCH64_SIGN_LINK_REGISTER then you need to add appropriate AARCH64_VALIDATE_LINK_REGISTER statements before every return, and ensure that each code path his this only once.
That is additional work (basically applying pointer authentication to the link register) beyond what is necessary to get BTI to not fail.

Merged to the master, 3.3, 3.2 and 3.1 branches. Thank you for your contribution.


Got error during  starter_script.bat execution

After building docker i tried start the script "starter_script.bat" and got this error. It looks like I have a problem with secmaster_db_symbol_loader.py.
How can I solve this?

PS C:\Users\***\desktop\Microservices-Based-Algorithmic-Trading-System> .\starter_script.bat

C:\Users\***\desktop\Microservices-Based-Algorithmic-Trading-System>echo "scripts on jupyter notebook"
"scripts on jupyter notebook"

C:\Users\***\desktop\Microservices-Based-Algorithmic-Trading-System>docker exec -it jupyter-image /bin/sh -c "python /home/jovyan/work/q_pack/db_pack/schema/secmaster_db_schema_builder.py"
Database does not exist.
Creating new database.
Database exists.
Building tables.
Building tables.
Building tables.
Building tables.
Building tables.

C:\Users\***\desktop\Microservices-Based-Algorithmic-Trading-System>docker exec -it jupyter-image /bin/sh -c "python /home/jovyan/work/q_pack/db_pack/schema/secmaster_db_symbol_loader.py"
Traceback (most recent call last):
  File "/home/jovyan/work/q_pack/db_pack/schema/secmaster_db_symbol_loader.py", line 131, in <module>
    main()
  File "/home/jovyan/work/q_pack/db_pack/schema/secmaster_db_symbol_loader.py", line 118, in main
    symbols = parse_wiki_forex()
  File "/home/jovyan/work/q_pack/db_pack/schema/secmaster_db_symbol_loader.py", line 38, in parse_wiki_forex
    rv = client.request(r)
  File "/opt/conda/lib/python3.7/site-packages/oandapyV20/oandapyV20.py", line 306, in request
    request_args, headers=headers)
  File "/opt/conda/lib/python3.7/site-packages/oandapyV20/oandapyV20.py", line 243, in __request
    response.content.decode('utf-8'))
oandapyV20.exceptions.V20Error: {"errorMessage":"Insufficient authorization to perform request."}

C:\Users\***\desktop\Microservices-Based-Algorithmic-Trading-System>docker exec -it jupyter-image /bin/sh -c "python /home/jovyan/work/q_pack/db_pack/schema/risk_db_schema_builder.py"
Database does not exist.
Creating new database.
Database exists.
Building tables.
Building tables.
Building tables.
Building tables.

C:\Users\***\desktop\Microservices-Based-Algorithmic-Trading-System>echo "..."
"..."

Update:
Please add to readme page about new user should:

Create demo or real account in Oanda
Oanda doesn't give public API
New user should generate API key
New user should know his ID
Copy this (3 and 4) to YOUR_DIRECTORY\Storage\q_pack\q_credentials\oanda_cred.py

After this my problem was solved.

Hi @cryptorevizor a new release with a few architectural changes is coming in the next few weeks, I will update the readme in that release.


feat(media): add URL-encoded form data handler

Just dropping a quick sketch from PyCon sprints, this still a bit rough on edges.
We could probably polish documentation & recipes etc, but otherwise this is ready to review as in proposal for inclusion in Falcon 3.0 alpha1.

Just dropping a quick sketch from PyCon sprints, this still a bit rough on edges.

@nZac it is so shockingly simple because we already had that functionality, albeit in a different form, and because it is simple :slightly_smiling_face:
Now, multipart/form-data is a completely different beast... and a really ugly one. I'm still wading through RFCs, and polishing something that at least could be demoed interface and functionality wise, although full correctness and improved performance are going to be challenging.

This looks like it would be super-useful for a project I'm working on right now! Thanks!

Implements #1580

Thanks @kgriffs , merging then!
I'll create a follow-up PR to promote this to default handlers (if we want that?) and to deprecate the old parameter merge approach as per #1580

Yes, I think we want this in default handlers. People can elect not to use it by avoiding req.media - just need to make sure we document that it is enabled by default.

(What is more, people can also cull it from default handlers by creating a new set of handlers by their own. So :+1: :arrow_double_up:  )


[UX QA] Local repos should not be represented as remote repos

The local repo should not be repeated as a remote repo because:

It might not even be part of the Sourcegraph instance
It is already listed as a context source on the "Local section"

Fixed in previous release


Backward compatibility for autotile setup from Godot 3.0.X

Fixes #20746

@akien-mga @reduz i think merging this before alpha is worth

Thanks!


feat: basic exclude for scope

Add basic excluding while the --filter flag is being developed.

Can you also add e2e tests?


Benchmark: aggregated scores - document date time for progress report

would be nice to have a history of models' performance on tasks

Added date time column to primary results. Aggregation still todo. Will need to adjust the "skip if already run" behaviour though; maybe a flag to confirm that it should run an additional test. Could be based on the model name, date cutoff, or a combination.


Update localize.ts

Hello,
normally (like for other projects) are attached (please see screenshot)

understood, it is in 2nd pull request.

If you eplain me "how to", I can make it, in future at once.

Please create one PR with all the files included.


Bind to both touch and mouse events

Fixes touch and mouse bindings so that you can use an external pointing device with a touchscreen device, a common scenario on touchscreen laptops.
Updates release version.

brill, thanks @skye2k2

My pleasure. Thanks for the plugin to begin with!


[Bug][Config-UI] Vulnerabilities in Image

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened

While I'm trying to setup the Config-UI. I am facing the vulnerabilities in the image.

What do you expect to happen
Ease in setting up of config-UI.
How to reproduce
While I'm running it on localhost:4000. It is showing me the following error.
Anything else
No response
Version
main
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

The vulnerabilities and the error 500 are two different issues. I suggest you file another issue for the error you're seeing and attaching container logs to it.

Okay , Surely Will do it.

For the security issue, currently, we're using nginxinc/nginx-unprivileged:1.21 as base image for config-ui, as nginx is stable enough, I guess we could use nginxinc/nginx-unprivileged:latest for get latest security updates from the upstream.

For the security issue, currently, we're using nginxinc/nginx-unprivileged:1.21 as base image for config-ui, as nginx is stable enough, I guess we could use nginxinc/nginx-unprivileged:latest for get latest security updates from the upstream.

Still, use nginxinc/nginx-unprivileged:latest tag in code repo is not a good practice, maybe we could introducing a checklist in release stage to ensure we're including the latest security updates from upstream at that moment.

For the security issue, currently, we're using nginxinc/nginx-unprivileged:1.21 as base image for config-ui, as nginx is stable enough, I guess we could use nginxinc/nginx-unprivileged:latest for get latest security updates from the upstream.

Still, use nginxinc/nginx-unprivileged:latest tag in code repo is not a good practice, maybe we could introducing a checklist in release stage to ensure we're including the latest security updates from upstream at that moment.

Got it 👍

Hi @lavakush07, I tried v0.15.0-rc4 with docker-compose and everything works fine. Do you think you could provide details steps for reproducing the  Config-UI issue? Thanks!

Hi @lavakush07, I'm gonna close this issue due to inactivity. But feel free to open a new issue if you need help.


[Feature] Add shape-aware grouping head in SSN

Add shape-aware grouping head in SSN (Shape Signature Networks)
Support different feature map sizes for grouping classes in anchor generator

Task linked: CU-4hvduv [SSN] Support Shape-aware grouping head (week 1)


Docs [3 of 4]

What this does

adds documentation comments for generated code
removes dead generated code
minor renames

Also, CI is 🔴


Do not show assessment if empty

For example, do not show STAR if no data is available

Will be addressed as part of student profile #373.


I just want to help with date extraction

 Issue by aleksandar-devedzic
Thu Aug 25 21:36:08 2022
Originally opened as https://github.com/codelucas/newspaper/issues/948

These are the names of tags that can be found in SCRIPT or META tags that represent dates, maybe you will find this helpful:
publishdatepublish-date
prism.publicationDate
coverageEndTime
uploadDate
date
published_date
published_time
pubdate
publish_date
Date
published_at
PublishDate
dcterms.created
rnews:datePublished
article:published_time
czhdev.publicationDate
OriginalPublicationDate
og:published_time
datePublished
article_date_original
czhdev.publicationDate
article.published
published_time_telegram
sailthru.date
DC.date.issued
date
parsely-pub-date
publishtime
publication_date
coverageEndTime,publishdate
publish-datepublishedAtDate
creationDateTime
pub_date
updated_time
dateModified
og:updated_time
last-modified
Last-Modified
DC.date.modified
krn:published_time
article:modified_time
modified_time
modifiedDateTime
dc.modified

added in v0.9.2


React 17 support

Error while installing with React 17 dev dependency:
npm i use-error-boundary

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/use-error-boundary
npm ERR!   use-error-boundary@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Are there plans to support React 17?

Hey, yes this package should not break with React 17.
Until I update the peer dependency, you can install the package with either --legacy-peer-deps or --force.

I fixed this in v2.0.6 🎉
Thanks for reporting the Issue!

@cbratschi Thanks a lot!


Allow PureTemplate to have a configurable element type

I'm working on a sortable data table widget and want to leverage the PureTemplate component: https://github.com/algolia/instantsearch.js/blob/develop/src/components/Template.js
Since this is rendering an actual html
, there are instances when I need render an element other than a div (eg tr, td).
Would be great if that were configurable.
@bobylito Any ideas welcome!

You could have a prop RootTag = “div” and when rendering switch div to RootTag

Hi @timkelty thanks for challenging the APIs we propose.
The connectors were created in order to provide this kind of flexibility. As I see things right now, providing a new API that is so specifically dedicated to templates will reinforce their usage. I think the balance of power of the template API, the simplicity of it and the impact on the code of the project is right. I will however sync back with the whole InstantSearch team to get their feelings too.

@bobylito sounds good, I'll stay tuned!

Hi @timkelty if we were to implement this feature, how would it make your code better? Can you show us the 2 versions with and without a new option such as rootTag?

@bobylito here's an example of how I would use rootTag:
const Template = 'instantsearch.js/es/components/Template.js';

class HitsTable extends React.Component {
  renderWithResults() {
    const renderedHits = map(this.props.hits, (hit, position) => {
      const data = {
        ...hit,
        __hitIndex: position,
      };
      return (
        <Template
          data={data}
          key={data.objectID}
          rootProps={{ className: this.props.cssClasses.item }}
          rootTag="tr"
          templateKey="item"
          {...this.props.templateProps}
        />
      );
    });

    return
{renderedHits}
;
  }
}

There really isn't an alternative - aside from duplicating the Template component with my own that allows this, or using a widget that renders a table as divs.

FYI there's now a rootTagName prop on the Template component that allows to render in another element than a div (see #2757).
Keep in mind that this Template component was originally made for internal usage. We wouldn't recommend relying on it.


Redirect to events from home

Description
Previously when you logged in you were shown a home page with the words Did admin panel. Something that does not fit the design.
Now, when you log in it takes you to the /eventos path. It also happens when you click on the page logo.
In summary: every time you try to go to home, it redirects you to eventos.
Note:
this logic only works for admin login, not for provider. You will have to adapt to this verification in the future.
Screenshots
https://user-images.githubusercontent.com/71513679/188319331-2aba10f5-2d6b-451a-8e39-dbd57f8c0709.mp4
Type of change

[x] New feature (non-breaking change which adds functionality)

Please check why deployment fails


Feature request: append

CombinedStream has the following:
var combinedStream = CombinedStream.create();
combinedStream.append(function(next) {
  next(fs.createReadStream('file1.txt'));
});
combinedStream.append(function(next) {
  next(fs.createReadStream('file2.txt'));
});

It would be useful to support append in multistream as well.

What are you trying to accomplish? You can already pass in a function to lazily create a stream (see the readme).

Infinite lazy streams. :)

PR welcome!

PR still welcome, but closing this stale issue.


Add tweaked federal register notices

This moves all of our tweaked federal register notices to this repo.

that's a lot of xml!!


fix: support symlinks, fixes #858

Fix #858.
Use suggestions from:
https://github.com/a-h/templ/issues/858#issuecomment-2245536447
https://github.com/a-h/templ/issues/858#issuecomment-2308354377

Great PR. Thanks for that.


do -i doesn't eat all errors

same problem exists in Nushell.
example, using git branch in a non-repo folder

My guess is that this is related to redirecting the stderr of externals.


Suggestion for update to the installation guide for URCap on a e-Series robot

Been trying to integrate UR10e to ROS 2 foxy with the universal robots driver, and followed Installing a URCap on a e-Series robot. Our UR10e did not come with Remote Control enabled out of the box, and at least from what I've seen, there isn't any guides that have pointed this out. Therefore I suggest a small update to the installation guide, where this is something the user checks before starting to install URCaps.

Thank you for the suggestion. from my understanding it should not necessarily be required to enable remote_control mode to move the robot, but many features will indeed require this. Maybe we can reflect this a bit more.


Add test cases for switch node

I added test cases for switch node to improve  the coverage.

Coverage increased (+0.2%) to 86.616% when pulling 7af6c0e2e2ca54bca7fb4b837930d569ffb85d0d on HirokiUchikawa:master-testcase into cb4f46decceaf39caf608838f1af01dcbbf5f51f on node-red:master.


Blog post: Introduction to SSDF and Adoptium's activities to support secure SDLC

@sxa Some failing checks...

@sxa Some failing checks...

Will aim to get those fixed this week, but thanks for reviewing the content. Was keen to chuck this into a PR for people to review before I went on vacation.

@sxa Some failing checks...

Now fixed.

Superceded by PR in website repository: https://github.com/adoptium/adoptium.net/pull/1227


Add ui-uploader documentation

ui-uploader module is not documented.

https://github.com/angular-ui/ui-utils/tree/master/modules/uploader
If you think more documentation would be appropriate, please open a PR.

@PowerKiKi do you know why the ui-uploader was removed from ui-utils page?

@realtica as far as I know it was never part of http://angular-ui.github.io/ui-utils/, because it does not have a demo/index.html but demo/demo.html instead.
But I just changed that, it should appear soon...


[FLINK-14032][state]Make the cache size of RocksDBPriorityQueueSetFactory configurable

What is the purpose of the change
This pull request make the cache size of RocksDBPriorityQueueSetFactory configurable.
Brief change log

Pass the configurableOptions of EmbeddedRocksDBStateBackend into RocksDBKeyedStateBackendBuilder,  then create RocksDBPriorityQueueSetFactory using the configured cache size

Verifying this change
This change is a trivial work without any test coverage.
Does this pull request potentially affect one of the following parts:

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

Documentation

Does this pull request introduce a new feature?  no

Thanks for the pr. PTAL my comments. And you should also provide a UT Case to verify reading the correct config.

@masteryhx  Thanks for the comments. In the latest commit,  i add the UT RocksDBStateBackendConfigTest#testConfigureRocksDBPriorityQueueFactoryCacheSize to verify cacheSize config.

@flinkbot run azure


Notify for repeated failures doesn't work

Slack plugin version 1.8
Jenkins version 1.611
All other options (notify on start/fail/success/etc) work fine, but notify for repeated failure does not produce any notifications.  Also, nothing comes up in the jenkins logs.

Could not reproduce.  Versions tested:

Jenkins: 1.631 (currently latest as of today), Slack: 1.8
Jenkins: 1.611, Slack: 1.8

Steps taken to attempt to reproduce.

Leave "notify for repeated failure" unchecked
Failed build 3 times
Enable "notify for repeated failure"
Failed build 3 times

Expected behavior was witnessed.

When "notify for repeated failure" was unchecked and the build failed 3 times; I only saw a single notification for the first build but the second two builds did not notify.
When "notify for repeated failure" was enabled and the build failed 3 times; All three builds notified slack.

I couldn't reproduce the behavior you reported.  Perhaps you have your job improperly configured somehow.  Did you upgrade the plugin and witnessed the poor behavior?  If so, go into your jobs and save the job configuration again to overwrite any potential bad settings.  The upgrade process of this plugin is currently shoddy.
If you would like to witness the proper behavior yourself then feel free to bootstrap jenkins with slack configured and join jenkins-slack-plugin.slack.com (see self sign up).
To test the older version Jenkins 6.311:

update the version of this line for the version you wish to test (6.311)
execute ./slack_bootstrap.sh to spin up Jenkins with slack configured.
Run the Test job as a build and be sure to check the fail box when building.

Hi Sam, thank you for the quick and detailed reply.  I bootstrapped jenkins with slack, but the same behavior occurs.
Steps to reproduce (should have included in my OP):

In job slack config, check only "Notify Repeated Failure"
Failed build 3 times

Observed: No slack notifications
Expected: Slack notifications on 2nd & 3rd failures
Only when I added a check for "Notify Failure" on the 4th run did it start sending notifications.
My use case here is to not send a notification on a first failure, but to only notify for any repeated failures.  I'm starting to guess that maybe this wasn't the intention for the feature.

I understand the desired behavior.  I don't think that was the original intention but you could always submit a patch.  Contributions are welcome to make it behave this way.  It shouldn't affect existing behavior as I originally described.  I don't actively develop this plugin.  I only maintain pull requests and releases.

I don't mind working on a fix for this tomorrow.  I'll open a pull request for review.


'pe_direction' trait of DiffusionSummaryInputSpec not being found

Hi. First of all, thanks for making this app - we are excited to try it out in our lab.
We are running a simple pipeline on one subject using docker to test things out:

Very soon after starting, we get this error:

I'm wondering where qsiprep gets pe_direction from. In the JSON files that accompany my DWI files, I believe the Phase Encoding Direction is specific as 'j', but somehow it's getting an empty string: ' '.

I tried working backwards a bit to check in the qsiprep code where DiffusionSummaryInputSpec comes from, but ultimately got a bit lost; any help would be appreciated. Thanks.

Hi @bwinsto2, thanks for trying qsiprep! Does your input data pass BIDS validation? You need to have a "PhaseEncodingDirection" key in your JSON sidecar for this to work

Thanks for your help on this. Yes, the data are BIDS compatible. Just did some research and looks like this is a known issue when converting DICOMs to NIfTIs with Philips data using dcm2niix. I should be able to figure it out and will update.


Cut New Release

Hi there's been some good commits since the last release would it be possible to cut a new one?

Sure, v0.0.3 is up now.


Adds the private TS annotation to _methods()

R: @philipwalton
When testing out the TypeScript functionality, I noticed that there were a bunch of methods on workbox-window that started with _ and were @private in JSDoc, but weren't marked private in TypeScript.
I wonder if this is something we could catch via linting or some sort of post-TypeScript-compilation test?

Coverage remained the same at 77.688% when pulling 40aa6fe961cb2b80e65bd0bf6a0858dc4f154985 on wb-window-private into bd6edcea1f6c7e502b017024673333964e544f8a on master.

Want me to push more changes to this PR that cleans up other instances?

If you want, but it'll like be a ton of files, so if you want to do it in a separate PR, that's fine too.

I did a quick search for the general pattern and found a few more obvious ones. We can include them in this PR, and then if I missed any, feel free to pick them up later.


Problem with label_image.py

I used docker toolbox on windows 10 64-bit and used this command
docker run -it gcr.io/tensorflow/tensorflow:latest-devel
to install tensorflow image.
After retraining of model is successfully done and when I run label_image.py it gives following message

I used this line
curl -L https://goo.gl/tx3dqg > $HOME/tf_files/label_image.py
and then
docker run -it -v $HOME/tf_files:/tf_files  gcr.io/tensorflow/tensorflow:latest-devel
NOTE: Issues that are not bugs or feature requests will be closed. Please ask usage questions on StackOverflow.

TensorFlow installed from (source or binary)?:
TensorFlow version:
Bazel version (if compiling from source):
CUDA/cuDNN version:
GPU Model and Memory:
Exact command to reproduce:

Describe the problem clearly
Source Code / Logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full-traceback. Large logs and files should be attached. Try to reproducible test-case code the bare-minimum necessary to generate the problem

From the error message, it seems that somehow your label_image.py file is corrupt (and contains <HTML> in it). Please confirm the contents of label_image.py are correct.

Thanks for your reply. Yes I found out that somehow the curl wasn't able to put code in the file. I copied and pasted from the site  and now its fine.


Integrate MZ feedback on Quickwit tutorial

We received an email feedback on different papercuts in the tutorials.
Break them down and fix  them for quickwit 0.3.

@fmassot can you have a look at this?


Save-LatestUpdate does not work for WindowsVersion = Windows7

Expected Behavior
"Get-LatestUpdate -WindowsVersion Windows7 | Save-LatestUpdate" should download updates
Current Behavior
Join-Path : Cannot convert 'System.Object[]' to the type 'System.String' required by parameter 'ChildPath'. Specified
method is not supported.
At C:\Program Files\WindowsPowerShell\Modules\LatestUpdate\<IP_ADDRESS>\Public\Save-LatestUpdate.ps1:83 char:39
+             $target = Join-Path $Path $filename
+                                       ~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [Join-Path], ParameterBindingException
    + FullyQualifiedErrorId : CannotConvertArgument,Microsoft.PowerShell.Commands.JoinPathCommand

This fails only for Windows 7. Windows 8 and 10 works fine.
Context
Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

LatestUpdate Version: <IP_ADDRESS>
PowerShell Version: 5.1.14393.2758
Operating System: Server 2016

What's the preferred update for Windows 7 - MSU like Windows 10 and 8 or EXE?

MSU!

Fixed in commit 39b003c637152214b59a71158ffbac9774d8d395

Fixed in release v<IP_ADDRESS>.


Hot to put a

Hello
Thanks for this plugin
How to change the *.js to put a </br> between text and url when we clik for example to the icon tweet
thanks and best regards

Redefine twitter sharing url:
jsSocials.shares.twitter.shareUrl = "https://twitter.com/share?url={url}&text={text}%0a&via={via}&hashtags={hashtags}"


Add repo_type to repo_info docstring

Add repo_type to repo_info docstring.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Refines v3.0 upgrade docs

Description

Enhances several sections
Corrects the upgrade page
Changes troubleshooting to downgrading
Other updates
Refinement/enhancements to be continued in further PRs

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

@caseydavenport Not sure when you made your comment about having links to the next steps at the bottom of each page but I think I already have these.


feat(openchallenges): add "MLCube" as a submission type

Fixes #2509
Changelog

update OC Data spreadsheet to include mlcube_submission column
update db-update script to include "mlcube_submission" in the CSV dump
add mlcube as an enum value to the challenge_submission_type database table
add mlcube to the API description
regenerate:

OpenAPI spec (with nx build openchallenges-api-description)
Java files (with nx run openchallenges-challenge-service:generate)
Angular API client (with nx run openchallenges-api-client-angular:generate)

add "MLCube" as one of the facet values for Submission Type

Preview

Describe challenge_submission_type table:

Challenge search page:

Looks like there are issues with sonar:

@tschaffter could these possibly be related to this message you sent on Slack?

I minor improvement could be to list the submission types in alphabetical order, with "Other" listed last?

minor improvement could be to list the submission types in alphabetical order in the UI, with "Other" listed last?

Done ✅


Add a country code to the geocoder request

I have a few questions :

Should the country code be an enum instead of a string within the Request object?
Should we validate that the country code is in the isoCountries map
Should the country code should a java Optional instead of being "nullable"?
Should I use a specific naming convention for my unit tests?

Should the country code be an enum instead of a string within the Request object?

What about checking if the iso code is in Locale.getISOCountries().

Should we validate that the country code is in the isoCountries map

In the worst case, the user will provide a wrong country code and will receive an empty response.

Should the country code should a java Optional instead of being "nullable"?

Yes, that's a good idea.

Should I use a specific naming convention for my unit tests?

I usually add the Test suffix to the class being tested.


Release 0.18.0

to coincide and be compatible with devnet release on April 9

note: I've triggered ci against berkeley to check for compatibility against the berkeley node


Adding @mixin make-col-ready() to grid.scss

Despite being referenced in the docs (http://daemonite.github.io/material/docs/4.0/layout/grid/#mixins), make-col-ready() was missing from the actual file.
All I did was copy the @mixin from the latest Bootstrap v4-release (https://github.com/twbs/bootstrap/blob/v4.0.0/scss/mixins/_grid.scss).
(PS: I see most of the other mixins here deviate from the bootstrap version, but I'm assuming there's a reason for that).

I missed this one probably because this mixin is not actually used for compiling the CSS, but you are right, we should include this since it is mentioned in the docs and can be useful for people in custom.scss.

@sesemaya just to clarify though: the other discrepancies with mixins in that file (and mixins in other files I might come across):
If they have a different syntax is it intentional or just overlooked (because who checks a function's input variables) and I should submit a PR?

Hi @justlevine feel free to submit PRs. Upon a quick review, I would say that mixins related breakpoint and grid are probably overlooked. Not sure about the others, some may be intentional, some may be due to different linting rules. Again, feel free to submit PRs, even if some are intentional, I maybe at least clarify the reasons for you.


addressing non-teaching bug in #250

See discussion in #250.  This adds a computation of whether an item is a non-teaching item if that flag has not been previously set.  This removes the dependency on the SectionName column, which we are no longer exporting (since it is redundant information).

This bugfix branch didn’t work for me locally. I haven’t run a development server on my home machine for a while, but think that I fired it up properly.
The test that fails is to load a working schedule, write it out and read it right back in. I did this with this existing/old schedule, which has the sectionName field:
?csv=https://kvlinden.github.io/data/full_schedule_2023.csv

I presume that you tried this. ?
keith

I think that is exactly what I did.  I used your link from #250, and actually fetched the CSV file.  Read it in, wrote it out, re-exported.  I didn't see any issues.  Can you describe exactly what problem we should be looking for?
Here's what I see after import/export/re-import locally using the bugfix branch.  I sorted by other hours.

For the record, here's how I'm running locally:
$ pwd
/Users/rpruim/projects/github/course-schedulizer/client-course-schedulizer
[rpruim@ ~/projects/github/course-schedulizer/client-course-schedulizer]
$ git branch
* bugfix/section-name-for-other-duties
  dart-sass
  feature/chairs-meeting-cleanup
  feature/custom-dates
  feature/issue250-csv-export
  feature/issue268-convert-instructional-method
  halfSemesterConflict
  production
[rpruim@ ~/projects/github/course-schedulizer/client-course-schedulizer]
$ npm start

Starting the development server...

  Line 3:10:    'Day' is defined but never used                               @typescript-eslint/no-unused-vars
  Line 49:11:   'meetingStartInternalStr' is assigned a value but never used  @typescript-eslint/no-unused-vars
  Line 51:11:   'meetingEndInternalStr' is assigned a value but never used    @typescript-eslint/no-unused-vars
  Line 56:11:   'roomCapacityStr' is assigned a value but never used          @typescript-eslint/no-unused-vars
  Line 114:13:  'sectionNameStr' is assigned a value but never used           @typescript-eslint/no-unused-vars

Search for the keywords to learn more about each warning.
To ignore, add // eslint-disable-next-line to the line before.

The eslint warnings have been addressed in my other PR.

That looks good - there must be something in my local environment that is messing this up.
I'd say push this fix to production expecting that your environment is set up properly.

I'm not sure I can review my own PR.

@kvlinden, I've merged into production.  Check to see that things are working for you there.  If so, we can declare victory for now.

The production branch still fails for me. Questions:

How long do updates to the production branch take to go live?
Is this the URL you’re using: https://senior-knights.github.io/course-schedulizer/#/?csv=https://kvlinden.github.io/data/full_schedule_2023.csv

Loading this file, then exporting/importing fails for me using Firefox and Chrome on Windows, in both the public browser and the private browser.

let me do an npm run deploy.  I keep forgetting about this step.
Production build being optimized as I type.  Should be live in a minute or so.

The build folder is ready to be deployed.

Find out more about deployment here:

  bit.ly/CRA-deploy

><EMAIL_ADDRESS>deploy
> gh-pages -d build

Published

works for me from https://senior-knights.github.io/course-schedulizer/#/ now.

Also from https://senior-knights.github.io/course-schedulizer/#/?csv=https://kvlinden.github.io/data/full_schedule_2023.csv

It's better now, but there's still one smaller bug.
The update appears to work for every non-teaching activity entry except the first one. For the fall-schedule2023 example, do the load-export-load cycle again and look at Vic Norman's teaching load fall courses. I see a "--" course there, and note that clicking on this fall courses no longer works. And I confirmed the first-row diagnosis by reordering the non-teaching entries and confirming that whatever is first is messed up.

Hmm... interesting bug.  I wonder if this is related somehow to the logic for checking for an existing section or course.

Looks like it was roughly what I imagined.  There are two else blocks at the end of the import
    // Otherwise, add the new section to the existing course

  // Otherwise, add the new course to the schedule

I put the code to infer the non-teaching status in both blocks.  It must be that all the non-teaching items are registered as one "course", so the first one in was in the second else block, which did not have this code.  Adding that one line seems to fix the issue @kvlinden is seeing.
I'll create a PR.
Even if this seems to be fixed, we should either leave this open or create a new issue to prompt creating some tests.


Add support for previewing images in room scrollback

An image says more than a thousand words:

There has been some work to get some small change into ratatui that allows for "skipping" of rendering some cells (characters). This in turn allowed to make a crate ratatui-image that provides a image widgets for ratatui, taking care of the terminal's graphics protocol automatically. Currently the supported "protocols" are sixels, kitty, and unicode-halfblocks. iTerm2's protocol should be easy to add, I just don't have access to a mac.
This PR uses ratatui-image widget's render() method to render images in the ScrollBack widget, in the chat lines. This seems hacky, but this kind of usage was actually intended and recommended for these kind of use cases in the discussion on the ratatui PR.
Currently, the download and image processing happens in one spawned tokio task per attachment. I also have a branch where only one "worker" is created, but I don't actually know if that is an actual improvement.  I mainly made that branch/version to learn a bit more about tokio/tasks/threads in rust.

really looking forward to this!

It really only works with this patch on Alacritty, which seems to work because it simply never draw over image graphics. I'm working on fixing this in  tui-rs-revival/ratatui in the linked PR, by setting some area to be "skipped".

This will be great. I am using foot on wayland/sway should work. please release! :+1:

I was happy to see movement in this PR today, how is going? do you think if I patch this myself will it be somehow a bit stable?

@r3k2 I don't know what you mean by "patch it up". I can give you a status update though:

[x] Graphics support merged in ratatui and graphics related code has been extracted to new crate ratatui-image.
[x] Iamb uses ratatui-image to render images with whatever protocol is detected (sixel, kitty, or unicode).
[ ] The attachments which are "autodownloaded" for rendering are not cached in any way (this should be configurable).
[ ] Windows builds won't work because sixel lib probably won't compile / link correctly and is missing terminal-font-size detection (rustix). We should be able to make use of the relevant feature in ratatui for font-size, but protocol-guessing is a whole 'nother can of worms. Maybe it should guess on linux, and just have a configuration setting for windows users to e.g. force sixels.

@benjajaja cool, who cares about windows? :D :D just release it and say only works on Linux/Nix systems for now and that windows will come.

I see all check passed and such, why we are not adding this already to the main IAMB? :thinking:

As @craftyguy said, this is a big feature, and I like to make sure I understand and try out PRs locally before merging, so that I can document them correctly on the website and answer questions in #iamb-users when they come up.
I've been playing around with this locally and it's really cool! :tada: This is amazing stuff @benjajaja ! Thank you for doing the halfblocks work, too, it'll make it possible for people without sixel-aware terminals or kitty to still get image previews.
I made a couple small changes in 164503b8dc1eb5d12fe97f3c7f5dde75da52f14d: I moved the picker setup code into src/base.rs so that it can run as part of ChatStore::new, and fixed a couple issues I ran into where the image_previews dir didn't exist yet, and images were missing the x offset for placing them in the right vertical split.
I see that you just pushed the updates to use<EMAIL_ADDRESS>yesterday. If you have anything else you want to add to the PR, let me know. but otherwise I'm down to merge this, and take care of anything else in a follow-up PR.

@benjajaja I've pushed some example docs to https://github.com/ulyssa/iamb.chat/pull/18 . Let me know if you think that anything else should be mentioned there.

@ulyssa There is nothing else I want to add for now. At some point later rataui-image will get support for iTerm2's graphics protocol (I can't test it because I don't have any mac around), but that should just be version bump.
Thank you for moving the setup code!


Add test for fire event in rfxtrx component

Description:
Add test for fire event in rfxtrx component
Checklist:
If code communicates with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

You don't need to wait for approval to merge PRs that contain tests


AUI-1930 Change functionality of add cols

Just started reviewing :) :octocat: Sent from GH.

Pull request submitted to https://github.com/fernandosouza/alloy-ui/pull/2. See changes here. :octocat: Sent from GH.


SET with EX PX NX XX

Add to SET the functionalities of EX PX NX XX, as described in https://redis.io/commands/set for Redis 2.6.12.

PR https://github.com/fppt/jedis-mock/pull/92


[question] Does VersionReq behave the same if the patch version is omitted?

According to the docs on VersionReq, 1.2.3 and ^1.2.3 are treated the same. This doesn't seem to be true if the patch version is not specified. Is that intentional?
https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=f5f25e18aa79eaa8a6837773c6ef1561

Same question here. I spend some time figuring out why my code limits version specified as 1.0 to the range of ≥1.0.0 and <1.1.0, while I was expecting the upper bound to be <2.0.0. Turned out to be because of SemVer.
It does not match the way how Cargo versioning works.

It looks like this behaviour changed between 0.10.0 and 0.11.0 and the reason Cargo sees different behaviour is it's currently on 0.10.0.

This is fixed in semver 1.0.0. major.minor and ^major.minor mean the same thing.


collinearity.pl

(base) appledeMacBook-Pro-4:MCScanX fatima$ perl add_ka_and_ks_to_collinearity.pl -i ../data/at.collinearity -d ../data/at.cds -o at.collinearity.kaks
Can't open perl script "add_ka_and_ks_to_collinearity.pl": No such file or directory
i am facing this problem. anybody guide me. how i can solve this problem

Looks like you need to specify the full path to the program, or add it to your $PATH (e.g. ~/bin/)

Thank you so much for your reply.
Now i shifted  MCscanX in bin folder and also add the Path. But still i am getting this error. please   help me . i will be veryyyy thankful.
BEGIN failed--compilation aborted at add_ka_and_ks_to_collinearity.pl line 5.
In my mac have Clustalw2.
please guide me about this error.

From: Reuben W Nowell<EMAIL_ADDRESS>Sent: Sunday, July 19, 2020 2:34 AM
To: reubwn/collinearity<EMAIL_ADDRESS>Cc: SAMANDOLL<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [reubwn/collinearity] collinearity.pl (#4)
Looks like you need to specify the full path to the program, or add it to your $PATH (e.g. ~/bin/)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/reubwn/collinearity/issues/4#issuecomment-660523105, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHWULUCUIKGYXQ74KSV2JKDR4HTNBANCNFSM4O73XBZA.

Line 5 refers to the module Getopt::Long - try cpanm Getopt::Long or conda install -c bioconda perl-getopt-long (if you use conda) to install it.

according to your instruction, i have installed with conda and CPAN successfully this module. but still have same error.
line 5 ;
use Bio::Tools::Run::Alignment::Clustalw;
please guide me again.

From: Reuben W Nowell<EMAIL_ADDRESS>Sent: Sunday, July 19, 2020 2:53 AM
To: reubwn/collinearity<EMAIL_ADDRESS>Cc: SAMANDOLL<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [reubwn/collinearity] collinearity.pl (#4)
Line 5 refers to the module Getopt::Long - try cpanm Getopt::Long or conda install -c bioconda perl-getopt-long (if you use conda) to install it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/reubwn/collinearity/issues/4#issuecomment-660525387, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHWULUHY4D75223SSD7UYBLR4HVS7ANCNFSM4O73XBZA.


[DO NOT MERGE] Add support for non-OIDC audience

Resolves #11

The audience parameter is only available when you choose the Auth0 server template:

👇

For sure it wouldn't make sense for the Google template. And since audience is not part of the official OIDC spec (it's more of an extension), it doesn't make sense for the Custom server template either.
If you check the Audience checkbox, you can provide an audience value:

Providing an audience will then allow you to specify non-OIDC scopes:

The above results a /authorization request that looks like:

There are a couple minor tweaks to the dev/build tools, including better instructions in the README as well as the introduction of the NON_SECURE_SESSION environment variable so that cookies don't need to be HTTPS when served from localhost.

Audience support is no longer needed with Auth0 since you can now set the Default Audience at the tenant level.


[HUDI-7508] Avoid collecting records in HoodieStreamerUtils.createHoodieRecords and JsonKafkaSource mapPartitions

Change Logs
This block of code is problematic and can lead to OOM when we are we converting the iterator into a list and then returning the iterator back. This just holds up memory in the heap when the executor is running this block of code.
https://github.com/apache/hudi/blob/master/hudi-utilities/src/main/java/org/apache/hudi/utilities/streamer/HoodieStreamerUtils.java#L86
        records = avroRDD.mapPartitions(
            (FlatMapFunction<Iterator<GenericRecord>, Either<HoodieRecord,String>>) genericRecordIterator -> {
              if (autoGenerateRecordKeys) {
                props.setProperty(KeyGenUtils.RECORD_KEY_GEN_PARTITION_ID_CONFIG, String.valueOf(TaskContext.getPartitionId()));
                props.setProperty(KeyGenUtils.RECORD_KEY_GEN_INSTANT_TIME_CONFIG, instantTime);
              }
              BuiltinKeyGenerator builtinKeyGenerator = (BuiltinKeyGenerator) HoodieSparkKeyGeneratorFactory.createKeyGenerator(props);
              List<Either<HoodieRecord,String>> avroRecords = new ArrayList<>();
              while (genericRecordIterator.hasNext()) {
                GenericRecord genRec = genericRecordIterator.next();
                try {
                  HoodieKey hoodieKey = new HoodieKey(builtinKeyGenerator.getRecordKey(genRec), builtinKeyGenerator.getPartitionPath(genRec));
                  GenericRecord gr = isDropPartitionColumns(props) ? HoodieAvroUtils.removeFields(genRec, partitionColumns) : genRec;
                  HoodieRecordPayload payload = shouldCombine ? DataSourceUtils.createPayload(cfg.payloadClassName, gr,
                      (Comparable) HoodieAvroUtils.getNestedFieldVal(gr, cfg.sourceOrderingField, false, props.getBoolean(
                          KeyGeneratorOptions.KEYGENERATOR_CONSISTENT_LOGICAL_TIMESTAMP_ENABLED.key(),
                          Boolean.parseBoolean(KeyGeneratorOptions.KEYGENERATOR_CONSISTENT_LOGICAL_TIMESTAMP_ENABLED.defaultValue()))))
                      : DataSourceUtils.createPayload(cfg.payloadClassName, gr);
                  avroRecords.add(Either.left(new HoodieAvroRecord<>(hoodieKey, payload)));
                } catch (Exception e) {
                  if (!shouldErrorTable) {
                    throw e;
                  }
                  avroRecords.add(generateErrorRecord(genRec));
                }
              }
              return avroRecords.iterator();
            });

Impact
No change in public API, this is making mapPartitions part of the code memory efficient instead of collecting the results in the executor.
Risk level (write none, low medium or high below)
Medium
Documentation Update
None.
Contributor's checklist

[x] Read through contributor's guide
[x] Change Logs and Impact were stated clearly
[x] Adequate tests were added if applicable
[ ] CI passed

hey @vinishjail97 : can you attach the memory profileing you did before and after this patch. and rebase w/ master. we are good to go

hey @vinishjail97 : can you attach the memory profileing you did before and after this patch. and rebase w/ master. we are good to go

15th March: Basic OOM Test (Consume 2M events, each payload is approximately 1KB with 2 maxExecutors and 1GB memory) and dynamic allocation ratio was 0.002 so essentially only 1 executor will be used as tasks spawned are not enough.
driver:
coreLimit: 2000m
coreRequest: 1800m
cores: 2
labels:
orgId: 0c043996-9e42-4904-95b9-f98918ebeda4
version: 3.1.1
memory: 2g
serviceAccount: staging-spark
dynamicAllocation:
enabled: true
initialExecutors: 0
maxExecutors: 2
minExecutors: 0
executor:
coreLimit: 1000m
coreRequest: 750m
cores: 1
labels:
orgId: 0c043996-9e42-4904-95b9-f98918ebeda4
version: 3.1.1
memory: 1g
Without the fix, the stage was failing with executor OOM after 20min.

After using this fix, the same stage completed in 17min with one executor.


Add embedClass for embedded media

Added embedClass and set it to embed-responsive-16by9. Close #8


Update README.md

Adds openapi json schema generator to Java section because it now supports generation and validation of schemas in java
Per the latest release: https://github.com/openapi-json-schema-tools/openapi-json-schema-generator/releases/tag/4.1.0

Great!


OCM-11030 | fix: honor current setting instead of populating as nil

OCM-11030
Change type

[ ] New feature
[x] Bug fix
[ ] Build
[ ] CI
[ ] Documentation
[ ] Performance
[ ] Refactor
[ ] Style
[ ] Unit tests
[x] Subsystem tests

Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.

/retest


Explicit Helm install ordering only required on OpenShift, and breaks cleanup elsewhere

The Portieris Helm chart doesn't always properly clean up installed resources - this is because we override the default Helm object creation logic with Helm preinstall hooks, and as the Helm documentation states, resources annotated with hooks are considered unmanaged by Helm and will not be removed on chart uninstall.
This annoyed me enough times to cause me to investigate, and I realized that we don't actually need to muck with Helm's installation ordering for most cases - it already does the right thing, which is why the use of Helm hooks is generally discouraged in most cases.
The only time we need to override the default Helm behavior (and break chart resource cleanup) is if we're using OpenShift, which has a resource creation dependency limitation that doesn't play nice with Helm.
If we're using OpenShift, we create an OShift-specific resource: helm/portieris/templates/securitycontextconstraint.yaml which breaks unless we force nonstandard Helm resource creation ordering.
To improve the chart removal process for everyone that isn't an OpenShift user, I wrapped the offending hooks in a conditional - this means that

if you aren't running on OpenShift, helm install portieris/helm uninstall portieris will do what you expect and clean up properly.
if you are running on OpenShift, helm install portieris/helm uninstall portieris will do exactly what it does today, and force a nonstandard resource creation order as required by the OpenShift-specific SecurityContextConstraints custom resource, leaving orphaned resources on uninstall.

Thanks for this, it works for me in the way it is described.