Prometheus pod is not able to pick up new PrometheusRule(CRD)

What did you do?
Deployed the Prometheus-Operator with helm from stable.  Have not changed any ruleSelector indent from values.yaml . Created our own PrometheusRules [CRDs]. They are  created/visible at cluster scope by browsing with kubectl. The custom one is the latest.
kubectl get prometheusrules -n monitoring
NAME                                                              AGE
monitoring-prometheus-oper-alertmanager.rules                     24h
monitoring-prometheus-oper-etcd                                   24h
monitoring-prometheus-oper-general.rules                          24h
monitoring-prometheus-oper-k8s.rules                              24h
monitoring-prometheus-oper-kube-apiserver.rules                   24h
monitoring-prometheus-oper-kube-prometheus-node-recording.rules   24h
monitoring-prometheus-oper-kubernetes-absent                      24h
monitoring-prometheus-oper-kubernetes-apps                        24h
monitoring-prometheus-oper-kubernetes-resources                   24h
monitoring-prometheus-oper-kubernetes-storage                     24h
monitoring-prometheus-oper-kubernetes-system                      24h
monitoring-prometheus-oper-node-exporter                          24h
monitoring-prometheus-oper-node-exporter.rules                    24h
monitoring-prometheus-oper-node-network                           24h
monitoring-prometheus-oper-node-time                              24h
monitoring-prometheus-oper-node.rules                             24h
monitoring-prometheus-oper-prometheus                             24h
monitoring-prometheus-oper-prometheus-operator                    24h
monitoring-prometheus-oper-customrules                               106m

I saw that prometheus pod is exposing 3 containers:

prometheus
rules-configmap-reloader
prometheus-config-reloader

The prometheus pod(1)  mounts a volume from a config-map. In that config map all the rules are stored. This config map does not take under consideration the new rule, and sticks with the previous one ( all CRDS without the latest one).
After applying the new CRD I am having a look at the logs from the rules-configmap-reloader and there are no logs:
kubectl logs prometheus-monitoring-prometheus-oper-prometheus-0 -n monitoring -c rules-configmap-reloader
[root@some_hostname centos]#

I decided to kill the pod with the idea that the deployment would recreate it and it would apply the new configuration, but again it's not working.
I was not able to find any information anywhere else regarding this. From the source code I could see a function like:
// makeRulesConfigMaps takes a Prometheus configuration and rule files and
// returns a list of Kubernetes ConfigMaps to be later on mounted into the
// Prometheus instance.
// If the total size of rule files exceeds the Kubernetes ConfigMap limit,
// they are split up via the simple first-fit [1] bin packing algorithm. In the
// future this can be replaced by a more sophisticated algorithm, but for now
// simplicity should be sufficient.
// [1] https://en.wikipedia.org/wiki/Bin_packing_problem#First-fit_algorithm
func makeRulesConfigMaps(p *monitoringv1.Prometheus, ruleFiles map[string]string) ([]v1.ConfigMap, error) {

I am just wondering if this functionality is actually implemented ( I saw the Changelog 0.20.0 / 2018-06-05, where they are talking about migration paths, but I do not consider this a migration , but an update. I feel like that this change should be in the hands of the Prometheus-Operator controller ) or if there's something with my set up that does not allow me to do that ?
Any help/guidance/hint would be highly appreciated.
Did you expect to see some different?
My expectation is that the Prometheus-Operator controller would tigger a workflow that ends up with an updated config-map, so that I could see my new alert/rule.
Environment

Prometheus Operator version:
	Chart: prometheus-operator-7.2.0   App Version: 0.32.0

Kubernetes version information:
kubectl version Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.2", GitCommit:"c97fe5036ef3df2967d086711e6c0c405941e14b", GitTreeState:"clean", BuildDate:"2019-10-15T19:18:23Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.6-eks-5047ed", GitCommit:"5047edce664593832e9b889e447ac75ab104f527", GitTreeState:"clean", BuildDate:"2019-08-21T22:32:40Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:
AWS Managed ( EKS )

Anything else we need to know?:
The Prometheus Operator supports multiple PrometheusRules (which are Custom Resources) that you can deploy to your cluster and the Operator then discovers and configures.
https://github.com/coreos/prometheus-operator/issues/2720

Could you please post the prometheus object and a rules object that is not being loaded? I suspect you have a mismatch in the labels.
The prometheus.spec.ruleSelector and prometheus.spec.ruleNamespaceSelector should match the labels on the prometheusRules you are creating. See the API doc here for more info.

Additionally linting the PrometheusRule object would be helpful. You can install the linting tool with:
go get -u -v https://github.com/coreos/prometheus-operator/tree/master/cmd/lint

then you can run the linter with just:
lint <filename>

if the exit code is 0 then all is good.

@vsliouniaev @brancz  thanks for the support and the quick feedback. I am really appreciating that two core commiters are reacting so quickly, this is a great sign for the project :)
It was indeed the ruleSelector, however what caused the confusion is that during the initial installation all the rules created with this script https://github.com/helm/charts/blob/master/stable/prometheus-operator/hack/sync_prometheus_rules.py expose those labels:

  prometheus: k8s
  role: alert-rules

Also in this example the labels are indeed again the  same => https://github.com/coreos/kube-prometheus/blob/master/manifests/prometheus-rules.yaml#L1-L9
I was having the expectation that those must be shared between all alerts. In my case the real default labels are:
  App:      prometheus-operator
  Release:  monitoring


Pinned Doodba Version incompatible with copier update

Not sure what you can do to be honest, maybe versioning of some kind for copier, but changing env vars and vscode configs while not respecting a pinned version using prior values is going to cause problems. But best to know I suppose

I don't understand you, could you be more specific?

We had a case where we had to pin a v11 config because the underlying build changed underlying OS and would no longer build due to exotic dependencies.
Then we ran copier update, which changed the env vars - specifically in relation to PTVSD and DEBUGPY while removing the .env file. The debug configs for VSCode also changed, but the old pinned version did not have the new dependencies.
As I say not much you can do, its fine, we worked it out.

OK, well... in case you keep the same odoo_version for the template when updating, if you changed later manually the line produced by this one, the smart update diff should leave the same one you had: https://github.com/Tecnativa/doodba-copier-template/blob/4b85e88858b2e56aa1be25adacdd5d9953897198/odoo/Dockerfile#L2
In case you're updating the odoo_version (from 11 to 12 for example), then a conflict should happen and you should have a Dockerfile.rej file there, which you should review manually, just like you would do with any other git conflict.
Pinning is something that's not on our rodamap for the template, apart from the fact that you can rely on copier's smart update diff as said. I think we can safely close this one.
Thanks for the report anyway :blush:


Mdl-dialog: cursor is not visible with focus on mdl-textfield which is exist in mdl-dialog's form control

Mdl-dialog: cursor is not visible with focus on mdl-textfield which is exist in mdl-dialog's form control
By adding is-focused class to mdl-textfield on opening mdl-dialog, then it focus on that textfield but cursor is not showing in mdl-textfield.
This behavior is same as on every browser, OS. I have tries autofocus but not working
Am I missing anything here, Please suggest me if anyone go through the same issue?

@UmeshRajani In case you just want autofocus, use autofocus directly. Maybe I didn't understand your issue.


Fix cache and hanging subscriptions

Fixes NIP-181
Fixes NIP-190
Added ops controller
Added check for 12week min left in message pack
Cleans CDR/CSR > 1 week

@larubbio, are there any issues with reporting if we clean out old CDRs & CSRs daily?

You also need to add the /ops/ endpoint to securityRules.json don't you think?

yup, missed updating security rules. fixed


fixing mmdet installation

Hello,
I encountered the same problem with the previous two issues (#6 and #7) and have identified the cause.

The mmdet package should be installed from the repository, specifically from the 2.x branch, because installing mmdet via mim does not provide the necessary configuration files.
The detector weight provided in evaluation/download_models.sh is intended for mmdet version 3.0, making it incompatible with the code that requires mmdet version 2.x.

To address this, I made some changes and submitted a pull request that includes modifications to README.md and evaluation/download_models.sh.
Please review the changes.
Thank you.

Hi @8uos, thank you so much for the fix. Did you face any issues with mmcv e.g., RuntimeError: ms_deform_attn_impl_forward: implementation for device cuda:0 not found? If not, could you please provide directions how you installed mmcv? I tried both pip install and building from the source, nothing works.

Hi @shaswati1.
Actually, I did not build the environment from environment.yml because it contains too many irrelevant packages.
I directly installed only the packages I needed (they were clip-benchmark open-clip-torch transformers openmim) using pip.
I suspect that both environment.yml and the mmdetection repository install mmcv, which causes a version conflict.

But when I just install mmdet, it say's
ModuleNotFoundError: No module named 'mmcv'

I checked it again and found I missed the installation part of MMCV.
You can install the correct versions of mmcv and mmengine with this command:
pip install -U openmim; mim install mmengine mmcv-full==1.7.2
The full installation command would be:
pip install -U openmim
mim install mmengine mmcv-full==1.7.2
git clone https://github.com/open-mmlab/mmdetection.git
cd mmdetection; git checkout 2.x
pip install -v -e .

Thanks once again. Could you please give me the version of mmengine and mmdet that is installed in your geneval environment?

Sure.

Here is my torch version.

Thanks a lot :)  I'll give it a try!

@8uos, thanks once again! Finally, it worked!! It seems changing the cuda version was the key!


Optional "improvements" to glove code

Changes like these were made in the process of debugging so that I could understand what was going on.  They are optional and I don't expect all of them to pass muster.  They are somewhat independent and in order to be cherry picked.

Looks nice, but there are some conflicts.


Add first tests mainly related to the home page

Hi guys.
First of all, as I said via mail to Jozef, I really like the idea behind this project.
Since I saw that fedora-software is currently missing automated tests, I've started writing some code.
The approach I'm following is that we may call "outside-in". The steps are the following:

Write a sort of storyline by user's point of view, starting from the main pages and details.
Write functional - also called acceptance - tests in order to simulate the user's interaction.
Write unit tests, in order to tests the behavior of the software on a lower level.

Functional tests are located on "functional_tests/test_base.py" whereas the most appropriate place for unit tests is "fedora_software/tests.py".
We might split them and organize the folder following features nor GitHub's issues, but it's not required at this point, since the TestCases are few.
For now, I've written these tests:

Steps for Selenium in order to open the home page.
A functional test in order to test if the Featured Apps appear on the home page.
Some unit tests related to HomeView, FeaturedApp and Component

I know the coverage is still low, but this is a starting point and I hope to write other cases soon.
In order to run the full testing suite, you should follow these steps:

Install firefox and selenium
Run Django's Webserver on the standard port (8000)
python manage.py test

Have a nice week-end

Giulio
GitHub: pigjuliux
FAS: juliuxpigface
Member of: FedoraQA

Thanks for contribution. I have to explore your code yet in detail, but it looks promising.


Almost zero documentation for the training modules API

Hello,
I would like to try out this package but realize there is close to zero documentation in the official 'readthedocs'/API for the train classes. Is this actually the official documentation? None of the parameters are defined, the differences between functions are undefined, and almost nothing is written here. Please correct me if this is not the official documentation. It's unclear how to even use the train modules
https://ncem.readthedocs.io/en/latest/readme.html

Hi @arunchakra,
we are currently in the process of enhancing our documentation to follow more closely scverse packages so it's easier to use the package. I just released a new readthedocs design and more function information and new tutorials will follow in the upcoming weeks. Please be patient and thanks for your interest in using ncem!

