Find suitable regex interpreter to check RegularExpression subpackets

While BC now implements the RegularExpression packet, the question how to implement the logic behind it still stands.
RFC4880 states
The regular expression uses the same syntax as the Henry Spencer's
"almost public domain" regular expression [[REGEX](https://datatracker.ietf.org/doc/html/rfc4880#ref-REGEX)] package.  A
description of the syntax is found in [Section 8](https://datatracker.ietf.org/doc/html/rfc4880#section-8) below.

Java's regex implementation is obviously way more capable and more complex, so it is a good question whether it is a good candidate for implementing OpenPGP REGEXs.
Sequoia-PGP transpiles the syntax to Rusts regular expression library.
I don't think there is something similar we could do for Java?
Googling "Henry Spencer Regex Java" leads to this library but I am not sure whether it is implementing the right syntax.
Originally posted by @vanitasvitae in https://github.com/pgpainless/pgpainless/issues/246#issuecomment-1125112485

I found a library which claims to implement the HSRE syntax: https://github.com/basis-technology-corp/tcl-regex-java
Unfortunately this library pulls in quite a bit of dependencies.
For that reason I decided to create a RegexInterpreterFactory which has a static instantiate() method and which in term acts as a singleton of which a custom implementation can be provided.
That way, by default we will rely on java.util.regex.Pattern to match regular expressions, but simply by calling
RegexInterpreterFactory.setInstance(new HSRegexInterpreterFactory());

the user can set their own factory (in this case from a new submodule hsregex which then makes use of the afforementioned library.
I hope this gives implementers enough flexibility.

I pushed some code for this to main.


Control over image fetching

I'd like to have more control over fetching and decoding of images referenced in SVG files, in order to use existing decoders that I have, and to enforce size and memory usage constraints.
Would you be interested in a PR that makes image decoding "pluggable"? I image it could be something like an ImageDecoder trait and the library could allow user to configure their own implementation.

Sure, but can you clarify the use case?  Therefore you're optimizing for an edge case.
Despite how it may look, I'm trying my best to simplify resvg. This is one of the reasons resvg is pure Rust.
So I don't really see a benefit from using custom raster image decoders, since they will only increase the complexity even more. Especially if you account building resvg as a C library. Linking would become a nightmare.
But again, as long as you will be able to introduce this feature with minimal changes - it might be ok. I have to see the code first.
PS: just in case, "pluggable" rendering is out of scope. resvg already had 4 backends and it's just not worth it. Or even technically possible, to begin with. Luckily, one can easy write their own "renderer" on top of usvg, as many do.

@RazrFalcon  We have a very wide range of use cases. For example, we use SVG for our ad templates, which contain a large number of images of products that are bitmaps.

So, in resvg-js v2.1.0, we forked resvg and made some adjustments to image loading to load <image> that contain http URLs. It would be nice if resvg could support this natively.
@kornelski Are your needs and ideas similar to ours?

Hey there.  I, too, would like to use resvg to render SVGs that reference images by HTTP URL.  e.g.
	<image x="0" y="0" width="32" height="32"
		style="image-rendering: optimizeSpeed"
		xlink:href="http://picture-files.nuke24.net/uri-res/raw/urn:bitprint:YA2TPCRUBEYF7NIXHXIBGF53O6J3JVRL.GDZQQXJDMHLFAG3CVREVYIE7KVJQBHWR6AZSFAY/TOGoS-Vital_2230-background-1.png"/>

Currently resvg reports that URL "is not a path to an image".
I wonder if it would make sense for this feature to be in resvg itself, maybe behind an option, or if anyone is maintaining something like a "resvg++" fork with such a capability.  In my case they are SVGs that I created myself, so I'm not too worried about any security issues.

This issue a bit outdated. You already can handle URLs. See crates/resvg/examples/custom_href_resolver.rs. You would have to download your image in the resolve_string closure.
If you're using resvg CLI, then no, it's not possible. And I'm not sure would ever be possible. I assume even the simplest file downloading crate would be quite a heavy dependency.

Hi, can you tell me how to get the final image pixels from pixmap?
Is that possible?
I just want to complete the task of converting svg to raster image, the input svg may is the group of raster image and vector graphics, and I want to be able to perform image pixel manipulation on the converted raster image data.
Thanks a lot.


Add ParticipantCard and update UI

Create ParticipantCard and switch over from PersonCard
Update UI to display Participant details (now includes participant ID, birthdate, notes, NOKs)

Probably doesn't look great aesthetically at the moment but can touch up later (let me know if you have suggestions for changes before merge). Also the Note Labels have different colours based on Importance, thought that would be nice lol.

Codecov Report

Merging #59 (a64fdb8) into master (81bfc07) will decrease coverage by 1.30%.
The diff coverage is 4.54%.

@@             Coverage Diff              @@
##             master      #59      +/-   ##
============================================
- Coverage     69.67%   68.36%   -1.31%
- Complexity      587      588       +1
============================================
  Files           100      101       +1
  Lines          1962     2001      +39
  Branches        254      258       +4
============================================
+ Hits           1367     1368       +1
- Misses          479      517      +38
  Partials        116      116

Impacted Files
Coverage Δ

...ain/java/seedu/address/model/participant/Note.java
77.77% <ø> (ø)

src/main/java/seedu/address/ui/MainWindow.java
0.00% <0.00%> (ø)

...rc/main/java/seedu/address/ui/ParticipantCard.java
0.00% <0.00%> (ø)

...in/java/seedu/address/ui/ParticipantListPanel.java
0.00% <0.00%> (ø)

.../java/seedu/address/model/nextofkin/NextOfKin.java
60.00% <100.00%> (+2.10%)
:arrow_up:

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 81bfc07...a64fdb8. Read the comment docs.


Sometime, sql operations studio stop work, due to sql syntax error.

Issue Type: Bug
I click on the run, the query does not run (Not Responding), no error message in the messages tab
I then close the sql operation studio, then re-launch.
I then run the same query, it show me the error.
Started executing query at Line 1
Msg 4104, Level 16, State 1, Line 5 The multi-part identifier "c.OFFICEID" could not be bound.
Msg 207, Level 16, State 1, Line 11 Invalid column name 'office'.
Total execution time: 00:00:00.108
SQL Operations Studio version: sqlops 0.32.9 (8004776eff330e8980b473b6a2f6faf607164005, 2018-09-19T05:11:56.160Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7660U CPU @ 2.50GHz (4 x 2496)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
15.93GB (9.08GB free)

Process Argv
C:\Program Files\SQL Operations Studio\sqlops.exe

Screen Reader
no

VM
0%

Extensions (7)

Extension
Author (truncated)
Version

alwayson-insights
mat
0.2.1

agent
Mic
0.32.7

import
Mic
0.1.0

profiler
Mic
0.1.5

server-report
Mic
0.1.3

whoisactive
Mic
0.1.1

sql-search
Red
0.2.1

@datauduong
looks like you didn't choose target database for query and it uses master, where don't exists objects from your query.
I advise you to follow what database is chosen now:

No, the query was working, therefore it is not the target database.
This problem was also occurred in the previous month release. Therefore
I then updating and running the query at some point the editor stop working due to my Syntax Error.
Editor not showing the error, then nothing will work (click on run or execute query is not working due to syntax error).

I haven't reproduced this issue lately, so will proceed to close.
If it reoccurs, please let us know and we can reopen issue to investigate.


Dataset; covid-19-uk-data/data/covid-19-cases-uk.csv has non numerical values in some of the total cases field

@tomwhite  - Tom is there any chance you can change the '1 to 4' values in the Total Cases field?  Your dataset is the best one I've found (I've been grabbing the NHSEngland from the ArcGis dashboard, but it doesn't include Wales and Scotland), so would like to reference yours instead - I work for Qlik and we are helping out where we can - our software allows for a huge amount of analysis in to the data and your set is perfect.  Any additional mapping fields etc.. and data I'm working on happy to share, and the dashboard.

Hi @Jcamain - thanks for raising this, glad you are finding the dataset useful.
What would you change the '1 to 4' values to? This is how PHE published them right at the beginning, before switching to actual case numbers. I agree it's annoying, but the simplest thing is probably to filter the dataset to drop dates up to 2020-03-05 (the last date with '1 to 4'-style values in it) for the cases file.

FWIW, in my (python) code reading the csv file, I map all the cells which I expect to contain numbers through a function which is currently
def value(s):
    if s=='1 to 4':
        return 2.5
    else:
        return float(s)

just on the grounds that if all of 1,2,3 & 4 are equally likely, that's the average.  (And because if any more odd things like that turned up which would break the conversion to float, I can intercept them there too.  Fortunately it's been pure numbers all the way since.)
Pretty much standard operating procedure for real world data IMHO.  If it's not something like "1 to 4" there'll be the odd "n/a" or "?" or blank cell for your processing to choke on.  You always need a way of dealing with them.

Thanks guys!  To be fair, I thought it might cause some issues, but everything is working as it should!  Will post up my dashboard when I'm finished, just in case you find it interesting, J


False Positive Unused golangci-lint

What would you like to be cleaned:
The linter yielded several false-positive unused for the file pkg/hierarchy/cohort.go in #2939. As a short-term workaround, I added a rule in .golangci.yaml

/assign


Extract gRPC stub creation to a filter

Avoids repeating the same 5 lines in every method.

Looks good, I like it!
One question: how does @Authenticated get wired to provider? I can follow everything else but that mapping...
Maybe it is somehow based on @NameBinding?

One question: how does @Authenticated get wired to provider?

The filter is also annotated with @Authenticated, that's how it gets associated with it.
https://eclipse-ee4j.github.io/jersey.github.io/documentation/latest/filters-and-interceptors.html#d0e9931

Force-pushed to rebase on latest v2.0.0 and adapt the new index resource.
I also renamed the annotation.


Allow input of inline Latex equations

Description
Second ticket from #494 that will enable inline equations within the rich text editor. This includes the option for users to define an equation as either a block equation or an inline equation within the equation add/edit modal.
Acceptance Criteria

When adding or editing an equation, there is an option for a user to define the equation as inline or block
If the equation being added is an inline equation, then the equation appears within the text of the surrounding paragraph, following styling decided with Ricardo
I can edit an inline equation, and can change it to become a block equation, and vice versa

Wireframes for reference: https://www.figma.com/proto/983kpjf1sXyt2CmKKKXhjY/Wireframes?page-id=1369%3A5004&node-id=1371%3A5065&viewport=487%2C449%2C0.19&scaling=min-zoom

@danielfdsilva was there ever a conclusion on how to address the problem of the document processing each section as a separate item (ie: if a document section looks like: [{text}, {equation}, {text}] that should show up in the document as:
text

equation

text

Since that's true of all sections (so far) we process each section item one at a time, inserting a newline (\n) between each section item. However, for an inline equation to be stored in the database as [{text}, {inline-equation}, {text}] and then displayed as
text inline-equation text

The document process has to have knowledge about both the preceding and proceeding sections to properly handle an inline equation, for example in the case of an inline equation being in between a table or image image and text section. eg:
[{text}, {inline-equation}, {image}]
should be generated in the PDF as:
text inline-equation

image

and [{list}, {inline-equation}, {text}] should be handled as:
list

inline-equation text

Eg: here's what an inline equation looks like added to the end of the abstract:

It's placed on a separate line because each "child" element of a high-level section (such as the abstract) gets separated by a newline (\n)

As I said in the comment in the other PR, I don't think inline equations should ever on the same level as block elements. Inline equations should behave like other inline markup, like bold text, so they must be a child of a paragraph-like element.
To use your examples, the structure that is produced when adding an inline equation is:
paragraph
  text
  inline-equation
image

and
list
  list-item
    text
  list-item
    text
paragraph
  text
  inline-equation

Consequently, in your abstract example, the structure is
paragraph
  text
paragraph
  inline-equation

and the PDF output in the first image is correct.
The second image would be correct if the the abstract is marked up as:
paragraph
  text
  inline-equation

I think it's down to the user editing the document to make sure inline equations end up where they should be.

@oliverroick Your logic is correct. The slate document model complicates things a little as there is a difference between a text node and a block node, which is where @leothomas' worries come into play.
A text node is a simple:
{
  "text": "some text"
}

Whereas a block node:
{
  "type": "equation",
  "children": [
    {
      "text": "latex~example: e=mc^2"
    }
  ]
}

The equation is treated as a block and therefore rendered as such. Leo explained it brilliantly in an issue (https://github.com/NASA-IMPACT/nasa-apt/issues/431).
Block level items are currently not allowed inside a paragraph, as things like equations, table, heading, etc, are inserted at root level. The solution, as Oliver is saying, is to ensure that the equation is added as a child of the paragraph (only when inline). We'll need to add some normalizers to slate to ensure that the structure is sound as the user can toggle between block and inline equations.
But the resulting document could look something like:
{
  "children": [
    {
      "type": "p",
      "children": [
        {
          "text": "This is some "
        },
        {
          "text": "content",
          "bold": true
        },
        {
          "text": ". Then comes an equation."
        },
        {
          "type": "equation",
          "inline": true,
          "children": [
            {
              "text": "latex~example: e=mc^2"
            }
          ]
        }
      ]
    }
  ]
}


rm: troubleshooting: add how to automatically load a kernel module

Signed-off-by: Vanessa Maegima<EMAIL_ADDRESS>

Docs for 36beba964ccde2328ab75942d2ae90a0b8eaf85d are browsable at: https://ci.foundries.io/projects/fio-docs/builds/1391/docs/artifacts/html/index.html


french number not detected as french

french word for number are not detected as 'fr' language
small test program below  yield result:
Text: ceci est du francais LANG: fr SCORE: 0.8692260980606079
Text: donnez quarante cinq cinquante euros LANG: xx SCORE: 0.44422411918640137
Text: donnez 45 50 euros LANG: en SCORE: 0.20330046117305756
import spacy
import spacy_fastlang
nlp_lang = spacy.blank('xx')
nlp_lang.add_pipe('language_detector', config={"supported_languages": ["fr","en"]})

texts = ["ceci est du francais","donnez quarante cinq cinquante euros", "donnez 45 50 euros"]

for t in texts:
    doc = nlp_lang(t)
    print( "Text: {} LANG: {} SCORE: {}".format( t, doc._.language, doc._.language_score))

You're right, but it is likely coming from the model itself rather than the library. Here are the top 3 languages detected for your examples
[('__label__fr', 0.8692260980606079), ('__label__la', 0.07981850951910019), ('__label__vi', 0.015786711126565933)]
Text: ceci est du francais LANG: fr SCORE: 0.8692260980606079
[('__label__it', 0.44422411918640137), ('__label__fr', 0.2902344763278961), ('__label__en', 0.05172138288617134)]
Text: donnez quarante cinq cinquante euros LANG: xx SCORE: 0.44422411918640137
[('__label__en', 0.20330046117305756), ('__label__it', 0.14236119389533997), ('__label__fr', 0.10877827554941177)]
Text: donnez 45 50 euros LANG: en SCORE: 0.20330046117305756

You have a couple of options:

provide your own model using model_path
add a threshold, so it falls back to xx (or something else) if the confidence is too low

Thank you for your help , I slove the problem with a bigger model found on fasttest lid.176.bin,
seem to be the same version of the lid.176.ftz but uncompressed.

Glad to hear you found a solution. Yes, the bigger version is supposed to be more accurate, but it feels too big to be shipped by default in this project.
I'll close the issue for now.


V2Ray doesn't respect /etc/gai.conf

Please read the instruction and answer the following questions before submitting your issue. Thank you.
Please answer all the questions with enough information. All issues not following this template will be closed immediately.
If you are not sure if your question is truely a bug in V2Ray, please discuss it here first.

What version of V2Ray are you using (If you deploy different version on server and client, please explicitly point out)?

Server: unstable-e425876afe56564e82a528661438aa95857632a7 (This issue doesn't appear on latest stable version 4.26.0, only on unstable version)
Client: 4.26.0

What's your scenario of using V2Ray? E.g., Watching YouTube videos in Chrome via Socks/VMess proxy.

/etc/gai.conf is the config file for getaddrinfo(3). I want V2Ray prefer IPv4 connections over IPv6 by setting precedence ::ffff:0:0/96 100 in /etc/gai.conf.

What did you see? (Please describe in detail, such as timeout, fake TLS certificate etc)

When visiting websites, V2Ray prefers IPv6 connections instead of IPv4 (the websites display server's IPv6 address).

What's your expectation?

V2Ray prefers IPv4 connections instead of IPv6 (the websites display server's IPv4 address).

Please attach your configuration file (Mask IP addresses before submit this issue).

Server configuration:
{
  "inbounds": [
    {
      "port": 443,
      "protocol": "vmess",
      "settings": {
        "clients": [
          {
            "id": "",
            "alterId": 4
          }
        ]
      },
      "streamSettings": {
        "security": "tls",
        "tlsSettings": {
          "certificates": [
            {
              "certificateFile": "",
              "keyFile": ""
            }
          ]
        }
      }
    }
  ],
  "outbounds": [
    {
      "protocol": "freedom"
    }
  ]
}

Client configuration: Not relevant to this issue, but I'm willing to provide if it is needed.

Please attach error logs, especially the bottom lines if the file is large. Error log file is usually at /var/log/v2ray/error.log on Linux.

Server error log:
    // Please attach your server error log here.

Client error log:
    // Please attach your client error log here.

Please attach access log. Access log is usually at '/var/log/v2ray/access.log' on Linux.

This is the access log when loglevel is set to debug and then visit http://google.com/search?q=1:
V2Ray 4.26.0 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.14.6 linux/amd64)
A unified platform for anti-censorship.
2020/08/04 11:34:20 [Debug] v2ray.com/core/app/log: Logger started
2020/08/04 11:34:20 [Debug] v2ray.com/core/app/proxyman/inbound: creating stream worker on <IP_ADDRESS>:443
2020/08/04 11:34:20 [Info] v2ray.com/core/transport/internet/tcp: listening TCP on <IP_ADDRESS>:443
2020/08/04 11:34:20 [Info] v2ray.com/core/common/platform/ctlcmd: <v2ctl message>
v2ctl> Read config:  config.json
2020/08/04 11:34:20 [Warning] v2ray.com/core: V2Ray 4.26.0 started
2020/08/04 11:34:22 [Info] [696230717] v2ray.com/core/proxy/vmess/inbound: received request for tcp:google.com:80
2020/08/04 11:34:22 [Info] [696230717] v2ray.com/core/app/dispatcher: default route for tcp:google.com:80
2020/08/04 11:34:22 [Info] [696230717] v2ray.com/core/proxy/freedom: opening connection to tcp:google.com:80
2020/08/04 11:34:22 [Info] [696230717] v2ray.com/core/transport/internet/tcp: dialing TCP to tcp:google.com:80
2020/08/04 11:34:22 x:12577 accepted tcp:google.com:80
2020/08/04 11:34:22 [Info] [696230717] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled
2020/08/04 11:34:23 [Info] [1389776534] v2ray.com/core/proxy/vmess/inbound: received request for tcp:www.google.com:80
2020/08/04 11:34:23 [Info] [1389776534] v2ray.com/core/app/dispatcher: default route for tcp:www.google.com:80
2020/08/04 11:34:23 [Info] [1389776534] v2ray.com/core/proxy/freedom: opening connection to tcp:www.google.com:80
2020/08/04 11:34:23 [Info] [1389776534] v2ray.com/core/transport/internet/tcp: dialing TCP to tcp:www.google.com:80
2020/08/04 11:34:23 x:12583 accepted tcp:www.google.com:80
2020/08/04 11:34:23 [Info] [1389776534] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled
2020/08/04 11:34:24 [Info] [615817618] v2ray.com/core/proxy/vmess/inbound: received request for tcp:www.google.com:443
2020/08/04 11:34:24 [Info] [615817618] v2ray.com/core/app/dispatcher: default route for tcp:www.google.com:443
2020/08/04 11:34:24 [Info] [615817618] v2ray.com/core/proxy/freedom: opening connection to tcp:www.google.com:443
2020/08/04 11:34:24 [Info] [615817618] v2ray.com/core/transport/internet/tcp: dialing TCP to tcp:www.google.com:443
2020/08/04 11:34:24 x:12585 accepted tcp:www.google.com:443
2020/08/04 11:34:25 [Info] [3665469194] v2ray.com/core/proxy/vmess/inbound: received request for tcp:www.gstatic.com:443
2020/08/04 11:34:25 [Info] [3665469194] v2ray.com/core/app/dispatcher: default route for tcp:www.gstatic.com:443
2020/08/04 11:34:25 [Info] [3665469194] v2ray.com/core/proxy/freedom: opening connection to tcp:www.gstatic.com:443
2020/08/04 11:34:25 [Info] [3665469194] v2ray.com/core/transport/internet/tcp: dialing TCP to tcp:www.gstatic.com:443
2020/08/04 11:34:25 x:12583 accepted tcp:www.gstatic.com:443
2020/08/04 11:34:26 [Info] [2993755919] v2ray.com/core/proxy/vmess/inbound: received request for tcp:edge.microsoft.com:443
2020/08/04 11:34:26 [Info] [2993755919] v2ray.com/core/app/dispatcher: default route for tcp:edge.microsoft.com:443
2020/08/04 11:34:26 [Info] [2993755919] v2ray.com/core/proxy/freedom: opening connection to tcp:edge.microsoft.com:443
2020/08/04 11:34:26 [Info] [2993755919] v2ray.com/core/transport/internet/tcp: dialing TCP to tcp:edge.microsoft.com:443
2020/08/04 11:34:26 x:12630 accepted tcp:edge.microsoft.com:443
2020/08/04 11:34:27 [Info] [797891954] v2ray.com/core/proxy/vmess/inbound: received request for tcp:fonts.gstatic.com:443
2020/08/04 11:34:27 [Info] [797891954] v2ray.com/core/app/dispatcher: default route for tcp:fonts.gstatic.com:443
2020/08/04 11:34:27 [Info] [797891954] v2ray.com/core/proxy/freedom: opening connection to tcp:fonts.gstatic.com:443
2020/08/04 11:34:27 [Info] [797891954] v2ray.com/core/transport/internet/tcp: dialing TCP to tcp:fonts.gstatic.com:443
2020/08/04 11:34:27 x:12631 accepted tcp:fonts.gstatic.com:443

Other configurations (such as Nginx) and logs.

If V2Ray doesn't run, please attach output from --test.

The command is usually /usr/bin/v2ray/v2ray --test --config /etc/v2ray/config.json, but may vary according to your scenario.

If V2Ray service doesn't run, please attach journal log.

Usual command is journalctl -u v2ray.

Additional info

I can still use domainStrategy to force V2Ray use IPv4 address, for example:
{
  "routing": {
    "rules": [
      {
        "type": "field",
        "domain": [
          "geosite:google"
        ],
        "outboundTag": "ipv4"
      }
    ]
  },
  "outbounds": [
    {
      "tag": "ipv4",
      "protocol": "freedom",
      "settings": {
        "domainStrategy": "UseIPv4"
      }
    }
  ]
}

https://golang.org/pkg/net/#hdr-Name_Resolution
You need "force cgo resolver".


Using openTSNE (with/without exaggeration) on your datasets

I ran openTSNE (https://github.com/pavlin-policar/openTSNE) on all your datasets and I thought you may find the following observations interesting:

t-SNE can run on all datasets, including HIGGS, in the default 750 iterations with all default parameters (openTSNE scales the learning rate with the sample size). It is also reasonably fast, e.g. ~50 min for HIGGS on my laptop.
t-SNE with late exaggeration ~4 produces results very similar to UMAP.
SCE roughly corresponds to t-SNE with much larger exaggeration than 4, however the exact value differs strongly between datasets (I don't know why!): for MNIST I get a good match with exaggeration ~4, for FLOWCYTOMETRY -- ~12, for IJCNN, SHUTTLE, HIGGS -- ~24, TOMORADAR -- ~50. Puzzling!

I post below all my embeddings. Each figure shows t-SNE with exaggerations 1, 4, 12, 24, 50. I post my code below.

And HIGGS figure plotted with smaller dot size, to emphasize some structure:

import numpy as np
import pylab as plt
import seaborn as sns
from openTSNE import TSNE
from openTSNE.affinity import Affinities
import h5py
from scipy.sparse import csc_matrix

def load_data(dataset):
    f = h5py.File(f'P_{dataset}.mat', 'r')
    P_data = np.squeeze(f['P']['data'][()].T)
    P_ir   = np.squeeze(f['P']['ir'][()].T)
    P_jc   = np.squeeze(f['P']['jc'][()].T)

    P = csc_matrix((P_data, P_ir, P_jc)).tocsr()
    P /= np.sum(P)

    return P

def compute_tsnes(P, exaggerations = [1, 4, 12, 24, 50], verbose = False):
    Zs = []

    A = Affinities()
    A.P = P

    for ex in exaggerations:
        if not verbose:
            print('.', end='')
        if ex <= 12:
            Z = TSNE(n_jobs=-1, exaggeration=ex,
                     initialization='random', random_state=42,
                     verbose=verbose).fit(affinities = A)
        else:
            Z = TSNE(n_jobs=-1, exaggeration=ex,
                     early_exaggeration=ex, learning_rate = P.shape[0]/ex,
                     initialization='random', random_state=42,
                     verbose=verbose).fit(affinities = A)

        Zs.append(Z)

    if not verbose:
        print('')

    return Zs

def make_figure(Zs, title=None, figsize=(9, 2.2), s=.1):
    plt.figure(figsize=figsize)

    for i,Z in enumerate(Zs):
        plt.subplot(1, len(Zs), i+1)
        plt.axis('equal')
        plt.scatter(Z[:,0], Z[:,1], s=s, ec='none')
        plt.xticks([])
        plt.yticks([])

    sns.despine(left=True, bottom=True)
    if title:
        plt.suptitle(title)
    plt.tight_layout()

datasets = ['MNIST', 'SHUTTLE', 'IJCNN', 'TOMORADAR', 'FLOWCYTOMETRY', 'HIGGS']

for dataset in datasets:
    P = load_data(dataset)
    Zs = compute_tsnes(P, verbose=True)
    make_figure(Zs, title=dataset)
    plt.savefig(f'{dataset}.png', dpi=200)

Please notice two things:

Early exaggerations are used only in t-SNE initialization. To get the final t-SNE result, you must use exaggeration=1.
Even if you use large exaggerations throughout the iterations, the amount of exaggerations differs a lot across the six datasets. In contrast, SCE uses alpha=0.5 for all datasets, which is consistent and much more accessible.

Yes I agree.
Anyway, this is not really an "issue", so feel free to close it. I just thought you might find these results interesting.

Thanks. Now I close it.


Support gadget api

Hi!
I saw in the readme and on youtube that this library can be ported to any embedded linux devices that has gadget api as well as usb device and host controller. I wonder if you are working on that, and if not how can I do this and contribute :)

@dominicgs Do you have a starting place for what would make the Beaglebone black work with this repository?  I have an application where I'd like to MITM or sidechannel USB data to the ethernet network while not disturbing the original application.  I don't see any of the newer devices having ethernet.
Alternatively, if they support the "two USB" in one connection thing I've heard about that work work as well.  Example: Adding a usb-to-serial interface beside the original interface without changing the vendor or product for the original.

I have a rough outline for making this work with gadgetfs, but using gadgetfs has a couple of issues -- it's soft-deprecated in favor of functionfs, and requires some kernel patches.
In general, umap2 is a good resource for studying a (very relevant) backend implementation:

https://github.com/nccgroup/umap2/blob/master/umap2/phy/gadgetfs/gadgetfs_phy.py
https://github.com/nccgroup/umap2/tree/master/gadget

This is still something I want to do, but there are a lot of things in my queue before I can get around to it. Note that even after merging this, the result will still be limited compared to a proper FaceDancer board-- mostly due to the fact that Linux UDC/Gadget drivers don't give us fine-grained control over every piece of hardware.
Alternatively, if they support the "two USB" in one connection thing I've heard about that would work as well. Example: Adding a usb-to-serial interface beside the original interface without changing the vendor or product for the original.
What's the class/subclass of the 'victim' USB device? If it's a Composite device (all zeroes) and has unused endpoints, you can easily add an additional interface that provides another type of USB functionality via FaceDancer::USBProxy.
If the victim isn't a Composite device, you can possibly use FD::USBProxy to change it to composite while maintaining its original function -- but this depends on how the relevant drivers describe which devices they handle, and what assumptions the drivers make about the device.

Building around Raw Gadget https://github.com/xairy/raw-gadget (mainline since 5.7) seems like the best move for this ticket.
GadgetFS provides limitations - notably by sanity checking descriptors. Gross.
See https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/usb/raw-gadget.rst

There's now a prototype of a Facedancer backend based on Raw Gadget. It relies on a couple out-of-tree Raw Gadget patches, so I'll hold off sending it as a PR until I finalize the approach.
On a related note, resolving #48 would help with figuring out whether the backend implementation follows the right approach.

this is awesome! thanks for your work on this xairy. I'm also interested in these out-of-tree raw gadget patches. More then once i have found myself editing raw gadget. I see you removed the semaphore in the dev branch. +1

This is really cool work!
I'm currently prepping to merge https://github.com/antoinevg/Facedancer/tree/antoinevg/facedancer-v3 over the next couple weeks:

Some imports have changed but, fundamentally, the backend interface remains the same.
I hope to get a chance to write some docs on backend implementation but, failing that, I'm here to help get a PR merged.

🥳


[Models] Add Qwen2.5

PR types

New features
PR changes

Models
Description

Add Qwen2.5 models.

Qwen2-Math
Qwen2.5
Qwen2.5-Math
Qwen2.5-Coder

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


No trades made in binance

Note: for support questions, please join our Discord server

I'm submitting a ...
[X ] bug report
[ ] feature request
[ ] question about the decisions made in the repository

Action taken (what you did)
Ive followd all the instructions on installing GEkko

Expected result (what you hoped would happen)
Ive did a backtest over the last 24 hour with the assumed stategy. Outcome is 9 trades and a gain of 54%

Actual result (unexpected outcome)
There were no actual transactions made. ive runned gekko for 24 hours but no result. After this a dit the backtest and resulted in 9 transactions. I am new to this programming and have no idea what went wrong. Api is set right and i believe everything should work just fine.

Can some help me?

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc)

Inside the gekko/logs folder there should be some logs, can you upload the one somewhere and link to it here? (maybe check that there is no personal information like the amount of money on the account).

2018-02-03-02-12-UTC-tradebot.log
2018-02-03-02-12-UTC-watcher.log

These are both form the last few hours. Again i did a backtest on them and again there were trades made. Except in real life then.  Glad your taking the time the help me out

It appears you where running the CCI strategy over 10 minute candles. Looking at your tradebot.log:
2018-02-03 05:14:48 (DEBUG):	Insufficient data available. Age:  17  of  90
2018-02-03 05:14:48 (DEBUG):	ind:  false   17   90
2018-02-03 05:14:48 (DEBUG):	Trend:  undefined  for  0

The CCI indicator requires at least 90 historical candles, in your case this means 90 * 10 minutes = 900 minutes of data (=15 hours of data) while the Gekko only ran for around 2 hours. For as long as your indicator is not ready it won't calculate any numbers, for as long as that happens your strategy won't spit out any trading advice. Gekko only trades on trading advice.
We are aware that this information should be visible better in the UI, right now you had no idea what was wrong and why nothing is happening. For now I can only advice to check the tradebot log every once in a while. Meanwhile we are working on a new version of the UI that will display such information better, see here: https://forum.gekko.wizb.it/thread-65.html

So theoretical, if i let the cci indicator run voor 900 minutes it should be working after that?
Thanks for all the help !!!


chore: release main

:robot: I have created a release beep boop
auto-instrumentations-node: 0.37.0
0.37.0 (2023-05-16)
Features

auto-instrumentations-node: Add "@opentelemetry/auto-instrumentations-node/register" for an agent-like experience (#1400) (2d8e2b8)

Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

Dependencies

The following workspace dependencies were updated

dependencies

@opentelemetry/instrumentation-amqplib bumped from ^0.32.3 to ^0.32.4
@opentelemetry/instrumentation-aws-lambda bumped from ^0.35.1 to ^0.35.2
@opentelemetry/instrumentation-aws-sdk bumped from ^0.34.1 to ^0.34.2
@opentelemetry/instrumentation-bunyan bumped from ^0.31.2 to ^0.31.3
@opentelemetry/instrumentation-cassandra-driver bumped from ^0.32.2 to ^0.32.3
@opentelemetry/instrumentation-connect bumped from ^0.31.2 to ^0.31.3
@opentelemetry/instrumentation-dataloader bumped from ^0.4.1 to ^0.4.2
@opentelemetry/instrumentation-dns bumped from ^0.31.3 to ^0.31.4
@opentelemetry/instrumentation-express bumped from ^0.32.2 to ^0.32.3
@opentelemetry/instrumentation-fs bumped from ^0.7.2 to ^0.7.3
@opentelemetry/instrumentation-fastify bumped from ^0.31.2 to ^0.31.3
@opentelemetry/instrumentation-generic-pool bumped from ^0.31.2 to ^0.31.3
@opentelemetry/instrumentation-graphql bumped from ^0.34.1 to ^0.34.2
@opentelemetry/instrumentation-hapi bumped from ^0.31.2 to ^0.31.3
@opentelemetry/instrumentation-ioredis bumped from ^0.34.1 to ^0.34.2
@opentelemetry/instrumentation-knex bumped from ^0.31.2 to ^0.31.3
@opentelemetry/instrumentation-koa bumped from ^0.34.4 to ^0.34.5
@opentelemetry/instrumentation-lru-memoizer bumped from ^0.32.2 to ^0.32.3
@opentelemetry/instrumentation-memcached bumped from ^0.31.2 to ^0.31.3
@opentelemetry/instrumentation-mongodb bumped from ^0.34.2 to ^0.34.3
@opentelemetry/instrumentation-mongoose bumped from ^0.32.2 to ^0.32.3
@opentelemetry/instrumentation-mysql bumped from ^0.33.1 to ^0.33.2
@opentelemetry/instrumentation-mysql2 bumped from ^0.33.2 to ^0.33.3
@opentelemetry/instrumentation-nestjs-core bumped from ^0.32.3 to ^0.32.4
@opentelemetry/instrumentation-net bumped from ^0.31.2 to ^0.31.3
@opentelemetry/instrumentation-pg bumped from ^0.35.1 to ^0.35.2
@opentelemetry/instrumentation-pino bumped from ^0.33.2 to ^0.33.3
@opentelemetry/instrumentation-redis bumped from ^0.34.5 to ^0.34.6
@opentelemetry/instrumentation-redis-4 bumped from ^0.34.4 to ^0.34.5
@opentelemetry/instrumentation-restify bumped from ^0.32.2 to ^0.32.3
@opentelemetry/instrumentation-router bumped from ^0.32.2 to ^0.32.3
@opentelemetry/instrumentation-socket.io bumped from ^0.33.2 to ^0.33.3
@opentelemetry/instrumentation-tedious bumped from ^0.5.2 to ^0.5.3
@opentelemetry/instrumentation-winston bumped from ^0.31.2 to ^0.31.3
@opentelemetry/resource-detector-alibaba-cloud bumped from ^0.27.4 to ^0.27.6
@opentelemetry/resource-detector-aws bumped from ^1.2.2 to ^1.2.4
@opentelemetry/resource-detector-container bumped from ^0.2.2 to ^0.2.4
@opentelemetry/resource-detector-gcp bumped from ^0.28.0 to ^0.28.2

auto-instrumentations-web: 0.32.2
0.32.2 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

Dependencies

The following workspace dependencies were updated

dependencies

@opentelemetry/instrumentation-document-load bumped from ^0.32.1 to ^0.32.2
@opentelemetry/instrumentation-user-interaction bumped from ^0.32.2 to ^0.32.3

contrib-test-utils: 0.33.3
0.33.3 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

host-metrics: 0.32.2
0.32.2 (2023-05-16)
Bug Fixes

eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

id-generator-aws-xray: 1.1.2
1.1.2 (2023-05-16)
Bug Fixes

eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

instrumentation-amqplib: 0.32.4
0.32.4 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.2 to ^0.33.3

instrumentation-aws-lambda: 0.35.2
0.35.2 (2023-05-16)
Bug Fixes

.cjs extension support for lambda functions (#1442) (da737f1)
deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)
eslint-eqeqeq: updated the eqeqeq rule to match the core repo (#1485) (5709008)

Dependencies

The following workspace dependencies were updated

dependencies

@opentelemetry/propagator-aws-xray bumped from ^1.2.0 to ^1.2.1

instrumentation-aws-sdk: 0.34.2
0.34.2 (2023-05-16)
Bug Fixes

aws-sdk: correct setting error in attributes (#1495) (5f87026)
deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)
eslint-eqeqeq: updated the eqeqeq rule to match the core repo (#1485) (5709008)

Dependencies

The following workspace dependencies were updated

dependencies

@opentelemetry/propagation-utils bumped from ^0.29.3 to ^0.29.4

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.2 to ^0.33.3

instrumentation-bunyan: 0.31.3
0.31.3 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

instrumentation-cassandra-driver: 0.32.3
0.32.3 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.2 to ^0.33.3

instrumentation-connect: 0.31.3
0.31.3 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

instrumentation-dataloader: 0.4.2
0.4.2 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

instrumentation-dns: 0.31.4
0.31.4 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

instrumentation-document-load: 0.32.2
0.32.2 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

instrumentation-express: 0.32.3
0.32.3 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

instrumentation-fastify: 0.31.3
0.31.3 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

instrumentation-fs: 0.7.3
0.7.3 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

instrumentation-generic-pool: 0.31.3
0.31.3 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

instrumentation-graphql: 0.34.2
0.34.2 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)
eslint-eqeqeq: updated the eqeqeq rule to match the core repo (#1485) (5709008)
eslint-no-floating-promises: added no-floating-promises rule (#1488) (4eb405e)

instrumentation-hapi: 0.31.3
0.31.3 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

instrumentation-ioredis: 0.34.2
0.34.2 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

Dependencies

The following workspace dependencies were updated

dependencies

@opentelemetry/redis-common bumped from ^0.35.0 to ^0.35.1

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.2 to ^0.33.3

instrumentation-knex: 0.31.3
0.31.3 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

instrumentation-koa: 0.34.5
0.34.5 (2023-05-16)
Bug Fixes

deps: update dependency @koa/router to v12 (#1483) (b5b951e)
deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

instrumentation-long-task: 0.32.4
0.32.4 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

instrumentation-lru-memoizer: 0.32.3
0.32.3 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.2 to ^0.33.3

instrumentation-memcached: 0.31.3
0.31.3 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.2 to ^0.33.3

instrumentation-mongodb: 0.34.3
0.34.3 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.2 to ^0.33.3

instrumentation-mongoose: 0.32.3
0.32.3 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.2 to ^0.33.3

instrumentation-mysql: 0.33.2
0.33.2 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)
mysql: metrics - align metrics description and unit to semconv (#1480) (9fbd9e8)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.2 to ^0.33.3

instrumentation-mysql2: 0.33.3
0.33.3 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)
mysql2-tav: add 'pretest' command to tav.yml for mysql2 version 3 (#1490) (1f6299d)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.2 to ^0.33.3

instrumentation-nestjs-core: 0.32.4
0.32.4 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

instrumentation-net: 0.31.3
0.31.3 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

instrumentation-pg: 0.35.2
0.35.2 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)
pg-values: values should be parsable when enhancedDatabaseRepoting:true (#1453) (49a0389)
pg: do not replace argument with plain object (#1432) (e691537)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.2 to ^0.33.3

instrumentation-pino: 0.33.3
0.33.3 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)
eslint-eqeqeq: updated the eqeqeq rule to match the core repo (#1485) (5709008)

instrumentation-redis: 0.34.6
0.34.6 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

Dependencies

The following workspace dependencies were updated

dependencies

@opentelemetry/redis-common bumped from ^0.35.0 to ^0.35.1

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.2 to ^0.33.3

instrumentation-redis-4: 0.34.5
0.34.5 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

Dependencies

The following workspace dependencies were updated

dependencies

@opentelemetry/redis-common bumped from ^0.35.0 to ^0.35.1

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.2 to ^0.33.3

instrumentation-restify: 0.32.3
0.32.3 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

instrumentation-router: 0.32.3
0.32.3 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

instrumentation-socket.io: 0.33.3
0.33.3 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.2 to ^0.33.3

instrumentation-tedious: 0.5.3
0.5.3 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.2 to ^0.33.3

instrumentation-user-interaction: 0.32.3
0.32.3 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

instrumentation-winston: 0.31.3
0.31.3 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

plugin-react-load: 0.28.2
0.28.2 (2023-05-16)
Bug Fixes

eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

propagation-utils: 0.29.4
0.29.4 (2023-05-16)
Bug Fixes

eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.2 to ^0.33.3

propagator-aws-xray: 1.2.1
1.2.1 (2023-05-16)
Bug Fixes

eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

propagator-grpc-census-binary: 0.26.1
0.26.1 (2023-05-16)
Bug Fixes

eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

propagator-instana: 0.2.2
0.2.2 (2023-05-16)
Bug Fixes

eslint-config: replace gts with prettier and eslint (#1439) (2571c37)
eslint-eqeqeq: updated the eqeqeq rule to match the core repo (#1485) (5709008)

propagator-ot-trace: 0.26.3
0.26.3 (2023-05-16)
Bug Fixes

eslint-config: replace gts with prettier and eslint (#1439) (2571c37)
eslint-eqeqeq: updated the eqeqeq rule to match the core repo (#1485) (5709008)

redis-common: 0.35.1
0.35.1 (2023-05-16)
Bug Fixes

eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

resource-detector-alibaba-cloud: 0.27.6
0.27.6 (2023-05-16)
Bug Fixes

eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.2 to ^0.33.3

resource-detector-aws: 1.2.4
1.2.4 (2023-05-16)
Bug Fixes

eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.2 to ^0.33.3

resource-detector-container: 0.2.4
0.2.4 (2023-05-16)
Bug Fixes

eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.2 to ^0.33.3

resource-detector-gcp: 0.28.2
0.28.2 (2023-05-16)
Bug Fixes

eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.2 to ^0.33.3

resource-detector-github: 0.27.1
0.27.1 (2023-05-16)
Bug Fixes

eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

resource-detector-instana: 0.4.3
0.4.3 (2023-05-16)
Bug Fixes

deps: update otel core experimental to ^0.39.1 (#1493) (8ef95bc)
eslint-config: replace gts with prettier and eslint (#1439) (2571c37)

Dependencies

The following workspace dependencies were updated

devDependencies

@opentelemetry/contrib-test-utils bumped from ^0.33.2 to ^0.33.3

This PR was generated with Release Please. See documentation.

@pichlermarc think we should release this then update the SDK or other way around?

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/resource-detector-alibaba-cloud-v0.27.6 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/resource-detector-aws-v1.2.4 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/resource-detector-github-v0.27.1 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/resource-detector-instana-v0.4.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/auto-instrumentations-node-v0.37.0 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/auto-instrumentations-web-v0.32.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/host-metrics-v0.32.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/propagation-utils-v0.29.4 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/redis-common-v0.35.1 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/contrib-test-utils-v0.33.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-amqplib-v0.32.4 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-dataloader-v0.4.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-fs-v0.7.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-lru-memoizer-v0.32.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-mongoose-v0.32.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-socket.io-v0.33.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-tedious-v0.5.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-aws-lambda-v0.35.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-aws-sdk-v0.34.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-bunyan-v0.31.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-cassandra-driver-v0.32.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-connect-v0.31.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-dns-v0.31.4 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-express-v0.32.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-fastify-v0.31.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-generic-pool-v0.31.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-graphql-v0.34.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-hapi-v0.31.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-ioredis-v0.34.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-knex-v0.31.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-koa-v0.34.5 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-memcached-v0.31.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-mongodb-v0.34.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-mysql-v0.33.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-nestjs-core-v0.32.4 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-net-v0.31.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-redis-v0.34.6 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-redis-4-v0.34.5 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-router-v0.32.3 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-document-load-v0.32.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/instrumentation-long-task-v0.32.4 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/plugin-react-load-v0.28.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/propagator-aws-xray-v1.2.1 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/propagator-grpc-census-binary-v0.26.1 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/propagator-instana-v0.2.2 :sunflower:

:robot: Release is at https://github.com/open-telemetry/opentelemetry-js-contrib/releases/tag/propagator-ot-trace-v0.26.3 :sunflower:


[PF-2348] Wrap command tokens with quotes

Previously, running a command like
terra gcloud compute ssh --zone us-central1-a jupyter@newenv --command "ps aux"
would fail to parse, as the space information in the quoted part would be lost when the command is built.

But double-quotes should work too.  Though it doesn't make sense to me that these would be different?  The flag parsing library should be providing the underlying value regardless?

Do single quotes work?

Just tested it with the ssh command and it doesn't appear to work. I doubt the dsub example works as intended either.. but haven't tried.

Good point that double quotes should work, and that flag-parsing library (picocli) should handle this.
https://github.com/remkop/picocli/issues/851
https://stackoverflow.com/questions/63629789/how-to-escape-chars-from-string-option
Is it possible to write a test that fails before this PR and passes after this PR?


Error when selecting project from Recent Projects list since this commit f6e8b071acb1c750e9f617aef66ad0886b441d5c

Describe the bug
since this commit https://github.com/nvimdev/dashboard-nvim/commit/f6e8b071acb1c750e9f617aef66ad0886b441d5c, the following error is encountered when selecting any project from the Recent Projects list in the hyper theme

To Reproduce
Steps to reproduce the behavior:

Update dashboard-nvim to latest version
Start Neovim
Press Enter or the number indicated in the Recent Projects list

Expected behavior
default action should be triggered: Telescope find files in cwd

Describe the bug since this commit f6e8b07, the following error is encountered when selecting any project from the Recent Projects list in the hyper theme
To Reproduce Steps to reproduce the behavior:

Update dashboard-nvim to latest version
Start Neovim
Press Enter or the number indicated in the Recent Projects list

Expected behavior default action should be triggered: Telescope find files in cwd

Same problem, also when choosing "empty project"

I am encountering the same problem after that commit, in addition to experiencing other error messages related to the Hyper theme and paths. Here is the stack traceback for reference:
stack traceback:
        [C]: in function 'assert'
        ...e/nvim/lazy/dashboard-nvim/lua/dashboard/theme/hyper.lua:126: in function 'read_project'
        ...e/nvim/lazy/dashboard-nvim/lua/dashboard/theme/hyper.lua:153: in function ''
        vim/_editor.lua: in function <vim/_editor.lua:0>


qmdns-responder, simple responder service

planned to open this PR last summer, but a lot of stuff happened.

Sorry for the (very) late reply, for some reason I did not receive an email notification about this PR.
Thanks for the fixes!


Add harness board schematic

Please check accuracy @robbederks

Due to the harness board being closed source, we cannot comment on the accuracy of this schematic, and we will not be merging in this pull request.
We consider the harness schematic as being too complicated for general users to build themselves.

You could PR this to the big three Forks. Looks like something we should not forget

Schematic in this PR is not accurate, still work in progress at https://github.com/hivoltag3/neo/tree/harness_board_schematic


mariadb: change location configuration file to /etc/my.cnf

Motivation for this change
Change location configuration file to /etc/my.cnf
Required for normal works mysql utilities.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Required for normal works mysql utilities.

Can you expand on that? Why is this needed? Preferably also add this in the commit message.

It is more convenient to view/edit my.cnf in default and static location.
mysql, mysql_install_db, mariabackup are looking by default for my.cnf in /etc. After this change, one does not need to always specify --defaults-extra-file, to point the utilities to non-default location of my.cnf.

Thanks!

By the looks of it this seems to have broken the mysqlReplication test:
https://hydra.nixos.org/build/85547230

@andir this correction method will do?
diff --git a/nixos/modules/services/databases/mysql.nix b/nixos/modules/services/databases/mysql.nix
index 89291d4438f..a98bacf3a75 100644
--- a/nixos/modules/services/databases/mysql.nix
+++ b/nixos/modules/services/databases/mysql.nix
@@ -289,6 +289,7 @@ in
       ${optionalString (cfg.bind != null) "bind-address = ${cfg.bind}" }
       ${optionalString (cfg.replication.role == "master" || cfg.replication.role == "slave") "log-bin=mysql-bin"}
       ${optionalString (cfg.replication.role == "master" || cfg.replication.role == "slave") "server-id = ${toString cfg.replication.serverId}"}
+      ${optionalString (cfg.replication.role == "master" || cfg.replication.role == "slave") "slave-skip-errors = 1062"}
       ${optionalString (cfg.ensureUsers != [])
       ''
         plugin-load-add = auth_socket.so

@Izorkin I once tried that too, and this gets the vm test to succeed, but as @grahamc mentioned, this is a terrible hack - we can't just ignore all duplicate keys errors on slave replication.

@flokli @andir please check this variant
diff --git a/nixos/modules/services/databases/mysql.nix b/nixos/modules/services/databases/mysql.nix
index 89291d4438f..de313d0c454 100644
--- a/nixos/modules/services/databases/mysql.nix
+++ b/nixos/modules/services/databases/mysql.nix
@@ -318,7 +318,7 @@ in
             if ! test -e ${cfg.dataDir}/mysql; then
                 mkdir -m 0700 -p ${cfg.dataDir}
                 chown -R ${cfg.user} ${cfg.dataDir}
-                ${mysql}/bin/mysql_install_db --defaults-file=/etc/my.cnf ${installOptions}
+                ${mysql}/bin/mysql_install_db ${installOptions}
                 touch /tmp/mysql_init
             fi

How to leave the parameter mysql_install_db --defaults-file=/etc/my.cnf in non replication mode?

Interresting - this seems to work indeed!
@Izorkin, can you explain why we should not pass /etc/my.cnf to mysql_install_db?

@flokli need create new db without log-bin=mysql-bin
example
diff --git a/nixos/modules/services/databases/mysql.nix b/nixos/modules/services/databases/mysql.nix
index 89291d4438f..a200cab4ba1 100644
--- a/nixos/modules/services/databases/mysql.nix
+++ b/nixos/modules/services/databases/mysql.nix
@@ -281,6 +281,13 @@ in

     environment.systemPackages = [mysql];

+    environment.etc."my-test.cnf".text =
+    ''
+      [mysqld]
+      port = 3306
+      datadir = /var/lib/mysql
+    '';
+
     environment.etc."my.cnf".text =
     ''
       [mysqld]
@@ -288,6 +295,8 @@ in
       datadir = ${cfg.dataDir}
       ${optionalString (cfg.bind != null) "bind-address = ${cfg.bind}" }
       ${optionalString (cfg.replication.role == "master" || cfg.replication.role == "slave") "log-bin=mysql-bin"}
+      ${optionalString (cfg.replication.role == "master" || cfg.replication.role == "slave") "log-bin-index=mysql-bin.index"}
+      ${optionalString (cfg.replication.role == "master" || cfg.replication.role == "slave") "relay-log=mysql-relay-bin"}
       ${optionalString (cfg.replication.role == "master" || cfg.replication.role == "slave") "server-id = ${toString cfg.replication.serverId}"}
       ${optionalString (cfg.ensureUsers != [])
       ''
@@ -318,7 +327,7 @@ in
             if ! test -e ${cfg.dataDir}/mysql; then
                 mkdir -m 0700 -p ${cfg.dataDir}
                 chown -R ${cfg.user} ${cfg.dataDir}
-                ${mysql}/bin/mysql_install_db --defaults-file=/etc/my.cnf ${installOptions}
+                ${mysql}/bin/mysql_install_db --defaults-file=/etc/my-test.cnf ${installOptions}
                 touch /tmp/mysql_init
             fi

I do not know how to fix it
And need to add replication
--log-basename = master/slave1/slave2
--relay-log=mysqld-relay-bin
https://mariadb.com/kb/en/library/setting-up-replication/

Normally this variant?
diff --git a/nixos/modules/services/databases/mysql.nix b/nixos/modules/services/databases/mysql.nix
index 89291d4438f..a63b8956518 100644
--- a/nixos/modules/services/databases/mysql.nix
+++ b/nixos/modules/services/databases/mysql.nix
@@ -287,7 +287,9 @@ in
       port = ${toString cfg.port}
       datadir = ${cfg.dataDir}
       ${optionalString (cfg.bind != null) "bind-address = ${cfg.bind}" }
-      ${optionalString (cfg.replication.role == "master" || cfg.replication.role == "slave") "log-bin=mysql-bin"}
+      ${optionalString (cfg.replication.role == "master" || cfg.replication.role == "slave") "log-bin=mysql-bin-${toString cfg.replication.serverId}"}
+      ${optionalString (cfg.replication.role == "master" || cfg.replication.role == "slave") "log-bin-index=mysql-bin-${toString cfg.replication.serverId}.index"}
+      ${optionalString (cfg.replication.role == "master" || cfg.replication.role == "slave") "relay-log=mysql-relay-bin"}
       ${optionalString (cfg.replication.role == "master" || cfg.replication.role == "slave") "server-id = ${toString cfg.replication.serverId}"}
       ${optionalString (cfg.ensureUsers != [])
       ''
@@ -319,6 +321,7 @@ in
                 mkdir -m 0700 -p ${cfg.dataDir}
                 chown -R ${cfg.user} ${cfg.dataDir}
                 ${mysql}/bin/mysql_install_db --defaults-file=/etc/my.cnf ${installOptions}
+                ${optionalString (cfg.replication.role == "master" || cfg.replication.role == "slave") "rm ${cfg.dataDir}/mysql-bin-${toString cfg.replication.serverId}.*"}
                 touch /tmp/mysql_init
             fi

I also saw the log messages recommending to setup a relay-log, so this might be a good idea.
Not so sure about the rm ${cfg.dataDir}/mysql-bin-${toString cfg.replication.serverId}.* part - why would we want to remove the binary log from servers or slaves during initial setup?

mysql-bin log causes replication conflict, since perhaps they are identical (sorry, bad english)

No worries, thanks for your help!
But this should be then a bug upstream, shouldn't it? How come it was introduced by this PR?

not running check mysqlReplication (

Let's continue discussion in https://github.com/NixOS/nixpkgs/pull/61671. Thanks!


CMake integration of "compiled" proto file

This only adds the dependency. Doesn't do anything yet - that would be the next step.

Good to merge - can you rebase against my branch for conflicts?


text-indent

text-indent

This issue was imported from Google Moderator
Moderator votes: +9
Issue added by ____ on 2013-11-19
To vote this issue up or down, simply include +1 or -1 in your comment.

Duplicate of #1065.


Publish packages as beta

Great work shifting many of the packages over to TypeScript. I was wondering if we could start to battle test them if they were published under a beta or alpha version to npm?

Yes! I will work on this in the next couple of days and track with this issue. Definitely want to battle test these. Converting the demo package should be a good test as well.

These are currently released now as<EMAIL_ADDRESS>🎉 Example codesandbox here.
Note that grid, axis, legend, and stats are still JS (track in the TS project associated with this issue) and @vx/brush is broken until #567 lands. I'm hoping to wrap up the remaining packages in the next ~week.
Thanks for testing, and please open issues for anything undesirable you encounter / PRs welcome if you want to help fix anything 🙏 Woot TS! 🤙

Awesome thanks for the quick response! I'll start testing these and I'm more than happy to contribute if and when I can 👍

@williaster Any chance you could also publish the latest changes from https://github.com/hshoff/vx/pull/567 too?

yes! trying to land the @vx/legend re-write in the next few minutes and will publish thereafter.

sorry for the delay, the types in @vx/legend were trickier than expected but that's merged.
0.0.193-alpha.1 is out now with all changes in master, the brush fix #567 and all packages re-written in TS 🎉 will likely now convert vx-demo to ts and release 0.0.193 after any needed fixes for that are in 👍

FYI I have a pretty big PR in progress for the vx-demo re-write: #579 . Lots of fixes being addressed and in linked PRs. Really hoping to wrap it up this week 🤞 🍀

#579 is in and TONS of fixes published under 0.0.193-alpha.2, hopefully can land non-alpha 0.0.193 soon and call TS v0 done 😄


test: add TEST_REPSITORY_NAME_PREFIX to isolate test recordings

Found a small typo.

Great catch! Fixed. Looking good otherwise?


how to reopen/restart stream after EndReached/Freeze

I have an issue / a question (pick one) about Vlc.DotNet.
Generic information

Vlc.DotNet version : 2.2.1
Vlc.DotNet project used : WinForms
libvlc version : x86 using this link's instruction -> https://github.com/ZeBobo5/Vlc.DotNet/wiki/Using-Vlc.DotNet-in-WinForms (nuget package manager)
.net version : 4.6.1
Project language : C#
Project build architecture : x86
Operating system : Windows10 x64

Summary
I am displaying a rtsp stream using a VlcControl in a windows form.
This stream is from an ONVIF conformant ip camera.
When I play the stream, I always encounter the EndReached flag of the VlcControl when the stream has been playing for a bit.
So, it looks like the display of the stream just freezes, because my VlcControl thinks there's no more images to show...
I have to repress my play button every time my stream freezes, so my application can't really run by itself...
I want my stream to restart by itself when it freezes.
I tried using the EndReached flag :
private void myVlcControl_EndReached(object sender, Vlc.DotNet.Core.VlcMediaPlayerEndReachedEventArgs e)
{
(sender as VlcControl).Play(MyStream.URL);
}
But, when I do so, my stream won't restart...
What's the best way to do what I'm trying to achieve?

Please read the wiki, there is a page for this kind of freezes

oh god, I feel stupid, it's right there! hahah
Thank allot!
Wiki link


Custom hostname support for Cloudflare API

💡 Feature request
Overview and problem statement
Currently, the Cloudflare api hostname api.cloudflare.com is hard coded in wrangler. It would be nice to support more than one hostname for resiliency purposes. Maybe something like  --api-hostname param or a config variable.

as discussed internally, coudl we consider an environment variable instead of a CLI argument.

I say we check for the CF_API_HOST backend. We will need to pass this host to cloudflare-rs and also use it in our own http module. I don't think we should add a flag as this is a very niche use case and not something we should bog users down with unless they go looking for it.

CF_API_HOST in env sounds like a good plan to me 👍

Sounds good to me too 👍

Comment to reopen issue. Been busy, I'll make a PR to fix


conmon: 2.0.21 -> 2.0.22

https://github.com/containers/conmon/releases/tag/v2.0.22

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@ofborg eval


[benchmark] Add test for lazy filter -> array

Adds a test of Array(collection.lazy.filter(predicate)) performance.

@swift-ci Please smoke test

The test as committed does not test creation of arrays from lazily filtered collection, but a lazy filter on creation of 1 000 000  one element arrays!

Ah, now that I’ve profiled it, creating 1 000 000 one Int element arrays is nothing. I got spooked by the disproportionately long time this benchmark takes on my machine compared to the others. I guess that is a problem with harness setting the N value?


Stream Membership Input : no user to subscribe error does not go away even after changing the entered input

When an incorrect or a non existing username is entered in the Stream Membership input to subscribe a user, and clicked on Add or enter is pressed, a "No User to Subscribe" error is thrown.
However, as soon as we change this input, the error is expected to fade away. But, the error still stays even after adding a valid User in the input and creating an input pill of it.

Steps to reproduce:

Go to Settings -> Manage Streams
Click on a stream name.
Go to the Subscribers tab.
In Stream membership input, type some text and press Enter.
Then change it but the error stays.

Instead:

[ ]  The error message should disappear when the user starts typing into the stream membership input field.
[ ] We should also show this error message in the stream creation UI. Currently, there is no clear feedback for non-existent names there.

CZO discussion

hey @roanster007 I would really like to try solving this issue, can you please assign me this. Thanks

@zulipbot claim

This issue can be rectified by this PR

@cherish2003 , I have looked at your PR, and it seems to somewhat solves the issue, but introduces a bug in which you add a Pill, and then enter some random text and press enter, then the error is not displayed, but the Pill is subscribed, with a successful message.

Also, refrain from making a new PR every time you change something in your branch... rather you can force push your updated branch into the same PR.

@zulipbot claim

@zulipbot yes i am working on it


What is the syntax for containment?

I couldn't easily see any code examples of the attribute to add for constraining the sv-elements to the bounds of the sv-root.
Please provide example.
Thank you for the great work. :)

I got containment to work by looking in the source code and trying out some different stuff. In the end i got it to work by using example below, but it creates some latency when moving because of the constant checking for bounderies.
HTML
<div sv-root sv-part="editItem.Gallery">
     <div sv-element="opts" class="editImage grid" ng-repeat="picture in editItem.Gallery">

CONTROLLER
// Set containment div - but this creates some latency when moving
var containmentElement = angular.element('#your_div_containment')[0];
$scope.opts = {
   "containment": containmentElement
};

sv-element="{containment:'.your-parent-div-class'}"  is the syntax I used and it worked


check compatibility of container run time failure scenario for csi based cstor volumes

PR is in review https://github.com/mayadata-io/e2e-konvoy/pull/178


Cannot compile on Linux (?)

I do as the linux.yml says, i get this error all the time:
dumitru@dumitru-Lenovo-V155-15API:~/Osiris$ cmake -D CMAKE_BUILD_TYPE=${{ matrix.configuration }} -D CMAKE_CXX_COMPILER=${{ matrix.compiler }} -S . -B ${{ matrix.configuration }}
bash: CMAKE_BUILD_TYPE=${{ matrix.configuration }}: bad substitution

How do I fix?

https://stackoverflow.com/a/20616103

what exactly did you do to fix it?


update phi3_nvmo_ptq example and onnxruntime-directml version

update phi3_nvmo_ptq example and onnxruntime-directml version
Checklist before requesting a review

[ ] Add unit tests for this change.
[ ] Make sure all tests can pass.
[ ] Update documents if necessary.
[ ] Lint and apply fixes to your code by running lintrunner -a
[ ] Is this a user-facing change? If yes, give a description of this change to be included in the release notes.
[ ] Is this PR including examples changes? If yes, please remember to update example documentation in a follow-up PR.

(Optional) Issue link

@jambayk : could you please review this change.
Updated the readme file and example doc


nimPackages cross-compilation fix

Description of changes
The Nim compiler can build for any supported target platform so disregard targetPlatform and build for hostPlatform instead.
The nim_builder is irrelevant for use within buildNimPackage and should therefore be taken from buildPackages.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

I think this is ok? Did you try cross-compiling any nim package with this change (both inside nixpkgs and outside)?

I am also not sure if this is how it works, but I've tested cross-compiling x86_64-linux -> aarch64-linux and x86_64-linux -> x86_64-genode.
It would be nice if there was an automatic cross-compile test I could add something to.

@ofborg build nitter pkgsCross.aarch64-multiplatform.nitter

@NixOS/exotic-platform-maintainers hey cross folks, does this look right?

The compiler should be built for hostPlatform, sure, but it should produce code for the targetPlatform always, this is nixpkgs assumption. The target prefix should be targetPlatform and if nim is multi target, we should (at least for the purposes of building derivations in nixpkgs) add a wrapped nim that passes the appropriate flags to fix the current targetPlatform (like we do for clang).

Yeah what @sternenseemann said. This needs to be reworked.

Ok, I'll keep an eye on it.

What huh? Unless I misread @sternenseemann was saying this is not done correctly yet and needs revision. That is what I meant to say at least.


FIX Cython extension not building on Windows

This PR fixes issue #183 (and possibly #125, if that was still an issue) with the compilation on Windows. All windows builds are tested again, which takes some time with appveyor but is probably safer.
The solution was to remove the libpython (mingw compiler) from the list of installed packages so that the already present Visual Studio compiler gets used.
Also removing all flags to hide warnings (as those might actually be useful),  reverting to the default flags.

Thanks for doing this @rth!
While the AppVeyor checks now pass, the Cython extensions are not actually building on AppVeyor.

@DanHickstein My mistake, thanks for spotting this! I'll fix it, it has something to do with libm being in msvcr when using MSVC compiler...

The situation on this PR is the following. Cython extensions build fine on Appveyor for PY3 but not for PY2. The issue is the libm (that is used for sqrt and arcosh function calls) is that should be included in the runtime enviroment of Microsoft visual studio compiler. This does work as expected with MSVC 2015 (PY3.5) but for some reason non on MSVC 2008.
I agree with @stggh  on this one, it would be disproportionate to spend more time debugging this, given the little value this actually brings compared to other features in PyAbel (at least for me).
I added some code to make sure that failed cython exceptions do raise an error in Travis / Appveyor, then explicitly ignored this error for PY2 on Windows. For users, it's still can silently fail and will just print a warning.
If this is a problem for conda-forge we could reopen this, or just say that PyAbel includes this direct C implementation only on Linux and PY3 Win. Another argument for not getting rid of cython altogether is that once we have this workflow, it's relatively easy to add some existing C implementations or potentially optimize existing algorithms with Cython without additional effort.

I agree that we shouldn't spend too much time on this, since it will appeal to only a small subset of users. Still, see my comment above: are we just not giving the win32 install access to the m library?

Cython extensions are now building on MSVC 2015 (Win+Py3 on Appveyor), but now on MSVC 2008 (Win+Py2 on Appveyor).
Partial victory declared!! :)

Cython extensions are now building on MSVC 2015 (Win+Py3 on Appveyor), but now on MSVC 2008 (Win+Py2 on Appveyor).
Partial victory declared!! :)

A strategic retreat would be more accurate :)

Great work @rth and @DanHickstein, BUT, what happened between:

Oh, that is weird. It means that acosh is not equal to ln( 1-sqrt(x**2 -1) ) on MSVC.

and

Cython extensions are now building on MSVC 2015 (Win+Py3 on Appveyor), but now on MSVC 2008 (Win+Py2 on Appveyor).

Oh, you mean "not"
Given that Python3 is developing fast, and Conda provides a simple OS-independent Python3 installation, perhaps Python2 support for PyAbel will be next ;-)

Yeah, I meant "not". :)


fix/mapper: add new reviewer

What type of PR is this?
What this PR does / why we need it:
add ttlv to devicetwin devicecontroller mapper module reviewer.
PRs authored:
https://github.com/kubeedge/mappers-go/pulls?q=pr+author%3Attlv+
https://github.com/kubeedge/kubeedge/pulls?q=+is%3Apr+author%3Attlv
reviews:
https://github.com/kubeedge/kubeedge/pulls?q=is%3Apr+reviewed-by%3Attlv+
https://github.com/kubeedge/mappers-go/pulls?q=is%3Apr+reviewed-by%3Attlv+
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

/cc @GsssC @sailorvii

/lgtm @fisherxu

/lgtm
/approve


[Question] Does cloud-trace-nodejs support head based sampling?

Is your feature request related to a problem? Please describe.
Does cloud-trace-nodejs support head based sampling?
I've run micro-services that send high-rate request.
A  -------- context propagation ----------> B
And I found that sometimes span A is sampled but span B is unsampled in same trace.
That is because this.sampler.shouldTrace(options.timestamp) returns false for span B.
I'm not sure but I think sampling rate is depended on each trace-agent. It is not considered trace context.
I wondering that it is normal operations?
Describe the solution you'd like
supports head based sampling?

Yes, we do head-based sampling, but we may re-sample to respect the configured sampling rate.
I believe a pure head-based sampling can be set up with a config like this:
require('@google-cloud/trace-agent').start({
  samplingRate: 0,
  contextHeaderBehavior: 'required',
});

Note: This will probably not create any root spans, but require all requests to come with a propagation header.
Let me know how this works for you.

@kintel , it works well to me!
thank you for your help :+1:


[feature] more eloquent style calls

Really appreciate the work gone into this sdk/library - and with it, the simplicity of the code that comes out it's usage.
As part of the definition - you specify an eloquent Like interface. To this end this Pull request adds additional functions and make some existing function more like their eloquent versions.
I hope this meets your expectations :)

At first glance this looks awesome! Thank you. I'll try to dig in and go through it more closely here soon.

@jszobody  - let me know if any questions - there's a few bits that i was thinking about - but didn't want to do a super large 1st PR out of no-where.

@BinaryKitten you got any thoughts on adding test coverage to all this? to be honest I haven't written tests for an SDK before. does it need a real hubspot test account to hit real endpoints (complicated, and slow for sure)? do I mock the heck out of everything (which to me reduces the value of the tests significantly)? dunno...

hmm this is a good question @jszobody.
Ultimately, if we're tying this to Laravel - we could use the laravel http client - and then we can substitute that for testing.


Combo-box as inline grid editor is not focused when entering edit mode

The default behavior for inline text editors in the grid is that they receive focus when entering edit mode. But when a combo-box appears as inline editor, one has to click it again to give it focus.
Perhaps this is because of the elem.focus() call in the setCaretAtEnd() function, which only works for <input> elements and not for <select> elements.
I would suggest to call the focus() method on any inline editor element when entering edit mode.

This example can be used to test the described behaviour:
<html xmlns="http://www.w3.org/1999/xhtml">
	<head>
		<title>Example for testing the cell rendering after editing.</title>
		<meta charset="utf-8" />
		<script src="https://code.jquery.com/jquery-2.1.4.min.js"></script>
		<script src="http://code.gijgo.com/1.1.0/js/gijgo.js" type="text/javascript"></script>
    <link href="http://code.gijgo.com/1.1.0/css/gijgo.css" rel="stylesheet" type="text/css" />
	</head>
	<body>
		<table id="grid" style="width:100%"/>
		<script type="text/javascript">

    var weekdays = ["Monday","Tuesday","Wednesday","Thursday","Friday","Saturday","Sunday"]
        $(document).ready(function () {
            var data, textEditor, weekDayEditor, weekDayRenderer;
            data = [
                { "ID": 1, "Name": "Hristo Stoichkov", "DayOfWeek": 1 },
                { "ID": 2, "Name": "Ronaldo Luís Nazário de Lima", "DayOfWeek": 3 },
                { "ID": 3, "Name": "David Platt", "DayOfWeek": 4 }
            ];
            weekDayRenderer = function (value, record, $cell, $displayEl) {
              $displayEl.text(weekdays[value]);
            };
            weekDayEditor = function ($container, currentValue) {
                var selectHtml, selected;
                selectHtml = "<select>";
                weekdays.forEach(function (label, value) {
                  selected = (currentValue !== undefined && value === currentValue)?"SELECTED":"";
                  selectHtml += "<option " + selected + " value=" + value + ">" + label + "</option>"
            });
                selectHtml += "</select>";
                $container.append(selectHtml);
            };
            $("#grid").grid({
                dataSource: data,
                columns: [
                    { field: "ID", width:"10%" },
                    { field: "Name", title: "Name", editor: true, width:"45%" },
                    { field: "DayOfWeek", title: "Renderer: Day of week", renderer:weekDayRenderer, editor: weekDayEditor },
                ]
            });
        });

    </script>
	</body>
</html>

This is fixed in the new development version. You can find the new build only in github at https://github.com/atatanasov/gijgo/tree/master/dist until the release of 1.2.0

That's a lightning fast solution :-)
Thanks!


Create nkuht.txt

nkuht.txt

nkuht.txt

the school's website is https://www.nkuht.edu.tw.  Thank you.

@Smartmanliu I am sorry, I have to close the request without merging, because you made a mistake in a request and requested to merge too many files, most of them do not relate to the organization which you would like to add to this repository. Please ensure that you are familiar with this repository rules located at the bottom of this page and submit a new request with the correct information. Thank you for your understanding!


Firefox wont load markets

still seeing this message and cant get markets to load on Firefox

btw putting this in RC2 as it's a bug not a feature.

@Chwy5 Try deleting your storage. If that fixes the issue this can be closed.

Yeah tried that....The markets dont filter in, the categories just spin and I still get the same...Uncaught exception: object in the console

It worked for me, deleted augur-42 database as well as all the 0x databases from the storage tab.
Paul
<EMAIL_ADDRESS>
From: Chwy5<EMAIL_ADDRESS>Sent: Tuesday, April 14, 2020 3:23:40 PM
To: AugurProject/augur<EMAIL_ADDRESS>Cc: Paul Gebheim<EMAIL_ADDRESS>Assign<EMAIL_ADDRESS>Subject: Re: [AugurProject/augur] Firefox wont load markets (#7244)
Yeah tried that....The markets dont filter in, the categories just spin and I still get the same...Uncaught exception: object in the console
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://github.com/AugurProject/augur/issues/7244#issuecomment-613710709, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAAU76RVBJ32PZOLPWMNLSLRMTO6ZANCNFSM4MF7TZYA.

Ohh those were under Indexed DB for me....I had deleted local storage underneath that....delted those and now i have markets...thanks


How to roll-back to an older version?

I need to rollback to release 1.27 but the package installer prevents this.
Is there a way to cleanly uninstall?

probably delete the installation receipt (but I forgot where OS X stores those nowadays) and reinstall

Thanks for the hint. The following does the trick:
sudo rm /var/db/receipts/com.rentzsch.mogenerator.*

Great. Yeah that jogs my memory.


Quotation border only printed on last page

Given:
Hello World
===========

[[someid]]
____
A

B

C

D

E

F

G

H

I

J

K

L

M

N

O

P

Q

R

S

T

U

V

W

X

Y

Z
____

Normal text afterwards.

Expected:
One border lefthandside to the quotation on both pages.
Actual:
First page shows no border. Second page has a border lefthandside to the quotation on both pages.

Framing for quote blocks that span multiple pages is not yet implemented. In fact, the only block type that currently supports this scenario (as of 1.5.0.alpha.13) are listing and literal blocks. The same treatment / logic needs to be applied to all blocks that have framing or background. This is a duplicate of #270.
Here are the issues to track multi-page support for various block types for reference:

quote block - #270
sidebar block - #259
example block - #362

quote & verse is very different from implementing sidebar & example.
First call means lowest z-index. Drawing a background rectangle means it needs to be called before anything else. However, asciidoctor relies on prawnpdf to determine where to put characters or even page breaks. Hence in between setting text across multiple pages, it would be required to draw the rectangles.
Basically prawnpdf's API is too poorly engineered for such use cases. The only workaround I can see is manually interrupting setting text and checking whether page_number has changed. I won't fix it. I want nice solutions, not another workaround.
As far as this issue is concerned, a fix is available. I consider it fixed.

We don't close issues until the PR is merged, so I'm going to reopen until then.

I agree the Prawn API is poor at helping with layout, but I created a two-phase writer in the converter for precisely this use case. (I'll admit this API is still rough around the edges, but it gets the job done for now). The first phase performs a dry run that brings back the total height (it should also return the the start page and the end page, so I might add that). From that information, you can perform all the graphics work at the beginning of the second phase, then write the content.

I'll share that it took me several weeks to come up with a solution for dealing with Prawn's single-pass rendering. That led me to using a scratch document, where I can test content before "burning" it into the main document.

I've send a revised pull request to your pull request. If that looks good to you, merge it and I'll rebase and push upstream.

Resolved by 471af3702929fccf89cd30149bf6399f9dec645f.

Thanks for improving it!


Get MIME type

Greetings,
Is there a method get the MIME type of an attachment of a received email? A quick search didn't turn up anything.
Thank you fir your help,
GTP

Thanks for your answer. I found an alternative way that I'll report here for future reference, but unfortunately semms that Gmail changes the content-type so I can't rely on it and I have to find a workaround. Anyway to get the content-type:
gmail.observe.on("view_email", (domEmail) => {
    const emailData = gmail.new.get.email_data(domEmail);
    const attachments = emailData.attachments;
    const type=attachment.type   //this gets the MIME type
});


Fix missing co-recommender functionalities

 Two bugs on the co-recommender functionalities that need to be corrected


Addition of pattern problems

Site URL
https://github.com/subhadipbhowmik/30-Days-Of-CPP/commit/0f47048363f660b0ef653fa0dda4611adcf71ff4
What information was incorrect, unhelpful, or incomplete?
As someone who learned C++ recently, I would like to add some pattern printing problems after the For loop-While loop and IF-ELSE portion. I feel these problems really help in understanding the functionality of the loops and it will also work as some practice exercise for the learner. I strongly believe that adding up these exercises will add value to your project as well as to the learning of users.
As GSSoC contributor,I would like you to assign this task to me.
What did you expect to see?
I expected some hands on experience about the use of while and for loops.
Do you have any supporting links, references?
No response
Do you have anything more you want to share?
No response

Looking Forward to see your PR.


Code contributions

This cannot be merged because it checks a bunch of binary files into git.
The right thing to do is to archive the binaries elsewhere (such as on the COSMOS wiki) and fetch them as needed.

This is also not passing tests.


use readable-stream module

https://www.npmjs.com/package/readable-stream

If you want to guarantee a stable streams base, regardless of what version of Node you, or the users of your libraries are using, use readable-stream only and avoid the "stream" module in Node-core, for background see this blogpost.
[...]
readable-stream is maintained by the Streams Working Group, which oversees the development and maintenance of the Streams API within Node.js.

I used quadstore in simple prototype app running in a web browser and streams from RdfStore#match didn't have AsyncIterator. Using this module fixes it and it looks like recommended way of using Node.js streams.

This change is

Hello @elf-pavlik ! Thank you for this PR. I am generally hesitant about depending on readable-streams instead of the natively-shipped stream library for backend-only projects. However, while it was born on the backend, quadstore now targets both the backend and frontend side of JS development and it makes sense to switch to readable-stream.

Merged in version 5.1.0, which I have just published to NPM.


No GitHub releases for latest vcpkg version

Problem
It's confusing that the vcpkg releases are not the latest version available. You have to look at the tags to find out the latest vcpkg version that was actually released.

Proposed solution
Create a release for every tag.

Thanks for posting this issue? Now every tag has the related release version in vcpkg. I think this issue can be closed.

Thanks!

Thanks!