When the from path is an emptry string "" a null value is improperly assigned

When the from path is "" it will be improperly assigned a null value
Example:
patch: [{"op":"copy","from":"","path":"/archive"}]
JSON: {"wow":"cool"}
The error message:
TypeError: null is not an object (evaluating 'from.get')
(same for move, although that should result in a warning)
Line 448:
var from = operation.from ? new JSONPointer(operation.from) : null;
This seems to be the culprit: operation.from is evaluating as "falsey" when it's an empty string so null is being returned by the ternary expression
One fix is:
var from = operation.from !== undefined ? new JSONPointer(operation.from) : null;
With that in place the operation completes as expected:
{
  "wow": "cool",
  "archive": {
    "wow": "cool"
  }
}

Or in the case of a move:
patch: [{"op":"move","from":"","path":"/archive"}]
JSON: {"wow":"cool"}
The proper result now displays:
Error: destination must not be a child of source

@almost You sick of jsonpatch bugs yet? Glad you could get #42, there's this oldie too. I swear this is the last one from me! 😅


Duplicate entries are allowed to be stored

During some testing in a local environment (thanks Docker!) I discovered it is possible to push an entry with the same timestamp and git_hash again and have both of them retrievable when fetching the metrics.
I do not personally think this should be the right behaviour. Ideally I would expect to see the new entry to replace the old one. As on what would be the primary key I would suggest to be the git_hash as that is the ultimate source of truth and it is salted with the timestamp as well.

@laqieer yeah I don't disagree. This is an oversight, not intended behavior. I have a ton of plates spinning, so I can't guarantee when I'll get to this. But please feel free to submit a PR!

Presumably multiple entries (from different versions, for example) could share the same git hash. But I think just having a unique constraint on git hash + a few other things would indeed be good. I'll try to work on this soon


ZRANGEBYSCORE fails with Timeout

We
are recieving timeout while calling
"ZRANGEBYSCORE" "yprofile.UNACK.yprofileScheduledEvents.yprofile" "0.0" "1.504169738376E12" "limit" "0" "1000" "withscores"

Called from :
https://github.com/Netflix/dyno-queues/blob/4c2c748530545d133bbbdfe83f74bbc8ad339c8b/dyno-queues-redis/src/main/java/com/netflix/dyno/queues/redis/RedisDynoQueue.java#L538
The setup for 3 node rack of dynomite is clone of given one
dyn_o_mite:
  secure_server_option: rack
  read_consistency: dc_quorum
  write_consistency: dc_quorum
  datacenter: dc
  rack: rack1
  dyn_listen: XX.XX.XX.12:8101
  dyn_seeds:
    - XX.XX.XX.13:8101:rack2:dc:1383429731
    - XX.XX.XX.14:8101:rack3:dc:1383429731
  listen: <IP_ADDRESS>:18102
  servers:
    - <IP_ADDRESS>:6379:1 #assigned to local iface intentionally
  tokens: '1383429731'

Exception is thrown
redis.clients.jedis.exceptions.JedisDataException: ERR Peer: Connection timed out
	at com.netflix.dyno.jedis.JedisConnectionFactory$JedisConnection.execute(JedisConnectionFactory.java:138)
	at com.netflix.dyno.connectionpool.impl.ConnectionPoolImpl.executeWithFailover(ConnectionPoolImpl.java:298)
	at com.netflix.dyno.jedis.DynoJedisClient.d_zrangeByScoreWithScores(DynoJedisClient.java:2643)
	at com.netflix.dyno.jedis.DynoJedisClient.zrangeByScoreWithScores(DynoJedisClient.java:2636)
	at com.hybris.dyno.queues.redis.RedisDynoQueue.lambda$processUnacks$12(RedisDynoQueue.java:591)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:748)
Caused by: redis.clients.jedis.exceptions.JedisDataException: ERR Peer: Connection timed out
	at redis.clients.jedis.Protocol.processError(Protocol.java:127)
	at redis.clients.jedis.Protocol.process(Protocol.java:161)
	at redis.clients.jedis.Protocol.read(Protocol.java:215)
	at redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:340)
	at redis.clients.jedis.Connection.getBinaryMultiBulkReply(Connection.java:276)
	at redis.clients.jedis.Connection.getMultiBulkReply(Connection.java:269)
	at redis.clients.jedis.Jedis.getTupledSet(Jedis.java:2162)
	at redis.clients.jedis.Jedis.zrangeByScoreWithScores(Jedis.java:2150)
	at com.netflix.dyno.jedis.DynoJedisClient$117.execute(DynoJedisClient.java:2649)
	at com.netflix.dyno.jedis.DynoJedisClient$117.execute(DynoJedisClient.java:2644)
	at com.netflix.dyno.jedis.JedisConnectionFactory$JedisConnection.execute(JedisConnectionFactory.java:114)
	... 8 common frames omitted

!!!The exception seem to occur only on dynomite layer!!!
The problem seems to be reproducable when reached >15k entries in the UNACKED queue.
The problem is not volatile - restart of the redis/dynomite doesn't help
It seems that while calling zrangeByScoreWithScores during migrating back UNACKED events back to QUEUE we get into state that dynomite  could not process them.
Strangely depending on the criteria of the ZRANGEBYSCORE this issue occurs or not.
It looks like the timeout is issued while XX.XX.XX.12 node getting synchronous response from one of the XX.XX.XX.13,XX.XX.XX.14 in RACK.
Actually both XX.XX.XX.13, XX.XX.XX.14 calls failed.
We have captured the logs on dynoqueue on node XX.XX.XX.12 DQ_12.log
We have captured the logs on dynoqueue on node XX.XX.XX.13/14 DQ_14.log
We also captured the traffic from Redis at node XX.XX.XX.14 talking to dynomite dump.log

@maryoush The problem seems to be that the xx12 is sending the message with id 28825 to other peer xx13. It then receives the response but is not able to decrypt it:
[2017-08-31 09:45:43.575] dyn_aes_decrypt:367 Bad data in EVP_DecryptFinal_ex, crypto data with 16336 bytes of data
and so that message gets dropped and hence the peer timeout.Do you have logs for the xx.13 host with that message id in it?

Also is there a reason why you have encryption within the DC?

Hi @shailesh33
what additional information log you would expect to have in order to hunt down the issue ?

The logs of the other node which you missed. Also, do you need Interzone encryption?

@shailesh33 honestly no, we will try to gather more logs and we will switch off encryption (because of in current setup there is no needs for encryption)

@KowalczykBartek @maryoush Any further steps on this?

Hi ! I forgot to mention, seems that in newest build this doesn't appear :) We didn't test this on production I just made couple of tests on my computer - I don't know if it can be open - or if we can close this and eventually re-open ?
Thanks !

I am interested in knowing which newest build is this? I know I fixed a decryption bug on the latest code.

We fixed a few decryption issues since, and haven't seen an error like the one mentioned here. Closing.


Run phpUnit on travis ci

Some of php tests are still failing.
Tests\Unit\CommandRouteGeneratorTest::file_is_created_with_the_expected_structure_when_named_routes_exist
is failing because of difference in application domain url.

Tightenco\Tests\Unit\BladeRouteGeneratorTest::generator_at_least_vaguely_works_and_outputs_something_vaguely_right_ish
is failing because we no longer have JSON.parse() method to search into output string.

@ankurk91 I got them fixed locally. I'll push up if your build fails.

I was able to fix one of them.
Push your changes because i not able to understand the remaining test failure.


Unable to debug flask and bottle projects with PTVSD 5.*

There's an issue with bottle and flask web projects. Create new project, install packages as needed and press F5, the browser starts and attempts to load the page but it never ends. By comparison, legacy debugger works fine, also start without debugging is fine.
Related to #5948

I've found a workaround.
Clear the Launch URL text box under project properties debug tab. This will prevent the browser from opening automatically.
Set breakpoint in your route and start debugging.
Manually open browser and navigate to the server URL (which you can see printed in the console)
Request should succeed and breakpoint in the route handler gets hit.
Hypothesis:
It appears to be that the browser is opened too early and the request that is sent to the server may be incomplete/partial and that puts the server in a state that no longer responds to requests (refreshing or sending more requests make no difference).
This used to happen periodically in the past with older versions of ptvsd, more frequently with Edge or Internet Explorer. Maybe those browsers just started faster than Chrome, causing the issue more easily.
Maybe now that we're starting up the adapter python process then starting the app process means that the server is ready to accept requests later than it used to be in the past, causing all browsers to be sending a request too early.
If we switch to watching the output for the URL and invoke the browser only at that time, that should fix the issue. We'll need to decide what to do with regards to the Launch URL in project debug properties though, as that will effectively become deprecated feature.

This should be addressed (or at least be better) when you switch to using output event to launch the browser rather than pinging the port that we do now.


Minor viewer.cpp bugs

