samples: update tcp-echo and helloworld, add ARM64 support

Fixes https://github.com/istio/istio/issues/49947

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
e206eb046bd0a2d2cf6fab4a2249be43f9083c98
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
7de2665e30784bb548437f449efc794a60d15dcb
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


[6/6] Arm(R) Ethos(TM)-U NPU codegen integration with tvmc

This PR integrates the codegen for Arm® Ethos™-U with tvmc.

Add an ethos-u target
Adds test coverage for the new target

This PR is blocked on merging #8795 , #8806, #8811 and #8849. Since this is built on top of all those PR branches, this contains the accumulation of contents of the all the PRs.
Co-authored-by: Manupa Karunaratne @manupa-arm
cc @manupa-arm @Mousius @grant-arm @gromero @areusch @mbaret  @u99127 for reviews

CI is now green, and all the dependency patches are now merged. Can we merge this, when possible?

Thanks everyone, this is merged.


Adding Edit option to journals

Description:
Currently, users can create and view their movie journals on the platform, but there is no option for users to edit their existing journals. To improve user experience and flexibility, we need to implement an "Edit" feature for journals, allowing users to modify their entries after they've been created.
Steps:

Add "Edit" button for each journal entry in the UI.
[ ] Create an "Edit Journal" modal
[ ] Implement backend API to handle journal updates.
[ ] Ensure data validation for updated journal entries.
[ ] Test the flow from editing to saving changes.

** Current Application **
https://github.com/user-attachments/assets/1cb42f20-bf75-47f8-879e-b1817e4d87ff
Expected Outcome:
Users should be able to edit their movie journals and see the updated version reflected in their list of journals. This feature should enhance the user experience by allowing more flexibility in managing their journal entries.

@sid0000007 sir you closed my issue marking duplicate but I can't find any related issue to editing the added journal. Can you please elaborate.


Default clonedUniforms  user's settings.uniforms ❓

https://github.com/vaneenige/phenomenon/blob/master/src/index.js#L363
instanceSettings.uniforms = Object.assign(settings.uniforms, clonedUniforms);

Seem like The User settings.uniforms is not work, because It will be cover

I've looked at the issue and it seems to work as intended, but I've tweaked it a little! In the piece of code below this.uniforms are those from the renderer that are passed to the instance. Those values will be assigned to the provided settings.uniforms or otherwise to an empty object.
instanceSettings.uniforms = Object.assign(
  settings.uniforms || {},
  JSON.parse(JSON.stringify(this.uniforms)),
);

Have a look at the updated demo! Every instance there has its own progress uniform.


Add support for edge labels to follow edges

Unless I am mistaken, it is currently not possible to have edge labels follow the edge they are attached to. Unfortunately, using the builtin rotate function causes diagram  to become very confused leading to spacing issues.
#import "@preview/fletcher:0.4.3" as fletcher: diagram, node, edge

#diagram(
  debug: 3, node((0, 0), "A"), node((0, 1), "B"), edge(
    (-1, 0), (-1, 1), "->", rotate(-90deg)[Some complicated flow], label-side: right,
  ), node((0, 3), "C"), node((1, 4), "D"), edge(
    (0, 3), (1, 4), "->", rotate(45deg)[Some complicated flow], label-side: right,
  ),
)

Try using rotate(reflow: true)?

Ah it was right there in the typst documentation! Much appreciated! It is getting there but still doesn't work properly for the 45deg label
#import "@preview/fletcher:0.4.3" as fletcher: diagram, node, edge
#set page(width: 270pt, height: 320pt)

#diagram(
  debug: 3, node((0, 0), "A"), node((0, 1), "B"), edge(
    (-1, 0), (-1, 1), "->", rotate(-90deg, reflow: true)[Some complicated flow], label-side: right,
  ), node((0, 3), "C"), node((2, 5), "D"), edge(
    (0, 3), (2, 5), "->", rotate(45deg, reflow: true)[Some complicated flow], label-side: left,
  ),
)

I think this behavior should be by default in fletcher, maybe eventually leading to "text along path" functionality like in latex. What do you think?

Yeah, that looks wrong - and worse I can't seem to fix it by playing around. Since this is so hard, automatic rotation of labels along (straight) edges would be a good feature to add.

This has been added in 7ba5655!


hi，please provide your data in this paper,thanks

hi，please provide your data in this paper,thanks

Hi,
You can find the MIMIC dataset via https://archive.physionet.org/mimic2/, the VDem dataset via https://www.v-dem.net/data/dataset-archive/country-year-v-dem-fullothers-v11/, the MNIST dataset via https://yann.lecun.com/exdb/mnist/, and the CUB dataset via https://www.vision.caltech.edu/datasets/cub_200_2011/. The preprocess for MNIST and CUB follows https://github.com/pietrobarbiero/logic_explained_networks/tree/Experments?tab=readme-ov-file

and please inform me that what version your pytorch_lightning is?thanks!
twy
@.***