Looking forward! A very simple getting started tutorial from anndata for the current version would be great.
None of the tutorials from ncem_tutorials seem to work for me
I managed to get through https://github.com/theislab/spatial_scog_workshop_2022/blob/main/ncem/tutorial_ncem.ipynb by fixing several function bugs until getting to function get_sender_receiver_effects

Any updates? I still can't find more detailed explanations of the parameters in the documentation. This package is very interesting, but it's hard to use properly without more documentation.


support for nested form-params in req options

e.g.
@(http/post "/foo/bar"
   { :form-params {:description "FIRSTNAME LASTNAME"}}))

https://github.com/http-kit/http-kit/blob/master/src/org/httpkit/client.clj#L37-L45

Interesting, I've tried to emulate all the relevant behaviors from clj-http, I'll look into why this isn't in there already.

suppose you could automatically coerce :body according to content-type header

this should be addressed by https://github.com/ztellman/aleph/commit/3de504c187dc98a3f5b29485858faabf987477b3 and the other related commits

@ztellman thnx!


go get -u could not get latest minor or patch releases

go get -u github.com/mritd/mmh aways download v1.3.4 but latest version is v1.3.5.

But it works fine when i remove GOPROXY.

@fitzix  Can you provide the import path?

@fitzix Can you provide the import path?

github.com/fitzix/proxy-test I have released several versions for testing, but it only downloads v0.0.1.

fixed and deployed online:
# go get github.com/fitzix/proxy-test@latest
go: finding github.com/fitzix/proxy-test v0.0.3
go: downloading github.com/fitzix/proxy-test v0.0.3

It works fine now

Thanks for your feedback.


karpenter Pod fails to Start -The specified queue does not exist.

Description
Observed Behavior:
Pod fails to start - panic: AWS.SimpleQueueService.NonExistentQueue: The specified queue does not exist.
Expected Behavior:
Pod runs
Reproduction Steps (Please include YAML):
Follow this documentation.
https://karpenter.sh/docs/getting-started/migrating-from-cas/
Doc mentions about setting a Interruption Queue -
--set "settings.interruptionQueue=${CLUSTER_NAME}"
But the policy for the service account - doesn't mention anything to do with Queue (sqs permissions).
** Extra info **
A service account is created -
# Source: karpenter/templates/serviceaccount.yaml
apiVersion: v1
kind: ServiceAccount
metadata:
  name: karpenter
  namespace: kube-system
  labels:
    helm.sh/chart: karpenter-1.0.7
    app.kubernetes.io/name: karpenter
    app.kubernetes.io/instance: karpenter
    app.kubernetes.io/version: "1.0.7"
    app.kubernetes.io/managed-by: Helm
  annotations:
    eks.amazonaws.com/role-arn: arn:aws:iam::797036517683:role/KarpenterControllerRole-tajawal-dev

Deployment refers to queue
            - name: INTERRUPTION_QUEUE
            value: "tajawal-dev"

Policy attached to the Service Account is copied from documentation
cat << EOF > controller-trust-policy.json
{
 "Version": "2012-10-17",
 "Statement": [
     {
         "Effect": "Allow",
         "Principal": {
             "Federated": "arn:${AWS_PARTITION}:iam::${AWS_ACCOUNT_ID}:oidc-provider/${OIDC_ENDPOINT#*//}"
         },
         "Action": "sts:AssumeRoleWithWebIdentity",
         "Condition": {
             "StringEquals": {
                 "${OIDC_ENDPOINT#*//}:aud": "sts.amazonaws.com",
                 "${OIDC_ENDPOINT#*//}:sub": "system:serviceaccount:${KARPENTER_NAMESPACE}:karpenter"
             }
         }
     }
 ]
}
EOF

aws iam create-role --role-name "KarpenterControllerRole-${CLUSTER_NAME}" \
 --assume-role-policy-document file://controller-trust-policy.json

cat << EOF > controller-policy.json
{
 "Statement": [
     {
         "Action": [
             "ssm:GetParameter",
             "ec2:DescribeImages",
             "ec2:RunInstances",
             "ec2:DescribeSubnets",
             "ec2:DescribeSecurityGroups",
             "ec2:DescribeLaunchTemplates",
             "ec2:DescribeInstances",
             "ec2:DescribeInstanceTypes",
             "ec2:DescribeInstanceTypeOfferings",
             "ec2:DeleteLaunchTemplate",
             "ec2:CreateTags",
             "ec2:CreateLaunchTemplate",
             "ec2:CreateFleet",
             "ec2:DescribeSpotPriceHistory",
             "pricing:GetProducts"
         ],
         "Effect": "Allow",
         "Resource": "*",
         "Sid": "Karpenter"
     },
     {
         "Action": "ec2:TerminateInstances",
         "Condition": {
             "StringLike": {
                 "ec2:ResourceTag/karpenter.sh/nodepool": "*"
             }
         },
         "Effect": "Allow",
         "Resource": "*",
         "Sid": "ConditionalEC2Termination"
     },
     {
         "Effect": "Allow",
         "Action": "iam:PassRole",
         "Resource": "arn:${AWS_PARTITION}:iam::${AWS_ACCOUNT_ID}:role/KarpenterNodeRole-${CLUSTER_NAME}",
         "Sid": "PassNodeIAMRole"
     },
     {
         "Effect": "Allow",
         "Action": "eks:DescribeCluster",
         "Resource": "arn:${AWS_PARTITION}:eks:${AWS_REGION}:${AWS_ACCOUNT_ID}:cluster/${CLUSTER_NAME}",
         "Sid": "EKSClusterEndpointLookup"
     },
     {
         "Sid": "AllowScopedInstanceProfileCreationActions",
         "Effect": "Allow",
         "Resource": "*",
         "Action": [
         "iam:CreateInstanceProfile"
         ],
         "Condition": {
         "StringEquals": {
             "aws:RequestTag/kubernetes.io/cluster/${CLUSTER_NAME}": "owned",
             "aws:RequestTag/topology.kubernetes.io/region": "${AWS_REGION}"
         },
         "StringLike": {
             "aws:RequestTag/karpenter.k8s.aws/ec2nodeclass": "*"
         }
         }
     },
     {
         "Sid": "AllowScopedInstanceProfileTagActions",
         "Effect": "Allow",
         "Resource": "*",
         "Action": [
         "iam:TagInstanceProfile"
         ],
         "Condition": {
         "StringEquals": {
             "aws:ResourceTag/kubernetes.io/cluster/${CLUSTER_NAME}": "owned",
             "aws:ResourceTag/topology.kubernetes.io/region": "${AWS_REGION}",
             "aws:RequestTag/kubernetes.io/cluster/${CLUSTER_NAME}": "owned",
             "aws:RequestTag/topology.kubernetes.io/region": "${AWS_REGION}"
         },
         "StringLike": {
             "aws:ResourceTag/karpenter.k8s.aws/ec2nodeclass": "*",
             "aws:RequestTag/karpenter.k8s.aws/ec2nodeclass": "*"
         }
         }
     },
     {
         "Sid": "AllowScopedInstanceProfileActions",
         "Effect": "Allow",
         "Resource": "*",
         "Action": [
         "iam:AddRoleToInstanceProfile",
         "iam:RemoveRoleFromInstanceProfile",
         "iam:DeleteInstanceProfile"
         ],
         "Condition": {
         "StringEquals": {
             "aws:ResourceTag/kubernetes.io/cluster/${CLUSTER_NAME}": "owned",
             "aws:ResourceTag/topology.kubernetes.io/region": "${AWS_REGION}"
         },
         "StringLike": {
             "aws:ResourceTag/karpenter.k8s.aws/ec2nodeclass": "*"
         }
         }
     },
     {
         "Sid": "AllowInstanceProfileReadActions",
         "Effect": "Allow",
         "Resource": "*",
         "Action": "iam:GetInstanceProfile"
     }
 ],
 "Version": "2012-10-17"
}
EOF

aws iam put-role-policy --role-name "KarpenterControllerRole-${CLUSTER_NAME}" \
 --policy-name "KarpenterControllerPolicy-${CLUSTER_NAME}" \
 --policy-document file://controller-policy.json

This issue comment mentions some SQS permissions -
https://github.com/aws/karpenter-provider-aws/issues/3185#issuecomment-1380648503
      - Effect: Allow
        Action:
          # Write Operations
          - sqs:DeleteMessage
          # Read Operations
          - sqs:GetQueueAttributes
          - sqs:GetQueueUrl
          - sqs:ReceiveMessage
        Resource: !GetAtt KarpenterInterruptionQueue.Arn

Versions:

Chart Version:
Kubernetes Version (kubectl version): 1.29

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

I could fix it by stitching things from other repos, issue comments and documentation -
SQS stack needs to be present - Ref - https://github.com/aws/karpenter-provider-aws/blob/main/website/content/en/docs/getting-started/getting-started-with-karpenter/cloudformation.yaml
SQS permission needs to be given to Karpenter pod's service Account -
Ref- https://github.com/aws/karpenter-provider-aws/issues/3185#issuecomment-1380648503
If this can be added to documentation or the --set "settings.interruptionQueue=${CLUSTER_NAME}" \ removed
That will help. Thanks

i have the same issue

This prevented errors related to the non-existent interruption queue and allowed the pod to start as expected

If you don't deploy the queue through the stack, then you are going to have to disable interruption handling by not specifying the queue. I'm going to close this out since this is AWS-specific. If you think that this is still an issue, please open a new issue against: https://github.com/aws/karpenter-provider-aws/issues


__cxx

