Kiosk-Mode or supressing adress bar?

Hi, I watched your short video with the Home Assitant interface with great enthusiasm.
Soon, thanks to your instructions, I would like to try putting the HA on the Shelly Wall Display.
I noticed in your video that the address bar is still visible in the browser.
https://github.com/user-attachments/assets/dfbf606d-deba-43f9-ac13-08e8eea46190
Is it possible to suppress this with a fully kiosk mode in Chrome, to gain more working space and better overview on the display?
Another approach might be to combine this FullyKiosk app, if the manufacturer allows it.
https://www.home-assistant.io/integrations/fully_kiosk/
Just an idea, but first of all, I want to thank you for all your effort!

Hi, I noticed that too. When you scroll down, the search bar disappears. I was planning to use WebView in a separate application, but the old preinstalled version of WebView doesn't work well with Home Assistant. Updating WebView was tricky for me and often led to a boot loop. However, I'm working on a guide to help with this and will be publishing it soon.

That would certainly be great, as it would surely have a positive impact on the user experience.
Thank you for further optimizing this already great implementation!

Hello, Shelly Wall Display lead dev here. Just a few notes:
First, great work, @RapierXbox
Next, any browser that you install will use the webview that is currently installed. Stock webview cannot show the HA pages in a fully usable manner, no matter what browser you use.
Finally, there is a new Wall Display version coming with new hardware and the webview will be updated to a more recent version that will be able to show HA normally. With this new version HA will be supported internally.
Again, great work!

@Fritz-la-chatte
This is really not the place for this, but I will nevertheless reply you, because you seem to be confused. Maybe I wasn't clear, and I will try to fix this.
Neither the Thermostat functionality, nor HomeAssistant integration were on the table when we first designed the Wall Display. We did find out there were issues with the temperature reading correctness when we received the first golden samples from the factory but initially those were overcome with an internal temperature offset. Only after we started implementing the Thermostat we found out that those readings were unreliable for this function. Hence we started offering free BLU H&T devices for every Wall Display purchased from the earliest batches. More info, here. Is this appealing enough for you?
As for the webview, we never intended to actually use it. We're using a proprietary Android build from what is called "a solution company" and only designed and wrote the front-end application. What we had was enough until recently, when we decided that HomeAssistant integration is a must. That's when we found out that the webview is outdated as hell and HA would not work, almost at all. Although using a webview in a system process is strongly discouraged for security reasons (here), we are currently preparing an OTA update that will update the implementation, and after that there will be another update in which HomeAssistant will be integrated in this webview in the application, so no, your guess is not correct - native HA integration will be available for the first Wall Display version. This large update will not be needed for the new hardware version, which will come with a more recent webview implementation and native HA integration.
You know what's really disappointing? Putting up invectives without being informed. I'm sorry we have lost you as a client. Maybe we should have popped up a message on the screen saying you're eligible for a free BLU H&T? Oh, sorry, I forgot about ./adb shell pm disable cloud.shelly.stargate...
Now that [I hope] I have made myself clear, let's keep this issue clean and refrain from any more off-topic comments.
Again, praises for the great work of RapierXbox!

Hi everyone,
Thanks again for your appreciation of my project. I’m reaching out to see if anyone with more knowledge might be willing to help me test the new version. I’ve figured out how to install a new system WebView, but the method I’m using is quite risky and could potentially result in a boot loop. I’m considering trying it out, but my family won't be thrilled if the lights don’t work for the next week since I don’t have a spare to test on, haha.
Also, it’s great to see someone from the Shelly team here!

@KaHa6uc That's basically what RapierXbox has already said and is now trying to correct.
I actually also bought the wall display as a thermostat. In the meantime, people are suggesting that you shouldn't rely on the internal sensor and that you should integrate an external H&T. (very appealing...) Now, apparently, if I understand right, the money is to be taken out of the customer's pocket because the product is generally disappointing or unsuitable for many users and to invest money once again in a new hardware revision. An interesting approach. I'm sure that someone from the HA community, not least RapierXbox, will also be able to solve this problem. If my guess is correct, I don't understand why Shelly doesn't release an update with a full webview and support the community. Shamed be he who thinks evil of it.
For me, this product is likely to be my 1st & last from Shelly under these circumstances, as I could have bought a Chinese touchscreen with relay for around €35. On the hardware side, it would have been just as good, if not better. A real disappointment.

Also added official thermostat implementation in  the readme for you!

Hello RapierXbox,
I don't know how much I should tell you thank you for this effort.
After realizing that the internal sensor is a bit “fickle” and I don't see the point of coupling an external sensor, which I find unattractive, I switched all the classic GIRA thermostats to anthracite Homematic wall thermostats instead of the wall display.
Since then, I have been hoping for a worthwhile alternative use, whereby I then intend to sacrifice a “stupid” wall lightswitch and until then look forward to your fantastic solution of the HA dashboard with switching function.
So I can only repeat how great I think your work is!
Many thanks and best regards from Austria.

Hi RapierXbox,
with all the joy of many Wall Disply users that at least a moderately functioning Home Assistant integration including a new WebView has now found its way into the official Shelly beta firmware, I wondered whether this might not have opened the door for you to disable the address bar or to operate a FullyKiosk mode?
Shelly is avoiding to hide a disturbing bar at the bottom of the screen. In their forum was written, that they will keep their bar because it should be a "core feature". Even if the majority don't like it.
https://community.shelly.cloudtopic/2401-home-assistant-in-/wall-display/?do=findComment&comment=12583
Also, the HA dashboard is still rather slow while the workload is kept simple.
I would be pleased if you would continue to pursue your approach, as I believe that many users, like me, are no longer interested in the Shelly environment and would prefer pure HA control.
Best regards

Hi everyone,
I was considering abandoning this project, especially after noticing that Shelly had implemented a similar feature, which I assumed most people would prefer. Additionally, I haven’t had much time to dedicate to it recently. However, knowing that many of you are still interested in seeing this project move forward has motivated me to continue.
I will first check if the latest update includes a new version of WebView. If it does, I will resume development by removing the access bar, adding a swipe-to-toggle light feature, and introducing more improvements.
Thank you for your support!

After realizing that the internal sensor is a bit “fickle” and I don't see the point of coupling an external sensor, which I find unattractive, I am maby working on replacing the internal sensor for a higher quality one. No promises though!

5 Shelly displays orderd. Expect some updates soon!


Compatibility Issues with Dependencies

I ran into dependency conflicts because the package currently uses older versions of http and webview_flutter.
Would you kindly consider updating these dependencies to their latest versions? This will help maintain compatibility with modern Flutter projects.

If you are facing an issue you version then you can remove both of their version then try pub get.


Fixed unit tests + added "optional" to middle name labels

Issue #: None
Description of changes:

added "Optional" to middle name labels
removed Fee Summary tests from App test suite
created/updated Sbc Fee Summary test suite

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the bcrs-entities-create-ui license (Apache 2.0).

I've decided to not update the app version so that I don't impact Lewis' outstanding PR. Also the actualy UI changes are minimal so I don't care too much about tracking this change through the dev/test/prod environments.


Add meson build definitions for facil 0.7.5

Do I need to add patch_url, patch_filename, and patch_hash?

No, it's added automatically.


Update Developer Guide

Pull Request Test Coverage Report for Build 171

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

Totals

Change from base Build 168:
0.0%

Covered Lines:
2055

Relevant Lines:
2423

💛  - Coveralls


Support user-defined generic password options/attributes.

This is a quick sketch to discuss support for custom attributes/options when creating generic passwords.
The desire is to be able to support more complex use cases such as specifying kSecAccessControl, kSecAccessGroup etc. for a generic password.
Currently I've added this as an additional set_generic_password_options() function so as not to introduce any breaking changes but ultimately I think a builder style API for PasswordOptions would be more ergonomic. Perhaps:
let options = PasswordOptions::builder()
  .service("com.example")
  .account("user-id")
  .password("mock-password")
  .access_control(AccessControlOptions::USER_PRESENCE)
  .access_group("com.example.shared-keychain-group")
  .build()
  .unwrap();  // Panic here as kSecAccessControl and kSecAccessGroup are mutually exclusive?

Then we could make the breaking change that set_generic_password() just accepts PasswordOptions and the password and wouldn't need the additional function if that is acceptable for the next major release.
I notice in #186 there are other people that would also like to be able to use kSecAccessControl with SecItemAdd so I think it makes sense that we support the other attributes too.
Your thoughts and feedback would be appreciated 🙏
Closes #219

Just for info, in the key management side of things, the pattern is to use a GenerateOptions struct which contains all your parameters, such as access control, etc.
https://github.com/kornelski/rust-security-framework/blob/b2189b20a6f07f9dd936bb8cd263bab177bc4356/security-framework/src/key.rs#L149
pub struct GenerateKeyOptions {
    /// kSecAttrKeyType
    pub key_type: Option<KeyType>,
    /// kSecAttrKeySizeInBits
    pub size_in_bits: Option<u32>,
    /// kSecAttrLabel
    pub label: Option<String>,
    /// kSecAttrTokenID
    pub token: Option<Token>,
    /// Which keychain to store the key in, if any.
    pub location: Option<Location>,
    /// Access control
    pub access_control: Option<SecAccessControl>,
}

Validation parameters is implemented in the GenerateKeyOptions::to_dictionary() method.

Thanks


Add a test for the round trip of Instant via .perl.EVAL

Fixed in https://github.com/rakudo/rakudo/pull/708


Review: Pricing and FAQ

Review Branch
review-pricing-and-faq
Files to review

Pricing.jsx
FAQ.jsx

Checklists

Architecture
Design
JS
React

Due date
3/4/2024 @ 10:30 am
For more information
The review process is documented at: http://courses.ics.hawaii.edu/ics414s21/morea/review/reading-idpm-review.html

Pricing.jsx:

Design-08: Can potentially refactor the form checks that contain the data on the different branches in order to shorten the code.
JS-08: Incorrect usage of JSDoc Comment.

FAQ.jsx:

Will need to review upon the style change, but for now follows all checklist requirements.

