No way to tell what type your event subscription is

As I'm not a user of event grid, I'm unsure how helpful this may be, but there isn't an easy way to discern what type of event subscription I'm generating mock events for.

The extension is being deprecated. No new work will be done on it.


Is there any way to reduce the GPU memory usage and enhance the inference speed?

The M-LSD's pred_lines takes a long time than I expected, about ~6Hz (including other stuff; M-LSD-tiny only seems to be about 10Hz).
And it takes about 2G of GPU memory.
Is there a way to reduce the GPU memory usage and enhance the inference speed? (including TensorRT, etc.)
Please give me an adivce as I'm not an expert of this.
Thanks!

You can try the TensorRT version by @rhysdg ,  https://github.com/lhwcv/mlsd_pytorch#benchmarks

You can try the TensorRT version by @rhysdg ,  https://github.com/lhwcv/mlsd_pytorch#benchmarks

Thx for sharing the link.
I'm not familiar with it. TensorRT would reduce the memory usage and enhance the inference speed at the same time?

@JinraeKim @lhwcv Apologies for the late reply, busy times! Forsure the main criteria with TensorRT is to reduce latency, and therefore increase inference speed pretty signifcantly with minimal reduction in quality at FP16. Given a successful conversion you should also see a significant reduction in memory allocation overhead.
Its worth bearing in mind that the setup I have here was developed for Jetson series devices, although my understanding is that it plays nice with Nvdia's NGC PyTorch docker container. I am hoping to start bringing in a TensorrT Python API/ Pycuda version shortly that should work across a wider range of devices. What were you hoping to deploy with @JinraeKim?

@rhysdg Thank you for the detailed explanation!
Yeah, I'm looking for employment with Nvidia Jetson as well, and my personal laptops for practice as well.
It gave me a really nice insight! Thank you again!

@JinraeKim I'm working on a more robust tool over at trt-devel that adds the ability to convert custom trained models with three channel inputs as per the training code, and drops to the result into a folder named accorrding to experiment. This will eventually become a pr but I'm hoping to do a little more testing with the onnx conversion when I get a chance. For now the tool works if you need it for a custom training run, and I can confirm that the results are fantastic with @lhwcv's training script plus some added aggressive pixel level augs!
After that's done I'll work on a straight TensorRT conversion tool, that has wider device support, and also post-training quantization for the onnx representation!

Ah yes, and I'm yet to update the documentation accordingly but adding the --custom experiment.pth arg with your checkpoint dropped into ./models/experiment.pth will result in a converted a sped up representation at ./models/experiment/mlsd_large/tiny__512_trt_fp16.pth


Technical User Management - enable inactive overview

Summary
Till now service account endpoints only support ACTIVE technical account details.
However it is likely that the Company Admin/IT Admin also wants to receive access of the technical user account history of probably DELETED technical users.
2 Options:

enhance the existing endpoint with an optional filter
new endpoint

Decision: enhance existing endpoint instead of adding new endpoints.
Where?
Enhance the view chipcards by adding a card for "inactive" users

API Endpoint to fetch inactive technical users for technical user table GET /api/administration/serviceaccount/owncompany/serviceaccounts?filterForInactive=true'
API Endpoint to fetch inactive technical users details (for the detail screen) GET /api/administration/serviceaccount/owncompany/serviceaccounts/{serviceAccountId} ...this is exactly the same endpoint as used for active technical user details
NOTE: regarding the chipcard design - please check once with Anni regarding the to be used chipcard/text color. Ideally its a bit different to our current used chipcards since we are displaying none active users

@jjeroch Anne suggested to create button for 'Inactive' as below link and before the 'ALL' chip. Does it okay for you ?
https://www.figma.com/file/pcHZWXTQJUguIT75QSk9KW/Portal-Designs?type=design&node-id=9168-198&mode=design&t=JcPSlsUMjxi6cszJ-0

@nidhigarg-bmw Anni her feedback is missing. i will see her at 10am - for now I would for sure say that we:

change the "All" Button to "Active"
add an "Inactive" button beside


Migrate Wiki to Github Discussions

Currently we have a Github wiki that has some discussion items that may or may not still be relevant (?)
Github now has a discussions feature that might be a better home for these types of 'discussions'.
Perhaps we could turn off the wiki on this repo or have a link from the Wiki to the Docs.

Yep you are right! I migrated the open discussions to issues :)


set source_address for requests

I am trying to run a number of different slave instances on a machine with more than one IP address.
I haven't been able to get the slaves to bind to anything other than the main IP address of the system.
I've spent some time digging down layers of python code looking to see where a source_address can be set.  It looks like this is possible with urllib3 (at newer levels of python 2.7).   But I can't figure out how to set it on the urllib3 object, or the request object, or any higher level objects that locustio uses.
This is a fairly major issue - without it, I will need to provision a lot more machines to produce the workload I need - since each IP address gets saturated at around 64k sockets.  I need to test 1M+ connections.

Hi -
Has anyone from the development team looked at this issue yet?

Hi @jefflowrey, I know we're a little late to the party, but help me understand your network setup. How is your machine configured with multiple IP's? Can you send the route output?
We can definitely think about exposing the source_address through the public API, but I'll have to dig into the underlying libraries and think about a sane way to do that. If you have the time or desire to take a stab yourself and open a PR, that would definitely expedite the feature.

We've moved on to other solutions, alas.  I'm not sure I quite remember where we were.
But simply imagine a machine with more than one ethernet interface, like eth0 and eth1.  One is a public address, that is bound to eht0.  eth1 is a private address.
I would need to make sure that any locust/locutio services were only bound and exposed to the private address, and not the public.
A simple way to do this, of course, would be to switch eht0 to be the private address and eth1 to be the publicl.  But since these are cloud hosted machines, that's not really possible.
So, again, the need to ensure that locust/locution slaves and even the server are using an ip address/interface that can be configured.

It sounds to me like you wanted to control which IP-address Locust bound to when listening for incoming connections? If so, couldn't you firewall the machines to make sure that the Locust ports wasn't accessible from the outside network?
Or did you need to somehow control which network interface that was used for the outgoing HTTP connections? Why wouldn't the correct interface get selected automatically when making requests to an IP on the internal network?
Just trying to understand the issue :).

Well, as I said, we've moved on... so I'm a bit fuzzy on the original question.  Reading it again, it looks like I wanted to be able to set slave A to always use ip 1, slave 2 to always use ip2, and etc.
This may have been for firewall or performance reasons - I don't remember.  Or even logging /performance testing issues.

I guess in general it would be good if both the server and the clients could have ip configuration exposed to end users - rather than relying on default behavior of urrlib3 or etc.

Well, as I said, we've moved on... so I'm a bit fuzzy on the original question.

I totally get that and sorry for not replying back then!
Even though I guess it doesn't really matter to you now, I'll address  the following just as reference for anyone else that might be interested in this in the future:

it looks like I wanted to be able to set slave A to always use ip 1, slave 2 to always use ip2, and etc.

I assume we're talking about which IP we want to send HTTP requests to. This could be done by setting the IP that we want to load test, as an environment variable when starting Locust, and then reading that environment variable in our load testing scripts. We would then start the slave processes with the correct IP set for them respectively. I guess it's kind of hackish, but I'm not sure that it's a common enough use-case to justify a feature in Locust for it.
I guess another - perhaps cleaner - way to do it could be to set a custom hostname (e.g. test-target) in /etc/hosts on the slave machines, that points to the correct IP, and then set that hostname when spawning Locust.
Again, I understand you ended up using other stuff. I'm just writing it down for future reference :).

