chore(deps): update module github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper to v1.37.2

This PR contains the following updates:

Package
Type
Update
Change

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
patch
v1.37.0 -> v1.37.2

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.37.2
Compare Source
Bug Fixes

deps: update gomod (#855) (131e322)

v1.37.1
Compare Source
Bug Fixes

deps: update gomod (#854) (a79629e)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

ℹ Artifact update notice
File name: tests/go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

13 additional dependencies were updated
The go directive was updated for compatibility reasons

Details:

Package
Change

go
1.21 -> 1.22

github.com/IBM-Cloud/bluemix-go
v0.0.0-20240423071914-9e96525baef4 -> v0.0.0-20240719075425-078fcb3a55be

github.com/IBM-Cloud/power-go-client
v1.6.0 -> v1.7.1

github.com/IBM/go-sdk-core/v5
v5.17.3 -> v5.17.4

github.com/IBM/platform-services-go-sdk
v0.63.1 -> v0.67.0

github.com/IBM/schematics-go-sdk
v0.2.3 -> v0.3.0

github.com/IBM/vpc-go-sdk
v0.51.0 -> v0.57.0

github.com/gruntwork-io/terratest
v0.46.15 -> v0.47.0

github.com/hashicorp/go-getter
v1.7.4 -> v1.7.5

github.com/hashicorp/go-retryablehttp
v0.7.5 -> v0.7.7

golang.org/x/crypto
v0.24.0 -> v0.26.0

golang.org/x/sync
v0.7.0 -> v0.8.0

golang.org/x/sys
v0.21.0 -> v0.23.0

golang.org/x/text
v0.16.0 -> v0.17.0

/run pipeline

:tada: This issue has been resolved in version 1.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Random string setter added

• Random string generator added
• Unit tests added

Coverage increased (+0.3%) to 81.898% when pulling f984f669f775d05f4b49ccf7b8c5ed19ec512bea on alkekkonen:feature/setRandomSequence into 9d0646099b66afb1f7cd1a08212d3fee134a33df on alfa-laboratory:master.

Coverage increased (+0.5%) to 82.044% when pulling 7988064db526d7f1c7618c1f6e9d44cf8e47061c on alkekkonen:feature/setRandomSequence into 9d0646099b66afb1f7cd1a08212d3fee134a33df on alfa-laboratory:master.


Fixed margin allignment problem

Fixed an issue with the margins being different every alternate page. Only noticed this after I handed in my diss 😢
Before:

After:

This is a deliberate choice. Your dissertation is printed on double sided paper and required alternating binding margin.

Oh mb then

This can be configured directly in the template, but we assume that the guidelines are the same to everyone in ECS


fix css file , add progress bar

i added a progress bar for the % done..  set color in css (default blue)
also, fixed the css file again..
when MM loads a module, it wraps it in a div, with the modulename as a class
so, if you always select the class first in the selector clause, then it can never apply to any other module..
the clasnames row, column...  don't use the modulename itself.. just the selector clause in the css file...

Thank you. I might tweak the progress bar a bit later. But a good idea.

I just updated the code so it should work on all browsers. You can also customize the colors of the progress bars with custom css as described in the updated README.md


Develop backend validation (apollo graphql error parsing)

@vilkazz Could you please describe what's the intention for this user story?
Thanks

Invalid GraphQL queries are handled and explicitly throw an exception at API level


Add devel tag devcontainer

It would be great to have the devel version of R since there are going to be some breaking changes in the next release.
I've tried messing around with it myself to get it to build a container using r-ver:devel but I can't seem to get it to work.

Thank you for your interest in this project.
I think the issue is build frequency and demand.
I mean rocker/r-ver:devel is built daily, but CI in this repository does not build unless me (or other maintainers) run.
This means that the image built here will always be older than the latest devel version.
What we are doing here now is just installing two Dev Container Features, ghcr.io/devcontainers/features/common-utils and ghcr.io/rocker-org/devcontainer-features/r-rig, on top of rocker/r-ver etc., so we figure if users want to try the latest devel version they can build this themselves.
Where did you not do well with your build?


Improved Error Messages

Description
This draft PR enhances error messages for end users by replacing memory references with custom messages based on error codes and locations. These changes improve the clarity and usability of the error messages.
Key Updates

Implemented custom error messages for the project_handler module.
Errors now provide detailed and actionable information.
Examples:

ERRO[0000] failed to create project: Project abc already exists
ERRO[0001] failed to delete project: Project my_project not found or already deleted

Error codes and types are mapped from the endpoint documentation:
Harbor Go Client Documentation.

Notes

Current changes are restricted to the project_handler module.
Additional modules will be updated after approval of this approach.

@bupd @Vad1mo could you please review this PR, Thanks

Please follow the #262 (comment)
* remove the prefix as mentioned.

@bupd the prefix is generated by the Errorf method of the fmt module, it we want to remove it we can use the Print method only, should i make that change?


add test for oss-fuzz

Move the fuzz checker code upstream as requested in this review https://github.com/google/oss-fuzz/pull/1694

Currently this fuzzer only tests with the default compression level (6), meaning either deflate_medium or _slow, depending on compilation choices. Maybe it would be better to get each of the compression algorithms tested equally? That would require changing to using the compress2 function, and selecting a compression level.
Have a look at configuration_table in deflate.c for example. We have deflate_quick, _fast, _medium and _slow being used at different compression levels.
How about the fuzzer takes a buffer and compresses it with levels 1, 3, 6, 7 and verifies each of the returned compressed buffers. (lvl 6 could be changed to lvl 4 to increase speed, but since lvl 6 is the default level, that might be an even more compelling reason not to.)
Btw, from a security standpoint, testing broken compressed streams through the decompressor would likely be very valuable. This is where a corrupt .png/.pdf etc file would be able to cause havoc on the unsuspecting users machine.

These are very good points: I will add code to the compress_fuzzer to check compression at different levels.
I will add a decompress_fuzzer that starts decompressing the inputs of the fuzzer, then it will compress that and finally match that the output of decompress+compress matches the original input.

The decompression tester might need a semi-valid header to actually get through to the decompression code more often, and not just fail during the init code (I did not verify that it does bail out during init, but I suspect it might).
Perhaps by testing both without a header and with a prepended header that just specifies the most common mode of using deflate with no preset dictionary.
Btw, maybe the bugfixes should go in a separate PR, so we don't clutter up this PR with comments regarding those.

Now that the oss-fuzzers are free of bugs and that the patches have stabilized, I think it is time to think about merging the patch series.
@Dead2 : could you please let me know how you would like to proceed?
I can rework the patches following your guidelines and create separate pull requests for each fixed bug.

@sebpop Separate pull requests for each fixed bug is great, just like I see you have started doing. 👍
Also a separate PR for the oss-fuzz support would be great.
I am a bit unsure about the attribution requirements from oss-fuzz though, didn't they require some text in the commit message?
@mtl1979 Please +1 the PRs you approve of if you can, I value your feedback.
Any others doing the same would be great. The more eyes reviewing zlib-ng changes, the better both for me and for the projects potential inclusion in distros.  :)
@sebpop Great work on this! If you ever visit (east) Norway, I'll buy you a beer or something :)

@Dead2 Already started going through the ones that seem ready for merging... Some of the changes did seem still work-in-progress so I'm waiting for @sebpop to finish them.
I'm currently quite busy with work so I can't go through the modifications every day, but I try to go through them when I have spare time.

@mtl1979 Great, I am not rushing anything here. But knowing you intend to review, I'll hold off on merging until I hear your feedback on them. Oh, and that beer offer goes for you too :)

@Dead2 Everybody knows I don't drink beer...

@mtl1979 Me neither ;)

@Dead2 I did empty my last bottle of alcohol about 1 year after I stopped working for local recycling center... After that I have not even tasted alcohol.

Also a separate PR for the oss-fuzz support would be great.

I just opened bug #204.

I am a bit unsure about the attribution requirements from oss-fuzz though, didn't they require some text in the commit message?

For the bugs with an oss-fuzz ticket, I added that reference in the subject of the patch fixing it.
If you want I can also add the reference in the commit message.

the projects potential inclusion in distros

I'd like to get zlib-ng in chromium.org and Android.  oss-fuzzer is going to help stabilize the code, and the big performance difference between zlib-ng and zlib.org already provides the incentive to make the switch.

If you ever visit (east) Norway, I'll buy you a beer or something :)

I like to keep my brain clear to work on code, I haven't got a beer from the time I was in Liverpool.
Hot chocolate or a tea would work ;-)

I am closing this old pull request.  The squashed patch to add the fuzzers in a single patch is #206.


Add optional use of exposure maps to temperature_from_filter_ratio

Added the ability to use exposure maps (i.e. images in which each pixel contains the exposure time for the image data for the corresponding pixel) in the routine temperature_from_filter_ratio. This allows the use of composite images in which different pixels have different exposure times, generally used to combine long-short or long-medium-short image combinations in order to increase the dynamic range of images. Also the routine make_exposure_map was added to create the exposure maps for a given composite image. A routine filename2repo_path was added to the util directory to facilitate downloading the files necessary to create the exposure maps. And a notebook was created illustrating the use of these routines.

Hi @jslavin Jon,
I've merged #209 "Adding to @Jslavin PR 207 - Add optional use of exposure maps to temperature_from_filter_ratio," which is an extension of the work you initiated in this PR. Therefore, we can close this branch.


DEP: deprecate positional arguments for special.comb

Towards #18703
This is a bit more of a discussion point, because then the question of consistency with other functions in that module arises. We don't strictly have to switch this to positional, but https://docs.scipy.org/doc/scipy/dev/missing-bits.html#required-keyword-names does state that changing the signature should switch to positional. Personally I'm in favour, but I don't feel very strongly about it.

I double-checked that invhilbert is the only instance in the code-base where exact is treated as a positional argument.

Thanks! The test suite should also fail on unexpected deprecation warnings (which is how I found that one occurrence).


Add Josh Ackerman to contributors list

Hi  @jackerman69, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added social share  to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.

Hi @Roshanjossey it was a good tutorial, this was my first commit to any open source but the first of many. I would like to contribute to more open sources to help develop my coding skills. I didn't have to many problems and the tutorial was very straight forward and well done. I do wish it went into a little more detail about what the commands you were using in Git meant as well as how to use git overall. Maybe that should be a separate tutorial, the basics of Git.
Thanks!

@jackerman69, I’d urge you to continue contributing to other open source projects.
We also have a slack team to help/mentor people trying to contribute to open source projects.
You can join the team by going to https://firstcontributions.herokuapp.com


[kroki-fetch-diagram] Configurable fetch dir

When  kroki-fetch-diagram is enabled, the diagram is fetched in the current dir.
I'd like to be able to select the target directory, for example images/kroki, containing downloaded diag-<hash>.svg  files.
In short, I'd like to have kroki-fetch-dir or kroki-images-dir which would be the default target folder and would override the default imagesdir when set.