Pricing.jsx
Looks good to me. Perhaps more comments describing parts of the page could be nice but I don't think is necessary.
FAQ.jsx

JS-08 @ Line 5:  Turn comment into JSdoc comment

##Pricing.jsx##
It looks fine, there may need to have comments about all of the forms and what they are for, or have variable names that are easily identifiable for the forms.
##FAQ.jsx##
-JS-08: Line 5, convert comment into jsdoc comment

Pricing.jsx

Looks fine, comments would be helpful though.

FAQ.jsx

JS-08: @ line 5, turn comment into JSdoc comment.

Pricing.jsx
n/a
FAQ.jsx
JS-08 @ Line 5: Turn comment into JSdoc comment
Update


settings.CKEDITOR_CONFIGS seems to be ignored

Firstly, thanks for your great library!
I have three different widgets and would like to use a different toolbar for each.  I have specified config_name in the widget constructor and the settings are not applied.  all of widgets seem to use the same config_name.
I have worked around this by overriding render and setting my config in there but I thought I would let you know.

It has already been solved (several times actually). See here https://github.com/syko/django-ckeditor/commit/46741569df452a8001c0b5d5949186fe6d7d69f0 for example.

thanks for your response!
That is better than my brute force approach!


make demo-ui run by default in tilt

Description of change
Add grafana dashboard to workload prioritization tab
Checklist

[ ] Tested in playground or other setup
[ ] Screenshot (Grafana) from playground added to PR for 15+ minute run
[ ] Documentation is changed or added
[ ] Tests and/or benchmarks are included
[ ] Breaking changes

Summary by CodeRabbit
New Feature:

Added a new GrafanaDashboard component for displaying Grafana dashboards in the UI.
Integrated the GrafanaDashboard component into the HomePage component, specifically under the "Workload Prioritization" tab.
Modified Grafana configuration to allow embedding.

Refactor:

Updated the useRequestToEndpoint hook with improved logic and functionality.

Test:

Adjusted load testing stages in the test.js file for more extended duration testing.

🎉 A dashboard new, for all to view, 📊
In our home page, it takes center stage. 🏠
With tests refined, and code realigned, 🧪
Our app's design is now redefined! 🚀

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

Addressed in #2434


Request help on survival

Hi, dear all, thanks a lot for your great tools and the detail documentation! Very helpful!
I have a question: how to interpret the relationship between C-Index and the KM curve? The C-Index is a criterion similar to the classification accuracy, right? And I read several papers, it seems the KM curve is generated from the \beta values (if using the CoxPH model), and take the median value (M) as split point, it beta is less than M, then that sample is belong to the low-risk group, and if beta is larger than M, then that sample is belong to the high-risk group. I don't understand this. Why could we use this median value to discriminate the high risk and the low risk? I think that depends on the samples themselves.

Hey @glhfgg1024, can you provide some papers that demonstrate this idea? My first thought is to avoid dichotomisation, and treat most outcomes from a "risk" point of view.

Hi, @CamDavidsonPilon , thanks a lot for your kind reply! Please check this paper http://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1006076, the last line in page 8, "A log-ranked p-value is then computed to differentiate the Kaplan-Meier survival curves between the higher vs. lower risk groups. In this report, we used the median log hazard ratio as the cutoff threshold."

Haven't had a chance to extensively read through the paper, however it seems like they calculate a prognostic score (risk score) based on some known variables from each of the models (Cox-nnet, standard Cox PH model, CoxBoost, RF-S). I don't know the other techniques really outside of Cox PH but each model should return some probability. Think predicted probabilities of death as a function of chronic conditions, but then add it as a function of time. Based on these calculated scores, they divide it into two categories (high: > 0.5; low: < 0.5). It seems like to me, they wanted to dichotomize  to compare the different models.
I am super confused by what they are doing with the Kaplan Meier. A Cox PH model makes the assumption of proportional hazards, so the generated survival curves will always meet the proportional hazards assumption. The survival curve that comes from the Cox PH is NOT the same as the survival curves from Kaplan Meier. The Kaplan Meier curve is nonparametric so it does not have to follow the proportional hazards assumption or other distributional assumptions. All a logrank tests compares is the proportional hazards assumption. If a beta is significant in the Cox model, the corresponding logrank test from generated Kaplan Meier curves would also be significant (ignoring conditioning / stratification)
@glhfgg1024 In regards to your thoughts, it is odd to divide them into categories like that. Realistically the probability that comes from the model is more meaningful than the binary category. I would guess it makes their comparisons between models easier, so that's why they did it. Realistically, they could have chosen any point (75th percentile), that why the actual probability generated is more informative. My guess they chose 50th percentile since it maximizes the n for statistical tests in comparing the different models. In practice, clinicians or others would be better informed by the probability itself

Hi @pzivich , thanks a lot for your kind reply and so detail explanation! I'm new on survival prediction. In my opinion, the circumstance is like this: given some patients, we have their clinical outcome and the task of survival prediction is to predict their survival probability in some certain time (e.g., 30 days, 60 days, or 2 months, 6 months). Thus the output of one model (e.g., CoxPH, Cox-Lasso, or many others) is the probability for each patient in each time point. Thus, for each patient, we could get a probability vector that shows the probabilities in each time point of one research period (e.g., 1 month, 2 months, ..., 6 months).  To my limited knowledge of CoxPH, given the features/variables X for one patient, the model will compute a risk factor by \beta = Xw, where w is a vector which is learned by minimizing the negative log-likelihood defined by the CoxPH model. For each patient, there is one \beta. Thus, for the given set of patients, there are a list of these \betas. Then the authors taken the median of these \betas, and split the set int the high-risk group and the low-risk group. I'm curious about this. I think the high-risk or low-risk depends on the patient himself/herself, and should not be from the predicted \betas. I found in many papers, the authors will provide two survival curves or one survival curve as follows:

I think the bottom figure is easy to understand.

@glhfgg1024  no problem. Ahhh okay. I think I see a source of potential confusion. I read the beta as the model coefficients, not as the sum/one beta for each patient. If they are using the predicted beta for each person, dividing into categories based on that value as you described, would seem to be problematic to me. Having said that, this is different and outside of the survival analysis I generally do. I will read through the paper more fully

Hi @pzivich , if I understood correctly, the authors seem to use the predicted median beta  as the split point. If you are convenient, please check their code:
https://github.com/traversc/cox-nnet/blob/8e73a1145f7a6c1577f8a107120b0494571e8541/examples/plots.r#L6
In my opinion with limited knowledge of survival prediction, we are given some patients (say 60), according to their clinical diagnosis, we first split them into two groups of high-risk or low-risk, then we split them into two sets (train and validation), then we train the model using the train set to obtain the beta coefficient for CoxPH, and using the validation set to do cross validation to select the hyper-parameters (e.g., the regularization parameters for L1/L2 regularization energy on \beta). Then, we are given the test set, we use the obtained model to predict their survival probabilities.


push update asset config for k8s on deploy

update ASSET_MANIFEST on k8s

Is this script guaranteed to run before the hokusai deploy/promote? It's frustratingly difficult to tell this from the .circleci/config.yml workflow definitions.

Right now it runs as part of the heroku deploy which runs concurrently with the k8s deploy. We could make it so the heroku one always runs first or take it further and factor it out into it's own step.

Whichever is easier! I'd fear the current approach would break a noticeable proportion of the time.
Making it a separate asset task simplifies the later transition away from Heroku, but at that point we might want to combine it with the single deploy step anyway. Maybe assets should be built and configured in both tasks for now.

As discussed, will merge as-is for now. I recommend an update to make this strictly-ordered before switching staging DNS.


How to avoid certain scan results to be stored?

Hello
I know that it is possible to exclude some parts of the code from ORT scanning but is it possible to configure .ort.yml file to exclude part of the code from being stored in the storage place?
I imagine a following scenario
My project App01 uses dependancies A, B and C
In a normal use case ORT scanner will store scan-result.yml file for all 4 objects: App01, A, B and C
I Imagine that I could configure a pattern to exclude storing the results of my App01 and store only A, B and C
I plan to use share place for projects to read/store the results but I would like to hide the information of the results between projects
What do you think?

Well not entirely because I do want to scan the project content. I just don't want to store the result in the common/shared artifactory where all other project will have an access.

But you do want to store the results (for performance reasons / reuse), just in another database, right?

I do want to store the results but only for project dependencies

But that would mean that if (the same commit of) com.orange/ort-test ever gets scanned again, there would be not stored results to reuse, and the whole scan process would (unnecessarily) run again. Is that an acceptable performance penalty for you?

Yes I know but hopefully it will concern only project files. I don't know what will be the duration loss but I have data sensitivity constrains as well :/
By default all projects will store they scan results in the shared space but for those who'd like to stay private I could give an opportunity to enable a variable DO_NOT_STORE_MY_RESULTS=1

Hello @sschuberth
Have you considered any update on this feature?

To be open, it's not a feature that I'm planning to implement any time soon. But we welcome PRs, and it shouldn't be too hard to extend ScannerConfiguration accordingly, depending on whether you envision this to be a storage-specific configuration or a scanner-specific configuration. Would you like to say "this storage generally only stores scan results from packages, not projects" or do you want to say "when using this scanner, only store its results for packages, not for projects"?

With almost 2 years of no activity on this, I don't think this will get implemented.


standardize benchmark

compare FftSharp to other libraries
https://www.codeproject.com/Articles/1095473/Comparison-of-FFT-Implementations-for-NET

do this after the API stabilizes #8


4SB show all data simultaneously checkbox & pinganimation longer

Checkbox option to show resources/maxstorage +income, this disables the hover functionality.
Pinganimation is larger and lasts longer, about as long as ping is visible on map.

Nice one! I've done some code-wise improvements, but idea itself is great.
Here is the feature:

Do you wanna be mentioned somehow? :D

Nice thanks! Not that you have to but sure why not :D


nodes are stuck in acquiring state

2 HBv3 nodes are stuck in the acquiring status. no instances exists in the Azure portal.
this is using spot instances
cc version is 8.2.0-1616

