Inconsistency while subsequent pREST calls

Hi!
Calling pREST POST operation twice (inserting value in two different tables) throws an error on the second operation. It is totally random, as the operations succeed sometimes and fail sometimes.
The error is pq: database "users" does not exist".
Note: It exists
Also setting debug=true does not output any error for pREST logs.

pREST version (or commit ref): Docker:latest (v0.3.4)
pREST endpoint: POST http://prest/DATABASE/SCHEMA/TABLE with JSON data
PostgreSQL version: Docker:11.1-alpine
Operating system: Dockerized pREST
Go version: Dockerized pREST
Log gist: Insert succeeds for the first op but fails for second with no logs. Sometimes, both the inserts succeed

Thanks for any help!

Get a similar problem on get.
[msg] pq: database "assets" does not exist
Completely random. I can serve 100s of requests without issue, or 2 and get the issue. Note that I'm not on the database asset.


431 multiple tasks alyssa felix

We changed the clientReadyMessage (which goes from the client to the server, indicating that they are ready to share updates) to contain the taskID. In this way, the signaling server can map each taskID to an array of readyPeers. This ensures that clients from different tasks/model architectures will not be selected to share weights and aggregate together.

What do you think of this suggestion: To add this.readyClientsBuffer = this.readyClientsBuffer.set(msg.taskID, []) in the first part of the handle function (before ws.on() ? This would allow us to avoid the if-else blocks at lines 59-69

An issue with this is that we don't know what kind of message is being sent before ws.on, so we couldn't be sure that the msg would have a taskID.


Improve some literal oddness in docs

Square brackets, when run on nightly, auto-link to the types that they refer
to. That doesn't work if the types are meant to be a grammar, not a reference
to a type, and it gives crazy warnings.
Also it just looks a bit more reasonable IMO to have literal terms look like
literal terms.

yup!


Sometimes controller.currentPositon is bigger than controller.duration when play end.

Media3 Version
1.0.0-beta01
Devices that reproduce the issue
Samsung galaxy note 10 5G running Android 11
Devices that do not reproduce the issue
No response
Reproducible in the demo app?
Not tested
Reproduction steps

Just play the audio attached
Open it, drag the seekbar to where a few second left
Wait it play end
Print the MediaController.getDuration and MediaController.getCurrentPosition, you will find that the latter is greater than the former, 900ms.
if it does not appear, repeat.Usually two to three times.

Expected result
The difference should not exceed 100ms I think.
Actual result
The difference is close to a second.
Media
Help (Sunset Rollercoaster 落日飛車 Remake) - 혁오 (HYUKOH) _ 落日飛車.mp3.zip
Bug Report

[ ] You will email the zip file produced by adb bugreport to<EMAIL_ADDRESS>after filing this issue.

I can repro this with the attached media in the demo app. The duration is 4.12 and the timebar goes to 4:13 when the songs play ends.

Seeking in MP3 files is known to be inaccurate due to limitations in the format. See https://github.com/google/ExoPlayer/issues/7767#issuecomment-677760688 for more explanations. You can work around this by setting Mp3Extractor#FLAG_ENABLE_INDEX_SEEKING in DefaultExtractorsFactory.setMp3ExtractorFlags. But note that this setting should only be used for relatively short MP3 files like this one.


Rename northarrow output

change the output name of northarrow to be northArrowSubReport instead of subReport

Makes sense to be consistent.


Add reports

There should be a way to see :

[x] the current time spent on each project...
[x] ... for a given period

d7cba8c somewhat solves this… Other than a Record that spans over one (or multiple) days. The whole duration would be reported for the start of the Record. I probably should add some tests for the reports too… Not sure all my math is right wrt lastweek et al… I'll do that still


Benchmark results in README

Hi, would it be possible for the authors to add the accuracy results that they're getting to the README? Right now I'm seeing numbers which are mid 80's for certain models when I know certain people have reported 89/90 with Deep Learning methods on IMDB.

Hey @joeybose, that is a good idea. We will consider doing that in the future.
In the meanwhile, if your question is which methods you should try - I recommend checking http://nlpprogress.com/english/text_classification.html


Add ilastik content types

@lzehl @UlrikeS91
I added the content types for Ilastik based on Issue #296
If you find that anything is missing or incorrect, let me know.

@lzehl @UlrikeS91
I added the content types for Ilastik based on Issue #296 If you find that anything is missing or incorrect, let me know.

I'm not an expert. So, I won't involve myself. I added @jagru20, @apdavison and @lzehl as reviewers. I don't believe that all are required, but this way whoever has time first, can review the PR.

@k-dominik could you help us figuring out the open issues in the PR? For your information: openMINDS content types are inspired by IANA.org media types to define software (version) specific file types that can go beyond generic formats (e.g. a software specific json). We are trying to register all input and output content types of Ilastik in this PR.

@k-dominik thank you so much for the clarifications.  I have a question in order to answer your question:
Are the internal file structure of the hdf5 files workflow specific?
If yes, I would indeed split the content types up and follow the naming convention you suggested (...image/vnd.ilastik.<workflowname>.probabilties+hdf5). If no, I would keep the workflow out of the content type definition (...image/vnd.ilastik.probabilties+hdf5).
I also have another favor to ask: could you give us a short (1-2 sentence) description we could add for each ilastik content type?

...image/vnd.ilastik.probabilties+hdf5
...image/vnd.ilastik.probabilties+csv
...image/vnd.ilastik.prediction+hdf5
...image/vnd.ilastik.prediction+jpeg
...image/vnd.ilastik.prediction+png
...image/vnd.ilastik.prediction+tiff-stack
...image/vnd.ilastik.prediction+tiff
...image/vnd.ilastik.segmentations+hdf5
...image/vnd.ilastik.segmentations+jpeg
...image/vnd.ilastik.segmentations+png
...image/vnd.ilastik.segmentations+tiff-stack
...image/vnd.ilastik.segmentations+tiff

Okay I see - I don't think adding the workflow to the predictions type is necessary - while there could be a semantic difference depending on the workflow, it will in any case be an nd-image.
For the 1-2 sentence description - can I assume that describing probabilities/predictions (terms we use interchangeably) and segmentation would be enough?

@k-dominik you mean we can only use "prediction" or only use "probabilties" in the content types above? I though the ...image/vnd.ilastik.probabilties+hdf5 and ...image/vnd.ilastik.prediction+hdf5 is not the same, or is it? Maybe we can have a short call to clarify this issue ?

RESULT discussion with @k-dominik :
...image/vnd.ilastik.hdf5

Reduce to one, because the internal structure does not change.
...application/vnd.ilastik.hdf5

contains feature table / object classification
...application/vnd.ilastik.csv

contains feature table

For the workflow project files:
...application/vnd.ilastik.project.WORKFLOW+hdf5

we could start with the workflows

Pixel Classification, and
Object Classification.

SUMMARY with feedback from @apdavison & @k-dominik  :

image/vnd.ilastik.hdf5 (input/output)
application/vnd.ilastik.features+hdf5 (output)
application/vnd.ilastik.features+csv (output)
application/vnd.ilastik.pixelclassification+hdf5 (input/output)
application/vnd.ilastik.objectclassification+hdf5 (input/output)

Note: additional input / output for ilastik are the general formats for png, jpeg, tiff, and tiff-stack (because they are not specially formatted/modified by ilastik in any way).

@MaaikevS sorry I forgot to ask: do you want to do the changes for this PR or should I take over?

@MaaikevS I think I'm not able to take make the needed edits on your branch. Could you do the final changes or should I close this PR and make a new one?
Here a summary of what needs to be done:
Please reduce the PR to the following content types
image/vnd.ilastik.hdf5 (input/output)
application/vnd.ilastik.features+hdf5 (output)
application/vnd.ilastik.features+csv (output)
application/vnd.ilastik.pixelclassification+hdf5 (input/output)
application/vnd.ilastik.objectclassification+hdf5 (input/output)
Please adapt the atIDs of the content types to this (new) convention:
"@id": "https://openminds.ebrains.eu/instances/contentTypes/image_vnd.ilastik.hdf5"
"@id": "https://openminds.ebrains.eu/instances/contentTypes/application_vnd.ilastik.features+hdf5"
"@id": "https://openminds.ebrains.eu/instances/contentTypes/application_vnd.ilastik.features+csv"
"@id": "https://openminds.ebrains.eu/instances/contentTypes/application_vnd.ilastik.pixelclassification+hdf5"
"@id": "https://openminds.ebrains.eu/instances/contentTypes/application_vnd.ilastik.objectclassification+hdf5"
Please also adapt the file names to this (new) convention:
image_vnd.ilastik.hdf5.jsonld
application_vnd.ilastik.features+hdf5.jsonld
application_vnd.ilastik.features+csv.jsonld
application_vnd.ilastik.pixelclassification+hdf5.jsonld
application_vnd.ilastik.objectclassification+hdf5.jsonld

@MaaikevS I'm closing your PR without merging due to the last discussions on this topic and the work connected to this. Thanks a lot for pushing this in the past.


added rails to bundled_commands

While switching to a different approach in developing with Ruby (discarding RVM and using rbenv with project specific bundles instead) I found out that rails is not being executed through bundler. This little patch fixes this.

I'd personally like to see this come back in but it was taken out in this pull request (https://github.com/robbyrussell/oh-my-zsh/pull/785).
For the full reasoning behind thing, see this blog post: http://blog.wyeworks.com/2011/12/27/bundle-exec-rails-executes-bundler-setup-3-times.
I've reached out to Santiago on his blog to confirm that 1) The issue will be fixed in the latest release of Bundler and 2) If Rails is not in the load path - meaning it's only installed in the bundle - then there is no issue.
Hopefully Santiago will clear things up soon. In the meantime, we're going to hold this until we can get some definitive answers.

I agree, I'm going to bring this back. Judging from the comment, if I understood correctly, Bundler 1.1 will take care of some of these issues.


Add an AppVeyor build of this repo

This build would export release builds of the SDK example apps, and possibly the Tableau connector as downloadable assets.

Fixed by #47


Request: draft init --minikube to force minikube detection

This is a minor feature request
I would like a draft init --minikube option, I am using Draft on Minikube and I have overriden the kube-context to work with some VirtualBox NAT rules on my VPN.
My workflow currently looks like this:
# (There is a block of entries like this in my .kube/config:
# - cluster:
#    certificate-authority: /Users/kingdonb/.minikube/ca.crt
#    server: https://kubernetes.default:8443
#  name: minikube-vpn
# contexts:
# - context:
#    cluster: minikube-vpn
#    user: minikube
#  name: vpn
# )
#
minikube start
helm init
draft init
# (connect to the VPN)
kubectl config use-context vpn
kubectl --namespace=kube-system get po -w

This works great!
But if I start the process of installing draft and I am already connected to the VPN, minikube detection fails, I am prompted to enter a registry, and the way to resolve it for me is to disconnect from the VPN, use-context minikube, and only draft init while I'm disconnected from the VPN.

This should be solved via #168. Under #168 the user will have to specify the cloud provider on draft init e.g. draft init --driver minikube

Awesome! Thank you


CoreNEURON CI via Github Actions

CI_BRANCHES:NEURON_BRANCH=master

please retest

not launching ci, will redo pr


More efficient forwards updates

Today, the updates of forwards is done with a fixed start_date and incrementing the index_offset. While this technically works, it places an unnecessary amount of strain on the backing LND instance. This PR changes the logic to make use of incrementing index_offset, but only if a start_date window is exhausted. This results in a large speed-up for syncing forward events in nodes that either use a slower DB backend (like kvdb_postgres) or if there are just lots of forwarding events (200k+).

This patch was tested on my node as well as Nodelou and RecklessApotheosis.

This PR not only greatly increases import speed of initial forwarding data in our tests, but also speeds up subsequent fwdinghistory calls that LNDg makes (every 20 seconds by default), which is a HUGE QOL improvement. Running this patch improved page loading times massively and completely eliminated the frequent timeouts I had been experiencing.

tested also here on a big node with a db of arround 23gb.
Huge speed up in almost all tabs, slighlty reduced CPU usage on the VM,
no more server error opening channel performance tab
great job guys!


Add reason for new lines at end of files

Fixes #93. Links to this article to explain why it should be done, specifically for JS files.

This is my reasoning:
https://gist.github.com/zackdouglas/0d4ce1a755e683332c64/revisions
If a newline is added, it is immediately clear that no existing logic is changed simply by adding logic.


RHIROS-393 | io Utilization as dict and max_io

Changes:

HostsApi modified marshall fields and added io dict sorting, max_io
HostDetailsApi modified marshall fields and added io dict sorting, max_io
to keep it consistent with HostsApi
HostHistoryApi io values are now dict and sorted on values
max_io added to build_sort_expression for enabling ASC and DESC sorting
Added util function for sorting io_dict
Modified Make file for easier testing, can be reverted if deemed not necessary

Sample Responses:
All Systems:
/api/ros/v0/systems?order_by=max_io&order_how=DESC
"data": [
        {
            "fqdn": "rhel8-test.hyrdvbbl3ugefmkdahnvv2bx1h.rx.internal.cloudapp.net",
            "display_name": "rhel8-test.hyrdvbbl3ugefmkdahnvv2bx1h.rx.internal.cloudapp.net",
            "inventory_id": "f73715ea-00b6-4a02-a4aa-528584b04dfd",
            "account": "0000001",
            "number_of_suggestions": 0,
            "state": "Optimized",
            "performance_utilization": {
                "cpu": 100,
                "memory": 95,
                "max_io": 700.0,
                "io_all": {
                    "xvdb": 700,
                    "xvdc": 92,
                    "xvda": 72
                }
            },
            "cloud_provider": "azure",
            "instance_type": "Standard_B1s",
            "idling_time": "98.90",
            "io_wait": null
        },
        {
            "fqdn": "ip-172-31-45-168.ap-south-1.compute.internal",
            "display_name": "ip-172-31-45-168.ap-south-1.compute.internal",
            "inventory_id": "f2b4c41d-27bd-4785-9dc4-ac09b6782981",
            "account": "0000001",
            "number_of_suggestions": 0,
            "state": "Optimized",
            "performance_utilization": {
                "cpu": 5,
                "memory": 22,
                "max_io": 400.0,
                "io_all": {
                    "sdb": 400,
                    "sda": 100,
                    "xvga": 95
                }
            },
            "cloud_provider": "aws",
            "instance_type": "t2.micro",
            "idling_time": "99.60",
            "io_wait": null
        },
        {
            "fqdn": "ip-172-31-25-176.ec2.internal",
            "display_name": "ip-172-31-25-176.ec2.internal",
            "inventory_id": "88f2588b-a1f1-4638-8b45-50ca2c3ec93e",
            "account": "0000001",
            "number_of_suggestions": 0,
            "state": "Waiting for data",
            "performance_utilization": {
                "cpu": 8,
                "memory": 27,
                "max_io": 352.0,
                "io_all": {
                    "sdb": 352,
                    "sda": 100,
                    "xvga": 75
                }
            },
            "cloud_provider": "aws",
            "instance_type": "t2.micro",
            "idling_time": null,
            "io_wait": null
        }
    ]

Individual Endpoint:
/api/ros/v0/systems/88f2588b-a1f1-4638-8b45-50ca2c3ec93e
{
    "fqdn": "ip-172-31-25-176.ec2.internal",
    "inventory_id": "88f2588b-a1f1-4638-8b45-50ca2c3ec93e",
    "display_name": "ip-172-31-25-176.ec2.internal",
    "performance_utilization": {
        "cpu": 8,
        "memory": 27,
        "max_io": 352,
        "io_all": {
            "sdb": 352,
            "sda": 100,
            "xvga": 75
        }
    },
    "rating": 0,
    "number_of_suggestions": 0,
    "state": "Waiting for data",
    "report_date": "2021-12-15",
    "instance_type": "t2.micro",
    "cloud_provider": "aws",
    "idling_time": null,
    "io_wait": null
}

History Endpoint:
api/ros/v0/systems/f2b4c41d-27bd-4785-9dc4-ac09b6782981/history
"data": [
        {
            "cpu": 5,
            "memory": 22,
            "io": {
                "sdb": 400,
                "sda": 100,
                "xvga": 95
            },
            "report_date": "2021-12-16"
        },
        {
            "cpu": 5,
            "memory": 22,
            "io": {
                "sdb": 400,
                "sda": 100,
                "xvga": 95
            },
            "report_date": "2021-12-15"
        }
    ]

Need to have this merged first, https://github.com/RedHatInsights/ros-backend/pull/138
Yet to add openapi spec changes

@apuntamb / @kgaikwad  On second thought, could you let me know if changes on the Individual and History endpoints make sense?
I'll make changes to the openapi.json and push accordingly.

@apuntamb / @kgaikwad On second thought, could you let me know if changes on the Individual and History endpoints make sense?
I'll make changes to the openapi.json and push accordingly.

IMO, yes they do make sense for both these endpoints as we do want to show consistent information throughout. Any other thoughts?

Here is the screenshot for same

I just noticed one thing that changing the sorting the API is giving 500
https://ci.foo.redhat.com:1337/api/ros/v0/systems?limit=50&offset=0&order_by=max_io&order_how=ASC
is it because you still need to handle that in the code?

@PreetiW About the 500 api error my money is on this one :point_down:
sqlalchemy.exc.DataError: (psycopg2.errors.InvalidTextRepresentation) invalid input syntax for type integer: "31.4"
IMO and based on my limited research IOPS values should be integers, hence I have tested with the same, refer Sample Responses above.
Hence, max_io should essentially be an int in db record.
I believe the archives have dummy values. But this should work with actual/int values, tested again on api/ros/v0/systems?limit=50&offset=0&order_by=max_io&order_how=ASC, works okay.
I am checking with @kgaikwad if in case we can expect float for any of the util values. If so, I'll push changes accordingly.

Thanks @saltgen for sharing the info, IIRC the disk IOPS values can be float, but it will be good to check with @kgaikwad 💯

Thanks @saltgen for sharing the info, IIRC the disk IOPS values can be float, but it will be good to check with @kgaikwad 100

@PreetiW All util values would be available in int including IOPS i.e. max_io and io object values.


Add periodic to check for updates and build new base image

This periodic job runs every weekday at 10am PST. It checks if there are available yum updates on the latest EKS Distro base image, and if available, it builds a new base image and creates PR's to the respective repos to change the image tag in the respective files.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Closing this PR as I created a new one -  #21


scope.generatorType undefined

Hey,
Not sure exactly how to use this package as I'm still a bit new to Sails.  After copying the project to a local directory, I have run:
npm install
node ./bin
but it complains about the scope.generatorType not being set.  Where do I set this or do I need to install this generator in a different way?

@bardlehel Ohh this actually a bit complicated. We don't have tests here. So I'm testing it using npm link command. Just link this module into my global sails module. and it uses needed generator when I call sails new someProject
Did you use npm link before ?

i haven't.  can you link me the proper documentation or give me run-down on steps i'd need to perform?

@bardlehel Actually there is no exact step by step documentation for sails-generators. Here are links that will help with linking modules.
https://docs.npmjs.com/cli/link
https://60devs.com/simple-way-to-manage-local-node-module-using-npm-link.html


Switch from SweetAlert to SweetAlert2

I would like to propose to switch from SweetAlert to SweetAlert2 - the supported fork of SweetAlert. The original reason for creating SweetAlert2 is inactivity of SweetAlert: https://stackoverflow.com/a/27842854/1331425
Reasons to switch:

Accessibility (WAI-ARIA) - SweetAlert2 is fully WAI-ARIA compatible and supports all popular screen-readers. Accessibility is a must in 2018, there are a lot of explanatory and tech articles, but this one is truly inspirable: Software development 450 words per minute

Better buttons contrast is a huge advantage for all users especially for users with vision disabilities.

Better support, average time to resolve an issue:

SweetAlert:
SweetAlert2:

SweetAlert2 is more popular that SweetAlert:

SweetAlert:
SweetAlert2:

laravel-admin users are trying to use SweetAlert2 parameters and get confused, e.g. https://github.com/sweetalert2/sweetalert2/issues/1203

Technical details about switching are described in the migration guide: https://github.com/sweetalert2/sweetalert2/wiki/Migration-from-SweetAlert-to-SweetAlert2

PS. I fixed indentation as well because it was mixed (2 spaces and 4 spaces), for better code review use ?w=1: https://github.com/z-song/laravel-admin/pull/2374/files?w=1

Thanks!


Many Portuguese badwords are not recognized anymore

Since we are not using stemming anymore, and the badwords list generated for Portuguese was originally created based on stems (21e410f), excluding variations of each word (when its stem was the same as the stem of a word which would be kept in the list), these variations are not recognized as badwords anymore.
For example:
>>> from revscoring.languages import portuguese
>>> [ portuguese.is_badword(x) for x in [ "mentiroso", "mentirosa", "mentirosos", "mentirosas" ] ]
[True, False, True, False]

This was the raw badwords list used in the filtering process:
https://gist.github.com/he7d3r/7e3718a43f5ce65e0dab
This was the script used for filtering:
https://gist.github.com/he7d3r/de5af63ac04338c3bfbf#file-stemtomostfrequentword-py

I added these particular badwords back in https://github.com/wiki-ai/revscoring/pull/179
But that doesn't solve the general problem.  We might need to use a hybrid of stemming/regex to get the both the coverage we had before and the flexibility that regex provides.

https://github.com/wiki-ai/revscoring/pull/228 might help with this.

Looks like this was resolved a long time ago


Incorporate Luis' variable groupings for WHO

This should combine a bunch of different higlight charts into a bar chart.
Before:

After:

Thanks Dan!


Load $PROFILE from PowerShell kernel

Is your feature request related to a problem? Please describe.
It appears that the runspace hosted by the PowerShell kernel does not expose a $PROFILE automatic variable, and that no profile scripts are run on startup.
Describe the solution you'd like
It would be really handy to be able to load common modules and functions from a PowerShell profile when starting a PowerShell Interactive session, perhaps by using the same $PROFILE logic as pwsh itself.
Describe alternatives you've considered

Use a $PROFILE path specific to .NET Interactive.
Use the same $PROFILE automatic variable, but also set a new automatic variable (e.g.: [boolean] $IsJupyter) to allow profiles to tailor their behavior based on the runspace host.
Expose the same $PROFILE automatic variable but with a new property for a Jupyter-specific path that is checked first before defaulting to proceeding to CurrentUserCurrentHost.

Thanks for an awesome new way to use PowerShell! 💕

On the one hand, the jupyter session isn't interactive in the same way as a terminal (there's no prompt!) and the goals of notebooks require them to portable in ways that normal interactive use is not. It would be painful to create a notebook and have it look different for others because they don't have the formatting rules I have in my profile...
On the other hand, I use my profile to customize my interactive PowerShell sessions significantly, not just adding information into my prompt, but also modifying my PSModulePath, fixing up type formats, etc. It's a little painful to me for all of that to be missing.
Buttom line, I'm torn on this. I don't think I want to run the normal default profile, but I do think maybe we need to support a host-specific dotnetinteractive_profile.ps1 ... but I will concede that the promise of profile.ps1 is "AllHosts" and it's weird that it doesn't run here...