You can use imagesoutdir but the path used in the HTML is controlled by imagesdir. The imagesoutdir attribute tells Asciidoctor Kroki where to write the file. The imagesdir attribute tells the processor what to put in the HTML.
Is that what you are looking for?
I'm adding the label documentation since this is an undocumented feature 😅

Thanks for pointing out the imagesoutdir attribute.
Given a document containing both handmade images and Kroki generated images. I'd like to be able to place images in different folders (the Kroki output directory can be Git ignored, can be pruned, can be a subfolder of the main imagesdir).
When I set imagesoutdir=kroki  and imagesdir=main, images are fetched in the kroki directory (good start), but the HTML references them in the main directory, so they are 404 not found.

As far as I know it's not supported by Asciidoctor. If you want to use this configuration then I think you will need to manually copy images to the imagesdir directory.
You should ask on https://asciidoctor.zulipchat.com/ maybe someone will have a better idea...
(sorry for the laaaaate reply!)


Added the feature of enabling a cloud trail bucket policy

what
Added functionality to enable adding a cloud trail bucket policy with a simple boolean variable
why
While there is a separate project to for cloud trail buckets, that project does not use the latest aws provider.
references
https://registry.terraform.io/modules/cloudposse/cloudtrail-s3-bucket/aws/latest

Note that you could do this with a policy too, but its nice if its baked in, and I think the use case happens frequently enough.  A policy in the examples such as this one for a log-delivery policy.
  policy = jsonencode({
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Principal": {
                "Service": "delivery.logs.amazonaws.com"
            },
            "Action": "s3:PutObject",
            "Resource": [
                "arn:aws:s3:::logs-bucket-${get_aws_account_id()}/S3_Access_logs/AWSLogs/${get_aws_account_id()}/*",
                "arn:aws:s3:::logs-bucket-${get_aws_account_id()}/elb-access-logs/*"
            ],
            "Condition": {
                "StringEquals": {
                    "s3:x-amz-acl": "bucket-owner-full-control"
                }
            }
        },
        {
            "Effect": "Allow",
            "Principal": {
                "Service": "delivery.logs.amazonaws.com"
            },
            "Action": "s3:GetBucketAcl",
            "Resource": "arn:aws:s3:::logs-bucket-${get_aws_account_id()}"
        }
    ]
  })

/test all

As useful as this is, I'm wondering if a cloudtrail specific policy is too specific for this module. All the other toggles are generic enough to work for many use-cases and this particularly policy is only for cloudtrail which is one of the reasons why we have a separate module for this cloudposse/cloudtrail-s3-bucket/aws.
cc: @andriy @Nuru @Gowiem  what do you think ?

As useful as this is, I'm wondering if a cloudtrail specific policy is too specific for this module. All the other toggles are generic enough to work for many use-cases and this particularly policy is only for cloudtrail which is one of the reasons why we have a separate module for this cloudposse/cloudtrail-s3-bucket/aws.

I am closing this as wontfix for just this reason. This s3-bucket module is complicated enough, we do not want to add extra complications. Our use model is that for common use cases of s3-bucket, we create a separate module, such as cloudposse/cloudtrail-s3-bucket/aws or terraform-aws-s3-log-storage.
The appropriate PR would be one on terraform-aws-cloudtrail-s3-bucket bringing it up-to-date so that it uses this module as its basis.


Robust FeatureDataSource.

(work in progress, don't review yet)
FeatureDataSource now works just with parameters passed from
constructor.
Highlights:

supports all normal OmvDataSource parameters, like styleSetName
support GeoJsonDataProvider options to enable cusotmization of
tiler
supports geoJson&features option to set features/GeoJson content
right at construction time

Update examples to use new API.

@heremaps-bot retest this please

Codecov Report

Merging #830 into master will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master    #830      +/-   ##
=========================================
+ Coverage   48.19%   48.2%   +0.01%
=========================================
  Files         242     242
  Lines       21943   21943
  Branches     4987    4987
=========================================
+ Hits        10575   10578       +3
+ Misses      11368   11365       -3

Impacted Files
Coverage Δ

@here/harp-test-utils/lib/TestUtils.ts
81.17% <0%> (+3.52%)
: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 daf0c05...6d6f8aa. Read the comment docs.


Fix link to the repo for the Travis CI batch

Travis CI batch was pointing to the previous repo URL .../xecmascript...

What about to the link to gitter? Is it working?

@rchavarria The gitter link is working but points to xecmascript channel. The ruby guys say gitter doesn't handle renames properly hence they chose to create a new channel ruby. Should we do the same and then change the link in readme? Maybe name it ecmascripts like our team.

Yep, ecmascripts sounds good to me :+1:
2017-06-23 8:29 GMT+02:00 Tejas Bubane<EMAIL_ADDRESS>
@rchavarria https://github.com/rchavarria The gitter link is working
but points to xecmascript channel. The ruby guys say gitter doesn't
handle renames properly hence they chose to create a new channel ruby.
Should we do the same and then change the link in readme? Maybe name it
ecmascripts like our team.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/exercism/ecmascript/pull/310#issuecomment-310583604,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAlZUJK9B8wWX5W9AKRFuAIphlxMQc21ks5sG1tdgaJpZM4ODKF4
.

--
Rubén Chavarría
blog http://rchavarria.github.io    linkedin
http://es.linkedin.com/in/rchavarriat
http://www.deliriumboutique.com/

Nobody @exercism/ecmascripts wants to merge this? Just a thumb up or down and I'll do it.

@rchavarria I almost did but thought we were waiting on the gitter change.

Thanks @rchavarria !


Not getting all the prompts as per docs

I am following https://docs.microsoft.com/en-us/learn/modules/publish-app-service-static-web-app-api/4-exercise-static-web-apps?pivots=vue and also looking at the docs at https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azurestaticwebapps
In those examples they appear to have 6 steps. When I run this, I only get 3 and the option to select the application folder and build output folder is not available. This breaks the lab.. I figured out that I could go change the github action and that would work.
is this by design. If so the docs needs to be changed..
FYI- @johnpapa

ok, figured out then when the prompt appears with list of frameworks, you can click custom - and then you get the other options.

ok, figured out then when the prompt appears with list of frameworks, you can click custom - and then you get the other options.

On our end, we can update the README and include the all the steps in the GitHub Wiki.

On our end, we can update the README and include the all the steps in the GitHub Wiki.

This issue has become stale and is at risk of being closed. The community has 60 days to upvote the issue. If it receives 5 upvotes we will keep it open and take another look. If not, we will close it. To learn more about how we handle issues, please see our documentation.
Happy Coding!

GitHub wiki was updated here: https://github.com/microsoft/vscode-azurestaticwebapps/wiki/Creating-a-Static-Web-App


The eigenvector of Hessian

Hi Dong,
Where is the Hessian operation in your program？

https://github.com/amirgholami/PyHessian
你看一下这个链接，希望能够帮到你！

i didnt find any hessian related code either....

Didn't see any hessian. Only hypothesis is that bit_config.py was somehow generated using hessian values? But not even sure.


feat(CORS): improve cors middleware

Fixes: #2325
This is a follow up of #2304

should be ready for review


Log crm updates

These are some debugging changes I've made locally that help me work out what's happening when the modules isn't applying change correctly. They only affect debug logging, so shouldn't cause problems for anyone. I'm submitting a pull request in case they're more generally useful, but I wouldn't be offended if it was rejected.

Why did you remove two debug() calls? I'm happy about the new ones and would merge them.

I moved them inside the ready method where they have access to the output from the exec to log it.

(fixed the checks too)

PCCI blames Centos but this was broken before, looks good.


Pre-compiled OSX-64bit download link is down

Error says 'Internal Error'.

Try refreshing the page.  There is some minor error on the web site.
On Mon, Feb 23, 2015 at 9:28 AM, westhechiang<EMAIL_ADDRESS>wrote:

Error says 'Internal Error'.
—
Reply to this email directly or view it on GitHub
https://github.com/heroku/force/issues/141.

--
Thanks,
Dave

Nice, thanks for the quick response.

On Feb 23, 2015, at 9:52 AM, Dave Carroll<EMAIL_ADDRESS>wrote:
Try refreshing the page. There is some minor error on the web site.
On Mon, Feb 23, 2015 at 9:28 AM, westhechiang<EMAIL_ADDRESS>wrote:

Error says 'Internal Error'.
—
Reply to this email directly or view it on GitHub
https://github.com/heroku/force/issues/141.

--
Thanks,
Dave
—
Reply to this email directly or view it on GitHub https://github.com/heroku/force/issues/141#issuecomment-75594171.


Implementing support for multiple PDBs

Hi,
I would like to extend the assembly example to allow for assemblies across different PDB IDs (essentially, have a select box with a custom list of PDBs for filtering). From what I can tell the software seems to support such cases (perhaps using EntryAssembliesCollector?), but since I am only superficially familiar with TypeScript I don't know how I would go about implementing this.
Perhaps I have to use the RcsbFv3DCustom class for this, instead? I'd appreciate a few pointers in terms of what direction to take.

I can see that src/RcsbFvWeb/RcsbFvBuilder/RcsbFvInstanceBuilder.ts exports further functionality. As an example, if instead of calling buildInstanceSequenceFv, I call the function buildMultipleInstanceSequenceFv here: https://github.com/rcsb/rcsb-saguaro-3d/blob/e39aaeac2bd751cbe9457c43942f128f331ee785/src/RcsbFvSequence/SequenceViews/AssemblyView/AssemblyView.tsx#L178
and make the relevant adaptations, I do get a select box with the PDB ID, but unfortunately, the interactivity of the sequence viewer is completely broken. Which makes sense, I think, but I cannot figure out how to fix it.

Hi! you are going in the right direction. The first problem was in buildMultipleInstanceSequenceFv that was ignoring the additional config parameter and it carries the board configuration and thus, the interactivity between viewers. I have fixed that in @rcsb/rcsb-saguaro-app. Could you update to version 1.0.1 and try again ? If you are interested in integrating this feature in master you can open a pull request and I will be very happy to help.

This is great! Thank you for your help and for so quickly providing a fix! I managed to create the PDB select box using version 1.0.1 and the sequence viewer interactivity works. Now, the next steps are:

What is the best way to populate the select box?
I tried modifying sequenceConfig which expects a string for its entryId value to allow for Array<string> but, unfortunately, could not get it to work. If I understand it correctly, the issue has to do with sequenceConfig having AssemblyViewInterface interface.  Replacing it with CustomViewInterface may work, but that seems to require a lot of work. As a test/hack, I provided ["4hhb", "2rh1"] directly as input to buildMultipleInstanceSequenceFv and that does work in terms of populating the select box, but breaks the interactivity of the app.

Update the structure viewer (Mol*) based on the selected PDB.
I can load two or more structures at the same time (using the MolStar Plugins LoadMethod.loadPdbIds and Array<LoadParams>), but that again breaks the interactivity of the app. It would also be much better for the structures to load upon selection, and not all of them upon DOM load. Weirdly, even though the sequence viewer updates successfully and correctly, the this keyword inside e.g. AssemblyView's pluginSelectCallback function still contains wrong references.

Hopefully fixing point 1 above will also go a long way to address the second point as well.

The "custom" path would require to build everything from scratch. I have created this branch
https://github.com/rcsb/rcsb-saguaro-3d/tree/dev-js-mutiple-entries
I haven't test all functionalities but interactivity seems to be working. However, use this branch very careful because its only a quick-and-dirty fix. Try the example in src/examples/assembly/index.ts and let me know if it works for you.

If no further help is needed I will close this issue.

@bioinsilico Thank you so much for your help with this. I have been busy working on different projects but I plan to get back to this very soon. The new branch you have created is really helpful. I've tested it and it fixes the issues I've noted above.
For me, the next step now is to fix/implement loading and removing structures from the Mol* scene based on select box choices made.
I believe this would be a nice extension to the capabilities of this repo as well and I would be happy to hopefully help in the future with this. But for now, I think you can close this issue.
Thanks so much for your help! :)