------------------ 原始邮件 ------------------
发件人:                                                                                "Yanci87/LR-XFL"                                                                                @.>;
发送时间: 2024年8月12日(星期一) 下午4:11
@.>;
<EMAIL_ADDRESS>主题: Re: [Yanci87/LR-XFL] hi，please provide your data in this paper,thanks (Issue #1)
Hi,
You can find the MIMIC dataset via https://archive.physionet.org/mimic2/, the VDem dataset via https://www.v-dem.net/data/dataset-archive/country-year-v-dem-fullothers-v11/, the MNIST dataset via https://yann.lecun.com/exdb/mnist/, and the CUB dataset via https://www.vision.caltech.edu/datasets/cub_200_2011/. The preprocess for MNIST and CUB follows https://github.com/pietrobarbiero/logic_explained_networks/tree/Experments?tab=readme-ov-file
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

The pytorch-lightning version is 1.7.7

sorry for bothering you:I am a student ,and I cannot have the acess to MIMIC dataset ,please provide me with that, I promised to use it just for learning FL,I will be very grateful if you can give me this dataset,thanks!
twy
@.***

------------------ 原始邮件 ------------------
发件人:                                                                                "Yanci87/LR-XFL"                                                                                @.>;
发送时间: 2024年8月12日(星期一) 下午4:11
@.>;
<EMAIL_ADDRESS>主题: Re: [Yanci87/LR-XFL] hi，please provide your data in this paper,thanks (Issue #1)
Hi,
You can find the MIMIC dataset via https://archive.physionet.org/mimic2/, the VDem dataset via https://www.v-dem.net/data/dataset-archive/country-year-v-dem-fullothers-v11/, the MNIST dataset via https://yann.lecun.com/exdb/mnist/, and the CUB dataset via https://www.vision.caltech.edu/datasets/cub_200_2011/. The preprocess for MNIST and CUB follows https://github.com/pietrobarbiero/logic_explained_networks/tree/Experments?tab=readme-ov-file
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


Multiple Set speed limit calls when holding mouse button while changing speed limit

Description
Speed limits tool - multiple set speed limit of lane calls if user holds mouse button while changing speed limit.
Noticeable only in debug build log.
Reproduction Steps
Add more steps as nessecary.

Open speed limits tool
Select any speed limit
Try to change speed limit of lane by 'click and hold' mouse button.

The longer you hold mouse button the more updates will be triggered.
Mod List
Please list the mods enabled when you noticed the bug.

TM:PE [STABLE]

Output Log

Log fragment
[Debug] @<PHONE_NUMBER> SpeedLimitManager: Setting speed limit of lane 138206 to 40
[Debug] @<PHONE_NUMBER> SpeedLimitManager: Setting speed limit of lane 95423 to 40
[Debug] @<PHONE_NUMBER> SpeedLimitManager: Setting speed limit of lane 138206 to 40
[Debug] @<PHONE_NUMBER> SpeedLimitManager: Setting speed limit of lane 95423 to 40
[Debug] @<PHONE_NUMBER> SpeedLimitManager: Setting speed limit of lane 138206 to 40
[Debug] @<PHONE_NUMBER> SpeedLimitManager: Setting speed limit of lane 95423 to 40
[Debug] @<PHONE_NUMBER> SpeedLimitManager: Setting speed limit of lane 138206 to 40
[Debug] @<PHONE_NUMBER> SpeedLimitManager: Setting speed limit of lane 95423 to 40
[Debug] @<PHONE_NUMBER> SpeedLimitManager: Setting speed limit of lane 138206 to 40
[Debug] @<PHONE_NUMBER> SpeedLimitManager: Setting speed limit of lane 95423 to 40
[Debug] @<PHONE_NUMBER> SpeedLimitManager: Setting speed limit of lane 138206 to 40
[Debug] @<PHONE_NUMBER> SpeedLimitManager: Setting speed limit of lane 95423 to 40
[Debug] @<PHONE_NUMBER> SpeedLimitManager: Setting speed limit of lane 138206 to 40
[Debug] @<PHONE_NUMBER> SpeedLimitManager: Setting speed limit of lane 95423 to 40
[Debug] @<PHONE_NUMBER> SpeedLimitManager: Setting speed limit of lane 138206 to 40
[Debug] @<PHONE_NUMBER> SpeedLimitManager: Setting speed limit of lane 95423 to 40
[Debug] @<PHONE_NUMBER> SpeedLimitManager: Setting speed limit of lane 138206 to 40
[Debug] @<PHONE_NUMBER> SpeedLimitManager: Setting speed limit of lane 95423 to 40
[Debug] @<PHONE_NUMBER> SpeedLimitManager: Setting speed limit of lane 138206 to 40
[Debug] @<PHONE_NUMBER> SpeedLimitManager: Setting speed limit of lane 95423 to 40
[Debug] @<PHONE_NUMBER> SpeedLimitManager: Setting speed limit of lane 138206 to 40
[Debug] @<PHONE_NUMBER> SpeedLimitManager: Setting speed limit of lane 95423 to 40

Is this something to do with the fact that it's designed to allow "dragging" a speed down a road? I think that feature was added about a year or two ago prior to some shortcuts being added for similar effect.

We can probably improve this by not setting and not logging if the value is already the same. For this we need to propagate success boolean from the deepest setSpeedLimit function.

btw: Does the code check if new speed is different to current speed before taking any action?

Just been reading the old wiki, which states:

To apply the selected speed limit to multiple (nearby) road segments, hold the mouse button down and then move it over the road segments you want to apply the speed limit to.

So it's definitely a "feature" rather than a "bug".

It should not log "changed speed limit" if it was actually set to the same value. Then it will work as intended.

Could we also despam it based on either mouse move delta or skip every n frames?

This feature was removed by #709


add hp monitors for disk controller/cache/battery

The current HP hardware monitors only cover cpu/dimm/disk.
This commit adds status monitoring via hpssacli for
controller/cache/battery status too
Fixes: #407

lgtm
:+1:

:+1: looks good to me as well


[stable/superset] init_superset.sh initfile is no longer run.

Describe the bug
Since the entrypoint / args was changed from init_superset.sh to use gunicorn (c56f4d4ad95917b6736c25cd9120944e85a83d18) I cannot see any evidence that ini_superset.sh is being run.
I deployed the helm chart and the superset app ran fine and is accessible via the host address, but the user does not exist.
Checking the k8s logs there is no output from the superset init script.
Version of Helm and Kubernetes:
Helm 2.14.3 / 2.14.3
Kubernetes 1.16 / 1.14
Which chart:
stable/superset
What happened:
Using helm install I installed the chart (with host address changed) and I can access the superset app but cannot login. gunicorn is running fine.
If I shell onto the pod and run the init script (init_superset.sh) then the account / db is created and I can log in.
What you expected to happen:
The app should be running and the username and password that are specified in the initFile config should be created to log in with.
How to reproduce it (as minimally and precisely as possible):
Change the hosts address and helm install the chart. Try to log in with the default admin/admin account.
Anything else we need to know:
I have since reverted the entrypoint / args to the init_superset.sh script and replaced the superset run line in initFile to be:
/usr/bin/env python /usr/local/bin/gunicorn -b <IP_ADDRESS>:8088 --limit-request-line 0 --limit-request-field_size 0 superset:app
And this is initialising / creating the user and running as expected.

Is there any way to get traction on this? Do you want a pull request?

Well I did configure a workaround that works for me, but I am not sure it is fit for production as the idempotency element that I also added to work with already configured pvc's is not best practice. So I don't want to submit it as a solution.

Ok, I can work with the existing chart (Adding extra config for extra ingresses and network policies outside), except that I need to control the start up of superset. So I basically just want this particular bug fixed. I fixed it like this:
diff --git a/stable/superset/templates/deployment.yaml b/stable/superset/templates/deployment.yaml
index c10422918..c632102ed 100644
--- a/stable/superset/templates/deployment.yaml
+++ b/stable/superset/templates/deployment.yaml
@@ -49,8 +49,12 @@ spec:
         - name: {{ .Chart.Name }}
           image: "{{ .Values.image.repository }}:{{ .Values.image.tag }}"
           imagePullPolicy: {{ .Values.image.pullPolicy }}
-          command: ["/usr/bin/env"]
-          args: ["python", "/usr/local/bin/gunicorn", "-b", "<IP_ADDRESS>:8088", "--limit-request-line", "0", "--limit-request-field_size", "0", "superset:app"]
+          command: ["/bin/bash"]
+          args:
+          - /home/superset/init_superset.sh
+          {{- range .Values.extraArguments }}
+          - {{ . }}
+          {{- end }}
           volumeMounts:
             - name: superset-configs
               mountPath: /home/superset


resinOS as an OS base for IoT

Hi there,
Sorry if this is not the right place to do this kind of questions. Is it possible (or has sense) to build a resinOS to create a base OS for IoT devices? To create images like for example RancherOS.
This base image would not necessary needs to connect to resin services (I have seen in the doc this would be possible), you just have a base OS which is really good about running docker containers. Because, I can see that you are maybe one of the most advanced people about running containers in many devices. I am finding a lot of difficulties using RancherOS in the Intel Edison, or even Raspberry, but you seem to support many many devices.

Hi @jgato . We do indeed have a mechanism to build images for people who only want to run docker on their target. In this direction we define a variable called RESIN_CONNECTABLE. Based on this variable, the image created by Yocto will contain resin specific bits or will be a plain yocto image which will only be intended to run docker. You can as well preload a docker image with some additional variables. The entire documentation is available here: https://github.com/resin-os/meta-resin/blob/master/README.md#resin_connectable--0 .
Regards,
Andrei

I'm closing this issue as it seems to be resolved. If you have any further questions please feel free to start a new topic at https://forums.resin.io where we will be happy to help you with any problems you might have. Thanks!


about jedispool

hi.i want to ask you how i can check the jedispool current status just like current link/current idle link ,and so on.

@cifeng101 JedisPool internally uses commons-pool from apache which exposes a lot of information about the pool through JMX. If you attach any JMX client to your JVM you'll be able to see the pool internal status.
JedisPool also provides some methods to get some basic statistics about the pool such as:
getNumActive
getNumIdle
getNumWaiters


Unsure how to tell when graph is locked to a repository

Testing #229375
I noticed when I selected a specific repository for the SCM graph that the repository name next to the book icon changed, but that the branch icon still had the text "auto" next to it. Is there some indicator for when I have the SCM graph set to a specific repository versus when I have it set to auto?

Thanks for the feedback. I agree that the two pickers render differently when they are in "auto" mode.


Fabric Gateway SDKs v1.1 release

https://github.com/hyperledger/fabric-gateway/releases/tag/v1.1.0


iOS SDK 4.3.0

'queueLoadItems:startIndex:playPosition:repeatMode:customData:' is deprecated: Use queueLoadItems:withOptions:
Method "queueLoadItems:withOptions:" doesn't exist.

The queueLoadItems:withOptions: is available in the Cast SDK 4.3.1 or later.
For more information please refer this documentation : https://developers.google.com/cast/docs/reference/ios/interface_g_c_k_remote_media_client.html#ada70798e3291a532e8ad27d94e8f8218


[Fatal] [JDA]: One of the EventListeners had an uncaught exception

Cannot get my simple ping bot to work~
getting the following errors
[21:55:03] [Fatal] [JDA]: One of the EventListeners had an uncaught exception [21:55:03] [Fatal] [JDA]: Encountered an exception: java.lang.NullPointerException 	at Commands.PingCommand.action(PingCommand.java:19) 	at Bot1.handleCommand(Bot1.java:41) 	at BotListener.onMessageReceived(BotListener.java:13) 	at net.dv8tion.jda.hooks.ListenerAdapter.onEvent(ListenerAdapter.java:176) 	at net.dv8tion.jda.hooks.InterfacedEventManager.handle(InterfacedEventManager.java:57) 	at net.dv8tion.jda.handle.MessageReceivedHandler.handleInternally(MessageReceivedHandler.java:65) 	at net.dv8tion.jda.handle.SocketHandler.handle(SocketHandler.java:36) 	at net.dv8tion.jda.requests.WebSocketClient.handleEvent(WebSocketClient.java:545) 	at net.dv8tion.jda.requests.WebSocketClient.onTextMessage(WebSocketClient.java:296) 	at com.neovisionaries.ws.client.ListenerManager.callOnTextMessage(ListenerManager.java:352) 	at com.neovisionaries.ws.client.ReadingThread.callOnTextMessage(ReadingThread.java:233) 	at com.neovisionaries.ws.client.ReadingThread.callOnTextMessage(ReadingThread.java:211) 	at com.neovisionaries.ws.client.ReadingThread.handleTextFrame(ReadingThread.java:910) 	at com.neovisionaries.ws.client.ReadingThread.handleFrame(ReadingThread.java:693) 	at com.neovisionaries.ws.client.ReadingThread.main(ReadingThread.java:102) 	at com.neovisionaries.ws.client.ReadingThread.run(ReadingThread.java:61)

The null pointer exception is in your own code. Can you upload that class to hastebin? I don't think this is a JDA issue.

Yeah, this doesn't look to be a JDA issue. provide the PingCommand class on http://hastebin.com please.

http://hastebin.com/uhotuxawom.java

In the code you shared, line 19 is blank
Also, MessageReceivedEvent#getTextChannel() can be null if the message was a Direct/Private message

sorry, re-ran it and now it's saying line 16 rather than 19

That will throw a NPE whenever the bot gets a private message

@jagrosh what's the fix then?

If you take a look at the docs, you'll see the TextChannel extends Channel, which represents a Guild channel. MessageReceivedEvent is for both Guild and Private messages. You need to either use the MessageReceivedEvent#getPrivate() boolean to determine if you need getTextChannel() or getPrivateChannel(), or use the MessageChannel interface returned from MessageReceivedEvent#getChannel()

thanks. the bot responds correctly when pinged from the server but not private messages.

Considering that this was an error in your own code, would you mind closing this issue?

Also, if you have more questions, this channel will be an excellent resource: https://discord.gg/0SBTUU1wZTUgGuC8


Add a note on what "deprecation" means in the spec

For a separate PR: Might be good to have a note on deprecation in the spec itself. Something like:

DEPRECATED - A "deprecated" entity or metadata field SHOULD NOT be used in the generation of new datasets. It remains in the standard in order to preserve the interpretability of existing datasets. Validating software SHOULD warn when deprecated practices are detected and provide a suggestion for updating the dataset to preserve the curator's intent.

Originally posted by @effigies in https://github.com/bids-standard/bids-specification/pull/605#discussion_r490236412

#508 and #424 use the term "legacy" for suffixes that fit this description. Should that be replaced with "deprecated"?

Well, I think "DEPRECATED" only appears once. I think we could just as easily go with "LEGACY".

Deprecation has a more standardized meaning though, right? In BEP001 it looks like "legacy" is actually used as a precursor to "deprecation", which is a nuance I missed when I initially responded. That said, I don't think it's a distinction worth making since deprecation means that the element will be removed at a later date, not that it has been removed. As such, I'm not sure that have a pre-deprecation term (i.e., legacy) buys us anything. WDYT?

As such, I'm not sure that have a pre-deprecation term (i.e., legacy) buys us anything. WDYT?

+1, no sense in a pre-deprecation term --> either we fully support something or we tell people to please not use it anymore (but keep it for backward compatibility)
regarding "legacy" vs. "deprecation", I like deprecation better, but I am not going to die on that hill :-) I think Chris' definition from the original post is nice and should be used.

That works for me. I'm happy to update #424 and comment on #508 about switching to "deprecation" once there's a merged PR.

That works for me. I'm happy to update #424 and comment on #508 about switching to "deprecation" once there's a merged PR.

thanks!

Sounds good to move forward with "deprecated". Looking at our current case, though, I'm unclear on what suggestion a validator should be making.

(Deprecated) Manufacturer’s designation of the software of the device that created this Hardcopy Image (the printer). Corresponds to DICOM Tag 0018, 101A Hardcopy Device Software Version

Neither "hardcopy" nor "printer" show up elsewhere. It may just be that it didn't seem meaningful. I think to be explicit, we should add "There is no recommended alternative for this DEPRECATED key." so validator writers don't waste their time.

I think to be explicit, we should add "There is no recommended alternative for this DEPRECATED key." so validator writers don't waste their time.

I agree. I also think we should clarify at the initial definition that deprecated items will be removed at the next major release (i.e., BIDS 2.0), just so users know that it's not happening at the next patch or minor release.


The client only sends a REFRESH message when sending data

In the 1.0.1 ROS, the server stops sending messages to clients with expired tokens.(default time for that is 10 min).
However, the cocoa binding only sends a refresh token when it wants to send some data.
That means it will stop receiving data after the access token expires until it will try to send new data.
Currently the server does not send any message to indicate that the client will not be receiving any data.
We will have to revert the fix in the ROS 1.0.1 until the clients can handle it.
cc @austinzheng @jpsim

I thought this was fixed? Upon receiving the refresh token, the binding and object store immediately forwards it to sync. However, I have noticed that the server does not seem to receive the token until the client attempts to transfer data, so it may be an issue with how sync decides to schedule sending up the token.

You are right, this looks a bug in realm-sync. I'll open an issue.

Great, thanks ❤! Sorry for not reporting the sync issue earlier; I wasn't sure if it was intended behavior or not.


gerented bounding volume(region) has reversed dimension and direction

https://github.com/PrincessGod/objTo3d-tiles/blob/0e0d32fa3a8cca0a07bd782945cc333690f433e8/lib/obj2Tileset.js#L31
the indice of Height and Y are wrong.
Line 31 should be minmaxPoint.max[1] - minmaxPoint.min[1];
Line 35 should be var offsetY = height / 2 + minmaxPoint.min[1];
Line 40, 41 should be minmaxPoint.min[2]  and minmaxPoint.max[2]
https://github.com/PrincessGod/objTo3d-tiles/blob/0e0d32fa3a8cca0a07bd782945cc333690f433e8/lib/createSingleTileset.js#L62
Line 62 should be + offsetY / tileHeight * latitudeExtent;
Line 64 should be + offsetY / tileHeight * latitudeExtent; (use plus sign instead of minus sign)

My output seems to be tilted 90 degrees on the roll axis.
I tried your patch but it seems it did not make a difference.

it works well, thanks


Consider dropping support for call_actor_id

Every actor has double the amount of methods it should have, as it offers both call_actor (address) and call_actor_id variants. Consider dropping the call_actor_id variants entirely. On the EVM runtime side, call_actor_id simply wraps the ID in an f0 address. Instead, we should offer the user a FilecoinAddress conversion method as part of #241, so that users wanting to call an actor by ActorID can do (pseudocode):
uint64 actorID = 123;
FilecoinAddress idAddr = Addressing.fromActorID(actorID);
MinerAPI.doTheThing(idAddr, ...);

:link: zboto Link

Please check convo in Slack for the latest direction!


Update pytest arguments

Currently,

pytest-xdist is installed but not leveraged
test output is verbose for all tests, making it excessively long and difficult to parse

https://docs.pytest.org/en/8.0.x/how-to/output.html

#263 would be nice to get in before this

Unblocked by #263, but currently CI is failing for reasons that are likely on MolSSI's side. Given that xdist might cause its own concurrency issues, let's wait until we get green CI on main to test+merge this.


feat(args): spacekey is specified through args

changes

change spacekey to an optional variable. i think i must've accidentally changed things accidentally to make it not optional even though it should.

If omitted, then it'll just use the user's id as the space key

This change is

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Implement cluster sync for manual Chart release actions

Problem
When a Chart release is deleted/created/upgraded manually, the cluster gets out of sync with the prescribed state defined in the get repo.
A/C
When a manual Chart release change (delete/create/upgrade) is performed, the cluster  is synced back to the prescribed state defined in the get repo.

Implementation
Helm operator regularly checks the state of the cluster:

compares FluxHelmRelease resource information describing the desired state of a Chart release, with the corresponding Chart release. Makes a new release if the current one diverged from the prescribed state
finds redundant Chart releases and purges them
detects missing Chart releases and installs them

There are several ways for ascertaining whether a current Chart release satisfies the prescribed desired state.

Comparing values and Chart information of the existing Chart release with a dry run based on the associated FluxHelmRelease resource

Pros:
Compares relevant parts of the release data to provide a definitive answer

Cons:
Some Helm applications may create random values for certain fields. If these fields are not overridden, this way of comparison does not work, because each release creates a different value. This is the case with some Helm databases and their passwords.
Possible solution
Make it mandatory that the user overrides parameters that have random values by default.

Comparing last updated dates of a FluxHelmRelease resource and its Chart release counterpart
(selected solution)

Pros:
Works for any Helm application

Cons:
There may be possibly a lag between the FluxHelmRelease resource change and the subsequent Chart release. The lag can only be determined empirically, ie there may be edge cases where the lag may exceed the expected threshold with the result of a redundant Chart release.
This may not need to be of concern. Looking at the respective dates in Minikube, the FluxHelmRelease resource update triggers the Chart release immediately. This needs be tested in a remote cloud with a realistic amount of Helm applications to confirm. However it would seem the lag is unlikely to be big enough to cause problems.

Examples:
A) Kibana
FluxHelmRelease Event info
Name:             kibana.151f7bf88efcd192
Namespace:        default
First Timestamp:  2018-03-26T13:38:26Z
Involved Object:
API Version:       helm.integrations.flux.weave.works
Kind:              FluxHelmRelease
Name:              kibana
Namespace:         default
Resource Version:  209180
UID:               9c1af72c-30f8-11e8-8f3d-080027661afa
Kind:                Event
Last Timestamp:      2018-03-26T13:38:26Z
Message:             Chart managed by FluxHelmRelease processed successfully
Reason:                ChartSynced
Source:
Component:  helm-operator
Type:         Normal
Events:
.....
Chart release
helm list |grep kibana
NAME            	REVISION	UPDATED                 	STATUS  	CHART         	NAMESPACE
my-kibana       	1       	Mon Mar 26 14:38:26 2018	DEPLOYED	kibana-0.2.2  	default