using namespace std;
std:: can`t appear __cxx11

Can you give more info please? Minimal example, config and logs.


Update Pulsar client to 2.1.0

Since Pulsar has already released, would like to update Pulsar client to latest verison

@jiazhai @merlimat @sijie IMO, it's time to separate the benchmark API from the project. I would like to call for discussion in the next week, hoping to see you.

@jiazhai welcome to pr it

close this, since it is already in 2.1.1


2.6.x

ok

We can't accept such big PR without any description. Please reopen it when you think it's ready


Add functionality to generate and save Payment QR codes as a file

As a user, allow me to generate and save a QR code that the Hotspot App can scan and populate for common and frequent payment transactions.
Scanning a QR code instead of typing can reduce errors. Adding a nickname to generated QR codes that can be saved as a file will enable those with frequent payments (i.e patrons, rev-share) allows users to identify recipients by a common name instead of a string of characters.
This is a good stop-gap for the address book feature requested for the Hotspot App, and starts the initial work to enable staking and delegating.
Recipient: this field will be b58-validated address. add a check to confirm this address is compatible with Helium. This is a required field.
Nickname: this field will be a user-supplied string. do not allow scripts or special characters. alphanumeric only. not required. Add a character limit of 120 chars.
HNT amount: this field will be user-supplied. numbers only, decimals allowed. not required.
Once these fields are populated, a user can click "Create QR code", with a QR code appearing in the right panel. The QR code will encode information entered on the left panel.
Save As .. will open a system dialog to save the QR code as an image file.
More details can be found in Figma.

interesting idea. Would be willing to assist the development of this functionality, if anyone would like to assign me or collaborate with me to add this feature. l

interesting idea. Would be willing to assist the development of this functionality, if anyone would like to assign me or collaborate with me to add this feature. l


P2P connection support

Current PeerJS transport does not work with more than 2 peers due to Interest loop.
Actually, the Forwarder class of NDNts is not a real forwarder at all, but simply a demultiplexer.
https://github.com/zjkmxy/ndn-workspace-solid/blob/dbb3c470b1fdc62c2a52a3cc78889a64686ebdd8/src/adaptors/peerjs-transport.ts#L8
To correctly use PeerJS transport without having Interest loop, we need to do one of the following:

Avoid Interests' being forwarded. (Recommended by the professor)
Drop in some quick fix to the NDNts's "forwarder" so that it can surpress unsatisfied Interests
Compile an in-browser forwarder using WASM.

Varun has implemented a face to support WebSocket broadcast: https://github.com/pulsejet/ndnts-ws
It may also be ported.

Drop in some quick fix to the NDNts's "forwarder" so that it can surpress unsatisfied Interests

NDNts probably will never have a full featured forwarder as default, because it would significantly increase code size.
I'd see whether I can provide hooks to customize certain parts of the forwarding logic.

Avoid Interests' being forwarded

NDNts can potentially offer an Interest forwarding filter option or FIB lookup hook.
Sample API would look like one of these:
Forwarder.create({
  canForwardInterest(inFace: FwFace, outFace: FwFace, pkt: FwPacket<Interest>): boolean {
    return true;
  },
});

Forwarder.create({
  forwardInterest(inFace: FwFace, pkt: FwPacket<Interest>, lookupFIB: () => Iterable<FwFace>): Iterable<FwFace> {
    return lookupFIB();
  },
});

Let me know your thoughts.

Varun has implemented a face to support WebSocket broadcast: https://github.com/pulsejet/ndnts-ws

Browser side code copies each packet passing through the Forwarder to the WebSocket server; it does not correctly handle non-encodable messages such as RejectInterest and CancelInterest.
I don't see how it's related to PeerJS or loop prevention.

Browser side code copies each packet passing through the Forwarder to the WebSocket server; it does not correctly handle non-encodable messages such as RejectInterest and CancelInterest. I don't see how it's related to PeerJS or loop prevention.

@pulsejet
Sorry. I have not been working on this for a while and I'm not aware of current progress. Maybe Varun can give more details.

Yes I expect there to be issues. This is more of a quick hack to emulate a broadcast medium; probably much better ways to do this.

Compile an in-browser forwarder using WASM.

I'd consider this to be the ideal solution.

I'd consider this to be the ideal solution.

Now it is the time to pick up your old Rust NDN forwarder. (I'm joking)

No plan to fix this for now.
Maybe related: there was a NDN microforwarder in browser: 2nd-ndn-hackathon/firefox-micro-forwarder

Poster paper: https://conferences2.sigcomm.org/acm-icn/2016/proceedings/p201-shang.pdf


Write and publish more blogs to the Blogs Page

Description
Write and publish more blogs to the Blogs Page
Screenshots
No response

Hi, I want to contribute more blogs, but can you please tell me blogs on which topics are allowed?

yes I also want to contribute, please tells about the blog topics

assign me

Hi,
can you please assign it to me?

HI,
can you assign this to me ?

yes I also like to contribute, May I know about that what are the topics you like to add?

hi can you please assign this to me

Hey @SauravMukherjee44 I want to work on this issue plz assign it to me

@atul120212 @MayuriKolhe-2003  Go for it!


better setup instructions

e.g. tips for troubleshooting ocaml setup, creating a switch

added ocaml setup instructions to README


To separate unrelated code, the DOM scheduler should be split into another solution

The DOM scheduler could easily stand alone as a micro-package. This should be split away into a package of its own and referenced by this one.

The package for this now exists, the code in this module needs to be removed and replaced with that.


Add docker for backend and frontend

Well done, Stanislav.
I see you have more experience with Docker containers.
Take my approve!


AllowClear shoundn't open the box, no ?

When you click on close button, select value is cleared but the box is open.
This box should stay closed, no ?

This is a duplicate of https://github.com/select2/select2/issues/3320.


React-router history pushes / replaces not triggering webview events unless links are clicked twice

Bug description:

On Android, when navigating on our React web app, running inside a react-native-webview, no navigation events are triggered, unless you click the link twice.
Adding the workarounds previously found in Guide.md (shimming the history methods) works, but I was under the impression this shouldn't be necessary.
The page I'm working with doesn't use react-router directly but it uses the same underlying library (ReactTraining/history) and I can confirm the problem exists with react-router as well.
To Reproduce:

Load this codesandbox (it's one of the react-router demo pages): https://bnpsd.csb.app/ in a react-native-webview
Click around
Expected behavior:

Navigation events (like onNavigationStateChange) are called.
Environment:

OS: Android
OS version: 9 / 10
react-native version: 0.61.4
react-native-webview version: 8.0.3

Any updates on this?

I encounter the same problem, iOS is ok, but not Android.

me too

@ijasm It was in an older version of that file. I'm injecting this snipped of Javascript code:
const historyAPIShim = `
(function() {
    function wrap(fn) {
      return function wrapper() {
        var res = fn.apply(this, arguments);
        window.ReactNativeWebView.postMessage(
          '{"method": "historyChange"}'
        );
        return res;
      };
    }
    history.pushState = wrap(history.pushState);
    history.replaceState = wrap(history.replaceState);
    window.addEventListener("popstate", function() {
      window.ReactNativeWebView.postMessage(
        '{"method": "historyChange"}'
      );
    });
  })();
