Test Discovery

I’ve been working on a project that essentially brings this library (XCTest) into a package I’ve called PGTest (Playground Test).
I’ve made very minor modifications to the existing code, namely:

XCTest needs to inherit from NSObject
I’ve also added @objcMembers to XCTest to enable runtime lookup

In addition, I’ve written my own version of XCTestMain since I don’t run it from command line and don’t want it to exit after its run.
Besides what’s mentioned above, I’ve also included a full set of SwiftUI components that provide test results and interactions similar to what you may see in Xcode (though with a more iPad Swift Playgrounds design).
I’ve managed to ‘discover’ all XCTestCase subclasses as well as any testXxx methods that may be present. However as I’m sure you’re already aware I cannot provide these to the library in order to execute them.
In order to combat this I’ve come up with an alternate strategy. I discover any ‘implicitly’ defined tests using the runtime, i.e. I show all ‘found’ tests in the UI, but in a disabled state, to help bring attention to that fact, for a user. In addition, I’ve included (in the UI) a button that allows the user to automatically generate the required allTests static property that PGTest then uses to enable those tests.
However I’ve hit a particular snag. The user still needs to provide the list of XCTestCase subclasses that should be included, since any auto-discovery I do returns a mere selector, rather than a pure Swift function.
Its not ideal having to include any of this code generation or manual labour writing allTests properties. But I had hoped I could at least simplify with the included ‘code gen’ by at least only requiring a regular copy/paste of generated code.
I did manage a while back, using @convention, to represent a selector as a Swift function, which compiles, but as you can imagine crashes at runtime since it cannot be ‘called’.

Quick note, I’ve also not yet been able to successfully call any allTests properties provided to the framework, I’ve found it tricky to find a working solution that ideally protocol extension based. I tried adding the property directly to XCTest but that just leads down a type-safe rabbit hole, since the expected allTests closure expected by XCTestMain (or my own variant) doesn’t allow a subclass definition.

I realise none of the above (especially Obj-C runtime features) are likely to be candidates for this project, however I was hoping someone may have some guidance or a new direction to help me progress. I feel like I’m on the precipice and it’d be great to have a familiar XCTest workflow when building apps (or at least pieces of apps) on iPad, which I’m doing personally more and more, until we have a formal introduction from .
My plan is to open source for everyone’s benefit but I need it to be usable and practical before I can do that. If necessary, I’m happy to share the project here or at least working sample code but any help or ideas here would be appreciated.

Ignoring the visual bugs (mostly stuff still to-do) but this should give you an idea of what I’m trying to get to and have envisioned so far.

I guess this repo isn't maintained at least in terms of questions/issues. Pity and disappointing. Moving on.


Make .toPromise attempt to use default Promise constructor

Hi,
I don't understand what's stopping .toPromise() to try to use the default Promise constructor if none is passed as argument?
I really think this should be the default behavior.

Have you seen the discussion in the original PR?
https://github.com/caolan/highland/pull/628#issuecomment-306671817
Basically, I was uncomfortable with writing code that implicitly depends on
a JS feature that doesn't exist in all execution environments without a
proper fallback.
On Fri, May 11, 2018 at 11:32 AM, Alexandre<EMAIL_ADDRESS>wrote:

Hi,
I don't understand what's stopping .toPromise() to try to use the default
Promise constructor if none is passed as argument?
I really think this should be the default behavior.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/caolan/highland/issues/647, or mute the thread
https://github.com/notifications/unsubscribe-auth/AGIyZVZVQ-EFWWLjdbNo3OxuMAOBj5u6ks5txb0qgaJpZM4T7u99
.

Hi @vqvu, sorry for the late reply.
I understand you avoid default arguments values, though is it still a problem to depend on Promise nowadays? It's standard, widely used and available in most environments.

