Settings and initial contents for Korean localization

This PR is to initiate Korean localization based on

Issue to #288
https://github.com/cncf/glossary/blob/main/LOCALIZATION.md guide

Base and target branch of this PR is dev-ko which is development branch for Korean localization.
This PR includes

[languages.ko] section in config.toml
content/ko/ directory
i18n/ko.toml
Some  translated documents

Main page

content/ko/_index.md

Terms

"Cloud Native Technology": content/ko/cloud_native_tech.md

Others

contribute: content/ko/contribute/_index.md (partially localized)
style-guide: content/ko/style-guide/_index.md (partially localized)

Since Korean localization team owns content/ko/* only,
this PR will require approvals from upstream owners (maintainers).

I hope to note that there is no Netlify preview for this branch (dev-ko) yet.

@seokho-son, just to clarify, this is to create the Korean branch and that's why you need one of us to approve as well, correct?

@CathPag

this is to create the Korean branch .. ?

I created Korean branch https://github.com/cncf/glossary/tree/dev-ko already. This PR is not about creating a new branch but is to config Korean language to enable Korean option to the glossary website. The configuration will be effective only in dev-ko.
I assume this kind of PR is the first PR that each localization team open firstly.

that's why you need one of us to approve as well, correct?

Each localization team needs to modify config.toml for a new language configuration according to https://github.com/cncf/glossary/blob/main/LOCALIZATION.md#add-a-new-language-setting-to-site-configuration
Even though the target branch of this PR is dev-ko, config.toml needs to be properly modified since config.toml will be merged to main branch eventually.
So, maintainers would better to check config.toml is configured properly to help localization teams. :)
[FYI] I added Korean approvers for files in /contents/ko/ to CODEOWNERS. https://github.com/cncf/glossary/blob/dev-ko/CODEOWNERS#L11
But it seems not work yet since permission setting for dev-ko branch is not appropriate yet.
(I guess PR #293 will resolve this problem)

Ok, since you would like a maintainer to review for correctness, let's wait for Jason to come back next week as I can only really review and approve content, not setups.

@JasonMorgan Thanks :)
I just wanted to show basic files that need to be included in a new language configuration to maintainers and new l10n teams. obviously not for requesting Korean review ;)
In case of content/ko/_index.md, the contents in the file is Korean.
File name should be same with the file in English directory (content/en/_index.md).
Then Hugo understands it is a localized document.


Resolve Issue #28

For resolving https://github.com/acthp/ucsc-xena-client/issues/28, and reverting an html element back to previous.

Oddly, I just tried return the original param, and it "seems" to be working:
var nn = (...args) => args.filter(x => x);
Within the callback provided to .filter( ), I tried a variety of return tests such as an empty array and "untruthy" values like undefined and null.  All appeared to work.

Not so odd... x => x  is same as  x => x !== false  when x is false.
That should work.
On Fri, Feb 26, 2016 at 2:29 PM, Albert Chang<EMAIL_ADDRESS>wrote:

Oddly, I just tried return the original param, and it "seems" to be
working:
var nn = (...args) => args.filter(x => x);
Within the callback provided to .filter( ), I tried a variety of return
tests such as an empty array and "untruthy" values like undefined and null.
All appeared to work.
—
Reply to this email directly or view it on GitHub
https://github.com/acthp/ucsc-xena-client/pull/34#issuecomment-189509235
.

Please reject this PR.  Submitting different, cleaner, PR for this change.


Create jobcentre-* and qualification-* registers in alpha

Context
Promote jobcentre-* and qualification-* to alpha. They will be removed from discovery in a separate PR.
Changes proposed in this pull request
Create the following registers in alpha:

jobcentre
jobcentre-district
jobcentre-group
qualification-assessment-method
qualification-level
qualification-sector-subject-area
qualification-type

Guidance to review
https://trello.com/c/mqme6ZLm
https://trello.com/c/LhuqthJP

Given that qualification-subject has been renamed to qualification-sector-subject-area, will this cause us problems for the alpha until such time as we remove this renamed register from the manifest file (qualification-subject no longer exists in registers.tf)?


Create the basic User object

including:

[x] user.model
[x] user.interface
[x] user.manager
[ ] user.router
[x] user.spec

[x] add user
[x] get user
[x] delete user
[x] get all users
[x] update user
[x] delete all users

close example

reopening


Add async await syntax.

Add the possibility to use async/await as discussed in  #56
E.g.
`
const Hook: webhook.Webhook = new webhook.Webhook("WEBHOOK URL");
const msg = new webhook.MessageBuilder().setAuthor("TEST_AUTHOR");
await Hook.send(msg);
`

Accidentally marked as approved

Also looks like there is a gnarly eslint error in there

The benefit is to use async and await syntax. As discussed. This pr is just to introduce them and make it available. It does not fix bad coding decisions nor any logical errors. This should be handled by other pull requests.

@Exitare the implementation you have proposed is broken. It does not work at all, I appreciate another PR should fix "poor coding decisions" but this is not working by any means.
/Users/joseph/Desktop/Projects/JavaScript/Node.js/webhook-discord/lib/webhook.js:109
                                    await this.sendPayload(payload, resolve);
                                    ^^^^^

SyntaxError: await is only valid in async function
    at new Script (vm.js:79:7)
    at createScript (vm.js:251:10)
    at Object.runInThisContext (vm.js:303:10)
    at Module._compile (internal/modules/cjs/loader.js:657:28)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
    at Module.load (internal/modules/cjs/loader.js:599:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
    at Function.Module._load (internal/modules/cjs/loader.js:530:3)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at require (internal/modules/cjs/helpers.js:22:18)

That wasn’t meant to be rude. Anyways, I don’t have any time to spare in the foreseeable future and therefore will close this PR. If someone would like to take over feel free to do that.

I'll look into it. I do agree though that the current async system is iffy, if it is reimplemented it should be a full rewrite of all the promises.


Update the README’s Mac-specific instructions

Rename the “Installing RGBDS (UNIX)” section to “Building RGBDS”, as that’s what we’re doing, regardless of platform.
Update references of Mac OS X to macOS.
State that only libpng and pkg-config need to be downloaded with Homebrew; the others are pre-installed along with Xcode.
State that RGBDS itself is available through Homebrew (originally suggested in #105).

I guess I have to trust you on this one. :P

Heh 😉


[BUG]: Admin | Sync Template v2 (Model Driven Apps) failing for some environments

Describe the bug
Hi there, we updated our core components solutions with the newest version (1.45) and still facing the failed model driven app flow issue. The flow failed for 11 environments and giving me an error saying "CRM organization with unique name 'orgf38f21e8' not found." We are unable view model driven apps for those environments.
Component (please tell us which flow or app you are experiencing issues with):

Solution Core Components
Version 1.45
Admin | Sync Template v2 (Model Driven Apps)

Expected behavior
Display ALL model driven apps in the tenant on Power Platform Admin View Model driven apps
Screenshots

Can you please look at the output of the Get Environment as Admin call up above your screenshot? And then validate that you have access to view the environments? Follow the links from the output as shown here:

Hi I don't see a Get Environment as Admin call

I've pointed to it from your first screenshot

Oh my bad sorry I will double check now

No problem, there's a lot of collapsed steps. Let me know

Hi Jenefer, we validated if the account that was used to set up CoE had access to the environments that caused the flow to fail and turns out even with admin role in the tenant, the account had environments with no access. We granted the account access and are able to see more and more model driven apps in the PowerApps App table.  Thanks so much for your help!

Of course. Thanks for using the CoE.


[Usage]: Got nccl error when deploy vllm in k8s with multiple GPUs

Your current environment
The output of `python collect_env.py`

How would you like to use vllm
I trying to deploy a Qwen2-72b model in k8s, with 4 GPUs in one node. Accroding to the log it seems can't enable NCCL P2P in k8s pod, even the GPUs are in the same node. Or is there a way to enable it?
Here is my k8s deployment file:
apiVersion: apps/v1 kind: Deployment metadata:   name: vllm-deployment   namespace: model spec:   replicas: 1 # You can scale this up to 10   selector:     matchLabels:       app: vllm   template:     metadata:       labels:         app: vllm     spec:       volumes:       - name: dshm         emptyDir:           medium: Memory       containers:       - name: vllm-container         image: vllm/vllm-openai:latest         env:         - name: NCCL_DEBUG           value: INFO         args: ["--model", "Qwen/Qwen2-72B-Instruct-GPTQ-Int4", "--download-dir", "/models", "--served-model-name", "qwen2-72b", "--kv-cache-dtype", "fp8_e4m3", "--tensor-parallel-size", "4", "--gpu-memory-utilization", "0.8", "--max-model-len", "14336", "--port", "11434"]         # check the health of the container by hitting port 8000/health endpoint         readinessProbe:           httpGet:             path: /health             port: 11434           initialDelaySeconds: 5           periodSeconds: 1         ports:         - containerPort: 11434           name: vllm-port         resources:           requests:             memory: '5000Mi'             nvidia.com/gpu: 4           limits:             memory: '5000Mi'             nvidia.com/gpu: 4         volumeMounts:           - mountPath: /models             name: model-storage       volumes:       - name: model-storage         persistentVolumeClaim:           claimName: model-storage-pvc
Here is the error log:
2024-08-13T07:37:27.223526999Z vllm-deployment-8577b94b74-fhx85:61:61 [0] NCCL INFO P2P is disabled between connected GPUs 1 and 3. You can repress this message with NCCL_IGNORE_DISABLED_P2P=1. 2024-08-13T07:37:27.401053965Z vllm-deployment-8577b94b74-fhx85:61:61 [ERROR 08-13 07:37:27 multiproc_worker_utils.py:120] Worker VllmWorkerProcess pid 111 died, exit code: -15 2024-08-13T07:37:27.401078075Z INFO 08-13 07:37:27 multiproc_worker_utils.py:123] Killing local vLLM worker processes 2024-08-13T07:37:27.506937412Z Process Process-1: 2024-08-13T07:37:27.508190691Z Traceback (most recent call last): 2024-08-13T07:37:27.508231292Z   File "/usr/lib/python3.10/multiprocessing/process.py", line 314, in _bootstrap     self.run() 2024-08-13T07:37:27.508242732Z   File "/usr/lib/python3.10/multiprocessing/process.py", line 108, in run 2024-08-13T07:37:27.508246402Z     self._target(*self._args, **self._kwargs) 2024-08-13T07:37:27.508249772Z   File "/usr/local/lib/python3.10/dist-packages/vllm/entrypoints/openai/rpc/server.py", line 217, in run_rpc_server 2024-08-13T07:37:27.508253072Z     server = AsyncEngineRPCServer(async_engine_args, usage_context, port)   File "/usr/local/lib/python3.10/dist-packages/vllm/entrypoints/openai/rpc/server.py", line 25, in __init__ 2024-08-13T07:37:27.508259922Z     self.engine = AsyncLLMEngine.from_engine_args(async_engine_args, 2024-08-13T07:37:27.508263112Z   File "/usr/local/lib/python3.10/dist-packages/vllm/engine/async_llm_engine.py", line 471, in from_engine_args 2024-08-13T07:37:27.508266912Z     engine = cls( 2024-08-13T07:37:27.508270963Z   File "/usr/local/lib/python3.10/dist-packages/vllm/engine/async_llm_engine.py", line 381, in __init__ 2024-08-13T07:37:27.508275343Z     self.engine = self._init_engine(*args, **kwargs) 2024-08-13T07:37:27.508279263Z   File "/usr/local/lib/python3.10/dist-packages/vllm/engine/async_llm_engine.py", line 552, in _init_engine 2024-08-13T07:37:27.508283243Z     return engine_class(*args, **kwargs)   File "/usr/local/lib/python3.10/dist-packages/vllm/engine/llm_engine.py", line 249, in __init__ 2024-08-13T07:37:27.508291193Z     self.model_executor = executor_class( 2024-08-13T07:37:27.508295083Z   File "/usr/local/lib/python3.10/dist-packages/vllm/executor/multiproc_gpu_executor.py", line 215, in __init__ 2024-08-13T07:37:27.508298743Z     super().__init__(*args, **kwargs) 2024-08-13T07:37:27.508301943Z   File "/usr/local/lib/python3.10/dist-packages/vllm/executor/distributed_gpu_executor.py", line 25, in __init__     super().__init__(*args, **kwargs) 2024-08-13T07:37:27.508308343Z   File "/usr/local/lib/python3.10/dist-packages/vllm/executor/executor_base.py", line 47, in __init__ 2024-08-13T07:37:27.508311943Z     self._init_executor() 2024-08-13T07:37:27.508315093Z   File "/usr/local/lib/python3.10/dist-packages/vllm/executor/multiproc_gpu_executor.py", line 137, in _init_executor     self._run_workers("init_device") 2024-08-13T07:37:27.508321623Z   File "/usr/local/lib/python3.10/dist-packages/vllm/executor/multiproc_gpu_executor.py", line 192, in _run_workers 2024-08-13T07:37:27.508324823Z     driver_worker_output = driver_worker_method(*args, **kwargs) 2024-08-13T07:37:27.508328293Z   File "/usr/local/lib/python3.10/dist-packages/vllm/worker/worker.py", line 132, in init_device     init_worker_distributed_environment(self.parallel_config, self.rank, 2024-08-13T07:37:27.508334623Z   File "/usr/local/lib/python3.10/dist-packages/vllm/worker/worker.py", line 348, in init_worker_distributed_environment 2024-08-13T07:37:27.508337834Z     ensure_model_parallel_initialized(parallel_config.tensor_parallel_size, 2024-08-13T07:37:27.508341424Z   File "/usr/local/lib/python3.10/dist-packages/vllm/distributed/parallel_state.py", line 965, in ensure_model_parallel_initialized 2024-08-13T07:37:27.508344584Z     initialize_model_parallel(tensor_model_parallel_size, 2024-08-13T07:37:27.508347804Z   File "/usr/local/lib/python3.10/dist-packages/vllm/distributed/parallel_state.py", line 931, in initialize_model_parallel 2024-08-13T07:37:27.508350984Z     _TP = init_model_parallel_group(group_ranks, 2024-08-13T07:37:27.508370514Z   File "/usr/local/lib/python3.10/dist-packages/vllm/distributed/parallel_state.py", line 773, in init_model_parallel_group 2024-08-13T07:37:27.508386234Z     return GroupCoordinator( 2024-08-13T07:37:27.508389804Z   File "/usr/local/lib/python3.10/dist-packages/vllm/distributed/parallel_state.py", line 154, in __init__ 2024-08-13T07:37:27.508393004Z     self.pynccl_comm = PyNcclCommunicator(   File "/usr/local/lib/python3.10/dist-packages/vllm/distributed/device_communicators/pynccl.py", line 89, in __init__ 2024-08-13T07:37:27.508399564Z     self.comm: ncclComm_t = self.nccl.ncclCommInitRank( 2024-08-13T07:37:27.508402775Z   File "/usr/local/lib/python3.10/dist-packages/vllm/distributed/device_communicators/pynccl_wrapper.py", line 244, in ncclCommInitRank 2024-08-13T07:37:27.508405955Z     self.NCCL_CHECK(self._funcs["ncclCommInitRank"](ctypes.byref(comm), 2024-08-13T07:37:27.508409115Z   File "/usr/local/lib/python3.10/dist-packages/vllm/distributed/device_communicators/pynccl_wrapper.py", line 223, in NCCL_CHECK 2024-08-13T07:37:27.508412315Z     raise RuntimeError(f"NCCL error: {error_str}") 2024-08-13T07:37:27.508415555Z RuntimeError: NCCL error: unhandled system error (run with NCCL_DEBUG=INFO for details)

please follow https://docs.vllm.ai/en/latest/getting_started/debugging.html to add more details.

please follow https://docs.vllm.ai/en/latest/getting_started/debugging.html to add more details.

Here is the output of the test.py
root@vllm-deployment-8577b94b74-fhx85:/vllm-workspace# python3 test.py  Traceback (most recent call last):   File "/vllm-workspace/test.py", line 3, in <module>     dist.init_process_group(backend="nccl")   File "/usr/local/lib/python3.10/dist-packages/torch/distributed/c10d_logger.py", line 79, in wrapper     return func(*args, **kwargs)   File "/usr/local/lib/python3.10/dist-packages/torch/distributed/c10d_logger.py", line 93, in wrapper     func_return = func(*args, **kwargs)   File "/usr/local/lib/python3.10/dist-packages/torch/distributed/distributed_c10d.py", line 1361, in init_process_group     store, rank, world_size = next(rendezvous_iterator)   File "/usr/local/lib/python3.10/dist-packages/torch/distributed/rendezvous.py", line 246, in _env_rendezvous_handler     rank = int(_get_env_or_raise("RANK"))   File "/usr/local/lib/python3.10/dist-packages/torch/distributed/rendezvous.py", line 231, in _get_env_or_raise     raise _env_error(env_var) ValueError: Error initializing torch.distributed using env:// rendezvous: environment variable RANK expected, but not set

Problem sovled. It is because my /dev/shm is too small. But the P2P disable log is still exist. So my question is, GPUs can't use p2p to conmmunicate in k8s, right?

Problem sovled. It is because my /dev/shm is too small. But the P2P disable log is still exist. So my question is, GPUs can't use p2p to conmmunicate in k8s, right?

It depends on the interconnects used on your system. Is it PCIe or NvLink

Problem sovled. It is because my /dev/shm is too small. But the P2P disable log is still exist. So my question is, GPUs can't use p2p to conmmunicate in k8s, right?

It depends on the interconnects used on your system. Is it PCIe or NvLink

It's PCIe

I have the same issue. How have you solved it? @ZhaoGuoXin

I have the same issue. How have you solved it? @ZhaoGuoXin

If you are using Kubernetes, the default size is 64MB. You can change it by mounting an empty dir volume. As mentioned in https://github.com/gpustack/gpustack/issues/835


[request] Expose VXAO via DXVK?

So DXVK is able to emulate all DirectX9-10-11 calls through Vulkan.
DXVK also allows to set a custom device ID, for device spoofing.
Is it possible to make DXVK expose Nvidia's VXAO option in games, if you don't have a Maxwell GPU or newer?
It's only present in like 4 games total to my knowledge. Rise of the Tomb Raider, Final Fantasy 15, I think Division 1 and I think Shadow of the Tomb Raider. And it's only present in DX11, not DX12.
It's a voxel based AO solution, similar to a path traced AO option like ReShade MXAO. Or you can think of it a precursor to Nvidia's work on RT ambient occlusion.
I'm really not sure if this is within's DXVK or any developer's means, but I wanted to ask.

VXAO works in FFXV if you have a supported GPU . I don't know about the other games, they may require some sort of nvapi magic that probably doesn't work on Linux.

I only tried on Windows, on 5700 XT and NimeZ 22.8.2 drivers. Used DXVK 1.10.3, set the Nvapi to not report as an AMD GPU (so False) and set the device ID to an RTX 3080.
Rise of the Tomb Raider in DX11 would still not expose VXAO.

DXVK supports all the features necessary, if the game decides to only expose VXAO on an actual Nvidia GPU due to some vendor library interactions (which cannot ever work with DXVK on Windows) then there's nothing we can do on our end.


fix(ci): egrep behavior different - WIP (Do not merge)

Summary
Try to use xcpretty. egrep returns 1 when result is not found, and 0 when result is found. travis-ci use egrep returns value as exit code which causes failure.
Test plan
Issues

"THING-1234" or "Fixes #123"

Closing due to inactivity


added some probing to pinpoint the issues with the build-action bug

adds some debugging output the github worflow "build-action"
related #41

note that the success of the current CI is dependent on #42

is the point here to get the build checks to succeed again?

The point is to figure out why it was crashing
GlynLeine<EMAIL_ADDRESS>schrieb am Mo., 27. Juli 2020, 20:55:

is the point here to get the build checks to succeed again?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/Args-Engine/Args-Engine/pull/44#issuecomment-664576884,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC6OMSAYV3YUL4EYBZK6GZLR5XEQLANCNFSM4PIRC2OQ
.

The point is to figure out why it was crashing GlynLeine<EMAIL_ADDRESS>schrieb am Mo., 27. Juli 2020, 20:55:
…
is the point here to get the build checks to succeed again? — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#44 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC6OMSAYV3YUL4EYBZK6GZLR5XEQLANCNFSM4PIRC2OQ .

cool i won't review untill you gimme a go ahead then

This PR is meant to give me insight to when it happens again on other branches, because I cannot repro this anywhere right now. So I would actually appreciate if you would merge it. This is more maintenance than actual fix.
Von: GlynLeine<EMAIL_ADDRESS>Gesendet: Dienstag, 28. Juli 2020 18:06
An: Args-Engine/Args-Engine<EMAIL_ADDRESS>Cc: Algo-ryth-mix<EMAIL_ADDRESS>Assign<EMAIL_ADDRESS>Betreff: Re: [Args-Engine/Args-Engine] added some probing to pinpoint the issues with the build-action bug (#44)
The point is to figure out why it was crashing GlynLeine<EMAIL_ADDRESS><EMAIL_ADDRESS>schrieb am Mo., 27. Juli 2020, 20:55:
…
is the point here to get the build checks to succeed again? — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#44 (comment) https://github.com/Args-Engine/Args-Engine/pull/44#issuecomment-664576884 >, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC6OMSAYV3YUL4EYBZK6GZLR5XEQLANCNFSM4PIRC2OQ .
cool i won't review untill you gimme a go ahead then
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub https://github.com/Args-Engine/Args-Engine/pull/44#issuecomment-665129386 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AC6OMSDGK3BCOH5KMNSDEPTR53ZNJANCNFSM4PIRC2OQ .  https://github.com/notifications/beacon/AC6OMSHIHC67E5DFKHD4MV3R53ZNJA5CNFSM4PIRC2O2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOE6SRDKQ.gif


skip_download param in the implicit get when put

When put a large object to gcs, it is a kind of waste to download the object again from the bucket because of the implicit get. Can we provide a param, e.g. skip_download, to skip downloading the file, and just retrieve its metadata, e.g. generation and url?

Seems this would be fixed by https://github.com/frodenas/gcs-resource/pull/36

Fixed at #36.


Res.Render documentation missing information.

I cannot find any information anywhere in the documentation or of other sources where res.render pulls the HTML from that we are referencing in the documentation.
For example, I want to render some HTML (preferably in a file somewhere) and inject some variables into it. In the photo below at docs we are stating 'email'.

Does this mean email.html in the same directory as this .js script?
Does this mean we previously read the file email.html and read it into memory somewhere?

I have been trying to understand this process of express and utilize this function but everyone just glances over this part in particular.
So. where is the html for email?

It uses the configured view engine ('view engine' option) to render templates from the directory specified in 'views' (process.cwd() + '/views' by default).
You can read more about template engines e.g. in the Using template engines with Express guide.


cuba.Entity instead of cuba.Class

Maybe have a discussion on the perfect name name of the top-level class.
cuba.Class was awkward, because an instance would be a "Class" CUDS-object but should probably be an "Object" CUDS-object,
So I changed it back to what it was in the very beginning: cuba.Entity, which is also kinda awkward, because everything in the ontology is an entity, isn't it?
OWL uses owl:Thing as top-level Class.

Duplicate of #47
Closing that one in favour of this one

I'll rollback to Entity for now, to much the current implementation.


Backport security fixes to version 2.x

Hi there.
First of all thank you for your package. I was actually not aware of using it, but thanks to the power of npm I actually do.
I noticed that I'll get a npm audit warning which points to https://www.npmjs.com/advisories/1755.
As far as I understand there are already bugfix releases of version 4, 5 and 6 available, which is awesome.
Would it be possible to also do a bugfix release of version 2? Npm audit shows me the following chain:
normalize-url  <=4.5.0 || 5.0.0 - 5.3.0 || 6.0.0
Severity: high
Regular Expression Denial of Service - https://npmjs.com/advisories/1755
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/download/node_modules/normalize-url
  cacheable-request  0.1.0 - 6.0.0
  Depends on vulnerable versions of normalize-url
  node_modules/download/node_modules/cacheable-request
    got  8.0.0 - 9.5.0
    Depends on vulnerable versions of cacheable-request
    node_modules/download/node_modules/got
      download  >=7.0.0
      Depends on vulnerable versions of got
      node_modules/download
        bin-wrapper  2.1.2 || >=4.0.0
        Depends on vulnerable versions of download
        node_modules/bin-wrapper
          saucelabs  >=4.1.0
          Depends on vulnerable versions of bin-wrapper
          node_modules/saucelabs
            karma-sauce-launcher  >=4.1.5
            Depends on vulnerable versions of saucelabs
            node_modules/karma-sauce-launcher

E.g. https://www.npmjs.com/package/bin-wrapper is a highly used package (~ 1 million installs a week) but likely no longer updated (last update three years ago). This packages indirectly relies on normalize-url version 2.

Versions below 4.3.0 are not affected by this. I have asked them to update the CVE.
The vulnerable feature was released in v4.4.0: https://github.com/sindresorhus/normalize-url/releases/tag/v4.4.0

@sindresorhus  Awesome. Thank you for the additional information!

Could you also contact https://snyk.io/vuln/SNYK-JS-NORMALIZEURL-1296539 ? I think that is currently the source for npm audit. I already heard other open source developer just do that (see https://github.com/mafintosh/multicast-dns/issues/75#issuecomment-848561343).


ExLlamaDeviceMap's layers offload to CPU?

I would like to test run 7b model on my 4g vram 3050, look like exllama does not support offload model to CPU yet?

It doesn't, no. I would require a whole separate implementation of the model to process CPU layers and I wouldn't expect that to come anytime soon. When it does, it probably won't be better than Llama.cpp anyway, but either way that's your best bet for running a 7B model on a 4 GB GPU right now.


Missing Support for Integrity Check

Tracking issue for:

[ ] https://github.com/Egekinhwkns/juice-shop/security/code-scanning/39

https://github.com/Egekinhwkns/juice-shop/blob/master/frontend/src/index.html


[Bug]: Regrid does not preserve attributes

What happened?
After ds.regridder.horizontal process, attributions (e.g., units) are not preserved.
What did you expect to happen?
To be preserved.
Minimal Complete Verifiable Example
>>> ds = xc.open_dataset('/work/lee1043/cdat/pmp/E3SM/E3SMv3_evaluation/mean_climate/clim/clim/cmip6.historical.E3SMv3.r1i1p1f1.mon.pr.198101-200512.AC.v20230404.nc')
>>> ds['pr'].units
'kg m-2 s-1'
>>> t_grid = xc.create_uniform_grid(-88.875, 88.625, 2.5, 0, 357.5, 2.5)
>>> varname = 'pr'
>>> ds_regridded = ds.regridder.horizontal(varname, t_grid, tool='regrid2')
>>> ds_regridded[varname].attrs
{}
>>> ds_regridded['pr'].units
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/lee1043/.conda/envs/pcmdi_metrics_dev_20230201/lib/python3.9/site-packages/xarray/core/common.py", line 278, in __getattr__
    raise AttributeError(
AttributeError: 'DataArray' object has no attribute 'units'

### Relevant log output

_No response_

### Anything else we need to know?

_No response_

### Environment

xCDAT 0.5.0

@lee1043 If possible could you provide a link to the source file?

@jasonb5 Thank you for taking this a look. I noticed the directory path slightly changed since then. Would you be able to access below file from the gates? Otherwise I will email or upload it.
/work/lee1043/cdat/pmp/E3SM/E3SMv3_evaluation/mean_climate/clim/cmip6.historical.E3SMv3.r1i1p1f1.mon.pr.198101-200512.AC.v20230404.nc

Found the issue, will have a PR soon. Regrid2 is creating the dataarray from scratch and not copying the attributes from the source dataarray, we do copy the dataset attributes.


Incompatible with Next 15 /  React 19

I get a dependency conflict whilst adding Lenis to Nextjs 15 but I don't see why Lenis shouldn't be able to work with React 19:
npm WARN Found<EMAIL_ADDRESS>npm WARN node_modules/react
npm WARN<EMAIL_ADDRESS>from the root project
npm WARN   3 more (next, react-dom, styled-jsx)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>

it's just a warning, lenis works with react19 but we can't update the dependencies until react v19 is officially released.


'Link' tool seems to be broken?

This is what I see when I try to create a Link
, using the version of databrowser that is included in NSS master:

@Vinnl bump

@timbl What is the Link pane supposed to do? The mintNew function simply resolves without doing anything - is it simply unfinished? (The commit message seems to imply so...

Yes it is unfinished.. the links pane was for a holding just  a set of links, like references to things discussed in a meeting, or relevant remote web sites to folder, etc ... it was a while ago


Update auto save for focus changes to include more cases

For #10853
Window state changes and view state changes for a webview should all cause a 'focus' change. Include these in our list of stuff that causes a focus change save.

Codecov Report

Merging #11026 into master will increase coverage by 0.53%.
The diff coverage is 25.00%.

@@            Coverage Diff             @@
##           master   #11026      +/-   ##
==========================================
+ Coverage   60.76%   61.30%   +0.53%
==========================================
  Files         585      591       +6
  Lines       31947    32380     +433
  Branches     4527     4585      +58
==========================================
+ Hits        19414    19850     +436
+ Misses      11546    11527      -19
- Partials      987     1003      +16

Impacted Files
Coverage Δ

...ascience/data-viewing/dataViewerMessageListener.ts
16.66% <0.00%> (+1.28%)
:arrow_up:

...ractive-common/interactiveWindowMessageListener.ts
17.50% <0.00%> (+0.42%)
:arrow_up:

src/client/datascience/types.ts
100.00% <ø> (ø)

.../datascience/interactive-common/interactiveBase.ts
5.69% <50.00%> (+0.14%)
:arrow_up:

src/datascience-ui/react-common/arePathsSame.ts
75.00% <0.00%> (-12.50%)
:arrow_down:

src/client/common/utils/platform.ts
64.70% <0.00%> (-11.77%)
:arrow_down:

src/client/common/utils/cacheUtils.ts
83.33% <0.00%> (-6.15%)
:arrow_down:

src/client/interpreter/display/index.ts
88.23% <0.00%> (-2.88%)
:arrow_down:

src/client/linters/pydocstyle.ts
86.66% <0.00%> (-2.23%)
:arrow_down:

src/client/datascience/debugLocationTracker.ts
76.56% <0.00%> (-1.57%)
:arrow_down:

... and 41 more

Continue to review full report at Codecov.

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


small assignment layout updates/fixes

I'll need help with the proper class for the os-search-value-selector in assignment-detail.component.html:149. Right now it looks okayish in desktop view, but messes up in mobile.
@tsiegleauq could you help me out?

I rebased it. @tsiegleauq @emanuelschuetze

@MaximilianKrambach fixed it


local_indices errors with SparseFunctions and SparseTimeFunctions running with MPI and 1 point

call this script example.py
(this behavior also holds for SparseTimeFunctions)
import devito
grd = devito.Grid(shape=(4,5))
f = devito.Function(name="f", grid=grd)
sf = devito.SparseFunction(name="sf", grid=grd, npoint=1)
print(sf.local_indices)

if I run
DEVITO_MPI=1 mpirun -n 2 python example.py
it errors with
(slice(0, 1, None),)
Traceback (most recent call last):
  File "/home/cvx/.julia/dev/Devito/ex.py", line 5, in <module>
    print(sf.local_indices)
  File "/home/cvx/.conda/envs/conda_jl/lib/python3.10/site-packages/cached_property.py", line 36, in __get__
    value = obj.__dict__[self.func.__name__] = self.func(obj)
  File "/home/cvx/.conda/envs/conda_jl/lib/python3.10/site-packages/devito/types/dense.py", line 643, in local_indices
    return tuple(self._distributor.glb_slices.get(d, slice(0, s))
  File "/home/cvx/.conda/envs/conda_jl/lib/python3.10/site-packages/devito/types/dense.py", line 643, in <genexpr>
    return tuple(self._distributor.glb_slices.get(d, slice(0, s))
  File "/home/cvx/.conda/envs/conda_jl/lib/python3.10/site-packages/cached_property.py", line 36, in __get__
    value = obj.__dict__[self.func.__name__] = self.func(obj)
  File "/home/cvx/.conda/envs/conda_jl/lib/python3.10/site-packages/devito/mpi/distributed.py", line 116, in glb_slices
    return {d: slice(min(i), max(i) + 1)
  File "/home/cvx/.conda/envs/conda_jl/lib/python3.10/site-packages/devito/mpi/distributed.py", line 116, in <dictcomp>
    return {d: slice(min(i), max(i) + 1)
ValueError: min() arg is an empty sequence

At least for the purposes of Devito.jl we would love for it to return a tuple  (0:-1,) for ranks where the sparsefunction memory isn't allocated.

@deckerla this is what your PR has fixed right Luke? can we close it?

Yes it is, PR was saying close instead of fix so didn't auto close. closing


[TEMPLATE] Calendly clone with stripe integration

Describe the template
This App is the perfect clone of the Calendly app it has Stripe integration which makes the person who wants to have a meeting with the person needs to pay before he can schedule his meeting in the respective timing. The price for the meeting is set by the developer or the account user. This uses the meeting scheduler template from appsmith
Link to the public app
Link
Integrations and features
A list of specific integrations, data sources, and specific features

Google Calendar
Stripe API
Zoom API

JSON File
Meeting Scheduler Copy.json.zip
Screenshots

@rlnorthcutt I have made the changes


upload simple project subnetting class C with C++

I have added a simple project subnetting class C with C++, please merge it and give a hacktoberfest label to make it a successful PR, Thanks

I have added a simple project subnetting class C width C++, please merge it and give a hacktoberfest label to make it a successful PR, Thanks

If you could add the project in English, that would be great.


Add tests for checking the format of CSV files

Input CSVs should have a standard, documented format. Test should check that correctly formatted CSVs work and that easy-to-make errors don't.

Documented in docstring, added assertion test when running setup() fn.


Projects using skan

Maybe you could add a list of references that cite your work. If you want, I can open a PR.
This would increase the "prestige" of skan and people browsing this page could see related papers.

@CsatiZoltan I would certainly welcome such a PR, thank you!

@jni On which page would you like me to place it?

@jni PR #106 created.


Netifaces don't expected return

Hi! i am implementing this code.
I've a issue with line 92 netifaces, it call this function local_ip = _get_local_ip(IFACE) but when i run the code i get the next error:

And wen i run netifaces.interfaces() i get the next response:

I've 0.10.8 netifaces installed, it's supposed that it will response something like lo0 or something like that, ¿why am i getting? ¿can you help me?
Thanks!

5 years late, but here was a solution I found for Windows 10.
You can figure out which interface is the one you want through Wireshark or by using the command ni.ifaddresses('<YOUR_INTERFACE_ID_HERE>') with each one until you find the right one.
Then you will need to add this bit of code "\\Device\\NPF_"+ before the iface is passed to scapy

You can't set the IFACE further down to that value because netifaces won't recognize it as valid, but using print(scapy.get_if_list()), you can see that scapy is expecting the full value.


Requiring module from Node-webkit : "Module did not self-register"

I'm trying to load mode_mdns from node-webkit 0.10.5 (based on Node v0.11.13, Chromium 35.0.1916.157) with this simple javascript line :
var mdns = require('mdns');

I get this result:
[9084:1103/094449:INFO:CONSOLE(1)] ""process.mainModule.filename: /index.html"", source: process_main (1)
[9084:1103/094449:INFO:CONSOLE(35)] "Uncaught Error: Module did not self-register.", source: /home/sgaze/dev/local/nw-sp/node_modules/mdns/lib/dns_sd.js (35)

I have to say that it works with node-webkit 0.8.6 (based on Node v0.10.22, Chrome 30.0.1599.66)

I know this hasn't been updated for a while, but I came up against this issue recently. Here's how I worked around it:

I made sure to use node-webkit 0.8.6 (Previously I was on 0.12.0-alpha2).
Installed nw-gyp globally with npm install -g nw-gyp.
I added a postinstall script to my package.json to rebuild mdns with nw-gyp after it installs:

  "scripts": {
    "postinstall": "cd node_modules/mdns && nw-gyp configure --target=0.8.6 && nw-gyp build && cd ../..",
    "postupdate": "cd node_modules/mdns && nw-gyp configure --target=0.8.6 && nw-gyp build && cd ../.."
  }

It isn't the most elegant solution, but it's doing the trick for me.

I need more specific information on what exactly works. This discussion is all over the place.
Node version.
Node-Webkit version.
Configure flags.

 Most of the issues are because someone missed a bit of documentation — but to be fair there are lots of them.
It definitely works on Windows 7 & OsX using node 0.11.x and node-webkit 0.11.x Probably Linux too but haven't tested. But mdns needs to be rebuilt using nw-gyp and both node & node-webkit need to use the same architecture. And on Windows the binary needs to be called nw.exe. Maybe there are other caveats I'm forgetting about but really everything is documented somewhere.

So,
Node v0.11.x
Node-Webkit v0.11.x
npm install mdns
./node_modules/mdns nw-gyp rebuild (with no flags?)

Downloaded: nw-v0.11.5, node-v0.11.5
npm install mdns
test/node_modules/mdns> nw-gyp configure --arch=ia32 --version=v0.11.5
test/node_modules/mdns> nw-gyp build
test>nw-v0.11.5\nw.exe .
Working.

Downloaded nw v0.11.6
git clone http://github.com/agnat/node_mdns mdns
nw-gyp configure --target=0.11.6
nw-gyp build
Working on Windows 7 directly
Working too on Ubuntu 64bits but had to disable ipv6 discovery to find devices:
var sequence = [           mdns.rst.DNSServiceResolve()         , mdns.rst.getaddrinfo({'families':[4]})         , mdns.rst.makeAddressesUnique()       ]; var browser = mdns.createBrowser(mdns.tcp('http'), {resolverSequence: sequence});

Tried with v0.11.6 and latest nw from npm on Debian Linux x64.
Still getting error:
[25725:0208/052705:INFO:CONSOLE(35)] "Uncaught Error: Module did not self-register.", source: /home/drasko/nw/test/node_modules/mdns/lib/dns_sd.js (35)
[25725:0208/052705:ERROR:nw_shell.cc(324)] TypeError: Cannot read property 'createBrowser' of undefined
I tied with default mdns from npm and the one from the master branch

hi, everyone.  @ghostoy  @rongerwang
some of my users got the error "Module did not self-register." just sometimes  when they access the app's local sqlite3 database(node-sqlite3) on nwjs, but some of users did never got this and never did myself.  And never got this error access by node.js v4.x and v5.x.
Who can tell me why? What the true problem is？ thanks all.
test on computer environments :
window xp & WIN7 32bit & WIN7 64 bit
both nw0.12.3  node.js v4.x node-sqlite3 v3.1.x  node-sqlite3 rebuilded by nw-gyp
nw0.13.x - nw0.14.x   node.js v5.x and  node-sqlite3 v3.1.x  node-sqlite3 rebuilded by node-gyp
.node path for nw0.14.x   and node.js v5.x
.node path:
path\app\node_modules\sqlite3\lib\binding\node-v47-win32-ia32\node_sqlite3.node
path\app\node_modules\sqlite3\lib\binding\node-v47-win32-x64\node_sqlite3.node
nw0.12.3
.node path for node.js v4.x (never got this error):
path\app\node_modules\sqlite3\lib\binding\node-v46-win32-ia32\node_sqlite3.node
path\app\node_modules\sqlite3\lib\binding\node-v46-win32-x64\node_sqlite3.node
.node path for nwjs v0.12.3:
path\app\node_modules\sqlite3\lib\binding\node-webkit-v0.12.3-win32-ia32\node_sqlite3.node
path\app\node_modules\sqlite3\lib\binding\node-webkit-v0.12.3-win32-x64\node_sqlite3.node


Avoid triggering extraneous MediaControl events which can cause playbar to show unexpectedly

The Poster Plugin was enabling/disabling the media control bar on every buffer, bufferfull, and play events.  This caused the media control bar to show up unexpectedly (for example during hls.js's instantaneous jumps over holes in a segment).  The container now only triggers the CONTAINER_MEDIACONTROL_ENABLE and CONTAINER_MEDIACONTROL_DISABLE events when they change.

Thanks for the feedback (that was me just being paranoid about truthiness).  Fixed to be more readable.

@clappr/core can we merge this? it is looking good.


pf2e key/picklock not actually unlocking doors

Keys simply don't work. Pick lock brings up the proper roll and the chat identifies success/failure but doesn't change the the lock state.
Everything is upto date and current release:

From the error messages it seems like you were testing the lock picking while being logged in as a player but without having a gm logged in. Most features of Lock & Key require a GM account to be logged in (which is the case for many modules). The reason is, that in core foundry it is impossible for players to change certain door states. To allow players to have a certain access to this data, Lock & Key basically makes the GM account do the required changes.

did not realize that was an issue. Thank you!

You are welcome


Multiplicity in Data Groups and Sub Groups

When we created data groups and sub groups in a data set with James, he said we didn't need to add multiplicity.
However, we had a further discussion with James when we were creating data groups and sub groups.
This is because, currently words are used for the multiplicity but moving forward when we author in Mauro should we be using multiplicity?

28/2/22 - agreed to add the multiplicity and the words for each data group and sub group.

Is this fixed or is it dependant on #372.

Dependent on #372

Issue closed as it is covered in #372 and doesn't have a t shirt label.


Baseline Expression Data Widget 'Variation GTex tab' issue

When I view Baseline Expression on a target profile page, the Summary and Experiments tab loads, but when I click on the 'Variation GTex tab' the whole data widget disappears, and so I am taken to the view of the Cancer DepMap data widget. Example page here: https://platform.opentargets.org/target/ENSG00000167207. The Baseline Expression data widget does not reappear unless I refresh the page, but again the same behaviour occurs when going the to Variation tab.
Expected behaviour
I would expect to stay within the Baseline Expression data widget and when clicking on the tab information is displayed, or if not available a notification.

@DSuveges sorry it wasn't me it was a contribution from another user ricardo-lourenco.

@remo87, we should work together more, I haven't recognised your github handle! 😄 btw, it's great we have outside contributors.


Alert commands

Currently pghoard's alerting just writes an alert file on disk.  Enhance this with a configurable alert command to allow running external commands which create alerts in external monitoring systems or send notifications to slack, etc.

@saaros you should use a real monitoring system for that. Try Nagios, Sensu.


refactor(llm): enhance a string of graph query method

Main Changes

[x] enhance vid k-neighbor query
[x] enhance property k-neighbor query
[x] limit edges to avoid super vertex expanding
[x] fetch vids only instead of fetch all vertices (with property)
[ ] compress duplicate property output
[ ] use better path for LLM to get the graph related info
[ ] .....

Follow #84 (merge it first), and maybe include some vid matching enhancement


[FEAT] Provide a TypeScript example in a live IDE

We currently have examples using JavaScript. Providing an example using TypeScript would let users experiment the API with this language.
Also display the bpmn-visualization version as for #319

Duplicates #302 created by me, my bad 😈.
So closing


League\Csv\Writer - Invalid CSV

Issue summary
A string with a doubled backslash at the end, leads to an invalid CSV file.
It looks like that in the CSV File:
"a text string \\"", "..."

System informations

Information
Description

League\Csv version
9.1.4

PHP/HHVM version
PHP 7.2

OS Platform
Debian GNU/Linux 9

Standalone code, or other way to reproduce the problem
Code not tested, just written to make it more easy to understand the problem:
$csvWriter = Writer::createFromPath('/tmp/file.csv', 'a+');
$csvWriter->setNewline("\r\n"); //RFC4180 Line feed
RFC4180Field::addTo($csvWriter);
$line=['a text string \\','...'];
$csvWriter->insertOne($line);

Expected result
"a text string \\", "..."

Actual result
"a text string \\"", "..."

@tom-d-77 thanks for submitting your bug report indeed I was able to reproduce the bug.
After some digging I found the source of the issue but resolving it won't be as simple as I thought. The main issue is that PHP fputcsv is broken beyond repair and can never generate a valid RFC4180 compliant CSV. My patch works in 80% of cases but not in 100%. So I was wondering if it woudn't be much simpler to just add a switch parameter to the Writer class so that if someone wants a true RFC4180 compliant CSV the engine would not use fputcsv at all.
I've been toying around that concept lately If I can come up with a decent implementation then it will land on the next minor release as I won't break any existing code.
If that solution is ok with you then the question becomes what to do with the RFC4180Field class ? Well I would deprecate the class and issue a warning in the documentation ? Thoughts ?

Seems that fgetcsv does not suffer from the same issue so I will only patch the Writer class as only fputcsv is broken.
I will have to double check this but If this is true then my patch will need some ironing (adding the appropriate tests) but is aleady done. when my PR is ready I'll let you know so that you could test it with your own data that way I'll be sure I've done it correctly or maybe you'll find other subtle bugs I haven't thought about 👍
Of course this will be done/finished when I have some spare times 😢

@tom-d-77 I've toying with a local dev that fix this issue but before submitting a PR I'd like your opinion on 2 possible implemetations
Using a dedicated setter/getter method
<?php

use League\Csv\Writer;

$writer = Writer::createFromString('');
$writer->getWritingMode(); //returns Writer::MODE_PHP
$writer->insertOne($arr); //the record is added using fputcsv
$writer->setWritingMode(Writer::MODE_RFC4180); //the new RFC4180 compliant writing mode
$writer->insertAll([$arr]); //the records are added using RFC4180 rules

Using an optional argument on the insertXXX methods
<?php

use League\Csv\Writer;

$writer = Writer::createFromString('');
$writer->insertOne($arr, Writer::MODE_PHP);  //the record is added using fputcsv
$writer->insertAll([$arr], Writer::MODE_RFC4180); //the records are added using RFC4180 rules

In both implementations, if no mode is set on the insertXXX methods Writer::MODE_PHP will be used to avoid BC break.
I'm leaning towards the second solution. Thoughts and comments ?

@nyamsprod : Sounds like a question of taste. I also would go with the secound solution, because it is less code. In my opinion there should not be to much parameters in methods - but with 2 parameters it is not to much.
But i only have seen the writing part of the library, if in general the first solution is already implemented more often, i would stay with that one.
Hope this helps a little to get a decision.

@tom-d-77 even thought most of the other setters uses the setter/getter option I believe I want to make a exception for that rule here as choosing the right engine is important and the dev should really be in control of what he wants to do. The second option forces the developer to choose wisely which is a good thing IMHO.

@nyamsprod I think you are right - the developer should know which "writer mode" is used. One more thought about it: If the second parameter has a default value, developers tend to use the default value (this is also true for me). So it may be a good decision, to set no default value to it, and throw a self explaning Error if it is not set.

I can do that as it would be BC break .. the parameter needs to be optional ... but should be required in the next major release it's the only tradeoff I see

@nyamsprod It was just a additional thought from me - i think your solution is valid in terms of a coding view.

I ran into this exact same issue when trying to insert arbitrary text from a database, where some of the rows contain backslashed double quotes, commas, and newlines. Here's a code example:
$csv = Writer::createFromFileObject(new SplTempFileObject());

$exampleText = <<<'EOD'
"Some text with \"backslashed\" double quotes"
Another line with "double" quotes, and a comma
EOD;

$rows = [
    ['a' => 'row 1', 'b' => 'column b'],
    ['a' => $exampleText, 'b' => 'row 2, column b'],
    ['a' => 'row 3', 'b' => 'column b'],
];

$csv->insertAll($rows);
$csv->output('escape_bug.csv');

When I open the CSV in Excel, it's completely broken:

The double quotes are messed up, the newline created a new row, and the comma split the text into another column!
Actual CSV contents
"row 1","column b"
"""Some text with \"backslashed\" double quotes""
Another line with ""double"" quotes, and a comma","row 2, column b"
"row 3","column b"

Expected CSV contents
"row 1","column b"
"""Some text with \""backslashed\"" double quotes""
Another line with ""double"" quotes, and a comma","row 2, column b"
"row 3","column b"

I dug into the code for the Writer class and traced the issue back to the fputcsv PHP function, which takes an $escape_char argument defaulting to a backslash. Apparently any enclosure characters (double quotes) preceded by the escape character aren't escaped.
It turns out there is a thread on PHP internals about the issue here: https://externals.io/message/100729. The issue could be fixed in PHP by allowing a blank string to be passed to fputcsv for the escape character.
I was able to work around the bug by adding the following line before the call to $csv->insertAll:
$csv->setEscape("\0");

Perhaps this library could also work around the issue by simply changing the default escape character to a null byte.

@theodorejb thanks for the input. When I say that

After some digging I found the source of the issue but resolving it won't be as simple as I thought. The main issue is that PHP fputcsv is broken beyond repair and can never generate a valid RFC4180 compliant CSV.

It's because I did the same research as yours but we differ on the solution. I can not change the default settings of the lib otherwise:

it is a major BC break so change to null byte is not a solution.
In addition, changing to the null byte is essentially a hack what happens if you CSV document contains such character ?

Bottom line, I've submitted a PR #309 which fix this issue and also allow broader support for RFC4180 in the library. The only downside is deprecating RFC4180Field filter and for those using it we will update the documentation and provide guidance between upgrading to the new release OR changing the espace delimilter to the null bytes otherwise if possible.

@nyamsprod You're right that using a null byte as the default escape character would be a BC break, and it's somewhat of a hack that may not work in every situation.
I'm not entirely convinced that adding a new writing mode parameter is the best solution, however. It's still possible that the issue could be fixed in PHP by allowing a blank string to be set as the escape character. In the meantime before PHP allows this, perhaps this library could special-case calling setEscape(''), which would switch to a writing mode that doesn't use fputcsv. In the next major version of League/Csv, this could be the default. Then if PHP eventually supports a blank string as the escape character, the separate writing mode could be removed.
Are there any other important differences in the RFC4180 writing mode other than ignoring the escape character? If so, I'm concerned that it might be a bigger BC break than just allowing a blank escape character but keeping the rest of the fputcsv behavior. Also, how does the new writing mode perform compared to the native PHP function?

@theodorejb the following PR #309 contains the fix TL;DR it falls back to using fwrite instead of fputcsv.

It's still possible that the issue could be fixed in PHP by allowing a blank string to be set as the escape character. In the meantime before PHP allows this, perhaps this library could special-case calling setEscape(''), which would switch to a writing mode that doesn't use fputcsv.

Indeed if  the upstream code in fputcsv was patch I would longer need the optional parameter. But since I can not 100% guarantee that this is how the patch will land (using an empty string) I'd rather not rely on a fix which has not yet land, what if the patch uses null or false instead of the empty string ?

I'm not entirely convinced that adding a new writing mode parameter is the best solution, however.

The issue is not with how the patch works but how it is triggered. Should it be triggered by a special input for the escape character OR should it be triggered by a optional argument on the insertXXX methods.
IMO using an optional argument is the best approach for the following reason If PHP was to fix the escape parameter bug

v9.2.0 introduced the Writer::MODE_RFC4180 relying on fwrite (see #309);
PHP patchs lands on fputcsv;
a patch release for League\Csv is released which switch internally to fputcsv on all modes but still uses fwrite for legacy PHP version;
the next major release drops the Writer::MODE_RFC4180 constant and just relies on fputcsv behavior;

This is clean simple and reliable. On the other hand if we use the "escape" parameter switch and the PHP patch is done differently (let's hope not 😄 ) then we will have to directly release a v10 because of potential bugs. Not to mention that nothing is said for fgetcsv will it be patch too to ignore the escape parameter using the same empty string 🤔
I've seen your post on the PHP internal mailing list 👍  . Let's hope this boost the release of a patch quickly!!

Also, how does the new writing mode perform compared to the native PHP function?

I suppose that benchmark using fwrite decrease insertion speed, but it should depend on the record content length 🤔 You can benchmark the PR to see the difference.

Are there any other important differences in the RFC4180 writing mode other than ignoring the escape character?
yes there's one fputcsv adds enclosures in presence of the white spaces in a record field, RFC4180 does not.

There is now a pull request to fix this in PHP: https://github.com/php/php-src/pull/3515.

@theodorejb @tom-d-77 should we wait for the patch to land ?
If it lands for PHP7.2 and PHP7.1  we will be able to get rid of the flag all together and only fallback to my implementation for version which do not support the empty string. (ie.. this code would never be called in PHP7.3+ for instance)
This would be IMO better because it would be transparent for the end user and provide polyfill for PHP version that do not support the empty string while taking advantage of the patch when possible.

I've updated the patch to get rid of the flag... But I also saw the response on the internals about the patch landing in min. 1 year with PHP 7.4 ... Currently the patch works but I'm not sure about the fgetcsv patch which just replace the escape character with the null byte ... Any suggestions?

@nyamsprod Indeed, it sounds like the PHP patch won't land until 7.4, so a polyfill will be needed for previous versions.
I'm not sure about the fgetcsv approach, either. I don't really like the inconsistency it creates between reading and writing. Conceivably someone could write a CSV containing a null byte before the enclosure character, and then not be able to read it back properly. I feel that it would be better to either use a custom RFC4180-compliant reader, or replace an empty string with a null byte when both reading and writing with the native PHP functions.
Personally I think the latter approach would be fine in practice, since needing to read/write a null byte followed by a double quote seems extremely unlikely compared to reading/writing backslashed quotes.
If a custom writer is used, it also seems like it should match PHP's behavior of always surrounding fields with the enclosure character, so that this behavior won't change when upgrading to PHP 7.4.

@theodorejb patching the PR so that it escape "like" fputcsv patched is easy ... patching fgetcsv is another daunting task as it means it means creating a equivalent of fgetcsv in full userland PHP minus the escape bug... I'll see what can be done I don't like having to use the null byte hack


Lock language-babel grammar to v2.22.0

Same as #3091, except this time we use our own fork to make sure we don't update it again by mistake. Fixes #3178.

:+1: thanks @pchaigno


⚠ Blutopia has degraded performance

In ef0f3cc, Blutopia ($BLU) experienced degraded performance:

HTTP code: 200
Response time: 4875 ms

Resolved: Blutopia performance has improved in 6059fbe after 7 minutes.


The comment inside a pop-up window of the intellisense list is incorrect

Regression Info

Worked in Dev17.4.4

Repro Steps

File > New Project > Blazor Server App > .NET 7.0 > Create
Open Index.razor, Type "<InputText @bind-foo :",verify the intellisense list, and the comment inside a pop-up window of the intellisense list is incorrect

VS version
Not using Legacy Editor (default)
Using Legacy Editor

Dev17.4.4
Not repro
Not repro

Dev17.5 Preview 2
repro
Not repro

Dev17.5 Preview 3
repro
Not repro

Actual behavior
The comment inside a pop-up window of the intellisense list is incorrect

Expected behavior

Note: 'Enable experimental Razor editor' has been replaced with 'Use legacy Razor editor for ASP.NET Core (requires restart)'.
The position of the new feature of 'Use legacy Razor editor for ASP.NET Core (requires restart)' setting in Tools-Options is as follows:

This also reproduces on 17.6 Preview 1, and it's visible when manually typing out the line. (or even copy pasting the line and pressing CTRL+J)


Return Largest Numbers in Arrays - Not Recognizing Correct Answer

The output is same as suggested out put but program doesn't recognize.

This is not an issue with the tests, but a problem with your code. Github issues are not for challenge help. Please visit the Help Chat for assistance. Thanks and happy coding!


ML LLM guide additions

Proposed changes
Add LUMI examples, SFTTrainer mentioned, Ollama example and discussion on quantization.
Preview: https://csc-guide-preview.2.rahtiapp.fi/origin/ml-llm-additions/support/tutorials/ml-llm/
Checklist before requesting a review

[x] I have followed the instructions in the Contributing and Styleguide documents.
[x] My pull request passes the automated tests. If not, visit pull requests at Travis CI and have a look at the job log.
[x] I have included a link to the appropriate preview page (select your branch from the list).

Note to self: Maybe add link to some overview of quantization in LLMs?

Possibly add link to: https://huggingface.co/blog/mlabonne/sft-llama3


Remove mungedocs and md-check

Let's see if it flies?

This change is

@thockin, Are you ready for me to merge this? Or did you want a review from anybody else? @chenopis is OOO today.

If you're happy with it, fire away.  Should I port to other branches?

@thockin, This seems to be working. But I don't understand why we see two Travis CI tests now.
See https://github.com/kubernetes/kubernetes.github.io/pull/5192.


Use ueberzug for preview rendering

ueberzug works in all terminals, so there will be no need to support different renderers

@sarmong Thanks for the report. Sorry for the delay
I was thinking about that but since ueberzug is not maintained anymore I decide to drop this dependency.
For rendering purposes I have plans to create my own tool when possible. That's is why I will close this issue for now. I will revisit this is issue in the couple of months.


Verifying revocation status

When a credential is revoked one can lookup the status of the revocation list. From the response you can confirm the if that status is a 1 or 0 from the position in the bitlist. From my understanding the process to determine this is the pass the encoded list into the vc-status-list library.
From the example 02-VC-status.md there is a code snippet at the bottom for this process:
import * as sl from "@digitalbazaar/vc-status-list";

const decoded = await sl.decodeList({
  encodedList: "H4sIAAAAAAAAA-3BIQEAAAACIKc73RcmoAEAAAAAAAAAAAAAAPgbjSrD2NQwAAA"
});

// return true, which means revoked
console.log(decoded.getStatus(0));

I am not sure from the examples or the vc-status-list repo how to get this check to pass. Can we provide more detail on this process?

Thank you. I understand the process to obtain the encoded list. Where I am struggling is to get the code snippet working to test the revocation status manually (outside of the verify functionality). To me the code snippet does not look to be complete. Can we provide a complete working code snippet:
`import * as sl from "@digitalbazaar/vc-status-list";
const decoded = await sl.decodeList({
encodedList: "H4sIAAAAAAAAA-3BIQEAAAACIKc73RcmoAEAAAAAAAAAAAAAAPgbjSrD2NQwAAA"
});
// return true, which means revoked
console.log(decoded.getStatus(0));`

Sorry, I fail to see what's missing? What would you expect to see? The current snippet just checks the index of a status in the list which is all that's needed to verify if a snippet has been revoked

I cannot get the code to work. Here is the code I am using from the examples (with a few tweaks).
`const { Client, FileContentsQuery } = require("@hashgraph/sdk");
const sl = require ("@digitalbazaar/vc-status-list");
const client = Client.forTestnet();
client.setOperator("0.0.XX", "302eXXX");
async function main() {
const query = new FileContentsQuery().setFileId("0.0.76XXX");
const contents = await query.execute(client);
const statusLists = JSON.parse(String(contents));
// in the credentialStatus, the status list index is 2
const statusListByIndex = statusLists[0];
const decoded = await sl.decodeList({
encodedList: statusListByIndex // could be "H4sIAAAAAAAAA-3BIQEAAAACIKc73RcmoAEAAAAAAAAAAAAAAPgbjSrD2NQwAAA"
});
// return true if revoked or false if not
console.log(decoded.getStatus(1));
}
main();`
When I run this I am hitting an error ERR_REQUIRE_ESM from "const sl = require ("@digitalbazaar/vc-status-list");".
I have tried import this module instead of require but run into different issues.
Have you run into this problem?


[BUG] Fix github action documentation build

The docs build is giving an error while trying to evaluate awq from python 3.12, when it doesn't exist in that version yet.
This change forces the use of python 3.11

Thanks @suparious! Didn't have bandwidth to investigate this yet, but this looks good to me.

Sorry this didn't work. I'd like to help fix this anything else I can help with. Is there a way we can collaborate in real time?

DM me on X
https://twitter.com/casper_hansen_


Add support for setting folder where pypandoc downloads installation files to

Hi.
Would it be posible to be able to specify the path to where pypandoc downloads installation packages for pandoc.
Like where you can set "download_pandoc(targetfolder="path/to/custom/pandoc/folder")"
Installation pages are the files like "pandoc-2.4-windows-x86_64.msi", "pandoc-2.4-windows-x86_64.pkg" and such.
Suggestion:
Extend the pypandoc.download_pandoc function to include an argument for setting the installer download folder.
Something like: download_pandoc(targetfolder/"Here/pandoc/gets/installed", installation_file_cash="here/the/temporary/installation/files/gets/downloaded/to")
And set it so the new parameter defaults to the current working dir (like it does now), if a custom path aren't provided.
Why:
It cause problems for windows users (with User account control) and Mac Os users, if the program that used pypandoc (that tries to download pandoc through pypandoc) are placed in a permission restricted folder (f.x. the C:\Program Files) or in /Applications on mac.

Isn't this what the targetfolder argument does? See https://github.com/bebraw/pypandoc/blob/master/pypandoc/pandoc_download.py#L152

@ecederstrand
this is not what targetfolder does, from the file itself:

targetfolder: directory, where the binaries should be installed.

What that does, is set the path, where pandoc gets installed. What I'm asking for, is an option to set where the pandoc installers (ie pandoc-x.x.msi and the same for mac) gets downloaded to, before getting installed.


suitesparse-graphblas: 9.3.1 -> 9.4.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/DrTimothyAldenDavis/GraphBLAS/releases.
meta.description for suitesparse-graphblas is: Graph algorithms in the language of linear algebra
meta.homepage for suitesparse-graphblas is: https://people.engr.tamu.edu/davis/GraphBLAS.html
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 9.4.2 in filename of file in /nix/store/5p7spavpl2grqshaic5f0a7v5ddlgqlb-suitesparse-graphblas-9.4.2

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

suitesparse-graphblas

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/5p7spavpl2grqshaic5f0a7v5ddlgqlb-suitesparse-graphblas-9.4.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/36c71c53a03721afcc181c2623e3b9802a9949e2#suitesparse-graphblas

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/5p7spavpl2grqshaic5f0a7v5ddlgqlb-suitesparse-graphblas-9.4.2
ls -la /nix/store/5p7spavpl2grqshaic5f0a7v5ddlgqlb-suitesparse-graphblas-9.4.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 2 packages built:

suitesparse-graphblas
suitesparse-graphblas.dev

Maintainer pings
cc @wegank for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 357761

aarch64-darwin

:white_check_mark: 2 packages built:

suitesparse-graphblas
suitesparse-graphblas.dev

@NixOS/nixpkgs-merge-bot merge


Cann't build SolidOak with stable rust

When I builds SolidOak with stable rust I get error:
error: linking with `x86_64-pc-linux-gnu-gcc` failed: exit code: 1
  |
  = note: "x86_64-pc-linux-gnu-gcc" "-Wl,--as-needed" "-Wl,-z,noexecstack" "-m64" "-L" "/usr/lib64/rust-1.16.0/rustlib/x86_64-unknown-linux-gnu/lib" "/tmp/portage/dev-util/SolidOak-9999/work/SolidOak-9999/target/release/deps/solidoak-2f668c0daa3c865a.0.o" "-o" "/tmp/portage/dev-util/SolidOak-9999/work/SolidOak-9999/target/release/deps/solidoak-2f668c0daa3c865a" "-Wl,--gc-sections" "-pie" "-Wl,-O1" "-nodefaultlibs" "-L" "/tmp/portage/dev-util/SolidOak-9999/work/SolidOak-9999/target/release/deps" "-L" "/usr/lib64" "-L" "/usr/lib64" "-L" "/usr/lib64" "-L" "/usr/lib64" "-L" "/usr/lib64" "-L" "/usr/lib64" "-L" "/usr/lib64" "-L" "/usr/lib64" "-L" "/usr/lib64" "-L" "/tmp/portage/dev-util/SolidOak-9999/work/SolidOak-9999/target/release/build/gtk-sys-364a846e4c5d162c/out" "-L" "/usr/lib64" "-L" "/tmp/portage/dev-util/SolidOak-9999/homedir/.cargo/git/checkouts/neovim-rs-d2da26a4d9159b47/a874281/neovim/build/lib" "-L" "/tmp/portage/dev-util/SolidOak-9999/homedir/.cargo/git/checkouts/neovim-rs-d2da26a4d9159b47/a874281/neovim/.deps/usr/lib" "-L" "/usr/lib64/rust-1.16.0/rustlib/x86_64-unknown-linux-gnu/lib" "-Wl,-Bstatic" "-Wl,-Bdynamic" "/tmp/portage/dev-util/SolidOak-9999/work/SolidOak-9999/target/release/deps/libgtk-8c97b5da4e45162b.rlib" "/tmp/portage/dev-util/SolidOak-9999/work/SolidOak-9999/target/release/deps/libpango-055fdd573440e976.rlib" "/tmp/portage/dev-util/SolidOak-9999/work/SolidOak-9999/target/release/deps/libgdk-a8d5f2c55fe44fd5.rlib" "/tmp/portage/dev-util/SolidOak-9999/work/SolidOak-9999/target/release/deps/libneovim-63b4a5a9627f69a5.rlib" "/tmp/portage/dev-util/SolidOak-9999/work/SolidOak-9999/target/release/deps/liblibc-e3f62af94a956a6a.rlib" "/tmp/portage/dev-util/SolidOak-9999/work/SolidOak-9999/target/release/deps/libcairo-594f97a33bd6515c.rlib" "/tmp/portage/dev-util/SolidOak-9999/work/SolidOak-9999/target/release/deps/libc_vec-c14fcb9c0a16a2a7.rlib" "/tmp/portage/dev-util/SolidOak-9999/work/SolidOak-9999/target/release/deps/libglib-f78bd29dbb2abf6f.rlib" "/tmp/portage/dev-util/SolidOak-9999/work/SolidOak-9999/target/release/deps/libgtk_sys-5b17c923dba29348.rlib" "/tmp/portage/dev-util/SolidOak-9999/work/SolidOak-9999/target/release/deps/libgdk_sys-9223286d42563c9c.rlib" "/tmp/portage/dev-util/SolidOak-9999/work/SolidOak-9999/target/release/deps/libcairo_sys-f4399e3e841b7db2.rlib" "/tmp/portage/dev-util/SolidOak-9999/work/SolidOak-9999/target/release/deps/libpango_sys-38158f2ee7602b38.rlib" "/tmp/portage/dev-util/SolidOak-9999/work/SolidOak-9999/target/release/deps/libgdk_pixbuf_sys-29ebd82d76d50229.rlib" "/tmp/portage/dev-util/SolidOak-9999/work/SolidOak-9999/target/release/deps/libatk_sys-2f084c483ab047e7.rlib" "/tmp/portage/dev-util/SolidOak-9999/work/SolidOak-9999/target/release/deps/libgio_sys-33e2893e75c51075.rlib" "/tmp/portage/dev-util/SolidOak-9999/work/SolidOak-9999/target/release/deps/libgobject_sys-4e3267daa88612e7.rlib" "/tmp/portage/dev-util/SolidOak-9999/work/SolidOak-9999/target/release/deps/libglib_sys-2b53c1d2944f8dba.rlib" "/tmp/portage/dev-util/SolidOak-9999/work/SolidOak-9999/target/release/deps/libbitflags-56398aa7a661adb6.rlib" "/tmp/portage/dev-util/SolidOak-9999/work/SolidOak-9999/target/release/deps/liblibc-c2668eb07a902d7f.rlib" "/tmp/portage/dev-util/SolidOak-9999/work/SolidOak-9999/target/release/deps/librustc_serialize-c6bffcf8fd2d6915.rlib" "/usr/lib64/rust-1.16.0/rustlib/x86_64-unknown-linux-gnu/lib/libstd-63283ac5.rlib" "/usr/lib64/rust-1.16.0/rustlib/x86_64-unknown-linux-gnu/lib/libpanic_unwind-63283ac5.rlib" "/usr/lib64/rust-1.16.0/rustlib/x86_64-unknown-linux-gnu/lib/libunwind-63283ac5.rlib" "/usr/lib64/rust-1.16.0/rustlib/x86_64-unknown-linux-gnu/lib/librand-63283ac5.rlib" "/usr/lib64/rust-1.16.0/rustlib/x86_64-unknown-linux-gnu/lib/libcollections-63283ac5.rlib" "/usr/lib64/rust-1.16.0/rustlib/x86_64-unknown-linux-gnu/lib/liballoc-63283ac5.rlib" "/usr/lib64/rust-1.16.0/rustlib/x86_64-unknown-linux-gnu/lib/liballoc_jemalloc-63283ac5.rlib" "/usr/lib64/rust-1.16.0/rustlib/x86_64-unknown-linux-gnu/lib/liblibc-63283ac5.rlib" "/usr/lib64/rust-1.16.0/rustlib/x86_64-unknown-linux-gnu/lib/libstd_unicode-63283ac5.rlib" "/usr/lib64/rust-1.16.0/rustlib/x86_64-unknown-linux-gnu/lib/libcore-63283ac5.rlib" "/usr/lib64/rust-1.16.0/rustlib/x86_64-unknown-linux-gnu/lib/libcompiler_builtins-63283ac5.rlib" "-l" "nvim" "-l" "uv" "-l" "msgpack" "-l" "termkey" "-l" "unibilium" "-l" "vterm" "-l" "util" "-l" "util" "-l" "gtk-3" "-l" "gdk-3" "-l" "pangocairo-1.0" "-l" "pango-1.0" "-l" "atk-1.0" "-l" "cairo-gobject" "-l" "cairo" "-l" "gdk_pixbuf-2.0" "-l" "gio-2.0" "-l" "gobject-2.0" "-l" "glib-2.0" "-l" "vte-2.91" "-l" "z" "-l" "gnutls" "-l" "gdk-3" "-l" "pangocairo-1.0" "-l" "pango-1.0" "-l" "gdk_pixbuf-2.0" "-l" "cairo-gobject" "-l" "cairo" "-l" "gobject-2.0" "-l" "glib-2.0" "-l" "cairo" "-l" "pango-1.0" "-l" "gobject-2.0" "-l" "glib-2.0" "-l" "gdk_pixbuf-2.0" "-l" "gobject-2.0" "-l" "glib-2.0" "-l" "atk-1.0" "-l" "gobject-2.0" "-l" "glib-2.0" "-l" "gio-2.0" "-l" "gobject-2.0" "-l" "glib-2.0" "-l" "gobject-2.0" "-l" "glib-2.0" "-l" "glib-2.0" "-l" "c" "-l" "m" "-l" "dl" "-l" "pthread" "-l" "gcc_s" "-l" "pthread" "-l" "c" "-l" "m" "-l" "rt" "-l" "util"
  = note: /tmp/portage/dev-util/SolidOak-9999/homedir/.cargo/git/checkouts/neovim-rs-d2da26a4d9159b47/a874281/neovim/build/lib/libnvim.a(input.c.o): In function `term_input_init':
          /tmp/portage/dev-util/SolidOak-9999/homedir/.cargo/git/checkouts/neovim-rs-d2da26a4d9159b47/a874281/neovim/src/nvim/tui/input.c:38: undefined reference to `termkey_hook_terminfo_getstr'
          collect2: error: ld returned 1 exit status

Rust version: 1.16.0

Somehow it was fixed. I suppose it can be caused be library order.


i18n(es): Update index, configuration & frontmatter

What kind of changes does this PR include?

Changes or translations of Starlight docs site content

Description

What does this PR change? Give us a brief description.
Update index, configuration & frontmatter based on these commits:

b45719b581353f8d8f0ce0a9b5c89132e902377b
140e729a8bf12f805ae0b7e2b5ad959cf68d8e22
b45719b581353f8d8f0ce0a9b5c89132e902377b
b7b23a2c90a25fe8ea08338379b83d19c74d9037
903a57942ceb99b68672c3fa54622b39cc5d76f8
140e729a8bf12f805ae0b7e2b5ad959cf68d8e22
903a57942ceb99b68672c3fa54622b39cc5d76f8

I'm participating in the hacktoberfest. Could you kindly add the hacktoberfest-accepted tag?


Issue 83

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #83
Test URLs:

Before: https://main--channelco-crn-com--hlxsites.hlx.page/
After: https://issue-83--channelco-crn-com--hlxsites.hlx.live/news/computing/?page=2

@varunmitra can you fix the extra gap at the top of the pages with previous/next before we merge this in


Method printMap not exists in control reference

Following this example, to print map during on click from user, the method printMap from PrintControl ref not exists

Hi,
Can you provide a jsFiddle or a CodePen to reproduce this?
I also recommend to refer to the codepen below for a working example of using the printMap method.
For react-leaflet v1: CodePen
For react-leaflet v2: CodePen
Thanks!


Close PRs for breaking changes while in version-range if patch release fixes it

Example: https://github.com/hoodiehq/hoodie/pull/508
About 3h ago<EMAIL_ADDRESS>was released which broke tests in several repositories I maintain. Only 25minutes later<EMAIL_ADDRESS>was released which fixed the problem. It would be nice if Greenkeeper would do a check with<EMAIL_ADDRESS>and see that tests are now passing, then go ahead and close the PRs for<EMAIL_ADDRESS>itself, with a note that<EMAIL_ADDRESS>was released and it solved the issue.
The same happened several times in the past, it would help with maintaining projects quite a bit :)

With Greenkeeper 2 and threaded PRs this is solved quite nicely. I'll close this issue.


Dont work in Live environment

Recently I integrated PayPal in my application . Everything works fine in sandbox but i got ( Invalid client_id or redirect_uri  ) error in my Live environment.
client_id: AcJevGxT4sKQEKmmXf5N2gN21dXVkl9qhXxgdhJtR2qwajIihPZmfvcD1iXgHZy6rpKH8Q8ntVuZSBzz
Can you please help me ?

hello,I have the same problem, have you solved it?

hello,I have the same problem, have you solved it?

Brother, did you solve it?


display of the hamburger to get the file explorer to show isn't there

I am on mobile and dark mode.  In other themes there is a hamburger item in the top left that I can tap to get the left pan to show which is usually the file explorer.  This isn't present in thiss theme which is my default for desktop.  I prefer to use on mobile but cant without this

You can try to slide the screen to the right, of course I prefer to sliding the title bar

no, swiping right is the back gesture and so it can go back a screen or exits the app.

Try swiping the middle of the screen instead of swiping the edge of the screen

nope, same result

划右上角或者左上角是可以的


fetching alpha1 packages fails to fetch the package

Describe your problem
It looks like when I fetch an old package I only get the Kptfile, but not anything else in that package.  This makes it impossible for me to update the package locally.   The work around I need to resort to then is either getting alpha1 kpt and juggling both of them, or using raw git.
Example:
$ kpt pkg get https://github.com/GoogleCloudPlatform/blueprints.git/catalog/bucket
Package "bucket":
Fetching https://github.com/GoogleCloudPlatform/blueprints@main
From https://github.com/GoogleCloudPlatform/blueprints
 * branch            main       -> FETCH_HEAD
 * [new branch]      main       -> origin/main
Error: Kptfile at "https:/github.com/GoogleCloudPlatform/blueprints/catalog/bucket@main" has an old version ("v1alpha1") of the Kptfile schema.
Please update the package to the latest format by following https://kpt.dev/installation/migration.
$ ls
bucket
$ cd bucket
$ ls
Kptfile

What would I expect instead?
When fetching the old package the new binary should at the very least do what I would do with git - grab the current package and have full contents of it on my local machine.  That way I can fork and migrate.
Steps to fork and migrate:

I do kpt pkg get of an old package
I get a warning which links to a place to download the old kpt
If I proceed I am obviously interested in migrating. I run the fix function written by @phanimarupaka
I am now able to save the updated package to a branch or another git repo.

Q: What happens if I am under impression that I will still be able to get updates upstream?
We should give an error that says that the upstream package is of the old format and the consumer should ask the producer to migrate the package and provide the link to the download of the old binary if they updated by mistake.

Personally, I would expect that I can fetch an alpha1 package. It should download the contents as they are from the repo and prompt me that I need to upgrade (by running kpt fn fix). This is better UX than forcing customers to leave kpt and figure out the right Git commands to get a copy of the package.

I think it would be confusing to just fetch a package using kpt pkg get and making the functionality equivalent to git clone. kpt pkg get does many more things than just fetching the package and users have different expectations from get command.
In v0.39 kpt pkg get does the following things

Fetches the package (= git clone)
Adds Kptfile to top level folder if it is not present
Updates the upstream section of Kptfile
Applies auto-setters

Now we are saying if the fetched package is of old version, then just exit after step 1. I think if would confuse users more when kpt pkg get behaves differently.
Instead, users are prompted to use, git clone which makes it very clear as to what to expect of that command. I think we should not make changes for now and wait for more feedback.

Why couldn't we fetch the package, run kpt fix, then add upstream info?

You mean kpt1 pkg get should fetch any package, run fix ? That would be confusing and doesn't fall under the contract of get command. We should have migration to be a clear step and users should know what to expect from it.
This is better UX than forcing customers to leave kpt => git is already part of kpt workflow for initializing and committing changes. So it is not a new thing to use git.

I think other options are on the table as well.  One of the ideas to explore is possibly to use the checkout with "detached head" which explicitly disables upstream rebase down the line: https://www.git-tower.com/learn/git/faq/detached-head-when-checkout-commit/
So if there is a command to get a detached pkg get command then people can fix it locally.
My fear is that without having 1-2 commands that easily help migration a large portion of the packages we are forcing the package consumer to do too much.  What's losing here is kpt.

You mean kpt1 pkg get should fetch any package, run fix ? That would be confusing and doesn't fall under the contract of get command. We should have migration to be a clear step and users should know what to expect from it.

Fine, we don't need to run fix automatically but I think it is still reasonable to expect kpt pkg get to be able to fetch older packages.

This is better UX than forcing customers to leave kpt => git is already part of kpt workflow for initializing and committing changes. So it is not a new thing to use git.

It is new to require consumers to make their own checkout of the entire upstream repo.

Another data point to consider here is the desire to support the following use cases:

#2300 by @bgrant0607
#2352 by @justinsb
local packages to aid in working in a monorepo without having to go through git roundtrips (https://kubernetes.slack.com/archives/C0155NSPJSZ/p1625160488048400)

All of those use cases would probably result in not being able to fully support a 3 way merge and I am not sure that customers would expect that.  The higher order decision here is - do we support what the upstream storage system supports (lowest level being rsync) or do we limit the upstream storage and format because we want to ensure advanced merge scenarios.

We should be able to support a 3-way merge with OCI, with an opinionated versioning model.

So we have discussed supporting backwards compatibility and automatic migration of kpt v1alpha1 packages. Given the number of changes to the package format and the functionality in kpt v1, this will require significant amount of work and it will not be a seamless migration. We just don't think the resulting experience will be worth the additional effort and complexity required. Given that we have published the v1 version of the package format, it should not change in any backwards incompatible ways unless there is a v2 version of the format at some point in the future.
As for supporting OCI, I expect we will be able to do that with 3-way merge. The current package schema is designed to allow for non-git storage backends.
Supporting the "dumb" git protocol will not cause any problems for the 3-way merge. It is still git, so we can fetch old revisions just like we currently do. It is just less efficient and not really widely used.

We don't necessarily need to support automatic migration.
I think the ask here is just to be able to run kpt pkg get and end up with a copy of the package locally which I can then begin to migrate.
What would be the significant complexity in that?

Hello team, this error seems to be persistent. We

The workaround is to download this file from github ASM Packages  and clean up the resources manually by running kubectl delete -f asm/canonical-service/controller.yaml


WIP API Introduce changelogs to the planner

This will compare the "prior release" to the currently checked out commit of the release project. The information is presented in a summary form, as a git log, and a GitHub compare link is provided

This is based off of the #143 PR branch.
WIP because I think this needs:

[x] Don't show the changelog when asking for a prior version
[x] Some indication of where intermediary tags exist in the given log
[ ] I think the log is showing merge commits. Probably doesn't need that
[x] Preferably some smarts to calculate whether the current branch of the release project already matches the previously released tag.
[ ] Tests

Excuse the awful commit names. I've just pushed a change that does three items from my wishlist:

Don't show the changelog when asking for a prior version
Some indication of where intermediary tags exist in the given log
Preferably some smarts to calculate whether the current branch of the release project already matches the previously released tag.

If and when this is merged, be sure to update release checklist (not merged yet) that refers to this PR

This would be awesome to get finished. I'm sure you guys are wishing you had this right now 😅 . I'll try and put some time towards this now that I actually have a desk at home again.

Hey @ScopeyNZ, congratulations on getting a desk ;) We're looking to put some work into Cow over the next couple of weeks. If there's specifics with this PR (or others) that you'd like some support on let us know :)

I think this is mostly working. Just needs tests to prove it 😅 . I would feel awful asking a different developer to write tests for my code

Here's the behaviour I'm seeing with this branch checked out when running release:plan against CWP 2.5.0-rc1:

It seems to hide all the individual modules inside the recipes. Not sure if this is expected.

.cow.json

{
    "cwp/cwp-recipe-kitchen-sink": {
        "PriorVersion": null,
        "Version": "2.5.0-rc1",
        "Changelog": null,
        "Items": {
            "cwp/cwp-installer": {
                "PriorVersion": "2.4.0",
                "Version": "2.5.0-rc1",
                "Changelog": null,
                "Items": [],
                "Branching": null
            },
            "cwp/agency-extensions": {
                "PriorVersion": "2.3.0",
                "Version": "2.3.1",
                "Changelog": null,
                "Items": [],
                "Branching": null
            },
            "cwp/watea-theme": {
                "PriorVersion": "3.0.1",
                "Version": "3.0.1",
                "Changelog": null,
                "Items": [],
                "Branching": null
            },
            "silverstripe/controllerpolicy": {
                "PriorVersion": "2.1.0",
                "Version": "2.1.0",
                "Changelog": null,
                "Items": [],
                "Branching": null
            },
            "silverstripe/crontask": {
                "PriorVersion": "2.1.3",
                "Version": "2.1.3",
                "Changelog": null,
                "Items": [],
                "Branching": null
            },
            "silverstripe/gridfieldqueuedexport": {
                "PriorVersion": "2.3.0",
                "Version": "2.3.0",
                "Changelog": null,
                "Items": [],
                "Branching": null
            },
            "silverstripe/ldap": {
                "PriorVersion": "1.1.2",
                "Version": "1.1.2",
                "Changelog": null,
                "Items": [],
                "Branching": null
            },
            "silverstripe/recipe-content-blocks": {
                "PriorVersion": "2.4.0",
                "Version": "2.5.0-rc1",
                "Changelog": null,
                "Items": [],
                "Branching": null
            },
            "dnadesign/silverstripe-elemental-userforms": {
                "PriorVersion": "3.0.0",
                "Version": "3.0.0",
                "Changelog": null,
                "Items": [],
                "Branching": null
            },
            "silverstripe/textextraction": {
                "PriorVersion": "3.0.3",
                "Version": "3.0.4",
                "Changelog": null,
                "Items": [],
                "Branching": null
            },
            "silverstripe/realme": {
                "PriorVersion": "3.1.3",
                "Version": "3.1.3",
                "Changelog": null,
                "Items": [],
                "Branching": null
            },
            "silverstripe/ckan-registry": {
                "PriorVersion": "1.1.0",
                "Version": "1.1.1",
                "Changelog": null,
                "Items": [],
                "Branching": null
            },
            "silverstripe/mfa": {
                "PriorVersion": "4.0.0",
                "Version": "4.0.2",
                "Changelog": null,
                "Items": [],
                "Branching": null
            },
            "silverstripe/totp-authenticator": {
                "PriorVersion": "4.0.0",
                "Version": "4.0.0",
                "Changelog": null,
                "Items": [],
                "Branching": null
            },
            "silverstripe/webauthn-authenticator": {
                "PriorVersion": "4.0.0",
                "Version": "4.0.1",
                "Changelog": null,
                "Items": [],
                "Branching": null
            },
            "silverstripe/security-extensions": {
                "PriorVersion": "4.0.0",
                "Version": "4.0.1",
                "Changelog": null,
                "Items": [],
                "Branching": null
            },
            "silverstripe/login-forms": {
                "PriorVersion": "4.0.0",
                "Version": "4.1.0",
                "Changelog": null,
                "Items": [],
                "Branching": null
            }
        },
        "Branching": null
    }
}

Ah right - I see what you mean. It does that if you've chosen an existing tag for a recipe. Makes sense, you can't change the versions of a recipe that's already tagged. I can't remember what the logic is in the PR for doing this - it should assume recipes need releases.

I've been working on this a bit today.  It looks to see if the most recent prior release is also the HEAD commit. In the case of me trialing a 2.5.0-rc2 right now, it's expecting not to release any child recipes because the head commit is already tagged as the prior rc1 release. There's a few problems here to work out:

[ ] RC1 shouldn't be counted. Any stability attributes of a release should probably be ignored for prior releases. I think that makes sense as even in the case of creating an RC2 you would still want commits showing since the last stable, not since the last RC.
[ ] We'll need to codify the modules we want to remain in lock-step. This is a little annoying, but should be a pretty trivial addition to .cow.json (in cwp/cwp-recipe-kitchen-sink`
[ ] It's not currently considering the children of recipes. Just checking that the HEAD commit is tagged is not enough. It also needs to check (recursively) that it's children all have their HEAD commits tagged with the latest prior (non unstable) release too.

I'll start working on this and commit with how far I get this afternoon.

Ok I did the hardest of the three problems. The other two shouldn't be too bad, but I'm done for the day. Not sure if I'll get another chance to work on this until next weekend.

This pull request hasn't had any activity for a while. Are you going to be doing further work on it, or would you prefer to close it now?

I'm realistically never going to use this library again Steve. This is work that we would've really appreciated when I was in your team using this tool. It's entirely up to you whether you think this still has value.
I'm definitely not going to work further on this.

Totally fair. This change would reduce a lot of toil in our release process, so it's definitely valuable, but we're not in a position to dedicate time to it at the moment. I think we'll close it out for now, but will use it as a starting point for a future endeavour. Thanks for all of your work, @ScopeyNZ ❤


docs: fix to correct package name (config-conventional)

Description
Fix to correct package name (maybe typo):
@commitlint/config-conventions => @commitlint/config-conventional
Motivation and Context
Motivation to correct package documentation.
Usage examples
N/A
How Has This Been Tested?
N/A
Types of changes

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

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Thanks!


studio: Include docs URL in warnings

    > When docs are ready I will update to include the link in the message

Do we need an issue for it to not forget/add it to our shared checklist?
Originally posted by @mvshmakov in https://github.com/iterative/dvclive/pull/391#discussion_r1045844930

Not needed if we implement https://github.com/iterative/studio/issues/4801


New version brokes with Django==1.5.10 and six==1.3.0

   File "/var/www/.virtualenvs/ditchcity/local/lib/python2.7/site-packages/django/db/models/loading.py", line 72, in _populate
     self.load_app(app_name, True)
   File "/var/www/.virtualenvs/ditchcity/local/lib/python2.7/site-packages/django/db/models/loading.py", line 94, in load_app
     app_module = import_module(app_name)
   File "/var/www/.virtualenvs/ditchcity/local/lib/python2.7/site-packages/django/utils/importlib.py", line 35, in import_module
     __import__(name)
   File "/var/www/.virtualenvs/ditchcity/local/lib/python2.7/site-packages/compat/__init__.py", line 42, in <module>
     from six.moves._thread import get_ident  # noqa
 ImportError: No module named _thread

ubuntu@staging:~$ python --version
Python 2.7.6

django-compat intends to provide for- and backwards compatibility to all version supported by django itself. This is the list of all supported version at the moment.  More info can be taken from the mailing list.

(@joac the idea is to make all your apps "compatible" using compat and then upgrade django itself to the next or latest greatest release.)


Rewrite to TypeScript

Do not merge, this currently doesn't work 😞
this.$gtm not typed in external project 🤔

Found out that it indeed worked
I just had to remove node_modules/vue from projects dir when using yarn link "vue-gtm" to test the repo
Otherwise declare module "vue/types/vue" will override the internal vue package interface instead of the repos one from the project that uses the plugin 🤕
I will release a beta 2.4.0-typescript-beta.1 and try it out in real world project

YES! :tada: It's working :smile:
Also JSDocs are available and $gtm-methods also.
When I had used yarn link, there were no JSDoc :thinking:
Maybe cause I also had to remove node_modules completely instead just node_modules/vue :man_shrugging:

@mib200 Do you want to review such PRs? Or should I just merge it?
I also want to rewrite the README.md file and improve the code with some sugar like nullish coalescing and so on.


chore(deps): upgrade jenkins-x/jx3-pipeline-catalog to version 3.10.121

from: https://github.com/jenkins-x/jx

/retest


arlon controller image v0.9.0 crashes with "config file has incorrect permission flags"

ubuntu@ip-10-0-30-109:~/downloads$ kubectl -n arlon get pod
NAME                               READY   STATUS             RESTARTS         AGE
arlon-controller-569c94696-cmnhn   0/1     CrashLoopBackOff   29 (2m22s ago)   126m
ubuntu@ip-10-0-30-109:~/downloads$ kubectl -n arlon logs arlon-controller-569c94696-cmnhn
time="2022-08-31T22:42:15Z" level=fatal msg="config file has incorrect permission flags:-rw-r--r--.change the file permission either to 0400 or 0600."

It's possible the newer version of argocd library we're using is stricter with the permissions on the config file.
Aha! Link: https://pf9.aha.io/features/ARLON-289

Confirmed that image version 0.3.0 works, so this only affects 0.9.0+. So it is a change in logic in the argocd library code.
After tinkering, haven't found a solution yet. The pod runs as a non-root user. But the file projected from the secret is owned by root. If we set the permissions to something like 0400, arlon/argocd cannot read the file. But if the permissions are changed back to 0644, then it can read the file, but it'll complain about the permissions and exit (see above). And Kubernetes offers no way of changing the file ownership: https://github.com/kubernetes/kubernetes/issues/81089


[Crash] on startup on MacOS Mojave

Lapce crashes on start up.
Error log can be found here:
https://pastebin.com/B3h40Hgm
I am running MacOs Mojave (10.14.6) on a MacBookPro 2011 (exact specs can be found in the crash report)

duplicate of https://github.com/lapce/lapce/issues/889


常用字 broken on the deployed site

只顯示常用字 shows no result (the other two modes working as intended).
Looks like the built index.ts does not contain the content of 常用字頻序表.txt
Strangely, I'm currently unable to reproduce on my computer :thinking:
Will investigate later today.
Update:
Here is the culprit: The URL of '常用字頻序表.txt' is not encoded properly, as the actual fetched content says:
Couldn't find the requested file /texts/å¸¸ç¨åé »åºè¡¨.txt in ayaka14732/syyon-vencie.

Changing the "postinstall" script to bun -e "Bun.write('常用字頻序表.txt', await fetch('https://cdn.jsdelivr.net/gh/ayaka14732/syyon-vencie/texts/常用字頻序表.txt'))" (suggestion from: https://github.com/nk2028/tshet-uinh-tools/pull/13#issuecomment-2271797391) seems to fix the problem. (with the only drawback being Bun-exclusive)

Changing the "postinstall" script to bun -e "Bun.write('常用字頻序表.txt', await fetch('https://cdn.jsdelivr.net/gh/ayaka14732/syyon-vencie/texts/常用字頻序表.txt'))" (suggestion from: #13 (comment)) seems to fix the problem. (with the only drawback being Bun-exclusive)

Works ✓


pwhash example

Still working on more complete documentation for pwhash, but as you mentioned adding examples in #81 I thought I'd drop this one in. Checked and working with current master.

Thanks!!


Add coffee-script to deps for safety

Noticed rewire was catching this, and checking over there its still expecting an old dep: https://github.com/jhnns/rewire/blob/master/package.json#L33

(Re updating rewire upstream, I think changing coffee-script to coffeescript was someone contentious. I don't want to rock the boat for those depending on it.)