Add mixin for creating text-ellipses

Description of the use:
If you only need text ellipsis in only one line you can use:
@include text-ellipsis and it works with one line, and this is the result:

In case that you need text ellipsis in the third line of text you can pass the number of lines as a parameter:
@include text-ellipsis(3) and this is the result:

Can add your PR explanation in the code comments, and also update the readme/docs in this repo? :)

Done!

@ThaNarie does this meet your request or are additional actions needed?

@ThaNarie does this meet your request or are additional actions needed?


Fixed what we talked about before 758 lab

Fixed the file name and made a typo in the main declaration.

 Can you pull latest changes from main and then re-open a pull request?


selection.raise and selection.lower

moveToFront, moveToBack

This sounds like a really cool feature, can't wait to try it out!

yes man!that's very cool, you need'n to remove an element ,and then append or insert to its parent node.


Add scanner 'Get-ScheduledTaskActions' to get more info about Scheduled Tasks

This scanner will give more information about scheduled tasks and its actions.

Ignore this. New PR in #114


blockbench: 4.8.1 -> 4.9.3, build from source, rename package

Description of changes
Closes https://github.com/NixOS/nixpkgs/issues/279495
Supersedes https://github.com/NixOS/nixpkgs/pull/264654 (has the same fix)
Other than changing the version, I also changed the blockbench-electron package to use buildNpmPackage.
According to upstream, this should use electron_26. I tried it out, but after running the app for a few seconds, it suddenly crashed. Interestingly, any later electron version worked fine for me. For now, I set it to always use the latest version of electron.
I'd appreciate if someone could check if it's only a problem on my part.
I personally think that the package name should be blockbench instead of blockbench-electron. I changed the internal directory and file names to just blockbench, but kept the package name and executable name as blockbench-electron.
Edit:
I moved the package over to pkgs/by-name under the new name of blockbench
Other changes:

remove with lib; from meta
set meta.changelog
update meta.description
set meta.mainProgram
set meta.platforms (inherit from electron)
manually generate icons (using the --dir flag on electron-builder unfortunately doesn't generate the icons)
add myself to meta.maintainers

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

this looks wonderful at a first glance! I think you should go ahead with that rename, making sure to preserve backwards compat using pkgs/top-level/aliases.nix. maybe try by-name out if you're in the mood, blockbench is a good fit.

Huh, seems like all current PR workflows are getting internal server errored

@ckiee previously there was a line which added cc to the library path, which I removed:
--prefix LD_LIBRARY_PATH : "${lib.makeLibraryPath [ stdenv.cc.cc ]}"

Why was this needed originally? Was it just something needed for pre-packaged electron apps?

@ckiee previously there was a line which added cc to the library path, which I removed:
--prefix LD_LIBRARY_PATH : "${lib.makeLibraryPath [ stdenv.cc.cc ]}"

Why was this needed originally? Was it just something needed for pre-packaged electron apps?

yes, i think they just shipped some weird binary, i'm not too sure - probably a libstdc++ thing

@ofborg build blockbench

@ofborg build blockbench

@ofborg build blockbench

Oh sorry about that other PR I lost track of this one. I'll take a look.


Error loading server extension jupyter_tabnine

Jupyter tabnine was working fine but then for past couple of days it was giving the error mentioned in this issue
I tried uninstalling and then installing again.
This time I'm getting the following error:
[W 11:41:14.136 NotebookApp] Error loading server extension jupyter_tabnine
    Traceback (most recent call last):
      File "/Users/z0049x2/anaconda3/lib/python3.7/urllib/request.py", line 1317, in do_open
        encode_chunked=req.has_header('Transfer-encoding'))
      File "/Users/z0049x2/anaconda3/lib/python3.7/http/client.py", line 1229, in request
        self._send_request(method, url, body, headers, encode_chunked)
      File "/Users/z0049x2/anaconda3/lib/python3.7/http/client.py", line 1275, in _send_request
        self.endheaders(body, encode_chunked=encode_chunked)
      File "/Users/z0049x2/anaconda3/lib/python3.7/http/client.py", line 1224, in endheaders
        self._send_output(message_body, encode_chunked=encode_chunked)
      File "/Users/z0049x2/anaconda3/lib/python3.7/http/client.py", line 1016, in _send_output
        self.send(msg)
      File "/Users/z0049x2/anaconda3/lib/python3.7/http/client.py", line 956, in send
        self.connect()
      File "/Users/z0049x2/anaconda3/lib/python3.7/http/client.py", line 1392, in connect
        server_hostname=server_hostname)
      File "/Users/z0049x2/anaconda3/lib/python3.7/ssl.py", line 412, in wrap_socket
        session=session
      File "/Users/z0049x2/anaconda3/lib/python3.7/ssl.py", line 853, in _create
        self.do_handshake()
      File "/Users/z0049x2/anaconda3/lib/python3.7/ssl.py", line 1117, in do_handshake
        self._sslobj.do_handshake()
    ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1056)

    During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
      File "/Users/z0049x2/anaconda3/lib/python3.7/site-packages/notebook/notebookapp.py", line 1618, in init_server_extensions
        func(self)
      File "/Users/z0049x2/.local/lib/python3.7/site-packages/jupyter_tabnine/__init__.py", line 29, in load_jupyter_server_extension
        tabnine = TabNine()
      File "/Users/z0049x2/.local/lib/python3.7/site-packages/jupyter_tabnine/tabnine.py", line 96, in __init__
        self.download_if_needed()
      File "/Users/z0049x2/.local/lib/python3.7/site-packages/jupyter_tabnine/tabnine.py", line 157, in download_if_needed
        self._download()
      File "/Users/z0049x2/.local/lib/python3.7/site-packages/jupyter_tabnine/tabnine.py", line 160, in _download
        tabnine_sub_path = get_tabnine_sub_path()
      File "/Users/z0049x2/.local/lib/python3.7/site-packages/jupyter_tabnine/tabnine.py", line 167, in get_tabnine_sub_path
        version = get_tabnine_version()
      File "/Users/z0049x2/.local/lib/python3.7/site-packages/jupyter_tabnine/tabnine.py", line 176, in get_tabnine_version
        version = urlopen(_TABNINE_UPDATE_VERSION_URL).read().decode("UTF-8").strip()
      File "/Users/z0049x2/anaconda3/lib/python3.7/urllib/request.py", line 222, in urlopen
        return opener.open(url, data, timeout)
      File "/Users/z0049x2/anaconda3/lib/python3.7/urllib/request.py", line 525, in open
        response = self._open(req, data)
      File "/Users/z0049x2/anaconda3/lib/python3.7/urllib/request.py", line 543, in _open
        '_open', req)
      File "/Users/z0049x2/anaconda3/lib/python3.7/urllib/request.py", line 503, in _call_chain
        result = func(*args)
      File "/Users/z0049x2/anaconda3/lib/python3.7/urllib/request.py", line 1360, in https_open
        context=self._context, check_hostname=self._check_hostname)
      File "/Users/z0049x2/anaconda3/lib/python3.7/urllib/request.py", line 1319, in do_open
        raise URLError(err)
    urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1056)>

Any help would be much appreciated.
Thanks.

hey @vivekpayasi, What OS are you using?
From SO: Take a look at this post, it seems like for later versions of Python, certificates are not pre-installed which seems to cause this error.
See here: https://stackoverflow.com/questions/50236117/scraping-ssl-certificate-verify-failed-error-for-http-en-wikipedia-org
Please let me know if this works and I'll close. Thanks.

Hi @dimacodota,
I'm using MacOS and the SO link you shared helped! The issue is resolved for me now.
Thanks!

I'm running into this same problem while using anaconda jupyter on a remote linux server.
I have tried things like
conda install -c anaconda certifi
but it doesn't fix it. Any ideas?


[Bug] - can't work in pnpm workspace

Describe the bug
When right click on a nest project in pnpm workspace, it doesn't work
Platform

IDE Details:  IntelliJ IDEA 2024.2.3 (Ultimate Edition)
Build #IU-242.23339.11, built on September 25, 2024

is this related to this bug? If so can you see if the workaround described here would work?
https://github.com/dinbtechit/jetbrains-nestjs/issues/2#issuecomment-1877508490

is this related to this bug? If so can you see if the workaround described here would work?
#2 (comment)

