clang 3.5 cannot find C++ header files

nixpkgs commit: a00e19ceb96ed8ae2910b009c1ed79dff7167517 @ 5 Mar 2015
Sample code: hello.cpp
#include <iostream>
int main(int argc, char **argv) {
    std::cout << "Hello World" << std::endl;
    return 0;
}

Run /nix/store/7hgqhdhwlsk3qlwx22l1a4ll8rx9hrzw-clang-wrapper-3.5.0/bin/clang++ -v hello.cpp
The problem is iostream header file not found
clang version 3.5.0 (tags/RELEASE_350/final)
Target: x86_64-unknown-linux-gnu
Thread model: posix
Found candidate GCC installation: /nix/store/jrhjp66sdfv0pc95dwgdz2sly9hima23-gcc-4.8.4/lib/gcc/x86_64-unknown-linux-gnu/4.8.4
Found candidate GCC installation: /nix/store/jrhjp66sdfv0pc95dwgdz2sly9hima23-gcc-4.8.4/lib64/gcc/x86_64-unknown-linux-gnu/4.8.4
Selected GCC installation: /nix/store/jrhjp66sdfv0pc95dwgdz2sly9hima23-gcc-4.8.4/lib64/gcc/x86_64-unknown-linux-gnu/4.8.4
Candidate multilib: .;@m64
Selected multilib: .;@m64
 "/nix/store/ypcbdpgaqhgjcdw5z7sir2rc6fcv1ark-clang-3.5.0/bin/clang-3.5" -cc1 -triple x86_64-unknown-linux-gnu -emit-obj -mrelax-all -disable-free -disable-llvm-verifier -main-file-name hello.cpp -mrelocation-model static -mdisable-fp-elim -fmath-errno -masm-verbose -mconstructor-aliases -munwind-tables -fuse-init-array -target-cpu x86-64 -v -dwarf-column-info -nostdsysteminc -resource-dir /nix/store/ypcbdpgaqhgjcdw5z7sir2rc6fcv1ark-clang-3.5.0/bin/../lib/clang/3.5.0 -idirafter /nix/store/93zfs0zzndi7pkjkjxawlafdj8m90kg5-glibc-2.20/include -idirafter /nix/store/ypcbdpgaqhgjcdw5z7sir2rc6fcv1ark-clang-3.5.0/lib/gcc/*/*/include-fixed -internal-isystem /nix/store/ypcbdpgaqhgjcdw5z7sir2rc6fcv1ark-clang-3.5.0/bin/../lib/clang/3.5.0/include -fdeprecated-macro -fdebug-compilation-dir /home/demo -ferror-limit 19 -fmessage-length 80 -mstackrealign -fobjc-runtime=gcc -fcxx-exceptions -fexceptions -fdiagnostics-show-option -fcolor-diagnostics -o /tmp/hello-83b60d.o -x c++ hello.cpp
clang -cc1 version 3.5.0 based upon LLVM 3.5.0svn default target x86_64-unknown-linux-gnu
ignoring nonexistent directory "/nix/store/ypcbdpgaqhgjcdw5z7sir2rc6fcv1ark-clang-3.5.0/lib/gcc/*/*/include-fixed"
#include "..." search starts here:
#include <...> search starts here:
 /nix/store/ypcbdpgaqhgjcdw5z7sir2rc6fcv1ark-clang-3.5.0/bin/../lib/clang/3.5.0/include
 /nix/store/93zfs0zzndi7pkjkjxawlafdj8m90kg5-glibc-2.20/include
End of search list.
hello.cpp:1:10: fatal error: 'iostream' file not found
#include <iostream>
         ^
1 error generated.

Invoking clang++ from the nix store won't bring in all the headers and libraries you need. You either need to create a derivation for your test program, or write a short shell.nix file in your source directory with something like the following:
with import <nixpkgs> {}; {
  testEnv = stdenv.mkDerivation {
    name = "test";
  }
}

and then use the nix-shell command. Now you should be able to just run
clang++ hello.cpp

Adding a note for people like me who arrived here from a search engine:
You probably also want
    hardeningDisable = [ "all" ];
in the shell.nix, because of #18995


firstOrNew return null value

$user = Utilisateur::firstOrNew(
['id_user' => $agent->age_id],
['id_user' => $agent->age_id, 'id_profil' => '9']
);
SQLSTATE[23502]: Not null violation: 7 ERROR:  null value in column "id_profil" violates not-null constraint
Version Laravel: 5.1

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.


Custom post type translatable labels not working

Thanks for creating lumberjack. This is the first time we use it and I've run into a problem with translations. We register custom post type as show in the documentation:
return [
    'register' => [
        App\PostTypes\Offer::class,
    ],
];

The custom post type is registert and we can use it in the admin and have an archive and detail view.
In the getPostTypeConfig we try to translate the labels off the custom post type:
protected static function getPostTypeConfig()
{
    return [
        'public' => true,
        'show_in_rest' => true,
        'capability_type' => 'page',
        'has_archive' => true,
        'query_var' => true,
        'label'  => __('Offers', 'text-domain'),
        'labels' => [
            'name' => __('Offers', 'text-domain'),
            'singular_name' => __('Offer', 'text-domain'),
        ],
    ];
}

In poedit we can create a .po file in the language folder. In the functions.php we load the text domain like so:
add_action('after_setup_theme', function () {
    load_theme_textdomain('text-domain', get_template_directory() . '/languages');
});

If checked the loaded paths and the textdomain path is correct. But still the labels aren't translated. After some testing with displaying translated text in several places and in different actions. I've discovered that if I put the translation in a init action it get translated. The CustomPostTypesServiceProvider register the custom post type not in action. If I wrap the post type register in an init action, the labels get translation. Here is my quick and dirty fix for the CustomPostTypesServiceProvider:
public function boot(Config $config)
{
    add_action('init', function () use ($config) {
        $postTypesToRegister = $config->get('posttypes.register');

        foreach ($postTypesToRegister as $postType) {
            $postType::register();
        }
    });
}

Is there any possible way of register the post type in the proper action hook? So that the translation is working.
What versions of software are you using?
Operating System: MacOS 11.5
PHP Version: 7.4.1
Lumberjack Version: 5.0

Hey thanks for reporting the issue. We'll look into whether we can apply your fix to the Lumberjack core. In the meantime, you can replace the core CustomPostTypeServiceProvider with your own version.
In config/app.php all the service providers are defined here:
https://github.com/Rareloop/lumberjack/blob/master/config/app.php#L22
You should be able to add your own service provider inside of your theme. Here are some docs on creating a service provider if that's new to you:
https://docs.lumberjack.rareloop.com/container/service-providers#creating-service-providers
Once you have your own service provider, replace our one with yours in config/app.php. For example:
/**
     * List of providers to initialise during app boot
     */
    'providers' => [
        Rareloop\Lumberjack\Providers\RouterServiceProvider::class,
        Rareloop\Lumberjack\Providers\WordPressControllersServiceProvider::class,
        Rareloop\Lumberjack\Providers\TimberServiceProvider::class,
        Rareloop\Lumberjack\Providers\ImageSizesServiceProvider::class,
        // Rareloop\Lumberjack\Providers\CustomPostTypesServiceProvider::class,
        Rareloop\Lumberjack\Providers\MenusServiceProvider::class,
        Rareloop\Lumberjack\Providers\LogServiceProvider::class,
        Rareloop\Lumberjack\Providers\ThemeSupportServiceProvider::class,
        Rareloop\Lumberjack\Providers\QueryBuilderServiceProvider::class,
        Rareloop\Lumberjack\Providers\SessionServiceProvider::class,
        Rareloop\Lumberjack\Providers\EncryptionServiceProvider::class,

        // Application Providers
        App\Providers\AppServiceProvider::class,
        App\Providers\CustomPostTypesServiceProvider,
    ],

Hope this helps!

@adamtomat thanks for the temp fix! Great work. I've manage to get the CPT labels translated with my own Service Provider


Update SSRSS

Updated SSRSS

Added RSS and SigmaBinary as dependencies
Added recommendations for the new options
Added suggestions for mod support

Added SSRSS-StockIncl to install stock inclinations for SSRSS
Added SSRSS-Clouds to install Low and High Res clouds

This PR will fail on SSRSS because CKAN doesn't like installing folders that only have folders. This is the current layout of the zip:
GameData
  | SSRSS
      | configs
        - files
      | visuals
          | more folders
            - files

It fails because it doesn't detect any files in SSRSS but only folders. If @Galileo88 could include/move a file in the SSRSS folder, it will detect a file and install the mod.
We should change InstallsFilesValidator.cs so it can detect folders with files too as a valid install.

Have we got SigmaBinary back, yet? Last I heard, we still needed author approval to re-add that.

@Sigma88 wants to keep them off CKAN atm, so no we don't have it back. But SSRSS needs SigmaDimensions because it uses the mod to resize the solar system what is the purpose of SSRSS.

I asked @Olympic1 to not add my mods to CKAN because I don't have much time to maintain my mods at the moment and I would not be able to sustain the greater "public" CKAN would expose my mods to
however, I can give you permission to install SD through CKAN only alongside SSRSS
I guess it is possible for you to make this (SD would need to be uninstalled when uninstalling SSRSS)
I'd also like if SD was not listed as a mod, but rather installed as a "module" of SSRSS so bug reports would go through SSRSS devs first and reach me only when the issue is actually related to SD
if all this is possible, you have my permission to install SD with SSRSS
if there are other mods that are currently blocked by SD being off CKAN let me know, I'll take a look and let you know for which one you can do the same

pinging @Galileo88 to make sure he is aware of this

Ok, so given sigma88's permission, we sshould move SigmaDimensions to a "conflicts", and add an install stanza.
As for the failing empty folder install, we can get around that by installing the subfolders into the SSRSS folder, which might be a better solution if all these mods are in a single file structure in the zip.

I'm not sure what this means, but if you plan to install SigmaDimensions inside the SSRSS folder that probably won't work

I'm not sure I understand what you mean when you say I have empty folders? I am pretty certain I laid everything out correctly for eventual CKAN compatibility. I will be glad to change anything so long as I understand what needs to happen :)

@Galileo88 , nothing you need to worry about. We've got an issue in Netkan where it doesn't count files in subfolders and sees an install target as empty when it contains only folders.

@politas I solved it with using SSRSS - Rescale.
So if this way is ok by @Sigma88 , this can be merged.

you have my blessing :)

Sneaky! I like the Dimensions solution! :-)
Other than that, I may be off base, but I think SSRSS-Cont should be providing EnvironmentalVisualEnhancements-Config

Totally overlooked that. Added it.

Cool. Merging!

