webportal: allow jsonc in job submission

Allowing user to import json with comment (JSONC) on job submission page.
Addressing #1986.

To submit JSONC to PAI in vscode extension, there are two solutions:

Convert JSONC to JSON (strip comments) in client side, and submit JSON to PAI.
Make REST server able to receive JSONC as job config, also store JSONC for latter retrieving.

In fact, what I'm trying to achieve is allowing user to edit jsonc in vscode directly as the commented configuration file will be easier to read.
When user finishes their editing and wants to submit a job, they can either

...submit the file directly to web portal, without an extra step to strip the comments, which is currently not available due to web portal not allowing jsonc
...or use the extension to submit the configuration to PAI via the REST api directly, in which case the extension will take care of the conversion from jsonc to json

By allowing jsonc in web portal job submission page, the first option will be available.

Offline synced with @fanyangCS , this change could be checked-in as long as it introduces no extra dependencies. So approved, feel free to :shipit:


Android Eyesore

Describe your bug here. If you are modding, try testing your bug in a clean version of the engine instead. Also, if you're using an older version of JSE, please try the latest version/action build. Also, be sure to check the pinned 'JS Engine: Known Issues' issue, to check if your issue hasn't already been found!
When Rainbow Eyesore event on android build is activate, then the engine gives an error that cannot be closed, just restart the game

Command Prompt/Terminal/Crash logs (if existing)
No response
Have you identified any steps to reproduce the bug? If so, please describe them below in as much detail as possible. Use images if possible.
No response
Are you modding a build from source or with Lua?
Source
What is your build target?
Android
Did you edit anything in this build? If so, mention or summarize your changes.
I add a lot of songs to engine
If you use 1.12.0 or earlier, did you have Optimized Chart Loading turned on?
None
Did you check for any similar issues to what you're reporting? Check, then come back here. If there is a similar issue, then do not report the issue, otherwise it will be marked as a duplicate.
Yes

well that's kinda new

After the update the problem on Android persists

okay should be fixed on https://github.com/JordanSantiagoYT/FNF-JS-Engine/actions/runs/10973548372


laod checkpoint

Hi
thanks for this repo, is there an easy way to load a checkpoint and retrain on it?

ok I actually managed to do that with the checkpoint module. thanks!


Bug when cancel WalletConnect login

When i select WalletConnect for login and close their modal i have a spinning wheel that never end. If i reload Snapshot i still get the spinning wheel. I need to manually delete the localStorage _lock.connector to fix it.

Closing this issue was fixed in snapshot-labs/lock#10


Fixed kinematic body axis lock

Fixed axis lock for kinematic body and changed variable name to make it similar to the other bodies.
Fixes #37017

Thanks!

move lock still doesn't do anything but you closed this?

This is not closed, this a PR and it was merged.


Refactor lb_sensitive_port_is_exposed_to_entire_network query for CloudFormation

Platform
CloudFormation
Description
The load balancer of the application with a sensitive port connection is exposed to the entire internet
Refactor and split lb_sensitive_port_is_exposed_to_entire_network into two queries lb_sensitive_tcp_port_is_exposed_to_entire_network and lb_sensitive_udp_port_is_exposed_to_entire_network
Closes #1718

@ruigomescx please don't merge yet, I want to compare the performance with the previous version.

@ruigomescx please don't merge yet, I want to compare the performance with the previous version.


WIP Expanding test coverage for the influxql package

Overall I think it looks good. Two issues:

I don't like making Test structs. I think they either a) are too simple and don't add much value, or b) they are too complicated and tightly couple tests together. The implementation you have right now doesn't seem to add much value outside of slurping and comparing so I think it's overkill. There's already an influxql_test.Iterators.ReadAll(). We could add something similar for the typed iterator test wrappers.

I think the test wrappers for the typed iterators should be moved to a regular file. They're simple enough that we can just update them manually if needed. I'd rather not add additional generated files if possible.


docs: Updates file references in API docs

Coverage remained the same at 49.621% when pulling 5e3339554afad5b09eaf5bb97e7ac5732fd6467d on docs into 1509a6b21b85308dc9508fcf3899221b653a43e2 on master.


Add NATS JetStream Store Plugin

I have created a Store plugin for NATS JetStream, as NATS offers both a keystore and an object store, I found it useful to use NATS for both my pub/sub, events, and store.
For this plugin I used the ObjectStore, allowing you to store an unlimited amount of data within a single key, as the keystore is limited to 1mb.
Test coverage is 86%

@xpunch

@Davincible seams the unit tests failed

It's an issue with the nats server. They pas 8/10 times locally, but sometimes it throws the context deadline exceeded like here. Tests themselves pass

I've invited you as member of this org, which was created by asim, and very welcome for those who willing to contribute to go micro.


refactor: reduce compiled schema size

Current dependencies on/for this PR:

main

PR #31

PR #32   👈

This comment was auto-generated by Graphite.

Graphite Merge Job
Current status: ⏳ Queued to merge
This pull request is currently queued to be merged as part of a stack.
This comment was auto-generated by Graphite.

Job Reference: 9BzgHsfDernqvMzHCN2o

Graphite Merge Job
Current status: ⏳ Queued to merge
This pull request is currently queued to be merged as part of a stack.
This comment was auto-generated by Graphite.

Job Reference: 4q7XSmmn1AMhDgyvtGlo


To increase the size of dark/light mode button

Current Behavior
I would like to contribute to the project by suggesting an improvement to the dark/light mode button. Currently, the button is small and not very visible, especially in the bottom left corner. I believe increasing the size of the button would make it more prominent and improve the accessibility and usability of the feature.
Desired Behavior
By increasing the size of the dark/light mode button, I propose to make it more visible and accessible, allowing users to switch between modes effortlessly. The larger size will enhance the button's clickability and improve the overall user experience.
Screenshots / Mockups

please assign me this issue i will solve under GSSOC'23


prevent crash in text-ticker

The marquee crashes in certain conditions, especially when multiple marquees are present.
It was probably caused by not properly unmounting the component (not releasing timers), causing an attempt to perform calculations on a null node.
This pull request fixes these issues.

Fantastic work, I know this bug has tripped up a few people using this. Will merge and push out a new release now!


[fastrtpsgen] ERROR: Getting platforms. null [6221]

I see this issue has been reported before https://github.com/eProsima/Fast-RTPS/issues/248 but I seem to be encountering it. I am building a container with all of the dependencies inside of it to work with FastRTPS (my Dockerfile) is below.
 -DSECURITY=ON -DBUILD_JAVA=ON \
    && cmake --build . --target install

ARG USER
ARG GROUP
ENV USER ${USER:-1000}
ENV GROUP ${GROUP:-1000}
RUN set -ex && groupadd -o -g ${GROUP} user && useradd -Nmo -g ${GROUP} -u ${USER} user

When I run the resulting container and attempt to use fastrtpsgen I get
user@4b9169cf0692:~$ fastrtpsgen HelloWorld.idl
java version "1.8.0_221"
Java(TM) SE Runtime Environment (build 1.8.0_221-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.221-b11, mixed mode)
ERROR: Getting platforms. null
user@4b9169cf0692:~$

Any ideas? There are no errors during the container build process.

A little bit of research seems to indicate that the file platforms cannot be read, is this file supposed to be in the .jar file (its not)?
user@95d0bae7f6ee:/usr/local/share/fastrtps$ unzip -l fastrtpsgen.jar | grep fastrtpsgen
Archive:  fastrtpsgen.jar
     1149  2019-08-22 13:58   com/eprosima/fastrtps/fastrtpsgen$LANGUAGE.class
    29943  2019-08-22 13:58   com/eprosima/fastrtps/fastrtpsgen.class
     1339  2019-08-22 13:58   com/eprosima/fastrtps/fastrtpsgen$TemplateErrorListener.class

Hi @salerio-gs

unzip -l fastrtpsgen.jar | grep fastrtpsgen

This command will not find the platforms file as you are grepping by fastrtpsgen instead.
You should find the file if you execute:
unzip -l fastrtpsgen.jar | grep platforms
In any case, this is a recurrent issue hard to reproduce from our side, so we are going to remove that file. There exists a PR with this done: 1
Note that Fast-RTPS-Gen is being moved from Fast-RTPS to its own project, and this PR is done to this new repository.
Best regards.

Apologies, the command I pasted is of course incorrect! Thanks for addressing the issue.

@salerio-gs try to build Fast-RTPS as non root user.


Issue with bundler while using Platform.select in release build

Is this a bug report?
Yes

Have you read the Contributing Guidelines?
Yes
Environment
Environment:
OS: macOS Sierra 10.12.6
Node: 8.2.1
Yarn: 1.1.0
npm: 5.3.0
Watchman: 4.9.0
Xcode: Xcode 9.2 Build version 9C40b
Android Studio: 2.3 AI-162.4069837
Packages: (wanted => installed)
react: ^16.2.0 => 16.2.0
react-native: ^0.52.2 => 0.52.2
Target Platform: iOS and Android
Steps to Reproduce

I have a react-native app in production for the last few months. I updated to latest react-native 0.52.2 and started to see some strange problems with Platform.select behaviour only in the release app. Values set using Platform.select were not set in certain cases. I was able to confirm it by updating the release app to print logs. I want to emphasise again that it happens only in release app and NOT in development app. Below are some code excerpts that work and don't work.
// I have a reusable module to show a context menu.
// It exposes an API `ContextMenu.show(options)` that can be used to show the context menu.
// The items in the context menu could be different on iOS vs Android.
// Below piece of code used to work before I updated to 0.52.2 but it doesn't work now.

let ctxOptions = {
  items: Platform.select({
    'ios': showDelete ? [I18n.t('takePhoto'), I18n.t('chooseFromLibrary'), I18n.t('delete'), I18n.t('cancel')] :
      [I18n.t('takePhoto'), I18n.t('chooseFromLibrary'), I18n.t('cancel')],
    'android': showDelete ? [I18n.t('takePhoto'), I18n.t('chooseFromLibrary'), I18n.t('delete')] :
      [I18n.t('takePhoto'), I18n.t('chooseFromLibrary')]
  }),
  info: Platform.select({
    'ios': {
      destructiveButtonIndex: showDelete ? 2 : undefined,
      cancelButtonIndex: showDelete ? 3 : 2
    },
    'android': {}
  })
}

// Both info and items are undefined on both iOS and Android
ContextMenu.show(ctxOptions)

// I changed the above code to not use Platform.select but just pick the right object based on Platform.OS value without changing anything else and this works