Oh thx! It does work now

is this related to this bug? If so can you see if the workaround described here would work?
#2 (comment)

Sorry, the menu item occurred, but it still can't work when I tried to create a new service. Cuz when I clicked the menu item, nothing happened.

are you able to provide a screen recording demonstrating the issue?

are you able to provide a screen recording demonstrating the issue?

Sure, here is a gif

interesting... Can you send me the following to resolve this issue?

IDE log:

[!Important]
Before copying the logs -> try creating the service/controller/module using the nestjs menu.

On MacOS: (This is how you can get the logs). I assuming it would be similar for other operating systems.
IDE -> Help (menu) -> Show log in Finder -> idea.log

Can you create a sample repo with similar folder structure?

interesting... Can you send me the following to resolve this issue?

IDE log:

Important
Before copying the logs -> try creating the service/controller/module using the nestjs menu.
On MacOS: (This is how you can get the logs). I assuming it would be similar for other operating systems.
IDE -> Help (menu) -> Show log in Finder -> idea.log

Can you create a sample repo with similar folder structure?

idea.log
OK，here is the log

interesting... Can you send me the following to resolve this issue?

IDE log:

Important
Before copying the logs -> try creating the service/controller/module using the nestjs menu.
On MacOS: (This is how you can get the logs). I assuming it would be similar for other operating systems.
IDE -> Help (menu) -> Show log in Finder -> idea.log

Can you create a sample repo with similar folder structure?

https://github.com/tomwray13/nestjs-nextjs-trpc, u can use this repo to test
and here is my log: idea.log

I was able to reproduce the issue. I will try to fix this in the next release. I am in the middle of switching jobs so please bare with me.

Fixed in v0.0.3


App shortcut requires 3 clciks, lower it or make an additinal app shortcut icon for "freeze after quit"

Is your feature request related to a problem? Please describe.
Yes. "freeze after quit" options is a bit cucumbersome.  After enabling this option, apps vanishes. Now i can use the option " freeze unfreeze shortcut". However, it requires 3 clciks instead of 1.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Lets say i created a "app shortcut" for my browser. Now if i click it, 2 more pop up confirmation window appears. In total three clicks needed for the app to open. So it would nice to reduce required "clicks". Preferably only 1 click, like other regular apps.
Thanks every people behind it. i just downloaded it today. Its a nice one!

I think we can go to Settings - Freeze and Unfreeze, and use the Open Immediately, Unfreeze immediately then run when clicking the shortcut, Shortcut auto freeze or unfreeze, Extra confirmation when freeze, Run immediately after unfreezing options to reach the goal.
Is this the desired answer?


Can not change set parameters

I can normally print from Birch Bp-T3W printer without any problem. But When I need to change some parameter such as size or bold with the code 👍
adisyon_printer.set(codepage=None, size='2x', align='center', bold=True)
it gives error, saying set is undefined.
Python 3.8
python-escpos : latest

In V2.2 the set method does not have these parameters.
In v3 releases (currently up to v3.0a9) this is possible.


Create strings.xml

Added Ukrainian language

@xdsopl please add 🙏

Thanks. I've merged and integrated your translation file and the translation will be available with the next release.


Property name formatter

This project looks cool, it could potentially be useful for some things I work on. The main thing I would want though is the ability to extend it with a custom property name formatter.
The majority of the XML I work with looks like
<Line_num><System_Config></System_Config></Line_num>

Notice that the capitalizing is not consistent. I would extend it with the ability to convert the element names when they are assigned to the dynamic object to a CamelCase format.
What do you think?

Hi @mikehaas763, thanks for your idea! That sounds pretty legit. At least there should be a way for you to pass in your own formatting class, which extends an appropriate interface.
Sorry about the very late reply, I didn't even notice this issue! I'm still new to this open-source/GitHub world.
But I'll follow up on your feature request.


Adding initial civil comments README

Oops, I actually did this too! https://github.com/conversationai/unintended-ml-bias-analysis/blob/master/presentations/nuanced_metrics_dataset.md
I also don't think we're ready to release the name "Civil Comments" just yet (We need Aja from Civil Comments to be the first).


Is project DEAD or ALIVE?

Many pull request are still open, why?

Seems that project need to be moved to org with more core contributors 👍


Remove RazorGenerator generated files and replace it with RazorGenerator.MsBuild

YES! If this will remove all these turds from our code reviews, then definitely a must!


Roll Engine from 6de212bdaeb8 to e0c16f0f7f0b (3 revisions)

