AttributeError: Can only use .str accessor with string values!

Hello,
Thanks for making this useful tool!  I am trying to get it working on my own data set but ran into some errors.
I followed the instructions and converted my preprocessed Seurat object as:
require(Seurat)
require(DropletUtils)
hs1 <- readRDS('~/scdata.rds')
If the object contains only gene expression:

write10xCounts(x = hs1@assays$RNA@counts, path = './hs1_mtx/')

Can you confirm that if I have access to the original mtx file that I still need to do the above?  The rds file I am using has been filtered/preprocessed (so has fewer cells than the original mtx).
Then I ran setup as follows:
python ~/conga/scripts/setup_10x_for_conga.py --filtered_contig_annotations_csvfile filtered_contig_annotations.csv --output_clones_file out-clones.tsv --organism human
I see these files created:
out-clones.tsv.barcode_mapping.tsv
out-clones.tsv
out-clones_AB.dist_50_kpcs

Then I called run_conga as follows:
python conga/scripts/run_conga.py --all --gex_data conga_mtx/hs1_mtx/ --gex_data_type 10x_mtx --clones_file out-clones.tsv --organism human --outfile_prefix tmp_out-clones
and get the following output.  I was hoping to get some help to figure out how to get rid of the error.
Thanks for your help!
@s2hui
--all implies --graph_vs_graph ==> Running graph_vs_graph analysis.
--all implies --graph_vs_graph_stats ==> Running graph_vs_graph_stats analysis.
--all implies --graph_vs_features ==> Running graph_vs_features analysis.
--all implies --cluster_vs_cluster ==> Running cluster_vs_cluster analysis.
--all implies --find_hotspot_features ==> Running find_hotspot_features analysis.
--all implies --find_gex_cluster_degs ==> Running find_gex_cluster_degs analysis.
--all implies --tcr_clumping ==> Running tcr_clumping analysis.
--all implies --match_to_tcr_database ==> Running match_to_tcr_database analysis.
--all implies --make_tcrdist_trees ==> Running make_tcrdist_trees analysis.
WARNING: If you miss a compact list, please try `print_header`!
The `sinfo` package has changed name and is now called `session_info` to become more discoverable and self-explanatory. The `sinfo` PyPI package will be kept around to avoid breaking old installs and you can downgrade to 0.3.2 if you want to use it without seeing this message. For the latest features and bug fixes, please install `session_info` instead. The usage and defaults also changed slightly, so please review the latest README at https://gitlab.com/joelostblom/session_info.
-----
anndata     0.7.5
scanpy      1.8.1
sinfo       0.3.4
-----
PIL                 8.3.1
cairocffi           1.2.0
cffi                1.12.2
colorama            0.4.1
conga               NA
cycler              0.10.0
cython_runtime      NA
dateutil            2.8.0
defusedxml          0.7.1
h5py                2.10.0
igraph              0.8.3
joblib              0.14.1
kiwisolver          1.0.1
leidenalg           0.8.3
llvmlite            0.32.0
matplotlib          3.4.3
mpl_toolkits        NA
natsort             7.1.0
numba               0.49.0
numexpr             2.7.3
numpy               1.19.5
packaging           20.8
pandas              1.2.0
pkg_resources       NA
psutil              5.7.0
pyparsing           2.3.1
pytz                2019.3
scipy               1.4.1
six                 1.12.0
sklearn             0.22.2.post1
statsmodels         0.12.2
tables              3.6.1
texttable           1.6.3
typing_extensions   NA
wcwidth             0.2.5
yaml                5.1.1
zipp                NA
-----
Python 3.7.2 (default, Dec 29 2018, 06:19:36) [GCC 7.3.0]
Linux-3.10.0-1160.36.2.el7.x86_64-x86_64-with-centos-7.9.2009-Core
38 logical CPU cores, x86_64
-----
Session information updated at 2021-09-28 10:36

reading: conga_mtx/hs1_mtx/ of type 10x_mtx
conga/conga/preprocess.py:221: DeprecationWarning: Use is_view instead of isview, isview will be removed in the future.
  if adata.isview: # ran into trouble with AnnData views vs copies
total barcodes: 5557 (5557, 33538)
reading: out-clones.tsv
reading: out-clones_AB.dist_50_kpcs
Reducing to the 0 barcodes (out of 5557) with paired TCR sequence data
Traceback (most recent call last):
  File "conga/scripts/run_conga.py", line 378, in <module>
    suffix_for_non_gene_features = args.suffix_for_non_gene_features,
  File "conga/conga/preprocess.py", line 393, in read_dataset
    store_tcrs_in_adata( adata, tcrs )
  File "conga/conga/preprocess.py", line 168, in store_tcrs_in_adata
    adata.obs['cdr3a_nucseq'] = adata.obs.cdr3a_nucseq.str.lower()
  File ".local/lib/python3.7/site-packages/pandas/core/generic.py", line 5456, in __getattr__
    return object.__getattribute__(self, name)
  File ".local/lib/python3.7/site-packages/pandas/core/accessor.py", line 180, in __get__
    accessor_obj = self._accessor(obj)
  File ".local/lib/python3.7/site-packages/pandas/core/strings/accessor.py", line 154, in __init__
    self._inferred_dtype = self._validate(data)
  File ".local/lib/python3.7/site-packages/pandas/core/strings/accessor.py", line 218, in _validate
    raise AttributeError("Can only use .str accessor with string values!")
AttributeError: Can only use .str accessor with string values!

Hi,
Thank you for your interest and for trying out the software. To answer your first question, you do not need to export the matrix from Seurat if you have access to the cellranger outputs. Either the cellranger mtx files or the h5 matrix file can be used. Regarding your error, it seems none of the cell barcodes in your GEX matrix aligned to those in your out-clones.tsv file. One common reason for this is a discrepancy between the barcode suffixes in the GEX matrix and the filtered_contig_annotations.csv file. Can you confirm if this is the case? Using the pre-Seurat GEX matrix instead of the exported one may fix the issue if the suffixes were changed after you processed it through Seurat.

Hello, Thanks for your reply.  As it turns out, I wasn't using the correct gex matrix that matched the filtered_contig_annotations.csv file!  It works now!


webView downloads corrupted file when blob url

Hello.
Thank you for you library.
I tried to handle blob url and download file from it. For example my blob url: "blob:http://example.com/bd0ae6c8-796c-488e-b691-cee86fa72f04".
But downloadData function return me corrupted file.
I tried to take your last commit with removeBlob method.
PS: In desktop browser file downloading normal.
Sorry I cannot give you example link, because I am testing on local url.
For android I user js method (XMLHttpRequest) for download blob url. But for iOS it does not work.
webView.evaluateJavaScript("javascript: var xhr = new XMLHttpRequest();" +
            "xhr.open('GET', '" + blobUrl + "', true);" +
            "xhr.setRequestHeader('Content-type','" + mimeType + "');" +
            "xhr.responseType = 'blob';" +
            "xhr.onload = function(e) {" +
            "    if (this.status == 200) {" +
            "        var blob = this.response;" +
            "        var reader = new FileReader();" +
            "        reader.readAsDataURL(blob);" +
            "        reader.onloadend = function() {" +
            "            base64data = reader.result;" +
            "            window.webkit.messageHandlers.callback.postMessage(base64data);" +
            "        }" +
            "    }" +
            "};" +
            "xhr.send();")

Does not call in onload function.
Any help?

@gualtierofrigerio  Yes, onload never called. xhr.onerror called with status 0 and empty responseText

And additionally I asked question on stackoverflow


Revamp hub issue commands

This marks hub issue family of commands coming out of beta.

hub issue cleaner output

doesn't include pull requests
red/green color based on closed/open state
list both open and closed issues with hub issue -s all

All commands reimplemented using simpleApi and not go-octokit

hub issue create small tweaks for compatibility with hub release create

Todo:

[ ] Implement other hub issue filtering options

[ ] Add hub issue --format=... option to choose which fields to output a la git log

[ ] List all pages of results from API (currently consuming just 1st page)

[ ] Cache previously fetched pages locally

[ ] hub issue edit command to change labels, assignee, closed/open state

[ ] hub issue comment command to add a comment to the thread?

[ ] Ability to list all your issues a la Issues Dashboard, i.e. not project-specific?
[ ] Flag to specify a repository to manage issues for, e.g. if not in a git working directory?

I can confirm that this PR also works with Ubuntu 15.10 (where hub 2.2.3 failed to retrieve anything). Sweet, thanks!

@pcorpet I've pushed some extra features and will merge this to master as the first iteration of the new issue command. Additional upgrades should come in form of separate PRs.

Add multiple assignees & milestone support
Add hub issue create --browse flag
--format placeholders renamed & expanded (see below)
All pages of API results now fetched. We'll have to figure out some caching strategy.

%I: issue number

%i: issue number prefixed with "#"

%U: the URL of this issue

%S: state (i.e. "open", "closed")

%sC: set color to red or green, depending on issue state.

%t: title

%l: colored labels

%L: raw, comma-separated labels

%b: body

%au: login name of author

%as: comma-separated list of assignees

%Mn: milestone number

%Mt: milestone title

%NC: number of comments

%Nc: number of comments wrapped in parentheses, or blank string if zero.

%cD: created date-only (no time of day)

%cr: created date, relative

%ct: created date, UNIX timestamp

%cI: created date, ISO 8601 format

%uD: updated date-only (no time of day)

%ur: updated date, relative

%ut: updated date, UNIX timestamp

%uI: updated date, ISO 8601 format

Cool, thanks. Do you have an idea of a feature / issue I could help with to get a new release of hub with the code currently in master? (I saw you created a 2.2.5 but it seems to cherry-pick only some small fixes).

Do you have an idea of a feature / issue I could help with to get a new release of hub with the code currently in master?

Your help is greatly appreciated. Here are my ideas for the next release: https://github.com/github/hub/issues/1232
Obviously, not everything will probably make it in. I'm leaving on vacation for 2 weeks next week, so by the end of this week I was thinking to try to push a prerelease with the stuff currently in master.


bug(drag-and-drop): Drag and drop not animating

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
https://material.angular.io/cdk/drag-drop/examples
This may or may not be a bug i apologise, but I can't seem to for the life of me get the drag and drop functionality to animate when dragging about.
The drag/drop functionality itself works fine, but I can see in that demo above that when you drag, the cdkDrag element gets css applied such as transform: translate3d(...) etc but i get no such css applied.
Reproduction
StackBlitz link:
Steps to reproduce:
1.
2.
Expected Behavior
Css to transition when dragging is applied
Actual Behavior
No css is applied,
Environment

Angular: 18.2.2
CDK/Material: 18.2.2
Browser(s): Chrome
Operating System (e.g. Windows, macOS, Ubuntu): OSX

Urgh, nevermind, found it buried in the docs for the "mixed" mode:
It has the advantage of allowing the items to wrap to the next line, but it cannot animate the sorting action.
Any plans to support animations with mixed?

There are no plans to support animations for mixed orientation. The problem is that we need to be able to predict the size and position  of the elements after they're re-ordered and that can be difficult with some CSS layouts.


Add ability to see passed specs via tooltips

This is my first PR against atom, so let me know if I've gotten anything wrong.
It's not currently possible to see what specs pass when you ctrl-alt-cmd-P. You see that some tests pass (via the red and green dots), but you can't see which ones (except by process of deduction by looking at which fail)
This PR adds the description of the spec, as well as all it's parent suites, to a tooltip so you can see what's passing and failing on mouseover.
I couldn't find tests for atom-reporter. Given the simplicity of the change and the overhead of learning how to write tests for this component, it didn't seem worthwhile. If there are already specs for it, please point me to them and I'll be happy to add a quick test.
Before: (no tooltip)

After: (tooltip, showing suite and test name)

I'm :+1: on this.  Any chance you can upload an image of this in action?

@50Wliu Cool, thanks. Just added an image.

I looked at the tests on circleci (heh), and it looks like an intermittent failure in a different component. Tests pass on the other services.

