text:
Broken short routing variant $app->get('/route', 'Controller:method');

I cannot say exactly which commit leads to this problem. I updated my project through composer (48be9d2) and saw that routes like:
$app->get('/', function () {
    ...
});

work well, but routes like:
$app->get('/route', 'Controller:method');

doesn't work.

Show the exception throwed

Page not found 404.
I suppose it means - no exceptions. In this particular case I didn't use namespaces. Fully qualified class name exactly YourController:method
I want to say that application worked well and after last update (using composer) I have problems and for now I can't continue developing my app.

Sorry guys. I mistaken. Just tested my case on pure slim/slim (3.0.0-RC3) installation. Routing doesn't work at all.
Works only $app->get('/' pattern.
For example: $app->get('/test' gives Page Not Found.
My code:
<?php

require __DIR__ . '/src/vendor/autoload.php';

$app = new \Slim\App;

$app->get('/', function ($request, $response, $args) {
    return $response->write("It works... only");
});

$app->get('/test', function ($request, $response, $args) {
    return $response->write("It doesn't works...");
});

$app->get('/hello/{name}', function ($request, $response, $args) {
    return $response->write("Hello " . $args['name']); //doesn't works too
});

$app->run();

You do have rewrite rules in .htaccess file?

Your code works for me in a clean project using the built-in PHP web server (PHP -S).

I switched to older version
  - Removing slim/slim (3.0.0-RC3)
  - Installing slim/slim (3.0.0-RC2)

Now all work just fine.
If it's my apache/.httaccess configuration problem I can give you all data you need.
But it seems very strange then.
My configuration:
Windows 10
XAMP
Apache/2.4.16 (Win32) OpenSSL/1.0.1p
PHP Version 5.6.11
Rewrite module endbled and AllowOverride All (it does not matter )
From apache access log:
::1 - - [02/Dec/2015:11:58:30 +0200] "GET /slim3/api.php HTTP/1.1" 200 6 "-" "Mozilla/5.0
::1 - - [02/Dec/2015:11:58:34 +0200] "GET /slim3/api.php/users HTTP/1.1" 404 886 "-" "Mozilla/5.0

after I switched to (3.0.0-RC2)
::1 - - [02/Dec/2015:12:44:55 +0200] "GET /slim3/api.php HTTP/1.1" 200 6 "-" "Mozilla/5.0
::1 - - [02/Dec/2015:12:44:59 +0200] "GET /slim3/api.php/users HTTP/1.1" 200 2634 "-" "Mozilla/5.0

hmm... so you're accessing your test app via:
localhost/somepath/index.php/test

?

Yes. For example route from my current app:
http://localhost:8081/slim3/api.php/users

I can confirm this issue. after updating to RC3 the routing is broken.
I'm not using .htaccess,  im on tomcat :/ (long story)
so i'm using localhost/project/public/index.php/route
it used to work normally when i change one line of code in Uri.php line 194
from
$requestUri = parse_url($env->get('REQUEST_URI'), PHP_URL_PATH);

to
$requestUri = parse_url($env->get('PHP_SELF'), PHP_URL_PATH);

after updating to the latest version, but now its broken.
here is my route file
$app->group('/', function() use ($app) {
	$app->group('/employees', function() use ($app) {
		$app->get('', 'App\Controller\View\EmployeesController:dispatch')->setName('employees');
		$app->get('/categories', 'App\Controller\View\employeesCategoriesViewController:dispatch')->setName('employeesCategories');
	});
});

I can confirm the issue too ;) Rolled back to RC2

This is a base path issue which was reported as https://github.com/slimphp/Slim/issues/1590
The fix: https://github.com/slimphp/Slim/pull/1606 is what causes this problem

Is there a fix? I'm having this same problem. Only my root path works, but anything thing else '/xxx' doesn't work... :(

authors: akrabat dukeatcoding elshobokshy geniuscd mathmarques tssvl tuupola

repo: slimphp/Slim


text:
🛑 Web MŠVVaM SR is down

In 01c21e7, Web MŠVVaM SR (https://www.minedu.sk) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Web MŠVVaM SR is back up in c4cd440 after 1 day, 7 minutes.

source: gharchive/issue

repo: slovak-egov/upptime

license: MIT

license_type: permissive

license_source: github-api


text:
Suggestion: batch uploads

Hi, it would be amazing to have the ability to batch-upload a set of letters in Word or PDF format.

Parsing Word and PDF files is a very involved task because they aren't text files. Dealing with a batch upload with multiple files is even more involved. It may be best for someone to make a new project that could deal with such things.

authors: jjgray slowe

repo: slowe/genderbias

license: mit

license_source: bigquery


text:
tokio-modbus version 0.16.1 failing to connect in several devices

I'm using tokio-modbus in several gateway for about 1 year and it working perfectly. However, when i updated the library to version 0.16.1, I was unable to connect with several devices in my system (modbus TCP). Any reason why this is happening?

Can you describe in more detail what kind of error messages you are getting?

🤔 do you have the opportunity to inspect the devices?

These are commercial devices, meters from a Brazilian company. Therefore, I do not have access to how they work. To try to help, I have two types of meters. I can connect to one of them and exchange data. With the other type, the connection fails due to timeout. It always worked with tokio-modbus up to version 0.15.0. My code implement a gateway for 27 devices, but only 4 of them connect when using tokio-modbus 0.16.1.

Alright, then we need to take a closer look at what has changed since v0.15.0.
Unfortunately I don't have much time at the moment. I'll see what I can maybe do later.

Alright, then we need to take a closer look at what has changed since v0.15.0. Unfortunately I don't have much time at the moment. I'll see what I can maybe do later.

Thanks. I found that version 0.16.0 works as well. The problem is in version 0.16.1.

Alright, then we need to take a closer look at what has changed since v0.15.0. Unfortunately I don't have much time at the moment. I'll see what I can maybe do later.

Thanks. I found that version 0.16.0 works as well. The problem is in version 0.16.1.

I realized that I had turned on the tcp-server feature, even though I wasn't using it. When I removed it and left only the tcp feature, it worked with version 0.16.1.

I don't understand how enabling the server feature could cause client-side connection failures? Please re-enable it, rebuild,  and re-test. If it does not occur again it was most likely just a hiccup of your local build and we should close this issue.

Sorry guys. It was a hardware failure. I rebooted the meters and all started to work again.
It was completely random, sometimes it worked and sometimes it didn't. There was a time when even going back to version 0.14.0 didn't work. So I came to the conclusion that the problem wasn't on tokio-modbus' side.
Thanks and sorry again.

authors: flosse gustavowd uklotzde

repo: slowtec/tokio-modbus


text:
[e2e]: generic tag main annotated slsa3

Repo: https://github.com/slsa-framework/example-package/tree/v26.0.457
Run: https://github.com/slsa-framework/example-package/actions/runs/6463965664
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.tag.main.annotated.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.tag.main.annotated.slsa3.yml
Trigger: push
Branch: v26.0.457
Date: Tue Oct 10 02:29:48 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/v26.0.458
Run: https://github.com/slsa-framework/example-package/actions/runs/6477241081
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.tag.main.annotated.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.tag.main.annotated.slsa3.yml
Trigger: push
Branch: v26.0.458
Date: Wed Oct 11 02:34:35 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/v26.0.459
Run: https://github.com/slsa-framework/example-package/actions/runs/6490480697
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.tag.main.annotated.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.tag.main.annotated.slsa3.yml
Trigger: push
Branch: v26.0.459
Date: Thu Oct 12 02:27:43 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/v26.0.460
Run: https://github.com/slsa-framework/example-package/actions/runs/6503288149
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.tag.main.annotated.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.tag.main.annotated.slsa3.yml
Trigger: push
Branch: v26.0.460
Date: Fri Oct 13 02:33:07 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/v26.0.461
Run: https://github.com/slsa-framework/example-package/actions/runs/6515014684
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.tag.main.annotated.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.tag.main.annotated.slsa3.yml
Trigger: push
Branch: v26.0.461
Date: Sat Oct 14 02:27:02 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/v26.0.462
Run: https://github.com/slsa-framework/example-package/actions/runs/6521456434
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.tag.main.annotated.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.tag.main.annotated.slsa3.yml
Trigger: push
Branch: v26.0.462
Date: Sun Oct 15 02:31:24 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/v26.0.463
Run: https://github.com/slsa-framework/example-package/actions/runs/6528249903
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.tag.main.annotated.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.tag.main.annotated.slsa3.yml
Trigger: push
Branch: v26.0.463
Date: Mon Oct 16 02:32:06 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/v26.0.464
Run: https://github.com/slsa-framework/example-package/actions/runs/6541745339
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.tag.main.annotated.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.tag.main.annotated.slsa3.yml
Trigger: push
Branch: v26.0.464
Date: Tue Oct 17 02:40:48 UTC 2023
Tests are passing now. Closing this issue.

repo: slsa-framework/slsa-github-generator


text:
Keras functional model and SHAP

I am loading a keras functional model but I am having the following error:
ValueError: Input ['[MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK] [MASK]'] is not valid. Should be a string, a list/tuple of strings or a list/tuple of integers.
The code is this:
import tensorflow as tf
from transformers import BertTokenizer
import pandas as pd
from tensorflow import keras
import shap
import scipy as sp
model = keras.models.load_model("Models//ECG//55scipts_512maxlen_7epochs.h5")
tokenizer = BertTokenizer.from_pretrained('bert-base-uncased')
df = pd.read_csv('twtud.csv')
def f(x):
token = tokenizer.encode_plus(
x,
max_length=512,
padding='max_length',
return_tensors='tf'
)
probs = model.predict([tf.cast(token.input_ids, tf.int32),
tf.cast(token.attention_mask, tf.int32)],
verbose=0)[0]
return sp.special.logit(probs[0])
X = df['text'][:10]
explainer = shap.Explainer(f, tokenizer)
shap_values = explainer(X)

model = keras.models.load_model("Models//ECG//55scipts_512maxlen_7epochs.h5")
tokenizer = BertTokenizer.from_pretrained('bert-base-uncased')
df = pd.read_csv('twtud.csv')

This script references assets that I don't have access to. Can you please update your example to include the source code required to load these assets? Please format your example in a code block so it is easier to read.

Closing, as no feedback was received.

authors: GiannisHaralabopoulos dsgibbons

repo: slundberg/shap


text:
fix sparse nonzero background case in shap and add validation test

This fixes the issue found by @suzinyou here:
https://github.com/slundberg/shap/pull/200
When adding a test, I found several additional problems that made the sparse result differ from dense when there were non-zero values in the background dataset.  I never noticed this issue previously because I've only tested the case with sparse all-zero background values.
I also manually validated locally by printing the varying indices returned by the varying groups method in both the sparse and dense case and manually comparing the two to ensure that they have the exact same indices.  This was partly how I was able to find and resolve the other issues.

Thanks!

source: gharchive/pull-request

authors: imatiach-msft slundberg


text:
Activate or deactivate checks with configuration

We are creating an internal lib with custom liveness and readiness checks.
It would be very handy if we could activate or deactivate individual checks as needed on particular microservices, where we will use that lib.
Can you please add a property like:
com.mypackage.healthcheck.RabbitMqReadyCheck.enabled=false
They should be enabled by default.
Can you please add this behaviour?

I think this is an interesting idea.

authors: brunobat xstefank

repo: smallrye/smallrye-health


text:
🛑 Dokumentasi/Foto Website (tunnel) is down

In 27daa29, Dokumentasi/Foto Website (tunnel) (https://dokumentasi.sman3palu.sch.id/owncloud) was down:

HTTP code: 530
Response time: 105 ms

Resolved: Dokumentasi/Foto Website (tunnel) is back up in bbd6a79 after 1 hour, 2 minutes.

repo: smantriplw/uptime-services


text:
🛑 CBT (Computer Based Test) Website (proxmox) is down

In 118ea39, CBT (Computer Based Test) Website (proxmox) (https://cbt.sman3palu.sch.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CBT (Computer Based Test) Website (proxmox) is back up in 3631856 after 1 day, 15 hours.


text:
🛑 Links (tunnel) is down

In 0965d91, Links (tunnel) (https://links.sman3palu.sch.id) was down:

HTTP code: 502
Response time: 839 ms

Resolved: Links (tunnel) is back up in 3828356 after 21 minutes.


text:
🛑 Website is down

In 54bc050, Website (https://sman3palu.sch.id) was down:

HTTP code: 530
Response time: 151 ms

Resolved: Website is back up in d40f91f after 8 minutes.


text:
Rebrand

This pull request depends on https://github.com/smarkets/pyinotify-smarkets/pull/4

:+1:

authors: alexdias jstasiak

repo: smarkets/pyinotify-smarkets


text:
Add examples/tests for the ws2812-spi PR  improving the fifo handling

(https://github.com/smart-leds-rs/ws2812-spi-rs/pull/12)
Also contains an example for https://github.com/smart-leds-rs/ws2812-spi-rs/pull/14

Thanks for the review @rahix! The AVR example works, but requires way more RAM & time than necessary. A ASM solution like the one in FastLED would be way better, but this should work fine for the meantime and be good enough for most applications.

repo: smart-leds-rs/smart-leds-samples


text:
L2 Flag for Optimism/Arbitrum

New Feature, once someone is assigned, need to have a quick sync

I think it's better if you describe the expected feature and then we can decide who has to be assigned to it.

closed with #289

repo: smartcontractkit/documentation


text:
[Enhancement]: Infographic to understand the Chainlink Node architecture

What would you like us to improve?
https://docs.linkpool.io/docs/general_chainlink_guide
Recommend we use something like the infographic in the above link for our CL Node related documents, and x-link to it in our docs regarding jobs, external adapters etc.  It would offer an excellent overview and ready reference to see the flow of operations and the architecture.
There are some small bits in the language that need to be disambiguated, and I can assist with that when we are putting this together.
How important it is?
The tool would dramatically improve the comprehensibility of our docs and give users a snapshot view, rather than requiring them to pore over the docs and piece together the components.

The Chainlink Architecture docs need significant improvement. An info-graphic would help with that. +1

authors: dwightjl zeuslawyer


text:
Send Requests async

Have you been thinking about adding SendAsync method ti IClient?
I've made a quick research and the biggest this is, that it would require cutting off .NET 3.5 as it does not support Task.

See previous discussion: https://github.com/smartystreets/smartystreets-dotnet-sdk/pull/1#issuecomment-257563204

Any chance this could be revisited? I have a PR ready to go adding Async and dropping 3.5 and 4.0 since they aren't supported anymore.

Typically what we have seen is for those that need direct async support, they simply wrap the synchronous call in a Task and then use the async capabilities of the Task Parallel Library.

Typically what we have seen is for those that need direct async support, they simply wrap the synchronous call in a Task and then use the async capabilities of the Task Parallel Library.

That doesn't help me with anything. Using Task.Run will just pull another thread from the thread pool and block on that thread (slowing things down even more with the overhead of doing that). I'm wanting async for scalability, not to avoid blocking on a UI thread.

Yeah i think its pretty silly there is no async api

Like, "they simply wrap the synchronous call in a Task"? Git isuses are a weird place for a standup routine, and since we all know that doesn't work it has to be a joke right?

An API client that only offers unnecessarily blocking calls on network IO does not deserve to be used in production. This is a bare minimum capability I would expect of the smarty SDK.
Its not confidence inspiring that this has been an issue since 2016.

authors: ConnorCallison Fullmight GrzesiekP joliver jumpingjackson mdwhatcott ryanjerskine

repo: smartystreets/smartystreets-dotnet-sdk


text:
Remove unused pendingTableCharactersNull dynamic property

Ticket: https://smb.myjetbrains.com/youtrack/issue/IN-429/Update-our-html5lib-php-lib-for-PHP-8.2

the only change seems to be this line:
#1 (files)

Yup. The rest is the IDE doing its job ;)

I can't tell if this property is otherwise unused.
@TheDeadJoe did you grep for it in the code base?

Yes. No occurrences. There is a property called $pendingTableCharactersDirty so at first I thought this could be just a forgotten name change, but in code it's used as a boolean value, so writing there null would make no sense.


text:
AUTOLINGO - UNKNOWN CHALLENGE TYPE: listenMatch

Popup with error: AUTOLINGO - UNKNOWN CHALLENGE TYPE: listenMatch

turn off listening exercises

repo: smintf/autolingo


text:
Scrolling Issue

Scrolling for text view at bottom is buggy

Fixed with this commit: https://github.com/smite1921/enigma-machine/commit/1140d2975b5be5f4bd93132c94c98bc8987183c7


text:
XL Search question: How are cleavable cross-link results reported? I see no MS3 hits

Not a bug report, but a question, and my apologies if this is documented somewhere. And I'm willing to concede that there's something I'm not understanding about how MS3 cleavable searches work...
When I do a DSSO cleavable cross-linker search, all of the cross-linked results I get seem to be hits to MS2 spectra and the linker mass reported is the uncleaved linker mass for DSSO. (using PepXML output)
Is MetaMorpheus, in fact, searching the MS3 spectra for peptide matches, and reporting the results at the MS2 level using the scan number for the MS2 scan that was the parent of the MS3 scans?
Or are these MS2 hits separate from MS3 ones, and I'm just not finding these in the results for some reason?
Are the scan numbers for the MS3 scans used to ID each peptide available?

Currently MS3 data isn't searched, but it's in the pipeline (PR #1551). Hopefully this version will be out within a month or so - it's got to go through code review and bug testing.

Ah OK, that would explain it! If you want some feedback about how the new data are being output to PepXML, just let me know. I'm currently adding in native support for cleavable cross-linkers and MS2 into proxl so am thinking about it quite a bit.

I think that would be very helpful, thanks. I think after US HUPO we'll have a bit more bandwidth to push some new stuff through the pipeline.
I definitely want to make sure our XL input is still readable into ProXL after these changes.

Actually followup question then: how are cleavable cross-linkers handled at the MS2 level? Is it looking in the MS2 spectra for the cleaved products and the uncleaved products for the same scans?

I believe we look for: cleaved products (short-cleave product, long-cleave product), cleaved precursor (M-short, M-long), but not uncleaved products or uncleaved precursor in the MS2 scan. I can double-check that with @lonelu .

Yes, That is what we do currently. It would be easy for us to search uncleaved products (peptide bond breaks but not crosslink bond) or uncleaved precursor but we don't do that now. I guess it depends on crosslinker bond strength and the dissociation type. We have plans to make the crosslinker cleave with certain dissociation types (i.e., HCD but not ETD) (#1509) instead of just having a true/false value in the future also.

Thanks for all the details. For the record, not suggesting that it looked for uncleaved products, just curious if it id. Thanks again.

Hi @mriffle ,
sorry for the delay of this issue. We didn't get any good MS2-MS3 type of data previously, and MS3 in general is in low res CID which is not working well for MetaMorpheus. Anyway, it is working now and we are optimizing the matching and the scoring.
Could you let me know what should I do about the output for proxl? Thanks

This sounds great, I'll get back to you soon!

Update on this issue - the XL task now reports child scan matched ions in the .tsv output, whether they be MS2 or MS3. Here's an example. It doesn't seem to be reported in the .pep.XML output, though, which I think is probably needed by proxl to interpret correctly?
Task1-XLSearchTask.zip

authors: lonelu mriffle rmillikin

repo: smith-chem-wisc/MetaMorpheus


text:
Sandbox module demand

Hello!
For my large project (website builder) I made a sandbox module.
It catches both Virtual DOM exceptions and Real DOM exceptions from executing code and instead of attaching virtual tree shows and error instead.
Using this I can give my users possibility to write they own code and to attach it in real time no matter what is inside code.
I want to publish it but not sure there is a demand. So just checking.

Thank you for sharing your work, @grimalschi. I'm not sure whether there's shareable value in this. What's the API?

Something like this

By "untrusted" I don't mean just that code can throw any kind of exception. Not secure isolation.

What kinds of errors are we expecting?

Well, there is two areas of errors. First is virtual dom and second is a real.
First area error:
h('div, {}) // Stupid mistype, but can ruin app if goes production

Second area error:
patch(document.createElement('div'), h('div', {
  attrs: {
    "\"": "test"
  }
}))

Here virtual dom is correct, but patching it to real causes DOMException: Failed to execute 'setAttribute' on 'Element': '"' is not a valid attribute name.

You can successfully wrap with try-catch first type of errors and catch all errors before patch.
But second area (real dom exceptions) are hard to catch because they are coming in the middle of patching. So whole patching process becomes broken after this.

Why is the choice of handling these errors inside a snabbdom module?

Because this is part of virtual dom. Wrong approach?

Way too early for me to determine. What is the API that you provide your users?

There is no API for users. My users know nothing about snabbdom - they just edit HTML and CSS and whatever they are writing it will not go out sandbox.

My app uses snabbdom-virtualize also, but especially sandbox is just a module without dependencies.

What module does - is when on GIF I write "whatever" and code become broken, module shows an error div instead of dom, but when I am fixing this it shows dom again.
This is just an example of applying.

If your users provide HTML, then why don't you use Element.innerHTML? Why use snabbdom at all?

Because this HTML is full of settings and on a GIF you can see them - when I drag slider. So changes like this should work fast and also this HTML can contains another DOM trees which I can not erase by innerHTML. InnerHTML is slow and removes all old elements.

Thank you for the explanations. I understand to some degree. A sandbox is kind of a user feature. The difference between this library and a user feature in terms of where they are on the stack is too great. Thus a sandbox module doesn't sit well with me. Perhaps an error handling module. And that's pretty much what the example API describes. Regarding the question of whether this repository is the right place for it — I don't feel that it would be. The API surface determines the amount of work it takes to maintain a project. And adding more surface here doesn't feel right.

Ok, probably I should make it as an external repo

What about making it a plugin?

@patomation in Snabbdom the concept of a plugin is "module".

authors: grimalschi mightyiam patomation

repo: snabbdom/snabbdom


text:
Validate EntityType

We've had requests to validate allowed types of CPF and Resource.
On the one hand, it would be a straightforward safety check that could run on a schema save and warn editors in the Issues page. On the other hand, we should consider how much client-side validation the extension should handle, or if it is better to rely more on the API for error handling. If the latter, the API error handling on incorrect CPF entityType should be improved, as it currently returns an html xdebug warning. Warning: pg_execute(): Query failed: ERROR:  null value in column &quot;entity_type&quot; violates not-null constraint

Interesting.  I think we should update the validation engine on the server to check for entity type, even if we do add that validation on the OpenRefine client side.  I would like to stop any non-JSON error messages before they make it out to the user.

authors: deternitydx glassjoseph


text:
fix: input unit

resolved #379

It is still one pixel off. It would be good to figure out why it is not the same location as the placeholder and fix the root cause instead of just trying to hit the correct value by a random offset. Otherwise it may look off on other screens and Diete is presumed to be run on many different screens.

authors: agazso hlavkat


text:
Type alias for readabilty

@snakefoot your opinion please
(I think case it's not that needed, but in other cases it could help us removing boilerplate stuff)

I have no real opinion. Both styles works for me. Just like that one tries to use a single style.

repo: snakefoot/NLog


text:
install error

Dear @antunderwood.
mamba create -c conda-forge -c bioconda -n snakemake snakemake

                  __    __    __    __
                 /  \  /  \  /  \  /  \
                /    \/    \/    \/    \
███████████████/  /██/  /██/  /██/  /████████████████████████
              /  / \   / \   / \   / \  \____
             /  /   \_/   \_/   \_/   \    o \__,
            / _/                       \_____/  `
            |/
        ███╗   ███╗ █████╗ ███╗   ███╗██████╗  █████╗
        ████╗ ████║██╔══██╗████╗ ████║██╔══██╗██╔══██╗
        ██╔████╔██║███████║██╔████╔██║██████╔╝███████║
        ██║╚██╔╝██║██╔══██║██║╚██╔╝██║██╔══██╗██╔══██║
        ██║ ╚═╝ ██║██║  ██║██║ ╚═╝ ██║██████╔╝██║  ██║
        ╚═╝     ╚═╝╚═╝  ╚═╝╚═╝     ╚═╝╚═════╝ ╚═╝  ╚═╝

        mamba (1.2.0) supported by @QuantStack

        GitHub:  https://github.com/mamba-org/mamba
        Twitter: https://twitter.com/QuantStack

█████████████████████████████████████████████████████████████

Looking for: ['snakemake']

warning  libmamba Could not parse mod/etag header
warning  libmamba Could not parse mod/etag header
warning  libmamba Could not parse mod/etag header
warning  libmamba Could not parse mod/etag header
warning  libmamba Could not parse mod/etag header
warning  libmamba Could not parse mod/etag header
bioconda/osx-64                                               No change
bioconda/noarch                                               No change
filesystem error: last_write_time: Permission denied ["/Users/liam/opt/miniconda3/pkgs/cache/3e39a7aa.json"]

# >>>>>>>>>>>>>>>>>>>>>> ERROR REPORT <<<<<<<<<<<<<<<<<<<<<<

    Traceback (most recent call last):
      File "/Users/liam/opt/miniconda3/lib/python3.9/site-packages/conda/exceptions.py", line 1124, in __call__
        return func(*args, **kwargs)
      File "/Users/liam/opt/miniconda3/lib/python3.9/site-packages/mamba/mamba.py", line 936, in exception_converter
        raise e
      File "/Users/liam/opt/miniconda3/lib/python3.9/site-packages/mamba/mamba.py", line 929, in exception_converter
        exit_code = _wrapped_main(*args, **kwargs)
      File "/Users/liam/opt/miniconda3/lib/python3.9/site-packages/mamba/mamba.py", line 887, in _wrapped_main
        result = do_call(parsed_args, p)
      File "/Users/liam/opt/miniconda3/lib/python3.9/site-packages/mamba/mamba.py", line 754, in do_call
        exit_code = create(args, parser)
      File "/Users/liam/opt/miniconda3/lib/python3.9/site-packages/mamba/mamba.py", line 630, in create
        return install(args, parser, "create")
      File "/Users/liam/opt/miniconda3/lib/python3.9/site-packages/mamba/mamba.py", line 497, in install
        index = load_channels(pool, channels, repos)
      File "/Users/liam/opt/miniconda3/lib/python3.9/site-packages/mamba/utils.py", line 129, in load_channels
        index = get_index(
      File "/Users/liam/opt/miniconda3/lib/python3.9/site-packages/mamba/utils.py", line 110, in get_index
        is_downloaded = dlist.download(api.MAMBA_DOWNLOAD_FAILFAST)
    RuntimeError: filesystem error: last_write_time: Permission denied ["/Users/liam/opt/miniconda3/pkgs/cache/3e39a7aa.json"]

`$ /Users/liam/opt/miniconda3/bin/mamba create -c conda-forge -c bioconda -n snakemake snakemake`

  environment variables:
                 CIO_TEST=<not set>
        CONDA_DEFAULT_ENV=base
                CONDA_EXE=/Users/liam/opt/miniconda3/bin/conda
             CONDA_PREFIX=/Users/liam/opt/miniconda3
    CONDA_PROMPT_MODIFIER=(base)
         CONDA_PYTHON_EXE=/Users/liam/opt/miniconda3/bin/python
               CONDA_ROOT=/Users/liam/opt/miniconda3
              CONDA_SHLVL=1
           CURL_CA_BUNDLE=<not set>
     JAVA_LD_LIBRARY_PATH=/Users/liam/opt/miniconda3/lib/jvm/lib/server
               LD_PRELOAD=<not set>
                     PATH=/Users/liam/opt/miniconda3/bin:/Users/liam/opt/miniconda
                          3/condabin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:
                          /usr/sbin:/sbin:/usr/local/ncbi/blast/bin:/Library/TeX/texbin:/opt/X11
                          /bin:/Library/Frameworks/Mono.framework/Versions/Current/Commands:/var
                          /run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:
                          /var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/v
                          ar/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleint
                          ernal/bin
       REQUESTS_CA_BUNDLE=<not set>
            SSL_CERT_FILE=<not set>

     active environment : base
    active env location : /Users/liam/opt/miniconda3
            shell level : 1
       user config file : /Users/liam/.condarc
 populated config files : /Users/liam/.condarc
          conda version : 23.1.0
    conda-build version : not installed
         python version : 3.9.15.final.0
       virtual packages : __archspec=1=x86_64
                          __osx=13.6.6=0
                          __unix=0=0
       base environment : /Users/liam/opt/miniconda3  (writable)
      conda av data dir : /Users/liam/opt/miniconda3/etc/conda
  conda av metadata url : None
           channel URLs : https://conda.anaconda.org/conda-forge/osx-64
                          https://conda.anaconda.org/conda-forge/noarch
                          https://conda.anaconda.org/bioconda/osx-64
                          https://conda.anaconda.org/bioconda/noarch
                          https://repo.anaconda.com/pkgs/main/osx-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/osx-64
                          https://repo.anaconda.com/pkgs/r/noarch
          package cache : /Users/liam/opt/miniconda3/pkgs
                          /Users/liam/.conda/pkgs
       envs directories : /Users/liam/opt/miniconda3/envs
                          /Users/liam/.conda/envs
               platform : osx-64
             user-agent : conda/23.1.0 requests/2.31.0 CPython/3.9.15 Darwin/22.6.0 OSX/13.6.6
                UID:GID : 501:20
             netrc file : None
           offline mode : False

An unexpected error has occurred. Conda has prepared the above report.

I just tried running mamba create -c conda-forge -c bioconda -n snakemake snakemake and it went fine.
If the error persists, than it probably is something with either your mamba/conda instalation or your filesystem (you are getting a Permission denied error).

authors: fgvieira liamxg

repo: snakemake/snakemake


text:
style: display link to newly created space at the end of the page

We should change the message "Soon will appear here" and the position to be in bottom of the page, we can use a Check icon with the message "Space is ready" with a link to the space under. We can add a manual delay of 10sec to make sure it will be indexed by thegraph.

Maybe instead of waiting 10sec, we can just try to call the subgraph for the space and show a checkmark once we see it's finally indexed.

repo: snapshot-labs/sx-ui


text:
🛑 Snap! Wiki is down

In 25c0cd4, Snap! Wiki (https://snapwiki.miraheze.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Snap! Wiki is back up in d45e8fa.

repo: snapwiki/SnapWikiUptime


text:
[1.1.9] Class 'Predis\Profile\Factory' not found

Hi,
When upgrading from 1.1.8 to 1.1.9, this error popped.
Fatal error: Class 'Predis\Profile\Factory' not found in vendor/snc/redis-bundle/Snc/RedisBundle/DependencyInjection/SncRedisExtension.php on line 158
PHP Fatal error:  Class 'Predis\Profile\Factory' not found in vendor/snc/redis-bundle/Snc/RedisBundle/DependencyInjection/SncRedisExtension.php on line 158
Script Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::clearCache handling the post-update-cmd event terminated with an exception

Going back to 1.1.8 solved the problem for now.

See #172

authors: iammichiel snc

repo: snc/SncRedisBundle


text:
Newbie question on adding extra content to footer

Hi, I'd like to add extra content to the footer of my website but don't quite know  how to do it. I know there is the extrafooter block in footer.html (discussed here) but how can I add stuff to that from conf.py?
I would just love to add couple of Licence logos (CC 4.0 BY-SA and GPLv3) to the footer and have been searching for a solution to achieve that. Thanks, in advance!

This page in the Sphinx docs explains how to add stuff to an existing block.
For the extrafooter block, you need to put a new HTML file into your templates_path (usually /_templates), with the following content:
{% extends "!footer.html" %}
{% block extrafooter %}

new example link

    {{ super() }}
{% endblock %}

Here's an example from a project of mine.

Please close this @ericholscher

authors: Blendify HTenkanen christianspecht


text:
Scala Core: Remove resolutionRepos from BuildSettings (Closes #390)

To make the module compilable.

Looks unusual to me, too. But that line has:
Dependencies.resolutionRepos
and there is no such thing in Dependencies.scala file:
https://github.com/snowplow/iglu/blob/develop/0-common/scala-core/project/Dependencies.scala
You removed that line your previous commit:
https://github.com/snowplow/iglu/commit/e7821c021dd8431b1015d64fe7b3de9732b5ce9f#diff-fec9746d8dc3c96432f568d3c5623da4

Should be part of https://github.com/snowplow/iglu/issues/385

Merged into https://github.com/snowplow/iglu/issues/385

authors: chuwy szareiangm

repo: snowplow/iglu


text:
Detect sensible int ranges

We want to restrict to signed/unsigned, and use 2/4/8 byte ranges [1]
[1] http://docs.aws.amazon.com/redshift/latest/dg/r_Numeric_types201.html

Example schema created manually: https://github.com/snowplow/iglu-central/blob/master/schemas/org.w3/PerformanceTiming/jsonschema/1-0-0

What about zero and negative minimum?
Redshift defines negative ranges. But example schema defines minimum as 0.
We actually could detect both, but does it make any sense since Redshift don't care?

It's a good question. Redshift is perhaps a bad example because it's constraints are informational only.
In a database like Postgres or Oracle, it's very easy to enforce a constraint such as "this field must not contain a negative number". So it feels to me like the important things are:

Determining what int byte size is needed to hold the number
Determining whether the number is always positive, is always negative, or can be both

Does that make sense?

AFAIK, in Postgres this constraint is only about >0 and not like unsigned Int, so always positive maximum remains +32767, right?

Hey @chuwy - I think so:

http://stackoverflow.com/questions/20810134/why-unsigned-integer-is-not-available-in-postgresql
http://www.postgresql.org/docs/8.1/static/ddl-constraints.html

BTW - I am sure we will end up making some tweaks to schema-guru after you've worked on a first iglu-utils release. Because iglu-utils will make the required relationships JSON Schemas<>database tables more clear...

authors: alexanderdean chuwy

repo: snowplow/schema-guru


text:
Add dictionary of flags for contexts

So mobile context can be switched on and off

Closing as the upcoming version 2.0 allows the configuration of contexts we want to track passing the TrackerConfiguration object.
See issue #558

authors: AlexBenny alexanderdean

repo: snowplow/snowplow-objc-tracker


text:
Scala Common Enrich: correctly parse url hosts which contain underscores

There is a bug in the JDK which gives back null when retrieving the host of an URI which contains an underscore: https://bugs.java.com/bugdatabase/view_bug.do?bug_id=6587184.
scala> new java.net.URI("http://www.psychic_bazaar.com/oracles/119-psycards-deck.html?view=print#detail")
res0: java.net.URI = http://www.psychic_bazaar.com/oracles/119-psycards-deck.html?view=print#detail

scala> .getHost
res2: String = null

could be explored at the same time as #3880

Handled by #3880.

authors: BenFradet benjben

repo: snowplow/snowplow


text:
About clean lambda in loss calculation

Hi, thank you for the interesting work and its codes.
I have a question about the loss calculation in the code.
In the imagenet directory, the loss for obtaining saliency map is calculated as follows:
    loss=clean_lam * criterion (image,target)

However, in the case of others ('tiny-imagenet' and 'cifar' code),
the loss for obtaining saliency map is calculated as follows:
    loss=2*clean_lam*criterion (image,target)/num_classes

Is there any special reason to calculate the loss for generating a saliency map in a different way?

Hello!
Please note that

When clean_lam is positive, we update networks using aggregated gradients from clean and mixup data.
We used BCE for CIFAR and Tiny-ImageNet (codes borrowed from manifold mixup), and CE for ImageNet (codes borrowed from CutMix) for mixup data loss.
We fixed the saliency calculation method that we used CE for all datasets. (The kind of saliency loss functions do not matter much for the performance)

So the problem is that gradient scales between gradients from CE (saliency calculation with clean data) and gradients from BCE (mixup data) is different. We tried to rebalance gradient scales so that we can use an identical hyperparameter (clean_lam) regardless of the setting.
Hope this helps!

Thank you for the fast answer!

repo: snu-mllab/PuzzleMix


text:
🛑 Archives is down

In 597f5fa, Archives (https://archives.sochara.org) was down:

HTTP code: 502
Response time: 466 ms

Resolved: Archives is back up in dcc116d after .

repo: sochara-org/status


text:
Dependency not found

Error:Failed to resolve: com.hannesdorfmann.mosby3:mvi-conductor:3.0.0-alhpa1

https://search.maven.org/#artifactdetails|com.hannesdorfmann.mosby3|mvi-conductor|3.0.0-alpha1|aar
Maybe it just took some time until it was synced with repo

oops there was a typo in alpha1

Thanks

repo: sockeqwe/mosby-conductor


text:
sio::socket::impl::on_close() crashed in webrtc

Process:               NDMeeting [57251]
Path:                  /Users/USER/Documents/*/xxxx.app/Contents/MacOS/NDMeeting
Identifier:            cn.nd.ndmeetig
Version:               1.2.9
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           NDMeeting [57251]
User ID:               501
Date/Time:             2021-03-05 11:17:53.996 +0800
OS Version:            Mac OS X 10.14.6 (18G84)
Report Version:        12
Bridge OS Version:     4.6 (17P6610)
Anonymous UUID:        7F0AE481-B1B4-BACE-7E4D-97C69BA9F610
Time Awake Since Boot: 910000 seconds
System Integrity Protection: enabled
Crashed Thread:        22
Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY
Application Specific Information:
terminating with uncaught exception of type std::__1::system_error: mutex lock failed: Invalid argument
abort() called
Thread 0:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	0x00007fff5adf31d6 __close_nocancel + 10
1   libsystem_c.dylib             	0x00007fff5ad4194c fclose + 92
2   cn.nd.ndmeetig                	0x0000000105584dd6 webrtc::FileWrapper::Close() + 22 (file_wrapper.cc:116)
3   cn.nd.ndmeetig                	0x0000000105559b36 rtc::FileRotatingStream::~FileRotatingStream() + 118 (file_rotating_stream.cc:194)
4   cn.nd.ndmeetig                	0x000000010555aa9e rtc::CallSessionFileRotatingStream::~CallSessionFileRotatingStream() + 14 (file_rotating_stream.h:144)
5   cn.nd.ndmeetig                	0x00000001055844fa rtc::CallSessionFileRotatingLogSink::~CallSessionFileRotatingLogSink() + 42 (log_sinks.cc:74)
6   cn.nd.ndmeetig                	0x0000000105bf99cb -[RTCFileLogger dealloc] + 27 (RTCFileLogger.mm:83)
7   cn.nd.ndmeetig                	0x000000010535f99b -[NdRtcEngine .cxx_destruct] + 123 (ndrtc_engine.mm:45)
8   libobjc.A.dylib               	0x00007fff594eac18 object_cxxDestructFromClass(objc_object*, objc_class*) + 127
9   libobjc.A.dylib               	0x00007fff594e3792 objc_destructInstance + 76
10  libobjc.A.dylib               	0x00007fff594e3735 object_dispose + 19
11  cn.nd.ndmeetig                	0x000000010534729d -[NdRtcEngine dealloc] + 205 (ndrtc_engine.mm:66)
12  cn.nd.ndmeetig                	0x0000000105360e62 NdrtcEngineAdapter::initialize(NDSDK::RtcContext const&) + 34 (ndrtc_sdk-adapter.mm:30)
13  cn.nd.ndmeetig                	0x000000010533e822 MeetingWorkFlowMgr::initRtcHelper() + 98 (meeting_workflow_mgr.cpp:1566)
14  cn.nd.ndmeetig                	0x000000010533de94 MeetingWorkFlowMgr::start(NDSDK::tagMeetingStartParam&) + 68 (meeting_workflow_mgr.cpp:188)
15  cn.nd.ndmeetig                	0x000000010537efae non-virtual thunk to NDSDK::CMeetingServiceImpl::start(NDSDK::tagMeetingStartParam&) + 94
16  cn.nd.ndmeetig                	0x0000000105325291 LoginDialog::p_join(QString, QString, QString) + 545 (login_dialog_mac.mm:348)
17  cn.nd.ndmeetig                	0x0000000105324063 LoginDialog::on_sig_meetingCreated(int, QString) + 163 (login_dialog_mac.mm:252)
18  cn.nd.ndmeetig                	0x0000000105327421 QtPrivate::FunctorCall<QtPrivate::IndexesList<0, 1>, QtPrivate::List<int, QString>, void, void (LoginDialog::)(int, QString)>::call(void (LoginDialog::)(int, QString), LoginDialog*, void**) + 65 (qobjectdefs_impl.h:152)
19  org.qt-project.QtCore         	0x0000000107396cff QObject::event(QEvent*) + 943
20  org.qt-project.QtWidgets      	0x00000001062f1a3a QWidget::event(QEvent*) + 4698
21  org.qt-project.QtWidgets      	0x00000001062b5f5a QApplicationPrivate::notify_helper(QObject*, QEvent*) + 266
22  org.qt-project.QtWidgets      	0x00000001062b73e6 QApplication::notify(QObject*, QEvent*) + 598
23  org.qt-project.QtCore         	0x000000010736b9f4 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 212
24  org.qt-project.QtCore         	0x000000010736cbe9 QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 809
25  libqcocoa.dylib               	0x00000001092d00e9 0x109297000 + 233705
26  libqcocoa.dylib               	0x00000001092d0858 0x109297000 + 235608
27  com.apple.CoreFoundation      	0x00007fff2ed35683 CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION + 17
28  com.apple.CoreFoundation      	0x00007fff2ed35629 __CFRunLoopDoSource0 + 108
29  com.apple.CoreFoundation      	0x00007fff2ed18feb __CFRunLoopDoSources0 + 195
30  com.apple.CoreFoundation      	0x00007fff2ed185b5 __CFRunLoopRun + 1189
31  com.apple.CoreFoundation      	0x00007fff2ed17ebe CFRunLoopRunSpecific + 455
32  com.apple.HIToolbox           	0x00007fff2df771ab RunCurrentEventLoopInMode + 292
33  com.apple.HIToolbox           	0x00007fff2df76ee5 ReceiveNextEventCommon + 603
34  com.apple.HIToolbox           	0x00007fff2df76c76 _BlockUntilNextEventMatchingListInModeWithFilter + 64
35  com.apple.AppKit              	0x00007fff2c30f79d _DPSNextEvent + 1135
36  com.apple.AppKit              	0x00007fff2c30e48b -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361
37  com.apple.AppKit              	0x00007fff2c3085a8 -[NSApplication run] + 699
38  libqcocoa.dylib               	0x00000001092cf5d3 0x109297000 + 230867
39  org.qt-project.QtCore         	0x0000000107367a7f QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) + 431
40  org.qt-project.QtCore         	0x000000010736c002 QCoreApplication::exec() + 130
41  cn.nd.ndmeetig                	0x0000000105327cde main + 206
42  libdyld.dylib                 	0x00007fff5acbd3d5 start + 1
Thread 1:
0   libsystem_pthread.dylib       	0x00007fff5aeb03f0 start_wqthread + 0
Thread 2:
0   libsystem_pthread.dylib       	0x00007fff5aeb03f0 start_wqthread + 0
Thread 3:: com.apple.NSEventThread
0   libsystem_kernel.dylib        	0x00007fff5adf222a mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff5adf276c mach_msg + 60
2   com.apple.CoreFoundation      	0x00007fff2ed191ee __CFRunLoopServiceMachPort + 328
3   com.apple.CoreFoundation      	0x00007fff2ed1875c __CFRunLoopRun + 1612
4   com.apple.CoreFoundation      	0x00007fff2ed17ebe CFRunLoopRunSpecific + 455
5   com.apple.AppKit              	0x00007fff2c3174c2 _NSEventThread + 175
6   libsystem_pthread.dylib       	0x00007fff5aeb12eb _pthread_body + 126
7   libsystem_pthread.dylib       	0x00007fff5aeb4249 _pthread_start + 66
8   libsystem_pthread.dylib       	0x00007fff5aeb040d thread_start + 13
Thread 4:: Qt bearer thread
0   libsystem_kernel.dylib        	0x00007fff5adfa36e poll + 10
1   org.qt-project.QtCore         	0x00000001073c353a qt_safe_poll(pollfd*, unsigned int, timespec const*) + 90
2   org.qt-project.QtCore         	0x00000001073c4f31 QEventDispatcherUNIX::processEvents(QFlagsQEventLoop::ProcessEventsFlag) + 833
3   org.qt-project.QtCore         	0x0000000107367a7f QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) + 431
4   org.qt-project.QtCore         	0x00000001071978e3 QThread::exec() + 131
5   org.qt-project.QtCore         	0x0000000107198849 0x107176000 + 141385
6   libsystem_pthread.dylib       	0x00007fff5aeb12eb _pthread_body + 126
7   libsystem_pthread.dylib       	0x00007fff5aeb4249 _pthread_start + 66
8   libsystem_pthread.dylib       	0x00007fff5aeb040d thread_start + 13
Thread 5:: QNetworkAccessManager thread
0   libsystem_kernel.dylib        	0x00007fff5adfa36e poll + 10
1   org.qt-project.QtCore         	0x00000001073c353a qt_safe_poll(pollfd*, unsigned int, timespec const*) + 90
2   org.qt-project.QtCore         	0x00000001073c4f31 QEventDispatcherUNIX::processEvents(QFlagsQEventLoop::ProcessEventsFlag) + 833
3   org.qt-project.QtCore         	0x0000000107367a7f QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) + 431
4   org.qt-project.QtCore         	0x00000001071978e3 QThread::exec() + 131
5   org.qt-project.QtCore         	0x0000000107198849 0x107176000 + 141385
6   libsystem_pthread.dylib       	0x00007fff5aeb12eb _pthread_body + 126
7   libsystem_pthread.dylib       	0x00007fff5aeb4249 _pthread_start + 66
8   libsystem_pthread.dylib       	0x00007fff5aeb040d thread_start + 13
Thread 6:: Thread (pooled)
0   libsystem_kernel.dylib        	0x00007fff5adf586a __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5aeb456e _pthread_cond_wait + 722
2   org.qt-project.QtCore         	0x00000001071a06bf 0x107176000 + 173759
3   org.qt-project.QtCore         	0x00000001071a038e 0x107176000 + 172942
4   org.qt-project.QtCore         	0x00000001071a02ad QWaitCondition::wait(QMutex*, QDeadlineTimer) + 93
5   org.qt-project.QtCore         	0x00000001071a021e QWaitCondition::wait(QMutex*, unsigned long) + 62
6   org.qt-project.QtCore         	0x000000010719ce44 0x107176000 + 159300
7   org.qt-project.QtCore         	0x0000000107198849 0x107176000 + 141385
8   libsystem_pthread.dylib       	0x00007fff5aeb12eb _pthread_body + 126
9   libsystem_pthread.dylib       	0x00007fff5aeb4249 _pthread_start + 66
10  libsystem_pthread.dylib       	0x00007fff5aeb040d thread_start + 13
Thread 7:
0   libsystem_pthread.dylib       	0x00007fff5aeb03f0 start_wqthread + 0
Thread 8:
0   libsystem_pthread.dylib       	0x00007fff5aeb03f0 start_wqthread + 0
Thread 9:
0   libsystem_kernel.dylib        	0x00007fff5adf227e semaphore_timedwait_trap + 10
1   libdispatch.dylib             	0x00007fff5ac70c99 _dispatch_sema4_timedwait + 76
2   libdispatch.dylib             	0x00007fff5ac71377 _dispatch_semaphore_wait_slow + 58
3   libdispatch.dylib             	0x00007fff5ac7e1fd _dispatch_worker_thread + 317
4   libsystem_pthread.dylib       	0x00007fff5aeb12eb _pthread_body + 126
5   libsystem_pthread.dylib       	0x00007fff5aeb4249 _pthread_start + 66
6   libsystem_pthread.dylib       	0x00007fff5aeb040d thread_start + 13
Thread 10:: com.apple.CFSocket.private
0   libsystem_kernel.dylib        	0x00007fff5adf961a __select + 10
1   com.apple.CoreFoundation      	0x00007fff2ed46b72 __CFSocketManager + 635
2   libsystem_pthread.dylib       	0x00007fff5aeb12eb _pthread_body + 126
3   libsystem_pthread.dylib       	0x00007fff5aeb4249 _pthread_start + 66
4   libsystem_pthread.dylib       	0x00007fff5aeb040d thread_start + 13
Thread 11:
0   libsystem_kernel.dylib        	0x00007fff5adf5f32 __semwait_signal + 10
1   libsystem_c.dylib             	0x00007fff5ad81914 nanosleep + 199
2   libc++.1.dylib                	0x00007fff57ef2dc4 std::__1::this_thread::sleep_for(std::__1::chrono::duration<long long, std::__1::ratio<1l, 1000000000l> > const&) + 73
3   cn.nd.ndmeetig                	0x00000001054b26a1 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_deletestd::__1::__thread_struct >, owt::conference::ConferenceSocketSignalingChannel::OnReconnectionTicket(std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > const&)::$_30> >(void*) + 65 (thread:283)
4   libsystem_pthread.dylib       	0x00007fff5aeb12eb _pthread_body + 126
5   libsystem_pthread.dylib       	0x00007fff5aeb4249 _pthread_start + 66
6   libsystem_pthread.dylib       	0x00007fff5aeb040d thread_start + 13
Thread 12:: peerconnection_dependency_factory_thread
0   libsystem_kernel.dylib        	0x00007fff5adf878e kevent + 10
1   cn.nd.ndmeetig                	0x00000001055778db rtc::PhysicalSocketServer::kq_dispatch(int, int, bool) + 283 (physical_socket_server.cc:2166)
2   cn.nd.ndmeetig                	0x0000000105562b3c rtc::MessageQueue::Get(rtc::Message*, int, bool) + 1292 (message_queue.cc:330)
3   cn.nd.ndmeetig                	0x00000001055829a3 rtc::Thread::ProcessMessages(int) + 115 (thread.cc:526)
4   cn.nd.ndmeetig                	0x0000000105582698 rtc::Thread::PreRun(void*) + 88 (thread.cc:68)
5   libsystem_pthread.dylib       	0x00007fff5aeb12eb _pthread_body + 126
6   libsystem_pthread.dylib       	0x00007fff5aeb4249 _pthread_start + 66
7   libsystem_pthread.dylib       	0x00007fff5aeb040d thread_start + 13
Thread 13:: worker_thread
0   libsystem_kernel.dylib        	0x00007fff5adf878e kevent + 10
1   cn.nd.ndmeetig                	0x00000001055778db rtc::PhysicalSocketServer::kq_dispatch(int, int, bool) + 283 (physical_socket_server.cc:2166)
2   cn.nd.ndmeetig                	0x0000000105562b3c rtc::MessageQueue::Get(rtc::Message*, int, bool) + 1292 (message_queue.cc:330)
3   cn.nd.ndmeetig                	0x0000000105582a0e rtc::Thread::ProcessMessages(int) + 222 (thread.cc:526)
4   cn.nd.ndmeetig                	0x0000000105582698 rtc::Thread::PreRun(void*) + 88 (thread.cc:68)
5   libsystem_pthread.dylib       	0x00007fff5aeb12eb _pthread_body + 126
6   libsystem_pthread.dylib       	0x00007fff5aeb4249 _pthread_start + 66
7   libsystem_pthread.dylib       	0x00007fff5aeb040d thread_start + 13
Thread 14:: signaling_thread
0   libsystem_kernel.dylib        	0x00007fff5adf878e kevent + 10
1   cn.nd.ndmeetig                	0x00000001055778db rtc::PhysicalSocketServer::kq_dispatch(int, int, bool) + 283 (physical_socket_server.cc:2166)
2   cn.nd.ndmeetig                	0x0000000105562b3c rtc::MessageQueue::Get(rtc::Message*, int, bool) + 1292 (message_queue.cc:330)
3   cn.nd.ndmeetig                	0x0000000105582a0e rtc::Thread::ProcessMessages(int) + 222 (thread.cc:526)
4   cn.nd.ndmeetig                	0x0000000105582698 rtc::Thread::PreRun(void*) + 88 (thread.cc:68)
5   libsystem_pthread.dylib       	0x00007fff5aeb12eb _pthread_body + 126
6   libsystem_pthread.dylib       	0x00007fff5aeb4249 _pthread_start + 66
7   libsystem_pthread.dylib       	0x00007fff5aeb040d thread_start + 13
Thread 15:: network_thread
0   libsystem_kernel.dylib        	0x00007fff5adf878e kevent + 10
1   cn.nd.ndmeetig                	0x00000001055778db rtc::PhysicalSocketServer::kq_dispatch(int, int, bool) + 283 (physical_socket_server.cc:2166)
2   cn.nd.ndmeetig                	0x0000000105562b3c rtc::MessageQueue::Get(rtc::Message*, int, bool) + 1292 (message_queue.cc:330)
3   cn.nd.ndmeetig                	0x0000000105582a0e rtc::Thread::ProcessMessages(int) + 222 (thread.cc:526)
4   cn.nd.ndmeetig                	0x0000000105582698 rtc::Thread::PreRun(void*) + 88 (thread.cc:68)
5   libsystem_pthread.dylib       	0x00007fff5aeb12eb _pthread_body + 126
6   libsystem_pthread.dylib       	0x00007fff5aeb4249 _pthread_start + 66
7   libsystem_pthread.dylib       	0x00007fff5aeb040d thread_start + 13
Thread 16:: network_thread 0x0x7fb756c7dab0
0   libsystem_kernel.dylib        	0x00007fff5adf878e kevent + 10
1   cn.nd.ndmeetig                	0x00000001055778db rtc::PhysicalSocketServer::kq_dispatch(int, int, bool) + 283 (physical_socket_server.cc:2166)
2   cn.nd.ndmeetig                	0x0000000105562b3c rtc::MessageQueue::Get(rtc::Message*, int, bool) + 1292 (message_queue.cc:330)
3   cn.nd.ndmeetig                	0x00000001055829a3 rtc::Thread::ProcessMessages(int) + 115 (thread.cc:526)
4   cn.nd.ndmeetig                	0x0000000105582698 rtc::Thread::PreRun(void*) + 88 (thread.cc:68)
5   libsystem_pthread.dylib       	0x00007fff5aeb12eb _pthread_body + 126
6   libsystem_pthread.dylib       	0x00007fff5aeb4249 _pthread_start + 66
7   libsystem_pthread.dylib       	0x00007fff5aeb040d thread_start + 13
Thread 17:: worker_thread 0x0x7fb756c7dc10
0   libsystem_kernel.dylib        	0x00007fff5adf586a __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5aeb456e _pthread_cond_wait + 722
2   cn.nd.ndmeetig                	0x0000000105552605 rtc::Event::Wait(int, int) + 549 (event.cc:181)
3   cn.nd.ndmeetig                	0x000000010556bf32 rtc::NullSocketServer::Wait(int, bool) + 18 (null_socket_server.cc:25)
4   cn.nd.ndmeetig                	0x0000000105562b3c rtc::MessageQueue::Get(rtc::Message*, int, bool) + 1292 (message_queue.cc:330)
5   cn.nd.ndmeetig                	0x0000000105582a0e rtc::Thread::ProcessMessages(int) + 222 (thread.cc:526)
6   cn.nd.ndmeetig                	0x0000000105582698 rtc::Thread::PreRun(void*) + 88 (thread.cc:68)
7   libsystem_pthread.dylib       	0x00007fff5aeb12eb _pthread_body + 126
8   libsystem_pthread.dylib       	0x00007fff5aeb4249 _pthread_start + 66
9   libsystem_pthread.dylib       	0x00007fff5aeb040d thread_start + 13
Thread 18:: signaling_thread 0x0x7fb756c7c950
0   libsystem_kernel.dylib        	0x00007fff5adf586a __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5aeb456e _pthread_cond_wait + 722
2   cn.nd.ndmeetig                	0x0000000105552605 rtc::Event::Wait(int, int) + 549 (event.cc:181)
3   cn.nd.ndmeetig                	0x000000010556bf32 rtc::NullSocketServer::Wait(int, bool) + 18 (null_socket_server.cc:25)
4   cn.nd.ndmeetig                	0x0000000105562b3c rtc::MessageQueue::Get(rtc::Message*, int, bool) + 1292 (message_queue.cc:330)
5   cn.nd.ndmeetig                	0x0000000105582a0e rtc::Thread::ProcessMessages(int) + 222 (thread.cc:526)
6   cn.nd.ndmeetig                	0x0000000105582698 rtc::Thread::PreRun(void*) + 88 (thread.cc:68)
7   libsystem_pthread.dylib       	0x00007fff5aeb12eb _pthread_body + 126
8   libsystem_pthread.dylib       	0x00007fff5aeb4249 _pthread_start + 66
9   libsystem_pthread.dylib       	0x00007fff5aeb040d thread_start + 13
Thread 19:: CVDisplayLink
0   libsystem_kernel.dylib        	0x00007fff5adf586a __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5aeb45a1 _pthread_cond_wait + 773
2   com.apple.CoreVideo           	0x00007fff30a85797 CVDisplayLink::waitUntil(unsigned long long) + 229
3   com.apple.CoreVideo           	0x00007fff30a84d46 CVDisplayLink::runIOThread() + 482
4   libsystem_pthread.dylib       	0x00007fff5aeb12eb _pthread_body + 126
5   libsystem_pthread.dylib       	0x00007fff5aeb4249 _pthread_start + 66
6   libsystem_pthread.dylib       	0x00007fff5aeb040d thread_start + 13
Thread 20:: CVDisplayLink
0   libsystem_kernel.dylib        	0x00007fff5adf586a __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5aeb45a1 _pthread_cond_wait + 773
2   com.apple.CoreVideo           	0x00007fff30a85797 CVDisplayLink::waitUntil(unsigned long long) + 229
3   com.apple.CoreVideo           	0x00007fff30a84d46 CVDisplayLink::runIOThread() + 482
4   libsystem_pthread.dylib       	0x00007fff5aeb12eb _pthread_body + 126
5   libsystem_pthread.dylib       	0x00007fff5aeb4249 _pthread_start + 66
6   libsystem_pthread.dylib       	0x00007fff5aeb040d thread_start + 13
Thread 21:
0   libsystem_pthread.dylib       	0x00007fff5aeb03f0 start_wqthread + 0
Thread 22 Crashed:
0   libsystem_kernel.dylib        	0x00007fff5adf82c6 __pthread_kill + 10
1   libsystem_pthread.dylib       	0x00007fff5aeb3bf1 pthread_kill + 284
2   libsystem_c.dylib             	0x00007fff5ad626a6 abort + 127
3   libc++abi.dylib               	0x00007fff57f3e641 abort_message + 231
4   libc++abi.dylib               	0x00007fff57f3e7c7 default_terminate_handler() + 243
5   libobjc.A.dylib               	0x00007fff594f1eeb _objc_terminate() + 105
6   libc++abi.dylib               	0x00007fff57f4a19e std::__terminate(void ()()) + 8
7   libc++abi.dylib               	0x00007fff57f49f86 __cxxabiv1::failed_throw(__cxxabiv1::__cxa_exception) + 27
8   libc++abi.dylib               	0x00007fff57f3cf99 __cxa_throw + 113
9   libc++.1.dylib                	0x00007fff57f300e7 std::__1::__throw_system_error(int, char const*) + 77
10  libc++.1.dylib                	0x00007fff57eea96d std::__1::mutex::lock() + 29
11  cn.nd.ndmeetig                	0x0000000105e3b60c sio::socket::impl::on_close() + 108
12  cn.nd.ndmeetig                	0x0000000105e46b0b boost::asio::detail::wait_handler<std::__1::__bind<void (sio::socket::impl::)(), sio::socket::impl>, boost::asio::detail::io_object_executorboost::asio::executor >::do_complete(void*, boost::asio::detail::scheduler_operation*, boost::system::error_code const&, unsigned long) + 219
13  cn.nd.ndmeetig                	0x0000000105e437b6 boost::asio::detail::scheduler::do_run_one(boost::asio::detail::conditionally_enabled_mutex::scoped_lock&, boost::asio::detail::scheduler_thread_info&, boost::system::error_code const&) + 806
14  cn.nd.ndmeetig                	0x0000000105e431a2 boost::asio::detail::scheduler::run(boost::system::error_code&) + 258
15  cn.nd.ndmeetig                	0x0000000105e4b3a7 sio::client_impl::run_loop() + 71
16  cn.nd.ndmeetig                	0x0000000105e53e3e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_deletestd::__1::__thread_struct >, std::__1::__bind<void (sio::client_impl::)(), sio::client_impl> > >(void*) + 62
17  libsystem_pthread.dylib       	0x00007fff5aeb12eb _pthread_body + 126
18  libsystem_pthread.dylib       	0x00007fff5aeb4249 _pthread_start + 66
19  libsystem_pthread.dylib       	0x00007fff5aeb040d thread_start + 13
Thread 23:
0   libsystem_kernel.dylib        	0x00007fff5adf586a __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5aeb456e _pthread_cond_wait + 722
2   cn.nd.ndmeetig                	0x0000000105e4366b boost::asio::detail::scheduler::do_run_one(boost::asio::detail::conditionally_enabled_mutex::scoped_lock&, boost::asio::detail::scheduler_thread_info&, boost::system::error_code const&) + 475
3   cn.nd.ndmeetig                	0x0000000105e431a2 boost::asio::detail::scheduler::run(boost::system::error_code&) + 258
4   cn.nd.ndmeetig                	0x0000000105e4304c boost::asio::detail::posix_thread::funcboost::asio::detail::resolver_service_base::work_scheduler_runner::run() + 60
5   cn.nd.ndmeetig                	0x0000000105e42fe0 boost_asio_detail_posix_thread_function + 16
6   libsystem_pthread.dylib       	0x00007fff5aeb12eb _pthread_body + 126
7   libsystem_pthread.dylib       	0x00007fff5aeb4249 _pthread_start + 66
8   libsystem_pthread.dylib       	0x00007fff5aeb040d thread_start + 13
Thread 24:
0   libsystem_kernel.dylib        	0x00007fff5adf5f32 __semwait_signal + 10
1   libsystem_c.dylib             	0x00007fff5ad81914 nanosleep + 199
2   libc++.1.dylib                	0x00007fff57ef2dc4 std::__1::this_thread::sleep_for(std::__1::chrono::duration<long long, std::__1::ratio<1l, 1000000000l> > const&) + 73
3   cn.nd.ndmeetig                	0x00000001054b26a1 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_deletestd::__1::__thread_struct >, owt::conference::ConferenceSocketSignalingChannel::OnReconnectionTicket(std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > const&)::$_30> >(void*) + 65 (thread:283)
4   libsystem_pthread.dylib       	0x00007fff5aeb12eb _pthread_body + 126
5   libsystem_pthread.dylib       	0x00007fff5aeb4249 _pthread_start + 66
6   libsystem_pthread.dylib       	0x00007fff5aeb040d thread_start + 13
Thread 25:: CVDisplayLink
0   libsystem_kernel.dylib        	0x00007fff5adf586a __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5aeb45a1 _pthread_cond_wait + 773
2   com.apple.CoreVideo           	0x00007fff30a85797 CVDisplayLink::waitUntil(unsigned long long) + 229
3   com.apple.CoreVideo           	0x00007fff30a84d46 CVDisplayLink::runIOThread() + 482
4   libsystem_pthread.dylib       	0x00007fff5aeb12eb _pthread_body + 126
5   libsystem_pthread.dylib       	0x00007fff5aeb4249 _pthread_start + 66
6   libsystem_pthread.dylib       	0x00007fff5aeb040d thread_start + 13
Thread 26:: CVDisplayLink
0   libsystem_kernel.dylib        	0x00007fff5adf586a __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5aeb45a1 _pthread_cond_wait + 773
2   com.apple.CoreVideo           	0x00007fff30a85797 CVDisplayLink::waitUntil(unsigned long long) + 229
3   com.apple.CoreVideo           	0x00007fff30a84d46 CVDisplayLink::runIOThread() + 482
4   libsystem_pthread.dylib       	0x00007fff5aeb12eb _pthread_body + 126
5   libsystem_pthread.dylib       	0x00007fff5aeb4249 _pthread_start + 66
6   libsystem_pthread.dylib       	0x00007fff5aeb040d thread_start + 13
Thread 27:: CVDisplayLink
0   libsystem_kernel.dylib        	0x00007fff5adf586a __psynch_cvwait + 10
1   libsystem_pthread.dylib       	0x00007fff5aeb45a1 _pthread_cond_wait + 773
2   com.apple.CoreVideo           	0x00007fff30a85797 CVDisplayLink::waitUntil(unsigned long long) + 229
3   com.apple.CoreVideo           	0x00007fff30a84d46 CVDisplayLink::runIOThread() + 482
4   libsystem_pthread.dylib       	0x00007fff5aeb12eb _pthread_body + 126
5   libsystem_pthread.dylib       	0x00007fff5aeb4249 _pthread_start + 66
6   libsystem_pthread.dylib       	0x00007fff5aeb040d thread_start + 13
Thread 28:
0   libsystem_kernel.dylib        	0x00007fff5adf49de __ulock_wait + 10
1   libsystem_pthread.dylib       	0x00007fff5aeb56de _pthread_join + 358
2   libc++.1.dylib                	0x00007fff57f30148 std::__1::thread::join() + 24
3   cn.nd.ndmeetig                	0x0000000105e49fe5 sio::client_impl::~client_impl() + 133
4   cn.nd.ndmeetig                	0x0000000105e36cf6 sio::client::~client() + 22
5   cn.nd.ndmeetig                	0x00000001054a5f97 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_deletestd::__1::__thread_struct >, owt::conference::ConferenceSocketSignalingChannel::~ConferenceSocketSignalingChannel()::$_0> >(void*) + 167 (thread:283)
6   libsystem_pthread.dylib       	0x00007fff5aeb12eb _pthread_body + 126
7   libsystem_pthread.dylib       	0x00007fff5aeb4249 _pthread_start + 66
8   libsystem_pthread.dylib       	0x00007fff5aeb040d thread_start + 13
Thread 22 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000  rbx: 0x00007000076ab000  rcx: 0x00007000076aa5e8  rdx: 0x0000000000000000
rdi: 0x000000000001ec73  rsi: 0x0000000000000006  rbp: 0x00007000076aa620  rsp: 0x00007000076aa5e8
r8: 0x00007000076aa4b0   r9: 0x00007000076aa680  r10: 0x0000000000000000  r11: 0x0000000000000206
r12: 0x000000000001ec73  r13: 0x0000003000000008  r14: 0x0000000000000006  r15: 0x000000000000002d
rip: 0x00007fff5adf82c6  rfl: 0x0000000000000206  cr2: 0x00007fff9150a188

I've solved it


text:
GNUInstallDirs should be included before usage of CMAKE_INSTALL_INCLUDEDIR

If it's included too late, the interface directory will not be populated.
Currently:
$ cmake -B _builds -D CMAKE_INSTALL_PREFIX=${HOME}/opt/sioclient
$ cmake --build _builds --target install

$ grep INTERFACE_INCLUDE_DIRECTORIES ${HOME}/opt/sioclient/lib/cmake/sioclient/sioclientTargets.cmake || echo FAIL
FAIL

As a workaround, CMAKE_INSTALL_INCLUDEDIR can be added explicitly:
$ cmake -B _builds -D CMAKE_INSTALL_PREFIX=${HOME}/opt/sioclient -D CMAKE_INSTALL_INCLUDEDIR=include
$ cmake --build _builds --target install

$ grep INTERFACE_INCLUDE_DIRECTORIES ${HOME}/opt/sioclient/lib/cmake/sioclient/sioclientTargets.cmake || echo FAIL
  INTERFACE_INCLUDE_DIRECTORIES "${_IMPORT_PREFIX}/include"
  INTERFACE_INCLUDE_DIRECTORIES "${_IMPORT_PREFIX}/include"

With this patch:
$ cmake -B _builds -D CMAKE_INSTALL_PREFIX=${HOME}/opt/sioclient
$ cmake --build _builds --target install

$ grep INTERFACE_INCLUDE_DIRECTORIES ${HOME}/opt/sioclient/lib/cmake/sioclient/sioclientTargets.cmake || echo FAIL
  INTERFACE_INCLUDE_DIRECTORIES "${_IMPORT_PREFIX}/include"
  INTERFACE_INCLUDE_DIRECTORIES "${_IMPORT_PREFIX}/include"

Wow so, weird. Thank you for fixing this!

As soon as the build succeeds I'll merge.

authors: jmigual ruslo


text:
superfluous argument in invocation

here in the method invocation there is a second argument responders which is not in the method definition, and I looked back some months it looks like it hasn't been used in quite awhile if ever.
Just leaving this issue here as a reminder to delete the second arg in the invocation, or if someone objects  to call it up.

I should mention also, it's confusing when the argument name in the invocation is different from the argument name in the definition.  In this case it's api in the invocation and ss in the definition.  It should probably be api in the definition as well.

Looks good.

authors: arxpoetica kulicuu

repo: socketstream/socketstream


text:
MMseqs2 as a shared library ?

Hi,
Would it be possible to use MMseqs2 as a shared-library ?
Any examples how to do blastp like search ?
Regards,

MMseqs2 can not be used as shared library but it can be compiled in other projects. @milot-mirdita do you have documentation for this?

Could you give us a short description of what you want to achieve?
We do not support using MMseqs2 as a shared library, especially since we use exit() for aborting in error conditions. You probably don't want your libraries to kill your application.

Shared libraries are usually loaded in many popular scripting languages (i.e. Julia, Python, R)
https://docs.julialang.org/en/release-0.6/manual/calling-c-and-fortran-code/
https://docs.python.org/3/library/ctypes.html
https://www.rdocumentation.org/packages/base/versions/3.4.3/topics/dyn.load
I could call externally command line tool, but library could more elegant.
Basically I would like to obtain BLAST-like bit-scores in all-vs-all comparisons between multiple fasta files.

Sorry, that will not work (at least not without a lot of refactoring).
Our error handling would just kill the whole python/r/julia process. You could hack our EXIT macro, but then you would be leaking memory.
Do you want all-against-all exact Smith-Waterman alignments (like SWIPE) or also the prefiltering stage?

Whole pipeline including pre-filtering. But it's ok if not possible. I was just curious. You can close this issue.

authors: martin-steinegger mashu milot-mirdita


text:
🛑 Subs EU is down

In c1a88a8, Subs EU (https://subscene.eu.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Subs EU is back up in 646997b after 25 minutes.

repo: softsub/uptime


text:
Add HTTP headers to

Feature Request
It would be nice to be able to specify HTTP headers for SvgUri.
Why it is needed
Sometimes the server could serve a different variant of the SVG file depending on client features like dark contrast or inverted colours.
Possible implementation
It would just need on addition property headers which is modelled after the default ImageURISource prop.
Code sample
export type UriProps = {
  uri: string | null;
  headers?: { [name:string]: string };
} & AdditionalProps;

export async function fetchText(uri: string, headers?: {[name:string]: string}) {
  const response = await fetch(uri, { headers });
  return await response.text();
}

export function SvgUri(props: UriProps) {
  const { onError = err, uri, headers } = props;
  const [xml, setXml] = useState<string | null>(null);
  useEffect(() => {
    uri
      ? fetchText(uri, headers)
          .then(setXml)
          .catch(onError)
      : setXml(null);
  }, [onError, uri, headers]);
  return <SvgXml xml={xml} override={props} />;
}

Worth a PR?
The caller would need to ensure that headers is stable, or it would cause unnecessary re-rerenders.

@bot its a feature request not a bug. The template looks totally different and I filled out everything.

Hello @pke,
Could you provide an example of how it can be useful? For instance, it can be a private API for which we can give headers to authorize. Do you know if there is another example?

authors: bohdanprog pke

repo: software-mansion/react-native-svg


text:
[BUG] Signature Generation Discrepancy between starknet.js and starknet_py

What happened
I'm encountering an issue when comparing signatures generated by starknet.js and starknet_py. I've verified that both scripts generate the same transaction_hash, but despite this, the produced signatures are different.

Create two separate scripts, one in JavaScript using starknet.js and one in Python using starknet_py.
In both scripts, use the same private key (set the key in the env) and transaction parameters (hardcodded in the github script).
Verify that both scripts generate the same transaction_hash.
Generate the signature using signTransaction on starknet.js and sign_invoke_v1 on starknet_py.
Compare the obtained signatures.

I've uploaded both scripts used for this test in this repository: Github repo
Current Result
Despite the same transaction_hash being generated in both scripts and the same private_key used for signing, the signatures produced by starknet.js and starknet_py are different.
Expected Result
I would expect that, given the same transaction_hash and private key, both libraries would generate the same signature.
Environment

starknet_py version: 0.23.0
starknet.js version: 6.11.0

Support Request
Considering that the transaction_hash is identical in both scripts, is there any known difference in the signing process between starknet.js and starknet_py that could explain this discrepancy?
I appreciate any assistance or guidance on how to resolve this discrepancy. If additional information or details about my setup are needed, I'll be happy to provide them. The test scripts are available in the linked repository above for a more in-depth review. Thank you
Stack trace
No error, the signatures do not match.
Despite the same transaction_hash being generated in both scripts and the same private_key used for signing, the signatures produced by starknet.js and starknet_py are different.
Steps to reproduce
I've uploaded both scripts used for this test in this repository: Github repo
There is a README in the repo with all the information to run both scripts.
Steps to Reproduce

Create two separate scripts, one in JavaScript using starknet.js and one in Python using starknet_py.
In both scripts, use the same private key (set the key in the env) and transaction parameters (hardcodded in the github script).
Verify that both scripts generate the same transaction_hash.
Generate the signature using signTransaction on starknet.js and sign_invoke_v1 on starknet_py.
Compare the obtained signatures.

SDK Version
0.23.0
Python version
3.10.14
What operating system are you using?
Mac
Is there an existing issue for this?

[X] I have searched the existing issues and verified no issue exits for this problem.

hey @eugypalu , thanks for report, will see handle it today and update you 👍 .

@eugypalu the discrepancy comes from different seed value in a function from crypto_cpp_py.
Seed in this function has a default value of 32, when in starknet.js it's 0. It looks like we maye have a small mistake, but I need to confirm it. Will update you on this.

Seed causes that signature is different, however it's still correct (it's checked by cpp_verify) and the discrepancy  between other SDKs and starknet.py is not a bug. Closing.

authors: eugypalu franciszekjob


text:
Bring bach Ledger device model to nanox

Feature Request
self-descriptive

Blocked by https://github.com/LedgerHQ/app-starknet/issues/45


text:
Even More Endpoints

Adds a few more endpoints:

Getting

[[https://spec.matrix.org/v1.1/client-server-api/#get_matrixclientv3roomsroomideventeventid][getRoomEvent]]
[[https://spec.matrix.org/v1.1/client-server-api/#get_matrixclientv3roomsroomidjoined_members][getRoomMembers]]
[[https://spec.matrix.org/v1.1/client-server-api/#get_matrixclientv3roomsroomidstate][getRoomState]]
[[https://spec.matrix.org/v1.1/client-server-api/#get_matrixclientv3roomsroomidstateeventtypestatekey][getRoomStateEvent]]
[[https://spec.matrix.org/v1.1/client-server-api/#get_matrixclientv3roomsroomidmessages][getRoomMessages]]

Sending

[[https://spec.matrix.org/v1.1/client-server-api/#put_matrixclientv3roomsroomidstateeventtypestatekey][sendRoomStateEvent]]
[[https://spec.matrix.org/v1.1/client-server-api/#put_matrixclientv3roomsroomidsendeventtypetxnid][sendMessageEvent]]
[[https://spec.matrix.org/v1.1/client-server-api/#client-behaviour][redact]]

This branch is forked off my other current API branch. I figured it would be easier to review as a separate PR, but the other one should get merged first.

Thanks, could you please rebase it?

Thanks, could you please rebase it?

yeah, hows ti look now?

I have also sent you an invite for write access to the project, this project is currently missing a proper CONTRIBUTING.md doc, but it should have this mentioned: https://github.com/byorgey/swarm/blob/main/CONTRIBUTING.md#i-have-push-access-to-the-swarm-repository-now-what

Did something weird happen with this merge? I don't see any of the changes on master

Something very wrong happen indeed. The repository has been replicated from the original remote (https://softwarefactory-project.io/r/admin/repos/software-factory/matrix-client-haskell) using an old commit. It used to not do that unless there is a change merged there, and I guess it did a git push -f nonetheless.
I was not able to replicate the exact merge commit produced by GitHub, thus I ran the following command on c7dcf50cbcb672eef8fd6aa47c525f01cd4b84be:
git fetch https://github.com/softwarefactory-project/matrix-client-haskell refs/pull/14/head
git rebase FETCH_HEAD
git fetch https://github.com/softwarefactory-project/matrix-client-haskell refs/pull/15/head
git rebase FETCH_HEAD
git push git@github.com/softwarefactory-project/matrix-client-haskell

which should get us back to the last state.

authors: TristanCacqueray solomon-b


text:
feat: tune the generated Scala CLI project according to the guidelines

The following suggestions were implemented:

entry about importing Scala CLI project to popular IDEs (Metals / IntelliJ) was added to the generated README.md
project files (*.sc) were renamed to *.scala so that IDEs are not confused, what is more test.sc was renamed to build.test.scala to better reflect its intent
comment-based using notation is used in the generated project files as it is the recommended way of doing it

Note that .gitignore was not introduced as it is a good candidate for both Build tools and as such will be added as a part of separate PR.
Part of #194

Thx :)

authors: adamw geminicaprograms

repo: softwaremill/adopt-tapir


text:
Loading custom config files in elasticmq native

Fixes #368
With those changes it is possible to start the docker with mounted custom config via command docker run --rm -it --publish 9324:9324 -v /path/to/elasticmq.conf:/opt/elasticmq.conf softwaremill/elasticmq-native. Before, the path was /opt/docker/elasticmq.conf which was not compliant with standard elasticmq image.
I have also added few classes to reflect-config.json as the application was failing with NoClassDefFoundError

👍

Thx a lot for the fix!
I'm now using the native version. ❤

authors: mchmielarz wojciechUrbanski yanns

repo: softwaremill/elasticmq


text:
Upgrading to Akka 2.4

Akka 2.4.0 has been out for two months and it's binary compatible with 2.3.x.
A simple change in the build.sbt allows Reactive Kafka to use Akka 2.4.0.

OK, we are good to go with 2.4.0, thx.

I'm not sure about this one, if 2.3 is binary compatible with 2.4, why would we constrain the users of the library and require 2.4? It would make sense if we used some 2.4 features, but otherwise I think it would be better to leave 2.3, no?

Actually you've got a point. Also Akka 2.4 hasn't got support for Scala
2.10 - I'm not in front of a computer now so I can't check if
reactive-kafka is cross built for 2.10.
Could it be a good idea to have a branch that supports 2.4 instead of
having that on master or you would prefer just users to upgrade Akka at
their own will?
On Mon, 23 Nov 2015 at 08:13, Adam Warski notifications@github.com wrote:

I'm not sure about this one, if 2.3 is binary compatible with 2.4, why
would we constrain the users of the library and require 2.4? It would make
sense if we used some 2.4 features, but otherwise I think it would be
better to leave 2.3, no?
—
Reply to this email directly or view it on GitHub
https://github.com/softwaremill/reactive-kafka/pull/54#issuecomment-158874186
.

Right, @adamw has a point. I missed that it doesn't support 2.10 too - that's also important. Akka-streams 2.0 is going to support Akka 2.3 so let's keep a single branch for now.

authors: adamw kciesielski manub

repo: softwaremill/reactive-kafka


text:
如何用workflow的httptask 发送一个post请求，来用于访问Restful的服务器

如何用workflow的httptask 发送一个post请求，来用于访问Restful的服务器
看例子好像是get方式的请求，暂时在HttpRequest类中没有找到相应的方法
比如用curl命令发一个post请求： curl -X POST http://ip:port/func  -F 'file=@"123.jpg"'  -F "rotate=true"

@boookc

An experiment code: https://github.com/chanchann/workflow_annotation/tree/main/demos/14_restful

authors: Barenboim boookc chanchann

repo: sogou/workflow


text:
Update the name of antigen plugin in README

added a pointer to the current branch

:+1:

authors: VladimirSinitsin soimort

repo: soimort/translate-shell

license: unlicense


text:
Animate.css transitions has no callback and leads to bug with specific positions settings

For example:
Take an element with data-position="top" and piano initialized with slideContent: true.
When it appears, it goes on the top of the screen. When click out the keyboard container, the whole container slides down, but not behind visible part of the screen: it's still here, with its opacity to 0 but in the foreground so you can click on the keys and change the input.
PRO TIP:  answer's here: https://github.com/daneden/animate.css#usage

Fixed this with display: none in hide function and display: block in display function. The problem is caused by scaling keyboard.

authors: hugohil kucherenkovova

repo: soixantecircuits/piano


text:
unexpected cabal-version higher than 2.2 cannot be specified as a range

If I try to specify cxx-options: -std=c++11  I get:

- 19:23:
unexpected cabal-version higher than 2.2 cannot be specified as a range. See https://github.com/haskell/cabal/issues/4899
expecting ".", "-", white space, "&&" or "||"

>= 2.2

The referenced issue is https://github.com/haskell/cabal/issues/4899, but I don't know enough to know how that relates to this this. I guess it's something sufficiently new in cabal that it isn't supported in hpack, and to that end:
I see this in the the hpack readme:

Note: Hpack does not require you to specify a cabal-version manually. When generating a .cabal file, Hpack sets the cabal-version automatically based on the features that are used.

Perhaps it's worth documenting what the latest known working cabal-version is (and perhaps warning when going beyond it, as a I presume 2.2 is?).

It used to be that the Cabal file had to have something like this:
cabal-version: >= 1.10

As of Cabal 2.0, the following syntax was allowed:
cabal-version: 2.0 -- essentially means ">= 2.0"

As of Cabal 2.2, that syntax was required. hpack needs to choose the appropriate syntax for the given version of Cabal.

The designated workaround for this would be:
verbatim:
  cabal-version: 2.2

However, Cabal won't accept that neither as cabal-version is now required to be at the beginning of the file.
Not even comments are allowed before cabal-version anymore.  This is problematic as hpack puts a header comment at the beginning of the file.  It's not yet clear to me what's the best way to address this.

As I understand it, the following steps will be required to address this:

We have to put the cabal-version at beginning of the generated cabal file, even before the header.  This will make calculating the file hash more convoluted; it's ugly but solvable.
When cabal-version is 2.1 or higher, we have to skip the >= when rendering.

Also if I manually edit the generated .cabal to put cabal-version: 2.2 at the top, I then get:
unexpected Unknown SPDX license identifier: 'BSD3' Do you mean BSD-3-Clause?

If I also manually set license:  BSD-3-Clause then it works.
I'm not sure other licenses have also been changed.
Shall I open a separate issue for this, or keep it all on this one?

@dukedave yes, separate issue please.  It may also make sense to make the cabal devs aware that those breaking changes impact users.  While I'm able to capture the motivation behind the cabal-version change, the breaking change to license is hard to justify by my book (but of course, I may not have the full picture here).

@tfausak we still have to address this in hpack, as Hpack users usually do not set cabal-version explicitly.

Unrecognized license used to be a warning, now it's an error (even though confusingly it says warning in the output).
So the license change are actually two breaking changes, firstly warnings are errors now, secondly e.g. BSD3 is not accepted anymore.
no comment

Btw, should it be spdx-license? spdx defines more than just license I assume?

Hmm, spdx-license is better, yes. I don't know if it's worth trying to be too smart here: if people are on cabal-version: 2.2 or later, can we tell them to just use spdx-license rather than license? Detecting that in hpack would be nice, but I don't think it can be perfect in the presence of verbatim and fields we don't want to parse too deeply.

Hmm, from a technical point of view this sounds like a solid solution.
From a users point of view I'm still puzzled whether asking users to change license to spdx-license and BSD3 to BSD-3-clause as soon as they use e.g. cxx-options is justified.  They are semantically the same and odds are that many users just don't care and just want to hack on stuff and continue build their packages.
This whole SPDX change mainly matters for GPL licensed stuff, but most Haskell packages are either in-house or BSD3/MIT anyway.

Bottom line: I'm still tempted to map at least some of the license to SPDX transparently.
I think it's safe to do so where there is a one-to-one correspondence between traditional cabal and SPDX, which is e.g. the case for MIT/BSD.
For e.g. GPL2 it's less clear what to do, as it could mean GPL-2.0-only or GPL-2.0-or-later.  Apparently Hackage maps to GPL-2.0-only, so we could follow that.

One more thing regarding licenses: I haven't read this in the official spec, but some people say SPDX license are case insensitive.  However, Cabal parses them cases sensitive.

https://spdx.org/spdx-license-list/matching-guidelines:

4. Capitalization
4.1 Purpose:  To avoid the possibility of a non-match due to lower case or upper case letters in otherwise the same words.
4.1.1 Guideline:  All upper case and lower case letters should be treated as lower case letters. Templates do not include markup for this guideline.

Thanks @tfausak. Do we want to shim this in hpack?

I opened https://github.com/sol/hpack/issues/296 for the remaining issue with SPDX license identifiers (case sensitive matching).

@dukedave released to Hackage as 0.29.0.  Please test!

authors: dukedave quasicomputational sol tfausak

repo: sol/hpack


text:
add multi-choice proposals in UI

It supports the creation and display of the multi-choice proposals in the UI.
The summary of the changes: https://gist.github.com/0xShuk/fdb2a8118dc795f03abde5e880d73661
Screenshots:

Test Proposal Links:
Proposal: https://solscan.io/account/FjyuvDQnRkix37P4qqQGSn9JuiX92VbPv4Xz8Lm8grxA?cluster=devnet
Create Proposal TX: https://solscan.io/tx/9ayjfcgWwKbyE23zFLcwQ5w4NAvNhBryYMwfmaF5ihMJ1cBSzJrgwfg1xb7Qdrs3p1JqtwqraCbcndC5VsMwDic?cluster=devnet
Vote TX: https://solscan.io/tx/5TwJ55LyXfrEdt18ZH1tjEiJj1ZhyZcg2QrfwndycaML2wnZoHEFmTcYETPSv9Uoi2wz2qsRR2tPkd2oYaGXMRaA?cluster=devnet

Left a few more comments here and on discord. Aside from that looks good enough to me. I would like it better if new.tsx was refactored such that the executable form's code (state, handlers, etc) and the multi choice were totally separate, and they just had a parent that stored title, description, and isMulti. But this is also fine enough.

We made a simple token transfer proposal and our entire UI keeps crashing and is now unusable due to this error

Seems like it has something to do with this feature. We're also using an older version of the program

We made a simple token transfer proposal and our entire UI keeps crashing and is now unusable due to this error

Seems like it has something to do with this feature. We're also using an older version of the program

It's fixed now. Thanks for pointing out.

authors: 0xShuk asktree billythedummy

repo: solana-labs/governance-ui


text:
I have transferred Wweth from Solana to Eth, but it has not arrived

https://explorer.solana.com/tx/24B4bwwCF7FL3pjHJfWKV4nXVrDs5BRoaqSGS6SvoUFerRYmJcYRj7q3kHhAh3wAaaZjWoyy2Mwx3EF2e7KGNNos
I have transferred Wweth from Solana to Eth, but it has not arrived

My account of eth: 0xE3666187c7Fbd30ea514a00747f27BeF2Df27d69

I transfered 0.2 wWETH

have you checked the bottom table? you need to connect both wallets and select the correct token so the transactions show up

Hola Juan, perdona que no te pudiera esperar ayer, soy español, el tema es que pase weth por el wormhole y me dieron wWeth, pero no puede hacer swap en ninguna pool, entonces pasé los wweth por wormhole otra vez pero para la red eth, y es cuando no me han llegado a metamask, abajo en el historial sale no data

The transaction was successfully processed by the Wormhole network, but the client-side transaction submission may have failed. Try clearing your cache and reloading wormholebridge.com to see if the transaction can be completed there. Make sure both wallets are connected.
If wormholebridge.com doesn't work, you can manually submit the signed VAA bytes below to the submitVAA method on the Wormhole contract: https://etherscan.io/address/0xf92cd566ea4864356c5491c177a430c222d7e678#writeContract

Digest (for reference only): 3fcea92ff77a3b6cf8ee081de8a493e2919a3603d53a4608b0c708abd069f240
Signed VAA bytes to submit to the contract:

0x01000000010d00a90f1d5506a47f88c591335cbf263bde1ef9471064d35ff368734db16497a1564578b5a93e184d8bfdfd083cd857b417a7226b425cf32580a08312eccb5a0e0401018a8a40d8ca0b0d032953d8be5336995764e579231b5835e5e3fd1a1dc584f1f5604599404a8541163e7c65230f23e4f2f4666b1b4912237a8f0dcb40c007cbb70103f6741414d9e667c7c4e9a8aa2a6de961e3eff21e1778e0d6f13dc5dcef695e261cf1dd201152308907d83ae2b6028725ff28384448701d8e410d0a58cef2fbc30004fa8e454c0e3501d6fa13dfe2f4fec62340b14a3e28d00ebf314576c9390ab26a1902cb5a0cc899ec6fab3aa7272855658f49eddd27b3cc25dac6475dc6f03f6001055da6ab22b6dd5f867b8e1d9ad9a8d28523f03cf6ca7785e2e38c4e35aaa028521c2ed2fc5f8cde32a90d1f8fa8a2dca7017658d528fe2a94625b35f447e9243100079063bc1b854d4c275cc77d567623a93fadc412fc9333c83b3a1e15d34777819e49e740c9e56e43a9ff14b5ab4bad811969d1880ac456d06bd20bde4af10d4f770108c61bc00a468f42e33df7b9c2d67a16ce71d5f3f5328cf279cd1450f96c746d1a0d111d12fca3d0caf4f88531513ede6c085e7ae60038d722bbe73985d360b01f00099bf01e74139b752cf38b4f1914028c7ac51d77e5edc3ba063db22c52792e75aa4d176b60bb3c118d380b27a50ecb97367dea9fca52383e2c1caa7313a82461c9010a9512db81c6dbe8f15132552a99342466750a14d4e48c7d46552a271e5d89fce77d64d4305ade710cfae0a0c83b30d05d1df394ef443515d431fa44711705e6e7000bcfdebca010a0ed4e5b6678dc982fce485cdbe17c5b742d61de5b9bff145b28d418a8ebd8fc148be480e3251863191a19012d0cc98f851292f3b8854b32ddd1bb000d42ac9953a5bdfbdb93b1b1626f5cd0fb349e601dd36cb854778aec917448fffa5108feb6998f49ab8545c33d23a1c3cbf438449fe0986983bf3e2a1111e6da1f00101e2fc98df6c1a07920936eae3b79a6a8c22a7f07e94c17764be471272cb713971e908beaef70fdcde7a3a4631fff32f3ce1492dc49fd7ed3bcb3e5f98f73d1eb0011a4f5f5394b92e29b6c4422c909c421afc6d777aab9705457f2cfd68cd2ab236c7fd45cb6496a9df863f40f78f66e32cb1985049e479b2d3761e61bca4acf020b006130d6b7100001440a0102a8440201f407e0456fa0247ba42dfdd779dac402b5afeda387134c2f54ddc3a4000000000000000000000000e3666187c7fbd30ea514a00747f27bef2df27d6902000000000000000000000000c02aaa39b223fe8d0a0e5c4f27ead9083c756cc209000000000000000000000000000000000000000000000000000000000bebc200

I am traianus in the discord, all right, it has worked, thank you very much!
El vie, 3 sept 2021 a las 14:30, Leopold Schabel @.***>)
escribió:

The transaction was successfully processed by the Wormhole network, but
the client-side transaction submission may have failed. Try clearing your
cache and reloading wormholebridge.com to see if the transaction can be
completed there. Make sure both wallets are connected.
If wormholebridge.com doesn't work, you can manually submit the signed
VAA bytes below to the submitVAA method on the Wormhole contract:
https://etherscan.io/address/0xf92cd566ea4864356c5491c177a430c222d7e678#writeContract
Digest (for reference only):
3fcea92ff77a3b6cf8ee081de8a493e2919a3603d53a4608b0c708abd069f240
Signed VAA bytes to submit to the contract:
0x01000000010d00a90f1d5506a47f88c591335cbf263bde1ef9471064d35ff368734db16497a1564578b5a93e184d8bfdfd083cd857b417a7226b425cf32580a08312eccb5a0e0401018a8a40d8ca0b0d032953d8be5336995764e579231b5835e5e3fd1a1dc584f1f5604599404a8541163e7c65230f23e4f2f4666b1b4912237a8f0dcb40c007cbb70103f6741414d9e667c7c4e9a8aa2a6de961e3eff21e1778e0d6f13dc5dcef695e261cf1dd201152308907d83ae2b6028725ff28384448701d8e410d0a58cef2fbc30004fa8e454c0e3501d6fa13dfe2f4fec62340b14a3e28d00ebf314576c9390ab26a1902cb5a0cc899ec6fab3aa7272855658f49eddd27b3cc25dac6475dc6f03f6001055da6ab22b6dd5f867b8e1d9ad9a8d28523f03cf6ca7785e2e38c4e35aaa028521c2ed2fc5f8cde32a90d1f8fa8a2dca7017658d528fe2a94625b35f447e9243100079063bc1b854d4c275cc77d567623a93fadc412fc9333c83b3a1e15d34777819e49e740c9e56e43a9ff14b5ab4bad811969d1880ac456d06bd20bde4af10d4f770108c61bc00a468f42e33df7b9c2d67a16ce71d5f3f5328cf279cd1450f96c746d1a0d111d12fca3d0caf4f88531513ede6c085e7ae60038d722bbe73985d360b01f00099bf01e74139b752cf38b4f1914028c7ac51d77e5edc3ba063db22c52792e75aa4d176b60bb3c118d380b27a50ecb97367dea9fca52383e2c1caa7313a82461c9010a9512db81c6dbe8f15132552a99342466750a14d4e48c7d46552a271e5d89fce77d64d4305ade710cfae0a0c83b30d05d1df394ef443515d431fa44711705e6e7000bcfdebca010a0ed4e5b6678dc982fce485cdbe17c5b742d61de5b9bff145b28d418a8ebd8fc148be480e3251863191a19012d0cc98f851292f3b8854b32ddd1bb000d42ac9953a5bdfbdb93b1b1626f5cd0fb349e601dd36cb854778aec917448fffa5108feb6998f49ab8545c33d23a1c3cbf438449fe0986983bf3e2a1111e6da1f00101e2fc98df6c1a07920936eae3b79a6a8c22a7f07e94c17764be471272cb713971e908beaef70fdcde7a3a4631fff32f3ce1492dc49fd7ed3bcb3e5f98f73d1eb0011a4f5f5394b92e29b6c4422c909c421afc6d777aab9705457f2cfd68cd2ab236c7fd45cb6496a9df863f40f78f66e32cb1985049e479b2d3761e61bca4acf020b006130d6b7100001440a0102a8440201f407e0456fa0247ba42dfdd779dac402b5afeda387134c2f54ddc3a4000000000000000000000000e3666187c7fbd30ea514a00747f27bef2df27d6902000000000000000000000000c02aaa39b223fe8d0a0e5c4f27ead9083c756cc209000000000000000000000000000000000000000000000000000000000bebc200
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/solana-labs/oyster/issues/242#issuecomment-912501523,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVOST323O3YZE4G4DXXNPIDUAC5VRANCNFSM5DJLOJHQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

authors: leoluk traianus1 yamijuan

repo: solana-labs/oyster


text:
logo changed TruSwap token

I'm submitting a ...
[ ] bug report
[ ] feature request
[ ] question about the decisions made in the repository
[ ] question about how to use this project

Summary

Other information (e.g. detailed explanation, stack traces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)

hello sir i'm send here PR for my issue. and you just all time reply on email. close and Merged. but not explain 1 time where i'm going for clear this problam. my token logo dnot show in wallet and solscan. plz
and not send me same again close and Merged just tell me how to fix this thanks
https://github.com/solana-labs/token-list/pull/22107

@spacemandev-git

this is my logo and show here
https://github.com/solana-labs/token-list/tree/main/assets/mainnet/2TocBpcDms9xWB9oGBo1Pek3bZDhbBtFRNUkSYbQ9N5P
and show in list https://raw.githubusercontent.com/solana-labs/token-list/main/src/tokens/solana.tokenlist.json
this https://github.com/Msaqib0786/crypto/blob/main/logo.png
but not show on wallet and solscan just clear this my prblm

https://github.com/solana-labs/token-list#scannerwallet-hasnt-updated-yet

repo: solana-labs/token-list