let ctxOptions = {
  items: ({
    'ios': showDelete ? [I18n.t('takePhoto'), I18n.t('chooseFromLibrary'), I18n.t('delete'), I18n.t('cancel')] :
      [I18n.t('takePhoto'), I18n.t('chooseFromLibrary'), I18n.t('cancel')],
    'android': showDelete ? [I18n.t('takePhoto'), I18n.t('chooseFromLibrary'), I18n.t('delete')] :
      [I18n.t('takePhoto'), I18n.t('chooseFromLibrary')]
  })[Platform.OS],
  info: ({
    'ios': {
      destructiveButtonIndex: showDelete ? 2 : undefined,
      cancelButtonIndex: showDelete ? 3 : 2
    },
    'android': {}
  })[Platform.OS]
}

// Both info and items are set according to the OS
ContextMenu.show(ctxOptions)

// I also changed the above statements to ternary statements using Platform.OS and that works as well.

I am using Platform.select at other places such as styles such as below where it works as expected.
const styles = StyleSheet.create({
  container: Platform.select({
    android: {
      flex: 1,
      justifyContent: 'center',
      alignItems: 'center',
      backgroundColor: 'rgba(0, 0, 0, 0.4)',
    },
    ios: {
      justifyContent: 'center',
      alignItems: 'center',
    },
  })
})

This leads me to believe that this may be an issue with the bundler used in the release app causing the values to be not set.
Expected Behavior
The values set using Platform.select should be set according to the OS
Actual Behavior
The values were not set as described above.
Reproducible Demo
I have created a new project which can be downloaded from here. In the App.js file, in componentDidMount, there are two calls: one with Platform.select and the other with Platform.OS as described above. The app will abort when Platform.select section is not commented out and wouldn't abort when Platform.OS section is not commented out only in the release builds.

Hi @varungupta85, thanks for reporting!
I was able to reproduce the bug.
Here is a smaller version for reproduction:
const select1 = Platform.select({ ios: 'ios', default: 'default' })
const select2 = Platform.select({ 'ios': 'ios', default: 'default' })
const select3 = Platform.select({ 'ios': 'ios', 'default': 'default' })

alert(`OS: ${Platform.OS}, 1: ${select1}, 2: ${select2}, 3: ${select3}`)
// expected:          OS: ios, 1: ios, 2: ios, 3: ios
// result on release: OS: ios, 1: ios, 2: default, 3: undefined

As you can see, this bug is happening when you write the object keys using quotes.
As a workaround , please remove the quotes for now, while this issue is not fixed.
Thank you!

After more investigation, it works fine on 0.51.0 and was introduced on 0.52.0.
Not sure which commit, but my guess would be this metro bundler version bump: https://github.com/facebook/react-native/commit/0bbd9f042a8ad7c7be094bd7636ca767c6f7b231
cc @rafeca

@brunolemos Thanks for investigating the issue further and wow, I didn't realise that the quotes in the key names could have caused this. I guess, I shouldn't take anything for granted 😃  Thanks for the workaround. I will check other places in my code as well where I may be using quotes in the key names.

I am a little confused by where does this problem affect and where it doesn't. For e.g., I have an object defined as below:
    CascadingAlarmIntervals: {
      '5mins': {
        label: I18n.t('minutes', {count: 5}),
        value: 300000
      },
      '10mins': {
        label: I18n.t('minutes', {count: 10}),
        value: 600000
      },
      '15mins': {
        label: I18n.t('minutes', {count: 15}),
        value: 900000
      },
      '30mins': {
        label: I18n.t('minutes', {count: 30}),
        value: 1800000
      },
      '1hr': {
        label: I18n.t('hours', {count: 1}),
        value: 3600000
      },
      '2hr': {
        label: I18n.t('hours', {count: 2}),
        value: 7200000
      },
      '3hr': {
        label: I18n.t('hours', {count: 3}),
        value: 10800000
      }
    }

This works fine even though the key names have strings.

This could have been caused by one of the changes in metro. At this point it's hard for me to bisect the actual metro change since lots of things changed between the metro version in RN 0.51 and 0.52 (we almost rebuilt the bundling logic).
If anybody is up to fix it, the logic that needs to be updated is the one in inline-platform.js, which transform the Platform.select() calls in prod to remove the non-used platforms (so if you have Platform.select({ios: require('implementation-ios.js'), android: require('implementation-android.js')});, when you build the iOS app the android code won't be included in the bundle, and viceversa).
@varungupta85 : the last code you posted should work fine (the issue only affects Platform.select() calls).


mpq-somj2hm16 open

http://forum.wc3edit.net/deprotection-cheating-f64/how-to-unhex-mpq-somj2hm16-t28627.html
stormlib not working with this files :(

Could you please send me an example to my e-mail?


feat(header): add header component

What: add header component
Why: To have the latest header component render correctly
How:

Add partials in the application layout to render the header

Media:

gif

Hey @thiagodemellobueno, here's the PR to integrate the header

Let's not merge this one til we launched the new nav elsewhere.
Talked to @hissingpanda and we're gonna issue one with the 2.5.0.nav for now

Thank you @orlando

I will update this as we need to change host by returnurl


Update dependencies (circe 0.13, magnolia 0.17)

Add FAQ on fixing derivation for indirectly-recursive types

Looks like mercator version is not published for scalajs🤔

It seems that the problem is in scalaJS version - mercator is still published with scalajs 0.6.


Support scheduling constraints in Helm-deployed clusters

Why are these changes needed?
Currently, tolerations and nodeSelector specified in the values.yaml are not being passed to the Helm deployment. This PR fixes that.
Checks

[x] I've made sure the tests are passing.
Testing Strategy

[ ] Unit tests
[x] Manual tests
[ ] This PR is not tested :(

Thanks for the contribution. We should build helm chart validation in CI later to help us check yaml.

@ebr I am trying to get some feedbacks from your side. Do you want to use helm to deploy a cluster? or prefer to use YAML directly? We do have helm charts for both operator and sample cluster. I am trying to evaluate how easy to use helm for cluster provision over YAML (kubectl)

@Jeffwan thank you for replying to me in Slack. To expand on what I said there: we had built some custom tooling to create Ray clusters from YAML+Jinja2 templates, and apply them with the Python K8s client. But this was based the old version of the CRD (from the kopf-based ray-operator). Once we switched to kuberay, it looked like we would have to do a major refactor of our code to use the new CRD. So we decided that using Helm charts from this repo would help us stay more in sync with the developments on this fast-moving project. Now I am beginning to realize this is still a challenge, because Helm charts still need to separately implement features supported by the Ray cluster spec (hence my PRs from the last few days - many thanks for the reviews and merges btw).
To answer your question: ultimately we would prefer to not use helm. But this seems to be the best middle ground right now for our users and devs to deploy Ray clusters in a parametrized fashion (helm install . --set [...] is easy enough). We don't want to force excessive YAML editing on the users. I.e., if we went with kustomize manifests, we'd still need to 1) build some CLI wrapper around it, and 2) rely on a local copy of those YAML files.
The kuberay CLI seems very promising (it essentially fulfills the same function as our homegrown tool and implements the same abstractions), but our users already have access to k8s, so exposing and securing the apiserver adds an untenable complication for us at the moment.
So it seems like the kuberay CLI without the apiserver in the middle (i.e. using the k8s client, and/or to rendering complete YAML manifests) would be the ideal solution for us, though looking through the CLI code it seems like maintaining feature parity between the CLI and the raycluster spec would still be manual (correct me if i'm wrong).
Hope this makes sense - I'd be happy to continue the conversation on Slack and/or contribute elsewhere. Thanks!


ImageProcessor fail to add image

If rewrite creation of Drawing node, it will be fixed. Currently blocked by #10.

Fixed in https://github.com/SightRo/Templatium/commit/6f899461e607b761e91d632101bd28f128be20a0.


Operator Metrics

Is your feature request related to a problem?
We should add a prometheus metrics endpoint, so the nifikop operator can be monitored
Describe the solution you'd like to see
Some custom metrics, similar to the prometheus operator
Things like total reconcile operations, error count etc
This could help spot operator bugs
Describe alternatives you've considered
No response
Additional context
No response

I discovered through working on this that most of the metrics in the linked Prometheus example are already provided by the controller runtime. There may still be additional metrics we'd like to capture but we can specify those in this issue before raising another PR.
https://book.kubebuilder.io/reference/metrics-reference.html

Off the top of my head, we could capture metrics around the following:

Number, response code, and duration of requests-by-API-endpoint to NiFi nodes/clusters
Number of CRDs a nifikop pod is actively watching

We can use a similar Metrics setup as i used in #154


AspNetCore.TestHost.TestServer - Response.OnStarting() called twice for a single request

I created an out-of-the-box template ASP.NET Core MVC web application in Visual Studio.
I then added a AspNetCore.TestHost.TestServer  and a parallel integration test to hit the home page.
This works fine.
I then added a simple Middleware class with a Response.OnStarting() callback to add a header.
Re-running the same test now results in exceptions when the headers are added:
"An item with the same key has already been added."
After adding some debug, I can see that Response.OnStarting() is being called more than once for the same request, so it is trying to update the response headers twice for a single request, causing the exception. Unfortunately, I can't see why Response.OnStarting() would be called twice. It seems the controller action is sometimes hit twice too, but that is not required to raise the exception.
If I run a non-parallel integration test, there are no exceptions.
If you have VS2015 and .net core tools installed, you can download the solution yourself and try it here:
HeadersNoWorky.zip

@jimasp any chance you can put this in a github repo?

https://github.com/jimasp/HeadersNoWork

Does it behave any differently if you make your test fully async?

@Tratcher - knocked up a quick async version here:
https://github.com/jimasp/HeadersNoWork/tree/fullasync
As you'd expect it spawns threads slightly differently so the behaviour is a little different, but the result is fundamentally the same, i.e. Response.OnStarting() is still called multiple times for a single request.
i.e. the (simplified) debug output is like this for both cases:
###CTX:3278065, url:http://localhost:5000/3  (response.onstarting() called once for url /3)
###CTX:3278065, url:http://localhost:5000/3  (response.onstarting() called twice for url /3 - with same context object hashcode)
Exception: an item with the same key has already been added

This may be related to https://github.com/aspnet/Hosting/commit/b6da89f54cff11474f17486cdc55c2f21f2bbd6b. Can you give it one more try with 1.1?

@Tratcher test project is only a month old, so it didn't occur to me someone would have used an old version!
looking at that commit, it looks very likely to be the problem.
on train, will try it when I get home and report back.
thanks.

@Tratcher  yep that fixed it, but strangely only in the full async stack branch.
I don't know why that would be?
At any rate, it's good enough for me if you want to close the issue.
(My single test was actually simulating the test runner running 100+ integration tests in parallel in the real solution, 10 or so at a time - and that now all works).
Thank you.
(/smackshead for not thinking to check the version...)


Question about the test of CIRR

When calculating the similarity between a query and images in CIRR, it seems that the entire image database only includes the reference image mentioned in the triplets, rather than considering all the images in the entire test set. This seems to be somewhat problematic.

Hi @Code-kunkun,
Thank you for bringing this to our attention! You're correct in your observation. I initially assumed that all targets had associated reference images, but it turns out there are 137 targets, approximately 6% of the dataset, without references.
I have addressed this issue in the latest commit (fba3427), so that all images are considered during similarity calculations. You can see the updated results here:

Mode
Evaluation
Recall@K
R_subset@K

K=1
K=5
K=10
K=50
K=1
K=2
K=3

Train (CIRR)
Old
49.69
78.60
86.77
94.31
75.01
88.12
93.16

New
50.41
80.96
89.35
97.64
77.25
91.04
96.34

Zero-shot
Old
38.48
66.70
77.25
91.47
69.28
83.76
91.11

New
39.28
68.22
78.94
94.65
71.23
86.22
94.02

Thanks again!
Best regards,
Lucas

You're welcome :)
I've added the functionality to evaluate on the CIRR validation set separately in the latest commit (3b3ab37). You can now run the evaluation using the command: python test.py test=cirr-val
Here are the results I obtained: {'R1': 29.7536, 'R5': 71.1552, 'R10': 82.4444, 'R50': 95.4556, 'R_mean': 61.1178}

Thanks for your quick reply!!! However, it seems that the evaluation on the validation set suffers from the same issue as mentioned earlier with the test set, namely, the entire image database does not include all the images from the validation set. I hope the authors can recheck this part of the code, and perhaps provide calculations for Recall@Subset metrics?

Regarding your concern about the validation set, I've checked that all target images in the validation set are indeed included as reference images. Here's a snippet of the code used for this check:
import json
from pathlib import Path

annotation_pth = "annotation/cirr/cap.rc2.val.json"
annotation = json.load(open(annotation_pth, "r"))
ann_ids = {ann["reference"] for ann in annotation}

val_dir = Path("datasets/CIRR/images/dev/")
val_ids = {pth.stem for pth in val_dir.glob("*/*.png")}

The result of len(val_ids - ann_ids) was 0, confirming that all validation set images are included as references.
Additionally, I’ve implemented the Recall@Subset metrics in the CIRR evaluation code, which I adapted from CIRPLANT.
The changes are in the latest commit (3ed13c5); please let me know if you find any issue.
Best regards,
Lucas

It seems like there's a discrepency between the 2165 elements in ann_ids and 2297 elements in split.rc2.val.json, and the R@1 on CIRR validation set being only 29.75 seems a bit low.

I've updated the code to be similar to the test set (926df9a). I saw that I forgot to normalize the target embeddings, the updated results are the following:
Recall@1: 41.57
Recall@5: 70.13
Recall@10: 79.91
Recall@50: 94.16
Recall_subset@1: 78.56
Recall_subset@2: 91.73
Recall_subset@3: 95.93

Thanks for your reply!!! Here are the results I reproduced on the CIRR validation set, which seems to have some differences from what you provided.
Recall@1: 54.58
Recall@5: 82.68
Recall@10: 90.07
Recall@50: 97.58
Recall_subset@1: 78.51
Recall_subset@2: 91.75
Recall_subset@3: 95.93

Nice! Which checkpoint are you using? I'm running the following:
python test.py test=cirr-val model/ckpt=cirr_ft-covr+gt

I used the same command as you 🤔


No back to top option on the main page

Actual Behaviour
There is no back to top option on the main page.
Expected Behaviour
There should be a back to top option on the main page.
Would you like to work on the issue?
YES

I would like to work on this issue

@ashupednekar I'm already working on this

Fine
On Tue, Feb 20, 2018, 7:50 PM harshJindal<EMAIL_ADDRESS>wrote:

@ashupednekar https://github.com/ashupednekar I'm already working on
this
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fossasia/open-event-webapp/issues/1719#issuecomment-366991590,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYOmbXE3DvZVqrk8THcveflpX0tE326iks5tWtS_gaJpZM4SIouh
.

Low priority. What we need is a working app before we go into other details.


Implement support for Peripheral API on iOS

The Peripheral API is implemented for Android. Add support also for iOS.

Why is this issue closed? There is still no Peripheral API implementation for iOS. Please re-open this issue and start working on it :)

@trancee Thanks, it was a mistake to close it! Issue is now open!

@trancee In fact this issue was never closed, it is "Merge periperal branch" #92 that is closed!


could you please develop a stable diffusion webui extension

yes, we are working on it, stay tuned :)

