text:
Add react node text util

Description
I wanted to implement a simple matchFilter for the SingleSelectWithFilter that can match on the content attribute, which is a ReactNode.
Proposed Changes

I added a small util called getReactNodeTextContent that converts a ReactNode into a string by keeping only the text content (it strips the html tags)

Potential Breaking Changes
None.
Acceptance Criteria

[x] The proposed changes are covered by unit tests
[x] The potential breaking changes are clearly identified
[x] README.md is adjusted to reflect the proposed changes (if relevant)

Codecov Report

Merging #1170 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1170   +/-   ##
=======================================
  Coverage   99.74%   99.74%
=======================================
  Files         350      350
  Lines        8537     8537
  Branches     2033     2033
=======================================
  Hits         8515     8515
  Misses         22       22

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 9d9e0a8...426b534. Read the comment docs.

authors: codecov-io gdostie

repo: coveo/react-vapor


text:
refactor(svg.tsx): moved the icon modifier in svg component

Proposed Changes

Potential Breaking Changes

Acceptance Criteria

[ ] The proposed changes are covered by unit tests
[ ] The potential breaking changes are clearly identified
[ ] README.md is adjusted to reflect the proposed changes (if relevant)

Codecov Report

Merging #1442 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1442   +/-   ##
=======================================
  Coverage   98.98%   98.98%
=======================================
  Files         492      492
  Lines       10218    10218
  Branches     2358     2358
=======================================
  Hits        10114    10114
  Misses        104      104

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 406ba6c...6c7676b. Read the comment docs.

source: gharchive/pull-request

authors: FelixBlaisThon codecov-io

license_type: permissive

license_source: github-api


text:
feat(atomic-react): add CommonJS output

https://coveord.atlassian.net/browse/KIT-1752
Thanks @btaillon for the idea! Looked harder than I though 😅

@liviarett It was a customer request https://discuss.coveo.com/t/support-00084474-is-it-possible-to-compile-atomic-react-into-commonjs-modules-cjs/8011/6

repo: coveo/ui-kit


text:
Add Tested cases in state wise table

Is your feature request related to a problem? Please describe.
It would be nice to have column to have number of tested cases against each state

This cannot be added in the main UI as there is simply not enough space to display these numbers. Also, this information is available in the state pages.

source: gharchive/issue

authors: sudevschiz vikramnr

license: MIT


text:
Where is the FENet?

Thanks for your work! But I can't find the FENet and its config file.

I didn't find it either. It seems that the code does not have the new modules in the paper

repo: cowarder/FENet


text:
Question relating the amount of output mixture parameters

Hi! Thanks for your implementation, great work. I am still learning about mixture density networks and have a question relating to the amount of output parameters.
In this implementation it seems that there are (2 * NUMBER_MIXTURES * OUTPUT_DIM) + (NUMBER_MIXTURES * OUTPUT_DIM) parameters. For example, in the Kanji notebook this results in 2*10*3 + 10 = 70 outputs.
However, in some other implementations of MDN-RNN's such as the one from World Models (https://github.com/hardmaru/WorldModelsExperiments/blob/master/carracing/rnn/rnn.py) there seems to be 3 * NUMBER_MIXTURES * OUTPUT_DIM output parameters. I think the difference is that you only model NUMBER_MIXTURES mixing coefficients, and they model NUM_MIXTURES * OUTPUT_DIM mixture coefficients. In your Kanji notebook this would result in 3*10*3 = 90 outputs.
I was wondering why this difference between implementations exists? Is this due to the difference that your code does not model the covariance of the Gaussians or is that something unrelated? Thanks in advance!

Astute observation! I've noticed this as well.
Yep, MDNs can be different depending on how you want to set up the mixture model at the output. This library is a bit different from hardmaru's one over in the World Models repo. But I don't think it's to do with covariances.
For this library, the output model is a mixture of multivariate Gaussian distributions. Each of the Gaussian distributions has a dimension (OUTPUT_DIM), and is constrained to have a diagonal covariance matrix (this just makes it easy to calculate the PDF, and so that we can use the TensorFlow MultivariateNormalDiag implementation of this distribution). This means that there are two parameters for each dimension of the Gaussian distributions, a centre and a variance, which could be called mu and sigma. This gives us 2 * OUTPUT_DIM parameters for each multivariate Gaussian distribution.
Now, of course, we need to have one independent instance of this distribution for each component of the mixture model. So this gives us NUMBER_MIXTURES * 2 * OUTPUT_DIM parameters for all of the Gaussian distributions.
There's one last thing: the parameters that mix these Gaussian components such that some of them are more or less likely to be drawn than others. For this, we need one parameter for each mixture component (pi).
Thus, we end up with a total of (NUMBER_MIXTURES * 2 * OUTPUT_DIM) + NUMBER_MIXTURES parameters.

Now as far as I can tell, and it has been a while (9-10 months) since I checked, but the World Models repo actually uses a completely separate mixture distribution for each dimension to be modelled.
So this gives us NUM_MIXTURES * (2 + 1) == NUM_MIXTURES * 3 for each dimension, and then NUM_MIXTURES * 3 * OUTPUT_DIM for the complete model.
This method for constructing the output distribution didn't (and still doesn't) make as much sense to me because the mixtures are kind of independent for each dimension. I think the samples must then be drawn independently for each dimension.
My view is that each mixture should be a complete model of the "World" (or data), that is all dimensions at once. And that you can navigate between "Worlds" by manipulating the mixing variables.
I asked hardmaru about this at Neurips and he said (very politely) something along the lines of "because it trains better"---tbh I can't argue with that! If it works, then great! I still think that my version here has the benefit of each mixture component modelling all output dimensions at once, but it is certainly a bit more complicated for training (due to the MultivariateNormalDiag distribution). Additionally, some of my colleagues have tried replicating some of the World Models tasks (e.g., vizdoom dodging) and the results may not have been quite as good (not sure of details).
Certainly happy to continue thinking about the best way to model multidimensional data here! Any thoughts or experiments are welcome!

authors: cpmpercussion vanmil

repo: cpmpercussion/keras-mdn-layer


text:
Removed old Python API

@zalox merge if it's ok to remove these files

To avoid conflicts I think It's better to cherry pick 1cb806eb0067482e6f7397731e90320c30823299.

I can do it if you'd like :)

Sure, thank you!

authors: eidheim zalox

repo: cppit/jucipp

license: mit

license_source: bigquery


text:
Icon dont starts with default svg size

<svgo-social-discord
					color="var(--grey-700)"
					class="w-[16px] h-[16px]"
				/>

I import an icon, but the sizes dont keep values on viewbox or original svg file, i need to set on every icon the sizes?

the size is controlled by font size by default
to disable font control, use :font-controlled="false"
the default svgo configuration is mentioned in the readme, you can change the behavior if you need to

repo: cpsoinos/nuxt-svgo


text:
Add secure authentication

Integrate it with third party oauth provider such as Google

Google Oauth integrated


text:
Assembly bounding_box

In response to #152

Thank you o programmatic $DEITY.

haha!, no problem @zignig!
I think of myself more of a servant to the programming gods, and less of a god myself ;)

authors: fragmuffin zignig

repo: cqparts/cqparts


text:
Make ll_tim_utils a class with TIMER instance member