✨ Add Japanese Yen currency

Added Japanese Yen currency symbol and abbreviations to bottom of relevant strings to enable currency in Stripe.

Thank you for your contribution! We are planning some work that will improve our currency support in a more complete way and so I'm closing this in lieu of the proper solution.

@ErisDS I apologize for the sudden interruption.
I'm considering installing Ghost and I'm running into the same problem.
Is there any progress since then?


[docs] fix workflow example

The directory for the checkout must be created before we can use it.

@hasbro17 Thanks for your propose, add the lines.
Sorry for the delay, did not check my github

@Comradin could you also update the user_guide to make installing the operator-sdk more explicit?

@fanminshi Thanks for the suggest, adjusted the file, too

lgtm


Bug: Bindable property and notify property do not work with enums

it's not working with enumerators
maybe IEquatable<T> is the problem

This is right, I'll have a look into that tomorrow.


eurostat code changes done

Source URL: https://ec.europa.eu/eurostat/databrowser/bulk

I've addressed all the  comments on https://github.com/datacommonsorg/data/pull/1112 for the import Eurostat data. Since it's outdated, I've closed it and created a new https://github.com/datacommonsorg/data/pull/1119 reflecting the changes. Please review: https://github.com/datacommonsorg/data/pull/1119


add tehran-stocks