In your picture it looks like the two describes are flipped?  Shouldn't it be "paredit-el" first and then "Basic Insertion Commands tests"?  Also, the actual spec is missing the leading it,

@50Wliu I forgot to reverse the order when traversing the parents. And great suggestion on adding "it" - I'm new to BDD so it hadn't occurred to me.
Code and "after" screenshot are updated.

@atom/feedback any comments?

⚡  This is a great improvement; thanks so much for adding it @pbiggar! And nice to see you again, also. I left one question, but otherwise I'd love to 🚢  this.

I couldn't find tests for atom-reporter. Given the simplicity of the change and the overhead of learning how to write tests for this component, it didn't seem worthwhile.

Yeah, there are no tests on it currently; thanks for checking.

This will be released in Atom v1.11.

Awesome, thanks!


New Topic: SignalR Groups and Users

We should have a topic that expands on Groups and Users in SignalR
Some outline notes:

Groups

Use Groups to manage collections of connections you want to be able to broadcast to
It's not possible to enumerate or count the members of a group (because each server only knows about it's own connections, not those on other servers)
Group membership is not preserved when you reconnect
A connection can be a part of multiple groups
Groups are the recommended way for one connection to send to another connection (or connections)
Group names are case-sensitive

Users

Use Users to manage all the connections associated with a single logical user
Adding a custom IUserIdProvider to DI allows you to change the "Identifier" used by SignalR (used in Clients.User(...) calls
User identifiers are case-sensitive.

Might be a dupe of #5910.


TypeScript Site is experiencing 404s

In production, I am seeing the v2 site (as noted on the Documentation page) but other pages are not loading:

Downloads: "The resource you are looking for has been removed, had its name changed, or is temporarily unavailable."
Tools: "The resource you are looking for has been removed, had its name changed, or is temporarily unavailable."
Playground: Stuck infinitely on "Downloading TypeScript...", console shows 404's for various resources

The whole reference site seems to be down.

None of the handbook sidebar links at the "Handbook Reference" or below work.
The search box does nothing.

And there are a ton of JavaScript files and a manifest that return 404.
Everything is broken. 😭

online accident

So they're aware and it's being fixed?

I am now, I've just deployed the v2 site to see if that fixes it ( https://github.com/microsoft/TypeScript-Website/actions/runs/57628789 )

I've tried deploying https://github.com/microsoft/TypeScript-Website/commit/578726141df8c9bde76e38046a64d086fff9a7c4 an older build c3b67960b88a6c853945aef3ba71927f91fcf966 of the site in case it's something which has been added in the last few days

I've tried deploying 5787261 an older build c3b6796 of the site in case it's something which has been added in the last few days

Has this been deployed? Just went to link someone to the playground and saw it was broken like described above. Getting a few errors in the console.

It has, it just doesn't seem to have worked
I'm now trying to deploy an even older v1 without the v2 at all

Still looking at this

Is it possible to access old version for now?

Deploying the old site is having the same problems as deploying the new site I'm afraid.

I've successfully got the current site up and running on our internal staging services: http://testsite-typescript-41eeb979-7eaa-4c74-9d47-9d182c7b61ab.azurewebsites.net/
With luck I can port that over

To me, it looks like your staging website is working.

Note that I am also getting 404s in the Playground. It never stops "Downloading Typescript...":

Alright, I've figured out the underlaying cause and will do a post-mortem once I've got all the site wrapped up and working fine, shouldn't be long now.

OK, that's it back up and running 🎉

Not sure of the usefulness of my comment, but I can't access https://www.typescriptlang.org/tsconfig.

Keep the good work going ! :+1:

That page is only available during the betas, you can get access to it at https://www.typescriptlang.org/v2/tsconfig

Playground appears to be up & running. Other links I have were wrong but everything seems accessible off the main site now. Thanks for the fast replies & updates, @orta & team!

I've created a post-mortem for the downtime: https://github.com/microsoft/TypeScript-Website/issues/385

Good work @orta! Thanks for your timely fixes.


Question: best practices for metric-based monitoring?

Hello!
I'm considering using Elysia for a production project, migrating off of a next.js app. I've been continually frustrated by the next.js ecosystem and regressions, and want to try the bleeding edge of Elysia -- congrats on all your recent success.
I'd love to set-and-forget some production metrics system like datadog APM, which is supported by frameworks like express
Is that something you'd consider building out in Elysia? If not, any tips for hooking into application event lifecycle for an easy production monitoring setup?
Cheers.

Ideally we are building one based on Trace API but it isn't done yet.

Close with introduction of trace.


DEV: Use exec for IPython commands.

This makes the SIGTERM sent by docker stop hit the correct process.

Looks like this doesn't actually work: it makes docker stop work correctly, but ipython notebook can't spawn kernels if it's been exec'ed.  I'm seeing that behavior outside of docker as well, so I'm guessing there's a bug in the interaction between IPython and exec

:unamused:

@rgbkrk FYI, the note here regarding seeing weirdness with exec outside of docker turned out not to be true.
I'm working around this right now using more or less the solution described as Option 3 in https://github.com/ipython/docker-notebook/issues/38.

I'll leave that up to @ssanderson.
@parente has been using supervisord inside docker-stacks.

@krallin recommended tini as a replacement for supervisord (https://github.com/jupyter/docker-stacks/issues/24#issuecomment-139322416) I plan to look into it soon for the docker-stacks.

Closing since this has been in a WIP state for a while, re-open if we continue on with it.

i'm using the notebook-image in a Docker Compose-setup on a local machine for data processing.
in this use-case this patch does help and i'd pledge to merge it.

sorry, it took me a while to notice the kernel-issue.


Jerryliu ch25267 missing dependency bigint in react native

📦 Pull Request
Use ~ to lock dependency versions. Lock whatwg-url to ~8.1.0 to prevent usage of BigInt which RN env has not supported
🗜 Versioning
(Check one!)

[x] Patch: Bug Fix?
[ ] Minor: New Feature?
[ ] Major: Breaking Change?

✅ Fixed Issues

Fixes #131

🚨 Test instructions
Install the latest version
⚠ Update CHANGELOG.md

[x] I have updated the Upcoming Changes section of CHANGELOG.md with context related to this Pull Request.

:rocket: PR was released in<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>:rocket:


"ModuleNotFoundError: No module named 'fastapi'"

Starting last night, whenever I try to run your Colab version of Automatic1111, I get the following error:
Traceback (most recent call last):
  File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/webui.py", line 7, in <module>
    from fastapi import FastAPI
ModuleNotFoundError: No module named 'fastapi'

I tried deleting all of the files from my Google Drive and trying again, but it doesn't help.

Even gradio server is very slow now

I too am experiencing this problem. I get the same error message.

are you using the latest colab ?

are you using the latest colab ?

Yes.

run this in a new cell : !pip install -U fastapi

It gave me the message:
Looking in indexes: https://pypi.org/simple, https://us-python.pkg.dev/colab-wheels/public/simple/ Requirement already satisfied: fastapi in /usr/local/lib/python3.8/dist-packages (0.88.0) Requirement already satisfied: starlette==0.22.0 in /usr/local/lib/python3.8/dist-packages (from fastapi) (0.22.0) Requirement already satisfied: pydantic!=1.7,!=1.7.1,!=1.7.2,!=1.7.3,!=1.8,!=1.8.1,<2.0.0,>=1.6.2 in /usr/local/lib/python3.8/dist-packages (from fastapi) (1.10.2) Requirement already satisfied: anyio<5,>=3.4.0 in /usr/local/lib/python3.8/dist-packages (from starlette==0.22.0->fastapi) (3.6.2) Requirement already satisfied: typing-extensions>=3.10.0 in /usr/local/lib/python3.8/dist-packages (from starlette==0.22.0->fastapi) (4.1.1) Requirement already satisfied: sniffio>=1.1 in /usr/local/lib/python3.8/dist-packages (from anyio<5,>=3.4.0->starlette==0.22.0->fastapi) (1.3.0) Requirement already satisfied: idna>=2.8 in /usr/local/lib/python3.8/dist-packages (from anyio<5,>=3.4.0->starlette==0.22.0->fastapi) (2.10)
Then, when I ran the "Start stable-diffusion" cell, it worked this time.

fastapi should be installed by default, I don't know what caused it to break

module 'ldm.models.autoencoder' has no attribute 'VQModelInterface' This means the current LDSR upscaling script isn't compatible with the sd v2 repo

But I'm using the 1.5 model.

Yes but the SD repo is the new stability one, not the old one from Compvis

Is there a way to fix that?
On Saturday, December 3, 2022 at 01:44:50 AM CST, Ben @.***> wrote:
Yes but the SD repo is the new stability one, not the old one from Compvis
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Yes but the SD repo is the new stability one, not the old one from Compvis

Is there a way to fix that?

Check with the A1111 team, I'm sure they will find a fix

Hello. Same problem.
Traceback (most recent call last):
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/webui.py", line 7, in
from fastapi import FastAPI
ModuleNotFoundError: No module named 'fastapi'
pasted into a new cell: !pip install -U fastapi
but another message came out:
Looking in indexes: https://pypi.org/simple, https://us-python.pkg.dev/colab-wheels/public/simple/
Requirement already satisfied: fastapi in /usr/local/lib/python3.9/dist-packages (0.93.0)
Requirement already satisfied: pydantic!=1.7,!=1.7.1,!=1.7.2,!=1.7.3,!=1.8,!=1.8.1,<2.0.0,>=1.6.2 in /usr/local/lib/python3.9/dist-packages (from fastapi) (1.10.5)
Requirement already satisfied: starlette<0.26.0,>=0.25.0 in /usr/local/lib/python3.9/dist-packages (from fastapi) (0.25.0)
Requirement already satisfied: typing-extensions>=4.2.0 in /usr/local/lib/python3.9/dist-packages (from pydantic!=1.7,!=1.7.1,!=1.7.2,!=1.7.3,!=1.8,!=1.8.1,<2.0.0,>=1.6.2->fastapi) (4.5.0)
Requirement already satisfied: anyio<5,>=3.4.0 in /usr/local/lib/python3.9/dist-packages (from starlette<0.26.0,>=0.25.0->fastapi) (3.6.2)
Requirement already satisfied: idna>=2.8 in /usr/local/lib/python3.9/dist-packages (from anyio<5,>=3.4.0->starlette<0.26.0,>=0.25.0->fastapi) (2.10)
Requirement already satisfied: sniffio>=1.1 in /usr/local/lib/python3.9/dist-packages (from anyio<5,>=3.4.0->starlette<0.26.0,>=0.25.0->fastapi) (1.3.0)
Traceback (most recent call last):
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/webui.py", line 15, in
from modules import import_hook, errors, extra_networks, ui_extra_networks_checkpoints
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/ui_extra_networks_checkpoints.py", line 6, in
from modules import shared, ui_extra_networks, sd_models
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/shared.py", line 9, in
import gradio as gr
ModuleNotFoundError: No module named 'gradio'

what to do?

what to do?
create two code blocks after "Requirements"
1st:
%%writefile requirements.txt blendmodes accelerate basicsr fonts font-roboto gfpgan gradio==3.16.2 invisible-watermark numpy omegaconf opencv-contrib-python requests piexif Pillow pytorch_lightning==1.7.7 realesrgan scikit-image>=0.19 timm==0.4.12 transformers==4.25.1 torch einops jsonmerge clean-fid resize-right torchdiffeq kornia lark inflection GitPython torchsde safetensors psutil albumentations==0.4.3 opencv-python pudb==2019.2 imageio==2.9.0 omegaconf==2.1.1 test-tube>=0.7.5 webdataset==0.2.5 open-clip-torch==2.7.0 kornia==0.6 invisible-watermark>=0.1.5 streamlit-drawable-canvas==0.8.0 xformers fastapi
2nd:
!pip install -r requirements.txt !pip install git+https://github.com/openai/CLIP.git !pip install --upgrade fastapi==0.90.1

Hello, when trying to run AUTOMATIC 1111.ipynb, at the last stage, loading Star Stable-Diffusion I get an error:
"
Traceback (most recent call last):
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/webui.py", line 7, in
from fastapi import FastAPI
ModuleNotFoundError: No module named 'fastapi'"
In my case, what can be done to correct the error?

I have now received a notification that I have exhausted my limit in the Collab.

what to do?
create two code blocks after "Requirements"
1st:
%%writefile requirements.txt blendmodes accelerate basicsr fonts font-roboto gfpgan gradio==3.16.2 invisible-watermark numpy omegaconf opencv-contrib-python requests piexif Pillow pytorch_lightning==1.7.7 realesrgan scikit-image>=0.19 timm==0.4.12 transformers==4.25.1 torch einops jsonmerge clean-fid resize-right torchdiffeq kornia lark inflection GitPython torchsde safetensors psutil albumentations==0.4.3 opencv-python pudb==2019.2 imageio==2.9.0 omegaconf==2.1.1 test-tube>=0.7.5 webdataset==0.2.5 open-clip-torch==2.7.0 kornia==0.6 invisible-watermark>=0.1.5 streamlit-drawable-canvas==0.8.0 xformers fastapi
2nd:
!pip install -r requirements.txt !pip install git+https://github.com/openai/CLIP.git !pip install --upgrade fastapi==0.90.1

It works!!!!


fix race condition in libpod.GetEvents(...)

Fix a race that could cause read errors to be masked.  Masking such
errors is likely to report red herrings since users don't see that
reading failed for some reasons but that a given event could not be
found.
Signed-off-by: Valentin Rothberg<EMAIL_ADDRESS>

LGTM, and a very good catch!
@baude @giuseppe @rhatdan PTAL

nice!
/hold

/hold

/lgtm

/hold cancel


[TASK] Prototype UI for AI Conductor

Description
*** Take a look at video in references first, lmk if you cant access.
** In this context a task is the representation of an app that exists or needs to be built out by the user
Add a new route for our AI conductor, and start the mapping of tasks that get generated for the prompt a user asks.  This list of tasks will come from the Backend.  But for the time being we will hardcode a list of tasks that represent a list of our drag and drop apps.
For MVP we will need to map out this list of tasks, and for each task show the inputs that are tied to that particular app/task.  These inputs will then be gathered from our user (require them to be filled out), to then be consumed as an api for that specific app/task.
Things to keep in mind:
This list of tasks may not always have an associated app for them, we have to keep this in mind and allow the user to create the app associated to said task.
Existing
N/A
Reference
This issue references https://github.com/SEMOSS/community/issues/2
Tasks

[x] #221
[ ] #222
[ ] #240
[ ] Execution of tasks and outputs per app (AI Conductor)
[ ] Scaffold UI and Set up chat Interface (AI Conductor)

Update:
Phillip Kem started a prototype to get the thought process going.
Neel also started a branch called 'ai-pipeline' that utilizes react flow and some idea on the DS that we will have for the pipeline.  Should have some stuff about isInput and isOutput.  But likely alot more to handle different types of operations.

@tombetthauser will get you to look at branch and get exposure, will ask you to take lead on this.  Will be along side as well.

started new branch 219-prototype-ai-conductor

updated app cards last week and incorporated PK's ask to include the app cards as mini versions in the second step so user has flexibility to move between apps without having to go back another screen
new ask: look at app card sizing and refactor
new ask: update input output mapping to be more visual-based
note: does not want to incorporate more chat features


chore: Add pr deployment preview

Description

Motivation & context

Code review

Type of change

[ ] 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 not work as expected)

Checklist

[ ] I have done a self-review of my own code
[ ] Any new and existing tests pass locally with my changes
[ ] My changes generate no new warnings (lint warnings, console warnings, etc)

Closing this PR as these changes are now on a branch + new environment called "staging"


added the documentation for simplicity

Nothing just added the documentation for simplicity and easy to understand

@OscarArroyoVega have a look

Ok
On Tue, Jul 16, 2024, 14:33 OscarAV @.***> wrote:

@.**** requested changes on this pull request.
Hello Sanjay,Thank you! if you take a look to unifyai style (also in dspy)
they don't add "Args" to the docstring, just a single line description.
Just remove the "args" for approval :)
—
Reply to this email directly, view it on GitHub
https://github.com/OscarArroyoVega/dspy/pull/19#pullrequestreview-2179650355,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A43TAWK7CLUCG45QU7V4K5DZMTOUZAVCNFSM6AAAAABK6BOB5GVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDCNZZGY2TAMZVGU
.
You are receiving this because you authored the thread.Message ID:
@.***>