this should be fixed in https://packages.microsoft.com/yumrepos/cyclecloud-insiders/cyclecloud8-8.2.1-1675.x86_64.rpm and is due to a new VMSS behavior


Getting "CUDA error: an illegal memory access was encountered" with model.generate

Hi, thanks for making this! Definitely a lot faster. I'd like to use it with generate() but getting that error in the title. The model works fine just calling it like in ppl.py, but calling the huggingface generate function causes issues. Any idea what's going on?
Below is how I'm calling generate.
model.generate(
        **input_tokens,
        do_sample=False,
        min_length=0,
        max_length=newlen,
        temperature=0.6,
        top_p=0.6,
        use_cache=True,
        repetition_penalty=1.1
        ).cpu()

I haven't tried generate yet. I'll have to take a look.  Maybe try disabling use_cache?

I tried that, but then it just takes forever - waited for like 30 seconds with a context length of 100 before terminating, GPU was running at max according to nvtop though

Actually, now that I think about it I think the kernel isn't set up to handle context lengths that aren't divisible by the block size.  Oops!  I just finished writing and testing the kernel last night, so forgive the bug.  Let me get that patched up.  Hopefully later today.

I pushed an update that should fix the issue for you. Please let me know.  On my system generate works correctly now.

It works! This is great, thanks for the speedy fix.


#132 - do not interpolate nil or boolean values

I think this looks great @doug-martin . Much simpler than my prior approach.

Merging in to a v9 branch as there are a lot of other housekeeping items to do to release this.


TypeError: Cannot read property 'useStyle' of undefined after upgrading from echart 4.8 to 5.x

Version
5.1.2
Steps to reproduce
No idea, so here's a screenshoot of the error
https://imgur.com/keTUuUL
What is expected?
To be able to load my page
What is actually happening?
so, i tried upgrading echarts from v 4.8 to v 5.x in my project, but whenever i tried to start my project, i straightly get this error. I have no idea what caused this, and i have read the docs and guide on how to upgrade to v5, but still haven't find the solution or why this is happening. Any help will be appreciated. thank you!

@flyaway22 Please provide a minimum reproducible demo for the issue either with https://codepen.io/Ovilia/pen/dyYWXWM , https://www.makeapie.com/editor.html or https://codesandbox.io/s/mystifying-bash-2uthz.
A minimum reproducible demo should contain as little data and components as possible but can still illustrate your problem. This is the best way for us to reproduce it and solve the problem faster.

https://codepen.io/Ovilia/pen/dyYWXWM
this is one of the chart that i use in the project, is there anything that's causing the error in the option?

@flyaway22 Please provide a minimum reproducible demo for the issue either with https://codepen.io/Ovilia/pen/dyYWXWM , https://www.makeapie.com/editor.html or https://codesandbox.io/s/mystifying-bash-2uthz.
A minimum reproducible demo should contain as little data and components as possible but can still illustrate your problem. This is the best way for us to reproduce it and solve the problem faster.

https://codesandbox.io/s/proud-shadow-gbpme
this is one of the chart that i used for my project. it was made using echart 4.8. Is there anything that's causing the error here?

I can't get this error from your project


Partial bitstream support

This PR adds partial bitstream generation support to the switch_processing example.
Submodule dependencies:
prjxray: https://github.com/SymbiFlow/prjxray/pull/1492
xc-fasm: https://github.com/SymbiFlow/xc-fasm/pull/6

The changes in this PR look okay, but I think a couple things are missing.
First, there needs to a be a usage document on how to use this flag safely.  Just reading the comment in the cmake file doesn't seem nearly enough.  For example, there is no discussion on what happens if the partial reconfiguration region overlaps a frame address, etc.
Second, there doesn't appear to be a test that verifies the partial reconfiguration files work as intended.  For example, I would expect that you'd want to do something like a simulation on fasm2bits before and after the partial reconfiguration was applied that shows the different behavior.
Third, has this been tested in hardware?  If so, how was that test done, and how could others redo the test?


List, delete Replica snapshotapi

IIRC, we are gonna start using 'develop' as our main branch, to be aligned with all our other repos.

bors merge

bors merge

bors cancel

bors merge


relationship validation must allow NONE and NOASSERTION

The spec explicitly allows the keywords NOASSERTION or NONE on the right hand side of a relationship (see here). When trying to parse the example file SPDXJSONExample-v2.3.spdx.json the validation returns the following messages:
ValidationMessage(validation_message='spdx_id must only contain letters, numbers, "." and "-" and must begin with "SPDXRef-", but is: NOASSERTION', context=ValidationContext(spdx_id=None, parent_id=None, element_type=<SpdxElementType.RELATIONSHIP: 13>, full_element=Relationship(spdx_element_id='SPDXRef-CommonsLangSrc', relationship_type=<RelationshipType.GENERATED_FROM: 25>, related_spdx_element_id='NOASSERTION', comment=None))),
ValidationMessage(validation_message='did not find the referenced spdx_id NOASSERTION in the SPDX document', context=ValidationContext(spdx_id=None, parent_id=None, element_type=<SpdxElementType.RELATIONSHIP: 13>, full_element=Relationship(spdx_element_id='SPDXRef-CommonsLangSrc', relationship_type=<RelationshipType.GENERATED_FROM: 25>, related_spdx_element_id='NOASSERTION', comment=None)))

fixed by #390


rxjs operators

I'm a bit confused on how to import rxjs operators from this fork.
This seems to not work:
import { filterMap } from 'ts-results-es/rxjs-operators' //Cannot find module 'ts-results-es/rxjs-operators' or its corresponding type declarations

However,
import { filterMap } from 'ts-results-es/esm/rxjs-operators'

Should work.
BUT I assume that would remove compatibility for common js.
Any solution to fix this issue?

Hey, oh yeah, I think I broke this when I added some ESM-compatibility changes. We don't use RxJS here. I'm not sure what's the right way to solve this and I probably don't have resources to figure it out right now.

That’s fine. I’ll try to figure it out 💪
On Mon, Apr 3, 2023 at 7:48 AM Jakub Stasiak @.***>
wrote:

Hey, oh yeah, I think I broke this when I added some ESM-compatibility
changes. We don't use RxJS here. I'm not sure what's the right way to solve
this and I probably don't have resources to figure it out right now.
—
Reply to this email directly, view it on GitHub
https://github.com/lune-climate/ts-results-es/issues/38#issuecomment-1494263273,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASJS6O32E6FGZW7UK4WGBUTW7LBKBANCNFSM6AAAAAAWPZED5A
.
You are receiving this because you authored the thread.Message ID:
@.***>

https://github.com/jacoobes/ts-results-es
in progress at the moment

#39