Tehran-stocks is a project to get data from Tehran stock exchange.
Thank you for contributing! Please confirm this pull request meets the following requirements:

[x] I followed the contributing guidelines: https://github.com/github/explore/blob/master/CONTRIBUTING.md
[ ] I have no affiliation with the project I am suggesting (as a maintainer, creator, contractor, or employee).

Which change are you proposing?

[x] Suggesting edits to an existing topic or collection
[ ] Curating a new topic or collection
[ ] Something that does not neatly fit into the binary options above

Editing an existing topic or collection
I'm suggesting these edits to an existing topic or collection:

[ ] Image (and my file is *.png, square, dimensions 288x288, size <= 75 kB)
[x] Content (and my changes are in index.md)

It a project that made in Iran for Iranians(and others if like to invest or investigate Tehran stock exchange)

Curating a new topic or collection

[ ] I've formatted my changes as a new folder directory, named for the topic or collection as it appears in the URL on GitHub (e.g. https://github.com/topics/[NAME] or https://github.com/collections/[NAME])
[ ] My folder contains a *.png image (if applicable) and index.md
[ ] All required fields in my index.md conform to the Style Guide and API docs: https://github.com/github/explore/tree/master/docs

Please replace this line with an explanation of why you think this topic or collection should be curated.

Something that does not neatly fit into the binary options above

[ ] My suggested edits are not about an existing topic or collection, or at least not a single one
[ ] My suggested edits are not about curating a new topic or collection, or at least not a single one
[ ] My suggested edits conform to the Style Guide and API docs: https://github.com/github/explore/tree/master/docs

Please replace this line with an explanation of your proposed changes.

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

Hi,
Thanks for starting this pull request. In order to review it for acceptance, we need to make sure that all of the prerequisites are satisfied. I see that you didn't check this:

I have no affiliation with the project I am suggesting (as a maintainer, creator, contractor, or employee)

This is a requirement so that we can maintain a high level of independence in this project. Please update if you are able to verify that you meet that requirement.
Thanks!


DAT-65899: scrollbar styles

see my comment on DAT-65899

@makc-dataloop I checked and now the scroll is constantly visible, which is not what product wanted. You couldn't find a solution that works for both Firefox and the new Chrome version to show it only on hover?

@makc-dataloop i will merge this in another fix, thanks for the awesome research and solution.
Closing this PR


adding additional data source Isolario project

From @jkldgoefgkljefogeg on August 24, 2017 18:3
MRT is available at https://www.isolario.it/Isolario_MRT_data/
Copied from original issue: CAIDA/bgpstream#51

Isolario project no longer maintained; this is OBE.


Import "ibm_noise_models" could not be resolved.

Please delete the line: import "ibm_noise_models" as we are not considering any noise in this work.

Thank you.


Widget caching

A slightly more updated version of #39

@ajb — this is great!
I’ve been spending a lot of time thinking about this, and I’m currently leaning towards the idea of making caching a separate gem that layers on top of Fortitude. The reasons are subtle, but basically boil down to caching being complex (bugs are nasty, exactly what cache keys should be can be tricky, it’s easy to flood your cache if you’re not careful, etc.) and not wanting to have that load placed on Fortitude’s core.
One question I have for you: the @virtual_path stuff seems like the only part of this that wouldn’t work very cleanly in a separate gem. (This is exactly the sort of thing that around_content is for!) Can you elaborate a little more on what that’s used for? In your code it looks like it’s required to be set, and is passed properly, but nothing in the diff actually uses it — I assume that means Rails magically uses it under the covers for caching somehow?

Yeah, you've got it. Rails looks at the virtual_path in order to find the template file to digest: https://github.com/rails/rails/blob/92703a9ea5d8b96f30e0b706b801c9185ef14f0e/actionview/lib/action_view/helpers/cache_helper.rb#L204

OK, I just went spelunking down quite the rabbit-hole. I have a question for you, and then a broader discussion:
Question: What specific case was failing for you that caused you to add the virtual_path stuff into this PR? As far as I can tell, virtual_path already gets set correctly in almost all cases; the only one where it doesn’t is when using render :widget (or possibly also render :inline) from a controller. The consequence of not having virtual_path set there is that if you actually change the code in the widget you’re rendering with render :widget, things won’t cache-bust properly, and you might still get the old cache contents. But perhaps there’s another case that I’m totally missing.
Discussion: I just discovered a giant piece of madness in Rails I didn’t even realize existed — this code. In short, it tries to use regular expressions on ERb template files to build a dependency tree for a view. The goal is to add the hashes of a view template, and every template that view template calls, recursively, to the cache digest used in the cache call. The net result is that if you use Rails’ fragment caching, and you change either the underlying view or any of the views it calls, recursively, the cache gets busted (because the key changes) and things work properly. This can matter both in development mode (most common) but also in production, if you’re (a) using a persistent store like Memcache and (b) don’t in any other way invalidate it on each deploy.
There are a couple of problems with this. Generic to Rails, this kind of “dependency tracking” is very far from perfect, since it’s using regular expressions to parse code. It’ll catch common patterns like changing a partial you call from your template, but it definitely won’t catch things like calls to helpers that are defined elsewhere, and so on. Specific to Fortitude, in order to have this sort of dependency tracking work properly, someone would need to write code that tried to parse Fortitude widgets to determine dependencies. This is probably a significantly more difficult task than it is for ERb. (Ruby syntax is more flexible than ERb, there are more ways to invoke other widgets than rendering partials, Fortitude code is going to be more highly factored — which is part of the whole point — and so on.) I think I read something about Ruby exposing its own AST to other Ruby code more easily in recent versions, so maybe that could be used? — but it still seems like quite a task.
Currently, I’m disinclined to try to tackle that whole bag of worms. I think the result would be something that would “mostly work” — which, personally, is something I kind of hate in software, because it’d work often enough you’d tend to forget about it, but, when it failed, the kinds of bugs it causes can be really hard to track down, and you wouldn’t stop to think about this as a potential cause for quite some time. The ROI just doesn’t seem to be there. It’s much cleaner just to tell people “don’t turn on caching in development, or, if you do, you have to clear the cache manually when you change templates; in production, make sure you bust the cache on every deploy”. That’s honestly something you really need to do to get 100% correct results using ERb fragment caching anyway.
Coming back to your original proposal — what I’d love to do is to sort out any remaining virtual_path issues and put that into Fortitude core. This would then make it really easy to build a fortitude-caching gem on top of the core that would add any kind of syntax anyone desires to make widgets cacheable automatically.

I agree with you about dependency tracking, and not trying to implement it for Fortitude. I think that would quickly turn into a losing battle for the reasons you mention.
I'll look into your virtual_path question, but I remember it being vital for everything that I implemented.

I'm having a lot of trouble getting my test suite to work properly, as well as getting this PR up-to-date with master, but I'm pretty convinced that the virtual_path stuff needs to be in here. If it's not set in Fortitude, where else would it be set?

Re: test suite — let me know if I can help. I saw the issue you open/closed around bundler exec, but happy to help with anything else.
Re: virtual_path — it gets set on the ActionView::Template here. Locally, I just put a puts in CacheHelper#fragment_name_with_digest to print out the virtual_path it was using. The only way I ended up with a nil virtual_path is if I was using render :widget directly from a controller. (These were all tests with Rails <IP_ADDRESS>.)
There is something slightly tricky that goes on here — it doesn’t change the outcome, but it’s worth understanding.
Under ERb, due to all the weird instance-variable copying that happens, @virtual_path will be set directly in a view (e.g.,
<%= @virtual_path %>
 will show you what it’s set to), because your ERb code gets compiled up into a method that gets splatted onto an instance of an anonymous subclass of ActionView::Base.
Under Fortitude, your widget class is much “cleaner” — it’s a completely separate object, and thus @virtual_path will be nil. However, when you call helpers (like cache), they get delegated back to that instance of an anonymous subclass of ActionView::Base, and so have access to things like @virtual_path, and thus should “just work”.
I’m not aware of any place where this actually breaks something, but it’s worth noting in case it makes a difference…

Gotcha!
I suspect then, that the issue is that I'm calling include ActionView::Helpers::CacheHelper inside of lib/fortitude/widget/caching.rb, which means that when cache is called, it's no longer delegating to the anonymous subclass, and doesn't have access to @virtual_path. Would that make sense?

Ah, excellent. That does make sense.
You shouldn’t actually need to include CacheHelper at all — helpers should be available to you automatically in any Fortitude widget.
If you remove that line, does it actually break? If so, how?

I will have to get back to you on this, once I fix these broken tests :)
On Mon, Oct 17, 2016 at 11:51 AM, Andrew Geweke<EMAIL_ADDRESS>wrote:

Ah, excellent. That does make sense.
You shouldn’t actually need to include CacheHelper at all — helpers
should be available to you automatically in any Fortitude widget.
If you remove that line, does it actually break? If so, how?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ageweke/fortitude/pull/54#issuecomment-254298168, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABNiLXU63mTLEhev9VVGgcybotSV_ovgks5q08OZgaJpZM4KBDUQ
.

--
Adam Becker
(951) 9-BECKER
@AdamJacobBecker

OK, I've got my dev environment back to normal, and I just rebased this branch on top of master.
As we expected, everything works fine when I remove include ActionView::Helpers::CacheHelper.
The only question left is: when a widget is rendered via render widget:, and that widget has the cachable directive, what is the expected behavior? Should it throw an error? If so, I'm not sure how to check for the absence of @virtual_path, since only the helpers have access to it.