I was searching for the ability to set the SRC IP for the locust process and arrived at this thread.
I think what the OP meant here is that he wants to be able to bind a specific source IP address to a locust process.
For example:
if we have NIC eth0 with 2 IPs <IP_ADDRESS> and <IP_ADDRESS>
Then, if we run 2 locust processes in slave mode, one would send the requests using .1 IP and the other using .2 IP.
The ability to generate traffic from multiple source IPs to the same destination IP is very important when testing multi node / multi core systems that rely on the IP as the hash for distributing the traffic/load.
It would be great if this capability could be exposed as a  command line argument when starting the process.
As a reference, wget has this capability with "--bind-address"

Any solution yet for this issue?
Simple scenario (1 host, 2 NICs):
locust -f ./good_traffic.py --host=http://myserver:80 **--source-ip=<IP_ADDRESS>**
locust -f ./bad_traffic.py --host=http://myserver:80 **--source-ip=<IP_ADDRESS>**
Is there a way to do something like that?

Adding to the thread.
We want to simulate users coming from different IP addresses in order to test:

Our load balancer sends requesters to the closest cluster (according to its IP)
Our HA Proxy and the sticky session mechanism works as it should keeping session data per unique IP
Our service behind the HA proxy can handle incoming load and stress

Note: We have only 1 target host
Is there any progress in such feature for the slaves?

Is there any progress in such feature for the slaves?

No, but Pull Requests are welcomed

In case someone is still looking for this feature. There are HTTPAdapters that can be leveraged for this purpose. This code shows how (works for me):
from locust import HttpLocust, TaskSet
from requests_toolbelt.adapters.source import SourceAddressAdapter
import random

def login(l):
    l.client.post("/login", {"username":"ellen_key", "password":"education"})

def logout(l):
    l.client.post("/logout", {"username":"ellen_key", "password":"education"})

def index(l):
    l.client.get("/")

def profile(l):
    l.client.get("/profile")

class UserBehavior(TaskSet):
    tasks = {index: 2, profile: 1}

    def on_start(self):
        # List of IP's that can be used as "source" - hardcoded for simplicity
        ips = ['<IP_ADDRESS>', '<IP_ADDRESS>', '<IP_ADDRESS>', '<IP_ADDRESS>']
        i = random.randint(0, len(self.ips)-1)
        self.client.mount("https://", SourceAddressAdapter(self.ips[i]))
        self.client.mount("http://", SourceAddressAdapter(self.ips[i]))
        login(self)

    def on_stop(self):
        logout(self)

class WebsiteUser(HttpLocust):
    task_set = UserBehavior
    min_wait = 5000
    max_wait = 9000

Thanks for your suggested workaround @ram-ibm ! Closing this.


[BUG] Rancher pods panic on startup if cluster .spec.rancherKubernetesEngineConfig is null

Rancher Server Setup

Rancher version: v2.6.13 (but reproducible on latest)
Installation option (Docker install/Helm Chart): n/a

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): n/a

Proxy/Cert Details: n/a

Information about the Cluster

Kubernetes version: n/a
Cluster Type (Local/Downstream): local

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:

Admin
Describe the bug

Rancher pods panic'ing when importing a cluster that has .spec.rancherKubernetesEngineConfig as null.
To Reproduce

See ticket, but here is the POST the user was doing:
curl -ksS \
  -X POST \
  -H "Authorization: Bearer token-xxxxx:xxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '
{
  "answers": {
    "values": {
      "rancherKubernetesEngineConfig.ingress.provider": "none",
      "rancherKubernetesEngineConfig.kubernetesVersion": "v1.24.13-rancher2-1",
      "rancherKubernetesEngineConfig.monitoring.provider": "metrics-server",
      "rancherKubernetesEngineConfig.services.etcd.backupConfig.intervalHours": 12,
      "rancherKubernetesEngineConfig.services.etcd.backupConfig.retention": 6,
      "rancherKubernetesEngineConfig.services.kubeApi.secretsEncryptionConfig.enabled": "false",
      "rancherKubernetesEngineConfig.services.kubeApi.serviceNodePortRange": "30000-32767",
      "rancherKubernetesEngineConfig.upgradeStrategy.drain": "false",
      "rancherKubernetesEngineConfig.upgradeStrategy.nodeDrainInput.deleteLocalData": "false",
      "rancherKubernetesEngineConfig.upgradeStrategy.nodeDrainInput.force": "false"
    }
  },
  "clusterTemplateId": "",
  "clusterTemplateRevisionId": "",
  "dockerRootDir": "/var/lib/docker",
  "enableClusterAlerting": false,
  "enableClusterMonitoring": false,
  "enableNetworkPolicy": null,
  "localClusterAuthEndpoint": null,
  "name": "testing-testing
",
  "rancherKubernetesEngineConfig": null,
  "scheduledClusterScan": {
    "enabled": false,
    "scanConfig": null,
    "scheduleConfig": null,
    "type": "/v3/schemas/scheduledClusterScan"
  },
  "type": "cluster",
  "windowsPreferedCluster": false
}' \
  https://rancher-server/v3/cluster?_replace=true

Result
Rancher goes into a crashloop when trying to migrate secrets.
Expected Result

Rancher does not crash.
Screenshots

n/a
Additional context

SURE-6754

Root cause
There was no check if the cluster.management.cattle.io .spec.RancherKubernetesEngineConfig field was nil before accessing sub-fields on that struct. This could lead to rancher pods panic'ing and restarting.
What was fixed, or what changes have occurred
Added a check for nil before accessing the CloudPrivdier field of the RancherKubernetesEngineConfig struct when migrating secrets.
Areas or cases that should be tested
Probably just create clusters normally via cURL as in the issue above.
What areas could experience regressions?
None that I'm aware of - since we are just adding a nil check before accessing a field.
Are the repro steps accurate/minimal?
Yes. I included the exact curl request above.

Ticket #42377 - Test Results - ✅
Reproduced on HA Helm running Rancher v2.7.5:

Fresh install of Rancher v2.7.5
As admin, create an API Token
Supply API Token to authorization headers, and modify rancher-server portion of URL to point to host url, then run the following command:

curl -ksS \
  -X POST \
  -H "Authorization: Bearer token-xxxxx:xxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '
{
  "answers": {
    "values": {
      "rancherKubernetesEngineConfig.ingress.provider": "none",
      "rancherKubernetesEngineConfig.kubernetesVersion": "v1.24.13-rancher2-1",
      "rancherKubernetesEngineConfig.monitoring.provider": "metrics-server",
      "rancherKubernetesEngineConfig.services.etcd.backupConfig.intervalHours": 12,
      "rancherKubernetesEngineConfig.services.etcd.backupConfig.retention": 6,
      "rancherKubernetesEngineConfig.services.kubeApi.secretsEncryptionConfig.enabled": "false",
      "rancherKubernetesEngineConfig.services.kubeApi.serviceNodePortRange": "30000-32767",
      "rancherKubernetesEngineConfig.upgradeStrategy.drain": "false",
      "rancherKubernetesEngineConfig.upgradeStrategy.nodeDrainInput.deleteLocalData": "false",
      "rancherKubernetesEngineConfig.upgradeStrategy.nodeDrainInput.force": "false"
    }
  },
  "clusterTemplateId": "",
  "clusterTemplateRevisionId": "",
  "dockerRootDir": "/var/lib/docker",
  "enableClusterAlerting": false,
  "enableClusterMonitoring": false,
  "enableNetworkPolicy": null,
  "localClusterAuthEndpoint": null,
  "name": "testing-testing
",
  "rancherKubernetesEngineConfig": null,
  "scheduledClusterScan": {
    "enabled": false,
    "scanConfig": null,
    "scheduleConfig": null,
    "type": "/v3/schemas/scheduledClusterScan"
  },
  "type": "cluster",
  "windowsPreferedCluster": false
}' \
  https://rancher-server/v3/cluster?_replace=true