https://github.com/flutter/engine/compare/6de212bdaeb8...e0c16f0f7f0b
2021-06-10<EMAIL_ADDRESS>Revert "Add support for native callbacks to the macOS embedder test harness (#26623)" (flutter/engine#26693)
2021-06-10<EMAIL_ADDRESS>Updates the objectc docs script to use env variables. (flutter/engine#26666)
2021-06-10<EMAIL_ADDRESS>Roll Skia from d2e096069691 to 9d1cc0510039 (4 revisions) (flutter/engine#26691)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Commit queue failed; closing this roll.


Added solution using map()

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

Closes #XXXXX

@thecodingaviator The other solutions do not use bullet points.  Plus, I viewed the article locally and it looks fine to me (see screenshot below).  It does not look good on GitHub though, which is why we should test formatting-related issues locally first.

I think the changes are fine.  Merge it if you agree.

@vzla0094 Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


Idea: Link github discussions on the docs (if uses have more questions)

there is now a link to GitHub discussions on the landing page: https://docs.stackable.tech/home/stable/index.html


Update WorkManager according to Google recommendation

Following this recommendation:

WorkManager updated to latest beta version
If something fails, the job retries 3 times
There is a foreground notification during key download

conflict


Extend / enhance rollup build capabilities -  Feature/105

Description

Refactored tsconfig for api-client and composables
Refactored / extended rollup.config.js for api-client and composables
Updated build script to include rimraf to delete the preceding build files, and appended additional command to run type coverage report
Added type coverage config to the package.json for api-client and composables

Related Issue
https://github.com/vuestorefront/shopify/issues/105
Motivation and Context
The current setup is a "minimal configuration" approach, which is not necessarily bad, but I feel the added feature will make the overall build process and related developer activities more useful.
How Has This Been Tested?

Executed revised build
Validated outputs via build and application startup
Validated console message / warnings

Screenshots (if appropriate):
Types of changes

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

Checklist:

[ X] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[X ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ X] All new and existing tests passed.

Please resolve conflicts

Will work on conflicts and resubmit...thx

Let's have more discussion on this on #105 for now I've up #124 to address inconsistency with other integration. I am going to close this for now.


no metrics labels about pod namespace/name when Pod uses time slicing GPU

what did I do
I configured GPU time-slicing using GPU Operator.  The k8s extended resource name of time-slicing GPU is nvidia.com/gpu.shared。
See the extended resource in node pek01 where time-slicing is configured.
$ kubectl get node pek01 -o json | jq .status.allocatable
{
  "cpu": "40",
  "ephemeral-storage": "54967737049",
  "hugepages-1Gi": "0",
  "hugepages-2Mi": "0",
  "memory": "131788776Ki",
  "nvidia.com/gpu": "0",
  "nvidia.com/gpu.shared": "8",
  "pods": "110"
}

I created a Pod named test that uses extended resource nvidia.com/gpu.shared, pod test can run in node pek01, GPU Device ID is GPU-be6e8706-1ee7-9ce9-7c5e-80ebf0f66714.
$ kubectl get pod test -o wide
NAME   READY   STATUS    RESTARTS   AGE     IP               NODE    NOMINATED NODE   READINESS GATES
test   1/1     Running   0          2m51s   <IP_ADDRESS>   pek01   <none>           <none>
$ kubectl exec test -- env | grep NVIDIA_VISIBLE_DEVICES
NVIDIA_VISIBLE_DEVICES=GPU-be6e8706-1ee7-9ce9-7c5e-80ebf0f66714

what do I expect
I expect to get Pod info and GPU Device ID from dcgm-exporter's metrics' labels. DCGM Exporter's metrics do not contain pod info:
# HELP DCGM_FI_DEV_SM_CLOCK SM clock frequency (in MHz).
# TYPE DCGM_FI_DEV_SM_CLOCK gauge
DCGM_FI_DEV_SM_CLOCK{gpu="0",UUID="GPU-be6e8706-1ee7-9ce9-7c5e-80ebf0f66714",device="nvidia0",modelName="NVIDIA GeForce GTX 1080 Ti",Hostname="nvidia-dcgm-exporter-x7htp",DCGM_FI_DRIVER_VERSION="525.85.12",container="",namespace="",pod=""} 139
# HELP DCGM_FI_DEV_MEM_CLOCK Memory clock frequency (in MHz).
# TYPE DCGM_FI_DEV_MEM_CLOCK gauge
DCGM_FI_DEV_MEM_CLOCK{gpu="0",UUID="GPU-be6e8706-1ee7-9ce9-7c5e-80ebf0f66714",device="nvidia0",modelName="NVIDIA GeForce GTX 1080 Ti",Hostname="nvidia-dcgm-exporter-x7htp",DCGM_FI_DRIVER_VERSION="525.85.12",container="",namespace="",pod=""} 405

For now, DCGM exporter only support pod info in metrics labels when pod uses extend resource whose name is nvidia.com/gpu or whose name's prefix is nvidia.com/mig-(reference: dcgm exporter source code).
Will you support to provide Pod Info in metrics' labels when Pod uses extended resource nvidia.com/gpu.shared?

I have some issue.

same issue and expectations here.
we were able to fetch fine grained gpu util/mem info via cadvisor's accelerator metrics feature gate. each pod using time sliced gpu had its own gpu metrics. however those metrics were removed (since K8s 1.26 i guess) when we upgraded to K8s 1.28.
since then we have switched to dcgm exporter for gpu metrics but have to confess to the regression that we can no longer have gpu util/mem for time sliced gpu...
really looking forward to some updates here.

Cannot believe this issue has been here for more than half a year .... @nikkon-dev Would you please assign someone from your team to look into this?
I will append my setup here if it helps at all
apiVersion: v1
kind: Pod
metadata:
  annotations:
    cni.projectcalico.org/containerID: a8fed4acc578f331056a120a873b1b6e5478bada3b3f384196eb428dc66d23d3
    cni.projectcalico.org/podIP: <IP_ADDRESS>/32
    cni.projectcalico.org/podIPs: <IP_ADDRESS>/32
  creationTimestamp: "2023-11-09T09:23:35Z"
  generateName: nvidia-dcgm-exporter-
  labels:
    app: nvidia-dcgm-exporter
    app.kubernetes.io/managed-by: gpu-operator
    controller-revision-hash: 588696657b
    helm.sh/chart: gpu-operator-v23.6.0
    pod-template-generation: "4"
  name: nvidia-dcgm-exporter-tvmlp
  namespace: gpu-operator
  ownerReferences:
  - apiVersion: apps/v1
    blockOwnerDeletion: true
    controller: true
    kind: DaemonSet
    name: nvidia-dcgm-exporter
    uid: 07dd8cf4-9afc-438e-8aa6-feba5ccec844
  resourceVersion: "141728901"
  uid: e91b3f71-df43-42b1-86f1-354b93fb024f
spec:
  affinity:
    nodeAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
        - matchFields:
          - key: metadata.name
            operator: In
            values:
            - ip-10-0-6-97.ec2.internal
  containers:
  - env:
    - name: DCGM_EXPORTER_LISTEN
      value: :9400
    - name: DCGM_EXPORTER_KUBERNETES
      value: "true"
    - name: DCGM_EXPORTER_COLLECTORS
      value: /etc/dcgm-exporter/dcp-metrics-included.csv
    - name: DCGM_EXPORTER_KUBERNETES_GPU_ID_TYPE
      value: device-name
    image: nvcr.io/nvidia/k8s/dcgm-exporter:3.1.3-3.1.2-ubuntu20.04
    imagePullPolicy: IfNotPresent
    name: nvidia-dcgm-exporter
    ports:
    - containerPort: 9400
      name: metrics
      protocol: TCP
    resources: {}
    securityContext:
      privileged: true
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /var/lib/kubelet/pod-resources
      name: pod-gpu-resources
      readOnly: true
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: kube-api-access-7h5x4
      readOnly: true
  dnsPolicy: ClusterFirst
  enableServiceLinks: true
  initContainers:
  - args:
    - until [ -f /run/nvidia/validations/toolkit-ready ]; do echo waiting for nvidia
      container stack to be setup; sleep 5; done
    command:
    - sh
    - -c
    image: nvcr.io/nvidia/cloud-native/gpu-operator-validator:v23.6.0
    imagePullPolicy: IfNotPresent
    name: toolkit-validation
    resources: {}
    securityContext:
      privileged: true
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /run/nvidia
      mountPropagation: HostToContainer
      name: run-nvidia
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: kube-api-access-7h5x4
      readOnly: true
  nodeName: ip-10-0-6-97.ec2.internal
  nodeSelector:
    nvidia.com/gpu.deploy.dcgm-exporter: "true"
  preemptionPolicy: PreemptLowerPriority
  priority:<PHONE_NUMBER>
  priorityClassName: system-node-critical
  restartPolicy: Always
  runtimeClassName: nvidia
  schedulerName: default-scheduler
  securityContext: {}
  serviceAccount: nvidia-dcgm-exporter
  serviceAccountName: nvidia-dcgm-exporter
  terminationGracePeriodSeconds: 30
  tolerations:
  - effect: NoSchedule
    key: nvidia.com/gpu
    operator: Exists
  - effect: NoSchedule
    key: type
    operator: Equal
    value: gpu
  - effect: NoSchedule
    key: type
    operator: Equal
    value: rendering
  - effect: NoExecute
    key: node.kubernetes.io/not-ready
    operator: Exists
  - effect: NoExecute
    key: node.kubernetes.io/unreachable
    operator: Exists
  - effect: NoSchedule
    key: node.kubernetes.io/disk-pressure
    operator: Exists
  - effect: NoSchedule
    key: node.kubernetes.io/memory-pressure
    operator: Exists
  - effect: NoSchedule
    key: node.kubernetes.io/pid-pressure
    operator: Exists
  - effect: NoSchedule
    key: node.kubernetes.io/unschedulable
    operator: Exists
  volumes:
  - hostPath:
      path: /var/lib/kubelet/pod-resources
      type: ""
    name: pod-gpu-resources
  - hostPath:
      path: /run/nvidia
      type: ""
    name: run-nvidia
  - name: kube-api-access-7h5x4
    projected:
      defaultMode: 420
      sources:
      - serviceAccountToken:
          expirationSeconds: 3607
          path: token
      - configMap:
          items:
          - key: ca.crt
            path: ca.crt
          name: kube-root-ca.crt
      - downwardAPI:
          items:
          - fieldRef:
              apiVersion: v1
              fieldPath: metadata.namespace
            path: namespace

Server Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.0+rke2r2"


add references to function approach to reading nsg flow logs

add reference to Azure Function approach to consuming nsg flow logs, fix doc title.

@sebastus : Thanks for your contribution! The author, @mattreatMSFT, has been notified to review your proposed change.

@jimdial - Would you review the proposed changes? Thanks.

Matt Reat should also be involved. I discussed the changes with him
ahead of time. @mattreatMSFT
On Wed, Feb 6, 2019 at 5:17 PM Patricia (Trisha) McNary <
<EMAIL_ADDRESS>wrote:

@jimdial https://github.com/jimdial - Would you review the proposed
changes? Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/pull/24370#issuecomment-461107652,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABOrrNUK_3qABZ7eaeYOWZZcwfzNm66fks5vKw5BgaJpZM4aldF3
.

@jimdial can you please review and sign off if there are no additional comments?

#sign-off

@jimdial: I'm sorry - only the author of this article, @mattreatMSFT, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

@mattreatMSFT Looks like you'll need to add the sign-off comment for this to merge.

#sign-off


Ultrazed carrier card components review

We have to choose needed components of Ultrazed carrier card and port them in our board.
https://files.slack.com/files-pri/T107M5C0G-F65C4EUCW/aes-zu3eges-1-som-g-schematics.pdf
https://files.slack.com/files-pri/T107M5C0G-F64FCF4H1/ultrazeddatasheet.pdf

Schematic of Ultrazed IO carrier card
http://picozed.org/sites/default/files/documentations/PRJ-US1CAR.pdf

Preparing block diagram
https://docs.google.com/document/d/1Yx7d9yRpH7DAKFFM9LMtAUQNKGNkV_UcAUGlIjkJypE/edit

Ultrazed IO carrier cards PS MIO connections will be used as existing, just on PL side we will add our pheripherials

Block diagram is ready


Fixed #8813 -- Correctly validate from/to column index in redirect import

Fixes issue #6913 (and #8813 which is a duplicate). In addition this PR makes it impossible for the user to manipulate the values of the hidden import_file_name and input_format fields by signing these values.

Thanks for this @jaap3  reviewing now.
Just a heads up for future, it would have been easier to review this PR if it was split into two (one for the from/to import fix and another for the form tampering solution).
Not a huge problem right now and I know personally what it's like to see a problem and want to fix more than one at a time.
Sometimes, if the changes overlap the same files, you can do an initial PR with the bare bones fix for the bug and then a a second PR that includes that commit and the additional improvement.

The other thing that helps is if you tick the 'allow pushing to remote repository' when you create a PR - it means we can push a refined version of your commit (with changelog etc) to your branch.
All good though, I will merge on main and reference this PR.

Merged in via 649a8623a0449bad6e935cff73fae36a6a20c2e8
Thanks so much @jaap3 !


TypeScript function names are no longer colourised

Since the new textmate based colourised, function names are no longer colorized for TypeScript. This is clearly not intended as the same code that will be colourised in JavaScript will not be colourised in TypeScript.

It will colorized in all themes except "Light"

It will colorize in all themes except "Light"

@xlexi  Can you give more information, maybe a screenshot.
What color theme are you using?
Do you mean function declarations or references?

Try "Light" theme, it's only theme that not colorizing function names (including C#).

Appologies, I meant the function name in function calls. Here is an example showing setTimeout using the default "Dark" theme in TypeScript (Left) and JavaScript (Right)

Fixed function calls in in light and dark themes.
 The color was not intended. The light and dark theme only use a reduced number of colors and themes.


Cannot deploy the website?

Describe the bug
No deployment URL is issued
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-hrynkt
Steps to reproduce
Press deploy
Expected behavior
See a deployment URL
Screen Recording / Screenshot
No response
Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 131
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 96319977,
  "usedJSHeapSize": 89058713,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = andaydvice
Chat ID = 1700f37fd1dc

Additional context
No response

https://app.screencast.com/7guvgBQAWQc73

Deploy and Downloading both ain't working ?

Try to open it in Stackblitz and click on bolt.new on the left side and try then again. I had it too in past. The workaround like that fix always.


Paths to the SVG sprite via SCSS return 404

Firstly, thanks for this plugin! Secondly, you'll have to forgive this ramble, as I'm new to vitejs.
I'm using vitejs as a development environment, but mainly to compile my javascript and sass. I'm using Craft CMS as a backend, so all assets export to a dist folder, and Craft CMS picks them up from there via a plugin.
I'm using your SASS mixin to load an icon from my sprite file into my sass like so:
@use '../mixins' as *;

h1 {
    &:before {
        content: '';
        display: inline-block;
        @include sprite(
            $name: icon-example,
            $include-size: box,
            $type: fragment
        );
    }
}

When my CSS is generated for production this works great, apart from the path to assets are wrong and I get a note in the console.
Note in console:
/__spritemap#sprite-icon-example-view in /var/www/html/build/scss/app.scss didn't resolve at build time, it will remain unchanged to be resolved at runtime
Actual path to sprite in generated CSS:
https://vite.local.ddev.site/assets/spritemap.1242586e.svg#sprite-icon-example-view
Expected path to sprite:
https://vite.local.ddev.site/dist/assets/spritemap.1242586e.svg#sprite-icon-example-view
When the vite dev server is running, it returns the following path which returns a 404:
https://vite.local.ddev.site/__spritemap__1242586e.svg#sprite-icon-example-view
Here's a cut down version of my vite.config.js:
import {defineConfig} from 'vite';
import path from 'path';
import VitePluginSvgSpritemap from '@spiriit/vite-plugin-svg-spritemap';

export default defineConfig(({command}) => ({
    base: command === 'serve' ? '' : '/dist/',
    publicDir: path.resolve(__dirname, './build/static'),
    build: {
        emptyOutDir: true,
        manifest: true,
        outDir: path.resolve('./public/dist'),
        sourcemap: true,
        rollupOptions: {
            input: {
                // scss imported via my js
                'js/app': './build/js/app.js',
              },
            output: {
                entryFileNames: '[name].[hash].js',
                chunkFileNames: '[name].[hash].js',
                assetFileNames: '[ext]/[name].[hash].[ext]',
            }
        },
    },
    plugins: [
        VitePluginSvgSpritemap('./build/icons/*.svg', {
            prefix: 'sprite-',
            output: {
                filename: '[name].[hash].[ext]',
              },
            styles: {
                lang: 'scss',
                filename: 'build/scss/mixins/_sprite.scss',
            }
        }),
    ],
}));

Any help appreciated.

Hello, for the note in the console I didn't find a fix yet. It doesn't cause a bug, it's just a warning from ViteJS.
In development with a backend, you need to manage the url manually because vitejs doesn't rewrite your HTML.
For example :
https://github.com/SpiriitLabs/vite-plugin-svg-spritemap/blob/a215dc79b7685bd47c89c0f6614eeceb1ec63341/demo/server/index.html#L32
I will update the readme to be more clear about this.

Hello, for the note in the console I didn't find a fix yet. It doesn't cause a bug, it's just a warning from ViteJS.

No problem!

In development with a backend, you need to manage the url manually because vitejs doesn't rewrite your HTML.

I read about this. My backend is simply loading the compiled CSS, so won't have the ability to rewrite any URLS within the CSS.
As I'm using your SASS mixin, I don't have any control over the URL either, which leaves me with 2 options:

Re-write your SASS mixin
Use PostCSS to rewrite the URLs on build

I think the underlying problem is: your plugin doesn't seem to respect vite js build.outDir setting.

Oh ok, I didn't test the fragment option in the mixin with this context and It will not work. I need to check if I can make it work for this context. You can use the default option using base64 url @include sprite($name);.

Hi @Applelo - I'm going to close this issue as I have found a work around for using your SASS mixin in dev/build modes for my use case.
If anybody else stumbles across this post, this might help you. I have the following in my vite.config.js file:
css: {
    preprocessorOptions: {
        scss: {
            // conditionally set SASS $sprite-type value
            additionalData:  command === 'serve' ? `@use 'build/scss/theme/setup' with ($sprite-type: uri);` : `@use 'build/scss/theme/setup' with ($sprite-type: fragment);`,
        },
    },
},

And use the mixin like so:
@use '../mixins' as *;
@use '../theme' as *;

h1 {
    &:before {
        content: '';
        display: inline-block;
        @include sprite(
            $name: icon-example,
            $include-size: box,
            $type: $sprite-type
        );
    }
}

Now in dev, the sprite mixin will base64 the url (type uri). In production the url will be given to the sprite file (type fragment).


Add minimal JavaScript wrapper

The idea here is to allow the RDKit to be used from JavaScript so that we can add chemical capabilities to web applications.
Rather than attempting a comprehensive wrapper (like RDKitJS), this exposes a small set of key functionality. I think the general approach, including this actual library, can be useful for other wrapper projects in the future.
This initial set of functionality is not complete, but it's intended to already be directly useful. Here's what's there: https://github.com/greglandrum/rdkit/blob/dev/js_wrappers/Code/MinimalLib/jswrapper.cpp
There's a Dockerfile here that shows how to setup an environment to build this and do a build: https://github.com/greglandrum/rdkit/blob/dev/js_wrappers/Code/MinimalLib/docker/Dockerfile
Some questions/things to think about:

This currently uses three different methods to return non-trivial values: get_substruct_match() function returns a wrapped std::vector. This results in an API that I find strange on the JS side. get_descriptors() returns JSON that can be trivially parsed into a JS object. get_morgan_fp() returns a bitstring (e.g. "01000111010"). Would it be better to pick a single return value type (i.e. JSON) or, perhaps JSON for get_descritors() and get_substruct_match() but still the string for get_morgan_fp().
Which other pieces of functionality should be there?
Is it worth adding build options to the wrapper itself so that people who are really only interested in a subset of what's there can create a super-stripped down version?

I haven't done any benchmarking yet, that would also be interesting at some point in the future.

@thegodone : it would be great if you could also take a look at this.

To give a taste of what the wrapper can do, and to provide pre-built .js and .wasm files for anyone who wants to test, I've put a build online:
https://www.rdkit.org/temp/demo/demo.html
Having a long-term version of this available online makes sense, but that would require a somewhat better styled page. :-)

Merging after conversations with @bp-kelley and @thegodone

This is amazing!
But, how do I do in win10 with conda3?
I like to use in a Flask project.
Thanks for all!
Ed

@edtrawtmam I'm not sure what you're asking.
This is a JS wrapper, so operating system and python version aren't really relevant.
There's an RDKit blog post about the wrappers that may be helpful: http://rdkit.blogspot.com/2019/11/introducing-new-rdkit-javascript.html


Add language to user object.

Changes
Adds language field to the user, so we can collect that. References DoSomething/phoenix#6224.

For review: @angaither or @weerd

:globe_with_meridians:


Use node legacy host ip on older kubernetes versions

Can one of the admins verify this patch?

Just to clarify, the current assumption is that older kubernetes versions should not be using the latest heapster. We bundle a specific version of heapster with a kubernetes release. We can re-think that strategy in the future once the kube API and some of the internal code stabilizes.

ok to test

LGTM. Will merge once the tests pass.

@cadvisorJenkinsBot: ok to test


Please document performance

Hi, this seems like a nice library and I would like to use it, but I have no idea what runtime behavior to expect because the documentation makes no mention of time complexities and neither is the internal data structure described anywhere.
Please consider documenting performance characteristics of operations in the Haddocks.

Absolutely, can (and will) do.
The complexity for each operation is the same as for Data.Set.
This then is faster depending the shape of the data.

Absolutely, can (and will) do.

Great, thanks!

The complexity for each operation is the same as for Data.Set.
This then is faster depending the shape of the data.

That's very nice, I'll likely use it then.

The complexity for each operation is the same as for Data.Set. This then is faster depending the shape of the data.

Are you sure? It looks like size is O(n) instead of O(1) as for Set, for example.

The complexity for each operation is the same as for Data.Set. This then is faster depending the shape of the data.

Are you sure? It looks like size is O(n) instead of O(1) as for Set, for example.

Yes, I'm sure. Although since writing that I did make the size operation O(n) compared to Data.Set.


DaggerAppComponent

In module presentation, class App, your method intializeInjector()
You have appComponent = DaggerAppComponent
in the import statements it shows its supposed to be in the
import com.buddysearch.android.presentation.di.component.DaggerAppComponent;

only see ActivityComponent and AppComponent

According to Dagger 2 User Guide:

Dagger 2 is the first to implement the full stack with generated code. The guiding principle is to generate code that mimics the code that a user might have hand-written to ensure that dependency injection is as simple, traceable and performant as it can be.

It means, that if no compile errors or DI issues were found in your project, then your DaggerAppComponent will be generated automatically after you run (build) the project for the first time.
Let me know if you have some troubles with it.

Thanks again!

You are welcome. Please let me know if you need some help.
Also, pay attention, that this repository also have develop branch that has newer updates than master. But in final case, develop will be merged into master as a new application release.

Yeah, I was checking that out. I am using firebase create and sign in with email and password. I saw you were heading in that direction too.


Add blank slate and loading animation

Add blank slate for the following conditions

Initially when nothing is scanned
When there is no result in the scan

Also, add animation in empty table view when scan is in progress

Hi @ibreakthecloud :-) may I work on this enhancement?

@Le-Roi777 Certainly :)