`;

@vascofg 's workaround is working but I was unable to capture title change(w/ react-helmet).
put code below to root element of web app(not in native) and use it from WebView.onMessage event.
  React.useEffect(() => {
    const titleElement = document.getElementsByTagName('title')[0];
    const documentElement = document.documentElement;

    function onElementChange(e: any) {
      const changedElement = e.target;

      if (changedElement === titleElement) {
        window.ReactNativeWebView.postMessage(
          JSON.stringify({
            method: 'titleChange',
            title: titleElement.innerText,
          }),
        );
      }
    }

    if (documentElement) {
      documentElement.addEventListener('DOMSubtreeModified', onElementChange);

      return () => {
        documentElement.removeEventListener(
          'DOMSubtreeModified',
          onElementChange,
        );
      };
    }
  });

As I can see in source code it works on iOS because it injects similar shim js code into WebView.
I'm not sure why it's not on Android. I wonder Is it just not implemented or it worked without shim and broken on some environment?

This is still not fixed

Although this is an old thread, maybe it's helpful for others. It appears that onNavigationStateChange is not called on Android when the app uses history pushState and popState when navigating back in history. On iOS it is being called just fine.
I noticed that onLoadProgress is called in both platforms so what I did was to use both like this:
      onNavigationStateChange={(navState) => {
        // On Android if the page uses history pushState and popState,
        // onNavigationStateChange is not called but onLoadProgress does
        setCanGoBackInWebView(navState.canGoBack);
      }}
      onLoadProgress={(syntheticEvent) => {
        const { nativeEvent } = syntheticEvent;
        // On Android if the page uses history pushState and popState,
        // onNavigationStateChange is not called but onLoadProgress does
        setCanGoBackInWebView(nativeEvent.canGoBack);
      }}

This problem is not solved. Can this issue be opened again?

Why is this issue closed?


Support multi-inputs

Add SamplesBatch class
Utilize SamplesBatch class

Reference Issues/PRs
Resolves #161

What does this implement/fix? Explain your changes.
I've added a SamplesBatch class, which holds multiple inputs and single target.
Inputs are stored as a dict(str, np.ndarray). Sequence is stored at inputs_batch['sequence_batch'].
If only sequence is provided as an input, then inputs() getter will return just a sequence.
It also has a function to convert inputs and targets to torch.Tensors. The sequence's tensor is transposed to [batch_size, channels_size, sequnece_length], so we don't need to do transpose it everywhere in the code.
What testing did you do to verify the changes in this PR?
I added unit tests for the SamplesBatch class.
I also ran case2/1_train_with_online_sampler.yml with a validation on every other step. So intervals_sampler, train, and validate do work.
Please let me know if this is sufficient, or may be you have a list of commands you run to check that everything works.

PTAL @jzthree @kathyxchen


Why some modules are not being exported in index.ts?

Hi, there.
First of all, thanks for all your great works.
This library resolved many inconveniences I experienced while using nest/config.
I wondered why source provider modules like DotenvSourceProvider are not exported in index.ts.
It seems possible to specify the sourceProvider as an option in the ConfigModule.forFeature, but when I want to use DotenvSourceProvider, I can't import it.
I want to use as below.
// Module '"@nestjs-library/config"' has no exported member 'DotenvSourceProvider'.
import { ConfigModule, DotenvSourceProvider } from '@nestjs-library/config';

@Module({
    imports: [
        TypeOrmModule.forRootAsync({
            imports: [
                ConfigModule.forFeature(TypeOrmConfigService, {
                    sourceProvider: new DotenvSourceProvider(),
                }),
            ],
            useFactory: (typeORMConfigService: TypeOrmConfigService) => typeORMConfigService,
            inject: [TypeOrmConfigService],
        }),
    ],
    controllers: [AppController],
    providers: [AppService],
})
export class AppModule {}

Current index.ts is like below.
It exports only ConfigModule, AbstractConfigService, OptionalBoolean, ConfigScanner
export * from './lib/config.module';
export * from './lib/abstract/abstract-config.service';

export * from './lib/type-transformer';
export * from './lib/config-scanner';

Hi, @JadenKim-dev
As far as I know, there's no particular reason for this, it's simply missing.
The most likely reason is that my team doesn't use 'DotenvSourceProvider' and I didn't know about it. 😁
And as a background on providers,
they expect you to create and utilize your own, not have it provided by config library.
A DotenvSourceProvider was created as a guide for creating providers.

Thank you for your kind explanation, @jiho-kr!
Considering your points, it would be beneficial to also export the abstract class AbstractConfigSourceProvider to make it easier for users to implement their own provider.
I will proceed with this task and create a PR afterward! Thanks.

It has been resolved in #415.

It has been resolved in https://github.com/woowabros/nestjs-library-config/pull/415.


Add automatic link (facet) detection example

Automatic link detection using regex. Let me know if you want me to integrate this into one of the built-in methods in the library.
Co-authored-by: mavreyn<EMAIL_ADDRESS>

Fixed ruff linting.

cool! thank you!
could you pls run poetry run black examples to fix positions of )?

thank you!


Use of unsupported opcode (LIST_EXTEND) found

Reporting a bug
I tried to run this example from the documentation:
from numba import njit
from numba.typed import List

@njit
def foo():
    # Instantiate a typed-list
    l = List()
    # Append a value to it, this will set the type to int32/int64
    # (depending on platform)
    l.append(42)
    # The usual list operations, getitem, pop and length are
    # supported
    print(l[0])   # 42
    l[0] = 23
    print(l[0])   # 23
    print(len(l)) # 1
    l.pop()
    print(len(l)) # 0
    return l

foo()

I get
UnsupportedError                          Traceback (most recent call last)
<ipython-input-10-bf2ac9c9766e> in <module>
     19     return l
     20
---> 21 foo()

~/.local/lib/python3.9/site-packages/numba/core/dispatcher.py in _compile_for_args(self, *args, **kws)
    416         except errors.UnsupportedError as e:
    417             # Something unsupported is present in the user code, add help info
--> 418             error_rewrite(e, 'unsupported_error')
    419         except (errors.NotDefinedError, errors.RedefinedError,
    420                 errors.VerificationError) as e:

~/.local/lib/python3.9/site-packages/numba/core/dispatcher.py in error_rewrite(e, issue_type)
    356                 raise e
    357             else:
--> 358                 reraise(type(e), e, None)
    359
    360         argtypes = []

~/.local/lib/python3.9/site-packages/numba/core/utils.py in reraise(tp, value, tb)
     78         value = tp()
     79     if value.__traceback__ is not tb:
---> 80         raise value.with_traceback(tb)
     81     raise value
     82

UnsupportedError: Failed in nopython mode pipeline (step: nopython mode backend)
Failed in nopython mode pipeline (step: analyzing bytecode)
Use of unsupported opcode (LIST_EXTEND) found

File "../../../.local/lib/python3.9/site-packages/numba/cpython/builtins.py", line 569:
    def call_ctor(cls, *args):
        return numba_typeref_ctor(cls, *args)
        ^

During: lowering "$4call_function.1 = call $2load_global.0(func=$2load_global.0, args=[], kws=(), vararg=None)" at <ipython-input-10-bf2ac9c9766e> (7)

Version

aarch64
Python 3.9.1
numba 0.51.2
llvmlite 0.34.0
llvm: tested with versions 9 to 11. I know only 9 is supported but currently on arm stable only llvm 10 and 11 are present. I still had llvm9 but it did not install files for python 3.9. I get the exact same error on all 3 versions. I can execute other njit numba code fine with all versions.

There is definitely something wrong in my installation:
from numba import njit
import numpy as np

@njit
def f(l):
    return np.argsort(l)

f(np.arange(10))

TypingError: Failed in nopython mode pipeline (step: nopython mode backend)
Failed in nopython mode pipeline (step: nopython frontend)
No implementation of function Function(<function make_quicksort_impl.<locals>.run_quicksort at 0xffff9fb82310>) found for signature:

 >>> run_quicksort(array(int64, 1d, C))

There are 2 candidate implementations:
    - Of which 2 did not match due to:
    Overload in function 'register_jitable.<locals>.wrap.<locals>.ov_wrap': File: numba/core/extending.py: Line 150.
      With argument(s): '(array(int64, 1d, C))':
     Rejected as the implementation raised a specific error:
       UnsupportedError: Failed in nopython mode pipeline (step: analyzing bytecode)
     Use of unsupported opcode (LOAD_ASSERTION_ERROR) found

     File "../../../.local/lib/python3.9/site-packages/numba/misc/quicksort.py", line 180:
         def run_quicksort(A):
             <source elided>
                 while high - low >= SMALL_QUICKSORT:
                     assert n < MAX_STACK
                     ^

  raised from /home/louisabraham/.local/lib/python3.9/site-packages/numba/core/byteflow.py:269

During: resolving callee type: Function(<function make_quicksort_impl.<locals>.run_quicksort at 0xffff9fb82310>)
During: typing of call at /home/louisabraham/.local/lib/python3.9/site-packages/numba/np/arrayobj.py (5032)

File "../../../.local/lib/python3.9/site-packages/numba/np/arrayobj.py", line 5032:
    def array_argsort_impl(arr):
        return sort_func(arr)
        ^

During: lowering "$8call_method.3 = call $4load_method.1(l, func=$4load_method.1, args=[Var(l, <ipython-input-2-2fb691d45df3>:3)], kws=(), vararg=None)" at <ipython-input-2-2fb691d45df3> (3)

There is definitely something wrong in my installation:
from numba import njit
import numpy as np

@njit
def f(l):
    return np.argsort(l)

f(np.arange(10))

TypingError: Failed in nopython mode pipeline (step: nopython mode backend)
Failed in nopython mode pipeline (step: nopython frontend)
No implementation of function Function(<function make_quicksort_impl.<locals>.run_quicksort at 0xffff9fb82310>) found for signature:

 >>> run_quicksort(array(int64, 1d, C))

There are 2 candidate implementations:
    - Of which 2 did not match due to:
    Overload in function 'register_jitable.<locals>.wrap.<locals>.ov_wrap': File: numba/core/extending.py: Line 150.
      With argument(s): '(array(int64, 1d, C))':
     Rejected as the implementation raised a specific error:
       UnsupportedError: Failed in nopython mode pipeline (step: analyzing bytecode)
     Use of unsupported opcode (LOAD_ASSERTION_ERROR) found

     File "../../../.local/lib/python3.9/site-packages/numba/misc/quicksort.py", line 180:
         def run_quicksort(A):
             <source elided>
                 while high - low >= SMALL_QUICKSORT:
                     assert n < MAX_STACK
                     ^

  raised from /home/louisabraham/.local/lib/python3.9/site-packages/numba/core/byteflow.py:269

During: resolving callee type: Function(<function make_quicksort_impl.<locals>.run_quicksort at 0xffff9fb82310>)
During: typing of call at /home/louisabraham/.local/lib/python3.9/site-packages/numba/np/arrayobj.py (5032)

File "../../../.local/lib/python3.9/site-packages/numba/np/arrayobj.py", line 5032:
    def array_argsort_impl(arr):
        return sort_func(arr)
        ^

During: lowering "$8call_method.3 = call $4load_method.1(l, func=$4load_method.1, args=[Var(l, <ipython-input-2-2fb691d45df3>:3)], kws=(), vararg=None)" at <ipython-input-2-2fb691d45df3> (3)

AH! Trying to compile/install from master tells me 3.9 is not supported, is that the reason?

AH! Trying to compile/install from master tells me 3.9 is not supported, is that the reason?

Correct, Python 3.9 is not supported yet.  See #6345.
We haven't found a reliable way to convince pip not to install Numba on unsupported Python versions yet...

Correct, Python 3.9 is not supported yet.  See #6345.
We haven't found a reliable way to convince pip not to install Numba on unsupported Python versions yet...

Closing as duplicate of https://github.com/numba/numba/issues/6345. Thanks for reporting.
To follow 3.9 support progress please subscribe to https://github.com/numba/numba/pull/6579.

Closing as duplicate of https://github.com/numba/numba/issues/6345. Thanks for reporting.
To follow 3.9 support progress please subscribe to https://github.com/numba/numba/pull/6579.

Hitting Use of unsupported opcode (LOAD_ASSERTION_ERROR) found; also with Python 3.9.

Hitting Use of unsupported opcode (LOAD_ASSERTION_ERROR) found; also with Python 3.9.

@alobbs thank you for adding to this, this is the result of Python 3.9 currently not being supported by Numba.

@alobbs thank you for adding to this, this is the result of Python 3.9 currently not being supported by Numba.


Allow to keep preview for Git modified files even if enablePreview is false

I like to use "workbench.editor.enablePreview": true,, but the problem is if I have a lot of modified Git files when I'm reviewing changes all these files are opened. I suggest to keep enabled preview for Git modified files if enablePreview is false. This feature is really useful if you want to keep track of files you have opened via Go To Definition, etc., but with every Git modified file being opened which shows diffs makes it unusable...

If it's unclear what I wanted to say is I want to disable preview which means files are always opened and you don't need to double-click on them for everything except for Git modified files changes filename.ext (Working Tree) which are opened via SCM by looking through diff. The reason is this feature is useful, but when you're opening a lot of Git files to see diff's, etc. you end up with a lot of opened files.

I have renamed the title from:

Enable preview for Git modified files even if enablePreview is true

to

Allow to keep preview for Git modified files even if enablePreview is false

I suggest to simply have a git.enablePreview setting or similar.

@joaomoreno good idea, maybe I can create the PR?

Yes sir!

What I understand is you can't have these two:
  "workbench.editor.enablePreview": false,
  "workbench.editor.enablePreviewFromQuickOpen": true,

If workbench.editor.enablePreview is false having workbench.editor.enablePreviewFromQuickOpen set to true will not work. So my feature request will not work as expected...

Got it, gotta have @bpasero in this.

Yeah setting is not ideal. The one is the global switch and the other does not work if the global switch is off. A better setting would probably be some enumeration where you can list the things to enable.


Refactor CircularNotchedRectangle.getOuterPath()

This pull request is a follow-up on https://github.com/flutter/flutter/pull/151386#pullrequestreview-2170626471.

The circular notched rectangle's getOuterPath() method no longer uses any null-asserts.
It also used to have 2 variables (r and notchRadius) that held the same value, but that's no longer the case.

test-exempt: code refactor with no semantic change

autosubmit has been here for several days, and the tree is green…
Perhaps landing this one manually is the best way to go.


Make diagnostic about using unsupported compilers an error

Fixes https://github.com/rzwitserloot/lombok/issues/2714

There's a reason we generate a warning. There are a bunch of environments for help files and other bizarre scenarios where 'emit a warning but otherwise don't prevent this build from succeeding' is the better move.
So, instead I added some code to explicitly detect Turbine and fail with an error in that case. Just pushed, but I haven't tested it though. We'll roll out an edge release with this soon.


 I see it in the repo here for this step, but my working copy doesn't have one and I can't seem to find a mention of it in the tutorial.

@ocrickard This might depend on the version of Create React App you had used when you first created the project. I think the older version did not add that file. For the sake of the tutorial the file doesn't matter but it's good to update your Create React App and react-scripts as well if you haven't.

This issue was moved to https://discourse.serverless-stack.com/t/comments-create-containers/62


Mask certain tokens during annotation

There are many cases where a token is better off invisible to a sequence tagger or shift-reduce parser (ex. the bullet in a bulleted list, ®, °, etc.).  If such symbols have not been seen in training, they may have unexpected effects on the output sequence.  It would be convenient to provide masked tokens for specific steps in the annotation pipeline using a regular expression or list of strings.

This is with the veil:

This is without:

Here's the extra code:
    val veil = text.indices
        .filter { index =>
          val char = text.charAt(index)
          char == '®' || char == '*'
        }
        .map { index => index to index }
    val veiledText = new VeiledText(text, veil)
    val document = processor.annotate(veiledText.mkDocument(processor))

Nice!


Helper generated terraform script not working

Describe the bug
When using terraform scripts. it always says
requesting validating: resources.DeploymentsClient#Validate: Failure sending request: StatusCode=400 -- Original Error: Code="InvalidDeployment" Message="Support for symbolic name resources requires a minimum API version of '2020-09-01', but API version '2020-06-01' was supplied."

To Reproduce
Steps to reproduce the behavior:

Go to 'AKSC helper page', choose any configuration
Use generated terraform script

Expected behavior
no error
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Reproduced.
2023-06-23T08:54:00.020Z [DEBUG] provider.terraform-provider-azurerm_v3.62.0_x5: AzureRM Response for https://management.azure.com/subscriptions/REDACTED/resourcegroups/az-k8s-dr3x-rg/providers/Microsoft.Resources/deployments/AKS-C/validate?api-version=2020-06-01:
HTTP/2.0 400 Bad Request
Content-Length: 177
Cache-Control: no-cache
Content-Type: application/json; charset=utf-8
Date: Fri, 23 Jun 2023 08:53:59 GMT
Expires: -1
Pragma: no-cache
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Ms-Correlation-Request-Id: 49692083-00fa-e9b8-73f4-0bc8a6365144
X-Ms-Failure-Cause: gateway
X-Ms-Ratelimit-Remaining-Subscription-Writes: 1199
X-Ms-Request-Id: cdd64c0b-3cec-4c12-b2e3-ae74d810da92
X-Ms-Routing-Request-Id: WESTEUROPE:20230623T085400Z:cdd64c0b-3cec-4c12-b2e3-ae74d810da92

{"error":{"code":"InvalidDeployment","message":"Support for symbolic name resources requires a minimum API version of '2020-09-01', but API version '2020-06-01' was supplied."}}: timestamp=2023-06-23T08:54:00.019Z
2023-06-23T08:54:00.020Z [ERROR] provider.terraform-provider-azurerm_v3.62.0_x5: Response contains error diagnostic: @module=sdk.proto tf_resource_type=azurerm_resource_group_template_deployment @caller=github.com/hashicorp/terraform-plugin-go@v0.14.3/tfprotov5/internal/diag/diagnostics.go:55 diagnostic_detail= diagnostic_severity=ERROR diagnostic_summary="validating Template Deployment "AKS-C" (Resource Group "az-k8s-dr3x-rg"): requesting validating: resources.DeploymentsClient#Validate: Failure sending request: StatusCode=400 -- Original Error: Code="InvalidDeployment" Message="Support for symbolic name resources requires a minimum API version of '2020-09-01', but API version '2020-06-01' was supplied."" tf_proto_version=5.3 tf_provider_addr=provider tf_req_id=a08ed4ce-cfa2-2a46-134f-f73a622d8f84 tf_rpc=ApplyResourceChange timestamp=2023-06-23T08:54:00.020Z
2023-06-23T08:54:00.179Z [ERROR] vertex "azurerm_resource_group_template_deployment.aksc_deploy" error: validating Template Deployment "AKS-C" (Resource Group "az-k8s-dr3x-rg"): requesting validating: resources.DeploymentsClient#Validate: Failure sending request: StatusCode=400 -- Original Error: Code="InvalidDeployment" Message="Support for symbolic name resources requires a minimum API version of '2020-09-01', but API version '2020-06-01' was supplied."
╷
│ Error: validating Template Deployment "AKS-C" (Resource Group "az-k8s-dr3x-rg"): requesting validating: resources.DeploymentsClient#Validate: Failure sending request: StatusCode=400 -- Original Error: Code="InvalidDeployment" Message="Support for symbolic name resources requires a minimum API version of '2020-09-01', but API version '2020-06-01' was supplied."
│
│   with azurerm_resource_group_template_deployment.aksc_deploy,
│   on main.tf line 18, in resource "azurerm_resource_group_template_deployment" "aksc_deploy":
│   18: resource "azurerm_resource_group_template_deployment" "aksc_deploy" {
│
╵
2023-06-23T08:54:00.445Z [DEBUG] provider.stdio: received EOF, stopping recv loop: err="rpc error: code = Unavailable desc = error reading from server: EOF"

Logged the issue with the AzureRm provider.
https://github.com/hashicorp/terraform-provider-azurerm/issues/22259

I am having same issue and I am surprised that the issue still exists up till now.


v0.9.732 Invoke-SQLCMD2 Credentials parameter missing

Hi
It appears that Invoke-SQLCmd2 has been replaced by Invoke-DBAQuery
But seeing at Invoke-SQLCmd2 still exists, why oh why did the -Credential parameter get removed?
and on calling Invoke-SQLCmd2 it does not state that it is deprecated...?

Invoke-DbaQuery does not replace Invoke-Sqlcmd2. Invoke-Sqlcmd2 is a function added to dbatools module out of convenience, and is maintained by a different individual. (We simply host it under sqlcollaborative\invoke-sqlcmd2)
The -Credential parameter was not removed.
It is not being deprecated.

Thanks Shawn, I don't understand why the 2 commands below are so different?
0.9.501
Invoke-Sqlcmd2 [-ServerInstance] <String[]> [[-Database] <String>] [-Query] <String>      [[-Credential] <PSCredential>] [[-Encrypt]] [[-QueryTimeout] <Int32>]      [[-ConnectionTimeout] <Int32>] [[-As] <String>] [[-SqlParameters] <IDictionary>]      [[-AppendServerInstance]] [[-ParseGO]] []`
0.9.732
Invoke-Sqlcmd2 [-ServerInstance] <String> [-Database] <String> [[-Query] <String>]      [[-CommandType] {Text | StoredProcedure | TableDirect}] [[-CommandParameters] <Array>]      [[-Username] <String>] [[-Password] <String>] [[-QueryTimeout] <Int32>]      [[-ConnectionTimeout] <Int32>] [[-InputFile] <String>] [[-As] <String>]      [[-CallingFunction] <String>] [[-ApplicationName] <String>] [[-ReturnStream]]      [<CommonParameters>]