Convert to a class
Added std::unique_ptr member to the TIMER instance i.e. TIM14
Add constructor that will set that TIMER (preferably through c'tor arg)
[optional] Add additional setup to the c'tor for the timer.

https://github.com/cracked-machine/embedded_utils/commit/20f5373ef93a7f8f8d773304ab3207e4c89b377d


text:
There's no POT file for translations

I need to translate Checkout Labels from English to Spanish, I tried using Loco Translate WP Plugin but no template was found, I tried creating one from source files (php) but only 4 strings were found. Please add a POT template and update. Thanks!

Thanks for the suggestion. I created the POT files and pushed the to the following branch:
https://github.com/craigchristenson/woocommerce-2checkout-api/tree/translations
Please let me know if this works ok for you.

Many thanks for the POT file, I haven't tried it yet since I'm redesigning my website, but I'd soon let you know if it works. :)

authors: craigchristenson natirivero


text:
error: cannot downgrade package-xyz from 1.0.0-rc10 to 1.0.0-rc9

After rc9 I cannot create rc10, however rc91 is working. Is this my mistake?

Thanks for the clarification @page, much appreciated!

repo: crate-ci/cargo-release


text:
add CrateDB Guide and reshuffle docs organisation

this PR:

retires the Cactus links
adds links to the new CrateDB Guide
reshuffles the organisation of the docs

see: https://trello.com/c/7od7BLjy/74
the menu now looks like this:

the new URLs look like this:
/docs/cratedb/reference (the main CrateDB docs, a reference work)
/docs/cratedb/guide (the new CrateDB guide)
/docs/clients/crash
/docs/clients/python
/docs/clients/java
...
for this to work, we will have to update our fastly config

lgtm

thanks! I'll wait until the new project is up before I merge and release

authors: chaudum nslater

repo: crate/crate-docs-theme


text:
Add scalar function pg_get_function_result required by conn.getMetaData().getFunctions()

complementing https://github.com/crate/crate/pull/10286 to resolve https://github.com/crate/crate/issues/9976

Shouldn't the query mentioned in https://github.com/crate/crate/issues/9976 return proper values for pg_get_function_result(oid)?
With this PR I get:
cr> select pg_get_function_result(oid), proname from pg_proc where proname = 'trunc' limit 10;
+-----------------------------+---------+
| pg_get_function_result(oid) | proname |
+-----------------------------+---------+
|                        NULL | trunc   |
|                        NULL | trunc   |
|                        NULL | trunc   |
|                        NULL | trunc   |
|                        NULL | trunc   |
|                        NULL | trunc   |
|                        NULL | trunc   |
+-----------------------------+---------+

The pg_prog table was registering function OID's based on their name, instead of their signature.
This PR is ready for review, I have added a specific test.

authors: marregui mfussenegger

repo: crate/crate


text:
implement broadcast distributing downstream

distributing downstream will block now if 1 page is consumed and not yet sent to downstreams.
also renamed existing distributing downstream to ModuloDistributingDownstream

otherwise ack

ack

authors: mfussenegger seut


text:
RAG: Problems resolving dependencies on Google Colab

Problem
@hammerhead reported a flaw with the cratedb_rag_customer_support_langchain.ipynb Notebook when invoked on Google Colab.
Dependency resolution around Dask fails, bzw. takes ages to complete, if at all.
Collecting dask (from fsspec[abfs,dask,gcs,git,github,http,s3,smb]<2024.3->pueblo[cli,fileio,nlp]>=0.0.7->-r https://raw.githubusercontent.com/crate/cratedb-examples/main/topic/machine-learning/llm-langchain/requirements.txt (line 9))
  Downloading dask-2022.5.2-py3-none-any.whl (1.1 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.1/1.1 MB 65.4 MB/s eta 0:00:00
Collecting distributed (from fsspec[abfs,dask,gcs,git,github,http,s3,smb]<2024.3->pueblo[cli,fileio,nlp]>=0.0.7->-r https://raw.githubusercontent.com/crate/cratedb-examples/main/topic/machine-learning/llm-langchain/requirements.txt (line 9))
  Downloading distributed-2022.5.1-py3-none-any.whl (871 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 871.6/871.6 kB 54.8 MB/s eta 0:00:00
Collecting dask (from fsspec[abfs,dask,gcs,git,github,http,s3,smb]<2024.3->pueblo[cli,fileio,nlp]>=0.0.7->-r https://raw.githubusercontent.com/crate/cratedb-examples/main/topic/machine-learning/llm-langchain/requirements.txt (line 9))
  Downloading dask-2022.5.1-py3-none-any.whl (1.1 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.1/1.1 MB 57.8 MB/s eta 0:00:00
Collecting distributed (from fsspec[abfs,dask,gcs,git,github,http,s3,smb]<2024.3->pueblo[cli,fileio,nlp]>=0.0.7->-r https://raw.githubusercontent.com/crate/cratedb-examples/main/topic/machine-learning/llm-langchain/requirements.txt (line 9))
  Downloading distributed-2022.5.0-py3-none-any.whl (856 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 856.7/856.7 kB 60.6 MB/s eta 0:00:00
Collecting dask (from fsspec[abfs,dask,gcs,git,github,http,s3,smb]<2024.3->pueblo[cli,fileio,nlp]>=0.0.7->-r https://raw.githubusercontent.com/crate/cratedb-examples/main/topic/machine-learning/llm-langchain/requirements.txt (line 9))
  Downloading dask-2022.5.0-py3-none-any.whl (1.1 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.1/1.1 MB 59.9 MB/s eta 0:00:00
Collecting distributed (from fsspec[abfs,dask,gcs,git,github,http,s3,smb]<2024.3->pueblo[cli,fileio,nlp]>=0.0.7->-r https://raw.githubusercontent.com/crate/cratedb-examples/main/topic/machine-learning/llm-langchain/requirements.txt (line 9))
  Downloading distributed-2022.4.2-py3-none-any.whl (856 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 856.7/856.7 kB 61.6 MB/s eta 0:00:00
Collecting dask (from fsspec[abfs,dask,gcs,git,github,http,s3,smb]<2024.3->pueblo[cli,fileio,nlp]>=0.0.7->-r https://raw.githubusercontent.com/crate/cratedb-examples/main/topic/machine-learning/llm-langchain/requirements.txt (line 9))
  Downloading dask-2022.4.2-py3-none-any.whl (1.1 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.1/1.1 MB 61.3 MB/s eta 0:00:00
Collecting distributed (from fsspec[abfs,dask,gcs,git,github,http,s3,smb]<2024.3->pueblo[cli,fileio,nlp]>=0.0.7->-r https://raw.githubusercontent.com/crate/cratedb-examples/main/topic/machine-learning/llm-langchain/requirements.txt (line 9))
  Downloading distributed-2022.4.1-py3-none-any.whl (855 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 855.5/855.5 kB 59.3 MB/s eta 0:00:00
Collecting dask (from fsspec[abfs,dask,gcs,git,github,http,s3,smb]<2024.3->pueblo[cli,fileio,nlp]>=0.0.7->-r https://raw.githubusercontent.com/crate/cratedb-examples/main/topic/machine-learning/llm-langchain/requirements.txt (line 9))
  Downloading dask-2022.4.1-py3-none-any.whl (1.1 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.1/1.1 MB 60.5 MB/s eta 0:00:00
Collecting distributed (from fsspec[abfs,dask,gcs,git,github,http,s3,smb]<2024.3->pueblo[cli,fileio,nlp]>=0.0.7->-r https://raw.githubusercontent.com/crate/cratedb-examples/main/topic/machine-learning/llm-langchain/requirements.txt (line 9))
  Downloading distributed-2022.4.0-py3-none-any.whl (853 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 853.8/853.8 kB 52.3 MB/s eta 0:00:00
Collecting dask (from fsspec[abfs,dask,gcs,git,github,http,s3,smb]<2024.3->pueblo[cli,fileio,nlp]>=0.0.7->-r https://raw.githubusercontent.com/crate/cratedb-examples/main/topic/machine-learning/llm-langchain/requirements.txt (line 9))
  Downloading dask-2022.4.0-py3-none-any.whl (1.1 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.1/1.1 MB 56.7 MB/s eta 0:00:00
Collecting distributed (from fsspec[abfs,dask,gcs,git,github,http,s3,smb]<2024.3->pueblo[cli,fileio,nlp]>=0.0.7->-r https://raw.githubusercontent.com/crate/cratedb-examples/main/topic/machine-learning/llm-langchain/requirements.txt (line 9))
  Downloading distributed-2022.3.0-py3-none-any.whl (851 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 851.2/851.2 kB 54.7 MB/s eta 0:00:00
Collecting dask (from fsspec[abfs,dask,gcs,git,github,http,s3,smb]<2024.3->pueblo[cli,fileio,nlp]>=0.0.7->-r https://raw.githubusercontent.com/crate/cratedb-examples/main/topic/machine-learning/llm-langchain/requirements.txt (line 9))
  Downloading dask-2022.3.0-py3-none-any.whl (1.1 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.1/1.1 MB 60.3 MB/s eta 0:00:00
Requirement already satisfied: httplib2>=0.9.1 in /usr/local/lib/python3.10/dist-packages (from oauth2client>=1.5.2->gcsfs->fsspec[abfs,dask,gcs,git,github,http,s3,smb]<2024.3->pueblo[cli,fileio,nlp]>=0.0.7->-r https://raw.githubusercontent.com/crate/cratedb-examples/main/topic/machine-learning/llm-langchain/requirements.txt (line 9)) (0.22.0)
  Downloading dask-2023.8.1-py3-none-any.whl (1.2 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.2/1.2 MB 7.8 MB/s eta 0:00:00
INFO: pip is looking at multiple versions of distributed to determine which version is compatible with other requirements. This could take a while.
INFO: pip is looking at multiple versions of distributed to determine which version is compatible with other requirements. This could take a while.
INFO: This is taking longer than usual. You might need to provide the dependency resolver with stricter constraints to reduce runtime. See https://pip.pypa.io/warnings/backtracking for guidance. If you want to abort this run, press Ctrl + C.
ERROR: Operation cancelled by user

Thoughts
It looks like it is clearly related to the Python 3.11.9 vs. Dask hiccup from last week.

https://github.com/pycaret/pycaret/issues/3966
https://github.com/crate/cratedb-examples/pull/421

References
Maybe related; I will execute this first; maybe, it will yield some insights.

GH-422

@hammerhead also provided a fix already.

GH-423

Observations
@hammerhead reported that he experienced the problems in the area of pueblo[fileio]. As of its v0.0.9, this is the list of dependencies of this extra:
fileio = [
  "fsspec[abfs,dask,gcs,git,github,http,s3,smb]<2024.3",
  "pathlibfs<0.6",
  "python-magic<0.5",
  "yarl<1.10",
]

-- https://github.com/pyveci/pueblo/blob/v0.0.9/pyproject.toml#L95-L100
On the other hand, this is the list of dependencies of current development head, which deviates in the version of fsspec, which, in turn, also pulls in dask, but without specifying any version.
fileio = [
  "fsspec[abfs,dask,gcs,git,github,http,s3,smb]<2024.4",
  "pathlibfs<0.6",
  "python-magic<0.5",
  "yarl<1.10",
]

-- https://github.com/pyveci/pueblo/blob/71ff638/pyproject.toml
Thoughts
I don't see any immediate problems with the combination of dependencies, but the devil may well be in the details.

@hammerhead reported that he experienced the problems in the area of pueblo[fileio].

This patch gets rid of the dependency completely.

GH-428

repo: crate/cratedb-examples


text:
Query with missing semi-colon gets wrongfully parsed

The following 4 statements
select 1;
select 1 I can put anything here
select 3

... get parsed into 2 seemly valid statements ...
[
  Statement {
    query: 'select 1',
    originalQuery: 'select 1;\nselect 1 I can put anything here\nselect 3;',
    tree: '(statement (query (queryNoWith (queryTerm (querySpec select (selectItem (expr (booleanExpression (predicated (valueExpression (primaryExpression (parameterOrLiteral (parameterOrSimpleLiteral (numericLiteral (integerLiteral 1)))))))))))))))',
    type: 'select',
    ctx: DefaultContext {
      parentCtx: [StatementsContext],
      invokingState: 250,
      children: [Array],
      start: [Pt],
      stop: [Pt],
      exception: null,
      parser: [_SqlBaseParser],
      ruleIndex: 3
    },
    exception: null,
    metadata: Metadata {
      tables: [],
      parameterizedProperties: {},
      withProperties: {}
    }
  },
  Statement {
    query: 'select 1 I',
    originalQuery: 'select 1;\nselect 1 I can put anything here\nselect 3;',
    tree: '(statement (query (queryNoWith (queryTerm (querySpec select (selectItem (expr (booleanExpression (predicated (valueExpression (primaryExpression (parameterOrLiteral (parameterOrSimpleLiteral (numericLiteral (integerLiteral 1))))))))) (ident (unquotedIdent I))))))))',
    type: 'select',
    ctx: DefaultContext {
      parentCtx: [StatementsContext],
      invokingState: 252,
      children: [Array],
      start: [Pt],
      stop: [Pt],
      exception: null,
      parser: [_SqlBaseParser],
      ruleIndex: 3
    },
    exception: null,
    metadata: Metadata {
      tables: [],
      parameterizedProperties: {},
      withProperties: {}
    }
  }
]

... ignoring the missing semicolon ;  and dropping the select 2; query.

It's one of those situation edge cases where antlr4 doesn't give us context of the error, so we have to make up for that and use some heuristics. It's where we differ from the original CrateDB implementation, they only parse single statements while we do multiple statements, issues arises that never appeared to the core team hence the novelty.
These are very edge cases and we might find more in the future but at least they are very self contained (I know exactly where they happen) and at some point the heuristics will be good enough to cover most if not all. Growing pain unfortunately.

authors: proddata surister

repo: crate/cratedb-sqlparse


text:
Custom Init script

Is there a way of running a custom init script at container start?
the gist:
At container startup, set a default route within the torrent container so that traffic goes through through my VPN container that uses IP masquerade. (I am avoiding setting the network mode to container or service)
how I normally accomplish this:
Using linuxserver images, one can just mount a script into the container at ./script/dir:/custom-init-script.d and the container will run every script there at startup
What I have tried:
mount script into cont-init: ./script.sh:/etc/cont-init.d/99-script.sh
result: Container starts but script fails
Command line is not complete. Try option "help"
/var/run/s6/etc/cont-init.d/99-script.sh: line 7: curl: command not found
mount script directory into container and use command in docker compose 'command: /script/dir/script.sh
result:
Script works but the container goes on a restart/terminate loop.
I can run the script after container startup using docker exec, and it works, but this doesn't persist between restarts.
script I am trying to run(env vars are passed via docker compose environment:):
#!/bin/bash

ip route del default
ip route add default via ${VPN_CONT_IP}
ip route add ${HOST_LAN:-10.0.1.0/24} via 10.0.10.1

wanip=$(curl icanhazip.com)

echo "##############################################################"
echo "# Now routing through ${VPN_CONT_IP} to WAN IP $wanip. #"
echo "##############################################################"

any suggestions on how I can accomplish this are greatly appreciated

Similar issue here, would like to set WAN and incoming port at container startup. I could probably achieve that by running a script at startup.

I agree that this should be done properly, but mounting a shell script into /etc/cont-init.d worked fine for me. Try to add the full path to the curl command like /usr/local/bin/curl, it's possible that the s6-init is not appending all the known bin locations on PATH environment variable.

authors: gnammix tigerkzr trunet

repo: crazy-max/docker-rtorrent-rutorrent


text:
Day69: LeetCode-2133. Check if Every Row and Column Contains All Numbers - HashTable

Check if Every Row and Column Contains All Numbers
https://leetcode.com/problems/check-if-every-row-and-column-contains-all-numbers/
An n x n matrix is valid if every row and every column contains all the integers from 1 to n (inclusive).
Given an n x n integer matrix matrix, return true if the matrix is valid. Otherwise, return false.

Example 1:
Input: matrix = [[1,2,3],[3,1,2],[2,3,1]]
Output: true
Explanation: In this case, n = 3, and every row and column contains the numbers 1, 2, and 3.
Hence, we return true.
Example 2:
Input: matrix = [[1,1,1],[1,2,3],[1,2,3]]
Output: false
Explanation: In this case, n = 3, but the first row and the first column do not contain the numbers 2 or 3.
Hence, we return false.

repo: crazymanish/dsa


text:
[BUG] Selecting Configuration menu from tray menu shows javascript error

General information

OS: macOS M1 64Gb
Hypervisor: vfkit
Did you run crc setup before starting it? - Yes, using configuration wizard popped up after firs start
Running CRC on: Laptop

CRC version
CRC version: 2.15.0+72256c3c
OpenShift version: 4.12.5
Podman version: 4.3.1

CRC status
DEBU CRC version: 2.15.0+72256c3c
DEBU OpenShift version: 4.12.5
DEBU Podman version: 4.3.1
DEBU Running 'crc status'
CRC VM:          Running
OpenShift:       Running (v4.12.5)
RAM Usage:       6.78GB of 9.353GB
Disk Usage:      16.78GB of 32.74GB (Inside the CRC VM)
Cache Usage:     73.71GB
Cache Directory: /Users/eskimo/.crc/cache
DEBU Running 'sw_vers -productVersion'

Looks like CRC version step could be removed, because it is in CRC status output anyway
CRC config
- consent-telemetry                     : yes

Host Operating System
ProductName:		macOS
ProductVersion:		13.2
BuildVersion:		22D49

Steps to reproduce

Start OpenShift Local
Open Configuration from tray menu
Close configuration using Cancel
Open Configuration again

Expected
To see configuration
Actual

Logs

@dgolovin is this issue happening all the time?

It works first time, then I get the message every time I try to open configuration dialog.

authors: dgolovin gbraad

repo: crc-org/tray-electron


text:
Refactor blockhash-python into a library

We'd like to experiment with https://github.com/commonsmachinery/blockhash-python, but it's not written as a library, just a command-line tool.
Refactor into a library through our own fork, https://github.com/creativecommons/blockhash-python
This is to support #5

Done.

repo: creativecommons/open-ledger


text:
Fixed storybook link in README and also removed styleguide

Fixes

Fixes #174 by @techievivek
Description
It updates the storybook link in README and also removes the styleguide that has been deleted.
Type of PR
This PR is a [feature|hotfix|refactor].
Technicalities
Just updates the link.
Tests
Click on the stylebook link.
Screenshots

Checklist:

[x] My pull request has a descriptive title (not a vague title like "Update index.md").
[x] My pull request targets the master branch of the repository.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no visible errors.

Legal
By submitting this PR, I agree to abide by the terms of the Developer
Certificate of Origin.

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1
Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.

I think the issue persists. It still takes to Page not found. This is the link https://cc-vue-vocabulary.netlify.com/storybook it takes to.

I will update it, sorry for the mistake.

@dhruvkb is this the correct URL https://cc-vocabulary.netlify.com/

@dhruvkb Because what I remember it had storybook part too in URL? But I am not getting that link anywhere.

@dhruvkb Also please help me how can I update this edit, do I have to create a new Issue and then a new PR, or is there any way to directly get the change?

Actually the link was /storybook but it was changed again! @techievivek please create a new PR for this issue.

authors: Dhruvi16 dhruvkb techievivek

repo: creativecommons/vue-vocabulary


text:
[Feature Request] Electron

What is your enhancement?
Add support to nextron or electron

Hello there, @inginheiiro ,
Unfortunately, we won't add support for nextron or electron.
Best,
Manu

authors: EINazare inginheiiro


text:
Add bower build

Browser compatibility will be nice.

We can use browserify unless otherwise needed.


text:
@bs.scope equivalent

I've been looking into testing genType on a larger project and currently I'm unsure about how to import it when it's deeply nested in JS objects. Here's an example:
https://github.com/FiberJW/reason-expo/blob/6be95471afd0ce0b88b8bb92d371c9692b88a08d/src/Camera.re#L5

@cem2ran would something like this work?
[@genType.import "expo-camera/src/Camera"]
[@genType.as "Constants.Type"]
[@bs.module "./TestImport.gen"]
external cameraType: Js.t(_) = "";

which generates
// flowlint-next-line nonstrict-import:off
import {Constants as cameraTypeNotChecked} from 'expo-camera/src/Camera';

// In case of type error, check the type of 'cameraType' in 'TestImport.re' and 'expo-camera/src/Camera'.
export const cameraTypeTypeChecked: Js_t<mixed> = cameraTypeNotChecked.Type;

// Export 'cameraType' early to allow circular import from the '.bs.js' file.
export const cameraType: mixed = cameraTypeTypeChecked;

This should take care of the use case:
https://github.com/cristianoc/genType/commit/df0d810eb49d166759d8fdda2bb6623d786b0979
Let me know if that works for you.

Closing optimistically.
If the use case is not completely covered, or if related issues come up, feel free to reopen.

repo: cristianoc/genType


text:
Create additional HTMLs

Creation of additional HTMLs for other pages in application.

completed


text:
拼团和砍价页面丢失

购买商业版，才有这两个功能

repo: crmeb/CRMEB


text:
No system manifest found

When trying to install/update the system I get the following error:

I'm using the most recent version of foundry (V11 Build 315). I believe the error is caused by a mistake in the naming of the latest release which was named 0.6.19 instead of 0.16.9 and thus the link foundry tries to access does not exist.
For anyone having this issue: This is a really well mantained repo and I'm sure this will be fixed very soon, however in the meantime anyone looking to install the latest version I believe it's just a matter of using the following manifest URL to install the system:
https://github.com/crnormand/gurps/releases/download/0.6.19/system.json
Foundry will thin

Right... was a bit shaky... it was the first release in a while ;-)
I'll fix it.

OK, "should" be fixed!

authors: crnormand henrypickler

repo: crnormand/gurps


text:
Update plugin version and remove powermock

Because of #7, I tried to fix the build.
Turns out, that the error in the build was because the intellij gradle plugin was too old.
When updating this it turned out that powermock didn't work. Since I don't like the usage of Powermock anyway, I removed it.

@cowclaw could your review this when you've got time ?

To avoid, or at least get notifed when this plugin doesn't build anymore I suggest running a monthly github actions build 4563eefa70475afde56ab72ae508802a4e41750e


text:
using components transport.endpoint.tls.trust_root requires to call tls.load_default_certs() to work with sslmate certificate

We have a certificate generated with sslmate.
crosbar config:
---
version: 2
workers:
  - type: router
    realms:
      - name: foobar
        roles:
          - name: anonymous
            permissions:
              # allow all
              - uri: ""
                match: prefix
                allow:
                  call: true
                  register: true
                  publish: true
                  subscribe: true
                disclose:
                  caller: false
                  publisher: false
                cache: true
    transports:
      - type: websocket
        endpoint:
          type: tcp
          port: 8443
          tls:
            key: ../certs/foobar.key
            certificate: ../certs/foobar.crt
        url: wss://foobar:8443/ws

The autobahn component gets the following config (parsed from yaml and put straight into **kwargs):
component:
  realm: foobar
  transports:
    - type: websocket
      url: wss://foobar:8443/ws
      endpoint:
        type: tcp
        host: foobar
        port: 8443
        tls:
          hostname: foobar
          trust_root: certs/foobar.chain.crt

Connecting the component gives following error:
2018-05-29T08:56:54.330776Z [info     ] Connection failed: SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:833) [autobahn.asyncio.component.Component]

openssl s_client -CAfile certs/foobar.chain.crt -showcerts -connect foobar:8443 works as expected.
When I call tls.load_default_certs() after https://github.com/crossbario/autobahn-python/blob/master/autobahn/asyncio/component.py#L248 everything works.
So the question appears, is this intended and should I use a custom SSLContext for this, while I imaging it would be a good way to load default certs at least as an option, if not allways...

load default certs at least as an option

This sounds useful! I think we should have that .. in crossbar.io (means: I will close and move the issue)

Moved to https://github.com/crossbario/crossbar/issues/1343

authors: diefans oberstet

repo: crossbario/autobahn-python


text:
flaky test: test_non_depleting

The test occasionally fails, here is one such instance https://travis-ci.org/crossbario/autobahn-python/jobs/628375836

FWIW, test_non_depleting fails consistently on my machine. Here is a sample run: (I commented out test_depleting as it appears to never finish like what https://github.com/crossbario/autobahn-python/issues/1275 described)
$ PYTHONPATH=. trial3 autobahn/test/test_rng.py
autobahn.test.test_rng
  TestEntropy
    test_non_depleting ...
system entropy depletion stats:
0: 1000
                                              [FAIL]

===============================================================================
[FAIL]
Traceback (most recent call last):
  File "/usr/lib/python3.8/unittest/case.py", line 60, in testPartExecutor
    yield
  File "/usr/lib/python3.8/unittest/case.py", line 676, in run
    self._callTestMethod(testMethod)
  File "/usr/lib/python3.8/unittest/case.py", line 633, in _callTestMethod
    method()
  File "/home/yen/tmp/autobahn-python/autobahn/test/test_rng.py", line 87, in test_non_depleting
    self.assertTrue(skeys[0] > 10)
  File "/usr/lib/python3.8/unittest/case.py", line 765, in assertTrue
    raise self.failureException(msg)
builtins.AssertionError: False is not true

autobahn.test.test_rng.TestEntropy.test_non_depleting
-------------------------------------------------------------------------------
Ran 1 tests in 6.468s

FAILED (failures=1)

Tested with autobahn commit ae29569ac03c51a7a7aa106a498a903b8f457bb0.

ok, pls see https://github.com/crossbario/autobahn-python/issues/1275#issuecomment-574105216
I have left the test active in our CI .. but yes, the test did fail for me in the past occasionally as well .. it is definitely somewhat non-deterministic (and hence not really correct). hence, for now, I leave this issue open ..


text:
提供的二进制文件里面没有windows版本

提供的二进制文件里面没有windows版本

暂时没有 window 设备进行编译，可以参考这里手动安装。
https://github.com/crossoverJie/gscript/issues/14
也可以在线试用：
https://gscript.crossoverjie.top/

现已提供 docker 版本：
https://github.com/crossoverJie/gscript#docker

authors: crossoverJie fenginsc

repo: crossoverJie/gscript


text:
Configure ResourcePolicy.dynamodb resource and add example

Description of your changes
This PR configures ResourcePolicy.dynamodb resource and adds an example.
Fixes https://github.com/crossplane-contrib/provider-upjet-aws/issues/1307
I have:

[ ] Read and followed Crossplane's contribution process.
[ ] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

/test-examples="examples/dynamodb/v1beta1/resourcepolicy.yaml"

repo: crossplane-contrib/provider-upjet-aws


text:
Unintended deletion of CRDs causes cascaded deletion of all CRs

What problem are you facing?
If a CRD gets a deletion request, it cascades to all CRs and deletion is completed when there is no instance anymore. https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiextensions-apiserver/pkg/controller/finalizer/crd_finalizer.go#L55
However, deleting a CRD by accident is just too easy. A bug in controllers, unexpected behavior of tiller or unexpected garbage collection by Kubernetes can cause a deletion request to be made on CRD. We need to make sure that the deletion process of CRs doesn't start without explicit intent. This is especially more critical for infrastructure custom resources where almost all of them are stateful and recreation may not be possible with the full state.
Example; https://github.com/crossplaneio/crossplane/issues/895

How could Crossplane help solve your problem?
Instead of just checking deletionTimestamp, we can have a constant annotation like crossplane.io/explicit-deletion to check whether the entity who is deleting the resource can confirm its intent. It's easy to have controllers to put that annotation before the Delete call but if a user tries to delete a managed resource, it'd be a bit more work for them to put an annotation and to know that they need to put an annotation. Though this suggestion takes some amount of automation.
Another solution could be to put a finalizer to all CRDs that a StackInstall or ClusterStackInstall registers. Only entity who removes that finalizer would be the stack manager so that we lower the possibility of unexpected deletion to be cascaded to all CRs. I personally like this pattern more but it'd be a little bit cumbersome to integrate this into our CRD generation flow.

It does not seem like the issue here - the blast radius of CRD deletion - is something we should try to solve in Crossplane. If this is a problem for Crossplane, surely it's a problem for any project that uses Kubernetes. Perhaps this should be raised and discussed upstream (if it has not already)?
If I follow correctly the proposed solution seems little broader than the problem, in that it seems to be suggesting that our controllers should require more than the presence of the deletion timestamp in order to process any delete, not just cascading deletes due to CRD removal. I'm also wary about diverging from typical Kubernetes behaviour here, and would suggest discussing this upstream if we really think it's too easy to delete Kubernetes resources in general, or that there should be a class of Kubernetes resource that is extra difficult to delete.

The second suggestion sounded more appealing to me but I just tested it by putting an arbitrary finalizer to CRD manually and see whether the CR instance will be deleted and they did. Apparently, the cleanup logic only checks whether there is a deletion timestamp and its own specific finalizer is in place https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiextensions-apiserver/pkg/controller/finalizer/crd_finalizer.go#L116
The first proposal is indeed divergence from Kubernetes patterns and I don't like it very much, too.
I agree that it's probably best to fix this in upstream. Nevertheless, I feel we should somehow harden it.

Cross linking to this relevant upstream issue - https://github.com/kubernetes/kubernetes/issues/10179.

authors: muvaf negz

repo: crossplaneio/crossplane


text:
small issue downloading the .net runtime

when the runtime is not found the link to download it points to the .net runtime when it really needs the asp.net core runtime and desktop runtime.
I installed booth then it worked. thanks.

Hello and welcome!
The plan down the road is to eventually have a full fledged installer that will fetch the appropriate package, as well as fixing the old link for the guys who hate installers. We will get there someday!

authors: crowbarmaster pepepaco

repo: crowbarmaster/BedrockManagementService


text:
Add support for passbolt

https://www.passbolt.com/
Finally, a password manager built for organizations that take their security and privacy seriously. Passbolt is trusted by 15 000 of them worldwide, including F500 companies, the defense industry, universities, startups and many others.
I havent tested it yet but I believe we could detect alot of bruteforcing.

Had a brief look at this, so looks like all the authentication is done client side in the addon, the server logs never show any authentication logs that i can see.

Thank you for checking. I'll close for now.

authors: LaurenceJJones LePresidente

repo: crowdsecurity/hub


text:
Delivery Needed map should display all Airtable records with Delivery Needed status.

Should be merged after/with https://github.com/crownheightsaid/mutual-aid-app/issues/158
Summary
Delivery Needed map should display all Airtable records with Delivery Needed status. Currently, it filters for requests that have been posted to Slack only. We used to need the Slack post as that was the only way to claim a delivery. However, with SMS pickup, this is no longer a requirement.
Note: SMS pickup is still hidden behind the sms_pickup=true URL param, so this work should only be merged after SMS pickup is fully launched to all delivery volunteers.
Requirements:

remove this filter
update UI to handle cases where there is no corresponding Slack post. We link out to Slack in a couple of places in the UI:

In the table, the delivery code:

On the popup, the name of the neighbor

Where
The place where we filter out for Slack-posted requests lives here: https://github.com/crownheightsaid/mutual-aid-app/blob/3059c228af9fb7851356cd77bfd30f8c11443ab3/src/lib/airtable/tables/requests.js#L87
Bonus
Write some tests for the above changes in airtable/tables/requests.js.

completed with #165

repo: crownheightsaid/mutual-aid-app


text:
Update checker is completely non functional

On launch the script asks if you would like to check for updates, if you press yes it says an update is found and you can press yes to update! Except there isnt an update. I had my ethernet cable unplugged from my dock. After wondering why everything else wasnt working but finding the issue was hardware, I replicated the situation to test the update checker and sure enough the update script defaults to "an update is found" even when there is no internet connection.
If the update script is non functional then why is there the two button press dialogs necessary to launch Fusion 360. I would personally prefer an update.sh file to use in case anything stops working, OR a part of the launch script that checks for updates in the background and notifies if there is an update, keeping the time to launch Fusion minimal.
The launch experience should be as similar to using it natively as possible, just launch it from your DE, fusion splash screen, (update notification if necessary), then software opens, no additional interaction needed.

#413

authors: cryinkfly spusuf


text:
Update location card implementations

Updates all currently implemented locations.
Converts implementations to use the cost and/or target API.
Makes sure the ability can only trigger or initiate if it would change the game state.
Standardises action labels, prompt titles and chat messages.
Changes actions to use a handler instead of method, where needed.
Changes var into let where possible.
Invokes game.transferGold() instead of two times invoking game.addGold().

There's some conflicts here that need resolving

Github could use a feature alerting PR owners of when this happens.

Or I could just be more helpful and point it out sooner :)

authors: DukeTax cryogen

repo: cryogen/throneteki


text:
Implement fast pairing according to SFC specification

(This issue has been imported from the Gitlab repository because it seems to not have been addressed yet)
Original Text (Issue 70)
To get really fast pairings for various hardware architectures, the pbc Java implementation is not appropriate. This issue requests the integration of fast hardware specific pairings into the new interface. The arithmetic upto the pairing computation is provided as a library that is called from within java.
Comment by Jan Bobolz
New idea is to handle group operations, exponentiations, and pairings completely inside a C library (which [at]peterg writes). We ([at]mirkoj ?!) then write a Java (JNI) wrapper that calls the C library for group operations and exposes the Group/GroupElement interface.
The main advantage is that we only need to implement group operations once (namely, in C), and that we do not have to implement a semantic-preserving mapping of the C-representation of elliptiv curve points and their corresponding Java object hierarchy (which turns out to be a lot of code and which probably causes a lot of unnecessary runtime overhead).
So the C code produces points as simple structs and just hands the bytes in the struct's allocated memory to Java. Java would only get to see"black box" bit strings. Java can then hand back that bit string, which the C code can directly interpret as the appropriate struct.
Comment by Peter Günther
The pairing that shall be implemented as part of this issue is the (optimal) ate pairing on BN curves. Details pending.
Comment by Peter Günther
issure is handled in branch feature/fast_pairing_sfc
Comment by Jan Bobolz
One of the tasks left here is to integrate it into the build process.
I propose to make the native implementation (Java and C side) its own project so that people can build upb_pbc without any platform-dependent worries. (However, I'm not sure yet how to elegantly do the decision whether to instantiate the java or the native pairing.)
For future reference, I found

http://www.tricoder.net/blog/?p=197 which seems pretty clean.
https://www.humboldt.co.uk/wrapping-a-native-library-with-maven/ which may be more appropriate as Peter has already supplied a make file.

I guess this ended up being handled using the approach of wrapping existing fast implementations such as Mcl?

repo: cryptimeleon/math


text:
Use AES/createHash directly

See https://github.com/crypto-browserify/browserify-aes/issues/19 for more information.
Essentially this change will dramatically reduce the number of dependencies this package will pull in, making browserify builds much smaller.

I understand the createHash part, but not AES? scryptsy uses the aes package directly, this was before crypto-browserify supported aes.

scryptsy uses the aes package directly, this was before crypto-browserify supported aes.

What do you mean?  scryptsy doesn't use AES at all?

this was before crypto-browserify supported aes.

This package uses crypto now and its AES implementation (aka, browserify-aes).
There is no difference except that we "drop" the rest of the unused code.

What do you mean? scryptsy doesn't use AES at all?

Right. I meant bip38.
Let's start with this...
Why drop crypto at all in place of createHash? I mean, I understand it's akin to the using the inherits package over require('util').inherits... but is it worth it in this case?
Pros:

Probable decreased payload size. But by how much? I'd like this quantified (especially with using tools like Google Closure)

Cons:

Another dependency. I do prefer the simplicity of just requiring crypto. [The irony doesn't escape me given the nature of mission of this organization =) ] Browser side, I like browserify just handling the dependencies.
Node.js side, it's not as clear to the reader of the code that it's actually using Node.js crypto. (Maybe grasping at straws here).

I'm not opposed to this, just don't want to make a rash decision.

Probable decreased payload size. But by how much? I'd like this quantified (especially with using tools like Google Closure)

In Bitcoinjs-lib, we saw a 330kb decrease in size.  I'm looking to save a similar amount once this package is updated in my applications.
I don't personally use a tool like Google Closure,  but even if I did,  I see no reason why we can't have both.

Another dependency. I do prefer the simplicity of just requiring crypto. [The irony doesn't escape me given the nature and mission of cryptocoinjs =) ] Browser side, I like browserify just handling the dependencies.

Simple in that we know about crypto already,  but crypto has many different facets in its API,  and I don't know which version of crypto I'm using,  is it node 0.12?  Node 0.10? Iojs? All these versions,  all have different subleties in their API.
I want semver for my crypto,  and using npm is one way to do that very easily.

Node.js side, it's not as clear to the reader of the code that it's actually using Node.js crypto. (Maybe grasping at straws here).

To the reader of the package, its impossible to know a lot of the assumptions,  but at least with a package version and a package to go look up,  I can see for myself and have some safety around what will happen.
With require("crypto"),  I just have to hope we're using the same standard library.

I don't personally use a tool like Google Closure, but even if I did, I see no reason why we can't have both.

It's not that we can't have both, I'm just trying to explore whether it's worth it or not.

I want semver for my crypto, and using npm is one way to do that very easily.

createHash isn't semver though for the Node.js crypto.createHash.

With require("crypto"), I just have to hope we're using the same standard library.

But it's not just require('crypto'), it's `require('crypto').createHash'.
I have actually put thought into this, while I'm leaning more towards the idea, I'm still not 100% just yet.

createHash isn't semver though for the Node.js crypto.createHash.

True.  That is a bogus benefit.   I guess ideally though we could enforce that compatibility better at the one point though, because a change in the API would fire the specific tests for that in createHash,  and we could choose to either upgrade or enforce a set API.
Where as, it could have unintended side effects if its deep in your stack.
But you're right,  that isn't entirely true.

Closing,  was implemented in https://github.com/cryptocoinjs/bip38/commit/eaf15b7d0df16bdaa06878c2264e5b4b0b063dd0

authors: dcousens jprichardson


text:
Support merging doc comments of macro generated items

Say you have a macro that defines something that is displayed in the generated API docs, a method for example:
macro gen_method(name)
  # Comment added via macro
  def {{name.id}}
  end
end

# Comment on macro call
gen_method foo

In this example the doc comments on the method definition and macro invocation are mutually exclusive; with the docs added within the macro itself taking precedence:

This is ultimately due to this logic: https://github.com/crystal-lang/crystal/blob/123de814fdbaa1256044a798b0272c9af19e7cca/src/compiler/crystal/semantic/semantic_visitor.cr#L382
I propose that there should be a way to support both, such that you can have macro generated docs, but then provide additional documentation when calling said macro.
A naive approach could be just do something like node.doc = "#{@doc}\n\n#{node.doc}".lstrip. A more robust approach could be the introduction of a new doc directive that will gsub the invocation docs where ever that token is located in the macro definition docs. We can't reuse :inherit: due to that probably causing conflicts if the method generated via the macro happens to override the same method in a parent type.

Whould it be possible to apply the doc comment concatenation inside the macro?

It would be a possible workaround yea, just wouldn't be all that natural from the end users perspective tho.

If we had access to a macro's caller context, the call site could potentially look exactly as it does in your example.

Even if we had this, wouldn't it be blocked by the outcome of https://github.com/crystal-lang/crystal/issues/7273? Which last I read thru was mostly :-1:.

The macro's caller context would be something new as well yea? Were you thinking that would be a new meta var like @caller that is a Call of the call that invoked the macro yea? Is that something that would be specific to macros, or could work on normal methods too?

Yeah, something like that. I wasn't thinking about a specific implementation though, just the general concept.
It would be limited to macros because defs are in general instantiated only once and cannot be traced back to specific callers at compile time. The equivalent at runtime is the caller method which is based on the stack trace.

self.doc.gsub("\n", "\n# ") should do the same transformation much simpler.
I would argue this should probably happen in the calling macro code though. {{ @caller.docs.gsub(/\n/, "\n# ").id }}

This was resolved via a combination of https://github.com/crystal-lang/crystal/pull/14048 and https://github.com/crystal-lang/crystal/pull/14050.

repo: crystal-lang/crystal


text:
Update docker image crystallang/crystal to the latest version

The docker image crystallang/crystal at https://hub.docker.com/r/crystallang/crystal/tags/ was last updated to 0.23.1, that was 5 months ago.
Please update it for 0.24.1 and following releases.

I also noticed the Dockerfile in the project root does not use an immutable base-tag, it uses the latest of the project's docker image which could vary greatly between local cache and the remote docker repository. This makes docker builds much less reliable as cache creep occurs over time.
The "release" dockerfile uses an ubuntu base image which is not as problematic, but in my mind the canonical project Dockerfile and the people who use it will suffer from cache creep over time.
For example the docker build fails right now when attempting to build on a clean system with:
git clone https://github.com/crystal-lang/crystal
cd crystal
git checkout 0.24.1
docker build -t crystallang/crystal:0.24.1 .

in the project root.
In the past I greatly reduced this problem by publishing versioned base images to the project's docker repository or ensuring the project's base image was a version-pinned OS image. It also helps to have the CI build artifacts and run tests using docker and to repeat that process at least once daily even when there is no code-change to master. That would allow for incompatible 3rd party library creep to be detected earlier.

Hi there!
Thanks for the reminder. I've just pushed a 0.24.1 tag, and updated the latest one to that.
If you can confirm it's working, we'll close the issue :)
Sorry about the delay!

It's working. Thanks!


text:
Numbered list not rendered correctly in docs when using code block

This is how the current Installation section looks in the generated docs:

1 and 1 instead of 1 and 2.
Even if this is actually in the README:
## Installation

1. Add the dependency to your `shard.yml`:
```yaml
dependencies:
  library:
    github: user/library
```
2. Run `shards install`

That's probably a bug with the markdown renderer

The bug is very likely here: parser.cr:253.

Another solution is to stop investing time for this in the stdlib and use e.g. markd

Let's just ignore the error for now and change the list to be unordered. A fix can be delayed until we have some final decision on how to provide proper markdown support to the compiler. Or maybe we don't even need that if the compiler just outputs plain markdown and an external doc generator renderes it to HTML or whatever format.

There are battle tested markdown libraries, that's not a problem if we'd like to go in that direction.

We've been through the logistics of the compiler depending on external shards before and it's not going to happen any time soon.

@bcardiff shouldn't this be rather fixed before releasing 0.27.0?

I'd say not necessarily, the readme is usually read from GitHub, etc. The docs are used for the API (yes, the readme appears there too but someone will have read GitHub before, or having 1., 1. isn't a big deal).

Unfortunately now after #7118, the Installation section is rendered even buggier:

## Installation

1. Add the dependency to your `shard.yml`:

   ```yaml
   dependencies:
     library:
       github: user/library
   ```

2. Run `shards install`

IMHO the only sane way to proceed is to invest in a proper markdown implementation. I don't think it makes sense apply makeshift patches to the Markdown library every now and then when a new flaw is detected. This continuously requires attention and effort.
The stdlib Markdown implementation is very rudimentary and flawed. It's safe to assume it would require a complete rewrite to push it to an acceptable Markdown support level.
I proposed #4613 a long time ago, but it has been sidetracked from the main issue to discussions about the organization of the compiler code etc.. So it's still inconclusive and lacks any path to action.
Until there is any progress in that issue, I think it's best to simply avoid any flaws in the Markdown parser. I.e. change ordered list to unordered and revert #7118.


text:
Backtick and classes

This is perhaps more of an undocumented corner of the language rather than a bug. The compiler allows backtick to be overloaded, and notes that fact in error messages although it isn't otherwise documented:
Error: expecting any of these tokens: IDENT, CONST, `, <<, <, <=, ==, ===, !=, =~, !~, >>, >, >=, +, -, *, /, //, !, ~, %, &, |, ^, **, [], []?, []=, <=>, &+, &-, &*, &** (not '.')

But it doesn't do anything sensible with it. Calls to backtick in this example still go to the top-level one.
class A
  def `(**double_splat)
    p double_splat
  end

  def call
    `testing...`
  end
end

There's a mistake. Double splat will indeed not match positional args that the backticks use.
class A
  def `(*double_splat)
    p double_splat
  end

  def call
    `testing...`
  end
end

A.new.call

This works

TIL you can use backtick defined on a type

OK, this now works the way I wish, and closing the bug.
class A
  def `(*splat)
    p splat
  end

  def interpret
    with self yield
  end
end

a = A.new
a.interpret do
  `testing...`
end

Note that backtick isn't supposed to be called as an instance method. This will most definitely change in the future so I wouldn't rely on this behavior.
The only reason why backtick is implemented as a method is so that we can change the implementation with Crystal itself

It's not a bad feature from an expressiveness perspective, for example one can use it to access a shell on a remote server rather than the local one, or another interpretive language than the shell. Since it's free to do so, I suggest that it be kept as it is.

authors: BrucePerens asterite oprypin


text:
Add UUID v7

Part of #14288. This PR doesn't implement all of the requested UUID versions, but v7 is gaining in popularity for its ability to sort UUID values chronologically and RFC 9562 was published last month.
It's notable that RFC 4122 has been obsoleted via RFC 9562, so I included an alias for the new RFC in the Variant enum.
Spec: https://www.rfc-editor.org/rfc/rfc9562#name-uuid-version-7

the spec is weird as the format has optional non-random parts to increase precision + counter 😕
I understand the more precise, the better for database indexes, but less randomness means more chances for collisions, so we should give some control over it.
Do you think we could specify the precision (second vs millisecond), and later a counter to control this aspect?

I hear you, reducing entropy honestly sounds scary. I've given it the maximum randomness and minimum monotonicity the spec allows for. Millisecond precision is prescribed by the spec.
In thinking about the failure modes of a UUID collision (admittedly from my own perspective, which mostly revolves around using them as DB primary keys), the most likely scenario would be an exception due to INSERTing 2 rows into a table with the same primary key. With a keyspace of 2**74 (roughly 1.9e22) values per millisecond, this would happen infrequently enough that a simple retry should work.
Since there are other UUID solutions that provide more randomness and less precision, if that's what you need, I'd argue that a v7 UUID is not.

Sorry, I misread the spec, the timestamp is in milliseconds :+1:

Feel free to ignore the above suggestions, they're just nitpicks. But WASM32 doesn't like the call to sleep in the spec. I think the eventloop isn't implemented.

Looks like pending! also doesn't work on WASM? 🤔

nice, I didn't know this existed.  I will be switching a few projects to V7.

Dang, didn't realize that. We can use pending_wasm32 instead.

authors: jgaskins jkthorne straight-shoota ysbaddaden


text:
Switches Darwin to arc4random

Based on discussions on #6340.

Performance improvements
Works in chroot
No File Descriptors needed

Note: The same could also be done for FreeBSD.

@RX14  - Based on my current research.

arc4random introduced in macOS 10.6 (2009)

arc4random_buf introduced in macOS 10.7 (2011)

arc4random is reseeded with getentropy, not /dev/[u]random

The documentation explicitly states to use arc4random as it is safe in chroot.

man arc4random:

They can be called in almost all environments, including chroot(2), and their use is encouraged over all other standard library functions for random numbers.

arc4random is based on an AES cipher as of macOS 10.12 (2016)

With regards to whether you should use arc4random or /dev/urandom/. The documentation is explicit. You should always use arc4random.

man random:

Applications requiring cryptographic quality randomness should use arc4random(3).

man urandom:

The same random data is also available from getentropy(2).  Using the getentropy(2) system call interface will provide resiliency to file descriptor exhaustion, chroot, or sandboxing which can make /dev/random unavailable. Additionally, the arc4random(3) API provides a fast userspace random number generator built on the random data source and is preferred over directly accessing the system's random device.

man getentropy:

However, it should be noted that getentropy() is primarily intended for use in the construction and seeding of userspace PRNGs like arc4random(3) [...].

@RX14 - You can trust whoever you like. I don't trust the libsodium guys. I happen to be of the perspective everyone should just duplicate OpenBSD's arc4random and keep it up to date. That isn't the case though. What is the case is macOS has /dev/urandom and their implementation of arc4random.
All the official documentation says use arc4random, as does the preponderance of unofficial documentation/discussions. arc4random is a better choice then /dev/urandom on macOS.

And until recently the linux manpages said using urandom wasn't cryptocraphically secure. Which was against the advice of almost every cryptographer out there.
At the end of the day, this is a performance problem, and if there's any conflict at all, i'd rather stick with what we know works and is secure.

So, there are two main problems with arc4random

it is userspace (so some side-channel attacks can be possible, but this possibility is debatable). There are controversial opinions about it.
it can use RC4 (that is nonuniform and generally broken) on old systems.
Checking the source confirms, that macOS 10.12 (Sep 20, 2016) uses AES and 10.11 uses (modified but still unreliable) RC4 seeding it from /dev/random.
https://opensource.apple.com/source/Libc/Libc-1158.1.2/gen/FreeBSD/arc4random.c.auto.html
https://opensource.apple.com/source/Libc/Libc-1081.1.3/gen/FreeBSD/arc4random.c.auto.html

so even if we ignore first point, arc4random shouldn't be used on OSX10.11 and older.
On the other hand, getentropy was introduced in macOS 10.12 (Sep 20, 2016) and is a (strictly) better solution then /dev/urandom - it yields same data (not a userspace prng) and is safer because doesn't depends on file descriptors. So if a getentropy is available - it is a modern OSX and we can use either arc4random or getentropy (depending on the opinion about first point).
On the other other hand, it a libsodium issue cited before tells that getentropy uses \dev\urandom. I think the additional research is needed on this, man page isn't a proof.
From what Apple opensourced
if (getentropy(buf, size) == 0) {
		return;
	}
	// The above should never fail, but we'll try /dev/random anyway

so it in theory can fallback to reading from /dev/random, but does it possible in practice depends from can getentropy fail. I wasn't able to find getentropy source to check.

And even if arc4random is secure on 10.12, are all the runtime checks and complexity (read: vulnerabilities) worth it? Just for some performance?

Closing. We can't trust ourselves on security topics. We need strong guarantees from cryptographers that something is safe and correct.
Sadly, we don't have enough guarantees that arc4random is cryptographically correct on macOS. The only guarantee we have is that it was very bad prior to macOS 10.12 :disappointed:

authors: RX14 chris-huxtable konovod ysbaddaden


text:
Attempt to install reva-sharees branch of owncloud/core

The oc-sciencemesh app relies on functionality from https://github.com/pondersource/core/tree/reva-sharees .
The current Dockerfile for owncloud installs owncloud/core from a tar file, we'll probably have to somehow compile from source in the Dockerfile.

https://doc.owncloud.com/server/next/developer_manual/general/devenv.html#install-dependencies-on-ubuntu-16-0418-04

@navid-dada I think you were very close, the build works now with that tiny edit.
Testing it on the VPS now


text:
[WIP] New OIDC ESCAPE auth driver.

This allows for authentication via the ESCAPE IAM service.
The IAM account group must be mapped to a reva user in a json file where the IAM group name is linked to the reva user through the username.
Example of this file:
[
	{
		"oidc_issuer": "http://iam-login-service:8080/",
		"oidc_group": "Analysis",
		"username": "einstein"
	},
	{
		"oidc_issuer": "http://iam-login-service:8080/",
		"oidc_group": "Sciencemesh",
		"username": "marie"
	}
]

For authentication you must have a valid IAM access token. As an example we can do a login using an access token obtained from the IAM service (use a token tool) and use that as the secret. Leave username empty and use the token as password:
/go/src/github/cs3org/reva # ./cmd/reva/reva -insecure login oidcmapping
username:
password: OK
/go/src/github/cs3org/reva # ./cmd/reva/reva -insecure whoami
id:<idp:"reva-oidc-escape:20080" opaque_id:"4c510ada-c86b-4815-8820-42cdf82c3d51" > username:"einstein" mail:"test-100@test.org" mail_verified:true display_name:"Test-100 User" groups:"sailing-lovers" groups:"violin-haters" groups:"physics-lovers"

Here the IAM 'Test-100 User' test user is mapped by one of its groups to the reva 'einstein' test user. From hereon you can start sharing etc. as usual.
Regarding mapping:
The IAM user may be a member of multiple groups. If more than one groups are mapped each to a different reva user authentication can not take place because we currently have no mechanism to decide in that case which reva user to use.

Concerning merger of oidc & oidcmapping
I want have something clear: if mapping is unsuccessful, either because no mapping is found or a mapping file is not configured, should we then default to 'bare' oidc ?
Same for errors: if a mapping file IS configured but parsing it fails (file not found or parsing error), should authentication fail or should we default to 'bare' oidc ?

I want have something clear: if mapping is unsuccessful, either because no mapping is found or a mapping file is not configured, should we then default to 'bare' oidc ?

This to me is a "user" condition and we should default to bare OIDC.

if a mapping file IS configured but parsing it fails (file not found or parsing error), should authentication fail or should we default to 'bare' oidc ?

This instead is a "service" error, i.e. caused by misconfiguration by the service manager. In that case I would actually fail the init phase so that revad cannot even start.
Makes sense?

Makes sense?

Yes

authors: glpatcern redblom


text:
AttributeError: module 'cupy' has no attribute 'util'

When running inference.py:
Traceback (most recent call last):
  File "/home/ubuntu/github/CDVD-TSP/code/model/flow_pwc.py", line 10, in <module>
    from model import correlation
  File "/home/ubuntu/github/CDVD-TSP/code/model/correlation.py", line 282, in <module>
    @cupy.util.memoize(for_each_device=True)
  File "/home/ubuntu/anaconda3/envs/deblur37/lib/python3.7/site-packages/cupy/__init__.py", line 875, in __getattr__
    f"module 'cupy' has no attribute {name!r}")
AttributeError: module 'cupy' has no attribute 'util'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "inference.py", line 10, in <module>
    from model.cdvd_tsp import CDVD_TSP
  File "/home/ubuntu/github/CDVD-TSP/code/model/cdvd_tsp.py", line 4, in <module>
    from model import flow_pwc
  File "/home/ubuntu/github/CDVD-TSP/code/model/flow_pwc.py", line 13, in <module>
    import correlation  # you should consider upgrading python
ModuleNotFoundError: No module named 'correlation'

This error is related to the version of the package "cupy".
You can fix this error by modifying line282 in the file "./code/model/correlation.py":
"@cupy.util.memoize(for_each_device=True)" -> "@cupy.memoize(for_each_device=True)"

authors: csbhr jpiabrantes

repo: csbhr/CDVD-TSP


text:
Support graceful shutdown of worker

When root context is canceled, stop polling for new work, complete in-progress work, and then exit.
Have some kind of timeout.

In the future might add a timeout for waiting for activities to finish, but for now still stop polling and wait for in-progress activities to finish before exiting.

repo: cschleiden/go-dt


text:
Tests

Adds a test to make sure the application's Firebase logic properly gets an entry from the DB. To do this, we now have to pass in an instance of Firebase to the tree so it could be decoupled from the app.js and index.html.

[ ] Does the PR description accurately reflect the changes made?
[ ] Do the commit messages accurately reflect the changes made?
[ ] Is the changelist for this pull request under ~200 lines? (Excepting automatically generated code and package installations)
[ ] Does the code follow the coding style guidelines that we have set up?
[ ] Does the coder include unit tests for his functions?
[ ] Does the QA who reviews the code include his unit tests for all the functions?
[ ] Is there a documentation in place if the functions is related to how users build, test, interact with, or release code?

:tada: This PR is included in version 1.2.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

authors: JackTuxh dkshibat


text:
throw new errors.Error('ERR_UNKNOWN_SIGNAL', signal);

I have run this project using npm run dev, the app ran fine, but I also got this output:

[WARN] No ENV file found
03:14:29 electron.1   |  starting electron
03:14:30 react.1      |  > electron-with-create-react-app@0.1.0 start C:\Users\G\Downloads\electron-with-create-react-app-master
03:14:30 react.1      |  > react-scripts start
03:14:34 react.1      |  Something is already running on port 3000.
[DONE] Killing all processes with signal  null
internal/util.js:186
throw new errors.Error('ERR_UNKNOWN_SIGNAL', signal);
^
Error [ERR_UNKNOWN_SIGNAL]: Unknown signal: null
at convertToValidSignal (internal/util.js:186:9)
at ChildProcess.kill (internal/child_process.js:379:5)
at EventEmitter. (C:\Users\G\Downloads\electron-with-create-react-app-master\node_modules\foreman\lib\proc.js:54:11)
at emitOne (events.js:121:20)
at EventEmitter.emit (events.js:211:7)
at ChildProcess. (C:\Users\G\Downloads\electron-with-create-react-app-master\node_modules\foreman\lib\proc.js:50:13)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! electron-with-create-react-app@0.1.0 dev: nf start -p 3000
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the electron-with-create-react-app@0.1.0 dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\G\AppData\Roaming\npm-cache_logs\2018-04-28T23_14_34_096Z-debug.log

Is this normal?

It isn't normal. Do you have something else running on port 3000? You could edit package.json and change the port to something else to see if you still get the error.

@csepulv No there is nothing on port 3000.
I noticed when it does it. The first time I run the app it doesn't produce this error.
As soon as I closed the app using 'x' button, I got this message.
And then each time I run app I see it now (the app runs though, just the message is there).
ps. I am running on windows.

npm run dev runs a few processes. I wouldn't stop by closing/exiting the window, but press Cntrl-C in your command line (terminal) to kill all the processes. It seems the window exit only kills the electron process, but leaves the react dev server running on port 3000.
Task Manager may let you find/kill the runaway process, but if you use Cntrl-C it should work.
In production, with a packaged and installed app, closing the window would be fine as you wouldn't have the react/webpack dev server running.

Not exactly the same issue but I had the same error (when starting tho) and it was simply because I had changed the path to the electron-wait-react path and didn't update the Procfile, might be useful for posterity.
Hope you have found what was bothering you tho :pray:

authors: csepulv gabriel-dehan giorgim

repo: csepulv/electron-with-create-react-app


text:
Update KlipTok.fr.json

add new translations from playlists

Looks like you added the French translation for Feedback into the English file.  Can you swap that back to the French file?

oups, sorry...
i just fixed it
Le jeu. 28 avr. 2022, à 14 h 51, Jeffrey T. Fritz @.***>
a écrit :

Looks like you added the French translation for Feedback into the English
file. Can you swap that back to the French file?
—
Reply to this email directly, view it on GitHub
https://github.com/csharpfritz/KlipTok.Translations/pull/144#issuecomment-1112548455,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXWUM3FZ5HUPMLYIRSKMNTVHLM3ZANCNFSM5UTMMCVA
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Martin Labelle
@.***
http://www.martinlabelle.com

Yea!  Looks good...  I'll get this deployed in 5 minutes

authors: bestter csharpfritz


text:
Fix invalid output for template string

Fixes #100

Good job!

Fixed in cst@0.0.28

Can you push tags? The latest is 0.0.26 on github

Done :)

authors: hzoo ikokostya mdevils

repo: cst/cst


text:
How to reset the canvas?

I experimented on the plunker , I made clear function to reset to initial state:
clear() {       this.data1 = {};     }
the image cropper data resets but the canvas content is still there.

The cropper object has a reset function available

cropper object has not reset by using this function
clear() { this.data1 = {}; }

plz help me to  Reset canvas in anotherway

I have the same issue. I am not using the cropper as a component, just using it directly inside my other component, so I don't have the whole cropper object to reset. How can I clear the canvas without using cropper1.reset()?

I found an answer to this (to reset the canvas. you already know how to clear the cropped data):
In the html use #cropper like this:
<img-cropper #cropper [image]="data1" [settings]="cropperSettings" (onCrop)="cropped($event)">
In component.ts include these lines:
export class myComponent implements OnInit {
@ViewChild('cropper', undefined) cropper:ImageCropperComponent;
constructor () {}
clear () {
this.cropper.reset();
}
}

I am using the reset function as well as the resizeCanvas function, but the cropper size isn't changing. Anyone find how to do this?

thanks @savita-turner

authors: hank-ehly josephserrano15 savita-turner venkatasairamu vistajess


text:
Add solo shuffle toggle

Fixes #2

Thanks, merged.

authors: AlexanderRousseeuw csutcliff

repo: csutcliff/SimpleCombatLogger

license: Unlicense


text:
use a robust fitting in timing_parameters

Right now the computation, using np.polyfit() of the timing axis in timing_parameters can be quite biased if there are outliers included (some noise included after cleaning, which happens relatively often).  It was suggested here  https://github.com/cta-observatory/ctapipe/issues/602#issuecomment-350823139 that we should use a robust fitting routine (e.g. one that is not strongly affected by outliers), and this is already implenmented in MARS and EventDisplay.
Here is a comparison of the results of fitting a linear function  with polyfit to several robust methods included in SciPy:
    N = 15
    x = np.arange(N)
    y = 3*x+2 + np.random.uniform(5.0,size=N)-2.5

    # add some outliers
    y[outlier_pos] = 3*x[4]+2 + outlier_level

    pslope, pintercept = np.polyfit(x,y,1)
    tslope, tintercept, err_slope_low, err_slope_high= stats.theilslopes(y,x=x)
    sslope, sintercept, = stats.siegelslopes(y,x=x, method='hierarchical')
    ssslope, ssintercept, = stats.siegelslopes(y,x=x, method='separate')

I suggest we replace polyfit  with scipy.stats.siegelslopes to get a better fit.  The only problem is that these functions do not return error estimates, so those must be computed separately.
This is also mentioned in #1215

The only problem is that these functions do not return error estimates, so those must be computed separately.

In think we could probably also live without these here. Or just a simple rmse (which again would be affected by outliers).

yes, so far I don't think we use the error estimates, so could just drop them.

I would like to reopen this for further discussion, as the currently used algorithm turned out to be forbiddingly slow.
@GernotMaier @moralejo Could you comment on which algorithms are used in EventDisplay and Mars for this?
I have several ideas what kind of algorithms could be used here and how one could implement them in a fast way.
I think this should be a configurable component to allow for comparisons between different algorithms.

Eventdisplay uses the 'rob' option from TGraph::Fit():
https://root.cern.ch/doc/master/classTGraph.html#aa978c8ee0162e661eae795f6f3a35589

Thanks, this seems to be this method: https://en.wikipedia.org/wiki/Least_trimmed_squares

MARS uses also ROOT's "robust" fit option. We use "ROB=0.85", which means that at most 15% of the points (if found to be outliers) are discarded.
Note: by default ROOT requires a minimum of (npoints+nparams+1)/2  of the original points to be used in the final fit.

Okay, this indeed sounds like the least trimmed squares algorithm, I'll look into it.

which means that at most 15% of the points (if found to be outliers) are discarded.

Minor nitpick, but if I understood the algorithm correctly, it always uses the 85 % points with the lowest squared error, it performs no real outlier detection.

@maxnoe and @Karl Kosack For outlier robust fitting I have successfully used the RANSAC algorithm in the past as well. It is one of the standard algorithms for feature point matching in computer vision. There is an implementation available in scikit-learn: https://scikit-learn.org/stable/auto_examples/linear_model/plot_ransac.html.  Maybe it's worth a try...

For now we go with the same approach as the ROOT base frameworks, which should also improve comparability of the DL1 stage.
Implemented in #1419.
I am closing this for now again. But a more comparative study should be done including e.g. RANSAC and checking both computation performance and physics performance.

authors: GernotMaier MaxNoe adonath kosack moralejo

repo: cta-observatory/ctapipe


text:
Instrument module:  Just store camera geometries by camera id, not telescope id

This will drastically reduce time and memory usage.
Give the telescope table a column camera id and then just create tables for each camera, not for each telescope.

I don't think so: only in the MC the cameras are identical. In reality, each camera will be different.
For the MC production, already now some of the cameras are different (as e.g. the quantum efficiency is the base value + a random value calculated using the expected uncertainty)

This bring up a point, however - the reason we break down the instrument description into multiple sub-classes/tables is for exactly this use case.
The CameraGeometry is probably fixed for all cameras (at least for a single camera version and type), but other parts of the instrument model change (like the QE, etc) and those should be in a different object/table.  That was the point of the ObsConfig data model : separate things that change from things that don't change often, and group things that change roughly at the same time, so they can be identified by a unique key.
Max is correct: we should be able to load a single CameraGeometryDescription per type, but still load a different CameraDetectorDescription (or whatever you want to call it) that contains the QE's, etc per camera.  In an event display you only need the fixed geometry, but in the MC you need all the info.
That implies that you need to break up the CameraDescription into at least these two pieces

Yes, I just meant Geometry not values that might be different for each camera.

authors: GernotMaier MaxNoe kosack


text:
ImPACT updates

Fairly major refactoring of the ImPACT code adding several new features to the code:

Optional addition of fit priors
Selection of minimisation algorithm
Helper functions for drawing likelihood surface

several ImPACT tests are still failing

OK tests should be fixed now. I will also add some (small) ImPACT template file to the ctapipe extras  repo today so we can properly run all tests.

The tests pass, but the documentation has a bug in it somewhere:
Warning, treated as error:
/home/travis/build/cta-observatory/ctapipe/docs/reco/ImPACT.rst:48: (WARNING/2) Title underline too short.
Calculating Image Likelihood
++++++++++++++++++++++

There are still doc errors - I suggest running make doc (or cd docs; make html) to generate the docs locally, and fix the errors  before committing - it seems the Travis build is configured to stop on the first error, rather than show all of them, so using it to debug will be tedious.
You may need to install the sphinx packages listed in environment.yml in the top-level directory to build the docs. Specifically:

sphinx
sphinx_rtd_theme
sphinx-automodapi

Haha yes this has been driving may crazy, will try checking locally.

authors: ParsonsRD kosack


text:
Update README.md

Read more link is broken, I think this is the best replacement.

thanks king!

authors: ChrisChinchilla ctjlewis

repo: ctjlewis/react-spotify-embed


text:
Options System

[ ] Allow override of working only on localhost
[ ] Some method of authentication?
[ ] Allow customisation of configuration items which are redacted.
[ ] Override endpoint URL. Currently hard-coded to use /options.

These will probably need to be split out into individual issues.

Sent a PR for configuration through options.
For authentication/authorization, I would consider the middleware to go through endpoint routing in 3.0. That way, we would get that mostly for free.
For the redacted-customization, maybe the options could include some callback that gets called and can redact entries.

For the redacted-customization, maybe the options could include some callback that gets called and can redact entries.

Either this, or perhaps you implement and register an IConfigRedacterererer, and we pick up all of them from DI and run a known method on them?

Or maybe support both so you can have different redacterererererers depending on which config explorer you refer to but still allow it to be configured through DI.
E.g. ASP.NET Core authentication has this Type EventsType property that is used to auto-provide an events type if the object Events property is not set. We could do the same and retrieve it through DI if the RedacterererererererererType is specified.
Not sure if all this is worth the effort though. Chances are, people don’t need that much configuration.

I don't think we need an IRedacterererere we now get auth for endpoint routing. Closing!

authors: ctolkien poke

repo: ctolkien/AspNetOptionsExplorer


text:
Impossible to use already cracked passwords by crackerhack

I just noticed that when you create a session and you have to choose the wordlist, if the user clicks on the "Create wordlist from already cracked passwords" button, crackjacker does not take in consideration the pwd_cracked.dict or hashes.cracked file from the previous session. Instead, it creates an empty "pwd_wordlist.dict" file. Once the new session is launched, we get an error, which is normal because the wordlist is empty.

it would be nice to be able to insert the cracked passwords with the concerned session id, their hash and their username (if existing) in a common database/table, it would avoid having redundant hash files since the "/files" part reads in one of the files I quoted above (if I'm not saying anything wrong)

repo: ctxis/crackerjack


text:
Add CreateTagInstancesTaskGraphExpandCommand

Added

Added CreateTagInstancesTaskGraphExpandCommand.

Codecov Report

Merging #190 (f6b379d) into master (35ae332) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #190   +/-   ##
=======================================
  Coverage   95.75%   95.75%
=======================================
  Files         110      110
  Lines        1672     1673    +1
  Branches      231      231
=======================================
+ Hits         1601     1602    +1
  Misses         69       69
  Partials        2        2

Flag
Coverage Δ

cuaktask
99.17% <ø> (ø)

iocuak
94.11% <100.00%> (+<0.01%)
:arrow_up:

porygon
98.30% <ø> (ø)

porygon-typeorm
98.67% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...Task/models/cuaktask/TaskGraphExpandCommandType.ts
100.00% <100.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 c4c93c6...f6b379d. Read the comment docs.

authors: codecov-commenter notaphplover

repo: cuaklabs/cuaktask


text:
Have separate conda envs for different executors and clouds

Initial work for #5.
I think it would be useful to standardise the naming of the config and conda env files. Something like {executor-name}_{cloud}, so we'd have:

single-threaded (there's no cloud for this one, so we just drop it, alternatively we could have single-threaded_nocloud or something)
lithops_aws
lithops_gcp

If we wanted more options within a config (e.g. because we wanted to try a different serverless runtime), we could just add more modifiers, e.g. lithops_gcp_cloudrun. But I don't think we need that yet.

Comparing GCP with AWS from yesterday:
$ duckdb benchmark.db
D select name, duration from test_run where name like '%lithops%' and duration is not null;
┌────────────────────────────────────────────────────────────┬────────────────────┐
│                            name                            │      duration      │
│                          varchar                           │       double       │
├────────────────────────────────────────────────────────────┼────────────────────┤
│ test_quadratic_means_xarray[configs/lithops_aws.yaml-50]   │  34.91558289527893 │
│ test_quadratic_means_xarray[configs/lithops_aws.yaml-500]  │ 56.183167934417725 │
│ test_quadratic_means_xarray[configs/lithops_aws.yaml-5000] │  66.49491095542908 │
│ test_quadratic_means_xarray[configs/lithops_gcp.yaml-50]   │  43.74802899360657 │
│ test_quadratic_means_xarray[configs/lithops_gcp.yaml-500]  │   93.0142970085144 │
│ test_quadratic_means_xarray[configs/lithops_gcp.yaml-5000] │ 132.36643505096436 │
└────────────────────────────────────────────────────────────┴────────────────────┘

I've updated this PR so that one runtime (spec) is run per pytest invocation. This works well with a GitHub Actions matrix (as suggested by @TomNicholas here: https://github.com/cubed-dev/cubed-benchmarks/issues/5#issue-2163640415), which I've also included for a single-threaded executor and Lithops on AWS. These are passing: https://github.com/cubed-dev/cubed-benchmarks/actions/runs/8188522733
There's more work to do of course (more benchmarks, merge db files, make config naming consistent, run on GCP, ...), but I think this is at a good point to merge. Any thoughts @TomNicholas?

repo: cubed-dev/cubed-benchmarks


text:
Scroll bounds and scrollBy()

When using scrollBy() the scroll bounds are not respected.  So when I scrollBy(-10,0), the content never stops it just keeps scrolling.  It doesn't respect the bounds like when you scroll with the mouse wheel or scrollbar.
Right now I have to explicitly check if scroller.maxScrollX < scroller.x before each interval.  This works but I would imagine any scrolling action should respect the scroll bounds.

+1

authors: Hugheth benjamingeorge

repo: cubiq/iscroll


text:
Icarus verilog differing from verilator

For the following files, k.futil and k.data, fud e --to dat --through verilog -s verilog.data k.data k.futil works as expected, while fud e --to --dat --through icarus-verilog -s verilog.data k.data k.futil produces the following error:
[fud] ERROR: Invalid Numeric Type: Memory contains the value: `0xx', which is uninitialized.
This happens when the Calyx design attempts to read a port that is not connected to anything.
Try to generate a VCD file using `--to vcd` and look for signals that are not driven in a given cycle.

Is this an issue with icarus verilog itself, or with the input we are generating for icarus verilog?

I provided an explanation here: https://github.com/cucapra/pollen/discussions/15#discussioncomment-4090082
The problem is some port is likely undriven and neither Verilator nor interpreter would provide an error when that happens. However, it points to a real bug in the program.

With the changes in this PR: https://github.com/cucapra/calyx/pull/1242, I get the following output from icarus:
% fud e --to dat --through icarus-verilog -s verilog.data k.json k.futil -s futil.flags ' -p no-opt' -q
[fud] ERROR: Memory contains the value: `0xx', which is uninitialized. This happens when the Calyx design attempts to read a port that is not connected to anything. Try to generate a VCD file using `--to vcd` and look for signals that are not driven in a given cycle.
{
  "cycles": 52,
  "memories": {
    "depth_output": [
      2,
      1
    ],
    "path_ids1": [
      1,
      2
    ],
    "path_ids2": [
      2,
      0
    ],
    "paths_to_consider1": [
      0,
      1,
      1
    ],
    "paths_to_consider2": [
      0,
      1,
      1
    ],
    "uniq_output": [
      "2",
      "x"
    ]
  }
}

Note how uniq_output contains an "x" value. This is the problem that fud was complaining about. Somewhere along the computation that generates uniq_output[1], there is an undriven port (i.e., a port without an assignment) causing the problem.

@susan-garry can you close the issue once you validate that the bug is caused from generated code?

Yep, this was an issue with me not instantiating all of the memories. Thank you for all your help!

authors: rachitnigam susan-garry

repo: cucapra/calyx


text:
Issue deleting tasks with identical tags

I have found that if several tasks are submitted with a given tag, deleting a single task via the API deletes all of the tasks.
Appears to be an issue with the unique constraint on the tags.names column and the bi-directional relationships between the tasks, tasks_tags and tags tables as defined in database.py.
Adding two samples with tag 'a':
curl -F file=@/tmp/sample.exe --form_string "tags=a" http://server/tasks/create/file
curl -F file=@/tmp/sample2.exe --form_string "tags=a" http://server/tasks/create/file
sees the following in the DB tables:
tasks
id=1, target=sample.exe
id=2, target=sample.exe
tasks_tags
task_id=1, tag_id=1
task_id=2, tag_id=1
tags
id=1, name=a
Then issuing 'curl http://server/tasks/delete/1', both tasks 1 and 2 are deleted and I am left with:
tasks
tasks_tags
tags
Both tasks have been deleted despite only requesting task 1 to be deleted.
The proposed change addresses the issue.

Very interesting issue. I'll have to confirm the bug later, thanks.

This sounds like a cascading delete issue. I'm not sure if the right approach is to create multiple tags with the same name (which might hamper searching, and is the point of tasks_tags "joing" table) vs. resolving the issue that deleting a task also deletes tags associated with that task, even if there are other tasks using the same tag.

I'd certainly be interested to know if there is an alternate solution that maintains the uniqueness in the tags table.
Perhaps @jekil has some thoughts given he authored that part of the DB schema?

I have done some more testing of this and found a solution that addresses the initial bug but still maintains the uniqueness on the tags table.  Any orphaned tags are automatically cleaned up once they are no longer referenced by any machines or tasks.
This is based off the example provided here:
http://stackoverflow.com/questions/9234082/setting-delete-orphan-on-sqlalchemy-relationship-causes-assertionerror-this-att/9264556#9264556

I've recently run into the same issue. Given this issue is around tags though I'd be in favour of getting rid of the whole cascade="all, delete" at all - in practice there are only, at the very most a few dozen tags anyway.
Getting rid of it also fixes this issue. Thoughts?

I believe that will work OK as well.  It just means that every time a user submits a task and typos the tag or uses a non-existent tag, it will end up left in the tags table.  That was why I proposed the event listener to clean up any orphans along the way.  Really shouldn't be a big deal though I guess.

Sorry for the delay. I've just committed the patch that I proposed upstream. In this case I prefer simplicity over relatively complex logic with the event listeners etc.
Anyway, closing this issue as it is resolved for me. Please re-open or create a new issue if you're still experiencing issues.. :)

authors: Shane-Carr gtback jbremer

repo: cuckoobox/cuckoo


text:
Draft: Cucumber expressions support (#124)

Part of #124
Synopsis
This is the first PR in the story of Cucumber expressions support.
Solution
This PR implements Cucumber expressions AST and a parser for it. Next PRs will be adding AST into regex transformation and support inside proc-macros.
Checklist

Created PR:

[x] In draft mode
[x] Name contains Draft:  prefix
[x] Name contains issue reference
[x] Has assignee

[x] Documentation is updated (if required)
[x] Tests are updated (if required)
[x] Changes conform code style
[x] CHANGELOG entry is added (if required)
[ ] FCM (final commit message) is posted

[ ] and approved

[ ] Review is completed and changes are approved
Before merge:

[ ] Milestone is set
[ ] PR's name and description are correct and up-to-date
[ ] Draft:  prefix is removed
[ ] All temporary labels are removed

FCM
Cucumber expression AST and parser (#153, #124)

repo: cucumber-rs/cucumber