Replace int by size_t for numerous template variables

Traditionally,
most of the templates involving the CALL_FIXED_SIZE mechanism use ints as template parameters where they should be using size_t. This leads to implicit conversions that static analysis (correctly) complains about.

There were a number of template variables in the context of CALL_FIXED_SIZE that were used only for unsigned values, but declared int.  They are now all size_t.


Make RSA-PSS verification use PSA with MBEDTLS_USE_PSA_CRYPTO

Duplicate a test case but with a different expected error due to error translation to and from PSA.
Fixes #5333

The existing code has special treatment for the case when the input starts with a valid signature but the passed sig_len is larger than the length of the signature - in that case we return the special error code MBEDTLS_ERR_PK_SIG_LEN_MISMATCH is a valid signature was found to be a prefix of the input.
It's actually part of the documentation:
 *                  #MBEDTLS_ERR_PK_SIG_LEN_MISMATCH if there is a valid
 *                  signature in sig but its length is less than \p siglen,

This is not a feature I like a lot - I really think when a signature is transmitted, it should be encoded in such a way that its length is known - but it was requested by a user back then, and since it's documented now, I think this is something we have to preserve.
I think we can achieve this in the PSA case by doing the same dance as we do in non-PSA case.
Also, it seems we have a test gap here, as the CI should have caught that. Actually, grep shows that we don't have any test case ensuring that we return MBEDTLS_ERR_PK_SIG_LEN_MISMATCH when we're supposed to. Would you mind adding such a case, at least for pk_verify_ext()?

The existing code has special treatment for the case when the input starts with a valid signature but the passed sig_len is larger than the length of the signature - in that case we return the special error code MBEDTLS_ERR_PK_SIG_LEN_MISMATCH is a valid signature was found to be a prefix of the input.
It's actually part of the documentation:
 *                  #MBEDTLS_ERR_PK_SIG_LEN_MISMATCH if there is a valid
 *                  signature in sig but its length is less than \p siglen,

This is not a feature I like a lot - I really think when a signature is transmitted, it should be encoded in such a way that its length is known - but it was requested by a user back then, and since it's documented now, I think this is something we have to preserve.
I think we can achieve this in the PSA case by doing the same dance as we do in non-PSA case.
Also, it seems we have a test gap here, as the CI should have caught that. Actually, grep shows that we don't have any test case ensuring that we return MBEDTLS_ERR_PK_SIG_LEN_MISMATCH when we're supposed to. Would you mind adding such a case, at least for pk_verify_ext()?

Added that, let me know if it's enough :)


Some environmental issues

Due to the server cuda version, I was unable to use the pytorch1.0.0 version requested by the author. So I upgraded PyTorch to 1.9.1. But then it didn't work.How can I deal with this problem.
_
/opt/conda/envs/semiseg2/lib/python3.6/site-packages/torch/distributed/launch.py:186: FutureWarning: The module torch.distributed.launch is deprecated
and will be removed in future. Use torch.distributed.run.
Note that --use_env is set by default in torch.distributed.run.
If your script expects --local_rank argument to be set, please
change it to read from os.environ['LOCAL_RANK'] instead. See
https://pytorch.org/docs/stable/distributed.html#launch-utility for
further instructions
FutureWarning,
WARNING:torch.distributed.run:*****************************************
Setting OMP_NUM_THREADS environment variable for each process to be 1 in default, to avoid your system being overloaded, please further tune the variable for optimal performance in your application as needed.

Traceback (most recent call last):
File "train.py", line 28, in
Traceback (most recent call last):
File "train.py", line 28, in
from apex.parallel import DistributedDataParallel, SyncBatchNorm
from apex.parallel import DistributedDataParallel, SyncBatchNorm
File "/opt/conda/envs/semiseg2/lib/python3.6/site-packages/apex-0.1-py3.6-linux-x86_64.egg/apex/init.py", line 12, in
File "/opt/conda/envs/semiseg2/lib/python3.6/site-packages/apex-0.1-py3.6-linux-x86_64.egg/apex/init.py", line 12, in
from . import optimizers
File "/opt/conda/envs/semiseg2/lib/python3.6/site-packages/apex-0.1-py3.6-linux-x86_64.egg/apex/optimizers/init.py", line 2, in
from . import optimizers
File "/opt/conda/envs/semiseg2/lib/python3.6/site-packages/apex-0.1-py3.6-linux-x86_64.egg/apex/optimizers/init.py", line 2, in
from .fp16_optimizer import FP16_Optimizer
File "/opt/conda/envs/semiseg2/lib/python3.6/site-packages/apex-0.1-py3.6-linux-x86_64.egg/apex/optimizers/fp16_optimizer.py", line 8, in
from .fp16_optimizer import FP16_Optimizer
File "/opt/conda/envs/semiseg2/lib/python3.6/site-packages/apex-0.1-py3.6-linux-x86_64.egg/apex/optimizers/fp16_optimizer.py", line 8, in
lib.THCudaHalfTensor_normall.argtypes=[ctypes.c_void_p, ctypes.c_void_p]
File "/opt/conda/envs/semiseg2/lib/python3.6/ctypes/init.py", line 361, in getattr
lib.THCudaHalfTensor_normall.argtypes=[ctypes.c_void_p, ctypes.c_void_p]
File "/opt/conda/envs/semiseg2/lib/python3.6/ctypes/init.py", line 361, in getattr
func = self.getitem(name)
File "/opt/conda/envs/semiseg2/lib/python3.6/ctypes/init.py", line 366, in getitem
func = self.getitem(name)
File "/opt/conda/envs/semiseg2/lib/python3.6/ctypes/init.py", line 366, in getitem
func = self._FuncPtr((name_or_ordinal, self))
AttributeError: /opt/conda/envs/semiseg2/bin/python: undefined symbol: THCudaHalfTensor_normall
func = self._FuncPtr((name_or_ordinal, self))
AttributeError: /opt/conda/envs/semiseg2/bin/python: undefined symbol: THCudaHalfTensor_normall
Traceback (most recent call last):
File "train.py", line 28, in
from apex.parallel import DistributedDataParallel, SyncBatchNorm
File "/opt/conda/envs/semiseg2/lib/python3.6/site-packages/apex-0.1-py3.6-linux-x86_64.egg/apex/init.py", line 12, in
from . import optimizers
File "/opt/conda/envs/semiseg2/lib/python3.6/site-packages/apex-0.1-py3.6-linux-x86_64.egg/apex/optimizers/init.py", line 2, in
from .fp16_optimizer import FP16_Optimizer
File "/opt/conda/envs/semiseg2/lib/python3.6/site-packages/apex-0.1-py3.6-linux-x86_64.egg/apex/optimizers/fp16_optimizer.py", line 8, in
lib.THCudaHalfTensor_normall.argtypes=[ctypes.c_void_p, ctypes.c_void_p]
File "/opt/conda/envs/semiseg2/lib/python3.6/ctypes/init.py", line 361, in getattr
func = self.getitem(name)
File "/opt/conda/envs/semiseg2/lib/python3.6/ctypes/init.py", line 366, in getitem
func = self._FuncPtr((name_or_ordinal, self))
AttributeError: /opt/conda/envs/semiseg2/bin/python: undefined symbol: THCudaHalfTensor_normall
Traceback (most recent call last):
File "train.py", line 28, in
from apex.parallel import DistributedDataParallel, SyncBatchNorm
File "/opt/conda/envs/semiseg2/lib/python3.6/site-packages/apex-0.1-py3.6-linux-x86_64.egg/apex/init.py", line 12, in
from . import optimizers
File "/opt/conda/envs/semiseg2/lib/python3.6/site-packages/apex-0.1-py3.6-linux-x86_64.egg/apex/optimizers/init.py", line 2, in
from .fp16_optimizer import FP16_Optimizer
File "/opt/conda/envs/semiseg2/lib/python3.6/site-packages/apex-0.1-py3.6-linux-x86_64.egg/apex/optimizers/fp16_optimizer.py", line 8, in
lib.THCudaHalfTensor_normall.argtypes=[ctypes.c_void_p, ctypes.c_void_p]
File "/opt/conda/envs/semiseg2/lib/python3.6/ctypes/init.py", line 361, in getattr
func = self.getitem(name)
File "/opt/conda/envs/semiseg2/lib/python3.6/ctypes/init.py", line 366, in getitem
func = self._FuncPtr((name_or_ordinal, self))
AttributeError: /opt/conda/envs/semiseg2/bin/python: undefined symbol: THCudaHalfTensor_normall
ERROR:torch.distributed.elastic.multiprocessing.api:failed (exitcode: 1) local_rank: 0 (pid: 34178) of binary: /opt/conda/envs/semiseg2/bin/python
Traceback (most recent call last):
File "/opt/conda/envs/semiseg2/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "/opt/conda/envs/semiseg2/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/opt/conda/envs/semiseg2/lib/python3.6/site-packages/torch/distributed/launch.py", line 193, in
main()
File "/opt/conda/envs/semiseg2/lib/python3.6/site-packages/torch/distributed/launch.py", line 189, in main
launch(args)
File "/opt/conda/envs/semiseg2/lib/python3.6/site-packages/torch/distributed/launch.py", line 174, in launch
run(args)
File "/opt/conda/envs/semiseg2/lib/python3.6/site-packages/torch/distributed/run.py", line 692, in run
)(*cmd_args)
File "/opt/conda/envs/semiseg2/lib/python3.6/site-packages/torch/distributed/launcher/api.py", line 116, in call
return launch_agent(self._config, self._entrypoint, list(args))
File "/opt/conda/envs/semiseg2/lib/python3.6/site-packages/torch/distributed/launcher/api.py", line 246, in launch_agent
failures=result.failures,
torch.distributed.elastic.multiprocessing.errors.ChildFailedError:

        train.py FAILED