IE11 is still a thing, unfortunately :(.
On Wed, May 23, 2018 at 3:14 AM, Alexandre<EMAIL_ADDRESS>wrote:

Hi @vqvu https://github.com/vqvu, sorry for the late reply.
I understand you avoid default arguments values, though is it still a
problem to depend on Promise nowadays? It's standard, widely used and
available in most environments.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/caolan/highland/issues/647#issuecomment-391260751,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGIyZVburVnze8f6bK9oW8u5jhBpQax1ks5t1Rp2gaJpZM4T7u99
.


[WIP] feat: Jobab api endpoints

For now looks good, do you want to add the comment APIs in this PR too?

Yes sure, giving an update asap

@riya09 should we have votings in jobab comments as well?

@riya09 done with with all the major endpoints I could think of. Please let me know if I have missed anything.

@riya09 can you please check if I understood everything correctly and if further changes are needed.

@riya09 all done


How to change location of error messages

By default, error messages that get generated when someone doesn't sign a form are displayed at the very beginning of the form, using the markup . Unfortunately, my signature pads are at the bottom of the form, so users that forget to sign the form never see the error message and just keep clicking the "submit" button.
How do I re-position the error messages so they display close to where the signature pad is displayed? Thanks.
Regards,
Bill

You could try using the onFormError callback function to create your own error message on the form where you'd like to see it.

You wouldn't happen to have an example of this, would you? Unfortunately, I'm a non-programmer that sometimes has to deal with programming. Thanks.
--------- Original Message --------- Subject: Re: [thomasjbradley/signature-pad] How to change location of error messages (#183)
From: "Thomas J Bradley"<EMAIL_ADDRESS>Date: 6/15/16 4:43 am
To: "thomasjbradley/signature-pad"<EMAIL_ADDRESS>Cc: "radman63"<EMAIL_ADDRESS>"Author"<EMAIL_ADDRESS>You could try using the onFormError callback function to create your own error message on the form where you'd like to see it.
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

To start you can do something like this:
$('.sigPad').signaturePad({
  onFormError: function (errors, context, settings) {
    // In here you can write the code needed to insert the error message
  }
});


Add Chat Component

Implement the Chat component according to spec: https://www.lightningdesignsystem.com/components/chat/

Here is my initial prop proposal for the component, what do you think?
Chat

Name
Type
Description

ClassName
array/object/string
Additional Class Names

isPastChat
boolean
Whether the chat is from past. Defaults to false.

children
Element[ ]
Chat body/content

Message

Name
Type
Description

direction
enum {"inbound","outbound"}
Direction of the message

time
string
Time of sending message

user
string
User sending the message

showAvatar
boolean
Whether to show user avatar. Defaults to false.

isTyping
boolean
Whether user is typing the message. Defaults to false.

peek
boolean
Whether to peek into message being typed. Defaults to false.

isUnsupported
boolean
Whether the message is unsupported. Defaults to false.

isUndelivered
boolean
Whether the message is undelivered. Defaults to false.

isCurrentAgent
boolean
Whether the message is sent by current agent. Defaults to true.

Attachment

Name
Type
Description

direction
enum {"inbound","outbound"}
Direction of the message

time
string
Time of sending message

user
string
User sending the message

thumbnail
string
URL to thumbnail

link
string
Link to the attachment

title
string
Title for the attachment

format
string
Format of the attachment

Event

Name
Type
Description

time
string
Time of the event

title
node
Description of the event

icon
string
Icon for the event

message
string
Message left by the agent additionally

isError
boolean
Whether the event is an error. Defaults to false.

Here is a basic example using these specs -
<Chat>
    <Event
      title={Chat started byAndy Martinez}
      time="4:58 PM"
      icon="chat"
    />
    <Message
        direction="inbound"
	    time="4:59 PM"
		user="Andy Martinez"
		showAvatar
	>Hi, my CloudWidget only speaks French</Message>
	<Message
        direction="outbound"
	    time="5:02 PM"
		user="Jason Dewar"
	>Hi Andy, thank you for contacting Widget Support. Can you please tell me what language you are trying to program on your CloudWidget?</Message>
	<Attachment
	    thumbnail="...."
	    title="Image.jpg"
	    format="image"
	    link="..."
	 />
</Chat>

Great props proposal. It's clear for a complex component.

isUnsupported and isUndelivered should probably be the same prop, since they can't both be true and it looks like they are limited to whether they are inbound or outbound.
peek and showAvatar are booleans and probably should be isSneakPeek and hasAvatar
Attachment should be a variant of the File component https://www.lightningdesignsystem.com/components/files/ 's "File with actions" it could be named Attachment, but take all the same props of File. I see that you proposed making File https://github.com/salesforce/design-system-react/issues/1879 so that's good. You might consider making that one first after the API is approved. So I am going to wait to comment on the props until file is reviewed.
title should probably be reserved for the HTML title attribute. label is fine.
Event should probably have variants that choose the icon.
Many of the string types should also be node also, so that styling can be done on the text.
I see showAvatar but I don't see an an avatar prop. Maybe it should just the avatar if one is passed in?

Please update and confirm by posting to this thread.

I will try to get https://github.com/salesforce/design-system-react/issues/1879 looked over tomorrow.


[Runtime] Stack trace is printed during error

Please see following
error in ballerina program: failed to invoke 'post' action in HTTPConnector. Connection refused, <IP_ADDRESS>-9793 	 at ballerina.net.http:post(NormalizeIntegrator.bal:115) 	 at sendMessageToBackEnd(NormalizeIntegrator.bal:51) 	 at bal.integration.normalize:normalizeResource(NormalizeIntegrator.bal:16) 	 at bal.integration.normalize:NormalizeIntegrator(NormalizeIntegrator.bal:12)
Rather than printing the stack trace, it's better to print the ERROR

This is fixed in the latest versions (tested in v0.91).
Now the following error is thrown:
error: ballerina.lang.errors:Error, message: failed to invoke 'post' action in ClientConnector. Failed to send the request : connection refused, <IP_ADDRESS>-80
	at ballerina.net.http:ClientConnector.post(<native>:0)
	at .:main(mainFunction.bal:46)


fix: docs of import text on icons modules

fix: #114

@amontalvof can you review the tests failed please??


Invalid RML file

Hi. Generating RML rules from my spreadsheet results in an invalid RML file (according to RMLMapper).
I managed to identify one of the problems, not the other.

CSV appears to be an invalid data format. Replacing 'CSV' by 'csv' as specified in YARRRML specification works. From the attached spreadsheet, I am able to generate YARRRML rules, then to convert these rules to RML rules using yarrrml-parser, then to generate RDF triples using RMLMapper.
However, if I try to generate RML rules directly from the spreadsheet, then RMLMapper returns the following error during RDF generation:

10:40:42.691 [main] ERROR be.ugent.rml.cli.Main               .main(179) - Unable to parse mapping rules as Turtle. Does the file exist and is it valid Turtle?
org.eclipse.rdf4j.rio.RDFParseException: Not a valid (absolute) IRI: #CONSUMER [line 11]

mapping.xlsx
s.tsv.txt

Hi,
As for the second issue, I also encountered the same error. I added an empty namespace and use the command I mentioned in issue #21 and it worked for me. You can also add your own default namespace directly in the generated RML mapping file.

Hi, this should be fixed, let me know if something comes up

Hi, I just tried the new version (using the Docker image) and the issue is still there. When using RMLMapper-java :
docker run --rm -v $(pwd):/data rmlmapper -m test.rml.rml.ttl
results in
10:16:01.809 [main] ERROR be.ugent.rml.cli.Main .main(191) - Unable to parse mapping rules as Turtle. Does the file exist and is it valid Turtle?
org.eclipse.rdf4j.rio.RDFParseException: Not a valid (absolute) IRI: #EMPLOYED [line 10]

Please note that this time I tried with your test example available in the data folder.

Hi!
I tried again, and I don't get the error running rmlmapper (rmlmapper-4.13.0) any longer. I generated RML files with the last version of both pypi and docker and it works. I leave the files here so you can try: Input XLSX, output RML mapping and test data
test_rml_mapeathor.zip

From my latest tests, it appears that everything works just fine. Thank you.


remove_interpolated_string can be simplified and made to match Luau behavior more precisely

Currently, the following expression:
`hello {name}!`

is translated as:
string.format("hello %s!", tostring(name))

This can be simplified to:
string.format("hello %*!", name)

This also more closely matches how Luau compiles it and means we don't need to track if tostring has been redefined somewhere.
In fact, the most accurate translation is:
("hello %*!"):format(name)

This would also mean we don't need to track if string was redefined.
This may have a minor performance drawback as currently Luau doesn't optimize this method-call style for string functions.

There is a strategy parameter to the existing rule which lets you pick between both translations
When set to string, it will use the %s formatter and add the call to convert the value. You can get it to use %* when it is set to tostring.
It is mentioned there: https://darklua.com/docs/rules/remove_interpolated_string/#parameters


Cleanup of uuv_dave.launch example

The default example is uuv_dave.launch.  This PR cleans up a few loose ends to update that example.

Removes image sonar (image_sonar_ros_plugin.so implemented in uuv_simulator) from the Rexrov uuv_dave.launch because the primary multibeam sonar sensor plugin is now here: https://github.com/Field-Robotics-Lab/nps_uw_multibeam_sonar
Removes the uuv_simulator GPS plugin from the example because

GPS doesn't work underwater and
Issue#77 and
if you need a GPS, you should use a standard plugin like the hector gps plugin.

@bsb808 Quick question.
I once thought of removing image_sonar_ros_plugin.so plugin in the uuv_dave.launch, but thought it would be something worthwhile for those who are not going to use multibeam sonar. I thought having multibeam sonar is going to be provided as an 'Optional' advanced feature. Should we still remove sonar entirely from our first-look uuv_dave.launch?


JdbcConnectionDetails Docker for testing

up to 3.1, use mysql docker for testing

<dependency>
  <groupId>org.springframework.boot</groupId>
  <artifactId>spring-boot-testcontainers</artifactId>
  <scope>test</scope>
</dependency>

can not inject application.properties, because the container start before it.
it not good to use dynamic properties

consider spring-boot-docker-compose
https://docs.spring.io/spring-boot/docs/current/reference/html/features.html#features.docker-compose

spring-boot-docker-compose provide a DataSource to MYSQL_DATABASE


Unable to read buffer with more than 512 bytes with read function

Describe the bug
We read and write a JSON config file to a device using read and write functions. If the file is shorter than 512 bytes, everything runs fine. But then it is longer, in Android devices we get up to 512 bytes.
To Reproduce
You will need a device that allows reading/writing capabilities/

Scan and connect to the BT using your Android device.
Write a string with more than 512 bytes using write function.
Read the written string using read function.
Compare both strings.

Plugin version:

@capacitor-community/bluetooth-le: [e.g. 0.4.0]

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Devices where there is no error:

iPhone (Latest iOS version)
Samsung S7 with Android Oreo (8.1)

-Devices with the BUG:

Samsung S23 ultra  - Android 14
Xiaomi Redmi 9  - Android 12
Samsung Galaxy Tab A8 - Android 14

Additional context
The JSON file we write:
{"wifi": {"ap_pass": "password", "sta_ssid": "Entrepanoles", "sta_pass": "entrepanesq244", "ap_ssid": "tankmont3l3m0"}, "channel": [{"min_level": "10.00", "max_level": "100.00", "chan_label": 1, "type": "RS485|ADC", "name": "Mi tanque grande en el cuarto azul", "min_volt": 0, "idpin": 1, "enable": false, "min_amp": 0, "tank_capacity": "5000.00"}], "info": {"refresh_interval": 30, "model": "XXXXX-S3", "interval": 30, "mcu_id": "3030f959d194", "channels": 1, "url": "https://api.XXXXXXXXX.net/api/v1", "refresh_inerval": 30}}
The JSON file we read:
{"wifi": {"ap_pass": "password", "sta_ssid": "Entrepanoles", "sta_pass": "entrepanesq244", "ap_ssid": "tankmont3l3m0"}, "channel": [{"min_level": "10.00", "max_level": "100.00", "chan_label": 1, "type": "RS485|ADC", "name": "Mi tanque grande en el cuarto azul", "min_volt": 0, "idpin": 1, "enable": false, "min_amp": 0, "tank_capacity": "5000.00"}], "info": {"refresh_interval": 30, "model": "XXXXX-S3", "interval": 30, "mcu_id": "3030f959d194", "channels": 1, "url": "https://api.XXXXXXXXX.net/api/v1", "refresh
Add any other context about the problem here.

@aitriago this is likely an issue with your Bluetooth device.
Each read command here generally corresponds to a single BLE packet, that normally are usually between 185 up to about 512 bytes. If your payload is exceeding the MTU (maximum transmission unit) that the BLE receiver & BLE device have negotiated, it will be cut off.
You will need to change your peripheral implementation to properly support Long Attribute Reads if you are sending payloads that exceed a single packet. See https://stackoverflow.com/questions/38241986/ble-read-long-characteristics-value-using-android-ios for some discussion about this. But, there's nothing that can be fixed or handled in the plugin for this.

You will need to change your peripheral implementation to properly support Long Attribute Reads if you are sending payloads that exceed a single packet. See https://stackoverflow.com/questions/38241986/ble-read-long-characteristics-value-using-android-ios for some discussion about this. But, there's nothing that can be fixed or handled in the plugin for this.

I agree. Thank you @peitschie!


Configure documentation autobuilds

Done. To trigger a documentation update, merge main into deploy-docs and push. I think it has to be a push and can't just be a merge via github.
This process can almost certainly be improved on, but works sufficiently well for now.
Documentation is live at https://wams-js.github.io/wams/


Update docs, dirs and templates

Changes:

[ ] Move modules into actual Modules folder to conform with Paper structure
[ ] Add functional templates for the full pipeline

Update:

[x] ReadMe
[x] Changing Params
[ ] Run Scripts Advanced

Check Links:

[ ] ReadMe
[ ] Changing Params
[ ] Run Scripts Advanced

add option to use direct path to plan in preprocessing
"""
preprocessor = preprocessor_class(path_to_plan)
preprocessor.to_the_moon()
"""


add more sophisticated usage examples for contained-network mode

Examples we should provide at least are

[ ] Container-2-Container connectivity
[ ] Host-2-Container connectivity

@steveeJ were you planning on doing this yourself?

@jonboulle eventually ;-)

Any chance we can get this soon-ish?

Yes, also linked to #1522.

I am merging this into #1522


cuba , senegal , angola , EI salvador, cameroon, italy, ireland,leben…

Summary
This pull request adds support for the following new currencies: Cuba, Senegal, Angola, El Salvador, Cameroon, Italy, Ireland, Lebanon, Mali, Malta, Madagascar, Togo, and Tonga.
Changes Made

Added new currencies to the currency list.
Updated the country flags associated with the new currencies.

Why do you want to add Italy and Ireland for example? It is a currency list not a country list.


Searching when there is an active tag

Need to be able to use search feature when a tag is active

this is working


utils.get_netrc_auth silently fails when netrc exists but fails to parse

My .netrc contains a line for the github auth, like this.
It turns out that netrc.netrc() doesn't like that:
>>> from netrc import netrc
>>> netrc()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/netrc.py", line 35, in __init__
    self._parse(file, fp, default_netrc)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/netrc.py", line 117, in _parse
    file, lexer.lineno)
netrc.NetrcParseError: bad follower token 'protocol' (/Users/david/.netrc, line 9)

get_netrc_auth catches the NetrcParseError but just ignores it.
At least having it emit a warning would have saved some hair-pulling.

Yeah, this is tricky. You can see the reason we added this logic in #449.
Given that you're using the function explicitly, maybe the best option is to add a kwarg to get_netrc_auth that allows it to be used in an explodey way (when users like yourself want to be explicit), but that allows us to continue to use it in a not-explodey way.

Because this can be done in a backwards compatible way, I've tagged this optimistically for 2.8.0


Add support to publish release artifacts to Pypi.org

@stevenhartley To publish artifacts, we would need a PyPI account.
https://pypi.org/account/register/


SClientIntegrationSpec doesn't run twice

The default implementation of the SClientIntegrationSpec class gives an error if we try to run the tests twice. (port already in use).
The default template from giter8 uses TestKit and BeforeAndAfterAll to cleanly close the test class after execution. Why not use those?

Yep you're correct. Someone else pointed this out as well - I just haven't gotten around to fixing it. Feel free to make a pull request if you have a good example already.


Won't just, go away? Braking SSL

I uninstalled, deleted the files on my host's file manager, and it's still there, I can not seem to find or remove the
wp-content/themes/matthew-pillado-pllc/js/jquery.sticky.js => N/A
It's breaking my SSL being un-secure but it doesn't even exist the js file or the query.sticky.js inside it, I can not seem to get rid of this.
Any ideas would be greatly appreciated, I use HostGator and C-Panel to manage the files. I use the Divi theme

matthew-pillado-pllc

Who created the theme?

Elegant Themes, Divi, is the parent
Is mise Le meas
Matthew T Thurner
<EMAIL_ADDRESS><EMAIL_ADDRESS>www,matthewthurner.com
817-350-7400 (SMS only)
This email may contain privileged or confidential information. The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future.
From: Daniel Ruf<EMAIL_ADDRESS>Sent: Monday, February 5, 2018 7:52 AM
To: garand/sticky<EMAIL_ADDRESS>Cc: Just-Being-Me<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [garand/sticky] Won't just, go away? Braking SSL (#271)
matthew-pillado-pllc
Who created the theme?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/garand/sticky/issues/271#issuecomment-363090131 , or mute the thread https://github.com/notifications/unsubscribe-auth/AhDkaVKec92lKZOlrZqBzq_NPMJ77ayDks5tRwdigaJpZM4RGAje .  https://github.com/notifications/beacon/AhDkabVpxowrZKypQWfhZS8Jm0UYaTslks5tRwdigaJpZM4RGAje.gif


Adding Indian-centeric datasets

Gather Point , Line, Polygon vector data for indian region

My proposal

replace obs data with point data in CSV format ( e.g. airports in india )
replace lakes  geojson to only include lakes in India
Add a line data for indian region

I added an Indian dataset here: https://github.com/geopython/diving-into-pygeoapi/blob/main/workshop/exercises/data/greater_hyderabad_municipal_corporation_ward_Boundaries.geojson


Remove isAfterRedirect parameters from notifications

These methods have been deleted anyway

Was afraid you'd handle that in the deprecations issue yeah... 😄


ONNX export problem.

Error info:

def get_seg_scripted(cate_list: list[torch.Tensor], kernel_list: list[torch.Tensor], seg_pred: torch.Tensor):
TypeError: 'type' object is not subscriptable

Could you please tell me how to export onnx model? Thanks

When exporting ONNX model, you should guarantee that the model do detect some masks from the input image. Or it will encounter an error in post-process. When inference with the exported ONNX model, you should use try-except to skip the inference error if the model do not detect any mask.

Ok, Thank you, I will try


Confuse about the code of multi-attention

In the example:
python -u train.py \
                       --data "Criteo"  --blocks 3 --heads 2  --block_shape "[64, 64, 64]" \
                       --is_save "True" --save_path "./test_code/Criteo/b3h2_64x64x64/"  \
                       --field_size 39  --run_times 1 --data_path "./" \
                       --epoch 3 --has_residual "True"  --has_wide "False" \
                       --batch_size 128 \
                       > test_code_single.out &

And default embedding size is 16.
So according to the code:
def multihead_attention():
    ...
    Q = tf.layers.dense(queries, num_units, activation=tf.nn.relu)
    K = tf.layers.dense(keys, num_units, activation=tf.nn.relu)
    V = tf.layers.dense(values, num_units, activation=tf.nn.relu)
    if has_residual:
        V_res = tf.layers.dense(values, num_units, activation=tf.nn.relu)

    # Split and concat
    Q_ = tf.concat(tf.split(Q, num_heads, axis=2), axis=0)
    K_ = tf.concat(tf.split(K, num_heads, axis=2), axis=0)
    V_ = tf.concat(tf.split(V, num_heads, axis=2), axis=0)

    ...

The num_units is 64 and num_heads is 2, it seems that the embedding size is 32 but not 16. I confused about it.

Yes, you are right that the default embedding size(which is d in our paper) for embedding layer is 16 and the embedding size for each head(which is d' in our paper) is 32 in this case.
There is a transformation that map the original embedding space R^d to R^{d'}. See
    Q = tf.layers.dense(queries, num_units, activation=tf.nn.relu)
    K = tf.layers.dense(keys, num_units, activation=tf.nn.relu)
    V = tf.layers.dense(values, num_units, activation=tf.nn.relu)


Accurate or normalized depth value in training?

Thanks for your contribution in FusionDepth!
I wonder whether the "depth" in the trainer.py is normalized or the accurate value of the depth in each pixel. When I print them in the training process, the value looks like normalized, which is generally below 1. But in the reprojection procedure, this depth value is used directly.

What's more, when calculating the loss, the depth is multiplied by 26. I have no idea what the "26" means.

Hi @Renatusphere :
The depth in the trainer.py is normalized and does not reflect the absolute scale. However, the pose net and the depth net are sharing the same scale so they could be used directly for re-projection.
We observe that the ratio between the predicted depth scale and absolute scale is around 26, so we use it here to roughly filter out the invalid depth points.

Thanks for your reply. I get it!

Hi @Renatusphere :
The depth in the trainer.py is normalized and does not reflect the absolute scale. However, the pose net and the depth net are sharing the same scale so they could be used directly for re-projection.
We observe that the ratio between the predicted depth scale and absolute scale is around 26, so we use it here to roughly filter out the invalid depth points.

Hi, thanks a lot for the work. If I want to use the  si_loss in other datasets, should I calculate the ratio again? and how to calculate the ratio between the predicted depth scale and absolute scale? Thanks again!

Hi @GANWANSHUI :
Thank you for your interest. In the KITTI dataset, the valid depth range is 0-80m, so we roughly scale the predicted depth to the real-world metric and filter out the depth points that are out of this range.
For other datasets, you do not have to calculate the ratio, using any method to filter out the unreasonable depth points should be good. By the way, torch.median(depth_gt) / torch.median(depth_pred) in this line is the ratio between the predicted depth and GT depth.


add keybindings to UI window

Allows for expanding servers to view more information about it.
Allows for installing/reinstalling/uninstalling servers.

The default keybindings is an attempt to mimic vim-fugitive's :Git
maps, and these can be overriden.
The keybinding implementation in display.lua is a bit hacky, but it
works and the "public" API is at least manageable. This will also
open up for adding more metadata in the future, such as filetype
information, currently installed version, latest available version,
etc.
Also there's Cowth Vader.

https://user-images.githubusercontent.com/6705160/136621980-3765a6a9-9a4b-4753-8e8d-df68a5fc67b4.mov


tx.Prepare undefined

The error occured when I'm trying to use xray for SQL Transactions:
stmt, err := tx.Prepare(ctx, `INSERT INTO names ( name ) VALUES ( ? )`)
if err != nil {
	return err
}

Err: tx.Prepare undefined (type *xray.Tx has no field or method Prepare)
Environment:

Go version go1.12.1 darwin/amd64
SDK version 1.0.0-rc.13

It seems that the issue is because dep dependency manager not installing specific version correctly; Overriding with master branch fixed it!


loopProtect.protect problem

loopProtect.protect causes problems for every for loop!!!!
           var conquer=function(divide){
                var m=divide.length, biggest=0;
                for(var i=0; i<m; i++){
                    if(biggest<divide[i]) biggest=divide;
                 }
                 return biggest;
           };

Please provide more details, like what challenge you are working on and exact steps to reproduce.

It is in bonfire: Find the Longest Word in a String. The last for loop of every program I write gets blocked even if they identical to the one prior. I think it is the website's js interfering. It is not a natural javascript feature.

Please provide the entirety of the code that is getting incorrectly blocked so that we can attempt to reproduce, not just part of it.

function findLongestWord(str) {
  var divide=function(str)
  {
    var m=str.length, word, amount=[];
    for(var i=0; i<m; i++){
         if(str[i]===" ")
          {
             var size=word.length;
             amount.push(size);
          }
          else word+=str[i];
    }
    return amount;
  };

  var conquer=function(){
    var m=divide.length, biggest=0;
    for(var i=0; i<m; i++){
      if(biggest<divide[i]) biggest=divide;
    }
    return biggest;
  };
  return conquer ;
}

findLongestWord("The quick brown fox jumped over the lazy dog");

Loop protect is not the problem. Your code is returning a function and the contents of that function are being output to the console. Please in the future use the Help Chat to ensure that what you're seeing is a bug with the site and not with your code.
Thanks and happy coding!


[SPARK-8819] Fix build for maven 3.3.x

This is a workaround for MSHADE-148, which leads to an infinite loop when building Spark with maven 3.3.x. This was originally caused by #6441, which added a bunch of test dependencies on the spark-core test module. Recently, it was revealed by #7193.
This patch adds a -Prelease profile. If present, it will set createDependencyReducedPom to true. The consequences are:

If you are releasing Spark with this profile, you are fine as long as you use maven 3.2.x or before.
If you are releasing Spark without this profile, you will run into SPARK-8781.
If you are not releasing Spark but you are using this profile, you may run into SPARK-8819.
If you are not releasing Spark and you did not include this profile, you are fine.

This is all documented in pom.xml and tested locally with both versions of maven.

@pwendell @JoshRosen @srowen could you take a look?

Merged build triggered.

Merged build started.

Test build #36522 has started for   PR 7219 at commit 77b43ec.

Test build #36522 has finished for   PR 7219 at commit 77b43ec.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  *

Merged build finished. Test PASSed.

I think this should also be a solution, yes.
Why does scalatest become a compile scope dependency instead of test? because test deps aren't transitive? right-er would be to have all test modules depend on scalatest then, if so.

Hey @andrewor14 - I took a look at this. It seems, to me a bit weird to have Spark core dependend on Scalatest. This will affect all of our downstream applications, since they will also inherit the scalatest dependency, and that seems risky given that it has its own transitive dependencies (most of those are marked as optional - but I have no idea how various build tools handle optional dependencies). I was wondering abut some alternative solutions such as:

Just declare SparkFunSuite in each module - this is a bit clunky, but you could have a large warning in the class file that it's N-way replicated. It's a very small class so I don't anticipate large modifications in the future. Then we don't have to reason about any build tool behaviors.
Do the suggestion from my email where you disable the dependency reduced pom, except we only enable it for a certain profile.

I am pretty hesitant to change compile dependencies around in 1.4.1 vs 1.4.0 - since we've typically not done this in a release. I also think it would be good not to have test dependencies as compile, if we can avoid it.

If this is just because test dependencies are not transitive in Maven, yes indeeed the alternative is to declare the scalatest test-scope dependency in each module. It's more boilerplate, but the right-er thing to do. So I like 1.

Hey @srowen - there is more going on here. The issue is that there is actually a class called SparkFunSuite that is defined inside of the core module that the other modules need to depend on. It's not just that all of them need the scalatest dependency. So we'd have to copy/paste the source code for SparkFunSuite N times.

Oh I get it, darn. Well, I vote for 2 then. This amounts to dodging the shade plugin bug where the cause doesn't have to come up anyway. The profile release-profile should be a special name in Maven that gets enabled automatically when you run the release plugin; is that useable?

Yeah, I completely agree it's a terrible idea to introduce scalatest as a core dependency. This patch goes against most of my own principles in software development and I would be very happy to change it.
@pwendell is the idea with (2) that we use a maven version before 3.3.x during releases, and additionally pass in a -Prelease flag or something that enables createReducedDependencyPom?

If so, sounds like the solution is to revert my revert at #7193 and add another profile that has its own maven shade plugin dependency.

Hey @andrewor14 - sorry for the delay I didn't see this comment yesterday. I see - I didn't realize one thing - the maven version being used on jenkins is 3.1.X (that must be why it worked rather than the profiles). This is a little bit unfortunate because it means if we go with solution (2) then we'll need to reason about the version installed on Jenkins and if that gets upgraded things will fail.
What about just doing (1) here and throwing our hands up and seeing if we can convince the maven project to make this fix, so that we can use this feature in the future?

(Why does option 2 not work with later Maven? I missed that part.)

My understanding was this bug affects maven version 3.3 and later. I've never tried publishing the release with Maven 3.3, so I don't know whether we would still just hit this bug when the profile is enabled.

From the discussion I thought it was observed with 3.2 and 3.3, though I wasn't clear it was actually related to the Maven version. But even if so, option 2 should dodge this bug in the shade plugin wherever it occurs right? or will it then somehow make things not-work in older Maven?

Hey sean - option 2 still enables the bug-causing option when we publish releases. So I think this means we may not be able to publish releases with maven 3.2 and 3.2. I'd prefer not to be tied to specific versions for publishing releases since it's a bit brittle. But maybe it would be okay for now.

Got it, I had in my head that somehow the release incantation was not affected by this.
In the spirit of option 1 again then, is SparkFunSuite that essential anyway? it's a short class with one overridden method that logs the test name in the output. Worth considering whether it can just go away.

@srowen SparkFunSuite should stay because it makes the unit-tests.log actually useful, which is instrumental in debugging flaky tests. Unfortunately because many (hundreds) suites currently extend it, it will be difficult to revert the patch that added it in the first place, and I don't think we want to do that because eventually we want to keep it in the long run.
I think the verdict for now is just to go with (2), which adds a special release profile, and if that doesn't work, we'll fallback to (1), which duplicates SparkFunSuite.

OK sounds good. Good point about all of the things extending it. So you're saying option 2, plus, using some version of Maven that doesn't somehow trip on this issue?

Yes, I believe the plan is to restrict ourselves to use a specific version of maven to do releases.

Merged build triggered.

Merged build started.

Test build #36550 has started for   PR 7219 at commit f4c00e0.

@pwendell Please try this out. I have tested this with maven 3.3.3 and 3.2.1 with and without the new -Prelease profile. The results are summarized in the PR description and I have verified this locally.

Hey Andrew,
Can you update the release preparation script https://github.com/apache/spark/blob/master/dev/create-release/create-release.sh#L121 so that it uses the correct profile the two times when it does "mvn install"?

Test build #36550 has finished for   PR 7219 at commit f4c00e0.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

@srowen @pwendell please let me know whether I understood your comments correctly in the latest commit.

Merged build triggered.

Merged build started.

Test build #36556 has started for   PR 7219 at commit 537579a.

I made a minor comment regarding the name. Pending that small update this LGTM

Test build #36556 has finished for   PR 7219 at commit 537579a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Hi guys,
I haven't had the chance to distill the discussion and the changes yet, but I have a suggestion.
What about moving SparkFunSuite to a separate module? That module can depend on scalatest, and it's added to all other modules as a test-scope dependency.
It's not optimal, but I kinda like it better than the more intrusive approach that seems to have been chosen here.

Marcelo - That is not a bad idea. It's not guaranteed it will work because the underlying issue here is that having test-jar dependencies screws up the maven shade plugin, and having a dedicated project would also require test-jar dependencies. However, my guess is that the underlying cause here is there is some corner case given the overall complexity of the dependency graph and it's not taken into account in the maven shade plugin. So maybe this would be simpler and it would just work.
For 1.4.1 I'd probably prefer to go with this approach since it's a bit more conservative (introducing a new build module involves some potential issues, such as making sure it is published correctly, etc). But I think for the master branch we should introduce the new module and see if that works.

the underlying issue here is that having test-jar dependencies screws up the maven shade plugin

But my suggestion does not add a "test-jar" dependency. You'd have a proper module, providing SparkFunSuite, just that it's separate from spark-core. It's just a dependency like any other, that happens to provide test code.

Oh I see - I thought you meant to make it a test-jar dependency. Yeah, this is a good idea.

Ok, I'll see what I can do.

Yeah so it looks like the circular dependencies mean we can't really make good use of a separate build project (because we can never have any code in there that refers to SC). This IMO makes it less valuable. Also, I guess maven shade plugin just solved this issue upstream, so we'll probably get a release soon that we can just upgrade too.
So given all that, I am again inclined to just do this simple fix here, unblock the release, and then simply upgrade to the newer maven shade plugin when it's avaialble, hopefully within a few days.

I have some temporary changes here: https://github.com/apache/spark/compare/apache:master...andrewor14:fix-maven-build-alternative?expand=1
@vanzin and I spoke offline. Because the new test module actually depended on Logging from spark-core, we needed to copy the file to the test module to avoid introducing a circular dependency. The resulting set of changes actually turned out to be quite large, as it changes dependencies across many modules.
I also prefer the simpler fix of introducing a profile that's used only internally. Once MSHADE-148 (which is resolved just 3 hours ago, hoorah!) is packaged into a new release, we can just upgrade our maven plugin version and get rid of the profile. It's a much narrower interface to revert.

I've removed the revert of #7193 from this patch. This will make this patch easier to revert in the future. After this patch is merged we will revert #7193 separately.

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

retest this please

Merged build triggered.

Merged build started.

Test build #36622 has started for   PR 7219 at commit 1d37e87.

LGTM. Hopefully there'll be a release of the plugin soon.

@vanzin thanks for helping with his

Test build #36622 has finished for   PR 7219 at commit 1d37e87.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

retest this please

Merged build triggered.

Merged build started.

Test build #36624 has started for   PR 7219 at commit 1d37e87.

Test build #36624 has finished for   PR 7219 at commit 1d37e87.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

OK, merging into master, 1.4 and 1.3. Thanks everyone for the reviews.

Agree that a separate module is a logically nice fix, but probably does have the circular dependency problem and introduce a whole new module for a few lines of code.
I also saw @pwendell 's message about release-profile having side-effects. Darn. I had hoped side effects of setting up like Maven does for release are helpful, like building javadoc, but I guess the javadoc doesn't build on its own. LGTM


IR of certain deopts cannot be accessed in irhydra2

When I click on any of the red "extend" methods of the following trace, the corresponding IR is not shown but the view still displays the previously selected method:
http://mrale.ph/irhydra/2/#gist:b5a405768d12f49d49e5e3188749de42

Thank you for the report and reproduction! This should now be fixed.
Sorry for somewhat long turn around time - I was on vacation.


Enable caching Python installs also

This cache action works to cache the Python installs:
      - name: Cache UV python installs
        uses: actions/cache@v2
        with:
          path: ~/.local/share/uv/python
          key: ${{ runner.os }}-uv-python-${{ hashFiles('.python-version', 'pyproject.toml') }}

but are you in favor of adding another input to do put the Python installs in the same cache as the dependencies?
E.g.:
function setPythonInstallDirToCacheDir(cacheLocalPath: string): void {
  core.exportVariable("UV_PYTHON_INSTALL_DIR", `${cacheLocalPath}/_python_installs`);
  core.info(`Set UV_PYTHON_INSTALL_DIR to ${cacheLocalPath}/_python_installs`);
}

      - name: Cache UV python installs
        uses: astral-sh/setup-uv@v3
        with:
          enable-cache: true
          cache-python-with-dependencies: true

Thank you for suggesting this. I am looking into it.

@merlinz01 if you are already using that in an existing workflow. Can you share some statistics how much time is saved by also caching the python interpreters vs. always downloading them again?

Sure, once I'm done pulling the 209MB updated docker image for act over my <1MB/s connection :).

This is using act on my local machine. I realize that on a hosted actions runner it might be more efficient not to cache.
When I cache all the dependencies but not the Python install, and the cache exists, my test suite takes 50 seconds.
When I cache both the dependencies and the Python install, and the cache exists, my test suite takes 18 seconds.

I'm always in favor for adding new functionalities if it helps users but otherwise want to keep the codebase as small as possible. So can you help me to understand the usecase a bit better?
On self-hosted runners the python interpreter should be "cached" anyways.
On GitHub hosted (ephemeral) runners the question is if caching is more efficient than downloading it fresh every time.
Did I miss a usecase?

On self-hosted runners the python interpreter should be "cached" anyways. On GitHub hosted (ephemeral) runners the question is if caching is more efficient than downloading it fresh every time.

Correct. The use case this would be targeted at is running jobs locally via the act tool on one's development machine.
To confine this caching to that context, you can specify it like this:
 cache-python-with-dependencies: ${{ env.ACT == 'true' }}


OmniSharp is not getting attached to the buffer

Hello Neelfrost,
Firstly THANK YOU for this awesome well made nvim config i really like it.
I am having an issue with using the config though for Unity Development Omnisharp is not getting attached to the buffer at all i tried a couple of things in the servers lua but to no avail any idea how can i fix that ? i have attached a screenshot

there is sln and the .csproj files that got generated by unity
Thank you!

Firstly THANK YOU for this awesome well made nvim config i really like it.

Glad you liked it :)

I am having an issue with using the config though for Unity Development Omnisharp is not getting attached to the buffer at all i tried a couple of things in the servers lua but to no avail any idea how can i fix that ? i have attached a screenshot

I'll look into it. Omnisharp never worked automatically for me; it took a lot of tweaking to get it to attach to the buffer.

Please check if the lastest commit fixes it on your end!
Make sure to read the updated installation instructions!.


Simple methods

saner refactor o post-processing files
better organisation of info on post processor types
fixed aggregator reduce bug
longhand versions of pct (percentile) and med (median)
@adambraimbridge @laurieboyes

Hey cool


Fix issue #96 "delete of resource".

#96
Deny delete of resource.
Signed-off-by: Achim Kraus<EMAIL_ADDRESS>

Sounds goods.
(But you clearly have a problem with your formatter ;), did you try mvn eclipse:eclipse as explained here?)

No ...
but I will do right now ...

Integrated in master (commit d5ed2fe0e23e711cb3e402940a8187c44d20c14e)


chore(deps): update concerto dependencies

Closes #

Changes

Flags

Screenshots or Video

Related Issues

Issue #
Pull Request #

Author Checklist

[x] Ensure you provide a DCO sign-off for your commits using the --signoff option of git commit.
[ ] Vital features and changes captured in unit and/or integration tests
[ ] Commits messages follow AP format
[ ] Extend the documentation, if necessary
[ ] Merging to main from fork:branchname

coverage: 98.767%. remained the same
when pulling 3e6af180f726c442bf1e4490a0e400f57d03237e on ertugrul/update-concerto
into b385482df5ac36f8a2cfd00f373544837de86c8c on main.


How to implement payload in a Cross-platform App

@evollu Hi, thanks for all the good work on this package it works great.
I have a question about how to handle cross platform apps using react-native-fcm.
So, android needs a payload using custom-notification and ios needs notification, that's all well and good but how do you determine what payload to send at the time of sending? Do I need to keep track of the OS that each user is using? I'm thinking I could have each user update the db with the current OS in use when the app is opened then use that information to send the correct payload.
Or is there another way?

that is what I'm doing. will be happy if there is another way

Ah ok well I'll go ahead with this until something better comes up! Thanks


Publish 4/6/2021 10:30 AM PT

Docs Build status updates of commit e585c5b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2019-ps/configci/New-CIPolicy.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2019-ps/smbshare/Close-SmbOpenFile.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2022-ps/configci/New-CIPolicy.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Cannot build ios

I had no problems with the debug mode, but I cannot build a release because of "bitcode" (or whatever) issues.
At the end of the README there are some suggestions about what to do if we cannot build in iOS.
My own suggestions about that:

I guess you could say at the beginning of the README that there are potential release build problems. I'm in the process of  building a release for iOS, starting from a full Android flutter app version, and it's not that easy to locate where the build problems come from (which package, which feature), especially if the debug mode works OK. Dev on Apple is already a pain in the neck (mandatory use of a Mac computer, mandatory - and irrelevant - connection to a iOS smartphone for the release build, mandatory use of the latest OS for Xcode)
I have more an Android than iOS background, and the point of flutter is for me not to worry too much about the iOS settings details. Therefore, please be explicit in whatever you recommend in your "4. Compiling issues and their fixes" chapter. I have NO intention to learn Xcode and more specifically its build details. And for the record no intention to understand "gradle" either.

Unfortunately today I cannot use your package because I cannot afford to waste too much energy in that iOS nonsense. It would be a valuable, but not an essential feature, for my app.
I hope I'll be able to use this package soon. Thank you and good luck!

I just managed to build my app with this plugin on IOS and managed to upload it. The plugin works well both on Android and iOS with the below setup.
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, v1.17.5, on Mac OS X 10.14.6 18G4032, locale en-GB)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.1)
[✓] Xcode - develop for iOS and macOS (Xcode 11.3)
[✓] Android Studio (version 3.6)
[✓] Connected device (1 available)