b) mongodb
FluxHelmRelease Event info
13:56:36.490896       5 event.go:218] Event(v1.ObjectReference{Kind:"FluxHelmRelease", Namespace:"default", Name:"mongodb", UID:"9c1dbf0d-30f8-11e8-8f3d-080027661afa", APIVersion:"helm.integrations.flux.weave.works", ResourceVersion:"209865", FieldPath:""}): type: 'Normal' reason: 'ChartSynced' Chart managed by FluxHelmRelease processed successfully
Chart release
helm list |grep mongo
mongodb-database	4       	Mon Mar 26 14:56:36 2018	DEPLOYED	mongodb-0.4.25	default

Issues with triggering of Chart release updates (due to prior manual release)
A) Criteria for detecting a manual Chart release change
There are currently two criteria considered for making a decision whether there a manual Chart release occurred or not. Pros and cons of each approach are given in the comment above (Implementation thoughts)

Comparing values and Chart release info of a currently installed Chart and one created through a dry run release based on its currently deployed Custom Resource

Comparing last deploy date of a Custom Resource and that of its Chart release counterpart

B) Triggering a Chart release upgrade
There are two ways to trigger a release reinstallation:

Directly through the Helm client API
Through Custom Resource deployment (by fluxd) with the associated k8s event triggering a Chart release upgrade (in helm-operator)

Discussion
When using A.1 (comparing release contents), B.1 (release installation through helm client API) is the most straightforward and easy approach to upgrade a release.
Initially, not to impose the need to override randomised values, I opted for A.2 (date comparison) and B.1 (release installation through helm client API), but came across the hurdle of multiple Chart releases.
Using A.2, ie using deploy dates comparison to detect the need to sync:

Using Helm client API leads to repeated Chart releases after a manual release is detected because the Custom Resource deploy time stays the same (until a user change and a subsequent commit). To prevent this the CR deploy date needs to be brought up to date with :
Possible solutions:

Patching the Custom resource to trigger the release upgrade, then patch again to remove the change not to have to commit to the git repo:

Add annotation, then remove it:

when new commits are detected by fluxd and the manifest of this CR is applied, it may still trigger a new Chart release (?)

Committing the manifest change to the git repo -> the commit will trigger fluxd syncing

Triggering Chart release through deploying an updated Custom Resource:

Add an annotation to the CR with the last sync time:

needs committing the manifest change to the git repo -> the commit will trigger fluxd syncing

Conclusion
Depending on CD deploy date for detecting manual release changes requires bringing the CR deploy time up to date with the Chart release upgrade time. This requires changing the CR and possibly committing its changed manifest to the repo. The commit will trigger fluxd syncing.
I now think that A.1 (comparing release contents) as a means of detecting manual Chart release changes is a preferable choice. The requirement to provide an override value for parameters with randomised defaults is, I believe now, not a great deal as these parameters will be in most, if not all cases, passwords, so would be overridden anyway.


"delta_actions" key in the embeddings dataset

Hi!
I am wondering what "delta_actions" key means? This key for sure exists in the pouring_parsed_with_embeddings_moco_conv5.pkl file.

Hi,
Thank you for your question. The "delta_actions" key gives the robot action in delta joint angles instead of absolute joint angles. This benefits some reinforcement learning algorithms according to our experience. It contains equivalent information as the "actions" key. Hope this helps and let us know if you have additional questions!

Thanx for clarifications!


Bump Approx disk size to 400 Gb

400 should be enough for now: https://github.com/bitcoin/bitcoin/blame/v0.21.0rc2/src/chainparams.cpp#L108

@Sjors done

ACK 2868084

My current blocks dir is 332GB. I think 400gb is enough for now but that number should bump soon again.
It's a bad experience if people buy disk space according to this number then figure "weeks" later out that its not enough to sync further (without prune).

@jonasschnelli I think it's fine.  The variable is used with this text on the Download page:

Bitcoin Core requires a one-time download of about 300GB of data plus a further 5-10GB per month. By default, you will need to store all of that data, but if you enable pruning, you can store as little as 6GB total without sacrificing any security. For more information about setting up Bitcoin Core, please read the full node guide.

ACK 2868084e467bb08fd644dd43586ebb5485516f41


SQL CLR Create Assembly Error: BouncycastleCrypto is malformed or not a pure .NET assembly.

Is it possible to use the library in SQL CLR? The SQL server supports pure .NET assemblies but does not support mixed mode

Bouncy Castle is not mixed-mode


Relax pyvista requirement upper bound

Allow all pyvista versions <1 to be used. This is required for compatibility
with ansys-fluent-visualization, which depends on >=0.39.0.

Note: this is not required to go into the 0.2 release.


feat: Update sdk-core

:tada: This PR is included in version 1.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


nip46 get_public_key responds with an npub instead of a hex pubkey

Current result:
{"error":null,"id":"3728bb79-cfce-490b-b21f-84cdffcc456a","result":"npub1cadgmfjpqhdyhjh0g7dv95h3m0jer76z0qv6s2pu534v2rdf8afq2ayp62"}