Motivation and Context
This PR addresses a few minor bugs in viewer, where values that should have been mapped from constants were being mapped via magic numbers, or else not being mapped at all (such as the agent's dims if navmesh recalc is requested).

How Has This Been Tested
It's Viewer! It Always Works!

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have completed my CLA (see CONTRIBUTING)
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Agreed that settings should come from any loaded config. Not sure about the hard-coded slope fix here. I understand why we should change it, but maybe it should be a change in the NavMesh default settings instead.

Yeah, that would be the ideal situation, but not sure if folks are prepared for any changes that might entail.

Also note we have the python viewer application here. Should these be expected to behave the same way? Open to thoughts here.

I think they should, especially for these particular value-driven quantities (if we are recomputing the navmesh and have locally defined agent specs, we really should use those to build the navmesh, I think)

Got rid of a bunch of needless if checks building the string sensor key in drawEvent, and streamlined the draw/render process a bit.


FUnreal cannot detect UE path for UE5.3

Using UE5.3, FUnreal fails to start with the following error:

Root Cause
In order to detect UE path, FUnreal scan Visual Studio solution (.sln) in order to find a "Visualizers" file, expecting just 1 file of this kind (true for UE <= 5.2.X):

With UE5.3 the solution file generated by UBT has been changed a lot and now 2 file exists:

Solution
Possible solution can be to look for the first file with extension .natvis.
(or eventually look for the filename Unreal.nativs)
@AWildErin in pull request #21 propose to search for extension.

Tested with success on UE v5.3.1, v5.2.1, v5.0.3, v4.27.2

Published FUnreal v0.1.0 on marketplace
https://marketplace.visualstudio.com/items?itemName=fdefelici.vs-funreal


Steps for product profile optimizations is missing info

Description:
In APIM 3.1.0 after profile optimization, the DB is changes to mysql with following DB configurations.
Thus, we have to have copied the connector jar to lib folder and created dbs before executing server startup script. It is worthwhile to mention, that the user is required to copy mysql connector jar to lib folder, create databases and change this DB configs to match their environment (with correct host, username and password)
[database.apim_db]
type = "mysql"
hostname = "localhost"
name = "apimgt_db"
port = "3306"
username = "root"
password = "root"

[database.shared_db]
type = "mysql"
hostname = "localhost"
name = "shared_db"
port = "3306"
username = "root"
password = "root"

Affected Product Version:
APIM 3.1.0
Steps to reproduce:
Follow the steps in https://apim.docs.wso2.com/en/3.1.0/install-and-setup/deploying-wso2-api-manager/distributed-deployment/product-profiles/ doc.

@msm1992 , need more clarity in this regard.

@msm1992 , thanks for the clarification with regard to this issue. Please let us know whether this issue is applicable to the APIM 3.0.0 docs as well.
Fixed in -

https://github.com/wso2/docs-apim/pull/1423
3.1.0

https://github.com/wso2/docs-apim/pull/1424
master


Bridgy Micropub: 500s returned when creating posts

When using https://gitlab.com/jamietanna/micropub-go/ to submit a post to Bridgy via Micropub, I receive an HTTP 500 error:
<!doctype html>

<title>500 Internal Server Error</title>

Internal Server Error

The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.

This will be using a form-encoded body, where the access token will be in the body.
I can also reproduce this with an Authorization header:
curl https://brid.gy/micropub -i -d h=entry -d content='Hi' -H 'Authorization: Bearer ....'
HTTP/2 500
content-type: text/html; charset=utf-8
access-control-allow-headers: *
access-control-allow-methods: *
access-control-allow-origin: *
content-security-policy: script-src https: localhost:8080 my.dev.com:8080 'unsafe-inline'; frame-ancestors 'self';
strict-transport-security: max-age=16070400; preload
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-cloud-trace-context: ee901e38f6a846b2e8d47c34b5994fb8;o=1
date: Sun, 09 Oct 2022 07:38:41 GMT
server: Google Frontend
content-length: 265

<!doctype html>

<title>500 Internal Server Error</title>

Internal Server Error

The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.

This is using a new Twitter account, https://brid.gy/twitter/jamietanna_bot so could be due to some internal Twitter policies for new accounts?

Argh, sorry for the trouble @jamietanna, and thanks for the report, those requests tickled an untested code path. Fixed now!


replaced V3 nCoV-2019.bed, renamed original as nCoV-2019.bed.ORIGINAL

i meant to do this on a local fork.  there appears to be a similar request already in place, closing this one


Very long secret context data fails to load to disk

While testing client certificate authentication, I discovered that if the context secrets have long base64 encoded data, the entire data is not loaded to disk but only a part of it was visible in the mounted secrets.
Need to investigate what is the maximum length right now, and what is causing the limitation.

Have we ever been able to reproduce this?

Closing this for lack of response.


setLabels method feature request

From customer:
We use cloud function to label all of the instances created in our projects with the user id of the person who created it. This way we can notify the user when their instance comes under governance. Basically we create a sink from the gce instance log and filter it to look at insert events. This gets written to a bucket (or a pub/sub topic) that triggers a cloud function to run.
Here is what our instance tagging cloud function looks like.
exports.processFile = function(event, callback) {
// Requires

const path = require('path');

const os = require('os');

const fs = require('fs');

const readline = require('readline');

var storage = require('@google-cloud/storage')();

var google = require('googleapis');

var compute = google.compute('beta');

That obviously changed since the compute is now v1. But if I try either I get the following error.
2018-05-14 08:18:08.522 EDTnetapp-hcl-func<PHONE_NUMBER>50845 TypeError: google.compute is not a function at exports.processFile (/user_code/index.js:19:27) at
So I try this one that gives me almost everything I need.
const Compute = require('@google-cloud/compute');
const compute = new Compute();
Except there is no setLabels() API anywhere to be found in that Node.js package.

is there an update?


0C4 when running mantastic

Running:
gum version 0.13.0
mandb 2.12.0
GNU bash, version 5.2.21(1)-release (i370-ibm-openedition)
Results from:

mantastic -h

mantastic diff

mantastic -help works as before.
Now seeing an 0C4 with mantastic and mantastic diff

FYI @lbdyck .
@gngrossi , are you able to add a set -x to the 2nd line of mantastic.  This will tell us which command is triggering the OC4.

@IgorTodorovskiIBM
Screen capture from set -x

--
1st page of CEEDUMP without set -x
mantastic_CEEDUMP.txt
Screen capture without set -x

This is the version of bash that I'm working with and have no issues in case this helps - it's from the z/OS Open Tools install
bash --version
GNU bash, version 5.2.21(1)-release (i370-ibm-openedition)
Copyright (C) 2022 Free Software Foundation, Inc.

Thanks @gngrossi . The OC4 seems to be stemming from gum.
@dustin-ward FYI - Is _rto_s390x_zos a Go function?

what version of z/OS are you encountering this error on?
I have tested on 2.5 and 3.1 - on my 2.4 system I get a number of CEE.... type errors but haven't followed up as 2.4 won't be around much longer.

Running z/OS 2.5
10:08:17 RC=(0) [SYSA] bash-5.2$ bash --version
GNU bash, version 5.2.21(1)-release (i370-ibm-openedition)
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
10:08:25 RC=(0) [SYSA] bash-5.2$ mandb --version
mandb 2.12.0
10:08:36 RC=(0) [SYSA] bash-5.2$ gum --version
gum version 0.13.0

@dustin-ward FYI - Is _rto_s390x_zos a Go function?

 Something is crashing the Go runtime, but I am unable to reproduce the issue

Upgraded to the current package.
Commands worked first time:
mantastic -h
mantastic diff  (diff nothing appropriate)
mantastic        (received a prompt for search)
Second time:
mantastic -h  (worked)
mantastic diff

mantastic

Logged off/on
Same results as the Second time.

Last part the CEEDUMP.
errno information :
Thread Id .... 33D1200000000000 Errno ...... 137 Errnojr .... 05FC0119
CEE3846I CEEDUMP Processing completed.
CEEDUMP_gum.txt
--
References to Errno
https://www.ibm.com/docs/en/zos/2.5.0?topic=codes-return-errnos
137	0089	ENOTTY	The I/O control operator is inappropriate.
https://www.ibm.com/docs/en/zos/2.5.0?topic=errnojrs-zos-unix-reason-codes
05FC	JRICSFnotActive
ICSF must be running to open/read from /dev/random or /dev/urandom.
0119	JRNotSupportedForFileType
The requested service is not supported for this file type.
Action: Reissue the request, specifying a file of the correct type for the request.

how do i generate an environment dump?

Unless someone else has this issue I'm not going to pursue it as our 2.4 system is schedule to retire very very soon and the issue does not occur on 2.5 or 3.1

Running z/OS 2.5
10:08:17 RC=(0) [SYSA] bash-5.2$ bash --version GNU bash, version 5.2.21(1)-release (i370-ibm-openedition) Copyright (C) 2022 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software; you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.
10:08:25 RC=(0) [SYSA] bash-5.2$ mandb --version mandb 2.12.0
10:08:36 RC=(0) [SYSA] bash-5.2$ gum --version gum version 0.13.0

This error is still happening in 2.5 for @gngrossi no?
printenv will dump the environment contents to the terminal

Yes, I'm seeing the 0C4 on a 2.5 system. Soon I will be testing on 3.1.
These commands work:
mantastic -h
mantastic -help
mantastic diff -d
These commands generate an 0C4:
mantastic
mantastic ?
mantastic diff
mantastic git -a push

This is on a z/OS 2.4 system - no go or gum involved - just the zot version of man
/home/splbd>man diff
man: command exited with status 137: (cd /home/splbd/zopen/usr/local/share/man && /jenkins/zopen/usr/local/zopen/man/man-db-2.12.0/libexec/man-db/zsoelim) | (cd /home/splbd/zopen/usr/local/share/man && /jenkins/zopen/usr/local/zopen/man/man-db-2.12.0/libexec/man-db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE) | (cd /home/splbd/zopen/usr/local/share/man && preconv -e UTF-8) | (cd /home/splbd/zopen/usr/local/share/man && tbl) | (cd /home/splbd/zopen/usr/local/share/man && nroff -mandoc -rLL=138n -rLT=138n [-Tutf8)

manenv.txt

Here's the env output.
env_output.txt

After two updates to my environment, I ran through these use cases without an 0C4.

unset STEPLIB   (export STEPLIB=SYS1.SCCNCMP)
sourced a profile /hewitt/zopentools/oelcpp20/oelcpp.profile   for C/C++ for Open Enterprise Languages (pax file installed)

Use cases: with expected results
mantastic -h
mantastic -help
mantastic diff -d  (result was the gum pager for diff)
Use cases without abends
mantastic
Enter a command for a man page or a keyword to search for: diff
diff: nothing appropriate.
No manual entry for no
provide some content to display
mantastic diff
diff: nothing appropriate.
No manual entry for no
provide some content to display
Seeing a set of man pages for CoZ ? After a selection, the result was the gum pager for it.
mantastic ?
Select Man Page to View

catsearch
cozclient
cozcontrol
cozsftp
fromdsn
fromfile
safauth
todsn
tofile
zsym

mantastic git -a push
push: nothing appropriate.
No manual entry for no
provide some content to display


Extra step on Ambari Configuration

Step 6 of https://docs.microsoft.com/en-us/azure/hdinsight/kafka/apache-kafka-ssl-encryption-authentication#update-kafka-configuration-to-use-tls-and-restart-brokers should not exists and in fact step 7 should be the action.
At least for HDI 4.0, if you anything on the server.properties, it will get undone on broker restart.
Note: If you do the kafka env template for HDI 4.0, the server.properties will end up with duplicated entries.

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

ID: c117dccb-22e3-b6b3-ae19-9e2b6ec477a8
Version Independent ID: 4c0a71c1-e367-e103-2839-beb08348b2d6
Content: Apache Kafka TLS encryption & authentication  - Azure HDInsight
Content Source: articles/hdinsight/kafka/apache-kafka-ssl-encryption-authentication.md
Service: hdinsight
GitHub Login: @hrasheed-msft
Microsoft Alias: hrasheed

Please assign this issue to @dagiro

@Fabiest Step6 talks about "Configuration" and step7 talks about "verify the configuration using Ambari UI".
There is no extra step on Ambari configuration and step6 and step7 are different and which don't create duplicate entries.
Hope this helps.

But step 6 mentions to "Add new configuration properties to the server.properties file" and that should not be done, because when you restart the brokers, your changes go away.
The properties should be set on Ambari UI, at least for HDI 4.0.

@dagiro Could you please look into this issue?

@Fabiest, Thank you again for bringing this to our attention. I have updated the article. The update should be visible shortly.

We will now close this issue.
#please-close


ENH: add synchronization method nearest_advocate to SciPy.signal.

Post-hoc time synchronization of event-based time-series data.
What does this implement/fix?
This is an alternativ approach to the cross-correlation and is better suited for event-based time-series data like arrays of timestamps.
Additional information
The first paper addressing this approach is here (in german) and a second larger paper is in preparation which will be submitted in February.

Hi @tupui,
Thank you for your fast reply. Yes we will go for the official steps as suggested.

Hi @ChristophSchranz, please proceed first with sending an email to the mailing list. At this stage making CI pass is not necessary as if this gets approved, most of the implementation will get commented/modified. Also if you really want to do this otherwise, please test locally the changes before to save our CI credits (almost everything can be tested with our python dev.py).


Query HELP field for a metric

For technical (but also a bit of security) reasons we have engineers who can't access the Prometheus /metrics endpoint of exporters to look at the HELP description of metrics. I understand that there is an API endpoint that allows for querying for HELP description, however there is no GUI option for it.
Feature request: Be able to somehow query for a metric HELP description in the GUI.

Do we have any plans on this? Like a design doc, or anything related.

There's no real need for a design doc for something like this, it's purely a UI feature.

Can you please try Prometheus 2.26?
The help is present in the new experimental editor:

Hello from the bug scrub.
We agree with @roidelapluie that this has been implemented in 2.26. Closing, but please follow up if that's not what you wanted.


page.renderBuffer can't work

Which version of PhantomJS are you using? Tip: run phantomjs --version.
phantomjs  version:2.1.1

What steps will reproduce the problem?
when I use this demo :http://phantomjs.org/api/webpage/method/render-buffer.html
I can't get anything when I open browser with localhost:8001,It's always waiting response.
and I change the response data to text,and content-type:"text/html",it will return the text.
and then I change to using page.render("img.png"),It alos can return the scrrencapture as the image "img.png "

Which operating system are you using?
win7 64bit

Did you use binary PhantomJS or did you compile it from source?
no I download form the official site.

Please provide any additional information below.
myCodes:
`var server = require('webserver').create();
var listening = server.listen(8001, function(request, response) {
var url = "https://..com/login/";
var  format = 'png', quality = -1;
console.log("requestURL:",request.url)
var page = require('webpage').create();
page.viewportSize = {
width: 800,
height: 600
};
page.open(url, function start(status) {
if (status !== 'success') {
console.log('FAIL to load the address');
} else {
console.log("open url:",url ,"status:",status);
// page.render('loginpage.png');
var buffer = page.renderBuffer(format, quality);
response.statusCode = 200;
response.headers = {
"Cache": "no-cache",
//"Content-Type":"text/html"
"Content-Type": "image/" + format
};
page.close();
// Pass the Buffer to 'write' to send the Uint8ClampedArray to the client
response.write(buffer);
response.close();
}
});
});`

renderBuffer available in development build only.

how can i download development version @Vitallium

I offer development builds for Windows only. If you need development version for Linux or macOS you have to build it from sources.

thanks,can u publish on http://phantomjs.org/download.html this page. or give me an link to download. @Vitallium

@Vitallium I need window development version

I met exactly the same problem. My build is 2.1.1, Win10, 64bit, WebStorm2.1. I am trying to scrape a image url directly. The thread of execution seems broken after running renderBuffer. I will give the development version a trial.

@cfa532 see my github [https://github.com/tinhour/screencapture-sendmail/blob/master/index.js] project ,I using a webcamera to do this .
it's can used as renderBuffer.

Thanx, tinhour. I have to run it under Phantomjs. webcam package won't do. I used child_process to start a http.get to download the image. It is an ugly solution but it works. I will wait for the renderBuffer to be released.


feat: IAM反向查询项目资源支持按名称查询 --story=119726965

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.cheynechen seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Request for audio vizualization

Is there any possibility to add this function? Draw some bars showing left and right volumes?
Thanks.

I think you could easily implement this yourself, since you have access to the WebAudio nodes of JSMPEG through JSMpeg.AudioOutput.WebAudio. See "https://github.com/phoboslab/jsmpeg/blob/master/src/webaudio.js". By using the gain node, you could add audio visualization like this: https://developer.mozilla.org/en-US/docs/Web/API/Web_Audio_API/Visualizations_with_Web_Audio_API
I don't know if I'm right, but I think it would be a bit out of scope to implement this as a part of JSMPEG.


A complete refactor to Deep* types

Refactor DeepReadonly, DeepWritable, DeepPartial
Implement DeepNonNullably
Refactor and add related tests

This refactor should solve #14 #40
And since all Deep types are very similar now, it provides a foundation for #12

VS Code yields no errors, however, tsc fails.

It is related to prettier... If I do not format the code, tsc can pass.

TypeScript > 3.5 is OK, but 3.2 fails.

I suggest we follow TypeScript > 3.5, in which arrays do not need specific judgment, and can be treated just like {}

By treating arrays just like {}, issues with tuples (#40) are also addressed like charm.

I realized that the easiest way is to upgrade TypeScript version in devDeps.

This is a really enormous help for the project! Thanks for this PR!
Bumping TS version is for sure not perfect but on the other hand, we can release this as version<EMAIL_ADDRESS>and let folks know that they can still use 2.x.x if they use older TS version.
I will need a while to review this PR. Hopefully today/tmrw I will get right back to you.

Thanks! I am gonna merge this 🎉
I created a new branch next and that is the branch for explicit support for TS 3.5. I will also publish it as<EMAIL_ADDRESS>so it's already usable for early adopters. My plan would be to wait a little bit before releasing it to master to give the community time to migrate to TS 3.5. On next branch we can also remove deprecated types that became part of TS standard lib (omit)

Part of next branch. Released as<EMAIL_ADDRESS>


Add rule(s) to check for caching

[ ] Check if static resources (images, js, css, fonts) are served with far-future expires headers (allow this to be configurable).
[ ] Check if resources cached for a long time use any form of cache busting .
[ ] Check if the cache busting is done using query strings (?v231) instead of something such as .231.extension.
[ ] Cache-Control: immutable ?
[ ] Other?

Some documentation:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9
https://jakearchibald.com/2016/caching-best-practices/
https://youtu.be/vAgKZoGIvqs?t=12m20s

Proposal
The ideal configuration is:

Static assets (anything but HTML): max-age + cache busting + immutable
HTML content: no-cache or a relatively small max-age (a few minutes), although no-cache preferred
Cache busting is done via filename and not query parameter
No explicit cache-control is an error as the behavior is left to the browser implementation and it can change from one to another

On top of that:

wrong cache-control configurations. E.g.: no-cache with max-age
invalid directives. E.g.: cache-control: max-ages=11234
alert about the use of extension directives not supported by any browser (stale-while-revalidate and stale-if-error)?
must-revalidate doesn't seem to be recommended anywhere, should we

User configurations

max-age value: By default one year
Preferred type of cache busting (parameter/file)
Cache busting regular expression(s). By default we should find filename.hash.ext and filename-hash.ext (those are the 2 most popular I've found).
What do we do with explicit no caching? Maybe have an option to not flag it?

Some data from HTTP Archive
Some data from the latest HTTP Archive (2017/10/15)
SELECT cache_header, round(100*ratio) as percent, resource_count FROM (
SELECT count(*) as resource_count, RATIO_TO_REPORT(resource_count) OVER() ratio,
       CASE WHEN resp_cache_control = "" THEN "no cache header"
            WHEN resp_cache_control contains "no-cache" THEN "no-cache"
            WHEN resp_cache_control contains "no-store" THEN "no-store"
            WHEN resp_cache_control contains "must-revalidate" THEN "must-revalidate"
            WHEN resp_cache_control contains "immutable" THEN "immutable"
            WHEN resp_cache_control contains "max-age=0" THEN "max age 0"
            WHEN resp_cache_control contains "no-cache" AND resp_cache_control contains "no-store" AND resp_cache_control contains "must-revalidate" THEN "no caching"
            ELSE "other"
       END as cache_header
FROM httparchive:runs.2017_10_15_requests
WHERE (resp_etag = "" AND resp_last_modified = "")
GROUP BY cache_header
)
ORDER BY resource_count desc

Original query from https://discuss.httparchive.org/t/how-many-resources-return-last-modified-and-or-etag-values/407

cache_header
percent
resource_count

no-cache
48.0
6656302

no cache header
32.0
4394414

other
16.0
2259399

immutable
1.0
145738

no-store
1.0
126617

must-revalidate
1.0
126371

max age 0
1.0
124476

Interestingly, the method to avoid caching proposed in https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control#Preventing_caching doesn't seem to be used anywhere.
I'll keep updating this message when I dig more results.

Adding @jakearchibald, @mikewest, @aliams @torgo see if they have any comments about the cache-control rule or if they think someone else should be involved.

Another link to review: https://www.smashingmagazine.com/2017/11/understanding-vary-header/

Interestingly, the method to avoid caching proposed in https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control#Preventing_caching doesn't seem to be used anywhere.

FWIW, I edited the code snippet on MDN some time ago - to prevent caching it now suggests: Cache-Control: no-store. When @molant linked to it, it was proposing Cache-Control: no-cache, no-store, must-revalidate which is overkill. https://www.mnot.net/blog/2017/03/16/browser-caching confirms that browsers correctly respond to each directive, e.g.:

Cache-Control: no-store in responses bypasses all tested browser caches correctly, and Cache-Control: no-cache in responses will correctly get stored, but checked on each request.

so there's really no scenario where Cache-Control: no-cache, no-store, must-revalidate would be considered proper usage.


Error: 'colors.danger.400' does not exist in theme config when configuring Tailus UI with Vite

Describe the bug
Hello, I'm a front-end beginner. I followed this tutorial to configure Tailus UI: https://ui.tailus.io/react/guides/vite/
However, I encountered the following error. Did I miss something?
Thank you for your assistance!
[plugin:vite:css] [postcss] D:/DEV/podcast/my-project/src/index.css:1:1: 'colors.danger.400' does not exist in your theme config. 'colors' has the following keys: 'inherit', 'current', 'transparent', 'black', 'white', 'slate', 'gray', 'zinc', 'neutral', 'stone', 'red', 'orange', 'amber', 'yellow', 'lime', 'green', 'emerald', 'teal', 'cyan', 'sky', 'blue', 'indigo', 'violet', 'purple', 'fuchsia', 'pink', 'rose'
D:/DEV/podcast/my-project/src/index.css:1:0
1  |  @tailwind base;
   |  ^
2  |  @tailwind components;
3  |  @tailwind utilities;

To Reproduce
Steps to reproduce the behavior:

Create a new Vite project

npm create vite@latest my-project -- --template react
cd my-project

Install Tailwind CSS

npm install -D tailwindcss postcss autoprefixer
npx tailwindcss init -p

Install Tailus UI Themer

npm install @tailus/themer tailwind-merge lucide-react

Update Tailwind CSS configuration

/** @type {import('tailwindcss').Config} */
module.exports = {
  content: [
    './index.html',
    './src/**/*.{js,ts,jsx,tsx}',
    './node_modules/@tailus/themer/dist/components/**/*.{js,ts}',
  ],
  theme: {
    extend: {},
  },
  plugins: [],
}

Add css directives

// index.css

@tailwind base;
@tailwind components;
@tailwind utilities;

Add cloneElement utility
npm run dev

Expected behavior
Without any error
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Windows
Browser chrome
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Hello @eMUQI sorry for the late response, did you manage to solve your error ?

No, I've given up.

I am having the same problem but I found a workaround for the moment. Is it a real bug or a problem of installation or configuration ?


Feature Request: Font Sizing.

Hi.
I love this add-on - my only issue is, i'm using it as the last button on my menu line, and the size of the fonts causes the tile to be truncated on  my tablets. (example below)
I'd love an easy way to specify the date and time font sizes (separately if possible) in the yaml.

Thanks

If you like to change the font size please use card-mod.
https://github.com/thomasloven/lovelace-card-mod
If you need some help, you can respond to this issue.

is it possible to use card-mod to change the text size of each line independently?
Thanks

My configuration:
GRID

first:

type: custom:digital-clock
dateFormat: ' '
card_mod:
style: |
.type-custom-digital-clock {
font-size: 40px !important;
font-weight: bold !important;
color: orange;
}

next...

type: custom:digital-clock
timeFormat: ' '
dateFormat:
weekday: long
day: 2-digit
month: short
card_mod:
style: |
.type-custom-digital-clock {
font-size: 15px !important;
font-weight: normal !important;
color: orange;
}

Just in case anyone else finds this like I did to figure out how to change font size, you can change the each line without having to have two cards:
type: custom:digital-clock
dateFormat:
  weekday: long
  day: 2-digit
  month: short
  year: numeric
timeFormat:
  hour: 2-digit
  minute: 2-digit
  second: 2-digit
card_mod:
  style: |
    .first-line {
      font-size: 56px !important;}
    .second-line {
      font-size: 8px !important;}

card_mod:
style: |
.first-line {
font-size: 56px !important;}
.second-line {
font-size: 8px !important;}

Works for me. Many thanks


Restrict form email characters allowed

From @harobed on June 25, 2015 12:46
Restrict form email characters allowed, see https://tools.ietf.org/html/rfc5322#section-3.2.3
Copied from original issue: modoboa/modoboa-admin#28

@harobed This issue should be fixed since 1.4.0.


Light HC: Editor gutter icons are low contrast

Testing #143425

Install the hex editor extension
See an invisible icon in the editor gutter:

Here's what it looks like in the normal Light+ theme:

I installed the extension and opened a file with it but don't see that icon rendered. Anything obvious I'm missing?

I'm also guessing this is related to the harcoded values in #143743

Oh this is actually from a different extension, "hexdump for vscode"

Looking at this again. The hexdump extension only contributes a light and dark version of that icon:
https://github.com/stef-levesque/vscode-hexdump/blob/2e115c32de41a9f6bbc04f29929ffb495e87eb38/package.json#L52-L58
I'm not sure why our dark HC theme is defaulting to use the asset intended for dark themes. Maybe it's just luck that it happened to default to that one, hence why we're seeing the invisible dark theme icon in the light HC theme. However the colors are hardcoded in the SVG anyway so this wouldn't be a fix on our end.


Create Minimum Dual Area.cpp

Description
Please include a summary of the change and which issue is fixed. List any dependencies that are required for this change.
Fixes #898
Replace issue_no with the issue number which is fixed in this PR
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Documentation Update

Checklist:

[ ] My code follows the style guidelines(Clean Code) of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have created a helpful and easy to understand README.md
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works

@vanishasamriddhi add test case

@Amit366 I should add the test case in comments (in the code)?

@vanishasamriddhi add it below the code in the form of comments

@Amit366 Done, My apologies for the delay.


Update NHM v1.1 byHWobs model output to extend time period (1979-01-01 to 2021-12-31)

Current NHM model output covers 1979-01-01 to 2019-12-31. The gridmet forcing product for the NHM has been extended through 2021-12-31. The on-prem NHM byHWobs model output should be updated to include the additional time steps.

The on-prem NHM v1.1 byHWobs model output has been extended to cover 1979-01-01 to 2021-12-31.


Add Lightning Studio Launch Button

Closes #850
This PR adds a launch button for Lightning Studios a quiet powerful development platform for Deep Learning applications with GPU support.
As stated in the issue, we would like to make this option available to more easily run tutorials for our Deep Learning Uncertainty library, where some require GPUs,  and I would imagine that it could be a quiet useful tool for other documentations.

@agoose77 sorry to ping you, but wondering if might have time to review or give your opinion about the idea?

@chrisjsewell @choldgraf sorry to ping you as well, but was hoping to get a response :)

@jangenoe sorry to ping you you as well, but since you have been active on this PR before, I thought I would try :)

@jangenoe @chrisjsewell @choldgraf ping

@nilsleh thanks for your patience here! Let me just run this past the other maintainers to make sure there aren't any policies about which products we support in our config!

@agoose77 sorry for the ping abuse, but wondering if there has been already a decision on this?

@agoose77

To get this over the line, we need to update the snapshot tests.

Is there something we (@adamjstewart and I) can do to help move this forward?


Go references

Motivation for this change
Things done

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

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

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

buildGoModule?

If we're doing this we may as well do sbin and lib.

Also:
https://github.com/NixOS/nixpkgs/blob/6eae50cca8014a2eb773d73bbe10552c60841217/pkgs/applications/virtualization/singularity/default.nix#L71

If we're doing this we may as well do sbin and lib.

I checked sbin but it is already moved in fixupPhase to bin, so I left it.

Also:
https://github.com/NixOS/nixpkgs/blob/6eae50cca8014a2eb773d73bbe10552c60841217/pkgs/applications/virtualization/singularity/default.nix#L71

done

buildGoModule? Nothing uses libexec.

Eventually docker and co could be migrated to it at which point it will be used.

There is also the deepin desktop (~ 3 packages) that could make use of it but it is marked as broken atm.

There is also the deepin desktop (~ 3 packages) that could make use of it but it is marked as broken atm.

I'd include them anyway.

done.

All good?


Monorepo proposal

Hi,
I reviewed some code and eventually I tried making a PR fixing a comment, here are my thoughts.
I think you're going to want to think about doing a monorepo (monolithic repo) where the documentation and the package live in the same repo; or many people are going to have workflow problems.
I've had to juggle two repo's with npm link, it's not fun from a workflow standpoint to change something in one project, to then have to save another project to see the result. If it's not fun for me I can see it not being fun for someone else.
What you want is to change the CSS and to see the documentation change with it. Your documentation = your unit test whether everything is working.
The branching on appuniversum.github.io feels weird, with master referring to the deploy, then build being the branch to work on (I guess this is Github pages related).
What I was fixing in the docs (the editor vs. content issue) was actually an issue from another repo.
What we are going to want there is something that people know like git-flow.
We're also going to need a way to name branches to know which issue to refer to.
So, here's my proposal:

Merge the appuniversum/appuniversum and appuniversum/appuniversium.github.io to one repository
Work with git-flow: master is the reference version, development is what in development, use branches like enhancement/xyz or feature/xyz to have some organisation
Keep working with 11ty for documentation purposes
Deploy the site: not sure if we can use Github pages with a different repo structure?

What do you think?

I agree, in practice it indeed seems a bit overkill to have this as seperate branches.
I merged the documentation to this repo.

builds automatically from the master branch to gh-pages
new url: https://appuniversum.github.io/appuniversum/

If all is good I'll remove the appuniversum.github.io branch.


Despawn failure should not panic

Reported on discord. If the server replicates an entity despawn but the entity was manually despawned on the client, replicon currently panics. It should not need to panic.

thread 'main' panicked at /home/mirsella/.local/share/cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_replicon-0.28.4/src/client.rs:429:45:
Entity Entity { index: 175, generation: 1 } does not exist
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Encountered a panic in system `bevy_replicon::client::ClientPlugin::receive_replication`!
Encountered a panic in system `bevy_app::main_schedule::Main::run_main`!

this correspond to
        // SAFETY: access is unique and used to obtain `EntityMut`, which is just a wrapper over `UnsafeEntityCell`.
        let mut client_entity: EntityMut =
            unsafe { world_cell.world_mut().entity_mut(client_entity).into() };

its entity_mut which panic as stated in its doc.
is now here:
https://github.com/projectharmonia/bevy_replicon/blob/0efa80723af57cac220cbf9ddbe30c08251b7220/src/core/replication/deferred_entity.rs#L23

If the server replicates an entity despawn but the entity was manually despawned on the client, replicon currently panics.

Hm... That's actually not the case, we very explicitly handle it:
https://github.com/projectharmonia/bevy_replicon/blob/0efa80723af57cac220cbf9ddbe30c08251b7220/src/client.rs#L394-L405

its entity_mut which panic as stated in its doc.

It looks like this occurs during removals and changes. If the entity is already despawned on the client but the server sends replication for it, we panic. It is a user mistake; they should not despawn a replicated entity from the server. Should we replace this with a warning instead?

Should we replace this with a warning instead?

Yeah this seems better. Less aggressive

Maybe it should be error instead of warning? :thinking:

Maybe it should be error instead of warning? 🤔

I personally like to do error when there is a catastrophic problem of some kind (usually a library bug), and warn if the user caused some problem that is bad but not catastrophic.

I looked into it, and to avoid a panic, I will need to skip the deserialization of the invalid entity. But I don't know size of components.
I can serialize the components size instead of their count, but that would make the packing worse. I think I'll keep it as a panic for now to prioritize the efficiency.


Implement bootstrapping

[ ] How to deal with the matching table and postestimation commands? just omitting the bootstrapping therein?
[ ] The ereturns after bootstrapping have to be continued

[ ] How to deal with normalize and the fact that bootstrapping p-values would be off

Add all possible options to specify in the main option of the nopo-command


Adding missing Thing Group ARN to FakeThingGroup

The thingGroupArn should be returned for Thing Groups, according to boto3 docs.

Coverage remained the same at 94.244% when pulling 8582766d2636e659dc3fdf93b8d75a5f4d7aa3bc on TierMobility:master into f1f7ddb69d79c1b83ccb45f4e37f847f6199fde8 on spulec:master.

Superceded by #3634 - will close this one

Superceded by #3634 - will close this one


Pull diagnostics not cleared when file deleted

With workspace diagnostic support enabled, diagnostics for a file are not cleared when the file is deleted (either through VSCode or externally). The diagnostics remain in the problems tab.
This issue becomes more apparent when using commands like git stash

Got fixed in HEAD.

I can confirm this is fixed when the file is deleted within VSCode by the user, but it still seems to be a problem when the file is deleted externally (e.g. through File Explorer or when git deletes the file using git stash). The problems still remain then

When the file is deleted externally and open in an editor the editor usually doesn't close. This is why I don't clear the problem. In case you are using workspace diagnostics they aren't cleared automatically.
In which case are you seeing this: workspace diagnostics or document diagnostics?

Using workspace diagnostics. Document diagnostics and push method both handle this fine I think

For workspace diagnostics we actually recommend that the server is doing this. VS Code doesn't delete problems on file deletion either so we didn't want to add this to the LSP libs.


Indent subheadings in exported TOC?

In the TOC of the editor, the headings, the subheadings are properly indented:

The styles of baz1 and bar1 clearly suggests that baz1 is a subheading of bar1.
However, if I generate a TOC using the {{#tocToHtml files.0.content.toc 3}} tag, baz1 and bar1 look the same in the TOC:

Can this be fixed?

Export templates can be customized. Have you checked that?

I know I can customise export templates, but I can't customise what {{#tocToHtml files.0.content.toc 3}} turns into, right?


Implement searching projects

This PR:

Move search input from navbar component to tasks list
Implements searching projects by task's details field.

Coverage remained the same at 93.796% when pulling c7f3ac8e7b68eab9cf1edd354f9fc224723cdc78 on implement-searching-projects into 31d41700af2eb4f0610fe1975209112f6cfe22ab on orchestra-reactify-frontend.


Suggest setting meson buildtype for a debug build

This suggestion will be correct on all platforms meson supports.

Thank you!


[GSB] Compute the dependent type for ProtocolRequirement sources.

The dependent type that is the subject of a ProtocolRequirement
source is independently computable based on the root potential
archetype of the source and the potential archetype to which the
requirement applies, i.e., it's just the dependent member type that
gets from the former to the later. Compute this directly, rather than
relying on the passed-down dependent type.
This is possible now because we no longer capriciously rebase
requirements onto the representatives of equivalence classes, nor
destroy any other structural information in the formation of potential
archetypes.

@swift-ci please smoke test and merge


Nextjs 15 support

When using next.js 15 getPathname crashes the app with the following error:
"Error: Cannot find module 'next/dist/client/components/static-generation-async-storage.external'"

Hello, thanks for the issue, looking into it!

Also maybe tests need to be updated:
https://github.com/vordgi/nimpl-getters#stability

All getters are covered with tests. Tests are run on every release and every 6 hours on the latest Canary version of Next.js.
In this way, you can be sure not only of the stability of the code, but also that if there is a breaking change in Next.js, this will immediately become known. Even before the release of a stable version of Next.js.

[ ] Update helpers
[ ] Remove get-search-params
[ ] Update tests
[ ] Update docs

Version 2.0.0-canary.0 has been released. The stable version will be published tomorrow


fix(ingestion): issue a warning if the column list is empty

Checklist

[x] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[x] Docs related to the changes have been added/updated (if applicable)

Will be nice if the warning is displayed. Otherwise beginners might not know what's the problem until they try --debug option of CLI.


DAVIS datafiles uncomplete?

"datafiles.tar" in provided "Google Drive" download link consists  only triangulation data.
There are no  "JPEGImages/1080p" and "Annotation//1080p" folders that "python ./scripts/preprocess/davis/generate_frame_midas.py" refers to:
---
data_list_root = "./datafiles/DAVIS/JPEGImages/1080p"
camera_path = "./datafiles/DAVIS/triangulation"
mask_path = './datafiles/DAVIS/Annotations/1080p'
---

you can download the DAVIS dataset from their official website: https://data.vision.ee.ethz.ch/csergi/share/davis/DAVIS-2017-trainval-Full-Resolution.zip


hotfix/sdk upgrade 1.0.3

symbol-sdk version is upgraded to v1.0.3
package version is updated to 1.4.1

Look good! Can you update the changelog as well?

@yilmazbahadir looks good from my side. Could you just add changelog into CHANGELOG.md?

@yilmazbahadir looks good from my side. Could you just add changelog into CHANGELOG.md?

Thanks, updated.


GEOMESA-664,666 Follow Tools Naming Convention

Replaced "Remote" with "Distributed" in tools
Renamed queryStats and ingestRaster to follow all lower case naming convention

1d19606da39a9642fce4cac9ea11349ac03a584c


[Java] Fix generation of models with underscores

I finally found the time to get to this 😅
Fixes #3824

Sorry for the delay, swamped 😓

@andreaTP this change seems to have revealed an issue with Go, would you mind taking a look at it while you're on this please?
https://github.com/microsoft/kiota/actions/runs/7266365004/job/19798236796?pr=3939

In Go 😲 , I'm finishing something right now, I'll have a look tomorrow 👍

I took a quick look at the failure and I can reproduce it locally, the bug is triggered by the added pattern in the integration tests, the constructor is generating the following code:
func NewCreateImageRequest()(*CreateImageRequest) {
    m := &CreateImageRequest{
    }
    m.SetAdditionalData(make(map[string]any))
    modelValue := "dall-e-2"
    m.SetModel(&modelValue)
    return m
}

but m.SetModel accepts only CreateImageRequest_CreateImageRequest_modelable and not strings, which seems to be a type wrapper over string:
type CreateImageRequest_CreateImageRequest_modelable interface {
    i878a80d2330e89d26896388a3f487eef27b0a0e6c010c493bf80be1452208f91.Parsable
    GetString()(*string)
    SetString(value *string)()
}

@baywet I have 0 clue about the expected result, I would very much appreciate another couple of eyes or, at least, some guidance. Alternatively, we can open a separate issue and ignore the test.
wdyt?

Thanks for looking into this.
Most likely because of https://github.com/microsoft/kiota/pull/3937
Out of curiosity, if you merge both PRs locally, do you still get the error?

rebased on the latest main which contains the linked fix, but the problem remains ...

Thanks for taking over this one @baywet !

no worries, thanks for the contribution as always!


In quick start documentation, "Access Prometheus" command is not working

What happened?
I tried to run the command in the quick-start#access-prometheus section of the doc, but it didn't work.
How to reproduce it (as minimally and precisely as possible):
run kubectl --namespace monitoring port-forward svc/alertmanager-k8s 9090

Prometheus Operator version:

0.46.0
Anything else we need to know?:
The command should be kubectl --namespace monitoring port-forward svc/prometheus-k8s 9090

Oops. You're right, can you create a PR with a fix? The file is located in https://github.com/prometheus-operator/website/blob/main/content/docs/prologue/quick-start.md


How to get wechaty instance in on functions in typescript, Global.this?

Hi, with javascript version, we can get wechaty instance(bot) like this way.

@see https://github.com/wechaty/wechaty-getting-started/blob/b0e00a28993dc83824544d0f28058996186907b0/examples/advanced/busy-bot.js#L79
but how can I get the wechaty instance in the on('message','../on-message.ts') functions?
here is my way to walk around.

========中文========
请教大家一个问题， wechaty，typescript中on-message 无法使用this获取wechaty实例，提示Global.this 但是又不会怎么搞？
需求图片：

on-message函数定义：

not work like this

搞定了！
// @see http://www.semlinker.com/ts-this-param-type/
async function onMessage(this: Wechaty, msg: Message) {
  // const wechaty: Wechaty = Wechaty.instance() // wrong!
  const wechaty: Wechaty = this

@guoxiangke Hi, I have noticed that you are using the Hot Import function from the Wechaty.
Please notice that in the next version of Wechaty, this function has been removed to our Plugin system, instead of binding it with the Wechaty itself.
Please go to https://github.com/wechaty/wechaty-plugin-contrib#9-eventhothandler to learn the EventHotHandler plugin for Wechaty v0.40+.


Add a project name Javascript Image-carousel

I created a project for sliding images. In this project, we can easily slide images by clicking a button.

Thanks for the PR. The image slider looks dope. It has been merged.
I will be glad if you can leave a start on this repository.


Custom error reporters

@pudgereyem on #14:

Custom jest reporters prevent --verbose to output individual tests
I like to run jest --verbose so that I can see the results of the individual tests when working. However, the custom reporters that was added, see code here prevents that behaviour. In order to see the individual tests (as shown in the above section) I had to comment out those. See below.
// jest.config.js

module.exports = {
  preset: 'ts-jest',
  setupFilesAfterEnv: [
    "<rootDir>/tests/setupTests.js"
  ],
  testEnvironment: 'node',
  testPathIgnorePatterns: [
    "/node_modules/",
    "/api/"
  ],
  // reporters: [
  //   '<rootDir>/tests/reporter.js',
  //   '<rootDir>/tests/summary-reporter.js',
  // ],
};

What are your thoughts on this? I personally appreciate seeing what different tests are running.

Ahh, I thought something had changed with the tests but couldn't put a finger on it :sweat_smile:
Ok, so the customer error reporter hides console output for passing tests.
This is because e.g. we have a lot of tests that test failing validation, and you've seen how much console output that generates.  (So you can imagine how I didn't notice the missing test names after getting rid of thousands other lines :sweat_smile:)
Clearly an unintended consequence is that it's hiding the console output that lists the name of the test itself.
I think the solution is actually to drop the custom reporter and look into a way to disable console output temporarily just for those specific tests.  Will report back.

@gadicc, yes I could see what you tried to do there. I agree that it's a good idea to drop the custom reporter for now and then solve that problem you presented without unexpected side effects 👍

Great, it's done! :tada:


Can't build 0.1.64 with cuBLAS support. Can build 0.1.63 in the same environment.

I am using Oobabooga on Windows 11, all the latest updates.
python-llama-cpp 0.1.64 works fine on CPU. 0.1.63 builds just fine with cuBLAS support too. However, building 0.1.64 with cuBLAS fails with a long log.
I also need to add -DCMAKE_CUDA_ARCHITECTURES=native to the CMAKE_ARGS or it does not build, complaining that it is missing. 0.1.63 did not require that too.
Here is normal log.
Here is verbose log

With set "CUDAFLAGS=-arch=all -lcublas" it builds with no problem.

I'm having a problem with this too on linux, was working in the past but now for some reason i'm getting swamped with these errors:
CMake Error in vendor/llama.cpp/CMakeLists.txt:
CUDA_ARCHITECTURES is set to "native", but no GPU was detected.
this is during a docker build, so there is no GPU.. but it worked before

But otherwise llama.cpp builds correctly as a standalone program with the same flags?

Closing. Please reopen if the problem is reproducible with the latest llama-cpp-python which includes an updated llama.cpp


Bug (Platform-Specific:OSX): UIThread instantiation fails

While performing cross-platform testing prior to PR #17, it was discovered that the PSAvalonia-based UIThread instantiation fails with the following error:
MethodInvocationException: Exception calling ".ctor" with "0" argument(s):
    "Can not have multiple active ClassicDesktopStyleApplicationLifetime
    instances and the previously created one was not disposed"

Patch #17 temporarily disables Mac OS, while a new patch is being worked on. A resolution to this issue will also contribute to #14

The native APIs used by Avalonia can be found here:

https://github.com/AvaloniaUI/Avalonia/blob/master/src/Avalonia.Native/avn.idl#L1
the namespace used is on the first line of the file (highlighted)

No longer an issue after #20


MINOR: fix html generation syntax errors

*More detailed description of your change,
The html document generation has some errors in it, specifically related to protocols. The two issues identified and resolved are:

Missing </tbody> closing tags added
Invalid usage of a <p> tag as a wrapper element for <table> elements. Changed the <p> tag to be a <div>.

*Summary of testing strategy (including rationale)
Tested by running ./gradlew siteDocsTar and observing that the output was properly formed.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

cc @ijuma @guozhangwang


tests: add test_backup_volume_list to make sure that listing volume does not fail even there are bad names in backups folder.

test_backup_volume_list() make sure that instead of erroring the backup list should ignore the badly named files in backups folder.
longhorn/longhorn#1410

Sorry. It should be Change Request rather than Approved for the review result.

Hi Shua! I did not break the NFS server operation inside the test test_listing_backup_volume:
    # invalidate backup volume 1 by renaming volume.cfg to volume.cfg.tmp
    cmd = ["mkdir", "-p", "/mnt/nfs"]
    subprocess.check_output(cmd)
    cmd = ["mount", "-t", "nfs4", nfs_url, "/mnt/nfs"]
    subprocess.check_output(cmd)
    cmd = ["find", "/mnt/nfs", "-type", "d", "-name", volume1_name]
    volume1_backup_volume_path = \
        subprocess.check_output(cmd).strip().decode('utf-8')

    cmd = ["find", volume1_backup_volume_path, "-name", "volume.cfg"]
    volume1_backup_volume_cfg_path = \
        subprocess.check_output(cmd).strip().decode('utf-8')
    cmd = ["mv", volume1_backup_volume_cfg_path,
           volume1_backup_volume_cfg_path + ".tmp"]
    subprocess.check_output(cmd)
    subprocess.check_output(["sync"])

into a common function because of 2 reasons:

The test test_backup_volume_list use S3 instead of NFS
The above code trying to rename a file in NFS, not create a new file. There is only the test test_listing_backup_volume want this feature. Therefore, I did not create a new common function in common.py for this code.

Please let me know if I am wrong.

All right. If NFS is not used in the test and you won't implement the related NFS functions, it's better to remove nfs_create_file_in_backupstore and nfs_delete_file_in_backupstore.
In general, LGTM.

Oops! Cannot rebase to longhorn-test master. The repo has been restructured and some helper functions no longer exists. I need to re-write this E2E test which will take some time.

Close this PR because created a new PR for this issue at https://github.com/longhorn/longhorn-tests/pull/366


[WIP] Brusselator Benchmarks

@ChrisRackauckas appleaccelerate_isavailable at /cache/julia-buildkite-plugin/depots/5b300254-1738-4989-ae0a-f4d2d937f953/packages/LinearSolve/1B5tc/src/appleaccelerate.jl:18 [inlined] this shouldn't segfault on Non Apple hardware right?

appleaccelerate_isavailable at /cache/julia-buildkite-plugin/depots/5b300254-1738-4989-ae0a-f4d2d937f953/packages/LinearSolve/1B5tc/src/appleaccelerate.jl:18 [inlined] this shouldn't segfault on Non Apple hardware right?

It definitely shouldn't, @staticfloat maybe might know something about that?

No, that definitely should not segfault.


Vulnerability roundup 99: hadoop-2.9.1: 1 advisory [8.8]

search, files

[ ] CVE-2020-9492 CVSSv3=8.8 (nixos-20.09, nixos-unstable)

Scanned versions: nixos-20.09: 95ce0f52ec1; nixos-unstable: 64b46178838.
Cc @volth

hadoop 2.9.1 was dropped in #141143


为什么Android 升级到weex0.26的时候，之前的项目里面的console.log日志再AndroidStudio打印不出来了

Describe the bug

To Reproduce

Environment

Expected behavior

Screenshots

Additional context

0.24的也不行

需要用https://weex.apache.org/zh/docs/modules/console-log.html#switchloglevel

确定这demo能跑？

Safari，Chorme直接run就抛错，能不能再用点心维护

在这里，每个人都是无偿在为社区做贡献，请记住，你并没有付钱给我们。
I am sorry, but everyone here is doing this job for free, and you don't pay I or anyone else money, or do you?

I'd like to close the issue accroding to our code of conduct.

Examples of unacceptable behavior by participants include:

Trolling, insulting/derogatory comments, and personal or political attacks
Public or private harassment

If you find something wrong, something unexpected, please describe your questions politely and try to figure it out by yourself.


Error: Calling the 'writeAsStringAsync' function has failed → Caused by: File '/var/mobile/Containers/Data/Application/XXXXXXXXXXXXXX/Documents/.posthog-rn.json' is not writable

The error "Error: Calling the 'writeAsStringAsync' function has failed
→ Caused by: File '/var/mobile/Containers/Data/Application/XXXXXXXXXXXXXDocuments/.posthog-rn.json' is not writable" showed up in my sentry logs three times.
It's hard to pinpoint commonalities with the three events I have gotten, but it seems related to pressing a text component inside of an animated view?
V3.1.2 of posthog-react-native
OS: iOS only as of right now.
Let me know if any other information is needed! I've seen this 3 times in production so far.

@noahkurz thanks for the issue, I transferred the issue to the right repo.
writeAsStringAsync  comes from https://github.com/PostHog/posthog-js-lite/blob/dfd70e6cb0dfdaf1b8cccc19f5531b846b8f4f6c/posthog-react-native/src/native-deps.tsx#L81 and here https://github.com/PostHog/posthog-js-lite/blob/dfd70e6cb0dfdaf1b8cccc19f5531b846b8f4f6c/posthog-react-native/src/storage.ts#L4
Which storage do you use? expo-file-system or @react-native-async-storage/async-storage? Which version?
I think this is an edge case where the app doesn't have write permissions in the folder, not sure we can do something about it.

Wow, thanks for the quick response and tracking down of this issue. I currently have both because I am migrating away from async storage, so looking at the code it should be boiling down to expo-file-system here. I am on version 17.0.1.

It's hard to pinpoint commonalities with the three events I have gotten, but it seems related to pressing a text component inside of an animated view?

It's hard to pinpoint commonalities with the three events I have gotten, but it seems related to pressing a text component inside of an animated view?

If it breaks when saving a file, the action can be anything, if the file isn't writable it seems to be something like the device, the simulator/environment the app is running, can you reproduce this issue? Is that happening only in production with real users? Do you have any more details?

I cannot recreate the issue myself and it is only happening with real users in production. It is very rare as it is currently 0.002 percent of my users.
The users are on iOS 17.4.1 or 17.6.1
All of the events happened in the same build and version of my app. (which is very weird)
The device type is either  iPhone 12 pro or iPhone 13 pro max.

@noahkurz thanks.
I wonder if those are jailbreak devices with restricted permissions since it's a so small % of users and no one else reported it so far.
Without an MRE would be hard to figure out what's happening.
I'll close it as non-reproducible for now but let us know if that happens again and if it increases, or if you can reproduce it, thanks.


Confused about Security Center Logs

I'm trying to trigger a Logic App based on Advanced Threat Protection scans of my blob containers. I cannot for the life of me locate WHERE these logs are written to.
This is beginning to get frustrating.
Where are ATP logs stored and how can I programmatically access them to take action.
Thank you!

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

ID: 8267e218-3748-2820-3eee-80479705eec2
Version Independent ID: 8c6d5fce-6383-a0f8-7df3-f5e0a77bbad6
Content: Data Collection in Azure Security Center
Content Source: articles/security-center/security-center-enable-data-collection.md
Service: security-center
GitHub Login: @memildin
Microsoft Alias: memildin

@ericthomas1 Security Center uses the Log Analytics agent to collect and store data. Log analytics stores all the data in workspaces.  It can be the default workspace created by Security center or any exiting one which you might have linked with security center.
To find which workspace are you using for security center. Go to :

Login to Azure portal.

Go to security center dashboard.

Select Pricing & Settings

Select your subscription from right pane.

Select Data Collection :

Here you can see your workspace configuration to identify workspace your security center is using.

Once done, search workspace in Azure portal

You can then select your workspace and it will have your security center data stored which you can use with Logic Apps.

I don't have permissions to view anything past step 4. Trying to find the correct person to speak with at my org.

@ericthomas1  Sure, let us know if you need any further help. We will close this for now, you can always comment here to get this re-opened.


Unable to save received files

Hi, I'm using crocgui on a Xiaomi 11T with MIUI Global 12.5.5.
Whenever I try to send a file to my device it seems to download correctly, but after it finishes getting it, a file explorer pops up, and it doesn't show any way to save the file. If some screenshots or logs would be of help, I'm happy to provide them.

screenshots would help
Also, are you able to try "Fyne Demo" on the google play store? Just to see if the save/file dialog works there.

Also, are you able to try "Fyne Demo"

So according to that application, the File Save dialog does not work on my device, but the Folder Open dialog does. So, the window I get showed whenever I receive a file is the Folder Open one.
Also, here are some screenshots. Before downloading, everything works like normal. After it finishes getting the file, the Folder  Open dialog appears, which doesn't have any options to save the file. If I select a file and click on confirm, it goes back to the app and shows that error while freezing it. If I just cancel, the app crashes.

I think your best bet is to get the "fyne demo" to do file save, as all I do is use fyne. I don't know how to help you.

Hi again. This apparently was a problem with MIUI that seems to be fixed in its version 13.
Will be closing the issue for now


bugfix: Don't try to always get system jvm first

Previously, we would always first specify system| when downloading default JVM, which would coursier just return java from JAVA_HOME without any checks even if we needed to download never Java. Now, we only use specific versions, since java home is handled before.
Trying to figure out the tests in https://github.com/VirtusLab/scala-cli/pull/2507

I rebased this on top of main, that should fix the CI


Fix QPDFOutlineDocumentHelper::resolveNamedDest  (fixes #1238)

Handle named destinations where the entry is a dictionary with /D entry.

This is a fix for #1238


Device linking reliability

I've done some testing of device linking and it is uh reliably unreliable; in numerous tests with various browsers / OS, device linking stalls:

in browser A, open the devtools and network tab and filter by 'WS'. Notice there seems to be 2 connections? Click on one connection to view the messages
in browser A, click on "connect an additional device", then copy the url
in browser B, paste and go to the url, then open the devtools / network tab and filter by 'WS'.

What happens:

while the numeric code will likely appear in browser B, the code entry field never appears in browser A
If you look at the WS connection in browser A, you see binary messages being received that decode to something like this:

{
"iv":"aODILVs2hrs6aCaSEgbP+g==",
"msg":"Rss0HEgjpecVMPpbvUBu4rvsUetzSvCfDZNhzozXQpjBFkvBMEUYbx9OpRnPmsv0HrWGDxczg7U7FMJaH8bJSMdidj9t+Srt25jsq3R7n51xyMCi7pfQORzRZoP+SI63cP65J4/6ZNi4iBzQTedod6nw9An09VDOfzkoo1Nw26RaE7Iupepa6/LzaOU6O+cebD6wm3+SMwBVvgxnw3S3uokJwV2uVs0f7lsxkKhjGc9/7hyNx+HdnQOBkXJi7duq5ybRAMFvKa6TUBzYqDlxKrRU7eHOkh9oV6JvgXtn5tZfjUehtgHxbPX+5D0hxGSfgGZVs6rwHflGE5uXwhEd0SBpyb5ch8KpQgJW/SPsi2fPYE9klErz0iisDOCI92OvOL0P+0ta0RXhnmI4R7xOqiTqUyjD+Ogw/8zOEnMZkYiOOjvKe34eJ5DIU5TSQ6d3RlnRtxfJPsFyghIEFHtg2QBEmmG4XJeyH6btPECGNbjFIlrokCLFAPRJq0J5POOwqw011eOxYepOsFpjbu7IZMFUSzxbPllVxej+AVzfKgHc7GtK27B8Io++Y41fgRiIbqMh7CcuMfHCp8WaGdxqVqUwjqLweTWrjYZjI38="}

When the browsers are in this state, I have seen it start working after refreshing browser A, but this is not reliable.
In a successful device linking session I see WS messages being sent from browser A in response to browser B, but this never happens on the first attempt to link.

As a first step on this issue - we should deploy and test with versions of WAT etc and webnative 0.34, not the currently deployed version. No use in trying to fix a bug that's already fixed.

Andy fixed this issue in the 0.35 branch
The issue was indeed that the connection was opened multiple times.

I've attempted a reproduction in https://github.com/fission-codes/aol-demo/tree/upgrade-webnative-0.35.0 to gather more information from a second app.
The issue was not reproducible on a couple of attempts linking between desktop browsers including:

Chrome -> Safari
Chrome -> Firefox container

There were however issues linking from Desktop Firefox to Chrome on iOS. The symptoms are a bit different. Using chrome://inspect logging, the following is logged:

These messages are logged here: https://github.com/fission-codes/webnative/blob/3bd09cdd70d24d6df32cf9630d6565b9b2beff5b/src/components/auth/channel.ts#L53-L87
It seems like this should make more than just two attempts.

Safari iOS has a similar issue as Chrome on iOS.
Starting the linking process there while debugging in macOS Safari shows the following output:

As with Chrome on iOS, we are only making two attempts.

The Chrome on iOS and Safari iOS issues with retries described above are fixed in https://github.com/fission-codes/webnative/issues/446.


drop python 3.8 and support 3.12

Closing in favor of https://github.com/iterative/scmrepo/pull/312


[release] release for 1.6.0

[ ] I have registered the PR changes.

Ⅰ. Describe what this PR did
release for 1.6.0 and merge into master
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.9 out of 33 committers have signed the CLA.:white_check_mark: wangliang181230:white_check_mark: slievrly:white_check_mark: a364176773:white_check_mark: tuwenlin:white_check_mark: Bughue:white_check_mark: jsbxyyx:white_check_mark: renliangyu857:white_check_mark: zw201913:white_check_mark: xingfudeshi:x: lcmvs:x: liujunlin5168:x: AlexStocks:x: pengten:x: a1104321118:x: duanqiaoyanyu:x: liuqiufeng:x: robynron:x: conghuhu:x: AlbumenJ:x: yujianfei1986:x: doubleDimple:x: JavaLionLi:x: miaoxueyu:x:<PHONE_NUMBER>:x: github-ganyu:x: whxxxxx:x: crazy-sheep:x: neillee95:x: wingchi-leung:x: l81893521:x: zhangzq7:x: odidev:x: zhuyoufengYou have signed the CLA already but the status is still pending? Let us recheck it.


800 Remove dependency on require_all

From require_all's changelog:
2.0.0:
Merged PR #24 (https://github.com/jarmo/require_all/pull/24) Prior to
version 2, RequireAll attempted to automatically resolve dependencies
between files, thus allowing them to be required in any order. Whilst
convenient, the approach used (of rescuing NameErrors and later retrying
files that failed to load) was fundamentally unsafe and can result in
incorrect behaviour (for example issue #8, plus more detail and
discussion in #21).
Thanks to Joe Horsnell (@joehorsnell)
This commit removes the dependency on the require_all gem by using
Ruby's #require method wherever it is needed.

Thanks, this is good.
The fewer dependencies the better.
Explicitly requiring what is needed is better than magically including everything (which was a result of me being lazy while I was initially developing all this.)
Thanks.

Hmm this passes the tests, but still fails when trying to run generate --all


Testing deprecated methods

Deprecated features still need to be tested to guarantee they keep working until they're finally removed.
They will trigger deprecation warnings on the spec suite. This adds unnecessary noise because when we explicitly test deprecated methods, it's obvious that they're deprecated. And it incentivizes submitting "fix warning" PRs such as #8454.
To circumvent this, we could add some kind of comment or another form of annotation for such specs that are explicitly meant to test deprecated behaviour.
This would at least prevent PRs for fixing the deprecation message.
One step further would be to automatically suppress deprecation warnings for the respective spec.
I think this could actually be very simple to implement. Because this really only affects specs and deprecated methods should only be called directly in the spec body, a naive static filter should be enough.
require "spec"

@[Deprecated]
def deprecated
end

it "test deprecated method" do
  deprecated
end

This is the warning:
In deprecation_spec.cr:8:3

 8 | deprecated
     ^---------
Warning: Deprecated top-level deprecated.

crystal spec, after compiling the program reports the warnings. These could simply be filtered based on file and line number. If it's in a spec file and maybe has some kind of annotation naming the deprecated method that should be suppressed.
Obviously this won't work if the deprecated method is called indirectly. But that should be avoided anyway because it would mean the deprecated method is used in some code other than specs.
This idea originally started in #8454

Has anyone tested just using --exclude-warnings spec when compiling the spec suite?

Oh, nice. That could actually work 😃
That way there would be no comments attached to specs for deprecated features (or at least not required). But I suppose that's not really important as deprecation warnings are disabled anyway. And when the deprecated features are removed, the spec will fail and prompt to be removed.
So, yeah that sounds like a perfect solution.
I'd propose to make --exclude-warnings spec the default when running crystal spec.

@straight-shoota it's only really a safe default in the crystal repo itself, since crystal has no dependencies. Otherwise, spec code is just normal code and you don't want a warning for a spard's spec suite which uses a deprecated stdlib method to be supressed.

I think it's fine to have warnings in the compiler's test suite. After all they are just warnings and they remind us to eventually remove those methods.

@RX14 Yeah, right. That's why I suggested to somehow annotate which deprecated methods a spec tests in order to exclude warnings for them.
@asterite Yes, it's not a big deal, but having a simple and efficient solution to this problem would be quite useful in the long run considering not only stdlib but the entire Crystal ecosystem.


Doc: fixed typo in cheat sheet.

SSE = Server-Sent Events, not "Server Side Events"!
Just one word exchanged. Decided to adopt the notation used in the docs/http/sse ("Server Sent Events") instead of the more widely used notation with dash ("Server-Sent Events") because of consistency reasons.

Facepalm! Thanks!


deployment: support of Zurich region

Describe the feature
Support deployment in Zurich region.
Use Case
Support deployment in Zurich region.
Proposed Solution
No response
Other Information
No response
Solution version used
v2.1.1

fixed in v2.2.0


documentSelector from server capability have lower priority

https://github.com/Microsoft/vscode-languageserver-node/blob/e3b566dc9e6ae60fa3d6641c3bb480634e4a0ad8/client/src/common/features.ts#L539
let options: RO & { documentSelector: DocumentSelector } = (Is.boolean(capability) && capability === true ? { documentSelector } : Object.assign({}, capability, { documentSelector })) as any;

It works as expected when documentSelector of capability is null, but overrides the documentSelector when it is a valid value.
Seems documentSelector from capability should have higher priority when it's not null or undefined, otherwise there's no need for it.

@chemzqm The notebook registration happens here https://github.com/microsoft/vscode-languageserver-node/blob/ffaf05ddd1fa9ca5f258cd0b08cc6cd1794c5b57/client/src/common/notebook.ts#L953 and doesn't go through the code mentioned here: https://github.com/microsoft/vscode-languageserver-node/issues/1060#issuecomment-1220421520 is


Fix debian build; Bring debian build into ci_parameterized_build

@tensorflow-jenkins test this please

Ready to be reviewed/merged.


[mp4] MP4 container doesn't know the color space

So it reports a dummy value of YUV420p which is incorrect for ProRes. Setting null (because we don't know) and figuring out from the actual coded picture.

@svitvitskiy maybe we should parse avcc video sample entry sps (if available) for that?
like here https://ffmpeg.org/pipermail/ffmpeg-cvslog/2013-January/058857.html

This will require pulling the first frame. We'll have to cache it and later feed it through the 'nextFrame' (possible but complicated). Then we can ask the specific decoder to probe it's frame for the metadata (all the supported decoders support this).
Let me know if you want to do that.
I'd say color information is specific to the codec not the container, the color is known the moment the first image is decoded. All the decoders support probing the packet for metadata.

i mean stsd.avcc.sps

Sure, agree.


Add Hybrid Compute Machine Alerts YAML

Overview/Summary
Added Hybrid Compute Machine Alerts YAML file with visible alerts.  Uses Log alerts only.
This PR fixes/adds/changes/removes

Adds Hybrid Compute Machine alerts

Breaking Changes

Replace me
Replace me

As part of this Pull Request I have

[x] Read the Contribution Guide and ensured this PR is compliant with the guide
[x] Checked for duplicate Pull Requests
[x] Associated it with relevant GitHub Issues or ADO Work Items (Internal Only)
[x] Ensured my code/branch is up-to-date with the latest changes in the main branch
[x] Ensured PR tests are passing
[x] Updated relevant and associated documentation (e.g. Contribution Guide, Docs etc.)

@Brunoga-MS added you as a reviewer since these alerts are tagged with alz


clang-format.language.proto.style is not utilized

The clang-format extension has overrides for languages, including proto. It is configurable with clang-format.language.proto.style but the extension does not seem to utilize that field.
If I set a style in clang-format.style it is respected but clang-format.language.proto.style is ignored.

I believe this was an issue with clang-format.


#9 Start timer only if server is registered

timer is not working reliable on android. branch will be abandonded


Access Log pattern is not configurable in APIM 3.0.0

The access log pattern which is defined in repository/conf/tomcat/catalina-server.xml file has not been templated in new config model. The following config has to be introduced to repository/resources/conf/templates/repository/conf/tomcat/catalina-server.xml.j2
<Valve className="org.apache.catalina.valves.AccessLogValve" directory="${carbon.home}/repository/logs"
prefix="http_access_" suffix=".log" pattern="{{http_access_log.pattern}}"/>

tagging https://github.com/wso2/product-apim/issues/7228


[build] Publish IntegrationTest utils

Summary, imperative, start upper case, don't end with a period

Publishes IntegrationTest Utils artifact so that it can be used in other projects.
How was this PR tested?

 ./gradlew -Pversion="0.0.1-SNAPSHOT" publishToMavenLocal
Does this PR introduce any user-facing changes?

[x] No. You can skip the rest of this section.
[ ] Yes. Make sure to explain your proposed changes and call out the behavior change.

Could you describe for example how integration test module could be used in other projects? It is a bit confusing for me.

Another project can subclass SystemProducer for example and may need access to integration test framework for validation.


SharedApp inherit api based auth enable property from root app

Purpose
$Subject
Fix: https://github.com/wso2/product-is/issues/19662

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/7933038666

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/7933038666
Status: success


Only generate .json output on successful compile.

The current master will drop the ABI JSON file even if the compile fails, which might be fine but feels weird to me.

Note to self: Double check if we are emitting JSON when we run just pint build

@otrho Is this still an issue? I'm unable to reproduce it.
When I run my own test.pnt file with cargo run --bin pintc test.pnt I do not get any ABI JSON file or other JSON files.
ex.
predicate test {
    var x = 2;
    var y: ( int => int );
}

results in

Error: variables cannot have storage map type
   ╭─[test.pnt:3:9]
   │
 3 │     var y: ( int => int );
   │         ┬
   │         ╰── found variable of type storage map here
───╯
Error: could not compile `test.pnt` due to previous error

When I try with the latest pint toolchain using pint build I also do not get any JSON files in the /out directory
ex.
storage {
    counter: int,
}

predicate Increment {
    state counter: int = storage::counter;

    constraint (counter == nil && counter' == 1) || counter' == counter + 1;

    var x: (int => int);
}

results in

   Compiling counter [contract] ...
Error: expected `::`, `a type`, `an identifier`, or `{`, found `(`
    ╭─...
    │
 10 │     var x: (int => int);
    │            ┬
    │            ╰── expected `::`, `a type`, `an identifier`, or `{`
────╯
Error: `pintc` encountered an error: parse error

This is for both parsing and flattening compilation errors.
Please let me know if I'm missing something key here 😄

Yeah, if you take a look in main.rs the steps we take are lex+parse, followed by type-check & flatten, then to write the ABI, then to compile the contract.  So if there's any error during asm-gen then it'll have written the abi but still report an error (probably an InternalError).
Here's a contrived example:
predicate test {
    state x = __storage_get(123);
}

This was annoying me when using tests which might (deliberately) fail during asm-gen and I'd use cargo r on the test file to confirm the error messages looked correct before putting them into the test file for cargo t and a .json file would get dropped, which the test harness now checks against.  So you get a weird error from cargo t until you realise you need to delete the ABI file.
So it's not high priority but it was annoying.  The answer I think is to put all the .json dropping code together in main.rs after we've successfully built everything.

Ah I see. The issue is happening from the compile failing during the asm-gen and not from parsing and flattening issues.


Not Seeing the Service Under "Services" in Windows

Hello, sorry this might be a really newb issue. I'm using a .Net 4.6.1 Console App.
I am new to this but when I first started with a very basic service I was seeing it show up under the Services panel in Windows. But now I don't see it anywhere. My code is mostly straight from docs. Below is my configure service method and the main() method within Program.cs runs this method like standard. The service starts because the timer and code I have within the start() method runs so I have no problem with the application, it works. But I can no longer find the service name anywhere under the Services panel. I do build the application and use the .exe to run it on other machines including the one I'm building it on and I don't see the name anywhere on other machines either.
Is using the .exe why I'm not seeing a service name? No service is being installed? When I debug the application I also see no service name but I swear that I used to. What am I not understanding?
internal static void Configure()
		{
			HostFactory.Run(configure =>
			{
				configure.Service< Initializer > (service =>
				{
					service.ConstructUsing(s => new Initializer());
					service.WhenStarted(s => s.Start());
					service.WhenStopped(s => s.Stop());
				});
				configure.RunAsLocalSystem();
				configure.SetServiceName("DataRefresherService");
				configure.SetDisplayName("DataRefresher");
				configure.SetDescription("Refreshes Public Database with NetSuite Data");
			});
		}

Hi,
With the exe you builded, did you try to install like in the example here: https://topshelf.readthedocs.io/en/latest/overview/commandline.html
Ex: in cmd, try DataRefresher.exe install -autostart and check if it shows.

Yes it looks like that made it show up. Except autostart took two hyphens and it didn't actually start itself, I still had to manually start it. Thank you!
My only other question would be the command line interface that comes up when you run the .exe by double clicking. Is there any way to get that back while the service is running? Or is that not something I should be relying on to know the status of the service as it runs day by day?

Dear DanJ210,
I am not sure if I understand you right, but if your service is installed, then it is running in the background without the commandline interface. The windows system will handle starting and stoping, if you have used the "-autostart" option.
There should be no need to start your DataRefresher.exe by double click.

@chrkon So when you double click the .exe a command line interface comes up, do you know that? When you install the service via command line the command line interface does not come up, the service just starts and runs in the background.
I was only wondering if there was a way to get the command line interface back without double clicking the .exe to run. Not a big deal. But if you double click the .exe you'll clearly see a command window come up telling you what the service is doing. This doesn't come up unless you double click. Very easy to notice.
Does this make sense?


Camera: Fixes crash during camera configuration

This PR fixes a potential runtime crash during camera re-configuration where the texture it's still None.

This causes https://github.com/kivy/kivy/issues/7259. I believe the issue is that when on_load is dispatched, we may not have the final texture, and the real texture never gets set. So https://github.com/kivy/kivy/pull/7049 is a better fix as it only sets the texture when the texture is updated.


Added a portable way of getting the jupyter executable in target ma…

…chine.
It's not necessary that jupyter will always be available system-wide (i.e., /opt/...). It's possible it's only available in a particular user space. Hence, using command -v <command_name>, we can get the location of the jupyter executable and substitute it in the required place.

@shubhambhattar Thanks for PR.

@vharsh @satyamz I think I found a few other places  in which we can make a similar change. Shall I do those too?

Also, why is the pull request not being merged?

@vharsh @satyamz I think I found a few other places in which we can make a similar change. Shall I do those too?

@shubhambhattar  Are you making these changes in this PR? I'm waiting for your response on this.

@satyamz No. I'll probably make other PRs. I found another issue in one of the Python files, and am currently working on it. This PR is done from my side. If you find it satisfying, you can merge it. I'll raise other requests for other issues.

@shubhambhattar Thanks for the PR!

Congratulations @shubhambhattar  for your PR getting merged! Thanks for taking part in OpenEBS Hackfest.
Fill up the doc form to get the Hackfest T-Shirt and Swags
https://docs.google.com/spreadsheets/d/1TZYIdERnD72YPeUsdS5hDfI6xgXXCax4-DHpXh-o6r0/edit?usp=sharing
Looking for some more awesome contributions from you and win more prizes


EIO-696 create static site deployer chart

https://github.com/rancherlabs/eio/issues/696

This is no longer required.


[fix] clippy warnings

Codecov Report

Merging #187 (4159741) into main (2e03eff) will decrease coverage by 0.05%.
The diff coverage is 45.45%.

@@            Coverage Diff             @@
##             main     #187      +/-   ##
==========================================
- Coverage   50.44%   50.38%   -0.06%
==========================================
  Files          58       58
  Lines        1929     1927       -2
==========================================
- Hits          973      971       -2
  Misses        956      956

Impacted Files
Coverage Δ

app/src/commands/apply.rs
0.00% <0.00%> (ø)

app/src/main.rs
0.00% <ø> (ø)

lib/src/actions/package/repository.rs
0.00% <0.00%> (ø)

lib/src/atoms/file/decrypt.rs
87.09% <ø> (-0.41%)
:arrow_down:

lib/src/contexts/mod.rs
80.55% <ø> (ø)

lib/src/manifests/load.rs
0.00% <0.00%> (ø)

lib/src/actions/file/link.rs
93.00% <100.00%> (ø)

lib/src/actions/package/providers/aptitude.rs
64.28% <100.00%> (ø)

lib/src/atoms/git/clone.rs
73.33% <100.00%> (ø)

Continue to review full report at Codecov.

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


ci: cancel github workflows if there is a new trigger

Use Concurrency Groups to cancel github workflows if there is a new trigger.

Hm, doesn't this already happen?

No, from what I can tell, this is a good watch https://youtu.be/JMHs5lYpvAM?t=314

Hm, doesn't this already happen?

Just confirmed it. For example, this workflow was canceled while it was running because of a new push to the PR branch
https://github.com/ockam-network/ockam/actions/runs/1581076168

Hm, I must be misunderstanding — that's what I thought "cancel github workflows if there is a new trigger" meant. I'll watch the video.

Oh, I see, that's from this branch, hmm...

What I meant to say was that it doesn't happen if you don't have a concurrency group defined. New pushes continue to trigger more runs. This PR adds concurrency group definitions that are unique to a workflow+branch.
https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#concurrency

I also tried
    if: |
      github.event_name != "pull_request" ||
        github.event.pull_request.head.repo.full_name == github.event.pull_request.base.repo.full_name

based on this article (it has a good description of the tradeoffs)
https://wildwolf.name/github-actions-how-to-avoid-running-the-same-workflow-multiple-times/
but it didn't quite work on my first try .. will try on a later PR.

I see. I'm fairly certain that I've seen that behavior on PRs already (that is, when you update a PR branch, typically the pending jobs all fail — I've never dug into why, nor do I have a branch on hand that did it the other way).
I guess the default is slightly different though https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#examples-using-concurrency-and-the-default-behavior-1, and doesn't seem to have the flag to cancel in progress... Hrm, strange.
Well, either way I agree this behavior sounds desirable.

Hm, that blog post helps some, the description of the problem here:

Therefore we have four wasted jobs running: the jobs running for pull_request are the same as the ones running for push.

is something I've seen before, although I've followed the suggestion here:

The easiest workaround is to restrict the push event only to the main repository branch, like this: <snip>

(You may note that my blog on using Github Actions with Rust doesn't mention it (I don't think it does anyway, it's been a while since I wrote it), but does manage to suggest doing the right thing for this — because it's a problem I'm familiar with)
I'm not exactly how concurrency ties in here, but will do some more reading.