• No issues found!

The issues mentioned in the readme are more to do with how xcode and iOS building works than the plugin itself.
The following is what worked for me on iOS

Under Build Settings for the overall project (Runner inside the Project Section), set Enable Bitcode = Yes. For all of the Targets below set Enable Bitcode as No
Under Build Settings for the overall Project and the Runner Target (The first under under the Target section), set Always Embed swift standard libraries = Yes. Set this as NO for the Sharing Extension or any other Extension under Targets

Regarding App Groups
If you follow the Readme, there is a section asking you to add the Share Extension and the Runner Target to the same App Group and it asks you to create an App Group. This is where i had the biggest issue. If you mess this step, the app builds but sharing does not seem to work. In fact nothing happens when you share to your app. Only Sharing Text works, even that just opens the app and does nothing.
Since my app also uses OneSignal for notifications, i already had an App Group so i just added the same to the Share Extension. This does not work. In fact the following steps are needed for it to work

Select the Share Extension from the Target section -> Under Signing & Capabilities -> Click + -> Add App Group. If you already have an App Group added, then simply click on the + Sign below and you would need to name the app group in this format group.YOUR_BUNDLE_IDENTIFIER. eg: group.com.company.app. You can simple copy paste your Bundle Identifier from your Runner target and prefix it with group.
Add the same app group to your Runner Target as well. So in the end you would have the Runner Target and the Sharing Extension Target both have the same app group checked/selected.
You would need to also update ios/Share Extension/ShareViewController.swift file with your Bundle Identifier. You can see the TODO mentioning the same in the code. Update it as let hostAppBundleIdentifier = "INSERT BUNDLE IDENTIFIER" eg let hostAppBundleIdentifier = "com.company.app" the plugin code simply prepends group. to get the App Group Name so having any other group name does not work.