Expected result:
{"id":"3728bb79-cfce-490b-b21f-84cdffcc456a","result":"c75a8da64105da4bcaef479ac2d2f1dbe591fb427819a8283ca46ac50da93f52"}

Fixed by 923670c827316b95e7bd046bfe2b3669f2abd3b8


[T4A4][T16-B2]ZhaoDingfan

Ready for review.

@ZhaoDingfan Good effort. Some comments added. Please close the PR after reading comments.


DataPaper: Add field/information on terms for data paper publication

e.g. does data have to be publicly available or just metadata + "request by author"
attn @dorianps

Hi @yarikoptic ,
Is the question for me or the maintainers of the repo?


findUniqueOrFail / findFirstOrFail

Problem
Sometimes you query an object from database and require it to exist.
Suggested solution
Two new methods:findUniqueOrFail and findFirstOrFail.
If no object is found, an error will be thrown.
Alternatives
Right now, I see myself often writing code such as:
// Return type is Machine | null
const machine = await prisma.machine.findUnique({
  where: {
    id: gameServer.machineId,
  },
})

if (machine === null) {
  throw new Error('Machine not found.')
}

With the suggested solution the code would just be
// Return type is Machine
const machine = await prisma.machine.findUniqueOrFail({
  where: {
    id: gameServer.machineId,
  },
})

Maybe an alternate name can be findOneOrThrow since Throw is more explicit than Fail.

I took the naming from TypeORM, but it can definitely be changed to be more explicit.
If findOne is renamed to findUnique (see #3697), names should obviously be also changed to findUniqueOrFail / findUniqueOrThrow.

Closing as this has been implemented using the rejectOnNotFound: true option on findFirst and findUnique.


Updated Developer Guide Design Segment

Coverage remained the same at 85.391% when pulling db6ea755b0349d1527cb47e08b4583ba6b7fa475 on awarenessxz:v1.3_Developer_Guide into 00a61e06f5520370f2a66e4994f51d15a91328e5 on CS2103AUG2017-W14-B2:master.


Allow relative symlinks

At the moment my relative symlinks are converted to absolute symlinks what using TarGz, this breaks the code I'm archiving.

relative symlinks are converted to absolute symlinks

That's what I thought at first too, but it turns out that symlink support hadn't been implemented at all. The absolute path is the original source path, not the target path.


Unable to use live server

Sublime text shows the live server command palette but does not do anything if I hit start or stop.
I am on mac and new to programming, so I could not clean up the npm audit. If I even need to.

Did you set up the plugin according to the documentation? https://github.com/molnarmark/sublime-live-server#-settings

Tried it by myself, but what do you mean by setting it up. The default settings should work out of the box, shouldnt they?

The default settings indeed work, but only on Linux. Any other OS, you need to change the settings.

Did you set up the plugin according to the documentation? https://github.com/molnarmark/sublime-live-server#-settings

yea i did. but on live server start and stop, it don't do anything but on live server open in browser it displays: live server isnt running. nothing to open
I dont know what to do...

For Windows:
{
  "node_executable_path": "C:/Program Files/nodejs/node",
  "global_node_modules_path": "C:/Users/User/AppData/Roaming/npm/node_modules"
}

/User/ is your user name.

No offense, but this thing is a bit of a trainwreck, it doesn't run, but says it's 'running' per problems above even with correct dirs, but the thing that makes it bad software is it outputs no debug information on failure to the console, just silently not working but pretending it is. I got a python script to solve the same function of starting a server working in sublime as a plugin in about 5 min to replace this.

@kyle-wendling Great, so use that instead.

@frostphex The comment was directed at the person I tagged (User "kyle-wendling"), who since then deleted the comment. :)
He complained that he made a package in 10 minutes which was in every way better than this one, so I told him to complain about the original npm package at its repository, as this plugin is just a wrapper around it.
It's not directed at people who come here with decent mannerisms asking for guideance about the package. :)

Okay, Okay, firstly I would like to apologize as I didn't read you have tagged a username as I have joined Github last month, and it was the other guy who you tagged. I assumed you are pissed off because of multiple people facing the same issue about the extension not working, and I thought how could this be that you are not helping, because my laptop specs are very weak which doesn't support VScode. I don't know what that guy commented about making it in 10 minutes, I read the first 5-6 comments, and saw that they're from 2022 and got concerned that where are the 2024 comments and thought it's over, but saw you've replied to the issue on Sept 15 last month.
I downloaded sublime-text for continuing my journey of web dev from the odin project, and I wanted an extension similar to live server which has 40M+ downloads on VSCode not the microsoft or other one. Furthermore, I installed your one from the package repository, and it was not working. The problem was my node_modules were not in /usr/local/lib but in /usr/lib while the extension is working fine, but there are problems I would like to bring to your notice.
I've to start and stop the server multiple times and have to select open in browser for different html files. It's kinda tiring.
 And you are kinda cute though!

@frostphex Of course, its understandable.
The "Open in browser" feature (if you mean the one where you right click on the file in the sidebar) is not part of this plugin. That is provided by a different plugin (maybe this) or built into Sublime Text by default, I honestly don't remember.
If you launch the server, you should be able to access the files in the browser by navigating to localhost:8080, or whatever port you've set up in the settings.
Yes, some people had problems, most (as far as I know, ~59.000 installs so far) were able to get things going.
It's just really hard to help others if you don't experience/can't reproduce the issue they are having.

It's working fine, same as the VSCode extension! Thank you for making this one, but if I may ask, why didn't you update this extension from 2021?
I'm new to open source and all web development, I'm seeing many packages in the sublime text which are not updated since 2018/2019 and similar, why is it so? Is it because these packages are stable and don't require further updates or they've abandoned (the authors who made it) and moved to VSCode?

For windows, i had to run these. also opened a pull req.
note that in the file paths, backslash has to escaped with another backslash


generator-star should ignore transpiled async/await functions

getting this error:
Expected no space before *  generator-star

instead, this rule should somehow be ignored with transpiled async/await functions

Should babel-eslint patch actual eslint rules?

Certainly not. It's way too risky as they change so much and it'd mostly require replacing the entire rule. I'm not sure if this specific issue can be addressed since you have to turn await expressions into something and the likely equivalent is a yield.

Yeah agree. Although I guess people will ask since

I can speak for myself here: we aren't implementing experimental features. If you need such support in ESLint, you can use babel-eslint.

I guess we'll just close for now?

would be great if there were a "known rule conflicts" list in the readme so i know just to not use this rule when using babel. no biggie.

@jonathanong That sounds like a good idea. I already made a comment about using the react plugin for jsx issues. Would you like to make a PR to start the list?

Instead of patching eslint rules, what about a babel plugin that adds comments to disable the rule for that expression (/*eslint-disable generator-star*/)?

:+1: for @matthewwithanm comment

@jonathanong Ok I added the rule to the Known Issues section of the readme.
Unless I'm misunderstanding how it would work, I don't get how the plugin would help with the errors? The babel plugin would transform your generated file to have the comments while the source file wouldn't  have them - and eslint is usually run on the source file itself?

Just notifying people here that there's now a https://github.com/babel/eslint-plugin-babel - will try to reimplement rules as a plugin (similar to eslint-plugin-react). I will add a note in the readme about it.

@hzoo Awesome, thanks!

Apparently, this still happens even with babel/generator-star-spacing when you do static async myFunc() { for example. Will investigate and follow-up in the appropriate repo.


Feature: Add ARM Support

Add ARM support
Optional: if/when MacOS is supported, also verify on Apple ARM (M1 chip etc)

test mac silicon build
dolphin-memory-engine.tar.gz

Not planned, but others are free to add it in a PR


Rpi 4 - memLayout returns empty array

First things first: AWSOME lib.
Describe the bug
When calling si.memLayout() on my Raspberry Pi 4, I get an empty array as the return value.
On macOs it works as expected, returning info about the installed memory banks.
According to the docs, this feature should be available on Linux systems. That's why I submit this report.
To Reproduce
Steps to reproduce the behavior:

Call si.memLayout()
si.memLayout().then(res => console.log(res));
run the code
See output/error '....'

Current Output
[]
Expected behavior
Should see information about installed memory modules:
e.g response:
[    {       "size":"***",       "bank":"BANK 0",       "type":"LPDDR3",       "clockSpeed":2133,       "formFactor":"",       "manufacturer":"Micron Technology Inc.",       "partNum":"***",       "serialNum":"-",       "voltageConfigured":-1,       "voltageMin":-1,       "voltageMax":-1    },    {       "size":8589934592,       "bank":"BANK 1",       "type":"LPDDR3",       "clockSpeed":2133,       "formFactor":"",       "manufacturer":"Micron Technology Inc.",       "partNum":"***",       "serialNum":"-",       "voltageConfigured":-1,       "voltageMin":-1,       "voltageMax":-1    } ]
Environment (please complete the following information):

OS:
Rasbian Buster
Kernel: 4.19.97-v7l+
Release 10

Hardware:
BCM2835 - Pi 4 Model B
c03111 - Rev. 1.1

@jeth318 let me check it tomorrow. If this is reproducible also on my machines I will find a quick solution for this. If not, I probably will come back to you for further information. Hope this is ok for you.

@jeth318 ok, as dmidecode does not work on Raspberries, I am considering another method. Please give me one or two days ... will figure it out ;-)

Great! Let me know if there are any more examples you need.

@jeth318 so I just released a new version 4.22.1. Maybe you can give it a try and post results here.

Great!! I’ll try it out soon.

@sebhildebrandt It works like a charm. Thanks for the quick patch!

@jeth318 can you provide a sample output, just to see if we are getting the expected values ;-)
Thank you in advance.

Here is a sample output when calling memLayout().
[   {     size:<PHONE_NUMBER>,     bank: '',     type: 'LPDDR4',     clockSpeed: 3200,     formFactor: 'SoC',     partNum: '',     serialNum: '',     voltageConfigured: -1,     voltageMin: -1,     voltageMax: -1   } ]

@jeth318 So as voltage was missing, I made a fix for that. Version 4.22.2 just published.

@jeth318 ... the rest is not really determinable as there is no bank, no serial and part number for the RAM.

That's perfectly fine! Really nice. Thanks again for fixing the support.


automation: provide PR template

Signed-off-by: Miguel Duarte Barroso<EMAIL_ADDRESS>

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 54.268%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
871

Relevant Lines:
1605

💛  - Coveralls


All actions for not backed up snaphot are shown in VM sidebar, no icon for Create Template action

All actions are available for snapshot with error, allocated,  status. Action for Create Template has no icon for snapshot with Backed Up status.
Steps:

Login and go to VM
Attach data disk to this VM
Create few snapshots - one by one
Go to VM sidebar/Storage and see actions
Open View All

Actual result: All actions are available for not backed up snapshot. Action for Create Template has no icon for snapshot with Backed Up status.
Expected result: Only Delete action are available for not backed up snapshot. Action for Create Template has icon for snapshot with Backed Up status.

@tamazlykar no feature ID provided. Please, check out features involved in this issue.

Feature ID:
vm_disk_snap_display

Also there is no tool-tip assigned to this actions. Need to fix

TBD in #1049

@Nadya913 please check whether the problem is solved on the master branch.

@tamazlykar please fix 2nd problem (1st was fixed in #1049)

Tested on tamazlykar/990-snapshot-actions/


Playing songs with spotify connect

It is currently not possible to start playing a different song when another is already playing when using Spotify connect; instead it must first be added to the song queue and the currently playing song skipped.
My apologies if this has already been pointed out.

This is a bug in librespot that's since been fixed but we are still shipping the old, bugger verison. I need to update librespot. Thanks for the reminder.

I fixed this on my MusicBox like this...
ssh<EMAIL_ADDRESS>[default pw is musicbox]

curl -sSL https://dtcooper.github.io/raspotify/key.asc | sudo apt-key add -v -
echo 'deb https://dtcooper.github.io/raspotify jessie main' | sudo tee /etc/apt/sources.list.d/raspotify.list
apt-get update
apt-get -y install raspotify
rm /opt/librespot/librespot
ln -s /usr/bin/librespot /opt/librespot/librespot
reboot

My workaround for this is to click the connect to device button on PC, choose this computer, start playing the song you want, then switch back to the device. ("listening on MusicBox") However when I get some time I'll probably use @fiid 's solution, thanks!

I fixed this on my MusicBox like this... commands in terminal...
ssh<EMAIL_ADDRESS>[default pw is musicbox]

curl -sSL https://dtcooper.github.io/raspotify/key.asc | sudo apt-key add -v -
echo 'deb https://dtcooper.github.io/raspotify jessie main' | sudo tee /etc/apt/sources.list.d/raspotify.list
apt-get update
apt-get -y install raspotify
rm /opt/librespot/librespot
ln -s /usr/bin/librespot /opt/librespot/librespot
reboot

hero!

I fixed this on my MusicBox like this... commands in terminal...
ssh<EMAIL_ADDRESS>[default pw is musicbox]

curl -sSL https://dtcooper.github.io/raspotify/key.asc | sudo apt-key add -v -
echo 'deb https://dtcooper.github.io/raspotify jessie main' | sudo tee /etc/apt/sources.list.d/raspotify.list
apt-get update
apt-get -y install raspotify
rm /opt/librespot/librespot
ln -s /usr/bin/librespot /opt/librespot/librespot
reboot

Thank you very much, it worked for me also :))

Glad it's working!!  👍
Note you can re-run the two apt-get commands to upgrade raspotify if anything gets funky in the future.

I am having trouble with spotify connect where the player appears in list but spotify cannot connect. Is this fix still working? I noticed that some sources are 404'ing now although raspotify installs OK.
Anyone able to help? Thanks!

I fixed this on my MusicBox like this... commands in terminal...
ssh<EMAIL_ADDRESS>[default pw is musicbox]

curl -sSL https://dtcooper.github.io/raspotify/key.asc | sudo apt-key add -v -
echo 'deb https://dtcooper.github.io/raspotify jessie main' | sudo tee /etc/apt/sources.list.d/raspotify.list
apt-get update
apt-get -y install raspotify
rm /opt/librespot/librespot
ln -s /usr/bin/librespot /opt/librespot/librespot
reboot

Worked for me, absolute saviour.


Add LTO Network coins logo

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

[x] Filename in the lowercase format
[x] Image format: png
[x] Image size: 256 by 256 px

Consider adding LTC coin to Wallet Core https://developer.trustwallet.com/wallet-core


fix typo

..

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


Update circe-core, circe-literal, ... to 0.14.7

About this PR
📦 Updates

io.circe:circe-core
io.circe:circe-literal
io.circe:circe-parser

from 0.13.0 to 0.14.7
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.circe" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "io.circe" }
}]

labels: library-update, early-semver-major, semver-spec-minor, version-scheme:early-semver, commit-count:1

Superseded by #138.


Bump Go and gimme versions

Poke @BanzaiMan.

Please update the specs, too.

@AlekSi please update https://github.com/travis-ci/travis-build/blob/master/spec/build/script/go_spec.rb

@BanzaiMan @msoap Done.

See #1148.


Cleanup Build Artifacts from Binary Codegen

There is some terrible clutter with the current system.

Removed codegen in favor of relocating to LM project.


[MAS4.1.2][Name, Role and Value-Debug] Incorrect role is defined for the chat boxes.

Actual Result:
The chat boxes are defined in the list but they are not accessible by up/down arrow key whereas they are accessible by tab only, due to tab access on each chat boxes the user will not be able to reach "New Message" button.
Expected Result:
The chat boxes should be accessible by up and down arrow and on pressing tab from chat box the focus should jump on "New Message" button.
Repro Steps:

Open the Bot Framework V4 Emulator.
Welcome tab screen gets opened.
Navigate to the "Open Bot" button and activate it.
Open a Bot Dialog box gets opened.
Navigate to the "bot URL" edit box and enter URL- http://localhost:3979/api/messages
Enter "Microsoft App ID and Microsoft App Password". As well as check debug mode.
Navigate to "Connect" button and activate it.
"Debug" separate window appears.
Copy the "/INSPECT attach ” and paste it in M.S. Teams opened from "Azure Portal"
Chat with the created bot, the chat's done on "MS Teams" are appeared on the "Debug" screen.
Navigate to the chat boxes and observe the issue.

User Impact:
Keyboard user will have to use "Tab" key again and again, if the chat list have more data.
As well as to reach to the next item i.e. "JSON", the user must be go through all the chat.
More over the AT user will not be able to activate or use the functionality of "New Message" button.
Note:
Same issue observed on "Live chat" screen.
Observation:
"New Message" button can be accessed by mouse. Moreover if it can be accessed by any predefined "Shortcut keys" it will be beneficial for the user.
Test Environment:
OS: Ubuntu 18.04.3 LTS
Application: BotFramework-Emulator-4.5.2-linux
Impacted MAS Link:
https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={54f28d1f-a2d1-4dcd-84e1-5c9b87e8aba4}
Attachment:
Incorrect role is defined for the chat boxes.zip

@corinagum @compulim This would have to be fixed at the Web Chat level and is not a Linux-specific issue.
The problem is that the "New messages" button on Web Chat to scroll down to the bottom is not easily accessible via keyboard. By the time you use tab to navigate to where it would be in the DOM, you are already at the bottom of the messages panel, which causes the button to disappear.
The only way you can access it currently is via mouse, or by putting focus into the send box, and then using shift-tab to go out of the send box, to the button.

@tonyanziano agreed. I'm a little sad that I overlooked this. I'm going to transfer this over to Web Chat for tracking. Thanks for the heads up.

@ShikhaMishra11, @awalia13, what role should the transcript be changed to do allow for up/down arrow navigation?

@tonyanziano Though the role is correct in code which is list item ideally element should be accessible through up\down arrow key but we are not able to access the element through up/down arrow , they are only accessible through tab key. Due to the use of tab we are not be able to use the functionality of "New Messages" button.
It is beneficial if the user reaches the first chat elements with Tab then navigate to them via arrow keys. On pressing next tab the focus should lands on the "New Message" button. By this implementation the user will able to use each and every functionality of the application.

@awalia13 so if the role is correct, what behavior needs to be corrected here? My plan is to add an access key that will return focus to the send box, with an aria-live region that will announce the presence of the button and shortcut when it shows up.
I'm also seeing the transcript as navigable via arrows when in scan mode. Is it true that the arrows need to be enabled for non-scan mode as well?

@corinagum We took the SME opinion on this issue. According to him, "The focus should go to each item of the list via up/down arrow keys. This is the expectation in order to avoid the navigation flaws".
As well as i agree with you to implement the shortcut key to access the "New Message" button.

Thank you! Just one more clarification: should up/down arrows work in non-scan mode? I am confused on this point.

@corinagum  - It should work in both modes Scan/Non-Scan mode.

@awalia13 I believe there are two problems that are being addressed in this issue.

Up/down arrows in AT mode should navigate up and down the transcript
New Messages button is not reachable via keyboard

Right now, my question is only regarding:

Up/down arrows in AT mode should navigate up and down the transcript

To summarize the issue with problem 1 above, currently in Web Chat AT focus does not navigate from the send box (bottom input) to inside the transcript. This makes it difficult for keyboard users to individually access different activities in the transcript, and to review the conversation.
I have been having trouble finding a fix for this. However, I believe this is an Edge problem, not a Web Chat problem.
Please see attached for my sample index.html, which I have tested in Chrome x Narrator (a) and Edge Anaheim x Narrator (b).
1978.zip

I am able to navigate through the transcript using up and down arrows in Web Chat, using Narrator x Chrome
When I open the index.html file in (a), I am able to navigate through the different DOM objects using up and down arrows
I am NOT able to navigate using up and down arrows in Edge x Narrator using Web Chat, nor in the index.html

For the following error, can we mark the following as an Edge problem?

Up/down arrows in AT mode should navigate up and down the transcript

Please note: I will continue working on the following regardless of outcome of the above.

New Messages button is not reachable via keyboard

I am happy to schedule a call to go over this in real time to discuss questions / solutions.

@corinagum As per previous comments. The bug is fixed for the online bot emulator but our issue are still repro for "Bot Emulator Framework" application.
The chats should be accessible by up/down arrow in all mode (Keyboard and Screen reader). For reference you can have a look on "MS Teams or Skype".
For the second issue i.e. 'New Message', it sounds good to have a shortcut key to reach them but it should also be accessible by tab as if the new user will use the application who is not aware of shortcut keys. He also be able to access the "New Message" button.

Thank you for the help.
After looking into this problem more closely, I recall that each activity being clickable is by design. Since every activity can be accessed in the log panel, it is necessary for the user to be able to iterate through all of them. This means that after the fix, the user will still be tabbing from the activity they search all the way to the sendbox. This behavior is different from Web Chat, but is also intentional.
The accesskey will be announced when a new message arrives, and allow the user to move to the bottom. Rather than focusing on the New Message button, it will focus on the sendbox.

As per above comment I am closing the bug.


Support Bundle Capability