@Le-Roi777 Certainly :)

Awesome! Keep you posted.


Update DubboCodec.java

fix issue #3537: 新旧版本兼容问题
Brief changelog
dubbo 反序列化对分片流操作时的兼容性支持
Verifying this change
1、DubboCodec 解码时，对is流进行多次操作
            ObjectInput in = CodecSupport.deserialize(channel.getUrl(), is, proto);
            if (status == Response.OK) {
                Object data;
                if (res.isHeartbeat()) {
                    data = decodeHeartbeatData(channel, in);
                } else if (res.isEvent()) {
                    data = decodeEventData(channel, in);
                } else {
                    DecodeableRpcResult result;
                    if (channel.getUrl().getParameter(
                            Constants.DECODE_IN_IO_THREAD_KEY,
                            Constants.DEFAULT_DECODE_IN_IO_THREAD)) {
                        result = new DecodeableRpcResult(channel, res, is,
                                (Invocation) getRequestData(id), proto);
                        result.decode();
                    } else {
                        result = new DecodeableRpcResult(channel, res,
                                new UnsafeByteArrayInputStream(readMessageData(is)),
                                (Invocation) getRequestData(id), proto);
                    }
                    data = result;
                }
                res.setResult(data);

2、当序列化工具使用分片读取is时，将造成result.decode()解码错误;比如fst.

Codecov Report

Merging #3568 into 2.6.x will decrease coverage by 0.06%.
The diff coverage is 33.33%.

@@             Coverage Diff              @@
##              2.6.x    #3568      +/-   ##
============================================
- Coverage     47.18%   47.11%   -0.07%
+ Complexity     4396     4390       -6
============================================
  Files           565      565
  Lines         25084    25087       +3
  Branches       4422     4422
============================================
- Hits          11835    11820      -15
- Misses        11426    11439      +13
- Partials       1823     1828       +5

Impacted Files
Coverage Δ
Complexity Δ

...m/alibaba/dubbo/rpc/protocol/dubbo/DubboCodec.java
58.41% <33.33%> (-1.79%)
13 <0> (ø)

...ba/dubbo/remoting/transport/netty/NettyClient.java
74.13% <0%> (-8.63%)
12% <0%> (-1%)

...om/alibaba/dubbo/rpc/filter/ActiveLimitFilter.java
83.33% <0%> (-5.56%)
6% <0%> (-1%)

...rpc/protocol/dubbo/telnet/InvokeTelnetHandler.java
54.21% <0%> (-3.62%)
13% <0%> (-2%)

...ba/dubbo/remoting/transport/netty/NettyServer.java
67.85% <0%> (-3.58%)
8% <0%> (-1%)

.../com/alibaba/dubbo/monitor/dubbo/DubboMonitor.java
87.85% <0%> (-1.87%)
15% <0%> (ø)

...baba/dubbo/remoting/transport/mina/MinaClient.java
57.81% <0%> (-1.57%)
8% <0%> (-1%)

Continue to review full report at Codecov.

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

@linhuaichuan  Can you please add some unit test or integration test to verify the change ?

1、CodecSupport.deserialize 反序列化 is ，当序列化工具使用分片读流时，当RpcResult序列化byte大于分片值时，将引起is的startIndex变动。比如fst工具：org.nustaq.serialization.util.FSTInputStream 默认使用 8000 byte读取is。
2、result.decode() 也是使用CodecSupport来反序列is。若startIndex产生变动，将引起RpcResult 读取带序列化byte不正确。最终可能产生 #3537 bug。

哇哈哈
所以
要解决了么？
什么时候发？

this change looks reasonable, but it will not solve issue #3537.

I will port your change into main trunk with this: https://github.com/apache/incubator-dubbo/issues/3991. Once it's in, I will merge your change too. @linhuaichuan

The same issue with https://github.com/apache/dubbo/issues/4612
Why nobody take care of old stable version ?

Another place also has this code
Why not modify all?

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

@linhuaichuan hi, thanks for your contribution
pls resolve conflicts with the latest master branch

Close for long time no response.
Please feel free to reopen if you have any question.


Add widgetColor option

Allow passing a color to builder.widgetColor() in the declaration of dialog params.

thanks @jamiesanerd , would you mind mentioning this in the readme?

@jamiesanerd is this done?

I guess it is done, thanks!


Implement Basic Authentication

This commit adds support for basic authentication - and fixes
a few bugs along the way.

[Current coverage][cc-pull] is 86.25%

Merging [#174][cc-pull] into [master][cc-base-branch] will decrease coverage by 1.28%

@@             master       #174   diff @@
==========================================
  Files            36         37     +1
  Lines           770        800    +30
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            674        690    +16
- Misses           96        110    +14
  Partials          0          0

[][cc-pull]

Powered by Codecov. Last updated by [0f5d850...9162750][cc-compare]
[cc-base-branch]: https://codecov.io/gh/TryGhost/Ghost-Desktop/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/TryGhost/Ghost-Desktop/compare/0f5d8502dcdcca848f049fef5f76fbe5a8806bf4...9162750b66d29d49a02e324edb913c3742e435c6?src=pr
[cc-pull]: https://codecov.io/gh/TryGhost/Ghost-Desktop/pull/174?src=pr


ServerPath

[VULNERABLE]: HOST: https://<IP_ADDRESS> | Code: 200 | ServerPath: The zip file did not contain an entry exportDescriptor.properties
root@cp:~/.cache/CVE-2023-22518#

Hi @sec13b ,
We request you to provide the image of the output and your target confluence server version.
Kind regards,
@RevoltSecurities

Hi @sec13b ,
Please send the image of the output you got from the exploiter tool
Kind regards,
@RevoltSecurities


Demonstrate state-of-the-art multilingual QA performance in top leaderboards

jaydesen created the following on Jan 25:
The datasets being considered here are : TyDi, XOR-TyDi and Mr. TyDi
Example snapshot from XOR TyDI dataset and its task variations:

Original issue: https://github.ibm.com/ai-foundation/PrimeQA/issues/4

duplicate https://github.com/primeqa/primeqa/issues/14


API to expand/collapse custom TreeItems

I am looking for an API to expand or collapse a specified TreeItem (both deep and shallow).
For example, I would like to provide a Collapse All command for some of my trees to provide a deep collapse (all descendants from the specified item should collapse). Same with expand.
Here are a few more examples: https://github.com/Microsoft/vscode/issues/30288#issuecomment-369989263, https://github.com/eamodio/vscode-gitlens/issues/383, https://github.com/eamodio/vscode-gitlens/issues/275
Something similar to reveal that would allow for specifying deep (affects all descendants) or not.
expand(element: T, options?: { deep: boolean } = { deep: false }): Thenable<void>
collapse(element: T, options?: { deep: boolean } = { deep: false }): Thenable<void>

@eamodio Need of this API is to implement a global expand or collapse all actions? Or is there other requirements?

@sandy081 is there anyway to get this bumped up from the backlog? I know a few other extension devs anxiously awaiting this 😄

Planning for October :)

@eamodio Here is the plan to support this.
Took your suggestion to support expand using reveal api.
reveal(element: T, options?: { select?: boolean, focus?: boolean, expand?: boolean }): Thenable<void>;
collapseAll will be an opt in action while registering the view in package.json. When opted in, collapse all action will be shown in the view header.

Will expand be 1 level or all levels?

1 level and not recursive.

Any chance for reveal(element: T, options?: { select?: boolean, focus?: boolean, expand?: boolean | number }): Thenable<void>;
Where is it is fully recursive when true or recursive to the specified number?
https://github.com/eamodio/vscode-gitlens/issues/275 requires a recursive expansion

Where it is fully recursive when true or recursive to the specified number?

Recursive expand has the potential for performance suicide that's why we are pushing back on it. The boolean | number proposal isn't bad we are scared of large numbers here. How many levels to you have to expand? Is it feasible for you to "manually" expand them?

Ah, yeah, that make a lot of sense. I think in most cases, having the option to expand the item or the item and its children is probably enough.

Only up to the items children.
Where am I getting the list of children to iterate over to then reveal? Do I have to call item.getChildren() and then make sure that each item maintains an active list of it's children (often I don't maintain a list as the list is already being maintained by vscode and it makes it more complicated to handles refreshes as there are no events when items are removed from the tree)