Also for anyone wanting to debug the Extension on XCODE. You would need to click on the Runner select the Sharing Extension and then click Run. When you do that, it will ask you to select an app to run, you need to select your app, it would then build the app and run it as always but you can now set breakpoints on the ShareViewController.swift file and it would stop there when you attempt to share files from a different app. I had reverted the code to the default one to check if the extension even works.

It took a lot of fiddling to find this out as i have very little experience with Xcode and iOS native development. Hope this helps someone.

@mohamedazher Thank you, I'll give it a try when I finally implement this extension.

@mohamedazher thank you! That helped me progress with this issue. One more thing that I needed to do was to set the same iOS Development Target. In my case Runner was set to 13.2 and Extension was set to 14.2. Setting them to the same target allowed me to see my app in Share popup.

For me, to fix the issue "Undefined symbols for architecture armv7" of Share Extension target, when building for real device.

delete Share Extension

modify the podfile:
post_install do |installer|
installer.pods_project.targets.each do |target|
if target.name != "Share Extension"
flutter_additional_ios_build_settings(target)
end
end
end

recreate Share Extension

update info.plist

<key>CFBundleVersion</key>
<string>1.0</string>

For bookkeeping, I had a working Share Extension, and I upgraded flutter and this error started popping. I used @mohamedazher but changed all of them to "NO", and it worked for me. Details here https://stackoverflow.com/a/76080055/2464822