OK, awesome! Glad to hear it.
Re: render :widget and cacheable…it’s really up to you. Without @virtual_path set, Rails caching does still work, and works fine; the only difference seems to be that since it doesn’t know what view you’re rendering, it doesn’t do the view-digesting magic that it otherwise does. The net result of this is that it’ll cache, but, if you change any of the code in the widget for render :widget, it won’t bust the cache, and you’ll get the old, cached view data instead.
If it were me, I’d simply accept this behavior as fine, and document it, since it’s a pretty edge case — and probably mostly applies to development mode, where view caching is disabled by default anyway.
The alternative would be to check for the presence of @virtual_path and do something different (raise an error?) if it’s not set. The easiest way to do that would be to have a caching gem add its own internal Rails helper (_fortitude_caching_get_virtual_path) that simply returns @virtual_path (this would need to be in a legit Rails helpers file, not something mixed into a Fortitude class). You could also do it by saying invoke_helper :instance_variable_get, "@virtual_path" from within a widget, which actually ought to do the same thing.
You probably have a better idea than I do what the right path is, though — you’re using render :widget much more than I ever have.
In fact, if you have a few, I’d be curious to know what causes you to use render :widget instead of separate view files — always useful to understand better what people’s use cases are.

With regard to busting the cache, I you're assuming that the cache will usually be manually cleared during a deploy? (Correct me if I'm wrong.)
With Rails fragment caching, I believe the recommended behavior is not to do that, since you want to have as warm of a cache as possible.
As for render widget:, we don't actually use it, although we do use Widget::Foo.to_html a bit. (Although now that Rails 5 has ApplicationController.render, we could use that, which would populate @virtual_path correctly.)
My main concern is that we make some mistake and use cachable when @virtual_path is nil, and we don't realize that the view isn't being digested until we start seeing stale views in production.
I think raising an error would be appropriate, and in the case that you're aware of the fact that the template cannot be digested, and want to cache anyway, you can pass skip_digest: true as an option.
I'll take a shot at creating an external gem for this.

Hmm, I'm getting an undefined method error for the cache method when rendering a widget directly, via Views::Foo.new.to_html. I can't square this with https://github.com/ageweke/fortitude/pull/43, which seems to add the Rails helpers to every view. Any idea what's up?
I was expecting this to work:

Re: your last comment — #43 doesn't actually add the Rails helpers to every view. All it does is change it so that if Fortitude’s automatic_helper_access setting is false, you should still have access to built-in Rails helpers in your widgets — just not user-defined ones.
The issue you’re running into is one I think you’ve run into in the past. In short, the only place you can use Rails helpers is in an actual view or partial, or something else rendered via a controller action. What you’re doing with Fortitude is equivalent to doing this with ERb:
puts ERB.new("Helper is: <%= distance_of_time_in_words_to_now(Time.now - 1_000_000) %>").result(binding)

If you do that, even running in a Rails console, you’ll see it fail…for the exact same reasons as it does in Fortitude. Here’s what’s going on:
Rails helpers — despite many appearances otherwise — don’t actually exist as global methods all over Rails. Instead, what happens is that when Rails gets ready to render a view, it creates this magic “context” object — an instance of an anonymous subclass of ActionView::Base, which I’m going to call the “view rendering object”. Depending on various settings (the helper_method method on a controller, the include_all_helpers flag, and so on), it then mixes in various modules full of helpers into this view rendering object. It then uses the view rendering object as the “binding” for ERb code — that is, your ERb view code gets compiled into the view rendering object and run from there. That’s why ERb views have access to those helpers. Fortitude is slightly different in that your Fortitude widget is a separate class, but there’s method_missing magic to delegate helpers automatically to the view rendering object.
Critically, it’s important to note that there is no such thing as a “global” or “generic” view rendering object, nor could there be. There are at least two reasons for this: (a) exactly which helpers end up in that object depends on the exact controller/action you’re executing; and (b) some helpers require additional context to be set on that object — like @controller, for example — to work properly. In particular, all the helpers that generate URLs (like the really-old url_for, and the newer _path, _url methods) require access to @controller to grab the current request and extract the host/protocol/port from it — this is how Rails can generate full URLs without being told explicitly what host/protocol/port it’s running on, and even work properly via proxies, multiple hostnames, etc.
Above, you’re trying to render a view without a view rendering object. Under the scenes, Fortitude notices this, and ends up using a new bare Object instead, since it has nothing else to fall back on. If you could get a hold of a view rendering object, you could easily pass one in:
Views::Test.new.to_html(Fortitude::RenderingContext.new(delegate_object: my_view_rendering_object))

…and it would all “just work”. This is just like doing in ERb:
puts ERB.new("Helper is: <%= distance_of_time_in_words_to_now(Time.now - 1_000_000) %>").result(my_view_rendering_object.send(:binding))

If you really need to render lots of widgets outside the context of a Rails controller/action, it’s probably possible to gin up a fake view rendering object that does a “good enough” job, and pass that in…but it’s never going to be perfect; for example, what would it use for that host/port on the incoming request, since there isn’t an incoming request? To me, the gotchas are too big to make Fortitude hack together one of those itself, since it’d always be a pretty gross hack of some kind.
This is very clearly something I need to put into the Fortitude FAQ — I believe jdickey ran into the exact same issues. It’s a subtle and tricky set of issues, and not at all obvious to nearly anybody since it’s almost always covered up by Rails’ internal magic.
I hope this makes sense, and outlines why you’re running into that issue. One question — what’s the reason for trying to render using a bare #to_html? That method’s really intended for use by folks not running via Rails at all…

Re: caching and @virtual_path. I’ve been thinking about this one quite a bit.
The problem of stale views is going to be there, unfortunately, no matter what you do. Even with ERb, helper methods and various unusual ways of invoking partials (and probably other stuff, too) is going to go undetected by that (IMHO very janky) DependencyTracker, and you’re going to have cache-invalidation headaches already. With Fortitude they’re worse, because it can’t track child dependencies at all.
Ironically, I’m actually reluctant to worry about @virtual_path too much exactly because setting it only takes you from “pretty damn broken caching” to “only slightly less broken caching”. To me, a cache that I understand completely only busts when I manually change the key is actually much better than a cache that “mostly invalidates correctly, but a small fraction of the time doesn’t”. The former puts worrying about cache invalidation front and center into your hands, while the latter pretends to be magic but actually bites you in the butt in some horribly hard-to-reproduce ways (like when a critical change gets made inside a helper method, and so the tracker doesn’t pick it up).
However, when you build your gem, this can be completely under your control. All you need to do is add a cache method on some widget class or module you mix in, and it can look something like this:
def cache(*args, &block)
  raise "No @virtual_path!" unless shared_variables[:virtual_path]
  super(*args, &block)
end

…and there you go. shared_variables is a Fortitude method that gives you direct access to what you’d reference as @foo in ERb by indexing it as a Hash instead.
Last, crazy crazy crazy idea:
I realized that there’s a way of building dependency tracking for caching in Fortitude that’s actually probably at least as good as ERb, if not better, and is a lot less gross. Basically, in order for any Fortitude widget to get rendered, it needs a RenderingContext. (Methods like to_html can take one, and create an empty one if you don’t pass one in.) That object gets #start_widget!(widget) and #end_widget!(widget) called on it whenever a new widget is rendered, all the way down through partials or anything else.
So, it’d be easy enough to create a subclass of RenderingContext that simply records all of the classes of all the widgets invoked during the rendering of a view, turns that back into filenames through obvious string manipulation, and then uses that as the dependency set. Seems to me that’s a lot cleaner than using regular expressions on the source text. However, it’s still far from perfect: if, for example, a widget sometimes calls a partial Foo and sometimes doesn’t, then, depending on which invocation you’re tracing, you may or may not pick up that dependency. (In the end, I don’t remember enough of my CS Theory to prove that this is basically the halting problem and therefore impossible in the general case…but I’m pretty sure it is. ;)

Thanks for the patient explanation. (Again?)
This certainly makes sense. I'm really embarrassed that after working with Rails for years, there is still magic like this that trips me up time and time again.
Here's a v1 of the fortitude-caching gem: https://github.com/dobtco/fortitude-caching.
I was already working on this when you posted your last comment, so give me a little while to read it and digest :)

Whoops, I got confused…I’d explained that bit of madness to other people before in different threads, but not you. My apologies! Take it as evidence that it trips up everyone. I certainly didn’t have any freaking clue that that’s how that stuff worked before I wrote Fortitude, and I’ve been doing Rails since 2008, so…yeah. Some of the guts of Rails is pretty crazy.


Why validate event at yii.activeForm.js submit form with forceValidate = true?

I think, if user trigger validate event on Yii form, it shouldn't be submitted? If user want to submit form it trigger submit event.
it happens if call validate method with forceValidate = true:
$('#form-id').yiiactiveForm('validate', true);

If I was write, it need to disable submitting state after validate. Need add next command at https://github.com/yiisoft/yii2/blob/master/framework/assets/yii.activeForm.js#L404:
               ...
                } else {
                    updateInputs($form, messages, submitting);
                }
            });
            if (forceValidate) {
                $(this).data('yiiActiveForm').submitting = false;
            }
        },
        ...

Additional info

Q
A

Yii version
<IP_ADDRESS>

PHP version
7.1.18-1+ubuntu16.04.1+deb.sury.org+1

Operating system
Linux Mint 18.3

What exactly is the problem? Validation and submitting must be two separate actions.

@lubosdz exactly.
But if set forceValidate = true it actual will be submitting.
I think, will be good if:

$('#form-id').yiiactiveForm('validate'); - only validation
$('#form-id').yiiactiveForm('validate', true); - validation with showing error messages
$('#form-id').yiiactiveForm('submit'); - submitting form

I don't want to submit form when I call validate action.

Well, forceValidate argument was introduced 2 years ago to solve another issue - see:
https://github.com/yiisoft/yii2/blame/02b469e8b6c037a4e028aaeaa52fdb3d9c059f24/framework/assets/yii.activeForm.js#L302


versions bump

alpine 3.7
jobber 1.3.2
only apk and pip packages.
Jobber improvements:
Support range expressions in time specs https://github.com/dshearer/jobber/issues/59
Support time expressions like "10,20" in jobber file https://github.com/dshearer/jobber/issues/65

Hello, I am preparing to integrate blacklabelops/crow as the new cron scheduler. This will be necessary to support #12.
First going to jobber 1.3 with it's new features will be counter productive. The migration to the new scheduler will be harder.

Not accepted due to Jobber 1.3.


X (close) on wallet connect modal a dead click when switching wallet providers

Overview
Currently in production, when a user goes to switch wallet providers to Wallet Connect from having another wallet connected, the Close X is a dead click.  The user must click outside of the modal if they would like to close the screen.
This is not the case when trying to close the modal if Wallet Connect is the first wallet to connect.
References and additional details
Recreation steps:

Connect a non-wallet connect wallet to app.shapeshift.com
Select 'switch wallet providers'
Select Wallet Connect as the wallet option
try to close the window by clicking the X
Witness dead click

Video of dead click:
https://github.com/shapeshift/web/assets/94998097/073f5e75-553e-4a81-a890-ff91ed8a657b
Acceptance Criteria
Wallet connect close button is functional when clicked.
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response

