Find a good feature voting solution.

Have tried theideawall.com Seems like it could work as a start.
Big minus it seems as exporting data is going to be hard aka web scrape. So if i want to change its back start over.


Item Permissions and Visibility: Broken URL

The page includes a link to "Catalog Admins" which takes us to a 404 page.

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

ID: 212fb765-5319-c1f1-3eaf-f2fdd86e6425
Version Independent ID: 850e1070-404e-1270-721e-2abb79abfa47
Content: Item Status & Moderation - PlayFab
Content Source: playfab-docs/features/economy-v2/catalog/item-status.md
Service: playfab
GitHub Login: @wesjong
Microsoft Alias: wesjong

URLs on the page have been fixed!


PDF Export-All Allows Country Check Circumvention

Your Question

Documentation File: https://www.coronawarn.app/en/faq/results/#eu_dcc_export
Line / Paragraph:

"Unlike the export of individual certificates, the export of all certificates is not limited to those issued in Germany, taking into account all EU digital COVID certificates."

Question:

What is the reasoning behind not filtering foreign certificates in the "export all" feature?
Right now (CWA version 2.24, 2.25), I can simply import a single foreign DCC, click export all, and I get a nice 1-page PDF of my foreign DCC with a German look around it. Why prevent this in the individual export, but not in the bulk export?
What is more: the individual export (on Android) is hidden in the certificate details, behind the overflow menu. From the certificate landing page, this requires 4 taps and 1 scroll.
The export-all on the other hand is on the certificate landing page and is clearly visible through its icon. 1 tap away.
Thus it is much more exposed to the user.
Why this difference? What are the two different threat models that you applied here?

Related to https://github.com/corona-warn-app/cwa-wishlist/issues/836

See also https://github.com/corona-warn-app/cwa-website/issues/2958#issuecomment-1161932229 & following comments.

I'm interested because as far as I understand the original intention was to limit abuse. I.e. make it harder to disguise a foreign cert as a German cert. For example, Switzerland introduced a similar limitation to only transform Swiss-issued DCCs to "light certificates" and PDFs after media reports of mal-issued German certs. Hence I was surprised to see that this is by-design according to the FAQ.
After all, DCCs are an official document. As a comparison: you don't want to make it trivial to create a German-signed Personalausweis with the 🇨🇭 on it, nor a Swiss-signed Personalausweis with the Bundesadler.
So did the German threat model change? Is abuse only an issue for individual exports? Or is abuse not an issue at all anymore (and the individual export is just lagging behind and will be allowed for certs of all nations in a future version)?

@thgoebel the main reason for restricting the original export to DCCs issued by Germany was simply that there were legal concerns as to what template to use for DCCs issued by other countries, as there is no standardized template across countries.
In the meantime, these concerns have been dismissed. The batch export uses the DE template for DCCs issued by Germany and a similar generic template for DCCs issued by other countries.
There are ongoing discussions whether to enable the single export also for non-DE DCCs (see https://github.com/corona-warn-app/cwa-wishlist/issues/836).


Basic enum validation

closes #913

Not quite ready for merge yet. Shoring up an issue with nulls.


Implement a test producing a jwt with array element undisclosed

Spec: https://drafts.oauth.net/oauth-selective-disclosure-jwt/draft-ietf-oauth-selective-disclosure-jwt.html#section-6.1
Base Branch: https://github.com/adorsys/keycloak-oid4vc/tree/issue-25638
Before You Start
Have a look at how to contribute

Implemented with #12


SSL connection write event crash

@htuch FYI we have seen a few of these crashes since our last deploy. I suspect this might somehow be related to https://github.com/lyft/envoy/pull/558 but I'm not sure how yet. I'm going to poke around a bit now.
Backtrace:
#0  0x000000000074d64d in evbuffer_peek (buffer=0xee87960, len=-1, start_at=<optimized out>, vec=0x7fbab1a6f830, n_vec=288926) at buffer.c:2814
#0  0x000000000074d64d in evbuffer_peek (buffer=0xee87960, len=-1, start_at=<optimized out>, vec=0x7fbab1a6f830, n_vec=288926) at buffer.c:2814
#1  0x0000000000616a3b in Buffer::OwnedImpl::getRawSlices (this=this@entry=0x1f3fcf80, out=out@entry=0x7fbab1ed8260, out_size=out_size@entry=288926) at /srv/repos/envoy-private/envoy/source/common/buffer/buffer_impl.cc:44
#2  0x00000000006d23d7 in Ssl::ConnectionImpl::doWriteToSocket (this=0x1f3fcf00) at /srv/repos/envoy-private/envoy/source/common/ssl/connection_impl.cc:143
#3  0x00000000006a4c65 in Network::ConnectionImpl::onWriteReady (this=0x1f3fcf00) at /srv/repos/envoy-private/envoy/source/common/network/connection_impl.cc:374
#4  0x000000000075c1b4 in event_persist_closure (ev=<optimized out>, base=0x315ab00) at event.c:1580
#5  event_process_active_single_queue (base=base@entry=0x315ab00, activeq=0x2fbed50, max_to_process=max_to_process@entry=2147483647, endtime=endtime@entry=0x0) at event.c:1639
#6  0x000000000075cb9f in event_process_active (base=0x315ab00) at event.c:1738
#7  event_base_loop (base=0x315ab00, flags=0) at event.c:1961
#8  0x0000000000615338 in Worker::threadRoutine (this=0x31fe860) at /srv/repos/envoy-private/envoy/source/server/worker.cc:62
#9  0x0000000000619ba1 in Thread::Thread::Thread(std::function<void ()>)::{lambda(void*)#1}::_FUN(void*) () at /usr/include/c++/4.9/functional:2440
#10 0x00007fbab4681184 in start_thread (arg=0x7fbab2341700) at pthread_create.c:312
#11 0x00007fbab3ea037d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

From looking at this, #558 was deployed by us on 3/14. We had a deploy on 3/16 and first saw this crash very early in the morning on the 3/18, so I'm a little suspicious the cause is #558 though it is possible. The delta between those deploys was fd58242d2bda61487aadff25af64646e08631151 .. 1d5035fd0b7bc8e721d059720736a31eb005e329.

I think this is actually a stack overflow because the write buffer contains a giant number of small buffers that we are trying move into a chain. I doubt this is related to #558, and is probably just related to traffic patterns, moving write buffers, and potentially changes in libevent 2.1.8.

I suspect this is somehow related to new traffic patterns, and the fact that we move data always vs. copying small chunks. The fix here is not trivial and needs a bunch of thinking.

Yeah, I don't think #558 would significantly affect the number of chunks given the 1MB default set. Maybe could get big gains by setting a minimum chunk size (e.g. 1KB) and trying to merge (via copy) into the previous chunk. This would come at the expense of some internal fragmentation if you had traffic patterns like LITTLE BIG LITTLE BIG .., but LITTLE LITTLE .. and BIG BIG ... would be fine.

I'd suggest disabling the read buffer limit temporarily (it's a one line change to the doReadFromSocket()), which would make the read buffer limit PRs impotent without having to roll back, if there is any remaining concern. We typically do full rollback at Google though, so I'm good with that too if you think it's wise.

@htuch I don't think this issue is related to your changes so we don't need to revert. It's a pathological case where downstream is not accepting writes, the upstream writes are small, and we are always moving data vs. copying if the data is very small. I will come up with a fix.


User Defined Functions in initial_hive_commands_*

Hi,
I am checking out how your repo is structured and have some questions. I haven't used java before so I would really appreciate it if you can clarify some points for me.
As an example for route interpolation the following query is executed:
insert overwrite table {provider_prefix}_cdr_by_uid_trip_routing_array_apd partition (pdt) select uid,f_routing(uid,arr,"{osm}","{voronoi}"), pdt from {provider_prefix}_cdr_by_uid_trip_realloc_array_apd where (size(arr)>0 and  size(arr)<={max_size_interpolation})
which uses f_routing and that function is in turn defined in initial_hive_commands_interpolation.json as:
"create temporary function f_routing         as 'jp.ac.ut.csis.pflow.turkcell.hive.udf.TurkcellRoutingUDF'"
Am I supposed to have these Hive user defined functions somewhere? I downloaded PFlow from sekilab github, but can't find any such related functions.
Similarly some functions like FindPolygon are defined as "create temporary function FindPolygon as 'com.apichon.mobility.hive.udf.FindPolygon'", which are UDFs written by Dr. Apichon Witayangkurn I assume.
Thanks a lot in advance.

i have already uploaded lib. please check folder lib.


ERROR ReferenceError: google is not defined

google is not defined  Error

you need to place the google script in the "Head" html section.

This thing happened because google is used before it initialized. Because of inactivity of this package, I created my own package which is fully compatible with this one, code base was used from this package and adjusted to new coding standards.
You can try:
https://www.npmjs.com/package/@angular-magic/ngx-gp-autocomplete


Amazon Security Lake integration - DTD - Python script

Description
A middle point between creating a Logstash output plugin or codec to send binary data to S3 and using a Lambda function with an auxiliary S3 bucket is to continue the Logstash pipeline with a custom script that transforms and uploads the data.
The benefits of this approach are:

The data transformation and upload process is independent of the Logstash's ingest pipeline.
The script can be self-hosted, reducing costs.
The script can be used for future integrations starring integratord.
Agile development, as Python is a language we are confident with, unlike Ruby.
We do not need to learn and comply with Logstash's plugins development requirements and lifecycle.

Functional requirements

Read data from the Logstash's pipeline.
Transform our data to OCSF compatible schema.
Encode our data as Apache Parquet.
Upload the data to an S3 bucket.

Implementation restrictions

The Logstash pipeline will invoke our script using the pipe output plugin, so the script must be able to read the data from standard input.
To upload the data, use AWS SDK for Python (Boto3).
Ensure data encryption is enabled and pay special attention to safe handling of AWS credentials.

Additional information
As a guideline, check how other companies do it. For example, CrowdStrike.

What are you thinking for mapping Wazuh events to OCSF event classes? Will you likely do it as a single class of "Security Finding(2001)" or will you try to break it out to various classes?

What are you thinking for mapping Wazuh events to OCSF event classes? Will you likely do it as a single class of "Security Finding(2001)" or will you try to break it out to various classes?

For the time being, we are researching various approaches to the pipeline mechanism itself as the OCSF mapping is being developed in parallel to our effort here.

What are you thinking for mapping Wazuh events to OCSF event classes? Will you likely do it as a single class of "Security Finding(2001)" or will you try to break it out to various classes?

We are investigating that and should have a reply shortly. In the meantime, we'll use the "Security Finding(2001)" class, fill the required values, and include the rest of the data in the "unmapped" field, so we can test whether the integration works, even if it's not mapped properly yet.
We'd like to use various classes, but we'll see.

Now that we have a docker testing environment, we are moving back to this one.
In my tests I'm also including a s3.ninja local bucket for ease of debugging.
In order to authenticate and write to a local S3 bucket using pyarrow, we need to explicitly instantiate a fs.S3FileSystem object in order to set the endpoint_override parameter to the local bucket's IP address and listening port.
I've opted for using boto3 to handle reading the .aws/credentials file so as to be able to read a single profile's credentials as well.
As of right now, the logic for this lives within a function, but this should ideally be moved out to a class.