Fail to open dashboard through "open dashboard" in explorer

Right click "open dashboard" and then http://localhost:8001/ui/ is opened in my browser with error message "This website can not be reached".
If I run below command in TERMINAL, I can successfully open the dashboard.
az aks browse -g xxx -n xxx
http://localhost:8001/ui/

@testforstephen , could you please take a look? Thank you.

@bnookala , could you please take a look this issue? I can open the dashboard through az aks browse.

Below is the detail when we run the command "Kubernetes: open dashboard"
command "Kubernetes: open dashboard" get the wrong url

On unbuntu:
after execute the command , open "http://localhost:8001/ui" will redirect to http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/
and get error like below:

Actually ,The right url is http://<IP_ADDRESS>:8001/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy/#!/overview?namespace=default
On mac:
after execute the command open "http://localhost:8001/ui" will redirect to http://<IP_ADDRESS>:8001/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy/
Actually ,The right url is http://<IP_ADDRESS>:8001/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy/#!/overview?namespace=default

Taking a look!

Looking at the implementation of az aks browse it looks like it locates a dashboard pod and does a port-forward to that.  Would that work generically on k8s clusters, and if so should we do that instead of using kubectl proxy or having detection and special handling for AKS?

@itowlson I think there's more going on… I've tried this myself, and the dashboard doesn't completely load when just using a kubectl port-forward. It would be ideal to use the underlying behavior of kubectl proxy, since then we wouldn't have to simulate the behavior of az aks browse within the context of the extension.
However… even if we did choose to detect AKS clusters and use az aks browse, we'd still need to know the name and the resource group of the cluster to invoke the az cli. I don't think this is information that is known to us already since we don't interact with the az cli, so we'd also have to gather that from the user to make the dashboard work.

Weird.  az aks browse doesn't seem to do much more than getting the pod info and doing a kubectl port-forward to that pod; so if that works and the dashboard loads, then I don't see why doing the same thing directly wouldn't work... strange!  Here's the implementation if it's any help...:
https://github.com/Azure/azure-cli/blob/c8edc8b04aa7630da246e5d01cd587c3d836aac5/src/command_modules/azure-cli-acs/azure/cli/command_modules/acs/custom.py#L1254

@itowlson I had an another try to see what kubectl proxy would do on two clusters, and it appears that the localhost:8001/ui redirect is somewhat broken between k8s versions, so maybe I had missed something originally.
AKS 1.8.7: kubectl proxy with a load of localhost:8001/ui in a browser loads http://<IP_ADDRESS>:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/, which promptly fails with this TLS error:
Error: 'tls: oversized record received with length 20527'
Trying to reach: 'https://<IP_ADDRESS>:9090/'

Though hitting http://<IP_ADDRESS>:8001/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy/#!/overview?namespace=default on the same cluster seems to load the dashboard fine.
ACS-Engine with k8s 1.9.3: kubectl proxy with a load of localhost:8001/ui in a browser redirects to
http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/overview?namespace=default, which loads fine, but http://<IP_ADDRESS>:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/ does not.
So… AKS 1.8.7 (latest) will load at http://<IP_ADDRESS>:8001/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy/#!/overview?namespace=default
ACS-Engine w/ k8s 1.9.3 will load at http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/overview?namespace=default
As I'm using kubectl 1.9.5, I think this may have something to do with that. So perhaps port-forward would be the most straightforward route to get to the dashboard. I tried this with AKS, and it works fine. However, port-forwarding the ACS engine pod doesn't seem to work.

holy criminoly, batman.

Ok, after discussion, this will be the course of action:
Detect if the active cluster is AKS, if yes, port-forward to the kube-system dashboard pod, and open a browser to the bound port on localhost. If no: shell out to kubectl proxy, and pray.

OS: Mac&&linux
Build: 4407
For AKS:
Now open dashboard works good with AKS.
For ACS &&local minikube:
open dashboard still open the wrong url

Right click a cluster and choose "Open Dashboard"
Only some info output in the terminal, browse is not open

click the cluster and choose "Open Dashboard" again. A browse is open and the url is  http://<IP_ADDRESS>:8001/ui

if the cluster is ACS the url will redirect to
http://localhost:8001/api/v1/namespaces/kube-system/services/kubernetes-dashboard:/proxy/
The page is blank.
if the cluster is minikube, the url won't redirect. The page shows like below

local cluster can be open correctly with "minikube dashboard"


apt update: E: The repository 'http://download.opensuse.org/repositories/home:/kernc:/xsuspender/xUbuntu_22.04  Release' no longer has a Release file.

When I ran apt update on my Ubuntu 22.04 today, it complained:
E: The repository 'http://download.opensuse.org/repositories/home:/kernc:/xsuspender/xUbuntu_22.04  Release' no longer has a Release file.
This seems to be caused by Open Build Service requiring additional project configurations to select preferred dependencies. See the Monitor page, it says:
have choice for libjpeg-dev needed by libgdk-pixbuf-2.0-dev: libjpeg-dev libjpeg-turbo8-dev, have choice for libjpeg-dev needed by libtiff-dev: libjpeg-dev libjpeg-turbo8-dev

Duplicate of https://github.com/kernc/xsuspender/issues/37 and https://github.com/openSUSE/open-build-service/issues/10773. You should find this resolved now.

Confirmed, works for me, thanks!


Uncaught SyntaxError: Unexpected token ILLEGAL

[Enter steps to reproduce below:]

Drag React Native Project which contains js files and non js files such as Xcode files etc into the Atom Editor's Icon on the Application Menu Bar......
If that doesn't open the project and the folder.  Manually activate atom by clicking on the icon and then open the project like usual. After that try typing.....it won't let u type....a Uncaught SyntaxError warning inside of a Modal Box keeps on popping up......

Atom Version: 1.0.11
System: Mac OS X 10.10.4
Thrown From: Atom Core
Stack Trace
Uncaught SyntaxError: Unexpected token ILLEGAL
At /Applications/Atom.app/Contents/Resources/app.asar/node_modules/text-buffer/lib/text-buffer.js:773