Please remove links to sourceforge and kbranigans repo from the readme

The version on sourceforge is outdated and contains several security flaws. Kbranigans fork is currently up to date, but only because I made a pull request that brings it up to date (so that people are not downloading old versions with security flaws from his repo).
So please remove those two links from the readme.

ok i will.

removed


Backport: Using cloud config in Azure with a Service Principal that has multiple subscriptions fails to operate

Backport https://github.com/rancher/rancher/issues/20632

Reproduction:
Version: v2.2.4
We were able to see that when we supply azure cloud information the subscription id is essentially ignored.

Create an RKE Azure nodeTemplate with correct credentials (Subscription ID, Client/app ID, secret); just make it a simple cluster, say 1 node with all 3 roles
Fill out Azure cloud fields, but put in a fake subscription ID
SSH into cluster node. Review kubelet logs and kube-controller-manager logs. grep for our fake subscription ID that we entered
The fake subscription id is not found, instead we find another subscription id that we did not specify.

We expected provisioning the cluster to fail since we provided a false/fake subscription id in the azure cloud subscriptionid field. Instead, the cluster worked and came up for us (because in this case it used a subscriptionid that was set up and able to create the azure resources). In our case we had difficulty setting up a subscriptionid such that it would fail to provision -- but the point is that we have effectively reproduced because we saw when we inspect kubelet and kube-controller-manager logs that our fake subscription id was not used.
Here is an example:
docker-user@david-224invalid1:~$ cat kube-cntrl-mgr_logs | grep "8070bfdf-3a92-47fe-bec5-2f3ae43d2bf6"
+ local az_subscription_id=8070bfdf-3a92-47fe-bec5-2f3ae43d2bf6
+ '[' -z 8070bfdf-3a92-47fe-bec5-2f3ae43d2bf6 ']'
+ jq '.subscriptionId="8070bfdf-3a92-47fe-bec5-2f3ae43d2bf6"'
docker-user@david-224invalid1:~$ cat kube-cntrl-mgr_logs | grep "7070bfdf-3a92-47fe-bec5-2f3ae43d2bf6"

First command greps for incorrect subscription id (we did not supply this) Second command greps for what we actually entered in the UI when we plugged in subscriptionid for azure cloud field.

This change causes failures bringing up a cluster even with correct cloud info provided (all four required fields).
Something's not quite right with the original PR I think. https://github.com/rancher/rke-tools/pull/38
[workerPlane] Failed to bring up Worker Plane: [Failed to verify healthcheck: Failed to check https://localhost:10250/healthz for service [kubelet] on host [<IP_ADDRESS>]: Get https://localhost:10250/healthz: dial tcp <IP_ADDRESS>:10250: connect: connection refused, log: ++ cut -d / -f 9]; waiting on cluster-scoped-gc

I confirmed in v2.2.4 I can bring up azure RKE cluster with azure cloud without any issues (and thus our config supplied is good)

Is there a link to PR @alena1108 I don't see any new commits to fix the issue.

@davidnuzik this is the original PR which is in rke-tools, https://github.com/rancher/rke-tools/pull/53
And new rke-tools got added in these backport PR,
https://github.com/rancher/rancher/pull/21180

Version: v2.2-head (6/27/19)
The PR fixed our previous issue. We can now bring up an azure cluster with azure cloud option without any issues (when proper credentials are supplied).
I also checked with my own test app in separate subscription. As long as correct credentials are supplied the cluster now comes up (this was broken with previous PR and preventing creating any azure nodes with cloud option before).
Also ensured we can leverage Azure cloud features like Azure disk storage class and bind a volume.

Reproduction:
Refer to previous comment https://github.com/rancher/rancher/issues/21124#issuecomment-506026017
Validation:
Version: v2.2-head (6/27/19) Ver from logs: 5521557f

Create an RKE Azure nodeTemplate with correct credentials (Subscription ID, Client/app ID, secret); just make it a simple cluster, say 1 node with all 3 roles
Fill out Azure cloud fields, but put in a fake subscription ID
SSH into cluster node. Review kube-controller-manager logs. grep for our fake subscription ID that we entered
The fake subscription id IS NOW found (it was not before).

First is correct subscription id (we did not supply this)
Second is our fake subscription id (which we supplied)
docker-user@david-testappbad1:~$ cat kubelogs.txt | grep 8070bfdf-3a92-47fe-bec5-2f3ae43d2bf6
docker-user@david-testappbad1:~$ cat kubelogs.txt | grep 7070bfdf-3a92-47fe-bec5-2f3ae43d2bf6
+ local az_subscription_id=7070bfdf-3a92-47fe-bec5-2f3ae43d2bf6
+ '[' -z 7070bfdf-3a92-47fe-bec5-2f3ae43d2bf6 ']'
+ jq '.subscriptionId="7070bfdf-3a92-47fe-bec5-2f3ae43d2bf6"'

Previous behavior was that logs showed the subscription id that we did NOT supply in our cloud config.
Confirmed that since I supplied bad subscriptionID I cannot make use of cloud features like provision storage with azure disk. The volume cannot be bound because we get an error stating credentials issue like:

I also made sure that when we DO supply correct credentials we can make sure of such features (I can make an azure disk storage class and provision a volume).
Note as node provisioned saw we are indeed pulling latest rke-tools (build 34).

Version: v2.2-head (6/27/19)
The PR fixed our previous issue. We can now bring up an azure cluster with azure cloud option without any issues (when proper credentials are supplied).
I also checked with my own test app in separate subscription. As long as correct credentials are supplied the cluster now comes up (this was broken with previous PR and preventing creating any azure nodes with cloud option before).
Also ensured we can leverage Azure cloud features like Azure disk storage class and bind a volume.

Reproduction:
Refer to previous comment https://github.com/rancher/rancher/issues/21124#issuecomment-506026017
Validation:
Version: v2.2-head (6/27/19) Ver from logs: 5521557f

Create an RKE Azure nodeTemplate with correct credentials (Subscription ID, Client/app ID, secret); just make it a simple cluster, say 1 node with all 3 roles
Fill out Azure cloud fields, but put in a fake subscription ID
SSH into cluster node. Review kube-controller-manager logs. grep for our fake subscription ID that we entered
The fake subscription id IS NOW found (it was not before).

First is correct subscription id (we did not supply this)
Second is our fake subscription id (which we supplied)
docker-user@david-testappbad1:~$ cat kubelogs.txt | grep 8redacted
docker-user@david-testappbad1:~$ cat kubelogs.txt | grep 7redacted
+ local az_subscription_id=7redacted
+ '[' -z 7redacted ']'
+ jq '.subscriptionId="7redacted"'

Previous behavior was that logs showed the subscription id that we did NOT supply in our cloud config.
Confirmed that since I supplied bad subscriptionID I cannot make use of cloud features like provision storage with azure disk. The volume cannot be bound because we get an error stating credentials issue like:

I also made sure that when we DO supply correct credentials we can make sure of such features (I can make an azure disk storage class and provision a volume).
Note as node provisioned saw we are indeed pulling latest rke-tools (build 34).


sun.awt.image.BufImgSurfaceData cannot be cast to sun.java2d.xr.XRSurfaceData

What TMM version are you using?
tmm.version      : 2.9.7
java.version     : 1.8.0_161
default encoding : UTF-8 | UTF8 | UTF-8
set encoding to  : UTF-8 | UTF8 | UTF-8
System language  : en_US
GUI language     : en_US
Using MediaInfoLib - v0.7.98
OS: Ubuntu 17.10
release, pre-release, nightly, or directly from GitHub/branch?
Package: tmm_2.9.7_8513bee_linux.tar.gz from the website http://www.tinymediamanager.org
What is the actual behavior?
TMM is open and the computer goes into power saving mode (only the screen are powered off).
When I wake up the OS and enter the password, I see a popup with the following exception and every time I close the popup, it reappears; so I kill the process manually. Based on the log, the exception appears just after the wakeup.
2018-02-06 07:04:19,253 ERROR [main] org.tinymediamanager.Log4jBackstop:37 - Uncaught exception in thread: main
java.lang.ClassCastException: sun.awt.image.BufImgSurfaceData cannot be cast to sun.java2d.xr.XRSurfaceData
        at sun.java2d.xr.XRPMBlitLoops.cacheToTmpSurface(XRPMBlitLoops.java:148)
        at sun.java2d.xr.XrSwToPMBlit.Blit(XRPMBlitLoops.java:356)
        at sun.java2d.pipe.DrawImage.blitSurfaceData(DrawImage.java:959)
        at sun.java2d.pipe.DrawImage.renderImageCopy(DrawImage.java:577)
        at sun.java2d.pipe.DrawImage.copyImage(DrawImage.java:67)
        at sun.java2d.pipe.DrawImage.copyImage(DrawImage.java:1014)
        at sun.java2d.pipe.ValidatePipe.copyImage(ValidatePipe.java:186)
        at sun.java2d.SunGraphics2D.drawImage(SunGraphics2D.java:3318)
        at sun.java2d.SunGraphics2D.drawImage(SunGraphics2D.java:3296)
        at javax.swing.RepaintManager$PaintManager.paintDoubleBuffered(RepaintManager.java:1589)
        at javax.swing.RepaintManager$PaintManager.paint(RepaintManager.java:1502)
        at javax.swing.BufferStrategyPaintManager.paint(BufferStrategyPaintManager.java:306)
        at javax.swing.RepaintManager.paint(RepaintManager.java:1272)
        at javax.swing.JComponent.paint(JComponent.java:1042)
        at java.awt.GraphicsCallback$PaintCallback.run(GraphicsCallback.java:39)
        at sun.awt.SunGraphicsCallback.runOneComponent(SunGraphicsCallback.java:79)
        at sun.awt.SunGraphicsCallback.runComponents(SunGraphicsCallback.java:116)
        at java.awt.Container.paint(Container.java:1976)
        at java.awt.Window.paint(Window.java:3906)
        at javax.swing.RepaintManager$4.run(RepaintManager.java:842)
        at javax.swing.RepaintManager$4.run(RepaintManager.java:814)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80)
        at javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:814)
        at javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:789)
        at javax.swing.RepaintManager.prePaintDirtyRegions(RepaintManager.java:738)
        at javax.swing.RepaintManager.access$1200(RepaintManager.java:64)
        at javax.swing.RepaintManager$ProcessingRunnable.run(RepaintManager.java:1732)
        at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
        at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
        at java.awt.EventQueue.access$500(EventQueue.java:97)
        at java.awt.EventQueue$3.run(EventQueue.java:709)
        at java.awt.EventQueue$3.run(EventQueue.java:703)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80)
        at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)
        at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
        at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
        at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)