Actually, now that I have slept on it (accidentally), I wonder  whether it might be the SSRSS-Clouds-*  that are providing "EnvironmentalVisualEnhancements-Config". @Galileo88, can you advise?

Ok, I looked at every file and this should be the correct state of the EVE/Scatterer-configs.
@politas so this can be merged if nothing needs to be changed.

Looks good to me.merging!


Game sometimes crashes when clearing a level and getting an achievement

Two users have reported the game crashing when they clear a level. One user encountered a crash when completing the initial tutorial:

New save file, tutorial pops up, I do the skip, achiev "Now we're cooking", the game crash and close up

Another user reported a crash when beating a level in Poki Desert:

I beat a level in the Poki Desert called "Double Trouble" or "Back to Back" or something like that (it was a level with a well in the middle), and crashed. It was a few levels into that run in career mode yet . it was right after I got these two achievemnts; but i don't know if it's related. they were on screen for a moment

It seems related to unlocking an achievement.

godot.log
Here is a log file which occurred along with the most recent crashes.

This was fixed by the GodotSteam upgrade, although I was accidentally using the GDNative binaries which caused the issue to resurface temporarily.


[test] Update CPMD check

I provide an updated check for CPMD (based on #2454 for VASP), with a modified Slurm setup yielding improved performance for both gpu and mc architecture (note that the current check only runs on the gpu constraint of Piz Daint):

I am setting the number of nodes for the smaller test case to 6, as we do for the other application performance checks
the current test case does not scale beyond 72 MPI tasks and it is outdated (see warning about XC_DRIVER IN &DFT)

Hello @lucamar, Thank you for updating!

In the file cscs-checks/apps/cpmd/cpmd_check.py:

Line 97:73: W291 trailing whitespace

Do see the ReFrame Coding Style Guide


how to access kong ingress controller admin api from aws kubernetes?

Is this a request for help?:
yes
What keywords did you search in Kong Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.):
kong ingress controller in aws kubernetes
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
no

Kong Ingress controller version:
Installed using this command -
curl https://raw.githubusercontent.com/Kong/kubernetes-ingress-controller/master/deploy/single/all-in-one-postgres.yaml \
| kubectl create -f -

Kubernetes version (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.3", GitCommit:"2bba0127d85d5a46ab4b778548be28623b32d0b0", GitTreeState:"clean", BuildDate:"2018-05-21T09:17:39Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.3", GitCommit:"d2835416544f298c919e2ead3be3d0864b52323b", GitTreeState:"clean", BuildDate:"2018-02-07T11:55:20Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}

Environment:

Cloud provider or hardware configuration: AWS
OS (e.g. from /etc/os-release): Amazon linux
Kernel (e.g. uname -a):  Linux ip-172-31-46-44 4.14.33-51.37.amzn1.x86_64 #1 SMP Thu May 3 20:07:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Install tools:
Others:

What happened:
I have tried https://github.com/Kong/kubernetes-ingress-controller/blob/master/deploy/minikube.md in my laptop and it works well. I managed to create ingress resource for another api exposed as a service.
Now trying the same with AWS kubernetes cluster created by kops with k8s.local gossip private network (not a subdomain of a domain from AWS Route53 with public network) and able to deploy ingress controller, services and ingress routes for them using kubectl utility in the cluster and now stuck at accessing the kong admin and proxy apis. There is a elastic load balancer created in aws and its set to listen on port 443 and Kubernetes API is accessible only through https.
Is there any documentation explains how to setup access via AWS ELB to Kong admin and proxy apis running in kubernetes cluster?
This is my cluster in AWS - output from kops edit cluster command.
apiVersion: kops/v1alpha2
kind: Cluster
metadata:
  creationTimestamp: 2018-05-29T13:51:32Z
  name: k8slab.k8s.local
spec:
  api:
    loadBalancer:
      type: Public
  authorization:
    rbac: {}
  channel: stable
  cloudProvider: aws
  configBase: s3://k8s-lab-kops-state-store/k8slab.k8s.local
  etcdClusters:
  - etcdMembers:
    - instanceGroup: master-eu-west-1a
      name: a
    name: main
  - etcdMembers:
    - instanceGroup: master-eu-west-1a
      name: a
    name: events
  iam:
    allowContainerRegistry: true
    legacy: false
  kubernetesApiAccess:
  - <IP_ADDRESS>/0
  kubernetesVersion: 1.9.3
  masterInternalName: api.internal.k8slab.k8s.local
  masterPublicName: api.k8slab.k8s.local
  networkCIDR: <IP_ADDRESS>/16
  networkID: vpc-7d8a061a
  networking:
    kubenet: {}
  nonMasqueradeCIDR: <IP_ADDRESS>/10
  sshAccess:
  - <IP_ADDRESS>/0
  subnets:
  - cidr: <IP_ADDRESS>/20
    name: eu-west-1a
    type: Public
    zone: eu-west-1a
  - cidr: <IP_ADDRESS>/20
    name: eu-west-1b
 topology:
    dns:
      type: Public
    masters: public
    nodes: public

What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Create a kubernetes cluster using this guide - https://dzone.com/articles/how-to-create-a-kubernetes-cluster-on-aws-in-few-m and deploy kong ingress controller and necessary services and ingress routes using https://github.com/Kong/kubernetes-ingress-controller/blob/master/deploy/minikube.md document.
Anything else we need to know:

Did you try to change the type of the service kong-proxy to LoadBalancer ? the type NodePort mean the service will be exposed on the node so it probably does not create any loadbalancer in AWS ELB. Can you try something like:
kubectl delete svc kong-proxy -n kong
echo "
apiVersion: v1
kind: Service
metadata:
  name: kong-proxy
  namespace: kong
spec:
  type: NodePort
  ports:
  - name: kong-proxy
    port: 80
    targetPort: 8000
    protocol: TCP
  - name: kong-proxy-ssl
    port: 443
    targetPort: 8443
    protocol: TCP
  selector:
    app: kong
" | kubectl apply -f -

@Ngob  thanks for that, I have used the type: LoadBalancer to solve this already.

@arunk16 You are welcome
@gerred I can help to improve the deployment documentation on GKE / AWS Kubernetes, feel free to assign me

I'm using the same setup but I have configured it on a subdomain on Route53
I have the same issue, I couldn't connect to the Kong proxy or Admin API also, I have done as suggested by @Ngob
Could you please advise?

@engmsaleh I do not know about AWS deployment or Route53, but I will try to help:
I think this is a AWS specific problem (and the kubernetes deployment), so this is probably not a kong issue. From what I know, if you configure a subdomain you will need something like the route53 mapper
Let me know if this help.
I think your question should be posted on Kong Nation.

Hi,
I'm able to access the Proxy API via the LoadBalancer. Which Pod or Service needs to be exposed to access the Admin API?
I'm trying to setup the Admin API Loopback, but I'm not sure how to access it.
Thank you
kubectl apply -f https://bit.ly/kong-ingress

kubectl get all -n kong

NAME                                READY   STATUS      RESTARTS   AGE
pod/ingress-kong-74f469bbb6-hlxkf   2/2     Running     1          13m
pod/kong-migrations-qztcl           0/1     Completed   0          13m
pod/postgres-0                      1/1     Running     0          13m

NAME                              TYPE           CLUSTER-IP       EXTERNAL-IP                                                                     PORT(S)                      AGE
service/kong-proxy                LoadBalancer   <IP_ADDRESS>   xxxxxx.elb.us-west-2.amazonaws.com   80:32500/TCP,443:30156/TCP   13m
service/kong-validation-webhook   ClusterIP      <IP_ADDRESS>   <none>                                                                          443/TCP                      13m
service/postgres                  ClusterIP      <IP_ADDRESS>   <none>                                                                          5432/TCP                     13m

NAME                           DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/ingress-kong   1         1         1            1           13m

NAME                                      DESIRED   CURRENT   READY   AGE
replicaset.apps/ingress-kong-74f469bbb6   1         1         1       13m

NAME                        DESIRED   CURRENT   AGE
statefulset.apps/postgres   1         1         13m

NAME                        COMPLETIONS   DURATION   AGE
job.batch/kong-migrations   1/1           17s        13m

I was able to edit yaml to create kong-admin service.
---
apiVersion: v1
kind: Service
metadata:
  name: kong-admin
  namespace: kong
spec:
  type: NodePort
  ports:
  - name: admin
    port: 8001
    protocol: TCP
    targetPort: 8001
  - name: admin-ssl
    port: 8444
    targetPort: 8444
    protocol: TCP
  selector:
    app: ingress-kong
  type: ClusterIP
---

Additionally, I modified the ingress-kong deployment
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  labels:
    app: ingress-kong
  name: ingress-kong
  namespace: kong
spec:
  ...
  template:
    ...
    spec:
      containers:
        - env:
            ...
            - name: KONG_ADMIN_LISTEN
              value: <IP_ADDRESS>:8001,<IP_ADDRESS>:8444 ssl
            - name: KONG_PROXY_LISTEN
              value: <IP_ADDRESS>:8000,<IP_ADDRESS>:8443 ssl
          image: kong:1.3
          name: proxy
          ports:
            - containerPort: 8001
              name: admin
              protocol: TCP
            - containerPort: 8444
              name: admin-ssl
              protocol: TCP
            - containerPort: 8000
              name: proxy
              protocol: TCP
            - containerPort: 8443
              name: proxy-ssl
              protocol: TCP
            - containerPort: 9542
              name: metrics
              protocol: TCP
...

Once the Admin-API is created, I'm able to port forward it to my local machine by issuing following command
# Port forward Admin API service to localhost:8080
kubectl port-forward -n kong svc/kong-admin 8080:8001

From there, I can setup the Admin API Loopback by creating a consumer and key credentials associated with that. Finally, remove the Admin-API service and just access the loopback endpoint via the proxy service LoadBalancer.
Is there a better strategy?

I'm also able to access the admin using the instructions @jaskiratr described.
Could you guys please confirm if this is the best way of enabling the admin using the ingress controller?

@jaskiratr It seems that your define both NodePort and ClusterIP for your service (which is incorrect), I think ClusterIP should be used as you don't want do expose your API to the internet

@jaskiratr Could you please describe what address you provided in the loopback ?
Also could you provide the request you used to create the consumer ?
I am puzzled which service you will consume
Thanks in advance

Side note: I commented out type: ClusterIP in favor of type: NodePort
@WoodyFleurant

Also could you provide the request you used to create the consumer ?
I am puzzled which service you will consume

Once the loopback is setup, you can stop the port-forward on your local machine. You can then access the Kong admin API via proxy. Your question pertains to my comment :

From there, I can setup the Admin API Loopback by creating a consumer and key credentials associated with that. Finally, remove the Admin-API service and just access the loopback endpoint via the proxy service LoadBalancer.