SyntaxError: Unexpected token ILLEGAL
    at /Applications/Atom.app/Contents/Resources/app.asar/node_modules/text-buffer/lib/set-helpers.js:26:31
    at Set.forEach (native)
    at subtractSet (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/text-buffer/lib/set-helpers.js:24:18)
    at Leaf.splice (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/text-buffer/lib/marker-index.js:402:9)
    at Node.splice (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/text-buffer/lib/marker-index.js:154:32)
    at MarkerIndex.module.exports.MarkerIndex.splice (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/text-buffer/lib/marker-index.js:549:38)
    at MarkerStore.module.exports.MarkerStore.splice (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/text-buffer/lib/marker-store.js:194:25)
    at TextBuffer.module.exports.TextBuffer.applyChange (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/text-buffer/lib/text-buffer.js:636:15)
    at TextBuffer.module.exports.TextBuffer.setTextInRange (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/text-buffer/lib/text-buffer.js:553:12)
    at Selection.module.exports.Selection.insertText (/Applications/Atom.app/Contents/Resources/app.asar/src/selection.js:472:43)

Commands

Config
{
  "core": {
    "themes": [
      "one-dark-ui",
      "atom-dark-syntax"
    ]
  },
  "editor": {
    "fontSize": 13,
    "invisibles": {}
  }
}

Installed Packages
# User
highlight-nbsp, v0.1.1
meteor-api, v2.12.0

# Dev
No dev packages

Just faced same issue in Atom 1.7.2 on Ubuntu Linux.
I just wanted to select some text in PHP file.


Feedback email for event and proposal

This email fixes #49 partially if we don't break the issue into smaller ones. If we do, we can close it.

done @jonatasoliveira


feat: supported langs parameter (#538)

1. Description

1.1. Checklist

[ ] The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs: etc).
[ ] I have read the Contributor Guide and followed the process outlined for submitting PRs.
[ ] I have updated/added tests for ALL new/updated/fixed functionality.
[ ] I have updated/added relevant documentation in docs and added dartdoc comments with ///.
[ ] I have updated/added relevant examples in examples.

1.2. Breaking Change

[ ] Yes, this is a breaking change.
[ ] No, this is not a breaking change.

1.3. Related Issues

Codecov Report

Merging #542 (486b4ea) into main (48f2e47) will increase coverage by 15.40%.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@             Coverage Diff             @@
##             main     #542       +/-   ##
===========================================
+ Coverage   68.52%   83.92%   +15.40%
===========================================
  Files         204        6      -198
  Lines        1903      112     -1791
===========================================
- Hits         1304       94     -1210
+ Misses        599       18      -581

see 198 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


FlexVersion created wrong and convert all / to -

-There was a bug where the 'tag' and 'isDirty' booleans were swapped in the constructor
-Convert / to - in all cases of domain picking

How embarrassing. A bug and something I should have done earlier.
@EXBreder
@imawuman

+1


fixes, plus keep message header for REP user-space inspection

Thank you for this useful package. While testing I ran into a few issues. Please, would you take a look at enclosed PR.

I need to break these commits up -- stay tuned.  (Normally I prefer just one issue per PR, unless they are intrinsically linked.)

Actually you can make it much much easier for me to take in your changes.  I prefer to have each "issue" a backed by a separate github Issue -- one issue per commit usually (and never more than one commit per issue!)  And I use a specific form of commit message -- one line like this:
"fixes # "
More detail about the nature of the issue, and how you fixed it, if not in inline comments (rarely appropriate, but sometimes) can be provided in the github issue.
I can of course fix this all up and cherry-pick your commits, but that's a little more work on my end, and you'll still wind up having to rebase/merge.  So better, I think if you do it.
Let me know if you're able to do this.  If not, I'll do it myself for these -- you've certainly uncovered a few problems I want to have fixed!  :-)

Thank you for the reply. I am more than happy to put this into individual issues.
With regard to passing the header on the rep socket, I have been thinking a lot about this -- will respond in the individual commit; please can you have a look?
Otherwise this PR can be closed. Thanks again.


Created Product Card-1

Hey, I have worked on the component specified in the ISSUE #294
Here is the screenshot of the same

Image used in the component : https://images.unsplash.com/photo-1647880087459-30f07c4faba5?ixlib=rb-1.2.1&ixid=MnwxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8&auto=format&fit=crop&w=2232&q=80

Good job @a-u-m
Congrats 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow this steps.

Star this repository. ⭐
SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/) .
Go to profile section from the top right hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard !
And don’t forget to share your achievement with your friends.


Add support for aarch64

Motivation
Fixed the tests issue on aarch64. Previously tests was failing on aarch64 with below error:
[^[[1;31mERROR^[[m] testCompressDecompress(org.apache.pulsar.common.compression.CompressorCodecBackwardCompatTest)  Time elapsed: 0.02 s  <<< FAILURE! java.lang.NoClassDefFoundError: Could not initialize class org.xerial.snappy.Snappy         at org.apache.pulsar.common.compression.CompressionCodecSnappyJNI.decode(CompressionCodecSnappyJNI.java:60)         at org.apache.pulsar.common.compression.CompressorCodecBackwardCompatTest.testCompressDecompress(CompressorCodecBackwardCompatTest.java:66)         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Modifications
Upgrade netty-tcnative to 2.0.33.Final and snappy-java to <IP_ADDRESS> which includes aarch64 support.

/pulsarbot run-failure-checks

Updated snappy-java to <IP_ADDRESS> because snappy-java latest version <IP_ADDRESS> is having some issues with jdk8.That's why previously unit tests were failing.
https://github.com/xerial/snappy-java/issues/247
https://github.com/xerial/snappy-java/issues/251

Hi,
Please have a look into this PR.

Hi,
Please have a look into this PR.
It will be useful if arm64 jobs are added in Travis-CI. If you are interested, I can help by raising another PR for adding arm64 jobs in Travis-CI.

Hi,
Please have a look into this PR.
It will be useful if arm64 jobs are added in Travis-CI. If you are interested, I can help by raising another PR for adding arm64 jobs in Travis-CI.

Thanks for merging.
It will be useful if arm64 jobs are added to Travis-CI. If you are interested, I can help by raising another PR for adding arm64 jobs in Travis-CI.

@odidev After merged this PR, I can't build the source code on my laptop(macos 10.15.7). Here is the problem that I met:
Run mvn clean install -DskipTest on the master branch
Then, the problem appears
[INFO] --- exec-maven-plugin:1.6.0:exec (rename-epoll-library) @ pulsar-broker-shaded ---
----- Renaming epoll lib in /Users/lipenghui/GitHub/pulsar/pulsar-broker-shaded/target/pulsar-broker-shaded.jar ------
checkdir error:  /var/folders/t4/w6thygwj0y596w0j5h_pzlw40000gn/T/tmp.A0pwRE4r/META-INF/license exists but is not directory
                 unable to process META-INF/license/.
checkdir error:  /var/folders/t4/w6thygwj0y596w0j5h_pzlw40000gn/T/tmp.A0pwRE4r/META-INF/license exists but is not directory
                 unable to process META-INF/license/LICENSE.tomcat-native.txt.
checkdir error:  /var/folders/t4/w6thygwj0y596w0j5h_pzlw40000gn/T/tmp.A0pwRE4r/META-INF/license exists but is not directory
                 unable to process META-INF/license/LICENSE.boringssl.txt.
checkdir error:  /var/folders/t4/w6thygwj0y596w0j5h_pzlw40000gn/T/tmp.A0pwRE4r/META-INF/license exists but is not directory
                 unable to process META-INF/license/LICENSE.aix-netbsd.txt.
checkdir error:  /var/folders/t4/w6thygwj0y596w0j5h_pzlw40000gn/T/tmp.A0pwRE4r/META-INF/license exists but is not directory
                 unable to process META-INF/license/LICENSE.mvn-wrapper.txt.
[ERROR] Command execution failed.
org.apache.commons.exec.ExecuteException: Process exited with an error: 2 (Exit value: 2)
    at org.apache.commons.exec.DefaultExecutor.executeInternal (DefaultExecutor.java:404)
    at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:166)
    at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:804)
    at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:751)
    at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:313)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:498)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)

Do you have any idea for fixing this issue? Looks related to the netty related dependency upgrade.

Seems only affect the macos, I tried on ubuntu, it works. And after revert the version of netty-tc-native to 2.0.30.Final also works well on macos.


File name on disk for content

Describe your problem
The name of the file for content is index.txt.
Is there a way to have it named with the title of the post, the way the folder is named?
Steps to reproduce the problem
Bludit version
docker latest - 2020-03-30, but in about it says..

Bludit Edition | Standard - Upgrade to Bludit PRO
Bludit Version | 3.8.1
Bludit Codename | APA
Bludit Build Number | 20190228

PHP version
docker official latest
PHP logs

Hello, with the new version of Bludit v4.0 rc1, I would like to close the old Github issues. If you feel that your issue is not resolved in the latest version, create a new ticket.

Help and Support use the Forum https://forum.bludit.org
Bugs and new requests here in Github https://github.com/bludit/bludit/issues


Internal error (see logs): merge_strict_job exception: Types_js.Key_not_found("SigContextHeap")