thx shawn you are right, Credential is aliased so would still work. skattie the commands are different because invoke-dbaquery adheres to our toolset conventions and has more goodies baked in 👍

Thanks Chrissy, but I am comparing 2 versions of Invoke-Sqlcmd2, forget invoke-dbaquery, the 2 commands above are very different...or am I missing something?

I can't answer what the state of the command was in previous versions. Someone may have got a change in but it apparently was reverted in a later release. The 501 release was from beginning of Nov and we release a handle of times every week.
Overall the end result will be that Invoke-Sqlcmd2 is going to be removed and no longer exist in the module. Invoke-DbaQuery is a new command that conforms to our standard and performs similiar (if not more) functionality. You will want to use this going forward.
If you happen to just desire to keep using Sqlcmd2 you can pull it from the GitHub repository.


[Bug] Tx list for BTC is showing $4 fee

After the migration to the new layout the TX fee is fixed at 4$ and the memo is not being shown.

https://github.com/voltix-vault/voltix/pull/242


#1138 Switch to license expression

Use a licence expression for the 1 project that was missing it
Closes #1138

Merged into Sonic Boom 1.1.0, which is a fork of NAudio. Thank you for your contribution!


Fields Identification

Hi,
Really nice work, I've managed to modify my pom.xml file and I can tell for now this is the only one CDR generator that works for me!!!
Is it possible to identify the fields of the data generated? Maybe on the readme, i'm not very skilled at Java so i cant check what file generates the output:
 0,01794666666,0,01799999999,16/10/2017,16/10/2017,14:55:00,15:22:00,Local,27.0
I can figure this:
0, Register ID
01794666666, Caller
0, unknown
01799999999, called
16/10/2017, start date?
16/10/2017, end date?
14:55:00, start time?
15:22:00, end time?
Local, call type (this is clear)
27.0, cost?
regards!

Hi,
Really nice work, I've managed to modify my pom.xml file and I can tell for now this is the only one CDR generator that works for me!!!
Is it possible to identify the fields of the data generated? Maybe on the readme, i'm not very skilled at Java so i cant check what file generates the output:
 0,01794666666,0,01799999999,16/10/2017,16/10/2017,14:55:00,15:22:00,Local,27.0
I can figure this:
0, Register ID
01794666666, Caller
0, unknown
01799999999, called
16/10/2017, start date?
16/10/2017, end date?
14:55:00, start time?
15:22:00, end time?
Local, call type (this is clear)
27.0, cost?
regards!

I've found it:
 for (Person p : customers) {
                for (Call c : p.getCalls()) {
                    fw.append(c.getId() + ","
                            + p.getPhoneNumber() + ","
                            + c.getLine() + ","
                            + c.getDestPhoneNumber() + ","
                            + c.getTime().getStart().toString(dateFormatter) + ","
                            + c.getTime().getEnd().toString(dateFormatter) + ","
                            + c.getTime().getStart().toString(timeFormatter) + ","
                            + c.getTime().getEnd().toString(timeFormatter) + ","
                            + c.getType() + ","
                            + c.getCost()
                            + newLine);
                }
            }

So, 0 unknown is the line of the user configured in JSON file...
Thank you very much!


Create Dictionary Model

Codecov Report

Merging #11 (259a0ea) into dev (e699bbf) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##               dev       #11   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            8        17    +9
  Lines          136       191   +55
  Branches        22        39   +17
=========================================
+ Hits           136       191   +55

Impacted Files
Coverage Δ

apps/dictionaries/admin.py
100.00% <100.00%> (ø)

apps/dictionaries/apps.py
100.00% <100.00%> (ø)

apps/dictionaries/factories.py
100.00% <100.00%> (ø)

apps/dictionaries/models.py
100.00% <100.00%> (ø)

apps/profiles/admin.py
100.00% <100.00%> (ø)

apps/profiles/apps.py
100.00% <100.00%> (ø)

apps/profiles/factories.py
100.00% <100.00%> (ø)

apps/profiles/models.py
100.00% <100.00%> (ø)

apps/profiles/tests.py
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Added 'exec' to the command in the node-red-pi script

Hello,
The benefits of this change are:

it allows process supervisors (like daemontools) to get the PID of the actual node-red process
it leaves fewer process hanging around

nick.

Coverage decreased (-0.1%) to 88.248% when pulling 472771a4d8017f582c3422ecc5523371e9e31b0c on njh:exec-node-red-pi into 0eba04aac03ee464b9f97a96a5e72c0debd9fa34 on node-red:master.

Yay!


Make parser module to a independent module

For #2722.
Changes proposed in this pull request:

Move parser module from sharding-core module to top level module
Rename sharding-core-parse to shardingsphere-sql-parser
Decouple shardingsphere-sql-parser and sharding-core

Pull Request Test Coverage Report for Build 825

554 of 1686 (32.86%)  changed or added relevant lines in 221 files are covered.
236 unchanged lines in 16 files lost coverage.
Overall coverage decreased (-0.1%) to 68.521%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sharding-core/sharding-core-common/src/main/java/org/apache/shardingsphere/core/database/DatabaseTypes.java
0
1
0.0%

sharding-core/sharding-core-common/src/main/java/org/apache/shardingsphere/spi/database/H2DatabaseType.java
4
5
80.0%

sharding-core/sharding-core-common/src/main/java/org/apache/shardingsphere/spi/database/OracleDatabaseType.java
3
4
75.0%

sharding-core/sharding-core-common/src/main/java/org/apache/shardingsphere/spi/database/PostgreSQLDatabaseType.java
3
4
75.0%

sharding-core/sharding-core-common/src/main/java/org/apache/shardingsphere/spi/database/SQL92DatabaseType.java
3
4
75.0%

sharding-core/sharding-core-common/src/main/java/org/apache/shardingsphere/spi/database/SQLServerDatabaseType.java
3
4
75.0%

sharding-proxy/sharding-proxy-backend/src/main/java/org/apache/shardingsphere/shardingproxy/backend/schema/LogicSchema.java
0
1
0.0%

shardingsphere-spi/src/main/java/org/apache/shardingsphere/spi/TypeBasedSPIServiceLoader.java
15
16
93.75%

shardingsphere-sql-parser/shardingsphere-sql-parser-common/src/main/java/org/apache/shardingsphere/sql/parser/core/constant/Paren.java
11
12
91.67%

shardingsphere-sql-parser/shardingsphere-sql-parser-common/src/main/java/org/apache/shardingsphere/sql/parser/core/extractor/impl/common/expression/impl/CommonExpressionExtractor.java
1
2
50.0%

Files with Coverage Reduction
New Missed Lines
%

sharding-core/sharding-core-route/src/main/java/org/apache/shardingsphere/core/route/router/sharding/RoutingEngineFactory.java
1
93.75%

sharding-jdbc/sharding-jdbc-core/src/main/java/org/apache/shardingsphere/shardingjdbc/jdbc/adapter/AbstractDataSourceAdapter.java
1
97.44%

sharding-jdbc/sharding-jdbc-core/src/main/java/org/apache/shardingsphere/shardingjdbc/jdbc/adapter/AbstractMasterSlavePreparedStatementAdapter.java
1
0.0%