If it helps, im not a programmer, but i make it work, but i takes a long time every process :(
DragDiffusion.zip
i edited some requirements to not replace Automatic1111 requirements.

Hello, when i install this extension, it shows no module named drag_pipeline, idk how to deal with it. Thank you very much

Hello, when i install this extension, it shows no module named drag_pipeline, idk how to deal with it. Thank you very much

git clone https://github.com/Yujun-Shi/DragDiffusion
and then copy the files in the zip to the folder.

It doesnt work as extension, webui wont even start with it  cause of some gradio errors

when does this complete??

abandobed??


dsFPD: Logic for dsGetFPColor dsSetFPColor

Fix the issue of dsGetFPColor and dsSetFPColor logic where it retrieves color (single or multi) form YAML file for comparing.

available in tag 3.1.1


[top/dv] Fix chip_tap_strap tests

The test had three issues previously

There were no default pulls on the JTAG pins, so when the tb's default pull downs
were removed, x's would propagate into jtag_if when the jtag interface was not enabled.
Normally this would not matter, but the test specifically checks that the interface
is inactive with 0's.

The DFT tap test randomly toggles the JTAG pins through forces and releases.
After the last release the trst_n line can sometimes remain 0.
This causes jtag transactions to fall through and the whole test to
misbehave.

Similar to issue 1, if the jtag taps were actively driven to 0, the jtag_if
became completely floating, this also interfered with the test's expectations.

These fixes should allow the chip_strap_tap tests to run again.

ugh..i think i keep forgetting the subtlties of force / release, i think i know why now..

i've running into a few other things when i run more seeds.
I'm still debugging and will let you guys know soon.
On Wed, Oct 19, 2022 at 10:55 AM Cindy Chen @.***>
wrote:

@.**** approved this pull request.
—
Reply to this email directly, view it on GitHub
https://github.com/lowRISC/opentitan/pull/15588#pullrequestreview-1148047442,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH2RSXXKYR2MOCUDPQ5ODLWEAYZ5ANCNFSM6AAAAAARIZS2E4
.
You are receiving this because you authored the thread.Message ID:
@.***>

@weicaiyang please have a look at the latest.


Chunk file is not created if routing is more than 2 level deep

OS?

Windows 7

Versions.
angular-cli: 1.0.0-beta.24
node: 6.9.1
os: win32 x64
@angular/common: 2.4.1
@angular/compiler: 2.4.1
@angular/core: 2.4.1
@angular/forms: 2.4.1
@angular/http: 2.4.1
@angular/platform-browser: 2.4.1
@angular/platform-browser-dynamic: 2.4.1
@angular/router: 3.4.1
@angular/compiler-cli: 2.4.1
Repro steps.
Chunk file is not being created for 3rd level lazy routed module.
The log given by the failure.
No error while build or serve, errors out to fetch the Module while route is navigated.
Mention any other details that might be useful.
Here is the Plunker http://plnkr.co/edit/n5BkE5HNCK6uhDNbaZEB?p=preview which works.
But when try to build this with Angular CLI, no chunk file is created for the 3rd level lazy loaded route.

Duplicate. See https://github.com/angular/angular-cli/issues/3663

Closing this as duplicate of #3663.


podman network create: validate user input

Disallow invalid/confusing names such as '../bar' or 'foo '
Closes #4184
Signed-off-by: Mrigank Krishan<EMAIL_ADDRESS>

/approve
/ok-to-test

/ok-to-test

Other than @mheon's comments and the gating issue, LGTM

what is wrong with a network named foo ?

@baude Trailing space

LGTM

/lgtm


Add override geth binary variable

Add override geth binary variable.  Needs for HECO fork but maybe useful for other geth forks.

@mikolajsobolewski you have to generate a new readme file (make docs) if you update the version of any helm charts. You can run the linting locally make lint commands to ensure that linting would not fail in the PR.

Since version 1.0.1 of the geth chart you can now overwrite the default command via .Values.defaultCommandTemplate.
https://github.com/ethpandaops/ethereum-helm-charts/blob/geth-1.0.1/charts/geth/values.yaml#L33
That should allow you to set any custom binary in there.


Update link to gcloud-java's landing page

This PR updates the links to gcloud-java (from the docs pages) to reflect gcloud-java's shorter URL.
After a build, the link from the docs pages will look like this (see bottom of screenshot):

@ajkannan : Just wanted to let you know that you really only need a screenshot if you're changing something visual (like adding a logo or rearranging the page, or changing styles). Changing the link shouldn't change anything visual, so no screenshot required :)

LGTM


Hello Minikube

This tutorial shows you how to run a sample app on Kubernetes using minikube. The tutorial provides a container image that uses NGINX to echo back all the requests.
Objectives
Deploy a sample application to minikube.
Run the app.
View application logs.

Before you begin
This tutorial assumes that you have already set up minikube. See Step 1 in minikube start for installation instructions.
Note:
Only execute the instructions in Step 1, Installation. The rest is covered on this page.
You also need to install kubectl. See Install tools for installation instructions.
Create a minikube cluster
minikube start
Open the Dashboard
Open the Kubernetes dashboard. You can do this two different ways:
[Launch a browser](https://kubernetes.io/docs/tutorials/hello-minikube/#dashboard-0)
[URL copy and paste](https://kubernetes.io/docs/tutorials/hello-minikube/#dashboard-1)

Open a new terminal, and run:
Start a new terminal, and leave this running.
minikube dashboard
Now, switch back to the terminal where you ran minikube start.
Note:
The dashboard command enables the dashboard add-on and opens the proxy in the default web browser. You can create Kubernetes resources on the dashboard such as Deployment and Service.
To find out how to avoid directly invoking the browser from the terminal and get a URL for the web dashboard, see the "URL copy and paste" tab.
By default, the dashboard is only accessible from within the internal Kubernetes virtual network. The dashboard command creates a temporary proxy to make the dashboard accessible from outside the Kubernetes virtual network.
To stop the proxy, run Ctrl+C to exit the process. After the command exits, the dashboard remains running in the Kubernetes cluster. You can run the dashboard command again to create another proxy to access the dashboard.
Create a Deployment
A Kubernetes Pod is a group of one or more Containers, tied together for the purposes of administration and networking. The Pod in this tutorial has only one Container. A Kubernetes Deployment checks on the health of your Pod and restarts the Pod's Container if it terminates. Deployments are the recommended way to manage the creation and scaling of Pods.
Use the kubectl create command to create a Deployment that manages a Pod. The Pod runs a Container based on the provided Docker image.

# Run a test container image that includes a webserver
kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.39 -- /agnhost netexec --http-port=8080

View the Deployment:

kubectl get deployments

The output is similar to:

NAME         READY   UP-TO-DATE   AVAILABLE   AGE
hello-node   1/1     1            1           1m

(It may take some time for the pod to become available. If you see "0/1", try again in a few seconds.)

View the Pod:

kubectl get pods

The output is similar to:

NAME                          READY     STATUS    RESTARTS   AGE
hello-node-5f76cf6ccf-br9b5   1/1       Running   0          1m

View cluster events:

kubectl get events

View the kubectl configuration:

kubectl config view

View application logs for a container in a pod (replace pod name with the one you got from kubectl get pods).
Note:
Replace hello-node-5f76cf6ccf-br9b5 in the kubectl logs command with the name of the pod from the kubectl get pods command output.

kubectl logs hello-node-5f76cf6ccf-br9b5

The output is similar to:

I0911 09:19:26.677397       1 log.go:195] Started HTTP server on port 8080
I0911 09:19:26.677586       1 log.go:195] Started UDP server on port  8081