Hi,
I have a problem on version 0.23.* and 0.24.* on check.
On each of my files there is the following error:
app/Screen/Component/ReviewButtons.js:1
  1: /* @flow */
     ^ Internal error (see logs): merge_strict_job exception: Types_js.Key_not_found("SigContextHeap",    "/Users/maarek/Documents/projects/netosoft/chevalannonce_mobile/ca/app/BBCode/Templater.js")`

The version 0.22.1 work perfectly.
An idea ?

@maarekj I ran across the same issue and just spent the last 30 minutes back tracing the error to find the cause. In the end, it was due to an external module class (fully flow typed written in ES6 with module.mapper enabled) that had one of its async static methods without any return type. Once i added the return type (Promise), that error disappeared. Hope this helps.

Ok, I need to check any error so.
Thanks You.

I fix the errors.
The main error was related to the dynamic polymorphic type bad bound.
Thank you for your help.

we did a bunch of work around this exception a few months ago and haven't seen any new reports, so I'm gonna close this. but let us know if there's a new repro!

Declaring a module like this causes the exception:
declare module module {
  declare function hot(path: string, callback:() => void): void;
}

This works:
declare module module {
  declare function hot(path: string, callback:void => void): void;
}


[ETFE-2002] Accessibility fixes for date input

Also fixes ETFE-2003 and ETFE-2005

https://github.com/hmrc/emcs-tfe-explain-shortage-excess-frontend/assets/16954819/566fb3bb-c516-4ebd-89b2-4cbff90e8055


Text is not bolded in html tags

For certain reasons i had to manually make my list items with an ol tags and discovered that text bolding doesnt work with it. For example for the mark down :

 **Hello**

results in the list item being surrounded by asteriks instead of bold. Might be the same issue with italics as well though i did not test that

Hey SirKitboard,
Markdown inside of HTML could not be parsed. Please use either Markdown or HTML, but do not mix it.
Correct HTML

One (in italic)

Two

Three (in bold)

Correct Markdown
1.	*One (in italic)*
2.	Two
3.	**Three (in bold)**


Migrate to Rust

RoyalGuard is using 130MB of memory in 33 servers.
Due to my VPS having only 1 GB of memory, switching to a language that is optimized for memory usage is the best call.
RoyalGuard V2 should be a complete rewrite in Rust and this will decrease memory usage as a whole.

This will be an ongoing issue for people to subscribe to

Leftovers:

Add reaction-role auto deletion when all reactions are cleared
Add a restore command for the prefix cache

Restore command resolved by commit 966601301a2425c4f2077fc7c973c20eb6a8e3b2

Rewrite is complete and live! Please let me know if there are errors either in Discord or issues.


Useful aliases and mixins

Never mind. Here few useful aliases and mixins:
alias SolidColorBrush(key, color)
{
  SolidColorBrush Key=$key
  {
    Color: $color
  }
}

alias Thickness(key, left, top, right, bottom)
{
  Thickness Key=$key
  {
    Left: $left
    Top: $top
    Right: $right
    Bottom: $bottom
  }
}

mixin Size(width=none, height=none) for FrameworkElement
{
  Width: $width
  Height: $height
}

Good stuff 👍

@ionoy I'm also curious. How can this (Diploma) could be translated in Ammy?
l:Static is kinda System.Windows.Markup.StaticExtension the implementation of it is here Gu.Localization.

Yeah i was also wondering about StaticExtensions, more specifically this (the OpeningEffectsOffset thing). Is it possible to achieve with AmmyUI currently without having to write XAML syntax?

Just import materialDesign with typeless property:
"xmlns:materialDesign": "clr-namespace: ..."

OpeningEffectsOffset: "{materialDesign:IndexedItemOffsetMultiplier 0:0:0.05}"

or you can do something like this:
<TransitioningContent.OpeningEffectsOffset>
  0:0:0.05
</TransitioningContent.OpeningEffectsOffset>


Auto install ipykernel doesn't work on Codespaces

Create a Codespace from https://github.com/kieferrm/vscode-remote-python
Switch active interpreter to /usr/bin/python3
Install pip with sudo apt update && sudo apt install python3-pip
Open interactive window or notebook and try to run cells
🐛 ipykernel install fails with the following spew:

vscode ➜ /workspaces/vscode-remote-python (main ✗) $ /usr/bin/python3 /home/vscode/.vscode-remote/extensions/ms-python.python-2021.6.944021595/pythonFiles/shell_exec.py /usr/bin/python3 -m pip install -U --force-reinstall ipykernel --user /tmp/tmp-663b0naQ0jTIxQ9.log
Executing command in shell >> /usr/bin/python3 -m pip install -U --force-reinstall ipykernel --user
Collecting ipykernel
  Using cached https://files.pythonhosted.org/packages/b6/4a/b9e7d67637549e1b75c2946e93e35740ea63a521d7d455343e6a8a8a7b91/ipykernel-6.0.1-py3-none-any.whl
Collecting tornado>=4.2 (from ipykernel)
  Using cached https://files.pythonhosted.org/packages/bf/fa/2befee379094720b54065daa9c6117f3edb7d35f86cde0f50b3a28ecfadf/tornado-6.1-cp37-cp37m-manylinux1_x86_64.whl
Collecting jupyter-client (from ipykernel)
  Using cached https://files.pythonhosted.org/packages/88/4e/50fcf8b38d9c08d5b4839c1650e595f6bfa4fc9b419e2b800db8f14ee532/jupyter_client-6.2.0-py3-none-any.whl
Collecting ipython>=7.23.1 (from ipykernel)
  Using cached https://files.pythonhosted.org/packages/f7/b2/733ea4551a04866bbcfbbade4d9d2c82c829cf1cc6fac1ac5974b8c7f756/ipython-7.25.0-py3-none-any.whl
Collecting debugpy>=1.0.0 (from ipykernel)
  Using cached https://files.pythonhosted.org/packages/84/89/bb91c5e3b676721d3a9c13489767b2ec83c7035464e68e8e2fe477ad4566/debugpy-1.3.0-cp37-cp37m-manylinux1_x86_64.whl
Collecting importlib-metadata<4; python_version < "3.8.0" (from ipykernel)
  Using cached https://files.pythonhosted.org/packages/52/d0/bdb31463f2d9ca111e39b268518e9baa3542ef73ca449b711a7b4da69764/importlib_metadata-3.10.1-py3-none-any.whl
Collecting traitlets>=4.1.0 (from ipykernel)
  Using cached https://files.pythonhosted.org/packages/f6/7d/3ecb0ebd0ce8dcdfa7bd47ab85c1d4a521e6770ef283d0824f5804994dfe/traitlets-5.0.5-py3-none-any.whl
Collecting jupyter-core>=4.6.0 (from jupyter-client->ipykernel)
  Using cached https://files.pythonhosted.org/packages/53/40/5af36bffa0af3ac71d3a6fc6709de10e4f6ff7c01745b8bc4715372189c9/jupyter_core-4.7.1-py3-none-any.whl
Collecting python-dateutil>=2.1 (from jupyter-client->ipykernel)
  Using cached https://files.pythonhosted.org/packages/d4/70/d60450c3dd48ef87586924207ae8907090de0b306af2bce5d134d78615cb/python_dateutil-2.8.1-py2.py3-none-any.whl
Collecting nest-asyncio>=1.5 (from jupyter-client->ipykernel)
  Using cached https://files.pythonhosted.org/packages/52/e2/9b37da54e6e9094d2f558ae643d1954a0fa8215dfee4fa261f31c5439796/nest_asyncio-1.5.1-py3-none-any.whl
Collecting pyzmq>=13 (from jupyter-client->ipykernel)
  Using cached https://files.pythonhosted.org/packages/2d/4b/256767441a6c4223fbc7c3eab1b3762d9d70b657899d844228a782f48af3/pyzmq-22.1.0-cp37-cp37m-manylinux1_x86_64.whl
Collecting pickleshare (from ipython>=7.23.1->ipykernel)
  Using cached https://files.pythonhosted.org/packages/9a/41/220f49aaea88bc6fa6cba8d05ecf24676326156c23b991e80b3f2fc24c77/pickleshare-0.7.5-py2.py3-none-any.whl
Collecting matplotlib-inline (from ipython>=7.23.1->ipykernel)
  Using cached https://files.pythonhosted.org/packages/7f/de/6c111d687335729cf8c156394c8d119b0dc3c34b6966ff2a2f7fe4aa79cf/matplotlib_inline-0.1.2-py3-none-any.whl
Collecting setuptools>=18.5 (from ipython>=7.23.1->ipykernel)
  Using cached https://files.pythonhosted.org/packages/a2/e1/902fbc2f61ad6243cd3d57ffa195a9eb123021ec912ec5d811acf54a39f8/setuptools-57.1.0-py3-none-any.whl
Collecting jedi>=0.16 (from ipython>=7.23.1->ipykernel)
  Using cached https://files.pythonhosted.org/packages/f9/36/7aa67ae2663025b49e8426ead0bad983fee1b73f472536e9790655da0277/jedi-0.18.0-py2.py3-none-any.whl
Collecting pygments (from ipython>=7.23.1->ipykernel)
  Using cached https://files.pythonhosted.org/packages/a6/c9/be11fce9810793676017f79ffab3c6cb18575844a6c7b8d4ed92f95de604/Pygments-2.9.0-py3-none-any.whl
Collecting pexpect>4.3; sys_platform != "win32" (from ipython>=7.23.1->ipykernel)
  Using cached https://files.pythonhosted.org/packages/39/7b/88dbb785881c28a102619d46423cb853b46dbccc70d3ac362d99773a78ce/pexpect-4.8.0-py2.py3-none-any.whl
Collecting prompt-toolkit!=3.0.0,!=3.0.1,<3.1.0,>=2.0.0 (from ipython>=7.23.1->ipykernel)
  Using cached https://files.pythonhosted.org/packages/1e/34/1d9880ac1339ad4c6697b330e7a507584105613751318249d9e820faa25f/prompt_toolkit-3.0.19-py3-none-any.whl
Collecting decorator (from ipython>=7.23.1->ipykernel)
  Using cached https://files.pythonhosted.org/packages/6a/36/b1b9bfdf28690ae01d9ca0aa5b0d07cb4448ac65fb91dc7e2d094e3d992f/decorator-5.0.9-py3-none-any.whl
Collecting backcall (from ipython>=7.23.1->ipykernel)
  Using cached https://files.pythonhosted.org/packages/4c/1c/ff6546b6c12603d8dd1070aa3c3d273ad4c07f5771689a7b69a550e8c951/backcall-0.2.0-py2.py3-none-any.whl
Collecting typing-extensions>=3.6.4; python_version < "3.8" (from importlib-metadata<4; python_version < "3.8.0"->ipykernel)
  Using cached https://files.pythonhosted.org/packages/2e/35/6c4fff5ab443b57116cb1aad46421fb719bed2825664e8fe77d66d99bcbc/typing_extensions-<IP_ADDRESS>-py3-none-any.whl
Collecting zipp>=0.5 (from importlib-metadata<4; python_version < "3.8.0"->ipykernel)
  Using cached https://files.pythonhosted.org/packages/92/d9/89f433969fb8dc5b9cbdd4b4deb587720ec1aeb59a020cf15002b9593eef/zipp-3.5.0-py3-none-any.whl
Collecting ipython-genutils (from traitlets>=4.1.0->ipykernel)
  Using cached https://files.pythonhosted.org/packages/fa/bc/9bd3b5c2b4774d5f33b2d544f1460be9df7df2fe42f352135381c347c69a/ipython_genutils-0.2.0-py2.py3-none-any.whl
Collecting six>=1.5 (from python-dateutil>=2.1->jupyter-client->ipykernel)
  Using cached https://files.pythonhosted.org/packages/d9/5a/e7c31adbe875f2abbb91bd84cf2dc52d792b5a01506781dbcf25c91daf11/six-1.16.0-py2.py3-none-any.whl
Collecting parso<0.9.0,>=0.8.0 (from jedi>=0.16->ipython>=7.23.1->ipykernel)
  Using cached https://files.pythonhosted.org/packages/a9/c4/d5476373088c120ffed82f34c74b266ccae31a68d665b837354d4d8dc8be/parso-0.8.2-py2.py3-none-any.whl
Collecting ptyprocess>=0.5 (from pexpect>4.3; sys_platform != "win32"->ipython>=7.23.1->ipykernel)
  Using cached https://files.pythonhosted.org/packages/22/a6/858897256d0deac81a172289110f31629fc4cee19b6f01283303e18c8db3/ptyprocess-0.7.0-py2.py3-none-any.whl
Collecting wcwidth (from prompt-toolkit!=3.0.0,!=3.0.1,<3.1.0,>=2.0.0->ipython>=7.23.1->ipykernel)
  Using cached https://files.pythonhosted.org/packages/59/7c/e39aca596badaf1b78e8f547c807b04dae603a433d3e7a7e04d67f2ef3e5/wcwidth-0.2.5-py2.py3-none-any.whl
Installing collected packages: tornado, ipython-genutils, traitlets, jupyter-core, six, python-dateutil, nest-asyncio, pyzmq, jupyter-client, pickleshare, matplotlib-inline, setuptools, parso, jedi, pygments, ptyprocess, pexpect, wcwidth, prompt-toolkit, decorator, backcall, ipython, debugpy, typing-extensions, zipp, importlib-metadata, ipykernel
Exception:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pip/_internal/cli/base_command.py", line 143, in main
    status = self.run(options, args)
  File "/usr/lib/python3/dist-packages/pip/_internal/commands/install.py", line 386, in run
    use_user_site=options.use_user_site,
  File "/usr/lib/python3/dist-packages/pip/_internal/req/__init__.py", line 49, in install_given_reqs
    **kwargs
  File "/usr/lib/python3/dist-packages/pip/_internal/req/req_install.py", line 760, in install
    use_user_site=use_user_site, pycompile=pycompile,
  File "/usr/lib/python3/dist-packages/pip/_internal/req/req_install.py", line 382, in move_wheel_files
    warn_script_location=warn_script_location,
  File "/usr/lib/python3/dist-packages/pip/_internal/wheel.py", line 215, in move_wheel_files
    prefix=prefix,
  File "/usr/lib/python3/dist-packages/pip/_internal/locations.py", line 165, in distutils_scheme
    i.finalize_options()
  File "/usr/lib/python3.7/distutils/command/install.py", line 274, in finalize_options
    raise DistutilsOptionError("can't combine user with prefix, "
distutils.errors.DistutilsOptionError: can't combine user with prefix, exec_prefix/home, or install_(plat)base
Traceback (most recent call last):
  File "/home/vscode/.vscode-remote/extensions/ms-python.python-2021.6.944021595/pythonFiles/shell_exec.py", line 26, in <module>
    subprocess.check_call(shell_args, stdout=sys.stdout, stderr=sys.stderr)
  File "/usr/lib/python3.7/subprocess.py", line 347, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/bin/python3', '-m', 'pip', 'install', '-U', '--force-reinstall', 'ipykernel', '--user']' returned non-zero exit status 2.

6. Run `/usr/bin/python3 -m pip install ipykernel` and everything works

We're failing to detect installed ipykernel:
Terminal:

Jupyter logs:
Error 2021-07-06 23:55:47: Install Missing Dependencies, Class name = w, completed in 7317ms, has a falsy return value, Return Value: undefined a [Error]: IPyKernel not installed into interpreter Python 3.7.3 64-bit:/usr/bin/python3
    at w.handleKernelDependencyResponse (/home/vscode/.vscode-remote/extensions/ms-toolsai.jupyter-2021.6.999662501/out/client/extension.js:90:244702)
    at w.installMissingDependencies (/home/vscode/.vscode-remote/extensions/ms-toolsai.jupyter-2021.6.999662501/out/client/extension.js:90:244075)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5) {
  category: 'noipykernel',
  reason: 2
}
Error 2021-07-06 23:55:47: Raw session failed to start because dependencies not installed
Info 2021-07-06 23:55:47: Shutdown session -- complete
Error 2021-07-06 23:55:47: Exception attempting to start notebook:  a [Error]: IPyKernel not installed into interpreter Python 3.7.3 64-bit:/usr/bin/python3
    at w.handleKernelDependencyResponse (/home/vscode/.vscode-remote/extensions/ms-toolsai.jupyter-2021.6.999662501/out/client/extension.js:90:244702)
    at w.installMissingDependencies (/home/vscode/.vscode-remote/extensions/ms-toolsai.jupyter-2021.6.999662501/out/client/extension.js:90:244075)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5) {
  category: 'noipykernel',
  reason: 2,
  vslsStack: [ CallSite {}, CallSite {}, CallSite {}, CallSite {} ]
}
Info 2021-07-06 23:55:47: Closing interactive window: Interactive - #1
Error 2021-07-06 23:55:47: DataScience Error a [Error]: IPyKernel not installed into interpreter Python 3.7.3 64-bit:/usr/bin/python3
    at w.handleKernelDependencyResponse (/home/vscode/.vscode-remote/extensions/ms-toolsai.jupyter-2021.6.999662501/out/client/extension.js:90:244702)
    at w.installMissingDependencies (/home/vscode/.vscode-remote/extensions/ms-toolsai.jupyter-2021.6.999662501/out/client/extension.js:90:244075)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5) {
  category: 'noipykernel',
  reason: 2,
  vslsStack: [ CallSite {}, CallSite {}, CallSite {}, CallSite {} ]
}

See also: microsoft/vscode-python#15632 and #5116


Configuration Option: Default open links in new tab

Is your feature request related to a problem? Please describe.
Not
A description of what the problem is. Ex. I'm always frustrated when...
if i want to keep the file list in place, i need to use right click to open the file  in new window,  or keep going history back if i forget the 'open in new window' to open the files
Describe the solution you'd like
add a default configuration in app/configure/app.php to setting the default behavior of open links  in  a new window
A description of what you want to happen.
when i click in a link of the file list, i like to see the file in a new window
Describe alternatives you've considered
A description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Thanks for the suggestion but this is not something we will likely add. Opening a new tab for every link would rapidly clutter the user's browser tabs, especially when navigating to a file or folder several levels deep. This would also prevent the browser's back button from being useful.

NOTE: You can always use one of the following shortcuts to open a link in a new tab.

Middle Mouse
Ctrl + Click
⌘ + Click (on Mac)


Need --cfg=libc_align in v0.3.16 but not v0.3.15; why?

Hi! I transitively use socket2 as part of a Rust project built with
Bazel. I’m noting that socket2 builds successfully for me at v0.3.15,
but not at version v0.3.16 (released today) unless I specify the extra
flag --cfg=libc_align. I’m a bit hesitant to do so because it feels
low-level and platform specific, so I wanted to check and see whether
this is expected or whether there’s a better solution?
Here is a repro repo. You do need to have Bazel to repro, but you
don’t need any additional setup. The error is:
INFO: From Compiling Rust lib socket2 v0.3.16 (7 files):
error[E0063]: missing field `__align` in initializer of `libc::in6_addr`
   --> external/raze__socket2__0_3_16/src/sockaddr.rs:243:25
    |
243 |         let sin6_addr = in6_addr {
    |                         ^^^^^^^^ missing `__align`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0063`.