What is the expected behaviour?
The exception should not appear or only 1 time.
Steps to reproduce:

Start TMM.
Wait for the power saving mode to activate
Wake up and enter password
The popup appears.

Additional
Have you attached the Logfile from the day it happened? Yes
tmm.log
Your Operating system? Ubuntu 17.10

puh, seems to be a Java bug https://bugs.openjdk.java.net/browse/JDK-8147542
Might already be fixed in Java 9, and Java 8 update 172 (upcoming? next?)
Anyhow, we cannot do anything about it :(

the new java version is out - could you try that again?


Socket.select and null params

For the cpp target Socket.select maps to _hx_std_socket_select in Socket.cpp.  This function expects non-null parameters however tink_tcp passes nulls in two calls to Socket.select in Connection.hx.

Yeah, this is generally a little horrible right now. There should be an actual selection in place. Would passing [] solve your particular issue?

Passing empty arrays solves my issue.  Otherwise I get a Null Object Reference exception.
I would have thought nulls should work too, but not a big deal.  The weird effect was the socket still worked as long as I slept a little between stepping the RunLoop.  Maybe the GC got a chance to run and somehow that hid the error.


Use deferred files when opening files

If the files were opened in the submission task, it would cause too many file handles to be opened. Now this gets opened in the IOExecutor which has a limit of 1000 tasks and should not be an issue because most OS's have a max of 1024 open file handles.
cc @jamesls @JordonPhillips

To make sure  I understand the issue, even though the request executor also has a 1000 cap on its queue size, the file is still opened when the task is done executing because it's sent off to the io executor.  As a result, it's possible to exceed more than 1024 open files right?
Otherwise change looks good to me.

Yeah that is pretty much sums it up. Before, we had a bunch of open files that were not being worked on in the request executor's queue because they got opened in a submission executor and since the io executor has a queue itself there were some open file handles there too, causing us to easily spill over 1024 because both of those queues were of size 1000.
Ideally we only want to be opening the file if it is about to be worked on, not if we are preparing to work on it. The one downside I see with this is that before we would fast fail in the submission task if say we did not have permissions to the file as we opened the file there but now we will fail at the first attempt of a write to the file.

@jamesls I updated based on feedback. Should be good to look at again.

@jamesls I updated. Should be good to look at again.


Need help with CRUD and Routes

I apologize if my question is such a basic question but unfortunately I was not able to find an answer to my question here.
I have successfully run the app and connected it to my Firebase account.
Now i need to create a new data model let's say named "todoitem" and generate a new page and be able to do CRUD in that page for the todoitem.
In other words:

if I GET at /todoitem I should be able to get all the todoitem that the user is an author of
if I POST to /todoitem/new I will be adding a new todoitem
if IPUT by ID at /todoitem/:id/edit
if I DELETE at /todoitem/:id . I should be able to delete that todoitem

I basically need some guidance in two areas:

How can I create a new page and add routes (/todoitem) to that page
How to go about adding a new data model and doing a restful CRUD?

Any help, pointers etc would be much appreciated,
Thanks

Hello @amirm-eng and welcome to GitHub!
The answer to your first question can be divided into some steps (assume the page is called "Room"):

Create a RoomContent folder along with RoomContent.js, RoomContent.test.js, and index.js.
Initialize a new React component in RoomContent.js.
Add a basic smoke test for RoomContent.test.js, you can find pretty much any component and copy-paste their test and modifying it for RoomContent.
Add export { default } from "./RoomContent"; in index.js. This is used to more easily reference the component from other components.
Add <Route path="/room/:roomId"><RoomContent /></Route>, for example,  in Router.js under the already defined routes.
Navigate to http://localhost:3000/room/test and you’ll be on your new page.

The setup of a back-end RESTful API compatible with RMUIF might be cumbersome, I have not tried it yet, quite frankly not with a lot of React projects. I would suggest consulting https://create-react-app.dev/docs/integrating-with-an-api-backend for more information on how to do so. RMUIF is based on CRA, so the principle is the same, I would imagine. Other than that, you would do your API calls in componentDidMount on your pages using fetch() or axios.
Some additional resources:
https://create-react-app.dev/docs/documentation-intro
https://reacttraining.com/react-router/web/guides/quick-start
https://expressjs.com/
https://www.freecodecamp.org/news/create-a-react-frontend-a-node-express-backend-and-connect-them-together-c5798926047c/
Thank you for using RMUIF and have a pleasant evening.

Thank you so much for your help @phoqe
I really appreciate your step by step and clear explanations, it helped me alot.
Q 1) So I was able to follow your instructions regarding my first question and it worked for me. Thank you.
Q 2) In regards to the second question, I meant to say how can I do CRUD with the recommended way that this project talks to the Firebase Firestore?
In other words, for instance let's say we have created a brand new page using your instructions in step 1 and this page is now is located at /room/:roomId
Now let's say we have created a data object called roomdata in Firestore.
A roomdata object in Firestore would look like this:
roomdata: {
name: 'some room name',
category: 'social',
capacity: 200
}
To get all the roomdata objects for the currently logged in user, what's the best way that I can import the same instance of the firestore that is used in App.js into RoomContent.js and have access to the user Id of the user that is logged in and consequently be able to do queries like:
firestore.collection("roomdata").get().then(function(querySnapshot) {...}
It would be great if you could help me see some basic implementation that I should have in the RoomContent.js that will allow me to fetch all roomdata and user objects.
Thank you :)

You can accomplish this by using the useParams() hook from React Router in conjunction with Firebase Cloud Firestore.
It would look something like this:
import React, { useState, useEffect } from "react";
import { useParams } from "react-router-dom";

import { firestore } from "../../firebase";

function RoomContent() {
  const [room, setRoom] = useState(null);
  const { roomId } = useParams();

  useEffect(() => {
    firestore.collection("rooms").doc(roomId).get().then((value) => {
      setRoom(value.data());
    }).catch((reason) => {
      console.error(reason);
    });
  });

  if (!room) {
    return null;
  }

  return (
    <div>
      {room.name}
    </div>
  );
}

export default RoomContent;

Also, regarding extending Webpack, you need to eject CRA by using npm run eject or yarn eject, read this before doing it because it’s a one-way operation.

I think I will take your request one step further and begin working on the user pages, I just need to solve for the user data consistency first, meaning I can guarantee that users have some form of info available before showing a profile. I will do a route at /user/:userId which will require the user to be authenticated. And since this is the first user-to-user interaction, I will implement some administrative actions for the user as well (for users that are administrators of course) and begin thinking of how to do relationships with users etc.

Thank you for the sample code, I'm yet to try that. I'll report here once I try it.
About ejecting the CRA to be able to extend Webpack, to be honest I feel uncomfortable to eject CRA as by doing so my project becomes out of sync with rmuif. I may have to look for alternative approaches to load an external html template into my react component. I'll look into it. Thanks.

Thanks, thats pretty helpful, i think you should add a crud example to de documentation, I now we can figure it out learning deeper firebase, react and redux, but is really nice to understand it from your point of view.

In regards to building on top of this request, I think that's a great idea and the whole community can benefit from it.
User Profile:
Having a dedicated profile page for the user is a necessity for almost any SaaS app.
CRUD
Additionally a sample CRUD page which can easily be extended would be a great starting point for anyone to custom build their own model for the crud operations.
I would suggest we name the data model an "article":
All of the following would work based on user permissions and user role:
POST /article/new
GET all articles  /article/
GET single article. /article/:id
PUT update an article. /article/:id
DELETE remove an article. /article/:id
What are your thoughts @phoqe
Thank you

Yes, I agree with your proposal. I will start with the profiles after I’ve fixed the issue with user data consistency and then move on to the actual content.
Thank you for your feedback!

This is great news.
Looking forward to it..
Please let me know if I can help with any brainstorming or really anything at all,
Best,

By the way, @amirm-eng, do not use that code snippet for content fetching, you should use something similar to:
  useEffect(() => {
    return firestore
      .collection("users")
      .doc(userId)
      .onSnapshot(
        snapshot => {
          setUser(snapshot.data());
          setLoading(false);
        },
        error => {
          setError(error);
        }
      );
  }, [userId]);

Really important to include the [userId] part in the end, else it will just continue to register listeners all the time.

Here's a more complete example, including error handling:
import React, { useState, useEffect } from "react";

import { useParams } from "react-router-dom";

import { firestore } from "../../firebase";

import ErrorIcon from "@material-ui/icons/Error";
import PersonOutlineIcon from "@material-ui/icons/PersonOutline";

import EmptyState from "../EmptyState";

function UserContent() {
  const [loading, setLoading] = useState(true);
  const [user, setUser] = useState(null);
  const [error, setError] = useState(null);
  const { userId } = useParams();

  useEffect(() => {
    return firestore
      .collection("users")
      .doc(userId)
      .onSnapshot(
        snapshot => {
          setUser(snapshot.data());
          setLoading(false);
        },
        error => {
          setError(error);
        }
      );
  }, [userId]);

  if (error) {
    return (
      <EmptyState
        icon={<ErrorIcon />}
        title="Something went wrong"
        description="There was an error while trying to fetch the requested user"
      />
    );
  }

  if (loading) {
    return null;
  }

  if (!user) {
    return (
      <EmptyState
        icon={<PersonOutlineIcon />}
        title="User not found"
        description="The requested user was not found"
      />
    );
  }

  return <EmptyState title={user.username} />;
}

export default UserContent;

@amirm-eng @ortegoncarlos There’s now a user-content branched of develop, it’s only basic info at this point, but I will continue when time allows.

I was just about to get started with the code that you provided for UserContent that I saw your post that you already have the  user-content done.  Perfect 💯
So what are the user facing changes?