=======================================
Root Cause:
[0]:
time: 2021-09-22_11:17:30
rank: 0 (local_rank: 0)
exitcode: 1 (pid: 34178)
error_file: <N/A>
msg: "Process failed with exitcode 1"
Other Failures:
[1]:
time: 2021-09-22_11:17:30
rank: 1 (local_rank: 1)
exitcode: 1 (pid: 34179)
error_file: <N/A>
msg: "Process failed with exitcode 1"
[2]:
time: 2021-09-22_11:17:30
rank: 2 (local_rank: 2)
exitcode: 1 (pid: 34180)
error_file: <N/A>
msg: "Process failed with exitcode 1"
[3]:
time: 2021-09-22_11:17:30
rank: 3 (local_rank: 3)
exitcode: 1 (pid: 34181)
error_file: <N/A>
msg: "Process failed with exitcode 1"

22 11:17:31 using devices 0, 1, 2, 3
_

Hi, we recommend using the same environment to make sure the results could be reproduced.
We used docker to run our experiments before and here is the docker we used: charlescxk/ssc:2.0 .
You could pull it from https://hub.docker.com/ and mount your local file system to it.

Ok, thank you very much for your reply.


Extends teams channel get command with support for teamName and channelName options

Extended teams channel get command with support to get information using teamName and channelName as options.
Closes #1887

Thank you. We will have a look into this asap

Hi @plamber
Please review

Thank you for the work. Looks good to me


Remove the nova environment file

This file was only used to get a round a bug. That bug was fixed a long
while ago so this env.d file does nothing.
PR that fixed the bug:
https://review.openstack.org/#/c/411348/
Signed-off-by: Kevin Carter<EMAIL_ADDRESS>

recheck_cit_all

Just proposed the backport upstream. https://review.openstack.org/#/c/459443/

thanks :D

Just bumped the upstream patch to include a link to this PR. This PR should get a nudge once it merges. ;)

@prometheanfire @cloudnull Upstream patch has merged.

just need master to consume it then

recheck_cit_all

looks like this needs to be removed from https://github.com/rcbops/rpc-openstack/blob/master/scripts/bootstrap-aio.yml#L126 and https://github.com/rcbops/rpc-openstack/blame/master/rpcd/etc/openstack_deploy/README.rst#L68-L76

It looks like this may need a rebase.

This has been moved to https://github.com/rcbops/rpc-openstack/pull/2375


No obvious way to renew 10 node license

Actual Behavior
My Tectonic 10 node cluster is warning that I have X days left with the current license. However, on the website there is no obvious way to generate a new license.

Jwalters,
It is not possible to extend existing licenses, as the dates are baked into the license. Please contact<EMAIL_ADDRESS>and they will be able to get you a new license.
Cheers,
Will

I have the same problem, I contacted the sales representative and he told me that the license should renew by itself. Past the XXX days my license expired and the cluster is down, it did not renew as stated by the representative. Now I have two options, create a new cluster or move completely out of coreos tectonic.
I am still waiting for the representative to get me a new license and I need to install it from the command line since cluster is down and the only access to it is through SSH.

I'm getting this notice in the console as well now.  "Cluster License Expires Soon
Your license will expire in 21 days. View the cluster settings or log in to your Tectonic account".
Neither of the recommended steps lead to a mechanism to refresh the license. We can't allow our cluster to go down, see we need to validate the renewal path in the next week to insure there isn't an interruption in service.
Any help would be much appreciated. Thanks.

Hi @rjbaucells and @JoshuaKolden, this notice is informational and shouldn't impact any running apps on the cluster, but in older Tectonic versions it may prevent you from using the Console until the license is updated. We viewed this as too restrictive so newer versions don't restrict the Console at all. kubectl shouldn't be impacted at all.
If you are both using the 10 free nodes, you can login to account.coreos.com to download a renewed license.

The question I have, and I think others have given the title of the issue is when I go to account.coreos.com  I still do not see how to acquire a new Tectonic license.  There is no renew Tectonic licenses link, and the section marked “CoreOS Tectonic” contains only two links one for documentation and a gear icon with dropdown menu with a link to “Deactivate Product…”

There is, however, a clearly labeled CoreOS license link:

So I think we’re all just looking for the "Download Tectonic License” link.
——
In preparing this detailed response I discovered that the “CoreOS” license file that is downloaded is named “tectonic-license.txt”, so it turns out to be a UI mistake. The title and link to the Tectonic license are mislabeled.

I have the same problem (Your license will expire in X days)
I have downloaded the license from account.coreos.com and pasted it in tectonic, but the expire-warning doesn't disappear.


We need a more permissive/comprehensive version parser

our current version parsing/comparison library is pretty strict and doesn't fully account for the version formats we could come across. We should probably write our own so that we can better handle all the different formats languages/libraries can throw at us

Moving this to low priority as this is needed very much so for the future, but is not going to generally increase our coverage with the current need to deliver the integration AFAIK. If this is incorrect please let me know.


fix: temp fix type convert function

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information:

Codecov Report

Merging #449 (e620329) into dev/0.5 (6fbd53c) will increase coverage by 0.17%.
The diff coverage is 0.00%.

:exclamation: Current head e620329 differs from pull request most recent head fd813e2. Consider uploading reports for the commit fd813e2 to get more accurate results

@@             Coverage Diff             @@
##           dev/0.5     #449      +/-   ##
===========================================
+ Coverage    48.93%   49.11%   +0.17%
===========================================
  Files          346      346
  Lines        18552    18483      -69
  Branches      2482     2467      -15
===========================================
- Hits          9079     9078       -1
+ Misses        9473     9405      -68

Impacted Files
Coverage Δ

...ackages/loader/src/scene-loader/temp.compatible.ts
0.00% <0.00%> (ø)

packages/draco/src/decoder.ts
0.00% <0.00%> (-0.92%)
:arrow_down:

packages/loader/src/scene-loader/Oasis.ts
0.00% <0.00%> (ø)

...ackages/loader/src/scene-loader/ResourceManager.ts
0.00% <0.00%> (ø)

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 6fbd53c...fd813e2. Read the comment docs.


facsimile -> graphic@url

Please add a trailing slash to the graphic url as we had it in AMP:
e.g.
<graphic url="https://iiif.acdh.oeaw.ac.at/aad/aad_00001/"/>
also update the <pb facs="https://iiif.acdh.oeaw.ac.at/aad/aad_00001/"/>

63d6cca
7f4aec8


Programatically Execute Command

Hello, I was looking to programmatically execute a command in Termination. Basically I'm writing a small package that allows some basic commands to be easily accessible in atom and having the output displayed in the terminal window. I've been able to open the window up programmatically but have had no luck inserting a command in the window. Any help would be greatly appreciated!

This is interresting for me as well.
I wanted to write an addition for the tool-bar to execute the docker-machine and eval commands.
I know that there is an option to make auto commands on shell startup, but I wanted to have a better control over this kind of stuff.


improve performance

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@48e4906). Click here to learn what that means.
The diff coverage is 92.15%.

@@            Coverage Diff            @@
##             master       #2   +/-   ##
=========================================
  Coverage          ?   93.82%
=========================================
  Files             ?        2
  Lines             ?       81
  Branches          ?        0
=========================================
  Hits              ?       76
  Misses            ?        3
  Partials          ?        2

Impacted Files
Coverage Δ

parser.go
100% <100%> (ø)

reader.go
79.16% <60%> (ø)

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 48e4906...e17f320. Read the comment docs.


[Task] Custom Logging

Task Description
The custom logging module (EventsLog) only contains three main loggers as of now - member events (joins/leaves), mod events (bans, kicks, etc), and eco events (later to be implemented, but plans to add for who bought what, etc). Later will be added in the future. In order to complete the EventsLog module, the following tasks needs to be completed:

[x] Implement listeners for the events
[x] Add the events config
[x] Polish up the code and test

finished


[DRAFT] feat(v1): lazy loading custom selection set POC - implementation only

Issue #

Description

General Checklist

[ ] Added new tests to cover change, if needed
[ ] Build succeeds with all target using Swift Package Manager
[ ] All unit tests pass
[ ] All integration tests pass
[ ] Security oriented best practices and standards are followed (e.g. using input sanitization, principle of least privilege, etc)
[ ] Documentation update for the change if required
[ ] PR title conforms to conventional commit style
[ ] New or updated tests include Given When Then inline code documentation and are named accordingly testThing_condition_expectation()
[ ] If breaking change, documentation/changelog update with migration instructions

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

From a few quick test runs, the custom selection set change eliminates the subscription GraphQL error described in this issue: https://github.com/aws-amplify/amplify-flutter/issues/663 . A create mutation originated from an Android device, can correctly trigger a onCreate event with correct payload delivered to the iOS App.

I'm looking forward to finalize this draft PR so we can resolve the linked issue for amplify-flutter developers and developers who develop Apps communicate between iOS and Android.

Closing for https://github.com/aws-amplify/amplify-swift/pull/2944


[Program]: Write a C# program to find the cofactor of a matrix

Description
Write a C# program to find the cofactor of a matrix
The cofactor of an element aij of a square matrix A is the determinant of the minor of A obtained by deleting the ith row and jth column of A. The cofactor of a matrix A is the matrix of cofactors of A.
Input  :
1 2 3
4 5 6
7 8 9

Output :
[[-3, 6, -3], [6, -12, 6], [-3, 6, -3]]

How to contribute

Save the solution in program/program/find-the-cofactor-of-a-matrix/program/FindTheCofactorOfAMatrix.cs file

Hi, I was looking to make my first open source contribution. I will work on Write a C# program to find the cofactor of a matrix.

Ok, thanks @harshraj8843 !

!assign


Is it possible to copy all JavaScript challenges to TypeScript?