Reproduced - Rancher pods panic;

Verified on HA Helm running Rancher v2.8-57dfc4300a3071a8d58b3d865d178ababe55d33c-head:

Fresh install of Rancher v2.8-head
As admin, create API Token
Supply API Token to authorization headers, and modify rancher-server portion of URL to point to host url, then run the following command:

curl -ksS \
  -X POST \
  -H "Authorization: Bearer token-xxxxx:xxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '
{
  "answers": {
    "values": {
      "rancherKubernetesEngineConfig.ingress.provider": "none",
      "rancherKubernetesEngineConfig.kubernetesVersion": "v1.24.13-rancher2-1",
      "rancherKubernetesEngineConfig.monitoring.provider": "metrics-server",
      "rancherKubernetesEngineConfig.services.etcd.backupConfig.intervalHours": 12,
      "rancherKubernetesEngineConfig.services.etcd.backupConfig.retention": 6,
      "rancherKubernetesEngineConfig.services.kubeApi.secretsEncryptionConfig.enabled": "false",
      "rancherKubernetesEngineConfig.services.kubeApi.serviceNodePortRange": "30000-32767",
      "rancherKubernetesEngineConfig.upgradeStrategy.drain": "false",
      "rancherKubernetesEngineConfig.upgradeStrategy.nodeDrainInput.deleteLocalData": "false",
      "rancherKubernetesEngineConfig.upgradeStrategy.nodeDrainInput.force": "false"
    }
  },
  "clusterTemplateId": "",
  "clusterTemplateRevisionId": "",
  "dockerRootDir": "/var/lib/docker",
  "enableClusterAlerting": false,
  "enableClusterMonitoring": false,
  "enableNetworkPolicy": null,
  "localClusterAuthEndpoint": null,
  "name": "testing-testing
",
  "rancherKubernetesEngineConfig": null,
  "scheduledClusterScan": {
    "enabled": false,
    "scanConfig": null,
    "scheduleConfig": null,
    "type": "/v3/schemas/scheduledClusterScan"
  },
  "type": "cluster",
  "windowsPreferedCluster": false
}' \
  https://rancher-server/v3/cluster?_replace=true

Verified - Rancher pods no longer panic, imported cluster hangs in provisioning state; as expected


The maximum volume of uploaded videos is too loud, and is louder than the max volume when uploaded to any other site.

Steps to Reproduce

Upload a video
Listen at max volume, which is often the default volume

Not only is the maximum volume way louder than when listened to after uploading to other sites, it is also much louder than the max volume even on my computer. This means that by default, users are getting a different experience from a video than a creator can even test for when making a video, leaving open for the possibility of not only overly/usafely loud sounds that could hurt the ears, but also quiet sounds/audio that would normally be unnoticed, that can now be heard, contrary to the creators intent.
Attachments
No response
What platform(s) does this occur on?
Web (Desktop)
Device Info
Using Google Chrome on Windows 10
What version of the app are you using?
Build version: 1.93.0; Bundle info: 5f449e3 (prod); Bundle date: 24111700; Platform: web
Additional Information
No response

In addition it would be great if the volume level setting is saved between page refreshes. It's really kind of annoying to have to keep adjusting it to a comfortable level.

seconding that. it should remember volume settings.
example of me getting jumpscared every once in a while: when a video autoplays it's muted by default, but as soon as you manually interact with the video player in any way for the first time (scrubbing, pausing/unpausing) it instantly jumps to max volume, which is not a great experience.


[FEATURE] floppy-free broadcaster

Is your feature request related to a problem? Please describe.
I really like your mod, but it's very difficult to work with floppy disks in the game.
Sometimes you just want to play the entire playlist, like in "FileCaster", but without having to change floppy disks every time and stand next to musical instruments
Describe the solution you'd like
Available only to admins (or not) a new item, similar to the "broadcaster", but with the ability to work without floppy disks, using all midi from the "default music" folder of the server.
Describe alternatives you've considered
High capacity diskettes. Or storage for a large number of floppy disks with the ability to connect to the "Broadcaster"
Additional context
I'm tired of logging into the game with a second account to play music from "FileCaster", or changing the floppy disk to a new one every time :(
I apologize for possible errors in the text, I do not speak English, but I tried to avoid this.

Hello! Sorry for taking so long to get to this, life has been super busy recently and I haven't been able to find time for the mod -
I think this is a very good idea and I will be adding something like this soon! Thank you for the suggestion! 😄

Hello again! Apologies for the super late reply. Life got super crazy for awhile and I had pretty much no time for the mod. I've just released Beta versions for a major 4.0.0 update for versions 1.19.2-1.20.4 which replaces Broadcasters with a new Server Transmitter block that supports MIDI files provided by the server!
Please let me know if you have any other issues!


chore: hide progressive onboarding on first session

This PR resolves []
Description
This PR comes as a fix to showing the progressive onboarding on the first app session.
PS: The new flag can be useful in many other context in the app
https://github.com/artsy/eigen/assets/11945712/f3c3b909-0890-4f5d-ab06-614a021c87cc

PR Checklist

[x] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

hide progressive onboarding on first session - mounir

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Cross-platform user-facing changes (hide progressive onboarding on first session - mounir)

  Generated by :no_entry_sign: dangerJS against 0f5411ef3a41a77ebc308421c66274415be7fd03


cannot import name 'errors' in qickstart.py

apps_script/quickstart/quickstart.py reffers to errors.HttpError.
https://github.com/gsuitedevs/python-samples/blob/2c871ce0c223b62a91ff0347f5f9eee749f5cffc/apps_script/quickstart/quickstart.py#L57
errors is not defined
Traceback (most recent call last):
  File "manage.py", line 7, in <module>
    from apiclient.discovery import build, errors
ImportError: cannot import name 'errors'

I'm guessing the resolution is to add
from apiclient import errors

works for me.

Thanks for reporting this issue!


navigateToRoute doas not reload same page

I have problem with navigateToRoute.
I am trying to reload current page localhost:9000/#/contacts with
this.router.navigateToRoute('contacts', { groupId: 25 }, { replace: true})
but it is not working.
It is wotking only if i call another route like "users", but not from same.
Url is changed to localhost:9000/#/contacts?groupId=25 but it is not reloading current page, no network activity.
Please how to do reload current page with additional parameters, thanks

@denimaaark See https://github.com/aurelia/router/issues/255 - this can be controlled by changing the activation strategy.


Deploy frontend github pages

I can get this working for sure!

This might be interesting: https://github.blog/changelog/2021-12-16-github-pages-using-github-actions-for-builds-and-deployments-for-public-repositories/
It's a blog post that contains a new (official) GitHub Action called "deploy-pages", to automatically deploy on push

Automation through GitHub will hopefully be a go through #13


[WIP] Index.vue final review

Summary

Updated copy
FAQ cards no longer spill over the sides at the iPhone 5 SE size
Fixed a few :xs column bindings
Justified more things to center on mobile sizes

Screenshots
Still seeing an issue with the header image- setting the #hero element to have height: 44vw; produces a giant amount of whitespace around 1500px wide. I'm also just very unclear why we have a breakpoint at 1760px, since the page container has a max-width of 1240px, so we should be seeing any changes above that?

There are breakpoints at 1760px because the svg files don't respect the bounds of the v-container unless explicitly changed in some way (width/height %, hard px width/height, etc).  If you comment out the 1760px breakpoints this is the result (on my large monitor of ~1800 px width):