Note:
For more information about kubectl commands, see the kubectl overview.
Create a Service
By default, the Pod is only accessible by its internal IP address within the Kubernetes cluster. To make the hello-node Container accessible from outside the Kubernetes virtual network, you have to expose the Pod as a Kubernetes Service.
Warning:
The agnhost container has a /shell endpoint, which is useful for debugging, but dangerous to expose to the public internet.
Expose the Pod to the public internet using the kubectl expose command:

kubectl expose deployment hello-node --type=LoadBalancer --port=8080

The --type=LoadBalancer flag indicates that you want to expose your Service outside of the cluster.

The application code inside the test image only listens on TCP port 8080. If you used kubectl expose to expose a different port, clients could not connect to that other port.

View the Service you created:

kubectl get services

The output is similar to:

NAME         TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)          AGE
hello-node   LoadBalancer   <IP_ADDRESS>   <pending>     8080:30369/TCP   21s
kubernetes   ClusterIP      <IP_ADDRESS>       <none>        443/TCP          23m

On cloud providers that support load balancers, an external IP address would be provisioned to access the Service. On minikube, the LoadBalancer type makes the Service accessible through the minikube service command.

Run the following command:

minikube service hello-node

This opens up a browser window that serves your app and shows the app's response.

Enable addons
The minikube tool includes a set of built-in addons that can be enabled, disabled and opened in the local Kubernetes environment.
List the currently supported addons:

minikube addons list

The output is similar to:

addon-manager: enabled
dashboard: enabled
default-storageclass: enabled
efk: disabled
freshpod: disabled
gvisor: disabled
helm-tiller: disabled
ingress: disabled
ingress-dns: disabled
logviewer: disabled
metrics-server: disabled
nvidia-driver-installer: disabled
nvidia-gpu-device-plugin: disabled
registry: disabled
registry-creds: disabled
storage-provisioner: enabled
storage-provisioner-gluster: disabled

Enable an addon, for example, metrics-server:

minikube addons enable metrics-server

The output is similar to:

The 'metrics-server' addon is enabled

View the Pod and Service you created by installing that addon:

kubectl get pod,svc -n kube-system

The output is similar to:

NAME                                        READY     STATUS    RESTARTS   AGE
pod/coredns-5644d7b6d9-mh9ll                1/1       Running   0          34m
pod/coredns-5644d7b6d9-pqd2t                1/1       Running   0          34m
pod/metrics-server-67fb648c5                1/1       Running   0          26s
pod/etcd-minikube                           1/1       Running   0          34m
pod/influxdb-grafana-b29w8                  2/2       Running   0          26s
pod/kube-addon-manager-minikube             1/1       Running   0          34m
pod/kube-apiserver-minikube                 1/1       Running   0          34m
pod/kube-controller-manager-minikube        1/1       Running   0          34m
pod/kube-proxy-rnlps                        1/1       Running   0          34m
pod/kube-scheduler-minikube                 1/1       Running   0          34m
pod/storage-provisioner                     1/1       Running   0          34m

NAME                           TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)             AGE
service/metrics-server         ClusterIP   <IP_ADDRESS>    <none>        80/TCP              26s
service/kube-dns               ClusterIP   <IP_ADDRESS>      <none>        53/UDP,53/TCP       34m
service/monitoring-grafana     NodePort    <IP_ADDRESS>     <none>        80:30002/TCP        26s
service/monitoring-influxdb    ClusterIP   <IP_ADDRESS>   <none>        8083/TCP,8086/TCP   26s

Check the output from metrics-server:

kubectl top pods

The output is similar to:

NAME                         CPU(cores)   MEMORY(bytes)
hello-node-ccf4b9788-4jn97   1m           6Mi

If you see the following message, wait, and try again:

error: Metrics API not available

Disable metrics-server:

minikube addons disable metrics-server

The output is similar to:

metrics-server was successfully disabled

Clean up
Now you can clean up the resources you created in your cluster:
kubectl delete service hello-node
kubectl delete deployment hello-node
Stop the Minikube cluster
minikube stop
Optionally, delete the Minikube VM:
Optional
minikube delete

@Hellal1997 Is this the correct issue title and description you want to report? It would be helpful to provide accurate details in the description. At the moment, it seems to be a copy-paste of the tutorial page’s content rather than the actual issue.
/triage needs-information

Hey @Hellal1997 !!
As asked by @dipesh-rawat earlier, please correct the issue description so that the community can understand your concern.
I suggest going through the guide to understand raising issues in the community and more.

sure will issue descriptions

well do this

@Hellal1997 Still unclear by the community that why the issue is raised for

/close not-planned


Add requirements.txt file

You can add requirements.txt file with this command in cmd or other CLIs.
command:
pip isntall freaze => requirements.txt

You can add requirements.txt file with this command in cmd or other CLIs.
command:
pip isntall freaze => requirements.txt

pip install -r requirements.txt

To generate a list of the Python package requirements for your code, we can use the pipreqs tool. Here's how we can use it:
Install pipreqs by running the following command in our command prompt or terminal:
pip install pipreqs
Navigate to the directory containing your Python code.
Run the pipreqs command followed by the path to our code directory:
pipreqs path/to/ourcodedirectory
This command will scan our code and generate a requirements.txt file in the current directory, listing all the Python package requirements based on the imported modules in our code.
If we don't specify a directory, pipreqs will use the current directory by default.
Once the command finishes executing, we should have a requirements.txt file that contains the package requirements for our code. We can open the file to see the list of requirements.

Thanks. This is a good way, too.

If you want to open and read a .txt file in Python, you can use the built-in open() function.


LoadingModel fixes

coverage: 70.37% (+10.8%) from 59.521%
when pulling 169557fe08d6b49cb5a9849994bf8f569120b851 on loading-model-fixes
into d0228de9033c9dcd05f70ce2309b06eaffd35b26 on main.

coverage: 65.267% (+5.7%) from 59.521%
when pulling 169557fe08d6b49cb5a9849994bf8f569120b851 on loading-model-fixes
into d0228de9033c9dcd05f70ce2309b06eaffd35b26 on main.


Create wiki with api sample

[x] Example of transaction list with different types
[x] Examples of different detail responses

I have added a provisional wiki page for the purpose of the Engineering presentation: https://github.com/gnosis/safe-client-gateway/wiki

https://github.com/gnosis/safe-client-gateway/wiki
Let's re-open the issue if the samples I added are insufficient.


Remove global shortcuts when player isn't active

@feross

Fixes #263

Merged. I just forgot to force push dc/shortcuts first

:scream: force push? :scream:

You never want to force push master, but its cool to rebase and force push
feature branches before they're merged
That lets you keep a nice linear history w/out merge commits
On Mar 29, 2016 13:56, "Nate Goldman"<EMAIL_ADDRESS>wrote:

[image: :scream:] force push? [image: :scream:]
—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
https://github.com/feross/webtorrent-desktop/pull/266#issuecomment-203099290

@dcposch yep I do that with feature branches too, was worried it was master. ignore me, please carry on!


Disable section index pages in docs

Section index is required for autogenerated API docs, so this does not apply.


ESP32C6 ROM Bootloader resets PMU_TIE_HIGH_HP_PAD_HOLD_ALL upon boot (IDFGH-12130)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
I'm on the esp32c6 and I want to keep the output state of a GPIO pin low during deep sleep.

First the output in question (e.g. gpio22) is set low.
Then, before entering deep sleep,  I set the PMU_TIE_HIGH_HP_PAD_HOLD_ALL flag to 1.
I enter deep sleep (with wakeup source of some other lpio gpio e.g. gpio0)
During deep sleep the pin (gpio22) indeed hold its state (low)
After wakeup (e.g. with IO interrupt) the pin immediately turns to high, as soon as the ROM bootloader starts.

I've used the esp32 rust driver, but I think it is a ROM bug, because the part up and including sleeping works as expected.
Can you advise here?

Thank you @t-moe  for reporting this problem, I think this problem should exist on all esp chips, the reason to unhold all IOs in ROM boot is to avoid that the IOs of key system peripherals such as SPI /UART are held before reset making it impossible continue to run the flash boot.
Currently, if you want to avoid this wrong signal, you can use LP_IOs, which on esp32c6 are GPIO0~7, they don't lose configuration during deepsleep, so there is no pulse signal even if they unhold. Refer https://github.com/espressif/esp-idf/blob/master/components/esp_driver_gpio/include/driver/rtc_io.h
We are evaluating the reasonableness of this requirement, I'll update in this thread if there's any progress

Hi @esp-wzh,
Thanks for your response.
We also found that we can successfully hold a GPIO8..GPIO30 if we set the corresponding LP_AON_GPIO_HOLD0_REG[n] bit. This seems to work with the current ROM.  This probably works in our case, as a workaround. I hope this continues to work and you dont extend the ROM in future versions to also unhold this upon boot.
Regarding the initial problem:
I understand the reasoning behind the current ROM implementation, but I would expect that the technical reference manual contains a warning near the PMU_TIE_HIGH_HP_PAD_HOLD_ALL documentation. Can you add this? Also, is the "Hold all" esp32c6 specific?
Thank you

@t-moe I figured it out! the hold en signal for gpio[n] is arbitrated out by the following logic,

so there is no problem with the ROM, I have suggested to documentation colleague to add a description in this section, thanks for your feedback!

Got it, we will add these two notes to the document.