JavaScript shows 5000+ available Kata while TypeScript - 400+.
Is it not possible to just move them somehow, since TypeScript compiles to plain JavaScript?

No, it uses different test frameworks and TypeScript uses proper modules unlike JavaScript that concatenates solution file to test file.
It's technically possible to transpile to JS and then use the tests written for JS, but we don't have any plans to do this. Codewars have lots of JS because it's the first language that was supported and it has many issues because of it. Maybe in the future, automatically generating JS version from TS version might become possible, but not vice versa.

Is it not possible to just move them somehow, since TypeScript compiles to plain JavaScript?

No, because there are advanced JS katas that, for the most part, has nothing to do with the additional capabilities of TS. Making them TS kata wouldn't add anything to them.


Character encoding issue, “â€™” showing on page instead of “ ' ”

An old article on the subject:
http://stackoverflow.com/questions/2477452/â€™-showing-on-page-instead-of

@jhsware Just letting you know that was fixed on the spot, temporary DB issue. Thank you for letting us know though :)


Add retry to openqa-cli

Actually retrying is even worse, because the jobs are actually started despite the proxy error and retry may still fail because of Apache timeout. Should better use async requests, it looks openQA should allow it


Vernemq should have working default flow for factorycube-server

Vernemq should have an up-to-date flow for sample injecting to factorycube-server.
This flow should be able to connect to factorycube-server vernemq without user configuration and inject an sample json message

Replaced by flow lib


Occasional panics occurring in the Emitter Transport layer

Describe the bug
When running the tracker there are occasional panics thrown which cause the whole application to crash.  These occur not in the Tracker itself but in the Emitter transport layer below it - however it might be possible to handle this panic within the Emitter to recover gracefully.
To Reproduce
This is not easy to reproduce but in a long running application I will see crashes consistently every 1-2 days.
Expected behavior
The tracker should not throw a panic performing its core function.
Environment (please complete the following information):

ECS Fargate on AWS
Golang 1.13.8
Container: alpine:3.7

Additional context
The stack trace:
1594737074490,fatal error: concurrent map read and map write
1594737074493,goroutine 1385994 [running]:
1594737074493,"runtime.throw(0x10170e9, 0x21)"
1594737074493,	/home/travis/.gimme/versions/go1.13.8.linux.amd64/src/runtime/panic.go:774 +0x72 fp=0xc00096ea80 sp=0xc00096ea50 pc=0x42dc02
1594737074493,"runtime.mapaccess1(0xe630a0, 0xc000396060, 0xc00096eb60, 0x19844c0)"
1594737074493,	/home/travis/.gimme/versions/go1.13.8.linux.amd64/src/runtime/map.go:411 +0x269 fp=0xc00096eac8 sp=0xc00096ea80 pc=0x40da49
1594737074493,"net/http.(*Transport).removeIdleConnLocked(0x1957300, 0xc00116e480, 0x8)"
1594737074493,	/home/travis/.gimme/versions/go1.13.8.linux.amd64/src/net/http/transport.go:983 +0x1ac fp=0xc00096eba8 sp=0xc00096eac8 pc=0x6bcc4c
1594737074493,"net/http.(*Transport).removeIdleConn(0x1957300, 0xc00116e480, 0xc000080b00)"
1594737074493,	/home/travis/.gimme/versions/go1.13.8.linux.amd64/src/net/http/transport.go:973 +0x80 fp=0xc00096ec08 sp=0xc00096eba8 pc=0x6bca50
1594737074493,"net/http.(*persistConn).readLoop.func1(0xc00116e480, 0xc00096ed88)"
1594737074493,	/home/travis/.gimme/versions/go1.13.8.linux.amd64/src/net/http/transport.go:1880 +0x58 fp=0xc00096ec30 sp=0xc00096ec08 pc=0x6ca168
1594737074493,net/http.(*persistConn).readLoop(0xc00116e480)
1594737074493,	/home/travis/.gimme/versions/go1.13.8.linux.amd64/src/net/http/transport.go:1917 +0x1148 fp=0xc00096efd8 sp=0xc00096ec30 pc=0x6c37b8
1594737074493,runtime.goexit()
1594737074493,	/home/travis/.gimme/versions/go1.13.8.linux.amd64/src/runtime/asm_amd64.s:1357 +0x1 fp=0xc00096efe0 sp=0xc00096efd8 pc=0x45b151
1594737074493,created by net/http.(*Transport).dialConn
1594737074493,	/home/travis/.gimme/versions/go1.13.8.linux.amd64/src/net/http/transport.go:1580 +0xb0d

Isolating this down it seems like something in this function is causing the issue: https://github.com/snowplow/snowplow-golang-tracker/blob/master/tracker/emitter.go#L100-L115
Going to see if the issue can be fixed by using a custom transport instead of the default one.

Also we are editing the global transport object in this way which feels like something we should be avoiding - it seems likely that providing a custom transport rather than using the default transport is almost certainly the way to clean this issue up and stop it from occurring.

The issue is line 109 which dereferences the pointer and therefore copies the mutex value.
https://github.com/snowplow/snowplow-golang-tracker/blob/88ca5cf2930840e8c7f0c65efbaef326de5fffd2/tracker/emitter.go#L109
I think it would be fixed by
defaultTransport := http.DefaultTransport.(*http.Transport).Clone()

A workaround is to pass a custom http client to InitEmitter().


Adding basic health check endpoint

The endpoint /status can be used to determine if puppetboard is running or not.
Reason for needing an endpoint like this is because if the puppetdb has no
data yet (due to a fresh install for example), it will return a 404 on all pages.
This will throw off health checks for example docker or the AWS ALB.
The health check endpoint can later be expanded by puppetdb health as soon
as this functionality has been merged in the pypuppetdb module.

This seems simple and sane to me; thanks for the contribution.


Consider renaming deployment-exposed-with-service

This prototype is super long.  Perhaps deployed-service or deploy-and-service or simple-service.

two cents: I like deployed-service because it keeps the element of "Deployment" in there. can wait for consensus though

This is meant to be handled in #90.

My vote is for deployed-service. It neatly captures intent.

Not sure that this is the same as #90.  That issue is about the naming scheme (reverse DNS vs. repo/name@version).  This is about the specific name of this prototype.
Reopening.

@jbeda, there is #154, taking care of changing the name in the prototype/systemPrototypes.go file, as well as the documentation that mentions the prototype by name.

Yes, confirming it works ...
➜  foo git:(init-namespace) ✗ ../ks prototype use deployed-service guestbook-ui \
--name guestbook-ui \
--image alpinejay/dns-single-redis-guestbook:1.0 \
--type LoadBalancer
INFO  Writing component at 'components/guestbook-ui'


qtile should not use LD_LIBRARY_PATH

[avn@bulldozer:pts/18]/home/avn/invoicing% zathura example.pdf
** (zathura:17204): WARNING **: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
/nix/store/75b1vkjfia3x6qwn7j592ypg33xj1vjh-zathura-core-0.3.3/bin/zathura: symbol lookup error: /nix/store/rwcwfdghyxxl9jzznly23y29iaz438i3-gtk+3-3.18.4/lib/libgtk-3.so.0: undefined symbol: g_param_spec_get_name_quark