Problem
As someone who supports other users of Liquibase, I would like to make it easier to collect diagnostic data from a user who is experiencing a problem. As it stands today, I must ask the user to collect several pieces of data. This can be a very manual, time-consuming and error-prone effort for the user which results in delays in resolving the user's problem.
Ideal outcomes
We would like to make it easy for users to collect this data and provide it to the people who are supporting their usage of Liquibase. This would ideally be a command line argument that can be passed to any command to collect diagnostic data for that command.  e.g.g  liquibase --support <command>
Data Included

Liquibase Version
Liquibase Integration & Version
Liquibase Extension(s) & Version
Database Vendor & Version
Operating System Type & Version
Liquibase log output with highly verbose logs
A redacted form of the Liquibase properties
The recent history of Liquibase commands and their arguments
The most recent stdout and stderr
Any additional diagnostic data that may be useful to debugging a particular issue or command.

Anonymization

The data should be anonymized so that any confidential data is redacted.
It should be possible to provide a "stop word" list, perhaps as a file. This would allow the user to anonymize additioonal tokens which may happen to appear in the data collected.

Archive file

The data should be collected into a single compressed archive so it easy to move around and upload.
The archive should have a timestamp in the filename so that users can see which files were generated when even when they are passed between remote systems. This makes it easy for participants to verify they have the correct file when there are multiple files being passed around.
eg. liquibase-support-2022-02-27-1310.zip

Other Considerations

The data collected should be both human-readable and machine-readable (perhaps  so that tools can be built to automatically parse and diagnose common problems.
It should be possible for extensions to contribute additional diagnostic data to the bundle.

Thanks @recampbell !

This is great guys,
Here are a few questions:
@recampbell @kataggart

You mention "As someone who supports Liquibase users" Does this mean anyone? Is this for the support team? Internal Liquibase employees? Or will users/License Holders also be able to access this function?

What Liquibase Edition/Product will this be available in? Community, Pro, Hub, Enterprise?

"which results in delays in resolving the user's problem." Can we quantify the average delay to measure impact? On average, would this be hours, days, or weeks lost?

Ideal outcomes: Would it be correct to say that the Value of this command would be that:
A. It allows customers, internal support teams, to diagnose Liquibase Problems?
B. It allows Liquibase's support team to reduce the time spent on Support for our users to seconds vs days by automating and simplifying the error/problem diagnosis process?

Regarding the command name itself, I would recommend using Diagnose or supportdiagnosis and not "support", support could imply that they would receive support somehow and cause confusion.
Let me know your thoughts here.
Thx!
n.

@NileeBadillo keep the feedback coming; as you know, we are coordinating the implementation of this internally via the team


Crash occurs sometimes on audioPlayerDidFinishPlaying

I have found crash on Crashlytics that says audioPlayerDidFinishPlaying(player:entryId:stopReason:progress:duration:). The issue occurs sometime. Can you help me how to fix this issue.

Can you share the symbolicated crash log from Crashlytics?

Sorry for late replay. This is the text log from crashlytics.
Crashed: com.apple.main-thread
0  MyApp                           0x73428 specializedQuesAudioPlayer.audioPlayerDidFinishPlaying(player:entryId:stopReason:progress:duration:) + 163 (QuesAudioPlayer.swift:163)
1  AudioStreaming                 0x11978 $s14AudioStreaming0A6PlayerC20processFinishPlaying33_58F85687851C4E0621A9958C10937433LL5entry4withyAA0A5EntryCSg_AJtFyAJ_SbtcfU0_yycfU_ + 208
2  AudioStreaming                 0x19940 $sIeg_IeyB_TR + 28
3  libdispatch.dylib              0x26a8 _dispatch_call_block_and_release + 32
4  libdispatch.dylib              0x4300 _dispatch_client_callout + 20
5  libdispatch.dylib              0x12998 _dispatch_main_queue_drain + 984
6  libdispatch.dylib              0x125b0 _dispatch_main_queue_callback_4CF + 44
7  CoreFoundation                 0x3720c CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE + 16
8  CoreFoundation                 0x33f18 __CFRunLoopRun + 1996
9  CoreFoundation                 0x33668 CFRunLoopRunSpecific + 608
10 GraphicsServices               0x35ec GSEventRunModal + 164
11 UIKitCore                      0x22c2b4 -[UIApplication _run] + 888
12 UIKitCore                      0x22b8f0 UIApplicationMain + 340
13 UIKitCore                      0x4559c8 __swift_destroy_boxed_opaque_existential_1Tm + 12220
14 MyApp                           0x7d2a0 main +<PHONE_NUMBER> (AppDelegate.swift:4367028896)
15 ???                            0x1d3512dcc (Missing)

Seems the crash occurs on QuesAudioPlayer in line 163 which should be on audioPlayerDidFinishPlaying method, have a look at what might go wrong there


openapi3 emitter should issue diagnostic for optional path parameter

The OpenAPI v3 specification requires path parameters to be required: true. link to spec.
The openapi3 emitter does not check for this and thus can produce an OpenAPI 3 definition that does not conform to the spec.
The openapi3 emitter should issue a diagnostic for a path parameter that is not required.

Are you testing this with the latest changes,

Playground
Fix in https://github.com/microsoft/cadl/issues/672

A path parameter cannot be optional even if you specify a default value.  The above error goes away by adding a default value but that leaves the path parameter optional, which is not allowed by the OpenAPI spec.

Playground

I guess iam not sure if then we should allow optional with default value in rest lib as well. Default being a server default it doesn’t make much sense for building the path?

At the very least, this should be enforced by openapi3 and cadl-autorest emitters.  I think the likely intention here is to make the path parameter optional for generated clients, which the client-side defaults issue should take care of, the underlying property should still be required.
We may want to add this as a linting rule to the cadl-rest


Izzy's Sequence Diagrams for ASv2

Describe interactions between stakeholders in different scenarios (ex. onboarding, account revocation, escrow) in notion doc

@isabellewei:

[ ] Complete ticket body to reflect work

@isabellewei during sprint planning:

will show these to Mariano tomorrow (Thursday)

@isabellewei during sprint planning:

will go through them again for final review


Fix: Info button bug

Description
This PR resolves the issue Ting found here.
Linked Issue(s)

common-samples/issues/3603

How To Test
Tap on the accessory buttons next to the sample titles to confirm that the app doesn't crash.

I'll add Phil to take a look.


upgrade to angular 4

Hi, Thanks for this awesome solution. Is there any chance to have angular 4 version of this repo?
Thanks

I would also love it

Well, if someone can start a PR why not :)
It shouldn't be that difficult


fix: Add certs to argocli image. Fixes #2129

Checklist:

[x] Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
[x] The title of the PR is (a) conventional, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
[x] I have written unit and/or e2e tests for my change. PRs without these are unlike to be merged.
[x] Optional. I've added My organization is added to the README.
[x] I've signed the CLA and required builds are green.

Fixes #2129

@sarabala1979 could you review for me please? Can be merged if you are happy with it.

Have we confirmed that this fixes the actual underlying issue?

It's been tested and confirm. See https://github.com/argoproj/argo/issues/2129#issuecomment-581575119 (not it reveals another issue).


在UI管理页面的日志页面，无法查看client js上报的error page字段和调用栈

Please answer these questions before submitting your issue.

Why do you submit this issue?
[ ] Question or discussion
[x] Bug
[ ] Requirement
[ ] Feature or performance improvement

Question

What do you want to know?

Bug

Which version of SkyWalking, OS, and JRE?
SkyWalking client js
SkyWalking  v8.3.0 for H2/MySQL/TiDB/InfluxDB/ElasticSearch 7

Which company or project?

What happened?
If possible, provide a way to reproduce the error. e.g. demo application, component version.

vue开发的前端控制台报了错误，但在UI管理页面貌似没有正确展示字段和调用栈
能否展示更多字段，以及展示调用栈。

Requirement or improvement

Please describe your requirements or improvement suggestions.

Please use English on Github.

Please use English on Github.


Update wasm-timer to wasmtimer

Swaps over to wasmtimer, an updated library from wasm-timer which is not maintained.
Closes #199
See here for fork: https://github.com/google/tarpc/pull/388

lgtm, but the change has conflicts now.


Feature request: reduce_random

Just as tf.reduce_max, tf.reduce_random is to randomly return the elements across dimensions of a tensor with some probabilities, such as respect to the value of the tensor at those dimensions.
Or any other ways to implement it?

Could you first define mathematically what is the operation you're requesting? I think it's not clear enough from your text description.

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue?


command line option to prepend track number to file names

Adds a "--prefix" command line option (bool) which would in turn output files with 3 -forced- digits of track number in playlist (i.e. "003 - The Airborne Toxic Event - Sometime Around Midnight").

Leading zeroes help mp3 players to keep order if they use lexicographical sort rather than natural (sony :man_shrugging: ).
I also sorted out keeping track of track number in case of an error by keeping a dictionary to map appended track numbers to original track numbers.
My test bash script is also included because I dont know how to remove it from PR.

w/love
-Alp

Well we aren't accepting v2 changes. Sorry.  If you'd like we'll add a link to your fork for those who would like the functionality you implemented.

Thank you for considering the PR. That's alright, this functionality was 100% for my personal use, I'll just (try to) merge v2 onto my fork instead. I just thought it could be helpful to some other people.
Re. adding a link: up to you really because of same/similar reasons.
Thanks again for the work! :)

Don't mention. @ritiek wanted a way to download his music and I wanted a way to download all my weird songs accurately... the work we put in was really for personal use.
Just like you.

would be a nice feature to have in v3!

@vesper8 saw your comment and did this: https://github.com/spotDL/spotify-downloader/pull/933

@alpsayin thank you for that wonderful PR! hope it gets merged : )

Yep, wonderful PR indeed. I actually wanted to ask if you guys (@vesper8 & @alpsayin) would be interested in another project-wide project to develop a decent, easy-to-use GUI framework? It needs combined-knowledge of HTML+CSS+JS+Python. Drop a 👍 if interested.


⚠ Bofrost.at has degraded performance

In 9dc754d, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1437 ms

Resolved: Bofrost.at performance has improved in 60dab7d after 11 minutes.


Java 9: 3.x: Some SoftAssertions error messages include NativeMethodAccessorImpl.invoke0 line

For example:
SoftAssertions.fail("Should not reach here");

outputs:
 <"Should not reach here
at NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2)">

instead of expected output:
 <"Should not reach here">

This also effects extracting.

Fixed in https://github.com/joel-costigliola/assertj-core/commit/2c24d3794550885b941737d6117679987e17cf51


feat(ol): sort ol.ext entry point to the top if present