@purelycrickets is this still happening for you? Can't repro on upstream nor local develop
https://github.com/shapeshift/web/assets/17035424/5e78f857-b7fd-4a86-99a1-4959f5af9e27

unable to reproduce this issue any longer. good to close. thanks @gomesalexandre


Sb v2 dev progress2

This is my changes for the last sprint.  It includes buttons, icon, and collections page changes.

Please recreate with request to v2.0-sandbox


Resolve URIs with special characters correctly

Previously, model URIs were synced with typescript without encoding (uri.toString(true)), breaking resolution of URIs that had special characters in them, e.g. file:///node_modules/@some/module or file:///C:/test.js. This fix makes sure that typescript sees the correct, encoded file URIs. I've also verified that features like Peek Definition is still working with this fix.
Fixes #3281
Fixes #3236
History:
https://github.com/microsoft/monaco-editor/commit/675844ac7e5c505603d20f8391051e7eee322565 tried to introduce a fix for this problem, but only provided half the solution. This new patch still solves #2295 which was the original target for that commit, while also fixing the encoding problems entirely.

Bumping this PR as it will fix a bunch of uncaught errors that show up in console while inspecting the TypeScript playground downstream.
Any project using @typescript/ata with monaco-editor will see this issue.
Here's a TypeScript Playground repro link: https://www.typescriptlang.org/play?#code/JYWwDg9gTgLgBAbzgVwM4FMDKMCGN1wC+cAZlBCHAERTo4DGMVA3ALABQH9EAdqvAG1uyHjAC6cALwoM2POgAUABgCUbTu2Gj1QA
Inspect the page and you will see the following error:
Uncaught (in promise) Error: Could not find source file: 'file:///file%3A///node_modules/react/package.json'.
    at Ee (tsWorker.js:269:8118)
    at Object.en [as getSyntacticDiagnostics] (tsWorker.js:269:14274)
    at Um.getSyntacticDiagnostics (tsWorker.js:36129:2574)
    at S.fmr (typescript.azureedge.net/cdn/4.9.4/monaco/min/vs/base/worker/workerMain.js:22:34476)
    at o._handleMessage (typescript.azureedge.net/cdn/4.9.4/monaco/min/vs/base/worker/workerMain.js:22:18089)
    at Object.handleMessage (typescript.azureedge.net/cdn/4.9.4/monaco/min/vs/base/worker/workerMain.js:22:17714)
    at L._handleRequestMessage (typescript.azureedge.net/cdn/4.9.4/monaco/min/vs/base/worker/workerMain.js:22:14546)
    at L._handleMessage (typescript.azureedge.net/cdn/4.9.4/monaco/min/vs/base/worker/workerMain.js:22:13996)
    at L.handleMessage (typescript.azureedge.net/cdn/4.9.4/monaco/min/vs/base/worker/workerMain.js:22:13884)
    at o.onmessage (typescript.azureedge.net/cdn/4.9.4/monaco/min/vs/base/worker/workerMain.js:22:17806)

I cloned TypeScript playground locally, patched monaco-editor (particularly this change) and the error went away.


some problem with the README and the model for fashionMNIST

In the dependency part of README
I can not create the environment by the command provided.
I add some code about cuda into the model for fashionMNIST.

Merged. @hushyangqing Thank you very much!


Can't use Ruby 2.1.2. We should use Ruby 2.2.2 for this task.

When I used Ruby 2.1.2, I had a issue:
"activesupport-<IP_ADDRESS> requires ruby version >= 2.2.2, which is incompatible with the current version, ruby 2.1.2p95"

I fixed this issue by using Ruby 2.2.2.


autoconifg µc from Papyrus

In Papyrus JSON export file, replace "id": "control" by "id": "µc.ST_nucleo_F042K6"

For S4E_electron #26


all auth'd commands should optionally take the decryption-passphrase

We'd like the env information om uses for all its authorized commands to optionally include the decryption passphrase, so that if the Ops Manager has been restarted, commands can still work.
This is a little bit of a counter-intuitive or maybe too-clever idea, so we want to lay out what we're thinking very clearly.

Any time the Ops Manager VM is restarted, it needs to be decrypted before it can be used.
Ops Manager VMs may be rebooted at any time, because IaaSs
om is intended to be CI-native, that is, make design decisions that maximize it's value in a CI/pipeline/build context.
Given 1 and 2, any use of om in an automatic build will need to ensure the Ops Manager is decrypted before attempting to use it.
The decryption-passphrase is not necessarily more or less sensitive than the Ops Man login information that would ordinarily be provided as a target. It's differently sensitive; env information combines with a running Ops Manager to give up everything (or potentially not-everything, if there's RBAC or whatever), while the decryption-passphrase pairs up with an exported installation to give up everything (with no RBAC or whatever to mitigate it).

Conclusion: given 4 and 5, it would be useful for operators to have the option to provide the decryption passphrase for all om commands, so that they can make the appropriate trade-off between reliability and security for their particular context.
This also smooths out a problem in our automated upgrade workflow about which flags are in which config files.
This would remove the need for a config file for import installation, as it would be able to get the information it needs as part of the env file. The decryption passphrase could be required for this particular command.

Sounds interesting! To double check, the proposed workflow is:

the global decryption-passphrase is optional for all commands
if the OpsMgr is already running/decrypted, the decryption-passphrase is unused
if a request is made to an OpsMgr which is "locked", om will transparently unlock it if the decryption-passphrase was provided
if a request is made to an OpsMgr which is "locked" and the decryption-passphrase was not provided, raise an error

If so, sounds reasonable to me 👍

Yes, you have accurately described what we want to do.

We're going to start working on a PR for this.

We're discussing how to handle the fact that --decryption-passphrase is currently required as a command argument by import-installation.
We think ideally, we'd keep the interface consistent, and use it as a global flag - but in the case of import-installation, the typically-optional flag would be required. In this scenario, we'd remove any command-specific mention of the flag, which would be a breaking change. We might have to mention it's required for import-installation in the global description?
Alternatively, we could leave the command argument for import installation, and allow it to be "optional" if the argument has been provided as a global argument. This would have the virtue of being non-breaking, but would be kind of confusing and weird to document in the help.
Thoughts?

I'm fine with making a breaking change in this case, we'll just need to make sure to document the change in the release notes. A single global flag that is required for import-installation but optional otherwise sounds good to me.

The PR's merged! Thanks.


Signature Decoder broken. Error 403

Encrypted Videos cant be downloaded since yesterday, got Error 403, so Signature Decoder is broken.
Example Video: https://www.youtube.com/watch?v=lWA2pjMjpBs

