Don't show IPython kernels in the Python console by default

From contrebasse on 2014-06-20T02:59:24Z
Spyder Version:  2.3.0rc (3802: rc376e27fb117 )
Python Version:  3.4.1
Qt Version    :  4.8.6, PySide 1.2.2 on Linux
pyflakes >=0.6.0:  0.7.3 (OK)
pep8 >=0.6      :  1.4.6 (OK)
IPython >=0.13  :  2.1.0 (OK)
pygments >=1.6  :  1.6 (OK)
sphinx >=0.6.6  :  1.2.2 (OK)
psutil >=0.3    :  2.1.1 (OK)
jedi >=0.8.0    :  None (NOK)
rope >=0.9.2    :  0.9.4-1 (OK)
matplotlib >=1.0:  1.3.1 (OK)
sympy >=0.7.0   :  0.7.5 (OK)
pylint >=0.25   :  1.2.1 (OK)
What steps will reproduce the problem?

open spyder (I tried resetting the defaults)
Show the Console Tab 3.

What is the expected output? What do you see instead?
I expect to see one python console, but I also have an ipython kernel with the following text:
NOTE: When using the `ipython kernel` entry point, Ctrl-C will not work.

To exit, you will have to explicitly quit this process, by either sending
"quit" from a client, or using Ctrl-\ in UNIX-like environments.

To read more about this, see https://github.com/ipython/ipython/issues/2049 To connect another client to this kernel, use:
    --existing kernel-12934.json

Also, while the kernel is cloed if I type "quit" in the corresponding ipython console, if I stop the kernel manually with the topright button I still have to close the ipythonconsole and I can't quit the kernel directly.
So I have 2 problems:

Why is the ipython kernel showing up in the python console tab ?
Why can't I close the kernel once I killed it ?

Please provide any additional information below
.
I rarely use python interactively so I'm not used to the ipython console, these problems are very misleading for beginners.
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=1860

From contrebasse on 2014-06-20T09:17:05Z
Worse use case:

Close the ipython panel
Kill the kernel
It is not possible to close the kernel without reopening the ipython panel

From ccordoba12 on 2014-08-17T18:52:50Z
Labels: -MS-v2.3.1 MS-v2.3.2

From ccordoba12 on 2014-06-27T11:10:51Z
I thought we were going to get away with one :) I mean, I don't know why no one raised these concerns before because I'm aware they are really confusing.
About your problems:

IPython kernels are shown in the Python Console pane because we need them there to make the Variable Explorer work for IPython consoles. It's the only possible way to do it right now, given how the Variable Explorer works and the fact that we can't communicate directly with IPython kernels. To alleviate this issue, I'm working to just hide the kernels by default. I hope to have it for 2.3.1.

You can't close the kernel because it still has an IPython console associated with it. So you need to close the IPython console, which will close the kernel automatically.

Labels: MS-v2.3.1

From ccordoba12 on 2014-08-26T07:58:24Z
Summary: Don't show IPython kernels in the Python console by default  <span class="oldvalue"> (was: Ipython kernel in Python consoles) </span>

From ccordoba12 on 2014-08-26T07:57:47Z
issue #1862 has been merged into this issue.

From ccordoba12 on 2014-09-25T03:49:16Z
The idea for this issue is:

Add kernels to the list of external consoles but not as tabs (by default).

Add an action to the External Console menu called "Show IPython kernels" that when clicked will add a tab for each kernel.

Labels: Easy

From ccordoba12 on 2014-10-31T15:07:53Z
Labels: -MS-v2.3.2 MS-v2.3.3

From<EMAIL_ADDRESS>on 2014-11-01T09:30:14Z
I don't understand why "regular" Python consoles are offered at all (esp. on startup).
It seems to me that IPython is always preferred; I'd rather that Spyder defaults to presenting an iPython console (avoiding the need to do Consoles>Open an IPython console).
Perhaps there's some reason this isn't done that I don't understand (likely!); if so, this is one (of many things) that ought to be mentioned in documentation.
I have only ever used Spyder for serious Python development - I get the sense that many things re Spyder are undocumented because the assumption is that users are already experienced with IPython, etc.
If Spyder gets more popular, this will be less true - many users will start with Spyder as their first Python environment.
To support that, a lot more documentation is needed.

From ccordoba12 on 2014-11-01T11:31:22Z
I think you're using 2.3.0beta2 (because of your report on issue #2030 ). That release was done almost a year ago, so please update to the latest stable release (2.3.1) because since 2.3.0 the default is opening and focusing an IPython console.
I don't think Python consoles are going to be removed. Many people still use them and prefer them over IPython ones. However, I'll probably hide them by default in 2.4 to not confuse newbies.
I know documentation is lacking, but things improved in 2.3.1 with the addition of a new tutorial and will improve more in 2.4 with the addition of interactive tutorials. If you have time, please help us to improve our rst docs even further (instead of complaining). Right now I'm the only core developer and (unfortunately) my plate is more than full with maintenance, so I don't have time to write docs :-)

From ccordoba12 on 2014-11-18T14:07:01Z
issue #2052 has been merged into this issue.

From ccordoba12 on 2015-01-08T15:10:53Z
Labels: -MS-v2.3.3 MS-v2.3.4

I plan to solve this in the right way in 2.4. If we'd try to do it now, it'd be quite hacky.

I think it was said somewhere but I can't find it any more: another idea is to merge the Python console widget and the IPython consoles widget. There would only be one widget with consoles of different types (IPython, standard python, dedicated python).
Even the internal console could be shown here, It would feel more clean but it could be misleading for the unaware user. Maybe set the background as light red to give a clue that it should not be used (this could be done anyway).

This is not a possibility. The two consoles are very different :-)

What is inside the tabs are different, but couldn't they be in the same container (a dockwidget) ?

Please take a look at the code ;-)
plugins/ipythonconsole has a lot of supporting code to handle kernels, debugging and preferences.

We should have a Pane for the internal console (as it is), a pane for Python console (and should be named python console and not have any ipython kernels there..) and we should have a Pane for an Ipython Console (how it is now).
Can we go around not having that Kernel tab inside the console dockwidget @ccordoba12 ?

@goanpeca this is the title of the issue :smile:

Oops... true :)

@goanpeca, yes, having kernel widgets inside our Python console is one of the ugliest things in Spyder right now.
Unfortunately, there is no workaround to get rid of that ;-) What we need to do is to talk directly the IPython protocol to connect IPython kernels to the Variable Explorer.
Embedding kernels in the Python console was the easiest and most straightforward way to do that. That's why Pierre did it 4 years ago :-) But I plan to change that in Spyder 3.0.


dex_auth non leader units should set active as well

While doing some juju testing, found non-leader units are never set to active.
https://github.com/juju-solutions/bundle-kubeflow/blob/aac5a218cf29f144aaa6c037bfc51b97d34ecbb9/charms/dex-auth/reactive/dex_auth.py#L47
# this should be set for non leader units to set `active` status.
set_flag("charm.started")

dex-auth/0*                     active       idle        <IP_ADDRESS>  5556/TCP
dex-auth/1                      maintenance  idle        <IP_ADDRESS>  5556/TCP           fetching resource: oci-image
dex-auth/2                      maintenance  idle        <IP_ADDRESS>  5556/TCP           fetching resource: oci-image

The non-leader "units" can't meaningfully effect change, nor can they actually query the status of the workload pod that they're supposed to represent.  I do think that the current maintenance status is not correct, but I think the best that the charms could accomplish as it stands today would be to exit earlier and never call status-set at all so that it stays at unknown. There's still an issue with the status set by the leader unit, though, because active in that case really just means "I've given Juju a pod spec".  If the charm knows that its workload has a health / liveness endpoint, or an API that it could try to query, it might be worth improving the charm to do so.  However, a lot of that is already handled by Kubernetes and ideally the charm would just be able to see and respond to that.

Agreed, for now, we probably just never call status-set for minion units for less confusion.


other server can't use squid make https request