This goes along with ngageoint/opensphere/pull/1341 to sort the ol.ext entry point to the top of the generated webpack entry point, index.js. That entry point needs to be loaded first, so if plugins contribute entry points they previously would have been added before the main app entry points. With this change, ol.ext will be sorted to the top and the remaining order will be unchanged.

:tada: This PR is included in version 9.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


fix(API): Fix bug in DbCollection.repr

Fixes #264

Add an integration test for DbCollection class.

Fix test_driver_call to be less dependent on driver string.

[x] This contribution adheres to CONTRIBUTING.md.

[x] New tests have been created for any new features or regression tests for bugfixes.

[x] tox successfully runs, including unit tests and style checks (see CONTRIBUTING.md).

Coverage remained the same at 67.742% when pulling 68953fc056a46c69296b6c240290e3bc8ae4b503 on d-bohls:database.cluster__repr__exception into 489166755b2505c79cce692794e948dbe72bba4a on ni:master.

Coverage remained the same at 67.742% when pulling 68953fc056a46c69296b6c240290e3bc8ae4b503 on d-bohls:database.cluster__repr__exception into 489166755b2505c79cce692794e948dbe72bba4a on ni:master.


Imagemagick6 update

This PR includes the property source-type: tar to the imagemagick part; the snap doesn't build without it. The source url has php on the end which I suspect is confusing snapcraft:
source: http://git.imagemagick.org/repos/ImageMagick/repository/archive.tar.bz2?ref=ImageMagick-6

This change is

 many thanks!

Reviewed 2 of 2 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Renames app to content-performance-manager

Trello card
A few weeks ago, when we set up the Repo in Github is wasn’t
clear to us what the name of the application were going to be,
so we decided to go with a temporary one: com-prototype.
But, we have finally agreed to name it content-performance-manager,
so it is time to update the name across the Rails app.
This PR updates all references to the old name (com-prototype)
across the codebase:

Layout
Application config
Database names
Session info

Thank you for your review @chao-xian


Search option on the documentation page

A search option on the documentation page of the Shoelace webpage would help in find classes more easily.

Closing in prep for the 2.0 release. The new documentation is based on Docsify and does feature a search. Thanks for submitting this suggestion!


Modified styled components for the create quiz page and edit quiz page

Description
I made some modifications to the names and CSS used in styled components for the create quiz and edit quiz page.

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
I tested this on my local machine. After making modifications to the styled components for the create quiz and edit quiz page, both pages still look similar, are responsive and functional.

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] My code has been reviewed by at least one peer
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

I guess I'll just approve this so at least we have that functionality in place.


Can i use sherpa onnx directly on python ?

HI,
i want to use sherpa directly on python editor, not using cmd
i can't find that on documentation
is that possible ?
thanks in advance

Definitely possible.
It's just a Python package, like PyTorch and numpy. There is nothing special with sherpa-onmx.
Please see the folder python-api-examples for usage.
We also have doc for it.
Please read it first.


sdist for 1.2.1 is missing on PyPI

There is no sdist for 1.2.1 on PyPI. Is it possible to upload it? Thanks.