The height also changes the 'How it Works' header below distance from the hero.  The current setup is a bit hacky, admittedly.  I was under the impression we wanted this hero svg to have a limit of 1240px (and white on other side from there).  If that is the case, I believe the current solution achieves that.  Is that not the case?

Re: NewsCards on index.vue, the Featured News section needs some work it appears (you very well may be aware of this as you said WIP for this branch!)

I made two changes here (below).  Note that there is still some white space on the left and right from the v-container padding, which is a recurring theme we should discuss and come to a conclusion about.  It's subtle but you can see it here:

CHANGES:

NewsCards appear as expected on larger screen and mobile.

Messed around w the spacing for the hero and how-it-works sections.  There is probably a better way to do this I got the following below.  The fact that the background image is not a separate element makes this a bit tricky in balancing that the background hero svg takes up the whole width of the screen while being responsive as it shrinks.  Seems simple and straightforward, for me at least it's proved otherwise hence the hacky solutions.


🐛 After pauseRecording(), stopRecording() takes 4 seconds longer than if not paused

What's happening?
I logged every appendBuffer call at all if cases that are commented. While the video is recording we get a ton of
2024-04-09 16:05:17.089435-0400 Hetal[11959:1948327] [native] VisionCamera.appendBuffer(_:clock:type:): 3: Last Written Timestamp Buffer Optional(__C.CMTime(value:<PHONE_NUMBER>22041, timescale:<PHONE_NUMBER>, flags: __C.CMTimeFlags(rawValue: 1), epoch: 0))

But our design calls for a pause function before saving. So we pause the video before calling stopRecording. When paused the buffer logs don't write cause the camera is paused. We have a button for the user to save and that calls stopRecording(). When that is called then these logs happen
2024-04-09 16:05:21.210329-0400 Hetal[11959:1948456] [native] VisionCamera.stop(clock:): Requesting stop at<PHONE_NUMBER>07333 seconds for AssetWriter with status "writing"...
2024-04-09 16:05:25.410054-0400 Hetal[11959:1948327] [native] VisionCamera.stop(clock:): Waited 4.0 seconds but no late Frames came in, aborting capture...

On the react side the camera init looks like this
<Camera
       style={StyleSheet.absoluteFill}
       ref={cameraRef}
       device={device}
       isActive={true}
       format={format}
       video={true}
       fps={format.maxFps}
       enableZoomGesture={true}
     />

When the user pauses the recording we call
cameraRef.current.pauseRecording();
We then have buttons to save or retake the video. On save we call
cameraRef.current.stopRecording();
I think because it is in a pause state when we call stop no buffers are being called and that prevent finish() from happening as it normally would
Reproduceable Code
cameraRef.current.pauseRecording();
cameraRef.current.stopRecording();

Relevant log output
2024-04-09 16:05:17.089435-0400 Hetal[11959:1948327] [native] VisionCamera.appendBuffer(_:clock:type:): 3: Last Written Timestamp Buffer Optional(__C.CMTime(value:<PHONE_NUMBER>22041, timescale:<PHONE_NUMBER>, flags: __C.CMTimeFlags(rawValue: 1), epoch: 0))
2024-04-09 16:05:21.210329-0400 Hetal[11959:1948456] [native] VisionCamera.stop(clock:): Requesting stop at<PHONE_NUMBER>07333 seconds for AssetWriter with status "writing"...
2024-04-09 16:05:25.410054-0400 Hetal[11959:1948327] [native] VisionCamera.stop(clock:): Waited 4.0 seconds but no late Frames came in, aborting capture...

Camera Device
{
  "hardwareLevel": "full",
  "hasTorch": true,
  "formats": [],
  "isMultiCam": false,
  "sensorOrientation": "landscape-right",
  "maxExposure": 8,
  "supportsLowLightBoost": false,
  "minZoom": 1,
  "minExposure": -8,
  "hasFlash": true,
  "name": "Back Camera",
  "maxZoom": 123.75,
  "minFocusDistance": 10,
  "physicalDevices": [
    "wide-angle-camera"
  ],
  "supportsFocus": true,
  "supportsRawCapture": false,
  "neutralZoom": 1,
  "id": "com.apple.avfoundation.avcapturedevice.built-in_video:0",
  "position": "back"
}

Device
iPhone SE
VisionCamera Version
3.9.1
Can you reproduce this issue in the VisionCamera Example app?
No, I cannot reproduce the issue in the Example app
Additional information

[X] I am using Expo
[ ] I have enabled Frame Processors (react-native-worklets-core)
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

yea, this is a bug.

Any update on this? facing similar issue
"react": "18.2.0",
"react-native": "0.74.1",
"react-native-vision-camera": "^4.0.3"

No update yet, if you want me to fix this for ya, contact me thru my agency or sponsor this issue.

Hey all!
I just spent a few days on thinking about a battleproof timestamp synchronization solution, and I came up with a great idea.
I built a TrackTimeline helper class which represents a video or audio track - it can be started & stopped, paused & resumed, and even supports nesting pauses without issues.

The total duration of the video is summed up from the difference between the first and the last actually written timestamps, minus the total duration of all pauses between a video. No more incorrect video.duration! 🥳
Whereas before I just had a 4 second timeout if no frames arrive, I now just wait twice the frame latency (a few milliseconds) to ensure no frames are left out at maximum! 🎉
A video can be stopped while it is paused without any issues, as a pause call is taken into consideration before stopping 💪
A video file's session now exactly starts at the start() timestamp, and ends at the exact timestamp of the last video frame - this ensures there can never be any blank frames in the video, even if the audio track is longer 🤩

This was really complex to built as I had to synchronize timestamps between capture sessions, and the entire thing is a producer model - a video buffer can come like a second or so later than the audio buffer, but I need to make sure the video track starts before the audio track starts, and ends after the audio track ends - that's a huge brainf*ck! 🤯😅
There's also no helper APIs for this on iOS, and it looks like no other Camera framework (not even native Swift/ObjC iOS Camera libraries) support this - they all break when timestamps have a delay (e.g. video stabilization enabled) (or dont even support delays at all) ; so I had to build the thing myself.
Check out this PR and try if it fixes the issue for you; https://github.com/mrousavy/react-native-vision-camera/pull/2948
Thanks! ❤


Fine Tuning Mixtral 8x7b

Hi there,
Thanks for the scripts and posts! I am interested in fine-tuning Mixtral 8x7b on sagemaker. The task I have requires around 8k token length.
I have tried running training following this tutorial: https://solano-todeschini.medium.com/fine-tune-mixtral-8x7b-on-aws-sagemaker-and-deploy-to-runpod-6bbb79981d7b#31b4, but using this updated script instead https://www.philschmid.de/sagemaker-train-evalaute-llms-2024.
The first post uses a ml.g5.24xlarge instance, which, funnily enough, has no sharding or fsdp parameter set up. When I try running the same setup with increased context length, I get an OOM. I went up to a ml.g5.48xlarge instance with 192 GB VRAM, but nothing changed.
I also looked into this: https://www.philschmid.de/sagemaker-fsdp-gpt and tried setting fsdp up by adding 'fsdp': '"full_shard auto_wrap"'
The estimated setup cost, according to this chart https://github.com/hiyouga/LLaMA-Factory#hardware-requirement, should be around 30-60 GB for the model? How much does the context length affect?
I also saw that here https://github.com/philschmid/sagemaker-huggingface-llama-2-samples/blob/master/training/sagemaker-notebook.ipynb you are using a much larger instance, but not sure if that's because that was old or not.
PS: I am using pretty much the same parameters you do in the post except the max_seq_len, with the addition of fsdp
Any insight would be greatly appreciated.