sharding-jdbc/sharding-jdbc-core/src/main/java/org/apache/shardingsphere/shardingjdbc/jdbc/core/connection/MasterSlaveConnection.java
3
7.14%

sharding-ui/sharding-ui-backend/src/main/java/org/apache/shardingsphere/ui/repository/impl/YamlRegistryCenterConfigsRepositoryImpl.java
4
0.0%

sharding-ui/sharding-ui-backend/src/main/java/org/apache/shardingsphere/ui/security/UserAuthenticationService.java
4
0.0%

sharding-proxy/sharding-proxy-backend/src/main/java/org/apache/shardingsphere/shardingproxy/backend/text/TextProtocolBackendHandlerFactory.java
5
78.57%

sharding-ui/sharding-ui-backend/src/main/java/org/apache/shardingsphere/ui/util/ConfigurationYamlConverter.java
7
0.0%

sharding-ui/sharding-ui-backend/src/main/java/org/apache/shardingsphere/ui/security/AuthenticationFilter.java
11
0.0%

sharding-core/sharding-core-common/src/main/java/org/apache/shardingsphere/core/rule/ShardingRule.java
12
84.57%

Totals

Change from base Build 546:
-0.1%

Covered Lines:
11482

Relevant Lines:
16757

💛  - Coveralls


Remove key in tags to reduce metrics count

Issue: https://github.com/knative/serving/issues/8609
Signed-off-by: Lance Liu<EMAIL_ADDRESS>

You probably also want to remove keyTagKey from line 170 and 175 (which is where we instruct OpenCensus to aggregate divided by key), and the definition on line 49.

/ok-to-test

I removed the key tag accordingly. Thank you @evankanderson.
After apply this patch, the total metrics count for controller drops significantly.
Before:
~ wc -l metrics-controller.txt
   68628 metrics-controller.txt

After:
~ wc -l metrics-controller.txt
     570 metrics-controller.txt

Also the size of metrics drops from ~11M to ~66K
@vagababov

/test pull-knative-pkg-unit-tests

/retest

Wow, the cardinality for key must have been really high (which will cause problems with Stackdriver, at least, but many monitoring systems struggle with high-cardinality labels).
/lgtm
/approve

/retest


pick stats derive for "not equal“, avoid to derive zero ndv