Did I do something wrong when uploading v1.2.1?  My checklist says ...
rm dist/*
python setup.py sdist bdist_wheel
ls -al dist
python -m twine upload dist/*

... though I may have missed something.  I'll try again.

Please check if this is still an issue?

Thanks. It is no longer an issue.


delete failed stacks by default

Changelog

cloudformation:CreateStack OnFailure = DELETE by default

Issues fixed or closed
Questions (open the PR then click the check boxes)
Did you update the documentation related to your changes?

[x] Yes
[ ] My changes were not already documented

Did you run make before committing code and opening this PR?

[x] Yes
[ ] I didn't change any code

Did you run porter create-stack and porter sync-stack to verify provisioning
works?

[ ] Yes
[x] N/A

:shipit:


[WIP] [restructure] Restructure the core files

This patch restructures the internal files
include and src folders are replaced with more relevant and clustered folders
headers and souces now live together
Also the headers exposed in the packaging are severely limited than exposing
all the headers. Updated for Android and Tizen packaging as well.
Commit: 2
Updated debian packaging to limit the files which are packaged and exposed.
Self evaluation:
1. Build test: [x]Passed [ ]Failed [ ]Skipped
2. Run test: [x]Passed [ ]Failed [ ]Skipped
Signed-off-by: Parichay Kapoor<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #699. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

:octocat: cibot: @kparichay, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/699-202011041202330.38628005981445-7d3dc31f5675125be139d46e78e2f6755caed270/.

:octocat: cibot: @kparichay, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/699-202011041216410.95716404914856-88be3043c95b835c712e382867146685722b4142/.

:octocat: cibot: @kparichay, **** does not include doxygen tags such as @file @brief. You must include the doxygen tags in the source code at least.

:octocat: cibot: @kparichay, You wrote code with incorrect doxygen statements. Please check a doxygen rule at http://github.com/nnsuite/TAOS-CI/blob/master/ci/doc/doxygen-documentation.md

:octocat: cibot: @kparichay, Oooops. The commit has an invalid executable file. The file is Applications/tensorflow-1.13.1/tensorflow-lite/include/flatbuffers/base.h. Please turn the executable bits off. Run chmod 644 file-name command.

:octocat: cibot: @kparichay, One of the module of prebuild group is failed. If you want to get a hint to fix this issue, please go to https://github.com/nnstreamer/nntrainer/wiki/.

:octocat: cibot: @kparichay, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/699-202011041229040.020653009414673-6823350e67916337dafd94fa6db306d2b4e7ea0b/.

:octocat: cibot: @kparichay, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/699-202011060935410.8136100769043-8e64f31f5749de0821768ad5f5114ff9b8041ca4/.


next accepts named arguments

Arguments to next are parsed like arguments to method calls, but they shouldn't support named parameters:
next 1, foo: 2

This should probably raise a syntax error. Could also capture the named arguments and provide them somehow to the yielding scope, but that's probably too complicated - and not really useful.
If only named arguments are provided next foo: 2, it raises Index out of bounds.

return statement accepts named arguments (of course not work). Because they are parsed by same parse_control_expression method.
Additionally yield accepts named arguments also, but we cannot refer these values. It should be fixed.

If no positional arguments are present, named arguments could perhaps be transformed to a named tuple.

All of this works in Ruby, I would do nothing regarding this for now.

foo = while true
        break 1, foo: 1
      end
p foo

In Ruby it yields [1, {foo: 1}], but in Crystal it yields what?

I just checked and #10566 did not resolve this one.

#10566 is only concerned with how while expressions interpret break arguments; it doesn't change what is supported by the break expressions themselves (and by extension the remaining control statements).
Ruby's behaviour here is to combine all named arguments, including from double splats (analogous to #10193), into a hash as the last value. But then there is the following oddity:
def foo(**opts)
  yield **opts
end

foo { |x| x }  # => {}
foo { |*x| x } # => []

In Ruby 3 the first line will return nil. By the way, only yield in Ruby allows named arguments alone (yield x: 1); the other control statements require at least one positional argument if named ones are also present, otherwise it is a syntax error.
I am not sure which behaviour we would choose, or even whether we need them. IMO it shouldn't be possible to mix positional arguments and named arguments in the same parameter:
def foo
  yield 1, 2
  yield 3, a: 4
end

foo { |_, y| typeof(y) } # => (Int32 | NamedTuple(a: Int32))

I would just make named arguments from these keywords an error and be done with it. I don't see much usefulness for using named arguments with next, break or yield. If you want to pass a named tuple, you can just use a named tuple literal.

For break, next, and return I agree. For yield there is actually the possibility of supporting named parameters in blocks. In Ruby:
def foo
  yield a: 1, b: 2
end

foo do |b:, **ns|
  [b, ns] # => [2, {:a=>1}]
end

def bar
  yield 1, 2, 3, 4, a: 5, b: 6, c: 7, d: 8
end

bar do |x0, x1, *xs, b:, a:, **ns|
  [x0, x1, xs, b, a, ns] # => [1, 2, [3, 4], 6, 5, {:c=>7, :d=>8}]
end

A Crystal analogue would be:
def foo
  yield a: 1, b: 2
end

foo do |*, b, **ns|
  {b, ns} # => {2, {a: 1}}
end

def bar
  yield 1, 2, 3, 4, a: 5, b: 6, c: 7, d: 8
end

bar do |x0, x1, *xs, b, a, **ns|
  {x0, x1, xs, b, a, ns} # => {1, 2, {3, 4}, 6, 5, {c: 7, d: 8}}
end

However this is very tricky to implement because it implies all Procs must also support named parameters. (Ruby lambdas do support them.) So perhaps disallowing named arguments in all control statements is the only sensible thing to do.


Fix: Adding and Removing public config take long time to reflect.

Description
Replaced the binding on the 'modelValue' with the initialized 'config' object.
Changes

Created the config object and set the value of the node public config inside it
Send the config object to the node as an event to update the UI
Created a separate function for toggling adding/removing the config to make it readable and easier to code.

Related Issues

https://github.com/threefoldtech/tfgrid-sdk-ts/issues/1855

Screenshots/Video
Screencast from 01-21-2024 03:47:00 PM.webm
Checklist

[ ] Tests included
[ ] Build pass
[ ] Documentation
[ ] Code format and docstrings
[ ] Screenshots/Video attached (needed for UI changes)

Screencast from 01-22-2024 04:01:19 PM.webm

After clearing the public config then instantly switching the page and returning to it the config will stay the same and won't be removed.
Screencast.from.22-01-<IP_ADDRESS>.webm

The same flow mentioned above is also reversible and can be done with adding public config.
Screencast.from.22-01-<IP_ADDRESS>.webm

That happened because the changes reflected in the chain in time but not in the gql, so I think using the chain directly will be better to fix this issue


Plans to support more cheatcodes in chisel?

Component
Chisel
Describe the feature you would like
Support all the cheatocdes in chisel
Additional context
Today only a few cheatcodes are supported in chisel, like prank and deal. But many are still missing : assertLt , envUnit, envAddress, assertEq , etc.
Furthermore it is not clear which ones are already supported and which are not.

Supportive,
What do you think ahould be prioritized?

For quick testing purposes I think most important ones are assertions related ones like, especially assertEq.

Not sure what you are doing, but you can probably just use require instead of assertEq for that use case.
But the distinction here seems to be that the vm interface/cheats are available, but the stdCheats/etc from forge-std are not present. Maybe we just need a way to pull in forge-std into chisel (if that's not currently present)? cc @clabby

This feature is useful to be able to debug tests faster inside chisel for example.

Another annoying inconsistency I noticed is that vm.deal cheatcode in Chisel is only available for native ETH, but not for ERC20 tokens. I.e only the 2 arguments version of deal cheatcode is available. It would be nice if we can re-use same cheatcodes in Test and in Chisel.

Not sure what you are doing, but you can probably just use require instead of assertEq for that use case.
But the distinction here seems to be that the vm interface/cheats are available, but the stdCheats/etc from forge-std are not present. Maybe we just need a way to pull in forge-std into chisel (if that's not currently present)? cc @clabby

We can definitely pull in forge-std, but when I did that for the first iteration to get it working, it slowed down compilation time and made the repl feel a good bit less snappy. We'd also have to add forge-std as a submodule - will defer to @mattsse and you on whether or not this is worth it!
As for the inconsistency of some of the cheatcodes (i.e. the lack of the version of vm.deal that is for ERC20 tokens), it's looking like that cheatcode is not present in testdata/cheats/Cheats.sol. Should probably go through and make sure Cheats.sol has parity w/ forge-std's Vm.sol and write tests for the ones that aren't there at the moment.


use equivalentClass instead of AbstractClass

An alternative approach for flagging a class as abstract, instead of subclassing it with "http://spdx.invalid./AbstractClass".
This approach adds SHACL validation that prevents abstract classes from being directly instantiated.
It looks something like:
:ExtendableLicense a owl:Class ;
    sh:not [
        sh:class :ExtendableLicense ;
        sh:message "ExtendableLicense is an abstract class and should not be instantiated directly. Instantiate a subclass instead."@en
    ] .

@zvr @JPEWdev - Pls review - it looks like this should work, but it requires changes to the code generators as well as the spec parser.  I have no problem updating the Java code generator if this approach works for both of you.

I've updated the PR with a diffetent method that doesn't require listing subclasses in the constraints.
Pleasse read the updated description.

Changed the PR to use a simpler method:

Removed OWL.oneOf because it's not needed for validation.
Instead of SH.disjoint I'm using a more straightforward approach with SH.not on the SH.class.
Added a helpful SH.message.
Updated the PR description with an example.

For validation, I run this script:
import rdflib
from rdflib import SH
from pyshacl import validate

s = """
@prefix ex: <http://example.org/ns#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix spdxcore: <https://spdx.org/rdf/3.0.1/terms/Core/> .

ex:MyAgent
    a spdxcore:Agent ;
    spdxcore:creationInfo _:MyCreationInfo .

_:MyCreationInfo
    a spdxcore:CreationInfo ;
    spdxcore:createdBy ex:MyAgent ;
    spdxcore:created "2024-09-04T20:25:34Z"^^xsd:dateTimeStamp ;
    spdxcore:specVersion "3.0.1" .

ex:MyElement
    a spdxcore:Element ;
    spdxcore:creationInfo _:MyCreationInfo .

ex:MyTool
    a spdxcore:Tool ;
    spdxcore:creationInfo _:MyCreationInfo .

"""
data_graph = rdflib.Graph()
data_graph.parse(data=s, format="turtle")

shapes_graph = rdflib.Graph()
shapes_graph.parse("output/rdf/spdx-model.ttl", format="turtle")

_, report_graph, _ = validate(data_graph, shacl_graph=shapes_graph, allow_warnings=True)
for violation in report_graph.subjects(rdflib.RDF.type, SH["ValidationResult"]):
    message = report_graph.value(subject=violation, predicate=SH["resultMessage"], )
    print(message)

Which produces:
Node ex:MyElement must not conform to shape [
  sh:class ns1:Element ;
  sh:message Literal(
    "https://spdx.org/rdf/3.0.1/terms/Core/Element is an abstract class and should not be instantiated directly. Instantiate a subclass instead.",
    lang=en
  )
]

Excellent. I like this solution. I'll work on adding support for this idiom to shacl2code. My only request here is that we squash the commits when they are merged (or squash them before merging in the PR)

There are two changes here:
a. remove the Abstract class
b. implement what it means to be an abstract class in SHACL
I'm fully supporting (b) above -- we needed this!
Regarding (a), for people who use the TTL file to automatically produce class generations in some language, is everyone OK with not having the simple Abstract class? The discovery that a class is abstract in our model should then be made by recognizing the generated SHACL entries.

There are two changes here:
a. remove the Abstract class b. implement what it means to be an abstract class in SHACL
I'm fully supporting (b) above -- we needed this!
Regarding (a), for people who use the TTL file to automatically produce class generations in some language, is everyone OK with not having the simple Abstract class? The discovery that a class is abstract in our model should then be made by recognizing the generated SHACL entries.

I can update the Java code generator to work with this new approach.  It sounds like @JPEWdev is also cool with this.  I don't know of any other tools that are using this approach, so I think we're OK removing it.

https://github.com/JPEWdev/shacl2code/pull/28

@zvr - Can we merge this?  I'm using the feature branch for my tooling and it would be great to use an official merged version.

I believe this PR caused issue #165


python3-jetson-stats: update to 4.2.12 for JP6.1 compatibility

Hello,
Pull request https://github.com/OE4T/meta-tegra-community/pull/131 updates python3-jetson-stats to 4.2.4 but this version is not compatible with JP6.0 or JP6.1 and has various bugs fixed in 4.2.12 :

no compatibility warning is displayed
OFA is not detected
nvpmodel is not working
crash when all CPU are not online
crash when service is starting

Furthermore the patches are wrong because CUDA version is 12.2 and VPI is 3 into scarthgap or master :
into jetson_libraries need
-    if os.path.isfile("/usr/local/cuda/version.txt"):
-        version = cat("/usr/local/cuda/version.txt")
+    if os.path.isfile("/usr/local/cuda-12.2/version.txt"):
+        version = cat("/usr/local/cuda-12.2/version.txt")
         match = re.search(CUDA_FILE_RE, version)
         if match:
             cuda_version = match.group(1)
-    elif os.path.isfile("/usr/local/cuda/bin/nvcc"):
-        cmd = Command(['/usr/local/cuda/bin/nvcc', '--version'])
+    elif os.path.isfile("/usr/local/cuda-12.2/bin/nvcc"):
+        cmd = Command(['/usr/local/cuda-12.2/bin/nvcc', '--version'])

And
vpi_match = re.search('libnvvpi.so.(\d+.\d+.\d+)',str(list(Path('/opt/nvidia/vpi3/lib/aarch64-linux-gnu/').glob("libnvvpi.so.*.*"))))

Done in master


Fix follow_cwd option

follow_cwd and nil or session always use session because the true and nil expression is evaluated to false

Thanks for the PR!


HTTPS support

Hello,
It would be awesome if this container supported https for the web applications, any plans for that or shall I add it myself ?
Thanks,
Mathias.

Hi @macoopma when you say support, what are you expecting? Added apache configs, LetsEncrypt?
Thanks,
Matt

Great project! It would be perfect if this project had (SSL) security-by-design.

@rodgermoore would you be expecting to include certificates directly, or use a service like LetsEncrypt?

This is a really beautiful project. I finally have no problems with user and group permissions.
Unfortunately, however, in my opinion it is essential to configure the request over https.
In my opinion, considering that the main use of the container is development, it may be enough to create a self-signed certificate and then configure Apache...

I don't think this under the scope of this project. As load balancing, caching, etc isn't, their network layer considerations.
Docker provides you the simplicify of spliting those services into multiple containers. Shoving everything in one container is really not a great a job.
As such, I could see this as a dev container, which is fine but throws away any and all security best practices. And as such should not be used in production.
There plenty of options out there for SSL termination with docker, certbot integration. load balaning. All of them can easily end up redirecting requests to appropriate application containers (PHP or else).
On that note, the following is an excerpt from a docker compose file I use in 2 production deploys. Includes a NGINX reverse proxy that does SSL termination, and a certbot container that automatically generates new SSL certificates for newly created containers that defined LETS_ENCRYPT_* environment variables. Certificate generation is 100% automated. Works like a charm, and can easily support add a container with the image from this project.
services:
  reverse-proxy:
    image: jwilder/nginx-proxy
    container_name: reverse-proxy
    ports:
      - 80:80
      - 443:443
    networks:
      - service_network
    volumes:
      - /var/run/docker.sock:/tmp/docker.sock:ro
      - nginx-logs:/var/log/nginx
      - nginx-certs:/etc/nginx/certs
      - nginx-vhost:/etc/nginx/vhost.d
      - nginx-html:/usr/share/nginx/html

  ssl-certbot:
    image: jrcs/letsencrypt-nginx-proxy-companion
    container_name: ssl-certbot
    environment:
      NGINX_PROXY_CONTAINER: reverse-proxy
    networks:
      - service_network
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - nginx-certs:/etc/nginx/certs
      - nginx-vhost:/etc/nginx/vhost.d
      - nginx-html:/usr/share/nginx/html
    depends_on:
      - reverse-proxy

  app:
    image: <some/image>
    container_name: app
    environment:
      VIRTUAL_HOST: app.example.local
      LETSENCRYPT_HOST: app.example.local
      LETSENCRYPT_EMAIL<EMAIL_ADDRESS>    networks:
      - service_network

networks:
  service_network:
    driver: bridge

volumes:
  nginx-logs:
    driver: local
  nginx-certs:
    driver: local
  nginx-vhost:
    driver: local
  nginx-html:


[BUG] Missing release-v2.9 on chart.rancher.io

Rancher Server Setup

Rancher version: v2.9.1
Installation option (Docker install/Helm Chart):

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): k3s v1.27.15

Proxy/Cert Details:

Air Gapped

Information about the Cluster

Kubernetes version:
Cluster Type (Local/Downstream):

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider):

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)

If custom, define the set of permissions:

Describe the bug
Missing charts for release-v2.9 on charts.rancher.io
After promoted rancher v2.9.1 to rancher-stable I supposed this is a missing promotion in rancher/charts repo.
To Reproduce
helm repo add rancher-chart https://chart.rancher.io
helm repo update
helm search repo rancher-monitoring

Result
helm search repo rancher-monitoring
NAME                                 	CHART VERSION    	APP VERSION	DESCRIPTION
rancher-charts/rancher-monitoring    	103.1.1+up45.31.1	v0.65.1    	kube-prometheus-stack collects Kubernetes manif...
rancher-charts/rancher-monitoring-crd	103.1.1+up45.31.1	           	Installs the CRDs for rancher-monitoring.

Expected Result
helm search repo rancher-monitoring
NAME                                 	CHART VERSION    	APP VERSION	DESCRIPTION
rancher-charts/rancher-monitoring    	104.1.0+up57.0.3	v0.72.0    	kube-prometheus-stack collects Kubernetes manif...
rancher-charts/rancher-monitoring-crd	104.1.0+up57.0.3	           	Installs the CRDs for rancher-monitoring.
Screenshots
Additional context
I do not have the option to use the git source for helm repo.

Thanks for publishing!