Looks like libgtk3 miss 1 symbol from glib and 6 from pango
[avn@bulldozer:pts/18]~% ldd -r /nix/store/rwcwfdghyxxl9jzznly23y29iaz438i3-gtk+3-3.18.4/lib/libgtk-3.so.0.1800.4                                                                            ~
	linux-vdso.so.1 (0x00007ffdbd9fe000)
	libgdk-3.so.0 => /nix/store/rwcwfdghyxxl9jzznly23y29iaz438i3-gtk+3-3.18.4/lib/libgdk-3.so.0 (0x00007fc77918c000)
	libXinerama.so.1 => /nix/store/56ps0jrhf0q7d7mdhgiwqk2pggf41dzn-libXinerama-1.1.3/lib/libXinerama.so.1 (0x00007fc778f84000)
	libXrandr.so.2 => /nix/store/9nmm2i2rlhl4x6rmzv634zy9c2g53ssa-libXrandr-1.5.0/lib/libXrandr.so.2 (0x00007fc778d74000)
	libXcursor.so.1 => /nix/store/ggwf1p2dkiab59v7j9sdrns7c5yrh4hq-libXcursor-1.1.14/lib/libXcursor.so.1 (0x00007fc778b64000)
	libpangocairo-1.0.so.0 => /nix/store/1hgr2q3mfixs10kj9yzqyyrqbyzjkm29-pango-1.36.8/lib/libpangocairo-1.0.so.0 (0x00007fc778954000)
	libXi.so.6 => /nix/store/x75lb2x9anzka6qwn8f0zi8bc33djnzs-libXi-1.7.5/lib/libXi.so.6 (0x00007fc778744000)
	libXcomposite.so.1 => /nix/store/qw1a6xzkb35afsg317dm209iwvk9dj5v-libXcomposite-0.4.4/lib/libXcomposite.so.1 (0x00007fc77853c000)
	libcairo-gobject.so.2 => /nix/store/fl7srm0d8z5zdm9gp2diqr67rkfsxd36-cairo-1.14.2/lib/libcairo-gobject.so.2 (0x00007fc778334000)
	libcairo.so.2 => /nix/store/fl7srm0d8z5zdm9gp2diqr67rkfsxd36-cairo-1.14.2/lib/libcairo.so.2 (0x00007fc77800c000)
	libpixman-1.so.0 => /nix/store/100rzjkjc3293h4pbwcqkc58f49va3mz-pixman-0.32.8/lib/libpixman-1.so.0 (0x00007fc777d5c000)
	libEGL.so.1 => /run/opengl-driver/lib/libEGL.so.1 (0x00007fc777b2c000)
	libgbm.so.1 => /run/opengl-driver/lib/libgbm.so.1 (0x00007fc77791c000)
	libwayland-server.so.0 => /nix/store/1964rliyxykqpg57f5gvlg6g6klm5lvq-wayland-1.9.0/lib/libwayland-server.so.0 (0x00007fc777704000)
	libxcb-shm.so.0 => /nix/store/r3xv21sfbky2pi0x8gypidal63m057f7-libxcb-1.11.1/lib/libxcb-shm.so.0 (0x00007fc7774fc000)
	libXrender.so.1 => /nix/store/daj5y488f74q24jgxr4i2gj1ri58970a-libXrender-0.9.9/lib/libXrender.so.1 (0x00007fc7772ec000)
	libGL.so.1 => /run/opengl-driver/lib/libGL.so.1 (0x00007fc77705c000)
	libglapi.so.0 => /run/opengl-driver/lib/libglapi.so.0 (0x00007fc776e2c000)
	libXdamage.so.1 => /nix/store/20x2pzahzk7nz9lndvzhb37cypvzgf3n-libXdamage-1.1.4/lib/libXdamage.so.1 (0x00007fc776c24000)
	libXfixes.so.3 => /nix/store/4jpalpbkxc6kfz6filfcsq9x0jqqdxmp-libXfixes-5.0.1/lib/libXfixes.so.3 (0x00007fc776a1c000)
	libX11-xcb.so.1 => /nix/store/frg4x2wa979bvw6ahac5wvi0bx3kf53w-libX11-1.6.3/lib/libX11-xcb.so.1 (0x00007fc776814000)
	libxcb-glx.so.0 => /nix/store/r3xv21sfbky2pi0x8gypidal63m057f7-libxcb-1.11.1/lib/libxcb-glx.so.0 (0x00007fc7765fc000)
	libxcb-dri2.so.0 => /nix/store/r3xv21sfbky2pi0x8gypidal63m057f7-libxcb-1.11.1/lib/libxcb-dri2.so.0 (0x00007fc7763f4000)
	libxcb-dri3.so.0 => /nix/store/r3xv21sfbky2pi0x8gypidal63m057f7-libxcb-1.11.1/lib/libxcb-dri3.so.0 (0x00007fc7761ec000)
	libxcb-present.so.0 => /nix/store/r3xv21sfbky2pi0x8gypidal63m057f7-libxcb-1.11.1/lib/libxcb-present.so.0 (0x00007fc775fe4000)
	libxcb-randr.so.0 => /nix/store/r3xv21sfbky2pi0x8gypidal63m057f7-libxcb-1.11.1/lib/libxcb-randr.so.0 (0x00007fc775dd4000)
	libxcb-xfixes.so.0 => /nix/store/r3xv21sfbky2pi0x8gypidal63m057f7-libxcb-1.11.1/lib/libxcb-xfixes.so.0 (0x00007fc775bcc000)
	libxcb-render.so.0 => /nix/store/r3xv21sfbky2pi0x8gypidal63m057f7-libxcb-1.11.1/lib/libxcb-render.so.0 (0x00007fc7759bc000)
	libxcb-shape.so.0 => /nix/store/r3xv21sfbky2pi0x8gypidal63m057f7-libxcb-1.11.1/lib/libxcb-shape.so.0 (0x00007fc7757b4000)
	libxcb-sync.so.1 => /nix/store/r3xv21sfbky2pi0x8gypidal63m057f7-libxcb-1.11.1/lib/libxcb-sync.so.1 (0x00007fc7755ac000)
	libxshmfence.so.1 => /nix/store/ba4ma29s4dvvs6jas07nf9yjgfl9y5ig-libxshmfence-1.2/lib/libxshmfence.so.1 (0x00007fc7753a4000)
	libXxf86vm.so.1 => /nix/store/asc1fqbb5qqh8h1xyziz4gdp4l8yydbx-libXxf86vm-1.1.4/lib/libXxf86vm.so.1 (0x00007fc77519c000)
	libXext.so.6 => /nix/store/nwa59yl3sz6ldrhg94g45pf9rn0j8nwr-libXext-1.3.3/lib/libXext.so.6 (0x00007fc774f84000)
	libxcb.so.1 => /nix/store/r3xv21sfbky2pi0x8gypidal63m057f7-libxcb-1.11.1/lib/libxcb.so.1 (0x00007fc774d64000)
	libXau.so.6 => /nix/store/r3zpj4sa3bn8jxr2zk8k2ax9y7mrkhfj-libXau-1.0.8/lib/libXau.so.6 (0x00007fc774b5c000)
	libXdmcp.so.6 => /nix/store/n3ybgbqy68pr7810j95xq79dmj2687cb-libXdmcp-1.1.2/lib/libXdmcp.so.6 (0x00007fc774954000)
	libdrm.so.2 => /nix/store/z9l0w0dpqflmfkyjx6wyi3718xh1s68q-libdrm-2.4.65/lib/libdrm.so.2 (0x00007fc774744000)
	libgdk_pixbuf-2.0.so.0 => /nix/store/yxdzfjqmc63gxq1kwk6zg2h2xhscmkrc-gdk-pixbuf-2.32.1/lib/libgdk_pixbuf-2.0.so.0 (0x00007fc77451c000)
	libatk-bridge-2.0.so.0 => /nix/store/fhrwdhjbj5cdzyzg997jippkbh76xvrv-at-spi2-atk-2.18.0/lib/libatk-bridge-2.0.so.0 (0x00007fc7742ec000)
	libatk-1.0.so.0 => /nix/store/ggdlrcjk4q4h1vf0vvdlrpv4blhj1k2k-atk-2.18.0/lib/libatk-1.0.so.0 (0x00007fc7740c4000)
	libatspi.so.0 => /nix/store/qcqd6fhp20rb4hdipjgzcyrli95i9qlk-at-spi2-core-2.18.0/lib/libatspi.so.0 (0x00007fc773e94000)
	libSM.so.6 => /nix/store/v8vvnzib0ijfdjxx1i83qixh5arxlp3j-libSM-1.2.2/lib/libSM.so.6 (0x00007fc773c8c000)
	libICE.so.6 => /nix/store/smnk65pdkc99imchbfadpfb4f0j6gbv6-libICE-1.0.9/lib/libICE.so.6 (0x00007fc773a6c000)
	libX11.so.6 => /nix/store/frg4x2wa979bvw6ahac5wvi0bx3kf53w-libX11-1.6.3/lib/libX11.so.6 (0x00007fc77372c000)
	libdbus-1.so.3 => /nix/store/0gwqsj2xbs58dia6aklhbaqz6dzf3c98-dbus-libs-1.8.20/lib/libdbus-1.so.3 (0x00007fc7734e4000)
	libxkbcommon.so.0 => /nix/store/ibm01l5fzncap0ablkvxgjmgx68sq49q-libxkbcommon-0.5.0/lib/libxkbcommon.so.0 (0x00007fc7732a4000)
	libwayland-cursor.so.0 => /nix/store/1964rliyxykqpg57f5gvlg6g6klm5lvq-wayland-1.9.0/lib/libwayland-cursor.so.0 (0x00007fc77309c000)
	libwayland-egl.so.1 => /run/opengl-driver/lib/libwayland-egl.so.1 (0x00007fc772e94000)
	libwayland-client.so.0 => /nix/store/1964rliyxykqpg57f5gvlg6g6klm5lvq-wayland-1.9.0/lib/libwayland-client.so.0 (0x00007fc772c84000)
	librt.so.1 => /nix/store/y8scgsh8warhiy3pl39mqxyxphybcy7p-glibc-2.21/lib/librt.so.1 (0x00007fc772a7c000)
	libepoxy.so.0 => /nix/store/0hl15p8v2lz3cpqwkry910cm6w0lzh9q-epoxy-1.3.1/lib/libepoxy.so.0 (0x00007fc772784000)
	libpangoft2-1.0.so.0 => /nix/store/1hgr2q3mfixs10kj9yzqyyrqbyzjkm29-pango-1.36.8/lib/libpangoft2-1.0.so.0 (0x00007fc77256c000)
	libharfbuzz.so.0 => /nix/store/im0m6nyg2vmpw3czghymhwc9h4xx1m1i-harfbuzz-1.0.6/lib/libharfbuzz.so.0 (0x00007fc772304000)
	libgraphite2.so.3 => /nix/store/n3c5392g317zik4bb7fj6lj0af4xb01g-graphite2-1.2.4/lib/libgraphite2.so.3 (0x00007fc7720dc000)
	libpango-1.0.so.0 => /nix/store/1hgr2q3mfixs10kj9yzqyyrqbyzjkm29-pango-1.36.8/lib/libpango-1.0.so.0 (0x00007fc771e8c000)
	libgthread-2.0.so.0 => /nix/store/zy7xi64lsmnx0i0d0h8qgqigs4m85crc-glib-2.44.1/lib/libgthread-2.0.so.0 (0x00007fc771c84000)
	libfontconfig.so.1 => /nix/store/2msjjbmmrcx4cjqr76v31l8kvkrqkcq9-fontconfig-2.11.1/lib/libfontconfig.so.1 (0x00007fc771a44000)
	libexpat.so.1 => /nix/store/8hvsmq24ap9mnvx3x96gmq1qm86kyx8s-expat-2.1.0/lib/libexpat.so.1 (0x00007fc771814000)
	libfreetype.so.6 => /nix/store/v42khwmgdddlyqwmh6an87pvk9x4h8bw-freetype-2.5.4/lib/libfreetype.so.6 (0x00007fc77150c000)
	libbz2.so.1.0 => /nix/store/0iv2ykxshmq5gwfm8qbc4n7649algn3h-bzip2-1.0.6/lib/libbz2.so.1.0 (0x00007fc7712fc000)
	libpng16.so.16 => /nix/store/y7qsx1scsxxh9yvc1yjx9dx7vs13rljq-libpng-apng-1.6.18/lib/libpng16.so.16 (0x00007fc7710c4000)
	libgio-2.0.so.0 => /nix/store/zy7xi64lsmnx0i0d0h8qgqigs4m85crc-glib-2.44.1/lib/libgio-2.0.so.0 (0x00007fc770d44000)
	libgmodule-2.0.so.0 => /nix/store/zy7xi64lsmnx0i0d0h8qgqigs4m85crc-glib-2.44.1/lib/libgmodule-2.0.so.0 (0x00007fc770b3c000)
	libdl.so.2 => /nix/store/y8scgsh8warhiy3pl39mqxyxphybcy7p-glibc-2.21/lib/libdl.so.2 (0x00007fc770934000)
	libz.so.1 => /nix/store/s6zky9ysv3qpwz53xvza43n8vzijyafn-zlib-1.2.8/lib/libz.so.1 (0x00007fc77071c000)
	libresolv.so.2 => /nix/store/y8scgsh8warhiy3pl39mqxyxphybcy7p-glibc-2.21/lib/libresolv.so.2 (0x00007fc770504000)
	libgobject-2.0.so.0 => /nix/store/zy7xi64lsmnx0i0d0h8qgqigs4m85crc-glib-2.44.1/lib/libgobject-2.0.so.0 (0x00007fc7702ac000)
	libffi.so.6 => /nix/store/yp3n0vk0wggj1fm1bwagwssih9rarq1c-libffi-3.2.1/lib/../lib64/libffi.so.6 (0x00007fc77009c000)
	libglib-2.0.so.0 => /nix/store/zy7xi64lsmnx0i0d0h8qgqigs4m85crc-glib-2.44.1/lib/libglib-2.0.so.0 (0x00007fc76fd64000)
	libpthread.so.0 => /nix/store/y8scgsh8warhiy3pl39mqxyxphybcy7p-glibc-2.21/lib/libpthread.so.0 (0x00007fc76fb44000)
	libm.so.6 => /nix/store/y8scgsh8warhiy3pl39mqxyxphybcy7p-glibc-2.21/lib/libm.so.6 (0x00007fc76f83c000)
	libc.so.6 => /nix/store/y8scgsh8warhiy3pl39mqxyxphybcy7p-glibc-2.21/lib/libc.so.6 (0x00007fc76f49c000)
	/nix/store/y8scgsh8warhiy3pl39mqxyxphybcy7p-glibc-2.21/lib64/ld-linux-x86-64.so.2 (0x00005646621e1000)
	libuuid.so.1 => /nix/store/fr25hj7nh6hiwayzj7npwk2bb2h7zgr3-util-linux-2.27.1/lib/libuuid.so.1 (0x00007fc76f294000)
undefined symbol: pango_attr_foreground_alpha_new	(/nix/store/rwcwfdghyxxl9jzznly23y29iaz438i3-gtk+3-3.18.4/lib/libgtk-3.so.0.1800.4)
undefined symbol: g_param_spec_get_name_quark	(/nix/store/rwcwfdghyxxl9jzznly23y29iaz438i3-gtk+3-3.18.4/lib/libgtk-3.so.0.1800.4)
undefined symbol: pango_fc_font_map_config_changed	(/nix/store/rwcwfdghyxxl9jzznly23y29iaz438i3-gtk+3-3.18.4/lib/libgtk-3.so.0.1800.4)
undefined symbol: pango_renderer_set_alpha	(/nix/store/rwcwfdghyxxl9jzznly23y29iaz438i3-gtk+3-3.18.4/lib/libgtk-3.so.0.1800.4)
undefined symbol: pango_renderer_get_alpha	(/nix/store/rwcwfdghyxxl9jzznly23y29iaz438i3-gtk+3-3.18.4/lib/libgtk-3.so.0.1800.4)
undefined symbol: pango_attr_font_features_new	(/nix/store/rwcwfdghyxxl9jzznly23y29iaz438i3-gtk+3-3.18.4/lib/libgtk-3.so.0.1800.4)
undefined symbol: pango_attr_background_alpha_new	(/nix/store/rwcwfdghyxxl9jzznly23y29iaz438i3-gtk+3-3.18.4/lib/libgtk-3.so.0.1800.4)

That's weird. What about nix-store -qR /nix/store/75b1vkjfia3x6qwn7j592ypg33xj1vjh-zathura-core-0.3.3 | grep gtk ? Either you have an LD_LIBRARY_PATH somewhere, or zathura uses dynamic loading and the gtk version used for it is wrong.