pick (#31566)
Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


ValueError: need more than 0 values to unpack

I got this issue and have no idea to resolve. I need your help.

Hi @binhna,
Thank you for your report.
Could you tell me your command?
I think you didn't set --dev_file argument?

I have modified README.md to set  --dev_file input_file_dev.txt.
Please let me know if you have some problems.

Thank you very much. But I still have a problem when predicting:
Binhs-MacBook-Pro:deep-crf BinhNguyen$ deep-crf predict input_raw_file.txt --model_name bilstm-cnn-crf --model_filename /Users/BinhNguyen/Downloads/deep-crf/save_model_dir/bilstm-cnn-crf_adam_epoch26.model --predicted_output predicted.txt
{'dropout_rate': 0.33, 'vocab_file': None, 'n_char_hidden': 30, 'batchsize': 32, 'model_filename': '/Users/BinhNguyen/Downloads/deep-crf/save_model_dir/bilstm-cnn-crf_adam_epoch26.model', 'use_crf': 1, 'vocab_char_file': None, 'weight_decay': 0.0, 'optimizer': u'adam', 'n_hidden': 200, 'efficient_gpu': 1, 'init_lr': 0.001, 'use_lr_decay': 0, 'use_cudnn': 1, 'n_word_emb': 100, 'predicted_output': u'predicted.txt', 'gpu': -1, 'save_name': u'', 'test_file': None, 'word_emb_file': None, 'max_iter': 50, 'n_layer': 1, 'dev_file': None, 'word_emb_vocab_type': u'replace_all', 'n_vocab_min_cnt': 0, 'input_idx': u'0', 'output_idx': u'-1', 'delimiter': u'\t', 'n_char_emb': 30, 'save_dir': u'save_model_dir', 'n_add_feature_emb': 100, 'model_name': u'bilstm-cnn-crf'}
[2017-09-21 08:12:38,640] [INFO] train:2388 (run@main.py:230)
[2017-09-21 08:12:38,640] [INFO] dev  :0 (run@main.py:231)
[2017-09-21 08:12:38,640] [INFO] test :0 (run@main.py:232)
[2017-09-21 08:12:38,640] [INFO] vocab     :17496 (run@main.py:233)
[2017-09-21 08:12:38,640] [INFO] vocab_tags:9 (run@main.py:234)
[2017-09-21 08:12:38,640] [INFO] unk count (train):4566 (run@main.py:235)
[2017-09-21 08:12:38,641] [INFO] unk rate  (train):0.0686203787196 (run@main.py:236)
[2017-09-21 08:12:38,641] [INFO] cnt all words (train):66540 (run@main.py:237)
[2017-09-21 08:12:38,641] [INFO] unk count (dev):0 (run@main.py:238)
[2017-09-21 08:12:38,641] [INFO] unk rate  (dev):0.0 (run@main.py:239)
[2017-09-21 08:12:38,641] [INFO] cnt all words (dev):0 (run@main.py:240)
[2017-09-21 08:12:38,641] [INFO] ###################### (run@main.py:242)
[2017-09-21 08:12:38,641] [INFO] ## Model Config (run@main.py:243)
[2017-09-21 08:12:38,641] [INFO] model_name:bilstm-cnn-crf (run@main.py:244)
[2017-09-21 08:12:38,641] [INFO] batchsize:32 (run@main.py:245)
[2017-09-21 08:12:38,641] [INFO] optimizer:adam (run@main.py:246)
[2017-09-21 08:12:38,641] [INFO] ###################### (run@main.py:248)
[2017-09-21 08:12:38,641] [INFO] ## Model Save Config (run@main.py:249)
[2017-09-21 08:12:38,641] [INFO] save_dir :save_model_dir/ (run@main.py:250)
[2017-09-21 08:12:38,641] [INFO] save_vocab        :save_model_dir/bilstm-cnn-crf_adam.vocab (run@main.py:253)
[2017-09-21 08:12:38,642] [INFO] save_vocab_char   :save_model_dir/bilstm-cnn-crf_adam.vocab_char (run@main.py:254)
[2017-09-21 08:12:38,642] [INFO] save_tags_vocab   :save_model_dir/bilstm-cnn-crf_adam.vocab_tag (run@main.py:255)
[2017-09-21 08:12:38,642] [INFO] save_train_config :save_model_dir/bilstm-cnn-crf_adam.train_config (run@main.py:256)
Traceback (most recent call last):
  File "/usr/local/bin/deep-crf", line 11, in <module>
    load_entry_point('DeepCRF==1.0', 'console_scripts', 'deep-crf')()
  File "/Library/Python/2.7/site-packages/click-6.7-py2.7.egg/click/core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "/Library/Python/2.7/site-packages/click-6.7-py2.7.egg/click/core.py", line 697, in main
    rv = self.invoke(ctx)
  File "/Library/Python/2.7/site-packages/click-6.7-py2.7.egg/click/core.py", line 1066, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/Library/Python/2.7/site-packages/click-6.7-py2.7.egg/click/core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/Library/Python/2.7/site-packages/click-6.7-py2.7.egg/click/core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "build/bdist.macosx-10.12-intel/egg/deepcrf/__init__.py", line 112, in predict
  File "build/bdist.macosx-10.12-intel/egg/deepcrf/main.py", line 367, in run
UnboundLocalError: local variable 'predict_dev_tags' referenced before assignment

Hi @binhna
I'm sorry for that bug.
I have modified that bug few days ago.
So can you update the deep-crf with following commands?
cd deep-crf
git pull
python setup.py install

Thats great! But a bug when evaluate!

Thank you for your report and I'm sorry for that bug.
Can you show me your gold.txt and predicted.txt?
head -n 20 gold.txt
head -n 20 predicted.txt

I think that the line of your file is difference?
please tell me your number of line in gold and predicted.
wc -l gold.txt
wc -l predicted.txt

I can send to you via email, is it ok?

OK.
<EMAIL_ADDRESS>Please send it to me when you have time.

sent! Please check for me. Thank you

Thank you.
I checked your gold file.
Around line 29 - 65,  it seems wrong sentence between gold.txt and predicted.txt .
Please check your input_raw_file.txt whether input_raw_file.txt and gold.txt have same sentence order?

can you tell me
head -n 5 input_raw_file.txt

I'm sorry for the inconvenience. It's my fault, exactly what you say. The input_raw_file.txt is incorrect. I fixed and it worked now.
Thank you very much.

OK!
If you have other questions, please let me know!


Search form wording - leave blank to search all counties

Initial testing indicates Users do not realize they can search all census counties or all birth counties by not selecting a county (due to the current wording that says "Select one to three").  Since there is no "All counties" option in the drop-down like in FC1, we should clarify the wording with something such as "..., or leave blank to search all" or else add an "All Counties" option to the drop down.

Add 'all counties' option.

@dougkdev
https://github.com/FreeUKGen/MyopicVicar/blob/freecen_parsing/app/views/search_queries/_form_freecen.html.erb#L100
All Counties
For the option to be there but pass nothing as a value.
I was wondering what's the best way of reviewing code, since we are not using pull requests.
If the solution is small i can post it here but what if it's multiple lines and files?  because if i just push it on master directly and wait for a review, it might cause issues, someone can deploy the code without a review first. Or still need multiple corrections until it's ready.

Hi @AlexAvlonitis ,
When working on FreeCen, instead of checking in to master, check in to the freecen_parsing branch.
The way we have done it in the past has been to test changes on our own development machine, then push to origin freecen_parsing, and then test on test2.  We haven't really had any formal code review before committing changes to the git repository, although a few times have had each other look something over informally, and I assume we all sort of keep tabs on what is being committed at a high level (commit messages) even if we don't review the code itself.  For major work, sometimes a new branch has been started for that work (primarily from master, I don't think we have branched freecen_parsing at all).
Now that there are more of us, and especially now that we will have a production FreeCen deployment, maybe bring this up in the scrum tomorrow and we can get @benwbrum 's opinion of how to best communicate going forward to avoid accidental deployment of code that isn't finished being tested.  We will also want to get @Captainkirkdawson 's opinion once he is back for how best to coordinate for FreeReg.


how i can i make this unclickable or unchangeable progress in seekbar so that user can't change that i need static progress

i got it
this can be done using this line of code :


codegen failed with exit code 1

Using codegen as a build step in xcode generates this error:
Command /bin/sh failed with exit code 1
++ exec apollo-codegen generate --schema schema.json --output API.swift
TypeError: Cannot read property 'length' of undefined
at Object.yargs.command.command.command.argv [as handler] (/usr/local/lib/node_modules/apollo-codegen/src/cli.js:186:17)
at Object.runCommand (/usr/local/lib/node_modules/apollo-codegen/node_modules/yargs/lib/command.js:235:44)
at Object.parseArgs [as _parseArgs] (/usr/local/lib/node_modules/apollo-codegen/node_modules/yargs/yargs.js:1013:30)
at Object.get [as argv] (/usr/local/lib/node_modules/apollo-codegen/node_modules/yargs/yargs.js:957:21)
at Object. (/usr/local/lib/node_modules/apollo-codegen/lib/cli.js:197:5)
at Module._compile (module.js:649:30)
at Object.Module._extensions..js (module.js:660:10)
at Module.load (module.js:561:32)
at tryModuleLoad (module.js:501:12)
at Function.Module._load (module.js:493:3)
Not sure if this is a codegen issue or something very specific to my project (first time I'm trying this), so any help would be appreciated!

This should generate a better error message, but it means you're trying to invoke codegen without any .graphql files (which contain the queries).

That was it, thanks!


[WIP] Setup Danger

Changes in this pull request
Getting some basic Danger automation up and running. Should see comments from @iglistkit-bot.
Issue fixed: #394

Sick.
Ok setting up some basic rules.

LOVE that it edits the original post. 👏👏👏

nice

It's like it was never even in this comment thread


Are helm ownership label/annotations applied to hook resources as well?

Versions

Helm version.BuildInfo{Version:"v3.3.4", GitCommit:"a61ce5633af99708171414353ed49547cf05013d", GitTreeState:"clean", GoVersion:"go1.14.9"}
Kubectl Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.6", GitCommit:"dff82dc0de47299ab66c83c626e08b245ab19037", GitTreeState:"clean", BuildDate:"2020-07-15T16:58:53Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Cloud provider is Digital Ocean

Helm applies label app.kubernetes.io/managed-by: Helm and annotations meta.helm.sh/release-name, meta.helm.sh/release-namespace automatically to every resource it creates. Is this the case for resource created as hook? It looks like it does not so I would like to confirm this and also to understand if there is any good reason for this.
My usecase
I am installing sentry using this helm chart. The chart is handling order in which various components goes up by using hooks. On initial fresh install subset of resources is created as hooks (.Values.asHook=true) while later upgrades are supposed to be installed as regular resource objects (.Values.asHook=false). In my exprience this upgrade is failing with this error:
"Error: UPGRADE FAILED: rendered manifests contain a resource that already exists.
Unable to continue with update: Deployment "sentry-relay" in namespace "infra-sentry" exists and cannot
be imported into the current release: invalid ownership metadata; label validation error: missing key
"app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key
"meta.helm.sh/release-name": must be set to "sentry"; annotation validation error: missing key
"meta.helm.sh/release-namespace": must be set to "infra-sentry"

After digging around a bit I think this is because helm is not annotating hook objects as described above. A possible way out of this for me is to add these label/annotations manually as part of chart and call it a day. However I wonder cannot Helm add these metadata to hook resources as well? It looks like all semantics would hold. It certainly is managed by helm, present in the namespace and part of the release. Maybe "part of the release" is debatable. On the other hand going through source code it looks like helm is using these "only" to ensure it will not mess up with resources created by somebody else which would be ok here as well.
What do you think?

As described in the documentation, Helm does not control the lifecycle of hooks, so yes this is to be expected.

Thanks. One more thing I still wanted to ask. The error above (cannot be imported) is not occuring all the time. In fact usually it is ok but not always. Any idea of why this might be the case?

That error occurs when a resource is already present in the cluster that a helm install is attempting to overwrite.


Create a new deck with randomly selected cards

A new method Deck.randomFill() could be added.
Need #5 to be closed first!

Closed with commit 9c63c42 and 94c0e2d.


Slurm profile for CHEO-RI and Stager integration

Note that we don't actually want to merge this into master- we'll keep this as a separate branch. I'm making a pull request here to explain key files and discuss relevant issues.
Questions:

Will the pipeline be run as the 'slurm' user?

We talked about the variables SF=~/crg2/Snakefile; CP="/home/slurm/conda_envs/crg2-conda"; SLURM=~/crg2/slurm_profile; being defined outside of the commands passed to the script parameter of the slurm API. I'm not sure where the best place is for this- maybe the slurm.py script?

For now, I'm setting up analyses in /storage/data/test_crg2_automation. We'll want to determine a better location and structure for these analyses.

Key scripts:

dnaseq_slurm_api.sh: the contents of this file should be passed to slurm here.
dnaseq_slurm_api_2621.sh: this is a script to test exome setup and crg2 in the CHEO-RI space. The pipeline will run but fail at the cram2fastq step because haven't yet copied over the hg19 reference to the CHEO-RI space.
-dnaseq_slurm_api_2910.sh: a second script for testing exome setup and crg2. The pipeline will fail at the qualimap step as we haven't copied over the gtf file.

What's the purpose of the remaining dnaseq*.sh scripts?

Not sure what editor was used to write the shell scripts, but they should have trailing newlines like every other text file to be POSIX-compliant.

VSCode :/

What's the purpose of the remaining dnaseq*.sh scripts?

dnaseq.sh: the very first script we wrote for running crg2 on the CHEO-RI space, without a slurm profile
dnaseq_slurm.sh: this is the original script for running crg2 on the CHEO-RI space with slurm integration and sans automation
Neither script incorporated automated setup of the analysis directory.
Won't need either of these in the future...

@kevinlul input is now a JSON, see a595e76

If dnaseq_slurm_api.sh is the script to be run, make sure to chmod +x it!

TO DO:

[ ] create two benchmark.tsv (one for hpf, one for CHEO-RI)
[ ] remove config.yaml, add config_hpf.yaml
[ ] remove dnaseq.sh
[ ] modify dnaseq_slurm_api.sh: add --configfile argument
[ ] remove dnaseq_slurm_api_2910.sh
[ ] modify slurm_profile/settings.json default account


bug: enable compatability with offline studio

Hey'o, I tried to use this module in a game of mine that is fully rojo managed, and I ran into a few errors to-do with the Roblox MemoryStore/DataStore APIs breaking when attempting to do anything in an Offline environment.
This PR aims to fix those errors, where if this module is required, or depended upon during an offline environment it silently errors and doesn't break the code that's calling the relevant APIs.

It would also be cool if this had official wally support, but if thats not on the agenda then i'm happy to push my own changes to wally so I can continue to use this resource.. :sweat_smile:

Thanks for the contribution!
Added Wally support<EMAIL_ADDRESS>(I don't know how well this works in production yet so I would make sure to verify it all works and stress test it. Roblox's Memory Stores with SortedMaps and sharding don't really scale reliably when your game gets more players, you can check out my criticism here: https://devforum.roblox.com/t/introducing-memorystore-sortedmap-sortkey-beta/2673559/23)

Following up on this, @arxkdev - it appears the v0.0.1 package on wally does not contain the fixes mentioned in this PR, is this intebtional? 👀

Also I acknowledge Roblox's limits... Its not an ideal situation but worst case scenario I'll stick to global leaderboards (given this also supports them! I just appreciate not having to inplement datastores by hand 😅)

Hey @4x8Matrix, I just updated the package with the latest code<EMAIL_ADDRESS>Let me know with any further issues, much appreciated.


[Linux] Add JavaScript modal dialog

Leverage components app_modal's JavaScript modal dialog implementation.
BUG=XWALK-5819
(cherry picked from commit c1dd999fce5ed1982431bc48bb0bee9394f14060)

@rakuco

This looks more like a new feature implementation than a bug fix. Do we really need it in 17?

Nope per policy, no new features in beta branches.

It's a critical bug reported by Deepin, if it can't be merged to crosswalk-17 then crosswalk-17 becomes useless for them and they have to start from crosswalk-18.

Well,  this is a critial bug fix for Deepin. Please prioritize to merge it if possible..
copy @baleboy ..

Is 17 the last version DeepIn will ever use?

the situation is that deepin is going to release a new version soon,  and during the app test  this major issue was reported by deepin.  so if we can solve this issue in crosswalk 17, it will be the best, otherwise the schedule might be postponded

and we will further double check w/ Deepin on the release schedule .

Sure. We understand their pressure but they also need to understand our release model. It's a 2 way relationship. Plus their schedule slipped a lot the past months and we kind of ramped down because of that. Also they just figured out now right before their release that the JS dialogs are not working?
How we can merge a feature in the beta branch (which is against our policy) without even a QA report on master?
For the record I'm still debugging this patch on Windows. I simply ported the patch to Windows (just removing the ifdef OS_LINUX) because most of the code is cross-platform aka Aura + Toolkit Views and so far it asserts in Debug. I haven't had time to double check that on Linux but based on the fact that the assert is in non windows specific code right in the middle of toolkit views I strongly suspect it asserts as well on Linux. I will verify that first thing tomorrow morning.

Is DeepIn using the beta branch? We are not building nor testing it for Linux

And the code asserts in debug on Linux as well. As-is anyway it can't be backported.

Just double confirm with Deepin, they agree to use the latest canary build. So I will close this PR.
Sorry for any inconvenience.


feat: update to eye v2.10.0

feat: update to eye v2.10.0

:tada: This PR is included in version 2.13.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release
v2.13.0

Your semantic-release bot :package::rocket:


Drain scripts waiting for green cluster status are dangerous

I recently discovered that you added drain scripts for elasticsearch at some point in time. How they're implemented is kind of dangerous, and here is why:

your drain scripts wait for a green elasticsearch cluster status
the agent executes drain scripts forever, there is no timeout

So guess what happens when you want to repair a broken elasticsearch cluster with a bosh deploy? The drain hangs forever, nothing moves.
I know (now) that I can disable the drain scripts from the manifest. That didn't really do it for me because I only realized it when I had it already deployed. I know I can do bosh stop --skip-drain and then re-deploy, which I eventually did.
I'm not sure which cases you're covering with the scripts, maybe a scale-down without dataloss? Seems like the current idea of the drain has some unwanted side-effects you want to think about or document thoroughly.

To add to @voelzmo , it seems also that the drain script disables allocations, which are reenabled only once a node is back up (in the ctl script). This means that if you downscale the cluster (where the node will not return) and are not aware of this, the cluster will remain locked and unusable.
I believe the idea behind this script was to prevent a massive rellocation of data during an update (e.g. stemcell update) of the cluster.

@voelzmo, @momchil-sap: we are ware of the problems.
We completely reworked the data node upgrade process, the changes are waiting for a new feature to be added to BOSH which is expected to be released with one of the next few releases, we are hoping within a few weeks.

@cromega Thanks for explaining the rationale behind this. Out of curiosity: which feature would that be that you're waiting for?

@voelzmo: the ability to run post-deploy scripts

Ah nice, that is on the develop branch already, so the next release should probably have it :)

@voelzmo - The next release - v201 - will
(a) Disable shard allocations at the beginning of a deploy
(b) Have an errand - bosh run errand enable-shard-allocation to re-enable then after a deploy has finished
As soon as BOSH releases with post-deploy scripts, (b) will be turned into a  post-deploy scripts.
Hope that helps; and thanks for your thoughts!

Does fully disabling allocations prevent indices from being created if log
messages with new dates/times come through, potentially causing data loss
until re-enabling?
On Thursday, March 3, 2016, David Laing<EMAIL_ADDRESS>wrote:

@voelzmo https://github.com/voelzmo - The next release - v201 - will
(a) Disable shard allocations at the beginning of a deploy
(b) Have an errand - bosh run errand enable-shard-allocation to re-enable
then after a deploy has finished
As soon as BOSH releases with post-deploy scripts, (b) will be turned into
a post-deploy scripts.
Hope that helps; and thanks for your thoughts!
—
Reply to this email directly or view it on GitHub
https://github.com/logsearch/logsearch-boshrelease/issues/209#issuecomment-191841450
.

--
Danny Berger
https://dpb587.me

@dpb587 - Bummer; you are right.
During a deploy, attempts to create new indicies will fail, eg:
curl -XPOST "http://localhost:9200/new_index/my_type" -d "{ \"field\" : \"value\"}"
{"error":{"root_cause":[{"type":"unavailable_shards_exception","reason":"[new_index][3] primary shard is not active Timeout: [1m], request: [index {[new_index][my_type][AVM9gHBuL3eDRI8kcjes], source[{ \"field\" : \"value\"}]}]"}],"type":"unavailable_shards_exception","reason":"[new_index][3] primary shard is not active Timeout: [1m], request: [index {[new_index][my_type][AVM9gHBuL3eDRI8kcjes], source[{ \"field\" : \"value\"}]}]"},"status":503}%

Indexing to existing indices continue to work during the deploy, as do searches.
@cromega, @ablease - thoughts?

We can experiment with disabling replica allocations only. I have a feeling that will impact recovery time after a deploy on larger clusters though.
I think there will be a trade off that comes down to how people manage their clusters.
If you have big indices, then you want to disable shard allocation.
If you have small indices and create many per day, then you might be able to live without disabling shard allocation at all...


Procstat upd

@ranjib I've made some additions to your procstat plugin, because I realized that I think it would be useful for users to be able to track processes that have multiple PIDs.
This change adds two default tags to each process: name and pid. I've also made a change so that getPidExe returns a list of PIDs.
let me know what you think, this is related to what @arnimarj was asking about in PR #240

One other thing, I've made prefix a default argument. This is because some users will want to be able to query for all of their procstat measurements, being able to then filter by the name and pid tags.

:+1: awesome.


Fix mypy ci

Seeing if pinning version of mypy to previous version fixes CI

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

Oh by the way, I did find that by changing these two signatures in _deprecation.py, you can get mypy to pass as well on latest version...
# added 'list'
class DeprecateListMetaclass(type, list):

# added 'type'
class DeprecatedList(list, type, metaclass=DeprecateListMetaclass):

Though I have no idea what I'm doing here or if this is OK 😅

the other option is to just ignore the errors for that class or file

Thanks @nateraw for having a look at it :) I just played locally with mypy and doesn't really understand the class DeprecatedList(list, type, metaclass=DeprecateListMetaclass): solution either. Since it's very specific (and will be removed in a few versions), I would keep it as it is now. Besides, I already check in the metaclass init if the base is a subtype of list (which mypy would guarantee) so really not necessary to think too much about it IMO.
Let's pin the mypy version, it's good practice anyway :)


Clarify Vague Expressions in Documentation

This PR is focused on refining current language for clarity.
It does not introduce any new concepts or significant changes to existing documentation content.
Changes:

Updated JavaDoc comments to provide clearer explanations.
Revised some descriptions to be more precise and less ambiguous.
Enhanced wording for improving overall clarity.

Impact:
These changes are solely within documentation and do not affect the functionality of the code. It is intended to make the documentation more user-friendly.

@724thomas Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@724thomas Thank you for signing the Contributor License Agreement!


Fix process shutdown on Android

fix: handle process shutdown with limited permissions

Certain platforms like Android do not have permission to list all child processes. In this instance, just continue

Done

Merged the PR by hand into the main branch, due to to the docs/readthedocs.org:pytest-shell-utilities requirement is met on https://readthedocs.org/projects/pytest-shell-utilities/builds/, but the passed response appears to not have made it back to Github.

@dead10ck Just released version 1.9.4 with your fix for pytest-shell-utilities

Thank you!


fix: sort migrations by time

Fix data migration without sorting based on timestamp

Not recommended to sort within a loop , Placed outside the loop . Already updated . Thanks for your advice


Update Script: Zigbee2MQTT dev branch install method from npm to pnpm

[!NOTE]
We are meticulous when it comes to merging code into the main branch, so please understand that we may reject pull requests that do not meet the project's standards. It's never personal. Also, game-related scripts have a lower chance of being merged.

Description
Changes the broken npm install for the dev branch to pnpm as stated by the maintainer of Zigbee2mqtt KLICK
Tested both, dev and no dev, all still working.
I also tidied up the script :)
Fixes #698
Type of change
Please check the relevant option(s):