This should be fixed in 3.6.1 that I just released (includes https://github.com/lune-climate/ts-results-es/pull/45), please reopen if not.


ostree: fix TLS errors

Motivation for this change
Fixes #119634. In short, ostree wasn't able to pull from https:// remotes
Things done

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

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

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

Result of nixpkgs-review pr 119661 at a350ad30 run on x86_64-linux 1

2 packages marked as broken and skipped:

libsForQt512.discover
libsForQt514.discover

1 package failed to build:

pantheon.appcenter

14 packages built successfully:

flatpak
flatpak-builder
gnome-builder
gnome3.gnome-software
haskellPackages.gi-ostree
libsForQt5.discover (libsForQt515.discover ,plasma5Packages.discover)
malcontent-ui
minishift
ostree
pantheon.sideload
rpm-ostree
vala-language-server
xdg-desktop-portal
xdg-desktop-portal-gtk

1 suggestion:

warning: unused-argument
Unused argument: fetchpatch.
Near pkgs/tools/misc/ostree/default.nix:3:3:
  |
3 | , fetchpatch
  |   ^

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement.

Thanks! Does this need a backport?

I'm not sure. If you mean "is this broken in 20.09" then I just checked and yes, there's the same problem. I don't know how much anyone uses ostree directly though, and it works fine when used through flatpak for some reason, so it might not be important to backport this fix.

would be great if you could test https://github.com/NixOS/nixpkgs/pull/119773

looks good
~ $ nix build nixpkgs/b2a189a8618fc1ba61593016fe5699b38971b89f#ostree
~ $ mkdir foo
~ $ cd foo
foo $ ../result/bin/ostree --repo=. init --mode=bare-user-only
foo $ ../result/bin/ostree --repo=. remote add flathub https://dl.flathub.org/repo --set=gpg-verify=false
foo $ ../result/bin/ostree --repo=. pull flathub runtime/org.freedesktop.Platform.GL.default/x86_64/20.08
1 delta parts, 20 loose fetched; 93077 KiB transferred in 7 seconds; 261.0 MB content written
foo $


Output of Pygbe

The output of pygbe of the Lysozyme example give me three files: outout.log, resultspickle and phi.txt. It is possible to visualize the electrostatic surface in VMD? What is the phi.txt file? Which program can open it?

Hi @Marr575,
The phi.txt file is in fact the electrostatic potential and its derivative on the molecular surface, for each triangular element. Then, the first N terms will be the potential and the second N terms the normal derivatives (taken from the inside of the surface). If you have more than one surface, it will have potential_{surface 1}, derivative_{surface 1}, potential_{surface 2}, derivative_{surface 2}, and so on. Surface 1, surface 2, etc. will be in the same order as are in the .config file. I've never tried to open this with any software, but probably you can extract the data you need (for example, the first N values), and using the mesh VMD should be able to plot that.
Hope this helps!

More or less. Mmmmmm, to extract the electrostatic potential from the phi.txt will be a little complicated for me. But in the figures of your articles you have the figures with the representation of the electrostatic potential on the surface of the enzyme, how you did it? At the beginning I had the idea with a .dx file or add the phi.txt as extra information in a .pqr or a mesh file at the moment of create the representation, but that does not work. Why the output of the electrostatic potential is in the form of a .txt, any special reason?
gracias totales
Manuel Ruiz

ok. mmmmmmmm at the end I think could get the visualization of the example of Lysozyme. It is necessary to convert the pickle file to opendx, and then use VMD in volume representation for that I used this:
https://www.mdanalysis.org/GridDataFormats/
Lysozyme.tar.gz
Is ok?

mmmmmmmm at the end I copied the xyz colums from the .vert file, the vertex from the .face file, and the phi values from the phi.txt and create a VTK file and open it with Paraview software. Is it ok?
I got this.
Lysozyme.vtk.tar.gz


Remove Leaderboard Images

From some local testing it appears that rendering the images in the leaderboard is causing significant slowdowns during the 'leaderboard' command. This PR removes the images entirely, although downscaling them might be another option.

If we remove user images from the leaderboard we probably would want remove these lines:

https://github.com/liatrio/gratibot/blob/2a09a5c39f5d7158483a4dfe5fd2c51f572e658c/skills/leaderboard.js#L269
https://github.com/liatrio/gratibot/blob/2a09a5c39f5d7158483a4dfe5fd2c51f572e658c/skills/leaderboard.js#L297

I am not sure I understand why including an image in the response message is responsible for slowing down gratibot itself.  I'd assume that if the image was too large or something, the problem would manifest itself when your slack client tried to render the large image.
But I trust your judgement on this.

@gesparza3 - good catch. Thank you.

Added commit to remove user icon related function calls.


iossue with remnux upgrade on newly downloaded VM

hello,
I downloaded the VM remnux-v7-focal.ova and verified that the checksum is correct.
I imported the ova into VMWare fusion and I didn't have any issues.
When I run remnux upgrade the process stops at the end with:
>> Running: ssh
Update returned exit code not zero
Error: Update returned exit code not zero
    at ChildProcess.<anonymous> (/snapshot/remnux-cli/remnux-cli.js:569:23)
    at ChildProcess.emit (events.js:315:20)
    at maybeClose (internal/child_process.js:1021:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)

Sometimes problems occur due to network or server issues when

I tried the remnux upgrade multiple times and I also tried the remnux update, but I receive the same error.
I checked in the file /var/cache/remnux/cli/v2023.15.1/saltstack.log and the first occurrence of result: false shows:
start_time: '12:22:07.381141'
  archive_|-remnux-mitmproxy-archive_|-/usr/local/bin/_|-extracted:
    __run_num__: 321
    __sls__: remnux.python3-packages.mitmproxy
    changes: {}
    comment: 'One or more requisite failed: remnux.python3-packages.mitmproxy.remnux-mitmproxy-source'
    duration: 0.009
    result: false

I checked the my firewall is not blocking the connection, and it doesn't.
It seems the dependencies are all complaining for this file.
I attached the saltstack.log in case it can be relevant.
How can I move on and get the VM updated?
Thanks,
Alex
saltstack.log.zip

Hi @horserunning , can you provide the output of the following command:
cat /etc/apt/sources.list.d/vscode.list

Sure:
remnux@remnux:~$ cat /etc/apt/sources.list.d/vscode.list
deb [arch=amd64 signed-by=/usr/share/keyrings/MICROSOFT.asc] http://packages.microsoft.com/repos/vscode stable main

Sure:
The content of the file:
remnux@remnux:/etc/apt/sources.list.d$ cat microsoft.list
deb [arch=amd64] https://packages.microsoft.com/ubuntu/20.04/prod focal main

output of the update
remnux@remnux:/etc/apt/sources.list.d$ sudo apt-get update
Get:1 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB]
Hit:2 https://download.sysdig.com/stable/deb stable-amd64/ InRelease
Hit:3 https://download.docker.com/linux/ubuntu focal InRelease
Get:4 https://repo.saltproject.io/py3/ubuntu/20.04/amd64/3004 focal InRelease [2,125 B]
Get:5 http://packages.microsoft.com/repos/vscode stable InRelease [2,413 B]
Hit:6 http://us.archive.ubuntu.com/ubuntu focal InRelease
Get:7 http://ppa.launchpad.net/gift/stable/ubuntu focal InRelease [18.0 kB]
Hit:8 https://download.mono-project.com/repo/ubuntu stable-focal InRelease
Hit:9 http://www.inetsim.org/debian binary/ InRelease
Get:10 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]
Get:11 https://packages.microsoft.com/ubuntu/20.04/prod focal InRelease [3,611 B]
Hit:12 http://deb.nodesource.com/node_14.x focal InRelease
Get:13 http://us.archive.ubuntu.com/ubuntu focal-backports InRelease [108 kB]
Hit:14 http://ppa.launchpad.net/openjdk-r/ppa/ubuntu focal InRelease
Get:15 http://packages.microsoft.com/repos/vscode stable/main amd64 Packages [165 kB]
Get:16 http://ppa.launchpad.net/remnux/stable/ubuntu focal InRelease [18.1 kB]
Hit:17 http://ppa.launchpad.net/sift/stable/ubuntu focal InRelease
Hit:18 http://ppa.launchpad.net/wireshark-dev/stable/ubuntu focal InRelease
Get:19 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages [2,085 kB]
Get:20 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages [575 kB]
Get:21 http://us.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages [807 kB]
Get:22 http://security.ubuntu.com/ubuntu focal-security/main amd64 c-n-f Metadata [12.5 kB]
Get:23 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages [821 kB]
Get:24 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [2,469 kB]
Get:25 http://us.archive.ubuntu.com/ubuntu focal-updates/main Translation-en [421 kB]
Get:26 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 c-n-f Metadata [16.4 kB]
Get:27 http://us.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages [1,047 kB]
Get:28 http://us.archive.ubuntu.com/ubuntu focal-updates/universe i386 Packages [722 kB]
Fetched 9,521 kB in 4s (2,252 kB/s)
Reading package lists... Do
```ne

Hi @horserunning , it looks like everything seems to be fine. You should be able to try your upgrade again without issue.
For what it's worth, the error you gave here does not match what's in the log you provided in the same comment. This is what it shows in your attached log for the mitmproxy archive, so possibly you provided the wrong log file?
 archive_|-remnux-mitmproxy-archive_|-/usr/local/bin/_|-extracted:
    __id__: remnux-mitmproxy-archive
    __run_num__: 322
    __sls__: remnux.python3-packages.mitmproxy
    changes: {}
    comment: All files in archive are already present
    duration: 360.519
    name: /usr/local/bin/
    result: true
    start_time: '13:59:23.165953'

Thank you for your reply, and I apologize for the delayed answer.
Regarding the log file, I have two directories containing the saltstack.log, and the one on the 2023.15.1 directory is the one that gets updated.
Anyway, magically, the remnux upgrade worked fine today, and I have no idea why because I didn't change anything on my side or in my network.
Thank you for helping me with this issue.


Allow text-2.1, bytestring-0.12, filepath 1.5

Builds fine locally, in particular with
constraints: text == 2.1.*
constraints: bytestring == 0.12.*
constraints: filepath == 1.5.*

I published a matching revision to Hackage


Add web based payment app flow diagram.

This pull request will add a diagram that illustrates how web based payment app works.
CC: @petele

Whoops!
There were 2 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/fundamentals/payments/payment-apps-developer-guide/web-payment-apps.md#L271 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/fundamentals/payments/payment-apps-developer-guide/web-payment-apps.md#L294 - Common typo found: 'ServiceWorker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.

:tada: This has been pushed live to https://developers.google.com/web/


Server Crash Report 1.15.2

Issue description:
Server Crash Report
Version (make sure you are on the latest version before reporting):
Forge:  31.1.0
industrial-foregoing-1.15.2-2.2.1-f27c515
https://gist.github.com/xxlio109/4eceb3689a56c9b8dd0ffc77738b1a0e

Not an IF issue its not even mentioned in the crash report


Replace anything with ControlNet

I want to use ControlNet to replace anything such that foreground image shape does not change, only the background will change as per the text prompt. Can we do this? If yes, then please guide me. I am interested to change the product background as per the text prompt but do not want to change the product shape.
Thanks

Hi,
Is there any update on this, can we use controlnet with replace anything?
Thanks

any update on this

Thanks, RuoyuFeng. I am looking for python code which can be used commercially. Automatic 1111 is an AGPL license.


iDEAL pay

Coverage increased (+0.3%) to 100.0% when pulling 84cfa9d22856d87f739cb137ea51087ed88af840 on Trimnosh:105-ideal-payment into bf6563cc0bdd9726dfee5a4ed90fbb3d5fceb301 on wirecard:105-ideal.

Coverage increased (+0.3%) to 100.0% when pulling 59c9bd963019f4f4f17b8efefba83c25a50d2d50 on Trimnosh:105-ideal-payment into bf6563cc0bdd9726dfee5a4ed90fbb3d5fceb301 on wirecard:105-ideal.

Coverage increased (+0.3%) to 100.0% when pulling 766cfd6759c67bcaac9b0ef305c72653e3ff1fe6 on Trimnosh:105-ideal-payment into bf6563cc0bdd9726dfee5a4ed90fbb3d5fceb301 on wirecard:105-ideal.

Coverage increased (+0.3%) to 100.0% when pulling 6c17d826f3913463203967dc76dc14a2cbb16c6e on Trimnosh:105-ideal-payment into bf6563cc0bdd9726dfee5a4ed90fbb3d5fceb301 on wirecard:105-ideal.

Coverage decreased (-2.1%) to 97.583% when pulling 7937fdabbd78cadf89cbb750f07e3d9251082e82 on Trimnosh:105-ideal-payment into bf6563cc0bdd9726dfee5a4ed90fbb3d5fceb301 on wirecard:105-ideal.

Coverage increased (+0.2%) to 99.849% when pulling 026a28108b249f7d50da20b142c3a3ccf82efbd6 on Trimnosh:105-ideal-payment into bf6563cc0bdd9726dfee5a4ed90fbb3d5fceb301 on wirecard:105-ideal.

Coverage increased (+0.3%) to 100.0% when pulling b557cc544ac066f9fcf170570efeeafb253a602a on Trimnosh:105-ideal-payment into bf6563cc0bdd9726dfee5a4ed90fbb3d5fceb301 on wirecard:105-ideal.


Resources: Adding lint check for testing; re-enabling tests

Closing, this is meant to point at my fork :fearful:


Schedule font size too small

Schedule font size too small!!! @ayush29feb make it like 30% bigger please. 😁

Goto js/schedule.js and change config.fontSize

increased to 18


fix for delay in fee events pk count table

the fee_events_pk_count table is currently delayed. this fix makes sure we can still get fresh data in our gold tables even during this delay. Julius has an open ticket with HEVO to address the issue, but this will fix the issue in the meantime


TODO: Update the requirements file

The requirements file is missing tqdm package.

Hey Akshay, thanks for pointing it out, and fixing it at the same time. 😄


runtime: NumCPU() should respect zone CPU cap on illumos

In the machine independent runtime bits:
// NumCPU returns the number of logical CPUs usable by the current process.
//
// The set of available CPUs is checked by querying the operating system
// at process startup. Changes to operating system CPU allocation after
// process startup are not reflected.
func NumCPU() int {
        return int(ncpu)
}

On illumos, this is initialised using sysconf(3C) with the _SC_NPROCESSORS_ONLN variable, returning the "number of processors online":
func getncpu() int32 {
        n := int32(sysconf(__SC_NPROCESSORS_ONLN))
        if n < 1 {
                return 1
        }
        return n
}

func osinit() {
        ncpu = getncpu()
...

The operating system affords several different mechanisms for controlling (capping) the resources used by a zone.  One is to place the zone in a processor set, which would generally exclude other zones from sharing the CPUs in the set.  When in configured to run under a processor set, the _SC_NPROCESSORS_ONLN value would reflect the number of processors in that set, which is fine.
Another common limiting mechanism is a CPU cap, which works differently.  All available processors are still visible as online, and are potentially available for use.  The cap is enforced by preventing processes from running for more than the configured quantity of CPU seconds per second.  For example, if a system has 48 processors and the zone has a cap equivalent to 2 CPUs, the zone may expend its cap running just two threads on two actual CPUs, or on 48 threads each running for 1/24 seconds per wall clock second.
It should be reasonably easy to enhance the getncpu() function to check for a CPU cap when determining the count of usable CPUs.

I wrote a short C program that demonstrates roughly what we'll need to do to check for the cap:
#include <stdlib.h>
#include <stdio.h>
#include <unistd.h>
#include <rctl.h>
#include <err.h>
#include <errno.h>

int
main(int argc, char *argv[])
{
	int32_t sysconf_ncpus = (int32_t)sysconf(_SC_NPROCESSORS_ONLN);

	printf("ncpu = %d\n", sysconf_ncpus);

	rctlblk_t *rblks[] = {
		calloc(1, rctlblk_size()),
		calloc(1, rctlblk_size()),
	};

	/*
	 * As per resource_controls(5), the "zone.cpu-cap" resource control is
	 * "the percentage of a single CPU that can be used by all user threads
	 * in a zone, expressed as an integer."  That is, a value of 100 means
	 * one whole CPU on this system.  If there is no cap, or the cap is
	 * greater than the number of actual detected CPUs, we just use the CPU
	 * count value.
	 */
	uint64_t capval = 0;

	int flag = RCTL_FIRST;
	for (unsigned i = 0; ; i++) {
		int flag = i == 0 ? RCTL_FIRST : RCTL_NEXT;
		rctlblk_t *rblk = rblks[i % 2];
		rctlblk_t *rblkprev = rblks[(i + 1) % 2];

		if (getrctl("zone.cpu-cap", rblkprev, rblk, flag) != 0) {
			if (errno == ENOENT) {
				break;
			}
			err(1, "getrctl");
		}

		int s = 0;
		if (!(rctlblk_get_local_flags(rblk) & RCTL_LOCAL_MAXIMAL) &&
		    rctlblk_get_local_action(rblk, &s) == RCTL_LOCAL_DENY) {
			rctl_qty_t v = rctlblk_get_value(rblk);

			if (capval == 0 || capval > v) {
				capval = v;
			}
		}
	}

	if (capval == 0) {
		printf("uncapped, so %d CPUs\n", sysconf_ncpus);
	} else {
		int cap_ncpus = capval / 100;

		if (cap_ncpus > sysconf_ncpus) {
			printf("cap too large, so %d CPUs\n", sysconf_ncpus);
		} else {
			printf("capped, at %d CPUs\n", cap_ncpus);
		}
	}
}

Run on a system with 8 CPUs and no cap configured:
$ ./ncpus
ncpu = 8
uncapped, so 8 CPUs

Run on the current illumos buildlet host:
[root@gobuild1 /var/tmp]# ./ncpus
ncpu = 48
capped, at 3 CPUs

I tested this on a couple of systems with a simple program:
package main

import (
        "fmt"
        "runtime"
)

func main() {
        fmt.Printf("runtime.NumCPU() = %v\n", runtime.NumCPU())
}

With no cap and 8 CPUs:
$ psrinfo | wc -l
       8
$ prctl -n zone.cpu-cap $$
process: 14207: -bash
NAME    PRIVILEGE       VALUE    FLAG   ACTION                       RECIPIENT
zone.cpu-cap
        usage               0
        system          4.29G     inf   deny                                 -
$ ./printncpus
runtime.NumCPU() = 8

With a cap and 48 CPUs:
$ psrinfo | wc -l
48
$ prctl -n zone.cpu-cap $$
process: 962118: -bash
NAME    PRIVILEGE       VALUE    FLAG   ACTION                       RECIPIENT
zone.cpu-cap
        usage              13
        privileged        336       -   deny                                 -
        system          4.29G     inf   deny                                 -
$ /var/tmp/printncpus
runtime.NumCPU() = 3


Introduice :io subproject

The purpose of this subproject is to contain I/O-related utilities used throughout the codebase. Most of the code comes from :base-services's org.gradle.internal.io package.
It is used in workers.
Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

@bot-gradle test this please.

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

The merge queue build has failed. Click here to see all failures.

The merge queue build has failed. Click here to see all failures.


feature/修改单元测试test_workflow

Codecov Report

Merging #226 (a6d997d) into v2.6.x_develop (4098ee8) will increase coverage by 0.01%.
The diff coverage is n/a.

@@                Coverage Diff                 @@
##           v2.6.x_develop     #226      +/-   ##
==================================================
+ Coverage           51.77%   51.79%   +0.01%
==================================================
  Files                 445      445
  Lines               27419    27419
==================================================
+ Hits                14197    14202       +5
+ Misses              13222    13217       -5

Impacted Files
Coverage Δ

itsm/workflow/managers.py
45.42% <0.00%> (+0.37%)
:arrow_up:

itsm/component/utils/misc.py
57.26% <0.00%> (+1.70%)
:arrow_up:

Continue to review full report at Codecov.

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


previousAttributes on Webhook events

Presently there's no implementation on previous attributes so cannot see what field changed on webhooks for update events. There's a TODO: noted currently in Event.swift
    // TODO: - Figure out how to decode this.
    /// Object containing the names of the attributes that have changed, and their previous values (sent along only with *.updated events).
    //public var previousAttributes: [String: Any]?

@Steven4294 Not entirely sure how this can be done. Because the previous attributes aren't a known type  and could be literally a subset of data for any given stripe model type it's damn near impossible to make it codable to decode the response. I'm open to any ideas you might have around this.

So the previous attributes are guaranteed to be the same type as the actual event. E.g. for a Charge event the previous attributes would be decoded as a Charge object. As long as all the fields on each model are optional it should work to just decode it as another EventObject I believe.

I'm not sure but as a test can you give that a try in a fork/branch? And see if it decodes if that type is an EventObject

Also some fields on stripe aren't optional like created and the id field of course so that might be tricky as well if only the changed attributes would show up

    "previous_attributes": {
      "attempt_count": 0,
      "attempted": false,
      "charge": null,
      "effective_at": null,
      "ending_balance": null,
      "hosted_invoice_url": null,
      "invoice_pdf": null,
      "next_payment_attempt": xxxxx,
      "number": null,
      "payment_intent": null,
      "status": "draft",
      "status_transitions": {
        "finalized_at": null
      }
    }
    ```

    So here's what the previous_attributes JSON looks like. Doesn't include some of the non-null attributes. Would need to make the created etc values optional for this to work via that method