[avn@bulldozer:pts/18]~% nix-store -qR /nix/store/75b1vkjfia3x6qwn7j592ypg33xj1vjh-zathura-core-0.3.3 | grep gtk                                                                             ~
/nix/store/rwcwfdghyxxl9jzznly23y29iaz438i3-gtk+3-3.18.4

Ok so it looks like zathura has been compiled with gtk 3.18 and pango 3.16, but gtk 3.18 closure has pango 3.18 instead. So, again, it must be an `LD_LIBRARY_PATH¿ somewhere.

As per IRC, this is an LD_LIBRARY_PATH problem somewhere. If possible, please try to understand where it's coming from, so we may try to patch it. Closing this, feel free to open another one if you understand which nixos module is mining LD_LIBRARY_PATH.

qtile (windowmanager) wrapper was

Has that been fixed? It isn't nice if a WM passes $LD_LIBRARY_PATH into env of all executables under it.

@vcunat I think @avnik was working on this already, but this issue is not about zathura being broken anymore.

Reopening with different title perhaps...

What's the simplest way to set LD_LIBRARY_PATH for buildPhase only?

Just define it within the attrset passed to stdenv.mkDerivation.

@kamilchm  I discuss possible package improvements in irc, I sure, that these part of conversation may be interesting for you:

11:34 < Lethalman> avn, so you have to understand where that LD_LIBRARY_PATH comes from, it might be a nixos module, in which case we may need to fix it to avoid using LD_LIBRARY_PATH
11:35 < avn> Lethalman: qtile (window-manager) wrapper export them
11:36 < Lethalman> I see
11:37 < Lethalman> avn, btw LD_LIBRARY_PATH= zathura should work
11:37 < Lethalman> avn, and someone better fix the qtile derivation to avoid LD_LIBRARY_PATH :)
11:40 < avn> Lethalman: thinking about how to fix... It accessing
libxcb and pango via cffi
11:44 < avn> Lethalman: https://github.com/NixOS/nixpkgs/blob/mast
er/pkgs/applications/window-managers/qtile/default.nix#L31
11:44 < Lethalman> avn, not that, the qtile code...
11:46 < avn> Lethalman: https://github.com/qtile/qtile/blob/develo
p/libqtile/pangocffi.py#L61 loading itself
11:47 < Lethalman> avn, perfect, replace that string with an absol
ute path :)
11:48 < Lethalman> avn, avn, gobject = ffi.dlopen('${glib}/lib/lib
gobject-2.0.so.0')
11:51 < avn> Lethalman: btw, if you start look to qtile package --
 may be you hint me any idea about improving this: https://github.
com/NixOS/nixpkgs/blob/master/pkgs/applications/window-managers/qt
ile/restart_executable.patch
11:55 < avn> Lethalman: I thinking about  put  export QTILE_WRAPPER=$0 in wrapper, and use env["QTILE_WRAPPER"] for restart, so it should "catch" cases when /run/current.../bin/qtile updated, and I want to restart to new one
11:56 < Lethalman> avn, ah, that's a good idea yes

@kamilchm any toughts about absolute paths, and restart modification?
(I can do this).
Another thing, which I don't know how to improve -- PATH and PYTHONPATH also have some stuff, related only to this qtile derivation (come from wrappers), but they taint any child process environment (like xterms)

About PATH and PYTHONPATH, they should probably be unset when child processes are spawned by qtile.

PYTHONPATH can be just unset, but not PATH
btw they can be unset in first lines on unwrapped bin/qtile, as I know mangling os.environ["PYTHONPATH"] not affect current interpreter, only child processes

@avnik :+1: for absolute paths, I was thinking about it yesterday but I don't have time to do it now.
Restart modification looks good too.
I'll be happy with your patch.

Note that unsetting $LD_LIBRARY_PATH will also cause problems to some programs.

@vcunat I don't think anybody wanted to unset LD_LIBRARY_PATH. Of course also for PATH and PYTHONPATH, it's probably best to store somewhere the original env and reset in qtile.

I saw the suggestion to run LD_LIBRARY_PATH= zathura (above), so I just wanted to warn it won't always work (well).

What is the best way to test it? I'll try to find some time to fix it.

Fixed in #11386

LD_LIBRARY_PATH now just not touched in wrapper (I change all paths to absolute),  PATH and PYTHONPATH saved in wrapper, and restored in python code


Oficial documentation

The Readme.md is surely a good intro to the library, but I believe a good documentation is in need.
Also, it would be awesome if docstrings are done in the process.
Surely I can help!

No, since then, I couldn't found it. The Docs are inline with the code. You should have some sort of intellisense from your ide when you hover on something (vs code has it).
If someone finds documentation, please comment down below!

If anyone still wants to contribute to docs then is appreciated, I can review & merge.

Thanks! Have a great day


Tests

This branch deals with everything being done to get this django app ready for a github release. So it includes documentation, a requirements file, CI integration, etc., but the really important additions are the tests to make sure we know what we need to do to make this work as expected, and to make sure it works with Django 1.8 and Python 2.7.

@ldko, @damonkelley, I'm kind of stuck. Do you guys have any suggestions on extra tests, or changes to the tests I've already added?

@ldko, @damonkelley, I'm kind of stuck. Do you guys have any suggestions on extra tests, or changes to the tests I've already added?

@ldko, @damonkelley, this PR is ready for review.

Is requirements.txt meant to be the "dev requirements"? If so, we should add edtf-validate

Yep, you are correct. Adding edtf-validate.

:+1:

:+1:

errr actually there is some pep8 stuff in multiple files that should be cleaned up before merging. Then merge! Thanks!


fix: Fix for incorrect increment of the attempts number

Pull Request
Description
Fix for the incorrect increment of attempts number in case of some fail during webhook processing.
Type of change
Please delete options that are not relevant.

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Code cleanup/refactoring
[ ] Documentation update
[ ] This change requires a documentation update
[ ] CI system update
[ ] Test Coverage update

Testing
Test Configuration:

Java: v17
LPVS Release: v1.4.1

Checklist:

[X] My code follows the style guidelines of this project
[X] My code meets the required code coverage for lines (90% and above)
[X] My code meets the required code coverage for branches (80% and above)
[X] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 90.76%. Comparing base (dfb2b4d) to head (8c530ac).
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##               main     #442   +/-   ##
=========================================
  Coverage     90.76%   90.76%
  Complexity      489      489
=========================================
  Files            47       47
  Lines          1732     1732
  Branches        207      207
=========================================
  Hits           1572     1572
  Misses           97       97
  Partials         63       63

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


LWP Improvements

Your changes have been integrated into master and version 0.09 should hit cpan by tomorrow.  Sorry it took so long and thanks for posting improvements.


Upgrade pulumi-terraform-bridge to v3.83.0

This PR was generated via $ upgrade-provider pulumiverse/pulumi-grafana --kind=bridge --target-bridge-version=latest.

Updating Java Gen version from 0.10.0 to 0.12.0.
Upgrading pulumi-terraform-bridge from v3.80.0 to v3.83.0.
Upgrading pulumi-terraform-bridge/pf from v0.33.0 to v0.36.0.

Superseded by #166


Fix Docs page responsive on mobile

Context
Docs page did not make the responsive correctly.
Solution
Add minChildWith prop used on Chakra SimpleGrid component to make the grid responsive and adjust automatically without passing columns
More info: https://chakra-ui.com/docs/components/simple-grid/usage#auto-responsive-grid
Demo

Muchas gracias 🚀🚀


Update README.md - add team publication for VM shape change

Migrate a Compute shape from VM.Standard2.x to flexible shape on OCI. Created a document and added the link to Compute Hardware page.

Approved

Approved


"@" symbol is converted to "<blade"  in blade.php files.

Input
The code looked like this before beautification:
<script type="text/javascript">
     document.write( "@" );
</script>

Expected Output
The code should have looked like this after beautification:
<script type="text/javascript">
     document.write( "@" );
</script>

Actual Output
The  code actually looked like this after beautification:
<script type="text/javascript">
    document.write("<blade " / > );
</script>

Steps to Reproduce

Use ATOM editor
create file with above content
save as test.blade.php
run beautify through atom-beautify:beautify-language-blade

Environment
OS: Ubuntu 18.04
Using Beautify in Atom Editor
Settings
I did not specify any settings anywhere

@iwasherefirst2
Did you try this on https://beautifier.io ?
I can think of no code in this library that would do what you have described.  It is likely that this is cause by some other part of Atom and/or that plugin.

@bitwiseman it seems that it was not related to the language-blade package. I can reproduce the issue even with all other packages beeing disabled. One has to call the command  atom-beautify:beautify-language-blade from console ( I adjusted the reproduce-steps from original post).
It seems that calling Beautify through the menu does not call atom-beautify:beautify-language-blade by default, but it did when I enabled the language-blade package. That why I thought the package is causing it.

If this isn't reproducible on  https://beautifier.io it is unlikely to be caused by this library.  You'll need to talk to the author of that plugin.  Sorry.

@bitwiseman the error appears even if all other plugins are disabled. But I just noticed that there is another repo for the atom package of beautify: https://github.com/Glavin001/atom-beautify
I will create an issue on atom-beautify repo


[flink][cdc] Add support for retry cnt instead of busy wait and additional support to skip corrupt records in cdc writer

Purpose
This change adds support for retry count and skipping corrupt records instead of assuming a schema change has happened and waiting indefinitely on schema change. This change will cause the Flink cdc job to fail loudly due to a corrupt message (alternatively users have an option to use config option to log and skip such messages) instead of waiting indefinitely on schema change which might not have happened. For more details check the linked issue.

Linked issue: close #4239

Tests

API and Format

Documentation

Maybe we can add a few unit tests and some docs for the new options?

@JingsongLi could you please help review this? We are currently running this patch internally for Yelp as we cannot afford to block all ingestion based on one "corrupt" message. Corrupt messages entering our stream is rare but inevitable (e.g. older schemas that are not backwards compatible) and it is better for us to log and skip them (or even fail the app) rather than block.

@JingsongLi can you assign someone to look at the PR? I need your thoughts and opinions on this PR before I resolve other comments.

Thanks for contribution! I have rename some options, please check: #4756


Fix NODEV errors on Thinkpad when parsing battery status

On thinkpads, reading power_supply class charge_control_end_threshold returns no such device error, which results in battery metrics not being exported.
Fixes: https://github.com/prometheus/node_exporter/issues/3019

LGTM, although, it seems to be only some thinkpads. My X1 Carbon seems to work OK for this file.


Spring Boot Integration

Hey,
I just wanted to live this note. Since I am a very happy ModelMapper user I have decided to build a seamless integration with Spring Boot: https://github.com/jmnarloch/spring-boot-starter-modelmapper. It allows it to simply drop the extension to Spring Boot app classpath and just inject ModelMapper to any Spring bean.

Very nice Jakob! I tweeted a link to your blog post.


mesh2sdf errors

Hi,
I'm trying to build the sdf-net portion of the repository, but I'm having issues with the mesh2sdf library. I'm not entirely sure what library this corresponds to because it's not in the requirements.txt, but I've guessed that it must be the mesh-to-sdf library. I've tried this and changing the imports to match, but the build still breaks in compute_sdf.py. which uses mesh2sdf_gpu and doesn't exist in mesh-to-sdf.
So I'm curious what library I'm supposed to use for this or if this is just legacy code that needs to be reconfigured. I've had other dependency issues, but so far, those have been pretty easy to resolve. Happy to help contribute for this, but want to make sure I'm not making a glaring mistake.
Thanks.

Hi @kingcodefish,
Our codebase relies on two custom CUDA kernels which can be found in sdf-net/lib/extensions, where mesh2sdf is one of them. You can refer to our read-me file for install instructions. What other dependency issues were you having?

@joeylitalien Whoops, my bad. Somehow I managed to skip over that part of the setup. I've now built the extensions and have gotten the neural network to train on the armadillo example. However, when I run the following command to export the .npz file:
python app/sdf_renderer.py \
    --net OctreeSDF \
    --num-lods 5 \
    --pretrained _results/models/armadillo.pth \
    --render-res 1280 720 \
    --shading-mode matcap \
    --lod 4
    --export armadillo.npz

I get the following error:
Total number of parameters: 10146213
Traceback (most recent call last):
  File "app/sdf_renderer.py, line 106, in <module>
    net = SOL_NGLOD(net)
  File "~/Documents/nglod/sdf-net/lib/models/SOL_NGLOD.py", line 50, in __init__
    self.vs = voxel_sparsify(2000000, net, self.lod, sol=False)
  File "~/Documents/nglod/sdf-net/lib/renderutils.py", line 63, in voxel_sparsify
    surface = sample_surface(n, net, sol=sol, device=device)[:n]
  File "~/Documents/nglod/sdf-net/lib/renderutils.py", line 33, in sample_surface
    tracer = SphereTracer(device, sol=sol)
TypeError: __init__() got an unexpected keyword argument 'sol'

A lot of this is affected by some recent refactors we've had which includes deprecating some of the exporting capabilities to opt for a Python-based interactive renderer. Said Python-based renderer isn't available yet but will be soon (hopefully over the weekend)!

@joeylitalien Whoops, my bad. Somehow I managed to skip over that part of the setup. I've now built the extensions and have gotten the neural network to train on the armadillo example. However, when I run the following command to export the .npz file:
python app/sdf_renderer.py \
    --net OctreeSDF \
    --num-lods 5 \
    --pretrained _results/models/armadillo.pth \
    --render-res 1280 720 \
    --shading-mode matcap \
    --lod 4
    --export armadillo.npz

I get the following error:
Total number of parameters: 10146213
Traceback (most recent call last):
  File "app/sdf_renderer.py, line 106, in <module>
    net = SOL_NGLOD(net)
  File "~/Documents/nglod/sdf-net/lib/models/SOL_NGLOD.py", line 50, in __init__
    self.vs = voxel_sparsify(2000000, net, self.lod, sol=False)
  File "~/Documents/nglod/sdf-net/lib/renderutils.py", line 63, in voxel_sparsify
    surface = sample_surface(n, net, sol=sol, device=device)[:n]
  File "~/Documents/nglod/sdf-net/lib/renderutils.py", line 33, in sample_surface
    tracer = SphereTracer(device, sol=sol)
TypeError: __init__() got an unexpected keyword argument 'sol'

Hi @kingcodefish  I'm just wondering have you solved the TypeError: __init__() got an unexpected keyword argument 'sol' issue? Thank you!

@joeylitalien Whoops, my bad. Somehow I managed to skip over that part of the setup. I've now built the extensions and have gotten the neural network to train on the armadillo example. However, when I run the following command to export the .npz file:
python app/sdf_renderer.py \
    --net OctreeSDF \
    --num-lods 5 \
    --pretrained _results/models/armadillo.pth \
    --render-res 1280 720 \
    --shading-mode matcap \
    --lod 4
    --export armadillo.npz

I get the following error:
Total number of parameters: 10146213
Traceback (most recent call last):
  File "app/sdf_renderer.py, line 106, in <module>
    net = SOL_NGLOD(net)
  File "~/Documents/nglod/sdf-net/lib/models/SOL_NGLOD.py", line 50, in __init__
    self.vs = voxel_sparsify(2000000, net, self.lod, sol=False)
  File "~/Documents/nglod/sdf-net/lib/renderutils.py", line 63, in voxel_sparsify
    surface = sample_surface(n, net, sol=sol, device=device)[:n]
  File "~/Documents/nglod/sdf-net/lib/renderutils.py", line 33, in sample_surface
    tracer = SphereTracer(device, sol=sol)
TypeError: __init__() got an unexpected keyword argument 'sol'

how did you solve this problem( TypeError: init() got an unexpected keyword argument 'sol') in the end？Thank you!


Trouble Running "Hello, KAN!" Code: SyntaxError in MultKAN.py

Good morning,
In order to run the "Hello, KAN!" code (https://kindxiaoming.github.io/pykan/intro.html#hello-kan), is it sufficient to execute the following commands?
conda create --name pykan-env python=3.9.7
conda activate pykan-env
pip install pykan

and install the packages from requirements.txt?
I am asking because when I write:
from kan import *
# create a KAN: 2D inputs, 1D output, and 5 hidden neurons. cubic spline (k=3), 5 grid intervals (grid=5).
model = KAN(width=[2,5,1], grid=5, k=3, seed=0)

I get an error message:
File ~\anaconda3\envs\pykan-env\lib\site-packages\kan\MultKAN.py:806
<<<<<<< HEAD
^
SyntaxError: invalid syntax

It's a just conflict, just locate multKAN.py file in your environment and open using VS and accept the both changes option inside the file

@edkamesh , first of all, thank you very much for the response!
Do you know if I can find a similar solution through Spyder? VS was giving me various problems on another project, so I have replaced it with Spyder.

Open and check if you can see those options visible else do it manually by removing the conflict markers and unwanted changes

@edkamesh , I 'll try it. Thanks a lot!

Update me if you can solve it or not ?👍🏻

Sorry, I’m new to GitHub.

I am using google colab due to various reasons. How can I solve this with google colab?

Try cloning the package into gdrive and open the multKAN.py in colab and edit the changes there. So by this way you can resolve the issue right now.
I tried for searching other fixes but couldn't find !!
Hope it works

just solve the conflict and update to version 0.2.1, please let me know if the new version works!

I tried it and no error occurred. Thanks for the update.


[global-load-balancer-operator] maintenance

Type of repository request
maintenance
Requested name for the repository
global-load-balancer-operator
Additional details
Please add the following github secrets
QUAY_USERNAME
QUAY_PASSWORD
with push grants to the following quay repo (create them if necessary):
quay.io/redhat-cop/global-load-balancer-operator
quay.io/redhat-cop/global-load-balancer-operator-bundle
these repos should be public.
Finally disconnect travis and any permission that it holds against this repo.

Review request:
cc: @redhat-cop/container-cop-core

Resolved by #311


Specify Laravel version

Since Laravel doesn't follow SemVer we wont know if this package will break in 5.3. We can be more specific.

good point.
I have a question, when your building a package that supports several breaking releases of laravel (5.1, 5.2, ...). Sometimes the methods signature change, or even never exist in earlier version. How can you be sure that it'll work on all version specified? do you manually test the package on every laravel version to make sure it's working?

I usually rely on my test suite and keep up to date with changes in breaking Laravel releases. But in trickier cases I create a new Laravel application.

I thought so, thank you :)


Implement znx INFO file

znx will make use of a .INFO file for updates. The code here only embeds the update URL in the ISO.
https://github.com/Nitrux/znx/issues/40

:thinking: I remember to have written the necessary code to write the .INFO file.

Yeah, I remember that too, but I couldn't find it.

Implemented on 782be05.


Building skeleton project with pnpm fails with "SyntaxError: Named export 'svelteInspector' not found"

Describe the bug
Building default SvelteKit project fails with pnpm.
error during build:
file:///C:/Users/***/import-bug-app/node_modules/.pnpm/@sveltejs+vite-plugin-svelte@4.0.0-next.6_svelte@5.0.0-next.242_vite@5.4.2/node_modules/@sveltejs/vite-plugin-svelte/src/index.js:2
import { svelteInspector } from '@sveltejs/vite-plugin-svelte-inspector';
         ^^^^^^^^^^^^^^^
SyntaxError: Named export 'svelteInspector' not found. The requested module '@sveltejs/vite-plugin-svelte-inspector' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from '@sveltejs/vite-plugin-svelte-inspector';
const { svelteInspector } = pkg;

    at ModuleJob._instantiate (node:internal/modules/esm/module_job:171:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:254:5)
    at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:485:26)
    at async load_config (file:///C:/Users/***/import-bug-app/node_modules/.pnpm/@sveltejs+kit@2.5.25_@sveltejs+vite-plugin-svelte@4.0.0-next.6_svelte@5.0.0-next.242_vite@5.4_ufaaiyt2bqpun3h6qnri6hdj2e/node_modules/@sveltejs/kit/src/core/config/index.js:70:17)
    at async sveltekit (file:///C:/Users/***/import-bug-app/node_modules/.pnpm/@sveltejs+kit@2.5.25_@sveltejs+vite-plugin-svelte@4.0.0-next.6_svelte@5.0.0-next.242_vite@5.4_ufaaiyt2bqpun3h6qnri6hdj2e/node_modules/@sveltejs/kit/src/exports/vite/index.js:130:24)
    at async Promise.all (index 0)
    at async asyncFlatten (file:///C:/Users/***/import-bug-app/node_modules/.pnpm/vite@5.4.2/node_modules/vite/dist/node/chunks/dep-BzOvws4Y.js:17501:12)
    at async resolveConfig (file:///C:/Users/***/import-bug-app/node_modules/.pnpm/vite@5.4.2/node_modules/vite/dist/node/chunks/dep-BzOvws4Y.js:66054:27)
    at async build (file:///C:/Users/***/import-bug-app/node_modules/.pnpm/vite@5.4.2/node_modules/vite/dist/node/chunks/dep-BzOvws4Y.js:65125:18)
    at async CAC.<anonymous> (file:///C:/Users/***/import-bug-app/node_modules/.pnpm/vite@5.4.2/node_modules/vite/dist/node/cli.js:828:5)

Reproduction URL
npm create svelte@latest my-app
Reproduction

npm create svelte@latest import-bug-app
a. Which Svelte app template? -> Skeleton project
b. Add type checking with TypeScript? -> Yes, using TypeScript syntax
c. Select additional options (use arrow keys/space bar) -> Try the Svelte 5 preview (unstable!)
cd import-bug-app
pnpm install
pnpm run build

Logs
No response
System Info
System:
    OS: Windows 11 10.0.22631
  Binaries:
    Node: 22.4.1 - C:\Program Files\nodejs\node.EXE
    npm: 10.8.2 - C:\Program Files\nodejs\npm.CMD
    pnpm: 9.9.0 - ~\AppData\Roaming\npm\pnpm.CMD
  npmPackages:
    @sveltejs/adapter-auto: ^3.0.0 => 3.2.4
    @sveltejs/kit: ^2.0.0 => 2.5.25
    @sveltejs/vite-plugin-svelte: ^4.0.0-next.6 => 4.0.0-next.6
    svelte: ^5.0.0-next.1 => 5.0.0-next.242
    vite: ^5.0.3 => 5.4.2

Updating the Node from 22.4.1 to 22.7.0 solved the issue.
The error changed to the following warning:
(node:46756) [MODULE_TYPELESS_PACKAGE_JSON] Warning: file:///C:/Users/***/import-bug-app/node_modules/.pnpm/@sveltejs+vite-plugin-svelte-inspector@3.0.0-next.3_@sveltejs+vite-plugin-svelte<EMAIL_ADDRESS>parsed as an ES module because module syntax was detected; to avoid the performance penalty of syntax detection, add "type": "module" to C:\Users\***\import-bug-app\node_modules\.pnpm\@sveltejs+vite-plugin-svelte-inspector@3.0.0-next.3_<EMAIL_ADDRESS>(Use `node --trace-warnings ...` to show where the warning was created)

this is not the first report for this issue, however type: module is set https://github.com/sveltejs/vite-plugin-svelte/blob/16eae1bc7b204c401ccfe16722a6098cc70753b0/packages/vite-plugin-svelte-inspector/package.json#L10
its possible that something in pnpm goes wrong, deleting node_modules and reinstalling might help too

I've been trying a few things multiple times. I did a ppm cash reset and uninstalled ppm several times.
But, only after updating the Node version,the issue was immediately resolved in three separate projects.

#922 mentioned changing the pnpm version installed by corepack helped them. i don't think its node itself but either way glad it is resolved for you. Happy svelting

Also experienced this on windows today, no pnpm cache clear / store prune whatever helped. The relevant info here was to update node, which solved the problem immediately.