Are you trying to fine-tune Mixtral with Qlora and FSDP on a g5.48xlarge?

I still couldn't resolve this, any idea on how to approach? HF docs are pretty weak on Sagemaker + Model Parellel Distributed Training

Also accelerate doesn't seem to have Model Parallel option still


Legislator Profiles - Secondary Research

Expand the profile types, to include 1) state legislators (rep + senator) and 2) candidates for state legislature.
Current Status (Updated Feb 27th):

Akhil has made scripts and revised them. Ready for review.
HAs added availability and consent form.
Matt had conversation with stakeholder, waiting on results.

Next Steps

Recruit participants.
Provide more feedback if needed

Feb 27th -

Review script for wordings. Minqi and Constantin.
Have we looked into what legislators want or their staff, etc.

Discussion notes from Feb 27th -

One concept is to create auto generated profiles (using ballotpedia or another surveying tools candidates already do)
For incumbents wen can show voting history or amendment votes. (May be difficult to have a focus on counts as some sessions votes aren't recorded)
Legislators can claim the profiles if they wish to show their info
@mvictor55  to share sites (https://justfacts.votesmart.org/candidate/political-courage-test/15237/michael-moran)


[KYLO-2572] The 400 error (bad request) is caused by an revision issu…

[KYLO-2572] The 400 error (bad request) is caused by an revision issue. NiFi uses revision version or clientId to validate client's update request. If it doesn't increase the version at that time, it gets 400 error when it try to reset the processor status to 'running'

SonarQube analysis reported 14 issues

 4 critical
 6 major
 4 minor

Top 10 extra issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 AbstractNiFiControllerServicesRestClient.java#L105: Refactor this method to reduce its Cognitive Complexity from 31 to the 15 allowed.
 AbstractNiFiControllerServicesRestClient.java#L127: Define a constant instead of duplicating this literal "PROCESSOR" 3 times.
 AbstractNiFiControllerServicesRestClient.java#L134: Define a constant instead of duplicating this literal "ControllerService" 3 times.
 AbstractNiFiControllerServicesRestClient.java#L157: Define a constant instead of duplicating this literal "DISABLED" 4 times.
 AbstractNiFiControllerServicesRestClient.java#L9: This block of commented-out lines of code should be removed.
 AbstractNiFiControllerServicesRestClient.java#L173: Remove this useless assignment to local variable "updatedService".
 AbstractNiFiControllerServicesRestClient.java#L182: A "NullPointerException" could be thrown; "controllerServiceRevisions" is nullable here.
 AbstractNiFiControllerServicesRestClient.java#L197: Remove this expression which always evaluates to "true"
 AbstractNiFiControllerServicesRestClient.java#L326: Remove this expression which always evaluates to "true"
 AbstractNiFiControllerServicesRestClient.java#L326: Remove this expression which always evaluates to "true"


Bump merkle library to latest version

This is primarily to pull in https://github.com/transparency-dev/merkle/pull/140 now to confirm it doesn't have any suprises while I'm still context loaded on the issue. Better that than it surprising someone down the road.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 33.40%. Comparing base (3c58af4) to head (3673856).
Report is 104 commits behind head on main.

:exclamation:  There is a different number of reports uploaded between BASE (3c58af4) and HEAD (3673856). Click for more details.
HEAD has 3 uploads less than BASE

Flag
BASE (3c58af4)
HEAD (3673856)

4
1

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #267       +/-   ##
===========================================
- Coverage   51.05%   33.40%   -17.65%
===========================================
  Files          11       23       +12
  Lines         903     1383      +480
===========================================
+ Hits          461      462        +1
- Misses        374      823      +449
- Partials       68       98       +30

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Flip cards on mouseover

From filterable-landscape created by dankohn : cncf/filterable-landscape#34
On mouseover, the cards should flip while staying in place like on https://dribbble.com/. This should show the description and one or two other fields.

@dankohn the cards are flipping, I've made the description to appear on the back side:

Please say, what other fields do you want to see there

Thanks, but I've decided I'd rather not include this functionality after all.


Add timer for when to refresh AWS credentials

The targets that refresh AWS credentials take a while to run when all dependency targets have been built. ~20 AWS refreshes in a row takes ~30 mins. I think we should add a timer that is used within each of the AWS refresh targets to indicate if the credentials should be refreshed or not.

Update: The time is largely spent pulling the dummy_var from S3. Generating the credentials file is quick. As far as I can tell, targets will load all of the dependency targets before executing the command. So, I'm not sure how to speed up these AWS refresh targets. I think in the future it will be best to include the generate_credentials() function at the end of every long-to-run target / function.


Soldermask around vias

In version 0.1.0 soldermask clearance around vias is at JLCPCB's minimum. As a result some vias are soldermasked, some are not. Everything works, but such random pattern looks badly.

This problem seems to be more complex than it seems. The fact is that all vias are marked to be tented (covered with soldermask). There is nothing on mask layer. The other thing is that, when designer decides not to tent vias, then he should add clearance around via ring to +0.05mm, which is unsupported by KiCAD at the moment AFAIK.
So the only improvement at the moment is to check "Do not tent vias", when generating Gerbers. This could, but might not solve the problem. But on the other hand, sometimes tenting vias is good idea (e.g. BGA balls, maybe close to pads?).


kubectl get logs does not return all expected log entries

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT (possibly)
Seeing this on two clients (aws linux and darwin) and a single shared server, debian.
Kubernetes version (use kubectl version):
My Local mac
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.3", GitCommit:"2bba0127d85d5a46ab4b778548be28623b32d0b0", GitTreeState:"clean", BuildDate:"2018-05-21T09:17:39Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.6", GitCommit:"9f8ebd171479bec0ada837d7ee641dec2f8c6dd1", GitTreeState:"clean", BuildDate:"2018-03-21T15:13:31Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

AWS Ec2 box:
Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.4", GitCommit:"9befc2b8928a9426501d3bf62f72849d5cbcd5a3", GitTreeState:"clean", BuildDate:"2017-11-20T05:28:34Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.6", GitCommit:"9f8ebd171479bec0ada837d7ee641dec2f8c6dd1", GitTreeState:"clean", BuildDate:"2018-03-21T15:13:31Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

Environment:

Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Server AWS Hosted, kops deployment, k8s-1.9-debian-jessie-amd64-hvm-ebs-2018-03-11 (ami-4bfe6f33)
Others:

What happened:
What you expected to happen:
Was noticing our logging ETL was dropping records. Narrowed this down to the step in the process that gathers logs from k8s by way of kubectl. This uses a command such as this, once a minute:
kubectl --namespace NS logs POD_ID --since-time 2019-03-07T14:35:34.315Z
In debugging, I generated large volumes of known log records and asserted their passage through the etl. It appears that kubectl get logs is returning only some of the logs I expect. For example, generating an expected 30,000 log messages, the command kubectl --namespace NS logs POD_ID returns only the last 4719 messages, a total of 3044213 bytes.
Use of --limit-bytes flag does not appear to change this behavior. Is it possible that get logs may be enforcing some hard coded byte limit or perhaps some other misconfiguration?
How to reproduce it (as minimally and precisely as possible):
Generate a large volume of log entries and either ask for all logs since container start or with a timestamp far enough back in time to have the resulting log payload large enough.
Any insight is appreciated.

Actually, nevermind. This can likely be explained by logrotate on max file size occurring between get logs commands. Feel free to reopen or comment, but that seems like the most obvious explanation


Add: Ellada TV

Channel Name
Ellada TV
Alternative Names (optional)
No response
Network (optional)
No response
Owners (optional)
No response
Country
GR
Subdivision (optional)
No response
City (optional)
Sparta
Broadcast Area
c/GR
Languages
ell
Categories (optional)
general
NSFW
FALSE
Launched (optional)
No response
Closed (optional)
No response
Replaced By (optional)
No response
Website (optional)
https://elladafm.gr/webtvnew/
Logo
https://www.lyngsat.com/logo/tv/ee/ellada-tv-gr.png
Notes
No response

Are you sure it's not http://www.elladatv.gr/?

You're correct: thanks and edited.


ls: cannot access 'c': Input/output error

Windows Build Number
Microsoft Windows [版本 10.0.19043.1165]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
Ubuntu18.04
Other Software
Visual Studio Code with extension:Remote-WSL-v0.58.2
Repro Steps
step1: open vscode,connect to wsl,and reports error:
sh: 1: /mnt/c/Users/admin/.vscode/extensions/ms-vscode-remote.remote-wsl-0.58.2/scripts/wslServer.sh: Input/output error
step2: open wsl,use commond 'ls /mnt/,and reports error:
ls: cannot access 'c': Input/output error
Expected Behavior
vscode can connect to wsl
ls can access 'c'
Actual Behavior
ls: cannot access 'c': Input/output error
Diagnostic Logs
No response

Will wsl --shutdown help with your problem?
Not sure if you are hitting the same problem with #6174 or #3256.
Without a log, you may check dmesg in Ubuntu first. most likely you will see a error

Well， it's ok  after running commond 'wsl --shutdown'
Thanks!


feat: add profile and settings on home sidebar

In the home sidebar we should add a link to the user profile and settings pages, using "user" and "cog" icons like this:

Depend on #217 and #291

Is the profile link in the this sidebar different from the user profile link elsewhere ?

@wa0x6e No

This will be weird, since this looks like it will show my profile, but if I click on other user's profile, it will also have this sidebar

I think I get confused with your comment, profile page shouldn't have sidebar, I'm just saying adding "Profile" to the sidebar for home pages

Closed on #300


Hate to be that guy but..

Is there any way at all this could be ported to 1.16? i would greatly appreciate this as this was JUST the mod I was looking for, thanks.

I don't have any plans to back-port it to 1.16.5, but the stuff is open source, so someone else could do the port if they want, the primary code for this mod is this section of the ThutCore api:
https://github.com/Thuts-Mods/ThutCore/tree/1.18/src/main/java/thut/api/block/flowing


php artisan migrate --path option seems to be broken

Running php artisan migrate --path=/app/database/migrations/foo/ does not run the migrations under that directory. Output in the terminal is "Nothing to migrate".
The same issue seems to exist if the --path=/app/database/migrations/ as well (which is the default directory to run)

In my case, php artisan migrate --path=database/migrations/foo is enough. The app directory is not necessary.

thanks @zzpwestlife . That worked for me.

thanks @zzpwestlife. It 's worked like a charm

Open Illuminate\Database\Migrations\Migrator.php file. At line 430 (Migrator::getMigrationFiles()). Replace return $this->files->glob($path.'/.php'); with return Str::endsWith($path,'.php') ? [$path] : $this->files->glob($path.'/.php');
Now the --path option will work normally


doesn't appear to work with Electron

I'm possibly having Docker issues (tho docker works fine on my system generally)
even so, none of the menus read 'electron' -
and there's been no commit to repo since the electron's release.
so I'm writing for a Y/N as to whether or not we should expect local compilation to work with the Electron.

That is correct. We have to add support for Electron. Current sprint is focused on improving Build IDE but next one should take care of Dev issues (including this one).

This should be included in the README. I spent a long time trying to get this plugin to work only to find out it won't work with the Electron.

A whitelist of supported platforms should be added to the README. As this package exists, this is essentially a booby trap for people working on the electron...

lack of local compiler made me not want to work on the platform. I've not touched it since this.
Is there now a local compiler ?


Could we get a new version uploaded to PyPI?

https://pypi.org/project/ChatExchange/#history shows version 0.0.4 uploaded in 2018. It would be nice to get the bug fixes from the last few years uploaded there for wider consumption and visibility.

I'll try to do this when I get a chance

Issthere something a volunteer could help out with? For example, a Github workflow to upload to test PyPI (and eventually to prod under some conditions, probably to be hashed out in more detail) should be within reach for someone to contribute if it's not something you already have somewhere. Unearthing the commits which correspond to previous releases so they can be tagged appropriately on Github would also be vaguely useful, I imagine.

Both would be helpful, yes.
It's taking a while because I'm travelling rn and primarily using my work computer; and while I have my personal laptop I'm not using it during the day so I'm not able to cut a release.


Fix for user library error conflicting with the wishlist.

Wishlist is only rendered when there are no errors. Because I have no games in my library an error is being raised which conflicts with the wishlist. As a result the wishlist also believes there are no games.
https://github.com/jolupa/stdbgames/blob/e7a39c2fd7996fea169327cfbe7a3b1625d9452f/app/Controllers/Libraries.php#L13
https://github.com/jolupa/stdbgames/blob/604a663abfef0b87ff461804e6646c5559df8b88/app/Views/wishlists/userwishlist.php#L1-L9
I've opened a PR to resolve the issue, though it bypasses the errors altogether. Also I've renamed the wishlist variable within the foreach loop to avoid confusion and unwanted side effects. Also note this hasn't been tested as I don't have your project set up.

Hi thanks for the patch I didn't sae it before because apple shuts down my email account and can verify the patches, tomorrow I will try it on local machine but I think they're ok.
I will be continue the project on here https://github.com/jolu-pa/stdbgames thanks a lot!!

Hi thanks for the patch I didn't sae it before because apple shuts down my email account and can verify the patches, tomorrow I will try it on local machine but I think they're ok.
I will be continue the project on here https://github.com/jolu-pa/stdbgames thanks a lot!!

@jolu-pa No probs! FYI, I sent you a PM on Twitter regarding an authentication bug that I came across. 🕵♂

@jolu-pa No probs! FYI, I sent you a PM on Twitter regarding an authentication bug that I came across. 🕵♂

DM answered! I will try to fix all later! When I come out of work! Also thanks a lot!

DM answered! I will try to fix all later! When I come out of work! Also thanks a lot!


"staleness indicators"

maybe bring back the gantt chart? point is to show when components are "stale." two types of stale:

component was run a long time ago
there are "fresher" runs of the component

See #165 and #161


WIP: Signal result of tap-install-script back to the stack

Congratulations, your PR made it through the pipeline! :tada:

Your PR sadly failed, please check here

Your PR sadly failed, please check here


Update Files.pt-BR.xlf

Fix missing translations for pt-BR

The state of the translated strings must be "translated"
state="new" --> state="translated"

Thank you!


Breaking change introduced in 5.1.0

Related plugins

[X] plugin-vue

[ ] plugin-vue-jsx

Describe the bug
This is simply to raise a concern regarding the breaking change introduced in 5.1.0 for setting custom features (e.g. propsDestructure). My Nuxt 3 application suddenly stopped working as I'm using propsDestructure by default and it took me a while to realize that it was due to the latest @vitejs/plugin-vue package update. I'm just raising the issue in case other packages/libraries/frameworks relying on it face the same issue.
Related: https://github.com/nuxt/nuxt/issues/28295
Reproduction
https://stackblitz.com/edit/github-g3udp4?file=nuxt.config.ts
Steps to reproduce
No response
System Info
-

Used Package Manager
pnpm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I have a breaking change in 5.1.0 as well, builds are breaking with
Expected ">" but found "lang"
It's really tough to debug as it was working locally, broken in CI. Rolling back the version to 5.0.5 fixed it.
Here is link to build
https://github.com/fictionco/fiction/actions/runs/10084436525/job/27883222507

Could you please provide a minimal reproduction or at least a detailed method to easily reproduce the build error on the local machine?

@sxzz i would love to but I couldn't duplicate this outside of CI.
All I know is rolling back the dep fixed the problem.
Will try again in a couple days.

@sxzz Another similar report found. https://github.com/dcloudio/uni-preset-vue/issues/102

Should be fixed in v5.1.1

I would add that although propsDestructure is experimental, I don't think the way to enable/disable it should break unexpectedly. At the very least until it is stabilised, I would suggest preserve backwards-compatibility for how to enable/disable this feature, which would be a one-line change.

@danielroe Thanks for your advice. It's fixed!

Thank you ❤

I have a breaking change in 5.1.0 as well, builds are breaking with
Expected ">" but found "lang"

I'm experiencing the same error on 5.1.0 - 5.1.2, it happens when building a production build in the server bundle.

Could you create a new issue with a reproduction?

@sxzz updating @vitejs/plugin-vue from version 5.1.0 to 5.1.1 breaks the PWA build. I manually reverted the changes in node_modules from this commit f5eb5ac5c0517c6718b8b0caca965ad640161d7f, and everything works fine. I wasn't able to create a reproduction to demonstrate the issue. However, I can provide the error log from the build:
> vite build --ssrManifest --outDir dist/client

vite v5.4.1 building for production...
✓ 1170 modules transformed.
x Build failed in 7.20s
error during build:
[vite-plugin-pwa:build] Unexpected token, expected "," (1:8)
file: /home/negezor/projects/shiromu/web-service/src/components/EventCard.vue?vue&type=script&setup=true&lang.ts:1:8
    at constructor (/home/negezor/projects/shiromu/web-service/node_modules/@babel/parser/lib/index.js:349:19)
    at TypeScriptParserMixin.raise (/home/negezor/projects/shiromu/web-service/node_modules/@babel/parser/lib/index.js:3247:19)
    at TypeScriptParserMixin.unexpected (/home/negezor/projects/shiromu/web-service/node_modules/@babel/parser/lib/index.js:3267:16)
    at TypeScriptParserMixin.expect (/home/negezor/projects/shiromu/web-service/node_modules/@babel/parser/lib/index.js:3577:12)
    at TypeScriptParserMixin.tsParseDelimitedListWorker (/home/negezor/projects/shiromu/web-service/node_modules/@babel/parser/lib/index.js:7654:14)
    at TypeScriptParserMixin.tsParseDelimitedList (/home/negezor/projects/shiromu/web-service/node_modules/@babel/parser/lib/index.js:7631:25)
    at TypeScriptParserMixin.tsParseBracketedList (/home/negezor/projects/shiromu/web-service/node_modules/@babel/parser/lib/index.js:7671:25)
    at TypeScriptParserMixin.tsParseTypeParameters (/home/negezor/projects/shiromu/web-service/node_modules/@babel/parser/lib/index.js:7773:24)
    at /home/negezor/projects/shiromu/web-service/node_modules/@babel/parser/lib/index.js:9410:29
    at TypeScriptParserMixin.tryParse (/home/negezor/projects/shiromu/web-service/node_modules/@babel/parser/lib/index.js:3585:20)

For now, I have locked the version of @vitejs/plugin-vue to 5.1.0.

@negezor Could you please raise a new issue & provide a minimal reproduction? Thanks.

Why reproduction is required


Support documenting namespace packages

I am hoping to use sphinx-autodoc2 to document PEP 420 namespace packages. These are packages which are assembled together via multiple "distributions" which each provide a submodule within the namespace package. The way this is encoded in the package definition on the filesystem is that the directory which defines the namespace package contains submodules, but does not contain an __init__.py to define it as a module itself.
sphinx-autodoc2 walks the directory tree of all packages and assumes that there will be a Python file for each module that is then parsed by Astroid. Normal packages have the __init__.py but namespace packages do not. This PR changes the module enumeration code to detect when it has been instructed to find all modules in a namespace package and encode that in the module list as the directory path itself represents the module. Then (conveniently) we can use some existing Astroid namespace module builder code to produce the same AST stuff for the rest of the documentation generation pipeline.

Hi,
I wanted to try sphinx-autodoc2 on a package that uses this namespace package.
I was happy to see this PR, and I decided to give it a try.
I got a TypeError exception because at some point the sphinx-docutils package through its system_message function was trying to call  our get_source_and_line() with an li value set to None. For context:
This is the implementation of get_source_and_line (in this package):
https://github.com/sphinx-extensions2/sphinx-autodoc2/blob/1f55a8872cccd235cafa6323e2ae8c3a563156f4/src/autodoc2/sphinx/docstring.py#L141-L144
This is the caller function:
https://sphinx-docutils.readthedocs.io/en/latest/_modules/docutils/utils.html#system_message
So I had to patch this pull request with the following commit:
https://github.com/zeehio/sphinx-autodoc2/commit/564b7169da59bbe154deb380b99c4ffae72dcc60
I guess that since a namespace pkg does not have a file, it's one of the few cases where sphinx-docutils sets li to None, and autodoc2 wasn't ready for that.
I sent a PR to your branch @davidselassie to include my commit in this PR

Besides my small commit, everything else in this PR worked great for me.


Add support for custom format validators

It would be nice if there would be a way to implement validators to support custom formats.

Good idea, but Im not sure if this is required: Just implement an own class inheriting from to JsonSchemaValidator and override protected Validate(...). There you can validate custom formats or call the base impl

I think it would be much easier to have some interface for validators (i.e. IJsonSchemaFormatValidator) and have possibility to add them to the validator instance. If that's too much, then there could be a protected virtual method ValidateFormat in JsonSchemaValidator that would contain format validations now existing in ValidateString method.


Using new StringRouteConstraint for area constraint

related to #4846 MapAreaRoute constraint not escaped
@rynowak @Eilon @sebastienros

:up: :date:

LKGTM. I'll let @rynowak sign off on this.

🆙 :date:

:shipit: from me, I'll take care of merging

Merged as  6e5187c1ae731b09ff2bd94d65fc6c670be735f3 - @iscifoni Thanks! :+1:


Navigation URLs being resolved only for root

Hi !
First of all, thanks a lot for the lovely template and the excellent work you've done with it.
Coming to the gist, I'm very noobish when it comes to JS, so please correct me if I'm doing something wrong. The issue is as follows:
Whatever URLs I add to the Navigation list, they're resolving to root URL
Ex:
(Assume root is example.com)
Say I'm adding,
About: example.com/about
Google: google.com
Now, on the home page, two buttons, About, Google are created. But both of them point only to example.com, not to their respective URLs.
I tried using {{log url}} within the {{for each}} blog in links.hbs. The logged output looks good. (/about, google.com).
So I'm wondering where it goes wrong.
Live site: gln.me

I am also having exactly the same problem. Any workaround ?

I was experiencing the same issue.
Looks like the builtin Ghost {{url}} helper overrides {{url}} attribute even inside the {{#foreach @blog.navigation}} loop.
One way to solve this is to rename links.hbs into navigation.hbs and include it with {{navigation}} helper instead of {{> links}} and loop over just navigation instead of @blog.navigation.
However there is also a more elegant fix: just use {{this.url}} instead of {{url}} - https://github.com/jcdenton/uno-zen/commit/3ec11ecfce4ca9f8045fab7c842fe6148054f9b8.

I managed to fix the issue. I removed the foreach loop in links.hbs and added the page links like the previous versions of this theme. My links.hbs looks like this now.

Home
Blog
About
Contact

@ayon115 Thought that would definitely work, that is not a solution after all :)
@jcdenton What you've told sounds probably, but as I've mentioned, I logged the url INSIDE the {{for each}} block and the logged url appeared proper. I just used {{log url}}. Since the logged url was proper, I wonder where it gets messed up when passed to href.

@glnarayanan and does my explanation about the attribute being overridden by the builtin {{url}} helper contradict the fact that {{log url}} would work as expected? BTW using {{this.url}} just confirms this.

thank you for report this. Somebody can create a PR with the solution?

@glnarayanan Well, may not be a good solution, but it's working for me. Here's my steps to make it work in my website.

Edit links.hbs like my earlier message.
Add appropriate in Navigation in Ghost Settings panel. (Ex. http://base_url/about)
Create static page content with a post from Ghost Settings panel. (Ex- about me page contents)
Create page in theme's root directory with name like page-pagename.hbs (Ex - page-about.hbs).
Such a page of mine looks like this

{{!< default}}
{{#post}}

About me

      {{content}}

{{/post}}

Restart Ghost

@ayon115 absolutely works setup manually the markup, but the idea is integrate as soon as possible the themes with the Ghost API.
BTW, related: http://themes.ghost.org/docs/navigation
the current code generator of the themes is:
{{#foreach @blog.navigation}}
        {{label}}
{{/foreach}}

I think that could be enough using {{url absolute="true"}} . Let's try

I've tried it already, didn't work for me.

Fixed in #54 and available in 2.3.5 tag.
Notes that all external links of the blog are opened with target=_blank!


folsom_sample_uniform sampling error

folsom_sample_uniform does not generate a true random sampling of the values.
Once the reservoir is full each new value is replacing an existing value in the reservoir.
This causes a bias for later values.
e.g.

lists:foldl(fun(V,A) -> folsom_sample_uniform:update(A,V) end, folsom_sample_uniform:new(5000),lists:seq(1,50000)).
lists:sum(folsom_sample_uniform:get_values(S))/5000.

gives an arithmetic mean of ~45000 instead of the expected 25000
Exactly which algorithm in the Vitter paper is supposed to be implemented here?

I was attempting to implement "Algorithm R". Used https://github.com/codahale/metrics/blob/development/metrics-core/src/main/java/com/yammer/metrics/stats/UniformSample.java as a reference.


Fixes Issue #66 - Transfer DoS 2nd Proposal

This PR solves the issue #66.
It proposes to prevent a possible DoS withdraw attack, where an attacker prevents everybody to withdraw any funds from the root-contract by making this withdraw request throw all the time.
This is prevented by avoiding the transfer function during the finalizeExit call and only crediting balances, which can be withdrawn later.
In order to prevent any race on the withdraw requests of the balance, it is ensured that never more balances are credited, as there are funds in the contract available.
For this, I calculate the virtualBalance = sum of all deposits - sum of all withdraw request went through finalizeExit.
If virtualBalance < 0, then the chain operator was malicious and in this case stop the finalizeExit method.
While the proposed switch of transfer to send would also work for Ether, I prefer my solution, as it would also work for generic ERC20 Tokens.

I think you're missing the check that virtualBalance > 0.
Another (less important) case: if the attacker ever receives an invalid balance, then they'll effectively be able to immediately steal from anyone who deposits into the contract in the future. Note that we can probably assume that if the attacker has an invalid balance, then the chain is byzantine and people probably shouldn't be using it. The current implementation also has this problem.

Thanks for reviewing my PR.

I think you're missing the check that virtualBalance > 0.

It throws here virtualBalance = virtualBalance.sub(currentExit.amount); if the virtualBalance would turn negative.
I know, its not brilliant, since then all executed code is reverted. But since the while loop needs anyway some more optimiazation in order to not run out of gas, I thought I would leave this to another PR. There needs to be some restriction on how many loops are taken in the while loop, in order to not run out of gas. Depending on how this restriction is chosen, we can also check virtualBalance>0.

Another (less important) case: if the attacker ever receives an invalid balance, then they'll effectively be able to immediately steal from anyone who deposits into the contract in the future. Note that we can probably assume that if the attacker has an invalid balance, then the chain is byzantine and people probably shouldn't be using it. The current implementation also has this problem.

I thought exactly about the same problem. Unfortunately, there is no easy solution that crosses my mind. Currently users first have to check that the plasma chain operates well. But the plasma operator could also wait to become malicious, as a high deposit to the plasma chain is on the fly, but not yet confirmed  by the root chain.

Also closing for now, as per #67. I think this is something we can come back to for production work.


Error when running DFN half-cell without a lithium plating parameter set

PyBaMM version - $ python -m pip show pybamm: 21.9
Python version - $ python --version: any

Describe the bug
At the moment, if you try to use the PyBaMM half-cell model with a parameter set that doesn't include lithium plating (like the default one) it throws a rather non-informative error:
KeyError: KeyError("'Typical plated lithium concentration [mol.m-3]' not found. Best matches are ['Typical electrolyte concentration [mol.m-3]', 'Bulk solvent concentration [mol.m-3]', 'Lithium interstitial reference concentration [mol.m-3]']")

It would be good if the error was more informative.
This was identified by @sklein-ise in #1717.

Default parameter set for a half-cell model is now "Xu2019"

Hello,
Could you please revisit to this issue? what should we do for half cell when we have customized parameter sets?

Either copy any missing parameters from Xu2019 or use very high values so that the overpotential from the lithium metal anode is zero
{
        "Negative electrode OCP [V]": 0.0,
        "Negative electrode conductivity [S.m-1]": 1e7,
        "Typical plated lithium concentration [mol.m-3]": 76900.0,
        "Exchange-current density for plating [A.m-2]": 1000,
        "Negative electrode thickness [m]": 1e-5,
    }


Minimize unnecessary message deserialization

Part of https://github.com/microsoft/vscode-jupyter/issues/5662
Simple change, deserialization is a little slower, hence using plain string operations over deserialization.

Codecov Report

Merging #6946 (7946ea8) into main (13cf495) will increase coverage by 0%.
The diff coverage is n/a.

@@          Coverage Diff          @@
##            main   #6946   +/-   ##
=====================================
  Coverage     65%     65%
=====================================
  Files        410     410
  Lines      28528   28528
  Branches    4263    4263
=====================================
+ Hits       18584   18628   +44
+ Misses      8316    8272   -44
  Partials    1628    1628

Impacted Files
Coverage Δ

...ent/datascience/jupyter/pythonVariableRequester.ts
65% <0%> (-2%)
:arrow_down:

...client/datascience/kernel-launcher/kernelDaemon.ts
53% <0%> (-2%)
:arrow_down:

...ient/datascience/editor-integration/codewatcher.ts
68% <0%> (-1%)
:arrow_down:

src/client/datascience/jupyter/jupyterNotebook.ts
66% <0%> (ø)

src/client/datascience/jupyter/kernels/helpers.ts
73% <0%> (+<1%)
:arrow_up:

...t/datascience/notebook/vscodeNotebookController.ts
80% <0%> (+<1%)
:arrow_up:

...lient/datascience/jupyter/kernels/cellExecution.ts
71% <0%> (+<1%)
:arrow_up:

src/client/datascience/telemetry/telemetry.ts
73% <0%> (+1%)
:arrow_up:

src/client/datascience/baseJupyterSession.ts
66% <0%> (+1%)
:arrow_up:

src/client/datascience/notebook/notebookEditor.ts
41% <0%> (+1%)
:arrow_up:

... and 10 more


Allow newer RSpec version

All specs are compatible with the latest RSpec without any modification :yum:

Thanks!