The current date (used for the files' timestamps) was being evaluated at the begging of the main block and not within the loop.
Moving it to the appropriate spot now generates files properly.

Latest update on https://github.com/wazuh/wazuh-indexer/pull/186#issuecomment-2006985534


CI/Add versioning for docker hub

We need to add tagging for the images in the Docker Hub.
I think, we need to add changelog.md to store changing in code.

Closed issue by PR #36


feat: [PROD-11411] In Table component, blur trigger submit

Could you change the commit message please ? The commit prefix should be fix: instead of feat: :slightly_smiling_face:


Set execinfo=no by default when compiling for Linux/*BSD

Alpine 3.17 and later no longer provide execinfo in its repositories, making compilation impossible unless you pass execinfo=no.
I suppose a better approach would be to use execinfo on non-glibc systems when available on the system, and skip it otherwise. I'm not sure how to implement this though.

See https://github.com/DataDog/dd-trace-php/issues/1824.

Thanks!


While updating, mark baseOs state as DEFERRED instead of throwing an error

WIP because controller changes are yet to be deployed on alpha.
Signed-off-by: adarsh-zededa<EMAIL_ADDRESS>

Does Adam need to support the new deferred enum value?

Are you asking in a sense whether it would keep working (I guess the answer is yes since Eden is passing) or whether it can actually take advantage of the new value @eriknordmark ?

Hey @eriknordmark @adarsh-zededa -- should we merge this now?

Hey @eriknordmark @adarsh-zededa -- should we merge this now?

Yeah @rvs


Wrong sizes set when allocating gTestNames in suites: test_bruteforce and test_half

I have got a null pointer dereference error when testing math bruteforce and half in function parseAndCallCommandLineTests while dereferencing parameter argv:
int parseAndCallCommandLineTests(... )
{
    ...
    if( argc == 1 )
    {
       ...
    }
    else
    {
        for( int i = 1; i < argc; i++ )
        {
            if( strchr( argv[i], '*' ) != NULL )
            {
                ...
            }

This parameter is initialized in function ParseArgs in main.cpp:
static int ParseArgs( int argc, const char **argv )
{
    int i;
    gTestNames = (const char**) calloc( argc - 1, sizeof( char*) );
    ...
}

The first parameter of calloc should be argc in stead of argc - 1 as other tests do to avoid the null pointer dereference error. This happens in following files:

test_conformance/half/main.cpp
test_conformance/math_brute_force/main.cpp

Best Wishes!
Apr. 11th. 2020

math_brute_force was fixed (#1240).
half wasn't modified but a similar fix is most likely needed.


Magic numbers

https://github.com/ahmetsduru/quadcopter_simulator/blob/b99e3547c4e7605bed792276c67fa716b4358350/src/mid_level_cont.cpp#L33
Do not add magic numbers in your code. You can set parameters to defaults, but they should better be read from a config, or passes as an argument.

ok


Add env variables for quickly running in both dev env and production.

Specific example is redis instance. Dev env should just ref local redis node without configuration. This is also related to #24

Resolved by https://github.com/3box/3box-pinning-server/pull/42 and another pr later to make redis optional for development


add pschalk to the repo

@hawky-4s- my colleague Patrick started working on this project as well. Could you add him as a member, so he can interact with the repo directly? Thanks.

Are there any updates to this?

I sent Jan the corporate CLA today.

You just received a company CLA ... so please go ahead!

Invitation sent.


Synchronize OWNERS_ALIASES file with Github teams

This pull request updates the OWNERS_ALIASES file, based on the current Github team associations.

/lgtm

/approve


letter line under cursor

I started to use the keyboard and find difficult to see  which letter i'm on.
it will be nice to have a wheel under the cursor or over the bar. this wheel will have the current letter line.

I'm not quite sure if I understood your request correctly. The current letter to be selected is "highlighted" (the letter which can be selected is bold and displayed in a square on the keyboard)

The problem is that often the input finger hides the letters on the diagonal.
Can we buy a clear stylus?
This suggestion ( if I understand it correctly ) is to also put a preview of the letter in the same position where it is about to permanently appear.
It is where the eye naturally falls.


Querying mechanism issue

Hi, I issued #2153 previously, Thank you very much for fixing this bug in version 7.0.2! But I find there is a problem remaining.
After minimising a window,  do not focus on any others, command yabai -m query --windows --window results "could not retrieve window details." while the command yabai -m query --windows --space shows the minimised window has property has-focused: true. I think these two outputs might be conflicted, because the Wiki shows the command yabai -m query --windows --window queries "focused/selected window", but it can't query the focused minimized window here.

Same as https://github.com/koekeishiya/yabai/issues/1985


Add option for JHOVE to return OK even with WB error

Due to the known limitation of JHOVE, validation fails if the white balance has a value outside the expected. Will add an option to check the messages and ignore the WB and set it as passed unless it finds other issues.

Added in 719c22ce01aec3b6fad4528118e238e52c96ebc3


Move our images and videos to docs branch

Is your enhancement related to a problem? Please describe
We should place all our videos / pictures into a branch rather than having to rely on storing it on github cache / imgur / etc.
Describe the solution you'd like
Move the images and videos we have to a separate branch.
Describe alternatives you've considered
No response
Additional context
No response

I still believe it's not part of this repository (branch would still be cloned by default) even if it would be convenient
could be an additional repo ?

@benoitf that would be really beneficial as we do the same and rely on github cache for videos / pictures.
could you create a repo that is just generic "podman desktop assets" or something we can throw our videos / pictures in?

PR here: https://github.com/containers/podman-desktop-media/pull/1


Having some problem while testing

I've followed the step in https://asciinema.org/a/302094,
but after I create the sharePod and input kubectl get sharepod pod1 -o yaml | egrep -m2 'GPUID|nodeName' ,
it didn't show anything. Why?
I don't know if it is because of my cuda version is 11.2 or what.
BTW, do I need to run the makefile? I'm not sure if that is necessary.

Hi,
Please make sure that the following settings are completed:

cuda works

nvcc
nvidia-smi

docker configured with nvidia as the default runtime

Runtimes: nvidia runc
Default Runtime: nvidia

nvidia device  plugin is running
see more:   https://github.com/NVIDIA/k8s-device-plugin

After completing the above work, you can install KubeShare
Please also confirm that the status of KubeShare's Pod is running.

kubeshare-scheduler
kubeshare-device-manager
 kubeshare-node-daemon

BTW, I don't think it is caused by the cuda version 11.2 because I try to build on cuda 11.2 and it works.
You not need to run the makefile unless you modify the code.
If the above installation is successful, please provide log if there are any problems.

Sorry, I've checked those things you mentioned above but the result is still nothing.

cuda works
nvcc:

root@k8s-node1:/home/ms0244456# nvcc -V
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2017 NVIDIA Corporation
Built on Fri_Nov__3_21:07:56_CDT_2017
Cuda compilation tools, release 9.1, V9.1.85

nvidia-smi:
root@k8s-node1:/home/ms0244456# nvidia-smi
Wed Apr 28 04:43:38 2021
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 460.73.01    Driver Version: 460.73.01    CUDA Version: 11.2     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  GeForce GTX 950     Off  | 00000000:01:00.0  On |                  N/A |
| 38%   30C    P8     7W /  90W |    131MiB /  1993MiB |      1%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A      1794      G   /usr/lib/xorg/Xorg                100MiB |
|    0   N/A  N/A      2216      G   /usr/bin/gnome-shell               25MiB |
+-----------------------------------------------------------------------------+

docker configured with nvidia as the default runtime
Those two are also checked through docker info

 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux nvidia runc
 Default Runtime: nvidia

nvidia device plugin
I use kubectl describe to check if my k8s cluster has get the gpu from the worker node

Capacity:
  cpu:                12
  ephemeral-storage:  239314556Ki
  hugepages-1Gi:      0
  hugepages-2Mi:      0
  memory:             8027428Ki
  nvidia.com/gpu:     1
  pods:               110
Allocatable:
  cpu:                12
  ephemeral-storage:<PHONE_NUMBER>45
  hugepages-1Gi:      0
  hugepages-2Mi:      0
  memory:             7925028Ki
  nvidia.com/gpu:     1
  pods:               110

KubeShare's pods

root@k8s-master:/home/k8s-master/demo# kubectl get pods -n kube-system
NAME                                   READY   STATUS    RESTARTS   AGE
coredns-f9fd979d6-6cgct                1/1     Running   16         196d
coredns-f9fd979d6-qsbr8                1/1     Running   16         196d
etcd-k8s-master                        1/1     Running   12         196d
kube-apiserver-k8s-master              1/1     Running   8          160d
kube-controller-manager-k8s-master     1/1     Running   10         160d
kube-flannel-ds-lfn7l                  1/1     Running   10         7d
kube-flannel-ds-t7gch                  1/1     Running   0          56d
kube-flannel-ds-vhqmx                  1/1     Running   14         196d
kube-flannel-ds-wt9q9                  1/1     Running   21         196d
kube-proxy-6mpl5                       1/1     Running   0          56d
kube-proxy-czvgt                       1/1     Running   10         7d
kube-proxy-n8sb7                       1/1     Running   12         196d
kube-proxy-ncqm2                       1/1     Running   21         196d
kube-scheduler-k8s-master              1/1     Running   15         193d
kubeshare-device-manager               1/1     Running   0          165m
kubeshare-node-daemon-bbjbm            2/2     Running   0          165m
kubeshare-node-daemon-mtdx2            2/2     Running   1          165m
kubeshare-node-daemon-x8r4t            2/2     Running   0          165m
kubeshare-node-daemon-z4l7d            2/2     Running   0          165m
kubeshare-scheduler                    1/1     Running   0          165m
nvidia-device-plugin-daemonset-pw8hh   1/1     Running   1          3d11h
nvidia-device-plugin-daemonset-wgv44   1/1     Running   0          3d11h
nvidia-device-plugin-daemonset-wtp2b   1/1     Running   0          3d11h

My sharepod1 & 2
apiVersion: kubeshare.nthu/v1
kind: SharePod
metadata:
  name: pod1
  annotations:
    "kubeshare/gpu_request": "0.4"
    "kubeshare/gpu_limit": "1.0"
spec:
  terminationGracePeriodSeconds: 0
  containers:
  - name: tf
    image: tensorflow/tensorflow:1.15.2-gpu-py3
    command: ["sh", "-c", "curl -s https://lsalab.cs.nthu.edu.tw/~ericyeh/KubeShare/demo/mnist.py | python3 -"]
  restartPolicy: OnFailure
-----------------------------------------------------------------------------------------------
apiVersion: kubeshare.nthu/v1
kind: SharePod
metadata:
  name: pod2
  annotations:
    "kubeshare/gpu_request": "0.6"
    "kubeshare/gpu_limit": "1.0"
spec:
  terminationGracePeriodSeconds: 0
  containers:
  - name: tf
    image: tensorflow/tensorflow:1.15.2-gpu-py3
    command: ["sh", "-c", "curl -s https://lsalab.cs.nthu.edu.tw/~ericyeh/KubeShare/demo/mnist.py | python3 -"]
  restartPolicy: OnFailure

Test command:
root@k8s-master:/home/k8s-master/demo# kubectl get sharepod
NAME   AGE
pod1   36m
pod2   36m
root@k8s-master:/home/k8s-master/demo# kubectl get pod
NAME                       READY   STATUS    RESTARTS   AGE
gpu-test-7d87449d9-dvsvj   1/1     Running   0          41d
root@k8s-master:/home/k8s-master/demo# kubectl get sharepod pod1 -o yaml | egrep -m2 'GPUID|nodeName'
root@k8s-master:/home/k8s-master/demo#
root@k8s-master:/home/k8s-master/demo# kubectl get sharepod pod2 -o yaml | egrep -m2 'GPUID|nodeName'
root@k8s-master:/home/k8s-master/demo#

My docker version: 20.10.6
And I want to ask if I can add nodeSelector in sharepod.yaml or not?

Hi @benesse1899

docker configured with nvidia as the default runtime
Actually, I’m not sure if there are many runtimes in the environment that can be detected correctly.
You can check the working status of the nvidia device plugin by submitting the gpu pod

apiVersion: v1
kind: Pod
metadata:
  name: gpu-pod
spec:
  containers:
    - name: cuda-container
      image: nvcr.io/nvidia/cuda:9.0-devel
      resources:
        limits:
          nvidia.com/gpu: 2 # requesting 2 GPUs
    - name: digits-container
      image: nvcr.io/nvidia/digits:20.12-tensorflow-py3
      resources:
        limits:
          nvidia.com/gpu: 2 # requesting 2 GPUs

Also we provide you with our settings
cat /etc/docker/daemon.json

{
    "runtimes": {
        "nvidia": {
            "path": "/usr/bin/nvidia-container-runtime",
            "runtimeArgs": []
        }
    },
    "default-runtime": "nvidia"
}

When applying sharepod, please provide some logs about KubeShare pod
kubectl logs -n kube-system kubeshare-node-daemon
kubectl logs -n kube-system kubeshare-device-manager
kubectl logs -n kube-system kubeshare-scheduler

current version is not support nodeSelector

Hi @StarCoral
The setting of
cat /etc/docker/daemon.json

I've done already, but I forgot to show in my previous reply, sorry for that.
And because I only have one gpu in each node(I have two nodes, and my master node doesn't have gpu), so I use this pod to check
apiVersion: v1
kind: Pod
metadata:
  name: gpu-pod
spec:
  containers:
    - name: cuda-container
      image: nvidia/cuda:11.0-devel
      resources:
        limits:
          nvidia.com/gpu: 1
      command: ["/bin/sh","-c","--"]
      args: ["while true; do sleep 30; done;"]
  nodeSelector:
    accelerator: nvidia-gtx-950

Then I go into the pod and write nvidia-smi
root@gpu-pod:/# nvidia-smi
Mon May  3 09:37:41 2021
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 460.73.01    Driver Version: 460.73.01    CUDA Version: 11.2     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  GeForce GTX 950     Off  | 00000000:01:00.0  On |                  N/A |
| 38%   30C    P8     6W /  90W |    127MiB /  1993MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
+-----------------------------------------------------------------------------+

And the log of kubeshare-device-manager
I0503 09:59:58.803297       1 reflector.go:418] pkg/mod/k8s.io/client-go@v0.17.2/tools/cache/reflector.go:105: Watch close - *v1.Pod total 15 items received
I0503 10:00:00.263311       1 config.go:188] Receive heartbeat from node: k8s-node2
I0503 10:00:08.498214       1 config.go:188] Receive heartbeat from node: k8s-node1
I0503 10:00:12.644666       1 reflector.go:268] pkg/mod/k8s.io/client-go@v0.17.2/tools/cache/reflector.go:105: forcing resync
E0503 10:00:12.644818       1 controller.go:259] SharePod 'default/pod1' must be scheduled! Spec.NodeName is empty.
I0503 10:00:12.644847       1 controller.go:228] Successfully synced 'default/pod1'
E0503 10:00:12.644872       1 controller.go:259] SharePod 'default/pod2' must be scheduled! Spec.NodeName is empty.
I0503 10:00:12.646050       1 controller.go:228] Successfully synced 'default/pod2'
I0503 10:00:13.737963       1 reflector.go:268] pkg/mod/k8s.io/client-go@v0.17.2/tools/cache/reflector.go:105: forcing resync
I0503 10:00:15.263033       1 config.go:188] Receive heartbeat from node: k8s-node2
I0503 10:00:23.497876       1 config.go:188] Receive heartbeat from node: k8s-node1
I0503 10:00:30.262750       1 config.go:188] Receive heartbeat from node: k8s-node2
I0503 10:00:38.497394       1 config.go:188] Receive heartbeat from node: k8s-node1
I0503 10:00:42.645114       1 reflector.go:268] pkg/mod/k8s.io/client-go@v0.17.2/tools/cache/reflector.go:105: forcing resync
E0503 10:00:42.645331       1 controller.go:259] SharePod 'default/pod1' must be scheduled! Spec.NodeName is empty.
I0503 10:00:42.645370       1 controller.go:228] Successfully synced 'default/pod1'
E0503 10:00:42.645397       1 controller.go:259] SharePod 'default/pod2' must be scheduled! Spec.NodeName is empty.

I think this is the reason why the Pod cannot be created.

Hi @StarCoral ,
Well, I've tried add the kubeshare/gpu_mem back but still not working.
The value I set is 500000000.

According to the  log of kubeshare-device-manager , the kubeshare-scheduler didn't find the node to assign pod.
I tried the yaml file you provided and it can work normally in our environment.
I may need more error message to be able to help you.

Hi @StarCoral,
I met almost the same problem when I tried to deploy sharepod with YAML file in the doc/yaml/ folder
the log of kubeshare-device-manager showed that it didn't find the node to assign pod.
I1004 05:27:55.545279       1 reflector.go:268] pkg/mod/k8s.io/client-go@v0.17.2/tools/cache/reflector.go:105: forcing resync
E1004 05:27:55.545515       1 controller.go:259] SharePod 'default/pod1' must be scheduled! Spec.NodeName is empty.
I1004 05:27:55.545549       1 controller.go:228] Successfully synced 'default/pod1'

However, I found error messages in the Kubelet log after I deployed Kubeshare
Oct 04 13:21:51 master-OptiPlex-7050 kubelet[4346]: 2022-10-04 13:21:51.826 [INFO][17519] k8s.go 417: Wrote updated endpoint to datastore ContainerID="cfedeb9ce5aa8dc8e7e7633ac099dd24cb8dd045f289e9ce37844bbcb680f406" Namespace="kube-system" Pod="kubeshare-scheduler" WorkloadEndpoint="master--optiplex--7050-k8s-kubeshare--scheduler-eth0"
Oct 04 13:21:54 master-OptiPlex-7050 kubelet[4346]: E1004 13:21:54.098101    4346 remote_runtime.go:295] ContainerStatus "68b822e852c01812ead249fae6d0dd4efb601866441f3274587d710f456d5999" from runtime service failed: rpc error: code = Unknown desc = Error: No such container: 68b822e852c01812ead249fae6d0dd4efb601866441f3274587d710f456d5999
Oct 04 13:21:54 master-OptiPlex-7050 kubelet[4346]: E1004 13:21:54.098118    4346 kuberuntime_manager.go:952] getPodContainerStatuses for pod "kubeshare-scheduler_kube-system(6c4e994a-6cc6-4e59-abb7-2bbdc255a3e9)" failed: rpc error: code = Unknown desc = Error: No such container: 68b822e852c01812ead249fae6d0dd4efb601866441f3274587d710f456d5999
Oct 04 13:21:55 master-OptiPlex-7050 kubelet[4346]: W1004 13:21:55.654111    4346 container.go:412] Failed to create summary reader for "/kubepods/besteffort/pod94d51d32-dfca-461b-a15c-f3dde9aae779/9d98c32a777265b61be37b8b310c7041229fef235bd3bec1f087672800b8e8d3": none of the resources are being tracked.

But kubectl get pod -n kube-system looks good
coredns-7ff77c879f-htmhw                       1/1     Running   9          12d
coredns-7ff77c879f-qf5kt                       1/1     Running   9          12d
etcd-master-optiplex-7050                      1/1     Running   9          12d
kube-apiserver-master-optiplex-7050            1/1     Running   9          12d
kube-controller-manager-master-optiplex-7050   1/1     Running   9          12d
kube-proxy-547ps                               1/1     Running   0          6d1h
kube-proxy-54gbr                               1/1     Running   9          12d
kube-proxy-j784s                               1/1     Running   0          3h7m
kube-scheduler-master-optiplex-7050            1/1     Running   9          12d
kubeshare-device-manager                       1/1     Running   0          46m
kubeshare-node-daemon-6f7c7                    2/2     Running   1          46m
kubeshare-node-daemon-qrrlc                    2/2     Running   0          46m
kubeshare-node-daemon-rq272                    2/2     Running   0          46m
kubeshare-scheduler                            1/1     Running   0          46m

Maybe this is the reason, but I can't solve it.
Hope you are still paying attention to this issue and I can provide more information.

Hi @y-ykcir, the error SharePod 'default/pod1' must be scheduled! Spec.NodeName is empty. may be a temparory error and it will be requeued to be handle again, which you can see Successfully synced 'default/pod1' after the error.
Can you see the pod running normally in the default namespace?

Hi @justin0u0, I can't see the pod running normally in the default namespace. However, It seemed to work after I re-installed Kubernetes and Kubeshare.
But I'm still stuck in issue https://github.com/NTHU-LSALAB/KubeShare/issues/19, could you help me answer it?


Formatter indentation bug

Extracted from #5146.
[1, 2, 3]
  .each do |n|
    n
  end

Gets formatted to:
[1, 2, 3]
  .each do |n|
  n
end

/cc @MakeNowJust

Not a bug. The expression starts at indent 0 and the block is at indent 2. Look:
# This is OK
[1, 2, 3].each do |n|
  n
end

# Now I just put a newline after `]`, still OK
[1, 2, 3]
  .each do |n|
  n
end

Maybe it's not a bug but what about a feature request?
I think this example looks bad. It would make more sense to increase the indent of the next line after a do and close the block at the same indent as the line with do regardless of where the expression started.

Okay, then we have this:
[1, 2, 3].map { |x| x - 1 }
         .select { |x| x > 1 }
         .each do |x|
  puts 1
end

Do we want it to format like this:
[1, 2, 3].map { |x| x - 1 }
         .select { |x| x > 1 }
         .each do |x|
            puts 1
end

Or maybe it's already wrong that . is indent too far, so maybe it should be like this:
[1, 2, 3].map { |x| x - 1 }
  .select { |x| x > 1 }
  .each do |x|
     puts 1
end

Or maybe like this:
[1, 2, 3].map { |x| x - 1 }
         .select { |x| x > 1 }
         .each do |x|
            puts 1
         end

In the end, it boils down to user preference, something that the formatter doesn't allow.
But yes, we can continue discussing what's the best formatting here.

For my taste end should be on the same line as starting do, in the same vein as in other places.

@Sija uhh, you mean?
foo do |x|
      bar
    end

I think thats a terrible idea

I think he means the end should have the same indent as the line including do. And the lines in between should be increased indent by one.
[1, 2, 3]
  .each do |n|
    n
  end

foo do |x|
  bar
end

[1, 2, 3].map { |x| x - 1 }
         .select { |x| x > 1 }
         .each do |x|
            puts 1
         end

I'd say this is the most logical.

@straight-shoota yep, u get my drift.

All cases work fine!

I'll create a new pull request.

[1, 2, 3].map { |x| x - 1 }
         .select { |x| x > 1 }
         .each do |x|
            puts 1
         end

The problem with the above is that a small change on position of the first call will cause a ripple effect on all the lines of the block:
[1, 2, 3, 4, 5].map { |x| x - 1 }
               .select { |x| x > 1 }
               .each do |x|
                  puts 1
               end

Adding noise to the diffs. :confused:

You can just ignore whitespace in the diff... And this style with high indents should certainly not be promoted.
You can write it better this way:
numbers = [1, 2, 3, 4, 5]
numbers = .map { |x| x - 1 }
          .select { |x| x > 1 }
          .each do |x|
            puts 1
          end

A style that I've been using recently is to double-indent the lines before the block body starts, but keep everything else the same:
[1, 2, 3, 4, 5]
    .map { |x| x - 1 }
    .select { |x| x > 1 }
    .each do |x|
  puts 1
end

I like this format because it keeps the body from being arbitrarily lengthened by leading whitespaced, and (imo) makes it more clear where the method chaining ends and the block body actually starts.
Particularly, I think this looks better for nested blocks:
[1, 2, 3, 4, 5]
    .map { |x| x - 1 }
    .select { |x| x > 1 }
    .each do |x|
  puts 1

  [1, 2, 3, 4, 5]
      .map { |x| x - 1 }
      .select { |x| x > 1 }
      .each do |x|
    puts 1
  end
end

Let's call  this closed via #5234, everything else seems too opinionated.


Add option to generate subcommand for specifying which access levels are included

My original motivation for swift-doc was to generate documentation for libraries. However, as the tool gains wider adoption, teams will likely want to use it internally for their own apps. The major difference between libraries and apps is that apps are typically much less concerned about ACL (if all of your code is in a single app target, everything "just works").
Rather than force teams to change their code in a way that would otherwise provide no immediate benefit (i.e. sprinkling public throughout their code base), I think it would make sense to provide an option for internal declarations to be included in the generated output.
As far as how this should work:

The current behavior of only looking for public or open declarations should probably continue to be the default.
To help folks who might be confused about nothing happening when they run swift doc generate (#70), we should communicate something like "No public declarations found, set the (option) flag to...).
To accommodate future distinctions, this option should probably take an enumerated value rather than a Boolean. So --minimum-access-level internal instead of --include-internal-declarations.
And, of course, this should be documented. I think a "Getting Started" guide should be considered a P1 for our 1.0.0 release. (#73)

Hi 👋
Has there been any movement on this? 😃
I see there's an open PR with some conflicts... Would be really helpful 😊


New API for slot filling

Which allows slot-filling anything, not just input parameters and filters. Most importantly, it allows slot filling inside arrays, and slot filling of timers.

Pull Request Test Coverage Report for Build 504

277 of 340 (81.47%)  changed or added relevant lines in 11 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.2%) to 82.082%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/describe.js
2
3
66.67%

lib/runtime/format_objects.js
9
10
90.0%

lib/i18n.js
13
17
76.47%

lib/typecheck.js
14
18
77.78%

lib/ast/program.js
31
36
86.11%

lib/ast/api.js
113
128
88.28%

lib/ast/slots.js
90
123
73.17%

Files with Coverage Reduction
New Missed Lines
%

lib/typecheck.js
1
87.78%

lib/format_utils.js
1
90.0%

Totals

Change from base Build 503:
-0.2%

Covered Lines:
6135

Relevant Lines:
7270

💛  - Coveralls


Broken Link

Submitting this per conversation with Aaron at MMSMOA.  This link no longer works:  https://docs.microsoft.com/en-us/powershell/module/configurationmanager/about_configurationmanager_cmdlets?view=sccm-ps

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

ID: 5e2f0b6d-c7ca-cb30-3de9-e50eae55c24d
Version Independent ID: 01e64fb6-4385-6864-7430-38ac98632aaf
Content: ConfigurationManager
Content Source: sccm-ps/ConfigurationManager/ConfigurationManager.md
Service: powershell

Thanks @monkeyskullfire for reminding me 😄
I looked into it, I deleted the file a few weeks ago. It was poorly formatted and basically a duplicate of the overview article. At the time I forgot to create a redirect, but I'm adding one now. It should go live later this afternoon. I'll keep this open until I can confirm (in part to make sure I got the redirect syntax correct!)

Redirect is working. Your bookmark should still work, or you can update it to the new target: https://docs.microsoft.com/powershell/sccm/overview?view=sccm-ps


The model file could not be found

When I try to tun python -u demo/demo_mug.py, I encountered the following error:
no checkpoint found at '/data/hfn5052/text2motion/videoflowdiff_mug/snapshots-j-sl-random-of-tr-rmm/flowdiff_0005_S111600.pth'
I notice that there are two model paths in the code, RESTORE_FROM and AE_RESTORE_FROM. I gave the path about the pre-training model on the MUG dataset to AE_RESTORE_FROM, but what should the RESTORE_FROM value be?
Also want to ask, code about when will be updated a version? Now many variables in this version are written to the code, to modify and run a lot of inconvenience, if can be integrated into the YAML configuration file, I think it would be a great benefit for the rest of the community to follow your work.
Finally, thank you for this work, gave us a lot of inspiring ideas, also hope to see this project can get more attention.

Hi, @zhtjtcz, thanks a lot for your interest and suggestion for our work! Sorry for the unclear variable names. RESTORE_FROM  should be the path to the pre-trained DM model and AE_RESTORE_FROM should be the path to the pre-trained LFAE model. You can download them from the table in our Readme and set the paths to downloaded models.
The YAML configuration is more common, but I personally prefer to put all the variables at the top of the main program to ease the debugging. But thanks again for your suggestion! I can try so in the future. Please feel free to let me know if you have any questions or comments!


[19.03 backport] Fix error handling for bind mount spec parser.

backport of https://github.com/moby/moby/pull/39251 for 19.03
fixes https://github.com/docker/for-linux/issues/674 for 19.03
Errors were being ignored and always telling the user that the path
doesn't exist even if it was some other problem, such as a permission
error.

ping @cpuguy83 @kolyshkin ptal

@kolyshkin Can you give your LGTM on moby#39251 ?


[Backend Configuration Ia] Pydantic models for communicating backend-independent dataset information

replaces #549
~250 new lines of source code
~600 lines of tests
Introduces Pydantic models for modelling fields of in-memory neurodata objects that are destined to become Datasets (of h5py or zarr variety) in a way that is agnostic to which backend will ultimately be chosen
Pydantic is used here for many key benefits, one the best of which is automatic JSON schema generation for handling this information to generate forms for the NWB GUIDE
Instantaneous and thorough validation of inputs is also a big plus when there are this many dictionary-like values being passed around - many of the problems that could result from bad inputs to fields like chunk shapes would only be caught at or near the final step of writing, which in this case could be well after specification by the user
In the long-term, using autodoc-pydantic could also allow us to automatically generate formatted docstrings, sphinx API docs, and Entity-Resource graphs (similar to UML) all automatically while still preserving the ability for developers to quickly read and parse the signatures of classes and methods
The design of inputs to the dataset models is also to be friendly and flexible as possible to users of the API; for those using YAML feature or simple string specification, we automatically fetch and instantiate any complicated hdf5plugin/numcodec objects from the string inputs; and for those who already know how to instantiate such items, they may pass them directly

Following the standard of that makes sense. Would it be a good idea to generate a separate instance of object_id each time?

I actually kind of prefer having it be static, such that if you ever see that object ID in practice, you know there is a near certainty that the object was generated by the mock instead of an actual neurodata object

@h-mayorquin I made a few final changes to the string printout and added automatic parsing of the dataset name
Also added a bunch more tests and parameterized a lot of the previous ones to save space

If that feature were available, would you be OK with the unification?

Yeah, that would be cool

Although, to be aware, at that point you would loose the hashability feature, which relies on the entire object being immutable. Earlier designs of the later PRs utilized this approach until the location parsing became so reliable that it wasn't really needed any more... might still be nice to have? The v2 jump isn't happening any time soon though so maybe we'll cross that bridge when we get there


Repeated rules in SPI/CGPA calculator

Describe the bug
Repeated rules in SPI/CGPA calculator
Screenshots

Please assign me this issue

Go ahead
Deadline: 22 April 2021


Fix: Crashes after entering additional questions

Fixes #754.
Cause:
From a recent Langchain update, it seems the AIMessage object has a much stricter schema which only allows is_chunk attributes to have a False value. However, in gpt_engineer, the deserialization of clarify logs implicitly sets is_chunk to True.
Proposed fixes:

Either go to Langchain (or Pydantic which they use internally for model validation of their types) and loosen their requirements for an AIMessage object model. They may or may not agree with my proposal.
Make it explicit that when message objects are deserialized from the  JSON string, that their is_chunk attribute can never be True.

Containment/Fix:
I go with Fix 2.
This commit deserializes and stores an intermediate list, from which we explicitly set all is_chunk values to False. Since the Langchain messages_from_dict(..) method anyways expect a Message object with an is_chunk property of False, we don't have the effect of hotfixing this property, but rather add an additional check to make sure Messages have valid properties (like this is_chunk property for e.g.).

Thanks for picking this up. Just answer my minor question and I will merge.

Thanks for picking this up. Just answer my minor question and I will merge.

Sorry, I missed your question?

Is the call on line 349 really necessary? Can't you just directly put modified_data in the return and omit the json.loads statement on the following line?
It looks like we are serializing and deserializing on two consecutive lines.

Thanks, great that you dug out the error.

Done ✅ I would also recommend to put this in a minor release for its PyPi package soon (I'm not sure what your release cycles are like), because this breaks the application whenever the user is asked for clarification. Even if the user skips.

Thanks, great that you dug out the error.

No problem, glad I could help 😄

gpt-engineer            0.0.9
i have this problem tooo
in which version this is solved?

So, it is solved on commit https://github.com/AntonOsika/gpt-engineer/commit/d37feec9bb29f1c81ceead9bea584d9c9e1f41d2
We currently do not update the version in each commit, so many commits are called 0.0.9. If you refer to the version on pypi, this bug still persists.


tweak CI

@homunkulus r+

:pushpin: Commit ff55630 has been approved by japaric

:hourglass: Testing commit ff55630 with merge ff55630...

:broken_heart: Test failed - status-travis

:pushpin: Commit 494736b has been approved by japaric

@homunkulus r+

:hourglass: Testing commit 494736b with merge 494736b...

:sunny: Test successful - status-travis
Approved by: japaric
Pushing 494736b2fb2597843b25043078a8fa21868219f0 to master...


Tools: extend the information gathered by image-info

image-info now inspects multiple paths (such as /etc, /usr/lib, /usr/local/lib) when gathering configuration of specific parts of the system. Notable changes are:

read modprobe configs from multiple paths
read dracut configs from multiple paths
read systemd-logind configs from multiple paths
read cloud-init configs from multiple paths
read systemd service unit drop-ins from multiple paths
read tmpfiles.d config files from multiple paths
read security limits config files from multiple paths
read sysctl.d config files from multiple paths
read content of /etc/resolv.conf
check not installed documentation as part of rpm-verify
sort partitions list in the report

All image test cases have been regenerated as part of this PR.
This pull request includes:

[ ] adequate testing for the new functionality or fixed issue
[ ] adequate documentation informing people about the change such as

[ ] create a file in news/unreleased directory if this change should be mentioned in the release news
[ ] submit a PR for the guides repository if this PR changed any behavior described there: https://www.osbuild.org/guides/

Hmm, I wonder if we should ship all fixes for 8.6 and 9.0b first and then merge this... I don't want to backport this, it isn't entirely necessary... Do you have any thoughts?

8.5 and 9.0b, right?

Yep, sorry, edited.

Yes, lets wait for #1798 and #1759 to land first... Hopefully soon... 🙂

Note for myself: Update 8.4 repos to the latest RPMrepo snapshot with released content and regenerate 8.4...

Resolved all conflicts in rhel-90 edge image test cases. Ready for review...

sorry, had to rebase due to CI fixes.... hopefully the last time 😄

Amazing work! Thanks!


More read interface IList.Count once rather than per iteration + miscellany

Inspired by #9962 I had a look through some of the less hot-path areas to see if there were anymore IList.Count for loops that could benefit from the same change. There's also some for ReadOnlyCollection<T> as looking at the code that just calls through to IList.Count anyway, so would benefit the same way(?).
Use nameof() on an enum value instead of ToString() to make a compile-time constant.
Initialise a dictionary with a fixed number of members with a capacity equal to the number of members.
Override DisposeAsync on FileBufferingReadStream to call DisposeAsync() on the wrapped Stream.
Use FileBufferingReadStream.DisposeAsync() in a number of input formatters.
Use GetValueOrDefault() on a long? instead of calling HasValue once and Value up to three times in a number of input formatters.

I wasn't sure exactly what tool was used in #9962 to generate the call counts, so I haven't crunched the before and after numbers.

@aspnet-hello triage https://dev.azure.com/dnceng/public/_build/results?buildId=226845

@davidfowl You added VerifyCountersFireWithCorrectValues, I'll disable if this continues to fail.
@halter73 also a reconnect test failure: https://dev.azure.com/dnceng/public/_build/results?buildId=226845&view=ms.vss-test-web.build-test-results-tab&runId=5614518&resultId=133322&paneView=debug

This comment was made automatically. If there is a problem contact<EMAIL_ADDRESS>I've triaged the above build. I've created/commented on the following issue(s)
https://github.com/aspnet/AspNetCore-Internal/issues/2293
https://github.com/aspnet/AspNetCore-Internal/issues/1979


When I try to install elasticsearch ,I get in trouble.What should I do?

yjy@ddh:/opt/elasticsearch-6.2.3/bin$ ./elasticsearch
Exception in thread "main" java.nio.file.AccessDeniedException: /opt/elasticsearch-6.2.3/config/jvm.options
at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)
at java.nio.file.Files.newByteChannel(Files.java:361)
at java.nio.file.Files.newByteChannel(Files.java:407)
at java.nio.file.spi.FileSystemProvider.newInputStream(FileSystemProvider.java:384)
at java.nio.file.Files.newInputStream(Files.java:152)
at org.elasticsearch.tools.launchers.JvmOptionsParser.main(JvmOptionsParser.java:58)

Please follow the template that is preloaded when you open the issue — it makes it much easier for us to help you :)
Are you even using our Docker containers, because I cannot see anything around that in your problem? Generally this looks more like a question for https://discuss.elastic.co. Please start a discussion there and add more information: What system are you using, which package did you install,..


Proposal:  Minimum uptime

I've been experimenting with the Zero LIPO and clean-shutdown and run into the following scenario:
Sometimes I want to power my Pi Zero through USB power, not the LIPO connector.  The Zero LIPO supports this just fine, but in conjunction with clean-shutdown yields a problem, since without the battery connected the low-battery GPIO fires, and clean-shutdown almost immediately turns the system back off.
My proposed solution is to add a system uptime check to clean-shutdown that will cause it not to act until the system has been up for less than min_uptime seconds (a new config parameter).  Once min_uptime seconds elapse, the daemon may shut the system down, but this gives the user a grace period to log in and disable the service if we're actually running from USB.
Another option would be to permanently disable clean-shutdown (until restarted) if the very first poll of the GPIO indicates low battery (on the assumption we're actually not using a battery).  This would be really convenient when running from USB and avoid a new config parameter, but will behave badly if we're actually booting the system off a low battery.
I'd be happy to submit a pull request if this feature would be welcome.

These are some good suggestions! I'll see what we can do. I'll summon @RogueM since this script is very much his baby.

from the README at the top of this repo:

you may add the following to your /boot/config.txt file from another computer:
disable_cleanshutd=1

incidentally, the shutdown_delay should already be 5 minutes? it's not exactly what you are asking, but as default for the Zero LIPO, at least if installed by passing the product parameter, I think it does end up having the same effect?

Huh.  Good point about shutdown_delay -- I agree it should be functionally equivalent to my suggestion.  Silly of me not to have considered it.  I need to go back and figure out why my device was shutting down almost instantly, since I didn't intentionally change that parameter.
Closing this issue since equivalent functionality should already exist.


Allows passing through custom transforms

Wasn't sure which branch to base off of as it seems release/2.0 as diverged from master quite a bit.
As the title states, simply pipes through a customer transformers option from creation to the language service.

Build break seems unrelated.


Just a little Feedback on the mod.

There's a little problem with the precision of the m1 shot, that sometimes it doesn't go where you are aiming , and the follow-up for the dash atack sometimes wont give any stacks.
But away from this little things, the mod is great, nice job.

Thanks for the feedback! I would love to push an update immediately, but I am not my workplace currently. However, I will ensure that your feedback is added to my next patch.


feat: warn users (if verbose) that certain programs don't exist

add 3 new functions

check-if-program-exists: check if a program exists and is executable by directly invoking the program and checking the result code

warn-if-program-doesnt-exist: added to keep consistency between warning messages

warn-if-missing-required-programs: used as a one stop shop for warning before required programs are ran (e.g install and version check)

Fixes #69

This is perfect.  Thank you!


Support for withVolumesFrom from dockerjava

Hi,
is mounting volumes from another (data) container is supported?
Dockerjava supports this by using withVolumesFrom.
Regards,
Peter

I've added it on a local branch.
I'll create a PR for this.
Thanks,
Peter

Peter
Thanks, that's not currently supported, so the PR would be good. Thank you!
Richard
On Fri, 25 Nov 2016 at 11:49 Peter<EMAIL_ADDRESS>wrote:

I've added it on a local branch.
I'll create a PR for this.
Thanks,
Peter
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/testcontainers/testcontainers-java/issues/244#issuecomment-262940466,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIET5eZ66UClpMTd2iBI7QR831ghJgFks5rBss7gaJpZM4K7ez4
.

Hey @peterbollen,
any luck?

@bsideup Lost track of this. I'll create the PR in a bit.

Fixed in #289


If TOML path is not found, try prepending pkgdir to the path

This is needed to fix #2167, where configurations in config that used a TOML file could only be run from pkgdir(CA).
Content

prepend pkgdir(CA) to the TOML path if the given TOML path does not point to a file.
Remove support for multiple TOML files. I don't think that this is useful, and if anything could cause issues.

What was the point of having lists in the toml entry?

What was the point of having lists in the toml entry?

@Sbozzolo It enabled multiple parameter files to be passed in. I thought that this flexibility might be useful, but it has not been. Since it is not used and could cause issues with multiple parameter sources, it seems better to remove for now.

What was the point of having lists in the toml entry?

@Sbozzolo It enabled multiple parameter files to be passed in. I thought that this flexibility might be useful, but it has not been. Since it is not used and could cause issues with multiple parameter sources, it seems better to remove for now.

Thanks! Supporting a list will aksi introduce the problem of what to do when there's a conflict. So, I guess we can postpone supporting this until we find that we need to.

What was the point of having lists in the toml entry?

@Sbozzolo It enabled multiple parameter files to be passed in. I thought that this flexibility might be useful, but it has not been. Since it is not used and could cause issues with multiple parameter sources, it seems better to remove for now.

Thanks! Supporting a list will aksi introduce the problem of what to do when there's a conflict. So, I guess we can postpone supporting this until we find that we need to.

There is already defined functionality in CLIMAParameters.merge_toml_files(), which is to warn the user about the overrides and merge parameters with the same priority as merge (rightmost argument takes first priority). See here


images are inaccessible from amazon after 5-7 days

we agreed to store screenshots for 10 years if I remember correctly.
Please investigate what happen with this functionality

to make them accessible for upto 10 years we have to setup cloudfront integration.
so closing as not a bug.


memory error for big big trees

Hi Terence,
first of all, thank you for this amazing library (and for the great blog articles you put out there).
I'm writing here because I experience an issue with a tree that has a big depth.
Would it be possible to somehow tell dtreeviz that we want to plot only the first part of such a tree (say, the first four splits) ? That would help avoid memory errors when the tree is too big and the structure gets out of hand.
Thank you for your time

I've added a parameter 'depth_range_to_display', which can take a range of depth levels to be displayed. Like in the picture bellow.

@parrt what do you think ?

Hi,
great job ! Yes I still have access to the data. I'll try this feat and let you know how it goes.
thanks a lot!

@benjamin-du this new functionality is not yet released. I will make a PR soon and if everything is ok, @parrt will make a new release


Fix wrong expansion for masked vmsge{u}.vx with temp register

vmsge{u}.vx vd, va, x, v0.t, vt can expand into
vmslt{u}.vx vt, va, x;  vmandnot.mm vd, vd, vt only if vd == v0

Add expansion for vmsge{u}.vx vd, va, x, v0.t, vt for any vd.

 vmslt{u}.vx vt, va, x
 vmandnot.mm vt, v0, vt
 vmandnot.mm vd, v0, vd
 vmor.mm vd, vt, vd

Derivation process for the instruction sequence:

   vd[i] = (mask[i] && va[i] >= x) || (!mask[i] && vd[i])
   =>
   vt[i] = (va[i] < x)
   vd[i] = (mask[i] && !vt[i]) || (!mask[i] && vd[i])
   =>
   vt[i] = (va[i] < x)
   vt[i] = (mask[i] && !vt[i])
   vd[i] = (!mask[i] && vd[i])
   vd[i] = vt[i] || vd[i]

Fix wrong operand order for the later vmandnot.mm :
  expansion: vmslt{u}.vx vt, va, x;  vmandnot.mm vt, v0, vt;  vmandnot.mm vd, v0, vd;  vmor.mm vd, vt, vd

->
  expansion: vmslt{u}.vx vt, va, x;  vmandnot.mm vt, v0, vt;  vmandnot.mm vd, vd, v0;  vmor.mm vd, vt, vd

This is so complicated! At some point it must be better just to splat x to vt and use a .vv version.
(Moved my comment here for visibility.)

This is so complicated!

@knightsifive Agreed, but the binutils hackers just need to get it right once...

At some point it must be better just to splat

Main problem with splatting is that it needs an entire vector register group as a temporary, whereas this formulation only needs one vector register regardless of LMUL.
Regardless, a compiler with an accurate cost model will just avoid this more expensive instruction and reorganize the code to use SLT or SLE instead of SGE.  So it really is only about hand-coded assembly anyway.

Don't know if the comment helps, but the derivation process is too complicated to me :P
vmslt{u}.vx vt, va, x  /* vt = 1 if va < x; Otherwise, vt = 0.  */
vmandnot.mm vt, v0, vt  /* Use mask v0 to determine whether vt should be updated.  Change the temp result vt from '<' to '>='.  */
vmandnot.mm vd, vd, v0  /* Use mask v0 to determine whether vd should be updated.  */
vmor.mm vd, vt, vd  /* Get the final result.  */

For the third instruction, if mask v0 is set, then vd should be updated, so set vd to zero.  Otherwise, keep the original value of vd (that is, vd & !v0).


iOS crashed when app in background for a while

Describe the bug
put app in background for about 2 hours, then open the phone found app crashed. we got a crash report from testflight.
using agora_rtm: ^1.1.1
Screenshots

Smartphone (please complete the following information):

Additional context
Add any other context about the problem here.

*** Terminating app due to uncaught exception 'NSGenericException', reason: '*** Collection <__NSDictionaryM: 0x28171dbc0> was mutated while being enumerated.'

has been fixed at the latest version


assertion failed in emacs-24/default.nix

I'm suddenly seeing this error message trying to upgrade...
sudo nixos-rebuild switch --upgrade
downloading Nix expressions from ‘http://nixos.org/releases/nixos/unstable/nixos-15.08pre67355.1357692//nixexprs.tar.xz’...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
unpacking channels...
building Nix...
building the system configuration...
error: assertion failed at /nix/store/4l4dc2zrgjwziapnhjg3bb3d6zpbjfa3-nixos-15.08pre67355.1357692/nixos/pkgs/applications/editors/emacs-24/default.nix:14:1
(use ‘--show-trace’ to show detailed location information)

The relevant line:
assert withGTK2 -> !withGTK3 && gtk2 != null;

My config (thought this error appears regardless of any combination of settings):
  nixpkgs = {
    config = {
...
      packageOverrides = pkgs: {
        emacs = pkgs.emacs.override {
          withGTK3 = true;
        };
      };
    };
  };

You asking emacs to build itself with both gtk2 and gtk3.
Try
packageOverrides = pkgs: {
  emacs = pkgs.emacs.override {
    withGTK2 = false;
    withGTK3 = true;
  };
};

Thanks!
PS Shouldn't they be mutually exclusive... ?!

They kinda are. Error you reported in the first post says the assertion
checking their mutual exclusion failed.


Support for relative paths?

I might just be missing something, but is there a way to do relative paths to json files?  I seem to need to specify everything from the root of my workspace.

I believe the Obsidian team "fix" that. Is not longer possible to access files outside your vault.


Unexpected token: name (context) when building (Using ES6 let)

Error msg as below with UglifyJS, which cannot used on ES6:
Failed to compile.
static/js/main.082bd144.js from UglifyJs
Unexpected token: name (context) [./~/striptags/src/striptags.js:17,0][static/js/main.082bd144.js:142975,12]

would you consider build src file in ES5?

Sorry guys, just read the notes:
Note: v3+ targets ES6, and is therefore incompatible with the master branch of uglifyjs. You can either:

use babili, which supports ES6
use the harmony branch of uglifyjs
stick with the 2.x.x branch

Got it work with version 2.2.1, keep on the great work and I just close the issue now.
For others get here from Google (including myself, Read the f* manual lol

Ha, no problem @foreseaz. I didn't realize writing an ES6-only NPM library would cause so many issues, but I'd like to keep it ES6 since it's nicer.

@ericnorris Would you consider compiling it to down to ES5 as well? However I totally understand that many library authors only publish an ES6 version since they target modern browsers or node.js only.

@egoist v2.x.x is ES5 compatible, and so I'd rather leave that as the go-to for people that need ES5 and have the latest versions be ES6.

If you have this in your webpack config:
rules: [
      {
        test: /\.js$/,
        exclude: /(node_modules|bower_components)/,
        use: {
          loader: 'babel-loader',
          options: {
            presets: ['es2015'],
            plugins: ['transform-object-rest-spread', 'add-module-exports']
          }
        }
      }

Change the exclude to (node_modules(?!\/striptags)|bower_components).
That way, babel will compile striptags down for you.


Influxdumper multipule ports

I'm not 100% in love with this approach.
As it is, we scan for any host in the network that has any of these listed ports... we're making a big assumption that no conflicts can occur where another service is using the same port.
@zaibon what do you think?

@rkhamis I also hate the scan approach, not only for this reason but also for the amount of time it takes to scan the entire IP range. If your IP range is wide the scan can take forever.
I suggest we totally modify this to our current use case, to only scan local host for the configured ports

@rkhamis @zaibon
The idea of the network-scanner was to find out which hosts are listening on a given port inside a certain IP range (defined by the cidr)
If we need to change this to accept multiple ports, we need to make sure of the following
1- nmap actually work with the given new parameters (multiple ports) and it lists out the hosts and the detected open ports in a parsable format)
2- return the right structure as per my comment.
IMHO: we can totally drop the network scanner in this new implementation. Since you already gonna scan localhost only, and you already know the list of open ports. we can just start the dumper with that information.
This will also fix an issue if one of the redis instances where down when we started the dumper and then it come back up, the dumper will just start pulling data from it. With the network scanner approach there is know why to know that the instance is alive again

I think now that we have the code for it. we should keep the ability to scan a range.
But if we specify a host and a list of port, we should skip scanning and only use the host and ports given

Add a flag to bypass the scanner

After looking at the code I dont think we need this flag after all if we add a host with cidr / 32 scanning will take no time at all and result will be as expected.

@muhamadazmy  is the solution proposed by Jo ok for you ?
I'll let you review this and merge when you're done.

Output of test now yields
[U influxdumper_multipule_ports][aggregator] jspython AggregatorClientTest.py
[Sun03 11:21] -        AggregatorClientTest.py:90   - INFO     - Injecting 100000 points for minute 0
[Sun03 11:21] -        AggregatorClientTest.py:100  - INFO     - Injected 40% points for minute 0
[Sun03 11:21] -        AggregatorClientTest.py:100  - INFO     - Injected 80% points for minute 0
[Sun03 11:21] -        AggregatorClientTest.py:103  - INFO     - Finished 100000 points for minute 0
[Sun03 11:21] -        AggregatorClientTest.py:90   - INFO     - Injecting 100000 points for minute 1
[Sun03 11:21] -        AggregatorClientTest.py:100  - INFO     - Injected 39% points for minute 1
[Sun03 11:21] -        AggregatorClientTest.py:100  - INFO     - Injected 80% points for minute 1
[Sun03 11:21] -        AggregatorClientTest.py:103  - INFO     - Finished 100000 points for minute 1
[Sun03 11:21] -        AggregatorClientTest.py:90   - INFO     - Injecting 100000 points for minute 2
[Sun03 11:21] -        AggregatorClientTest.py:100  - INFO     - Injected 38% points for minute 2
[Sun03 11:21] -        AggregatorClientTest.py:100  - INFO     - Injected 78% points for minute 2
[Sun03 11:21] -        AggregatorClientTest.py:103  - INFO     - Finished 100000 points for minute 2
[Sun03 11:21] -        AggregatorClientTest.py:90   - INFO     - Injecting 100000 points for minute 3
[Sun03 11:21] -        AggregatorClientTest.py:100  - INFO     - Injected 40% points for minute 3
[Sun03 11:21] -        AggregatorClientTest.py:100  - INFO     - Injected 82% points for minute 3
[Sun03 11:21] -        AggregatorClientTest.py:103  - INFO     - Finished 100000 points for minute 3
[Sun03 11:21] -        AggregatorClientTest.py:90   - INFO     - Injecting 100000 points for minute 4
[Sun03 11:22] -        AggregatorClientTest.py:100  - INFO     - Injected 40% points for minute 4
[Sun03 11:22] -        AggregatorClientTest.py:100  - INFO     - Injected 80% points for minute 4
[Sun03 11:22] -        AggregatorClientTest.py:103  - INFO     - Finished 100000 points for minute 4
[Sun03 11:22] - ...umpScale/sal/process/SystemProcess.py:1318 - INFO     - exec:which nmap
[Sun03 11:22] - ...umpScale/sal/process/SystemProcess.py:1364 - INFO     - system.process.execute [which nmap]
[Sun03 11:22] - ...umpScale/sal/process/SystemProcess.py:1318 - INFO     - exec:nmap -n --disable-arp-ping -send-ip -Pn -sS -p6379 -oX - <IP_ADDRESS>
[Sun03 11:22] - ...umpScale/sal/process/SystemProcess.py:1364 - INFO     - system.process.execute [nmap -n --disable-arp-ping -send-ip -Pn -sS -p6379 -oX - <IP_ADDRESS>]

Let's talk about this
On Apr 3, 2016 1:30 PM, "Jo De Boeck"<EMAIL_ADDRESS>wrote:

Merged #108 https://github.com/Jumpscale/jumpscale_core8/pull/108.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/Jumpscale/jumpscale_core8/pull/108#event-612610932


2871 ws invocation with 3 or more output parameters

Invalid pull request because too commits comming from Flowable 6.6.0 and previous are included.


Allow methods returning IIterable to be used as synchronous generators

See #349.
This PR adds a synchronous generator implementation for methods that return IIterable<T>.
The generator promise implements both IIterator<T> and IIterable<T> and therefore saves an allocation; however, this can be observed via QueryInterface, so I'm not too sure whether this is a good idea in practice.

IIterable<T> is expected to be multi-pass. Please correct me if I'm wrong, but wouldn't this break if you tried to get more than one IIterator<T> out of it?

Yes, but C# already violates that expectation with its own generator methods.

That seems... bad. But I'll defer to @jonwis on this one

I realize that this problem is made worse by the fact that APIs tend to accept an IIterable<T> and rarely an IIterator<T>, even if they don't need multiple passes over the data. My primary concern is that code can pretty easily silently break by new versions of Windows (or other frameworks like WinAppSDK) because an update is made that enumerates more than once. I don't think that's likely to happen often, but it seems easy enough to happen sooner or later.

I realize that this problem is made worse by the fact that APIs tend to accept an IIterable<T> and rarely an IIterator<T>, even if they don't need multiple passes over the data. My primary concern is that code can pretty easily silently break by new versions of Windows (or other frameworks like WinAppSDK) because an update is made that enumerates more than once. I don't think that's likely to happen often, but it seems easy enough to happen sooner or later.

Agree on this; IIterable<T>::First should be returning a fresh new iterator that can be walked over again. It's usually rare, as most implementation code takes the iterable, obtains an iterator, and then pulls values out of that into a vector.
But, it would be a very sharp edge if the IIterable<T> this produces is one-shot.

My mistake, the C# iterator methods do support being iterated multiple times, as long as they return IEnumerable<T> (IEnumerator<T> does not, however). C# achieves this by storing the parameters that where passed to the function and rerunning the function from the start when enumerating it a second time, as if you had called the method a second time with the same parameters (which sounds like a potential footgun if any input reference type is modified). C++'s coroutines do not have the required level of introspection to achieve this, they are indeed one-shot.
We could constrain this implementation to IIterator<T> (which is one-shot, as it can only advance forwards and cannot be reset) only but unfortunately this greatly limits its usefulness (can't easily iterator, no API directly taking IIterator<T>).
nit: MoveNext should throw hresult_out_of_bounds if it is called but the state is already Done

I've now changed the implementation so that the generator is constrained onto IIterator<T>. To get an IIterable<T>, one needs to use a new helper method, wil::make_iterable_from_iterator, which takes the address of a function returning an IIterator<T> and invokes it for every call to First():
IIterator<winrt::hstring> Generator(int x)
{
	co_yield winrt::to_hstring(x);
}

void Foo()
{
	IIterable<winrt::hstring> iterable = wil::make_iterable_from_iterator(&Generator, 3);
}

Mostly looks good to me, however it's been far too long since I've dealt with coroutines in C++. @oldnewthing is probably the most resident coroutine expert if he has any input

I think this is solving the problem at the wrong level. I think we should add a basic wil::generator to wil/coroutine.h for general-purpose generation, and then the C++/WinRT version can be a wrapper around that.

Why not use std::generator then

Because it requires C++23, not C++17/20 like the coroutine infrastructure, and has yet to be implemented by the STL.

Given the one approval, should I still follow the suggestion of adding wil::generator instead?

Either that or implement a WinRT interface which returns IIterable via a generator

The use cases for this feature are the same ones as in C# - as IIterable<T> is mapped to IEnumerable<T> and IIterator<T> to IEnumerator<T>, it is possible to implement Windows Runtime methods returning IIterable<T> and IIterator<T> using yield statements. This PR adds the same functionality to C++, but as C++ coroutines cannot be reused multiple times - with IEnumerable<T>, you can just ask it for a new enumerator - the actual generator was moved to methods returning IIterator<T>, which cannot be reused to iterate from the beginning anyway. This PR also provides a helper method and a helper object implementing IIterable<T> which creates a new generator every time an IIterator<T> is requested, as most of the Windows Runtime passes around IIterable<T> as opposed to IIterator<T>.
Just like in C#, this can be used any time someone wants to use a generator to implement a collection; right now, the choices are implementing a custom iterator or prefilling and returning a collection of which all elements may not even bee needed, both of which aren't as ergonomic as generators.

Yes, I understand how this could be used in theory. But are there practical examples of cases in which you want to pass a generator to a Windows Runtime method? I'm hoping to see a compelling scenario like
struct watcher_desires
{
    bool want_adds;
    bool want_removes;
    bool want_updates;
};

auto trigger = DeviceWatcher::GetBackgroundTrigger(make_iterable_from_generator(
    [=](auto desires) -> IIterator<DeviceWatcherEventKind> {
    if (desires.want_adds) co_yield DeviceWatcherEventKind::Add;
    if (desires.want_removes) co_yield DeviceWatcherEventKind::Remove;
    if (desires.want_updates) co_yield DeviceWatcherEventKind::Update;
}, desires));


What to do about Set in the PDF?

Set is confusing to people not familiar to Agda/type theory. Here are some options:

rename/display it as Prop (or even use the actual Prop?) or Type (probably as confusing as Set)
use something like Rel
others?

We agreed that we'd rename Set to Type everywhere, and add a very short explanation for 'propositions as types'. If this is still confusing to people, we can try Proposition as an alias for Type.

I would avoid renaming Set to Type and also not then capturing the name Set.
I think this is from Bengt's book.
I wise man once said "Set is Agda's name for Type" <- you can write this in the document.

There are two reasons why Set is bad in our case:

it is confusing to people who don't know Agda (why does actionWellFormed return a Set?)
we also have 'actual' sets, which are different from Set.

Anything that people will understand without explanation is better than something that does need an explanation, that why I personally prefer Prop (or Proposition), but Ulf and William convinced me to go with Type. That does need an explanation, but is at least less confusing than Set.

I'll go with the consensus we arrived at on Tuesday (change Agda's Set to Type).  We can revert if this makes @jmchapman very unhappy 😰 ...an alternative would be to find a new notation for @WhatisRT's Set.  Perhaps, aSet or AkSet?  The latter stands for "Andre Knispel Set" or "Also known as Set" (depending on the context).

or set, SET,ZSet, ZFSet, ZFCSet. Although if it only appears for predicates and relations I'm coming around to Andre's notion of Prop :)

I think the Agda terminology comes from here:
https://www.cse.chalmers.se/research/group/logic/book/book.pdf

Naming our axiomatic sets Set and types Type is clearly the least confusing option out of these for non-Agda people. This could make it a little more confusing to Agda people reading our specs, but most of our readers know little to no Agda. And I think most Agda people are very receptive to renaming Set to Type (since many of them do it as well).

I think the Agda terminology comes from here:
https://www.cse.chalmers.se/research/group/logic/book/book.pdf
Or possibly Martin-Löf

Chapter 19, "Types," in the book by NPS, explains how to represent the theory of sets in the theory of types.  It is a nice explanation, but it's not clear to me that this is where the use of Set instead of Type in Agda comes from.  Though something tells me that if I reread that chapter a few times and let it sink in for a while, then it might become obvious that this is precisely where it comes from! 😅


Migrate from tui-rs to ratatui and update other dependencies

tui-rs is deprecated, replaced by ratatui.

Spans replaced with Line

crossterm updated.

Specific error types deprecated. Moved to std::io::Error

notify updated

Thanks!


How to generate tests for RV64D and RV64F using riscv-ctg?

When I use 'riscv_ctg -v debug -d ./tests/ -r -cf ./sample_cgfs/dataset.cgf -cf ./sample_cgfs/rv64i.cgf -bi rv64i -p2,' I can generate tests for RV64I. However, I couldn't find the provided rv64d.cgf and rv64f.cgf. Now I want to generate tests for D and F extensions. How can I do that? Looking forward to your guidance. Thank you very much.

I'd like to use these files too, as a basis for Q and Zfh tests.  Looks like @pawks generated the F tests June 17, 2022.  Are the .cgf something you can post?


build script to sort photos into directories and append photo name to end of photo file name

upstream
downstream
inlet
outlet
barrel
road

I'll do a trial and error on this when I get the chance. Might not even need a script. I would think you would be able to do this in the attribute forms in our Q mergin project by adding a default of sorts?

Good idea but currently not an option I don't think because of this https://github.com/MerginMaps/input/issues/1595
potential workflow to abstract later to pull out the appended word after photo_{word} can be tweaked from the 0120-photos.R scripts

use case_when to mutate site_id from pscis_id and modelled_crossing_id
run  a bunch of mutates ex. `mutate(photo_downstream_renamed = paste0(photo_downstream, '_downstream')
dplyr::pivot_longer to make a 3 column dataframe with headers site_id, name_before, name_after
pull site_id and create.dir for that list
mutate name_before and name_after to be full path filenames with the site_id installed in name_after of course
pull the name columns and run them through fpr::fpr_photo_change_names

https://github.com/NewGraphEnvironment/fish_passage_peace_2023_reporting/issues/6
working function built in https://github.com/NewGraphEnvironment/fish_passage_peace_2023_reporting/blob/main/scripts/01_prep_inputs/0120-photos.R


Configuration shall refer to a file that contains the key and not a directory

Currently the keys are referenced in the configuration with a directory. The runtime searches for files within that directory which is not intuitive.
The configuration should look like this:
debug = true
console_address = "localhost:4200"
key = "examples/keys/north.pub"
container_uid = 1000
container_gid = 1000

[directories]
container_dirs = [ "target/north/registry" ]
run_dir = "target/north/run"
data_dir = "target/north/data"

The signature.yaml contains a key: field to support having different signing keys between NPKs (owned by different parties for example).
That's why the folder approach was used to search for the right one to use.
Maybe we don't need this flexbility.
In case we do want to keep it, we should rather have a key name -> key file mapping in configuration? Like:
[keys]
north = "examples/keys/north.pub"
external = "examples/keys/external.pub"

Or even tie it up to the container_dir:
[registries] // Not sure if that's a good name at all
foo:
   key: /system/etc/north/blah...
bar:

This would also allow to drive a "registry" dir without verity.

Yes, interesting middle ground 😉
I think the right name for that would be [repositories] instead of [registries]?

I tried to sketch this in config.rs:

The key is optional for a repository and indicated that the npk shouldn't be mounted via verity
runtime::state::State::applications gets a reference to a Repository
runtime::state::State::signing_keys is changed and holds a key for each repository.
The writeable flag indicated whether npk can be added/removed at runtime
The install/uninstall api commands must get a repository id
Npks with the same name in the manifest are not allowed
api::Container gets a repository id
api::Request::Repositories is added and returns a Map<api::RepositoryId, api::Repository> (note the api::)

/// Identification of a repository. This is used during add and remove operations
/// to identify the location.
type RepositoryId = String;

#[derive(Clone, Debug, Deserialize)]
pub struct Repository {
    /// Repository directory
    pub dir: PathBuf,
    /// Writeable
    pub writeable: bool,
    /// Signing key. If this is None the containers are mounted without verity
    pub key: Option<PathBuf>,
}

#[derive(Clone, Debug, Deserialize)]
pub struct Config {
    /// Print debug logs
    pub debug: bool,
    /// Console address
    pub console_address: String,
    /// Container UID
    pub container_uid: u32,
    /// Container GID
    pub container_gid: u32,
    /// Directory where containers are mounted at runtime. This must
    /// be read and writeable by the runtime.
    pub run_dir: PathBuf,
    /// Directory where rw data of container shall be stored. Thius
    /// must be read and writeable by the runtime.
    pub data_dir: PathBuf,
    /// List of repositories
    pub repositories: HashMap<RepositoryId, Repository>,
    /// CGroup configuration
    pub cgroups: CGroups,
    /// Platform specific device configuration
    pub devices: Devices,
}

@bzld Thoughts?

@flxo Looks pretty good.
Small point: for (future?) flexibility, the manifests contain a key name besides the actual signature. In your approach key names don't exist and there would be just the one key set for the repository. So we would just ignore the key name and try to check if the signature works or not? Then we might consider to remove the key name field from the manifest even.

@bzld Agree. I don't think that we need the complexity of multiple keys per Repository. This could also be easily added later if needed.


Pepperoni-app-kit not supporting "React Navigation (v2)"

@FruitieX - I noticed that currently pepperoni-app-kit is not supporting "React Navigation (v2)", also not getting any update from long time. I can understand that due to the some reason, we are not getting any update from your end but we would like to use pepperoni-app-kit.
If anyone share idea about how to use "React Navigation (v2)" it would be really good for us.
Thanks in advance.

Having same issue with it. Please provide newer versions support of packages.


Application size and width does not reflect width and height of target view

Hi, I'm here again!  :blush:
var app = new PIXI.Application( {transparent:true, antialias: true, view: mycanvas} );

Should not the height and width be aware of target view width and height instead of 800x600 as default?

Pixi does not have that logic, its your job to call app.renderer.resize and pass screen width and height there.
There's autoResize: true parameter that sets CSS width and height, useful with reslution: devicePixelRatio.

Now I'm doing this:
var canvas      = document.getElementById('c');
    canvas.width    = window.screen.width;
    canvas.height   = window.screen.height;

    var app = new PIXI.Application(canvas.width, canvas.height, {view: canvas, forceCanvas:false, transparent:true, antialias: true});

I was recently scratching my head on how to support autoResize and resolution. Is there any guide about that in the Docs? Or any interesting resource?

https://github.com/pixijs/pixi.js/blob/dev/src/core/renderers/SystemRenderer.js#L218
Basically, if you ask app to resize to (W,H) with resolution A,, you'll get canvas of size (W*A, H*A) and if autoResize is true, then (W,H) will be passed to CSS. real pixels will be stored in renderer.view.width because its a canvas. Screen (css) pixels size is in renderer.screen. For your elements (Sprites, Containers) you have to specify screen coordinates, so resolution doesnt affect them.
That's all. If you want more - you have to experiment. I gave you the only part of code that responsible for canvas size.

@DavidGOrtega hopefully this will help:
Resize to Parent Node
https://jsfiddle.net/bigtimebuddy/wLg7jezb/
Resize to Fullscreen
https://jsfiddle.net/bigtimebuddy/oaLwp0p9/

@bigtimebuddy please add it to wiki.

Done. https://github.com/pixijs/pixi.js/wiki/v4-Tips,-Tricks,-and-Pitfalls#resizing-renderer

Thanks a lot guys!


Can i use the private git repository?

Can i use the private repository like bitbucket in requirements.txt?
is there any config sets a ssh key or basic authentication?
thanks.

Do you mean when using docker? Because, when not using docker, yes pip should just find your ssh keys in your home directory. For Docker I could add -v $HOME/.ssh:/root/.ssh, probably optionally.

sls deploy -v $HOME/.ssh:/root/.ssh
Error --------------------------------------------------
Command "git clone -q ${private_repository_url} /tmp/pip-s2e56Y-build" failed with error code 128 in None
 For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.

Stack Trace --------------------------------------------
Error: Command "git clone -q ${private_repository_url} /tmp/pip-s2e56Y-build" failed with error code 128 in None
at module.exports.logError.errorHandlingError (/usr/local/lib/node_modules/serverless/lib/classes/Error.js:94:11)
at initializeErrorReporter.then.catch.e (/usr/local/lib/node_modules/serverless/bin/serverless:42:3)
at runCallback (timers.js:672:20)
at tryOnImmediate (timers.js:645:5)
at processImmediate [as _immediateCallback] (timers.js:617:5)

From previous event:
at __dirname (/usr/local/lib/node_modules/serverless/bin/serverless:40:9)
at Object. (/usr/local/lib/node_modules/serverless/bin/serverless:43:4)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.runMain (module.js:604:10)
at run (bootstrap_node.js:389:7)
at startup (bootstrap_node.js:149:9)
at bootstrap_node.js:504:3
Get Support --------------------------------------------
Docs:          docs.serverless.com
Bugs:          github.com/serverless/serverless/issues
Forums:        forum.serverless.com
Chat:          gitter.im/serverless/serverless
Your Environment Information -----------------------------
OS:                     darwin
Node Version:           6.11.0
Serverless Version:     1.20.2

Sorry, by add that option I meant a change to this plugin's codebase.

Yes, that happen when i'm using docker. I'll be happy if you add them for me. Thank you.

I tried getting around this by taking the default docker image, commiting the .ssh files to it and setting the new image as dockerImage in serverless.yml, but I'm still seeing the same error. Is there a reason that wouldn't work?

Hi, @mcgeeco .
use the lambci/lambda:build-python2.7 docker image.
You can get the image info in the serverless-python-requirements code. (index.js:87)

Yeah that's what I tried (lambci/lambda:build-python3.6). Thought it should work all right - I'll double check that I didn't make an error somewhere.

@SteveRoland @mcgeeco Did either of you figure out a way to accomplish accessing private git repos from docker?

@stickystyle No, sorry, I was going to come back to it when the proposed fix above was implemented.

I managed to work around it in my project by vendoring the repo into my project. Not ideal, but surely works.
$ mkdir vendor
$ pip download --no-deps --dest ./vendor -e git+https://github.com/myrepo/myproject.git#egg=0.4.2

then add to requirements.txt ./vendor/myproject-0.4.2.zip
Since everything gets downloaded ahead of time with your existing github keys and sent to docker with the rest of the src, there are no issues trying to do it in the container.

I just thought of another workaround. If the repo referencing the private repo is also private (most likely, i imagine) add your dependency as<EMAIL_ADDRESS>where $TOKEN is a github personal token.

I did try this on:
Running "serverless" from node_modules
Framework Core: 3.33.0 (local) 3.33.0 (global)
Plugin: 6.2.3
SDK: 4.3.2
Python3.10
But didn't work.
Error: `docker run --rm -v /Users/PC/Library/Caches/serverless-python-requirements/26b75300d35a96d32b00f7890599100276034aa3e2260e47761d1b99e085aad3_x86_64_slspyc:/test alpine stat -c %u /bin/sh` Exited with code 125
    at ChildProcess.<anonymous> (/Users/cristopherchaconltv/Projects/de-func-cloudflare-deadletter-processor/node_modules/child-process-ext/spawn.js:38:8)
    at ChildProcess.emit (node:events:520:28)
    at ChildProcess.emit (node:domain:475:12)
    at maybeClose (node:internal/child_process:1092:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)


Upgrade Stash dependencies to 3.7.2

The API in Stash was changed with version 3, so the plugin didn't work properly.
This commit updates the dependency to Stash 3.7.2 and uses the new APIs
(like Commit instead of Changeset etc.).
We had problems to install this plugin in our Stash instance which runs on version 3.7.2. So i updated the plugin to reflect the current API and remove deprecated API calls etc. Feel free to incorporate this pull request into your codebase.
Testing with Stash/Bitbucket Server 4.0 still pending, but i think with the current API usage it should work.

I just realized that we have Stash 3.8.0 and the plugin works fine. Although I think we installed it on an earlier Stash version and then upgraded it.

I wonder why it doesn't work for @mdoninger :)
In Stash 3.7 API Changelog Changeset has been deprecated and Commit was added.
Stash API Compatibility Policy states that deprecated classes and method should work until next major version release (which is 4.0).
@mdoninger how does your issue manifest exactly?

Nonetheless, thanks for the pull request. This will be required for the 4.0 release but for now it is a breaking change for users on older version.

After installing the plugin, we couldn't access the repository pages any more, everytime a 500 got thrown and in the logfile there were entries like "GET /rest/api/latest/profile/recent/repos HTTP/1.1" c.a.s.r.e.UnhandledExceptionMapper Unhandled exception while processin
g REST call"
Of course it can be totally unrelated to that plugin and maybe just an incompatibility between two plugins. I'm currently waiting, until our Stash admin installs my version on the Staging instance, then we will see.


[CB-15597] Upscale FreeIpa during datalake resize

So far this just includes changes to add the flow to datalake to call
and wait for freeipa upscale

@pdarvasi reaching out early if you have any feedback at this point

Can you please point me to the design doc?

Do not do this from Datalake code. If you want to do this, then move this logic to Env service. My suggestion: 1) upscale freeipa from env service 2) resize sdx from env service.

Do not do this from Datalake code. If you want to do this, then move this logic to Env service. My suggestion: 1) call freeipa upscale API from env service 2) call sdx resize API from env service.

It is not possible to move the sdx resize to env service. It could be possible to add a point in env service for FreeIpa upscale, but that would include a wait function for the change from FreeIpa or passing back the operation id to datalake and waiting there.

Can you please point me to the design doc?

This was a late requirement for resize and not included as a part of the original design doc

I agree with @sodre90. If we want to couple these together it's like the stop/start environment functionality, so it should be triggered from the EnvService. SDX does not want to control FreeIpa in any way.

@sodre90 any thoughts about this change now?


Why DiscoveryDocument will be cleared out on page refresh? (angular-oauth2-oidc.js:2887 Error)

Describe the bug
I use password flow login:

First I get the discovery document via .loadDiscoveryDocument()...
...and in .then() branch I call .fetchTokenUsingPasswordFlowAndLoadUserProfile(). Everything is cool, works fine, login success.
I reload the page, everything works fine, claims are still accessible via calling .getIdentityClaims().
But when I press logout button, I got an error, when .revokeTokenAndLogout() was called.
The error:
angular-oauth2-oidc.js:2887 Error revoking token TypeError: Cannot read property 'toLowerCase' of null
It does not find revocation endpoint, because Discovery Document is not loaded (it was lost on page refresh).
I double checked .discoveryDocumentLoaded boolean, it is false. But everything works well when I log in, and press logut (without page refreshing).

My question is that this is a by design working?
Or I missed something?
  private readonly authConfig: AuthConfig = {
    strictDiscoveryDocumentValidation: false,
    issuer: 'issuer', // no fix host issuer, so this is why strictDiscoveryDocumentValidation = false
    oidc: false,
    showDebugInformation: true,
    clientId: 'client',
    scope: 'openid username role apps full-api',
    sessionChecksEnabled: true
  };

In auth.service.ts's constructor:
    this.oAuthService.configure(this.authConfig);
    this.oAuthService.setupAutomaticSilentRefresh();

app.module.ts:
import { OAuthModule, OAuthStorage } from 'angular-oauth2-oidc';

@NgModule({
  declarations: [
    AppComponent
  ],
  imports: [
    ...,
    OAuthModule.forRoot({
      resourceServer: {
        allowedUrls: [`${environment.protocol}://${environment.hostname}`],
        sendAccessToken: true
      }
    })
  ],
  providers: [
    { provide: LocationStrategy, useClass: HashLocationStrategy },
    { provide: OAuthStorage, useFactory: oAuthStorageFactory },
  ],
  bootstrap: [AppComponent]
})
export class AppModule {
}

export function oAuthStorageFactory(): OAuthStorage {
  return sessionStorage;
}

Expected behavior
I would expect that discovery document will be stored such as claims, token, etc.
Desktop (please complete the following information):

OS: Windows 10 latest
Browser: Chrome latest
Version of angular-oauth2-oidc: 10.0.0

By design, and by default, every time you reload the SPA you need to again load the Discovery Document, before you do anything else.
Alternatives would include:

not loading disco document, but configuring everything manually
creating your own local cache for the disco document

Also, your IDS could well set caching headers on the disco document, helping the browser be faster.
Does that make sense?

Yes, that makes sense. Thanks for your reply. :)

I'm not sure what the historical reason is. But I presume that for a static document that doesn't change much existing caching mechanisms (cache headers and ETAGs) already suffice? Also, in Angular an interceptor for HttpClient requests to cache this document should also be easy to build?