Replace this code on SignatureDecoder.php
New code
 } else if (preg_match('@(?:\b|[^a-zA-Z0-9$])([a-zA-Z0-9$]{2,3})\s*=\s*function\(\s*a\s*\)\s*{\s*a\s*=\s*a\.split\(\s*""\s*\)@is', $js_code, $matches)) {
old code
 } else if (preg_match('@(?:\b|[^a-zA-Z0-9$])([a-zA-Z0-9$]{2})\s*=\s*function\(\s*a\s*\)\s*{\s*a\s*=\s*a\.split\(\s*""\s*\)@is', $js_code, $matches)) {

I can't replicate this issue on my end, but I can assume that this tiny change would not break any existing logic, so let's just go ahead with it
https://github.com/Athlon1600/youtube-downloader/commit/f739192fcfe63c2aeefaf7a8584cc98f62b58492

Can you get a valid link for these videos?
https://www.youtube.com/watch?v=cOlhzKPX0KU
https://www.youtube.com/watch?v=ldBroBrV6Fg
All download links give me 403 error... and some other videos have the same error.
https://youtube-downloader-v3.herokuapp.com also does not work with these videos (403).
I checked that both the new & old code can parse the function named JB:
(
[0] => JB=function(b){g.Ab(a,function(c){c(b)}
[1] => g.Ab(a,function(c){c(b)
)
don't know what is the problem.

yes, it happen because same function name coming 2 time from youtube, you can fix it replace code with new in SignatureDecoder.php
New code
 if (preg_match('/' . $func_name . '=function\([a-z]+\){(.*?)}/', $player_html, $matches)) {
Old code:
 if (preg_match('/' . $func_name . '=function\(\s*a\s*\){(.*?)}/', $player_html, $matches)) {
let me know is working or not

yes, it happen because same function name coming 2 time from youtube, you can fix it replace code with new in SignatureDecoder.php
Old code:
 if (preg_match('/' . $func_name . '=function\([a-z]+\){(.*?)}/', $player_html, $matches)) {
New code:
 if (preg_match('/' . $func_name . '=function\(\s*a\s*\){(.*?)}/', $player_html, $matches)) {
let me know is working or not

I'm getting 403 on all links, and this change did not fix it for me.

I'm so sorry. I don't check github very often. I just upgraded from v3.0.2 to v3.1.0 and it's generating links correctly now.


new entry to testimonials.rst

I've added yet another published paper to the list.

Thanks!

keep those cards and letters rolling in!


Can't build

I am running Ubuntu 17.04, I just installed stack Version 1.5.1, Git revision 600c1f01435a10d127938709556c1682ecfd694e (4861 commits) x86_64 hpack-0.17.1, stack setup installed ghc-nopie-8.0.2., but when I run stack install vgrep I get:

Error: While constructing the build plan, the following exceptions were encountered:
In the dependencies for vgrep-<IP_ADDRESS>:
aeson-<IP_ADDRESS> must match (>=0.11 && <1.0) || (>=0.9 && <0.10) (latest applicable is <IP_ADDRESS>)
needed for unknown reason - stack invariant violated.
Plan construction failed.

Set your stack resolver to lts-9.0 within ~/.stack/global-project/stack.yaml.

@kuwze Version 2.0 is not forward-compatible to Stackage LTS 9.x. I have published a release vgrep-<IP_ADDRESS> which should fix the issue, so stack update && stack install vgrep should work again.


Cow: Watch hrinternational.in

Cow requests the watch of the watch_keyword hrinternational\.in. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

hrinternational\.in has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by VLAZ in Charcoal HQ


Volume slider

Hi ! Is it possible to add the vol_nn! command to set the volume trough Home assistant. Thx for your help.

Hi. I tried but i couldn't get it to work. This esphome code almost works but i don't know how to get the volume value in the nn
number:
  - platform: template
    name: "Volume"
    min_value: 1
    max_value: 50
    id: volume_set
    step: 1
    set_action:
      then:
        - uart.write: "vol_nn!"

I created some buttons for myself with some fixed values:
  - platform: template
    name: "Set volume to 15"
    icon: "mdi:fast-forward-15"
    on_press:
      - uart.write: "vol_15!"

Hope this helps.


[Enhancement] Support qobuztitle

Closed with https://github.com/GioF71/upmpdcli-docker/commit/f7ec64f947f1ead0c77fd4d9d86e60e594009388


[Details Nerdlet] Move quickstart logo and CTAs, make header sticky

We want the CTA buttons for quickstarts to remain visible to users even after they scroll.
AC

[ ] (logo + name + main CTA) are in a sticky header and as the user scrolls down, they can access the main actions at any given time.
[ ] Logo moves to the left
[ ] CTA buttons move to the right
[ ] Measure before and after for data analysis so we understand the impact of this change + / -

Design

Looks like we got a couple small requests for adjusting the design. Once those are done and merged in this should be good to goooo!


node: fix race in access to lastSavedState

Current coverage is 53.62% (diff: 0.00%)

Merging #1538 into master will decrease coverage by 0.16%

@@             master      #1538   diff @@
==========================================
  Files            82         82
  Lines         13430      13435     +5
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           7224       7204    -20
- Misses         5225       5243    +18
- Partials        981        988     +7

Powered by Codecov. Last update 675f0f4...a6ea78b

Shouldn't all of save run with the lock held? It doesn't seem like a good idea to have two concurrent saves running to the same file.

@aaronlehmann @stevvooe Yeah, I think issue is not holding lock in Remove. I've pushed changes.

LGTM


Toolkits now work as tools

Toolkits now can be connected to Agents to be used as tools.

Is there something wrong for loading.py
def instantiate_toolkit(node_type, class_object, params):     loaded_toolkit = class_object(**params)     # Commenting this out for now to use toolkits as normal tools     # if toolkits_creator.has_create_function(node_type):     #     return load_toolkits_executor(node_type, loaded_toolkit, params)     if isinstance(loaded_toolkit, BaseToolkit):         return loaded_toolkit.get_tools()     return loaded_toolkit
It would make root node no longer an valid agent in test data "Openapi.json" when return tool list


Added a few translations

I only have text changes, so I'm guessing they are not the cause of the build failing.

Thanks, @SuperPranx!


Dragging a class to change superclass gets nil DNU #notEmpty

#moveClass:toSuperclass: creates a ClassBuilder without setting instanceVariables. ClassBuilder>>setInstanceVariablesOf: used to contain a nil-check, but this disappeared when switching to array storage of inst vars and creating ClassDescription>>setInstanceVariables:. It does optimize for the no-inst-vars case by storing nil instead of an empty array, but this gets an error if the argument is already nil. Note, the old and new superclass must have different inst vars (#instanceVariablesAreBeingChanged must answer true) for the problem to occur.
Does it seem reasonable to just add a nil-check to #setInstanceVariables:, e.g. instanceVariables := (aCollection isNil or: [aCollection isEmpty]) ifFalse: [aCollection]? Or should the nil-check be in #setInstanceVariablesOf: as before, and avoid calling #setInstanceVariables: at all if the argument would be nil? (This is how it was in D6, and seems strange, but I'm not clear on the context and possible implications...)

Wouldn't the best fix here be:
ClassBuilder>>setInstanceVariablesOf: aClass
...
    aClass setInstanceVariablesOf: **self** instanceVariables

?
Again there is a test hole though.

D'oh! I don't know how I didn't see that method. I used that fix and added tests—see pull #273.


Fix documentation

[Enter feedback here]
In my opinion, the documentation on this page is not clear. It is making hard for developers to understand how the nullable contexts works. It needs to be organized a bit more logically.
First the page have to specify what problem is with examples.
Then how it is fixed, why there are annotation and warning contexts, what are they and why developer need to care about them. Also more examples here. As the page stands now the possible values enable and disable are given even before we can understand what they mean.
The details of the values for the context and their combinations should be provided at the end, with more examples.
More in detail. These are some point that I find confusing:

In the first section, it is not made clear if this warnings provided by the compiler are the default behaviour or if they happen when enabling annotations, warnings or both.
The intro is jumping between the previous and the new compiler behaviour explanation in an unclear way, I would use past and present tenses and the words "previous/old" and "new".
It is not clear how a type can become oblivious or unknown. An example would be useful.
The section Nullable contexts section is not providing an actual definition of both context. What is the intention to provide both?
It is mentioned that the forgiving operator cannot be used in a disabled annotation context. I can use the operator without any error, so I guess it is an error.
It is mentioned that the compiler will show warnings when the annotation context is enabled. Does this happen even if the warning context is disabled? It is not very clear.

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

ID: a690704d-da32-dca7-ea3e-66b84fb1d00d
Version Independent ID: 11f314de-dd3a-362e-b2bb-d0a2133cfc7b
Content: Nullable reference types
Content Source: docs/csharp/nullable-references.md
Product: dotnet-csharp
Technology: csharp-null-safety
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Thanks for taking all these notes @ldwedari They provide a great roadmap for updating this article.
I've added this to the next sprint to address.


Fix path to TestShop.AppHost in contributing.md

Description
The instructions in contributing.md for running the TestShop AppHost project had an incorrect path. I corrected the documentation with the correct path so that the instructions are accurate.
Fixes #6479
Checklist

Is this feature complete?

[x] Yes. Ready to ship.
[ ] No. Follow-up changes expected.

Are you including unit tests for the changes and scenario tests if relevant?

[ ] Yes
[x] No

Did you add public API?

[ ] Yes

If yes, did you have an API Review for it?

[ ] Yes
[ ] No

Did you add <remarks /> and <code /> elements on your triple slash comments?

[ ] Yes
[ ] No

[x] No

Does the change make any security assumptions or guarantees?

[ ] Yes

If yes, have you done a threat model and had a security review?

[ ] Yes
[ ] No

[x] No

Does the change require an update in our Aspire docs?

[ ] Yes

Link to aspire-docs issue:

[x] No

Microsoft Reviewers: Open in CodeFlow

Thank you for the PR!


Minimap git-diff

Current colours do not match the theme ones.

This is related to the fact that the theme currently does not support the minimap-git-diff package.
I'll try to add it this evening for all theme variants.

Sorry for the long waiting period, but I've been busy on my job (one week SCRUM sprints are hectic :smile: ).
I've already implemented it, but it's not yet merged for the next release.
You can checkout the latest codebase to test it.
I'll merge it next weekend along with the support for #3 (react package)

Implemented support in v0.18.0.

Thanks it works, like it that the green and red are very light on the minimap.


Docker image creation fails for julia 1.9

Hello everyone,
I'm running a Docker where I use OpenSSL as a dependency. Unfortunately, I cannot update to Julia 1.9 since the system image creation fails due to a line in OpenSSL.jl. Every other (older) Julia version works perfectly fine.
The line 508 in OpenSSL.jl for the call of the version number fails:
@static if version_number() ≥ v"3"

Leads to the following error, originally coming from GoogleCloud.jl:
Step #5: ERROR: LoadError: could not load symbol "OpenSSL_version_num":
Step #5: /usr/local/julia/bin/julia: undefined symbol: OpenSSL_version_num
Step #5: Stacktrace:
Step #5:   [1] version_number()
Step #5:     @ OpenSSL ~/.julia/packages/OpenSSL/8wxMC/src/OpenSSL.jl:495
Step #5:   [2] top-level scope
Step #5:     @ none:1
Step #5:   [3] eval(m::Module, e::Any)
Step #5:     @ Core ./boot.jl:370
Step #5:   [4] var"@static"(__source__::LineNumberNode, __module__::Module, ex::Any)
Step #5:     @ Base ./osutils.jl:19
Step #5:   [5] include
Step #5:     @ ./Base.jl:457 [inlined]
Step #5:   [6] _require(pkg::Base.PkgId, env::String)
Step #5:     @ Base ./loading.jl:1836
Step #5:   [7] _require_prelocked(uuidkey::Base.PkgId, env::String)
Step #5:     @ Base ./loading.jl:1660
Step #5:   [8] macro expansion
Step #5:     @ ./loading.jl:1648 [inlined]
Step #5:   [9] macro expansion
Step #5:     @ ./lock.jl:267 [inlined]
Step #5:  [10] require(into::Module, mod::Symbol)
Step #5:     @ Base ./loading.jl:1611
Step #5:  [11] include
Step #5:     @ ./Base.jl:457 [inlined]
Step #5:  [12] _require(pkg::Base.PkgId, env::String)
Step #5:     @ Base ./loading.jl:1836
Step #5:  [13] _require_prelocked(uuidkey::Base.PkgId, env::String)
Step #5:     @ Base ./loading.jl:1660
Step #5:  [14] macro expansion
Step #5:     @ ./loading.jl:1648 [inlined]
Step #5:  [15] macro expansion
Step #5:     @ ./lock.jl:267 [inlined]
Step #5:  [16] require(into::Module, mod::Symbol)
Step #5:     @ Base ./loading.jl:1611
Step #5:  [17] include(mod::Module, _path::String)
Step #5:     @ Base ./Base.jl:457
Step #5:  [18] include(x::String)
Step #5:     @ GoogleCloud ~/.julia/packages/GoogleCloud/cyJtU/src/GoogleCloud.jl:4
Step #5:  [19] top-level scope
Step #5:     @ ~/.julia/packages/GoogleCloud/cyJtU/src/GoogleCloud.jl:17
Step #5:  [20] include
Step #5:     @ ./Base.jl:457 [inlined]
Step #5:  [21] _require(pkg::Base.PkgId, env::Nothing)
Step #5:     @ Base ./loading.jl:1836
Step #5:  [22] _require_prelocked(uuidkey::Base.PkgId, env::Nothing)
Step #5:     @ Base ./loading.jl:1660
Step #5:  [23] _require_prelocked
Step #5:     @ ./loading.jl:1658 [inlined]
Step #5:  [24] macro expansion
Step #5:     @ ./lock.jl:267 [inlined]
Step #5:  [25] require(uuidkey::Base.PkgId)
Step #5:     @ Base ./loading.jl:1655
Step #5:  [26] top-level scope
Step #5:     @ /tmp/jl_Yl6PGfGrqb:36
Step #5: in expression starting at /root/.julia/packages/OpenSSL/8wxMC/src/OpenSSL.jl:508

Unfortunately, I cannot reproduce this for a normal precompilation and I therefore don't know how to provide a MWE.
As a similar issue occurred for the Unitful.jl package earlier, I guess this is somehow related to to this MR.
Is there any way we can fix this?

This was actually an issue with the PackageCompiler. Julia 1.9 seems to need PackageCompiler version to be ^2.0.0.


dynamic  graph with different edges and nodes on the time dimension

❓ Questions & Help

Hello~, recently I meet some question about the dynamic graph on the time dimension. Is there any solution for this. Looking forward to replying.

For dynamic graph learning, we provide an example using ReNet on two datasets, although many other approaches should be straightforward to implement.

thanks very much. Hope this repo become stronger!

Hi, is there a more generative example for this purpose? To the best of my understanding, the output of ReNet in PGL remains the identical shape through time, which is not a graph structured data. I am wondering how to process the dynamic graph for regular GNN, such as GAT, to produce a graph structured data as well?


Return carousel items for albums

Currently, items in an album are not returned in the feed, this small tweak fixes that. Album items are accessible from the carouselMedia property.

good job


Failed to copy downloaded flutter_engine.dll

Hover doctor

D:\code\flutter\office_tools>hover doctor
hover: Hover version v0.46.3 running on windows
hover: Sharing packaging tools
hover: darwin-bundle is supported
hover: Packaging darwin-dmg is not supported on windows
hover: To still package darwin-dmg on windows you need to run hover with the `--docker` flag.
hover: Packaging darwin-pkg is not supported on windows
hover: To still package darwin-pkg on windows you need to run hover with the `--docker` flag.
hover: Packaging linux-appimage is not supported on windows
hover: To still package linux-appimage on windows you need to run hover with the `--docker` flag.
hover: Packaging linux-deb is not supported on windows
hover: To still package linux-deb on windows you need to run hover with the `--docker` flag.
hover: Packaging linux-pkg is not supported on windows
hover: To still package linux-pkg on windows you need to run hover with the `--docker` flag.
hover: Packaging linux-rpm is not supported on windows
hover: To still package linux-rpm on windows you need to run hover with the `--docker` flag.
hover: Packaging linux-snap is not supported on windows
hover: To still package linux-snap on windows you need to run hover with the `--docker` flag.
hover: To package windows-msi these tools are required: candle
hover: Install the WiX Toolset from https://wixtoolset.org/releases/
hover: To still package windows-msi without the required tools installed you need to run hover with the `--docker` flag.
hover:
hover: Sharing flutter version
Flutter 2.2.2 • channel stable • https://mirrors.tuna.tsinghua.edu.cn/git/flutter-sdk.git
Framework • revision d79295af24 (2 weeks ago) • 2021-06-11 08:56:01 -0700
Engine • revision 91c9fc8fe0
Tools • Dart 2.13.3
hover: Flutter engine commit: https://github.com/flutter/engine/commit/91c9fc8fe011352879e3bb6660966eafc0847233
hover: ⚠ The go-flutter project tries to stay compatible with the beta channel of Flutter.
hover: ⚠     It's advised to use the beta channel: `flutter channel beta`
hover: Finding out the C compiler version
hover: Sharing the content of go.mod
module office_tools/go

go 1.16

require (
        github.com/go-flutter-desktop/go-flutter v0.43.0
        github.com/pkg/errors v0.9.1
)
hover: Sharing the content of hover.yaml
application-name: ""
executable-name: ""
package-name: ""
organization-name: com.officetools
license: ""
target: lib/main_desktop.dart
branch: ""
cache-path: ""
opengl: ""
engine-version: ""
hover: Sharing the content of go/cmd
go\cmd\main.go  go\cmd\options.go

D:\code\flutter\office_tools>

Error output

D:\code\flutter\office_tools>hover run
hover: Downloading engine for platform windows-debug_unopt at version 91c9fc8fe011352879e3bb6660966eafc0847233...
Download completed in 1.09s
hover: zip: not a valid zip file
Download completed in 0.78s
hover: zip: not a valid zip file
hover: Failed to copy downloaded flutter_engine.dll: CreateFile C:\Users\LIUD~1.H\AppData\Local\Temp\hover-engine-download548538291\engine\flutter_engine.dll: The system cannot find the path specified.

D:\code\flutter\office_tools>

I want to try file_picker  plugin in a flutter project, so I followed the instructions on https://github.com/go-flutter-desktop/hover#getting-started-with-an-existing-flutter-project and https://github.com/miguelpruivo/flutter_file_picker/wiki/Setup#--desktop-go-flutter.
However when I tried to execute hover run, I got the above errors.

Fixed in latest hover version


Fix formatting issues

Fixes legacy &a in ping indicator for remote DBs in /lp info (#2670)

Returns the prefix back to it's old Aqua/Dark Aqua

Thanks!


nrnivmodl-core: adding -n name and dropping install script

Install script was transformed into a config file being saved/loaded

Please retest

@ferdonline : Jenkins Pipeline:
[ 16%] Built target cudacoreneuron
[ 21%] Built target scopmath
[ 22%] Linking CXX static library ../lib/libcoreneuron.a
Running nrnivmodl-core with halfgap.mod
# nrnivmodl-core options. Mods location: /jenkins/06/workspace/oss.coreneuron.pipeline/tests/integration/ring_gap/mod
params_NMODL_BINARY=/jenkins/06/workspace/oss.coreneuron.pipeline/build_GPU-non-unified/bin/mod2c_core
params_INCFLAGS=-I/jenkins/06/workspace/oss.coreneuron.pipeline -I/jenkins/06/workspace/oss.coreneuron.pipeline/build_GPU-non-unified/include
/jenkins/06/workspace/oss.coreneuron.pipeline/build_GPU-non-unified/bin/nrnivmodl-core: line 60: -I/jenkins/06/workspace/oss.coreneuron.pipeline/build_GPU-non-unified/include: No such file or directory
make[2]: *** [lib/libcoreneuron.a] Error 1
make[2]: *** Deleting file `lib/libcoreneuron.a'
make[1]: *** [coreneuron/CMakeFiles/coreneuron.dir/all] Error 2
make: *** [all] Error 2

retest this please

@ohm314 It seems I dont have right on this repo (?)


Xcode build error

Libraries/Plugins/iOS/GADURequest.h:3:1: error: use of '@import' when modules are disabled
@import Foundation;

Forgot to add the GoogleMobile framework 7.x to Xcode.
Surprised that it's not part of the plugin here


pejman

Problem encountered on https://dotnet.microsoft.com/en-us/learn/aspnet/blazor-tutorial/run
Operating System: windows
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

what error message do you get @pejmanZRA ? Please provide some more details.


[Core core-auth] Missing Readme Headers

As part of readme verification, we would want all headers to have required sections. The package core core-auth is missing the following sections:
^Getting started$
^Key concepts$
^Examples$
^Troubleshooting$
^Next steps$
Refer issue : #1583
The packages should have following headers:
Azure .+ client library for JS
^Getting started$
^Key concepts$
^Examples$
^Troubleshooting$
^Next steps$
^Contributing$

Once fixed, remove the exception for this package from https://github.com/Azure/azure-sdk-for-js/blob/master/eng/.docsettings.yml


Creating new branch failed

[I'm supposed to describe steps to replicate my issue here and if I don't do that, I understand that my issue will be probably ignored.]

Brackets 1.4.0-16380 (linux), Git 1.9.1 & Brackets-Git 0.14.32
Creating new branch failed
Error: fatal: A branch named 'modificandojs' already exists.

call: git checkout -b modificandojs modificandojs
Error: fatal: A branch named 'modificandojs' already exists.
    at Object.exports.toError (file:///home/tsalgado/.config/Brackets/extensions/user/zaggino.brackets-git/src/ErrorHandler.js:162:19)
    at NodeConnection.<anonymous> (file:///home/tsalgado/.config/Brackets/extensions/user/zaggino.brackets-git/src/Cli.js:185:44)
    at j (file:///opt/brackets/www/thirdparty/thirdparty.min.js:559:26911)
    at Object.k.fireWith (file:///opt/brackets/www/thirdparty/thirdparty.min.js:559:27724)
    at NodeConnection._receive (/utils/NodeConnection.js:498:34)

A branch named 'modificandojs' already exists.

Note to self, make sure A branch named 'modificandojs' already exists. is properly parsed out of git and shown to user as user error.


add fmm.org.br

@weblerson First stage of verification passed, official domain is fundacaomatiasmachline.org.br as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision. Proof of domain ownership: https://www.fundacaomatiasmachline.org.br/webmail/

@philipto the domain of the site is fundacaomatiasmachline.org.br, but our academic email use fmm.org.br
proof of domain ownership:

thanks for tour reply!

@weblerson  Thank you for the clarifications. Pull request merged.


Show completed tasks?

In your documentation you said you could toggle on showing completed tasks. I'm a complete newbie to Jekyll, could you explain how to toggle this on or off? I like to see the progress and show tasks that have been completed already. Thanks.

Sorry for not responding earlier. Indeed the feature has been removed from the current version. The tasks that are marked as completed - [x] will automatically be invisible and there is currently no switch to make them visible again. I will have to fix this in the next update.
For now, you can  easily avoid this behaviour by setting the css  style for completed tasks. to do this, edit file _scss/_base.scss in line 361 by removing the  lines max-height: 0; and overflow: hidden; :
      &.box_done {
        font-style: normal;
        font-size: $base-font-size * 1.2;
        color: $grey-color;
        text-decoration: line-through;
        max-height: 0;
        overflow: hidden;

        &:before {
          font: normal normal normal $base-font-size lablogIcons;
          padding-top: 0.5em;
          content: "\f046";
          color: $grey-color;
        }
      }

Then, completed tasks will be visible and clearly labelled as being completed.


Is dump.cs only metadata?

In the dump.cs, I can see the classes and their declarations, but not the implementation for the methods

Is this supposed to happen? Any way to get the full decompiled code?

You might need to use IDA or Ghidra to fully read the code or implementation.


I have installed ionic2' CLI,now ionic serve does't work in a new ionic2 project

From @yangheng on February 19, 2016 2:24
I have installed ionic2' CLI,now ionic serve does't work in a new ionic2 project
In ionic2 project, ionic serve does't work.while i try start a ionic1 project and cd &,ionic serve works !! What's matter ?
Ionic Version: 2.x
Browser & Operating System: Chrome
Run ionic info from terminal/cmd prompt:
Cordova CLI: 5.3.1
Gulp version:  CLI version 3.9.0
Gulp local:
Ionic Version: 2.0.0-beta.1
Ionic CLI Version: 2.0.0-beta.17
Ionic App Lib Version: 2.0.0-beta.8
ios-deploy version: 1.7.0
ios-sim version: 5.0.1
OS: Mac OS X El Capitan
Node Version: v0.12.7
Xcode version: Xcode 7.2.1 Build version 7C1002

Copied from original issue: driftyco/ionic#5521

When you say 'doesn't work' what do you mean? Are there any errors?

No errors !  In ionic1 project ,the chrome browser will start and load index.html after type "ionic serve",however there's nothing in ionic2 project and no errors.
The terminal like this :
root$ ionic serve
root$

Try cleaning up node and cordova and re-install the cli and the node-modules, here's my default alias for that:
type uionic
uionic is aliased to `rm -rf node_modules www/build platforms && npm uninstall -g ionic && npm uninstall -g cordova && npm cache clean && npm i -g cordova ionic@beta && npm i'

Hello all! As it seems it has been a while since there was any activity on this issue i will be closing it for now. Feel free to comment if you are still running into this issue. Thanks for using Ionic!


SlideOver appearance animation

Package
filament/filament
Package Version
v2.16.19
Laravel Version
v9.33
Livewire Version
v2.10.7
PHP Version
v8.1.3
Problem description
Slideover spawn animation starts from the left
Video:  https://www.dropbox.com/s/qxw0s3saeziq5gq/111.mov?dl=0
Expected behavior
Slideover spawn animation starts from the right
Steps to reproduce
Add to page action slideOver() methode
Reproduction repository
https://github.com/not-link
Relevant log output
No response

I can't reproduce this myself, and you've given no reproduction repository or code examples.

I can confirm that this does happen sometimes. I do not know why. But I did change this in the modal:
x-show="isShown"
x-transition:enter="duration-300"
x-transition:leave="duration-300"
@if ($width === MaxWidth::Screen)
@elseif ($slideOver)
       x-transition:enter-start="translate-x-full rtl:-translate-x-full"
       x-transition:enter-end="translate-x-0"
       x-transition:leave-start="translate-x-0"
       x-transition:leave-end="translate-x-full rtl:-translate-x-full"
@else

To this:
x-show="isShown"
x-transition:enter-start="duration-300"
x-transition:enter-end="duration-300"
x-transition:leave-start="duration-300"
x-transition:leave-end="duration-300"
@if ($width === MaxWidth::Screen)
@elseif ($slideOver)
       x-transition:enter-start="translate-x-full rtl:-translate-x-full"
       x-transition:enter-end="translate-x-0"
       x-transition:leave-start="translate-x-0"
       x-transition:leave-end="translate-x-full rtl:-translate-x-full"
@else

Which is pretty much the same right? But it causes the issue to go way.

Can you make a PR please @andrewdwallo?

Yeah sure!

@danharrin I noticed the issue occurred specifically when having an href element inside the modal, if that tells you anything of what  might be causing it. But here is more info in the meantime: https://discord.com/channels/883083792112300104/1138244989495824495/1193704489044168866


Add aria-describedby for 'Change' links in work history

Context
From our external accessibility audit it was noted that when we have Change links on review sections that consist of multiple entries, e.g. work history, they are not unique and descriptive which makes it difficult for screen readers users to identify the destination or purpose of the link out of context.
Following discussions, to improve the accessibility we decided that adding aria-describedby that includes a description of the job and the dates will uniquely identify and describe a job role. See https://ukgovernmentdfe.slack.com/archives/CPACU8GUF/p1578310497004300 for more detail.
As there are a number of other pages that have this issue, work history is the only one that is addressed so that a valid solution can be establish first. Further PRs will be made to fix the other pages.
Changes proposed in this pull request
This PR adds aria-describedby for Change links in work history.  In order to do this ids needed to be created for the value cell of the 'Job' and 'Dates' row of an entry so that they can be referenced in the aria-describedby.

Guidance to review
The implementation of this feels weird. Feels like there's a better way to do this. Recommendations are more than welcome! Pliz and tenk u.
Link to Trello card
https://trello.com/c/XsqlA0hu/698-dac-page-33-add-hidden-content-to-change-links-on-work-history-review-and-other-pages
Things to check

[x] This code doesn't rely on migrations in the same Pull Request
[x] API release notes have been updated if necessary
[x] New environment variables have been added to the Azure config

This looks great 💯
Do we need this for volunteering experience section too?
What about references?
Do you have an example screenreader output?

This looks great 💯
Do we need this for volunteering experience section too?
What about references?

Yush, we need to do those as well. Just wanted to address one section first so that we could establish an implementation before fixing the others. Will be doing those in a future PR or PRs.


sw-6660 adding guidance header #minor

Codecov Report
Patch and project coverage have no change.

Comparison is base (3353f54) 72.18% compared to head (5d9c94b) 72.18%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #366   +/-   ##
=======================================
  Coverage   72.18%   72.18%
=======================================
  Files          27       27
  Lines        1330     1330
=======================================
  Hits          960      960
  Misses        313      313
  Partials       57       57

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


[MINOR] fix violations of Sonarqube rule java:S2184

Hello,
This PR fixes 4 violations of Sonarqube Rule java:S2184 : 'Math operands should be cast before assignment'.
For more details, please see
MITRE, CWE-190 - Integer Overflow or Wraparound
CERT, NUM50-J.- Convert integers to floating point for floating-point operations
CERT, INT18-C. - Evaluate integer expressions in a larger size before comparing or assigning to that size
The patch was automatically generated using the ViolationFixer tool.

@KUTEJiang : Can you fix the PR to pass the validation

@KUTEJiang I fixed the PR description. Please do that yourself next time.


[utility] Don't test colors and smarter "if it's GNU"

Looks like most (if not all) others, will report at least 8. See https://gist.github.com/michael-lazar/4e1beb7be279c72f59662127b5a234e6 (423 different terminals reporting 8, 15, 16, 52, 64, 88, or 256).
To test "if it's GNU", don't just test for the presence of dircolors, but also check if ls is GNU by accepting the --version parameter.
This is being done because MacOS's homebrew allowed installing a mixture of GNU and BSD tools together, where we got the GNU dircolors, but the BSD ls. See Homebrew/homebrew-core#36241
The homebrew changes were partially reverted in Homebrew/homebrew-core#36494, which does not mix the two tools above anymore, thus not breaking our script anymore either. But I prefer we keep this safer for the future.

Maybe we should test for NO_COLOR, or for the terminal type instead. See https://no-color.org

Closing this in favor of https://github.com/zimfw/utility/pull/1


user-driven-interop fails at exit on mpi-linux-*

This seems like a non-recurring bug that I ran into once but didn't see during the second rerun of the Travis CI.
make[3]: Entering directory '/home/travis/build/UIUC-PPL/charm/mpi-linux-ppc64le/examples/charm++/user-driven-interop'
../../../bin/testrun   +p2 ./hello_user 8
Running as 2 OS processes: ./hello_user 8
charmrun> /usr/bin/setarch ppc64le -R mpirun -np 2 ./hello_user 8
Charm++> Running in non-SMP mode: 2 processes (PEs)
Converse/Charm++ Commit ID: 8430543f7
Charm++ built with internal error checking enabled.
Do not use for performance benchmarking (build without --enable-error-checking to do so).
Isomalloc> Synchronized global address space.
CharmLB> Load balancer assumes all CPUs are same.
Charm++> Running on 1 hosts (2 sockets x 1 cores x 8 PUs = 16-way SMP)
Charm++> cpu topology info is gathered in 0.000 seconds.
Chare 0 created on PE 0
Chare 1 created on PE 0
Chare 2 created on PE 0
Chare 3 created on PE 0
Starting in user driven mode on 0
Hello from chare 0
Hello from chare 1
Hello from chare 2
Hello from chare 3
Chare 4 created on PE 1
Chare 5 created on PE 1
Chare 6 created on PE 1
Chare 7 created on PE 1
Starting in user driven mode on 1
Hello from chare 4
Hello from chare 5
Hello from chare 6
Hello from chare 7
Chare 0 got an ack from 0
Chare 1 got an ack from 0
Chare 2 got an ack from 0
Chare 3 got an ack from 0
Chare 0 got an ack from 1
Chare 1 got an ack from 1
Chare 2 got an ack from 1
Chare 3 got an ack from 1
Chare 4 got an ack from 0
Chare 5 got an ack from 0
Chare 6 got an ack from 0
Chare 7 got an ack from 0
Chare 4 got an ack from 1
Chare 5 got an ack from 1
Chare 6 got an ack from 1
Chare 7 got an ack from 1
Attempting to use an MPI routine after finalizing MPICH
real	0m0.042s
user	0m0.026s
sys	0m0.038s
make[3]: *** [Makefile:36: test] Error 1
make[2]: *** [Makefile:71: test-user-driven-interop] Error 2
make[1]: *** [Makefile:34: test-charm++] Error 2
make: *** [Makefile.tests.common:40: test] Error 2
[Partition 0][Node 0] End of program
make[3]: Leaving directory '/home/travis/build/UIUC-PPL/charm/mpi-linux-ppc64le/examples/charm++/user-driven-interop'
make[2]: Leaving directory '/home/travis/build/UIUC-PPL/charm/mpi-linux-ppc64le/examples/charm++'
make[1]: Leaving directory '/home/travis/build/UIUC-PPL/charm/mpi-linux-ppc64le/examples'
make: Leaving directory '/home/travis/build/UIUC-PPL/charm/mpi-linux-ppc64le/include'
The command "make -C mpi-linux-ppc64le/tmp test" exited with 2.

I can reproduce this even on mpi-linux-x86_64. See https://github.com/UIUC-PPL/charm/pull/3477#issuecomment-1537559759


Removing rogue parenthesis

Removing rogue parenthesis from link to VS 2015 installer

@vturecek,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@vturecek : Thanks for your contribution to the Azure documentation! The author, @rwike77, has been notified to review your proposed change.

Looks good.
#sign-off


tuna/build_driver_cmd.py -> type annotation

build_driver_cmd.py , type hints are added
added mypy cmd execution under utils.groovy->runLint()

@JehandadKhan @alexandraBara @cderb Let me know for the review update


Add new makefile target cleanall to remove files pulled down by bootstrap.sh

This is to completely clean up your working environment without touching anything that's local in the git repo. Reasons for this are when changing the go binaries or wanting to be sure your repo and build environment is completely clean.

Maybe distclean is a better target name. not completely sure. cleanall seems clear to me.

LGTM


Git115 Pull out the columns for HMS external tables

#115

Tried on my test data engine environment.
Observed:
Mon Feb 27 09:10:15 GMT 2023 server1 Information OMRS-AUDIT-0053 The Open Metadata Repository Services (OMRS) has processed 986 types and 0 instances from open metadata archive Open Metadata Types
Mon Feb 27 09:10:15 GMT 2023 server1 Startup OMRS-AUDIT-0004 Connecting to the metadata highway
Mon Feb 27 09:10:15 GMT 2023 server1 Startup OMRS-AUDIT-0005 Connecting to open metadata repository cohort cohort
Mon Feb 27 09:10:15 GMT 2023 server1 Startup OMRS-AUDIT-0029 The cohort cohort inbound event manager is initializing
Mon Feb 27 09:10:15 GMT 2023 server1 Startup OMRS-AUDIT-0030 Registering the cohort event consumer with the local repository outbound event manager
Mon Feb 27 09:10:15 GMT 2023 server1 Startup OMRS-AUDIT-0030 Registering the Local Repository Content (TypeDef) Manager event consumer with the cohort cohort inbound event manager
Mon Feb 27 09:10:15 GMT 2023 server1 Startup OMRS-AUDIT-0030 Registering the Local Repository Inbound Instance Events event consumer with the cohort cohort inbound event manager
Mon Feb 27 09:10:15 GMT 2023 server1 Startup OMRS-AUDIT-0007 The Open Metadata Repository Services (OMRS) has initialized
Mon Feb 27 09:10:15 GMT 2023 server1 Startup OMRS-AUDIT-0031 The cohort cohort inbound event manager is starting with 1 type definition event consumer(s) and 1 instance event consumer(s)
Mon Feb 27 09:10:15 GMT 2023 server1 Startup OMRS-AUDIT-0026 Initializing listener for cohort cohort
Mon Feb 27 09:10:15 GMT 2023 server1 Startup OMRS-AUDIT-0019 An OMRS Topic Connector has registered with an event bus connector for topic egeriaTopics.openmetadata.repositoryservices.cohort.cohort.OMRSTopic.registration
Mon Feb 27 09:10:15 GMT 2023 server1 Startup OCF-KAFKA-TOPIC-CONNECTOR-0001 Connecting to Apache Kafka Topic egeriaTopics.openmetadata.repositoryservices.cohort.cohort.OMRSTopic.registration with a server identifier of 3640e2a3-7e99-43b3-9297-da8f01f562bc
Mon Feb 27 09:10:15 GMT 2023 server1 Startup OCF-KAFKA-TOPIC-CONNECTOR-0015 The local server is attempting to connect to Kafka brokers at localhost:9092 [ attempt 1 of 10 ]
Mon Feb 27 09:10:16 GMT 2023 server1 Exception OMRS-HMS-REPOSITORY-0011 Error Cannot invoke "java.util.List.listIterator()" because the return value of "org.odpi.egeria.connectors.hms.ConnectorTable.getColumns()" is null in Event mapper Polling loop, the cause is No cause message

In the debugger:


General feature request[Query Builder] to copy the Query

Is your feature request related to a problem? Please describe.
Its quite easy to build and execute the query. once I build the query I don't have a option to copy the query and use it in my apex. It would be really good if we have a clone button just beside the 'Run Query' button.
Describe the solution you'd like
It would be really good if we have button called 'Copy' beside the 'Run Query' button.
Describe alternatives you've considered
I need to select the query.
Additional context
None

We've added a toggle to let you swap to the editor.  From there, you can copy or edit the query if you want to add more complex conditions.  We don't plan to add an explicit copy button to the Builder at this time.  See https://developer.salesforce.com/tools/vscode/en/soql/soql-builder/#switch-between-soql-builder-and-text-editor for details on the toggle.