That's be a massive breaking change. Also these fields are guaranteed by stripe and it makes it easier for people to use. Otherwise people would have to nil coalesce an id Stripe guarantees which isn't an ideal experience.

Putting it in a dictionary for now so that I can manually decode the value I'm interested in could work for now while a more stable solution is figured out:

Other idea would be to generate a protocol that includes the non-optional fields, then extend the base Charge (which dont include the non-nullable's) with the protocol, so the base event decodes the extended structs and the previousAttribute decodes the base objects

Any is not a Codable type. So the Event won't be Codable anymore and can't easily be decoded by responses from the API

One more idea, just create a new Struct PreviousAttributes which is a huge struct of all optional fields from all the other objects 🗡

What would that example look like? Can you show some code for an ideal API and how it would look?

One more idea, just create a new Struct PreviousAttributes which is a huge struct of all optional fields from all the other objects 🗡

Lmao I wish. Then we'd have to keep up with all the attributes that get added to any stripe resource which would be a nightmare

class BaseCharge {
   let amount Double: ...
}
class Charge: StripeProtocol {
   let id: String // inherit from protocl
   ...
}

public struct Event: Codable {
    public var id: String
    public var data: EventData?
    public var previousAttributes: EventDateBase
 }```

somethign like this

Another solution would be to use e.g. https://github.com/Frizlab/generic-json which is basically Any, but Codable 🙂
Not ideal, but better than nothing I think.


Feature/move remote data to image

To avoid too request limits of github, update the configure to load local files in for k8s batch jobs.

@fivejjs I removed the dask_chunks param from the gm_mads_two_seasons_training function, and restored the full string path for the slope variable as this function will only be used in notebooks for training models and not as an K8S workflow.
With the Dockerfile changes, does this mean the entire Production and Testing folders are copied to the Docker image?  If so, what is the reason for copying the Production folder? Since all the item (geojsons, models) are in the Testing folder?


Push notifications

Hello. help me pls. Do you have pushy in the background? I just can't make it work(

Hello. Yes, we do have push to notification. It should work in theory. You can turn it on in Settings > Notification settings. Make sure you press the save button.

Hi @kaparray. Yes, we do have push to notification. It should work in theory. You can turn it on in Settings > Notification settings. Make sure you press the save button.

You do have push to notification in background and handle data in flutter?

in theory, or are you sure it works for you?

Hi @kaparray,
Currently we have only tried it in controlled environment, and it has worked consistently. We do not yet have data on how consistent it is on a wide range of devices. Theoretically you are able to process the data from the firebase message, but we currently dump it into a notification as json text.

does the onbackgroundmessage method work for you?
on what devices does it work?

Yes it worked when I tested it on my device, but as it was said earlier, we do not have data and haven't tested enough to know if it is working perfectly on all devices.


Limitations about a bug for the ExpressRoute circuit.

I could not get correct value in classic metric now. I hope that limitation will write in this documents.

@pareshmu  - Can you please take a look at this one?

@hisasima Hi! We've updated the doc and it should publish soon. Thanks for the recommendation!

#please-close


P2P - Implement an Error Handling interface - implement the android error handling mechanism

https://github.com/opensrp/fhircore/issues/1015 implemented here


Extension not support python < 3.10 because use future annotation format

its a problem for centos 7 where python is old version by default
Name: isort
Module: isort
Python extension loading
Waiting for interpreter from python extension.
Python extension loaded
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/server.py", line 4
    from __future__ import annotations
    ^
SyntaxError: future feature annotations is not defined
[Info  - 1:44:10 PM] Connection to server got closed. Server will restart.
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/server.py", line 4
    from __future__ import annotations
    ^
SyntaxError: future feature annotations is not defined
[Info  - 1:44:10 PM] Connection to server got closed. Server will restart.
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/server.py", line 4
    from __future__ import annotations
    ^
SyntaxError: future feature annotations is not defined
[Info  - 1:44:10 PM] Connection to server got closed. Server will restart.
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/server.py", line 4
    from __future__ import annotations
    ^
SyntaxError: future feature annotations is not defined
[Info  - 1:44:10 PM] Connection to server got closed. Server will restart.
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/server.py", line 4
    from __future__ import annotations
    ^
SyntaxError: future feature annotations is not defined
[Error - 1:44:10 PM] Connection to server got closed. Server will not be restarted.
Traceback (most recent call last):
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/server.py", line 40, in <module>
    import utils
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/utils.py", line 4
    from __future__ import annotations
    ^
SyntaxError: future feature annotations is not defined
Error in atexit._run_exitfuncs:
TypeError: stop_all_processes() missing 1 required positional argument: 'self'
[Info  - 1:45:26 PM] Connection to server got closed. Server will restart.
Traceback (most recent call last):
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/server.py", line 40, in <module>
    import utils
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/utils.py", line 4
    from __future__ import annotations
    ^
SyntaxError: future feature annotations is not defined
Error in atexit._run_exitfuncs:
TypeError: stop_all_processes() missing 1 required positional argument: 'self'
[Info  - 1:45:27 PM] Connection to server got closed. Server will restart.
Traceback (most recent call last):
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/server.py", line 40, in <module>
    import utils
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/utils.py", line 4
    from __future__ import annotations
    ^
SyntaxError: future feature annotations is not defined
Error in atexit._run_exitfuncs:
TypeError: stop_all_processes() missing 1 required positional argument: 'self'
[Info  - 1:45:27 PM] Connection to server got closed. Server will restart.
Traceback (most recent call last):
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/server.py", line 40, in <module>
    import utils
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/utils.py", line 4
    from __future__ import annotations
    ^
SyntaxError: future feature annotations is not defined
Error in atexit._run_exitfuncs:
TypeError: stop_all_processes() missing 1 required positional argument: 'self'
[Info  - 1:45:27 PM] Connection to server got closed. Server will restart.
Traceback (most recent call last):
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/server.py", line 40, in <module>
    import utils
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/utils.py", line 4
    from __future__ import annotations
    ^
SyntaxError: future feature annotations is not defined
Error in atexit._run_exitfuncs:
TypeError: stop_all_processes() missing 1 required positional argument: 'self'
[Error - 1:45:27 PM] Connection to server got closed. Server will not be restarted.
Traceback (most recent call last):
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/server.py", line 40, in <module>
    import utils
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/utils.py", line 4
    from __future__ import annotations
    ^
SyntaxError: future feature annotations is not defined
Error in atexit._run_exitfuncs:
TypeError: stop_all_processes() missing 1 required positional argument: 'self'
[Info  - 1:47:39 PM] Connection to server got closed. Server will restart.
Traceback (most recent call last):
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/server.py", line 40, in <module>
    import utils
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/utils.py", line 4
    from __future__ import annotations
    ^
SyntaxError: future feature annotations is not defined
Error in atexit._run_exitfuncs:
TypeError: stop_all_processes() missing 1 required positional argument: 'self'
[Info  - 1:47:39 PM] Connection to server got closed. Server will restart.
Traceback (most recent call last):
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/server.py", line 40, in <module>
    import utils
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/utils.py", line 4
    from __future__ import annotations
    ^
SyntaxError: future feature annotations is not defined
Error in atexit._run_exitfuncs:
TypeError: stop_all_processes() missing 1 required positional argument: 'self'
[Info  - 1:47:40 PM] Connection to server got closed. Server will restart.
Traceback (most recent call last):
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/server.py", line 40, in <module>
    import utils
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/utils.py", line 4
    from __future__ import annotations
    ^
SyntaxError: future feature annotations is not defined
Error in atexit._run_exitfuncs:
TypeError: stop_all_processes() missing 1 required positional argument: 'self'
[Info  - 1:47:40 PM] Connection to server got closed. Server will restart.
Traceback (most recent call last):
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/server.py", line 40, in <module>
    import utils
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/utils.py", line 4
    from __future__ import annotations
    ^
SyntaxError: future feature annotations is not defined
Error in atexit._run_exitfuncs:
TypeError: stop_all_processes() missing 1 required positional argument: 'self'
[Error - 1:47:40 PM] Connection to server got closed. Server will not be restarted.
Traceback (most recent call last):
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/server.py", line 40, in <module>
    import utils
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/utils.py", line 177, in <module>
    source: str = None,
TypeError: unsupported operand type(s) for |: 'type' and 'NoneType'
Error in atexit._run_exitfuncs:
TypeError: stop_all_processes() missing 1 required positional argument: 'self'
[Info  - 1:48:08 PM] Connection to server got closed. Server will restart.
Traceback (most recent call last):
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/server.py", line 40, in <module>
    import utils
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/utils.py", line 177, in <module>
    source: str = None,
TypeError: unsupported operand type(s) for |: 'type' and 'NoneType'
Error in atexit._run_exitfuncs:
TypeError: stop_all_processes() missing 1 required positional argument: 'self'
[Info  - 1:48:08 PM] Connection to server got closed. Server will restart.
Traceback (most recent call last):
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/server.py", line 40, in <module>
    import utils
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/utils.py", line 177, in <module>
    source: str = None,
TypeError: unsupported operand type(s) for |: 'type' and 'NoneType'
Error in atexit._run_exitfuncs:
TypeError: stop_all_processes() missing 1 required positional argument: 'self'
[Info  - 1:48:09 PM] Connection to server got closed. Server will restart.
Traceback (most recent call last):
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/server.py", line 40, in <module>
    import utils
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/utils.py", line 177, in <module>
    source: str = None,
TypeError: unsupported operand type(s) for |: 'type' and 'NoneType'
Error in atexit._run_exitfuncs:
TypeError: stop_all_processes() missing 1 required positional argument: 'self'
[Info  - 1:48:09 PM] Connection to server got closed. Server will restart.
Traceback (most recent call last):
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/server.py", line 40, in <module>
    import utils
  File "/root/.vscode-server/extensions/ms-python.isort-2022.9.13221008/bundled/tool/utils.py", line 177, in <module>
    source: str = None,
TypeError: unsupported operand type(s) for |: 'type' and 'NoneType'
Error in atexit._run_exitfuncs:
TypeError: stop_all_processes() missing 1 required positional argument: 'self'
[Error - 1:48:09 PM] Connection to server got closed. Server will not be restarted.

Hello! We have received this issue and will look into it soon, thanks!

Closing as a duplicate of https://github.com/microsoft/vscode-isort/issues/152 .


Quality of Life - "Report a Bug" on the Report picker

Until we reach v1, could we have a "report a bug" option on the "Report" feature? And perhaps a hyperlink to github / discord? That way we could easily tag posts that highlight bugs since we can't hyperlink directly to posts.

Nice idea - though I want to make sure this is only on for takahe.social! I'll work on an option for that.


VeRI Mis-labeled Types

The label file for VeRI train_label.xml version 1.0 (<TrainingImages Version="1.0">) has the following typeID errors:
Cars 3, 7, and 41 in the training set are labeled as typeID="0" which does not correspond to a legal type in list_type.txt.
Car 3 is an Audi Q5, which we believe is typeID="2" (SUV).
Car 7 is a Nissan of some sort. It looks like a cross-over, so again typeID="2" (SUV).
Car 41 is a Hummer H2, which should be typeID="2" (SUV).

This issue persists, but we are working around it.


[#164] add ci tests

Fixes #164
WIP do not merge
The following changes are contained in this pull request:

All VRT reference images have been regenerated on an Ubuntu 12.04 Vagrant box
Visual regression tests now run (& pass!) on Travis
Added provisioned Vagrant config to automate setup of local environment

There are undoubtedly improvements that could be made here, this is something of a proof of concept. I started from the premise that the phantom tests need to run on travis, therefore copying the environment in a vagrant box seemed logical.
This does add overhead:

running the VRTs now needs to be done inside a vagrant box (which needs some initial setup, most of which is automated)
at some point we’ll likely need to update the environment of the vagrant box (because npm packages used in bitstyles changed, or to mimic Travis’ environment). This will mean updating the vagrant config and recreating your local box, or manually updating the environment inside the already existing box.
if you’re not deving bitstyles inside the vagrant box (which I don’t expect to be a great experience), you’ll have to push from outside vagrant, then once inside pull & switch branches before testing

Can we mitigate the extra complexity all this adds? Is it a price worth paying to get the VRTs running on travis?
Do we need the font-smoothing fix we added last week? (it was for compatibility between macs when font-smoothing preferences are set differently)
Delete if not applicable:

[x] Changed the visual appearance of object(s), or changed the tests? npm run test:build script has been successfully run and new/changed images checked visually for correctness and committed.

Every time:

[x] npm run checks script has been run without errors.

@pmeinhardt @RRorg feedback on this one greatly appreciated! I’m basically new to vagrant so it’s very possible this could be done better (perhaps even without vagrant, actually?)

The workflow feels very clumsy, with duplicating the repository. vagrant could directly mount the project directoy, so you wouldn't need to ssh into the box to change branches, pull, etc. But there is no way to use an alternative node_modules path (that I know of, maybe it could be overwritten by some hacky symlink magic inside vagrant?), so there's no way I see making the build process work for the same physical project instance in both host and vm, due to npm binary compiling.
That being said, and without being able to offer a better solution, I just want to emphasize that vagrant comes with a heavy price tag:

a whole VM system with an external setup to complete, which also has to be maintained by us
disk space consumption, download time (the precise64 box download is by now taking over 50 minutes for me), memory consumption
hardware and OS limits, vagrant depends on hardware side virtualization (VT-X, AMD-X, etc) - this will unnecessarily lock out developers on older/cheaper devices or more exotic OS configurations (Hackintosh, some Linux distributions)

We'd be adding quite a few extra layers of bloat, complexion, maintenance and gateway hurdles for what basically amounts to comparing a few bitmaps. At that point, if I had to make a call I'd rather scrap VRT completely 😐

I've last used Vagrant for virtualization about two to three years ago. Back then I think it was a great tool… (you know where this is going 😁)
For what you're trying to achieve, I'd go down a different road, if visual regression tests are a must for you even though apparently, you'll get different results based on platform/installed fonts/….
Since you're running these tests on Travis, it would make sense to me to make the render output generated in that environment the "source of truth".
To make testing consistent, I'd use the Docker image used in the Travis CI tests and just run the visual regression tests in a container based on their image, in your case: https://quay.io/repository/travisci/ci-nodejs.
The Dockerfile would look something like this:
FROM travisci/ci-nodejs

USER travis

RUN mkdir -p ~/bitstyles
WORKDIR ~/bitstyles

# create a layer with the dependencies
COPY package.json package.json
# or yarn install, whatever
RUN npm install

COPY . ~/bitstyles

CMD ["npm", "run", "styleguide"]

The .dockerignore would look almost exactly like the .gitignore, but at the very least, it would ignore the node_modules.

To inspect the generated output images, you could mount a directory on your machine as a volume for the container. Maybe you should do that anyway, if you plan on committing the updated images for wanted changes.
Hope that helps?

Lots of great feedback, thanks so much both! 👍
Initial thoughts (I’ll digest and maybe come back with more later :D), correct me if I’ve misunderstood anything:

VRTs are always dependent on browser/fonts/platform (even with the same rendering engine, checkboxes etc. look different). The thing we’re looking for is change. That’s fine. Some of our current reference images don’t actually match what you see in browser (because phantom); what’s important is that they don’t unexpectedly change.
I’m thinking this morning that it’s possible the font is the main issue. Our original reference images used helvetica because we’re on Macs, this doesn’t exist as standard on linux. If we can avoid any kind of virtualisation by changing our default font to one that exists on both linux & macs, that may be a way forward — I’ll look into that this morning.
As you both seem to agree vagrant isn't the way forward(?), I’ll look into the Docker workflow if the font change seems unusable for whatever reason.
If this PR doesn’t go anywhere, that’s totally fine! It’s exploratory. In case of failure I’d update the corresponding issue with what I’ve found here, and remove the requirement for running the VRTs on Travis (that’s the aim here, the virtualisation was just a way to get the same rendering locally & on travis).

@planktonic @pmeinhardt thoughts about this? https://github.com/bitcrowd/bitstyles/issues/269#issuecomment-276466315

I mean basically what we need is a reference that has the "before" state so we can compare it with the "after" state. Nobody says the before state has to be in the form of prerendered images, and nobody said the "before" has to look exactly the same on all devices... 😋

Yes true, if we could render the reference images from master on travis for each PR, then checkout the current branch and run the tests (render & compare), that may solve the issue of platform incompatibility.
Though that would approximately double the time it takes the tests to complete.
We’d also loose the ability to run the tests locally, unless we also provide a docker-based solution as above (or something similar).

Ah I see, EDIT: no need to checkout master if we have hosted styleguide

Ok, so based on discussions with both @pmeinhardt and @RRorg today, we have a few potential solutions. These are my notes on what we’ve discussed, please let me know if i missed/misunderstood anything.
We could keep committing reference images & use a docker virtualisation process as paul outlined above. This results in tests always being run in the same environment, so no rendering differences. It adds some complications (install & setup docker, scripts to manage the process) & a dependency in the form of Docker.
The remaining two options require reference images to be regenerated on each feature branch, as they would no longer be committed to the repo. So test time increases but we remove generated files from the repo (see #269).
GitHub Pages version:

We’d have a hosted styleguide on GH pages (see #163) 👍
Adds dependency on an external resource & the network 👎

Process:

Initially, on master:

generate styleguide
commit generated html of styleguide
Set as gh-pages content so the styleguide is available at bitcrowd.github.io/bitstyles/

On feature-branches & on travis:

generate reference images from bitcrowd.github.io/bitstyles/ styleguide
generate local styleguide from feature-branch
generate test images, compare against those generated from gh-pages
commit styleguide changes

Local subdirectory version:

Self-contained, local 👍
No hosted styleguide (at least not as a direct result of this; doesn’t preclude the GH pages thing) 👎

Process locally & on travis:

clone repo from GH into a sub directory
checkout master
generate styleguide
generate reference images
copy those reference images to 'real' local version of repo (backstopjs config is the same between  master & feature-branch, it’s complicated by subdirectory)
back up to local branch
generate styleguide
generate test images, compare against those generated above

Of course for both of the these the steps would be scripted so it’d just be one command.
As ever, feedback welcome!

To try it out, I’ve updated this branch with the 'local subdirectory' version. Tests are currently passing on Travis and locally (I’m re-running tests right now to check there’s no flakiness).
It works well; my biggest issue with this approach is the time it takes  — local test runtime is up from 4minutes to 10mins. This is due mainly to regenerating the references images every time (and checking out & npm installing a new copy of the bitstyles repo takes a couple of minutes).
@RRorg can you try this out locally? Check it works for you, but also please measure the runtime.

Quick thought: To make the "takes twice the time" issue a little less severe, you could cache the reference images by commit id (e.g. master is at 3957da62b9e7a2dfd5f27dc1c3b07dda52411380) and only re-generate, if it has changed.

@pmeinhardt Yes, that’d be great! I’m not sure how to achieve this; can we discuss it sometime?

@planktonic: sure.

TODO if this branch is to be merged:

[ ] remove the font-smoothing fix from this branch
[ ] remove the font-smoothing fix from master

After discussion with @pmeinhardt, we’re now regenerating the reference images only if the commit hash of origin/master has changed since the last time the reference images were generated. This has no effect on the first run (nor test runs after master has been updated), but it reduces the runtime of subsequent test runs back to ~4m (locally).
The caching also works on Travis, cutting the runtime by half, down to ~6m. I can’t check this thoroughly until/if this branch is on master, but I hope this should be true across all branches we push i.e. if master hasn't changed since any branch generated the images, we can skip regenerating the images on the current branch.
@RRorg @pm if/when you have some time to take a look (I’m back on this monday), any suggestions for improvements are very welcome! Better error handling, code structure… I’m no shell scripter so I imagine there’s plenty of room for improvement here :D

Hmm, I really don't like that we have to rely on taskkill for this.  We can maybe do something hacky like using screen (does it come preinstalled on Mac?) to start the styleguide process, remember the screen ID and then just abort it instead of taskkilling.
As it is, we could even think about using the github pages version - the downside to this was network & url dependency, but we have this with the current approach too.

@RRorg thanks, I’ve updated this branch again — instead of killing the styleguide by grepping its name out of ps, it’s now killing just its own child processes (note that this is complicated by the fact different OSes spawn the new processes here differently; we cannot rely on a consistent structure of process groups nor of parent/child processes). screen isn’t on macs as standard.
Network access with this approach is limited to just the request for the github repo, my assumption here is that the process is less exposed to networking issues than if every test case is a new network request.
If you’ve thoughts on that, or suggestions on the code here, please fire away :) (and @pmeinhardt!)

fixes #269


load data failure, retun nil

sorry, my bad please close this issue! Your code is great!

Thanks!! and sorry for my late relpy.
i have several question.

Did you run 'go get github.com/kuroko1t/GoMNIST' for load Mnist library?
Did you use example/mlpMnist.go?
Which code returns nil? GoMNIST.Load("./data") ?

thank you


360 Video Support

Will/can this support 360 videos?

I created this package because the original one was not compatible with the latest versions of Flutter. If there are integrations that you would like to make, you can submit a pull request with the code to be corrected or added. Unfortunately, I don't have the time to add further features, but I am currently only maintaining the package for the latest versions of Flutter and dependencies of the component from any updated packages.

got it thanks. i found a few that work ok
video_player_extra
video_360
vr_player

ok. there are alternatives.
so I close this issue.


ci: drop dead code from yml

Triggers for release.yml are specified in the workflow itself:
name: Release

on:
  workflow_dispatch: # Manual triggering to re-run a release with a different run_number
  push:
    branches:
      - release

given that it misses workflow_call, I am actually surprise that we don't get any kind of error for the pipeline-main.yml...

given that it misses workflow_call, I am actually surprise that we don't get any kind of error for the pipeline-main.yml...

Ha - https://github.com/tigerbeetle/tigerbeetle/actions/workflows/pipeline-main.yml
So it turns out the answer is, pipeline-main.yml is not running at all, and the checks we see on main are from the merge group :exploding_head:

@cb22 so merging this as is should fix it, right? Or is there something you want me to do here?

@cb22 so merging this as is should fix it, right? Or is there something you want me to do here?

It will - what I meant to add though, was since it's been broken all this time and no one has noticed, do we need it at all?

I think we do, for two reasons:

"new code that passed not-rocket-science" is a good trigger to have, and exactly the thing we need for workbench
running a second round of CI is helpful to fish out any residual flakes

The non-discoverability is a bummer, but I think it'll get fixed soon:

the workbench should let us notice that something's off with our chars, so if things do not run at all, we'll notice
once the workflow parses, hopefully we'll also get a :x: in github's UI

hopefully we'll also get a ❌ in github's UI if any particular job fails

Red crosses confirmed!


refactor: refine thread variant for windows

close #4014, check thread id before making it into handle on Windows.

Great, thanks! Could you squash this into a single commit? (Using git rebase --interactive --keep-base to keep the diff nicer.)


Admin Router: Adding version endpoint to agent

High Level Description
Adding dcos version endpoint to agent
Related Issues
Cluster check
Checklist for all PR's

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[ ] Read the DC/OS contributing guidelines
[ ] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and Review Process
What is the review process and when will my changes land?
All PRs require 2 approvals using github's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

@mesosphere-mergebot Ready for review

@mesosphere-mergebot label Ready for review

@branden @darkonie ready for review

@mesosphere-mergebot bump-ee

@vespian @karlkfi Ping for review, an adminrouter expert should take a look.

@karlkfi currently the master has dcos-version . If we change that it would have to be in master and agent, I am not sure what implications that might have on users who rely/script against this endpoint. I lean towards not changing it.
For newer endpoints I agree with you.

This IS a new endpoint on agent nodes.
Changing it on the master node can be done in a reverse compatible way using a rewrite or redirect.
I recommend a policy of reviewing tech debt every time you change something in the vicinity. This is a prime example of a broken window being copied and creating more broken windows.

I will change both in that case, do you know if product has any issues?

If it improves UX of the API and is reverse compatible, then I doubt product will mind. They haven't historically taken much direct interest in the API.
However, if we're going to change the dcos-metadata path, I would recommend changing both files currently served under it: dcos-version and ui-config.
I'll bring it up in the tech leads mailing list and see if anyone has any reservations.

@karlkfi @amitaekbote We do not have a clear view/design on what we want the API to look like, we also do not have any deprecation policy for the "redirect" endpoints and ATM they have to be maintained forever.
Please do not rename/rewrite/redirect anything until we have a clear API design doc for Admin Router API along with 1-2 releases deprecation policy.
I would very much like to avoid having redirects to rewrites in Admin Router when/if the policy/point of view changes again. On top of that - the more complex the config is, the more complex testing it becomes.
Lets merge this PR as-is and concentrate on fixing bugs for the time being (there are lot's of them in Admin Router).
Thanks.

Also, as an example of partially finished improvements:

we still have not finished slave -> agent transition. I keep scrubbing slave term from Admin Router and adding rewrites/redirects+tests.
I just finished backporting /marathon rewrite from EE to Open in DCOS_OSS-1016.
/system api is inconsistent, i.e. /system/v1/logs/v1/ vs. /system/health/v1
etc...

My point is - I am totally in for API refactoring and some help in fixing it. But I would very much like to see a decent design doc with support from product and a roadmap/resources before we even start. Till then let's try to keep things simple and concentrate on important stuff.
Thanks.

@mesosphere-mergebot label Ship it

@amitaekbote Could you please prefix your PR name with "Admin Router:"? This allows us to easily track all the AR PRs that are in-flight.

@amitaekbote continuous-integration/jenkins/pr-head because there are docs changes, please try executing make api-docs and committing the changes. Thanks!

Once this passes those AR tests, this can ship again

@adam-mesos this is what i got after running make api-docs. Ill follow up on this today

@adam-mesos @vespian this is all passing with the make api-docs. good for ship it?

I hereby declare my review for this PR as still valid and in force. This PR shall be merged by the power given my by the Python and NGINX combined!
:D

I thought this was already merged as part of #1535 - it was probably rebased and we can just close this, right? @adam-mesos ?

Apparently this PR was kicked out of #1511... :(

Alright, I think I know what happened.... We merged the dcos-enterprise equivelent PR, but not the OSS one, because the OSS one didn't have the matching yaml/html changes.

Yup because of make api-docs, should go on the next train! Thanks :)


Composer - Block editing r/rw attrs

Currently forms are open for editing all of the values.
Additionally we need to block certain activities on embedded shapes like deleting connection or the shape itself if it's they are r/rw

That include blocking removing connection between core shape and it's embedded entity if it has it as rw value, or limits doesn't allow that


Duplicate property in boilerplate CSS - number sorter project

Describe the Issue
The Number Sorter project seems to have a duplicate property in the CSS boilerplate.
Affected Page
https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures-v8/learn-basic-algorithmic-thinking-by-building-a-number-sorter/step-1
Your code
form {
  width: 100%;
  padding: 15px auto;
  text-align: center;
  padding: 15px;
}

Expected behavior
Normally there'd only be one padding, right?
Screenshots
No response
System
All
Additional context
No response

Yeah, that is an oversight during the many revisions of this project.
I vote to keep the padding 15px on all sides
form {
  width: 100%;
  text-align: center;
  padding: 15px;
}

We can open this up for contribution

Note to interested contributors
This change will need to be applied to all css files for all steps
This has been opened for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors.
If you would like to contribute and have not read the contributors docs, please do so here: https://contribute.freecodecamp.org/#/
If you have any issues with contributing, be sure to join us on the contributors channel, or on the contributors sub-forum

Could anyone from the repo tell where this file is situated, because this file has 2 paddings in all the other languages except English, but we are allowed to only change english files right, so I don't know what the default language of site site is even though everything is in English.

@jayanth920
I looked through the file history and it looks like this issue was fixed in an unrelated PR here
https://github.com/freeCodeCamp/freeCodeCamp/pull/52744
it looks like they went ahead and fixed that issue even though the PR was concerning another matter.
On the next production deploy, this fix should show up on the site.
As such, I will go ahead and close this issue

@jayanth920
I looked through the file history and it looks like this issue was fixed in an unrelated PR here
#52744
it looks like they went ahead and fixed that issue even though the PR was concerning another matter. On the next production deploy, this fix should show up on the site.
As such, I will go ahead and close this issue

Aaah thank you so much, I was breaking my head all over the place lol, I was like how can I not solve such a simple issue.


Update the installfest checklist to an actual checklist

also remove the hint, since it doesn't seem to appear in the checkpoint anywhere anyway.

LGTM


Questions about cable covers.

Refined Storage 1.5.21
MC 1.12.2
Is there a way to use cable covers in the latest 1.12.x version?
I used Simple Covers and MC Multipart in MC 1.10, but Simple Covers has not been updated to 1.12.x
I have not been able to find documentation on how to cover cables in 1.12.x
If there is no solution implemented, maybe you would be willing to implement facade blocks in RS? The way XNet implements them seem simple enough that they could maybe be ported for RS?

Is there a way to use cable covers in the latest 1.12.x version?
Yes

I used Simple Covers and MC Multipart in MC 1.10, but Simple Covers has not been updated to 1.12.x
Use Chisel & Bits

I have not been able to find documentation on how to cover cables in 1.12.x
https://refinedstorage.raoulvdberge.com/wiki/hiding-the-cable-blocks

If there is no solution implemented, maybe you would be willing to implement facade blocks in RS?
No.

Thank you. I cannot use C&B since my FPS goes from 50 to 4 when I include it. Guess I will wait for simple covers to be updated.


Code cleanup + Optimization + Refactoring.

hey everyone, hope that you are doing well.
In this PR, I've fixed the callback hell that we had in our backed code-base. Also, I've optimized the code execution for faster and more efficient server state.
Please refer to the git commits for better info.
Hope that is clear.
Massiles.

Note: This PR is built on top of  #120.
Hope that is clear.
Massiles.

This looks amazing Massiles, Thank you!
On Sat, May 7, 2022 at 1:01 AM Massiles Ghernaout @.***>
wrote:

Note: This PR is built on top of #120
https://github.com/fairfield-programming/backend-server/pull/120.
Hope that is clear.
Massiles.
—
Reply to this email directly, view it on GitHub
https://github.com/fairfield-programming/backend-server/pull/121#issuecomment-1120134988,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHHTLJWLEOEPSUD7VZ73YGDVIX2LXANCNFSM5VJ3QRFA
.
You are receiving this because your review was requested.Message ID:
@.***>


Suppress Build Error

For the OSX build.
Creation of buffer needs to be force-unwrapped for Xcode 13 to build properly.

Duplicate of https://github.com/marmelroy/Zip/pull/221


Debug builds should be compiled without optimizations

Currently by default the Swift Compiler - Code Generation > Optimization Level setting is set to Fast for both Debug and Release. If you open the project in XCode to investigate a crash, debugging symbols are not available. It would be nice to have it set this to None for Debug builds.

Hmmm, in my case it is configured to None for Debug mode. Which version of XCode are you using ?

I have XCode 7.3

Fixed in version 1.6.0 thanks to @viskin PR.


How can I have lint alerts on build?

Can you precise the question? You want something like "build": "eslint . && next build"?

I want the lint errors during compilation on dev and build time. Is it possible?

You can customize the webpack config and add a preloader for linting.

Yes, like Create React App:

I hope you can use this: https://github.com/MoOx/eslint-loader
Try to prepend this to the beginning of the rules.