Yes, I am having some trouble with merging CI to GitHub Actions at the moment but that’s the plan. I am working on a v3.0 release and am merging documentation over to GitBooks, previewable at https://phoqe.gitbook.io/rmuif at the moment (will be docs.rmuif.com when done).

https://docs.rmuif.com/ is great and well organized.
Just one question though, should the docs mention anything about user role and perhaps the admin role as well?

I am currently adding more advanced sections as well.

@amirm-eng There’s now an initial draft on https://docs.rmuif.com/maintenance/roles

Tell me if there’s something missing and I’ll add it.

@phoqe
Looks great, it includes pages, roles and updates which are the main sections needed.
One thing that came to mind when reading the 'Set Role for User' section was how do I know that I can not  be hacked since anyone can intercept the running code in the browser to change a role of the logged in user.
Obviously this has been addressed by Firebase (I think by using privileged environments) but just thought it would be worth mentioning it in your documentation or simply by adding a link to where people can read about it.
https://docs.rmuif.com/maintenance/roles#set-role-for-user

@amirm-eng Thank you for your feedback, I have added some new explanations in those sections and hope they are adequate.

@phoqe I agree, it's great and covers all those areas. thnx

@amirm-eng You’re welcome. I will soon also have a main site up at https://rmuif.com and will move the demo to https://demo.rmuif.com, I will keep this issue open until I’ve added the article example to the main app and merged it to master.

@phoqe
That's great, thank you for letting me know, looking forward to the article example... . 💯 👍

Hi @phoqe
I noticed the new homepage for the project that you have built. It's looking very sleek and nice.
If I may suggest, the acronym "CRA" for Create React App is commonly used across the industry but I can imaging many people still not knowing that acronym.
It would be great to actually put that in bracket for them to know. ie. "CRA (Create React App)"
It would help with the SEO also, hopefully the project can be found by people much easier when they search in google.
I apologize if I am suggesting something that is irrelevant.

Thank you for your feedback @amirm-eng, yes, I agree with you and will probably rewrite some sections but am currently awaiting a response from the CRA team regarding usage with their logo etc.
Your advice is good, thank you :)

Hi @phoqe
I was thinking more about how the work for the "article" CRUD can become more generic so that anyone adopting this project would be able to leverage the crud operation capabilities in a boarder form as it is commonly seen in SaaS applications these days.
So then I came up with a list of about 7 important concepts that are used in SaaS and/or Social applications. But then later I thought to myself that this list should get even more shrunken down to 2 items that are super essential in many applications.
So this is the 2 items that I think are essential to many SaaS web apps.

Role based CRUD and views
Payment Subscriptions

1: The CRUD capability as we discussed previously would for instance consist of the following:
 - a no role (authenticated) user as well as premium or admin user would be able to view all articles posted by a premium role user. All articles can be viewed at (/article/)
- Note: For listing all articles anyone has posted, no pagination or lazy loading would be necessary initially as it just adds to the work. It can be added at a later time.

all articles that are posted by a specific premium user can be viewed at (/article/:userId)
when a user clicks on any of the articles title, that user is taken to a dedicated page for that article located at /article/:id where in which page all details of that article are shown
an article can be POSTed (/article/new) only and only by a user who has one of these roles ["premium", "admin"].
articles can be UPDATed or DELETEd by the same premium user or any admin user.

2: many applications have premium based offerings/services. Let's think of a premium service in our case to be the ability to post an article.
   - Users who are authenticated but still don't have a premium or admin role, can become a premium role user by subscribing to a subscription plan.

Let's call this subscription plan: "paidSubscriptionPlan"
To become a premium user the user would be taken to a page at (/upgrade/) where the user will see a form that includes their personal and credit card info and the amount for the premium subscription ie. $1 / month
Note: this can be a Stripe integration. Stripe has a Firebase integration:
     https://firebase.google.com/docs/use-cases/payments
     https://github.com/firebase/functions-samples/tree/master/stripe
Upon completion a callback would be called on Firebase side to update user role to premium.

Note: No need to have an administration page for cancellation or subscription etc. People can extend those additional functionalities on their own or they can be added in the future.

Sorry if I talked alot, these were my thoughts.
@phoqe can't wait to know what you think...?
Thanks,
Best,

I have actually considered your points before, especially payments through Stripe. It is a neat feature to have and makes the app more distinctive as there are not a lot of starter projects featuring a payment integration.
The first option is relatively easy to implement, the logic is essentially already implemented. I think I will have to postpone a Stripe integration until I’ve resolved some more issues and making the overall project more stable.
Thank you for your thoughts, it’s great to hear feedback on this level.

It's great to hear that you have considered both of the especially the payments through Stripe. The project will be very useful and likely attract alot of attention in the CRA and Firebase community.
Btw, in terms of the first option, in which branch will it be included, develop or it will have its own dedicated branch?
Thank you @phoqe

@amirm-eng It will be on its separate branch, branched off develop. Once it’s started I don’t think it’ll take a long time to complete though.

@phoqe cool, thanks

Great call on changing the title, our thoughts evolved alot through our discussions.
Btw out of curiosity, what are your plans in terms of the timeline you think you could work on this?
Thanks alot

Hello again, I have to complete #461 first, I will add this to the Roadmap, ETA is unknown at the moment.

Awesome, thanks for the update. Really hope that this could be included in
the current version / v3 Roadmap. This will give a good edge to the product.
Stability i great but people will be very pleased with features like CRUD
and Payment/Subscription.
Thanks, cheers
On Wed, Mar 4, 2020 at 10:39 PM Linus Långberg<EMAIL_ADDRESS>wrote:

Hello again, I have to complete #461
https://github.com/phoqe/rmuif/issues/461 first, I will add this to the
Roadmap https://docs.rmuif.com/docs/roadmap, ETA is unknown at the
moment.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/phoqe/rmuif/issues/420?email_source=notifications&email_token=AOPHFMVCEOKM6YOTQ7LDPNTRF5CIRA5CNFSM4KQSETHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEN35AKY#issuecomment-595054635,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOPHFMXMQRXJ5FMRJVBCAHTRF5CIRANCNFSM4KQSETHA
.

I recognize the need for this feature, I advice users of this template to study the user profiles at this time. And to clarify, the order of the items in the roadmap is not based on priority, it will be done in the order I see fit but am unable to sort them at the moment due to the more pressing issue, #461.

Understood, thank you for the clarification.


Minor issue in README

The README incorrectly states that troy-west.cronut/data-readers includes a reader function for tag ig/ref. Consider changing from edn/read-string to ig/read-string as the latter merges in ig/ref?
Just a small thing that caused me a little confusion.

Thanks for raising this @byrongibby, I've updated the README.


Forking Parity results in state_pruned error

Expected Behavior
When forking another network using --fork, it should be transparent if we're connected to the original chain or the fork
Current Behavior
When forking Parity 1.4.4, Parity complains about the state being pruned when doing eth_call:
This request is not supported because your node is running with state pruning. Run with --pruning=archive.
The same request when connecting directly to the Parity node succeeds.
Steps to Reproduce (for bugs)

Spin up Parity node
Send eth_call RPC call to Parity node
Fork Parity node with testrpc --fork $NODE_URL
Send eth_call RPC call to testrpc

Context
I'm setting up a dev environment for CI and want it to replicate my production environment.
Your Environment

Version used: 3.0.2
Environment name and version: Node.js 6.3.0, Parity 1.4.4

Hi @Schaeff,
Thanks for submitting the issue! I think this is probably a problem with Pairity. What happens when you run pairity with the --pruning=archive flag, as suggested in the error message?
Essentially, I think Pairity is dropping some of the data in the blockchain which it thinks is no longer relevant. Passing this flag should cause it to no longer do this.
Closing as I assume this will fix things for you. Please reopen if you feel this is still an issue.


Incorrect buffer value in compute example

Hi,
I was trying out some of the examples and it looks like the compute example only works for small vector sizes. To reproduce the issue simply replace the let data = [1u32, 2, 3 , etc.. ]; to let data = vec![1u32; 100000]; and assert that the sum should be 100000. In my case the value in the sum buffer is always the unmodified value 0.
Can anyone explain to me what is happening here?
Best,
Philippe

Having the number of elements being 16384 or bigger will cause the compute example to use a thread group size bigger than 1024:
let width = 16;

let thread_group_size = MTLSize {
    width: (NUM_ELEMENTS + width) / width,
    height: 1,
    depth: 1,
};

This is too big - see Maximum threads per threadgroup at https://developer.apple.com/metal/Metal-Feature-Set-Tables.pdf.
Running with MTL_DEBUG_LAYER=1 cargo run --example compute will indeed show the error:

-[MTLDebugComputeCommandEncoder _validateThreadsPerThreadgroup:]:1027: failed assertion `(threadsPerThreadgroup.width(1025) * threadsPerThreadgroup.height(1) * threadsPerThreadgroup.depth(1))(1025) must be <= 1024. (device threadgroup size limit)'

Awesome, thanks for the updated example as well!


Informs acknowledgement

Hi,
We have a distributed application running as containers. I need some help to set the source address for the acknowledgment packet going out of pysnmp.
So, this is our workflow:

The agent sends the informs to the application (running on server 1)

Application forwards the UDP packet to the informs processing app (running on server 2) --> It's for load balancing.

Server 2 receives and process the informs, sends the acknowledgment back to the Agent. This is done by the SNMP engine --> But the source IP is for the ack packet is set to the server 2 IP.

And our agent drops the acknowledgment bcos the informs were sent to the server 1.
Is there any way I can set the source address for the ack packet? Need some help.
Code:
from pysnmp.carrier.twisted.dgram import udp

self.snmp_engine = engine.SnmpEngine()
udp_transport.addressType().setLocalAddress(('<IP_ADDRESS>', 0))
        udp_transport.openServerMode(('::', self.informs_port))
        udp_transport.enablePktInfo()

        config.addTransport(
            self.snmp_engine,
            udp.domainName,
            udp_transport
        )

Note : I am using twisted udptransport.
Sa.

In my case, the source IP is reset to a different IP, with this doesn't it need to recalculate the checksums??

I am pretty sure pysnmp should not and in fact it does not mess with IP/UDP checksums. I believe this is done by the TCP/IP stack in the kernel (or even by the NICs now days). If checksum calculation is offloaded to the NIC, I can imagine tcpdump might not see the final checksum in the outgoing traffic.
It would be helpful if you paste some network related code - what you ended up with for the time being?

Did you manage to override source IP in responses? I think it's doable, but I am not sure that necessary API is exposed especially for Twisted.

@etingof  No. I am not able to. I have been looking at the code and realized that we need to have Python 3 to spoof the local address.
For ex:
https://github.com/etingof/pysnmp/blob/master/pysnmp/carrier/sockmsg.py#L104
This is what I am thinking for spoofing the address with twisted:  We make a custom twisted.internet.udp.Port implementation where self.socket.send and self.socket.sendto in write are replaced with calls to sendmsg similar to what pysnmp does. Then we will replace the twisted dispatcher with our custom implementation.


add ability to specify an ansi style

This adds the ability to specify an ansi style on the command line that will change the foreground, background, and attributes all at the same time.
Added this example to demonstrate.
Example {
    description: "Use ansi to color text with a style",
    example: r#"$"(ansi -e { fg: '#0000ff' bg: '#ff0000' attr: b })Hello Nu World(ansi reset)""#,
    result: Some(Value::test_string(
        "\u{1b}[1;48;2;255;0;0;38;2;0;0;255mHello Nu World\u{1b}[0m",
    )),
},

restarted several times to get ci to finish, twice it finished without ubuntu finishing, this time it finished without windows finishing. so I'm counting that as good.


More succinct documentation

Hi,
the documentation of the expected API is nice but at times a bit vague.
How about using a swagger.yaml for that?
I created this swagger.yaml if you would like to use it and start from there:
https://gist.github.com/fr-ser/b81b1ab70519e29a594daee7f59b6c18

Sounds like a good idea. However, I'd rather fancy XML or some other format that can be checked agaist schema or types.

Checked in what way?
We currently use this swagger.yaml to generate Postman Requests and test against that.
Also swagger is pretty much just an extension of JSONschema and we use the swagger also to verify requests and responses

Swagger sounds fine for me. But really, the base schema should be contributed to the upstream repository, i.e. the simplejson datasource.

Eg. when using standard XSD, the schema is checked whether it's valid, not outdated, not using redundant attributes etc.
So I'd rather use something more standardized than YAML for specifying swagger configuration. JSON is fine too but XML is the best out of these three.
@andig we don't have upstream repository anymore 🤔

Hmm. I think I might be out of my depth here :sweat_smile:
If you just want to convert the yaml to XML this should be no biggie. If you think the swagger documentation is useful feel free to incorporate it.
My main issue was just to have something more concrete than plain text. I didn't think about validating or anything like that for this repo (just a reference)

Yup, it's all about converting yaml into xml :) Willing to send PR?

Using XML simply eases maintainability on such config files. Eg. here it tells me I can drop the attribute backupGlobals from PHPUnit config that is default in new PHPUnit version even though it was not before but I don't have to study changelog to find out.

Also I can't do mistake by missing space as indentation in YAML is kind of fragile. Also this is worth checking out https://github.com/cblp/yaml-sucks :)

we don't have upstream repository anymore 🤔

Not technically but its still there (https://github.com/grafana/simple-json-datasource) and is responsible for largest part of the schema. Unless we plan to totally modify it (instead of adding smaller additions) a schema should at least be offered there.

Yup, we base on it's history, it's not overwritten and it's kept in git, but are not obliged not to change things anymore :). We already did some BC breaking modifications like renaming properties to proper english (timeseries). So I'm fine not to be bound to it anymore as guys from Grafana are more defensive to change than we are. I'd consider this plugin independent on it's original upstream.

Yup, it's all about converting yaml into xml :) Willing to send PR?

I think the main benefit of the yaml is that you can paste it into the editor.swagger.io and get some nice docs. I tried using online converters (yaml/json to xml) but the results look wonky to me.
Since I can't really assess the benefits of the XML I would prefer if somebody else does it

Changed my mind, any open api format would do, they're interchangeable anyway.


Sensor tags don't join thread network

Hi,
I set up an open thread border router according to your tutorial and started commissioning with the PSKd. Both of my sensor tags do not join the network. The firmware for the nordic usb stick linked in your post did not exist anymore so I used the current one and built it myself.

Only matters that firmware fits with open thread br software. I'd recommend to use both from recent versions.
I also recommend that you practice joining networks with cli before you try with custom firmware, it'll help you have a working reference to compare with, worst case, I'd recommend using a wireshark sniffer, it's hard, but helps you understand everything and find all problems.

And don't forget to fully delete the flash with factory reset, so that thread network config gets taken.

I have seen such an issue before most likely a factory reset will help (I have documented it somewhere, but currently I can not find it somehow) @wassfila do you have it somewhere?

@hansinator Which PSK did you used? I flashed the device with: ABCDE4

@wassfila I don't really get what you are talking about. I'm not using any custom firmware. I use the firmware from the openthread repository and followed this guide https://developer.nordicsemi.com/nRF_Connect_SDK/doc/v1.7-branch/matter/openthread_rcp_nrf_dongle.html to flash it. Can you elaborate on which flash I should delete?
I was mentioning it in case there is something different with the firmware that was referenced in the hackaday tutorial on how to set it up. All the links in the hackaday tutorial to the nrf dongle firmware and the guide are not working anymore.
Anyhow, since that's propbably just relaying the radio packets, I don't see why it should make any difference.
I am using ABCDE4 as the joiner key, but it does not work. I don't have any other thread devices yet to test it, but it looks like the reception is working. I receive packets that look like they come from the radio when I power up the sensor tag:
Nov 01 18:08:59 piradio otbr-agent[703]: 03:09:43.869 [I] MeshForwarder-: Received IPv6 UDP msg, len:83, chksum:67b0, ecn:no, from:a21216a434ef9868, sec:no, prio:net, rss:-62.0 Nov 01 18:08:59 piradio otbr-agent[703]: 03:09:43.869 [I] MeshForwarder-:     src:[fe80:0:0:0:a012:16a4:34ef:9868]:19788 Nov 01 18:08:59 piradio otbr-agent[703]: 03:09:43.869 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
I tried powering from a lab power supply to make sure there's enough juice, but it does not change anything.

@hansinator here, check out this page at the very bottom: https://hackaday.io/page/22272-how-to-setup-a-open-thread-border-router-with-raspberry-pi-and-connect-the-thread-sensor-tag
Try to run the factory reset as it is described there.

To do a factory reset you press the reset button and after the first hello signel (red,green,blue, and before the second helo signal) you press both button again for a quick boot. Once you see the hello signal press both buttons again. If you see the blue LED blinking 3 times, the device was factory reset.

Then you can try again to commission. If that does not help at all there might be an issue with the latest version of the RPC and the firmware of the Sensor Tag. But I don't think that this is the case dbh. I also was in the situation, that the comissioning worked but it did not connect for some reason. Thread is still relatively new and has some issues here and there and it is quite complex as well. We will figure it out.

The factory reset did the trick, thank you very much. It is strange though that both tags didn't work out-of-the-box.

The factory reset did the trick, thank you very much. It is strange though that both tags didn't work out-of-the-box.

it is indeed! there seems to be an issue with the initial comission. As I said, I have seen this multiple times already


Bot is using previous season's legality list

Fixed in #513?
On Fri., 4 Nov. 2016, 19:34 Thomas David Baker<EMAIL_ADDRESS>wrote:

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/PennyDreadfulMTG/Penny-Dreadful-Tools/issues/512, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAL2ztNcrAJF3x_S7sfgHuy7hMvjiALLks5q6u38gaJpZM4KpS9U
.

Ah, yes, I fixed this :)


2012 R2 servers and WAPs cannot be added to 2016 FBL

It appears that this has not been explicitly documented in the article and has caused some confusion.  Perhaps the article can be updated to state as such.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ebfd725f-1b77-751c-1948-f8f88d26a9bc
Version Independent ID: 7d9c78d9-7736-8f0a-9636-269125a10d6f
Content: Upgrading to AD FS in Windows Server 2016
Content Source: WindowsServerDocs/identity/ad-fs/deployment/upgrading-to-ad-fs-in-windows-server.md
Service: windows-server-threshold
GitHub Login: @billmath
Microsoft Alias: billmath

yes agree, we are on 2012R2 / ADFS 3.0 and were planning to use upgrade to ADFS 2019 (or 2016) to take advantage of Azure MFA build capabilities (without having to install MFA server) but stumbled upon this requirements which are not clearly specified and  are hidden towards the end of the document amongst last steps!

#please-close

The following users don't have valid GitHub IDs, or are not collaborators on this repo: ingridatmicrosoft
gh issue comment 773 -b ingridatmicrosoft


Minimum long read accuracy needed for metaMDBG

Congratulations on your recent pre-print about metaMDBG! One thing that I was curious about was the definition of "accurate long reads". I could not find an accuracy cutoff in the pre-print. For example, would long reads over Q20 (1% error rate) be acceptable as input into metaMDBG? Or is a more stringent accuracy cutoff (e.g., Q30, 0.1% error rate) needed? I am curious if you have any insights or predictions here. Thanks very much.

Hi, thank you very much!
The software has been designed and tested specifically on PacBio HiFi reads (so it's more like <0.1% error rate without homopolymer errors). We say "accurate long reads" because the sequencing technology is evolving quite fast, and maybe Nanopore reads will be compatible with our graph structure soon. We did some tests on the Nanopore R10.4 kits (they will be included in the next version of the manuscript) but the results are not that good and metaflye is still the way to go for that.

Thanks for the quick reply! It's good to know that the software was designed/tested for PacBio HiFi reads and that Nanopore R10.4 data still works better with metaFlye. Indeed, long read technology is progressing quickly... it would be interesting to test the new Q30+ duplex data coming from Nanopore R10.4.1 flow cells (especially the "high duplex" R10.4.1 flow cells currently under testing), although homopolymer errors are still an issue I think. Anyway, thanks for your work on this interesting tool and for the informative response.


Implement scrolling

Scrolling should be available in the command prompt. This requires writing the scrolling code from scratch (thanks Curses!)...

Finished in b685492 :smile:


[BL602] Update README.md, fix diagnosic impl

Problem
What is being fixed?  Examples:

Update README.md.Change demo board picture, and add debug log.
Fix diagnosic impl.This diagnosis is about get get used heap size. _heap_size is a symbol in ld scripts(examples/platform/bouffalolab/bl602/ldscripts/flash_rom.ld)，not a variable in RAM.So we use (uint32_t) &_heap_size to get total heap size.

Change overview
[BL602] Update README.md, fix diagnosic impl.
Testing
How was this tested? (at least one bullet point required)

test event:TC-CNET-4.15 TC-CNET-4.4

approve for v1.0 as platform specific fix.


Move jsonnet build to separate stage, to shrink final container

Move all the build dependencies into earlier stages to reduce the size
of the final output image.
In particular, this change moves the jsonnet compile and
ksonnet-lib git fetch into a new stage - and copies only the
necessary resulting artifacts into the final image.

I'm a bad person and haven't actually tested this, because I don't have a dockerd handy that supports multi-stage builds.  Someone else should do that before this is considered for merging.


Correctly setup parallel coveralls

https://coveralls.zendesk.com/hc/en-us/articles/203484329-Parallel-Build-Webhook

Coverage remained the same at 83.724% when pulling a6869c91c03cdeb7ae53113b07a1f5ab8b6e0919 on fix/coveralls into f8e9c420e318a3e92e72c5f6efa6f68b5a2ac04a on master.

Coverage remained the same at 83.724% when pulling a6869c91c03cdeb7ae53113b07a1f5ab8b6e0919 on fix/coveralls into f8e9c420e318a3e92e72c5f6efa6f68b5a2ac04a on master.

Coverage remained the same at 83.724% when pulling a6869c91c03cdeb7ae53113b07a1f5ab8b6e0919 on fix/coveralls into f8e9c420e318a3e92e72c5f6efa6f68b5a2ac04a on master.

Coverage remained the same at 83.724% when pulling a6869c91c03cdeb7ae53113b07a1f5ab8b6e0919 on fix/coveralls into f8e9c420e318a3e92e72c5f6efa6f68b5a2ac04a on master.

Coverage remained the same at 83.724% when pulling a6869c91c03cdeb7ae53113b07a1f5ab8b6e0919 on fix/coveralls into f8e9c420e318a3e92e72c5f6efa6f68b5a2ac04a on master.

Does not actually fixes multiple messages


Concurrent requests

Description
This pull request is set out to handle concurrent requests, when the table uses an api as datasource.
Each request gets assigned a number, which is then passed to the callbacks (both success and failure). The triggered callback checks if it is the latest request. If not, it terminates silently.
How to reproduce the issue the PR solves:
Setup

Implement a table with an api it requests data from
Ensure the api handles filters
Force the api to hang for a couple of seconds on a specific filter to simulate slower loading
Implement a toggle for the filter on the front-end

Execution

Set the filter to the slower loading setting
Before it finishes loading, set the filter to the faster loading setting
Wait for the table to load

Original result

The filter display will be the faster loading setting
The data displayed will be the slower request's data.

Expected result

The filter display will be the faster loading setting
The data displayed will be the faster request's data.

Thank you for your consideration,
Greg

Wow, this is very new to me. Thank you for your contribution. Will have to find time to merge it though.

@KrekoG I've implemented the support for concurrent request using your code, but I don't know how to properly test it. Could you please use this branch and see if it's working. So far, I've made a few modification so that all the previous tests are passed (npm t).
If it is, I can then merge it to v2.0 branch.


[add-resource] New Plugin

I would like to add my new plugin/theme to the Grav Repository._Here are the project details: https://github.com/Carve/grav-ui-libraries
It allows for users to integrate multiple or a single asset for multiple UI libraries.

Sorry, will add soon

Added to repo 👍


Wrong output using HED in process.py

When I use the functionality in process.py to generate edges using HED (after setting up the required things for HED), there seems to be a shift in the location of edges as compared to the colored ones.
Is there a reason for the same? How do we fix it?

@akileshbadrinaaraayanan same issue here. have you resolved it ?

I meet the same issue here. have you resolved this problem ?

@ningning32 Check my fork of the HED code
https://github.com/zaidalyafeai/pix2pix/blob/master/scripts/edges/batch_hed.py


Update-WinGetPackage default behavior

The default behavior of the Update-WingetPackage looks wrong. It should not try to upgrade all packages but only the ones with update available. So it should be a a syntactic sugar for Get-WinGetPackage | Where-Object -Property IsUpdateAvailable -eq $true | ForEach-Object { Update-WinGetPackage -Id $_.ID } , not Get-WinGetPackage | ForEach-Object { Update-WinGetPackage -Id $_.ID }. Currently it gets all the packages and then throws an exception.

Originally posted by @zbalkan in https://github.com/microsoft/winget-cli/discussions/3182#discussioncomment-5839059

I'll add to this re: "default behaviour". We should have an output that displays what has been updated (i.e. the name/id of the package in one of the columns). Currently it's like this:

IMO it's actually better behavior than the winget cli itself has, as assuming * is how other package managers behave, so the existing behavior is something of a consistency win.
But being able to use at least the common properties as params to the Update-WinGetPackage cmtlet itself would also be excellent and avoid the need to pipe it, which is clunky.


Ceylon tool import jar sources

The current tool import-jar does not allow to import a source jar along with the binary jar.

Should this simply add the specified source jar and a corresponding SHA1 file to the module subdirectory, or is there more work involved in this?

I assume that's all there is to it.

is it fixed ? it looks like there is activty for this.

would like this very much in 1.2.1 :)

Yes, AFAIK this should work now. Closing.

@quintesse milestone still 1.2.2?

It's already in master so I guess it will just be included. But I'll change the milestone anyway.


Updated palette and uses.  removed unused imports

This updates the way we use the palette code.  I went back to an earlier idea where we just import colors, but load them from a palette file instead of hard coding them in the init.py


trackline and recommanded parameters

Hi,
Thanks for developing epic which is much more stable than SICER ! that's great.
I have two comments:

If I'm correct, the output bed files are generated for UCSC visualization. Adding a trackline would be great in that case.
I think that other users already ask it, but having recommended parameters for different histone mark would be extremely useful.
I guess --window-size, --gaps-allowed and --false-discovery-rate-cutoff can be updated.
Any advice is welcome !

Those are to be found experimentally. I do not know them :/ But the original SICER README.pdf contained some suggestions.

i would suggest to add a parameter "--trackline", that simply add something a header like
"track name=pairedReads description="Clone Paired Reads" useScore=1"
See https://genome.ucsc.edu/FAQ/FAQformat.html#format1 for details
Thanks

But a generic name/description like that is not particularly helpful,
methinks.
On Mon, Jul 9, 2018 at 6:11 PM Nicolas Servant<EMAIL_ADDRESS>wrote:

i would suggest to add a parameter "--trackline", that simply add
something a header like
"track name=pairedReads description="Clone Paired Reads" useScore=1"
See https://genome.ucsc.edu/FAQ/FAQformat.html#format1 for details
Thanks
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/biocore-ntnu/epic/issues/81#issuecomment-403533564,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQ9I0hRn4cHlMESqQDqSQKSQXtizfSg2ks5uE4C1gaJpZM4VFto8
.

Sure. You can have a look at the Macs2 documentation for example.
It takes a --name option, and thus is the name in the "name=" and "description=" field.
Another idea would be to simply use the basename of the input file ....

There can be multiple input files so the basename cannot be used in
general.
I'm trying to cut down on features atm and instead outsource them to other
packages. But I will think about it/see if there are more requests for this.
Keeping the issue open :)
On Tue, Jul 10, 2018 at 9:58 AM Nicolas Servant<EMAIL_ADDRESS>wrote:

Sure. You can have a look at the Macs2 documentation for example.
It takes a --name option, and thus is the name in the "name=" and
"description=" field.
Another idea would be to simply use the basename of the input file ....
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/biocore-ntnu/epic/issues/81#issuecomment-403734847,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQ9I0kgemWhvMHGjEoc9vDJ1gTZFrgyNks5uFF6LgaJpZM4VFto8
.

Perfect ! Thanks

Do not use UCSC much, but aren't there tracklines in bigwigs? That would
also probably be a nice thing to add, since modifying binary formats is
much harder.
On Tue, Jul 10, 2018 at 10:43 AM Nicolas Servant<EMAIL_ADDRESS>wrote:

Perfect ! Thanks
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/biocore-ntnu/epic/issues/81#issuecomment-403746962,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQ9I0tY5dVFLvt8c4Eg5yxiALux7vDLNks5uFGkxgaJpZM4VFto8
.

For the bigwig, I think that the user can add its trackline when the data are loaded ;
track type=bigWig name="My Big Wig" description="A Graph of Data from My Lab" bigDataUrl=http://myorg.edu/mylab/myBigWig.bw


Question: how to serialize nodes.Node to protobuf?

It used to be uast.Node.Marshal() but not anymore.

import "gopkg.in/bblfsh/sdk.v2/uast/nodes/nodesproto"

var b bytes.Buffer
err := nodesproto.WriteTo(&b, node)
data := b.Bytes()

We should mention it somewhere in the docs.

:+1:

Reopening until documentation is updated

Closing as #105 is merged


SKU ID for powering up the PSU board

Product: (OC-SDR, OC-LTE, OC-LTE, OC-Power, others)
PSU
Component: (PSU, GBC, BBU, FEM, LED, ME)
PSU
Category: (Hardware, Software/stack, Firmware/bootloader, Documentation)
Software/Stack
Describe the solution you'd like

Framework to read/write on the EEPROM - CAT24C04WI-GT3
Depending on the SKU ID stored in the eeprom , the required power lines should be enabled

This feature is not needed as of now .
We can reopen this if this requirement resurfaces .


Adding a ghost role for parrots.

About the PR

This is a PR that adds a 5% chance that when creating a parrot it will become a ghost role.
Why / Balance

Our parrot has a voice and a speech accent (#26340). It would have been more appropriate to make him a ghost role.
Technical details

Changes were copied from part of the MobMonkey prototype
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Change history

Chance change from 10% >>> 2.5%
Chance change from 2,5% >>> 5%

Changelog

:cl: marbow

add: Now there is a chance that parrots can become a ghost role.

Ghost role + movement + ability to talk normally is really strong considering most ghost role pets are completely incapable of speech.

Ghost role + movement + ability to talk normally is really strong considering most ghost role pets are completely incapable of speech.
Pirate parrots absolutely should be a ghost role though.

that's right. In such cases, what is the best thing to do? Increasing the price of livestock parrots? Or reducing the chances of a ghost role?

just make it rarer

ok

Maybe they have a list of words they can actually say, and everything else gets replaced by bird noises?
Bonus fun if there's a small chance that if you hear a word it gets added to the list.

What about poly? Isn't that supposed to be what parrots are for.

agree with sloth, this isnt really what parrots are for, just need to implement ss13 parrots, theres plenty of other pet ghost roles to pick


Add Assembly Tutorial Starter Project

Add the project used at the start of the assembly tutorial

The place where we keep these under actual SCC is Vantiq/Contributions.  Moving the issue there...
Also, isn't this a tutorial?  In which case it belongs in Vantiq/Tutorials (I think).


Fix "The text of FeedFragment is clipped"

Issue

close #565

Overview (Required)

I don't know why it occurred 😭

Screenshot

LGTM! THIS IS ANDROID!


module dependencies now failing

At some point adding a dependency on a module has stopped working. On master, I noticed that the elk example was no longer working:
$ ./converge graph --local examples/elk/converge/elk.hcl
2016-10-18T21:05:09-04:00 |INFO| serving        addr=:47740 component=rpc
2016-10-18T21:05:09-04:00 |ERROR| could not load        component=rpc error=could not resolve dependencies: 4 error(s) occurred:

* root/docker.image.elasticsearch-image: nonexistent vertices in edges: module.docker
* root/task.filebeat-install: nonexistent vertices in edges: module.docker
* root/module.docker: nonexistent vertices in edges: module.packages
...

Here is a simple repro:
moduleTest.hcl:
module "submoduleTest.hcl" "submodule" {}

task "file" {
  check   = "test -f file.txt"
  apply   = "touch file.txt"
  depends = ["module.submodule"]
}

submoduleTest.hcl:
task "another-file" {
  check = "test -f first-file.txt"
  apply = "touch first-file.txt"
}

$ ./converge graph --local samples/moduleTest.hcl
2016-10-18T21:07:16-04:00 |INFO| serving        addr=:47740 component=rpc
2016-10-18T21:07:16-04:00 |ERROR| could not load        component=rpc error=could not resolve dependencies: 1 error(s) occurred:

* root/task.file: nonexistent vertices in edges: module.submodule location=samples/moduleTest.hcl runID=08008907-4a0d-4fd9-ae39-12cf403319f4
2016-10-18T21:07:16-04:00 |ERROR| loading failed        component=rpc error=loading samples/moduleTest.hcl: could not resolve dependencies: 1 error(s) occurred:

* root/task.file: nonexistent vertices in edges: module.submodule function=grapher.Graph runID=08008907-4a0d-4fd9-ae39-12cf403319f4
2016-10-18T21:07:16-04:00 |FATAL| could not get graph   component=client error=error getting graph component: rpc error: code = 2 desc = loading failed: loading samples/moduleTest.hcl: could not resolve dependencies: 1 error(s) occurred:

* root/task.file: nonexistent vertices in edges: module.submodule file=samples/moduleTest.hcl

This hcl works with converge 0.2.0:
$ ./converge-0.2.0 graph --local samples/moduleTest.hcl
2016-10-18T21:10:57-04:00 |INFO| serving        addr=:47740 component=rpc
digraph {

subgraph cluster_0 {
"root" [ label="Module: /" ];
"root/task.file" [ shape="component" , label="task.file" ];
}
subgraph cluster_1 {
"root/module.submodule" [ label="Module: module.submodule" ];
"root/module.submodule/task.another-file" [ shape="component" , label="module.submodule/task.another-file" ];
}
"root" -> "root/module.submodule" [ label="" ];
"root" -> "root/task.file" [ label="" ];
"root/module.submodule" -> "root/module.submodule/task.another-file" [ label="" ];
"root/task.file" -> "root/module.submodule" [ label="" ];
}

It looks like this was probably introduced by the changes to dependency resolution from the conditionals.  I'm looking into it.

I tracked it down to
https://github.com/asteris-llc/converge/blob/master/load/dependencyresolver.go#L175
If you remove that last kind == module check, it fixes the problem (and all tests still pass). But, I am guessing that check is there for a reason?

Actually I think that for whatever reason when I wrote that code I was convinced that we couldn’t depend on a module… should be safe to remove.

On Oct 19, 2016, at 7:27 AM, Ryan Eschinger<EMAIL_ADDRESS>wrote:
I tracked it down to
https://github.com/asteris-llc/converge/blob/master/load/dependencyresolver.go#L175 https://github.com/asteris-llc/converge/blob/master/load/dependencyresolver.go#L175
If you remove that last kind == module check, it fixes the problem (and all tests still pass). But, I am guessing that check is there for a reason?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub https://github.com/asteris-llc/converge/issues/395#issuecomment-254797495, or mute the thread https://github.com/notifications/unsubscribe-auth/AAMbqy11PeodvvgWKHeFhiV3AjFTTH1lks5q1gy8gaJpZM4KadW2.


Check the examples in the rule specifications

Waiting for #65 to merge in since its branched off of that


fixed maxigimenez/angular-atomic-notify#3

recovery the directive scope even when not nested in a parent controller

Here is the solution for that issue https://github.com/maxigimenez/angular-atomic-notify/releases/tag/v1.0.2 :smile:


feat(deck): Add service to return to gaming mode

Fixes users not being to switch to gaming mode when they have desktop autologin toggled and should allow users to start gaming mode immediately after Steam has been updated instead of having to reboot after setup (although this should be done regardless)
Fixes: https://github.com/ublue-os/bazzite/issues/165

Needs this for GNOME images: https://github.com/KyleGospo/tofumenu/pull/2


Make Backup-DbaDatabase use Database and ExcludeDatabase when piping

Type of Change

[x] Bug fix (non-breaking change, fixes #5044)
[ ] New feature (non-breaking change, adds functionality)
[ ] Breaking change (effects multiple commands or functionality)
[ ] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[x] Pester test is included
[ ] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

added some regression tests too

ugh, the code works but my tests blew 👎

heck yah, one unrelated failure


Mutations for Queries

Creating javascript file for mutations in graphql.

Don't make seperate PR for Queries and Mutations.


Automatically increment version and add changelog

VSCode Extension Installation Instructions

Download the extension at https://azuresdkreleasepreview.blob.core.windows.net/azd/vscode/pr/572/azure-dev-0.4.0-alpha.vsix
Extract the extension from the compressed file
In vscode
a. Open "Extensions" (Ctrl+Shift+X)
b. Click the ...\ menu at top of Extensions sidebar
c. Click "Install from VSIX"
d. Select location of downloaded file

Closing in favor of https://github.com/Azure/azure-dev/pull/814


Discussion: Support multiple platform such as macOS, windows

Recently, I'm trying to set up a development environment for milvus-sdk-cpp under my M1-based macbook. It failed while compiling grpc. Currently, I'm back working with Linux.
Maybe this is a further topic we could handle after the initial version was done under Linux. IMO we could have some discussions right now.
Do we need to support other platforms for the cpp SDK? And if so, what is the detailed solution ...
AIK, grpc/Zlib currently are supported for windows/macOS officially.

Milvus server can only run on linux OS. But SDK should be no limited by OS. Ideally, user ought to can use sdk in mainstream operation system including Mac, Windows, Linux.

/close


Fanchen/add support floating cluster addr

This change adds support for different clusters with different numbers of cores, which will be used in the Hemaia system.

Change the start.S
The computation of cluster_idx, cluster_local_core_id, and cluster_core_num follows the snrt.h
Change the snrt_cls_base_addr()
This function is related to the behavior of snrt_l1_next(). The start_addr should be computed from the snrt_cluster_base_addrl() instead of the old SNRT_TCDM_START_ADDR + snrt_cluster_idx() * SNRT_CLUSTER_OFFSET, which the SNRT_CLUSTER_OFFSET is hardcoded in snitch_cluster_defs.h. This is not a problem in snax but will be a problem in occamy.

@Konste11ation there's a white space on the C code haha

@rgantonio Your hypercorex seems to have failed while at last ci run it passed. Can you maybe make a short check? 😊

@Konste11ation @IveanEx oops haha I made hard modifications last night. Leave the hypercorex to fail. I will fix later the sw side. 🙂

@IveanEx Thank you for removing the space 😺
@rgantonio I will push to the main haha, thx


[Feature] Support for OpenShift

Description
This issue tracks the support for OpenShift Kubernetes distribution
Steps

[x] support for the OwnerReferencesPermissionEnforcement Admission Controller - #896
[x] disable the discovery component (it is useless, and causes troubles)

move the operators to the liqo controller manager - #902
remove the clusterID creation - #908
disable the deployment - #910

[x] add SecurityContextConstraints (privileged, anyuid) - #914

liqo-route
liqo-gateway
liqo-auth

[x] add dedicated liqoctl install provider - #914

Closing since addressed by #914


kata v1.11.0

time="2023-05-04T09:03:05Z" level=error msg="CPU property not found" arch=amd64 description=SSE4.1 na
me=sse4_1 pid=2251 source=runtime type=flag
time="2023-05-04T09:03:05Z" level=error msg="ERROR: System is not capable of running Kata Containers"
 arch=amd64 name=kata-runtime pid=2251 source=runtime
ERROR: System is not capable of running Kata Containers

https://blog.csdn.net/kunyus/article/details/106986621
https://discuss.linuxcontainers.org/t/lxd-4-0-cannot-use-vm-errors/7312

# /opt/kata/bin/kata-runtime kata-check
System is capable of running Kata Containers
System can currently create Kata Containers

root@ubuntu:~# docker run --runtime kata-runtime ubuntu
Unable to find image 'ubuntu:latest' locally
latest: Pulling from library/ubuntu
dbf6a9befcde: Pull complete
Digest: sha256:dfd64a3b4296d8c9b62aa3309984f8620b98d87e47492599ee20739e8eb54fbf
Status: Downloaded newer image for ubuntu:latest
docker: Error response from daemon: OCI runtime create failed: failed to launch qemu: exit status 1, error messages from qemu log: qemu-system-x86_64: -object memory-backend-ram,id=dimm1,size=2048M: cannot set up guest memory 'dimm1': Cannot allocate memory: unknown.
ERRO[0015] error waiting for container: context canceled

version: '3'
services:
  vm:
    image: ssst0n3/docker_archive:ubuntu-20.04_docker-ce-19.03.11_containerd.io-1.4.9_runc-1.0.1
    ports:
      - "2222:22"
    command: /start_vm.sh -m 4096M -cpu host -enable-kvm
    devices:
      - "/dev/kvm:/dev/kvm"

done https://github.com/ssst0n3/docker_archive/tree/branch_ubuntu-20.04_docker-ce-19.03.11_containerd.io-1.4.9_kata-1.11.0


chore: use Node's promisify function

Node's promisify function and the TS types for it give much better type
understanding when wrapping a function in promisify. This change means
we don't maintain our own implementation and our own (sub-par) types and
rather lean on the tested and thorough @types/node version instead.

This will pass once #5750 is merged + this PR updated.


[fix][flaky-test]BrokerServiceTest.testLookupThrottlingForClientByClient

Fixes #16521
Master Issue: #16521
Motivation

this test is still flaky
In BrokerServiceTest.testLookupThrottlingForClientByClient, if the broker responds and client handle response quickly enough, this test will fail.
Modifications
Add a signal to control the execution speed of "client handle response". The logic is almost like #16540
Documentation

[ ] doc-required
(Your PR needs to update docs and you will update later)

[x] doc-not-needed
(Please explain why)

[ ] doc
(Your PR contains doc changes)

[ ] doc-complete
(Docs have been already added)

@AnonHxy
Sorry, the PR is very similar to the PR you submitted last time, you can reopen the closed PR #https://github.com/apache/pulsar/pull/16540, and notice me close this.

@AnonHxy
Sorry, the PR is very similar to the PR you submitted last time, you can reopen the closed PR ##16540, and notice me close this.

OK. I have already reopen https://github.com/apache/pulsar/pull/16540 @poorbarcode


Feature: Import alternate hydroweb.xml format

The linked hydroweb.xml is a different format to the newer hydroweb.xml found at https://www.hydrodata.ch/data/xml/hydroweb.xml (Password protected.)
There seem to be differences in the amount of parameters and locations as well.

Plus its really more precise.

Implemented in v1.2.0