Ok. I will allow the API to take number of levels boolean | number. If

true - expands the element only

/**
		 * Reveals the given element in the tree view.
		 * If the tree view is not visible then the tree view is shown and element is revealed.
		 *
		 * By default revealed element is selected and not focused.
		 * In order to not to select, set the option `select` to `false`.
		 * In order to focus, set the option `focus` to `true`.
		 * In order to expand the revealed element, set the option `expand` to `true` or `1`. To expand recursively set `expand` to the number of levels to expand.
		 * **NOTE:** You can recursively expand to maximum only 3 levels.
		 *
		 * **NOTE:** [TreeDataProvider](#TreeDataProvider) is required to implement [getParent](#TreeDataProvider.getParent) method to access this API.
		 */
		reveal(element: T, options?: { select?: boolean, focus?: boolean, expand?: boolean | 1 | 2 | 3 }): Thenable<void>;


worker_process_entrypoint FAILED

llama inference start
/opt/LLama_Agentic_System/llama3_1venv/lib/python3.11/site-packages/llama_toolchain/utils.py:43: UserWarning:
The version_base parameter is not specified.
Please specify a compatability version level, or None.
Will assume defaults for version 1.1
initialize(config_path=relative_path)
Loading config from : /root/.llama/configs/inference.yaml
Yaml config:
inference_config:
impl_config:
impl_type: inline
checkpoint_config:
checkpoint:
checkpoint_type: pytorch
checkpoint_dir: /root/.llama/checkpoints/Meta-Llama-3.1-8B-Instruct/original/
tokenizer_path: /root/.llama/checkpoints/Meta-Llama-3.1-8B-Instruct/original/tokenizer.model
model_parallel_size: 1
quantization_format: bf16
quantization: null
torch_seed: null
max_seq_len: 16384
max_batch_size: 1