[X] Bug fix (non-breaking change that resolves an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (a fix or feature that would cause existing functionality to change unexpectedly)
[ ] New script (a fully functional and thoroughly tested script or set of scripts.)

Prerequisites
The following efforts must be made for the PR to be considered. Please check when completed:

[X] Self-review performed (I have reviewed my code, ensuring it follows established patterns and conventions)
[X] Testing performed (I have tested my changes, ensuring everything works as expected)
[ ] Documentation updated (I have updated any relevant documentation)

Additional Information (optional)
Provide any additional context or screenshots about the feature or fix here.
Related Pull Requests / Discussions
If there are other pull requests or discussions related to this change, please link them here:

Related PR #

This change will not work in update function, since it uses npm.
I see that the change from npm to pnpm is part of a big Zigbee2MQTT v2.0.0 release which will be out on 3 January 2025. we should consider temporarily disabling choosing dev branch on install, until the official release. Then we can update the whole script to use new install and update method.

This change will not work in update function, since it uses npm.
I see that the change from npm to pnpm is part of a big Zigbee2MQTT v2.0.0 release which will be out on 3 January 2025. we should consider temporarily disabling choosing dev branch on install, until the official release. Then we can update the whole script to use new install and update method.

Yes, I´ve also found that it is not done with installing the dev branch with pnmp, we would need to rewrite the whole script because npm is hardcoded in the service. It might be better to postpone.
I´ve you want to keep going, i can rewrite it, otherwise please close the PR.

i think, only switch to new variant.
Old Installations need to migrate himself.
Theres a Breaking Change and here is the Announcement for this:
https://github.com/community-scripts/ProxmoxVE/discussions/660

Oh my, i completle missed that. I will close this PR and we will se when 2.0 is out.


New Feature: Spectrum Analyzer

I was working on a project and wanted to construct this- https://www.instructables.com/Raspberry-Pi-Spectrum-Analyzer-with-RGB-LED-Strip-/
I am using dancyPi and modified some code to achieve this but was unsuccessful. Can someone probably help in creating this ?

You can most likely do this with numpy. This project uses numpy to generate the LED visualizations, Here's the code for the scroll effects: https://github.com/naztronaut/dancyPi-audio-reactive-led/blob/master/python/visualization.py#L108
If you can figure out the sequence needed for the spectrum analyzer, you should be able to do something similar. I'm still learning and getting comfortable with numpy so I'm a little bit away from being able to do this efficiently. But I got myself a 8x8 WS2812b LED Panel for this purpose.
Hope this helps guide you in the right direction. Good luck! We can keep this issue open to see if anyone else has already worked on this.


feature/UIDS-442 add Button to DS

closes #442

Added Primary, Warning, and Danger variants of the Button component
Updates documentation
Swaps out old buttons in various stories with new Button component

For cutover into rails-server, I'm most likely going to start with the Warning or Danger variants and just ensure stability of the component and identify any extra cleanup that might need to occur. I assume the Primary variant will take a few passes to update on RS, so can iterate if additional changes need to be made (including other variants that haven't been included yet).
https://www.figma.com/file/471iS3QrpPtXZpS1xbsJ20/Components?version-id=1070608432&node-id=7330%3A39808

So excited for this!! Just a couple notes for each variant:
Primary

Can we / is it necessary to add outline and disabled variants for the small primary button? Same for danger & warning buttons.
The button color does not change in the Pressed state for outline variants. Same for danger & warning buttons.

Danger

Can we set border-radius: 0.25 for the small button?
Are we able to add in leading & trailing icons to all danger buttons? Same for warning buttons.

Warning

For the default buttons, the border color does not change on hover

Currently looking into an issue with this branch that's causing some Modal issues.

Warning: react-modal: App element is not defined. Please use `Modal.setAppElement(el)` or set `appElement={el}`. This is needed so screen readers don't see main content when modal is opened. It is not recommended, but you can opt-out by setting `ariaHideApp={false}`.
    at ModalPortal (http://localhost:8080/packs/js/vendor-d758c945e6c6b429b304.chunk.js:90176:5)
    at Modal (http://localhost:8080/packs/js/vendor-d758c945e6c6b429b304.chunk.js:89810:5)
    at Modal (http://localhost:8080/packs/js/common-9a1bf521ab7bc378865b.chunk.js:1924:20)
    at div
    at DeleteParticipantsModal (http://localhost:8080/packs/js/researcher/participant_search-b5182deadd4beda5bc5a.chunk.js:17080:5)
    at TitledPage (http://localhost:8080/packs/js/shared-70732d3819cae9f1039f.chunk.js:14381:23)
    at ParticipantSearch (http://localhost:8080/packs/js/researcher/participant_search-b5182deadd4beda5bc5a.chunk.js:19662:5)
    at http://localhost:8080/packs/js/shared-70732d3819cae9f1039f.chunk.js:10179:89
    at C (http://localhost:8080/packs/js/vendor-d758c945e6c6b429b304.chunk.js:281921:37)
    at WithTracking (http://localhost:8080/packs/js/vendor-d758c945e6c6b429b304.chunk.js:291707:28)
    at div
    at Route (http://localhost:8080/packs/js/vendor-d758c945e6c6b429b304.chunk.js:281664:29)
    at Switch (http://localhost:8080/packs/js/vendor-d758c945e6c6b429b304.chunk.js:281866:29)
    at div
    at main
    at SidebarView (http://localhost:8080/packs/js/shared-70732d3819cae9f1039f.chunk.js:7852:5)
    at Router (http://localhost:8080/packs/js/vendor-d758c945e6c6b429b304.chunk.js:281299:30)
    at BrowserRouter (http://localhost:8080/packs/js/vendor-d758c945e6c6b429b304.chunk.js:280919:35)
    at ErrorBoundary (http://localhost:8080/packs/js/vendor-d758c945e6c6b429b304.chunk.js:110489:36)
    at UIBrowserRouter (http://localhost:8080/packs/js/shared-70732d3819cae9f1039f.chunk.js:14438:23)
    at Provider (http://localhost:8080/packs/js/vendor-d758c945e6c6b429b304.chunk.js:279191:20)
    at ParticipantSearchRouter (http://localhost:8080/packs/js/researcher/participant_search-b5182deadd4beda5bc5a.chunk.js:20604:5)
    at _class (http://localhost:8080/packs/js/shared-70732d3819cae9f1039f.chunk.js:10279:7)
    at WithTracking (http://localhost:8080/packs/js/vendor-d758c945e6c6b429b304.chunk.js:291707:28)
    at push../app/javascript/common/hoc/with_auth_user_context.jsx.__webpack_exports__.default (http://localhost:8080/packs/js/shared-70732d3819cae9f1039f.chunk.js:9878:89)


Resolution of scalajs:* files fails if the containing project aggregates another scalaJS project

When a project aggregates other projects, it runs the command sequentially on each of the aggregated projects and then finally on the specified project. However, in this mode, it adds a tab character to the start of each project's individual output.  This means that the output for fastLinkJSOutput and fullLinkJSOutput have a tab character in front and the plugin doesn't trim it, so path resolution fails.
PR incoming.

If anyone else runs into this before this is merged, you can disable aggregation for this particular command in your project via:
Compile / fastLinkJSOutput / aggregate := false
and
Compile / fullLinkJSOutput / aggregate := false


Documentation for aggregate_results

We have a script to aggregate results together, but it's not well documented. It should be.
https://github.com/zeno-ml/zeno-build/blob/main/zeno_build/reporting/aggregate_results.py

Not relevant anymore given #107