1. Temporary access for Admin API
We can now expose the Admin API through Kubernetes Port Forwarding
Issue the following command in a separate terminal to expose the Admin API on :8080
kubectl port-forward -n kong svc/kong-control-plane 8080:8001
# OR
kubectl port-forward -n kong svc/kong-admin 8080:8001

Verify if the Admin API endpoint is available locally on :8080
curl -X GET http://localhost:8080

Expected Response:
{
    "hostname": "",
    "node_id": "6a72192c-a3a1-4c8d-95c6-efabae9fb969",
    "lua_version": "LuaJIT 2.1.0-beta3",
    "plugins": {
        "available_on_server": [
            ...
        ],
        "enabled_in_cluster": [
            ...
        ]
    },
    "configuration" : {
        ...
    },
    "tagline": "Welcome to Kong",
    "version": "0.14.0"
}

2. Create Admin API Service
curl -X POST http://localhost:8080/services \
  --data name=admin-api \
  --data host=kong-admin \
  --data port=8001

3. Add a route for Admin API Service
curl -X POST http://localhost:8080/services/admin-api/routes \
  --data 'paths[]=/admin-api'

3. Access Admin-API through Proxy
Get the Proxy API endpoint
kubectl get svc -n kong

NAME                      TYPE           CLUSTER-IP       EXTERNAL-IP         PORT(S)
kong-admin                ClusterIP      <IP_ADDRESS>   <none>              8001/TCP,8444/TCP
kong-proxy                LoadBalancer   <IP_ADDRESS>    <LoadBalancer-URL>  80:30594/TCP,443:30325/TCP
kong-validation-webhook   ClusterIP      <IP_ADDRESS>    <none>              443/TCP
konga-svc                 LoadBalancer   <IP_ADDRESS>     <LoadBalancer-URL>  1337:30337/TCP
postgres                  ClusterIP      <IP_ADDRESS>    <none>              5432/TCP

We can now transparently reach the Admin API through the proxy server
export PROXY_API=$(kubectl get svc --namespace kong kong-proxy -o jsonpath='{.status.loadBalancer.ingress[*].hostname}')

# or
export PROXY_API=$(kubectl get svc --namespace kong kong-ingress-data-plane -o jsonpath='{.status.loadBalancer.ingress[*].hostname}')

curl $PROXY_API/admin-api/

4. Enable ACL Plugin on Admin-API Service
Reference: https://docs.konghq.com/hub/kong-inc/acl/ We will create two consumer groups admin-group & dev-group. Later, we will configure only the users in admin-group to access the Admin API endpoint via proxy.
curl -X POST \
  --url http://localhost:8080/services/admin-api/plugins/ \
    --data "name=acl"  \
    --data "config.whitelist=admin-group" \
    --data "config.hide_groups_header=true"

5. Create Admin consumer
curl -i -X POST \
  --url http://localhost:8080/consumers/ \
  --data "username=admin"

5. Create key credentials for Admin consumer
curl -i -X POST \
  --url http://localhost:8080/consumers/admin/key-auth/ \
  --data 'key=ENTER_ADMIN_KEY'

6. Add Admin consumer to Admin group
curl -i -X POST \
  --url http://localhost:8080/consumers/admin/acls \
  --data "group=admin-group"

7. Verify ACLS configuration for Admin
curl -X GET http://localhost:8080/consumers/admin/acls

Expected response:
{
    "total": 1,
    "data": [
        {
            "group": "admin-group",
            "created_at":<PHONE_NUMBER>,
            "consumer": {
                "id": "e827e641-409c-4543-8059-13403e9da44f"
            },
            "id": "27f827b1-542d-4221-96b2-b95f08808af1"
        }
    ]
}

8. Enable Key Auth Plugin on Admin-API Service
curl -i -X POST \
  --url http://localhost:8080/services/admin-api/plugins/ \
  --data 'name=key-auth'

9. Access Admin-API through Proxy API as Admin
As expected, access to the endpoint without Admin key credentials should now be blocked.
curl -X GET $PROXY_API/admin-api

Expected response:
{"message":"No API key found in request"}

Now provide the Admin key credentials to access the Admin API endpoint via the Proxy API.
curl -X GET $PROXY_API/admin-api \
--header "apikey: ENTER_ADMIN_KEY"

Expected Response:
{
    "hostname": "",
    "node_id": "6a72192c-a3a1-4c8d-95c6-efabae9fb969",
    "lua_version": "LuaJIT 2.1.0-beta3",
    "plugins": {
        "available_on_server": [
            ...
        ],
        "enabled_in_cluster": [
            ...
        ]
    },
    "configuration" : {
        ...
    },
    "tagline": "Welcome to Kong",
    "version": "0.14.0"
}

Finally, you may now stop the port forwarding for Admin API to localhost:8080.

Could someone use the API Loopback the way @jaskiratr did and use Konga with this configuration?
I have kong and a service for Konga in Google Kubernetes Engine, but I haven't figured out yet how to do the connection if the admin API has key-auth enabled

Is there a way to do this that does not involve setting the KONG_ADMIN_LISTEN to <IP_ADDRESS>:8001 ?
Given there's a service (kong-admin above) I would expect kong-admin:8001 to work - but it doesn't seem to


Visualizing more than one rows of a Pandas DF

Hi there!
First of all, thanks for the project, it is awesome.
I'm working on it since a couple of days, trying to upload and visualize a csv/parquet file.
I've followed the pandas example, and looked to the documentation, in order to understand how to create an Ag Grid from a pandas dataframe.
However, I am not able to visualize more than one row of  my DF.
If I try to show more than one row (even just two rows)  I get an empty div in the web page.
I've checked the grid.options which it seems to have all the field in a correct way. The rawdata are correctly populated.

The first image is about my log, where the df.head() and the grid.options are printed.
The second image reports the correct visualization if just one row is showed.
Thanks for the help!

Please note that we are not using issues for questions/support like requests any more. Since justpy is an interface to javascript components we need to make sure first what the nature of the issues is and therefore it's suggested t to ask your question at https://stackoverflow.com/questions/tagged/justpy additionally adding the aggrid tag. Please follow the stackoverflow rules to supply a full explanation including source code. Later you might come back here with an issue that specifies what the correct justpy behavior should be.


Add schema.org markup on datasets page

More info on how-to here https://ai.googleblog.com/2018/09/building-google-dataset-search-and.html

NOTE: Schema.org's Dataset vocabulary was originally based on DCAT, which in turn used Dublin Core and FOAF terms.

Hi @pzwsk
Yes, thank you. The first link had the information I was after.
Here it says:
"We can understand structured data in Web pages about datasets, using either schema.org Dataset markup, or equivalent structures represented in W3C's Data Catalog Vocabulary (DCAT) format"
Given JKAN already embeds DCAT markup, I'm hesitant to add Schema.org markup on top of it (it will be a lot of time and effort to do so), hence why I ask about the advantages/enhancements adding Schema.org would bring.
That said, when I say "embeds DCAT", this is true only for the built-in JKAN fields. For instance, I have not embedded DCAT markup alongside the information in custom tables (e.g., fields under "RDL Hazard Info" and "Additional Info" on this page).
I could add DCAT markup or Schema.org markup to these fields, but again, hesitant to do both.

Thanks, Taku, not sure either there is a clear need at this stage to go
further. Next step is contact potential platforms that would harvest us (WB
data hub, google dataset search, etc.)
At least we can and should put in the documentation of our JKAN instance
that core metadata are exposed in DCAT format.
Best,
On Mon, Mar 15, 2021 at 11:00 AM Takuya Iwanaga @.***>
wrote:

Hi @pzwsk https://github.com/pzwsk
Yes, thank you. The first link had the information I was after.
Here
https://developers.google.com/search/docs/data-types/dataset#approach
it says:
"We can understand structured data in Web pages about datasets, using
either schema.org Dataset markup, or equivalent structures represented in
W3C's Data Catalog Vocabulary (DCAT) format"
Given JKAN already embeds DCAT markup, I'm hesitant to add Schema.org
markup on top of it (it will be a lot of time and effort to do so), hence
why I ask about the advantages/enhancements adding Schema.org would bring.
That said, when I say "embeds DCAT", this is true only for the built-in
JKAN fields. For instance, I have not embedded DCAT markup alongside the
information in custom tables (e.g., fields under "RDL Hazard Info" and
"Additional Info" on this page
http://jkan.riskdatalibrary.org/datasets/hzd-afg-dr/).
I could add DCAT markup or Schema.org markup to these fields, but again,
hesitant to do both.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GFDRR/rdl-jkan/issues/12#issuecomment-799287017, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AASEVRYWL5JZEXI6JEFE2TTTDXLENANCNFSM4XWG5IFA
.

Google dataset search does support both DCAT and Schema.org although they recommend the latter.
I had a look at the DCAT embedded in the JKAN pages, using this RDFa extractor it seems to parse fine. Although the OGP properties are mixed in with the Dataset.
So it should be possible for Google, at least, to index the pages in JKAN. I can't see the site in Google search, but they might not have harvested yet. If that covers the core requirement, then perhaps we don't need the Schema.org markup as well?
Looking at the World Bank Data Hub they are embedding both sets of metadata. They're using RDFa to provide the DCAT metadata (as we are with JKAN). They'e usings a variety of extra schemas to (see example output).
To provide the Schema.org metadata they're using an embedded JSON-LD block:
<script type="application/ld+json">...</script>

This probably simplifies things as it avoids having to add both set of properties across the HTML page. But still requires a conversion of the metadata to the other format.

In reviewing this I've noticed some bugs in the DCAT metadata, as parsed by the RDFa extractor linked above:

I don't think the metadata download should be marked up as a distribution, as it doesn't contain the data.
the title property seems to be picking up the titles of the distributions, not the dataset title. That might be related to the above
the OGP description property should have same value as the dataset description?

Thanks for the review @ldodds
Would this be resolved by having a dedicated endpoint (#14) ?
Otherwise:

I don't think the metadata download should be marked up as a distribution, as it doesn't contain the data.

For clarity, this was the default behavior for files exposed via JKAN which I copied when modifying for RDL.
But I guess this goes back to how "data" is defined/framed.
From my perspective this metadata is data describing the dataset, and is made available as a distributed resource.
But semantics aside, would dcat:CatalogRecord be more acceptable?
(I suspect not but trying to find a suitable alternative).

the title property seems to be picking up the titles of the distributions, not the dataset title. That might be related to the above

Sorry, I am missing something here.
If we take this entry as an example, the title of the dataset is "Afghanistan agriculture", and the given resource name (the distribution) matches.
Are you suggesting that the distribution should match the resource filename, or otherwise made different from the resource name?

the OGP description property should have same value as the dataset description?

Assuming this is the Open Graph Protocol, I suggest we disable the OGP feature.
The base JKAN implementation is set up to include OGP at the page level (hence why you're seeing different values), and the only configuration provided is "on or off".
Modifying this to be more configurable is a much larger body of work.

Currently we have a general title and description for the whole dataset page, and specific titles descriptions for each of the resources (shown on "details").
Related to what was said in https://github.com/GFDRR/rdl-standard/issues/7, would it be better to split resources and have more univocal/precise metadata?

A Distribution is "A specific representation of a dataset. A dataset might be available in multiple serializations that may differ in various ways, including natural language, media-type or format, schematic organization, temporal and spatial resolution, level of detail or profiles".
The metadata is a description of the dataset, rather than a distribution of it. So it doesn't really fit with serving it as a Distribution in my opinion. A Catalog Record is closer perhaps but also doesn't look quite right.
Portals sometimes have link to download the dataset metadata (which is displayed and embedded into the page) in different formats, e.g. on WB DH: "The information on this page (the dataset metadata) is also available in these formats...". But that's different to the resources associated with the dataset.
re: "the title property. I just meant that there's something wrong with the embedded RDFa markup. When extracting the metadata from the page, the dcterms:title property ends up with two values: "Afghanistan agriculture" and "Metadata". There's also only a single Distribution with the title of "Afghanistan agriculture". So something not quite right in there, but I've not identified the source of the problem.
I've included a screenshot. I used the Structured Data Sniffer extension to try and show it.

Hope that helps.

Thanks, if I understand correctly:

different distributions should always refer to the same dataset (different version or language), and then should not be used for different subsets (e.g. one distribution is residential exposure and another one is industrial exposure);
those should be distinct datasets instead

@matamadio broadly yes. Sometimes you might split a large dataset over multiple files in different ways. I think its legitimate to have those as separate distributions associated with the same dataset. The most common case is usually a single distribution per dataset.
My rule of thumb is that if there's any differences in the provenance or governance of the data (e.g. its produced by a different process, or by a different organisation, or has different licensing) then it's a different dataset and will have its own distribution(s).

Alright, then I will need to split several sets after the schema update.

Hi @ldodds

re: "the title property. I just meant that there's something wrong with the embedded RDFa markup. When extracting the metadata from the page, the dcterms:title property ends up with two values: "Afghanistan agriculture" and "Metadata".

The reason for this is because the base JKAN template assigns a dcterms:title property for each associated resource entry (and I subsequently used as a basis for the RDL metadata file).
JKAN assigns a dcat:Dataset property for each file resource, so it seems that the sniffer tool lumps all the dcterms:title tags together.
The implemented approach may not align with DCAT completely either, as the DCAT v2 documentation appears to suggest that Datasets can represent collections of Distributions (as per your statement above re definition of "Distribution").
I've tentatively adjusted the JKAN template (only on local dev) such that dcat:Dataset property is provided on a once-per-page basis, with all resources listed therein marked as dcat:Distribution.
In this way, each dcterms:title gets associated with a Distribution.

The metadata is a description of the dataset, rather than a distribution of it. So it doesn't really fit with serving it as a Distribution in my opinion. A Catalog Record is closer perhaps but also doesn't look quite right.

If I've interpreted the DCAT v2 documentation example correctly (and good chance I haven't) then the Distribution type can also be used for accompanying metadata, as given in the example linked/shown below
dcat:distribution [
      rdf:type dcat:Distribution ;
      dct:title "RDF/XML representation of the ontology used for the data"@en ;
      dcat:downloadURL <http://resource.geosciml.org/ontology/timescale/gts.rdf> ;
      dcat:mediaType <https://www.iana.org/assignments/media-types/application/rdf+xml> ;
]

https://www.w3.org/TR/vocab-dcat-2/#ex-elaborated-bag
I've also updated the dcat:accessURL for Distributions and rdl-metadata files to dcat:downloadURL.
Again these changes are only made locally until we are in agreement.


Fix kubectl incorrect download URL version

Specify v on the version element of Tool struct for kubectl.
Addresses #436
Signed-off-by: Yankee Maharjan<EMAIL_ADDRESS>
Description

Motivation and Context

[x] I have raised an issue to propose this change (required)

How Has This Been Tested?

Types of changes

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

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I've read the CONTRIBUTION guide
[x] I have signed-off my commits with git commit -s
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

[ ] I have tested this on arm, or have added code to prevent deployment

Sorry, i was not sure what the prefered way is.  the version in the version tag of arkade or in the url... Sorry for the trouble...


Rest: Rate limiting issues on Bearer token requests

reported by hycord via discord
const restClient = new Rest({ token: access_token, tokenType: token_type })
  let userData = {};
  try {
  console.log('restClient > getCurrentUser : getCurrentUser()')
  userData = await restClient.user.getCurrentUser() } catch (e) {
    return {
      status: e.status,
      body: { message: e.message }
    }
  }
  console.log('restClient > getCurrentUser : getCurrentUserGuilds()')
  userData.guilds = (await restClient.user.getCurrentUserGuilds()).sort((a) => a.owner ? -1 : 0);

for some reason it is throwing rate limit on getCurrentUserGuilds

I am also reminded I never handled global rate limiting so lol

seems to be stuff with bearer token requests which isn't something I widely tested. gotta see if these share with other bearer tokens from the same bot and so on.

https://discord.com/developers/docs/topics/oauth2#client-credentials-grant
Good for testing oAuth Bearer tokens

I just realized are these routes even exposed by our thing because they're not written as actual endpoints

yes 🕺🏼

this is a rounding issue and a fix has been implemented in an upcoming pr.


Added green/red styling for chart to reflect change over time

@carrotderek provide me with your ARK address or contact me on Ark slack (boldninja) if you don't want to share it publicly.

@boldninja For sure - APh1rr659qmB1he1JSWDUvxzpwHVujSWXZ


Added case_sensitive_completion option to extension

This fixes a bug with recent IPython versions, namely the fact that completions are listed in a case-insensitive order (ignoring both the default behavior of dir and __dir__ as well as the semantic importance of case in Python identifiers).
As this monkey patches a particular function in IPython, the default of this parameter is False but you can enable it by adding a ~/.holoviews.rc:
import holoviews as hv
hv.extension.case_sensitive_completion=True

This is highly recommended as it allows you to index into Layout and Overlayas originally intended. Hopefully, this fix will make it's way into the next IPython release.

Looks good to me.

I've improved handling of the holoviews.rc file. You can now stick a 'holoviews.rc' at the top-level of the git repo and it will be used, instead of having to stick the file in home.

@jbednar @philippjfr I am open to suggestions for a better name than case_sensitive_completion. Otherwise ready for review.

Looks good to me.  Ready to merge?

Will merge once tests pass.


Add Jupyterlab into Winget repository

Provide Jupyterlab in winget for easier way to download

I submitted a PR to winget for this here: https://github.com/microsoft/winget-pkgs/pull/90660

thanks for working on this @brl0 . I tested on a Windows machine and it works fine!


pkg/endpointmanager: Extend subscribers for restored endpoints

Enables subscribers to be notified about restored endpoints as the EndpointCreated is called only for newly created endpoints.
Signed-off-by: Aditi Ghag<EMAIL_ADDRESS>

/test

/test

/test

/test

/test


Update in the projects list

I have added 4 of the DesignSystemsOSS Projects in this module.
Please take a look at this PR.
ℹ Repository information
The repository has:

[x] At least three issues with the good first issue label.
[ ] Detailed setup instructions for the project.
[x] CONTRIBUTING.md
[x] Actively maintained.

Please review my PR

Thanks for adding repositories! @yashsehgal 🎉
Hope you add detailed setup instructions soon.

Thanks for adding repositories! @yashsehgal 🎉
Hope you add detailed setup instructions soon.

Sure @shubhendra-deepsource 👍🏽


Update index built with newer OPM for OpenShift 4.6

This new index image fixes a problem where the operator could not be installed on OpenShift 4.6. This PR also removes the namespace from the catalog source YAML. Image for testing can be found at quay.io/ebaron/container-jfr-operator-index:0.0.3.

Looks good and seems to have successfully installed the operator for me on CRC 1.22.0/OpenShift 4.6.15. Should we also document the opm version used in the README?

Looks good and seems to have successfully installed the operator for me on CRC 1.22.0/OpenShift 4.6.15. Should we also document the opm version used in the README?

Good idea. I've done this now.

Image pushed to quay.io/rh-jmc-team/container-jfr-operator-index:0.0.3.


Feature: Allow opening from URL

It would be nice if the web version could be passes a URL to load data from. It could either be a .ply to work as a viewer, or a .zip and start training.
It would be especially nice if this worked with something like Google Drive URLs, but I'm not sure if you can simple download data from those or whether that needs some special authentication.
Would need a simple HTTP library:

That is async
ideally compiles down to just a JS fetch() call on wasm

How to ensure the safety of ZIP URLs?

It depends. I consider the case that a zip file can be decompress in this way:
https://brush-demo.com/?url=https://bad.com/bomb.zip

It should be fine if the URL is passed to the obvious <input>.

This is now done post #35 and #37 !
Loading a zip bomb might crash the tab, but that's all it should do, up to Chrome to not have that catastrophically go wrong imo.

Get "Error: Failed to download data (are you trying to download from Google Drive? You might have to use the proxy" when inputting a Google Drive URL. Get "Error: error sending request" when inputting a github URL. What format should the URL be when we put ply files on Google Drive or github?


Limit the number of events sent to firehose.putRecordBatch to 500

Describe the bug
According to API_PutRecordBatch only 500 events can be sent simultaneously. However in case of a spike of events within the Kinesis Stream, we might receive more than 500 events. Thus the call fails, events are not consumed and the stream starts to lag behind.
To Reproduce
Send a spike of events simultaneously.
Expected behavior
We should chunk the incoming events into batches of 500 max.
Please complete the following information about the solution:

[v4.0.2]
[eu-central-1]
[no] Was the solution modified from the version published on this repository?
[na] If the answer to the previous question was yes, are the changes available on GitHub?
[yes] Have you checked your service quotas for the sevices this solution uses?
[yes] Were there any errors in the CloudWatch Logs? How to enable debug mode?

Screenshots
The following screenshot shows how the Stream get filled up.

And this is the error in CloudWatch:

Additional context
NA

Getting same results at cloudwatch, can we get an update for this error ASAP ?

Hi, thanks for reaching out. This solution is being EOL and will only be receiving critical patches. We recently launched the Centralized Logging with OpenSearch solution and recommend migrating to this new solution.

fixed in https://github.com/aws-solutions/aws-centralized-logging/pull/57


Add support for tokio-tungstenite.

This will prevent twilight users from compiling two separate Websocket libraries. Ideally, this should be implemented as an additive feature: having features for both backends selected should add a parameter to Config to choose this at runtime (with an arbitrary default).

What do you think about switching serenity and songbird to tokio-tungstenite?

That should be fine, and means we don't need to worry about all the conditional config that would come up if we supported two backends. While I'm not sure what the exact library differences are, this seems reasonable versus supporting many backends if serenity makes the switch.

It's mostly just s/async_tungstenite/tokio_tungstenite/.

Check for the required changes in serenity

https://github.com/serenity-rs/serenity/pull/2036


pull request for e2e test at 12/21/2016 10:45:21

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[Feat]: Improper presentation of CSS

Feature Description
The web-page content are not aligned properly and it does not have logo.
Provide a detailed description of the feature
I would like to add a logo beside Ticketify heading and align the contents of the page properly.
Put here any screenshots or videos (optional)

By submitting this issue, you agree to

[X] I agree to follow this project's Code of Conduct
[X] I’ve read all the issues in the issue section, and this feature has not been proposed yet.

Other Information

[X] I'm a GSSoC '24 Extended contributor
[X] I'm a Hacktoberfest '24 contributor
[X] I am willing to work on this feature (optional)

Feature Description:
Can make a better UI using Next ui,tailwind css or Magic UI using a better color scheme
Provide a detailed description of the feature
By adding the better CSS that  enhances the UI and glow of website were website becomes more user friendly.
Please assign this to me , I am ready for this
Thankyou!
By submitting this issue, you agree to
I agree to follow this project's Code of Conduct
I’ve read all the issues in the issue section,
Other Information

[ ]  I'm a GSSoC '24 Extended contributor
[ ]  I'm a Hacktoberfest '24 contributor
[ ]  I am willing to work on this feature


Filter netem related chaos with pod/ip/port

What problem does this PR solve?
UCP #295
What is changed and how does it work?
This PR introduce filter for netem chaos action, it works by combile ipset and tc filter, if user specify target selector, save those into ipset and add filter for those traffic route to a netem qdisc.
Details in the code comment of netem controller.
The selector logic reused network partition target and direction, so it can work with from/to/both directions as well.
To keep backward compalibility, if user don’t specify target selector, netem will apply to all the logic.
Check List
Tests

Unit test
Manual test (add detailed scripts or steps below)

Code changes

Has Go code change

Side effects

Breaking backward compatibility

Related changes
Does this PR introduce a user-facing change?:

NONE

Codecov Report

Merging #403 into master will increase coverage by 0.41%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #403      +/-   ##
==========================================
+ Coverage   58.16%   58.57%   +0.41%
==========================================
  Files          60       60
  Lines        3650     3626      -24
==========================================
+ Hits         2123     2124       +1
+ Misses       1355     1333      -22
+ Partials      172      169       -3

Impacted Files
Coverage Δ

pkg/utils/selector.go
51.65% <0.00%> (-0.83%)
:arrow_down:

controllers/timechaos_controller.go
0.00% <0.00%> (ø)

api/v1alpha1/timechaos_types.go
4.34% <0.00%> (+0.18%)
:arrow_up:

api/v1alpha1/kernelchaos_types.go
4.65% <0.00%> (+0.20%)
:arrow_up:

api/v1alpha1/networkchaos_types.go
18.93% <0.00%> (+0.28%)
:arrow_up:

api/v1alpha1/iochaos_types.go
32.55% <0.00%> (+1.44%)
:arrow_up:

api/v1alpha1/podchaos_types.go
32.55% <0.00%> (+1.44%)
:arrow_up:

controllers/iochaos_controller.go
90.47% <0.00%> (+4.76%)
:arrow_up:

controllers/podchaos_controller.go
90.47% <0.00%> (+4.76%)
:arrow_up:

controllers/networkchaos_controller.go
90.47% <0.00%> (+4.76%)
:arrow_up:

... and 1 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bdb15d3...5fc598b. Read the comment docs.

Thank @vincent178 for the great work!
Would you mind to add some yaml example file or explanation how to use the feature?
It would be very appreciated for newbies like me :)

Hi @hoang-tranviet , I will add those examples and detailed comments once the feature is completed, thanks for your patience.

@Yisaer code updated, PTAL, thanks

@vincent178 Great job!

/run-e2e-test

/merge


Add size option to limit the total documents to move

Limit the number of objects to move totally (not by shard).
Should fix:

https://github.com/taskrabbit/elasticsearch-dump/issues/311

ElasticDump is looking for a new maintainer(per #333). We have one volunteer so far, but we can always use more! @ebuildy are you interested in helping out?
This PR is missing a test.  A section should be added to the test suite to confirm this new behavior works as intended (and lock it in).

Hello @evantahler , sure!
At Qwant.com we use elasticdump very often, personnaly I could help a few, I will ask to the guys if someone is interested too.
+1 for the test, I will do it tomorrow (end of the day here in France).
Thanks you,

test is here!

great! Thanks!


Add update program method with few other small changes

Purpose
The purpose of this PR is to fixes #53 and closes #55
Goals

Introduced a new API to edit a program.
Limit the ability to change the program State when creating/ editing the state of a program.

Approach

Added the new API with relevant test cases.
Updated the existing add/edit state APIs and updated the test cases.

Screenshots

Preview Link
N/A
Checklist

[x] This PR doesn't commit any keys, passwords, tokens, usernames, or other secrets.
[x] I have read and understood the development best practices guidelines ( http://bit.ly/sef-best-practices )
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation

Related PRs
N/A
Test environment

MacOS 10.15
JDK 1.8
MySQL 5.7
Chrome

Learning
N/A

Yes for the current stage. But in case a requirement arises it’s flexible to change


add links to core getting-started tutorials

/cc: @richlander added paragraph with tutorial links to about/index.md and standard/index.md

I'd liked your idea so much ... can you do the same with welcome.md, too?

@richlander done

Sweet. Thanks!

Should we start using included for such cases?

@mairaw yes, do includes work with docs.ms.com, are relative links in an include relative to the include file location rather than the articles it's included in, and what's the syntax?

I know they work, but haven't actually used them. The syntax looks like this:
[!INCLUDE[sample include file](./includes/sampleinclude.md)]

We can chat this week with the EMS team who has been doing this for longer and check how the relative links work with the includes.


Fix v6 server-side use of missing APIs

When running the e2e smoketest with Puppet v6 server, we get 500 errors.
Running e2e and monitoring the server container logs, error can be seen here:
2020-06-25 20:02:55,317 ERROR [p.r.core] Internal Server Error: org.jruby.exceptions.NotImplementedError: (NotImplementedError) NotImplementedError
        at RUBY.create_session(/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/http/external_client.rb:77)
        at RUBY.initialize(/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/ssl/state_machine.rb:376)
        at RUBY.certificate(/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/ssl/host.rb:126)
        at RUBY.localhost(/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/ssl/host.rb:28)
        at RUBY.decrypt(/etc/puppetlabs/code/environments/production/modules/conjur/lib/puppet/functions/conjur/decrypt.rb:11)

in this block of code: https://github.com/cyberark/conjur-puppet/blob/v2.0.3/lib/puppet/functions/conjur/decrypt.rb#L11
Relevant block:
  def decrypt pkcs7
    host = Puppet::SSL::Host.localhost
    key = host.key.content
    certificate = host.certificate.content
    decryptor = OpenSSL::PKCS7.new pkcs7
    sensitive.new decryptor.decrypt key, certificate
  end

closing as duplicate of cyberark/conjur-puppet#91


Code cleanup!

Description
The language folders have a lot of files that are not part of any subfolder. Some of them are potentially the same code with the same different approaches. I want:

All the code files, well arranged.
If you can evaluate the code quality and find them poorly written, feel free to remove them.
Just list all the files removed so that others can contribute better code.
Every language will be assigned to a different person for a fair chance.

Languages and Assignees:

[ ] Python: @
[ ] Java: @
[ ] C: @
[ ] C++: @

@kaustubhgupta assign this to me! Would like to contribute.

Hey assign this to me I would like to contribute

@kaustubhgupta I would like to contribute in Java

hey, i can contribute to this. would love to contribute

@kaustubhgupta I would like to contribute to Java

Assigned to you in Java

@govindraj111 @VishalS047 @theyashwanthsai let me know your preferred languages

@kaustubhgupta
Can you please elaborate on the description about what exactly you want.
What do you mean by well arranged? Do I have to write code myself also or just remove unnecessary code or correct it?
please elaborate more so that we can be more efficient.
I hope you understand.

@kaustubhgupta Can you please elaborate on the description about what exactly you want. What do you mean by well-arranged? Do I have to write code myself also or just remove unnecessary code or correct it? please elaborate more so that we can be more efficient. I hope you understand.

For example, you can create subfolders under the Java directory for Sorting Algos where all the sorting algorithms such as heap sort, merge are present. In this way, you can create multiple subfolders for such categories. If you don't find any particular category, then put in Others.
And, do check if the codes are good enough and not repetitive. You can free to remove such cases.

ok great thanks

@kaustubhgupta java

@kaustubhgupta Will be drilling it with Java !

Java is already assigned, you can pick up other languages

I would like to work on java

@kaustubhgupta
I have made a PR please review it.
I am waiting for your acceptance.


Create SystemLibraryHowTo.md

Add a short guide for using the SE-0208 system library targets feature.

Thanks, this will be great. I think we should merge the existing guide with this and have just one document for all system library stuff. Would you be interested in doing that?

Basic noob question
I've got a libssh2 installed from brew: brew install libssh2. pkg-config --cflags libssh2 fails with error.
I can still use libssh2 via CSSH package: https://github.com/jakeheis/CSSH/blob/master/Package.swift
It does not include systemLibrary target.
Apparently, this guide does not cover all cases, does it? What's the difference between using systemLibrary vs. exporting a library like CSSH package does? How do I choose the right/better way?
If you could post your thoughts about this here or even reflect this in your guide it will be awesome!

@aciidb0mb3r we can replace Clibgit example with my guide, but we would lose the JPEG example which unfortunately is still using the old import system

@beefon I don’t know how it is on brew but the name of the package from apt is just libssh
sudo apt install libssh-dev
pkg-config --cflags --libs libssh

-lssh

note libssh has no --cflags because its headers live in /usr/include/

@aciidb0mb3r I tried linking libjpeg and it works normally? i don’t know why the documentation says it needs an -Xlinker flag, the reason it can’t find it is because the name of the package is spelled wrong. (libjpeg, not jpeg)

The original guide might be out-of-date about libjpeg. I don't think we need two examples as long as we have something that explains everything clearly. I'd suggesting updating this guide with the libgit project for both methods with preference for .systemLibrary.

what’s wrong with the cairo example? and there’s really no good reason for anyone to use the old method anymore so maybe a short note that you might see a different layout in older repositories would be enough

You could add a small section with deprecated importing style with a note that everybody’s encouraged to move to the new syntax.

There is nothing wrong with cario per-say, its just that more people might be familiar with the libgit library as it is more general purpose tool. I agree with @beefon that we should keep docs for old method as we'll be supporting it. But we should clearly mark that it is deprecated and people shouldn't really use it.

how’s this?

Closing due to inactivity, feel free to update and reopen.

I'm glad I found this message on the Swift forums, which links to the guide in this PR. Before I found it, I had the greatest difficulties using systemLibrary targets (read: I could never guess how to make it work, based on the available documentation).
I wish this PR would be reopened, @aciidb0mb3r, @kelvin13.


[WIP] Reject out-of-range PoW nonces in header validation

finishes PT-152915267 - Validate received block nonce
Checks if nonce is within uint64 limits.
WIP: As a consistent solution, requires PR #369 as uint64 nonces are implemented there.

Closed and continued in PR #391


Staging cli trigger for patch v0.19.2

Issue #, if available:
Description of changes:
Staging cli trigger for patch v0.19.2
Testing (if applicable):
Documentation added/planned (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/hold

/approve


Tutorial Average Neural operator

Fixing bugs with existing implementation
Creating tutorial

@ndem0 @guglielmopadula can we merge?


System Text/Copy Button

[ ] Copy Text need to be changed to System Text

[ ] Copy Text need to be changed to System Text


New version: Web3 v0.2.4

Registering package: Web3
Repository: https://github.com/lambda-mechanics/Web3.jl
Created by: @zot
Version: v0.2.4
Commit: 051f0b03a2a5d51903f4d0105939632ccc5b6379
Reviewed by: @zot
Reference: https://github.com/lambda-mechanics/Web3.jl/issues/4#issuecomment-627828488

This can be removed -- it was a mistake


gnomeExtensions.appindicator: 29 -> 30

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/gnome-shell-extension-appindicator/versions.
meta.description for gnomeExtensions.appindicator is: '"AppIndicator/KStatusNotifierItem support for GNOME Shell"'.
meta.homepage for gnomeExtensions.appindicator is: '"https://github.com/Ubuntu/gnome-shell-extension-appindicator"
Compare changes on GitHub

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 30 with grep in /nix/store/751m0kn1pc5xc65rw7hvnprr0zpy2jh1-gnome-shell-extension-appindicator-30

directory tree listing: https://gist.github.com/6c308464bde3e99dc401f460b6944a4a

du listing: https://gist.github.com/d8894d044b7acb25c27e07e8ddc232de

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

3 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
gnomeExtensions.appindicator

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/751m0kn1pc5xc65rw7hvnprr0zpy2jh1-gnome-shell-extension-appindicator-30 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A gnomeExtensions.appindicator https://github.com/r-ryantm/nixpkgs/archive/89f0ec1853902914fd2160bbfcac68d48cf4495b.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/751m0kn1pc5xc65rw7hvnprr0zpy2jh1-gnome-shell-extension-appindicator-30
ls -la /nix/store/751m0kn1pc5xc65rw7hvnprr0zpy2jh1-gnome-shell-extension-appindicator-30/bin

cc @jonafato for testing.

This bumps the requirements to GNOME Shell 3.34:
https://github.com/Ubuntu/gnome-shell-extension-appindicator/compare/v29...v30

Fixed in https://github.com/NixOS/nixpkgs/pull/68608


Refactor for dryer code and move format logic to util.py

Refactor reference_repository to lessen code repetition.
Move Inproceedings formatting logic to util.py.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 12.50000% with 7 lines in your changes missing coverage. Please review.

Files with missing lines
Patch %
Lines

src/util.py
12.50%
7 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files with missing lines
Coverage Δ

src/util.py
84.61% <12.50%> (-13.12%)
:arrow_down:

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests


I wonder if it wouldn't be better/easier to maintain in the future if instead of having different items in localStorage, we have one object containing all

          I wonder if it wouldn't be better/easier to maintain in the future if instead of having different items in localStorage, we have one object containing all

So instead of having'accesskey' , 'secretkey' , 'neo4jconnection' etc we only have one item : 'nameOfYourApp' which would be an object like nameOfYourApp: {s3AccessKey: 'xxx', s3SecretKey: 'yyy', neo4jConnection: {uri...}, etc...}
This is how we tend to usually do it in other Neo4j apps I believe
Originally posted by @msenechal in https://github.com/neo4j-labs/llm-graph-builder/pull/77#discussion_r1508866030

@prakriti-solankey


make AST.pick correctly handle key renames

Type

[ ] Refactor
[ ] Feature
[x] Bug Fix
[ ] Optimization
[ ] Documentation Update

Related

Closes #2510

It looks like using the new name for the key is explicitly dis-allowed.  Is the reasoning for this that there is no way to determine which key the new key was renamed from in the type signature?
I think that in almost every case, if a developer has chosen to rename a key they expect to refer to it that way from then on, so this is really confusing. if after seeing that it doesn't typecheck and they have to use the old name, I expect that they are likely to be suspicious that it is a bug rather than an intentional descision because it is so counter-intuitive.
const someSchema = S.struct({
  a: S.propertySignature(S.string).pipe(S.fromKey('b')),
  b: S.number,
})

const schema = pipe(
  someSchema,
  S.omit('a') // <-- Seems like the expected usage
)

this schema is illegal and raises a Duplicate property signature "b" error
const someSchema = S.struct({
  a: S.propertySignature(S.string).pipe(S.fromKey("b")),
  b: S.number
})

let's change S.fromKey("b") to S.fromKey("c")
import * as S from "@effect/schema/Schema"

const opaque = S.struct({
  a: S.propertySignature(S.string).pipe(S.fromKey("c")),
  b: S.number
})

/*
const schema: S.Schema<{
    readonly a: string;
    readonly b: number;
}, {
    readonly c: string;
    readonly b: number;
}, never>
*/
const schema = S.asSchema(opaque)

const p = schema.pipe(S.omit("a"))

what do you expect p to look like?

let's change S.fromKey("b") to S.fromKey("c")
Yes, sorry. Made an error when simplifying from a local test.

what do you expect p to look like?
I think I'd expect:

const p = schema.pipe(S.omit("a"))
type p = S.Schema<{ readonly b: number; }, { readonly b: number; }, never>

const q = schema.pipe(S.pick("a"))
type q = S.Schema<{ readonly a: number; }, { readonly c: number; }, never>

That would be possible at runtime (since the underlying ast still has all the information), but it's a problem at the type-level as there's nothing anymore linking the a prop with the c prop.

I wonder if it is possible to create some kind of sentinal type:
type opaque = S.Schema<{
  readonly a: string;
  readonly b: number;
}, {
  readonly c: Renamed<'c', 'a'>;
  readonly b: number;
}, never>

// S.Schema.Encoded<opaque>
type opaqueEncoded = {
  readonly c: string;
  readonly b: number;
}

// S.Schema.Type<opaque>
type opaqueEncoded = {
  readonly a: string;
  readonly b: number;
}

yeah it might be possible, but it complicates things and I'm not sure it's worth it, when working with structs I would suggest the following workaround
import * as S from "@effect/schema/Schema"
import { omit, pick } from "effect/Struct"

const schema = S.struct({
  a: S.propertySignature(S.string).pipe(S.fromKey("c")),
  b: S.number
})

const p = S.struct(omit(schema.fields, "a"))

const q = S.struct(pick(schema.fields, "a"))


Support renaming metrics

Originally reported at https://github.com/prometheus/prometheus/issues/8579
Proposal
In projects like Kubernetes, we have thousands of contributors and metrics, and hence it is common for metrics that end users rely on to be created inconsistently. It is very difficult and disruptive to standardize/normalize metrics right now as there is no means of renaming a metric in the open metric format. To work around this, we follow a multi-release deprecation cycle for end users to update all their use cases. This is extremely painful for both the development cycle and end users as it currently takes 3 full releases just to rename a metric: 2 overlapping releases supporting both metric names, 1 additional release for removal. Hence, there is a strong disincentive to fix metric naming issues, even if they would provide an improved user experience, because there is so much work and technical overhead in proportion to the benefits.
It would be much improved experience if there was a means of renaming metrics, so clients could update the metric names to something more reasonable while not breaking the world.
If an exported metric looks like
# HELP go_goroutines Number of goroutines that currently exist.
# TYPE go_goroutines gauge
go_goroutines 42

A renamed metric could perhaps look like
# HELP not_go_goroutines Number of goroutines that currently exist.
# TYPE not_go_goroutines gauge
# ALIAS not_go_goroutines go_goroutines
not_go_goroutines 42

(ht @RichiH https://github.com/prometheus/prometheus/issues/8579#issuecomment-796769353 for the ALIAS suggestion)
Clients could continue to query for either go_goroutines or not_go_goroutines interchangeably so long as this metadata flag was present at scrape. We would no longer need to worry about the overhead of duplicating metrics during a deprecation period. (I am not attached to this particular implementation, just throwing something out there for discussion.)
Why not rename the timeseries client-side?
Recording rules must be explicitly configured by clients. Clients must therefore know that the rename happened. This is very manual and labour-intensive. I would like a mechanism at the scrape point or server side to be able to indicate a rename.

Clients could continue to query for either go_goroutines or not_go_goroutines interchangeably so long as this metadata flag was present at scrape. We would no longer need to worry about the overhead of duplicating metrics during a deprecation period

This is not the case, this would be basically the same net effect and overheads as duplicating the metrics - with the additional cost that the observable samples no longer match what's in the format, making life harder for all implementors and downstream users.
I don't think this is something that we should be specifying in OpenMetrics, particularly as we should be looking to standardise existing practices and I'm not aware of any monitoring system out there that does this.

Clients could continue to query for either go_goroutines or not_go_goroutines interchangeably so long as this metadata flag was present at scrape. We would no longer need to worry about the overhead of duplicating metrics during a deprecation period

This is not the case, this would be basically the same net effect and overheads as duplicating the metrics - with the additional cost that the observable samples no longer match what's in the format, making life harder for all implementors and downstream users.

Hi @brian-brazil, given what you've written here, I don't think you understand the use case.
Currently, here is how Kubernetes handles deprecation of metrics, say, if we add a new name.

Release 1: old_metric_name
Release 2: old_metric_name, new_metric_name
Release 3: old_metric_name, new_metric_name
Release 4: new_metric_name only

In order to rename metrics, we end up having to duplicate what gets served and scraped, because there is no mechanism to tell clients that the metric is the same but has been renamed. Hence, we could instead have:

Release 1: old_metric_name
Release 2: new_metric_name with name hint to old_metric name
Release 3: new_metric_name with name hint to old_metric name
Release 4: new_metric_name only

and thus avoid duplication of metrics in two releases.
It's unclear to me why having a rename capability would have the same net effect and overhead as duplicating a metric, as you'd only need to serve/scrape the metric once, as opposed to the duplication present above. The scrape client could then maintain a lookup table for the multiple names, which should have relatively low overhead.

given what you've written here, I don't think you understand the use case.

I understand the use case.

The scrape client could then maintain a lookup table for the multiple names, which should have relatively low overhead.

This is not the case. In TSDB terms it'd have essentially the same overhead as ingesting a duplicate metric, as it need to be considered per time-series so needs an entry in the index with all of those costs. Thus this has no real performance gain compared to a duplicate metric, and still doesn't help with updating dashboards etc. while breaking the invariant that what's in the exposition is what's in the database, thus leading to confusion.
If you think this would be useful, I'd suggest mentioning it in the help string while also duplicating and seeing how that works out in practice for end users.

This is not the case. In TSDB terms it'd have essentially the same overhead as ingesting a duplicate metric, as it need to be considered per time-series so needs an entry in the index with all of those costs. Thus this has no real performance gain compared to a duplicate metric, and still doesn't help with updating dashboards etc. while breaking the invariant that what's in the exposition is what's in the database, thus leading to confusion.

That sounds like an architectural/implementation issue to me, rather than technical infeasibility.
Furthermore, performance is not the only overhead to consider, because the current situation already suffers from the performance overhead of having two timeseries. We must also consider the human costs in expecting end users to directly be responsible for taking action on all metric renames.

If you think this would be useful, I'd suggest mentioning it in the help string while also duplicating and seeing how that works out in practice for end users.

I don't think this is sufficient for the Kubernetes use case as we have thousands of metrics. Adding it to HELP text would require users to manually look at metrics, and is no different than the status quo, where renaming burdens are pushed directly on sysadmins. Adding support for automatic relabelling means that a user does not have to think about this.

We must also consider the human costs in expecting end users to directly be responsible for taking action on all metric renames.

Your proposal doesn't change this, end users still need to rename everything by release 4. Accordingly I think the tooling around this is where you should focus investigation into the utility of this feature.

Would really be nice to support something like # ALIAS. Prometheus exporters suffer sometimes from quiet inconsistent metrics naming. Supporting aliases would help to stimulate cleaning up metric names.
Version 0.1:
# TYPE app_unicorn counter
# HELP app_unicorn How many unicorns were spotted.
app_unicorn 12

Version 0.2:
# TYPE app_unicorns counter
# HELP app_unicorns How many unicorns were spotted.
# ALIAS app_unicorns app_unicorn
app_unicorns 12

Version 1.0:
# TYPE app_unicorns_total counter
# HELP app_unicorns_total How many unicorns were spotted.
# ALIAS app_unicorns_total app_unicorns app_unicorn
app_unicorns_total 12

If e.g. Prometheus recorded app_unicorn for some months from a Version 0.1 exporter which was updated to Version 1.0, it would check for ALIASes and rename all app_unicorn in its database to the new app_unicorns_total name. Another idea would be to not rename it in the database, but just return the same for app_unicorn, app_unicorns and app_unicorns_total queries.
That would of course, only work if you use a (e.g.) Prometheus version which already supports this feature. The time between might be pretty annoying and confusing (e.g. there are already exporters using this feature, but you did not update Prometheus for a year).

Currently running into this issue because the dotnet library OpenTelemetry.Instrumentation.Runtime renamed a bunch of their metrics between versions 1.9.0 and 1.10.0. If there is a solution (even just as a workaround), I'd appreciate pointers in the right direction.


Move most utils and synthetic traits into core

Motivation and Context
As part of refactoring more code into the core module, this PR:

Moves most of the util package from codegen-client into codegen-core
Moves the synthetic traits into codegen-core
Consolidates duplicated RustTypesTest files
Corrects lang -> rustlang package name in codegen-client tests
Moves letIf from SymbolVisitor into its own file in codegen-core

The Synthetics util was left in codegen-client since its unit test requires testutil, and testutil requires dozens more files from codegen-client. Pulling it in would easily quadruple the size of this PR.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

It looks like Writable.kt and a few other modules have not been moved from the rustlang folder in client to core. Is this intended?

Should we move everything in the rustlang folder into core?

Yes, we should. Not in this PR though :smile: I'm trying to keep the changes smaller and easier to review. I attempted to move rustlang, but that ended up requiring a lot of smithy as well, so I decided to just stick with util for this PR.


[SPARK-41405][SQL] Centralize the column resolution logic

What changes were proposed in this pull request?

This PR is a major refactor of how Spark resolves columns. Today, the column resolution logic is placed in several rules, which makes it hard to understand. It's also very fragile to maintain the resolution precedence, as you have to carefully deal with the interactions between these rules.
This PR centralizes the column resolution logic into a single rule: the existing ResolveReferences rule, so that we no longer need to worry about the interactions between multiple rules. The detailed resolution precedence is also documented.
Why are the changes needed?

code cleanup
Does this PR introduce any user-facing change?

no
How was this patch tested?

existing tests

cc @viirya @allisonwang-db @MaxGekk

Yes, I've updated the PR description to make it clear.

@viirya can you take another look when you have time? thanks!

I will take another look today.

The last commit is just a minor code simplification.

thanks for review, merging to master!

Sorry for missing this earlier, late LGTM. Changes like this are moving in a good direction to move analysis logic closer to one pass. Ideally we could e.g. start making ResolveReferences immediately return an error if any unresolved reference could not be resolved, rather than waiting later until CheckAnalysis. We can make such improvements iteratively if we wish.


allow dynamic version

Name is the only field than cannot be dynamic: https://peps.python.org/pep-0621/#name

Version cannot be Dynamic according to PEP 641. See https://packaging.python.org/en/latest/specifications/core-metadata/#version and https://packaging.python.org/en/latest/specifications/core-metadata/#dynamic-multiple-use.
I think you are confusing Version and Dynamic in the core metadata with version and dynamic in pyproject.toml from PEP 621. Dynamic in the core metadata means a wheel metadata field is allowed to be computed when building from an SDist, which is not allowed for version! (It's also a metadata 2.2 feature, which wasn't yet very well supported by PyPI tooling last I checked).

Huh. I remain confused.

We absolutely do support version in the dynamic field in the pyproject.toml.

I disagree 😏.
This script, per your README.md usage:
import tomllib
from pyproject_metadata import StandardMetadata

parsed_pyproject = tomllib.load(open("pyproject.toml", "rb"))
metadata = StandardMetadata.from_pyproject(parsed_pyproject)
pkg_info = metadata.as_rfc822()
print(str(pkg_info))

Run against main:
Traceback (most recent call last):
  File "/home/arthur/wrk/python-pyproject-metadata/test.py", line 6, in <module>
    pkg_info = metadata.as_rfc822()
               ^^^^^^^^^^^^^^^^^^^^
  File "/home/arthur/wrk/python-pyproject-metadata/pyproject_metadata/__init__.py", line 264, in as_rfc822
    self.write_to_rfc822(message)
  File "/home/arthur/wrk/python-pyproject-metadata/pyproject_metadata/__init__.py", line 271, in write_to_rfc822
    raise ConfigurationError('Missing version field')
pyproject_metadata.ConfigurationError: Missing version field

Against this patch I get:
Metadata-Version: 2.2
Name: pyproject-metadata
Summary: PEP 621 metadata parsing
Home-page: https://github.com/FFY00/python-pyproject-metadata
Author-Email: Filipe Laíns<EMAIL_ADDRESS>Classifier: License :: OSI Approved :: MIT License
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3 :: Only
Classifier: Programming Language :: Python :: 3.7
Classifier: Programming Language :: Python :: 3.8
Classifier: Programming Language :: Python :: 3.9
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.11
Project-URL: Changelog, https://pyproject-metadata.readthedocs.io/en/stable/changelog.html
Project-URL: Homepage, https://github.com/FFY00/python-pyproject-metadata
Requires-Python: >=3.7
Requires-Dist: packaging>=19.0
Requires-Dist: furo>=2020.11.19b18; extra == "docs"
Requires-Dist: Jinja2<3.1; extra == "docs"
Requires-Dist: sphinx-autodoc-typehints>=1.10.0; extra == "docs"
Requires-Dist: sphinx~=3.0; extra == "docs"
Requires-Dist: pytest-cov[toml]>=2; extra == "test"
Requires-Dist: pytest>=6.2.4; extra == "test"
Requires-Dist: tomli>=1.0.0; python_version < "3.11" and extra == "test"
Provides-Extra: docs
Provides-Extra: test
Description-Content-Type: text/markdown
Dynamic: version

<snip>

Please read the specification I linked. It says:

A string containing the name of another core metadata field. The field names Name, Version, and Metadata-Version may not be specified in this field.

Your example has Dynamic: version, which, besides the miscapitilzation, is invalid via the above standard (Metadata-Version 2.2, from PEP 641).
You are confusing PEP 621 and pyproject.toml, which do allow a dynamic version, and Core Metadata and PEP 641, which do not allow a Dynamic Version. The version must be known when you make your SDist, since it's part of the file name. An SDist must make a matching versioned wheel. However, everything else (besides Name and of course the Metadata-Version) can be computed differently for the wheel from the SDist. For example, when you build the wheel, you might lock your binary dependency on numpy to >= 1.21, even though your SDist supports >=1.13. That's why something would be listed in Dynamic.
In your case, you just need to set the version (via however it is supposed to be computed) before producing the metadata if it's listed in dynamic in the pyproject.toml. Look at the implementations in sciit-build-core, pdm-backend, etc. They all use this project and they all support a dynamic PEP 621 versions (but of course, not a Dynamic Version - in fact, most projects still follow Metadata-Version 2.1, which doesn't have the Dynamic field).

My apologies. PEP 621 on the brain... Thank you for the detailed explanation.


Feature/community page

First pass at adding a community page.
It's not perfect and I am more than open to suggestions - I'm sure there's plenty of other links out we can add on here but I can't think of any off the top of my head

Hype!!!

Some build errors that I don't think are your fault, I'll fix them :)


Make KVM support optional

One think I'd like to look into further is if the Makefile $(COMPOSEBIN) target is getting executed even when the target file already exists, as it prints a message every time.

@jakogut the COMPOSEBIN stuff was reworked in the first 3 commits of https://github.com/balena-os/leviathan/pull/568. Might want to give it a try, just cherry-pick the commits in question and we can break them into a separate PR if needed.

@balena-ci rebase


Select same spec instance types from a specific instance type

It would be cool to select same spec instance types from a specific instance type. Like below.
ec2-instance-selector instance-type m5.xlarge
# OUTPUT, it can be list
m4.xlarge, m5.xlarge, m5a.xlarge, m5ad.xlarge, m5d.xlarge, m5dn.xlarge, m5n.xlarge

This feature is useful for dynamically creating CloudFormation template with AWS::EKS::Nodegroup.InstanceTypes. Now, I tried an unattractive way with AWS CLI...
CPUS=aws ec2 describe-instance-types --instance-types m5.xlarge --query 'InstanceTypes[].VCpuInfo.DefaultVCpus | [0]'
# Fetch other specs: MEMORY and  GPUS
ec2-instance-selector --vcpus=$CPUS --memory=$MEMORY --cpu-architecture=x86_64 --gpus $GPUS --burst-support=false

That's it! Thanks. This issue can be closed.


Remove extra foobar println on testing

Signed-off-by: John Howard<EMAIL_ADDRESS>@tiborvass This was introduced in #20697 but don't think it should have made it in and was a debugging statement.

LGTM

I just merged #20824 that also removed this line. This is no longer necessary. Thanks @jhowardmsft !
:heart_eyes_cat:

Cool


Dropdown items of navbar doesn't work well.

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[X] I have tried creating a repro with https://new.docusaurus.io.
[ ] I have read the console error message carefully (if applicable).

Description
I create a new docusaurus project and add a dropdown item for navbar.
And I find that the dropdown items are all actived on the navbar.
Reproducible demo
https://stackblitz.com/edit/github-rgqq1d?file=docusaurus.config.js
Steps to reproduce

Init the project with docusaurus v2.1.0
keep the sidebars config type as autogenerated ( I didn't modify it)
Add 1 dropdown item into navbar items

navbar: {
        // ...
        items: [
           // ...
            {
                type: "dropdown",
                position: "left",
                label: "dropdown",
                items: [
                    {
                        type: "doc",
                        docId: "tutorial-extras/translate-your-site",
                        label: "dropdown 1",
                    },
                    {
                        type: "doc",
                        docId: "tutorial-extras/manage-docs-versions",
                        label: "dropdown 2",
                    },
                ],
            },
            // ...
        ],
    },

Expected behavior
There should be only 1 navbar item actived in the dropdown menu.
Like this:

Actual behavior
All of the dropdown items being actived, including the doc navbar item.
If you add 2 dropdown items, all of the items in both dropdowns are actived.

Your environment

Public source code: https://stackblitz.com/edit/github-rgqq1d?file=docusaurus.config.js
Public site URL: -
Docusaurus version used: 2.1.0
Environment name and version (e.g. Chrome 89, Node.js 16.4):  Chrome 105.0.5195.102, Node.js v16.14.2
Operating system and version (e.g. Ubuntu 20.04.2 LTS): macOS Monterey 12.5.1

Self-service

[ ] I'd be willing to fix this bug myself.

can I try working on it?

Of course you can. And I am trying to find out what cause this at the moment...But unfortuanately I am still stuck here

can I try working on it?

Of course you can. And I am trying to find out what cause this at the moment...But unfortuanately I am still stuck here

A workable solution is setting type of  DropdownItems as default instead of  doc, the dropdown items perform as expect.
    items: [
-        {
-            type: "doc",
-            docId: "tutorial-extras/translate-your-site",
-            label: "dropdown 1",
-        },
-        {
-            type: "doc",
-            docId: "tutorial-extras/manage-docs-versions",
-            label: "dropdown 2",
-        },

+        {
+            label: "dropdown 1",
+            to: "tutorial-extras/translate-your-site"
+        },
+        {
+            label: "dropdown 1",
+            to: "tutorial-extras/manage-docs-versions"
+        }
    ],

The document of Navbar doc link mentions:

Navbar doc link
If you want to link to a specific doc, this special navbar item type will render the link to the doc of the provided docId. It will > get the class navbar__link--active as long as you browse a doc of the same sidebar.

So I wonder that maybe it is a feature ,but I found the website of React Native was using Docusaurus v2.0.1, but the dropdown items work well.

Even the source code shows that they using Navbar doc link like:
    {
      label: 'Development',
      type: 'dropdown',
      position: 'right',
      items: [
        {
          label: 'Guides',
          type: 'doc',
          docId: 'getting-started',
        },
        {
          label: 'Components',
          type: 'doc',
          docId: 'components-and-apis',
        },
      ],
    }

The different between mine and theirs config is that their documents are placed in the same dictionary.

Hey,
This issue is duplicate of https://github.com/facebook/docusaurus/issues/8018 reported by @juliusmarminge and is a problem in DocNavbarItem isActive() function, not directly related to being in a dropdown.
Currently the doc item gets highlighted if any of doc of the same sidebar if browsed.
For React-Native website the issue does not happen because the 4 docs in the dropdown belong to 4 distinct sidebars, while in your case the 2 docs belong to the same sidebar. If you isolate one doc in another sidebar you'll notice the problem will disappear.
I'll review soon the pending PR (https://github.com/facebook/docusaurus/pull/8079) and will get this fixed


Granthamblin0/tces 45 clt client table

Description
Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
Issue #
Type of change
Please delete options that are not relevant.

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

Checklist
Please delete options that are not applicable.

[x] My code follows the style guidelines of this project (required)
[x] I have performed a self-review of my code (required)
[x] I have linted and formatted my code (required)
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works

Just a reminder note, App.jsx will need to be reverted before merge


Enhancement

Gujarat total cases 122, 11 deaths
13 new cases in MP
9 new cases HP, Total 15
12 new cases in UP
Rajasthan total cases 210, 1 new death
Tamil nadu Death toll reaches 5
6 new cases in Punjab
2 new cases in Delhi
Source Indiatoday and ANI

https://telegra.ph/CoVID-19--India-Ops-03-24
Please follow the google form to report the cases.

Not relevant here


Ideas for improvement

First, let me say I'm a big fan and also love how you've open sourced the show notes. I have a couple suggestions for the community here to consider. If we agree these are good, I'm happy to do the work and raise a PR...

Would it make sense to add a Creative Commons license? Maybe CC-BY?
Some of the "cover art" images are really fun. For example, my favorite is this one here. What do you think about including these images on the respective show notes pages?

Would it make sense to add a Creative Commons license? Maybe CC-BY?

Sounds good. Would you be interested in a PR?

Some of the "cover art" images are really fun. For example, my favorite is this one here. What do you think about including these images on the respective show notes pages?

I'm loath to add more labor, minimal as it is. The images are available by downloading the YouTube video... does that suffice?

Sounds good. Would you be interested in a PR?

Yes, I'll open a PR.

I'm loath to add more labor, minimal as it is. The images are available by downloading the YouTube video... does that suffice?

That's fine.


How could I get an Object in callback

I want to get an obejct in below callback not int type, what should i do?
Override
public void onPositiveButtonClicked(int requestCode) {
}

You should probably create your own dialog extending BaseDialogFragment and define your own callbacks.


Float/double equals fixes

Please consider fix for (supposedly) rt_compare, which will fix failing in JS env test.
https://github.com/konsoletyper/teavm/compare/master...Ihromant:teavm:double-equals-fixes?expand=1#diff-82a57ed5fe3b9c9c8e7ff9af89119d3faf3fe8ba2a4519eaec3c203411540c09R137

First issue introduced in this commit is that $rt_compare fails when we are putting 0.0 and -0.0. It returns 0 when it needs to be 1. In java side this behavior is correct.

I don't touch this function because it seems that it is used alot in compilations/translations.

Plese, revert 'Fixed comparator in runtime.js'

I get it from posted question on codegolf stackexchange. https://codegolf.stackexchange.com/questions/265365/comparator-function-in-javascript#265366
Strangely, but it works and covers all cases in tests. If you wish so, I will revert it, but it seems to be performant enough, simple and correct.

Please, revert. If you want this particular change, we can discuss it later in a separate PR.


issue with adjusted rates breaking projected costs page identified

closes #91
If changes are made to transition rates, when the exit rate table is calculated for the projected costs page, this gives an error where two columns are meant to be made from a .str.split() and no split can occur. This error occurs when there are no rows of data to split (after removing all data except rows where children are leaving care).
I've temporarily popped a try/except block in there as this works as a fix, but I'm not sure if this is an actual long term solution. Also, I wonder if we might need to account for this in other instances if there's a chance we might be trying to split where there is no data to split. If we find a long term solution, it might make sense to handle this in another function and use it each time we do thsi split?

Just a reminder on this one - we want to add logic so that users won't be displayed an empty dataframe as in image below. I beleive the logic for this is already in the view/template, but looks like the if statement in the charts.py functions (for all rates tables) is in the wrong place to return None. Could you fix that on this branch please?

0aafec5
Hi @amynickolls

I think this is working as expected now, and I think I've understood what was asked. I was confused as there is now no exit rate table button for me to check if it has an empty dataframe in, but of course there is not, if it gets none, it doesn't make the button


⚠ TiendaEnLinea has degraded performance

In c254d20, TiendaEnLinea (https://www.fahorro.com/) experienced degraded performance:

HTTP code: 200
Response time: 5194 ms

Resolved: TiendaEnLinea performance has improved in 5b0b620.


Column == operator does not compare values with Nothing

Discord username
No response
What type of issue is this?
Permanent – Occurring repeatably
Is this issue blocking you from using Enso?

[ ] Yes, I can't use Enso because of this issue.

Is this a regression?

[ ] Yes, previous version of Enso did not have this issue.

What issue are you facing?
column == Nothing always returns a column filled with Nothings (see the screenshot)
Expected behaviour
Vectorized column == operator compare values with Nothing
How we can reproduce it?
Consider the following program (see the screenshot)
operator1 = Column.from_vector "Number" [Date.new 2022, Nothing]
operator2 = operator1 == Nothing

Screenshots or screencasts

Logs
No response
Enso Version
792cbc448
Browser or standalone distribution
Chromium
Browser Version or standalone distribution
113.0.5672.126
Operating System
Linux
Operating System Version
No response
Hardware you are using
No response

Agreed behaviour for == with Nothing is this.


Peer-Peer code review

** Well done Winnie;
you have done a very good job with this project .

Your code looks very well organized and professional

I think you could look into the color contrast of your UI and see if you could make it a bit brighter

You have done an amazing job overall
Well-done once again and happy coding!!

##GOOD JOB
Great job completing your project,

you used the classes well

you showed good understanding of webpack

Improvements

you can use more Es6 code especially arrow functions.