[WIP] Excluding getter-setter from sonar

@MikeEdgar I noticed, after I removed ExcludedPOJO.class from the pom the coverage went down by 8%, so I added it back. Also, trying to add<EMAIL_ADDRESS>for removing the generated class. I wanted to suggest, what do you think about removing api module completely as well from coverage?

after I removed ExcludedPOJO.class from the pom the coverage went down by 8%
There's something strange about that - there is no such class in the project. I suspect it is something else in that same commit that caused the decrease.

what do you think about removing api module completely as well from coverage?
Once the getter/setter methods are excluded, there is very little code left and I think most of it is covered. One of the earlier pushes I think had the coverage up to 62% or so right?

Once the getter/setter methods are excluded, there is very little code left and I think most of it is covered. One of the earlier pushes I think had the coverage up to 62% or so right?

Right! at commit [81a3a6d](https://github.com/bf2fc6cc711aee1a0c2a/kas-fleetshard/pull/809/commits/81a3a6dbf05765d11eb3e4ffd311a2cc4234c6a7) it went up to 62%. Once I moved all the getter/setter to a class level it went back to 59%. So I'm not sure, what's causing the various.


Fix syntax issue with automation file

Missing , during path templating.
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running

Duplicate of https://github.com/openstack-k8s-operators/ci-framework/pull/1367 I think


Arch_prctl

@nh2 this ties us to x86_64 but I guess we are not able to use 32bit kernel, right?
I suppose simple example prog doing dummy ARCH_GET_FS will be OK as a test?

This change is

this ties us to x86_64

@qrilka which part does the tying, the usage of ARCH_GET_FS? I would like to support the 32-bit use case (do we have anything else that forbids that?), so I think we should make it optional if possible.

I suppose simple example prog doing dummy ARCH_GET_FS will be OK as a test?

Yep!

Regarding 32bit I think we need a separate issue. I suppose we need a VM to run 32bit kernel, probably it makes sense to add automation code for that to the repo, what do you think? Any suggestion what to use for it? I didn't look into this topic lately, I just remember using Vagrant (with VBox probably) some years ago...

@nh2 added a test case


Reject response on error

The correct way to close a response error handler is to reject the response, not simply return it, or anything using the plugin won't be able to use the error handler clause with their promises.

Just to be clear, the interceptor overrides the behaviour for everything in the project that includes the oauth plugin. This causes some unexpected behaviour, for example where I'm returning error 400 (bad request) from my webapi backend. Instead of angular passing on the error to my error handler (of my .then call) it comes back as a "successful" response, with the error details in the response as if it was the data I requested.

Hello, I just encountered this same issue.  As vvmoppescapita  said, just returning the response will mean the error callbacks never get executed because angular will treat all responses as successful.

Agreed, silly mistake. Merged and bower version bumped up so you should be able to get it through a package update.


Request to add Fitbot

Fitbot is software for strength coaches & personal trainers to deliver workouts online and train their clients remotely.
We're proudly built with Ember :)

Woohoo. Thanks!

On Aug 24, 2015, at 12:36 PM, José Padilla<EMAIL_ADDRESS>wrote:
Merged #76.
—
Reply to this email directly or view it on GitHub.


v0.7.1 Honest Validator Updates

Submit deposit
In Phase 0, all incoming validator deposits originate from the Ethereum 1.0 PoW chain. Deposits are made to the deposit contract located at DEPOSIT_CONTRACT_ADDRESS.
To submit a deposit:

Pack the validator's initialization parameters into deposit_data, a DepositData SSZ object.
Let amount be the amount in Gwei to be deposited by the validator where MIN_DEPOSIT_AMOUNT <= amount <= MAX_EFFECTIVE_BALANCE.
Set deposit_data.amount = amount.
Let signature be the result of bls_sign of the signing_root(deposit_data) with domain=bls_domain(DOMAIN_DEPOSIT). (Deposits are valid regardless of fork version, bls_domain will default to zeroes there).
Send a transaction on the Ethereum 1.0 chain to DEPOSIT_CONTRACT_ADDRESS executing def deposit(pubkey: bytes[48], withdrawal_credentials: bytes[32], signature: bytes[96]) along with a deposit of amount Gwei.

Note: Deposits made for the same pubkey are treated as for the same validator. A singular Validator will be added to state.validator_registry with each additional deposit amount added to the validator's balance. A validator can only be activated when total deposits for the validator pubkey meet or exceed MAX_EFFECTIVE_BALANCE.
Activation
In normal operation, the validator is quickly activated at which point the validator is added to the shuffling and begins validation after an additional ACTIVATION_EXIT_DELAY epochs (25.6 minutes).
The function is_active_validator can be used to check if a validator is active during a given epoch. Usage is as follows:

validator = state.validator_registry[validator_index]
is_active = is_active_validator(validator, get_current_epoch(state))

Once a validator is activated, the validator is assigned responsibilities until exited.
Note: There is a maximum validator churn per finalized epoch so the delay until activation is variable depending upon finality, total active validator balance, and the number of validators in the queue to be activated.
Block proposal
A validator is expected to propose a BeaconBlock at the beginning of any slot during which is_proposer(state, validator_index) returns True. To propose, the validator selects the BeaconBlock, parent, that in their view of the fork choice is the head of the chain during slot - 1. The validator creates, signs, and broadcasts a block that is a child of parent that satisfies a valid beacon chain state transition.
There is one proposer per slot, so if there are N active validators any individual validator will on average be assigned to propose once per N slots (e.g. at 312500 validators = 10 million ETH, that's once per ~3 weeks).
Block header
Slot
Set block.slot = slot where slot is the current slot at which the validator has been selected to propose. The parent selected must satisfy that parent.slot < block.slot.
Note: There might be "skipped" slots between the parent and block. These skipped slots are processed in the state transition function without per-block processing.
Parent root
Set block.parent_root = signing_root(parent).
Eth1 Data
block.eth1_data is a mechanism used by block proposers vote on a recent Ethereum 1.0 block hash and an associated deposit root found in the Ethereum 1.0 deposit contract. When consensus is formed, state.latest_eth1_data is updated, and validator deposits up to this root can be processed. The deposit root can be calculated by calling the get_deposit_root() function of the deposit contract using the post-state of the block hash.

Let D be the list of Eth1DataVote objects vote in state.eth1_data_votes where:

vote.eth1_data.block_hash is the hash of an Eth 1.0 block that is (i) part of the canonical chain, (ii) >= ETH1_FOLLOW_DISTANCE blocks behind the head, and (iii) newer than state.latest_eth1_data.block_hash
vote.eth1_data.deposit_count is the deposit count of the Eth 1.0 deposit contract at the block defined by vote.eth1_data.block_hash.
vote.eth1_data.deposit_root is the deposit root of the Eth 1.0 deposit contract at the block defined by vote.eth1_data.block_hash.

If D is empty:

Let block_hash be the block hash of the ETH1_FOLLOW_DISTANCE'th ancestor of the head of the canonical Eth 1.0 chain.
Let deposit_root and deposit_count be the deposit root and deposit count of the Eth 1.0 deposit contract in the post-state of the block referenced by block_hash
Let best_vote_data = Eth1Data(block_hash=block_hash, deposit_root=deposit_root, deposit_count=deposit_count).

If D is nonempty:

Let best_vote_data be the eth1_data member of D that has the highest vote count (D.count(eth1_data)), breaking ties by favoring block hashes with higher associated block height.

Set block.eth1_data = best_vote_data.

Signature
Set block.signature = block_signature where block_signature is defined as:

block_signature = bls_sign(
    privkey=validator.privkey,  # privkey store locally, not in state
    message_hash=signing_root(block),
    domain=get_domain(
        fork=fork,  # `fork` is the fork object at the slot `block.slot`
        epoch=slot_to_epoch(block.slot),
        domain_type=DOMAIN_BEACON_BLOCK,
    )
)

Deposits
If there are any unprocessed deposits for the existing state.latest_eth1_data (i.e. state.latest_eth1_data.deposit_count > state.deposit_index), then pending deposits must be added to the block. The expected number of deposits is exactly min(MAX_DEPOSITS, latest_eth1_data.deposit_count - state.deposit_index).  These deposits are constructed from the Deposit logs from the Eth 1.0 deposit contract and must be processed in sequential order. The deposits included in the block must satisfy the verification conditions found in deposits processing.
The proof for each deposit must be constructed against the deposit root contained in state.latest_eth1_data rather than the deposit root at the time the deposit was initially logged from the 1.0 chain. This entails storing a full deposit merkle tree locally and computing updated proofs against the latest_eth1_data.deposit_root as needed. See minimal_merkle.py for a sample implementation.
Attestations
A validator is expected to create, sign, and broadcast an attestation during each epoch. The committee, assigned shard, and assigned slot for which the validator performs this role during an epoch is defined by get_committee_assignment(state, epoch, validator_index).
A validator should create and broadcast the attestation halfway through the slot during which the validator is assigned ― that is, SECONDS_PER_SLOT * 0.5 seconds after the start of slot.
Attestation data
First the validator should construct attestation_data, an AttestationData object based upon the state at the assigned slot.

Let head_block be the result of running the fork choice during the assigned slot.
Let head_state be the state of head_block processed through any empty slots up to the assigned slot using process_slots(state, slot).

LMD GHOST vote
Set attestation_data.beacon_block_root = signing_root(head_block).
FFG vote

Set attestation_data.source_epoch = head_state.current_justified_epoch.
Set attestation_data.source_root = head_state.current_justified_root.
Set attestation_data.target_epoch = get_current_epoch(head_state)
**Set attestation_data.target_root = epoch_boundary_block_root where epoch_boundary_block_root is the root of block at the most recent epoch boundary.

Note: epoch_boundary_block_root can be looked up in the state using:

Let epoch_start_slot = get_epoch_start_slot(get_current_epoch(head_state)).
Let epoch_boundary_block_root = signing_root(head_block) if epoch_start_slot == head_state.slot else get_block_root(state, epoch_start_slot).**

Crosslink vote
Construct attestation_data.crosslink via the following.

Set attestation_data.crosslink.shard = shard where shard is the shard associated with the validator's committee.
Let parent_crosslink = head_state.current_crosslinks[shard].
Set attestation_data.crosslink.start_epoch = parent_crosslink.end_epoch.
Set attestation_data.crosslink.end_epoch = min(attestation_data.target_epoch, parent_crosslink.end_epoch + MAX_EPOCHS_PER_CROSSLINK).
Set attestation_data.crosslink.parent_root = hash_tree_root(head_state.current_crosslinks[shard]).
Set attestation_data.crosslink.data_root = ZERO_HASH. Note: This is a stub for Phase 0.

Construct attestation
Next the validator creates attestation, an Attestation object.
Data
Set attestation.data = attestation_data where attestation_data is the AttestationData object defined in the previous section, attestation data.

Let index_into_committee be the index into the validator's committee at which validator_index is located.
Set aggregation_bitfield[index_into_committee // 8] |= 2 ** (index_into_committee % 8).
Set attestation.aggregation_bitfield = aggregation_bitfield.

Note: Calling get_attesting_indices(state, attestation.data, attestation.aggregation_bitfield) should return a list of length equal to 1, containing validator_index.
Custody bitfield

Let custody_bitfield be a byte array filled with zeros of length (len(committee) + 7) // 8.
Set attestation.custody_bitfield = custody_bitfield.

Note: This is a stub for Phase 0.
Aggregate signature
Set attestation.aggregate_signature = signed_attestation_data where signed_attestation_data is defined as:
attestation_data_and_custody_bit = AttestationDataAndCustodyBit(
    data=attestation.data,
    custody_bit=0b0,
)
attestation_message = hash_tree_root(attestation_data_and_custody_bit)

signed_attestation_data = bls_sign(
    privkey=validator.privkey,  # privkey stored locally, not in state
    message_hash=attestation_message,
    domain=get_domain(
        fork=fork,  # `fork` is the fork object at the slot, `attestation_data.slot`
        epoch=slot_to_epoch(attestation_data.slot),
        domain_type=DOMAIN_ATTESTATION,
    )
)

Attester slashing
To avoid "attester slashings", a validator must not sign two conflicting AttestationData objects, i.e. two attestations that satisfy is_slashable_attestation_data.
Specifically, when signing an Attestation, a validator should perform the following steps in the following order:

Save a record to hard disk that an attestation has been signed for source -- attestation_data.source_epoch -- and target -- slot_to_epoch(attestation_data.slot).
Generate and broadcast attestation.

If the software crashes at some point within this routine, then when the validator comes back online the hard disk has the record of the potentially signed/broadcast attestation and can effectively avoid slashing.

[ ] Construct attestation_data.crosslink

[ ] Update attestation_data FFG vote variable


Add event page, hook and components

added event component for the event page (EventItem, EventList)
added event page
added event hook that fetches events from Lego and can be easily reused
the design could be much better and is currently being fixed

LGTM 🚀


fix tb hparams logging

What does this PR do?
allows the default call to log_hyperparams to actually log hparams since it's called without a metric
also changes the method of logging to the official method in pytorch docs (will revert if problematic)
Fixes #2971 #2406
Before submitting

[x] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together? Otherwise, we ask you to create a separate PR for every change.
[x] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] If you made a notable change (that affects users), did you update the CHANGELOG?

PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

Hello @s-rog! Thanks for opening this PR.

In the file pytorch_lightning/loggers/tensorboard.py:

Line 143:39: E231 missing whitespace after ':'

Do see the Hitchhiker's guide to code style

@s-rog  make sure to ping me here, once this is ready to review :)

@justusschock should the log_hparams metrics just be locked to scalar? since fit by default calls log_hparams without specifying metrics the user cannot change the key of the metric logged anyways. and the key cannot be updated by a subsequent call, only the value.

I don't understand, why you cannot update the key?

I see, for my own workflow I would want to see hparams from the get go, hence this implementation. Unless this is not the norm?

yeah that's the tradeoff, why we had to make a decision. I'm not sure, what would be the best way here. Maybe log once, as soon as there is a metric dict passed and then just update these metrics?

I have not tried separating logging the hparams themselves and the hparams metric, I'll test it out come monday. For default use cases that would still make hparams only be viewable at the end of training (if no metrics dict was passed during training and we add a default placeholder at the end).
This compromise works for me since I can still manually force hparams to show in the beginning, but it still may not be the best default mode. Any thoughts on this? @williamFalcon
Also, regarding the tests I'm not sure why they are failing if the master passed. Currently they are failing because self.log_metrics(metrics) is decorated in tests forcing the optional step arg to be mandatory, but I did not change the call to log_metrics from master which is also missing step.

Maybe log once, as soon as there is a metric dict passed and then just update these metrics?

@justusschock logging the hparams without metrics just breaks logging (same as the current implementation)

Mhm, this could be a way to go, although I don't like that we do different things for different loggers here

yeah that's what I thought as well, but tb hparams logging is fundamentally different from other loggers

Yeah, I see. Thoughts @Borda @williamFalcon @awaelchli @nateraw ?

@justusschock since no one seems to have any input, I prefer the logger init arg approach. If you approve, I'll go ahead and work on that (possibly in a different PR).

@s-rog yeah that'd be great!

@justusschock should be mostly done, except updating docs

So you habe a default metric now, that always shows up but the other ones are displayed as well?

the value can yes, and it can be updated just by logging values to the hp_metric key, without calling log_hyperparams
if you want to log more than one metric for hparams then you can just disable the flag and call log_hyperparams manually

Hi! This indeed seems like a much-needed feature, but I can't find a good tutorial on the current state of its implementation.
Can you elaborate on how to overwrite the hp_metric placeholder? Can it be done like:
logger = TensorBoardLogger(
                        tensor_log_dir,
                        **default_hp_metric = 'val_loss'  # replaces "hp_metric" value on "metrics" dict?**
)

I've tried that, but to no avail: I keep getting the hp_metric = -1 all the time (having started logging on a fresh new folder and averything).

I'm having an issue with this PR. I want to log multiple metrics, along with hyperparameters. However, calling log_hyperparams with my metrics dictionary in addition to lightning_module.log duplicates all the values in TensorBoard. However, it's not possible to stop the calls to lightning_module.log, as that's how e.g. learning rate schedulers are written.

@jbohnslav Do you have reproducible code that I can look at? Multiple hparams metrics work fine last I checked.

Edit, I found a workaround just by using a separate key for my hyperparameter metrics. (e.g. calling val_accuracy val_accuracy_hp and passing that as a dictionary to log_hyperparams). If I have time in the future, I'll try to reproduce the double-logging and re-open.

@jbohnslav
I see what you mean, log_hyperparams does write its own metrics value so selecting the same key as other log calls would result in duplicate metrics. This is why the default metric key in this PR is not something like val_loss.
A little tip: if you have multiple hp metrics try hp/{metric_name} instead of {metric_name}_hp to group them in tb scalar view or collapse them altogether.

I dont see the purpose of _default_hp_metric _. No documentation on how it should be used and when it is True the only value on tensorboard is -1. I did the same thing as @s-rog and created redundant plots. However I noted if I can log_hyperparams multiple times it will still stay on step 0 without moving.
Adding a feature to change the step could be an idea, I am calling log_hyperparams on epoch_end since I want to log the validation and training loss and compare it to other models? Or link to existing plots if they exist instead of forcing to create new ones.

@s-rog Something that should be more clear in the documentation? After a lot of trouble I understand that now but it was not clear from the beginning.

@s-rog I don't understand why you are doing the self.log_metrics(metrics, 0) in line 175, why is this needed? Because it messes up some plots if you call log_hyperparams after the training.


Removing brew cask cleanup step in mac update

Brew is giving out the following warning when running mac update:
Warning: Calling `brew cask cleanup` is deprecated and will be disabled on 2018-09-30! Use `brew cleanup` instead.

This change solves the warning.

Thanks for your contribution!


UnboundLocalError: local variable 'extra_network_data' referenced before assignment

Traceback (most recent call last):
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/call_queue.py", line 56, in f
res = list(func(*args, **kwargs))
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/call_queue.py", line 37, in f
res = func(*args, **kwargs)
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/txt2img.py", line 56, in txt2img
processed = process_images(p)
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/processing.py", line 486, in process_images
res = process_images_inner(p)
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/processing.py", line 716, in process_images_inner
extra_networks.deactivate(p, extra_network_data)
UnboundLocalError: local variable 'extra_network_data' referenced before assignment

probably your sd folder is corrupt, try the notebook without running the first cell

I had to install unprompted before installing controlnet to fix this issue


Set EnableWindowsTargeting to true / Allow linux development

Verbatim from commit:
This permits .NET to download the Windows targeting packs, which enables VRCX development on Linux.
It's not recommended to build the Windows apps with Linux though, so actual release builds should likely stick with Windows CI/CD, as per Microsoft:

This property is currently recommended to allow development on non-Windows platforms. But when the application is ready to be released, it should be built on Windows. When building on a non-Windows platform, the output may not be the same as when building on Windows. In particular, the executable is not marked as a Windows application (which means that it will always launch a console window) and won't have an icon embedded.

https://learn.microsoft.com/en-us/dotnet/core/project-sdk/msbuild-props#enablewindowstargeting

Err, I'm actually second guessing myself on following MS's recommendation here.
My build pretty evidently has an icon embedded:

And running that binary through Wine doesn't open another terminal window, so both of the concerns mentioned don't seem to apply.
I think I'd require a proper Windows user to double check that.


Issue Pulling image from an internal private registry

What happened:
trying to pull an image from an internal private registry (harbor) failed
I may have missed something , but right now, i have no idea what it is.
crictl --debug pull registry.xx.xx/project/nginx:latest --creds admin:xxxx

DEBU[0000] get image connection
DEBU[0000] PullImageRequest: &PullImageRequest{Image:&ImageSpec{Image:registry.xx.xx/project/nginx:latest,Annotations:map[string]string{},},Auth:nil,SandboxConfig:nil,}
E0831 14:45:03.040510   53605 remote_image.go:218] "PullImage from image service failed" err="rpc error: code = Unknown desc = failed to pull and unpack image \"registry.xx.xx/project/nginx:latest\": failed to resolve reference \"registry.xx.xx/project/nginx:latest": failed to do request: Head \"https://registry.xx.xx/v2/project/nginx/manifests/latest\": Service Unavailable" image="registry.xx.xx/project/nginx:latest"
FATA[0060] pulling image: rpc error: code = Unknown desc = failed to pull and unpack image "registry.xx.xx/project/nginx:latest": failed to resolve reference "registry.xx.xx/project/nginx:latest": failed to do request: Head "registry.xx.xx/v2/project/nginx:latest": Service Unavailable