i am sorry i come here again,,
Now i deploy haipproxy on server A. I have other server B, i need B request server A, and get a agent ip.
after my test, i get this below:
run this same code:
import requests
proxies = {'https': 'http://myip:3128'}
resp = requests.get('https://httpbin.org/ip', proxies=proxies)
print(resp.text)
on server A, i can get a agent ip ( not same with my actually ip )
on server B, i can't get a agent ip and it raise exception like this:
requests.exceptions.ProxyError: HTTPSConnectionPool(host='httpbin.org', port=443): Max retries exceeded with url: /ip (Caused by ProxyError('Cannot connect to proxy.', NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x041155F0>: Failed to establish a new connection: [WinError 10060]
and when i change the code
proxies = {'https': 'http://myip:3128'}
to
proxies = {'http': 'http://myip:3128'}
it return a ip on server B, but it is my real ip, not a agent ip, can you help me fix this ?
my squid config like this:
acl localnet src servier_a_ip/8
acl localnet src server_b_ip/8
acl localnet src <IP_ADDRESS>/8     # RFC1918 possible internal network
acl localnet src <IP_ADDRESS>/12  # RFC1918 possible internal network
acl localnet src <IP_ADDRESS>/16 # RFC1918 possible internal network
acl localnet src fc00::/7       # RFC 4193 local private network range
acl localnet src fe80::/10      # RFC 4291 link-local (directly plugged) machines
acl SSL_ports port 443
acl Safe_ports port 80          # http
acl Safe_ports port 21          # ftp
acl Safe_ports port 443         # https
acl Safe_ports port 70          # gopher
acl Safe_ports port 210         # wais
acl Safe_ports port 1025-65535  # unregistered ports
acl Safe_ports port 280         # http-mgmt
acl Safe_ports port 488         # gss-http
acl Safe_ports port 591         # filemaker
acl Safe_ports port 777         # multiling http
acl CONNECT method CONNECT
http_access deny !Safe_ports
http_access deny CONNECT !SSL_ports
http_access allow localhost manager
http_access deny manager
http_access allow localnet
http_access allow localhost
http_access deny all
http_port 3128
i also try to make a CA certificate and use https_port config, but it useless, everything not change, server b can't use https proxy.
thanks

I'm sorry but i think you should learn ACL about squid! This project won't teach you how to config if you have special requirements. It cares only about the proxy pool and it's availablity.
BTW, my blog may be helpful, it's written in Chinese.

ok, thanks, i will read it


V1.4.0: Unable to change index name in elasticsearch sink

With
sink config:
        - "--sink=elasticsearch:http://elasticsearch.monitoring.svc:9200?index=k8sevents?cluster_name={{ .Values.clusterName }}?sniff=0"
error:
W0630 00:47:10.151271       1 driver.go:75] Failed to export data to ElasticSearch sink: elastic: Error 400 (Bad Request): Invalid index name [k8sevents?cluster_name=prod.us-west-6.aws.k8s?sniff=0-2017.06.30], must not contain the following characters [ , ", *, \, <, |, ,, >, /, ?] [type=invalid_index_name_exception]

@AlmogBaku @andyxning @huangyuqi

@dvdklnr you should separate parameters with &, not with multiple ?, so it should be --sink=elasticsearch:http://elasticsearch.monitoring.svc:9200?index=k8sevents&cluster_name={{ .Values.clusterName }}&sniff=0

Thank you for pointing it out, it's not clear from the examples.

can we close it?

yes, please


Fix fatal error for enqueued/processing tasks when duration is null.

Fixes #163

@fitimvata Thx!


Question about reproducibility

Hi,
Thanks for developing such an excellent tool.
I noticed that if I want to make the phase_common results reproducible, I have to use a single thread (and keep the seed, although the default seed is fixed).
This was described in the SHAPEIT4's document as follows:

Reproducibility
Making reproducible runs can sometimes be useful. To do so, you need to specify the random generator seed using --seed and to use a single thread. Using multi-threading prevents reproducibility.

Regarding ligate and phase_rare, should I use a single thread to make it reproducible?
Although I want to use multiple threads to speed up, I am also concerned about reproducibility and its potential effects on my downstream analysis.
Best,

Hi Masuru,
I think ligate and phase_rare are safe, there's no random sampling in
there.
Multi-threading and reproducibility should be possible.
But as you mention; this is not the case for phase_common.
Cheers;
Olivier Delaneau
http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
Sans
virus.www.avg.com
http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
Le ven. 21 avr. 2023 à 06:13, Masaru Koido @.***> a
écrit :

Hi,
Thanks for developing such an excellent tool.
I noticed that if I want to make the phase_common results reproducible, I
have to use a single thread (and keep the seed, although the default seed
is fixed).
This was described in the SHAPEIT4's document as follows:

Reproducibility
Making reproducible runs can sometimes be useful. To do so, you need
to specify the random generator seed using --seed and to use a single
thread. Using multi-threading prevents reproducibility.

Regarding ligate and phase_rare, should I use a single thread to make it
reproducible?
Although I want to use multiple threads to speed up, I am also concerned
about reproducibility and its potential effects on my downstream analysis.
Best,
—
Reply to this email directly, view it on GitHub
https://github.com/odelaneau/shapeit5/issues/25, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD4XTINW67XJAHRLT5FL22DXCICQHANCNFSM6AAAAAAXGK6TQU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hi Olivier,
Thank you very much for your helpful response.
Best,
Masaru


Kevin smart gui

Changed the name of the function printTables() to getMetaData(). Command out some testing purpose print lines. The function is working after several tests by using Post Man.

Congratulations on your team's first Pull Request. 👍
A few comments on this Pull Request:

I recently fixed a bug in RelationManager and made some changes, please merge the latest master branch into your branch and resolve the merge conflict.
It looks like you are developing based on the new angular2 GUI branch. I don't know if you are also making changes to the front end, but since that code is not yet reviewed and merged, I think you should add the functionality on backend first. Furthermore, the backend changes and the frontend changes should in separate PRs. Please redo this using the latest master branch.
I noticed that some files have unnecessary changes, for example, the .gitignore file, some lines in QueryPlanResource.java, line 354 in RelationManager.java. It makes the reviewers difficult to see the differences. Please fix that.
In the newly added printTables function in RelationManager, you are using Lucene's APIs directly. TextDB has wrappers around Lucene, they are DataWriter and DataReader. Please see how other functions in RelationManager works.
The name printTables is not good. It currently returns an hashmap of <String, Object>, but a metadata object is probably better. Please refer to Prof Li's comments on Slack.
In the newly added initQueryPlan function in queryPlanResource, The endpoint's path is queryplan/init.  First of all I don't think this functionality belongs to queryplan. Second of all, I don't think the name init doesn't describe its functionality.  Third of all, I think in this case GET is better than POST.

@KevinKozj : great to see your first PR!  As @zuozhiw said, in general it's very important to make each PR small to review and add necessary test cases.
@zuozhiw : regarding point 4), is there any way to HIDE the lucene API so that other modules don't use it unnecessarily?

@chenlica We are heavily relying on Lucene. All the Source operators need to generate a Lucene Query to pass to data reader. We also use Lucene's analyzers everywhere. So I guess hiding Lucene will be a problem.

OK then.

Going to re-create the branch from the master branch


add dns resolver to nginx config

Fixes https://github.com/canonical/cos-lib/issues/94
This change tells Nginx to update the IP whenever it changes.
To test:
deploy COS-lite plus Mimir.
refresh worker with any locally packed charm
verify you can ping the /ready endpoint soon (max 5sec) after the new worker service has reported ready.

Manually tested ✅ Re-running itests now


Naming convention and consistency

Rename directory How_to_calculate_speeding_fines_under_Italian_law to speeding_fines_ita or similar
Ensure consistency between directory and file naming. E.g., dir speeding_fines_ita -> filename from speed_limit.py to speeding_fines_ita.py, or, if it's the only file in the directory main.py is ok, too.
Rename Wiki.tx to README.md and rewrite in markdown.

Once everything is done, commit with comment "fix #1" to automagically close this issue.

I am not able to rename directory
Done
Done

fix #1


Register the webhook with the Speech service

Could you explain how to register the webhook with the Speech service ?. The Batch Transcription service runs and generates the text, I can verify it by calling GET
/api/speechtotext/v2.0/transcriptions , however I am not receiving anything in a webhook I created.
When I created the webhook I got this response:
{
"id": "xxxxxx",
"name": "TranscriptionCompletionWebHook",
"description": "This is a Webhook created to trigger an HTTP POST request when my audio file transcription is completed.",
"configuration": {
"url": "https://bin.webhookrelay.com/v1/webhooks/xxxxxxxxxxxxxxxx"
},
"events": [
"TranscriptionCompletion"
],
"active": true,
"pingUrl": "https://northeurope.cris.ai:443/api/speechtotext/v2.1/transcriptions/hooks/xxxxxx/ping",
"testUrl": "https://northeurope.cris.ai:443/api/speechtotext/v2.1/transcriptions/hooks/xxxxxxxx/test",
"apiVersion": "v2.1",
"createdDateTime": "2019-05-23T11:35:17Z",
"lastActionDateTime": "2019-05-23T11:35:17Z",
"status": "Succeeded",
"properties": {
"Active": "True"
}
}
How can I register this webhook with my Speech Service ?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: abdefe38-e71e-4e84-d504-a47351bc1325
Version Independent ID: acea917c-e0f6-689f-09be-97db2524a466
Content: Webhooks - Speech Services
Content Source: articles/cognitive-services/Speech-Service/webhooks.md
Service: cognitive-services
Sub-service: speech-service
GitHub Login: @PanosPeriorellis
Microsoft Alias: panosper

@caespinosam Thanks for the feedback! We are currently investigating and will update you shortly.

This is what I get when I call GET /api/speechtotext/v2.0/transcriptions:
{
"recordingsUrl": "https://xxxaccount.blob.core.windows.net/xxxxxcontainer/simple.wav?sp=r&st=2019-05-22T12:47:06Z&se=2019-05-22T20:47:06Z&spr=https&sv=2018-03-28&sig=xxxxxxxxxxx%2F5OME%3D&sr=b",
"resultsUrls": {
"channel_0": "https://spsvcprodneu.blob.core.windows.net/bestor-xxxxxxx/TranscriptionData/xxxxxxxx-45eee9cecbfe.json?sv=2017-04-17&sr=b&sig=xxxxxx%2BvI%3D&st=2019-05-22T13:34:17Z&se=2019-05-25T13:39:17Z&sp=rl"
},
"models": [
{
"modelKind": "AcousticAndLanguage",
"datasets": [],
"id": "xxxxx-27d97888bde0",
"createdDateTime": "2019-03-26T13:43:38Z",
"lastActionDateTime": "2019-03-26T15:28:49Z",
"status": "Succeeded",
"locale": "en-US",
"name": "v4.13 Unified",
"description": "Unified",
"properties": {
"Purpose": "OnlineTranscription,BatchTranscription,LanguageAdaptation",
"ModelClass": "unified-v4"
}
}
],
"statusMessage": "None.",
"id": "xxxxxxx-e22225d2b268",
"createdDateTime": "2019-05-22T13:29:24Z",
"lastActionDateTime": "2019-05-22T13:29:51Z",
"status": "Succeeded",
"locale": "en-US",
"name": "Transcription using locale en-US",
"description": "An optional description of the transcription.",
"properties": {
"ProfanityFilterMode": "Masked",
"PunctuationMode": "DictatedAndAutomatic",
"Duration": "00:00:11"
}
},

@caespinosam It looks like you have registered the webhook successfully and received a response with the recording URL that you can use.
You can use the webhooks for the following types of speech operations.

@RohitMungi-MSFT Thank you!. The problem was that for some reason  bin.webhookrelay.com is not showing me all the request it is supposed to receive. I tried out a different online tool and now I can see all the request (transcriptions) sent by the webhook.
I see that if  I create many webhooks all of them will be executed once a transcription is finished.  Is there a way to tell the Batch Service which webhook I want to be executed when a given transcription is finished?

@PanosPeriorellis @erhopf Do we have an option to specify which webhook to call if there are multiple for one event type or do we need to set the Active property to false and delete the webhook after each transcription?

This has been identified as a product issue, not a doc bug or enhancement.
We want you to get an answer as quickly as possible so, please take a look at this document and post your issue to the relevant forum.
#please-close

@RohitMungi-MSFT So is there anyway to specify which webhook to call if there are multiple? Or do we have to manually delete and create such that only one exists at a time?

This is a real concern. The Speech Service Webhook is hard to make sense of, little to no documentation.
Do I register a single lifetime webhook or do I create a new individual Webhook for each request. I have a list of items with a unique ID that needs to wait for the response on Batch Transcription.
const request = await createTranscriptionWebhook({
    displayName: `${id} - Webhook`,
    events: {
      transcriptionCompletion: true,
    },
    webUrl: `${BASE_URL}/webhook/transcriptionCompletion/${id}`,

I used a unique ID parameter in URL so I can handle every webhook response as a known entity with ID.
This function calls the Webhook_Create route. Originally, I thought when you register a webhook like this, complete the challenge and the webhook returns the actual response, the cycle completes, but alas, No.
The webURL is unique, but when I register a new Webhook, when it's time to process, previous webhooks registers with similar URLs under different ID from the current request still get triggered.
For example:
I register the speech webhook: ${BASE_URL}/webhook/transcriptionCompletion/1
Here is my handler.
function handleWebhook(id){}
When the webhook runs the first time, the handler is called once with 1. Now when I register a new Webhook
I register the speech webhook: ${BASE_URL}/webhook/transcriptionCompletion/2, when the handler runs, this time, the handler runs twice, it runs for 1 and 2, it keeps growing exponentially and I can't make sense how this works if the URL is unique. The doc is not telling us all we need to know.
Do we need to Delete a webhook after it's done processing? Why is a webhook called multiple times even after a 200 response was returned from the initial call?

@paschaldev Hey, check out https://learn.microsoft.com/en-us/rest/api/speechtotext/web-hooks?view=rest-speechtotext-v3.2-preview.2
From this, I am led to believe that web hooks are registered for lifetime, once. You can list all web hooks as shown in the link ^.
I also think the docs are extremely poor, and it's not obvious why the webhook mechanism is built as such. The way you're trying to use it is more reasonable, and their way of making you programmatically validate it once for lifetime is just odd.


Changing the upstream proxy via the requestheaders hook

Problem Description
I'm trying to change the upstream proxy based on the request host and path, for this I'm trying the requestheaders hook.
Here's my setup:

Filter instance: mitmproxy in upstream mode listening on port 8990. This is the proxy server used for the browser.
mitmdump -s filter_reqs.py -p 8990 --mode upstream:http://<IP_ADDRESS>:8993
Residential instance: mitmproxy in upstream mode listening on port 8993, traffic is forwarded to a residential proxy (localhost:8992)
mitmproxy -p 8993 --mode upstream:http://<IP_ADDRESS>:8992
Regular instance: mitmproxy in regular mode listening on port 8994:
mitmproxy -p 8994

filter_reqs.py:
from mitmproxy.net.server_spec import ServerSpec

def requestheaders(flow):
	flow.server_conn.via = ServerSpec('http', ('<IP_ADDRESS>', 8994))

So basically what I'm trying to do as a test is:

Browser is configured to use the Filter instance.
Filter instance is supposed to reroute all traffic to the Regular instance
What happens is: 1 request goes through the Regular instance and all the rest go through the Residential instance

Steps to reproduce the behavior:

Run all mitmproxy instances as described above
Run chromium with the Filter instance as the proxy server:

chromium --proxy-server="http://<IP_ADDRESS>:8990"

Visit https://lumtest.com/myip.json: Local IP appears, and the request appears on the Regular instance
Visit https://whoer.net: Residential IP appears, requests appear on the Residential instance

System Information
Paste the output of "mitmproxy --version" here.
Mitmproxy: 7.0.4
Python:    3.9.7
OpenSSL:   OpenSSL 1.1.1l  24 Aug 2021
Platform:  Linux-5.9.16-1-MANJARO-x86_64-with-glibc2.33

Any help highly appreciated. Thank you.

I spotted what could be the culprit in the logs of the Filter instance
Loading script filter_reqs.py
Proxy server listening at http://*:8990
<IP_ADDRESS>:53540: client connect
<IP_ADDRESS>:53540: server connect <IP_ADDRESS>:8993
<IP_ADDRESS>:53546: client connect
<IP_ADDRESS>:53548: client connect
<IP_ADDRESS>:53546: server connect <IP_ADDRESS>:8994
<IP_ADDRESS>:53546: GET http://lumtest.com/myip.json
              << 200 OK 211b
<IP_ADDRESS>:53546: GET http://lumtest.com/favicon.ico
              << 404 Not Found 150b

#### lumtest.com request is done ####

<IP_ADDRESS>:53540: POST https://accounts.google.com/ListAccounts?gpsia=1&source…

Thanks for the detailed report! I think this boils down to us not properly supporting a dynamic upstream proxy change at the moment. #4820 also inquired about this. Here's a super hacky script that somewhat works for me:
from mitmproxy.connection import ConnectionState
from mitmproxy.net.server_spec import ServerSpec

def requestheaders(flow):
    if flow.server_conn.via.address != ('<IP_ADDRESS>', 8002):
        flow.server_conn.state = ConnectionState.CLOSED
        flow.server_conn.via = ServerSpec('http', ('<IP_ADDRESS>', 8002))

We should eventually look into adding a proper API here. :)

Thank you for taking the time! Very appreciated. I tested out your suggested solution, it does work, but although the Residential instance doesn't show any requests coming in, I can still see requests in my residential proxy's logs (localhost:8992).
I tried something else, was reading an unrelated issue and saw your comment about --no-upstream-cert. I tried that and it worked! 🥳
So now, I run the Filter instance like this:
mitmdump -s filter_reqs.py --set upstream_cert=false -p 8990 --mode upstream:http://<IP_ADDRESS>:8993

Although I have to admit, I don't understand why this works. Any ideas ?
I can't see anything on my residential proxy's logs using this method. So that's a win.

Do you see HTTP requests or do you see TCP client connections that then get closed before anything is sent? There are some cases where mitmproxy connects upstream early, for example when we negotiate HTTP/2 during the TLS handshake we want to make sure that the server actually speaks it. That is expected, one can influence that with connection_strategy and - as you discovered - upstream_cert to some degree.

Do you see HTTP requests or do you see TCP client connections that then get closed before anything is sent?

I'm not quite sure, I checked mitmproxy's event log, and it only shows client connects, server connects and then disconnects.
I did some more testing with upstream_cert=false, I forgot to mention I had the connection_strategy set to lazy. If I remove that, then I can see output in the event log of the Residential Instance.
So a combination of  upstream_cert=false and  connection_strategy set to lazy is what worked best for me.

@d3vr using upstream_cert=false and  connection_strategy=lazy works for me.
but what if upstream proxy needs authentication? i found upstream_auth option, but it seems that it is handled globally, and can not be dynamic (per flow).

@4bo Did you find out how to dynamically change upstream_auth inside addon?


More Filters!

I use few filters in my own games, so trying to generate ideas here.
Current thoughts:
Filter by card type (Action, Reaction, Attack, etc.)
Filter by card archetype (trickier - would need some classifiers here, like Big Money, etc)
We already have one archetype - Cursers.

Merged into https://github.com/Mark-Lauman/DominionPicker/issues/43


Fix docs.rs link in esp-wifi/README.md

Thank you for your contribution!
We appreciate the time and effort you've put into this pull request.
To help us review it efficiently, please ensure you've gone through the following checklist:
Submission Checklist 📝

[x] I have updated existing examples or added new ones (if applicable).
[x] I have used cargo xtask fmt-packages command to ensure that all changed code is formatted correctly.
[x] My changes were added to the CHANGELOG.md in the proper section.
[x] My changes are in accordance to the esp-rs API guidelines

Extra:

[x] I have read the CONTRIBUTING.md guide and followed its instructions.

Pull Request Details 📖
Description
I fixed the docs.rs link in the README.md of the esp-wifi crate.
Testing
Clicking the badge leads to the correct docs.rs page.

Thanks! The link is indeed broken. I think we want to link to our self-hosted docs like https://docs.esp-rs.org/esp-hal/esp-wifi/0.6.0/esp32/esp_wifi/ - we don't have an esp-wifi landing page so probably we should just link to https://docs.esp-rs.org/esp-hal/ for now
Probably it wouldn't need a CHANGELOG.md entry

Thank you for your feedback. I removed the CHANGELOG.md entry and changed the link to https://docs.esp-rs.org/esp-hal/ as suggested.
The other crates in this repository link to their https://docs.rs page. For example:
https://github.com/esp-rs/esp-hal/blob/921ecc4d561e6dbd880c27aa89f63a33e02379fd/esp-alloc/README.md?plain=1#L4
While checking that, I have found that two crates have broken links for crates.io, docs and license, esp-ieee802154 and esp-lp-hal. But I think that they currently unpublished.

👍
Yes, the links for the unpublished crates will be fine once they are published (which we plan to publish with the next release)
The smaller crates usually don't really have different API depending on the target so users can just use docs.rs. We might self-host their docs in future, too but it's not planned yet


Request to join pattern house

Github username: novalramdhani
A web developer who really likes technology, new things and likes to join many organizations. Love open source.
PHP and Ruby enthusiast, experience with Laravel and Ruby On Rails.

Hey there, I have sent the invite link! Happy to have you join the org :)


Ability to mount a single file, not just a share

In regard to this stackoverflow question:
https://stackoverflow.com/questions/55602201/mount-an-individual-file-in-azure-container-instances
There are times in which a docker container setup would expect being able to mount a single file rather than a folder. It would be great if we could do this in ACI to make things more cross compatible without requiring tweaks to the container.

Would be really nice to have it

We can't use ACI because of this.

Will there be any updates on this issue , i dont see any updates since the issue is opened.

Have this issue been addressed?

Would be really nice to have it


Struggle to get it working

I use my phone number to login in the app; so have used +316xxxxxxxx as SAIC_user in HA config
In HA I get the following log error for 'SAIC MQTT Gateway Python".
Can't figure out why this is not working. Any help would be highly appreciated.
Exception in thread Thread-1 (_thread_main):
Traceback (most recent call last):
File "/usr/local/lib/python3.10/threading.py", line 1016, in _bootstrap_inner
self.run()
File "/usr/local/lib/python3.10/threading.py", line 953, in run
self._target(*self._args, **self._kwargs)
File "/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py", line 3591, in _thread_main
2023-07-13 23:59:40,155 Starting new HTTPS connection (1): tap-eu.soimt.com:443
self.loop_forever(retry_first_connection=True)
File "/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py", line 1756, in loop_forever
rc = self._loop(timeout)
File "/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py", line 1164, in _loop
rc = self.loop_read()
File "/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py", line 1556, in loop_read
rc = self._packet_read()
File "/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py", line 2439, in _packet_read
rc = self._packet_handle()
File "/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py", line 3039, in _packet_handle
return self._handle_connack()
File "/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py", line 3138, in _handle_connack
on_connect(
File "/usr/src/app/mqtt_publisher.py", line 51, in __on_connect
self.client.subscribe(f'{basic_topic}/refresh/mode/set')
File "/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py", line 1491, in subscribe
raise ValueError('Invalid subscription filter.')
ValueError: Invalid subscription filter.
2023-07-13 23:59:40,643 https://tap-eu.soimt.com:443 "POST /TAP.Web/ota.mp HTTP/1.1" 200 None
2023-07-13 23:59:40,656 MqttGateway crashed due to SaicApiException
Traceback (most recent call last):
File "/usr/src/app/./mqtt_gateway.py", line 383, in run
login_response_message = self.saic_api.login()
File "/usr/local/lib/python3.10/site-packages/saic_ismart_client/saic_api.py", line 117, in login
raise SaicApiException(login_response_message.body.error_message.decode(),
saic_ismart_client.saic_api.SaicApiException: return code: 15011, message: The account is not registered.
return code: 15011, message: The account is not registered.

The format for phone numbers for the European and Australien API endpoints is:
316-1234567
Country Code - phone number
No leading zeros.

Thanks. Good to know.
your<PHONE_NUMBER> didn't work, but then I tried 31-61234567 which worked !
Thanks


adds --show-interactive-dev-session flag to dev options

I was very happy to find this (I'm also using Turbo repo and the interactive prompt reduces the signal:noise), so I figured others might also be grateful for the option.

Matching declaration at https://github.com/cloudflare/workers-sdk/blob/327a4568751a4046ff8794c72c658c074964a7c7/packages/wrangler/src/tests/dev.test.tsx#L1262


CodeChickenLib-1.7.10-<IP_ADDRESS>-universal

I don't know how, but the  CodeChickenLib-1.7.10-<IP_ADDRESS>-universal that CodeChickenCore auto downloads is not the same as the one that it originally downloaded, and the file that it is downloading now is just causing any modpacks created with it to auto-crash, yet if I copy over and replace the CodeChickenLib-1.7.10-<IP_ADDRESS>-universal from an older modpack that I have downloaded the packs start working again.
Please fix this as soon as you can

Same issue here, please fix!

Also finally can run the modpack, i downloaded this version of the lib http://chickenbones.net/maven/codechicken/CodeChickenLib/1.7.10-<IP_ADDRESS>/CodeChickenLib-1.7.10-<IP_ADDRESS>-universal.jar
(<IP_ADDRESS>) then renamed the file to 'CodeChickenLib-1.7.10-<IP_ADDRESS>-universal' inside /modes/1.7.10 folder and it worked!
Huge thanks @GoldKai for the lead! I couldn't fix it otherwise!

It doesnt work because the Core Mod tries to download
http://files.minecraftforge.net/maven/codechicken/CodeChickenLib/1.7.10-<IP_ADDRESS>/CodeChickenLib-1.7.10-<IP_ADDRESS>-universal.jar
wich doesnt exist (anymore?).
So maybe you have to make the file available again or change the dependencies.info in the Core mod to download CodeChickenLib-1.7.10-<IP_ADDRESS>-universal.jar like this:
"repo": "http://files.minecraftforge.net/maven/codechicken/CodeChickenLib/1.7.10-<IP_ADDRESS>/",
"file": "CodeChickenLib-1.7.10-<IP_ADDRESS>-universal.jar",

I don't know how, but the CodeChickenLib-1.7.10-<IP_ADDRESS>-universal that CodeChickenCore auto downloads is not the same as the one that it originally downloaded, and the file that it is downloading now is just causing any modpacks created with it to auto-crash, yet if I copy over and replace the CodeChickenLib-1.7.10-<IP_ADDRESS>-universal from an older modpack that I have downloaded the packs start working again.
Please fix this as soon as you can

To everyone who had this issue, a new version was posted on Curse not long ago with the fixed CCL downloader.

To everyone who had this issue, a new version was posted on Curse not long ago with the fixed CCL downloader.

Do you have a link for this? When I'm using CurseForge / Overwolf, I've tried downloading a new copy of Twilight Forest but it still crashes on CodeChicken.

I don't know how, but the CodeChickenLib-1.7.10-<IP_ADDRESS>-universal that CodeChickenCore auto downloads is not the same as the one that it originally downloaded, and the file that it is downloading now is just causing any modpacks created with it to auto-crash, yet if I copy over and replace the CodeChickenLib-1.7.10-<IP_ADDRESS>-universal from an older modpack that I have downloaded the packs start working again.
Please fix this as soon as you can

To everyone who had this issue, a new version was posted on Curse not long ago with the fixed CCL downloader.

I've searched up CodeChickenLib-1.7.10-<IP_ADDRESS>-universal curseforge and they only have 1.8+ codechickenlib, there's no new version unless they decided to take said new V down.

To everyone who had this issue, a new version was posted on Curse not long ago with the fixed CCL downloader.

Do you have a link for this? When I'm using CurseForge / Overwolf, I've tried downloading a new copy of Twilight Forest but it still crashes on CodeChicken.

https://www.curseforge.com/minecraft/mc-mods/codechickencore/files/3293859

i did that but it still auto downloads it

i did that but it still auto downloads it

Make sure your on the latest version and delete the old CCL file.

I can confirm, seems like it's still happening. I'm getting a <IP_ADDRESS> now, and it deletes my old CCL files - which I do not want. If I wanted a new version, I'd download it. :P
Can we just add a config file to turn this off, please?

The same happens on 1.6.4

Yeah I'm returning to MC with my old server and both the client and server fail to start because of this missing URL problem.  Setting the file to read-only doesn't avoid the issue.  Disabling the update check in config doesn't avoid the issue.
I don't know how to change the dependencies like @LMAA-basedow mentioned.
CodeChicken's stuff seems to just be completely removed from the Forge site as of modern times, and anyone posting on the forums about old versions is met with "we don't support this, use the latest" thread locked
If modern versions of CCC were updated to use curseforge instead of minecraftforge, well, then older versions never received this update and are broken out of box.
The older I get, the more I see the problems with the digital era old people keep complaining about.

Also finally can run the modpack, i downloaded this version of the lib http://chickenbones.net/maven/codechicken/CodeChickenLib/1.7.10-<IP_ADDRESS>/CodeChickenLib-1.7.10-<IP_ADDRESS>-universal.jar (<IP_ADDRESS>) then renamed the file to 'CodeChickenLib-1.7.10-<IP_ADDRESS>-universal' inside /modes/1.7.10 folder and it worked! Huge thanks @GoldKai for the lead! I couldn't fix it otherwise!

THANKS SO MUCH


Can this be configured in a .remarkrc file?

The documentation mentions how to configure with the programmatic API, but not the config-file api.
How do I configure this in my .remarkrc file?
Here's my .remarkrc file:
{
  "plugins": [
    "remark-preset-lint-recommended",
    ["remark-toc", {
      "tight": true,

    }],
    ["remark-lint-list-item-indent", false],
    ["remark-lint-code", {"js": {
      "module": "node_modules/remark-lint-code-eslint",
      "options": {
        "fix": true
      }
    }}]
  ]
}

You’re already using it right!?

But it's not actually adding the tocs..
What could I be doing wrong?

How are you running remark? Tip: add the DEBUG env variable.

Here's how I'm calling remark:
https://github.com/storybooks/storybook/blob/ndelangen/dev/package.json#L49

In remark . # -- -o to update, the # makes the rest of the line into a comment, if you want to generate files, you do need to pass -o, --output, like so: remark . -o!

I know, I'm actually running this:
npm run lint:markdown -- --o

ow I think I've spotted a problem between the keyboard and chair

Is any markdown reformatted? Maybe -- -o isn't the proper way to pass flags?

No it appears no markdown is formatted, strange that was working before..

New npm version? I’m note sure, but I think they switched it around before.
So is it working now?

So it DOES work when I change my npm script like so:
"lint:markdown": "DEBUG=\"*\" remark . -o",

Maybe because of the comment? Maybe npm execs like so: remark . # -- -o to update -o (where the last -o is added from outside the npm script).

I guess it could be because of the comment, yeah, I'll reset, and try without 👍

remark-toc is adding the tocs correctly now, thanks. 😎
I will stop adding comments to my npm script and dislike json for configuring even more 😒

😛
Alright, good! Feel free to add more issues if you run into stuff, but I’d also like to point out that the Gitter channel is really good for more question-like stuff!


trade prices of another player

its a Feature Request:
add a option to shows the trade prices of another player

Cool feature idea
Are you talking about just seeing what the price would be for another player? Or having a universal price applied?
A universal price wouldn't be possible unfortunately, I've looked into that
Are you talking about reputation specifically or all the item prices?

Exactly, I mean how high the prices are for other players' items (the prices vary depending on reputation).
Is there even a universal price or what do you mean by that?
Showing the reputation in addition would also be a good idea though.

@seema84 A universal price is the a price that everyone can use instead of the given price.
For example, if you wanted everyone to get a discount if only one player cures the Villager, rather than just the regular player.
As for reputation, we are looking into a way to determine the prices of other players based on the reputation.

So a universal price (as you described), I don't find that interesting at the moment.
I was only interested in being able to check the offers of other players.

Cool, gonna look into how to implement this :3

Request has been moved to the new repo https://github.com/Simplexity-Development/VillagerInfo/issues/2


[FULL_AUTO] Use tag to determine if a host is on FULL_AUTO or not

Summary
This PR change the implementation of isDataNodeInFullAutoMode.
The issue with the current implementation is that when data node restarts, helix would remove it from all the IdealState and ExternalView so we can't figure out which resource this host's partitions belong to. In this case, whenever a data node restarts, it will be changed back out to SEMI AUTO.
The new implementation fixes this issue.
The new implementation relies on the tag rather then the IdealState. Before we turn on FULL_AUTO on any resource, we would add a tag to the resource and the same tag to all the instances that belong to this resource. The tag is not going to disappear when the instance (data node) restarts. In this way, we can rely on this tag to determine if the FULL_AUTO is turned on.

Codecov Report
Patch coverage has no change and project coverage change: -39.25 :warning:

Comparison is base (1a19e09) 53.44% compared to head (674e736) 14.19%.

Additional details and impacted files
@@              Coverage Diff              @@
##             master    #2459       +/-   ##
=============================================
- Coverage     53.44%   14.19%   -39.25%
+ Complexity     7395     2365     -5030
=============================================
  Files           778      778
  Lines         61787    61842       +55
  Branches       7586     7594        +8
=============================================
- Hits          33021     8780    -24241
- Misses        25851    52546    +26695
+ Partials       2915      516     -2399

Impacted Files
Coverage Δ

...m/github/ambry/clustermap/HelixClusterManager.java
0.00% <0.00%> (-45.80%)
:arrow_down:

... and 512 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


support for Laravel Scout

Summary of problem or feature request
There was a ticket to request Laravel Scout support (#1042)  and there is also a package for it (https://github.com/yajra/laravel-datatables-scout). The issue is the package has been abandoned since July 2017. Please spend more time on laravel-datatables-scout package as you know that in large scale tables, mysql is not really a good solution.
Things to improve on laravel-datatables-scout

more tutorials to get started so people can start using it and give more feedback
respond to reported laravel-datatables-scout issues
laravel-datatables-scout package should do whatever laravel-datatables can do atm

It's my opinion and I (and others) are really appreciate your great contribution. I believe laravel-datatables-scout will make laravel-datatables to the next level.
Thank you

What needs to be done to implement this? Is it possible to create a project for the Laravel Scout support? When there's a clear vision in what needs to be done I, and most likely some other users of this repo, might be able to help.


feat: get_optimizely_config API to get static experiments and features data

Summary
Added a get_optimizely_config API which returns static experiments and features data.
Test plan

Manually tested thoroughly
Full Stack Integration tests passed
Adding Unit tests

Coverage decreased (-0.5%) to 99.054% when pulling e234f34af10a44a29846ee8437b8ed9b8f6a22cd on zeeshan/get_optimizely_config into 6e84924f095aa32e311e247333219796371c9e57 on master.

Coverage decreased (-0.5%) to 99.054% when pulling e234f34af10a44a29846ee8437b8ed9b8f6a22cd on zeeshan/get_optimizely_config into 6e84924f095aa32e311e247333219796371c9e57 on master.

Coverage decreased (-0.5%) to 99.054% when pulling e234f34af10a44a29846ee8437b8ed9b8f6a22cd on zeeshan/get_optimizely_config into 6e84924f095aa32e311e247333219796371c9e57 on master.

Coverage decreased (-0.5%) to 99.054% when pulling e234f34af10a44a29846ee8437b8ed9b8f6a22cd on zeeshan/get_optimizely_config into 6e84924f095aa32e311e247333219796371c9e57 on master.


Use /types everywhere

Closes #701.

Should this be included as well?
https://github.com/grammyjs/website/blob/556a890b508fe9d3d94ae4cbe75b37727109c0ec/site/docs/guide/api.md?plain=1#L79

No, it was intentionally omitted. We still want to link to the original source of the types. We explain right after this that they are exported from grammY, and how they can be used.


Gävle, Sweden

I'm looking for more Swedish municipalities right now and it seems that a couple have started publishing recently.
Here is Gävle: https://www.gavle.se/service-och-information/om-gavle-kommun/oppna-data/datakatalog/data/#esc_entry=45&esc_context=1
I'm not creating a PR for now, waiting to see the feedback on the one I did for Göteborg.
Related issue: #5255

Hey do you want to take on cutting a PR? Otherwise I'm happy to! Thanks for finding these sources!

I don't have time right now unfortunately. Maybe in October. If you can't wait, go ahead!


String parsing for Int64?

As Javascript is not really equipped to handle large integers, and it's required to use strings for anything above 53-bits, wouldn't it be logical if the decode function of Int64 automatically parses strings?

that makes sense to me. Would you be able to open a PR for it?

I tried to that this afternoon, but cloning Argo and running bin/setup crashed carthage. That was, however, before I read this. After running submodule init and submodule update, all works fine again. Anyway, I will try again tomorrow :)

Merged in the fix from #301 as e7680fc


Add Ukrainian names

My concern is about project names. The root project must be named, otherwise it will be named root, and in the list of projects such name is not comprehensive. Thus, I give name country-codes to root project and country-codes-scala to inner one. If the latter affects package name, then it must be changed.


AMC and quantization will work for cnn+rnn?

hi, I want to know if AMC is useful for neural networks like CNN + LSTM like CRNN or what should i do to apply AMC to CRNN?
one more that, i tried run quantization for quantizing CRNN, but i'm failed, the parameters of LSTM seem to be lost. so I want to know if the quantization method in distiller work for cnn + rnn networks.
and if i change code to control layers that will be quantized and compressed in CRNN (such as only execute AMC and quantization for CNN part and ignored RNN part), will it cause accuracy heaily loss heavily?
thank!

Hi,
Closing this issue as it seems resolved.


Improved Speakers page

Improved Speaker Page . Resolved Issue #1078 . Please review and merge
@aayusharora Please check the links color and underlining and I have also fixed empty data issue

Codecov Report

Merging #1083 into development will increase coverage by 0.02%.
The diff coverage is 75%.

@@               Coverage Diff               @@
##           development    #1083      +/-   ##
===============================================
+ Coverage        68.79%   68.82%   +0.02%
===============================================
  Files                7        7
  Lines             1141     1145       +4
  Branches           178      179       +1
===============================================
+ Hits               785      788       +3
- Misses             356      357       +1

Impacted Files
Coverage Δ

src/backend/generator.js
70.49% <75%> (+0.07%)
:white_check_mark:

Continue to review full report at Codecov.

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

@SparshBansal  please provide the live link. Thanks

@aayusharora Here is the link : safe-sea-55983.herokuapp.com

@SparshBansal  It seem that you have understood the issue incorrectly, the underline and color should come on hovering the session.

@aayusharora  Sorry i misunderstood , I have updated the PR and I request you to review and merge.
Now icon colors and underline change on hover.
Demo Link : https://safe-sea-55983.herokuapp.com/


C++ Publication::tryClaim max payload length check bug

I haven't used this API yet, but reading over it in preparation I think I've discovered a bug in the max payload length check.
checkForMaxMessageLength() checks, as the name suggests, m_maxMessageLength, but prints in the error message m_maxPayloadLength.
    void checkForMaxMessageLength(const util::index_t length)
    {
        if (length > m_maxMessageLength)
        {
            throw util::IllegalStateException(
                util::strPrintf("Encoded message exceeds maxMessageLength of %d, length=%d",
                    m_maxPayloadLength, length), SOURCEINFO);
        }
    }

More seriously, unless I've missed something, tryClaim() only calls checkForMaxMessageLength() (https://github.com/real-logic/Aeron/blob/master/aeron-client/src/main/cpp/Publication.h#L337) which will not check for max payload length as documented. I don't know what happens here when this calls into TermAppender::claim(), but this inconsistent use of max message length and max payload length doesn't seem right.

Yes you are correct. This code did not reflect the same semantics at the Java client. Thanks!

No worries. Thanks for the quick fix!


Improve col2im and im2col

I assume that it does simplify the code, but its computational cost is almost the same. Is it right?

Yes, almost the same.
But the computational cost is not same in col2im_gpu with dilation mode.

Ok I understand. In the case of dilated convolution, the previous one is not efficient, whereas the proposed one efficiently handles such case.

Reading the PR, I conclude that there does not any crucial problems.

LGTM

Thank you! then I would like to merge this.


Crashed in release. But Ok in debug

When running in debug mode - everything ok.
But if I gneretaed apk and run app from play market - it will be crashed with following message:
Failed uploading photo to Google Photos.
Error cause:
java.lang.NoSuchMethodError: No static method join(Ljava/lang/CharSequence;Ljava/lang/Iterable;)Ljava/lang/String; in class Ljava/lang/String; or its super classes (declaration of 'java.lang.String' appears in /system/framework/core-oj.jar)
java.lang.NoSuchMethodError: No static method join(Ljava/lang/CharSequence;Ljava/lang/Iterable;)Ljava/lang/String; in class Ljava/lang/String; or its super classes (declaration of 'java.lang.String' appears in /system/framework/core-oj.jar)
Resume url: Optional.empty
java.lang.Exception: Error cause:
java.lang.NoSuchMethodError: No static method join(Ljava/lang/CharSequence;Ljava/lang/Iterable;)Ljava/lang/String; in class Ljava/lang/String; or its super classes (declaration of 'java.lang.String' appears in /system/framework/core-oj.jar)
java.lang.NoSuchMethodError: No static method join(Ljava/lang/CharSequence;Ljava/lang/Iterable;)Ljava/lang/String; in class Ljava/lang/String; or its super classes (declaration of 'java.lang.String' appears in /system/framework/core-oj.jar)
Resume url: Optional.empty
at vitalypanov.phototracker.googlephotos.GooglePhotosAPIHelper.upload(GooglePhotosAPIHelper.java:175)
at vitalypanov.phototracker.googlephotos.GooglePhotos.upload(GooglePhotos.java:309)
at vitalypanov.phototracker.googlephotos.GooglePhotosUploadTask.doInBackground(GooglePhotosUploadTask.java:125)
at vitalypanov.phototracker.googlephotos.GooglePhotosUploadTask.doInBackground(GooglePhotosUploadTask.java:21)
at android.os.AsyncTask$2.call(AsyncTask.java:305)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
at java.lang.Thread.run(Thread.java:762)

I was cut off using of this "shi..." library from my project.
And reimplemented all work with direct REST calls. "Thank you"
So question is not actual.


MiSTer: append games/ to every mister cifs rom folder

As per @theypsilon's comments here https://github.com/danmons/retronas/issues/21#issuecomment-1029052031 (which are totally accurate), best practices would be to append games/ to the beginning of each destination folder for the layout. This proposed change ought to fix it (please double check my work, I've never done anything in Ansible before).
The core path hierarchy works like so:
https://birdybro.github.io/MkDocs_MiSTer/cores/paths/#path-priority

This could have been achieved with appending games to dest: in a single spot could it not removing a lot of duplication?
 dest: "{{ retronas_path }}/mister/games/{{ item.dest }}"
also while we are at it, couldn't we move ../roms/ up to src: and remove some additional duplication?
src: "../roms/{{ item.src }}"
Another note on the existing approach, not specifically related to these changes. I would have always thought it better to use absolute pathing instead of relative because it is clearer/cleaner, there should be a var than can be used in src:

That would cause problems if at a later time there might be a need or want to create things like /saves/ or /wallpapers/ in the root of the share. I was trying to leave that possibility open, however there is probably a better way by creating another variable in the yaml for games, but that would require a lot of additional redundancy for each of these lines too, I suspect.

The way i did this in puppet many years ago was to have a single array for the folders with src/dest that existed globally for the manifest I then have 3 loops over that array that inject the unique paths i.e. roms, saves, config etc within the loop, it shouldn't need to be any different with ansible.
In regards to saves, (going the opposite way perhaps) I had a setup that would leverage systemd path files to monitor the save paths for changes and then the sync was handled by a git commit and push in a systemd service unit .. kinda daft being binary files but I got sick of restarting Chrono Trigger. These systemd path units also leveraged the same array to generate the instances.

We'll hold off on this one until we've had a bit more of a discussion around the apprach and the new concepts you've proposed in discussion https://github.com/danmons/retronas/discussions/60.
I've created an alt branch to test ideas out. If you could take a look at the approach in the fix-mister-shares-alt branch it may help demonstrate my approach.

Thanks for the submission but we're going to close this one off and approach it as per https://github.com/danmons/retronas/pull/86 which should better accommodate the future sync and share vision you have proposed.


[ACR] Updates for 2017-03-01 api-version

New ApiVersion 2017-03-01.
Support two passwords for admin login credentials.
Renew credential now requires an argument to specify which password to regenerate.
Add SKU as a required property when creating registries.
General improvement.

Fixes https://github.com/Azure/azure-cli/issues/1889

@tjprescott Regarding https://github.com/Azure/azure-cli/issues/1889
What is the recommended way to default location now? For example, if I set the default location by az configure --defaults location=westus but my resource group is in eastus, where should the resource be created when I didn't provide a location in az acr create command?
Another question regarding default deployment_name. Considering each resource group allows a maximum of 800 deployments, wouldn't generate_deployment_name here be a concern when a large number of resources are deployed/created?

/cc @SajayAntony

Codecov Report

Merging #2563 into master will increase coverage by 0.04%.
The diff coverage is 84.31%.

@@            Coverage Diff             @@
##           master    #2563      +/-   ##
==========================================
+ Coverage   72.29%   72.34%   +0.04%
==========================================
  Files         363      363
  Lines       19832    19827       -5
  Branches     2923     2920       -3
==========================================
+ Hits        14338    14344       +6
+ Misses       4584     4576       -8
+ Partials      910      907       -3

Impacted Files
Coverage Δ

...i-acr/azure/cli/command_modules/acr/_validators.py
72.72% <100%> (+14.83%)
:arrow_up:

...-cli-acr/azure/cli/command_modules/acr/_factory.py
88.88% <100%> (+7.93%)
:arrow_up:

...li-acr/azure/cli/command_modules/acr/repository.py
51.92% <100%> (ø)
:arrow_up:

...e-cli-acr/azure/cli/command_modules/acr/_params.py
100% <100%> (ø)
:arrow_up:

...li-acr/azure/cli/command_modules/acr/credential.py
73.68% <100%> (ø)
:arrow_up:

...ure-cli-acr/azure/cli/command_modules/acr/_help.py
100% <100%> (ø)
:arrow_up:

...-cli-acr/azure/cli/command_modules/acr/commands.py
100% <100%> (ø)
:arrow_up:

...re-cli-acr/azure/cli/command_modules/acr/custom.py
80.35% <100%> (-0.35%)
:arrow_down:

...e-cli-acr/azure/cli/command_modules/acr/_format.py
38.88% <16.66%> (-2.29%)
:arrow_down:

...re-cli-acr/azure/cli/command_modules/acr/_utils.py
86.3% <85%> (+7.42%)
:arrow_up:

... and 1 more

Continue to review full report at Codecov.

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

@djyou

If you configured a default resource group, it will use that (correct me if I'm wrong @yugangw-msft). If you didn't configure a default, then  it is up to the logic of your command to decide. There's a stock validator in azure.cli.core.commands .validators called get_location_from_resource_group which will do just that. That is the most common thing to do.

We've not run into any instances of people hitting their quotas on deployments. Is there a particular place where you envision potentially exceeding the quota?

Thanks. appservice plan create defaults to the resource group's location when a location is not provided, even if I also set a default location that is different from the resource group's location. I have made the similar change to fix https://github.com/Azure/azure-cli/issues/1889.
Even our own CI exceeds the limit.  Our CLI implementation uses resource provider's name plus a small number as index to avoid deployment conflict but a deployment can also be overridden when it is completed. If we were using unique names the workaround was to clear deployments in a resource group, or use a different resource group, etc.

:shipit:


Endpoint build trigger for endpoint already waiting to be built triggers warning

2019-01-21T10:47:27.592006537Z level=debug msg="Skipped invalid state transition to waiting-to-regenerate due to: Triggering synchronous endpoint regeneration while syncing state to host" code=Warning containerID=f5678a1465 datapathPolicyRevision=0 desiredPolicyRevision=0 endpointID=83 endpointState=waiting-to-regenerate identity=34866 ipv4=<IP_ADDRESS> ipv6="f00d::a0a:100:0:f26b" k8sPodName=monitoring/prometheus-core-5c9fbf5cc6-h874w policyRevision=0 subsys=endpoint type=0
2019-01-21T10:47:27.592075407Z level=warning msg="Endpoint in inconsistent state" endpointID=83 endpointState=waiting-to-regenerate subsys=daemon

Skipping transition to Ready when another regeneration is queued is normal, but currently logged as a warning. The solution is to not log status in this case.

The first one above is a case of trying to transition to a state the endpoint is already in. It is not supported in general, as it may indicate a logic error. In this case it happens in endpoint restoration after waiting for an initial kvstore sync. It is likely that an endpoint regeneration has already been triggered for some other reason (creation?) and thus the second regeneration is not necessary, as the first one will take care of any current regeneration need as the regeneration has not yet started. It seem that skipping the 2nd (unnecessary) regeneration would be fine in this case.


Question?

it possible to use sudo command to run tun
currently neoray using osascript
my program will be signed with developer id certifcate
p.start("osascript", {"-e", QString("do shell script \"%1\" with administrator privileges")                                         .arg("pkill -2 -U 0 nekobox_core")});

I don't know anything about osascript or applescript. Sorry about that. If they require some sort of support from applications it probably not work. If it is similar to sh it should work.


Update azure-storage-blob to 12.13.0

Updates com.azure:azure-storage-blob from 12.12.0 to 12.13.0.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.azure", artifactId = "azure-storage-blob" } ]

labels: library-update, semver-minor

Closed in favor of #482


added task to catalog ip data

follow on to https://github.com/RackHD/on-tasks/pull/183 providing a task definition
@RackHD/corecommitters

👍

:+1:

+1


Readme updates

Couple of quick fixes to the README.

[...] a payload signature. Looking Glass reads the output of a previous GitHub action. To use [...]

When I read this sentence, I'm expecting to also learn about what Looking Glass does with the output of the action. Maybe we can add something about reporting using the specified GitHub feature?

filename: "can be empty if no file is associated with the report",

In the second example, could we maybe just leave the filename off? We can include the "can be empty..." copy in the first example.

msg:
       "# something was incorrect\n**expected:** some correct answer\n**got:** some incorrect answewr",
   },

This is actually a pretty common pattern, message/expected/got. Should we support this?

When I read this sentence, I'm expecting to also learn about what Looking Glass does with the output of the action. Maybe we can add something about reporting using the specified GitHub feature?

Sure, the details weren't my initial mindspace when writing this up, but if you have an idea let's add it and see!

In the second example, could we maybe just leave the filename off? We can include the "can be empty..." copy in the first example.

We can just leave it blank since it's shown as not required in the table of payload values.

This is actually a pretty common pattern, message/expected/got. Should we support this?

I like this idea, what if msg was
msg:{
    expected: "something",
    got: "this thing"
}

I'm also not sold on this payload being an array.  I don't think Looking Glass should support more than one report for initial release.
We could keep it at an array an only focus on the first item in the array, that way we can extend this easier in the future, but we may want to add some sort of key to the payload that informs Looking Glass what kind of report it's getting

hands on lab
some maintenance thing
some other sort of feedback
etc

How about the following, ideally if we could support just msg: "some message" AND the longform:
msg:{
    context: "general message to use",
    expected: "something",
    got: "this thing"
}

I'm also not sold on this payload being an array.

I agree, but this is only relevant to the action itself right? What are the alternatives?

we may want to add some sort of key to the payload that informs Looking Glass what kind of report it's getting

I'm definitely focused on the hands-on lab so I haven't been thinking about how this impacts other potential uses.


Are the install docs up to date with Laravel 5.5?

In the install docs, there is a part that says "Update the App\User::class in: 'config/auth.php' and 'database/factory/ModelFactory.php' to this:".
The first file exists, the second does not. Anyone come across this?

The file database/factories/ModelFactory.php does exist if you ran the laracogs:starter or installed a fresh app using the Laracogs Installer.
As for the docs, it does need some tweaks but I haven't found anything incompatible with Laravel 5.5
Proof for skeptics

Hhhm, I definitely ran the laracogs:starter command since that's right at that beginning of that page. I will try again to verify when I have a chance.

The latest build should no longer use the database/factories/ModelFactory.php. I'll review docs this weekend, the site is currently not up to date but I should be able to deploy this weekend. Thanks.


Depexts for opam-monorepo projects

Projects using opam-monorepo to vendor their dependencies need a proper way to handle transitive external dependencies.
Right now this is handled by hand, copying the depexts field from the lockfile to the opam file before the release and removing it afterward.
This is bad for two reasons:

it requires editing the opam file which is something we want to avoid
It uses depexts directly and therefore duplicates the work that's been done in conf-* packages. This also means that it won't benefit from changes in said conf-* packages and that opam maintainers have to update opam-monorepo projects metadata when that happens.

During discussions with the opam team, we decided that 1 could be solved by writing the depexts to a separate opam package, somehting along the lines of -conf.opam, generated during the lock step. The main package in an opam-monorepo should always depend on this package with a {=version} constraint and they should always be released together.
Ideally opam file generation should also have a opam-monorepo mode where it automatically add the dependency from the main package to this one.
This extra package would be virtual (meaning dune-release must also be adapted to properly release this) and have all the external deps in the form of dependencies on conf-* packages whenever possible and would only contain a depexts field if the project or some of its non conf dependencies had such fields.

cc @kit-ty-kate

cc @kit-ty-kate

cc @emillon how should we handle this in the CI?
My impression is that this file should be versioned along with the lockfile. We should then be able to pin it and run opam depexts <main-package-name>-conf without too much trouble. Does that seem correct to you?

cc @emillon how should we handle this in the CI?
My impression is that this file should be versioned along with the lockfile. We should then be able to pin it and run opam depexts <main-package-name>-conf without too much trouble. Does that seem correct to you?

I think that the point of using lock files is to have something that represents the exact build plan. It's expected that it introduces some duplication, since it's a way to take a snapshot of the relevant bits of the opam repository. In my opinion that's a tradeoff you make when you opt into an opam-monorepo workflow. You become responsible for fixing issues like this (that opam-repository maintainers could do for you otherwise). I think there's a parallel to be made with dynamic vs static linking: when something is statically linked, it won't benefit from changes until it is linked again (here: until it's locked again).
If we consider that conf packages are "independent" from the application, it can make sense not to lock them and instead keep the dependency resolved at install time. That means that opam-repository can fix (or break) your project by changing the depext definitions. This strategy can even be selected at lock time.
Regarding creating an extra package-conf opam package, I don't think that this has any advantage compared to keeping the conf-x dependencies (the only difference is when a package has depexts itself, but you can either duplicate it in the lock file or extract a conf package, which is probably a good idea in any case).

I think that the point of using lock files is to have something that represents the exact build plan. It's expected that it introduces some duplication, since it's a way to take a snapshot of the relevant bits of the opam repository. In my opinion that's a tradeoff you make when you opt into an opam-monorepo workflow. You become responsible for fixing issues like this (that opam-repository maintainers could do for you otherwise). I think there's a parallel to be made with dynamic vs static linking: when something is statically linked, it won't benefit from changes until it is linked again (here: until it's locked again).
If we consider that conf packages are "independent" from the application, it can make sense not to lock them and instead keep the dependency resolved at install time. That means that opam-repository can fix (or break) your project by changing the depext definitions. This strategy can even be selected at lock time.
Regarding creating an extra package-conf opam package, I don't think that this has any advantage compared to keeping the conf-x dependencies (the only difference is when a package has depexts itself, but you can either duplicate it in the lock file or extract a conf package, which is probably a good idea in any case).

Regarding "how to handle that in CI", there's not much to change:

if all conf dependencies are statically resolved (like in a 0.2 lock file), the CI needs access to the oldest opam-monorepo state that touched dune, opam-monorepo and the selected compiler.
if the lock file has "dynamic" conf-x dependencies (everything locked except (transitive) conf packages, relaxed bounds for conf packages, and only self depexts + transitive depexts of non-conf packages), the CI needs access to the oldest opam-monorepo state that touched dune, opam-monorepo, the compiler and the transitive conf packages (this is a more recent version of the repo and will have more cache misses)

Regarding "how to handle that in CI", there's not much to change:

if all conf dependencies are statically resolved (like in a 0.2 lock file), the CI needs access to the oldest opam-monorepo state that touched dune, opam-monorepo and the selected compiler.
if the lock file has "dynamic" conf-x dependencies (everything locked except (transitive) conf packages, relaxed bounds for conf packages, and only self depexts + transitive depexts of non-conf packages), the CI needs access to the oldest opam-monorepo state that touched dune, opam-monorepo, the compiler and the transitive conf packages (this is a more recent version of the repo and will have more cache misses)

One thing I wish to clarify is that opam-monorepo isn't really intended to "lock" your depexts as well. The best it can do is lock a depext formula which will be interpreted by another tool and will result in the installation of a system package without further control on its source or version so I think it's "okay" if they are less tightly controlled by opam-monorepo.
That being said I agree changes upstream in the conf packages might result in breaking an opam-monorepo project if we don't control their version tightly and I'm not sure I understand why the opam maintainers would want to fix an opam-monorepo package's opam file in the first place, even if it's not in sync with the conf package it derived its depexts from.

Regarding creating an extra package-conf opam package, I don't think that this has any advantage compared to keeping the conf-x dependencies (the only difference is when a package has depexts itself, but you can either duplicate it in the lock file or extract a conf package, which is probably a good idea in any case).

That's not actually true since the conf packages might be transitive dependencies and therefore not a part of the opam file. The extra package allow us to release without any modification to the opam files in the repo.

One thing I wish to clarify is that opam-monorepo isn't really intended to "lock" your depexts as well. The best it can do is lock a depext formula which will be interpreted by another tool and will result in the installation of a system package without further control on its source or version so I think it's "okay" if they are less tightly controlled by opam-monorepo.
That being said I agree changes upstream in the conf packages might result in breaking an opam-monorepo project if we don't control their version tightly and I'm not sure I understand why the opam maintainers would want to fix an opam-monorepo package's opam file in the first place, even if it's not in sync with the conf package it derived its depexts from.

Regarding creating an extra package-conf opam package, I don't think that this has any advantage compared to keeping the conf-x dependencies (the only difference is when a package has depexts itself, but you can either duplicate it in the lock file or extract a conf package, which is probably a good idea in any case).

That's not actually true since the conf packages might be transitive dependencies and therefore not a part of the opam file. The extra package allow us to release without any modification to the opam files in the repo.


Fixes client build issues

Several HTML elements were getting passed extra empty lists that were causing the client project to fail building.
** Someone else may already be addressing this, but I fixed it for my local development and thought it might be helpful if someone isn't working on it.  I can create an issue for this if that's more appropriate.**

Thx


Fixed base path variable

Description
This pr solves the issues with the base uri path. In React Scripts everything depended from a so called base tag. This base tag was rewritten when serving the frontend leading to the JavaScript and CSS being loaded from the rewritten tag in the Java code.  This pr simply takes all resource links and points them to a new location that is set via the properties.
What does this pr not solve
During my testing I realized that you still need a proxy that rewrites the paths and fetches them from the original location. Only the paths in the index.html are rewritten. So the resource location needs to be configured via proxy config but this seems to be also the case before.
Closes #3742

I ran via
$ ZIPKIN_UI_BASEPATH=/admin/zipkin java -jar ./zipkin-server/target/zipkin-server-*slim.jar

Then, looked at the links and look good
$ curl -s localhost:9411/zipkin/index.html |tidy -q -i --tidy-mark no --wrap 1024

<!DOCTYPE html>

  <base href="/zipkin">
  <meta charset="utf-8">
  <link rel="icon" href="/admin/zipkin/favicon.ico">
  <title>Zipkin</title>

  <link rel="stylesheet" href="/admin/zipkin/static/css/index.a7aa86b4.css">

  You need to enable JavaScript to run this app.

sorry screwed something up.. one sec

ok ready.

Thanks for the fix and explanation @SamTV12345!


cleanup: Run standard:fix

This PR offers the auto-fix for the a standardrb violation.
This gets us back to green.
Seen when cf5dcf7 ran its build.

Thanks!


New App: Pterodactyl Server Status

Description
Gets a single Pterodactyl server's status.
Copilot

🤖 Generated by Copilot at 6266714
Summary
📄🐉📝

This pull request adds a new app called pterostatus, which shows the status of a Pterodactyl server on the Tidbyt device. It includes a manifest.yaml file, a ptero_status.star script, and a README.md file that define the app's metadata, logic, and documentation.

pterostatus app
Shows server status on screen
Autumn leaves falling

Walkthrough

Create a new app called pterostatus that displays the status of a Pterodactyl server (link, link, link)
Define the app's metadata in manifest.yaml, including its id, name, summary, description, author, file name, and package name (link)
Implement the app's logic in ptero_status.star, using the http, render, and schema modules to make API requests, parse JSON, render text and circle, and define configuration schema (link)
Define a main function that takes the config as an argument and returns a render.Root object that contains the app's display (link)
Define a get_schema function that returns a schema.Schema object that describes the app's settings (link)
Provide a brief description of the app, the author, and some screenshots in README.md (link)

I have read the CLA Document and I hereby sign the CLA

recheck

recheck


Undefined when using prefilter with record selector of record selector

https://forum.cortezaproject.org/t/record-values-fieldname-filter-quirk/1629/4

Its a per user configuration issue, needed of a fallback.
For example FieldNameModuleC = ${record.values.FieldNameInModuleAthatExistsAsArecordInModuleB || "''"}


Disabling threads with native gcc-11/-12 produces a compiler error

Running the build specified in the ci file (or an example given in the readme) with an official arm-none-eabi toolchain fails to compile.

Project Version/Tag/Commit: 3d809a75669f3f3600a57ac2ab30f71591338bfb
Operating System: Fedora 36
SDK version: ?
Toolchain version: See log; tried with two later releases with same effect

I set the path to the compiler by editing build/cross/arm.txt
I can imagine that there are some requirements on how the compiler itself is compiled (in that case having threads enabled?). Could you provide a working example with an official arm-none-eabi-gcc or point to a compiler that works with the example configuration of this project?
Thanks!
$ meson buildresults/arm/ --cross-file build/cross/arm.txt --cross-file build/cross/cortex-m3.txt -Denable-threading=false -Dlibcxx-enable-chrono=false -Dlibcxx-monotonic-clock=false

DEPRECATION: c_args in the [properties] section of the machine file is deprecated, use the [built-in options] section.
DEPRECATION: c_link_args in the [properties] section of the machine file is deprecated, use the [built-in options] section.
DEPRECATION: cpp_args in the [properties] section of the machine file is deprecated, use the [built-in options] section.
DEPRECATION: cpp_link_args in the [properties] section of the machine file is deprecated, use the [built-in options] section.
The Meson build system
Version: 0.63.0
Source dir: /home/user/Downloads/libcpp
Build dir: /home/user/Downloads/libcpp/buildresults/arm
Build type: cross build
Project name: Embedded Artistry libcpp
Project version: undefined
C++ compiler for the host machine: /home/user/.local/gcc/9-2019/bin/arm-none-eabi-c++ (gcc 9.2.1 "arm-none-eabi-c++ (GNU Tools for Arm Embedded Processors 9-2019-q4-major) 9.2.1 20191025 (release) [ARM/arm-9-branch revision 277599]")
C++ linker for the host machine: /home/user/.local/gcc/9-2019/bin/arm-none-eabi-c++ ld.bfd <IP_ADDRESS>91025
C++ compiler for the build machine: ccache c++ (gcc 12.1.1 "c++ (GCC) 12.1.1 20220507 (Red Hat 12.1.1-1)")
C++ linker for the build machine: c++ ld.bfd 2.37-27
Build machine cpu family: x86_64
Build machine cpu: x86_64
Host machine cpu family: arm
Host machine cpu: cortex-m3
Target machine cpu family: arm
Target machine cpu: cortex-m3
Compiler for C++ supports arguments -Wold-style-cast: YES
Compiler for C++ supports arguments -Wnon-virtual-dtor: YES
Compiler for C++ supports arguments -Wctor-dtor-privacy: YES
Compiler for C++ supports arguments -Woverloaded-virtual: YES
Compiler for C++ supports arguments -Wnoexcept: YES
Compiler for C++ supports arguments -Wstrict-null-sentinel: YES
Compiler for C++ supports arguments -Wuseless-cast: YES
Compiler for C++ supports arguments -Wzero-as-null-pointer-constant: YES
Compiler for C++ supports arguments -Wextra-semi: YES
Compiler for C++ supports arguments -fdiagnostics-show-option: YES
Compiler for C++ supports arguments -fcolor-diagnostics: NO
Compiler for C++ supports arguments -ffunction-sections: YES
Compiler for C++ supports arguments -fdata-sections: YES
Compiler for C++ supports arguments -fdevirtualize: YES
Compiler for C++ supports arguments -Wno-unknown-pragmas: YES
Compiler for C++ supports arguments -Wno-c++98-compat: NO
Compiler for C++ supports arguments -Wno-c++98-compat-pedantic: NO
Compiler for C++ supports arguments -Wno-padded: YES
Compiler for C++ supports arguments -Wno-exit-time-destructors: NO
Compiler for C++ supports arguments -Wno-global-constructors: NO
Compiler for C++ supports arguments -Wno-covered-switch-default: NO
Compiler for C++ supports arguments -Wfloat-equal: YES
Compiler for C++ supports arguments -Wconversion: YES
Compiler for C++ supports arguments -Wlogical-op: YES
Compiler for C++ supports arguments -Wundef: YES
Compiler for C++ supports arguments -Wredundant-decls: YES
Compiler for C++ supports arguments -Wshadow: YES
Compiler for C++ supports arguments -Wstrict-overflow=2: YES
Compiler for C++ supports arguments -Wwrite-strings: YES
Compiler for C++ supports arguments -Wpointer-arith: YES
Compiler for C++ supports arguments -Wcast-qual: YES
Compiler for C++ supports arguments -Wformat=2: YES
Compiler for C++ supports arguments -Wformat-truncation: YES
Compiler for C++ supports arguments -Wmissing-include-dirs: YES
Compiler for C++ supports arguments -Wcast-align: YES
Compiler for C++ supports arguments -Wswitch-enum: YES
Compiler for C++ supports arguments -Wsign-conversion: YES
Compiler for C++ supports arguments -Wdisabled-optimization: YES
Compiler for C++ supports arguments -Winline: YES
Compiler for C++ supports arguments -Winvalid-pch: YES
Compiler for C++ supports arguments -Wmissing-declarations: YES
Compiler for C++ supports arguments -Wdouble-promotion: YES
Compiler for C++ supports arguments -Wshadow: YES (cached)
Compiler for C++ supports arguments -Wtrampolines: YES
Compiler for C++ supports arguments -Wvector-operation-performance: YES
Compiler for C++ supports arguments -Wshift-overflow=2: YES
Compiler for C++ supports arguments -Wnull-dereference: YES
Compiler for C++ supports arguments -Wduplicated-cond: YES
Compiler for C++ supports arguments -Wshift-overflow=2: YES (cached)
Compiler for C++ supports arguments -Wnull-dereference: YES (cached)
Compiler for C++ supports arguments -Wduplicated-cond: YES (cached)
Compiler for C++ supports arguments -Wcast-align=strict: YES
Compiler for C++ supports arguments -Wno-pedantic: YES
Compiler for C++ supports arguments -W: YES
Compiler for C++ supports arguments -Wwrite-strings: YES (cached)
Compiler for C++ supports arguments -Wno-unused-member-function: NO
Compiler for C++ supports arguments -Wno-useless-cast: YES
Compiler for C++ supports arguments -Wno-weak-vtables: NO
Compiler for C++ supports arguments -Wno-missing-prototypes: NO
Compiler for C++ supports arguments -Wno-class-varargs: NO
Compiler for C++ supports arguments -Wno-unused-template: NO
Compiler for C++ supports arguments -Wno-zero-as-null-pointer-constant: YES
Compiler for C++ supports arguments -Wno-reserved-id-macro: NO
Compiler for C++ supports arguments -Wno-deprecated-dynamic-exception-spec: NO
Compiler for C++ supports arguments -Wno-comma: NO
Compiler for C++ supports arguments -Wno-old-style-cast: YES
Compiler for C++ supports arguments -Werror=return-type: YES
Compiler for C++ supports arguments -Wno-unused-parameter: YES
Compiler for C++ supports arguments -Wno-long-long: YES
Compiler for C++ supports arguments -Wno-switch-default: YES
Compiler for C++ supports arguments -Wno-switch-enum: YES
Compiler for C++ supports arguments -Wno-inline: YES
Compiler for C++ supports arguments -Wno-effc++: YES
Compiler for C++ supports arguments -Wno-cast-align: YES
Compiler for C++ supports arguments -Wold-style-cast: YES
Compiler for C++ supports arguments -Wnon-virtual-dtor: YES
Compiler for C++ supports arguments -Wctor-dtor-privacy: YES
Compiler for C++ supports arguments -Woverloaded-virtual: YES
Compiler for C++ supports arguments -Wnoexcept: YES
Compiler for C++ supports arguments -Wstrict-null-sentinel: YES
Compiler for C++ supports arguments -Wuseless-cast: YES
Compiler for C++ supports arguments -Wzero-as-null-pointer-constant: YES
Compiler for C++ supports arguments -Wextra-semi: YES
Compiler for C++ supports arguments -fdiagnostics-show-option: YES
Compiler for C++ supports arguments -fcolor-diagnostics: NO
Compiler for C++ supports arguments -ffunction-sections: YES
Compiler for C++ supports arguments -fdata-sections: YES
Compiler for C++ supports arguments -fdevirtualize: YES
Compiler for C++ supports arguments -Wno-unknown-pragmas: YES
Compiler for C++ supports arguments -Wno-c++98-compat: NO
Compiler for C++ supports arguments -Wno-c++98-compat-pedantic: NO
Compiler for C++ supports arguments -Wno-padded: YES
Compiler for C++ supports arguments -Wno-exit-time-destructors: NO
Compiler for C++ supports arguments -Wno-global-constructors: NO
Compiler for C++ supports arguments -Wno-covered-switch-default: NO
Compiler for C++ supports arguments -Wfloat-equal: YES
Compiler for C++ supports arguments -Wconversion: YES
Compiler for C++ supports arguments -Wlogical-op: YES
Compiler for C++ supports arguments -Wundef: YES
Compiler for C++ supports arguments -Wredundant-decls: YES
Compiler for C++ supports arguments -Wshadow: YES
Compiler for C++ supports arguments -Wstrict-overflow=2: YES
Compiler for C++ supports arguments -Wwrite-strings: YES
Compiler for C++ supports arguments -Wpointer-arith: YES
Compiler for C++ supports arguments -Wcast-qual: YES
Compiler for C++ supports arguments -Wformat=2: YES
Compiler for C++ supports arguments -Wformat-truncation: YES
Compiler for C++ supports arguments -Wmissing-include-dirs: YES
Compiler for C++ supports arguments -Wcast-align: YES
Compiler for C++ supports arguments -Wswitch-enum: YES
Compiler for C++ supports arguments -Wsign-conversion: YES
Compiler for C++ supports arguments -Wdisabled-optimization: YES
Compiler for C++ supports arguments -Winline: YES
Compiler for C++ supports arguments -Winvalid-pch: YES
Compiler for C++ supports arguments -Wmissing-declarations: YES
Compiler for C++ supports arguments -Wdouble-promotion: YES
Compiler for C++ supports arguments -Wshadow: YES (cached)
Compiler for C++ supports arguments -Wtrampolines: YES
Compiler for C++ supports arguments -Wvector-operation-performance: YES
Compiler for C++ supports arguments -Wshift-overflow=2: YES
Compiler for C++ supports arguments -Wnull-dereference: YES
Compiler for C++ supports arguments -Wduplicated-cond: YES
Compiler for C++ supports arguments -Wshift-overflow=2: YES (cached)
Compiler for C++ supports arguments -Wnull-dereference: YES (cached)
Compiler for C++ supports arguments -Wduplicated-cond: YES (cached)
Compiler for C++ supports arguments -Wcast-align=strict: YES
Compiler for C++ supports arguments -Wno-pedantic: YES
Compiler for C++ supports arguments -W: YES
Compiler for C++ supports arguments -Wwrite-strings: YES (cached)
Compiler for C++ supports arguments -Wno-unused-member-function: NO
Compiler for C++ supports arguments -Wno-useless-cast: YES
Compiler for C++ supports arguments -Wno-weak-vtables: NO
Compiler for C++ supports arguments -Wno-missing-prototypes: NO
Compiler for C++ supports arguments -Wno-class-varargs: NO
Compiler for C++ supports arguments -Wno-unused-template: NO
Compiler for C++ supports arguments -Wno-zero-as-null-pointer-constant: YES
Compiler for C++ supports arguments -Wno-reserved-id-macro: NO
Compiler for C++ supports arguments -Wno-deprecated-dynamic-exception-spec: NO
Compiler for C++ supports arguments -Wno-comma: NO
Compiler for C++ supports arguments -Wno-old-style-cast: YES
Compiler for C++ supports arguments -Werror=return-type: YES
Compiler for C++ supports arguments -Wno-unused-parameter: YES
Compiler for C++ supports arguments -Wno-long-long: YES
Compiler for C++ supports arguments -Wno-switch-default: YES
Compiler for C++ supports arguments -Wno-switch-enum: YES
Compiler for C++ supports arguments -Wno-inline: YES
Compiler for C++ supports arguments -Wno-effc++: YES
Compiler for C++ supports arguments -Wno-cast-align: YES
build/compiler/check-and-apply-flags/meson.build:47: WARNING: Expected variable link_settings_list not defined. Not processing linker arguments.
Compiler for C++ supports arguments -Wmismatched-tags: NO
Compiler for C++ supports arguments -Wnewline-eof: NO
Compiler for C++ supports arguments -Wshorten-64-to-32: NO
Compiler for C++ supports arguments -Wconversion: YES (cached)
Compiler for C++ supports arguments -Wchar-subscripts: YES
Compiler for C++ supports arguments -Wmissing-braces: YES
Compiler for C++ supports arguments -Wshadow: YES (cached)
Compiler for C++ supports arguments -Wsign-compare: YES
Compiler for C++ supports arguments -Wsign-conversion: YES (cached)
Compiler for C++ supports arguments -Wstrict-aliasing=2: YES
Compiler for C++ supports arguments -Wstrict-overflow=4: YES
Compiler for C++ supports arguments -Wunused-variable: YES
Compiler for C++ supports arguments -Wundef: YES (cached)
Compiler for C++ supports arguments -Wno-switch: YES
Compiler for C++ supports arguments -Wno-missing-declarations: YES
Compiler for C++ supports arguments -Wmismatched-tags: YES
Compiler for C++ supports arguments -Wnewline-eof: NO
Compiler for C++ supports arguments -Wshorten-64-to-32: NO
Compiler for C++ supports arguments -Wconversion: YES (cached)
Compiler for C++ supports arguments -Wchar-subscripts: YES
Compiler for C++ supports arguments -Wmissing-braces: YES
Compiler for C++ supports arguments -Wshadow: YES (cached)
Compiler for C++ supports arguments -Wsign-compare: YES
Compiler for C++ supports arguments -Wsign-conversion: YES (cached)
Compiler for C++ supports arguments -Wstrict-aliasing=2: YES
Compiler for C++ supports arguments -Wstrict-overflow=4: YES
Compiler for C++ supports arguments -Wunused-variable: YES
Compiler for C++ supports arguments -Wundef: YES (cached)
Compiler for C++ supports arguments -Wno-switch: YES
Compiler for C++ supports arguments -Wno-missing-declarations: YES
Compiler for C++ supports arguments -Wno-literal-suffix: YES
Compiler for C++ supports arguments -Wno-c++14-compat: YES
Compiler for C++ supports arguments -Wno-noexcept-type: YES
Compiler for C++ supports arguments -Wno-user-defined-literals: NO
Compiler for C++ supports arguments -Wno-covered-switch-default: NO (cached)
Compiler for C++ supports arguments -Wno-sign-conversion: YES
Compiler for C++ supports arguments -Wno-conversion: YES
Compiler for C++ supports arguments -Wno-double-promotion: YES
Compiler for C++ supports arguments -Wno-literal-suffix: YES
Compiler for C++ supports arguments -Wno-c++14-compat: YES
Compiler for C++ supports arguments -Wno-noexcept-type: YES
Compiler for C++ supports arguments -Wno-user-defined-literals: NO
Compiler for C++ supports arguments -Wno-covered-switch-default: NO (cached)
Compiler for C++ supports arguments -Wno-sign-conversion: YES
Compiler for C++ supports arguments -Wno-conversion: YES
Compiler for C++ supports arguments -Wno-double-promotion: YES
Message: Compiling with the built-in libc and system headers
Message: Exceptions are enabled
Message: Building without threading support.
 -I../.. -Iinclude/c++ -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor -Wextra -Wpedantic -std=c++17 -O2 -Wold-style-cast -Wnon-virtual-dtor -Wctor-dtor-privacy -Woverloaded-virtual -Wnoexcept -Wstrict-null-sentinel -Wuseless-cast -Wzero-as-null-pointer-constant -Wextra-semi -fdiagnostics-show-option -ffunction-sections -fdata-sections -fdevirtualize -Wno-unknown-pragmas -Wno-padded -Wfloat-equal -Wconversion -Wlogical-op -Wundef -Wredundant-decls -Wshadow -Wstrict-overflow=2 -Wwrite-strings -Wpointer-arith -Wcast-qual -Wformat=2 -Wformat-truncation -Wmissing-include-dirs -Wcast-align -Wswitch-enum -Wsign-conversion -Wdisabled-optimization -Winline -Winvalid-pch -Wmissing-declarations -Wdouble-promotion -Wshadow -Wtrampolines -Wvector-operation-performance -Wshift-overflow=2 -Wnull-dereference -Wduplicated-cond -Wshift-overflow=2 -Wnull-dereference -Wduplicated-cond -Wcast-align=strict -Wno-pedantic -W -Wwrite-strings -Wno-useless-cast -Wno-zero-as-null-pointer-constant -Wno-old-style-cast -Werror=return-type -Wno-unused-parameter -Wno-long-long -Wno-switch-default -Wno-switch-enum -Wno-inline -Wno-effc++ -Wno-cast-align -fPIC -isystem../../include/c++ -isysteminclude/c++ -isystem../../include/c++abi -isysteminclude/c++abi -D_LIBCXXABI_BUILDING_LIBRARY -D_LIBCPP_ENABLE_CXX17_REMOVED_UNEXPECTED_FUNCTIONS -D_GNU_SOURCE -nostdinc++ -funwind-tables -DLIBCXXABI_USE_LLVM_UNWINDER -DLIBCXXABI_SILENT_TERMINATE -D_LIBCXXABI_HAS_NO_THREADS -Wmismatched-tags -Wconversion -Wchar-subscripts -Wmissing-braces -Wshadow -Wsign-compare -Wsign-conversion -Wstrict-aliasing=2 -Wstrict-overflow=4 -Wunused-variable -Wundef -Wno-switch -Wno-missing-declarations -idirafter/usr/include -MD -MQ libc++abi_native.a.p/libcxxabi_src_cxa_virtual.cpp.o -MF libc++abi_native.a.p/libcxxabi_src_cxa_virtual.cpp.o.d -o libc++abi_native.a.p/libcxxabi_src_cxa_virtual.cpp.o -c ../../libcxxabi/src/cxa_virtual.cpp
In Datei, eingebunden von include/c++/stddef.h:39,
                 von include/c++abi/cxxabi.h:17,
                 von ../../libcxxabi/src/cxa_virtual.cpp:9:
include/c++/__config:1176:2: Fehler: #error _LIBCPP_HAS_NO_THREADS cannot be set when __STDCPP_THREADS__ is set.
 1176 | #error _LIBCPP_HAS_NO_THREADS cannot be set when __STDCPP_THREADS__ is set.
      |  ^~~~~

Starting point: running that exact same set of commands works fine for me with official arm-gcc 10.3.1 + MacOS clang.
In your case looks like the failure is not with the cross-compiler but with the native GCC. I installed gcc-12 and can reproduce the error. It also fails with gcc-11; gcc-10 and earlier work fine. It could be that the compiler is now defining that value when it wasn't before.

I see. Didn't realize that the native libs are also automatically built. I expected that to only happen if no cross files where selected. If I manually remove those targets, things work as expected.
Regarding the original issue: Looks like the old gcc behavior was not correct then (the compiler almost certainly had threads support but __STDCPP_THREADS__ was not set). Right?

I agree. Haven't seen that this was already fixed upstream

Fyi: I managed to build upstream 'libcxxandlibcxxabi` in a simple configuration against newlib and picolibc with just a few tweaks. I think it should not be too hard to create an own "mirror" (as in just a copy of some directories and small tweaks or moving files around) of those libraries.

That's largely what this repo is (copy of the code + some alternative implementations I substitute), I just need to migrate from the old llvm-mirror submodules to a newer process that keeps them in sync re: what you described with a sparse checkout + filter.

Yes, I know. I was just suggesting to kind of recreate/reactivate the old mirror so you could just point to a different repo and commit from this repo. Following upstream's history directly is of course preferable if it works without easily

Got it, that was the original approach I had in mind and what I'm likely to fall back to - you just got the wheels turning in my head :).


Modify Scan

What file creates the NMAp scan line?  I would like to add the -Pn flag.  Having issues in my environment when trying to do host discovery before scan.

Add it into this args list and restart Kraken: https://github.com/Sw4mpf0x/Kraken/blob/master/Kraken/Web_Scout/tasks.py#L555


Showcase Submission for challenges/98-quadtree

Thank you mars91 for your contribution! A member of the Coding Train team will review it shortly.

Maxwell–Boltzmann distribution
mars91

Wow!


Docker builds do not honour the --ssh flag being passed through

Executing ./makejdk-any-platform.sh --keep --ssh --version jdk8u
I'm still challenged for my username and password (https download challenge)

Is the issue still valid? I was not able to reproduce it.

Yeah - private key doesn't get passed through to the Docker container.  But that said -ssh is really not required as all repos we pull from have https anon access (or should do)

This is because the docker container does not copy your private keys. We should probably just add a step to the docker container to copy your id_rsa if --ssh is specified

This issue should be closed