ERROR: /HOMEDIR/.cache/bazel/_bazel_wchargin/e6b2d93af64d3456b38c9c9d2131e939/external/raze__socket2__0_3_16/BUILD.bazel:33:13: output 'external/raze__socket2__0_3_16/libsocket2--1560485693.rlib' was not created
ERROR: /HOMEDIR/.cache/bazel/_bazel_wchargin/e6b2d93af64d3456b38c9c9d2131e939/external/raze__socket2__0_3_16/BUILD.bazel:33:13: not all outputs were created or valid
Target @raze__socket2__0_3_16//:socket2 failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 0.707s, Critical Path: 0.20s
INFO: 2 processes: 1 internal, 1 linux-sandbox.
FAILED: Build did NOT complete successfully

I dug far enough into the libc structure to see the align/no_align
modules and guess that this cfg flag would probably fix it; it does.
The failing Bazel action, with directory structure and command line
invocation, is here (in a Gist because it has some long paths):
https://gist.github.com/wchargin/4da947cf43d2a241cfffb89873788a82
In all cases, the libc dependency is at version 0.2.80. But I note
that socket2 v0.3.15 depends on libc with default features, whereas
in v0.3.16 it depends on the align feature:
$ cargo tree -e features --manifest-path socket2-0.3.15/Cargo.toml
socket2-libc-align-demo v0.0.0 (/HOMEDIR/git/socket2-libc-align-demo/socket2-0.3.15)
└── socket2 feature "default"
    └── socket2 v0.3.15
        ├── cfg-if feature "default"
        │   └── cfg-if v0.1.10
        └── libc feature "default"
            ├── libc v0.2.80
            └── libc feature "std"
                └── libc v0.2.80
$ cargo tree -e features --manifest-path socket2-0.3.16-default/Cargo.toml
socket2-libc-align-demo v0.0.0 (/HOMEDIR/git/socket2-libc-align-demo/socket2-0.3.16-default)
└── socket2 feature "default"
    └── socket2 v0.3.16
        ├── cfg-if feature "default"
        │   └── cfg-if v0.1.10
        ├── libc feature "align"
        │   └── libc v0.2.80
        └── libc feature "default"
            ├── libc v0.2.80
            └── libc feature "std"
                └── libc v0.2.80
$ cargo tree -e features --manifest-path socket2-0.3.16-libc-align/Cargo.toml
socket2-libc-align-demo v0.0.0 (/HOMEDIR/git/socket2-libc-align-demo/socket2-0.3.16-libc-align)
└── socket2 feature "default"
    └── socket2 v0.3.16
        ├── cfg-if feature "default"
        │   └── cfg-if v0.1.10
        ├── libc feature "align"
        │   └── libc v0.2.80
        └── libc feature "default"
            ├── libc v0.2.80
            └── libc feature "std"
                └── libc v0.2.80

So I’m hoping that you can help me understand what caused this change,
why it requires me to build with --cfg=libc_align, (maybe) why it’s
needed with Bazel but not with Cargo (though I understand if that’s
outside your purview/expertise), and whether I should feel comfortable
doing so? I want to build for non-Linux platforms, too, eventually.
I’m on rustc 1.47.0 (18bf6b4f0 2020-10-07) on Debian-like Linux.
Thanks much!

This was done in https://github.com/rust-lang/socket2-rs/pull/120, maybe @faern can elaborate why it's needed a bit.

It is very strange that you get this on rustc 1.47.0. According to the libc build script it should automatically activate libc_align when you compile it on rustc 1.25 or newer: https://github.com/rust-lang/libc/blob/master/build.rs#L56-L59
And also having socket2 activate the feature should also make the need for the __align field go away.
I have never used Bazel. Maybe it does not support features or build scripts enough?

Or maybe it simply does not parse the build script output of cargo:rustc-cfg=libc_align!? That would make kind of sense since the line includes cargo:. But then again, would not almost everything break if it did not support those? :O

Ah! Thank you, thank you. Indeed, it can pass cfg=... outputs from
build.rs, but only if you specify gen_buildrs = true (by design, to
make it explicit where the build isn’t necessarily hermetic), and
I hadn’t done so for this crate. Silly of me; sorry for the trouble, and
thanks for the pointer. :-)