What you expected to happen:
got the image pulled with crictl .  It works fine with ctr and nerdctl.
even using curl
curl -I https://registry.xx.xx/v2/project/nginx/manifests/latest -u admin
Enter host password for user 'admin':
HTTP/1.1 200 OK
Server: nginx
Date: Wed, 31 Aug 2022 13:36:22 GMT
Content-Type: application/vnd.docker.distribution.manifest.v2+json
Content-Length: 1570
Connection: keep-alive
Docker-Content-Digest: sha256:f26fbadb0acab4a21ecb4e337a326907e61fbec36c9a9b52e725669d99ed1261
Docker-Distribution-Api-Version: registry/2.0
Etag: "sha256:f26fbadb0acab4a21ecb4e337a326907e61fbec36c9a9b52e725669d99ed1261"
Set-Cookie: sid=7e6219b2a60b612bb1a3b60858705583; Path=/; HttpOnly
X-Request-Id: 6e7c11f0-8367-4e34-ab54-b29d66b8009b
Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
X-Frame-Options: DENY
Content-Security-Policy: frame-ancestors 'none'

Anything else we need to know?:
a no_proxy env is set to avoid communication to registry. xx.xx to go through the internet proxy.
it is set as default env and in  /etc/systemd/system/containerd.service.d/http-proxy.conf
Environment:
./crictl version
Version:  0.1.0
RuntimeName:  containerd
RuntimeVersion:  1.4.9
RuntimeApiVersion:  v1alpha2