Listening on :::5000
INFO:     Started server process [6765]
INFO:     Waiting for application startup.

initializing model parallel with size 1
initializing ddp with size 1
initializing pipeline with size 1
E0725 12:48:53.920000<PHONE_NUMBER>11456 torch/distributed/elastic/multiprocessing/api.py:702] failed (exitcode: -9) local_rank: 0 (pid: 6774) of fn: worker_process_entrypoint (start_method: fork)
E0725 12:48:53.920000<PHONE_NUMBER>11456 torch/distributed/elastic/multiprocessing/api.py:702] Traceback (most recent call last):
E0725 12:48:53.920000<PHONE_NUMBER>11456 torch/distributed/elastic/multiprocessing/api.py:702]   File "/opt/LLama_Agentic_System/llama3_1venv/lib/python3.11/site-packages/torch/distributed/elastic/multiprocessing/api.py", line 659, in _poll
E0725 12:48:53.920000<PHONE_NUMBER>11456 torch/distributed/elastic/multiprocessing/api.py:702]     self._pc.join(-1)
E0725 12:48:53.920000<PHONE_NUMBER>11456 torch/distributed/elastic/multiprocessing/api.py:702]   File "/opt/LLama_Agentic_System/llama3_1venv/lib/python3.11/site-packages/torch/multiprocessing/spawn.py", line 170, in join
E0725 12:48:53.920000<PHONE_NUMBER>11456 torch/distributed/elastic/multiprocessing/api.py:702]     raise ProcessExitedException(
E0725 12:48:53.920000<PHONE_NUMBER>11456 torch/distributed/elastic/multiprocessing/api.py:702] torch.multiprocessing.spawn.ProcessExitedException: process 0 terminated with signal SIGKILL
Process ForkProcess-1:
Traceback (most recent call last):
File "/root/anaconda3/lib/python3.11/multiprocessing/process.py", line 314, in _bootstrap
self.run()
File "/root/anaconda3/lib/python3.11/multiprocessing/process.py", line 108, in run
self._target(*self._args, **self._kwargs)
File "/opt/LLama_Agentic_System/llama3_1venv/lib/python3.11/site-packages/llama_toolchain/inference/parallel_utils.py", line 175, in launch_dist_group
elastic_launch(launch_config, entrypoint=worker_process_entrypoint)(
File "/opt/LLama_Agentic_System/llama3_1venv/lib/python3.11/site-packages/torch/distributed/launcher/api.py", line 133, in call
return launch_agent(self._config, self._entrypoint, list(args))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/LLama_Agentic_System/llama3_1venv/lib/python3.11/site-packages/torch/distributed/launcher/api.py", line 264, in launch_agent
raise ChildFailedError(
torch.distributed.elastic.multiprocessing.errors.ChildFailedError:
=====================================================
worker_process_entrypoint FAILED

Failures:
<NO_OTHER_FAILURES>
Root Cause (first observed failure):
[0]:
time      : 2024-07-25_12:48:53
host      : ip-119-181-1-31.ec2.internal
rank      : 0 (local_rank: 0)
exitcode  : -9 (pid: 6774)
error_file: <N/A>
traceback : Signal 9 (SIGKILL) received by PID 6774

LLaMA says: Chat
🦙
I'm an open-source chatbot.
I can explain concepts, write poems and code, solve logic puzzles, or even name your pets.
What do you want to chat about?
🥸
Hi any idea how to fix: Root Cause (first observed failure): [0]: time : 2024-07-25_12:48:53 host : ip-119-181-1-31.ec2.internal rank : 0 (local_rank: 0) exitcode : -9 (pid: 6774) error_file: <N/A> traceback : Signal 9 (SIGKILL) received by PID 6774
🦙
The error message you're seeing typically indicates that your process was terminated by the operating system, usually due to resource constraints such as running out of memory. Here are some steps you can take to try and resolve the issue:

Check system logs: Look into system logs (e.g., /var/log/syslog or /var/log/messages) around the time of the error (2024-07-25_12:48:53) to see if there are any messages indicating why the process was killed.
Monitor system resources: Use tools like top, htop, or atop to monitor your system's resource usage (CPU, memory, disk, etc.) while running your application. This can help you identify if you're running low on any resources.
Increase resources: If you're running your application on an AWS EC2 instance (as indicated by the hostname ip-119-181-1-31.ec2.internal), you might need to upgrade to a larger instance type with more memory or adjust your application's configuration to use fewer resources.
Configure OOM Killer: If your process is being killed by the Out-of-Memory (OOM) Killer, you might want to consider configuring it to spare your critical processes or to start killing other, less important processes first.
Check your application's memory usage: Use profiling tools to analyze your application's memory usage patterns. For example, if you're running a Python application, you could use tools like mprof or line_profiler to identify memory leaks.
Implement retries or checkpoints: If your application is performing a long-running task, consider implementing retries or checkpoints so that if it's terminated, it can resume from where it left off.
Check for any resource-intensive tasks: Review your code for any resource-intensive tasks that might be causing the system to run low on resources.
System configuration: Ensure your system's configuration is optimal for your workload. This includes adjusting ulimits, kernel parameters, or other system settings.
If none of these suggestions help, please provide more details about your application, its environment, and any relevant configurations, and I'll do my best to provide a more specific solution.


Cannot rename Path node

Godot version:
3.2.3.stable
OS/device including version:
Windows 10.0.19042.630
Issue description:
I added a Path node and a PathFollow node as a child. When I try to rename the Path node, I can edit the name but after I hit enter it reverts to the name "Path". This only seems to happen on a particular scene that I have, I've tried with other scenes and it seems to work fine.
Steps to reproduce:

Open the project.
Open the scene "Main".
Click on the node "Path" to rename it,
Rename it.
Hit enter.

Minimal reproduction project:
squash_the_creeps_start_1.1.0.zip

Here's a recording of the issue:
2020-12-07 10-15-51.zip

I'm able to reproduce that renaming is generally somewhat glitchy, in the sense that I occasionally need to rename a node twice for it to work. Same thing in your provided minimal reproduction project, however ultimately I'm always able to rename a node.

Still occur in 41e9028.


Bug fix for equipment dropdown missing

Replaced data fetcher component with React 18 loader/useLoader functionality which asynchronously fetches the equipments.

What caused the field to be missing?

@khelwood
The page requires 'equipments' to be fetched from the core to populate the dropdown, and the dropdown visibility is based on whether there are equipments or not.
There are two fixes -

I believe the equipment field should be visible in all cases, whether there are equipments or not. So, I have removed that checking so that even in cases where it couldn't fetch equipments, it will display an empty dropdown box, which I believe is more intuitive.

Currently, the fetching of equipments is achieved using a higher-order component (HOC) called DataFetcher, which fetches data and passes it as props to the component. However, with the React 18 upgrade, a new approach has been introduced using the loader and the useLoader hook. This facilitates asynchronous calls to fetch any props necessary for page loading.
Despite the React 18 upgrade, the existing approach has been retained as it was working and to avoid extensive changes, given its widespread use across many pages.
But as it is showing inconsistencies, this is now changed to loader function.

Also, I think it would be better to replace all the existing pages using this loader function, as this is the second time a similar issue has been reported. Therefore, I have added a story for it.
https://github.com/orgs/sanger/projects/9/views/2?pane=issue&itemId=47310511

Sounds good. If this is a change to the recordInPlace page, have you checked there are no uses of that page that are not linked to an equipment?

Sounds good. If this is a change to the recordInPlace page, have you checked there are no uses of that page that are not linked to an equipment?

Updated


loading of S3 assets in admin media index page takes too long

Hi, I've just noticed that after using for several days the now working moduler branch with added native S3 integration as documented in this closed issue
https://github.com/owen2345/camaleon-cms/issues/210
when browsing the admin media index page the retrieval from S3 is too slow (it's kinda running like London traffic).
I've been playing with the methods in the UploaderHelper and I've actually find out that this closure is the affected line of code that is actually clogging images retrieval from S3.
https://github.com/owen2345/camaleon-cms/blob/moduler/app/helpers/camaleon_cms/uploader_helper.rb#L185
I am saying this since if I just try to instantiate a new @fog_connection I authenticate and I just fetch the files the retrieval procedure is blazing fast, so this pointed me to think that this got something to do with camaleon itself and particularly with the resident logic that has been used to display assets on the media index page.
Since there is no test and no documentation for this part, I was wondering if you can take a look at this issue when you got time because this way S3 integration is working, but it's just NOT production ready :cry:
Thanks in advance.

@owen2345  Still about this matter, could you please shed some light on @tree[:files] ???
https://github.com/owen2345/camaleon-cms/blob/bc204d858b6e02425e93ad62ea58790cd586b582/app/views/camaleon_cms/admin/media/_files_list.html.erb#L1
This is used in the partial for the file retrieval part but it's not clear to me how and why it is used there???
By reviewing the slow running method I've understand you are trying to add references from S3 from the @fog_connection to some sort of hash ? So is that used on the admin media index page to display the file list???
Could you also provide the final hash structure that you are trying to build and pass to the view to build the partial so I can understand how to try to replicate that hash (is that used to be passed as json somewhere????) and see if I can tweak that method?
Thanks in advance!

Hi @yortz
the @tree[:files] line is filtering the file format (images, audio, video, ...)
It is creating a json with file/folder structure, sample:
root folder
  {
      folders: {
      child_folder1:{
          folders: {},
          files: []
      }
    }, files: [
        {name: '', file: '', size:' ', url: ''}
    ],
     path: ""
  }

Every request only use this json to get inner folders and inner files for current path
Regards,

Thanks for your support on this, I actually came up with some simpler/faster solution for S3 file retrieval
 @fog_connection_bucket_dir.files.select do |file|
    File.dirname(file.key).include?(@fog_connection_hook_res[:thumb_folder_name])
  end.group_by {|s| s.key.scan /^\d{1}\/.*\// }

This seems to be enough to get the files object from S3. I am now working on the views trying to change the files_list.html.erb partial that displays images and folder structure on the media index page. As I told you that method takes too long to respond; now the hard part would be to recreate the json structure to feed the js to render the file browser on that page :cry:

Great!

https://github.com/owen2345/camaleon-cms/pull/241


router config - nested edge.csr - deprecated or required?

The router config ref says the nested edge.csr section is deprecated, favoring the top-level csr section, but the nested edge.csr seems to also be required. Without it, the router run.go panics:

required section [edge.csr] not found

I was unable to work around by defining empty edge.csr like this.
edge: {}

edge:
    csr: {}

or
edge:
    csr:

I can start the router without panic if I provide both csr and edge.csr, but csr is then ignored when composing the CSR.


Improvements for FileProvider

Documentation for the FileProvider was not linked in the official documentation.
Secondly: using the file provider failed when not calling php app/console uecode:qpush:build before. Using the methods of the Filesystem class is more consistent with the remainder of the code of the FileProvider and also creates parent directories when they are missing.

A new inspection was created.

The inspection completed: No new issues

@czenker - thanks for the contribution!  Looks good to me, is ready to merge?

@kmfk Yes - works for me :)
I didn't test the doc rendering, but the changes there are simple enough to not break.

@czenker thanks!


Upgraded kcp to release-0.4 for the local dev env

With the 0.4 release, removed the flags that are no more in use.

/lgtm
I may follow up on this PR to use go install to download & install the kcp binary. So far it looks like we only need kcp start.

@adambkaplan Yes, we only need kcp start (same goes for kcp running inside a pod too).
The kcp binary is generated from this line. (The make build command triggers a go build $params command which generates the kcp binary)

/lgtm
I may follow up on this PR to use go install to download & install the kcp binary. So far it looks like we only need kcp start.

yes that's a good point. However:

kcp uses "replaces" in go.mod, which seems to get into the way of go install github.com/kcp-dev/kcp@version
the existing approach allowed to follow a release branch (the prototype versions: 0.3 and now 0.4). Patches to release branches are not consistently tagged in kcp and with go install it is not possible to install binaries for a specific branch. Although, we may be fine without that.


What does the color of the Icon component do? Is it the background color?

I see that the color of the icon is set in the Button, but it has no effect.

@CooperCao thank you for your feedback and I apologize for the long delay. We are currently working to overhaul this repo.
If using a pure white PNG as the icon, setting a color will change the icon to that color. We can update our documentation to make that more clear.


refactor(Gatsby): Upgrade npm dependencies

Most of the lint fails because of updated eslint I assume? 🤔

Seems all good to me, lets merge this 🚀


[WIP]Provide onset of symptoms before upload (EXPOSUREAPP-2484, EXPOSUREAPP-2485)

Thank you for this this PR! Please consider the following:

To the Community :heart::

Please link to an issue ticket where your code change has been greenlit, otherwise it's unlikely it can be merged.
Use a descriptive title: {task_name} (closes #{issue_number}), e.g.: Use logger (closes # 41).
If this PR comes from a fork, please Allow edits from maintainers
The PR can not contain changes in localization files, e.g. values-[LANGUAGE-CODE]/strings/* and / or assets/* (see #332 for further information).

To the Maintainers :coffee::

Title structure: Jira ticket name (EXPOSUREAPP-XXXX).
Set labels: maintainers, sprintX.
Update Jira status: In Review.
Fulfill internal Acceptance Criteria.
If mentioned in the Jira ticket link all corresponding GitHub issues in the sidebar.

To everyone :world_map::

Describe your changes in detail, if you changed the UI, screenshots or GIFs would be awesome!
Short step by step instructions help the reviewer test your changes, e.g. how to navigate to a new UI element you added.
The PR won't be reviewed if CircleCi is failing or if there are merge conflicts. If Circle CI is still failing mark the PR as a draft and write a little comment on your status.
Provide at least a few unit and/or instrumentation tests.
Use a meaning full branch name. Use either fix or feature as prefix for your branch, e.g. fix/prevent-npe-on-device-rotation-issue_123
Test your changes thoroughly. Only open PRs which you think is ready to be merged. If you explicitly need feedback mark the PR as DRAFT on Github.
Don't introduce unrelated code reformatting (e.g., on-save hooks in your IDE)
Remove this checklist before creating your pull request.

Description
Initial implementation of symptom introduction and calendar screen.
NOTE - This PR is just being used during our marry session and is not final.

Closed as it's include in: https://github.com/corona-warn-app/cwa-app-android/pull/1170


no such file or directory, open /node_modules/steam-resources/protobuf_gen/protos.csv

index.js contains the following:
var protos = parse(fs.readFileSync(__dirname + '/protobuf_gen/protos.csv', {
  encoding: 'ascii'
}), {
  columns: true
});

But this "protobuf_gen" folder does simply not exist.

Did you follow the instructions when installing it?

Yes, try it out yourself.
new folder.
npm init
npm install steam-resources
node index.js

What was the output for npm install seishun/node-steam-resources? And what's your npm version?

npm -v  --> 6.13.7
npm install seishun/node-steam-resources
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.

<EMAIL_ADDRESS>added 37 packages from 34 contributors and audited 56 packages in 6.628s
found 1 moderate severity vulnerability
run npm audit fix to fix them, or npm audit for details

Does it create the folder for you? :)

I am getting this vulnerability:
https://www.npmjs.com/advisories/605
But I don't really know how to solve this..

It does create the directory for me. What's your output of ls node_modules/steam-resources?

index.js  LICENSE  node_modules  package.json  package-lock.json  README.md  steam_language_parser

There's probably something wrong with your setup. Try clearing the cache or using a different machine.

There's probably something wrong with your setup. Try clearing the cache or using a different machine.

I already did clear the cache. :(

It seems it didn't work because there shouldn't be a package-lock.json file. Sorry, can't help you further.


Adds missing attirbutes to zone settings override and LB Monitor resources

Adds zone settings override for ciphers: https://api.cloudflare.com/#zone-settings-change-ciphers-setting
Adds probe_zone argument to LB Monitor resource: https://api.cloudflare.com/#load-balancer-monitors-create-monitor
Also I've noticed that client/v4/zones/.../settings returns some more options that are not available in terraform:
{
  "result": [

...

    {
      "id": "ciphers",
      "value": [],
      "modified_on": null,
      "editable": true
    },

...

    {
      "id": "edge_cache_ttl",
      "value": 7200,
      "modified_on": null,
      "editable": true
    },

...

    {
      "id": "orange_to_orange",
      "value": "off",
      "modified_on": null,
      "editable": true
    },

...

    {
      "id": "visitor_ip",
      "value": "on",
      "modified_on": null,
      "editable": true
    },

...

  ],
  "success": true,
  "errors": [],
  "messages": []
}

Should I also add visitor_ip, orange_to_orange, edge_cache_ttl settings? Also I do not see anything for these settings in the docs...

Can you please split this into two separate PRs? The changes are not related and should be reviewed separately.

sure.

sure.

@jacobbednarz sure, thanks for looking into this
probe_zone change is here: #903
Also can you please comment on my question in description about visitor_ip, orange_to_orange, edge_cache_ttl attributes that returned by API? I am struggling to find any documentation related to these

@jacobbednarz sure, thanks for looking into this
probe_zone change is here: #903
Also can you please comment on my question in description about visitor_ip, orange_to_orange, edge_cache_ttl attributes that returned by API? I am struggling to find any documentation related to these

Should I also add visitor_ip, orange_to_orange, edge_cache_ttl settings?

I'll confirm about these first two however edge_cache_ttl was removed in #653. I'm assuming they are enterprise only features too which will make the pool of who will be using them smaller again.

Should I also add visitor_ip, orange_to_orange, edge_cache_ttl settings?

I'll confirm about these first two however edge_cache_ttl was removed in #653. I'm assuming they are enterprise only features too which will make the pool of who will be using them smaller again.

@riuvshyn, are you still looking into this? would you like me to take it over since I have a need for this?

@elovelan if you want this functionality, i'd recommend grabbing a new PR and submitting as this one is now stagnent.


[benchmark] Change the readme to consistently use the "#" heading form

We need this to use Heading 3+. Better to just standardize on that one
convention so we are consistent.

@swift-ci smoke test and merge


Installation Issues.

How do I solve this?

Environment:

OS and version: macOS Catalina 10.15.4
Node.js version: 6.13.4

You're installing from github instead of npm? npm run build

My bad,
Worked, Thanks!❤


Port Cassaforte Query API to new Query Builder

I've been following this, great job. Do we plan on replacing Hayt with this? but still keep the API exactly as is?

Yes, that was the idea. I'm trying to stick to Hayt as much as possible, but several things there are bit inconsistent. It will be 99.9% compatible (I'll run it over the Hayt test case when I'm done). For the cases where we decided to take another way, there will be a special namespace "hayt-compatibility" which will live for some time until people migrate.
Some things will be done in a syntax (and naming) introduced by Java Driver, I think that is a better path to follow. Maybe eventually, Hayt will change naming scheme to ones Java Driver introduced, mostly because that's the way people around actually call things.