crictl -v
crictl version v1.24.2

/etc/containerd/config.toml have the following added :
        [plugins."io.containerd.grpc.v1.cri".registry.mirrors."reg"]
          endpoint = ["https://registry.xx.xx"]

      [plugins."io.containerd.grpc.v1.cri".registry.configs]
        [plugins."io.containerd.grpc.v1.cri".registry.configs."reg".tls]
          insecure_skip_verify = true
        [plugins."io.containerd.grpc.v1.cri".registry.configs."reg".auth]
          username = "admin"
          password = "xxxx"

Kernel  : 3.10.0-1160.62.1.el7.x86_64

i am ready to do more test, and provides more logs if needed.
Thanks a lot.

I believe you need to place the creds before the registry in your command.
ex:
crictl --debug pull --creds admin:xxxx registry.xx.xx/project/nginx:latest

Thanks for help @daviddale  but unfortunately, it give same result :
[root@k8-worker-gpu-1 ~]# ./crictl --debug pull --creds admin:xxxx  registry.xx.xx/project/nginx:latest
DEBU[0000] get image connection
DEBU[0000] PullImageRequest: &PullImageRequest{Image:&ImageSpec{Image:registry.xx.xx/project/nginx:latest,Annotations:map[string]string{},},Auth:&AuthConfig{Username:admin,Password:xxxx,Auth:,ServerAddress:,IdentityToken:,RegistryToken:,},SandboxConfig:nil,}
E0908 09:25:59.582623   62077 remote_image.go:218] "PullImage from image service failed" err="rpc error: code = Unknown desc = failed to pull and unpack image \"registry.xx.xx/project/nginx:latest\": failed to resolve reference \"registry.xx.xx/project//nginx:latest\": failed to do request: Head \"https://registry.xx.xx/v2/project/nginx/manifests/latest\": Service Unavailable" image="registry.xx.xx/project//nginx:latest"
FATA[0060] pulling image: rpc error: code = Unknown desc = failed to pull and unpack image "registry.xx.xx/project//nginx:latest": failed to resolve reference "registry.xx.xx/project/nginx:latest": failed to do request: Head "https://registry.xx.xx/v2/project/nginx/manifests/latest": Service Unavailable


ci: rework workflows for automated publishing

Noticing that the workflow introduced in #4 did not really work as I expected it to do, this PR adds a couple of workflows which generate changelogs using a tool called git-cliff, automatically creates new releases via a release PR, and publish the result to pub.dev.
Currently, I am still waiting for an update of one particular GitHub Action; after the update, I am going to merge this PR (and hope that it works 🤞).

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

Project coverage is 100.00%. Comparing base (eb37f10) to head (77e7a6d).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##              main        #5   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            3         3
  Lines           54        54
=========================================
  Hits            54        54

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


Move Swizzlean to right category

Moved Swizzlean to new category: Objective-C Runtime

          1 Warning

:warning:
Found 2 link issues, a project collaborator will take care of these, thanks :)

Link issues by awesome_bot

Line
Status
Link

2928
301
http://nomad-cli.com redirects tohttps://nomad-cli.com/

2929
301
https://github.com/RahulKatariya/FrameworkTemplate redirects tohttps://github.com/RahulKatariya/SwiftFrameworkTemplate

  Generated by :no_entry_sign: Danger


Docs: Chinese mirror domain deprecated

https://zhuanlan.zhihu.com/p/432578145
The old domain will be out of service on 2022.05.31.
npm.taobao.org => npmmirror.com

Thank you / xie xie!

@xmsz You'll need to ask the maintainers of npmmirror over at https://github.com/cnpm as it doesn't appear to have mirrored the latest v8.13.1 binaries yet:
https://github.com/lovell/sharp-libvips/releases/tag/v8.13.1
https://registry.npmmirror.com/binary.html?path=sharp-libvips/v8.13.1/


date time problem

there is the time difference between the server and application.
**@zeus:/opt/traccar/conf# date
Tue Sep 27 16:11:27 EEST 2016
2016-09-27 13:02:56 DEBUG: [80DF117B: 5055 > <IP_ADDRESS>] HEX: 485454502f312e3120323030204f4b0d0a436f6e74656e742d4c656e6774683a20300d0a0d0a
2016-09-27 13:02:56  INFO: [80DF117B] id: 677928, time: 2016-09-27 13:02:56, lat: 38.39663, lon: 27.09496, speed: 0.0, course: 242.9
2016-09-27 13:02:58  INFO: [80DF117B] disconnected

The problem seems similar to https://github.com/tananaev/traccar/issues/1522.


Can I ask how to use the SSD structure model?

Seems like the demo.py use the FPN structure

Seems like the demo.py use the FPN structure

@yw2278
Yepp, our current version is FPN  (for more accuracy).
You can easily convert our model into SSD like structure by using the source feature maps to
s1,...., s6 instead of s6,u1....u5 in the EXTD_XX.py files (training required).

OH， I see，Thank you！


Popup does not fit within the boundaries of the viewport

I have a long list inside a popup and it is entirely OK for it to be outside the viewport in part. It does not make any sense to refuse to display a popup if the developer requests it to be shown.
I resolved the issue in my private fork  by deleting the whole if() block in popup.js:
if( module.is.offstage(distanceFromBoundary, position) ) { ... }

There is another closed issue: https://github.com/Semantic-Org/Semantic-UI/issues/3004 on the same topic and multiple users seem to support the same approach.

Looks like the lastResort setting is what you are looking for.

I tried lastResort but it didn't change anything. It seems to me that it tries other position but there is no way my popup would fit into the viewport - regardless of the position. I want it to be larger and the user will have to scroll down to see all of it.

That's exactly what it does for me.
Description is:
Setting this to a position like, right center forces the popup to use this position as a last resort even if it is partially offstage. Setting this to true will use the last attempted position.
If it is not working for you, show us the codez!

Popups now include a new setting boundary that let you specify that a popup should not escape the boundary of another section.  Have you tried this? Providing a jsFiddle example would help.

@philrykoff Thank you for pointing me back to lastResort. It turns out I had another problem which prevented the lastResort from working for me initially. Now everything works as expected. Thanks again and sorry for raising a false alarm.

you can do a dirty way here, which is set the max-height of the ui list class to 300px for example, and the overflow-y:scroll. So it will appear just like the image below


use MTLHeap in GPU Conform session to minimize driver memory management time

A large portion of our time (10% according to profiling) is managing what amounts to temporary memory in our Gpu conform session allocating and deallocating device memory.
We can ameliorate that cost by using a heap and allocating once on conform session startup.

Test implementation notes a small improvement, but CoreML is so weird with deterministic performance its hard to tell how much of a difference this makes. Maybe a few % - which ill take..


New versions

Will there be continued builds? (Version 5.10 for example)
Thanks so much!

Yes. Are there special features from 5.1.0 which you are missing?

I have issues with some files and I do not know if they can be resolved with a new version of tesseract/leptonica.

Meanwhile there is a new version available. Maybe you want to try it.


Unable open file.erd.json -166...

Describe the bug
When try open my diagram created by this plugin for visual studio code says Error no surch file or directory, open /home/user/.var/app/com.visualstudio.code/config/Code/User/workspaceStorage/9568.../dineug.vuerd-vscode/-1668366....
What is -1668366... file name?, attach a screenshot:

To Reproduce
I don't know exactly how to reproduce this error, I have a private diagram of a project and until I saved it there was no problem but now it doesn't want to load. I have no problems creating a new diagram, the problem is when it tries to open the existing one. I have not made any manual changes to this file, the computer where it is located is mine alone so no one else or any software could have made additional changes to it.
I try reinstall the plugin but does not work.
If you need any specific information from the diagram file, please let me know, I cannot publish it openly in this place as it contains confidential information.
Browser:

OS: GNU/Linux Ubuntu 22.04 LTS.
Browser Google Chrome
Version 126.0.6478.126 (Official Build) (64-bit) (flatpak)

VSCode:

OS: GNU/Linux Ubuntu 22.04 LTS.
VSCode version: 1.90.2 (flatpak)
Extension Version: 1.0.20

I try delete parts of .erd.json file and try load again in visual studio but I ended up deleting almost all the content without even being able to open it, I realized that the problem is not the file with its content but a problem with the file path, I have changed the name and it has loaded correctly, but why does it happen? This is not a problem with access to the json file, it is not a permissions problem or anything, could it be a problem in the webcache of the webkit engine in visual studio?
Maybe there is some configuration of the plugin that is corrupting access to the diagram, if I rename the file to the original name it cannot open it again, throwing the same error again. Please review how the configurations related to the open diagram files are being saved.

VSCode has a backup process for cases when files are closed without saving. The backup path seems to be managed by VSCode, but it appears that it was deleted by an external factor.
It seems that the integrity of the backup information managed by VSCode has been compromised. Therefore, it looks necessary to cleanly delete all VSCode-related caches and perform a fresh reinstallation.
https://github.com/dineug/erd-editor/blob/e1c685ea5d72b509174461b2f03039cef3070dde/packages/erd-editor-vscode/src/erd-editor-provider.ts#L44


Adding benchmarks that use caching.

Description of change
NOTE: This is a new PR replacing https://github.com/awslabs/mountpoint-s3/pull/761 because through this branch wf-changes/caching-benchmarks I was able to actually run the new job for caching: https://github.com/awslabs/mountpoint-s3/actions/runs/8031555207.
This change is adding benchmarks that use mountpoint caching with files up to 1 GB in size because the current workers have only 30 GB of disk. If we want to support bigger sizes, we'll likely need to make changes to provision new workers.
The fio jobs were copied from the read benchmarks and renamed accordingly. I ran some of the tests locally by using the filter functionality. We might not need all of these tests for the cache benchmarks but defaulted to have the same as the read ones and change later if needed.
# filter to only run this test for both for normal reads and cached ones
export JOB_NAME_FILTER=seq_read_small

./mountpoint-s3/scripts/fs_cache_bench.sh
Will only run fio jobs which match seq_read_small
Skipping job mountpoint-s3/scripts/fio/read/rand_read_4t_direct.fio because it does not match seq_read_small
Skipping job mountpoint-s3/scripts/fio/read/rand_read_4t_direct_small.fio because it does not match seq_read_small
...

# list the mount and caching directories (sample)
ls -d1 /tmp/fio*

/tmp/fio-ZaNYWdZaBK3W
/tmp/fio-ZaNYWdZaBK3W-cache-O8X4T2w4UDnx

# benchmark results for this run
[
  {
    "name": "cache_sequential_read_small_file",
    "value": 1184.8017578125,
    "unit": "MiB/s"
  },
  {
    "name": "sequential_read_small_file",
    "value": 16.4091796875,
    "unit": "MiB/s"
  }
]

There is opportunity of doing some refactor between the different bench scripts but I'm prioritizing getting this out first and do refactor later if needed.
Does this change impact existing behavior?
The only impact should be to our CI benchmarks that now will run additional tests that use caching (in a separate job).

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and I agree to the terms of the Developer Certificate of Origin (DCO).

I think this can be incremental and moves us in the right direction. I'd prefer to push this and tackle the host in a separate PR.

For this one I'd rather we get the config right before merging. We've seen that customers look at our benchmark results to guide them on architecture decisions. We don't want to mislead them with the results that we publish if we're using a platform/config/etc that we actually don't recommend.

Ok. I'll reach out to discuss what we think the right hosts should be.
Thanks!

The caching benchmarks has been updated to use a m5dn.24xlarge instance with local storage and test using 100GB files.


New permissions

Hello,
I've just learned that there were new permissions, but I can't figure out how they work. I'm trying to limit a group so that they can only craft and use a specific wand but I don't think I do it right.
Here is an example of my groups :
HH:
permissions:
- magic.commands.cast
- magic.wand.use
- -magic.use.wand
- -magic.use.beginner
- -magic.use.blaster
- -magic.use.broomstick
- magic.cast.*
- magic.wand.craft
- -magic.craft.wand
- -magic.craft.beginner
- -magic.craft.blaster
- -magic.craft.broomstick
- magic.wand.enchant
- magic.upgrade
- -magic.cast.worm
- -magic.cast.virus
- -magic.cast.hunter
- -magic.cast.animate
- -magic.cast.meteor
- -magic.cast.supercollapse
options:
rank: '900'
prefix: '&f&l[&2&lHH&f&l]&r '
inheritance:
- ESSENTIALS
- default
I hope you'll be able to help me, because I didn't find how to lock any wand.
Best regards,
Elsopeen
Edit  1: I read the "plugin.yml" file to try to understand the new permissions, but I can't figure out how to use the list-typed permissions as magic.craft or magic.use .

I found a way to disable crafts and uses of the different wands, I just set the permissions "- -magic.use." and "- -magic.craft.". But I think that could be great to explain that in the permissions page of the wiki.


Create livingstonschools.txt

Holden High

@beau08 First stage of verification passed, official domain is lpsb.org as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision. Proof of domain ownership: https://www.lpsb.org/UserFiles/Servers/Server_546/File/Technology Quotes/2020-2021/Livingston Parish - Connecting your Google Account.pdf

@beau08 Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Move away from jquery and speedup loading

Maybe thats one? http://www.sitepoint.com/jquip-lightweight-jquery/
But you still need way to provide original jquery for those who need.

0c64348c4b14eeff5262ba7d801d372b6fbabad0 Better network utilise

#84 Async cascade resolution. Even better network utilise

#98 Making huge breaking changes, you should know it.


Blazor MSAL auth options login mode

clicking on 'Log In' opens login popup
setting NavigateToLoginRequestUrl: true inside wwwroot/appsettings.json from MsalProviderOptions has no effect and popup opens instead of redirecting to login URL in the same window
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 520b9821-ecef-20af-a601-ea36c4297d88
Version Independent ID: da9c8ac9-4d7a-4b40-56a2-a4bfe7083567
Content: Secure an ASP.NET Core Blazor WebAssembly hosted app with Azure Active Directory B2C
Content Source: aspnetcore/blazor/security/webassembly/hosted-with-azure-active-directory-b2c.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @Ma3yTa ... Yes, it was by-design for 3.x. It's going to be a new feature for 5.0, which is in preview now and should be out by the end of the year.

https://github.com/dotnet/aspnetcore/issues/20374
https://github.com/dotnet/aspnetcore/pull/23694

It's going to be a property (LoginMode) on MsalAuthenticationOptions.

Actually, I won't close this ... I was going to open an issue to track the update for the docs, but I can use your issue here and take care of this today. It will appear in the doc when the doc version selector is set to 5.0.

Is this feature available for .Net Core 3.1 or only available for .Net 5?

@adixon501 ... Only 5.0 or later.

@guardrex, thats one way to get us to migrate to 5.0 😄


esmvaltool run --resume-from option fails without metadata.yml

The resume-from option fails if it can't find the metadata.yml file for each processor group.
In my case, it can take several hours to run a set of data and still fail! Meanwhile, --resume-from requires the metadata.yml file, which is only written at the end of the run.
From what I can tell, metadata.yml is just a list a completed files in each preproc subdirectory. Could we write metadata.yml to disk more often, or perhaps after each netcdf file is written? It would reduce the overhead of resume-from, save a lot of compute time and energy.

A second potential issue - resume-from links to previous runs. Is there an option to instead make a local copy of the preproc files?
I ask because I'm running several analyses at once, and I have data from several half-finished runs. It's very hard to figure out exactly which output directories need to be kept and which can be booted!


Support EIP681

https://github.com/ethereum/EIPs/blob/master/EIPS/eip-681.md
It seems on the line with many stable coins use cases. @colourful-land

Check function_name empty or not available, prompt not supported.
Check chain_id empty or not available or the same as current chain's -> Use current chain.
If chain_id is available but doesn't match, prompt wrong network.


manager doesnt work at all

hey  somehow i cant seem to get the manager to work i added my steam install as version . it says its version 0.14.21 but its  not since its the lastest 0.16 installled and somehjow it doesnt start my modpacks i created

Try to remove and re-add it. Make sure you select the correct path as described here: https://github.com/Artentus/ModMyFactory/wiki/Add-Factorio

i cant even remove it .... i used the button for detecting seam version

Well, you can "remove" it by deleting your settings file located in %appdata%\ModMyFactory.
Your mods and modpacks are not affected by this so don't worry.

You can add modpacks with "File->New Modpack" or with the "New Modpack" button in the toolbar (second from left). Once you have created a modpack you can drag and drop mods (and other modpacks) into it.

Yeah, I had similar difficulties when first using it. The interface is great for those who know how to make it work, but for those new to the program, it's terribly confusing and non-intuitive. You should take a look to see if there's anything you can do to help that. And this isn't just me, either. I've had a few others use it, and they couldn't figure it out easily either. I had to guide them through it with discord. Please, make the interface more intuitive.

If you have any suggestions you are more than welcome to tell me. I'm a programmer, not a UI designer, I don't really know what I'm doing in that regard besides making it work.

Well firstly, one that would probably be pretty easy would be making it so that you can create a modpack from the right-click context menu when in the right-side pane. The existing modpack button is too small to be easily noticed by first-time users.

I have made some improvements in the latest release. Please check it out and tell me what you think.

It's excellent, I love it. Thank you much.

I have successfully added the Steam version to the program, but when I try to play it doesn't load any mods. I've tried making a modpack, selecting it and activating it, as well as selecting and activating selected mods but it just won't work, since it always starts base factorio...

Are you launching FROM the mod manager? Because when using it, you have to specifically select the factorio version from the drop-down menu in order for it to put the mods into the mods folder. If you don't do that, it won't work. And if you don't do that, it won't launch from the mod manager.

Yes, I'm launching from the manager (hitting the green play game button thing) after I've selected Steam 0.16.51 (whatever the latest version is) from the dropdown menu to the right. I've even tried starting the manager as administrator. I'm on win10 64bit.


chore: Upgrade clsx to 2.0.0

Pre-flight checklist

[x] I have read the Contributing Guidelines on pull requests.
[ ] If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
[ ] If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation
Upgrading clsx to 2.0.0 doesn't seems to effect anything.
According to their release note, the breaking change is "Add "exports" map for native ESM support", which shouldn't effect docusaurus.
Test Plan
Test links
clsx v2.0.0 release note: https://github.com/lukeed/clsx/releases/tag/v2.0.0
Deploy preview: https://deploy-preview-9464--docusaurus-2.netlify.app/
Related issues/PRs

@slorber Hi, is there any updates to this?

Missed it but an unfortunate result of this upgrade is that we now have twice the lib in our client bundle. Wondering if we'll backport this? 🤔

@carloskelly13 any plan to upgrade clsx in prism-react-renderer?

clsx is extremely small so not a huge deal. Upgrading would certainly be better, though.

@slorber Yeah, we'll get @harryzcy's PR merged in and we'll publish a build. Thanks for getting that in.

@slorber Prism React Renderer 2.3.0 with clsx 2.0 is published. https://github.com/FormidableLabs/prism-react-renderer/releases/tag/prism-react-renderer%402.3.0
Thanks @harryzcy for the PR!

thanks ❤


#159758423 add down vote an answer functionality

What does this PR do?
This PR creates the functionality for users to down vote an answer
How should this be manually tested?

Clone the repo

$ git clone https://github.com/asheuh/StackOverflow-lite
$ cd StackOverflow-lite

Create virtualenv

$ python -m venv venv

Run app

$ flask run

Then go to <IP_ADDRESS>:5000/api/v2

What are the relevant pivotal tracker stories?
159758423

Pull Request Test Coverage Report for Build 132

0 of 0   changed or added relevant lines in 0 files are covered.
8 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.5%) to 79.171%

Files with Coverage Reduction
New Missed Lines
%

home/travis/build/asheuh/StackOverflow-lite/stackoverflow/api/v2/questions/routes.py
8
43.12%

Totals

Change from base Build 130:
-0.5%

Covered Lines:
802

Relevant Lines:
1013

💛  - Coveralls


Document that xamarin is only supported for creating iOS and Android Apps

When creating user docs for xamarin sdk, it's important that we set expectations, Windows is not supported, so need something like:
NOTE: You can only use the AeroGear Xamarin SDK to create iOS and Android Apps.

moving to mobile-docs


No "main" field in package.json

This package has no "main" field in package.json, making it not work with Node.

It seems I can't import this at all from CommonJS actually 🤔

Maybe the problem is that I'm bundling the whole thing esbuild 🤔

Closing as I don't care anymore about this.